From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 25 04:59:44 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A168416A402 for ; Sun, 25 Feb 2007 04:59:44 +0000 (UTC) (envelope-from bmeike@speakeasy.net) Received: from mail6.sea5.speakeasy.net (mail6.sea5.speakeasy.net [69.17.117.8]) by mx1.freebsd.org (Postfix) with ESMTP id 83DB813C491 for ; Sun, 25 Feb 2007 04:59:44 +0000 (UTC) (envelope-from bmeike@speakeasy.net) Received: (qmail 3193 invoked from network); 25 Feb 2007 04:33:03 -0000 Received: from callmeike.net (HELO mail.callmeike.net) ([66.92.65.81]) (envelope-sender ) by mail6.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 25 Feb 2007 04:33:03 -0000 Received: from [192.168.89.130] (emma.callmeike.net [192.168.89.130]) by mail.callmeike.net (Postfix) with ESMTP id D4EEE22DD1A; Sat, 24 Feb 2007 23:33:02 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: <00EE2F1E-CE3C-4124-936C-9F8D5B543468@speakeasy.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-hardware@freebsd.org, freebsd-amd64@freebsd.org, freebsd-net@freebsd.org From: Blake Meike Date: Sat, 24 Feb 2007 23:33:01 -0500 X-Mailer: Apple Mail (2.752.2) Cc: Subject: FreeBSD ethernet on a Sun Ultra 20 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Feb 2007 04:59:44 -0000 I've had some trouble getting the ethernet ports on my shiny new Sun Ultra 20 to show up under FreeBSD 6.2. Although this seems like an obvious configuration, it required some digging around, and the kindness of strangers to get it to work. There is now a thread at http://www.bsdforums.org/forums/showthread.php?t=47766 that shows how to get it to work. Please pardon the cross posting. Blake Meike From owner-freebsd-amd64@FreeBSD.ORG Sun Feb 25 13:22:50 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 12ACA16A402; Sun, 25 Feb 2007 13:22:50 +0000 (UTC) (envelope-from lars.tunkrans@bredband.net) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.freebsd.org (Postfix) with ESMTP id F181213C4CE; Sun, 25 Feb 2007 13:22:48 +0000 (UTC) (envelope-from lars.tunkrans@bredband.net) Received: from ironport2.bredband.com ([195.54.107.84] [195.54.107.84]) by mxfep03.bredband.com with ESMTP id <20070225122725.UOHB2708.mxfep03.bredband.com@ironport2.bredband.com>; Sun, 25 Feb 2007 13:27:25 +0100 Received: from c-24a770d5.035-199-73746f23.cust.bredbandsbolaget.se (HELO [192.168.1.75]) ([213.112.167.36]) by ironport2.bredband.com with ESMTP; 25 Feb 2007 13:27:25 +0100 Message-ID: <45E183C7.7040904@bredband.net> Date: Sun, 25 Feb 2007 13:40:39 +0100 From: Lars Tunkrans User-Agent: Thunderbird 1.5.0.8 (X11/20061204) MIME-Version: 1.0 To: Blake Meike References: <00EE2F1E-CE3C-4124-936C-9F8D5B543468@speakeasy.net> In-Reply-To: <00EE2F1E-CE3C-4124-936C-9F8D5B543468@speakeasy.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: FreeBSD ethernet on a Sun Ultra 20 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Feb 2007 13:22:50 -0000 Yes, Im not surprised really, New PCI DEVICE ID's is used all the time. The "Sun Ultra 20 M2" is just a few months old. Its a new motherboard compared to the "Sun Ultra20" which has been around for a year and is already obsolete. Maybe the real question is: When any new Motherboard is evaluated for compatability, do we have a list of which PCI Device ID's the current FreeBSD devicedrivers support ? I am a bit rusty on FreeBSD presently , having worked mostly with OpenSolaris for the last year. On Solaris10/OpenSolaris a file called /etc/driver_aliases is created which contains all the known PCI-DEVICE ID's known by the software ( devicedrivers ). Then when you perform a pciscan you can evaluate whether the hardware you actually have has PCIDevice codes unkown to the device-drivers. FreeBSD has a very good list of supported Hardware that details which chipsets are supported. Maybe this list now needs to be enhanced with the PCI device codes, as a device with the same generic name apperantly now can have several PCI Device codes. Regards //Lars Blake Meike wrote: > I've had some trouble getting the ethernet ports on my shiny new Sun > Ultra 20 to show up under FreeBSD 6.2. Although this seems like an > obvious configuration, it required some digging around, and the > kindness of strangers to get it to work. > > There is now a thread at > > http://www.bsdforums.org/forums/showthread.php?t=47766 > > that shows how to get it to work. Please pardon the cross posting. > > Blake Meike > _______________________________________________ > 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 Mon Feb 26 02:18:44 2007 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A759216A404 for ; Mon, 26 Feb 2007 02:18:44 +0000 (UTC) (envelope-from openjaf@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.freebsd.org (Postfix) with ESMTP id 4180813C47E for ; Mon, 26 Feb 2007 02:18:43 +0000 (UTC) (envelope-from openjaf@gmail.com) Received: by ug-out-1314.google.com with SMTP id 71so624613ugh for ; Sun, 25 Feb 2007 18:18:43 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=tm9pIS/6FbBRzPosYTZWCk+6bV3x8tFFGeZEghDfX4O0LJRL2icDB9u2+PpBm6tSPdXjUHde+ORPbwK/ohyivxKlKE4H3bpqHQC4zIXJsaYbt4LQnURFlp1WrUctUyRNn8bh2ZwiSr0DEMKqtHi1J5lpxJZBe3bY9E5wZbdtgvU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=K1gtlFAq97SIBDq78HN+VgVOt/T/sfolqtnH/tdejBg26hc73eFHChiZceTRHYcmdxqZ5PIABOsJ1OPmAZeZEN6aPczaF04TrHU5TALdGUsgk2NNru37r7qSgmE1+ijvjmgop/binbGY0HbMwKBZfyM5tsM0fveLa8v8l59yHuA= Received: by 10.78.204.20 with SMTP id b20mr396550hug.1172454687761; Sun, 25 Feb 2007 17:51:27 -0800 (PST) Received: by 10.78.167.13 with HTTP; Sun, 25 Feb 2007 17:51:27 -0800 (PST) Message-ID: Date: Sun, 25 Feb 2007 20:51:27 -0500 From: james To: freebsd-amd64@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: MSI K8N Neo4 Platinum X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 26 Feb 2007 02:18:44 -0000 I currently own a MSI K8N Neo4 Platinum and understand that it is currently not a supported AMD64 mother board. How could I help change that. Please email me back. - James A. Feister From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 26 09:24:20 2007 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4242A16A404 for ; Mon, 26 Feb 2007 09:24:18 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id CA3A913C48D for ; Mon, 26 Feb 2007 09:24:17 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 8372B2085; Mon, 26 Feb 2007 10:24:13 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 025F72049; Mon, 26 Feb 2007 10:24:12 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 1001) id D4976B874; Mon, 26 Feb 2007 10:24:12 +0100 (CET) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: james References: Date: Mon, 26 Feb 2007 10:24:12 +0100 In-Reply-To: (openjaf@gmail.com's message of "Sun, 25 Feb 2007 20:51:27 -0500") Message-ID: <86vehp8e6b.fsf@dwp.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-amd64@FreeBSD.org Subject: Re: MSI K8N Neo4 Platinum X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 26 Feb 2007 09:24:20 -0000 james writes: > I currently own a MSI K8N Neo4 Platinum and understand that it is > currently not a supported AMD64 mother board. I don't see why it shouldn't. FreeBSD has been known to work reasonably well with the nForce4 chipset for at least a couple of years. > How could I help change that. Try to run FreeBSD on it and tell us what works and what doesn't. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 26 09:46:46 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CD12716A400; Mon, 26 Feb 2007 09:46:46 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-3-125.belrs4.nsw.optusnet.com.au [220.239.3.125]) by mx1.freebsd.org (Postfix) with ESMTP id A32F913C441; Mon, 26 Feb 2007 09:46:41 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.8/8.13.8) with ESMTP id l1Q99iIx001551; Mon, 26 Feb 2007 20:09:44 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.8/8.13.8/Submit) id l1Q99iIn001550; Mon, 26 Feb 2007 20:09:44 +1100 (EST) (envelope-from peter) Date: Mon, 26 Feb 2007 20:09:44 +1100 From: Peter Jeremy To: Lars Tunkrans Message-ID: <20070226090944.GC844@turion.vk2pj.dyndns.org> References: <00EE2F1E-CE3C-4124-936C-9F8D5B543468@speakeasy.net> <45E183C7.7040904@bredband.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KFztAG8eRSV9hGtP" Content-Disposition: inline In-Reply-To: <45E183C7.7040904@bredband.net> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-net@freebsd.org, freebsd-amd64@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: FreeBSD ethernet on a Sun Ultra 20 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 26 Feb 2007 09:46:47 -0000 --KFztAG8eRSV9hGtP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2007-Feb-25 13:40:39 +0100, Lars Tunkrans w= rote: >On Solaris10/OpenSolaris a file called /etc/driver_aliases is=20 >created which contains all the known PCI-DEVICE ID's=20 >known by the software ( devicedrivers ). There's nothing similar in FreeBSD. Most drivers have a PCI ID table embedded in them in some form but there's no defined interface for querying a driver as to what PCI IDs it recognizes. Each driver is responsible for deciding whether it can support a specific device or not. That decision can be based on information other than just the PCI ID. For example the RealTek 8139 and 8139C+ share the same PCI ID but have different FreeBSD drivers (rl(4) and re(4), respectively). Note that ISA devices (for example) don't have anything equivalent to a PCI ID. >FreeBSD has a very good list of supported Hardware that details =20 >which chipsets are supported.=20 That list is auto-generated from the section 4 man pages. If someone wanted to annotate all the man pages with PCI IDs then the web page would update automatically. >Maybe this list now needs to be enhanced with the PCI device codes, as =20 >a device with the same generic name apperantly >now can have several PCI Device codes. This has always been the case. Compaq/HP (and probably other vendors) regularly put vendor-specific PCI IDs into generic parts in their systems. Conversely, changing the chips in systems without mentioning this anywhere is also quite common (WLAN cards are notorious for this) - this can mean that two cards with identical part numbers and otherwise indistinguishable from the outside of the box can require totally different drivers. --=20 Peter Jeremy --KFztAG8eRSV9hGtP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFF4qPY/opHv/APuIcRAp6zAJ94oNfglTXI7gjTSHMAOQwvGqAaOACfTAIT /0YMzMc85NhXp/OIot1EhBY= =M+4r -----END PGP SIGNATURE----- --KFztAG8eRSV9hGtP-- From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 26 10:56:02 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 551B416A404 for ; Mon, 26 Feb 2007 10:56:02 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id CAA1513C46B for ; Mon, 26 Feb 2007 10:56:01 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from ap-h.matik.com.br (ap-h.matik.com.br [200.152.83.36]) by msrv.matik.com.br (8.13.8/8.13.1) with ESMTP id l1Q9o9nc098881; Mon, 26 Feb 2007 06:50:10 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-amd64@freebsd.org Date: Mon, 26 Feb 2007 06:50:09 -0300 User-Agent: KMail/1.9.5 References: <86vehp8e6b.fsf@dwp.des.no> In-Reply-To: <86vehp8e6b.fsf@dwp.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200702260650.09886.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on msrv.matik.com.br X-Virus-Status: Clean Cc: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= , james Subject: Re: MSI K8N Neo4 Platinum X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 26 Feb 2007 10:56:02 -0000 On Monday 26 February 2007 06:24, Dag-Erling Sm=F8rgrav wrote: > james writes: > > I currently own a MSI K8N Neo4 Platinum and understand that it is > > currently not a supported AMD64 mother board. > > I don't see why it shouldn't. FreeBSD has been known to work > reasonably well with the nForce4 chipset for at least a couple of > years. > > > How could I help change that. > > Try to run FreeBSD on it and tell us what works and what doesn't. > this MB works well, I do have several of them running X2 with up to 4GB and= no=20 problem.=20 =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 26 11:14:31 2007 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CD6DA16A400 for ; Mon, 26 Feb 2007 11:14:31 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id B80DD13C4A7 for ; Mon, 26 Feb 2007 11:14:31 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l1QBEVD1005332 for ; Mon, 26 Feb 2007 11:14:31 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l1QBEPF9005328 for freebsd-amd64@FreeBSD.org; Mon, 26 Feb 2007 11:14:25 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 26 Feb 2007 11:14:25 GMT Message-Id: <200702261114.l1QBEPF9005328@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: linimon set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Cc: Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 26 Feb 2007 11:14:31 -0000 Current FreeBSD problem reports Critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/89202 amd64 [ufs] [panic] Kernel crash when accessing filesystem w 1 problem total. Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/69704 amd64 ext2/ext3 unstable in amd64 o amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o amd64/71644 amd64 [panic] amd64 5.3-BETA4 crash when heavy load o amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was seen but timeout o amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdosfs locks up o amd64/73650 amd64 5.3-release panics on boot o amd64/74747 amd64 System panic on shutdown when process will not die o amd64/76136 amd64 system halts before reboot o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys o amd64/80114 amd64 kldload snd_ich causes interrupt storm when ACPI is en o amd64/80691 amd64 amd64 kernel hangs on load o amd64/81037 amd64 SATA problem o amd64/81602 amd64 SATA crashes with parallel pcm access o amd64/82425 amd64 [fxp] fxp0: device timeout, fxp interface dies on 5.4/ o amd64/82555 amd64 Kernel Panic - after i connect to my "amd64" from anot o amd64/83005 amd64 Memory Occupied during installation of the FreeBSD 5.4 o amd64/84832 amd64 Installation crashes just at boot AMD64/ Version 5.4 o amd64/85431 amd64 AMD64 has short but temporary freezes (hangups) on Sun o amd64/85451 amd64 [hang] 6.0-BETA3 lockups on AMD64 (PREEMPTION only) o amd64/86080 amd64 [radeon] [hang] radeon DRI causes system hang on amd64 o amd64/86503 amd64 [atapicam] [panic] k3b crash the system like hardware o amd64/87156 amd64 First Installation: Kernel crashes o amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Areca ARC-1160 r o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in o amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6 o amd64/87348 amd64 amd64+smp+startkde always crashing o amd64/87472 amd64 I downloaded 5.4 and went to install it, but it keeps o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock called (by ata o amd64/88299 amd64 swapcontext fails with errno 0 f amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/88790 amd64 kernel panic on first boot (after the FreeBSD installa o amd64/89501 amd64 System crashes on install using ftp on local subnet o amd64/89503 amd64 Cant Boot Installation Disk o amd64/89546 amd64 [geom] GEOM error o amd64/89549 amd64 [amd64] nve timeouts on 6.0-release o amd64/89550 amd64 [amd64] sym0: VTOBUS failed (6.0 Release) o amd64/89968 amd64 [ata] Asus A8N-E MediaShield RAID problem (read-only s o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 o amd64/91492 amd64 BTX halted o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/92889 amd64 [libc] xdr double buffer overflow o amd64/92991 amd64 FreeBSD(amd64) freezes when primary disk is on a SiI 3 o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/94677 amd64 panic in amd64 install at non-root user creation o amd64/94989 amd64 BTX Halts on Sun Fire X2100 w/6.1-BETA4 (amd64) and 5. f amd64/95167 amd64 driver for SuperMicro H8DAR-T (Adaptec AIC-8130: (Marv o amd64/95414 amd64 kernel crashes during install o amd64/95888 amd64 kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP DL140G o amd64/96400 amd64 FreeBSD 6.0 Bootin Conflict between Broadcom on-broad o amd64/97075 amd64 Panic, Trap 12 o amd64/97337 amd64 xorg reboots system if dri module is enabled o amd64/99561 amd64 system hangs in FreeBSD AMD64 when writting ext2fs o amd64/102122 amd64 6.1-RELEASE amd64 Install Media panics on boot. s amd64/104311 amd64 ports/wine should be installable on amd64 o amd64/105207 amd64 nVidia MCP55 drivers fail to boot on 6.2B3 amd64 o amd64/105513 amd64 Kernel Panic during package installation on 6.2 beta3 o amd64/105531 amd64 gigabyte GA-M51GM-S2G / nVidia nForce 430 - does not d o amd64/105629 amd64 [re] Issue with re driver p amd64/106109 amd64 amd64: si_addr is not set when sending a signal o amd64/106604 amd64 saslauthd crashes with signal 6 on FreeBSD 6.2-PREREL o amd64/106918 amd64 Asus P5B with internal RealTek PCIe Ethernet o amd64/107345 amd64 Kernel Panic/Crash on dd if=/dev/ad4 of=/dev/ad6 bs=1m o amd64/107433 amd64 i can't install FreeBSD Release 6.1 on HP Pavillion dv o amd64/108172 amd64 Installation fails on new Intel 965 motherboards. o amd64/108328 amd64 FreeBSD-6.2: CD does not boot o amd64/108861 amd64 [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work 67 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/61209 amd64 ppc0: cannot reserve I/O port range o amd64/63188 amd64 [ti] ti(4) broken on amd64 o amd64/69705 amd64 IPC problem (msq_queues) o amd64/74608 amd64 [mpt] [hang] mpt hangs 5 minutes when booting o amd64/74811 amd64 [nfs] df, nfs mount, negative Avail -> 32/64-bit confu s amd64/85273 amd64 FreeBSD (NetBSD or OpenBSD) not install on laptop Comp o amd64/87882 amd64 emu10k1 and APCI on amd64 is just noisy o amd64/88730 amd64 kernel panics during booting from the installation CD o amd64/91195 amd64 FreeBSD 6.0(amd64) and Asus A8R-MVP a amd64/92527 amd64 [ciphy.c] ][patch] no driver for "CICADA VSC 8201 Giga o amd64/93002 amd64 amd64 (6.0) coredumps at unpredictable times a amd64/93090 amd64 NIC on GA-K8NF-9 motherboard is recognized, but does n o amd64/95282 amd64 [ed] fix ed for RELENG_5 amd64 so that it has network o amd64/97489 amd64 nForce 410 ATA controller dma time out o amd64/100326 amd64 /dev/fd0 not created after installation FreeBSD 6.1 AM o amd64/100347 amd64 No hardware support Silicon Image SiI 3132 o amd64/100838 amd64 FreeBSD 6.0/6.1 kernel panics when booting with EIST e o amd64/101132 amd64 Incorrect cpu idle and usage statistics in top and sys o amd64/101248 amd64 vi(1) can crash in ncurses(3) on amd64 o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV f amd64/102975 amd64 NIC unknown o amd64/103259 amd64 Cannot use ataraid on nvidia nForce4+amd64 o amd64/104875 amd64 unsupported intel Desktop Board DG965WH o amd64/105129 amd64 Compatibility with Intel D o amd64/106186 amd64 panic in swap_pager_swap_init (amd64/smp/6.2-pre) o amd64/107858 amd64 amd64 motherboard project - none working sound and gra o amd64/108345 amd64 6.2-* GENERIC will not boot Intel PD EMT64 w/ ACPI o amd64/108841 amd64 Zdump prints bad information and hangs o amd64/108848 amd64 Motherboard MSI K9NGM-L 29 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Feb 26 11:14:33 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 86D9B16A404 for ; Mon, 26 Feb 2007 11:14:33 +0000 (UTC) (envelope-from dfeustel@mindspring.com) Received: from alnrmhc13.comcast.net (alnrmhc13.comcast.net [206.18.177.53]) by mx1.freebsd.org (Postfix) with ESMTP id 6557313C4B4 for ; Mon, 26 Feb 2007 11:14:33 +0000 (UTC) (envelope-from dfeustel@mindspring.com) Date: Mon, 26 Feb 2007 11:04:26 +0000 (GMT) X-Comment: Sending client does not conform to RFC822 minimum requirements X-Comment: Date has been added by Maillennium Received: from localhost (c-69-245-198-27.hsd1.in.comcast.net[69.245.198.27]) by comcast.net (alnrmhc13) with SMTP id <20070226110426b1300e5m84e>; Mon, 26 Feb 2007 11:04:26 +0000 From: dfeustel@mindspring.com To: freebsd-amd64@freebsd.org Message-Id: <20070226111433.6557313C4B4@mx1.freebsd.org> Subject: Re: MSI K8N Neo4 Platinum X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 26 Feb 2007 11:14:33 -0000 On Monday 26 February 2007 06:24, Dag-Erling Sm=F8rgrav wrote: > james writes: > > I currently own a MSI K8N Neo4 Platinum and understand that it is > > currently not a supported AMD64 mother board. > > I don't see why it shouldn't. FreeBSD has been known to work > reasonably well with the nForce4 chipset for at least a couple of > years. I have been running 64-bit OpenBSD 4.0 on the MSI K9N Neo with an 3500+ Athlon 64 (single processor) for several months. Everything works. Looking forware to Barcelona :-). Dave Feustel From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 27 01:10:02 2007 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A8CDF16A403 for ; Tue, 27 Feb 2007 01:10:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 6F23A13C442 for ; Tue, 27 Feb 2007 01:10:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l1R1A2fF064297 for ; Tue, 27 Feb 2007 01:10:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l1R1A2Rg064296; Tue, 27 Feb 2007 01:10:02 GMT (envelope-from gnats) Resent-Date: Tue, 27 Feb 2007 01:10:02 GMT Resent-Message-Id: <200702270110.l1R1A2Rg064296@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-amd64@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Daniel Crandall Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5CE9316A401 for ; Tue, 27 Feb 2007 01:07:33 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [69.147.83.33]) by mx1.freebsd.org (Postfix) with ESMTP id 4ED0013C481 for ; Tue, 27 Feb 2007 01:07:33 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.13.1/8.13.1) with ESMTP id l1R17WM2025513 for ; Tue, 27 Feb 2007 01:07:32 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id l1R17WIj025512; Tue, 27 Feb 2007 01:07:32 GMT (envelope-from nobody) Message-Id: <200702270107.l1R17WIj025512@www.freebsd.org> Date: Tue, 27 Feb 2007 01:07:32 GMT From: Daniel Crandall To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.0 Cc: Subject: amd64/109584: zdump doesn't work X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Feb 2007 01:10:02 -0000 >Number: 109584 >Category: amd64 >Synopsis: zdump doesn't work >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Feb 27 01:10:02 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Daniel Crandall >Release: 5.4 - 6.2 amd64 >Organization: Simple Star Inc. >Environment: FreeBSD cache001.internal.photoshow.com 6.2-RC2 FreeBSD 6.2-RC2 #0: Sun Dec 24 21:28:09 UTC 2006 root@portnoy.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP amd64 >Description: the zdump utility doesn't work on amd64 machines. I see that this was reported as a bug a while ago, but for some reason it was categorized as low priority. Given the fact that Daylight Saving Time rules have been changed and this change is to take effect March 12th, it is imperative to be able to verify whether the installed time zone data is correct. >How-To-Repeat: login to a FreeBSD/amd64 machine `zdump -v /etc/localtime` What it should do: dump lots of timezone information including DST changes. What it does: spits out a couple of lines and hangs. >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 27 06:09:41 2007 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BEC9916A400; Tue, 27 Feb 2007 06:09:41 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 6F06813C48D; Tue, 27 Feb 2007 06:09:41 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id l1R69eoi085009; Tue, 27 Feb 2007 01:09:40 -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.8/8.13.8) with ESMTP id l1R69eIf008199; Tue, 27 Feb 2007 01:09:40 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 6CDF073039; Tue, 27 Feb 2007 01:09:40 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20070227060940.6CDF073039@freebsd-current.sentex.ca> Date: Tue, 27 Feb 2007 01:09:40 -0500 (EST) X-Virus-Scanned: ClamAV version devel-20070108, clamav-milter version devel-111206 on clamscanner2 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2007 06:09:41 -0000 TB --- 2007-02-27 04:40:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-02-27 04:40:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2007-02-27 04:40:00 - cleaning the object tree TB --- 2007-02-27 04:40:58 - checking out the source tree TB --- 2007-02-27 04:40:58 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2007-02-27 04:40:58 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-02-27 04:51:25 - building world (CFLAGS=-O2 -pipe) TB --- 2007-02-27 04:51:25 - cd /src TB --- 2007-02-27 04:51:25 - /usr/bin/make -B buildworld >>> World build started on Tue Feb 27 04:51:27 UTC 2007 >>> 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 >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Tue Feb 27 06:09:39 UTC 2007 TB --- 2007-02-27 06:09:39 - generating LINT kernel config TB --- 2007-02-27 06:09:39 - cd /src/sys/amd64/conf TB --- 2007-02-27 06:09:39 - /usr/bin/make -B LINT TB --- 2007-02-27 06:09:39 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-02-27 06:09:39 - cd /src TB --- 2007-02-27 06:09:39 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Feb 27 06:09:40 UTC 2007 >>> stage 1: configuring the kernel -------------------------------------------------------------- cd /src/sys/amd64/conf; PATH=/obj/amd64/src/tmp/legacy/usr/sbin:/obj/amd64/src/tmp/legacy/usr/bin:/obj/amd64/src/tmp/legacy/usr/games:/obj/amd64/src/tmp/usr/sbin:/obj/amd64/src/tmp/usr/bin:/obj/amd64/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /obj/amd64/src/sys/LINT /src/sys/amd64/conf/LINT WARNING: duplicate option `DEV_MEM' encountered. WARNING: duplicate device `mem' encountered. WARNING: duplicate option `DEV_ISA' encountered. WARNING: duplicate device `isa' encountered. /src/sys/amd64/conf/LINT: unknown option "GEOM_MULTIPATH" *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-02-27 06:09:40 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-02-27 06:09:40 - ERROR: failed to build lint kernel TB --- 2007-02-27 06:09:40 - tinderbox aborted TB --- 0.88 user 3.48 system 5379.51 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 27 11:09:54 2007 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 213A816A401; Tue, 27 Feb 2007 11:09:54 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id D8BC913C428; Tue, 27 Feb 2007 11:09:53 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id l1RB9rVf001618; Tue, 27 Feb 2007 06:09:53 -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.8/8.13.8) with ESMTP id l1RB9qKI015841; Tue, 27 Feb 2007 06:09:53 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id A464173039; Tue, 27 Feb 2007 06:09:52 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20070227110952.A464173039@freebsd-current.sentex.ca> Date: Tue, 27 Feb 2007 06:09:52 -0500 (EST) X-Virus-Scanned: ClamAV version devel-20070108, clamav-milter version devel-111206 on clamscanner2 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2007 11:09:54 -0000 TB --- 2007-02-27 09:40:01 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-02-27 09:40:01 - starting HEAD tinderbox run for amd64/amd64 TB --- 2007-02-27 09:40:01 - cleaning the object tree TB --- 2007-02-27 09:40:44 - checking out the source tree TB --- 2007-02-27 09:40:44 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2007-02-27 09:40:44 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-02-27 09:51:43 - building world (CFLAGS=-O2 -pipe) TB --- 2007-02-27 09:51:43 - cd /src TB --- 2007-02-27 09:51:43 - /usr/bin/make -B buildworld >>> World build started on Tue Feb 27 09:51:44 UTC 2007 >>> 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 >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Tue Feb 27 11:09:51 UTC 2007 TB --- 2007-02-27 11:09:51 - generating LINT kernel config TB --- 2007-02-27 11:09:51 - cd /src/sys/amd64/conf TB --- 2007-02-27 11:09:51 - /usr/bin/make -B LINT TB --- 2007-02-27 11:09:52 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-02-27 11:09:52 - cd /src TB --- 2007-02-27 11:09:52 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Feb 27 11:09:52 UTC 2007 >>> stage 1: configuring the kernel -------------------------------------------------------------- cd /src/sys/amd64/conf; PATH=/obj/amd64/src/tmp/legacy/usr/sbin:/obj/amd64/src/tmp/legacy/usr/bin:/obj/amd64/src/tmp/legacy/usr/games:/obj/amd64/src/tmp/usr/sbin:/obj/amd64/src/tmp/usr/bin:/obj/amd64/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /obj/amd64/src/sys/LINT /src/sys/amd64/conf/LINT WARNING: duplicate option `DEV_MEM' encountered. WARNING: duplicate device `mem' encountered. WARNING: duplicate option `DEV_ISA' encountered. WARNING: duplicate device `isa' encountered. /src/sys/amd64/conf/LINT: unknown option "GEOM_MULTIPATH" *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-02-27 11:09:52 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-02-27 11:09:52 - ERROR: failed to build lint kernel TB --- 2007-02-27 11:09:52 - tinderbox aborted TB --- 0.61 user 2.48 system 5391.09 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 27 16:24:38 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C7A5616A400 for ; Tue, 27 Feb 2007 16:24:38 +0000 (UTC) (envelope-from seanjstrand@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.239]) by mx1.freebsd.org (Postfix) with ESMTP id 84DDC13C461 for ; Tue, 27 Feb 2007 16:24:38 +0000 (UTC) (envelope-from seanjstrand@gmail.com) Received: by wr-out-0506.google.com with SMTP id 55so2424726wri for ; Tue, 27 Feb 2007 08:24:37 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=tcme9mzLqDowdy4DxIMis07czWv+KK3rMw2IYT+w4DKSUJvPYSo/ywihHo0epeMnrfvJdyZxHAC8VoJWFb9eyiSp4rnoC+5is0aOkKg/jbNxfwS//Pr5H/9nFkneWW4JxKu87J/OIJ5y7NrmPMQG7zHqZNW9tmjk5yswg+eR1h0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=mnJecWUHfFveuCAGIW0470NmcPvNCHs+Dw9RfgIlZj6axMgAHPntAZbBR7jXz7hFpp4nf0GnUc/S2mvwmqw4yKgog9rUdGQ6AZTbYIog5M5By5OEhtVylpsC+wVaBcXsQOFTi4Z1BM1bEI0A+moswKhzakpMnVQwgNTn9Wrx85E= Received: by 10.115.61.1 with SMTP id o1mr2584984wak.1172591819010; Tue, 27 Feb 2007 07:56:59 -0800 (PST) Received: by 10.114.179.10 with HTTP; Tue, 27 Feb 2007 07:56:58 -0800 (PST) Message-ID: <7619cc20702270756j344f9632we576d07482e66ecb@mail.gmail.com> Date: Tue, 27 Feb 2007 15:56:58 +0000 From: "SEan Strand" To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: FreeBSD-amd64-Release 6.2 config a USB Mouse X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Feb 2007 16:24:38 -0000 FreeBSD-amd64-Release 6.2 How do I configure a USB Mouse? Have read lots; have toyed with: cd /dev ./MAKEDEV mse - command not found Also: ls /dev/psm /dev/ums* - nothing found What d oI do next ? Rgds SEanS From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 27 18:21:41 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A9B9C16A40B for ; Tue, 27 Feb 2007 18:21:41 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id F40CE13C4B5 for ; Tue, 27 Feb 2007 18:21:39 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 0336E2091; Tue, 27 Feb 2007 19:21:35 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id EA30C2085; Tue, 27 Feb 2007 19:21:34 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 1001) id D0F7CB874; Tue, 27 Feb 2007 19:21:34 +0100 (CET) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: "SEan Strand" References: <7619cc20702270756j344f9632we576d07482e66ecb@mail.gmail.com> Date: Tue, 27 Feb 2007 19:21:34 +0100 In-Reply-To: <7619cc20702270756j344f9632we576d07482e66ecb@mail.gmail.com> (SEan Strand's message of "Tue, 27 Feb 2007 15:56:58 +0000") Message-ID: <86zm6zlavl.fsf@dwp.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD-amd64-Release 6.2 config a USB Mouse X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Feb 2007 18:21:41 -0000 "SEan Strand" writes: > FreeBSD-amd64-Release 6.2 How do I configure a USB Mouse? With a stock kernel? You plug it in. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 27 19:20:09 2007 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 586E416A402 for ; Tue, 27 Feb 2007 19:20:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id EC83F13C4A3 for ; Tue, 27 Feb 2007 19:20:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l1RJK8S3042829 for ; Tue, 27 Feb 2007 19:20:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l1RJK8fo042824; Tue, 27 Feb 2007 19:20:08 GMT (envelope-from gnats) Date: Tue, 27 Feb 2007 19:20:08 GMT Message-Id: <200702271920.l1RJK8fo042824@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Daniel Crandall Cc: Subject: Re: amd64/109584: zdump doesn't work X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Crandall List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2007 19:20:09 -0000 The following reply was made to PR amd64/109584; it has been noted by GNATS. From: Daniel Crandall To: bug-followup@FreeBSD.org, dcrandall@simplestar.com Cc: Subject: Re: amd64/109584: zdump doesn't work Date: Tue, 27 Feb 2007 10:28:17 -0800 Additionally, it appears that the time zone files become damaged on the amd64 machines. I copied a good localtime file from a machine on which zdump works properly to the amd64 machine. Tried to zdump it on the amd64 box and got the behavior described in this bug. But then I copied the same file back to a the machine it came from where it was known to be good. Tried to zdump it and it shows the same corruption as on the amd64 box. From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 27 19:54:06 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 25A0B16A420 for ; Tue, 27 Feb 2007 19:54:06 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id A2E9C13C4B5 for ; Tue, 27 Feb 2007 19:54:05 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l1RJrrlP052947; Tue, 27 Feb 2007 14:53:58 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-amd64@freebsd.org, Daniel Crandall Date: Tue, 27 Feb 2007 14:54:14 -0500 User-Agent: KMail/1.9.1 References: <200702271920.l1RJK8fo042824@freefall.freebsd.org> In-Reply-To: <200702271920.l1RJK8fo042824@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200702271454.14774.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Tue, 27 Feb 2007 14:54:00 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2665/Tue Feb 27 11:26:03 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: wollman@freebsd.org, kensmith@freebsd.org Subject: Re: amd64/109584: zdump doesn't work X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Feb 2007 19:54:06 -0000 On Tuesday 27 February 2007 14:20, Daniel Crandall wrote: > The following reply was made to PR amd64/109584; it has been noted by GNATS. > > From: Daniel Crandall > To: bug-followup@FreeBSD.org, dcrandall@simplestar.com > Cc: > Subject: Re: amd64/109584: zdump doesn't work > Date: Tue, 27 Feb 2007 10:28:17 -0800 > > Additionally, it appears that the time zone files become damaged on the > amd64 machines. I copied a good localtime file from a machine on which > zdump works properly to the amd64 machine. Tried to zdump it on the > amd64 box and got the behavior described in this bug. > > But then I copied the same file back to a the machine it came from where > it was known to be good. Tried to zdump it and it shows the same > corruption as on the amd64 box. It's not corruption. zdump works by trying to enumerate all the possible values of time_t. On a 32-bit machine this means going from -2^31 to 2^31 - 1. On amd64 which has a 64-bit time_t, this means from from -2^63 to 2^63 - 1. If you understand exponential math you will see that the zone files aren't corrupted, and zdump isn't hung. Rather, it's just taking a long time to run. Specifically, at work I timed the 32-bit zdump -v as taking about 0.05 seconds of wall time. If the same box did a full 64-bit zdump -v run it would take about 4294967296 * 0.05 = 214748364.80 seconds to run. Well, some simple math shows: 214748364.80 last / 60 3579139.4133 last / 60 59652.3235 last / 24 2485.5134 last / 365.25 6.8049 Yes, 6.8 _years_ for zdump -v to finish. :) Apparently the tzcode code that zdump comes from has been updated by the vendor to add some limits on the time_t values searched (-500 years to +2500 years IIRC). Hopefully we can get the newer zdump imported into the base system to resolve this issue on 64-bit platforms. For now you can simply make use of date -r with a known time_t to see if your system is up to date. For example, on EST5EDT (Eastern time) this should show up: % date -r 1173596400 Sun Mar 11 03:00:00 EDT 2007 If you don't have the updated file, then you would see 2am EST instead. For PST8PDT (Pacific time) use 1173607200. -- John Baldwin From owner-freebsd-amd64@FreeBSD.ORG Tue Feb 27 22:45:29 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F2EF516A402; Tue, 27 Feb 2007 22:45:28 +0000 (UTC) (envelope-from dcrandall@simplestar.com) Received: from mail.monkeybrains.net (mail1.monkeybrains.net [208.69.40.8]) by mx1.freebsd.org (Postfix) with ESMTP id D75D513C461; Tue, 27 Feb 2007 22:45:28 +0000 (UTC) (envelope-from dcrandall@simplestar.com) Received: from [192.168.0.66] (67-42-179-244.eugn.qwest.net [67.42.179.244]) (authenticated bits=0) by mail.monkeybrains.net (8.13.7/8.13.7) with ESMTP id l1RMPWAp033182 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 27 Feb 2007 14:25:33 -0800 (PST) (envelope-from dcrandall@simplestar.com) From: Daniel Crandall To: John Baldwin In-Reply-To: <200702271454.14774.jhb@freebsd.org> References: <200702271920.l1RJK8fo042824@freefall.freebsd.org> <200702271454.14774.jhb@freebsd.org> Content-Type: text/plain Organization: Simple Star Inc. Date: Tue, 27 Feb 2007 14:25:32 -0800 Message-Id: <1172615132.5198.34.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88.7, clamav-milter version 0.88.7 on mail.monkeybrains.net X-Virus-Status: Clean Cc: wollman@freebsd.org, kensmith@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: amd64/109584: zdump doesn't work X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dcrandall@simplestar.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Feb 2007 22:45:29 -0000 Thanks! I appreciate the detail and provided work around. dc On Tue, 2007-02-27 at 14:54 -0500, John Baldwin wrote: > On Tuesday 27 February 2007 14:20, Daniel Crandall wrote: > > The following reply was made to PR amd64/109584; it has been noted by GNATS. > > > > From: Daniel Crandall > > To: bug-followup@FreeBSD.org, dcrandall@simplestar.com > > Cc: > > Subject: Re: amd64/109584: zdump doesn't work > > Date: Tue, 27 Feb 2007 10:28:17 -0800 > > > > Additionally, it appears that the time zone files become damaged on the > > amd64 machines. I copied a good localtime file from a machine on which > > zdump works properly to the amd64 machine. Tried to zdump it on the > > amd64 box and got the behavior described in this bug. > > > > But then I copied the same file back to a the machine it came from where > > it was known to be good. Tried to zdump it and it shows the same > > corruption as on the amd64 box. > > It's not corruption. zdump works by trying to enumerate all the possible > values of time_t. On a 32-bit machine this means going from -2^31 to > 2^31 - 1. On amd64 which has a 64-bit time_t, this means from from -2^63 to > 2^63 - 1. > > If you understand exponential math you will see that the zone files aren't > corrupted, and zdump isn't hung. Rather, it's just taking a long time to > run. Specifically, at work I timed the 32-bit zdump -v as taking about 0.05 > seconds of wall time. If the same box did a full 64-bit zdump -v run it > would take about 4294967296 * 0.05 = 214748364.80 seconds to run. Well, > some simple math shows: > > 214748364.80 > last / 60 > 3579139.4133 > last / 60 > 59652.3235 > last / 24 > 2485.5134 > last / 365.25 > 6.8049 > > Yes, 6.8 _years_ for zdump -v to finish. :) Apparently the tzcode code that > zdump comes from has been updated by the vendor to add some limits on the > time_t values searched (-500 years to +2500 years IIRC). Hopefully we can > get the newer zdump imported into the base system to resolve this issue on > 64-bit platforms. For now you can simply make use of date -r with a known > time_t to see if your system is up to date. For example, on EST5EDT (Eastern > time) this should show up: > > % date -r 1173596400 > Sun Mar 11 03:00:00 EDT 2007 > > If you don't have the updated file, then you would see 2am EST instead. For > PST8PDT (Pacific time) use 1173607200. > From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 28 03:58:45 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2AC7316D26D for ; Wed, 28 Feb 2007 03:58:45 +0000 (UTC) (envelope-from brucegb@realtime.net) Received: from ruth.realtime.net (mercury.realtime.net [205.238.132.86]) by mx1.freebsd.org (Postfix) with ESMTP id E3A6913C471 for ; Wed, 28 Feb 2007 03:58:44 +0000 (UTC) (envelope-from brucegb@realtime.net) Received: from tigerfish2.my.domain (cpe-72-177-112-115.austin.res.rr.com [72.177.112.115]) by realtime.net (Realtime Communications Advanced E-Mail Services V9.2) with ESMTP id 59925788-1817707 for ; Tue, 27 Feb 2007 21:18:29 -0600 Received: from tigerfish2.my.domain (localhost [127.0.0.1]) by tigerfish2.my.domain (8.13.8/8.13.8) with ESMTP id l1S3ISqN039452 for ; Tue, 27 Feb 2007 21:18:28 -0600 (CST) (envelope-from brucegb@tigerfish2.my.domain) Received: (from brucegb@localhost) by tigerfish2.my.domain (8.13.8/8.13.8/Submit) id l1S3IS1K039451 for freebsd-amd64@freebsd.org; Tue, 27 Feb 2007 21:18:28 -0600 (CST) (envelope-from brucegb) Date: Tue, 27 Feb 2007 21:18:28 -0600 From: Bruce Burden To: freebsd-amd64@freebsd.org Message-ID: <20070228031828.GG30309@tigerfish2.my.domain> References: <7619cc20702270756j344f9632we576d07482e66ecb@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7619cc20702270756j344f9632we576d07482e66ecb@mail.gmail.com> User-Agent: Mutt/1.4.2.2i Subject: Re: FreeBSD-amd64-Release 6.2 config a USB Mouse X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Feb 2007 03:58:45 -0000 On Tue, Feb 27, 2007 at 03:56:58PM +0000, SEan Strand wrote: > FreeBSD-amd64-Release 6.2 How do I configure a USB Mouse? > > Have read lots; have toyed with: > cd /dev > ./MAKEDEV mse - command not found > MAKEDEV was last used in the 4.x days, I believe. You will need: device usb device ums in the kernel, which should be there, unless you have done something to specifically remove them. Now, to use them with X, that is a bit more work, and somewhat dependent on what you have. Fortunately, some googling with usb mouse and X should get you the info you need. Bruce -- ------------------------------------------------------------------------ "I like bad!" Bruce Burden Austin, TX. - Thuganlitha The Power and the Prophet Robert Don Hughes From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 28 06:50:08 2007 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A17AA16A401 for ; Wed, 28 Feb 2007 06:50:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 9151E13C4B3 for ; Wed, 28 Feb 2007 06:50:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l1S6o8g5088569 for ; Wed, 28 Feb 2007 06:50:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l1S6o8x9088566; Wed, 28 Feb 2007 06:50:08 GMT (envelope-from gnats) Date: Wed, 28 Feb 2007 06:50:08 GMT Message-Id: <200702280650.l1S6o8x9088566@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Vasil Dimov Cc: Subject: Re: amd64/109584: zdump doesn't work X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vasil Dimov List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2007 06:50:08 -0000 The following reply was made to PR amd64/109584; it has been noted by GNATS. From: Vasil Dimov To: John Baldwin Cc: freebsd-amd64@freebsd.org, Daniel Crandall , wollman@freebsd.org, kensmith@freebsd.org, rwatson@freebsd.org, bug-followup@FreeBSD.org Subject: Re: amd64/109584: zdump doesn't work Date: Wed, 28 Feb 2007 08:43:37 +0200 On Tue, Feb 27, 2007 at 14:54:14 -0500, John Baldwin wrote: [...] > zdump works by trying to enumerate all the possible > values of time_t. On a 32-bit machine this means going from -2^31 to > 2^31 - 1. On amd64 which has a 64-bit time_t, this means from from -2^63 to > 2^63 - 1. Yes, this is true. > If you understand exponential math you will see that the zone files aren't > corrupted, and zdump isn't hung. Rather, it's just taking a long time to > run. I think this is not the case. It is actually hung in infinite loop in localtime(3) in libc. Try the following code on amd64 platform: --- cut --- time_t t; t = -9223372036762365600; localtime(&t); --- cut --- it hangs in this loop: src/lib/libc/stdtime/localtime.c: 1320 y = EPOCH_YEAR; 1321 #define LEAPS_THRU_END_OF(y) ((y) / 4 - (y) / 100 + (y) / 400) 1322 while (days < 0 || days >= (long) year_lengths[yleap = isleap(y)]) { 1323 long newy; 1324 1325 newy = y + days / DAYSPERNYEAR; 1326 if (days < 0) 1327 --newy; 1328 days -= (newy - y) * DAYSPERNYEAR + 1329 LEAPS_THRU_END_OF(newy - 1) - 1330 LEAPS_THRU_END_OF(y - 1); 1331 y = newy; 1332 } where days oscillates between -1 and 365, y and newy between -292277022654 and -292277022655. E.g. try so see what happens if you enter the loop with days=365 and y=-292277022655. -- Vasil Dimov gro.DSBeerF@dv % Grelb's Reminder: Eighty percent of all people consider themselves to be above average drivers. From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 28 07:11:45 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0A8BC16A403; Wed, 28 Feb 2007 07:11:45 +0000 (UTC) (envelope-from vd@datamax.bg) Received: from jengal.datamax.bg (jengal.datamax.bg [82.103.104.21]) by mx1.freebsd.org (Postfix) with ESMTP id B823013C4B3; Wed, 28 Feb 2007 07:11:44 +0000 (UTC) (envelope-from vd@datamax.bg) Received: from qlovarnika.bg.datamax (qlovarnika.bg.datamax [192.168.10.2]) by jengal.datamax.bg (Postfix) with SMTP id 687CAB848; Wed, 28 Feb 2007 08:43:37 +0200 (EET) Received: (nullmailer pid 35262 invoked by uid 1002); Wed, 28 Feb 2007 06:43:37 -0000 Date: Wed, 28 Feb 2007 08:43:37 +0200 From: Vasil Dimov To: John Baldwin Message-ID: <20070228064337.GA34966@qlovarnika.bg.datamax> References: <200702271920.l1RJK8fo042824@freefall.freebsd.org> <200702271454.14774.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200702271454.14774.jhb@freebsd.org> Cc: Daniel Crandall , bug-followup@FreeBSD.org, freebsd-amd64@freebsd.org, rwatson@freebsd.org, wollman@freebsd.org, kensmith@freebsd.org Subject: Re: amd64/109584: zdump doesn't work X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vd@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, 28 Feb 2007 07:11:45 -0000 On Tue, Feb 27, 2007 at 14:54:14 -0500, John Baldwin wrote: [...] > zdump works by trying to enumerate all the possible > values of time_t. On a 32-bit machine this means going from -2^31 to > 2^31 - 1. On amd64 which has a 64-bit time_t, this means from from -2^63 to > 2^63 - 1. Yes, this is true. > If you understand exponential math you will see that the zone files aren't > corrupted, and zdump isn't hung. Rather, it's just taking a long time to > run. I think this is not the case. It is actually hung in infinite loop in localtime(3) in libc. Try the following code on amd64 platform: --- cut --- time_t t; t = -9223372036762365600; localtime(&t); --- cut --- it hangs in this loop: src/lib/libc/stdtime/localtime.c: 1320 y = EPOCH_YEAR; 1321 #define LEAPS_THRU_END_OF(y) ((y) / 4 - (y) / 100 + (y) / 400) 1322 while (days < 0 || days >= (long) year_lengths[yleap = isleap(y)]) { 1323 long newy; 1324 1325 newy = y + days / DAYSPERNYEAR; 1326 if (days < 0) 1327 --newy; 1328 days -= (newy - y) * DAYSPERNYEAR + 1329 LEAPS_THRU_END_OF(newy - 1) - 1330 LEAPS_THRU_END_OF(y - 1); 1331 y = newy; 1332 } where days oscillates between -1 and 365, y and newy between -292277022654 and -292277022655. E.g. try so see what happens if you enter the loop with days=365 and y=-292277022655. -- Vasil Dimov gro.DSBeerF@dv % Grelb's Reminder: Eighty percent of all people consider themselves to be above average drivers. From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 28 07:52:49 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5A6C816A47F; Wed, 28 Feb 2007 07:52:49 +0000 (UTC) (envelope-from vd@datamax.bg) Received: from jengal.datamax.bg (jengal.datamax.bg [82.103.104.21]) by mx1.freebsd.org (Postfix) with ESMTP id 1862F13C569; Wed, 28 Feb 2007 07:52:45 +0000 (UTC) (envelope-from vd@datamax.bg) Received: from qlovarnika.bg.datamax (qlovarnika.bg.datamax [192.168.10.2]) by jengal.datamax.bg (Postfix) with SMTP id 59BD1B84A; Wed, 28 Feb 2007 09:52:44 +0200 (EET) Received: (nullmailer pid 36515 invoked by uid 1002); Wed, 28 Feb 2007 07:52:44 -0000 Date: Wed, 28 Feb 2007 09:52:44 +0200 From: Vasil Dimov To: John Baldwin Message-ID: <20070228075244.GA36076@qlovarnika.bg.datamax> References: <200702271920.l1RJK8fo042824@freefall.freebsd.org> <200702271454.14774.jhb@freebsd.org> <20070228064337.GA34966@qlovarnika.bg.datamax> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070228064337.GA34966@qlovarnika.bg.datamax> Cc: Daniel Crandall , bug-followup@FreeBSD.org, freebsd-amd64@freebsd.org, rwatson@freebsd.org, wollman@freebsd.org, kensmith@freebsd.org Subject: Re: amd64/109584: zdump doesn't work X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vd@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, 28 Feb 2007 07:52:49 -0000 On Wed, Feb 28, 2007 at 08:43:37 +0200, Vasil Dimov wrote: [...] > it hangs in this loop: > > src/lib/libc/stdtime/localtime.c: > 1320 y = EPOCH_YEAR; > 1321 #define LEAPS_THRU_END_OF(y) ((y) / 4 - (y) / 100 + (y) / 400) > 1322 while (days < 0 || days >= (long) year_lengths[yleap = isleap(y)]) { > 1323 long newy; > 1324 > 1325 newy = y + days / DAYSPERNYEAR; > 1326 if (days < 0) > 1327 --newy; > 1328 days -= (newy - y) * DAYSPERNYEAR + > 1329 LEAPS_THRU_END_OF(newy - 1) - > 1330 LEAPS_THRU_END_OF(y - 1); > 1331 y = newy; > 1332 } > > where days oscillates between -1 and 365, y and newy between > -292277022654 and -292277022655. E.g. try so see what happens if you > enter the loop with days=365 and y=-292277022655. What about this patch: --- localtime.c_infloop.diff begins here --- Index: localtime.c =================================================================== RCS file: /home/ncvs/src/lib/libc/stdtime/localtime.c,v retrieving revision 1.41 diff -u -r1.41 localtime.c --- localtime.c 19 Jan 2007 01:16:35 -0000 1.41 +++ localtime.c 28 Feb 2007 07:40:24 -0000 @@ -1326,8 +1326,8 @@ if (days < 0) --newy; days -= (newy - y) * DAYSPERNYEAR + - LEAPS_THRU_END_OF(newy - 1) - - LEAPS_THRU_END_OF(y - 1); + LEAPS_THRU_END_OF(newy - (newy > 0 ? 1 : -1)) - + LEAPS_THRU_END_OF(y - (y > 0 ? 1 : -1)); y = newy; } tmp->tm_year = y - TM_YEAR_BASE; --- localtime.c_infloop.diff ends here --- -- Vasil Dimov gro.DSBeerF@dv % Everything should be made as simple as possible, but not simpler. -- Albert Einstein From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 28 08:00:35 2007 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EAB2916A50B for ; Wed, 28 Feb 2007 08:00:35 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 7298813C60C for ; Wed, 28 Feb 2007 08:00:22 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l1S80L5v094746 for ; Wed, 28 Feb 2007 08:00:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l1S80LCx094745; Wed, 28 Feb 2007 08:00:21 GMT (envelope-from gnats) Date: Wed, 28 Feb 2007 08:00:21 GMT Message-Id: <200702280800.l1S80LCx094745@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Vasil Dimov Cc: Subject: Re: amd64/109584: zdump doesn't work X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vasil Dimov List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2007 08:00:36 -0000 The following reply was made to PR amd64/109584; it has been noted by GNATS. From: Vasil Dimov To: John Baldwin Cc: freebsd-amd64@freebsd.org, Daniel Crandall , wollman@freebsd.org, kensmith@freebsd.org, rwatson@freebsd.org, bug-followup@FreeBSD.org Subject: Re: amd64/109584: zdump doesn't work Date: Wed, 28 Feb 2007 09:52:44 +0200 On Wed, Feb 28, 2007 at 08:43:37 +0200, Vasil Dimov wrote: [...] > it hangs in this loop: > > src/lib/libc/stdtime/localtime.c: > 1320 y = EPOCH_YEAR; > 1321 #define LEAPS_THRU_END_OF(y) ((y) / 4 - (y) / 100 + (y) / 400) > 1322 while (days < 0 || days >= (long) year_lengths[yleap = isleap(y)]) { > 1323 long newy; > 1324 > 1325 newy = y + days / DAYSPERNYEAR; > 1326 if (days < 0) > 1327 --newy; > 1328 days -= (newy - y) * DAYSPERNYEAR + > 1329 LEAPS_THRU_END_OF(newy - 1) - > 1330 LEAPS_THRU_END_OF(y - 1); > 1331 y = newy; > 1332 } > > where days oscillates between -1 and 365, y and newy between > -292277022654 and -292277022655. E.g. try so see what happens if you > enter the loop with days=365 and y=-292277022655. What about this patch: --- localtime.c_infloop.diff begins here --- Index: localtime.c =================================================================== RCS file: /home/ncvs/src/lib/libc/stdtime/localtime.c,v retrieving revision 1.41 diff -u -r1.41 localtime.c --- localtime.c 19 Jan 2007 01:16:35 -0000 1.41 +++ localtime.c 28 Feb 2007 07:40:24 -0000 @@ -1326,8 +1326,8 @@ if (days < 0) --newy; days -= (newy - y) * DAYSPERNYEAR + - LEAPS_THRU_END_OF(newy - 1) - - LEAPS_THRU_END_OF(y - 1); + LEAPS_THRU_END_OF(newy - (newy > 0 ? 1 : -1)) - + LEAPS_THRU_END_OF(y - (y > 0 ? 1 : -1)); y = newy; } tmp->tm_year = y - TM_YEAR_BASE; --- localtime.c_infloop.diff ends here --- -- Vasil Dimov gro.DSBeerF@dv % Everything should be made as simple as possible, but not simpler. -- Albert Einstein From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 28 08:09:18 2007 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A2EDD16A403; Wed, 28 Feb 2007 08:09:18 +0000 (UTC) (envelope-from vd@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 7AD7C13C442; Wed, 28 Feb 2007 08:09:18 +0000 (UTC) (envelope-from vd@FreeBSD.org) Received: from freefall.freebsd.org (vd@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l1S89ILd095079; Wed, 28 Feb 2007 08:09:18 GMT (envelope-from vd@freefall.freebsd.org) Received: (from vd@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l1S89IhW095075; Wed, 28 Feb 2007 08:09:18 GMT (envelope-from vd) Date: Wed, 28 Feb 2007 08:09:18 GMT From: Vasil Dimov Message-Id: <200702280809.l1S89IhW095075@freefall.freebsd.org> To: dlt@mebtel.net, vd@FreeBSD.org, freebsd-amd64@FreeBSD.org Cc: Subject: Re: amd64/108841: Zdump prints bad information and hangs X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Feb 2007 08:09:18 -0000 Synopsis: Zdump prints bad information and hangs State-Changed-From-To: open->closed State-Changed-By: vd State-Changed-When: Wed Feb 28 08:08:04 UTC 2007 State-Changed-Why: Superseded by amd64/109584 http://www.freebsd.org/cgi/query-pr.cgi?pr=108841 From owner-freebsd-amd64@FreeBSD.ORG Wed Feb 28 09:15:28 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C5E6D16A401 for ; Wed, 28 Feb 2007 09:15:28 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 87FBA13C4A3 for ; Wed, 28 Feb 2007 09:15:28 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id C68252087; Wed, 28 Feb 2007 10:15:24 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 4E65E2049; Wed, 28 Feb 2007 10:15:24 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 1001) id 2DF8FB874; Wed, 28 Feb 2007 10:15:24 +0100 (CET) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: Bruce Burden References: <7619cc20702270756j344f9632we576d07482e66ecb@mail.gmail.com> <20070228031828.GG30309@tigerfish2.my.domain> Date: Wed, 28 Feb 2007 10:15:24 +0100 In-Reply-To: <20070228031828.GG30309@tigerfish2.my.domain> (Bruce Burden's message of "Tue, 27 Feb 2007 21:18:28 -0600") Message-ID: <861wkafxsj.fsf@dwp.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-amd64@freebsd.org Subject: Re: FreeBSD-amd64-Release 6.2 config a USB Mouse X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 28 Feb 2007 09:15:28 -0000 Bruce Burden writes: > Now, to use them with X, that is a bit more work, and somewhat > dependent on what you have. Fortunately, some googling with usb > mouse and X should get you the info you need. No. It should just work, without any manual configuration. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 1 02:46:31 2007 Return-Path: X-Original-To: amd64@freebsd.org Delivered-To: freebsd-amd64@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5F9B616A400; Thu, 1 Mar 2007 02:46:31 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 1E4D813C428; Thu, 1 Mar 2007 02:46:30 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id l212kUtF088646; Wed, 28 Feb 2007 21:46:30 -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.8/8.13.8) with ESMTP id l212kUat032212; Wed, 28 Feb 2007 21:46:30 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 0365773039; Wed, 28 Feb 2007 21:46:29 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20070301024630.0365773039@freebsd-current.sentex.ca> Date: Wed, 28 Feb 2007 21:46:29 -0500 (EST) X-Virus-Scanned: ClamAV version devel-20070108, clamav-milter version devel-111206 on clamscanner3 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Mar 2007 02:46:31 -0000 TB --- 2007-03-01 01:35:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-03-01 01:35:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2007-03-01 01:35:00 - cleaning the object tree TB --- 2007-03-01 01:36:10 - checking out the source tree TB --- 2007-03-01 01:36:10 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2007-03-01 01:36:10 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-03-01 01:49:54 - building world (CFLAGS=-O2 -pipe) TB --- 2007-03-01 01:49:54 - cd /src TB --- 2007-03-01 01:49:54 - /usr/bin/make -B buildworld >>> World build started on Thu Mar 1 01:49:55 UTC 2007 >>> 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 [...] cc -O2 -pipe -DIPSEC -DFAST_IPSEC -DINET6 -DIPX -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /src/usr.bin/netstat/ipsec.c cc -O2 -pipe -DIPSEC -DFAST_IPSEC -DINET6 -DIPX -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /src/usr.bin/netstat/bpf.c cc -O2 -pipe -DIPSEC -DFAST_IPSEC -DINET6 -DIPX -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /src/usr.bin/netstat/pfkey.c cc -O2 -pipe -DIPSEC -DFAST_IPSEC -DINET6 -DIPX -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /src/usr.bin/netstat/inet6.c cc -O2 -pipe -DIPSEC -DFAST_IPSEC -DINET6 -DIPX -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c /src/usr.bin/netstat/ipx.c cc -O2 -pipe -DIPSEC -DFAST_IPSEC -DINET6 -DIPX -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -o netstat if.o inet.o main.o mbuf.o mcast.o mroute.o route.o unix.o atalk.o netgraph.o mroute6.o ipsec.o bpf.o pfkey.o inet6.o ipx.o -lkvm -lmemstat -lnetgraph -lutil -lipx mcast.o(.text+0x1ff): In function `ifmalist_dump_af': : undefined reference to `addr2ascii' *** Error code 1 Stop in /src/usr.bin/netstat. *** Error code 1 Stop in /src/usr.bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-03-01 02:46:29 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-03-01 02:46:29 - ERROR: failed to build world TB --- 2007-03-01 02:46:29 - tinderbox aborted TB --- 0.70 user 3.62 system 4289.12 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 1 14:11:51 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 25D6316A402 for ; Thu, 1 Mar 2007 14:11:51 +0000 (UTC) (envelope-from ewinter@west.bsn.com) Received: from west.bsn.com (host-62-245-151-69.customer.m-online.net [62.245.151.69]) by mx1.freebsd.org (Postfix) with ESMTP id 1D98013C4A7 for ; Thu, 1 Mar 2007 14:11:44 +0000 (UTC) (envelope-from ewinter@west.bsn.com) Received: from west.bsn.com (localhost [127.0.0.1]) by west.bsn.com (8.13.8/8.13.8) with ESMTP id l21DWvtc001435 for ; Thu, 1 Mar 2007 14:33:08 +0100 (CET) (envelope-from ewinter@west.bsn.com) Received: (from ewinter@localhost) by west.bsn.com (8.13.8/8.13.8/Submit) id l21DWqFZ001434 for freebsd-amd64@freebsd.org; Thu, 1 Mar 2007 14:32:52 +0100 (CET) (envelope-from ewinter) Date: Thu, 1 Mar 2007 14:32:46 +0100 From: "Ernst W. Winter" To: "freebsd-amd64@freebsd.org" Message-ID: <20070301133246.GB1400@lobo.ewinter.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Phone: + 49-89-3075-6800 Organization: FreeBSD Evangelist X-Operating-System: FreeBSD lobo.ewinter.org 6.2-STABLE FreeBSD 6.2-STABLE User-Agent: mutt-ng/devel-r804 (FreeBSD) Subject: ZyDAS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Ernst W. Winter" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Mar 2007 14:11:51 -0000 Hello, has anyone had any experiment or use with: [---------------------------Snip------------------------------------] ugen0: ZyDAS USB2.0 WLAN, rev 2.00/48.02, addr 2 ugen0: at uhub1 port 7 (addr 2) disconnected All threads purged from ugen0.4 All threads purged from ugen0.3 All threads purged from ugen0.2 All threads purged from ugen0.1 All threads purged from ugen0 ugen0: detached ugen0: ZyDAS USB2.0 WLAN, rev 2.00/48.02, addr 2 ugen0: at uhub1 port 8 (addr 2) disconnected All threads purged from ugen0.4 All threads purged from ugen0.3 All threads purged from ugen0.2 All threads purged from ugen0.1 All threads purged from ugen0 ugen0: detached [---------------------------Snip------------------------------------] or any that use this with 6.2_STABLE? Ernst -- Ernst Winter ewinter@ewinter.org "Nec scire fas est onmnia" --Horaz FreeBSD provides a "Gates-free PC" - FreeUnix Pioneers "FreeBSD pioneers - every day a new installation" Vista? What Vista? Hasta la vista baby! From owner-freebsd-amd64@FreeBSD.ORG Thu Mar 1 15:12:33 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E7CC216A403 for ; Thu, 1 Mar 2007 15:12:33 +0000 (UTC) (envelope-from zombyfork@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by mx1.freebsd.org (Postfix) with ESMTP id 83D5613C4A7 for ; Thu, 1 Mar 2007 15:12:33 +0000 (UTC) (envelope-from zombyfork@gmail.com) Received: by ug-out-1314.google.com with SMTP id 71so361509ugh for ; Thu, 01 Mar 2007 07:12:32 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=IHFpdpom+rYEPPnPXJ5zDQoMixWYbPb25U0vNlnbiZwhXUaUPrEZFhrBrLRCfkv7LniSKLzxJQrFAQpqPRY+01nzTNMtuTQD09Fs83QN2+CPuSoC1LSfSAEyyGUkNGnNpaqqWqzulU3xo4l47XTaj4NW53uO4/sqErDFInV2cyk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=EdmIdeM/3Pj/Szq4kQZOt8eCR3J6kwD+lftJHONFqNdpdC/fzyKKvnCwLSH7DA8SCzNbvy34UMPgXS0K3q/NVO97ZKAXNByDHXLSHdQ3SMhKFSN9y68ghvgdo9jWRp+tL2G1+TZCegDECq4ndxnDBpUK9ivZ9XicaFbUTwKVSgI= Received: by 10.114.168.1 with SMTP id q1mr145422wae.1172761947552; Thu, 01 Mar 2007 07:12:27 -0800 (PST) Received: by 10.115.108.15 with HTTP; Thu, 1 Mar 2007 07:12:27 -0800 (PST) Message-ID: <346a80220703010712i1c38b919x5c1c998d491d1a66@mail.gmail.com> Date: Thu, 1 Mar 2007 08:12:27 -0700 From: "Coleman Kane" To: "Ernst W. Winter" In-Reply-To: <20070301133246.GB1400@lobo.ewinter.org> MIME-Version: 1.0 References: <20070301133246.GB1400@lobo.ewinter.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-amd64@freebsd.org" Subject: Re: ZyDAS X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cokane@cokane.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Mar 2007 15:12:34 -0000 On 3/1/07, Ernst W. Winter wrote: > > Hello, > > has anyone had any experiment or use with: > > [---------------------------Snip------------------------------------] > > ugen0: ZyDAS USB2.0 WLAN, rev 2.00/48.02, addr 2 > ugen0: at uhub1 port 7 (addr 2) disconnected > All threads purged from ugen0.4 > All threads purged from ugen0.3 > All threads purged from ugen0.2 > All threads purged from ugen0.1 > All threads purged from ugen0 > ugen0: detached > ugen0: ZyDAS USB2.0 WLAN, rev 2.00/48.02, addr 2 > ugen0: at uhub1 port 8 (addr 2) disconnected > All threads purged from ugen0.4 > All threads purged from ugen0.3 > All threads purged from ugen0.2 > All threads purged from ugen0.1 > All threads purged from ugen0 > ugen0: detached > > [---------------------------Snip------------------------------------] > > or any that use this with 6.2_STABLE? > > Ernst > > -- > Ernst Winter ewinter@ewinter.org "Nec scire fas est onmnia" --Horaz > FreeBSD provides a "Gates-free PC" - FreeUnix Pioneers > "FreeBSD pioneers - every day a new installation" > Vista? What Vista? Hasta la vista baby! Yes, I experimented with one of them. There is no driver for it for FreeBSD. There is a driver for Linux (http://linux-lc100020.sourceforge.net/), but I don't know how well it works. You likely won't be able to make use of it under 6.2-STABLE unless you (or someone else) writes a driver for it. BTW, there are a number of more applicable lists for this question, and you'd probably get more information posting there, such as maybe someone else has already started writing a driver for it. The amd64 list is typically for amd64 architecture-related discussion (and your query is more likely to be ignored here as off-topic). -- Coleman From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 2 10:22:42 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9C00C16A404; Fri, 2 Mar 2007 10:22:42 +0000 (UTC) (envelope-from ale@unixmania.net) Received: from smtpi1.ngi.it (smtpi1.ngi.it [88.149.128.20]) by mx1.freebsd.org (Postfix) with ESMTP id A9B2E13C491; Fri, 2 Mar 2007 10:22:41 +0000 (UTC) (envelope-from ale@unixmania.net) Received: from libero.sunshine.ale (81-174-26-112.f5.ngi.it [81.174.26.112]) (authenticated bits=0) by smtpi1.ngi.it (8.13.8/8.13.8) with ESMTP id l228lmKq009762; Fri, 2 Mar 2007 09:47:49 +0100 Received: by libero.sunshine.ale (Postfix, from userid 1001) id 755811550CC; Fri, 2 Mar 2007 09:47:47 +0100 (CET) Date: Fri, 2 Mar 2007 09:47:47 +0100 From: Alessandro de Manzano To: freebsd-net@freebsd.org Message-ID: <20070302084747.GA80114@libero.sunshine.ale> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.9-RELEASE-p3 Cc: freebsd-amd64@freebsd.org Subject: two problems with broadcom NICs X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Mar 2007 10:22:42 -0000 Hello, I've got a bunch of new Dell PowerEdge SC440 machines, but I've some problems running FreeBSD on them. OS: FreeBSD 6.2-RELEASE (but also -stable of yesterday), SMP (but tried also GENERIC monoprocessor), both i386 and amd64, always same results. Situation: Two Broadcom NICs, one on the motherboard and one on PCI-express bus, here is a snippet of pciconf -lv (as you can see I had to add a 3COM PCI card in order to have connectivity) bge0@pci3:0:0: class=0x020000 card=0x165914e4 chip=0x165914e4 rev=0x21 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5750A1 NetXtreme Gigabit Ethernet PCI Express' class = network subclass = ethernet none1@pci4:0:0: class=0x020000 card=0x01df1028 chip=0x167a14e4 rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' class = network subclass = ethernet xl0@pci5:2:0: class=0x020000 card=0x100010b7 chip=0x920010b7 rev=0x74 hdr=0x00 vendor = '3COM Corp, Networking Division' device = '3C905C-TX Fast EtherLink for PC Management NIC' class = network subclass = ethernet The first one (bge0) is the motherboard integrated, the second one (none1) is on PCI-express Problems: First NIC: recognized, but it never see the carrier. ifconfig gives always this result: bge0: flags=8802 mtu 1500 options=1b ether 00:10:18:27:f3:4c media: Ethernet autoselect (none) status: no carrier No matter of what I do (change cable, change remote switch) it always gives "status: no carrier". Leds on the RJ-45 female connector are on (orange one for link) and off (activity). On the switch(es) link leds are always correctly on, so physic carrier should be present. What could be ? What could I try ? Ideas ? Second NIC: is not recognized at all. Maybe it's a matter of missing PCI IDs ? I don't know exactly which model is supposed to be, searching for those IDs gives inconsitances results.. This is a not-yet-in-production machine, so I can do any experiment necessary to solve these problems Hoping in your help ;) below is my full verbose dmesg Many thanks anyway! -- bye! Ale Copyright (c) 1992-2007 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-STABLE #0: Thu Mar 1 12:21:39 CET 2007 root@power64.playstos.ldr:/usr/obj/usr/src/sys/POWER64 Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff80a9b000. Preloaded elf obj module "/boot/kernel/geom_mirror.ko" at 0xffffffff80a9b1f8. INTR: Adding local APIC 0 as a target ACPI APIC Table: Calibrating clock(s) ... i8254 clock: 1193207 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 1862010668 Hz CPU: Intel(R) Xeon(R) CPU 3040 @ 1.86GHz (1862.01-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xbfebfbff Features2=0xe3bd,CX16,XTPR,> AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 2 real memory = 1072152576 (1022 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009bfff, 634880 bytes (155 pages) 0x0000000000b98000 - 0x000000003e03efff, 1028288512 bytes (251047 pages) avail memory = 1022246912 (974 MB) INTR: Adding local APIC 1 as a target FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 APIC: CPU 0 has ACPI ID 1 APIC: CPU 1 has ACPI ID 2 MADT: Found IO APIC ID 8, Interrupt 0 at 0xfec00000 ioapic0: Changing APIC ID to 8 ioapic0: Routing external 8259A's -> intpin 0 MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level lapic: Routing NMI -> LINT1 lapic: LINT1 trigger: level lapic: LINT1 polarity: high ioapic0 irqs 0-23 on motherboard lapic0: Forcing LINT1 to edge trigger cpu0 BSP: ID: 0x00000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00008400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 ath_rate: version 1.2 wlan: <802.11 Link Layer> null: random: nfslock: pseudo-device kbd: new array size 4 kbd1 at kbdmux0 mem: io: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) rr232x: RocketRAID 232x controller driver v1.02 (Mar 1 2007 12:21:26) acpi0: on motherboard ioapic0: routing intpin 9 (ISA IRQ 9) to vector 48 acpi0: [MPSAFE] pci_open(1): mode 1 addr port (0x0cf8) is 0x80000098 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=27788086) acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 0 dev 31 func 0 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 0 dev 31 func 0 acpi0: Power Button (fixed) ACPI timer: 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 pci_link0: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 3 4 5 6 7 9 10 11 12 15 Validation 0 11 N 0 3 4 5 6 7 9 10 11 12 15 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 3 4 5 6 7 9 10 11 12 15 Validation 0 10 N 0 3 4 5 6 7 9 10 11 12 15 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 3 N 0 3 4 5 6 7 9 10 11 12 15 Validation 0 3 N 0 3 4 5 6 7 9 10 11 12 15 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 9 N 0 3 4 5 6 7 9 10 11 12 15 Validation 0 9 N 0 3 4 5 6 7 9 10 11 12 15 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link4: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 3 4 5 6 7 9 10 11 12 15 Validation 0 5 N 0 3 4 5 6 7 9 10 11 12 15 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link5: Index IRQ Rtd Ref IRQs Initial Probe 0 9 N 0 3 4 5 6 7 9 10 11 12 15 Validation 0 9 N 0 3 4 5 6 7 9 10 11 12 15 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link6: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 3 4 5 6 7 9 10 11 12 15 Validation 0 5 N 0 3 4 5 6 7 9 10 11 12 15 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link7: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 3 4 5 6 7 9 10 11 12 15 Validation 0 10 N 0 3 4 5 6 7 9 10 11 12 15 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 12 15 cpu0: on acpi0 cpu0: switching to generic Cx mode acpi_perf0: on cpu0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: physical bus=0 found-> vendor=0x8086, dev=0x2778, revid=0x00 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x2090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x2779, revid=0x00 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message pcib0: matched entry for 0.1.INTA pcib0: slot 1 INTA hardwired to IRQ 16 found-> vendor=0x8086, dev=0x27d0, revid=0x01 bus=0, slot=28, func=0 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message pcib0: matched entry for 0.28.INTA pcib0: slot 28 INTA hardwired to IRQ 16 found-> vendor=0x8086, dev=0x27e0, revid=0x01 bus=0, slot=28, func=4 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message pcib0: matched entry for 0.28.INTA pcib0: slot 28 INTA hardwired to IRQ 16 found-> vendor=0x8086, dev=0x27e2, revid=0x01 bus=0, slot=28, func=5 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0107, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) intpin=b, irq=10 powerspec 2 supports D0 D3 current D0 MSI supports 1 message pcib0: matched entry for 0.28.INTB pcib0: slot 28 INTB hardwired to IRQ 17 found-> vendor=0x8086, dev=0x27c8, revid=0x01 bus=0, slot=29, func=0 class=0c-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=9 map[20]: type 4, range 32, base 0000ff80, size 5, enabled pcib0: matched entry for 0.29.INTA pcib0: slot 29 INTA hardwired to IRQ 21 found-> vendor=0x8086, dev=0x27c9, revid=0x01 bus=0, slot=29, func=1 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=5 map[20]: type 4, range 32, base 0000ff60, size 5, enabled pcib0: matched entry for 0.29.INTB pcib0: slot 29 INTB hardwired to IRQ 22 found-> vendor=0x8086, dev=0x27ca, revid=0x01 bus=0, slot=29, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=3 map[20]: type 4, range 32, base 0000ff40, size 5, enabled pcib0: matched entry for 0.29.INTC pcib0: slot 29 INTC hardwired to IRQ 18 found-> vendor=0x8086, dev=0x27cb, revid=0x01 bus=0, slot=29, func=3 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=10 map[20]: type 4, range 32, base 0000ff20, size 5, enabled pcib0: matched entry for 0.29.INTD pcib0: slot 29 INTD hardwired to IRQ 23 found-> vendor=0x8086, dev=0x27cc, revid=0x01 bus=0, slot=29, func=7 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=9 powerspec 2 supports D0 D3 current D0 map[10]: type 1, range 32, base ff980800, size 10, enabled pcib0: matched entry for 0.29.INTA pcib0: slot 29 INTA hardwired to IRQ 21 found-> vendor=0x8086, dev=0x244e, revid=0xe1 bus=0, slot=30, func=0 class=06-04-01, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x0a (2500 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x27b8, revid=0x01 bus=0, slot=31, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0107, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x27df, revid=0x01 bus=0, slot=31, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0288, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 map[20]: type 4, range 32, base 0000ffa0, size 4, enabled pcib0: matched entry for 0.31.INTA pcib0: slot 31 INTA hardwired to IRQ 16 found-> vendor=0x8086, dev=0x27c0, revid=0x01 bus=0, slot=31, func=2 class=01-01-8f, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=5 powerspec 2 supports D0 D3 current D0 map[10]: type 4, range 32, base 0000fe00, size 3, enabled map[14]: type 4, range 32, base 0000fe10, size 2, enabled map[18]: type 4, range 32, base 0000fe20, size 3, enabled map[1c]: type 4, range 32, base 0000fe30, size 2, enabled map[20]: type 4, range 32, base 0000fec0, size 4, enabled map[24]: type 1, range 32, base effffc00, size 10, enabled pcib0: matched entry for 0.31.INTC pcib0: slot 31 INTC hardwired to IRQ 20 found-> vendor=0x8086, dev=0x27da, revid=0x01 bus=0, slot=31, func=3 class=0c-05-00, hdrtype=0x00, mfdev=0 cmdreg=0x0101, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=10 map[20]: type 4, range 32, base 0000ece0, size 5, enabled pcib0: matched entry for 0.31.INTB pcib0: slot 31 INTB hardwired to IRQ 17 pcib1: irq 16 at device 1.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xf000-0xfff pcib1: memory decode 0xefe00000-0xefefffff pcib1: prefetched decode 0xfff00000-0xfffff pci1: on pcib1 pci1: physical bus=1 pcib2: irq 16 at device 28.0 on pci0 pcib2: secondary bus 2 pcib2: subordinate bus 2 pcib2: I/O decode 0xf000-0xfff pcib2: memory decode 0xefd00000-0xefdfffff pcib2: prefetched decode 0xfff00000-0xfffff pci2: on pcib2 pci2: physical bus=2 pcib3: irq 16 at device 28.4 on pci0 pcib3: secondary bus 3 pcib3: subordinate bus 3 pcib3: I/O decode 0xf000-0xfff pcib3: memory decode 0xefc00000-0xefcfffff pcib3: prefetched decode 0xfff00000-0xfffff pci3: on pcib3 pci3: physical bus=3 found-> vendor=0x14e4, dev=0x1659, revid=0x21 bus=3, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 8 messages, 64 bit map[10]: type 1, range 64, base efcf0000, size 16, enabled pcib3: requested memory range 0xefcf0000-0xefcfffff: good pcib3: matched entry for 3.0.INTA pcib3: slot 0 INTA hardwired to IRQ 16 bge0: mem 0xefcf0000-0xefcfffff irq 16 at device 0.0 on pci3 bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xefcf0000 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: bpf attached bge0: Ethernet address: 00:10:18:27:f3:4c ioapic0: routing intpin 16 (PCI IRQ 16) to vector 49 bge0: [MPSAFE] pcib4: irq 17 at device 28.5 on pci0 pcib4: secondary bus 4 pcib4: subordinate bus 4 pcib4: I/O decode 0xf000-0xfff pcib4: memory decode 0xefb00000-0xefbfffff pcib4: prefetched decode 0xfff00000-0xfffff pci4: on pcib4 pci4: physical bus=4 found-> vendor=0x14e4, dev=0x167a, revid=0x02 bus=4, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 3 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type 1, range 64, base efbf0000, size 16, enabled pcib4: requested memory range 0xefbf0000-0xefbfffff: good pcib4: matched entry for 4.0.INTA pcib4: slot 0 INTA hardwired to IRQ 17 pci4: at device 0.0 (no driver attached) uhci0: port 0xff80-0xff9f irq 21 at device 29.0 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0xff80 ioapic0: routing intpin 21 (PCI IRQ 21) to vector 50 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xff60-0xff7f irq 22 at device 29.1 on pci0 uhci1: Reserved 0x20 bytes for rid 0x20 type 4 at 0xff60 ioapic0: routing intpin 22 (PCI IRQ 22) to vector 51 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xff40-0xff5f irq 18 at device 29.2 on pci0 uhci2: Reserved 0x20 bytes for rid 0x20 type 4 at 0xff40 ioapic0: routing intpin 18 (PCI IRQ 18) to vector 52 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xff20-0xff3f irq 23 at device 29.3 on pci0 uhci3: Reserved 0x20 bytes for rid 0x20 type 4 at 0xff20 ioapic0: routing intpin 23 (PCI IRQ 23) to vector 53 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xff980800-0xff980bff irq 21 at device 29.7 on pci0 ehci0: Reserved 0x400 bytes for rid 0x10 type 3 at 0xff980800 ehci0: [GIANT-LOCKED] usb4: waiting for BIOS to give up control usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered pcib5: at device 30.0 on pci0 pcib5: secondary bus 5 pcib5: subordinate bus 5 pcib5: I/O decode 0xd000-0xdfff pcib5: memory decode 0xef900000-0xefafffff pcib5: prefetched decode 0xe0000000-0xe7ffffff pcib5: Subtractively decoded bridge. pci5: on pcib5 pci5: physical bus=5 found-> vendor=0x10b7, dev=0x9200, revid=0x74 bus=5, slot=2, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0210, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x0a (2500 ns), maxlat=0x0a (2500 ns) intpin=a, irq=3 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 4, range 32, base 0000d880, size 7, enabled pcib5: requested I/O range 0xd880-0xd8ff: in range map[14]: type 1, range 32, base ef9eff80, size 7, enabled pcib5: requested memory range 0xef9eff80-0xef9effff: good pcib5: matched entry for 5.2.INTA pcib5: slot 2 INTA hardwired to IRQ 18 found-> vendor=0x1002, dev=0x515e, revid=0x02 bus=5, slot=7, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0183, statreg=0x0290, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) intpin=a, irq=9 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 3, range 32, base e0000000, size 27, enabled pcib5: requested memory range 0xe0000000-0xe7ffffff: good map[14]: type 4, range 32, base 0000dc00, size 8, enabled pcib5: requested I/O range 0xdc00-0xdcff: in range map[18]: type 1, range 32, base ef9f0000, size 16, enabled pcib5: requested memory range 0xef9f0000-0xef9fffff: good pcib5: matched entry for 5.7.INTA pcib5: slot 7 INTA hardwired to IRQ 19 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xd880-0xd8ff mem 0xef9eff80-0xef9effff irq 18 at device 2.0 on pci5 xl0: Reserved 0x80 bytes for rid 0x14 type 3 at 0xef9eff80 xl0: using memory mapped I/O xl0: media options word: a xl0: found MII/AUTO miibus1: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus1 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: bpf attached xl0: Ethernet address: 00:04:76:24:2c:e6 xl0: [MPSAFE] pci5: at device 7.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf irq 16 at device 31.1 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xffa0 ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=01 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x01 err=0x04 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=00 stat1=01 devices=0x4 ioapic0: routing intpin 14 (ISA IRQ 14) to vector 54 ata0: [MPSAFE] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=00 ostat0=ff ostat1=ff ioapic0: routing intpin 15 (ISA IRQ 15) to vector 55 ata1: [MPSAFE] atapci1: port 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfec0-0xfecf mem 0xeffffc00-0xefffffff irq 20 at device 31.2 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xfec0 ioapic0: routing intpin 20 (PCI IRQ 20) to vector 56 atapci1: [MPSAFE] ata2: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0xfe00 atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at 0xfe10 ata2: reset tp1 mask=03 ostat0=80 ostat1=80 ata2: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: stat1=0x50 err=0x01 lsb=0x00 msb=0x00 ata2: reset tp2 stat0=50 stat1=50 devices=0x3 ata2: [MPSAFE] ata3: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0xfe20 atapci1: Reserved 0x4 bytes for rid 0x1c type 4 at 0xfe30 ata3: reset tp1 mask=00 ostat0=ff ostat1=ff ata3: [MPSAFE] pci0: at device 31.3 (no driver attached) fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: ic_type 90 part_id 80 ioapic0: routing intpin 6 (ISA IRQ 6) to vector 57 fdc0: [MPSAFE] fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: irq maps: 0x4c29 0x4c39 0x4c29 0x4c29 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ioapic0: routing intpin 4 (ISA IRQ 4) to vector 58 ahc_isa_probe 0: ioport 0xc00 alloc failed ahc_isa_probe 13: ioport 0xdc00 alloc failed ahc_isa_probe 14: ioport 0xec00 alloc failed ex_isa_identify() fdc: fdc0 already exists; skipping it sio: sio0 already exists; skipping it pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: at iomem 0xc0000-0xc8fff,0xc9000-0xc97ff,0xc9800-0xcb7ff,0xcb800-0xcbfff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0045 atkbd: keyboard ID 0xffffffff (1) atkbd: failed to reset the keyboard. kbd0 at atkbd0 kbd0: atkbd0, AT 84 (1), config:0x0, flags:0x3d0000 ioapic0: routing intpin 1 (ISA IRQ 1) to vector 59 atkbd0: [GIANT-LOCKED] psm0: current command byte:0045 psm0: failed to reset the aux device. ppc0: cannot reserve I/O port range ppc0: failed to probe at irq 7 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd1, terminal emulator: sc (syscons terminal) sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: irq maps: 0x4c29 0x4c29 0x4c29 0x4c29 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 isa_probe_children: probing PnP devices ums0: Dell Dell USB Mouse, rev 1.10/29.10, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. uhub5: vendor 0x0451 product 0x1446, class 9/0, rev 1.10/1.10, addr 2 uhub5: 4 ports with 4 removable, self powered ukbd0: vendor 0x045e Microsoft Internet Keyboard Pro, rev 1.10/1.11, addr 3, iclass 3/1 kbd2 at ukbd0 kbd2: ukbd0, generic (0), config:0x0, flags:0x3d0000 uhid0: vendor 0x045e Microsoft Internet Keyboard Pro, rev 1.10/1.11, addr 3, iclass 3/1 Device configuration finished. linprocfs registered procfs registered lapic: Divisor 2, Frequency 133000422 hz Timecounter "TSC" frequency 1862010668 Hz quality -100 Timecounters tick every 1.000 msec Linux ELF exec handler installed lo0: bpf attached rr232x: no controller detected. ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire acd0: setting PIO4 on ICH7 chip acd0: setting UDMA33 on ICH7 chip acd0: DVDROM drive at ata0 as master acd0: read 8268KB/s (8268KB/s), 256KB buffer, UDMA33 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, packet acd0: Writes: acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc ata2-slave: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ata2-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad4: 76293MB at ata2-master SATA150 ad4: 156250000 sectors [155009C/16H/63S] 16 sectors/interrupt 1 depth queue ad4: Intel check1 failed ad4: Adaptec check1 failed ad4: LSI (v3) check1 failed ad4: LSI (v2) check1 failed ad4: FreeBSD check1 failed ad5: 76293MB at ata2-slave SATA150 ad5: 156250000 sectors [155009C/16H/63S] 16 sectors/interrupt 1 depth queue ad5: Intel check1 failed ad5: Adaptec check1 failed ad5: LSI (v3) check1 failed ad5: LSI (v2) check1 failed ad5: FreeBSD check1 failed ATA PseudoRAID loaded lapic1: Forcing LINT1 to edge trigger SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x01000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00008400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 ioapic0: Assigning ISA IRQ 1 to local APIC 0 ioapic0: Assigning ISA IRQ 4 to local APIC 1 ioapic0: Assigning ISA IRQ 6 to local APIC 0 ioapic0: Assigning ISA IRQ 9 to local APIC 1 ioapic0: Assigning ISA IRQ 14 to local APIC 0 ioapic0: Assigning ISA IRQ 15 to local APIC 1 ioapic0: Assigning PCI IRQ 16 to local APIC 0 ioapic0: Assigning PCI IRQ 18 to local APIC 1 ioapic0: Assigning PCI IRQ 20 to local APIC 0 ioapic0: Assigning PCI IRQ 21 to local APIC 1 ioapic0: Assigning PCI IRQ 22 to local APIC 0 ioapic0: Assigning PCI IRQ 23 to local APIC 1 GEOM: new disk ad4 GEOM: new disk ad5 GEOM_MIRROR: Device gm0 created (id=3212637885). GEOM_MIRROR: Device gm0: provider ad4 detected. GEOM_MIRROR: Device gm0: provider ad5 detected. GEOM_MIRROR: Device gm0: provider ad5 activated. GEOM_MIRROR: Device gm0: provider ad4 activated. GEOM_MIRROR: Device gm0: provider mirror/gm0 launched. Trying to mount root from ufs:/dev/mirror/gm0s1a start_init: trying /sbin/init From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 2 11:45:35 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 954DF16A402; Fri, 2 Mar 2007 11:45:35 +0000 (UTC) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by mx1.freebsd.org (Postfix) with ESMTP id E7CD413C442; Fri, 2 Mar 2007 11:45:34 +0000 (UTC) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by freebsd.czest.pl (8.13.4/8.12.9) with ESMTP id l22BaHOB002797; Fri, 2 Mar 2007 11:36:19 GMT (envelope-from dunstan@freebsd.czest.pl) Received: (from dunstan@localhost) by freebsd.czest.pl (8.13.4/8.12.9/Submit) id l22BaHtS002796; Fri, 2 Mar 2007 11:36:17 GMT (envelope-from dunstan) Date: Fri, 2 Mar 2007 11:36:15 +0000 From: "Wojciech A. Koszek" To: Alessandro de Manzano Message-ID: <20070302113615.GA2766@FreeBSD.czest.pl> References: <20070302084747.GA80114@libero.sunshine.ale> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <20070302084747.GA80114@libero.sunshine.ale> User-Agent: Mutt/1.4.2.1i X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-2.0.2 (freebsd.czest.pl [80.48.250.4]); Fri, 02 Mar 2007 11:36:19 +0000 (UTC) Cc: freebsd-net@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: two problems with broadcom NICs X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Mar 2007 11:45:35 -0000 On Fri, Mar 02, 2007 at 09:47:47AM +0100, Alessandro de Manzano wrote: > Hello, > > > What could be ? What could I try ? Ideas ? You can check if changing the interface "UP" flag makes in any better: ifconfig up -- Wojciech A. Koszek wkoszek@FreeBSD.org http://FreeBSD.czest.pl/dunstan/ From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 2 12:51:35 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DF6BA16A401; Fri, 2 Mar 2007 12:51:35 +0000 (UTC) (envelope-from ale@unixmania.net) Received: from smtpi2.ngi.it (smtpi2.ngi.it [88.149.128.21]) by mx1.freebsd.org (Postfix) with ESMTP id 6381613C461; Fri, 2 Mar 2007 12:51:35 +0000 (UTC) (envelope-from ale@unixmania.net) Received: from libero.sunshine.ale (81-174-26-112.f5.ngi.it [81.174.26.112]) (authenticated bits=0) by smtpi2.ngi.it (8.13.8/8.13.8) with ESMTP id l22CpXi7031136; Fri, 2 Mar 2007 13:51:33 +0100 Received: by libero.sunshine.ale (Postfix, from userid 1001) id 6A18C1550CC; Fri, 2 Mar 2007 13:51:32 +0100 (CET) Date: Fri, 2 Mar 2007 13:51:32 +0100 From: Alessandro de Manzano To: freebsd-net@freebsd.org Message-ID: <20070302125132.GA80931@libero.sunshine.ale> References: <20070302084747.GA80114@libero.sunshine.ale> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070302084747.GA80114@libero.sunshine.ale> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.9-RELEASE-p3 Cc: freebsd-amd64@freebsd.org Subject: Re: two problems with broadcom NICs X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Mar 2007 12:51:36 -0000 On Fri, Mar 02, 2007 at 09:47:47AM +0100, Alessandro de Manzano wrote: > The first one (bge0) is the motherboard integrated, the second one > (none1) is on PCI-express ERRATA: sorry, I swapped them, bge0 is the PCI-express one, none1 is the motherboard integrated one! -- bye! Ale From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 2 19:38:16 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0D1FD16A402 for ; Fri, 2 Mar 2007 19:38:16 +0000 (UTC) (envelope-from archwndas@yahoo.com) Received: from web56508.mail.re3.yahoo.com (web56508.mail.re3.yahoo.com [66.196.97.37]) by mx1.freebsd.org (Postfix) with SMTP id 9F86E13C471 for ; Fri, 2 Mar 2007 19:38:15 +0000 (UTC) (envelope-from archwndas@yahoo.com) Received: (qmail 59987 invoked by uid 60001); 2 Mar 2007 19:11:34 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=zLIiiRD7Q1Uss2OkVmGrCE8J6b8jk2WYYB4X9AG8BnRygnXq7Clu0evue3vzsKxf87VeSV+fk02X20/pBYo7TslSosD00QiObdW9Re9LIs28zhy6+bACu9havQJDRBq7IG5l7mB6xszOh8MArMDWPFOr498VAaMqR6eZvc+GlCM=; X-YMail-OSG: NAW3c2UVM1mjrx19ONvAG5yOdDKa0RCwv6.etavo1WJ5uwaVbklo_.fLy5KlfY32tw-- Received: from [85.75.40.167] by web56508.mail.re3.yahoo.com via HTTP; Fri, 02 Mar 2007 11:11:34 PST Date: Fri, 2 Mar 2007 11:11:34 -0800 (PST) From: Simeon Nifos To: freebsd-amd64@freebsd.org In-Reply-To: <20061004120041.CB1BB16A519@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <13863.59495.qm@web56508.mail.re3.yahoo.com> Subject: LiveCD 2006.1 boot stops Set Up Hardware Clock to UTC problem X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Mar 2007 19:38:16 -0000 Hi List, I just bought an ACER Laptop 5630. Unfortunately this is the only Laptop where I encountered the following problem: When I try to install Linux from the Gentoo 2006.1 live CD the boot process stops at "Setting Up Hardware Clock to UTC". After that it says "one or more boot scripts didn't start properly". give root password or press CTRL-D for maintainance: With SuSE 10.1 I get a time-out while trying to set hardware clock and then it goes on properly. while other Linux distros either hang or stop at the same point. Moreover FreeBSD 6.2 doesn't boot at all, it stops after loading the kernel and the modules. I tried bood with ACPI off e.t.c. but nothing changed. Is this a motherboard related problem a BIOS problem? Has any one of you had similar problems in the past? What can I do? Best, S.N. ____________________________________________________________________________________ Do you Yahoo!? Everyone is raving about the all-new Yahoo! Mail beta. http://new.mail.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 2 21:11:00 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 89FF116A402; Fri, 2 Mar 2007 21:11:00 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from smtp2.utdallas.edu (smtp2.utdallas.edu [129.110.10.33]) by mx1.freebsd.org (Postfix) with ESMTP id 6CF5B13C461; Fri, 2 Mar 2007 21:11:00 +0000 (UTC) (envelope-from pauls@utdallas.edu) Received: from utd59514.utdallas.edu (utd59514.utdallas.edu [129.110.3.28]) by smtp2.utdallas.edu (Postfix) with ESMTP id 1D96A5C2EF; Fri, 2 Mar 2007 14:37:50 -0600 (CST) Date: Fri, 02 Mar 2007 14:37:50 -0600 From: Paul Schmehl To: freebsd-net@freebsd.org, freebsd-amd64@freebsd.org Message-ID: <0596BF936C9E2F724954C223@utd59514.utdallas.edu> In-Reply-To: <20070302084747.GA80114@libero.sunshine.ale> References: <20070302084747.GA80114@libero.sunshine.ale> X-Mailer: Mulberry/4.0.6 (Linux/x86) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========9CE1C0190F08AECC356A==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: two problems with broadcom NICs X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Mar 2007 21:11:00 -0000 --==========9CE1C0190F08AECC356A========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On Friday, March 02, 2007 09:47:47 +0100 Alessandro de Manzano=20 wrote: > Hello, > > I've got a bunch of new Dell PowerEdge SC440 machines, but I've some > problems running FreeBSD on them. > > OS: FreeBSD 6.2-RELEASE (but also -stable of yesterday), SMP (but tried > also GENERIC monoprocessor), both i386 and amd64, always same results. > > Situation: Two Broadcom NICs, one on the motherboard and one on > PCI-express bus, here is a snippet of pciconf -lv (as you can see I had > to add a 3COM PCI card in order to have connectivity) > > > bge0@pci3:0:0: class=3D0x020000 card=3D0x165914e4 chip=3D0x165914e4 = rev=3D0x21 > hdr=3D0x00 vendor =3D 'Broadcom Corporation' > device =3D 'BCM5750A1 NetXtreme Gigabit Ethernet PCI Express' > class =3D network > subclass =3D ethernet > none1@pci4:0:0: class=3D0x020000 card=3D0x01df1028 chip=3D0x167a14e4 = rev=3D0x02 > hdr=3D0x00 vendor =3D 'Broadcom Corporation' > class =3D network > subclass =3D ethernet > xl0@pci5:2:0: class=3D0x020000 card=3D0x100010b7 chip=3D0x920010b7 = rev=3D0x74 > hdr=3D0x00 vendor =3D '3COM Corp, Networking Division' > device =3D '3C905C-TX Fast EtherLink for PC Management NIC' > class =3D network > subclass =3D ethernet > Shouldn't you be using the bce driver? This is an i386 machine, but amd64=20 should work the same (you're using the same chipset): bce0@pci9:0:0: class=3D0x020000 card=3D0x01b31028 chip=3D0x164c14e4 = rev=3D0x11=20 hdr=3D0x00 vendor =3D 'Broadcom Corporation' class =3D network subclass =3D ethernet bce1@pci5:0:0: class=3D0x020000 card=3D0x01b31028 chip=3D0x164c14e4 = rev=3D0x11=20 hdr=3D0x00 vendor =3D 'Broadcom Corporation' class =3D network subclass =3D ethernet This is a Dell 1950, from dmesg.boot: bce0: mem=20 0xf4000000-0xf5ffffff irq 16 at device 0.0 on pci9 bce0: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz bce1: mem=20 0xf8000000-0xf9ffffff irq 16 at device 0.0 on pci5 bce1: ASIC ID 0x57081010; Revision (B1); PCI-X 64-bit 133MHz Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/ir/security/ --==========9CE1C0190F08AECC356A==========-- From owner-freebsd-amd64@FreeBSD.ORG Fri Mar 2 22:55:41 2007 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E581E16A400; Fri, 2 Mar 2007 22:55:41 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.freebsd.org (Postfix) with ESMTP id 9C50D13C442; Fri, 2 Mar 2007 22:55:41 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.6/8.13.6) with ESMTP id l22Mtehf064319; Fri, 2 Mar 2007 17:55:40 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-net@FreeBSD.org Date: Fri, 2 Mar 2007 17:55:35 -0500 User-Agent: KMail/1.6.2 References: <20070302084747.GA80114@libero.sunshine.ale> In-Reply-To: <20070302084747.GA80114@libero.sunshine.ale> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200703021755.36600.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88.6/2702/Fri Mar 2 10:04:51 2007 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-amd64@FreeBSD.org Subject: Re: two problems with broadcom NICs X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 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, 02 Mar 2007 22:55:42 -0000 On Friday 02 March 2007 03:47 am, Alessandro de Manzano wrote: > Hello, > > I've got a bunch of new Dell PowerEdge SC440 machines, but I've > some problems running FreeBSD on them. > > OS: FreeBSD 6.2-RELEASE (but also -stable of yesterday), SMP (but > tried also GENERIC monoprocessor), both i386 and amd64, always same > results. > > Situation: Two Broadcom NICs, one on the motherboard and one on > PCI-express bus, here is a snippet of pciconf -lv (as you can see I > had to add a 3COM PCI card in order to have connectivity) > > > bge0@pci3:0:0: class=0x020000 card=0x165914e4 chip=0x165914e4 > rev=0x21 hdr=0x00 vendor = 'Broadcom Corporation' > device = 'BCM5750A1 NetXtreme Gigabit Ethernet PCI Express' > class = network > subclass = ethernet I am not sure about this controller (BTW, you had to include dmesg output) but you may want to try -CURRENT. > none1@pci4:0:0: class=0x020000 card=0x01df1028 chip=0x167a14e4 > rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' > class = network > subclass = ethernet This controller is not supported in 6.2-RELEASE. It should be supported in -CURRENT. Jung-uk Kim From owner-freebsd-amd64@FreeBSD.ORG Sat Mar 3 07:41:29 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AF93516A403 for ; Sat, 3 Mar 2007 07:41:29 +0000 (UTC) (envelope-from f.bonnet@esiee.fr) Received: from mail.esiee.fr (mail.esiee.fr [147.215.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 74AB813C478 for ; Sat, 3 Mar 2007 07:41:29 +0000 (UTC) (envelope-from f.bonnet@esiee.fr) Received: from mail.esiee.fr (localhost.esiee.fr [127.0.0.1]) by mail.esiee.fr (Postfix) with SMTP id 8AB7B3658E8 for ; Sat, 3 Mar 2007 08:14:24 +0100 (CET) Received: from secure.esiee.fr (secure.esiee.fr [147.215.1.19]) by mail.esiee.fr (Postfix) with ESMTP id 67DC83658E4 for ; Sat, 3 Mar 2007 08:14:24 +0100 (CET) Received: from [192.168.0.11] (chs77-1-82-238-8-126.fbx.proxad.net [82.238.8.126]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: bonnetf) by secure.esiee.fr (Postfix) with ESMTP id C5B2C3991B for ; Sat, 3 Mar 2007 08:05:22 +0100 (CET) Message-ID: <45E92060.9060902@esiee.fr> Date: Sat, 03 Mar 2007 08:14:40 +0100 From: Frank Bonnet User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: freebsd-amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: ng_fec compiles well but cannot be loaded (6.2) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2007 07:41:29 -0000 Hello trying to install ng_fec on a 2 procs IBM X3650 it appears this module compiles well but generate an exec format error when I try to load it into the kernel ... Any infos welcome thanks a lot Frank From owner-freebsd-amd64@FreeBSD.ORG Sat Mar 3 17:53:21 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C754C16A400; Sat, 3 Mar 2007 17:53:21 +0000 (UTC) (envelope-from ale@unixmania.net) Received: from smtpi1.ngi.it (smtpi1.ngi.it [88.149.128.20]) by mx1.freebsd.org (Postfix) with ESMTP id 0557A13C48D; Sat, 3 Mar 2007 17:53:20 +0000 (UTC) (envelope-from ale@unixmania.net) Received: from libero.sunshine.ale (81-174-26-112.f5.ngi.it [81.174.26.112]) (authenticated bits=0) by smtpi1.ngi.it (8.13.8/8.13.8) with ESMTP id l23HrIeU002210; Sat, 3 Mar 2007 18:53:19 +0100 Received: by libero.sunshine.ale (Postfix, from userid 1001) id ED6391550DA; Sat, 3 Mar 2007 18:53:17 +0100 (CET) Date: Sat, 3 Mar 2007 18:53:17 +0100 From: Alessandro de Manzano To: Paul Schmehl Message-ID: <20070303175317.GA89496@libero.sunshine.ale> References: <20070302084747.GA80114@libero.sunshine.ale> <0596BF936C9E2F724954C223@utd59514.utdallas.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0596BF936C9E2F724954C223@utd59514.utdallas.edu> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.9-RELEASE-p3 Cc: freebsd-net@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: two problems with broadcom NICs X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2007 17:53:21 -0000 On Fri, Mar 02, 2007 at 02:37:50PM -0600, Paul Schmehl wrote: > Shouldn't you be using the bce driver? This is an i386 machine, but amd64 > should work the same (you're using the same chipset): well, actually I have that driver in my kernel but it does not get attached (tried both i386 and x64 kernel) Looking for that card id it seems indeed a bge-supported card in -CURRENT (browswed the cvs commit archive for poweredge SC440), problem is if/when it will be supported in RELENG_6... Many thanks for your answer! -- bye! Ale ale@unixmania.net From owner-freebsd-amd64@FreeBSD.ORG Sat Mar 3 17:59:12 2007 Return-Path: X-Original-To: freebsd-amd64@FreeBSD.org Delivered-To: freebsd-amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D017516A403; Sat, 3 Mar 2007 17:59:12 +0000 (UTC) (envelope-from ale@unixmania.net) Received: from smtpi1.ngi.it (smtpi1.ngi.it [88.149.128.20]) by mx1.freebsd.org (Postfix) with ESMTP id 55F2113C478; Sat, 3 Mar 2007 17:59:12 +0000 (UTC) (envelope-from ale@unixmania.net) Received: from libero.sunshine.ale (81-174-26-112.f5.ngi.it [81.174.26.112]) (authenticated bits=0) by smtpi1.ngi.it (8.13.8/8.13.8) with ESMTP id l23HxBNt002661; Sat, 3 Mar 2007 18:59:11 +0100 Received: by libero.sunshine.ale (Postfix, from userid 1001) id A96341550CC; Sat, 3 Mar 2007 18:59:10 +0100 (CET) Date: Sat, 3 Mar 2007 18:59:10 +0100 From: Alessandro de Manzano To: Jung-uk Kim Message-ID: <20070303175910.GA89601@libero.sunshine.ale> References: <20070302084747.GA80114@libero.sunshine.ale> <200703021755.36600.jkim@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200703021755.36600.jkim@FreeBSD.org> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.9-RELEASE-p3 Cc: freebsd-net@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: two problems with broadcom NICs X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2007 17:59:12 -0000 On Fri, Mar 02, 2007 at 05:55:35PM -0500, Jung-uk Kim wrote: > > bge0@pci3:0:0: class=0x020000 card=0x165914e4 chip=0x165914e4 > > rev=0x21 hdr=0x00 vendor = 'Broadcom Corporation' > > device = 'BCM5750A1 NetXtreme Gigabit Ethernet PCI Express' > > class = network > > subclass = ethernet > > I am not sure about this controller (BTW, you had to include dmesg > output) but you may want to try -CURRENT. My verbose dmesg was in my original mail (not attached, just after my signature), I hope it is not been removed from some MUA :-) Unfortunately I need this machines in production and I must stay with 6.2(-stable if needed) I saw your commit on -CURRENT for BCM7574 on Dell SC440 (did you received my mail ? :) ) > > > none1@pci4:0:0: class=0x020000 card=0x01df1028 chip=0x167a14e4 > > rev=0x02 hdr=0x00 vendor = 'Broadcom Corporation' > > class = network > > subclass = ethernet > > This controller is not supported in 6.2-RELEASE. It should be > supported in -CURRENT. Do you plan/know if/when it will be backported to RELENG_6 ? (maybe for 6.3 ?) Thanks a lot! -- bye! Ale ale@unixmania.net From owner-freebsd-amd64@FreeBSD.ORG Sat Mar 3 18:01:03 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B9E8216A400; Sat, 3 Mar 2007 18:01:03 +0000 (UTC) (envelope-from ale@unixmania.net) Received: from smtpi1.ngi.it (smtpi1.ngi.it [88.149.128.20]) by mx1.freebsd.org (Postfix) with ESMTP id 29A6A13C481; Sat, 3 Mar 2007 18:01:02 +0000 (UTC) (envelope-from ale@unixmania.net) Received: from libero.sunshine.ale (81-174-26-112.f5.ngi.it [81.174.26.112]) (authenticated bits=0) by smtpi1.ngi.it (8.13.8/8.13.8) with ESMTP id l23I12eI002857; Sat, 3 Mar 2007 19:01:02 +0100 Received: by libero.sunshine.ale (Postfix, from userid 1001) id E333B1550CC; Sat, 3 Mar 2007 19:01:00 +0100 (CET) Date: Sat, 3 Mar 2007 19:01:00 +0100 From: Alessandro de Manzano To: "Wojciech A. Koszek" Message-ID: <20070303180100.GB89601@libero.sunshine.ale> References: <20070302084747.GA80114@libero.sunshine.ale> <20070302113615.GA2766@FreeBSD.czest.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070302113615.GA2766@FreeBSD.czest.pl> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.9-RELEASE-p3 Cc: freebsd-net@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: two problems with broadcom NICs X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2007 18:01:03 -0000 On Fri, Mar 02, 2007 at 11:36:15AM +0000, Wojciech A. Koszek wrote: > > What could be ? What could I try ? Ideas ? > > You can check if changing the interface "UP" flag makes in any better: > > ifconfig up yep, this worked for use with my 2 switches. I today also tried with another switch and the NIC worked also without forcing it up.. :-| Maybe some weird in my previous cheap switches ? ;) Thanks! -- bye! Ale ale@unixmania.net From owner-freebsd-amd64@FreeBSD.ORG Sat Mar 3 19:56:53 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0E96516A400; Sat, 3 Mar 2007 19:56:53 +0000 (UTC) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by mx1.freebsd.org (Postfix) with ESMTP id 88AC513C461; Sat, 3 Mar 2007 19:56:52 +0000 (UTC) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by freebsd.czest.pl (8.13.4/8.12.9) with ESMTP id l23KQX2P014165; Sat, 3 Mar 2007 20:26:34 GMT (envelope-from dunstan@freebsd.czest.pl) Received: (from dunstan@localhost) by freebsd.czest.pl (8.13.4/8.12.9/Submit) id l23KQWLY014164; Sat, 3 Mar 2007 20:26:32 GMT (envelope-from dunstan) Date: Sat, 3 Mar 2007 20:26:30 +0000 From: "Wojciech A. Koszek" To: Alessandro de Manzano Message-ID: <20070303202630.GA14147@FreeBSD.czest.pl> References: <20070302084747.GA80114@libero.sunshine.ale> <0596BF936C9E2F724954C223@utd59514.utdallas.edu> <20070303175317.GA89496@libero.sunshine.ale> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <20070303175317.GA89496@libero.sunshine.ale> User-Agent: Mutt/1.4.2.1i X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-2.0.2 (freebsd.czest.pl [80.48.250.4]); Sat, 03 Mar 2007 20:26:34 +0000 (UTC) Cc: Paul Schmehl , freebsd-amd64@freebsd.org, freebsd-net@freebsd.org Subject: Re: two problems with broadcom NICs X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2007 19:56:53 -0000 On Sat, Mar 03, 2007 at 06:53:17PM +0100, Alessandro de Manzano wrote: > On Fri, Mar 02, 2007 at 02:37:50PM -0600, Paul Schmehl wrote: > > > Shouldn't you be using the bce driver? This is an i386 machine, but amd64 > > should work the same (you're using the same chipset): > > well, actually I have that driver in my kernel but it does not get > attached (tried both i386 and x64 kernel) > > Looking for that card id it seems indeed a bge-supported card in > -CURRENT (browswed the cvs commit archive for poweredge SC440), problem > is if/when it will be supported in RELENG_6... > > Many thanks for your answer! You might want to generate a patch for RELENG_6 for yourself, if it's a matter of quirk with proper ID. This should only apply if probe method doesn't return true in your case, and none other changes were made to support your specific device. -- Wojciech A. Koszek wkoszek@FreeBSD.org http://FreeBSD.czest.pl/dunstan/ From owner-freebsd-amd64@FreeBSD.ORG Sat Mar 3 20:06:48 2007 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DF00516A402; Sat, 3 Mar 2007 20:06:48 +0000 (UTC) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by mx1.freebsd.org (Postfix) with ESMTP id 6888013C48E; Sat, 3 Mar 2007 20:06:48 +0000 (UTC) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by freebsd.czest.pl (8.13.4/8.12.9) with ESMTP id l23KaXfw014203; Sat, 3 Mar 2007 20:36:33 GMT (envelope-from dunstan@freebsd.czest.pl) Received: (from dunstan@localhost) by freebsd.czest.pl (8.13.4/8.12.9/Submit) id l23KaWKe014202; Sat, 3 Mar 2007 20:36:32 GMT (envelope-from dunstan) Date: Sat, 3 Mar 2007 20:36:32 +0000 From: "Wojciech A. Koszek" To: Alessandro de Manzano Message-ID: <20070303203631.GB14147@FreeBSD.czest.pl> References: <20070302084747.GA80114@libero.sunshine.ale> <20070302113615.GA2766@FreeBSD.czest.pl> <20070303180100.GB89601@libero.sunshine.ale> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <20070303180100.GB89601@libero.sunshine.ale> User-Agent: Mutt/1.4.2.1i X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-2.0.2 (freebsd.czest.pl [80.48.250.4]); Sat, 03 Mar 2007 20:36:33 +0000 (UTC) Cc: freebsd-net@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: two problems with broadcom NICs X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2007 20:06:49 -0000 On Sat, Mar 03, 2007 at 07:01:00PM +0100, Alessandro de Manzano wrote: > On Fri, Mar 02, 2007 at 11:36:15AM +0000, Wojciech A. Koszek wrote: > > > > What could be ? What could I try ? Ideas ? > > > > You can check if changing the interface "UP" flag makes in any better: > > > > ifconfig up > > yep, this worked for use with my 2 switches. > I today also tried with another switch and the NIC worked also without > forcing it up.. :-| > Maybe some weird in my previous cheap switches ? ;) Unfortunately for FreeBSD, it's not a problem with your switches -- it's rather driver's fault, since I've seen such issue before. -- Wojciech A. Koszek wkoszek@FreeBSD.org http://FreeBSD.czest.pl/dunstan/