On Fri, Jun 28, 2002 at 11:39:29PM -0700, Julian Elischer wrote:
> Jake just checked something in that looks like it may be relevant.
Yes it was. `thediff' on sparc64 is solid.
Still some ast funkiness on Alpha, but it is not so bad as to make it so
someone cannot get work done on Alpha if they
you are missing kern_thread.c
On Fri, 28 Jun 2002, David O'Brien wrote:
> Not buildable on sparc64:
>
> linking kernel.debug
> procfs_ctl.o: In function `procfs_control':
> procfs_ctl.o(.text+0x56c): undefined reference to `thread_unsuspend'
> init_main.o: In function `proc0_init':
> init_main
You must have something wrong in the MD code that jake added..
I don't do anything in that code or with any allignments
none of these functions have been altered..
Jake said he had it going...
On Fri, 28 Jun 2002, David O'Brien wrote:
> On Fri, Jun 28, 2002 at 11:02:51PM -0700, David O'Brien
Jake just checked something in that looks like it may be relevant.
On Fri, 28 Jun 2002, David O'Brien wrote:
> On Fri, Jun 28, 2002 at 11:02:51PM -0700, David O'Brien wrote:
> > Not buildable on sparc64:
>
> User error. Now I get:
>
> Mounting root from ufs:/dev/ad0a
> WARNING: / was not pro
Some people have suggested to me that adding threads to the system would
harm performance on our normal applications..
Here are times for 6 buildworlds. First 3 buildworlds
on a NON KSE kernel:
---
3394.762u 1465.676s 1:27:45.19 92.3%
On Fri, Jun 28, 2002 at 11:02:51PM -0700, David O'Brien wrote:
> Not buildable on sparc64:
User error. Now I get:
Mounting root from ufs:/dev/ad0a
WARNING: / was not properly dismounted
panic: trap: memory address not aligned
cpuid = 0; Debugger("panic")
Stopped at Debugger+0x1c: ta
Not buildable on sparc64:
linking kernel.debug
procfs_ctl.o: In function `procfs_control':
procfs_ctl.o(.text+0x56c): undefined reference to `thread_unsuspend'
init_main.o: In function `proc0_init':
init_main.o(.text+0x3a8): undefined reference to `threadinit'
kern_condvar.o: In function `cv_chec
In message: <[EMAIL PROTECTED]>
Gavin Atkinson <[EMAIL PROTECTED]> writes:
: I'm going to try backing out the recent pcmcia changes (as it has a topic
: chipset) unless anyone can suggest anything else. However the hang is
: random, so it may be hard to know if the back-out it fixes it
Wm Brian McCane wrote:
>I am having a problem with a new server that I am setting up to host my
>UseNet news and email.
>
>Machine:
> 1.26GHz 512MB/L1 Cache
> 768MB PC133 Memory
> 4x60GB UDMA100 IDE Drives
> 4x36GB 160MBit SCSI Drives
>
>OS:5.0-CURRENT (yes I know, but
I did a small test today to try test the speed impact of
the KSE test.
during this, I noticed that soft updates is not having it's usual
performance increaseing effect..
Normal kernel, soft updates:
1387.881u 603.392s 35:48.63 92.6% 2694+2248k 12424+3310io 3587pf+0w
KSE kernel, soft update
Hello.
While trying to fix the bug described in a problem report about
'w -n', and finding out that it is somewhat broken*, I came to
the conclusion that our 'struct utmp' is too limiting.
I would like to modernize it as follows:
#define UT_USERSIZE 16
#define UT_LINESIZE
11 matches
Mail list logo