From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 23 04:22:51 2007 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 39DEF16A419 for ; Sun, 23 Dec 2007 04:22:51 +0000 (UTC) (envelope-from tinierbean@gmail.com) Received: from hs-out-2122.google.com (hs-out-0708.google.com [64.233.178.244]) by mx1.freebsd.org (Postfix) with ESMTP id 0918F13C448 for ; Sun, 23 Dec 2007 04:22:50 +0000 (UTC) (envelope-from tinierbean@gmail.com) Received: by hs-out-2122.google.com with SMTP id j58so878610hsj.11 for ; Sat, 22 Dec 2007 20:22:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=5a6ylNlIxpu9EgM0QBFIJIPtMdtlem36ymc8kMIAa+M=; b=sPl1OdO4MXMrgSqi1z/7u9nNqcxA11aMFxQDGBYdvfzlUmh4IQQYQz41dpzPYKPM/bf9AybJDpkhxb0UlpO9RnrD10puMdWh5yCsmt9j6M/JeFcF8k0mAEQPSbal1jv9z6Nux13Z/qZsbsuhBrOc4X3nooscootTiyniMdLX+5Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=Z3PqpFnNobg726g+21xRNje8msjgP9RwF+pfWC8RGjFid4Wkh/AbFp9FIBfPbhZt5IrgNLIIfxRvTr/qvw7NUHdNRwApa6f1OkEpjEpF3tOH4doVafS3bROdToKuh401N6epubFTz2NHvVIYMhpB6l5Fj0pdtGgAR6NbLty6NBI= Received: by 10.151.15.3 with SMTP id s3mr928309ybi.29.1198382202333; Sat, 22 Dec 2007 19:56:42 -0800 (PST) Received: by 10.150.122.10 with HTTP; Sat, 22 Dec 2007 19:56:42 -0800 (PST) Message-ID: Date: Sun, 23 Dec 2007 11:56:42 +0800 From: "zhang feng" To: freebsd-amd64@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: how do i write assembly code in amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Dec 2007 04:22:51 -0000 hello,all i write asm32 code in linux.when i run the code in freebsd amd64, it cannt run. someone give me a help for coding asm64 in freebsd. ths. From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 23 04:29:47 2007 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CCA5816A417 for ; Sun, 23 Dec 2007 04:29:46 +0000 (UTC) (envelope-from nge@cs.hmc.edu) Received: from knuth.cs.hmc.edu (knuth.cs.hmc.edu [134.173.42.100]) by mx1.freebsd.org (Postfix) with ESMTP id 8702C13C457 for ; Sun, 23 Dec 2007 04:29:46 +0000 (UTC) (envelope-from nge@cs.hmc.edu) Received: by knuth.cs.hmc.edu (Postfix, from userid 26983) id 3A73785140; Sat, 22 Dec 2007 20:29:46 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by knuth.cs.hmc.edu (Postfix) with ESMTP id 3A09A42F7E0; Sat, 22 Dec 2007 20:29:46 -0800 (PST) Date: Sat, 22 Dec 2007 20:29:46 -0800 (PST) From: Nate Eldredge X-X-Sender: nate@knuth.cs.hmc.edu To: zhang feng In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-amd64@freebsd.org Subject: Re: how do i write assembly code in amd64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Dec 2007 04:29:47 -0000 On Sun, 23 Dec 2007, zhang feng wrote: > hello,all > i write asm32 code in linux.when i run the code in freebsd amd64, it cannt > run. > someone give me a help for coding asm64 in freebsd. amd64 has a whole different instruction set than 32-bit x86, though there are similarities. Documentation is available at http://www.amd.com/us-en/Processors/DevelopWithAMD/0,,30_2252_9044,00.html , under "AMD64 Architecture Programmers' Manuals". -- Nate Eldredge nge@cs.hmc.edu From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 23 04:52:40 2007 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8774416A417 for ; Sun, 23 Dec 2007 04:52:38 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.freebsd.org (Postfix) with ESMTP id 55B3513C459 for ; Sun, 23 Dec 2007 04:52:38 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with ESMTP id <0JTH003TBK7PCP00@osl1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Sun, 23 Dec 2007 05:52:37 +0100 (CET) Received: from kg-work.kg4.no ([80.202.173.59]) by osl1sminn1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with SMTP id <0JTH002COK7OHCO2@osl1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Sun, 23 Dec 2007 05:52:37 +0100 (CET) Date: Sun, 23 Dec 2007 05:52:36 +0100 From: Torfinn Ingolfsen To: freebsd-amd64@freebsd.org Message-id: <20071223055236.ebf95247.torfinn.ingolfsen@broadpark.no> In-reply-to: <20071221022122.a4b4c7c9.torfinn.ingolfsen@broadpark.no> References: <20071221022122.a4b4c7c9.torfinn.ingolfsen@broadpark.no> X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.3; i386-portbld-freebsd6.2) X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH Subject: Re: Recommended motherboard + cpu combination for AMD Socket AM2+ / Phenom? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Dec 2007 04:52:40 -0000 On Fri, 21 Dec 2007 02:21:22 +0100 Torfinn Ingolfsen wrote: > A quad core machine would be nice. I'm looking at AMD Socket AM2+ and > Phenom. FWIW, an Asus M2A-VM HDMI motherboard and an AMD Phenom 9500 seems to be a working combination (so far). root@kg-vm# uname -a FreeBSD kg-vm.kg4.no 7.0-BETA4 FreeBSD 7.0-BETA4 #0: Sun Dec 2 16:34:41 UTC 2007 root@myers.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >From /var/log/messages: CPU: AMD Phenom(tm) 9500 Quad-Core Processor (2199.93-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x100f22 Stepping = 2 Features=0x178bfbff Features2=0x802009> AMD Features=0xee500800,RDTSCP,LM,3DNow!+,3DNow!> AMD Features2=0x7ff,,,Prefetch,,> Cores per package: 4 usable memory = 4147097600 (3954 MB) avail memory = 3977867264 (3793 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 SMP: AP CPU #3 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! Nice. :) -- Regards, Torfinn Ingolfsen From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 23 12:52:37 2007 Return-Path: Delivered-To: amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3BF416A419 for ; Sun, 23 Dec 2007 12:52:37 +0000 (UTC) (envelope-from erwin@mail.droso.net) Received: from mail.droso.net (koala.ipv6.droso.net [IPv6:2001:6c8:6:0:206:5bff:fef8:267d]) by mx1.freebsd.org (Postfix) with ESMTP id 8FC3513C455 for ; Sun, 23 Dec 2007 12:52:37 +0000 (UTC) (envelope-from erwin@mail.droso.net) Received: by mail.droso.net (Postfix, from userid 1001) id 87FE61CC2F; Sun, 23 Dec 2007 13:52:36 +0100 (CET) Date: Sun, 23 Dec 2007 13:52:36 +0100 From: Erwin Lansing To: amd64@FreeBSD.org Message-ID: <20071223125236.GM1616@droso.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rKoHqF+aPLVth8b2" Content-Disposition: inline User-Agent: Mutt/1.5.16 (2007-06-09) Cc: Subject: Can't panic from debugger X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Dec 2007 12:52:37 -0000 --rKoHqF+aPLVth8b2 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, The amd64 nodes in the pointyhat cluster are starting to behave quite interestingly. They stop to respond to ssh, but are still answering ping. More worrying is that I cannot get a useful dump out of it, as a panic from the debugger just hangs there, and all I am left with is to pull the plug. This even happens on a normal working system after entering the debugger, of which there is a typescript below. FreeBSD hammer1.isc.gumbysoft.com 8.0-CURRENT FreeBSD 8.0-CURRENT #11: Sat Dec 8 17:18:09 UTC 2007 root@danner.isc.gumbysoft.com:/usr/obj/usr/src/sys/HAMMER amd64 http://people.freebsd.org/~erwin/hammer1 -erwin --=20 Erwin Lansing http://droso.org (o_ _o) Errare humanum est \\\_\ /_/// erwin@FreeBSD.org perseverare diabolicum <____) (____> erwin@aauug.dk --rKoHqF+aPLVth8b2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHbloUqy9aWxUlaZARAh73AJ41xhOaJpCPwbOy2ZWqjVHFgwQynwCgsCCv WQ/u4QqNS265ReoIoGoz4Y8= =w9HY -----END PGP SIGNATURE----- --rKoHqF+aPLVth8b2-- From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 23 13:16:31 2007 Return-Path: Delivered-To: amd64@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76ACC16A417 for ; Sun, 23 Dec 2007 13:16:31 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 5F55E13C459 for ; Sun, 23 Dec 2007 13:16:31 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id B799F47936; Sun, 23 Dec 2007 07:58:14 -0500 (EST) Date: Sun, 23 Dec 2007 12:58:14 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Erwin Lansing In-Reply-To: <20071223125236.GM1616@droso.net> Message-ID: <20071223125714.K79882@fledge.watson.org> References: <20071223125236.GM1616@droso.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Sun, 23 Dec 2007 13:18:25 +0000 Cc: amd64@FreeBSD.org Subject: Re: Can't panic from debugger X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Dec 2007 13:16:31 -0000 On Sun, 23 Dec 2007, Erwin Lansing wrote: > The amd64 nodes in the pointyhat cluster are starting to behave quite > interestingly. They stop to respond to ssh, but are still answering ping. > More worrying is that I cannot get a useful dump out of it, as a panic from > the debugger just hangs there, and all I am left with is to pull the plug. > This even happens on a normal working system after entering the debugger, of > which there is a typescript below. > > FreeBSD hammer1.isc.gumbysoft.com 8.0-CURRENT FreeBSD 8.0-CURRENT #11: Sat > Dec 8 17:18:09 UTC 2007 > root@danner.isc.gumbysoft.com:/usr/obj/usr/src/sys/HAMMER amd64 > > http://people.freebsd.org/~erwin/hammer1 I discovered yesterday that I was seeing the same problem on a dual-cpu, dual-core box in the netperf cluster: cheetah-rwatson# sysctl debug.kdb.enter=1 debug.kdb.enter:K DB0: enter: sysctl debug.kdb.enter [thread pid 1136 tid 100091 ] Stopped at kdb_enter+0x3d: movq $0,0x603f38(%rip) db> show pcpu cpuid = 0 curthread = 0xffffff00032e56a0: pid 1136 "sysctl" curpcb = 0xffffffffabae7d40 fpcurthread = none idlethread = 0xffffff00010d56a0: pid 11 "idle: cpu0" spin locks held: db> panic panic: from debugger cpuid = 0 I *can* get a coredump if I directly "call doadump" and then "reset", but I can't get one if I just do "panic". Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 23 19:13:09 2007 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3469916A474 for ; Sun, 23 Dec 2007 19:13:09 +0000 (UTC) (envelope-from nehe@telus.net) Received: from defout.telus.net (defout.telus.net [204.209.205.55]) by mx1.freebsd.org (Postfix) with ESMTP id EE5BF13C458 for ; Sun, 23 Dec 2007 19:13:08 +0000 (UTC) (envelope-from nehe@telus.net) Received: from priv-edtnaa04.telusplanet.net ([204.191.193.188]) by priv-edtnes28.telusplanet.net (InterMail vM.7.08.02.02 201-2186-121-104-20070414) with ESMTP id <20071223184252.TOEY29066.priv-edtnes28.telusplanet.net@priv-edtnaa04.telusplanet.net> for ; Sun, 23 Dec 2007 11:42:52 -0700 Received: from nehe.divine (unknown [204.191.193.188]) by priv-edtnaa04.telusplanet.net (BorderWare MXtreme Infinity Mail Firewall) with ESMTP id 8CR4FA2XWD for ; Sun, 23 Dec 2007 11:42:52 -0700 (MST) Message-ID: <476EAC22.6040008@telus.net> Date: Sun, 23 Dec 2007 11:42:42 -0700 From: Jeff Molofee User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: freebsd-amd64@freebsd.org References: <20071223120004.A35D116A4C2@hub.freebsd.org> In-Reply-To: <20071223120004.A35D116A4C2@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: freebsd-amd64 Digest, Vol 236, Issue 5 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Dec 2007 19:13:09 -0000 I would also love to see a 64bit Nvidia driver. I have been waiting for more than a year now, and I see some people have been waiting up to 3 years (according to the post dates on the nvidia forums). As well, if anyone is able to add Page 0C scancodes to ukbd.c that would also be wonderful :) -- A computer is like air conditioning: it becomes useless when you open windows. From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 23 23:11:01 2007 Return-Path: Delivered-To: amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45C0816A418; Sun, 23 Dec 2007 23:11:01 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from fallbackmx08.syd.optusnet.com.au (fallbackmx08.syd.optusnet.com.au [211.29.132.10]) by mx1.freebsd.org (Postfix) with ESMTP id EFC4513C467; Sun, 23 Dec 2007 23:11:00 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail04.syd.optusnet.com.au (mail04.syd.optusnet.com.au [211.29.132.185]) by fallbackmx08.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id lBNKQ4eg026690; Mon, 24 Dec 2007 07:26:04 +1100 Received: from c211-30-219-213.carlnfd3.nsw.optusnet.com.au (c211-30-219-213.carlnfd3.nsw.optusnet.com.au [211.30.219.213]) by mail04.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id lBNKQ1LJ019168 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Dec 2007 07:26:02 +1100 Date: Mon, 24 Dec 2007 07:26:01 +1100 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Robert Watson In-Reply-To: <20071223125714.K79882@fledge.watson.org> Message-ID: <20071224065516.K4239@delplex.bde.org> References: <20071223125236.GM1616@droso.net> <20071223125714.K79882@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: amd64@freebsd.org Subject: Re: Can't panic from debugger X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Dec 2007 23:11:01 -0000 On Sun, 23 Dec 2007, Robert Watson wrote: > On Sun, 23 Dec 2007, Erwin Lansing wrote: > >> The amd64 nodes in the pointyhat cluster are starting to behave quite >> interestingly. They stop to respond to ssh, but are still answering ping. >> More worrying is that I cannot get a useful dump out of it, as a panic from >> the debugger just hangs there, and all I am left with is to pull the plug. >> This even happens on a normal working system after entering the debugger, >> of which there is a typescript below. >> ... > I discovered yesterday that I was seeing the same problem on a dual-cpu, > dual-core box in the netperf cluster: This is as expected. Debugger context is special, and no non-debugger functions can be called from it without going through the (unimplemented) trampoline needed to temporarily leave it. Some non-debugger functions may work accidentally or appear to work when called directly. panic() is not one of these, since it tends to trip over a lock. panic() called from an arbitrary context has the same problem, since the calling context may hold a lock that is used by panic(). Debugger context always holds the pseudo-spinlock of masked CPU interrupts and stopped other CPUs. panic() (actually boot()) normally begins with a normal sync() call that is not aware that it may be called in either panic or debugger context and depends on a large amount of system code working normally. It cannot legitimately sync anything when called in debugger context, since syncing requires i/o and i/o normally requires interrupts. > I *can* get a coredump if I directly "call doadump" and then "reset", but I > can't get one if I just do "panic". Dumps have some chance of working since they are required to try harder than sync() to work in any context. In particular, they are or were aware that they are not permitted to use interrupts. Reset has a better chance of working since it is simpler and reset is a legitimate debugger command. I was asleep when the panic debugger command was added. Interrupt-driven I/O in sync for panics back then tended to work bogusly by blowing away both spl*() masks and the hard CPU interrupt disable mask. Bruce From owner-freebsd-amd64@FreeBSD.ORG Mon Dec 24 11:06:54 2007 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45F6116A475 for ; Mon, 24 Dec 2007 11:06:54 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 28D1E13C4E1 for ; Mon, 24 Dec 2007 11:06:54 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id lBOB6sXD031865 for ; Mon, 24 Dec 2007 11:06:54 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id lBOB6rS1031861 for freebsd-amd64@FreeBSD.org; Mon, 24 Dec 2007 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 24 Dec 2007 11:06:53 GMT Message-Id: <200712241106.lBOB6rS1031861@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-amd64@FreeBSD.org X-Mailman-Approved-At: Mon, 24 Dec 2007 12:24:10 +0000 Cc: Subject: Current problem reports assigned to freebsd-amd64@FreeBSD.org X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Dec 2007 11:06:54 -0000 Current FreeBSD problem reports Critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/112222 amd64 [libc] 32-bit libc incorrectly converts some FP number 1 problem total. Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/73322 amd64 [msdosfs] [hang] unarchiving /etc to msdosfs locks up o amd64/74747 amd64 System panic on shutdown when process will not die o amd64/76136 amd64 system halts before reboot o amd64/78406 amd64 [panic]AMD64 w/ SCSI: issue 'rm -r /usr/ports' and sys o amd64/80691 amd64 amd64 kernel hangs on load o amd64/85451 amd64 [hang] 6.0-BETA3 lockups on AMD64 (PREEMPTION only) o amd64/86080 amd64 [radeon] [hang] radeon DRI causes system hang on amd64 o amd64/87258 amd64 [smp] [boot] cannot boot with SMP and Areca ARC-1160 r o amd64/87305 amd64 [smp] Dual Opteron / FreeBSD 5 & 6 / powerd results in o amd64/87316 amd64 [vge] "vge0 attach returned 6" on FreeBSD 6.0-RC1 amd6 o amd64/87689 amd64 [powerd] [hang] powerd hangs SMP Opteron 244 5-STABLE o amd64/87977 amd64 [busdma] [panic] amd64 busdma dflt_lock called (by ata o amd64/88568 amd64 [panic] 6.0-RELEASE install cd does not boot with usb o amd64/88790 amd64 kernel panic on first boot (after the FreeBSD installa o amd64/89501 amd64 System crashes on install using ftp on local subnet o amd64/89503 amd64 Cant Boot Installation Disk o amd64/89546 amd64 [geom] GEOM error o amd64/91405 amd64 [asr] [panic] Kernel panic caused by asr on 6.0-amd64 o amd64/91492 amd64 BTX halted o amd64/92337 amd64 [em] FreeBSD 6.0 Release Intel Pro 1000 MT em1 no buff o amd64/92889 amd64 [libc] xdr double buffer overflow o amd64/93961 amd64 [busdma] Problem in bounce buffer handling in sys/amd6 o amd64/94677 amd64 panic in amd64 install at non-root user creation o amd64/94989 amd64 BTX Halts on Sun Fire X2100 w/6.1-BETA4 (amd64) and 5. f amd64/95414 amd64 kernel crashes during install o amd64/95888 amd64 kernel: ad2: TIMEOUT - WRITE_DMA retrying on HP DL140G f amd64/97075 amd64 Panic, Trap 12 o amd64/97337 amd64 [dri] xorg reboots system if dri module is enabled o amd64/102122 amd64 6.1-RELEASE amd64 Install Media panics on boot. s amd64/104311 amd64 ports/wine should be installable on amd64 f amd64/105514 amd64 FreeBSD/amd64 - Fails to boot on HP Pavilion dv8000 La o amd64/105531 amd64 [sata] gigabyte GA-M51GM-S2G / nVidia nForce 430 - doe o amd64/105629 amd64 [re] TrendNet TEG-BUSR 10/100/1000 disables itself on o amd64/106604 amd64 saslauthd crashes with signal 6 on FreeBSD 6.2-PREREL o amd64/108861 amd64 [nve] nve(4) driver on FreeBSD 6.2 AMD64 does not work f amd64/109584 amd64 zdump doesn't work o amd64/110655 amd64 [threads] 32 bit threaded applications crash on amd64 o amd64/111955 amd64 [install] Install CD boot panic due to missing BIOS sm o amd64/111992 amd64 BTX failed - HP Laptop dv2315nr s gnu/112215 amd64 [patch] gcc(1): "gcc -m32" attempts to link against 64 o amd64/112677 amd64 [aac] Adaptec 4805SAS causes 6.2 (AMD64) to panic (amd o amd64/113021 amd64 [re] ASUS M2A-VM onboard NIC does not work o amd64/114111 amd64 [nfs] System crashes while writing on NFS-mounted shar o amd64/115194 amd64 LCD screen remains blank after Dell XPS M1210 lid is c o amd64/115784 amd64 Compiling with -m32 breaks on FreeBSD/amd64 s amd64/115815 amd64 [sata] [request] Gigabyte GA-M61P-S3 Motherboard unsup o amd64/116159 amd64 Panic while debugging on CURRENT o amd64/116322 amd64 At start fsck on current, the system panics o amd64/116620 amd64 Ifconfig spins when creating carp(4) device on amd64/S o amd64/116977 amd64 FreeBSD/amd64 - Fails to boot on HP Pavilion dv9030ea o amd64/117296 amd64 [sata] I don`t see second SATA IDE on VIA VT8237A o amd64/117316 amd64 [acpi] ACPI lockups on SuperMicro motherboard o amd64/117418 amd64 FreeBSD 6.2 crash on amd64 4400+ o amd64/117858 amd64 can not install / does not recognize network / no netw o amd64/117972 amd64 [ast] SATA DLT V4 not recognized properly 55 problems total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- o amd64/74608 amd64 [mpt] [hang] mpt hangs 5 minutes when booting s amd64/85273 amd64 FreeBSD (NetBSD or OpenBSD) not install on laptop Comp o amd64/88730 amd64 kernel panics during booting from the installation CD o amd64/91195 amd64 FreeBSD 6.0(amd64) and Asus A8R-MVP a amd64/93002 amd64 amd64 (6.0) coredumps at unpredictable times a amd64/93090 amd64 [nve] NIC on GA-K8NF-9 motherboard is recognized, but o amd64/97489 amd64 [ata] nForce 410 ATA controller dma time out (ASUS K8N o amd64/100326 amd64 [fdc] /dev/fd0 not created after installation FreeBSD o amd64/100838 amd64 [powerd] FreeBSD 6.0/6.1 kernel panics when booting wi f amd64/101132 amd64 [smp] Incorrect cpu idle and usage statistics in top a o amd64/102716 amd64 ex with no argument in an xterm gets SIGSEGV o amd64/103259 amd64 [ar] Cannot use ataraid on nvidia nForce4+amd64 o bin/105542 amd64 on amd64, ldd(1) produces bogus output for i386 execut o amd64/106186 amd64 [panic] panic in swap_pager_swap_init (amd64/smp/6.2-p f amd64/108345 amd64 6.2-* GENERIC will not boot Intel PD EMT64 w/ ACPI o amd64/110599 amd64 [geli] geli attach to gmirror device hangs and cannot o amd64/111096 amd64 motherboard ASRock AM2NF6G-VSTA not supported a amd64/113111 amd64 [Makefile] [patch] Potentially wrong instructions will o amd64/114270 amd64 [cpufreq] cpufreq doesnt work when compiled in to kern o amd64/115581 amd64 [patch] -mfancy-math-387 has no effect o amd64/116457 amd64 cant install freebsd on dv9420us o amd64/116514 amd64 freebsd6.2 can't detect GA-M61SME-S2's onboard lan car o amd64/116670 amd64 [sata] onboard SATA RAID1 controllers not supported fo o amd64/116689 amd64 [request] support for MSI K9MM-V o amd64/117186 amd64 kldload Unsupported file type on STABLE amd64 25 problems total. From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 26 14:00:22 2007 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E8D416A420 for ; Wed, 26 Dec 2007 14:00:22 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.freebsd.org (Postfix) with ESMTP id 0B3F913C461 for ; Wed, 26 Dec 2007 14:00:22 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with ESMTP id <0JTN00F04TKK2T20@osl1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Wed, 26 Dec 2007 15:00:20 +0100 (CET) Received: from kg-work.kg4.no ([80.202.173.59]) by osl1sminn1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with SMTP id <0JTN007ADTKIVXM3@osl1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Wed, 26 Dec 2007 15:00:20 +0100 (CET) Date: Wed, 26 Dec 2007 15:00:18 +0100 From: Torfinn Ingolfsen To: freebsd-amd64@freebsd.org Message-id: <20071226150018.6ed4fb5e.torfinn.ingolfsen@broadpark.no> In-reply-to: <20071223055236.ebf95247.torfinn.ingolfsen@broadpark.no> References: <20071221022122.a4b4c7c9.torfinn.ingolfsen@broadpark.no> <20071223055236.ebf95247.torfinn.ingolfsen@broadpark.no> X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.3; i386-portbld-freebsd6.2) X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH Subject: Re: Recommended motherboard + cpu combination for AMD Socket AM2+ / Phenom? X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Dec 2007 14:00:22 -0000 On Sun, 23 Dec 2007 05:52:36 +0100 Torfinn Ingolfsen wrote: > FWIW, an Asus M2A-VM HDMI motherboard and an AMD Phenom 9500 seems to > be a working combination (so far). Ok, I found a (strange) problem. If I plug in a usb keyboard after the machine is up and running, it works fine. From /var/log/messages: Dec 25 21:44:25 kg-vm root: Unknown USB device: vendor 0x046d product 0xc512 bus uhub2 Dec 25 21:44:25 kg-vm kernel: ukbd0: on uhub2 Dec 25 21:44:25 kg-vm kernel: kbd2 at ukbd0 Dec 25 21:44:25 kg-vm kernel: ums0: on uhub2 Dec 25 21:44:25 kg-vm kernel: ums0: 16 buttons and Z dir. And output from 'usbdevs -v': root@kg-vm# usbdevs -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), ATI(0x0000), rev 1.00 port 1 powered port 2 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), ATI(0x0000), rev 1.00 port 1 powered port 2 powered Controller /dev/usb2: addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), ATI(0x0000), rev 1.00 port 1 addr 2: low speed, power 98 mA, config 1, USB Receiver(0xc512), Logitech(0x046d), rev 30.07 port 2 powered Controller /dev/usb3: addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), ATI(0x0000), rev 1.00 port 1 powered port 2 powered Controller /dev/usb4: addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), ATI(0x0000), rev 1.00 port 1 powered port 2 powered Controller /dev/usb5: addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), ATI(0x0000), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered port 5 powered port 6 powered port 7 powered port 8 powered port 9 powered port 10 powered So far everything is good. However, if a usb keyboard is attached when FreeBSD boots, the machine panics during boot, with some message about ohci. I have tried with two different usb keyboards (different make and model) - same problem. If I try with a usb mouse instead, the machine doesn't panic during boot, it just disablesthe port that the mouse is attached to. I haven't seen this kind of error before, and doesn't know how to debug this further. any hints welcome. As always, output and info is at the machine page: http://tingox.googlepages.com/asus_m2a-vm_hdmi_freebsd -- Regards, Torfinn Ingolfsen From owner-freebsd-amd64@FreeBSD.ORG Wed Dec 26 20:30:05 2007 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DD8316A46B for ; Wed, 26 Dec 2007 20:30:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 239BF13C442 for ; Wed, 26 Dec 2007 20:30:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id lBQKU4cY058340 for ; Wed, 26 Dec 2007 20:30:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id lBQKU4KB058333; Wed, 26 Dec 2007 20:30:04 GMT (envelope-from gnats) Resent-Date: Wed, 26 Dec 2007 20:30:04 GMT Resent-Message-Id: <200712262030.lBQKU4KB058333@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, Sebastian Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7447316A417 for ; Wed, 26 Dec 2007 20:25:13 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id 694E513C468 for ; Wed, 26 Dec 2007 20:25:13 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.2/8.14.2) with ESMTP id lBQKObhI036699 for ; Wed, 26 Dec 2007 20:24:37 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.2/8.14.1/Submit) id lBQKObxG036698; Wed, 26 Dec 2007 20:24:37 GMT (envelope-from nobody) Message-Id: <200712262024.lBQKObxG036698@www.freebsd.org> Date: Wed, 26 Dec 2007 20:24:37 GMT From: Sebastian To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 X-Mailman-Approved-At: Wed, 26 Dec 2007 20:47:56 +0000 Cc: Subject: amd64/119047: Not correct working RealTek 8168/8111B PCIe Gigabit Ethernet X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Dec 2007 20:30:05 -0000 >Number: 119047 >Category: amd64 >Synopsis: Not correct working RealTek 8168/8111B PCIe Gigabit Ethernet >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Dec 26 20:30:04 UTC 2007 >Closed-Date: >Last-Modified: >Originator: Sebastian >Release: FreeBSD 7.0-PRERELEASE >Organization: >Environment: FreeBSD bluxx.mueller.mn 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #1: Tue Dec 25 21:52:51 CET 2007 basti@bluxx.mueller.mn:/usr/obj/usr/src/sys/GENERIC amd64 >Description: Hi, I've got a RealTek 8168/8111B PCIe Gigabit Ethernet network chip, connected to a 100mbit switch, DHCP is not working. Furthermore all network traffic is getting worse after some time, I don't know how to explain it exactly. When starting the system, everthing works fine, but after 2-3 days uptime SSH connections are breaking with "Garbled packet", Websites on this apache Server are not displayed, pictures are 0 byte big when opening in a browser, ftp connections are timing out (starting speed with 2-3kbyte, normal speed is 5mbyte). After a reboot of the machine, everything is working fine again, I tried to look if the hardware is damaged, on debian everything worked fine. Please help me solving this problem. Dmesg: Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-BETA4 #9: Mon Dec 17 06:08:19 CET 2007 basti@bluxx.mueller.mn:/usr/obj/usr/src/sys/bluxx Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ (2999.99-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x40f33 Stepping = 3 Features=0x178bfbff Features2=0x2001 AMD Features=0xea500800 AMD Features2=0x1f Cores per package: 2 usable memory = 6400897024 (6104 MB) avail memory = 6184538112 (5898 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, ddf00000 (3) failed ACPI HPET table warning: Sequence is non-zero (2) Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 cpu0: on acpi0 acpi_throttle0: on cpu0 acpi_throttle0: CLK_VAL field overlaps THT_EN bit device_attach: acpi_throttle0 attach returned 6 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xc000-0xc0ff mem 0xfc000000-0xfdffffff,0xfe9f0000-0xfe9fffff,0xfe800000-0xfe8fffff irq 18 at device 5.0 on pci1 pci1: at device 5.2 (no driver attached) pcib2: at device 7.0 on pci0 pci2: on pcib2 re0: port 0xd800-0xd8ff mem 0xfeaff000-0xfeafffff irq 19 at device 0.0 on pci2 re0: Using 2 MSI messages miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:19:db:d0:35:aa re0: [FILTER] re0: [FILTER] atapci0: port 0xb000-0xb007,0xa000-0xa003,0x9000-0x9007,0x8000-0x8003,0x7000-0x700f mem 0xfe7ff800-0xfe7ffbff irq 22 at device 18.0 on atapci0: [ITHREAD] atapci0: AHCI Version 01.10 controller with 4 ports detected ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ata4: on atapci0 ata4: [ITHREAD] ata5: on atapci0 ata5: [ITHREAD] ohci0: mem 0xfe7fe000-0xfe7fefff irq 16 at device 19.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered ohci1: mem 0xfe7fd000-0xfe7fdfff irq 17 at device 19.1 on pci0 ohci1: [GIANT-LOCKED] ohci1: [ITHREAD] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered ohci2: mem 0xfe7fc000-0xfe7fcfff irq 18 at device 19.2 on pci0 ohci2: [GIANT-LOCKED] ohci2: [ITHREAD] usb2: OHCI version 1.0, legacy support usb2: SMM does not respond, resetting usb2: on ohci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered ohci3: mem 0xfe7fb000-0xfe7fbfff irq 17 at device 19.3 on pci0 ohci3: [GIANT-LOCKED] ohci3: [ITHREAD] usb3: OHCI version 1.0, legacy support usb3: SMM does not respond, resetting usb3: on ohci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ohci4: mem 0xfe7fa000-0xfe7fafff irq 18 at device 19.4 on pci0 ohci4: [GIANT-LOCKED] ohci4: [ITHREAD] usb4: OHCI version 1.0, legacy support usb4: SMM does not respond, resetting usb4: on ohci4 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered ehci0: mem 0xfe7ff000-0xfe7ff0ff irq 19 at device 19.5 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb5: EHCI version 1.0 usb5: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4 usb5: on ehci0 usb5: USB revision 2.0 uhub5: on usb5 uhub5: 10 ports with 10 removable, self powered pci0: at device 20.0 (no driver attached) atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on pci0 ata0: on atapci1 ata0: [ITHREAD] isab0: at device 20.3 on pci0 isa0: on isab0 pcib3: at device 20.4 on pci0 pci3: on pcib3 acpi_button0: on acpi0 sio0: configured irq 3 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 3 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] orm0: at iomem 0xcd800-0xce7ff on isa0 ppc0: cannot reserve I/O port range sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec ad4: 715404MB at ata2-master SATA150 ad6: 715404MB at ata3-master SATA150 SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad4s1a >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 27 10:16:03 2007 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 431CD16A417 for ; Thu, 27 Dec 2007 10:16:03 +0000 (UTC) (envelope-from freebsd@abv.bg) Received: from smtp-out.abv.bg (smtp-out.abv.bg [194.153.145.70]) by mx1.freebsd.org (Postfix) with ESMTP id 427D513C448 for ; Thu, 27 Dec 2007 10:16:02 +0000 (UTC) (envelope-from freebsd@abv.bg) Received: from mail54.abv.bg (mail54.ni.bg [192.168.151.57]) by smtp-out.abv.bg (Postfix) with ESMTP id EA03814AD0A for ; Thu, 27 Dec 2007 12:15:49 +0200 (EET) DomainKey-Signature: a=rsa-sha1; s=smtp-out; d=abv.bg; c=simple; q=dns; b=B4olBrUBDvm+eoWjRGz8GpvIkwXa6+wRa4RJF3sVNTfHiJCKhw8qEvl8dXNxtqzJs cq/kAoIgsrbI5pD6HkxYXqgsRr+9KTxEaWjwf0B/Wx/L+/Eeo/MavNtXOVZE3KQXROg wgV8Mf/6aYllSM05gR9n7XzI01JWPmdgHyag4zA= DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=abv.bg; s=smtp-out; t=1198750549; bh=KjxAQllVug6QLeDJzNCGrbfUVH8=; h=Received:Date:From: To:Message-ID:Subject:MIME-Version:Content-Type: Content-Transfer-Encoding:X-Priority:X-Mailer:X-Originating-IP: DomainKey; b=JrIJcFOUkAaq7g7rtx8lSFHeoAQUfoZIDpd4AjI9HZCcqlJmeBvbb 9ZOYdihSI8t+pffmkHcM7/rIXJJUa01dlaTnyqC1JYlBuesqFmxFRFJStviVgRp+aNM 9nTJAVm+0xwZuQcsGp6zCFrjUH3jo+FHgyyXfBq7fSI0OLI6G1M= Received: from mail54.abv.bg (localhost [127.0.0.1]) by mail54.abv.bg (Postfix) with ESMTP id 265EA1A261A for ; Thu, 27 Dec 2007 12:16:00 +0200 (EET) Date: Thu, 27 Dec 2007 12:16:00 +0200 (EET) From: Mario Pavlov To: freebsd-amd64@freebsd.org Message-ID: <1825008839.105809.1198750560154.JavaMail.nobody@mail54.abv.bg> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: 8bit X-Priority: 3 X-Mailer: AbvMail 1.0 X-Originating-IP: 78.128.21.208 Subject: Re: amd64/119047: Not correct working RealTek 8168/8111B PCIe Gigabit Ethernet X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Dec 2007 10:16:03 -0000 >>Number: 119047 >>Category: amd64 >>Synopsis: Not correct working RealTek 8168/8111B PCIe Gigabit Ethernet >>Confidential: no >>Severity: serious >>Priority: medium >>Responsible: freebsd-amd64 >>State: open >>Quarter: >>Keywords: >>Date-Required: >>Class: sw-bug >>Submitter-Id: current-users >>Arrival-Date: Wed Dec 26 20:30:04 UTC 2007 >>Closed-Date: >>Last-Modified: >>Originator: Sebastian >>Release: FreeBSD 7.0-PRERELEASE >>Organization: >>Environment: >FreeBSD bluxx.mueller.mn 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #1: Tue Dec 25 21:52:51 CET 2007 basti@bluxx.mueller.mn:/usr/obj/usr/src/sys/GENERIC amd64 > >>Description: >Hi, > >I've got a RealTek 8168/8111B PCIe Gigabit Ethernet network chip, connected to a 100mbit switch, DHCP is not working. Furthermore all network traffic is getting worse after some time, I don't know how to explain it exactly. >When starting the system, everthing works fine, but after 2-3 days uptime SSH connections are breaking with "Garbled packet", Websites on this apache Server are not displayed, pictures are 0 byte big when opening in a browser, ftp connections are timing out (starting speed with 2-3kbyte, normal speed is 5mbyte). After a reboot of the machine, everything is working fine again, I tried to look if the hardware is damaged, on debian everything worked fine. > >Please help me solving this problem. > > > >Dmesg: > >Copyright (c) 1992-2007 The FreeBSD Project. >Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. >FreeBSD is a registered trademark of The FreeBSD Foundation. >FreeBSD 7.0-BETA4 #9: Mon Dec 17 06:08:19 CET 2007 > basti@bluxx.mueller.mn:/usr/obj/usr/src/sys/bluxx >Timecounter "i8254" frequency 1193182 Hz quality 0 >CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ (2999.99-MHz K8-class CPU) > Origin = "AuthenticAMD" Id = 0x40f33 Stepping = 3 > Features=0x178bfbff > Features2=0x2001 > AMD Features=0xea500800 > AMD Features2=0x1f > Cores per package: 2 >usable memory = 6400897024 (6104 MB) >avail memory = 6184538112 (5898 MB) >ACPI APIC Table: >FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 >ioapic0 irqs 0-23 on motherboard >acpi0: on motherboard >acpi0: [ITHREAD] >acpi0: Power Button (fixed) >acpi0: reservation of 0, a0000 (3) failed >acpi0: reservation of 100000, ddf00000 (3) failed >ACPI HPET table warning: Sequence is non-zero (2) >Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 >acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 >acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 >Timecounter "HPET" frequency 14318180 Hz quality 900 >cpu0: on acpi0 >acpi_throttle0: on cpu0 >acpi_throttle0: CLK_VAL field overlaps THT_EN bit >device_attach: acpi_throttle0 attach returned 6 >cpu1: on acpi0 >pcib0: port 0xcf8-0xcff on acpi0 >pci0: on pcib0 >pcib1: at device 1.0 on pci0 >pci1: on pcib1 >vgapci0: port 0xc000-0xc0ff mem 0xfc000000-0xfdffffff,0xfe9f0000-0xfe9fffff,0xfe800000-0xfe8fffff irq 18 at device 5.0 on pci1 >pci1: at device 5.2 (no driver attached) >pcib2: at device 7.0 on pci0 >pci2: on pcib2 >re0: port 0xd800-0xd8ff mem 0xfeaff000-0xfeafffff irq 19 at device 0.0 on pci2 >re0: Using 2 MSI messages >miibus0: on re0 >rgephy0: PHY 1 on miibus0 >rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto >re0: Ethernet address: 00:19:db:d0:35:aa >re0: [FILTER] >re0: [FILTER] >atapci0: port 0xb000-0xb007,0xa000-0xa003,0x9000-0x9007,0x8000-0x8003,0x7000-0x700f mem 0xfe7ff800-0xfe7ffbff irq 22 at device 18.0 on >atapci0: [ITHREAD] >atapci0: AHCI Version 01.10 controller with 4 ports detected >ata2: on atapci0 >ata2: [ITHREAD] >ata3: on atapci0 >ata3: [ITHREAD] >ata4: on atapci0 >ata4: [ITHREAD] >ata5: on atapci0 >ata5: [ITHREAD] >ohci0: mem 0xfe7fe000-0xfe7fefff irq 16 at device 19.0 on pci0 >ohci0: [GIANT-LOCKED] >ohci0: [ITHREAD] >usb0: OHCI version 1.0, legacy support >usb0: SMM does not respond, resetting >usb0: on ohci0 >usb0: USB revision 1.0 >uhub0: on usb0 >uhub0: 2 ports with 2 removable, self powered >ohci1: mem 0xfe7fd000-0xfe7fdfff irq 17 at device 19.1 on pci0 >ohci1: [GIANT-LOCKED] >ohci1: [ITHREAD] >usb1: OHCI version 1.0, legacy support >usb1: SMM does not respond, resetting >usb1: on ohci1 >usb1: USB revision 1.0 >uhub1: on usb1 >uhub1: 2 ports with 2 removable, self powered >ohci2: mem 0xfe7fc000-0xfe7fcfff irq 18 at device 19.2 on pci0 >ohci2: [GIANT-LOCKED] >ohci2: [ITHREAD] >usb2: OHCI version 1.0, legacy support >usb2: SMM does not respond, resetting >usb2: on ohci2 >usb2: USB revision 1.0 >uhub2: on usb2 >uhub2: 2 ports with 2 removable, self powered >ohci3: mem 0xfe7fb000-0xfe7fbfff irq 17 at device 19.3 on pci0 >ohci3: [GIANT-LOCKED] >ohci3: [ITHREAD] >usb3: OHCI version 1.0, legacy support >usb3: SMM does not respond, resetting >usb3: on ohci3 >usb3: USB revision 1.0 >uhub3: on usb3 >uhub3: 2 ports with 2 removable, self powered >ohci4: mem 0xfe7fa000-0xfe7fafff irq 18 at device 19.4 on pci0 >ohci4: [GIANT-LOCKED] >ohci4: [ITHREAD] >usb4: OHCI version 1.0, legacy support >usb4: SMM does not respond, resetting >usb4: on ohci4 >usb4: USB revision 1.0 >uhub4: on usb4 >uhub4: 2 ports with 2 removable, self powered >ehci0: mem 0xfe7ff000-0xfe7ff0ff irq 19 at device 19.5 on pci0 >ehci0: [GIANT-LOCKED] >ehci0: [ITHREAD] >usb5: EHCI version 1.0 >usb5: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4 >usb5: on ehci0 >usb5: USB revision 2.0 >uhub5: on usb5 >uhub5: 10 ports with 10 removable, self powered >pci0: at device 20.0 (no driver attached) >atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 20.1 on pci0 >ata0: on atapci1 >ata0: [ITHREAD] >isab0: at device 20.3 on pci0 >isa0: on isab0 >pcib3: at device 20.4 on pci0 >pci3: on pcib3 >acpi_button0: on acpi0 >sio0: configured irq 3 not in bitmap of probed irqs 0 >sio0: port may not be enabled >sio0: configured irq 3 not in bitmap of probed irqs 0 >sio0: port may not be enabled >sio0: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 flags 0x10 on acpi0 >sio0: type 16550A >sio0: [FILTER] >atkbdc0: port 0x60,0x64 irq 1 on acpi0 >atkbd0: irq 1 on atkbdc0 >kbd0 at atkbd0 >atkbd0: [GIANT-LOCKED] >atkbd0: [ITHREAD] >orm0: at iomem 0xcd800-0xce7ff on isa0 >ppc0: cannot reserve I/O port range >sc0: at flags 0x100 on isa0 >sc0: VGA <16 virtual consoles, flags=0x300> >vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 >Timecounters tick every 1.000 msec >ad4: 715404MB at ata2-master SATA150 >ad6: 715404MB at ata3-master SATA150 >SMP: AP CPU #1 Launched! >Trying to mount root from ufs:/dev/ad4s1a > > >>How-To-Repeat: > >>Fix: > > >>Release-Note: >>Audit-Trail: >>Unformatted: Hi, I'm experiencing exactly the same problem after reboot everything is OK but after some time all network transfers are getting worse and worse. The packet loss goes above 50% you can easily reproduce this, without waiting days, with the fallowing steps: * reboot * plug some local network to the "re" interface * start FTP download from machine in the local network to the FreeBSD-amd64 (and make sure you start downloading of significant amount of data...for example 50GBs) * wait some minutes until the speed starts getting lower I've tried this with windows and it appears to be working there...haven't tried it with linux I've tried different kernel configuration but the result is still the same I've tried to listen with tcpdump but it seemed normal except for the packet loss (I can see all requests but not all responses are returned) my motherboard is Asus P5B with chipset Intel P965 and integrated RealTek 8168/8111B PCIe Gigabit Ethernet $ dmesg Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-PRERELEASE #0: Tue Dec 25 18:50:04 EET 2007 root@e-soul.org:/usr/obj/usr/src/sys/Ss Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz (2206.71-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6fd Stepping = 13 Features=0xbfebfbff Features2=0xe39d AMD Features=0x20100800 AMD Features2=0x1 Cores per package: 2 usable memory = 4285284352 (4086 MB) avail memory = 4084629504 (3895 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 7ff00000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 cpu0: on acpi0 ACPI Warning (tbutils-0243): Incorrect checksum in table [OEMB] - EB, should be E6 [20070320] est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr b280b2806000b28 device_attach: est0 attach returned 6 p4tcc0: on cpu0 cpu1: on acpi0 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr b280b2806000b28 device_attach: est1 attach returned 6 p4tcc1: on cpu1 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0x8c00-0x8c7f mem 0xfd000000-0xfdffffff,0xc0000000-0xcfffffff,0xfc000000-0xfcffffff irq 16 at device 0.0 on pci1 uhci0: port 0xdc00-0xdc1f irq 16 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xe000-0xe01f irq 17 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered ehci0: mem 0xfebffc00-0xfebfffff irq 18 at device 26.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb2: waiting for BIOS to give up control usb2: EHCI version 1.0 usb2: companion controllers, 2 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: on usb2 uhub2: 4 ports with 4 removable, self powered pcm0: mem 0xfebf8000-0xfebfbfff irq 22 at device 27.0 on pci0 pcm0: [ITHREAD] pcib2: irq 16 at device 28.0 on pci0 pci4: on pcib2 pcib3: irq 19 at device 28.3 on pci0 pci3: on pcib3 re0: port 0xa800-0xa8ff mem 0xfe9ff000-0xfe9fffff irq 19 at device 0.0 on pci3 re0: Using 2 MSI messages miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto re0: Ethernet address: 00:1d:60:2a:4f:56 re0: [FILTER] re0: [FILTER] pcib4: irq 16 at device 28.4 on pci0 pci2: on pcib4 atapci0: port 0x9c00-0x9c07,0x9880-0x9883,0x9800-0x9807,0x9480-0x9483,0x9400-0x940f mem 0xfe8fe000-0xfe8fffff irq 16 at device 0.0 on pci2 atapci0: [ITHREAD] atapci0: AHCI called from vendor specific driver atapci0: AHCI Version 01.00 controller with 2 ports detected ata2: on atapci0 ata2: [ITHREAD] ata3: on atapci0 ata3: [ITHREAD] ata4: on atapci0 ata4: [ITHREAD] uhci2: port 0xd480-0xd49f irq 23 at device 29.0 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb3: on uhci2 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered uhci3: port 0xd800-0xd81f irq 19 at device 29.1 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb4: on uhci3 usb4: USB revision 1.0 uhub4: on usb4 uhub4: 2 ports with 2 removable, self powered uhci4: port 0xd880-0xd89f irq 18 at device 29.2 on pci0 uhci4: [GIANT-LOCKED] uhci4: [ITHREAD] usb5: on uhci4 usb5: USB revision 1.0 uhub5: on usb5 uhub5: 2 ports with 2 removable, self powered ehci1: mem 0xfebff800-0xfebffbff irq 23 at device 29.7 on pci0 ehci1: [GIANT-LOCKED] ehci1: [ITHREAD] usb6: EHCI version 1.0 usb6: companion controllers, 2 ports each: usb3 usb4 usb5 usb6: on ehci1 usb6: USB revision 2.0 uhub6: on usb6 uhub6: 6 ports with 6 removable, self powered pcib5: at device 30.0 on pci0 pci5: on pcib5 dc0: port 0xb800-0xb8ff mem 0xfeaffc00-0xfeaffcff irq 22 at device 1.0 on pci5 miibus1: on dc0 amphy0: PHY 1 on miibus1 amphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: Ethernet address: 00:08:a1:27:88:1c dc0: [ITHREAD] rl0: port 0xb400-0xb4ff mem 0xfeaff800-0xfeaff8ff irq 23 at device 2.0 on pci5 miibus2: on rl0 rlphy0: PHY 0 on miibus2 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:19:e0:0e:a7:fa rl0: [ITHREAD] isab0: at device 31.0 on pci0 isa0: on isab0 atapci1: port 0xec00-0xec07,0xe880-0xe883,0xe800-0xe807,0xe480-0xe483,0xe400-0xe40f,0xe080-0xe08f irq 19 at device 31.2 on pci0 atapci1: [ITHREAD] ata5: on atapci1 ata5: [ITHREAD] ata6: on atapci1 ata6: [ITHREAD] pci0: at device 31.3 (no driver attached) atapci2: port 0xd400-0xd407,0xd080-0xd083,0xd000-0xd007,0xcc00-0xcc03,0xc880-0xc88f,0xc800-0xc80f irq 19 at device 31.5 on pci0 atapci2: [ITHREAD] ata7: on atapci2 ata7: [ITHREAD] ata8: on atapci2 ata8: [ITHREAD] acpi_button0: on acpi0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model IntelliMouse, device ID 3 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ukbd0: on uhub3 kbd2 at ukbd0 uhid0: on uhub3 Timecounters tick every 1.000 msec ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to deny, logging unlimited ad10: 476940MB at ata5-master SATA150 acd0: DVDR at ata6-master SATA150 pcm0: pcm0: SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad10s2a rl0: link state changed to UP re0: link state changed to UP Regards MGP P.S. since this is my home PC I can provide access to it if someone wants to take a look ----------------------------------------------------------------- Коментирай и гласувай за най-лудия фен на Rihanna! vivarihanna.zoom.bg From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 27 15:22:15 2007 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9709F16A417 for ; Thu, 27 Dec 2007 15:22:15 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) Received: from osl1smout1.broadpark.no (osl1smout1.broadpark.no [80.202.4.58]) by mx1.freebsd.org (Postfix) with ESMTP id 95BC513C4D3 for ; Thu, 27 Dec 2007 15:22:14 +0000 (UTC) (envelope-from torfinn.ingolfsen@broadpark.no) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII Received: from osl1sminn1.broadpark.no ([80.202.4.59]) by osl1smout1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with ESMTP id <0JTP002CYS0KQ960@osl1smout1.broadpark.no> for freebsd-amd64@freebsd.org; Thu, 27 Dec 2007 16:21:56 +0100 (CET) Received: from kg-work.kg4.no ([80.202.173.59]) by osl1sminn1.broadpark.no (Sun Java(tm) System Messaging Server 6.3-3.01 (built Jul 12 2007; 32bit)) with SMTP id <0JTP009BHS0JIA41@osl1sminn1.broadpark.no> for freebsd-amd64@freebsd.org; Thu, 27 Dec 2007 16:21:56 +0100 (CET) Date: Thu, 27 Dec 2007 16:21:55 +0100 From: Torfinn Ingolfsen To: freebsd-amd64@freebsd.org Message-id: <20071227162155.9a9bd2f1.torfinn.ingolfsen@broadpark.no> In-reply-to: <1825008839.105809.1198750560154.JavaMail.nobody@mail54.abv.bg> References: <1825008839.105809.1198750560154.JavaMail.nobody@mail54.abv.bg> X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.3; i386-portbld-freebsd6.2) X-Face: "t9w2,-X@O^I`jVW\sonI3.,36KBLZE*AL[y9lL[PyFD*r_S:dIL9c[8Y>V42R0"!"yb_zN,f#%.[PYYNq; m"_0v; ~rUM2Yy!zmkh)3&U|u!=T(zyv,MHJv"nDH>OJ`t(@mil461d_B'Uo|'nMwlKe0Mv=kvV?Nh@>Hb<3s_z2jYgZhPb@?Wi^x1a~Hplz1.zH Subject: Re: amd64/119047: Not correct working RealTek 8168/8111B PCIe Gigabit Ethernet X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Dec 2007 15:22:15 -0000 Hmm, this sounds kind of like the problem I have with my Asus M2A-VM HDMI motherboard. Also running FreeBSD / amd64 (currently 7.0-beta4). More details below. On Thu, 27 Dec 2007 12:16:00 +0200 (EET) Mario Pavlov wrote: > Hi, > I'm experiencing exactly the same problem > after reboot everything is OK but after some time all network > transfers are getting worse and worse. The packet loss goes above 50% Can you see errors with 'netstat -i'? In my case, neither 'netstat -i' nor 'netstat -m' reports any signs of trouble. My problem is that ssh connections _to_ the machine closes unexpectedly with "bad packet length" or somesuch. Any ssh connections _from_ the machine seems to be unaffected. > you can easily reproduce this, without waiting days, with the > fallowing steps: I must try this. > I've tried this with windows and it appears to be working > there...haven't tried it with linux I've tried different kernel > configuration but the result is still the same I've tried to listen > with tcpdump but it seemed normal except for the packet loss (I can > see all requests but not all responses are returned) > > my motherboard is Asus P5B with chipset Intel P965 and integrated > RealTek 8168/8111B PCIe Gigabit Ethernet What does 'pciconf -lv | grep -B 4 network' show? On my Asus M2A-VM HDMI motherboard I get this: tingo@kg-vm$ pciconf -lv | grep -B 4 network subclass = VGA re0@pci0:2:0:0: class=0x020000 card=0x81aa1043 chip=0x816810ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network Hmm, ethernet is probably better: tingo@kg-vm$ pciconf -lv | grep -B 4 ethernet re0@pci0:2:0:0: class=0x020000 card=0x81aa1043 chip=0x816810ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network subclass = ethernet The machine is running 7.0-beta4: tingo@kg-vm$ uname -a FreeBSD kg-vm.kg4.no 7.0-BETA4 FreeBSD 7.0-BETA4 #0: Sun Dec 2 16:34:41 UTC 2007 root@myers.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 -- Torfinn From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 27 16:04:34 2007 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 775FC16A474 for ; Thu, 27 Dec 2007 16:04:34 +0000 (UTC) (envelope-from jimmyblim@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.236]) by mx1.freebsd.org (Postfix) with ESMTP id 387EA13C44B for ; Thu, 27 Dec 2007 16:04:34 +0000 (UTC) (envelope-from jimmyblim@gmail.com) Received: by wx-out-0506.google.com with SMTP id i29so858093wxd.7 for ; Thu, 27 Dec 2007 08:04:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=UHl09OuxxN1vgxXehYZsGHbagHaxWfMepaRMDUjDknk=; b=P902ig6HfDZqmGzUBrOJGGSgRDH14aKTMQqcE4qhth75+vRhsE0ejOmZNh8HfMdDadUUxnCkJo6y8tH6zqQizJaZLmhUQCZhQPAg5KxrEjjv1PyliHi11BSqA1lt6/+VrQLtu4JMtiYQuYNnat0GpuWeyfn5S1eR3UP+8j8u4qY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=p+w83S59EfQWuNnof+7NbX+XyqnI2W0uViUs/6cCnteRJsn2QJOEgB32FQ2AANIPyvSN78x4YWLhL0jeKLi/+ANlBp4a4zSgzJZH4M90GiwZ/9n9F1vHRaCY4SPO43WSOt0tiIwpytyA9Mxe3iPNhvSptCkmeoM1wdoRDc0htqU= Received: by 10.150.49.15 with SMTP id w15mr2203135ybw.32.1198769948527; Thu, 27 Dec 2007 07:39:08 -0800 (PST) Received: by 10.150.202.16 with HTTP; Thu, 27 Dec 2007 07:39:08 -0800 (PST) Message-ID: <127fb190712270739s77ac68b5n2b76081698f17783@mail.gmail.com> Date: Thu, 27 Dec 2007 23:39:08 +0800 From: "Jimmy Lim" To: freebsd-amd64@freebsd.org In-Reply-To: <152504599.32107.1198356297575.JavaMail.nobody@mail51.abv.bg> MIME-Version: 1.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: base64 Content-Disposition: inline References: <152504599.32107.1198356297575.JavaMail.nobody@mail51.abv.bg> Subject: Re: 64bit nVidia video driver X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Dec 2007 16:04:34 -0000 SGksCgpJIGp1c3QgYm91Z2h0IGFuIEFjZXIgQXNwaXJlIDQ1MjAgQU1ENjQvVHVyaW9uIGFuZCBJ IGhhdmUgblZpZGlhCnZpZGVvLCBJIHRyaWVkIHVzaW5nIHRoZSBkZWZhdWx0IGZyb20geG9yZyBu diBkcml2ZXIgYnV0IG5vIGx1Y2sgdG8KbWFrZSBpdCB3b3JraW5nLCBhbmQgaWYgSSB0cmllZCB0 byBpbnN0YWxsCi91c3IvcG9ydHMveDExL252aWRpYS1kcml2ZXIsIGl0IGNvbXBsYWlucyB0aGF0 IHRoaXMgb25seSBhcHBsaWVzIHRvCmkzODYgZW52aXJvbm1lbnQuCgpBbnkgbHVjayB0byBtYWtl IEdlRm9yY2UtNzAwME0gd29ya2luZyB1bmRlciBGcmVlQlNELTcuMC1QUkVSRUxFQVNFL0FNRDY0 PwoKVGhhbmtzIGluIGFkdmFuY2UuCgotLUppbW15CgpPbiBEZWMgMjMsIDIwMDcgNDo0NCBBTSwg TWFyaW8gUGF2bG92IDxmcmVlYnNkQGFidi5iZz4gd3JvdGU6Cj4gSGVsbG8gbGlzdCwKPiBJJ20g b25lIG9mIHRoZSBzbyBtYW55IG90aGVycyB0aGF0IHdvdWxkIHJlYWxseSBsaWtlIDY0Yml0IG5W aWRpYSBkcml2ZXIKPiBJIGtub3cgdGhhdCB0aGUgZ3V5cyBmcm9tIG5WaWRpYSByZXF1aXJlIHNv bWUgZnVuY3Rpb25hbGl0eSBmcm9tIHRoZSBGcmVlQlNEIGtlcm5lbCBpbiBvcmRlciB0byBiZSBh YmxlIHRvIHdyaXRlIHRoZSBkcml2ZXIuIEhlcmUgaXMgYSBsaXN0IGh0dHA6Ly93aWtpLmZyZWVi c2Qub3JnL052aWRpYUZlYXR1cmVSZXF1ZXN0cwo+IEkganVzdCB3YW50ZWQgdG8gYXNrLCBkb2Vz IGFueW9uZSBoYXZlIHRpbWUgdG8gd29yayBvbiB0aGF0PyBPciBpcyBpdCBwbGFubmVkIGZvciB0 aGVzZSBmZWF0dXJlcyB0byBiZSBmaW5pc2hlZCBpbiB0aGUgbmVhciBmdXR1cmU/Cj4KPiBSZWdh cmRzCj4gTUdQCj4KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLQo+IOvPzcXO1MnSwcogySDHzMHT1dfByiDawSDOwcotzNXE ydEgxsXOIM7BIFJpaGFubmEhIHZpdmFyaWhhbm5hLnpvb20uYmcKPiBfX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+IGZyZWVic2QtYW1kNjRAZnJlZWJzZC5v cmcgbWFpbGluZyBsaXN0Cj4gaHR0cDovL2xpc3RzLmZyZWVic2Qub3JnL21haWxtYW4vbGlzdGlu Zm8vZnJlZWJzZC1hbWQ2NAo+IFRvIHVuc3Vic2NyaWJlLCBzZW5kIGFueSBtYWlsIHRvICJmcmVl YnNkLWFtZDY0LXVuc3Vic2NyaWJlQGZyZWVic2Qub3JnIgo+Cg== From owner-freebsd-amd64@FreeBSD.ORG Thu Dec 27 17:06:51 2007 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B045316A417 for ; Thu, 27 Dec 2007 17:06:51 +0000 (UTC) (envelope-from freebsd@abv.bg) Received: from smtp-out.abv.bg (smtp-out.abv.bg [194.153.145.70]) by mx1.freebsd.org (Postfix) with ESMTP id 4056613C4D3 for ; Thu, 27 Dec 2007 17:06:51 +0000 (UTC) (envelope-from freebsd@abv.bg) Received: from mail52.abv.bg (mail52.ni.bg [192.168.151.19]) by smtp-out.abv.bg (Postfix) with ESMTP id F2F2114AEB8 for ; Thu, 27 Dec 2007 19:06:38 +0200 (EET) DomainKey-Signature: a=rsa-sha1; s=smtp-out; d=abv.bg; c=simple; q=dns; b=kdpy+N2RTU5BYnGHYBRjDAgrjL8bMhHlxRw+jFTr6ayuBdV0Haa+5jMpzAfleJpBM 4HIP2zBJ/0IGTKj48aSPK2RMXwJv9Aiur2hWlknTEAwP5qCbB2mNChBe7Z6II8gaMD0 TYOKvc8iZbxbJhirBvRoBv+yaRFPfr+qUvd5kMA= DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=abv.bg; s=smtp-out; t=1198775198; bh=kQqelVs6xEBnhUAIWIBpSXPLjy8=; h=Received:Date:From: To:Message-ID:Subject:DomainKey; b=XDx6/kz29k5vnPoduvcNpNZzBq9DTVa vX5+86AOk2R0e2ovVQ9A3Lw1c3nfeIrp5wCD2+X3jLGqf3tOLD4c53A2tH3H5Lo1Pcy 3LOXA/y//kEKgkdorSI+oKKc4ZogOiWuhYF1gGfBg2mJ5NXpQb/OPvzx3tebIR5Pxp7 518TTo= Received: from mail52.abv.bg (localhost.localdomain [127.0.0.1]) by mail52.abv.bg (Postfix) with ESMTP id ABFBB8AECE for ; Thu, 27 Dec 2007 19:06:47 +0200 (EET) Date: Thu, 27 Dec 2007 19:06:47 +0200 (EET) From: Mario Pavlov To: freebsd-amd64@freebsd.org Message-ID: <424352075.119591.1198775207700.JavaMail.nobody@mail52.abv.bg> Subject: Re: Re: amd64/119047: Not correct working RealTek 8168/8111B PCIe X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Dec 2007 17:06:51 -0000 Gigabit Ethernet MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: 8bit X-Priority: 3 X-Mailer: AbvMail 1.0 X-Originating-IP: 78.128.21.208 >Hmm, this sounds kind of like the problem I have with my Asus M2A-VM HDMI motherboard. Also running FreeBSD / amd64 (currently 7.0-beta4). >More details below. > >On Thu, 27 Dec 2007 12:16:00 +0200 (EET) >Mario Pavlov wrote: > >> Hi, >> I'm experiencing exactly the same problem >> after reboot everything is OK but after some time all network >> transfers are getting worse and worse. The packet loss goes above 50% > >Can you see errors with 'netstat -i'? In my case, neither 'netstat -i' nor 'netstat -m' reports any signs of trouble. > >My problem is that ssh connections _to_ the machine closes unexpectedly with "bad packet length" or somesuch. >Any ssh connections _from_ the machine seems to be unaffected. > >> you can easily reproduce this, without waiting days, with the >> fallowing steps: > >I must try this. > >> I've tried this with windows and it appears to be working >> there...haven't tried it with linux I've tried different kernel >> configuration but the result is still the same I've tried to listen >> with tcpdump but it seemed normal except for the packet loss (I can >> see all requests but not all responses are returned) >> >> my motherboard is Asus P5B with chipset Intel P965 and integrated >> RealTek 8168/8111B PCIe Gigabit Ethernet > >What does 'pciconf -lv | grep -B 4 network' show? >On my Asus M2A-VM HDMI motherboard I get this: >tingo@kg-vm$ pciconf -lv | grep -B 4 network > subclass = VGA >re0@pci0:2:0:0: class=0x020000 card=0x81aa1043 chip=0x816810ec rev=0x01 hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > class = network > >Hmm, ethernet is probably better: >tingo@kg-vm$ pciconf -lv | grep -B 4 ethernet >re0@pci0:2:0:0: class=0x020000 card=0x81aa1043 chip=0x816810ec rev=0x01 hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > class = network > subclass = ethernet > >The machine is running 7.0-beta4: >tingo@kg-vm$ uname -a >FreeBSD kg-vm.kg4.no 7.0-BETA4 FreeBSD 7.0-BETA4 #0: Sun Dec 2 16:34:41 UTC 2007 root@myers.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > > >-- >Torfinn here is the output from these commands: # netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll re0 1500 00:1d:60:2a:4f:56 3398658 0 6617403 0 0 re0 1500 192.168.20.0 192.168.20.1 3372490 - 6617341 - - dc0 1500 00:08:a1:27:88:1c 461424 0 267683 0 0 dc0 1500 my.public.ip e-soul 284738 - 267109 - - rl0 1500 00:19:e0:0e:a7:fa 30436 0 46058 0 0 rl0 1500 192.168.10.0 192.168.10.1 51 - 0 - - lo0 16384 840 0 840 0 0 lo0 16384 your-net localhost 840 - 840 - - # netstat -m 259/701/960 mbufs in use (current/cache/total) 256/550/806/65536 mbuf clusters in use (current/cache/total/max) 256/289 mbuf+clusters out of packet secondary zone in use (current/cache) 0/374/374/12800 4k (page size) jumbo clusters in use (current/cache/total/max) 0/0/0/6400 9k jumbo clusters in use (current/cache/total/max) 0/0/0/3200 16k jumbo clusters in use (current/cache/total/max) 576K/2771K/3348K bytes allocated to network (current/cache/total) 0/0/0 requests for mbufs denied (mbufs/clusters/mbuf+clusters) 0/0/0 requests for jumbo clusters denied (4k/9k/16k) 0/0/0 sfbufs in use (current/peak/max) 0 requests for sfbufs denied 0 requests for sfbufs delayed 49051 requests for I/O initiated by sendfile 0 calls to protocol drain routines # pciconf -lv | grep -B 4 network subclass = VGA re0@pci0:3:0:0: class=0x020000 card=0x81aa1043 chip=0x816810ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network -- subclass = ATA dc0@pci0:5:1:0: class=0x020000 card=0x50323030 chip=0x91021282 rev=0x40 hdr=0x00 vendor = 'Davicom Semiconductor Inc.' device = 'DM9102/A/AF 10/100 Mbps Fast Ethernet Controller' class = network subclass = ethernet rl0@pci0:5:2:0: class=0x020000 card=0x813910ec chip=0x813910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RT8139 (A/B/C/810x/813x/C+) Fast Ethernet Adapter' class = network # pciconf -lv | grep -B 4 ethernet re0@pci0:3:0:0: class=0x020000 card=0x81aa1043 chip=0x816810ec rev=0x01 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' class = network subclass = ethernet -- dc0@pci0:5:1:0: class=0x020000 card=0x50323030 chip=0x91021282 rev=0x40 hdr=0x00 vendor = 'Davicom Semiconductor Inc.' device = 'DM9102/A/AF 10/100 Mbps Fast Ethernet Controller' class = network subclass = ethernet rl0@pci0:5:2:0: class=0x020000 card=0x813910ec chip=0x813910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RT8139 (A/B/C/810x/813x/C+) Fast Ethernet Adapter' class = network subclass = ethernet # uname -a FreeBSD e-soul.org 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #1: Thu Dec 27 13:05:12 EET 2007 noDrugs@e-soul.org:/usr/obj/usr/src/sys/Ss amd64 ----------------------------------------------------------------- Коментирай и гласувай за най-лудия фен на Rihanna! vivarihanna.zoom.bg From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 28 00:46:38 2007 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD28416A418 for ; Fri, 28 Dec 2007 00:46:38 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9C8B513C447 for ; Fri, 28 Dec 2007 00:46:38 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so5413972waf.3 for ; Thu, 27 Dec 2007 16:46:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=XpzDKX7fklbWi4KKT0AuAjjJzr1275AzYdt+4EE+gD0=; b=sPDv4qPGOInXP/nxt7khN9nVTaxcOgrEYEqkZSCraK+cEAtLOu/g/2Og0/qJLrEkzdw88axnPjXpN1g31Lt6wPVFkmRJDcM8Yf5rTzv7yjWxwb7a8LMCcMwSsbwg4aVjOr7ylD14oYjv/1ax+8NjP0AWzMc4GY0NusKMgZW46kg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=cL8KaHvF2Nr0pmkVpv30nwkWgXhMimfnqyvdySrH/yL9QHNbs/KO/a1lyWuW0+OfWjBX3UHpeW3PWEm1XE8D0iw217h21jSpeO5g3tODMWAwkwOy3O63a8yrnvwAq9n+heMmQYCy6w5KGpJ9LfntwJAw3zZ0ryi9iI3QOdAPP74= Received: by 10.114.14.1 with SMTP id 1mr7189384wan.9.1198801254281; Thu, 27 Dec 2007 16:20:54 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id k23sm4376449waf.15.2007.12.27.16.20.51 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 27 Dec 2007 16:20:52 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id lBS0K3tI009100 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Dec 2007 09:20:03 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id lBS0K12u009099; Fri, 28 Dec 2007 09:20:01 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 28 Dec 2007 09:20:01 +0900 From: Pyun YongHyeon To: Torfinn Ingolfsen Message-ID: <20071228002001.GA8872@cdnetworks.co.kr> References: <1825008839.105809.1198750560154.JavaMail.nobody@mail54.abv.bg> <20071227162155.9a9bd2f1.torfinn.ingolfsen@broadpark.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071227162155.9a9bd2f1.torfinn.ingolfsen@broadpark.no> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: amd64/119047: Not correct working RealTek 8168/8111B PCIe Gigabit Ethernet X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Dec 2007 00:46:38 -0000 On Thu, Dec 27, 2007 at 04:21:55PM +0100, Torfinn Ingolfsen wrote: > Hmm, this sounds kind of like the problem I have with my Asus M2A-VM HDMI motherboard. Also running FreeBSD / amd64 (currently 7.0-beta4). > More details below. For users who are suffering from re(4) instability issues please try the following patch. The patch shall fix bus_dma(9) issues and will enable TSO capability as well as 64bit dma support. http://people.freebsd.org/~yongari/re/re.HEAD.patch or http://people.freebsd.org/~yongari/re/if_re.c http://people.freebsd.org/~yongari/re/if_rlreg.h Please report back the result as I have plan to commit the patch after 7.0 goes out. > > On Thu, 27 Dec 2007 12:16:00 +0200 (EET) > Mario Pavlov wrote: > > > Hi, > > I'm experiencing exactly the same problem > > after reboot everything is OK but after some time all network > > transfers are getting worse and worse. The packet loss goes above 50% > > Can you see errors with 'netstat -i'? In my case, neither 'netstat -i' nor 'netstat -m' reports any signs of trouble. > > My problem is that ssh connections _to_ the machine closes unexpectedly with "bad packet length" or somesuch. > Any ssh connections _from_ the machine seems to be unaffected. > > > you can easily reproduce this, without waiting days, with the > > fallowing steps: > > I must try this. > > > I've tried this with windows and it appears to be working > > there...haven't tried it with linux I've tried different kernel > > configuration but the result is still the same I've tried to listen > > with tcpdump but it seemed normal except for the packet loss (I can > > see all requests but not all responses are returned) > > > > my motherboard is Asus P5B with chipset Intel P965 and integrated > > RealTek 8168/8111B PCIe Gigabit Ethernet > > What does 'pciconf -lv | grep -B 4 network' show? > On my Asus M2A-VM HDMI motherboard I get this: > tingo@kg-vm$ pciconf -lv | grep -B 4 network > subclass = VGA > re0@pci0:2:0:0: class=0x020000 card=0x81aa1043 chip=0x816810ec rev=0x01 hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > class = network > > Hmm, ethernet is probably better: > tingo@kg-vm$ pciconf -lv | grep -B 4 ethernet > re0@pci0:2:0:0: class=0x020000 card=0x81aa1043 chip=0x816810ec rev=0x01 hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > class = network > subclass = ethernet > > The machine is running 7.0-beta4: > tingo@kg-vm$ uname -a > FreeBSD kg-vm.kg4.no 7.0-BETA4 FreeBSD 7.0-BETA4 #0: Sun Dec 2 16:34:41 UTC 2007 root@myers.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > > > -- > Torfinn -- Regards, Pyun YongHyeon From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 28 19:43:21 2007 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5149B16A419 for ; Fri, 28 Dec 2007 19:43:21 +0000 (UTC) (envelope-from freebsd@abv.bg) Received: from smtp-out.abv.bg (smtp-out.abv.bg [194.153.145.70]) by mx1.freebsd.org (Postfix) with ESMTP id B8C2413C4EC for ; Fri, 28 Dec 2007 19:43:20 +0000 (UTC) (envelope-from freebsd@abv.bg) Received: from mail51.abv.bg (mail51.ni.bg [192.168.151.12]) by smtp-out.abv.bg (Postfix) with ESMTP id 1090E14ADF6 for ; Fri, 28 Dec 2007 21:43:08 +0200 (EET) DomainKey-Signature: a=rsa-sha1; s=smtp-out; d=abv.bg; c=simple; q=dns; b=j2vdBtrlhmbByf65S14Q5ImieMHF+lgfqdBNvFeO3i8Dyc3lhuIjsG7vMqYTODwXh 5M7WuKy+78Z4+5YndUvFHDKGrAk4NUHWfvbQ3PMkilzop7Qfa9YZ+pHy2/mQAP+wp6U vzgBzkc7HmX3kfZjRn1LIMbJNMGuPMcjL9laiLQ= DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=abv.bg; s=smtp-out; t=1198870988; bh=qpmo1H/DZIvuqBNXwpgRBwFvUPA=; h=Received:Date:From: To:Message-ID:Subject:DomainKey; b=uNj9Uq/Y1NDO2dDH/J42hNc3YZdFslT 6HJzRdn1X12nazMudB25FKwcW1nz7jqbftFTAFzLUi4kHDMvDMH7gWiTDOa//Y/aoJo mBcF+SA8muCxJ6h6liYJU6IFO2V5IDffqzyugtFobm6MxX5xkL2dD1GufEmxlF5d6PN WpO39U= Received: from mail51.abv.bg (localhost.localdomain [127.0.0.1]) by mail51.abv.bg (Postfix) with ESMTP id 694C41BD651 for ; Fri, 28 Dec 2007 21:43:13 +0200 (EET) Date: Fri, 28 Dec 2007 21:43:13 +0200 (EET) From: Mario Pavlov To: freebsd-amd64@freebsd.org Message-ID: <308089437.146523.1198870993429.JavaMail.nobody@mail51.abv.bg> Subject: Re: Re: amd64/119047: Not correct working RealTek 8168/8111B PCIe X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Dec 2007 19:43:21 -0000 Gigabit Ethernet MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: 8bit X-Priority: 3 X-Mailer: AbvMail 1.0 X-Originating-IP: 78.128.21.208 >On Thu, Dec 27, 2007 at 04:21:55PM +0100, Torfinn Ingolfsen wrote: > > Hmm, this sounds kind of like the problem I have with my Asus M2A-VM HDMI motherboard. Also running FreeBSD / amd64 (currently 7.0-beta4). > > More details below. > >For users who are suffering from re(4) instability issues please try >the following patch. The patch shall fix bus_dma(9) issues and will >enable TSO capability as well as 64bit dma support. > >http://people.freebsd.org/~yongari/re/re.HEAD.patch >or >http://people.freebsd.org/~yongari/re/if_re.c >http://people.freebsd.org/~yongari/re/if_rlreg.h > >Please report back the result as I have plan to commit the patch >after 7.0 goes out. > > > > > On Thu, 27 Dec 2007 12:16:00 +0200 (EET) > > Mario Pavlov wrote: > > > > > Hi, > > > I'm experiencing exactly the same problem > > > after reboot everything is OK but after some time all network > > > transfers are getting worse and worse. The packet loss goes above 50% > > > > Can you see errors with 'netstat -i'? In my case, neither 'netstat -i' nor 'netstat -m' reports any signs of trouble. > > > > My problem is that ssh connections _to_ the machine closes unexpectedly with "bad packet length" or somesuch. > > Any ssh connections _from_ the machine seems to be unaffected. > > > > > you can easily reproduce this, without waiting days, with the > > > fallowing steps: > > > > I must try this. > > > > > I've tried this with windows and it appears to be working > > > there...haven't tried it with linux I've tried different kernel > > > configuration but the result is still the same I've tried to listen > > > with tcpdump but it seemed normal except for the packet loss (I can > > > see all requests but not all responses are returned) > > > > > > my motherboard is Asus P5B with chipset Intel P965 and integrated > > > RealTek 8168/8111B PCIe Gigabit Ethernet > > > > What does 'pciconf -lv | grep -B 4 network' show? > > On my Asus M2A-VM HDMI motherboard I get this: > > tingo@kg-vm$ pciconf -lv | grep -B 4 network > > subclass = VGA > > re0@pci0:2:0:0: class=0x020000 card=0x81aa1043 chip=0x816810ec rev=0x01 hdr=0x00 > > vendor = 'Realtek Semiconductor' > > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > > class = network > > > > Hmm, ethernet is probably better: > > tingo@kg-vm$ pciconf -lv | grep -B 4 ethernet > > re0@pci0:2:0:0: class=0x020000 card=0x81aa1043 chip=0x816810ec rev=0x01 hdr=0x00 > > vendor = 'Realtek Semiconductor' > > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > > class = network > > subclass = ethernet > > > > The machine is running 7.0-beta4: > > tingo@kg-vm$ uname -a > > FreeBSD kg-vm.kg4.no 7.0-BETA4 FreeBSD 7.0-BETA4 #0: Sun Dec 2 16:34:41 UTC 2007 root@myers.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > > > > > > -- > > Torfinn > >-- >Regards, >Pyun YongHyeon works for me, thanks! :) From owner-freebsd-amd64@FreeBSD.ORG Fri Dec 28 23:05:22 2007 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC71C16A417 for ; Fri, 28 Dec 2007 23:05:22 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.154]) by mx1.freebsd.org (Postfix) with ESMTP id 5C9CE13C45B for ; Fri, 28 Dec 2007 23:05:22 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so2623896fgg.35 for ; Fri, 28 Dec 2007 15:05:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=5ZJaRww7jo7lcxtE2aqSVI+RPfruvOqqhy7oQo8w5Z4=; b=nrgk/+X5ZKaEflKagYPzVKSgDZReg/FG/AEWPDBdisQnmXuwlBpC9vYUJ4MrPvWBJUs+0gLPN9t9wIjufWkBExTkVj7XhP5hvhkx8LfsDtdF6t9jykhz+V76l3REcrv4HmiBd94YopYqLpMsRcdVOOVEJVPb+BpOruO03+eq70w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=E5oU5TxVlUuu5cSwj9WHyecEaNXc67MUWcc2ML1UMNLYL6erg3p/mMHIGmTNx9F+A14A7DFYKFrxHxs4YWCiMs81y/MR3V9l9HNP+4mBEbsAE2WrtlnLgRArZtdldGqp/VLRnhiCgrHFPGPvmbu085cMffAhWoduVzQgbZPfrsw= Received: by 10.86.79.19 with SMTP id c19mr9374953fgb.31.1198881408928; Fri, 28 Dec 2007 14:36:48 -0800 (PST) Received: by 10.86.52.19 with HTTP; Fri, 28 Dec 2007 14:36:48 -0800 (PST) Message-ID: <499c70c0712281436u220bd798l2a3dbe5bbf622156@mail.gmail.com> Date: Sat, 29 Dec 2007 01:36:48 +0300 From: "Abdullah Ibn Hamad Al-Marri" To: "Mario Pavlov" In-Reply-To: <308089437.146523.1198870993429.JavaMail.nobody@mail51.abv.bg> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <308089437.146523.1198870993429.JavaMail.nobody@mail51.abv.bg> Cc: freebsd-amd64@freebsd.org Subject: Re: Re: amd64/119047: Not correct working RealTek 8168/8111B PCIe X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Dec 2007 23:05:22 -0000 Works for me too! Can you put it in RELENG_7 since RELENG_7_0 is there? On Dec 28, 2007 10:43 PM, Mario Pavlov wrote: > Gigabit Ethernet > MIME-Version: 1.0 > Content-Type: text/plain; charset="windows-1251" > Content-Transfer-Encoding: 8bit > X-Priority: 3 > X-Mailer: AbvMail 1.0 > X-Originating-IP: 78.128.21.208 > > >On Thu, Dec 27, 2007 at 04:21:55PM +0100, Torfinn Ingolfsen wrote: > > > Hmm, this sounds kind of like the problem I have with my Asus M2A-VM HDMI motherboard. Also running FreeBSD / amd64 (currently 7.0-beta4). > > > More details below. > > > >For users who are suffering from re(4) instability issues please try > >the following patch. The patch shall fix bus_dma(9) issues and will > >enable TSO capability as well as 64bit dma support. > > > >http://people.freebsd.org/~yongari/re/re.HEAD.patch > >or > >http://people.freebsd.org/~yongari/re/if_re.c > >http://people.freebsd.org/~yongari/re/if_rlreg.h > > > >Please report back the result as I have plan to commit the patch > >after 7.0 goes out. > > > > > > > > On Thu, 27 Dec 2007 12:16:00 +0200 (EET) > > > Mario Pavlov wrote: > > > > > > > Hi, > > > > I'm experiencing exactly the same problem > > > > after reboot everything is OK but after some time all network > > > > transfers are getting worse and worse. The packet loss goes above 50% > > > > > > Can you see errors with 'netstat -i'? In my case, neither 'netstat -i' nor 'netstat -m' reports any signs of trouble. > > > > > > My problem is that ssh connections _to_ the machine closes unexpectedly with "bad packet length" or somesuch. > > > Any ssh connections _from_ the machine seems to be unaffected. > > > > > > > you can easily reproduce this, without waiting days, with the > > > > fallowing steps: > > > > > > I must try this. > > > > > > > I've tried this with windows and it appears to be working > > > > there...haven't tried it with linux I've tried different kernel > > > > configuration but the result is still the same I've tried to listen > > > > with tcpdump but it seemed normal except for the packet loss (I can > > > > see all requests but not all responses are returned) > > > > > > > > my motherboard is Asus P5B with chipset Intel P965 and integrated > > > > RealTek 8168/8111B PCIe Gigabit Ethernet > > > > > > What does 'pciconf -lv | grep -B 4 network' show? > > > On my Asus M2A-VM HDMI motherboard I get this: > > > tingo@kg-vm$ pciconf -lv | grep -B 4 network > > > subclass = VGA > > > re0@pci0:2:0:0: class=0x020000 card=0x81aa1043 chip=0x816810ec rev=0x01 hdr=0x00 > > > vendor = 'Realtek Semiconductor' > > > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > > > class = network > > > > > > Hmm, ethernet is probably better: > > > tingo@kg-vm$ pciconf -lv | grep -B 4 ethernet > > > re0@pci0:2:0:0: class=0x020000 card=0x81aa1043 chip=0x816810ec rev=0x01 hdr=0x00 > > > vendor = 'Realtek Semiconductor' > > > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > > > class = network > > > subclass = ethernet > > > > > > The machine is running 7.0-beta4: > > > tingo@kg-vm$ uname -a > > > FreeBSD kg-vm.kg4.no 7.0-BETA4 FreeBSD 7.0-BETA4 #0: Sun Dec 2 16:34:41 UTC 2007 root@myers.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 > > > > > > > > > -- > > > Torfinn > > > >-- > >Regards, > >Pyun YongHyeon > > works for me, thanks! :) > _______________________________________________ > 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" > -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ From owner-freebsd-amd64@FreeBSD.ORG Sat Dec 29 02:52:09 2007 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0925416A419 for ; Sat, 29 Dec 2007 02:52:09 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by mx1.freebsd.org (Postfix) with ESMTP id D023D13C455 for ; Sat, 29 Dec 2007 02:52:08 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so6225783waf.3 for ; Fri, 28 Dec 2007 18:52:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=KLzS6UmWEEq86EJXtIwKuE5uucegWZVicW8IF7M3c4U=; b=yCfykHB1LLbBncQxC8hR9AMNKX7MMI+ZqLuReRKM73LZFTBUyxkqpioBVL+v1JBcHfwyjRFHUlXoYEzMKaulqGBCecn+HdwsEhH3DW75yWetU3viUVY+yj1GEGqQq1jBczcoQeqyL5kLFKErwFP+g4bj4ZlsxKUMMA3VyrrEMP4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=mcGlCr2xBq/M0T33cbIRGIrddz7lfJ6doohKrhctd0Ss2cvRmFDEC49Vp+TT4TeK9JNE10uPDXSPKNZZkGXjEKuCOD1ZWpfcWruaADOdmCwC6LFsho/r0sRg65XlZlBMPoqq3zo4URkIUidaCiRySQ/D+PJbnZ3de4DDvw2vQyo= Received: by 10.114.15.1 with SMTP id 1mr9737693wao.27.1198896728074; Fri, 28 Dec 2007 18:52:08 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id m40sm11298151waf.16.2007.12.28.18.52.05 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 28 Dec 2007 18:52:06 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id lBT2p02T013437 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 29 Dec 2007 11:51:01 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id lBT2oxs8013436; Sat, 29 Dec 2007 11:50:59 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Sat, 29 Dec 2007 11:50:59 +0900 From: Pyun YongHyeon To: Abdullah Ibn Hamad Al-Marri Message-ID: <20071229025059.GA13309@cdnetworks.co.kr> References: <308089437.146523.1198870993429.JavaMail.nobody@mail51.abv.bg> <499c70c0712281436u220bd798l2a3dbe5bbf622156@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <499c70c0712281436u220bd798l2a3dbe5bbf622156@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-amd64@freebsd.org Subject: Re: Re: amd64/119047: Not correct working RealTek 8168/8111B PCIe X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Dec 2007 02:52:09 -0000 On Sat, Dec 29, 2007 at 01:36:48AM +0300, Abdullah Ibn Hamad Al-Marri wrote: > Works for me too! > Thanks for feedback! > Can you put it in RELENG_7 since RELENG_7_0 is there? > As you noticed from the size of the jumbo patch it changes several operation scheme in the driver. Since re(4) supports lots of model/revisions from RealTek it requires much more exposure and testing under various environments(e.g. testing on sparc64 platforms and > 4GB memory configuration etc). I think updating drivers in HEAD prior to releasing 7.0/6.3 is not good idea as it would make it hard to find/test possible bugs in the release. The patch would be committed to HEAD first after 7.0 goes out. Thanks. -- Regards, Pyun YongHyeon