Hello gentlemen,
I seem to have threading problems with 5.1-RELEASE. Every time I run
a multithreaded application (linked against libc_r) on a SMP system,
I get only 1 CPU loaded at any moment given. I tried different
software, including Viewperf, but results remain the same. When linked
against L
t;
> In the last episode (Sep 01), RMH said:
> > Hello gentlemen,
> >
> > I seem to have threading problems with 5.1-RELEASE. Every time I run
> > a multithreaded application (linked against libc_r) on a SMP system,
> > I get only 1 CPU loaded at any moment given. I t
Dan Nelson wrote:
> In the last episode (Sep 29), Wilko Bulte said:
> > On Mon, Sep 29, 2003 at 12:19:30PM -0700, Marcel Moolenaar wrote:
> > > I also mentioned recently (in the last couple of days) that we
> > > should worry more about sparc64 than alpha. Simply because I think
> > > alpha is on i
Sascha Holzleiter wrote:
>
> On Thu, 2003-10-02 at 15:54, Poul-Henning Kamp wrote:
> > I wouldn't think the drive take 60-90 seconds to figure out there is
> > no disk, but I'm not a scsi-specialist...
>
> Seems like it does, if there is a disc present or the tray is open there
> is no delay only
Roberto de Iriarte wrote:
>
> Scott Likens wrote:
>
> >On Thu, 2003-11-06 at 03:27, Tom wrote:
> >
> >
> >>On Thu, 6 Nov 2003, Scott Likens wrote:
> >>
> >>...
> >>
> >>
> >>>Onboard SCSI, 1gig of ECC, dual P2-450's. Never had this problem
> >>>before.
> >>>
> >>>
> >> I hope you are using P3s,
Hello gentlemen,
I have to note that currently it isn't really possible to compile
-CURRENT by GCC 2.95.x in the way it has to be. Buildkernel is
broken in several places by different means, however GCC 3.2.x
passes them successfully, even with no warnings shown.
Namely, first problem is in bsd.k
> On Thu, Mar 20, 2003 at 03:21:13AM +0000, RMH wrote:
> > I have to note that currently it isn't really possible to compile
> > -CURRENT by GCC 2.95.x in the way it has to be. Buildkernel is
> > broken in several places by different means, however GCC 3.2.x
> > pas
Hello gentlemen,
I've observed a very strange SCSI trouble never seen before.
It happened suddenly, under very low system load and disk
activity; though it didn't lead to any damage or data loss,
but I'm curious what could be a cause. Visually, it appeared
like a delay in disk access but at the sa
Hello gentlemen,
it seems CPU_SUSP_HLT does nothing for SMP kernels.
i386/i386/machdep.c:
#ifdef SMP
static int cpu_idle_hlt = 0;
#else
static int cpu_idle_hlt = 1;
#endif
It's noted that when enabled it will result in about 4.2%
loss in performance while doing buildworld. I haven't
c
