From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 31 06:12:19 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E19A16A4CE for ; Sun, 31 Oct 2004 06:12:19 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BDE243D55 for ; Sun, 31 Oct 2004 06:12:19 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id i9V6CIIX061284; Sat, 30 Oct 2004 23:12:18 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id i9V6CHPq060865; Sat, 30 Oct 2004 23:12:17 -0700 (PDT) (envelope-from obrien) Date: Sat, 30 Oct 2004 23:12:17 -0700 From: "David O'Brien" To: Nicolas Blais Message-ID: <20041031061217.GA56606@dragon.nuxi.com> References: <200410301940.i9UJeTkY081142@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200410301940.i9UJeTkY081142@freefall.freebsd.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/67745: boot fails on compaq presario r3000z X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Oct 2004 06:12:19 -0000 On Sat, Oct 30, 2004 at 07:40:29PM +0000, Nicolas Blais wrote: > How come the patch exists.... works perfectly.... and isn't being commited? Because it removes code that does something on other machines. No one has done a good analysis of why this fixes booting on a few models of laptops. Thus we don't understand the consequences of this change. -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 31 15:16:10 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAD7B16A4CE for ; Sun, 31 Oct 2004 15:16:10 +0000 (GMT) Received: from web12822.mail.yahoo.com (web12822.mail.yahoo.com [216.136.174.203]) by mx1.FreeBSD.org (Postfix) with SMTP id 971FD43D31 for ; Sun, 31 Oct 2004 15:16:10 +0000 (GMT) (envelope-from neshort@yahoo.com) Message-ID: <20041031151610.68195.qmail@web12822.mail.yahoo.com> Received: from [216.198.97.46] by web12822.mail.yahoo.com via HTTP; Sun, 31 Oct 2004 07:16:10 PST Date: Sun, 31 Oct 2004 07:16:10 -0800 (PST) From: Neil Short To: freebsd-amd64@freebsd.org In-Reply-To: <200410301940.i9UJeTkY081142@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: amd64/67745: boot fails on compaq presario r3000z X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Oct 2004 15:16:10 -0000 Frustrating, isn't it? --- Nicolas Blais wrote: > The following reply was made to PR amd64/67745; it > has been noted by GNATS. > > From: Nicolas Blais > To: freebsd-gnats-submit@freebsd.org, > newntrbr@ucla.edu > Cc: > Subject: Re: amd64/67745: boot fails on compaq > presario r3000z > Date: Sat, 30 Oct 2004 15:35:54 -0400 > > How come the patch exists.... works perfectly.... > and isn't being commited? > > Nicolas. > _______________________________________________ > 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" > ===== If history always begins this morning, the world holds exciting surprises around every corner (241). --Ann Coulter. Treason. __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 31 16:57:49 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CCE716A4CE; Sun, 31 Oct 2004 16:57:49 +0000 (GMT) Received: from out006.verizon.net (out006pub.verizon.net [206.46.170.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79AF443D41; Sun, 31 Oct 2004 16:57:48 +0000 (GMT) (envelope-from andrew.lankford@verizon.net) Received: from [192.168.0.2] ([138.88.220.111]) by out006.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041031165747.CGXE4017.out006.verizon.net@[192.168.0.2]>; Sun, 31 Oct 2004 10:57:47 -0600 Message-ID: <4185196F.5030705@verizon.net> Date: Sun, 31 Oct 2004 11:57:19 -0500 From: Andrew Lankford User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: gnats@freebsd.org, amd64@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out006.verizon.net from [138.88.220.111] at Sun, 31 Oct 2004 10:57:47 -0600 cc: obrien@FreeBSD.org cc: nb_root@videotron.ca Subject: Re: amd64/67745: boot fails on compaq presario r3000z X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Oct 2004 16:57:49 -0000 >Because it removes code that does something on other machines. No one >has done a good analysis of why this fixes booting on a few models of >laptops. Thus we don't understand the consequences of this change. >-- David (obrien@FreeBSD.org) On account of the fact that my machine was no longer bootable shortly after the long awaited kernel module loading improvements (due to acpi/keyboard driver/whoknowswhat), I've been reluctant to fiddle around further with Kim's patch. I just noticed though that I never tried compiling the kernel on any machine with KBDIO_DEBUG set to some high value (I take it you can do this from buildkernel?). Maybe that would be useful, provided that the tester doesn't set it to a value high enough to bring the machine to its knees. In the end, I suppose some major FreeBSDer will do a keyboard code overhaul eventually as "atkbd0: [GIANT-LOCKED]" still shows up on my p3 machine boot log. Then everything will be peachy or peachy/much worse/peachy/much much worse/peachy... Andrew Lankford From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 31 21:00:10 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC9B216A4CE for ; Sun, 31 Oct 2004 21:00:10 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7E7843D2F for ; Sun, 31 Oct 2004 21:00:09 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id B18F51FF9A8 for ; Sun, 31 Oct 2004 22:00:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id BC9AB1FF92F; Sun, 31 Oct 2004 22:00:05 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 7C9461539F; Sun, 31 Oct 2004 20:59:30 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 71ADD15384 for ; Sun, 31 Oct 2004 20:59:31 +0000 (UTC) Date: Sun, 31 Oct 2004 20:59:31 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: freebsd-amd64@freebsd.org In-Reply-To: Message-ID: References: <20041002144347.GA66319@enemy.org> <20041002192307.GC66319@enemy.org> <20041003011653.GA76597@cat.robbins.dropbear.id.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Subject: Re: amd64 on Asus K8V SE Deluxe X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Oct 2004 21:00:10 -0000 On Thu, 7 Oct 2004, Bjoern A. Zeeb wrote: Hi, sorry for replying to myself... > > Not sure but I'm probably not looking in the right places: > ... > > Is there anywhere else I can look? > > ifconfig sk0 txcsum > ifconfig sk0 -txcsum > > but imho if_sk does not support txcsum so ifconfig sk0 txcum should > give you invalid argument. ... just a quick note: the card does support checksum offloading accoording to[1] but the driver does not seem to support this. [1] http://www.marvell.com/products/pcconn/yukon/Yukon_88E8001_10_073103_final.pdf -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 31 21:20:12 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F13FA16A4CF for ; Sun, 31 Oct 2004 21:20:12 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C481D43D41 for ; Sun, 31 Oct 2004 21:20:12 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i9VLKCiT080901 for ; Sun, 31 Oct 2004 21:20:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i9VLKCHZ080900; Sun, 31 Oct 2004 21:20:12 GMT (envelope-from gnats) Resent-Date: Sun, 31 Oct 2004 21:20:12 GMT Resent-Message-Id: <200410312120.i9VLKCHZ080900@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, "Simson L. Garfinkel" Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D928616A4CE for ; Sun, 31 Oct 2004 21:15:44 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA9FB43D4C for ; Sun, 31 Oct 2004 21:15:44 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i9VLFixw013972 for ; Sun, 31 Oct 2004 21:15:44 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.12.11/8.12.11/Submit) id i9VLFisD013971; Sun, 31 Oct 2004 21:15:44 GMT (envelope-from nobody) Message-Id: <200410312115.i9VLFisD013971@www.freebsd.org> Date: Sun, 31 Oct 2004 21:15:44 GMT From: "Simson L. Garfinkel" To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/73360: sk0: watchdog timeout X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Oct 2004 21:20:13 -0000 >Number: 73360 >Category: amd64 >Synopsis: sk0: watchdog timeout >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Oct 31 21:20:12 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Simson L. Garfinkel >Release: 5.3-RC1 FreeBSD amd64 >Organization: MIT >Environment: FreeBSD r3.nitroba.com 5.3-RC1 FreeBSD 5.3-RC1 #0: Sat Oct 30 13:05:38 EDT 2004 simsong@r3.nitroba.com:/usr/src/sys/amd64/compile/R3 amd64 >Description: I have an AMD64 machine with an ASUS motherboard and an on-board syskonect gigabit ethernet. The syskonect is periodically going mute. It still receives packets but will not transmit. This happens in both gigabit and 100BaseT modes. It started happening a lot when I made the machine an NFS server. Using a plug-in Intel etherexpress makes the problem go away. >From reviewing the freeBSD mailing lists,this is a known problem. sk0: discard frame w/o leading ethernet header (len 0 pkt len 0) sk0: discard frame w/o leading ethernet header (len 0 pkt len 0) sk0: discard frame w/o leading ethernet header (len 0 pkt len 0) sk0: watchdog timeout sk0: watchdog timeout sk0: watchdog timeout sk0: watchdog timeout I wanted you to know that the problem hasn't gone away. >How-To-Repeat: >Fix: Don't use a syskonect. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 31 21:45:09 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39B4916A4CF; Sun, 31 Oct 2004 21:45:09 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id E487943D45; Sun, 31 Oct 2004 21:45:08 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id B3AF41FF91D; Sun, 31 Oct 2004 22:45:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id D3A011FF9A8; Sun, 31 Oct 2004 22:45:05 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 39AEF1539F; Sun, 31 Oct 2004 21:42:22 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 2EB5E15384; Sun, 31 Oct 2004 21:42:23 +0000 (UTC) Date: Sun, 31 Oct 2004 21:42:23 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: "Simson L. Garfinkel" In-Reply-To: <200410312115.i9VLFisD013971@www.freebsd.org> Message-ID: References: <200410312115.i9VLFisD013971@www.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: freebsd-gnats-submit@FreeBSD.org cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/73360: sk0: watchdog timeout X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Oct 2004 21:45:09 -0000 > I have an AMD64 machine with an ASUS motherboard and an on-board syskonect gigabit ethernet. The syskonect is periodically going mute. It still receives packets but will not transmit. This happens in both gigabit and 100BaseT modes. how do you know that it still receives packets ? - can you see counters increasing ? - can you see packets coming in using tcpdump or such ? PS: see also kern/73052, kern/73038, kern/71858, kern/71229, i386/67818, and closed: kern/69879 From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 31 21:50:28 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A78BF16A4CE for ; Sun, 31 Oct 2004 21:50:28 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9567943D45 for ; Sun, 31 Oct 2004 21:50:28 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i9VLoS3r082670 for ; Sun, 31 Oct 2004 21:50:28 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i9VLoSe7082669; Sun, 31 Oct 2004 21:50:28 GMT (envelope-from gnats) Date: Sun, 31 Oct 2004 21:50:28 GMT Message-Id: <200410312150.i9VLoSe7082669@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Bjoern A. Zeeb" Subject: Re: amd64/73360: sk0: watchdog timeout X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Bjoern A. Zeeb" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Oct 2004 21:50:28 -0000 The following reply was made to PR amd64/73360; it has been noted by GNATS. From: "Bjoern A. Zeeb" To: "Simson L. Garfinkel" Cc: freebsd-gnats-submit@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: amd64/73360: sk0: watchdog timeout Date: Sun, 31 Oct 2004 21:42:23 +0000 (UTC) > I have an AMD64 machine with an ASUS motherboard and an on-board syskonect gigabit ethernet. The syskonect is periodically going mute. It still receives packets but will not transmit. This happens in both gigabit and 100BaseT modes. how do you know that it still receives packets ? - can you see counters increasing ? - can you see packets coming in using tcpdump or such ? PS: see also kern/73052, kern/73038, kern/71858, kern/71229, i386/67818, and closed: kern/69879 From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 31 22:17:05 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D42816A4CE for ; Sun, 31 Oct 2004 22:17:05 +0000 (GMT) Received: from sonic.wsrcc.com (sonic.wsrcc.com [64.142.50.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id D70EF43D5D for ; Sun, 31 Oct 2004 22:17:04 +0000 (GMT) wolfgang+gnus20041031T133906@dailyplanet.dontspam.wsrcc.com) Received: by sonic.wsrcc.com (Postfix, from userid 100) id 45A448463EC; Sun, 31 Oct 2004 14:17:04 -0800 (PST) Sender: wolfgang@bonnet.wsrcc.com References: <200410312115.i9VLFisD013971@www.freebsd.org> From: "Wolfgang S. Rupprecht" X-WSRCC: To: freebsd-amd64@freebsd.org Date: 31 Oct 2004 14:17:04 -0800 In-Reply-To: <200410312115.i9VLFisD013971@www.freebsd.org> Message-ID: Lines: 29 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: amd64/73360: sk0: watchdog timeout X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Oct 2004 22:17:05 -0000 simsong@acm.org (Simson L. Garfinkel) writes: > sk0: watchdog timeout > > I wanted you to know that the problem hasn't gone away. Looks like some sk hardware needs to have the tx prodded continually. This solved my tx problem under openbsd/amd64 (grabbed from a netbsd fix). Maybe the freebsd drivers need something similar too? --- if_sk.c 14 Oct 2004 15:27:39 -0000 1.47 +++ if_sk.c 17 Oct 2004 04:30:39 -0000 @@ -1949,8 +1946,11 @@ sk_txeof(struct sk_if_softc *sc_if) } sc_if->sk_cdata.sk_tx_cnt--; SK_INC(idx, SK_TX_RING_CNT); - ifp->if_timer = 0; } + if (sc_if->sk_cdata.sk_tx_cnt == 0) + ifp->if_timer = 0; + else /* nudge chip to keep tx ring moving */ + CSR_WRITE_4(sc, sc_if->sk_tx_bmu, SK_TXBMU_TX_START); sc_if->sk_cdata.sk_tx_cons = idx; -- Wolfgang S. Rupprecht http://www.wsrcc.com/wolfgang/ From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 31 22:33:32 2004 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68FE016A4CE for ; Sun, 31 Oct 2004 22:33:32 +0000 (GMT) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id B571343D2F for ; Sun, 31 Oct 2004 22:33:29 +0000 (GMT) (envelope-from james@jrv.org) Received: from [192.168.3.156] (zippy.jrv.org [192.168.3.156]) (authenticated bits=0) by mail.jrv.org (8.12.11/8.12.10) with ESMTP id i9VMXSge067684 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 31 Oct 2004 16:33:29 -0600 (CST) (envelope-from james@jrv.org) Message-ID: <41856838.6010309@jrv.org> Date: Sun, 31 Oct 2004 16:33:28 -0600 From: "James R. Van Artsalen" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@www.freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: amd64 5.3rc1 panic during install on 8GB RAM Tyan S2885 w/ twe disk X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Oct 2004 22:33:32 -0000 My Tyan S2885 K8W repeatedly panics during the file copy with CD install of 5.3rc1. 2x Operon 248, 8GB split between them (2 2GB DIMMs each CPU). 2 disk (mirrored arrays) under twe (3ware 8606-8). This hardware configuration worked well under 5.2.1 for a couple of months. I've reinstalled 5.2.1 and it still works fine there. The system reboots before I can see what the message is, but there's something about "busdma" in there. From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 31 23:19:26 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3A8F16A4CE; Sun, 31 Oct 2004 23:19:26 +0000 (GMT) Received: from fort-point-station.mit.edu (FORT-POINT-STATION.MIT.EDU [18.7.7.76]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49EA343D1F; Sun, 31 Oct 2004 23:19:26 +0000 (GMT) (envelope-from simsong@csail.mit.edu) Received: from grand-central-station.mit.edu (GRAND-CENTRAL-STATION.MIT.EDU [18.7.21.82])i9VNJMnn008300; Sun, 31 Oct 2004 18:19:22 -0500 (EST) Received: from melbourne-city-street.mit.edu (OUTGOING-LEGACY.MIT.EDU [18.7.22.104])i9VNJJiP012719; Sun, 31 Oct 2004 18:19:22 -0500 (EST) Received: from [192.168.1.239] (ip-64-7-15-235.dsl.bos.megapath.net [64.7.15.235]) )i9VNJHjc016686; Sun, 31 Oct 2004 18:19:17 -0500 (EST) In-Reply-To: References: <200410312115.i9VLFisD013971@www.freebsd.org> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-2-698480383; protocol="application/pkcs7-signature" Message-Id: <4D9834F9-2B93-11D9-B7B6-000A95DA91E2@csail.mit.edu> From: "Simson L. Garfinkel" Date: Sun, 31 Oct 2004 18:19:24 -0500 To: "Bjoern A. Zeeb" X-Mailer: Apple Mail (2.619) X-Scanned-By: MIMEDefang 2.42 X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd-gnats-submit@FreeBSD.org cc: "Simson L. Garfinkel" cc: freebsd-amd64@FreeBSD.org Subject: Re: amd64/73360: sk0: watchdog timeout X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Oct 2004 23:19:27 -0000 --Apple-Mail-2-698480383 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed On Oct 31, 2004, at 4:42 PM, Bjoern A. Zeeb wrote: >> I have an AMD64 machine with an ASUS motherboard and an on-board >> syskonect gigabit ethernet. The syskonect is periodically going mute. >> It still receives packets but will not transmit. This happens in both >> gigabit and 100BaseT modes. > > how do you know that it still receives packets ? > > - can you see counters increasing ? I ran tcpdump and saw that the packets were still arriving > - can you see packets coming in using tcpdump or such ? > > PS: > see also kern/73052, kern/73038, kern/71858, kern/71229, i386/67818, > and closed: kern/69879 Okay. ... I'm not sure what to do about those. ... I think that this is a syskonnect problem, rather than an AMD64 problem. I'm happy to assist the debugging. I seem to be able to make this happen pretty easily. > --Apple-Mail-2-698480383-- From owner-freebsd-amd64@FreeBSD.ORG Sun Oct 31 23:20:27 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E66AB16A4CE for ; Sun, 31 Oct 2004 23:20:27 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5AEA43D41 for ; Sun, 31 Oct 2004 23:20:27 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i9VNKR3i093533 for ; Sun, 31 Oct 2004 23:20:27 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i9VNKRJA093532; Sun, 31 Oct 2004 23:20:27 GMT (envelope-from gnats) Date: Sun, 31 Oct 2004 23:20:27 GMT Message-Id: <200410312320.i9VNKRJA093532@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Simson L. Garfinkel" Subject: Re: amd64/73360: sk0: watchdog timeout X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Simson L. Garfinkel" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Oct 2004 23:20:28 -0000 The following reply was made to PR amd64/73360; it has been noted by GNATS. From: "Simson L. Garfinkel" To: "Bjoern A. Zeeb" Cc: "Simson L. Garfinkel" , freebsd-amd64@FreeBSD.org, freebsd-gnats-submit@FreeBSD.org Subject: Re: amd64/73360: sk0: watchdog timeout Date: Sun, 31 Oct 2004 18:19:24 -0500 --Apple-Mail-2-698480383 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed On Oct 31, 2004, at 4:42 PM, Bjoern A. Zeeb wrote: >> I have an AMD64 machine with an ASUS motherboard and an on-board >> syskonect gigabit ethernet. The syskonect is periodically going mute. >> It still receives packets but will not transmit. This happens in both >> gigabit and 100BaseT modes. > > how do you know that it still receives packets ? > > - can you see counters increasing ? I ran tcpdump and saw that the packets were still arriving > - can you see packets coming in using tcpdump or such ? > > PS: > see also kern/73052, kern/73038, kern/71858, kern/71229, i386/67818, > and closed: kern/69879 Okay. ... I'm not sure what to do about those. ... I think that this is a syskonnect problem, rather than an AMD64 problem. I'm happy to assist the debugging. I seem to be able to make this happen pretty easily. > --Apple-Mail-2-698480383 Content-Transfer-Encoding: base64 Content-Type: application/pkcs7-signature; name=smime.p7s Content-Disposition: attachment; filename=smime.p7s MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGQTCCAvow ggJjoAMCAQICAw0E2zANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt YWlsIElzc3VpbmcgQ0EwHhcNMDQwOTEwMTcyMzE5WhcNMDUwOTEwMTcyMzE5WjBHMR8wHQYDVQQD ExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMSQwIgYJKoZIhvcNAQkBFhVzaW1zb25nQGNzYWlsLm1p dC5lZHUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDPLsUeV6/8PNIFyEXXGCdqAxJQ JQeQ88JVHa0K4S8+DdAQTmLsLGPsblhVaaZPrRhYpSMyeaJltplhiGWVsGPCzmLYRM8AFkw/NqW/ yBBsTpPZdNkGJYbubhIDBgX5LgWk4nml8FbU20edtIJ3TbPcXnxlsvOl03vdVC2111Qi1bldlqeY k3pFrgAcI8KUYpPcPsJbi576FOx+V+LKeFH2T5QRsDw36q8XdkUB207gGYqPY8VZmaXkB+8N4Svq jnMdRDp418gCULfdRJjJC1q5KDXEgRsm92tzzPP7kTAO0oYeCe9dEv1+kjs+xk67GJfv1oA/Z9YV DGVL9EXFe5GVAgMBAAGjVTBTMA4GA1UdDwEB/wQEAwID+DARBglghkgBhvhCAQEEBAMCBaAwIAYD VR0RBBkwF4EVc2ltc29uZ0Bjc2FpbC5taXQuZWR1MAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcNAQEE BQADgYEATYti6/MBmw128O1SiAETMMD1CT60c6RHlmZ68TOU7rWD+bSmwbwmys3EpwRlZoY8Nxu+ xTBZNxVYWttrGjQ89MNkCRKLJ6lnmgVSliAfIVF0/Bx1oNjaZkJsvcPP/uqV3uEKxHXNqs/Wo7Hh YHRioRt7gUgUfqs2K2koYNderPIwggM/MIICqKADAgECAgENMA0GCSqGSIb3DQEBBQUAMIHRMQsw CQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAY BgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2Vz IERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG 9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDMwNzE3MDAwMDAwWhcNMTMw NzE2MjM1OTU5WjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0 eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwgZ8w DQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMSmPFVzVftOucqZWh5owHUEcJ3f6f+jHuy9zfVb8hp2 vX8MOmHyv1HOAdTlUAow1wJjWiyJFXCO3cnwK4Vaqj9xVsuvPAsH5/EfkTYkKhPPK9Xzgnc9A74r /rsYPge/QIACZNenprufZdHFKlSFD0gEf6e20TxhBEAeZBlyYLf7AgMBAAGjgZQwgZEwEgYDVR0T AQH/BAgwBgEB/wIBADBDBgNVHR8EPDA6MDigNqA0hjJodHRwOi8vY3JsLnRoYXd0ZS5jb20vVGhh d3RlUGVyc29uYWxGcmVlbWFpbENBLmNybDALBgNVHQ8EBAMCAQYwKQYDVR0RBCIwIKQeMBwxGjAY BgNVBAMTEVByaXZhdGVMYWJlbDItMTM4MA0GCSqGSIb3DQEBBQUAA4GBAEiM0VCD6gsuzA2jZqxn D3+vrL7CF6FDlpSdf0whuPg2H6otnzYvwPQcUCCTcDz9reFhYsPZOhl+hLGZGwDFGguCdJ4lUJRi x9sncVcljd2pnDmOjCBPZV+V2vf3h9bGCE6u9uo05RAaWzVNd+NWIXiC3CEZNd4ksdMdRv9dX2VP MYIC5zCCAuMCAQEwaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcg KFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EC Aw0E2zAJBgUrDgMCGgUAoIIBUzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJ BTEPFw0wNDEwMzEyMzE5MjRaMCMGCSqGSIb3DQEJBDEWBBTx/UcqCcbE4dxxW3HmsOQsuKt8ZzB4 BgkrBgEEAYI3EAQxazBpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGlu ZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBD QQIDDQTbMHoGCyqGSIb3DQEJEAILMWugaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3Rl IENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWls IElzc3VpbmcgQ0ECAw0E2zANBgkqhkiG9w0BAQEFAASCAQBpAfN9sDv8djY4wuG8F0AHp+ncOog+ TnZ355D7W1VhTywlzrJ6/1UUzSJthjCvUuUxXFm3HpbRB6ndrsXicGDOAxpkGANH8OzLpTY5srw+ 6UMz/BIVuLb+t3mNBEDut7ut6TV2pGwp8aLdYCHqNCXToduM6MofsfIAkYW6uxtZXNnxq45xSB5+ aQ7Y7iNeWxeu4vwqN8+wzwCeplm5yEzwi3YmnrkY12dbS7LGL5y2p+6fGpPl+UsKSxDE/BWaKlSO gsk2u3l3FMlpCJazZDAUnpAaAXj2BYTkE8/7mCaCcEFjvhSloM1pZyIM9J/vWWiu4otYPLtAYuZw uSawzo9tAAAAAAAA --Apple-Mail-2-698480383-- From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 1 00:09:38 2004 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58EC016A4CE for ; Mon, 1 Nov 2004 00:09:38 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DB6E43D39 for ; Mon, 1 Nov 2004 00:09:38 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iA109CIP070990; Sun, 31 Oct 2004 16:09:13 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iA109CaV070961; Sun, 31 Oct 2004 16:09:12 -0800 (PST) (envelope-from obrien) Date: Sun, 31 Oct 2004 16:09:12 -0800 From: "David O'Brien" To: "James R. Van Artsalen" Message-ID: <20041101000912.GE56606@dragon.nuxi.com> References: <41856838.6010309@jrv.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41856838.6010309@jrv.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-amd64@www.freebsd.org Subject: Re: amd64 5.3rc1 panic during install on 8GB RAM Tyan S2885 w/ twe disk X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-amd64@FreeBSD.org List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 00:09:38 -0000 On Sun, Oct 31, 2004 at 04:33:28PM -0600, James R. Van Artsalen wrote: > My Tyan S2885 K8W repeatedly panics during the file copy with CD install > of 5.3rc1. .. > This hardware configuration worked well under 5.2.1 for a couple of > months. I've reinstalled 5.2.1 and it still works fine there. Can you try the 5.3 Beta's to see when this broke for you? -- -- David (obrien@FreeBSD.org) From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 1 00:57:38 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6600C16A4CE for ; Mon, 1 Nov 2004 00:57:38 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B1DD43D2D for ; Mon, 1 Nov 2004 00:57:38 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 16836 invoked from network); 1 Nov 2004 00:57:37 -0000 Received: from gate.funkthat.com (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail3.speakeasy.net (qmail-ldap-1.03) with SMTP ; 1 Nov 2004 00:57:37 -0000 Received: from hydrogen.funkthat.com (mdazwt@localhost.funkthat.com [127.0.0.1])iA10vaB6069645; Sun, 31 Oct 2004 16:57:37 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id iA10vZl4069644; Sun, 31 Oct 2004 16:57:35 -0800 (PST) Date: Sun, 31 Oct 2004 16:57:35 -0800 From: John-Mark Gurney To: "Wolfgang S. Rupprecht" Message-ID: <20041101005735.GO22681@funkthat.com> Mail-Followup-To: "Wolfgang S. Rupprecht" , freebsd-amd64@freebsd.org References: <200410312115.i9VLFisD013971@www.freebsd.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="WR+jf/RUebEcofwt" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: freebsd-amd64@freebsd.org Subject: Re: amd64/73360: sk0: watchdog timeout X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 00:57:38 -0000 --WR+jf/RUebEcofwt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Wolfgang S. Rupprecht wrote this message on Sun, Oct 31, 2004 at 14:17 -0800: > > simsong@acm.org (Simson L. Garfinkel) writes: > > sk0: watchdog timeout > > > > I wanted you to know that the problem hasn't gone away. > > Looks like some sk hardware needs to have the tx prodded continually. > > This solved my tx problem under openbsd/amd64 (grabbed from a netbsd > fix). Maybe the freebsd drivers need something similar too? > > --- if_sk.c 14 Oct 2004 15:27:39 -0000 1.47 > +++ if_sk.c 17 Oct 2004 04:30:39 -0000 > @@ -1949,8 +1946,11 @@ sk_txeof(struct sk_if_softc *sc_if) > } > sc_if->sk_cdata.sk_tx_cnt--; > SK_INC(idx, SK_TX_RING_CNT); > - ifp->if_timer = 0; > } > + if (sc_if->sk_cdata.sk_tx_cnt == 0) > + ifp->if_timer = 0; > + else /* nudge chip to keep tx ring moving */ > + CSR_WRITE_4(sc, sc_if->sk_tx_bmu, SK_TXBMU_TX_START); > > sc_if->sk_cdata.sk_tx_cons = idx; Hey, thanks for pointing this patch out... I've slightly modified it to better handle IFF_OACTIVE since it's possible to clear the flag when it shouldn't be... If people see this patch improve things, I'll commit it... I haven't tested w/ my sk card yet though... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." --WR+jf/RUebEcofwt Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="if_sk.diff" Index: if_sk.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_sk.c,v retrieving revision 1.86 diff -u -r1.86 if_sk.c --- if_sk.c 20 Aug 2004 06:22:04 -0000 1.86 +++ if_sk.c 1 Nov 2004 00:54:20 -0000 @@ -1816,11 +1816,13 @@ } /* Transmit */ - sc_if->sk_cdata.sk_tx_prod = idx; - CSR_WRITE_4(sc, sc_if->sk_tx_bmu, SK_TXBMU_TX_START); + if (idx != sc_if->sk_cdata.sk_tx_prod) { + sc_if->sk_cdata.sk_tx_prod = idx; + CSR_WRITE_4(sc, sc_if->sk_tx_bmu, SK_TXBMU_TX_START); - /* Set a timeout in case the chip goes out to lunch. */ - ifp->if_timer = 5; + /* Set a timeout in case the chip goes out to lunch. */ + ifp->if_timer = 5; + } SK_IF_UNLOCK(sc_if); return; @@ -1960,13 +1962,15 @@ } sc_if->sk_cdata.sk_tx_cnt--; SK_INC(idx, SK_TX_RING_CNT); - ifp->if_timer = 0; } - sc_if->sk_cdata.sk_tx_cons = idx; - - if (cur_tx != NULL) + if (sc_if->sk_cdata.sk_tx_cnt == 0) { + ifp->if_timer = 0; ifp->if_flags &= ~IFF_OACTIVE; + } else /* nudge chip to keep tx ring moving */ + CSR_WRITE_4(sc, sc_if->sk_tx_bmu, SK_TXBMU_TX_START); + + sc_if->sk_cdata.sk_tx_cons = idx; return; } --WR+jf/RUebEcofwt-- From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 1 03:10:10 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF36D16A4CE for ; Mon, 1 Nov 2004 03:10:10 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADA3343D55 for ; Mon, 1 Nov 2004 03:10:10 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id iA13AAHY019534 for ; Mon, 1 Nov 2004 03:10:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id iA13AA2u019533; Mon, 1 Nov 2004 03:10:10 GMT (envelope-from gnats) Resent-Date: Mon, 1 Nov 2004 03:10:10 GMT Resent-Message-Id: <200411010310.iA13AA2u019533@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, "Simson L. Garfinkel" Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B071E16A4CE for ; Mon, 1 Nov 2004 03:04:07 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5310E43D48 for ; Mon, 1 Nov 2004 03:04:07 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.12.11/8.12.11) with ESMTP id iA1346u5001899 for ; Mon, 1 Nov 2004 03:04:06 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.12.11/8.12.11/Submit) id iA13461F001898; Mon, 1 Nov 2004 03:04:06 GMT (envelope-from nobody) Message-Id: <200411010304.iA13461F001898@www.freebsd.org> Date: Mon, 1 Nov 2004 03:04:06 GMT From: "Simson L. Garfinkel" To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/73369: on-board firewire unreliable with Asus K8V SE motherboard and AMD64 FreeBSD 5.3 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 03:10:11 -0000 >Number: 73369 >Category: amd64 >Synopsis: on-board firewire unreliable with Asus K8V SE motherboard and AMD64 FreeBSD 5.3 >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Nov 01 03:10:10 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Simson L. Garfinkel >Release: 5.3 >Organization: MIT >Environment: FreeBSD r3.nitroba.com 5.3-RC1 FreeBSD 5.3-RC1 #0: Sat Oct 30 13:05:38 EDT 2004 simsong@r3.nitroba.com:/usr/src/sys/amd64/compile/R3 amd64 >Description: I don't know if this is worth fixing or not, but it is certainly worth documenting. I hav e abrand new AMD64 machine with a K8V SE motherboard. It's an amazing motherboard with an 800 Mhz system bus, 5 pci slots, a wifi slot, 2 Ultra ATA 133 connectors, 2 serial ATA connectors, 8 USB 2.0 ports, built-in gigabit, and 2 Firewire ports. I have a bunch of firewire drives. WHen I attach the drives to the motherboard, it gets the bus reset but it usually doesn't create the /dev entries for the drives. I try resetting the bus with the fwcontrol command. That doesn't work either. Here is what is printed on the console: fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc1, gen=2, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) firewire0: bus manager 1 (me) fwohci0: txd err= 3 miss Ack err firewire0: bus_explore node=0 addr=0x400 resp=22 retry=1 fwohci0: txd err= 3 miss Ack err firewire0: bus_explore node=0 addr=0x400 resp=22 retry=2 fwohci0: txd err= 3 miss Ack err firewire0: bus_explore node=0 addr=0x400 resp=22 retry=3 fwohci0: txd err= 3 miss Ack err firewire0: bus_explore node=0 addr=0x400 resp=22 retry=4 firewire0: bus_explore failed for 1 nodes fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc1, gen=3, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) firewire0: bus manager 1 (me) fwohci0: txd err= 3 miss Ack err firewire0: bus_explore node=0 addr=0x400 resp=22 retry=1 fwohci0: txd err= 3 miss Ack err firewire0: bus_explore node=0 addr=0x400 resp=22 retry=2 fwohci0: txd err= 3 miss Ack err firewire0: bus_explore node=0 addr=0x400 resp=22 retry=3 fwohci0: txd err= 3 miss Ack err firewire0: bus_explore node=0 addr=0x400 resp=22 retry=4 firewire0: bus_explore failed for 1 nodes [simsong@r3 ~] 306 % I plug in a standard Firewire card and it works just fine. >How-To-Repeat: Buy this motherboard. Or don't. >Fix: Don't use the on-board firewire. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 1 03:10:13 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CD1616A4D0 for ; Mon, 1 Nov 2004 03:10:13 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75B3F43D54 for ; Mon, 1 Nov 2004 03:10:13 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id iA13ADuD019586 for ; Mon, 1 Nov 2004 03:10:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id iA13ADJg019585; Mon, 1 Nov 2004 03:10:13 GMT (envelope-from gnats) Date: Mon, 1 Nov 2004 03:10:13 GMT Message-Id: <200411010310.iA13ADJg019585@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Simson L. Garfinkel" Subject: Re: amd64/73360: sk0: watchdog timeout X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Simson L. Garfinkel" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 03:10:13 -0000 The following reply was made to PR amd64/73360; it has been noted by GNATS. From: "Simson L. Garfinkel" To: simsong@acm.org, freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: amd64/73360: sk0: watchdog timeout Date: Sun, 31 Oct 2004 22:06:09 -0500 update: I have plugged in a syskonect I had around the house; it is now sk1. I am seeing if the problem is specific to the on-board K8V SE's syskonect, or if the problem is for all of them. From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 1 03:11:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F249116A4CE; Mon, 1 Nov 2004 03:11:55 +0000 (GMT) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4845C43D1D; Mon, 1 Nov 2004 03:11:54 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.43 (FreeBSD)) id 1COSek-00098m-WD; Mon, 01 Nov 2004 11:14:55 +0800 Message-Id: <6.1.2.0.2.20041101110528.02b43b90@202.179.0.80> X-Sender: ganbold@micom.mng.net@202.179.0.80 X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Mon, 01 Nov 2004 11:11:32 +0800 To: Ken Smith From: Ganbold In-Reply-To: <20041031201950.GA99257@bobbi.cse.buffalo.edu> References: <20041031201950.GA99257@bobbi.cse.buffalo.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: freebsd-amd64@freebsd.org cc: scottl@freebsd.org Subject: Re: FreeBSD 5.3-RC2 Available X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 03:11:56 -0000 At 04:19 AM 11/1/2004, you wrote: > - A problem with extremely large memory allocations on amd64 was fixed. Did RC2 fix the problem related to ips driver? Is it worth to try RC2 on amd64 with 8GB machine? thanks in advance, Ganbold From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 1 03:59:44 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C29716A4CE; Mon, 1 Nov 2004 03:59:44 +0000 (GMT) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC0BE43D1F; Mon, 1 Nov 2004 03:59:43 +0000 (GMT) (envelope-from ganbold@micom.mng.net) Received: from [202.179.0.164] (helo=ganbold.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.43 (FreeBSD)) id 1COTP1-0009SB-GH; Mon, 01 Nov 2004 12:02:43 +0800 Message-Id: <6.1.2.0.2.20041101115617.02b58eb0@202.179.0.80> X-Sender: ganbold@micom.mng.net@202.179.0.80 X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Mon, 01 Nov 2004 11:59:25 +0800 To: Ken Smith From: Ganbold Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: freebsd-amd64@freebsd.org cc: scottl@freebsd.org Subject: Re: FreeBSD 5.3-RC2 Available X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 03:59:44 -0000 At 04:19 AM 11/1/2004, you wrote: > - A problem with extremely large memory allocations on amd64 was fixed. It seems like the ips driver problem still exist in RC2. I tried RC2 on amd64 with 8GB machine and still same problem exists as before. File system gets corrupted with 8GB RAM. Ganbold From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 1 04:18:39 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D9ED16A4CE for ; Mon, 1 Nov 2004 04:18:39 +0000 (GMT) Received: from web12822.mail.yahoo.com (web12822.mail.yahoo.com [216.136.174.203]) by mx1.FreeBSD.org (Postfix) with SMTP id DDA5543D46 for ; Mon, 1 Nov 2004 04:18:38 +0000 (GMT) (envelope-from neshort@yahoo.com) Message-ID: <20041101041838.96004.qmail@web12822.mail.yahoo.com> Received: from [216.198.97.39] by web12822.mail.yahoo.com via HTTP; Sun, 31 Oct 2004 20:18:38 PST Date: Sun, 31 Oct 2004 20:18:38 -0800 (PST) From: Neil Short To: gnats@freebsd.org, amd64@freebsd.org In-Reply-To: <4185196F.5030705@verizon.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: andrew.lankford@verizon.net Subject: Re: amd64/67745: boot fails on compaq presario r3000z X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 04:18:39 -0000 Understandable. From my (and several other people's - who have this equipment) perspective, it is really-really hard to install when you have to hack the installable CD first - and try to remember to swap kernels at the end of the install - and not accidentally replace it with the wrong one - and before the first boot. -Neil --- Andrew Lankford wrote: > >Because it removes code that does something on > other machines. No one > >has done a good analysis of why this fixes booting > on a few models of > >laptops. Thus we don't understand the > consequences of this change. > >-- David (obrien@FreeBSD.org) > > On account of the fact that my machine was no longer > bootable shortly > after the long awaited kernel module loading > improvements (due to > acpi/keyboard driver/whoknowswhat), I've been > reluctant to fiddle around > further with Kim's patch. I just noticed though > that I never tried > compiling the kernel on any machine with KBDIO_DEBUG > set to some high > value (I take it you can do this from buildkernel?). > Maybe that would > be useful, provided that the tester doesn't set it > to a value high > enough to bring the machine to its knees. > > In the end, I suppose some major FreeBSDer will do a > keyboard code > overhaul eventually as "atkbd0: [GIANT-LOCKED]" > still shows up on my p3 > machine boot log. Then everything will be peachy or > peachy/much > worse/peachy/much much worse/peachy... > > Andrew Lankford > ===== If history always begins this morning, the world holds exciting surprises around every corner (241). --Ann Coulter. Treason. __________________________________ Do you Yahoo!? Yahoo! Mail Address AutoComplete - You start. We finish. http://promotions.yahoo.com/new_mail From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 1 07:41:07 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CEA316A4CE for ; Mon, 1 Nov 2004 07:41:07 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 945B543D1F for ; Mon, 1 Nov 2004 07:41:06 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id A64E41FF9A8; Mon, 1 Nov 2004 08:41:04 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id C8AD01FF9AC; Mon, 1 Nov 2004 08:41:02 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 138A0153C4; Mon, 1 Nov 2004 07:36:22 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 083E315384; Mon, 1 Nov 2004 07:36:23 +0000 (UTC) Date: Mon, 1 Nov 2004 07:36:22 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: John-Mark Gurney In-Reply-To: <20041101005735.GO22681@funkthat.com> Message-ID: References: <200410312115.i9VLFisD013971@www.freebsd.org> <20041101005735.GO22681@funkthat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: freebsd-amd64@freebsd.org Subject: Re: amd64/73360: sk0: watchdog timeout X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 07:41:07 -0000 Hi, > Hey, thanks for pointing this patch out... yupp many thanks. I hadn't seen this one either:( > I've slightly modified it > to better handle IFF_OACTIVE since it's possible to clear the flag when > it shouldn't be... *hmm* if I tell you that I see the intr for txeof fired regularly - also on "hangs" - but I don't see the intr for rxeof whouldn't that be the opposite situation? > If people see this patch improve things, I'll commit it... I haven't > tested w/ my sk card yet though... anyway I am going to test this patch ASAP on my ASUS K8V SE Deluxe; I also have an excellent esting setup here. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 1 08:27:06 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 363D216A4CE for ; Mon, 1 Nov 2004 08:27:06 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95AD443D1F for ; Mon, 1 Nov 2004 08:27:05 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 65E1B1FF9AC; Mon, 1 Nov 2004 09:27:04 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 659741FF9A8; Mon, 1 Nov 2004 09:27:02 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 51984153C4; Mon, 1 Nov 2004 08:26:46 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 44F1915384; Mon, 1 Nov 2004 08:26:47 +0000 (UTC) Date: Mon, 1 Nov 2004 08:26:45 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: John-Mark Gurney In-Reply-To: <20041101005735.GO22681@funkthat.com> Message-ID: References: <200410312115.i9VLFisD013971@www.freebsd.org> <20041101005735.GO22681@funkthat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: "Wolfgang S. Rupprecht" cc: freebsd-amd64@freebsd.org Subject: Re: amd64/73360: sk0: watchdog timeout X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 08:27:06 -0000 On Sun, 31 Oct 2004, John-Mark Gurney wrote: > Wolfgang S. Rupprecht wrote this message on Sun, Oct 31, 2004 at 14:17 -0800: [patch] > > Hey, thanks for pointing this patch out... I've slightly modified it > to better handle IFF_OACTIVE since it's possible to clear the flag when > it shouldn't be... > > If people see this patch improve things, I'll commit it... I haven't > tested w/ my sk card yet though... it didn't improve the situtation here but made it worse:( that patch itself is not compileable that way anyway. sc is not defined in txeof. > Index: if_sk.c > =================================================================== > RCS file: /home/ncvs/src/sys/pci/if_sk.c,v > retrieving revision 1.86 > diff -u -r1.86 if_sk.c > --- if_sk.c 20 Aug 2004 06:22:04 -0000 1.86 > +++ if_sk.c 1 Nov 2004 00:54:20 -0000 > @@ -1816,11 +1816,13 @@ > } > > /* Transmit */ > - sc_if->sk_cdata.sk_tx_prod = idx; > - CSR_WRITE_4(sc, sc_if->sk_tx_bmu, SK_TXBMU_TX_START); > + if (idx != sc_if->sk_cdata.sk_tx_prod) { > + sc_if->sk_cdata.sk_tx_prod = idx; > + CSR_WRITE_4(sc, sc_if->sk_tx_bmu, SK_TXBMU_TX_START); > > - /* Set a timeout in case the chip goes out to lunch. */ > - ifp->if_timer = 5; > + /* Set a timeout in case the chip goes out to lunch. */ > + ifp->if_timer = 5; > + } > SK_IF_UNLOCK(sc_if); > > return; [pasted in] @@ -1937,10 +1940,12 @@ static void sk_txeof(sc_if) struct sk_if_softc *sc_if; { + struct sk_softc *sc; struct sk_tx_desc *cur_tx = NULL; struct ifnet *ifp; u_int32_t idx; + sc = sc_if->sk_softc; ifp = &sc_if->arpcom.ac_if; /* > @@ -1960,13 +1962,15 @@ > } > sc_if->sk_cdata.sk_tx_cnt--; > SK_INC(idx, SK_TX_RING_CNT); > - ifp->if_timer = 0; > } > > - sc_if->sk_cdata.sk_tx_cons = idx; > - > - if (cur_tx != NULL) > + if (sc_if->sk_cdata.sk_tx_cnt == 0) { > + ifp->if_timer = 0; > ifp->if_flags &= ~IFF_OACTIVE; > + } else /* nudge chip to keep tx ring moving */ > + CSR_WRITE_4(sc, sc_if->sk_tx_bmu, SK_TXBMU_TX_START); > + > + sc_if->sk_cdata.sk_tx_cons = idx; > > return; > } if I add two printfs to each rxeof,txeof to print i resp. idx this slows down processing to about 120KB/s and make the thing live for about 3-6 MB transferred before "hanging". The output of the time the hanging starts looks like that: legend: tx = txeof rx = rxeof s = start e = end i = i,idx output: rx s i=47 rx e i=54 tx s i=104 tx e i=126 rx s i=54 rx e i=60 tx s i=126 tx e i=150 rx s i=60 rx e i=67 tx s i=150 tx e i=161 rx s i=67 rx e i=71 tx s i=161 tx e i=163 tx s i=163 tx e i=190 rx s i=71 rx e i=78 tx s i=190 tx e i=217 rx s i=78 rx e i=82 tx s i=217 tx e i=230 tx s i=230 tx e i=232 tx s i=232 tx e i=235 tx s i=235 tx e i=237 tx s i=237 tx e i=240 tx s i=240 tx e i=242 tx s i=242 tx e i=244 tx s i=244 tx e i=247 tx s i=247 tx e i=249 tx s i=249 tx e i=251 tx s i=251 tx e i=254 tx s i=254 tx e i=256 tx s i=256 tx e i=258 tx s i=258 tx e i=260 tx s i=260 tx e i=263 tx s i=263 tx e i=265 tx s i=265 tx e i=267 tx s i=267 tx e i=270 tx s i=270 tx e i=272 tx s i=272 tx e i=275 tx s i=275 tx e i=277 tx s i=277 tx e i=280 The funny thing is if I go into the "also hanging" xterm where I logged in on that amd64 with ssh and started the ftp put from and then hit some keys like enter I will see Rx intr fired again: rx s i=82 rx e i=83 tx s i=297 tx e i=298 rx s i=83 rx e i=84 tx s i=298 tx e i=301 rx s i=84 rx e i=85 tx s i=301 tx e i=304 rx s i=85 rx e i=86 tx s i=304 tx e i=305 tx s i=305 tx e i=308 tx s i=308 tx e i=311 rx s i=86 rx e i=87 tx s i=311 tx e i=313 rx s i=87 rx e i=88 tx s i=313 tx e i=314 -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 1 08:59:22 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from [IPv6:::1] (hub.freebsd.org [216.136.204.18]) by hub.freebsd.org (Postfix) with ESMTP id EDA9716A4CE; Mon, 1 Nov 2004 08:59:20 +0000 (GMT) Message-ID: <4185FB30.8060101@freebsd.org> Date: Mon, 01 Nov 2004 02:00:32 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ganbold References: <20041031201950.GA99257@bobbi.cse.buffalo.edu> <6.1.2.0.2.20041101110528.02b43b90@202.179.0.80> In-Reply-To: <6.1.2.0.2.20041101110528.02b43b90@202.179.0.80> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: obrien@FreeBSD.org cc: Ken Smith cc: freebsd-amd64@FreeBSD.org Subject: Re: FreeBSD 5.3-RC2 Available X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 08:59:22 -0000 Ganbold wrote: > At 04:19 AM 11/1/2004, you wrote: > >> - A problem with extremely large memory allocations on amd64 was >> fixed. > > > Did RC2 fix the problem related to ips driver? Is it worth to try RC2 on > amd64 with 8GB machine? > > thanks in advance, > > Ganbold > > No. Fixing it requires more work than can be done during the final stages of a release. Scott From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 1 11:01:59 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ACF6416A4D8 for ; Mon, 1 Nov 2004 11:01:59 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8734243D2D for ; Mon, 1 Nov 2004 11:01:59 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id iA1B1xst094164 for ; Mon, 1 Nov 2004 11:01:59 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id iA1B1v3b094158 for freebsd-amd64@freebsd.org; Mon, 1 Nov 2004 11:01:57 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 1 Nov 2004 11:01:57 GMT Message-Id: <200411011101.iA1B1v3b094158@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org Subject: Current problem reports assigned to you X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 11:01:59 -0000 Current FreeBSD problem reports Critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/10/27] amd64/73211 amd64 FAST_IPSEC broken on amd64 1 problem total. Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2003/11/26] amd64/59714 amd64 device timeout and ad0: WARNING - WRITE_D o [2004/06/09] amd64/67745 amd64 boot fails on compaq presario r3000z o [2004/07/28] amd64/69704 amd64 ext2/ext3 unstable in amd64 o [2004/07/28] amd64/69707 amd64 IPC32 dont work OK in amd64 FreeBSD o [2004/09/07] amd64/71471 amd64 Can not install 5.3beta3/amd64 on IBM eSe o [2004/10/04] amd64/72333 amd64 vinum doesn't scan for drives on slices o o [2004/10/28] amd64/73252 amd64 ad6: WARNING - READ_DMA interrupt was see o [2004/10/30] amd64/73322 amd64 unarchiving /etc to msdos fs locks up amd o [2004/10/31] amd64/73360 amd64 sk0: watchdog timeout o [2004/11/01] amd64/73369 amd64 on-board firewire unreliable with Asus K8 10 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2004/01/11] amd64/61209 amd64 ppc0: cannot reserve I/O port range o [2004/02/21] amd64/63188 amd64 ti(4) broken on amd64 o [2004/07/28] amd64/69705 amd64 IPC problem (msq_queues) o [2004/07/28] amd64/69709 amd64 ACPI enabled then floppy don't work (5.2. o [2004/07/28] amd64/69712 amd64 no DRI (hardware OpenGL) for ATI Radeon 9 o [2004/08/15] amd64/70500 amd64 bge driver for 3Com 3C996B on amd64 preve o [2004/09/12] amd64/71674 amd64 static libraries cannot be linked when bu o [2004/09/15] amd64/71753 amd64 DRI loads but fails to render on Radeon 9 o [2004/09/30] amd64/72213 amd64 No vesa device o [2004/10/10] amd64/72493 amd64 CD-Image of amd64-5.3-BETA6 missing files o [2004/10/11] amd64/72517 amd64 Minor Bug in /etc/login.access 11 problems total. From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 1 11:40:10 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B24A16A4CE; Mon, 1 Nov 2004 11:40:10 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id C291043D39; Mon, 1 Nov 2004 11:40:09 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id C88141FF9AC; Mon, 1 Nov 2004 12:40:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id C9A9C1FF9A8; Mon, 1 Nov 2004 12:40:05 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id A33141564A; Mon, 1 Nov 2004 11:36:01 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id A07A615384; Mon, 1 Nov 2004 11:36:02 +0000 (UTC) Date: Mon, 1 Nov 2004 11:36:02 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: freebsd-amd64@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: FreeBSD current mailing list Subject: if_sk patch to get more info from people with problems X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 11:40:10 -0000 Hi, a lot of people seem to have problems with if_sk. A lot of people consider it simply broken on some boards. Let's see if we can find out what problems happen for which people. - watchdog timeouts - rx/tx "hangs" - ... At [1] you can find a quick, dirty and ugly hack[2] (unverified to be implemented correctly in the last 5 minutes) to dump more VPD (vital product data) from those cards. It will print out sth like this (on may amd64 with ASUS K8V SE Deluxe): ! ... ! skc0: port 0xa800-0xa8ff mem 0xf7b00000-0xf7b03fff irq 17 at device 10.0 on pci0 ! skc0: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter ! skc0: PN: Yukon 88E8001 ! skc0: EC: Rev. 1.3 ! skc0: MN: Marvell ! skc0: SN: AbCdEfG334454 ! sk0: on skc0 ! ... PN is Part Number EC is Engineering Change level MN is the Manufacture ID SN is Serial Number would be interesting to see if we can find more similarities. [1] http://sources.zabbadoz.net/freebsd/patchset/EXPERIMENTAL/if_sk_vpd.diff [2] I am still not checking VPD checksum; nor should this handling be done in the driver because it's a PCI thing and should be cleanly implemented somewhere else. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 1 12:36:24 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76C5616A4CE for ; Mon, 1 Nov 2004 12:36:24 +0000 (GMT) Received: from out001.verizon.net (out001pub.verizon.net [206.46.170.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDD4943D1D for ; Mon, 1 Nov 2004 12:36:23 +0000 (GMT) (envelope-from pgermoff@verizon.net) Received: from HPa643n ([68.239.116.24]) by out001.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041101123623.JSOP23519.out001.verizon.net@HPa643n> for ; Mon, 1 Nov 2004 06:36:23 -0600 Message-ID: <000601c4c00f$6dc97c20$0200a8c0@HPa643n> From: "Paul Gerasimoff" To: Date: Mon, 1 Nov 2004 07:36:33 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Authentication-Info: Submitted using SMTP AUTH at out001.verizon.net from [68.239.116.24] at Mon, 1 Nov 2004 06:36:23 -0600 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Suscribe X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 12:36:24 -0000 Please send any replies to pgermoff@ieee.org From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 1 13:22:55 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5002816A4CE for ; Mon, 1 Nov 2004 13:22:55 +0000 (GMT) Received: from mta1.siol.net (pegasus.siol.net [193.189.160.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C5AF43D4C for ; Mon, 1 Nov 2004 13:22:53 +0000 (GMT) (envelope-from tomaz.borstnar@over.net) Received: from edge1.siol.net ([10.10.10.210]) by mta1.siol.net with ESMTP id <20041101132251.XUNT8856.mta1.siol.net@edge1.siol.net> for ; Mon, 1 Nov 2004 14:22:51 +0100 Received: from game.over.net ([193.189.169.9]) by edge1.siol.net with ESMTP id <20041101132250.DXRA3658.edge1.siol.net@game.over.net> for ; Mon, 1 Nov 2004 14:22:50 +0100 Received: from BSN-77-70-7.dsl.siol.net ([193.77.70.7]:20365 "EHLO zvezek.over.net") by game.over.net with ESMTP id ; Mon, 1 Nov 2004 14:22:41 +0100 Message-Id: <6.1.2.0.0.20041101141735.0cf68bc0@193.189.169.9> X-Sender: tmail@193.189.169.9 X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Mon, 01 Nov 2004 14:22:59 +0100 To: freebsd-amd64@freebsd.org From: Tomaz Borstnar In-Reply-To: <4181F8AF.8030800@freebsd.org> References: <6.1.2.0.2.20041029101540.02b28eb0@202.179.0.80> <20041029033416.GC13963@dragon.nuxi.com> <6.1.2.0.2.20041029115322.02b43510@202.179.0.80> <4181F8AF.8030800@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-OverNet-MailScanner-Information: Contact mailscanner@over.net for more information X-OverNet-MailScanner: Found to be clean X-OverNet-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.192, required 5, BAYES_00 -4.90, RCVD_IN_NJABL_DUL 1.71) X-MailScanner-From: tomaz.borstnar@over.net Subject: Re: FreeBSD 5.3 problem on Dual AMD64 2.2GHz with 8GB RAM X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 13:22:55 -0000 At 09:00 29.10.2004, Scott Long wrote: >The ips driver looks like it will fail under heavy load when more than 4GB >of RAM is present. I tries to force busdma to not defer requests >when the bounce page reserve is low, but that looks to be broken and >will result in corrupted commands. could this be the reason for my failure to install any FreeBSD 5.3 version to same type of machine (eserver 325) except with 5 gigs of RAM? When it appeared to be working it ALWYAS crashed while writing files to filesystem - UFS1, UFS2, softupdates - nothing changed this. Tomaz From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 1 16:33:49 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFCD816A4CE; Mon, 1 Nov 2004 16:33:49 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FCA743D55; Mon, 1 Nov 2004 16:33:49 +0000 (GMT) (envelope-from obrien@FreeBSD.org) Received: from freefall.freebsd.org (obrien@localhost [127.0.0.1]) iA1GXnZA036304; Mon, 1 Nov 2004 16:33:49 GMT (envelope-from obrien@freefall.freebsd.org) Received: (from obrien@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id iA1GXnsS036300; Mon, 1 Nov 2004 16:33:49 GMT (envelope-from obrien) Date: Mon, 1 Nov 2004 16:33:49 GMT From: "David E. O'Brien" Message-Id: <200411011633.iA1GXnsS036300@freefall.freebsd.org> To: obrien@FreeBSD.org, freebsd-amd64@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: amd64/72517: Minor Bug in /etc/login.access X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 16:33:49 -0000 Synopsis: Minor Bug in /etc/login.access Responsible-Changed-From-To: freebsd-amd64->freebsd-bugs Responsible-Changed-By: obrien Responsible-Changed-When: Mon Nov 1 16:32:49 GMT 2004 Responsible-Changed-Why: Misfiled - isn't AMD64 specific. http://www.freebsd.org/cgi/query-pr.cgi?pr=72517 From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 1 16:41:10 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 058A616A4CE; Mon, 1 Nov 2004 16:41:10 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D61B843D4C; Mon, 1 Nov 2004 16:41:09 +0000 (GMT) (envelope-from obrien@FreeBSD.org) Received: from freefall.freebsd.org (obrien@localhost [127.0.0.1]) iA1Gf91I036565; Mon, 1 Nov 2004 16:41:09 GMT (envelope-from obrien@freefall.freebsd.org) Received: (from obrien@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id iA1Gf9TN036561; Mon, 1 Nov 2004 16:41:09 GMT (envelope-from obrien) Date: Mon, 1 Nov 2004 16:41:09 GMT From: "David E. O'Brien" Message-Id: <200411011641.iA1Gf9TN036561@freefall.freebsd.org> To: mrkvrg@acm.org, obrien@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: amd64/72213: No vesa device X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 16:41:10 -0000 Synopsis: No vesa device State-Changed-From-To: open->closed State-Changed-By: obrien State-Changed-When: Mon Nov 1 16:34:02 GMT 2004 State-Changed-Why: AMD64 has no vm86 (virtual machine 8086) mode. This means we don't have VESA capabilities to use to program the VGA device - vm86 lets you ask the video BIOS to do it for you. Someone would need to write code to program the vga registers directly in order to get the various VGA modes on FreeBSD/AMD64. http://www.freebsd.org/cgi/query-pr.cgi?pr=72213 From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 1 16:43:03 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F9FF16A4CE; Mon, 1 Nov 2004 16:43:03 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D90843D4C; Mon, 1 Nov 2004 16:43:03 +0000 (GMT) (envelope-from obrien@FreeBSD.org) Received: from freefall.freebsd.org (obrien@localhost [127.0.0.1]) iA1Gh33f036638; Mon, 1 Nov 2004 16:43:03 GMT (envelope-from obrien@freefall.freebsd.org) Received: (from obrien@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id iA1Gh3NA036634; Mon, 1 Nov 2004 16:43:03 GMT (envelope-from obrien) Date: Mon, 1 Nov 2004 16:43:03 GMT From: "David E. O'Brien" Message-Id: <200411011643.iA1Gh3NA036634@freefall.freebsd.org> To: pete@twisted.org.uk, obrien@FreeBSD.org, freebsd-amd64@FreeBSD.org Subject: Re: amd64/71674: static libraries cannot be linked when building shared libraries X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 16:43:03 -0000 Synopsis: static libraries cannot be linked when building shared libraries State-Changed-From-To: open->analyzed State-Changed-By: obrien State-Changed-When: Mon Nov 1 16:41:30 GMT 2004 State-Changed-Why: The reasoning for the issue has been determined. http://www.freebsd.org/cgi/query-pr.cgi?pr=71674 From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 1 16:46:12 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D277216A4CE; Mon, 1 Nov 2004 16:46:12 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B11E543D1D; Mon, 1 Nov 2004 16:46:12 +0000 (GMT) (envelope-from obrien@FreeBSD.org) Received: from freefall.freebsd.org (obrien@localhost [127.0.0.1]) iA1GkCbD036724; Mon, 1 Nov 2004 16:46:12 GMT (envelope-from obrien@freefall.freebsd.org) Received: (from obrien@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id iA1GkCmW036720; Mon, 1 Nov 2004 16:46:12 GMT (envelope-from obrien) Date: Mon, 1 Nov 2004 16:46:12 GMT From: "David E. O'Brien" Message-Id: <200411011646.iA1GkCmW036720@freefall.freebsd.org> To: obrien@FreeBSD.org, freebsd-amd64@FreeBSD.org, kensmith@FreeBSD.org Subject: Re: amd64/72493: CD-Image of amd64-5.3-BETA6 missing files X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 16:46:12 -0000 Synopsis: CD-Image of amd64-5.3-BETA6 missing files Responsible-Changed-From-To: freebsd-amd64->kensmith Responsible-Changed-By: obrien Responsible-Changed-When: Mon Nov 1 16:43:13 GMT 2004 Responsible-Changed-Why: Reassigned to a Release Engineer. Also, there is no linux.ko -- the linux32 support must be statically compiled into the kernel. So this isn't a bug. Also it isn't as usable as in alpha and i386 yet. It should be taken as an experimental peice of functionality at this time. http://www.freebsd.org/cgi/query-pr.cgi?pr=72493 From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 1 19:31:27 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CBE716A501 for ; Mon, 1 Nov 2004 19:31:27 +0000 (GMT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB32143D31 for ; Mon, 1 Nov 2004 19:31:24 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 10134 invoked from network); 1 Nov 2004 19:31:24 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 1 Nov 2004 19:31:24 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iA1JV42S061830; Mon, 1 Nov 2004 14:31:19 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org, obrien@FreeBSD.org Date: Mon, 1 Nov 2004 15:18:13 -0500 User-Agent: KMail/1.6.2 References: <200410301940.i9UJeTkY081142@freefall.freebsd.org> <20041031061217.GA56606@dragon.nuxi.com> In-Reply-To: <20041031061217.GA56606@dragon.nuxi.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411011518.13026.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Nicolas Blais Subject: Re: amd64/67745: boot fails on compaq presario r3000z X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 19:31:27 -0000 On Sunday 31 October 2004 01:12 am, David O'Brien wrote: > On Sat, Oct 30, 2004 at 07:40:29PM +0000, Nicolas Blais wrote: > > How come the patch exists.... works perfectly.... and isn't being > > commited? > > Because it removes code that does something on other machines. No one > has done a good analysis of why this fixes booting on a few models of > laptops. Thus we don't understand the consequences of this change. We could add a flag to the atkbd driver so that the probe could be turned off via hints. That at least wouldn't require a custom kernel for installing, etc. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Mon Nov 1 23:56:58 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B4D016A4CE; Mon, 1 Nov 2004 23:56:58 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C3C743D3F; Mon, 1 Nov 2004 23:56:55 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iA1NupBe078311; Tue, 2 Nov 2004 10:26:52 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Tue, 2 Nov 2004 10:26:42 +1030 User-Agent: KMail/1.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart7967569.E0LmVEa7TJ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411021026.50163.doconnor@gsoft.com.au> X-Spam-Score: -2.8 () IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_01_02,USER_AGENT X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: FreeBSD current mailing list cc: freebsd-amd64@freebsd.org Subject: Re: if_sk patch to get more info from people with problems X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Nov 2004 23:56:58 -0000 --nextPart7967569.E0LmVEa7TJ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Mon, 1 Nov 2004 22:06, Bjoern A. Zeeb wrote: > Hi, > > a lot of people seem to have problems with if_sk. A lot of people > consider it simply broken on some boards. > > Let's see if we can find out what problems happen for which people. > - watchdog timeouts > - rx/tx "hangs" > - ... I have a 4.10 system and I get rx/tx hangs, I applied your patch (small=20 offsets) and this is the result.. skc0: port 0xc000-0xc0ff mem 0xfb010000-0xfb013f= ff irq 5 at device 1.0 on pci2 skc0: SysKonnect FDDI PCI Adapter SK-5844 (SK-NET FDDI-LP64 DAS) skc0: PN: SK-5844 skc0: EC: Rev. 1.0 skc0: MN: SysKonnect skc0: SN: L6D10S8000000 sk0: on skc0 sk0: Ethernet address: 00:04:61:67:b2:76 miibus0: on sk0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart7967569.E0LmVEa7TJ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBhs1C5ZPcIHs/zowRAmcoAJkBsG1X0rfBnklZbGrENpL4ssRdOACfUv8T MMKp0r+IO6PuRHa+YigNdiw= =YdDS -----END PGP SIGNATURE----- --nextPart7967569.E0LmVEa7TJ-- From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 2 01:21:34 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D28116A4CE; Tue, 2 Nov 2004 01:21:34 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F33843D64; Tue, 2 Nov 2004 01:21:33 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iA21LTmg081000; Tue, 2 Nov 2004 11:51:30 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Tue, 2 Nov 2004 11:51:29 +1030 User-Agent: KMail/1.7 References: <200411021026.50163.doconnor@gsoft.com.au> In-Reply-To: <200411021026.50163.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1985641.SPCDK8IT74"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411021151.29488.doconnor@gsoft.com.au> X-Spam-Score: -2.5 () IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: FreeBSD current mailing list cc: freebsd-amd64@freebsd.org Subject: Re: if_sk patch to get more info from people with problems X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Nov 2004 01:21:34 -0000 --nextPart1985641.SPCDK8IT74 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, 2 Nov 2004 10:26, Daniel O'Connor wrote: > I have a 4.10 system and I get rx/tx hangs, I applied your patch (small > offsets) and this is the result.. > > skc0: port 0xc000-0xc0ff mem > 0xfb010000-0xfb013fff irq 5 at device 1.0 on pci2 skc0: SysKonnect FDDI P= CI > Adapter SK-5844 (SK-NET FDDI-LP64 DAS) > skc0: PN: SK-5844 > skc0: EC: Rev. 1.0 > skc0: MN: SysKonnect > skc0: SN: L6D10S8000000 > sk0: on skc0 > sk0: Ethernet address: 00:04:61:67:b2:76 > miibus0: on sk0 > ukphy0: on miibus0 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Oh and this is on an Epox 4PDA5+ motherboard (it's the onboard interface) The PHY is.. Nov 2 00:12:06 fts /kernel: ukphy0: = on miibus0 Nov 2 00:12:06 fts /kernel: ukphy0: OUI 0x005043, model 0x0002, rev. 5 Nov 2 00:12:06 fts /kernel: ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100b= aseTX-FDX, auto I had a go at MFC'ing e1000phy but I couldn't manage it :( =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1985641.SPCDK8IT74 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBhuEZ5ZPcIHs/zowRAvoAAJ9kwYxRoFJefvgyu6NU3k1bXitoIwCdE3hC nZ7Aw/0voCl4EV1ZqGChZGk= =4C09 -----END PGP SIGNATURE----- --nextPart1985641.SPCDK8IT74-- From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 2 09:25:11 2004 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DB3016A4CE for ; Tue, 2 Nov 2004 09:25:11 +0000 (GMT) Received: from mail.sbb.co.yu (mail.sbb.co.yu [82.117.194.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91AD743D41 for ; Tue, 2 Nov 2004 09:25:10 +0000 (GMT) (envelope-from ggajic@mail.sbb.co.yu) Received: from mail.sbb.co.yu (mail.sbb.co.yu [82.117.194.7]) by mail.sbb.co.yu (8.12.10/8.12.10) with ESMTP id iA29P3PO075221 for ; Tue, 2 Nov 2004 10:25:03 +0100 (CET) Date: Tue, 2 Nov 2004 10:25:03 +0100 (CET) From: Goran Gajic To: freebsd-amd64@www.freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sbb.co.yu-MailScanner-Information: Please contact the ISP for more information X-Sbb.co.yu-MailScanner: Found to be clean Subject: sk driver works fine 5.3rc2 - amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Nov 2004 09:25:11 -0000 Hi, I have reported problems with sk driver in FreeBSD 5.3RC1 on amd64 on Fujitsu Siemens Celsisu (dual amd64 box with 4 GB memory). I have tried new 5.3RC2 and now sk driver works fine. No crashes for last 24h. However I have noticed that SMP is disabled in GENERIC kernel (on amd64). I have recompiled kernel with SMP enabled, but machine also works fine for last 24h - no crashes so far. I have also tested 5.3RC1 on single processor i386 and sk driver works fine. Whatever problem was seems it has been fixed in RC2. Regards, Goran Gajic From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 2 16:29:59 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E083216A4CE for ; Tue, 2 Nov 2004 16:29:59 +0000 (GMT) Received: from scii.nl (217-19-24-25.dsl.cambrium.nl [217.19.24.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 420A743D3F for ; Tue, 2 Nov 2004 16:29:57 +0000 (GMT) (envelope-from albi@scii.nl) Received: by scii.nl (Postfix, from userid 1004) id 8F8BE9B560; Tue, 2 Nov 2004 17:36:32 +0100 (CET) Date: Tue, 2 Nov 2004 17:36:32 +0100 From: albi@scii.nl To: freebsd-amd64@freebsd.org Message-ID: <20041102163632.GA16337@scii.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i Subject: Getting Qemu to compile on AMD64. X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Nov 2004 16:30:00 -0000 hi, i'd love to get qemu to work on an AMD64-machine running FreeBSD 5.3-STABLE and gcc 3.4.2 the following happens : /usr/ports/emulators/qemu/work/qemu-snapshot-2004-10-20_23/target-i386/op.c:2091: warning: cast to pointer from integer of different size /usr/ports/emulators/qemu/work/qemu-snapshot-2004-10-20_23/target-i386/op.c: In function _fnstenv_A0': /usr/ports/emulators/qemu/work/qemu-snapshot-2004-10-20_23/target-i386/op.c:2140: warning: cast to pointer from integer of different size /usr/ports/emulators/qemu/work/qemu-snapshot-2004-10-20_23/target-i386/op.c: In function _fldenv_A0': /usr/ports/emulators/qemu/work/qemu-snapshot-2004-10-20_23/target-i386/op.c:2145: warning: cast to pointer from integer of different size /usr/ports/emulators/qemu/work/qemu-snapshot-2004-10-20_23/target-i386/op.c: In function _fnsave_A0': /usr/ports/emulators/qemu/work/qemu-snapshot-2004-10-20_23/target-i386/op.c:2150: warning: cast to pointer from integer of different size /usr/ports/emulators/qemu/work/qemu-snapshot-2004-10-20_23/target-i386/op.c: In function _frstor_A0': /usr/ports/emulators/qemu/work/qemu-snapshot-2004-10-20_23/target-i386/op.c:2155: warning: cast to pointer from integer of different size /usr/ports/emulators/qemu/work/qemu-snapshot-2004-10-20_23/target-i386/op.c: In function _divw_AX_T0': /usr/ports/emulators/qemu/work/qemu-snapshot-2004-10-20_23/target-i386/op.c:301: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See for instructions. gmake[1]: *** [op.o] Error 1 gmake[1]: Leaving directory /usr/ports/emulators/qemu/work/qemu-snapshot-2004-10-20_23/i386-softmmu' gmake: *** [all] Error 1 *** Error code 2 Stop in /usr/ports/emulators/qemu. ======================================================= the mentioned http://gcc.gnu.org/bugs.html asks for : =++++++++++++++++++++++++++++++++ What we need Please include in your bug report all of the following items, the first three of which can be obtained from the output of gcc -v: * the exact version of GCC; * the system type; * the options given when GCC was configured/built; * the complete command line that triggers the bug; * the compiler output (error messages, warnings, etc.); and * the preprocessed file (*.i*) that triggers the bug, generated by adding -save-temps to the complete compilation command, or, in the case of a bug report for the GNAT front end, a complete set of source files (see below). =+++++++++++++++++++++++++++++++ Can someone tell me how to proceed ? e.g. how find the "complete command line that triggers the bug" ? One other question is how to try with other gcc-versions(3.4.3 and 4.0-snapshot) ? From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 2 17:56:45 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C3DC16A4CE for ; Tue, 2 Nov 2004 17:56:45 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA0E543D46 for ; Tue, 2 Nov 2004 17:56:44 +0000 (GMT) (envelope-from peadar.edwards@gmail.com) Received: by rproxy.gmail.com with SMTP id 74so270513rnk for ; Tue, 02 Nov 2004 09:56:41 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=X4T9PyYvPYz0ypecJ1X/uor7ZPjihKs0BfSOk9yhLdTVVZptdB53XT0zjit/SbWztkkIG3IeyN79uIZVc9xeld6zOovynsD2Tb3WZRC3Oxv/OFsaj60UQN2RHGsdMYBBIdBqxIVmHnVxPBEXH2GRkwpJ273PoRJd2KslXzzmRt8= Received: by 10.38.154.11 with SMTP id b11mr202865rne; Tue, 02 Nov 2004 09:56:40 -0800 (PST) Received: by 10.38.149.43 with HTTP; Tue, 2 Nov 2004 09:56:40 -0800 (PST) Message-ID: <34cb7c8404110209563fc01498@mail.gmail.com> Date: Tue, 2 Nov 2004 17:56:40 +0000 From: Peter Edwards To: "Bjoern A. Zeeb" In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: cc: peadar@freebsd.org cc: FreeBSD current mailing list cc: freebsd-amd64@freebsd.org Subject: Re: if_sk patch to get more info from people with problems X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Peter Edwards List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Nov 2004 17:56:45 -0000 Ok, I don't have this hardware, but dumb question: A (very) quick look at the source reveals that buffers are allocated via sk_rxeof()->sk_newbuf()->sk_jalloc() in the interrupt receive function, with the softc lock held in sk_rxeof(). They're freed by the mbuf system via a call to sk_jfree(), but that doesn't hold the SK_LOCK. Is this possibly the source of the corruption problems? What am I missing? This compiles, anyway :-) --- /tmp/if_sk.c Tue Nov 2 17:49:26 2004 +++ if_sk.c Tue Nov 2 17:52:20 2004 @@ -1115,12 +1115,14 @@ if ((i < 0) || (i >= SK_JSLOTS)) panic("sk_jfree: asked to free buffer that we don't manage!"); + SK_LOCK(sc_if->sk_softc); entry = SLIST_FIRST(&sc_if->sk_jinuse_listhead); if (entry == NULL) panic("sk_jfree: buffer not in use!"); entry->slot = i; SLIST_REMOVE_HEAD(&sc_if->sk_jinuse_listhead, jpool_entries); SLIST_INSERT_HEAD(&sc_if->sk_jfree_listhead, entry, jpool_entries); + SK_UNLOCK(sc_if->sk_softc); return; } From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 2 19:08:54 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E4A016A4CF for ; Tue, 2 Nov 2004 19:08:54 +0000 (GMT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04D0B43D5A for ; Tue, 2 Nov 2004 19:08:54 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 22455 invoked from network); 2 Nov 2004 19:08:53 -0000 Received: from gate.funkthat.com (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 2 Nov 2004 19:08:53 -0000 Received: from hydrogen.funkthat.com (abufwd@localhost.funkthat.com [127.0.0.1])iA2J8qB6022730; Tue, 2 Nov 2004 11:08:53 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id iA2J8p8b022729; Tue, 2 Nov 2004 11:08:51 -0800 (PST) Date: Tue, 2 Nov 2004 11:08:51 -0800 From: John-Mark Gurney To: Peter Edwards Message-ID: <20041102190851.GR22681@funkthat.com> Mail-Followup-To: Peter Edwards , "Bjoern A. Zeeb" , peadar@freebsd.org, FreeBSD current mailing list , freebsd-amd64@freebsd.org References: <34cb7c8404110209563fc01498@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="wHh0aNzodMFDTGdO" Content-Disposition: inline In-Reply-To: <34cb7c8404110209563fc01498@mail.gmail.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: peadar@freebsd.org cc: FreeBSD current mailing list cc: freebsd-amd64@freebsd.org Subject: Re: if_sk patch to get more info from people with problems X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Nov 2004 19:08:54 -0000 --wHh0aNzodMFDTGdO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Peter Edwards wrote this message on Tue, Nov 02, 2004 at 17:56 +0000: > A (very) quick look at the source reveals that buffers are allocated > via sk_rxeof()->sk_newbuf()->sk_jalloc() in the interrupt receive > function, with the softc lock held in sk_rxeof(). > > They're freed by the mbuf system via a call to sk_jfree(), but that > doesn't hold the SK_LOCK. Is this possibly the source of the > corruption problems? What am I missing? > This compiles, anyway :-) Well, try the attached patch (it also includes my changes from a previous diff) that will see what happens... Make sure you have your kernel compiled with WITNESS and INVARIANTS... If you hit one of these asserts, make sure you post the back trace... Thanks for the testing.. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." --wHh0aNzodMFDTGdO Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="if_sk.diff" Index: if_sk.c =================================================================== RCS file: /home/ncvs/src/sys/pci/if_sk.c,v retrieving revision 1.87 diff -u -r1.87 if_sk.c --- if_sk.c 1 Nov 2004 17:21:04 -0000 1.87 +++ if_sk.c 2 Nov 2004 19:05:29 -0000 @@ -1076,6 +1076,8 @@ { struct sk_jpool_entry *entry; + SK_IF_LOCK_ASSERT(sc_if); + entry = SLIST_FIRST(&sc_if->sk_jfree_listhead); if (entry == NULL) { @@ -1108,6 +1110,8 @@ if (sc_if == NULL) panic("sk_jfree: didn't get softc pointer!"); + SK_IF_LOCK_ASSERT(sc_if); + /* calculate the slot this buffer belongs to */ i = ((vm_offset_t)buf - (vm_offset_t)sc_if->sk_cdata.sk_jumbo_buf) / SK_JLEN; @@ -1845,11 +1849,13 @@ } /* Transmit */ - sc_if->sk_cdata.sk_tx_prod = idx; - CSR_WRITE_4(sc, sc_if->sk_tx_bmu, SK_TXBMU_TX_START); + if (idx != sc_if->sk_cdata.sk_tx_prod) { + sc_if->sk_cdata.sk_tx_prod = idx; + CSR_WRITE_4(sc, sc_if->sk_tx_bmu, SK_TXBMU_TX_START); - /* Set a timeout in case the chip goes out to lunch. */ - ifp->if_timer = 5; + /* Set a timeout in case the chip goes out to lunch. */ + ifp->if_timer = 5; + } SK_IF_UNLOCK(sc_if); return; @@ -1989,13 +1995,15 @@ } sc_if->sk_cdata.sk_tx_cnt--; SK_INC(idx, SK_TX_RING_CNT); - ifp->if_timer = 0; } - sc_if->sk_cdata.sk_tx_cons = idx; - - if (cur_tx != NULL) + if (sc_if->sk_cdata.sk_tx_cnt == 0) { + ifp->if_timer = 0; ifp->if_flags &= ~IFF_OACTIVE; + } else /* nudge chip to keep tx ring moving */ + CSR_WRITE_4(sc, sc_if->sk_tx_bmu, SK_TXBMU_TX_START); + + sc_if->sk_cdata.sk_tx_cons = idx; return; } Index: if_skreg.h =================================================================== RCS file: /home/ncvs/src/sys/pci/if_skreg.h,v retrieving revision 1.22 diff -u -r1.22 if_skreg.h --- if_skreg.h 20 Aug 2004 06:22:04 -0000 1.22 +++ if_skreg.h 2 Nov 2004 19:05:29 -0000 @@ -1441,6 +1441,7 @@ #define SK_LOCK_ASSERT(_sc) mtx_assert(&(_sc)->sk_mtx, MA_OWNED) #define SK_IF_LOCK(_sc) SK_LOCK((_sc)->sk_softc) #define SK_IF_UNLOCK(_sc) SK_UNLOCK((_sc)->sk_softc) +#define SK_IF_LOCK_ASSERT(_sc) SK_LOCK_ASSERT((_sc)->sk_softc) /* Softc for each logical interface */ struct sk_if_softc { --wHh0aNzodMFDTGdO-- From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 2 19:16:34 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BA9816A4CE for ; Tue, 2 Nov 2004 19:16:34 +0000 (GMT) Received: from mail.komvista.lt (ns.komvista.lt [213.190.36.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E95243D1F for ; Tue, 2 Nov 2004 19:16:33 +0000 (GMT) (envelope-from ssmailys@komvista.lt) Received: by mail.komvista.lt (Postfix, from userid 23) id 308B9BDCA; Tue, 2 Nov 2004 22:16:17 +0200 (EET) Received: from [192.168.127.253] (omega64.komvista.lt [192.168.127.253]) by mail.komvista.lt (Postfix) with ESMTP id 4B277BDC9 for ; Tue, 2 Nov 2004 22:16:16 +0200 (EET) Message-ID: <4187EB23.1060407@komvista.lt> Date: Tue, 02 Nov 2004 22:16:35 +0200 From: Stasys Smailys User-Agent: Mozilla Thunderbird 0.8 (X11/20041102) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "[FreeBSD-AMD64]" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: ioctl() 64-bit issues X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Nov 2004 19:16:34 -0000 Hi, all! I think we have a problem here at least it seems so to me. Trying to fix an infinite loop that occured in usr.sbin/burncd/burncd.c when I have tried to blank cdrw disc I discovered that sys/ioccom.h [...] int ioctl(int, unsigned long, ...); [...] usr.sbin/burncd/burncd.c [...] int blank, pct, last = 0; [...] if (ioctl(fd, CDRIOCGETPROGRESS, &pct) == -1) err(EX_IOERR,"ioctl(CDRIOGETPROGRESS)"); [...] always returns a zero value in pct (pct == 0). By the way there is a typo in burncd.c: the second CDRIOCGETPROGRESS misses 'C'. Anyway it is not essential. As you can see by yourself in that case the loop becomes infinite. Further investigations showed me that pct gets overwritten every ioctl's call by CDRIOCGETPROGRESS constant's upper bytes. At the moment of ioctl's call the CDRIOCGETPROGRESS value is 0x0000004004636f. I suppose this is not the only case. May be this case and PR amd64/69704 (ext2/ext3 unstable in amd64) are interconnected somehow, because both use sys/ioccom.h. May be some others too. I don't know. Here is something to start: http://docsun.cites.uiuc.edu/sun_docs/C/solaris_9/SUNWdev/SOL64TRANS/p15.html -- WBR Stasys Smailys From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 2 19:31:32 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB90716A4CE for ; Tue, 2 Nov 2004 19:31:32 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id D267F43D2F for ; Tue, 2 Nov 2004 19:31:32 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id B23F82A8F1 for ; Tue, 2 Nov 2004 11:31:32 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 3C61FE2B3 for ; Tue, 2 Nov 2004 11:31:32 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.1/8.13.1) with ESMTP id iA2JVVUf006729; Tue, 2 Nov 2004 11:31:31 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id iA2JVUdI006728; Tue, 2 Nov 2004 11:31:30 -0800 (PST) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-amd64@freebsd.org Date: Tue, 2 Nov 2004 12:31:30 -0700 User-Agent: KMail/1.7 References: <4187EB23.1060407@komvista.lt> In-Reply-To: <4187EB23.1060407@komvista.lt> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411021131.30701.peter@wemm.org> cc: Stasys Smailys Subject: Re: ioctl() 64-bit issues X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Nov 2004 19:31:33 -0000 On Tuesday 02 November 2004 12:16 pm, Stasys Smailys wrote: > Hi, all! > > I think we have a problem here at least it seems so to me. Trying to > fix an infinite loop that occured in usr.sbin/burncd/burncd.c when I > have tried to blank cdrw disc I discovered that > > sys/ioccom.h > [...] > int ioctl(int, unsigned long, ...); > [...] > > usr.sbin/burncd/burncd.c > [...] > int blank, pct, last = 0; > [...] > if (ioctl(fd, CDRIOCGETPROGRESS, &pct) == -1) > > err(EX_IOERR,"ioctl(CDRIOGETPROGRESS)"); > [...] > > always returns a zero value in pct (pct == 0). By the way there is a > typo in burncd.c: the second CDRIOCGETPROGRESS misses 'C'. Anyway it > is not essential. As you can see by yourself in that case the loop > becomes infinite. Further investigations showed me that pct gets > overwritten every ioctl's call by CDRIOCGETPROGRESS constant's upper > bytes. At the moment of ioctl's call the CDRIOCGETPROGRESS value is > 0x0000004004636f. If you have a look at cdrio.h: #define CDRIOCGETPROGRESS _IOR('c', 111, int) And the implementation is: case CDRIOCGETPROGRESS: error = acd_get_progress(cdp, (int *)addr); Compare to: #define CDRIOCSENDCUE _IOW('c', 104, struct cdr_cuesheet) burncd.c: if (ioctl(fd, CDRIOCSENDCUE, &sheet) < 0) atapi-cd.c: case CDRIOCSENDCUE: error = acd_send_cue(cdp, (struct cdr_cuesheet *)addr); Our ioctl wrapper code causes a copyin/copyout according to the IOR/IOW encoding. It should be an int, and is being accessed as though it were an int within the kernel. If I had to guess, I'm wondering if you got this info from gdb.. I don't trust gdb for this stuff yet. I'd be more concerned if it was printf("pct %d\n", pct) that told you this. If you want to try something, set pct to 12345 right before the ioctl call in case you're looking at random contents or something. I don't know what is wrong though. But my initial thought is that it isn't this... -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 2 20:22:47 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43F1C16A4CE for ; Tue, 2 Nov 2004 20:22:47 +0000 (GMT) Received: from mail.komvista.lt (ns.komvista.lt [213.190.36.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFFC343D4C for ; Tue, 2 Nov 2004 20:22:45 +0000 (GMT) (envelope-from ssmailys@komvista.lt) Received: by mail.komvista.lt (Postfix, from userid 23) id 1F357BDCA; Tue, 2 Nov 2004 23:22:31 +0200 (EET) Received: from [192.168.127.253] (omega64.komvista.lt [192.168.127.253]) by mail.komvista.lt (Postfix) with ESMTP id 4185EBDC9; Tue, 2 Nov 2004 23:22:30 +0200 (EET) Message-ID: <4187EC93.2050709@komvista.lt> Date: Tue, 02 Nov 2004 22:22:43 +0200 From: Stasys Smailys User-Agent: Mozilla Thunderbird 0.8 (X11/20041102) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Wemm , "[FreeBSD-AMD64]" References: <4187EB23.1060407@komvista.lt> <200411021131.30701.peter@wemm.org> <4187F49A.5050006@komvista.lt> <200411021206.55318.peter@wemm.org> In-Reply-To: <200411021206.55318.peter@wemm.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ioctl() 64-bit issues X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Nov 2004 20:22:47 -0000 Last time I forgot to cc to the list. Peter Wemm wrote: > On Tuesday 02 November 2004 12:56 pm, Stasys Smailys wrote: > >>Peter Wemm wrote: >> >>>If you have a look at cdrio.h: >>>#define CDRIOCGETPROGRESS _IOR('c', 111, int) >>> >>>And the implementation is: >>> case CDRIOCGETPROGRESS: >>> error = acd_get_progress(cdp, (int *)addr); >>> >>>Compare to: >>>#define CDRIOCSENDCUE _IOW('c', 104, struct cdr_cuesheet) >>> >>>burncd.c: if (ioctl(fd, CDRIOCSENDCUE, &sheet) < 0) >>>atapi-cd.c: >>> case CDRIOCSENDCUE: >>> error = acd_send_cue(cdp, (struct cdr_cuesheet *)addr); >>> >>>Our ioctl wrapper code causes a copyin/copyout according to the >>>IOR/IOW encoding. It should be an int, and is being accessed as >>>though it were an int within the kernel. >> >>I think you are somewhere right. But anyway I can't >>CDRIOCGETPROGRESS. Can it be only my CDRW drive's issue? >> >> >>>If I had to guess, I'm wondering if you got this info from gdb.. I >>>don't trust gdb for this stuff yet. I'd be more concerned if it >>>was printf("pct %d\n", pct) that told you this. If you want to >>>try >> >>You're right. I was using printf() to get values. >> >> >>>something, set pct to 12345 right before the ioctl call in case >>>you're looking at random contents or something. >> >>Done. Getting "burncd: ioctl(CDRIOCGETPROGRESS): Inappropriate ioctl >>for device". Seems to be fine, but pct still has 0. > > > Well, this means that nothing is updating the 'pct' value because the > ioctl isn't executed at all. So you were seeing the previous random > contents. The big question is though... why doesn't the driver > recognize the ioctl? I don't know. I'll check tomorrow. It's late already. > Here's a silly thought.. you dont have a 32 bit burncd binary lying > around in your path by any chance, do you? No. It is impossible. # file `which burncd` /usr/sbin/burncd: ELF 64-bit LSB executable, AMD x86-64, version 1 (FreeBSD), dynamically linked (uses shared libs), stripped -- WBR Stasys Smailys From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 3 02:34:44 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D472B16A4CE; Wed, 3 Nov 2004 02:34:44 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED4EB43D45; Wed, 3 Nov 2004 02:34:43 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iA32YWtH008815; Wed, 3 Nov 2004 13:04:32 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org, John-Mark Gurney Date: Wed, 3 Nov 2004 13:04:30 +1030 User-Agent: KMail/1.7 References: <34cb7c8404110209563fc01498@mail.gmail.com> <20041102190851.GR22681@funkthat.com> In-Reply-To: <20041102190851.GR22681@funkthat.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart6075508.at3aiTZfpd"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411031304.31518.doconnor@gsoft.com.au> X-Spam-Score: -2.5 () IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_02_03,USER_AGENT X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: peadar@freebsd.org cc: freebsd-amd64@freebsd.org cc: FreeBSD current mailing list cc: Peter Edwards Subject: Re: if_sk patch to get more info from people with problems X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Nov 2004 02:34:45 -0000 --nextPart6075508.at3aiTZfpd Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 3 Nov 2004 05:38, John-Mark Gurney wrote: > Peter Edwards wrote this message on Tue, Nov 02, 2004 at 17:56 +0000: > > A (very) quick look at the source reveals that buffers are allocated > > via sk_rxeof()->sk_newbuf()->sk_jalloc() in the interrupt receive > > function, with the softc lock held in sk_rxeof(). > > > > They're freed by the mbuf system via a call to sk_jfree(), but that > > doesn't hold the SK_LOCK. Is this possibly the source of the > > corruption problems? What am I missing? > > This compiles, anyway :-) > > Well, try the attached patch (it also includes my changes from a previous > diff) that will see what happens... Make sure you have your kernel > compiled with WITNESS and INVARIANTS... If you hit one of these > asserts, make sure you post the back trace... I didn't see the previous patch, but I applied it from this one to 4.x and = it=20 seems to be behaving itself now. I'll keep testing it, but previously it would lock up pretty quickly :) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart6075508.at3aiTZfpd Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBiEO35ZPcIHs/zowRAqmIAJ9ukCzqgBKkmsJPztDSTdueJAdTjQCgjjH4 o92QPeHXyjlvAKPIjKEbhQU= =3lPf -----END PGP SIGNATURE----- --nextPart6075508.at3aiTZfpd-- From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 3 09:05:24 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36D6B16A4DF; Wed, 3 Nov 2004 09:05:24 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8AB343D3F; Wed, 3 Nov 2004 09:05:23 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id iA395NCA094428; Wed, 3 Nov 2004 04:05:23 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.1/8.13.1) with ESMTP id iA395MFo064166; Wed, 3 Nov 2004 04:05:22 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 1FF9B7306E; Wed, 3 Nov 2004 04:05:23 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041103090523.1FF9B7306E@freebsd-current.sentex.ca> Date: Wed, 3 Nov 2004 04:05:23 -0500 (EST) Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Nov 2004 09:05:24 -0000 TB --- 2004-11-03 07:29:29 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-03 07:29:29 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-11-03 07:29:29 - checking out the source tree TB --- 2004-11-03 07:29:29 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2004-11-03 07:29:29 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-03 07:35:33 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-03 07:35:33 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-11-03 07:35:33 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-11-03 08:53:39 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-11-03 08:53:39 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-11-03 08:53:39 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Wed Nov 3 08:53:40 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph/atm/sscop/../../../../contrib/ngatm/netnatm/saal/saal_sscop.c:4300: error: incompatible type for argument 1 of `ng_untimeout' /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph/atm/sscop/../../../../contrib/ngatm/netnatm/saal/saal_sscop.c:4301: error: incompatible type for argument 1 of `ng_untimeout' /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph/atm/sscop/../../../../contrib/ngatm/netnatm/saal/saal_sscop.c:4302: error: incompatible type for argument 1 of `ng_untimeout' /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph/atm/sscop/../../../../contrib/ngatm/netnatm/saal/saal_sscop.c:4302: warning: passing arg 3 of `ng_timeout' makes pointer from integer without a cast /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph/atm/sscop/../../../../contrib/ngatm/netnatm/saal/saal_sscop.c:4302: warning: passing arg 4 of `ng_timeout' makes integer from pointer without a cast /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph/atm/sscop/../../../../contrib/ngatm/netnatm/saal/saal_sscop.c:4302: warning: passing arg 5 of `ng_timeout' from incompatible pointer type /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph/atm/sscop/../../../../contrib/ngatm/netnatm/saal/saal_sscop.c:4302: error: too few arguments to function `ng_timeout' /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph/atm/sscop/../../../../contrib/ngatm/netnatm/saal/saal_sscop.c:4302: error: incompatible types in assignment *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph/atm/sscop. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph/atm. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys/modules. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-11-03 09:05:23 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-03 09:05:23 - ERROR: failed to build generic kernel TB --- 2004-11-03 09:05:23 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 3 10:21:10 2004 Return-Path: Delivered-To: freebsd-amd64@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4879D16A4CF for ; Wed, 3 Nov 2004 10:21:10 +0000 (GMT) Received: from mail.sbb.co.yu (mail.sbb.co.yu [82.117.194.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C66343D2F for ; Wed, 3 Nov 2004 10:21:09 +0000 (GMT) (envelope-from ggajic@mail.sbb.co.yu) Received: from mail.sbb.co.yu (mail.sbb.co.yu [82.117.194.7]) by mail.sbb.co.yu (8.12.10/8.12.10) with ESMTP id iA3AKmPO092175; Wed, 3 Nov 2004 11:20:48 +0100 (CET) Date: Wed, 3 Nov 2004 11:20:47 +0100 (CET) From: Goran Gajic To: Peter Edwards In-Reply-To: <34cb7c840411030155710d8a26@mail.gmail.com> Message-ID: References: <34cb7c840411030155710d8a26@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Sbb.co.yu-MailScanner-Information: Please contact the ISP for more information X-Sbb.co.yu-MailScanner: Found to be clean cc: freebsd-amd64@www.freebsd.org Subject: Re: if_sk patch to get more info from people with problems X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Nov 2004 10:21:10 -0000 I was talking about your small patch. FreeBSD 5.3RC2-amd64 was working fine for some 18 h even with SMP compiled kernel until I have tried file copying over NFS (using linux 2.6.9 as NFS client). Performance was poor and after incomplite copy of single file system rebooted with panic. It was also strange that copying of 700mb took some 30 min. on 100Mbit/s FD. After that I have applied small two lines patch, recompiled kernel and although I have coppied something like 100Gb of different mp3 and avi files over NFS - so far everything seems ok. I haven't compiled kernel with options WITNESS but it was my intention and will do so if I experience any further (if any) sk driver caused suspected crashes. Regards, gg. On Wed, 3 Nov 2004, Peter Edwards wrote: > Hi Goran: > Just to clarify: were you specifically talking about my (smaller) > patch? ie, the one that just added the two lock/unlock lines in > sk_jfree(), or John-Mark Gurney's one? > > Did you have witness/invariants compiled into your kernel? > From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 3 14:15:17 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2B4E16A4CF for ; Wed, 3 Nov 2004 14:15:17 +0000 (GMT) Received: from mail.komvista.lt (ns.komvista.lt [213.190.36.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFFCD43D31 for ; Wed, 3 Nov 2004 14:15:16 +0000 (GMT) (envelope-from ssmailys@komvista.lt) Received: by mail.komvista.lt (Postfix, from userid 23) id 13DB9BDCE; Wed, 3 Nov 2004 17:15:01 +0200 (EET) Received: from [192.168.127.253] (omega64.komvista.lt [192.168.127.253]) by mail.komvista.lt (Postfix) with ESMTP id DC0E3BDC9 for ; Wed, 3 Nov 2004 17:14:50 +0200 (EET) Message-ID: <4188E7E7.6010903@komvista.lt> Date: Wed, 03 Nov 2004 16:15:03 +0200 From: Stasys Smailys User-Agent: Mozilla Thunderbird 0.8 (X11/20041102) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "[FreeBSD-AMD64]" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: ioctl() 64-bit issues X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Nov 2004 14:15:17 -0000 Still not working. System is [deepred@omega64]:[~] > uname -a FreeBSD omega64.komvista.lt 5.3-STABLE FreeBSD 5.3-STABLE #0: Tue Nov 2 10:04:01 EET 2004 root@omega64.komvista.lt:/usr/obj/usr/src/sys/GENERAL amd64 ata_queue_request() returns zeros in request->u.atapi.sense_data.sk* after calling acd_get_progress() in dev/ata/atapi-cd.c. If request->u.atapi.sense_data.sksv is 0, then *finished is 0. That's why pct always gets zero, even if it has a value. Other functions don't care about second value when calling acd_get_progress() so they are not sensitive. Could it be that acd_get_progress() is deprecated and should not return anything excluding 0 or ENOMEM? -- WBR Stasys Smailys From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 3 18:59:23 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D548B16A4CE for ; Wed, 3 Nov 2004 18:59:23 +0000 (GMT) Received: from mclmx.mail.saic.com (mclmx.mail.saic.com [149.8.64.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F5F643D54 for ; Wed, 3 Nov 2004 18:59:23 +0000 (GMT) (envelope-from vanderbiltr@fdleweb.orl.saic.com) Received: from mcl-its-ieg01.mail.saic.com by mclmx.mail.saic.com; Wed, 3 Nov 2004 13:59:07 -0500 Received: from mclmx.mail.saic.com ([149.8.64.10]) M2004110313590708261 ; Wed, 03 Nov 2004 13:59:07 -0500 Received: from edison.orl.saic.com by mclmx.mail.saic.com with ESMTP; Wed, 3 Nov 2004 13:59:07 -0500 Received: from orl1021 (214.236.DHCP.orl.saic.com [10.26.214.236]) by edison.orl.saic.com (8.12.8/8.12.8) with ESMTP id iA3Ix6Om000342; Wed, 3 Nov 2004 13:59:06 -0500 From: "Richard Vanderbilt" To: Date: Wed, 3 Nov 2004 14:04:11 -0500 Message-Id: <000b01c4c1d7$e7d28740$ecd61a0a@orl.saic.com> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Importance: Normal Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: Home Subject: Boot/Installation problem on emachines M6805 Laptop X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Nov 2004 18:59:24 -0000 I have tried to install 5.2.1 / 5.3 Beta 7, RC1 versions onto my Laptop system from a CD of the amd64 distribution (boot only CD iso image from = ftp site). The boot loader program starts up with the options to boot, but = when you select the default (1) it stops without any error messages = displayed. The laptop is an Emachines M6805 with mobile amd64 processor, I am not = sure which chipset it contains. =20 Is there anything that I can do, or that I may be doing wrong, to get = the amd64 distribution to boot on my laptop. =20 Rich Vanderbilt From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 3 20:20:29 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CA7A16A4D0 for ; Wed, 3 Nov 2004 20:20:29 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 374F943D5C for ; Wed, 3 Nov 2004 20:20:29 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id iA3KKTII046283 for ; Wed, 3 Nov 2004 20:20:29 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id iA3KKTCj046282; Wed, 3 Nov 2004 20:20:29 GMT (envelope-from gnats) Date: Wed, 3 Nov 2004 20:20:29 GMT Message-Id: <200411032020.iA3KKTCj046282@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Jeff Connelly Subject: Re: amd64/67745: boot fails on compaq presario r3000z X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jeff Connelly List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Nov 2004 20:20:29 -0000 The following reply was made to PR amd64/67745; it has been noted by GNATS. From: Jeff Connelly To: freebsd-gnats-submit@freebsd.org Cc: Subject: Re: amd64/67745: boot fails on compaq presario r3000z Date: Wed, 3 Nov 2004 12:19:35 -0800 (PST) RC2 was released yesterday, and this patch still hasn't been applied. Can someone please apply it, or at least increase the priority so it gets noticed? Thanks... -Jeff __________________________________ Do you Yahoo!? Check out the new Yahoo! Front Page. www.yahoo.com From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 3 20:28:12 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 654B816A4CE for ; Wed, 3 Nov 2004 20:28:12 +0000 (GMT) Received: from chaos.fxp.org (chaos.fxp.org [209.251.159.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FC9A43D31 for ; Wed, 3 Nov 2004 20:28:12 +0000 (GMT) (envelope-from jedgar@fxp.org) Received: by chaos.fxp.org (Postfix, from userid 1000) id 0C61B2F3; Wed, 3 Nov 2004 15:28:11 -0500 (EST) Date: Wed, 3 Nov 2004 15:28:10 -0500 From: Chris Faulhaber To: Richard Vanderbilt Message-ID: <20041103202810.GB48022@chaos.fxp.org> References: <000b01c4c1d7$e7d28740$ecd61a0a@orl.saic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000b01c4c1d7$e7d28740$ecd61a0a@orl.saic.com> X-Mailer: socket() cc: freebsd-amd64@freebsd.org Subject: Re: Boot/Installation problem on emachines M6805 Laptop X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Nov 2004 20:28:12 -0000 On Wed, Nov 03, 2004 at 02:04:11PM -0500, Richard Vanderbilt wrote: > I have tried to install 5.2.1 / 5.3 Beta 7, RC1 versions onto my Laptop > system from a CD of the amd64 distribution (boot only CD iso image from ftp > site). The boot loader program starts up with the options to boot, but when > you select the default (1) it stops without any error messages displayed. > The laptop is an Emachines M6805 with mobile amd64 processor, I am not sure > which chipset it contains. > > Is there anything that I can do, or that I may be doing wrong, to get the > amd64 distribution to boot on my laptop. > My M6805 works quite well in 64-bit mode after updating the bios: http://www.rmecc.com/~v2/em/index.html -- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 3 22:19:43 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0693B16A4CE; Wed, 3 Nov 2004 22:19:43 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E8F243D3F; Wed, 3 Nov 2004 22:19:42 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id AC50E1FFACC; Wed, 3 Nov 2004 23:19:41 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id CF7871FF91D; Wed, 3 Nov 2004 23:19:39 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 88B98153C4; Wed, 3 Nov 2004 22:19:26 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 7E19415389; Wed, 3 Nov 2004 22:19:27 +0000 (UTC) Date: Wed, 3 Nov 2004 22:19:27 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: FreeBSD amd64 mailing list Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: FreeBSD current mailing list Subject: if_sk summary X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Bjoern A. Zeeb" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Nov 2004 22:19:43 -0000 Hi, I noted that I started to lose track with all the private replies, up to one day delayed mailing list replies and all. Thanks everyone for the feedback so far. I tried to summarize some things on http://sources.zabbadoz.net/freebsd/if_sk.html If you have any additions, corections etc. you will find an email address at the end of that page. What is especially missing is information on "known" systems and behavior with one of the patches applied. Please give the numer of the patch from the list on the page when telling me if possible. Please reply offlist; Reply-To: set. Thanks in advance. -- Greetings Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 3 22:36:46 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C5E916A4CE for ; Wed, 3 Nov 2004 22:36:46 +0000 (GMT) Received: from mail.trippynames.com (mail.trippynames.com [38.113.223.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71F6843D41 for ; Wed, 3 Nov 2004 22:36:46 +0000 (GMT) (envelope-from sean@chittenden.org) Received: from localhost (localhost [127.0.0.1]) by mail.trippynames.com (Postfix) with ESMTP id 49FCBA9439 for ; Wed, 3 Nov 2004 14:36:45 -0800 (PST) Received: from mail.trippynames.com ([127.0.0.1]) by localhost (rand.nxad.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 94036-03 for ; Wed, 3 Nov 2004 14:36:43 -0800 (PST) Received: from [192.168.123.123] (unknown [38.113.223.82]) by mail.trippynames.com (Postfix) with ESMTP id 3BA64A8C50 for ; Wed, 3 Nov 2004 14:36:43 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: References: <34cb7c840411030155710d8a26@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Sean Chittenden Date: Wed, 3 Nov 2004 14:36:40 -0800 To: freebsd-amd64@freebsd.org X-Mailer: Apple Mail (2.619) Subject: Status of the sk driver/NIC (was: Re: if_sk patch to get more info from people with problems) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Nov 2004 22:36:46 -0000 > I was talking about your small patch. FreeBSD 5.3RC2-amd64 was working > fine for some 18 h even with SMP compiled kernel until I have tried > file copying over NFS (using linux 2.6.9 as NFS client). Performance > was poor and after incomplite copy of single file system rebooted with > panic. It was also strange that copying of 700mb took some 30 min. > on 100Mbit/s FD. After that I have applied small two lines patch, > recompiled kernel and although I have coppied something like 100Gb of > different mp3 and avi files over NFS - so far everything seems ok. I > haven't compiled kernel with options WITNESS but it was my intention > and will do so if I experience any further (if any) sk driver caused > suspected crashes. Can someone authoritatively give me a quick answer regarding this? *) Is the sk driver not working/not working properly? *) Is the sk driver making up for deficiencies in the hardware? *) Will the sk driver be able to make up for the deficiencies in the hardware such that sk will perform well enough for most uses (under no pretenses that it will perform as well as an em nic/driver)? Sorry, I've been following this for a while. I have a few machines with an sk on the famous K8V SE Deluxe, but am exclusively using em0 instead of sk0. At some point I'd like to turn up the sk0 NIC and use OSPF to multipath traffic... but that's all predicated on the sk0 not sucking too much (sk can be slow, just can't cause the machine to crash). -sc -- Sean Chittenden From owner-freebsd-amd64@FreeBSD.ORG Wed Nov 3 22:40:34 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B602116A4D3 for ; Wed, 3 Nov 2004 22:40:34 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F75643D1F for ; Wed, 3 Nov 2004 22:40:34 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id iA3MeYUe062436 for ; Wed, 3 Nov 2004 22:40:34 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id iA3MeYQ1062435; Wed, 3 Nov 2004 22:40:34 GMT (envelope-from gnats) Date: Wed, 3 Nov 2004 22:40:34 GMT Message-Id: <200411032240.iA3MeYQ1062435@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: John Baldwin Subject: Re: amd64/67745: boot fails on compaq presario r3000z X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John Baldwin List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Nov 2004 22:40:34 -0000 The following reply was made to PR amd64/67745; it has been noted by GNATS. From: John Baldwin To: freebsd-gnats-submit@FreeBSD.org, newntrbr@ucla.edu Cc: Subject: Re: amd64/67745: boot fails on compaq presario r3000z Date: Wed, 3 Nov 2004 17:39:28 -0500 Ok, can someone please try the attached patch and see if setting 'hint.atkbd.0.flags=8' fixes the problem with the patch applied? Thanks. Index: atkbd.c =================================================================== RCS file: /usr/cvs/src/sys/dev/kbd/atkbd.c,v retrieving revision 1.43 diff -u -r1.43 atkbd.c --- atkbd.c 10 Jun 2004 20:30:56 -0000 1.43 +++ atkbd.c 3 Nov 2004 22:37:55 -0000 @@ -1117,7 +1117,8 @@ * to set the command byte to particular values. */ test_controller(kbdc); - test_kbd_port(kbdc); + if (!(flags & KB_CONF_NO_PROBE_TEST)) + test_kbd_port(kbdc); err = get_kbd_echo(kbdc); Index: atkbdreg.h =================================================================== RCS file: /usr/cvs/src/sys/dev/kbd/atkbdreg.h,v retrieving revision 1.6 diff -u -r1.6 atkbdreg.h --- atkbdreg.h 19 Mar 2000 03:25:12 -0000 1.6 +++ atkbdreg.h 3 Nov 2004 22:37:22 -0000 @@ -35,6 +35,7 @@ #define KB_CONF_FAIL_IF_NO_KBD (1 << 0) /* don't install if no kbd is found */ #define KB_CONF_NO_RESET (1 << 1) /* don't reset the keyboard */ #define KB_CONF_ALT_SCANCODESET (1 << 2) /* assume the XT type keyboard */ +#define KB_CONF_NO_PROBE_TEST (1 << 3) /* don't test keyboard during probe */ #ifdef _KERNEL -- John Baldwin <>< http://www.baldwin.cx/~john/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 4 01:50:40 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C5D716A4CE for ; Thu, 4 Nov 2004 01:50:38 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E42E43D8E for ; Thu, 4 Nov 2004 01:50:36 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id iA41oVH9085775 for ; Thu, 4 Nov 2004 01:50:31 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id iA41oVi9085774; Thu, 4 Nov 2004 01:50:31 GMT (envelope-from gnats) Date: Thu, 4 Nov 2004 01:50:31 GMT Message-Id: <200411040150.iA41oVi9085774@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Nicolas Blais Subject: Re: amd64/67745: boot fails on compaq presario r3000z X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Nicolas Blais List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Nov 2004 01:50:40 -0000 The following reply was made to PR amd64/67745; it has been noted by GNATS. From: Nicolas Blais To: freebsd-gnats-submit@freebsd.org, newntrbr@ucla.edu Cc: Subject: Re: amd64/67745: boot fails on compaq presario r3000z Date: Wed, 03 Nov 2004 20:42:01 -0500 If I had a working ISO, I could test it right now. Nicolas. From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 4 02:13:41 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 788C116A4CF for ; Thu, 4 Nov 2004 02:13:41 +0000 (GMT) Received: from mail.jrv.org (rrcs-24-73-246-106.sw.biz.rr.com [24.73.246.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A4B043D2F for ; Thu, 4 Nov 2004 02:13:41 +0000 (GMT) (envelope-from james@jrv.org) Received: from [192.168.3.156] (zippy.jrv.org [192.168.3.156]) (authenticated bits=0) by mail.jrv.org (8.12.11/8.12.10) with ESMTP id iA42Degj098509 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 3 Nov 2004 20:13:40 -0600 (CST) (envelope-from james@jrv.org) Message-ID: <41899054.9070406@jrv.org> Date: Wed, 03 Nov 2004 20:13:40 -0600 From: "James R. Van Artsalen" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@FreeBSD.org References: <41856838.6010309@jrv.org> <20041101000912.GE56606@dragon.nuxi.com> In-Reply-To: <20041101000912.GE56606@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: amd64 5.3rc1 panic during install on 8GB RAM Tyan S2885 w/ twe disk X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Nov 2004 02:13:41 -0000 David O'Brien wrote: >On Sun, Oct 31, 2004 at 04:33:28PM -0600, James R. Van Artsalen wrote: > > >>My Tyan S2885 K8W repeatedly panics during the file copy with CD install >>of 5.3rc1. >> >> >.. > > >>This hardware configuration worked well under 5.2.1 for a couple of >>months. I've reinstalled 5.2.1 and it still works fine there. >> >> > >Can you try the 5.3 Beta's to see when this broke for you? > > > Can anyone suggest where I might find the older betas to look for this? From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 4 02:31:13 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3355016A4CE; Thu, 4 Nov 2004 02:31:13 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C744043D66; Thu, 4 Nov 2004 02:31:12 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iA42VCim083520; Wed, 3 Nov 2004 21:31:12 -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.12.11/8.12.11) with ESMTP id iA42VC1E018146; Wed, 3 Nov 2004 21:31:12 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id F179C7306E; Wed, 3 Nov 2004 21:31:11 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041104023111.F179C7306E@freebsd-current.sentex.ca> Date: Wed, 3 Nov 2004 21:31:11 -0500 (EST) Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Nov 2004 02:31:13 -0000 TB --- 2004-11-04 01:07:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-04 01:07:00 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-11-04 01:07:00 - checking out the source tree TB --- 2004-11-04 01:07:00 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2004-11-04 01:07:00 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-04 01:13:04 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-04 01:13:04 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-11-04 01:13:04 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-11-04 02:19:45 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-11-04 02:19:45 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-11-04 02:19:45 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Thu Nov 4 02:19:45 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph/atm/sscop/../../../../contrib/ngatm/netnatm/saal/saal_sscop.c:4300: error: incompatible type for argument 1 of `ng_untimeout' /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph/atm/sscop/../../../../contrib/ngatm/netnatm/saal/saal_sscop.c:4301: error: incompatible type for argument 1 of `ng_untimeout' /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph/atm/sscop/../../../../contrib/ngatm/netnatm/saal/saal_sscop.c:4302: error: incompatible type for argument 1 of `ng_untimeout' /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph/atm/sscop/../../../../contrib/ngatm/netnatm/saal/saal_sscop.c:4302: warning: passing arg 3 of `ng_timeout' makes pointer from integer without a cast /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph/atm/sscop/../../../../contrib/ngatm/netnatm/saal/saal_sscop.c:4302: warning: passing arg 4 of `ng_timeout' makes integer from pointer without a cast /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph/atm/sscop/../../../../contrib/ngatm/netnatm/saal/saal_sscop.c:4302: warning: passing arg 5 of `ng_timeout' from incompatible pointer type /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph/atm/sscop/../../../../contrib/ngatm/netnatm/saal/saal_sscop.c:4302: error: too few arguments to function `ng_timeout' /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph/atm/sscop/../../../../contrib/ngatm/netnatm/saal/saal_sscop.c:4302: error: incompatible types in assignment *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph/atm/sscop. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph/atm. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys/modules/netgraph. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/sys/modules. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-11-04 02:31:11 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-04 02:31:11 - ERROR: failed to build generic kernel TB --- 2004-11-04 02:31:11 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 4 16:09:57 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3961516A4CF for ; Thu, 4 Nov 2004 16:09:57 +0000 (GMT) Received: from mail.komvista.lt (ns.komvista.lt [213.190.36.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0318F43D5C for ; Thu, 4 Nov 2004 16:09:56 +0000 (GMT) (envelope-from ssmailys@komvista.lt) Received: by mail.komvista.lt (Postfix, from userid 23) id D4184BDCA; Thu, 4 Nov 2004 19:09:39 +0200 (EET) Received: from [192.168.127.253] (omega64.komvista.lt [192.168.127.253]) by mail.komvista.lt (Postfix) with ESMTP id D986CBDC9; Thu, 4 Nov 2004 19:09:37 +0200 (EET) Message-ID: <418A544F.7090903@komvista.lt> Date: Thu, 04 Nov 2004 18:09:51 +0200 From: Stasys Smailys User-Agent: Mozilla Thunderbird 0.8 (X11/20041102) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "[FreeBSD-AMD64]" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ioctl() 64-bit issues X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Nov 2004 16:09:57 -0000 Hi all! > Still not working. System is > > [deepred at omega64]:[~] > uname -a > FreeBSD omega64.komvista.lt 5.3-STABLE FreeBSD 5.3-STABLE #0: Tue Nov 2 > 10:04:01 EET 2004 > root at omega64.komvista.lt:/usr/obj/usr/src/sys/GENERAL amd64 > > ata_queue_request() returns zeros in request->u.atapi.sense_data.sk* > after calling acd_get_progress() in dev/ata/atapi-cd.c. If > request->u.atapi.sense_data.sksv is 0, then *finished is 0. That's why > pct always gets zero, even if it has a value. Other functions don't care > about second value when calling acd_get_progress() so they are not > sensitive. Could it be that acd_get_progress() is deprecated and should > not return anything excluding 0 or ENOMEM? First of all I'm sorry for the false alarm. It appeared that the problem was in CDRW drive. After changing NEC NR-7700A to LiteOn SOHR-5238S everything works just fine. It seems to be a hardware bug because I can't change transfer mode to anything more than WDMA2 (by default it starts at PIO4). I would never thought that it was the hardware issue. Thanks anyway. -- WBR Stasys Smailys From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 4 20:55:28 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8759216A607 for ; Thu, 4 Nov 2004 20:55:28 +0000 (GMT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 606CA43D46 for ; Thu, 4 Nov 2004 20:55:28 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 14300 invoked from network); 4 Nov 2004 20:55:28 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 4 Nov 2004 20:55:26 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iA4KsIlL088385; Thu, 4 Nov 2004 15:55:13 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-amd64@FreeBSD.org, Nicolas Blais Date: Thu, 4 Nov 2004 15:52:49 -0500 User-Agent: KMail/1.6.2 References: <200411040150.iA41oVi9085774@freefall.freebsd.org> In-Reply-To: <200411040150.iA41oVi9085774@freefall.freebsd.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411041552.49099.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx Subject: Re: amd64/67745: boot fails on compaq presario r3000z X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Nov 2004 20:55:28 -0000 On Wednesday 03 November 2004 08:50 pm, Nicolas Blais wrote: > The following reply was made to PR amd64/67745; it has been noted by GNATS. > > From: Nicolas Blais > To: freebsd-gnats-submit@freebsd.org, newntrbr@ucla.edu > Cc: > Subject: Re: amd64/67745: boot fails on compaq presario r3000z > Date: Wed, 03 Nov 2004 20:42:01 -0500 > > If I had a working ISO, I could test it right now. Working ISO is a bit harder to build on the fly. It could be done though by compiling a GENERIC kernel, then fetching an ISO, using mdconfig to mount it, then build a new ISO but setup the new kernel to replace the one on the ISO. I don't have a bunch of spare time to do that atm, can someone test it w/o requiring an ISO? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-amd64@FreeBSD.ORG Thu Nov 4 21:50:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 776EA16A4CE for ; Thu, 4 Nov 2004 21:50:56 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1855443D1D for ; Thu, 4 Nov 2004 21:50:56 +0000 (GMT) (envelope-from calmasy@gmail.com) Received: by wproxy.gmail.com with SMTP id 64so239914wri for ; Thu, 04 Nov 2004 13:50:55 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=RshAAtwnHuOg/pUlrc95jgnLlX/z/+26y/gf25Pml2xFrifbW8sqZzuGw+R8xWtv3GIZcl74xAFM+EVhZZXpJCxtahJpZXXTOJadA5PMKSht2DCCNMJGZ8LvABeJvHRhATRlr2et9j3BL0/oXpK0j5AqD2eAykR7bpElJj+nt5E= Received: by 10.38.209.1 with SMTP id h1mr56841rng; Thu, 04 Nov 2004 13:50:55 -0800 (PST) Received: by 10.38.83.36 with HTTP; Thu, 4 Nov 2004 13:50:55 -0800 (PST) Message-ID: Date: Thu, 4 Nov 2004 14:50:55 -0700 From: =?ISO-8859-1?Q?Count_L=E1szl=F3_de_Alm=E1sy?= To: freebsd-amd64@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: FreeBSD 5.3-RC2 doesn't work X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: =?ISO-8859-1?Q?Count_L=E1szl=F3_de_Alm=E1sy?= List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Nov 2004 21:50:56 -0000 I tried to boot off the CD I made from 5.3-RC2-amd64-miniinst.iso on an IntelEM64T system, and it fails with simply: panic: No BIOS smap info from loader! cpuid = 0 Uptime: 1s Any ideas? From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 5 00:23:06 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C91416A4CE; Fri, 5 Nov 2004 00:23:06 +0000 (GMT) Received: from out010.verizon.net (out010pub.verizon.net [206.46.170.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7ED643D45; Fri, 5 Nov 2004 00:23:05 +0000 (GMT) (envelope-from andrew.lankford@verizon.net) Received: from [192.168.0.2] ([138.88.232.152]) by out010.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041105002305.FZUZ25072.out010.verizon.net@[192.168.0.2]>; Thu, 4 Nov 2004 18:23:05 -0600 Message-ID: <418AC7EB.6080503@verizon.net> Date: Thu, 04 Nov 2004 19:23:07 -0500 From: Andrew Lankford User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin , amd64@freebsd.org, Nicolas Blais Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out010.verizon.net from [138.88.232.152] at Thu, 4 Nov 2004 18:23:04 -0600 Subject: Re: amd64/67745: boot fails on compaq presario r3000z X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Nov 2004 00:23:06 -0000 >Working ISO is a bit harder to build on the fly. It could be done >though by compiling a GENERIC kernel, then fetching an ISO, using >mdconfig to mount it, then build a new ISO but setup the new kernel to >replace the one on the ISO. I don't have a bunch of spare time to do >that atm, can someone test it w/o requiring an ISO? I was wondering a while back if it was possible to net boot off of some sort of fixit floppy image (possibly after cross-building it from -i386). Andrew Lankford From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 5 07:54:01 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81A2D16A4CE for ; Fri, 5 Nov 2004 07:54:01 +0000 (GMT) Received: from manor.msen.com (manor.msen.com [148.59.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E85C43D58 for ; Fri, 5 Nov 2004 07:54:01 +0000 (GMT) (envelope-from wayne@manor.msen.com) Received: from manor.msen.com (localhost [127.0.0.1]) by manor.msen.com (8.12.9p2/8.12.9) with ESMTP id iA57rwO7065693 for ; Fri, 5 Nov 2004 02:54:00 -0500 (EST) (envelope-from wayne@manor.msen.com) Received: (from wayne@localhost) by manor.msen.com (8.12.9p2/8.12.9/Submit) id iA57rwaB065692 for freebsd-amd64@freebsd.org; Fri, 5 Nov 2004 02:53:58 -0500 (EST) (envelope-from wayne) Date: Fri, 5 Nov 2004 02:53:57 -0500 From: "Michael R. Wayne" To: freebsd-amd64@freebsd.org Message-ID: <20041105075357.GQ30984@manor.msen.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Problems with 4GB and 5.3 on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Nov 2004 07:54:01 -0000 Loaded 5.3RC2 from the iso onto my new 4GB dual Opteron server today. After getting cvsuop installed, I got 5.3-RELEASE and did a buildworld. It never completed: repeating it several times resulted in random crashes in various places throughout the build. A bit of googling suggested adding a line to /boot/loader.conf hw.physmem=2G This permitted the buildworld to complete so I built a new kernel using the following config file: include GENERIC options SMP options VM_KMEM_SIZE_MAX=(400*1024*1024) Leaving the 2G line in loader.conf, I managed to complete the entire build/install process normally. SMP seems to work properly as well. I removed the 2G limit from loader.conf and tried several more buildworlds and the random crashes returned. A bit of googling suggested adding the following to /etc/make.conf: CFLAGS= -O -pipe -g -DKVA_PAGES=512 COPTFLAGS= -O -pipe -DKVA_PAGES=512 This had no effect, the random crashes continue during buildworlds. I tried raising the limit to 3G and the crashes returned. Any suggestions as to how to proceed would be greatly appreciated. /\/\ \/\/ From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 5 08:22:00 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB7E416A4CE for ; Fri, 5 Nov 2004 08:22:00 +0000 (GMT) Received: from web14122.mail.yahoo.com (web14122.mail.yahoo.com [66.163.171.113]) by mx1.FreeBSD.org (Postfix) with SMTP id CF18A43D39 for ; Fri, 5 Nov 2004 08:22:00 +0000 (GMT) (envelope-from cguttesen@yahoo.dk) Received: (qmail 22637 invoked by uid 60001); 5 Nov 2004 08:22:00 -0000 Message-ID: <20041105082200.22635.qmail@web14122.mail.yahoo.com> Received: from [194.248.174.58] by web14122.mail.yahoo.com via HTTP; Fri, 05 Nov 2004 09:22:00 CET Date: Fri, 5 Nov 2004 09:22:00 +0100 (CET) From: Claus Guttesen To: "Michael R. Wayne" , freebsd-amd64@freebsd.org In-Reply-To: <20041105075357.GQ30984@manor.msen.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: Problems with 4GB and 5.3 on amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Nov 2004 08:22:01 -0000 > today. After getting cvsuop installed, I got > 5.3-RELEASE and did > a buildworld. > It never completed: repeating it several times > resulted in random > crashes in various places throughout the build. What type of controller do you have? Claus From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 5 10:56:56 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E5ED16A4CE for ; Fri, 5 Nov 2004 10:56:56 +0000 (GMT) Received: from mail.trippynames.com (mail.trippynames.com [38.113.223.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AD2D43D41 for ; Fri, 5 Nov 2004 10:56:56 +0000 (GMT) (envelope-from sean@chittenden.org) Received: from localhost (localhost [127.0.0.1]) by mail.trippynames.com (Postfix) with ESMTP id 33610A10F5 for ; Fri, 5 Nov 2004 02:56:55 -0800 (PST) Received: from mail.trippynames.com ([127.0.0.1]) by localhost (rand.nxad.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 49545-01 for ; Fri, 5 Nov 2004 02:56:53 -0800 (PST) Received: from [192.168.1.3] (dsl081-069-073.sfo1.dsl.speakeasy.net [64.81.69.73]) by mail.trippynames.com (Postfix) with ESMTP id 64806A10FB for ; Fri, 5 Nov 2004 02:56:53 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: <63590666-2F19-11D9-A891-000A95C705DC@chittenden.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-amd64@freebsd.org From: Sean Chittenden Date: Fri, 5 Nov 2004 02:56:47 -0800 X-Mailer: Apple Mail (2.619) Subject: [Q & A] Bootup too quick, switch port isn't up... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Nov 2004 10:56:56 -0000 [ This email is mainly line noise at this point, but, it's probably better ] [ to have it in the archives since I didn't find anything when I was looking ] [ earlier. While about to push send, shmaz on irc came up the the answer. ] [ Many thanks. -sc ] Alright, I joked about this last time, but I'm actually having problems related to amd64 booting too quick (slower damn it! slower!) All joking aside, someone at the data center today suggested I install Linux as a solution to FreeBSD booting too fast on amd64... As many are aware (and hopefully more don't have to deal with this if they don't have Cisco hardware), Cisco takes a year and a day to bring up a port. Back in the day, this didn't used to be a problem, but with faster hardware and startup times, it's become one. I have bootp machines, and even full blown servers that are getting to multi-user mode faster than a Cisco switch is able to bring the line up. So, when the OS gets to multi-user mode, all kinds of things fail and in strange/obtuse ways (hostname, reverse DNS, NFS, etc). I'm sure I'm not the only one who's had/having this problem. Since this doesn't seem to effect folks on older hardware that isn't as snappy, I'll ask here even though this question is more suited to net@ than amd64@. Can ifconfig be taught to block (with an extra option) so that it doesn't return until the interface in question has been brought up to its desired speed/duplex? As things stand, I can fire off an `ifconfig em0 10.0.0.1 netmask 0xFFFFFF00 media 100baseTX mediaopt full-duplex` and have it return in a second. It takes the switch another 20-30 seconds to actually come up, at which point I get a nice message (that's about to be hidden behind a verbose flag) that tells me, "em0: Link is up 100 Mbps Full Duplex"... after I've been sitting at the login prompt and am staring at various failure messages. Doing this in serial isn't ideal on servers that have many interfaces, but, it seems cleaner to me to have each invocation of ifconfig(8) block instead of having some new command (ex: `ifmediachk em0 em1 em2 em3`) that blocks until the interfaces specified come up to their desired level. *shrug* The best workaround that I've been able to come up with is to reintroduce the SCSI delay and set it to 30 sec... but I don't think that'll save me since the line status is reset when I issue an ifconfig statement and the SCSI delay is issued well before the interfaces are brought up. As I've said, I'm sure I'm not the only one who's run into this. Any suggestions from those that have dealt with this already? -sc ### Answer ### For Cisco switches, use the 'fastport' and '' options, though the fastport option seems to make the biggest difference. Two links for those interested: http://www.cisco.com/en/US/products/hw/switches/ps663/ products_configuration_guide_chapter09186a00800d83f4.html#1019873 http://www.cisco.com/en/US/products/hw/switches/ps663/ products_configuration_guide_chapter09186a00800d83f4.html#1019960 Again, sorry for the noise. Hope someone reading this in the archives finds it useful. I wonder if this'll become an FAQ or not. -sc -- Sean Chittenden From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 5 11:09:26 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F14716A4CE for ; Fri, 5 Nov 2004 11:09:26 +0000 (GMT) Received: from freebee.digiware.nl (dsl439.iae.nl [212.61.63.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9A8D43D1F for ; Fri, 5 Nov 2004 11:09:25 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.71] (dual.digiware.nl [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with ESMTP id iA5B8p5p048849; Fri, 5 Nov 2004 12:08:51 +0100 (CET) (envelope-from wjw@withagen.nl) Message-ID: <418B5F45.4090508@withagen.nl> Date: Fri, 05 Nov 2004 12:08:53 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sean Chittenden References: <63590666-2F19-11D9-A891-000A95C705DC@chittenden.org> In-Reply-To: <63590666-2F19-11D9-A891-000A95C705DC@chittenden.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-amd64@freebsd.org Subject: Re: [Q & A] Bootup too quick, switch port isn't up... X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Nov 2004 11:09:26 -0000 Sean Chittenden wrote: > [ This email is mainly line noise at this point, but, it's probably > better ] > [ to have it in the archives since I didn't find anything when I was > looking ] > [ earlier. While about to push send, shmaz on irc came up the the > answer. ] > [ Many thanks. -sc ] > > Alright, I joked about this last time, but I'm actually having problems > related to amd64 booting too quick (slower damn it! slower!) All > joking aside, someone at the data center today suggested I install > Linux as a solution to FreeBSD booting too fast on amd64... How about asking the people at the data centre to hard set the port to the mode that you prefer. Even cisco's can be hardwired in a config. Or tell them to buy proper switches. :) --WjW From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 5 15:43:00 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56D6D16A4CF; Fri, 5 Nov 2004 15:43:00 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A1AE43D2D; Fri, 5 Nov 2004 15:42:58 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id iA5FgwkR093440; Fri, 5 Nov 2004 10:42:58 -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.12.11/8.12.11) with ESMTP id iA5FgwZv024981; Fri, 5 Nov 2004 10:42:58 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id BB6997306E; Fri, 5 Nov 2004 10:42:57 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041105154257.BB6997306E@freebsd-current.sentex.ca> Date: Fri, 5 Nov 2004 10:42:57 -0500 (EST) Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Nov 2004 15:43:00 -0000 TB --- 2004-11-05 15:13:30 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-05 15:13:30 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-11-05 15:13:31 - checking out the source tree TB --- 2004-11-05 15:13:31 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2004-11-05 15:13:31 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-05 15:19:31 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-05 15:19:31 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-11-05 15:19:31 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] cc -O2 -pipe -DPACKAGE_NAME=\"libarchive\" -DPACKAGE_VERSION=\"1.01.015\" -I/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/lib/libarchive -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /tinderbox/CURRENT/amd64/amd64/src/lib/libarchive/archive_write_open_file.c cc -O2 -pipe -DPACKAGE_NAME=\"libarchive\" -DPACKAGE_VERSION=\"1.01.015\" -I/tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/lib/libarchive -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /tinderbox/CURRENT/amd64/amd64/src/lib/libarchive/archive_write_set_compression_bzip2.c /tinderbox/CURRENT/amd64/amd64/src/lib/libarchive/archive_write_set_compression_bzip2.c:163: error: conflicting types for 'archive_compressor_bzip2_write' /tinderbox/CURRENT/amd64/amd64/src/lib/libarchive/archive_write_set_compression_bzip2.c:61: error: previous declaration of 'archive_compressor_bzip2_write' was here /tinderbox/CURRENT/amd64/amd64/src/lib/libarchive/archive_write_set_compression_bzip2.c:163: error: conflicting types for 'archive_compressor_bzip2_write' /tinderbox/CURRENT/amd64/amd64/src/lib/libarchive/archive_write_set_compression_bzip2.c:61: error: previous declaration of 'archive_compressor_bzip2_write' was here /tinderbox/CURRENT/amd64/amd64/src/lib/libarchive/archive_write_set_compression_bzip2.c:61: warning: 'archive_compressor_bzip2_write' declared `static' but never defined /tinderbox/CURRENT/amd64/amd64/src/lib/libarchive/archive_write_set_compression_bzip2.c:163: warning: 'archive_compressor_bzip2_write' defined but not used *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/lib/libarchive. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src/lib. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-11-05 15:42:57 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-05 15:42:57 - ERROR: failed to build world TB --- 2004-11-05 15:42:57 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Fri Nov 5 18:46:03 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 098E916A4CE for ; Fri, 5 Nov 2004 18:46:03 +0000 (GMT) Received: from sb.santaba.com (sb.santaba.com [207.154.84.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id E359B43D2D for ; Fri, 5 Nov 2004 18:46:02 +0000 (GMT) (envelope-from jbehl@fastclick.com) Received: from [192.168.3.100] (unknown [205.180.85.193]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sb.santaba.com (Postfix) with ESMTP id B802628433 for ; Fri, 5 Nov 2004 10:46:02 -0800 (PST) Message-ID: <418BCAB8.7080801@fastclick.com> Date: Fri, 05 Nov 2004 10:47:20 -0800 From: Jeff Behl User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-amd64@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: apache2 performance on 5.3 SMP machine X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Nov 2004 18:46:03 -0000 howdy, i'm running the latest apache2, compiled from the ports collection (apache-2.0.52_2; prefork), on a dual 2gHz AMD64 box from ibm. the performance is very bad, with ~ %20 cpu at only ~115 req/s. for whatever reason, almost all of the %20 cpu time is spent in system: CPU states: 0.4% user, 0.0% nice, 17.3% system, 1.3% interrupt, 81.0% idle is there a known problem that could lead to this? i'm a bsd bigot, and after going mad with the IO lockup issues in the kernel that RedHat uses in their AES line (it's truely abysmal), I'd be overjoyed to move everything to BSD, but the redhat boxes on the same hardware aren't even breaking a sweat under the same load. what i'd guess to be the most relevant pieces of hardware that could lead to high system load, the NIC and hard disk controller, are as follows: bge0: mem 0xfe000000-0xfe00ffff,0xfe010000-0xfe01ffff irq 24 at device 1.0 on pci2 mpt0: port 0x3000-0x30ff mem 0xfe040000-0xfe04ffff,0xfe050000-0xfe05ffff irq 26 at device 2.0 on pci2 apache config is: ServerLimit 3000 StartServers 100 MinSpareServers 100 MaxSpareServers 500 MaxClients 3000 MaxRequestsPerChild 0 is this a 5.3 issue in general, or specific to the AMD line? any help or tips greatly appreciated. From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 6 07:36:32 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 380AC16A4CE; Sat, 6 Nov 2004 07:36:32 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5B1B43D2D; Sat, 6 Nov 2004 07:36:31 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id iA67aVaj040558; Sat, 6 Nov 2004 02:36:31 -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.12.11/8.12.11) with ESMTP id iA67aU3E051067; Sat, 6 Nov 2004 02:36:30 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 9E8497306E; Sat, 6 Nov 2004 02:36:30 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041106073630.9E8497306E@freebsd-current.sentex.ca> Date: Sat, 6 Nov 2004 02:36:30 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/574/Thu Nov 4 19:12:58 2004 clamav-milter version 0.80j on clamscanner1.sentex.ca X-Virus-Scanned: ClamAV 0.80/574/Thu Nov 4 19:12:58 2004 clamav-milter version 0.80j on clamscanner2.sentex.ca X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Nov 2004 07:36:32 -0000 TB --- 2004-11-06 05:40:56 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-06 05:40:56 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2004-11-06 05:40:56 - checking out the source tree TB --- 2004-11-06 05:40:56 - cd /home/tinderbox/CURRENT/amd64/amd64 TB --- 2004-11-06 05:40:56 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-06 05:58:44 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-06 05:58:44 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-11-06 05:58:44 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-11-06 07:28:48 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-11-06 07:28:48 - cd /home/tinderbox/CURRENT/amd64/amd64/src TB --- 2004-11-06 07:28:48 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sat Nov 6 07:28:48 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64 /src/sys/vm/vm_page.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64 /src/sys/vm/vm_pageq.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64 /src/sys/vm/vm_contig.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/tinderbox/CURRENT/amd64/amd64/src/sys -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/altq -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/pf -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/amd64/amd64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror /tinderbox/CURRENT/amd64/amd64 /src/sys/vm/vm_zeroidle.c /tinderbox/CURRENT/amd64/amd64/src/sys/vm/vm_zeroidle.c: In function `vm_pagezero': /tinderbox/CURRENT/amd64/amd64/src/sys/vm/vm_zeroidle.c:164: error: `pages' undeclared (first use in this function) /tinderbox/CURRENT/amd64/amd64/src/sys/vm/vm_zeroidle.c:164: error: (Each undeclared identifier is reported only once /tinderbox/CURRENT/amd64/amd64/src/sys/vm/vm_zeroidle.c:164: error: for each function it appears in.) *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/obj/amd64/tinderbox/CURRENT/amd64/amd64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. *** Error code 1 Stop in /tinderbox/CURRENT/amd64/amd64/src. TB --- 2004-11-06 07:36:30 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-06 07:36:30 - ERROR: failed to build generic kernel TB --- 2004-11-06 07:36:30 - tinderbox aborted From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 6 09:30:27 2004 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A510B16A4CE for ; Sat, 6 Nov 2004 09:30:27 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AE9A43D49 for ; Sat, 6 Nov 2004 09:30:27 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.11/8.12.11) with ESMTP id iA69URc8080697 for ; Sat, 6 Nov 2004 09:30:27 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id iA69URA5080688; Sat, 6 Nov 2004 09:30:27 GMT (envelope-from gnats) Resent-Date: Sat, 6 Nov 2004 09:30:27 GMT Resent-Message-Id: <200411060930.iA69URA5080688@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, Patrick Lehner Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 21C2716A4CE for ; Sat, 6 Nov 2004 09:24:32 +0000 (GMT) Received: from www.freebsd.org (www.freebsd.org [216.136.204.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1667E43D39 for ; Sat, 6 Nov 2004 09:24:32 +0000 (GMT) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.12.11/8.12.11) with ESMTP id iA69OVT1010864 for ; Sat, 6 Nov 2004 09:24:31 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.12.11/8.12.11/Submit) id iA69OVLB010863; Sat, 6 Nov 2004 09:24:31 GMT (envelope-from nobody) Message-Id: <200411060924.iA69OVLB010863@www.freebsd.org> Date: Sat, 6 Nov 2004 09:24:31 GMT From: Patrick Lehner To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: amd64/73603: kernel build amd64 fails when device ath and device ath_hal included X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Nov 2004 09:30:27 -0000 >Number: 73603 >Category: amd64 >Synopsis: kernel build amd64 fails when device ath and device ath_hal included >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Nov 06 09:30:26 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Patrick Lehner >Release: 5.3-RC2 >Organization: >Environment: Install from 5.3-RC2 CD (sorry i don't have the original output saved) But errror is reproduceable >Description: kernel build fails when device ath and ath_hal included in kernel config ath_hal.ko is not created when building new kernel. .................. ah_osdep.o(.text+0x157): In function `ath_hal_modevent': : undefined reference to `ath_hal_version' ah_osdep.o(.data+0x1b8): undefined reference to `ath_hal_version' if_ath.o(.text+0x1eb2): In function `ath_start': : undefined reference to `ath_hal_computetxtime' ........ Build fails after those error messages >How-To-Repeat: add: device ath device ath_hal to kernel config file in amd64 >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Sat Nov 6 18:18:12 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 533D816A4CE for ; Sat, 6 Nov 2004 18:18:12 +0000 (GMT) Received: from freenix.no (atreides.freenix.no [212.33.142.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43B7E43D1D for ; Sat, 6 Nov 2004 18:18:11 +0000 (GMT) (envelope-from shamz@atreides.freenix.no) Received: from atreides.freenix.no (localhost [127.0.0.1]) by freenix.no (8.12.11/8.12.11) with ESMTP id iA6II6YD036939; Sat, 6 Nov 2004 19:18:07 +0100 (CET) (envelope-from shamz@atreides.freenix.no) Received: (from shamz@localhost) by atreides.freenix.no (8.12.11/8.12.11/Submit) id iA6II0kn036938; Sat, 6 Nov 2004 19:18:00 +0100 (CET) (envelope-from shamz) Date: Sat, 6 Nov 2004 19:18:00 +0100 From: Shaun Jurrens To: freebsd-amd64@FreeBSD.org Message-ID: <20041106181800.GP90420@atreides.freenix.no> 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.10-RELEASE-p2 X-Philosophy: If you can read this, you're too close. X-Virus-Scanned: ClamAV 0.80/571/Wed Nov 3 01:15:45 2004 clamav-milter version 0.80j on atreides.freenix.no X-Virus-Status: Clean Subject: Re: apache2 performance on 5.3 SMP machine X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Nov 2004 18:18:12 -0000 >howdy, > >i'm running the latest apache2, compiled from the ports collection >(apache-2.0.52_2; prefork), on a dual 2gHz AMD64 box from ibm. the >performance is very bad, with ~ %20 cpu at only ~115 req/s. for >whatever reason, almost all of the %20 cpu time is spent in system: > >CPU states: 0.4% user, 0.0% nice, 17.3% system, 1.3% interrupt, 81.0% >idle > [...] Jeff, fwiw, you're going to have to provide a lot more information as to your kernel configuration, whether you built apache from ports or not, where you're serving your "pages" from (local disk or nfs), which FreeBSD version you're using (uname -a), and so on. A kernel config and a dmesg are at least a start. I don't think you're going to get a lot of help unless you give the people here something to work with... -- Yours truly, Shaun D. Jurrens shaun@shamz.net