Re: CPUTYPE in general - was Re: Which CPUTYPE for a dualcore Xeon on AMD64

Mike Meyer wrote: In <[EMAIL PROTECTED]>, Garrett Cooper <[EMAIL PROTECTED]> typed: Martin Turgeon wrote: Mike Meyer a écrit : In <[EMAIL PROTECTED]>, Roman Divacky <[EMAIL PROTECTED]> typed: For the record, I believe the nocona cores are: pentium 4/some prescott, prescott 2m,

Re: CPUTYPE in general - was Re: Which CPUTYPE for a dualcore Xeon on AMD64

2007/6/26, Garrett Cooper <[EMAIL PROTECTED]>: Mike Meyer wrote: > In <[EMAIL PROTECTED]>, Garrett Cooper <[EMAIL PROTECTED]> typed: > >> Martin Turgeon wrote: >> >>> Mike Meyer a écrit : >>> In <[EMAIL PROTECTED]>, Roman Divacky <[EMAIL PROTECTED]> typed: For the record, I believe

Play with the VM

Hi, I have some questions about virtual memory and the freebsd implementation. I am trying to map in userland (with a syscall like mmap) some anonymous data (from sockets, files ...). What's the best way to do this ? There are callbacks in the VM when a user process tries to access a specific addr

Re: CPUTYPE in general - was Re: Which CPUTYPE for a dualcore Xeon on AMD64

In <[EMAIL PROTECTED]>, Zavam, Vinícius <[EMAIL PROTECTED]> typed: > 2007/6/26, Garrett Cooper <[EMAIL PROTECTED]>: > > Mike Meyer wrote: > > nowadays). > > >> Intel suggests using -march=prescott (32-bit) and -march=nocona > > >> (64-bit) with gcc on Core2Duo processors and equivalent Xeons. >

strange wi driver things.

Hi.. Last kernel was build at Wed Jun 20 23:20:34 CEST 2007 from head. At first glance: 1) Channel number is +1. 2) Getting alot of wi0: record read mismatch, rid=fd44, got=8000 Where the got part changes randomly. 3) wi0: xmit failed 4) 'ifconfig wi0 list scan' returns nothing at first run, t

Re: UPEK/TouchChip Biometric Device problem

Maxim Konovalov wrote: On Fri, 22 Jun 2007, 17:42-0300, Patrick Tracanelli wrote: Hello all, I have used the mentioned devices on FreeBSD 5.4 in the past, and they worked just fine, but now I get problems with the same device, on top of 6.2-STABLE and also 7.0-CURRENT. [...] Just for the re

Re: UPEK/TouchChip Biometric Device problem

On Tue, 26 Jun 2007, 15:40-0300, Patrick Tracanelli wrote: > Maxim Konovalov wrote: > > On Fri, 22 Jun 2007, 17:42-0300, Patrick Tracanelli wrote: > > > > > Hello all, > > > > > > I have used the mentioned devices on FreeBSD 5.4 in the past, and > > > they worked just fine, but now I get problems

Re: UPEK/TouchChip Biometric Device problem

On Fri, 22 Jun 2007, 17:42-0300, Patrick Tracanelli wrote: > Hello all, > > I have used the mentioned devices on FreeBSD 5.4 in the past, and > they worked just fine, but now I get problems with the same device, > on top of 6.2-STABLE and also 7.0-CURRENT. > [...] Just for the record: the above m

Re: UPEK/TouchChip Biometric Device problem

Maxim Konovalov wrote: On Tue, 26 Jun 2007, 15:40-0300, Patrick Tracanelli wrote: Maxim Konovalov wrote: On Fri, 22 Jun 2007, 17:42-0300, Patrick Tracanelli wrote: Hello all, I have used the mentioned devices on FreeBSD 5.4 in the past, and they worked just fine, but now I get problems with

Re: UPEK/TouchChip Biometric Device problem

[...] > Exactly the same. Did you do anything different from using > securyt/bioapi, securiy/bsp_upektfmess and security/pam_bsdbioapi > and creating birdb.conf? > No, I didn't. It works out of the box. -- Maxim Konovalov ___ freebsd-hackers@freebsd.or

Re: 6.1 - amd64 arch. Hangs twice a day, how can i debug problem

On 2007-Jun-23 11:01:49 +0300, zkan KIRIK <[EMAIL PROTECTED]> wrote: > I have a FreeBSD 6.1 - STABLE 200609 gateway have 3 up interfaces. > First one connected to 16Mbps Internet Connection, > Next onet connected to DMZ Zone (192.168.0.0/24 network) > The Last interface connected to Local network.

Re: Which CPUTYPE for a dualcore Xeon on AMD64

Martin Turgeon wrote on Sun, Jun 24, 2007 at 07:32:22PM -0400: > Hi, > > I recently installed AMD64 6.2 Release on 2 PowerEdge servers, both with > dual core Xeon (3070 and 5110). I extensively benchmarked different compiler options on Xeon 5160 (3.0 GHz Core2) with gcc-4.1.2 and gcc-4.2. Apar

devfs symlink over device doesn't work

After deleting a device in devfs, any symlink placed over it results in ENOENT. # cd /dev # rm console # touch /var/log/console # ln -s /var/log/console console # ls -l console ls: console: No such file or directory I'd like to fix this behavior. Or is there a reason for it that I'm n

Gigabit Ethernet w/Jumbo Frames

I'm having poor luck trying to use NFS over a gigabit ethernet using jumbo frames. By all indications, my switch (Netgear GS608) forwards jumbo frames with no difficulty, but my Realtek 8169-based cards seem unreceptive to the idea, giving many watchdog timeouts and other obscure log messages. On

Re: devfs symlink over device doesn't work

Stef Walter wrote: > After deleting a device in devfs, any symlink placed over it results in > ENOENT. > > I'd like to fix this behavior. Or is there a reason for it that I'm not > seeing? Filed a bug report with a patch that solves the issue: http://www.freebsd.org/cgi/query-pr.cgi?pr=114057 C

Re: Gigabit Ethernet w/Jumbo Frames

On Tue, Jun 26, 2007 at 05:33:46PM -0700, [EMAIL PROTECTED] wrote: > I'm having poor luck trying to use NFS over a gigabit ethernet using > jumbo frames. By all indications, my switch (Netgear GS608) forwards > jumbo frames with no difficulty, but my Realtek 8169-based cards seem > unreceptive to

Re: Gigabit Ethernet w/Jumbo Frames

On Tue, Jun 26, 2007 at 05:33:46PM -0700, [EMAIL PROTECTED] wrote: > I'm having poor luck trying to use NFS over a gigabit ethernet using > jumbo frames. By all indications, my switch (Netgear GS608) forwards > jumbo frames with no difficulty, but my Realtek 8169-based cards seem > unreceptive

Re: Gigabit Ethernet w/Jumbo Frames

[EMAIL PROTECTED] wrote this message on Tue, Jun 26, 2007 at 17:33 -0700: > I'm having poor luck trying to use NFS over a gigabit ethernet using > jumbo frames. By all indications, my switch (Netgear GS608) forwards > jumbo frames with no difficulty, but my Realtek 8169-based cards seem Are you s