scalbn and scalbnf failure on amd64

If you do (in -current) something like:

  cd /usr/tests/lib/libm && atf-run t_scalbn | atf-report

you will get:

Failed test cases:
    t_scalbn:scalbn_ldexp, t_scalbn:scalbnf_ldexpf

Summary for 1 test programs:
    18 passed test cases.
    2 failed test cases.
    0 expected failed test cases.
    0 skipped test cases.

The failures in more detail show up if you only run "atf-run t_scalbn":

tc-se:*** Check failed: /usr/src/tests/lib/libm/t_scalbn.c:168: test 2: exponent=-1, y=inf,
expected 1.45644 (diff: inf)
tc-se:*** Check failed: /usr/src/tests/lib/libm/t_scalbn.c:168: test 4: exponent=-100, y=inf,
expected 2.29786e-30 (diff: inf)

and:

tc-se:*** Check failed: /usr/src/tests/lib/libm/t_scalbn.c:321: test 2: exponent=-1, y=1.45644
ldexpf returns inf (diff: -inf)
tc-se:*** Check failed: /usr/src/tests/lib/libm/t_scalbn.c:321: test 4: exponent=-100,
y=2.29786e-30 ldexpf returns inf (diff: -inf)

which basically means that

Changing the default i387 precision

Hi all,
one of the missing parts of our libm is proper long double support for
x86. This is somewhat complicated by the fact that our long double is
castrated by the default rounding to 53bit (a.k.a. double) mantissa
size. The historic reason is that forcing double rounding in code that
needs the precision to be exact requires care and in theory, it might
change results of code that doesn't expect it. Given that Linux and
FreeBSD default to the whole mantissa, I doubt that the second argument
is valid. It doesn't normally apply to amd64 anyway, since most
compilers will default to the faster SSE units for double arithmetic
anyway. This leads to the important question of whether we want to have
real long double or not. Opinions?

Joerg

port-amd64/47782 - ifconfig SIOCSIFMEDIA error with bge

Just a quick follow up to port-amd64/47782

I did a fresh install on several SuperMicro amd64 servers with bge ethernet
interfaces and configured both bge's in an acceptable fashion.  I then clean
booted the servers 865 times to gather some stats.

Background:  I'm using NetBSD ukato 6.0.1 NetBSD 6.0.1 (GENERIC) amd64.  I
was using a custom kernel with bge/brgphy, but thought for this test using
generic would be best.

ifconfig.bge0:
up
media autoselect
192.94.73.7 netmask 0xffffff00 media autoselect

ifconfig.bge1:
up
media autoselect
10.0.0.7 netmask 0xffffff00 media autoselect

bge1 always had its interface successfully configured.  However, bge0
failed with an ifconfig: SIOCSIFMEDIA: Invalid argument 343 times, but was
successful 522 times (total of 865 clean boots).

For media and mediaopts I did implicitly set those, but still ran into issues
with bge0 failing iwth a SIOCSIFMEDIA.  When the interface is in this state,
you cannot even do a simple ifconfig bge0 192.94.73.7 to bring the interface
up even by doing a ksh /etc/rc.d/network stop first.  I believe that this
is likely a serious bug.  Originally I thought that this may be an autoneg
issue with the switch, but simple ifconfigs are failing without a reboot.

Intermittent SpeedStep?

I have a machine I'm running amd64 5.2 on.  It is apparently
SpeedStep-capable, but only intermittently.  I've set up code to record
boot-time messages (via /var/run/dmesg.boot) on each boot.  It's a
relatively mobile machine, so it gets rebooted frequently.  And I see
SpeedStep appearing only sometimes.

For example, the boot of 2013-03-05 04:41:33 shows

cpu0 at mainbus0 apid 0: Intel 686-class, 2493MHz, id 0x10676
cpu1 at mainbus0 apid 1: Intel 686-class, 2493MHz, id 0x10676

but the boots of 2013-03-05 12:44:12 and 2013-03-06 18:33:30 showed

cpu0 at mainbus0 apid 0: Intel 686-class, 2493MHz, id 0x10676
cpu0: Enhanced SpeedStep (1068 mV) 600 MHz
cpu0: Enhanced SpeedStep frequencies available (MHz): 7600 7000 6400 5700 5100 4500 3800 3200 2600 1900
1300 700
cpu1 at mainbus0 apid 1: Intel 686-class, 2493MHz, id 0x10676

Any idea what could be behind this intermittent presence?  Even without
a complete answer to that, is there anything I can do to make it work
more often?

In case it helps, here's what cpuctl identify 0 has to say:

cpu0: Intel Core 2 Extreme (686-class), 2493.94 MHz, id 0x10676
cpu0: features 0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR>
cpu0: features 0xbfebfbff<PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX>
cpu0: features 0xbfebfbff<FXSR,SSE,SSE2,SS,HTT,TM,SBF>
cpu0: features2 0x8e3bd<SSE3,DTES64,MONITOR,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE41>

Does that work? Intel C204 PCH Chipset on /AMD

Hello dear NetBSD/AMD-supporters,

I am currently evaluating whether I can switch to a server with a 
chipset "Intel C204 PCH Chipset" running NetBSD/AMD with 64Bit support.
Mainboard would be a "Supermicro X9SCM-F" with "Intel Xeon E3-1200" CPU.

Are there any contras on running such a system (apart speed, the server 
is for personal use)?

Please answer with Cc to me, I am currently not subscribed.

Thanks!

--
Markus Illenseer

32bit linux emulation on amd64

Hello,

I did at one time have working 32bit linux emulation on amd64. This
involved:

a few suse100_32_* packages, auto-fetched by wip/tsm 

procfs /usr/pkg/emul/linux32/proc proc ro 0 0
tmpfs /usr/pkg/emul/linux32/dev/shm tmpfs rw 0 0

and a link /emul/linux32 -> /usr/pkg/emul/linux32

The machine did run NetBSD-5.1.x at that time.

Nowadays, it's running -6.0 (_RC2, to be exact), and after some
scratching about an updated package I'm working on, which only
prints "abort", I noted that /emul/linux32/bin/ldd did abort, too,
so I tried /emul/linux32/bin/date which aborts, too.

I tried several different suse32_base packages - freshly built
suse113 and suse121 and the old suse100 from netbsd-5 times - no
change.

config -x claims that

COMPAT_LINUX
COMPAT_LINUX32
COMPAT_NETBSD32
EXEC_ELF32

Hello

We have approved a cash sum of $500,000.00 USD as our personal donation to you this new year 2013.Contact us
via email : densagl <at> aol.com
Regards

RAID5 3x 3TB SATA drives, help!

I cannot get this to work!

Using NetBSD 6.0.1/amd64 with 3x 3TB SATA disks as RAID5, booting from a 
CF card.

I've set up a dk partition on all 3 disks, set the RAID up on dk0, 1 and 
2, created a new dk3 device on the RAID. All works so far but I'm unable 
to mount dk3 as the root file system; it seems that NetBSD doesn't 
support autoconfigure of a dk file system, unless there's something I've 
missed?

Have googled and found this:

http://mail-index.netbsd.org/netbsd-users/2012/07/20/msg011157.html

which seems like someone's having the same problem. Googling is limited 
as it sees the "dk" in the search string and tends to return a whole lot 
of Danish websites...

Is there a HOWTO somewhere on how to do this? Failing that is it 
possible to change the root filesystem "on-the-fly" from wd3a to dk3 
before going multi-user?

Thanks in advance... while I still have some hair left!

--

-- 
  Squirrel Solutions Ltd                             Tel: (01453) 845735
  http://www.squirrelsolutions.co.uk/                Fax: (01453) 843773

  Registered in England: 05877408

de vendedor a cerrador

Boot failure while installing on ASUS UEFI

Hi guys,

I am not sure this is the most perfect place to post, please redirect me
if needed.

I tried to boot NetBSD 6.0 amd64 CD on ASUS P8H61-M LX3 board, which
features H61 chipset, HD3000 integrated graphics, and a UEFI firmware;
the boot started, but stopped on init panic just after the USB
enumeration; the 2nd to last message was
	warning: no /dev/console
which I believe is the direct cause.

I am not very used to *BSD, and I was not able to dump dmesg into some
usable device; but I successfully booted FreeBSD 9.1, and I noticed that
FreeBSD detects the graphics adapter when enumerating the PCI buses;
while no similar message showed detection of a class-2 (video) device on
NetBSD.

What are my options at this point?

Antoine

RE: BETA6.0 - AMD Opetron 6272 (16 core) multiprocessor config crashes

Manuel

A funny thing happened today.. we were trying to replicate this issue in our
lab and were never able to reproduce it.. however in the lab once we
connected a network cable and enabled the 2nd nic .. the server crashed in
minutes..

So seems like having one network interface connected makes this work.. I can
have all 16 cores running and processing with no error and any work load..
however the moment I connect and activate the second nic.. (even if no data
flows on the second nic) the server crashs.. keep the second nic and reboot
netbsd in SMB mode and it works.. 

So theres something related to the 2nd nic that causing this issue..

Hope this helps.. I can live by disabling the second nic, but if a solution
is possible it would be great..

I am using netbsd 6.0 currently.

Derrick

-----Original Message-----
From: Manuel Bouyer [mailto:bouyer <at> antioche.eu.org] 
Sent: Wednesday, May 02, 2012 9:23 AM
To: Derrick Lobo
Subject: Re: BETA6.0 - AMD Opetron 6272 (16 core) multiprocessor config
crashes

On Wed, May 02, 2012 at 08:43:15AM -0400, Derrick Lobo wrote:
> Thanks Manuel
> 
> I will try disabling ixpide0 and 1
> 
> I am also running boot netbsd -2 as it usually hangs when I do a 
> normal boot.

Hum, can you tell me where it hangs ?
Also, I'm running with the attached patch. I could boot without it a GEENRIC
kernel, but XEN3_DOM0 would panic without it.
I'm not sure it the problem affects your config too.

--
Manuel Bouyer <bouyer <at> antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--