J.R. Oldroyd wrote:
On Wed, 09 Jan 2008 20:38:29 +0100, Kris Kennaway <[EMAIL PROTECTED]> wrote:
OK, same requests as to the others then.
I presume you mean hwpmc...
LOCK_PROFILING, sched_graph, hwpmc.
In setting that up, I may have stumbled upon a possible cause.
I ran pmcstat for a whi
On Wed, Jan 09, 2008 at 11:58:19PM -0500, J.R. Oldroyd wrote:
> On Wed, 09 Jan 2008 20:38:29 +0100, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> >
> >
> > OK, same requests as to the others then.
> >
>
> I presume you mean hwpmc...
>
> In setting that up, I may have stumbled upon a possible cause
On Wed, 09 Jan 2008 20:38:29 +0100, Kris Kennaway <[EMAIL PROTECTED]> wrote:
>
>
> OK, same requests as to the others then.
>
I presume you mean hwpmc...
In setting that up, I may have stumbled upon a possible cause.
I ran pmcstat for a while and ended up with a very large output
file. Having
"Julian H. Stacey" wrote:
> I too saw mountd / exports just fail on 2 systems upgraded in last
> days from 7RC4 to newest 7 Stable (CTM src-7 80, received here Jan
> 6 15:15 CEST=GMT+01:00). I am not using .snap snapshot. My other
> AMD & NFS on other FreeBSD-4 & 6 hosts remains OK.
> AMD & NFS a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Richard Bates wrote:
> Sorry for the repost...
> I don't think the first one posted..
>
> posted to freebsd.stable, freebsd-current, Freebsd-hardware
>
> I checked the hardware in the online documentation manual/hardware
>
> It only lists the bits a
Toomas Aas wrote:
Kris Kennaway wrote:
I mean use /dev/sysmouse in X instead of /dev/psm0 directly.
That's how my xorg has always been configured:
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device"
Kris Kennaway wrote:
I mean use /dev/sysmouse in X instead of /dev/psm0 directly.
That's how my xorg has always been configured:
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/sysmouse"
Toomas Aas wrote:
Kris Kennaway wrote:
Toomas Aas wrote:
# grep psm /var/run/dmesg.boot
psm0: irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model IntelliMouse, device ID 3
There was another report of problems with psm. Can you try with
sysmouse instead? If that works around the issue th
Kris Kennaway wrote:
Toomas Aas wrote:
# grep psm /var/run/dmesg.boot
psm0: irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model IntelliMouse, device ID 3
There was another report of problems with psm. Can you try with
sysmouse instead? If that works around the issue then we can
investig
http://www.thinkwiki.org/wiki/BIOS_Upgrade/X_Series
looks as if it could be valuable... Sorry for disturbing.
On 1/9/08, Johannes Dieterich <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> half offtopic: concerning the BIOS update:
>
> On 1/8/08, Nathan Lay <[EMAIL PROTECTED]> wrote:
> >
> >
> > If you
On Wed, Jan 09, 2008 at 02:18:59PM -0500, J.R. Oldroyd wrote:
[...]
> As I said, I have two systems here which exhibit this. Both systems
> here are 7.0BETA4. Different i386 hardware; both are UP systems; one is
> a fast 3200Ghz processor with 4GB ram, the other is a very slow
> processor with n
J.R. Oldroyd wrote:
I believe this same problem may also be present on 7.0, at least on
the BETA releases; BETA4 is the latest I have here.
I have the same problem on two systems here: periodically the systems
will stop dead (no mouse action, no ping responses from other systems,
processes with
Hello,
half offtopic: concerning the BIOS update:
On 1/8/08, Nathan Lay <[EMAIL PROTECTED]> wrote:
>
>
> If you can, use DR-DOS (Caldera's DOS). Not to rag on FreeDOS or
> anything, but I've had bad experiences with FreeDOS and BIOS updates.
>
> http://www.drdosprojects.de/
>
> Best Regards,
> N
I believe this same problem may also be present on 7.0, at least on
the BETA releases; BETA4 is the latest I have here.
I have the same problem on two systems here: periodically the systems
will stop dead (no mouse action, no ping responses from other systems,
processes with windows on the screen
Toomas Aas wrote:
Kris Kennaway wrote:
OK, you may need to set up hwpmc or LOCK_PROFILING to figure out what
your system is doing at that moment.
While experimenting with pmcstat I found that my problem seems to be
mouse-related. I did several tests - booted, logged in with xdm, started
an
Krassimir Slavchev wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Kris Kennaway wrote:
Krassimir Slavchev wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Here are lock profiling results with select patch applied.
OK, you are doing I/O over TCP. Are you sure you ar
Kris Kennaway wrote:
OK, you may need to set up hwpmc or LOCK_PROFILING to figure out what
your system is doing at that moment.
While experimenting with pmcstat I found that my problem seems to be
mouse-related. I did several tests - booted, logged in with xdm, started
an xterm and left 'pmc
Johan Hendriks wrote:
> it looks like I miss a lot of gmirror options.
>
>
>
> Am I doing something wrong ?
Find and symlink the directory with GEOM userland libraries to /lib/geom
before using it.
The directory should contain geom_mirror.so and other files.
OTOH, I though that a fixed for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Kris Kennaway wrote:
> Krassimir Slavchev wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hello,
>>
>> Here are lock profiling results with select patch applied.
>
> OK, you are doing I/O over TCP. Are you sure you are using
Hello all
I always use the live cd to create my gmirrors with the following
commands
Start live cd -->> fixit cdrom Livecd
Then
chroot /dist
mount -t devfs devfs /dev
gmirror load
gmirror label -v -b round-robin gm0 /dev/ad0
But on the amd64 live cd I get the following error
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Results with lock_manager and select patches and kern.hz=100
#threads#transactions/sec
1 582
5 2083
10 2030
20 2421
40 1739
60 1409
80 1124
100
21 matches
Mail list logo
