From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 26 22:35:20 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4840C16A4CE for ; Sun, 26 Dec 2004 22:35:20 +0000 (GMT) Received: from ns.yar.post.ru (ns.yar.post.ru [213.187.102.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0168543D62 for ; Sun, 26 Dec 2004 22:35:14 +0000 (GMT) (envelope-from liettneff@bk.ru) Received: from gate-corbina.km.vibrators.ru (km.yar.post.ru [213.187.105.186]) by ns.yar.post.ru (8.12.9p2/8.12.9) with ESMTP id iBQMZ9ql048180 for ; Mon, 27 Dec 2004 01:35:10 +0300 (MSK) (envelope-from liettneff@bk.ru) Received: from comp-reaper (reaper.1.168.192.in-addr.arpa [192.168.1.100] (may be forged))iBQMZ0Ik075648 for ; Mon, 27 Dec 2004 01:35:02 +0300 (MSK) (envelope-from liettneff@bk.ru) Date: Mon, 27 Dec 2004 01:34:30 +0300 From: Mike X-Mailer: The Bat! (v2.01) Business Organization: none X-Priority: 3 (Normal) Message-ID: <39261500.20041227013430@bk.ru> To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: xdelta@amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: liettneff List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Dec 2004 22:35:20 -0000 Hello, freebsd-amd64. i've noticed strange behaviour of xdelta on amd64. it refuses to apply deltas created on i386. command xdelta patch ...xdelta results in xdelta: @@@SerialSource: Incorrect allocation deltas created on amd64 applying fine on i386 -- Best regards, Mike mailto:liettneff@bk.ru From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 27 01:31:31 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3817316A4CE; Mon, 27 Dec 2004 01:31:31 +0000 (GMT) Received: from phoenix.gargantuan.com (phoenix.gargantuan.com [24.73.171.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99E5D43D48; Mon, 27 Dec 2004 01:31:30 +0000 (GMT) (envelope-from michael@gargantuan.com) Received: from localhost (localhost.gargantuan.com [127.0.0.1]) by spamassassin-injector (Postfix) with SMTP id 927D9612; Sun, 26 Dec 2004 20:31:29 -0500 (EST) Received: by phoenix.gargantuan.com (Postfix, from userid 1001) id 07135417; Sun, 26 Dec 2004 20:31:18 -0500 (EST) Date: Sun, 26 Dec 2004 20:31:18 -0500 From: "Michael W. Oliver" To: freebsd-amd64@freebsd.org Message-ID: <20041227013118.GA76674@gargantuan.com> References: <20041220152647.GA31796@gargantuan.com> <20041223163929.GA52351@gargantuan.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline In-Reply-To: <20041223163929.GA52351@gargantuan.com> X-WWW-Site: http://michael.gargantuan.com X-PGP-Public-Key: $X-WWW-Site/gnupg/pubkey.asc X-PGP-Fingerprint: 2694 0179 AE3F BFAE 0916 0BF5 B16B FBAB C5FA A3C9 X-Home-Phone: +1-863-816-8091 X-Mobile-Phone: +1-863-738-2334 X-Home-Address0: 8008 Apache Lane X-Home-Address1: Lakeland, FL X-Home-Address2: 33810-2172 X-Home-Address3: United States of America X-Good-Question-Guide: http://www.catb.org/~esr/faqs/smart-questions.html X-Netiquette-Guidelines: http://www.ietf.org/rfc/rfc1855.txt User-Agent: Mutt/1.5.6i X-Spam-DCC: dcc.uncw.edu: phoenix.gargantuan.com 1201; Body=1 Fuz1=1 Fuz2=1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on phoenix.gargantuan.com X-Spam-Level: X-Spam-Status: No, score=-105.5 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, USER_IN_WHITELIST autolearn=ham version=3.0.1 X-Spam-Pyzor: Reported 0 times. cc: simokawa@freebsd.org Subject: Re: fwohci init on 5.3-RELEASE blowing up X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2004 01:31:31 -0000 --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004-12-23T11:39:29-0500, Michael W. Oliver wrote: > On 2004-12-20T10:26:47-0500, Michael W. Oliver wrote: > > Good morning folks, I am having trouble here and hope that you can help. > > I just got a new machine here, and it is giving me fits with FreeBSD > > 5.3-RELEASE (amd64 ISO). I am saying that this is a fwohci issue based > > on the following thread on the dfly list: > > http://marc.theaimsgroup.com/?t=3D109967176800001&r=3D1&w=3D2 > > also noted in this thread: > > http://lists.freebsd.org/pipermail/freebsd-current/2004-November/thread= =2Ehtml#42637 > > My question: Is there a way to disable firewire at the loader prompt so > > that I can get FreeBSD installed and cvsup to a point where this is > > fixed? If not, perhaps my only choice is to find a amd64 snapshot since > > I cannot disable firewire in the BIOS. > > Other suggestions welcome, thanks. > Anyone want to take a stab at this? I would really like to get FreeBSD > installed and running on this machine. I cannot find a snapshot site > that has updated snapshots post-5.3-RELEASE, and just can't get my head > around building a custom release (though, I will keep trying). > Here is the exact output (hand-transcribed) from booting a 5.3-RELEASE > amd64 ISO: > -----------------8<---------------------------------------- > [...] > fwohci0: mem 0xd0000000-0xd0003ff= f,0xd0008000-0xd00087ff irq 17 at device 6.0 on pci0 > fwohci0: Reserved 0x800 bytes for rid 0x10 type 3 at 0xd0008000 > fwohci0: [MPSAFE] > fwohci0: OHCI version 1.10 (ROM=3D1) > NMI ISA b0, EISA ff > RAM parity error, likely hardware failure. > Fatal trap 19: non-maskable interrupt trap while in kernel mode > instruction pointer =3D 0x8:0xffffffff8024db66 > stack pointer =3D 0x10:0xffffffff80c99950 > frame pointer =3D 0x10:0xffffffff80e39000 > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags =3D interrupt enabled, IOPL =3D 0 > current process =3D 0 (swapper) > trap number =3D 19 > panic: non-maskable interrupt trap > Uptime: 1s > Shutting down ACPI > Automatic reboot in 15 seconds - press a key on the console to abort > -----------------8<---------------------------------------- > I get the same message (though with slightly different pointers) when > booting the 5.3-RELEASE amd64 ISO with ACPI disabled, as well as with > the FreeSBIE 1.1 i386 ISO with and without ACPI. > I went to http://www.freebsd.org/releases/snapshots.html and from there > to ftp://current.freebsd.org/pub/FreeBSD/snapshots/amd64/ but couldn't > find anything newer than late-October. > I did just now download the latest snapshot of dragonflybsd, dated > 2004-12-22 (dfly-20041222-stable.iso.gz), and it will boot up without > panic on fwohci. > Any help at all getting 64bit FreeBSD installed and running on this > machine would be most appreciated. Thanks. OK, I have tried in vain now 6 times to build a custom release to get FreeBSD installed on this laptop. If I were a newbie to FreeBSD, I would have long since thrown in the towel and stuck with LINUX. But, alas, I am not that person. Unfortunately, I am no kernel/build hacker either, which means that I get to spend 5+ hours on each build attempt, only to fail again and again. In the end, all I would like is an installation CD that doesn't blow up when probing my firewire controller. Sounds simple, eh? First try: ------------ I have one fast machine that I was going to try the cross-build on, just for the sake of getting it done quickly. Unfortunately, it is running 4.9, and the build of RELENG_5/amd64 blew up initially because of missing proxy, authpf, and _pflogd groups and missing proxy & _pflogd users. Once those were added, the build blew up again due to missing /sbin/mdconfig, which doesn't exist on my 4.9 box. Well, so much for doing a quick cross-build on this machine. Subsequent tries: ------------------- This machine is a P2/400MHz running -CURRENT from about 2 weeks ago, which means that it has the /sbin/mdconfig that was missing on the 4.9 machine. Hooray! Unfortunately, this machine is painfully slow at building an entire release. First build attempt failed trying to 'make index' for ports, so I started again with 'NOPORTS=3DYES'. This worked for a little while longer, then failed again with the following error: ------8<------------------------------- [...] ln /R/stage/mfsfd/stand/etc/services /R/stage/mfsfd/etc/services ln /R/stage/mfsfd/stand/etc/group /R/stage/mfsfd/etc/group ln /R/stage/mfsfd/stand/etc/netconfig /R/stage/mfsfd/etc/netconfig cp /R/stage/trees/base/COPYRIGHT /R/stage/mfsfd/stand/help/COPYRIGHT.hlp test -f /usr/src/release/install.cfg && cp /usr/src/release/install.cfg /R/stage/mfsfd *** Error code 1 (ignored) sh -e /usr/src/release/scripts/doFS.sh bsdlabel amd64 /R/stage/mfsroot/mfsr= oot /R/stage /mnt 4096 /R/stage/mfsfd 8192 auto + export BLOCKSIZE=3D512 + DISKLABEL=3Dbsdlabel + shift + MACHINE=3D-m amd64 + shift + FSIMG=3D/R/stage/mfsroot/mfsroot + shift + RD=3D/R/stage + shift + MNT=3D/mnt + shift + FSSIZE=3D4096 + shift + FSPROTO=3D/R/stage/mfsfd + shift + FSINODE=3D8192 + shift + FSLABEL=3Dauto + shift + [ 4096 -eq 0 -a auto =3D auto ] + rm -f /R/stage/mfsroot/mfsroot + dd of=3D/R/stage/mfsroot/mfsroot if=3D/dev/zero count=3D4096 bs=3D1k + uname -r + [ -f /R/stage/trees/base/boot/boot ] + BOOT=3D-B -b /R/stage/trees/base/boot/boot + dofs_md + [ x !=3D x ] + mdconfig -a -t vnode -f /R/stage/mfsroot/mfsroot mdconfig: ioctl(/dev/mdctl): Inappropriate ioctl for device + MDDEVICE=3D *** Error code 1 Stop in /usr/src/release. + umount /dev *** Error code 1 Stop in /usr/src/release. ------8<------------------------------- Guys, I am now to the point of begging for suggestions to get this working. I am not going to give up, ever, but I would like to get this working before I retire. Does the build machine have to be running the same release that you are trying to build? The man page and various results from googling seem to indicate the answer is no. If the answer is no, then wtf is my problem? Am I going way overboard here trying to build a custom release with fwohci_pci.c patched? I mean, the firewire is included in GENERIC, which means that it is loaded with the kernel from the 5.3-RELEASE ISO, and as such, I cannot unload it from the loader prompt (lsmod only shows the kernel loaded, with a bunch of stuff after it, including firewire.1). Since it is built into the kernel, am I right that it cannot be unloaded separate from the other stuff? Oh, I have also submitted my first PR ever, which includes the patch =66rom the dfly list, which (ironically) was submitted to that list by the same guy who made the most recent commits to FreeBSD's fwohci_pci.c in CVS. Perhaps he will commit his patch to the FreeBSD tree, perhaps someone will see the PR (kern/75482) and commit it. I am actually really trying here guys, toss me a bone or two. --=20 Michael W. Oliver [see complete headers for contact information] --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBz2XmsWv7q8X6o8kRAjpqAKDCGDU1HrhEYHxOWE1h7k+3QZbhQgCbBSGF sRKpcAajQ3GP/xzXhxrNH5Y= =sEDA -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh-- From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 27 11:02:11 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A18D16A4CE for ; Mon, 27 Dec 2004 11:02:11 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49AD543D1F for ; Mon, 27 Dec 2004 11:02:11 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iBRB2B6w030160 for ; Mon, 27 Dec 2004 11:02:11 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iBRB2AbF030154 for freebsd-amd64@freebsd.org; Mon, 27 Dec 2004 11:02:10 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 27 Dec 2004 11:02:10 GMT Message-Id: <200412271102.iBRB2AbF030154@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2004 11:02:11 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/10/27] amd64/73211 amd64 FAST_IPSEC broken on amd64 1 problem total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59714 amd64 device timeout and ad0: WARNING - WRITE_D o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/09/07] amd64/71471 amd64 Can not install 5.3beta3/amd64 on IBM eSe o [2004/10/28] amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was see o [2004/10/30] amd64/73322 amd64 unarchiving /etc to msdos fs locks up amd o [2004/11/01] amd64/73369 amd64 on-board firewire unreliable with Asus K8 o [2004/11/07] amd64/73650 amd64 5.3-release panics on boot o [2004/11/10] amd64/73775 amd64 Kernel panic (trap 12) when booting with o [2004/11/16] amd64/74014 amd64 5.3-RELEASE-AMD64 freezes on boot during o [2004/12/05] amd64/74747 amd64 System panic on shutdown when process wil o [2004/12/18] amd64/75209 amd64 5.3-Release panics on attempted boot from o [2004/12/23] amd64/75417 amd64 ACPI: SATA Hard-disk 13 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/01/11] amd64/61209 amd64 ppc0: cannot reserve I/O port range o [2004/02/21] amd64/63188 amd64 ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/07/28] amd64/69709 amd64 ACPI enabled then floppy don't work (5.2. o [2004/08/15] amd64/70500 amd64 bge driver for 3Com 3C996B on amd64 preve o [2004/12/02] amd64/74608 amd64 mpt hangs 5 minutes when booting o [2004/12/07] amd64/74811 amd64 df, nfs mount, negative Avail -> 32/64-bi o [2004/12/25] amd64/75488 amd64 ntfs_iconv not working on amd64 8 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 27 14:01:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8F0416A4CE for ; Mon, 27 Dec 2004 14:01:56 +0000 (GMT) Received: from kong.rascom.ru (kong.rascom.ru [80.64.99.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB89943D45 for ; Mon, 27 Dec 2004 14:01:55 +0000 (GMT) (envelope-from kong@kong.spb.ru) Received: from kong.rascom.ru (localhost [127.0.0.1]) by kong.rascom.ru (8.13.1/8.12.9) with ESMTP id iBRE1rXT039017 for ; Mon, 27 Dec 2004 17:01:53 +0300 (MSK) (envelope-from kong@kong.spb.ru) Received: from localhost (kong@localhost) by kong.rascom.ru (8.13.1/8.12.10/Submit) with ESMTP id iBRE1qZS039014 for ; Mon, 27 Dec 2004 17:01:53 +0300 (MSK) (envelope-from kong@kong.spb.ru) X-Authentication-Warning: kong.rascom.ru: kong owned process doing -bs Date: Mon, 27 Dec 2004 17:01:52 +0300 (MSK) From: Hostas Red X-X-Sender: kong@kong.rascom.ru To: freebsd-amd64@freebsd.org Message-ID: <20041227163559.L38579@kong.rascom.ru> X-NCC-RegId: ru.rascom MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: aac controller in amd64 very slow? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2004 14:01:57 -0000 Hi! 1) I have one Quad Opteron box with FreeBSD 5.3-amd64 installed and have strange downgrade in performance with Adaptec 2120S raid controller (acc driver, 4-disk RAID5 configured). It is approx. 30-40% loss in performance of disk operations compared to my previous Dual 2.4 Xeon with Adaptec 2015S with two disks mirrored. Is it normal or maybe I need some tweaking? Also one of my colleagues suggested installation of i386 version of 5.3 for speeding things up, that sound strange for me. I'm new for amd64 version of freebsd, but using freebsd-i386 for 7 years or so on i386 platforms. May this problem be an amd64-specific? Any suggestions how I can resolve this problem? 2) One more Q - apache is eating a lot of memory when running - about 64M for each process instead of usual approx 7-10M per process on previous i386 with same compiled configuration: == from top === PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 3351 www 96 0 69560K 18712K select 3 0:01 0.93% 0.93% httpd ========== Other programs looks the same or about it. Is it normal for amd64 platform or also my mistake? 3) And one more Q - box has 4G of memory, but kernel can see only 3.5G, as can be seen from following dmesg output. What can be a problem? Box is a Tyan's Thunder K8QS Pro (S4882) 4-way AMD Opteron platform (with Tyan S4882UG2NR board). Disk split in two parts: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/aacd0s1a 6090094 1998300 3604588 36% / devfs 1 1 0 100% /dev /dev/aacd0s1d 402268316 26148124 343938728 7% /work On /, of course, is a system and second one is working partiton. Here's boot message of the new box: Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #2: Mon Dec 27 08:27:05 GMT 2004 root@sys154.3fn.net:/usr/obj/usr/src/sys/kong Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 846 (1992.22-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 Features=0x78bfbff AMD Features=0xe0500800 real memory = 3757506560 (3583 MB) avail memory = 3627720704 (3459 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard ioapic3 irqs 32-35 on motherboard ioapic4 irqs 36-39 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) unknown: I/O range not supported unknown: I/O range not supported Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xc008-0xc00b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 acpi_button0: on acpi0 pcib0: port 0xc080-0xc0ff,0xc000-0xc07f,0xcf8-0xcff iomem 0xd8000-0xdbfff on acpi0 pci0: on pcib0 pcib1: at device 6.0 on pci0 pci1: on pcib1 ohci0: mem 0xe8000000-0xe8000fff irq 19 at device 0.0 on pci1 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xe8001000-0xe8001fff irq 19 at device 0.1 on pci1 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered pci1: at device 4.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1000-0x100f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 7.3 (no driver attached) pcib2: on acpi0 pci8: on pcib2 pcib3: at device 1.0 on pci8 pci9: on pcib3 aac0: mem 0xf8000000-0xfbffffff irq 26 at device 2.0 on pci9 aac0: [FAST] aac0: Enabling 64-bit address support aac0: Unknown processor 100MHz, 48MB cache memory, optional battery not installed aac0: Kernel 4.1-0, Build 7244, S/N be37b0 aac0: Supported Options=11d7e aacp0: on aac0 pci8: at device 1.1 (no driver attached) pcib4: at device 2.0 on pci8 pci14: on pcib4 mpt0: port 0x3000-0x30ff mem 0xed000000-0xed00ffff,0xed010000-0xed01ffff irq 29 at device 1.0 on pci14 mpt0: [GIANT-LOCKED] mpt1: port 0x3400-0x34ff mem 0xed020000-0xed02ffff,0xed030000-0xed03ffff irq 30 at device 1.1 on pci14 mpt1: [GIANT-LOCKED] bge0: mem 0xed040000-0xed04ffff,0xed050000-0xed05ffff irq 31 at device 3.0 on pci14 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:00:1a:1a:0d:5a bge1: mem 0xed060000-0xed06ffff,0xed070000-0xed07ffff irq 28 at device 3.1 on pci14 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:00:1a:1a:0d:5b pci8: at device 2.1 (no driver attached) pcib5: mem 0xea202000-0xea202fff irq 32 at device 3.0 on pci8 pci19: on pcib5 pci8: at device 3.1 (no driver attached) pcib6: mem 0xea204000-0xea204fff irq 36 at device 4.0 on pci8 pci27: on pcib6 pci8: at device 4.1 (no driver attached) atkbdc0: port 0x64,0x60 irq 1 on acpi0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 orm0: at iomem 0xcc800-0xd0fff,0xcb000-0xcc7ff,0xc9800-0xcafff,0xc9000-0xc97ff,0xc8000-0xc8fff,0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec ipfw2 initialized, divert disabled, rule-based forwarding disabled, default to accept, logging disabled acd0: DVDROM at ata0-master UDMA33 Waiting 15 seconds for SCSI devices to settle aacd0: on aac0 aacd0: 419943MB (860045184 sectors) (probe0:aacp0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe0:aacp0:0:0:0): ILLEGAL REQUEST asc:55,3 (probe0:aacp0:0:0:0): Reserved ASC/ASCQ pair (probe5:aacp0:0:5:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe5:aacp0:0:5:0): ILLEGAL REQUEST asc:55,3 (probe5:aacp0:0:5:0): Reserved ASC/ASCQ pair (probe9:aacp0:0:10:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe9:aacp0:0:10:0): ILLEGAL REQUEST asc:55,3 (probe9:aacp0:0:10:0): Reserved ASC/ASCQ pair (probe10:aacp0:0:11:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe10:aacp0:0:11:0): ILLEGAL REQUEST asc:55,3 (probe10:aacp0:0:11:0): Reserved ASC/ASCQ pair (probe13:aacp0:0:14:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe13:aacp0:0:14:0): ILLEGAL REQUEST asc:55,3 (probe13:aacp0:0:14:0): Reserved ASC/ASCQ pair (probe1:aacp0:0:1:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe1:aacp0:0:1:0): ILLEGAL REQUEST asc:55,3 (probe1:aacp0:0:1:0): Reserved ASC/ASCQ pair (probe2:aacp0:0:2:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe2:aacp0:0:2:0): ILLEGAL REQUEST asc:55,3 (probe2:aacp0:0:2:0): Reserved ASC/ASCQ pair (probe3:aacp0:0:3:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe3:aacp0:0:3:0): ILLEGAL REQUEST asc:55,3 (probe3:aacp0:0:3:0): Reserved ASC/ASCQ pair (probe4:aacp0:0:4:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe4:aacp0:0:4:0): ILLEGAL REQUEST asc:55,3 (probe4:aacp0:0:4:0): Reserved ASC/ASCQ pair (probe6:aacp0:0:6:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe6:aacp0:0:6:0): ILLEGAL REQUEST asc:55,3 (probe6:aacp0:0:6:0): Reserved ASC/ASCQ pair (probe7:aacp0:0:8:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe7:aacp0:0:8:0): ILLEGAL REQUEST asc:55,3 (probe7:aacp0:0:8:0): Reserved ASC/ASCQ pair (probe8:aacp0:0:9:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe8:aacp0:0:9:0): ILLEGAL REQUEST asc:55,3 (probe8:aacp0:0:9:0): Reserved ASC/ASCQ pair (probe11:aacp0:0:12:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe11:aacp0:0:12:0): ILLEGAL REQUEST asc:55,3 (probe11:aacp0:0:12:0): Reserved ASC/ASCQ pair (probe12:aacp0:0:13:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe12:aacp0:0:13:0): ILLEGAL REQUEST asc:55,3 (probe12:aacp0:0:13:0): Reserved ASC/ASCQ pair (probe14:aacp0:0:15:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe14:aacp0:0:15:0): ILLEGAL REQUEST asc:55,3 (probe14:aacp0:0:15:0): Reserved ASC/ASCQ pair SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! Mounting root from ufs:/dev/aacd0s1a Thank You. adios, /kong ======================================================================== Hostas Red (KVK10, KVK10-RIPE) || IP Networks Administrator, CJSC Rascom ======================================================================== From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 27 19:33:11 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 33E7116A4CE; Mon, 27 Dec 2004 19:33:11 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A89E43D55; Mon, 27 Dec 2004 19:33:08 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id iBRJX2Jt026905; Mon, 27 Dec 2004 14:33:02 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org Date: Mon, 27 Dec 2004 14:32:48 -0500 User-Agent: KMail/1.6.2 References: <20041214182153.GA80721@ip.net.ua> <1103066141.2041.4.camel@server.mcneil.com> <20041215102625.GM25967@ip.net.ua> In-Reply-To: <20041215102625.GM25967@ip.net.ua> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Multipart/Mixed; boundary="Boundary-00=_gNG0BOrY9Rv3wKf" Message-Id: <200412271432.48988.jkim@niksun.com> X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on anuket.mj.niksun.com X-Virus-Status: Clean Subject: Re: ports/emulators/linux_base on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2004 19:33:11 -0000 --Boundary-00=_gNG0BOrY9Rv3wKf Content-Type: text/plain; charset="euc-kr" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Wednesday 15 December 2004 05:26 am, Ruslan Ermilov wrote: > On Tue, Dec 14, 2004 at 03:15:41PM -0800, Sean McNeil wrote: > > On Tue, 2004-12-14 at 14:13 -0800, Sean McNeil wrote: > > > On Tue, 2004-12-14 at 23:54 +0200, Ruslan Ermilov wrote: > > > > On Tue, Dec 14, 2004 at 10:34:06AM -0800, Sean McNeil wrote: > > > > [...] > > > > > > > > > rpm scripts should also be fixed. It seems like a bug in > > > > > the rpm port that no one has addressed. > > > > > > > > rpm port is not guilty -- running the postinstall script > > > > manually on amd64 returns 1, but on i386 it returns 0: > > > > > > > > Script started on Tue Dec 14 23:10:31 2004 > > > > hammer# /compat/linux/bin/sh > > > > sh-2.04# uname -srm > > > > Linux 2.4.2 amd64 > > > > sh-2.04# /usr/sbin/glibc_post_upgrade > > > > sh-2.04# echo $? > > > > 1 > > > > Script done on Tue Dec 14 23:10:53 2004 > > > > > > Yes, I just got to this point. Thanks for the confirmation. > > > I'm trying to find sources to glibc_post_upgrade to take a > > > look. > > > > Here is what I have so far.... > > > > The source looks like this: > > > > #ifdef ARCH_386 > > /* Work around rpm bug */ > > char *remove_file[] = { > > "/lib/i686/libc-" VERSION ".so", > > "/lib/i686/libm-" VERSION ".so", > > "/lib/i686/libpthread-" PVERSION ".so", > > "/lib/i686/libc.so.6", > > "/lib/i686/libm.so.6", > > "/lib/i686/libpthread.so.0", > > NULL }; > > int i; > > > > for (i = 0; remove_file[i]; i++) > > unlink (remove_file[i]); > > #endif > > pid = vfork (); > > if (pid == 0) { > > execl ("/sbin/ldconfig", "/sbin/ldconfig", NULL); > > _exit (1); > > } else if (pid < 0) { > > _exit (1); > > } > > if (waitpid (0, &status, 0) != pid || !WIFEXITED (status)) { > > _exit (1); > > } > > if (WEXITSTATUS (status)) > > _exit (WEXITSTATUS (status)); > > > > ktrace shows: > > > > 2018 ktrace RET ktrace 0 > > 2018 ktrace CALL > > execve(0x7fffffffee0f,0x7fffffffec60,0x7fffffffec70) > > 2018 ktrace NAMI "/compat/linux/usr/sbin/glibc_post_upgrade" > > 2018 glibc_post_upgrade RET execve 0 > > 2018 glibc_post_upgrade CALL unlink(0x8048788) > > 2018 glibc_post_upgrade NAMI > > "/compat/linux/lib/i686/libc-2.2.4.so" 2018 glibc_post_upgrade > > NAMI "/lib/i686/libc-2.2.4.so" 2018 glibc_post_upgrade RET > > unlink JUSTRETURN > > 2018 glibc_post_upgrade CALL unlink(0x80487a0) > > 2018 glibc_post_upgrade NAMI > > "/compat/linux/lib/i686/libm-2.2.4.so" 2018 glibc_post_upgrade > > NAMI "/lib/i686/libm-2.2.4.so" 2018 glibc_post_upgrade RET > > unlink JUSTRETURN > > 2018 glibc_post_upgrade CALL unlink(0x80487b8) > > 2018 glibc_post_upgrade NAMI > > "/compat/linux/lib/i686/libpthread-0.9.so" > > 2018 glibc_post_upgrade NAMI "/lib/i686/libpthread-0.9.so" > > 2018 glibc_post_upgrade RET unlink JUSTRETURN > > 2018 glibc_post_upgrade CALL unlink(0x80487d4) > > 2018 glibc_post_upgrade NAMI > > "/compat/linux/lib/i686/libc.so.6" 2018 glibc_post_upgrade NAMI > > "/lib/i686/libc.so.6" > > 2018 glibc_post_upgrade RET unlink JUSTRETURN > > 2018 glibc_post_upgrade CALL unlink(0x80487e8) > > 2018 glibc_post_upgrade NAMI > > "/compat/linux/lib/i686/libm.so.6" 2018 glibc_post_upgrade NAMI > > "/lib/i686/libm.so.6" > > 2018 glibc_post_upgrade RET unlink JUSTRETURN > > 2018 glibc_post_upgrade CALL unlink(0x80487fc) > > 2018 glibc_post_upgrade NAMI > > "/compat/linux/lib/i686/libpthread.so.0" 2018 glibc_post_upgrade > > NAMI "/lib/i686/libpthread.so.0" 2018 glibc_post_upgrade RET > > unlink JUSTRETURN > > 2018 glibc_post_upgrade CALL lstat > > 2018 glibc_post_upgrade RET lstat 2019/0x7e3 > > 2018 glibc_post_upgrade CALL old.sendmsg(0,0xffffdb8c,0,0) > > 2018 glibc_post_upgrade RET old.sendmsg 2019/0x7e3 > > 2018 glibc_post_upgrade CALL exit(0x1) > > > > Looks like there is a mismatch in kernel entry points here. > > > > lstat instead of vfork and old.sendmsg instead of (maybe) > > waitpid. > > > > Does ktrace work with linux abi? > > On i386 it looks identical, except that sendmsg doesn't result in > exit(0x1): > > 20167 ktrace RET ktrace 0 > 20167 ktrace CALL execve(0xbfbfec77,0xbfbfeb60,0xbfbfeb68) > 20167 ktrace NAMI "/compat/linux/usr/sbin/glibc_post_upgrade" > 20167 glibc_post_upgrade RET execve 0 > 20167 glibc_post_upgrade CALL unlink(0x8048788) > 20167 glibc_post_upgrade NAMI > "/compat/linux/lib/i686/libc-2.2.4.so" 20167 glibc_post_upgrade > NAMI "/lib/i686/libc-2.2.4.so" > 20167 glibc_post_upgrade RET unlink JUSTRETURN > 20167 glibc_post_upgrade CALL unlink(0x80487a0) > 20167 glibc_post_upgrade NAMI > "/compat/linux/lib/i686/libm-2.2.4.so" 20167 glibc_post_upgrade > NAMI "/lib/i686/libm-2.2.4.so" > 20167 glibc_post_upgrade RET unlink JUSTRETURN > 20167 glibc_post_upgrade CALL unlink(0x80487b8) > 20167 glibc_post_upgrade NAMI > "/compat/linux/lib/i686/libpthread-0.9.so" 20167 glibc_post_upgrade > NAMI "/lib/i686/libpthread-0.9.so" 20167 glibc_post_upgrade RET > unlink JUSTRETURN > 20167 glibc_post_upgrade CALL unlink(0x80487d4) > 20167 glibc_post_upgrade NAMI "/compat/linux/lib/i686/libc.so.6" > 20167 glibc_post_upgrade NAMI "/lib/i686/libc.so.6" > 20167 glibc_post_upgrade RET unlink JUSTRETURN > 20167 glibc_post_upgrade CALL unlink(0x80487e8) > 20167 glibc_post_upgrade NAMI "/compat/linux/lib/i686/libm.so.6" > 20167 glibc_post_upgrade NAMI "/lib/i686/libm.so.6" > 20167 glibc_post_upgrade RET unlink JUSTRETURN > 20167 glibc_post_upgrade CALL unlink(0x80487fc) > 20167 glibc_post_upgrade NAMI > "/compat/linux/lib/i686/libpthread.so.0" 20167 glibc_post_upgrade > NAMI "/lib/i686/libpthread.so.0" 20167 glibc_post_upgrade RET > unlink JUSTRETURN > 20167 glibc_post_upgrade CALL lstat > 20167 glibc_post_upgrade RET lstat 20168/0x4ec8 > 20167 glibc_post_upgrade CALL old.sendmsg(0,0xbfbfea1c,0,0) > 20167 glibc_post_upgrade RET old.sendmsg 20168/0x4ec8 > 20167 glibc_post_upgrade CALL accept(0x8048880,0) > 20167 glibc_post_upgrade NAMI > "/compat/linux/usr/lib/gconv/gconv-modules.cache" 20167 > glibc_post_upgrade NAMI "/compat/linux" > 20167 glibc_post_upgrade NAMI > "/compat/linux/usr/lib/gconv/gconv-modules.cache" 20167 > glibc_post_upgrade RET accept 0 > 20167 glibc_post_upgrade CALL lstat > 20167 glibc_post_upgrade RET lstat 20171/0x4ecb > 20167 glibc_post_upgrade CALL old.sendmsg(0,0xbfbfea1c,0,0) > 20167 glibc_post_upgrade RET old.sendmsg 20171/0x4ecb > 20167 glibc_post_upgrade CALL access(0x804883b,0x1) > 20167 glibc_post_upgrade NAMI "/compat/linux/sbin/telinit" > 20167 glibc_post_upgrade NAMI "/sbin/telinit" > 20167 glibc_post_upgrade RET access JUSTRETURN > 20167 glibc_post_upgrade CALL exit(0) > > The reason for this is as follows: > > hammer# grep -C3 TJR /sys/compat/linux/linux_socket.c > struct iovec *iov; > int error; > > /* XXXTJR sendmsg is broken on amd64 */ > > error = copyin(args, &linux_args, sizeof(linux_args)); > if (error) > -- > struct cmsghdr *cmsg; > int error; > > /* XXXTJR recvmsg is broken on amd64 */ > > if ((error = copyin(args, &linux_args, > sizeof(linux_args)))) return (error); I thought sendmsg was the culprit too but it wasn't. You guys forgot '-i' option for krace (to trace children). The problem is in linux_execve() from src/sys/amd64/linux32/linux32_machdep.c. 888 glibc_post_upgrade RET fork 0 888 glibc_post_upgrade CALL obs_execv(0x80490ee,0xffffb644,0) 888 glibc_post_upgrade NAMI "/compat/linux/sbin/ldconfig" 888 glibc_post_upgrade NAMI "/compat/linux" 888 glibc_post_upgrade NAMI "/compat/linux/sbin/ldconfig" 888 glibc_post_upgrade RET obs_execv -1 errno -14 Unknown error: -14 888 glibc_post_upgrade CALL exit(0x6e) One of copyin/copyout is failing from linux_execve() with EFAULT. On i386, it returns 0, of course. Parent exited because child failed. Full ktrace dump and glibc_post_upgrade.c (with RedHat 8.0's local patch) attached. Thanks, Jung-uk Kim --Boundary-00=_gNG0BOrY9Rv3wKf Content-Type: text/plain; charset="euc-kr"; name="glibc_post_upgrade.c" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="glibc_post_upgrade.c" #include #include #include #include #include #include #include #include #include #include int main(void) { pid_t pid; int status; char initpath[256]; #ifdef ARCH_386 char buffer[4096]; char *remove_file[] = { "/lib/i686/libc-" VERSION ".so", "/lib/i686/libm-" VERSION ".so", "/lib/i686/librt-" VERSION ".so", "/lib/i686/libpthread-" PVERSION ".so", "/lib/i686/libc.so.6", "/lib/i686/libm.so.6", "/lib/i686/librt.so.1", "/lib/i686/libpthread.so.0", NULL }; struct pref { char *p; int len; } prefix[] = { { "libc-", 5 }, { "libm-", 5 }, { "librt-", 6 }, { "libpthread-", 11 } }; int i, fd; off_t base; ssize_t ret; for (i = 0; remove_file[i]; i++) unlink (remove_file[i]); fd = open ("/lib/i686", O_RDONLY); if (fd >= 0 && (ret = getdirentries (fd, buffer, sizeof (buffer), &base)) >= (ssize_t) offsetof (struct dirent, d_name)) { for (base = 0; base + offsetof (struct dirent, d_name) < ret; ) { struct dirent *d = (struct dirent *) (buffer + base); for (i = 0; i < sizeof (prefix) / sizeof (prefix[0]); i++) if (! strncmp (d->d_name, prefix[i].p, prefix[i].len)) { char *p = d->d_name + prefix[i].len; while (*p == '.' || (*p >= '0' && *p <= '9')) p++; if (p[0] == 's' && p[1] == 'o' && p[2] == '\0' && p + 3 - d->d_name < sizeof (initpath) - strlen ("/lib/i686/")) { strcpy (initpath, "/lib/i686/"); strcpy (initpath + strlen ("/lib/i686/"), d->d_name); unlink (initpath); break; } } base += d->d_reclen; } close (fd); } #endif pid = vfork (); if (pid == 0) { execl ("/sbin/ldconfig", "/sbin/ldconfig", NULL); _exit (110); } else if (pid < 0) _exit (111); if (waitpid (0, &status, 0) != pid || !WIFEXITED (status)) _exit (112); if (WEXITSTATUS (status)) _exit (WEXITSTATUS (status)); if (! utimes (GCONV_MODULES_CACHE, NULL)) { pid = vfork (); if (pid == 0) { execl ("/usr/sbin/iconvconfig", "/usr/sbin/iconvconfig", NULL); _exit (113); } else if (pid < 0) _exit (114); if (waitpid (0, &status, 0) != pid || !WIFEXITED (status)) _exit (115); if (WEXITSTATUS (status)) _exit (WEXITSTATUS (status)); } /* Check if telinit is available and the init fifo as well. */ if (access ("/sbin/telinit", X_OK) || access ("/dev/initctl", F_OK)) _exit (0); /* Check if we are not inside of some chroot, because we'd just timeout and leave /etc/initrunlvl. */ if (readlink ("/proc/1/exe", initpath, 256) <= 0 || readlink ("/proc/1/root", initpath, 256) <= 0) _exit (0); pid = vfork (); if (pid == 0) { execl ("/sbin/telinit", "/sbin/telinit", "u", NULL); _exit (116); } else if (pid < 0) _exit (117); if (waitpid (0, &status, 0) != pid || !WIFEXITED (status)) _exit (118); /* Check if we can safely condrestart sshd. */ if (access ("/sbin/service", X_OK) == 0 && access ("/usr/sbin/sshd", X_OK) == 0 && access ("/bin/bash", X_OK) == 0) { pid = vfork (); if (pid == 0) { execl ("/sbin/service", "/sbin/service", "sshd", "condrestart", NULL); _exit (119); } else if (pid < 0) _exit (120); if (waitpid (0, &status, 0) != pid || !WIFEXITED (status)) _exit (121); } _exit(0); } int __libc_multiple_threads; int __libc_enable_asynccancel (void) { return 0; } void __libc_disable_asynccancel (int x) { } void __libc_csu_init (void) { } void __libc_csu_fini (void) { } pid_t __fork (void) { return -1; } char thr_buf[8192]; #ifndef __powerpc__ int __libc_start_main (int (*main) (void), int argc, char **argv, void (*init) (void), void (*fini) (void), void (*rtld_fini) (void), void * stack_end) #else struct startup_info { void *sda_base; int (*main) (int, char **, char **, void *); int (*init) (int, char **, char **, void *); void (*fini) (void); }; int __libc_start_main (int argc, char **ubp_av, char **ubp_ev, void *auxvec, void (*rtld_fini) (void), struct startup_info *stinfo, char **stack_on_entry) #endif { #if defined __ia64__ || defined __powerpc64__ register void *r13 __asm ("r13") = thr_buf + 4096; __asm ("" : : "r" (r13)); #elif defined __sparc__ register void *g6 __asm ("g6") = thr_buf + 4096; register void *g7 __asm ("g7") = thr_buf + 4096; __asm ("" : : "r" (g6), "r" (g7)); #elif defined __s390__ && !defined __s390x__ __asm ("sar %%a0,%0" : : "d" (thr_buf + 4096)); #elif defined __s390x__ __asm ("sar %%a1,%0; srlg 0,%0,32; sar %%a0,0" : : "d" (thr_buf + 4096) : "0"); #elif defined __powerpc__ && !defined __powerpc64__ register void *r2 __asm ("r2") = thr_buf + 4096; __asm ("" : : "r" (r2)); #endif main(); return 0; } --Boundary-00=_gNG0BOrY9Rv3wKf Content-Type: text/plain; charset="euc-kr"; name="linux32_dump.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="linux32_dump.txt" 887 ktrace RET ktrace 0 887 ktrace CALL execve(0x7fffffffe963,0x7fffffffe750,0x7fffffffe760) 887 ktrace NAMI "/usr/compat/linux/usr/sbin/glibc_post_upgrade" 887 glibc_post_upgrade RET execve 0 887 glibc_post_upgrade CALL unlink(0x8049008) 887 glibc_post_upgrade NAMI "/compat/linux/lib/i686/libc-2.3.2.so" 887 glibc_post_upgrade NAMI "/lib/i686/libc-2.3.2.so" 887 glibc_post_upgrade RET unlink JUSTRETURN 887 glibc_post_upgrade CALL unlink(0x8049020) 887 glibc_post_upgrade NAMI "/compat/linux/lib/i686/libm-2.3.2.so" 887 glibc_post_upgrade NAMI "/lib/i686/libm-2.3.2.so" 887 glibc_post_upgrade RET unlink JUSTRETURN 887 glibc_post_upgrade CALL unlink(0x8049038) 887 glibc_post_upgrade NAMI "/compat/linux/lib/i686/librt-2.3.2.so" 887 glibc_post_upgrade NAMI "/lib/i686/librt-2.3.2.so" 887 glibc_post_upgrade RET unlink JUSTRETURN 887 glibc_post_upgrade CALL unlink(0x8049051) 887 glibc_post_upgrade NAMI "/compat/linux/lib/i686/libpthread-0.10.so" 887 glibc_post_upgrade NAMI "/lib/i686/libpthread-0.10.so" 887 glibc_post_upgrade RET unlink JUSTRETURN 887 glibc_post_upgrade CALL unlink(0x804906e) 887 glibc_post_upgrade NAMI "/compat/linux/lib/i686/libc.so.6" 887 glibc_post_upgrade NAMI "/lib/i686/libc.so.6" 887 glibc_post_upgrade RET unlink JUSTRETURN 887 glibc_post_upgrade CALL unlink(0x8049082) 887 glibc_post_upgrade NAMI "/compat/linux/lib/i686/libm.so.6" 887 glibc_post_upgrade NAMI "/lib/i686/libm.so.6" 887 glibc_post_upgrade RET unlink JUSTRETURN 887 glibc_post_upgrade CALL unlink(0x8049096) 887 glibc_post_upgrade NAMI "/compat/linux/lib/i686/librt.so.1" 887 glibc_post_upgrade NAMI "/lib/i686/librt.so.1" 887 glibc_post_upgrade RET unlink JUSTRETURN 887 glibc_post_upgrade CALL unlink(0x80490ab) 887 glibc_post_upgrade NAMI "/compat/linux/lib/i686/libpthread.so.0" 887 glibc_post_upgrade NAMI "/lib/i686/libpthread.so.0" 887 glibc_post_upgrade RET unlink JUSTRETURN 887 glibc_post_upgrade CALL open(0x80490e4,0,0) 887 glibc_post_upgrade NAMI "/compat/linux/lib/i686" 887 glibc_post_upgrade NAMI "/lib/i686" 887 glibc_post_upgrade RET open JUSTRETURN 887 glibc_post_upgrade CALL lstat 888 glibc_post_upgrade RET fork 0 888 glibc_post_upgrade CALL obs_execv(0x80490ee,0xffffb644,0) 888 glibc_post_upgrade NAMI "/compat/linux/sbin/ldconfig" 888 glibc_post_upgrade NAMI "/compat/linux" 888 glibc_post_upgrade NAMI "/compat/linux/sbin/ldconfig" 888 glibc_post_upgrade RET obs_execv -1 errno -14 Unknown error: -14 888 glibc_post_upgrade CALL exit(0x6e) 887 glibc_post_upgrade RET lstat 888/0x378 887 glibc_post_upgrade CALL old.sendmsg(0,0xffffc68c,0,0) 887 glibc_post_upgrade RET old.sendmsg 888/0x378 887 glibc_post_upgrade CALL exit(0x6e) --Boundary-00=_gNG0BOrY9Rv3wKf-- From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 28 05:57:22 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5BF1716A4CE for ; Tue, 28 Dec 2004 05:57:22 +0000 (GMT) Received: from homer.softcoin.com (homer.softcoin.com [65.223.127.243]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3687B43D41 for ; Tue, 28 Dec 2004 05:57:22 +0000 (GMT) (envelope-from mcomb@softcoin.com) Received: from macgeek.dyndns.org ([192.168.101.222]) by homer.softcoin.com (Lotus Domino Release 6.53HF53) with ESMTP id 2004122721560397-7418 ; Mon, 27 Dec 2004 21:56:03 -0800 Received: from [192.168.101.150] (dyna-0 [192.168.101.150]) by macgeek.dyndns.org (Postfix) with ESMTP id BEB69BC5392 for ; Mon, 27 Dec 2004 21:57:20 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v619) Message-Id: <5B88EFBD-5895-11D9-9EC4-000A95CD04E4@softcoin.com> To: freebsd-amd64@freebsd.org From: mcomb@softcoin.com Date: Mon, 27 Dec 2004 21:57:29 -0800 X-Mailer: Apple Mail (2.619) X-MIMETrack: Itemize by SMTP Server on Homer/SoftCoin(Release 6.53HF53 | October 26, 2004) at 12/27/2004 09:56:04 PM,2004) at 12/27/2004 09:56:04 PM, Serialize complete at 12/27/2004 09:56:04 PM Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: amd64 and tx2000 compatibility X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 05:57:22 -0000 Hi, I just setup a shiny new AMD64 box and I'm trying to get FreeBSD 5.3 release installed on it. As it boots from the install CD it displays LOADER briefly and then immediately reboots. If I remove my RAID card (Promise tx2000) it seems to boot fine. I searched the archives, but couldn't find anything relating to this specific card. Should it be supported? Anybody have a workaround besides going to the 32bit distro? Thanks, -Mike From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 28 07:02:23 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D53B16A4CE for ; Tue, 28 Dec 2004 07:02:23 +0000 (GMT) Received: from homer.softcoin.com (homer.softcoin.com [65.223.127.243]) by mx1.FreeBSD.org (Postfix) with ESMTP id 060CD43D31 for ; Tue, 28 Dec 2004 07:02:23 +0000 (GMT) (envelope-from mcomb@softcoin.com) Received: from macgeek.dyndns.org ([192.168.101.222]) by homer.softcoin.com (Lotus Domino Release 6.53HF53) with ESMTP id 2004122723010419-7471 ; Mon, 27 Dec 2004 23:01:04 -0800 Received: from [192.168.101.150] (dyna-0 [192.168.101.150]) by macgeek.dyndns.org (Postfix) with ESMTP id 488D7BC5392 for ; Mon, 27 Dec 2004 23:02:21 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <5B88EFBD-5895-11D9-9EC4-000A95CD04E4@softcoin.com> References: <5B88EFBD-5895-11D9-9EC4-000A95CD04E4@softcoin.com> Message-Id: <70A41EEA-589E-11D9-9EC4-000A95CD04E4@softcoin.com> From: mcomb@softcoin.com Date: Mon, 27 Dec 2004 23:02:30 -0800 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.619) X-MIMETrack: Itemize by SMTP Server on Homer/SoftCoin(Release 6.53HF53 | October 26, 2004) at 12/27/2004 11:01:04 PM,2004) at 12/27/2004 11:01:05 PM, Serialize complete at 12/27/2004 11:01:05 PM Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: Re: amd64 and tx2000 compatibility X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 07:02:23 -0000 Apologies for replying to my own thread. The tx2000 seems to work fine if I just use it as an IDE adapter, but as soon as I stripe or span the drives attached to it and reboot I get the crashing behavior described below. If anybody has tips for getting this working I'd really appreciate it. I've already made sure the RAID controller bios (and motherboard bios) is up to date. As a fallback I am wondering if built-in RAID on my motherboard (ABIT AV8 3rd Eye) is supported? It is SATA and I don't have any SATA drives to try it with, but I could probably dig up some adapters if it would get this working. Also, for what it is worth, this same controller and drives worked great on a different 32 bit FreeBSD system for the last year. -Mike On Dec 27, 2004, at 9:57 PM, mcomb@softcoin.com wrote: > Hi, I just setup a shiny new AMD64 box and I'm trying to get FreeBSD > 5.3 release installed on it. As it boots from the install CD it > displays LOADER briefly and then immediately reboots. If I remove my > RAID card (Promise tx2000) it seems to boot fine. I searched the > archives, but couldn't find anything relating to this specific card. > Should it be supported? Anybody have a workaround besides going to > the 32bit distro? > > Thanks, > -Mike > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to > "freebsd-amd64-unsubscribe@freebsd.org" > > From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 28 16:23:57 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D71A216A4CE; Tue, 28 Dec 2004 16:23:57 +0000 (GMT) Received: from phoenix.gargantuan.com (phoenix.gargantuan.com [24.73.171.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3590D43D31; Tue, 28 Dec 2004 16:23:57 +0000 (GMT) (envelope-from michael@gargantuan.com) Received: from localhost (localhost.gargantuan.com [127.0.0.1]) by spamassassin-injector (Postfix) with SMTP id 608495ED; Tue, 28 Dec 2004 11:23:56 -0500 (EST) Received: by phoenix.gargantuan.com (Postfix, from userid 1001) id 3EC1B3AB; Tue, 28 Dec 2004 11:23:38 -0500 (EST) Date: Tue, 28 Dec 2004 11:23:38 -0500 From: "Michael W. Oliver" To: freebsd-amd64@freebsd.org Message-ID: <20041228162338.GA51840@gargantuan.com> References: <20041220152647.GA31796@gargantuan.com> <20041223163929.GA52351@gargantuan.com> <20041227013118.GA76674@gargantuan.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK" Content-Disposition: inline In-Reply-To: <20041227013118.GA76674@gargantuan.com> X-WWW-Site: http://michael.gargantuan.com X-PGP-Public-Key: $X-WWW-Site/gnupg/pubkey.asc X-PGP-Fingerprint: 2694 0179 AE3F BFAE 0916 0BF5 B16B FBAB C5FA A3C9 X-Home-Phone: +1-863-816-8091 X-Mobile-Phone: +1-863-738-2334 X-Home-Address0: 8008 Apache Lane X-Home-Address1: Lakeland, FL X-Home-Address2: 33810-2172 X-Home-Address3: United States of America X-Good-Question-Guide: http://www.catb.org/~esr/faqs/smart-questions.html X-Netiquette-Guidelines: http://www.ietf.org/rfc/rfc1855.txt User-Agent: Mutt/1.5.6i X-Spam-DCC: dcc3mcgill: phoenix.gargantuan.com 1275; Body=1 Fuz1=1 Fuz2=1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on phoenix.gargantuan.com X-Spam-Level: X-Spam-Status: No, score=-105.6 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, USER_IN_WHITELIST autolearn=ham version=3.0.1 X-Spam-Pyzor: Reported 0 times. cc: simokawa@freebsd.org Subject: Re: fwohci init on 5.3-RELEASE blowing up X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 16:23:58 -0000 --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004-12-26T20:31:18-0500, Michael W. Oliver wrote: > On 2004-12-23T11:39:29-0500, Michael W. Oliver wrote: > > On 2004-12-20T10:26:47-0500, Michael W. Oliver wrote: SOLVED! I had received suggestions to use hints to disable firewire, but that didn't help. Even when I set the hint, the controller was still probed and caused a panic. So, no joy there. However, I finally did get a custom release rolled! This may not sound like a big deal to you hardcore developers, but it is huge for me, and I have learned a LOT. The cross-build actually only worked for me when the build machine was running the same release that I was trying to build, which was 5.3-RELEASE. So, I applied the patch in kern/75482 to my src and built the release successfully. That's the good news. Now for the bad news. Once I tried the new release CD, it got past the fwohci probe (success!), but died at the cardbus controller. cbb0: at device 12.0 on pci0 This was with ACPI enabled. I disabled ACPI and that kept the machine =66rom panic()ing on cbb, and I was actually able to get FreeBSD 5.3-RELEASE installed on the disk from my custom ISO. Once installed, I cvsup'd the src for RELENG_5 and rebuilt world, but still had issues with cbb while ACPI was enabled. Time to step it up a notch. I cvsup'd to HEAD and the ACPI+cbb panic is now gone, and almost everything on this machine is running now. There are some errors in the acpidump that I need to work out (custom DSDT), and the Atheros card won't work (ath_hal in my kernel blows up, and it is a 5213 so it might not work anyway :/), but otherwise it is running great! Thanks to Astrodog and Roland Smith for their suggestions and support. While their suggestions didn't actually solve the problem, they pushed my mind in the right direction, which made me learn. Thanks guys. The page doesn't exist yet, but I am going to start a diary for this laptop at http://michael.gargantuan.com/sager_4750v.htm Real Soon Now. --=20 Michael W. Oliver [see complete headers for contact information] --YZ5djTAD1cGYuMQK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB0YiKsWv7q8X6o8kRAry9AKCqT3XIUpgbg78ZvwkvBpgFx3IaSgCgribz gElZnR7PFWK3wKx/jifXIy0= =Ifdk -----END PGP SIGNATURE----- --YZ5djTAD1cGYuMQK-- From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 28 17:18:25 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 397CB16A4CE for ; Tue, 28 Dec 2004 17:18:25 +0000 (GMT) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9819043D54 for ; Tue, 28 Dec 2004 17:18:24 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87])iBSHINA6005255; Wed, 29 Dec 2004 04:18:23 +1100 Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) iBSHIHIm006726; Wed, 29 Dec 2004 04:18:18 +1100 Date: Wed, 29 Dec 2004 04:18:17 +1100 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: John-Mark Gurney In-Reply-To: <20041223202302.GG19624@funkthat.com> Message-ID: <20041229032725.P90388@delplex.bde.org> References: <1103830283.53421.3.camel@server.mcneil.com> <20041223202302.GG19624@funkthat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: amd64@freebsd.org Subject: Re: what is the proper asm spec for xchg X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 17:18:25 -0000 On Thu, 23 Dec 2004, John-Mark Gurney wrote: > Sean McNeil wrote this message on Thu, Dec 23, 2004 at 11:31 -0800: > > I'm looking at why audio/sdl_mixer will not compile and I see that > > devel/sdl12 has an include with > > > > #elif defined(__GNUC__) && defined(__x86_64__) > > static __inline__ Uint16 SDL_Swap16(Uint16 x) > > { > > __asm__("xchgb %b0,%h0" : "=q" (x) : "0" (x)); > > return x; > > } > > > > This appears to be incorrect as it is giving errors when compiled. Does > > anyone more conversant with asm directives for amd64 have an idea what > > this should be? > > well, from amd64/include/endian.h: > #define __byte_swap_word_var(x) \ > __extension__ ({ register __uint16_t __X = (x); \ > __asm ("xchgb %h0, %b0" : "+Q" (__X)); \ ^ actually q > __X; }) The critical difference is that the "q" constraint gives all general registers on amd64's, but "%h" (to give the second lowest 8-bit subregister) only works for the a, b, c and d registers. The "Q" constraint must be used to restrict to the latter. This difference from i386's is because gcc defines "q" registers to be ones whose lowest 8 bits can be addressed directly and amd64's support this for all general registers. The unimportant differences are: (1) The working version uses the "+" constraint where the broken version uses the "=" and "0" constraints. "0" is just old-fashioned and harder to use here. It was needed for general operands before "+" existed, and caused problems depending on optimization and register pressure. Now it is only supported for register operands, but the above only uses register operands so "0" should work. (2) The operand orders are are reversed. This makes no difference to the result because the operand order doesn't matter for exchanges. Bruce From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 28 18:49:29 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFBA116A4CE for ; Tue, 28 Dec 2004 18:49:29 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62E6E43D1F for ; Tue, 28 Dec 2004 18:49:29 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iBSInQcH070282; Tue, 28 Dec 2004 10:49:26 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iBSInQJ6070281; Tue, 28 Dec 2004 10:49:26 -0800 (PST) (envelope-from obrien) Date: Tue, 28 Dec 2004 10:49:26 -0800 From: "David O'Brien" To: Brian Myers Message-ID: <20041228184926.GA69940@dragon.nuxi.com> References: <5B1511FA-5540-11D9-AF1F-000A95B96642@charter.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5B1511FA-5540-11D9-AF1F-000A95B96642@charter.net> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: New board for a newbie X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 18:49:30 -0000 On Thu, Dec 23, 2004 at 04:11:27PM -0800, Brian Myers wrote: > 2) I've seen much conversation on which boards, memory, and SATA > controllers were supported by FreeBSD. So much so that I have no idea > what the current state of things is. So, if you were building a new > dual Opteron from scratch, what would you get? For cost reasons, I'm > going with 1.8 ghz processors and probably only 2GB of ram. I'll have > two RAID 1 SATA hard drives, but should I use an onboard controller, or > purchase a separate controller? Note that I may at some point upgrade > to 4 RAID 0+1 disks. What about video cards? I don't need much so, are > the onboard ones useable or not? Also, I, of course, would like the > onboard LAN controller to be supported. You really don't mention the use of the machine -- server or workstation (or mix)? Do you need an AGP slot for high-end graphics, or is low-end on-board VGA just fine? How many 64-bit PCI-X slots do you need? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 28 19:04:13 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B5F516A4CE; Tue, 28 Dec 2004 19:04:13 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2335B43D5E; Tue, 28 Dec 2004 19:04:13 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iBSJ4CBA070813; Tue, 28 Dec 2004 11:04:12 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iBSJ4BKY070812; Tue, 28 Dec 2004 11:04:11 -0800 (PST) (envelope-from obrien) Date: Tue, 28 Dec 2004 11:04:11 -0800 From: "David O'Brien" To: "Michael W. Oliver" Message-ID: <20041228190411.GB69940@dragon.nuxi.com> References: <20041220152647.GA31796@gargantuan.com> <20041223163929.GA52351@gargantuan.com> <20041227013118.GA76674@gargantuan.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041227013118.GA76674@gargantuan.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: simokawa@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: fwohci init on 5.3-RELEASE blowing up X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 19:04:13 -0000 On Sun, Dec 26, 2004 at 08:31:18PM -0500, Michael W. Oliver wrote: > On 2004-12-23T11:39:29-0500, Michael W. Oliver wrote: > > On 2004-12-20T10:26:47-0500, Michael W. Oliver wrote: > > I went to http://www.freebsd.org/releases/snapshots.html and from there > > to ftp://current.freebsd.org/pub/FreeBSD/snapshots/amd64/ but couldn't > > find anything newer than late-October. I tried to build a new 6-CURRENT snapshot a few weeks ago, but someone broke the release process. I'll see if I can actually get thru one today. > Subsequent tries: > ------------------- > This machine is a P2/400MHz running -CURRENT from about 2 weeks ago, > which means that it has the /sbin/mdconfig that was missing on the 4.9 > machine. Hooray! Unfortunately, this machine is painfully slow at > building an entire release. First build attempt failed trying to 'make > index' for ports, so I started again with 'NOPORTS=YES'. This worked > for a little while longer, then failed again with the following error: > > ------8<------------------------------- > [...] > ln /R/stage/mfsfd/stand/etc/services /R/stage/mfsfd/etc/services > ln /R/stage/mfsfd/stand/etc/group /R/stage/mfsfd/etc/group > ln /R/stage/mfsfd/stand/etc/netconfig /R/stage/mfsfd/etc/netconfig > cp /R/stage/trees/base/COPYRIGHT /R/stage/mfsfd/stand/help/COPYRIGHT.hlp > test -f /usr/src/release/install.cfg && cp /usr/src/release/install.cfg > /R/stage/mfsfd > *** Error code 1 (ignored) > sh -e /usr/src/release/scripts/doFS.sh bsdlabel amd64 /R/stage/mfsroot/mfsroot /R/stage /mnt 4096 /R/stage/mfsfd 8192 auto > + export BLOCKSIZE=512 > + DISKLABEL=bsdlabel > + shift > + MACHINE=-m amd64 It almost looks like you're trying to do a cross-build (ie, build a 64-bit release on a 32-bit machine). That isn't supported. RU often keeps it working enough to test compilation issues; but not to produce a real release. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 28 22:32:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3A2816A4CE; Tue, 28 Dec 2004 22:32:56 +0000 (GMT) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8DB643D2F; Tue, 28 Dec 2004 22:32:56 +0000 (GMT) (envelope-from peter@wemm.org) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id 9D9311979B; Tue, 28 Dec 2004 14:32:56 -0800 (PST) From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Tue, 28 Dec 2004 14:32:55 -0800 User-Agent: KMail/1.7.1 References: <1936407230.20041214120051@bk.ru> <41CC8950.90803@dellroad.org> <41CD2290.7060001@jrv.org> In-Reply-To: <41CD2290.7060001@jrv.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412281432.56309.peter@wemm.org> cc: "James R. Van Artsalen" cc: archie@freebsd.org cc: Archie Cobbs Subject: Re: mpd@amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 22:32:57 -0000 On Saturday 25 December 2004 12:19 am, James R. Van Artsalen wrote: > Archie Cobbs wrote: > > James R. Van Artsalen wrote: > >> I looked at this and it crashes starting up for me too. It > >> crashes in vprintf, within the second call to LogPrintf (), > >> apparently while logging ordinary startup messages. I don't see > >> any obvious cause at that point unfortunately. > > > > Can you try the attached patch? Someone else on the mpd-users > > mailing list had a similar problem and this helped. > > Thanks, it works now. > > Attached is a slightly different patch. This is against the source > currently in ports, and it fixes two additional questionable uses of > va_start (). Just as a BTW; powerpc platforms need this series of changes too, not just amd64. BTW2: I wonder if some of the attached changes really could be done more simply with va_copy()... Not that it matters of course. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 28 23:18:31 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 46C2916A4CE for ; Tue, 28 Dec 2004 23:18:31 +0000 (GMT) Received: from kong.rascom.ru (kong.rascom.ru [80.64.99.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCCE143D46 for ; Tue, 28 Dec 2004 23:18:29 +0000 (GMT) (envelope-from kong@rascom.ru) Received: from kong.rascom.ru (localhost [127.0.0.1]) by kong.rascom.ru (8.13.1/8.12.9) with ESMTP id iBSNIRxD051698 for ; Wed, 29 Dec 2004 02:18:27 +0300 (MSK) (envelope-from kong@rascom.ru) Received: from localhost (kong@localhost) by kong.rascom.ru (8.13.1/8.12.10/Submit) with ESMTP id iBSNIRJx051695 for ; Wed, 29 Dec 2004 02:18:27 +0300 (MSK) (envelope-from kong@rascom.ru) X-Authentication-Warning: kong.rascom.ru: kong owned process doing -bs Date: Wed, 29 Dec 2004 02:17:19 +0300 (MSK) From: Hostas Red X-X-Sender: kong@kong.rascom.ru To: Don Bowman In-Reply-To: <2BCEB9A37A4D354AA276774EE13FB8C219AE66@mailserver.sandvine.com> Message-ID: <20041229021224.E51667@kong.rascom.ru> References: <2BCEB9A37A4D354AA276774EE13FB8C219AE66@mailserver.sandvine.com> X-NCC-RegId: ru.rascom MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed ReSent-Date: Wed, 29 Dec 2004 02:18:24 +0300 (MSK) Resent-From: Hostas Red Resent-To: freebsd-amd64@freebsd.org ReSent-Subject: RE: aac controller in amd64 very slow? ReSent-Message-ID: <20041229021824.Q51667@kong.rascom.ru> Subject: RE: aac controller in amd64 very slow? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 23:18:31 -0000 Hi! On Tue, 28 Dec 2004, Don Bowman wrote: > well, on the aac, you need to disable the read-cache otherwise it has > very very poor performance. > I think this can be done from scsi bios. it can also be done via aaccli. As far as I can see from the tests the read speed is not a problem - it's a write operations that are VERY slow. Anyway, I've disabled a read-cache via aaccli - no effect. Or I need to reset a box to apply aac configuration changes? And one more - controller has no battery connected, but have an enabled write-cache: AAC0> container show cache 0 Executing: container show cache 0 Global Container Read Cache Size : 0 Global Container Write Cache Size : 16203776 Read Cache Setting : DISABLE Write Cache Setting : ENABLE ALWAYS Write Cache Status : Active, not protected, battery not present And that's my contaier config: AAC0> container list Executing: container list Num Total Oth Stripe Scsi Partition Label Type Size Ctr Size Usage C:ID:L Offset:Size ----- ------ ------ --- ------ ------- ------ ------------- 0 RAID-5 410GB 64KB Open 0:00:0 64.0KB: 136GB /dev/aacd0 raid 5 0:01:0 64.0KB: 136GB 0:02:0 64.0KB: 136GB 0:03:0 64.0KB: 136GB >> -----Original Message----- >> From: owner-freebsd-amd64@freebsd.org >> [mailto:owner-freebsd-amd64@freebsd.org] On Behalf Of Hostas Red >> Sent: December 27, 2004 9:02 AM >> To: freebsd-amd64@freebsd.org >> Subject: aac controller in amd64 very slow? >> >> Hi! >> >> 1) I have one Quad Opteron box with FreeBSD 5.3-amd64 >> installed and have strange downgrade in performance with >> Adaptec 2120S raid controller (acc driver, 4-disk RAID5 >> configured). It is approx. 30-40% loss in performance of disk >> operations compared to my previous Dual 2.4 Xeon with Adaptec >> 2015S with two disks mirrored. >> >> Is it normal or maybe I need some tweaking? Also one of my >> colleagues suggested installation of i386 version of 5.3 for >> speeding things up, that sound strange for me. >> >> I'm new for amd64 version of freebsd, but using freebsd-i386 >> for 7 years or so on i386 platforms. May this problem be an >> amd64-specific? >> >> Any suggestions how I can resolve this problem? >> >> >> >> 2) One more Q - apache is eating a lot of memory when running >> - about 64M for each process instead of usual approx 7-10M >> per process on previous >> i386 with same compiled configuration: >> >> == from top === >> PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU >> CPU COMMAND >> 3351 www 96 0 69560K 18712K select 3 0:01 0.93% >> 0.93% httpd >> ========== >> >> Other programs looks the same or about it. Is it normal for >> amd64 platform or also my mistake? >> >> >> >> 3) And one more Q - box has 4G of memory, but kernel can see >> only 3.5G, as >> can be seen from following dmesg output. What can be a problem? >> >> >> >> Box is a Tyan's Thunder K8QS Pro (S4882) 4-way AMD Opteron >> platform (with >> Tyan S4882UG2NR board). >> >> Disk split in two parts: >> >> Filesystem 1K-blocks Used Avail Capacity Mounted on >> /dev/aacd0s1a 6090094 1998300 3604588 36% / >> devfs 1 1 0 100% /dev >> /dev/aacd0s1d 402268316 26148124 343938728 7% /work >> >> On /, of course, is a system and second one is working partiton. >> >> Here's boot message of the new box: >> >> Copyright (c) 1992-2004 The FreeBSD Project. >> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, >> 1993, 1994 >> The Regents of the University of California. All >> rights reserved. >> FreeBSD 5.3-STABLE #2: Mon Dec 27 08:27:05 GMT 2004 >> root@sys154.3fn.net:/usr/obj/usr/src/sys/kong >> Timecounter "i8254" frequency 1193182 Hz quality 0 >> CPU: AMD Opteron(tm) Processor 846 (1992.22-MHz K8-class CPU) >> Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 >> >> Features=0x78bfbff ,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> >> AMD Features=0xe0500800 >> real memory = 3757506560 (3583 MB) >> avail memory = 3627720704 (3459 MB) >> ACPI APIC Table: >> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs >> cpu0 (BSP): APIC ID: 0 >> cpu1 (AP): APIC ID: 1 >> cpu2 (AP): APIC ID: 2 >> cpu3 (AP): APIC ID: 3 >> MADT: Forcing active-low polarity and level trigger for SCI >> ioapic0 irqs 0-23 on motherboard >> ioapic1 irqs 24-27 on motherboard >> ioapic2 irqs 28-31 on motherboard >> ioapic3 irqs 32-35 on motherboard >> ioapic4 irqs 36-39 on motherboard >> acpi0: on motherboard >> acpi0: Power Button (fixed) >> unknown: I/O range not supported >> unknown: I/O range not supported >> Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 >> acpi_timer0: <24-bit timer at 3.579545MHz> port 0xc008-0xc00b on acpi0 >> cpu0: on acpi0 >> cpu1: on acpi0 >> cpu2: on acpi0 >> cpu3: on acpi0 >> acpi_button0: on acpi0 >> pcib0: port >> 0xc080-0xc0ff,0xc000-0xc07f,0xcf8-0xcff iomem 0xd8000-0xdbfff on acpi0 >> pci0: on pcib0 >> pcib1: at device 6.0 on pci0 >> pci1: on pcib1 >> ohci0: mem >> 0xe8000000-0xe8000fff irq 19 at device 0.0 on pci1 >> ohci0: [GIANT-LOCKED] >> usb0: OHCI version 1.0, legacy support >> usb0: SMM does not respond, resetting >> usb0: on ohci0 >> usb0: USB revision 1.0 >> uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >> uhub0: 3 ports with 3 removable, self powered >> ohci1: mem >> 0xe8001000-0xe8001fff irq 19 at device 0.1 on pci1 >> ohci1: [GIANT-LOCKED] >> usb1: OHCI version 1.0, legacy support >> usb1: SMM does not respond, resetting >> usb1: on ohci1 >> usb1: USB revision 1.0 >> uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >> uhub1: 3 ports with 3 removable, self powered >> pci1: at device 4.0 (no driver attached) >> isab0: at device 7.0 on pci0 >> isa0: on isab0 >> atapci0: port >> 0x1000-0x100f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device >> 7.1 on pci0 >> ata0: channel #0 on atapci0 >> ata1: channel #1 on atapci0 >> pci0: at device 7.3 (no driver attached) >> pcib2: on acpi0 >> pci8: on pcib2 >> pcib3: at device 1.0 on pci8 >> pci9: on pcib3 >> aac0: mem 0xf8000000-0xfbffffff irq >> 26 at device 2.0 on pci9 >> aac0: [FAST] >> aac0: Enabling 64-bit address support >> aac0: Unknown processor 100MHz, 48MB cache memory, optional >> battery not installed >> aac0: Kernel 4.1-0, Build 7244, S/N be37b0 >> aac0: Supported >> Options=11d7e> ,SOFTERR,SGMAP64,ALARM,NONDASD> >> aacp0: on aac0 >> pci8: at device 1.1 >> (no driver attached) >> pcib4: at device 2.0 on pci8 >> pci14: on pcib4 >> mpt0: port 0x3000-0x30ff mem >> 0xed000000-0xed00ffff,0xed010000-0xed01ffff irq 29 at device >> 1.0 on pci14 >> mpt0: [GIANT-LOCKED] >> mpt1: port 0x3400-0x34ff mem >> 0xed020000-0xed02ffff,0xed030000-0xed03ffff irq 30 at device >> 1.1 on pci14 >> mpt1: [GIANT-LOCKED] >> bge0: > 0x2002> mem 0xed040000-0xed04ffff,0xed050000-0xed05ffff irq >> 31 at device 3.0 on pci14 >> miibus0: on bge0 >> brgphy0: on miibus0 >> brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, >> 1000baseTX, 1000baseTX-FDX, auto >> bge0: Ethernet address: 00:00:1a:1a:0d:5a >> bge1: > 0x2002> mem 0xed060000-0xed06ffff,0xed070000-0xed07ffff irq >> 28 at device 3.1 on pci14 >> miibus1: on bge1 >> brgphy1: on miibus1 >> brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, >> 1000baseTX, 1000baseTX-FDX, auto >> bge1: Ethernet address: 00:00:1a:1a:0d:5b >> pci8: at device 2.1 >> (no driver attached) >> pcib5: mem 0xea202000-0xea202fff irq 32 >> at device 3.0 on pci8 >> pci19: on pcib5 >> pci8: at device 3.1 >> (no driver attached) >> pcib6: mem 0xea204000-0xea204fff irq 36 >> at device 4.0 on pci8 >> pci27: on pcib6 >> pci8: at device 4.1 >> (no driver attached) >> atkbdc0: port 0x64,0x60 irq 1 on acpi0 >> sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 >> flags 0x10 on acpi0 >> sio0: type 16550A, console >> fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 >> drq 2 on acpi0 >> fdc0: [FAST] >> fd0: <1440-KB 3.5" drive> on fdc0 drive 0 >> orm0: at iomem >> 0xcc800-0xd0fff,0xcb000-0xcc7ff,0xc9800-0xcafff,0xc9000-0xc97f >> f,0xc8000-0xc8fff,0xc0000-0xc7fff on isa0 >> sc0: at flags 0x100 on isa0 >> sc0: VGA <16 virtual consoles, flags=0x100> >> sio1: configured irq 3 not in bitmap of probed irqs 0 >> sio1: port may not be enabled >> vga0: at port 0x3c0-0x3df iomem >> 0xa0000-0xbffff on isa0 >> Timecounters tick every 1.000 msec >> ipfw2 initialized, divert disabled, rule-based forwarding >> disabled, default to accept, logging disabled >> acd0: DVDROM at ata0-master UDMA33 >> Waiting 15 seconds for SCSI devices to settle >> aacd0: on aac0 >> aacd0: 419943MB (860045184 sectors) >> (probe0:aacp0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0 >> (probe0:aacp0:0:0:0): ILLEGAL REQUEST asc:55,3 >> (probe0:aacp0:0:0:0): Reserved ASC/ASCQ pair >> (probe5:aacp0:0:5:0): INQUIRY. CDB: 12 0 0 0 24 0 >> (probe5:aacp0:0:5:0): ILLEGAL REQUEST asc:55,3 >> (probe5:aacp0:0:5:0): Reserved ASC/ASCQ pair >> (probe9:aacp0:0:10:0): INQUIRY. CDB: 12 0 0 0 24 0 >> (probe9:aacp0:0:10:0): ILLEGAL REQUEST asc:55,3 >> (probe9:aacp0:0:10:0): Reserved ASC/ASCQ pair >> (probe10:aacp0:0:11:0): INQUIRY. CDB: 12 0 0 0 24 0 >> (probe10:aacp0:0:11:0): ILLEGAL REQUEST asc:55,3 >> (probe10:aacp0:0:11:0): Reserved ASC/ASCQ pair >> (probe13:aacp0:0:14:0): INQUIRY. CDB: 12 0 0 0 24 0 >> (probe13:aacp0:0:14:0): ILLEGAL REQUEST asc:55,3 >> (probe13:aacp0:0:14:0): Reserved ASC/ASCQ pair >> (probe1:aacp0:0:1:0): INQUIRY. CDB: 12 0 0 0 24 0 >> (probe1:aacp0:0:1:0): ILLEGAL REQUEST asc:55,3 >> (probe1:aacp0:0:1:0): Reserved ASC/ASCQ pair >> (probe2:aacp0:0:2:0): INQUIRY. CDB: 12 0 0 0 24 0 >> (probe2:aacp0:0:2:0): ILLEGAL REQUEST asc:55,3 >> (probe2:aacp0:0:2:0): Reserved ASC/ASCQ pair >> (probe3:aacp0:0:3:0): INQUIRY. CDB: 12 0 0 0 24 0 >> (probe3:aacp0:0:3:0): ILLEGAL REQUEST asc:55,3 >> (probe3:aacp0:0:3:0): Reserved ASC/ASCQ pair >> (probe4:aacp0:0:4:0): INQUIRY. CDB: 12 0 0 0 24 0 >> (probe4:aacp0:0:4:0): ILLEGAL REQUEST asc:55,3 >> (probe4:aacp0:0:4:0): Reserved ASC/ASCQ pair >> (probe6:aacp0:0:6:0): INQUIRY. CDB: 12 0 0 0 24 0 >> (probe6:aacp0:0:6:0): ILLEGAL REQUEST asc:55,3 >> (probe6:aacp0:0:6:0): Reserved ASC/ASCQ pair >> (probe7:aacp0:0:8:0): INQUIRY. CDB: 12 0 0 0 24 0 >> (probe7:aacp0:0:8:0): ILLEGAL REQUEST asc:55,3 >> (probe7:aacp0:0:8:0): Reserved ASC/ASCQ pair >> (probe8:aacp0:0:9:0): INQUIRY. CDB: 12 0 0 0 24 0 >> (probe8:aacp0:0:9:0): ILLEGAL REQUEST asc:55,3 >> (probe8:aacp0:0:9:0): Reserved ASC/ASCQ pair >> (probe11:aacp0:0:12:0): INQUIRY. CDB: 12 0 0 0 24 0 >> (probe11:aacp0:0:12:0): ILLEGAL REQUEST asc:55,3 >> (probe11:aacp0:0:12:0): Reserved ASC/ASCQ pair >> (probe12:aacp0:0:13:0): INQUIRY. CDB: 12 0 0 0 24 0 >> (probe12:aacp0:0:13:0): ILLEGAL REQUEST asc:55,3 >> (probe12:aacp0:0:13:0): Reserved ASC/ASCQ pair >> (probe14:aacp0:0:15:0): INQUIRY. CDB: 12 0 0 0 24 0 >> (probe14:aacp0:0:15:0): ILLEGAL REQUEST asc:55,3 >> (probe14:aacp0:0:15:0): Reserved ASC/ASCQ pair >> SMP: AP CPU #2 Launched! >> SMP: AP CPU #1 Launched! >> SMP: AP CPU #3 Launched! >> Mounting root from ufs:/dev/aacd0s1a >> >> Thank You. >> >> adios, >> /kong >> >> ============================================================== >> ========== >> Hostas Red (KVK10, KVK10-RIPE) || IP Networks Administrator, >> CJSC Rascom >> ============================================================== >> ========== >> _______________________________________________ >> freebsd-amd64@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 >> To unsubscribe, send any mail to >> "freebsd-amd64-unsubscribe@freebsd.org" >> >> > adios, /kong ======================================================================== Hostas Red (KVK10, KVK10-RIPE) || IP Networks Administrator, CJSC Rascom ======================================================================== From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 28 23:26:06 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7451616A4CE for ; Tue, 28 Dec 2004 23:26:06 +0000 (GMT) Received: from kong.rascom.ru (kong.rascom.ru [80.64.99.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35E6843D46 for ; Tue, 28 Dec 2004 23:26:05 +0000 (GMT) (envelope-from kong@kong.spb.ru) Received: from kong.rascom.ru (localhost [127.0.0.1]) by kong.rascom.ru (8.13.1/8.12.9) with ESMTP id iBSNQ4JF051756; Wed, 29 Dec 2004 02:26:04 +0300 (MSK) (envelope-from kong@kong.spb.ru) Received: from localhost (kong@localhost)iBSNQ46I051753; Wed, 29 Dec 2004 02:26:04 +0300 (MSK) (envelope-from kong@kong.spb.ru) X-Authentication-Warning: kong.rascom.ru: kong owned process doing -bs Date: Wed, 29 Dec 2004 02:26:04 +0300 (MSK) From: Hostas Red X-X-Sender: kong@kong.rascom.ru To: Don Bowman In-Reply-To: <2BCEB9A37A4D354AA276774EE13FB8C219AE70@mailserver.sandvine.com> Message-ID: <20041229022335.R51667@kong.rascom.ru> References: <2BCEB9A37A4D354AA276774EE13FB8C219AE70@mailserver.sandvine.com> X-NCC-RegId: ru.rascom MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-amd64@freebsd.org Subject: RE: aac controller in amd64 very slow? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 23:26:06 -0000 Hi! On Tue, 28 Dec 2004, Don Bowman wrote: > yeah, having the read cache on wrecks the write speed. > Something to do with having it write and then read it back into the > cache. Thanks, I'll try to reset system after container reconfiguration. Hope this helps. Without reboot I cannot see any difference. > This made a dramatic difference for me. I'm a dual Xeon, 5.3 Maybe this is the point. On i386/Dual Xeon I have no problems with raid5 controller speed... > CLI > open aac0 > Executing: open "aac0" > > AAC0> container show cache 0 > Executing: container show cache 0 > > Global Container Read Cache Size : 475136 > Global Container Write Cache Size : 40140800 > > Read Cache Setting : DISABLE > Write Cache Setting : ENABLE ALWAYS > Write Cache Status : Active, not protected, battery not present > > AAC0> container list > Executing: container list > Num Total Oth Stripe Scsi Partition > Label Type Size Ctr Size Usage C:ID:L Offset:Size > ----- ------ ------ --- ------ ------- ------ ------------- > 0 RAID-5 1.73TB 64KB Open 0:00:0 64.0KB: 136GB > /dev/aacd0 all 0:01:0 64.0KB: 136GB > 0:02:0 64.0KB: 136GB > 0:03:0 64.0KB: 136GB > 0:04:0 64.0KB: 136GB > 0:05:0 64.0KB: 136GB > 0:06:0 64.0KB: 136GB > 1:00:0 64.0KB: 136GB > 1:01:0 64.0KB: 136GB > 1:02:0 64.0KB: 136GB > 1:03:0 64.0KB: 136GB > 1:04:0 64.0KB: 136GB > 1:05:0 64.0KB: 136GB > 1:06:0 64.0KB: 136GB > > > AAC0> > > > >> -----Original Message----- >> From: Hostas Red [mailto:kong@kong.spb.ru] >> Sent: December 28, 2004 18:17 PM >> To: Don Bowman >> Subject: RE: aac controller in amd64 very slow? >> >> Hi! >> >> On Tue, 28 Dec 2004, Don Bowman wrote: >> >>> well, on the aac, you need to disable the read-cache >> otherwise it has >>> very very poor performance. >>> I think this can be done from scsi bios. it can also be >> done via aaccli. >> >> As far as I can see from the tests the read speed is not a >> problem - it's a write operations that are VERY slow. Anyway, >> I've disabled a read-cache via aaccli - no effect. Or I need >> to reset a box to apply aac configuration changes? And one >> more - controller has no battery connected, but have an >> enabled write-cache: >> >> AAC0> container show cache 0 >> Executing: container show cache 0 >> >> Global Container Read Cache Size : 0 >> Global Container Write Cache Size : 16203776 >> >> Read Cache Setting : DISABLE >> Write Cache Setting : ENABLE ALWAYS >> Write Cache Status : Active, not protected, battery not present >> >> And that's my contaier config: >> >> AAC0> container list >> Executing: container list >> Num Total Oth Stripe Scsi Partition >> Label Type Size Ctr Size Usage C:ID:L Offset:Size >> ----- ------ ------ --- ------ ------- ------ ------------- >> 0 RAID-5 410GB 64KB Open 0:00:0 64.0KB: 136GB >> /dev/aacd0 raid 5 0:01:0 64.0KB: 136GB >> 0:02:0 64.0KB: 136GB >> 0:03:0 64.0KB: 136GB >> >>>> -----Original Message----- >>>> From: owner-freebsd-amd64@freebsd.org >>>> [mailto:owner-freebsd-amd64@freebsd.org] On Behalf Of Hostas Red >>>> Sent: December 27, 2004 9:02 AM >>>> To: freebsd-amd64@freebsd.org >>>> Subject: aac controller in amd64 very slow? >>>> >>>> Hi! >>>> >>>> 1) I have one Quad Opteron box with FreeBSD 5.3-amd64 >> installed and >>>> have strange downgrade in performance with Adaptec 2120S raid >>>> controller (acc driver, 4-disk RAID5 configured). It is approx. >>>> 30-40% loss in performance of disk operations compared to >> my previous >>>> Dual 2.4 Xeon with Adaptec 2015S with two disks mirrored. >>>> >>>> Is it normal or maybe I need some tweaking? Also one of my >> colleagues >>>> suggested installation of i386 version of 5.3 for speeding >> things up, >>>> that sound strange for me. >>>> >>>> I'm new for amd64 version of freebsd, but using freebsd-i386 for 7 >>>> years or so on i386 platforms. May this problem be an >> amd64-specific? >>>> >>>> Any suggestions how I can resolve this problem? >>>> >>>> >>>> >>>> 2) One more Q - apache is eating a lot of memory when running >>>> - about 64M for each process instead of usual approx 7-10M per >>>> process on previous >>>> i386 with same compiled configuration: >>>> >>>> == from top === >>>> PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU >>>> CPU COMMAND >>>> 3351 www 96 0 69560K 18712K select 3 0:01 0.93% >>>> 0.93% httpd >>>> ========== >>>> >>>> Other programs looks the same or about it. Is it normal for >>>> amd64 platform or also my mistake? >>>> >>>> >>>> >>>> 3) And one more Q - box has 4G of memory, but kernel can see only >>>> 3.5G, as can be seen from following dmesg output. What can be a >>>> problem? >>>> >>>> >>>> >>>> Box is a Tyan's Thunder K8QS Pro (S4882) 4-way AMD Opteron >> platform >>>> (with Tyan S4882UG2NR board). >>>> >>>> Disk split in two parts: >>>> >>>> Filesystem 1K-blocks Used Avail Capacity Mounted on >>>> /dev/aacd0s1a 6090094 1998300 3604588 36% / >>>> devfs 1 1 0 100% /dev >>>> /dev/aacd0s1d 402268316 26148124 343938728 7% /work >>>> >>>> On /, of course, is a system and second one is working partiton. >>>> >>>> Here's boot message of the new box: >>>> >>>> Copyright (c) 1992-2004 The FreeBSD Project. >>>> Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, >> 1992, 1993, >>>> 1994 >>>> The Regents of the University of California. All rights >>>> reserved. >>>> FreeBSD 5.3-STABLE #2: Mon Dec 27 08:27:05 GMT 2004 >>>> root@sys154.3fn.net:/usr/obj/usr/src/sys/kong >>>> Timecounter "i8254" frequency 1193182 Hz quality 0 >>>> CPU: AMD Opteron(tm) Processor 846 (1992.22-MHz K8-class CPU) >>>> Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 >>>> >>>> Features=0x78bfbff>> ,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> >>>> AMD Features=0xe0500800 >>>> real memory = 3757506560 (3583 MB) >>>> avail memory = 3627720704 (3459 MB) >>>> ACPI APIC Table: >>>> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs >>>> cpu0 (BSP): APIC ID: 0 >>>> cpu1 (AP): APIC ID: 1 >>>> cpu2 (AP): APIC ID: 2 >>>> cpu3 (AP): APIC ID: 3 >>>> MADT: Forcing active-low polarity and level trigger for >> SCI ioapic0 >>>> irqs 0-23 on motherboard >>>> ioapic1 irqs 24-27 on motherboard >>>> ioapic2 irqs 28-31 on motherboard >>>> ioapic3 irqs 32-35 on motherboard >>>> ioapic4 irqs 36-39 on motherboard >>>> acpi0: on motherboard >>>> acpi0: Power Button (fixed) >>>> unknown: I/O range not supported >>>> unknown: I/O range not supported >>>> Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 >>>> acpi_timer0: <24-bit timer at 3.579545MHz> port 0xc008-0xc00b on >>>> acpi0 >>>> cpu0: on acpi0 >>>> cpu1: on acpi0 >>>> cpu2: on acpi0 >>>> cpu3: on acpi0 >>>> acpi_button0: on acpi0 >>>> pcib0: port >>>> 0xc080-0xc0ff,0xc000-0xc07f,0xcf8-0xcff iomem 0xd8000-0xdbfff on >>>> acpi0 >>>> pci0: on pcib0 >>>> pcib1: at device 6.0 on pci0 >>>> pci1: on pcib1 >>>> ohci0: mem >> 0xe8000000-0xe8000fff irq >>>> 19 at device 0.0 on pci1 >>>> ohci0: [GIANT-LOCKED] >>>> usb0: OHCI version 1.0, legacy support >>>> usb0: SMM does not respond, resetting >>>> usb0: on ohci0 >>>> usb0: USB revision 1.0 AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >>>> uhub0: 3 ports with 3 removable, self powered >>>> ohci1: mem >> 0xe8001000-0xe8001fff irq >>>> 19 at device 0.1 on pci1 >>>> ohci1: [GIANT-LOCKED] >>>> usb1: OHCI version 1.0, legacy support >>>> usb1: SMM does not respond, resetting >>>> usb1: on ohci1 >>>> usb1: USB revision 1.0 >>>> uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 >>>> uhub1: 3 ports with 3 removable, self powered >>>> pci1: at device 4.0 (no driver attached) >>>> isab0: at device 7.0 on pci0 >>>> isa0: on isab0 >>>> atapci0: port >>>> 0x1000-0x100f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device >>>> 7.1 on pci0 >>>> ata0: channel #0 on atapci0 >>>> ata1: channel #1 on atapci0 >>>> pci0: at device 7.3 (no driver attached) >>>> pcib2: on acpi0 >>>> pci8: on pcib2 >>>> pcib3: at device 1.0 on pci8 >>>> pci9: on pcib3 >>>> aac0: mem 0xf8000000-0xfbffffff irq >>>> 26 at device 2.0 on pci9 >>>> aac0: [FAST] >>>> aac0: Enabling 64-bit address support >>>> aac0: Unknown processor 100MHz, 48MB cache memory, >> optional battery >>>> not installed >>>> aac0: Kernel 4.1-0, Build 7244, S/N be37b0 >>>> aac0: Supported >>>> Options=11d7e>>> ,SOFTERR,SGMAP64,ALARM,NONDASD> >>>> aacp0: on aac0 >>>> pci8: at device 1.1 (no >>>> driver attached) >>>> pcib4: at device 2.0 on pci8 >>>> pci14: on pcib4 >>>> mpt0: port 0x3000-0x30ff mem >>>> 0xed000000-0xed00ffff,0xed010000-0xed01ffff irq 29 at >> device 1.0 on >>>> pci14 >>>> mpt0: [GIANT-LOCKED] >>>> mpt1: port 0x3400-0x34ff mem >>>> 0xed020000-0xed02ffff,0xed030000-0xed03ffff irq 30 at device >>>> 1.1 on pci14 >>>> mpt1: [GIANT-LOCKED] >>>> bge0: >>> 0x2002> mem 0xed040000-0xed04ffff,0xed050000-0xed05ffff irq >>>> 31 at device 3.0 on pci14 >>>> miibus0: on bge0 >>>> brgphy0: on miibus0 >>>> brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, >> 1000baseTX, >>>> 1000baseTX-FDX, auto >>>> bge0: Ethernet address: 00:00:1a:1a:0d:5a >>>> bge1: >>> 0x2002> mem 0xed060000-0xed06ffff,0xed070000-0xed07ffff irq >>>> 28 at device 3.1 on pci14 >>>> miibus1: on bge1 >>>> brgphy1: on miibus1 >>>> brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, >> 1000baseTX, >>>> 1000baseTX-FDX, auto >>>> bge1: Ethernet address: 00:00:1a:1a:0d:5b >>>> pci8: at device 2.1 (no >>>> driver attached) >>>> pcib5: mem 0xea202000-0xea202fff irq 32 at >>>> device 3.0 on pci8 >>>> pci19: on pcib5 >>>> pci8: at device 3.1 (no >>>> driver attached) >>>> pcib6: mem 0xea204000-0xea204fff irq 36 at >>>> device 4.0 on pci8 >>>> pci27: on pcib6 >>>> pci8: at device 4.1 (no >>>> driver attached) >>>> atkbdc0: port 0x64,0x60 irq >> 1 on acpi0 >>>> sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 >> flags 0x10 >>>> on acpi0 >>>> sio0: type 16550A, console >>>> fdc0: port 0x3f7,0x3f0-0x3f5 irq >> 6 drq 2 on >>>> acpi0 >>>> fdc0: [FAST] >>>> fd0: <1440-KB 3.5" drive> on fdc0 drive 0 >>>> orm0: at iomem >>>> 0xcc800-0xd0fff,0xcb000-0xcc7ff,0xc9800-0xcafff,0xc9000-0xc97f >>>> f,0xc8000-0xc8fff,0xc0000-0xc7fff on isa0 >>>> sc0: at flags 0x100 on isa0 >>>> sc0: VGA <16 virtual consoles, flags=0x100> >>>> sio1: configured irq 3 not in bitmap of probed irqs 0 >>>> sio1: port may not be enabled >>>> vga0: at port 0x3c0-0x3df iomem >> 0xa0000-0xbffff on >>>> isa0 Timecounters tick every 1.000 msec >>>> ipfw2 initialized, divert disabled, rule-based forwarding >> disabled, >>>> default to accept, logging disabled >>>> acd0: DVDROM at ata0-master UDMA33 Waiting >> 15 seconds >>>> for SCSI devices to settle >>>> aacd0: on aac0 >>>> aacd0: 419943MB (860045184 sectors) >>>> (probe0:aacp0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0 >>>> (probe0:aacp0:0:0:0): ILLEGAL REQUEST asc:55,3 >>>> (probe0:aacp0:0:0:0): Reserved ASC/ASCQ pair >>>> (probe5:aacp0:0:5:0): INQUIRY. CDB: 12 0 0 0 24 0 >>>> (probe5:aacp0:0:5:0): ILLEGAL REQUEST asc:55,3 >>>> (probe5:aacp0:0:5:0): Reserved ASC/ASCQ pair >>>> (probe9:aacp0:0:10:0): INQUIRY. CDB: 12 0 0 0 24 0 >>>> (probe9:aacp0:0:10:0): ILLEGAL REQUEST asc:55,3 >>>> (probe9:aacp0:0:10:0): Reserved ASC/ASCQ pair >>>> (probe10:aacp0:0:11:0): INQUIRY. CDB: 12 0 0 0 24 0 >>>> (probe10:aacp0:0:11:0): ILLEGAL REQUEST asc:55,3 >>>> (probe10:aacp0:0:11:0): Reserved ASC/ASCQ pair >>>> (probe13:aacp0:0:14:0): INQUIRY. CDB: 12 0 0 0 24 0 >>>> (probe13:aacp0:0:14:0): ILLEGAL REQUEST asc:55,3 >>>> (probe13:aacp0:0:14:0): Reserved ASC/ASCQ pair >>>> (probe1:aacp0:0:1:0): INQUIRY. CDB: 12 0 0 0 24 0 >>>> (probe1:aacp0:0:1:0): ILLEGAL REQUEST asc:55,3 >>>> (probe1:aacp0:0:1:0): Reserved ASC/ASCQ pair >>>> (probe2:aacp0:0:2:0): INQUIRY. CDB: 12 0 0 0 24 0 >>>> (probe2:aacp0:0:2:0): ILLEGAL REQUEST asc:55,3 >>>> (probe2:aacp0:0:2:0): Reserved ASC/ASCQ pair >>>> (probe3:aacp0:0:3:0): INQUIRY. CDB: 12 0 0 0 24 0 >>>> (probe3:aacp0:0:3:0): ILLEGAL REQUEST asc:55,3 >>>> (probe3:aacp0:0:3:0): Reserved ASC/ASCQ pair >>>> (probe4:aacp0:0:4:0): INQUIRY. CDB: 12 0 0 0 24 0 >>>> (probe4:aacp0:0:4:0): ILLEGAL REQUEST asc:55,3 >>>> (probe4:aacp0:0:4:0): Reserved ASC/ASCQ pair >>>> (probe6:aacp0:0:6:0): INQUIRY. CDB: 12 0 0 0 24 0 >>>> (probe6:aacp0:0:6:0): ILLEGAL REQUEST asc:55,3 >>>> (probe6:aacp0:0:6:0): Reserved ASC/ASCQ pair >>>> (probe7:aacp0:0:8:0): INQUIRY. CDB: 12 0 0 0 24 0 >>>> (probe7:aacp0:0:8:0): ILLEGAL REQUEST asc:55,3 >>>> (probe7:aacp0:0:8:0): Reserved ASC/ASCQ pair >>>> (probe8:aacp0:0:9:0): INQUIRY. CDB: 12 0 0 0 24 0 >>>> (probe8:aacp0:0:9:0): ILLEGAL REQUEST asc:55,3 >>>> (probe8:aacp0:0:9:0): Reserved ASC/ASCQ pair >>>> (probe11:aacp0:0:12:0): INQUIRY. CDB: 12 0 0 0 24 0 >>>> (probe11:aacp0:0:12:0): ILLEGAL REQUEST asc:55,3 >>>> (probe11:aacp0:0:12:0): Reserved ASC/ASCQ pair >>>> (probe12:aacp0:0:13:0): INQUIRY. CDB: 12 0 0 0 24 0 >>>> (probe12:aacp0:0:13:0): ILLEGAL REQUEST asc:55,3 >>>> (probe12:aacp0:0:13:0): Reserved ASC/ASCQ pair >>>> (probe14:aacp0:0:15:0): INQUIRY. CDB: 12 0 0 0 24 0 >>>> (probe14:aacp0:0:15:0): ILLEGAL REQUEST asc:55,3 >>>> (probe14:aacp0:0:15:0): Reserved ASC/ASCQ pair >>>> SMP: AP CPU #2 Launched! >>>> SMP: AP CPU #1 Launched! >>>> SMP: AP CPU #3 Launched! >>>> Mounting root from ufs:/dev/aacd0s1a >>>> >>>> Thank You. >>>> >>>> adios, >>>> /kong >>>> >>>> ============================================================== >>>> ========== >>>> Hostas Red (KVK10, KVK10-RIPE) || IP Networks Administrator, CJSC >>>> Rascom >> ============================================================== >>>> ========== >>>> _______________________________________________ >>>> freebsd-amd64@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 >>>> To unsubscribe, send any mail to >>>> "freebsd-amd64-unsubscribe@freebsd.org" >>>> >>>> >>> >> >> adios, >> /kong >> >> ============================================================== >> ========== >> Hostas Red (KVK10, KVK10-RIPE) || IP Networks Administrator, >> CJSC Rascom >> ============================================================== >> ========== >> > adios, /kong ======================================================================== Hostas Red (KVK10, KVK10-RIPE) || IP Networks Administrator, CJSC Rascom ======================================================================== From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 28 23:26:48 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEC1D16A4CE; Tue, 28 Dec 2004 23:26:48 +0000 (GMT) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEB5D43D48; Tue, 28 Dec 2004 23:26:48 +0000 (GMT) (envelope-from peter@wemm.org) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id 9B18B1979B; Tue, 28 Dec 2004 15:26:48 -0800 (PST) From: Peter Wemm To: Archie Cobbs Date: Tue, 28 Dec 2004 15:26:48 -0800 User-Agent: KMail/1.7.1 References: <1936407230.20041214120051@bk.ru> <200412281432.56309.peter@wemm.org> <41D1E0B2.3020500@dellroad.org> In-Reply-To: <41D1E0B2.3020500@dellroad.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412281526.48335.peter@wemm.org> cc: "James R. Van Artsalen" cc: archie@freebsd.org cc: freebsd-amd64@freebsd.org Subject: Re: mpd@amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 23:26:48 -0000 On Tuesday 28 December 2004 02:39 pm, Archie Cobbs wrote: > Peter Wemm wrote: > >>Attached is a slightly different patch. This is against the source > >>currently in ports, and it fixes two additional questionable uses > >> of va_start (). > > > > Just as a BTW; powerpc platforms need this series of changes too, > > not just amd64. > > Thanks.. this change should work for all. > > > BTW2: I wonder if some of the attached changes really could be > > done more simply with va_copy()... Not that it matters of course. > > Probably.. that's new though? No va_copy() on 4.x. Yes, its formerly part of C99, but gcc has had it for a while. In gcc-2.95 it is implemented in the gnu version of stdarg.h as __va_copy(), but we neglected to add it to our includes in 4.x: default implementation: gcc/ginclude/stdarg.h:#define __va_copy(dest, src) (dest) = (src) gcc/ginclude/varargs.h:#define __va_copy(dest, src) (dest) = (src) platform override for ppc: gcc/ginclude/va-ppc.h:#define __va_copy(dest, src) *(dest) = *(src) The same variation for ppc there would work for amd64 as well. I have run into quite a number of ports that have this knowledge built in so that they can compile on ppc with older gcc's without the includes. Anyway, never mind. :-) -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 28 23:39:11 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 696AB16A4CE for ; Tue, 28 Dec 2004 23:39:11 +0000 (GMT) Received: from eagle.sharma-home.net (cpe-24-221-178-208.ca.sprintbbd.net [24.221.178.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4869B43D41 for ; Tue, 28 Dec 2004 23:39:11 +0000 (GMT) (envelope-from adsharma@eagle.sharma-home.net) Received: by eagle.sharma-home.net (Postfix, from userid 500) id E67921F5F9; Tue, 28 Dec 2004 15:39:10 -0800 (PST) Date: Tue, 28 Dec 2004 15:39:10 -0800 From: Arun Sharma To: freebsd-amd64@freebsd.org Message-ID: <20041228233910.GA29072@sharma-home.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: Enable the i810 driver? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 23:39:11 -0000 5.3 failed to recognize my video card and I tracked it down to this patch: http://dev.gentoo.org/~spyderous/xorg-x11/redhat/xorg-x11-6.7.0-6/xorg-x11-6.7.0-AMD64-enable-i810-driver.patch While this is dealt with in xorg CVS, can we apply it locally? -Arun From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 29 01:53:00 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84EE616A4CE; Wed, 29 Dec 2004 01:53:00 +0000 (GMT) Received: from daintree.corp.yahoo.com (daintree.corp.yahoo.com [216.145.52.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F4B843D1D; Wed, 29 Dec 2004 01:53:00 +0000 (GMT) (envelope-from peter@wemm.org) Received: by daintree.corp.yahoo.com (Postfix, from userid 2154) id 677801979B; Tue, 28 Dec 2004 17:53:00 -0800 (PST) From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Tue, 28 Dec 2004 17:52:59 -0800 User-Agent: KMail/1.7.1 References: <20041228233910.GA29072@sharma-home.net> In-Reply-To: <20041228233910.GA29072@sharma-home.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412281753.00118.peter@wemm.org> cc: Arun Sharma Subject: Re: Enable the i810 driver? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 01:53:00 -0000 On Tuesday 28 December 2004 03:39 pm, Arun Sharma wrote: > 5.3 failed to recognize my video card and I tracked it down to this > patch: > > http://dev.gentoo.org/~spyderous/xorg-x11/redhat/xorg-x11-6.7.0-6/xor >g-x11-6.7.0-AMD64-enable-i810-driver.patch > > While this is dealt with in xorg CVS, can we apply it locally? > > -Arun Sounds like a good idea to me... Eric is away for a few days more though, I think.. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 29 06:17:08 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5C5616A4CE for ; Wed, 29 Dec 2004 06:17:08 +0000 (GMT) Received: from smtp3.adl2.internode.on.net (smtp3.adl2.internode.on.net [203.16.214.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE2F043D5D for ; Wed, 29 Dec 2004 06:17:07 +0000 (GMT) (envelope-from malcolm.kay@internode.on.net) Received: from beta.home (ppp35-138.lns1.adl1.internode.on.net [150.101.35.138])iBT6H5Ga074328 for ; Wed, 29 Dec 2004 16:47:06 +1030 (CST) From: Malcolm Kay Organization: at home To: freebsd-amd64@freebsd.org Date: Wed, 29 Dec 2004 16:47:05 +1030 User-Agent: KMail/1.5.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412291647.05283.malcolm.kay@internode.on.net> Subject: Sound on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 06:17:08 -0000 I've just installed FreeBSD-5.3-amd64 on an Athlon64 3200 and GA-K8VT800 motherboard. The kernel modules, in contradiction to the handbook, seem not to contain any named snd_*. Nor can I find any clues in /usr/src/sys/amd64/conf/NOTES on how the kernel or modules for sound support are to be included. Some selected dmesg lines:--------------------------------- pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pci0: at device 16.4 (no driver attached) isab0: at device 17.0 on pci0 isa0: on isab0 pci0: at device 17.5 (no driver attached) And from 'pciconf -lv':-------------------------------------- none1@pci0:17:5: class=0x040100 card=0xa0021458 chip=0x30591106 rev=0x60 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8233/33A/8235/8237 AC97 Enhanced Audio Controller' class = multimedia subclass = audio Any help would be appreciated. Malcolm From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 29 06:25:21 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D61F216A4CE for ; Wed, 29 Dec 2004 06:25:21 +0000 (GMT) Received: from sophia3.e-shell.net (sophia3.e-shell.net [64.246.46.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DB2043D48 for ; Wed, 29 Dec 2004 06:25:21 +0000 (GMT) (envelope-from loox@e-shell.net) Received: from [201.128.64.246] (unknown [201.128.64.246]) by sophia3.e-shell.net (Postfix) with ESMTP id 2E3AD65682E; Wed, 29 Dec 2004 00:25:16 -0600 (CST) From: Axel Gonzalez To: freebsd-amd64@freebsd.org Date: Wed, 29 Dec 2004 00:25:20 -0600 User-Agent: KMail/1.7.2 References: <200412291647.05283.malcolm.kay@internode.on.net> In-Reply-To: <200412291647.05283.malcolm.kay@internode.on.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412290025.20761.loox@e-shell.net> Subject: Re: Sound on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 06:25:21 -0000 I think 5.3-amd64 doesn't support loadable sound modules (correct me if I'm wrong), you need to compile sound in your kernel Add this lines to your kernel file, and recompile: device sound device "snd_via8233" HTH On Wednesday 29 December 2004 00:17, Malcolm Kay wrote: > I've just installed FreeBSD-5.3-amd64 on an Athlon64 3200 > and GA-K8VT800 motherboard. > > The kernel modules, in contradiction to the handbook, seem > not to contain any named snd_*. Nor can I find any clues in > /usr/src/sys/amd64/conf/NOTES on how the kernel or modules > for sound support are to be included. > > Some selected dmesg lines:--------------------------------- > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pci1: at device 0.0 (no driver attached) > > pci0: at device 16.4 (no driver attached) > isab0: at device 17.0 on pci0 > isa0: on isab0 > pci0: at device 17.5 (no driver attached) > > And from 'pciconf -lv':-------------------------------------- > none1@pci0:17:5: class=0x040100 card=0xa0021458 chip=0x30591106 > rev=0x60 hdr=0x00 vendor = 'VIA Technologies Inc' > device = 'VT8233/33A/8235/8237 AC97 Enhanced Audio Controller' > class = multimedia > subclass = audio > > Any help would be appreciated. > > Malcolm > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 29 07:39:49 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6560516A4CE; Wed, 29 Dec 2004 07:39:49 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 263C043D5A; Wed, 29 Dec 2004 07:39:49 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iBT7dmbr002877; Tue, 28 Dec 2004 23:39:48 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iBT7dmkS002876; Tue, 28 Dec 2004 23:39:48 -0800 (PST) (envelope-from obrien) Date: Tue, 28 Dec 2004 23:39:47 -0800 From: "David O'Brien" To: Arun Sharma Message-ID: <20041229073947.GA2780@dragon.nuxi.com> References: <20041228233910.GA29072@sharma-home.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041228233910.GA29072@sharma-home.net> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: Enable the i810 driver? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 07:39:49 -0000 On Tue, Dec 28, 2004 at 03:39:10PM -0800, Arun Sharma wrote: > 5.3 failed to recognize my video card and I tracked it down to this patch: > > http://dev.gentoo.org/~spyderous/xorg-x11/redhat/xorg-x11-6.7.0-6/xorg-x11-6.7.0-AMD64-enable-i810-driver.patch I'm courious why enabling an Intel on-board video driver would fix your problem on an AMD64 system. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 29 08:56:14 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF5C216A4CE for ; Wed, 29 Dec 2004 08:56:14 +0000 (GMT) Received: from smtp1.adl2.internode.on.net (smtp1.adl2.internode.on.net [203.16.214.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CA7943D41 for ; Wed, 29 Dec 2004 08:56:14 +0000 (GMT) (envelope-from malcolm.kay@internode.on.net) Received: from beta.home (ppp35-138.lns1.adl1.internode.on.net [150.101.35.138])iBT8u9RF022166; Wed, 29 Dec 2004 19:26:10 +1030 (CST) From: Malcolm Kay Organization: at home To: Axel Gonzalez , freebsd-amd64@freebsd.org Date: Wed, 29 Dec 2004 19:26:09 +1030 User-Agent: KMail/1.5.4 References: <200412291647.05283.malcolm.kay@internode.on.net> <200412290025.20761.loox@e-shell.net> In-Reply-To: <200412290025.20761.loox@e-shell.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412291926.09243.malcolm.kay@internode.on.net> Subject: Re: Sound on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 08:56:14 -0000 On Wed, 29 Dec 2004 04:55 pm, Axel Gonzalez wrote: > I think 5.3-amd64 doesn't support loadable sound modules (correct me if I'm > wrong), you need to compile sound in your kernel > > Add this lines to your kernel file, and recompile: > > device sound > device "snd_via8233" > This seems to work -- thanks. As yet I've not actually put any sound through but the sound HW connects up as reported by dmesg: pcm0: port 0xbc00-0xbcff irq 22 at device 17.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: And pciconf -lv: pcm0@pci0:17:5: class=0x040100 card=0xa0021458 chip=0x30591106 rev=0x60 hdr=0x00 vendor = 'VIA Technologies Inc' device = 'VT8233/33A/8235/8237 AC97 Enhanced Audio Controller' class = multimedia subclass = audio And i find /dev/dsp* now exist. Help is much appreciated; I did eventually find device sound in the man pages; but where does device "snd_via8233" come from? Malcolm From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 29 09:15:22 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ACCE516A4CE for ; Wed, 29 Dec 2004 09:15:22 +0000 (GMT) Received: from heechee.tobez.org (heechee.tobez.org [217.157.39.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDCB343D49 for ; Wed, 29 Dec 2004 09:15:21 +0000 (GMT) (envelope-from tobez@tobez.org) Received: by heechee.tobez.org (Postfix, from userid 1001) id AB062125460; Wed, 29 Dec 2004 10:15:19 +0100 (CET) Date: Wed, 29 Dec 2004 10:15:19 +0100 From: Anton Berezin To: Malcolm Kay Message-ID: <20041229091519.GD75219@heechee.tobez.org> References: <200412291647.05283.malcolm.kay@internode.on.net> <200412290025.20761.loox@e-shell.net> <200412291926.09243.malcolm.kay@internode.on.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200412291926.09243.malcolm.kay@internode.on.net> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: Sound on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 09:15:22 -0000 On Wed, Dec 29, 2004 at 07:26:09PM +1030, Malcolm Kay wrote: > On Wed, 29 Dec 2004 04:55 pm, Axel Gonzalez wrote: > > I think 5.3-amd64 doesn't support loadable sound modules (correct me if I'm > > wrong), you need to compile sound in your kernel > > > > Add this lines to your kernel file, and recompile: > > > > device sound > > device "snd_via8233" Actually it supports loadable sound modules. Or at least loadable sound modules work just fine, they are simply not connected to the build. I've been doing cd /sys/modules/sound make obj make make install right after buildworld/buildkernel/installkernel/installworld cycle, and then everything worked as intended. Why those modules are not connected to the build is a different story. \Anton. -- The moronity of the universe is a monotonically increasing function. -- Jarkko Hietaniemi From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 29 10:27:26 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA7DA16A4CE for ; Wed, 29 Dec 2004 10:27:26 +0000 (GMT) Received: from smtp-vbr12.xs4all.nl (smtp-vbr12.xs4all.nl [194.109.24.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32F0F43D1F for ; Wed, 29 Dec 2004 10:27:26 +0000 (GMT) (envelope-from rsmith@xs4all.nl) Received: from slackbox.xs4all.nl (slackbox.xs4all.nl [213.84.242.160]) by smtp-vbr12.xs4all.nl (8.12.11/8.12.11) with ESMTP id iBTAROZK031431 for ; Wed, 29 Dec 2004 11:27:25 +0100 (CET) (envelope-from rsmith@xs4all.nl) Received: by slackbox.xs4all.nl (Postfix, from userid 1001) id 0455D6299; Wed, 29 Dec 2004 11:27:58 +0100 (CET) Date: Wed, 29 Dec 2004 11:27:58 +0100 From: Roland Smith To: freebsd-amd64@freebsd.org Message-ID: <20041229102757.GA51915@slackbox.xs4all.nl> Mail-Followup-To: freebsd-amd64@freebsd.org References: <200412291647.05283.malcolm.kay@internode.on.net> <200412290025.20761.loox@e-shell.net> <200412291926.09243.malcolm.kay@internode.on.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uAKRQypu60I7Lcqm" Content-Disposition: inline In-Reply-To: <200412291926.09243.malcolm.kay@internode.on.net> User-Agent: Mutt/1.4.2.1i X-GPG-Fingerprint: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 Organization: Me, organized? X-Virus-Scanned: by XS4ALL Virus Scanner Subject: Re: Sound on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 10:27:27 -0000 --uAKRQypu60I7Lcqm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 29, 2004 at 07:26:09PM +1030, Malcolm Kay wrote: >=20 > Help is much appreciated; > I did eventually find > device sound > in the man pages; but where does > device "snd_via8233" > come from? It's listed in /usr/src/sys/conf/NOTES, with all the other sound drivers. Roland --=20 R.F. Smith /"\ ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ / No HTML/RTF in email http://www.xs4all.nl/~rsmith/ X No Word docs in email / \ Respect for open standards --uAKRQypu60I7Lcqm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB0oatEnfvsMMhpyURAtgRAKCS/lbCBwfzoADkpqaoN2QCqDeLaACfcleG QIfUVxJSO9Ht4v+6okJ1mig= =jPVN -----END PGP SIGNATURE----- --uAKRQypu60I7Lcqm-- From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 29 12:09:24 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5146916A4CE; Wed, 29 Dec 2004 12:09:24 +0000 (GMT) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id A22FE43D49; Wed, 29 Dec 2004 12:09:23 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87])iBTC9IHn007748; Wed, 29 Dec 2004 23:09:18 +1100 Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) iBTC9DIm024986; Wed, 29 Dec 2004 23:09:15 +1100 Date: Wed, 29 Dec 2004 23:09:14 +1100 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Peter Wemm In-Reply-To: <200412281526.48335.peter@wemm.org> Message-ID: <20041229221042.X92684@delplex.bde.org> References: <1936407230.20041214120051@bk.ru> <200412281432.56309.peter@wemm.org> <41D1E0B2.3020500@dellroad.org> <200412281526.48335.peter@wemm.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-amd64@freebsd.org cc: "James R. Van Artsalen" cc: archie@freebsd.org cc: Archie Cobbs Subject: Re: mpd@amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 12:09:24 -0000 On Tue, 28 Dec 2004, Peter Wemm wrote: > On Tuesday 28 December 2004 02:39 pm, Archie Cobbs wrote: > > Peter Wemm wrote: > > >>Attached is a slightly different patch. This is against the source > > >>currently in ports, and it fixes two additional questionable uses > > >> of va_start (). > > > > > > Just as a BTW; powerpc platforms need this series of changes too, > > > not just amd64. > > > > Thanks.. this change should work for all. > > > > > BTW2: I wonder if some of the attached changes really could be > > > done more simply with va_copy()... Not that it matters of course. > > > > Probably.. that's new though? No va_copy() on 4.x. > > Yes, its formerly part of C99, but gcc has had it for a while. In > gcc-2.95 it is implemented in the gnu version of stdarg.h as > __va_copy(), but we neglected to add it to our includes in 4.x: Probably not. va_copy() is only needed for restarting at a place other than the start, and possibly for acting on multiple active copies of the args (is this required to work?), but the patch seemed to only need restarting at the start. va_start() is ideal for restarting at the start; using va_copy() for this is just illogical, gratuitously unportable to systems that don't implement this part of C99 (e.g., RELENG_4), and takes slightly more code (for declaring the variable that holds the copy): dump/optr.c still gives an example of how not to use va_copy() (rev.1.27). Fix: % Index: optr.c % =================================================================== % RCS file: /home/ncvs/src/sbin/dump/optr.c,v % retrieving revision 1.30 % diff -u -2 -r1.30 optr.c % --- optr.c 19 Jun 2004 22:41:18 -0000 1.30 % +++ optr.c 20 Jun 2004 07:05:14 -0000 % @@ -234,5 +234,4 @@ % { % va_list ap; % - va_list ap2; % % (void) fprintf(stderr," DUMP: "); The patch removes the extra declaration which is the only extra code (by line count) needed to use va_copy. (But having an extra line of code is another style bug -- in KNF, local declarations of the same type should be on the same line if possible.) % @@ -241,11 +240,11 @@ % #endif % va_start(ap, fmt); % - va_copy(ap2, ap); The patch removes the va_copy() which gives 2 active copies throughout the function. We only need 1 active copy at a time. % (void) vfprintf(stderr, fmt, ap); % + va_end(ap); va_end() as soon as we have finished with a pass over the args is more natural than at the end of the function, and is needed to reuse the ap variable. % (void) fflush(stdout); % (void) fflush(stderr); % - (void) vsnprintf(lastmsg, sizeof(lastmsg), fmt, ap2); % + va_start(ap, fmt); % + (void) vsnprintf(lastmsg, sizeof(lastmsg), fmt, ap); To make another pass over the args restarting at the start, just start with va_start(). % va_end(ap); % - va_end(ap2); Using va_copy() doesn't even simplify cleaning up, since a va_end() is needed for each va_copy() just like it is needed for each va_start(). % } % > > default implementation: > gcc/ginclude/stdarg.h:#define __va_copy(dest, src) (dest) = (src) > gcc/ginclude/varargs.h:#define __va_copy(dest, src) (dest) = (src) > > platform override for ppc: > gcc/ginclude/va-ppc.h:#define __va_copy(dest, src) *(dest) = *(src) > > The same variation for ppc there would work for amd64 as well. I have > run into quite a number of ports that have this knowledge built in so > that they can compile on ppc with older gcc's without the includes. Apparently va_copy() wasn't much missed, since it wasn't in C90. Did the ports really need va_copy() or just not understand va_start()? Bruce From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 29 13:28:03 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8609616A4CE for ; Wed, 29 Dec 2004 13:28:03 +0000 (GMT) Received: from phoenix.gargantuan.com (phoenix.gargantuan.com [24.73.171.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id D006243D53 for ; Wed, 29 Dec 2004 13:28:02 +0000 (GMT) (envelope-from michael@gargantuan.com) Received: from localhost (localhost.gargantuan.com [127.0.0.1]) by spamassassin-injector (Postfix) with SMTP id 12C9C744; Wed, 29 Dec 2004 08:28:02 -0500 (EST) Received: by phoenix.gargantuan.com (Postfix, from userid 1001) id 3C608245; Wed, 29 Dec 2004 08:27:58 -0500 (EST) Date: Wed, 29 Dec 2004 08:27:58 -0500 From: "Michael W. Oliver" To: Anton Berezin Message-ID: <20041229132758.GB89526@gargantuan.com> References: <200412291647.05283.malcolm.kay@internode.on.net> <200412290025.20761.loox@e-shell.net> <200412291926.09243.malcolm.kay@internode.on.net> <20041229091519.GD75219@heechee.tobez.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rS8CxjVDS/+yyDmU" Content-Disposition: inline In-Reply-To: <20041229091519.GD75219@heechee.tobez.org> X-WWW-Site: http://michael.gargantuan.com X-PGP-Public-Key: $X-WWW-Site/gnupg/pubkey.asc X-PGP-Fingerprint: 2694 0179 AE3F BFAE 0916 0BF5 B16B FBAB C5FA A3C9 X-Home-Phone: +1-863-816-8091 X-Mobile-Phone: +1-863-738-2334 X-Home-Address0: 8008 Apache Lane X-Home-Address1: Lakeland, FL X-Home-Address2: 33810-2172 X-Home-Address3: United States of America X-Good-Question-Guide: http://www.catb.org/~esr/faqs/smart-questions.html X-Netiquette-Guidelines: http://www.ietf.org/rfc/rfc1855.txt User-Agent: Mutt/1.5.6i X-Spam-DCC: dcc3mcgill: phoenix.gargantuan.com 1275; Body=1 Fuz1=1 Fuz2=1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on phoenix.gargantuan.com X-Spam-Level: X-Spam-Status: No, score=-105.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, USER_IN_WHITELIST autolearn=ham version=3.0.1 X-Spam-Pyzor: Reported 0 times. cc: freebsd-amd64@freebsd.org Subject: Re: Sound on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 13:28:03 -0000 --rS8CxjVDS/+yyDmU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004-12-29T10:15:19+0100, Anton Berezin wrote: > On Wed, Dec 29, 2004 at 07:26:09PM +1030, Malcolm Kay wrote: > > On Wed, 29 Dec 2004 04:55 pm, Axel Gonzalez wrote: > Why those modules are not connected to the build is a different story. I have just upgraded to CURRENT on my machine, and the sound modules are now connected to the build. They are built and installed in /boot/kernel/ and I am loading them via /boot/loader.conf. /boot/loader.conf ------------------ ng_ubt_load=3D"YES" sound_load=3D"YES" snd_via8233_load=3D"YES" radeon_load=3D"YES" loader_color=3D"YES" boot_verbose=3D"YES" --=20 Michael W. Oliver [see complete headers for contact information] --rS8CxjVDS/+yyDmU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB0rDesWv7q8X6o8kRAqsMAKC2xo3fS4C1wobrzKu8w3lYwi0KbgCgtP08 cG8vIiSBswYukLVgXA7b7wc= =3aQu -----END PGP SIGNATURE----- --rS8CxjVDS/+yyDmU-- From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 29 14:15:30 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A27C716A4CE for ; Wed, 29 Dec 2004 14:15:30 +0000 (GMT) Received: from smtp3.adl2.internode.on.net (smtp3.adl2.internode.on.net [203.16.214.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED64F43D41 for ; Wed, 29 Dec 2004 14:15:29 +0000 (GMT) (envelope-from malcolm.kay@internode.on.net) Received: from beta.home (ppp35-138.lns1.adl1.internode.on.net [150.101.35.138])iBTEFRGa021222; Thu, 30 Dec 2004 00:45:27 +1030 (CST) From: Malcolm Kay Organization: at home To: Roland Smith , freebsd-amd64@freebsd.org Date: Thu, 30 Dec 2004 00:45:27 +1030 User-Agent: KMail/1.5.4 References: <200412291647.05283.malcolm.kay@internode.on.net> <200412291926.09243.malcolm.kay@internode.on.net> <20041229102757.GA51915@slackbox.xs4all.nl> In-Reply-To: <20041229102757.GA51915@slackbox.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412300045.27317.malcolm.kay@internode.on.net> Subject: Re: Sound on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 14:15:30 -0000 On Wed, 29 Dec 2004 08:57 pm, Roland Smith wrote: > On Wed, Dec 29, 2004 at 07:26:09PM +1030, Malcolm Kay wrote: > > Help is much appreciated; > > I did eventually find > > device sound > > in the man pages; but where does > > device "snd_via8233" > > come from? > > It's listed in /usr/src/sys/conf/NOTES, with all the other sound drivers. Hmm, I did not realise /usr/src/sys/conf/ existed. I've worked in the old way in /usr/src/sys/amd64/conf which also contains a NOTES file but no reference to sound. Now, I find a lot of interesting things in the /usr/src/sys/conf/ directory. But how is this meant to be used? Perhaps the Makefiles.* come into effect with "Building a Kernel the ``New'' Way" Malcolm From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 29 15:41:29 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9973616A4CE for ; Wed, 29 Dec 2004 15:41:29 +0000 (GMT) Received: from phoenix.gargantuan.com (phoenix.gargantuan.com [24.73.171.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id 434AF43D2D for ; Wed, 29 Dec 2004 15:41:29 +0000 (GMT) (envelope-from michael@gargantuan.com) Received: from localhost (localhost.gargantuan.com [127.0.0.1]) by spamassassin-injector (Postfix) with SMTP id 630CB7C3; Wed, 29 Dec 2004 10:41:28 -0500 (EST) Received: by phoenix.gargantuan.com (Postfix, from userid 1001) id 62BDDA8; Wed, 29 Dec 2004 10:41:24 -0500 (EST) Date: Wed, 29 Dec 2004 10:41:24 -0500 From: "Michael W. Oliver" To: Malcolm Kay Message-ID: <20041229154124.GC89526@gargantuan.com> References: <200412291647.05283.malcolm.kay@internode.on.net> <200412291926.09243.malcolm.kay@internode.on.net> <20041229102757.GA51915@slackbox.xs4all.nl> <200412300045.27317.malcolm.kay@internode.on.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DSayHWYpDlRfCAAQ" Content-Disposition: inline In-Reply-To: <200412300045.27317.malcolm.kay@internode.on.net> X-WWW-Site: http://michael.gargantuan.com X-PGP-Public-Key: $X-WWW-Site/gnupg/pubkey.asc X-PGP-Fingerprint: 2694 0179 AE3F BFAE 0916 0BF5 B16B FBAB C5FA A3C9 X-Home-Phone: +1-863-816-8091 X-Mobile-Phone: +1-863-738-2334 X-Home-Address0: 8008 Apache Lane X-Home-Address1: Lakeland, FL X-Home-Address2: 33810-2172 X-Home-Address3: United States of America X-Good-Question-Guide: http://www.catb.org/~esr/faqs/smart-questions.html X-Netiquette-Guidelines: http://www.ietf.org/rfc/rfc1855.txt User-Agent: Mutt/1.5.6i X-Spam-DCC: dcc3mcgill: phoenix.gargantuan.com 1275; Body=1 Fuz1=1 Fuz2=1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on phoenix.gargantuan.com X-Spam-Level: X-Spam-Status: No, score=-105.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, USER_IN_WHITELIST autolearn=ham version=3.0.1 X-Spam-Pyzor: Reported 0 times. cc: freebsd-amd64@freebsd.org Subject: Re: Sound on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 15:41:29 -0000 --DSayHWYpDlRfCAAQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004-12-30T00:45:27+1030, Malcolm Kay wrote: > On Wed, 29 Dec 2004 08:57 pm, Roland Smith wrote: > > On Wed, Dec 29, 2004 at 07:26:09PM +1030, Malcolm Kay wrote: > > > Help is much appreciated; > > > I did eventually find > > > device sound > > > in the man pages; but where does > > > device "snd_via8233" > > > come from? > > It's listed in /usr/src/sys/conf/NOTES, with all the other sound driver= s. > Hmm, I did not realise /usr/src/sys/conf/ existed. I've worked in the old > way in /usr/src/sys/amd64/conf which also contains a NOTES file but no re= ference > to sound. > Now, I find a lot of interesting things in the /usr/src/sys/conf/ directo= ry. > But how is this meant to be used? Perhaps the Makefiles.* come into effec= t with > "Building a Kernel the ``New'' Way" =46rom /usr/src/sys/amd64/conf you can run `make LINT' and the resulting LINT file will have the sound and snd* devices listed within. --=20 Michael W. Oliver [see complete headers for contact information] --DSayHWYpDlRfCAAQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB0tAksWv7q8X6o8kRArdSAKCKxT0HoAV4Td7hhd0SwGbugaSuIACfXioe DtQvQhrFdw6MJwqCWccJ/Vg= =3V7+ -----END PGP SIGNATURE----- --DSayHWYpDlRfCAAQ-- From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 29 16:09:41 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CA3E216A4CE for ; Wed, 29 Dec 2004 16:09:41 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13D2143D1D for ; Wed, 29 Dec 2004 16:09:41 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iBTG9dnR034967; Wed, 29 Dec 2004 18:09:39 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 64510-07; Wed, 29 Dec 2004 18:09:39 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iBTG9cgW034964 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 29 Dec 2004 18:09:39 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iBTG9m7u035427; Wed, 29 Dec 2004 18:09:48 +0200 (EET) (envelope-from ru) Date: Wed, 29 Dec 2004 18:09:48 +0200 From: Ruslan Ermilov To: Anton Berezin Message-ID: <20041229160948.GB35305@ip.net.ua> References: <200412291647.05283.malcolm.kay@internode.on.net> <200412290025.20761.loox@e-shell.net> <200412291926.09243.malcolm.kay@internode.on.net> <20041229091519.GD75219@heechee.tobez.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ftEhullJWpWg/VHq" Content-Disposition: inline In-Reply-To: <20041229091519.GD75219@heechee.tobez.org> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: freebsd-amd64@freebsd.org Subject: Re: Sound on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 16:09:42 -0000 --ftEhullJWpWg/VHq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 29, 2004 at 10:15:19AM +0100, Anton Berezin wrote: > On Wed, Dec 29, 2004 at 07:26:09PM +1030, Malcolm Kay wrote: > > On Wed, 29 Dec 2004 04:55 pm, Axel Gonzalez wrote: > > > I think 5.3-amd64 doesn't support loadable sound modules (correct me = if I'm > > > wrong), you need to compile sound in your kernel > > > > > > Add this lines to your kernel file, and recompile: > > > > > > device sound > > > device "snd_via8233" >=20 > Actually it supports loadable sound modules. Or at least loadable sound > modules work just fine, they are simply not connected to the build. >=20 > I've been doing >=20 > cd /sys/modules/sound > make obj > make > make install >=20 > right after buildworld/buildkernel/installkernel/installworld cycle, and > then everything worked as intended. >=20 > Why those modules are not connected to the build is a different story. >=20 PR misc/74870 Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --ftEhullJWpWg/VHq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB0tbMqRfpzJluFF4RAn5aAJ9/dl37M1lWjCntoFrNj4G0vzQJEwCfYki/ ljib5Y5CK/sNRzC5vd4n25o= =zLp+ -----END PGP SIGNATURE----- --ftEhullJWpWg/VHq-- From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 29 16:13:12 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E98C316A4CE for ; Wed, 29 Dec 2004 16:13:12 +0000 (GMT) Received: from web51008.mail.yahoo.com (web51008.mail.yahoo.com [206.190.38.139]) by mx1.FreeBSD.org (Postfix) with SMTP id 6588043D2D for ; Wed, 29 Dec 2004 16:13:12 +0000 (GMT) (envelope-from tfcheng@yahoo.com) Received: (qmail 35037 invoked by uid 60001); 29 Dec 2004 16:13:11 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=EP4AyHxAR5UIcGWm1d29luvacmGHHE7bEP+Q6v61L075cT/21zCR6L/ck1M90GNY+itV6qe3+HRM5+wojwP+f1NHQhcwCRmd7vQxi5sF+yzgNwmXe5voWkQGv0Q6meUFw9uRl7sVvhSOH23wLvpsBKsNQcTpExtr0ZPFbr02r7Q= ; Message-ID: <20041229161311.35035.qmail@web51008.mail.yahoo.com> Received: from [69.113.106.60] by web51008.mail.yahoo.com via HTTP; Thu, 30 Dec 2004 00:13:11 CST Date: Thu, 30 Dec 2004 00:13:11 +0800 (CST) From: "T.F. Cheng" To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 8bit Subject: i386 compat X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 16:13:13 -0000 hi, i am running amd64 version of freebsd 5.3-stable and would like to have i386 compatibility. Have read an article about a "build32.sh" in the /usr/src/tools.. but I didn't find it on my system. There is a README though, [quote] # $FreeBSD: src/tools/lib32/README,v 1.1.2.1 2004/11/26 19:33:01 peter Exp $ Set WITH_LIB32=yes in /etc/make.conf and do a buildworld/installworld. Alternatively, if you have just done a buildworld/installworld, you might be able to 'make build32' and 'make install32' in the top of the /usr/src tree. [/quote] has anybody ever done that? I am not quite sure and would like to ask before i start it. thanks!! TFC ===== Best Regards, Tsu-Fan Cheng _________________________________________________________ Do You Yahoo!? µn°O§K¶Oªº @yahoo.com ¤¤¤å¹q¤l¶l¥ó @ http://chinese.mail.yahoo.com Get your free @yahoo.com address at http://chinese.mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 29 17:23:46 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DBF616A4DC for ; Wed, 29 Dec 2004 17:23:46 +0000 (GMT) Received: from eagle.sharma-home.net (cpe-24-221-178-208.ca.sprintbbd.net [24.221.178.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id C35CE43D45 for ; Wed, 29 Dec 2004 17:23:45 +0000 (GMT) (envelope-from adsharma@eagle.sharma-home.net) Received: by eagle.sharma-home.net (Postfix, from userid 500) id 319001F5F9; Wed, 29 Dec 2004 09:23:45 -0800 (PST) Date: Wed, 29 Dec 2004 09:23:45 -0800 From: Arun Sharma To: freebsd-amd64@freebsd.org Message-ID: <20041229172345.GA32737@sharma-home.net> References: <20041228233910.GA29072@sharma-home.net> <20041229073947.GA2780@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041229073947.GA2780@dragon.nuxi.com> User-Agent: Mutt/1.4.1i Subject: Re: Enable the i810 driver? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 17:23:46 -0000 On Tue, Dec 28, 2004 at 11:39:47PM -0800, David O'Brien wrote: > On Tue, Dec 28, 2004 at 03:39:10PM -0800, Arun Sharma wrote: > > 5.3 failed to recognize my video card and I tracked it down to this patch: > > > > http://dev.gentoo.org/~spyderous/xorg-x11/redhat/xorg-x11-6.7.0-6/xorg-x11-6.7.0-AMD64-enable-i810-driver.patch > > I'm courious why enabling an Intel on-board video driver would fix your > problem on an AMD64 system. > I thought EM64T based systems are on-topic on this list. http://www.freebsd.org/platforms/amd64.html -Arun From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 29 20:17:27 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3342B16A4CE; Wed, 29 Dec 2004 20:17:27 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B545F43D4C; Wed, 29 Dec 2004 20:17:26 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iBTKHP6L068448; Wed, 29 Dec 2004 12:17:25 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iBTKHPww068447; Wed, 29 Dec 2004 12:17:25 -0800 (PST) (envelope-from obrien) Date: Wed, 29 Dec 2004 12:17:25 -0800 From: "David O'Brien" To: Arun Sharma Message-ID: <20041229201725.GA68336@dragon.nuxi.com> References: <20041228233910.GA29072@sharma-home.net> <20041229073947.GA2780@dragon.nuxi.com> <20041229172345.GA32737@sharma-home.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041229172345.GA32737@sharma-home.net> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: Enable the i810 driver? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 20:17:27 -0000 On Wed, Dec 29, 2004 at 09:23:45AM -0800, Arun Sharma wrote: > On Tue, Dec 28, 2004 at 11:39:47PM -0800, David O'Brien wrote: > > On Tue, Dec 28, 2004 at 03:39:10PM -0800, Arun Sharma wrote: > > > 5.3 failed to recognize my video card and I tracked it down to this patch: > > > > > > http://dev.gentoo.org/~spyderous/xorg-x11/redhat/xorg-x11-6.7.0-6/xorg-x11-6.7.0-AMD64-enable-i810-driver.patch > > > > I'm courious why enabling an Intel on-board video driver would fix your > > problem on an AMD64 system. > > I thought EM64T based systems are on-topic on this list. > http://www.freebsd.org/platforms/amd64.html They are on-topic. But my knowledge of the i810 video driver is that it is to drive the video on Intel's i810 and i815 Pentium-3 motherboards. Those certainly can't accept an EM64T CPU. So I'm puzzled what piece of hardware, in a platform that FreeBSD/AMD64 runs on, that could need this driver. src/sys/conf/files.amd64 revision 1.46 removed pci/agp_i810.c under these assumptions. Were they wrong and I should add pci/agp_i810.c back? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 29 21:00:50 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDB9D16A4D1 for ; Wed, 29 Dec 2004 21:00:50 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4C2943D60 for ; Wed, 29 Dec 2004 21:00:50 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 15594 invoked from network); 29 Dec 2004 21:00:50 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 29 Dec 2004 21:00:49 -0000 Received: from [10.50.41.243] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iBTL0QdJ004673; Wed, 29 Dec 2004 16:00:42 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org Date: Wed, 29 Dec 2004 15:52:34 -0500 User-Agent: KMail/1.6.2 References: <20041228233910.GA29072@sharma-home.net> <20041229172345.GA32737@sharma-home.net> <20041229201725.GA68336@dragon.nuxi.com> In-Reply-To: <20041229201725.GA68336@dragon.nuxi.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200412291552.34223.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Arun Sharma cc: David O'Brien Subject: Re: Enable the i810 driver? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 21:00:51 -0000 On Wednesday 29 December 2004 03:17 pm, David O'Brien wrote: > On Wed, Dec 29, 2004 at 09:23:45AM -0800, Arun Sharma wrote: > > On Tue, Dec 28, 2004 at 11:39:47PM -0800, David O'Brien wrote: > > > On Tue, Dec 28, 2004 at 03:39:10PM -0800, Arun Sharma wrote: > > > > 5.3 failed to recognize my video card and I tracked it down to this > > > > patch: > > > > > > > > http://dev.gentoo.org/~spyderous/xorg-x11/redhat/xorg-x11-6.7.0-6/xor > > > >g-x11-6.7.0-AMD64-enable-i810-driver.patch > > > > > > I'm courious why enabling an Intel on-board video driver would fix your > > > problem on an AMD64 system. > > > > I thought EM64T based systems are on-topic on this list. > > http://www.freebsd.org/platforms/amd64.html > > They are on-topic. > > But my knowledge of the i810 video driver is that it is to drive the > video on Intel's i810 and i815 Pentium-3 motherboards. Those certainly > can't accept an EM64T CPU. So I'm puzzled what piece of hardware, in a > platform that FreeBSD/AMD64 runs on, that could need this driver. > > src/sys/conf/files.amd64 revision 1.46 removed pci/agp_i810.c under these > assumptions. Were they wrong and I should add pci/agp_i810.c back? The i810 actually drives up to i830 now, and will eventually be replaced by a driver that does i810 up through i915 and i925 (the latest PCI express chipsets with onboard graphics IIRC). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 29 21:02:59 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E96E616A4CE for ; Wed, 29 Dec 2004 21:02:59 +0000 (GMT) Received: from eagle.sharma-home.net (cpe-24-221-178-208.ca.sprintbbd.net [24.221.178.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94D9243D3F for ; Wed, 29 Dec 2004 21:02:57 +0000 (GMT) (envelope-from adsharma@eagle.sharma-home.net) Received: by eagle.sharma-home.net (Postfix, from userid 500) id 029F51F5F9; Wed, 29 Dec 2004 13:02:56 -0800 (PST) Date: Wed, 29 Dec 2004 13:02:56 -0800 From: Arun Sharma To: freebsd-amd64@freebsd.org Message-ID: <20041229210256.GA798@sharma-home.net> References: <20041228233910.GA29072@sharma-home.net> <20041229073947.GA2780@dragon.nuxi.com> <20041229172345.GA32737@sharma-home.net> <20041229201725.GA68336@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041229201725.GA68336@dragon.nuxi.com> User-Agent: Mutt/1.4.1i Subject: Re: Enable the i810 driver? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 21:03:00 -0000 On Wed, Dec 29, 2004 at 12:17:25PM -0800, David O'Brien wrote: > They are on-topic. > > But my knowledge of the i810 video driver is that it is to drive the > video on Intel's i810 and i815 Pentium-3 motherboards. Those certainly > can't accept an EM64T CPU. So I'm puzzled what piece of hardware, in a > platform that FreeBSD/AMD64 runs on, that could need this driver. > The board in question is grantsdale (aka 915G): http://www.intel.com/design/chipsets/915g/ > src/sys/conf/files.amd64 revision 1.46 removed pci/agp_i810.c under these > assumptions. Were they wrong and I should add pci/agp_i810.c back? My understanding is that, this driver needs to be enhanced to support the 915G chipset: #define CHIP_I810 0 /* i810/i815 */ #define CHIP_I830 1 /* 830M/845G */ #define CHIP_I855 2 /* 852GM/855GM/865G */ Also, agp_810.c may be a little bit of a misnomer for the file, given that it seems to support other chipsets. This is true of the xorg i810_drv.o as well. Even though the name suggests only i810, it really supports a range of chipsets including the 915G: http://cvs.freedesktop.org/xorg/xc/programs/Xserver/hw/xfree86/drivers/i810/i810_driver.c?rev=1.13&view=auto -Arun From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 29 21:26:16 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 196AD16A4CE; Wed, 29 Dec 2004 21:26:16 +0000 (GMT) Received: from phoenix.gargantuan.com (phoenix.gargantuan.com [24.73.171.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78D7B43D2F; Wed, 29 Dec 2004 21:26:15 +0000 (GMT) (envelope-from michael@gargantuan.com) Received: from localhost (localhost.gargantuan.com [127.0.0.1]) by spamassassin-injector (Postfix) with SMTP id 592015F8; Wed, 29 Dec 2004 16:26:14 -0500 (EST) Received: by phoenix.gargantuan.com (Postfix, from userid 1001) id 42295C4; Wed, 29 Dec 2004 16:25:55 -0500 (EST) Date: Wed, 29 Dec 2004 16:25:55 -0500 From: "Michael W. Oliver" To: amd64@freebsd.org;, questions@freebsd.org Message-ID: <20041229212555.GD89526@gargantuan.com> Mail-Followup-To: amd64@freebsd.org;, questions@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="C1iGAkRnbeBonpVg" Content-Disposition: inline X-WWW-Site: http://michael.gargantuan.com X-PGP-Public-Key: $X-WWW-Site/gnupg/pubkey.asc X-PGP-Fingerprint: 2694 0179 AE3F BFAE 0916 0BF5 B16B FBAB C5FA A3C9 X-Home-Phone: +1-863-816-8091 X-Mobile-Phone: +1-863-738-2334 X-Home-Address0: 8008 Apache Lane X-Home-Address1: Lakeland, FL X-Home-Address2: 33810-2172 X-Home-Address3: United States of America X-Good-Question-Guide: http://www.catb.org/~esr/faqs/smart-questions.html X-Netiquette-Guidelines: http://www.ietf.org/rfc/rfc1855.txt User-Agent: Mutt/1.5.6i X-Spam-DCC: EATSERVER: phoenix.gargantuan.com 1166; Body=1 Fuz1=1 Fuz2=1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on phoenix.gargantuan.com X-Spam-Level: X-Spam-Status: No, score=-105.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, USER_IN_WHITELIST autolearn=ham version=3.0.1 X-Spam-Pyzor: Reported 0 times. Subject: CPU speed not reported correctly X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 21:26:16 -0000 --C1iGAkRnbeBonpVg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello again folks. Here is the head of my `dmesg -a': Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-CURRENT #3: Wed Dec 29 09:10:47 EST 2004 mwoliver@gambit.gargantuan.com:/usr/obj/usr/src/sys/GAMBIT WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant WARNING: MPSAFE network stack disabled, expect reduced performance. Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff8091e000. Preloaded elf obj module "/boot/kernel/sound.ko" at 0xffffffff8091e1a8. Preloaded elf obj module "/boot/kernel/snd_via8233.ko" at 0xffffffff8091e7d= 0. Preloaded acpi_dsdt "/boot/DSDT.aml" at 0xffffffff8091ed00. Preloaded elf obj module "/boot/kernel/ng_ubt.ko" at 0xffffffff8091ed50. Preloaded elf obj module "/boot/kernel/netgraph.ko" at 0xffffffff8091f278. Preloaded elf obj module "/boot/kernel/radeon.ko" at 0xffffffff8091f8a8. Preloaded elf obj module "/boot/kernel/agp.ko" at 0xffffffff8091fe50. ACPI APIC Table: Calibrating clock(s) ... i8254 clock: 1193174 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 801825045 Hz CPU: AMD Athlon(tm) 64 Processor 3400+ (801.83-MHz K8-class CPU) Origin =3D "AuthenticAMD" Id =3D 0xf4a Stepping =3D 10 Features=3D0x78bfbff AMD Features=3D0xe0500800 L1 2MB data TLB: 8 entries, fully associative L1 2MB instruction TLB: 8 entries, fully associative L1 4KB data TLB: 32 entries, fully associative L1 4KB instruction TLB: 32 entries, fully associative L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associative L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way associat= ive L2 2MB unified TLB: 0 entries, disabled/not present L2 4KB data TLB: 512 entries, 4-way associative L2 4KB instruction TLB: 512 entries, 4-way associative L2 unified cache: 1024 kbytes, 64 bytes/line, 1 lines/tag, 16-way associati= ve OK, here is my question: Why is the CPU speed reported as 801.83MHz? Is there something really wrong with my setup here? I have this machine configured to dual boot with the other OS being the x64 version of XP, and it reports a 2.2GHz CPU (for what it's worth...). Is this just some cosmetic thing, or is my CPU really running that slow? $ uname -a FreeBSD gambit.gargantuan.com 6.0-CURRENT FreeBSD 6.0-CURRENT #3: Wed Dec 29 09:10:47 EST 2004 mwoliver@gambit.gargantuan.com:/usr/obj/usr/src/sys/GAMBIT amd64 Thanks. --=20 Michael W. Oliver [see complete headers for contact information] --C1iGAkRnbeBonpVg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB0yDjsWv7q8X6o8kRAhZDAJ0eIQ1ElcmA4bsX+ijFlzhaVTSrpQCgiue1 O9puwsVDx4r9Zu4F63lSBp8= =Eg+8 -----END PGP SIGNATURE----- --C1iGAkRnbeBonpVg-- From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 29 21:31:21 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C06316A4CE for ; Wed, 29 Dec 2004 21:31:21 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E97E43D39 for ; Wed, 29 Dec 2004 21:31:20 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iBTLVKe4069925 for ; Wed, 29 Dec 2004 13:31:20 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iBTLVKVr069924 for freebsd-amd64@freebsd.org; Wed, 29 Dec 2004 13:31:20 -0800 (PST) (envelope-from obrien) Date: Wed, 29 Dec 2004 13:31:20 -0800 From: "David O'Brien" To: freebsd-amd64@freebsd.org Message-ID: <20041229213120.GA69862@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="3V7upXqbjpZ4EhLz" Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Subject: NEW 6-CURRENT snapshot uploaded X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 21:31:21 -0000 --3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/6-CURRENT-20041229/ MD5 (6-CURRENT-20041229-amd64-disc2.iso) =3D 50b007c099e6b395a9092b76888d10= 72 MD5 (6-CURRENT-20041229-amd64-miniinst.iso) =3D 6fbbbb4d65c76d12e2b22ce0717= 362ad --=20 -- David (obrien@FreeBSD.org) --3V7upXqbjpZ4EhLz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: FcMuLrOail4FmCCUfDuKxZFYSKmqxW6P iQCVAwUBQdMiJmVgqaw0+fnVAQGfcAQAmFeKEQY3K6bv9ILGKtMIU/MlO9B1KE7b ZlXH7WLCxfuXyIqkGx5/psUHBIOCGBIXwOCYptALK0tcqsPGsbwwA9+Mkh839hT9 kU0ufLZVf23H2xaDyHY2vKhimOP4VyjTfNOtZVNnJ+aQRl9E2Mdglkk23OFpNDR8 BrYs3j5tJt8= =0Dv2 -----END PGP SIGNATURE----- --3V7upXqbjpZ4EhLz-- From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 29 23:57:43 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61F7716A4CE for ; Wed, 29 Dec 2004 23:57:43 +0000 (GMT) Received: from rc.tex-an.net (rc.tex-an.net [141.198.193.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 266B943D39 for ; Wed, 29 Dec 2004 23:57:43 +0000 (GMT) (envelope-from wayside@rc.tex-an.net) Received: from rc.tex-an.net (localhost.capnet.state.tx.us [127.0.0.1]) by rc.tex-an.net (8.13.1/8.13.1) with ESMTP id iBTNtdNH049893 for ; Wed, 29 Dec 2004 17:55:39 -0600 (CST) (envelope-from wayside@rc.tex-an.net) Received: from localhost (wayside@localhost) by rc.tex-an.net (8.13.1/8.13.1/Submit) with ESMTP id iBTNtdkn049890 for ; Wed, 29 Dec 2004 17:55:39 -0600 (CST) (envelope-from wayside@rc.tex-an.net) Date: Wed, 29 Dec 2004 17:55:39 -0600 (CST) From: dev tree To: freebsd-amd64@freebsd.org In-Reply-To: <20041229213120.GA69862@dragon.nuxi.com> Message-ID: <20041229175411.S49222@rc.tex-an.net> References: <20041229213120.GA69862@dragon.nuxi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: NEW 6-CURRENT snapshot uploaded X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 23:57:43 -0000 I'm not seeing it: ftp> pwd 257 "/pub/FreeBSD/snapshots/amd64" ftp> dir 229 Entering Extended Passive Mode (|||21035|) 150 Here comes the directory listing. drwxrwxr-x 2 110 0 512 Oct 25 12:05 5-20040324-CURRENT 226 Directory send OK. Did you pull it back off? On Wed, 29 Dec 2004, David O'Brien wrote: > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/amd64/6-CURRENT-20041229/ > > MD5 (6-CURRENT-20041229-amd64-disc2.iso) = 50b007c099e6b395a9092b76888d1072 > MD5 (6-CURRENT-20041229-amd64-miniinst.iso) = 6fbbbb4d65c76d12e2b22ce0717362ad > > -- > -- David (obrien@FreeBSD.org) > From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 30 00:08:03 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F9F216A4CE for ; Thu, 30 Dec 2004 00:08:03 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2032743D39 for ; Thu, 30 Dec 2004 00:08:03 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 465ED51194; Wed, 29 Dec 2004 16:07:59 -0800 (PST) Date: Wed, 29 Dec 2004 16:07:59 -0800 From: Kris Kennaway To: dev tree Message-ID: <20041230000758.GA96442@xor.obsecurity.org> References: <20041229213120.GA69862@dragon.nuxi.com> <20041229175411.S49222@rc.tex-an.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jI8keyz6grp/JLjh" Content-Disposition: inline In-Reply-To: <20041229175411.S49222@rc.tex-an.net> User-Agent: Mutt/1.4.2.1i cc: freebsd-amd64@freebsd.org Subject: Re: NEW 6-CURRENT snapshot uploaded X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 00:08:03 -0000 --jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 29, 2004 at 05:55:39PM -0600, dev tree wrote: > I'm not seeing it: >=20 > ftp> pwd > 257 "/pub/FreeBSD/snapshots/amd64" > ftp> dir > 229 Entering Extended Passive Mode (|||21035|) > 150 Here comes the directory listing. > drwxrwxr-x 2 110 0 512 Oct 25 12:05 5-20040324-CURR= ENT > 226 Directory send OK. >=20 > Did you pull it back off? If David uploaded it to ftp-master, it will take a few hours for ftp.freebsd.org to mirror it. Try again later. Kris --jI8keyz6grp/JLjh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB00beWry0BWjoQKURAt1fAKDYKKeBIPWUkIaO41Jwqwn1Es0pcgCgiCH4 dgU48ZB9XKNWBjtE2uqHFic= =Lwwr -----END PGP SIGNATURE----- --jI8keyz6grp/JLjh-- From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 30 00:47:26 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6312C16A4CE for ; Thu, 30 Dec 2004 00:47:26 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 306FA43D3F for ; Thu, 30 Dec 2004 00:47:26 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iBU0lObX092107; Wed, 29 Dec 2004 16:47:24 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iBU0lMbw092103; Wed, 29 Dec 2004 16:47:22 -0800 (PST) (envelope-from obrien) Date: Wed, 29 Dec 2004 16:47:22 -0800 From: "David O'Brien" To: Anton Berezin Message-ID: <20041230004722.GB68336@dragon.nuxi.com> References: <200412291647.05283.malcolm.kay@internode.on.net> <200412290025.20761.loox@e-shell.net> <200412291926.09243.malcolm.kay@internode.on.net> <20041229091519.GD75219@heechee.tobez.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041229091519.GD75219@heechee.tobez.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: Sound on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 00:47:26 -0000 On Wed, Dec 29, 2004 at 10:15:19AM +0100, Anton Berezin wrote: > On Wed, Dec 29, 2004 at 07:26:09PM +1030, Malcolm Kay wrote: > > On Wed, 29 Dec 2004 04:55 pm, Axel Gonzalez wrote: > > > I think 5.3-amd64 doesn't support loadable sound modules (correct me if I'm > > > wrong), you need to compile sound in your kernel > > > > > > Add this lines to your kernel file, and recompile: > > > > > > device sound > > > device "snd_via8233" > > Actually it supports loadable sound modules. Or at least loadable sound > modules work just fine, they are simply not connected to the build. .. > Why those modules are not connected to the build is a different story. Are you sure? ---------------------------- revision 1.395 date: 2004/08/29 09:14:18; author: obrien; state: Exp; lines: +1 -0 Enable sound modules. ---------------------------- Can you check to see what revsion of src/sys/modules/Makefile you have? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 30 00:50:14 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 156D316A4CF for ; Thu, 30 Dec 2004 00:50:14 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4A7343D53 for ; Thu, 30 Dec 2004 00:50:13 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iBU0oCnI092244; Wed, 29 Dec 2004 16:50:12 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iBU0oCa5092243; Wed, 29 Dec 2004 16:50:12 -0800 (PST) (envelope-from obrien) Date: Wed, 29 Dec 2004 16:50:12 -0800 From: "David O'Brien" To: Anton Berezin Message-ID: <20041230005012.GC68336@dragon.nuxi.com> References: <200412291647.05283.malcolm.kay@internode.on.net> <200412290025.20761.loox@e-shell.net> <200412291926.09243.malcolm.kay@internode.on.net> <20041229091519.GD75219@heechee.tobez.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041229091519.GD75219@heechee.tobez.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: Sound on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 00:50:14 -0000 On Wed, Dec 29, 2004 at 10:15:19AM +0100, Anton Berezin wrote: > On Wed, Dec 29, 2004 at 07:26:09PM +1030, Malcolm Kay wrote: > > On Wed, 29 Dec 2004 04:55 pm, Axel Gonzalez wrote: > > > I think 5.3-amd64 doesn't support loadable sound modules (correct > > > me if I'm wrong), you need to compile sound in your kernel > > > > > > Add this lines to your kernel file, and recompile: > > > > > > device sound > > > device "snd_via8233" > > Actually it supports loadable sound modules. Or at least loadable sound > modules work just fine, they are simply not connected to the build. Ah, we didn't build them in RELENG_5 (vs. 6-CURRENT). I've MFC'ed the change. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 30 00:57:38 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A736B16A4CE; Thu, 30 Dec 2004 00:57:38 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C9E343D45; Thu, 30 Dec 2004 00:57:38 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iBU0vcr2092485; Wed, 29 Dec 2004 16:57:38 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iBU0vc3L092484; Wed, 29 Dec 2004 16:57:38 -0800 (PST) (envelope-from obrien) Date: Wed, 29 Dec 2004 16:57:38 -0800 From: "David O'Brien" To: freebsd-amd64@freebsd.org;, questions@freebsd.org Message-ID: <20041230005738.GD68336@dragon.nuxi.com> References: <20041229212555.GD89526@gargantuan.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041229212555.GD89526@gargantuan.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Subject: Re: CPU speed not reported correctly X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 00:57:38 -0000 On Wed, Dec 29, 2004 at 04:25:55PM -0500, Michael W. Oliver wrote: > CPU: AMD Athlon(tm) 64 Processor 3400+ (801.83-MHz K8-class CPU) .. > OK, here is my question: Why is the CPU speed reported as 801.83MHz? > Is there something really wrong with my setup here? I have this machine > configured to dual boot with the other OS being the x64 version of XP, > and it reports a 2.2GHz CPU (for what it's worth...). You've some how gotten your Athlon64 processor in Cool-n-Quiet (ie, PowerNOW) cool, low-power mode. If you do a cold boot into FreeBSD, what CPU speed is reported? By chance is this a laptop and not a desktop. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 30 01:03:25 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A84716A4CE; Thu, 30 Dec 2004 01:03:25 +0000 (GMT) Received: from smtp1.adl2.internode.on.net (smtp1.adl2.internode.on.net [203.16.214.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 271B943D2F; Thu, 30 Dec 2004 01:03:24 +0000 (GMT) (envelope-from malcolm.kay@internode.on.net) Received: from beta.home (ppp35-138.lns1.adl1.internode.on.net [150.101.35.138])iBU137RF006846; Thu, 30 Dec 2004 11:33:08 +1030 (CST) From: Malcolm Kay Organization: at home To: Axel Gonzalez , Anton Berezin , "Michael W. Oliver" , Ruslan Ermilov , Roland Smith Date: Thu, 30 Dec 2004 11:33:07 +1030 User-Agent: KMail/1.5.4 References: <200412291647.05283.malcolm.kay@internode.on.net> In-Reply-To: <200412291647.05283.malcolm.kay@internode.on.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412301133.07296.malcolm.kay@internode.on.net> cc: freebsd-amd64@freebsd.org Subject: Re: Sound on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 01:03:25 -0000 Thanks guys; for the helpful responses. It is now working and zI have gained other useful info. Malcolm On Wed, 29 Dec 2004 04:47 pm, Malcolm Kay wrote: > I've just installed FreeBSD-5.3-amd64 on an Athlon64 3200 > and GA-K8VT800 motherboard. > > The kernel modules, in contradiction to the handbook, seem > not to contain any named snd_*. Nor can I find any clues in > /usr/src/sys/amd64/conf/NOTES on how the kernel or modules > for sound support are to be included. .. .. .. From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 30 04:45:06 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 09D2B16A4CE for ; Thu, 30 Dec 2004 04:45:06 +0000 (GMT) Received: from mxsf32.cluster1.charter.net (mxsf32.cluster1.charter.net [209.225.28.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id 921C243D1D for ; Thu, 30 Dec 2004 04:45:04 +0000 (GMT) (envelope-from tarkawebfoot@charter.net) Received: from mxip12.cluster1.charter.net (mxip12a.cluster1.charter.net [209.225.28.142])iBU4j324008581 for ; Wed, 29 Dec 2004 23:45:03 -0500 Received: from 66-169-225-54.or.charter.com (HELO [10.0.1.3]) (66.169.225.54) by mxip12.cluster1.charter.net with ESMTP; 29 Dec 2004 23:45:03 -0500 X-Ironport-AV: i="3.88,91,1102309200"; d="scan'208"; a="695910894:sNHT12834492" Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <20041228184926.GA69940@dragon.nuxi.com> References: <5B1511FA-5540-11D9-AF1F-000A95B96642@charter.net> <20041228184926.GA69940@dragon.nuxi.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <7BD5AFC2-595E-11D9-BE3E-000A95B96642@charter.net> Content-Transfer-Encoding: 7bit From: Brian Myers Date: Tue, 28 Dec 2004 21:57:12 -0800 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.619) Subject: Re: New board for a newbie X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 04:45:06 -0000 Yes, I realized I didn't mention how I was using it just after I posted. Surprised I got away with it this long. Initially it will be primarily a server machine. It will be a database/webserver/app server all-in-one box. Occasionally it will do some more hefty database and ETL work. I might want the AGP graphics card in it though, because eventually I may try to turn it into a video editing box running Cinnerella. For now, I'd like to keep the cost under $2K. Thanx Brian On Dec 28, 2004, at 10:49 AM, David O'Brien wrote: > On Thu, Dec 23, 2004 at 04:11:27PM -0800, Brian Myers wrote: >> 2) I've seen much conversation on which boards, memory, and SATA >> controllers were supported by FreeBSD. So much so that I have no idea >> what the current state of things is. So, if you were building a new >> dual Opteron from scratch, what would you get? For cost reasons, I'm >> going with 1.8 ghz processors and probably only 2GB of ram. I'll have >> two RAID 1 SATA hard drives, but should I use an onboard controller, >> or >> purchase a separate controller? Note that I may at some point upgrade >> to 4 RAID 0+1 disks. What about video cards? I don't need much so, are >> the onboard ones useable or not? Also, I, of course, would like the >> onboard LAN controller to be supported. > > You really don't mention the use of the machine -- server or > workstation > (or mix)? Do you need an AGP slot for high-end graphics, or is low-end > on-board VGA just fine? How many 64-bit PCI-X slots do you need? > > -- > -- David (obrien@FreeBSD.org) > From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 30 08:13:43 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BD1616A4CE for ; Thu, 30 Dec 2004 08:13:43 +0000 (GMT) Received: from mailout10.sul.t-online.com (mailout10.sul.t-online.com [194.25.134.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8F6343D53 for ; Thu, 30 Dec 2004 08:13:42 +0000 (GMT) (envelope-from mike@reifenberger.com) Received: from fwd04.aul.t-online.de by mailout10.sul.t-online.com with smtp id 1CjvRF-00065E-02; Thu, 30 Dec 2004 09:13:41 +0100 Received: from fw.reifenberger.com (ZY0b4eZbrebQXw-QFPfEtEaMiUM230KVP2FQHtK5PgROmJ9THihoQx@[62.158.167.50]) by fmrl04.sul.t-online.com with esmtp id 1CjvR2-2H7O8O0; Thu, 30 Dec 2004 09:13:28 +0100 Received: from localhost (mike@localhost)iBU8DM8k082573 for ; Thu, 30 Dec 2004 09:13:22 +0100 (CET) (envelope-from mike@reifenberger.com) X-Authentication-Warning: fw.reifenberger.com: mike owned process doing -bs Date: Thu, 30 Dec 2004 09:13:22 +0100 (CET) From: Michael Reifenberger To: freebsd-amd64@freebsd.org Message-ID: <20041230090557.I82461@fw.reifenberger.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-ID: ZY0b4eZbrebQXw-QFPfEtEaMiUM230KVP2FQHtK5PgROmJ9THihoQx@t-dialin.net X-TOI-MSGID: 651a006b-5839-4688-b18b-8137459dcaed Subject: Migrating i386 to amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 08:13:43 -0000 Hi, I currently have a intel-p4 board which I will replace by an Asus A8V one. At first it should run in i386 mode without problems. But how to migrate to amd64? Is it possible to cross compile amd64 kernel/userland on i386? Can I use amd64 kernel with i386 userland? Thanks in advance! Bye/2 --- Michael Reifenberger, Business Development Manager SAP-Basis, Plaut Consulting Comp: Michael.Reifenberger@plaut.de | Priv: Michael@Reifenberger.com http://www.plaut.de | http://www.Reifenberger.com From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 30 11:21:57 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6238016A4CE for ; Thu, 30 Dec 2004 11:21:57 +0000 (GMT) Received: from mail.lovett.com (core.lovett.com [216.168.8.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40FE243D5A for ; Thu, 30 Dec 2004 11:21:57 +0000 (GMT) (envelope-from ade@FreeBSD.org) Received: from 66-169-244-255.or.charter.com ([66.169.244.255] helo=[10.21.91.101]) by mail.lovett.com with esmtpa (Exim 4.43 (FreeBSD)) id 1CjyNR-0008Fj-6O; Thu, 30 Dec 2004 11:21:57 +0000 Message-ID: <41D3E4D4.2020403@FreeBSD.org> Date: Thu, 30 Dec 2004 03:21:56 -0800 From: Ade Lovett User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Reifenberger References: <20041230090557.I82461@fw.reifenberger.com> In-Reply-To: <20041230090557.I82461@fw.reifenberger.com> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Migrating i386 to amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 11:21:57 -0000 Michael Reifenberger wrote: > But how to migrate to amd64? 1. Back up your data 2. Insert native amd64 miniinst cdrom [a new 6-current snap has *just* gone up, so now's a great time] 3. boot, follow prompts. Having done both this option, and the heavily convoluted i386->amd64 option (mainly just for the bragging rights :) trust me when I say thaat steps 1-3 above are going to be considerably quicker, easier, more painless, etc. than anything else. Really. -aDe From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 30 12:15:37 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08D7B16A4CE for ; Thu, 30 Dec 2004 12:15:37 +0000 (GMT) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1F6443D2F for ; Thu, 30 Dec 2004 12:15:35 +0000 (GMT) (envelope-from a.degroot@science.ru.nl) Received: from odin.cs.kun.nl [131.174.33.33] (helo=odin.cs.kun.nl) by pandora.cs.kun.nl (8.12.10/4.23) with ESMTP id iBUCFYga001317 for ; Thu, 30 Dec 2004 13:15:34 +0100 (MET) Date: Thu, 30 Dec 2004 13:15:34 +0100 (MET) From: a.degroot@science.ru.nl X-X-Sender: adridg@odin.cs.kun.nl To: amd64@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: A cvsup without libm.so.2 ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: a.degroot@science.ru.nl List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 12:15:37 -0000 I'm updating some desktop machines here that went through the 5.3-BETA phase and hence have a libm.so.2 as well as a libm.so.3. Since there's no real reason to have a libm.so.2 (is there?), I'm trying to get rid of all references to it [1]. portupgrade -af mostly does the job, but I'm sort of stuck with cvsup. It's still binary-only, isn't it? The current packages of cvsup still link to libm.so.2, which is somewhat annoying. In particular, clean installs of 5.3 can't run cvsup. Can we get a libm.so.2-free cvsup sometime? [1] Yes, I realize there might not be a good reason to pitch it out, either, and /etc/libmap.conf will make it go away entirely. -- As of September 1st, 2004, the University of Nijmegen will _still_ be the University of Nijmegen, but with a different nonsensical adjective in front. Reach me at groot@kde.org instead. GPG FEA2 A3FE From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 30 13:46:27 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BF3716A4CE for ; Thu, 30 Dec 2004 13:46:27 +0000 (GMT) Received: from mail.freebsd.org.cn (dns3.freebsd.org.cn [61.129.66.75]) by mx1.FreeBSD.org (Postfix) with SMTP id D7E5543D41 for ; Thu, 30 Dec 2004 13:46:22 +0000 (GMT) (envelope-from delphij@frontfree.net) Received: (qmail 29447 invoked by uid 0); 30 Dec 2004 13:39:10 -0000 Received: from unknown (HELO beastie.frontfree.net) (219.239.99.7) by mail.freebsd.org.cn with SMTP; 30 Dec 2004 13:39:10 -0000 Received: from localhost (localhost.frontfree.net [127.0.0.1]) by beastie.frontfree.net (Postfix) with ESMTP id 49EE7131293; Thu, 30 Dec 2004 21:46:14 +0800 (CST) Received: from beastie.frontfree.net ([127.0.0.1]) by localhost (beastie.frontfree.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03808-05; Thu, 30 Dec 2004 21:46:00 +0800 (CST) Received: by beastie.frontfree.net (Postfix, from userid 1001) id 8BD82131041; Thu, 30 Dec 2004 21:45:59 +0800 (CST) Date: Thu, 30 Dec 2004 21:45:59 +0800 From: Xin LI To: a.degroot@science.ru.nl Message-ID: <20041230134559.GA3255@frontfree.net> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2oS5YaxWCcQjTEyO" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-GPG-key-ID/Fingerprint: 0xCAEEB8C0 / 43B8 B703 B8DD 0231 B333 DC28 39FB 93A0 CAEE B8C0 X-GPG-Public-Key: http://www.delphij.net/delphij.asc X-Operating-System: FreeBSD beastie.frontfree.net 5.3-delphij FreeBSD 5.3-delphij #11: Tue Oct 26 14:12:03 CST 2004 delphij@beastie.frontfree.net:/usr/obj/usr/src/sys/BEASTIE i386 X-URL: http://www.delphij.net X-By: delphij@beastie.frontfree.net X-Location: Beijing, China X-Virus-Scanned: by amavisd-new at frontfree.net cc: amd64@freebsd.org Subject: Re: A cvsup without libm.so.2 ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 13:46:27 -0000 --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 30, 2004 at 01:15:34PM +0100, a.degroot@science.ru.nl wrote: > I'm updating some desktop machines here that went through the 5.3-BETA > phase and hence have a libm.so.2 as well as a libm.so.3. Since there's no > real reason to have a libm.so.2 (is there?), I'm trying to get rid of all > references to it [1]. portupgrade -af mostly does the job, but I'm sort of > stuck with cvsup. It's still binary-only, isn't it? The current packages > of cvsup still link to libm.so.2, which is somewhat annoying. In > particular, clean installs of 5.3 can't run cvsup. Can we get a > libm.so.2-free cvsup sometime? >=20 >=20 > [1] Yes, I realize there might not be a good reason to pitch it out, > either, and /etc/libmap.conf will make it go away entirely. Maybe you want to try out the latest pointyhat build here: http://pointyhat.freebsd.org/errorlogs/amd64-5-packages-latest/net Cheers, --=20 Xin LI http://www.delphij.net/ See complete headers for GPG key and other information. --2oS5YaxWCcQjTEyO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB1AaX/cVsHxFZiIoRAm5TAJ4xuhoQqngn2jtP5dwco9yOF8CuKACcDG5z kVcCH2KJwTmPv90cgTlQN1s= =zUw2 -----END PGP SIGNATURE----- --2oS5YaxWCcQjTEyO-- From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 30 14:00:42 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D93816A4E7 for ; Thu, 30 Dec 2004 14:00:42 +0000 (GMT) Received: from phoenix.gargantuan.com (phoenix.gargantuan.com [24.73.171.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB7D943D45 for ; Thu, 30 Dec 2004 14:00:41 +0000 (GMT) (envelope-from michael@gargantuan.com) Received: from localhost (localhost.gargantuan.com [127.0.0.1]) by spamassassin-injector (Postfix) with SMTP id C91C7744 for ; Thu, 30 Dec 2004 09:00:40 -0500 (EST) Received: by phoenix.gargantuan.com (Postfix, from userid 1001) id 16D114D2; Thu, 30 Dec 2004 09:00:22 -0500 (EST) Date: Thu, 30 Dec 2004 09:00:22 -0500 From: "Michael W. Oliver" To: freebsd-amd64@freebsd.org Message-ID: <20041230140022.GC59271@gargantuan.com> References: <20041229212555.GD89526@gargantuan.com> <20041230005738.GD68336@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SLDf9lqlvOQaIe6s" Content-Disposition: inline In-Reply-To: <20041230005738.GD68336@dragon.nuxi.com> X-WWW-Site: http://michael.gargantuan.com X-PGP-Public-Key: $X-WWW-Site/gnupg/pubkey.asc X-PGP-Fingerprint: 2694 0179 AE3F BFAE 0916 0BF5 B16B FBAB C5FA A3C9 X-Home-Phone: +1-863-816-8091 X-Mobile-Phone: +1-863-738-2334 X-Home-Address0: 8008 Apache Lane X-Home-Address1: Lakeland, FL X-Home-Address2: 33810-2172 X-Home-Address3: United States of America X-Good-Question-Guide: http://www.catb.org/~esr/faqs/smart-questions.html X-Netiquette-Guidelines: http://www.ietf.org/rfc/rfc1855.txt User-Agent: Mutt/1.5.6i X-Spam-DCC: MC: phoenix.gargantuan.com 1128; Body=1 Fuz1=1 Fuz2=1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on phoenix.gargantuan.com X-Spam-Level: X-Spam-Status: No, score=-105.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, USER_IN_WHITELIST autolearn=ham version=3.0.1 X-Spam-Pyzor: Reported 0 times. Subject: Re: CPU speed not reported correctly X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 14:00:42 -0000 --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004-12-29T16:57:38-0800, David O'Brien wrote: > On Wed, Dec 29, 2004 at 04:25:55PM -0500, Michael W. Oliver wrote: > > CPU: AMD Athlon(tm) 64 Processor 3400+ (801.83-MHz K8-class CPU) > . > > OK, here is my question: Why is the CPU speed reported as 801.83MHz? > > Is there something really wrong with my setup here? I have this machine > > configured to dual boot with the other OS being the x64 version of XP, > > and it reports a 2.2GHz CPU (for what it's worth...). > You've some how gotten your Athlon64 processor in Cool-n-Quiet (ie, > PowerNOW) cool, low-power mode. If you do a cold boot into FreeBSD, what > CPU speed is reported? By chance is this a laptop and not a desktop. Thanks for the reply David. When booting cold, the same speed is reported -- 801.83-MHz. Yes, this is a laptop (Sager 4750-V). entire output of `dmesg -a': http://michael.gargantuan.com/yabbse/index.php?action=3Ddlattach;topic=3D30= 9.0;id=3D17 other info about this laptop: http://michael.gargantuan.com/yabbse/index.php/board,44.0.html --=20 Michael W. Oliver [see complete headers for contact information] --SLDf9lqlvOQaIe6s Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB1An1sWv7q8X6o8kRAv3fAJ9Ofl2X2Qv0tTFdtcYYnp1PrtmbeQCgrB22 YtujIcWdPLIIqmwRE4iVcaE= =e2Td -----END PGP SIGNATURE----- --SLDf9lqlvOQaIe6s-- From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 30 14:53:00 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1ADA616A4CE for ; Thu, 30 Dec 2004 14:53:00 +0000 (GMT) Received: from smtp104.rog.mail.re2.yahoo.com (smtp104.rog.mail.re2.yahoo.com [206.190.36.82]) by mx1.FreeBSD.org (Postfix) with SMTP id 7D04E43D45 for ; Thu, 30 Dec 2004 14:52:59 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from unknown (HELO cpe000103d44c07-cm000f9f7ae88c.cpe.net.cable.rogers.com) (mikej@69.193.222.195 with login) by smtp104.rog.mail.re2.yahoo.com with SMTP; 30 Dec 2004 14:52:58 -0000 Received: from 207.219.213.163 (proxying for unknown) (SquirrelMail authenticated user mikej); by cpe000103d44c07-cm000f9f7ae88c.cpe.net.cable.rogers.com with HTTP; Thu, 30 Dec 2004 09:52:51 -0500 (EST) Message-ID: <58083.207.219.213.163.1104418371.squirrel@207.219.213.163> In-Reply-To: <20041230140022.GC59271@gargantuan.com> References: <20041229212555.GD89526@gargantuan.com> <20041230005738.GD68336@dragon.nuxi.com> <20041230140022.GC59271@gargantuan.com> Date: Thu, 30 Dec 2004 09:52:51 -0500 (EST) From: "Mike Jakubik" To: "Michael W. Oliver" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal cc: freebsd-amd64@freebsd.org Subject: Re: CPU speed not reported correctly X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 14:53:00 -0000 Michael W. Oliver said: > When booting cold, the same speed is reported -- 801.83-MHz. Yes, this > is a laptop (Sager 4750-V). > > entire output of `dmesg -a': > http://michael.gargantuan.com/yabbse/index.php?action=dlattach;topic=309.0;id=17 > > other info about this laptop: > http://michael.gargantuan.com/yabbse/index.php/board,44.0.html This is normal for AMD laptops. I have an Emachine M5310, and the CPU speed varies on it. If i right click on my computer in Windows XP, the reported frequency is almost always different. Strangely enough in FreeBSD its always the max though, i belive this technology may require a proper driver for the frequency to be adjusted. I would check your BIOS settings. From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 30 15:14:39 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E52C16A4CE for ; Thu, 30 Dec 2004 15:14:39 +0000 (GMT) Received: from phoenix.gargantuan.com (phoenix.gargantuan.com [24.73.171.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9B5643D55 for ; Thu, 30 Dec 2004 15:14:38 +0000 (GMT) (envelope-from michael@gargantuan.com) Received: from localhost (localhost.gargantuan.com [127.0.0.1]) by spamassassin-injector (Postfix) with SMTP id 0216A52F; Thu, 30 Dec 2004 10:14:37 -0500 (EST) Received: by phoenix.gargantuan.com (Postfix, from userid 1001) id B0350334; Thu, 30 Dec 2004 10:14:23 -0500 (EST) Date: Thu, 30 Dec 2004 10:14:23 -0500 From: "Michael W. Oliver" To: Mike Jakubik Message-ID: <20041230151423.GD59271@gargantuan.com> References: <20041229212555.GD89526@gargantuan.com> <20041230005738.GD68336@dragon.nuxi.com> <20041230140022.GC59271@gargantuan.com> <58083.207.219.213.163.1104418371.squirrel@207.219.213.163> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IrhDeMKUP4DT/M7F" Content-Disposition: inline In-Reply-To: <58083.207.219.213.163.1104418371.squirrel@207.219.213.163> X-WWW-Site: http://michael.gargantuan.com X-PGP-Public-Key: $X-WWW-Site/gnupg/pubkey.asc X-PGP-Fingerprint: 2694 0179 AE3F BFAE 0916 0BF5 B16B FBAB C5FA A3C9 X-Home-Phone: +1-863-816-8091 X-Mobile-Phone: +1-863-738-2334 X-Home-Address0: 8008 Apache Lane X-Home-Address1: Lakeland, FL X-Home-Address2: 33810-2172 X-Home-Address3: United States of America X-Good-Question-Guide: http://www.catb.org/~esr/faqs/smart-questions.html X-Netiquette-Guidelines: http://www.ietf.org/rfc/rfc1855.txt User-Agent: Mutt/1.5.6i X-Spam-DCC: EATSERVER: phoenix.gargantuan.com 1166; Body=1 Fuz1=1 Fuz2=1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on phoenix.gargantuan.com X-Spam-Level: X-Spam-Status: No, score=-105.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, USER_IN_WHITELIST autolearn=ham version=3.0.1 X-Spam-Pyzor: Reported 0 times. cc: freebsd-amd64@freebsd.org Subject: Re: CPU speed not reported correctly X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 15:14:39 -0000 --IrhDeMKUP4DT/M7F Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004-12-30T09:52:51-0500, Mike Jakubik wrote: > Michael W. Oliver said: > > When booting cold, the same speed is reported -- 801.83-MHz. Yes, this > > is a laptop (Sager 4750-V). > > entire output of `dmesg -a': > > http://michael.gargantuan.com/yabbse/index.php?action=3Ddlattach;topic= =3D309.0;id=3D17 > > other info about this laptop: > > http://michael.gargantuan.com/yabbse/index.php/board,44.0.html > This is normal for AMD laptops. I have an Emachine M5310, and the CPU > speed varies on it. If i right click on my computer in Windows XP, the > reported frequency is almost always different. Strangely enough in FreeBSD > its always the max though, i belive this technology may require a proper > driver for the frequency to be adjusted. I would check your BIOS settings. Thanks Mike. The BIOS on this laptop is unusually sparse, and I don't see any options with regards to the CPU. So, is there something deep inside this machine, either in BIOS or CPU or ??? that throttles the CPU based on load? I have noticed that the fan speed goes up and down depending on what I am doing. I don't see any throttling stuff in `sysctl hw.acpi' like I do on my P2 laptop, so does that mean that CPU throttling is not something that I can control? Also, since the throttling seems to be out of my hands, is it possible that the CPU is actually running at 2.2GHz when it needs to, depending on load? I know that amd64 is a growth area, and I don't expect it to be as rich as i386 is... yet. I am not a programmer, but I follow directions pretty well and am willing to help further FreeBSD's amd64 support in any way that I can. --=20 Michael W. Oliver [see complete headers for contact information] --IrhDeMKUP4DT/M7F Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB1BtPsWv7q8X6o8kRAv/zAKDBehJzcyHDUCW6hLr3je47lzDwegCfUBty 5LAJfJiLoI2PTDrUtTaQzls= =/vz/ -----END PGP SIGNATURE----- --IrhDeMKUP4DT/M7F-- From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 30 16:46:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 33E3316A4CE for ; Thu, 30 Dec 2004 16:46:56 +0000 (GMT) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF1D243D41 for ; Thu, 30 Dec 2004 16:46:55 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01 ([66.130.198.54]) by VL-MO-MR011.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id <0I9J007ATNXZAQ@VL-MO-MR011.ip.videotron.ca> for freebsd-amd64@freebsd.org; Thu, 30 Dec 2004 11:46:48 -0500 (EST) Date: Thu, 30 Dec 2004 11:46:48 -0500 From: Nicolas Blais In-reply-to: <58083.207.219.213.163.1104418371.squirrel@207.219.213.163> To: freebsd-amd64@freebsd.org Message-id: <200412301146.49669.nb_root@videotron.ca> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: KMail/1.7.2 References: <20041229212555.GD89526@gargantuan.com> <20041230140022.GC59271@gargantuan.com> <58083.207.219.213.163.1104418371.squirrel@207.219.213.163> Subject: Re: CPU speed not reported correctly X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 16:46:56 -0000 This is because AMD uses PowerNOW! technology which changes the voltage (therefore the speed) of the cpu for the load it gets. Nick. On December 30, 2004 09:52, Mike Jakubik wrote: > Michael W. Oliver said: > > When booting cold, the same speed is reported -- 801.83-MHz. Yes, this > > is a laptop (Sager 4750-V). > > > > entire output of `dmesg -a': > > http://michael.gargantuan.com/yabbse/index.php?action=dlattach;topic=309. > >0;id=17 > > > > other info about this laptop: > > http://michael.gargantuan.com/yabbse/index.php/board,44.0.html > > This is normal for AMD laptops. I have an Emachine M5310, and the CPU > speed varies on it. If i right click on my computer in Windows XP, the > reported frequency is almost always different. Strangely enough in FreeBSD > its always the max though, i belive this technology may require a proper > driver for the frequency to be adjusted. I would check your BIOS settings. > > > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 30 18:12:29 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BCF8E16A4CE for ; Thu, 30 Dec 2004 18:12:29 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A7A743D2F for ; Thu, 30 Dec 2004 18:12:29 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 21362 invoked from network); 30 Dec 2004 18:12:28 -0000 Received: from gate.funkthat.com (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail4.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 30 Dec 2004 18:12:28 -0000 Received: from hydrogen.funkthat.com (ojuzmj@localhost.funkthat.com [127.0.0.1])iBUICSGH082562; Thu, 30 Dec 2004 10:12:28 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id iBUICS1d082561; Thu, 30 Dec 2004 10:12:28 -0800 (PST) Date: Thu, 30 Dec 2004 10:12:28 -0800 From: John-Mark Gurney To: Nicolas Blais Message-ID: <20041230181227.GR19624@funkthat.com> Mail-Followup-To: Nicolas Blais , freebsd-amd64@freebsd.org References: <20041229212555.GD89526@gargantuan.com> <20041230140022.GC59271@gargantuan.com> <58083.207.219.213.163.1104418371.squirrel@207.219.213.163> <200412301146.49669.nb_root@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200412301146.49669.nb_root@videotron.ca> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: freebsd-amd64@freebsd.org Subject: Re: CPU speed not reported correctly X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Dec 2004 18:12:29 -0000 Nicolas Blais wrote this message on Thu, Dec 30, 2004 at 11:46 -0500: > This is because AMD uses PowerNOW! technology which changes the voltage > (therefore the speed) of the cpu for the load it gets. just for clarification, changed the voltage does not imply a change of the speed, it just means that at slower clock rates, it can reduce the voltage for the chip since the transistors don't need to switch as quickly.. > On December 30, 2004 09:52, Mike Jakubik wrote: > > Michael W. Oliver said: > > > When booting cold, the same speed is reported -- 801.83-MHz. Yes, this > > > is a laptop (Sager 4750-V). > > > > > > entire output of `dmesg -a': > > > http://michael.gargantuan.com/yabbse/index.php?action=dlattach;topic=309. > > >0;id=17 > > > > > > other info about this laptop: > > > http://michael.gargantuan.com/yabbse/index.php/board,44.0.html > > > > This is normal for AMD laptops. I have an Emachine M5310, and the CPU > > speed varies on it. If i right click on my computer in Windows XP, the > > reported frequency is almost always different. Strangely enough in FreeBSD > > its always the max though, i belive this technology may require a proper > > driver for the frequency to be adjusted. I would check your BIOS settings. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 31 00:37:21 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1F6416A4CE for ; Fri, 31 Dec 2004 00:37:21 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id C269143D1F for ; Fri, 31 Dec 2004 00:37:21 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iBV0bLRN029472; Thu, 30 Dec 2004 16:37:21 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iBV0bK8Y029470; Thu, 30 Dec 2004 16:37:20 -0800 (PST) (envelope-from obrien) Date: Thu, 30 Dec 2004 16:37:20 -0800 From: "David O'Brien" To: "Michael W. Oliver" Message-ID: <20041231003720.GA29434@dragon.nuxi.com> References: <20041229212555.GD89526@gargantuan.com> <20041230005738.GD68336@dragon.nuxi.com> <20041230140022.GC59271@gargantuan.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041230140022.GC59271@gargantuan.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: CPU speed not reported correctly X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2004 00:37:22 -0000 On Thu, Dec 30, 2004 at 09:00:22AM -0500, Michael W. Oliver wrote: > On 2004-12-29T16:57:38-0800, David O'Brien wrote: > > On Wed, Dec 29, 2004 at 04:25:55PM -0500, Michael W. Oliver wrote: > > > CPU: AMD Athlon(tm) 64 Processor 3400+ (801.83-MHz K8-class CPU) > > . > > > OK, here is my question: Why is the CPU speed reported as 801.83MHz? > > > Is there something really wrong with my setup here? I have this machine > > > configured to dual boot with the other OS being the x64 version of XP, > > > and it reports a 2.2GHz CPU (for what it's worth...). > > > You've some how gotten your Athlon64 processor in Cool-n-Quiet (ie, > > PowerNOW) cool, low-power mode. If you do a cold boot into FreeBSD, what > > CPU speed is reported? By chance is this a laptop and not a desktop. > > Thanks for the reply David. > > When booting cold, the same speed is reported -- 801.83-MHz. Yes, this > is a laptop (Sager 4750-V). This is normal behavior for many laptops then -- they start up in low-power mode. I've been waiting for the FreeBSD power-freqency control framework to hit the tree before adding AMD64 Cool-n-Quiet support. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 31 00:39:51 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1156316A4CE for ; Fri, 31 Dec 2004 00:39:51 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF7B643D39 for ; Fri, 31 Dec 2004 00:39:50 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iBV0dnex029581; Thu, 30 Dec 2004 16:39:49 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iBV0dknK029580; Thu, 30 Dec 2004 16:39:46 -0800 (PST) (envelope-from obrien) Date: Thu, 30 Dec 2004 16:39:46 -0800 From: "David O'Brien" To: a.degroot@science.ru.nl Message-ID: <20041231003946.GB29434@dragon.nuxi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@freebsd.org Subject: Re: A cvsup without libm.so.2 ? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@freebsd.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2004 00:39:51 -0000 On Thu, Dec 30, 2004 at 01:15:34PM +0100, a.degroot@science.ru.nl wrote: > I'm updating some desktop machines here that went through the 5.3-BETA > phase and hence have a libm.so.2 as well as a libm.so.3. Since there's no > real reason to have a libm.so.2 (is there?), I'm trying to get rid of all > references to it [1]. portupgrade -af mostly does the job, but I'm sort of > stuck with cvsup. It's still binary-only, isn't it? The current packages > of cvsup still link to libm.so.2, which is somewhat annoying. In > particular, clean installs of 5.3 can't run cvsup. Can we get a > libm.so.2-free cvsup sometime? You may easily need libm.so.2 for running other 5.3 binaries on 6-CURRENT. I would move libm.so.2 to /usr/lib/compat and keep on running the cvsup you have now. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 31 04:44:47 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8DAF16A4CE; Fri, 31 Dec 2004 04:44:47 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F2F143D1F; Fri, 31 Dec 2004 04:44:47 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id iBV4ikSK090197; Thu, 30 Dec 2004 23:44:46 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.1/8.13.1) with ESMTP id iBV4ik8c081958; Thu, 30 Dec 2004 23:44:46 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 7FA817306E; Thu, 30 Dec 2004 23:44:46 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041231044446.7FA817306E@freebsd-current.sentex.ca> Date: Thu, 30 Dec 2004 23:44:46 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/640/Thu Dec 23 13:48:27 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Status: Clean Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2004 04:44:47 -0000 TB --- 2004-12-31 03:06:28 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-12-31 03:06:28 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-12-31 03:06:28 - checking out the source tree TB --- 2004-12-31 03:06:28 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2004-12-31 03:06:28 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-12-31 03:12:29 - building world (CFLAGS=-O2 -pipe) TB --- 2004-12-31 03:12:29 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-12-31 03:12:29 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-12-31 04:19:31 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-12-31 04:19:31 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-12-31 04:19:31 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Dec 31 04:19:31 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Fri Dec 31 04:34:11 UTC 2004 TB --- 2004-12-31 04:34:12 - generating LINT kernel config TB --- 2004-12-31 04:34:12 - cd /home/tinderbox/CURRENT/amd64/amd64/src/sys/amd64/conf TB --- 2004-12-31 04:34:12 - /usr/bin/make -B LINT TB --- 2004-12-31 04:34:12 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-12-31 04:34:12 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-12-31 04:34:12 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Dec 31 04:34:12 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/a md64/amd64/src/sys/netinet6/udp6_output.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/a md64/amd64/src/sys/netinet6/udp6_usrreq.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/a md64/amd64/src/sys/netipx/ipx.c In file included from /tinderbox/CURRENT/amd64/amd64/src/sys/netipx/ipx.c:52: /tinderbox/CURRENT/amd64/amd64/src/sys/netipx/ipx_var.h:88: warning: "struct ipxpcb" declared inside parameter list /tinderbox/CURRENT/amd64/amd64/src/sys/netipx/ipx_var.h:88: warning: its scope is only this definition or declaration, which is probably not what you want /tinderbox/CURRENT/amd64/amd64/src/sys/netipx/ipx_var.h:94: warning: "struct ipxpcb" declared inside parameter list /tinderbox/CURRENT/amd64/amd64/src/sys/netipx/ipx_var.h:96: warning: "struct ipxpcb" declared inside parameter list *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/LINT. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-12-31 04:44:46 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-12-31 04:44:46 - ERROR: failed to build lint kernel TB --- 2004-12-31 04:44:46 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 31 08:45:14 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07FCA16A4CE; Fri, 31 Dec 2004 08:45:14 +0000 (GMT) Received: from mailout11.sul.t-online.com (mailout11.sul.t-online.com [194.25.134.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6703243D46; Fri, 31 Dec 2004 08:45:13 +0000 (GMT) (envelope-from mike@reifenberger.com) Received: from fwd10.aul.t-online.de by mailout11.sul.t-online.com with smtp id 1CkIPI-0001kv-01; Fri, 31 Dec 2004 09:45:12 +0100 Received: from fw.reifenberger.com (bjeafwZXreqYCfyvjfUqigEikNA9tLOYuz6WtOEDvbPl3xT7hb0OgT@[62.158.166.253]) by fmrl10.sul.t-online.com with esmtp id 1CkIP1-1VpnjU0; Fri, 31 Dec 2004 09:44:55 +0100 Received: from localhost (mike@localhost)iBV8inWM087781; Fri, 31 Dec 2004 09:44:49 +0100 (CET) (envelope-from mike@reifenberger.com) X-Authentication-Warning: fw.reifenberger.com: mike owned process doing -bs Date: Fri, 31 Dec 2004 09:44:49 +0100 (CET) From: Michael Reifenberger To: Ade Lovett In-Reply-To: <41D3E4D4.2020403@FreeBSD.org> Message-ID: <20041231094258.Y87761@fw.reifenberger.com> References: <20041230090557.I82461@fw.reifenberger.com> <41D3E4D4.2020403@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-ID: bjeafwZXreqYCfyvjfUqigEikNA9tLOYuz6WtOEDvbPl3xT7hb0OgT@t-dialin.net X-TOI-MSGID: c7bfdf7a-8d64-4195-b996-2eb5829c92b0 cc: freebsd-amd64@freebsd.org Subject: Re: Migrating i386 to amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2004 08:45:14 -0000 On Thu, 30 Dec 2004, Ade Lovett wrote: ... > 1. Back up your data > 2. Insert native amd64 miniinst cdrom > [a new 6-current snap has *just* gone up, so now's a great time] > 3. boot, follow prompts. > > Having done both this option, and the heavily convoluted i386->amd64 option > (mainly just for the bragging rights :) trust me when I say thaat steps 1-3 > above are going to be considerably quicker, easier, more painless, etc. than > anything else. > Thanks! Will do. Do my old i386 ports (like X etc) work under amd64? Bye/2 --- Michael Reifenberger, Business Development Manager SAP-Basis, Plaut Consulting Comp: Michael.Reifenberger@plaut.de | Priv: Michael@Reifenberger.com http://www.plaut.de | http://www.Reifenberger.com From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 31 13:47:55 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2D6416A4CE for ; Fri, 31 Dec 2004 13:47:55 +0000 (GMT) Received: from svr1.16o.com (svr1.16o.com [69.50.175.34]) by mx1.FreeBSD.org (Postfix) with SMTP id A31D743D31 for ; Fri, 31 Dec 2004 13:47:55 +0000 (GMT) (envelope-from neil@mpfspromotions.com) Received: (qmail 35899 invoked from network); 31 Dec 2004 13:49:16 -0000 Received: from unknown (HELO HOME) (195.137.35.72) by 0 with SMTP; 31 Dec 2004 13:49:16 -0000 From: "Neil Doody" To: Date: Fri, 31 Dec 2004 13:50:10 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcTvP6UmC4xA+PK+R4OIwpIybJHb4g== Message-Id: <20041231134755.A31D743D31@mx1.FreeBSD.org> Subject: Server hanging after few days X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2004 13:47:55 -0000 Hi, got the FreeBSD AMD64 5.3R OS installed on an AMD64 system, it works fine except after a few days it seems to hang, I then have to log onto the APC and send a hard reboot before I can get back into it? I look in the /var/log/messages at the end and don't see any kind of kernel panics or any reason why I can't get back into the system. The system is at a remote location, hosted in a data centre so I cannot look at the console, though I may have to put in a request for a technician to look at it for me next time. Has anyone else experienced such hanging from there AMD64 implementation of FreeBSD? Vital signs:- FreeBSD svr1.16o.com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Thu Dec 2 01:16:45 UTC 2004 toor@svr1.16o.com:/usr/src/sys/amd64/compile/SVR1 amd64 CPU: AMD Athlon(tm) 64 Processor 3000+ (1800.08-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x10ff0 Stepping = 0 Features=0x78bfbff AMD Features=0xe2500800,LM,3DNow+,3DNow> From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 31 13:53:39 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07F8516A4CE for ; Fri, 31 Dec 2004 13:53:39 +0000 (GMT) Received: from svr1.16o.com (svr1.16o.com [69.50.175.34]) by mx1.FreeBSD.org (Postfix) with SMTP id CD37043D45 for ; Fri, 31 Dec 2004 13:53:38 +0000 (GMT) (envelope-from neil@mpfspromotions.com) Received: (qmail 36132 invoked from network); 31 Dec 2004 13:54:59 -0000 Received: from unknown (HELO HOME) (195.137.35.72) by 0 with SMTP; 31 Dec 2004 13:54:59 -0000 From: "Neil Doody" Sender: "Neil Doody" To: Date: Fri, 31 Dec 2004 13:55:54 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcTvP6UmC4xA+PK+R4OIwpIybJHb4g== Message-Id: <20041231135338.CD37043D45@mx1.FreeBSD.org> Subject: Server hanging after few days X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2004 13:53:39 -0000 Hi, got the FreeBSD AMD64 5.3R OS installed on an AMD64 system, it works fine except after a few days it seems to hang, I then have to log onto the APC and send a hard reboot before I can get back into it? I look in the /var/log/messages at the end and don't see any kind of kernel panics or any reason why I can't get back into the system. The system is at a remote location, hosted in a data centre so I cannot look at the console, though I may have to put in a request for a technician to look at it for me next time. Has anyone else experienced such hanging from there AMD64 implementation of FreeBSD? Vital signs:- FreeBSD svr1.16o.com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Thu Dec 2 01:16:45 UTC 2004 toor@svr1.16o.com:/usr/src/sys/amd64/compile/SVR1 amd64 CPU: AMD Athlon(tm) 64 Processor 3000+ (1800.08-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x10ff0 Stepping = 0 Features=0x78bfbff AMD Features=0xe2500800,LM,3DNow+,3DNow> From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 31 18:37:35 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C7B916A4CE for ; Fri, 31 Dec 2004 18:37:35 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE0EE43D45 for ; Fri, 31 Dec 2004 18:37:34 +0000 (GMT) (envelope-from java.public@gmail.com) Received: by rproxy.gmail.com with SMTP id z35so185409rne for ; Fri, 31 Dec 2004 10:37:34 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=jBED5nCdfqXoEWUS8gQ/Z0PYaJZFz8dV6z9qecLU1MjuW2ER0rqSXRfBIj3Sw3h2pEPPj/R64GO/ChA0yxjCy+jehdmgcpVWUADHuN2culVcgE4AqX7400GlO3u0P/jnu4uUQHWrL2xLPP86I7cddIBlQYn9vdAIn2zs2selRko= Received: by 10.39.3.9 with SMTP id f9mr153168rni; Fri, 31 Dec 2004 10:37:34 -0800 (PST) Received: by 10.38.126.4 with HTTP; Fri, 31 Dec 2004 10:37:33 -0800 (PST) Message-ID: Date: Fri, 31 Dec 2004 19:37:33 +0100 From: Java News To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: ASUS K8V SE + onboard sound recording X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Java News List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2004 18:37:35 -0000 Hi, I have a problem with my FreeBSD 5.3 workstation - based on ASUS K8V SE, AMD64 3000+, works nearly perfect for me but today I had to record some messages, and just couldn't. Soundcard is configured and works fine xmms plays, PSI beeps on message - output from kldstat: 3 1 0xc0973000 47dc snd_via8233.ko 4 2 0xc0978000 1d4fc sound.ko ps -ax | grep artsd 741 ?? S 1:02.20 artsd -F 10 -S 4096 -a oss -s 60 -m artsmessage -c drkonqi -l 3 -f KDE 3.3 on fresh Xorg, I put microphone (tested & working) into pink jack, I run KRec, I run KMix in KMix I choose microphone and in KRec start to record - no sound record was done. Anyone can help me with this? Anyone use microphone with succes on ASUS K8V SE? Any help would be great. Thx in advance and Happy New Year :) Lee From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 31 19:57:38 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD22716A4CE for ; Fri, 31 Dec 2004 19:57:38 +0000 (GMT) Received: from mail.lovett.com (core.lovett.com [216.168.8.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3C0A43D2D for ; Fri, 31 Dec 2004 19:57:38 +0000 (GMT) (envelope-from ade@FreeBSD.org) Received: from 66-169-244-255.or.charter.com ([66.169.244.255] helo=[10.21.91.101]) by mail.lovett.com with esmtpa (Exim 4.43 (FreeBSD)) id 1CkSu2-000IJf-LK; Fri, 31 Dec 2004 19:57:38 +0000 Message-ID: <41D5AF31.7050903@FreeBSD.org> Date: Fri, 31 Dec 2004 11:57:37 -0800 From: Ade Lovett User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Reifenberger References: <20041230090557.I82461@fw.reifenberger.com> <41D3E4D4.2020403@FreeBSD.org> <20041231094258.Y87761@fw.reifenberger.com> In-Reply-To: <20041231094258.Y87761@fw.reifenberger.com> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: Migrating i386 to amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2004 19:57:38 -0000 Michael Reifenberger wrote: > On Thu, 30 Dec 2004, Ade Lovett wrote: > ... > >> 1. Back up your data >> 2. Insert native amd64 miniinst cdrom [snip] > Do my old i386 ports (like X etc) work under amd64? Simple answer. No. Steps (1) and (2) above are implying a complete binary system reinstall. Part of the data you should probably be backing up is a list of installed packages so you can put the amd64 ones back in after installing kernel+userland. -aDe From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 31 21:17:23 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 174DE16A4CE; Fri, 31 Dec 2004 21:17:23 +0000 (GMT) Received: from mailout02.sul.t-online.com (mailout02.sul.t-online.com [194.25.134.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 945CA43D31; Fri, 31 Dec 2004 21:17:22 +0000 (GMT) (envelope-from mike@reifenberger.com) Received: from fwd08.aul.t-online.de by mailout02.sul.t-online.com with smtp id 1CkU9B-0000AL-01; Fri, 31 Dec 2004 22:17:21 +0100 Received: from fw.reifenberger.com (bVIELcZL8eVPNhmurRIZA9SZWzZBXxjyYwuJUNUPfdFVbMs5hDEn8S@[62.158.166.253]) by fmrl08.sul.t-online.com with esmtp id 1CkU98-1kenBI0; Fri, 31 Dec 2004 22:17:18 +0100 Received: from localhost (mike@localhost)iBVLHHiE090533; Fri, 31 Dec 2004 22:17:17 +0100 (CET) (envelope-from mike@reifenberger.com) X-Authentication-Warning: fw.reifenberger.com: mike owned process doing -bs Date: Fri, 31 Dec 2004 22:17:17 +0100 (CET) From: Michael Reifenberger To: Ade Lovett In-Reply-To: <41D5AF31.7050903@FreeBSD.org> Message-ID: <20041231221342.E90486@fw.reifenberger.com> References: <20041230090557.I82461@fw.reifenberger.com> <41D3E4D4.2020403@FreeBSD.org><41D5AF31.7050903@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-ID: bVIELcZL8eVPNhmurRIZA9SZWzZBXxjyYwuJUNUPfdFVbMs5hDEn8S@t-dialin.net X-TOI-MSGID: f5bd3613-28b6-4c6b-9427-b6e709f28cb0 cc: freebsd-amd64@FreeBSD.org Subject: Re: Migrating i386 to amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2004 21:17:23 -0000 On Fri, 31 Dec 2004, Ade Lovett wrote: ... >> Do my old i386 ports (like X etc) work under amd64? > > Simple answer. No. Steps (1) and (2) above are implying a complete binary > system reinstall. Part of the data you should probably be backing up is a > list of installed packages so you can put the amd64 ones back in after > installing kernel+userland. > Autsch. Thats what I didn't want to hear. Thanks anyway! BTW: Do I have any benefit of using this hardware (2GB RAM) with amd64 in favour of i386 (besides a bigger virtual address space)? Bye/2 --- Michael Reifenberger, Business Development Manager SAP-Basis, Plaut Consulting Comp: Michael.Reifenberger@plaut.de | Priv: Michael@Reifenberger.com http://www.plaut.de | http://www.Reifenberger.com From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 31 22:02:38 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD6D516A4CE for ; Fri, 31 Dec 2004 22:02:38 +0000 (GMT) Received: from mail.lovett.com (core.lovett.com [216.168.8.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id B738443D2F for ; Fri, 31 Dec 2004 22:02:38 +0000 (GMT) (envelope-from ade@FreeBSD.org) Received: from 66-169-244-255.or.charter.com ([66.169.244.255] helo=[10.21.91.101]) by mail.lovett.com with esmtpa (Exim 4.43 (FreeBSD)) id 1CkUr0-000J1L-Lf; Fri, 31 Dec 2004 22:02:38 +0000 Message-ID: <41D5CC74.4050906@FreeBSD.org> Date: Fri, 31 Dec 2004 14:02:28 -0800 From: Ade Lovett User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Reifenberger References: <20041230090557.I82461@fw.reifenberger.com> <41D3E4D4.2020403@FreeBSD.org><41D5AF31.7050903@FreeBSD.org> <20041231221342.E90486@fw.reifenberger.com> In-Reply-To: <20041231221342.E90486@fw.reifenberger.com> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@FreeBSD.org Subject: Re: Migrating i386 to amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2004 22:02:38 -0000 Michael Reifenberger wrote: > BTW: Do I have any benefit of using this hardware (2GB RAM) with amd64 > in favour of i386 (besides a bigger virtual address space)? Perhaps a more pertinent question is why y'all shelled out the extra cash for an amd64 chip as opposed to a 32-bit processor. What benefits were you expecting? -aDe From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 31 22:13:49 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 82CBA16A4CE for ; Fri, 31 Dec 2004 22:13:49 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5472243D41 for ; Fri, 31 Dec 2004 22:13:49 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iBVMDmXT015656; Fri, 31 Dec 2004 14:13:48 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iBVMDlQ2015655; Fri, 31 Dec 2004 14:13:47 -0800 (PST) (envelope-from obrien) Date: Fri, 31 Dec 2004 14:13:47 -0800 From: "David O'Brien" To: Michael Reifenberger Message-ID: <20041231221347.GA1467@dragon.nuxi.com> References: <20041230090557.I82461@fw.reifenberger.com> <20041231221342.E90486@fw.reifenberger.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041231221342.E90486@fw.reifenberger.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@FreeBSD.org Subject: Re: Migrating i386 to amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Dec 2004 22:13:49 -0000 On Fri, Dec 31, 2004 at 10:17:17PM +0100, Michael Reifenberger wrote: > On Fri, 31 Dec 2004, Ade Lovett wrote: > ... > >>Do my old i386 ports (like X etc) work under amd64? > > > >Simple answer. No. Steps (1) and (2) above are implying a complete > >binary system reinstall. Part of the data you should probably be backing > >up is a list of installed packages so you can put the amd64 ones back in > >after installing kernel+userland. > > > > Autsch. > Thats what I didn't want to hear. > Thanks anyway! > > BTW: Do I have any benefit of using this hardware (2GB RAM) with amd64 > in favour of i386 (besides a bigger virtual address space)? Yes. A 64-bit kernel is often more efficient because so many of the kernel data structures these days are 64-bit counters, etc.. Also the AMD64 ABI has 8 more general purpose registers, which gives the compiler a lot more to work with in optimizing and allows parameters to be passed thru registers vs. the slower memory stack. I also would not dismiss the benefits of the larger virtual address space. There are applications where the kernel really benefits from not being constrained to its limited amount of VA in 32-bit mode. -- -- David (obrien@FreeBSD.org)