Re: failed to set mtrr: invalid argument

2009-05-19 Thread Laurent Grangeau

I think I can handle this answer.

This is the default behavior of Xorg 7.4. If you want to see the old  
screen, launch Xorg with the -retro option.

The command should be like this :
X -config xorg.conf.new -retro

If your mouse or your keyboard doesn't seem to work, look if you have  
enable dbus and hald. In your /etc/rc.conf, you should have  
dbus_enable="YES" and hald_enable="YES" (I'm not sure about this).


All this is explain in the handbook : Configuring X11.

Le 19 mai 09 à 19:15, Chris H  a écrit :


Quoting Robert Noland :


On Mon, 2009-05-18 at 23:40 -0700, Chris H wrote:

Quoting "Paul B. Mahol" :

> On 5/19/09, Chris H  wrote:
>> Quoting Chris H :
>>
>>> Quoting Chris H :
>>>
 Greetings,
 I'm unable to get xorg-7.4 to accomodate my Gforce4 MX 440.
 On 7.1-7.2 releases. I'm currently working (struggling) with
 it on a 7.1 install/GENERIC with cvsup over the weekend  
(Sunday),

 I've seen only a few discussions regarding this, but no joy.

 I'm not sure what to post for additional information. So I'll
 provide the output of dmesg(8), and Xorg.0.log via links.

 Thank you for all your time and consideration in this matter.

 Sincerely,
 Chris H

 Xorg log:
 http://codewarehouse.NET/output/Xorg.0.log

 relevent dmesg(8) output:
 http://codewarehouse.NET/output/dmesg.output
>>>
>>> OOPS! I guess the xorg config might be useful:
>>> http://codewarehouse.NET/output/xorg.conf.nvidia
>>>

>> SIGH... Seems that the registrar isn't paying attention.
>> They happily accepted my money, but forgot to renew the domain.
>>
>> So here's trying to attach the files...
>
> That message appears for me only when I use xf86-video-vesa  
driver.


I see. Well I'm specifically using the nv driver. Here's another
attempt to provide the relevant info:


You have more than one card in the machine, which might be confusing
things.  The mtrr failure is caused by how your bios sets up memory
regions.  It should only impact performance.

Exactly what issue are you seeing?


I'm seeing a black screen on ctl-alt-f9 (tty8)
I'm seeing the message listed as this thread topic on tty0 (ctl-alt- 
f1).

The proceedure theat led me here is:
Xorc -configure
edit /root/xorg.config.new (move all the ati related stuff to  
xorg.conf.ati).

Tweak whats left, and save it as /etc/X11/xorg.conf.nvidia.
exec Xorg -config /etc/X11/xorg.conf.nvidia

The ctl-alt-backspace won't break me out of Xorg/tty8. I am forced
to ctl-alt-f1 (where I read the error message) then use ctl-C -
which kills Xorg, and returns me to a working console.

Thank you Robert, for taking the time to respond.

--Chris H



robert.


Xorg log:
X.Org X Server 1.6.0
Release Date: 2009-2-25
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD 7.1-RELEASE i386 Current Operating
System: FreeBSD udns 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu Jan  1
14:37:25 UTC 2009
r...@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
Build Date: 16 May 2009  07:15:01AM

   Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon May 18 20:34:43 2009
(++) Using config file: "/etc/X11/xorg.conf.nvidia"
(==) ServerLayout "X.org Configured"
(**) |-->Screen "Screen0" (0)
(**) |   |-->Monitor "Monitor1"
(**) |   |-->Device "Card1"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(**) Option "AllowEmptyInput" "false"
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/local/lib/X11/fonts/Type1/" does not exist.
   Entry deleted from font path.
(WW) `fonts.dir' not found (or not valid) in
"/usr/local/lib/X11/fonts/100dpi/".
   Entry deleted from font path.
   (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/100dpi/").
(WW) `fonts.dir' not found (or not valid) in
"/usr/local/lib/X11/fonts/75dpi/".
   Entry deleted from font path.
   (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/75dpi/").
(WW) The directory "/usr/local/lib/X11/fonts/Type1/" does not exist.
   Entry deleted from font path.
(WW) `fonts.dir' not found (or not valid) in
"/usr/local/lib/X11/fonts/100dpi/".
   Entry deleted from font path.
   (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/100dpi/").
(WW) `fonts.dir' not found (or not valid) in
"/usr/local/lib/X11/fonts/75dpi/".
   Entry deleted from font path.
   (Run 'mkfontdir' on "/usr/local/lib/X11/fonts/75dpi/").
(**) FontPath set to:
   /usr/local/lib/X11/fonts/misc/,
   /usr/local/lib/X11/fonts/TTF/,
   /usr/local/lib/X11/fonts/OTF,
   /usr/local/lib/X11/fonts/misc/,
   /usr/local/lib/X11/fonts/TTF/,
   /usr/local/lib/X11/fonts/OTF,
   built-ins
(**) ModulePath set to "/usr/local/lib/xorg/modules"
(II) Loader magic: 0x6a0
(II) Module ABI versions:
   

Problem when compiling stable FreeBSD kernel

2009-05-19 Thread Laurent Grangeau
Hi !

I'm new on FreeBSD and I have some troubles with an option in the kernel
config. I was reading
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/consoles.html#CONSOLES-VIDCONTROLto
increase the resolution of my console.
So I put this two options in my kernel config file :

options VESA
options SC_PIXEL_MODE

And when I try to compile it, it says that option "VESA" is not recognise.
Is it normal ?

I'm using the stable kernel on an AMD64 cpu.
(I'm not on my computer now, so I can't send you my conf file, and the
error, but I will do it tonight.)

Laurent.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


how to compute vm.pmap.pv_entry_count from procstat ?

2008-09-06 Thread Laurent Frigault
Hi,

On a 7.0-STABLE i386 web server, I got kernel messages reporting
problems with PV entries:
Approaching the limit on PV entries, consider increasing either the 
vm.pmap.shpgperproc or the vm.pmap.pv_entry_max tunable.

This server (DELL poweredge R200 quad core 4G RAM) is having random
hang every few weeks  (need power off/on cycle, IPMI not responding
any more with those hangs) , but I don't know if the hangs are related
to a PV entries problem.

Before increasing blindly vm.pmap.shpgperproc , I would like to evaluate
a good value for vm.pmap.shpgperproc (default 200) because I remember
reading somewhere that increasing too much shpgperproc could result in
panic at boot time or later.

If I guess correctly (I did not find any understandable by me
documentation on vm.pmap.*) vm.pmap.pv_entry_count is the value
of currently used PV entries .

My idea was to use procstat -av output to compute some statistics about
the number of PV entries needed by various kind of process (apache, ...)

It should be possible to compute a good evaluation of
vm.pmap.pv_entry_count by adding some combination of RES,PRES, SHD
columns.

When I add RES,PRES, SHD values, the result is bigger than pv_entry_count.

What is the formula to retrieve pv_entry_count from procstat output or
in other words, how to compute the number of PV entries used by a
process ?

Regards,
-- 
Laurent Frigault | http://www.agneau.org/>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: major bge(4) performance problem

2007-12-15 Thread Laurent Frigault
On Fri, Dec 14, 2007 at 12:20:22PM +0300, Lenar Tukhvatullin wrote:

> > We are experiencing a problem with BCM5721 bge interfaces, which seems to
> > be able to receive at almost 1Gbps but can only transmit at < 540Mbps.

> Hello, can you test patch from Igor Sysoev with recommended tunables?
> http://lists.freebsd.org/pipermail/freebsd-net/2007-November/015951.html
> 
> Also comments from Bruce Evans:
> http://lists.freebsd.org/pipermail/freebsd-net/2007-November/015954.html
> 
> I have same problem with bge, but currently can't
> test this patch on production system.

I apply those patches (edited version) on our test server (7.0BETA4).
Unfortunately, it does not seems to change anything about our transmit
performance problem. I tried to play with the new sysctls, but without
any knowlegde on the driver internal, I did not see any noticeable
improvement and our FreeBSD mirror project remains stalled.

Regards,
-- 
Laurent Frigault | Free.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


major bge(4) performance problem

2007-12-10 Thread Laurent Frigault
Hi,

We are experiencing a problem with BCM5721 bge interfaces, which seems to
be able to receive at almost 1Gbps but can only transmit at < 540Mbps.

It is the exactly same problem describes at
http://lists.freebsd.org/pipermail/freebsd-net/2007-June/014373.html

Our test server is as Dell PE860
CPU: Intel(R) Xeon(R) CPU   X3220  @ 2.40GHz (2400.10-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x6fb  Stepping = 11
  
Features=0xbfebfbff
  Features2=0xe3bd
  AMD Features=0x20100800
  AMD Features2=0x1
  Cores per package: 4
usable memory = 8577101824 (8179 MB)
avail memory  = 8297656320 (7913 MB)

[EMAIL PROTECTED]:4:0:0:class=0x02 card=0x01e61028 chip=0x165914e4 
rev=0x11 hdr=0x00
vendor = 'Broadcom Corporation'
device = 'BCM5721 NetXtreme Gigabit Ethernet PCI Express'
class  = network
subclass   = ethernet
[EMAIL PROTECTED]:5:0:0:class=0x02 card=0x01e61028 chip=0x165914e4 
rev=0x11 hdr=0x00
vendor = 'Broadcom Corporation'
device = 'BCM5721 NetXtreme Gigabit Ethernet PCI Express'
class  = network
subclass   = ethernet


We ran the following test with FreeBSD 6.3-PRERELEASE/i386 , FreeBSD
7.0BETA4/amd64 (ULE and BSD,  with and without POLLING).

# dd if=/dev/zero bs=1m count=102400 | nc peer 15000

no firewall on the server.
netstat -i show no errors 

interface forced 1000baseTX duplex-full on both server and switch, no autoneg.

The server as 2  bge interfaces, and both have the same problem.

Peer was running 6.3-PRERELEASE/amd64 with an em interface
on peer we run :
nc -l 15000 >/dev/null

If we boot our test server with a linux ubuntu 6.0.6 and run the same test, we
can transmit at more than 900 Mbps so it is not an harware problem. But
we would like to stay away from linux on our servers.

Is there any patch/fix available for this driver ?

Unfortunatly our server has no more slot available so we can't forget the bge
interfaces and add an em interface.

I can run tests on a spare server if needed (same hardware).

Regards,
-- 
Laurent Frigault | http://www.agneau.org/>
"Ask not what Windows 2000 can do for you, ask what you can do for
Windows 2000."
- John F. Kennedy, after submitting his first bug report.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Clamav-90_2 Lockup with freebsd 6.2

2007-03-15 Thread Laurent Frigault
On Thu, Mar 15, 2007 at 08:28:10PM +, Rob MacGregor wrote:
> >> FWIW, we have several machines running with the libmap.conf hack.
> >> clamav no longer locks up, but has instead taken to occasionally dying
> >> altogether.
> > Hi,
> > I think there are other bugs in the current clamd, the main one that
> > we run into is when it tries to reload the database, and it somehow
> > confuses itself and exits.
> > 
> > http://lurker.clamav.net/message/20070314.170629.9118e704.en.html
> 
> At least on FreeBSD 5.4 I think I've tracked the problem down to -lthr:
> 
>   http://www.freebsd.org/cgi/query-pr.cgi?pr=110352
> 
> Using either -lpthread or simply not using -lthr clamd (for me) doesn't
> crash (well, not yet :>).
> 
> Only happens to me with 0.90.1 in daemon mode.  With 0.90_x or 0.90.1 in
> foreground mode it stays running afer the selfcheck.

I have seen several clamd locks under 5.5 + libthr with 0.90.1 . No
problem under 5.5 with pthread . See the 2nd part of 

http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/110334

regards,
-- 
Laurent Frigault | http://www.agneau.org/>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


[AMD64-SMP] I can't get my cpus working at 100%

2006-08-24 Thread Laurent C

Hello all,

I can't get my athlon x2 processor working at 100% on cpu-intensive apps.
I've made some tests with "john --test" and "transcode", wich are both
multithreaded apps.

For example if I launch transcode it takes between 50% and 55% cpu (on top),
and if I launch
a second transcode session on another file, the total cpu used on top is
100%, without lower the speed
of the first transcode session.

The same behavior occurs with john. A single "john --test" give me some
speed results, and the same
command with a transcode or second "john --test" give me the same speed
results but now with 100%
cpu used.

I made a "portupgrade -auf" just after building and installing my SMP kernel
and World, to be sure all is up-to-date.

So it's seems it's not a "top" output problem, but a real underuse of the
computing power.

%uname -a
FreeBSD wks02.chez.oim 6.1-STABLE FreeBSD 6.1-STABLE #0: Thu Aug 17 18:47:31
CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/WKS02_SMP  amd64

Does anyone could explain me what's happening with my system ?

--
Laurent C.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Upgrading Question

2005-11-28 Thread Laurent C
2005/11/26, Yousef Raffah <[EMAIL PROTECTED]>:
>
> Hello Everyone,


Hello,


I just thought of upgrading from FreeBSD 6 BETA5 to 6-STABLE so I
> followed the http://www.freebsd.org/doc/handbook/makeworld.html manual
> page.
> I reached to a point where I had to reboot into single user mode to
> continue with make installworld and mergemaster but I wasn't able to
> boot into single user mode. The machine was hanging saying:
>
> Trying to mount root from ufs:/dev/ad0s2a


 Did the prompt ask you to enter a shell path after this message ?
If yes, you can try to press "Enter" then type mount -a, and your slices in
/etc/fstab will be mounted, letting you continue in single user.

That's a thing I had when upgrading from 5.4 to 6-stable


I tried and tried and kept on trying with no luck, I disable some
> modules during kernel bootup and unset some variables but no luck!
>
> Anyhow, one of the guys on IRC told me to build a GENERIC kernel to at
> least boot so I built it but it panicked!
>
> My only way to boot my system now is going to the loader prompt and
> boot /boot/kernel.old/kernel
>
> No here comes my question, by booting this way, can I still create a new
> GENERIC kernel in order to upgrade my system? I would really appreciate
> your advice


I think that if you can (almost) boot with your old kernel, you must keep
it, and try to add some drivers on it.

--
Laurent
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: [FreeBSD6] kinfo_size mismatch

2005-11-22 Thread Laurent C
2005/11/21, Robert Watson <[EMAIL PROTECTED]>:
>
> On Mon, 21 Nov 2005, Laurent C wrote:
>
> >> This is almost certainly a mismatch between the kernel version and a
> >> monitoring tool that is trying to inspect kernel state (specifically,
> >> retrieve process lists). If your buildworld/installworld doesn't match
> >> your kernel version, then you need to rebuild and make sure everything
> >> is in sync. If it does, it's probably a third-party package that is out
> >> of sync and needs updating.
> >
> > Ok, I will try to buildworld and builkernel again after a fresh cvsup.
> > But for "third party packages" do you mean the "port tree", becouse I
> > though that base system and ports were completely separated and can be
> > also upgraded separately. Thanks for your reply, -- Laurent
>
> Yes -- I'd start with the base system just to confirm everything really is
> sync. If the message goes away at that point, then that is good news.
> If everything is in sync, then that pretty much leaves us with a port or
> package as being the culprit.
>
> For example, if you're running an SNMP agent package that polls system
> state once a second, that could well be the source of the message.
> What's unfortunate is that whatever program it is is not reporting which
> program it is that is generating the error, and apparently not logging it
> via syslog (I assume you checked the system logs to make sure it's not
> also being sent there -- if not, you might want to). That is definitely a
> bug, and should be fixed once we find out the culprit.


Well, after :

deleting /usr/obj
cd /usr/ports
make clean
make cleanworld
cvsup base system and ports
build and install kernel and world
and then portupgrade -f all my ports
[ouf ! :-)]

It works now like a charm and my lovely FreeBSD is again fast and stable.

But I don't know what was the problem, and there was no trace of it on any
logfile.
So its solved !

Thanks both for your support.

See you on the list.

--
Laurent
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: [FreeBSD6] kinfo_size mismatch

2005-11-21 Thread Laurent C
2005/11/19, Kris Kennaway <[EMAIL PROTECTED]>:
>
> On Sat, Nov 19, 2005 at 06:38:29PM +0100, Laurent wrote:
> > Hello all,
> >
> > I've recently upgraded my AMD64 FreeBSD station from 5.4 to 6.0 using
> > the handbook method.
> >
> > Everything seems to work OK but I have the message after repeating every
> > second on tty1 after I log on X :
> >
> > kvm_open : kinfo_proc size mismatch (expected 912 got 1088).
> >
> > After some search on Internet I gave an eye to /usr/src/sys/sys/user.h
> > for kinfo_proc_size values, but the right value (1088) is already set
> > for amd64.
> >
> > So I don't know how to solve this problem, and I'm quite afraid to touch
> > some souce code on my system.
> >
> > %uname -a
> > FreeBSD wks02.chez.oim 6.0-STABLE Thu Nov 17 19:40:44 CET 2005 amd64
> >
> > Thanks.
>
> The last time you asked this question I answered it, but I didn't see
> any response. Didn't you like my answer? :-)

 Ho I'm sorry, I've first posted my question to [EMAIL PROTECTED] instead
of freebsd-stable@freebsd.org, but it seems my message arrived at the same
place. Sorry for this double-post.
 And yes I like your answer. I tried a portugrade -fua but I had problem
with pkgdb base consistency after some port upgrades, with pkgdb taking a
long time each port to rebuild is database. So my ports are not up-to-date.
 Lets go for redoing all...
 Tank you late for your answer.
 --
Laurent
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: [FreeBSD6] kinfo_size mismatch

2005-11-21 Thread Laurent C
2005/11/19, Robert Watson <[EMAIL PROTECTED]>:
>
>
> On Sat, 19 Nov 2005, Laurent wrote:
>
> > I've recently upgraded my AMD64 FreeBSD station from 5.4 to 6.0 using
> > the handbook method.
> >
> > Everything seems to work OK but I have the message after repeating every
> > second on tty1 after I log on X :
> >
> > kvm_open : kinfo_proc size mismatch (expected 912 got 1088).
> >
> > After some search on Internet I gave an eye to /usr/src/sys/sys/user.h
> > for kinfo_proc_size values, but the right value (1088) is already set
> > for amd64.
> >
> > So I don't know how to solve this problem, and I'm quite afraid to touch
> > some souce code on my system.
>
> This is almost certainly a mismatch between the kernel version and a
> monitoring tool that is trying to inspect kernel state (specifically,
> retrieve process lists). If your buildworld/installworld doesn't match
> your kernel version, then you need to rebuild and make sure everything is
> in sync. If it does, it's probably a third-party package that is out of
> sync and needs updating.

 Ok, I will try to buildworld and builkernel again after a fresh cvsup. But
for "third party packages" do you mean the "port tree", becouse I though
that base system and ports were completely separated and can be also
upgraded separately.
 Thanks for your reply,
 --
Laurent
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


[FreeBSD6] kinfo_size mismatch

2005-11-19 Thread Laurent

Hello all,

I've recently upgraded my AMD64 FreeBSD station from 5.4 to 6.0 using 
the handbook method.


Everything seems to work OK but I have the message after repeating every 
second on tty1 after I log on X :


kvm_open : kinfo_proc size mismatch (expected 912 got 1088).

After some search on Internet I gave an eye to /usr/src/sys/sys/user.h 
for kinfo_proc_size values, but the right value (1088) is already set 
for amd64.


So I don't know how to solve this problem, and I'm quite afraid to touch 
some souce code on my system.


%uname -a
FreeBSD wks02.chez.oim 6.0-STABLE Thu Nov 17 19:40:44 CET 2005 amd64

Thanks.

--
Laurent
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


[FreeBSD6] kinfo_size mismatch

2005-11-18 Thread Laurent

Hello all,

I've recently upgraded my AMD64 FreeBSD station from 5.4 to 6.0 using 
the handbook method.


Everything seems to work OK but I have the message after repeating every 
second on tty1 after I log on X :


kvm_open : kinfo_proc size mismatch (expected 912 got 1088).

After some search on Internet I gave an eye to /usr/src/sys/sys/user.h 
for kinfo_proc_size values, but the right value (1088) is already set 
for amd64.


So I don't know how to solve this problem, and I'm quite afraid to touch 
some souce code on my system.


%uname -a
FreeBSD wks02.chez.oim 6.0-STABLE Thu Nov 17 19:40:44 CET 2005 amd64

Thanks.

--
Laurent
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"