From owner-freebsd-hardware@FreeBSD.ORG Mon Aug 3 02:44:22 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55DF51065673 for ; Mon, 3 Aug 2009 02:44:22 +0000 (UTC) (envelope-from achilov-rn@askd.ru) Received: from master.askd.ru (master.askd.ru [80.242.75.6]) by mx1.freebsd.org (Postfix) with ESMTP id B8A308FC13 for ; Mon, 3 Aug 2009 02:44:21 +0000 (UTC) (envelope-from achilov-rn@askd.ru) Received: from to-495.askd.gmbh (IDENT:shelton@sentry [192.168.1.94]) by master.askd.ru (8.14.3/8.14.3) with ESMTP id n732iKJu020238 for ; Mon, 3 Aug 2009 09:44:20 +0700 (NOVST) (envelope-from achilov-rn@askd.ru) From: "Rashid N. Achilov" Organization: =?koi8-r?b?7+/v?= "=?koi8-r?b?4fMt88nT1MXNwQ==?= =?koi8-r?b?IOvPzdDMxcvT?=" To: freebsd-hardware@freebsd.org Date: Mon, 3 Aug 2009 09:47:15 +0700 User-Agent: KMail/1.9.7 References: <200907311505.43450.achilov-rn@askd.ru> <200907310855.n6V8tEBU088592@banyan.cs.ait.ac.th> In-Reply-To: <200907310855.n6V8tEBU088592@banyan.cs.ait.ac.th> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200908030947.16780.achilov-rn@askd.ru> Subject: Re: Intel 024B server deadlock X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Achilov, Rashid" List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Aug 2009 02:44:22 -0000 On Friday 31 July 2009, Olivier Nicole wrote: > Hi, > > > Intel server (configuration below) with 4 SCSI and one IDE > > drives. When I try to READ big archive file (i.e. 150-180 Mb) > > idependently, through tar -xf filename.tar or reading through Samba, > > from IDE drive (ad0) box throws a message > > > > Jul 30 16:11:38 svr-63 kernel: ad0: TIMEOUT - READ_DMA retrying (1 > > retry left) LBA=151318527 > > Just a wild guess, but what about trying to change your BIOS settings > for the IDE disk, like disable DMA? Or a firware upgrade of that > ServerWorks ROSB4 UDMA33 controller? Probably, I'll try to do this. But I'm confused that - it isn't new server, on the contrary, about 3-4 years it was our Windows Domain Controller and works fine. -- With Best Regards. Rashid N. Achilov (RNA1-RIPE), JID: citycat4@jabber.org OOO "ACK" telecommunications administrator, e-mail: achilov-rn [at] askd.ru PGP: 83 CD E2 A7 37 4A D5 81 D6 D6 52 BF C9 2F 85 AF 97 BE CB 0A From owner-freebsd-hardware@FreeBSD.ORG Mon Aug 3 14:20:49 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D79DD10656C7 for ; Mon, 3 Aug 2009 14:20:49 +0000 (UTC) (envelope-from whizzter@gmail.com) Received: from mail-fx0-f210.google.com (mail-fx0-f210.google.com [209.85.220.210]) by mx1.freebsd.org (Postfix) with ESMTP id E34D78FC3B for ; Mon, 3 Aug 2009 14:20:03 +0000 (UTC) (envelope-from whizzter@gmail.com) Received: by fxm6 with SMTP id 6so1351957fxm.43 for ; Mon, 03 Aug 2009 07:19:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=WuLUjR2M5mMjtvmIoeVYp+fdHYk9tbQfeFV5UhC3e6c=; b=fjcYiSt8oPCiVh/iql4Vb09eUf6rYaDRx35TnilxKZSooz1OK6XjBL0AyfWOtCEXJz AFR7v4KjMnmkcEuINRimrMJuvh4Uz3Y8U0V0+2pc/wlyZqjZk0ObnCIK/UG98Wzmsd11 fiwhrp2eC8ihzbV+lmwzyNkKwA+xaJG1Nv+ec= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=P6aAiKU6DiNLdeomgIUAXgTvTCWRqNB/TEK2X6uLTHyjD8Pz4+vgq7wj7H5mSDoSM3 2mGzfmhcZRLaIdlMkeb7afsVBzmgviJvdiVy9sMyxgsLZtI1tdUArwXa02cjtsEC9P03 rdqe2nUvvXXGAVytPLAI7TH3Ckbs1p5fwJAEE= MIME-Version: 1.0 Received: by 10.103.224.8 with SMTP id b8mr3525954mur.118.1249307502753; Mon, 03 Aug 2009 06:51:42 -0700 (PDT) In-Reply-To: <200908030947.16780.achilov-rn@askd.ru> References: <200907311505.43450.achilov-rn@askd.ru> <200907310855.n6V8tEBU088592@banyan.cs.ait.ac.th> <200908030947.16780.achilov-rn@askd.ru> Date: Mon, 3 Aug 2009 15:51:42 +0200 Message-ID: <436c7eda0908030651j37263783h2a4157da49230011@mail.gmail.com> From: Jonas Lund To: "Achilov, Rashid" Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Cc: freebsd-hardware@freebsd.org Subject: Re: Intel 024B server deadlock X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Aug 2009 14:20:53 -0000 Tried checking smart stats on the disk? these timeout messages are quite common to happen when a disk is nearing death (Ignored it myself once.. stupid move) 2009/8/3 Rashid N. Achilov : > On Friday 31 July 2009, Olivier Nicole wrote: >> Hi, >> >> > Intel server (configuration below) with 4 SCSI and one IDE >> > drives. When I try to READ big archive file (i.e. 150-180 Mb) >> > idependently, through tar -xf filename.tar or reading through Samba, >> > from IDE drive (ad0) box throws a message >> > >> > Jul 30 16:11:38 svr-63 kernel: ad0: TIMEOUT - READ_DMA retrying (1 >> > retry left) LBA=3D151318527 >> >> Just a wild guess, but what about trying to change your BIOS settings >> for the IDE disk, like disable DMA? Or a firware upgrade of that >> ServerWorks ROSB4 UDMA33 controller? > > Probably, I'll try to do this. But I'm confused that - it isn't new serve= r, on > the contrary, about 3-4 years it was our Windows Domain Controller and wo= rks > fine. > -- > =9A With Best Regards. > =9A Rashid N. Achilov (RNA1-RIPE), JID: citycat4@jabber.org > =9A OOO "ACK" telecommunications administrator, e-mail: achilov-rn [at] a= skd.ru > =9A PGP: 83 CD E2 A7 37 4A D5 81 D6 D6 52 BF C9 2F 85 AF 97 BE CB 0A > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.or= g" > From owner-freebsd-hardware@FreeBSD.ORG Tue Aug 4 23:29:37 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B983F1065670 for ; Tue, 4 Aug 2009 23:29:37 +0000 (UTC) (envelope-from frank@undermydesk.org) Received: from amazone.undermydesk.org (amazone.undermydesk.org [213.211.198.100]) by mx1.freebsd.org (Postfix) with ESMTP id 31BA58FC1D for ; Tue, 4 Aug 2009 23:29:36 +0000 (UTC) (envelope-from frank@undermydesk.org) Received: from localhost (localhost [127.0.0.1]) by amazone.undermydesk.org (Postfix) with ESMTP id AF522A85D for ; Wed, 5 Aug 2009 01:13:44 +0200 (CEST) Received: from amazone.undermydesk.org ([213.211.198.100]) by localhost (amazone.undermydesk.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VAvHcr4NJ+zQ for ; Wed, 5 Aug 2009 01:13:36 +0200 (CEST) Received: from [192.168.0.74] (p4FD5CF79.dip.t-dialin.net [79.213.207.121]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by amazone.undermydesk.org (Postfix) with ESMTPSA id B9B7FA85B for ; Wed, 5 Aug 2009 01:13:35 +0200 (CEST) Message-ID: <4A78C0B5.8080808@undermydesk.org> Date: Wed, 05 Aug 2009 01:13:57 +0200 From: Frank Reppin User-Agent: Thunderbird 2.0.0.22 (Windows/20090605) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [if_re.c] INTEL mini/itx DE945GSEJT X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Aug 2009 23:29:38 -0000 Hi all, just purchased the above mentioned board: http://www.intel.com/products/desktop/motherboards/D945GSEJT/D945GSEJT-overview.htm and this board claims to come with a so called: Realtek 8111D network (10/100/1000m) chipset onboard. Digging in -current and google.com/ncr revealed that this certain board/nic seems to be not supported by the -CURRENT- if_re.c provided by FreeBSD. Some further investigations reveals that OpenBSD claims to support this (most prolly) precious chipset (8111D) within their 4.5 release: http://www.openbsd.org/45.html (searching for 8111D will point you to re(4)) My question(s) is(are): a) does anyone run this board without flaws on fbsd-current with its intergrated 8111D NIC ( my 'failover' option is to run this board using xl thanks to it's pci slot) b) if a) doesn't apply - how did you get it working on current/stable without another driver c) OpenBSD mentions this one ( 8111D support ) in their release notes for a _stable_ version ( 4.5 )- but I cannot even see support for this specific device in FreeBSD trunk/head d) realtek itself does provide drivers for even FreeBSD (sources)... ... are there any experiences using those drivers To make a long story short/and to be honest... ... I'd like to see native support in at least -current. TIA, frank reppin -- http://www.undermydesk.org From owner-freebsd-hardware@FreeBSD.ORG Wed Aug 5 15:20:16 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 78B34106566C for ; Wed, 5 Aug 2009 15:20:16 +0000 (UTC) (envelope-from whizzter@gmail.com) Received: from mail-fx0-f224.google.com (mail-fx0-f224.google.com [209.85.220.224]) by mx1.freebsd.org (Postfix) with ESMTP id F36938FC1D for ; Wed, 5 Aug 2009 15:20:15 +0000 (UTC) (envelope-from whizzter@gmail.com) Received: by fxm24 with SMTP id 24so167297fxm.36 for ; Wed, 05 Aug 2009 08:20:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=rb+oeIRhG1DJ/e7i2V9xH4Rjn38PvMRTsR6mDMSUnXo=; b=dvh+v7xH0IMQND8gOnpObG2AFTTSW/ljoTGwJe1KQc4TjntAqUwxzRG+f7K6dt3pjw 1pdEWd+fFjh4ra75gSn69Xutou4CDMP1YVy4OgGic1lcn8IWiFticukC3vZL2osRU9hD QfiLS4XE5EnC/mI7uyqQzMMSXukXIoLuH7FoE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=P9SdNhBcP9L0SLAkSG8bwFreV7MvJkJj6GyYJtpuqOrBb4hO71ZYwzmhwZXTrPPvtF slYCQBCG4hY56CgfkH4GDSvF3DWIKl2RBNUJp/1rsbgFoMiMZB2MANPpJwBUMzOU/9SO hLTLPTFNetTeywxGpquFT5B2r3yuIL4HMO/Vo= MIME-Version: 1.0 Received: by 10.223.121.205 with SMTP id i13mr2205642far.41.1249485613455; Wed, 05 Aug 2009 08:20:13 -0700 (PDT) In-Reply-To: <4A78C0B5.8080808@undermydesk.org> References: <4A78C0B5.8080808@undermydesk.org> Date: Wed, 5 Aug 2009 17:20:13 +0200 Message-ID: <436c7eda0908050820g5a610a9dk6b1b1cf20afe2be8@mail.gmail.com> From: Jonas Lund To: Frank Reppin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hardware@freebsd.org Subject: Re: [if_re.c] INTEL mini/itx DE945GSEJT X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Aug 2009 15:20:16 -0000 If you've just purchased a new board i think you could try it out as you install it. Apart from the mentioned things boards usually contains the same chipsets as other boards so chances are it'll work. And if not directly then under some compat mode (Altho could be with reduced speed) And if realtek does provide source for their drivers i'd prolly not be too worried. The shitties drivers i've used was some crap produced by some random chineese chip-shop that had delay(10000) or something alike it inside kernel-code (That's right.. it waited 10 seconds in kernel for no apperant reason!) but the code was functional with this removed. 2009/8/5 Frank Reppin : > Hi all, > > just purchased the above mentioned board: > > http://www.intel.com/products/desktop/motherboards/D945GSEJT/D945GSEJT-ov= erview.htm > > and this board claims to come with a so called: > > =A0Realtek 8111D > > network (10/100/1000m) chipset onboard. > > Digging in -current and google.com/ncr revealed that this certain board/n= ic > seems to be not supported by the -CURRENT- if_re.c provided > by FreeBSD. Some further investigations reveals that OpenBSD claims to > support this (most prolly) precious chipset (8111D) within their 4.5 > release: > > =A0http://www.openbsd.org/45.html > =A0(searching for 8111D will point you to re(4)) > > My question(s) is(are): > > =A0a) does anyone run this board without flaws on fbsd-current > =A0 =A0 with its intergrated 8111D NIC > =A0 =A0 ( my 'failover' option is to run this board using xl thanks to > =A0 =A0 =A0 it's pci slot) > > =A0b) if a) doesn't apply - how did you get it working on current/stable > =A0 =A0 without another driver > > =A0c) OpenBSD mentions this one ( 8111D support ) in their release notes > =A0 =A0 for a _stable_ version ( 4.5 )- but I cannot even see support for > =A0 =A0 this specific device in FreeBSD trunk/head > > =A0d) realtek itself does provide drivers for even FreeBSD (sources)... > =A0 =A0 ... are there any experiences using those drivers > > To make a long story short/and to be honest... > > ... I'd like to see native support in at least -current. > > TIA, > > frank reppin > > -- > > http://www.undermydesk.org > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.or= g" > From owner-freebsd-hardware@FreeBSD.ORG Sat Aug 8 21:39:57 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A75E1065672; Sat, 8 Aug 2009 21:39:57 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id B1E858FC15; Sat, 8 Aug 2009 21:39:56 +0000 (UTC) Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPSA id 251041323; Sun, 09 Aug 2009 00:39:53 +0300 Message-ID: <4A7DF076.4070203@FreeBSD.org> Date: Sun, 09 Aug 2009 00:39:02 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.21 (X11/20090405) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org, freebsd-arch@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Do we still need ATA disk CHS addressing? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Aug 2009 21:39:57 -0000 While preparing wrapping ATA(4) low-level drivers code into CAM SIM, I would like to remove CHS addressing support to make code cleaner. CHS addressing is officially declared obsoleted and replaced by LBA. Since ATA/ATAPI-6 specification (October 2001) it is even no longer documented. Have anybody seen ATA drive without LBA support in last years? Any other objections against removing it? -- Alexander Motin