From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 02:34:34 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E945816A41B for ; Sun, 28 Oct 2007 02:34:34 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outU.internet-mail-service.net (outU.internet-mail-service.net [216.240.47.244]) by mx1.freebsd.org (Postfix) with ESMTP id C3AEC13C48E for ; Sun, 28 Oct 2007 02:34:34 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Sat, 27 Oct 2007 19:34:33 -0700 X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id 59E86126825; Sat, 27 Oct 2007 19:34:33 -0700 (PDT) Message-ID: <4723F557.9060608@elischer.org> Date: Sat, 27 Oct 2007 19:35:03 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Marcel Moolenaar References: <200710111741.34992.jhb@FreeBSD.org> <200710151216.36509.jhb@freebsd.org> <3E7A944C-6182-41A1-8881-C4B94428B65A@mac.com> <200710151510.35000.jhb@freebsd.org> <20071027174205.GK39759@funkthat.com> <20071027175856.GL39759@funkthat.com> <9F674BF7-58E2-4DC5-A082-F5128316F889@mac.com> <20071027214253.GA12390@owl.midgard.homeip.net> <3117246F-26D0-414B-9CBA-65F460F5EA39@mac.com> <20071027230132.GA12961@owl.midgard.homeip.net> <899CA6AE-C21C-45EE-B95A-787F587616A6@mac.com> In-Reply-To: <899CA6AE-C21C-45EE-B95A-787F587616A6@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: New-bus unit wiring via hints.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 02:34:35 -0000 Marcel Moolenaar wrote: > > On Oct 27, 2007, at 4:01 PM, Erik Trulsson wrote: > >> On Sat, Oct 27, 2007 at 03:09:38PM -0700, Marcel Moolenaar wrote: >>> >>> On Oct 27, 2007, at 2:42 PM, Erik Trulsson wrote: >>> >>>> On Sat, Oct 27, 2007 at 12:09:29PM -0700, Marcel Moolenaar wrote: >>>>> >>>>> On Oct 27, 2007, at 10:58 AM, John-Mark Gurney wrote: >>>>> >>>>>> Yeh, you're solution was to simply declare that anyone who knows that >>>>>> COM1 is at 0x3f8 is wrong, and to use a different, yet again >>>>>> arbitrary >>>>>> solution which is which is listed first in ACPI... >>>>> >>>>> Exactly. Anyone who "knows" that COM1 is at 0x3f8 while >>>>> the computer right in front of them clearly states that >>>>> COM1 is at 0x2f8 is in denial. >>>> >>>> If I say in the BIOS setup screen that the first serial port is >>>> to use 0x3f8, then that is the port which I want sio0 to attach to, >>>> regardless of in which order FreeBSD sees them enumerated. >>> >>> What is the first serial port in the BIOS? >> >> It is the port which is labeled 'Serial Port 1' or something similar. > > I see. Some argue it's the UART at port 0x3f8, because > that's how things have been documented. I like your > definition, but unfortunately this thread is mostly > about how we want sio0 at a fixed port by virtue of > hints. > >>> Is that not the one >>> that's enumerated first? >> >> Not necessarily, no. It should be, but is not always. > > Ok. What's buggy if it's not -- ACPI? > >> BIOSs are fairly often buggy or get things wrong. Being able to override >> the BIOS when it is wrong is a Good Thing. > > I would presume that we can patch the AML if it's an ACPI > problem. That seems to me to be the right thing to do: > you patch what is broken... I'd argue that com0 is the one that windows calls com1 > From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 05:01:11 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB9F016A419; Sun, 28 Oct 2007 05:01:11 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from que02.charter.net (que02.charter.net [209.225.8.190]) by mx1.freebsd.org (Postfix) with ESMTP id 499EC13C4BF; Sun, 28 Oct 2007 05:01:10 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from aarprv02.charter.net ([10.20.200.72]) by mtao02.charter.net (InterMail vM.7.08.03.00 201-2186-126-20070710) with ESMTP id <20071028040334.GDBT27011.mtao02.charter.net@aarprv02.charter.net>; Sun, 28 Oct 2007 00:03:34 -0400 Received: from [192.168.15.101] (really [75.138.219.8]) by aarprv02.charter.net with ESMTP id <20071028040334.HCPZ495.aarprv02.charter.net@[192.168.15.101]>; Sun, 28 Oct 2007 00:03:34 -0400 Message-ID: <47240A15.8080305@charter.net> Date: Sun, 28 Oct 2007 00:03:33 -0400 From: Andrew Lankford User-Agent: Thunderbird 2.0.0.6 (X11/20071017) MIME-Version: 1.0 To: stable@freebsd.org, current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Chzlrs: 0 X-Mailman-Approved-At: Sun, 28 Oct 2007 05:29:54 +0000 Cc: Subject: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 05:01:11 -0000 I just noticed that /usr/share/man/man8/MAKEDEV.8 is still in the FreeBSD-7 tree. Is this intentional? It still says that MAKEDEV is located in /dev and mentions MAKEDEV.local as well. Just wondering. Andrew Lankford From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 05:30:39 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C806916A420 for ; Sun, 28 Oct 2007 05:30:39 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outE.internet-mail-service.net (outE.internet-mail-service.net [216.240.47.228]) by mx1.freebsd.org (Postfix) with ESMTP id B141B13C4B8 for ; Sun, 28 Oct 2007 05:30:39 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Sat, 27 Oct 2007 22:30:39 -0700 X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id C195A126836 for ; Sat, 27 Oct 2007 22:30:38 -0700 (PDT) Message-ID: <47241E9C.7000605@elischer.org> Date: Sat, 27 Oct 2007 22:31:08 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: learned something about coretemp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 05:30:39 -0000 never kldload it on an 8 year old system. *bewm* I presume that my 8 YO inspiron 7500 doesn't have whatever is needed, but, "*Bewm*" is probably a less than optimal reaction. From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 07:02:43 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4BFD116A476 for ; Sun, 28 Oct 2007 07:02:43 +0000 (UTC) (envelope-from SRS0=18136c24d292759ccff70853cfbd41647e5f2e31=502=es.net=oberman@es.net) Received: from postal1.es.net (postal3.es.net [IPv6:2001:400:14:3::8]) by mx1.freebsd.org (Postfix) with ESMTP id 186B913C480 for ; Sun, 28 Oct 2007 07:02:41 +0000 (UTC) (envelope-from SRS0=18136c24d292759ccff70853cfbd41647e5f2e31=502=es.net=oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id HRE47136; Sun, 28 Oct 2007 00:02:36 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 0B04345028; Sun, 28 Oct 2007 00:02:34 -0700 (PDT) To: Marcel Moolenaar In-Reply-To: Your message of "Sat, 27 Oct 2007 15:04:40 PDT." <28D8C5EF-8BAB-433D-A6E3-25B2A40B9BD1@mac.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1193554954_50909P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Sun, 28 Oct 2007 00:02:34 -0700 From: "Kevin Oberman" Message-Id: <20071028070234.0B04345028@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ; ; ; X-Sender: X-To_Name: Marcel Moolenaar X-To_Domain: mac.com X-To: Marcel Moolenaar X-To_Email: xcllnt@mac.com X-To_Alias: xcllnt Cc: John-Mark Gurney , current@freebsd.org Subject: Re: New-bus unit wiring via hints.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 07:02:43 -0000 --==_Exmh_1193554954_50909P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > From: Marcel Moolenaar > Date: Sat, 27 Oct 2007 15:04:40 -0700 > > > On Oct 27, 2007, at 2:24 PM, Kevin Oberman wrote: > > >> From: Marcel Moolenaar > >> Date: Sat, 27 Oct 2007 13:57:25 -0700 > >> > >> > >> On Oct 27, 2007, at 12:40 PM, Kevin Oberman wrote: > >> > >>>> I'm not mandating anything. I'm merely pointing out how > >>>> reality has changed and that it's important to adapt, > >>>> adopt and improve... > >>> > >>> "Reality has changed"? Yes, it has, at least a bit, but not to the > >>> point where we want to confuse serial ports. > >> > >> Are you saying that "we" should accept reality's change > >> only for as far as it doesn't confuse "us" ??? > > > > Just in case I don't understand the issue, feel free to correct me, > > but > > it sounds like you are saying that there will not be a clear link > > between the serial port (sio) number and the port marked '1' on most > > systems. If I am wrong about this, please tell me and I climb back > > under my rock. > > That is not what I'm saying. What I'm saying is: > If the firmware tells the OS that the port marked > "1" on the back corresponds to a UART that has a > base I/O port address of 0x2e8, then who are we > to disagree and demand that it should be 0x3f8? > > You rightly point out that what it really boils > down to is how devX maps to a port on the back or > front of the machine. This mapping should not > change gratuitously. Device wiring achieves that. OK. I'm still not entirely comfortable with this, but you make an excellent point here. I'd feel better about it if I had not encountered so many systems with broken BIOS, though. > Why not? You replace a mainboard. You really replaced the > whole computer, because there's no concept of chassis > port numbers in FreeBSD. All we know about the hardware > is what is on the mainboard. > > > The new system has, to the typical user's eyes, the same > > configuration. > > Yes. this means there's a gap between what the user sees > (the chassis) and what FreeBSD sees (the mainboard). As > long as the mainboard is designed for the chassis, that > gap is mostly non-existent or insignificant and what the > firmware tells the OS is what you see on the back (or > front). Otherwise, all bets are off... > Once again, this assumes competent firmware from the manufacturer, but you are probably really right. I guess it goes back to when you HAD to specify an address and IRQ for every device (as well as where it tied to the system) in the old days and I will concede that those days are past and that is a good thing. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1193554954_50909P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFHJDQKkn3rs5h7N1ERAqV1AJ0bjcJBtjJL+4iL40j6vkoeDbmMBQCfUhmo H+aa51dO3IF0Ihdz7YKz/U8= =M5PU -----END PGP SIGNATURE----- --==_Exmh_1193554954_50909P-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 07:07:37 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5D3216A418 for ; Sun, 28 Oct 2007 07:07:37 +0000 (UTC) (envelope-from SRS0=18136c24d292759ccff70853cfbd41647e5f2e31=502=es.net=oberman@es.net) Received: from postal1.es.net (postal4.es.net [IPv6:2001:400:6000:1::66]) by mx1.freebsd.org (Postfix) with ESMTP id 0793A13C4A7 for ; Sun, 28 Oct 2007 07:07:34 +0000 (UTC) (envelope-from SRS0=18136c24d292759ccff70853cfbd41647e5f2e31=502=es.net=oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal4.es.net (Postal Node 4) with ESMTP (SSL) id HRJ42633; Sun, 28 Oct 2007 00:07:33 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 0271A4500E; Sun, 28 Oct 2007 00:07:32 -0700 (PDT) To: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= In-Reply-To: Your message of "Sat, 27 Oct 2007 17:46:34 EDT." <4723B1BA.5010102@conducive.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1193555251_50909P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Sun, 28 Oct 2007 00:07:32 -0700 From: "Kevin Oberman" Message-Id: <20071028070732.0271A4500E@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ;; X-Sender: X-To_Name: =?utf-8?Q?=E9=9F=93=E5=AE=B6=E6=A8=99 Bill Hacker?= X-To_Domain: conducive.net X-To: =?utf-8?Q?=E9=9F=93=E5=AE=B6=E6=A8=99 Bill Hacker ?= X-To_Email: askbill@conducive.net X-To_Alias: askbill Cc: freebsd-current@freebsd.org Subject: Re: New-bus unit wiring via hints.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 07:07:37 -0000 --==_Exmh_1193555251_50909P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Sat, 27 Oct 2007 17:46:34 -0400 > From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= > Sender: owner-freebsd-current@freebsd.org > > Kevin Oberman wrote: > >> From: Marcel Moolenaar > >> Date: Sat, 27 Oct 2007 12:09:29 -0700 > >> Sender: owner-freebsd-current@freebsd.org > >> > >> > >> On Oct 27, 2007, at 10:58 AM, John-Mark Gurney wrote: > >> > >>> Yeh, you're solution was to simply declare that anyone who knows that > >>> COM1 is at 0x3f8 is wrong, and to use a different, yet again arbitrary > >>> solution which is which is listed first in ACPI... > >> Exactly. Anyone who "knows" that COM1 is at 0x3f8 while > >> the computer right in front of them clearly states that > >> COM1 is at 0x2f8 is in denial. > >> > >>> So, if one ACPI implementation puts _UID = 0 at 0x3f8, but lists it > >>> after _UID = 1 at 0x2f8, that it's fine for sio0 to be _UID = 1? > >> Yes. sio0 is nothing more than the first serial port found during > >> enumeration. > >> > >> > >>> So, why are you continuing to argue about a simple thing that you > >>> on your > >>> machines can simply remove the hints? > >> The ability to wire is good. Implementing it right > >> is important. > >> > >>> What are your technical arguments > >>> for mandating a different, non-historical, based arbitrary selection? > >> I'm not mandating anything. I'm merely pointing out how > >> reality has changed and that it's important to adapt, > >> adopt and improve... > >> > >> Where are your technical arguments, putting aside the > >> mere technically of the statement that you consider > >> yourself an old fart? > > > > "Reality has changed"? Yes, it has, at least a bit, but not to the > > point where we want to confuse serial ports. > > > > You are exhibiting are very 'selective' memory (the wetware one). My wetware is subject to too many errors, but I don't think this is one. > > Back in the days of v3 and v4, adding an IDE disk to a system could > > cause existing drives to change their device names. This meant that the > > fstab was unexpectedly wrong and things sometimes got messy. The option > > to fix this was added in V4 and moved to GENERIC after a while. Now the > > order in which IDE ports is scanned does not break the device names. > > That would be nice - if only it were true. It is very true and I didn't find it nice. It was fixed in head on Dec. 8, 1999 with the new ATA driver. Prior to that, if you had two drives, one on each IDE bus as master, they were numbered 0 and 1. If you added a slave disk on the first bus, it became drive 1 and the master on the second bus became drive 2. You still get the same behavior today if you remove the ATA_STATIC_ID option from your kernel. While I found most of your arguments rather weak, Marcel has me pretty much convinced that he is right, so I will not waste everyone's time with countering them. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1193555251_50909P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFHJDUzkn3rs5h7N1ERAh0GAJ0c5t0x7xS07E2Oh5aqJVpfCej6ZQCeLc06 5pioIXJtOQvPtpISSQ9gbro= =OBFP -----END PGP SIGNATURE----- --==_Exmh_1193555251_50909P-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 08:12:59 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E35B16A526; Sun, 28 Oct 2007 08:12:59 +0000 (UTC) (envelope-from chris@hitnet.RWTH-Aachen.DE) Received: from mta-2.ms.rz.rwth-aachen.de (mta-2.ms.rz.RWTH-Aachen.DE [134.130.7.73]) by mx1.freebsd.org (Postfix) with ESMTP id D618113C48E; Sun, 28 Oct 2007 08:12:58 +0000 (UTC) (envelope-from chris@hitnet.RWTH-Aachen.DE) Received: from ironport-out-1.rz.rwth-aachen.de ([134.130.3.58]) by mta-2.ms.rz.RWTH-Aachen.de (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTP id <0JQM000N02RKH470@mta-2.ms.rz.RWTH-Aachen.de>; Sun, 28 Oct 2007 08:42:56 +0100 (CET) Received: from talos.rz.rwth-aachen.de (HELO smarthost.rwth-aachen.de) ([134.130.3.22]) by ironport-in-1.rz.rwth-aachen.de with ESMTP; Sun, 28 Oct 2007 08:42:56 +0100 Received: from bigboss.hitnet.rwth-aachen.de (bigspace.hitnet.RWTH-Aachen.DE [137.226.181.2]) by smarthost.rwth-aachen.de (8.13.8/8.13.8/1) with ESMTP id l9S7gt7q004026; Sun, 28 Oct 2007 08:42:55 +0100 Received: from haakonia.hitnet.rwth-aachen.de ([137.226.181.92]) by bigboss.hitnet.rwth-aachen.de with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1Im2nO-0000Wt-Ko; Sun, 28 Oct 2007 08:42:55 +0100 Received: by haakonia.hitnet.rwth-aachen.de (Postfix, from userid 1001) id 24B5F3F433; Sun, 28 Oct 2007 08:42:49 +0100 (CET) Date: Sun, 28 Oct 2007 08:42:49 +0100 From: Christian Brueffer In-reply-to: <47240A15.8080305@charter.net> To: Andrew Lankford Message-id: <20071028074248.GA1511@haakonia.hitnet.RWTH-Aachen.DE> MIME-version: 1.0 Content-type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary=ZGiS0Q5IWpPtfppv Content-disposition: inline X-IronPort-AV: E=Sophos;i="4.21,338,1188770400"; d="scan'208";a="31353455" X-Operating-System: FreeBSD 6.2-STABLE X-PGP-Key: http://people.FreeBSD.org/~brueffer/brueffer.key.asc X-PGP-Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D References: <47240A15.8080305@charter.net> User-Agent: Mutt/1.5.11 Cc: stable@freebsd.org, current@freebsd.org Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 08:12:59 -0000 --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 28, 2007 at 12:03:33AM -0400, Andrew Lankford wrote: > I just noticed that /usr/share/man/man8/MAKEDEV.8 is still in the=20 > FreeBSD-7 tree. Is this intentional? It still says that MAKEDEV is > located in /dev and mentions MAKEDEV.local as well. >=20 Could it be that you have updated this machine from RELENG_4? The fact that the file you're referring to has no .gz extention show that it's stale, manpages have been compressed for some time now. Also, I was the one who removed the original MAKEDEV.8 manpage, so I know ;-) After the removal, a small new one was added to refer people to devfs-related material. - Christian --=20 Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D --ZGiS0Q5IWpPtfppv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFHJD14bHYXjKDtmC0RAlLRAKDxU4/ah/0DRPD8VzAspjrMsA3f2ACgrKdi G821QYDiXLCKp1IhUYjwNB0= =JZxj -----END PGP SIGNATURE----- --ZGiS0Q5IWpPtfppv-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 08:16:14 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C93AE16A521 for ; Sun, 28 Oct 2007 08:16:14 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (conducive.net [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id 8FA9713C494 for ; Sun, 28 Oct 2007 08:16:14 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:63827 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1Im3Jd-000Fg7-2L for freebsd-current@freebsd.org; Sun, 28 Oct 2007 08:16:13 +0000 Message-ID: <47244548.9060301@conducive.net> Date: Sun, 28 Oct 2007 04:16:08 -0400 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20071028070732.0271A4500E@ptavv.es.net> In-Reply-To: <20071028070732.0271A4500E@ptavv.es.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: New-bus unit wiring via hints.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 08:16:14 -0000 Kevin Oberman wrote: *snip* >>> >> You are exhibiting are very 'selective' memory (the wetware one). > > My wetware is subject to too many errors, but I don't think this is one. > Sorry - that was meant in re Marcel's belief that the mapping of logical name to hex baseport addr of serial ports had [at some point in time | ever] been 'fixed'. They never were. Though from IBM ISA onward they were at least a smaller 'pool' of two, three, or four. >>> Back in the days of v3 and v4, adding an IDE disk to a system could >>> cause existing drives to change their device names. This meant that the >>> fstab was unexpectedly wrong and things sometimes got messy. The option >>> to fix this was added in V4 and moved to GENERIC after a while. Now the >>> order in which IDE ports is scanned does not break the device names. >> That would be nice - if only it were true. > > It is very true and I didn't find it nice. It was fixed in head on > Dec. 8, 1999 with the new ATA driver. That's only a partial 'fix'. > Prior to that, if you had two > drives, one on each IDE bus as master, they were numbered 0 and 1. If > you added a slave disk on the first bus, it became drive 1 and the > master on the second bus became drive 2. An improvement, certainly. > You still get the same > behavior today if you remove the ATA_STATIC_ID option from your kernel. > Sorry - it is more complex than that, and for (at least) two reasons: 1) Presence of at least two, often three or more *onboard* controllers, not to mention those commonly added to the bus. The entire controller 'block' may be inserted before as well as after the 'legacy' one(s). Likewise some environments place a bus-attached controller before, others after the onboard one(s) in the ordering. This also changes with BIOS rev & 'race', specifics of the add-on gear, and even PCI slot-order. Has done since pre-ISA days, (jumpers, DIP). Still does so in current MB, such as ASUS P5K and Gigagbyte GA G33-DS3R. 2) Then there are the BIOS options, including 'mode' as in 'IDE', 'Native', 'Compatible', 'RAID' and/or 'AHCI' enable/disable choices. Result: Citing just those two newest boards, is that the 'legacy' IDE block retains sequence-order, reserving 'seats' 0 thru 3 for devices - attached or absent - just as you noted. That IS 'nice'. But no longer 'enough', and absent PATA devices, perhaps not even relevant. - Supplementary SATA controllers may logically enumerate their 'seats' in EITHER forward OR reverse order vs the hardware / MB silkscreen labels, AND may insert the resulting block either after or BEFORE the legacy IDE block (0 thru 3) - renumber it in the process. /dev/ad0 becoming /dev/ad9, for example. A casual user is likely to have to deal with at least *part* of that menage, if only once... An R&D shop experimenting with the BIOS settings has to keep multiple /fstab and paper 'cheat sheets' just to go multi.. That is part of the same 'mapping' issue as serial ports, but is a growing problem, whereas serial ports have all but disappeared in any case. > While I found most of your arguments rather weak, Marcel has me pretty > much convinced that he is right, so I will not waste everyone's time > with countering them. Not interested in 'argument'. Just pointing out the assumptions about immutability of hex-addr to logical device ID are flawed. Historical OR recent. That is not going away. A better 'fix' needs steering options adopted by the BIOS-provider(s). Don't hold your breath while waiting on those to arrive OR be consistent. Beyond our control. Plan to adapt. Bill From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 08:32:36 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6421B16A421 for ; Sun, 28 Oct 2007 08:32:36 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with SMTP id 0104513C4B7 for ; Sun, 28 Oct 2007 08:32:35 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 6331 invoked by uid 399); 28 Oct 2007 08:32:35 -0000 Received: from localhost (HELO slave.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 28 Oct 2007 08:32:35 -0000 X-Originating-IP: 127.0.0.1 Date: Sun, 28 Oct 2007 01:32:33 -0700 (PDT) From: Doug Barton To: Christian Brueffer In-Reply-To: <20071028074248.GA1511@haakonia.hitnet.RWTH-Aachen.DE> Message-ID: References: <47240A15.8080305@charter.net> <20071028074248.GA1511@haakonia.hitnet.RWTH-Aachen.DE> X-message-flag: Outlook -- Not just for spreading viruses anymore! X-OpenPGP-Key-ID: 0xD5B2F0FB Organization: http://www.FreeBSD.org/ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: Andrew Lankford , stable@freebsd.org, current@freebsd.org Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 08:32:36 -0000 On Sun, 28 Oct 2007, Christian Brueffer wrote: > On Sun, Oct 28, 2007 at 12:03:33AM -0400, Andrew Lankford wrote: >> I just noticed that /usr/share/man/man8/MAKEDEV.8 is still in the >> FreeBSD-7 tree. Is this intentional? It still says that MAKEDEV is >> located in /dev and mentions MAKEDEV.local as well. >> > > Could it be that you have updated this machine from RELENG_4? The fact > that the file you're referring to has no .gz extention show that it's > stale, manpages have been compressed for some time now. A simple way to make sure you don't get bitten by this is to 'rm -r /usr/share/man' right before you do 'make installworld'. (Or you can mv it if you're paranoid, I've been deleting it for a long time now and it's never bitten me.) hth, Doug -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 10:24:06 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 177B516A418 for ; Sun, 28 Oct 2007 10:24:06 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.freebsd.org (Postfix) with ESMTP id 9096213C480 for ; Sun, 28 Oct 2007 10:24:04 +0000 (UTC) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.14.1/8.14.1) with ESMTP id l9SAO3ie032284; Sun, 28 Oct 2007 13:24:03 +0300 (MSK) (envelope-from marck@rinet.ru) Date: Sun, 28 Oct 2007 13:24:03 +0300 (MSK) From: Dmitry Morozovsky To: David Taylor In-Reply-To: <20071027122454.GA15883@outcold.yadt.co.uk> Message-ID: <20071028132301.N47854@woozle.rinet.ru> References: <200710252120.l9PLKYFJ041330@himinbjorg.tucs-beachin-obx-house.com> <47210FBE.6080803@gmail.com> <20071025220742.GA45217@owl.midgard.homeip.net> <200710251516.19505.fjwcash+freebsd@gmail.com> <20071027122454.GA15883@outcold.yadt.co.uk> X-NCC-RegID: ru.rinet X-OpenPGP-Key-ID: 6B691B03 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (woozle.rinet.ru [0.0.0.0]); Sun, 28 Oct 2007 13:24:03 +0300 (MSK) Cc: current@freebsd.org Subject: Re: 7.0-BETA1.5 ISO/ftp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 10:24:06 -0000 On Sat, 27 Oct 2007, David Taylor wrote: DT> > > But csup does not yet support CVS mode, so you can't use it to maintain DT> > > a local copy of the repository. For some people (including me) this DT> > > means that csup is not yet a suitable replacement for CVSup. DT> > DT> > Maybe not, but for the bulk of the users of cvsup, csup is a drop-in DT> > replacement. :) As with most things in Unix-land, there's more than one DT> > way to do things, and every one will defend to the death their way of DT> > doing things. :D DT> DT> I think the point is there _isn't_ more than one way to cvsup the CVS DT> repo - csup currently cannot do that. Oh well there are - however, there should be efforts applied on the server side (one example: rsync) Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck@FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 11:18:07 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2AB1316A419 for ; Sun, 28 Oct 2007 11:18:07 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Received: from mx.isc.org (mx.isc.org [IPv6:2001:4f8:0:2::1c]) by mx1.freebsd.org (Postfix) with ESMTP id 12AD213C4A8 for ; Sun, 28 Oct 2007 11:18:07 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "farside.isc.org", Issuer "ISC CA" (verified OK)) by mx.isc.org (Postfix) with ESMTP id 4FA0611401E for ; Sun, 28 Oct 2007 11:18:06 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Received: from manx.isc.org (manx.isc.org [IPv6:2001:4f8:3:bb::37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by farside.isc.org (Postfix) with ESMTP id 6CAD8E6058; Sun, 28 Oct 2007 11:18:06 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Message-ID: <47246FED.6000103@isc.org> Date: Sun, 28 Oct 2007 04:18:05 -0700 From: Peter Losher Organization: ISC User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG X-Enigmail-Version: 0.95.4 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigC2A42DAD31925A51276AFB52" Cc: Subject: Clearing out vdevs (can't create new zpool) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 11:18:07 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC2A42DAD31925A51276AFB52 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I have been poking around with our 16-port SATA RAID chassis (in JBOD mode) with a fresh RELENG_7 internal build from Saturday. I only had half the disks {da0-7) at first, when I brought over the second set (da8-15), I destroyed the existing pool and then tried to create a new one with all 16 disks, and encountered this error: -=3D- # zpool create tank raidz da{0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15} cannot create 'tank': one or more vdevs refer to the same device -=3D- I can create one with the second set of disks (and destroy/create again) but somehow I have some old vdevs sitting around which is preventing me from using the first set of disks. How can I clear them out? Best Wishes - Peter --=20 Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow" --------------enigC2A42DAD31925A51276AFB52 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFHJG/uPtVx9OgEjQgRAlo2AKCmUU1ZoXFUQkMD1oGFxPXPWspijwCfeYnA zRQwOL/KjmK8f+cvugMPBiI= =HDCw -----END PGP SIGNATURE----- --------------enigC2A42DAD31925A51276AFB52-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 12:22:17 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7420616A419 for ; Sun, 28 Oct 2007 12:22:17 +0000 (UTC) (envelope-from simias.n@gmail.com) Received: from simias.hd.free.fr (vit94-5-82-243-51-8.fbx.proxad.net [82.243.51.8]) by mx1.freebsd.org (Postfix) with ESMTP id 0FC7213C4B9 for ; Sun, 28 Oct 2007 12:22:16 +0000 (UTC) (envelope-from simias.n@gmail.com) Received: from simias.hd.free.fr (localhost [127.0.0.1]) by simias.hd.free.fr (8.14.1/8.14.1) with ESMTP id l9SC6Exd001167 for ; Sun, 28 Oct 2007 13:06:14 +0100 (CET) (envelope-from simias.n@gmail.com) Received: (from simias@localhost) by simias.hd.free.fr (8.14.1/8.14.1/Submit) id l9SC64Ki001166; Sun, 28 Oct 2007 13:06:04 +0100 (CET) (envelope-from simias.n@gmail.com) X-Authentication-Warning: simias.hd.free.fr: simias set sender to simias.n@gmail.com using -f From: Lionel Flandrin To: freebsd-current@freebsd.org Date: Sun, 28 Oct 2007 13:05:53 +0100 Message-ID: <86tzobzboe.fsf@simias.hd.free.fr> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/23.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: fresh -CURRENT: ps: time: keyword not found X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 12:22:17 -0000 On a -CURRENT csup'd a couple of hours ago, I get a message on stderr every time in run "ps": "ps: time: keyword not found". For instance: ,---- | $ uname -a | FreeBSD simias.hd.free.fr 8.0-CURRENT FreeBSD 8.0-CURRENT #0: | Sun Oct 2810:08:04 CET 2007 | root@simias.hd.free.fr:/usr/obj/usr/src/sys/SIMKERNEL i386 | $ ps | ps: time: keyword not found | PID TT STAT COMMAND | 943 v0 I -zsh (zsh) | 976 v0 I+ /bin/sh /usr/local/bin/startx | 994 v0 I+ xinit /home/simias/.xinitrc -- -auth /home/simias/.serverauth.9 | 1000 v0 I sh /home/simias/.xinitrc | 1007 v0 I /bin/sh /home/simias/bin/start-stumpwm | 1009 v0 S /home/simias/dev/lisp/stumpwm/stumpwm | 1015 v0 I /bin/sh -c rxvt | 1016 v0 S rxvt | 1044 v0 I /bin/sh -c emacs | 1045 v0 S emacs | 1095 v0 I /bin/sh -c rxvt | 1096 v0 S rxvt | 1017 p0 Is zsh | 1028 p0 S+ screen | 1031 p1 Is /usr/local/bin/zsh | 1043 p1 S+ ssh -p2223 myrix.net | 1097 p2 Is+ zsh `---- Any clues? -- Lionel Flandrin From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 13:07:31 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C909D16A417 for ; Sun, 28 Oct 2007 13:07:31 +0000 (UTC) (envelope-from bv@bilver.wjv.com) Received: from wjv.com (fl-65-40-24-38.sta.embarqhsd.net [65.40.24.38]) by mx1.freebsd.org (Postfix) with ESMTP id 5BAC413C494 for ; Sun, 28 Oct 2007 13:07:31 +0000 (UTC) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.14.1/8.13.1) with ESMTP id l9SCkA67081526 for ; Sun, 28 Oct 2007 08:46:15 -0400 (EDT) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.14.1/8.13.1/Submit) id l9SCk4Vd081525 for freebsd-current@freebsd.org; Sun, 28 Oct 2007 08:46:04 -0400 (EDT) (envelope-from bv) Date: Sun, 28 Oct 2007 08:46:04 -0400 From: Bill Vermillion To: freebsd-current@freebsd.org Message-ID: <20071028124604.GA43062@wjv.com> References: <20071028081634.722CF16A547@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071028081634.722CF16A547@hub.freebsd.org> User-Agent: Mutt/1.4.2.2i Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com Subject: Re: New bus-unit wiring via hints.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bv@wjv.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 13:07:31 -0000 Wise men talk because they have something to say, however on Sun, Oct 28, 2007 at 08:16 , freebsd-current-request@freebsd.org just had to say something so we heard: > Date: Sat, 27 Oct 2007 20:53:21 +0200 > From: Erik Trulsson > Subject: Re: New-bus unit wiring via hints.. > On Sat, Oct 27, 2007 at 10:58:56AM -0700, John-Mark Gurney > wrote: > > Marcel Moolenaar wrote this message on Sat, Oct 27, 2007 at > > 10:48 -0700: > > > On Oct 27, 2007, at 10:42 AM, John-Mark Gurney wrote: > > > >I believe that the hints is the correct thing, Marcel never > > > >answered how to ensure ACPI kept sio0 as COM1, > > > I did answer that. You obvious did not read or understand a > > > I word was saying... > > Yeh, you're solution was to simply declare that anyone who > > knows that COM1 is at 0x3f8 is wrong, and to use a different, > > yet again arbitrary solution which is which is listed first in > > ACPI... > > To quote you: More legacy PC fixation. If the BIOS claims that > > COM1 is at 0x2f8 then so be it. If COM2 is enumerated first > > and it ends up as uart0 then so be it. There's no bug. It's > > all in a name. Device wiring would allow people to tie COM2 > > to uart1 if they want to, but all this COM-stuff is really > > nothing more than a fixation on 20-year old conventions that > > the rest of the world abandoned many years ago. It's turned > > into a bigger problem than it really is, mostly because we > > still have those stupid hints that are based on 20-year old > > conventions. > > So, if one ACPI implementation puts _UID = 0 at 0x3f8, but > > lists it after _UID = 1 at 0x2f8, that it's fine for sio0 to > > be _UID = 1? I'm fine w/ that... Just as long as we ship a > > hints file to keep us old farts sane... > Yup. If I in the BIOS setup screen tells the BIOS that the first > serial port should be at 0x3f8, and the second serial port > should be at 0x2f8, then it is very annoying if FreeBSD attaches > sio0 to the serial port at 0x2f8 and sio1 to the port at 0x3f8 > - the opposite of what I wanted. (This is not a hypothetical > example, by the way.) Hmm. I started running Xenix systems on Intel systems [SCO's Xenix, and Altos systems] back in the 1984 era. At that time as I recall it the BIOS was ONLY used to get the information to boot the system, and everything else in the BIOS was ignored. This caused a lot of confusion for people who had come from a DOS oriented world and saying things such as "well it works in DOS so *i*x must be broken. So - have things changed where the OS looks at the BIOS [in the *i*x world - or is it like this old fart remembers where BIOS was only used to find the HD and boot the OS? Bill -- Bill Vermillion - bv @ wjv . com From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 12:53:43 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 274AE16A417 for ; Sun, 28 Oct 2007 12:53:43 +0000 (UTC) (envelope-from blacknova@tut.by) Received: from speedy.tutby.com (mail.tut.by [195.137.160.40]) by mx1.freebsd.org (Postfix) with ESMTP id A45A313C494 for ; Sun, 28 Oct 2007 12:53:42 +0000 (UTC) (envelope-from blacknova@tut.by) Received: from [91.149.132.24] (account blacknova@tut.by HELO [192.168.1.2]) by speedy.tutby.com (CommuniGate Pro SMTP 5.1.12) with ESMTPA id 419979277 for freebsd-current@freebsd.org; Sun, 28 Oct 2007 14:38:38 +0200 Message-ID: <4724823B.3090606@tut.by> Date: Sun, 28 Oct 2007 14:36:11 +0200 From: =?UTF-8?B?0JLQu9Cw0LTQuNC80LjRgCDQndC+0LLQvtGB0LXQu9GM0YbQtdCy?= User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 28 Oct 2007 13:20:13 +0000 Subject: Problem with ATAPI device on JMicron JMB363 on 7.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 12:53:43 -0000 Hi, I've tried to install FreeBSD 7.0-BETA1/amd64 on Gigabyte P35-S3 mb with PATA DVD-RW drive attached to JMicron JMB363 controller. acd0: DVDR with hw.ata.atapi_dma=1 I got the following error messages while booting from CD: acd0: TIMEOUT - READ_BIG retrying (1 retry left) acd0: TIMEOUT - READ_BIG retrying (0 retries left) acd0: FAILURE- READ_BIG timed out with hw.ata.atapi_dma=0 system boots correctly, but during boot it output several lines like: acd0: FAILURE - READ_BIG ILLEGAL REQUEST overall it looks similar to kern/103602 and kern/111419 which are already marked as closed. If you need any additional info, please ask. WBR, Vladimir Novoseltsev From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 13:36:40 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9225C16A469 for ; Sun, 28 Oct 2007 13:36:40 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:610:652::211]) by mx1.freebsd.org (Postfix) with ESMTP id 5691813C4A7 for ; Sun, 28 Oct 2007 13:36:40 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 6B5EF1CC1E; Sun, 28 Oct 2007 14:36:37 +0100 (CET) Date: Sun, 28 Oct 2007 14:36:37 +0100 From: Ed Schouten To: Bill Vermillion Message-ID: <20071028133637.GC5411@hoeg.nl> References: <20071028081634.722CF16A547@hub.freebsd.org> <20071028124604.GA43062@wjv.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IhRHiOJhC/7Q+39k" Content-Disposition: inline In-Reply-To: <20071028124604.GA43062@wjv.com> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: FreeBSD Current Subject: Re: New bus-unit wiring via hints.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 13:36:40 -0000 --IhRHiOJhC/7Q+39k Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Bill Vermillion wrote: > Hmm. I started running Xenix systems on Intel systems [SCO's > Xenix, and Altos systems] back in the 1984 era. >=20 > At that time as I recall it the BIOS was ONLY used to get > the information to boot the system, and everything else in the BIOS > was ignored. This caused a lot of confusion for people who had > come from a DOS oriented world and saying things such as "well it > works in DOS so *i*x must be broken. >=20 > So - have things changed where the OS looks at the BIOS [in the > *i*x world - or is it like this old fart remembers where BIOS was > only used to find the HD and boot the OS? A good example is FreeBSD on the Microsoft Xbox. The Xbox has no PC-style BIOS and yet it's capable of running a (slightly patched) FreeBSD kernel. A disadvantage of the Xbox is that it doesn't have a VGA BIOS interface, which means the port uses a custom framebuffer driver to make the console work. --=20 Ed Schouten WWW: http://g-rave.nl/ --IhRHiOJhC/7Q+39k Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHJJBl52SDGA2eCwURAtFEAJsEwdlyD2gfEqcWmrNl+j1v1HNskgCeKdYr uI2d6QtLV08r8+Hq41xly24= =qzWp -----END PGP SIGNATURE----- --IhRHiOJhC/7Q+39k-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 14:02:54 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A01CD16A41A for ; Sun, 28 Oct 2007 14:02:54 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 7903113C4B0 for ; Sun, 28 Oct 2007 14:02:54 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 5D58742318; Sun, 28 Oct 2007 09:45:56 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Sun, 28 Oct 2007 09:45:56 -0400 X-Sasl-enc: xc9b9LS4Sh1W8hOi/CODRuNWbL+SvbBRQiGzXlymbNd0 1193579155 Received: from [192.168.1.239] (64-142-85-108.dsl.dynamic.sonic.net [64.142.85.108]) by mail.messagingengine.com (Postfix) with ESMTP id A289125071; Sun, 28 Oct 2007 09:45:55 -0400 (EDT) Message-ID: <47249270.6090707@freebsd.org> Date: Sun, 28 Oct 2007 06:45:20 -0700 From: Darren Reed Organization: FreeBSD User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: Julian Elischer References: <47241E9C.7000605@elischer.org> In-Reply-To: <47241E9C.7000605@elischer.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: learned something about coretemp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: darrenr@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 14:02:54 -0000 Julian Elischer wrote: > never kldload it on an 8 year old system. > > *bewm* > > I presume that my 8 YO inspiron 7500 doesn't have whatever is needed, > but, "*Bewm*" is probably a less than optimal reaction. So what happened when you did kldload it? (at least "*bewm*" does not mean anything to me.) Darren From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 14:21:00 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1388416A417; Sun, 28 Oct 2007 14:21:00 +0000 (UTC) (envelope-from andy@neu.net) Received: from neu.net (neu.net [204.3.153.161]) by mx1.freebsd.org (Postfix) with ESMTP id D019313C4A7; Sun, 28 Oct 2007 14:20:59 +0000 (UTC) (envelope-from andy@neu.net) Received: from neu.net (localhost [127.0.0.1]) by neu.net (8.13.6.20060614/8.13.6) with ESMTP id l9SE4fem022559; Sun, 28 Oct 2007 14:04:42 GMT Received: from localhost (andy@localhost) by neu.net (8.13.6.20060614/8.13.6/Submit) with ESMTP id l9SE4fFW022556; Sun, 28 Oct 2007 14:04:41 GMT Date: Sun, 28 Oct 2007 14:04:41 +0000 (GMT) From: AN To: freebsd-current@freebsd.org Message-ID: <20071028134603.H19526@neu.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-openoffice@freebsd.org, freebsd-questions@freebsd.org, freebsd-gnome@freebsd.org Subject: library issue? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 14:21:00 -0000 I am trying to setup a workstation with 7.0-BETA1.5, xorg-7.3_1, gnome2-2.18.3., and openoffice.org-2.3.0. I installed openoffice via pkg_add -r. Everything installs correctly, however, when I try to run openoffice.org-2.3.0 after the install I get the following: %openoffice.org-2.3.0 /libexec/ld-elf.so.1: Shared object "libm.so.4" not found, required by "javaldx" /libexec/ld-elf.so.1: Shared object "libm.so.4" not found, required by "pagein" /libexec/ld-elf.so.1: Shared object "libm.so.4" not found, required by "soffice.bin" Here is the output from ldd: ldd: /usr/local/openoffice.org-2.3.0/program/swriter: not a dynamic executable uname:FreeBSD opteron.foo.bar 7.0-BETA1.5 FreeBSD 7.0-BETA1.5 #0: Thu Oct 25 01:19:36 UTC 2007 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 I don't know what to try to troubleshoot this, any help would be appreciated. If I did not provide enough info, please let me know exactly what to provide and I will be happy to supply it (explicit commands would be appreciated). TIA From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 14:36:06 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 955F916A41A for ; Sun, 28 Oct 2007 14:36:06 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181]) by mx1.freebsd.org (Postfix) with ESMTP id 4640113C48E for ; Sun, 28 Oct 2007 14:36:06 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so2426571pyb for ; Sun, 28 Oct 2007 07:36:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=AOUm31BPO9HkUL6JjsVIreDedtF8ehrVa59G5HviyI8=; b=ig92Sh3PIAlU6Mfx1U8GJ4EeLCEn/dYpEgYV3gCvL7fTlI3QtxZrJUeeazQ9mWCoZDpwRj7nBra/BC6DLuINgXi2IIzhOD3flt73ueBz55mJ7tjXST7y+paFEaL/twEvSW/A4IEu8LnaEzFUQUdz593UZZSZZBOGD3vUMiai6x8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=YoIN5ZBn5Kjt0ACfnc9GQHTq7/o+Ubapbg/Di7xr9qRpVbvT72VUbAGq1LApegt2122PUNpzpVml4gxHMOGKzKDMsNgm6iKWrUMOZ5HnN9rVRnaGcX81CBnO4QCYxLjdlGIXbOgjtobQaZ0p9iogZs2YoII583Sg9wN0EBOYk+k= Received: by 10.35.129.19 with SMTP id g19mr6163512pyn.1193582165634; Sun, 28 Oct 2007 07:36:05 -0700 (PDT) Received: by 10.35.108.9 with HTTP; Sun, 28 Oct 2007 07:36:05 -0700 (PDT) Message-ID: Date: Sun, 28 Oct 2007 14:36:05 +0000 From: "Rui Paulo" Sender: rpaulo@gmail.com To: "Julian Elischer" In-Reply-To: <47241E9C.7000605@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47241E9C.7000605@elischer.org> X-Google-Sender-Auth: 9bbc5ac19d8be9d1 Cc: FreeBSD Current Subject: Re: learned something about coretemp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 14:36:06 -0000 On 10/28/07, Julian Elischer wrote: > never kldload it on an 8 year old system. > > *bewm* > > I presume that my 8 YO inspiron 7500 doesn't have whatever is needed, > but, "*Bewm*" is probably a less than optimal reaction. That has been reported in the past. It's Intel's fault, not ours. The spec says that if you issue a CPUID you should be able to tell if the CPU has the temperature sensors regardless of the CPU model, but on old systems these CPUID call "returns true". -- Rui Paulo From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 14:37:04 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A981C16A420 for ; Sun, 28 Oct 2007 14:37:04 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5FF6413C4A5 for ; Sun, 28 Oct 2007 14:37:03 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so2426923pyb for ; Sun, 28 Oct 2007 07:37:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=qhuBz4Xsxrb71DZb7Qy4+8et3sgCUumF4FPVWErLH0c=; b=EOrxm6jyXwd7yr6uF9e+yF6PtQj1CfAT+VjsrrLpiLa8lL/b+ZLux13cp2A2xwZHsWyVpJvXcRfaqaj6vg4bjrbS+u7dQTnG8Yst2gqu8Vvu8dIZA8Z8/PdNtBSXoJasYZLE1JNRSHUxLCC96WuavLfUMM1a8AsFBnTsOrIZ3bg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=ki3j5ALItXc8Xq4byzMHJV7aAvfK9AWDtHZpOpU0moorm79pgsqIGDcxLS2xESikJwW3pgZjkjfrPMSVRWjy9yuT97hZfSk5BTAOCWPDQZlp6bxjJBssDhI0s6ReF9TgmDbF13bUyFg54s1m5L0zl7jpV+6ZsKziOkRi/NKKx+A= Received: by 10.35.60.15 with SMTP id n15mr6194177pyk.1193582222490; Sun, 28 Oct 2007 07:37:02 -0700 (PDT) Received: by 10.35.108.9 with HTTP; Sun, 28 Oct 2007 07:37:01 -0700 (PDT) Message-ID: Date: Sun, 28 Oct 2007 14:37:01 +0000 From: "Rui Paulo" Sender: rpaulo@gmail.com To: darrenr@freebsd.org In-Reply-To: <47249270.6090707@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47241E9C.7000605@elischer.org> <47249270.6090707@freebsd.org> X-Google-Sender-Auth: d1195c8ad18cb1df Cc: Julian Elischer , FreeBSD Current Subject: Re: learned something about coretemp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 14:37:04 -0000 On 10/28/07, Darren Reed wrote: > Julian Elischer wrote: > > never kldload it on an 8 year old system. > > > > *bewm* > > > > I presume that my 8 YO inspiron 7500 doesn't have whatever is needed, > > but, "*Bewm*" is probably a less than optimal reaction. > > So what happened when you did kldload it? > (at least "*bewm*" does not mean anything to me.) Be Window Manager started up. :-) -- Rui Paulo From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 15:29:52 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13A0116A417 for ; Sun, 28 Oct 2007 15:29:52 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outI.internet-mail-service.net (outI.internet-mail-service.net [216.240.47.232]) by mx1.freebsd.org (Postfix) with ESMTP id EE92113C48A for ; Sun, 28 Oct 2007 15:29:51 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Sun, 28 Oct 2007 08:29:50 -0700 X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id 72006126836; Sun, 28 Oct 2007 08:29:50 -0700 (PDT) Message-ID: <4724AB0C.3070200@elischer.org> Date: Sun, 28 Oct 2007 08:30:20 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: darrenr@freebsd.org References: <47241E9C.7000605@elischer.org> <47249270.6090707@freebsd.org> In-Reply-To: <47249270.6090707@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: learned something about coretemp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 15:29:52 -0000 Darren Reed wrote: > Julian Elischer wrote: >> never kldload it on an 8 year old system. >> >> *bewm* >> >> I presume that my 8 YO inspiron 7500 doesn't have whatever is needed, >> but, "*Bewm*" is probably a less than optimal reaction. > > So what happened when you did kldload it? > (at least "*bewm*" does not mean anything to me.) > > Darren *bewm* is freebsd (and other) slang for *boom* it's takne from Inspector cluseau's pronounciation of it in the "Pink Panther" (instant reboot) From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 16:41:53 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1717F16A418; Sun, 28 Oct 2007 16:41:53 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 044A313C4B0; Sun, 28 Oct 2007 16:41:52 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id BC45F1CC087; Sun, 28 Oct 2007 09:41:52 -0700 (PDT) Date: Sun, 28 Oct 2007 09:41:52 -0700 From: Jeremy Chadwick To: Andrew Lankford Message-ID: <20071028164152.GA7516@eos.sc1.parodius.com> References: <47240A15.8080305@charter.net> <20071028074248.GA1511@haakonia.hitnet.RWTH-Aachen.DE> <4724BAD9.7000400@charter.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4724BAD9.7000400@charter.net> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: stable@freebsd.org, current@freebsd.org Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 16:41:53 -0000 On Sun, Oct 28, 2007 at 12:37:45PM -0400, Andrew Lankford wrote: > Thanks for replying, but once again I've miscommunicated the issue. I > meant that MAKEDEV.8 is in /usr/src/share/man/man8/, and the > modification time is Oct 13th, recent, which suggests to me that it's still > in the 7.0-BETA1 cvs tree. And you're very much correct: http://www.freebsd.org/cgi/cvsweb.cgi/src/share/man/man8/MAKEDEV.8 -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 17:12:12 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A33216A41A for ; Sun, 28 Oct 2007 17:12:12 +0000 (UTC) (envelope-from amb@amb.kiev.ua) Received: from simq3-srv.bellnexxia.net (simq3.bellnexxia.net [206.47.199.153]) by mx1.freebsd.org (Postfix) with ESMTP id 4082B13C494 for ; Sun, 28 Oct 2007 17:12:12 +0000 (UTC) (envelope-from amb@amb.kiev.ua) Received: from amb.homeunix.org ([156.34.188.4]) by simmts12-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20071028165903.NCVC25485.simmts12-srv.bellnexxia.net@amb.homeunix.org> for ; Sun, 28 Oct 2007 12:59:03 -0400 Received: from server.amb.kiev.ua ([10.15.25.2] helo=amb.kiev.ua) by amb.homeunix.org with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1ImBTY-00034m-3B for current@freebsd.org; Sun, 28 Oct 2007 13:59:00 -0300 Message-ID: <4724BFD4.2040406@amb.kiev.ua> Date: Sun, 28 Oct 2007 13:59:00 -0300 From: Andrew Birukov User-Agent: Thunderbird 2.0.0.6 (X11/20070803) MIME-Version: 1.0 To: current@freebsd.org Content-Type: multipart/mixed; boundary="------------090005000506050008010101" X-SA-Exim-Connect-IP: 10.15.25.2 X-SA-Exim-Rcpt-To: current@freebsd.org X-SA-Exim-Mail-From: amb@amb.kiev.ua X-SA-Exim-Scanned: No (on amb.homeunix.org); SAEximRunCond expanded to false Cc: Subject: pf broken in 7.0-BETA1 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 17:12:12 -0000 This is a multi-part message in MIME format. --------------090005000506050008010101 Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit pf.conf: --------------------------------------------------------------- ext_if="xl0" altq on $ext_if priq bandwidth 520Kb queue { ssh, traf } queue ssh priority 1 queue traf priority 15 priq(default) pass in all pass out all pass out on $ext_if proto tcp from any to any tos 0x10 queue ssh ----------------------------------------------------------------- I connected to remote host by ssh. In tcpdump i see many packets witch tos 0x10. 12:54:46.732928 IP (tos 0x10, ttl 64, id 12486, offset 0, flags [DF], proto TCP (6), length 52) 10.15.25.2.56587 > 194.0.91.110.22: ., cksum 0x35d5 (correct), 1919:1919(0) ack 2832 win 8181 12:54:46.746958 IP (tos 0x10, ttl 64, id 12487, offset 0, flags [DF], proto TCP (6), length 100) 10.15.25.2.56587 > 194.0.91.110.22: P 1919:1967(48) ack 2832 win 8195 12:54:46.900186 IP (tos 0x10, ttl 64, id 12488, offset 0, flags [DF], proto TCP (6), length 52) 10.15.25.2.56587 > 194.0.91.110.22: ., cksum 0x33ec (correct), 1967:1967(0) ack 2944 win 8181 12:54:46.915079 IP (tos 0x10, ttl 64, id 12489, offset 0, flags [DF], proto TCP (6), length 100) 10.15.25.2.56587 > 194.0.91.110.22: P 1967:2015(48) ack 2944 win 8195 tcpdump confirms that the outgoing ssh data packets have tos 0x10, but the majority of the packets are still going to the default "traf" queue. queue ssh on xl0 [ pkts: 0 bytes: 0 dropped pkts: 0 bytes: 0 ] [ qlength: 0/ 50 ] [ measured: 0.0 packets/s, 0 b/s ] queue traf on xl0 priority 15 priq( default ) [ pkts: 5059 bytes: 1130390 dropped pkts: 69 bytes: 80689 ] [ qlength: 0/ 50 ] [ measured: 3.9 packets/s, 2.15Kb/s ] This problem is affected 7.0 only. pf rools witch tos in FreeBSD-6.2 work properly. My configuration: # uname -a FreeBSD amb.kiev.ua 7.0-BETA1 FreeBSD 7.0-BETA1 #1: Sun Oct 28 10:08:13 ADT 2007 root@amb.kiev.ua:/usr/obj/usr/src/sys/AMB.7.0 i386 dmesg output and kernel config file are attached to this letter. If you need any additional info, please ask. Should I open an PR ? -- Andrew Biriukov amb@amb.kiev.ua --------------090005000506050008010101 Content-Type: text/plain; name="KERNEL" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="KERNEL" # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ../../conf/NOTES and NOTES files. # If you are in doubt as to the purpose or necessity of a line, check first # in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.474.2.1 2007/10/11 06:20:26 kensmith Exp $ #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident AMB # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols options SCHED_4BSD # 4BSD scheduler #options SCHED_ULE options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking #options INET6 # IPv6 communications protocols #options SCTP # Stream Control Transmission Protocol options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options UFS_GJOURNAL # Enable gjournal-based UFS journaling options MD_ROOT # MD is a potential root device #options NFSCLIENT # Network Filesystem Client #options NFSSERVER # Network Filesystem Server #options NFS_ROOT # NFS usable as /, requires NFSCLIENT #options MSDOSFS # MSDOS Filesystem #options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_PART_GPT # GUID Partition Tables. options GEOM_LABEL # Provides labelization options COMPAT_43TTY # BSD 4.3 TTY compat [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options COMPAT_FREEBSD6 # Compatible with FreeBSD6 #options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. options STOP_NMI # Stop CPUS using NMI instead of IPI options AUDIT # Security event auditing #options IPFIREWALL #options IPFIREWALL_DEFAULT_TO_ACCEPT #options IPFIREWALL_FORWARD #options DUMMYNET #options IPFILTER #options IPFILTER_LOG #options ACCEPT_FILTER_DATA #options ACCEPT_FILTER_HTTP options ALTQ options ALTQ_CBQ options ALTQ_RED options ALTQ_RIO options ALTQ_HFSC options ALTQ_CDNR options ALTQ_PRIQ options ALTQ_NOPCC options ALTQ_DEBUG #options NETGRAPH #options NETGRAPH_SPPP #options NETGRAPH_PPP #options NETGRAPH_PPPOE #options NETGRAPH_PPTPGRE options DEVICE_POLLING device atapicam # To make an SMP kernel, the next two lines are needed options SMP # Symmetric MultiProcessor Kernel device apic # I/O APIC # CPU frequency control device cpufreq # Bus support. #device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives #device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI Controllers #device ahb # EISA AHA1742 family #device ahc # AHA2940 and onboard AIC7xxx devices #options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. #device ahd # AHA39320/29320 and onboard AIC79xx devices #options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. #device amd # AMD 53C974 (Tekram DC-390(T)) #device hptiop # Highpoint RocketRaid 3xxx series #device isp # Qlogic family #device ispfw # Firmware for QLogic HBAs- normally a module #device mpt # LSI-Logic MPT-Fusion #device ncr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') #device trm # Tekram DC395U/UW/F DC315U adapters #device adv # Advansys SCSI adapters #device adw # Advansys wide SCSI adapters #device aha # Adaptec 154x SCSI adapters #device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. #device bt # Buslogic/Mylex MultiMaster SCSI adapters #device ncv # NCR 53C500 #device nsp # Workbit Ninja SCSI-3 #device stg # TMC 18C30/18C50 # SCSI peripherals device scbus # SCSI bus (required for SCSI) #device ch # SCSI media changers device da # Direct Access (disks) #device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) #device ses # SCSI Environmental Services (and SAF-TE) # RAID controllers interfaced to the SCSI subsystem #device amr # AMI MegaRAID #device arcmsr # Areca SATA II RAID #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID #device ciss # Compaq Smart RAID 5* #device dpt # DPT Smartcache III, IV - See NOTES for options #device hptmv # Highpoint RocketRAID 182x #device rr232x # Highpoint RocketRAID 232x #device iir # Intel Integrated RAID #device ips # IBM (Adaptec) ServeRAID #device mly # Mylex AcceleRAID/eXtremeRAID #device twa # 3ware 9000 series PATA/SATA RAID # RAID controllers #device aac # Adaptec FSA RAID #device aacp # SCSI passthrough for aac (requires CAM) #device ida # Compaq Smart RAID #device mfi # LSI MegaRAID SAS #device mlx # Mylex DAC960 family #device pst # Promise Supertrak SX6000 #device twe # 3ware ATA RAID # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard #device psm # PS/2 mouse device kbdmux # keyboard multiplexer device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. #device pmtimer # PCCARD (PCMCIA) support # PCMCIA and cardbus bridge support #device cbb # cardbus (yenta) bridge #device pccard # PC Card (16-bit) bus #device cardbus # CardBus (32-bit) bus # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports device uart # Generic UART driver # Parallel port #device ppc #device ppbus # Parallel port bus (required) #device lpt # Printer #device plip # TCP/IP over parallel #device ppi # Parallel port interface device #device vpo # Requires scbus and da # If you've got a "dumb" serial or parallel PCI card that is # supported by the puc(4) glue driver, uncomment the following # line to enable it (connects to sio, uart and/or ppc drivers): #device puc # PCI Ethernet NICs. device de # DEC/Intel DC21x4x (``Tulip'') device em # Intel PRO/1000 adapter Gigabit Ethernet Card device ixgb # Intel PRO/10GbE Ethernet Card device le # AMD Am7900 LANCE and Am79C9xx PCnet device txp # 3Com 3cR990 (``Typhoon'') device vx # 3Com 3c590, 3c595 (``Vortex'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support #device bce # Broadcom BCM5706/BCM5708 Gigabit Ethernet #device bfe # Broadcom BCM440x 10/100 Ethernet #device bge # Broadcom BCM570xx Gigabit Ethernet #device dc # DEC/Intel 21143 and various workalikes #device fxp # Intel EtherExpress PRO/100B (82557, 82558) #device lge # Level 1 LXT1001 gigabit Ethernet #device msk # Marvell/SysKonnect Yukon II Gigabit Ethernet #device nfe # nVidia nForce MCP on-board Ethernet #device nge # NatSemi DP83820 gigabit Ethernet #device nve # nVidia nForce MCP on-board Ethernet Networking #device pcn # AMD Am79C97x PCI 10/100 (precedence over 'le') device re # RealTek 8139C+/8169/8169S/8110S #device rl # RealTek 8129/8139 #device sf # Adaptec AIC-6915 (``Starfire'') #device sis # Silicon Integrated Systems SiS 900/SiS 7016 #device sk # SysKonnect SK-984x & SK-982x gigabit Ethernet #device ste # Sundance ST201 (D-Link DFE-550TX) #device stge # Sundance/Tamarack TC9021 gigabit Ethernet #device ti # Alteon Networks Tigon I/II gigabit Ethernet #device tl # Texas Instruments ThunderLAN #device tx # SMC EtherPower II (83c170 ``EPIC'') #device vge # VIA VT612x gigabit Ethernet #device vr # VIA Rhine, Rhine II #device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. pccard NICs included. #device cs # Crystal Semiconductor CS89x0 NIC # 'device ed' requires 'device miibus' #device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards #device ex # Intel EtherExpress Pro/10 and Pro/10+ #device ep # Etherlink III based cards #device fe # Fujitsu MB8696x based cards #device ie # EtherExpress 8/16, 3C507, StarLAN 10 etc. #device sn # SMC's 9000 series of Ethernet chips #device xe # Xircom pccard Ethernet # Wireless NIC cards #device wlan # 802.11 support #device wlan_wep # 802.11 WEP support #device wlan_ccmp # 802.11 CCMP support #device wlan_tkip # 802.11 TKIP support #device wlan_amrr # AMRR transmit rate control algorithm #device wlan_scan_ap # 802.11 AP mode scanning #device wlan_scan_sta # 802.11 STA mode scanning #device an # Aironet 4500/4800 802.11 wireless NICs. #device ath # Atheros pci/cardbus NIC's #device ath_hal # Atheros HAL (Hardware Access Layer) #device ath_rate_sample # SampleRate tx rate control for ath #device awi # BayStack 660 and others #device ral # Ralink Technology RT2500 wireless NICs. #device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. #device wl # Older non 802.11 Wavelan wireless NIC. # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support #device sl # Kernel SLIP #device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" #device gif # IPv6 and IPv4 tunneling #device faith # IPv6-to-IPv4 relaying (translation) #device firmware # firmware assist module # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard #device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse #device ural # Ralink Technology RT2500USB wireless NICs #device rum # Ralink Technology RT2501USB wireless NICs #device urio # Diamond Rio 500 MP3 player #device uscanner # Scanners # USB Ethernet, requires miibus device aue # ADMtek USB Ethernet device axe # ASIX Electronics USB Ethernet device cdce # Generic USB over Ethernet device cue # CATC USB Ethernet device kue # Kawasaki LSI USB Ethernet device rue # RealTek RTL8150 USB Ethernet # FireWire support #device firewire # FireWire bus code #device sbp # SCSI over FireWire (Requires scbus and da) #device fwe # Ethernet over FireWire (non-standard!) #device fwip # IP over FireWire (RFC 2734,3146) #device dcons # Dumb console driver #device dcons_crom # Configuration ROM for dcons device sound device snd_hda device coretemp --------------090005000506050008010101 Content-Type: text/plain; name="dmesg" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="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-BETA1 #1: Sun Oct 28 10:08:13 ADT 2007 root@amb.kiev.ua:/usr/obj/usr/src/sys/AMB.7.0 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (1805.49-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6f2 Stepping = 2 Features=0xbfebfbff Features2=0xe39d AMD Features=0x20100000 AMD Features2=0x1 Cores per package: 2 real memory = 2147024896 (2047 MB) avail memory = 2087424000 (1990 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 coretemp0: on cpu0 est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 928092806000928 device_attach: est0 attach returned 6 p4tcc0: on cpu0 cpu1: on acpi0 coretemp1: on cpu1 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 928092806000928 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 nvidia0: mem 0xfd000000-0xfdffffff,0xc0000000-0xcfffffff,0xfc000000-0xfcffffff irq 16 at device 0.0 on pci1 nvidia0: [GIANT-LOCKED] nvidia0: [ITHREAD] uhci0: port 0xe000-0xe01f 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 0xe080-0xe09f 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 0xfebff400-0xfebff7ff 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 0xb800-0xb8ff 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:18:f3:74:54:de re0: [FILTER] re0: [FILTER] pcib4: irq 16 at device 28.4 on pci0 pci2: on pcib4 atapci0: port 0xac00-0xac07,0xa880-0xa883,0xa800-0xa807,0xa480-0xa483,0xa400-0xa40f mem 0xfe8fe000-0xfe8fffff irq 16 at device 0.0 on pci2 atapci0: [ITHREAD] 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 0xd800-0xd81f 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 0xd880-0xd89f 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 0xdc00-0xdc1f 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 0xfebff000-0xfebff3ff 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 xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xcc00-0xcc7f mem 0xfeaffc00-0xfeaffc7f irq 23 at device 2.0 on pci5 miibus1: on xl0 ukphy0: PHY 24 on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:01:03:ba:e0:71 xl0: [ITHREAD] isab0: at device 31.0 on pci0 isa0: on isab0 atapci1: port 0xec00-0xec07,0xe880-0xe883,0xe800-0xe807,0xe480-0xe483,0xe400-0xe41f mem 0xfebff800-0xfebfffff irq 19 at device 31.2 on pci0 atapci1: [ITHREAD] atapci1: AHCI Version 01.10 controller with 4 ports detected ata5: on atapci1 ata5: [ITHREAD] ata6: on atapci1 ata6: [ITHREAD] ata7: on atapci1 ata7: port not implemented ata7: [ITHREAD] ata8: on atapci1 ata8: port not implemented ata8: [ITHREAD] ata9: on atapci1 ata9: [ITHREAD] ata10: on atapci1 ata10: [ITHREAD] pci0: at device 31.3 (no driver attached) 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] fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 orm0: at iomem 0xd2000-0xd27ff pnpid ORM0000 on isa0 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata0: [ITHREAD] ata1 at port 0x170-0x177,0x376 irq 15 on isa0 ata1: [ITHREAD] atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] 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 uhub7: on uhub4 uhub7: 4 ports with 4 removable, self powered ukbd0: on uhub7 kbd2 at ukbd0 uhid0: on uhub7 ums0: on uhub7 ums0: 5 buttons and Z dir and a TILT dir. uhid1: on uhub7 uhid2: on uhub7 uhid2: unexpected endpoint device_attach: uhid2 attach returned 6 Timecounters tick every 1.000 msec acd0: DVDR at ata4-slave UDMA33 ad10: 305245MB at ata5-master SATA300 ad12: 381554MB at ata6-master SATA150 pcm0: pcm0: acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01 acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 sks=0x40 0x00 0x01 SMP: AP CPU #1 Launched! cd0 at ata4 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from ufs:/dev/ad10s1a WARNING: ZFS is considered to be an experimental feature in FreeBSD. ZFS filesystem version 6 ZFS storage pool version 6 re0: link state changed to UP altq: emulate 256000000Hz cpu clock xl0: promiscuous mode enabled xl0: promiscuous mode disabled xl0: promiscuous mode enabled xl0: promiscuous mode disabled xl0: promiscuous mode enabled xl0: promiscuous mode disabled xl0: promiscuous mode enabled xl0: promiscuous mode disabled --------------090005000506050008010101-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 17:22:44 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E669416A468; Sun, 28 Oct 2007 17:22:44 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.freebsd.org (Postfix) with ESMTP id 9749813C4AC; Sun, 28 Oct 2007 17:22:44 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1ImBHh-000OiV-Mc; Sun, 28 Oct 2007 18:46:45 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Jeremy Chadwick In-reply-to: <20071028164152.GA7516@eos.sc1.parodius.com> References: <47240A15.8080305@charter.net> <20071028074248.GA1511@haakonia.hitnet.RWTH-Aachen.DE> <4724BAD9.7000400@charter.net> <20071028164152.GA7516@eos.sc1.parodius.com> Comments: In-reply-to Jeremy Chadwick message dated "Sun, 28 Oct 2007 09:41:52 -0700." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 28 Oct 2007 18:46:45 +0200 From: Danny Braniss Message-ID: Cc: Andrew Lankford , stable@freebsd.org, current@freebsd.org Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 17:22:45 -0000 > On Sun, Oct 28, 2007 at 12:37:45PM -0400, Andrew Lankford wrote: > > Thanks for replying, but once again I've miscommunicated the issue. I > > meant that MAKEDEV.8 is in /usr/src/share/man/man8/, and the > > modification time is Oct 13th, recent, which suggests to me that it's still > > in the 7.0-BETA1 cvs tree. > > And you're very much correct: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/share/man/man8/MAKEDEV.8 how about reading what ity says? it might be very educational :-) NAME MAKEDEV -- old script for creating device nodes DESCRIPTION The MAKEDEV script was deprecated by devfs(5) and removed from FreeBSD after devfs(5) became mandatory. From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 17:47:16 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CD6E16A417 for ; Sun, 28 Oct 2007 17:47:16 +0000 (UTC) (envelope-from peo@intersonic.se) Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com [212.247.8.98]) by mx1.freebsd.org (Postfix) with ESMTP id 24F7B13C4B2 for ; Sun, 28 Oct 2007 17:47:16 +0000 (UTC) (envelope-from peo@intersonic.se) X-Virus-Scanned: amavisd-new at inter-sonic.com Message-ID: <4724CB1F.7080202@intersonic.se> Date: Sun, 28 Oct 2007 18:47:11 +0100 From: Per olof Ljungmark Organization: Intersonic AB User-Agent: Thunderbird 2.0.0.6 (X11/20071009) MIME-Version: 1.0 To: Andrew Birukov References: <4724BFD4.2040406@amb.kiev.ua> In-Reply-To: <4724BFD4.2040406@amb.kiev.ua> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: pf broken in 7.0-BETA1 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 17:47:16 -0000 Andrew Birukov wrote: > > This problem is affected 7.0 only. > pf rools witch tos in FreeBSD-6.2 work properly. Just a guess, could this be the problem? "Warning: When browsing the pf user's guide, please keep in mind that different versions of FreeBSD contain different versions of pf." I believe pf in 7 is based on OpenBSD 4.1. --per From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 18:37:55 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 158EE16A46C for ; Sun, 28 Oct 2007 18:37:55 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id A202313C4A6 for ; Sun, 28 Oct 2007 18:37:53 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.13.8/jtpda-5.4) with ESMTP id l9SIRRdC054262 for ; Sun, 28 Oct 2007 19:27:27 +0100 (CET) X-Ids: 168 Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.13.3/jtpda-5.2) with ESMTP id l9SIRQDf020969 for ; Sun, 28 Oct 2007 19:27:26 +0100 (MET) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.13.3/8.13.1/Submit) id l9SIRQa4020966; Sun, 28 Oct 2007 19:27:26 +0100 (MET) (envelope-from arno) To: current@freebsd.org From: "Arno J. Klaassen" Date: 28 Oct 2007 19:27:25 +0100 Message-ID: Lines: 38 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (shiva.jussieu.fr [134.157.0.168]); Sun, 28 Oct 2007 19:27:27 +0100 (CET) X-Virus-Scanned: ClamAV 0.88.7/4616/Sun Oct 28 18:25:58 2007 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at shiva.jussieu.fr with ID 4724D48F.001 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Cc: Subject: 2nd nfe interface not showing up on Tyan S2895 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 18:37:55 -0000 Hi, I'm playing with RELENG_7 on a spare S2895 I have around and have difficulties with the ethernet interfaces : - nfe0 shows up and works OK under 1Gbps (at least for buildworlds etc over NFS) but under 100Mbps it says : install kernel: nfe0: tx v2 error 0x6004 install kernel: nfe0: tx v2 error 0x6204 - more serious, this board is supposed to have two of them (enabled in BIOS as 'Slave Device') but only one of them shows up at boot (and in pciconf -vl) According to the manual : "Two IEEE 802.3 Nvidia MAC 1000/100/10 Ethernet (First from PRO 2200, Second from PRO 2050)" so apparently not connected to the same chipset, and according to the block diagram of MB-architecture, the "PRO 2050" should be connected directly to the second CPU. Does anyone have a hint how to get that second interface at least to show up? Thanx in advance and feel free to contact me for more detailed info. Regards, Arno -- Arno J. Klaassen SCITO S.A. 8 rue des Haies F-75020 Paris, France http://scito.com From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 20:31:30 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F4D216A41B for ; Sun, 28 Oct 2007 20:31:30 +0000 (UTC) (envelope-from kps@ucsb.edu) Received: from smtp.ucsb.edu (smtp.ucsb.edu [128.111.24.45]) by mx1.freebsd.org (Postfix) with ESMTP id 78D6613C48D for ; Sun, 28 Oct 2007 20:31:30 +0000 (UTC) (envelope-from kps@ucsb.edu) Received: from splat.oit.ucsb.edu ([128.111.12.20]) by smtp.ucsb.edu with esmtpsa TLSv1:AES256-SHA:256 id 1ImEbe-00037t-3i; Sun, 28 Oct 2007 13:19:34 -0700 From: Kevin Schmidt Organization: University of California, Santa Barbara To: Erik Osterholm Date: Sun, 28 Oct 2007 13:19:32 -0700 User-Agent: KMail/1.9.7 References: <48344.172.16.9.1.1192472836.squirrel@www.xtra-net.be> <1193342809.30674.3.camel@localhost> <20071025201857.GC43606@aleph.cepheid.org> In-Reply-To: <20071025201857.GC43606@aleph.cepheid.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200710281319.33309.kps@ucsb.edu> Cc: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= , Vincent Blondel , freebsd-current@freebsd.org, Harrison Grundy Subject: Re: Xen Status : FreeBSD-current as Dom/U. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kps@ucsb.edu List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 20:31:30 -0000 On Thursday 25 October 2007, Erik Osterholm wrote: > On Fri, Oct 26, 2007 at 05:06:49AM +0900, Harrison Grundy wrote: > > On Thu, 2007-10-25 at 12:05 +0200, Dag-Erling Sm=F8rgrav wrote: > > > "Vincent Blondel" writes: > > > > Can somebody indicate me what settings I have to include in > > > > GENERIC config file so to compile a Xen Dom/U FreeBSD kernel. > > > > > > FreeBSD currently does not support running under Xen. > > > > I just thought I'd note that you can use Xen with FreeBSD if your > > processor supports hardware virtualization, I believe. > > I have yet to hear any independant verification of this. Anyone > actually running FreeBSD as a domU with hardware virtualization? =46WIW, I've tried FreeBSD as an HVM guest on several Linux distros as=20 Dom0, Xen 3.0 (3.0.3, 3.0.4) and 3.1 (3.1.0), using Xen packages and=20 manual compiles. Linux distros included Ubuntu 7.04 and Debian 4. =20 =46reeBSD 6.2 and 7.0 -- release and snapshots -- consistently fail to=20 boot with a looping "BTX halted" and register dump. If there's a way=20 to install stock FreeBSD under Xen HVM, I haven't seen it. Without=20 saying whether this is properly a Xen problem or FBSD BTX problem, my=20 guess is this type of installation will not work until there are BTX=20 changes. =2D-=20 Kevin Schmidt Office of Information Technology University of California, Santa Barbara North Hall 2124 Santa Barbara, CA 93106-3201 805-893-7779 805-893-5051 FAX kps@ucsb.edu From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 20:44:45 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6C80016A417 for ; Sun, 28 Oct 2007 20:44:45 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by mx1.freebsd.org (Postfix) with ESMTP id 3977713C49D for ; Sun, 28 Oct 2007 20:44:45 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so1881824waf for ; Sun, 28 Oct 2007 13:44:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; 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=56Pn2uK8czl+YO+sFUW1R69Fr74pVXY/yKjEaBdQsi0=; b=GTYBShnRd6mdWttpg7UtQNqXvYa7n/UTgUco9hzjyFWAI5IhbQrS0e3IKp8bxPUowyw1EXYeQabUNAM0AN/Rli1wy8U4Lx1RQP8xGYB2MKYeVX37gWy9fG4+GPqs4lnFiukYpgs24072OZ2WulNBvcrAbfX6vfo7BrzVzjhE2SI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=cozxdvDtwU08hOOJXN4tAhrHQv4+9ZErVngO5DmKorcd8BMXGT3TC5YXgSj6RVYCECpm0rf7wYyKAA/ITnOuZShSIzO1EgGlgFPLyQYivonmgm857tK94ACuVX5pwiEjFnaFfnNqXtH5E+I+2oGajDzDMe4dHr2mb36lMvEx5ag= Received: by 10.115.15.1 with SMTP id s1mr3499466wai.1193604284831; Sun, 28 Oct 2007 13:44:44 -0700 (PDT) Received: by 10.114.13.15 with HTTP; Sun, 28 Oct 2007 13:44:44 -0700 (PDT) Message-ID: Date: Sun, 28 Oct 2007 13:44:44 -0700 From: "Kip Macy" To: kps@ucsb.edu In-Reply-To: <200710281319.33309.kps@ucsb.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <48344.172.16.9.1.1192472836.squirrel@www.xtra-net.be> <1193342809.30674.3.camel@localhost> <20071025201857.GC43606@aleph.cepheid.org> <200710281319.33309.kps@ucsb.edu> Cc: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= , Vincent Blondel , freebsd-current@freebsd.org, Harrison Grundy , Erik Osterholm Subject: Re: Xen Status : FreeBSD-current as Dom/U. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 20:44:45 -0000 On 10/28/07, Kevin Schmidt wrote: > On Thursday 25 October 2007, Erik Osterholm wrote: > > On Fri, Oct 26, 2007 at 05:06:49AM +0900, Harrison Grundy wrote: > > > On Thu, 2007-10-25 at 12:05 +0200, Dag-Erling Sm=F8rgrav wrote: > > > > "Vincent Blondel" writes: > > > > > Can somebody indicate me what settings I have to include in > > > > > GENERIC config file so to compile a Xen Dom/U FreeBSD kernel. > > > > > > > > FreeBSD currently does not support running under Xen. > > > > > > I just thought I'd note that you can use Xen with FreeBSD if your > > > processor supports hardware virtualization, I believe. > > > > I have yet to hear any independant verification of this. Anyone > > actually running FreeBSD as a domU with hardware virtualization? > > FWIW, I've tried FreeBSD as an HVM guest on several Linux distros as > Dom0, Xen 3.0 (3.0.3, 3.0.4) and 3.1 (3.1.0), using Xen packages and > manual compiles. Linux distros included Ubuntu 7.04 and Debian 4. > FreeBSD 6.2 and 7.0 -- release and snapshots -- consistently fail to > boot with a looping "BTX halted" and register dump. If there's a way > to install stock FreeBSD under Xen HVM, I haven't seen it. Without > saying whether this is properly a Xen problem or FBSD BTX problem, my > guess is this type of installation will not work until there are BTX > changes. It is obviously inadequate emulation on HVM's part. It would be interesting to see how this fared on SVM, but on VT-x one needs to emulate real mode and what exists there now is somewhat limited. This worked very briefly a few years ago. HVM's primary target is running windows. -Kip From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 23:14:27 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5B7116A419 for ; Sun, 28 Oct 2007 23:14:27 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: from bsd.ultra-secure.de (bsd.ultra-secure.de [62.146.20.26]) by mx1.freebsd.org (Postfix) with ESMTP id 3275813C480 for ; Sun, 28 Oct 2007 23:14:26 +0000 (UTC) (envelope-from rainer@ultra-secure.de) Received: (qmail 23116 invoked by uid 89); 28 Oct 2007 23:25:23 -0000 Received: by simscan 1.1.0 ppid: 23090, pid: 23102, t: 3.9009s scanners: attach: 1.1.0 clamav: 0.88.7/m:43/d:3620 spam: 3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on bsd.ultra-secure.de X-Spam-Level: X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00, FORGED_RCVD_HELO autolearn=ham version=3.1.7 Received: from unknown (HELO lbe8010.example.net) (rainer@ultra-secure.de@217.71.83.52) by bsd.ultra-secure.de with (DHE-RSA-AES256-SHA encrypted) SMTP; 28 Oct 2007 23:25:19 -0000 Message-ID: <472517C8.5090606@ultra-secure.de> Date: Mon, 29 Oct 2007 00:14:16 +0100 From: Rainer Duffner User-Agent: Thunderbird 2.0.0.6 (X11/20071017) MIME-Version: 1.0 To: Sam Leffler References: <47209EB2.5080109@palisadesys.com> <200710251911.24346.shoesoft@gmx.net> <4720D849.2010409@errno.com> In-Reply-To: <4720D849.2010409@errno.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: iwi0 firmware error on Dell Inspiron 6000 w/ Intel PRO/Wireless 2200BG X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 23:14:27 -0000 Sam Leffler wrote: > I just tested this on a t42 w/ 2200 card and it worked for me. Try > setting debug.iwi to something like 2 or 5 and collect a log. The > firmware is very finnicky and getting it to integrate w/ wpa_supplicant > was a challenge. Hi, I also have this problem now, with 7-BETA1. none4@pci0:1:13:0: class=0x028000 card=0x27028086 chip=0x42208086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/Wireless 2200BG Network Connection' class = network Enabling these debug-options make iwi produce lots of these messages: sending command idx=6 type=8 len=8 Scan request: index 2275 dwell 200/200/200 Scan 1 2.4GHz channels: 3/BDIR sending command idx=7 type=26 len=96 received frame len=109 chan=3 rssi=20 rssi_dbm=47 Scan of channel 2422 complete (3) Scan completed (1, 1) exit FW state 4 enter FW state 4 sending command idx=8 type=8 len=8 Scan request: index 2276 dwell 200/200/200 Scan 1 2.4GHz channels: 4/BDIR sending command idx=9 type=26 len=96 Scan of channel 2427 complete (4) Scan completed (1, 1) exit FW state 4 enter FW state 4 sending command idx=10 type=8 len=8 Scan request: index 2277 dwell 200/200/200 Scan 1 2.4GHz channels: 5/BDIR sending command idx=11 type=26 len=96 received frame len=103 chan=5 rssi=23 rssi_dbm=61 Scan of channel 2432 complete (5) Scan completed (1, 1) exit FW state 4 enter FW state 4 sending command idx=12 type=8 len=8 Scan request: index 2278 dwell 200/200/200 Scan 1 2.4GHz channels: 8/BDIR sending command idx=13 type=26 len=96 received frame len=103 chan=8 rssi=24 rssi_dbm=81 received frame len=122 chan=8 rssi=20 rssi_dbm=44 received frame len=109 chan=8 rssi=24 rssi_dbm=85 received frame len=122 chan=8 rssi=20 rssi_dbm=44 received frame len=109 chan=8 rssi=24 rssi_dbm=85 Scan of channel 2447 complete (8) Scan completed (1, 1) exit FW state 4 enter FW state 4 sending command idx=14 type=8 len=8 Scan request: index 2279 dwell 200/200/200 Scan 1 2.4GHz channels: 9/BDIR sending command idx=15 type=26 len=96 received frame len=103 chan=9 rssi=24 rssi_dbm=85 received frame len=109 chan=9 rssi=24 rssi_dbm=81 received frame len=109 chan=9 rssi=24 rssi_dbm=85 Scan of channel 2452 complete (9) Scan completed (1, 1) exit FW state 4 enter FW state 4 sending command idx=0 type=8 len=8 Scan request: index 2280 dwell 200/200/200 Scan 1 2.4GHz channels: 10/BDIR sending command idx=1 type=26 len=96 received frame len=103 chan=10 rssi=24 rssi_dbm=85 received frame len=109 chan=10 rssi=24 rssi_dbm=81 received frame len=109 chan=10 rssi=24 rssi_dbm=85 Scan of channel 2457 complete (10) Scan completed (1, 1) exit FW state 4 enter FW state 4 sending command idx=2 type=8 len=8 Scan request: index 2281 dwell 200/200/200 Scan 1 2.4GHz channels: 12/BDIR sending command idx=3 type=26 len=96 received frame len=103 chan=12 rssi=24 rssi_dbm=79 received frame len=109 chan=12 rssi=24 rssi_dbm=79 Scan of channel 2467 complete (12) Scan completed (1, 1) exit FW state 4 enter FW state 4 sending command idx=4 type=8 len=8 received frame len=109 chan=12 rssi=24 rssi_dbm=79 Scan request: index 2282 dwell 200/200/200 Scan 1 2.4GHz channels: 14/BDIR sending command idx=5 type=26 len=96 Scan of channel 2484 complete (14) Scan completed (1, 1) exit FW state 4 enter FW state 4 sending command idx=6 type=8 len=8 Scan request: index 2283 dwell 200/200/200 Scan 1 2.4GHz channels: 1/BDIR sending command idx=7 type=26 len=96 Scan of channel 2412 complete (1) Scan completed (1, 1) exit FW state 4 enter FW state 4 sending command idx=8 type=8 len=8 Scan request: index 2284 dwell 200/200/200 Scan 1 2.4GHz channels: 6/BDIR sending command idx=9 type=26 len=96 received frame len=103 chan=6 rssi=23 rssi_dbm=80 received frame len=122 chan=6 rssi=21 rssi_dbm=44 received frame len=109 chan=6 rssi=24 rssi_dbm=79 iwi_newstate: SCAN -> INIT flags 0x20 iwi_newstate: INIT -> INIT flags 0x0 WPA supplicant seems to start automatically, when I unload and load if_iwi. This did work with 6.2 very nicely. What else can I do? Best Regards, Rainer From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 00:10:45 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B8BFF16A46C for ; Mon, 29 Oct 2007 00:10:45 +0000 (UTC) (envelope-from rodperson@verizon.net) Received: from vms040pub.verizon.net (vms040pub.verizon.net [206.46.252.40]) by mx1.freebsd.org (Postfix) with ESMTP id 6B7E613C4B9 for ; Mon, 29 Oct 2007 00:10:45 +0000 (UTC) (envelope-from rodperson@verizon.net) Received: from atomizer.opensourcebeef.net ([72.77.117.239]) by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JQN00HJ2CHFFH96@vms040.mailsrvcs.net> for current@freebsd.org; Sun, 28 Oct 2007 19:10:28 -0500 (CDT) Date: Sun, 28 Oct 2007 20:05:38 -0400 From: Rod Person In-reply-to: To: "Arno J. Klaassen" Message-id: <20071028200538.2181ba87@atomizer.opensourcebeef.net> Organization: Open Source Beef MIME-version: 1.0 X-Mailer: Claws Mail 3.0.2 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: base64 References: Cc: current@freebsd.org Subject: Re: 2nd nfe interface not showing up on Tyan S2895 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 00:10:45 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBMQ0KDQpPbiBTdW4s IDI4IE9jdCAyMDA3IDE5OjI3OjI1ICswMTAwDQoiQXJubyBKLiBLbGFhc3NlbiIgPGFybm9AaGVo by5zbnYuanVzc2lldS5mcj4gd3JvdGU6DQoNCj4gDQo+ICAtIG1vcmUgc2VyaW91cywgdGhpcyBi b2FyZCBpcyBzdXBwb3NlZCB0byBoYXZlIHR3byBvZiB0aGVtDQo+ICAgIChlbmFibGVkIGluIEJJ T1MgYXMgJ1NsYXZlIERldmljZScpIGJ1dCBvbmx5IG9uZSBvZiB0aGVtDQo+ICAgIHNob3dzIHVw IGF0IGJvb3QgKGFuZCBpbiBwY2ljb25mIC12bCkNCg0KIA0KPiBEb2VzIGFueW9uZSBoYXZlIGEg aGludCBob3cgdG8gZ2V0IHRoYXQgc2Vjb25kIGludGVyZmFjZSBhdCBsZWFzdA0KPiB0byBzaG93 IHVwPyBUaGFueCBpbiBhZHZhbmNlIGFuZCBmZWVsIGZyZWUgdG8gY29udGFjdCBtZSBmb3INCj4g bW9yZSBkZXRhaWxlZCBpbmZvLg0KPiANCg0KSSBoYXZlIGFuIFMyODk1IHdpdGggdGhlIGR1YWwg R2lnYWJpdCBuaWNzLiBJJ3ZlIGJlZW4gcnVubmluZyBDVVJSRU5UDQpzaW5jZSBGZWIgMjAwNiBh bmQgbmV2ZXIgaGFkIGEgcHJvYmxlbSBnZXR0aW5nIGJvdGggbmljcyB0byBzaG93IHVwIGFzDQps b25nIGFzIHRoZSAybmQgaXMgZW5hYmxlZCBpbiB0aGUgQklPUy4gVGhlIG9ubHkgcHJvYmxlbXMg SSd2ZSBoYWQgaXMNCndpdGggdGhlIEZpcmV3aXJlIHN1cHBvcnQsIHdoaWNoIHdvcmtlZCBmb3Ig YSBtb21lbnQgdGhlbiBjYXVzZSBhbGwNCmtpbmRzIG9mIHByb2JsZW1zLiBBcmUgeW91IHN1cmUg dGhhdCB0aGUgMm5kIG5pYyBpcyBnb29kPw0KDQoNCi0gLS0gDQpSb2QNCg0KaHR0cDovL3JvZGRp ZXJvZC5ob21ldW5peC5uZXQ6ODA4MA0KLS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0NClZl cnNpb246IEdudVBHIHYxLjQuNyAoRnJlZUJTRCkNCg0KaUQ4REJRRkhKU1BTWmU2QjdCMkltcHNS QXBCZUFKOWpGYkdxblcwcjlCdi9COXlmOWw2UEV3ZkR2Z0Nna1ZZZQ0KTWoyNkpmZWVWUVRydW16 YzlrQm9tS289DQo9QXVSbg0KLS0tLS1FTkQgUEdQIFNJR05BVFVSRS0tLS0tDQo= From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 00:22:11 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB6B816A417 for ; Mon, 29 Oct 2007 00:22:11 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id 6347413C4A5 for ; Mon, 29 Oct 2007 00:22:11 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.13.8/jtpda-5.4) with ESMTP id l9T0M93N060791 ; Mon, 29 Oct 2007 01:22:10 +0100 (CET) X-Ids: 166 Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.13.3/jtpda-5.2) with ESMTP id l9T0M8Ia022016 ; Mon, 29 Oct 2007 01:22:08 +0100 (MET) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.13.3/8.13.1/Submit) id l9T0M88f022013; Mon, 29 Oct 2007 01:22:08 +0100 (MET) (envelope-from arno) To: Rod Person References: <20071028200538.2181ba87@atomizer.opensourcebeef.net> From: "Arno J. Klaassen" Date: 29 Oct 2007 01:22:08 +0100 In-Reply-To: <20071028200538.2181ba87@atomizer.opensourcebeef.net> Message-ID: Lines: 57 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (shiva.jussieu.fr [134.157.0.166]); Mon, 29 Oct 2007 01:22:10 +0100 (CET) X-Virus-Scanned: ClamAV 0.88.7/4616/Sun Oct 28 18:25:58 2007 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at shiva.jussieu.fr with ID 472527B1.002 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Cc: current@freebsd.org Subject: Re: 2nd nfe interface not showing up on Tyan S2895 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 00:22:11 -0000 Rod Person writes: > On Sun, 28 Oct 2007 19:27:25 +0100 > "Arno J. Klaassen" wrote: > > > > > - more serious, this board is supposed to have two of them > > (enabled in BIOS as 'Slave Device') but only one of them > > shows up at boot (and in pciconf -vl) > > > > Does anyone have a hint how to get that second interface at least > > to show up? Thanx in advance and feel free to contact me for > > more detailed info. > > > > I have an S2895 with the dual Gigabit nics. I've been running CURRENT > since Feb 2006 and never had a problem getting both nics to show up as > long as the 2nd is enabled in the BIOS. The only problems I've had is > with the Firewire support, which worked for a moment then cause all > kinds of problems. Are you sure that the 2nd nic is good? No : I just bought the board a couple of days ago and did not try anything else than fbsd on it. That said, I looked again at the Block Diagram in the manual and wonder whether they mean "second physical CPU"? I just have one Opteron 285 installed for now (ordered a second one). Do you have physically two CPUs installed? I have both interfaces enabled in the BIOS (and playing with the "MAC Bridge" setting does not help (but I do not understand what that setting is supposed to do...) Thanx for your help Regards, Arno > > -- > Rod > > http://roddierod.homeunix.net:8080 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Arno J. Klaassen SCITO S.A. 8 rue des Haies F-75020 Paris, France http://scito.com From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 00:31:20 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C77E816A581 for ; Mon, 29 Oct 2007 00:31:20 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id 4E62613C4A7 for ; Mon, 29 Oct 2007 00:31:20 +0000 (UTC) (envelope-from erikt@midgard.homeip.net) Received: from c83-253-25-183.bredband.comhem.se ([83.253.25.183]:61685 helo=falcon.midgard.homeip.net) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1ImIXH-0001G8-4Z for current@freebsd.org; Mon, 29 Oct 2007 01:31:19 +0100 Received: (qmail 10041 invoked from network); 29 Oct 2007 01:31:16 +0100 Received: from owl.midgard.homeip.net (10.1.5.7) by falcon.midgard.homeip.net with ESMTP; 29 Oct 2007 01:31:16 +0100 Received: (qmail 23362 invoked by uid 1001); 29 Oct 2007 01:31:16 +0100 Date: Mon, 29 Oct 2007 01:31:16 +0100 From: Erik Trulsson To: "Arno J. Klaassen" Message-ID: <20071029003116.GA23339@owl.midgard.homeip.net> Mail-Followup-To: "Arno J. Klaassen" , Rod Person , current@freebsd.org References: <20071028200538.2181ba87@atomizer.opensourcebeef.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) X-Originating-IP: 83.253.25.183 X-Scan-Result: No virus found in message 1ImIXH-0001G8-4Z. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1ImIXH-0001G8-4Z db775907b586168b0c1d3689ba47d3a3 Cc: Rod Person , current@freebsd.org Subject: Re: 2nd nfe interface not showing up on Tyan S2895 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 00:31:20 -0000 On Mon, Oct 29, 2007 at 01:22:08AM +0100, Arno J. Klaassen wrote: > Rod Person writes: > > > On Sun, 28 Oct 2007 19:27:25 +0100 > > "Arno J. Klaassen" wrote: > > > > > > > > - more serious, this board is supposed to have two of them > > > (enabled in BIOS as 'Slave Device') but only one of them > > > shows up at boot (and in pciconf -vl) > > > > > > > Does anyone have a hint how to get that second interface at least > > > to show up? Thanx in advance and feel free to contact me for > > > more detailed info. > > > > > > > I have an S2895 with the dual Gigabit nics. I've been running CURRENT > > since Feb 2006 and never had a problem getting both nics to show up as > > long as the 2nd is enabled in the BIOS. The only problems I've had is > > with the Firewire support, which worked for a moment then cause all > > kinds of problems. Are you sure that the 2nd nic is good? > > No : I just bought the board a couple of days ago and did not > try anything else than fbsd on it. > > That said, I looked again at the Block Diagram in the manual and > wonder whether they mean "second physical CPU"? I just > have one Opteron 285 installed for now (ordered a second one). > Do you have physically two CPUs installed? That would do it. If you only have one CPU, then any device that should be connected to the second CPU will not work, since those devices are connected to the HyperTransport links the CPU provides - and without the CPU in place those devices are simply not connected to the rest of the board. > > I have both interfaces enabled in the BIOS (and playing with the > "MAC Bridge" setting does not help (but I do not understand what > that setting is supposed to do...) > > Thanx for your help > > Regards, Arno > -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 00:39:47 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C013C16A41A for ; Mon, 29 Oct 2007 00:39:47 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id 5821113C4C6 for ; Mon, 29 Oct 2007 00:39:47 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.13.8/jtpda-5.4) with ESMTP id l9T0dkNG082921 ; Mon, 29 Oct 2007 01:39:46 +0100 (CET) X-Ids: 165 Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.13.3/jtpda-5.2) with ESMTP id l9T0djOx022092 ; Mon, 29 Oct 2007 01:39:45 +0100 (MET) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.13.3/8.13.1/Submit) id l9T0dijM022089; Mon, 29 Oct 2007 01:39:44 +0100 (MET) (envelope-from arno) To: Erik Trulsson References: <20071028200538.2181ba87@atomizer.opensourcebeef.net> <20071029003116.GA23339@owl.midgard.homeip.net> From: "Arno J. Klaassen" Date: 29 Oct 2007 01:39:44 +0100 In-Reply-To: <20071029003116.GA23339@owl.midgard.homeip.net> Message-ID: Lines: 43 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (shiva.jussieu.fr [134.157.0.165]); Mon, 29 Oct 2007 01:39:46 +0100 (CET) X-Virus-Scanned: ClamAV 0.88.7/4616/Sun Oct 28 18:25:58 2007 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at shiva.jussieu.fr with ID 47252BD2.001 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Cc: current@freebsd.org Subject: Re: 2nd nfe interface not showing up on Tyan S2895 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 00:39:47 -0000 Erik Trulsson writes: > On Mon, Oct 29, 2007 at 01:22:08AM +0100, Arno J. Klaassen wrote: > > Rod Person writes: > > > > > On Sun, 28 Oct 2007 19:27:25 +0100 > > > "Arno J. Klaassen" wrote: > > > > > > > > > > > - more serious, this board is supposed to have two of them > > > > (enabled in BIOS as 'Slave Device') but only one of them > > > > shows up at boot (and in pciconf -vl) > > > > > > > > > > Does anyone have a hint how to get that second interface at least > > > > to show up? Thanx in advance and feel free to contact me for > > > > more detailed info. > > > > > > > > > > I have an S2895 with the dual Gigabit nics. I've been running CURRENT > > > since Feb 2006 and never had a problem getting both nics to show up as > > > long as the 2nd is enabled in the BIOS. The only problems I've had is > > > with the Firewire support, which worked for a moment then cause all > > > kinds of problems. Are you sure that the 2nd nic is good? > > > > No : I just bought the board a couple of days ago and did not > > try anything else than fbsd on it. > > > > That said, I looked again at the Block Diagram in the manual and > > wonder whether they mean "second physical CPU"? I just > > have one Opteron 285 installed for now (ordered a second one). > > Do you have physically two CPUs installed? > > That would do it. If you only have one CPU, then any device that should be > connected to the second CPU will not work, since those devices are connected > to the HyperTransport links the CPU provides - and without the CPU in place > those devices are simply not connected to the rest of the board. OK, I see. Thanx again for you help. Regards, Arno From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 14:48:33 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FCB316A41A for ; Sun, 28 Oct 2007 14:48:33 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by mx1.freebsd.org (Postfix) with ESMTP id CD67513C4A8 for ; Sun, 28 Oct 2007 14:48:31 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so2431179pyb for ; Sun, 28 Oct 2007 07:48:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=AOUm31BPO9HkUL6JjsVIreDedtF8ehrVa59G5HviyI8=; b=CXdzWypo/JtjHb1DUoMb3wih/SC1+/BIaAqU2tkyfGlc5cg5V6CrkX8XYWl/7xXzfAhTRbeOw3hQjLvkg49tuQvB0NATSwJo8z/KReePBXx2ivSWiiBsl600sluNMkvsdXcOnR+gcYvDxSi8yb+PZyLDP+hCXtzgBtgz3UIAz80= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=Mmwt3B2SBTLnX7aNMlyQGQWzEWLIijdS+Vq1S0goMMdRLuqxrkQHB5mCHvOmZfVpS0W9AJpwo/EHi1jMDnkTLqXOeU1E6uJ4i31gecVShxv4IT9jaKTn1OYHMWOXWM1PpO/y+9Aznk+pbGayAYSQ0ld3ahZyXeLU9Do+qxh2LZA= Received: by 10.35.33.15 with SMTP id l15mr6159199pyj.1193581223020; Sun, 28 Oct 2007 07:20:23 -0700 (PDT) Received: by 10.35.108.9 with HTTP; Sun, 28 Oct 2007 07:20:22 -0700 (PDT) Message-ID: Date: Sun, 28 Oct 2007 14:20:22 +0000 From: "Rui Paulo" Sender: rpaulo@gmail.com To: "Julian Elischer" In-Reply-To: <47241E9C.7000605@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <47241E9C.7000605@elischer.org> X-Google-Sender-Auth: 5c71be71b27cd13e X-Mailman-Approved-At: Mon, 29 Oct 2007 01:50:29 +0000 Cc: FreeBSD Current Subject: Re: learned something about coretemp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 14:48:33 -0000 On 10/28/07, Julian Elischer wrote: > never kldload it on an 8 year old system. > > *bewm* > > I presume that my 8 YO inspiron 7500 doesn't have whatever is needed, > but, "*Bewm*" is probably a less than optimal reaction. That has been reported in the past. It's Intel's fault, not ours. The spec says that if you issue a CPUID you should be able to tell if the CPU has the temperature sensors regardless of the CPU model, but on old systems these CPUID call "returns true". -- Rui Paulo From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 16:37:54 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B81B16A41A; Sun, 28 Oct 2007 16:37:54 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from mtao04.charter.net (mtao04.charter.net [209.225.8.178]) by mx1.freebsd.org (Postfix) with ESMTP id 99DB413C4CA; Sun, 28 Oct 2007 16:37:52 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from aa04.charter.net ([10.20.200.156]) by mtao04.charter.net (InterMail vM.7.08.02.00 201-2186-121-20061213) with ESMTP id <20071028163747.EBQ23660.mtao04.charter.net@aa04.charter.net>; Sun, 28 Oct 2007 12:37:47 -0400 Received: from [192.168.15.101] (really [75.138.219.8]) by aa04.charter.net with ESMTP id <20071028163747.GVNO1254.aa04.charter.net@[192.168.15.101]>; Sun, 28 Oct 2007 12:37:47 -0400 Message-ID: <4724BAD9.7000400@charter.net> Date: Sun, 28 Oct 2007 12:37:45 -0400 From: Andrew Lankford User-Agent: Thunderbird 2.0.0.6 (X11/20071017) MIME-Version: 1.0 References: <47240A15.8080305@charter.net> <20071028074248.GA1511@haakonia.hitnet.RWTH-Aachen.DE> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Chzlrs: 0 X-Mailman-Approved-At: Mon, 29 Oct 2007 01:50:29 +0000 Cc: stable@freebsd.org, current@freebsd.org Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 16:37:54 -0000 Thanks for replying, but once again I've miscommunicated the issue. I meant that MAKEDEV.8 is in /usr/src/share/man/man8/, and the modification time is Oct 13th, recent, which suggests to me that it's still in the 7.0-BETA1 cvs tree. Andrew Lankford Doug Barton wrote: > On Sun, 28 Oct 2007, Christian Brueffer wrote: > >> On Sun, Oct 28, 2007 at 12:03:33AM -0400, Andrew Lankford wrote: >>> I just noticed that /usr/share/man/man8/MAKEDEV.8 is still in the >>> FreeBSD-7 tree. Is this intentional? It still says that MAKEDEV is >>> located in /dev and mentions MAKEDEV.local as well. >>> >> >> Could it be that you have updated this machine from RELENG_4? The fact >> that the file you're referring to has no .gz extention show that it's >> stale, manpages have been compressed for some time now. > > A simple way to make sure you don't get bitten by this is to 'rm -r > /usr/share/man' right before you do 'make installworld'. (Or you can mv > it if you're paranoid, I've been deleting it for a long time now and > it's never bitten me.) > > hth, > > Doug > From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 16:50:28 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5406A16A41B; Sun, 28 Oct 2007 16:50:28 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from mtai04.charter.net (mtai04.charter.net [209.225.8.184]) by mx1.freebsd.org (Postfix) with ESMTP id E04BF13C491; Sun, 28 Oct 2007 16:50:26 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from aa04.charter.net ([10.20.200.156]) by mtai04.charter.net (InterMail vM.7.08.02.00 201-2186-121-20061213) with ESMTP id <20071028165025.AYI12338.mtai04.charter.net@aa04.charter.net>; Sun, 28 Oct 2007 12:50:25 -0400 Received: from [192.168.15.101] (really [75.138.219.8]) by aa04.charter.net with ESMTP id <20071028165025.HBBD1254.aa04.charter.net@[192.168.15.101]>; Sun, 28 Oct 2007 12:50:25 -0400 Message-ID: <4724BDD0.1020701@charter.net> Date: Sun, 28 Oct 2007 12:50:24 -0400 From: Andrew Lankford User-Agent: Thunderbird 2.0.0.6 (X11/20071017) MIME-Version: 1.0 References: <47240A15.8080305@charter.net> <20071028074248.GA1511@haakonia.hitnet.RWTH-Aachen.DE> <4724BAD9.7000400@charter.net> <20071028164152.GA7516@eos.sc1.parodius.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Chzlrs: 0 X-Mailman-Approved-At: Mon, 29 Oct 2007 01:50:29 +0000 Cc: stable@freebsd.org, current@freebsd.org Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 16:50:28 -0000 Danny Braniss wrote: >> On Sun, Oct 28, 2007 at 12:37:45PM -0400, Andrew Lankford wrote: >>> Thanks for replying, but once again I've miscommunicated the issue. I >>> meant that MAKEDEV.8 is in /usr/src/share/man/man8/, and the >>> modification time is Oct 13th, recent, which suggests to me that it's still >>> in the 7.0-BETA1 cvs tree. >> And you're very much correct: >> >> http://www.freebsd.org/cgi/cvsweb.cgi/src/share/man/man8/MAKEDEV.8 > > how about reading what ity says? it might be very educational :-) > > NAME > MAKEDEV -- old script for creating device nodes > > DESCRIPTION > The MAKEDEV script was deprecated by devfs(5) and removed from FreeBSD > after devfs(5) became mandatory. > > > > From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 16:54:13 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF8B216A420; Sun, 28 Oct 2007 16:54:13 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from mtai05.charter.net (mtai05.charter.net [209.225.8.185]) by mx1.freebsd.org (Postfix) with ESMTP id 36D7413C4BB; Sun, 28 Oct 2007 16:54:13 +0000 (UTC) (envelope-from lankfordandrew@charter.net) Received: from aarprv06.charter.net ([10.20.200.76]) by mtai05.charter.net (InterMail vM.7.08.02.00 201-2186-121-20061213) with ESMTP id <20071028165412.MOIU7894.mtai05.charter.net@aarprv06.charter.net>; Sun, 28 Oct 2007 12:54:12 -0400 Received: from [192.168.15.101] (really [75.138.219.8]) by aarprv06.charter.net with ESMTP id <20071028165412.KVLO14098.aarprv06.charter.net@[192.168.15.101]>; Sun, 28 Oct 2007 12:54:12 -0400 Message-ID: <4724BEB3.5080905@charter.net> Date: Sun, 28 Oct 2007 12:54:11 -0400 From: Andrew Lankford User-Agent: Thunderbird 2.0.0.6 (X11/20071017) MIME-Version: 1.0 References: <47240A15.8080305@charter.net> <20071028074248.GA1511@haakonia.hitnet.RWTH-Aachen.DE> <4724BAD9.7000400@charter.net> <20071028164152.GA7516@eos.sc1.parodius.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Chzlrs: 0 X-Mailman-Approved-At: Mon, 29 Oct 2007 01:50:29 +0000 Cc: stable@freebsd.org, current@freebsd.org Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 16:54:13 -0000 Thbbt! I'm reading the catman version of MAKEDEV. Wish I could disable that "feature". Oh well. I'll delete it all and rebuild it again if needed. Thanks! Andrew Lankford Danny Braniss wrote: >> On Sun, Oct 28, 2007 at 12:37:45PM -0400, Andrew Lankford wrote: >>> Thanks for replying, but once again I've miscommunicated the issue. I >>> meant that MAKEDEV.8 is in /usr/src/share/man/man8/, and the >>> modification time is Oct 13th, recent, which suggests to me that it's still >>> in the 7.0-BETA1 cvs tree. >> And you're very much correct: >> >> http://www.freebsd.org/cgi/cvsweb.cgi/src/share/man/man8/MAKEDEV.8 > > how about reading what ity says? it might be very educational :-) > > NAME > MAKEDEV -- old script for creating device nodes > > DESCRIPTION > The MAKEDEV script was deprecated by devfs(5) and removed from FreeBSD > after devfs(5) became mandatory. > > > > From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 23:02:27 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2149D16A421 for ; Sun, 28 Oct 2007 23:02:27 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 0216413C481 for ; Sun, 28 Oct 2007 23:02:26 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1ImGsK-0002XS-Fv for freebsd-current@freebsd.org; Sun, 28 Oct 2007 15:44:56 -0700 Message-ID: <13458892.post@talk.nabble.com> Date: Sun, 28 Oct 2007 15:44:56 -0700 (PDT) From: c0stra To: freebsd-current@freebsd.org In-Reply-To: <200710242042.l9OKgJPm017907@himinbjorg.tucs-beachin-obx-house.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: costra@centrum.cz References: <200710241652.l9OGqIGk013274@himinbjorg.tucs-beachin-obx-house.com> <20071024181909.248660@gmx.net> <20071024185927.GA83731@nagual.pp.ru> <200710241935.l9OJZLOC016429@himinbjorg.tucs-beachin-obx-house.com> <20071024202021.GA85884@nagual.pp.ru> <1193258036.41270.32.camel@opus.cse.buffalo.edu> <200710242042.l9OKgJPm017907@himinbjorg.tucs-beachin-obx-house.com> X-Mailman-Approved-At: Mon, 29 Oct 2007 01:50:29 +0000 Subject: Re: Undefined symbol "__mb_sb_limit" during 7.0-BETA1 installworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 23:02:27 -0000 For me this trick helped (explicit installation of libc before other world): cd /usr/src/lib/libc make make install affter this make buildworld + make installworld went through (and any other messages with missing '__mb_sb_limit' disapeared). But to be honest, I run into this problem a bit differently. I had problems already on 7-CURRENT with buildworld with mesages "'opt_w' redefined", so i did make -k buildworld and make -k installworld, so the world may wasn't complete. Anyway you can give it a try, and maybe it helps. Tuc at T-B-O-H.NET wrote: > >> On Thu, 2007-10-25 at 00:20 +0400, Andrey Chernov wrote: >> > Perhaps something is wrong in ISO making. >> >> Oops. Yes there is. New ones on the way. >> >> Sigh. >> > Will it be considered BETA2? Or BETA1 revised? > > Is it possible to find out how the issue happened? > > Thanks, Tuc > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > -- View this message in context: http://www.nabble.com/Undefined-symbol-%22__mb_sb_limit%22-during-7.0-BETA1-installworld-tf4685571.html#a13458892 Sent from the freebsd-current mailing list archive at Nabble.com. From owner-freebsd-current@FreeBSD.ORG Sun Oct 28 23:32:54 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F059716A418 for ; Sun, 28 Oct 2007 23:32:54 +0000 (UTC) (envelope-from robbak@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.190]) by mx1.freebsd.org (Postfix) with ESMTP id 80CDC13C4A5 for ; Sun, 28 Oct 2007 23:32:53 +0000 (UTC) (envelope-from robbak@gmail.com) Received: by mu-out-0910.google.com with SMTP id w9so1774437mue for ; Sun, 28 Oct 2007 16:32:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=pER8kLPskpovFtw0NQh2EBh6d+a46cEugDY/9+vkkyM=; b=XlAQ9CxQ7zUi4Z08dIb0PSHnq0DRJVTjlpKNtNAWQv/M7+A3GBCWlTeDU3tWxiGoMqKsJXhX7f8VHlOXfXzTbzcTRMMr/8DR+XH+FOspAuf3I/d3xKMamwlWioWeKLWhRpUEyhgHqz0L4doKOE7JTl5+h2AGv3j+IqMqEvyJ7Kc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=Bv2qgb1VfV6ocwXoYxt82u71b+T5x8zK/JY2dnGLXC6essLUqS1SWQqxaG5d2fi1RZHpoLV5ZPUnWhORiIeFs0qYQm9fVOi0o2ApqT3PAiNU7827aVScI6dCftVYr7+iar8L1O2HEq6C2jJpc2zLOLCbDHMCu6803VPq31OMomM= Received: by 10.86.99.9 with SMTP id w9mr4311690fgb.1193612893768; Sun, 28 Oct 2007 16:08:13 -0700 (PDT) Received: by 10.86.99.10 with HTTP; Sun, 28 Oct 2007 16:08:13 -0700 (PDT) Message-ID: Date: Mon, 29 Oct 2007 09:08:13 +1000 From: "Robert Backhaus" Sender: robbak@gmail.com To: "John Baldwin" In-Reply-To: <200710111741.34992.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200710111741.34992.jhb@FreeBSD.org> X-Google-Sender-Auth: 8188f81bfd3a895b X-Mailman-Approved-At: Mon, 29 Oct 2007 01:50:29 +0000 Cc: current@freebsd.org Subject: Re: New-bus unit wiring via hints.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Oct 2007 23:32:55 -0000 Any chance of extending this to the USB bus? The problem of 'wandering ugen' and 'wandering ulpt' devices has been bothering me for a while now. It would also help if it could be used to tell more specific drivers to leave a device for ugen - for instance, HP USB printers are best addressed by ugen, and the user mode drivers take it from there. You loose functionality if you have to talk through the ulpt drivers. From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 01:50:37 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF53C16A41B for ; Mon, 29 Oct 2007 01:50:37 +0000 (UTC) (envelope-from gkozyrev@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.freebsd.org (Postfix) with ESMTP id DFB4113C491 for ; Mon, 29 Oct 2007 01:49:57 +0000 (UTC) (envelope-from gkozyrev@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1112625nfb for ; Sun, 28 Oct 2007 18:49:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; 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=GRSS1jmbcv4yrf9YuOOdfrytQwm72DV8Z9PjTjMn8qg=; b=W97Yn2rqX81vVefipEBfH7uoIwkMtqoz2vuCf+vI9wD655NYTK49imUEPf9VPqZSZUiwK54cFDRZqL7HtJ/DhLxLwWpgqZ8qCwMEzkp2/Xs8Jo4TFnJw6w7rq9h+vKdFnpG4hHkZ7pm74zmF5YVIDuG57w66JHPlXkztifzc7EY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XhKQl6qdInN28ZQ2VtaaDA3gQmtd38qy4B1c1osT+fD2Sd8Ap/WEfCOiANJW1mdueeXkfjzAr/Wi6USfNyOQpHyKF2BInANtronBhW1lACLX4ho8r3MHXGgDCEhmRJqMlTwC7EB2bBNrElCHMP6yi4IRsWWhsLTRLx5VUX1oq4A= Received: by 10.78.185.15 with SMTP id i15mr3746894huf.1193622584546; Sun, 28 Oct 2007 18:49:44 -0700 (PDT) Received: by 10.78.148.14 with HTTP; Sun, 28 Oct 2007 18:49:44 -0700 (PDT) Message-ID: Date: Mon, 29 Oct 2007 03:49:44 +0200 From: "Gleb Kozyrev" To: freebsd-current@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200710251435.58984.jhb@freebsd.org> <200710261222.28656.jhb@freebsd.org> <20071026184536.GE37471@deviant.kiev.zoral.com.ua> Subject: Re: Deadlock, exclusive sx so_rcv_sx, amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 01:50:37 -0000 On 26/10/2007, Gleb Kozyrev wrote: > I managed to find a kernel message that precedes the freeze: > Approaching the limit on PV entries, consider increasing sysctl > vm.pmap.shpgperproc or vm.pmap.pv_entry_max > > rtorrent likes to mmap large files. > After increasing (one of) these sysctls everything seems ok. > Probably, setting rtorrent's memory limit could have helped either. > > Is there a way to know if some process is becoming close to that limit? It now just takes longer until freeze with shpgperproc = 5000 (originally 200). -- With best regards, Gleb Kozyrev. From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 07:18:55 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 43CD916A418 for ; Mon, 29 Oct 2007 07:18:55 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Received: from mx.isc.org (mx.isc.org [IPv6:2001:4f8:0:2::1c]) by mx1.freebsd.org (Postfix) with ESMTP id 11E2E13C49D for ; Mon, 29 Oct 2007 07:18:55 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "farside.isc.org", Issuer "ISC CA" (verified OK)) by mx.isc.org (Postfix) with ESMTP id 03876114027 for ; Mon, 29 Oct 2007 07:18:54 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Received: from manx.plosh.net (manx.vpn.isc.org [149.20.66.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by farside.isc.org (Postfix) with ESMTP id 17304E6059; Mon, 29 Oct 2007 07:18:54 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Message-ID: <4725895A.8030905@isc.org> Date: Mon, 29 Oct 2007 00:18:50 -0700 From: Peter Losher Organization: ISC User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <47246FED.6000103@isc.org> In-Reply-To: <47246FED.6000103@isc.org> X-Enigmail-Version: 0.95.5 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig41E5856CD630E50EADA71368" Subject: weird ZFS and mpt interactions (WAS Re: Clearing out vdevs (can't create new zpool)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 07:18:55 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig41E5856CD630E50EADA71368 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Peter Losher wrote: > I have been poking around with our 16-port SATA RAID chassis (in JBOD > mode) with a fresh RELENG_7 internal build from Saturday. I only had > half the disks {da0-7) at first, when I brought over the second set > (da8-15), I destroyed the existing pool and then tried to create a new > one with all 16 disks, and encountered this error: >=20 > -=3D- > # zpool create tank raidz da{0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15} > cannot create 'tank': one or more vdevs refer to the same device > -=3D- >=20 > I can create one with the second set of disks (and destroy/create again= ) > but somehow I have some old vdevs sitting around which is preventing me= > from using the first set of disks. How can I clear them out? O.k. poked at this some more this evening and I see what the problem might be. The SATA RAID chassis (in JBOD mode) is presenting the 16 drives as two sets of 8 drives each (it has two FC connections, one for each set - incidentally in RAID mode, it just needs one to cover all 16 disks as it's able to bridge the two controllers together). Those two FC connections are plugged into a dual port LSI Logic FC HBA: -=3D- mpt0: port 0x2400-0x24ff mem 0xb8a20000-0xb8a23fff,0xb8a00000-0xb8a0ffff irq 24 at device 3.0 on p= ci8 mpt0: [ITHREAD] mpt0: MPI Version=3D1.5.10.0 mpt1: port 0x2000-0x20ff mem 0xb8a24000-0xb8a27fff,0xb8a10000-0xb8a1ffff irq 27 at device 3.1 on p= ci8 mpt1: [ITHREAD] mpt1: MPI Version=3D1.5.10.0 -=3D- so this disks show up as such: -=3D- da0 at mpt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 100.000MB/s transfers da0: Command Queueing Enabled da0: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) da1 at mpt0 bus 0 target 0 lun 1 da1: Fixed Direct Access SCSI-3 device da1: 100.000MB/s transfers da1: Command Queueing Enabled da1: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) da2 at mpt0 bus 0 target 0 lun 2 da2: Fixed Direct Access SCSI-3 device da2: 100.000MB/s transfers da2: Command Queueing Enabled da2: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) da3 at mpt0 bus 0 target 0 lun 3 da3: Fixed Direct Access SCSI-3 device da3: 100.000MB/s transfers da3: Command Queueing Enabled da3: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) da4 at mpt0 bus 0 target 0 lun 4 da4: Fixed Direct Access SCSI-3 device da4: 100.000MB/s transfers da4: Command Queueing Enabled da4: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) da5 at mpt0 bus 0 target 0 lun 5 da5: Fixed Direct Access SCSI-3 device da5: 100.000MB/s transfers da5: Command Queueing Enabled da5: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) da6 at mpt0 bus 0 target 0 lun 6 da6: Fixed Direct Access SCSI-3 device da6: 100.000MB/s transfers da6: Command Queueing Enabled da6: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) da7 at mpt0 bus 0 target 0 lun 7 da7: Fixed Direct Access SCSI-3 device da7: 100.000MB/s transfers da7: Command Queueing Enabled da7: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) da8 at mpt1 bus 0 target 0 lun 0 da8: Fixed Direct Access SCSI-3 device da8: 100.000MB/s transfers da8: Command Queueing Enabled da8: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) da9 at mpt1 bus 0 target 0 lun 1 da9: Fixed Direct Access SCSI-3 device da9: 100.000MB/s transfers da9: Command Queueing Enabled da9: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) da10 at mpt1 bus 0 target 0 lun 2 da10: Fixed Direct Access SCSI-3 device da10: 100.000MB/s transfers da10: Command Queueing Enabled da10: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) da11 at mpt1 bus 0 target 0 lun 3 da11: Fixed Direct Access SCSI-3 device da11: 100.000MB/s transfers da11: Command Queueing Enabled da11: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) da12 at mpt1 bus 0 target 0 lun 4 da12: Fixed Direct Access SCSI-3 device da12: 100.000MB/s transfers da12: Command Queueing Enabled da12: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) da13 at mpt1 bus 0 target 0 lun 5 da13: Fixed Direct Access SCSI-3 device da13: 100.000MB/s transfers da13: Command Queueing Enabled da13: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) da14 at mpt1 bus 0 target 0 lun 6 da14: Fixed Direct Access SCSI-3 device da14: 100.000MB/s transfers da14: Command Queueing Enabled da14: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) da15 at mpt1 bus 0 target 0 lun 7 da15: Fixed Direct Access SCSI-3 device da15: 100.000MB/s transfers da15: Command Queueing Enabled da15: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) -=3D- Two identical sets of 8 disks, the only difference is that one set is presented over mpt0, the other over mpt1. I suspect ZFS is treating this as just one set of eight vdevs as I can create a pool with either the first set of eight or the second set of eight, just not with BOTH sets of disks. Hope this helps explain things a bit better. Best Wishes - Peter --=20 Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow" --------------enig41E5856CD630E50EADA71368 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHJYlgPtVx9OgEjQgRAnQQAJ9OoPuAr0qCaVwqK+yaYyqEmtZr2ACeO38Z pY2u7oNVOS2N6RTDyD2xGTM= =sRYs -----END PGP SIGNATURE----- --------------enig41E5856CD630E50EADA71368-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 08:20:56 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AEB5916A417; Mon, 29 Oct 2007 08:20:56 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Received: from mx.isc.org (mx.isc.org [IPv6:2001:4f8:0:2::1c]) by mx1.freebsd.org (Postfix) with ESMTP id 8F39913C4A5; Mon, 29 Oct 2007 08:20:56 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "farside.isc.org", Issuer "ISC CA" (verified OK)) by mx.isc.org (Postfix) with ESMTP id 65D5511401E; Mon, 29 Oct 2007 08:20:55 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Received: from tardis-plosh-net.local (tardis.vpn.isc.org [149.20.66.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by farside.isc.org (Postfix) with ESMTP id 4623AE6056; Mon, 29 Oct 2007 08:20:53 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Message-ID: <472597FB.90800@isc.org> Date: Mon, 29 Oct 2007 01:21:15 -0700 From: Peter Losher User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <47246FED.6000103@isc.org> <4725895A.8030905@isc.org> <20071029090141.GA4407@garage.freebsd.pl> In-Reply-To: <20071029090141.GA4407@garage.freebsd.pl> X-Enigmail-Version: 0.95.3 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig083EF5CA2E629BE4F3BB4A9D" Cc: freebsd-current@freebsd.org Subject: Re: weird ZFS and mpt interactions (WAS Re: Clearing out vdevs (can't create new zpool)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 08:20:56 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig083EF5CA2E629BE4F3BB4A9D Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Pawel Jakub Dawidek wrote: > Let me get this right. Those are 16 physically different disks? Not 8 > disks visible through two FC path? Can you show: >=20 > # apply "camcontrol inquiry da%1 -S" `jot 16 0` erg... it seems looking at that output it's the same set of 8 disks (the chassis isn't presenting the second set at all). The next time I am in front of the box, I will poke at the disk appliance firmware to get it to present all 16 (unique) disks. Sorry for the noise, should have thought that might have been the issue before sending that last message. (as I have been poking the box all day remotely) Best Wishes - Peter --=20 Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow" --------------enig083EF5CA2E629BE4F3BB4A9D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFHJZgBPtVx9OgEjQgRAi7HAJ4uFN24RpGxftSwuO9mld4OgKHYGwCgiKwS mJ8JtpQ9E7VVYgYdnJDUfrQ= =9N6K -----END PGP SIGNATURE----- --------------enig083EF5CA2E629BE4F3BB4A9D-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 10:37:29 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80ECC16A417 for ; Mon, 29 Oct 2007 10:37:29 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7C6B913C48A; Mon, 29 Oct 2007 10:37:28 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4725B7EA.5080807@FreeBSD.org> Date: Mon, 29 Oct 2007 11:37:30 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Gleb Kozyrev References: <200710251435.58984.jhb@freebsd.org> <200710261222.28656.jhb@freebsd.org> <20071026184536.GE37471@deviant.kiev.zoral.com.ua> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Deadlock, exclusive sx so_rcv_sx, amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 10:37:29 -0000 Gleb Kozyrev wrote: > On 26/10/2007, Gleb Kozyrev wrote: >> I managed to find a kernel message that precedes the freeze: >> Approaching the limit on PV entries, consider increasing sysctl >> vm.pmap.shpgperproc or vm.pmap.pv_entry_max >> >> rtorrent likes to mmap large files. >> After increasing (one of) these sysctls everything seems ok. >> Probably, setting rtorrent's memory limit could have helped either. >> >> Is there a way to know if some process is becoming close to that limit? > > It now just takes longer until freeze with shpgperproc = 5000 (originally 200). > So how about vm.pmap.pv_entry_max? Have you obtained the usual debugging information (DDB backtraces, etc) when the system freezes? Kris From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 15:45:57 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F054D16A4C6 for ; Mon, 29 Oct 2007 15:45:55 +0000 (UTC) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (nagual.pp.ru [194.87.13.69]) by mx1.freebsd.org (Postfix) with ESMTP id 4EEE413C459 for ; Mon, 29 Oct 2007 15:45:46 +0000 (UTC) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.14.1/8.14.1) with ESMTP id l9T4SObx000236; Mon, 29 Oct 2007 07:28:24 +0300 (MSK) (envelope-from ache@nagual.pp.ru) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nagual.pp.ru; s=default; t=1193632104; bh=yjpH23e20oRKEvh+EPkffUNT/RPKIehyjqbVRtt TjhY=; l=792; h=Date:From:To:Cc:Subject:Message-ID:Mail-Followup-To: References:MIME-Version:Content-Type:Content-Disposition: In-Reply-To:User-Agent; b=OyW1+LWB96ZwfF+pj9DMbWFcoymQomQE9bfDGf98 xMRcNa7rEadHi1YbkHfml0jCvkk00KkMXR6eertXIYN1gk3iPTmfEgiIjsGD4PdiPCE F1XutGNg43n83JVAyUv1z+OBWKvce351UbSDUAFB76JzzLwowfrpzx6ZJmob6C5Y= Received: (from ache@localhost) by nagual.pp.ru (8.14.1/8.14.1/Submit) id l9T4SOro000235; Mon, 29 Oct 2007 07:28:24 +0300 (MSK) (envelope-from ache) Date: Mon, 29 Oct 2007 07:28:23 +0300 From: Andrey Chernov To: c0stra Message-ID: <20071029042823.GA210@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , c0stra , freebsd-current@FreeBSD.ORG References: <200710241652.l9OGqIGk013274@himinbjorg.tucs-beachin-obx-house.com> <20071024181909.248660@gmx.net> <20071024185927.GA83731@nagual.pp.ru> <200710241935.l9OJZLOC016429@himinbjorg.tucs-beachin-obx-house.com> <20071024202021.GA85884@nagual.pp.ru> <1193258036.41270.32.camel@opus.cse.buffalo.edu> <200710242042.l9OKgJPm017907@himinbjorg.tucs-beachin-obx-house.com> <13458892.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <13458892.post@talk.nabble.com> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@FreeBSD.ORG Subject: Re: Undefined symbol "__mb_sb_limit" during 7.0-BETA1 installworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 15:45:58 -0000 On Sun, Oct 28, 2007 at 03:44:56PM -0700, c0stra wrote: > > For me this trick helped (explicit installation of libc before other world): > > cd /usr/src/lib/libc > make > make install > > affter this make buildworld + make installworld went through (and any other > messages with missing '__mb_sb_limit' disapeared). > But to be honest, I run into this problem a bit differently. I had problems > already on 7-CURRENT with buildworld with mesages "'opt_w' redefined", so i > did make -k buildworld and make -k installworld, so the world may wasn't > complete. This step needed when manually rebuild sourses by just 'make' but unneded for 'make world' or 'make buildworld' + 'make installworld' because libc is rebuilded and installed first. -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 15:46:48 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7B2E16A4CD; Mon, 29 Oct 2007 15:46:46 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id C217113C469; Mon, 29 Oct 2007 15:46:27 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (vader.bytemobile-rio.ondsl.gr [83.235.57.37]) (authenticated bits=128) by igloo.linux.gr (8.14.1/8.14.1/Debian-9) with ESMTP id l9TDP8Bv004307 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 29 Oct 2007 15:25:24 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.1/8.14.1) with ESMTP id l9TDOljm002717; Mon, 29 Oct 2007 15:25:02 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by kobe.laptop (8.14.1/8.14.1/Submit) id l9TDOlmm002716; Mon, 29 Oct 2007 15:24:47 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Mon, 29 Oct 2007 15:24:47 +0200 From: Giorgos Keramidas To: Andrew Lankford Message-ID: <20071029132447.GA2658@kobe.laptop> References: <47240A15.8080305@charter.net> <20071028074248.GA1511@haakonia.hitnet.RWTH-Aachen.DE> <4724BAD9.7000400@charter.net> <20071028164152.GA7516@eos.sc1.parodius.com> <4724BEB3.5080905@charter.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4724BEB3.5080905@charter.net> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.987, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.41, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: stable@freebsd.org, current@freebsd.org Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 15:46:48 -0000 On 2007-10-28 12:54, Andrew Lankford wrote: > Thbbt! I'm reading the catman version of MAKEDEV. Wish I could > disable that "feature". Oh well. I'll delete it all and rebuild it > again if needed. Thanks! Ah, that's it then :) My usual `installworld' steps include this too: # cd /usr/share/man # find cat[0-9] \! -type d -exec rm {} + This takes care of deleting any `stale' preformatted manpages, so the next time I ask for a manpage, it's going to be reformatted. From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 15:59:48 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A3A416A46E for ; Mon, 29 Oct 2007 15:59:48 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from smtp02.dentaku.gol.com (smtp02.dentaku.gol.com [203.216.5.72]) by mx1.freebsd.org (Postfix) with ESMTP id E0F9A13C45A for ; Mon, 29 Oct 2007 15:59:34 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from pat.gol.co.jp ([203.216.1.191] helo=[127.0.0.1]) by smtp02.dentaku.gol.com with esmtpa (Dentaku) id 1ImLRx-0004Pd-S0 for ; Mon, 29 Oct 2007 12:38:01 +0900 Message-ID: <4725558F.6040702@fusiongol.com> Date: Mon, 29 Oct 2007 12:37:51 +0900 From: Nathan Butcher User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV GOL X-Abuse-Complaints: abuse@gol.com Subject: Re: Problem with ATAPI device on JMicron JMB363 on 7.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 15:59:50 -0000 >Hi, >I've tried to install FreeBSD 7.0-BETA1/amd64 on Gigabyte P35-S3 mb >with >PATA DVD-RW drive attached to JMicron JMB363 controller. The JMicron JMB363 controller is *still* broken. I have a Gigabyte GA-G33-DS3R. FreeBSD 7.0-BETA1 detects the chipset, but no devices attached to the SATA controllers find their relative /dev entries. My SATA DVD-combo drive simply doesn't get /dev/acd0, and as a result I cannot access the drive. I've tried hard drives too, with the same results. The IDE interface seems to work for me (I have an IDE -> CF converter in there), but I don't have a PATA optical drive to test. From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 16:04:36 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B0B916A417 for ; Mon, 29 Oct 2007 16:04:35 +0000 (UTC) (envelope-from brucegb@realtime.net) Received: from ruth.realtime.net (mercury.realtime.net [205.238.132.86]) by mx1.freebsd.org (Postfix) with ESMTP id BFCC713C474 for ; Mon, 29 Oct 2007 16:04:17 +0000 (UTC) (envelope-from brucegb@realtime.net) Received: from tigerfish2.my.domain (cpe-70-122-44-4.austin.res.rr.com [70.122.44.4]) by realtime.net (Realtime Communications Advanced E-Mail Services V9.2) with ESMTP id 123866736-1817707 for ; Sun, 28 Oct 2007 22:14:33 -0500 Received: from tigerfish2.my.domain (localhost [127.0.0.1]) by tigerfish2.my.domain (8.13.8/8.13.8) with ESMTP id l9T3EWce074759 for ; Sun, 28 Oct 2007 22:14:32 -0500 (CDT) (envelope-from brucegb@tigerfish2.my.domain) Received: (from brucegb@localhost) by tigerfish2.my.domain (8.13.8/8.13.8/Submit) id l9T3EW1p074758 for current@freebsd.org; Sun, 28 Oct 2007 22:14:32 -0500 (CDT) (envelope-from brucegb) Date: Sun, 28 Oct 2007 22:14:32 -0500 From: Bruce Burden To: current@freebsd.org Message-ID: <20071029031432.GT1005@tigerfish2.my.domain> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: Subject: Re: 2nd nfe interface not showing up on Tyan S2895 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 16:04:36 -0000 Hi, For those of you with the Tyan S2895 board, have you been able to get the USB system to run at USB 2.0 speeds? I have had problems with ehci and USB sticks, so I run at Legacy/ USB 1.1 levels in the BIOS. This is with FBSD 6.2, in both 32 and 64 bit modes. And, yeah, I have a CPU in both sockets. :-) Thank you, Bruce -- ------------------------------------------------------------------------ "I like bad!" Bruce Burden Austin, TX. - Thuganlitha The Power and the Prophet Robert Don Hughes From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 16:04:56 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72B1E16A4F5; Mon, 29 Oct 2007 16:04:56 +0000 (UTC) (envelope-from freebsd@masm.elcom.ru) Received: from smtp.elcom.ru (smtp.elcom.ru [84.53.200.28]) by mx1.freebsd.org (Postfix) with ESMTP id CBB7C13C45B; Mon, 29 Oct 2007 16:04:37 +0000 (UTC) (envelope-from freebsd@masm.elcom.ru) Received: by smtp.elcom.ru (Postfix, from userid 65534) id C4CFD3D8706; Mon, 29 Oct 2007 12:31:05 +0300 (MSK) Received: from VMHOST (dsl-212-78.elcom.ru [84.53.212.78]) by smtp.elcom.ru (Postfix) with ESMTP id 8CA793D868E; Mon, 29 Oct 2007 12:31:05 +0300 (MSK) Date: Mon, 29 Oct 2007 12:31:12 +0300 From: "Victor M. Blood" X-Mailer: The Bat! (v3.80.06) Professional Organization: Home Programming Inc. X-Priority: 3 (Normal) Message-ID: <844298991.20071029123112@masm.elcom.ru> To: Darren Reed , freebsd-current@freebsd.org In-Reply-To: <47200F5E.9070104@freebsd.org> References: <359284519.20071018014832@masm.elcom.ru> <200710172357.18221.max@love2party.net> <6210619899.20071018020530@masm.elcom.ru> <200710180021.39250.max@love2party.net> <1564774296.20071018172432@masm.elcom.ru> <47200F5E.9070104@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: ipfilter cannot be build within because warning's are present X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 16:04:56 -0000 On 25.10.2007, Darren Reed wrote: > Please try the attached patch. Hmm... All patches failed in /sys/contrib/ipfilter/netinet Script started on Mon Oct 29 13:25:23 2007 release# patch=07 -p4 Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 594D016A420 for ; Mon, 29 Oct 2007 16:53:25 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id CFD5E13C4A6 for ; Mon, 29 Oct 2007 16:53:24 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.13.8/jtpda-5.4) with ESMTP id l9T92AFw058434 ; Mon, 29 Oct 2007 10:02:10 +0100 (CET) X-Ids: 166 Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.13.3/jtpda-5.2) with ESMTP id l9T929jT024991 ; Mon, 29 Oct 2007 10:02:09 +0100 (MET) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.13.3/8.13.1/Submit) id l9T928bS024988; Mon, 29 Oct 2007 10:02:08 +0100 (MET) (envelope-from arno) To: pyunyh@gmail.com References: <20071029024452.GB32892@cdnetworks.co.kr> From: "Arno J. Klaassen" Date: 29 Oct 2007 10:02:08 +0100 In-Reply-To: <20071029024452.GB32892@cdnetworks.co.kr> Message-ID: Lines: 43 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (shiva.jussieu.fr [134.157.0.166]); Mon, 29 Oct 2007 10:02:10 +0100 (CET) X-Virus-Scanned: ClamAV 0.88.7/4617/Mon Oct 29 07:41:06 2007 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at shiva.jussieu.fr with ID 4725A192.003 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Cc: current@freebsd.org Subject: Re: 2nd nfe interface not showing up on Tyan S2895 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 16:53:25 -0000 Dear Pyun YongHyeon, > On Sun, Oct 28, 2007 at 07:27:25PM +0100, Arno J. Klaassen wrote: > > Hi, > > > > I'm playing with RELENG_7 on a spare S2895 I have around and > > have difficulties with the ethernet interfaces : > > > > - nfe0 shows up and works OK under 1Gbps (at least for > > buildworlds etc over NFS) but under 100Mbps it says : > > > > install kernel: nfe0: tx v2 error 0x6004 > > install kernel: nfe0: tx v2 error 0x6204 > > > > Because developers don't know what exact meaning for Tx completion > status word would be(Only NVIDIA knows that) nfe(4) just shows the > possible error candidate. OK > If you see the code you may notice no error > recovery is attempted for the case. > So I guess you can also ignore it unless the message contiously is > printed on youe console while network activity is in progress. Ehmm, I notice no network activity at all ... when plugged at a 100Mbps 3com hub. As said, plugged at a (Netgear) 1Gbps it works flawlessly. Let me know if I can test a patch/sysctl etc. For the time being I will use this board internally anyway. Regards, Arno -- Arno J. Klaassen SCITO S.A. 8 rue des Haies F-75020 Paris, France http://scito.com From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 17:07:43 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ADE7016A468 for ; Mon, 29 Oct 2007 17:07:43 +0000 (UTC) (envelope-from gkozyrev@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.freebsd.org (Postfix) with ESMTP id 4361D13C4AC for ; Mon, 29 Oct 2007 17:07:31 +0000 (UTC) (envelope-from gkozyrev@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1281409nfb for ; Mon, 29 Oct 2007 10:07:00 -0700 (PDT) Received: by 10.78.138.6 with SMTP id l6mr4039713hud.1193657818386; Mon, 29 Oct 2007 04:36:58 -0700 (PDT) Received: by 10.78.148.14 with HTTP; Mon, 29 Oct 2007 04:36:58 -0700 (PDT) Message-ID: Date: Mon, 29 Oct 2007 13:36:58 +0200 From: "Gleb Kozyrev" To: "Kris Kennaway" In-Reply-To: <4725B7EA.5080807@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200710251435.58984.jhb@freebsd.org> <200710261222.28656.jhb@freebsd.org> <20071026184536.GE37471@deviant.kiev.zoral.com.ua> <4725B7EA.5080807@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: Re: Deadlock, exclusive sx so_rcv_sx, amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 17:07:43 -0000 On 29/10/2007, Kris Kennaway wrote: > > It now just takes longer until freeze with shpgperproc = 5000 (originally 200). > > > > So how about vm.pmap.pv_entry_max? Have you obtained the usual > debugging information (DDB backtraces, etc) when the system freezes? vm.pmap.pv_entry_max and vm.pmap.shpgperproc turn out to be related and raising one of them automatically raises the other. If there's a bug those sysctls won't help, will they? If there's no bug what values can you suggest? Defaults are vm.pmap.pv_entry_max: 1479365 vm.pmap.shpgperproc: 200 Backtraces, etc are provided in this thread. -- With best regards, Gleb Kozyrev. From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 17:19:03 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 275FE16A420 for ; Mon, 29 Oct 2007 17:19:03 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id D481413C48A for ; Mon, 29 Oct 2007 17:18:57 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1ImXEb-0007dI-TN for freebsd-current@freebsd.org; Mon, 29 Oct 2007 16:13:02 +0000 Received: from dhcp-69-07.cc.fer.hr ([161.53.69.167]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Oct 2007 16:13:01 +0000 Received: from ivoras by dhcp-69-07.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Oct 2007 16:13:01 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Mon, 29 Oct 2007 17:14:53 +0100 Lines: 23 Message-ID: References: <20071005000046.GC92272@garage.freebsd.pl> <20071008121523.GM2327@garage.freebsd.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: dhcp-69-07.cc.fer.hr User-Agent: Thunderbird 2.0.0.6 (X11/20070801) In-Reply-To: <20071008121523.GM2327@garage.freebsd.pl> Sender: news Cc: freebsd-fs@freebsd.org Subject: Re: ZFS kmem_map too small. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 17:19:03 -0000 Pawel Jakub Dawidek wrote: > Here are some updates: > > I was able to reproduce the panic by rsyncing big files and trying > bonnie++ test suggested in this thread. > > Can you guys retry with this patch: > > http://people.freebsd.org/~pjd/patches/vm_kern.c.2.patch > > It's a hack, yes, but allows to mitigate the problem quite well. I'm > looking for a solution that can be used for 7.0 before we find a better > fix. Your patch makes this configuration work: RELENG_7 on VMWare Server with 256 MB of memory, without any tuning to sysctl.conf and loader.conf. This is as bad environment (wrt memory pressure and timings) as you can get :) With this patch the (virtual) machine survives portsnap fetch extract, where before the patch it would soon panic with kmem_map too small. You have my vote to commit it :) From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 17:24:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 21F8016A41B for ; Mon, 29 Oct 2007 17:24:18 +0000 (UTC) (envelope-from freebsd@masm.elcom.ru) Received: from smtp.elcom.ru (smtp.elcom.ru [84.53.200.28]) by mx1.freebsd.org (Postfix) with ESMTP id B710213C4C3 for ; Mon, 29 Oct 2007 17:24:07 +0000 (UTC) (envelope-from freebsd@masm.elcom.ru) Received: by smtp.elcom.ru (Postfix, from userid 65534) id AD2563D86FC; Mon, 29 Oct 2007 16:47:02 +0300 (MSK) Received: from VMHOST (dsl-212-78.elcom.ru [84.53.212.78]) by smtp.elcom.ru (Postfix) with ESMTP id D499D3D865B; Mon, 29 Oct 2007 16:47:01 +0300 (MSK) Date: Mon, 29 Oct 2007 16:47:08 +0300 From: "Victor M. Blood" X-Mailer: The Bat! (v3.80.06) Professional Organization: Home Programming Inc. X-Priority: 3 (Normal) Message-ID: <634999938.20071029164708@masm.elcom.ru> To: "Victor M. Blood" , In-Reply-To: <1676188657.20071025214328@masm.elcom.ru> References: <359284519.20071018014832@masm.elcom.ru> <200710172357.18221.max@love2party.net> <6210619899.20071018020530@masm.elcom.ru> <200710180021.39250.max@love2party.net> <1564774296.20071018172432@masm.elcom.ru> <47200F5E.9070104@freebsd.org> <1676188657.20071025214328@masm.elcom.ru> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------10BA214A39C7BC59" Subject: Re: ipfilter cannot be build within because warning's are present X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 17:24:18 -0000 ------------10BA214A39C7BC59 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit On 25.10.2007, Victor M. Blood wrote: > On 25.10.2007, Darren Reed wrote: >> Please try the attached patch. > [skip] >> Darren > I try new kernel with ipf 4.1.28 and these patches at sunday... If > understand how to apply it for files in sys/contrib and > contrib/ipfilter/ipfilter all errors was in 4.1.27 stay in 1.4.28, that's with "nat -s" I don't know... -- With all regards, Victor M. Blood. mailto: freebsd@masm.elcom.ru FTN: 2:5024/1.95@Fidonet.org, ICQ#3567656 ------------10BA214A39C7BC59 Content-Type: text/plain; name="kerncomp.txt" Content-transfer-encoding: base64 Content-Disposition: attachment; filename="kerncomp.txt" U2NyaXB0IHN0YXJ0ZWQgb24gTW9uIE9jdCAyOSAxNzo0Mzo1OSAyMDA3CnJlbGVhc2UjIG1h a2UNDQpjYyAtYyAtTyAtcGlwZSAtbWFyY2g9cGVudGl1bTMgLXN0ZD1jOTkgLWcgLVdhbGwg LVdyZWR1bmRhbnQtZGVjbHMgLVduZXN0ZWQtZXh0ZXJucyAtV3N0cmljdC1wcm90b3R5cGVz ICAtV21pc3NpbmctcHJvdG90eXBlcyAtV3BvaW50ZXItYXJpdGggLVdpbmxpbmUgLVdjYXN0 LXF1YWwgIC1XdW5kZWYgLVduby1wb2ludGVyLXNpZ24gLWZmb3JtYXQtZXh0ZW5zaW9ucyAt bm9zdGRpbmMgIC1JLiAtSS4uLy4uLy4uIC1JLi4vLi4vLi4vY29udHJpYi9hbHRxIC1EX0tF Uk5FTCAtREhBVkVfS0VSTkVMX09QVElPTl9IRUFERVJTIC1pbmNsdWRlIG9wdF9nbG9iYWwu aCAtZm5vLWNvbW1vbiAtZmlubGluZS1saW1pdD04MDAwIC0tcGFyYW0gaW5saW5lLXVuaXQt Z3Jvd3RoPTEwMCAtLXBhcmFtIGxhcmdlLWZ1bmN0aW9uLWdyb3d0aD0xMDAwICAtbW5vLWFs aWduLWxvbmctc3RyaW5ncyAtbXByZWZlcnJlZC1zdGFjay1ib3VuZGFyeT0yICAtbW5vLW1t eCAtbW5vLTNkbm93IC1tbm8tc3NlIC1tbm8tc3NlMiAtbW5vLXNzZTMgLWZmcmVlc3RhbmRp bmcgLVdlcnJvciAgLi4vLi4vLi4vY29udHJpYi9pcGZpbHRlci9uZXRpbmV0L2ZpbC5jIC1J Li4vLi4vLi4vY29udHJpYi9pcGZpbHRlcg0KSW4gZmlsZSBpbmNsdWRlZCBmcm9tIC4uLy4u Ly4uL2NvbnRyaWIvaXBmaWx0ZXIvbmV0aW5ldC9maWwuYzoxMTU6DQouLi8uLi8uLi9jb250 cmliL2lwZmlsdGVyL25ldGluZXQvaXBfY29tcGF0Lmg6Mzc6NTogZXJyb3I6ICJTT0xBUklT MiIgaXMgbm90IGRlZmluZWQNCkluIGZpbGUgaW5jbHVkZWQgZnJvbSAuLi8uLi8uLi9jb250 cmliL2lwZmlsdGVyL25ldGluZXQvZmlsLmM6MTIzOg0KLi4vLi4vLi4vY29udHJpYi9pcGZp bHRlci9uZXRpbmV0L2lwX2ZpbC5oOjEyNDk6NzogZXJyb3I6ICJOZXRCU0QiIGlzIG5vdCBk ZWZpbmVkDQouLi8uLi8uLi9jb250cmliL2lwZmlsdGVyL25ldGluZXQvaXBfZmlsLmg6MTM0 Mjo5OiBlcnJvcjogIl9CU0RJX1ZFUlNJT04iIGlzIG5vdCBkZWZpbmVkDQouLi8uLi8uLi9j b250cmliL2lwZmlsdGVyL25ldGluZXQvaXBfZmlsLmg6MTM0NDozMzogZXJyb3I6ICJfQlNE SV9WRVJTSU9OIiBpcyBub3QgZGVmaW5lZA0KLi4vLi4vLi4vY29udHJpYi9pcGZpbHRlci9u ZXRpbmV0L2ZpbC5jOjI1MTI6NjogZXJyb3I6ICJPcGVuQlNEIiBpcyBub3QgZGVmaW5lZA0K Li4vLi4vLi4vY29udHJpYi9pcGZpbHRlci9uZXRpbmV0L2ZpbC5jOjI3NzU6NjogZXJyb3I6 ICJPcGVuQlNEIiBpcyBub3QgZGVmaW5lZA0KKioqIEVycm9yIGNvZGUgMQ0KDQpTdG9wIGlu IC91c3Ivc3JjL3N5cy9pMzg2L2NvbXBpbGUvc3lzb25lLg0KcmVsZWFzZSMgZXhpdA0NCmV4 aXQNCgpTY3JpcHQgZG9uZSBvbiBNb24gT2N0IDI5IDE3OjQ0OjA5IDIwMDcK ------------10BA214A39C7BC59-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 17:31:03 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AAE3B16A46D for ; Mon, 29 Oct 2007 17:31:03 +0000 (UTC) (envelope-from fjwcash+freebsd@gmail.com) Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140]) by mx1.freebsd.org (Postfix) with ESMTP id 6ECBB13C4AC for ; Mon, 29 Oct 2007 17:30:49 +0000 (UTC) (envelope-from fjwcash+freebsd@gmail.com) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id CAC1B1A000B34; Mon, 29 Oct 2007 10:12:46 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at smtp.sd73.bc.ca Received: from smtp.sd73.bc.ca ([127.0.0.1]) by localhost (smtp.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id bAxF5nBqxzNu; Mon, 29 Oct 2007 10:12:39 -0700 (PDT) Received: from coal (s10.sbo [192.168.0.10]) by smtp.sd73.bc.ca (Postfix) with ESMTP id 8DFFE1A000B17; Mon, 29 Oct 2007 10:12:39 -0700 (PDT) From: Freddie Cash Organization: School District 73 To: kps@ucsb.edu Date: Mon, 29 Oct 2007 10:12:37 -0700 User-Agent: KMail/1.9.7 References: <48344.172.16.9.1.1192472836.squirrel@www.xtra-net.be> <20071025201857.GC43606@aleph.cepheid.org> <200710281319.33309.kps@ucsb.edu> In-Reply-To: <200710281319.33309.kps@ucsb.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200710291012.38130.fjwcash+freebsd@gmail.com> Cc: current@freebsd.org Subject: Re: Xen Status : FreeBSD-current as Dom/U. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 17:31:03 -0000 On October 28, 2007 01:19 pm Kevin Schmidt wrote: > On Thursday 25 October 2007, Erik Osterholm wrote: > > On Fri, Oct 26, 2007 at 05:06:49AM +0900, Harrison Grundy wrote: > > > On Thu, 2007-10-25 at 12:05 +0200, Dag-Erling Sm=F8rgrav wrote: > > > > "Vincent Blondel" writes: > > > > > Can somebody indicate me what settings I have to include in > > > > > GENERIC config file so to compile a Xen Dom/U FreeBSD kernel. > > > > > > > > FreeBSD currently does not support running under Xen. > > > > > > I just thought I'd note that you can use Xen with FreeBSD if your > > > processor supports hardware virtualization, I believe. > > > > I have yet to hear any independant verification of this. Anyone > > actually running FreeBSD as a domU with hardware virtualization? > > FWIW, I've tried FreeBSD as an HVM guest on several Linux distros as > Dom0, Xen 3.0 (3.0.3, 3.0.4) and 3.1 (3.1.0), using Xen packages and > manual compiles. Linux distros included Ubuntu 7.04 and Debian 4. > FreeBSD 6.2 and 7.0 -- release and snapshots -- consistently fail to > boot with a looping "BTX halted" and register dump. If there's a way > to install stock FreeBSD under Xen HVM, I haven't seen it. Without > saying whether this is properly a Xen problem or FBSD BTX problem, my > guess is this type of installation will not work until there are BTX > changes. Crap, that's not what I want to hear. :( Any chance you would be willing/able to test using XenEnterprise 4 as the=20 Dom0 (there's a free version available at: http://www.citrixxenserver.com/products/Pages/XenExpress.aspx). We're in the process of ordering a system for use with Xen and were hoping= =20 to use if for virtualising FreeBSD 7.x (using HVM), Windows 2k3 (using=20 HVM), along with Debian and Ubuntu Server (using paravirt). =2D-=20 =46reddie Cash, LPIC-2 CCNT CCLP Network Support Technician School District 73 (250) 377-HELP [377-4357] fjwcash+freebsd@gmail.com From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 17:47:56 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 68F6116A41A for ; Mon, 29 Oct 2007 17:47:56 +0000 (UTC) (envelope-from fjwcash+freebsd@gmail.com) Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140]) by mx1.freebsd.org (Postfix) with ESMTP id 496E913C4B2 for ; Mon, 29 Oct 2007 17:47:48 +0000 (UTC) (envelope-from fjwcash+freebsd@gmail.com) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id 7954A1A000B0F for ; Mon, 29 Oct 2007 10:16:23 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at smtp.sd73.bc.ca Received: from smtp.sd73.bc.ca ([127.0.0.1]) by localhost (smtp.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Bry83q3kHfxW for ; Mon, 29 Oct 2007 10:16:16 -0700 (PDT) Received: from coal (s10.sbo [192.168.0.10]) by smtp.sd73.bc.ca (Postfix) with ESMTP id 78CD21A000B2A for ; Mon, 29 Oct 2007 10:16:16 -0700 (PDT) From: Freddie Cash Organization: School District 73 To: current@freebsd.org Date: Mon, 29 Oct 2007 10:16:14 -0700 User-Agent: KMail/1.9.7 References: <200710252120.l9PLKYFJ041330@himinbjorg.tucs-beachin-obx-house.com> <200710251516.19505.fjwcash+freebsd@gmail.com> <20071027122454.GA15883@outcold.yadt.co.uk> In-Reply-To: <20071027122454.GA15883@outcold.yadt.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710291016.15064.fjwcash+freebsd@gmail.com> Cc: Subject: Re: 7.0-BETA1.5 ISO/ftp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 17:47:56 -0000 On October 27, 2007 05:24 am David Taylor wrote: > On Thu, 25 Oct 2007, Freddie Cash wrote: > > On October 25, 2007 03:07 pm Erik Trulsson wrote: > > > But csup does not yet support CVS mode, so you can't use it to > > > maintain a local copy of the repository. For some people > > > (including me) this means that csup is not yet a suitable > > > replacement for CVSup. > > > > Maybe not, but for the bulk of the users of cvsup, csup is a drop-in > > replacement. :) As with most things in Unix-land, there's more than > > one way to do things, and every one will defend to the death their > > way of doing things. :D > > I think the point is there _isn't_ more than one way to cvsup the CVS > repo - csup currently cannot do that. Fine, to end the arguments: for non-developer, "normal" users, who only use cvsup to update their source tree for a normal buildworld cycle (and for the ports tree for those who haven't moved to portsnap), csup is a drop-in replacement for cvsup. There, does that make the lot of you pedants happy? :D -- Freddie Cash, LPIC-2 CCNT CCLP Network Support Technician School District 73 (250) 377-HELP [377-4357] fjwcash+freebsd@gmail.com From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 18:04:28 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35A8B16A469 for ; Mon, 29 Oct 2007 18:04:28 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outM.internet-mail-service.net (outM.internet-mail-service.net [216.240.47.236]) by mx1.freebsd.org (Postfix) with ESMTP id 1A3C713C4B3 for ; Mon, 29 Oct 2007 18:04:19 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Mon, 29 Oct 2007 11:03:58 -0700 X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (nat.ironport.com [63.251.108.100]) by idiom.com (Postfix) with ESMTP id 45BD012684D; Mon, 29 Oct 2007 11:03:58 -0700 (PDT) Message-ID: <472620AD.8070905@elischer.org> Date: Mon, 29 Oct 2007 11:04:29 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Rui Paulo References: <47241E9C.7000605@elischer.org> <472551FE.3020703@elischer.org> <38C11A33-7BA8-46DF-A9DB-E7677DF41885@FreeBSD.org> In-Reply-To: <38C11A33-7BA8-46DF-A9DB-E7677DF41885@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: learned something about coretemp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 18:04:28 -0000 Rui Paulo wrote: > > On 29 Oct 2007, at 03:22, Julian Elischer wrote: > >> Rui Paulo wrote: >>> On 10/28/07, Julian Elischer wrote: >>>> never kldload it on an 8 year old system. >>>> >>>> *bewm* >>>> >>>> I presume that my 8 YO inspiron 7500 doesn't have whatever is needed, >>>> but, "*Bewm*" is probably a less than optimal reaction. >>> That has been reported in the past. It's Intel's fault, not ours. >>> The spec says that if you issue a CPUID you should be able to tell if >>> the CPU has the temperature sensors regardless of the CPU model, but >>> on old systems these CPUID call "returns true". >> >> maybe we should just return true to part of the mail seems missing.. I think it went on something like: ...the startup routines for this module only of the cpu seems new enough. > > I'm sorry, but what do you mean? > > -- > Rui Paulo From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 18:15:58 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 634A816A420; Mon, 29 Oct 2007 18:15:58 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [210.51.165.229]) by mx1.freebsd.org (Postfix) with ESMTP id 45CB213C4B7; Mon, 29 Oct 2007 18:15:56 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from localhost (tarsier.geekcn.org [210.51.165.229]) by tarsier.geekcn.org (Postfix) with ESMTP id B81A8EB7FFD; Mon, 29 Oct 2007 12:29:55 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([210.51.165.229]) by localhost (mail.geekcn.org [210.51.165.229]) (amavisd-new, port 10024) with ESMTP id MJcCL8tUHkPs; Mon, 29 Oct 2007 12:29:48 +0800 (CST) Received: from LI-Xins-MacBook.local (c-67-161-39-180.hsd1.ca.comcast.net [67.161.39.180]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id 515EAEB0E91; Mon, 29 Oct 2007 12:29:45 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type; b=hmBgSFrJ+tvg8kirjBc7nJHlmK2XE4z/IHN9j0pOMFzVsHDAQvhVNHHZ0Wb+pR3Se IqNTRWLdDzLC+JjjhjOlw== Message-ID: <472561A7.60108@delphij.net> Date: Sun, 28 Oct 2007 21:29:27 -0700 From: LI Xin Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: qpadla@gmail.com References: <20070917194009.W84177@woozle.rinet.ru> <200709171912.09060.qpadla@gmail.com> <46EEA89F.3060606@delphij.net> <200709241223.52140.qpadla@gmail.com> In-Reply-To: <200709241223.52140.qpadla@gmail.com> X-Enigmail-Version: 0.95.5 OpenPGP: url=http://www.delphij.net/delphij.asc Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enig422B78417B2D4AFA177E69EB" Cc: MingyanGuo , d@delphij.net, current@freebsd.org, Dmitry Morozovsky , freebsd-current@freebsd.org, delphij@freebsd.org, Howard Su Subject: Re: tmpfs on contemporary -current: panic: locked against myself X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 18:15:58 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig422B78417B2D4AFA177E69EB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Nikolay Pavlov wrote: > On Monday 17 September 2007 19:17:35 LI Xin wrote: >> Nikolay Pavlov wrote: >> [...] >> >>> Yes it's still need more fixes. I have send a mail to delphij >>> regarding this one panic: >>> http://docs.freebsd.org/cgi/mid.cgi?200708201848.22157.qpadla >>> But with out any response. May be he is busy :( >> Sorry I am aware of the issue and am busy for $REALJOB these days. I >> have cc'ed howardsu@ and mingyanguo@ to see if they have some >> suggestions. The problem seems to be a race condition caused by >> incorrect VFS related locking, but diagnosing it is relatively hard. >> >> I'll try to pick up with the development in early October. Before tha= t >> I can only do some small scale bugfixes rather than investing more tim= e >> into tmpfs stuff... :-( >> >> Cheers, >=20 > Just want to be sure that no one lose this. Here is a PR: > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D116600 Can not reproduce here. Could you please confirm that this still persists for latest RELENG_7? Cheers, --=20 Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! --------------enig422B78417B2D4AFA177E69EB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHJWGnOfuToMruuMARCuqwAJ41zHuG7FWTE+tmIpDFDRvz4WZE8QCgitGH 7W82UNjz8fazV03URX3UC2A= =KE1J -----END PGP SIGNATURE----- --------------enig422B78417B2D4AFA177E69EB-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 18:15:58 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 634A816A420; Mon, 29 Oct 2007 18:15:58 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [210.51.165.229]) by mx1.freebsd.org (Postfix) with ESMTP id 45CB213C4B7; Mon, 29 Oct 2007 18:15:56 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from localhost (tarsier.geekcn.org [210.51.165.229]) by tarsier.geekcn.org (Postfix) with ESMTP id B81A8EB7FFD; Mon, 29 Oct 2007 12:29:55 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([210.51.165.229]) by localhost (mail.geekcn.org [210.51.165.229]) (amavisd-new, port 10024) with ESMTP id MJcCL8tUHkPs; Mon, 29 Oct 2007 12:29:48 +0800 (CST) Received: from LI-Xins-MacBook.local (c-67-161-39-180.hsd1.ca.comcast.net [67.161.39.180]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id 515EAEB0E91; Mon, 29 Oct 2007 12:29:45 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type; b=hmBgSFrJ+tvg8kirjBc7nJHlmK2XE4z/IHN9j0pOMFzVsHDAQvhVNHHZ0Wb+pR3Se IqNTRWLdDzLC+JjjhjOlw== Message-ID: <472561A7.60108@delphij.net> Date: Sun, 28 Oct 2007 21:29:27 -0700 From: LI Xin Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: qpadla@gmail.com References: <20070917194009.W84177@woozle.rinet.ru> <200709171912.09060.qpadla@gmail.com> <46EEA89F.3060606@delphij.net> <200709241223.52140.qpadla@gmail.com> In-Reply-To: <200709241223.52140.qpadla@gmail.com> X-Enigmail-Version: 0.95.5 OpenPGP: url=http://www.delphij.net/delphij.asc Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enig422B78417B2D4AFA177E69EB" Cc: MingyanGuo , d@delphij.net, current@freebsd.org, Dmitry Morozovsky , freebsd-current@freebsd.org, delphij@freebsd.org, Howard Su Subject: Re: tmpfs on contemporary -current: panic: locked against myself X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 18:15:58 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig422B78417B2D4AFA177E69EB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Nikolay Pavlov wrote: > On Monday 17 September 2007 19:17:35 LI Xin wrote: >> Nikolay Pavlov wrote: >> [...] >> >>> Yes it's still need more fixes. I have send a mail to delphij >>> regarding this one panic: >>> http://docs.freebsd.org/cgi/mid.cgi?200708201848.22157.qpadla >>> But with out any response. May be he is busy :( >> Sorry I am aware of the issue and am busy for $REALJOB these days. I >> have cc'ed howardsu@ and mingyanguo@ to see if they have some >> suggestions. The problem seems to be a race condition caused by >> incorrect VFS related locking, but diagnosing it is relatively hard. >> >> I'll try to pick up with the development in early October. Before tha= t >> I can only do some small scale bugfixes rather than investing more tim= e >> into tmpfs stuff... :-( >> >> Cheers, >=20 > Just want to be sure that no one lose this. Here is a PR: > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D116600 Can not reproduce here. Could you please confirm that this still persists for latest RELENG_7? Cheers, --=20 Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! --------------enig422B78417B2D4AFA177E69EB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHJWGnOfuToMruuMARCuqwAJ41zHuG7FWTE+tmIpDFDRvz4WZE8QCgitGH 7W82UNjz8fazV03URX3UC2A= =KE1J -----END PGP SIGNATURE----- --------------enig422B78417B2D4AFA177E69EB-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 18:24:10 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED0E816A41A for ; Mon, 29 Oct 2007 18:24:10 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: from akis.salford.ac.uk (akis.salford.ac.uk [146.87.0.14]) by mx1.freebsd.org (Postfix) with SMTP id 68BBB13C4BC for ; Mon, 29 Oct 2007 18:24:09 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 26412 invoked by uid 98); 29 Oct 2007 09:59:13 +0000 Received: from 146.87.255.121 by akis.salford.ac.uk (envelope-from , uid 401) with qmail-scanner-2.01 (clamdscan: 0.90/3843. spamassassin: 3.1.8. Clear:RC:1(146.87.255.121):. Processed in 0.046486 secs); 29 Oct 2007 09:59:13 -0000 Received: from rust.salford.ac.uk (HELO rust.salford.ac.uk) (146.87.255.121) by akis.salford.ac.uk (qpsmtpd/0.3x.614) with SMTP; Mon, 29 Oct 2007 09:59:13 +0000 Received: (qmail 19318 invoked by uid 1002); 29 Oct 2007 09:59:11 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 29 Oct 2007 09:59:11 -0000 Date: Mon, 29 Oct 2007 09:59:11 +0000 (GMT) From: "Mark Powell" To: freebsd-current@freebsd.org Message-ID: <20071029092531.J99722@rust.salford.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: WRITE_DMA48 error causing loss of ZFS array X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 18:24:11 -0000 I've experienced several dma errors over the past few months with various incarnations of 7.0 which were all fixed. Seems I have a new one. Don't know if there was a connection, but this only occured after updating to 7.0-BETA1 last weekend. I have a small ufs mirror for /boot and everything else on one ZFS pool. I scrub my zpool in the early hours every monday morning. Last Monday when I got to the console I saw DMA_ERRORs slowly scrolling up the screen. Could type 'root' to login prompt on virtual terminal but it just hung. Nothing I could do apart from reset. When it came back it was fine AFAICT. Later that day I got the problem again. Reset and all ok. I then, confusingly, managed to successfully scrub the whole pool with no problems. However, again this morning I had the same symptoms. A couple of screenshots here, as nothing got logged, the pool seemed to be effectively unavailable: http://webhost.salford.ac.uk/aix502/29102007(001).thb.jpg http://webhost.salford.ac.uk/aix502/29102007(004).thb.jpg The errors all seemto be on one drive. AFAICT it had probably been going on for hours when I get to it and seems like it will continue this way forever. I've looked in the smartctl output for the drive (I do a short offline test everyday and a long offline test every Sunday) but nothing there. Ran the Hitachi Drive Fitness test on the drive and no problems reported. This is one of two drives on a JMB363 controller which is in IDE mode. If that makes a difference, as I've seen posts referring to problems with that controller, but think they might've been dealing with AHCI mode only? Is this a known problem? I've seen mention of known problems with ata, but it's hard to get a clear picture of what is currently outstanding from searching the last few month's -current. Also, why do I lose my zpool and have to reset? This one drive failing would not cause a problem for the zpool, as it has redundancy. However, why am I effectively losing the whole pool due to this error? I'll be glad to provide any more info. Many thanks in advance. -- Mark Powell - UNIX System Administrator - The University of Salford Information Services Division, Clifford Whitworth Building, Salford University, Manchester, M5 4WT, UK. Tel: +44 161 295 4837 Fax: +44 161 295 5888 www.pgp.com for PGP key From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 18:27:28 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C9E916A477; Mon, 29 Oct 2007 18:27:28 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id 7308E13C4DB; Mon, 29 Oct 2007 18:27:27 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.14.1/8.13.8) with ESMTP id l9TI9OYQ093696; Mon, 29 Oct 2007 14:09:25 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.14.1/8.14.1) with ESMTP id l9TI9O17074104; Mon, 29 Oct 2007 14:09:24 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 38CB173039; Mon, 29 Oct 2007 13:09:23 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20071029180924.38CB173039@freebsd-current.sentex.ca> Date: Mon, 29 Oct 2007 13:09:23 -0500 (EST) X-Virus-Scanned: ClamAV version 0.91.1, clamav-milter version 0.91.1 on clamscanner2 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 18:27:28 -0000 TB --- 2007-10-29 17:55:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-10-29 17:55:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2007-10-29 17:55:00 - cleaning the object tree TB --- 2007-10-29 17:55:56 - checking out the source tree TB --- 2007-10-29 17:55:56 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2007-10-29 17:55:56 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-10-29 18:06:46 - building world (CFLAGS=-O2 -pipe) TB --- 2007-10-29 18:06:46 - cd /src TB --- 2007-10-29 18:06:46 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 29 18:06:47 UTC 2007 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree [...] ===> gnu/usr.bin/texinfo/infokey (obj) /obj/amd64/src/gnu/usr.bin/texinfo/infokey created for /src/gnu/usr.bin/texinfo/infokey ===> gnu/usr.bin/texinfo/install-info (obj) /obj/amd64/src/gnu/usr.bin/texinfo/install-info created for /src/gnu/usr.bin/texinfo/install-info ===> gnu/usr.bin/texinfo/texindex (obj) /obj/amd64/src/gnu/usr.bin/texinfo/texindex created for /src/gnu/usr.bin/texinfo/texindex ===> gnu/usr.bin/texinfo/doc (obj) mkdir: Permission denied *** Error code 126 Stop in /src/gnu/usr.bin/texinfo/doc. *** Error code 1 Stop in /src/gnu/usr.bin/texinfo. *** Error code 1 Stop in /src/gnu/usr.bin. *** Error code 1 Stop in /src/gnu. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-10-29 18:09:23 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-10-29 18:09:23 - ERROR: failed to build world TB --- 2007-10-29 18:09:23 - tinderbox aborted TB --- 1.05 user 3.79 system 862.45 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 18:29:11 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A3ED16A46B; Mon, 29 Oct 2007 18:29:11 +0000 (UTC) (envelope-from freebsd@masm.elcom.ru) Received: from smtp.elcom.ru (smtp.elcom.ru [84.53.200.28]) by mx1.freebsd.org (Postfix) with ESMTP id 84B3E13C4AA; Mon, 29 Oct 2007 18:29:10 +0000 (UTC) (envelope-from freebsd@masm.elcom.ru) Received: by smtp.elcom.ru (Postfix, from userid 65534) id DC62B3D8734; Mon, 29 Oct 2007 16:32:14 +0300 (MSK) Received: from VMHOST (dsl-212-78.elcom.ru [84.53.212.78]) by smtp.elcom.ru (Postfix) with ESMTP id 75ED63D8725; Mon, 29 Oct 2007 16:32:14 +0300 (MSK) Date: Mon, 29 Oct 2007 16:32:21 +0300 From: "Victor M. Blood" X-Mailer: The Bat! (v3.80.06) Professional Organization: Home Programming Inc. X-Priority: 3 (Normal) Message-ID: <1618834866.20071029163221@masm.elcom.ru> To: Darren Reed , freebsd-current@freebsd.org In-Reply-To: <47200F5E.9070104@freebsd.org> References: <359284519.20071018014832@masm.elcom.ru> <200710172357.18221.max@love2party.net> <6210619899.20071018020530@masm.elcom.ru> <200710180021.39250.max@love2party.net> <1564774296.20071018172432@masm.elcom.ru> <47200F5E.9070104@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: ipfilter cannot be build within because warning's are present X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 18:29:11 -0000 On 25.10.2007, Darren Reed wrote: > Please try the attached patch. #pwd /var/tmp ls ip_* ip_filter4.1.28 #patch <28a.patch all patches failed... ++++ Script started on Mon Oct 29 17:29:30 2007 release# popd=08=08=08wd=1B[K=08=08atch -p4 < ip_fil_freebsd.c.patch=08=1B[= K=08=1B[K=08=1B[K=08=1B[K=08=1B[K=08=1B[K=08=1B[K=08=1B[K=08=1B[K=08=1B[K= =08=1B[K=08=1B[K=08=1B[K=08=1B[K=08=1B[K=08=1B[K=08=1B[K=08=1B[K=08=1B[K=08= =1B[K=08=1B[K=08=1B[K=08=08=1B[K=08=08=1B[K=08=1B[K=08=1B[K=08 <28a.patch= =20 Hmm... Looks like a context diff to me... The text leading up to this was: -------------------------- |Only in ip_fil4.1.28a/BSD: NetBSD-4.99.33-i386 |Only in ip_fil4.1.28a/BSD: tools |diff -cr ip_fil4.1.28/fil.c ip_fil4.1.28a/fil.c |*** ip_fil4.1.28/fil.c Wed Oct 10 02:27:20 2007 |--- ip_fil4.1.28a/fil.c Sat Oct 20 22:30:01 2007 -------------------------- Patching file ip_fil4.1.28/fil.c using Plan A... (Fascinating--this is really a new-style context diff but without the telltale extra asterisks on the *** line that usually indicate the new style...) Hunk #1 failed at 7019. Hunk #2 failed at 7034. Hunk #3 failed at 7176. Hunk #4 failed at 7183. 4 out of 4 hunks failed--saving rejects to ip_fil4.1.28/fil.c.rej Hmm... The next patch looks like a context diff to me... The text leading up to this was: -------------------------- |diff -cr ip_fil4.1.28/ip_fil_freebsd.c ip_fil4.1.28a/ip_fil_freebsd.c |*** ip_fil4.1.28/ip_fil_freebsd.c Thu Sep 20 05:51:50 2007 |--- ip_fil4.1.28a/ip_fil_freebsd.c Sat Oct 20 22:29:37 2007 -------------------------- Patching file ip_fil4.1.28/ip_fil_freebsd.c using Plan A... (Fascinating--this is really a new-style context diff but without the telltale extra asterisks on the *** line that usually indicate the new style...) Hunk #1 failed at 345. 1 out of 1 hunks failed--saving rejects to ip_fil4.1.28/ip_fil_freebsd.c.rej Hmm... The next patch looks like a context diff to me... The text leading up to this was: -------------------------- |diff -cr ip_fil4.1.28/ip_fil_netbsd.c ip_fil4.1.28a/ip_fil_netbsd.c |*** ip_fil4.1.28/ip_fil_netbsd.c Sat Sep 15 20:33:58 2007 |--- ip_fil4.1.28a/ip_fil_netbsd.c Sat Oct 20 22:52:03 2007 -------------------------- Patching file ip_fil4.1.28/ip_fil_netbsd.c using Plan A... (Fascinating--this is really a new-style context diff but without the telltale extra asterisks on the *** line that usually indicate the new style...) Hunk #1 failed at 406. 1 out of 1 hunks failed--saving rejects to ip_fil4.1.28/ip_fil_netbsd.c.rej Hmm... The next patch looks like a context diff to me... The text leading up to this was: -------------------------- |diff -cr ip_fil4.1.28/ip_nat.c ip_fil4.1.28a/ip_nat.c |*** ip_fil4.1.28/ip_nat.c Tue Oct 16 03:08:10 2007 |--- ip_fil4.1.28a/ip_nat.c Sat Oct 20 22:48:19 2007 -------------------------- Patching file ip_fil4.1.28/ip_nat.c using Plan A... Hunk #1 failed at 187. (Fascinating--this is really a new-style context diff but without the telltale extra asterisks on the *** line that usually indicate the new style...) Hunk #2 failed at 817. Hunk #3 failed at 888. Hunk #4 failed at 1190. Hunk #5 failed at 1201. Hunk #6 failed at 1213. Hunk #7 failed at 1229. Hunk #8 failed at 1247. Hunk #9 failed at 1267. Hunk #10 failed at 1287. Hunk #11 failed at 1361. 11 out of 11 hunks failed--saving rejects to ip_fil4.1.28/ip_nat.c.rej Hmm... The next patch looks like a context diff to me... The text leading up to this was: -------------------------- |diff -cr ip_fil4.1.28/ip_pool.c ip_fil4.1.28a/ip_pool.c |*** ip_fil4.1.28/ip_pool.c Wed Oct 10 02:45:37 2007 |--- ip_fil4.1.28a/ip_pool.c Wed Oct 24 19:59:13 2007 -------------------------- Patching file ip_fil4.1.28/ip_pool.c using Plan A... Hunk #1 failed at 977. 1 out of 1 hunks failed--saving rejects to ip_fil4.1.28/ip_pool.c.rej Hmm... The next patch looks like a context diff to me... The text leading up to this was: -------------------------- |Only in ip_fil4.1.28a: ip_rules.h |diff -cr ip_fil4.1.28/ip_state.c ip_fil4.1.28a/ip_state.c |*** ip_fil4.1.28/ip_state.c Tue Oct 16 02:33:23 2007 |--- ip_fil4.1.28a/ip_state.c Sat Oct 20 22:47:57 2007 -------------------------- Patching file ip_fil4.1.28/ip_state.c using Plan A... (Fascinating--this is really a new-style context diff but without the telltale extra asterisks on the *** line that usually indicate the new style...) Hunk #1 failed at 653. Hunk #2 failed at 672. Hunk #3 failed at 683. 3 out of 3 hunks failed--saving rejects to ip_fil4.1.28/ip_state.c.rej Hmm... The next patch looks like a context diff to me... The text leading up to this was: -------------------------- |Only in ip_fil4.1.28a: ipf |Only in ip_fil4.1.28a: ipftest |Only in ip_fil4.1.28a: ipmon |Only in ip_fil4.1.28a: ipnat |Only in ip_fil4.1.28a: ippool |Only in ip_fil4.1.28a: ipscan |Only in ip_fil4.1.28a: ipsyncm |Only in ip_fil4.1.28a: ipsyncs |diff -cr ip_fil4.1.28/lib/getproto.c ip_fil4.1.28a/lib/getproto.c |*** ip_fil4.1.28/lib/getproto.c Fri Jun 16 10:21:00 2006 |--- ip_fil4.1.28a/lib/getproto.c Sat Oct 20 22:59:02 2007 -------------------------- Patching file ip_fil4.1.28/lib/getproto.c using Plan A... Hunk #1 failed at 23. 1 out of 1 hunks failed--saving rejects to ip_fil4.1.28/lib/getproto.c.rej Hmm... The next patch looks like a context diff to me... The text leading up to this was: -------------------------- |diff -cr ip_fil4.1.28/lib/printproto.c ip_fil4.1.28a/lib/printproto.c |*** ip_fil4.1.28/lib/printproto.c Fri Jun 16 10:21:14 2006 |--- ip_fil4.1.28a/lib/printproto.c Sat Oct 20 22:59:49 2007 -------------------------- Patching file ip_fil4.1.28/lib/printproto.c using Plan A... Hunk #1 failed at 29. 1 out of 1 hunks failed--saving rejects to ip_fil4.1.28/lib/printproto.c.rej Hmm... The next patch looks like a context diff to me... The text leading up to this was: -------------------------- |Only in ip_fil4.1.28a/net: done |Only in ip_fil4.1.28a/net: radix_ipf.h |Only in ip_fil4.1.28a/netinet: bpf-ipf.h |Only in ip_fil4.1.28a/netinet: done |Only in ip_fil4.1.28a/netinet: ip_auth.h |Only in ip_fil4.1.28a/netinet: ip_compat.h |Only in ip_fil4.1.28a/netinet: ip_fil.h |Only in ip_fil4.1.28a/netinet: ip_frag.h |Only in ip_fil4.1.28a/netinet: ip_ftp_pxy.c |Only in ip_fil4.1.28a/netinet: ip_h323_pxy.c |Only in ip_fil4.1.28a/netinet: ip_htable.h |Only in ip_fil4.1.28a/netinet: ip_ipsec_pxy.c |Only in ip_fil4.1.28a/netinet: ip_irc_pxy.c |Only in ip_fil4.1.28a/netinet: ip_lookup.h |Only in ip_fil4.1.28a/netinet: ip_nat.h |Only in ip_fil4.1.28a/netinet: ip_netbios_pxy.c |Only in ip_fil4.1.28a/netinet: ip_pool.h |Only in ip_fil4.1.28a/netinet: ip_pptp_pxy.c |Only in ip_fil4.1.28a/netinet: ip_proxy.h |Only in ip_fil4.1.28a/netinet: ip_raudio_pxy.c |Only in ip_fil4.1.28a/netinet: ip_rcmd_pxy.c |Only in ip_fil4.1.28a/netinet: ip_rpcb_pxy.c |Only in ip_fil4.1.28a/netinet: ip_rules.h |Only in ip_fil4.1.28a/netinet: ip_scan.h |Only in ip_fil4.1.28a/netinet: ip_state.h |Only in ip_fil4.1.28a/netinet: ip_sync.h |Only in ip_fil4.1.28a/netinet: ipf.h |Only in ip_fil4.1.28a/netinet: ipl.h |Only in ip_fil4.1.28a/netinet: ipmon.h |Only in ip_fil4.1.28a/netinet: ipt.h |Only in ip_fil4.1.28a/netinet: kmem.h |Only in ip_fil4.1.28a/netinet: linux.h |Only in ip_fil4.1.28a/netinet: md5.h |Only in ip_fil4.1.28a/netinet: opts.h |Only in ip_fil4.1.28a/netinet: pcap-ipf.h |Only in ip_fil4.1.28a/netinet: radix_ipf.h |Only in ip_fil4.1.28a/netinet: snoop.h |Only in ip_fil4.1.28a/netinet: tcpip.h |Only in ip_fil4.1.28a/test/expected: i19 |Only in ip_fil4.1.28a/test: f1 |Only in ip_fil4.1.28a/test: f10 |Only in ip_fil4.1.28a/test: f11 |Only in ip_fil4.1.28a/test: f12 |Only in ip_fil4.1.28a/test: f13 |Only in ip_fil4.1.28a/test: f14 |Only in ip_fil4.1.28a/test: f15 |Only in ip_fil4.1.28a/test: f16 |Only in ip_fil4.1.28a/test: f17 |Only in ip_fil4.1.28a/test: f18 |Only in ip_fil4.1.28a/test: f19 |Only in ip_fil4.1.28a/test: f2 |Only in ip_fil4.1.28a/test: f20 |Only in ip_fil4.1.28a/test: f24 |Only in ip_fil4.1.28a/test: f3 |Only in ip_fil4.1.28a/test: f4 |Only in ip_fil4.1.28a/test: f5 |Only in ip_fil4.1.28a/test: f6 |Only in ip_fil4.1.28a/test: f7 |Only in ip_fil4.1.28a/test: f8 |Only in ip_fil4.1.28a/test: f9 |Only in ip_fil4.1.28a/test: i1 |Only in ip_fil4.1.28a/test: i10 |Only in ip_fil4.1.28a/test: i11 |Only in ip_fil4.1.28a/test: i12 |Only in ip_fil4.1.28a/test: i13 |Only in ip_fil4.1.28a/test: i14 |Only in ip_fil4.1.28a/test: i15 |Only in ip_fil4.1.28a/test: i16 |Only in ip_fil4.1.28a/test: i17 |Only in ip_fil4.1.28a/test: i18 |Only in ip_fil4.1.28a/test: i19 |Only in ip_fil4.1.28a/test: i2 |Only in ip_fil4.1.28a/test: i20 |Only in ip_fil4.1.28a/test: i21 |Only in ip_fil4.1.28a/test: i3 |Only in ip_fil4.1.28a/test: i4 |Only in ip_fil4.1.28a/test: i5 |Only in ip_fil4.1.28a/test: i6 |Only in ip_fil4.1.28a/test: i7 |Only in ip_fil4.1.28a/test: i8 |Only in ip_fil4.1.28a/test: i9 |Only in ip_fil4.1.28a/test: in1 |Only in ip_fil4.1.28a/test: in2 |Only in ip_fil4.1.28a/test: in3 |Only in ip_fil4.1.28a/test: in4 |Only in ip_fil4.1.28a/test: in5 |Only in ip_fil4.1.28a/test: in6 |diff -cr ip_fil4.1.28/test/input/n9 ip_fil4.1.28a/test/input/n9 |*** ip_fil4.1.28/test/input/n9 Mon May 17 08:46:32 2004 |--- ip_fil4.1.28a/test/input/n9 Sat Oct 20 22:56:06 2007 -------------------------- Patching file ip_fil4.1.28/test/input/n9 using Plan A... Hunk #1 failed at 1. (Fascinating--this is really a new-style context diff but without the telltale extra asterisks on the *** line that usually indicate the new style...) Hunk #2 failed at 7. Hunk #3 failed at 15. Hunk #4 failed at 23. 4 out of 4 hunks failed--saving rejects to ip_fil4.1.28/test/input/n9.rej Hmm... The next patch looks like a context diff to me... The text leading up to this was: -------------------------- |Only in ip_fil4.1.28a/test: ip1 |Only in ip_fil4.1.28a/test: ip2 |Only in ip_fil4.1.28a/test: ipf5 |Only in ip_fil4.1.28a/test: ipv6.1 |Only in ip_fil4.1.28a/test: ipv6.2 |Only in ip_fil4.1.28a/test: ipv6.3 |Only in ip_fil4.1.28a/test: ipv6.5 |Only in ip_fil4.1.28a/test: ipv6.6 |Only in ip_fil4.1.28a/test: l1 |Only in ip_fil4.1.28a/test: n1 |Only in ip_fil4.1.28a/test: n10 |Only in ip_fil4.1.28a/test: n11 |Only in ip_fil4.1.28a/test: n12 |Only in ip_fil4.1.28a/test: n13 |Only in ip_fil4.1.28a/test: n14 |Only in ip_fil4.1.28a/test: n16 |Only in ip_fil4.1.28a/test: n2 |Only in ip_fil4.1.28a/test: n3 |Only in ip_fil4.1.28a/test: n4 |Only in ip_fil4.1.28a/test: n5 |Only in ip_fil4.1.28a/test: n6 |Only in ip_fil4.1.28a/test: n7 |Only in ip_fil4.1.28a/test: n8 |Only in ip_fil4.1.28a/test: n9 |Only in ip_fil4.1.28a/test: ni1 |Only in ip_fil4.1.28a/test: ni10 |Only in ip_fil4.1.28a/test: ni11 |Only in ip_fil4.1.28a/test: ni12 |Only in ip_fil4.1.28a/test: ni13 |Only in ip_fil4.1.28a/test: ni14 |Only in ip_fil4.1.28a/test: ni15 |Only in ip_fil4.1.28a/test: ni16 |Only in ip_fil4.1.28a/test: ni19 |Only in ip_fil4.1.28a/test: ni2 |Only in ip_fil4.1.28a/test: ni20 |Only in ip_fil4.1.28a/test: ni21 |Only in ip_fil4.1.28a/test: ni23 |Only in ip_fil4.1.28a/test: ni3 |Only in ip_fil4.1.28a/test: ni4 |Only in ip_fil4.1.28a/test: ni5 |Only in ip_fil4.1.28a/test: ni6 |Only in ip_fil4.1.28a/test: ni7 |Only in ip_fil4.1.28a/test: ni8 |Only in ip_fil4.1.28a/test: ni9 |Only in ip_fil4.1.28a/test: p1 |Only in ip_fil4.1.28a/test: p2 |Only in ip_fil4.1.28a/test: p3 |Only in ip_fil4.1.28a/test: p5 |Only in ip_fil4.1.28a/test: results |diff -cr ip_fil4.1.28/tools/ipmon.c ip_fil4.1.28a/tools/ipmon.c |*** ip_fil4.1.28/tools/ipmon.c Thu Sep 20 05:51:56 2007 |--- ip_fil4.1.28a/tools/ipmon.c Sat Oct 20 23:02:04 2007 -------------------------- Patching file ip_fil4.1.28/tools/ipmon.c using Plan A... (Fascinating--this is really a new-style context diff but without the telltale extra asterisks on the *** line that usually indicate the new style...) Hunk #1 failed at 419. 1 out of 1 hunks failed--saving rejects to ip_fil4.1.28/tools/ipmon.c.rej done release# exirt=08=1B[K=08=1B[Kt exit Script done on Mon Oct 29 17:29:48 2007 --=20 With all regards, Victor M. Blood. mailto: freebsd@masm.elcom.ru FTN: 2:5024/1.95@Fidonet.org, ICQ#3567656 From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 18:34:17 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9613E16A41A for ; Mon, 29 Oct 2007 18:34:17 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by mx1.freebsd.org (Postfix) with ESMTP id 30DD913C4A3 for ; Mon, 29 Oct 2007 18:34:07 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1304267nfb for ; Mon, 29 Oct 2007 11:33:53 -0700 (PDT) Received: by 10.86.95.20 with SMTP id s20mr4637769fgb.1193649136797; Mon, 29 Oct 2007 02:12:16 -0700 (PDT) Received: from ?172.17.9.98? ( [193.136.24.243]) by mx.google.com with ESMTPS id v23sm11915900fkd.2007.10.29.02.12.15 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 29 Oct 2007 02:12:15 -0700 (PDT) In-Reply-To: <472551FE.3020703@elischer.org> References: <47241E9C.7000605@elischer.org> <472551FE.3020703@elischer.org> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <38C11A33-7BA8-46DF-A9DB-E7677DF41885@FreeBSD.org> Content-Transfer-Encoding: 7bit From: Rui Paulo Date: Mon, 29 Oct 2007 09:12:09 +0000 To: Julian Elischer X-Mailer: Apple Mail (2.752.3) Sender: Rui Paulo Cc: FreeBSD Current Subject: Re: learned something about coretemp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 18:34:17 -0000 On 29 Oct 2007, at 03:22, Julian Elischer wrote: > Rui Paulo wrote: >> On 10/28/07, Julian Elischer wrote: >>> never kldload it on an 8 year old system. >>> >>> *bewm* >>> >>> I presume that my 8 YO inspiron 7500 doesn't have whatever is >>> needed, >>> but, "*Bewm*" is probably a less than optimal reaction. >> That has been reported in the past. It's Intel's fault, not ours. >> The spec says that if you issue a CPUID you should be able to tell if >> the CPU has the temperature sensors regardless of the CPU model, but >> on old systems these CPUID call "returns true". > > maybe we should just return true to I'm sorry, but what do you mean? -- Rui Paulo From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 18:34:36 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9E5716A469 for ; Mon, 29 Oct 2007 18:34:36 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id 3E52413C491 for ; Mon, 29 Oct 2007 18:34:29 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 82E2145EA7; Mon, 29 Oct 2007 07:39:00 +0100 (CET) Received: from localhost (154.81.datacomsa.pl [195.34.81.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 4042A456AB; Mon, 29 Oct 2007 07:38:54 +0100 (CET) Date: Mon, 29 Oct 2007 08:38:50 +0100 From: Pawel Jakub Dawidek To: Peter Losher Message-ID: <20071029073850.GB2176@garage.freebsd.pl> References: <47246FED.6000103@isc.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7JfCtLOvnd9MIVvH" Content-Disposition: inline In-Reply-To: <47246FED.6000103@isc.org> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-current@FreeBSD.ORG Subject: Re: Clearing out vdevs (can't create new zpool) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 18:34:36 -0000 --7JfCtLOvnd9MIVvH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 28, 2007 at 04:18:05AM -0700, Peter Losher wrote: > I have been poking around with our 16-port SATA RAID chassis (in JBOD > mode) with a fresh RELENG_7 internal build from Saturday. I only had > half the disks {da0-7) at first, when I brought over the second set > (da8-15), I destroyed the existing pool and then tried to create a new > one with all 16 disks, and encountered this error: >=20 > -=3D- > # zpool create tank raidz da{0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15} > cannot create 'tank': one or more vdevs refer to the same device > -=3D- The only time I saw such an error is when I accidentally gave the same disk name twice, eg.: # zpool create tank da0 da1 da0 I don't see you doing the same mistake, so something else has to be wrong. > I can create one with the second set of disks (and destroy/create again) > but somehow I have some old vdevs sitting around which is preventing me > from using the first set of disks. How can I clear them out? Can you show me the output of: # zpool status # zpool import # sysctl -b kern.geom.confxml If no pool is imported currently, you should be able to create your pool. If one of the disks is in use already (by something else than ZFS), the error message should be different... --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --7JfCtLOvnd9MIVvH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHJY4KForvXbEpPzQRAvzzAJ4hHoyOc17laMH1GC6shlKtES5tDwCgqW5J lstPyerL3gtaWCK1o6asjvE= =OArN -----END PGP SIGNATURE----- --7JfCtLOvnd9MIVvH-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 18:48:59 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E131D16A418 for ; Mon, 29 Oct 2007 18:48:59 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mx.egr.msu.edu (surfnturf.egr.msu.edu [35.9.37.164]) by mx1.freebsd.org (Postfix) with ESMTP id A861013C491 for ; Mon, 29 Oct 2007 18:48:59 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from localhost (localhost.egr.msu.edu [127.0.0.1]) by mx.egr.msu.edu (Postfix) with ESMTP id 042F22EB948 for ; Sun, 28 Oct 2007 22:43:57 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mx.egr.msu.edu ([127.0.0.1]) by localhost (surfnturf.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ll-UiXWH21YB for ; Sun, 28 Oct 2007 22:43:56 -0400 (EDT) Received: from localhost (daemon.egr.msu.edu [35.9.44.65]) by mx.egr.msu.edu (Postfix) with ESMTP id D05322EB944 for ; Sun, 28 Oct 2007 22:43:56 -0400 (EDT) Received: by localhost (Postfix, from userid 21281) id B8B5833C22; Sun, 28 Oct 2007 22:43:56 -0400 (EDT) Date: Sun, 28 Oct 2007 22:43:56 -0400 From: Adam McDougall To: freebsd-current@freebsd.org Message-ID: <20071029024356.GR3612@egr.msu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.16 (2007-06-09) Subject: zfs stuck, cannot do any I/O, processes in Disk Wait X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 18:49:00 -0000 I think I have had this happen at least once before, but someone else rebooted the system before I could see it. I have a server with a number of zfs filesystems mounted from a raidz, but it won't transfer any data. I'm not sure why its stuck. It is running 7.0-PRERELEASE Wed Oct 17 and I'm pretty sure it is WITHOUT vm_kern.c.2.patch. The system is amd64 and I have not seen a kmem panic since I raised kmem to 1.5G. I logged in to scp a file off of zfs, was able to ls -l to see the file but the scp hung before transferring any bytes. Now I cannot do a ls -l in that directory, /z. I noticed several days worth of rsync processes stuck in disk wait, it must have been in this state for several days. I have no urgent need to reboot this system, its more important to try to get a permanent fix. Please let me know what other information I can provide. 10:34PM up 10 days, 12:37, 3 users, load averages: 0.00, 0.00, 0.00 Stuck rsync processes (started from cron): 1:01AM 4:00AM 5:00AM Fri01AM Fri04AM Fri05AM Mon05AM Sat01AM Sat04AM Sat05AM Thu01AM Thu04AM Thu05AM Tue01AM Tue04AM Tue05AM Wed01AM Wed04AM Wed05AM # more /boot/loader.conf vm.kmem_size=1610612736 vm.kmem_size_max=1610612736 # sysctl -a | grep vnodes kern.maxvnodes: 100000 kern.minvnodes: 25000 vfs.freevnodes: 25000 vfs.wantfreevnodes: 25000 vfs.numvnodes: 49996 No errors in dmesg, and I can dd from the drives in the raidz1 fine. z/backups 101508480 0 101508480 0% /backups z/backups/a 101508480 0 101508480 0% /backups/a z/backups/b 149992448 48483968 101508480 32% /backups/b z/backups/c 219571968 118063488 101508480 54% /backups/c z/backups/d 105923968 4415488 101508480 4% /backups/d z/data 199868032 98359552 101508480 49% /data z 103982976 2474496 101508480 2% /z z/data4 206146688 104638208 101508480 51% /z/data4 z/mysqldb 102015488 507008 101508480 0% /z/mysqldb # zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT z 696G 540G 156G 77% ONLINE - # zpool status pool: z state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM z ONLINE 0 0 0 raidz1 ONLINE 0 0 0 ad4 ONLINE 0 0 0 ad6 ONLINE 0 0 0 ad8 ONLINE 0 0 0 errors: No known data errors From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 18:02:56 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE37816A475 for ; Mon, 29 Oct 2007 18:02:55 +0000 (UTC) (envelope-from jeff@rexdb.com) Received: from mail.rexdb.com (mx1.rexdb.com [216.243.161.232]) by mx1.freebsd.org (Postfix) with ESMTP id 972A313C4CB for ; Mon, 29 Oct 2007 18:02:44 +0000 (UTC) (envelope-from jeff@rexdb.com) Received: from Laptop.totaldiver.net (fl-209-26-20-205.sta.embarqhsd.net [209.26.20.205]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.rexdb.com (Postfix) with ESMTP id ECD0D228BABE for ; Mon, 29 Oct 2007 10:26:19 -0400 (EDT) Message-ID: <4725ED86.50005@rexdb.com> Date: Mon, 29 Oct 2007 10:26:14 -0400 From: Jeff Palmer User-Agent: Thunderbird 2.0.0.6 (X11/20071026) MIME-Version: 1.0 To: current@freebsd.org X-Enigmail-Version: 0.95.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 29 Oct 2007 23:35:53 +0000 Cc: Subject: ssh problems with 7.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 18:02:56 -0000 I have an odd problem with ssh on FreeBSD 7.0-BETA1, trying to connect to sshd on 6.2-RELEASE-p8/amd64. So far, it's not making any sense to me, so please bear with me as I try to explain it. On my home network, I have several machines running 7.0-BETA1, both amd64, and i386 versions. all machines get updated sources, and built world every morning. I also have 6.2-STABLE as well as RELENG_6_2 machines, on the same network. I have one specific machine, that none of my 7.x machines can connect to via ssh. using ssh in verbose mode doesn't offer anything in the way of diagnostics or hints. my 6.x machines can connect to it fine. Logging into the remote machine, I can run wireshark/tcpdump, and the tcp conversation looks like this: tcp handshake. 6.2 server sends version 7.x client sends version 7.x client sends a TCP Retransmission Unreassembled Packet to 6.x sshd 6.x sshd sends a RST, and that is the end of it. The ssh -vvvv user@host output ends in: debug1: Remote protocol version 2.0, remote software version OpenSSH_4.5p1 FreeBSD-20061110 debug1: match: OpenSSH_4.5p1 FreeBSD-20061110 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.5p1 FreeBSD-20061110 debug2: fd 3 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent Read from socket failed: Connection reset by peer Connections from the 6.2 box to any of the 7.x boxes work fine, and additionally connections from the 7.x box to *any other* 6.x box works. It's just this one specific machine. to re-iterate, the 6.x boxes can connect to this machine fine. it's only the 7.x boxes that get the error. Please let me know if I can provide more details, also I recieve current@ in daily digest mode, so please CC: me any replies. Thanks in advance. Jeff Palmer jpalmer @freenode IRC ##FreeBSD From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 19:09:44 2007 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DABB816A46D; Mon, 29 Oct 2007 19:09:44 +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 2117913C4D3; Mon, 29 Oct 2007 19:09:44 +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 401F146C02; Mon, 29 Oct 2007 14:00:32 -0500 (EST) Date: Mon, 29 Oct 2007 20:00:31 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: current@FreeBSD.org Message-ID: <20071029195933.G74595@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: trustedbsd-audit@TrustedBSD.org Subject: OpenBSM vendor import in HEAD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 19:09:45 -0000 FYI: I've just imported the latest OpenBSM 1.0 drop into the CVS HEAD. It basically contains minor bug fixes and tweaks, so shouldn't generate much disruption. The plan is to MFC it in a few days so that the bug fixes/tweaks appear in FreeBSD 7.0. Robert N M Watson Computer Laboratory University of Cambridge ---------- Forwarded message ---------- Date: Mon, 29 Oct 2007 18:40:32 +0000 (UTC) From: Robert Watson To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/contrib/openbsm - Imported sources rwatson 2007-10-29 18:40:32 UTC FreeBSD src repository src/contrib/openbsm - Imported sources Update of /home/ncvs/src/contrib/openbsm In directory repoman.freebsd.org:/tmp/cvs-serv23690 Log Message: Vendor import TrustedBSD OpenBSM 1.0, with the following change history since the last import: OpenBSM 1.0 - Fix bug in auditreduce(8) which resulted in a memory fault/crash when the user specified an event name with -m. - Remove AU_.* hard-coded audit class constants, as udit classes are now entirely dynamically configured using /etc/security/audit_class. MFC after: 3 days Obtained from: TrustedBSD Project Status: Vendor Tag: TrustedBSD Release Tags: OPENBSM_1_0 U src/contrib/openbsm/HISTORY U src/contrib/openbsm/LICENSE U src/contrib/openbsm/Makefile.am U src/contrib/openbsm/Makefile.in U src/contrib/openbsm/README U src/contrib/openbsm/TODO U src/contrib/openbsm/VERSION U src/contrib/openbsm/aclocal.m4 U src/contrib/openbsm/autogen.sh U src/contrib/openbsm/configure U src/contrib/openbsm/configure.ac U src/contrib/openbsm/bin/Makefile.am U src/contrib/openbsm/bin/Makefile.in U src/contrib/openbsm/bin/audit/Makefile.am U src/contrib/openbsm/bin/audit/Makefile.in U src/contrib/openbsm/bin/audit/audit.8 U src/contrib/openbsm/bin/audit/audit.c U src/contrib/openbsm/bin/auditd/Makefile.am U src/contrib/openbsm/bin/auditd/Makefile.in U src/contrib/openbsm/bin/auditd/audit_warn.c U src/contrib/openbsm/bin/auditd/auditd.8 U src/contrib/openbsm/bin/auditd/auditd.c U src/contrib/openbsm/bin/auditd/auditd.h U src/contrib/openbsm/bin/auditfilterd/Makefile.am U src/contrib/openbsm/bin/auditfilterd/Makefile.in U src/contrib/openbsm/bin/auditfilterd/auditfilterd.8 U src/contrib/openbsm/bin/auditfilterd/auditfilterd.c U src/contrib/openbsm/bin/auditfilterd/auditfilterd.h U src/contrib/openbsm/bin/auditfilterd/auditfilterd_conf.c U src/contrib/openbsm/bin/auditreduce/Makefile.am U src/contrib/openbsm/bin/auditreduce/Makefile.in U src/contrib/openbsm/bin/auditreduce/auditreduce.1 U src/contrib/openbsm/bin/auditreduce/auditreduce.c U src/contrib/openbsm/bin/auditreduce/auditreduce.h U src/contrib/openbsm/bin/praudit/Makefile.am U src/contrib/openbsm/bin/praudit/Makefile.in U src/contrib/openbsm/bin/praudit/praudit.1 U src/contrib/openbsm/bin/praudit/praudit.c U src/contrib/openbsm/bsm/Makefile.am U src/contrib/openbsm/bsm/Makefile.in C src/contrib/openbsm/bsm/audit.h U src/contrib/openbsm/bsm/audit_filter.h U src/contrib/openbsm/bsm/audit_internal.h U src/contrib/openbsm/bsm/audit_kevents.h U src/contrib/openbsm/bsm/audit_record.h U src/contrib/openbsm/bsm/audit_uevents.h U src/contrib/openbsm/bsm/libbsm.h U src/contrib/openbsm/compat/clock_gettime.h U src/contrib/openbsm/compat/endian.h U src/contrib/openbsm/compat/queue.h U src/contrib/openbsm/compat/strlcat.h U src/contrib/openbsm/config/config.guess U src/contrib/openbsm/config/config.h.in U src/contrib/openbsm/config/config.sub U src/contrib/openbsm/config/depcomp U src/contrib/openbsm/config/install-sh U src/contrib/openbsm/config/ltmain.sh U src/contrib/openbsm/config/missing C src/contrib/openbsm/etc/audit_class U src/contrib/openbsm/etc/audit_control C src/contrib/openbsm/etc/audit_event U src/contrib/openbsm/etc/audit_filter U src/contrib/openbsm/etc/audit_user U src/contrib/openbsm/etc/audit_warn U src/contrib/openbsm/libbsm/Makefile.am U src/contrib/openbsm/libbsm/Makefile.in U src/contrib/openbsm/libbsm/au_class.3 U src/contrib/openbsm/libbsm/au_control.3 U src/contrib/openbsm/libbsm/au_event.3 U src/contrib/openbsm/libbsm/au_free_token.3 U src/contrib/openbsm/libbsm/au_io.3 U src/contrib/openbsm/libbsm/au_mask.3 U src/contrib/openbsm/libbsm/au_open.3 U src/contrib/openbsm/libbsm/au_token.3 U src/contrib/openbsm/libbsm/au_user.3 U src/contrib/openbsm/libbsm/audit_submit.3 U src/contrib/openbsm/libbsm/bsm_audit.c U src/contrib/openbsm/libbsm/bsm_class.c U src/contrib/openbsm/libbsm/bsm_control.c U src/contrib/openbsm/libbsm/bsm_event.c U src/contrib/openbsm/libbsm/bsm_flags.c U src/contrib/openbsm/libbsm/bsm_io.c U src/contrib/openbsm/libbsm/bsm_mask.c U src/contrib/openbsm/libbsm/bsm_notify.c U src/contrib/openbsm/libbsm/bsm_token.c U src/contrib/openbsm/libbsm/bsm_user.c U src/contrib/openbsm/libbsm/libbsm.3 U src/contrib/openbsm/libbsm/bsm_wrappers.c U src/contrib/openbsm/man/Makefile.am U src/contrib/openbsm/man/Makefile.in U src/contrib/openbsm/man/audit.2 U src/contrib/openbsm/man/audit.log.5 U src/contrib/openbsm/man/audit_class.5 U src/contrib/openbsm/man/audit_control.5 U src/contrib/openbsm/man/audit_event.5 U src/contrib/openbsm/man/audit_user.5 U src/contrib/openbsm/man/audit_warn.5 U src/contrib/openbsm/man/auditctl.2 U src/contrib/openbsm/man/auditon.2 U src/contrib/openbsm/man/getaudit.2 U src/contrib/openbsm/man/getauid.2 U src/contrib/openbsm/man/setaudit.2 U src/contrib/openbsm/man/setauid.2 U src/contrib/openbsm/modules/Makefile.am U src/contrib/openbsm/modules/Makefile.in U src/contrib/openbsm/modules/auditfilter_noop/Makefile.am U src/contrib/openbsm/modules/auditfilter_noop/Makefile.in U src/contrib/openbsm/modules/auditfilter_noop/auditfilter_noop.c U src/contrib/openbsm/test/Makefile.am U src/contrib/openbsm/test/Makefile.in U src/contrib/openbsm/test/bsm/Makefile.am U src/contrib/openbsm/test/bsm/Makefile.in U src/contrib/openbsm/test/bsm/generate.c U src/contrib/openbsm/test/reference/arg32_record U src/contrib/openbsm/test/reference/arg32_token U src/contrib/openbsm/test/reference/data_record U src/contrib/openbsm/test/reference/data_token U src/contrib/openbsm/test/reference/file_record U src/contrib/openbsm/test/reference/file_token U src/contrib/openbsm/test/reference/header32_token U src/contrib/openbsm/test/reference/in_addr_record U src/contrib/openbsm/test/reference/in_addr_token U src/contrib/openbsm/test/reference/ip_record U src/contrib/openbsm/test/reference/ip_token U src/contrib/openbsm/test/reference/ipc_record U src/contrib/openbsm/test/reference/ipc_token U src/contrib/openbsm/test/reference/iport_record U src/contrib/openbsm/test/reference/iport_token U src/contrib/openbsm/test/reference/opaque_record U src/contrib/openbsm/test/reference/opaque_token U src/contrib/openbsm/test/reference/path_record U src/contrib/openbsm/test/reference/path_token U src/contrib/openbsm/test/reference/process32_record U src/contrib/openbsm/test/reference/process32_token U src/contrib/openbsm/test/reference/process64_record U src/contrib/openbsm/test/reference/process32ex_record-IPv4 U src/contrib/openbsm/test/reference/process32ex_record-IPv6 U src/contrib/openbsm/test/reference/process32ex_token-IPv4 U src/contrib/openbsm/test/reference/process32ex_token-IPv6 U src/contrib/openbsm/test/reference/process64_token U src/contrib/openbsm/test/reference/process64ex_record-IPv4 U src/contrib/openbsm/test/reference/process64ex_record-IPv6 U src/contrib/openbsm/test/reference/process64ex_token-IPv4 U src/contrib/openbsm/test/reference/process64ex_token-IPv6 U src/contrib/openbsm/test/reference/return32_record U src/contrib/openbsm/test/reference/return32_token U src/contrib/openbsm/test/reference/seq_record U src/contrib/openbsm/test/reference/seq_token U src/contrib/openbsm/test/reference/subject32_record U src/contrib/openbsm/test/reference/subject32_token U src/contrib/openbsm/test/reference/subject32ex_record U src/contrib/openbsm/test/reference/subject32ex_token-IPv4 U src/contrib/openbsm/test/reference/subject32ex_token-IPv6 U src/contrib/openbsm/test/reference/text_record U src/contrib/openbsm/test/reference/text_token U src/contrib/openbsm/test/reference/trailer_token U src/contrib/openbsm/test/reference/zonename_record U src/contrib/openbsm/test/reference/zonename_token U src/contrib/openbsm/test/samples/execve-long-args.trail U src/contrib/openbsm/tools/Makefile.am U src/contrib/openbsm/tools/Makefile.in U src/contrib/openbsm/tools/audump.c 3 conflicts created by this import. Use the following command to help the merge: cvs checkout -jTrustedBSD:yesterday -jTrustedBSD src/contrib/openbsm From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 19:13:13 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7B5F16A468 for ; Mon, 29 Oct 2007 19:13:13 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.freebsd.org (Postfix) with ESMTP id 9F6EC13C4C8 for ; Mon, 29 Oct 2007 19:13:09 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (localhost [127.0.0.1]) by bunrab.catwhisker.org (8.13.3/8.13.3) with ESMTP id l9TJ28iK084826 for ; Mon, 29 Oct 2007 12:02:08 -0700 (PDT) (envelope-from david@bunrab.catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.13.3/8.13.1/Submit) id l9TJ28IV084825 for current@freebsd.org; Mon, 29 Oct 2007 12:02:08 -0700 (PDT) (envelope-from david) Date: Mon, 29 Oct 2007 12:02:08 -0700 From: David Wolfskill To: current@freebsd.org Message-ID: <20071029190208.GD78150@bunrab.catwhisker.org> Mail-Followup-To: David Wolfskill , current@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3Pql8miugIZX0722" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: Detach of an0 induced kernel panic in 7.0-PRE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 19:13:14 -0000 --3Pql8miugIZX0722 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable This may well qualify as something for which the appropriate remedy is "Don't do that, then." :-} As is my habit,I built today's RELENG_6 on my laptop's slice 1, then booted it & updated ports, then booted RELENG_7 (on slice 3) and started building today's RELENG_7. Shortly thereafter, I headed in to work, leaving the laptop in the trunk of the car as I drove in (about 30 minutes),busily building stuff. Now, at home, I normally use the miniPCI wi0 NIC. Since I can't get the wi0 NIC to associate running RELENG_7 or HEAD, I use a PCMCIA an0 NIC at home when I run those. But at work, the access points are configured for 802.11g only -- no 802.11b compatibility. So there, I switch to the laptop's built-in xl0 NIC. So I got to my desk, started the Perk script I cobbled up to handle NIC transitions, wandered off to fill my water bottle, came back,and saw that the script was trying to get the an0 NIC to associate -- and then I realized that I had negelcted to plug the cable in to the xl0 NIC. Oh. :-( So I hot ^C to interrupt the script and plugged the cable in to the xl0 NIC. I was about to re-run the script and saw that I didn't yet have a command-line prompt. In an attempt to speed things up(!), I detached the an0 NIC. Boom! h252(7.0)[6] uname -a FreeBSD h252.dhw.mail-abuse.org. 7.0-BETA1 FreeBSD 7.0-BETA1 #573: Mon Oct = 29 10:24:52 PDT 2007 root@h252.dhw.mail-abuse.org.:/common/S3/obj/usr/s= rc/sys/CANARY i386 h252(7.0)[7]=20 h252(7.0)[1] cd /usr/obj/usr/src/sys/CANARY/ h252(7.0)[2] kgdb kernel.debug /var/crash/vmcore.5 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:= Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] =2E.. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: an0: RID access failed an0: detached Fatal trap 12: page fault while in kernel mode cpuid =3D 0; apic id =3D 00 fault virtual address =3D 0xc8283178 fault code =3D supervisor write, page not present instruction pointer =3D 0x20:0xc04daaf7 stack pointer =3D 0x28:0xe2987c5c frame pointer =3D 0x28:0xe2987c78 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 12 (swi4: clock sio) trap number =3D 12 panic: page fault cpuid =3D 0 Uptime: 31m46s Physical memory: 1011 MB Dumping 173 MB: 158 142 126 110 94 78 62 46 30 14 #0 doadump () at pcpu.h:195 195 __asm __volatile("movl %%fs:0,%0" : "=3Dr" (td)); (kgdb) bt #0 doadump () at pcpu.h:195 #1 0xc073b637 in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:4= 09 #2 0xc073b8f9 in panic (fmt=3DVariable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:563 #3 0xc0a005dc in trap_fatal (frame=3D0xe2987c1c, eva=3D3358077304) at /usr/src/sys/i386/i386/trap.c:872 #4 0xc0a00860 in trap_pfault (frame=3D0xe2987c1c, usermode=3D0, eva=3D3358= 077304) at /usr/src/sys/i386/i386/trap.c:785 #5 0xc0a011d5 in trap (frame=3D0xe2987c1c) at /usr/src/sys/i386/i386/trap.= c:463 #6 0xc09e71eb in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc04daaf7 in an_stats_update (xsc=3D0xc8282000) at atomic.h:149 #8 0xc074d7ea in softclock (dummy=3D0x0) at /usr/src/sys/kern/kern_timeout= .c:274 #9 0xc071ef0b in ithread_loop (arg=3D0xc3f0d2f0) at /usr/src/sys/kern/kern_intr.c:1036 #10 0xc071bc19 in fork_exit (callout=3D0xc071ed60 ,=20 arg=3D0xc3f0d2f0, frame=3D0xe2987d38) at /usr/src/sys/kern/kern_fork.c:= 796 #11 0xc09e7260 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:= 205 (kgdb)=20 Any hints would be welcome. (Save for this -- well, and the fact that I can't really use wi0(4) while running 7.x or 8 -- RELENG_7 seems OK so far.) I'm about to flip over to slice 4 (to build today's HEAD), but after that's done, I should be able to look at the crash dump a bit more. (And I'm fine with testing changes & patches -- given enough hints, I can cause moderate damage to unsuspecting source files, even.) Peace, david --=20 David H. Wolfskill david@catwhisker.org Proprietary data formats obfuscate, rather than disseminate, information. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --3Pql8miugIZX0722 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iEYEARECAAYFAkcmLi8ACgkQmprOCmdXAD0RXwCfbab8qYHTOWB6W3W94NP6DOEi vsoAn3Lxuz7j76qCTQu7dJksp2+pN6a2 =lh1g -----END PGP SIGNATURE----- --3Pql8miugIZX0722-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 19:22:38 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CE8816A475 for ; Mon, 29 Oct 2007 19:22:38 +0000 (UTC) (envelope-from rse@engelschall.com) Received: from visp1.engelschall.com (visp1.engelschall.com [195.30.6.144]) by mx1.freebsd.org (Postfix) with ESMTP id 31C4113C481 for ; Mon, 29 Oct 2007 19:22:36 +0000 (UTC) (envelope-from rse@engelschall.com) Received: by visp1.engelschall.com (Postfix, from userid 21100) id EB7351B44870; Mon, 29 Oct 2007 12:04:16 +0100 (CET) Received: by en1.engelschall.com (Postfix, from userid 10000) id 4C2E36DCCC; Mon, 29 Oct 2007 12:02:04 +0100 (CET) Date: Mon, 29 Oct 2007 12:02:04 +0100 From: "Ralf S. Engelschall" To: freebsd-current@freebsd.org Message-ID: <20071029110204.GA64046@engelschall.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: FreeBSD User-Agent: Mutt/1.5.16 OpenPKG/CURRENT (2007-06-09) Subject: "sigreturn: eflags = 0x80283" after medium-to-high load X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Ralf S. Engelschall" List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 19:22:38 -0000 Just FYI: When I compile lots of C++ code under 8.0 or 7.0 (both as of 2007-10-27 and running on ZFS inside a virtual machine) I'm still able to regularily bring the system into an unusable state. The effect is that first on the console the following kernel messages occur: sigreturn: eflags = 0x80283 sigreturn: eflags = 0x80297 Then after I type e.g. CTRL-C in my C++ compile session over SSH more such "sigreturn: eflags = 0x80283" occur on the console (and without bringing back a shell prompt on the SSH session). At this stage I also no longer can login via SSH through a new second SSH connection. Only on the console I still can perform a "sync; sync; sync; reboot" to rescue. In this situation even a regular "shutdown -r now" often just causes more "sigreturn: eflags = 0x80297" outputs but isn't really able to finally reboot the system. Hmmm... -- rse@FreeBSD.org Ralf S. Engelschall FreeBSD.org/~rse rse@engelschall.com FreeBSD committer www.engelschall.com From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 19:26:58 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9821A16A41B; Mon, 29 Oct 2007 19:26:58 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 9DECE13C4A7; Mon, 29 Oct 2007 19:26:55 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.8/8.13.8) with ESMTP id l9TCfpOq058442; Mon, 29 Oct 2007 08:41:51 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.14.1/8.14.1) with ESMTP id l9TCfpVr090050; Mon, 29 Oct 2007 08:41:51 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id BAE5473039; Mon, 29 Oct 2007 07:41:50 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20071029124150.BAE5473039@freebsd-current.sentex.ca> Date: Mon, 29 Oct 2007 07:41:50 -0500 (EST) X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on clamscanner3 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 19:26:58 -0000 TB --- 2007-10-29 10:05:02 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-10-29 10:05:02 - starting HEAD tinderbox run for i386/i386 TB --- 2007-10-29 10:05:02 - cleaning the object tree TB --- 2007-10-29 10:06:16 - checking out the source tree TB --- 2007-10-29 10:06:16 - cd /tinderbox/HEAD/i386/i386 TB --- 2007-10-29 10:06:16 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-10-29 10:20:12 - building world (CFLAGS=-O2 -pipe) TB --- 2007-10-29 10:20:12 - cd /src TB --- 2007-10-29 10:20:12 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 29 10:20:13 UTC 2007 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Mon Oct 29 11:41:46 UTC 2007 TB --- 2007-10-29 11:41:47 - generating LINT kernel config TB --- 2007-10-29 11:41:47 - cd /src/sys/i386/conf TB --- 2007-10-29 11:41:47 - /usr/bin/make -B LINT TB --- 2007-10-29 11:41:47 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-10-29 11:41:47 - cd /src TB --- 2007-10-29 11:41:47 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Oct 29 11:41:47 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Mon Oct 29 12:12:12 UTC 2007 TB --- 2007-10-29 12:12:12 - building GENERIC kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-10-29 12:12:12 - cd /src TB --- 2007-10-29 12:12:12 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Mon Oct 29 12:12:13 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Mon Oct 29 12:35:00 UTC 2007 TB --- 2007-10-29 12:35:00 - building PAE kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-10-29 12:35:00 - cd /src TB --- 2007-10-29 12:35:00 - /usr/bin/make -B buildkernel KERNCONF=PAE >>> Kernel build for PAE started on Mon Oct 29 12:35:01 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] if_zyd.o(.text+0x3a85): In function `zyd_ioctl': /src/sys/dev/usb/if_zyd.c:2390: undefined reference to `ieee80211_ioctl' if_zyd.o(.text+0x3b35): In function `zyd_media_change': /src/sys/dev/usb/if_zyd.c:673: undefined reference to `ieee80211_media_change' if_zyd.o(.text+0x3cc7): In function `zyd_rx_data': /src/sys/dev/usb/if_zyd.c:1942: undefined reference to `ieee80211_find_rxnode' if_zyd.o(.text+0x3d03):/src/sys/dev/usb/if_zyd.c:1943: undefined reference to `ieee80211_input' if_zyd.o(.text+0x3d0b):/src/sys/dev/usb/if_zyd.c:1947: undefined reference to `ieee80211_free_node' *** Error code 1 Stop in /obj/src/sys/PAE. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-10-29 12:41:49 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-10-29 12:41:49 - ERROR: failed to build PAE kernel TB --- 2007-10-29 12:41:49 - tinderbox aborted TB --- 0.78 user 3.12 system 9292.93 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 19:27:33 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FF9216A46B; Mon, 29 Oct 2007 19:27:33 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 63C2513C4AA; Mon, 29 Oct 2007 19:27:33 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id B92251CC066; Mon, 29 Oct 2007 12:18:36 -0700 (PDT) Date: Mon, 29 Oct 2007 12:18:36 -0700 From: Jeremy Chadwick To: Giorgos Keramidas Message-ID: <20071029191836.GA58058@eos.sc1.parodius.com> References: <47240A15.8080305@charter.net> <20071028074248.GA1511@haakonia.hitnet.RWTH-Aachen.DE> <4724BAD9.7000400@charter.net> <20071028164152.GA7516@eos.sc1.parodius.com> <4724BEB3.5080905@charter.net> <20071029132447.GA2658@kobe.laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071029132447.GA2658@kobe.laptop> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: Andrew Lankford , stable@freebsd.org, current@freebsd.org Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 19:27:33 -0000 On Mon, Oct 29, 2007 at 03:24:47PM +0200, Giorgos Keramidas wrote: > On 2007-10-28 12:54, Andrew Lankford wrote: > > Thbbt! I'm reading the catman version of MAKEDEV. Wish I could > > disable that "feature". Oh well. I'll delete it all and rebuild it > > again if needed. Thanks! > > Ah, that's it then :) > > My usual `installworld' steps include this too: > > # cd /usr/share/man > # find cat[0-9] \! -type d -exec rm {} + There's a periodic script (/etc/periodic/weekly/330.catman) which rebuilds all the catman pages for you. However, it makes an immense mess of your weekly system mails due to all the manpage/nroff formatting mistakes. Have a look: http://lists.freebsd.org/pipermail/freebsd-ports/2007-May/040648.html -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 19:47:31 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9D9C16A418; Mon, 29 Oct 2007 19:47:31 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 82F6C13C4BE; Mon, 29 Oct 2007 19:47:31 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.8/8.13.8) with ESMTP id l9TI9xTA008578; Mon, 29 Oct 2007 14:09:59 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.14.1/8.14.1) with ESMTP id l9TI9xMv043336; Mon, 29 Oct 2007 14:09:59 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 2CF0973039; Mon, 29 Oct 2007 13:09:59 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20071029180959.2CF0973039@freebsd-current.sentex.ca> Date: Mon, 29 Oct 2007 13:09:59 -0500 (EST) X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on clamscanner3 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 19:47:32 -0000 TB --- 2007-10-29 17:55:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-10-29 17:55:00 - starting HEAD tinderbox run for i386/i386 TB --- 2007-10-29 17:55:00 - cleaning the object tree TB --- 2007-10-29 17:55:55 - checking out the source tree TB --- 2007-10-29 17:55:55 - cd /tinderbox/HEAD/i386/i386 TB --- 2007-10-29 17:55:55 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-10-29 18:06:46 - building world (CFLAGS=-O2 -pipe) TB --- 2007-10-29 18:06:46 - cd /src TB --- 2007-10-29 18:06:46 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 29 18:06:47 UTC 2007 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools [...] echo make-roken: /usr/lib/libc.a /obj/src/tmp/legacy/usr/lib/libegacy.a >> .depend ===> kerberos5/tools/asn1_compile (depend) sed -e '106s/"/"#ifdef __PARSE_UNITS_H__\\n/;' -e '106s/",/\\n#endif\\n",/' /src/kerberos5/tools/asn1_compile/../../../crypto/heimdal/lib/asn1/gen_glue.c > gen_glue-fixed.c lex -t /src/kerberos5/tools/asn1_compile/../../../crypto/heimdal/lib/asn1/lex.l > lex.c yacc -d -o parse.c /src/kerberos5/tools/asn1_compile/../../../crypto/heimdal/lib/asn1/parse.y cd /src/kerberos5/tools/asn1_compile/../make-print-version && /usr/bin/make cc -O2 -pipe -DHAVE_CONFIG_H -I/src/kerberos5/tools/make-print-version/../../include -I/obj/src/tmp/legacy/usr/include -c /src/kerberos5/tools/make-print-version/../../../crypto/heimdal/lib/vers/make-print-version.c cc: installation problem, cannot exec `as': Permission denied *** Error code 2 Stop in /src/kerberos5/tools/make-print-version. *** Error code 1 Stop in /src/kerberos5/tools/asn1_compile. *** Error code 1 Stop in /src/kerberos5/tools. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-10-29 18:09:59 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-10-29 18:09:59 - ERROR: failed to build world TB --- 2007-10-29 18:09:59 - tinderbox aborted TB --- 0.89 user 3.12 system 898.12 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 19:53:13 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D557816A41A for ; Mon, 29 Oct 2007 19:53:13 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id C772F13C4D1 for ; Mon, 29 Oct 2007 19:53:13 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id 1D0961A3C1A; Sun, 28 Oct 2007 20:53:28 -0700 (PDT) From: John Baldwin To: "Robert Backhaus" Date: Sun, 28 Oct 2007 23:50:47 -0400 User-Agent: KMail/1.9.7 References: <200710111741.34992.jhb@FreeBSD.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710282350.48031.jhb@freebsd.org> Cc: current@freebsd.org Subject: Re: New-bus unit wiring via hints.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 19:53:13 -0000 On Sunday 28 October 2007 07:08:13 pm Robert Backhaus wrote: > Any chance of extending this to the USB bus? The problem of 'wandering > ugen' and 'wandering ulpt' devices has been bothering me for a while > now. > It would also help if it could be used to tell more specific drivers > to leave a device for ugen - for instance, HP USB printers are best > addressed by ugen, and the user mode drivers take it from there. You > loose functionality if you have to talk through the ulpt drivers. You could easily extend it to USB if you can come up with a reasonable way to specify the wiring. You could possibly wire units via hints that specify serial numbers or manfacturer and model strings, etc. However, I'm less familiar with USB so I'm less unsure what specific attributes would be suitable for wiring or not. As far as the second problem, that is not a unit wiring issue per-se. I think uhid(4) currently has a blacklist of devices it ignores (like some APC UPS devices that apcupsd wants to be ugen0 rather than uhid0). You could port that support over to ulpt(4) and add a blacklist to it perhaps. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 20:31:25 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7BF3216A41A for ; Mon, 29 Oct 2007 20:31:25 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id B866913C4BD for ; Mon, 29 Oct 2007 20:31:22 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 1849845E93; Mon, 29 Oct 2007 09:01:49 +0100 (CET) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 8BA9E45CD9; Mon, 29 Oct 2007 09:01:43 +0100 (CET) Date: Mon, 29 Oct 2007 10:01:41 +0100 From: Pawel Jakub Dawidek To: Peter Losher Message-ID: <20071029090141.GA4407@garage.freebsd.pl> References: <47246FED.6000103@isc.org> <4725895A.8030905@isc.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline In-Reply-To: <4725895A.8030905@isc.org> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-current@freebsd.org Subject: Re: weird ZFS and mpt interactions (WAS Re: Clearing out vdevs (can't create new zpool)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 20:31:25 -0000 --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 29, 2007 at 12:18:50AM -0700, Peter Losher wrote: > Peter Losher wrote: >=20 > > I have been poking around with our 16-port SATA RAID chassis (in JBOD > > mode) with a fresh RELENG_7 internal build from Saturday. I only had > > half the disks {da0-7) at first, when I brought over the second set > > (da8-15), I destroyed the existing pool and then tried to create a new > > one with all 16 disks, and encountered this error: > >=20 > > -=3D- > > # zpool create tank raidz da{0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15} > > cannot create 'tank': one or more vdevs refer to the same device > > -=3D- > >=20 > > I can create one with the second set of disks (and destroy/create again) > > but somehow I have some old vdevs sitting around which is preventing me > > from using the first set of disks. How can I clear them out? >=20 > O.k. poked at this some more this evening and I see what the problem > might be. The SATA RAID chassis (in JBOD mode) is presenting the 16 > drives as two sets of 8 drives each (it has two FC connections, one for > each set - incidentally in RAID mode, it just needs one to cover all 16 > disks as it's able to bridge the two controllers together). Those two > FC connections are plugged into a dual port LSI Logic FC HBA: >=20 > -=3D- > mpt0: port 0x2400-0x24ff > mem 0xb8a20000-0xb8a23fff,0xb8a00000-0xb8a0ffff irq 24 at device 3.0 on p= ci8 > mpt0: [ITHREAD] > mpt0: MPI Version=3D1.5.10.0 > mpt1: port 0x2000-0x20ff > mem 0xb8a24000-0xb8a27fff,0xb8a10000-0xb8a1ffff irq 27 at device 3.1 on p= ci8 > mpt1: [ITHREAD] > mpt1: MPI Version=3D1.5.10.0 > -=3D- >=20 > so this disks show up as such: >=20 > -=3D- > da0 at mpt0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-3 device > da0: 100.000MB/s transfers > da0: Command Queueing Enabled > da0: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) > da1 at mpt0 bus 0 target 0 lun 1 > da1: Fixed Direct Access SCSI-3 device > da1: 100.000MB/s transfers > da1: Command Queueing Enabled > da1: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) > da2 at mpt0 bus 0 target 0 lun 2 > da2: Fixed Direct Access SCSI-3 device > da2: 100.000MB/s transfers > da2: Command Queueing Enabled > da2: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) > da3 at mpt0 bus 0 target 0 lun 3 > da3: Fixed Direct Access SCSI-3 device > da3: 100.000MB/s transfers > da3: Command Queueing Enabled > da3: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) > da4 at mpt0 bus 0 target 0 lun 4 > da4: Fixed Direct Access SCSI-3 device > da4: 100.000MB/s transfers > da4: Command Queueing Enabled > da4: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) > da5 at mpt0 bus 0 target 0 lun 5 > da5: Fixed Direct Access SCSI-3 device > da5: 100.000MB/s transfers > da5: Command Queueing Enabled > da5: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) > da6 at mpt0 bus 0 target 0 lun 6 > da6: Fixed Direct Access SCSI-3 device > da6: 100.000MB/s transfers > da6: Command Queueing Enabled > da6: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) > da7 at mpt0 bus 0 target 0 lun 7 > da7: Fixed Direct Access SCSI-3 device > da7: 100.000MB/s transfers > da7: Command Queueing Enabled > da7: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) > da8 at mpt1 bus 0 target 0 lun 0 > da8: Fixed Direct Access SCSI-3 device > da8: 100.000MB/s transfers > da8: Command Queueing Enabled > da8: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) > da9 at mpt1 bus 0 target 0 lun 1 > da9: Fixed Direct Access SCSI-3 device > da9: 100.000MB/s transfers > da9: Command Queueing Enabled > da9: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) > da10 at mpt1 bus 0 target 0 lun 2 > da10: Fixed Direct Access SCSI-3 device > da10: 100.000MB/s transfers > da10: Command Queueing Enabled > da10: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) > da11 at mpt1 bus 0 target 0 lun 3 > da11: Fixed Direct Access SCSI-3 device > da11: 100.000MB/s transfers > da11: Command Queueing Enabled > da11: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) > da12 at mpt1 bus 0 target 0 lun 4 > da12: Fixed Direct Access SCSI-3 device > da12: 100.000MB/s transfers > da12: Command Queueing Enabled > da12: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) > da13 at mpt1 bus 0 target 0 lun 5 > da13: Fixed Direct Access SCSI-3 device > da13: 100.000MB/s transfers > da13: Command Queueing Enabled > da13: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) > da14 at mpt1 bus 0 target 0 lun 6 > da14: Fixed Direct Access SCSI-3 device > da14: 100.000MB/s transfers > da14: Command Queueing Enabled > da14: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) > da15 at mpt1 bus 0 target 0 lun 7 > da15: Fixed Direct Access SCSI-3 device > da15: 100.000MB/s transfers > da15: Command Queueing Enabled > da15: 381554MB (781422768 512 byte sectors: 255H 63S/T 48641C) > -=3D- >=20 > Two identical sets of 8 disks, the only difference is that one set is > presented over mpt0, the other over mpt1. I suspect ZFS is treating > this as just one set of eight vdevs as I can create a pool with either > the first set of eight or the second set of eight, just not with BOTH > sets of disks. >=20 > Hope this helps explain things a bit better. Let me get this right. Those are 16 physically different disks? Not 8 disks visible through two FC path? Can you show: # apply "camcontrol inquiry da%1 -S" `jot 16 0` --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --envbJBWh7q8WU6mo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHJaF1ForvXbEpPzQRAvTgAJ9lPws2KzW6BuRQkF2x7pm8m4FUgwCfRXXA L0qJ84X1Z+F7ixz92riO8/M= =GX+c -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 20:50:06 2007 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6F8C16A41A for ; Mon, 29 Oct 2007 20:50:06 +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 40A0613C49D for ; Mon, 29 Oct 2007 20:50:06 +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 678E4475F2 for ; Mon, 29 Oct 2007 11:34:12 -0500 (EST) Date: Mon, 29 Oct 2007 17:34:12 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: current@FreeBSD.org Message-ID: <20071029173220.F56037@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: New Neterion 10gbps driver drop in 8-CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 20:50:06 -0000 FYI: I have merged the new Neterion 10gbps driver drop into CVS, courtesy Neterion. They report significantly improved performance due to a variety of optimizations made in this drop. I'm not sure how many Neterion users we have out there running 8-CURRENT, but if you are, please give this drop a try as I plan to merge it for inclusion in 7.0-RELEASE. Thanks, Robert N M Watson Computer Laboratory University of Cambridge ---------- Forwarded message ---------- Date: Mon, 29 Oct 2007 14:19:32 +0000 (UTC) From: Robert Watson To: src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: src/share/man/man4 nxge.4 src/sys/dev/nxge if_nxge.c if_nxge.h xge-osdep.h xgell-version.h src/sys/dev/nxge/include build-version.h version.h xge-debug.h xge-defs.h xge-list.h xge-os-pal.h xge-os-template.h xge-queue.h xgehal-channel.h ... rwatson 2007-10-29 14:19:32 UTC FreeBSD src repository Modified files: share/man/man4 nxge.4 sys/dev/nxge if_nxge.c if_nxge.h xge-osdep.h xgell-version.h sys/dev/nxge/include build-version.h version.h xge-debug.h xge-defs.h xge-list.h xge-os-pal.h xge-queue.h xgehal-channel.h xgehal-config.h xgehal-device.h xgehal-driver.h xgehal-event.h xgehal-fifo.h xgehal-mgmt.h xgehal-mgmtaux.h xgehal-mm.h xgehal-regs.h xgehal-ring.h xgehal-stats.h xgehal-types.h xgehal.h sys/dev/nxge/xgehal xge-queue.c xgehal-channel-fp.c xgehal-channel.c xgehal-config.c xgehal-device-fp.c xgehal-device.c xgehal-driver.c xgehal-fifo-fp.c xgehal-fifo.c xgehal-mgmt.c xgehal-mgmtaux.c xgehal-mm.c xgehal-ring-fp.c xgehal-ring.c xgehal-stats.c sys/modules/nxge Makefile tools/tools/nxge Makefile xge_cmn.h xge_info.c xge_info.h xge_log.c xge_log.h Removed files: sys/dev/nxge/include xge-os-template.h Log: Merge Neterion if_nxge driver version 2.0.9.11230 with the following changes: 01 - Enhanced LRO: LRO feature is extended to support multi-buffer mode. Previously, Ethernet frames received in contiguous buffers were offloaded. Now, frames received in multiple non-contiguous buffers can be offloaded, as well. The driver now supports LRO for jumbo frames. 02 - Locks Optimization: The driver code was re-organized to limit the use of locks. Moreover, lock contention was reduced by replacing wait locks with try locks. 03 - Code Optimization: The driver code was re-factored to eliminate some memcpy operations. Fast path loops were optimized. 04 - Tag Creations: Physical Buffer Tags are now optimized based upon frame size. For better performance, Physical Memory Maps are now re-used. 05 - Configuration: Features such as TSO, LRO, and Interrupt Mode can be configured either at load or at run time. Rx buffer mode (mode 1 or mode 2) can be configured at load time through kenv. 06 - Driver Statistics: Run time statistics are enhanced to provide better visibility into the driver performance. 07 - Bug Fixes: The driver contains fixes for the problems discovered and reported since last submission. 08 - MSI support: Added Message Signaled Interrupt feature which currently uses 1 message. 09 Removed feature: Rx 3 buffer mode feature has been removed. Driver now supports 1, 2 and 5 buffer modes of which 2 and 5 buffer modes can be used for header separation. 10 Compiler warning: Fixed compiler warning when compiled for 32 bit system. 11 Copyright notice: Source files are updated with the proper copyright notice. MFC after: 3 days Submitted by: Alicia Pena , Muhammad Shafiq Revision Changes Path 1.4 +9 -4 src/share/man/man4/nxge.4 1.4 +2234 -2123 src/sys/dev/nxge/if_nxge.c 1.2 +255 -129 src/sys/dev/nxge/if_nxge.h 1.2 +2 -2 src/sys/dev/nxge/include/build-version.h 1.2 +6 -14 src/sys/dev/nxge/include/version.h 1.2 +15 -168 src/sys/dev/nxge/include/xge-debug.h 1.2 +56 -64 src/sys/dev/nxge/include/xge-defs.h 1.2 +18 -26 src/sys/dev/nxge/include/xge-list.h 1.2 +35 -48 src/sys/dev/nxge/include/xge-os-pal.h 1.2 +0 -614 src/sys/dev/nxge/include/xge-os-template.h (dead) 1.2 +30 -38 src/sys/dev/nxge/include/xge-queue.h 1.2 +85 -102 src/sys/dev/nxge/include/xgehal-channel.h 1.2 +438 -538 src/sys/dev/nxge/include/xgehal-config.h 1.2 +222 -248 src/sys/dev/nxge/include/xgehal-device.h 1.2 +30 -38 src/sys/dev/nxge/include/xgehal-driver.h 1.2 +10 -18 src/sys/dev/nxge/include/xgehal-event.h 1.2 +68 -72 src/sys/dev/nxge/include/xgehal-fifo.h 1.2 +42 -50 src/sys/dev/nxge/include/xgehal-mgmt.h 1.2 +21 -29 src/sys/dev/nxge/include/xgehal-mgmtaux.h 1.2 +30 -38 src/sys/dev/nxge/include/xgehal-mm.h 1.2 +340 -344 src/sys/dev/nxge/include/xgehal-regs.h 1.2 +128 -136 src/sys/dev/nxge/include/xgehal-ring.h 1.2 +263 -300 src/sys/dev/nxge/include/xgehal-stats.h 1.2 +198 -217 src/sys/dev/nxge/include/xgehal-types.h 1.2 +0 -9 src/sys/dev/nxge/include/xgehal.h 1.2 +303 -276 src/sys/dev/nxge/xge-osdep.h 1.2 +133 -141 src/sys/dev/nxge/xgehal/xge-queue.c 1.2 +124 -129 src/sys/dev/nxge/xgehal/xgehal-channel-fp.c 1.2 +208 -383 src/sys/dev/nxge/xgehal/xgehal-channel.c 1.2 +241 -249 src/sys/dev/nxge/xgehal/xgehal-config.c 1.2 +708 -716 src/sys/dev/nxge/xgehal/xgehal-device-fp.c 1.2 +2975 -2955 src/sys/dev/nxge/xgehal/xgehal-device.c 1.2 +82 -90 src/sys/dev/nxge/xgehal/xgehal-driver.c 1.2 +256 -264 src/sys/dev/nxge/xgehal/xgehal-fifo-fp.c 1.2 +200 -208 src/sys/dev/nxge/xgehal/xgehal-fifo.c 1.2 +493 -501 src/sys/dev/nxge/xgehal/xgehal-mgmt.c 1.2 +809 -817 src/sys/dev/nxge/xgehal/xgehal-mgmtaux.c 1.2 +244 -252 src/sys/dev/nxge/xgehal/xgehal-mm.c 1.2 +362 -370 src/sys/dev/nxge/xgehal/xgehal-ring-fp.c 1.2 +233 -241 src/sys/dev/nxge/xgehal/xgehal-ring.c 1.2 +360 -368 src/sys/dev/nxge/xgehal/xgehal-stats.c 1.2 +1 -9 src/sys/dev/nxge/xgell-version.h 1.2 +4 -7 src/sys/modules/nxge/Makefile 1.2 +0 -0 src/tools/tools/nxge/Makefile 1.2 +49 -46 src/tools/tools/nxge/xge_cmn.h 1.2 +569 -424 src/tools/tools/nxge/xge_info.c 1.2 +30 -34 src/tools/tools/nxge/xge_info.h 1.2 +286 -211 src/tools/tools/nxge/xge_log.c 1.2 +2519 -2500 src/tools/tools/nxge/xge_log.h From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 21:07:04 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 929A916A468 for ; Mon, 29 Oct 2007 21:07:04 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outX.internet-mail-service.net (outX.internet-mail-service.net [216.240.47.247]) by mx1.freebsd.org (Postfix) with ESMTP id 7FC6A13C4B0 for ; Mon, 29 Oct 2007 21:07:04 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Mon, 29 Oct 2007 13:11:31 -0700 X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (nat.ironport.com [63.251.108.100]) by idiom.com (Postfix) with ESMTP id E2759126851 for ; Mon, 29 Oct 2007 13:11:30 -0700 (PDT) Message-ID: <47263E91.9050908@elischer.org> Date: Mon, 29 Oct 2007 13:12:01 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: FYI (fun) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 21:07:04 -0000 in a freebsd 1.0 chroot on a freebsd 8.0 system on a 3 year old (i.e not the fastest) system. cd /usr/src/sys/i386/conf; config GENERICAH; cd ../../compile/GENERICAH; make depend all [...] loading 386bsd rearranging symbols text data bss dec hex 458752 16384 139504 614640 960f0 5.8u 3.9s 0:09.71 101.1% 617+625k 0+23io 0pf+0w yep folks.. that's 9.7 seconds from go to whoa. and of course that was only using 1 cpu.. hmm did make have -j in those days? (tries it and sees no change so apparently not). From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 21:20:59 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E43116A469 for ; Mon, 29 Oct 2007 21:20:59 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id B6CA813C4BB for ; Mon, 29 Oct 2007 21:20:57 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1ImZT7-0000Xs-CW for freebsd-current@freebsd.org; Mon, 29 Oct 2007 18:36:09 +0000 Received: from pagh.dogan.ch ([213.144.146.12]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Oct 2007 18:36:09 +0000 Received: from ihsan by pagh.dogan.ch with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 29 Oct 2007 18:36:09 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ihsan Dogan Date: Mon, 29 Oct 2007 19:35:59 +0100 Lines: 42 Message-ID: References: <20071011003619.GA84433@obelix.dsto.defence.gov.au> <2a41acea0710102002j5c09d285kac076ce2b5e4af41@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pagh.dogan.ch User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) In-Reply-To: <2a41acea0710102002j5c09d285kac076ce2b5e4af41@mail.gmail.com> Sender: news Subject: Re: em0: watchdog timeout ... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 21:20:59 -0000 on 11.10.2007 05:02 Jack Vogel said the following: >> em0@pci5:4:0: class=0x020000 card=0x10018086 chip=0x10268086 rev=0x04 hdr=0x00 >> vendor = 'Intel Corporation' >> device = '82545GM Gigabit Ethernet Controller' >> class = network >> subclass = ethernet >> >> And am consistently experiencing: >> >> em0: watchdog timeout -- resetting >> em0: link state changed to DOWN >> em0: link state changed to UP >> em0: watchdog timeout -- resetting >> em0: link state changed to DOWN >> em0: link state changed to UP >> em0: watchdog timeout -- resetting >> em0: link state changed to DOWN >> em0: link state changed to UP >> >> Anything I can do to help debug this ? > > Well, add more detail for one, like timestamps on these events, > do they happen once a minute, hour, day? I've got exactly the same problem on a machine, running 7.0-BETA1. The Problem occurs during the boot, when dhclient is trying to get IP. The messages are occuring all the time an it's not possible to use the network card at all. In my case, the network card and the soundcard are sharing an irq. If I don't load the the snd_emu10k1 driver, the network card works perfectly. The problem doesn't occur with 6.2 Ihsan -- ihsan@dogan.ch http://blog.dogan.ch/ http://ihsan.dogan.ch/ From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 21:36:54 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C998116A420 for ; Mon, 29 Oct 2007 21:36:54 +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 9F1F213C4BE for ; Mon, 29 Oct 2007 21:36:54 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so2301448waf for ; Mon, 29 Oct 2007 14:36:36 -0700 (PDT) Received: by 10.114.127.1 with SMTP id z1mr2849733wac.1193650836137; Mon, 29 Oct 2007 02:40:36 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id m5sm12810462wag.2007.10.29.02.40.31 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 29 Oct 2007 02:40:34 -0700 (PDT) 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 l9T9eRfY035189 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Oct 2007 18:40:27 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l9T9eP2m035188; Mon, 29 Oct 2007 18:40:25 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 29 Oct 2007 18:40:23 +0900 From: Pyun YongHyeon To: "Arno J. Klaassen" Message-ID: <20071029094023.GI32892@cdnetworks.co.kr> References: <20071029024452.GB32892@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: current@freebsd.org Subject: Re: 2nd nfe interface not showing up on Tyan S2895 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 21:36:54 -0000 On Mon, Oct 29, 2007 at 10:02:08AM +0100, Arno J. Klaassen wrote: > Dear Pyun YongHyeon, > > > On Sun, Oct 28, 2007 at 07:27:25PM +0100, Arno J. Klaassen wrote: > > > Hi, > > > > > > I'm playing with RELENG_7 on a spare S2895 I have around and > > > have difficulties with the ethernet interfaces : > > > > > > - nfe0 shows up and works OK under 1Gbps (at least for > > > buildworlds etc over NFS) but under 100Mbps it says : > > > > > > install kernel: nfe0: tx v2 error 0x6004 > > > install kernel: nfe0: tx v2 error 0x6204 > > > > > > > Because developers don't know what exact meaning for Tx completion > > status word would be(Only NVIDIA knows that) nfe(4) just shows the > > possible error candidate. > > OK > > > If you see the code you may notice no error > > recovery is attempted for the case. > > So I guess you can also ignore it unless the message contiously is > > printed on youe console while network activity is in progress. > > Ehmm, I notice no network activity at all ... when plugged at > a 100Mbps 3com hub. > As said, plugged at a (Netgear) 1Gbps it works flawlessly. > > Let me know if I can test a patch/sysctl etc. For the time being > I will use this board internally anyway. > Ok, show me the output of verbosed boot messagges related with nfe(4)/PHY driver. Also let me know the output of "pciconf -lcv". Btw, did you have a manual media option for nfe(4)? -- Regards, Pyun YongHyeon From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 21:53:51 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76EDD16A420 for ; Mon, 29 Oct 2007 21:53:51 +0000 (UTC) (envelope-from rrs@cisco.com) Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72]) by mx1.freebsd.org (Postfix) with ESMTP id 563E313C4BC for ; Mon, 29 Oct 2007 21:53:51 +0000 (UTC) (envelope-from rrs@cisco.com) X-IronPort-AV: E=Sophos;i="4.21,344,1188802800"; d="scan'208";a="540995123" Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-3.cisco.com with ESMTP; 29 Oct 2007 14:53:42 -0700 Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id l9TLrf6A015605 for ; Mon, 29 Oct 2007 14:53:41 -0700 Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id l9TLrUK7018508 for ; Mon, 29 Oct 2007 21:53:41 GMT Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 29 Oct 2007 14:53:39 -0700 Received: from [127.0.0.1] ([171.68.225.134]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 29 Oct 2007 14:53:38 -0700 Message-ID: <4726561D.7090805@cisco.com> Date: Mon, 29 Oct 2007 17:52:29 -0400 From: Randall Stewart User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20070601 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 29 Oct 2007 21:53:38.0861 (UTC) FILETIME=[29BA7DD0:01C81A76] DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=136; t=1193694821; x=1194558821; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rrs@cisco.com; z=From:=20Randall=20Stewart=20 |Subject:=20Opensolaris=20SMF=20for=20FreeBSD |Sender:=20; bh=tfk8qgSnhu5vFj3MmtL5G8lZfwws3ynx0PUhpRSgLXA=; b=bXCYuTaHE+WJ85flnyxIATGqX+4ZjUKwTN8RrbnPheZ600ZvXhB41Ud/eH8XdeVbRn4Hmbwh g3D7Yb1rb4zlz1N9tCC9toSNUiemlkq9ggpG5d22lVeln7BSG+i59Wm09oQYaZ/e1u/c2SR7fc Sd5vISInbDvHPPm+s54w0pJXs=; Authentication-Results: sj-dkim-1; header.From=rrs@cisco.com; dkim=pass (sig from cisco.com/sjdkim1004 verified; ); Subject: Opensolaris SMF for FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 21:53:51 -0000 Anyone looked at porting SMF to FreeBSD? R -- Randall Stewart NSSTG - Cisco Systems Inc. 803-345-0369 803-317-4952 (cell) From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 22:00:58 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2E8A16A419 for ; Mon, 29 Oct 2007 22:00:58 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 7D1F113C447 for ; Mon, 29 Oct 2007 22:00:58 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from mr08.lnh.mail.rcn.net ([207.172.157.28]) by smtp02.lnh.mail.rcn.net with ESMTP; 29 Oct 2007 13:04:01 -0400 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr08.lnh.mail.rcn.net (MOS 3.8.3-GA) with ESMTP id JGN01174; Mon, 29 Oct 2007 13:04:01 -0400 (EDT) Received: from 209-6-22-188.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com (HELO jerusalem.litteratus.org.litteratus.org) ([209.6.22.188]) by smtp01.lnh.mail.rcn.net with ESMTP; 29 Oct 2007 12:08:59 -0500 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18214.4735.303373.626810@jerusalem.litteratus.org> Date: Mon, 29 Oct 2007 13:03:59 -0400 To: Lionel Flandrin In-Reply-To: <86tzobzboe.fsf@simias.hd.free.fr> References: <86tzobzboe.fsf@simias.hd.free.fr> X-Mailer: VM 7.17 under 21.5 (beta28) "fuki" XEmacs Lucid X-Junkmail-Whitelist: YES (by domain whitelist at mr08.lnh.mail.rcn.net) Cc: freebsd-current@freebsd.org Subject: fresh -CURRENT: ps: time: keyword not found X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 22:00:58 -0000 Lionel Flandrin writes: > On a -CURRENT csup'd a couple of hours ago, I get a message on > stderr every time in run "ps": "ps: time: keyword not found". I'm getting this too, on ps and a couple of other commands. I had thought this was related to a failed system update (installworld broke; I thought I had sent a message but apparently it didn't get here; message is repeated below). Sorry to hear there's a problem, good to know I'm not alone. Robert Huff **************** repeated message **************** Yesterday (10/26 around 22:00 EDT) I updated source and went to rebuild. Buildworld, buildkernel, installkernel all seem to have gone fine. However, when I run installworld I get this: ===> sys/boot (install) ===> sys/boot/ficl (install) ===> sys/boot/efi (install) ===> sys/boot/efi/libefi (install) ===> sys/boot/i386 (install) ===> sys/boot/i386/mbr (install) install -o root -g wheel -m 444 mbr /boot ===> sys/boot/i386/pmbr (install) install -o root -g wheel -m 444 pmbr /boot ===> sys/boot/i386/boot0 (install) install -o root -g wheel -m 444 boot0 /boot ===> sys/boot/i386/boot0sio (install) install -o root -g wheel -m 444 boot0 /boot/boot0sio ===> sys/boot/i386/btx (install) ===> sys/boot/i386/btx/btx (install) ===> sys/boot/i386/btx/btxldr (install) ===> sys/boot/i386/btx/lib (install) ===> sys/boot/i386/boot2 (install) cc -Os -fno-guess-branch-probability -fomit-frame-pointer -fno-unit-at-a-time -mno-align-long-strings -mrtd -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -DUFS1_AND_UFS2 -DFLAGS=0x80 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 -I/usr/src/sys/boot/i386/boot2/../../common -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -Winline --param max-inline-insns-single=100 -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -S -o boot2.s.tmp /usr/src/sys/boot/i386/boot2/boot2.c sed -e '/align/d' -e '/nop/d' < boot2.s.tmp > boot2.s rm -f boot2.s.tmp as -o boot2.o boot2.s ld -static -N --gc-sections -nostdlib -Ttext 0x2000 -o boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o sio.o objcopy -S -O binary boot2.out boot2.bin btxld -v -E 0x2000 -f bin -b /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin btxld:No such file or directory *** Error code 1 Stop in /usr/src/sys/boot/i386/boot2. *** Error code 1 If I got to the directory and run "make", everything seems to work. Is anyone else seeing this? Is there anyway to find out which file btxld thinks is missing? (The system in question is at least semi-functional. It boots, and connects to the network; however, I would like to see a full install cycle before opening it up again.) Robert Huff From owner-freebsd-current@FreeBSD.ORG Mon Oct 29 22:27:15 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 741A516A421 for ; Mon, 29 Oct 2007 22:27:15 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outG.internet-mail-service.net (outG.internet-mail-service.net [216.240.47.230]) by mx1.freebsd.org (Postfix) with ESMTP id 5F12613C481 for ; Mon, 29 Oct 2007 22:27:15 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Sun, 28 Oct 2007 20:22:09 -0700 X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id C19FD12683E; Sun, 28 Oct 2007 20:22:08 -0700 (PDT) Message-ID: <472551FE.3020703@elischer.org> Date: Sun, 28 Oct 2007 20:22:38 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Rui Paulo References: <47241E9C.7000605@elischer.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: learned something about coretemp X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 22:27:15 -0000 Rui Paulo wrote: > On 10/28/07, Julian Elischer wrote: >> never kldload it on an 8 year old system. >> >> *bewm* >> >> I presume that my 8 YO inspiron 7500 doesn't have whatever is needed, >> but, "*Bewm*" is probably a less than optimal reaction. > > That has been reported in the past. It's Intel's fault, not ours. > The spec says that if you issue a CPUID you should be able to tell if > the CPU has the temperature sensors regardless of the CPU model, but > on old systems these CPUID call "returns true". maybe we should just return true to the top layer if it's a 686 or newer (or something). > From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 00:14:19 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C889E16A419 for ; Tue, 30 Oct 2007 00:14:19 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.239]) by mx1.freebsd.org (Postfix) with ESMTP id 7488D13C48A for ; Tue, 30 Oct 2007 00:14:19 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so1167464nzf for ; Mon, 29 Oct 2007 17:13:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; 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=UOxwG2Ek1h8ZiDnNz0nZ0Vl/eBDtO3YHTcxiJBVY1Ng=; b=I/7fBZXg84hQMfRYOhY1nWJbxUYf1UIwkfpF9DiijZcAOmStYz0Q40r9mNTkk1iG3eQ+srZj+d/BbmHJV1gX1Yj/tt0gAX296BNRuXBFICEis8oerIF6gAivJTWdgo4wwEk/bxaX7RJ/eUwJxa91MfCOii6DqfakxV5XQHJCWhY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=J/bDsF+a8ccOlsUIeaD/wT7BWSCAnOui/gNCOKwXbtJVMLE2sO6Sf8zUig37NoeNuquuMU6bjfG1CR1ZGGOZF+QDHpKI7ZOs7IW1M0J0UMgTurd+1zuusVdhe+L/fobi1/Ugcy7/wSQusbQYQLEYTy6Mhyu/bu2TxyHJRV8fw+8= Received: by 10.114.177.1 with SMTP id z1mr7625441wae.1193703237706; Mon, 29 Oct 2007 17:13:57 -0700 (PDT) Received: by 10.114.13.15 with HTTP; Mon, 29 Oct 2007 17:13:57 -0700 (PDT) Message-ID: Date: Mon, 29 Oct 2007 17:13:57 -0700 From: "Kip Macy" To: "Jack Vogel" In-Reply-To: <2a41acea0710291045m6f1d2acw78c26a455ea3894d@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0710291045m6f1d2acw78c26a455ea3894d@mail.gmail.com> Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List Subject: Re: RFC: Evolution of the em driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 00:14:19 -0000 Jack, you should know by now that we're not Linux. All we care about is that you not break the code that we rely on. I'm still slightly embarrassed when I explain to people that I build if_em as a module because em0 doesn't come up sometimes due to a race condition on initialization, so I need to be able to re-load the driver. We're happy that you're keeping support for Intel's hardware up to date on FreeBSD. -Kip On 10/29/07, Jack Vogel wrote: > I have an important decision to make and I thought rather than just make > it and spring it on you I'd present the issues and see what opinions were. > > Our newer hardware uses new features that, more and more, require > parallel code paths in the driver. For instance, the 82575 (Zoar) uses > what are called 'advanced descriptors', this means different TX path. > The 7.0 em driver has this support in it, it just uses a function pointer > to handle it. > > When I add in multiqueue/RSS support it will add even more code > that functions this way. > > What the Linux team did was to split the newer code into a standalone > driver, they call it 'igb'. I had originally resisted doing this, but with > the development I have been working on the past month I am starting > to wonder if it might not be best to follow them. > > I see 3 possibilities and I'd like feedback, which would you prefer if > you have a preference and why. > > First, keep the driver as is and just live with multiple code paths > and features, possibly #ifdef'ed as they appear. > > Second, split the driver as Linux has into em and igb. The added > question then is how to split it, Linux made the line the use of > advanced descriptors, so Zoar and after, but I could also see a > case for having everything PCI-E/MSI capable being in the new > driver. > > Third, sort of a half-way approach, split up code but not the > driver, in other words offer different source files that can be > compiled into the driver, so you could have the one big jumbo > driver with all in there, or one that will only work with a subset > of adapters. This one would probably be the most work, because > its a new approach. > > Cheers, > > Jack > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 00:45:37 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A9BA16A41A; Tue, 30 Oct 2007 00:45:37 +0000 (UTC) (envelope-from lists@swaggi.com) Received: from rusty.swaggy.net (rusty.swaggy.net [204.14.85.196]) by mx1.freebsd.org (Postfix) with ESMTP id 3B10513C4BC; Tue, 30 Oct 2007 00:45:37 +0000 (UTC) (envelope-from lists@swaggi.com) Received: from localhost ([127.0.0.1] helo=swaggi.com) by rusty.swaggy.net with esmtp (Exim 4.67 (FreeBSD)) (envelope-from ) id 1Imebu-000Gsr-CZ; Mon, 29 Oct 2007 20:05:37 -0400 From: "Yuri Lukin" To: freebsd-current@freebsd.org Date: Mon, 29 Oct 2007 19:05:34 -0500 Message-Id: <20071029235020.M75001@swaggi.com> X-Mailer: swaggi.com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Cc: freebsd-java@freebsd.org Subject: Firefox Java plugin with 7.0? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 00:45:37 -0000 I'm like to ask what people are using for Java plugin with Firefox. There were a few recent threads on this subject but no definitive answer: http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078038.html http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078492.html I tried compiling jdk15 port and was able to build it and install it successfully. However, when trying to load a java applet in Firefox, the browser seemingly crashes (exits). I then tried following the method described in the handbook by downloading the diablo-jre-freebsd6.i386.1.5.0.07.01.tbz package from FreeBSD Foundation website and adding it with pkg_add. Trying to load java applets crashes Firefox. In both cases, javavmwrapper was installed and about:plugins in Firefox shows that java plugin is installed. Is there a working combination for 7.0-PRERELEASE/BETA? My system is: # uname -a FreeBSD 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #0: Mon Oct 15 13:02:17 EDT 2007 swaggy@:/usr/obj/usr/src/sys/T61 i386 # pkg_info | grep java javavmwrapper-2.3 Wrapper script for various Java Virtual Machines # pkg_info | grep firefox firefox-2.0.0.8,1 Web browser based on the browser portion of Mozilla # ls -la /usr/local/lib/browser_plugins/ total 96 drwxr-xr-x 2 root wheel 512 Oct 29 19:22 . drwxr-xr-x 54 root wheel 31232 Oct 29 13:26 .. -rw-r--r-- 1 root wheel 0 Oct 20 00:20 .firefox.keep lrwxr-xr-x 1 root wheel 63 Oct 29 19:22 libjavaplugin_oji.so -> /usr/local/diablo-jre1.5.0/plugin/i386/ns7/libjavaplugin_oji.so -rwxr-xr-x 1 root wheel 62192 Sep 12 14:21 npwrapper.libflashplayer.so Currently with jre from FreeBSD foundation site: # pkg_info | grep jre diablo-jre-1.5.0.07.01 Java Runtime Environment 1.5.0_07.01 Thanks, Yuri From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 01:13:04 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0E90016A474 for ; Tue, 30 Oct 2007 01:13:04 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.freebsd.org (Postfix) with ESMTP id A5F2313C4C2 for ; Tue, 30 Oct 2007 01:13:03 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1386466nfb for ; Mon, 29 Oct 2007 18:12:52 -0700 (PDT) Received: by 10.86.84.5 with SMTP id h5mr4968722fgb.1193679917408; Mon, 29 Oct 2007 10:45:17 -0700 (PDT) Received: by 10.86.100.19 with HTTP; Mon, 29 Oct 2007 10:45:17 -0700 (PDT) Message-ID: <2a41acea0710291045m6f1d2acw78c26a455ea3894d@mail.gmail.com> Date: Mon, 29 Oct 2007 10:45:17 -0700 From: "Jack Vogel" To: "freebsd-net@freebsd.org" , "FreeBSD Stable List" , "FreeBSD Current" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: RFC: Evolution of the em driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 01:13:04 -0000 I have an important decision to make and I thought rather than just make it and spring it on you I'd present the issues and see what opinions were. Our newer hardware uses new features that, more and more, require parallel code paths in the driver. For instance, the 82575 (Zoar) uses what are called 'advanced descriptors', this means different TX path. The 7.0 em driver has this support in it, it just uses a function pointer to handle it. When I add in multiqueue/RSS support it will add even more code that functions this way. What the Linux team did was to split the newer code into a standalone driver, they call it 'igb'. I had originally resisted doing this, but with the development I have been working on the past month I am starting to wonder if it might not be best to follow them. I see 3 possibilities and I'd like feedback, which would you prefer if you have a preference and why. First, keep the driver as is and just live with multiple code paths and features, possibly #ifdef'ed as they appear. Second, split the driver as Linux has into em and igb. The added question then is how to split it, Linux made the line the use of advanced descriptors, so Zoar and after, but I could also see a case for having everything PCI-E/MSI capable being in the new driver. Third, sort of a half-way approach, split up code but not the driver, in other words offer different source files that can be compiled into the driver, so you could have the one big jumbo driver with all in there, or one that will only work with a subset of adapters. This one would probably be the most work, because its a new approach. Cheers, Jack From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 01:13:46 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A95516A41A for ; Tue, 30 Oct 2007 01:13:46 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.189]) by mx1.freebsd.org (Postfix) with ESMTP id 48D2013C480 for ; Tue, 30 Oct 2007 01:13:46 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so1524566rvb for ; Mon, 29 Oct 2007 18:13:34 -0700 (PDT) Received: by 10.115.32.1 with SMTP id k1mr6455090waj.1193625903628; Sun, 28 Oct 2007 19:45:03 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id k23sm12187233waf.2007.10.28.19.44.58 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 28 Oct 2007 19:45:02 -0700 (PDT) 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 l9T2irFv034000 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Oct 2007 11:44:53 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l9T2iqM7033999; Mon, 29 Oct 2007 11:44:52 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 29 Oct 2007 11:44:52 +0900 From: Pyun YongHyeon To: "Arno J. Klaassen" Message-ID: <20071029024452.GB32892@cdnetworks.co.kr> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: current@freebsd.org Subject: Re: 2nd nfe interface not showing up on Tyan S2895 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 01:13:46 -0000 On Sun, Oct 28, 2007 at 07:27:25PM +0100, Arno J. Klaassen wrote: > Hi, > > I'm playing with RELENG_7 on a spare S2895 I have around and > have difficulties with the ethernet interfaces : > > - nfe0 shows up and works OK under 1Gbps (at least for > buildworlds etc over NFS) but under 100Mbps it says : > > install kernel: nfe0: tx v2 error 0x6004 > install kernel: nfe0: tx v2 error 0x6204 > Because developers don't know what exact meaning for Tx completion status word would be(Only NVIDIA knows that) nfe(4) just shows the possible error candidate. If you see the code you may notice no error recovery is attempted for the case. So I guess you can also ignore it unless the message contiously is printed on youe console while network activity is in progress. > - more serious, this board is supposed to have two of them > (enabled in BIOS as 'Slave Device') but only one of them > shows up at boot (and in pciconf -vl) > > According to the manual : "Two IEEE 802.3 Nvidia MAC 1000/100/10 > Ethernet (First from PRO 2200, Second from PRO 2050)" so apparently > not connected to the same chipset, and according to the > block diagram of MB-architecture, the "PRO 2050" should > be connected directly to the second CPU. > > Does anyone have a hint how to get that second interface at least > to show up? Thanx in advance and feel free to contact me for > more detailed info. > > Regards, > > Arno -- Regards, Pyun YongHyeon From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 01:42:54 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2261C16A468 for ; Tue, 30 Oct 2007 01:42:54 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id 765A513C4A6 for ; Tue, 30 Oct 2007 01:42:53 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 26184 invoked from network); 29 Oct 2007 09:47:05 +0300 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 29 Oct 2007 09:47:05 +0300 X-AntiVirus: Checked by Dr.Web [version: 4.44, engine: 4.44.0.09170, virus records: 251535, updated: 28.10.2007] Message-ID: <00f101c819f7$833d5370$0c00a8c0@Artem> From: "Artem Kuchin" To: Date: Mon, 29 Oct 2007 09:46:59 +0300 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="koi8-r"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Subject: Problems with gjournal or something else. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 01:42:54 -0000 I am experiencing a very weird problem with filesystem and it seems to be related to gjournal. It is FreeBSD 7-BETA1 RAID controller: 3WARE 7500x device driver: twe SMP enabled (Pentium D) Mirror raid. I have created the following partitions: twed1s1a 1100MB * twed1s1b swap 1024MB SWAP twed1s1d 5120MB * twed1s1e 30720MB * twed1s1f 261GB * did reboot just is case something is cached. Then did: newfs -J -b 8192 -f 1024 -g 50000 -h 20 -i 40960 /dev/twed1s1f gjournal load gjournal label -f /dev/twed1s1f tunefs -J enable -n disable /dev/twed1s1f mount -o noatime /dev/twed1s1f.journal /NEW/suit osiris# tunefs -p /dev/twed1s1f tunefs: ACLs: (-a) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) disabled tunefs: gjournal: (-J) enabled tunefs: maximum blocks per file in a cylinder group: (-e) 1024 tunefs: average file size: (-f) 50000 tunefs: average number of files in a directory: (-s) 20 tunefs: minimum percentage of free space: (-m) 8% tunefs: optimization preference: (-o) time tunefs: volume label: (-L) # newfs command for /dev/twed1s1f (/dev/twed1s1f) newfs -O 2 -a 16 -b 8192 -d 8192 -e 1024 -f 1024 -g 50000 -h 20 -m 8 -o time -s 273771329 /dev/twed1s1f Then i started a huge and long copying process from the old raid 5 array (about 200GB of data). Some time later i have found machine practically frozen becauase log file is filling with error: Oct 28 22:18:42 osiris kernel: g_vfs_done():twed1s1f.journal[WRITE(offset=279275085824, length=131072)]error = 5 Oct 28 22:18:42 osiris kernel: g_vfs_done():twed1s1f.journal[WRITE(offset=279278362624, length=131072)]error = 5 Oct 28 22:18:42 osiris kernel: g_vfs_done():twed1s1f.journal[WRITE(offset=279272857600, length=131072)]error = 5 Oct 28 22:18:42 osiris kernel: g_vfs_done():twed1s1f.journal[WRITE(offset=279278493696, length=131072)]error = 5 Oct 28 22:18:42 osiris kernel: g_vfs_done():twed1s1f.journal[WRITE(offset=279275216896, length=131072)]error = 5 Oct 28 22:18:42 osiris kernel: g_vfs_done():twed1s1f.journal[WRITE(offset=279278624768, length=131072)]error = 5 Oct 28 22:18:42 osiris kernel: g_vfs_done():twed1s1f.journal[WRITE(offset=279272988672, length=131072)]error = 5 Oct 28 22:18:42 osiris kernel: g_vfs_done():twed1s1f.journal[WRITE(offset=279275347968, length=131072)]error = 5 Oct 28 22:18:42 osiris kernel: g_vfs_done():twed1s1f.journal[WRITE(offset=279278755840, length=131072)]error = 5 Oct 28 22:18:42 osiris kernel: g_vfs_done():twed1s1f.journal[WRITE(offset=279273119744, length=131072)]error = 5 Oct 28 22:18:42 osiris kernel: g_vfs_done():twed1s1f.journal[WRITE(offset=279278886912, length=131072)]error = 5 Oct 28 22:18:42 osiris kernel: g_vfs_done():twed1s1f.journal[WRITE(offset=279275479040, length=131072)]error = 5 Oct 28 22:18:42 osiris kernel: g_vfs_done():twed1s1f.journal[WRITE(offset=279279017984, length=131072)]error = 5 Oct 28 22:18:42 osiris kernel: g_vfs_done():twed1s1f.journal[WRITE(offset=279273250816, length=131072)]error = 5 Oct 28 22:18:42 osiris kernel: g_vfs_done():twed1s1f.journal[WRITE(offset=279279149056, length=131072)]error = 5 Oct 28 22:18:42 osiris kernel: g_vfs_done():twed1s1f.journal[WRITE(offset=279275610112, length=131072)]error = 5 Oct 28 22:18:42 osiris kernel: g_vfs_done():twed1s1f.journal[WRITE(offset=279279280128, length=131072)]error = 5 Oct 28 22:18:42 osiris kernel: g_vfs_done():twed1s1f.journal[WRITE(offset=279273381888, length=131072)]error = 5 Oct 28 22:18:42 osiris kernel: g_vfs_done():twed1s1f.journal[WRITE(offset=279279411200, length=131072)]error = 5 Oct 28 22:18:42 osiris kernel: g_vfs_done():twed1s1f.journal[WRITE(offset=279275741184, length=131072)]error = 5 Since it is a EIO i have started verify on the contoller - everything is ok. Did cat /dev/random > /NEW/suit/aaa.dat filling the whole fs with a hunge file. - ok did dd if=/dev/twed1s1f of=/dev/null bs=1M - ok The i re-newfs-ed this fs w/o -J, unloaded gjournal and did the same copying - it took several hours and went just fine. So, it is not a hardware problem and it seems to be related to gjournal. One more weird thing happened here. gjournal complained hat BIO_FLUSH is not supported by the driver. However, AFAIK twe is working via scsi subsystem and the authour of gjournal said somewhere that he has had implemeneted BIO_FLISH for scsi and he specifically mentioned that he has tested twe and twa and they both support BIO_FLUSH. Alo, I think offset value in the error message is out of range of this filesystem. The controller has a cache of 64MB on board and the author of gjournal said in some discussion that if BIO_FLUSH support is missing and controller chache is larger than gjournal's cache then there might be problems. I did not find any specific value for the gjournal cache. So, the problem maybe related to this issue (something gets messed up). but i am not sure. Any idea anyone? -- Regards, Artem From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 01:55:53 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9D55316A41A for ; Tue, 30 Oct 2007 01:55:53 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 9033F13C4B5 for ; Tue, 30 Oct 2007 01:55:53 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 991981CC06E; Mon, 29 Oct 2007 18:55:34 -0700 (PDT) Date: Mon, 29 Oct 2007 18:55:34 -0700 From: Jeremy Chadwick To: Mark Powell Message-ID: <20071030015534.GA69514@eos.sc1.parodius.com> References: <20071029092531.J99722@rust.salford.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071029092531.J99722@rust.salford.ac.uk> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org Subject: Re: WRITE_DMA48 error causing loss of ZFS array X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 01:55:53 -0000 On Mon, Oct 29, 2007 at 09:59:11AM +0000, Mark Powell wrote: > I've experienced several dma errors over the past few months with various > incarnations of 7.0 which were all fixed. This could be relevant: http://kerneltrap.org/mailarchive/freebsd-current/2007/10/2/326931 -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 02:03:46 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 770DE16A417 for ; Tue, 30 Oct 2007 02:03:46 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 6806013C48D for ; Tue, 30 Oct 2007 02:03:46 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id C6A581CC065; Mon, 29 Oct 2007 19:03:30 -0700 (PDT) Date: Mon, 29 Oct 2007 19:03:30 -0700 From: Jeremy Chadwick To: Rob Zietlow Message-ID: <20071030020330.GA69657@eos.sc1.parodius.com> References: <47230D02.1080602@moneybookers.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org, Stefan Lambrev Subject: Re: [7.0-Beta] can no longer ssh into just upgraded host X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 02:03:46 -0000 On Mon, Oct 29, 2007 at 06:11:24AM -0500, Rob Zietlow wrote: > Correct me if I'm wrong but with PAM shouldn't it be all or nothing? I > wouldn't be able to connect via the local LAN if pam was some how > misconfigured (I haven't touched any PAM files though I may have missed it > during mergemaster. Please correct me if I am incorrect. And there is > nothing listed in /var/log/messages or dmesg -a regarding this issue. The > only place that says anything is /var/log/auth. That's true. I didn't know LAN connectivity was working for you; sorry. There's another user who just reported something similar, although for him it's the opposite direction (failure when SSHing from a 7.0 host to one specific 6.2 host): http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078935.html -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 02:17:05 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D475416A41B for ; Tue, 30 Oct 2007 02:17:05 +0000 (UTC) (envelope-from avatar@mmlab.cse.yzu.edu.tw) Received: from www.mmlab.cse.yzu.edu.tw (www.mmlab.cse.yzu.edu.tw [140.138.150.166]) by mx1.freebsd.org (Postfix) with ESMTP id 7F36413C491 for ; Tue, 30 Oct 2007 02:17:05 +0000 (UTC) (envelope-from avatar@mmlab.cse.yzu.edu.tw) Received: by www.mmlab.cse.yzu.edu.tw (qmail, from userid 1000) id 2C0108CA04D; Tue, 30 Oct 2007 09:38:48 +0800 (CST) Received: from localhost (localhost [127.0.0.1]) by www.mmlab.cse.yzu.edu.tw (qmail) with ESMTP id 0D4348CA04C; Tue, 30 Oct 2007 09:38:48 +0800 (CST) Date: Tue, 30 Oct 2007 09:38:47 +0800 (CST) From: Tai-hwa Liang To: David Wolfskill In-Reply-To: <20071029190208.GD78150@bunrab.catwhisker.org> Message-ID: <0710300936223.30335@www.mmlab.cse.yzu.edu.tw> References: <20071029190208.GD78150@bunrab.catwhisker.org> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-727875523-1193708327=:30335" Cc: current@freebsd.org Subject: Re: Detach of an0 induced kernel panic in 7.0-PRE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 02:17:05 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-727875523-1193708327=:30335 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed On Mon, 29 Oct 2007, David Wolfskill wrote: [...] > command-line prompt. In an attempt to speed things up(!), I detached > the an0 NIC. > > Boom! > > h252(7.0)[6] uname -a > FreeBSD h252.dhw.mail-abuse.org. 7.0-BETA1 FreeBSD 7.0-BETA1 #573: Mon Oct 29 10:24:52 PDT 2007 root@h252.dhw.mail-abuse.org.:/common/S3/obj/usr/src/sys/CANARY i386 > h252(7.0)[7] > h252(7.0)[1] cd /usr/obj/usr/src/sys/CANARY/ > h252(7.0)[2] kgdb kernel.debug /var/crash/vmcore.5 > [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] > GNU gdb 6.1.1 [FreeBSD] > ... > This GDB was configured as "i386-marcel-freebsd". > > Unread portion of the kernel message buffer: > an0: RID access failed > an0: detached > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xc8283178 > fault code = supervisor write, page not present > instruction pointer = 0x20:0xc04daaf7 > stack pointer = 0x28:0xe2987c5c > frame pointer = 0x28:0xe2987c78 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 12 (swi4: clock sio) > trap number = 12 > panic: page fault > cpuid = 0 > Uptime: 31m46s > Physical memory: 1011 MB > Dumping 173 MB: 158 142 126 110 94 78 62 46 30 14 > > #0 doadump () at pcpu.h:195 > 195 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); > (kgdb) bt > #0 doadump () at pcpu.h:195 > #1 0xc073b637 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 > #2 0xc073b8f9 in panic (fmt=Variable "fmt" is not available. > ) at /usr/src/sys/kern/kern_shutdown.c:563 > #3 0xc0a005dc in trap_fatal (frame=0xe2987c1c, eva=3358077304) > at /usr/src/sys/i386/i386/trap.c:872 > #4 0xc0a00860 in trap_pfault (frame=0xe2987c1c, usermode=0, eva=3358077304) > at /usr/src/sys/i386/i386/trap.c:785 > #5 0xc0a011d5 in trap (frame=0xe2987c1c) at /usr/src/sys/i386/i386/trap.c:463 > #6 0xc09e71eb in calltrap () at /usr/src/sys/i386/i386/exception.s:139 > #7 0xc04daaf7 in an_stats_update (xsc=0xc8282000) at atomic.h:149 > #8 0xc074d7ea in softclock (dummy=0x0) at /usr/src/sys/kern/kern_timeout.c:274 > #9 0xc071ef0b in ithread_loop (arg=0xc3f0d2f0) > at /usr/src/sys/kern/kern_intr.c:1036 > #10 0xc071bc19 in fork_exit (callout=0xc071ed60 , > arg=0xc3f0d2f0, frame=0xe2987d38) at /usr/src/sys/kern/kern_fork.c:796 > #11 0xc09e7260 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:205 > (kgdb) > > Any hints would be welcome. > > (Save for this -- well, and the fact that I can't really use wi0(4) while > running 7.x or 8 -- RELENG_7 seems OK so far.) > > I'm about to flip over to slice 4 (to build today's HEAD), but after > that's done, I should be able to look at the crash dump a bit > more. > > (And I'm fine with testing changes & patches -- given enough hints, I > can cause moderate damage to unsuspecting source files, even.) Does the attached patch help? -- Cheers, Tai-hwa Liang --0-727875523-1193708327=:30335 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=if_an.c.stat.patch Content-Transfer-Encoding: BASE64 Content-ID: <07103009384712.30335@www.mmlab.cse.yzu.edu.tw> Content-Description: Content-Disposition: attachment; filename=if_an.c.stat.patch LS0tIGlmX2FuLmMub3JpZwkyMDA3LTA5LTEyIDE1OjA4OjI2LjAwMDAwMDAw MCArMDgwMA0KKysrIGlmX2FuLmMJMjAwNy0xMC0zMCAwOTozNDo0NS4wMDAw MDAwMDAgKzA4MDANCkBAIC0xMTUxLDYgKzExNTEsMTAgQEANCiANCiAJc2Mg PSB4c2M7DQogCUFOX0xPQ0soc2MpOw0KKwlpZiAoc2MtPmFuX2dvbmUpIHsN CisJCUFOX1VOTE9DSyhzYyk7DQorCQlyZXR1cm47DQorCX0NCiAJaWZwID0g c2MtPmFuX2lmcDsNCiANCiAJc2MtPmFuX3N0YXR1cy5hbl90eXBlID0gQU5f UklEX1NUQVRVUzsNCg== --0-727875523-1193708327=:30335-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 02:26:32 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 25ECD16A41A for ; Tue, 30 Oct 2007 02:26:32 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by mx1.freebsd.org (Postfix) with ESMTP id E0D9E13C49D for ; Tue, 30 Oct 2007 02:26:31 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so2377298waf for ; Mon, 29 Oct 2007 19:26:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; 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=JEGgeVixaD5Me8z0wnqjeHYt4aKUOOhAq4dEGOWVXQs=; b=cVlvFeRnboVC4ax6iQj8FqpXlJEtOfiVsrg6wn22+nBzZs47mjX72wtk2YnzXR2TNgfhXqfTzcpUEsiAitchKNZfSc2ji1Y5CSC2kaXKpLB3xw8WmUMk0cCd7IyzoMl5FDVKn3WGuJ+CTzVxuiVr0OXK735g1ME1Qkn7F+QjobA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=FRHEy05EfUxByLJZIVITJp7KfDcpnj+m0pFvnaoVHaKN38acKz7azhIXzfaArhjtyuMMJF+65Cb2KdYWGtLYkG+sv78naVQoowkl69NnNIP8ujbpdGBDCrd+7buuTGoqx2ONr0Hv0q/tXmODKgawmqJnH5fZKIbbvqv/ofqeyxI= Received: by 10.114.38.2 with SMTP id l2mr1272532wal.1193709505430; Mon, 29 Oct 2007 18:58:25 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id j21sm14475335wah.2007.10.29.18.58.21 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 29 Oct 2007 18:58:23 -0700 (PDT) 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 l9U1wGYW038402 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Oct 2007 10:58:16 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l9U1wGcO038401; Tue, 30 Oct 2007 10:58:16 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 30 Oct 2007 10:58:16 +0900 From: Pyun YongHyeon To: Joe Marcus Clarke Message-ID: <20071030015816.GD37693@cdnetworks.co.kr> References: <20070213000922.GA62412@cdnetworks.co.kr> <1171327083.98536.5.camel@shumai.marcuscom.com> <20070213044746.GC62412@cdnetworks.co.kr> <1171344897.98536.14.camel@shumai.marcuscom.com> <20070213054802.GD62412@cdnetworks.co.kr> <45D355D9.5000805@FreeBSD.org> <20070215055918.GA4319@cdnetworks.co.kr> <45D9F303.1030302@FreeBSD.org> <20070220012443.GB912@cdnetworks.co.kr> <45DB40A5.8000406@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="VrqPEDrXMn8OVzN4" Content-Disposition: inline In-Reply-To: <45DB40A5.8000406@FreeBSD.org> User-Agent: Mutt/1.4.2.1i Cc: current@FreeBSD.org Subject: Re: Constant stream of errors on msk0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 02:26:32 -0000 --VrqPEDrXMn8OVzN4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Feb 20, 2007 at 01:40:37PM -0500, Joe Marcus Clarke wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Pyun YongHyeon wrote: > > > > > Does the other GigE work without issues on Cisco 6500? > > I haven't tried this card on another gigE switch. However, the same > switch port on the same switch did not exhibit these problems with the > myk driver under 6.X. At least as far as I know my desk port was not > moved in the IDF. > > > > > The msk(4) can have a bug with autonegotiation but I've never seen > > negotiation mismatches on msk(4). Whilst writing the driver I've > > checked speed/link negotiation against gigabit switch and directly > > connected GigE and I found nothing unusual. Of course, that does > > not necessarily mean msk(4) is perfect for link negotiation. > > > > Because you've said myk(4) works well on Cisco 6500 I have to > > diagnose the issue. When setting the link manually on gigabit > > environments, nomally one side should be master and the other the > > slave so how about forcing master bit on msk(4) side? > > > > #ifconfig msk0 media 1000baseTX mediaopt full-duplex link0 > > ^^^^^ > > This does not help. I tried 1000BaseTX/full, 100BaseTX/full, and > 100BaseTX/half. All three exhibited the same problem with constantly > incrementing input errors. > Hi, Are you still interesting in fixing autonegotiation issue on msk(4) at 1000bps? If so please try attached patch and let me know result. -- Regards, Pyun YongHyeon --VrqPEDrXMn8OVzN4 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="e1000phy.aneg.patch" Index: e1000phy.c =================================================================== RCS file: /home/ncvs/src/sys/dev/mii/e1000phy.c,v retrieving revision 1.19 diff -u -r1.19 e1000phy.c --- e1000phy.c 29 Oct 2007 05:50:22 -0000 1.19 +++ e1000phy.c 30 Oct 2007 01:56:55 -0000 @@ -397,8 +397,10 @@ /* * Only used for autonegotiation. */ - if (IFM_SUBTYPE(ife->ifm_media) != IFM_AUTO) + if (IFM_SUBTYPE(ife->ifm_media) != IFM_AUTO) { + sc->mii_ticks = 0; break; + } /* * check for link. @@ -411,6 +413,8 @@ } /* Announce link loss right after it happens. */ + if (sc->mii_ticks++ == 0) + break; if (sc->mii_ticks <= sc->mii_anegticks) return (0); --VrqPEDrXMn8OVzN4-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 03:44:33 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DA1716A421 for ; Tue, 30 Oct 2007 03:44:33 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 2459D13C4B3 for ; Tue, 30 Oct 2007 03:44:32 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.222] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id l9U3iGH7097134 for ; Mon, 29 Oct 2007 20:44:16 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <4726A890.5090705@freebsd.org> Date: Mon, 29 Oct 2007 20:44:16 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: -mdoc vs. -man X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 03:44:33 -0000 I've had some requests from people who want to use the libarchive and bsdtar manpages on non-BSD systems that don't support -mdoc. Any problems if I reworked these manpages to only require -man-old for compatibility with these systems? (Other than the inherent tediousness of such a project, that is.) Tim Kientzle From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 03:50:01 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23F4E16A41B for ; Tue, 30 Oct 2007 03:50:01 +0000 (UTC) (envelope-from louisk@cryptomonkeys.com) Received: from abeyance.cryptomonkeys.com (abeyance.cryptomonkeys.com [67.42.3.2]) by mx1.freebsd.org (Postfix) with ESMTP id 8DDA713C4B0 for ; Tue, 30 Oct 2007 03:50:00 +0000 (UTC) (envelope-from louisk@cryptomonkeys.com) Received: from [192.168.1.102] (c-76-21-17-250.hsd1.ca.comcast.net [76.21.17.250]) (authenticated bits=0) by abeyance.cryptomonkeys.com (8.13.8+Sun/8.13.8) with ESMTP id l9U3W0Gn019975 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 29 Oct 2007 19:32:16 -0800 (PST) Message-ID: <4726A59F.4060002@cryptomonkeys.com> Date: Mon, 29 Oct 2007 20:31:43 -0700 From: Louis Kowolowski Organization: Cryptomonkeys UNIX/Security Consulting User-Agent: Thunderbird 2.0.0.6 (X11/20071012) MIME-Version: 1.0 To: current@freebsd.org References: <20071029190208.GD78150@bunrab.catwhisker.org> In-Reply-To: <20071029190208.GD78150@bunrab.catwhisker.org> X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-cryptomonkeys-MailScanner-Information: Please contact abuse@cryptomonkeys.com for more information X-cryptomonkeys-MailScanner: Found to be clean X-cryptomonkeys-MailScanner-From: louisk@cryptomonkeys.com X-Spam-Status: No Cc: Subject: kernel panic in 7.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 03:50:01 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've been getting these for about 2wks now. I see nothing in /var/log/messages. System just hangs and the screen goes black. I'm in X so I can't see what is on the console. I enabled crash dumps and I'm pasting the lastest backtrace. Is there anything else I can provide? Thanks! 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-BETA1 #6: Thu Oct 25 15:58:10 PDT 2007 root@dyn-2-201.pgp.com:/usr/obj/usr/src/sys/MONTEZUMA Timecounter "i8254" frequency 1193167 Hz quality 0 CPU: Intel(R) Core(TM)2 CPU T7600 @ 2.33GHz (2327.49-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20100000 AMD Features2=0x1 Cores per package: 2 real memory = 3219980288 (3070 MB) avail memory = 3145494528 (2999 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ACPI Warning (tbfadt-0505): Optional field "Gpe1Block" has zero address or length: 0 102C/0 [20070320] ioapic0: Changing APIC ID to 1 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) cryptosoft0: on motherboard acpi0: on motherboard acpi0: [ITHREAD] acpi_ec0: port 0x62,0x66 on acpi0 acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, bff00000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 cpu0: on acpi0 est0: on cpu0 p4tcc0: on cpu0 cpu1: on acpi0 est1: on cpu1 p4tcc1: on cpu1 acpi_lid0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0x2000-0x20ff mem 0xd0000000-0xdfffffff,0xee100000-0xee10ffff irq 16 at device 0.0 on pci1 pcm0: mem 0xee400000-0xee403fff irq 17 at device 27.0 on pci0 pcm0: [ITHREAD] pcib2: irq 20 at device 28.0 on pci0 pci2: on pcib2 em0: port 0x3000-0x301f mem 0xee000000-0xee01ffff irq 16 at device 0.0 on pci2 em0: Ethernet address: 00:16:41:58:25:48 em0: [ITHREAD] pcib3: irq 21 at device 28.1 on pci0 pci3: on pcib3 ath0: mem 0xedf00000-0xedf0ffff irq 17 at device 0.0 on pci3 ath0: [ITHREAD] ath0: using obsoleted if_watchdog interface ath0: Ethernet address: 00:16:cf:7b:0d:0d ath0: mac 10.3 phy 6.1 radio 10.2 pcib4: irq 22 at device 28.2 on pci0 pci4: on pcib4 pcib5: irq 23 at device 28.3 on pci0 pci12: on pcib5 uhci0: port 0x1800-0x181f irq 16 at device 29.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 0x1820-0x183f irq 17 at device 29.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 uhci2: port 0x1840-0x185f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb2: on uhci2 usb2: USB revision 1.0 uhub2: on usb2 uhub2: 2 ports with 2 removable, self powered uhci3: port 0x1860-0x187f irq 19 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb3: on uhci3 usb3: USB revision 1.0 uhub3: on usb3 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xee404000-0xee4043ff irq 19 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: on usb4 uhub4: 8 ports with 8 removable, self powered pcib6: at device 30.0 on pci0 pci21: on pcib6 cbb0: mem 0xe4300000-0xe4300fff irq 16 at device 0.0 on pci21 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb0: [ITHREAD] isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1880-0x188f at device 31.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] atapci1: port 0x18c8-0x18cf,0x18ac-0x18af,0x18c0-0x18c7,0x18a8-0x18ab,0x18b0-0x18bf mem 0xee404400-0xee4047ff irq 16 at device 31.2 on pci0 atapci1: [ITHREAD] atapci1: AHCI Version 01.10 controller with 4 ports detected ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: port not implemented ata3: [ITHREAD] ata4: on atapci1 ata4: port not implemented ata4: [ITHREAD] ata5: on atapci1 ata5: port not implemented ata5: [ITHREAD] pci0: at device 31.3 (no driver attached) acpi_tz0: on acpi0 acpi_tz1: on acpi0 speaker0: port 0x61 on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 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 Generic PS/2 mouse, device ID 0 sio0: configured irq 3 not in bitmap of probed irqs 0 sio0: port may not be enabled battery0: on acpi0 acpi_acad0: on acpi0 acpi_ibm0: on acpi0 sio0: configured irq 3 not in bitmap of probed irqs 0 sio0: port may not be enabled pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcffff,0xd0000-0xd0fff,0xd1000-0xd1fff,0xdc000-0xdffff,0xe0000-0xeffff pnpid ORM0000 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> 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 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio0: [FILTER] 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 ugen0: on uhub3 ugen1: on uhub3 NULL mp in getnewvnode() Timecounters tick every 1.000 msec ad0: 238475MB at ata0-master UDMA100 ad4: 238475MB at ata2-master SATA150 pcm0: pcm0: SMP: AP CPU #1 Launched! Trying to mount root from ufs:/dev/ad4s1a kgdb output: [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x20:0xc0712901 stack pointer = 0x28:0xe8e88824 frame pointer = 0x28:0xe8e88850 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 1437 (gkrellm) trap number = 12 panic: page fault cpuid = 0 Uptime: 5h5m16s Physical memory: 3058 MB Dumping 153 MB: 138 122 106 90 74 58 42 26 10 #0 doadump () at pcpu.h:195 195 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); (kgdb) backtrace #0 doadump () at pcpu.h:195 #1 0xc07461aa in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 #2 0xc074649c in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:563 #3 0xc0a26704 in trap_fatal (frame=0xe8e887e4, eva=0) at /usr/src/sys/i386/i386/trap.c:872 #4 0xc0a26975 in trap_pfault (frame=0xe8e887e4, usermode=0, eva=0) at /usr/src/sys/i386/i386/trap.c:785 #5 0xc0a272c1 in trap (frame=0xe8e887e4) at /usr/src/sys/i386/i386/trap.c:463 #6 0xc0a0e33b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc0712901 in clone_create (cdp=0xc0db3f74, csw=0xc0db2fa0, up=0xe8e88874, dp=0xe8e88940, extra=0) at /usr/src/sys/kern/kern_conf.c:938 #8 0xc0da3eae in ?? () #9 0xc0db3f74 in ?? () #10 0xc0db2fa0 in ?? () #11 0xe8e88874 in ?? () #12 0xe8e88940 in ?? () #13 0x00000000 in ?? () #14 0xc0ab29b5 in ?? () #15 0xc0d3511e in ?? () #16 0xffffffff in ?? () #17 0xc0da3e48 in ?? () #18 0xc66e4400 in ?? () #19 0xe8e88950 in ?? () #20 0xc06e0adc in devfs_lookup (ap=0x0) at /usr/src/sys/fs/devfs/devfs_vnops.c:627 Previous frame identical to this frame (corrupt stack?) (kgdb) - -- Louis Kowolowski louisk@cryptomonkeys.com Cryptomonkeys: http://www.cryptomonkeys.com/~louisk Everyone is a genius. It's just that some people are too stupid to realize it. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHJqWeZk0r6oAkN7YRAiUOAJsEzMjvY/e2rKFPP6/w4pQVh7NIGQCfRp39 18ZPUy4iDgE1hJ7KC8QXs7c= =kHMs -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 03:51:59 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FB7616A419 for ; Tue, 30 Oct 2007 03:51:59 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 65B6D13C4AA for ; Tue, 30 Oct 2007 03:51:57 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id l9U3p2jj018166 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Oct 2007 14:21:02 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Tue, 30 Oct 2007 14:20:57 +1030 User-Agent: KMail/1.9.7 References: <200710111741.34992.jhb@FreeBSD.org> <200710282350.48031.jhb@freebsd.org> In-Reply-To: <200710282350.48031.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1272948.B2tjWIDkzc"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200710301420.59163.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.58 on 203.31.81.10 Cc: Robert Backhaus , current@freebsd.org Subject: Re: New-bus unit wiring via hints.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 03:51:59 -0000 --nextPart1272948.B2tjWIDkzc Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Mon, 29 Oct 2007, John Baldwin wrote: > You could easily extend it to USB if you can come up with a > reasonable way to specify the wiring. You could possibly wire units > via hints that specify serial numbers or manfacturer and model > strings, etc. However, I'm less familiar with USB so I'm less unsure > what specific attributes would be suitable for wiring or not. Serial numbers can be OK. Bus/port number would be good too - a lot of cheap stuff doesn't have a=20 serial number (that is real) where as bus/port number would give you a=20 way to differentiate (eg cheap serial adapters) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1272948.B2tjWIDkzc Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHJqoj5ZPcIHs/zowRAocWAKCG/7eF6vZvXKBWSeGdPuslDg/JgACfSeut WmbgROIrcwRj+F7SzNtSxcs= =eHoM -----END PGP SIGNATURE----- --nextPart1272948.B2tjWIDkzc-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 03:53:13 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A7B916A474 for ; Tue, 30 Oct 2007 03:53:13 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.freebsd.org (Postfix) with ESMTP id 4E9C113C480 for ; Tue, 30 Oct 2007 03:53:12 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (localhost [127.0.0.1]) by bunrab.catwhisker.org (8.13.3/8.13.3) with ESMTP id l9U3qrvO086949; Mon, 29 Oct 2007 20:52:53 -0700 (PDT) (envelope-from david@bunrab.catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.13.3/8.13.1/Submit) id l9U3qr9D086948; Mon, 29 Oct 2007 20:52:53 -0700 (PDT) (envelope-from david) Date: Mon, 29 Oct 2007 20:52:53 -0700 From: David Wolfskill To: Tai-hwa Liang Message-ID: <20071030035253.GF78150@bunrab.catwhisker.org> Mail-Followup-To: David Wolfskill , Tai-hwa Liang , current@freebsd.org References: <20071029190208.GD78150@bunrab.catwhisker.org> <0710300936223.30335@www.mmlab.cse.yzu.edu.tw> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pyE8wggRBhVBcj8z" Content-Disposition: inline In-Reply-To: <0710300936223.30335@www.mmlab.cse.yzu.edu.tw> User-Agent: Mutt/1.4.2.1i Cc: current@freebsd.org Subject: Re: Detach of an0 induced kernel panic in 7.0-PRE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 03:53:13 -0000 --pyE8wggRBhVBcj8z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 30, 2007 at 09:38:47AM +0800, Tai-hwa Liang wrote: > ... > >Unread portion of the kernel message buffer: > >an0: RID access failed > >an0: detached > > > > > >Fatal trap 12: page fault while in kernel mode > ... > >#0 doadump () at pcpu.h:195 > >195 __asm __volatile("movl %%fs:0,%0" : "=3Dr" (td)); > >(kgdb) bt > >#0 doadump () at pcpu.h:195 > >#1 0xc073b637 in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.= c:409 > >#2 0xc073b8f9 in panic (fmt=3DVariable "fmt" is not available. > >) at /usr/src/sys/kern/kern_shutdown.c:563 > >#3 0xc0a005dc in trap_fatal (frame=3D0xe2987c1c, eva=3D3358077304) > > at /usr/src/sys/i386/i386/trap.c:872 > >#4 0xc0a00860 in trap_pfault (frame=3D0xe2987c1c, usermode=3D0,=20 > >eva=3D3358077304) > > at /usr/src/sys/i386/i386/trap.c:785 > >#5 0xc0a011d5 in trap (frame=3D0xe2987c1c) at=20 > >/usr/src/sys/i386/i386/trap.c:463 > >#6 0xc09e71eb in calltrap () at /usr/src/sys/i386/i386/exception.s:139 > >#7 0xc04daaf7 in an_stats_update (xsc=3D0xc8282000) at atomic.h:149 > >#8 0xc074d7ea in softclock (dummy=3D0x0) at=20 > >/usr/src/sys/kern/kern_timeout.c:274 > >#9 0xc071ef0b in ithread_loop (arg=3D0xc3f0d2f0) > > at /usr/src/sys/kern/kern_intr.c:1036 > >#10 0xc071bc19 in fork_exit (callout=3D0xc071ed60 , > > arg=3D0xc3f0d2f0, frame=3D0xe2987d38) at /usr/src/sys/kern/kern_fork.= c:796 > >#11 0xc09e7260 in fork_trampoline () at=20 > >/usr/src/sys/i386/i386/exception.s:205 > >(kgdb) > ... > Does the attached patch help? Aye, it does appear to do so. I tested at home, where the an0 NIC is actually useful. But I managed to detach the card before the script reported successful association; the machine kept running (and the script fell back to trying the wi0 NIC, since the an0 NIC was no longer there). I'd call that a definite improvement -- and fast response! Thanks again! Peace, david --=20 David H. Wolfskill david@catwhisker.org Proprietary data formats obfuscate, rather than disseminate, information. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --pyE8wggRBhVBcj8z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iEYEARECAAYFAkcmqpQACgkQmprOCmdXAD2A8gCfWcsyoKMuFQjJzFFbGM26DSq0 VNUAn1BdIPXHoKcdyNIsRIYcsVTQ4wbw =eKAa -----END PGP SIGNATURE----- --pyE8wggRBhVBcj8z-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 04:07:24 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC92E16A418; Tue, 30 Oct 2007 04:07:24 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 01D1713C4A5; Tue, 30 Oct 2007 04:07:23 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id l9U3p2jj018166 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Oct 2007 14:21:02 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Tue, 30 Oct 2007 14:20:57 +1030 User-Agent: KMail/1.9.7 References: <200710111741.34992.jhb@FreeBSD.org> <200710282350.48031.jhb@freebsd.org> In-Reply-To: <200710282350.48031.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1272948.B2tjWIDkzc"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200710301420.59163.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.58 on 203.31.81.10 Cc: Robert Backhaus , current@freebsd.org Subject: Re: New-bus unit wiring via hints.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 04:07:24 -0000 --nextPart1272948.B2tjWIDkzc Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Mon, 29 Oct 2007, John Baldwin wrote: > You could easily extend it to USB if you can come up with a > reasonable way to specify the wiring. You could possibly wire units > via hints that specify serial numbers or manfacturer and model > strings, etc. However, I'm less familiar with USB so I'm less unsure > what specific attributes would be suitable for wiring or not. Serial numbers can be OK. Bus/port number would be good too - a lot of cheap stuff doesn't have a=20 serial number (that is real) where as bus/port number would give you a=20 way to differentiate (eg cheap serial adapters) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1272948.B2tjWIDkzc Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHJqoj5ZPcIHs/zowRAocWAKCG/7eF6vZvXKBWSeGdPuslDg/JgACfSeut WmbgROIrcwRj+F7SzNtSxcs= =eHoM -----END PGP SIGNATURE----- --nextPart1272948.B2tjWIDkzc-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 04:57:01 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 144D316A418 for ; Tue, 30 Oct 2007 04:57:01 +0000 (UTC) (envelope-from avatar@mmlab.cse.yzu.edu.tw) Received: from www.mmlab.cse.yzu.edu.tw (www.mmlab.cse.yzu.edu.tw [140.138.150.166]) by mx1.freebsd.org (Postfix) with ESMTP id D59FC13C4B2 for ; Tue, 30 Oct 2007 04:57:00 +0000 (UTC) (envelope-from avatar@mmlab.cse.yzu.edu.tw) Received: by www.mmlab.cse.yzu.edu.tw (qmail, from userid 1000) id 652568CA066; Tue, 30 Oct 2007 12:39:38 +0800 (CST) Received: from localhost (localhost [127.0.0.1]) by www.mmlab.cse.yzu.edu.tw (qmail) with ESMTP id 4A0C38CA04D; Tue, 30 Oct 2007 12:39:38 +0800 (CST) Date: Tue, 30 Oct 2007 12:39:38 +0800 (CST) From: Tai-hwa Liang To: David Wolfskill In-Reply-To: <20071030035253.GF78150@bunrab.catwhisker.org> Message-ID: <0710301238250.31552@www.mmlab.cse.yzu.edu.tw> References: <20071029190208.GD78150@bunrab.catwhisker.org> <0710300936223.30335@www.mmlab.cse.yzu.edu.tw> <20071030035253.GF78150@bunrab.catwhisker.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@freebsd.org Subject: Re: Detach of an0 induced kernel panic in 7.0-PRE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 04:57:01 -0000 On Mon, 29 Oct 2007, David Wolfskill wrote: > On Tue, Oct 30, 2007 at 09:38:47AM +0800, Tai-hwa Liang wrote: >> ... >>> Unread portion of the kernel message buffer: >>> an0: RID access failed >>> an0: detached >>> >>> >>> Fatal trap 12: page fault while in kernel mode >> ... >>> #0 doadump () at pcpu.h:195 >>> 195 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); >>> (kgdb) bt >>> #0 doadump () at pcpu.h:195 >>> #1 0xc073b637 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 >>> #2 0xc073b8f9 in panic (fmt=Variable "fmt" is not available. >>> ) at /usr/src/sys/kern/kern_shutdown.c:563 >>> #3 0xc0a005dc in trap_fatal (frame=0xe2987c1c, eva=3358077304) >>> at /usr/src/sys/i386/i386/trap.c:872 >>> #4 0xc0a00860 in trap_pfault (frame=0xe2987c1c, usermode=0, >>> eva=3358077304) >>> at /usr/src/sys/i386/i386/trap.c:785 >>> #5 0xc0a011d5 in trap (frame=0xe2987c1c) at >>> /usr/src/sys/i386/i386/trap.c:463 >>> #6 0xc09e71eb in calltrap () at /usr/src/sys/i386/i386/exception.s:139 >>> #7 0xc04daaf7 in an_stats_update (xsc=0xc8282000) at atomic.h:149 >>> #8 0xc074d7ea in softclock (dummy=0x0) at >>> /usr/src/sys/kern/kern_timeout.c:274 >>> #9 0xc071ef0b in ithread_loop (arg=0xc3f0d2f0) >>> at /usr/src/sys/kern/kern_intr.c:1036 >>> #10 0xc071bc19 in fork_exit (callout=0xc071ed60 , >>> arg=0xc3f0d2f0, frame=0xe2987d38) at /usr/src/sys/kern/kern_fork.c:796 >>> #11 0xc09e7260 in fork_trampoline () at >>> /usr/src/sys/i386/i386/exception.s:205 >>> (kgdb) >> ... >> Does the attached patch help? > > Aye, it does appear to do so. > > I tested at home, where the an0 NIC is actually useful. But I managed > to detach the card before the script reported successful association; > the machine kept running (and the script fell back to trying the wi0 > NIC, since the an0 NIC was no longer there). > > I'd call that a definite improvement -- and fast response! Thanks again! Thank you for the testing works. I'll ask for re@'s approval once this is settled in HEAD. -- Thanks, Tai-hwa Liang From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 05:21:04 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4931716A418 for ; Tue, 30 Oct 2007 05:21:04 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp4.yandex.ru (smtp4.yandex.ru [213.180.223.136]) by mx1.freebsd.org (Postfix) with ESMTP id 8FCA713C48E for ; Tue, 30 Oct 2007 05:21:03 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mail.kirov.so-cdu.ru ([77.72.136.145]:58354 "EHLO [127.0.0.1]" smtp-auth: "bu7cher" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S738276AbXJ3FTu (ORCPT ); Tue, 30 Oct 2007 08:19:50 +0300 X-Comment: RFC 2476 MSA function at smtp4.yandex.ru logged sender identity as: bu7cher Message-ID: <4726BEEE.3070704@yandex.ru> Date: Tue, 30 Oct 2007 08:19:42 +0300 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: Nathan Butcher References: <4725558F.6040702@fusiongol.com> In-Reply-To: <4725558F.6040702@fusiongol.com> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, blacknova@tut.by Subject: Re: Problem with ATAPI device on JMicron JMB363 on 7.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 05:21:04 -0000 Nathan Butcher wrote: > I have a Gigabyte GA-G33-DS3R. FreeBSD 7.0-BETA1 detects the chipset, > but no devices attached to the SATA controllers find their relative /dev > entries. My SATA DVD-combo drive simply doesn't get /dev/acd0, and as a > result I cannot access the drive. I've tried hard drives too, with the > same results. You can update your BETA1 to the fresh RELENG_7. Soren have fixed this issue. Also, ATAPI support was added to the AHCI driver (only for CURRENT yet). > The IDE interface seems to work for me (I have an IDE -> CF converter in > there), but I don't have a PATA optical drive to test. For Vladimir: here is a description for your issue (russian) http://unix1.jinr.ru/~lavr/cd_dvd_intel965.html -- WBR, Andrey V. Elsukov From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 05:38:34 2007 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 21CEB16A418 for ; Tue, 30 Oct 2007 05:38:34 +0000 (UTC) (envelope-from marcus@FreeBSD.org) Received: from creme-brulee.marcuscom.com (penna-pt.tunnel.tserv1.fmt.ipv6.he.net [IPv6:2001:470:1f00:ffff::1279]) by mx1.freebsd.org (Postfix) with ESMTP id DCB6313C447 for ; Tue, 30 Oct 2007 05:38:33 +0000 (UTC) (envelope-from marcus@FreeBSD.org) Received: from [IPv6:2001:470:1f00:2464::4] (shumai.marcuscom.com [IPv6:2001:470:1f00:2464::4]) by creme-brulee.marcuscom.com (8.14.1/8.14.1) with ESMTP id l9U5e3Gc031806; Tue, 30 Oct 2007 01:40:03 -0400 (EDT) (envelope-from marcus@FreeBSD.org) From: Joe Marcus Clarke To: pyunyh@gmail.com In-Reply-To: <20071030015816.GD37693@cdnetworks.co.kr> References: <20070213000922.GA62412@cdnetworks.co.kr> <1171327083.98536.5.camel@shumai.marcuscom.com> <20070213044746.GC62412@cdnetworks.co.kr> <1171344897.98536.14.camel@shumai.marcuscom.com> <20070213054802.GD62412@cdnetworks.co.kr> <45D355D9.5000805@FreeBSD.org> <20070215055918.GA4319@cdnetworks.co.kr> <45D9F303.1030302@FreeBSD.org> <20070220012443.GB912@cdnetworks.co.kr> <45DB40A5.8000406@FreeBSD.org> <20071030015816.GD37693@cdnetworks.co.kr> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-ymvVIE3XIfmGHmDfSXla" Organization: FreeBSD, Inc. Date: Tue, 30 Oct 2007 01:38:39 -0400 Message-Id: <1193722720.92189.47.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 FreeBSD GNOME Team Port X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on creme-brulee.marcuscom.com Cc: current@FreeBSD.org Subject: Re: Constant stream of errors on msk0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 05:38:34 -0000 --=-ymvVIE3XIfmGHmDfSXla Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2007-10-30 at 10:58 +0900, Pyun YongHyeon wrote: > On Tue, Feb 20, 2007 at 01:40:37PM -0500, Joe Marcus Clarke wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > >=20 > > Pyun YongHyeon wrote: > >=20 > > >=20 > > > Does the other GigE work without issues on Cisco 6500? > >=20 > > I haven't tried this card on another gigE switch. However, the same > > switch port on the same switch did not exhibit these problems with the > > myk driver under 6.X. At least as far as I know my desk port was not > > moved in the IDF. > >=20 > > >=20 > > > The msk(4) can have a bug with autonegotiation but I've never seen > > > negotiation mismatches on msk(4). Whilst writing the driver I've > > > checked speed/link negotiation against gigabit switch and directly > > > connected GigE and I found nothing unusual. Of course, that does > > > not necessarily mean msk(4) is perfect for link negotiation. > > >=20 > > > Because you've said myk(4) works well on Cisco 6500 I have to > > > diagnose the issue. When setting the link manually on gigabit > > > environments, nomally one side should be master and the other the > > > slave so how about forcing master bit on msk(4) side? > > >=20 > > > #ifconfig msk0 media 1000baseTX mediaopt full-duplex link0 > > > ^^^^^ > >=20 > > This does not help. I tried 1000BaseTX/full, 100BaseTX/full, and > > 100BaseTX/half. All three exhibited the same problem with constantly > > incrementing input errors. > >=20 > Hi, >=20 > Are you still interesting in fixing autonegotiation issue on msk(4) > at 1000bps? > If so please try attached patch and let me know result. Of course I'd be interested, but since the initial posting, I've moved to a Catalyst 2950 switch, and I have not seen any autoneg problems with my msk and that switch. I would not be able to adequately test this patch. Thanks for the follow through, though. Joe --=20 Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome --=-ymvVIE3XIfmGHmDfSXla Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBHJsNeb2iPiv4Uz4cRAommAJ9N1NmFH927p0joXm8Aj4Fm7AxHuQCfUbnd +169NgP5YkCO9rBFRG1VV5c= =yhEv -----END PGP SIGNATURE----- --=-ymvVIE3XIfmGHmDfSXla-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 05:51:01 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8218B16A421 for ; Tue, 30 Oct 2007 05:51:01 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.187]) by mx1.freebsd.org (Postfix) with ESMTP id 4C44413C4B3 for ; Tue, 30 Oct 2007 05:51:01 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so1568923rvb for ; Mon, 29 Oct 2007 22:50:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; 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=YApoPS4rzFLSel42bpOt2l1hGAnYD2IG3VVizdQS+Kk=; b=Efg/9b1GDHdDx4xYHgoRQ77NoZKBGRXMSP4+MU2K4Yk/oh+fnCBKvmA65k61vFHyEa0aZGOvgMl84Q1AWWuEpYYFDJWM9ibUKZIiEkiMqzIB6YBMaZsS8o1LzHADpjXcK+igcgFCkLz+msDJZ7EjUWGcu/2N/UbUbHR7ZaoDVa8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=hpZpUmlarT7kCeRM03sTMhPx8S2lOrSZw0/DPKqFmyD+cmqh8zaL6mnMu8/W8mKoVWNbw3r/xiv5UMbpdiU26owSONWTYeFa+KFOMxWmGEUQ505c97+d80dSFiwyDzP60xEgQlgRSKdDzBx5PJUlX0wy2CMKc4sCuAHaRvBmp1U= Received: by 10.114.124.1 with SMTP id w1mr2607192wac.1193723449114; Mon, 29 Oct 2007 22:50:49 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id m27sm14798562wag.2007.10.29.22.50.45 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 29 Oct 2007 22:50:47 -0700 (PDT) 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 l9U5ofBF039144 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Oct 2007 14:50:41 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l9U5ofiD039143; Tue, 30 Oct 2007 14:50:41 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 30 Oct 2007 14:50:41 +0900 From: Pyun YongHyeon To: Joe Marcus Clarke Message-ID: <20071030055041.GB38663@cdnetworks.co.kr> References: <20070213044746.GC62412@cdnetworks.co.kr> <1171344897.98536.14.camel@shumai.marcuscom.com> <20070213054802.GD62412@cdnetworks.co.kr> <45D355D9.5000805@FreeBSD.org> <20070215055918.GA4319@cdnetworks.co.kr> <45D9F303.1030302@FreeBSD.org> <20070220012443.GB912@cdnetworks.co.kr> <45DB40A5.8000406@FreeBSD.org> <20071030015816.GD37693@cdnetworks.co.kr> <1193722720.92189.47.camel@shumai.marcuscom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1193722720.92189.47.camel@shumai.marcuscom.com> User-Agent: Mutt/1.4.2.1i Cc: current@FreeBSD.org Subject: Re: Constant stream of errors on msk0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 05:51:01 -0000 On Tue, Oct 30, 2007 at 01:38:39AM -0400, Joe Marcus Clarke wrote: > > On Tue, 2007-10-30 at 10:58 +0900, Pyun YongHyeon wrote: > > On Tue, Feb 20, 2007 at 01:40:37PM -0500, Joe Marcus Clarke wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA1 > > > > > > Pyun YongHyeon wrote: > > > > > > > > > > > Does the other GigE work without issues on Cisco 6500? > > > > > > I haven't tried this card on another gigE switch. However, the same > > > switch port on the same switch did not exhibit these problems with the > > > myk driver under 6.X. At least as far as I know my desk port was not > > > moved in the IDF. > > > > > > > > > > > The msk(4) can have a bug with autonegotiation but I've never seen > > > > negotiation mismatches on msk(4). Whilst writing the driver I've > > > > checked speed/link negotiation against gigabit switch and directly > > > > connected GigE and I found nothing unusual. Of course, that does > > > > not necessarily mean msk(4) is perfect for link negotiation. > > > > > > > > Because you've said myk(4) works well on Cisco 6500 I have to > > > > diagnose the issue. When setting the link manually on gigabit > > > > environments, nomally one side should be master and the other the > > > > slave so how about forcing master bit on msk(4) side? > > > > > > > > #ifconfig msk0 media 1000baseTX mediaopt full-duplex link0 > > > > ^^^^^ > > > > > > This does not help. I tried 1000BaseTX/full, 100BaseTX/full, and > > > 100BaseTX/half. All three exhibited the same problem with constantly > > > incrementing input errors. > > > > > Hi, > > > > Are you still interesting in fixing autonegotiation issue on msk(4) > > at 1000bps? > > If so please try attached patch and let me know result. > > Of course I'd be interested, but since the initial posting, I've moved > to a Catalyst 2950 switch, and I have not seen any autoneg problems with Glad to hear that. :) > my msk and that switch. I would not be able to adequately test this > patch. Thanks for the follow through, though. > Ok, Thanks for quick reply. -- Regards, Pyun YongHyeon From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 05:53:16 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94E0A16A41A; Tue, 30 Oct 2007 05:53:16 +0000 (UTC) (envelope-from tom.hurst@clara.net) Received: from spork.qfe3.net (spork.qfe3.net [212.13.207.101]) by mx1.freebsd.org (Postfix) with ESMTP id 3617A13C4B7; Tue, 30 Oct 2007 05:53:16 +0000 (UTC) (envelope-from tom.hurst@clara.net) Received: from [81.104.144.87] (helo=voi.aagh.net) by spork.qfe3.net with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1ImjRG-000Owx-HQ; Tue, 30 Oct 2007 05:14:54 +0000 Received: from freaky by voi.aagh.net with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1ImjRG-0001Q9-Ae; Tue, 30 Oct 2007 05:14:54 +0000 Date: Tue, 30 Oct 2007 05:14:54 +0000 From: Thomas Hurst To: Jeremy Chadwick Message-ID: <20071030051454.GB76585@voi.aagh.net> Mail-Followup-To: Jeremy Chadwick , Giorgos Keramidas , Andrew Lankford , stable@freebsd.org, current@freebsd.org References: <47240A15.8080305@charter.net> <20071028074248.GA1511@haakonia.hitnet.RWTH-Aachen.DE> <4724BAD9.7000400@charter.net> <20071028164152.GA7516@eos.sc1.parodius.com> <4724BEB3.5080905@charter.net> <20071029132447.GA2658@kobe.laptop> <20071029191836.GA58058@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="XsQoSWH+UP9D9v3l" Content-Disposition: inline In-Reply-To: <20071029191836.GA58058@eos.sc1.parodius.com> Organization: Not much. User-Agent: Mutt/1.5.16 (2007-06-09) Sender: Thomas Hurst Cc: Giorgos Keramidas , Andrew Lankford , stable@freebsd.org, current@freebsd.org Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 05:53:16 -0000 --XsQoSWH+UP9D9v3l Content-Type: text/plain; charset=us-ascii Content-Disposition: inline * Jeremy Chadwick (koitsu@FreeBSD.org) wrote: > There's a periodic script (/etc/periodic/weekly/330.catman) which > rebuilds all the catman pages for you. However, it makes an immense > mess of your weekly system mails due to all the manpage/nroff > formatting mistakes. Have a look: > > http://lists.freebsd.org/pipermail/freebsd-ports/2007-May/040648.html If you want to find what's causing these errors, you could run catman with -v so it prints the filename of what it's processing. Less spammy but still noisy in the event of these warnings would be something like the attached patch, which saves the stderr stream and prints it and the currently processed filename if it's non-empty. Maybe friendlier would be the other patch, which silences nroff unless catman is running verbose. -- Thomas 'Freaky' Hurst http://hur.st/ --XsQoSWH+UP9D9v3l Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="catman-detect-warnings.diff" --- catman.c.orig 2007-10-30 04:43:52.000000000 +0000 +++ catman.c 2007-10-30 04:45:35.000000000 +0000 @@ -403,6 +403,10 @@ dev_t src_dev; ino_t src_ino; const char *link_name; + struct stat err_st; + char err_file[MAXPATHLEN]; + int err_fd; + char err_buf[1024]; src_test = test_path(src, &src_mtime); if (!(src_test & (TEST_FILE|TEST_READABLE))) { @@ -447,13 +451,33 @@ } snprintf(tmp_file, sizeof tmp_file, "%s.tmp", cat); snprintf(cmd, sizeof cmd, - "%scat %s | tbl | nroff -T%s -man | col | %s > %s.tmp", + "%scat %s | tbl | nroff -T%s -man 2>%s.err | col | %s > %s.tmp", zipped == BZIP ? BZ2CAT_CMD : zipped == GZIP ? GZCAT_CMD : "", - src, nroff_device, + src, nroff_device, cat, zipped == BZIP ? BZ2_CMD : zipped == GZIP ? GZ_CMD : "cat", cat); if (system(cmd) != 0) err(1, "formatting pipeline"); + + snprintf(err_file, sizeof err_file, "%s.err", cat); + if (stat(err_file, &err_st) < 0) + warn("%s", err_file); + else if (err_st.st_size > 0) + { + fprintf(stderr, "nroff formatting errors in %s:\n", src); + if ((err_fd = open(err_file, O_RDONLY)) < 0) + warn("%s", err_file); + else + { + while (read(err_fd, &err_buf, sizeof err_buf) > 0) + fprintf(stderr, "%s", err_buf); + + close(err_fd); + } + } + if (unlink(err_file) < 0) + warn("%s", err_file); + if (rename(tmp_file, cat) < 0) warn("%s", cat); tmp_file[0] = '\0'; --XsQoSWH+UP9D9v3l Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="catman-quiet.diff" --- catman.c 2007-10-30 05:05:04.000000000 +0000 +++ catman.c.orig 2007-10-30 04:43:52.000000000 +0000 @@ -447,9 +447,9 @@ } snprintf(tmp_file, sizeof tmp_file, "%s.tmp", cat); snprintf(cmd, sizeof cmd, - "%scat %s | tbl | nroff -T%s -man %s| col | %s > %s.tmp", + "%scat %s | tbl | nroff -T%s -man | col | %s > %s.tmp", zipped == BZIP ? BZ2CAT_CMD : zipped == GZIP ? GZCAT_CMD : "", - src, nroff_device, verbose ? "" : "2>/dev/null", + src, nroff_device, zipped == BZIP ? BZ2_CMD : zipped == GZIP ? GZ_CMD : "cat", cat); if (system(cmd) != 0) --XsQoSWH+UP9D9v3l-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 07:06:33 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C77F16A419 for ; Tue, 30 Oct 2007 07:06:33 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with SMTP id AB0A113C4AC for ; Tue, 30 Oct 2007 07:06:32 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 8610 invoked by uid 399); 30 Oct 2007 06:06:09 -0000 Received: from localhost (HELO slave.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 30 Oct 2007 06:06:09 -0000 X-Originating-IP: 127.0.0.1 Date: Mon, 29 Oct 2007 23:06:07 -0700 (PDT) From: Doug Barton To: Andrew Lankford In-Reply-To: <4724BEB3.5080905@charter.net> Message-ID: References: <47240A15.8080305@charter.net> <20071028074248.GA1511@haakonia.hitnet.RWTH-Aachen.DE> <4724BAD9.7000400@charter.net> <20071028164152.GA7516@eos.sc1.parodius.com> <4724BEB3.5080905@charter.net> X-message-flag: Outlook -- Not just for spreading viruses anymore! X-OpenPGP-Key-ID: 0xD5B2F0FB Organization: http://www.FreeBSD.org/ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: stable@freebsd.org, current@freebsd.org Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 07:06:33 -0000 On Sun, 28 Oct 2007, Andrew Lankford wrote: > Thbbt! I'm reading the catman version of MAKEDEV. I'll try posting this one more time. :) Before you installworld, just do 'rm -r /usr/share/man/' and you won't ever have that problem. Doug -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 07:12:28 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5791416A41A for ; Tue, 30 Oct 2007 07:12:28 +0000 (UTC) (envelope-from lx@redundancy.redundancy.org) Received: from redundancy.redundancy.org (redundancy.redundancy.org [64.147.160.152]) by mx1.freebsd.org (Postfix) with SMTP id 29A3513C4BC for ; Tue, 30 Oct 2007 07:12:28 +0000 (UTC) (envelope-from lx@redundancy.redundancy.org) Received: (qmail 90352 invoked by uid 1001); 30 Oct 2007 06:45:59 -0000 Date: Mon, 29 Oct 2007 23:45:59 -0700 From: "David E. Thiel" To: freebsd-current@freebsd.org Message-ID: <20071030064559.GL82157@redundancy.redundancy.org> Mail-Followup-To: freebsd-current@freebsd.org References: <4726561D.7090805@cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4726561D.7090805@cisco.com> X-OpenPGP-Key-fingerprint: 482A 8C46 C844 7E7C 8CBC 2313 96EE BEE5 1F4B CA13 X-Face: %H~{$1~NOw1y#%mM6{|4:/ List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 07:12:28 -0000 On Mon, Oct 29, 2007 at 05:52:29PM -0400, Randall Stewart wrote: > Anyone looked at porting SMF to FreeBSD? Not to my knowledge. What do you feel that SMF offers that currently existing systems like rcNG or daemontools/runit do not? I haven't found SMF to be more useful or functional than those solutions, and it's certainly not as easy to use. From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 08:28:02 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA80C16A41A for ; Tue, 30 Oct 2007 08:28:02 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: from abbe.salford.ac.uk (abbe.salford.ac.uk [146.87.0.10]) by mx1.freebsd.org (Postfix) with SMTP id C80E413C4B5 for ; Tue, 30 Oct 2007 08:28:01 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 74568 invoked by uid 98); 30 Oct 2007 08:27:46 +0000 Received: from 146.87.255.121 by abbe.salford.ac.uk (envelope-from , uid 401) with qmail-scanner-2.01 (clamdscan: 0.90/3838. spamassassin: 3.1.8. Clear:RC:1(146.87.255.121):. Processed in 0.042846 secs); 30 Oct 2007 08:27:46 -0000 Received: from rust.salford.ac.uk (HELO rust.salford.ac.uk) (146.87.255.121) by abbe.salford.ac.uk (qpsmtpd/0.3x.614) with SMTP; Tue, 30 Oct 2007 08:27:46 +0000 Received: (qmail 31954 invoked by uid 1002); 30 Oct 2007 08:27:44 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 30 Oct 2007 08:27:44 -0000 Date: Tue, 30 Oct 2007 08:27:44 +0000 (GMT) From: "Mark Powell" To: Nathan Butcher In-Reply-To: <4725558F.6040702@fusiongol.com> Message-ID: <20071030081201.O26335@rust.salford.ac.uk> References: <4725558F.6040702@fusiongol.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: Problem with ATAPI device on JMicron JMB363 on 7.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 08:28:02 -0000 On Mon, 29 Oct 2007, Nathan Butcher wrote: >> Hi, >> I've tried to install FreeBSD 7.0-BETA1/amd64 on Gigabyte P35-S3 mb >with >> PATA DVD-RW drive attached to JMicron JMB363 controller. > > The JMicron JMB363 controller is *still* broken. I think the ATA maintainer has been busy recently. However, he was on the list with a correcting patch within a day, after I reported my last DMA problem. > I have a Gigabyte GA-G33-DS3R. FreeBSD 7.0-BETA1 detects the chipset, > but no devices attached to the SATA controllers find their relative /dev > entries. My SATA DVD-combo drive simply doesn't get /dev/acd0, and as a > result I cannot access the drive. I've tried hard drives too, with the > same results. I've a Gigabyte GA-P35-DS4 running 7.0-BETA and I'm using all 8 SATA ports; 6xICH9 (AHCI mode), 2xJMB363 (IDE mode). Plus a PATA DVDROM drive on the JMB363's IDE port. SATA DVD drives are a problem though. On an Intel 975 board I've also tried which has 4xICH8 and a Marvell controller with 2xSATA, the SATA DVD drive was never detected on the Marvell. On the ICH8 in AHCI mode, I was informed by the kernel that SATA DVD drives are not yet supported. So putting the ICH8 into IDE mode made everything work, except the hard drives working in SATAI mode instead of SATAII, which they previously did when it was in AHCI mode. Have you tried putting the SATA DVD drive on ICH9 but changing the controller's mode to IDE, and just keeping the JMB363 for hard drives? All this has been the case since I first started using 7 in August. > The IDE interface seems to work for me (I have an IDE -> CF converter in > there), but I don't have a PATA optical drive to test. As I noted above, a PATA DVD drive works fine on the JMB363 PATA port. Cheers. -- Mark Powell - UNIX System Administrator - The University of Salford Information Services Division, Clifford Whitworth Building, Salford University, Manchester, M5 4WT, UK. Tel: +44 161 295 4837 Fax: +44 161 295 5888 www.pgp.com for PGP key From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 05:47:14 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9904816A41B for ; Tue, 30 Oct 2007 05:47:14 +0000 (UTC) (envelope-from brian.mcginty@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.190]) by mx1.freebsd.org (Postfix) with ESMTP id 67B4413C4A5 for ; Tue, 30 Oct 2007 05:47:14 +0000 (UTC) (envelope-from brian.mcginty@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so1568302rvb for ; Mon, 29 Oct 2007 22:47:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=SAnUVJMWgRnU6m1tXNelvKWQajkPkBfykmL8iBJPs/Q=; b=C4YfMda2Mc3tdCms/oPsGx4NRN5Q+xzLKPVKEINDjaHkktHzXqqSWz4LdCyb+8xJuqdGWrS0biYujm4yjSELE003otTYdbGaPuoD07G9nCTqTGKNGF9vk/Ad1vW4rWk4sFGnsOjteNP6RoEx5Pr0lN6gxfhVKtpv/MlLEw65eAw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Xtp192lRLw2PaXUIChlNHGyDLteyHAE0piLbwjenCxDQA57xv9cgs76NpcjyD2Hl4A4rtA6dmUc54dOaTIyLZPzcqVIy4nU/9vyqSVyOYNRRi+s9erPlQl7e6/K/tUi2cFVvxHBbM60jc9mDM8pNXQ83mBZJsUKZ8nIT/RXHqGY= Received: by 10.142.171.6 with SMTP id t6mr1566603wfe.1193721711258; Mon, 29 Oct 2007 22:21:51 -0700 (PDT) Received: by 10.142.163.17 with HTTP; Mon, 29 Oct 2007 22:21:51 -0700 (PDT) Message-ID: <601bffc40710292221k35a6927fh9dfaa217ae68e416@mail.gmail.com> Date: Mon, 29 Oct 2007 22:21:51 -0700 From: "Brian McGinty" To: "Jack Vogel" In-Reply-To: <2a41acea0710291045m6f1d2acw78c26a455ea3894d@mail.gmail.com> MIME-Version: 1.0 References: <2a41acea0710291045m6f1d2acw78c26a455ea3894d@mail.gmail.com> X-Mailman-Approved-At: Tue, 30 Oct 2007 13:30:11 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List Subject: Re: RFC: Evolution of the em driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 05:47:14 -0000 I prefer (2) - non-intrusive on em, and the new one doesn't have to deal with legacy or backward compatibility with em. Any commonality with ixgbe? Later Brian. On 10/29/07, Jack Vogel wrote: > > I have an important decision to make and I thought rather than just make > it and spring it on you I'd present the issues and see what opinions were. > > Our newer hardware uses new features that, more and more, require > parallel code paths in the driver. For instance, the 82575 (Zoar) uses > what are called 'advanced descriptors', this means different TX path. > The 7.0 em driver has this support in it, it just uses a function pointer > to handle it. > > When I add in multiqueue/RSS support it will add even more code > that functions this way. > > What the Linux team did was to split the newer code into a standalone > driver, they call it 'igb'. I had originally resisted doing this, but with > the development I have been working on the past month I am starting > to wonder if it might not be best to follow them. > > I see 3 possibilities and I'd like feedback, which would you prefer if > you have a preference and why. > > First, keep the driver as is and just live with multiple code paths > and features, possibly #ifdef'ed as they appear. > > Second, split the driver as Linux has into em and igb. The added > question then is how to split it, Linux made the line the use of > advanced descriptors, so Zoar and after, but I could also see a > case for having everything PCI-E/MSI capable being in the new > driver. > > Third, sort of a half-way approach, split up code but not the > driver, in other words offer different source files that can be > compiled into the driver, so you could have the one big jumbo > driver with all in there, or one that will only work with a subset > of adapters. This one would probably be the most work, because > its a new approach. > > Cheers, > > Jack > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 07:20:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B0F416A421 for ; Tue, 30 Oct 2007 07:20:18 +0000 (UTC) (envelope-from blacknova@tut.by) Received: from speedy.tutby.com (mail.tut.by [195.137.160.40]) by mx1.freebsd.org (Postfix) with ESMTP id EC50813C48D for ; Tue, 30 Oct 2007 07:20:17 +0000 (UTC) (envelope-from blacknova@tut.by) Received: from [91.149.132.24] (account blacknova@tut.by HELO [192.168.1.2]) by speedy.tutby.com (CommuniGate Pro SMTP 5.1.12) with ESMTPA id 421182173 for freebsd-current@freebsd.org; Tue, 30 Oct 2007 09:19:53 +0200 Message-ID: <4726DA71.2050000@tut.by> Date: Tue, 30 Oct 2007 09:17:05 +0200 From: =?KOI8-R?Q?=F7=CC=C1=C4=C9=CD=C9=D2_=EE=CF=D7=CF=D3=C5=CC=D8=C3=C5?= =?KOI8-R?Q?=D7?= User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <4725558F.6040702@fusiongol.com> <4726BEEE.3070704@yandex.ru> In-Reply-To: <4726BEEE.3070704@yandex.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Tue, 30 Oct 2007 14:48:17 +0000 Subject: Re: Problem with ATAPI device on JMicron JMB363 on 7.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 07:20:18 -0000 Hi, thanks for info. WBR, Vladimir Novoseltsev Andrey V. Elsukov ÐÉÛÅÔ: > Nathan Butcher wrote: >> I have a Gigabyte GA-G33-DS3R. FreeBSD 7.0-BETA1 detects the chipset, >> but no devices attached to the SATA controllers find their relative /dev >> entries. My SATA DVD-combo drive simply doesn't get /dev/acd0, and as a >> result I cannot access the drive. I've tried hard drives too, with the >> same results. > > You can update your BETA1 to the fresh RELENG_7. Soren have fixed this > issue. Also, ATAPI support was added to the AHCI driver (only for > CURRENT yet). > >> The IDE interface seems to work for me (I have an IDE -> CF converter in >> there), but I don't have a PATA optical drive to test. > > For Vladimir: > here is a description for your issue (russian) > http://unix1.jinr.ru/~lavr/cd_dvd_intel965.html > From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 09:37:44 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07B9A16A468 for ; Tue, 30 Oct 2007 09:37:44 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: from abbe.salford.ac.uk (abbe.salford.ac.uk [146.87.0.10]) by mx1.freebsd.org (Postfix) with SMTP id 5A2DF13C465 for ; Tue, 30 Oct 2007 09:37:43 +0000 (UTC) (envelope-from M.S.Powell@salford.ac.uk) Received: (qmail 30695 invoked by uid 98); 30 Oct 2007 09:37:26 +0000 Received: from 146.87.255.121 by abbe.salford.ac.uk (envelope-from , uid 401) with qmail-scanner-2.01 (clamdscan: 0.90/3838. spamassassin: 3.1.8. Clear:RC:1(146.87.255.121):. Processed in 0.046877 secs); 30 Oct 2007 09:37:26 -0000 Received: from rust.salford.ac.uk (HELO rust.salford.ac.uk) (146.87.255.121) by abbe.salford.ac.uk (qpsmtpd/0.3x.614) with SMTP; Tue, 30 Oct 2007 09:37:26 +0000 Received: (qmail 32624 invoked by uid 1002); 30 Oct 2007 09:37:23 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 30 Oct 2007 09:37:23 -0000 Date: Tue, 30 Oct 2007 09:37:23 +0000 (GMT) From: "Mark Powell" To: Jeremy Chadwick In-Reply-To: <20071030015534.GA69514@eos.sc1.parodius.com> Message-ID: <20071030093229.O32304@rust.salford.ac.uk> References: <20071029092531.J99722@rust.salford.ac.uk> <20071030015534.GA69514@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: WRITE_DMA48 error causing loss of ZFS array X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 09:37:44 -0000 On Mon, 29 Oct 2007, Jeremy Chadwick wrote: > On Mon, Oct 29, 2007 at 09:59:11AM +0000, Mark Powell wrote: >> I've experienced several dma errors over the past few months with various >> incarnations of 7.0 which were all fixed. > > This could be relevant: > > http://kerneltrap.org/mailarchive/freebsd-current/2007/10/2/326931 Yes, thanks. Last time I mentioned this, des@des.no also said then it was a well known ATA bug, for which I should look in the archives. However, as I said, it's hard to pinpoint from searching the -current archives, quite which bug he is talking about. Does anyone have a link to a post which goes into greater detail about this problem? I'd like to post a PR regarding this, but would like to read these previous posts to get a little more info. Cheers. -- Mark Powell - UNIX System Administrator - The University of Salford Information Services Division, Clifford Whitworth Building, Salford University, Manchester, M5 4WT, UK. Tel: +44 161 295 4837 Fax: +44 161 295 5888 www.pgp.com for PGP key From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 10:17:27 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6086616A419 for ; Tue, 30 Oct 2007 10:17:27 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.184]) by mx1.freebsd.org (Postfix) with ESMTP id A164613C48D for ; Tue, 30 Oct 2007 10:17:26 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: by mu-out-0910.google.com with SMTP id w9so2319216mue for ; Tue, 30 Oct 2007 03:17:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; bh=UgnyFrT6jKn80SJ8eA/SPS1i1l6VdL+9pO3srxUDMdY=; b=nZFdSB/vvLSwpyP5E+vfyvcmDNnVvBKp+FGzlls2HGtMVxhixUmw2z31oJvxroPTiTC6E7NpzadMiuUF7Maid1ywFjrNZ5icZA8UD+RAT7xneMujs0O537V9jkOfdwfcY/92+5y/h86wfepOMCHkYrk7OuHo4OyxduvwS+3SEpk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; b=ZVylsWbnzu/V+JnntfZWLlwEbKylH17XtwJ9pGtT6XGIQbzsKEuYIh2xyzipBSiG0L7GpD84clfFHHEqybALkleBTzmPV75MUsZ5aIf7dZw9Xsly+xxz/i7UPp+NgPPVY9t5fmxPKa7ylIAngB6BowYYxgOUbvrfDy3D0wXNJe8= Received: by 10.82.156.12 with SMTP id d12mr13441262bue.1193737932642; Tue, 30 Oct 2007 02:52:12 -0700 (PDT) Received: from orion ( [89.162.141.1]) by mx.google.com with ESMTPS id g17sm7671356nfd.2007.10.30.02.52.09 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 30 Oct 2007 02:52:10 -0700 (PDT) From: Nikolay Pavlov To: freebsd-current@freebsd.org Date: Tue, 30 Oct 2007 11:51:59 +0200 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) References: <20070917194009.W84177@woozle.rinet.ru> <200709241223.52140.qpadla@gmail.com> <472561A7.60108@delphij.net> In-Reply-To: <472561A7.60108@delphij.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1390612.r2P8YyxfFY"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200710301152.06525.qpadla@gmail.com> Cc: delphij@freebsd.org, Dmitry Morozovsky Subject: acquiring duplicate lock of same type: "sleepq chain" [was: tmpfs on contemporary -current: panic: locked against myself] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: qpadla@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 10:17:27 -0000 --nextPart1390612.r2P8YyxfFY Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 29 October 2007 06:29:27 LI Xin wrote: > Can not reproduce here. =C2=A0Could you please confirm that this still > persists for latest RELENG_7? Well i am not able to reproduce it on my VMware box. However i'll try to do= =20 it later on my real box. I have another interesting report regarding RELENG_7. I don't know is this= =20 a bug or not, but... While testing tmpfs with postmark with a lot of=20 swapping on purpose i have got this panic: root@orion-vm:~# kgdb -q -n 0 /boot/kernel/kernel.symbols = = =20 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:= =20 Undefined symbol "ps_pglobal_lookup"] Unread portion of the kernel message buffer: acquiring duplicate lock of same type: "sleepq chain" 1st sleepq chain @ /usr/src/sys/kern/subr_sleepqueue.c:781 2nd sleepq chain @ /usr/src/sys/vm/vm_glue.c:770 KDB: stack backtrace: db_trace_self_wrapper(c0a9d415,cbd43be4,c078584e,c0a9f7cf,c0a9e2be,...) at= =20 db_trace_self_wrapper+0x26 kdb_backtrace(c0a9f7cf,c0a9e2be,c0abbe42,302,cbd43bd0,...) at=20 kdb_backtrace+0x29 witness_checkorder(c0bb4db0,9,c0abbe42,302,9,...) at=20 witness_checkorder+0x6de _thread_lock_flags(c0bae590,0,c0abbe42,302,cbd43c44,...) at=20 _thread_lock_flags+0x47 kick_proc0(c0bb4bb8,1,c0a9b2c7,1d3,c2c7f000,...) at kick_proc0+0x2a setrunnable(c2c7f000,1,c0a9e012,26b) at setrunnable+0xbb sleepq_resume_thread(c0bb0384,0,c0a9e012,30d,e40e5,...) at=20 sleepq_resume_thread+0x259 sleepq_timeout(c2c7f000,0,c0a9bb75,ef,0,...) at sleepq_timeout+0xc0 softclock(0,0,c0a97551,471,c292a6e4,...) at softclock+0x266 ithread_loop(c290a270,cbd43d38,c0a972c5,314,c290b550,...) at=20 ithread_loop+0x1b5 fork_exit(c0732ad0,c290a270,cbd43d38) at fork_exit+0xb8 fork_trampoline() at fork_trampoline+0x8 =2D-- trap 0, eip =3D 0, esp =3D 0xcbd43d70, ebp =3D 0 --- KDB: enter: witness_checkorder panic: from debugger cpuid =3D 0 KDB: stack backtrace: Uptime: 15m52s Physical memory: 243 MB Dumping 79 MB: 64 48 32 16 #0 doadump () at pcpu.h:195 195 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:195 #1 0xc074e0ce in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:4= 09 #2 0xc074e38b in panic (fmt=3DVariable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:563 #3 0xc048cc27 in db_panic (addr=3DCould not find the frame base=20 for "db_panic". ) at /usr/src/sys/ddb/db_command.c:433 #4 0xc048d615 in db_command_loop () at /usr/src/sys/ddb/db_command.c:401 #5 0xc048ed85 in db_trap (type=3D3, code=3D0)=20 at /usr/src/sys/ddb/db_main.c:222 #6 0xc0775026 in kdb_trap (type=3D3, code=3D0, tf=3D0xcbd43b54)=20 at /usr/src/sys/kern/subr_kdb.c:502 #7 0xc0a0407b in trap (frame=3D0xcbd43b54)=20 at /usr/src/sys/i386/i386/trap.c:621 #8 0xc09e9a6b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #9 0xc07751a2 in kdb_enter (msg=3D0xc0a378b0 "witness_checkorder") at=20 cpufunc.h:60 #10 0xc0785863 in witness_checkorder (lock=3D0xc0bb4db0, flags=3D9,=20 file=3D0xc0abbe42 "/usr/src/sys/vm/vm_glue.c", line=3D770)=20 at /usr/src/sys/kern/subr_witness.c:1124 #11 0xc0743227 in _thread_lock_flags (td=3D0xc0bae590, opts=3D0,=20 file=3D0xc0abbe42 "/usr/src/sys/vm/vm_glue.c", line=3D770)=20 at /usr/src/sys/kern/kern_mutex.c:486 #12 0xc095789a in kick_proc0 () at /usr/src/sys/vm/vm_glue.c:770 #13 0xc075633b in setrunnable (td=3D0xc2c7f000)=20 at /usr/src/sys/kern/kern_synch.c:496 #14 0xc077c589 in sleepq_resume_thread (sq=3D0xc28fd150, td=3D0xc2c7f000,=20 pri=3D-1) at /usr/src/sys/kern/subr_sleepqueue.c:660 #15 0xc077c7b0 in sleepq_timeout (arg=3D0xc2c7f000)=20 at /usr/src/sys/kern/subr_sleepqueue.c:789 #16 0xc075fe36 in softclock (dummy=3D0x0)=20 at /usr/src/sys/kern/kern_timeout.c:274 #17 0xc0732c85 in ithread_loop (arg=3D0xc290a270)=20 at /usr/src/sys/kern/kern_intr.c:1036 #18 0xc0730148 in fork_exit (callout=3D0xc0732ad0 ,=20 arg=3D0xc290a270, frame=3D0xcbd43d38) at /usr/src/sys/kern/kern_fork.c:796 #19 0xc09e9ae0 in fork_trampoline ()=20 at /usr/src/sys/i386/i386/exception.s:205 But I should mention that before the panic there was a lot of=20 "swap zone exhausted, increase kern.maxswzone" messages, so i don't know=20 whether this is a disired behavior or not. In my fstab i have this line: tmpfs /tmp tmpfs rw 0 0 =20 root@orion-vm:~# uname -a =46reeBSD orion-vm 7.0-BETA1 FreeBSD 7.0-BETA1 #0: Mon Oct 29 11:12:58 UTC= =20 2007 root@orion-vm:/usr/obj/usr/src/sys/DEBUG i386 postmark configuration is: The base number of files is 50000 Transactions: 10000 =46iles range between 500 bytes and 9.77 kilobytes in size Working directory: /usr/home/quetzal 1000 subdirectories will be used Block sizes are: read=3D512 bytes, write=3D512 bytes Biases are: read/append=3D5, create/delete=3D5 Using Unix buffered file I/O Random number generator seed is 42 Report format is verbose. root@orion-vm:~# swapinfo = = =20 Device 512-blocks Used Avail Capacity /dev/ad0s1b 1048576 0 1048576 0% hw.physmem: 255221760 hw.usermem: 212406272 hw.realmem: 268435456 =2D-=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 =2D Best regards, Nikolay Pavlov. <<<----------------------------------- = =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 --nextPart1390612.r2P8YyxfFY Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBHJv7G/2R6KvEYGaIRAo8sAKCPp/KOIJg6iixtXt0QN0yNSaR9MACeLlX8 sNum6tYAbG/GwZ40BpQKCPE= =ezNt -----END PGP SIGNATURE----- --nextPart1390612.r2P8YyxfFY-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 10:25:48 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 13B8B16A417 for ; Tue, 30 Oct 2007 10:25:48 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.freebsd.org (Postfix) with ESMTP id 91E4213C48A for ; Tue, 30 Oct 2007 10:25:47 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: by ug-out-1314.google.com with SMTP id y2so87360uge for ; Tue, 30 Oct 2007 03:25:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; bh=GpbpT35VS/jsTQCHeCD8x/sVRVL0sbxhXg6YPIQB0B4=; b=GYG7DuVdKfx6M4+JJoPvjc2KqtEmueqjIgA8J4+L32nVSOCdP5jyZafAA6pMQNZ/BK/LrdW2Wyp6sooFEzQpBeOryKkrtJUxzUhSgAG3nAfS37yesaUEN6GnzYKsT21QJuuLLvrbAsPPnc2OxE4n3aC1q5kWHjKF9A5EWiuGVyE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; b=QaASeqewh4yPnOdQclSb4j25uX7Q4gIVl1Rk3QLPvCJtVOqP5v8EYZSfFxobLpxoOQUpLpVXagJcYoooVgzyKm+dMIdcO466HaLPZMDTfXF0fZIdzjV78ZPWzbp8aIPUykIuawaJCrJEQFk34QlXBUnf+f6H4jCHN9o40VdW/Kk= Received: by 10.66.243.4 with SMTP id q4mr659744ugh.1193738209552; Tue, 30 Oct 2007 02:56:49 -0700 (PDT) Received: from orion ( [89.162.141.1]) by mx.google.com with ESMTPS id j1sm1114212ugf.2007.10.30.02.56.46 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 30 Oct 2007 02:56:47 -0700 (PDT) From: Nikolay Pavlov To: freebsd-current@freebsd.org Date: Tue, 30 Oct 2007 11:56:43 +0200 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) References: <20070917194009.W84177@woozle.rinet.ru> <472561A7.60108@delphij.net> <200710301152.06525.qpadla@gmail.com> In-Reply-To: <200710301152.06525.qpadla@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1920411.T4tRuytDdO"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200710301156.44164.qpadla@gmail.com> Cc: delphij@freebsd.org, Dmitry Morozovsky Subject: Re: acquiring duplicate lock of same type: "sleepq chain" [was: tmpfs on contemporary -current: panic: locked against myself] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: qpadla@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 10:25:48 -0000 --nextPart1920411.T4tRuytDdO Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 30 October 2007 11:51:59 Nikolay Pavlov wrote: > postmark configuration is: > The base number of files is 50000 > Transactions: 10000 > Files range between 500 bytes and 9.77 kilobytes in size > Working directory: /usr/home/quetzal ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Of course the original test was in /tmp directory > 1000 subdirectories will be used > Block sizes are: read=3D512 bytes, write=3D512 bytes > Biases are: read/append=3D5, create/delete=3D5 > Using Unix buffered file I/O > Random number generator seed is 42 > Report format is verbose. =2D-=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 =2D Best regards, Nikolay Pavlov. <<<----------------------------------- = =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 --nextPart1920411.T4tRuytDdO Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBHJv/c/2R6KvEYGaIRApILAKCfp0pibhaGr0FhoSwVoCI8Lups8ACgl5AQ iI4SB7twaBMEfk47GR8c0DI= =VOyu -----END PGP SIGNATURE----- --nextPart1920411.T4tRuytDdO-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 10:30:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 23F3016A46E for ; Tue, 30 Oct 2007 10:30:18 +0000 (UTC) (envelope-from christoph.friedrichs@helinet.de) Received: from smtp.helinet.de (mail.helidom.de [212.37.47.67]) by mx1.freebsd.org (Postfix) with ESMTP id D4C5813C4C3 for ; Tue, 30 Oct 2007 10:30:17 +0000 (UTC) (envelope-from christoph.friedrichs@helinet.de) Received: from localhost ([127.0.0.1]) by smtp.helinet.de with esmtp (Exim 4.67) (envelope-from ) id 1Imnzg-0006nc-Ge for freebsd-current@freebsd.org; Tue, 30 Oct 2007 11:06:46 +0100 Received: from smtp.helinet.de by schix.dmz.ad01.helidom.de with ESMTP; Tue, 30 Oct 2007 11:06:43 +0100 X-CMM-CAPTURED: false X-CMM-VERSION: 3.1.0 stable #200707102 Received: from [10.40.100.254] (helo=webmail.helinet.de) by smtp.helinet.de with esmtp (Exim 4.67) (envelope-from ) id 1Imnze-0006nQ-2F for freebsd-current@freebsd.org; Tue, 30 Oct 2007 11:06:43 +0100 Received: from [192.168.99.167] (unknown [192.168.99.167]) by webmail.helinet.de (Postfix) with ESMTP id B33C4268D5C for ; Tue, 30 Oct 2007 11:07:07 +0100 (CET) Message-ID: <47270246.4020400@helinet.de> Date: Tue, 30 Oct 2007 11:07:02 +0100 From: Christoph Friedrichs User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Problem with libthr after update X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 10:30:18 -0000 Hi Guys, I?m relatively new with my freebsd -current box and actual experiencing problems with starting kdm and portupgrade. Everytime I do so the kdm-bin log explodes with this error messages: Fatal error 'Cannot allocate red zone for initial thread' at line 382 in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) Fatal error 'Cannot allocate red zone for initial thread' at line 382 in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) Fatal error 'Cannot allocate red zone for initial thread' at line 382 in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) I googled this problem and found something concering some ruby packages. I did a manual rebuild of ruby-1.8.6_2,1 perl-5.8.8 ruby18-bdb-0.6.2 db41-4.1.25_4 portupgrade-2.3.1,2 With this rebuild problems with portupgrade were solved but kdm keeps refusing to start with same error messages. In UPDATING I found this: 20071009: Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and WITHOUT_LIBTHR are set. Does this probably have something to do with this? Any help will be highly apreciated, many greetings from Germany Christoph Friedrichs From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 11:33:41 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2247616A417; Tue, 30 Oct 2007 11:33:41 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id 8111F13C4AA; Tue, 30 Oct 2007 11:33:40 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (vader.bytemobile-rio.ondsl.gr [83.235.57.37]) (authenticated bits=128) by igloo.linux.gr (8.14.1/8.14.1/Debian-9) with ESMTP id l9UBXDaV023877 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Oct 2007 13:33:22 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.1/8.14.1) with ESMTP id l9UBWnYD011198; Tue, 30 Oct 2007 13:33:06 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by kobe.laptop (8.14.1/8.14.1/Submit) id l9UBWlKO010957; Tue, 30 Oct 2007 13:32:47 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Tue, 30 Oct 2007 13:32:47 +0200 From: Giorgos Keramidas To: Jeremy Chadwick Message-ID: <20071030113247.GA3941@kobe.laptop> References: <47240A15.8080305@charter.net> <20071028074248.GA1511@haakonia.hitnet.RWTH-Aachen.DE> <4724BAD9.7000400@charter.net> <20071028164152.GA7516@eos.sc1.parodius.com> <4724BEB3.5080905@charter.net> <20071029132447.GA2658@kobe.laptop> <20071029191836.GA58058@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071029191836.GA58058@eos.sc1.parodius.com> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.989, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.41, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: Andrew Lankford , stable@freebsd.org, current@freebsd.org Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 11:33:41 -0000 On 2007-10-29 12:18, Jeremy Chadwick wrote: > On Mon, Oct 29, 2007 at 03:24:47PM +0200, Giorgos Keramidas wrote: > > On 2007-10-28 12:54, Andrew Lankford wrote: > > > Thbbt! I'm reading the catman version of MAKEDEV. Wish I could > > > disable that "feature". Oh well. I'll delete it all and rebuild it > > > again if needed. Thanks! > > > > Ah, that's it then :) > > > > My usual `installworld' steps include this too: > > > > # cd /usr/share/man > > # find cat[0-9] \! -type d -exec rm {} + > > There's a periodic script (/etc/periodic/weekly/330.catman) which > rebuilds all the catman pages for you. However, it makes an immense > mess of your weekly system mails due to all the manpage/nroff formatting > mistakes. Have a look: > > http://lists.freebsd.org/pipermail/freebsd-ports/2007-May/040648.html Very interesting. Maybe we can tweak 330.catman to display the filename of the manpage which causes each error. Then we could use the periodic script as an aid to start actually *fixing* the errors :) From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 11:47:35 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 90A4216A417; Tue, 30 Oct 2007 11:47:35 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout2.yahoo.com (mrout2.yahoo.com [216.145.54.172]) by mx1.freebsd.org (Postfix) with ESMTP id 2B64E13C4BC; Tue, 30 Oct 2007 11:47:35 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (proxy8.corp.yahoo.com [216.145.48.13]) by mrout2.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id l9UBapuP091549; Tue, 30 Oct 2007 04:36:52 -0700 (PDT) Date: Tue, 30 Oct 2007 20:36:51 +0900 Message-ID: From: gnn@freebsd.org To: "Jack Vogel" In-Reply-To: <2a41acea0710291045m6f1d2acw78c26a455ea3894d@mail.gmail.com> References: <2a41acea0710291045m6f1d2acw78c26a455ea3894d@mail.gmail.com> User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.7 Emacs/22.1 (i386-apple-darwin8.9.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List Subject: Re: RFC: Evolution of the em driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 11:47:35 -0000 At Mon, 29 Oct 2007 10:45:17 -0700, Jack Vogel wrote: > > I have an important decision to make and I thought rather than just make > it and spring it on you I'd present the issues and see what opinions were. > > Our newer hardware uses new features that, more and more, require > parallel code paths in the driver. For instance, the 82575 (Zoar) uses > what are called 'advanced descriptors', this means different TX path. > The 7.0 em driver has this support in it, it just uses a function pointer > to handle it. > > When I add in multiqueue/RSS support it will add even more code > that functions this way. > > What the Linux team did was to split the newer code into a standalone > driver, they call it 'igb'. I had originally resisted doing this, but with > the development I have been working on the past month I am starting > to wonder if it might not be best to follow them. > > I see 3 possibilities and I'd like feedback, which would you prefer if > you have a preference and why. > > First, keep the driver as is and just live with multiple code paths > and features, possibly #ifdef'ed as they appear. > > Second, split the driver as Linux has into em and igb. The added > question then is how to split it, Linux made the line the use of > advanced descriptors, so Zoar and after, but I could also see a > case for having everything PCI-E/MSI capable being in the new > driver. > > Third, sort of a half-way approach, split up code but not the > driver, in other words offer different source files that can be > compiled into the driver, so you could have the one big jumbo > driver with all in there, or one that will only work with a subset > of adapters. This one would probably be the most work, because > its a new approach. As you're the main maintainer it's your choice. Whatever is easiest for you and gives us the most readable code. Best, George From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 12:35:50 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31E0E16A41B; Tue, 30 Oct 2007 12:35:50 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id 8AFBA13C4AC; Tue, 30 Oct 2007 12:35:49 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from kobe.laptop (vader.bytemobile-rio.ondsl.gr [83.235.57.37]) (authenticated bits=128) by igloo.linux.gr (8.14.1/8.14.1/Debian-9) with ESMTP id l9UCGOfw027167 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Oct 2007 14:16:36 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.1/8.14.1) with ESMTP id l9UCG4dA090791; Tue, 30 Oct 2007 14:16:19 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by kobe.laptop (8.14.1/8.14.1/Submit) id l9UCG3Un090790; Tue, 30 Oct 2007 14:16:03 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Tue, 30 Oct 2007 14:16:03 +0200 From: Giorgos Keramidas To: Jeremy Chadwick Message-ID: <20071030121603.GA90748@kobe.laptop> References: <47240A15.8080305@charter.net> <20071028074248.GA1511@haakonia.hitnet.RWTH-Aachen.DE> <4724BAD9.7000400@charter.net> <20071028164152.GA7516@eos.sc1.parodius.com> <4724BEB3.5080905@charter.net> <20071029132447.GA2658@kobe.laptop> <20071029191836.GA58058@eos.sc1.parodius.com> <20071030113247.GA3941@kobe.laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071030113247.GA3941@kobe.laptop> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.117, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.28, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: Andrew Lankford , stable@freebsd.org, current@freebsd.org Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 12:35:50 -0000 On 2007-10-30 13:32, Giorgos Keramidas wrote: >> http://lists.freebsd.org/pipermail/freebsd-ports/2007-May/040648.html > > Very interesting. Maybe we can tweak 330.catman to display the filename > of the manpage which causes each error. Then we could use the periodic > script as an aid to start actually *fixing* the errors :) Neat. The base-system manpages which have errors or warnings are just a few of the hundreds we have. I just finished running a slightly modified version of `/etc/periodic/weekly/330.catman', which uses `catman -v' and the list of files with errors (after a bit of manual parsing) is now: % Reformatting manual pages: % /usr/share/man: not writable - will only be able to write to existing cat directories % man directory /usr/share/man % section man1 % format man1/readelf.1.gz -> cat1/readelf.1.gz % :151: warning [p 1, 3.8i]: cannot adjust line % :300: warning [p 2, 9.7i, div `an-div', 0.0i]: cannot adjust line % :300: warning [p 2, 9.7i]: cannot adjust line % section man2 % format man2/minherit.2.gz -> cat2/minherit.2.gz % mdoc warning: .Fx: Unknown FreeBSD version `2.2.0' (#132) % format man2/sctp_generic_recvmsg.2.gz -> cat2/sctp_generic_recvmsg.2.gz % mdoc warning: Empty input line #76 % format man2/sctp_generic_sendmsg.2.gz -> cat2/sctp_generic_sendmsg.2.gz % mdoc warning: Empty input line #51 % mdoc warning: Empty input line #88 % format man2/sctp_peeloff.2.gz -> cat2/sctp_peeloff.2.gz % mdoc warning: Empty input line #82 % section man3 % format man3/ether_aton.3.gz -> cat3/ether_aton.3.gz % mdoc warning: Empty input line #169 % format man3/gss_add_cred.3.gz -> cat3/gss_add_cred.3.gz % Not a \-mdoc command: .PP (#89) % format man3/gss_inquire_cred_by_mech.3.gz -> cat3/gss_inquire_cred_by_mech.3.gz % mdoc warning: Empty input line #72 % format man3/gss_inquire_mechs_for_name.3.gz -> cat3/gss_inquire_mechs_for_name.3.gz % mdoc warning: Empty input line #50 % format man3/gss_seal.3.gz -> cat3/gss_seal.3.gz % mdoc warning: A .Bl directive has no matching .El (#146) % format man3/gss_unseal.3.gz -> cat3/gss_unseal.3.gz % mdoc warning: A .Bl directive has no matching .El (#159) % format man3/gss_wrap_size_limit.3.gz -> cat3/gss_wrap_size_limit.3.gz % mdoc warning: A .Bl directive has no matching .El (#131) % format man3/lwres_gabn.3.gz -> cat3/lwres_gabn.3.gz % :45: warning [p 1, 5.2i]: can't break line % format man3/lwres_gnba.3.gz -> cat3/lwres_gnba.3.gz % :45: warning [p 1, 5.2i]: can't break line % format man3/lwres_noop.3.gz -> cat3/lwres_noop.3.gz % :45: warning [p 1, 5.2i]: can't break line % format man3/valloc.3.gz -> cat3/valloc.3.gz % mdoc warning: Extraneous .Ef (#49) % format man3/zlib.3.gz -> cat3/zlib.3.gz % :52: warning [p 1, 7.0i]: cannot adjust line % section man4 % format man4/mac.4.gz -> cat4/mac.4.gz % mdoc warning: extraneous .El call (#200) % format man4/md.4.gz -> cat4/md.4.gz % mdoc warning: Unknown keyword `-ofset' in .Bd macro (#68) % mdoc warning: Unknown keyword `indent' in .Bd macro (#68) % format man4/ng_netflow.4.gz -> cat4/ng_netflow.4.gz % :254: warning [p 3, 3.3i]: can't break line % section man5 % format man5/bluetooth.device.conf.5.gz -> cat5/bluetooth.device.conf.5.gz % :93: warning [p 1, 7.2i]: can't break line % format man5/quota.group.5.gz -> cat5/quota.group.5.gz % mdoc warning: Unknown keyword `-indent' in .Bl macro (#53) % mdoc warning: Unknown keyword `offset' in .Bl macro (#53) % section man8 % format man8/fwcontrol.8.gz -> cat8/fwcontrol.8.gz % mdoc warning: Empty input line #179 % format man8/ifmcstat.8.gz -> cat8/ifmcstat.8.gz % mdoc warning: A .Bl directive has no matching .El (#82) % section man9 % format man9/uio.9.gz -> cat9/uio.9.gz % mdoc warning: A .Bl directive has no matching .El (#129) % link cat9/zpfind.9.gz -> cat9/pfind.9.gz These are just the manpages of the base-system. I think I can handle most of them, so I started patching the non-contrib stuff. - Giorgos From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 13:13:04 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0A7816A41B for ; Tue, 30 Oct 2007 13:13:04 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id 5592713C4C6 for ; Tue, 30 Oct 2007 13:13:03 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from kobe.laptop (vader.bytemobile-rio.ondsl.gr [83.235.57.37]) (authenticated bits=128) by igloo.linux.gr (8.14.1/8.14.1/Debian-9) with ESMTP id l9UDCc5E031420 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Oct 2007 15:12:52 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.1/8.14.1) with ESMTP id l9UDCH5b091234; Tue, 30 Oct 2007 15:12:32 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by kobe.laptop (8.14.1/8.14.1/Submit) id l9UDCHf7091233; Tue, 30 Oct 2007 15:12:17 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Tue, 30 Oct 2007 15:12:17 +0200 From: Giorgos Keramidas To: Tim Kientzle Message-ID: <20071030131216.GB91078@kobe.laptop> References: <4726A890.5090705@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4726A890.5090705@freebsd.org> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.119, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.28, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: current@freebsd.org Subject: Re: -mdoc vs. -man X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 13:13:05 -0000 On 2007-10-29 20:44, Tim Kientzle wrote: > I've had some requests from people who want to use the libarchive and > bsdtar manpages on non-BSD systems that don't support -mdoc. > > Any problems if I reworked these manpages to only require -man-old for > compatibility with these systems? (Other than the inherent > tediousness of such a project, that is.) Yes. At least from me. The -mdoc macro set is not only easier to grok than plain -man, but it produces consistently "prettier" output, with an emphasis on the semantic mark-up of manpage elements instead of manual, tedious formatting-related markup. For example, we don't use \f(CWpath\fR in -mdoc to denote pathnames, so that they are are printed with a constant-width font; we use ".Pa path". We don't have to manually track macro arguments and type stuff like: .IP "\-\fIdebug\fR[=[\fIon\fR|\fIverbose\fR|\fIoff\fR]]" .IX "\-\fIdebug\fR[=[\fIon\fR|\fIverbose\fR|\fIoff\fR]]" and so on... Although I understand the pains of people who don't have groff or -mdoc, I'd be a bit sorry if we switched from -mdoc to -man and started writing with the "old school" style of \fIitalic\fR and friends :( - Giorgos From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 14:02:27 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0772916A421 for ; Tue, 30 Oct 2007 14:02:27 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id A44BE13C4C8 for ; Tue, 30 Oct 2007 14:02:26 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.8/8.13.8) with ESMTP id l9UDSWum081479; Tue, 30 Oct 2007 09:28:32 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id l9UDSWAK081359 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Oct 2007 09:28:32 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <200710301328.l9UDSWAK081359@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Tue, 30 Oct 2007 09:29:06 -0400 To: Ihsan Dogan , freebsd-current@freebsd.org From: Mike Tancsa In-Reply-To: References: <20071011003619.GA84433@obelix.dsto.defence.gov.au> <2a41acea0710102002j5c09d285kac076ce2b5e4af41@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: Subject: Re: em0: watchdog timeout ... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 14:02:27 -0000 At 02:35 PM 10/29/2007, Ihsan Dogan wrote: >on 11.10.2007 05:02 Jack Vogel said the following: > > >> em0@pci5:4:0: class=0x020000 card=0x10018086 chip=0x10268086 > rev=0x04 hdr=0x00 > >> vendor = 'Intel Corporation' > >> device = '82545GM Gigabit Ethernet Controller' > >> class = network > >> subclass = ethernet > >> > >> And am consistently experiencing: > >> > >> em0: watchdog timeout -- resetting > >> em0: link state changed to DOWN > >> em0: link state changed to UP > >> em0: watchdog timeout -- resetting > >> em0: link state changed to DOWN > >> em0: link state changed to UP > >> em0: watchdog timeout -- resetting > >> em0: link state changed to DOWN > >> em0: link state changed to UP > >> > >> Anything I can do to help debug this ? > > > > Well, add more detail for one, like timestamps on these events, > > do they happen once a minute, hour, day? > >I've got exactly the same problem on a machine, running 7.0-BETA1. The >Problem occurs during the boot, when dhclient is trying to get IP. The >messages are occuring all the time an it's not possible to use the >network card at all. >In my case, the network card and the soundcard are sharing an irq. If I >don't load the the snd_emu10k1 driver, the network card works perfectly. Mine are shared interrupts as well, however, they are shared among the nics, so disabling is not an option % vmstat -i interrupt total rate irq1: atkbd0 5 0 irq4: sio0 61332 0 irq16: em0 1029688695 614 irq17: em1 em2 em3 775893384 463 irq19: atapci1 300947 0 cpu0: timer 3347198272 1997 cpu1: timer 3347136233 1997 Total 8500278868 5073 em1 is the one having the problems (and yes, I did check the eeprom issue) em1@pci1:0:1: class=0x020000 card=0x115e8086 chip=0x105e8086 rev=0x06 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/1000 PT' class = network subclass = ethernet cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 10[e0] = PCI-Express 1 endpoint its also in FastE mode and not gigE. Not sure if that makes a difference or not. ---Mike From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 14:03:57 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91FBD16A4C9 for ; Tue, 30 Oct 2007 14:03:57 +0000 (UTC) (envelope-from ihsan@dogan.ch) Received: from mail.blastwave.org (mail.blastwave.org [147.87.98.10]) by mx1.freebsd.org (Postfix) with ESMTP id 4AA7A13C4A7 for ; Tue, 30 Oct 2007 14:03:56 +0000 (UTC) (envelope-from ihsan@dogan.ch) Received: from localhost (localhost [127.0.0.1]) by mail.blastwave.org (Postfix) with ESMTP id CB7712971; Tue, 30 Oct 2007 14:45:41 +0100 (MET) X-Virus-Scanned: amavisd-new at blastwave.org Received: from mail.blastwave.org ([127.0.0.1]) by localhost (enterprise.blastwave.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id eG+RiEFpWuuk; Tue, 30 Oct 2007 14:45:28 +0100 (MET) Received: from [192.168.42.127] (pagh.dogan.ch [213.144.146.12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.blastwave.org (Postfix) with ESMTP id 9B30C2B23; Tue, 30 Oct 2007 14:45:27 +0100 (MET) Message-ID: <47273575.5030002@dogan.ch> Date: Tue, 30 Oct 2007 14:45:25 +0100 From: Ihsan Dogan User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Mike Tancsa References: <20071011003619.GA84433@obelix.dsto.defence.gov.au> <2a41acea0710102002j5c09d285kac076ce2b5e4af41@mail.gmail.com> <200710301328.l9UDSWAK081359@lava.sentex.ca> In-Reply-To: <200710301328.l9UDSWAK081359@lava.sentex.ca> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: em0: watchdog timeout ... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 14:03:57 -0000 on 30.10.2007 14:29 Mike Tancsa said the following: >> I've got exactly the same problem on a machine, running 7.0-BETA1. The >> Problem occurs during the boot, when dhclient is trying to get IP. The >> messages are occuring all the time an it's not possible to use the >> network card at all. >> In my case, the network card and the soundcard are sharing an irq. If I >> don't load the the snd_emu10k1 driver, the network card works perfectly. > Mine are shared interrupts as well, however, they are shared among the > nics, so disabling is not an option > > % vmstat -i > interrupt total rate > irq1: atkbd0 5 0 > irq4: sio0 61332 0 > irq16: em0 1029688695 614 > irq17: em1 em2 em3 775893384 463 > irq19: atapci1 300947 0 > cpu0: timer 3347198272 1997 > cpu1: timer 3347136233 1997 > Total 8500278868 5073 > > > em1 is the one having the problems (and yes, I did check the eeprom issue) > > em1@pci1:0:1: class=0x020000 card=0x115e8086 chip=0x105e8086 rev=0x06 > hdr=0x00 > vendor = 'Intel Corporation' > device = 'PRO/1000 PT' > class = network > subclass = ethernet > cap 01[c8] = powerspec 2 supports D0 D3 current D0 > cap 05[d0] = MSI supports 1 message, 64 bit > cap 10[e0] = PCI-Express 1 endpoint > > its also in FastE mode and not gigE. Not sure if that makes a difference > or not. I'm running 1000baseTX. Looks like, that it doesn't depend on that. Ihsan -- ihsan@dogan.ch http://blog.dogan.ch/ http://ihsan.dogan.ch/ From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 14:36:21 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14F4816A417 for ; Tue, 30 Oct 2007 14:36:21 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id E826A13C4A5 for ; Tue, 30 Oct 2007 14:36:20 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id E616F1A4D87; Tue, 30 Oct 2007 07:36:19 -0700 (PDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 30 Oct 2007 10:15:12 -0400 User-Agent: KMail/1.9.7 References: <20071027212420.EC7F94500E@ptavv.es.net> <28D8C5EF-8BAB-433D-A6E3-25B2A40B9BD1@mac.com> In-Reply-To: <28D8C5EF-8BAB-433D-A6E3-25B2A40B9BD1@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710301015.13245.jhb@freebsd.org> Cc: John-Mark Gurney , Marcel Moolenaar , current@freebsd.org Subject: Re: New-bus unit wiring via hints.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 14:36:21 -0000 On Saturday 27 October 2007 06:04:40 pm Marcel Moolenaar wrote: > > On Oct 27, 2007, at 2:24 PM, Kevin Oberman wrote: > > >> From: Marcel Moolenaar > >> Date: Sat, 27 Oct 2007 13:57:25 -0700 > >> > >> > >> On Oct 27, 2007, at 12:40 PM, Kevin Oberman wrote: > >> > >>>> I'm not mandating anything. I'm merely pointing out how > >>>> reality has changed and that it's important to adapt, > >>>> adopt and improve... > >>> > >>> "Reality has changed"? Yes, it has, at least a bit, but not to the > >>> point where we want to confuse serial ports. > >> > >> Are you saying that "we" should accept reality's change > >> only for as far as it doesn't confuse "us" ??? > > > > Just in case I don't understand the issue, feel free to correct me, > > but > > it sounds like you are saying that there will not be a clear link > > between the serial port (sio) number and the port marked '1' on most > > systems. If I am wrong about this, please tell me and I climb back > > under my rock. > > That is not what I'm saying. What I'm saying is: > If the firmware tells the OS that the port marked > "1" on the back corresponds to a UART that has a > base I/O port address of 0x2e8, then who are we > to disagree and demand that it should be 0x3f8? That isn't what is happening though. The port marked "1" is at 0x3f8 and happens to be "later" in the namespace than the port marked "2" which is at 0x2e8. The BIOS may _optionally_ decide to communicate this to the OS via the _UID method, but the _UID is only guaranteed to be a string that it suitable for use in a label in a GUI dialog box. The BIOS may use _UID's of "0" and "1", or "1" and "2", or "COMA" and "COMB". And it may not even supply any _UID values at all. If you want to bind by _UID I already have support for having: hint.sio.0.at="acpi0" hint.sio.0.uid="COMA" However, that 1) does not work out of the box since there is no "standard" format of _UID, so there aren't any default _UID values we can use and 2) does not work on the many boxes where the BIOS does not provide a _UID to begin with. Matching on resources does work for any off-the-shelf x86 box you can go buy at the store though. Even if a PC has non-standard resources for COM1 and COM2, the serial ports will show up as sio2 and sio3. Since you don't care what sio0 means at all why not let other people who _do_ care have it work on their systems? In the case of that system if someone really wants to fix it they can always adjust their hints, and they can even do so in the loader before the kernel is booted if it matters for install, etc. > You rightly point out that what it really boils > down to is how devX maps to a port on the back or > front of the machine. This mapping should not > change gratuitously. Device wiring achieves that. But on what basis will you wire things? The only currently reliable way I can see to wire things on x86 for an ISA device (and yes, the COM port on a PC is ISA even if ACPI is what enumerates it rather than PNPBIOS) is I/O resources or the name of the device in the ACPI namespace (ACPI-only). The latter is hard to get right as well since there is no standardized format for device names. Shoot, my laptop I have for work intentionally obfuscates all method/device/etc. names in the namespace that aren't using a standardized name like _SB_ or _PRS to be Cxxx where 'xxx' is a hexadecimal value so you end up with locations like \_SB_.C003.C026.C02A. ACPI's _UID is unreliable as mentioned above. For uart console wiring you use I/O resources for wiring even. > > The new system has, to the typical user's eyes, the same > > configuration. > > Yes. this means there's a gap between what the user sees > (the chassis) and what FreeBSD sees (the mainboard). As > long as the mainboard is designed for the chassis, that > gap is mostly non-existent or insignificant and what the > firmware tells the OS is what you see on the back (or > front). Otherwise, all bets are off... FYI, on many systems the '1' and '2' (or 'A' and 'B') labels are actually on the mobo, not on the chassis. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 15:02:51 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5EE5E16A469 for ; Tue, 30 Oct 2007 15:02:51 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 470B713C4A3 for ; Tue, 30 Oct 2007 15:02:51 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id E616F1A4D87; Tue, 30 Oct 2007 07:36:19 -0700 (PDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 30 Oct 2007 10:15:12 -0400 User-Agent: KMail/1.9.7 References: <20071027212420.EC7F94500E@ptavv.es.net> <28D8C5EF-8BAB-433D-A6E3-25B2A40B9BD1@mac.com> In-Reply-To: <28D8C5EF-8BAB-433D-A6E3-25B2A40B9BD1@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710301015.13245.jhb@freebsd.org> Cc: John-Mark Gurney , Marcel Moolenaar , current@freebsd.org Subject: Re: New-bus unit wiring via hints.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 15:02:51 -0000 On Saturday 27 October 2007 06:04:40 pm Marcel Moolenaar wrote: > > On Oct 27, 2007, at 2:24 PM, Kevin Oberman wrote: > > >> From: Marcel Moolenaar > >> Date: Sat, 27 Oct 2007 13:57:25 -0700 > >> > >> > >> On Oct 27, 2007, at 12:40 PM, Kevin Oberman wrote: > >> > >>>> I'm not mandating anything. I'm merely pointing out how > >>>> reality has changed and that it's important to adapt, > >>>> adopt and improve... > >>> > >>> "Reality has changed"? Yes, it has, at least a bit, but not to the > >>> point where we want to confuse serial ports. > >> > >> Are you saying that "we" should accept reality's change > >> only for as far as it doesn't confuse "us" ??? > > > > Just in case I don't understand the issue, feel free to correct me, > > but > > it sounds like you are saying that there will not be a clear link > > between the serial port (sio) number and the port marked '1' on most > > systems. If I am wrong about this, please tell me and I climb back > > under my rock. > > That is not what I'm saying. What I'm saying is: > If the firmware tells the OS that the port marked > "1" on the back corresponds to a UART that has a > base I/O port address of 0x2e8, then who are we > to disagree and demand that it should be 0x3f8? That isn't what is happening though. The port marked "1" is at 0x3f8 and happens to be "later" in the namespace than the port marked "2" which is at 0x2e8. The BIOS may _optionally_ decide to communicate this to the OS via the _UID method, but the _UID is only guaranteed to be a string that it suitable for use in a label in a GUI dialog box. The BIOS may use _UID's of "0" and "1", or "1" and "2", or "COMA" and "COMB". And it may not even supply any _UID values at all. If you want to bind by _UID I already have support for having: hint.sio.0.at="acpi0" hint.sio.0.uid="COMA" However, that 1) does not work out of the box since there is no "standard" format of _UID, so there aren't any default _UID values we can use and 2) does not work on the many boxes where the BIOS does not provide a _UID to begin with. Matching on resources does work for any off-the-shelf x86 box you can go buy at the store though. Even if a PC has non-standard resources for COM1 and COM2, the serial ports will show up as sio2 and sio3. Since you don't care what sio0 means at all why not let other people who _do_ care have it work on their systems? In the case of that system if someone really wants to fix it they can always adjust their hints, and they can even do so in the loader before the kernel is booted if it matters for install, etc. > You rightly point out that what it really boils > down to is how devX maps to a port on the back or > front of the machine. This mapping should not > change gratuitously. Device wiring achieves that. But on what basis will you wire things? The only currently reliable way I can see to wire things on x86 for an ISA device (and yes, the COM port on a PC is ISA even if ACPI is what enumerates it rather than PNPBIOS) is I/O resources or the name of the device in the ACPI namespace (ACPI-only). The latter is hard to get right as well since there is no standardized format for device names. Shoot, my laptop I have for work intentionally obfuscates all method/device/etc. names in the namespace that aren't using a standardized name like _SB_ or _PRS to be Cxxx where 'xxx' is a hexadecimal value so you end up with locations like \_SB_.C003.C026.C02A. ACPI's _UID is unreliable as mentioned above. For uart console wiring you use I/O resources for wiring even. > > The new system has, to the typical user's eyes, the same > > configuration. > > Yes. this means there's a gap between what the user sees > (the chassis) and what FreeBSD sees (the mainboard). As > long as the mainboard is designed for the chassis, that > gap is mostly non-existent or insignificant and what the > firmware tells the OS is what you see on the back (or > front). Otherwise, all bets are off... FYI, on many systems the '1' and '2' (or 'A' and 'B') labels are actually on the mobo, not on the chassis. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 15:02:51 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6263216A46C for ; Tue, 30 Oct 2007 15:02:51 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 4F3F013C4A5 for ; Tue, 30 Oct 2007 15:02:51 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id AB09D1A3C1A; Tue, 30 Oct 2007 07:36:18 -0700 (PDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 30 Oct 2007 09:57:35 -0400 User-Agent: KMail/1.9.7 References: <575715.97141.qm@web27805.mail.ukl.yahoo.com> In-Reply-To: <575715.97141.qm@web27805.mail.ukl.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710300957.35545.jhb@freebsd.org> Cc: Red Neck Subject: Re: Loader broken in Head? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 15:02:51 -0000 On Friday 26 October 2007 08:03:21 pm Red Neck wrote: > Hi, > > Within the last day (26/10/07) I've built and installed the sources from CVS > Head only to find the stage 3 boot loader, /boot/loader, not working. I'm > using a Mac Pro with 3 internal hard drives. On one hard disk I have > FreeBSD amd64 installed, occupying the entire disk (MBR). Using the sources > from Head, loader just freezes after displaying its initial messages with a > constantly spinning cursor. To access the system I have to revert to using > an older loader such as 6.2 release's. I have attached my make and kernel > config. What does 'lsdev' from the old loader output on the box? -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 15:02:51 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DE4116A46D for ; Tue, 30 Oct 2007 15:02:51 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 5829313C4A7 for ; Tue, 30 Oct 2007 15:02:51 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id 36C2C1A4D88; Tue, 30 Oct 2007 07:36:22 -0700 (PDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 30 Oct 2007 10:29:25 -0400 User-Agent: KMail/1.9.7 References: <20071029190208.GD78150@bunrab.catwhisker.org> <20071030035253.GF78150@bunrab.catwhisker.org> <0710301238250.31552@www.mmlab.cse.yzu.edu.tw> In-Reply-To: <0710301238250.31552@www.mmlab.cse.yzu.edu.tw> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710301029.26316.jhb@freebsd.org> Cc: Tai-hwa Liang Subject: Re: Detach of an0 induced kernel panic in 7.0-PRE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 15:02:51 -0000 On Tuesday 30 October 2007 12:39:38 am Tai-hwa Liang wrote: > On Mon, 29 Oct 2007, David Wolfskill wrote: > > On Tue, Oct 30, 2007 at 09:38:47AM +0800, Tai-hwa Liang wrote: > >> ... > >>> Unread portion of the kernel message buffer: > >>> an0: RID access failed > >>> an0: detached > >>> > >>> > >>> Fatal trap 12: page fault while in kernel mode > >> ... > >>> #0 doadump () at pcpu.h:195 > >>> 195 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); > >>> (kgdb) bt > >>> #0 doadump () at pcpu.h:195 > >>> #1 0xc073b637 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 > >>> #2 0xc073b8f9 in panic (fmt=Variable "fmt" is not available. > >>> ) at /usr/src/sys/kern/kern_shutdown.c:563 > >>> #3 0xc0a005dc in trap_fatal (frame=0xe2987c1c, eva=3358077304) > >>> at /usr/src/sys/i386/i386/trap.c:872 > >>> #4 0xc0a00860 in trap_pfault (frame=0xe2987c1c, usermode=0, > >>> eva=3358077304) > >>> at /usr/src/sys/i386/i386/trap.c:785 > >>> #5 0xc0a011d5 in trap (frame=0xe2987c1c) at > >>> /usr/src/sys/i386/i386/trap.c:463 > >>> #6 0xc09e71eb in calltrap () at /usr/src/sys/i386/i386/exception.s:139 > >>> #7 0xc04daaf7 in an_stats_update (xsc=0xc8282000) at atomic.h:149 > >>> #8 0xc074d7ea in softclock (dummy=0x0) at > >>> /usr/src/sys/kern/kern_timeout.c:274 > >>> #9 0xc071ef0b in ithread_loop (arg=0xc3f0d2f0) > >>> at /usr/src/sys/kern/kern_intr.c:1036 > >>> #10 0xc071bc19 in fork_exit (callout=0xc071ed60 , > >>> arg=0xc3f0d2f0, frame=0xe2987d38) at /usr/src/sys/kern/kern_fork.c:796 > >>> #11 0xc09e7260 in fork_trampoline () at > >>> /usr/src/sys/i386/i386/exception.s:205 > >>> (kgdb) > >> ... > >> Does the attached patch help? > > > > Aye, it does appear to do so. > > > > I tested at home, where the an0 NIC is actually useful. But I managed > > to detach the card before the script reported successful association; > > the machine kept running (and the script fell back to trying the wi0 > > NIC, since the an0 NIC was no longer there). > > > > I'd call that a definite improvement -- and fast response! Thanks again! > > Thank you for the testing works. I'll ask for re@'s approval once > this is settled in HEAD. This isn't really the best fix as it is still racey. A better approach is to make an(4) use the callout API with callout_init_mtx() and to add a callout_drain() during an_detach() otherwise you can still get panics due to the callout routine trying to lock a destroyed mutex. Something like this: Index: if_an.c =================================================================== RCS file: /host/cvs/usr/cvs/src/sys/dev/an/if_an.c,v retrieving revision 1.84 diff -u -r1.84 if_an.c --- if_an.c 10 Sep 2007 12:53:34 -0000 1.84 +++ if_an.c 30 Oct 2007 14:28:37 -0000 @@ -790,7 +790,7 @@ */ ether_ifattach(ifp, sc->an_caps.an_oemaddr); - callout_handle_init(&sc->an_stat_ch); + callout_init_mtx(&sc->an_stat_ch, &sc->an_mtx); return(0); fail:; @@ -818,6 +818,7 @@ AN_UNLOCK(sc); ether_ifdetach(ifp); bus_teardown_intr(dev, sc->irq_res, sc->irq_handle); + callout_drain(&sc->an_stat_ch); if_free(ifp); an_release_resources(dev); mtx_destroy(&sc->an_mtx); @@ -1150,7 +1151,7 @@ struct ifnet *ifp; sc = xsc; - AN_LOCK(sc); + AN_LOCK_ASSERT(sc); ifp = sc->an_ifp; sc->an_status.an_type = AN_RID_STATUS; @@ -1164,8 +1165,7 @@ /* Don't do this while we're transmitting */ if (ifp->if_drv_flags & IFF_DRV_OACTIVE) { - sc->an_stat_ch = timeout(an_stats_update, sc, hz); - AN_UNLOCK(sc); + callout_reset(&sc->an_stat_ch, hz, an_stats_update, sc); return; } @@ -1173,8 +1173,7 @@ sc->an_stats.an_type = AN_RID_32BITS_CUM; an_read_record(sc, (struct an_ltv_gen *)&sc->an_stats.an_len); - sc->an_stat_ch = timeout(an_stats_update, sc, hz); - AN_UNLOCK(sc); + callout_reset(&sc->an_stat_ch, hz, an_stats_update, sc); return; } @@ -2615,7 +2614,7 @@ ifp->if_drv_flags |= IFF_DRV_RUNNING; ifp->if_drv_flags &= ~IFF_DRV_OACTIVE; - sc->an_stat_ch = timeout(an_stats_update, sc, hz); + callout_reset(&sc->an_stat_ch, hz, an_stats_update, sc); AN_UNLOCK(sc); return; @@ -2828,7 +2827,7 @@ for (i = 0; i < AN_TX_RING_CNT; i++) an_cmd(sc, AN_CMD_DEALLOC_MEM, sc->an_rdata.an_tx_fids[i]); - untimeout(an_stats_update, sc, sc->an_stat_ch); + callout_stop(&sc->an_stat_ch); ifp->if_drv_flags &= ~(IFF_DRV_RUNNING|IFF_DRV_OACTIVE); Index: if_anreg.h =================================================================== RCS file: /host/cvs/usr/cvs/src/sys/dev/an/if_anreg.h,v retrieving revision 1.23 diff -u -r1.23 if_anreg.h --- if_anreg.h 10 Jun 2005 16:49:03 -0000 1.23 +++ if_anreg.h 30 Oct 2007 14:24:50 -0000 @@ -485,7 +485,7 @@ int an_have_rssimap; struct an_ltv_rssi_map an_rssimap; #endif - struct callout_handle an_stat_ch; + struct callout an_stat_ch; struct mtx an_mtx; device_t an_dev; struct ifmedia an_ifmedia; -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 15:47:12 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A09AA16A47A for ; Tue, 30 Oct 2007 15:47:12 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 7476A13C4A7 for ; Tue, 30 Oct 2007 15:47:11 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id EC3E444A74; Tue, 30 Oct 2007 11:47:10 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Tue, 30 Oct 2007 11:47:10 -0400 X-Sasl-enc: g/YmlKte5kHjWLgCDfIZPULocmp2MKluoL77/d8u/kZ3 1193759230 Received: from [192.168.1.235] (64-142-85-108.dsl.dynamic.sonic.net [64.142.85.108]) by mail.messagingengine.com (Postfix) with ESMTP id 6792F112E5; Tue, 30 Oct 2007 11:47:10 -0400 (EDT) Message-ID: <472751E9.7@freebsd.org> Date: Tue, 30 Oct 2007 08:46:49 -0700 From: Darren Reed User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Randall Stewart References: <4726561D.7090805@cisco.com> In-Reply-To: <4726561D.7090805@cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Opensolaris SMF for FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 15:47:12 -0000 Randall Stewart wrote: > Anyone looked at porting SMF to FreeBSD? If SMF were to be ported to FreeBSD, I'd like for the design mistakes in the CLI tools for SMF to be corrected. SMF might be somewhat revolutionary for some Un*x folks, but its not as sexy and as much of a must-have as ZFS is. Darren From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 16:05:47 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FA3A16A4DE; Tue, 30 Oct 2007 16:05:47 +0000 (UTC) (envelope-from ulrich@pukruppa.net) Received: from pukruppa.net (pukruppa.net [213.146.114.24]) by mx1.freebsd.org (Postfix) with ESMTP id C5A8813C4B5; Tue, 30 Oct 2007 16:05:43 +0000 (UTC) (envelope-from ulrich@pukruppa.net) Received: from pukruppa.net (localhost [127.0.0.1]) by pukruppa.net (8.14.1/8.14.1) with ESMTP id l9UFdeuT052012; Tue, 30 Oct 2007 16:39:40 +0100 (CET) (envelope-from ulrich@pukruppa.net) Received: from localhost (ulrich@localhost) by pukruppa.net (8.14.1/8.14.1/Submit) with ESMTP id l9UFdd1f052009; Tue, 30 Oct 2007 16:39:40 +0100 (CET) (envelope-from ulrich@pukruppa.net) Date: Tue, 30 Oct 2007 16:39:39 +0100 (CET) From: "P.U.Kruppa" X-X-Sender: ulrich@small To: Yuri Lukin In-Reply-To: <20071029235020.M75001@swaggi.com> Message-ID: <20071030163704.R2455@small> References: <20071029235020.M75001@swaggi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org, freebsd-java@freebsd.org Subject: Re: Firefox Java plugin with 7.0? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 16:05:48 -0000 On Mon, 29 Oct 2007, Yuri Lukin wrote: > > I'm like to ask what people are using for Java plugin with Firefox. There were > a few recent threads on this subject but no definitive answer: > > http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078038.html > http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078492.html > > I tried compiling jdk15 port and was able to build it and install it > successfully. However, when trying to load a java applet in Firefox, the > browser seemingly crashes (exits). I then tried following the method described > in the handbook by downloading the diablo-jre-freebsd6.i386.1.5.0.07.01.tbz > package from FreeBSD Foundation website and adding it with pkg_add. Trying to > load java applets crashes Firefox. In both cases, javavmwrapper was installed > and about:plugins in Firefox shows that java plugin is installed. Is there a > working combination for 7.0-PRERELEASE/BETA? Since yesterday's portsnap I have got it running with native jdk1.6.0 (on amd64, but probably it will also work on i386). Good Luck, Uli. > > My system is: > > # uname -a > FreeBSD 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #0: Mon Oct 15 13:02:17 EDT > 2007 swaggy@:/usr/obj/usr/src/sys/T61 i386 > # pkg_info | grep java > javavmwrapper-2.3 Wrapper script for various Java Virtual Machines > # pkg_info | grep firefox > firefox-2.0.0.8,1 Web browser based on the browser portion of Mozilla > > # ls -la /usr/local/lib/browser_plugins/ > total 96 > drwxr-xr-x 2 root wheel 512 Oct 29 19:22 . > drwxr-xr-x 54 root wheel 31232 Oct 29 13:26 .. > -rw-r--r-- 1 root wheel 0 Oct 20 00:20 .firefox.keep > lrwxr-xr-x 1 root wheel 63 Oct 29 19:22 libjavaplugin_oji.so -> > /usr/local/diablo-jre1.5.0/plugin/i386/ns7/libjavaplugin_oji.so > -rwxr-xr-x 1 root wheel 62192 Sep 12 14:21 npwrapper.libflashplayer.so > > > Currently with jre from FreeBSD foundation site: > # pkg_info | grep jre > diablo-jre-1.5.0.07.01 Java Runtime Environment 1.5.0_07.01 > > > Thanks, > Yuri > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > Peter Ulrich Kruppa Wuppertal Germany From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 16:06:46 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3FC816A46B for ; Tue, 30 Oct 2007 16:06:46 +0000 (UTC) (envelope-from gtodd@bellanet.org) Received: from ik-out-1112.google.com (ik-out-1112.google.com [66.249.90.180]) by mx1.freebsd.org (Postfix) with ESMTP id 4803613C4BC for ; Tue, 30 Oct 2007 16:06:45 +0000 (UTC) (envelope-from gtodd@bellanet.org) Received: by ik-out-1112.google.com with SMTP id c21so801641ika for ; Tue, 30 Oct 2007 09:06:44 -0700 (PDT) Received: by 10.142.177.7 with SMTP id z7mr1723320wfe.1193758948166; Tue, 30 Oct 2007 08:42:28 -0700 (PDT) Received: from ?10.10.10.149? ( [198.62.158.205]) by mx.google.com with ESMTPS id g36sm4198172rob.2007.10.30.08.42.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 30 Oct 2007 08:42:27 -0700 (PDT) Message-ID: <472750EF.8070808@bellanet.org> Date: Tue, 30 Oct 2007 11:42:39 -0400 From: Graham Todd User-Agent: Thunderbird 2.0.0.5 (X11/20070727) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <4726561D.7090805@cisco.com> <20071030064559.GL82157@redundancy.redundancy.org> In-Reply-To: <20071030064559.GL82157@redundancy.redundancy.org> X-Enigmail-Version: 0.95.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Opensolaris SMF for FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 16:06:46 -0000 David E. Thiel wrote: > On Mon, Oct 29, 2007 at 05:52:29PM -0400, Randall Stewart wrote: >> Anyone looked at porting SMF to FreeBSD? > > Not to my knowledge. What do you feel that SMF offers that currently > existing systems like rcNG or daemontools/runit do not? I haven't > found SMF to be more useful or functional than those solutions, and > it's certainly not as easy to use. I agree. SMF has a lot of tools that go beyond basic service management (service snapshots, "self-healing" ??, etc) but don't a lot of those SMF features depend on base OS functionality that only is found Solaris? If you need to have service management a bit abstracted from the base system runit (smarden.org/runit/) makes it easy to write portable startup scripts and handle logging in a (mostly) nice way. It doesn't try to do too much - it's pretty simple. And it has a three-clause BSDish license unlike more featureful systems like launchd :) We use runit quite a bit (on systems that run a small number of services) and really like it - more than daemontools. We also use runit as a replacement for init on some small footprint linux boxes - it's statically linked against dietlibc and comes in at around 10k in size! I'd like to figure out how to shrink things a bit on FreeBSD as well but there doesn't seem to be easy way to do that (dietlibc is what makes it happen on Linux). Replacing init on FreeBSD is possible as well but we haven't seen the need to do that. cheers, From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 16:20:56 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D47016A420 for ; Tue, 30 Oct 2007 16:20:56 +0000 (UTC) (envelope-from ob@gruft.de) Received: from obh.snafu.de (v6.gruft.de [IPv6:2001:1560:2342::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3D59B13C4C2 for ; Tue, 30 Oct 2007 16:20:56 +0000 (UTC) (envelope-from ob@gruft.de) Received: from ob by obh.snafu.de with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Imtpn-000OIv-C3 for freebsd-current@freebsd.org; Tue, 30 Oct 2007 17:20:55 +0100 Date: Tue, 30 Oct 2007 17:20:55 +0100 From: Oliver Brandmueller To: freebsd-current@freebsd.org Message-ID: <20071030162055.GB54817@e-Gitt.NET> Mail-Followup-To: freebsd-current@freebsd.org References: <4726561D.7090805@cisco.com> <20071030064559.GL82157@redundancy.redundancy.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071030064559.GL82157@redundancy.redundancy.org> User-Agent: Mutt/1.5.16 (2007-06-09) Sender: Oliver Brandmueller Subject: Re: Opensolaris SMF for FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 16:20:56 -0000 Hi, On Mon, Oct 29, 2007 at 11:45:59PM -0700, David E. Thiel wrote: > On Mon, Oct 29, 2007 at 05:52:29PM -0400, Randall Stewart wrote: > > Anyone looked at porting SMF to FreeBSD? > > Not to my knowledge. What do you feel that SMF offers that currently > existing systems like rcNG or daemontools/runit do not? I haven't > found SMF to be more useful or functional than those solutions, and > it's certainly not as easy to use. It takes a little time (actually 2 hours should be fine) to get the idea and write the first few services. Although rcNG is quite good at it's job, SMF is able to offer quite some nice features, which rcNG can't offer. In fact SMF is not just start and stop scripts, but also watches if every service that is configured to run is running (not just if it started) and it knows about dependencies. For example SMF can do something like that: you configure apache depends on mysql. At system start everything is fine, but for whatever reason MySQL dies. SMF tries to restart MySQL, if this does not work it will also shutdown apache. (Please don't start a discussion if this example is useful, it's just to get the idea). Since SMF does not only start or stop services it needs support from the system level. It also highly different at all from doing things like setting a variable in rc.conf to austostart a service. While it surely would be a great thing, this changes a lot of things and I doubt this is just a simple port. If at all this could be a project for 8.0 and won't find it's way into a -STABLE branch. Greetings, Olli -- | Oliver Brandmueller | Offenbacher Str. 1 | Germany D-14197 Berlin | | Fon +49-172-3130856 | Fax +49-172-3145027 | WWW: http://the.addict.de/ | | Ich bin das Internet. Sowahr ich Gott helfe. | | Eine gewerbliche Nutzung aller enthaltenen Adressen ist nicht gestattet! | From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 16:27:27 2007 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2185C16A420; Tue, 30 Oct 2007 16:27:27 +0000 (UTC) (envelope-from keramida@FreeBSD.org) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id 1714D13C4C8; Tue, 30 Oct 2007 16:27:23 +0000 (UTC) (envelope-from keramida@FreeBSD.org) Received: from kobe.laptop (vader.bytemobile-rio.ondsl.gr [83.235.57.37]) (authenticated bits=128) by igloo.linux.gr (8.14.1/8.14.1/Debian-9) with ESMTP id l9UGQvX8011543 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 30 Oct 2007 18:27:12 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.1/8.14.1) with ESMTP id l9UGQadA092942; Tue, 30 Oct 2007 18:26:52 +0200 (EET) (envelope-from keramida@FreeBSD.org) Received: (from keramida@localhost) by kobe.laptop (8.14.1/8.14.1/Submit) id l9UGQasc092941; Tue, 30 Oct 2007 18:26:36 +0200 (EET) (envelope-from keramida@FreeBSD.org) Date: Tue, 30 Oct 2007 18:26:36 +0200 From: Giorgos Keramidas To: Jeremy Chadwick Message-ID: <20071030162636.GA92815@kobe.laptop> References: <20071028074248.GA1511@haakonia.hitnet.RWTH-Aachen.DE> <4724BAD9.7000400@charter.net> <20071028164152.GA7516@eos.sc1.parodius.com> <4724BEB3.5080905@charter.net> <20071029132447.GA2658@kobe.laptop> <20071029191836.GA58058@eos.sc1.parodius.com> <20071030113247.GA3941@kobe.laptop> <20071030121603.GA90748@kobe.laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071030121603.GA90748@kobe.laptop> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.121, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.28, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: stable@FreeBSD.org, current@FreeBSD.org Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 16:27:27 -0000 On 2007-10-30 14:16, Giorgos Keramidas wrote: > Neat. The base-system manpages which have errors or warnings are just a > few of the hundreds we have. I just finished running a slightly > modified version of `/etc/periodic/weekly/330.catman', which uses > `catman -v' and the list of files with errors (after a bit of manual > parsing) is now: > > % Reformatting manual pages: > % /usr/share/man: not writable - will only be able to write to existing cat directories > % [...] Hi again Jeremy. The 'trigger' for using 330.catman and "catman -v" was very useful indeed :) I've fixed the following manpages in CURRENT, and will MFC the changes after a while (given RE approval for RELENG_7): minherit.2, sctp_generic_recvmsg.2, sctp_generic_sendmsg.2, sctp_peeloff.2, ether_aton.3, gss_add_cred.3, gss_inquire_cred_by_mech.3, gss_inquire_mechs_for_name.3, gss_seal.3, gss_unseal.3, gss_wrap_size_limit.3, valloc.3, mac.4, md.4, quota.group.5, fwcontrol.8, ifmcstat.8, uio.9 There are still some errors/warnings in contrib manpages, like: readelf.1 (binutils) lwres_gabn.3 (bind) lwres_gnba.3 (bind) lwres_noop.3 (bind) zlib.3 (zlib) I'll ask the respective contrib-code maintainers before making changes here, to avoid taking files off the vendor branch if it's too bad. There are also a couple of manpages with references to very long URIs, which cannot be wrapped by nroff in a reasonable line-length: ng_netflow.4 bluetooth.device.conf.5 I don't think we can easily fix these, without manually wrapping the URIs, but that may 'break' copy/pasting of the URIs :/ - Giorgos From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 17:01:51 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F091516A4A0 for ; Tue, 30 Oct 2007 17:01:51 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.freebsd.org (Postfix) with ESMTP id B533313C4AC for ; Tue, 30 Oct 2007 17:01:49 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1578350nfb for ; Tue, 30 Oct 2007 10:01:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; 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=kPLGWcai8aRj5WZyjPn6cbPO1RmTlthZ2RkAnual+aE=; b=fG7G2LIh4tnEtoRArCGHm5OmLtuVa2t7Th3Jm8aOjDOODpOySi0QmsBv4BS6R41f4d2mLeP+6TRd+wg6T+67pDswXp1RhW/LRJ+WuLm0MINKZkMtZJ8kqVx2H09THM2zbH7ohyM+Kmor+0d/2rEysnLN9fGnx65GyuD07tEZM+Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=dyp3I86mw8EaBts1Gph9EUO/eMWUZbNlIrMBfcPuuNMGi/nU/GZ3EfAnwriOucCUfDt7wdTXjCD29qgczzeclYNxPpDnSGpNT9H5/nhzzyTX2g9R8lbwkVCFZI9CYI4gVjqtm06E6M/51f8vkzArmR/avMeAAlt5mVVE3D8WEYg= Received: by 10.86.90.2 with SMTP id n2mr5818352fgb.1193763708179; Tue, 30 Oct 2007 10:01:48 -0700 (PDT) Received: by 10.86.100.19 with HTTP; Tue, 30 Oct 2007 10:01:48 -0700 (PDT) Message-ID: <2a41acea0710301001k60442b26uae186209ac484780@mail.gmail.com> Date: Tue, 30 Oct 2007 10:01:48 -0700 From: "Jack Vogel" To: "gnn@freebsd.org" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0710291045m6f1d2acw78c26a455ea3894d@mail.gmail.com> Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List Subject: Re: RFC: Evolution of the em driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 17:01:52 -0000 On 10/30/07, gnn@freebsd.org wrote: > At Mon, 29 Oct 2007 10:45:17 -0700, > Jack Vogel wrote: > > > > I have an important decision to make and I thought rather than just make > > it and spring it on you I'd present the issues and see what opinions were. > > > > Our newer hardware uses new features that, more and more, require > > parallel code paths in the driver. For instance, the 82575 (Zoar) uses > > what are called 'advanced descriptors', this means different TX path. > > The 7.0 em driver has this support in it, it just uses a function pointer > > to handle it. > > > > When I add in multiqueue/RSS support it will add even more code > > that functions this way. > > > > What the Linux team did was to split the newer code into a standalone > > driver, they call it 'igb'. I had originally resisted doing this, but with > > the development I have been working on the past month I am starting > > to wonder if it might not be best to follow them. > > > > I see 3 possibilities and I'd like feedback, which would you prefer if > > you have a preference and why. > > > > First, keep the driver as is and just live with multiple code paths > > and features, possibly #ifdef'ed as they appear. > > > > Second, split the driver as Linux has into em and igb. The added > > question then is how to split it, Linux made the line the use of > > advanced descriptors, so Zoar and after, but I could also see a > > case for having everything PCI-E/MSI capable being in the new > > driver. > > > > Third, sort of a half-way approach, split up code but not the > > driver, in other words offer different source files that can be > > compiled into the driver, so you could have the one big jumbo > > driver with all in there, or one that will only work with a subset > > of adapters. This one would probably be the most work, because > > its a new approach. > > As you're the main maintainer it's your choice. Whatever is easiest > for you and gives us the most readable code. Thanks, I know its my choice, I was just looking for opinions about the options I had to chose from :) I think I've had enough feedback to decide, I think the seperate driver is the direction. I need to give some thought to where to make the split. Thanks for everyone's feedback. Jack From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 17:08:10 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3259E16A46B; Tue, 30 Oct 2007 17:08:10 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.83]) by mx1.freebsd.org (Postfix) with ESMTP id DBDBA13C4C1; Tue, 30 Oct 2007 17:08:09 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (asmtp003-s [10.150.69.66]) by smtpoutm.mac.com (Xserve/smtpout020/MantshX 4.0) with ESMTP id l9UH82WM010493; Tue, 30 Oct 2007 10:08:02 -0700 (PDT) Received: from mini-g4.jnpr.net (natint3.juniper.net [66.129.224.36]) (authenticated bits=0) by mac.com (Xserve/asmtp003/MantshX 4.0) with ESMTP id l9UH7kU0017114 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 30 Oct 2007 10:07:48 -0700 (PDT) Message-Id: <4B6E9989-28E0-4C73-8F0C-20BB009FAAA7@mac.com> From: Marcel Moolenaar To: John Baldwin In-Reply-To: <200710301015.13245.jhb@freebsd.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v912) Date: Tue, 30 Oct 2007 10:07:44 -0700 References: <20071027212420.EC7F94500E@ptavv.es.net> <28D8C5EF-8BAB-433D-A6E3-25B2A40B9BD1@mac.com> <200710301015.13245.jhb@freebsd.org> X-Mailer: Apple Mail (2.912) Cc: John-Mark Gurney , freebsd-current@freebsd.org, current@freebsd.org Subject: Re: New-bus unit wiring via hints.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 17:08:10 -0000 On Oct 30, 2007, at 7:15 AM, John Baldwin wrote: >> That is not what I'm saying. What I'm saying is: >> If the firmware tells the OS that the port marked >> "1" on the back corresponds to a UART that has a >> base I/O port address of 0x2e8, then who are we >> to disagree and demand that it should be 0x3f8? > > That isn't what is happening though. The port marked "1" is at 0x3f8 > and happens to be "later" in the namespace than the port marked "2" > which is at 0x2e8. The BIOS may _optionally_ decide to communicate > this to the OS via the _UID method, but the _UID is only guaranteed > to be a string that it suitable for use in a label in a GUI dialog > box. Doesn't this imply that enumerating on the lexicographical ordering of the (optional) _UID method would help us do what firmware writers intend? In other words, we don't need a number. We just need a means to determine the relative order and we enumerate in that relative order. Isn't that how it is now (and if not shouldn't it be that way)? > Even if a PC has non-standard resources for COM1 and COM2, the serial > ports will show up as sio2 and sio3. This is another sio(4) bug that uart(4) doesn't have, yes :-) > Since you don't care what sio0 > means at all why not let other people who _do_ care have it work on > their > systems? "I" may not care what sio0 means, but that doesn't mean "I" don't care that "my" serial ports aren't numbered starting with 0. >> You rightly point out that what it really boils >> down to is how devX maps to a port on the back or >> front of the machine. This mapping should not >> change gratuitously. Device wiring achieves that. > > But on what basis will you wire things? Correcting the mapping of device instances to physical/visible ports will need to be based on user input. A default mapping, based on the self-enumerating ability of hardware/firmware, may not get it just right in all cases. But may provide a good and reliable starting point that may end up 90+% correct. > The only currently reliable > way I can see to wire things on x86 for an ISA device (and yes, the > COM port on a PC is ISA even if ACPI is what enumerates it rather than > PNPBIOS) is I/O resources or the name of the device in the ACPI > namespace (ACPI-only). I disagree. Since the firmware describes the legacy devices present in the system, the only reliable way is to trust that information. Sure, bugs may exist but 95+% of the FreeBSD code assumes correctness of hardware as it is, so why not in this respect? Anyway, when ACPI describes the hardware, I prefer not to call the legacy hardware ISA devices. It's important to make a clear distinction between enumerating and non-enumerating hardware, because that allows you to create mechanisms for dealing with non-enumerating hardware (i.e. hints) without creating conflicts or ambiguity with enumerating HW. We have convoluted this and mistakenly accepted this convolution as a property of ISA hardware. I've been advocating that our bus-abstraction is a good one. Devices enumerated by ACPI can be said to be attached to an ACPI bus. At least it's not more wrong than saying that they are ISA devices when it's obvious that there's no ISA bus to be found in modern hardware and all the legacy hardware is really on the chipsets LPC bus. > For uart console wiring you use I/O resources for > wiring even. Yes, but not "even". Since bus-enumeration hasn't happened yet, we can not describe the serial console by name+unit, because we have no way of knowing upfront what unit number will be assigned to the UART. The only way you can describe the serial console is by hardware resources or by firmware-level names (such as is the case on powerpc & sparc64). This is why using hints to "mark" the console is wrong. Note also that on ia64 (at least) ACPI tables exist that describe the serial console (and debug port) and those tables use hardware resources. So, the common denominator is I/O resources (even for OFW-based machines) and as it is, it's really the only thing you need (module hardware type) to make a low-level console work. The only correct way to identify hardware for use as low-level console is by it's location in I/O space (module hardware type). This is what uart(4) does and it's one of the reasons uart(4) works on all platforms even though low-level console support is highly machine dependent. It's the right way of doing it and as such it just works. Do not mistake low-level console identification with bus-enumeration device wiring or it being similar to hints. To re-iterate: We should reserve hints for describing non-enumerating hardware (which means device.hints should be non-existent OOTB) and we should add other mechanisms to wire devices to hardware, making use of the fact that underneath it mechanisms exist to enumerate the hardware (incl. hints for non-enumerating hardware). In the future we can replace hints with a more flexible and expressive means to describe hardware so that it better meets the needs of embedded environments and without it impacting device wiring. -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 17:16:26 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 216DA16A418 for ; Tue, 30 Oct 2007 17:16:26 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.freebsd.org (Postfix) with ESMTP id 7350D13C4AC for ; Tue, 30 Oct 2007 17:16:25 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1582433nfb for ; Tue, 30 Oct 2007 10:16:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=W/l8AY7sBnxRg4v4pQSAq/1sQV1ax1M6TDAjozWQn40=; b=lOBwR9qRn41K5Vq4A8AWEuxSGammwF4mPmw7EadXK67CobAbMPmBeJ3k2UmLJPg4GAET+CH5Nd1rpS/nCHTtGl2XENwfGJ1CZSM89sLS7rIbbbvgfI7geEN4IlsT+IXtyHegEx7S3cIuyZd6L7kHlMw52mh+UQ/yyx3UzY7mFzg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=BOvkt1UhaTB/oEq60k+h9+A9VY67bWM84fTTxt3nxvDjnHMD8kjNeFrOA94JHECt+RgJwha2lnmNtXEgBWTwJZJQsOA3ExjZ3vJT0KKhjN2z3IOhfgkqNS3IfirX8IVDEkUFXqt//p0Sy+TBQKIdxygf2AGqlmLpcd9ICz+czRc= Received: by 10.86.71.1 with SMTP id t1mr5826381fga.1193764582321; Tue, 30 Oct 2007 10:16:22 -0700 (PDT) Received: by 10.86.100.19 with HTTP; Tue, 30 Oct 2007 10:16:22 -0700 (PDT) Message-ID: <2a41acea0710301016u4a0008dfjc83170257337863c@mail.gmail.com> Date: Tue, 30 Oct 2007 10:16:22 -0700 From: "Jack Vogel" To: "freebsd-net@freebsd.org" , "FreeBSD Stable List" , "FreeBSD Current" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: em watchdog problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 17:16:26 -0000 This morning I had an idea about what the source of the watchdog problem is. Also, we have repro'd at least one type of watchdog inhouse. One question, is this problem only happening for those running STABLE with the 6.6.6 merged driver? We found the problem does not seem to happen on 7.0. Right now my suspicion is that the FAST irq handling is again causing a problem. I am experimenting with variations to the code today to be sure whats going on, and hopefully fixing it. Cheers, Jack From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 17:38:56 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50A1016A4F0 for ; Tue, 30 Oct 2007 17:38:56 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.83]) by mx1.freebsd.org (Postfix) with ESMTP id 2A0D513C4A8 for ; Tue, 30 Oct 2007 17:38:56 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (asmtp003-s [10.150.69.66]) by smtpoutm.mac.com (Xserve/smtpout020/MantshX 4.0) with ESMTP id l9UH82WM010493; Tue, 30 Oct 2007 10:08:02 -0700 (PDT) Received: from mini-g4.jnpr.net (natint3.juniper.net [66.129.224.36]) (authenticated bits=0) by mac.com (Xserve/asmtp003/MantshX 4.0) with ESMTP id l9UH7kU0017114 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 30 Oct 2007 10:07:48 -0700 (PDT) Message-Id: <4B6E9989-28E0-4C73-8F0C-20BB009FAAA7@mac.com> From: Marcel Moolenaar To: John Baldwin In-Reply-To: <200710301015.13245.jhb@freebsd.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v912) Date: Tue, 30 Oct 2007 10:07:44 -0700 References: <20071027212420.EC7F94500E@ptavv.es.net> <28D8C5EF-8BAB-433D-A6E3-25B2A40B9BD1@mac.com> <200710301015.13245.jhb@freebsd.org> X-Mailer: Apple Mail (2.912) Cc: John-Mark Gurney , freebsd-current@freebsd.org, current@freebsd.org Subject: Re: New-bus unit wiring via hints.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 17:38:56 -0000 On Oct 30, 2007, at 7:15 AM, John Baldwin wrote: >> That is not what I'm saying. What I'm saying is: >> If the firmware tells the OS that the port marked >> "1" on the back corresponds to a UART that has a >> base I/O port address of 0x2e8, then who are we >> to disagree and demand that it should be 0x3f8? > > That isn't what is happening though. The port marked "1" is at 0x3f8 > and happens to be "later" in the namespace than the port marked "2" > which is at 0x2e8. The BIOS may _optionally_ decide to communicate > this to the OS via the _UID method, but the _UID is only guaranteed > to be a string that it suitable for use in a label in a GUI dialog > box. Doesn't this imply that enumerating on the lexicographical ordering of the (optional) _UID method would help us do what firmware writers intend? In other words, we don't need a number. We just need a means to determine the relative order and we enumerate in that relative order. Isn't that how it is now (and if not shouldn't it be that way)? > Even if a PC has non-standard resources for COM1 and COM2, the serial > ports will show up as sio2 and sio3. This is another sio(4) bug that uart(4) doesn't have, yes :-) > Since you don't care what sio0 > means at all why not let other people who _do_ care have it work on > their > systems? "I" may not care what sio0 means, but that doesn't mean "I" don't care that "my" serial ports aren't numbered starting with 0. >> You rightly point out that what it really boils >> down to is how devX maps to a port on the back or >> front of the machine. This mapping should not >> change gratuitously. Device wiring achieves that. > > But on what basis will you wire things? Correcting the mapping of device instances to physical/visible ports will need to be based on user input. A default mapping, based on the self-enumerating ability of hardware/firmware, may not get it just right in all cases. But may provide a good and reliable starting point that may end up 90+% correct. > The only currently reliable > way I can see to wire things on x86 for an ISA device (and yes, the > COM port on a PC is ISA even if ACPI is what enumerates it rather than > PNPBIOS) is I/O resources or the name of the device in the ACPI > namespace (ACPI-only). I disagree. Since the firmware describes the legacy devices present in the system, the only reliable way is to trust that information. Sure, bugs may exist but 95+% of the FreeBSD code assumes correctness of hardware as it is, so why not in this respect? Anyway, when ACPI describes the hardware, I prefer not to call the legacy hardware ISA devices. It's important to make a clear distinction between enumerating and non-enumerating hardware, because that allows you to create mechanisms for dealing with non-enumerating hardware (i.e. hints) without creating conflicts or ambiguity with enumerating HW. We have convoluted this and mistakenly accepted this convolution as a property of ISA hardware. I've been advocating that our bus-abstraction is a good one. Devices enumerated by ACPI can be said to be attached to an ACPI bus. At least it's not more wrong than saying that they are ISA devices when it's obvious that there's no ISA bus to be found in modern hardware and all the legacy hardware is really on the chipsets LPC bus. > For uart console wiring you use I/O resources for > wiring even. Yes, but not "even". Since bus-enumeration hasn't happened yet, we can not describe the serial console by name+unit, because we have no way of knowing upfront what unit number will be assigned to the UART. The only way you can describe the serial console is by hardware resources or by firmware-level names (such as is the case on powerpc & sparc64). This is why using hints to "mark" the console is wrong. Note also that on ia64 (at least) ACPI tables exist that describe the serial console (and debug port) and those tables use hardware resources. So, the common denominator is I/O resources (even for OFW-based machines) and as it is, it's really the only thing you need (module hardware type) to make a low-level console work. The only correct way to identify hardware for use as low-level console is by it's location in I/O space (module hardware type). This is what uart(4) does and it's one of the reasons uart(4) works on all platforms even though low-level console support is highly machine dependent. It's the right way of doing it and as such it just works. Do not mistake low-level console identification with bus-enumeration device wiring or it being similar to hints. To re-iterate: We should reserve hints for describing non-enumerating hardware (which means device.hints should be non-existent OOTB) and we should add other mechanisms to wire devices to hardware, making use of the fact that underneath it mechanisms exist to enumerate the hardware (incl. hints for non-enumerating hardware). In the future we can replace hints with a more flexible and expressive means to describe hardware so that it better meets the needs of embedded environments and without it impacting device wiring. -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 18:06:22 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94CF716A417 for ; Tue, 30 Oct 2007 18:06:22 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (conducive.net [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id 1A30113C48E for ; Tue, 30 Oct 2007 18:06:22 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:63605 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1ImvTn-000AP5-Sj for freebsd-current@freebsd.org; Tue, 30 Oct 2007 18:06:20 +0000 Message-ID: <47277297.3030407@conducive.net> Date: Tue, 30 Oct 2007 14:06:15 -0400 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20071029190208.GD78150@bunrab.catwhisker.org> <4726A59F.4060002@cryptomonkeys.com> In-Reply-To: <4726A59F.4060002@cryptomonkeys.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: kernel panic in 7.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 18:06:22 -0000 Louis Kowolowski wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I've been getting these for about 2wks now. I see nothing in > /var/log/messages. System just hangs and the screen goes black. I'm in > X so I can't see what is on the console. If you redirect console messages in /etc/syslog.conf to /var/log/console.log, then tail -f that from a separate ssh login, you will not be as 'blind' to what is happening behind that 'X' screen. See also /var/log/messages, var/log/all.log & friends... Sometimes the culprit is even in /var/log/maillog. Overloaded SpamAssassin or such are just examples. Running top -SH in yet-another ssh session can't hurt, either.... Quite often a line or three of such log entries will tell the tale w/o the need for divining cores or dumps at all, and will at the least paint a picture as to what was going on immediately preceding the fault. HTH, Bill > I enabled crash dumps and I'm > pasting the lastest backtrace. Is there anything else I can provide? > > Thanks! > > 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-BETA1 #6: Thu Oct 25 15:58:10 PDT 2007 > root@dyn-2-201.pgp.com:/usr/obj/usr/src/sys/MONTEZUMA > Timecounter "i8254" frequency 1193167 Hz quality 0 > CPU: Intel(R) Core(TM)2 CPU T7600 @ 2.33GHz (2327.49-MHz > 686-class CPU) > Origin = "GenuineIntel" Id = 0x6f6 Stepping = 6 > > Features=0xbfebfbff > Features2=0xe3bd > AMD Features=0x20100000 > AMD Features2=0x1 > Cores per package: 2 > real memory = 3219980288 (3070 MB) > avail memory = 3145494528 (2999 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > ACPI Warning (tbfadt-0505): Optional field "Gpe1Block" has zero address > or length: 0 102C/0 [20070320] > ioapic0: Changing APIC ID to 1 > ioapic0 irqs 0-23 on motherboard > kbd1 at kbdmux0 > ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) > cryptosoft0: on motherboard > acpi0: on motherboard > acpi0: [ITHREAD] > acpi_ec0: port 0x62,0x66 on acpi0 > acpi0: Power Button (fixed) > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, bff00000 (3) failed > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 > acpi_hpet0: iomem 0xfed00000-0xfed003ff on > acpi0 > Timecounter "HPET" frequency 14318180 Hz quality 900 > cpu0: on acpi0 > est0: on cpu0 > p4tcc0: on cpu0 > cpu1: on acpi0 > est1: on cpu1 > p4tcc1: on cpu1 > acpi_lid0: on acpi0 > acpi_button0: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pcib1: irq 16 at device 1.0 on pci0 > pci1: on pcib1 > vgapci0: port 0x2000-0x20ff mem > 0xd0000000-0xdfffffff,0xee100000-0xee10ffff irq 16 at device 0.0 on pci1 > pcm0: mem > 0xee400000-0xee403fff irq 17 at device 27.0 on pci0 > pcm0: [ITHREAD] > pcib2: irq 20 at device 28.0 on pci0 > pci2: on pcib2 > em0: port > 0x3000-0x301f mem 0xee000000-0xee01ffff irq 16 at device 0.0 on pci2 > em0: Ethernet address: 00:16:41:58:25:48 > em0: [ITHREAD] > pcib3: irq 21 at device 28.1 on pci0 > pci3: on pcib3 > ath0: mem 0xedf00000-0xedf0ffff irq 17 at device 0.0 on pci3 > ath0: [ITHREAD] > ath0: using obsoleted if_watchdog interface > ath0: Ethernet address: 00:16:cf:7b:0d:0d > ath0: mac 10.3 phy 6.1 radio 10.2 > pcib4: irq 22 at device 28.2 on pci0 > pci4: on pcib4 > pcib5: irq 23 at device 28.3 on pci0 > pci12: on pcib5 > uhci0: port 0x1800-0x181f irq 16 at > device 29.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 0x1820-0x183f irq 17 at > device 29.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 > uhci2: port 0x1840-0x185f irq 18 at > device 29.2 on pci0 > uhci2: [GIANT-LOCKED] > uhci2: [ITHREAD] > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: on usb2 > uhub2: 2 ports with 2 removable, self powered > uhci3: port 0x1860-0x187f irq 19 at > device 29.3 on pci0 > uhci3: [GIANT-LOCKED] > uhci3: [ITHREAD] > usb3: on uhci3 > usb3: USB revision 1.0 > uhub3: on usb3 > uhub3: 2 ports with 2 removable, self powered > ehci0: mem > 0xee404000-0xee4043ff irq 19 at device 29.7 on pci0 > ehci0: [GIANT-LOCKED] > ehci0: [ITHREAD] > usb4: EHCI version 1.0 > usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 > usb4: on ehci0 > usb4: USB revision 2.0 > uhub4: on usb4 > uhub4: 8 ports with 8 removable, self powered > pcib6: at device 30.0 on pci0 > pci21: on pcib6 > cbb0: mem 0xe4300000-0xe4300fff irq 16 at > device 0.0 on pci21 > cardbus0: on cbb0 > pccard0: <16-bit PCCard bus> on cbb0 > cbb0: [ITHREAD] > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1880-0x188f at device 31.1 on pci0 > ata0: on atapci0 > ata0: [ITHREAD] > ata1: on atapci0 > ata1: [ITHREAD] > atapci1: port > 0x18c8-0x18cf,0x18ac-0x18af,0x18c0-0x18c7,0x18a8-0x18ab,0x18b0-0x18bf > mem 0xee404400-0xee4047ff irq 16 at device 31.2 on pci0 > atapci1: [ITHREAD] > atapci1: AHCI Version 01.10 controller with 4 ports detected > ata2: on atapci1 > ata2: [ITHREAD] > ata3: on atapci1 > ata3: port not implemented > ata3: [ITHREAD] > ata4: on atapci1 > ata4: port not implemented > ata4: [ITHREAD] > ata5: on atapci1 > ata5: port not implemented > ata5: [ITHREAD] > pci0: at device 31.3 (no driver attached) > acpi_tz0: on acpi0 > acpi_tz1: on acpi0 > speaker0: port 0x61 on acpi0 > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > 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 Generic PS/2 mouse, device ID 0 > sio0: configured irq 3 not in bitmap of probed irqs 0 > sio0: port may not be enabled > battery0: on acpi0 > acpi_acad0: on acpi0 > acpi_ibm0: on acpi0 > sio0: configured irq 3 not in bitmap of probed irqs 0 > sio0: port may not be enabled > pmtimer0 on isa0 > orm0: at iomem > 0xc0000-0xcffff,0xd0000-0xd0fff,0xd1000-0xd1fff,0xdc000-0xdffff,0xe0000-0xeffff > pnpid ORM0000 on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > 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 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 8250 or not responding > sio0: [FILTER] > 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 > ugen0: on uhub3 > ugen1: 1.00/0.01, addr 3> on uhub3 > NULL mp in getnewvnode() > Timecounters tick every 1.000 msec > ad0: 238475MB at ata0-master UDMA100 > ad4: 238475MB at ata2-master SATA150 > pcm0: > pcm0: > SMP: AP CPU #1 Launched! > Trying to mount root from ufs:/dev/ad4s1a > > > kgdb output: > > [GDB will not be able to debug user-mode threads: > /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-marcel-freebsd". > > Unread portion of the kernel message buffer: > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x0 > fault code = supervisor write, page not present > instruction pointer = 0x20:0xc0712901 > stack pointer = 0x28:0xe8e88824 > frame pointer = 0x28:0xe8e88850 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 1437 (gkrellm) > trap number = 12 > panic: page fault > cpuid = 0 > Uptime: 5h5m16s > Physical memory: 3058 MB > Dumping 153 MB: 138 122 106 90 74 58 42 26 10 > > #0 doadump () at pcpu.h:195 > 195 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); > (kgdb) backtrace > #0 doadump () at pcpu.h:195 > #1 0xc07461aa in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409 > #2 0xc074649c in panic (fmt=Variable "fmt" is not available. > ) at /usr/src/sys/kern/kern_shutdown.c:563 > #3 0xc0a26704 in trap_fatal (frame=0xe8e887e4, eva=0) > at /usr/src/sys/i386/i386/trap.c:872 > #4 0xc0a26975 in trap_pfault (frame=0xe8e887e4, usermode=0, eva=0) > at /usr/src/sys/i386/i386/trap.c:785 > #5 0xc0a272c1 in trap (frame=0xe8e887e4) at > /usr/src/sys/i386/i386/trap.c:463 > #6 0xc0a0e33b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 > #7 0xc0712901 in clone_create (cdp=0xc0db3f74, csw=0xc0db2fa0, > up=0xe8e88874, > dp=0xe8e88940, extra=0) at /usr/src/sys/kern/kern_conf.c:938 > #8 0xc0da3eae in ?? () > #9 0xc0db3f74 in ?? () > #10 0xc0db2fa0 in ?? () > #11 0xe8e88874 in ?? () > #12 0xe8e88940 in ?? () > #13 0x00000000 in ?? () > #14 0xc0ab29b5 in ?? () > #15 0xc0d3511e in ?? () > #16 0xffffffff in ?? () > #17 0xc0da3e48 in ?? () > #18 0xc66e4400 in ?? () > #19 0xe8e88950 in ?? () > #20 0xc06e0adc in devfs_lookup (ap=0x0) > at /usr/src/sys/fs/devfs/devfs_vnops.c:627 > Previous frame identical to this frame (corrupt stack?) > (kgdb) > > - -- > > Louis Kowolowski louisk@cryptomonkeys.com > Cryptomonkeys: http://www.cryptomonkeys.com/~louisk > > Everyone is a genius. It's just that some people are too stupid to > realize it. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.4 (FreeBSD) > > iD8DBQFHJqWeZk0r6oAkN7YRAiUOAJsEzMjvY/e2rKFPP6/w4pQVh7NIGQCfRp39 > 18ZPUy4iDgE1hJ7KC8QXs7c= > =kHMs > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 18:34:10 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 751D016A418 for ; Tue, 30 Oct 2007 18:34:10 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (conducive.net [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id 3E20E13C4C1 for ; Tue, 30 Oct 2007 18:34:10 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:63635 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1Imvu7-000AST-Sj for freebsd-current@freebsd.org; Tue, 30 Oct 2007 18:33:31 +0000 Message-ID: <472778F7.9030405@conducive.net> Date: Tue, 30 Oct 2007 14:33:27 -0400 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <4725558F.6040702@fusiongol.com> <4726BEEE.3070704@yandex.ru> In-Reply-To: <4726BEEE.3070704@yandex.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Problem with ATAPI device on JMicron JMB363 on 7.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 18:34:10 -0000 Andrey V. Elsukov wrote: > Nathan Butcher wrote: >> I have a Gigabyte GA-G33-DS3R. FreeBSD 7.0-BETA1 detects the chipset, >> but no devices attached to the SATA controllers find their relative /dev >> entries. My SATA DVD-combo drive simply doesn't get /dev/acd0, and as a >> result I cannot access the drive. I've tried hard drives too, with the >> same results. > > You can update your BETA1 to the fresh RELENG_7. Soren have fixed this > issue. Also, ATAPI support was added to the AHCI driver (only for > CURRENT yet). > >> The IDE interface seems to work for me (I have an IDE -> CF converter in >> there), but I don't have a PATA optical drive to test. > There seem to also be certain 'proprietary' (I hope...) issues with that MB BIOS. We had tested combinations of BIOS settings extensively, using PATA CDR, PATA HDD, PATA <==> SATA converters, and SATA HDD - even an aged IDE Zip. To cut to the chase - When finished, we attached 2 SATA drives (only), wherein they appeared as /dev/ad10 and /dev/ad12, despite using the lower-numbered silkscreened-labeled SATA ports. Further tuning had us move from all IDE/ legacy BIOS settings to attempt AHCI enabling after a recent csup & makebuild* Nothing to do with FreeBSD - as we were unable to get out of the BIOS POST OR into 'setup'. Board hung-forever in the part where it tries to detect drives. BUT - after a screwdriver-blade CMOS clear, then BIOS reset to the *same* conservative/legacy settings as used with ad10 / ad12 ..what had been ad10 and ad12 appeared as ad0 and ad2 And gmirror complaineth not (thanks, PHK, PJD and others!) Bottom Line: BIOS is 'suboptimal', to put it kindly, and a CMOS reset is worthwhile before going further. HTH, Bill Hacker > For Vladimir: > here is a description for your issue (russian) > http://unix1.jinr.ru/~lavr/cd_dvd_intel965.html > From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 18:51:53 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E282C16A417 for ; Tue, 30 Oct 2007 18:51:53 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id 9EC1313C4AA for ; Tue, 30 Oct 2007 18:51:53 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8p) with ESMTP id 216938350-1834499 for multiple; Tue, 30 Oct 2007 13:51:21 -0500 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l9UIp4kJ082836; Tue, 30 Oct 2007 14:51:04 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Marcel Moolenaar Date: Tue, 30 Oct 2007 13:48:47 -0400 User-Agent: KMail/1.9.6 References: <20071027212420.EC7F94500E@ptavv.es.net> <200710301015.13245.jhb@freebsd.org> <4B6E9989-28E0-4C73-8F0C-20BB009FAAA7@mac.com> In-Reply-To: <4B6E9989-28E0-4C73-8F0C-20BB009FAAA7@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710301348.48031.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Tue, 30 Oct 2007 14:51:04 -0400 (EDT) X-Virus-Scanned: ClamAV 0.91.2/4640/Tue Oct 30 12:45:18 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: John-Mark Gurney , freebsd-current@freebsd.org Subject: Re: New-bus unit wiring via hints.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 18:51:54 -0000 On Tuesday 30 October 2007 01:07:44 pm Marcel Moolenaar wrote: > > On Oct 30, 2007, at 7:15 AM, John Baldwin wrote: > > >> That is not what I'm saying. What I'm saying is: > >> If the firmware tells the OS that the port marked > >> "1" on the back corresponds to a UART that has a > >> base I/O port address of 0x2e8, then who are we > >> to disagree and demand that it should be 0x3f8? > > > > That isn't what is happening though. The port marked "1" is at 0x3f8 > > and happens to be "later" in the namespace than the port marked "2" > > which is at 0x2e8. The BIOS may _optionally_ decide to communicate > > this to the OS via the _UID method, but the _UID is only guaranteed > > to be a string that it suitable for use in a label in a GUI dialog > > box. > > Doesn't this imply that enumerating on the lexicographical ordering > of the (optional) _UID method would help us do what firmware writers > intend? > > In other words, we don't need a number. We just need a means to > determine the relative order and we enumerate in that relative > order. Isn't that how it is now (and if not shouldn't it be that > way)? No. They are strings that have no implied ordering. > > Even if a PC has non-standard resources for COM1 and COM2, the serial > > ports will show up as sio2 and sio3. > > This is another sio(4) bug that uart(4) doesn't have, yes :-) Hmmm, I don't think you parsed what I meant, but maybe you mean that uart(4) doesn't have the poorly-implemented "feature" in sio(4) to make sure that all non-ISA serial ports start at unit 2 to "reserve" sio0 and sio1 for COM1 and COM2? Just look in sio_pci.c for 'device_set_unit()' which the current wiring patches remove with a vengance by making hints always reserve a given (name, unit) tuple. > > Since you don't care what sio0 > > means at all why not let other people who _do_ care have it work on > > their > > systems? > > "I" may not care what sio0 means, but that doesn't mean "I" don't > care that "my" serial ports aren't numbered starting with 0. And you could have an empty hints file and be happy. > >> You rightly point out that what it really boils > >> down to is how devX maps to a port on the back or > >> front of the machine. This mapping should not > >> change gratuitously. Device wiring achieves that. > > > > But on what basis will you wire things? > > Correcting the mapping of device instances to physical/visible > ports will need to be based on user input. A default mapping, > based on the self-enumerating ability of hardware/firmware, may > not get it just right in all cases. But may provide a good and > reliable starting point that may end up 90+% correct. Oof. See, here is where I think we hit a snag. :( I'm thinking in terms of automated installations to a wide variety of server boxes that don't have a GUI with a mouse and monitor hooked up so a user can clicky-clicky to set which serial port is sio0. :( > > The only currently reliable > > way I can see to wire things on x86 for an ISA device (and yes, the > > COM port on a PC is ISA even if ACPI is what enumerates it rather than > > PNPBIOS) is I/O resources or the name of the device in the ACPI > > namespace (ACPI-only). > > I disagree. Since the firmware describes the legacy devices present > in the system, the only reliable way is to trust that information. > Sure, bugs may exist but 95+% of the FreeBSD code assumes correctness > of hardware as it is, so why not in this respect? You've missed the point of this entirely then. :( Yes, the firmware is authoritative, and part of the goal is to fix a long-standing weakness where the OS is presented with two different enumerations of hardware: one supplied by the user via hints and one supplied by the firmware. The idea is to trust the firmware's notion of resources since it probably knows better while allowing for other non-resource information provided by the user to be tied to the correct piece of hardware. > Anyway, when ACPI describes the hardware, I prefer not to call the > legacy hardware ISA devices. It's important to make a clear distinction > between enumerating and non-enumerating hardware, because that allows > you to create mechanisms for dealing with non-enumerating hardware (i.e. > hints) without creating conflicts or ambiguity with enumerating HW. > We have convoluted this and mistakenly accepted this convolution as a > property of ISA hardware. > > I've been advocating that our bus-abstraction is a good one. Devices > enumerated by ACPI can be said to be attached to an ACPI bus. At least > it's not more wrong than saying that they are ISA devices when it's > obvious that there's no ISA bus to be found in modern hardware and all > the legacy hardware is really on the chipsets LPC bus. You continue to ignore that ACPI is not just a simple bus, but is a namespace that enumerates devices on multiple busses such as ISA/LPC, SMBus (e.g. an IPMI SSIF interface can be enumerated via ACPI), etc. It is much more generic than just an ISA enumerator like PNPBIOS. > > For uart console wiring you use I/O resources for > > wiring even. > > Yes, but not "even". Since bus-enumeration hasn't happened yet, > we can not describe the serial console by name+unit, because we > have no way of knowing upfront what unit number will be assigned > to the UART. The only way you can describe the serial console > is by hardware resources or by firmware-level names (such as is > the case on powerpc & sparc64). > > This is why using hints to "mark" the console is wrong. > > Note also that on ia64 (at least) ACPI tables exist that describe > the serial console (and debug port) and those tables use hardware > resources. So, the common denominator is I/O resources (even for > OFW-based machines) and as it is, it's really the only thing you > need (module hardware type) to make a low-level console work. > > The only correct way to identify hardware for use as low-level > console is by it's location in I/O space (module hardware type). > This is what uart(4) does and it's one of the reasons uart(4) > works on all platforms even though low-level console support is > highly machine dependent. It's the right way of doing it and > as such it just works. > > Do not mistake low-level console identification with bus-enumeration > device wiring or it being similar to hints. > > To re-iterate: > We should reserve hints for describing non-enumerating hardware > (which means device.hints should be non-existent OOTB) and we > should add other mechanisms to wire devices to hardware, making > use of the fact that underneath it mechanisms exist to enumerate > the hardware (incl. hints for non-enumerating hardware). In the > future we can replace hints with a more flexible and expressive > means to describe hardware so that it better meets the needs of > embedded environments and without it impacting device wiring. So what do you want: 'wire.sio.0.*?' Or do you want XML or some binary registery like Windows that can't be modified by the user w/o first booting the OS (which is real handy when it gets corrupted). Right now the current "solution" results in various places (like my employer) just turning off the ACPI support for sio(4) because hints are more reliable for us than ACPI when it comes to enumerating serial ports in _real_ _world_ _x86_ server-class machines. I'd much rather be trusting ACPI myself hence my attempts to make the two sets of information enumerating the same hardware agree on what they are talking about. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 18:54:58 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34C6016A419 for ; Tue, 30 Oct 2007 18:54:58 +0000 (UTC) (envelope-from rivers@dignus.com) Received: from dignus.com (mail.dignus.com [209.42.196.2]) by mx1.freebsd.org (Postfix) with ESMTP id 8BBB313C4B5 for ; Tue, 30 Oct 2007 18:54:57 +0000 (UTC) (envelope-from rivers@dignus.com) Received: from lakes.dignus.com (lakes.dignus.com [10.1.0.3]) by dignus.com (8.13.1/8.13.1) with ESMTP id l9UIWK8h038356 for ; Tue, 30 Oct 2007 14:32:20 -0400 (EDT) (envelope-from rivers@dignus.com) Received: (from rivers@localhost) by lakes.dignus.com (8.11.6/8.11.3) id l9UIYeW55836 for freebsd-current@freebsd.org; Tue, 30 Oct 2007 14:34:40 -0400 (EDT) (envelope-from rivers) Date: Tue, 30 Oct 2007 14:34:40 -0400 (EDT) From: Thomas David Rivers Message-Id: <200710301834.l9UIYeW55836@lakes.dignus.com> To: freebsd-current@freebsd.org X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on office.dignus.com Subject: 7.0 BETA1.5 initial findings... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 18:54:58 -0000 Just wanted to report some of my results with installing the BETA1.5 CDs.... with a CD-ONLY install. This is on an Intel quad-core with 2G of memory, and 300G SATA drive and older ATAPI DVD drive (Intel DG33BU motherboard.) First; after you partition & label and choose your distributions; it's time to remove the "BOOTONLY" CD and place DISC1 in the drive. There's nothing that tells you this.. if you don't do this, then the process merrily fails at trying to install everything.. twice over. After that, you have an opportunity to try and install again, putting DISC1 in the drive. I'd suggest a little box saying "remove the BOOTONLY CD, insert DISC1 and press OK" when it's time to start installing the distributions. Second - if you choose the X11 packages in the distributions; they don't work. The install process complains that it can't find packages/INDEX on either DISC1 or DISK2. I'm not sure how to get the X11 packages installed from a CD-only install. - Dave Rivers - -- Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 18:56:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F7A416A41B for ; Tue, 30 Oct 2007 18:56:18 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id C186E13C4B7; Tue, 30 Oct 2007 18:56:17 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47277E55.5060104@FreeBSD.org> Date: Tue, 30 Oct 2007 19:56:21 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Christoph Friedrichs References: <47270246.4020400@helinet.de> In-Reply-To: <47270246.4020400@helinet.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Problem with libthr after update X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 18:56:18 -0000 Christoph Friedrichs wrote: > Hi Guys, > > I?m relatively new with my freebsd -current box and actual experiencing > problems with starting kdm and portupgrade. Everytime I do so the > kdm-bin log explodes with this error messages: > > Fatal error 'Cannot allocate red zone for initial thread' at line 382 in > file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) > Fatal error 'Cannot allocate red zone for initial thread' at line 382 in > file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) > Fatal error 'Cannot allocate red zone for initial thread' at line 382 in > file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) > > I googled this problem and found something concering some ruby packages. > I did a manual rebuild of > > ruby-1.8.6_2,1 > perl-5.8.8 > ruby18-bdb-0.6.2 > db41-4.1.25_4 > portupgrade-2.3.1,2 > > With this rebuild problems with portupgrade were solved but kdm keeps > refusing to start with same error messages. In UPDATING I found this: > > 20071009: > Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and > WITHOUT_LIBTHR are set. > > Does this probably have something to do with this? Did you update from an older release of FreeBSD? Kris From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 18:58:09 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B306216A41A; Tue, 30 Oct 2007 18:58:09 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id 156CA13C4A5; Tue, 30 Oct 2007 18:58:08 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47277EC4.4030003@FreeBSD.org> Date: Tue, 30 Oct 2007 19:58:12 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: "Ralf S. Engelschall" References: <20071029110204.GA64046@engelschall.com> In-Reply-To: <20071029110204.GA64046@engelschall.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: "sigreturn: eflags = 0x80283" after medium-to-high load X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 18:58:09 -0000 Ralf S. Engelschall wrote: > Just FYI: When I compile lots of C++ code under 8.0 or 7.0 (both as of > 2007-10-27 and running on ZFS inside a virtual machine) I'm still able > to regularily bring the system into an unusable state. The effect is > that first on the console the following kernel messages occur: > > sigreturn: eflags = 0x80283 > sigreturn: eflags = 0x80297 > > Then after I type e.g. CTRL-C in my C++ compile session over SSH more > such "sigreturn: eflags = 0x80283" occur on the console (and without > bringing back a shell prompt on the SSH session). At this stage I also > no longer can login via SSH through a new second SSH connection. Only on > the console I still can perform a "sync; sync; sync; reboot" to rescue. > In this situation even a regular "shutdown -r now" often just causes > more "sigreturn: eflags = 0x80297" outputs but isn't really able to > finally reboot the system. Sounds like you need to do some debugging with DDB to identify the system state when it hangs. Kris From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 20:00:37 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 78FD716A417; Tue, 30 Oct 2007 20:00:37 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.79]) by mx1.freebsd.org (Postfix) with ESMTP id 60B7313C4B8; Tue, 30 Oct 2007 20:00:37 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (asmtp008-s [10.150.69.71]) by smtpoutm.mac.com (Xserve/smtpout016/MantshX 4.0) with ESMTP id l9UK0atT001629; Tue, 30 Oct 2007 13:00:36 -0700 (PDT) Received: from macbook-pro.jnpr.net (natint3.juniper.net [66.129.224.36]) (authenticated bits=0) by mac.com (Xserve/asmtp008/MantshX 4.0) with ESMTP id l9UK0TXB008126 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 30 Oct 2007 13:00:30 -0700 (PDT) Message-Id: From: Marcel Moolenaar To: John Baldwin In-Reply-To: <200710301348.48031.jhb@freebsd.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v912) Date: Tue, 30 Oct 2007 13:00:28 -0700 References: <20071027212420.EC7F94500E@ptavv.es.net> <200710301015.13245.jhb@freebsd.org> <4B6E9989-28E0-4C73-8F0C-20BB009FAAA7@mac.com> <200710301348.48031.jhb@freebsd.org> X-Mailer: Apple Mail (2.912) Cc: John-Mark Gurney , freebsd-current@freebsd.org Subject: Re: New-bus unit wiring via hints.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 20:00:37 -0000 On Oct 30, 2007, at 10:48 AM, John Baldwin wrote: >>> That isn't what is happening though. The port marked "1" is at >>> 0x3f8 >>> and happens to be "later" in the namespace than the port marked "2" >>> which is at 0x2e8. The BIOS may _optionally_ decide to communicate >>> this to the OS via the _UID method, but the _UID is only guaranteed >>> to be a string that it suitable for use in a label in a GUI dialog >>> box. >> >> Doesn't this imply that enumerating on the lexicographical ordering >> of the (optional) _UID method would help us do what firmware writers >> intend? >> >> In other words, we don't need a number. We just need a means to >> determine the relative order and we enumerate in that relative >> order. Isn't that how it is now (and if not shouldn't it be that >> way)? > > No. They are strings that have no implied ordering. Then there's no problem, for if _UID is designed as a user-visible label and there's no ordering then no-one can claim that one is to be before the other and thus that the logical ordering in the AML is in fact the right ordering. This of course means that the user can see COM2 before COM1 in some user-interface. This of course is exactly in accordance with the firmware and as such correct. >>> Even if a PC has non-standard resources for COM1 and COM2, the >>> serial >>> ports will show up as sio2 and sio3. >> >> This is another sio(4) bug that uart(4) doesn't have, yes :-) > > Hmmm, I don't think you parsed what I meant, but maybe you mean that > uart(4) > doesn't have the poorly-implemented "feature" in sio(4) to make sure > that all > non-ISA serial ports start at unit 2 to "reserve" sio0 and sio1 for > COM1 and > COM2? Exactly. > Just look in sio_pci.c for 'device_set_unit()' which the current > wiring patches remove with a vengance by making hints always reserve > a given > (name, unit) tuple. And since hints are shipped by us with default values, what we did is remove the poorly-implemented "feature" from sio(4) only to bank on hints to yield the same result, which makes hints nothing more than a different poorly-implemented "feature" :-) >>> Since you don't care what sio0 >>> means at all why not let other people who _do_ care have it work on >>> their >>> systems? >> >> "I" may not care what sio0 means, but that doesn't mean "I" don't >> care that "my" serial ports aren't numbered starting with 0. > > And you could have an empty hints file and be happy. With the exception of course of having an OS that does the wrong thing OOTB and that requires extensive fiddling to behave correctly, increasing the amount of maintenance and upgrade hassle. >>>> You rightly point out that what it really boils >>>> down to is how devX maps to a port on the back or >>>> front of the machine. This mapping should not >>>> change gratuitously. Device wiring achieves that. >>> >>> But on what basis will you wire things? >> >> Correcting the mapping of device instances to physical/visible >> ports will need to be based on user input. A default mapping, >> based on the self-enumerating ability of hardware/firmware, may >> not get it just right in all cases. But may provide a good and >> reliable starting point that may end up 90+% correct. > > Oof. See, here is where I think we hit a snag. :( I'm thinking in > terms of > automated installations to a wide variety of server boxes that don't > have > a GUI with a mouse and monitor hooked up so a user can clicky-clicky > to set > which serial port is sio0. :( I don't see a snag. But maybe that's because I use uart(4) on my machines and I have a serial consoles no matter how things are enumerated... >>> The only currently reliable >>> way I can see to wire things on x86 for an ISA device (and yes, the >>> COM port on a PC is ISA even if ACPI is what enumerates it rather >>> than >>> PNPBIOS) is I/O resources or the name of the device in the ACPI >>> namespace (ACPI-only). >> >> I disagree. Since the firmware describes the legacy devices present >> in the system, the only reliable way is to trust that information. >> Sure, bugs may exist but 95+% of the FreeBSD code assumes correctness >> of hardware as it is, so why not in this respect? > > You've missed the point of this entirely then. :( Yes, the firmware > is > authoritative, and part of the goal is to fix a long-standing > weakness where > the OS is presented with two different enumerations of hardware: one > supplied > by the user via hints and one supplied by the firmware. The "weakness" you mention is really the OSes own failure by "presenting" itself with hardware information that has no relation to the machine that it runs on, because it's actually fixated by virtue of being part of the OSes source code. It isn't supplied by the user at all. We supply it to ourselves. Don't go blaming the user for that... > The idea is to trust > the firmware's notion of resources since it probably knows better > while > allowing for other non-resource information provided by the user to > be tied > to the correct piece of hardware. Agreed... He, that's what I said previously and you responded to with saying that we hit a snag. I guess we don't then; or do we? I'm confused now :-) >> Anyway, when ACPI describes the hardware, I prefer not to call the >> legacy hardware ISA devices. It's important to make a clear >> distinction >> between enumerating and non-enumerating hardware, because that allows >> you to create mechanisms for dealing with non-enumerating hardware >> (i.e. >> hints) without creating conflicts or ambiguity with enumerating HW. >> We have convoluted this and mistakenly accepted this convolution as a >> property of ISA hardware. >> >> I've been advocating that our bus-abstraction is a good one. Devices >> enumerated by ACPI can be said to be attached to an ACPI bus. At >> least >> it's not more wrong than saying that they are ISA devices when it's >> obvious that there's no ISA bus to be found in modern hardware and >> all >> the legacy hardware is really on the chipsets LPC bus. > > You continue to ignore that ACPI is not just a simple bus, but is a > namespace > that enumerates devices on multiple busses such as ISA/LPC, SMBus > (e.g. an > IPMI SSIF interface can be enumerated via ACPI), etc. It is much more > generic than just an ISA enumerator like PNPBIOS. No, I don't ignore anything. I explicitly and deliberately use the term "abstraction". It's a simplified representation of reality. An "idea". My choice of calling ACPI a bus is probably what confuses you. I'm fully aware that it is much more than a bus, but it still "quacks" like one WRT legacy hardware... >>> For uart console wiring you use I/O resources for >>> wiring even. >> >> Yes, but not "even". Since bus-enumeration hasn't happened yet, >> we can not describe the serial console by name+unit, because we >> have no way of knowing upfront what unit number will be assigned >> to the UART. The only way you can describe the serial console >> is by hardware resources or by firmware-level names (such as is >> the case on powerpc & sparc64). >> >> This is why using hints to "mark" the console is wrong. >> >> Note also that on ia64 (at least) ACPI tables exist that describe >> the serial console (and debug port) and those tables use hardware >> resources. So, the common denominator is I/O resources (even for >> OFW-based machines) and as it is, it's really the only thing you >> need (module hardware type) to make a low-level console work. >> >> The only correct way to identify hardware for use as low-level >> console is by it's location in I/O space (module hardware type). >> This is what uart(4) does and it's one of the reasons uart(4) >> works on all platforms even though low-level console support is >> highly machine dependent. It's the right way of doing it and >> as such it just works. >> >> Do not mistake low-level console identification with bus-enumeration >> device wiring or it being similar to hints. >> >> To re-iterate: >> We should reserve hints for describing non-enumerating hardware >> (which means device.hints should be non-existent OOTB) and we >> should add other mechanisms to wire devices to hardware, making >> use of the fact that underneath it mechanisms exist to enumerate >> the hardware (incl. hints for non-enumerating hardware). In the >> future we can replace hints with a more flexible and expressive >> means to describe hardware so that it better meets the needs of >> embedded environments and without it impacting device wiring. > > So what do you want: 'wire.sio.0.*?' Or do you want XML or some > binary > registery like Windows that can't be modified by the user w/o first > booting > the OS (which is real handy when it gets corrupted). What I want is something that is appropriate. If we want to wire hardware to devices, then we need to be able to uniquely identify a device in hardware. A path if you will that mentions busses, bridges devices and functions therein. Look at ACPI, EFI and OFW for example. Such an identification is the keying entity. Data that corresponds to that key can be complex or compound so that you can actually specify which driver you want to use above and beyond simply wiring it to a unit number. This also also allows us to add other pieces of information. I'm not going to give concrete examples, because I foresee that the discussion will then be about how my "solution" sucks rather than it being treated for what it is: an illustration -- something to explain what I said and in no way complete or even usable. Ok, what the heck. For better or for worse: \begin{/boot/hardware.conf} # Lines starting with '#' are comments [pci0.0.18.0] # First function: standard UART # We use this for remote GDB driver="sio" unit=2 dbgport="9600,n,8,1" [pci0.0.18.1] # Second function: standard but memory-mapped UART # doesn't work with sio(4) -- needs uart(4) # We use this one as console. driver="uart" unit=3 console="115200,n,8,1" \end{/boot/hardware.conf} Don't get confused about marking the hardware as console or debug port and how we do the same in hints. It isn't the same. Hints mark the driver instance as console or debug port. Here I mark the *hardware* as console or debug port, even if we don't wish to wire it to a driver instance (although we do in the example) Fundamentally different! > Right now the current "solution" results in various places (like my > employer) > just turning off the ACPI support for sio(4) because hints are more > reliable > for us than ACPI when it comes to enumerating serial ports in _real_ > _world_ > _x86_ server-class machines. Use uart(4)? -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 20:34:02 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FD1A16A417 for ; Tue, 30 Oct 2007 20:34:02 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id ACBAA13C4C5 for ; Tue, 30 Oct 2007 20:33:50 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 3489 invoked from network); 30 Oct 2007 23:33:44 +0300 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 30 Oct 2007 23:33:44 +0300 X-AntiVirus: Checked by Dr.Web [version: 4.44, engine: 4.44.0.09170, virus records: 252594, updated: 30.10.2007] Message-ID: <001101c81b34$283e4cc0$0c00a8c0@Artem> From: "Artem Kuchin" To: Date: Tue, 30 Oct 2007 23:33:32 +0300 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="koi8-r"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Subject: wrong sector count in dumpfs -m newfs -s arg X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 20:34:02 -0000 Here it is /dev/twed0s1f is 199 636 542 1K blocks in size osiris#dumpfs -m /dev/twed0s1f # newfs command for /dev/twed0s1f (/dev/twed0s1f) newfs -O 2 -U -a 8 -b 16384 -d 16384 -e 2048 -f 2048 -g 16384 -h 64 -m 8 -o time -s 103062480 /dev/twed0s1f osiris# geom disk list Geom name: twed0 Providers: 1. Name: twed0 Mediasize: 240066101248 (224G) Sectorsize: 512 Mode: r5w5e6 fwsectors: 63 fwheads: 255 As you see the sector size is 512. newfs from dumpfs -s arg says this fs is 103062480 sectors long 512*103062480= 52 767 989 760 bytes or 51 531 240 in 1K blocks And i thought it should be exactly he size of the filesystem. Any idea what's up with this? -- Artem From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 20:50:26 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0C5216A41B; Tue, 30 Oct 2007 20:50:26 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id 033EA13C4C6; Tue, 30 Oct 2007 20:50:21 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47279910.5080909@FreeBSD.org> Date: Tue, 30 Oct 2007 21:50:24 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: d@delphij.net References: <20070917194009.W84177@woozle.rinet.ru> <200709171912.09060.qpadla@gmail.com> <46EEA89F.3060606@delphij.net> <200709241223.52140.qpadla@gmail.com> <472561A7.60108@delphij.net> In-Reply-To: <472561A7.60108@delphij.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: MingyanGuo , current@freebsd.org, Dmitry Morozovsky , freebsd-current@freebsd.org, delphij@freebsd.org, Howard Su Subject: Re: tmpfs on contemporary -current: panic: locked against myself X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 20:50:27 -0000 LI Xin wrote: > Nikolay Pavlov wrote: >> On Monday 17 September 2007 19:17:35 LI Xin wrote: >>> Nikolay Pavlov wrote: >>> [...] >>> >>>> Yes it's still need more fixes. I have send a mail to delphij >>>> regarding this one panic: >>>> http://docs.freebsd.org/cgi/mid.cgi?200708201848.22157.qpadla >>>> But with out any response. May be he is busy :( >>> Sorry I am aware of the issue and am busy for $REALJOB these days. I >>> have cc'ed howardsu@ and mingyanguo@ to see if they have some >>> suggestions. The problem seems to be a race condition caused by >>> incorrect VFS related locking, but diagnosing it is relatively hard. >>> >>> I'll try to pick up with the development in early October. Before that >>> I can only do some small scale bugfixes rather than investing more time >>> into tmpfs stuff... :-( >>> >>> Cheers, >> Just want to be sure that no one lose this. Here is a PR: >> http://www.freebsd.org/cgi/query-pr.cgi?pr=116600 > > Can not reproduce here. Could you please confirm that this still > persists for latest RELENG_7? > > Cheers, I don't know about that one, but I am able to get this panic still after a few seconds of load: panic: Assertion IMPLIES(dnode->tn_type == VDIR && dnode->tn_dir.tn_parent == dnode, !(cnp->cn_flags & ISDOTDOT)) failed at ../../../fs/tmpfs/tmpfs_vnops.c:97 If you can fix that I can look for the other one :) Kris From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 20:50:26 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0C5216A41B; Tue, 30 Oct 2007 20:50:26 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id 033EA13C4C6; Tue, 30 Oct 2007 20:50:21 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47279910.5080909@FreeBSD.org> Date: Tue, 30 Oct 2007 21:50:24 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: d@delphij.net References: <20070917194009.W84177@woozle.rinet.ru> <200709171912.09060.qpadla@gmail.com> <46EEA89F.3060606@delphij.net> <200709241223.52140.qpadla@gmail.com> <472561A7.60108@delphij.net> In-Reply-To: <472561A7.60108@delphij.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: MingyanGuo , current@freebsd.org, Dmitry Morozovsky , freebsd-current@freebsd.org, delphij@freebsd.org, Howard Su Subject: Re: tmpfs on contemporary -current: panic: locked against myself X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 20:50:27 -0000 LI Xin wrote: > Nikolay Pavlov wrote: >> On Monday 17 September 2007 19:17:35 LI Xin wrote: >>> Nikolay Pavlov wrote: >>> [...] >>> >>>> Yes it's still need more fixes. I have send a mail to delphij >>>> regarding this one panic: >>>> http://docs.freebsd.org/cgi/mid.cgi?200708201848.22157.qpadla >>>> But with out any response. May be he is busy :( >>> Sorry I am aware of the issue and am busy for $REALJOB these days. I >>> have cc'ed howardsu@ and mingyanguo@ to see if they have some >>> suggestions. The problem seems to be a race condition caused by >>> incorrect VFS related locking, but diagnosing it is relatively hard. >>> >>> I'll try to pick up with the development in early October. Before that >>> I can only do some small scale bugfixes rather than investing more time >>> into tmpfs stuff... :-( >>> >>> Cheers, >> Just want to be sure that no one lose this. Here is a PR: >> http://www.freebsd.org/cgi/query-pr.cgi?pr=116600 > > Can not reproduce here. Could you please confirm that this still > persists for latest RELENG_7? > > Cheers, I don't know about that one, but I am able to get this panic still after a few seconds of load: panic: Assertion IMPLIES(dnode->tn_type == VDIR && dnode->tn_dir.tn_parent == dnode, !(cnp->cn_flags & ISDOTDOT)) failed at ../../../fs/tmpfs/tmpfs_vnops.c:97 If you can fix that I can look for the other one :) Kris From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 21:59:42 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31A5516A419 for ; Tue, 30 Oct 2007 21:59:42 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id D540613C4B0 for ; Tue, 30 Oct 2007 21:59:41 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8p) with ESMTP id 216967012-1834499 for multiple; Tue, 30 Oct 2007 16:59:26 -0500 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l9ULxJTt084413; Tue, 30 Oct 2007 17:59:20 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Marcel Moolenaar Date: Tue, 30 Oct 2007 16:56:54 -0400 User-Agent: KMail/1.9.6 References: <20071027212420.EC7F94500E@ptavv.es.net> <200710301348.48031.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200710301656.55184.jhb@freebsd.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Tue, 30 Oct 2007 17:59:20 -0400 (EDT) X-Virus-Scanned: ClamAV 0.91.2/4641/Tue Oct 30 15:59:09 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: John-Mark Gurney , freebsd-current@freebsd.org Subject: Re: New-bus unit wiring via hints.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 21:59:42 -0000 On Tuesday 30 October 2007 04:00:28 pm Marcel Moolenaar wrote: > On Oct 30, 2007, at 10:48 AM, John Baldwin wrote: > > >>> That isn't what is happening though. The port marked "1" is at > >>> 0x3f8 > >>> and happens to be "later" in the namespace than the port marked "2" > >>> which is at 0x2e8. The BIOS may _optionally_ decide to communicate > >>> this to the OS via the _UID method, but the _UID is only guaranteed > >>> to be a string that it suitable for use in a label in a GUI dialog > >>> box. > >> > >> Doesn't this imply that enumerating on the lexicographical ordering > >> of the (optional) _UID method would help us do what firmware writers > >> intend? > >> > >> In other words, we don't need a number. We just need a means to > >> determine the relative order and we enumerate in that relative > >> order. Isn't that how it is now (and if not shouldn't it be that > >> way)? > > > > No. They are strings that have no implied ordering. > > Then there's no problem, for if _UID is designed as a user-visible > label and there's no ordering then no-one can claim that one is > to be before the other and thus that the logical ordering in the > AML is in fact the right ordering. This of course means that the > user can see COM2 before COM1 in some user-interface. This of course > is exactly in accordance with the firmware and as such correct. It would be interesting to see what Windows does since it still maintains 'COM1:' and 'COM2:' device aliases (if those are the correct DOS device names). > >>> Even if a PC has non-standard resources for COM1 and COM2, the > >>> serial > >>> ports will show up as sio2 and sio3. > >> > >> This is another sio(4) bug that uart(4) doesn't have, yes :-) > > > > Hmmm, I don't think you parsed what I meant, but maybe you mean that > > uart(4) > > doesn't have the poorly-implemented "feature" in sio(4) to make sure > > that all > > non-ISA serial ports start at unit 2 to "reserve" sio0 and sio1 for > > COM1 and > > COM2? > > Exactly. > > > Just look in sio_pci.c for 'device_set_unit()' which the current > > wiring patches remove with a vengance by making hints always reserve > > a given > > (name, unit) tuple. > > And since hints are shipped by us with default values, what > we did is remove the poorly-implemented "feature" from sio(4) > only to bank on hints to yield the same result, which makes > hints nothing more than a different poorly-implemented > "feature" :-) So you are missing that 1) our users really want this feature, and 2) by making hints do the reservation instead of _hard-coding_ it into the driver we know let users dictate how it should work since they can adjust the hints to suit their needs but still satisfy what users expect on off-the-shelf hardware with the default hints that ship. > >>> Since you don't care what sio0 > >>> means at all why not let other people who _do_ care have it work on > >>> their > >>> systems? > >> > >> "I" may not care what sio0 means, but that doesn't mean "I" don't > >> care that "my" serial ports aren't numbered starting with 0. > > > > And you could have an empty hints file and be happy. > > With the exception of course of having an OS that does the > wrong thing OOTB and that requires extensive fiddling to > behave correctly, increasing the amount of maintenance and > upgrade hassle. ? For the vast majority of x86 boxes (including all the varied boxes we have at work) the default hints will work just fine OOTB. Users are free to edit this, so it remains under user control and doesn't require a recompile. > >>>> You rightly point out that what it really boils > >>>> down to is how devX maps to a port on the back or > >>>> front of the machine. This mapping should not > >>>> change gratuitously. Device wiring achieves that. > >>> > >>> But on what basis will you wire things? > >> > >> Correcting the mapping of device instances to physical/visible > >> ports will need to be based on user input. A default mapping, > >> based on the self-enumerating ability of hardware/firmware, may > >> not get it just right in all cases. But may provide a good and > >> reliable starting point that may end up 90+% correct. > > > > Oof. See, here is where I think we hit a snag. :( I'm thinking in > > terms of > > automated installations to a wide variety of server boxes that don't > > have > > a GUI with a mouse and monitor hooked up so a user can clicky-clicky > > to set > > which serial port is sio0. :( > > I don't see a snag. But maybe that's because I use > uart(4) on my machines and I have a serial consoles > no matter how things are enumerated... So. I misread how uart's stuff works the first time, but I think I understand now, but I think it has its own confusion. So uart_cpu_{i386,amd64} expect there to be uart hints (wait, I thought hints were the great satan?) that are identical to sio hints. Thus: hint.uart.0.at="isa" hint.uart.0.flags="0x10" hint.uart.0.port="0x3f8" hint.uart.0.baud="9600" However, if you have a system with a PCI serial device or where ACPI lists the darn things backwards then uart0 might be the PCI device, and, say, uart2 might be the device corresponding to these hints. The uart(4) driver then goes and scans the hints on its own to find a set of hints that matches the resources for uart2 and migrates the flag (and thus the serial console setting) over to uart2, so uart2 (device at 0x3f8) does get set to the serial console. But /dev/ttyu0 in userland doesn't match hint.uart.0. Instead, the user has to know (how??) that it's /dev/ttyu2 when they setup /etc/ttys to have a getty listening on COM1. That seems very non-intuitive. At least remove the unit numbers or something and do: uart.console.port=0x3f8 uart.console.baud=9600 or some such. It seems very POLA-violating to have uart0 hints match some other unit number. Of course, that solves the console problem but what if someone wants to apply a different property to a device, like hint.foo.0.disable? or hint.foo.0.bar? ("baud" above corresponds to a "bar"). > >>> The only currently reliable > >>> way I can see to wire things on x86 for an ISA device (and yes, the > >>> COM port on a PC is ISA even if ACPI is what enumerates it rather > >>> than > >>> PNPBIOS) is I/O resources or the name of the device in the ACPI > >>> namespace (ACPI-only). > >> > >> I disagree. Since the firmware describes the legacy devices present > >> in the system, the only reliable way is to trust that information. > >> Sure, bugs may exist but 95+% of the FreeBSD code assumes correctness > >> of hardware as it is, so why not in this respect? > > > > You've missed the point of this entirely then. :( Yes, the firmware > > is > > authoritative, and part of the goal is to fix a long-standing > > weakness where > > the OS is presented with two different enumerations of hardware: one > > supplied > > by the user via hints and one supplied by the firmware. > > The "weakness" you mention is really the OSes own failure by > "presenting" itself with hardware information that has no > relation to the machine that it runs on, because it's > actually fixated by virtue of being part of the OSes source > code. It isn't supplied by the user at all. We supply it to > ourselves. Don't go blaming the user for that... Umm, the user can adjust /boot/device.hints (I do) and can even adjust it at boot time in the loader. > > The idea is to trust > > the firmware's notion of resources since it probably knows better > > while > > allowing for other non-resource information provided by the user to > > be tied > > to the correct piece of hardware. > > Agreed... > > He, that's what I said previously and you responded to with > saying that we hit a snag. I guess we don't then; or do we? > I'm confused now :-) The snag is you want the user to explicitly set it all up whereas I require it to be automated and reliable (_UID and ACPI namespace node names are not reliable as per previous e-mails). > >> Anyway, when ACPI describes the hardware, I prefer not to call the > >> legacy hardware ISA devices. It's important to make a clear > >> distinction > >> between enumerating and non-enumerating hardware, because that allows > >> you to create mechanisms for dealing with non-enumerating hardware > >> (i.e. > >> hints) without creating conflicts or ambiguity with enumerating HW. > >> We have convoluted this and mistakenly accepted this convolution as a > >> property of ISA hardware. > >> > >> I've been advocating that our bus-abstraction is a good one. Devices > >> enumerated by ACPI can be said to be attached to an ACPI bus. At > >> least > >> it's not more wrong than saying that they are ISA devices when it's > >> obvious that there's no ISA bus to be found in modern hardware and > >> all > >> the legacy hardware is really on the chipsets LPC bus. > > > > You continue to ignore that ACPI is not just a simple bus, but is a > > namespace > > that enumerates devices on multiple busses such as ISA/LPC, SMBus > > (e.g. an > > IPMI SSIF interface can be enumerated via ACPI), etc. It is much more > > generic than just an ISA enumerator like PNPBIOS. > > No, I don't ignore anything. I explicitly and deliberately use > the term "abstraction". It's a simplified representation of > reality. An "idea". My choice of calling ACPI a bus is probably > what confuses you. I'm fully aware that it is much more than a > bus, but it still "quacks" like one WRT legacy hardware... So where do you hang non-ISA devices on "dumb" busses like IIC that ACPI enumerates? Off acpi0 or the relevant parent such as iic0 or smbus0? > >>> For uart console wiring you use I/O resources for > >>> wiring even. > >> > >> Yes, but not "even". Since bus-enumeration hasn't happened yet, > >> we can not describe the serial console by name+unit, because we > >> have no way of knowing upfront what unit number will be assigned > >> to the UART. The only way you can describe the serial console > >> is by hardware resources or by firmware-level names (such as is > >> the case on powerpc & sparc64). > >> > >> This is why using hints to "mark" the console is wrong. > >> > >> Note also that on ia64 (at least) ACPI tables exist that describe > >> the serial console (and debug port) and those tables use hardware > >> resources. So, the common denominator is I/O resources (even for > >> OFW-based machines) and as it is, it's really the only thing you > >> need (module hardware type) to make a low-level console work. > >> > >> The only correct way to identify hardware for use as low-level > >> console is by it's location in I/O space (module hardware type). > >> This is what uart(4) does and it's one of the reasons uart(4) > >> works on all platforms even though low-level console support is > >> highly machine dependent. It's the right way of doing it and > >> as such it just works. > >> > >> Do not mistake low-level console identification with bus-enumeration > >> device wiring or it being similar to hints. > >> > >> To re-iterate: > >> We should reserve hints for describing non-enumerating hardware > >> (which means device.hints should be non-existent OOTB) and we > >> should add other mechanisms to wire devices to hardware, making > >> use of the fact that underneath it mechanisms exist to enumerate > >> the hardware (incl. hints for non-enumerating hardware). In the > >> future we can replace hints with a more flexible and expressive > >> means to describe hardware so that it better meets the needs of > >> embedded environments and without it impacting device wiring. > > > > So what do you want: 'wire.sio.0.*?' Or do you want XML or some > > binary > > registery like Windows that can't be modified by the user w/o first > > booting > > the OS (which is real handy when it gets corrupted). > > What I want is something that is appropriate. If we want to wire > hardware to devices, then we need to be able to uniquely identify > a device in hardware. A path if you will that mentions busses, > bridges devices and functions therein. Look at ACPI, EFI and OFW > for example. Such an identification is the keying entity. Data > that corresponds to that key can be complex or compound so that > you can actually specify which driver you want to use above and > beyond simply wiring it to a unit number. This also also allows > us to add other pieces of information. > > I'm not going to give concrete examples, because I foresee that > the discussion will then be about how my "solution" sucks rather > than it being treated for what it is: an illustration -- something > to explain what I said and in no way complete or even usable. > > Ok, what the heck. For better or for worse: > > \begin{/boot/hardware.conf} > # Lines starting with '#' are comments > [pci0.0.18.0] > # First function: standard UART > # We use this for remote GDB > driver="sio" > unit=2 > dbgport="9600,n,8,1" > [pci0.0.18.1] > # Second function: standard but memory-mapped UART > # doesn't work with sio(4) -- needs uart(4) > # We use this one as console. > driver="uart" > unit=3 > console="115200,n,8,1" > \end{/boot/hardware.conf} > > Don't get confused about marking the hardware as console > or debug port and how we do the same in hints. It isn't > the same. > Hints mark the driver instance as console or debug port. > Here I mark the *hardware* as console or debug port, even > if we don't wish to wire it to a driver instance (although > we do in the example) > Fundamentally different! I can appreciate that, though I consider that I'm binding "sio0" to a piece of hardware so that the other settings for sio0 are bound to the hardware and not to the first device that the sio(4) driver decides to attach to. I actually would like the ability to do something akin to 'hint.pci0.18.0.0.disabled=1' to disable a PCI device. (Granted, that's still in MIB form rather than a flat file, but conceptually similar. I still prefer using the kernel env primed via a file in /boot because you can adjust the kernel env easily in the loader.) Another thing to consider is that if you are going to "wire" a device to a specific driver/unit number (so I can make COM1 always be sio0/uart0 and thus always /dev/ttyd0|/dev/ttyu0) you need to make sure you reserve that driver/unit combo so it can't be probed or attached by something else. > > Right now the current "solution" results in various places (like my > > employer) > > just turning off the ACPI support for sio(4) because hints are more > > reliable > > for us than ACPI when it comes to enumerating serial ports in _real_ > > _world_ > > _x86_ server-class machines. > > Use uart(4)? No. Having to guess which device to start the getty on rather then being able to always use /dev/ttyd0 is annoying for one, and just always using hints works fine since COM1/COM2 is an effective de facto standard on all the hardware we buy at work. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 22:06:49 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C4FC16A468 for ; Tue, 30 Oct 2007 22:06:49 +0000 (UTC) (envelope-from ender@enderzone.com) Received: from www.ksdhost.com (www.ksdhost.com [75.126.66.82]) by mx1.freebsd.org (Postfix) with ESMTP id 409CC13C4BF for ; Tue, 30 Oct 2007 22:06:49 +0000 (UTC) (envelope-from ender@enderzone.com) Received: (qmail 17642 invoked from network); 30 Oct 2007 16:39:52 -0500 Received: from buff-broadband-ws-86.dsl.pwrtc.com (HELO ?192.168.5.101?) (64.184.124.87) by www.ksdhost.com with SMTP; 30 Oct 2007 16:39:52 -0500 Message-ID: <4727A487.1030604@enderzone.com> Date: Tue, 30 Oct 2007 17:39:19 -0400 From: Ender User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Mark Powell References: <20071029092531.J99722@rust.salford.ac.uk> <20071030015534.GA69514@eos.sc1.parodius.com> <20071030093229.O32304@rust.salford.ac.uk> In-Reply-To: <20071030093229.O32304@rust.salford.ac.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jeremy Chadwick , freebsd-current@freebsd.org Subject: Re: WRITE_DMA48 error causing loss of ZFS array X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 22:06:49 -0000 Mark Powell wrote: > On Mon, 29 Oct 2007, Jeremy Chadwick wrote: > >> On Mon, Oct 29, 2007 at 09:59:11AM +0000, Mark Powell wrote: >>> I've experienced several dma errors over the past few months with >>> various >>> incarnations of 7.0 which were all fixed. >> >> This could be relevant: >> >> http://kerneltrap.org/mailarchive/freebsd-current/2007/10/2/326931 > > Yes, thanks. Last time I mentioned this, des@des.no also said then it > was a well known ATA bug, for which I should look in the archives. > However, as I said, it's hard to pinpoint from searching the -current > archives, quite which bug he is talking about. > Does anyone have a link to a post which goes into greater detail > about this problem? > I'd like to post a PR regarding this, but would like to read these > previous posts to get a little more info. > Cheers. > Maybe one of these is related? http://www.freebsd.org/cgi/query-pr.cgi?pr=117656 Also if this is a well known (s)ata bug, should it maybe be added to UPDATING or some sort of documentation? Maybe http://www.freebsd.org/releases/7.0R/todo.html ? From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 22:45:16 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFEB116A418; Tue, 30 Oct 2007 22:45:16 +0000 (UTC) (envelope-from lists@swaggi.com) Received: from rusty.swaggy.net (rusty.swaggy.net [204.14.85.196]) by mx1.freebsd.org (Postfix) with ESMTP id C88ED13C480; Tue, 30 Oct 2007 22:45:16 +0000 (UTC) (envelope-from lists@swaggi.com) Received: from localhost ([127.0.0.1] helo=swaggi.com) by rusty.swaggy.net with esmtp (Exim 4.67 (FreeBSD)) (envelope-from ) id 1ImzDT-000IBc-7q; Tue, 30 Oct 2007 18:05:44 -0400 From: "Yuri Lukin" To: freebsd-current@freebsd.org Date: Tue, 30 Oct 2007 17:05:43 -0500 Message-Id: <20071030220251.M82173@swaggi.com> In-Reply-To: <20071029235020.M75001@swaggi.com> References: <20071029235020.M75001@swaggi.com> X-Mailer: swaggi.com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Cc: freebsd-java@freebsd.org Subject: Re: Firefox Java plugin with 7.0? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 22:45:17 -0000 On Mon, 29 Oct 2007 19:05:34 -0500, Yuri Lukin wrote > I'm like to ask what people are using for Java plugin with Firefox. > There were a few recent threads on this subject but no definitive answer: > > http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078038.html > http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078492.html > > I tried compiling jdk15 port and was able to build it and install it > successfully. However, when trying to load a java applet in Firefox, > the browser seemingly crashes (exits). I then tried following the > method described in the handbook by downloading the diablo-jre-freebsd6.i386.1.5.0.07.01.tbz > package from FreeBSD Foundation website and adding it with pkg_add. > Trying to load java applets crashes Firefox. In both cases, > javavmwrapper was installed and about:plugins in Firefox shows that > java plugin is installed. Is there a working combination for 7.0-PRERELEASE/BETA? > > My system is: > > # uname -a > > FreeBSD 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #0: Mon Oct 15 > 13:02:17 EDT 2007 swaggy@:/usr/obj/usr/src/sys/T61 i386 > # pkg_info | grep java > javavmwrapper-2.3 Wrapper script for various Java Virtual Machines > # pkg_info | grep firefox > firefox-2.0.0.8,1 Web browser based on the browser portion of Mozilla > > # ls -la /usr/local/lib/browser_plugins/ > total 96 > drwxr-xr-x 2 root wheel 512 Oct 29 19:22 . > drwxr-xr-x 54 root wheel 31232 Oct 29 13:26 .. > -rw-r--r-- 1 root wheel 0 Oct 20 00:20 .firefox.keep > lrwxr-xr-x 1 root wheel 63 Oct 29 19:22 libjavaplugin_oji.so - > > /usr/local/diablo-jre1.5.0/plugin/i386/ns7/libjavaplugin_oji.so - > rwxr-xr-x 1 root wheel 62192 Sep 12 14:21 npwrapper.libflashplayer.so > > Currently with jre from FreeBSD foundation site: > # pkg_info | grep jre > diablo-jre-1.5.0.07.01 Java Runtime Environment 1.5.0_07.01 > I found an answer off-list. In case anyone is wondering, I had to first install java/diablo-jdk15 (with compat6x), then install java/jdk15. After that, I simply removed diablo-jdk15 and added a symlink to /usr/local/lib/browser_plugins in order for Firefox to recognize the browser plugin. Works great now. Many thanks to Vlad Galu for the answer. Yuri From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 23:21:20 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FD7F16A481; Tue, 30 Oct 2007 23:21:20 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpoutm.mac.com (smtpoutm.mac.com [17.148.16.75]) by mx1.freebsd.org (Postfix) with ESMTP id 7678013C4A8; Tue, 30 Oct 2007 23:21:20 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (asmtp001-s [10.150.69.64]) by smtpoutm.mac.com (Xserve/smtpout012/MantshX 4.0) with ESMTP id l9UNL6kD013890; Tue, 30 Oct 2007 16:21:06 -0700 (PDT) Received: from mini-g4.jnpr.net (natint3.juniper.net [66.129.224.36]) (authenticated bits=0) by mac.com (Xserve/asmtp001/MantshX 4.0) with ESMTP id l9UNKxZx018557 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 30 Oct 2007 16:21:00 -0700 (PDT) Message-Id: <0B9CF454-8DF6-4053-BDE9-B3A583D456C0@mac.com> From: Marcel Moolenaar To: John Baldwin In-Reply-To: <200710301656.55184.jhb@freebsd.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v912) Date: Tue, 30 Oct 2007 16:20:58 -0700 References: <20071027212420.EC7F94500E@ptavv.es.net> <200710301348.48031.jhb@freebsd.org> <200710301656.55184.jhb@freebsd.org> X-Mailer: Apple Mail (2.912) Cc: John-Mark Gurney , freebsd-current@freebsd.org Subject: Re: New-bus unit wiring via hints.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 23:21:20 -0000 On Oct 30, 2007, at 1:56 PM, John Baldwin wrote: > >>>>>> You rightly point out that what it really boils >>>>>> down to is how devX maps to a port on the back or >>>>>> front of the machine. This mapping should not >>>>>> change gratuitously. Device wiring achieves that. >>>>> >>>>> But on what basis will you wire things? >>>> >>>> Correcting the mapping of device instances to physical/visible >>>> ports will need to be based on user input. A default mapping, >>>> based on the self-enumerating ability of hardware/firmware, may >>>> not get it just right in all cases. But may provide a good and >>>> reliable starting point that may end up 90+% correct. >>> >>> Oof. See, here is where I think we hit a snag. :( I'm thinking in >>> terms of >>> automated installations to a wide variety of server boxes that don't >>> have >>> a GUI with a mouse and monitor hooked up so a user can clicky-clicky >>> to set >>> which serial port is sio0. :( >> >> I don't see a snag. But maybe that's because I use >> uart(4) on my machines and I have a serial consoles >> no matter how things are enumerated... > > So. I misread how uart's stuff works the first time, but I think I > understand > now, but I think it has its own confusion. So uart_cpu_{i386,amd64} > expect > there to be uart hints (wait, I thought hints were the great satan?) Support for hints was added to i386 and amd64 to promote use of the uart(4) driver only. The uart-way is by using the tunable hw.uart.console and hw.uart.dbgport. > However, if you have a system with a PCI serial device or where ACPI > lists the > darn things backwards then uart0 might be the PCI device, and, say, > uart2 > might be the device corresponding to these hints. You're finally seeing it my way: hints are bad, m'kay :-) > The uart(4) driver then > goes and scans the hints on its own to find a set of hints that > matches the > resources for uart2 and migrates the flag (and thus the serial console > setting) over to uart2, so uart2 (device at 0x3f8) does get set to > the serial > console. Yes. The only thing uart(4) uses from the hints is the I/O address of the UART that is marked as console. Later, during bus-enumeration we map the driver instance onto the console like if you had no hints at all (the norm). > Instead, the > user has to know (how??) that it's /dev/ttyu2 when they setup /etc/ > ttys to > have a getty listening on COM1. Yes, /etc/ttys needs to match. This is a simple consequence of having configuration files, like network port setup in rc.conf and/or file systems in /etc/fstab. It's not a problem specific to uart(4) and any attempt in uart(4) to deal with that is wrong and futile. > That seems very non-intuitive. It is non-intuitive. Hints are. > At least > remove the unit numbers or something and do: > > uart.console.port=0x3f8 > uart.console.baud=9600 Why? There's already hw.uart.console and hw.uart.dbgport that allow you to set everything you need. >>>>> You've missed the point of this entirely then. :( Yes, the >>>>> firmware >>> is >>> authoritative, and part of the goal is to fix a long-standing >>> weakness where >>> the OS is presented with two different enumerations of hardware: one >>> supplied >>> by the user via hints and one supplied by the firmware. >> >> The "weakness" you mention is really the OSes own failure by >> "presenting" itself with hardware information that has no >> relation to the machine that it runs on, because it's >> actually fixated by virtue of being part of the OSes source >> code. It isn't supplied by the user at all. We supply it to >> ourselves. Don't go blaming the user for that... > > Umm, the user can adjust /boot/device.hints (I do) and can even > adjust it at > boot time in the loader. I guess OOTB means manual configuration before the kernel boots? :-) >>> The idea is to trust >>> the firmware's notion of resources since it probably knows better >>> while >>> allowing for other non-resource information provided by the user to >>> be tied >>> to the correct piece of hardware. >> >> Agreed... >> >> He, that's what I said previously and you responded to with >> saying that we hit a snag. I guess we don't then; or do we? >> I'm confused now :-) > > The snag is you want the user to explicitly set it all up whereas I > require it > to be automated and reliable (_UID and ACPI namespace node names are > not > reliable as per previous e-mails). No, that's the opposite of what I want. ACPI is reliable. >>>> Anyway, when ACPI describes the hardware, I prefer not to call the >>>> legacy hardware ISA devices. It's important to make a clear >>>> distinction >>>> between enumerating and non-enumerating hardware, because that >>>> allows >>>> you to create mechanisms for dealing with non-enumerating hardware >>>> (i.e. >>>> hints) without creating conflicts or ambiguity with enumerating HW. >>>> We have convoluted this and mistakenly accepted this convolution >>>> as a >>>> property of ISA hardware. >>>> >>>> I've been advocating that our bus-abstraction is a good one. >>>> Devices >>>> enumerated by ACPI can be said to be attached to an ACPI bus. At >>>> least >>>> it's not more wrong than saying that they are ISA devices when it's >>>> obvious that there's no ISA bus to be found in modern hardware and >>>> all >>>> the legacy hardware is really on the chipsets LPC bus. >>> >>> You continue to ignore that ACPI is not just a simple bus, but is a >>> namespace >>> that enumerates devices on multiple busses such as ISA/LPC, SMBus >>> (e.g. an >>> IPMI SSIF interface can be enumerated via ACPI), etc. It is much >>> more >>> generic than just an ISA enumerator like PNPBIOS. >> >> No, I don't ignore anything. I explicitly and deliberately use >> the term "abstraction". It's a simplified representation of >> reality. An "idea". My choice of calling ACPI a bus is probably >> what confuses you. I'm fully aware that it is much more than a >> bus, but it still "quacks" like one WRT legacy hardware... > > So where do you hang non-ISA devices on "dumb" busses like IIC that > ACPI > enumerates? Off acpi0 or the relevant parent such as iic0 or smbus0? A device hangs off of it's corresponding bus in most cases. The legacy devices are special in our case, because we have 1) hints that mess things up, and 2) the option of not using ACPI, so that we do need hints to enumerate things that we don't get enumerated any other way. Both 1) and 2) interact with each other in that we need 1) for 2). A separate bus is the best thing because it keeps things clear. >>>>> For uart console wiring you use I/O resources for >>>>> wiring even. >>>> >>>> Yes, but not "even". Since bus-enumeration hasn't happened yet, >>>> we can not describe the serial console by name+unit, because we >>>> have no way of knowing upfront what unit number will be assigned >>>> to the UART. The only way you can describe the serial console >>>> is by hardware resources or by firmware-level names (such as is >>>> the case on powerpc & sparc64). >>>> >>>> This is why using hints to "mark" the console is wrong. >>>> >>>> Note also that on ia64 (at least) ACPI tables exist that describe >>>> the serial console (and debug port) and those tables use hardware >>>> resources. So, the common denominator is I/O resources (even for >>>> OFW-based machines) and as it is, it's really the only thing you >>>> need (module hardware type) to make a low-level console work. >>>> >>>> The only correct way to identify hardware for use as low-level >>>> console is by it's location in I/O space (module hardware type). >>>> This is what uart(4) does and it's one of the reasons uart(4) >>>> works on all platforms even though low-level console support is >>>> highly machine dependent. It's the right way of doing it and >>>> as such it just works. >>>> >>>> Do not mistake low-level console identification with bus- >>>> enumeration >>>> device wiring or it being similar to hints. >>>> >>>> To re-iterate: >>>> We should reserve hints for describing non-enumerating hardware >>>> (which means device.hints should be non-existent OOTB) and we >>>> should add other mechanisms to wire devices to hardware, making >>>> use of the fact that underneath it mechanisms exist to enumerate >>>> the hardware (incl. hints for non-enumerating hardware). In the >>>> future we can replace hints with a more flexible and expressive >>>> means to describe hardware so that it better meets the needs of >>>> embedded environments and without it impacting device wiring. >>> >>> So what do you want: 'wire.sio.0.*?' Or do you want XML or some >>> binary >>> registery like Windows that can't be modified by the user w/o first >>> booting >>> the OS (which is real handy when it gets corrupted). >> >> What I want is something that is appropriate. If we want to wire >> hardware to devices, then we need to be able to uniquely identify >> a device in hardware. A path if you will that mentions busses, >> bridges devices and functions therein. Look at ACPI, EFI and OFW >> for example. Such an identification is the keying entity. Data >> that corresponds to that key can be complex or compound so that >> you can actually specify which driver you want to use above and >> beyond simply wiring it to a unit number. This also also allows >> us to add other pieces of information. >> >> I'm not going to give concrete examples, because I foresee that >> the discussion will then be about how my "solution" sucks rather >> than it being treated for what it is: an illustration -- something >> to explain what I said and in no way complete or even usable. >> >> Ok, what the heck. For better or for worse: >> >> \begin{/boot/hardware.conf} >> # Lines starting with '#' are comments >> [pci0.0.18.0] >> # First function: standard UART >> # We use this for remote GDB >> driver="sio" >> unit=2 >> dbgport="9600,n,8,1" >> [pci0.0.18.1] >> # Second function: standard but memory-mapped UART >> # doesn't work with sio(4) -- needs uart(4) >> # We use this one as console. >> driver="uart" >> unit=3 >> console="115200,n,8,1" >> \end{/boot/hardware.conf} >> >> Don't get confused about marking the hardware as console >> or debug port and how we do the same in hints. It isn't >> the same. >> Hints mark the driver instance as console or debug port. >> Here I mark the *hardware* as console or debug port, even >> if we don't wish to wire it to a driver instance (although >> we do in the example) >> Fundamentally different! > > I can appreciate that, though I consider that I'm binding "sio0" to > a piece of > hardware so that the other settings for sio0 are bound to the > hardware and > not to the first device that the sio(4) driver decides to attach to. I think I approach wiring from the opposite direction. It's the hardware I'm interested in: Fortune candidate: A driver without hardware is meaningless, but hardware without a driver is a source of opportunity and longing. :-) > I > actually would like the ability to do something akin > to 'hint.pci0.18.0.0.disabled=1' to disable a PCI device. Yes, I like that too. > (Granted, that's > still in MIB form rather than a flat file, but conceptually similar. Agreed. > I still > prefer using the kernel env primed via a file in /boot because you > can adjust > the kernel env easily in the loader.) That definitely is a plus. At this time I don't know if we can achieve that in the grand scheme of things, but we should definitely not abandon it gratuitously. > Another thing to consider is that if you are going to "wire" a > device to a > specific driver/unit number (so I can make COM1 always be sio0/uart0 > and thus > always /dev/ttyd0|/dev/ttyu0) you need to make sure you reserve that > driver/unit combo so it can't be probed or attached by something else. Maybe, yes. I haven't exactly ruled out a mode of operation where the wiring is ignored if the hardware isn't there (or is disabled) and thus that the driver instance is re-used. Think for example about 2 similar devices (let's keep them UARTs), one in active use and one for backup. Both are wired to the same tty to avoid configuration changes. You can then always use one of the two (either) knowing that the wiring will be consistent. I don't really know if this is a useful feature or a wave of featuritis... -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 10:42:23 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F36A16A418; Tue, 30 Oct 2007 10:42:23 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from galaxy.systems.pipex.net (galaxy.systems.pipex.net [62.241.162.31]) by mx1.freebsd.org (Postfix) with ESMTP id 31A6313C481; Tue, 30 Oct 2007 10:42:23 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from [192.168.23.2] (62-31-10-181.cable.ubr05.edin.blueyonder.co.uk [62.31.10.181]) by galaxy.systems.pipex.net (Postfix) with ESMTP id 2F52CE000C7A; Tue, 30 Oct 2007 10:23:59 +0000 (GMT) Message-ID: <4727063E.7060107@dial.pipex.com> Date: Tue, 30 Oct 2007 10:23:58 +0000 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.13) Gecko/20061205 X-Accept-Language: en MIME-Version: 1.0 To: Giorgos Keramidas , Andrew Lankford References: <47240A15.8080305@charter.net> <20071028074248.GA1511@haakonia.hitnet.RWTH-Aachen.DE> <4724BAD9.7000400@charter.net> <20071028164152.GA7516@eos.sc1.parodius.com> <4724BEB3.5080905@charter.net> <20071029132447.GA2658@kobe.laptop> In-Reply-To: <20071029132447.GA2658@kobe.laptop> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 31 Oct 2007 01:45:24 +0000 Cc: stable@freebsd.org, current@freebsd.org Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 10:42:23 -0000 Giorgos Keramidas wrote: >On 2007-10-28 12:54, Andrew Lankford wrote: > > >>Thbbt! I'm reading the catman version of MAKEDEV. Wish I could >>disable that "feature". Oh well. I'll delete it all and rebuild it >>again if needed. Thanks! >> >> > >Ah, that's it then :) > >My usual `installworld' steps include this too: > > # cd /usr/share/man > # find cat[0-9] \! -type d -exec rm {} + > >This takes care of deleting any `stale' preformatted manpages, so the >next time I ask for a manpage, it's going to be reformatted. > > Seems to me that there must a logic error in man. Man makes the effort to check to see if the unformatted manpage is newer than the cat-ed manpage, and if it is, it will try to re-create the cat-ed manpage, and will show you an nroff'ed version of the unformatted manpage if it cannot recreate the cat-ed version. Clearly that's breaking in this scenario, because the mtime of the new unformatted manpage, while presumably newer than that of the old unformatted man page is still older than the mtime of the cat-ed page. What seems to be missing, is that when the cat-ed manpage is first created, it should have its mtime set to the same as the mtime of the unformatted manpage, not the time at which you happened to read the man page. I don't see any evidence of that is the sources on my system (which is quite old, but it certainly looks like the bug persists). A bit of stat and utimes jiggery pokery looks like it would solve this problem. An else clause for " else if (rename(temp, cat_file) == -1) {" in /usr/src/gnu/usr.bin/man/man/man.c would look like the place to do that. (Alternatively, you could view it as a bug of the install/upgrade process, since it could be argued that the mtime of the unformatted manpage should be the time that the manpage was installed. Presumably that isn't happening, else you wouldn't be seeing the cat-ed version). Of course, with modern systems where nroff-ing a man page takes negligible time and system resources, it could also be argued that cat-ed man pages should be a thing of the past :-) --Alex From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 15:00:56 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1AE6D16A420 for ; Tue, 30 Oct 2007 15:00:56 +0000 (UTC) (envelope-from yaraghchi@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.176]) by mx1.freebsd.org (Postfix) with ESMTP id CA96C13C4A5 for ; Tue, 30 Oct 2007 15:00:55 +0000 (UTC) (envelope-from yaraghchi@gmail.com) Received: by el-out-1112.google.com with SMTP id s27so531312ele for ; Tue, 30 Oct 2007 08:00:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; bh=iOxXZuC7DWKvDGDrlyIGW0rWnKOlCh89kwGW8PzUVcY=; b=uAN3Jvb6khJJXalKuq4dv4UiEhLccRk0MnnZJ24wjIIMm06dv7rwHRAUoAd6hhIYnVnDdWDNF2Mgk0P2TLI4FNF/4V50vfKUlzl+WewcW5nRe9jePy5ooa6JB83RdsM5K/qmKqAptzeUOiv5cOlaE2gczEhok+jXmc1EbJ9zTK4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=G4rp9JbUebyI7LFkrqtj7OwblbZ2/YyCtAT68Ljk7qqyzz5Kmda9xTtH6tT5blxgiXK+SF2MZYV7gmkVs1ooWtAYod5wBNyQp7COpIoWiPOl7OopWQHDLRQwNP0ccDlQBtqDLkPzjZL2nnUCIbgQ78k7wk34iADqB9JyLUs++3k= Received: by 10.142.222.21 with SMTP id u21mr1667394wfg.1193754739375; Tue, 30 Oct 2007 07:32:19 -0700 (PDT) Received: by 10.143.158.18 with HTTP; Tue, 30 Oct 2007 07:32:19 -0700 (PDT) Message-ID: <25f52a3d0710300732x425f0c45vde1a29361096c018@mail.gmail.com> Date: Tue, 30 Oct 2007 15:32:19 +0100 From: "Stephan F. Yaraghchi" Sender: yaraghchi@gmail.com To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Google-Sender-Auth: 58699b0c22100465 X-Mailman-Approved-At: Wed, 31 Oct 2007 03:58:56 +0000 Subject: loader breaks with -O2 optimizations X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 15:00:56 -0000 After making world on a freshly installed 7.0-BETA1 the system does not boot anymore due to a broken loader: FreeBSD/i386 bootstrap loader, Revision 1.1 (root@bigblue, Tue Oct 30 11:26:32 CET 2007) Can't work out which disk we are booting from. Guessed BIOS device 0xffffffff not found by probes defaulting to disk0: panic: free: guard1 fail@ 0x6ded4 from /usr/src/sys/boot/i386/loader/../../common/module.c:959 --> Press a key on the console to reboot <-- I found out that the following line in my make.conf causes the problem: CFLAGS= -O2 -funroll-loops -pipe After changing down to -O1 and making /usr/src/sys/boot again the systems behaves properly at boot. Is this behavior intended? -- Stephan. www.deine-stimme-gegen-armut.de From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 19:10:00 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D601416A417 for ; Tue, 30 Oct 2007 19:10:00 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.187]) by mx1.freebsd.org (Postfix) with ESMTP id 6FC8013C48E for ; Tue, 30 Oct 2007 19:10:00 +0000 (UTC) (envelope-from ndenev@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so1736072rvb for ; Tue, 30 Oct 2007 12:10:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=lyv0iUpwYYhRsTjTQVkZDJWbZnAzN/oAvuqYpC8LLjg=; b=mKZOYgDi6ChMlXxGcrvlCEQxmKzawALgH72FdxtK4DGNF+JRyeBmFJW+46qU5QFkaObP9QWPB9cpbdZ01OcHIY3lM3cZUR+kHGdTsDLubm5GzQ/fw90Q3QMITilHp0JFPSmne71SpXqe7QNXmoEG34ZaUKH5jSWjNBJFgaFPAPM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=TK+SY7ZHumtd5B2f2S+SqFtQXKg/dRg+PQ0YNpaP035OooORltT03QRTQUlMky28o8qiMb8RpvfL+LE1JdLMEotgRTbYLbGmn4nr9QZi5m3Zdl+if/TqVrPKTOL88jlT4Wq1u6tGJS8t8lb+x2iV172qf7rZGDag7qHcl/+ky/E= Received: by 10.141.2.19 with SMTP id e19mr3523193rvi.1193769951989; Tue, 30 Oct 2007 11:45:51 -0700 (PDT) Received: by 10.141.170.18 with HTTP; Tue, 30 Oct 2007 11:45:51 -0700 (PDT) Message-ID: <2e77fc10710301145yf6441es948fd3a02e5dd35a@mail.gmail.com> Date: Tue, 30 Oct 2007 20:45:51 +0200 From: "Niki Denev" Sender: ndenev@gmail.com To: "Patrick Dung" In-Reply-To: <238725.26120.qm@web54304.mail.re2.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <238725.26120.qm@web54304.mail.re2.yahoo.com> X-Google-Sender-Auth: a63ffc96ebfa7b2a X-Mailman-Approved-At: Wed, 31 Oct 2007 03:58:47 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: kernel panic at shutdown with freebsd 7.0 current snapshot (oct-2007) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 19:10:01 -0000 On 10/24/07, Patrick Dung wrote: > Hi > > I have ZFS (and snapshot) mounted. > Then shutdown by `shutdown -p now`. > > There is the dump: > > # kgdb /boot/kernel/kernel.symbols vmcore.0 > [GDB will not be able to debug user-mode threads: > /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and > you are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "i386-marcel-freebsd". > > Unread portion of the kernel message buffer: > panic: vrele: negative ref cnt > cpuid = 0 > KDB: enter: panic > panic: from debugger > cpuid = 0 > Uptime: 8h44m12s > Physical memory: 507 MB > Dumping 120 MB: 105 89 73 57 41 25 9 > > #0 doadump () at pcpu.h:195 > 195 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) where > #0 doadump () at pcpu.h:195 > #1 0xc074d98e in boot (howto=260) at > /usr/src/sys/kern/kern_shutdown.c:409 > #2 0xc074dc4b in panic (fmt=Variable "fmt" is not available. > ) at /usr/src/sys/kern/kern_shutdown.c:563 > #3 0xc048cab7 in db_panic (addr=Could not find the frame base for > "db_panic". > ) at /usr/src/sys/ddb/db_command.c:433 > #4 0xc048d4a5 in db_command_loop () at > /usr/src/sys/ddb/db_command.c:401 > #5 0xc048ec15 in db_trap (type=3, code=0) at > /usr/src/sys/ddb/db_main.c:222 > #6 0xc07748e6 in kdb_trap (type=3, code=0, tf=0xd53d7984) at > /usr/src/sys/kern/subr_kdb.c:502 > #7 0xc0a02dfb in trap (frame=0xd53d7984) at > /usr/src/sys/i386/i386/trap.c:621 > #8 0xc09e87eb in calltrap () at /usr/src/sys/i386/i386/exception.s:139 > #9 0xc0774a62 in kdb_enter (msg=0xc0a996bc "panic") at cpufunc.h:60 > #10 0xc074dc34 in panic (fmt=0xc0aa528a "vrele: negative ref cnt") at > /usr/src/sys/kern/kern_shutdown.c:547 > #11 0xc07cb0a1 in vrele (vp=0xc2fccaa0) at > /usr/src/sys/kern/vfs_subr.c:2117 > #12 0xc0725905 in fdfree (td=0xc2f29a50) at > /usr/src/sys/kern/kern_descrip.c:1694 > #13 0xc072ea53 in exit1 (td=0xc2f29a50, rv=1) at > /usr/src/sys/kern/kern_exit.c:272 > #14 0xc07508bf in sigexit (td=Variable "td" is not available. > ) at /usr/src/sys/kern/kern_sig.c:2876 > #15 0xc0750c99 in postsig (sig=1) at /usr/src/sys/kern/kern_sig.c:2748 > #16 0xc077eb78 in ast (framep=0xd53d7d38) at > /usr/src/sys/kern/subr_trap.c:250 > #17 0xc09e910d in doreti_ast () at > /usr/src/sys/i386/i386/exception.s:290 > #18 0xd53d7d38 in ?? () > #19 0x0000003b in ?? () > #20 0x0000003b in ?? () > #21 0x0000003b in ?? () > #22 0x00000000 in ?? () > #23 0xffffffff in ?? () > #24 0xbfbfee58 in ?? () > #25 0xd53d7d64 in ?? () > #26 0x00000000 in ?? () > #27 0x0804fb20 in ?? () > #28 0x00000000 in ?? () > #29 0x00000004 in ?? () > #30 0x0000000c in ?? () > #31 0x00000002 in ?? () > #32 0x28167553 in ?? () > #33 0x00000033 in ?? () > #34 0x00000247 in ?? () > #35 0xbfbfee1c in ?? () > #36 0x0000003b in ?? () > #37 0x00000000 in ?? () > #38 0x00000000 in ?? () > #39 0x00000000 in ?? () > #40 0x00000000 in ?? () > #41 0x0116c000 in ?? () > #42 0xc2f5bd48 in ?? () > ---Type to continue, or q to quit--- > #43 0xc31e1000 in ?? () > #44 0xd53d7878 in ?? () > #45 0xd53d7854 in ?? () > #46 0xc2f29a50 in ?? () > #47 0xc076a756 in sched_switch (td=0x0, newtd=0xffffffff, flags=Cannot > access memory at address 0xbfbfee68 > ) at /usr/src/sys/kern/sched_4bsd.c:907 > Previous frame inner to this frame (corrupt stack?) > (kgdb) > > Regards > Patrick > I got exactly the same panic today. --niki From owner-freebsd-current@FreeBSD.ORG Tue Oct 30 20:52:45 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B75CE16A420 for ; Tue, 30 Oct 2007 20:52:45 +0000 (UTC) (envelope-from bj@cold.dk) Received: from frontend1.kadnet.dk (frontend1.kadnet.dk [83.221.137.240]) by mx1.freebsd.org (Postfix) with SMTP id 0E22D13C4B3 for ; Tue, 30 Oct 2007 20:52:44 +0000 (UTC) (envelope-from bj@cold.dk) Received: (qmail 97435 invoked by uid 89); 30 Oct 2007 20:11:23 -0000 Received: from unknown (HELO hamilton.sjovedyr.dk) (83.221.137.165) by frontend1.kadnet.dk with SMTP; 30 Oct 2007 20:11:23 -0000 Message-ID: <4727935B.1000007@cold.dk> Date: Tue, 30 Oct 2007 21:26:03 +0100 From: Brian Josefsen User-Agent: Thunderbird 2.0.0.6 (X11/20070924) MIME-Version: 1.0 To: Yuri Lukin References: <20071029235020.M75001@swaggi.com> In-Reply-To: <20071029235020.M75001@swaggi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 31 Oct 2007 03:58:35 +0000 Cc: freebsd-current@freebsd.org, freebsd-java@freebsd.org Subject: Re: Firefox Java plugin with 7.0? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2007 20:52:45 -0000 Yuri Lukin wrote: > I'm like to ask what people are using for Java plugin with Firefox. There were > a few recent threads on this subject but no definitive answer: > > http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078038.html > http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078492.html > > I tried compiling jdk15 port and was able to build it and install it > successfully. However, when trying to load a java applet in Firefox, the > browser seemingly crashes (exits). I then tried following the method described > in the handbook by downloading the diablo-jre-freebsd6.i386.1.5.0.07.01.tbz > package from FreeBSD Foundation website and adding it with pkg_add. Trying to > load java applets crashes Firefox. In both cases, javavmwrapper was installed > and about:plugins in Firefox shows that java plugin is installed. Is there a > working combination for 7.0-PRERELEASE/BETA? > I made sure i had freebsd 6 compability in the kernel, no problem viewing applets in FreeBSD 7 with firefox 2, but firefox-devel (firefox 3) crashes with every kind of plugin, and even with some extensions. I use the Diable JDK with latest patchset, don't know if that makes a difference. -- Best regards Brian Josefsen Copenhagen, Denmark From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 01:04:41 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8498F16A421 for ; Wed, 31 Oct 2007 01:04:41 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 4FE1C13C4B5 for ; Wed, 31 Oct 2007 01:04:41 +0000 (UTC) (envelope-from sam@errno.com) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id l9V0vDct026206 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 30 Oct 2007 17:57:13 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <4727D2E9.7060904@errno.com> Date: Tue, 30 Oct 2007 17:57:13 -0700 From: Sam Leffler User-Agent: Thunderbird 2.0.0.6 (X11/20070814) MIME-Version: 1.0 To: Jack Vogel References: <2a41acea0710301016u4a0008dfjc83170257337863c@mail.gmail.com> In-Reply-To: <2a41acea0710301016u4a0008dfjc83170257337863c@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-dcc-servers-Metrics: om; whitelist Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List Subject: Re: em watchdog problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 01:04:41 -0000 Jack Vogel wrote: > This morning I had an idea about what the source of the watchdog > problem is. Also, we have repro'd at least one type of watchdog > inhouse. > > One question, is this problem only happening for those running > STABLE with the 6.6.6 merged driver? > > We found the problem does not seem to happen on 7.0. > > Right now my suspicion is that the FAST irq handling is > again causing a problem. I am experimenting with variations > to the code today to be sure whats going on, and hopefully > fixing it. > I see it on HEAD and releng7. Sam From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 01:19:42 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C6AC16A418 for ; Wed, 31 Oct 2007 01:19:42 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 59FB313C4B5 for ; Wed, 31 Oct 2007 01:19:42 +0000 (UTC) (envelope-from roberthuff@rcn.com) Received: from mr08.lnh.mail.rcn.net ([207.172.157.28]) by smtp02.lnh.mail.rcn.net with ESMTP; 30 Oct 2007 21:19:16 -0400 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr08.lnh.mail.rcn.net (MOS 3.8.3-GA) with ESMTP id JGR19771; Tue, 30 Oct 2007 21:19:16 -0400 (EDT) Received: from 209-6-22-188.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com (HELO jerusalem.litteratus.org.litteratus.org) ([209.6.22.188]) by smtp01.lnh.mail.rcn.net with ESMTP; 30 Oct 2007 20:19:15 -0500 From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18215.55314.937529.793041@jerusalem.litteratus.org> Date: Tue, 30 Oct 2007 21:19:14 -0400 To: freebsd-current@freebsd.org In-Reply-To: References: X-Mailer: VM 7.17 under 21.5 (beta28) "fuki" XEmacs Lucid X-Junkmail-Whitelist: YES (by domain whitelist at mr08.lnh.mail.rcn.net) Subject: Re: em0: watchdog timeout ... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 01:19:42 -0000 Ihsan Dogan writes: > I've got exactly the same problem on a machine, running 7.0-BETA1. The > Problem occurs during the boot, when dhclient is trying to get IP. The > messages are occuring all the time an it's not possible to use the > network card at all. I get this (link state up/down), but only once and only while dhclient is hunting for the IP. > In my case, the network card and the soundcard are sharing an > irq. If I don't load the the snd_emu10k1 driver, the network card > works perfectly. Mine is shared as well, with ahc0. Robert Huff From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 01:36:19 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D991116A41A for ; Wed, 31 Oct 2007 01:36:19 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from smtp02.dentaku.gol.com (smtp02.dentaku.gol.com [203.216.5.72]) by mx1.freebsd.org (Postfix) with ESMTP id 8106E13C48A for ; Wed, 31 Oct 2007 01:36:19 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from pat.gol.co.jp ([203.216.1.191] helo=[127.0.0.1]) by smtp02.dentaku.gol.com with esmtpa (Dentaku) id 1In2V3-0007q0-Ti for ; Wed, 31 Oct 2007 10:36:06 +0900 Message-ID: <4727DC05.50501@fusiongol.com> Date: Wed, 31 Oct 2007 10:36:05 +0900 From: Nathan Butcher User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV GOL X-Abuse-Complaints: abuse@gol.com Subject: Re: Problem with ATAPI device on JMicron JMB363 on 7.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 01:36:19 -0000 My apologies to everyone on this issue. The IDE socket of the JMB363 works (I've been using it for while now with CF cards) - it's just that the SATA ATAPI features of the chipset apparently aren't supported yet. I did an update after Soren's latest ata patches, and I noticed that there's a warning message about the chipset's lack of SATA ATAPI support in dmesg just after the chipset is detected. Allow me to feel stupid for a minute, for not seeing this earlier. I am not sure if SATA hard drives now work in IDE mode on this chipset yet. All I know is that my SATA DVD combo drive doesn't work in it no matter what mode the chipset is in (IDE or AHCI). So now my question now is - will the JMB363 SATA ports get any SATA ATAPI support before RELEASE? In the meantime, I'll plug my DVD drive into my Promise card - and while I'm at it, I'll test to see if the Promise cards are working again. From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 03:04:24 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A2A3B16A417 for ; Wed, 31 Oct 2007 03:04:24 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 681A913C4AA for ; Wed, 31 Oct 2007 03:04:24 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.222] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id l9V34FH7005851; Tue, 30 Oct 2007 20:04:16 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <4727F0AF.4060605@freebsd.org> Date: Tue, 30 Oct 2007 20:04:15 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Giorgos Keramidas References: <4726A890.5090705@freebsd.org> <20071030131216.GB91078@kobe.laptop> In-Reply-To: <20071030131216.GB91078@kobe.laptop> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: -mdoc vs. -man X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 03:04:24 -0000 >>I've had some requests from people who want to use the libarchive and >>bsdtar manpages on non-BSD systems that don't support -mdoc. >> >>Any problems if I reworked these manpages to only require -man-old for >>compatibility with these systems? (Other than the inherent >>tediousness of such a project, that is.) > > Yes. At least from me. All good points. Any leads on software that can convert from -mdoc to -man? That would neatly address this issue for me. Tim Kientzle From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 03:07:11 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 073EF16A46B; Wed, 31 Oct 2007 03:07:11 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 978F113C4C4; Wed, 31 Oct 2007 03:07:10 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l9V36xMc099392; Tue, 30 Oct 2007 21:07:00 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4727F13F.1030607@samsco.org> Date: Tue, 30 Oct 2007 21:06:39 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4 MIME-Version: 1.0 To: Jack Vogel References: <2a41acea0710291045m6f1d2acw78c26a455ea3894d@mail.gmail.com> <2a41acea0710301001k60442b26uae186209ac484780@mail.gmail.com> In-Reply-To: <2a41acea0710301001k60442b26uae186209ac484780@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Tue, 30 Oct 2007 21:07:00 -0600 (MDT) X-Spam-Status: No, score=-1.4 required=5.5 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: "gnn@freebsd.org" , FreeBSD Current , FreeBSD Stable List , "freebsd-net@freebsd.org" Subject: Re: RFC: Evolution of the em driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 03:07:11 -0000 Jack Vogel wrote: > On 10/30/07, gnn@freebsd.org wrote: >> At Mon, 29 Oct 2007 10:45:17 -0700, >> Jack Vogel wrote: >>> I have an important decision to make and I thought rather than just make >>> it and spring it on you I'd present the issues and see what opinions were. >>> >>> Our newer hardware uses new features that, more and more, require >>> parallel code paths in the driver. For instance, the 82575 (Zoar) uses >>> what are called 'advanced descriptors', this means different TX path. >>> The 7.0 em driver has this support in it, it just uses a function pointer >>> to handle it. >>> >>> When I add in multiqueue/RSS support it will add even more code >>> that functions this way. >>> >>> What the Linux team did was to split the newer code into a standalone >>> driver, they call it 'igb'. I had originally resisted doing this, but with >>> the development I have been working on the past month I am starting >>> to wonder if it might not be best to follow them. >>> >>> I see 3 possibilities and I'd like feedback, which would you prefer if >>> you have a preference and why. >>> >>> First, keep the driver as is and just live with multiple code paths >>> and features, possibly #ifdef'ed as they appear. >>> >>> Second, split the driver as Linux has into em and igb. The added >>> question then is how to split it, Linux made the line the use of >>> advanced descriptors, so Zoar and after, but I could also see a >>> case for having everything PCI-E/MSI capable being in the new >>> driver. >>> >>> Third, sort of a half-way approach, split up code but not the >>> driver, in other words offer different source files that can be >>> compiled into the driver, so you could have the one big jumbo >>> driver with all in there, or one that will only work with a subset >>> of adapters. This one would probably be the most work, because >>> its a new approach. >> As you're the main maintainer it's your choice. Whatever is easiest >> for you and gives us the most readable code. > > Thanks, I know its my choice, I was just looking for opinions about > the options I had to chose from :) > > I think I've had enough feedback to decide, I think the seperate > driver is the direction. I need to give some thought to where to > make the split. > > Thanks for everyone's feedback. > > Jack There are too many examples to name in every OS of drivers that have tried in vain to support diverging hardware evolutionary paths. if_dc and if_bge are great (or horrible, depending on your perspective) examples of this in FreeBSD. My vote is to nip the madness in the bud on if_em and have two (or more drivers) that support their hardware families well instead of one driver that supports multiple families marginally. Scott From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 05:53:32 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6C97516A469 for ; Wed, 31 Oct 2007 05:53:32 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 5EFB213C4B6 for ; Wed, 31 Oct 2007 05:53:32 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 7B4C11CC079; Tue, 30 Oct 2007 22:36:10 -0700 (PDT) Date: Tue, 30 Oct 2007 22:36:10 -0700 From: Jeremy Chadwick To: "Stephan F. Yaraghchi" Message-ID: <20071031053610.GA10176@eos.sc1.parodius.com> References: <25f52a3d0710300732x425f0c45vde1a29361096c018@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <25f52a3d0710300732x425f0c45vde1a29361096c018@mail.gmail.com> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org Subject: Re: loader breaks with -O2 optimizations X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 05:53:32 -0000 On Tue, Oct 30, 2007 at 03:32:19PM +0100, Stephan F. Yaraghchi wrote: > I found out that the following line in my make.conf causes > the problem: > > CFLAGS= -O2 -funroll-loops -pipe You shouldn't have this in your make.conf. Remove it. This is very likely breaking a lot more than just loader. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 06:04:53 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6667816A417 for ; Wed, 31 Oct 2007 06:04:53 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from smtp02.dentaku.gol.com (smtp02.dentaku.gol.com [203.216.5.72]) by mx1.freebsd.org (Postfix) with ESMTP id 0DD3E13C4A8 for ; Wed, 31 Oct 2007 06:04:53 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from pat.gol.co.jp ([203.216.1.191] helo=[127.0.0.1]) by smtp02.dentaku.gol.com with esmtpa (Dentaku) id 1In5fM-00067d-D8 for ; Wed, 31 Oct 2007 13:58:56 +0900 Message-ID: <47280B90.70106@fusiongol.com> Date: Wed, 31 Oct 2007 13:58:56 +0900 From: Nathan Butcher User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV GOL X-Abuse-Complaints: abuse@gol.com Subject: Re: Problem with ATAPI device on JMicron JMB363 on 7.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 06:04:53 -0000 >There seem to also be certain 'proprietary' (I hope...) issues with >that MB >BIOS. We had tested combinations of BIOS settings extensively, using >PATA CDR, >PATA HDD, PATA <==> SATA converters, and SATA HDD - even an aged IDE >Zip. I haven't noticed any MB issues at all. My BIOS has been updated to the latest "F5" build, and in AHCI mode, the JMB363 detects IDE devices and my SATA DVD drive (as ODD0 or something like that) in the BIOS startup screens. Should I set the JMB to IDE mode, this BIOS screen doesn't appear, but IDE works anyway as it should. Still no SATA DVD drive love.... AFAIK, given what I am seeing, the drive isn't detected because of a FreeBSD issue - as it seems to be clearly detected in the AHCI BIOS at least. If SATA ATAPI support is added in CURRENT, then I'll wait until the modifications trickle into RELENG_7, which is what my system is currently on. Will do another "make build*" in 6 hours and try again. From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 07:20:39 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED4D016A469 for ; Wed, 31 Oct 2007 07:20:39 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp1.yandex.ru (smtp1.yandex.ru [213.180.223.87]) by mx1.freebsd.org (Postfix) with ESMTP id 39A8013C4A3 for ; Wed, 31 Oct 2007 07:20:38 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from ns.kirov.so-cdu.ru ([77.72.136.145]:47809 "EHLO [127.0.0.1]" smtp-auth: "bu7cher" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S8373911AbXJaHPy (ORCPT ); Wed, 31 Oct 2007 10:15:54 +0300 X-Comment: RFC 2476 MSA function at smtp1.yandex.ru logged sender identity as: bu7cher Message-ID: <47282B93.3010801@yandex.ru> Date: Wed, 31 Oct 2007 10:15:31 +0300 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: =?KOI8-R?Q?=3F=3F=3F_Bill_Hacker?= References: <4725558F.6040702@fusiongol.com> <4726BEEE.3070704@yandex.ru> <472778F7.9030405@conducive.net> In-Reply-To: <472778F7.9030405@conducive.net> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: Nathan Butcher , freebsd-current@freebsd.org, blacknova@tut.by, Mark Powell Subject: Re: Problem with ATAPI device on JMicron JMB363 on 7.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 07:20:40 -0000 Bill Hacker wrote: > There seem to also be certain 'proprietary' (I hope...) issues with that > MB BIOS. We had tested combinations of BIOS settings extensively, using > PATA CDR, PATA HDD, PATA <==> SATA converters, and SATA HDD - even an > aged IDE Zip. Yes. Several people reported that theirs issues with jmb363 was fixed after BIOS update. And seem that the "last" BIOS is not mean "stable". -- WBR, Andrey V. Elsukov From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 07:47:57 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2069E16A46B; Wed, 31 Oct 2007 07:47:57 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from gandalf.orthanc.ca (204-174-83-38.static569.dsl.ucc-net.ca [204.174.83.38]) by mx1.freebsd.org (Postfix) with ESMTP id EA51313C4B2; Wed, 31 Oct 2007 07:47:56 +0000 (UTC) (envelope-from lyndon@orthanc.ca) Received: from [192.168.42.7] (peregrin-4 [192.168.42.7]) (authenticated bits=0) by gandalf.orthanc.ca (8.14.1/8.14.1) with ESMTP id l9V717aP000972 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 31 Oct 2007 00:01:08 -0700 (PDT) (envelope-from lyndon@orthanc.ca) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Lyndon Nerenberg Date: Wed, 31 Oct 2007 00:01:02 -0700 To: Doug Barton X-Mailer: Apple Mail (2.752.3) Cc: John Marshall , freebsd-current@freebsd.org Subject: Re: Proposed change to rcorder for ypset X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 07:47:57 -0000 > If anyone is interested in and/or knowledgeable about NIS and would > like to weigh in on the following PR, please feel free. I plan to > commit this change to HEAD sometime next week if there is no > objection. To my mind, the proper solution is to move the /etc/rc.d/ypset functionality into /etc/rc.d/ypbind, and eliminate /etc/rc.d/ypset altogether. ypset(8) is only ever consumed by ypbind(8), so splitting them apart like this just adds needless complexity. I would eliminate the nis_ypset_enable rc.conf variable, and have / etc/rc.d/ypbind invoke ypset(8) directly if nis_ypset_flags is not empty. --lyndon From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 08:17:00 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACCD816A46C; Wed, 31 Oct 2007 08:17:00 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 8945313C4A6; Wed, 31 Oct 2007 08:17:00 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 05B631CC078; Wed, 31 Oct 2007 01:16:39 -0700 (PDT) Date: Wed, 31 Oct 2007 01:16:39 -0700 From: Jeremy Chadwick To: Scott Long Message-ID: <20071031081638.GA13564@eos.sc1.parodius.com> References: <2a41acea0710291045m6f1d2acw78c26a455ea3894d@mail.gmail.com> <2a41acea0710301001k60442b26uae186209ac484780@mail.gmail.com> <4727F13F.1030607@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4727F13F.1030607@samsco.org> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: "gnn@freebsd.org" , FreeBSD Current , FreeBSD Stable List , Jack Vogel , "freebsd-net@freebsd.org" Subject: Re: RFC: Evolution of the em driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 08:17:00 -0000 On Tue, Oct 30, 2007 at 09:06:39PM -0600, Scott Long wrote: > There are too many examples to name in every OS of drivers that have > tried in vain to support diverging hardware evolutionary paths. if_dc > and if_bge are great (or horrible, depending on your perspective) > examples of this in FreeBSD. My vote is to nip the madness in the bud > on if_em and have two (or more drivers) that support their hardware > families well instead of one driver that supports multiple families > marginally. For what it's worth, I agree with Scott. I'd rather see a new and separate driver (presumably igb(4)) than a "hacked up" em(4) driver trying to handle tons of IC revisions. A good example of the insanity the latter causes is nve(4) vs. nfe(4). :-) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 08:21:16 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37E5616A468 for ; Wed, 31 Oct 2007 08:21:16 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id 4F41C13C4C1; Wed, 31 Oct 2007 08:21:15 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47283AFE.3020603@FreeBSD.org> Date: Wed, 31 Oct 2007 09:21:18 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Christoph Friedrichs References: <47270246.4020400@helinet.de> <47277E55.5060104@FreeBSD.org> <47282454.3010108@gmx.net> In-Reply-To: <47282454.3010108@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Christoph Friedrichs , freebsd-current@freebsd.org Subject: Re: Problem with libthr after update X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 08:21:16 -0000 Christoph Friedrichs wrote: > Kris Kennaway wrote: >> Christoph Friedrichs wrote: >>> Hi Guys, >>> >>> I?m relatively new with my freebsd -current box and actual >>> experiencing problems with starting kdm and portupgrade. Everytime I >>> do so the kdm-bin log explodes with this error messages: >>> >>> Fatal error 'Cannot allocate red zone for initial thread' at line 382 >>> in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) >>> Fatal error 'Cannot allocate red zone for initial thread' at line 382 >>> in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) >>> Fatal error 'Cannot allocate red zone for initial thread' at line 382 >>> in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) >>> >>> I googled this problem and found something concering some ruby >>> packages. I did a manual rebuild of >>> >>> ruby-1.8.6_2,1 >>> perl-5.8.8 >>> ruby18-bdb-0.6.2 >>> db41-4.1.25_4 >>> portupgrade-2.3.1,2 >>> >>> With this rebuild problems with portupgrade were solved but kdm keeps >>> refusing to start with same error messages. In UPDATING I found this: >>> >>> 20071009: >>> Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and >>> WITHOUT_LIBTHR are set. >>> >>> Does this probably have something to do with this? >> >> Did you update from an older release of FreeBSD? >> >> Kris >> >> > Yes I did an update from an older release. I previously installed PC-BSD > 1.4 which is running a FreeBSD 6 Stable under hood. Actual im running > > root@helix# uname -a > FreeBSD helix 8.0-CURRENT FreeBSD 8.0-CURRENT #3: Tue Oct 30 09:45:09 > CET 2007 root@helix:/usr/obj/usr/src/sys/SELFMADE i386 > > Christoph You need to complete your update by rebuilding all installed ports. Kris From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 08:59:35 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E4A816A417 for ; Wed, 31 Oct 2007 08:59:35 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Received: from mx.isc.org (mx.isc.org [IPv6:2001:4f8:0:2::1c]) by mx1.freebsd.org (Postfix) with ESMTP id 5618313C4B5 for ; Wed, 31 Oct 2007 08:59:35 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Received: from farside.isc.org (farside.isc.org [IPv6:2001:4f8:3:bb::5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "farside.isc.org", Issuer "ISC CA" (verified OK)) by mx.isc.org (Postfix) with ESMTP id C76A6114028 for ; Wed, 31 Oct 2007 08:59:34 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Received: from manx.plosh.net (manx.vpn.isc.org [149.20.66.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by farside.isc.org (Postfix) with ESMTP id C92DAE6058; Wed, 31 Oct 2007 08:59:34 +0000 (UTC) (envelope-from Peter_Losher@isc.org) Message-ID: <472843FB.2040707@isc.org> Date: Wed, 31 Oct 2007 01:59:39 -0700 From: Peter Losher Organization: ISC User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.95.5 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig0A2F9DAA17724BB7A775B505" Subject: In Memoriam: Jun-ichiro Hagino X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 08:59:35 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0A2F9DAA17724BB7A775B505 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable For those that may not have heard yet. Re: http://undeadly.org/cgi?action=3Darticle&sid=3D20071030220114 -=3D- Jun-ichiro "itojun" Itoh Hagino passed away on October 29, 2007 at the age of 37. To those in the BSD communities he was simply Itojun, best known in his role as IPv6 KAME project core researcher. Itojun did the vast majority of the work to get IPv6 into the BSD network stacks. He was also instrumental in moving IPv6 forward in all aspects through his participation in IETF protocol design meetings. Itojun was helpful to everyone around him, and dedicated to his work. He believed and worked toward making technology available to everyone. He will be missed, and always remembered. -=3D- I had the honor of meeting him in person a couple of years ago, and his boundless enthusiasm was quite evident. Certainly to the BSD community and to the IPv6 community he will be greatly missed. As he was one of the driving forces behind IPv6 adoption; I will spend today turning up some IPv6-aware FreeBSD servers/services internally here at ISC. Best Wishes - Peter --=20 Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow" --------------enig0A2F9DAA17724BB7A775B505 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFHKEP7PtVx9OgEjQgRAhNSAKCxHb8JKzOjcNAURZNR5F6A2yXp4wCgk0Rc mPyEBXGKiqvJKaupxRMMrdE= =GxOv -----END PGP SIGNATURE----- --------------enig0A2F9DAA17724BB7A775B505-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 09:16:46 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F6E016A41A for ; Wed, 31 Oct 2007 09:16:46 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id DB11413C480 for ; Wed, 31 Oct 2007 09:16:45 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: by blah.sun-fish.com (Postfix, from userid 1002) id 17E731B10EE6; Wed, 31 Oct 2007 09:58:22 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on blah.cmotd.com X-Spam-Level: X-Spam-Status: No, score=-3.8 required=5.0 tests=ALL_TRUSTED,BAYES_00, J_CHICKENPOX_61 autolearn=no version=3.2.3 Received: from hater.haters.org (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id 523E21B10EE0; Wed, 31 Oct 2007 09:58:19 +0100 (CET) Message-ID: <472843AB.4080509@moneybookers.com> Date: Wed, 31 Oct 2007 10:58:19 +0200 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.6 (X11/20070918) MIME-Version: 1.0 To: Thomas David Rivers References: <200710301834.l9UIYeW55836@lakes.dignus.com> In-Reply-To: <200710301834.l9UIYeW55836@lakes.dignus.com> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.91.2/4645/Wed Oct 31 08:55:58 2007 on blah.cmotd.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: 7.0 BETA1.5 initial findings... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 09:16:46 -0000 Hi Thomas, Thomas David Rivers wrote: > Just wanted to report some of my results with installing > the BETA1.5 CDs.... with a CD-ONLY install. > > This is on an Intel quad-core with 2G of memory, and 300G SATA > drive and older ATAPI DVD drive (Intel DG33BU motherboard.) > > First; after you partition & label and choose your distributions; > it's time to remove the "BOOTONLY" CD and place DISC1 in the > drive. There's nothing that tells you this.. if you don't > do this, then the process merrily fails at trying to install > everything.. twice over. After that, you have an opportunity > Only twice ? I thought this is forever cycle :) > to try and install again, putting DISC1 in the drive. I'd > suggest a little box saying "remove the BOOTONLY CD, insert DISC1 > and press OK" when it's time to start installing the distributions. > If you have disk1 you do not need boot only CD. You can boot from disk1 and make normal installation. > Second - if you choose the X11 packages in the distributions; > they don't work. The install process complains that it > can't find packages/INDEX on either DISC1 or DISK2. I'm not > sure how to get the X11 packages installed from a CD-only install. > Sorry can't help you here - I never use binary packages (long live ports!) May be next big step after SMP will be fixing sysinstall ;) As sysinstall from unfriendly (for new users) on freebsd 3.X moves more and more to not-working at all. The problem is that sysinstall is not very interesting for developers and even not so advanced sysadmins, can leave almost without it, that's why I think sysinstall doesn't get enough attention. Here is my install procedure: boot disk1 when sysinstall starts go to Custom install create partition,label, MBR. from distribution - go to custom again, select kernel(s?), src, ports & base. commit, reboot, play with /etc/make.conf and your kernel conf csup src and ports, buildworld/kernel/installworld, install from ports and viola :) you have everything you need :) It's just little more complicated if you do this over serial console ;) > - Dave Rivers - > > -- > Work: (919) 676-0847 > Get your mainframe programming tools at http://www.dignus.com > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 09:29:59 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8BF6416A46D for ; Wed, 31 Oct 2007 09:29:59 +0000 (UTC) (envelope-from jhary@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:1f1::2]) by mx1.freebsd.org (Postfix) with ESMTP id EF27713C4AA for ; Wed, 31 Oct 2007 09:29:58 +0000 (UTC) (envelope-from jhary@unsane.co.uk) Received: from prawn.unsane.co.uk (150.117-84-212.staticip.namesco.net [212.84.117.150]) (authenticated bits=0) by unsane.co.uk (8.14.0/8.14.0) with ESMTP id l9V9TgPo097998 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Oct 2007 09:29:43 GMT (envelope-from jhary@unsane.co.uk) Message-ID: <47284AFF.3090000@unsane.co.uk> Date: Wed, 31 Oct 2007 09:29:35 +0000 From: Vince User-Agent: Thunderbird 2.0.0.6 (X11/20071029) MIME-Version: 1.0 To: Thomas David Rivers References: <200710301834.l9UIYeW55836@lakes.dignus.com> In-Reply-To: <200710301834.l9UIYeW55836@lakes.dignus.com> X-Enigmail-Version: 0.95.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: 7.0 BETA1.5 initial findings... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 09:29:59 -0000 Thomas David Rivers wrote: > Just wanted to report some of my results with installing > the BETA1.5 CDs.... with a CD-ONLY install. > > This is on an Intel quad-core with 2G of memory, and 300G SATA > drive and older ATAPI DVD drive (Intel DG33BU motherboard.) > > First; after you partition & label and choose your distributions; > it's time to remove the "BOOTONLY" CD and place DISC1 in the > drive. There's nothing that tells you this.. if you don't > do this, then the process merrily fails at trying to install > everything.. twice over. After that, you have an opportunity > to try and install again, putting DISC1 in the drive. I'd > suggest a little box saying "remove the BOOTONLY CD, insert DISC1 > and press OK" when it's time to start installing the distributions. > Umm bootonly, exactly what it says. Read section 2.13.1 of http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-diff-media.html for an explanation of what each disk contain/can be used for. If you want to install from CD just use the install disks not the bootonly. > Second - if you choose the X11 packages in the distributions; > they don't work. The install process complains that it > can't find packages/INDEX on either DISC1 or DISK2. I'm not > sure how to get the X11 packages installed from a CD-only install. Sorry not sure. I tend to install any packages from ftp or just compile from ports. Vince > > - Dave Rivers - > > -- > Work: (919) 676-0847 > Get your mainframe programming tools at http://www.dignus.com > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 09:43:16 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06CD916A419 for ; Wed, 31 Oct 2007 09:43:16 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.freebsd.org (Postfix) with ESMTP id 99FA213C4BB for ; Wed, 31 Oct 2007 09:43:15 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so188971pyb for ; Wed, 31 Oct 2007 02:42:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; 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=EmtPQRA4bQ19B3jbnW5TkQL4A51AHQZJhwr+DWMjpBg=; b=E+D8Xbz3cBwuUyJX/F/XUL2CTQobQ6x4aZjYkXENGhrV8y2czn+83vrNBvA4SD7TledHV3uabkzEPOrHE8AyCDP99aLDcD5sNMTUb28KCrH+NgA6L8Rbtp8UYMdDudhqwTH6+N/82sGP53UMyMWgq6qV29bP0F6WKS94ZjzOvQo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Z9gu4YGHzuBb5qhuMCFKFkoKo8MZRe9tGLjAa+9fvyi4W3hKOLSKE8zrg/Tz2NYol0LUQT2Delt5udIqvVGkSf59ur3Rb1Ty/LpOQc0qtLv9QmwTNnph8gDp0kYnTJJm8/JYRtrrcMC18ZhPkuMhXtBsJg3iqvdct4+/QCjPjok= Received: by 10.65.44.5 with SMTP id w5mr764149qbj.1193823775368; Wed, 31 Oct 2007 02:42:55 -0700 (PDT) Received: by 10.65.107.3 with HTTP; Wed, 31 Oct 2007 02:42:55 -0700 (PDT) Message-ID: Date: Wed, 31 Oct 2007 09:42:55 +0000 From: "Aryeh Friedman" To: "Thomas David Rivers" In-Reply-To: <200710301834.l9UIYeW55836@lakes.dignus.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200710301834.l9UIYeW55836@lakes.dignus.com> Cc: freebsd-current@freebsd.org Subject: Re: 7.0 BETA1.5 initial findings... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 09:43:16 -0000 Also note that amd64 disk1 fails to boot on some SATA cd/dvd drives (gets upto the end of the device detection but then goes into a finite series of read_fail timeouts on the cd/dvd drive)... Details ICH9 with on board SATA/300 P35 Chipset OEM SATA DVD drive On 10/30/07, Thomas David Rivers wrote: > > Just wanted to report some of my results with installing > the BETA1.5 CDs.... with a CD-ONLY install. > > This is on an Intel quad-core with 2G of memory, and 300G SATA > drive and older ATAPI DVD drive (Intel DG33BU motherboard.) > > First; after you partition & label and choose your distributions; > it's time to remove the "BOOTONLY" CD and place DISC1 in the > drive. There's nothing that tells you this.. if you don't > do this, then the process merrily fails at trying to install > everything.. twice over. After that, you have an opportunity > to try and install again, putting DISC1 in the drive. I'd > suggest a little box saying "remove the BOOTONLY CD, insert DISC1 > and press OK" when it's time to start installing the distributions. > > Second - if you choose the X11 packages in the distributions; > they don't work. The install process complains that it > can't find packages/INDEX on either DISC1 or DISK2. I'm not > sure how to get the X11 packages installed from a CD-only install. > > - Dave Rivers - > > -- > Work: (919) 676-0847 > Get your mainframe programming tools at http://www.dignus.com > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 09:43:41 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF8A116A41A for ; Wed, 31 Oct 2007 09:43:41 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id 30B8913C4A3; Wed, 31 Oct 2007 09:43:41 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47284E4F.5030008@FreeBSD.org> Date: Wed, 31 Oct 2007 10:43:43 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: "Stephan F. Yaraghchi" References: <25f52a3d0710300732x425f0c45vde1a29361096c018@mail.gmail.com> In-Reply-To: <25f52a3d0710300732x425f0c45vde1a29361096c018@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: loader breaks with -O2 optimizations X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 09:43:42 -0000 Stephan F. Yaraghchi wrote: > After making world on a freshly installed 7.0-BETA1 > the system does not boot anymore due to a broken loader: > > > FreeBSD/i386 bootstrap loader, Revision 1.1 > (root@bigblue, Tue Oct 30 11:26:32 CET 2007) > Can't work out which disk we are booting from. > Guessed BIOS device 0xffffffff not found by probes defaulting to disk0: > > panic: free: guard1 fail@ 0x6ded4 from > /usr/src/sys/boot/i386/loader/../../common/module.c:959 > > --> Press a key on the console to reboot <-- > > > I found out that the following line in my make.conf causes > the problem: > > CFLAGS= -O2 -funroll-loops -pipe > > > After changing down to -O1 and making /usr/src/sys/boot again > the systems behaves properly at boot. > > Is this behavior intended? Maybe, what happens if you use just -O2 -pipe? -funroll-loops is not an appropriate thing to be using globally anyway, unless your intention is to randomly make some code slower. Kris From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 10:03:43 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3661B16A417 for ; Wed, 31 Oct 2007 10:03:43 +0000 (UTC) (envelope-from yaraghchi@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.229]) by mx1.freebsd.org (Postfix) with ESMTP id E34C313C481 for ; Wed, 31 Oct 2007 10:03:42 +0000 (UTC) (envelope-from yaraghchi@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so63675nzf for ; Wed, 31 Oct 2007 03:03:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=bGfR3s2LmijirLuL8uPC5cbjby/VikFbtMnhaHBkiyw=; b=U9cwvOw9jsoqse97YRTZx/o6dyXi/SBu2Eg6uN397hCm4y0r27D3GjDSU6WVDnC7aX7OEHFeIZl11RMWEY2oWRlZtqcZJnkWdQQKu+MylAz3iQQS3ty5P9YXdKGh1XHhSMYAjefE18fnYOTog7zEVUB9w3NWEDE1ThXQ6n/K0K4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=UWNOu375kXt+wyroLBu+2GRNLI39Sp730Vugs02lj+/VIuOuc90KKQKs0yS6ktXlygH/yLPP8HtxTHMmfpjw1YsGngLC6Va6zQvGpDt0R6G4WgmB2q7W4rcE4ojwXycOYdC4zkIpGrbbkocExZbuYdcXagUgGKLT1hhmPFxAYs0= Received: by 10.142.86.7 with SMTP id j7mr1957622wfb.1193825000882; Wed, 31 Oct 2007 03:03:20 -0700 (PDT) Received: by 10.143.158.18 with HTTP; Wed, 31 Oct 2007 03:03:20 -0700 (PDT) Message-ID: <25f52a3d0710310303w7138bf5ds92698f1b6af2f655@mail.gmail.com> Date: Wed, 31 Oct 2007 11:03:20 +0100 From: "Stephan F. Yaraghchi" Sender: yaraghchi@gmail.com To: "Kris Kennaway" In-Reply-To: <47284E4F.5030008@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <25f52a3d0710300732x425f0c45vde1a29361096c018@mail.gmail.com> <47284E4F.5030008@FreeBSD.org> X-Google-Sender-Auth: a102d93bbcb9cc32 Cc: freebsd-current@freebsd.org Subject: Re: loader breaks with -O2 optimizations X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 10:03:43 -0000 On 10/31/07, Kris Kennaway wrote: > Stephan F. Yaraghchi wrote: > > After making world on a freshly installed 7.0-BETA1 > > the system does not boot anymore due to a broken loader: > > > > > > FreeBSD/i386 bootstrap loader, Revision 1.1 > > (root@bigblue, Tue Oct 30 11:26:32 CET 2007) > > Can't work out which disk we are booting from. > > Guessed BIOS device 0xffffffff not found by probes defaulting to disk0: > > > > panic: free: guard1 fail@ 0x6ded4 from > > /usr/src/sys/boot/i386/loader/../../common/module.c:959 > > > > --> Press a key on the console to reboot <-- > > > > > > I found out that the following line in my make.conf causes > > the problem: > > > > CFLAGS= -O2 -funroll-loops -pipe > > > > > > After changing down to -O1 and making /usr/src/sys/boot again > > the systems behaves properly at boot. > > > > Is this behavior intended? > > Maybe, what happens if you use just -O2 -pipe? -funroll-loops is not an > appropriate thing to be using globally anyway, unless your intention is > to randomly make some code slower. > > Kris > Hi Kris, I tried all possible combinations of these switches -- only -O2 led to the described behaviour. Anyway, it's very interesting to hear that adding these optimizations to make.conf is not recommended, even that -funroll-loops is possibly slowing down certain code. I'm sure many people use it since it's a common tuning tip found on the web. I read about it in Dru Lavigne's "BSD Hacks" (O'Reilly)... -- Stephan www.deine-stimme-gegen-armut.de From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 10:05:21 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6314716A421 for ; Wed, 31 Oct 2007 10:05:21 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id B933613C465; Wed, 31 Oct 2007 10:05:20 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47285364.9060600@FreeBSD.org> Date: Wed, 31 Oct 2007 11:05:24 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Thomas David Rivers References: <200710301834.l9UIYeW55836@lakes.dignus.com> In-Reply-To: <200710301834.l9UIYeW55836@lakes.dignus.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: 7.0 BETA1.5 initial findings... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 10:05:21 -0000 Thomas David Rivers wrote: > Just wanted to report some of my results with installing > the BETA1.5 CDs.... with a CD-ONLY install. > > This is on an Intel quad-core with 2G of memory, and 300G SATA > drive and older ATAPI DVD drive (Intel DG33BU motherboard.) > > First; after you partition & label and choose your distributions; > it's time to remove the "BOOTONLY" CD and place DISC1 in the > drive. There's nothing that tells you this.. if you don't > do this, then the process merrily fails at trying to install > everything.. twice over. After that, you have an opportunity > to try and install again, putting DISC1 in the drive. I'd > suggest a little box saying "remove the BOOTONLY CD, insert DISC1 > and press OK" when it's time to start installing the distributions. > > Second - if you choose the X11 packages in the distributions; > they don't work. The install process complains that it > can't find packages/INDEX on either DISC1 or DISK2. I'm not > sure how to get the X11 packages installed from a CD-only install. That is expected for beta installs, the packages are typically not yet available until later in the cycle. Kris From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 10:34:13 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 590AB16A468 for ; Wed, 31 Oct 2007 10:34:13 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.178]) by mx1.freebsd.org (Postfix) with ESMTP id F3C8C13C491 for ; Wed, 31 Oct 2007 10:34:12 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so212013pyb for ; Wed, 31 Oct 2007 03:33:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=46Tf3IWgu0w9wEXmZVxYuMfRSAxLT/it+7hp+DyNyg0=; b=ra/UiSH+9QkqgouBq54FCqRFc07gTNKTLFA/OpXnTH10mDT27r3BLTktj4sE9wexK5h/lXI1Ktud6+hBng0b6o5cfu+wA44LM+HVr3M0hNL+udPl1UHvNLZSSBWpfB65GyJHub6eIv1iei2VLVDcQAJOzQFubTDj3BE3nyYbwEM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=ITCWgxXoSsrmBzA150EsTtKsCQipgRviQ6KZSz5IGegcJ6ffMpgYNrEqR1Y2qjSG4wHqsiyTcwChLHVE9Prak37eZNHdMBHsJm9fLdKrMFudwgJWX/jPojpbD5j+LBwgbabO5ksVO8z1i+4d7DOwmod72hmlNH1e5iXQjq9BWHE= Received: by 10.65.180.9 with SMTP id h9mr894077qbp.1193826823051; Wed, 31 Oct 2007 03:33:43 -0700 (PDT) Received: by 10.65.107.3 with HTTP; Wed, 31 Oct 2007 03:33:43 -0700 (PDT) Message-ID: Date: Wed, 31 Oct 2007 10:33:43 +0000 From: "Aryeh Friedman" To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: need if_re patch for 8.0-Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 10:34:13 -0000 About 2 months ago someone posted a custom patch for my particular machine... sad to say for various reasons had to do a complete reinstall and in the process lost all the patches I use(d) [this is the only still needed]... can who ever made the patch please resend it to me? From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 10:36:25 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDAC716A419; Wed, 31 Oct 2007 10:36:25 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id 18C7513C4BF; Wed, 31 Oct 2007 10:36:24 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from kobe.laptop (vader.bytemobile-rio.ondsl.gr [83.235.57.37]) (authenticated bits=128) by igloo.linux.gr (8.14.1/8.14.1/Debian-9) with ESMTP id l9VAXU9G012140 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 31 Oct 2007 12:33:39 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.1/8.14.1) with ESMTP id l9VAXOn3002574; Wed, 31 Oct 2007 12:33:24 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by kobe.laptop (8.14.1/8.14.1/Submit) id l9VAXO5n002573; Wed, 31 Oct 2007 12:33:24 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Wed, 31 Oct 2007 12:33:24 +0200 From: Giorgos Keramidas To: Tim Kientzle , Ruslan Ermilov Message-ID: <20071031103324.GB1795@kobe.laptop> References: <4726A890.5090705@freebsd.org> <20071030131216.GB91078@kobe.laptop> <4727F0AF.4060605@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4727F0AF.4060605@freebsd.org> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.112, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.29, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: current@freebsd.org Subject: Re: -mdoc vs. -man X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 10:36:25 -0000 On 2007-10-30 20:04, Tim Kientzle wrote: >>> I've had some requests from people who want to use the >>> libarchive and bsdtar manpages on non-BSD systems that don't >>> support -mdoc. >>> >>> Any problems if I reworked these manpages to only require >>> -man-old for compatibility with these systems? (Other than >>> the inherent tediousness of such a project, that is.) >> >> Yes. At least from me. > > All good points. Any leads on software that can convert from > -mdoc to -man? That would neatly address this issue for me. Not really. I haven't really used -man for any substantial amount of work in years. Maybe Ruslan, who is our groff-guru knows about something? - Giorgos From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 02:17:16 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7952516A417 for ; Wed, 31 Oct 2007 02:17:16 +0000 (UTC) (envelope-from matheusber@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 5388313C4C2 for ; Wed, 31 Oct 2007 02:17:16 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so2807369waf for ; Tue, 30 Oct 2007 19:17:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=jk+3LwmXBpcAwMD53iWY6xGk4E3fDx6/BORL/QF7V/Q=; b=uVTx4xVmgAv5CnN2ILy2+rgcZj5tzxJJ2tXAQMe6JowFklMtdTKBnE3RbNqMmaolucmWad4DX7wO54brFpm9Wi8mkAMPvbUDjrXdHvcsR4bpZYWpAa8bFems3Zyj5RGGv/u4qCRM8B0ueXWhSlROpwE4Xkz/TXSP5/UQTJCLFgM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=QsJ9dRpxriUgKBnu52txvbKcKJf+5U9u1R/WrBhaawpBQxCaGCfhJ/sP9R9Zgsby28TL353jGWU1xLOQQ7aSE2ux8P51fwFr3eRDJRu27BmAIfbwYWOlJRDfSFu9uNAEhM2+9GvxgzrQJXOcUlsfmitHRfXlC9M9KuBU6AOzUeY= Received: by 10.114.120.1 with SMTP id s1mr1573225wac.1193795322767; Tue, 30 Oct 2007 18:48:42 -0700 (PDT) Received: by 10.115.77.9 with HTTP; Tue, 30 Oct 2007 18:48:42 -0700 (PDT) Message-ID: <4956a5e50710301848i50fa9b19ube28113cf29c13d5@mail.gmail.com> Date: Tue, 30 Oct 2007 22:48:42 -0300 From: Nenhum_de_Nos To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mailman-Approved-At: Wed, 31 Oct 2007 11:55:59 +0000 Subject: problems: nvidia latest driver and 7.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 02:17:16 -0000 first of all, since the RELENG_7 birth, I never know where to post 7.0-BETA stuff. well, here I go ... this is a fresh BETA1 install, did it yesterday. xorg and half gnome completed, I tried to make nvidia work and nothing. the kernel module kldloads ok, but nothing gets posted to dmesg(/var/log/messages) there are some sysctl things: [matheus@xxx /usr/home/matheus]$ sysctl hw.nvidia hw.nvidia.version: NVIDIA UNIX x86 Kernel Module 100.14.19 Tue Sep 18 13:59:09 PDT 2007 hw.nvidia.registry.EnableVia4x: 0 hw.nvidia.registry.EnableALiAGP: 0 hw.nvidia.registry.NvAGP: 1 hw.nvidia.registry.EnableAGPSBA: 0 hw.nvidia.registry.EnableAGPFW: 0 hw.nvidia.registry.SoftEDIDs: 1 hw.nvidia.registry.Mobile: 4294967295 hw.nvidia.registry.ResmanDebugLevel: 4294967295 hw.nvidia.registry.FlatPanelMode: 0 hw.nvidia.registry.DevicesConnected: 0 hw.nvidia.registry.RmLogonRC: 1 hw.nvidia.registry.DetectPrimaryVga: 1 hw.nvidia.registry.dwords: but no /dev/nvctl (or whatever it is) and when I startx it just says me the /dev entry is not there and no fun at all can be :/ [matheus@darkside /usr/home/matheus]$ uname -a FreeBSD xxx 7.0-BETA1 FreeBSD 7.0-BETA1 #0: Tue Oct 30 00:28:27 BRT 2007 root@:/usr/obj/usr/src/sys/xxx i386 if anyone has any clue, I'm using i386 just for nvidia(amd64 machine) thanks, matheus -- We will call you cygnus, The God of balance you shall be From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 07:12:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46A9D16A419 for ; Wed, 31 Oct 2007 07:12:18 +0000 (UTC) (envelope-from christophfriedrichs@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id AD30413C494 for ; Wed, 31 Oct 2007 07:12:17 +0000 (UTC) (envelope-from christophfriedrichs@gmx.net) Received: (qmail invoked by alias); 31 Oct 2007 06:44:37 -0000 Received: from fw.helinet.de (EHLO [192.168.99.167]) [212.37.38.2] by mail.gmx.net (mp005) with SMTP; 31 Oct 2007 07:44:37 +0100 X-Authenticated: #1804469 X-Provags-ID: V01U2FsdGVkX1+V4nNe+EOVrtP2DEJpYlXIL196P6vwH3qH+PDFKR xgbn6oXapcIlhU Message-ID: <47282454.3010108@gmx.net> Date: Wed, 31 Oct 2007 07:44:36 +0100 From: Christoph Friedrichs User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: Kris Kennaway References: <47270246.4020400@helinet.de> <47277E55.5060104@FreeBSD.org> In-Reply-To: <47277E55.5060104@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Mailman-Approved-At: Wed, 31 Oct 2007 11:55:48 +0000 Cc: Christoph Friedrichs , freebsd-current@freebsd.org Subject: Re: Problem with libthr after update X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 07:12:18 -0000 Kris Kennaway wrote: > Christoph Friedrichs wrote: >> Hi Guys, >> >> I?m relatively new with my freebsd -current box and actual >> experiencing problems with starting kdm and portupgrade. Everytime I >> do so the kdm-bin log explodes with this error messages: >> >> Fatal error 'Cannot allocate red zone for initial thread' at line 382 >> in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) >> Fatal error 'Cannot allocate red zone for initial thread' at line 382 >> in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) >> Fatal error 'Cannot allocate red zone for initial thread' at line 382 >> in file /usr/src/lib/libthr/thread/thr_init.c (errno = 12) >> >> I googled this problem and found something concering some ruby >> packages. I did a manual rebuild of >> >> ruby-1.8.6_2,1 >> perl-5.8.8 >> ruby18-bdb-0.6.2 >> db41-4.1.25_4 >> portupgrade-2.3.1,2 >> >> With this rebuild problems with portupgrade were solved but kdm keeps >> refusing to start with same error messages. In UPDATING I found this: >> >> 20071009: >> Setting WITHOUT_LIBPTHREAD now means WITHOUT_LIBKSE and >> WITHOUT_LIBTHR are set. >> >> Does this probably have something to do with this? > > Did you update from an older release of FreeBSD? > > Kris > > Yes I did an update from an older release. I previously installed PC-BSD 1.4 which is running a FreeBSD 6 Stable under hood. Actual im running root@helix# uname -a FreeBSD helix 8.0-CURRENT FreeBSD 8.0-CURRENT #3: Tue Oct 30 09:45:09 CET 2007 root@helix:/usr/obj/usr/src/sys/SELFMADE i386 Christoph From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 07:17:48 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 426AD16A479; Wed, 31 Oct 2007 07:17:48 +0000 (UTC) (envelope-from goran.lowkrantz@ismobile.com) Received: from mail.ismobile.com (mail.ismobile.com [62.119.44.68]) by mx1.freebsd.org (Postfix) with ESMTP id E5BC613C4B6; Wed, 31 Oct 2007 07:17:47 +0000 (UTC) (envelope-from goran.lowkrantz@ismobile.com) Received: from mail.ismobile.com (localhost [127.0.0.1]) by mail.ismobile.com (Postfix) with ESMTP id 7404B33C02; Wed, 31 Oct 2007 07:57:56 +0100 (CET) DKIM-Signature: v=0.5; a=rsa-sha1; c=relaxed; d=ismobile.com; h=received:date:from:to:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type:content-transfer-encoding:content-disposition; q=dns/txt; s=selector1; bh=WvsAbmucusxo/kViVXQ9pLjzCBE=; b=DCSyGgKZBKW9hEpgzw/n0+fDkbSkIYalq7x3LH2zt+3rGcX2v24GAYHGS2iusxOgakNe+Sx7/SprIQjNB7s4MsfWf30ObPf4+oJf1CcgrSPkrZw0RzjeaNTnfEy70o5CX2nmaBbrfc0MvxyvfygSDRYKn4stW6Iavq2QKJPOSos= Received: from [10.255.253.2] (modgunn.iii-norr.com [213.242.135.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.ismobile.com (Postfix) with ESMTP id 558A933C01; Wed, 31 Oct 2007 07:57:56 +0100 (CET) Date: Wed, 31 Oct 2007 07:57:55 +0100 From: Goran Lowkrantz To: Jack Vogel , freebsd-net@freebsd.org, FreeBSD Stable List , FreeBSD Current Message-ID: In-Reply-To: <2a41acea0710301016u4a0008dfjc83170257337863c@mail.gmail.com> References: <2a41acea0710301016u4a0008dfjc83170257337863c@mail.gmail.com> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Mailman-Approved-At: Wed, 31 Oct 2007 11:55:36 +0000 Cc: Subject: Re: em watchdog problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 07:17:48 -0000 Hi Jack, In my case, yes but only under higher loads, specifically when Amanda=20 started receive the backup data. At lower loads, like the check or sizing,=20 no problems. Best regards, G=F6ran L --On Tuesday, October 30, 2007 10:16 -0700 Jack Vogel =20 wrote: > This morning I had an idea about what the source of the watchdog > problem is. Also, we have repro'd at least one type of watchdog > inhouse. > > One question, is this problem only happening for those running > STABLE with the 6.6.6 merged driver? > > We found the problem does not seem to happen on 7.0. > > Right now my suspicion is that the FAST irq handling is > again causing a problem. I am experimenting with variations > to the code today to be sure whats going on, and hopefully > fixing it. > > Cheers, > > Jack > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" ................................................... the future isMobile Goran Lowkrantz System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Lule=E5, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ............................................... From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 11:58:07 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D9FB16A419 for ; Wed, 31 Oct 2007 11:58:07 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id C1B2413C494 for ; Wed, 31 Oct 2007 11:58:06 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 9628B45E97; Wed, 31 Oct 2007 10:52:18 +0100 (CET) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 9A14A45683; Wed, 31 Oct 2007 10:52:14 +0100 (CET) Date: Wed, 31 Oct 2007 10:52:13 +0100 From: Pawel Jakub Dawidek To: Artem Kuchin Message-ID: <20071031095213.GG8068@garage.freebsd.pl> References: <00f101c819f7$833d5370$0c00a8c0@Artem> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4LwthZj+AV2mq5CX" Content-Disposition: inline In-Reply-To: <00f101c819f7$833d5370$0c00a8c0@Artem> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-current@freebsd.org Subject: Re: Problems with gjournal or something else. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 11:58:07 -0000 --4LwthZj+AV2mq5CX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 29, 2007 at 09:46:59AM +0300, Artem Kuchin wrote: > I am experiencing a very weird problem with filesystem > and it seems to be related to gjournal. >=20 > It is FreeBSD 7-BETA1 > RAID controller: 3WARE 7500x > device driver: twe > SMP enabled (Pentium D) > Mirror raid. >=20 > I have created the following partitions: >=20 > twed1s1a 1100MB * > twed1s1b swap 1024MB SWAP > twed1s1d 5120MB * > twed1s1e 30720MB * > twed1s1f 261GB * >=20 > did reboot just is case something is cached. >=20 > Then did: >=20 > newfs -J -b 8192 -f 1024 -g 50000 -h 20 -i 40960 /dev/twed1s1f >=20 > gjournal load > gjournal label -f /dev/twed1s1f > tunefs -J enable -n disable /dev/twed1s1f > mount -o noatime /dev/twed1s1f.journal /NEW/suit It's wrong order. See gjournal(8) manual page, EXAMPLES section. You cannot create file system and then put journal on the same partition. gjournal would warn you about that, but you used force (-f) option. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --4LwthZj+AV2mq5CX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHKFBNForvXbEpPzQRAmC/AJ9MvlvEylVSNwkPNfXsJbkB12vQ3gCghUOW RnPSZxs9G9ud5QPmuu4DwKM= =YTgP -----END PGP SIGNATURE----- --4LwthZj+AV2mq5CX-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 11:58:07 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 687EE16A420 for ; Wed, 31 Oct 2007 11:58:07 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id 067C213C4A7 for ; Wed, 31 Oct 2007 11:58:06 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 9A3D745E90; Wed, 31 Oct 2007 10:54:35 +0100 (CET) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id D0E7045683; Wed, 31 Oct 2007 10:54:29 +0100 (CET) Date: Wed, 31 Oct 2007 10:54:28 +0100 From: Pawel Jakub Dawidek To: Adam McDougall Message-ID: <20071031095428.GH8068@garage.freebsd.pl> References: <20071029024356.GR3612@egr.msu.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SBT+cnFS/G3NVgv4" Content-Disposition: inline In-Reply-To: <20071029024356.GR3612@egr.msu.edu> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-current@freebsd.org Subject: Re: zfs stuck, cannot do any I/O, processes in Disk Wait X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 11:58:07 -0000 --SBT+cnFS/G3NVgv4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 28, 2007 at 10:43:56PM -0400, Adam McDougall wrote: > I think I have had this happen at least once before, but someone else > rebooted the system before I could see it. I have a server with a=20 > number of zfs filesystems mounted from a raidz, but it won't transfer > any data. I'm not sure why its stuck. It is running 7.0-PRERELEASE > Wed Oct 17 and I'm pretty sure it is WITHOUT vm_kern.c.2.patch. The > system is amd64 and I have not seen a kmem panic since I raised kmem > to 1.5G. =20 >=20 > I logged in to scp a file off of zfs, was able to ls -l to see the file > but the scp hung before transferring any bytes. Now I cannot do a ls -l > in that directory, /z. I noticed several days worth of rsync processes > stuck in disk wait, it must have been in this state for several days. > I have no urgent need to reboot this system, its more important to try > to get a permanent fix. Please let me know what other information I=20 > can provide. =20 I'm afraid you need to do some debugging on your own. I'd start from compiling INVARIANTS, INVARIANT_SUPPORT and WITNESS in. You may want to take a look at developers handbook to see how to obtain some informations from DDB. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --SBT+cnFS/G3NVgv4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHKFDUForvXbEpPzQRArbaAJ4xWDJewTWOBWKrWC4vBydNAR30hQCg4Ixe asCy7V5FJUbhFX8+Rgca2yU= =UBnB -----END PGP SIGNATURE----- --SBT+cnFS/G3NVgv4-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 12:50:35 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D0E7F16A419 for ; Wed, 31 Oct 2007 12:50:35 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by mx1.freebsd.org (Postfix) with ESMTP id 60A6B13C48E for ; Wed, 31 Oct 2007 12:50:35 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so109278nfb for ; Wed, 31 Oct 2007 05:50:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:subject:from:to:cc:in-reply-to:references:content-type:organization:date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=sM+J2A3X77zLNW3nA86hA30IdbcmcDXsSd9ppJEU/hg=; b=Al3WEaARFm/gee+bn6y6umnAx/BbNfo9ZBEOGPzsudSqC6HvpB/5N0BcMg2kcf9mvc2Bq5P+p4wIpSFBEC1k9T0y5Nvffd4Q4pKtgIYBBaugcTxN4wE/220mu8HjU9sXzWjWD5U8vX244KLokxuCXdXFWlwsQShP4eM8VWh9krY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:subject:from:to:cc:in-reply-to:references:content-type:organization:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=BnsTl9otFriFag44McQprjs1ABJamDp/HyPZio5VdkB6X9ZJobg/hM5BjBJQPKyyJkIjgXVcGW+24GNodNRIQf6y9bxTwuLztRvdjwr1Dg5ok7mK4XcJFAU5lUKhLm8Gvrx0S4pZHaUvuLui2z/Qs/ySy5EkvmZwPQwRD5f34dk= Received: by 10.86.62.3 with SMTP id k3mr6562448fga.1193835006182; Wed, 31 Oct 2007 05:50:06 -0700 (PDT) Received: from ?10.0.100.2? ( [89.176.79.57]) by mx.google.com with ESMTPS id 28sm880921fkx.2007.10.31.05.50.01 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 31 Oct 2007 05:50:01 -0700 (PDT) From: Michal Varga To: Nenhum_de_Nos In-Reply-To: <4956a5e50710301848i50fa9b19ube28113cf29c13d5@mail.gmail.com> References: <4956a5e50710301848i50fa9b19ube28113cf29c13d5@mail.gmail.com> Content-Type: text/plain Organization: Stonehenge Date: Wed, 31 Oct 2007 13:50:00 +0100 Message-Id: <1193835000.868.7.camel@xenon.stonehenge.sk> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: problems: nvidia latest driver and 7.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 12:50:35 -0000 On Tue, 2007-10-30 at 22:48 -0300, Nenhum_de_Nos wrote: > first of all, since the RELENG_7 birth, I never know where to post > 7.0-BETA stuff. well, here I go ... > > this is a fresh BETA1 install, did it yesterday. xorg and half gnome > completed, I tried to make nvidia work and nothing. > > the kernel module kldloads ok, but nothing gets posted to > dmesg(/var/log/messages) I had one user reporting the same thing here, it seems that removing freebsd's AGP driver from boot/loader.conf (and kernel, if you have it compiled in) and using driver's builtin nvAGP helped him. Did you try this, by a chance? Also, what is your card's model? ,. -- Michal Varga Stonehenge From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 12:52:54 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC5EF16A418; Wed, 31 Oct 2007 12:52:54 +0000 (UTC) (envelope-from henrik@brixandersen.dk) Received: from solow.pil.dk (relay.pil.dk [195.41.47.164]) by mx1.freebsd.org (Postfix) with ESMTP id 9750813C48E; Wed, 31 Oct 2007 12:52:54 +0000 (UTC) (envelope-from henrik@brixandersen.dk) Received: from tirith.brixandersen.dk (osgiliath.brixandersen.dk [87.53.223.189]) by solow.pil.dk (Postfix) with ESMTP id 92D9B1CC0B8; Wed, 31 Oct 2007 13:15:49 +0100 (CET) Received: by tirith.brixandersen.dk (Postfix, from userid 1001) id C283F1141D; Wed, 31 Oct 2007 13:15:48 +0100 (CET) Date: Wed, 31 Oct 2007 13:15:48 +0100 From: Henrik Brix Andersen To: Pawel Jakub Dawidek Message-ID: <20071031121548.GD988@tirith.brixandersen.dk> Mail-Followup-To: Pawel Jakub Dawidek , Claus Guttesen , freebsd-fs@freebsd.org, freebsd-current@freebsd.org References: <20071005000046.GC92272@garage.freebsd.pl> <20071008121523.GM2327@garage.freebsd.pl> <20071015082629.GB1290@tirith.brixandersen.dk> <20071015094716.GG10170@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Izn7cH1Com+I3R9J" Content-Disposition: inline In-Reply-To: <20071015094716.GG10170@garage.freebsd.pl> X-PGP-Key: http://www.brixandersen.dk/files/HenrikBrixAndersen.asc User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Claus Guttesen Subject: Re: ZFS kmem_map too small. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 12:52:55 -0000 --Izn7cH1Com+I3R9J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Pawel, On Mon, Oct 15, 2007 at 11:47:16AM +0200, Pawel Jakub Dawidek wrote: > This looks like VFS deadlock between process 42575 and 42585. You > debugging is really nice, but unfortunately there is no backtrace of > process 42575, so we don't know where and why it's stuck... >=20 > Can you next time take 'show lockedvnods', 'show alllocks' (as you did > this time), but also 'alltrace'? Here's a new debug session with the above requested information: http://www.brixandersen.dk/tmp/zfs-rsync-debug.2.txt As you can see, there were a couple of LORs before I entered the debugger. At least one of these (the last one) appeared when trying to list the files in one of the zfs filesystems, where rsync was hanging. This is with RELENG_7 from Thu Oct 25 14:30:37 CEST 2007. Regards, Brix --=20 Henrik Brix Andersen --Izn7cH1Com+I3R9J Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: GnuPG signed iD8DBQFHKHHzv+Q4flTiePgRApHAAKCyyZIAFik2FZckqseows4I+3gszgCeNsaS i9pP1XQkONml0Ts3/3EYJ4s= =53rb -----END PGP SIGNATURE----- --Izn7cH1Com+I3R9J-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 12:56:59 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC45916A417 for ; Wed, 31 Oct 2007 12:56:59 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id 964CE13C4A3 for ; Wed, 31 Oct 2007 12:56:59 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: by blah.sun-fish.com (Postfix, from userid 1002) id D314F1B10EED; Wed, 31 Oct 2007 13:30:52 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on blah.cmotd.com X-Spam-Level: X-Spam-Status: No, score=-3.8 required=5.0 tests=ALL_TRUSTED,BAYES_00, J_CHICKENPOX_26 autolearn=no version=3.2.3 Received: from hater.haters.org (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id 080EF1B10EBB; Wed, 31 Oct 2007 13:30:36 +0100 (CET) Message-ID: <4728756B.4020609@moneybookers.com> Date: Wed, 31 Oct 2007 14:30:35 +0200 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.6 (X11/20070918) MIME-Version: 1.0 To: Nenhum_de_Nos References: <4956a5e50710301848i50fa9b19ube28113cf29c13d5@mail.gmail.com> In-Reply-To: <4956a5e50710301848i50fa9b19ube28113cf29c13d5@mail.gmail.com> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.91.2/4646/Wed Oct 31 11:41:08 2007 on blah.cmotd.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: problems: nvidia latest driver and 7.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 12:57:00 -0000 Nenhum_de_Nos wrote: > first of all, since the RELENG_7 birth, I never know where to post > 7.0-BETA stuff. well, here I go ... > > this is a fresh BETA1 install, did it yesterday. xorg and half gnome > completed, I tried to make nvidia work and nothing. > > the kernel module kldloads ok, but nothing gets posted to > dmesg(/var/log/messages) > > there are some sysctl things: > > [matheus@xxx /usr/home/matheus]$ sysctl hw.nvidia > hw.nvidia.version: NVIDIA UNIX x86 Kernel Module 100.14.19 Tue Sep > 18 13:59:09 PDT 2007 > hw.nvidia.registry.EnableVia4x: 0 > hw.nvidia.registry.EnableALiAGP: 0 > hw.nvidia.registry.NvAGP: 1 > hw.nvidia.registry.EnableAGPSBA: 0 > hw.nvidia.registry.EnableAGPFW: 0 > hw.nvidia.registry.SoftEDIDs: 1 > hw.nvidia.registry.Mobile: 4294967295 > hw.nvidia.registry.ResmanDebugLevel: 4294967295 > hw.nvidia.registry.FlatPanelMode: 0 > hw.nvidia.registry.DevicesConnected: 0 > hw.nvidia.registry.RmLogonRC: 1 > hw.nvidia.registry.DetectPrimaryVga: 1 > hw.nvidia.registry.dwords: > > but no /dev/nvctl (or whatever it is) and when I startx it just says > me the /dev entry is not there and no fun at all can be :/ > > [matheus@darkside /usr/home/matheus]$ uname -a > FreeBSD xxx 7.0-BETA1 FreeBSD 7.0-BETA1 #0: Tue Oct 30 00:28:27 BRT > 2007 root@:/usr/obj/usr/src/sys/xxx i386 > > if anyone has any clue, I'm using i386 just for nvidia(amd64 machine) > > thanks, > > matheus > > add to /boot/loader.conf nvidia_load="YES" and reboot. May be you have device vga which blocks access to the card, so if you load nvidia module before the kernel .. -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 13:43:51 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A61CC16A46C for ; Wed, 31 Oct 2007 13:43:51 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id E648413C4AA for ; Wed, 31 Oct 2007 13:43:50 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 6184C20A2; Wed, 31 Oct 2007 14:35:20 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id D4B8220A0; Wed, 31 Oct 2007 14:35:19 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id CC08884462; Wed, 31 Oct 2007 14:35:19 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Jeremy Chadwick References: <25f52a3d0710300732x425f0c45vde1a29361096c018@mail.gmail.com> <20071031053610.GA10176@eos.sc1.parodius.com> Date: Wed, 31 Oct 2007 14:35:19 +0100 In-Reply-To: <20071031053610.GA10176@eos.sc1.parodius.com> (Jeremy Chadwick's message of "Tue\, 30 Oct 2007 22\:36\:10 -0700") Message-ID: <86ir4nxv8o.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, "Stephan F. Yaraghchi" Subject: Re: loader breaks with -O2 optimizations X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 13:43:51 -0000 Jeremy Chadwick writes: > Stephan F. Yaraghchi writes: > > I found out that the following line in my make.conf causes > > the problem: > >=20 > > CFLAGS=3D -O2 -funroll-loops -pipe > You shouldn't have this in your make.conf. Remove it. This is very > likely breaking a lot more than just loader. Uh, no. Please stop spreading FUD. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 14:03:14 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8A3416A468 for ; Wed, 31 Oct 2007 14:03:14 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.178]) by mx1.freebsd.org (Postfix) with ESMTP id 9054413C49D for ; Wed, 31 Oct 2007 14:03:13 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so308519pyb for ; Wed, 31 Oct 2007 07:02:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=+8W8Bma+VkkbFwqYu/jdxzRZebPwlv2ho1CvdWzPn74=; b=KU1PRK7FU29mgZTmA9WvjK7YtrV1KNDt2T6nE8sGQ/qfbF4n44K1SHm3rMzW3GmkOjb5S7CjQ4eSV7TpycpE0exFh/psKhvBOgvaDb5HKXAmAzIR8LaUj3s3loU4eainD81A3KCxlf1aDxkBbGScH4OUjeLG38u0cUYz5cB/Mmg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Z/XVTZCU3XlHob2skETBBWtIMZCq9V/W7h3Z6Kn1FTKRDmmGXq7VIjymTtox5W9/TWaSJ4gWgwRfTFk4BFaSoFLvRKbEmUAfON7V3OI8YtEAI5Rb6e7/VNCiRDDUuNIYEoEVi0BkeP2H3hkqleEkXedsnIrbNPva3V0CPsRfI74= Received: by 10.35.91.1 with SMTP id t1mr10236043pyl.1193839376258; Wed, 31 Oct 2007 07:02:56 -0700 (PDT) Received: by 10.35.110.17 with HTTP; Wed, 31 Oct 2007 07:02:56 -0700 (PDT) Message-ID: <8cb6106e0710310702w774c3c39sdcc9bf4fcf87d043@mail.gmail.com> Date: Wed, 31 Oct 2007 10:02:56 -0400 From: "Josh Carroll" To: "Kris Kennaway" In-Reply-To: <47284E4F.5030008@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <25f52a3d0710300732x425f0c45vde1a29361096c018@mail.gmail.com> <47284E4F.5030008@FreeBSD.org> Cc: freebsd-current@freebsd.org, "Stephan F. Yaraghchi" Subject: Re: loader breaks with -O2 optimizations X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: josh.carroll@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 14:03:15 -0000 > Maybe, what happens if you use just -O2 -pipe? -funroll-loops is not an > appropriate thing to be using globally anyway, unless your intention is > to randomly make some code slower. I encountered the same thing in 7.0-BETA1 and resolved it with an edit to make.conf, specifically: .if ! ${.CURDIR:M*/boot/i386/boot2*} CFLAGS+=-O2 -pipe CXXFLAGS+=-O2 -pipe .endif That way, everything else in world is built with -O2 (which I have never had a problem with, by the way), but loader's CFLAGS are retained. The crux of the problem is that gcc takes the LAST -O option as the effective one. That is: gcc -Os ... -O2 is the equivalent of: gcc -O2 ... Which is exactly what's happening in this case (the loader Makefile sets CFLAGS to include -Os to optimize for size). Short of finding a way to prepend to CFLAGS so that a Makefile's CFLAGS are appended to what is defined in make.conf, I don't see another way around this. The make.conf hack seems to work, though. Regards, Josh From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 14:16:46 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E09E16A417 for ; Wed, 31 Oct 2007 14:16:46 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id D461C13C4B0 for ; Wed, 31 Oct 2007 14:16:45 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: by blah.sun-fish.com (Postfix, from userid 1002) id 75A131B10EA4; Wed, 31 Oct 2007 15:04:26 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on blah.cmotd.com X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.3 Received: from hater.haters.org (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id B4FC61B10EEB; Wed, 31 Oct 2007 15:04:23 +0100 (CET) Message-ID: <47288B67.8030600@moneybookers.com> Date: Wed, 31 Oct 2007 16:04:23 +0200 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.6 (X11/20070918) MIME-Version: 1.0 To: Nenhum_de_Nos References: <4956a5e50710301848i50fa9b19ube28113cf29c13d5@mail.gmail.com> <4728756B.4020609@moneybookers.com> <4956a5e50710310645v2ff11ftc51065fdf35d09a4@mail.gmail.com> In-Reply-To: <4956a5e50710310645v2ff11ftc51065fdf35d09a4@mail.gmail.com> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.91.2/4646/Wed Oct 31 11:41:08 2007 on blah.cmotd.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: problems: nvidia latest driver and 7.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 14:16:46 -0000 Hi, Nenhum_de_Nos wrote: > On 10/31/07, Stefan Lambrev wrote: > >> add to /boot/loader.conf >> nvidia_load="YES" >> and reboot. >> May be you have device vga which blocks access to the card, so if you >> load nvidia module before the kernel .. >> > > i did it, and no good :( > > Michal Varga : > > this is a GeForce Go 7600 PCIe from an asus F3T notebook. when I > installed the port, I didnt marl to use FreeBSD agp driver. so by this > info I assume I'm using nvidia's. is that right ? > > it is really annoying using without the driver, I cant even watch a > video. frame dropping and everything is slow :( > > I also tried the 97xx driver and no luck also :( > > matheus > > Well I'm not sure what exactly is your problem, but this is how I get my driver working: /boot/loader.conf nvidia_load="YES" linux_load="YES" cd /usr/ports/x11/nvidia-driver && make config everything except AGP is selected. I'm using and this sysctl - compat.linux.osrelease=2.6.16 but nvidia driver should work without problems with default 2.4.2. And your card is too new to use legacy driver :) just go for the latest. Also if your card is detected you should have hw.nvidia.cards.0.XX too. can you provide dmesg and pciconf -vl ? -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 14:28:36 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8B1916A420; Wed, 31 Oct 2007 14:28:36 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id A34C613C4A6; Wed, 31 Oct 2007 14:28:35 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 4093B208D; Wed, 31 Oct 2007 15:18:13 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 320CC2088; Wed, 31 Oct 2007 15:18:13 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id 2292E8444A; Wed, 31 Oct 2007 15:18:13 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Jeremy Chadwick References: <20071027101312.GA42516@eos.sc1.parodius.com> Date: Wed, 31 Oct 2007 15:18:13 +0100 In-Reply-To: <20071027101312.GA42516@eos.sc1.parodius.com> (Jeremy Chadwick's message of "Sat\, 27 Oct 2007 03\:13\:12 -0700") Message-ID: <86bqafxt96.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, Rob Zietlow Subject: Re: [7.0-Beta] can no longer ssh into just upgraded host X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 14:28:37 -0000 Jeremy Chadwick writes: > On Fri, Oct 26, 2007 at 01:47:07PM -0500, Rob Zietlow wrote: >> #ssh -vv 192.168.8.163 >> OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003 >> debug1: Reading configuration data /etc/ssh/ssh_config >> debug1: Applying options for * >> debug2: ssh_connect: needpriv 0 >> debug1: Connecting to 192.168.8.163 [192.168.8.163] port 22. >> debug1: Connection established. >> debug1: identity file /home/$USER/.ssh/identity type -1 >> debug1: identity file /home/$USER/.ssh/id_rsa type -1 >> debug1: identity file /home/$USER/.ssh/id_dsa type -1 >> ssh_exchange_identification: read: Connection reset by peer > > Sounds like it might be a PAM-related problem. Have you looked > at /var/log/messages or "dmesg -a"? What makes you think it might be PAM-related? They don't even get as far as exchanging version strings. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 14:38:36 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1FB9616A419 for ; Wed, 31 Oct 2007 14:38:36 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 0C2F113C481 for ; Wed, 31 Oct 2007 14:38:36 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 4E4071CC076; Wed, 31 Oct 2007 07:30:10 -0700 (PDT) Date: Wed, 31 Oct 2007 07:30:10 -0700 From: Jeremy Chadwick To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= Message-ID: <20071031143010.GA21646@eos.sc1.parodius.com> References: <25f52a3d0710300732x425f0c45vde1a29361096c018@mail.gmail.com> <20071031053610.GA10176@eos.sc1.parodius.com> <86ir4nxv8o.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <86ir4nxv8o.fsf@ds4.des.no> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org, "Stephan F. Yaraghchi" Subject: Re: loader breaks with -O2 optimizations X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 14:38:36 -0000 On Wed, Oct 31, 2007 at 02:35:19PM +0100, Dag-Erling Smørgrav wrote: > Jeremy Chadwick writes: > > Stephan F. Yaraghchi writes: > > > I found out that the following line in my make.conf causes > > > the problem: > > > > > > CFLAGS= -O2 -funroll-loops -pipe > > You shouldn't have this in your make.conf. Remove it. This is very > > likely breaking a lot more than just loader. > > Uh, no. Please stop spreading FUD. Every time it's been discussed, the conclusion reached has been "stop setting CFLAGS, you're overwriting any previous definition used, which may be causing problems for you. Use += or COPTFLAGS." Even the Handbook explains the dangers of using CFLAGS= when one should be CFLAGS+=. http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/dads-cflags.html http://lists.freebsd.org/pipermail/freebsd-current/2004-August/034763.html http://lists.freebsd.org/pipermail/freebsd-questions/2004-February/036214.html http://www.nabble.com/buildworld-failure-(boot2.ld-too-big-when-CFLAGS-set-in-make.conf)-t4674137.html -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 14:48:39 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A961C16A421 for ; Wed, 31 Oct 2007 14:48:39 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 9600C13C480 for ; Wed, 31 Oct 2007 14:48:39 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id E12E91CC077; Wed, 31 Oct 2007 07:39:44 -0700 (PDT) Date: Wed, 31 Oct 2007 07:39:44 -0700 From: Jeremy Chadwick To: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= Message-ID: <20071031143944.GB21646@eos.sc1.parodius.com> References: <20071027101312.GA42516@eos.sc1.parodius.com> <86bqafxt96.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <86bqafxt96.fsf@ds4.des.no> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org, Rob Zietlow Subject: Re: [7.0-Beta] can no longer ssh into just upgraded host X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 14:48:39 -0000 On Wed, Oct 31, 2007 at 03:18:13PM +0100, Dag-Erling Smørgrav wrote: > Jeremy Chadwick writes: > > On Fri, Oct 26, 2007 at 01:47:07PM -0500, Rob Zietlow wrote: > >> #ssh -vv 192.168.8.163 > >> OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003 > >> debug1: Reading configuration data /etc/ssh/ssh_config > >> debug1: Applying options for * > >> debug2: ssh_connect: needpriv 0 > >> debug1: Connecting to 192.168.8.163 [192.168.8.163] port 22. > >> debug1: Connection established. > >> debug1: identity file /home/$USER/.ssh/identity type -1 > >> debug1: identity file /home/$USER/.ssh/id_rsa type -1 > >> debug1: identity file /home/$USER/.ssh/id_dsa type -1 > >> ssh_exchange_identification: read: Connection reset by peer > > > > Sounds like it might be a PAM-related problem. Have you looked > > at /var/log/messages or "dmesg -a"? > > What makes you think it might be PAM-related? They don't even get as > far as exchanging version strings. An old -stable post I read is what made me think it might be PAM-related: http://lists.freebsd.org/pipermail/freebsd-stable/2004-November/009414.html I don't know what stage PAM is actually induced within sshd (are any PAM-related API calls done before version exchange, etc.). -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 14:52:11 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 851E316A418 for ; Wed, 31 Oct 2007 14:52:11 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [IPv6:2001:1b20:1:3::1]) by mx1.freebsd.org (Postfix) with ESMTP id 0058B13C494 for ; Wed, 31 Oct 2007 14:52:10 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id l9VEq3oO040717; Wed, 31 Oct 2007 15:52:09 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id l9VEq33u040716; Wed, 31 Oct 2007 15:52:03 +0100 (CET) (envelope-from olli) Date: Wed, 31 Oct 2007 15:52:03 +0100 (CET) Message-Id: <200710311452.l9VEq33u040716@lurza.secnetix.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG, stephan@yaraghchi.org In-Reply-To: <25f52a3d0710300732x425f0c45vde1a29361096c018@mail.gmail.com> X-Newsgroups: list.freebsd-current User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 31 Oct 2007 15:52:09 +0100 (CET) X-Mailman-Approved-At: Wed, 31 Oct 2007 14:54:28 +0000 Cc: Subject: Re: loader breaks with -O2 optimizations X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-current@FreeBSD.ORG, stephan@yaraghchi.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 14:52:11 -0000 Stephan F. Yaraghchi wrote: > After making world on a freshly installed 7.0-BETA1 > the system does not boot anymore due to a broken loader: > [...] > I found out that the following line in my make.conf causes > the problem: > > CFLAGS= -O2 -funroll-loops -pipe > > After changing down to -O1 and making /usr/src/sys/boot again > the systems behaves properly at boot. Have you tried with the default flags? i.e. simply remove the CFLAGS line from your make.conf. Does the loader still break? Best regards Oliver PS: The default flags are: -O2 -fno-strict-aliasing -pipe (see /usr/share/mk/sys.mk) -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "Unix gives you just enough rope to hang yourself -- and then a couple of more feet, just to be sure." -- Eric Allman From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 15:05:34 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0ABA916A418 for ; Wed, 31 Oct 2007 15:05:34 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id B7E1F13C480 for ; Wed, 31 Oct 2007 15:05:32 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1InCuN-0002am-Pq for freebsd-current@freebsd.org; Wed, 31 Oct 2007 12:42:55 +0000 Received: from 161.53.72.68 ([161.53.72.68]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 31 Oct 2007 12:42:55 +0000 Received: from ivoras by 161.53.72.68 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 31 Oct 2007 12:42:55 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Wed, 31 Oct 2007 13:44:56 +0100 Lines: 28 Message-ID: References: <200710301834.l9UIYeW55836@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 161.53.72.68 User-Agent: Thunderbird 2.0.0.6 (X11/20070801) In-Reply-To: <200710301834.l9UIYeW55836@lakes.dignus.com> Sender: news Subject: Re: 7.0 BETA1.5 initial findings... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 15:05:34 -0000 Thomas David Rivers wrote: > Just wanted to report some of my results with installing > the BETA1.5 CDs.... with a CD-ONLY install. > > This is on an Intel quad-core with 2G of memory, and 300G SATA > drive and older ATAPI DVD drive (Intel DG33BU motherboard.) > > First; after you partition & label and choose your distributions; > it's time to remove the "BOOTONLY" CD and place DISC1 in the > drive. There's nothing that tells you this.. if you don't > do this, then the process merrily fails at trying to install > everything.. twice over. After that, you have an opportunity > to try and install again, putting DISC1 in the drive. I'd > suggest a little box saying "remove the BOOTONLY CD, insert DISC1 > and press OK" when it's time to start installing the distributions. > > Second - if you choose the X11 packages in the distributions; > they don't work. The install process complains that it > can't find packages/INDEX on either DISC1 or DISK2. I'm not > sure how to get the X11 packages installed from a CD-only install. Yes, you are right. These things are "idiosyncratic" for FreeBSD and sysinstall: - "bootonly" really means that you can't do anything with it except boot the kernel (you need disc1 to install it, it has everything on it) - beta install CDs (disc1) are missing all the packages and the fixit live system (at least the current one does). From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 15:12:54 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FBD816A418; Wed, 31 Oct 2007 15:12:54 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from optimus.centralmiss.com (ns.centralmiss.com [206.156.254.79]) by mx1.freebsd.org (Postfix) with ESMTP id F2E7513C48E; Wed, 31 Oct 2007 15:12:53 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by optimus.centralmiss.com (Postfix) with ESMTP id 6A85528433; Wed, 31 Oct 2007 09:39:24 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 046A161C42; Wed, 31 Oct 2007 09:39:24 -0500 (CDT) Date: Wed, 31 Oct 2007 09:39:23 -0500 From: "Matthew D. Fuller" To: Alex Zbyslaw Message-ID: <20071031143923.GA1580@over-yonder.net> References: <47240A15.8080305@charter.net> <20071028074248.GA1511@haakonia.hitnet.RWTH-Aachen.DE> <4724BAD9.7000400@charter.net> <20071028164152.GA7516@eos.sc1.parodius.com> <4724BEB3.5080905@charter.net> <20071029132447.GA2658@kobe.laptop> <4727063E.7060107@dial.pipex.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4727063E.7060107@dial.pipex.com> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.16-fullermd.4 (2007-06-09) Cc: stable@freebsd.org, current@freebsd.org Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 15:12:54 -0000 On Tue, Oct 30, 2007 at 10:23:58AM +0000 I heard the voice of Alex Zbyslaw, and lo! it spake thus: > > Of course, with modern systems where nroff-ing a man page takes > negligible time and system resources, it could also be argued that > cat-ed man pages should be a thing of the past :-) Quite. The slowest machine I currently have running (to get slower, I'd have to dig in my closet) is my laptop, which is a P54 Pentium 133MHz, with 32 megs of RAM and a hard drive that runs in PIO mode. It's running a 2002-vintage RELENG_4, on which the largest manpage is perlfunc(1) (at 71k). On the first run without the manpage in cache: % time sh -c 'man perlfunc > /dev/null' 6.881u 0.204s 0:07.22 98.0% 173+581k 8+0io 0pf+0w A while, but hardly an eternity. A more typical manpage like ls takes 3 seconds. On a less ancient machine (but still a few generations back; Athlon 1.25GHz, few month old RELENG_6), the biggest manpage is perltoc(1) at 150k. A cold cache run there takes just over 2 seconds. On my workstation (dual Athlon 1.4, HEAD), I've got wireshark-filter(4) at a whopping 746k. That takes about 8 seconds. Second place is gcc at 158k, which takes about 1. So, yes; outside of rather special cases, catpages deserve to enjoy their retirement at this point 8-} -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 15:38:12 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 750BD16A420; Wed, 31 Oct 2007 15:38:12 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 2F9E613C4A8; Wed, 31 Oct 2007 15:38:12 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 5665E208D; Wed, 31 Oct 2007 16:37:17 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id D453C2088; Wed, 31 Oct 2007 16:37:16 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id CEE8484462; Wed, 31 Oct 2007 16:37:16 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Jeremy Chadwick References: <20071027101312.GA42516@eos.sc1.parodius.com> <86bqafxt96.fsf@ds4.des.no> <20071031143944.GB21646@eos.sc1.parodius.com> Date: Wed, 31 Oct 2007 16:37:16 +0100 In-Reply-To: <20071031143944.GB21646@eos.sc1.parodius.com> (Jeremy Chadwick's message of "Wed\, 31 Oct 2007 07\:39\:44 -0700") Message-ID: <867il3xplf.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, Rob Zietlow Subject: Re: [7.0-Beta] can no longer ssh into just upgraded host X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 15:38:12 -0000 Jeremy Chadwick writes: > Dag-Erling Sm=C3=B8rgrav wrote: > > What makes you think it might be PAM-related? They don't even get as > > far as exchanging version strings. > An old -stable post I read is what made me think it might be > PAM-related: > > http://lists.freebsd.org/pipermail/freebsd-stable/2004-November/009414.ht= ml The symptoms are completely different. > I don't know what stage PAM is actually induced within sshd (are any > PAM-related API calls done before version exchange, etc.). No. The client and server send their version string in plain text immediately upon establishing a TCP connection. PAM isn't initialized until after they have agreed on algorithms and keys and decided which authentication method to use. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 16:07:09 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C101016A41B for ; Wed, 31 Oct 2007 16:07:09 +0000 (UTC) (envelope-from lance@gheek.net) Received: from smtpoutwbe07.prod.mesa1.secureserver.net (smtpoutwbe07.prod.mesa1.secureserver.net [208.109.78.209]) by mx1.freebsd.org (Postfix) with SMTP id 88BD813C4B0 for ; Wed, 31 Oct 2007 16:07:08 +0000 (UTC) (envelope-from lance@gheek.net) Received: (qmail 21877 invoked from network); 31 Oct 2007 15:59:27 -0000 Received: from unknown (HELO gem-wbe26.prod.mesa1.secureserver.net) (64.202.189.160) by smtpoutwbe07.prod.mesa1.secureserver.net with SMTP; 31 Oct 2007 15:59:27 -0000 Received: (qmail 23115 invoked by uid 99); 31 Oct 2007 15:59:27 -0000 Date: Wed, 31 Oct 2007 08:59:27 -0700 From: Lance To: Kevin Oberman Message-ID: <20071031085927.8e114e4890519e5179c192e02d6bca26.83f3291c85.wbe@email.secureserver.net> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII X-Sender: lance@gheek.net User-Agent: Web-Based Email 4.11.9 X-Originating-IP: 12.164.218.254 Cc: freebsd-current@freebsd.org Subject: RE: FreeBSD 6.2 Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 16:07:09 -0000 Kevin, Thank you for pointing out my mistake. None the less I think you most likely understood what I meant. To make sure you and anyone else understands what I misspoke about was Stable not current. I patched to the Oct 2007 Stable 6.2 release. I still see the same issue as noted before. It doesn't matter if the broadcomm cards are in a bridge,lagg,or just by themselves they do not show up in the logs. Any idea why this might be happening? -Lance > -------- Original Message -------- > Subject: Re: FreeBSD 6.2 Current > From: "Kevin Oberman" > Date: Fri, October 26, 2007 10:36 am > To: Lance > Cc: freebsd-current@freebsd.org > > Hello, > > > > I just did an upgrade to the 6.2 current (Oct 2007) from 6.2 stable to > > get the lagg feature. I noticed that the broadcomm cards no longer show > > up in /var/log/messages on a ifdown/ifup event. They will show up if I > > issue a "ifconfig" but if I don't they do not. The em interface is > > working just fine so I have a work around to get if_lagg working. Anyone > > seen a fix for this as of yet? > I am afraid you are very confused. There is no 6.2 current and there never has been. There was a 6-current, but it pre-dates 6.0. > You either want to update to 7-Beta1.5 or update your 6.2-stable. (6.3-BETA should show up soon.) > I have no idea how you updated, but I suspect that you are not running the code that you think you are. Ehat does 'uname -a' say? > -- > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > E-mail: oberman@es.net Phone: +1 510 486-8634 > Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 16:10:51 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B75716A420 for ; Wed, 31 Oct 2007 16:10:51 +0000 (UTC) (envelope-from kcender07@yahoo.co.uk) Received: from web27810.mail.ukl.yahoo.com (web27810.mail.ukl.yahoo.com [217.146.182.15]) by mx1.freebsd.org (Postfix) with SMTP id 1A60D13C48D for ; Wed, 31 Oct 2007 16:10:50 +0000 (UTC) (envelope-from kcender07@yahoo.co.uk) Received: (qmail 31812 invoked by uid 60001); 31 Oct 2007 16:10:24 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=qC2YINRT7PyN5KnlIuws+oftrB6QM1CTT8KfiXBRLlDiIgQHX7WWI8ln4ottmo+b9DB6N52+v/hTdfr9P6CW9CFSkUQmjdzLOAP8hHuf8t55HC5ztSS4b3DsIP6uQRbqf2/wfllP6GCejB+t7K7eSSnLw1oOHVr2/jhS3cJ2hl0=; X-YMail-OSG: nYvz734VM1m43FfwL1Iw2SUrkEbnGyGk5sUnSn.2bVrnyIxDhqyUOTbHebasWK9U_dIEJI9el_QeyGLrZyjJY0w- Received: from [195.166.157.72] by web27810.mail.ukl.yahoo.com via HTTP; Wed, 31 Oct 2007 16:10:24 GMT X-Mailer: YahooMailRC/814.06 YahooMailWebService/0.7.134.12 Date: Wed, 31 Oct 2007 16:10:24 +0000 (GMT) From: Red Neck To: John Baldwin , freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <862892.31020.qm@web27810.mail.ukl.yahoo.com> Cc: Subject: Re: Loader broken in Head? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 16:10:51 -0000 cd devices:=0Adisk devices:=0A disk0: BIOS drive C:=0A disk0s1= a: FFS=0A disk0s1b: swap=0A disk0s1d: FFS=0A disk0s1e:= FFS=0A disk0s1f: FFS=0A disk1: BIOS drive D:=0A disk1= s1: Unknown fs: 0x7=0A disk1s2: FAT-32=0A disk2: BIOS drive E:= =0A disk2s1: Unknown fs: 0xee=0Apxe devices:=0A=0AWhere disk1s1 is a= n NTFS filesystem and disk2s1 is the Mac GPT, don't touch, partition.=0A=0A= ----- Original Message ----=0AFrom: John Baldwin =0ATo: fr= eebsd-current@freebsd.org=0ACc: Red Neck =0ASent: Tu= esday, 30 October, 2007 1:57:35 PM=0ASubject: Re: Loader broken in Head?=0A= =0AOn Friday 26 October 2007 08:03:21 pm Red Neck wrote:=0A> Hi,=0A> =0A> W= ithin the last day (26/10/07) I've built and installed the sources=0A from = CVS=0A> Head only to find the stage 3 boot loader, /boot/loader, not workin= g.=0A I'm=0A> using a Mac Pro with 3 internal hard drives. On one hard di= sk I have=0A> FreeBSD amd64 installed, occupying the entire disk (MBR). Us= ing the=0A sources=0A> from Head, loader just freezes after displaying its = initial messages=0A with a=0A> constantly spinning cursor. To access the s= ystem I have to revert to=0A using=0A> an older loader such as 6.2 release'= s. I have attached my make and=0A kernel=0A> config.=0A=0AWhat does 'lsdev= ' from the old loader output on the box?=0A=0A-- =0AJohn Baldwin=0A________= _______________________________________=0Afreebsd-current@freebsd.org maili= ng list=0Ahttp://lists.freebsd.org/mailman/listinfo/freebsd-current=0ATo un= subscribe, send any mail to=0A "freebsd-current-unsubscribe@freebsd.org"=0A= =0A=0A=0A=0A=0A ______________________________________________________= _____ =0AWant ideas for reducing your carbon footprint? Visit Yahoo! For Go= od http://uk.promotions.yahoo.com/forgood/environment.html From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 16:23:07 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6943F16A474; Wed, 31 Oct 2007 16:23:07 +0000 (UTC) (envelope-from rermilov@team.vega.ru) Received: from mail.vega.ru (infra.dev.vega.ru [90.156.167.14]) by mx1.freebsd.org (Postfix) with ESMTP id 1D41213C4A6; Wed, 31 Oct 2007 16:23:06 +0000 (UTC) (envelope-from rermilov@team.vega.ru) Received: from [87.242.97.68] (port=55055 helo=edoofus.dev.vega.ru) by mail.vega.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1InDZo-000M8t-PD; Wed, 31 Oct 2007 13:25:44 +0000 Received: from edoofus.dev.vega.ru (localhost [127.0.0.1]) by edoofus.dev.vega.ru (8.14.1/8.14.1) with ESMTP id l9VDP0tv042932; Wed, 31 Oct 2007 16:25:00 +0300 (MSK) (envelope-from rermilov@team.vega.ru) Received: (from ru@localhost) by edoofus.dev.vega.ru (8.14.1/8.14.1/Submit) id l9VDP0bk042929; Wed, 31 Oct 2007 16:25:00 +0300 (MSK) (envelope-from rermilov@team.vega.ru) X-Authentication-Warning: edoofus.dev.vega.ru: ru set sender to rermilov@team.vega.ru using -f Date: Wed, 31 Oct 2007 16:25:00 +0300 From: Ruslan Ermilov To: Tim Kientzle Message-ID: <20071031132459.GC21541@team.vega.ru> References: <4726A890.5090705@freebsd.org> <20071030131216.GB91078@kobe.laptop> <4727F0AF.4060605@freebsd.org> <20071031103324.GB1795@kobe.laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071031103324.GB1795@kobe.laptop> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: Giorgos Keramidas , current@freebsd.org Subject: Re: -mdoc vs. -man X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 16:23:07 -0000 On Wed, Oct 31, 2007 at 12:33:24PM +0200, Giorgos Keramidas wrote: > On 2007-10-30 20:04, Tim Kientzle wrote: > >>> I've had some requests from people who want to use the > >>> libarchive and bsdtar manpages on non-BSD systems that don't > >>> support -mdoc. > >>> > >>> Any problems if I reworked these manpages to only require > >>> -man-old for compatibility with these systems? (Other than > >>> the inherent tediousness of such a project, that is.) > >> > >> Yes. At least from me. > > > > All good points. Any leads on software that can convert from > > -mdoc to -man? That would neatly address this issue for me. > > Not really. I haven't really used -man for any substantial > amount of work in years. Maybe Ruslan, who is our groff-guru > knows about something? > I'm not aware of any such tools. But perhaps having formatted versions of manpages (aka catpages) available in the libarchive distribution would be enough. Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 16:28:31 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95F9416A41A for ; Wed, 31 Oct 2007 16:28:31 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id D835913C4AC for ; Wed, 31 Oct 2007 16:28:30 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 32640 invoked from network); 31 Oct 2007 15:28:13 +0300 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 31 Oct 2007 15:28:13 +0300 X-AntiVirus: Checked by Dr.Web [version: 4.44, engine: 4.44.0.09170, virus records: 253050, updated: 31.10.2007] Message-ID: <02af01c81bb9$7f7828a0$0c00a8c0@Artem> From: "Artem Kuchin" To: "Pawel Jakub Dawidek" References: <00f101c819f7$833d5370$0c00a8c0@Artem> <20071031095213.GG8068@garage.freebsd.pl> Date: Wed, 31 Oct 2007 15:28:03 +0300 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="ISO-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Cc: freebsd-current@freebsd.org Subject: Re: Problems with gjournal or something else. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 16:28:31 -0000 >> Then did: >> >> newfs -J -b 8192 -f 1024 -g 50000 -h 20 -i 40960 /dev/twed1s1f >> >> gjournal load >> gjournal label -f /dev/twed1s1f >> tunefs -J enable -n disable /dev/twed1s1f >> mount -o noatime /dev/twed1s1f.journal /NEW/suit > >It's wrong order. See gjournal(8) manual page, EXAMPLES section. You >cannot create file system and then put journal on the same partition. >gjournal would warn you about that, but you used force (-f) option. Here is what man says: Configure gjournaling on an existing file system, but only if gjournal allows this (i.e.: if the last sector is not already used by the file system): umount /dev/da0s1d gjournal label da0s1d da0s1e tunefs -J enable -n disable mount -o async /dev/da0s1d.journal /mnt mount /dev/da0s1d /mnt However, this simple does not work. gjournal label da0s1d da0s1e - WILL FAIL ON EXISTING FS! Need to use -f switch for this. So, those whole thing will look like this 1: newfs /dev/da0s1d here we have our EXISTING filesyetm 2: gjournal load 3: gjournal label -f /dev/da0s1d 4: tunefs -J enable -n disable /dev/da0s1d 5: mount -o async /dev/da0s1d.journal /mnt Now, when you start to fill /mnt you will get error=5 with offset out of range of the filesystem, beceause metadata for the filesystem is used from /dev/da0s1f (step1) but gjournal used 1GB for the journal. This error goes away if i add additional step between 4 and 5 4.5: newfs /dev/da0s1d.journal question1: 4: tunefs -J enable -n disable /dev/da0s1d really must be for /dev/da0s1d or for /dev/da0s1d.journal question2: man says gjournal label da0s1d da0s1e && tunefs -J enable -n disable && mount -o async /dev/da0s1d.journal /mnt || mount /dev/da0s1d /mnt why there is no fs argument in tunefs? mistake? what does 'mount -o async /dev/da0s1d.journal /mnt || mount /dev/da0s1d /mnt; mean? (note ||) A couple more questions: 1) What size of journal to pick? 2) How stable is the whole thing? -- Artem From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 16:28:48 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CCB516A4CB; Wed, 31 Oct 2007 16:28:48 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from fallbackmx02.syd.optusnet.com.au (fallbackmx02.syd.optusnet.com.au [211.29.133.72]) by mx1.freebsd.org (Postfix) with ESMTP id 9A4F613C480; Wed, 31 Oct 2007 16:28:47 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail34.syd.optusnet.com.au (mail34.syd.optusnet.com.au [211.29.133.218]) by fallbackmx02.syd.optusnet.com.au (8.12.11.20060308/8.12.11) with ESMTP id l9VBjmwV015702; Wed, 31 Oct 2007 22:45:48 +1100 Received: from server.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mail34.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id l9VBilnq005497 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Oct 2007 22:44:48 +1100 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.1/8.14.1) with ESMTP id l9VBilmf041561; Wed, 31 Oct 2007 22:44:47 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.1/8.14.1/Submit) id l9VBil7J041560; Wed, 31 Oct 2007 22:44:47 +1100 (EST) (envelope-from peter) Date: Wed, 31 Oct 2007 22:44:47 +1100 From: Peter Jeremy To: Jack Vogel Message-ID: <20071031114447.GC70883@server.vk2pj.dyndns.org> References: <2a41acea0710291045m6f1d2acw78c26a455ea3894d@mail.gmail.com> <2a41acea0710301001k60442b26uae186209ac484780@mail.gmail.com> <4727F13F.1030607@samsco.org> <20071031081638.GA13564@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MXxcbiX/Q4+iy5U7" Content-Disposition: inline In-Reply-To: <20071031081638.GA13564@eos.sc1.parodius.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.16 (2007-06-09) Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List Subject: Re: RFC: Evolution of the em driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 16:28:48 -0000 --MXxcbiX/Q4+iy5U7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 31, 2007 at 01:16:39AM -0700, Jeremy Chadwick wrote: >For what it's worth, I agree with Scott. I'd rather see a new and >separate driver (presumably igb(4)) than a "hacked up" em(4) driver >trying to handle tons of IC revisions. A good example of the insanity >the latter causes is nve(4) vs. nfe(4). :-) A separate driver is probably cleaner. I'll just make the comment that if a separate driver is written, there needs to be a clear way for an end user to identify what driver is needed/preferred for his chipset. We already have cases like re(4)/rl(4) and sym(4)/ncr(4) where some chips are supported by two drivers - though generally only one driver fully supports the chip. This sort of thing is confusing for end users. --=20 Peter --MXxcbiX/Q4+iy5U7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHKGqv/opHv/APuIcRArIoAJoCNSMbMIwqTKH+lEbbrb5sC1PjZwCglsd7 HrZHfgxfPlO7uBKfY4e1XkI= =8p9Q -----END PGP SIGNATURE----- --MXxcbiX/Q4+iy5U7-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 16:35:28 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B87C416A46E for ; Wed, 31 Oct 2007 16:35:28 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.freebsd.org (Postfix) with ESMTP id 42CB013C4B8 for ; Wed, 31 Oct 2007 16:35:27 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so174812nfb for ; Wed, 31 Oct 2007 09:35:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=zXyFZFGbqRiJ2GTp0sk25Dbx7oyJw2UmUfOr6seSDgc=; b=eeIgvoI3nhOXotQViBtSPHSJCU3QPztBuwY8LZSr7c34AqNWBieaxCvuplRHe0jGUSjlGSkYA+qoesSqB8Fu+JK6ERH0bOKgBnhDxOje9CFxilfBso+dE4d94riQkRqT8D1tBnsOKQoIcPvb6/vu/WPI6S5df4OAUHHyE68BUaI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=QmIUm5O0My9CiIFxwNL3bXI7f/ipmnwUI9FtM+CelNNbQzbjhGEBjbZBpRRyS7wTNzg2gdfC9itov1+ZufoEk1udeSVO3t8m+oJkTCWXctaGAmt7uzDzS5wTVjETIvVSkeB9FlitIngRxqqrccmAR9rfoq/y/ZeJMGBOLD4ll1s= Received: by 10.86.65.11 with SMTP id n11mr6733314fga.1193848511175; Wed, 31 Oct 2007 09:35:11 -0700 (PDT) Received: by 10.86.100.19 with HTTP; Wed, 31 Oct 2007 09:35:11 -0700 (PDT) Message-ID: <2a41acea0710310935u6ed33491pcee4c6bd57d12d1a@mail.gmail.com> Date: Wed, 31 Oct 2007 09:35:11 -0700 From: "Jack Vogel" To: "freebsd-net@freebsd.org" , "FreeBSD Stable List" , "FreeBSD Current" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Proposed #ifdef change to em X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 16:35:28 -0000 I have found that the FAST interrupt handling is implicated in the watchdog resets that I have seen. What I plan to do is revert to the way 6.2 had things, meaning that FAST interrupts will be available but defined off by default. I wanted to know if anyone has an issue with this. And more importantly, I have personally not seen this problem on 7, but I could set up #ifdef's in that driver to be the same way. What does everyone think? Jack From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 16:36:17 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C78FE16A417 for ; Wed, 31 Oct 2007 16:36:17 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.freebsd.org (Postfix) with ESMTP id 4BACC13C4A5 for ; Wed, 31 Oct 2007 16:36:17 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so174811nfb for ; Wed, 31 Oct 2007 09:36:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; 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=dh62nfb4bX5pJsP3zYaUBZ/HcJf5RazE12Z27/RXEIk=; b=NDKldWK8oK7U0PA6dET87R+GrB1Y8O8mm4FfwdGjFCEFZIbqhKcAuOmhVen8pJHzlWxRl9gsd7p7s2NqjzcPrT6Zu9XwpupmwnGJFLmQvn9za42FTNrAAdO7hslk+9C5fPJsXU3nxRHnd9DNSidBCgKNUc7Bfg8+uxiM3tM+4Xc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LlvVfHk3lj/5Sd0PcFT5aQBvbdBdPLZEmI3tW/qVMsGHLTvqEv45gJm2wEC7Ta6+Pmls+BYx4D9uTtzBhEfMi1MU8oMgFuVuPCR2PWmYVriITnXTwiZvxf3rw2kyWHKGY7FzFbmLonrsQSdqjkqXIEqcFcYEMs46N2xw2oODbAg= Received: by 10.86.65.11 with SMTP id n11mr6717927fga.1193848176809; Wed, 31 Oct 2007 09:29:36 -0700 (PDT) Received: by 10.86.100.19 with HTTP; Wed, 31 Oct 2007 09:29:36 -0700 (PDT) Message-ID: <2a41acea0710310929o518c5f73l21513790bf5f378@mail.gmail.com> Date: Wed, 31 Oct 2007 09:29:36 -0700 From: "Jack Vogel" To: "Peter Jeremy" In-Reply-To: <20071031114447.GC70883@server.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0710291045m6f1d2acw78c26a455ea3894d@mail.gmail.com> <2a41acea0710301001k60442b26uae186209ac484780@mail.gmail.com> <4727F13F.1030607@samsco.org> <20071031081638.GA13564@eos.sc1.parodius.com> <20071031114447.GC70883@server.vk2pj.dyndns.org> Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List Subject: Re: RFC: Evolution of the em driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 16:36:17 -0000 On 10/31/07, Peter Jeremy wrote: > On Wed, Oct 31, 2007 at 01:16:39AM -0700, Jeremy Chadwick wrote: > >For what it's worth, I agree with Scott. I'd rather see a new and > >separate driver (presumably igb(4)) than a "hacked up" em(4) driver > >trying to handle tons of IC revisions. A good example of the insanity > >the latter causes is nve(4) vs. nfe(4). :-) > > A separate driver is probably cleaner. > > I'll just make the comment that if a separate driver is written, there > needs to be a clear way for an end user to identify what driver is > needed/preferred for his chipset. We already have cases like > re(4)/rl(4) and sym(4)/ncr(4) where some chips are supported by two > drivers - though generally only one driver fully supports the chip. > This sort of thing is confusing for end users. Yes, this is a good point, and when I'm done I will make sure that only the appropriate ID's will work on a particular driver so this kind of thing does not happen. Jack From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 16:39:15 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E82E816A468 for ; Wed, 31 Oct 2007 16:39:15 +0000 (UTC) (envelope-from cristi.magherusan@net.utcluj.ro) Received: from bavaria.utcluj.ro (unknown [IPv6:2001:b30:5000:2:20e:cff:fe4b:ca01]) by mx1.freebsd.org (Postfix) with ESMTP id 5AEAB13C4BC for ; Wed, 31 Oct 2007 16:39:15 +0000 (UTC) (envelope-from cristi.magherusan@net.utcluj.ro) Received: from localhost (localhost [127.0.0.1]) by bavaria.utcluj.ro (Postfix) with ESMTP id 75DC55088C; Wed, 31 Oct 2007 18:39:14 +0200 (EET) X-Virus-Scanned: by the daemon playing with your mail on local.mail.utcluj.ro Received: from bavaria.utcluj.ro ([127.0.0.1]) by localhost (bavaria.utcluj.ro [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VktacXwoExev; Wed, 31 Oct 2007 18:39:07 +0200 (EET) Received: from [193.226.5.50] (unknown [193.226.5.50]) (using SSLv3 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by bavaria.utcluj.ro (Postfix) with ESMTP id B2D455088B; Wed, 31 Oct 2007 18:39:07 +0200 (EET) From: Cristi Magherusan To: Szymon Kozak In-Reply-To: <289d9e390710261334v45b0b3d6te5ead0d56263532f@mail.gmail.com> References: <4712A4A8.7080503@FreeBSD.org> <200710241910.28201.joao@matik.com.br> <200710241904.47701.jkim@FreeBSD.org> <200710251102.33088.joao@matik.com.br> <289d9e390710261332l7739cc81t829ad56b63e0c90@mail.gmail.com> <289d9e390710261334v45b0b3d6te5ead0d56263532f@mail.gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-84iVnZgvKmedZpKbc3lT" Organization: Universitatea Tehnica din Cluj-Napoca, Centrul de Comunicatii "Pusztai Kalman" Date: Wed, 31 Oct 2007 18:39:07 +0200 Message-Id: <1193848747.8158.27.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 Cc: freebsd-current@freebsd.org Subject: Re: panic in 8-CURRENT / BGE hang X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cristi.magherusan@net.utcluj.ro List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 16:39:16 -0000 --=-84iVnZgvKmedZpKbc3lT Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2007-10-26 at 22:34 +0200, Szymon Kozak wrote: > On 10/25/07, JoaoBR wrote: > > > The main goal of the two technologies is the same, i.e., out-of-band > > > server management. Both use Remote Management and Control Protocol > > > (RMCP) for the network protocol but ASF is implemented on NIC > > > firmware level while IPMI is implemented on baseboard management > > > controller (BMC). Now BCM57xx firmware has built-in ASF stack and > > > the interface can be shared with BMC. If there is a BMC on-board and > > > network controller is shared, obviously you cannot just reset the > > > controller, etc. You have to 'tell' the firmware that you are about > > > to do critical things, such as reset, start, stop, link negotiation, > > > etc, so that it can communicate with BMC beforehand. If you turn on > > > hw.bge.allow_asf, it does just that. Unfortunately, it does not work > > > for all systems in the real world because they are not created equal= , > > > e.g., different spec. revisions, hardware implementations, firmware, > > > BIOS, etc. Basically some system fails *without* it while some > > > system fails *with* it. Hence, the tunable was necessary. At least, > > > that is how I understand it. > > > > > > thank you, that was great > > > > but would really not harm to put something about resumed into the man = page > > >=20 > Hello, > I have the same problem, but change value to hw.bge.allow_asf=3D"0" > doesn't work for me. > I have Broadcom NetLink (TM) Gigabit Ethernet in my ThinkPad R61. > Dmesg from FreeBSD-STABLE shows: >=20 > bge0: mem > 0xfe000000-0xfe00ffff irq 18 at device 0.0 on pci4 >=20 > Here is complete dmesg: http://slane.pl/tmp/dmesg.txt >=20 > Anybody know what's wrong? Hello,=20 I've tried again the latest version of if_bge.c on my HP 6710b laptop with no results, even after setting hw.bge.allow_asf=3D"0". I've also tried with the debugger and it seems to panic when calling free() in device_probe_child.c (IIRC). Then I #define'd BUS_PROBE and the freeze occurs after displaying something like "devclass_alloc_unit: now: unit 0 in devclass bge". The 7 Beta 1.5 install CD hangs also when loading the driver. I have a coredump made from whithin the debugger with the exact place where the faulty free() occurs, so I can provide more exact info if someone is interested. I just hope this is not a heisen-bug. Best regards, Cristi --=20 Cristi Magherusan, Universitatea Tehnica din Cluj - Napoca Centrul de Comunicatii "Pusztai Kalman" Tel. 0264/401247 http://cc.utcluj.ro --=-84iVnZgvKmedZpKbc3lT Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) iD8DBQBHKK+rfwrBISYVZFURAoQFAJ9QxO3013Vf5oeMs/okI/xPLafypgCcCIGX VGrrHTg1gQm1wMDu9EQGHao= =atH+ -----END PGP SIGNATURE----- --=-84iVnZgvKmedZpKbc3lT-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 16:41:02 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6D2516A419; Wed, 31 Oct 2007 16:41:02 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 67ACF13C48D; Wed, 31 Oct 2007 16:41:02 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l9VGe2Sa005195; Wed, 31 Oct 2007 10:40:02 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4728AFCC.7020706@samsco.org> Date: Wed, 31 Oct 2007 10:39:40 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4 MIME-Version: 1.0 To: Jack Vogel References: <2a41acea0710310935u6ed33491pcee4c6bd57d12d1a@mail.gmail.com> In-Reply-To: <2a41acea0710310935u6ed33491pcee4c6bd57d12d1a@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Wed, 31 Oct 2007 10:40:02 -0600 (MDT) X-Spam-Status: No, score=-1.4 required=5.5 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List Subject: Re: Proposed #ifdef change to em X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 16:41:02 -0000 Jack Vogel wrote: > I have found that the FAST interrupt handling is implicated > in the watchdog resets that I have seen. > > What I plan to do is revert to the way 6.2 had things, meaning > that FAST interrupts will be available but defined off by default. > > I wanted to know if anyone has an issue with this. And more > importantly, I have personally not seen this problem on 7, but > I could set up #ifdef's in that driver to be the same way. > > What does everyone think? > > Jack Let's give it another couple of days to work out the real problem before we throw in the towel. Follow-ups in private... Scott From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 16:53:21 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E9BB16A41A; Wed, 31 Oct 2007 16:53:21 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.freebsd.org (Postfix) with ESMTP id CB47013C4BD; Wed, 31 Oct 2007 16:53:20 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.1/8.14.1) id l9VFLpA5009763; Wed, 31 Oct 2007 10:21:51 -0500 (CDT) (envelope-from dan) Date: Wed, 31 Oct 2007 10:21:51 -0500 From: Dan Nelson To: Tim Kientzle Message-ID: <20071031152150.GD3109@dan.emsphone.com> References: <4726A890.5090705@freebsd.org> <20071030131216.GB91078@kobe.laptop> <4727F0AF.4060605@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4727F0AF.4060605@freebsd.org> X-OS: FreeBSD 7.0-BETA1 User-Agent: Mutt/1.5.16 (2007-06-09) Cc: Giorgos Keramidas , current@freebsd.org Subject: Re: -mdoc vs. -man X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 16:53:21 -0000 In the last episode (Oct 30), Tim Kientzle said: >>> I've had some requests from people who want to use the libarchive >>> and bsdtar manpages on non-BSD systems that don't support -mdoc. >>> >>> Any problems if I reworked these manpages to only require -man-old >>> for compatibility with these systems? (Other than the inherent >>> tediousness of such a project, that is.) >> >> Yes. At least from me. > > All good points. Any leads on software that can convert from -mdoc > to -man? That would neatly address this issue for me. I use mdoc2man.awk. There isn't really an official site for it, but you probably have a copy on your system at /usr/src/crypto/openssh/mdoc2man.awk -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 16:56:59 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4804216A46C; Wed, 31 Oct 2007 16:56:59 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id 3E3DA13C481; Wed, 31 Oct 2007 16:56:28 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (vader.bytemobile-rio.ondsl.gr [83.235.57.37]) (authenticated bits=128) by igloo.linux.gr (8.14.1/8.14.1/Debian-9) with ESMTP id l9VG8bDl000902 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 31 Oct 2007 18:08:44 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.1/8.14.1) with ESMTP id l9VG8WSH032779; Wed, 31 Oct 2007 18:08:32 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by kobe.laptop (8.14.1/8.14.1/Submit) id l9VG8WQd032778; Wed, 31 Oct 2007 18:08:32 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Wed, 31 Oct 2007 18:08:31 +0200 From: Giorgos Keramidas To: Jeremy Chadwick Message-ID: <20071031160831.GA32577@kobe.laptop> References: <4724BAD9.7000400@charter.net> <20071028164152.GA7516@eos.sc1.parodius.com> <4724BEB3.5080905@charter.net> <20071029132447.GA2658@kobe.laptop> <20071029191836.GA58058@eos.sc1.parodius.com> <20071030113247.GA3941@kobe.laptop> <20071030121603.GA90748@kobe.laptop> <20071030162636.GA92815@kobe.laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071030162636.GA92815@kobe.laptop> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.988, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.41, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: stable@freebsd.org, current@freebsd.org Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 16:56:59 -0000 On 2007-10-30 18:26, Giorgos Keramidas wrote: > There are also a couple of manpages with references to very long URIs, > which cannot be wrapped by nroff in a reasonable line-length: > > ng_netflow.4 > bluetooth.device.conf.5 > > I don't think we can easily fix these, without manually wrapping the > URIs, but that may 'break' copy/pasting of the URIs :/ Fixed with a bit of help from our resident groff-guru, Ruslan :) From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 17:05:00 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 557D616A417 for ; Wed, 31 Oct 2007 17:05:00 +0000 (UTC) (envelope-from fjwcash+freebsd@gmail.com) Received: from smtp.sd73.bc.ca (smtp.sd73.bc.ca [142.24.13.140]) by mx1.freebsd.org (Postfix) with ESMTP id 27E8513C4BD for ; Wed, 31 Oct 2007 17:04:59 +0000 (UTC) (envelope-from fjwcash+freebsd@gmail.com) Received: from localhost (localhost [127.0.0.1]) by localhost.sd73.bc.ca (Postfix) with ESMTP id 09BA91A000B1A for ; Wed, 31 Oct 2007 08:59:07 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at smtp.sd73.bc.ca Received: from smtp.sd73.bc.ca ([127.0.0.1]) by localhost (smtp.sd73.bc.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id G4u6qHK-bUw7 for ; Wed, 31 Oct 2007 08:59:00 -0700 (PDT) Received: from coal (s10.sbo [192.168.0.10]) by smtp.sd73.bc.ca (Postfix) with ESMTP id 18E861A000B13 for ; Wed, 31 Oct 2007 08:59:00 -0700 (PDT) From: Freddie Cash Organization: School District 73 To: current@freebsd.org Date: Wed, 31 Oct 2007 08:58:58 -0700 User-Agent: KMail/1.9.7 References: <200710301834.l9UIYeW55836@lakes.dignus.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710310858.59011.fjwcash+freebsd@gmail.com> Cc: Subject: Re: 7.0 BETA1.5 initial findings... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 17:05:00 -0000 On October 31, 2007 05:44 am Ivan Voras wrote: > Thomas David Rivers wrote: > > Just wanted to report some of my results with installing > > the BETA1.5 CDs.... with a CD-ONLY install. > > > > This is on an Intel quad-core with 2G of memory, and 300G SATA > > drive and older ATAPI DVD drive (Intel DG33BU motherboard.) > > > > First; after you partition & label and choose your distributions; > > it's time to remove the "BOOTONLY" CD and place DISC1 in the > > drive. There's nothing that tells you this.. if you don't > > do this, then the process merrily fails at trying to install > > everything.. twice over. After that, you have an opportunity > > to try and install again, putting DISC1 in the drive. I'd > > suggest a little box saying "remove the BOOTONLY CD, insert DISC1 > > and press OK" when it's time to start installing the distributions. > > > > Second - if you choose the X11 packages in the distributions; > > they don't work. The install process complains that it > > can't find packages/INDEX on either DISC1 or DISK2. I'm not > > sure how to get the X11 packages installed from a CD-only install. > > Yes, you are right. These things are "idiosyncratic" for FreeBSD and > sysinstall: > > - "bootonly" really means that you can't do anything with it except > boot the kernel (you need disc1 to install it, it has everything on it) And install via one of the network options. -- Freddie Cash, LPIC-2 CCNT CCLP Network Support Technician School District 73 (250) 377-HELP [377-4357] fjwcash+freebsd@gmail.com From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 17:13:02 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6158616A531 for ; Wed, 31 Oct 2007 17:13:02 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id 89CFA13C480 for ; Wed, 31 Oct 2007 17:13:01 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 2168 invoked from network); 31 Oct 2007 20:12:33 +0300 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 31 Oct 2007 20:12:33 +0300 X-AntiVirus: Checked by Dr.Web [version: 4.44, engine: 4.44.0.09170, virus records: 253097, updated: 31.10.2007] Message-ID: <0fbb01c81be1$37e698f0$0c00a8c0@Artem> From: "Artem Kuchin" To: Date: Wed, 31 Oct 2007 20:12:28 +0300 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="koi8-r"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Subject: BIO_FLUSH on twe driver. Why is it not there? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 17:13:02 -0000 7-BETA1 gjournal complained that BIO_FLUSH is not supported by the driver. That is twe driver. However, twe is working via scsi subsystem and the authour of gjournal said somewhere that he has had implemeneted BIO_FLISH for scsi and he specifically mentioned that he has tested twe and twa and they both support BIO_FLUSH. Then why BIO_FLISH is not supported now? -- Regards, Artem From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 17:25:50 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C01E316A468 for ; Wed, 31 Oct 2007 17:25:50 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from conducive.net (conducive.net [203.194.153.81]) by mx1.freebsd.org (Postfix) with ESMTP id 82C4313C4BC for ; Wed, 31 Oct 2007 17:25:50 +0000 (UTC) (envelope-from askbill@conducive.net) Received: from cm218-253-81-177.hkcable.com.hk ([218.253.81.177]:63695 helo=pb.local) by conducive.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1InGgr-000Hth-5K for freebsd-current@freebsd.org; Wed, 31 Oct 2007 16:45:13 +0000 Message-ID: <4728B114.80809@conducive.net> Date: Wed, 31 Oct 2007 12:45:08 -0400 From: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.1.2) Gecko/20070221 SeaMonkey/1.1.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <00f101c819f7$833d5370$0c00a8c0@Artem> <20071031095213.GG8068@garage.freebsd.pl> <02af01c81bb9$7f7828a0$0c00a8c0@Artem> In-Reply-To: <02af01c81bb9$7f7828a0$0c00a8c0@Artem> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Problems with gjournal or something else. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 17:25:50 -0000 Artem Kuchin wrote: >>> Then did: >>> >>> newfs -J -b 8192 -f 1024 -g 50000 -h 20 -i 40960 /dev/twed1s1f >>> >>> gjournal load >>> gjournal label -f /dev/twed1s1f >>> tunefs -J enable -n disable /dev/twed1s1f >>> mount -o noatime /dev/twed1s1f.journal /NEW/suit >> >> It's wrong order. See gjournal(8) manual page, EXAMPLES section. You >> cannot create file system and then put journal on the same partition. >> gjournal would warn you about that, but you used force (-f) option. > > Here is what man says: > > Configure gjournaling on an existing file system, but only if gjournal > allows this (i.e.: if the last sector is not already used by the file > system): > > umount /dev/da0s1d > gjournal label da0s1d da0s1e > tunefs -J enable -n disable mount -o async /dev/da0s1d.journal /mnt > mount /dev/da0s1d /mnt > > However, this simple does not work. > gjournal label da0s1d da0s1e - WILL FAIL ON EXISTING FS! > Need to use -f switch for this. > > So, those whole thing will look like this > > 1: newfs /dev/da0s1d here we have our EXISTING filesyetm > 2: gjournal load > 3: gjournal label -f /dev/da0s1d 4: tunefs -J enable -n disable /dev/da0s1d > 5: mount -o async /dev/da0s1d.journal /mnt > > Now, when you start to fill /mnt you will get error=5 with offset out of > range > of the filesystem, beceause metadata for the filesystem is used from > /dev/da0s1f (step1) but gjournal used 1GB for the journal. > > This error goes away if i add additional step between 4 and 5 > 4.5: newfs /dev/da0s1d.journal > > question1: > > 4: tunefs -J enable -n disable /dev/da0s1d > really must be for /dev/da0s1d or for /dev/da0s1d.journal > > question2: > man says > gjournal label da0s1d da0s1e && tunefs -J enable -n disable && mount -o > async /dev/da0s1d.journal /mnt || mount /dev/da0s1d /mnt > > why there is no fs argument in tunefs? mistake? Ah .. does it not expect a raw block device / portion? With no (other) fs type? > what does > 'mount -o async /dev/da0s1d.journal /mnt || mount /dev/da0s1d /mnt; > mean? (note ||) > > A couple more questions: > 1) What size of journal to pick? > 2) How stable is the whole thing? > > -- > Artem > Added question .. Is this apparent conflict [ occuring | will occur] [because | if/as/when ] the device has already been given a geom family 'label'. My specific interest is gjournal & gmirror RAID combination(s) and how/if/which can/may come first. Or NOT. Thanx, Bill _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 17:34:22 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0498416A421 for ; Wed, 31 Oct 2007 17:34:22 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id AFADB13C447 for ; Wed, 31 Oct 2007 17:34:21 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l9VHLhur005412; Wed, 31 Oct 2007 11:21:43 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4728B991.4020000@samsco.org> Date: Wed, 31 Oct 2007 11:21:21 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4 MIME-Version: 1.0 To: Artem Kuchin References: <0fbb01c81be1$37e698f0$0c00a8c0@Artem> In-Reply-To: <0fbb01c81be1$37e698f0$0c00a8c0@Artem> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Wed, 31 Oct 2007 11:21:43 -0600 (MDT) X-Spam-Status: No, score=-1.4 required=5.5 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: freebsd-current@freebsd.org Subject: Re: BIO_FLUSH on twe driver. Why is it not there? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 17:34:22 -0000 Artem Kuchin wrote: > 7-BETA1 > gjournal complained that BIO_FLUSH is not supported by the driver. That > is twe driver. > However, twe is working via scsi subsystem and the authour of gjournal > said somewhere that he > has had implemeneted BIO_FLISH for scsi and he specifically mentioned > that he has tested twe and twa and they both support BIO_FLUSH. > Then why BIO_FLISH is not supported now? > The twe driver does NOT operate under the SCSI subsystem. As for flush semantics in SCSI, they are much better done with ordered tags, not explicit SYNC_CACHE commands. That's not to say that SYNC_CACHE won't work (well, except for random devices that will hang with it in unpredictable ways, but no one seems to care about that little detail). Unfortunately, BIO_ORDERED was removed from the FreeBSD block layer several years ago. Scott From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 17:56:01 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6706216A418 for ; Wed, 31 Oct 2007 17:56:01 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.freebsd.org (Postfix) with ESMTP id EE15613C4A3 for ; Wed, 31 Oct 2007 17:56:00 +0000 (UTC) (envelope-from varga.michal@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so198250nfb for ; Wed, 31 Oct 2007 10:55:37 -0700 (PDT) Received: by 10.86.51.2 with SMTP id y2mr6677121fgy.1193843846987; Wed, 31 Oct 2007 08:17:26 -0700 (PDT) Received: from ?10.0.100.2? ( [89.176.79.57]) by mx.google.com with ESMTPS id o11sm1172848fkf.2007.10.31.08.17.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 31 Oct 2007 08:17:25 -0700 (PDT) From: Michal Varga To: Nenhum_de_Nos In-Reply-To: <47288B67.8030600@moneybookers.com> References: <4956a5e50710301848i50fa9b19ube28113cf29c13d5@mail.gmail.com> <4728756B.4020609@moneybookers.com> <4956a5e50710310645v2ff11ftc51065fdf35d09a4@mail.gmail.com> <47288B67.8030600@moneybookers.com> Content-Type: text/plain Organization: Stonehenge Date: Wed, 31 Oct 2007 16:17:23 +0100 Message-Id: <1193843843.868.16.camel@xenon.stonehenge.sk> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Stefan Lambrev Subject: Re: problems: nvidia latest driver and 7.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 17:56:01 -0000 On Wed, 2007-10-31 at 16:04 +0200, Stefan Lambrev wrote: > can you provide dmesg and pciconf -vl ? > Well, the product list says that your card should be supported in the latest (non-legacy) driver: http://www.nvidia.com/object/IO_18897.html As Stefan said, pciconf -vl will be a good start here. Also, do you know if your card worked before with any other freebsd X.Y + nvidia-driver X.Y combination? m. -- Michal Varga Stonehenge From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 18:22:43 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 413AE16A41B for ; Wed, 31 Oct 2007 18:22:43 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.179]) by mx1.freebsd.org (Postfix) with ESMTP id 1D10313C4A8 for ; Wed, 31 Oct 2007 18:22:42 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so300361waf for ; Wed, 31 Oct 2007 11:22:12 -0700 (PDT) Received: by 10.114.166.1 with SMTP id o1mr9175209wae.1193816371869; Wed, 31 Oct 2007 00:39:31 -0700 (PDT) Received: by 10.114.67.19 with HTTP; Wed, 31 Oct 2007 00:39:31 -0700 (PDT) Message-ID: Date: Wed, 31 Oct 2007 15:39:31 +0800 From: "Adrian Chadd" Sender: adrian.chadd@gmail.com To: "Jack Vogel" In-Reply-To: <2a41acea0710301016u4a0008dfjc83170257337863c@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0710301016u4a0008dfjc83170257337863c@mail.gmail.com> X-Google-Sender-Auth: 0b53bc779efc8fe8 Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List Subject: Re: em watchdog problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 18:22:43 -0000 On 31/10/2007, Jack Vogel wrote: > This morning I had an idea about what the source of the watchdog > problem is. Also, we have repro'd at least one type of watchdog > inhouse. > > One question, is this problem only happening for those running > STABLE with the 6.6.6 merged driver? This doesn't happen for me on my local testing network with RELENG_6 built from October 14 sources. These boxes generally throw about 350mbit in/out of TCP between each other. I've recently upgraded one to RELENG_7 to test so I can't provide a dmesg+interrupt count for it. Note that under load the interrupts are around 8000/sec for em0 but I haven't run the tests for a few days and thus the "rate" figure for em0 is a bit misleading. wendy# vmstat -i interrupt total rate irq1: atkbd0 76 0 irq6: fdc0 1 0 irq15: ata1 46 0 irq17: em0 fwohci0 1503419876 1866 irq19: atapci1 766603 0 irq20: ohci0 ohci+ 0 0 cpu0: timer 1611280255 2000 Total 3115466857 3867 pciconf for the ethernet card: em0@pci1:6:0: class=0x020000 card=0x13768086 chip=0x107c8086 rev=0x05 hdr=0x00 vendor = 'Intel Corporation' device = 'PRO/1000 GT' class = network subclass = 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 6.2-STABLE #6: Sun Oct 14 23:51:09 WST 2007 adrian@wendy.home.cacheboy.net:/usr/obj/usr/src/sys/WENDY Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 140 (1400.01-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0xf58 Stepping = 8 Features=0x78bfbff AMD Features=0xe0500800 real memory = 2147221504 (2047 MB) avail memory = 2096099328 (1998 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xf0000000-0xf7ffffff at device 0.0 on pci0 isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xfebfd000-0xfebfdfff irq 20 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 3 ports with 3 removable, self powered ohci1: mem 0xfebfe000-0xfebfefff irq 20 at device 2.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ehci0: mem 0xfebffc00-0xfebffcff irq 20 at device 2.2 on pci0 ehci0: [GIANT-LOCKED] usb2: EHCI version 1.0 usb2: companion controllers, 4 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 6 ports with 6 removable, self powered nve0: port 0xec00-0xec07 mem 0xfebfc000-0xfebfcfff irq 21 at device 5.0 on pci0 nve0: Ethernet address 00:0c:6e:98:55:5c miibus0: on nve0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto nve0: Ethernet address: 00:0c:6e:98:55:5c pci0: at device 6.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 8.0 on pci0 ata0: on atapci0 ata1: on atapci0 pcib1: at device 10.0 on pci0 pci1: on pcib1 em0: port 0xdc00-0xdc3f mem 0xfc9e0000-0xfc9fffff,0xfc9c0000-0xfc9dffff irq 17 at device 6.0 on pci1 em0: Ethernet address: 00:0e:0c:b9:42:d8 atapci1: port 0xd800-0xd83f,0xd400-0xd40f,0xd000-0xd07f mem 0xfc99f000-0xfc99ffff,0xfc960000-0xfc97ffff irq 19 at device 8.0 on pci1 ata2: on atapci1 ata3: on atapci1 ata4: on atapci1 fwohci0: mem 0xfc99e800-0xfc99efff,0xfc998000-0xfc99bfff irq 17 at device 9.0 on pci1 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:e0:18:00:00:2e:05:96 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:e0:18:2e:05:96 fwe0: Ethernet address: 02:e0:18:2e:05:96 fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc000ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) pcib2: at device 11.0 on pci0 pci2: on pcib2 pci2: at device 0.0 (no driver attached) acpi_button0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcffff,0xd0000-0xd0fff on isa0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1400008080 Hz quality 800 Timecounters tick every 1.000 msec ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding enabled, default to accept, logging disabled acd0: CDRW at ata1-master PIO4 ad4: 76319MB at ata2-master SATA150 hwpmc: TSC/1/0x20 K8/4/0x1ff Trying to mount root from ufs:/dev/ad4s1a HTH, -- Adrian Chadd - adrian@freebsd.org From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 18:53:56 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7920316A41B for ; Wed, 31 Oct 2007 18:53:56 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id CC4C813C4B3 for ; Wed, 31 Oct 2007 18:53:55 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 3216 invoked from network); 31 Oct 2007 21:53:35 +0300 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 31 Oct 2007 21:53:35 +0300 X-AntiVirus: Checked by Dr.Web [version: 4.44, engine: 4.44.0.09170, virus records: 253097, updated: 31.10.2007] Message-ID: <001b01c81bef$54805790$0c00a8c0@Artem> From: "Artem Kuchin" To: "Pawel Jakub Dawidek" References: <00f101c819f7$833d5370$0c00a8c0@Artem> <20071031095213.GG8068@garage.freebsd.pl> <02af01c81bb9$7f7828a0$0c00a8c0@Artem> <20071031183838.GB13180@garage.freebsd.pl> Date: Wed, 31 Oct 2007 21:53:07 +0300 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="ISO-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Cc: freebsd-current@freebsd.org Subject: Re: Problems with gjournal or something else. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 18:53:56 -0000 First of all, thank you for replying. It is always very nice and informative for hear from the actual developer of something. Thank you. >> Configure gjournaling on an existing file system, but only if gjournal >> allows this (i.e.: if the last sector is not already used by the file >> system): >> >> umount /dev/da0s1d >> gjournal label da0s1d da0s1e >> tunefs -J enable -n disable >> mount -o async /dev/da0s1d.journal /mnt >> mount /dev/da0s1d /mnt >> >> However, this simple does not work. >> gjournal label da0s1d da0s1e - WILL FAIL ON EXISTING FS! > >Have you read what the warning says? It tells you that the last sector, >where it tries to write metadata is used by existing file system. Using >-f option will destroy the last sector. You not only decided to >overwrite single sector, but 1GB of data, because you didn't give separate >provider for journal. My point here is that since it is and example of configuring a gjournaling onf existing system then this 'gjournal label da0s1d da0s1e' will always fail. Of course it says the warning, but basically, condidering that it overwrites last sector+1 GB of data on existing FS there is actual configuring on existing FS. It is simply destroying it. So, i wonder if man page should give such a big hope thar one can configure gjournal on existing fs. Even if another device is used for journal the last sector is overwritten and, as i understand, filesystem still thinks that that sector is free and any attemp to write/read at that sector will result in error=5 In any case, w/o newfs on .journal special the filesystem does not know that it is now shorter than before and IO will be attempted out of the boundaries of that filestem (in the area of journal and last sector) which will result in error 5. To fix it one must newfs spec.journal wich will result in loss of data. SO, there is no proper way to maje existing fs journaled. This is totally fine and not a big problem actually, but it should be mentioned specifically in the man page. >> Need to use -f switch for this. >> >> So, those whole thing will look like this >> >> 1: newfs /dev/da0s1d >> here we have our EXISTING filesyetm >> 2: gjournal load >> 3: gjournal label -f /dev/da0s1d > >This command destroys 1GB at the end of your file system. How do you >expect it to work properly after that? Do you think that giving '-f' >will magically add 1GB to your disk capacity? It won't. It will destroy >your data, because you asked for by giving *FORCE* option. >> what does >> 'mount -o async /dev/da0s1d.journal /mnt || mount /dev/da0s1d /mnt; >> mean? (note ||) > >There is more than that. It is given as one command on purpose. If any >of the previous commands (gjournal, tunefs or mount) fail, for example >because it is not possible to convert the file system to use gjournal, >it will mount the file system back. I'm sorry. I mean what || means here? I probaly just lack enough shell knowledge. >> A couple more questions: >> 1) What size of journal to pick? >2GB is fine. For any fs size and disk operations intensity? Mine is about 260GB moderatelly used. -- Artem From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 18:54:13 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E787116A418 for ; Wed, 31 Oct 2007 18:54:13 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id 37E5E13C4A6 for ; Wed, 31 Oct 2007 18:54:12 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 3213 invoked from network); 31 Oct 2007 21:53:34 +0300 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 31 Oct 2007 21:53:34 +0300 X-AntiVirus: Checked by Dr.Web [version: 4.44, engine: 4.44.0.09170, virus records: 253097, updated: 31.10.2007] Message-ID: <001a01c81bef$54496910$0c00a8c0@Artem> From: "Artem Kuchin" To: "Scott Long" References: <0fbb01c81be1$37e698f0$0c00a8c0@Artem> <4728B991.4020000@samsco.org> Date: Wed, 31 Oct 2007 21:39:49 +0300 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="ISO-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Cc: freebsd-current@freebsd.org Subject: Re: BIO_FLUSH on twe driver. Why is it not there? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 18:54:14 -0000 Scott Long wrote: > Artem Kuchin wrote: >> 7-BETA1 >> gjournal complained that BIO_FLUSH is not supported by the driver. >> That is twe driver. >> However, twe is working via scsi subsystem and the authour of >> gjournal said somewhere that he >> has had implemeneted BIO_FLISH for scsi and he specifically mentioned >> that he has tested twe and twa and they both support BIO_FLUSH. >> Then why BIO_FLISH is not supported now? >> > > The twe driver does NOT operate under the SCSI subsystem. As for > flush semantics in SCSI, they are much better done with ordered tags, > not explicit SYNC_CACHE commands. That's not to say that SYNC_CACHE > won't work (well, except for random devices that will hang with it in > unpredictable ways, but no one seems to care about that little > detail). Unfortunately, BIO_ORDERED was removed from the FreeBSD > block layer several years ago. How is this possible? [QUOTE:] URL:http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2006-08/msg00179.html DATE SOURCE: AUGUST 2006 freebsd-current maillis) WHO: Pawel Jakub Dawidek Unfortunately I'm not able to implement BIO_FLUSH to all out storage drivers. Currently BIO_FLUSH is supported by ata(4) (/dev/a[dr]X), da(4) and amr(4). That's the theory. I'm using standard SCSI commands for this. From the tests we made it seems that it works ok with twa(4)/twe(4). I'd still be glad if someone with SCSI/CAM foo could look at the code. [ENDQUOTE] So what changed since then? -- Artem From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 18:42:25 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE86A16A421 for ; Wed, 31 Oct 2007 18:42:25 +0000 (UTC) (envelope-from ANDREM@nortel.com) Received: from zrtps0kp.nortel.com (zrtps0kp.nortel.com [47.140.192.56]) by mx1.freebsd.org (Postfix) with ESMTP id 451CB13C48D for ; Wed, 31 Oct 2007 18:42:24 +0000 (UTC) (envelope-from ANDREM@nortel.com) Received: from zcarhxm1.corp.nortel.com (zcarhxm1.corp.nortel.com [47.129.230.97]) by zrtps0kp.nortel.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id l9VH3HE14791 for ; Wed, 31 Oct 2007 17:03:18 GMT X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 31 Oct 2007 13:02:39 -0400 Message-ID: <9671A92C3C8B5744BC97F855F7CB646512EA3D7A@zcarhxm1.corp.nortel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: OpenSSH Certkey (PKI) Thread-Index: Acgb39gcrsop9OULRm+EA0M/lPXyBg== From: "Andre Maurice" To: X-Mailman-Approved-At: Wed, 31 Oct 2007 19:00:44 +0000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: OpenSSH Certkey (PKI) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 18:42:25 -0000 Hi Andre. I have been researching the use of PKI with Openssh. I came = across a web posting that states that OpenSSH should work out of the box = with additions and this is why the X.509 support was not = desirable/pursued. Is there a way that we can configure OpenSSH to use X.509 certificate? Andr=E9 Maurice, Eng(OIQ) ESN 393-4509 External 613-763-4509 email: andrem@nortel.com Yahoo IM: andrem345 From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 19:11:36 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D197F16A419 for ; Wed, 31 Oct 2007 19:11:36 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id 32DA213C480 for ; Wed, 31 Oct 2007 19:11:35 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 7FD9145E97; Wed, 31 Oct 2007 19:38:57 +0100 (CET) Received: from localhost (154.81.datacomsa.pl [195.34.81.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 264BF45E90; Wed, 31 Oct 2007 19:38:43 +0100 (CET) Date: Wed, 31 Oct 2007 19:38:38 +0100 From: Pawel Jakub Dawidek To: Artem Kuchin Message-ID: <20071031183838.GB13180@garage.freebsd.pl> References: <00f101c819f7$833d5370$0c00a8c0@Artem> <20071031095213.GG8068@garage.freebsd.pl> <02af01c81bb9$7f7828a0$0c00a8c0@Artem> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZGiS0Q5IWpPtfppv" Content-Disposition: inline In-Reply-To: <02af01c81bb9$7f7828a0$0c00a8c0@Artem> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-current@freebsd.org Subject: Re: Problems with gjournal or something else. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 19:11:37 -0000 --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 31, 2007 at 03:28:03PM +0300, Artem Kuchin wrote: > >>Then did: > >> > >>newfs -J -b 8192 -f 1024 -g 50000 -h 20 -i 40960 /dev/twed1s1f > >> > >>gjournal load > >>gjournal label -f /dev/twed1s1f > >>tunefs -J enable -n disable /dev/twed1s1f > >>mount -o noatime /dev/twed1s1f.journal /NEW/suit > > > >It's wrong order. See gjournal(8) manual page, EXAMPLES section. You > >cannot create file system and then put journal on the same partition. > >gjournal would warn you about that, but you used force (-f) option. >=20 > Here is what man says: >=20 > Configure gjournaling on an existing file system, but only if gjournal > allows this (i.e.: if the last sector is not already used by the file > system): >=20 > umount /dev/da0s1d > gjournal label da0s1d da0s1e > tunefs -J enable -n disable=20 > mount -o async /dev/da0s1d.journal /mnt > mount /dev/da0s1d /mnt >=20 > However, this simple does not work. > gjournal label da0s1d da0s1e - WILL FAIL ON EXISTING FS! Have you read what the warning says? It tells you that the last sector, where it tries to write metadata is used by existing file system. Using -f option will destroy the last sector. You not only decided to overwrite single sector, but 1GB of data, because you didn't give separate provider for journal. > Need to use -f switch for this. >=20 > So, those whole thing will look like this >=20 > 1: newfs /dev/da0s1d=20 > here we have our EXISTING filesyetm > 2: gjournal load > 3: gjournal label -f /dev/da0s1d=20 This command destroys 1GB at the end of your file system. How do you expect it to work properly after that? Do you think that giving '-f' will magically add 1GB to your disk capacity? It won't. It will destroy your data, because you asked for by giving *FORCE* option. > question2: > man says > gjournal label da0s1d da0s1e && tunefs -J enable -n disable && mount -o= =20 > async /dev/da0s1d.journal /mnt || mount /dev/da0s1d /mnt >=20 > why there is no fs argument in tunefs? mistake? That's mistake. It should be 'tunefs -J enable -n disable /dev/da0s1d.journ= al'. > what does > 'mount -o async /dev/da0s1d.journal /mnt || mount /dev/da0s1d /mnt; > mean? (note ||) There is more than that. It is given as one command on purpose. If any of the previous commands (gjournal, tunefs or mount) fail, for example because it is not possible to convert the file system to use gjournal, it will mount the file system back. > A couple more questions: > 1) What size of journal to pick? 2GB is fine. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --ZGiS0Q5IWpPtfppv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHKMuuForvXbEpPzQRArjfAJ9oZhjZA14ZgnXTeIb/xyM2CbydOACdFyUZ 2IQ19ArUHmCPbVWiEuZAyoI= =5Ynd -----END PGP SIGNATURE----- --ZGiS0Q5IWpPtfppv-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 19:31:21 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85B1D16A419; Wed, 31 Oct 2007 19:31:21 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from optimus.centralmiss.com (ns.centralmiss.com [206.156.254.79]) by mx1.freebsd.org (Postfix) with ESMTP id 539AB13C465; Wed, 31 Oct 2007 19:31:21 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by optimus.centralmiss.com (Postfix) with ESMTP id 2C9D028BAD; Wed, 31 Oct 2007 14:30:46 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id AB63D61C43; Wed, 31 Oct 2007 14:30:45 -0500 (CDT) Date: Wed, 31 Oct 2007 14:30:45 -0500 From: "Matthew D. Fuller" To: ticso@cicely.de Message-ID: <20071031193045.GD1580@over-yonder.net> References: <20071028074248.GA1511@haakonia.hitnet.RWTH-Aachen.DE> <4724BAD9.7000400@charter.net> <20071028164152.GA7516@eos.sc1.parodius.com> <4724BEB3.5080905@charter.net> <20071029132447.GA2658@kobe.laptop> <4727063E.7060107@dial.pipex.com> <20071031143923.GA1580@over-yonder.net> <20071031190830.GJ82954@cicely12.cicely.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071031190830.GJ82954@cicely12.cicely.de> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.16-fullermd.4 (2007-06-09) Cc: stable@freebsd.org, current@freebsd.org, Alex Zbyslaw Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 19:31:21 -0000 On Wed, Oct 31, 2007 at 08:08:31PM +0100 I heard the voice of Bernd Walter, and lo! it spake thus: > > I don't completly agree. > Many people forget that FreeBSD is used on slow embedded systems as > well and I prefer having manpoages there as well. Oh, I don't argue that there are cases where catpages are still useful. But I think they're the exception, not the rule. When you're setting up a tiny system (by whatever the standards of the given day are) or an appliance, you expect the tradeoffs to be rather different than on a normal (by said standards) general-purpose computer. Heck, looking at Soekris, everything above the 4501 class is probably faster than my laptop 8-} -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 19:56:42 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56DCF16A421 for ; Wed, 31 Oct 2007 19:56:42 +0000 (UTC) (envelope-from lists@c0mplx.org) Received: from home.c0mplx.org (home.c0mplx.org [IPv6:2001:14b0:200::1]) by mx1.freebsd.org (Postfix) with ESMTP id 0FE8B13C4A5 for ; Wed, 31 Oct 2007 19:56:42 +0000 (UTC) (envelope-from lists@c0mplx.org) Received: from pi by home.c0mplx.org with local (Exim 4.66 (FreeBSD)) (envelope-from ) id 1InJg9-00082f-1z; Wed, 31 Oct 2007 20:56:41 +0100 Date: Wed, 31 Oct 2007 20:56:40 +0100 From: Kurt Jaeger To: Andre Maurice Message-ID: <20071031195640.GJ12479@home.c0mplx.org> References: <9671A92C3C8B5744BC97F855F7CB646512EA3D7A@zcarhxm1.corp.nortel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9671A92C3C8B5744BC97F855F7CB646512EA3D7A@zcarhxm1.corp.nortel.com> Cc: freebsd-current@freebsd.org Subject: Re: OpenSSH Certkey (PKI) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 19:56:42 -0000 Hi! > I have been researching the use of PKI with Openssh. I came across > a web posting that states that OpenSSH should work out of the box > with additions and this is why the X.509 support was not > desirable/pursued. > Is there a way that we can configure OpenSSH to use X.509 certificate? Seems non-trivial, but doable. See http://roumenpetrov.info/openssh/ -- pi@opsec.eu +49 171 3101372 13 years to go ! From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 20:14:31 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0379716A41A for ; Wed, 31 Oct 2007 20:14:31 +0000 (UTC) (envelope-from mashtizadeh@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.235]) by mx1.freebsd.org (Postfix) with ESMTP id 50A0513C494 for ; Wed, 31 Oct 2007 20:14:30 +0000 (UTC) (envelope-from mashtizadeh@gmail.com) Received: by wr-out-0506.google.com with SMTP id 70so156640wra for ; Wed, 31 Oct 2007 13:14:01 -0700 (PDT) Received: by 10.142.141.5 with SMTP id o5mr2103887wfd.1193845900506; Wed, 31 Oct 2007 08:51:40 -0700 (PDT) Received: by 10.142.254.15 with HTTP; Wed, 31 Oct 2007 08:51:40 -0700 (PDT) Message-ID: <440b3e930710310851x27325d3ane5804c82bf8edd2c@mail.gmail.com> Date: Wed, 31 Oct 2007 08:51:40 -0700 From: "Ali Mashtizadeh" To: "Pawel Jakub Dawidek" In-Reply-To: <20071009193051.GA13519@garage.freebsd.pl> MIME-Version: 1.0 References: <20071005000046.GC92272@garage.freebsd.pl> <20071008121523.GM2327@garage.freebsd.pl> <86bqb97mym.fsf@ds4.des.no> <20071008133846.GP2327@garage.freebsd.pl> <470BD649.9050505@freebsd.org> <20071009193051.GA13519@garage.freebsd.pl> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Darren Reed , freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Dag-Erling Sm??rgrav Subject: Re: ZFS kmem_map too small. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 20:14:31 -0000 Rm9yIFpGUyBLVkFfUEFHRVM9NTEyIHNlZW1zIHRvIHJ1biB2ZXJ5IHN0YWJsZSBzbyBpdCdzIHVu Zm9ydHVuYXRlIHRoYXQgd2UKaGF2ZSB0byBnaXZlIHVwIG91ciBWQSBzcGFjZSBpbiB0aGUgdXNl cmxhbmQuIEkgd291bGQgcGVyc29uYWxseSBsaWtlIHRvIHNlZQphIG1vdmUgdG8gYSA0LTQgTWVt b3J5IG1vZGVsIG9yIGF0IGxlYXN0IGhhdmUgaXQgYXMgYSBjb21waWxlIHRpbWUgb3B0aW9uLgpE b2VzIGFueW9uZSBrbm93IGlmIHRoYXQncyBiZWVuIGF0dGVtcHRlZCBvbiBGcmVlQlNEPwoKQWxp CgpPbiAxMC85LzA3LCBQYXdlbCBKYWt1YiBEYXdpZGVrIDxwamRAZnJlZWJzZC5vcmc+IHdyb3Rl Ogo+Cj4gT24gVHVlLCBPY3QgMDksIDIwMDcgYXQgMTI6Mjg6MDlQTSAtMDcwMCwgRGFycmVuIFJl ZWQgd3JvdGU6Cj4gPiBQYXdlbCBKYWt1YiBEYXdpZGVrIHdyb3RlOgo+ID4gPi4uLgo+ID4gPgo+ ID4gPkZvciBpMzg2IG9uZSBoYXMgdG8gc2V0LCBlZy4gJ29wdGlvbnMgS1ZBX1BBR0VTPTUxMicg dG8gdGhlIGtlcm5lbAo+ID4gPmNvbmZpZyB0byBiZSBhYmxlIHRvIGRlZmluZSBrbWVtIGxhcmdl ciB0aGFuIH43MDBNQi4gSSBndWVzcyB5b3UncmUKPiA+ID5ydW5uaW5nIGFtZDY0LCBtYXliZSB0 aGVyZSBpcyBzaW1pbGFyIHJlcXVpcmVtZW50Pwo+ID4gPgo+ID4KPiA+IEdpdmVuIGhvdyBtdWNo IFJBTSBQQ3MgaGF2ZSB0aGVzZSBkYXlzLCB3aHkgaXNuJ3QgdGhpcyBhIGRlZmF1bHQgZm9yCj4g PiBHRU5FUklDPwo+ID4KPiA+IE9yIHdoeSBpc24ndCBpdCBhdCBsZWFzdCBhIHR1bmFibGUgcmF0 aGVyIHRoYW4gYW4gb3B0aW9uPwo+Cj4gVGhpcyBtYXkgYmUgYSBnb29kIHJlYXNvbiAtIHRvZGF5 J3MgUENzIGhhdmUgYSBsb3Qgb2YgUkFNIGFuZCBLVkFfUEFHRVMKPiBzcGxpdHMgYWRkcmVzcyBz cGFjZSBiZXR3ZWVuIHVzZXJsYW5kIGFuZCBrZXJuZWwgLSB0aGUgbW9yZSBhZGRyZXNzCj4gc3Bh Y2UgZm9yIHRoZSBrZXJuZWwsIHRoZSBsZXNzIGFkZHJlc3Mgc3BhY2UgZm9yIHRoZSB1c2VybGFu ZC4KPiBLVkFfUEFHRVM9NTEyIHNwbGl0cyA0R0IgYWRkcmVzcyBzcGFjZSBpbiBoYWxmLCBzbyB1 c2VybGFuZCBwcm9jZXNzZXMKPiBjYW4gYWRkcmVzcyBhdCBtb3N0IDJHQiBvZiBtZW1vcnkuCj4K PiAtLQo+IFBhd2VsIEpha3ViIERhd2lkZWsgICAgICAgICAgICAgICAgICAgICAgIGh0dHA6Ly93 d3cud2hlZWwucGwKPiBwamRARnJlZUJTRC5vcmcgICAgICAgICAgICAgICAgICAgICAgICAgICBo dHRwOi8vd3d3LkZyZWVCU0Qub3JnCj4gRnJlZUJTRCBjb21taXR0ZXIgICAgICAgICAgICAgICAg ICAgICAgICAgQW0gSSBFdmlsPyBZZXMsIEkgQW0hCj4KPgoKCi0tIApBbGkgTWFzaHRpemFkZWgK 2LnZhNuMINmF2LTYqtuMINiy2KfYr9mHCg== From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 20:17:10 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 849EF16A41B for ; Wed, 31 Oct 2007 20:17:10 +0000 (UTC) (envelope-from mashtizadeh@gmail.com) Received: from rn-out-0102.google.com (rn-out-0910.google.com [64.233.170.191]) by mx1.freebsd.org (Postfix) with ESMTP id 8261A13C4A6 for ; Wed, 31 Oct 2007 20:17:09 +0000 (UTC) (envelope-from mashtizadeh@gmail.com) Received: by rn-out-0102.google.com with SMTP id s42so128744rnb for ; Wed, 31 Oct 2007 13:16:47 -0700 (PDT) Received: by 10.142.171.6 with SMTP id t6mr2170912wfe.1193852056047; Wed, 31 Oct 2007 10:34:16 -0700 (PDT) Received: by 10.142.254.15 with HTTP; Wed, 31 Oct 2007 10:34:16 -0700 (PDT) Message-ID: <440b3e930710311034q72ffdcc9o5013e798f5e62a6@mail.gmail.com> Date: Wed, 31 Oct 2007 10:34:16 -0700 From: "Ali Mashtizadeh" To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Coverity code scan X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 20:17:10 -0000 RG9lcyBhbnlvbmUga25vdyB3aG8gaGFzIGFjY2VzcyB0byBvdXIgYnVncyBpbiBjb3Zlcml0eSdz IG9wZW4gc291cmNlCnNvZnR3YXJlIHNjYW4/IChodHRwOi8vc2Nhbi5jb3Zlcml0eS5jb20vcnVu ZzEuaHRtbCkKCi0tIApBbGkgTWFzaHRpemFkZWgK2LnZhNuMINmF2LTYqtuMINiy2KfYr9mHCg== From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 20:35:13 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7EC816A417 for ; Wed, 31 Oct 2007 20:35:13 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id 7B61313C48E for ; Wed, 31 Oct 2007 20:35:13 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8p) with ESMTP id 217094813-1834499 for multiple; Wed, 31 Oct 2007 12:23:00 -0500 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l9VHLqDJ094328; Wed, 31 Oct 2007 13:22:48 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Red Neck Date: Wed, 31 Oct 2007 13:21:42 -0400 User-Agent: KMail/1.9.6 References: <862892.31020.qm@web27810.mail.ukl.yahoo.com> In-Reply-To: <862892.31020.qm@web27810.mail.ukl.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710311321.42463.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Wed, 31 Oct 2007 13:22:48 -0400 (EDT) X-Virus-Scanned: ClamAV 0.91.2/4651/Wed Oct 31 12:36:02 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-current@freebsd.org Subject: Re: Loader broken in Head? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 20:35:13 -0000 On Wednesday 31 October 2007 12:10:24 pm Red Neck wrote: > cd devices: > disk devices: > disk0: BIOS drive C: > disk0s1a: FFS > disk0s1b: swap > disk0s1d: FFS > disk0s1e: FFS > disk0s1f: FFS > disk1: BIOS drive D: > disk1s1: Unknown fs: 0x7 > disk1s2: FAT-32 > disk2: BIOS drive E: > disk2s1: Unknown fs: 0xee > pxe devices: > > Where disk1s1 is an NTFS filesystem and disk2s1 is the Mac GPT, don't touch, partition. Ok, so disk2 has a GPT. Can you capture the output to show exactly where it is spinning? Also, can you get the output from 'gpt show ad3' (or whatever drive disk2 is)? > ----- Original Message ---- > From: John Baldwin > To: freebsd-current@freebsd.org > Cc: Red Neck > Sent: Tuesday, 30 October, 2007 1:57:35 PM > Subject: Re: Loader broken in Head? > > On Friday 26 October 2007 08:03:21 pm Red Neck wrote: > > Hi, > > > > Within the last day (26/10/07) I've built and installed the sources > from CVS > > Head only to find the stage 3 boot loader, /boot/loader, not working. > I'm > > using a Mac Pro with 3 internal hard drives. On one hard disk I have > > FreeBSD amd64 installed, occupying the entire disk (MBR). Using the > sources > > from Head, loader just freezes after displaying its initial messages > with a > > constantly spinning cursor. To access the system I have to revert to > using > > an older loader such as 6.2 release's. I have attached my make and > kernel > > config. > > What does 'lsdev' from the old loader output on the box? > > -- > John Baldwin > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" > > > > > > ___________________________________________________________ > Want ideas for reducing your carbon footprint? Visit Yahoo! For Good http://uk.promotions.yahoo.com/forgood/environment.html > -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 21:08:21 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B455716A418 for ; Wed, 31 Oct 2007 21:08:21 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id 3078B13C4B7 for ; Wed, 31 Oct 2007 21:08:20 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id A5A7245F42; Wed, 31 Oct 2007 19:58:36 +0100 (CET) Received: from localhost (154.81.datacomsa.pl [195.34.81.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 9F99F456AB; Wed, 31 Oct 2007 19:58:31 +0100 (CET) Date: Wed, 31 Oct 2007 19:58:26 +0100 From: Pawel Jakub Dawidek To: Artem Kuchin Message-ID: <20071031185826.GC13180@garage.freebsd.pl> References: <00f101c819f7$833d5370$0c00a8c0@Artem> <20071031095213.GG8068@garage.freebsd.pl> <02af01c81bb9$7f7828a0$0c00a8c0@Artem> <20071031183838.GB13180@garage.freebsd.pl> <001b01c81bef$54805790$0c00a8c0@Artem> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PmA2V3Z32TCmWXqI" Content-Disposition: inline In-Reply-To: <001b01c81bef$54805790$0c00a8c0@Artem> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-current@freebsd.org Subject: Re: Problems with gjournal or something else. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 21:08:21 -0000 --PmA2V3Z32TCmWXqI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 31, 2007 at 09:53:07PM +0300, Artem Kuchin wrote: > First of all, thank you for replying. It is always very nice and informat= ive > for hear from the actual developer of something. Thank you. >=20 > >>Configure gjournaling on an existing file system, but only if gjournal > >>allows this (i.e.: if the last sector is not already used by the file > >>system): > >> > >>umount /dev/da0s1d > >>gjournal label da0s1d da0s1e > >>tunefs -J enable -n disable=20 > >>mount -o async /dev/da0s1d.journal /mnt > >>mount /dev/da0s1d /mnt > >> > >>However, this simple does not work. > >>gjournal label da0s1d da0s1e - WILL FAIL ON EXISTING FS! > > > >Have you read what the warning says? It tells you that the last sector, > >where it tries to write metadata is used by existing file system. Using > >-f option will destroy the last sector. You not only decided to > >overwrite single sector, but 1GB of data, because you didn't give separa= te > >provider for journal. >=20 > My point here is that since it is and example of configuring a gjournalin= g=20 > onf > existing system then this 'gjournal label da0s1d da0s1e' will always fail. No. It will fail only if your file system is using the last sector. UFS operates on fragments, so if your disk/slice/partition is not fragment-aligned it will work. > Of course it says the warning, but basically, condidering that it overwri= tes > last sector+1 GB of data on existing FS there is actual configuring on > existing FS. It is simply destroying it. =20 The example is using separate provider (da0s1e) for the journal, so it only needs one sector from da0s1d. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --PmA2V3Z32TCmWXqI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHKNBSForvXbEpPzQRAmmUAKDGy/znrPqmz4Is3fNjuuAKFugdXACfbJ4W lafAuumqiyXKVsUeWLHmMuY= =gALY -----END PGP SIGNATURE----- --PmA2V3Z32TCmWXqI-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 21:12:02 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 049A016A41A for ; Wed, 31 Oct 2007 21:12:02 +0000 (UTC) (envelope-from kcender07@yahoo.co.uk) Received: from web27808.mail.ukl.yahoo.com (web27808.mail.ukl.yahoo.com [217.146.182.13]) by mx1.freebsd.org (Postfix) with SMTP id 8894C13C4BB for ; Wed, 31 Oct 2007 21:12:01 +0000 (UTC) (envelope-from kcender07@yahoo.co.uk) Received: (qmail 81006 invoked by uid 60001); 31 Oct 2007 21:11:43 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.uk; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=SrZFQIeGxTro7qFY/YFMe4jADQ1JBtwWTYDYl4gL108fUZ79pBWaRXJL+SJY1ySS8+CvxsUNY0+MX7+P6TBK16A61QCQUKGq+OYr3pJW5ofDZf9tZpGflnrR1nxAI0gF6hSX7Ns6qxH959+2dHKN1tQ/aSLThvZGHjHswSRpWxI=; X-YMail-OSG: tOpfYNsVM1nAcG_qnQuwmw04EWZJ5xSPfOYrE1QHPinWWJymwX6Y6Dzpox9OdWrECtypnJ7pMBPsBuAc.owgSlAVY4Ix7TOr3A-- Received: from [195.166.157.72] by web27808.mail.ukl.yahoo.com via HTTP; Wed, 31 Oct 2007 21:11:42 GMT X-Mailer: YahooMailRC/814.06 YahooMailWebService/0.7.134.12 Date: Wed, 31 Oct 2007 21:11:42 +0000 (GMT) From: Red Neck To: John Baldwin MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Message-ID: <11078.80910.qm@web27808.mail.ukl.yahoo.com> Cc: freebsd-current@freebsd.org Subject: Re: Loader broken in Head? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 21:12:02 -0000 The output of the loader is as follows:=0A=0ABTX loader 1.00 BTX version= is 1.01=0AConsoles: internal video/keyboard=0ABIOS drive C: is disk0=0A= BIOS drive D: is disk1=0ABIOS drive E: is disk2=0ABIOS 639kB/2090660kB avai= lable memory=0A=0AFreeBSD/i386 bootstrap loader, Revision 1.1=0A(root@jerry= , Thu Oct 25 23:37:25 BST 2007)=0A\ ( <- spins forever)=0A=0A=0AThe output= of 'gpt show ad8' is as follows:=0A=0A start size index conte= nts=0A 0 1 PMBR=0A 1 1 = Pri GPT header=0A 2 32 Pri GPT table=0A 34= 6 =0A 40 409600 1 GPT part - EFI System= =0A 409640 487463200 2 GPT part - Apple HFS=0A 487872840 52= 4295 =0A 488397135 32 Sec GPT table=0A 488397167 = 1 Sec GPT header=0A=0A=0A----- Original Message ----=0AFro= m: John Baldwin =0ATo: Red Neck =0A= Cc: freebsd-current@freebsd.org=0ASent: Wednesday, 31 October, 2007 5:21:42= PM=0ASubject: Re: Loader broken in Head?=0A=0AOn Wednesday 31 October 2007= 12:10:24 pm Red Neck wrote:=0A> cd devices:=0A> disk devices:=0A> disk= 0: BIOS drive C:=0A> disk0s1a: FFS=0A> disk0s1b: swap=0A= > disk0s1d: FFS=0A> disk0s1e: FFS=0A> disk0s1f: FF= S=0A> disk1: BIOS drive D:=0A> disk1s1: Unknown fs: 0x7=0A> = disk1s2: FAT-32=0A> disk2: BIOS drive E:=0A> disk2s1= : Unknown fs: 0xee=0A> pxe devices:=0A> =0A> Where disk1s1 is an NTFS files= ystem and disk2s1 is the Mac GPT, don't=0A touch, =0Apartition.=0A=0AOk, so= disk2 has a GPT. Can you capture the output to show exactly=0A where it = =0Ais spinning? Also, can you get the output from 'gpt show ad3' (or=0A wh= atever =0Adrive disk2 is)?=0A=0A> ----- Original Message ----=0A> From: Joh= n Baldwin =0A> To: freebsd-current@freebsd.org=0A> Cc: Red= Neck =0A> Sent: Tuesday, 30 October, 2007 1:57:35 P= M=0A> Subject: Re: Loader broken in Head?=0A> =0A> On Friday 26 October 200= 7 08:03:21 pm Red Neck wrote:=0A> > Hi,=0A> > =0A> > Within the last day (2= 6/10/07) I've built and installed the sources=0A> from CVS=0A> > Head only= to find the stage 3 boot loader, /boot/loader, not=0A working.=0A> I'm= =0A> > using a Mac Pro with 3 internal hard drives. On one hard disk I=0A = have=0A> > FreeBSD amd64 installed, occupying the entire disk (MBR). Using= =0A the=0A> sources=0A> > from Head, loader just freezes after displaying = its initial=0A messages=0A> with a=0A> > constantly spinning cursor. To a= ccess the system I have to revert=0A to=0A> using=0A> > an older loader su= ch as 6.2 release's. I have attached my make and=0A> kernel=0A> > config.= =0A> =0A> What does 'lsdev' from the old loader output on the box?=0A> =0A>= -- =0A> John Baldwin=0A> _______________________________________________= =0A> freebsd-current@freebsd.org mailing list=0A> http://lists.freebsd.org/= mailman/listinfo/freebsd-current=0A> To unsubscribe, send any mail to=0A> = "freebsd-current-unsubscribe@freebsd.org"=0A> =0A> =0A> =0A> =0A> =0A> = ___________________________________________________________ =0A> Want ide= as for reducing your carbon footprint? Visit Yahoo! For Good=0A =0Ahttp://= uk.promotions.yahoo.com/forgood/environment.html=0A> =0A=0A=0A=0A-- =0AJohn= Baldwin=0A_______________________________________________=0Afreebsd-curren= t@freebsd.org mailing list=0Ahttp://lists.freebsd.org/mailman/listinfo/free= bsd-current=0ATo unsubscribe, send any mail to=0A "freebsd-current-unsubscr= ibe@freebsd.org"=0A=0A=0A=0A=0A=0A ___________________________________= ________________________=0AYahoo! Answers - Got a question? Someone out the= re knows the answer. Try it=0Anow.=0Ahttp://uk.answers.yahoo.com/ From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 21:31:35 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA9BE16A418 for ; Wed, 31 Oct 2007 21:31:35 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id 1FB0513C4A3; Wed, 31 Oct 2007 21:31:34 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4728F43A.1030500@FreeBSD.org> Date: Wed, 31 Oct 2007 22:31:38 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: "Stephan F. Yaraghchi" References: <25f52a3d0710300732x425f0c45vde1a29361096c018@mail.gmail.com> <47284E4F.5030008@FreeBSD.org> <25f52a3d0710310303w7138bf5ds92698f1b6af2f655@mail.gmail.com> In-Reply-To: <25f52a3d0710310303w7138bf5ds92698f1b6af2f655@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: loader breaks with -O2 optimizations X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 21:31:35 -0000 Stephan F. Yaraghchi wrote: > On 10/31/07, Kris Kennaway wrote: >> Stephan F. Yaraghchi wrote: >>> After making world on a freshly installed 7.0-BETA1 >>> the system does not boot anymore due to a broken loader: >>> >>> >>> FreeBSD/i386 bootstrap loader, Revision 1.1 >>> (root@bigblue, Tue Oct 30 11:26:32 CET 2007) >>> Can't work out which disk we are booting from. >>> Guessed BIOS device 0xffffffff not found by probes defaulting to disk0: >>> >>> panic: free: guard1 fail@ 0x6ded4 from >>> /usr/src/sys/boot/i386/loader/../../common/module.c:959 >>> >>> --> Press a key on the console to reboot <-- >>> >>> >>> I found out that the following line in my make.conf causes >>> the problem: >>> >>> CFLAGS= -O2 -funroll-loops -pipe >>> >>> >>> After changing down to -O1 and making /usr/src/sys/boot again >>> the systems behaves properly at boot. >>> >>> Is this behavior intended? >> Maybe, what happens if you use just -O2 -pipe? -funroll-loops is not an >> appropriate thing to be using globally anyway, unless your intention is >> to randomly make some code slower. >> >> Kris >> > > Hi Kris, > > I tried all possible combinations of these switches -- only -O2 led to > the described > behaviour. Presumably you mean -O2 -funroll-loops, not -O2. Or are you saying the latter also breaks the loader? > Anyway, it's very interesting to hear that adding these optimizations > to make.conf > is not recommended, even that -funroll-loops is possibly slowing down > certain code. > > I'm sure many people use it since it's a common tuning tip found on the web. > I read about it in Dru Lavigne's "BSD Hacks" (O'Reilly)... Yes, unfortunately it's bogus advice. What does she say this option is good for? Kris From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 21:57:12 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E226B16A418 for ; Wed, 31 Oct 2007 21:57:12 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id 6A19113C491 for ; Wed, 31 Oct 2007 21:57:11 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost2.sentex.ca (8.14.1/8.13.8) with ESMTP id l9VKw7tg027070; Wed, 31 Oct 2007 16:58:07 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id l9VKw6id089701 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Oct 2007 16:58:06 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <200710312058.l9VKw6id089701@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 31 Oct 2007 16:58:42 -0400 To: John Baldwin , freebsd-current@freebsd.org From: Mike Tancsa In-Reply-To: <200710311621.53910.jhb@freebsd.org> References: <20071011003619.GA84433@obelix.dsto.defence.gov.au> <200710301328.l9UDSWAK081359@lava.sentex.ca> <200710311621.53910.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: Subject: Re: em0: watchdog timeout ... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 21:57:13 -0000 At 04:21 PM 10/31/2007, John Baldwin wrote: > > > > em1@pci1:0:1: class=0x020000 card=0x115e8086 chip=0x105e8086 > > rev=0x06 hdr=0x00 > > vendor = 'Intel Corporation' > > device = 'PRO/1000 PT' > > class = network > > subclass = ethernet > > cap 01[c8] = powerspec 2 supports D0 D3 current D0 > > cap 05[d0] = MSI supports 1 message, 64 bit > > cap 10[e0] = PCI-Express 1 endpoint > > > > its also in FastE mode and not gigE. Not sure if that makes a > > difference or not. > >What if you use MSI? How do I enable that ? ---Mike >-- >John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 22:04:52 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0593C16A420 for ; Wed, 31 Oct 2007 22:04:52 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181]) by mx1.freebsd.org (Postfix) with ESMTP id A1F6C13C4BF for ; Wed, 31 Oct 2007 22:04:51 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so580203pyb for ; Wed, 31 Oct 2007 15:04:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=bfoZo6QD1aUU7OOaG5j9aHQD1TtBZyP97S8vUsDZmGg=; b=CVddnkINtRx6EH0isD7OxmLyicCpEXdBMeHQhLF2Fs9bQxoGTfvhKNTpVJ5hjGhYyFbfoSGJjj+kP3cYt6+6yVbU/7+bSVv0/wSnGZlhZgzntWlJYP0Tez5AwYO7I5VEhcHu98YVIobNyOvmLWXU5FH0IoxBN3wSOsJ7lcrvTCg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=pPSWKbsTAukc/2QZklXeRAd14R5LR2ZLeRcQHkwJCgR9+krSHSm+UlX+56HRhyfZ8qsB6vx5WvDIRCSkEjeKPBFSDTSQgrivcQyZWXBSZL1/nejVsGqyLbuub+vpVqmVbpEVKD7aYQhH4ZD/6d2iq87+daIjs/qpiC4ZwK9708U= Received: by 10.35.44.16 with SMTP id w16mr10655615pyj.1193866537332; Wed, 31 Oct 2007 14:35:37 -0700 (PDT) Received: by 10.35.110.17 with HTTP; Wed, 31 Oct 2007 14:35:37 -0700 (PDT) Message-ID: <8cb6106e0710311435q3e316599ye259f63679855f72@mail.gmail.com> Date: Wed, 31 Oct 2007 17:35:37 -0400 From: "Josh Carroll" To: "Kris Kennaway" In-Reply-To: <4728F43A.1030500@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <25f52a3d0710300732x425f0c45vde1a29361096c018@mail.gmail.com> <47284E4F.5030008@FreeBSD.org> <25f52a3d0710310303w7138bf5ds92698f1b6af2f655@mail.gmail.com> <4728F43A.1030500@FreeBSD.org> Cc: freebsd-current@freebsd.org, "Stephan F. Yaraghchi" Subject: Re: loader breaks with -O2 optimizations X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: josh.carroll@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 22:04:52 -0000 > Presumably you mean -O2 -funroll-loops, not -O2. Or are you saying the > latter also breaks the loader? Just -O2 broke it for me in RELENG_7, for the reason I said before (-O2 later in the gcc command line supersedes the -Os from the loader Makefile). Thanks, Josh From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 22:11:37 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFFA316A417 for ; Wed, 31 Oct 2007 22:11:37 +0000 (UTC) (envelope-from emaste@phaedrus.sandvine.ca) Received: from gw.sandvine.com (gw.sandvine.com [199.243.201.138]) by mx1.freebsd.org (Postfix) with ESMTP id 78B1A13C4AC for ; Wed, 31 Oct 2007 22:11:37 +0000 (UTC) (envelope-from emaste@phaedrus.sandvine.ca) Received: from labgw2.phaedrus.sandvine.com ([192.168.3.11]) by gw.sandvine.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 31 Oct 2007 17:57:40 -0400 Received: by labgw2.phaedrus.sandvine.com (Postfix, from userid 12627) id 26CCD11702; Wed, 31 Oct 2007 17:57:40 -0400 (EDT) Date: Wed, 31 Oct 2007 17:57:40 -0400 From: Ed Maste To: Angelo Turetta Message-ID: <20071031215739.GA20915@sandvine.com> References: <469881E4.3000808@commit.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <469881E4.3000808@commit.it> User-Agent: Mutt/1.4.2.1i X-OriginalArrivalTime: 31 Oct 2007 21:57:40.0346 (UTC) FILETIME=[0E7DADA0:01C81C09] Cc: freebsd-current@freebsd.org Subject: Re: Build error (make related?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 22:11:37 -0000 On Sat, Jul 14, 2007 at 09:57:24AM +0200, Angelo Turetta wrote: > This morning I'm trying to update my current system > (7.0-CURRENT #14: Mon Jul 9 21:55:06 CEST 2007) > > and when I issue the usual > > #make buildworld KERNCONF="GENERIC VIDEO VIDEODBG" buildkernel I just ran into the same failure. It seems that somehow specifying multiple entries in KERNCONF= has been broken; try building just one at a time. -Ed From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 22:23:42 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06D9D16A418; Wed, 31 Oct 2007 22:23:42 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 3EFC813C4B0; Wed, 31 Oct 2007 22:23:41 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id l9VJ8edb094054; Wed, 31 Oct 2007 20:08:40 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id l9VJ8WRr043045 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Oct 2007 20:08:33 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id l9VJ8Wbc089505; Wed, 31 Oct 2007 20:08:32 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id l9VJ8VUW089504; Wed, 31 Oct 2007 20:08:31 +0100 (CET) (envelope-from ticso) Date: Wed, 31 Oct 2007 20:08:31 +0100 From: Bernd Walter To: "Matthew D. Fuller" Message-ID: <20071031190830.GJ82954@cicely12.cicely.de> References: <47240A15.8080305@charter.net> <20071028074248.GA1511@haakonia.hitnet.RWTH-Aachen.DE> <4724BAD9.7000400@charter.net> <20071028164152.GA7516@eos.sc1.parodius.com> <4724BEB3.5080905@charter.net> <20071029132447.GA2658@kobe.laptop> <4727063E.7060107@dial.pipex.com> <20071031143923.GA1580@over-yonder.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071031143923.GA1580@over-yonder.net> X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1.8, BAYES_00=-2.599 autolearn=ham version=3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on cicely12.cicely.de Cc: stable@freebsd.org, current@freebsd.org, Alex Zbyslaw Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 22:23:42 -0000 On Wed, Oct 31, 2007 at 09:39:23AM -0500, Matthew D. Fuller wrote: > On Tue, Oct 30, 2007 at 10:23:58AM +0000 I heard the voice of > Alex Zbyslaw, and lo! it spake thus: > > > > Of course, with modern systems where nroff-ing a man page takes > > negligible time and system resources, it could also be argued that > > cat-ed man pages should be a thing of the past :-) > > Quite. I don't completly agree. Many people forget that FreeBSD is used on slow embedded systems as well and I prefer having manpoages there as well. > The slowest machine I currently have running (to get slower, I'd have > to dig in my closet) is my laptop, which is a P54 Pentium 133MHz, with > 32 megs of RAM and a hard drive that runs in PIO mode. It's running a > 2002-vintage RELENG_4, on which the largest manpage is perlfunc(1) (at > 71k). On the first run without the manpage in cache: > > % time sh -c 'man perlfunc > /dev/null' > 6.881u 0.204s 0:07.22 98.0% 173+581k 8+0io 0pf+0w [73]arm9# time sh -c 'man perlfunc > /dev/null' Formatting page, please wait...Done. 76.000u 5.000s 3:21.21 40.8% 2269+36014k 35+1io 27pf+0w [74]arm9# time sh -c 'man ls > /dev/null' Formatting page, please wait...Done. 15.000u 1.000s 0:45.48 38.3% 3286+30833k 18+1io 1pf+0w This was on an AT91RM9200 based system. It wasn't completely idle, since it is currently routing my DSL connection, but you get the point. > A while, but hardly an eternity. A more typical manpage like ls takes > 3 seconds. On a less ancient machine (but still a few generations > back; Athlon 1.25GHz, few month old RELENG_6), the biggest manpage is > perltoc(1) at 150k. A cold cache run there takes just over 2 seconds. > On my workstation (dual Athlon 1.4, HEAD), I've got > wireshark-filter(4) at a whopping 746k. That takes about 8 seconds. > Second place is gcc at 158k, which takes about 1. > > > So, yes; outside of rather special cases, catpages deserve to enjoy > their retirement at this point 8-} arm based FreeBSD is not that common, but 486 classed systems like Soekris are very commonly used. I wouldn't call it that special. -- B.Walter http://www.bwct.de http://www.fizon.de bernd@bwct.de info@bwct.de support@fizon.de From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 22:25:35 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B21616A417 for ; Wed, 31 Oct 2007 22:25:35 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.freebsd.org (Postfix) with ESMTP id ABE2613C49D for ; Wed, 31 Oct 2007 22:25:34 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so259060nfb for ; Wed, 31 Oct 2007 15:25:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; 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=bXadBribKhXoSnL6wBym0vrQ/8Yt4jW9m2hTTAMFCd4=; b=CQdxKAP2TnjVA5ZQt9vN9XurhLFpbEs3so+AXvDTQmZpAahf5aVBjQwp09AC8bG+NrrxdzdoS7RChXtHIbgVD3c1uXJNLiBXzUkOGI+shXwepehGINVjJ7PfIp+KbEIt9+ECVL13joDeMLJAys/oplaqc6vg5a0fkAjPWNMhb7s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LQRwQcbdly1v0wKJq4Urw32mzA6Mw/crStFNyxuWwmsQWH/tO78d5BK9psioLW7QdJvGhkDzWo+B1vQqU3IGo8Um1RtYxLpg2HinlTn+IOmlm5ljpjRWRjeoFejF1qYjKcLWWoOMAP2lkOzZmHPK3h28xbR/t+H50c+OKb8vq+I= Received: by 10.86.50.8 with SMTP id x8mr6949632fgx.1193869518401; Wed, 31 Oct 2007 15:25:18 -0700 (PDT) Received: by 10.86.100.19 with HTTP; Wed, 31 Oct 2007 15:25:17 -0700 (PDT) Message-ID: <2a41acea0710311525w1721f4h619237292829b071@mail.gmail.com> Date: Wed, 31 Oct 2007 15:25:17 -0700 From: "Jack Vogel" To: "Mike Tancsa" In-Reply-To: <200710312058.l9VKw6id089701@lava.sentex.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071011003619.GA84433@obelix.dsto.defence.gov.au> <200710301328.l9UDSWAK081359@lava.sentex.ca> <200710311621.53910.jhb@freebsd.org> <200710312058.l9VKw6id089701@lava.sentex.ca> Cc: freebsd-current@freebsd.org Subject: Re: em0: watchdog timeout ... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 22:25:35 -0000 On 10/31/07, Mike Tancsa wrote: > At 04:21 PM 10/31/2007, John Baldwin wrote: > > > > > > em1@pci1:0:1: class=0x020000 card=0x115e8086 chip=0x105e8086 > > > rev=0x06 hdr=0x00 > > > vendor = 'Intel Corporation' > > > device = 'PRO/1000 PT' > > > class = network > > > subclass = ethernet > > > cap 01[c8] = powerspec 2 supports D0 D3 current D0 > > > cap 05[d0] = MSI supports 1 message, 64 bit > > > cap 10[e0] = PCI-Express 1 endpoint > > > > > > its also in FastE mode and not gigE. Not sure if that makes a > > > difference or not. > > > >What if you use MSI? > > How do I enable that ? sysctl hw.pci.enable_msi=1 and sysctl hw.pci.enable_msix=1 For those that don't know, MSI/X is there in STABLE but off by default. Jack From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 22:44:54 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF23916A46C for ; Wed, 31 Oct 2007 22:44:54 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.187]) by mx1.freebsd.org (Postfix) with ESMTP id 7BAC913C4AC for ; Wed, 31 Oct 2007 22:44:54 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so262571nfb for ; Wed, 31 Oct 2007 15:44:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; 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=s3Zm401Z+NI0gTx5dWW64eJv4/4vOlpB3caYCMLjxjk=; b=XxUpd3LPkfzaE5fwWkAU3ScqNWzsoZ5J5mzXrMaQkZnPHJdxALGEA6DH3mS8zlfZszQh9tjLNAtnYMPnXdYTNTeo9NzIqGmnw9opJcXIBH1UzSzFQm8XwjS4Pa6bvJcHOvGy0DQSImvch0XEX4SGSpNHJgOTLN+sRjvcQJ6pxLI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=d87Fe2IoooGW/saAA+OSe+h0XOXuB/sriczhQLFygYqr5W2uULjTz721D2tAGPDr7EMkzW3dEKvyc05oTp0tCzZzYOcIic89/EBpPJTkst7om0aoRyznncxfDg7nsRNCre85zD9rGoXFI7EtFmHYjl3z0aHpLyNqRHxd6HvFQfk= Received: by 10.86.82.16 with SMTP id f16mr6944790fgb.1193870676850; Wed, 31 Oct 2007 15:44:36 -0700 (PDT) Received: by 10.86.100.19 with HTTP; Wed, 31 Oct 2007 15:44:36 -0700 (PDT) Message-ID: <2a41acea0710311544x5db98f27ta0f1276fd06d13f@mail.gmail.com> Date: Wed, 31 Oct 2007 15:44:36 -0700 From: "Jack Vogel" To: "Mike Tancsa" In-Reply-To: <200710312232.l9VMWgJJ090112@lava.sentex.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071011003619.GA84433@obelix.dsto.defence.gov.au> <200710301328.l9UDSWAK081359@lava.sentex.ca> <200710311621.53910.jhb@freebsd.org> <200710312058.l9VKw6id089701@lava.sentex.ca> <2a41acea0710311525w1721f4h619237292829b071@mail.gmail.com> <200710312232.l9VMWgJJ090112@lava.sentex.ca> Cc: freebsd-current@freebsd.org Subject: Re: em0: watchdog timeout ... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 22:44:55 -0000 On 10/31/07, Mike Tancsa wrote: > At 06:25 PM 10/31/2007, Jack Vogel wrote: > > > > > > > >What if you use MSI? > > > > > > How do I enable that ? > > > >sysctl hw.pci.enable_msi=1 > > > >and > > > >sysctl hw.pci.enable_msix=1 > > > >For those that don't know, MSI/X is there in STABLE but off by default. > > Thanks, > Do I need to do this in /boot/loader.conf or can I set it at > any time? Are there any performance hits / boosts to use this method > instead of the default ? I have set it after the system booted and it seemed to work. John could speak more authoritatively since he wrote it, but I have seen no problem turning em use on whenever. Uh, this means of course, enabling it and THEN loading the driver, if em is loaded and you enable the system it will have no effect on em until unload and reloading it. John has also said that MSI in 6.X is not as full an implementation as in 7 but I don't recall what that amounted to. It means you have a unique unshared interrupt, I have never really had any performance tests done on MSI vs Legacy so I can't speak to that. Jack From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 22:52:43 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFDA416A421; Wed, 31 Oct 2007 22:52:43 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id AAE1813C4B2; Wed, 31 Oct 2007 22:52:43 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.8/8.13.8) with ESMTP id l9VMWhcu037303; Wed, 31 Oct 2007 18:32:43 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id l9VMWgJJ090112 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 31 Oct 2007 18:32:43 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <200710312232.l9VMWgJJ090112@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 31 Oct 2007 18:33:19 -0400 To: "Jack Vogel" From: Mike Tancsa In-Reply-To: <2a41acea0710311525w1721f4h619237292829b071@mail.gmail.com> References: <20071011003619.GA84433@obelix.dsto.defence.gov.au> <200710301328.l9UDSWAK081359@lava.sentex.ca> <200710311621.53910.jhb@freebsd.org> <200710312058.l9VKw6id089701@lava.sentex.ca> <2a41acea0710311525w1721f4h619237292829b071@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: em0: watchdog timeout ... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 22:52:44 -0000 At 06:25 PM 10/31/2007, Jack Vogel wrote: > > > > > >What if you use MSI? > > > > How do I enable that ? > >sysctl hw.pci.enable_msi=1 > >and > >sysctl hw.pci.enable_msix=1 > >For those that don't know, MSI/X is there in STABLE but off by default. Thanks, Do I need to do this in /boot/loader.conf or can I set it at any time? Are there any performance hits / boosts to use this method instead of the default ? ---Mike >Jack From owner-freebsd-current@FreeBSD.ORG Wed Oct 31 23:31:48 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D05A16A418 for ; Wed, 31 Oct 2007 23:31:48 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.freebsd.org (Postfix) with ESMTP id 8B68013C481 for ; Wed, 31 Oct 2007 23:31:47 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A7646.dip.t-dialin.net [84.154.118.70]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id l9VMuGmu049253; Wed, 31 Oct 2007 23:56:16 +0100 (CET) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by js.berklix.net (8.13.8/8.13.8) with ESMTP id l9VMw329076469; Wed, 31 Oct 2007 23:58:03 +0100 (CET) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.13.8/8.13.8) with ESMTP id l9VMw3bw096834; Wed, 31 Oct 2007 23:58:03 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200710312258.l9VMw3bw096834@fire.js.berklix.net> To: "Ali Mashtizadeh" In-reply-to: <440b3e930710311034q72ffdcc9o5013e798f5e62a6@mail.gmail.com> References: <440b3e930710311034q72ffdcc9o5013e798f5e62a6@mail.gmail.com> Comments: In-reply-to "Ali Mashtizadeh" message dated "Wed, 31 Oct 2007 10:34:16 -0700." Date: Wed, 31 Oct 2007 23:58:03 +0100 From: "Julian H. Stacey" Cc: freebsd-current@freebsd.org Subject: Re: Coverity code scan X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2007 23:31:48 -0000 My EXMH 2.7.2 on FreeBSD-6.2-RELEASE shows: "Ali Mashtizadeh" wrote: > --===============1146199042== > Content-Type: text/plain; charset=UTF-8 > Content-Transfer-Encoding: base64 > Content-Disposition: inline > > RG9lcyBhbnlvbmUga25vdyB3aG8gaGFzIGFjY2VzcyB0byBvdXIgYnVncyBpbiBjb3Zlcml0eSdz > IG9wZW4gc291cmNlCnNvZnR3YXJlIHNjYW4/IChodHRwOi8vc2Nhbi5jb3Zlcml0eS5jb20vcnVu > ZzEuaHRtbCkKCi0tIApBbGkgTWFzaHRpemFkZWgK2LnZhNuMINmF2LTYqtuMINiy2KfYr9mHCg== > --===============1146199042== > Content-Type: text/plain; charset="us-ascii" > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Content-Disposition: inline > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > --===============1146199042==-- Or using mouse copy to rescue that: > Does anyone know who has access to our bugs in coverity's open source > software scan? (http://scan.coverity.com/rung1.html) I guess this would be better on security@freebsd.org than current@, but ... I suppose FreeBSD Security Officer & or people behind FreeBSD Security Advisories may know more/ might be in / want to initiate contact with coverity. http://www.eweek.com/article2/0,1895,1909946,00.asp (linked from coverity) says US Department of Homeland Security will spend $1.24 million over three years to fund open-source security improvement. Maybe US citizens (*) who are developers of FreeBSD should apply for some, if not already done. -- Julian Stacey. Munich Computer Consultant, BSD Unix C Linux. http://berklix.com Ihr Rauch=mein allergischer Kopfschmerz. Dump cigs 4 snuff. Q: Global warming,pollution,water,fish,fuel shortages etc. A: Contraception. From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 00:13:39 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 342CF16A417 for ; Thu, 1 Nov 2007 00:13:39 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id 50BD913C480 for ; Thu, 1 Nov 2007 00:13:38 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 3897 invoked from network); 31 Oct 2007 22:04:51 +0300 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 31 Oct 2007 22:04:51 +0300 X-AntiVirus: Checked by Dr.Web [version: 4.44, engine: 4.44.0.09170, virus records: 253189, updated: 31.10.2007] Message-ID: <004801c81bf0$e7bec7c0$0c00a8c0@Artem> From: "Artem Kuchin" To: "Pawel Jakub Dawidek" References: <00f101c819f7$833d5370$0c00a8c0@Artem> <20071031095213.GG8068@garage.freebsd.pl> <02af01c81bb9$7f7828a0$0c00a8c0@Artem> <20071031183838.GB13180@garage.freebsd.pl> <001b01c81bef$54805790$0c00a8c0@Artem> <20071031185826.GC13180@garage.freebsd.pl> Date: Wed, 31 Oct 2007 22:04:23 +0300 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="ISO-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Cc: freebsd-current@freebsd.org Subject: Re: Problems with gjournal or something else. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 00:13:39 -0000 >> My point here is that since it is and example of configuring a gjournaling >> onf >> existing system then this 'gjournal label da0s1d da0s1e' will always fail. > >No. It will fail only if your file system is using the last sector. UFS >operates on fragments, so if your disk/slice/partition is not >fragment-aligned it will work. So, i shoot myself in a foot and got all those error=5 because in my case i put journal in the same fs and cut 1GB of data from it, right? >> Of course it says the warning, but basically, condidering that it overwrites >> last sector+1 GB of data on existing FS there is actual configuring on >> existing FS. It is simply destroying it. >The example is using separate provider (da0s1e) for the journal, so it >only needs one sector from da0s1d. Ah! i see. What about porper journal size? Any recommendations? Also, please, take a look at "BIO_FLUSH on twe driver" thread. -- Artem From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 00:26:14 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF2A916A469 for ; Thu, 1 Nov 2007 00:26:14 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id 0F6EF13C4B0 for ; Thu, 1 Nov 2007 00:26:13 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 3212 invoked from network); 31 Oct 2007 21:53:34 +0300 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 31 Oct 2007 21:53:34 +0300 X-AntiVirus: Checked by Dr.Web [version: 4.44, engine: 4.44.0.09170, virus records: 253097, updated: 31.10.2007] Message-ID: <001901c81bef$542ce060$0c00a8c0@Artem> From: "Artem Kuchin" To: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= , References: <00f101c819f7$833d5370$0c00a8c0@Artem> <20071031095213.GG8068@garage.freebsd.pl><02af01c81bb9$7f7828a0$0c00a8c0@Artem> <4728B114.80809@conducive.net> Date: Wed, 31 Oct 2007 21:33:37 +0300 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=response Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Cc: Subject: Re: Problems with gjournal or something else. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 00:26:14 -0000 韓家標 Bill Hacker wrote: > Artem Kuchin wrote: >>>> Then did: >>>> >>>> newfs -J -b 8192 -f 1024 -g 50000 -h 20 -i 40960 /dev/twed1s1f >>>> >>>> gjournal load >>>> gjournal label -f /dev/twed1s1f >>>> tunefs -J enable -n disable /dev/twed1s1f >>>> mount -o noatime /dev/twed1s1f.journal /NEW/suit >>> >>> It's wrong order. See gjournal(8) manual page, EXAMPLES section. You >>> cannot create file system and then put journal on the same >>> partition. gjournal would warn you about that, but you used force >>> (-f) option. >> >> Here is what man says: >> >> Configure gjournaling on an existing file system, but only if >> gjournal allows this (i.e.: if the last sector is not already used >> by the file system): >> >> umount /dev/da0s1d >> gjournal label da0s1d da0s1e >> tunefs -J enable -n disable mount -o async /dev/da0s1d.journal /mnt >> mount /dev/da0s1d /mnt >> >> However, this simple does not work. >> gjournal label da0s1d da0s1e - WILL FAIL ON EXISTING FS! >> Need to use -f switch for this. >> >> So, those whole thing will look like this >> >> 1: newfs /dev/da0s1d here we have our EXISTING filesyetm >> 2: gjournal load >> 3: gjournal label -f /dev/da0s1d 4: tunefs -J enable -n disable >> /dev/da0s1d 5: mount -o async /dev/da0s1d.journal /mnt >> >> Now, when you start to fill /mnt you will get error=5 with offset >> out of range >> of the filesystem, beceause metadata for the filesystem is used from >> /dev/da0s1f (step1) but gjournal used 1GB for the journal. >> >> This error goes away if i add additional step between 4 and 5 >> 4.5: newfs /dev/da0s1d.journal >> >> question1: >> >> 4: tunefs -J enable -n disable /dev/da0s1d >> really must be for /dev/da0s1d or for /dev/da0s1d.journal >> >> question2: >> man says >> gjournal label da0s1d da0s1e && tunefs -J enable -n disable && mount >> -o async /dev/da0s1d.journal /mnt || mount /dev/da0s1d /mnt >> >> why there is no fs argument in tunefs? mistake? > > Ah .. does it not expect a raw block device / portion? With no > (other) fs type? osiris# tunefs -p usage: tunefs [-A] [-a enable | disable] [-e maxbpg] [-f avgfilesize] [-J enable | disable ] [-L volname] [-l enable | disable] [-m minfree] [-n enable | disable] [-o space | time] [-p] [-s avgfpdir] special | filesystem So either special or filesystem must be specified > Is this apparent conflict [ occuring | will occur] [because | > if/as/when ] the device has already been given a geom family 'label'. note here. The above example is related to ALRADY EXISTING filesystem. And my point is that IT NEVER WORKS W/O LOOSING DATA! The only was to create properly working journaled fs is to create from scratch. When i created partitions (lables) using sysinstall i had to do then cat /dev/zero > /dev/twed1s1f in otder to erase the label. The proper order seems to be: 1: do fdisk twed1 2: create labels (eg twed1s1f) 3: do cat /dev/zero > /dev/twed1sf into the partition which will be gjournaled 4: gjournal load 5: gjournal label -f /dev/twed1s1f 6: newfs -J /dev/twed1s1f.journal 7: tunefs -J enable -n disable /dev/twed1s1f.journal - I think this one is NOT NEEDED AT ALL! 8: : mount -o noatime /dev/twed1s1f.journal /NEW/suit After all these step journal fs works fine. I wonder how i can check journal usage and if it is really journaled at all :) -- Artem From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 00:35:32 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E338816A417 for ; Thu, 1 Nov 2007 00:35:32 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185]) by mx1.freebsd.org (Postfix) with ESMTP id 692DB13C4A5 for ; Thu, 1 Nov 2007 00:35:32 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so280170nfb for ; Wed, 31 Oct 2007 17:35:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; 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=jgbvK9bmZuy4EZyXK4ceXq4ffQXXGcEg8fFiaDey3es=; b=jB2k6U4fuoApeCRBf05sVJc8GCcM3rSHO89iZpa1EI4HCxHdJ5kQmt/f8vAXQFHxIGJnXMwFPBOJ2f8t8dEoXOJh5A/QK7T22Y7hKBfQjTx09cuUqmOgfcp6BsdlPFiyJ92Uk8/EaroFPK2UwlzCD6qfJDkbDPLNIcjt4JzJUco= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nOiaMTzedU1cngiFKsSKkdj6PKE5VLKlfCiB6klGYN2oueobDmlvFBgV1aktYPwx7onsyvoRpkjoo7QQf1jj0pSIiIXJK9GC5eQyvYswXXil0J2dwGgRKcioMiWEHt9suvKVAdDaZAISNRRCoF0HxoYhKLTaBBe+sFoYKGCKH3g= Received: by 10.86.71.1 with SMTP id t1mr6996698fga.1193876894038; Wed, 31 Oct 2007 17:28:14 -0700 (PDT) Received: by 10.86.100.19 with HTTP; Wed, 31 Oct 2007 17:28:13 -0700 (PDT) Message-ID: <2a41acea0710311728n69b5669fxb14fd382e3e072d4@mail.gmail.com> Date: Wed, 31 Oct 2007 17:28:13 -0700 From: "Jack Vogel" To: "Vladimir Ivanov" In-Reply-To: <47291716.1030904@yandex-team.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0710310935u6ed33491pcee4c6bd57d12d1a@mail.gmail.com> <4728AFCC.7020706@samsco.org> <47291716.1030904@yandex-team.ru> Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List Subject: Re: Proposed #ifdef change to em X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 00:35:33 -0000 Vladimir, Your one phrase "more or less patched" invalidated the whole data point. We are talking about code thats checked in and bound for 6.3 :) I have hundreds of machines here at Intel that DON'T have the problem, that's why in early 20th century philosophy they realized that verification as scientific method was ineffective, falsification on the other hand is powerful. So if any users out there have a problem I am trying to understand why. The only way that I have so far reproduced something like their failure is when FAST interrupts are enabled, THEN when I disable them on that same machine the problem disappears. Right now I have still not figured out why this is, I'm trying to do that as I write this. I am also not saying that nothing ever caused a watchdog before FAST handling, only that as best that I can tell right now the one repro I have on STABLE, October Snapshot, is related to it. Regards, Jack On 10/31/07, Vladimir Ivanov wrote: > Scott Long wrote: > > Jack Vogel wrote: > >> I have found that the FAST interrupt handling is implicated > >> in the watchdog resets that I have seen. > > It's not true. I have seen watchdogs much earlier then FASTINTR. > Also, please note: older driver had a bug preventing watchdog to be > reported (see http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/92895) > > >> > >> What I plan to do is revert to the way 6.2 had things, meaning > >> that FAST interrupts will be available but defined off by default. > >> > >> I wanted to know if anyone has an issue with this. And more > >> importantly, I have personally not seen this problem on 7, but > >> I could set up #ifdef's in that driver to be the same way. > >> > >> What does everyone think? > > We've a lot of computers w/FASTINTR (more or less patched). They carry > huge traffic. But I don't remember when I have seen last watchdog. > > E.g.: > > pitman:~# sysctl dev.em.0.stats=1; dmesg | tail -30 > dev.em.0.stats: -1 -> -1 > [skip] > em0: Excessive collisions = 0 > em0: Sequence errors = 0 > em0: Defer count = 0 > em0: Missed Packets = 44614035 > em0: Receive No Buffers = 5082415 > em0: Receive Length Errors = 0 > em0: Receive errors = 0 > em0: Crc errors = 1 > em0: Alignment errors = 0 > em0: Carrier extension errors = 0 > em0: RX overruns = 185231 > em0: watchdog timeouts = 0 > em0: XON Rcvd = 0 > em0: XON Xmtd = 0 > em0: XOFF Rcvd = 0 > em0: XOFF Xmtd = 0 > em0: Good Packets Rcvd = 918214961288 > em0: Good Packets Xmtd = 933147667144 > pitman:~# uptime > 2:54 up 247 days, 5:59, 1 user, load averages: 1,82 1,63 1,55 > > WBR, > Vladimir > From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 00:24:09 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A301816A420 for ; Thu, 1 Nov 2007 00:24:09 +0000 (UTC) (envelope-from wawa@yandex-team.ru) Received: from relanium.yandex.ru (relanium.yandex.ru [213.180.193.88]) by mx1.freebsd.org (Postfix) with ESMTP id 1BC5913C480 for ; Thu, 1 Nov 2007 00:24:08 +0000 (UTC) (envelope-from wawa@yandex-team.ru) Received: from [87.250.227.221] (v3-227-221.yandex.net [87.250.227.221]) by relanium.yandex.ru (8.14.1/8.14.1) with ESMTP id lA100Mn9053416 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Nov 2007 03:00:23 +0300 (MSK) (envelope-from wawa@yandex-team.ru) Message-ID: <47291716.1030904@yandex-team.ru> Date: Thu, 01 Nov 2007 03:00:22 +0300 From: Vladimir Ivanov Organization: Yandex LLC User-Agent: Thunderbird 1.5.0.14pre (X11/20071023) MIME-Version: 1.0 To: Scott Long References: <2a41acea0710310935u6ed33491pcee4c6bd57d12d1a@mail.gmail.com> <4728AFCC.7020706@samsco.org> In-Reply-To: <4728AFCC.7020706@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: Dr.Web (R) for Mail Servers on relanium.yandex.ru host X-Antivirus-Code: 100000 X-Mailman-Approved-At: Thu, 01 Nov 2007 01:01:15 +0000 Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List , Jack Vogel Subject: Re: Proposed #ifdef change to em X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 00:24:09 -0000 Scott Long wrote: > Jack Vogel wrote: >> I have found that the FAST interrupt handling is implicated >> in the watchdog resets that I have seen. It's not true. I have seen watchdogs much earlier then FASTINTR. Also, please note: older driver had a bug preventing watchdog to be reported (see http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/92895) >> >> What I plan to do is revert to the way 6.2 had things, meaning >> that FAST interrupts will be available but defined off by default. >> >> I wanted to know if anyone has an issue with this. And more >> importantly, I have personally not seen this problem on 7, but >> I could set up #ifdef's in that driver to be the same way. >> >> What does everyone think? We've a lot of computers w/FASTINTR (more or less patched). They carry huge traffic. But I don't remember when I have seen last watchdog. E.g.: pitman:~# sysctl dev.em.0.stats=1; dmesg | tail -30 dev.em.0.stats: -1 -> -1 [skip] em0: Excessive collisions = 0 em0: Sequence errors = 0 em0: Defer count = 0 em0: Missed Packets = 44614035 em0: Receive No Buffers = 5082415 em0: Receive Length Errors = 0 em0: Receive errors = 0 em0: Crc errors = 1 em0: Alignment errors = 0 em0: Carrier extension errors = 0 em0: RX overruns = 185231 em0: watchdog timeouts = 0 em0: XON Rcvd = 0 em0: XON Xmtd = 0 em0: XOFF Rcvd = 0 em0: XOFF Xmtd = 0 em0: Good Packets Rcvd = 918214961288 em0: Good Packets Xmtd = 933147667144 pitman:~# uptime 2:54 up 247 days, 5:59, 1 user, load averages: 1,82 1,63 1,55 WBR, Vladimir From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 01:04:15 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E203816A421 for ; Thu, 1 Nov 2007 01:04:15 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from mx.egr.msu.edu (surfnturf.egr.msu.edu [35.9.37.164]) by mx1.freebsd.org (Postfix) with ESMTP id AB24413C494 for ; Thu, 1 Nov 2007 01:04:15 +0000 (UTC) (envelope-from mcdouga9@egr.msu.edu) Received: from localhost (localhost.egr.msu.edu [127.0.0.1]) by mx.egr.msu.edu (Postfix) with ESMTP id 39E902EB862; Wed, 31 Oct 2007 16:17:32 -0400 (EDT) X-Virus-Scanned: amavisd-new at egr.msu.edu Received: from mx.egr.msu.edu ([127.0.0.1]) by localhost (surfnturf.egr.msu.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZYzCfeFLEA-I; Wed, 31 Oct 2007 16:17:32 -0400 (EDT) Received: from localhost (daemon.egr.msu.edu [35.9.44.65]) by mx.egr.msu.edu (Postfix) with ESMTP id 11E862EB82C; Wed, 31 Oct 2007 16:17:32 -0400 (EDT) Received: by localhost (Postfix, from userid 21281) id 0DB4C33C3D; Wed, 31 Oct 2007 16:17:32 -0400 (EDT) Date: Wed, 31 Oct 2007 16:17:32 -0400 From: Adam McDougall To: Pawel Jakub Dawidek Message-ID: <20071031201731.GA53377@egr.msu.edu> References: <20071029024356.GR3612@egr.msu.edu> <20071031095428.GH8068@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071031095428.GH8068@garage.freebsd.pl> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org Subject: Re: zfs stuck, cannot do any I/O, processes in Disk Wait X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 01:04:16 -0000 On Wed, Oct 31, 2007 at 10:54:28AM +0100, Pawel Jakub Dawidek wrote: On Sun, Oct 28, 2007 at 10:43:56PM -0400, Adam McDougall wrote: > I think I have had this happen at least once before, but someone else > rebooted the system before I could see it. I have a server with a > number of zfs filesystems mounted from a raidz, but it won't transfer > any data. I'm not sure why its stuck. It is running 7.0-PRERELEASE > Wed Oct 17 and I'm pretty sure it is WITHOUT vm_kern.c.2.patch. The > system is amd64 and I have not seen a kmem panic since I raised kmem > to 1.5G. > > I logged in to scp a file off of zfs, was able to ls -l to see the file > but the scp hung before transferring any bytes. Now I cannot do a ls -l > in that directory, /z. I noticed several days worth of rsync processes > stuck in disk wait, it must have been in this state for several days. > I have no urgent need to reboot this system, its more important to try > to get a permanent fix. Please let me know what other information I > can provide. I'm afraid you need to do some debugging on your own. I'd start from compiling INVARIANTS, INVARIANT_SUPPORT and WITNESS in. You may want to take a look at developers handbook to see how to obtain some informations from DDB. Thank you, this is useful guidance for me and I will do so. -- Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 01:29:33 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9436016A41A for ; Thu, 1 Nov 2007 01:29:33 +0000 (UTC) (envelope-from mgowda82@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.231]) by mx1.freebsd.org (Postfix) with ESMTP id 5B29A13C481 for ; Thu, 1 Nov 2007 01:29:33 +0000 (UTC) (envelope-from mgowda82@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so259560nzf for ; Wed, 31 Oct 2007 18:29:12 -0700 (PDT) Received: by 10.142.171.6 with SMTP id t6mr2194540wfe.1193855793029; Wed, 31 Oct 2007 11:36:33 -0700 (PDT) Received: by 10.142.192.12 with HTTP; Wed, 31 Oct 2007 11:36:33 -0700 (PDT) Message-ID: Date: Wed, 31 Oct 2007 11:36:33 -0700 From: "Manjunath R Gowda" To: "Thomas David Rivers" In-Reply-To: <200710301834.l9UIYeW55836@lakes.dignus.com> MIME-Version: 1.0 References: <200710301834.l9UIYeW55836@lakes.dignus.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: 7.0 BETA1.5 initial findings... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 01:29:33 -0000 > First; after you partition & label and choose your distributions; > it's time to remove the "BOOTONLY" CD and place DISC1 in the > drive. There's nothing that tells you this.. if you don't > do this, then the process merrily fails at trying to install > everything.. twice over. After that, you have an opportunity > to try and install again, putting DISC1 in the drive. I'd > suggest a little box saying "remove the BOOTONLY CD, insert DISC1 > and press OK" when it's time to start installing the distributions. It's really not "BOOTONLY" , I can install after boot. It should prompt for user to insert DISC1, if the user selects CD/DVD media for installation. If the CD is replaced before the start of the install distribution it would install fine any ways. It's annoying to do bunch of canels if don't insert the CD and leave the user to guess when to insert the CD. From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 01:58:12 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 399F016A418 for ; Thu, 1 Nov 2007 01:58:12 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from smtp02.dentaku.gol.com (smtp02.dentaku.gol.com [203.216.5.72]) by mx1.freebsd.org (Postfix) with ESMTP id D404313C4AC for ; Thu, 1 Nov 2007 01:58:11 +0000 (UTC) (envelope-from n-butcher=freebsd-current=freebsd.org=sbibybnr@fusiongol.com) Received: from pat.gol.co.jp ([203.216.1.191] helo=[127.0.0.1]) by smtp02.dentaku.gol.com with esmtpa (Dentaku) id 1InP3I-0006as-3Z for ; Thu, 01 Nov 2007 10:40:56 +0900 Message-ID: <47292EA7.5070803@fusiongol.com> Date: Thu, 01 Nov 2007 10:40:55 +0900 From: Nathan Butcher User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20071031120026.F1FC316A41A@hub.freebsd.org> In-Reply-To: <20071031120026.F1FC316A41A@hub.freebsd.org> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV GOL X-Abuse-Complaints: abuse@gol.com Subject: Re: Problem with ATAPI device on JMicron JMB363 on 7.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 01:58:12 -0000 An update to the current situation. I rebuilt my kernel with the latest ata-chipset and atapi-cd changes from Soren, and now the JMB363 chipset has SATA support in RELENG_7. My SATA DVD drive plugged into the JMB363 SATA port was able to mount and read from a DVD in AHCI mode - so this part is now working! Unfortunately I was unable to burn a CD with the burncd command. I got the following kernel errors:- acd0: FAILURE - MODE_SENSE_BIG timed out acd0: FAILURE - PREVENT_ALLOW timed out and well as a few SET FEATURES TRANSFER issues So mounting and reading works, but burning doesn't appear to yet. On a seperate note, having a blank CD in the drive while booting the FreeBSD kernel causes GEOM_LABEL to stall. The kernel tries to find a geom label on the blank CD, and since there isn't one - it stalls the kernel and the entire process. I also tried out my Promise SATA 300 TX4 again to see if any ata changes have fixed the device. Unfortunately it's support is still horribly broken, and is probably worse then before. (ZFS checksum errors galore) From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 02:45:42 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D74B16A419 for ; Thu, 1 Nov 2007 02:45:42 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id 14B8113C4B0 for ; Thu, 1 Nov 2007 02:45:41 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8p) with ESMTP id 217140407-1834499 for multiple; Wed, 31 Oct 2007 15:51:29 -0500 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l9VKpFrM095994; Wed, 31 Oct 2007 16:51:20 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 31 Oct 2007 16:21:53 -0400 User-Agent: KMail/1.9.6 References: <20071011003619.GA84433@obelix.dsto.defence.gov.au> <200710301328.l9UDSWAK081359@lava.sentex.ca> In-Reply-To: <200710301328.l9UDSWAK081359@lava.sentex.ca> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710311621.53910.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Wed, 31 Oct 2007 16:51:21 -0400 (EDT) X-Virus-Scanned: ClamAV 0.91.2/4652/Wed Oct 31 14:27:18 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Ihsan Dogan , Mike Tancsa Subject: Re: em0: watchdog timeout ... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 02:45:42 -0000 On Tuesday 30 October 2007 09:29:06 am Mike Tancsa wrote: > At 02:35 PM 10/29/2007, Ihsan Dogan wrote: > >on 11.10.2007 05:02 Jack Vogel said the following: > > > > >> em0@pci5:4:0: class=0x020000 card=0x10018086 chip=0x10268086 > > rev=0x04 hdr=0x00 > > >> vendor = 'Intel Corporation' > > >> device = '82545GM Gigabit Ethernet Controller' > > >> class = network > > >> subclass = ethernet > > >> > > >> And am consistently experiencing: > > >> > > >> em0: watchdog timeout -- resetting > > >> em0: link state changed to DOWN > > >> em0: link state changed to UP > > >> em0: watchdog timeout -- resetting > > >> em0: link state changed to DOWN > > >> em0: link state changed to UP > > >> em0: watchdog timeout -- resetting > > >> em0: link state changed to DOWN > > >> em0: link state changed to UP > > >> > > >> Anything I can do to help debug this ? > > > > > > Well, add more detail for one, like timestamps on these events, > > > do they happen once a minute, hour, day? > > > >I've got exactly the same problem on a machine, running 7.0-BETA1. The > >Problem occurs during the boot, when dhclient is trying to get IP. The > >messages are occuring all the time an it's not possible to use the > >network card at all. > >In my case, the network card and the soundcard are sharing an irq. If I > >don't load the the snd_emu10k1 driver, the network card works perfectly. > > > Mine are shared interrupts as well, however, they are shared among > the nics, so disabling is not an option > > % vmstat -i > interrupt total rate > irq1: atkbd0 5 0 > irq4: sio0 61332 0 > irq16: em0 1029688695 614 > irq17: em1 em2 em3 775893384 463 > irq19: atapci1 300947 0 > cpu0: timer 3347198272 1997 > cpu1: timer 3347136233 1997 > Total 8500278868 5073 > > > em1 is the one having the problems (and yes, I did check the eeprom issue) > > em1@pci1:0:1: class=0x020000 card=0x115e8086 chip=0x105e8086 > rev=0x06 hdr=0x00 > vendor = 'Intel Corporation' > device = 'PRO/1000 PT' > class = network > subclass = ethernet > cap 01[c8] = powerspec 2 supports D0 D3 current D0 > cap 05[d0] = MSI supports 1 message, 64 bit > cap 10[e0] = PCI-Express 1 endpoint > > its also in FastE mode and not gigE. Not sure if that makes a > difference or not. What if you use MSI? -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 03:00:20 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E220516A418 for ; Thu, 1 Nov 2007 03:00:20 +0000 (UTC) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (nagual.pp.ru [194.87.13.69]) by mx1.freebsd.org (Postfix) with ESMTP id 66DA813C4B6 for ; Thu, 1 Nov 2007 03:00:20 +0000 (UTC) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.14.1/8.14.1) with ESMTP id lA12xbCJ094901 for ; Thu, 1 Nov 2007 05:59:37 +0300 (MSK) (envelope-from ache@nagual.pp.ru) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nagual.pp.ru; s=default; t=1193885977; bh=wWSKUZ6BQExPRcIOLIQ4ZPXnM05uLMWwayeswSS SHtI=; l=443; h=Date:From:To:Subject:Message-ID:Mail-Followup-To: MIME-Version:Content-Type:Content-Disposition:User-Agent; b=gpkal7 dJ/JcxQO5rjgEp5geuVgRvbT4U9qOqUCPf6hV8gGfsnZjChcd//O85f268VkqTnbB0l d7LM7dni3/DcK8s7dN0BW3Dn3RyJO4LXUeMx7V2M2bf6jms3GWN1wkvQnE0pZJBmHU6 qRJQzHPfG0Wv0lMK2Y8WOP8Q7h3qDYA= Received: (from ache@localhost) by nagual.pp.ru (8.14.1/8.14.1/Submit) id lA12xbsC094900 for current@freebsd.org; Thu, 1 Nov 2007 05:59:37 +0300 (MSK) (envelope-from ache) Date: Thu, 1 Nov 2007 05:59:37 +0300 From: Andrey Chernov To: current@freebsd.org Message-ID: <20071101025937.GB94332@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.16 (2007-06-09) Cc: Subject: non-functional backout for review X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 03:00:21 -0000 Some people complaints that new check in __isctype() is not human readable and requests for backout. Compiler gives almost identical code for old and new excepting non-optimized case where non-human readable one wins. I am a bit tired to change it forth and back, so ask for final consensus here. Old one return (_c < 0 || _c >= 128) ? 0 : New one (requests for backout) return (_c & ~0x7F) ? 0 : -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 03:14:09 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6584516A41B for ; Thu, 1 Nov 2007 03:14:09 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.232]) by mx1.freebsd.org (Postfix) with ESMTP id 274AE13C4BF for ; Thu, 1 Nov 2007 03:14:09 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so277243nzf for ; Wed, 31 Oct 2007 20:13:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=AaEYpuO/McazlriKCOYbKeU6JrQchHQLRDGhFtX2724=; b=X+lWuGspHfNpT6U42vQMArUtZKjj3z7xQu0Ya1/OKJqzOm7A3sio6b+tKp/07403Wsg9/BRW9mJTiueXBdboYm3eAE5BTckk5IbfMVn0r3puUe0rWRXNxTlc926EFeoObU5JOZ3NB3lCjRRuv0729nbkZXHRsykZsGK7cdq2zvQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=rAqQSoZleJrxUXkUA6XjlJwF8ShcrvG2LeirKQlhTMlqk+hpW3Jl+PhZrntY234DRCjQ/ApR9Y9ptqzCQqvKrj8DTwA9pcqmxspFqF0oYyyTvA91l5UPV9Yi84kWHXCVaWCwtfGsEMRmIXsu+suNMt7oiggbIeylahVPHrN3jkU= Received: by 10.65.240.17 with SMTP id s17mr2691037qbr.1193886414143; Wed, 31 Oct 2007 20:06:54 -0700 (PDT) Received: by 10.65.107.3 with HTTP; Wed, 31 Oct 2007 20:06:54 -0700 (PDT) Message-ID: Date: Thu, 1 Nov 2007 03:06:54 +0000 From: "Aryeh Friedman" To: "freebsd-questions@freebsd.org" , freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: csup broken on -currnet amd64? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 03:14:09 -0000 monster# uname -a FreeBSD monster 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Tue Oct 30 18:07:21 UTC 2007 root@:/usr/obj/usr/src/sys/GENERIC amd64 monster# csup -h cvsup8.us.freebsd.org /usr/share/examples/cvsup/ports-supfile Connected to 216.165.129.134 Updating collection ports-all/cvs Checkout ports/UPDATING Receiver: Connection reset by peer Will retry at 23:04:37 monster# csup -h cvsup9.us.freebsd.org /usr/share/examples/cvsup/ports-supfile Connected to 128.205.32.21 Updating collection ports-all/cvs Edit ports/UPDATING^M Receiver: Connection reset by peer Will retry at 23:05:17 From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 03:14:30 2007 Return-Path: Delivered-To: current@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD02F16A581 for ; Thu, 1 Nov 2007 03:14:30 +0000 (UTC) (envelope-from davidxu@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B729B13C447; Thu, 1 Nov 2007 03:14:30 +0000 (UTC) (envelope-from davidxu@FreeBSD.org) Received: from [127.0.0.1] (root@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id lA13ERDM075303; Thu, 1 Nov 2007 03:14:28 GMT (envelope-from davidxu@freebsd.org) Message-ID: <472944C9.5020304@freebsd.org> Date: Thu, 01 Nov 2007 11:15:21 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20070516 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrey Chernov References: <20071101025937.GB94332@nagual.pp.ru> In-Reply-To: <20071101025937.GB94332@nagual.pp.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: current@FreeBSD.org Subject: Re: non-functional backout for review X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 03:14:30 -0000 Andrey Chernov wrote: > Some people complaints that new check in __isctype() is not human readable > and requests for backout. Compiler gives almost identical code for old and > new excepting non-optimized case where non-human readable one wins. I am a > bit tired to change it forth and back, so ask for final consensus here. > > Old one > > return (_c < 0 || _c >= 128) ? 0 : > > New one (requests for backout) > > return (_c & ~0x7F) ? 0 : > I will use a version which compiler can generate optimized code. the name __isctype already tells what the function is doing. :-) Regards, David Xu From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 03:19:54 2007 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F93916A417 for ; Thu, 1 Nov 2007 03:19:54 +0000 (UTC) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (nagual.pp.ru [194.87.13.69]) by mx1.freebsd.org (Postfix) with ESMTP id D772313C4BC for ; Thu, 1 Nov 2007 03:19:53 +0000 (UTC) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.14.1/8.14.1) with ESMTP id lA13JMBi095240; Thu, 1 Nov 2007 06:19:22 +0300 (MSK) (envelope-from ache@nagual.pp.ru) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nagual.pp.ru; s=default; t=1193887162; bh=99R3ZKcVn1+ekH/qwh9i0HS2DrPCsQQLNbBsx/D syTM=; l=700; h=Date:From:To:Cc:Subject:Message-ID:Mail-Followup-To: References:MIME-Version:Content-Type:Content-Disposition: In-Reply-To:User-Agent; b=hCf83xCvIWILJjhU7RIyGlNESg0C/xxFpSXeILsw Kw0Oa8UcaSSEsvEPvlO6srAEAgYTFp9RtWYcFePEo5Ft9RkaXuCKJ+8HLp0OQ3ttwA1 1IVHvoJpfmcA/efOkp7cFKqErdjvJ0UWJpyB3OqIzVLWWdAmiEU0Q1VELM5yOuWE= Received: (from ache@localhost) by nagual.pp.ru (8.14.1/8.14.1/Submit) id lA13JMLh095239; Thu, 1 Nov 2007 06:19:22 +0300 (MSK) (envelope-from ache) Date: Thu, 1 Nov 2007 06:19:22 +0300 From: Andrey Chernov To: David Xu Message-ID: <20071101031922.GA95201@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , David Xu , current@FreeBSD.org References: <20071101025937.GB94332@nagual.pp.ru> <472944C9.5020304@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <472944C9.5020304@freebsd.org> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: current@FreeBSD.org Subject: Re: non-functional backout for review X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 03:19:54 -0000 On Thu, Nov 01, 2007 at 11:15:21AM +0800, David Xu wrote: > Andrey Chernov wrote: >> Some people complaints that new check in __isctype() is not human readable >> and requests for backout. Compiler gives almost identical code for old and >> new excepting non-optimized case where non-human readable one wins. I am a >> bit tired to change it forth and back, so ask for final consensus here. >> Old one >> return (_c < 0 || _c >= 128) ? 0 : >> New one (requests for backout) >> return (_c & ~0x7F) ? 0 : > > I will use a version which compiler can generate optimized code. > the name __isctype already tells what the function is doing. :-) Already done. -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 03:23:12 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A1AC16A41B; Thu, 1 Nov 2007 03:23:12 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 30D5413C4B2; Thu, 1 Nov 2007 03:23:12 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.1/8.14.1) with ESMTP id lA13LjCR052491; Wed, 31 Oct 2007 20:21:45 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.1/8.14.1/Submit) id lA13LjZ9052490; Wed, 31 Oct 2007 20:21:45 -0700 (PDT) (envelope-from sgk) Date: Wed, 31 Oct 2007 20:21:45 -0700 From: Steve Kargl To: Aryeh Friedman Message-ID: <20071101032145.GA52478@troutmask.apl.washington.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org, "freebsd-questions@freebsd.org" Subject: Re: csup broken on -currnet amd64? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 03:23:12 -0000 On Thu, Nov 01, 2007 at 03:06:54AM +0000, Aryeh Friedman wrote: > monster# uname -a > FreeBSD monster 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Tue Oct 30 > 18:07:21 UTC 2007 root@:/usr/obj/usr/src/sys/GENERIC amd64 > > monster# csup -h cvsup8.us.freebsd.org /usr/share/examples/cvsup/ports-supfile > Connected to 216.165.129.134 > Updating collection ports-all/cvs > Checkout ports/UPDATING > Receiver: Connection reset by peer > Will retry at 23:04:37 > > monster# csup -h cvsup9.us.freebsd.org /usr/share/examples/cvsup/ports-supfile > Connected to 128.205.32.21 > Updating collection ports-all/cvs > Edit ports/UPDATING^M > Receiver: Connection reset by peer > Will retry at 23:05:17 Works for me. csup built from source less than 18 hours old. -- Steve From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 03:42:40 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1551216A41A for ; Thu, 1 Nov 2007 03:42:40 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id B908F13C48D for ; Thu, 1 Nov 2007 03:42:39 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8p) with ESMTP id 217182183-1834499 for multiple; Wed, 31 Oct 2007 22:42:11 -0500 Received: from [192.168.0.18] (osx.baldwin.cx [192.168.0.18]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id lA13g0o0000413; Wed, 31 Oct 2007 23:42:00 -0400 (EDT) (envelope-from jhb@freebsd.org) In-Reply-To: <11078.80910.qm@web27808.mail.ukl.yahoo.com> References: <11078.80910.qm@web27808.mail.ukl.yahoo.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <0794CD63-E196-4C80-A6CD-E5D7AC72DCC7@freebsd.org> Content-Transfer-Encoding: 7bit From: John Baldwin Date: Wed, 31 Oct 2007 23:40:06 -0400 To: Red Neck X-Mailer: Apple Mail (2.752.3) X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Wed, 31 Oct 2007 23:42:01 -0400 (EDT) X-Virus-Scanned: ClamAV 0.91.2/4654/Wed Oct 31 18:07:28 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-current@freebsd.org Subject: Re: Loader broken in Head? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 03:42:40 -0000 On Oct 31, 2007, at 5:11 PM, Red Neck wrote: > The output of the loader is as follows: > > BTX loader 1.00 BTX version is 1.01 > Consoles: internal video/keyboard > BIOS drive C: is disk0 > BIOS drive D: is disk1 > BIOS drive E: is disk2 > BIOS 639kB/2090660kB available memory > > FreeBSD/i386 bootstrap loader, Revision 1.1 > (root@jerry, Thu Oct 25 23:37:25 BST 2007) > \ ( <- spins forever) Ok. There are two things you can do to help debug this further: 1) Find the exact commit that breaks the loader for you. There were a few commits before the GPT commit that you could try backing out to. It should be sufficient to just change /sys/boot rather than the whole tree. 2) Start adding printfs (such as in open() in boot/common/open.c) to figure out what the loader is doing when the twiddle is spinning. The twiddle means it is doing disk I/O requests of some sort, so we need to see what it is trying to do. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 03:51:55 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98F0116A473 for ; Thu, 1 Nov 2007 03:51:55 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.freebsd.org (Postfix) with ESMTP id 32D6913C4A8 for ; Thu, 1 Nov 2007 03:51:54 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (adsl-68-252-59-152.dsl.wotnoh.ameritech.net [68.252.59.152]) (authenticated bits=0) by mail.united-ware.com (8.13.8/8.13.8) with ESMTP id lA13MGmt043491 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 31 Oct 2007 23:22:17 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-current@freebsd.org Date: Wed, 31 Oct 2007 23:22:26 -0400 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4984390.EDdBkmoi9k"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200710312322.33301.mistry.7@osu.edu> X-Virus-Scanned: ClamAV 0.91.2/4649/Wed Oct 31 11:27:15 2007 on mail.united-ware.com X-Virus-Status: Clean Subject: Unstopable ata1: FAILURE - non aligned DMA transfer attempted loop X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 03:51:55 -0000 --nextPart4984390.EDdBkmoi9k Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline When trying to access a bad DVD I get the following messages that loop=20 forever until I reboot the machine. The drive is unresponsive so=20 that's the only way to remove the disc. Any ideas? http://am-productions.biz/debug/pciconf.txt Running a recent -CURRENT. I'm also getting this same issue on=20 RELENG_7 on a different machine. Oct 31 12:01:29 littleguy kernel: ata1: FAILURE - non aligned DMA=20 transfer attempted Oct 31 12:01:29 littleguy kernel: acd0: setting up DMA failed Oct 31 12:01:29 littleguy kernel: ata1: FAILURE - non aligned DMA=20 transfer attempted Oct 31 12:01:29 littleguy kernel: acd0: setting up DMA failed Oct 31 12:01:29 littleguy kernel: ata1: FAILURE - non aligned DMA=20 transfer attempted Oct 31 12:01:29 littleguy kernel: acd0: setting up DMA failed Oct 31 12:01:29 littleguy kernel: ata1: FAILURE - non aligned DMA=20 transfer attempted Oct 31 12:01:29 littleguy kernel: acd0: setting up DMA failed Oct 31 12:01:29 littleguy kernel: ata1: FAILURE - non aligned DMA=20 transfer attempted Oct 31 12:01:29 littleguy kernel: acd0: setting up DMA failed Oct 31 12:01:29 littleguy kernel: ata1: FAILURE - non aligned DMA=20 transfer attempted Oct 31 12:01:29 littleguy kernel: acd0: setting up DMA failed Oct 31 12:01:29 littleguy kernel: ata1: FAILURE - non aligned DMA=20 transfer attempted Oct 31 12:01:29 littleguy kernel: acd0: setting up DMA failed Oct 31 12:01:29 littleguy kernel: ata1: FAILURE - non aligned DMA=20 transfer attempted Oct 31 12:01:29 littleguy kernel: acd0: setting up DMA failed =2D-=20 Anish Mistry --nextPart4984390.EDdBkmoi9k Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHKUZ5xqA5ziudZT0RAuFbAJ4lWg2v8mUsKcpx35a6GH657qsy8QCeLXjo tZftQrAN7FoPwIVdT/BM/1I= =XE6S -----END PGP SIGNATURE----- --nextPart4984390.EDdBkmoi9k-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 03:52:31 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0565916A420 for ; Thu, 1 Nov 2007 03:52:31 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.freebsd.org (Postfix) with ESMTP id B101713C4AC for ; Thu, 1 Nov 2007 03:52:30 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so713740pyb for ; Wed, 31 Oct 2007 20:52:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; 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=yl3LddQtu7NO0AiMBgbwuVi9CDFaTB79+3pwCu9HGVM=; b=Q6HRuA5Zb+Z5LgNhhAImg/rkJJLNdkBeoEvX2YYmYP2xvAOVb0BCCbQNukHR5SBJNIeF2bNPOTZJAL4rnShtdyBkjBtmmElychmSdCtdF/2JI0dH/I9A3kHWQYhwDIrPf1lkot1R68juMdF0bo6VBG7pfxHuXgR+QXocpang40o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TECGGD1bkwLeV+I/y+63rUAPTy997k6sU4GcjFPoQnvE+iug3d+w1tdw89L+Rdz7Oh7mz5bOKTl8d/GsDHZ2d4Jr53Uxg/AK7WoV5tROpCejZZ/ZKLAY1IFjnZhVPVKV7rfMgoIlm+QHDiH9XDdZxcxjQCHnHm+OSUYySFNNNrE= Received: by 10.65.254.5 with SMTP id g5mr2754952qbs.1193887664396; Wed, 31 Oct 2007 20:27:44 -0700 (PDT) Received: by 10.65.107.3 with HTTP; Wed, 31 Oct 2007 20:27:44 -0700 (PDT) Message-ID: Date: Thu, 1 Nov 2007 03:27:44 +0000 From: "Aryeh Friedman" To: "Steve Kargl" In-Reply-To: <20071101032145.GA52478@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071101032145.GA52478@troutmask.apl.washington.edu> Cc: freebsd-current@freebsd.org, "freebsd-questions@freebsd.org" Subject: Re: csup broken on -currnet amd64? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 03:52:31 -0000 On 11/1/07, Steve Kargl wrote: > On Thu, Nov 01, 2007 at 03:06:54AM +0000, Aryeh Friedman wrote: > > monster# uname -a > > FreeBSD monster 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Tue Oct 30 > > 18:07:21 UTC 2007 root@:/usr/obj/usr/src/sys/GENERIC amd64 > > > > monster# csup -h cvsup8.us.freebsd.org /usr/share/examples/cvsup/ports-supfile > > Connected to 216.165.129.134 > > Updating collection ports-all/cvs > > Checkout ports/UPDATING > > Receiver: Connection reset by peer > > Will retry at 23:04:37 > > > > monster# csup -h cvsup9.us.freebsd.org /usr/share/examples/cvsup/ports-supfile > > Connected to 128.205.32.21 > > Updating collection ports-all/cvs > > Edit ports/UPDATING^M > > Receiver: Connection reset by peer > > Will retry at 23:05:17 > > Works for me. csup built from source less than 18 hours old. My versions are roughly that old From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 03:57:41 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A657B16A421 for ; Thu, 1 Nov 2007 03:57:41 +0000 (UTC) (envelope-from nslay@comcast.net) Received: from alnrmhc16.comcast.net (alnrmhc16.comcast.net [206.18.177.56]) by mx1.freebsd.org (Postfix) with ESMTP id 3B09813C48A for ; Thu, 1 Nov 2007 03:57:41 +0000 (UTC) (envelope-from nslay@comcast.net) Received: from lightbulb.local (c-68-35-224-189.hsd1.fl.comcast.net[68.35.224.189]) by comcast.net (alnrmhc16) with ESMTP id <20071101032322b16006tu7le>; Thu, 1 Nov 2007 03:23:23 +0000 Message-ID: <4729467C.3080907@comcast.net> Date: Wed, 31 Oct 2007 23:22:36 -0400 From: Nathan Lay User-Agent: Thunderbird 2.0.0.6 (X11/20070805) MIME-Version: 1.0 To: Andrey Chernov , current@freebsd.org References: <20071101025937.GB94332@nagual.pp.ru> In-Reply-To: <20071101025937.GB94332@nagual.pp.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: non-functional backout for review X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 03:57:41 -0000 Andrey Chernov wrote: > Some people complaints that new check in __isctype() is not human readable > and requests for backout. Compiler gives almost identical code for old and > new excepting non-optimized case where non-human readable one wins. I am a > bit tired to change it forth and back, so ask for final consensus here. > > Old one > > return (_c < 0 || _c >= 128) ? 0 : > > New one (requests for backout) > > return (_c & ~0x7F) ? 0 : > > Why not just comment out the old version just above the new version? Best Regards, Nathan Lay From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 06:41:32 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C517D16A417 for ; Thu, 1 Nov 2007 06:41:32 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from ag-out-0708.google.com (ag-out-0708.google.com [72.14.246.246]) by mx1.freebsd.org (Postfix) with ESMTP id 884AF13C4AA for ; Thu, 1 Nov 2007 06:41:32 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by ag-out-0708.google.com with SMTP id 35so269843aga for ; Wed, 31 Oct 2007 23:41:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; bh=yoS5R0LW699zkJKzGt687pQufeI/JqKkblhe+cZ4Ad8=; b=JtNHY+VBv9jXw+0rrcCRRpBsdTQ/ocyCeJmT7AiTx/6Ipo0sP/WMlEry4FgyC9S0rXZ2ehEuQNZ4usbr5pArjqxQCeb8ThDJaj6+Vk2zY5zWbAbDJ6Pdl4gh99shnvFNZ/beHDWR7lQKBRC0yPnd70z0SisuxZVRdVGQ0Os3UCI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=qr2DsCMVb0H1Fm/3vmtUpmyH6/y32i5rMa/BrNNithiZ5DWkU9Q4R9JdpyydoilkHZYQWu1FE3V7aPlUsbYFr2GCd8ClxnpkGLwZ6Et/HzOlPHx1gUWEOL8IW7eK7hH1NOrrgm95Y3XewaUgWum8Z+hwsGauzS3QSFTjxjv+m7I= Received: by 10.70.67.4 with SMTP id p4mr142961wxa.1193898368421; Wed, 31 Oct 2007 23:26:08 -0700 (PDT) Received: from ?192.168.2.2? ( [67.85.89.184]) by mx.google.com with ESMTPS id o29sm2238846elf.2007.10.31.23.26.06 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 31 Oct 2007 23:26:07 -0700 (PDT) Message-ID: <472938FB.4090608@gmail.com> Date: Thu, 01 Nov 2007 02:24:59 +0000 From: "Aryeh M. Friedman" User-Agent: Thunderbird 2.0.0.6 (X11/20071031) MIME-Version: 1.0 To: freebsd-questions@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: optimizing current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 06:41:32 -0000 In /usr/src/UPDATE for 8-CURRENT it says to remove kernel debugging and malloc diagnostics in userland... I have done the first but am not sure if I got the second correct: 1. All I have to do is uncomment #define MALLOC_PRODUCTION in /usr/src/lib/libc/stdlib/malloc.c ? 2. If not what else needs to be done? From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 07:26:37 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7945616A46B for ; Thu, 1 Nov 2007 07:26:37 +0000 (UTC) (envelope-from yaraghchi@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.225]) by mx1.freebsd.org (Postfix) with ESMTP id 0968D13C491 for ; Thu, 1 Nov 2007 07:26:36 +0000 (UTC) (envelope-from yaraghchi@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so306467nzf for ; Thu, 01 Nov 2007 00:26:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=8yHP+NV2IpDyjfE6qaDGFdtzZU4Rlco4DWWInNRgY98=; b=eviaQj5AP5/nCG5e1xAQjwHweRUkc4LaJWKVenyt9bmK/4KKxxWduTrDtICutCqkVzMmUHs3H+3vDfsd3cLvuk+UUScXcCsy0Wq7MJZ1Se7aq2efXnkzY3pz4XFrdM+4GUn0J51qftVtHRe4k+uIAbEklV3MC6bhA8qsIofB+NQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=NDPUIpmR00u2XPhr11qoGh/Kavrrn57M0PANo0hbyM3NYaNgyz7WPY2LOMVAlJVbqeYWbaBqUvM86dGLJvmEAp/sXw+LZnYvfJXOots9TeVuAEElgvWgPUugu3QBfk7KemVStd+LIh0k8WmnF7ahT1uVSfHmdAJuLs2YTou1OqY= Received: by 10.142.225.11 with SMTP id x11mr26029wfg.1193901589916; Thu, 01 Nov 2007 00:19:49 -0700 (PDT) Received: by 10.143.158.18 with HTTP; Thu, 1 Nov 2007 00:19:49 -0700 (PDT) Message-ID: <25f52a3d0711010019v76aef126q6ccae27682f14568@mail.gmail.com> Date: Thu, 1 Nov 2007 08:19:49 +0100 From: "Stephan F. Yaraghchi" Sender: yaraghchi@gmail.com To: freebsd-current@freebsd.org, stephan@yaraghchi.org In-Reply-To: <200710311452.l9VEq33u040716@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <25f52a3d0710300732x425f0c45vde1a29361096c018@mail.gmail.com> <200710311452.l9VEq33u040716@lurza.secnetix.de> X-Google-Sender-Auth: ee99d7c35472d378 Cc: Subject: Re: loader breaks with -O2 optimizations X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 07:26:37 -0000 On 10/31/07, Oliver Fromme wrote: > Stephan F. Yaraghchi wrote: > > After making world on a freshly installed 7.0-BETA1 > > the system does not boot anymore due to a broken loader: > > [...] > > I found out that the following line in my make.conf causes > > the problem: > > > > CFLAGS=3D -O2 -funroll-loops -pipe > > > > After changing down to -O1 and making /usr/src/sys/boot again > > the systems behaves properly at boot. > > Have you tried with the default flags? i.e. simply remove > the CFLAGS line from your make.conf. Does the loader still > break? > > Best regards > Oliver > > PS: The default flags are: -O2 -fno-strict-aliasing -pipe > (see /usr/share/mk/sys.mk) > > -- > Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. > Handelsregister: Registergericht Muenchen, HRA 74606, Gesch=E4ftsfuehrun= g: > secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht M=FC= n- > chen, HRB 125758, Gesch=E4ftsf=FChrer: Maik Bachmann, Olaf Erb, Ralf Geb= hart > > FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd > > "Unix gives you just enough rope to hang yourself -- > and then a couple of more feet, just to be sure." > -- Eric Allman > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > Hi Oliver, I added -O2 -fno-strict-aliasing -pipe to the make.conf and it worked too! Jeremy came up with a post by Josh that points out that the size of the binary seems to be the problem: http://www.nabble.com/buildworld-failure-(boot2.ld-too-big-when-CFLAGS-set-= in-make.conf)-t4674137.html Using the default CFLAGS the resulting loader binary is 290816 Bytes, with -O1 -funroll-loops -pipe it's 319488 Bytes and after adding -funroll-loops to the defaults the binary becames 323584 Bytes... --=20 Stephan www.deine-stimme-gegen-armut.de From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 07:34:06 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3150F16A418 for ; Thu, 1 Nov 2007 07:34:06 +0000 (UTC) (envelope-from yaraghchi@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.226]) by mx1.freebsd.org (Postfix) with ESMTP id E50A613C49D for ; Thu, 1 Nov 2007 07:34:05 +0000 (UTC) (envelope-from yaraghchi@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so307287nzf for ; Thu, 01 Nov 2007 00:34:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=i9krYrGRkQkFVkWgmw89LVQpe7wVa41QwpI4gpkQ5BU=; b=ADMBX3PQWa8pMMapJPz7WOdPHvghPq5QeH/2bigD4r5+l0qrc0vGJUPtq83emSDspgJm6iO/LNTudG8xRnreAlwklcv6qNH2alq8qLaZEdZihb+RxiIos5U2L2nsCiCZev6mQpuj4QXmw1sPbcIFvHXHLlMmDUFehDSJTGSLJIE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=Un34e9dkG2OUsvLqstj0gIsQ/hnf1A5uAbQ1lgp5ImUk6eSBVfMOrd6m7IQ4+Kxl3qNDuZEsJTQcsFZ9GTqHnuwhhJMMbmVYMdIKjdsvs4L1V6i0UUsBN9vlgmrpp99bmKDjdO6FpqVrn4vvjw5/d6AaYi1TC839fDozvAWAOAk= Received: by 10.142.165.9 with SMTP id n9mr27716wfe.1193902046902; Thu, 01 Nov 2007 00:27:26 -0700 (PDT) Received: by 10.143.158.18 with HTTP; Thu, 1 Nov 2007 00:27:26 -0700 (PDT) Message-ID: <25f52a3d0711010027t6b124227gfbddcada12b16e24@mail.gmail.com> Date: Thu, 1 Nov 2007 08:27:26 +0100 From: "Stephan F. Yaraghchi" Sender: yaraghchi@gmail.com To: "Kris Kennaway" In-Reply-To: <4728F43A.1030500@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <25f52a3d0710300732x425f0c45vde1a29361096c018@mail.gmail.com> <47284E4F.5030008@FreeBSD.org> <25f52a3d0710310303w7138bf5ds92698f1b6af2f655@mail.gmail.com> <4728F43A.1030500@FreeBSD.org> X-Google-Sender-Auth: aff41aada20abbf1 Cc: freebsd-current@freebsd.org Subject: Re: loader breaks with -O2 optimizations X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 07:34:06 -0000 On 10/31/07, Kris Kennaway wrote: > Stephan F. Yaraghchi wrote: > > On 10/31/07, Kris Kennaway wrote: > >> Stephan F. Yaraghchi wrote: > >>> After making world on a freshly installed 7.0-BETA1 > >>> the system does not boot anymore due to a broken loader: > >>> > >>> > >>> FreeBSD/i386 bootstrap loader, Revision 1.1 > >>> (root@bigblue, Tue Oct 30 11:26:32 CET 2007) > >>> Can't work out which disk we are booting from. > >>> Guessed BIOS device 0xffffffff not found by probes defaulting to disk0: > >>> > >>> panic: free: guard1 fail@ 0x6ded4 from > >>> /usr/src/sys/boot/i386/loader/../../common/module.c:959 > >>> > >>> --> Press a key on the console to reboot <-- > >>> > >>> > >>> I found out that the following line in my make.conf causes > >>> the problem: > >>> > >>> CFLAGS= -O2 -funroll-loops -pipe > >>> > >>> > >>> After changing down to -O1 and making /usr/src/sys/boot again > >>> the systems behaves properly at boot. > >>> > >>> Is this behavior intended? > >> Maybe, what happens if you use just -O2 -pipe? -funroll-loops is not an > >> appropriate thing to be using globally anyway, unless your intention is > >> to randomly make some code slower. > >> > >> Kris > >> > > > > Hi Kris, > > > > I tried all possible combinations of these switches -- only -O2 led to > > the described > > behaviour. > > Presumably you mean -O2 -funroll-loops, not -O2. Or are you saying the > latter also breaks the loader? > > > Anyway, it's very interesting to hear that adding these optimizations > > to make.conf > > is not recommended, even that -funroll-loops is possibly slowing down > > certain code. > > > > I'm sure many people use it since it's a common tuning tip found on the web. > > I read about it in Dru Lavigne's "BSD Hacks" (O'Reilly)... > > Yes, unfortunately it's bogus advice. What does she say this option is > good for? > > Kris > Hi Kris, you are right: It's the combination of both that causes loader to break. Oliver suggested the defaults (-O2 -fno-strict-aliasing -pipe) and it works. By the way: "BSD Hacks" is a collection of hacks compiled by Dru. Hack #69 deals with tuning and is authored by Avleen Vig. It says: "The -funroll-loops saves one CPU register that would otherwise be tied up in tracking the iteration of the loop, but at the expense of making a slightly larger binary." -- Stephan www.deine-stimme-gegen-armut.de From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 08:30:05 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9D5816A417 for ; Thu, 1 Nov 2007 08:30:05 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id 6439213C4CC for ; Thu, 1 Nov 2007 08:30:05 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 4CEDB45E97; Thu, 1 Nov 2007 09:29:36 +0100 (CET) Received: from localhost (154.81.datacomsa.pl [195.34.81.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 45DC745684; Thu, 1 Nov 2007 09:29:31 +0100 (CET) Date: Thu, 1 Nov 2007 09:29:25 +0100 From: Pawel Jakub Dawidek To: Artem Kuchin Message-ID: <20071101082925.GD13180@garage.freebsd.pl> References: <00f101c819f7$833d5370$0c00a8c0@Artem> <20071031095213.GG8068@garage.freebsd.pl> <02af01c81bb9$7f7828a0$0c00a8c0@Artem> <20071031183838.GB13180@garage.freebsd.pl> <001b01c81bef$54805790$0c00a8c0@Artem> <20071031185826.GC13180@garage.freebsd.pl> <004801c81bf0$e7bec7c0$0c00a8c0@Artem> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nmemrqcdn5VTmUEE" Content-Disposition: inline In-Reply-To: <004801c81bf0$e7bec7c0$0c00a8c0@Artem> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-current@freebsd.org Subject: Re: Problems with gjournal or something else. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 08:30:05 -0000 --nmemrqcdn5VTmUEE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 31, 2007 at 10:04:23PM +0300, Artem Kuchin wrote: > >>My point here is that since it is and example of configuring a=20 > >>gjournaling onf > >>existing system then this 'gjournal label da0s1d da0s1e' will always fa= il. > > > >No. It will fail only if your file system is using the last sector. UFS > >operates on fragments, so if your disk/slice/partition is not > >fragment-aligned it will work. >=20 > So, i shoot myself in a foot and got all those error=3D5 because in my ca= se > i put journal in the same fs and cut 1GB of data from it, right? >=20 > >>Of course it says the warning, but basically, condidering that it=20 > >>overwrites > >>last sector+1 GB of data on existing FS there is actual configuring on > >>existing FS. It is simply destroying it. =20 >=20 > >The example is using separate provider (da0s1e) for the journal, so it > >only needs one sector from da0s1d. >=20 > Ah! i see. >=20 > What about porper journal size? Any recommendations? This is quite important to choose it right. I recommend 2GB. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --nmemrqcdn5VTmUEE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHKY5lForvXbEpPzQRAnpPAJ4nmTkZccxHht8biTYnQyiSh8jGzwCfbghv +DWblJERs+FT4mn+Wf4fu2o= =fzgV -----END PGP SIGNATURE----- --nmemrqcdn5VTmUEE-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 08:37:11 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD53816A41B for ; Thu, 1 Nov 2007 08:37:11 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id EC18C13C48E for ; Thu, 1 Nov 2007 08:37:10 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 3212 invoked from network); 31 Oct 2007 21:53:34 +0300 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 31 Oct 2007 21:53:34 +0300 X-AntiVirus: Checked by Dr.Web [version: 4.44, engine: 4.44.0.09170, virus records: 253097, updated: 31.10.2007] Message-ID: <001901c81bef$542ce060$0c00a8c0@Artem> From: "Artem Kuchin" To: =?UTF-8?B?6Z+T5a625qiZIEJpbGwgSGFja2Vy?= , References: <00f101c819f7$833d5370$0c00a8c0@Artem> <20071031095213.GG8068@garage.freebsd.pl><02af01c81bb9$7f7828a0$0c00a8c0@Artem> <4728B114.80809@conducive.net> Date: Wed, 31 Oct 2007 21:33:37 +0300 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="UTF-8"; reply-type=response Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Cc: Subject: Re: Problems with gjournal or something else. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 08:37:11 -0000 韓家標 Bill Hacker wrote: > Artem Kuchin wrote: >>>> Then did: >>>> >>>> newfs -J -b 8192 -f 1024 -g 50000 -h 20 -i 40960 /dev/twed1s1f >>>> >>>> gjournal load >>>> gjournal label -f /dev/twed1s1f >>>> tunefs -J enable -n disable /dev/twed1s1f >>>> mount -o noatime /dev/twed1s1f.journal /NEW/suit >>> >>> It's wrong order. See gjournal(8) manual page, EXAMPLES section. You >>> cannot create file system and then put journal on the same >>> partition. gjournal would warn you about that, but you used force >>> (-f) option. >> >> Here is what man says: >> >> Configure gjournaling on an existing file system, but only if >> gjournal allows this (i.e.: if the last sector is not already used >> by the file system): >> >> umount /dev/da0s1d >> gjournal label da0s1d da0s1e >> tunefs -J enable -n disable mount -o async /dev/da0s1d.journal /mnt >> mount /dev/da0s1d /mnt >> >> However, this simple does not work. >> gjournal label da0s1d da0s1e - WILL FAIL ON EXISTING FS! >> Need to use -f switch for this. >> >> So, those whole thing will look like this >> >> 1: newfs /dev/da0s1d here we have our EXISTING filesyetm >> 2: gjournal load >> 3: gjournal label -f /dev/da0s1d 4: tunefs -J enable -n disable >> /dev/da0s1d 5: mount -o async /dev/da0s1d.journal /mnt >> >> Now, when you start to fill /mnt you will get error=5 with offset >> out of range >> of the filesystem, beceause metadata for the filesystem is used from >> /dev/da0s1f (step1) but gjournal used 1GB for the journal. >> >> This error goes away if i add additional step between 4 and 5 >> 4.5: newfs /dev/da0s1d.journal >> >> question1: >> >> 4: tunefs -J enable -n disable /dev/da0s1d >> really must be for /dev/da0s1d or for /dev/da0s1d.journal >> >> question2: >> man says >> gjournal label da0s1d da0s1e && tunefs -J enable -n disable && mount >> -o async /dev/da0s1d.journal /mnt || mount /dev/da0s1d /mnt >> >> why there is no fs argument in tunefs? mistake? > > Ah .. does it not expect a raw block device / portion? With no > (other) fs type? osiris# tunefs -p usage: tunefs [-A] [-a enable | disable] [-e maxbpg] [-f avgfilesize] [-J enable | disable ] [-L volname] [-l enable | disable] [-m minfree] [-n enable | disable] [-o space | time] [-p] [-s avgfpdir] special | filesystem So either special or filesystem must be specified > Is this apparent conflict [ occuring | will occur] [because | > if/as/when ] the device has already been given a geom family 'label'. note here. The above example is related to ALRADY EXISTING filesystem. And my point is that IT NEVER WORKS W/O LOOSING DATA! The only was to create properly working journaled fs is to create from scratch. When i created partitions (lables) using sysinstall i had to do then cat /dev/zero > /dev/twed1s1f in otder to erase the label. The proper order seems to be: 1: do fdisk twed1 2: create labels (eg twed1s1f) 3: do cat /dev/zero > /dev/twed1sf into the partition which will be gjournaled 4: gjournal load 5: gjournal label -f /dev/twed1s1f 6: newfs -J /dev/twed1s1f.journal 7: tunefs -J enable -n disable /dev/twed1s1f.journal - I think this one is NOT NEEDED AT ALL! 8: : mount -o noatime /dev/twed1s1f.journal /NEW/suit After all these step journal fs works fine. I wonder how i can check journal usage and if it is really journaled at all :) -- Artem From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 08:37:12 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1595E16A468 for ; Thu, 1 Nov 2007 08:37:12 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id EB58613C48D for ; Thu, 1 Nov 2007 08:37:10 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 3897 invoked from network); 31 Oct 2007 22:04:51 +0300 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 31 Oct 2007 22:04:51 +0300 X-AntiVirus: Checked by Dr.Web [version: 4.44, engine: 4.44.0.09170, virus records: 253189, updated: 31.10.2007] Message-ID: <004801c81bf0$e7bec7c0$0c00a8c0@Artem> From: "Artem Kuchin" To: "Pawel Jakub Dawidek" References: <00f101c819f7$833d5370$0c00a8c0@Artem> <20071031095213.GG8068@garage.freebsd.pl> <02af01c81bb9$7f7828a0$0c00a8c0@Artem> <20071031183838.GB13180@garage.freebsd.pl> <001b01c81bef$54805790$0c00a8c0@Artem> <20071031185826.GC13180@garage.freebsd.pl> Date: Wed, 31 Oct 2007 22:04:23 +0300 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="ISO-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Cc: freebsd-current@freebsd.org Subject: Re: Problems with gjournal or something else. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 08:37:12 -0000 >> My point here is that since it is and example of configuring a gjournaling >> onf >> existing system then this 'gjournal label da0s1d da0s1e' will always fail. > >No. It will fail only if your file system is using the last sector. UFS >operates on fragments, so if your disk/slice/partition is not >fragment-aligned it will work. So, i shoot myself in a foot and got all those error=5 because in my case i put journal in the same fs and cut 1GB of data from it, right? >> Of course it says the warning, but basically, condidering that it overwrites >> last sector+1 GB of data on existing FS there is actual configuring on >> existing FS. It is simply destroying it. >The example is using separate provider (da0s1e) for the journal, so it >only needs one sector from da0s1d. Ah! i see. What about porper journal size? Any recommendations? Also, please, take a look at "BIO_FLUSH on twe driver" thread. -- Artem From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 09:20:38 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4ECB16A421 for ; Thu, 1 Nov 2007 09:20:38 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id C3B5513C4B7; Thu, 1 Nov 2007 09:20:31 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47299A5E.7090607@FreeBSD.org> Date: Thu, 01 Nov 2007 10:20:30 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: josh.carroll@gmail.com References: <25f52a3d0710300732x425f0c45vde1a29361096c018@mail.gmail.com> <47284E4F.5030008@FreeBSD.org> <25f52a3d0710310303w7138bf5ds92698f1b6af2f655@mail.gmail.com> <4728F43A.1030500@FreeBSD.org> <8cb6106e0710311435q3e316599ye259f63679855f72@mail.gmail.com> In-Reply-To: <8cb6106e0710311435q3e316599ye259f63679855f72@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, "Stephan F. Yaraghchi" Subject: Re: loader breaks with -O2 optimizations X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 09:20:38 -0000 Josh Carroll wrote: >> Presumably you mean -O2 -funroll-loops, not -O2. Or are you saying the >> latter also breaks the loader? > > Just -O2 broke it for me in RELENG_7, for the reason I said before > (-O2 later in the gcc command line supersedes the -Os from the loader > Makefile). OK. -funroll-loops is still bogus as a general setting, but I guess the real lesson is to stick with the defaults unless you want to fix the problem :) Kris From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 09:23:36 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFF1816A419 for ; Thu, 1 Nov 2007 09:23:36 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id E6AA613C4B8; Thu, 1 Nov 2007 09:23:35 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47299B1B.9020708@FreeBSD.org> Date: Thu, 01 Nov 2007 10:23:39 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: josh.carroll@gmail.com References: <25f52a3d0710300732x425f0c45vde1a29361096c018@mail.gmail.com> <47284E4F.5030008@FreeBSD.org> <25f52a3d0710310303w7138bf5ds92698f1b6af2f655@mail.gmail.com> <4728F43A.1030500@FreeBSD.org> <8cb6106e0710311435q3e316599ye259f63679855f72@mail.gmail.com> In-Reply-To: <8cb6106e0710311435q3e316599ye259f63679855f72@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, "Stephan F. Yaraghchi" Subject: Re: loader breaks with -O2 optimizations X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 09:23:36 -0000 Josh Carroll wrote: >> Presumably you mean -O2 -funroll-loops, not -O2. Or are you saying the >> latter also breaks the loader? > > Just -O2 broke it for me in RELENG_7, for the reason I said before > (-O2 later in the gcc command line supersedes the -Os from the loader > Makefile). OK. -funroll-loops is still bogus as a general setting, but I guess the real lesson is to stick with the defaults unless you want to fix the problem :) Kris From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 09:23:39 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 779C516A41A for ; Thu, 1 Nov 2007 09:23:39 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (pointyhat.freebsd.org [IPv6:2001:4f8:fff6::2b]) by mx1.freebsd.org (Postfix) with ESMTP id A7FF513C49D; Thu, 1 Nov 2007 09:23:38 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <47299B1D.7030507@FreeBSD.org> Date: Thu, 01 Nov 2007 10:23:41 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: "Stephan F. Yaraghchi" References: <25f52a3d0710300732x425f0c45vde1a29361096c018@mail.gmail.com> <47284E4F.5030008@FreeBSD.org> <25f52a3d0710310303w7138bf5ds92698f1b6af2f655@mail.gmail.com> <4728F43A.1030500@FreeBSD.org> <25f52a3d0711010027t6b124227gfbddcada12b16e24@mail.gmail.com> In-Reply-To: <25f52a3d0711010027t6b124227gfbddcada12b16e24@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: loader breaks with -O2 optimizations X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 09:23:39 -0000 Stephan F. Yaraghchi wrote: > On 10/31/07, Kris Kennaway wrote: >> Stephan F. Yaraghchi wrote: >>> On 10/31/07, Kris Kennaway wrote: >>>> Stephan F. Yaraghchi wrote: >>>>> After making world on a freshly installed 7.0-BETA1 >>>>> the system does not boot anymore due to a broken loader: >>>>> >>>>> >>>>> FreeBSD/i386 bootstrap loader, Revision 1.1 >>>>> (root@bigblue, Tue Oct 30 11:26:32 CET 2007) >>>>> Can't work out which disk we are booting from. >>>>> Guessed BIOS device 0xffffffff not found by probes defaulting to disk0: >>>>> >>>>> panic: free: guard1 fail@ 0x6ded4 from >>>>> /usr/src/sys/boot/i386/loader/../../common/module.c:959 >>>>> >>>>> --> Press a key on the console to reboot <-- >>>>> >>>>> >>>>> I found out that the following line in my make.conf causes >>>>> the problem: >>>>> >>>>> CFLAGS= -O2 -funroll-loops -pipe >>>>> >>>>> >>>>> After changing down to -O1 and making /usr/src/sys/boot again >>>>> the systems behaves properly at boot. >>>>> >>>>> Is this behavior intended? >>>> Maybe, what happens if you use just -O2 -pipe? -funroll-loops is not an >>>> appropriate thing to be using globally anyway, unless your intention is >>>> to randomly make some code slower. >>>> >>>> Kris >>>> >>> Hi Kris, >>> >>> I tried all possible combinations of these switches -- only -O2 led to >>> the described >>> behaviour. >> Presumably you mean -O2 -funroll-loops, not -O2. Or are you saying the >> latter also breaks the loader? >> >>> Anyway, it's very interesting to hear that adding these optimizations >>> to make.conf >>> is not recommended, even that -funroll-loops is possibly slowing down >>> certain code. >>> >>> I'm sure many people use it since it's a common tuning tip found on the web. >>> I read about it in Dru Lavigne's "BSD Hacks" (O'Reilly)... >> Yes, unfortunately it's bogus advice. What does she say this option is >> good for? >> >> Kris >> > > Hi Kris, > > you are right: It's the combination of both that causes loader to break. > > Oliver suggested the defaults (-O2 -fno-strict-aliasing -pipe) and it works. > > By the way: "BSD Hacks" is a collection of hacks compiled by Dru. > Hack #69 deals with tuning and is authored by Avleen Vig. > It says: "The -funroll-loops saves one CPU register that would otherwise > be tied up in tracking the iteration of the loop, but at the expense of making > a slightly larger binary." OK, so it's factually correct but just not good advice :) Kris From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 08:38:05 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91F6416A420; Thu, 1 Nov 2007 08:38:05 +0000 (UTC) (envelope-from wawa@yandex-team.ru) Received: from relanium.yandex.ru (relanium.yandex.ru [213.180.193.88]) by mx1.freebsd.org (Postfix) with ESMTP id 000BC13C4AA; Thu, 1 Nov 2007 08:38:04 +0000 (UTC) (envelope-from wawa@yandex-team.ru) Received: from [87.250.227.221] (v3-227-221.yandex.net [87.250.227.221]) by relanium.yandex.ru (8.14.1/8.14.1) with ESMTP id lA18aaLP040756 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Nov 2007 11:36:37 +0300 (MSK) (envelope-from wawa@yandex-team.ru) Message-ID: <47299014.6020207@yandex-team.ru> Date: Thu, 01 Nov 2007 11:36:36 +0300 From: Vladimir Ivanov Organization: Yandex LLC User-Agent: Thunderbird 1.5.0.14pre (X11/20071023) MIME-Version: 1.0 To: Jack Vogel References: <2a41acea0710310935u6ed33491pcee4c6bd57d12d1a@mail.gmail.com> <4728AFCC.7020706@samsco.org> <47291716.1030904@yandex-team.ru> <2a41acea0710311728n69b5669fxb14fd382e3e072d4@mail.gmail.com> In-Reply-To: <2a41acea0710311728n69b5669fxb14fd382e3e072d4@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: Dr.Web (R) for Mail Servers on relanium.yandex.ru host X-Antivirus-Code: 100000 X-Mailman-Approved-At: Thu, 01 Nov 2007 11:30:25 +0000 Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List Subject: Re: Proposed #ifdef change to em X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 08:38:05 -0000 Hi, Jack Vogel wrote: > Vladimir, > > Your one phrase "more or less patched" invalidated the whole > data point. We are talking about code thats checked in and bound > for 6.3 :) Oops. I've got it. Maybe we talk about different kinds of watchdog. I have meant TX queue watchdogs. Yes, there is a problem with system watchdog in mainstream driver. Sometimes system stops to respond due to kernel activity for a one minute or less. Hardware watchdog can reset system this time. This issue is specific to taskq (fastintr) version of driver The fix is very simple: we've to schedule less priority to RX thread. We use PRI_MAX_KERN instead of PI_NET in Yandex' revision of driver. > > I have hundreds of machines here at Intel that DON'T have the > problem, that's why in early 20th century philosophy they realized > that verification as scientific method was ineffective, falsification > on the other hand is powerful. So if any users out there have > a problem I am trying to understand why. The only way that I > have so far reproduced something like their failure is when > FAST interrupts are enabled, THEN when I disable them on that > same machine the problem disappears. Right now I have still > not figured out why this is, I'm trying to do that as I write this. > > I am also not saying that nothing ever caused a watchdog > before FAST handling, only that as best that I can tell right now > the one repro I have on STABLE, October Snapshot, is related to it. > > Regards, > > Jack > WBR,Vladimir From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 05:09:00 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD49416A481; Thu, 1 Nov 2007 05:08:47 +0000 (UTC) (envelope-from mpp@mppsystems.com) Received: from mail3.gulftel.com (mail3.gulftel.com [216.231.163.44]) by mx1.freebsd.org (Postfix) with ESMTP id 836A013C4A5; Thu, 1 Nov 2007 05:08:47 +0000 (UTC) (envelope-from mpp@mppsystems.com) Received: from localhost (localhost [127.0.0.1]) by mail3.gulftel.com (Postfix) with ESMTP id C629B2AA6B; Wed, 31 Oct 2007 20:37:55 -0500 (CDT) X-Virus-Scanned: amavisd-new at gulftel.com Received: from mail3.gulftel.com ([127.0.0.1]) by localhost (mail3.gulftel.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6jETPNVxl7w0; Wed, 31 Oct 2007 20:37:52 -0500 (CDT) Received: from mail.mppsystems.com (unknown [10.17.28.253]) by mail3.gulftel.com (Postfix) with ESMTP id 993402A948; Wed, 31 Oct 2007 20:37:48 -0500 (CDT) Received: by mail.mppsystems.com (Postfix, from userid 1000) id 311FA17041; Wed, 31 Oct 2007 20:37:48 -0500 (CDT) Date: Wed, 31 Oct 2007 20:37:48 -0500 From: Mike Pritchard To: Red Neck Message-ID: <20071101013748.GA1116@mail.mppsystems.com> References: <862892.31020.qm@web27810.mail.ukl.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <862892.31020.qm@web27810.mail.ukl.yahoo.com> User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Mailman-Approved-At: Thu, 01 Nov 2007 11:30:50 +0000 Cc: freebsd-current@freebsd.org Subject: Re: Loader broken in Head? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 05:09:00 -0000 > On Friday 26 October 2007 08:03:21 pm Red Neck wrote: > Hi, > > Within the last day (26/10/07) I've built and installed the sources > from CVS > Head only to find the stage 3 boot loader, /boot/loader, not working. > I'm > using a Mac Pro with 3 internal hard drives. On one hard disk I have > FreeBSD amd64 installed, occupying the entire disk (MBR). Using the sources > from Head, loader just freezes after displaying its initial messages with a > constantly spinning cursor. To access the system I have to revert to using > an older loader such as 6.2 release's. I have attached my make and kernel > config. I was seeing a similar problem. Booting from a floppy disk twice would probably be faster than booting off the hard disk. I had just done a makeworld, and updated the boot blocks on the disk (it previously had a pretty old install on it). But the system would eventually boot, and not hang up. I noticed that Red Necks boot loader build date was the same as the version I was having problems with. Fortunately, I have a 2nd HD in the machine with a 7.0 install, and installed the boot blocks from that HD to the one I was having problems with, and copied over /boot/loader from that HD. No more problems. System boots as fast as ever. So yes, I think there is something wrong with the current loader. With the slow boot, once the system is up and running, the disks are running at normal speeds (checked with iozone & bonnie). Some output from a slow boot with some comments in []'s to note how long things are taking (it took so long I was able to type all that initial boot information into a window on another machine): BTX loader 1.00 BTX version is 1.01 Consoles: internal video/keyboard BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS 639kb/1047488kB available memory FreeBSD/i386 bootstrap loader, Revision 1.1 (mpp@mail.mppsystems.com, Thu Oct 25 00:32:20 CDT 2007) Loading /boot/defaults/loader.conf /-\|/...[wait about 2 mins] /boot/kernel/kernel text=0x37e650 [spin for 3 mins] data=0x39600+0x30860 [30 seconds] syms=[0x4+0x44590+0x4+0x57708] [spin for about 2 mins] OK lsdev cd devices: disk devices: disk0: BIOS drive C: disk0s1a: FFS disk0s1d: FFS disk0s2a: FFS disk0s2b: swap disk0s2d: FFS disk0s2e: FFS disk0s2f: FFS disk0s3b: swap disk0s3d: FFS disk0s3e: FFS disk0s3f: FFS disk0s3g: FFS disk0: BIOS drive D: disk1s1a: FFS disk1s1b: swap disk1s1D: FFS disk1s1e: FFS disk1s1f: FFS pxe devices: OK boot [spins for about 30 seconds or so loading acpi.ko] [system boots normally now] 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 8.0-CURRENT #16: Thu Oct 25 17:55:37 CDT 2007 mpp@mail.mppsystems.com:/shared/src/sys/i386/compile/MAIL WARNING: DIAGNOSTIC option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) III CPU 1133MHz (1130.12-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 Features=0x383fbff real memory = 1073676288 (1023 MB) avail memory = 1041489920 (993 MB) ACPI APIC Table: [trimmed] atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xd400-0xd40f at device 7.1 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] ad0: 76319MB at ata0-master UDMA100 acd0: CDROM at ata0-slave PIO4 ad2: 28629MB at ata1-master UDMA100 Trying to mount root from ufs:/dev/ad0s1a -- Mike Pritchard mpp @ FreeBSD.org "If tyranny and oppression come to this land, it will be in the guise of fighting a foreign enemy." - James Madison (1787) From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 03:22:54 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C18F316A419 for ; Thu, 1 Nov 2007 03:22:54 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from ipmail01.adl2.internode.on.net (ipmail01.adl2.internode.on.net [203.16.214.140]) by mx1.freebsd.org (Postfix) with ESMTP id 0B59D13C494 for ; Thu, 1 Nov 2007 03:22:53 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) X-IronPort-AV: E=Sophos;i="4.21,354,1188743400"; d="scan'208";a="223319465" Received: from ppp121-45-121-213.lns11.adl6.internode.on.net (HELO mail.clearchain.com) ([121.45.121.213]) by ipmail01.adl2.internode.on.net with ESMTP; 01 Nov 2007 12:27:58 +1030 Received: from wolf.clearchain.com (wcl.ml.unisa.edu.au [130.220.166.5]) (authenticated bits=0) by mail.clearchain.com (8.13.8/8.13.8) with ESMTP id lA11vmUK089920 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 1 Nov 2007 12:27:55 +1030 (CST) (envelope-from Benjamin.Close@clearchain.com) Message-ID: <4729329B.2060805@clearchain.com> Date: Thu, 01 Nov 2007 12:27:47 +1030 From: Benjamin Close User-Agent: Thunderbird 2.0.0.0 (X11/20070615) MIME-Version: 1.0 To: freebsd-current Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on pegasus.clearchain.com X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (mail.clearchain.com [192.168.154.1]); Thu, 01 Nov 2007 12:27:55 +1030 (CST) X-Mailman-Approved-At: Thu, 01 Nov 2007 11:31:04 +0000 Subject: ZFS Panic: Memory Modified After Free X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 03:22:54 -0000 Hi Folks, I got a "memory modified after free" panic with zfs whilst dumping 1000's of debug messages/sec to syslog (long story) Sadly I've no serial console so ddb info is via photos: http://wcl.ml.unisa.edu.au/~closebs/FreeBSD Photo order: o Panic msg & backtrace (445) o lockedvnods with trace (446) o ps (460) o uma (448) o proc (449) o witness (450) o all pcpu (480) box: FreeBSD wolf.clearchain.com 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Thu Oct 11 08:12:46 CST 2007 benjsc@wolf:~| ident /boot/kernel/zfs.ko /boot/kernel/zfs.ko: $FreeBSD: src/sys/compat/opensolaris/kern/opensolaris_kmem.c,v 1.2 2007/04/10 02:35:56 pjd Exp $ $FreeBSD: src/sys/compat/opensolaris/kern/opensolaris_kobj.c,v 1.4 2007/05/31 11:51:49 kib Exp $ $FreeBSD: src/sys/compat/opensolaris/kern/opensolaris_kstat.c,v 1.2 2007/06/04 18:25:03 dwmalone Exp $ $FreeBSD: src/sys/compat/opensolaris/kern/opensolaris_misc.c,v 1.2 2007/04/23 00:52:06 pjd Exp $ $FreeBSD: src/sys/compat/opensolaris/kern/opensolaris_policy.c,v 1.2 2007/06/12 00:11:57 rwatson Exp $ $FreeBSD: src/sys/compat/opensolaris/kern/opensolaris_vfs.c,v 1.6 2007/06/04 11:31:45 pjd Exp $ $FreeBSD: src/sys/compat/opensolaris/kern/opensolaris_zone.c,v 1.1 2007/04/06 01:09:06 pjd Exp $ (gdb) l *zfs_kmem_alloc+0x12 0x3f62 is in zfs_kmem_alloc (/devel/src/sys/modules/zfs/../../compat/opensolaris/kern/opensolaris_kmem.c:90). 85 /devel/src/sys/modules/zfs/../../compat/opensolaris/kern/opensolaris_kmem.c: No such file or directory. in /devel/src/sys/modules/zfs/../../compat/opensolaris/kern/opensolaris_kmem.c (gdb) l *dmu_buf_hold_array_by_dnode+0x91 0x1aa51 is in dmu_buf_hold_array_by_dnode (/devel/src/sys/modules/zfs/../../contrib/opensolaris/uts/common/fs/zfs/dmu.c:193). 188 /devel/src/sys/modules/zfs/../../contrib/opensolaris/uts/common/fs/zfs/dmu.c: No such file or directory. in /devel/src/sys/modules/zfs/../../contrib/opensolaris/uts/common/fs/zfs/dmu.c I *think* I've been able to reproduce this just not provide any info ddb due to sc being hosed, so can't console switch (ie ddb commands wor just no visuals) and panic proved useless. Cheers, Benjamin From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 11:53:58 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C68416A417 for ; Thu, 1 Nov 2007 11:53:58 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 06A1F13C4A7 for ; Thu, 1 Nov 2007 11:53:57 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 24DCA209D; Thu, 1 Nov 2007 12:53:20 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.1/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 12F35209B; Thu, 1 Nov 2007 12:53:20 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id 97EDA84479; Thu, 1 Nov 2007 12:53:19 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "Stephan F. Yaraghchi" References: <25f52a3d0710300732x425f0c45vde1a29361096c018@mail.gmail.com> <47284E4F.5030008@FreeBSD.org> <25f52a3d0710310303w7138bf5ds92698f1b6af2f655@mail.gmail.com> <4728F43A.1030500@FreeBSD.org> <25f52a3d0711010027t6b124227gfbddcada12b16e24@mail.gmail.com> Date: Thu, 01 Nov 2007 12:53:19 +0100 In-Reply-To: <25f52a3d0711010027t6b124227gfbddcada12b16e24@mail.gmail.com> (Stephan F. Yaraghchi's message of "Thu\, 1 Nov 2007 08\:27\:26 +0100") Message-ID: <86ve8muqq8.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: loader breaks with -O2 optimizations X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 11:53:58 -0000 "Stephan F. Yaraghchi" writes: > By the way: "BSD Hacks" is a collection of hacks compiled by Dru. > Hack #69 deals with tuning and is authored by Avleen Vig. > It says: "The -funroll-loops saves one CPU register that would otherwise > be tied up in tracking the iteration of the loop, but at the expense of m= aking > a slightly larger binary." Avleen Vig is a clueless ****. I've rebutted his "tuning advice" several times in the past. I'm sorry to hear that Dru lends him her authority. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 12:01:01 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0F5316A41B for ; Thu, 1 Nov 2007 12:01:01 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id AB43913C4AC for ; Thu, 1 Nov 2007 12:01:01 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 9502020A2; Thu, 1 Nov 2007 13:00:40 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.1/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 06669209E; Thu, 1 Nov 2007 13:00:40 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id E177584481; Thu, 1 Nov 2007 13:00:39 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "Aryeh M. Friedman" References: <472938FB.4090608@gmail.com> Date: Thu, 01 Nov 2007 13:00:39 +0100 In-Reply-To: <472938FB.4090608@gmail.com> (Aryeh M. Friedman's message of "Thu\, 01 Nov 2007 02\:24\:59 +0000") Message-ID: <86mytyuqe0.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, freebsd-questions@freebsd.org Subject: Re: optimizing current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 12:01:02 -0000 "Aryeh M. Friedman" writes: > In /usr/src/UPDATE for 8-CURRENT it says to remove kernel debugging and > malloc diagnostics in userland... I have done the first but am not sure > if I got the second correct: man malloc DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 12:03:51 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84B5416A420; Thu, 1 Nov 2007 12:03:51 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id F1A1913C48A; Thu, 1 Nov 2007 12:03:50 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 1B5B3209B; Thu, 1 Nov 2007 12:54:00 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.1/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 0E0C32092; Thu, 1 Nov 2007 12:54:00 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id E6DAF84485; Thu, 1 Nov 2007 12:53:59 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Jeremy Chadwick References: <25f52a3d0710300732x425f0c45vde1a29361096c018@mail.gmail.com> <20071031053610.GA10176@eos.sc1.parodius.com> <86ir4nxv8o.fsf@ds4.des.no> <20071031143010.GA21646@eos.sc1.parodius.com> Date: Thu, 01 Nov 2007 12:53:59 +0100 In-Reply-To: <20071031143010.GA21646@eos.sc1.parodius.com> (Jeremy Chadwick's message of "Wed\, 31 Oct 2007 07\:30\:10 -0700") Message-ID: <86r6jauqp4.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, "Stephan F. Yaraghchi" Subject: Re: loader breaks with -O2 optimizations X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 12:03:51 -0000 Jeremy Chadwick writes: > On Wed, Oct 31, 2007 at 02:35:19PM +0100, Dag-Erling Sm=C3=B8rgrav wrote: > > Jeremy Chadwick writes: > > > Stephan F. Yaraghchi writes: > > > > CFLAGS=3D -O2 -funroll-loops -pipe > > > You shouldn't have this in your make.conf. Remove it. This is very > > > likely breaking a lot more than just loader. > > Uh, no. Please stop spreading FUD. > Every time it's been discussed, the conclusion reached has been "stop > setting CFLAGS, you're overwriting any previous definition used, which > may be causing problems for you. Use +=3D or COPTFLAGS." Even the > Handbook explains the dangers of using CFLAGS=3D when one should be > CFLAGS+=3D. So why didn't you say that in the first place, instead of "remove it"? DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 12:27:48 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDD6316A419 for ; Thu, 1 Nov 2007 12:27:48 +0000 (UTC) (envelope-from brucec@muon.bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [IPv6:2001:41c8:1:548a::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5725713C4AC for ; Thu, 1 Nov 2007 12:27:48 +0000 (UTC) (envelope-from brucec@muon.bluestop.org) Received: by muon.bluestop.org (Postfix, from userid 1000) id 8BAC330180; Thu, 1 Nov 2007 12:27:46 +0000 (GMT) Date: Thu, 1 Nov 2007 12:27:46 +0000 From: bruce@cran.org.uk To: "Stephan F. Yaraghchi" Message-ID: <20071101122745.GA16586@muon.bluestop.org> References: <25f52a3d0710300732x425f0c45vde1a29361096c018@mail.gmail.com> <47284E4F.5030008@FreeBSD.org> <25f52a3d0710310303w7138bf5ds92698f1b6af2f655@mail.gmail.com> <4728F43A.1030500@FreeBSD.org> <25f52a3d0711010027t6b124227gfbddcada12b16e24@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <25f52a3d0711010027t6b124227gfbddcada12b16e24@mail.gmail.com> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-current@freebsd.org Subject: Re: loader breaks with -O2 optimizations X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 12:27:49 -0000 On Thu, Nov 01, 2007 at 08:27:26AM +0100, Stephan F. Yaraghchi wrote: > On 10/31/07, Kris Kennaway wrote: > > Stephan F. Yaraghchi wrote: > > > On 10/31/07, Kris Kennaway wrote: > > >> Stephan F. Yaraghchi wrote: > > >>> After making world on a freshly installed 7.0-BETA1 > > >>> the system does not boot anymore due to a broken loader: > > >>> > > >>> > > >>> FreeBSD/i386 bootstrap loader, Revision 1.1 > > >>> (root@bigblue, Tue Oct 30 11:26:32 CET 2007) > > >>> Can't work out which disk we are booting from. > > >>> Guessed BIOS device 0xffffffff not found by probes defaulting to disk0: > > >>> > > >>> panic: free: guard1 fail@ 0x6ded4 from > > >>> /usr/src/sys/boot/i386/loader/../../common/module.c:959 > > >>> > > >>> --> Press a key on the console to reboot <-- > > >>> > > >>> > > >>> I found out that the following line in my make.conf causes > > >>> the problem: > > >>> > > >>> CFLAGS= -O2 -funroll-loops -pipe > > >>> > > >>> > > >>> After changing down to -O1 and making /usr/src/sys/boot again > > >>> the systems behaves properly at boot. > > >>> > > >>> Is this behavior intended? > > >> Maybe, what happens if you use just -O2 -pipe? -funroll-loops is not an > > >> appropriate thing to be using globally anyway, unless your intention is > > >> to randomly make some code slower. > > >> > > >> Kris > > >> > > > > > > Hi Kris, > > > > > > I tried all possible combinations of these switches -- only -O2 led to > > > the described > > > behaviour. > > > > Presumably you mean -O2 -funroll-loops, not -O2. Or are you saying the > > latter also breaks the loader? > > > > > Anyway, it's very interesting to hear that adding these optimizations > > > to make.conf > > > is not recommended, even that -funroll-loops is possibly slowing down > > > certain code. > > > > > > I'm sure many people use it since it's a common tuning tip found on the web. > > > I read about it in Dru Lavigne's "BSD Hacks" (O'Reilly)... > > > > Yes, unfortunately it's bogus advice. What does she say this option is > > good for? > > > > Kris > > > > Hi Kris, > > you are right: It's the combination of both that causes loader to break. > > Oliver suggested the defaults (-O2 -fno-strict-aliasing -pipe) and it works. > > By the way: "BSD Hacks" is a collection of hacks compiled by Dru. > Hack #69 deals with tuning and is authored by Avleen Vig. > It says: "The -funroll-loops saves one CPU register that would otherwise > be tied up in tracking the iteration of the loop, but at the expense of making > a slightly larger binary." > > -- > Stephan > There's a good thread explaining why -funroll-loops is generally bad and why it breaks the loader at http://lists.freebsd.org/pipermail/freebsd-stable/2006-September/028340.html -- Bruce From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 12:43:27 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F34D016A417 for ; Thu, 1 Nov 2007 12:43:26 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.freebsd.org (Postfix) with ESMTP id 6C0F013C4A7 for ; Thu, 1 Nov 2007 12:43:26 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so376149nfb for ; Thu, 01 Nov 2007 05:43:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; 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=/v+w9e1hcaf3a7CKwXPdJw9zoV4qFiwrcybUkWtb57U=; b=dx7e+HvJ4ICJxuTZ4QZjLnYc3be8NVWNDkYhcsSNHL3Oiag9Nx1nJ8W9Ls3nnse8783VsG8szlWyYfgGlJBYyXsihVQi2PkRnRorupHXY3i/0D1nCOHv8mjyV9T9eMMDgOroPFtHpYBKk6RkzsBVjsTf+0YWgSltFEV33cTL6b8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jnooZWewUr80pS/upEriLd1Cg8eyPlJzQV5pdiUehiNcbv+xDrEeAEB2AkzjT8oe8SWzMjQApt1fqBU7vTY7C4D6mLu7Xa7p1D7TQ6JEwjjh70aZ240yFVY2N7gM34aqwYDpgl8L21PVdCYLjcb7KJpyaLBWZEVMcFMXc6rwxEI= Received: by 10.78.160.2 with SMTP id i2mr354241hue.1193920550411; Thu, 01 Nov 2007 05:35:50 -0700 (PDT) Received: by 10.78.42.6 with HTTP; Thu, 1 Nov 2007 05:35:50 -0700 (PDT) Message-ID: Date: Thu, 1 Nov 2007 15:35:50 +0300 From: pluknet To: "John Baldwin" In-Reply-To: <200710251511.13161.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200710251511.13161.jhb@freebsd.org> Cc: freebsd-current@freebsd.org, syle ishere Subject: Re: kernel panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 12:43:27 -0000 On 25/10/2007, John Baldwin wrote: > On Thursday 25 October 2007 01:10:33 pm syle ishere wrote: > > > > I tried testing this. Added > > LOADER_FIREWIRE_SUPPORT=yes in /etc/make.conf > > (cd /sys/boot/i386 && make clean && make && make install)shutdown -r now > > All was great it the loader worked! > > > > To test this wasn't my imagination: > > I took that line out of make.conf > > (cd /sys/boot/i386 && make clean && make && make install)shutdown -r now > > > > And got same problem system not booting. > > > > Good catch pluknet, hopefully we can get this code compiled into the loader > as a mandatory fix > > for now. > > That seems odd. I would make sure you really have a clean build, and I would > build from /sys/boot, not /sys/boot/i386. > > -- > John Baldwin > Yes. I've just checked that loader brokeness is influenced by -funroll-loops in make.conf wbr, pluknet From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 12:44:30 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1C7116A418; Thu, 1 Nov 2007 12:44:30 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 4746413C48E; Thu, 1 Nov 2007 12:44:30 +0000 (UTC) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id lA1Chrhd034802; Thu, 1 Nov 2007 13:43:54 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id lA1ChiGm052231 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 1 Nov 2007 13:43:45 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id lA1Chi7d092130; Thu, 1 Nov 2007 13:43:44 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id lA1ChgCp092129; Thu, 1 Nov 2007 13:43:42 +0100 (CET) (envelope-from ticso) Date: Thu, 1 Nov 2007 13:43:41 +0100 From: Bernd Walter To: "Matthew D. Fuller" Message-ID: <20071101124341.GL82954@cicely12.cicely.de> References: <4724BAD9.7000400@charter.net> <20071028164152.GA7516@eos.sc1.parodius.com> <4724BEB3.5080905@charter.net> <20071029132447.GA2658@kobe.laptop> <4727063E.7060107@dial.pipex.com> <20071031143923.GA1580@over-yonder.net> <20071031190830.GJ82954@cicely12.cicely.de> <20071031193045.GD1580@over-yonder.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071031193045.GD1580@over-yonder.net> X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-4.2 required=5.0 tests=ALL_TRUSTED=-1.8, AWL=0.149, BAYES_00=-2.599 autolearn=ham version=3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on cicely12.cicely.de Cc: stable@freebsd.org, ticso@cicely.de, Alex Zbyslaw , current@freebsd.org Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 12:44:30 -0000 On Wed, Oct 31, 2007 at 02:30:45PM -0500, Matthew D. Fuller wrote: > On Wed, Oct 31, 2007 at 08:08:31PM +0100 I heard the voice of > Bernd Walter, and lo! it spake thus: > > > > I don't completly agree. > > Many people forget that FreeBSD is used on slow embedded systems as > > well and I prefer having manpoages there as well. > > Oh, I don't argue that there are cases where catpages are still > useful. But I think they're the exception, not the rule. When you're > setting up a tiny system (by whatever the standards of the given day > are) or an appliance, you expect the tradeoffs to be rather different > than on a normal (by said standards) general-purpose computer. My point was against retirement, which was mentioned by Alex. For me and many others slow systems are daily business. For many others modern systems are daily business, but those shouldn't think they are alone. We have already to face many slowdowns over the last years, such as the new rc.d system, which is painly slow on slow systems, but it has a real win, so I never complained against rc.d as such and I can live with it, since my systems rarely reboot. In case of catman retirement I just don't see the win, only the negative and just because many people don't see it doesn't mean it doesn't exist. Why do you expect me any tradeoff when there is nothing to trade? Show me the positives that outweights the negatives and I'm on your side. > Heck, looking at Soekris, everything above the 4501 class is probably > faster than my laptop 8-} Yes - but the 4501 is not the slowest system we support. And - many people may be surprised - but the 4501 is extremly power hungry compared to what we can do with ARM. The difference between a 4501 and an at91rm9200 based system is nearly a factor three, so there are valid reasons for such a system. And the at91rm9200 is very compareable in speed when it comes to network traffic, although it seems to be unexpected slow on some other points. -- B.Walter http://www.bwct.de http://www.fizon.de bernd@bwct.de info@bwct.de support@fizon.de From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 13:15:45 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC22F16A41A for ; Thu, 1 Nov 2007 13:15:45 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.freebsd.org (Postfix) with ESMTP id 83F2913C4A7 for ; Thu, 1 Nov 2007 13:15:45 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: by ug-out-1314.google.com with SMTP id y2so532290uge for ; Thu, 01 Nov 2007 06:15:10 -0700 (PDT) Received: by 10.67.116.4 with SMTP id t4mr2554652ugm.1193916344367; Thu, 01 Nov 2007 04:25:44 -0700 (PDT) Received: from orion ( [89.162.141.1]) by mx.google.com with ESMTPS id w40sm2173523ugc.2007.11.01.04.25.40 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 01 Nov 2007 04:25:42 -0700 (PDT) From: Nikolay Pavlov To: freebsd-current@freebsd.org Date: Thu, 1 Nov 2007 13:25:38 +0200 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) References: <00f101c819f7$833d5370$0c00a8c0@Artem> <20071031183838.GB13180@garage.freebsd.pl> <001b01c81bef$54805790$0c00a8c0@Artem> In-Reply-To: <001b01c81bef$54805790$0c00a8c0@Artem> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4706926.G1fZXTkjVL"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200711011325.42580.qpadla@gmail.com> Cc: Artem Kuchin , Pawel Jakub Dawidek Subject: Re: Problems with gjournal or something else. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: qpadla@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 13:15:46 -0000 --nextPart4706926.G1fZXTkjVL Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 31 October 2007 20:53:07 Artem Kuchin wrote: > For any fs size and disk operations intensity? Mine is about 260GB > moderatelly used. The journal size is not related to the HDD size. It's related to the number= =20 and value of the operations between data syncs. I am using 1GB on my=20 notebook and never see any problems.=20 =2D-=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 =2D Best regards, Nikolay Pavlov. <<<----------------------------------- = =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 --nextPart4706926.G1fZXTkjVL Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBHKbe2/2R6KvEYGaIRAhw0AKDbrYlHO+6tipmKdTEq3wcbvlQ99gCeMi6k FbW9p8nL2I0A1B4WbtHQdcU= =Gk9M -----END PGP SIGNATURE----- --nextPart4706926.G1fZXTkjVL-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 13:26:10 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AABD516A469; Thu, 1 Nov 2007 13:26:10 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from optimus.centralmiss.com (ns.centralmiss.com [206.156.254.79]) by mx1.freebsd.org (Postfix) with ESMTP id 7CD2013C4B5; Thu, 1 Nov 2007 13:26:10 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by optimus.centralmiss.com (Postfix) with ESMTP id C7DD728433; Thu, 1 Nov 2007 07:59:09 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 498A861C42; Thu, 1 Nov 2007 07:59:09 -0500 (CDT) Date: Thu, 1 Nov 2007 07:59:09 -0500 From: "Matthew D. Fuller" To: ticso@cicely.de Message-ID: <20071101125909.GA52150@over-yonder.net> References: <4724BAD9.7000400@charter.net> <20071028164152.GA7516@eos.sc1.parodius.com> <4724BEB3.5080905@charter.net> <20071029132447.GA2658@kobe.laptop> <4727063E.7060107@dial.pipex.com> <20071031143923.GA1580@over-yonder.net> <20071031190830.GJ82954@cicely12.cicely.de> <20071031193045.GD1580@over-yonder.net> <20071101124341.GL82954@cicely12.cicely.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071101124341.GL82954@cicely12.cicely.de> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.16-fullermd.4 (2007-06-09) Cc: stable@freebsd.org, current@freebsd.org, Alex Zbyslaw Subject: Re: /usr/share/man/man8/MAKEDEV.8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 13:26:10 -0000 On Thu, Nov 01, 2007 at 01:43:41PM +0100 I heard the voice of Bernd Walter, and lo! it spake thus: > > Show me the positives that outweights the negatives and I'm on your > side. Why do you think we're on different sides to begin with? I've not advocated removing catman capability, or denied that different situations have different needs, or that those needs may include catman, or for that matter said anything at all applicable to tiny environments or appliance building. The sole and entire point of my mail was to provide a handful of data points supporting the idea that on new, not particularly new, and even pretty freakin' old "normal" computers, there's no pressing performance need for catman. That there exist people with even older systems where the situation is otherwise, or situations with new (but otherwise aimed) systems other than general purpose systems aimed at workstations and servers, is not something I've ever denied, but it's also not at all related to what I was talking about. None of my statements were ever INTENDED to be applied in those cases, so why should you be surprised that they're invalid there? -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 14:26:09 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C791C16A418 for ; Thu, 1 Nov 2007 14:26:09 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id 5317513C481 for ; Thu, 1 Nov 2007 14:26:08 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from anb.matik.com.br (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.14.1/8.13.1) with ESMTP id lA1DC7HS041504 for ; Thu, 1 Nov 2007 11:12:07 -0200 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: current@freebsd.org Date: Thu, 1 Nov 2007 11:11:49 -0200 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200711011111.49847.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on msrv.matik.com.br X-Virus-Status: Clean Cc: Subject: kernel panic / bge related? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 14:26:09 -0000 Hi I get this trap on screen and seems the pointer leads to the bge nic ffffffff801e7050 t bge_newbuf_jumbo ffffffff801e7300 t bge_rxeof ffffffff801e77c0 t bge_ifmedia_upd_locked ffffffff801e79a0 t bge_start_locked any sugestion what I should look for? fatal trap 12:page fault while in kernel mode cpuid =3D 0 ; apic id =3D 00 fault virtual address =3D 0x28 fault code =3D supervisor write data, page not present instruction pointer:08:0xffffffff801e74b9 stack pointer=3D0x10:0xffffffffabfd0af0 frame pointer =3D0x10:0xffffffffad3dd680 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3DDPL 0,pres1 long 1,def 32 0, gran 1 process eflags=3D interrupt enable resume, IOPL =3D 0 current process =3D 16 (sri1:net) trap number =3D 12 panic:page fault cpuid=3D0 uptime:10h13m50s physical memory:4024mb dumping 541 mb =46reeBSD wco-ssp.speedvip.com.br 7.0-BETA1 FreeBSD 7.0-BETA1 #0: Tue Oct 3= 0=20 02:58:39 BRT 2007 mm@wco-ssp.speedvip.com.br:/usr/obj/usr/src/sys/wco7a= =20 amd64 =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 15:25:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8552716A420 for ; Thu, 1 Nov 2007 15:25:18 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id 2D8DC13C4B0 for ; Thu, 1 Nov 2007 15:25:17 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8p) with ESMTP id 217264608-1834499 for multiple; Thu, 01 Nov 2007 10:24:02 -0500 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id lA1FNpfe006973; Thu, 1 Nov 2007 11:23:51 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Jack Vogel" Date: Thu, 1 Nov 2007 11:21:15 -0400 User-Agent: KMail/1.9.6 References: <20071011003619.GA84433@obelix.dsto.defence.gov.au> <200710312232.l9VMWgJJ090112@lava.sentex.ca> <2a41acea0710311544x5db98f27ta0f1276fd06d13f@mail.gmail.com> In-Reply-To: <2a41acea0710311544x5db98f27ta0f1276fd06d13f@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711011121.15687.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 01 Nov 2007 11:23:51 -0400 (EDT) X-Virus-Scanned: ClamAV 0.91.2/4658/Thu Nov 1 08:50:49 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-current@freebsd.org, Mike Tancsa Subject: Re: em0: watchdog timeout ... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 15:25:18 -0000 On Wednesday 31 October 2007 06:44:36 pm Jack Vogel wrote: > On 10/31/07, Mike Tancsa wrote: > > At 06:25 PM 10/31/2007, Jack Vogel wrote: > > > > > > > > > >What if you use MSI? > > > > > > > > How do I enable that ? > > > > > >sysctl hw.pci.enable_msi=1 > > > > > >and > > > > > >sysctl hw.pci.enable_msix=1 > > > > > >For those that don't know, MSI/X is there in STABLE but off by default. > > > > Thanks, > > Do I need to do this in /boot/loader.conf or can I set it at > > any time? Are there any performance hits / boosts to use this method > > instead of the default ? > > I have set it after the system booted and it seemed to work. > > John could speak more authoritatively since he wrote it, but I have > seen no problem turning em use on whenever. Uh, this means of > course, enabling it and THEN loading the driver, if em is loaded and > you enable the system it will have no effect on em until unload and > reloading it. > > John has also said that MSI in 6.X is not as full an implementation as > in 7 but I don't recall what that amounted to. > > It means you have a unique unshared interrupt, I have never really had > any performance tests done on MSI vs Legacy so I can't speak to that. The only thing MSI in 6.x doesn't have is the MSI-X remap function, the rest of the implementation is identical. I just haven't enabled it by default on 6.x due to caution. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 15:32:28 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C68E616A417 for ; Thu, 1 Nov 2007 15:32:28 +0000 (UTC) (envelope-from freebsd@superhero.nl) Received: from superman.superhero.nl (superhero.nl [82.95.198.17]) by mx1.freebsd.org (Postfix) with ESMTP id 1DAB213C4A8 for ; Thu, 1 Nov 2007 15:32:27 +0000 (UTC) (envelope-from freebsd@superhero.nl) Received: (qmail 10073 invoked by uid 80); 1 Nov 2007 11:31:32 -0000 Received: from a80-127-127-95.adsl.xs4all.nl ([80.127.127.95]) (SquirrelMail authenticated user gelsemap) by webmail.superhero.nl with HTTP; Thu, 1 Nov 2007 12:31:32 +0100 (CET) Message-ID: <1154.80.127.127.95.1193916692.squirrel@webmail.superhero.nl> Date: Thu, 1 Nov 2007 12:31:32 +0100 (CET) From: "Gelsema, P \(Patrick\) - FreeBSD" To: freebsd-current@freebsd.org User-Agent: SquirrelMail/1.4.8 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: da0 detection garbled: da0: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 15:32:28 -0000 Hi all, on FreeBSD hulk.superhero.nl 7.0-BETA1 FreeBSD 7.0-BETA1 #0: Wed Oct 31 08:35:27 UTC 2007 root@hulk.superhero.nl:/usr/obj/usr/src/sys/GENERIC amd64 I have the following issue. da0 is garbled. This happened after rebuilding world on the 28th of October. Also.. the Disk is U320, should be 320MB instead of 160MB as the speed it is detected. In FreeBSD 6.2 it is detected as 320MB. It is RELENG_7 that detects it as 160MB. I have already changed the cable and tried a different disks. Before on 22nd of October: ahd0: port 0xe800-0xe8ff,0xe400-0xe4ff mem 0xdd 5fe000-0xdd5fffff irq 17 at device 10.0 on pci1 ahd0: [ITHREAD] aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI 33 or 66Mhz, 512 SCBs da0 at ahd0 bus 0 target 2 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit) da0: Command Queueing Enabled da0: 34732MB (71132960 512 byte sectors: 255H 63S/T 4427C) After 28th of October ahd0: port 0xe800-0xe8ff,0xe400-0xe4ff mem 0xdd 5fe000-0xdd5fffff irq 17 at device 10.0 on pci1 ahd0: [ITHREAD] aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI 33 or 66Mhz, 512 SCBs da0 at ahd0 bus 0 target 2 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit) da0: Command Queueing Enabled da0: 34732MB (71132960 512 byte sectors: 255H 63S/T 4427C) Please let me know if more information is required. Rgds, Patrick From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 15:45:45 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2AE3116A417 for ; Thu, 1 Nov 2007 15:45:45 +0000 (UTC) (envelope-from freebsd@superhero.nl) Received: from superman.superhero.nl (superhero.nl [82.95.198.17]) by mx1.freebsd.org (Postfix) with ESMTP id 744E013C48A for ; Thu, 1 Nov 2007 15:45:44 +0000 (UTC) (envelope-from freebsd@superhero.nl) Received: (qmail 19302 invoked by uid 80); 1 Nov 2007 15:45:00 -0000 Received: from 195.50.100.20 (SquirrelMail authenticated user gelsemap) by www.superhero.nl with HTTP; Thu, 1 Nov 2007 16:45:00 +0100 (CET) Message-ID: <63660.195.50.100.20.1193931900.squirrel@www.superhero.nl> In-Reply-To: <20071101154109.GA59070@eos.sc1.parodius.com> References: <1154.80.127.127.95.1193916692.squirrel@webmail.superhero.nl> <20071101154109.GA59070@eos.sc1.parodius.com> Date: Thu, 1 Nov 2007 16:45:00 +0100 (CET) From: "Gelsema, P \(Patrick\) - FreeBSD" To: "Jeremy Chadwick" User-Agent: SquirrelMail/1.4.8 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: freebsd-current@freebsd.org, "Gelsema, P \(Patrick\) - FreeBSD" Subject: Re: da0 detection garbled: da0: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 15:45:45 -0000 On Thu, November 1, 2007 16:41, Jeremy Chadwick wrote: > On Thu, Nov 01, 2007 at 12:31:32PM +0100, Gelsema, P (Patrick) - FreeBSD > wrote: >> da0: >> >> Please let me know if more information is required. > > This was discussed in October. See the thread here: > > http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078145.html > I did check the lists as I am subscribed. Must have missed this :( Anyways.. I still got the issue where the disks are detected as only 160.00 MB instead as 320.00MB as in RELENG_6_3. Cheers Patrick > -- > | Jeremy Chadwick jdc at parodius.com | > | Parodius Networking http://www.parodius.com/ | > | UNIX Systems Administrator Mountain View, CA, USA | > | Making life hard for others since 1977. PGP: 4BD6C0CB | > > From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 15:59:09 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D660416A41B for ; Thu, 1 Nov 2007 15:59:09 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id 7B4B213C4B0 for ; Thu, 1 Nov 2007 15:59:09 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8p) with ESMTP id 217264636-1834499 for multiple; Thu, 01 Nov 2007 10:24:08 -0500 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id lA1FNpff006973; Thu, 1 Nov 2007 11:23:54 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Mike Pritchard Date: Thu, 1 Nov 2007 11:23:35 -0400 User-Agent: KMail/1.9.6 References: <862892.31020.qm@web27810.mail.ukl.yahoo.com> <20071101013748.GA1116@mail.mppsystems.com> In-Reply-To: <20071101013748.GA1116@mail.mppsystems.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711011123.35870.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Thu, 01 Nov 2007 11:23:54 -0400 (EDT) X-Virus-Scanned: ClamAV 0.91.2/4658/Thu Nov 1 08:50:49 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-current@freebsd.org, Red Neck Subject: Re: Loader broken in Head? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 15:59:09 -0000 On Wednesday 31 October 2007 09:37:48 pm Mike Pritchard wrote: > > On Friday 26 October 2007 08:03:21 pm Red Neck wrote: > > Hi, > > > > Within the last day (26/10/07) I've built and installed the sources > > from CVS > > Head only to find the stage 3 boot loader, /boot/loader, not working. > > I'm > > using a Mac Pro with 3 internal hard drives. On one hard disk I have > > FreeBSD amd64 installed, occupying the entire disk (MBR). Using the > sources > > from Head, loader just freezes after displaying its initial messages > with a > > constantly spinning cursor. To access the system I have to revert to > using > > an older loader such as 6.2 release's. I have attached my make and > kernel > > config. > > I was seeing a similar problem. Booting from a floppy disk twice would > probably be faster than booting off the hard disk. I had just done > a makeworld, and updated the boot blocks on the disk (it previously had > a pretty old install on it). But the system would eventually boot, and > not hang up. I noticed that Red Necks boot loader build date was the > same as the version I was having problems with. > > Fortunately, I have a 2nd HD in the machine with a 7.0 install, > and installed the boot blocks from that HD to the one I was having > problems with, and copied over /boot/loader from that HD. > No more problems. System boots as fast as ever. > > So yes, I think there is something wrong with the current loader. > > With the slow boot, once the system is up and running, the disks > are running at normal speeds (checked with iozone & bonnie). Did you get the latest loader? For example, do you have this fix which might result in significantly slower disk I/O since w/o it every disk I/O is attempted 3 times with 2 drive resets in between: jhb 2007-10-25 16:53:35 UTC FreeBSD src repository Modified files: sys/boot/i386/libi386 biosdisk.c Log: Break out of the I/O retry loop as soon as an I/O operation succeeds rather than always retrying operations three times. Submitted by: nyan Revision Changes Path 1.53 +2 -0 src/sys/boot/i386/libi386/biosdisk.c -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 15:59:24 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 729AD16A419 for ; Thu, 1 Nov 2007 15:59:24 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 606E513C48E for ; Thu, 1 Nov 2007 15:59:24 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 897A81CC081; Thu, 1 Nov 2007 08:41:09 -0700 (PDT) Date: Thu, 1 Nov 2007 08:41:09 -0700 From: Jeremy Chadwick To: "Gelsema, P (Patrick) - FreeBSD" Message-ID: <20071101154109.GA59070@eos.sc1.parodius.com> References: <1154.80.127.127.95.1193916692.squirrel@webmail.superhero.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1154.80.127.127.95.1193916692.squirrel@webmail.superhero.nl> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org Subject: Re: da0 detection garbled: da0: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 15:59:24 -0000 On Thu, Nov 01, 2007 at 12:31:32PM +0100, Gelsema, P (Patrick) - FreeBSD wrote: > da0: > > Please let me know if more information is required. This was discussed in October. See the thread here: http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078145.html -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 17:01:52 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0966A16A418 for ; Thu, 1 Nov 2007 17:01:52 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id AD85313C48A for ; Thu, 1 Nov 2007 17:01:50 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id lA1H172s013379; Thu, 1 Nov 2007 11:01:07 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <472A063B.1030201@samsco.org> Date: Thu, 01 Nov 2007 11:00:43 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.6) Gecko/20070802 SeaMonkey/1.1.4 MIME-Version: 1.0 To: "Gelsema, P \(Patrick\) - FreeBSD" References: <1154.80.127.127.95.1193916692.squirrel@webmail.superhero.nl> <20071101154109.GA59070@eos.sc1.parodius.com> <63660.195.50.100.20.1193931900.squirrel@www.superhero.nl> In-Reply-To: <63660.195.50.100.20.1193931900.squirrel@www.superhero.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Thu, 01 Nov 2007 11:01:07 -0600 (MDT) X-Spam-Status: No, score=-1.4 required=5.5 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: Jeremy Chadwick , freebsd-current@freebsd.org Subject: Re: da0 detection garbled: da0: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 17:01:52 -0000 Gelsema, P (Patrick) - FreeBSD wrote: > On Thu, November 1, 2007 16:41, Jeremy Chadwick wrote: >> On Thu, Nov 01, 2007 at 12:31:32PM +0100, Gelsema, P (Patrick) - FreeBSD >> wrote: >>> da0: >>> >>> Please let me know if more information is required. >> This was discussed in October. See the thread here: >> >> http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078145.html >> > > I did check the lists as I am subscribed. Must have missed this :( > > Anyways.. I still got the issue where the disks are detected as only > 160.00 MB instead as 320.00MB as in RELENG_6_3. > The speed issue is a big one that I haven't had time to address, and I don't know if I'll be able to address it before 7.0 is released since it involves some pretty significant and delicate work. In the mean time, try running the following after the system is up: camcontrol negotiate da0 -a -R 160 Scott From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 17:06:01 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A04416A418 for ; Thu, 1 Nov 2007 17:06:01 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id 8380713C4A6 for ; Thu, 1 Nov 2007 17:06:00 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from anb.matik.com.br (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.14.1/8.13.1) with ESMTP id lA1FvkGX059047 for ; Thu, 1 Nov 2007 13:57:46 -0200 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR Organization: Infomatik To: freebsd-current@freebsd.org Date: Thu, 1 Nov 2007 13:57:29 -0200 User-Agent: KMail/1.9.7 References: <1154.80.127.127.95.1193916692.squirrel@webmail.superhero.nl> <20071101154109.GA59070@eos.sc1.parodius.com> <63660.195.50.100.20.1193931900.squirrel@www.superhero.nl> In-Reply-To: <63660.195.50.100.20.1193931900.squirrel@www.superhero.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200711011357.29420.joao@matik.com.br> X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on msrv.matik.com.br X-Virus-Status: Clean Subject: Re: da0 detection garbled: da0: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 17:06:01 -0000 On Thursday 01 November 2007 13:45:00 Gelsema, P (Patrick) - FreeBSD wrote: > On Thu, November 1, 2007 16:41, Jeremy Chadwick wrote: > > On Thu, Nov 01, 2007 at 12:31:32PM +0100, Gelsema, P (Patrick) - FreeBSD > > > > wrote: > >> da0: > >> > >> Please let me know if more information is required. > > > > This was discussed in October. See the thread here: > > > > http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078145.= ht > >ml > > I did check the lists as I am subscribed. Must have missed this :( > > Anyways.. I still got the issue where the disks are detected as only > 160.00 MB instead as 320.00MB as in RELENG_6_3. > are you sure that your scsi cable (and/or terminator) is 320 capable? =2D-=20 Jo=E3o A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 17:11:27 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E9FB16A469 for ; Thu, 1 Nov 2007 17:11:27 +0000 (UTC) (envelope-from ianf@clue.co.za) Received: from munchkin.clue.co.za (munchkin.clue.co.za [66.219.59.160]) by mx1.freebsd.org (Postfix) with ESMTP id 6504113C4BB for ; Thu, 1 Nov 2007 17:11:27 +0000 (UTC) (envelope-from ianf@clue.co.za) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=20070313; d=clue.co.za; h=Received:Received:Received:To:Subject:From:X-Attribution:Date:Message-Id; b=pr9ZTMOeRkTwjtfBhMmQjYmgHMoMSte244akpoY4QyS4SKPwG6RyTcrRVA+u96Om62pnq8UjWPnb3os6KLQiYEmbI92bzVJ0NNq96PekHX0i/Z3CnyoNBx3561ThdQtoZ8Ej0Gjl2GbuzpUdtEMjA6uBiwjA5TSR6mIytp+5EDpsLuVx2TAl/ttpeMGKERpEyPjUq9okGtOo2EIQF/lLzcBoeGg+j9+DQSXLGGckDBbi6Yti3onnux7f1Yk/+3yv; Received: from uucp by munchkin.clue.co.za with local-rmail (Exim 4.67) (envelope-from ) id 1InaGM-0001z1-F0 for current@freebsd.org; Thu, 01 Nov 2007 13:39:10 +0000 Received: from ianf.clue.co.za ([10.0.0.6] helo=clue.co.za) by urchin.clue.co.za with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.66) (envelope-from ) id 1InaFQ-0002vT-Lq for current@freebsd.org; Thu, 01 Nov 2007 13:38:12 +0000 Received: from localhost ([127.0.0.1] helo=clue.co.za) by clue.co.za with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1InaFP-0002HC-Sx for current@freebsd.org; Thu, 01 Nov 2007 15:38:11 +0200 To: current@freebsd.org From: Ian FREISLICH X-Attribution: BOFH Date: Thu, 01 Nov 2007 15:38:11 +0200 Message-Id: Cc: Subject: setitimer() odd timing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 17:11:27 -0000 Hi I've got a issue that I noticed recently. When I set an alarm() or use setitimer() the signal delivery is delayed somewhat. I'm not sure if it's that the signal is delayed or if it's just that the timer runs slowly. I am using ITIMER_REAL. It's pretty linear over 1 to 60 (asked for) seconds translating them into 3.7 real seconds: [apple] ~ # time sleep 5 real 0m18.542s user 0m0.000s sys 0m0.001s [apple] ~ # time sleep 10 real 0m37.081s user 0m0.000s sys 0m0.001s [apple] ~ # time sleep 60 real 3m42.468s user 0m0.000s sys 0m0.001s The hardware in question is an Apple MacBook Pro. FWIW, I don't notice this on other i386 based hardware that I have. It affects things like ping, cron, atrun and xclock but not gettimeofday(). I'm not sure where to start looking. If someone points me at what needs instrumenting, I'll see if I can narrow the problem space. Ian -- Ian Freislich From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 18:15:23 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9058F16A418; Thu, 1 Nov 2007 18:15:23 +0000 (UTC) (envelope-from syleishere@hotmail.com) Received: from bay0-omc3-s8.bay0.hotmail.com (bay0-omc3-s8.bay0.hotmail.com [65.54.246.208]) by mx1.freebsd.org (Postfix) with ESMTP id 72A5B13C4A5; Thu, 1 Nov 2007 18:15:23 +0000 (UTC) (envelope-from syleishere@hotmail.com) Received: from BAY102-W2 ([64.4.61.102]) by bay0-omc3-s8.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 1 Nov 2007 11:12:14 -0700 Message-ID: X-Originating-IP: [24.79.240.75] From: syle ishere To: pluknet , John Baldwin Date: Thu, 1 Nov 2007 13:12:14 -0500 Importance: Normal In-Reply-To: References: <200710251511.13161.jhb@freebsd.org> MIME-Version: 1.0 X-OriginalArrivalTime: 01 Nov 2007 18:12:14.0226 (UTC) FILETIME=[BAB54F20:01C81CB2] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: RE: kernel panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 18:15:23 -0000 Yep, I commented out that as well in make.conf and machine boots just fine = after taking out my CFLAGS and CPUTYPE lines. I had -funroll-loops in there as well. =20 Dan. =20 =20 > Date: Thu, 1 Nov 2007 15:35:50 +0300> From: pluknet@gmail.com> To: jhb@fr= eebsd.org> Subject: Re: kernel panic> CC: freebsd-current@freebsd.org; syle= ishere@hotmail.com> > On 25/10/2007, John Baldwin wrote:>= > On Thursday 25 October 2007 01:10:33 pm syle ishere wrote:> > >> > > I t= ried testing this. Added> > > LOADER_FIREWIRE_SUPPORT=3Dyes in /etc/make.co= nf> > > (cd /sys/boot/i386 && make clean && make && make install)shutdown -= r now> > > All was great it the loader worked!> > >> > > To test this wasn'= t my imagination:> > > I took that line out of make.conf> > > (cd /sys/boot= /i386 && make clean && make && make install)shutdown -r now> > >> > > And g= ot same problem system not booting.> > >> > > Good catch pluknet, hopefully= we can get this code compiled into the loader> > as a mandatory fix> > > f= or now.> >> > That seems odd. I would make sure you really have a clean bui= ld, and I would> > build from /sys/boot, not /sys/boot/i386.> >> > --> > Jo= hn Baldwin> >> > Yes. I've just checked that loader brokeness is influenced= by> -funroll-loops in make.conf> > wbr,> pluknet _________________________________________________________________ R U Ready for Windows Live Messenger Beta 8.5? Try it today! http://entertainment.sympatico.msn.ca/WindowsLiveMessenger= From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 18:55:38 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87A0B16A41B for ; Thu, 1 Nov 2007 18:55:38 +0000 (UTC) (envelope-from thierry@herbelot.com) Received: from postfix2-g20.free.fr (postfix2-g20.free.fr [212.27.60.43]) by mx1.freebsd.org (Postfix) with ESMTP id 1AA6C13C481 for ; Thu, 1 Nov 2007 18:55:38 +0000 (UTC) (envelope-from thierry@herbelot.com) Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30]) by postfix2-g20.free.fr (Postfix) with ESMTP id B8E321D8E970 for ; Thu, 1 Nov 2007 13:09:29 +0100 (CET) Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1]) by smtp4-g19.free.fr (Postfix) with ESMTP id E7F0D3EA0E5 for ; Thu, 1 Nov 2007 15:09:56 +0100 (CET) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp4-g19.free.fr (Postfix) with ESMTP id B3CF63EA0D9 for ; Thu, 1 Nov 2007 15:09:56 +0100 (CET) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.14.0/8.14.0) with ESMTP id lA1E9qlm014049 for ; Thu, 1 Nov 2007 15:09:53 +0100 (CET) From: Thierry Herbelot To: freebsd-current@freebsd.org Date: Thu, 1 Nov 2007 15:09:45 +0100 User-Agent: KMail/1.9.7 X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711011509.46094.thierry@herbelot.com> Subject: regression with gmirror, Promise SATA and 7.0 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 18:55:38 -0000 Hello, I have tried to switch my home server from a 6.3-PRERELEASE to the latest 7.0-BETA1.5-i386-disc1.iso. I have loopback-mounted the iso and unarchived the base and kernel to a new gmirrored partition hosted on two "Seagate ST3250823AS" SATA disks connected via a "Promise PDC40518 SATA150" controller. after rebooting to the new "current" gmirror partition, any disk access gives errors such as : ad6: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=58616578 ad6: FAILURE - device detached subdisk6: detached ad6: detached GEOM_MIRROR: Cannot write metadata on ad6s3 (device=gm0s3, error=6). GEOM_MIRROR: Cannot update metadata on disk ad6s3 (error=6). GEOM_MIRROR: Device gm0s4: provider ad6s4 disconnected. GEOM_MIRROR: Device gm0s2: provider ad6s2 disconnected. GEOM_MIRROR: Device gm0s1: provider ad6s1 disconnected. ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly ad10: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly ad10: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly ad10: WARNING - SET_MULTI taskqueue timeout - completing request directly ad10: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=62894473 GEOM_MIRROR: Cannot update metadata on disk ad6s3 (error=6). GEOM_MIRROR: Device gm0s3: provider ad6s3 disconnected. g_vfs_done():mirror/gm0s3f[READ(offset=5429510144, length=65536)]error = 6 vnode_pager_getpages: I/O read error The same ad6 and ad10 disks are presently used under 6.x without any (visbile) errors (and have been for more than one year). Thus, it seems that the combination of this Promise controller and the SATA disks has issues (there was a thread about Promise controllers and ZFS, but with no clear conclusion). TfH PS : I was also burnt by the forced conversion of gmirror metadata from v3 to v4, which makes it tricky to backtrack to 6.x, once a 7.x kernel + gmirror has been booted once. From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 19:08:03 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1B3E216A468 for ; Thu, 1 Nov 2007 19:08:03 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by mx1.freebsd.org (Postfix) with ESMTP id 70C1B13C4A7 for ; Thu, 1 Nov 2007 19:08:01 +0000 (UTC) (envelope-from max@love2party.net) Received: from amd64.laiers.local (dslb-088-066-041-091.pools.arcor-ip.net [88.66.41.91]) by mrelayeu.kundenserver.de (node=mrelayeu2) with ESMTP (Nemesis) id 0MKwtQ-1Inexn30Fj-0002Ay; Thu, 01 Nov 2007 19:40:23 +0100 From: Max Laier Organization: FreeBSD To: freebsd-current@freebsd.org Date: Thu, 1 Nov 2007 19:40:12 +0100 User-Agent: KMail/1.9.7 X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<%}*_BD U_or=\mOZf764&nYj=JYbR1PW0ud>|!~, , CPC.1-D$FG@0h3#'5"k{V]a~. X-Provags-ID: V01U2FsdGVkX18wZBGFbCFWNTVII0st08lEzTYSMwjyRG9pQf9 0XZUeFh9PRL5GQHk3n9rWnat1ae0rzMjOHkW2zFLR5GN/2fslN eY25K0dodcQVeAudQzbJx4E5jMYnf/dCfpR8Kh2ymo= X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-acpi@freebsd.org Subject: apic vs. ASUS P5N-E (nforce 650) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 19:08:03 -0000 --nextPart3828379.rAXiEC845h Content-Type: multipart/mixed; boundary="Boundary-01=_N2hKHZAYVDEsOTi" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-01=_N2hKHZAYVDEsOTi Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, I'm having big trouble with this board. It works fine once I set=20 hint.apic.0.disabled=3D1, but unfortunately without using the second core. = =20 When the apic is used, the nforce IDE/ATA controller and the nforce NIC=20 are not working at all. No disks or CDROMs are recognized, the NIC=20 doesn't send or receive any packets. Attached are verbose dmesgs (captured via serial): boot_v.apic - ACPI enabled APIC enabled boot_v.noacpi - ACPI disabled APIC enabled boot_v.noapic - ACPI enabled APIC disabled (this works) =46WIW, linux (knoppix CD) does boot and seems to use the apic (dmesg=20 attached). I suspect that there is something wrong with the ACPI interrupt overrides. = =20 IRQ9 is listed as (level, high) and IRQ0->2 seems only to make sense if=20 the HEPT is being used, but neither ACPI_Q_MADT_IRQ0 nor forcing (level,=20 low) for IRQ9 in madt.c doesn't seem to do the trick. I've tried a couple of things, but didn't get anywhere. If anyone has an=20 idea I'd be eager to try it. Thanks. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --Boundary-01=_N2hKHZAYVDEsOTi Content-Type: text/plain; charset="us-ascii"; name="mptable" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="mptable" =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D MPTable =2D------------------------------------------------------------------------= =2D----- MP Floating Pointer Structure: location: BIOS physical address: 0x000f5c80 signature: '_MP_' length: 16 bytes version: 1.4 checksum: 0x7d mode: Virtual Wire =2D------------------------------------------------------------------------= =2D----- MP Config Table Header: physical address: 0x000f1400 signature: 'PCMP' base table length: 300 version: 1.4 checksum: 0xcd OEM ID: 'OEM00000' Product ID: 'PROD00000000' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 29 local APIC address: 0xfee00000 extended table length: 0 extended table checksum: 0 =2D------------------------------------------------------------------------= =2D----- MP Config Base Table Entries: =2D- Processors: APIC ID Version State Family Model Step Flags 0 0x11 BSP, usable 6 15 11 0xfbff 1 0x11 AP, usable 6 15 11 0xfbff =2D- Bus: Bus ID Type 0 PCI =20 1 PCI =20 2 PCI =20 3 PCI =20 4 ISA =20 =2D- I/O APICs: APIC ID Version State Address 4 0x11 usable 0xfec00000 =2D- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# INT active-lo level 0 20:A 4 5 INT active-lo level 0 16:B 4 11 INT active-lo level 1 0:A 4 10 INT active-lo level 2 0:A 4 11 INT active-lo level 0 14:A 4 10 INT active-lo level 0 15:A 4 11 ExtINT conforms conforms 4 0 4 0 INT conforms conforms 4 1 4 1 INT conforms conforms 4 0 4 2 INT conforms conforms 4 3 4 3 INT conforms conforms 4 4 4 4 INT conforms conforms 4 6 4 6 INT conforms conforms 4 7 4 7 INT active-hi edge 4 8 4 8 INT conforms conforms 4 9 4 9 INT conforms conforms 4 12 4 12 INT conforms conforms 4 13 4 13 INT conforms conforms 4 14 4 14 INT conforms conforms 4 15 4 15 =2D- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 0 0:A 255 0 NMI conforms conforms 0 0:A 255 1 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D --Boundary-01=_N2hKHZAYVDEsOTi Content-Type: text/plain; charset="us-ascii"; name="dmesg.linux" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="dmesg.linux" Linux version 2.6.19 (root@Knoppix) (gcc version 4.1.2 20061028 (prerelease= ) (Debian 4.1.1-19)) #7 SMP PREEMPT Sun Dec 17 22:01:07 CET 2006 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009f000 (usable) BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000007fef0000 (usable) BIOS-e820: 000000007fef0000 - 000000007fef3000 (ACPI NVS) BIOS-e820: 000000007fef3000 - 000000007ff00000 (ACPI data) BIOS-e820: 00000000f0000000 - 00000000f2000000 (reserved) BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved) 1150MB HIGHMEM available. 896MB LOWMEM available. found SMP MP-table at 000f5c80 Entering add_active_range(0, 0, 524016) 0 entries of 256 used Zone PFN ranges: DMA 0 -> 4096 Normal 4096 -> 229376 HighMem 229376 -> 524016 early_node_map[1] active PFN ranges 0: 0 -> 524016 On node 0 totalpages: 524016 DMA zone: 32 pages used for memmap DMA zone: 0 pages reserved DMA zone: 4064 pages, LIFO batch:0 Normal zone: 1760 pages used for memmap Normal zone: 223520 pages, LIFO batch:31 HighMem zone: 2301 pages used for memmap HighMem zone: 292339 pages, LIFO batch:31 DMI 2.4 present. ACPI: RSDP (v002 Nvidia ) @ 0x000f77c0 ACPI: XSDT (v001 Nvidia ASUSACPI 0x42302e31 AWRD 0x00000000) @ 0x7fef30c0 ACPI: FADT (v003 Nvidia ASUSACPI 0x42302e31 AWRD 0x00000000) @ 0x7fef9740 ACPI: HPET (v001 Nvidia ASUSACPI 0x42302e31 AWRD 0x00000098) @ 0x7fef9980 ACPI: MCFG (v001 Nvidia ASUSACPI 0x42302e31 AWRD 0x00000000) @ 0x7fef9a00 ACPI: MADT (v001 Nvidia ASUSACPI 0x42302e31 AWRD 0x00000000) @ 0x7fef9880 ACPI: DSDT (v001 NVIDIA ASUSACPI 0x00001000 MSFT 0x03000000) @ 0x00000000 ACPI: PM-Timer IO Port: 0x1008 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 6:15 APIC version 20 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) Processor #1 6:15 APIC version 20 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] disabled) ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] disabled) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1]) ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 4, version 17, address 0xfec00000, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge) ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. ACPI: IRQ14 used by override. ACPI: IRQ15 used by override. Enabling APIC mode: Flat. Using 1 I/O APICs ACPI: HPET id: 0x10de8201 base: 0xfeff0000 Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 80000000 (gap: 7ff00000:70100000) Detected 2333.461 MHz processor. Built 1 zonelists. Total pages: 519923 Kernel command line: ramdisk_size=3D100000 init=3D/etc/init lang=3Dus apm= =3Dpower-off vga=3D791 initrd=3Dminirt.gz nomce loglevel=3D0 quiet BOOT_IMA= GE=3Dknoppix BOOT_IMAGE=3Dlinux apic=3Dverbose mapped APIC to ffffd000 (fee00000) mapped IOAPIC to ffffc000 (fec00000) Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 4096 (order: 12, 16384 bytes) spurious 8259A interrupt: IRQ7. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Memory: 2071932k/2096064k available (2747k kernel code, 22860k reserved, 95= 8k data, 336k init, 1178560k highmem) virtual kernel memory layout: fixmap : 0xffe16000 - 0xfffff000 (1956 kB) pkmap : 0xff800000 - 0xffc00000 (4096 kB) vmalloc : 0xf8800000 - 0xff7fe000 ( 111 MB) lowmem : 0xc0000000 - 0xf8000000 ( 896 MB) .init : 0xc04a6000 - 0xc04fa000 ( 336 kB) .data : 0xc03aef9c - 0xc049e7b4 ( 958 kB) .text : 0xc0100000 - 0xc03aef9c (2747 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Using HPET for base-timer Calibrating delay using timer specific routine.. 4670.54 BogoMIPS (lpj=3D93= 41081) Security Framework v1.0.0 initialized SELinux: Disabled at boot. Capability LSM initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000= e3fd 00000000 00000001 monitor/mwait feature present. using mwait in idle threads. CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 4096K CPU: Physical Processor ID: 0 CPU: Processor Core ID: 0 CPU: After all inits, caps: bfebfbff 20100000 00000000 00000940 0000e3fd 00= 000000 00000001 Compat vDSO mapped to ffffe000. Checking 'hlt' instruction... OK. Checking for popad bug... OK. SMP alternatives: switching to UP code ACPI: Core revision 20060707 CPU0: Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz stepping 0b enabled ExtINT on CPU#0 SMP alternatives: switching to SMP code Booting processor 1/1 eip 3000 Initializing CPU#1 masked ExtINT on CPU#1 Calibrating delay using timer specific routine.. 4666.73 BogoMIPS (lpj=3D93= 33460) CPU: After generic identify, caps: bfebfbff 20100000 00000000 00000000 0000= e3fd 00000000 00000001 monitor/mwait feature present. CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 4096K CPU: Physical Processor ID: 0 CPU: Processor Core ID: 1 CPU: After all inits, caps: bfebfbff 20100000 00000000 00000940 0000e3fd 00= 000000 00000001 CPU1: Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz stepping 0b Total of 2 processors activated (9337.27 BogoMIPS). ENABLING IO-APIC IRQs init IO_APIC IRQs IO-APIC (apicid-pin) 4-0, 4-16, 4-17, 4-18, 4-19, 4-20, 4-21, 4-22, 4-23 n= ot connected. =2E.TIMER: vector=3D0x31 apic1=3D0 pin1=3D2 apic2=3D-1 pin2=3D-1 Using local APIC timer interrupts. calibrating APIC timer ... =2E.... CPU clock speed is 2333.1335 MHz. =2E.... host bus clock speed is 333.1333 MHz. checking TSC synchronization across 2 CPUs: passed. Brought up 2 CPUs migration_cost=3D65 checking if image is initramfs...it isn't (no cpio magic); looks like an in= itrd =46reeing initrd memory: 1188k freed NET: Registered protocol family 16 EISA bus registered ACPI: bus type pci registered PCI: Using MMCONFIG Setting up standard PCI resources ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) PCI: Probing PCI hardware (bus 00) Boot video device is 0000:01:00.0 PCI: Transparent bridge - 0000:00:10.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT] ACPI: PCI Interrupt Link [LNK1] (IRQs 5 7 9 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNK2] (IRQs 5 7 9 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNK3] (IRQs 5 7 9 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNK4] (IRQs 5 7 9 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNK5] (IRQs 5 7 9 *10 11 14 15) ACPI: PCI Interrupt Link [LNK6] (IRQs 5 7 9 10 *11 14 15) ACPI: PCI Interrupt Link [LNK7] (IRQs 5 7 9 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNK8] (IRQs 5 7 9 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LUBA] (IRQs 5 7 9 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LUBB] (IRQs 5 7 9 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LMAC] (IRQs *5 7 9 10 11 14 15) ACPI: PCI Interrupt Link [LACI] (IRQs 5 7 9 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LAZA] (IRQs 5 7 9 10 *11 14 15) ACPI: PCI Interrupt Link [LPMU] (IRQs 5 7 9 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LMCI] (IRQs 5 7 9 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LSMB] (IRQs 5 7 9 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LUB2] (IRQs 5 7 9 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LIDE] (IRQs 5 7 9 10 11 14 15) *0, disabled. ACPI: PCI Interrupt Link [LSID] (IRQs 5 7 9 *10 11 14 15) ACPI: PCI Interrupt Link [LFID] (IRQs 5 7 9 10 *11 14 15) ACPI: PCI Interrupt Link [APC1] (IRQs 16) *0, disabled. ACPI: PCI Interrupt Link [APC2] (IRQs 17) *0, disabled. ACPI: PCI Interrupt Link [APC3] (IRQs 18) *0, disabled. ACPI: PCI Interrupt Link [APC4] (IRQs 19) *0, disabled. ACPI: PCI Interrupt Link [APC5] (IRQs 16) *0, disabled. ACPI: PCI Interrupt Link [APC6] (IRQs 16) *0, disabled. ACPI: PCI Interrupt Link [APC7] (IRQs 16) *0, disabled. ACPI: PCI Interrupt Link [APC8] (IRQs 16) *0, disabled. ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [APMU] (IRQs 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [AAZA] (IRQs 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [APCS] (IRQs 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [APSI] (IRQs 20 21 22 23) *0, disabled. ACPI: PCI Interrupt Link [APSJ] (IRQs 20 21 22 23) *0, disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 14 devices PnPBIOS: Disabled by ACPI PNP SCSI subsystem initialized libata version 2.00 loaded. PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try "pci=3Drouteirq". If it helps, post a r= eport number of MP IRQ sources: 15. number of IO-APIC #4 registers: 24. testing the IO APIC....................... IO APIC #4...... =2E... register #00: 00000000 =2E...... : physical APIC id: 00 =2E...... : Delivery Type: 0 =2E...... : LTS : 0 =2E... register #01: 00170011 =2E...... : max redirection entries: 0017 =2E...... : PRQ implemented: 0 =2E...... : IO APIC version: 0011 =2E... register #02: 00000000 =2E...... : arbitration: 00 =2E... IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: =20 00 000 00 1 0 0 0 0 0 0 00 01 003 03 1 0 0 0 0 1 1 39 02 003 03 0 0 0 0 0 1 1 31 03 003 03 0 0 0 0 0 1 1 41 04 003 03 1 0 0 0 0 1 1 49 05 003 03 1 0 0 0 0 1 1 51 06 003 03 0 0 0 0 0 1 1 59 07 003 03 1 0 0 0 0 1 1 61 08 003 03 1 0 0 0 0 1 1 69 09 003 03 0 1 0 0 0 1 1 71 0a 003 03 1 0 0 0 0 1 1 79 0b 003 03 1 0 0 0 0 1 1 81 0c 003 03 1 0 0 0 0 1 1 89 0d 003 03 1 0 0 0 0 1 1 91 0e 003 03 0 0 0 0 0 1 1 99 0f 003 03 0 0 0 0 0 1 1 A1 10 000 00 1 0 0 0 0 0 0 00 11 000 00 1 0 0 0 0 0 0 00 12 000 00 1 0 0 0 0 0 0 00 13 000 00 1 0 0 0 0 0 0 00 14 000 00 1 0 0 0 0 0 0 00 15 000 00 1 0 0 0 0 0 0 00 16 000 00 1 0 0 0 0 0 0 00 17 000 00 1 0 0 0 0 0 0 00 IRQ to pin mappings: IRQ0 -> 0:2 IRQ1 -> 0:1 IRQ3 -> 0:3 IRQ4 -> 0:4 IRQ5 -> 0:5 IRQ6 -> 0:6 IRQ7 -> 0:7 IRQ8 -> 0:8 IRQ9 -> 0:9 IRQ10 -> 0:10 IRQ11 -> 0:11 IRQ12 -> 0:12 IRQ13 -> 0:13 IRQ14 -> 0:14 IRQ15 -> 0:15 =2E................................... done. NetLabel: Initializing NetLabel: domain hash size =3D 128 NetLabel: protocols =3D UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default pnp: 00:01: ioport range 0x1000-0x107f could not be reserved pnp: 00:01: ioport range 0x1080-0x10ff has been reserved pnp: 00:01: ioport range 0x1400-0x147f has been reserved pnp: 00:01: ioport range 0x1480-0x14ff could not be reserved pnp: 00:01: ioport range 0x1800-0x187f has been reserved pnp: 00:01: ioport range 0x1880-0x18ff has been reserved PCI: Bridge: 0000:00:03.0 IO window: e000-efff MEM window: fa000000-fcffffff PREFETCH window: e0000000-efffffff PCI: Bridge: 0000:00:07.0 IO window: c000-cfff MEM window: fdd00000-fddfffff PREFETCH window: fdc00000-fdcfffff PCI: Bridge: 0000:00:10.0 IO window: d000-dfff MEM window: fdf00000-fdffffff PREFETCH window: fde00000-fdefffff PCI: Setting latency timer of device 0000:00:03.0 to 64 PCI: Setting latency timer of device 0000:00:07.0 to 64 PCI: Setting latency timer of device 0000:00:10.0 to 64 NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 8, 1572864 bytes) TCP bind hash table entries: 65536 (order: 7, 786432 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered audit: initializing netlink socket (disabled) audit(1193849666.040:1): initialized highmem bounce pool size: 64 pages Total HugeTLB memory allocated, 0 VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) fuse init (API version 7.8) fuse distribution version: 2.6.1 io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered (default) io scheduler cfq registered PCI: Setting latency timer of device 0000:00:03.0 to 64 pcie_portdrv_probe->Dev[03b7:10de] has invalid IRQ. Check vendor BIOS assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:03.0:pcie00] Allocate Port Service[0000:00:03.0:pcie03] PCI: Setting latency timer of device 0000:00:07.0 to 64 pcie_portdrv_probe->Dev[03bb:10de] has invalid IRQ. Check vendor BIOS assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:07.0:pcie00] Allocate Port Service[0000:00:07.0:pcie03] vesafb: framebuffer at 0xe0000000, mapped to 0xf8880000, using 3072k, total= 262144k vesafb: mode is 1024x768x16, linelength=3D2048, pages=3D1 vesafb: protected mode interface info at c000:c340 vesafb: pmi: set display start =3D c00cc376, set palette =3D c00cc3e0 vesafb: pmi: ports =3D 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce = 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da=20 vesafb: scrolling: redraw vesafb: Truecolor: size=3D0:5:6:5, shift=3D0:11:5:0 Console: switching to colour frame buffer device 128x48 fb0: VESA VGA frame buffer device isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found Real Time Clock Driver v1.12ac floppy0: no floppy controllers found RAMDISK driver initialized: 16 RAM disks of 100000K size 1024 blocksize Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=3D= xx NFORCE-MCP51: IDE controller at PCI slot 0000:00:0d.0 NFORCE-MCP51: chipset revision 161 NFORCE-MCP51: not 100% native mode: will probe irqs later NFORCE-MCP51: 0000:00:0d.0 (rev a1) UDMA133 controller ide0: BM-DMA at 0xfd00-0xfd07, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xfd08-0xfd0f, BIOS settings: hdc:DMA, hdd:DMA Probing IDE interface ide0... hda: IBM-DTLA-305040, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: HL-DT-ST DVDRAM GSA-4120B, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 hda: max request size: 128KiB hda: 80418240 sectors (41174 MB) w/380KiB Cache, CHS=3D65535/16/63 hda: cache flushes not supported hda: hda1 hda1: hdc: ATAPI 40X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache Uniform CD-ROM driver Revision: 3.20 Loading iSCSI transport class v2.0-724.<7>ahci 0000:02:00.0: version 2.0 ACPI: PCI Interrupt Link [APC6] enabled at IRQ 16 ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [APC6] -> GSI 16 (level, low) -= > IRQ 16 PCI: Setting latency timer of device 0000:02:00.0 to 64 ahci 0000:02:00.0: AHCI 0001.0000 32 slots 1 ports 3 Gbps 0x1 impl SATA mode ahci 0000:02:00.0: flags: 64bit ncq pm led clo pmp pio slum part=20 ata1: SATA max UDMA/133 cmd 0xF881C100 ctl 0x0 bmdma 0x0 irq 16 scsi0 : ahci ata1: SATA link down (SStatus 0 SControl 300) sata_nv 0000:00:0e.0: version 2.0 ACPI: PCI Interrupt Link [APSI] enabled at IRQ 23 ACPI: PCI Interrupt 0000:00:0e.0[A] -> Link [APSI] -> GSI 23 (level, low) -= > IRQ 17 PCI: Setting latency timer of device 0000:00:0e.0 to 64 ata2: SATA max UDMA/133 cmd 0x9F0 ctl 0xBF2 bmdma 0xF800 irq 17 ata3: SATA max UDMA/133 cmd 0x970 ctl 0xB72 bmdma 0xF808 irq 17 scsi1 : sata_nv ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300) ata2.00: ATA-7, max UDMA/133, 293046768 sectors: LBA48 NCQ (depth 0/32) ata2.00: ata2: dev 0 multi count 1 ata2.00: configured for UDMA/133 scsi2 : sata_nv ata3: SATA link down (SStatus 0 SControl 300) ATA: abnormal status 0x7F on port 0x977 scsi 1:0:0:0: Direct-Access ATA WDC WD1500AHFD-0 21.0 PQ: 0 ANSI: 5 SCSI device sda: 293046768 512-byte hdwr sectors (150040 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: drive cache: write back SCSI device sda: 293046768 512-byte hdwr sectors (150040 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: drive cache: write back sda: sda1 sd 1:0:0:0: Attached scsi disk sda ACPI: PCI Interrupt Link [APSJ] enabled at IRQ 22 ACPI: PCI Interrupt 0000:00:0f.0[A] -> Link [APSJ] -> GSI 22 (level, low) -= > IRQ 18 PCI: Setting latency timer of device 0000:00:0f.0 to 64 ata4: SATA max UDMA/133 cmd 0x9E0 ctl 0xBE2 bmdma 0xF300 irq 18 ata5: SATA max UDMA/133 cmd 0x960 ctl 0xB62 bmdma 0xF308 irq 18 scsi3 : sata_nv ata4: SATA link down (SStatus 0 SControl 300) ATA: abnormal status 0x7F on port 0x9E7 scsi4 : sata_nv ata5: SATA link down (SStatus 0 SControl 300) ATA: abnormal status 0x7F on port 0x967 PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12 serio: i8042 KBD port at 0x60,0x64 irq 1 serio: i8042 AUX port at 0x60,0x64 irq 12 mice: PS/2 mouse device common for all mice EISA: Probing bus 0 at eisa.0 Cannot allocate resource for EISA slot 1 EISA: Detected 0 cards. Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 15 Using IPI No-Shortcut mode ACPI: (supports S0 S1 S3 S4 S5) Time: tsc clocksource has been installed. input: AT Translated Set 2 keyboard as /class/input/input0 input: PS2++ Logitech Wheel Mouse as /class/input/input1 RAMDISK: Compressed image found at block 0 EXT2-fs warning: checktime reached, running e2fsck is recommended VFS: Mounted root (ext2 filesystem). =46ailed initialization of WD-7000 SCSI card! usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb ACPI: PCI Interrupt Link [APCL] enabled at IRQ 21 ACPI: PCI Interrupt 0000:00:0b.1[B] -> Link [APCL] -> GSI 21 (level, low) -= > IRQ 19 PCI: Setting latency timer of device 0000:00:0b.1 to 64 ehci_hcd 0000:00:0b.1: EHCI Host Controller ehci_hcd 0000:00:0b.1: new USB bus registered, assigned bus number 1 ehci_hcd 0000:00:0b.1: debug port 1 PCI: cache line size of 32 is not supported by device 0000:00:0b.1 ehci_hcd 0000:00:0b.1: irq 19, io mem 0xfe02e000 ehci_hcd 0000:00:0b.1: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 8 ports detected USB Universal Host Controller Interface driver v3.0 ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI) ACPI: PCI Interrupt Link [APCF] enabled at IRQ 20 ACPI: PCI Interrupt 0000:00:0b.0[A] -> Link [APCF] -> GSI 20 (level, low) -= > IRQ 20 PCI: Setting latency timer of device 0000:00:0b.0 to 64 ohci_hcd 0000:00:0b.0: OHCI Host Controller ohci_hcd 0000:00:0b.0: new USB bus registered, assigned bus number 2 ohci_hcd 0000:00:0b.0: irq 20, io mem 0xfe02f000 usb usb2: configuration #1 chosen from 1 choice hub 2-0:1.0: USB hub found hub 2-0:1.0: 8 ports detected usbcore: registered new interface driver libusual usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver Initializing USB Mass Storage driver... usbcore: registered new interface driver usb-storage USB Mass Storage support registered. ieee1394: Initialized config rom entry `ip1394' ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18 ACPI: PCI Interrupt 0000:03:08.0[A] -> Link [APC3] -> GSI 18 (level, low) -= > IRQ 21 ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=3D[21] MMIO=3D[fdfff000-fdfff= 7ff] Max Packet=3D[2048] IR/IT contexts=3D[4/8] ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=3D1) ieee1394: sbp2: Try serialize_io=3D0 for better performance ieee1394: Host added: ID:BUS[0-00:1023] GUID[0011d80001682310] Warning: /proc/ide/hd?/settings interface is obsolete, and will be removed = soon! Unable to identify CD-ROM format. VFS: Can't find an ext2 filesystem on dev hda. ReiserFS: hda: warning: sh-2021: reiserfs_fill_super: can not find reiserfs= on hda =46AT: invalid media value (0xa5) VFS: Can't find a valid FAT filesystem on dev hda. ISO 9660 Extensions: Microsoft Joliet Level 3 ISO 9660 Extensions: RRIP_1991A cloop: Initializing cloop v2.05 cloop: loaded (max 8 devices) cloop: /cdrom/KNOPPIX/KNOPPIX: 15609 blocks, 131072 bytes/block, largest bl= ock is 131098 bytes. cloop: loaded 256 blocks into cache. ISO 9660 Extensions: RRIP_1991A aufs 2.6.19-20061211 =46reeing unused kernel memory: 336k freed ACPI: Power Button (FF) [PWRF] ACPI: Power Button (CM) [PWRB] ACPI: Fan [FAN] (on) Using specific hotkey driver ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not= present [20060707] ACPI: Getting cpuindex for acpiid 0x2 ACPI Exception (acpi_processor-0681): AE_NOT_FOUND, Processor Device is not= present [20060707] ACPI: Getting cpuindex for acpiid 0x3 ACPI: Thermal Zone [THRM] (40 C) cpufreq: No nForce2 chipset. p4-clockmod: Unknown p4-clockmod-capable CPU. Please send an e-mail to p4-clockmod: Unknown p4-clockmod-capable CPU. Please send an e-mail to powernow: This module only works with AMD K7 CPUs Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled serial8250: ttyS0 at I/O 0x3f8 (irq =3D 4) is a 16550A eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0) forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.57. ACPI: PCI Interrupt Link [APCH] enabled at IRQ 23 ACPI: PCI Interrupt 0000:00:14.0[A] -> Link [APCH] -> GSI 23 (level, low) -= > IRQ 17 PCI: Setting latency timer of device 0000:00:14.0 to 64 forcedeth: using HIGHDMA 00:08: ttyS0 at I/O 0x3f8 (irq =3D 4) is a 16550A eth1: forcedeth.c: subsystem: 01043:8221 bound to 0000:00:14.0 i2c_adapter i2c-0: nForce2 SMBus adapter at 0x1c00 i2c_adapter i2c-1: nForce2 SMBus adapter at 0x1c80 parport: PnPBIOS parport detected. parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE,EPP] eth1: no link during initialization. ACPI: PCI Interrupt Link [AAZA] enabled at IRQ 22 ACPI: PCI Interrupt 0000:00:10.1[B] -> Link [AAZA] -> GSI 22 (level, low) -= > IRQ 18 PCI: Setting latency timer of device 0000:00:10.1 to 64 hda_codec: Unknown model for ALC883, trying auto-probe from BIOS... NET: Registered protocol family 17 eth1: link up. Linux agpgart interface v0.101 (c) Dave Jones device-mapper: ioctl: 4.10.0-ioctl (2006-09-14) initialised: dm-devel@redha= t.com NET: Registered protocol family 10 lo: Disabled Privacy Extensions Mobile IPv6 --Boundary-01=_N2hKHZAYVDEsOTi Content-Type: text/plain; charset="us-ascii"; name="boot_v.noapic" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="boot_v.noapic" /boot/kernel/acpi.ko text=0x53728 data=0x23a0+0x186c syms=[0x4+0x85f0+0x4+0xb06b] GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb SMAP type=01 base=0000000000000000 len=000000000009f000 SMAP type=02 base=00000000000f0000 len=0000000000010000 SMAP type=02 base=00000000fec00000 len=0000000001400000 SMAP type=02 base=00000000f0000000 len=0000000002000000 SMAP type=03 base=000000007fef3000 len=000000000000d000 SMAP type=04 base=000000007fef0000 len=0000000000003000 SMAP type=02 base=000000000009f000 len=0000000000001000 SMAP type=01 base=0000000000100000 len=000000007fdf0000 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-BETA1 #5: Thu Nov 1 18:21:33 CET 2007 mlaier@c2d.laiers.local:/usr/src/sys/i386/compile/GENERIC WARNING: WITNESS option enabled, expect reduced performance. Preloaded elf kernel "/boot/kernel/kernel" at 0xc1691000. Preloaded mfs_root "/boot/mfsroot" at 0xc1691180. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc16911c4. Calibrating clock(s) ... i8254 clock: 1193192 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2333352742 Hz CPU: Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz (2333.35-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6fb Stepping = 11 Features=0xbfebfbff Features2=0xe3fd AMD Features=0x20100000 AMD Features2=0x1 Cores per package: 2 Instruction TLB: 4 KB Pages, 4-way set associative, 128 entries 1st-level instruction cache: 32 KB, 8-way set associative, 64 byte line size 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size L2 cache: 4096 kbytes, 16-way associative, 64 bytes/line real memory = 2146369536 (2046 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009dfff, 643072 bytes (157 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000001828000 - 0x000000007daa4fff, 2082983936 bytes (508541 pages) avail memory = 2082439168 (1985 MB) bios32: Found BIOS32 Service Directory header at 0xc00fb430 bios32: Entry = 0xfba10 (c00fba10) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0xba40 pnpbios: Found PnP BIOS data at 0xc00fc5e0 pnpbios: Entry = f0000:c610 Rev = 1.0 Other BIOS signatures found: wlan: <802.11 Link Layer> ath_rate: version 1.2 wlan_amrr: random: nfslock: pseudo-device kbd: new array size 4 kbd1 at kbdmux0 mem: Pentium Pro MTRR support enabled io: null: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) rr232x: RocketRAID 232x controller driver v1.02 (Nov 1 2007 18:21:22) ACPI: RSDP @ 0x0xf77c0/0x0024 (v 2 Nvidia) ACPI: XSDT @ 0x0x7fef30c0/0x0044 (v 1 Nvidia ASUSACPI 0x42302E31 AWRD 0x00000000) ACPI: FACP @ 0x0x7fef9740/0x00F4 (v 3 Nvidia ASUSACPI 0x42302E31 AWRD 0x00000000) ACPI: DSDT @ 0x0x7fef3240/0x64AC (v 1 NVIDIA ASUSACPI 0x00001000 MSFT 0x03000000) ACPI: FACS @ 0x0x7fef0000/0x0040 ACPI: HPET @ 0x0x7fef9980/0x0038 (v 1 Nvidia ASUSACPI 0x42302E31 AWRD 0x00000098) ACPI: MCFG @ 0x0x7fef9a00/0x003C (v 1 Nvidia ASUSACPI 0x42302E31 AWRD 0x00000000) ACPI: APIC @ 0x0x7fef9880/0x0098 (v 1 Nvidia ASUSACPI 0x42302E31 AWRD 0x00000000) npx0: INT 16 interface acpi0: on motherboard acpi0: [MPSAFE] acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: wakeup code va 0xd9895000 pa 0x1000 atpic: Programming IRQ9 as level/low pci_open(1): mode 1 addr port (0x0cf8) is 0x80006804 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=03a310de) pcibios: BIOS version 3.00 AcpiOsDerivePciId: \_SB_.PCI0.BRCR -> bus 0 dev 0 func 0 AcpiOsDerivePciId: \_SB_.PCI0.VT86.PIO1 -> bus 0 dev 10 func 0 AcpiOsDerivePciId: \_SB_.PCI0.VT86.PIRQ -> bus 0 dev 10 func 0 acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 7fdf0000 (3) failed ACPI timer: 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 pci_link0: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link4: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 5 7 9 10 11 14 15 Validation 0 10 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link5: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 5 7 9 10 11 14 15 Validation 0 11 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link6: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link7: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link8: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link9: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link10: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 5 7 9 10 11 14 15 Validation 0 5 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link11: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link12: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 5 7 9 10 11 14 15 Validation 0 11 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link13: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link14: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link15: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link16: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link17: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link18: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 5 7 9 10 11 14 15 Validation 0 10 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link19: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 5 7 9 10 11 14 15 Validation 0 11 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link20: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 16 Validation 0 255 N 0 16 After Disable 0 255 N 0 16 pci_link21: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 17 Validation 0 255 N 0 17 After Disable 0 255 N 0 17 pci_link22: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 18 Validation 0 255 N 0 18 After Disable 0 255 N 0 18 pci_link23: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 19 Validation 0 255 N 0 19 After Disable 0 255 N 0 19 pci_link24: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 16 Validation 0 255 N 0 16 After Disable 0 255 N 0 16 pci_link25: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 16 Validation 0 255 N 0 16 After Disable 0 255 N 0 16 pci_link26: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 16 Validation 0 255 N 0 16 After Disable 0 255 N 0 16 pci_link27: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 16 Validation 0 255 N 0 16 After Disable 0 255 N 0 16 pci_link28: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link29: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link30: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link31: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link32: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link33: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link34: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link35: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link36: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link37: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link38: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link39: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link40: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 acpi_hpet0: iomem 0xfeff0000-0xfeff03ff on acpi0 acpi_hpet0: vend: 0x10de rev: 0x1 num: 7 hz: 25000000 opts: leg_route Timecounter "HPET" frequency 25000000 Hz quality 900 cpu0: on acpi0 cpu0: switching to generic Cx mode est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 72a072a0600072a device_attach: est0 attach returned 6 p4tcc0: on cpu0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 ACPI: Found matching pin for 0.10.INTA at func 1: 255 ACPI: Found matching pin for 0.11.INTA at func 0: 255 ACPI: Found matching pin for 0.11.INTB at func 1: 255 ACPI: Found matching pin for 0.20.INTA at func 0: 5 ACPI: Found matching pin for 0.16.INTB at func 1: 11 ACPI: Found matching pin for 0.14.INTA at func 0: 10 ACPI: Found matching pin for 0.15.INTA at func 0: 11 pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x10de, dev=0x03a3, revid=0xa2 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03ac, revid=0xa1 domain=0, bus=0, slot=0, func=1 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03aa, revid=0xa1 domain=0, bus=0, slot=0, func=2 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03a9, revid=0xa1 domain=0, bus=0, slot=0, func=3 class=05-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03ab, revid=0xa1 domain=0, bus=0, slot=0, func=4 class=05-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03a8, revid=0xa2 domain=0, bus=0, slot=0, func=5 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0004, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b5, revid=0xa1 domain=0, bus=0, slot=0, func=6 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b4, revid=0xa1 domain=0, bus=0, slot=0, func=7 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03ad, revid=0xa1 domain=0, bus=0, slot=1, func=0 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03ae, revid=0xa1 domain=0, bus=0, slot=1, func=1 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03af, revid=0xa1 domain=0, bus=0, slot=1, func=2 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b0, revid=0xa1 domain=0, bus=0, slot=1, func=3 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b1, revid=0xa1 domain=0, bus=0, slot=1, func=4 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b2, revid=0xa1 domain=0, bus=0, slot=1, func=5 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b3, revid=0xa1 domain=0, bus=0, slot=1, func=6 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b6, revid=0xa1 domain=0, bus=0, slot=2, func=0 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03bc, revid=0xa1 domain=0, bus=0, slot=2, func=1 class=05-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03ba, revid=0xa1 domain=0, bus=0, slot=2, func=2 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b7, revid=0xa1 domain=0, bus=0, slot=3, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D3 current D0 MSI supports 2 messages, 64 bit found-> vendor=0x10de, dev=0x03bb, revid=0xa1 domain=0, bus=0, slot=7, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D3 current D0 MSI supports 2 messages, 64 bit found-> vendor=0x10de, dev=0x0270, revid=0xa2 domain=0, bus=0, slot=9, func=0 class=05-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x0260, revid=0xa3 domain=0, bus=0, slot=10, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x0264, revid=0xa3 domain=0, bus=0, slot=10, func=1 class=0c-05-00, hdrtype=0x00, mfdev=1 cmdreg=0x0001, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[20]: type I/O Port, range 32, base 0x1c00, size 6, enabled map[24]: type I/O Port, range 32, base 0x1c80, size 6, enabled found-> vendor=0x10de, dev=0x0272, revid=0xa3 domain=0, bus=0, slot=10, func=2 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0400, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x026d, revid=0xa3 domain=0, bus=0, slot=11, func=0 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfe02f000, size 12, enabled found-> vendor=0x10de, dev=0x026e, revid=0xa3 domain=0, bus=0, slot=11, func=1 class=0c-03-20, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=b, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfe02e000, size 8, enabled found-> vendor=0x10de, dev=0x0265, revid=0xa1 domain=0, bus=0, slot=13, func=0 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) powerspec 2 supports D0 D3 current D0 map[20]: type I/O Port, range 32, base 0xfd00, size 4, enabled found-> vendor=0x10de, dev=0x0266, revid=0xa1 domain=0, bus=0, slot=14, func=0 class=01-01-85, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=10 powerspec 2 supports D0 D3 current D0 MSI supports 4 messages, 64 bit map[10]: type I/O Port, range 32, base 0x9f0, size 3, enabled map[14]: type I/O Port, range 32, base 0xbf0, size 2, enabled map[18]: type I/O Port, range 32, base 0x970, size 3, enabled map[1c]: type I/O Port, range 32, base 0xb70, size 2, enabled map[20]: type I/O Port, range 32, base 0xf800, size 4, enabled map[24]: type Memory, range 32, base 0xfe02d000, size 12, enabled pcib0: matched entry for 0.14.INTA (src \_SB_.PCI0.LSID:0) pcib0: slot 14 INTA routed to irq 10 via \_SB_.PCI0.LSID found-> vendor=0x10de, dev=0x0267, revid=0xa1 domain=0, bus=0, slot=15, func=0 class=01-01-85, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 4 messages, 64 bit map[10]: type I/O Port, range 32, base 0x9e0, size 3, enabled map[14]: type I/O Port, range 32, base 0xbe0, size 2, enabled map[18]: type I/O Port, range 32, base 0x960, size 3, enabled map[1c]: type I/O Port, range 32, base 0xb60, size 2, enabled map[20]: type I/O Port, range 32, base 0xf300, size 4, enabled map[24]: type Memory, range 32, base 0xfe02c000, size 12, enabled pcib0: matched entry for 0.15.INTA (src \_SB_.PCI0.LFID:0) pcib0: slot 15 INTA routed to irq 11 via \_SB_.PCI0.LFID found-> vendor=0x10de, dev=0x026f, revid=0xa2 domain=0, bus=0, slot=16, func=0 class=06-04-01, hdrtype=0x01, mfdev=1 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x02 (500 ns) found-> vendor=0x10de, dev=0x026c, revid=0xa2 domain=0, bus=0, slot=16, func=1 class=04-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x05 (1250 ns) intpin=b, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit, vector masks map[10]: type Memory, range 32, base 0xfe024000, size 14, enabled pcib0: matched entry for 0.16.INTB (src \_SB_.PCI0.LAZA:0) pcib0: slot 16 INTB routed to irq 11 via \_SB_.PCI0.LAZA found-> vendor=0x10de, dev=0x0269, revid=0xa3 domain=0, bus=0, slot=20, func=0 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x01 (250 ns), maxlat=0x14 (5000 ns) intpin=a, irq=5 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfe02b000, size 12, enabled map[14]: type I/O Port, range 32, base 0xf200, size 3, enabled pcib0: matched entry for 0.20.INTA (src \_SB_.PCI0.LMAC:0) pcib0: slot 20 INTA routed to irq 5 via \_SB_.PCI0.LMAC pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) pci0: at device 0.6 (no driver attached) pci0: at device 0.7 (no driver attached) pci0: at device 1.0 (no driver attached) pci0: at device 1.1 (no driver attached) pci0: at device 1.2 (no driver attached) pci0: at device 1.3 (no driver attached) pci0: at device 1.4 (no driver attached) pci0: at device 1.5 (no driver attached) pci0: at device 1.6 (no driver attached) pci0: at device 2.0 (no driver attached) pci0: at device 2.1 (no driver attached) pci0: at device 2.2 (no driver attached) pcib1: at device 3.0 on pci0 pcib1: domain 0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xe000-0xefff pcib1: memory decode 0xfa000000-0xfcffffff pcib1: prefetched decode 0xe0000000-0xefffffff pcib1: could not get PCI interrupt routing table for \_SB_.PCI0.XVRA - AE_NOT_FOUND pci1: on pcib1 pci1: domain=0, physical bus=1 found-> vendor=0x10de, dev=0x0391, revid=0xa1 domain=0, bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Memory, range 32, base 0xfa000000, size 24, enabled pcib1: requested memory range 0xfa000000-0xfaffffff: good map[14]: type Prefetchable Memory, range 64, base 0xe0000000, size 28, enabled pcib1: requested memory range 0xe0000000-0xefffffff: good map[1c]: type Memory, range 64, base 0xfb000000, size 24, enabled pcib1: requested memory range 0xfb000000-0xfbffffff: good map[24]: type I/O Port, range 32, base 0xef00, size 7, enabled pcib1: requested I/O range 0xef00-0xef7f: in range pcib0: matched entry for 0.3.INTA (src \_SB_.PCI0.LNK5:0) pcib0: slot 3 INTA routed to irq 10 via \_SB_.PCI0.LNK5 pcib1: slot 0 INTA is routed to irq 10 vgapci0: port 0xef00-0xef7f mem 0xfa000000-0xfaffffff,0xe0000000-0xefffffff,0xfb000000-0xfbffffff irq 10 at device 0.0 on pci1 pcib2: at device 7.0 on pci0 pcib2: domain 0 pcib2: secondary bus 2 pcib2: subordinate bus 2 pcib2: I/O decode 0xc000-0xcfff pcib2: memory decode 0xfdd00000-0xfddfffff pcib2: prefetched decode 0xfdc00000-0xfdcfffff pcib2: could not get PCI interrupt routing table for \_SB_.PCI0.XVRD - AE_NOT_FOUND pci2: on pcib2 pci2: domain=0, physical bus=2 found-> vendor=0x197b, dev=0x2360, revid=0x02 domain=0, bus=2, slot=0, func=0 class=01-06-01, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0xcf00, size 3, enabled pcib2: requested I/O range 0xcf00-0xcf07: in range map[14]: type I/O Port, range 32, base 0xce00, size 2, enabled pcib2: requested I/O range 0xce00-0xce03: in range map[18]: type I/O Port, range 32, base 0xcd00, size 3, enabled pcib2: requested I/O range 0xcd00-0xcd07: in range map[1c]: type I/O Port, range 32, base 0xcc00, size 2, enabled pcib2: requested I/O range 0xcc00-0xcc03: in range map[20]: type I/O Port, range 32, base 0xcb00, size 4, enabled pcib2: requested I/O range 0xcb00-0xcb0f: in range map[24]: type Memory, range 32, base 0xfddfe000, size 13, enabled pcib2: requested memory range 0xfddfe000-0xfddfffff: good pcib0: matched entry for 0.7.INTA (src \_SB_.PCI0.LNK6:0) pcib0: slot 7 INTA routed to irq 11 via \_SB_.PCI0.LNK6 pcib2: slot 0 INTA is routed to irq 11 atapci0: port 0xcf00-0xcf07,0xce00-0xce03,0xcd00-0xcd07,0xcc00-0xcc03,0xcb00-0xcb0f mem 0xfddfe000-0xfddfffff irq 11 at device 0.0 on pci2 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xcb00 atapci0: [MPSAFE] atapci0: [ITHREAD] atapci0: Reserved 0x2000 bytes for rid 0x24 type 3 at 0xfddfe000 atapci0: AHCI Version 01.00 controller with 1 ports detected ata2: on atapci0 ata2: SATA connect status=00000000 ata2: ahci_reset devices=0x0 ata2: [MPSAFE] ata2: [ITHREAD] pci0: at device 9.0 (no driver attached) isab0: at device 10.0 on pci0 isa0: on isab0 pci0: at device 10.1 (no driver attached) pci0: at device 10.2 (no driver attached) ohci0: mem 0xfe02f000-0xfe02ffff at device 11.0 on pci0 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfe02f000 pcib0: matched entry for 0.11.INTA (src \_SB_.PCI0.LUBA:0) pci_link8: Picked IRQ 9 with weight 0 pcib0: slot 11 INTA routed to irq 9 via \_SB_.PCI0.LUBA 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: 8 ports with 8 removable, self powered ehci0: mem 0xfe02e000-0xfe02e0ff at device 11.1 on pci0 ehci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0xfe02e000 pcib0: matched entry for 0.11.INTB (src \_SB_.PCI0.LUB2:0) pci_link16: Picked IRQ 5 with weight 1 pcib0: slot 11 INTB routed to irq 5 via \_SB_.PCI0.LUB2 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb1: EHCI version 1.0 usb1: companion controller, 8 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: on usb1 uhub1: 8 ports with 8 removable, self powered atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfd00-0xfd0f at device 13.0 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xfd00 ata0: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci1: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ata0: [MPSAFE] ata0: [ITHREAD] ata1: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci1: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=50 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=00 stat1=00 devices=0x4 ata1: [MPSAFE] ata1: [ITHREAD] atapci2: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xf800-0xf80f mem 0xfe02d000-0xfe02dfff irq 10 at device 14.0 on pci0 atapci2: Reserved 0x10 bytes for rid 0x20 type 4 at 0xf800 atapci2: [MPSAFE] atapci2: [ITHREAD] atapci2: Reserved 0x1000 bytes for rid 0x24 type 3 at 0xfe02d000 ata3: on atapci2 atapci2: Reserved 0x8 bytes for rid 0x10 type 4 at 0x9f0 atapci2: Reserved 0x4 bytes for rid 0x14 type 4 at 0xbf0 ata3: SATA connect time=0ms ata3: reset tp1 mask=01 ostat0=50 ostat1=00 ata3: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata3: reset tp2 stat0=50 stat1=00 devices=0x1 ata3: [MPSAFE] ata3: [ITHREAD] ata4: on atapci2 atapci2: Reserved 0x8 bytes for rid 0x18 type 4 at 0x970 atapci2: Reserved 0x4 bytes for rid 0x1c type 4 at 0xb70 ata4: SATA connect status=00000000 ata4: [MPSAFE] ata4: [ITHREAD] atapci3: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xf300-0xf30f mem 0xfe02c000-0xfe02cfff irq 11 at device 15.0 on pci0 atapci3: Reserved 0x10 bytes for rid 0x20 type 4 at 0xf300 atapci3: [MPSAFE] atapci3: [ITHREAD] atapci3: Reserved 0x1000 bytes for rid 0x24 type 3 at 0xfe02c000 ata5: on atapci3 atapci3: Reserved 0x8 bytes for rid 0x10 type 4 at 0x9e0 atapci3: Reserved 0x4 bytes for rid 0x14 type 4 at 0xbe0 ata5: SATA connect status=00000000 ata5: [MPSAFE] ata5: [ITHREAD] ata6: on atapci3 atapci3: Reserved 0x8 bytes for rid 0x18 type 4 at 0x960 atapci3: Reserved 0x4 bytes for rid 0x1c type 4 at 0xb60 ata6: SATA connect status=00000000 ata6: [MPSAFE] ata6: [ITHREAD] pcib3: at device 16.0 on pci0 pcib3: domain 0 pcib3: secondary bus 3 pcib3: subordinate bus 3 pcib3: I/O decode 0xd000-0xdfff pcib3: memory decode 0xfdf00000-0xfdffffff pcib3: prefetched decode 0xfde00000-0xfdefffff pcib3: Subtractively decoded bridge. ACPI: Found matching pin for 3.8.INTA at func 0: 255 pci3: on pcib3 pci3: domain=0, physical bus=3 found-> vendor=0x1106, dev=0x3044, revid=0xc0 domain=0, bus=3, slot=8, func=0 class=0c-00-10, hdrtype=0x00, mfdev=0 cmdreg=0x0017, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x20 (8000 ns) intpin=a, irq=255 powerspec 2 supports D0 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfdfff000, size 11, enabled pcib3: requested memory range 0xfdfff000-0xfdfff7ff: good map[14]: type I/O Port, range 32, base 0xdf00, size 7, enabled pcib3: requested I/O range 0xdf00-0xdf7f: in range fwohci0: port 0xdf00-0xdf7f mem 0xfdfff000-0xfdfff7ff at device 8.0 on pci3 fwohci0: Reserved 0x800 bytes for rid 0x10 type 3 at 0xfdfff000 pcib3: matched entry for 3.8.INTA (src \_SB_.PCI0.LNK3:0) pci_link2: Picked IRQ 9 with weight 1 pcib3: slot 8 INTA routed to irq 9 via \_SB_.PCI0.LNK3 fwohci0: [MPSAFE] fwohci0: [FILTER] fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:11:d8:00:01:68:23:10 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:11:d8:68:23:10 fwe0: bpf attached fwe0: Ethernet address: 02:11:d8:68:23:10 fwip0: on firewire0 fwip0: bpf attached fwip0: Firewire address: 00:11:d8:00:01:68:23:10 @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0xb825e0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode pci0: at device 16.1 (no driver attached) nfe0: port 0xf200-0xf207 mem 0xfe02b000-0xfe02bfff irq 5 at device 20.0 on pci0 nfe0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfe02b000 miibus0: on nfe0 e1000phy0: PHY 1 on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto nfe0: bpf attached nfe0: Ethernet address: 00:1d:60:0c:17:71 nfe0: [MPSAFE] nfe0: [FILTER] acpi_tz0: on acpi0 sio0: irq maps: 0x1 0x11 0x1 0x1 sio0: irq maps: 0x1 0x11 0x1 0x1 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio0: [FILTER] psmcpnp0: irq 12 on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 07 03 c8 psm: status 07 03 c8 psm: status 07 03 c8 psm: data c8 c2 38 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model MouseMan+, device ID 0-38, 3 buttons psm0: config:00000000, flags:00000008, packet size:3 psm0: syncmask:08, syncbits:00 unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff ex_isa_identify() ahc_isa_probe 0: ioport 0xc00 alloc failed ahc_isa_probe 1: ioport 0x1c00 alloc failed ahc_isa_probe 12: ioport 0xcc00 alloc failed ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it atkbdc: atkbdc0 already exists; skipping it sio: sio0 already exists; skipping it pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices pmtimer0 on isa0 orm0: at iomem 0xd0000-0xd7fff,0xd8000-0xd9fff pnpid ORM0000 on isa0 adv0: not probed (disabled) aha0: not probed (disabled) aic0: not probed (disabled) bt0: not probed (disabled) cs0: not probed (disabled) ed0: not probed (disabled) fdc0 failed to probe at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fe0: not probed (disabled) ie0: not probed (disabled) le0: not probed (disabled) ppc0: parallel port found at 0x378 ppc0: using extended I/O port range ppc0: EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 ppi0: on ppbus0 plip0: on ppbus0 plip0: bpf attached lpt0: on ppbus0 lpt0: Interrupt-driven port ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd1, terminal emulator: sc (syscons terminal) sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: irq maps: 0x1 0x1 0x1 0x1 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) sn0: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 vt0: not probed (disabled) isa_probe_children: probing PnP devices Device configuration finished. Reducing kern.maxvnodes 133530 -> 100000 procfs registered firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) Timecounter "TSC" frequency 2333352742 Hz quality 800 Timecounters tick every 1.000 msec lo0: bpf attached rr232x: no controller detected. md0: Preloaded image 9437184 bytes at 0xc0d237e0 ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=80 wire ad0: setting PIO4 on nForce MCP51 chip ad0: setting UDMA100 on nForce MCP51 chip ad0: 39266MB at ata0-master UDMA100 ad0: 80418240 sectors [79780C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad0 ad0: nVidia check1 failed ad0: Adaptec check1 failed ad0: LSI (v3) check1 failed ad0: LSI (v2) check1 failed ad0: FreeBSD check1 failed ata1-master: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=80 wire acd0: setting PIO4 on nForce MCP51 chip acd0: setting UDMA33 on nForce MCP51 chip acd0: DVDR drive at ata1 as master acd0: read 6890KB/s (6890KB/s) write 6890KB/s (6890KB/s), 2048KB buffer, UDMA33 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, DVDRAM, packet acd0: Writes: CDR, CDRW, DVDR, DVDRAM, test write, burnproof acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc ata3-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire ad6: 143089MB at ata3-master SATA150 ad6: 293046768 sectors [290721C/16H/63S] 16 sectors/interrupt 1 depth queue ad6: nVidia check1 failed ad6: Adaptec check1 failed ad6: LSI (v3) check1 failed ad6: LSI (v2) check1 failed ad6: FreeBSD check1 failed GEOM: new disk ad6 (probe0:sbp0:0:0:0): error 22 (probe0:sbp0:0:0:0): Unretryable Error (probe1:sbp0:0:1:0): error 22 (probe1:sbp0:0:1:0): Unretryable Error (probe6:sbp0:0:6:0): error 22 (probe6:sbp0:0:6:0): Unretryable Error (probe2:sbp0:0:2:0): error 22 (probe2:sbp0:0:2:0): Unretryable Error (probe3:sbp0:0:3:0): error 22 (probe3:sbp0:0:3:0): Unretryable Error (probe4:sbp0:0:4:0): error 22 (probe4:sbp0:0:4:0): Unretryable Error (probe5:sbp0:0:5:0): error 22 (probe5:sbp0:0:5:0): Unretryable Error ATA PseudoRAID loaded WARNING: WITNESS option enabled, expect reduced performance. --Boundary-01=_N2hKHZAYVDEsOTi Content-Type: text/plain; charset="us-ascii"; name="devinfo_rv" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="devinfo_rv" nexus0 legacy0 ram0 I/O memory addresses: 0x0-0x9dfff 0x100000-0x7feeffff npx0 acpi0 Interrupt request lines: 0x9 I/O ports: 0x10-0x1f 0x22-0x3f 0x44-0x5f 0x62-0x63 0x65-0x6f 0x74-0x7f 0x91-0x93 0xa2-0xbf 0xe0-0xef 0x290-0x297 0x4d0-0x4d1 0x800-0x87f 0x880-0x88f 0x1000-0x107f 0x1080-0x10ff 0x1400-0x147f 0x1480-0x14ff 0x1800-0x187f 0x1880-0x18ff I/O memory addresses: 0xda000-0xdbfff 0xf0000-0xf7fff 0xf8000-0xfbfff 0xfc000-0xfffff 0x7fef0000-0x7fefffff 0xf0000000-0xf1ffffff 0xfec00000-0xfec00fff 0xfee00000-0xfee00fff 0xfeff0000-0xfeff03ff 0xffff0000-0xffffffff cpu0 pnpinfo _HID=none _UID=0 at handle=\_PR_.CPU0 est0 p4tcc0 cpufreq0 unknown pnpinfo _HID=none _UID=0 at handle=\_PR_.CPU1 unknown pnpinfo _HID=none _UID=0 at handle=\_PR_.CPU2 unknown pnpinfo _HID=none _UID=0 at handle=\_PR_.CPU3 acpi_button0 pnpinfo _HID=PNP0C0C _UID=0 at handle=\_SB_.PWRB pcib0 pnpinfo _HID=PNP0A08 _UID=1 at handle=\_SB_.PCI0 pci0 hostb0 pnpinfo vendor=0x10de device=0x03a3 subvendor=0x0000 subdevice=0x0000 class=0x060000 at slot=0 function=0 unknown pnpinfo vendor=0x10de device=0x03ac subvendor=0x0000 subdevice=0x0000 class=0x050000 at slot=0 function=1 unknown pnpinfo vendor=0x10de device=0x03aa subvendor=0x0000 subdevice=0x0000 class=0x050000 at slot=0 function=2 handle=\_SB_.PCI0.MIP4 unknown pnpinfo vendor=0x10de device=0x03a9 subvendor=0x0000 subdevice=0x0000 class=0x050000 at slot=0 function=3 unknown pnpinfo vendor=0x10de device=0x03ab subvendor=0x0000 subdevice=0x0000 class=0x050000 at slot=0 function=4 unknown pnpinfo vendor=0x10de device=0x03a8 subvendor=0x0000 subdevice=0x0000 class=0x050000 at slot=0 function=5 unknown pnpinfo vendor=0x10de device=0x03b5 subvendor=0x0000 subdevice=0x0000 class=0x050000 at slot=0 function=6 unknown pnpinfo vendor=0x10de device=0x03b4 subvendor=0x0000 subdevice=0x0000 class=0x050000 at slot=0 function=7 unknown pnpinfo vendor=0x10de device=0x03ad subvendor=0x0000 subdevice=0x0000 class=0x050000 at slot=1 function=0 unknown pnpinfo vendor=0x10de device=0x03ae subvendor=0x0000 subdevice=0x0000 class=0x050000 at slot=1 function=1 unknown pnpinfo vendor=0x10de device=0x03af subvendor=0x0000 subdevice=0x0000 class=0x050000 at slot=1 function=2 unknown pnpinfo vendor=0x10de device=0x03b0 subvendor=0x0000 subdevice=0x0000 class=0x050000 at slot=1 function=3 unknown pnpinfo vendor=0x10de device=0x03b1 subvendor=0x0000 subdevice=0x0000 class=0x050000 at slot=1 function=4 unknown pnpinfo vendor=0x10de device=0x03b2 subvendor=0x0000 subdevice=0x0000 class=0x050000 at slot=1 function=5 unknown pnpinfo vendor=0x10de device=0x03b3 subvendor=0x0000 subdevice=0x0000 class=0x050000 at slot=1 function=6 unknown pnpinfo vendor=0x10de device=0x03b6 subvendor=0x0000 subdevice=0x0000 class=0x050000 at slot=2 function=0 unknown pnpinfo vendor=0x10de device=0x03bc subvendor=0x0000 subdevice=0x0000 class=0x050000 at slot=2 function=1 unknown pnpinfo vendor=0x10de device=0x03ba subvendor=0x0000 subdevice=0x0000 class=0x050000 at slot=2 function=2 pcib1 pnpinfo vendor=0x10de device=0x03b7 subvendor=0x10de subdevice=0x0c55 class=0x060400 at slot=3 function=0 handle=\_SB_.PCI0.XVRA pci1 vgapci0 pnpinfo vendor=0x10de device=0x0391 subvendor=0x1682 subdevice=0x2220 class=0x030000 at slot=0 function=0 I/O ports: 0xef00-0xef7f I/O memory addresses: 0xe0000000-0xefffffff 0xfa000000-0xfaffffff 0xfb000000-0xfbffffff drm0 pcib2 pnpinfo vendor=0x10de device=0x03bb subvendor=0x10de subdevice=0x0c55 class=0x060400 at slot=7 function=0 handle=\_SB_.PCI0.XVRD pci2 atapci0 pnpinfo vendor=0x197b device=0x2360 subvendor=0x1043 subdevice=0x8208 class=0x010601 at slot=0 function=0 Interrupt request lines: 0xb I/O ports: 0xcb00-0xcb0f 0xcc00-0xcc03 0xcd00-0xcd07 0xce00-0xce03 0xcf00-0xcf07 I/O memory addresses: 0xfddfe000-0xfddfffff ata2 unknown pnpinfo vendor=0x10de device=0x0270 subvendor=0x1043 subdevice=0x81bc class=0x050000 at slot=9 function=0 isab0 pnpinfo vendor=0x10de device=0x0260 subvendor=0x1043 subdevice=0x81bc class=0x060100 at slot=10 function=0 handle=\_SB_.PCI0.VT86 isa0 adv0 aha0 aic0 bt0 cs0 ed0 fdc0 I/O ports: 0x3f7 fe0 ie0 le0 ppc0 Interrupt request lines: 0x7 I/O ports: 0x378-0x37f ppbus0 ppi0 plip0 lpt0 sc0 sio1 sio2 sio3 sn0 vga0 I/O ports: 0x3c0-0x3df I/O memory addresses: 0xa0000-0xbffff vt0 orm0 pnpinfo pnpid=ORM0000 I/O memory addresses: 0xd0000-0xd7fff 0xd8000-0xd9fff pmtimer0 unknown pnpinfo vendor=0x10de device=0x0264 subvendor=0x1043 subdevice=0x81bc class=0x0c0500 at slot=10 function=1 handle=\_SB_.PCI0.SMB0 I/O ports: 0x1c00-0x1c3f 0x1c80-0x1cbf unknown pnpinfo vendor=0x10de device=0x0272 subvendor=0x1043 subdevice=0x81bc class=0x050000 at slot=10 function=2 ohci0 pnpinfo vendor=0x10de device=0x026d subvendor=0x1043 subdevice=0x81bc class=0x0c0310 at slot=11 function=0 handle=\_SB_.PCI0.USB0 I/O memory addresses: 0xfe02f000-0xfe02ffff usb0 uhub0 ehci0 pnpinfo vendor=0x10de device=0x026e subvendor=0x1043 subdevice=0x81bc class=0x0c0320 at slot=11 function=1 handle=\_SB_.PCI0.USB2 Interrupt request lines: 0x5 I/O memory addresses: 0xfe02e000-0xfe02e0ff usb1 uhub1 atapci1 pnpinfo vendor=0x10de device=0x0265 subvendor=0x1043 subdevice=0x81bc class=0x01018a at slot=13 function=0 handle=\_SB_.PCI0.IDE0 I/O ports: 0x170-0x177 0x1f0-0x1f7 0x376 0x3f6 0xfd00-0xfd0f ata0 Interrupt request lines: 0xe ad0 subdisk0 ata1 Interrupt request lines: 0xf acd0 atapci2 pnpinfo vendor=0x10de device=0x0266 subvendor=0x1043 subdevice=0x81bc class=0x010185 at slot=14 function=0 handle=\_SB_.PCI0.SAT1 Interrupt request lines: 0xa I/O ports: 0x970-0x977 0x9f0-0x9f7 0xb70-0xb73 0xbf0-0xbf3 0xf800-0xf80f I/O memory addresses: 0xfe02d000-0xfe02dfff ata3 ad6 subdisk6 ata4 atapci3 pnpinfo vendor=0x10de device=0x0267 subvendor=0x1043 subdevice=0x81bc class=0x010185 at slot=15 function=0 handle=\_SB_.PCI0.SAT2 I/O ports: 0x960-0x967 0x9e0-0x9e7 0xb60-0xb63 0xbe0-0xbe3 0xf300-0xf30f I/O memory addresses: 0xfe02c000-0xfe02cfff ata5 ata6 pcib3 pnpinfo vendor=0x10de device=0x026f subvendor=0x10de subdevice=0xcb84 class=0x060401 at slot=16 function=0 handle=\_SB_.PCI0.HUB0 pci3 fwohci0 pnpinfo vendor=0x1106 device=0x3044 subvendor=0x1043 subdevice=0x81fe class=0x0c0010 at slot=8 function=0 I/O ports: 0xdf00-0xdf7f I/O memory addresses: 0xfdfff000-0xfdfff7ff firewire0 fwe0 fwip0 sbp0 dcons_crom0 unknown pnpinfo vendor=0x10de device=0x026c subvendor=0x1043 subdevice=0x8249 class=0x040300 at slot=16 function=1 handle=\_SB_.PCI0.AZAD I/O memory addresses: 0xfe024000-0xfe027fff nfe0 pnpinfo vendor=0x10de device=0x0269 subvendor=0x1043 subdevice=0x8221 class=0x068000 at slot=20 function=0 handle=\_SB_.PCI0.MMAC I/O ports: 0xf200-0xf207 I/O memory addresses: 0xfe02b000-0xfe02bfff miibus0 e1000phy0 pnpinfo oui=0x5043 model=0x21 rev=0x1 at phyno=1 acpi_sysresource0 pnpinfo _HID=PNP0C02 _UID=5 at handle=\_SB_.PCI0.MBIO unknown pnpinfo _HID=none _UID=0 at handle=\_SB_.PCI0.SAT1.PRI0 unknown pnpinfo _HID=none _UID=0 at handle=\_SB_.PCI0.SAT1.PRI0.MAST unknown pnpinfo _HID=none _UID=0 at handle=\_SB_.PCI0.SAT1.SEC0 unknown pnpinfo _HID=none _UID=0 at handle=\_SB_.PCI0.SAT1.SEC0.MAST unknown pnpinfo _HID=none _UID=0 at handle=\_SB_.PCI0.SAT2.PRI0 unknown pnpinfo _HID=none _UID=0 at handle=\_SB_.PCI0.SAT2.PRI0.MAST unknown pnpinfo _HID=none _UID=0 at handle=\_SB_.PCI0.SAT2.SEC0 unknown pnpinfo _HID=none _UID=0 at handle=\_SB_.PCI0.SAT2.SEC0.MAST unknown pnpinfo _HID=none _UID=0 at handle=\_SB_.PCI0.IDE0.PRI0 unknown pnpinfo _HID=none _UID=0 at handle=\_SB_.PCI0.IDE0.PRI0.MAST unknown pnpinfo _HID=none _UID=0 at handle=\_SB_.PCI0.IDE0.PRI0.SLAV unknown pnpinfo _HID=none _UID=0 at handle=\_SB_.PCI0.IDE0.SEC0 unknown pnpinfo _HID=none _UID=0 at handle=\_SB_.PCI0.IDE0.SEC0.MAST unknown pnpinfo _HID=none _UID=0 at handle=\_SB_.PCI0.IDE0.SEC0.SLAV unknown pnpinfo _HID=none _UID=0 at handle=\_SB_.PCI0.XVRB unknown pnpinfo _HID=none _UID=0 at handle=\_SB_.PCI0.XVRC acpi_sysresource1 pnpinfo _HID=PNP0C02 _UID=1 at handle=\_SB_.PCI0.VT86.SYSR atpic0 pnpinfo _HID=PNP0000 _UID=0 at handle=\_SB_.PCI0.VT86.PIC_ atdma0 pnpinfo _HID=PNP0200 _UID=0 at handle=\_SB_.PCI0.VT86.DMA1 attimer0 pnpinfo _HID=PNP0100 _UID=0 at handle=\_SB_.PCI0.VT86.TMR_ unknown pnpinfo _HID=PNP0103 _UID=0 at handle=\_SB_.PCI0.VT86.HPET attimer1 pnpinfo _HID=PNP0B00 _UID=0 at handle=\_SB_.PCI0.VT86.RTC_ unknown pnpinfo _HID=PNP0800 _UID=0 at handle=\_SB_.PCI0.VT86.SPKR npxisa0 pnpinfo _HID=PNP0C04 _UID=0 at handle=\_SB_.PCI0.VT86.COPR unknown pnpinfo _HID=PNP0700 _UID=0 at handle=\_SB_.PCI0.VT86.FDC0 sio0 pnpinfo _HID=PNP0501 _UID=1 at handle=\_SB_.PCI0.VT86.UAR1 Interrupt request lines: 0x4 I/O ports: 0x3f8-0x3ff unknown pnpinfo _HID=PNP0400 _UID=1 at handle=\_SB_.PCI0.VT86.LPT1 unknown pnpinfo _HID=PNP0401 _UID=1 at handle=\_SB_.PCI0.VT86.ECP1 psmcpnp0 pnpinfo _HID=PNP0F13 _UID=0 at handle=\_SB_.PCI0.VT86.PS2M Interrupt request lines: 0xc atkbdc0 pnpinfo _HID=PNP0303 _UID=0 at handle=\_SB_.PCI0.VT86.PS2K I/O ports: 0x60 0x64 atkbd0 Interrupt request lines: 0x1 psm0 unknown pnpinfo _HID=PNP0C02 _UID=3 at handle=\_SB_.PCI0.VT86.PSMR unknown pnpinfo _HID=none _UID=0 at handle=\_SB_.PCI0.MACI unknown pnpinfo _HID=none _UID=0 at handle=\_SB_.PCI0.MMCI unknown pnpinfo _HID=NVRAIDBUS _UID=0 at handle=\_SB_.PCI0.NVRB unknown pnpinfo _HID=ATK0110 _UID=16843024 at handle=\_SB_.PCI0.ASOC pci_link0 pnpinfo _HID=PNP0C0F _UID=1 at handle=\_SB_.PCI0.LNK1 pci_link1 pnpinfo _HID=PNP0C0F _UID=2 at handle=\_SB_.PCI0.LNK2 pci_link2 pnpinfo _HID=PNP0C0F _UID=3 at handle=\_SB_.PCI0.LNK3 pci_link3 pnpinfo _HID=PNP0C0F _UID=4 at handle=\_SB_.PCI0.LNK4 pci_link4 pnpinfo _HID=PNP0C0F _UID=5 at handle=\_SB_.PCI0.LNK5 pci_link5 pnpinfo _HID=PNP0C0F _UID=6 at handle=\_SB_.PCI0.LNK6 pci_link6 pnpinfo _HID=PNP0C0F _UID=7 at handle=\_SB_.PCI0.LNK7 pci_link7 pnpinfo _HID=PNP0C0F _UID=8 at handle=\_SB_.PCI0.LNK8 pci_link8 pnpinfo _HID=PNP0C0F _UID=9 at handle=\_SB_.PCI0.LUBA pci_link9 pnpinfo _HID=PNP0C0F _UID=10 at handle=\_SB_.PCI0.LUBB pci_link10 pnpinfo _HID=PNP0C0F _UID=11 at handle=\_SB_.PCI0.LMAC pci_link11 pnpinfo _HID=PNP0C0F _UID=12 at handle=\_SB_.PCI0.LACI pci_link12 pnpinfo _HID=PNP0C0F _UID=13 at handle=\_SB_.PCI0.LAZA pci_link13 pnpinfo _HID=PNP0C0F _UID=14 at handle=\_SB_.PCI0.LPMU pci_link14 pnpinfo _HID=PNP0C0F _UID=15 at handle=\_SB_.PCI0.LMCI pci_link15 pnpinfo _HID=PNP0C0F _UID=16 at handle=\_SB_.PCI0.LSMB pci_link16 pnpinfo _HID=PNP0C0F _UID=17 at handle=\_SB_.PCI0.LUB2 pci_link17 pnpinfo _HID=PNP0C0F _UID=18 at handle=\_SB_.PCI0.LIDE pci_link18 pnpinfo _HID=PNP0C0F _UID=19 at handle=\_SB_.PCI0.LSID pci_link19 pnpinfo _HID=PNP0C0F _UID=20 at handle=\_SB_.PCI0.LFID pci_link20 pnpinfo _HID=PNP0C0F _UID=21 at handle=\_SB_.PCI0.APC1 pci_link21 pnpinfo _HID=PNP0C0F _UID=22 at handle=\_SB_.PCI0.APC2 pci_link22 pnpinfo _HID=PNP0C0F _UID=23 at handle=\_SB_.PCI0.APC3 pci_link23 pnpinfo _HID=PNP0C0F _UID=24 at handle=\_SB_.PCI0.APC4 pci_link24 pnpinfo _HID=PNP0C0F _UID=25 at handle=\_SB_.PCI0.APC5 pci_link25 pnpinfo _HID=PNP0C0F _UID=26 at handle=\_SB_.PCI0.APC6 pci_link26 pnpinfo _HID=PNP0C0F _UID=27 at handle=\_SB_.PCI0.APC7 pci_link27 pnpinfo _HID=PNP0C0F _UID=28 at handle=\_SB_.PCI0.APC8 pci_link28 pnpinfo _HID=PNP0C0F _UID=29 at handle=\_SB_.PCI0.APCF pci_link29 pnpinfo _HID=PNP0C0F _UID=30 at handle=\_SB_.PCI0.APCG pci_link30 pnpinfo _HID=PNP0C0F _UID=31 at handle=\_SB_.PCI0.APCH pci_link31 pnpinfo _HID=PNP0C0F _UID=32 at handle=\_SB_.PCI0.APCJ pci_link32 pnpinfo _HID=PNP0C0F _UID=33 at handle=\_SB_.PCI0.APMU pci_link33 pnpinfo _HID=PNP0C0F _UID=34 at handle=\_SB_.PCI0.AAZA pci_link34 pnpinfo _HID=PNP0C0F _UID=35 at handle=\_SB_.PCI0.APCK pci_link35 pnpinfo _HID=PNP0C0F _UID=36 at handle=\_SB_.PCI0.APCS pci_link36 pnpinfo _HID=PNP0C0F _UID=37 at handle=\_SB_.PCI0.APCL pci_link37 pnpinfo _HID=PNP0C0F _UID=38 at handle=\_SB_.PCI0.APCM pci_link38 pnpinfo _HID=PNP0C0F _UID=39 at handle=\_SB_.PCI0.APCZ pci_link39 pnpinfo _HID=PNP0C0F _UID=40 at handle=\_SB_.PCI0.APSI pci_link40 pnpinfo _HID=PNP0C0F _UID=41 at handle=\_SB_.PCI0.APSJ acpi_sysresource2 pnpinfo _HID=PNP0C02 _UID=4 at handle=\_SB_.PCI0.EXPL acpi_sysresource3 pnpinfo _HID=PNP0C01 _UID=0 at handle=\_SB_.MEM_ unknown pnpinfo _HID=PNP0C0B _UID=0 at handle=\_TZ_.FAN_ acpi_tz0 pnpinfo _HID=none _UID=0 at handle=\_TZ_.THRM acpi_timer0 pnpinfo unknown at unknown ACPI I/O ports: 0x1008-0x100b acpi_hpet0 pnpinfo unknown at unknown ACPI I/O memory addresses: 0xfeff0000-0xfeff03ff --Boundary-01=_N2hKHZAYVDEsOTi Content-Type: text/plain; charset="us-ascii"; name="boot_v.apic" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="boot_v.apic" set hint.apic.0.disabled=0 OK boot -vs /boot/kernel/acpi.ko text=0x53728 data=0x23a0+0x186c syms=[0x4+0x85f0+0x4+0xb06b] GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb SMAP type=01 base=0000000000000000 len=000000000009f000 SMAP type=02 base=00000000000f0000 len=0000000000010000 SMAP type=02 base=00000000fec00000 len=0000000001400000 SMAP type=02 base=00000000f0000000 len=0000000002000000 SMAP type=03 base=000000007fef3000 len=000000000000d000 SMAP type=04 base=000000007fef0000 len=0000000000003000 SMAP type=02 base=000000000009f000 len=0000000000001000 SMAP type=01 base=0000000000100000 len=000000007fdf0000 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-BETA1 #5: Thu Nov 1 18:21:33 CET 2007 mlaier@c2d.laiers.local:/usr/src/sys/i386/compile/GENERIC WARNING: WITNESS option enabled, expect reduced performance. Preloaded elf kernel "/boot/kernel/kernel" at 0xc1691000. Preloaded mfs_root "/boot/mfsroot" at 0xc1691180. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc16911c4. Calibrating clock(s) ... i8254 clock: 1193192 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2333351867 Hz CPU: Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz (2333.35-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6fb Stepping = 11 Features=0xbfebfbff Features2=0xe3fd AMD Features=0x20100000 AMD Features2=0x1 Cores per package: 2 Instruction TLB: 4 KB Pages, 4-way set associative, 128 entries 1st-level instruction cache: 32 KB, 8-way set associative, 64 byte line size 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size L2 cache: 4096 kbytes, 16-way associative, 64 bytes/line real memory = 2146369536 (2046 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009dfff, 643072 bytes (157 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000001828000 - 0x000000007daa4fff, 2082983936 bytes (508541 pages) avail memory = 2082439168 (1985 MB) Table 'FACP' at 0x7fef9740 Table 'HPET' at 0x7fef9980 Table 'MCFG' at 0x7fef9a00 Table 'APIC' at 0x7fef9880 MADT: Found table at 0x7fef9880 MP Configuration Table version 1.4 found at 0xc00f1400 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 0: enabled SMP: Added CPU 0 (AP) MADT: Found CPU APIC ID 1 ACPI ID 1: enabled SMP: Added CPU 1 (AP) MADT: Found CPU APIC ID 2 ACPI ID 2: disabled MADT: Found CPU APIC ID 3 ACPI ID 3: disabled ACPI APIC Table: INTR: Adding local APIC 1 as a target FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 bios32: Found BIOS32 Service Directory header at 0xc00fb430 bios32: Entry = 0xfba10 (c00fba10) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0xba40 pnpbios: Found PnP BIOS data at 0xc00fc5e0 pnpbios: Entry = f0000:c610 Rev = 1.0 Other BIOS signatures found: APIC: CPU 0 has ACPI ID 0 APIC: CPU 1 has ACPI ID 1 ACPI: RSDP @ 0x0xf77c0/0x0024 (v 2 Nvidia) ACPI: XSDT @ 0x0x7fef30c0/0x0044 (v 1 Nvidia ASUSACPI 0x42302E31 AWRD 0x00000000) ACPI: FACP @ 0x0x7fef9740/0x00F4 (v 3 Nvidia ASUSACPI 0x42302E31 AWRD 0x00000000) ACPI: DSDT @ 0x0x7fef3240/0x64AC (v 1 NVIDIA ASUSACPI 0x00001000 MSFT 0x03000000) ACPI: FACS @ 0x0x7fef0000/0x0040 ACPI: HPET @ 0x0x7fef9980/0x0038 (v 1 Nvidia ASUSACPI 0x42302E31 AWRD 0x00000098) ACPI: MCFG @ 0x0x7fef9a00/0x003C (v 1 Nvidia ASUSACPI 0x42302E31 AWRD 0x00000000) ACPI: APIC @ 0x0x7fef9880/0x0098 (v 1 Nvidia ASUSACPI 0x42302E31 AWRD 0x00000000) MADT: Found IO APIC ID 4, Interrupt 0 at 0xfec00000 ioapic0: Changing APIC ID to 4 ioapic0: Routing external 8259A's -> intpin 0 MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level MADT: Interrupt override: source 14, irq 14 MADT: Interrupt override: source 15, irq 15 lapic0: Routing NMI -> LINT1 lapic0: LINT1 trigger: edge lapic0: LINT1 polarity: high lapic1: Routing NMI -> LINT1 lapic1: LINT1 trigger: edge lapic1: LINT1 polarity: high MADT: Ignoring local NMI routed to ACPI CPU 2 MADT: Ignoring local NMI routed to ACPI CPU 3 ioapic0 irqs 0-23 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 wlan: <802.11 Link Layer> ath_rate: version 1.2 wlan_amrr: random: nfslock: pseudo-device kbd: new array size 4 kbd1 at kbdmux0 mem: Pentium Pro MTRR support enabled io: null: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) rr232x: RocketRAID 232x controller driver v1.02 (Nov 1 2007 18:21:22) npx0: INT 16 interface acpi0: on motherboard ioapic0: routing intpin 9 (ISA IRQ 9) to vector 48 acpi0: [MPSAFE] acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: wakeup code va 0xd9895000 pa 0x1000 pci_open(1): mode 1 addr port (0x0cf8) is 0x80006804 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=03a310de) pcibios: BIOS version 3.00 AcpiOsDerivePciId: \_SB_.PCI0.BRCR -> bus 0 dev 0 func 0 AcpiOsDerivePciId: \_SB_.PCI0.VT86.PIO1 -> bus 0 dev 10 func 0 AcpiOsDerivePciId: \_SB_.PCI0.VT86.PIRQ -> bus 0 dev 10 func 0 acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 7fdf0000 (3) failed ACPI timer: 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 pci_link0: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link4: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 5 7 9 10 11 14 15 Validation 0 10 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link5: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 5 7 9 10 11 14 15 Validation 0 11 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link6: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link7: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link8: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link9: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link10: Index IRQ Rtd Ref IRQs Initial Probe 0 5 N 0 5 7 9 10 11 14 15 Validation 0 5 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link11: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link12: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 5 7 9 10 11 14 15 Validation 0 11 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link13: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link14: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link15: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link16: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link17: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 5 7 9 10 11 14 15 Validation 0 255 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link18: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 5 7 9 10 11 14 15 Validation 0 10 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link19: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 5 7 9 10 11 14 15 Validation 0 11 N 0 5 7 9 10 11 14 15 After Disable 0 255 N 0 5 7 9 10 11 14 15 pci_link20: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 16 Validation 0 255 N 0 16 After Disable 0 255 N 0 16 pci_link21: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 17 Validation 0 255 N 0 17 After Disable 0 255 N 0 17 pci_link22: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 18 Validation 0 255 N 0 18 After Disable 0 255 N 0 18 pci_link23: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 19 Validation 0 255 N 0 19 After Disable 0 255 N 0 19 pci_link24: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 16 Validation 0 255 N 0 16 After Disable 0 255 N 0 16 pci_link25: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 16 Validation 0 255 N 0 16 After Disable 0 255 N 0 16 pci_link26: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 16 Validation 0 255 N 0 16 After Disable 0 255 N 0 16 pci_link27: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 16 Validation 0 255 N 0 16 After Disable 0 255 N 0 16 pci_link28: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link29: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link30: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link31: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link32: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link33: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link34: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link35: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link36: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link37: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link38: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link39: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 pci_link40: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 20 21 22 23 Validation 0 255 N 0 20 21 22 23 After Disable 0 255 N 0 20 21 22 23 acpi_hpet0: iomem 0xfeff0000-0xfeff03ff on acpi0 acpi_hpet0: vend: 0x10de rev: 0x1 num: 7 hz: 25000000 opts: leg_route Timecounter "HPET" frequency 25000000 Hz quality 900 cpu0: on acpi0 cpu0: switching to generic Cx mode est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 72a072a0600072a 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 72a072a0600072a device_attach: est1 attach returned 6 p4tcc1: on cpu1 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x10de, dev=0x03a3, revid=0xa2 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03ac, revid=0xa1 domain=0, bus=0, slot=0, func=1 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03aa, revid=0xa1 domain=0, bus=0, slot=0, func=2 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03a9, revid=0xa1 domain=0, bus=0, slot=0, func=3 class=05-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03ab, revid=0xa1 domain=0, bus=0, slot=0, func=4 class=05-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03a8, revid=0xa2 domain=0, bus=0, slot=0, func=5 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0004, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b5, revid=0xa1 domain=0, bus=0, slot=0, func=6 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b4, revid=0xa1 domain=0, bus=0, slot=0, func=7 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03ad, revid=0xa1 domain=0, bus=0, slot=1, func=0 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03ae, revid=0xa1 domain=0, bus=0, slot=1, func=1 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03af, revid=0xa1 domain=0, bus=0, slot=1, func=2 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b0, revid=0xa1 domain=0, bus=0, slot=1, func=3 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b1, revid=0xa1 domain=0, bus=0, slot=1, func=4 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b2, revid=0xa1 domain=0, bus=0, slot=1, func=5 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b3, revid=0xa1 domain=0, bus=0, slot=1, func=6 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b6, revid=0xa1 domain=0, bus=0, slot=2, func=0 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03bc, revid=0xa1 domain=0, bus=0, slot=2, func=1 class=05-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03ba, revid=0xa1 domain=0, bus=0, slot=2, func=2 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b7, revid=0xa1 domain=0, bus=0, slot=3, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D3 current D0 MSI supports 2 messages, 64 bit found-> vendor=0x10de, dev=0x03bb, revid=0xa1 domain=0, bus=0, slot=7, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D3 current D0 MSI supports 2 messages, 64 bit found-> vendor=0x10de, dev=0x0270, revid=0xa2 domain=0, bus=0, slot=9, func=0 class=05-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x0260, revid=0xa3 domain=0, bus=0, slot=10, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x0264, revid=0xa3 domain=0, bus=0, slot=10, func=1 class=0c-05-00, hdrtype=0x00, mfdev=1 cmdreg=0x0001, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[20]: type I/O Port, range 32, base 0x1c00, size 6, enabled map[24]: type I/O Port, range 32, base 0x1c80, size 6, enabled found-> vendor=0x10de, dev=0x0272, revid=0xa3 domain=0, bus=0, slot=10, func=2 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0400, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x026d, revid=0xa3 domain=0, bus=0, slot=11, func=0 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfe02f000, size 12, enabled found-> vendor=0x10de, dev=0x026e, revid=0xa3 domain=0, bus=0, slot=11, func=1 class=0c-03-20, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=b, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfe02e000, size 8, enabled found-> vendor=0x10de, dev=0x0265, revid=0xa1 domain=0, bus=0, slot=13, func=0 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) powerspec 2 supports D0 D3 current D0 map[20]: type I/O Port, range 32, base 0xfd00, size 4, enabled found-> vendor=0x10de, dev=0x0266, revid=0xa1 domain=0, bus=0, slot=14, func=0 class=01-01-85, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=10 powerspec 2 supports D0 D3 current D0 MSI supports 4 messages, 64 bit map[10]: type I/O Port, range 32, base 0x9f0, size 3, enabled map[14]: type I/O Port, range 32, base 0xbf0, size 2, enabled map[18]: type I/O Port, range 32, base 0x970, size 3, enabled map[1c]: type I/O Port, range 32, base 0xb70, size 2, enabled map[20]: type I/O Port, range 32, base 0xf800, size 4, enabled map[24]: type Memory, range 32, base 0xfe02d000, size 12, enabled pcib0: matched entry for 0.14.INTA (src \_SB_.PCI0.APSI:0) pci_link39: Picked IRQ 20 with weight 0 pcib0: slot 14 INTA routed to irq 20 via \_SB_.PCI0.APSI found-> vendor=0x10de, dev=0x0267, revid=0xa1 domain=0, bus=0, slot=15, func=0 class=01-01-85, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 4 messages, 64 bit map[10]: type I/O Port, range 32, base 0x9e0, size 3, enabled map[14]: type I/O Port, range 32, base 0xbe0, size 2, enabled map[18]: type I/O Port, range 32, base 0x960, size 3, enabled map[1c]: type I/O Port, range 32, base 0xb60, size 2, enabled map[20]: type I/O Port, range 32, base 0xf300, size 4, enabled map[24]: type Memory, range 32, base 0xfe02c000, size 12, enabled pcib0: matched entry for 0.15.INTA (src \_SB_.PCI0.APSJ:0) pci_link40: Picked IRQ 21 with weight 0 pcib0: slot 15 INTA routed to irq 21 via \_SB_.PCI0.APSJ found-> vendor=0x10de, dev=0x026f, revid=0xa2 domain=0, bus=0, slot=16, func=0 class=06-04-01, hdrtype=0x01, mfdev=1 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x02 (500 ns) found-> vendor=0x10de, dev=0x026c, revid=0xa2 domain=0, bus=0, slot=16, func=1 class=04-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x05 (1250 ns) intpin=b, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit, vector masks map[10]: type Memory, range 32, base 0xfe024000, size 14, enabled pcib0: matched entry for 0.16.INTB (src \_SB_.PCI0.AAZA:0) pci_link33: Picked IRQ 22 with weight 0 pcib0: slot 16 INTB routed to irq 22 via \_SB_.PCI0.AAZA found-> vendor=0x10de, dev=0x0269, revid=0xa3 domain=0, bus=0, slot=20, func=0 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x01 (250 ns), maxlat=0x14 (5000 ns) intpin=a, irq=5 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfe02b000, size 12, enabled map[14]: type I/O Port, range 32, base 0xf200, size 3, enabled pcib0: matched entry for 0.20.INTA (src \_SB_.PCI0.APCH:0) pci_link30: Picked IRQ 23 with weight 0 pcib0: slot 20 INTA routed to irq 23 via \_SB_.PCI0.APCH pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) pci0: at device 0.6 (no driver attached) pci0: at device 0.7 (no driver attached) pci0: at device 1.0 (no driver attached) pci0: at device 1.1 (no driver attached) pci0: at device 1.2 (no driver attached) pci0: at device 1.3 (no driver attached) pci0: at device 1.4 (no driver attached) pci0: at device 1.5 (no driver attached) pci0: at device 1.6 (no driver attached) pci0: at device 2.0 (no driver attached) pci0: at device 2.1 (no driver attached) pci0: at device 2.2 (no driver attached) pcib1: at device 3.0 on pci0 pcib1: domain 0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xe000-0xefff pcib1: memory decode 0xfa000000-0xfcffffff pcib1: prefetched decode 0xe0000000-0xefffffff pcib1: could not get PCI interrupt routing table for \_SB_.PCI0.XVRA - AE_NOT_FOUND pci1: on pcib1 pci1: domain=0, physical bus=1 found-> vendor=0x10de, dev=0x0391, revid=0xa1 domain=0, bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Memory, range 32, base 0xfa000000, size 24, enabled pcib1: requested memory range 0xfa000000-0xfaffffff: good map[14]: type Prefetchable Memory, range 64, base 0xe0000000, size 28, enabled pcib1: requested memory range 0xe0000000-0xefffffff: good map[1c]: type Memory, range 64, base 0xfb000000, size 24, enabled pcib1: requested memory range 0xfb000000-0xfbffffff: good map[24]: type I/O Port, range 32, base 0xef00, size 7, enabled pcib1: requested I/O range 0xef00-0xef7f: in range pcib0: matched entry for 0.3.INTA (src \_SB_.PCI0.APC5:0) pci_link24: Picked IRQ 16 with weight 0 pcib0: slot 3 INTA routed to irq 16 via \_SB_.PCI0.APC5 pcib1: slot 0 INTA is routed to irq 16 vgapci0: port 0xef00-0xef7f mem 0xfa000000-0xfaffffff,0xe0000000-0xefffffff,0xfb000000-0xfbffffff irq 16 at device 0.0 on pci1 pcib2: at device 7.0 on pci0 pcib2: domain 0 pcib2: secondary bus 2 pcib2: subordinate bus 2 pcib2: I/O decode 0xc000-0xcfff pcib2: memory decode 0xfdd00000-0xfddfffff pcib2: prefetched decode 0xfdc00000-0xfdcfffff pcib2: could not get PCI interrupt routing table for \_SB_.PCI0.XVRD - AE_NOT_FOUND pci2: on pcib2 pci2: domain=0, physical bus=2 found-> vendor=0x197b, dev=0x2360, revid=0x02 domain=0, bus=2, slot=0, func=0 class=01-06-01, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0xcf00, size 3, enabled pcib2: requested I/O range 0xcf00-0xcf07: in range map[14]: type I/O Port, range 32, base 0xce00, size 2, enabled pcib2: requested I/O range 0xce00-0xce03: in range map[18]: type I/O Port, range 32, base 0xcd00, size 3, enabled pcib2: requested I/O range 0xcd00-0xcd07: in range map[1c]: type I/O Port, range 32, base 0xcc00, size 2, enabled pcib2: requested I/O range 0xcc00-0xcc03: in range map[20]: type I/O Port, range 32, base 0xcb00, size 4, enabled pcib2: requested I/O range 0xcb00-0xcb0f: in range map[24]: type Memory, range 32, base 0xfddfe000, size 13, enabled pcib2: requested memory range 0xfddfe000-0xfddfffff: good pcib0: matched entry for 0.7.INTA (src \_SB_.PCI0.APC6:0) pci_link25: Picked IRQ 16 with weight 4 pcib0: slot 7 INTA routed to irq 16 via \_SB_.PCI0.APC6 pcib2: slot 0 INTA is routed to irq 16 atapci0: port 0xcf00-0xcf07,0xce00-0xce03,0xcd00-0xcd07,0xcc00-0xcc03,0xcb00-0xcb0f mem 0xfddfe000-0xfddfffff irq 16 at device 0.0 on pci2 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xcb00 ioapic0: routing intpin 16 (PCI IRQ 16) to vector 49 atapci0: [MPSAFE] atapci0: [ITHREAD] atapci0: Reserved 0x2000 bytes for rid 0x24 type 3 at 0xfddfe000 atapci0: AHCI Version 01.00 controller with 1 ports detected ata2: on atapci0 ata2: SATA connect status=00000000 ata2: ahci_reset devices=0x0 ata2: [MPSAFE] ata2: [ITHREAD] pci0: at device 9.0 (no driver attached) isab0: at device 10.0 on pci0 isa0: on isab0 pci0: at device 10.1 (no driver attached) pci0: at device 10.2 (no driver attached) ohci0: mem 0xfe02f000-0xfe02ffff at device 11.0 on pci0 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfe02f000 pcib0: matched entry for 0.11.INTA (src \_SB_.PCI0.APCF:0) pci_link28: Picked IRQ 20 with weight 1 pcib0: slot 11 INTA routed to irq 20 via \_SB_.PCI0.APCF ioapic0: routing intpin 20 (PCI IRQ 20) to vector 50 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: 8 ports with 8 removable, self powered ehci0: mem 0xfe02e000-0xfe02e0ff at device 11.1 on pci0 ehci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0xfe02e000 pcib0: matched entry for 0.11.INTB (src \_SB_.PCI0.APCL:0) pci_link36: Picked IRQ 21 with weight 1 pcib0: slot 11 INTB routed to irq 21 via \_SB_.PCI0.APCL ioapic0: routing intpin 21 (PCI IRQ 21) to vector 51 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb1: EHCI version 1.0 usb1: companion controller, 8 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: on usb1 uhub1: 8 ports with 8 removable, self powered atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfd00-0xfd0f at device 13.0 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xfd00 ata0: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci1: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ioapic0: routing intpin 14 (ISA IRQ 14) to vector 52 ata0: [MPSAFE] ata0: [ITHREAD] ata1: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci1: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=50 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=00 stat1=00 devices=0x4 ioapic0: routing intpin 15 (ISA IRQ 15) to vector 53 ata1: [MPSAFE] ata1: [ITHREAD] atapci2: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xf800-0xf80f mem 0xfe02d000-0xfe02dfff irq 20 at device 14.0 on pci0 atapci2: Reserved 0x10 bytes for rid 0x20 type 4 at 0xf800 atapci2: [MPSAFE] atapci2: [ITHREAD] atapci2: Reserved 0x1000 bytes for rid 0x24 type 3 at 0xfe02d000 ata3: on atapci2 atapci2: Reserved 0x8 bytes for rid 0x10 type 4 at 0x9f0 atapci2: Reserved 0x4 bytes for rid 0x14 type 4 at 0xbf0 ata3: SATA connect time=0ms ata3: reset tp1 mask=01 ostat0=50 ostat1=00 ata3: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata3: reset tp2 stat0=50 stat1=00 devices=0x1 ata3: [MPSAFE] ata3: [ITHREAD] ata4: on atapci2 atapci2: Reserved 0x8 bytes for rid 0x18 type 4 at 0x970 atapci2: Reserved 0x4 bytes for rid 0x1c type 4 at 0xb70 ata4: SATA connect status=00000000 ata4: [MPSAFE] ata4: [ITHREAD] atapci3: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xf300-0xf30f mem 0xfe02c000-0xfe02cfff irq 21 at device 15.0 on pci0 atapci3: Reserved 0x10 bytes for rid 0x20 type 4 at 0xf300 atapci3: [MPSAFE] atapci3: [ITHREAD] atapci3: Reserved 0x1000 bytes for rid 0x24 type 3 at 0xfe02c000 ata5: on atapci3 atapci3: Reserved 0x8 bytes for rid 0x10 type 4 at 0x9e0 atapci3: Reserved 0x4 bytes for rid 0x14 type 4 at 0xbe0 ata5: SATA connect status=00000000 ata5: [MPSAFE] ata5: [ITHREAD] ata6: on atapci3 atapci3: Reserved 0x8 bytes for rid 0x18 type 4 at 0x960 atapci3: Reserved 0x4 bytes for rid 0x1c type 4 at 0xb60 ata6: SATA connect status=00000000 ata6: [MPSAFE] ata6: [ITHREAD] pcib3: at device 16.0 on pci0 pcib3: domain 0 pcib3: secondary bus 3 pcib3: subordinate bus 3 pcib3: I/O decode 0xd000-0xdfff pcib3: memory decode 0xfdf00000-0xfdffffff pcib3: prefetched decode 0xfde00000-0xfdefffff pcib3: Subtractively decoded bridge. pci3: on pcib3 pci3: domain=0, physical bus=3 found-> vendor=0x1106, dev=0x3044, revid=0xc0 domain=0, bus=3, slot=8, func=0 class=0c-00-10, hdrtype=0x00, mfdev=0 cmdreg=0x0017, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x20 (8000 ns) intpin=a, irq=255 powerspec 2 supports D0 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfdfff000, size 11, enabled pcib3: requested memory range 0xfdfff000-0xfdfff7ff: good map[14]: type I/O Port, range 32, base 0xdf00, size 7, enabled pcib3: requested I/O range 0xdf00-0xdf7f: in range fwohci0: port 0xdf00-0xdf7f mem 0xfdfff000-0xfdfff7ff at device 8.0 on pci3 fwohci0: Reserved 0x800 bytes for rid 0x10 type 3 at 0xfdfff000 pcib3: matched entry for 3.8.INTA (src \_SB_.PCI0.APC3:0) pci_link22: Picked IRQ 18 with weight 0 pcib3: slot 8 INTA routed to irq 18 via \_SB_.PCI0.APC3 ioapic0: routing intpin 18 (PCI IRQ 18) to vector 54 fwohci0: [MPSAFE] fwohci0: [FILTER] fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:11:d8:00:01:68:23:10 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:11:d8:68:23:10 fwe0: bpf attached fwe0: Ethernet address: 02:11:d8:68:23:10 fwip0: on firewire0 fwip0: bpf attached fwip0: Firewire address: 00:11:d8:00:01:68:23:10 @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0xb825e0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode pci0: at device 16.1 (no driver attached) nfe0: port 0xf200-0xf207 mem 0xfe02b000-0xfe02bfff irq 23 at device 20.0 on pci0 nfe0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfe02b000 miibus0: on nfe0 e1000phy0: PHY 1 on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto nfe0: bpf attached nfe0: Ethernet address: 00:1d:60:0c:17:71 ioapic0: routing intpin 23 (PCI IRQ 23) to vector 55 nfe0: [MPSAFE] nfe0: [FILTER] acpi_tz0: on acpi0 sio0: irq maps: 0xcc21 0xcc31 0xcc21 0xcc21 sio0: irq maps: 0xcc21 0xcc31 0xcc21 0xcc21 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console ioapic0: routing intpin 4 (ISA IRQ 4) to vector 56 sio0: [FILTER] psmcpnp0: irq 12 on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 ioapic0: routing intpin 1 (ISA IRQ 1) to vector 57 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 07 03 c8 psm: status 07 03 c8 psm: status 07 03 c8 psm: data c8 c2 38 psm: status 00 02 64 psm0: irq 12 on atkbdc0 ioapic0: routing intpin 12 (ISA IRQ 12) to vector 58 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model MouseMan+, device ID 0-38, 3 buttons psm0: config:00000000, flags:00000008, packet size:3 psm0: syncmask:08, syncbits:00 unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff ex_isa_identify() ahc_isa_probe 0: ioport 0xc00 alloc failed ahc_isa_probe 1: ioport 0x1c00 alloc failed ahc_isa_probe 12: ioport 0xcc00 alloc failed ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it atkbdc: atkbdc0 already exists; skipping it sio: sio0 already exists; skipping it pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices pmtimer0 on isa0 orm0: at iomem 0xd0000-0xd7fff,0xd8000-0xd9fff pnpid ORM0000 on isa0 adv0: not probed (disabled) aha0: not probed (disabled) aic0: not probed (disabled) bt0: not probed (disabled) cs0: not probed (disabled) ed0: not probed (disabled) fdc0 failed to probe at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fe0: not probed (disabled) ie0: not probed (disabled) le0: not probed (disabled) ppc0: parallel port found at 0x378 ppc0: using extended I/O port range ppc0: EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 ppi0: on ppbus0 plip0: on ppbus0 plip0: bpf attached lpt0: on ppbus0 lpt0: Interrupt-driven port ioapic0: routing intpin 7 (ISA IRQ 7) to vector 59 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd1, terminal emulator: sc (syscons terminal) sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: irq maps: 0xcc21 0xcc21 0xcc21 0xcc21 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) sn0: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 vt0: not probed (disabled) isa_probe_children: probing PnP devices Device configuration finished. Reducing kern.maxvnodes 133530 -> 100000 procfs registered lapic: Divisor 2, Frequency 166667996 hz Timecounter "TSC" frfirewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) equency 2333351867 Hz quality -100 Timecounters tick every 1.000 msec lo0: bpf attached rr232x: no controller detected. md0: Preloaded image 9437184 bytes at 0xc0d237e0 ata0: reiniting channel .. ata0: reset tp1 mask=03 ostat0=58 ostat1=00 ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ata0: reinit done .. ata0: reiniting channel .. ata0: reset tp1 mask=03 ostat0=58 ostat1=00 ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ata0: reinit done .. ata1: reiniting channel .. ata1: reset tp1 mask=03 ostat0=58 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=00 stat1=00 devices=0x4 ata1: reinit done .. ata1: reiniting channel .. ata1: reset tp1 mask=03 ostat0=58 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=00 stat1=00 devices=0x4 ata1: reinit done .. (probe3:sbp0:0:3:0): error 22 (probe3:sbp0:0:3:0): Unretryable Error (probe4:sbp0:0:4:0): error 22 (probe4:sbp0:0:4:0): Unretryable Error (probe0:sbp0:0:0:0): error 22 (probe0:sbp0:0:0:0): Unretryable Error (probe1:sbp0:0:1:0): error 22 (probe1:sbp0:0:1:0): Unretryable Error (probe2:sbp0:0:2:0): error 22 (probe2:sbp0:0:2:0): Unretryable Error (probe5:sbp0:0:5:0): error 22 (probe5:sbp0:0:5:0): Unretryable Error (probe6:sbp0:0:6:0): error 22 (probe6:sbp0:0:6:0): Unretryable Error ata3: reiniting channel .. ata3: SATA connect time=0ms ata3: reset tp1 mask=01 ostat0=58 ostat1=00 ata3: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata3: reset tp2 stat0=50 stat1=00 devices=0x1 ata3: reinit done .. ata3: reiniting channel .. ata3: SATA connect time=0ms ata3: reset tp1 mask=01 ostat0=58 ostat1=00 ata3: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata3: reset tp2 stat0=50 stat1=00 devices=0x1 ata3: reinit done .. ATA PseudoRAID loaded SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x01000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 ioapic0: Assigning ISA IRQ 1 to local APIC 0 ioapic0: Assigning ISA IRQ 4 to local APIC 1 ioapic0: Assigning ISA IRQ 7 to local APIC 0 ioapic0: Assigning ISA IRQ 9 to local APIC 1 ioapic0: Assigning ISA IRQ 12 to local APIC 0 ioapic0: Assigning ISA IRQ 14 to local APIC 1 ioapic0: Assigning ISA IRQ 15 to local APIC 0 ioapic0: Assigning PCI IRQ 16 to local APIC 1 ioapic0: Assigning PCI IRQ 18 to local APIC 0 ioapic0: Assigning PCI IRQ 20 to local APIC 1 ioapic0: Assigning PCI IRQ 21 to local APIC 0 ioapic0: Assigning PCI IRQ 23 to local APIC 1 WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/ad0s1a Trying to mount root from ufs:/dev/md0 start_init: trying /sbin/init --Boundary-01=_N2hKHZAYVDEsOTi Content-Type: text/plain; charset="us-ascii"; name="boot_v.noacpi" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="boot_v.noacpi" GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb SMAP type=01 base=0000000000000000 len=000000000009f000 SMAP type=02 base=00000000000f0000 len=0000000000010000 SMAP type=02 base=00000000fec00000 len=0000000001400000 SMAP type=02 base=00000000f0000000 len=0000000002000000 SMAP type=03 base=000000007fef3000 len=000000000000d000 SMAP type=04 base=000000007fef0000 len=0000000000003000 SMAP type=02 base=000000000009f000 len=0000000000001000 SMAP type=01 base=0000000000100000 len=000000007fdf0000 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-BETA1 #5: Thu Nov 1 18:21:33 CET 2007 mlaier@c2d.laiers.local:/usr/src/sys/i386/compile/GENERIC WARNING: WITNESS option enabled, expect reduced performance. Preloaded elf kernel "/boot/kernel/kernel" at 0xc1625000. Preloaded mfs_root "/boot/mfsroot" at 0xc1625180. Calibrating clock(s) ... i8254 clock: 1193185 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2333352679 Hz CPU: Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz (2333.35-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6fb Stepping = 11 Features=0xbfebfbff Features2=0xe3fd AMD Features=0x20100000 AMD Features2=0x1 Cores per package: 2 Instruction TLB: 4 KB Pages, 4-way set associative, 128 entries 1st-level instruction cache: 32 KB, 8-way set associative, 64 byte line size 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size L2 cache: 4096 kbytes, 16-way associative, 64 bytes/line real memory = 2146369536 (2046 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009dfff, 643072 bytes (157 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000001828000 - 0x000000007daa4fff, 2082983936 bytes (508541 pages) avail memory = 2082459648 (1985 MB) MP Configuration Table version 1.4 found at 0xc00f1400 APIC: Using the MPTable enumerator. SMP: Added CPU 0 (BSP) SMP: Added CPU 1 (AP) MPTable: INTR: Adding local APIC 1 as a target FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 bios32: Found BIOS32 Service Directory header at 0xc00fb430 bios32: Entry = 0xfba10 (c00fba10) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0xba40 pnpbios: Found PnP BIOS data at 0xc00fc5e0 pnpbios: Entry = f0000:c610 Rev = 1.0 Other BIOS signatures found: ioapic0: Changing APIC ID to 4 ioapic0: Assuming intbase of 0 ioapic0: Routing external 8259A's -> intpin 0 ioapic0: intpin 10 bus PCI ioapic0: intpin 10 trigger: level ioapic0: intpin 10 polarity: low ioapic0: intpin 11 bus PCI ioapic0: intpin 11 trigger: level ioapic0: intpin 11 polarity: low ioapic0: intpin 5 bus PCI ioapic0: intpin 5 trigger: level ioapic0: intpin 5 polarity: low ioapic0: Routing IRQ 0 -> intpin 2 lapic: Routing ExtINT -> LINT0 lapic: Routing NMI -> LINT1 ioapic0 irqs 0-23 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 ath_rate: version 1.2 wlan_amrr: wlan: <802.11 Link Layer> null: random: nfslock: pseudo-device kbd: new array size 4 kbd1 at kbdmux0 mem: Pentium Pro MTRR support enabled io: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) rr232x: RocketRAID 232x controller driver v1.02 (Nov 1 2007 18:21:22) npx0: INT 16 interface cpu0 on motherboard est0: on cpu0 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 72a072a0600072a device_attach: est0 attach returned 6 p4tcc0: on cpu0 cpu1 on motherboard est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 72a072a0600072a device_attach: est1 attach returned 6 p4tcc1: on cpu1 pci_open(1): mode 1 addr port (0x0cf8) is 0x80006804 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=03a310de) pcibios: BIOS version 3.00 pcib0: pcibus 0 on motherboard pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x10de, dev=0x03a3, revid=0xa2 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03ac, revid=0xa1 domain=0, bus=0, slot=0, func=1 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03aa, revid=0xa1 domain=0, bus=0, slot=0, func=2 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03a9, revid=0xa1 domain=0, bus=0, slot=0, func=3 class=05-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03ab, revid=0xa1 domain=0, bus=0, slot=0, func=4 class=05-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03a8, revid=0xa2 domain=0, bus=0, slot=0, func=5 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0004, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b5, revid=0xa1 domain=0, bus=0, slot=0, func=6 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b4, revid=0xa1 domain=0, bus=0, slot=0, func=7 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03ad, revid=0xa1 domain=0, bus=0, slot=1, func=0 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03ae, revid=0xa1 domain=0, bus=0, slot=1, func=1 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03af, revid=0xa1 domain=0, bus=0, slot=1, func=2 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b0, revid=0xa1 domain=0, bus=0, slot=1, func=3 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b1, revid=0xa1 domain=0, bus=0, slot=1, func=4 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b2, revid=0xa1 domain=0, bus=0, slot=1, func=5 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b3, revid=0xa1 domain=0, bus=0, slot=1, func=6 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b6, revid=0xa1 domain=0, bus=0, slot=2, func=0 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03bc, revid=0xa1 domain=0, bus=0, slot=2, func=1 class=05-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03ba, revid=0xa1 domain=0, bus=0, slot=2, func=2 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0020, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x03b7, revid=0xa1 domain=0, bus=0, slot=3, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D3 current D0 MSI supports 2 messages, 64 bit found-> vendor=0x10de, dev=0x03bb, revid=0xa1 domain=0, bus=0, slot=7, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D3 current D0 MSI supports 2 messages, 64 bit found-> vendor=0x10de, dev=0x0270, revid=0xa2 domain=0, bus=0, slot=9, func=0 class=05-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x0260, revid=0xa3 domain=0, bus=0, slot=10, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x0264, revid=0xa3 domain=0, bus=0, slot=10, func=1 class=0c-05-00, hdrtype=0x00, mfdev=1 cmdreg=0x0001, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 2 supports D0 D3 current D0 map[20]: type I/O Port, range 32, base 0x1c00, size 6, enabled map[24]: type I/O Port, range 32, base 0x1c80, size 6, enabled pcib0: slot 10 INTA routed to irq 10 found-> vendor=0x10de, dev=0x0272, revid=0xa3 domain=0, bus=0, slot=10, func=2 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0400, statreg=0x00a0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x10de, dev=0x026d, revid=0xa3 domain=0, bus=0, slot=11, func=0 class=0c-03-10, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfe02f000, size 12, enabled pcib0: slot 11 INTA routed to irq 11 found-> vendor=0x10de, dev=0x026e, revid=0xa3 domain=0, bus=0, slot=11, func=1 class=0c-03-20, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=b, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfe02e000, size 8, enabled pcib0: slot 11 INTB routed to irq 10 found-> vendor=0x10de, dev=0x0265, revid=0xa1 domain=0, bus=0, slot=13, func=0 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) powerspec 2 supports D0 D3 current D0 map[20]: type I/O Port, range 32, base 0xfd00, size 4, enabled found-> vendor=0x10de, dev=0x0266, revid=0xa1 domain=0, bus=0, slot=14, func=0 class=01-01-85, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 4 messages, 64 bit map[10]: type I/O Port, range 32, base 0x9f0, size 3, enabled map[14]: type I/O Port, range 32, base 0xbf0, size 2, enabled map[18]: type I/O Port, range 32, base 0x970, size 3, enabled map[1c]: type I/O Port, range 32, base 0xb70, size 2, enabled map[20]: type I/O Port, range 32, base 0xf800, size 4, enabled map[24]: type Memory, range 32, base 0xfe02d000, size 12, enabled pcib0: slot 14 INTA routed to irq 11 found-> vendor=0x10de, dev=0x0267, revid=0xa1 domain=0, bus=0, slot=15, func=0 class=01-01-85, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x03 (750 ns), maxlat=0x01 (250 ns) intpin=a, irq=10 powerspec 2 supports D0 D3 current D0 MSI supports 4 messages, 64 bit map[10]: type I/O Port, range 32, base 0x9e0, size 3, enabled map[14]: type I/O Port, range 32, base 0xbe0, size 2, enabled map[18]: type I/O Port, range 32, base 0x960, size 3, enabled map[1c]: type I/O Port, range 32, base 0xb60, size 2, enabled map[20]: type I/O Port, range 32, base 0xf300, size 4, enabled map[24]: type Memory, range 32, base 0xfe02c000, size 12, enabled pcib0: slot 15 INTA routed to irq 10 found-> vendor=0x10de, dev=0x026f, revid=0xa2 domain=0, bus=0, slot=16, func=0 class=06-04-01, hdrtype=0x01, mfdev=1 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x02 (500 ns) found-> vendor=0x10de, dev=0x026c, revid=0xa2 domain=0, bus=0, slot=16, func=1 class=04-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x05 (1250 ns) intpin=b, irq=11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit, vector masks map[10]: type Memory, range 32, base 0xfe024000, size 14, enabled pcib0: slot 16 INTB routed to irq 11 found-> vendor=0x10de, dev=0x0269, revid=0xa3 domain=0, bus=0, slot=20, func=0 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x00b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x01 (250 ns), maxlat=0x14 (5000 ns) intpin=a, irq=5 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfe02b000, size 12, enabled map[14]: type I/O Port, range 32, base 0xf200, size 3, enabled pcib0: slot 20 INTA routed to irq 5 pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) pci0: at device 0.6 (no driver attached) pci0: at device 0.7 (no driver attached) pci0: at device 1.0 (no driver attached) pci0: at device 1.1 (no driver attached) pci0: at device 1.2 (no driver attached) pci0: at device 1.3 (no driver attached) pci0: at device 1.4 (no driver attached) pci0: at device 1.5 (no driver attached) pci0: at device 1.6 (no driver attached) pci0: at device 2.0 (no driver attached) pci0: at device 2.1 (no driver attached) pci0: at device 2.2 (no driver attached) pcib1: at device 3.0 on pci0 pcib1: domain 0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xe000-0xefff pcib1: memory decode 0xfa000000-0xfcffffff pcib1: prefetched decode 0xe0000000-0xefffffff pci1: on pcib1 pci1: domain=0, physical bus=1 found-> vendor=0x10de, dev=0x0391, revid=0xa1 domain=0, bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Memory, range 32, base 0xfa000000, size 24, enabled pcib1: requested memory range 0xfa000000-0xfaffffff: good map[14]: type Prefetchable Memory, range 64, base 0xe0000000, size 28, enabled pcib1: requested memory range 0xe0000000-0xefffffff: good map[1c]: type Memory, range 64, base 0xfb000000, size 24, enabled pcib1: requested memory range 0xfb000000-0xfbffffff: good map[24]: type I/O Port, range 32, base 0xef00, size 7, enabled pcib1: requested I/O range 0xef00-0xef7f: in range pcib1: slot 0 INTA routed to irq 10 vgapci0: port 0xef00-0xef7f mem 0xfa000000-0xfaffffff,0xe0000000-0xefffffff,0xfb000000-0xfbffffff irq 10 at device 0.0 on pci1 pcib2: at device 7.0 on pci0 pcib2: domain 0 pcib2: secondary bus 2 pcib2: subordinate bus 2 pcib2: I/O decode 0xc000-0xcfff pcib2: memory decode 0xfdd00000-0xfddfffff pcib2: prefetched decode 0xfdc00000-0xfdcfffff pci2: on pcib2 pci2: domain=0, physical bus=2 found-> vendor=0x197b, dev=0x2360, revid=0x02 domain=0, bus=2, slot=0, func=0 class=01-06-01, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0xcf00, size 3, enabled pcib2: requested I/O range 0xcf00-0xcf07: in range map[14]: type I/O Port, range 32, base 0xce00, size 2, enabled pcib2: requested I/O range 0xce00-0xce03: in range map[18]: type I/O Port, range 32, base 0xcd00, size 3, enabled pcib2: requested I/O range 0xcd00-0xcd07: in range map[1c]: type I/O Port, range 32, base 0xcc00, size 2, enabled pcib2: requested I/O range 0xcc00-0xcc03: in range map[20]: type I/O Port, range 32, base 0xcb00, size 4, enabled pcib2: requested I/O range 0xcb00-0xcb0f: in range map[24]: type Memory, range 32, base 0xfddfe000, size 13, enabled pcib2: requested memory range 0xfddfe000-0xfddfffff: good pcib2: slot 0 INTA routed to irq 11 atapci0: port 0xcf00-0xcf07,0xce00-0xce03,0xcd00-0xcd07,0xcc00-0xcc03,0xcb00-0xcb0f mem 0xfddfe000-0xfddfffff irq 11 at device 0.0 on pci2 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xcb00 ioapic0: routing intpin 11 (PCI IRQ 11) to vector 48 atapci0: [MPSAFE] atapci0: [ITHREAD] atapci0: Reserved 0x2000 bytes for rid 0x24 type 3 at 0xfddfe000 atapci0: AHCI Version 01.00 controller with 1 ports detected ata2: on atapci0 ata2: SATA connect status=00000000 ata2: ahci_reset devices=0x0 ata2: [MPSAFE] ata2: [ITHREAD] pci0: at device 9.0 (no driver attached) isab0: at device 10.0 on pci0 isa0: on isab0 pci0: at device 10.1 (no driver attached) pci0: at device 10.2 (no driver attached) ohci0: mem 0xfe02f000-0xfe02ffff irq 11 at device 11.0 on pci0 ohci0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfe02f000 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: 8 ports with 8 removable, self powered ehci0: mem 0xfe02e000-0xfe02e0ff irq 10 at device 11.1 on pci0 ehci0: Reserved 0x100 bytes for rid 0x10 type 3 at 0xfe02e000 ioapic0: routing intpin 10 (PCI IRQ 10) to vector 49 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb1: waiting for BIOS to give up control usb1: EHCI version 1.0 usb1: companion controller, 8 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: on usb1 uhub1: 8 ports with 8 removable, self powered atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfd00-0xfd0f at device 13.0 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xfd00 ata0: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci1: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ioapic0: routing intpin 14 (ISA IRQ 14) to vector 50 ata0: [MPSAFE] ata0: [ITHREAD] ata1: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci1: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=50 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=00 stat1=00 devices=0x4 ioapic0: routing intpin 15 (ISA IRQ 15) to vector 51 ata1: [MPSAFE] ata1: [ITHREAD] atapci2: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xf800-0xf80f mem 0xfe02d000-0xfe02dfff irq 11 at device 14.0 on pci0 atapci2: Reserved 0x10 bytes for rid 0x20 type 4 at 0xf800 atapci2: [MPSAFE] atapci2: [ITHREAD] atapci2: Reserved 0x1000 bytes for rid 0x24 type 3 at 0xfe02d000 ata3: on atapci2 atapci2: Reserved 0x8 bytes for rid 0x10 type 4 at 0x9f0 atapci2: Reserved 0x4 bytes for rid 0x14 type 4 at 0xbf0 ata3: SATA connect time=0ms ata3: reset tp1 mask=01 ostat0=50 ostat1=00 ata3: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata3: reset tp2 stat0=50 stat1=00 devices=0x1 ata3: [MPSAFE] ata3: [ITHREAD] ata4: on atapci2 atapci2: Reserved 0x8 bytes for rid 0x18 type 4 at 0x970 atapci2: Reserved 0x4 bytes for rid 0x1c type 4 at 0xb70 ata4: SATA connect status=00000000 ata4: [MPSAFE] ata4: [ITHREAD] atapci3: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xf300-0xf30f mem 0xfe02c000-0xfe02cfff irq 10 at device 15.0 on pci0 atapci3: Reserved 0x10 bytes for rid 0x20 type 4 at 0xf300 atapci3: [MPSAFE] atapci3: [ITHREAD] atapci3: Reserved 0x1000 bytes for rid 0x24 type 3 at 0xfe02c000 ata5: on atapci3 atapci3: Reserved 0x8 bytes for rid 0x10 type 4 at 0x9e0 atapci3: Reserved 0x4 bytes for rid 0x14 type 4 at 0xbe0 ata5: SATA connect status=00000000 ata5: [MPSAFE] ata5: [ITHREAD] ata6: on atapci3 atapci3: Reserved 0x8 bytes for rid 0x18 type 4 at 0x960 atapci3: Reserved 0x4 bytes for rid 0x1c type 4 at 0xb60 ata6: SATA connect status=00000000 ata6: [MPSAFE] ata6: [ITHREAD] pcib3: at device 16.0 on pci0 pcib3: domain 0 pcib3: secondary bus 3 pcib3: subordinate bus 3 pcib3: I/O decode 0xd000-0xdfff pcib3: memory decode 0xfdf00000-0xfdffffff pcib3: prefetched decode 0xfde00000-0xfdefffff pcib3: Subtractively decoded bridge. pci3: on pcib3 pci3: domain=0, physical bus=3 found-> vendor=0x1106, dev=0x3044, revid=0xc0 domain=0, bus=3, slot=8, func=0 class=0c-00-10, hdrtype=0x00, mfdev=0 cmdreg=0x0017, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x20 (8000 ns) intpin=a, irq=11 powerspec 2 supports D0 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfdfff000, size 11, enabled pcib3: requested memory range 0xfdfff000-0xfdfff7ff: good map[14]: type I/O Port, range 32, base 0xdf00, size 7, enabled pcib3: requested I/O range 0xdf00-0xdf7f: in range pcib3: slot 8 INTA routed to irq 11 fwohci0: port 0xdf00-0xdf7f mem 0xfdfff000-0xfdfff7ff irq 11 at device 8.0 on pci3 fwohci0: Reserved 0x800 bytes for rid 0x10 type 3 at 0xfdfff000 fwohci0: [MPSAFE] fwohci0: [FILTER] fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:11:d8:00:01:68:23:10 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0xb825e0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:11:d8:68:23:10 fwe0: bpf attached fwe0: Ethernet address: 02:11:d8:68:23:10 fwip0: on firewire0 fwip0: bpf attached fwip0: Firewire address: 00:11:d8:00:01:68:23:10 @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode pci0: at device 16.1 (no driver attached) nfe0: port 0xf200-0xf207 mem 0xfe02b000-0xfe02bfff irq 5 at device 20.0 on pci0 nfe0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfe02b000 miibus0: on nfe0 e1000phy0: PHY 1 on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto nfe0: bpf attached nfe0: Ethernet address: 00:1d:60:0c:17:71 ioapic0: routing intpin 5 (PCI IRQ 5) to vector 52 nfe0: [MPSAFE] nfe0: [FILTER] unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff ex_isa_identify() ahc_isa_probe 0: ioport 0xc00 alloc failed ahc_isa_probe 1: ioport 0x1c00 alloc failed ahc_isa_probe 12: ioport 0xcc00 alloc failed ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete pnpbios: 13 devices, largest 92 bytes PNP0200: adding dma mask 0x10 PNP0200: adding io range 0-0xf, size=0x10, align=0 PNP0200: adding io range 0x81-0x83, size=0x3, align=0 PNP0200: adding io range 0x87-0x87, size=0x1, align=0 PNP0200: adding io range 0x89-0x8b, size=0x3, align=0 PNP0200: adding io range 0x8f-0x91, size=0x3, align=0 PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0 pnpbios: handle 1 device ID PNP0200 (0002d041) PNP0100: adding irq mask 0x1 PNP0100: adding io range 0x40-0x43, size=0x4, align=0 pnpbios: handle 2 device ID PNP0100 (0001d041) PNP0b00: adding irq mask 0x100 PNP0b00: adding io range 0x70-0x71, size=0x2, align=0 pnpbios: handle 3 device ID PNP0b00 (000bd041) PNP0303: adding irq mask 0x2 PNP0303: adding io range 0x60-0x60, size=0x1, align=0 PNP0303: adding io range 0x64-0x64, size=0x1, align=0 pnpbios: handle 4 device ID PNP0303 (0303d041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0 pnpbios: handle 5 device ID PNP0800 (0008d041) PNP0c04: adding irq mask 0x2000 PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0 pnpbios: handle 6 device ID PNP0c04 (040cd041) PNP0c01: adding fixed memory32 range 0-0x9ffff, size=0xa0000 PNP0c01: adding fixed memory32 range 0xfffe0000-0xffffffff, size=0x20000 PNP0c01: adding fixed memory32 range 0xfec00000-0xfec0ffff, size=0x10000 PNP0c01: adding fixed memory32 range 0xfee00000-0xfee0ffff, size=0x10000 PNP0c01: adding fixed memory32 range 0x100000-0xffffff, size=0xf00000 pnpbios: handle 7 device ID PNP0c01 (010cd041) PNP0c02: adding fixed memory32 range 0xf0000-0xf3fff, size=0x4000 PNP0c02: adding fixed memory32 range 0xf4000-0xf7fff, size=0x4000 PNP0c02: adding fixed memory32 range 0xf8000-0xfffff, size=0x8000 PNP0c02: adding fixed memory32 range 0xda000-0xdbfff, size=0x2000 pnpbios: handle 8 device ID PNP0c02 (020cd041) PNP0a03: adding io range 0x290-0x29f, size=0x10, align=0 PNP0a03: adding io range 0x4d0-0x4d1, size=0x2, align=0 PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0 pnpbios: handle 9 device ID PNP0a03 (030ad041) PNP0f13: adding irq mask 0x1000 pnpbios: handle 10 device ID PNP0f13 (130fd041) PNP0501: adding irq mask 0x10 PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0 pnpbios: handle 11 device ID PNP0501 (0105d041) PNP0400: adding irq mask 0x80 PNP0400: adding io range 0x378-0x37f, size=0x8, align=0 PNP0400: adding io range 0x778-0x77f, size=0x8, align=0 pnpbios: handle 13 device ID PNP0400 (0004d041) sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices pmtimer0 on isa0 orm0: at iomem 0xd0000-0xd7fff,0xd8000-0xd9fff pnpid ORM0000 on isa0 adv0: not probed (disabled) aha0: not probed (disabled) aic0: not probed (disabled) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 ioapic0: routing intpin 1 (ISA IRQ 1) to vector 53 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 07 03 c8 psm: status 07 03 c8 psm: status 07 03 c8 psm: data c8 c2 38 psm: status 00 02 64 psm0: irq 12 on atkbdc0 ioapic0: routing intpin 12 (ISA IRQ 12) to vector 54 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model MouseMan+, device ID 0-38, 3 buttons psm0: config:00000000, flags:00000008, packet size:3 psm0: syncmask:08, syncbits:00 bt0: not probed (disabled) cs0: not probed (disabled) ed0: not probed (disabled) fdc0 failed to probe at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fe0: not probed (disabled) ie0: not probed (disabled) le0: not probed (disabled) ppc0: parallel port found at 0x378 ppc0: using extended I/O port range ppc0: EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 plip0: bpf attached lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ioapic0: routing intpin 7 (ISA IRQ 7) to vector 55 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd1, terminal emulator: sc (syscons terminal) sio0: irq maps: 0xc001 0xc011 0xc001 0xc001 sio0: irq maps: 0xc001 0xc011 0xc001 0xc001 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console ioapic0: routing intpin 4 (ISA IRQ 4) to vector 56 sio0: [FILTER] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: irq maps: 0xc001 0xc001 0xc001 0xc001 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) sn0: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 vt0: not probed (disabled) isa_probe_children: probing PnP devices unknown: can't assign resources (port) unknown: at port 0x60 pnpid PNP0303 on isa0 unknown: failed to probe at port 0x61 pnpid PNP0800 on isa0 unknown: can't assign resources (memory) unknown: at iomem 0-0x9ffff pnpid PNP0c01 on isa0 unknown: can't assign resources (irq) unknown: at irq 12 pnpid PNP0f13 on isa0 unknown: can't assign resources (port) unknown: at port 0x3f8-0x3ff pnpid PNP0501 on isa0 unknown: can't assign resources (port) unknown: at port 0x378-0x37f pnpid PNP0400 on isa0 Device configuration finished. Reducing kern.maxvnodes 133530 -> 100000 procfs registered lapic: Divisor 2, Frequency 166668054 hz Timecounter "TSC" frfirewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) equency 2333352679 Hz quality -100 Timecounters tick every 1.000 msec lo0: bpf attached rr232x: no controller detected. md0: Preloaded image 9437184 bytes at 0xc0d237e0 ata0: reiniting channel .. ata0: reset tp1 mask=03 ostat0=58 ostat1=00 ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ata0: reinit done .. ata0: reiniting channel .. ata0: reset tp1 mask=03 ostat0=58 ostat1=00 ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ata0: reinit done .. ata1: reiniting channel .. ata1: reset tp1 mask=03 ostat0=58 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=00 stat1=00 devices=0x4 ata1: reinit done .. ata1: reiniting channel .. ata1: reset tp1 mask=03 ostat0=58 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=00 stat1=00 devices=0x4 ata1: reinit done .. ata3: reiniting channel .. ata3: SATA connect time=0ms ata3: reset tp1 mask=01 ostat0=58 ostat1=00 ata3: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata3: reset tp2 stat0=50 stat1=00 devices=0x1 ata3: reinit done .. ata3: reiniting channel .. ata3: SATA connect time=0ms ata3: reset tp1 mask=01 ostat0=58 ostat1=00 ata3: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata3: reset tp2 stat0=50 stat1=00 devices=0x1 ata3: reinit done .. (probe0:sbp0:0:0:0): error 22 (probe0:sbp0:0:0:0): Unretryable Error (probe1:sbp0:0:1:0): error 22 (probe1:sbp0:0:1:0): Unretryable Error (probe2:sbp0:0:2:0): error 22 (probe2:sbp0:0:2:0): Unretryable Error (probe3:sbp0:0:3:0): error 22 (probe3:sbp0:0:3:0): Unretryable Error (probe4:sbp0:0:4:0): error 22 (probe4:sbp0:0:4:0): Unretryable Error (probe5:sbp0:0:5:0): error 22 (probe5:sbp0:0:5:0): Unretryable Error (probe6:sbp0:0:6:0): error 22 (probe6:sbp0:0:6:0): Unretryable Error ATA PseudoRAID loaded SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x01000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 ioapic0: Assigning ISA IRQ 1 to local APIC 0 ioapic0: Assigning ISA IRQ 4 to local APIC 1 ioapic0: Assigning PCI IRQ 5 to local APIC 0 ioapic0: Assigning ISA IRQ 7 to local APIC 1 ioapic0: Assigning PCI IRQ 10 to local APIC 0 ioapic0: Assigning PCI IRQ 11 to local APIC 1 ioapic0: Assigning ISA IRQ 12 to local APIC 0 ioapic0: Assigning ISA IRQ 14 to local APIC 1 ioapic0: Assigning ISA IRQ 15 to local APIC 0 WARNING: WITNESS option enabled, expect reduced performance. Trying to mount root from ufs:/dev/ad0s1a Trying to mount root from ufs:/dev/md0 start_init: trying /sbin/init --Boundary-01=_N2hKHZAYVDEsOTi-- --nextPart3828379.rAXiEC845h Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHKh2SXyyEoT62BG0RAlTBAJ0QiTXti9rqxJ+gmfPb0bRvxVPSTgCfdkk2 ZUBZ67JOsc9J0AZpUc89F+0= =F5MX -----END PGP SIGNATURE----- --nextPart3828379.rAXiEC845h-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 20:06:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F98F16A543 for ; Thu, 1 Nov 2007 20:06:18 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from optimus.centralmiss.com (ns.centralmiss.com [206.156.254.79]) by mx1.freebsd.org (Postfix) with ESMTP id 4067813C4B7 for ; Thu, 1 Nov 2007 20:06:15 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by optimus.centralmiss.com (Postfix) with ESMTP id 5FA5D28BB0; Thu, 1 Nov 2007 14:05:06 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id E104261C43; Thu, 1 Nov 2007 14:05:05 -0500 (CDT) Date: Thu, 1 Nov 2007 14:05:05 -0500 From: "Matthew D. Fuller" To: Thierry Herbelot Message-ID: <20071101190505.GJ1580@over-yonder.net> References: <200711011509.46094.thierry@herbelot.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200711011509.46094.thierry@herbelot.com> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.16-fullermd.4 (2007-06-09) Cc: freebsd-current@freebsd.org Subject: Re: regression with gmirror, Promise SATA and 7.0 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 20:06:18 -0000 On Thu, Nov 01, 2007 at 03:09:45PM +0100 I heard the voice of Thierry Herbelot, and lo! it spake thus: > > Thus, it seems that the combination of this Promise controller and > the SATA disks has issues (there was a thread about Promise > controllers and ZFS, but with no clear conclusion). See (and probably a number of other posts). This has been an issue for me with -CURRENT (and so now RELENG_7) early this year. This box is still running RELENG_6 (and I'm writing this mail on it), and will take a pounding on the drives all day long without the slightest tic. But put -CURRENT/RELENG_7 on it, and it's lucky to live long enough to get into multi-user mode, can be killed instantly with a find, and will eventually keel over even with nothing particular happening (where 'eventually' is measured in a single-digit number of minutes). Rather annoying, as I have several machines with Promise controllers I'd like to move to 7.x. But sadly, they need to access their hard drives occasionally, so... -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 21:41:46 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B58816A417 for ; Thu, 1 Nov 2007 21:41:46 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 25C9F13C48E for ; Thu, 1 Nov 2007 21:41:46 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 590D3209D; Thu, 1 Nov 2007 22:41:00 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.1/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 45CD2209B; Thu, 1 Nov 2007 22:41:00 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id 2B51184479; Thu, 1 Nov 2007 22:41:00 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "Artem Kuchin" References: <0fbb01c81be1$37e698f0$0c00a8c0@Artem> Date: Thu, 01 Nov 2007 22:41:00 +0100 In-Reply-To: <0fbb01c81be1$37e698f0$0c00a8c0@Artem> (Artem Kuchin's message of "Wed\, 31 Oct 2007 20\:12\:28 +0300") Message-ID: <863avptzir.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: BIO_FLUSH on twe driver. Why is it not there? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 21:41:46 -0000 "Artem Kuchin" writes: > However, twe is working via scsi subsystem and the authour of gjournal > said somewhere that he has had implemeneted BIO_FLISH for scsi and he > specifically mentioned that he has tested twe and twa and they both > support BIO_FLUSH. twa(4) uses CAM, but twe(4) doesn't (and never has). DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 23:07:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6AEFC16A417; Thu, 1 Nov 2007 23:07:18 +0000 (UTC) (envelope-from screwdriver@lxnt.info) Received: from mail.lxnt.info (mail.lxnt.info [217.23.143.142]) by mx1.freebsd.org (Postfix) with ESMTP id 2313213C4A5; Thu, 1 Nov 2007 23:07:18 +0000 (UTC) (envelope-from screwdriver@lxnt.info) Received: from [84.23.55.127] (helo=[192.168.1.100]) by mail.lxnt.info with esmtpa (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Inhq9-000Cos-Gb; Fri, 02 Nov 2007 00:44:37 +0300 Message-ID: <472A548B.50406@lxnt.info> Date: Fri, 02 Nov 2007 01:34:51 +0300 From: Alexander Sabourenkov User-Agent: Thunderbird 1.5.0.7 (X11/20061030) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, sos@FreeBSD.org, "Matthew D. Fuller" , Thierry Herbelot Subject: Patch RFC: Promise SATA300 TX4 hardware bug workaround. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 23:07:18 -0000 Hello. I have ported the workaround for the hardware bug that causes data corruption on Promise SATA300 TX4 cards to RELENG_7. Bug description: SATA300 TX4 hardware chokes if last PRD entry (in a dma transfer) is larger than 164 bytes. This was found while analysing vendor-supplied linux driver. Workaround: Split trailing PRD entry if it's larger that 164 bytes. Two supplied patches do fix problem on my machine. There is, however, a style problem with them. It seems like PRD entry count is limited at 256. I have not found a good way to guarantee that one entry is always available to do the split, thus the ugly solution of patching ata-dma.c. Patches, patched and original files are at http://lxnt.info/tx4/freebsd/. --- ata-chipset.c.orig 2007-11-02 01:05:49.000000000 +0300 +++ ata-chipset.c 2007-11-02 01:05:49.000000000 +0300 @@ -142,6 +142,7 @@ static int ata_promise_mio_command(struct ata_request *request); static void ata_promise_mio_reset(device_t dev); static void ata_promise_mio_dmainit(device_t dev); +static void ata_promise_mio_dmasetprd(void *xsc, bus_dma_segment_t *segs, int nsegs, int error); static void ata_promise_mio_setmode(device_t dev, int mode); static void ata_promise_sx4_intr(void *data); static int ata_promise_sx4_command(struct ata_request *request); @@ -185,7 +186,6 @@ static int ata_check_80pin(device_t dev, int mode); static int ata_mode2idx(int mode); - /* * generic ATA support functions */ @@ -3759,8 +3759,44 @@ static void ata_promise_mio_dmainit(device_t dev) { + struct ata_channel *ch = device_get_softc(dev); + /* note start and stop are not used here */ ata_dmainit(dev); + + if (ch->dma) + ch->dma->setprd = ata_promise_mio_dmasetprd; +} + +static void +ata_promise_mio_dmasetprd(void *xsc, bus_dma_segment_t *segs, int nsegs, int error) +{ + #define PDC_MAXLASTSGSIZE 41*4 + struct ata_dmasetprd_args *args = xsc; + struct ata_dma_prdentry *prd = args->dmatab; + int i; + + if ((args->error = error)) + return; + + for (i = 0; i < nsegs; i++) { + prd[i].addr = htole32(segs[i].ds_addr); + prd[i].count = htole32(segs[i].ds_len); + } + + if (segs[i - 1].ds_len > PDC_MAXLASTSGSIZE) { + /* + printf("splitting trailing PRD of %ld (limit %d)\n", segs[i - 1].ds_len, PDC_MAXLASTSGSIZE); + */ + prd[i - 1].count = htole32(segs[i - 1].ds_len - PDC_MAXLASTSGSIZE); + prd[i].count = htole32(PDC_MAXLASTSGSIZE); + prd[i].addr = htole32(segs[i - 1].ds_addr + PDC_MAXLASTSGSIZE); + i ++; + nsegs ++; + } + + prd[i - 1].count |= htole32(ATA_DMA_EOT); + args->nsegs = nsegs; } static void --- ata-dma.c.orig 2007-11-02 01:05:53.000000000 +0300 +++ ata-dma.c 2007-11-02 01:05:53.000000000 +0300 @@ -113,7 +113,7 @@ if (bus_dma_tag_create(ch->dma->dmatag,ch->dma->alignment,ch->dma->boundary, ch->dma->max_address, BUS_SPACE_MAXADDR, NULL, NULL, ch->dma->max_iosize, - ATA_DMA_ENTRIES, ch->dma->segsize, + ATA_DMA_ENTRIES - 1, ch->dma->segsize, 0, NULL, NULL, &ch->dma->data_tag)) goto error; -- ./lxnt From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 23:17:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE61E16A421 for ; Thu, 1 Nov 2007 23:17:18 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id D028913C4BD for ; Thu, 1 Nov 2007 23:17:17 +0000 (UTC) (envelope-from arno@heho.snv.jussieu.fr) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.13.8/jtpda-5.4) with ESMTP id lA1MCHUv024030 ; Thu, 1 Nov 2007 23:12:18 +0100 (CET) X-Ids: 164 Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) by heho.snv.jussieu.fr (8.13.3/jtpda-5.2) with ESMTP id lA1MCGZ3015118 ; Thu, 1 Nov 2007 23:12:16 +0100 (MET) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.13.3/8.13.1/Submit) id lA1MCGWm015115; Thu, 1 Nov 2007 23:12:16 +0100 (MET) (envelope-from arno) To: "Matthew D. Fuller" References: <200711011509.46094.thierry@herbelot.com> <20071101190505.GJ1580@over-yonder.net> From: "Arno J. Klaassen" Date: 01 Nov 2007 23:12:15 +0100 In-Reply-To: <20071101190505.GJ1580@over-yonder.net> Message-ID: Lines: 43 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (shiva.jussieu.fr [134.157.0.164]); Thu, 01 Nov 2007 23:12:18 +0100 (CET) X-Virus-Scanned: ClamAV 0.88.7/4659/Thu Nov 1 17:24:40 2007 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at shiva.jussieu.fr with ID 472A4F41.005 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! Cc: freebsd-current@freebsd.org Subject: Re: regression with gmirror, Promise SATA and 7.0 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Nov 2007 23:17:18 -0000 "Matthew D. Fuller" writes: > On Thu, Nov 01, 2007 at 03:09:45PM +0100 I heard the voice of > Thierry Herbelot, and lo! it spake thus: > > > > Thus, it seems that the combination of this Promise controller and > > the SATA disks has issues (there was a thread about Promise > > controllers and ZFS, but with no clear conclusion). > > See > > (and probably a number of other posts). > > This has been an issue for me with -CURRENT (and so now RELENG_7) > early this year. This box is still running RELENG_6 (and I'm writing > this mail on it), and will take a pounding on the drives all day long > without the slightest tic. But put -CURRENT/RELENG_7 on it, and it's > lucky to live long enough to get into multi-user mode, can be killed > instantly with a find, and will eventually keel over even with nothing > particular happening (where 'eventually' is measured in a single-digit > number of minutes). > > Rather annoying, as I have several machines with Promise controllers > I'd like to move to 7.x. But sadly, they need to access their hard > drives occasionally, so... Seems like Alexander Sabourenkov found a possible issue : http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/115337 Arno > > -- > Matthew Fuller (MF4839) | fullermd@over-yonder.net > Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ > On the Internet, nobody can hear you scream. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 00:02:06 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4E7A16A419; Fri, 2 Nov 2007 00:02:06 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from ipmail01.adl2.internode.on.net (ipmail01.adl2.internode.on.net [203.16.214.140]) by mx1.freebsd.org (Postfix) with ESMTP id 162BB13C4A8; Fri, 2 Nov 2007 00:02:04 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) X-IronPort-AV: E=Sophos;i="4.21,360,1188743400"; d="scan'208";a="223987938" Received: from ppp121-45-121-213.lns11.adl6.internode.on.net (HELO mail.clearchain.com) ([121.45.121.213]) by ipmail01.adl2.internode.on.net with ESMTP; 02 Nov 2007 10:23:53 +1030 Received: from wolf.clearchain.com (wcl.ml.unisa.edu.au [130.220.166.5]) (authenticated bits=0) by mail.clearchain.com (8.13.8/8.13.8) with ESMTP id lA1NriY2099916 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Nov 2007 10:23:50 +1030 (CST) (envelope-from Benjamin.Close@clearchain.com) Message-ID: <472A6708.9030109@clearchain.com> Date: Fri, 02 Nov 2007 10:23:44 +1030 From: Benjamin Close User-Agent: Thunderbird 2.0.0.0 (X11/20070615) MIME-Version: 1.0 To: freebsd-current Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on pegasus.clearchain.com X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (mail.clearchain.com [192.168.154.1]); Fri, 02 Nov 2007 10:23:50 +1030 (CST) X-Mailman-Approved-At: Fri, 02 Nov 2007 00:02:26 +0000 Cc: freebsd-drivers@freebsd.org, freebsd-mobile@freebsd.org Subject: [RFT] Intel 3945abg wireless driver (wpi) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 00:02:06 -0000 Howdy All, I'm pleased to announce the first 'official' experimental version of the wpi wireless driver and hence require your help in making it become stable. Expect a few things not to work (ie bg scanning, setting txpower) but in general the driver should be usable in station mode (hostap is not yet supported). If you've got an Intel 3945abg wireless card, grab the tarball at: http://people.freebsd.org/~benjsc/downloads/wpi/20071102-freebsd-wpi.tar.gz Untar and follow the instructions in the README. If you want more info about the driver, or to checkout the FAQ checkout: http://www.clearchain.com/wiki/Wpi I'm interested in all reports related to panics, things not working as expected, etc. The driver still has debug enabled so expect a few messages to be dumped to the screen whilst in use. Finally, many thanks to all those that have been helping debug the driver along the way. Cheers, Benjamin From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 00:37:33 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE95A16A46B; Fri, 2 Nov 2007 00:37:33 +0000 (UTC) (envelope-from syleishere@hotmail.com) Received: from bay0-omc3-s29.bay0.hotmail.com (bay0-omc3-s29.bay0.hotmail.com [65.54.246.229]) by mx1.freebsd.org (Postfix) with ESMTP id 90B4013C4A6; Fri, 2 Nov 2007 00:37:33 +0000 (UTC) (envelope-from syleishere@hotmail.com) Received: from BAY102-W11 ([64.4.61.111]) by bay0-omc3-s29.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Thu, 1 Nov 2007 08:05:35 -0700 Message-ID: X-Originating-IP: [24.79.240.75] From: syle ishere To: pluknet Date: Thu, 1 Nov 2007 10:05:34 -0500 Importance: Normal In-Reply-To: References: <200710251511.13161.jhb@freebsd.org> MIME-Version: 1.0 X-OriginalArrivalTime: 01 Nov 2007 15:05:35.0320 (UTC) FILETIME=[A7A3DD80:01C81C98] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: RE: kernel panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 00:37:33 -0000 I've had a few headaches lately with amd64 on my Dell 2650 server, but been= slowly solving them. =20 I've noticed a few things about options in make.conf breaking things lately= to. For instance, setting CPUTYPE to k8 explicitly in make.conf will segfault t= he port mysql-server50 soon as you try to start it up. =20 Installing pine4 port with Maildir patch will also crash unless you manuall= y incorporate amd64 patch from this site, http://www.gluelogic.com/code/PINE-maildir/ bef= ore building. I've emailed the maintainer of the maildir patch, but this person has as of= yet, not bothered responding. =20 Qmail from ports will also crash unless you tune 2 things 1) softlimit sett= ing needs to be increased to allow qmail-smtp more memory when running it and 2) you must patch qmail= from ports with the following : http://lists.freebsd.org/pipermail/freebsd-ports/2007-October/0= 44434.html or you'll never send a peice of mail without it segfaulting.=20 =20 I know these issues are offtopic with loader but it shows to demonstrate se= tting options in make.conf does cause alot of problems, and moving to amd64 isn't a quick fix for anyt= hing. =20 I've now removed any CFLAG and CPUTYPE lines out of make.conf permanently. = It was causing more problems than good. I'll try and test my i386 laptop later today without any make.conf options = as well to see if your on to something there pluknet. =20 =20 Dan. =20 > Date: Thu, 1 Nov 2007 15:35:50 +0300> From: pluknet@gmail.com> To: jhb@fr= eebsd.org> Subject: Re: kernel panic> CC: freebsd-current@freebsd.org; syle= ishere@hotmail.com> > On 25/10/2007, John Baldwin wrote:>= > On Thursday 25 October 2007 01:10:33 pm syle ishere wrote:> > >> > > I t= ried testing this. Added> > > LOADER_FIREWIRE_SUPPORT=3Dyes in /etc/make.co= nf> > > (cd /sys/boot/i386 && make clean && make && make install)shutdown -= r now> > > All was great it the loader worked!> > >> > > To test this wasn'= t my imagination:> > > I took that line out of make.conf> > > (cd /sys/boot= /i386 && make clean && make && make install)shutdown -r now> > >> > > And g= ot same problem system not booting.> > >> > > Good catch pluknet, hopefully= we can get this code compiled into the loader> > as a mandatory fix> > > f= or now.> >> > That seems odd. I would make sure you really have a clean bui= ld, and I would> > build from /sys/boot, not /sys/boot/i386.> >> > --> > Jo= hn Baldwin> >> > Yes. I've just checked that loader brokeness is influenced= by> -funroll-loops in make.conf> > wbr,> pluknet _________________________________________________________________ Are you ready for Windows Live Messenger Beta 8.5 ? Get the latest for free= today! http://entertainment.sympatico.msn.ca/WindowsLiveMessenger= From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 00:42:50 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03EFF16A418; Fri, 2 Nov 2007 00:42:50 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: from mail.0x20.net (mail.ipv6.0x20.net [IPv6:2001:aa8:fffb::3]) by mx1.freebsd.org (Postfix) with ESMTP id 8AE5C13C4C4; Fri, 2 Nov 2007 00:42:49 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: by mail.0x20.net (Postfix, from userid 1002) id 367793A57C; Fri, 2 Nov 2007 01:42:48 +0100 (CET) Date: Fri, 2 Nov 2007 01:42:48 +0100 From: Lars Engels To: Benjamin Close Message-ID: <20071102004248.GA5253@e.0x20.net> Mail-Followup-To: Lars Engels , Benjamin Close , freebsd-current , freebsd-drivers@freebsd.org, freebsd-mobile@freebsd.org References: <472A6708.9030109@clearchain.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IJpNTDwzlM2Ie8A6" Content-Disposition: inline In-Reply-To: <472A6708.9030109@clearchain.com> X-Editor: VIM - Vi IMproved 7.1 X-Operation-System: FreeBSD 5.5-RELEASE User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: freebsd-current , freebsd-drivers@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: [RFT] Intel 3945abg wireless driver (wpi) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Lars Engels List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 00:42:50 -0000 --IJpNTDwzlM2Ie8A6 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 02, 2007 at 10:23:44AM +1030, Benjamin Close wrote: > Howdy All, I'm pleased to announce the first 'official' experim= ental version of the wpi wireless driver and hence require your help in mak= ing it become=20 > stable. > Expect a few things not to work (ie bg scanning, setting txpower) but in = general the driver should be usable in station mode (hostap is not yet supp= orted). >=20 > If you've got an Intel 3945abg wireless card, grab the tarball at: >=20 > http://people.freebsd.org/~benjsc/downloads/wpi/20071102-freebsd-wpi.t= ar.gz >=20 > Untar and follow the instructions in the README. > If you want more info about the driver, or to checkout the FAQ checkout: >=20 > http://www.clearchain.com/wiki/Wpi >=20 > I'm interested in all reports related to panics, things not working as ex= pected, etc. > The driver still has debug enabled so expect a few messages to be dumped = to the screen whilst in use. >=20 > Finally, many thanks to all those that have been helping debug the driver= along the way. >=20 > Cheers, > Benjamin Good to know that someone is still working on it. However, it doesn't work for me. I cannot load the firmware: lars@ttyp3 # kldload wpifw lars@ttyp3 # dmesg wpifw: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/. wpifw: If you agree with the license, set legal.intel_wpi.license_ack=3D1 in /boot/loader.conf. module_register_init: MOD_LOAD (wpifw_fw, 0xc6d1151c, 0) error 1 lars@ttyp3 # grep legal.intel_wpi.license_ack /boot/loader.conf legal.intel_wpi.license_ack=3D1 lars@ttyp3 # sysctl legal sysctl: unknown oid 'legal' And I even read the license! ;-) Lars --IJpNTDwzlM2Ie8A6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFHKnKIKc512sD3afgRAp1pAJ4mAoMYbQrY3AzUZ4gukiInEs1XoACcCydj LJRcWlbKK1inM62rC8sWL7g= =qADt -----END PGP SIGNATURE----- --IJpNTDwzlM2Ie8A6-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 00:54:35 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E407516A417; Fri, 2 Nov 2007 00:54:34 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 99F2913C4A6; Fri, 2 Nov 2007 00:54:34 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.8/8.13.8) with ESMTP id lA202Wr1052967; Thu, 1 Nov 2007 20:02:32 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.14.1/8.14.1) with ESMTP id lA202W1n094170; Thu, 1 Nov 2007 20:02:32 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id D27AE73068; Thu, 1 Nov 2007 19:02:31 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20071102000231.D27AE73068@freebsd-current.sentex.ca> Date: Thu, 1 Nov 2007 19:02:31 -0500 (EST) X-Virus-Scanned: ClamAV 0.90.2/3781/Fri Jul 27 07:24:10 2007 clamav-milter version 0.91.1 on news X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 00:54:35 -0000 TB --- 2007-11-01 21:40:01 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-11-01 21:40:01 - starting HEAD tinderbox run for i386/i386 TB --- 2007-11-01 21:40:01 - cleaning the object tree TB --- 2007-11-01 21:40:06 - checking out the source tree TB --- 2007-11-01 21:40:06 - cd /tinderbox/HEAD/i386/i386 TB --- 2007-11-01 21:40:06 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-11-01 21:48:38 - building world (CFLAGS=-O2 -pipe) TB --- 2007-11-01 21:48:38 - cd /src TB --- 2007-11-01 21:48:38 - /usr/bin/make -B buildworld >>> World build started on Thu Nov 1 21:48:40 UTC 2007 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Thu Nov 1 23:04:26 UTC 2007 TB --- 2007-11-01 23:04:26 - generating LINT kernel config TB --- 2007-11-01 23:04:26 - cd /src/sys/i386/conf TB --- 2007-11-01 23:04:26 - /usr/bin/make -B LINT TB --- 2007-11-01 23:04:27 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-01 23:04:27 - cd /src TB --- 2007-11-01 23:04:27 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Nov 1 23:04:27 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Thu Nov 1 23:33:00 UTC 2007 TB --- 2007-11-01 23:33:00 - building GENERIC kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-01 23:33:00 - cd /src TB --- 2007-11-01 23:33:00 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Thu Nov 1 23:33:00 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Thu Nov 1 23:55:42 UTC 2007 TB --- 2007-11-01 23:55:42 - building PAE kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-01 23:55:42 - cd /src TB --- 2007-11-01 23:55:42 - /usr/bin/make -B buildkernel KERNCONF=PAE >>> Kernel build for PAE started on Thu Nov 1 23:55:42 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] if_zyd.o(.text+0x3a85): In function `zyd_ioctl': /src/sys/dev/usb/if_zyd.c:2390: undefined reference to `ieee80211_ioctl' if_zyd.o(.text+0x3b35): In function `zyd_media_change': /src/sys/dev/usb/if_zyd.c:673: undefined reference to `ieee80211_media_change' if_zyd.o(.text+0x3cc7): In function `zyd_rx_data': /src/sys/dev/usb/if_zyd.c:1942: undefined reference to `ieee80211_find_rxnode' if_zyd.o(.text+0x3d03):/src/sys/dev/usb/if_zyd.c:1943: undefined reference to `ieee80211_input' if_zyd.o(.text+0x3d0b):/src/sys/dev/usb/if_zyd.c:1947: undefined reference to `ieee80211_free_node' *** Error code 1 Stop in /obj/src/sys/PAE. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-11-02 00:02:31 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-11-02 00:02:31 - ERROR: failed to build PAE kernel TB --- 2007-11-02 00:02:31 - tinderbox aborted TB --- 0.10 user 0.16 system 8550.35 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 01:40:14 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4BC0616A46B for ; Fri, 2 Nov 2007 01:40:14 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by mx1.freebsd.org (Postfix) with ESMTP id 1EE4D13C4A3 for ; Fri, 2 Nov 2007 01:40:13 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so846013waf for ; Thu, 01 Nov 2007 18:39:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; 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=/Vo2lL7hdCjK5O/4tzLt1eLN3A6BD+QQfiNsJ0UPBZY=; b=JlO3P6ykhFSQy5BNt7ciO9LMgLxAct6YdPk3G2Uba0jAKeVj2mjNEVJnph7iRPl3tgjaYjmMFlCZeO9zvushBbQ6aBPNYoszcqo6LHZUgoah6lmXzx4k+Z4H/5BxI9mmShDow/GRNTlysbpdPtPazBcGdmjyuFpqHs/wQdnk2n0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NNM0SXtGE3C0gvq8WUiMJjyJaXyZHVZwhDslSoedI4PI42k2uncaeGsWu4TdllbV7sh958lbJGYyVkb7V4KcBt9644sGWmUbbcTrxz42N/nWJsK9fgslEvPjdZN1nTGZSjB530CVXkzIgj5wcJC1s9+Icu9NMmi0BRCi5NnEV3g= Received: by 10.115.22.1 with SMTP id z1mr1263571wai.1193964326259; Thu, 01 Nov 2007 17:45:26 -0700 (PDT) Received: by 10.114.13.15 with HTTP; Thu, 1 Nov 2007 17:45:26 -0700 (PDT) Message-ID: Date: Thu, 1 Nov 2007 17:45:26 -0700 From: "Kip Macy" To: "Lars Engels" , "Benjamin Close" , freebsd-current , freebsd-drivers@freebsd.org, freebsd-mobile@freebsd.org In-Reply-To: <20071102004248.GA5253@e.0x20.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <472A6708.9030109@clearchain.com> <20071102004248.GA5253@e.0x20.net> Cc: Subject: Re: [RFT] Intel 3945abg wireless driver (wpi) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 01:40:14 -0000 man kenv On 11/1/07, Lars Engels wrote: > On Fri, Nov 02, 2007 at 10:23:44AM +1030, Benjamin Close wrote: > > Howdy All, I'm pleased to announce the first 'official' experimental version of the wpi wireless driver and hence require your help in making it become > > stable. > > Expect a few things not to work (ie bg scanning, setting txpower) but in general the driver should be usable in station mode (hostap is not yet supported). > > > > If you've got an Intel 3945abg wireless card, grab the tarball at: > > > > http://people.freebsd.org/~benjsc/downloads/wpi/20071102-freebsd-wpi.tar.gz > > > > Untar and follow the instructions in the README. > > If you want more info about the driver, or to checkout the FAQ checkout: > > > > http://www.clearchain.com/wiki/Wpi > > > > I'm interested in all reports related to panics, things not working as expected, etc. > > The driver still has debug enabled so expect a few messages to be dumped to the screen whilst in use. > > > > Finally, many thanks to all those that have been helping debug the driver along the way. > > > > Cheers, > > Benjamin > > Good to know that someone is still working on it. > However, it doesn't work for me. I cannot load the firmware: > > lars@ttyp3 # kldload wpifw > lars@ttyp3 # dmesg > wpifw: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/. > wpifw: If you agree with the license, set legal.intel_wpi.license_ack=1 > in /boot/loader.conf. > module_register_init: MOD_LOAD (wpifw_fw, 0xc6d1151c, 0) error 1 > > lars@ttyp3 # grep legal.intel_wpi.license_ack /boot/loader.conf > legal.intel_wpi.license_ack=1 > > lars@ttyp3 # sysctl legal > sysctl: unknown oid 'legal' > > And I even read the license! ;-) > > Lars > > From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 02:57:39 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34C2316A417 for ; Fri, 2 Nov 2007 02:57:39 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.179]) by mx1.freebsd.org (Postfix) with ESMTP id 7786B13C4A8 for ; Fri, 2 Nov 2007 02:57:38 +0000 (UTC) (envelope-from max@love2party.net) Received: from amd64.laiers.local (dslb-088-066-044-048.pools.arcor-ip.net [88.66.44.48]) by mrelayeu.kundenserver.de (node=mrelayeu3) with ESMTP (Nemesis) id 0MKxQS-1InkmN38wV-0006w6; Fri, 02 Nov 2007 01:52:56 +0100 From: Max Laier Organization: FreeBSD To: freebsd-current@freebsd.org, Lars Engels Date: Fri, 2 Nov 2007 01:52:44 +0100 User-Agent: KMail/1.9.7 References: <472A6708.9030109@clearchain.com> <20071102004248.GA5253@e.0x20.net> In-Reply-To: <20071102004248.GA5253@e.0x20.net> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1448871.x47iAX1EqJ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200711020152.53535.max@love2party.net> X-Provags-ID: V01U2FsdGVkX19wX6xz7zvLyKEPl2knS4+0lvMY3McrRmaeMyD 715sfY2WaXUGrLK6VqOmLUUjgPLvJwBjgZj0UmEfewYkqDGVaF wn8hsIjaxrWN1aw1ZDunhikkwGR8g9vjcCxVMYSqAo= Cc: Benjamin Close , freebsd-drivers@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: [RFT] Intel 3945abg wireless driver (wpi) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 02:57:39 -0000 --nextPart1448871.x47iAX1EqJ Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 02 November 2007, Lars Engels wrote: > On Fri, Nov 02, 2007 at 10:23:44AM +1030, Benjamin Close wrote: > > Howdy All, I'm pleased to announce the first 'official' > > experimental version of the wpi wireless driver and hence require > > your help in making it become stable. > > Expect a few things not to work (ie bg scanning, setting txpower) but > > in general the driver should be usable in station mode (hostap is not > > yet supported). > > > > If you've got an Intel 3945abg wireless card, grab the tarball at: > > > > =20 > > http://people.freebsd.org/~benjsc/downloads/wpi/20071102-freebsd-wpi. > >tar.gz > > > > Untar and follow the instructions in the README. > > If you want more info about the driver, or to checkout the FAQ > > checkout: > > > > http://www.clearchain.com/wiki/Wpi > > > > I'm interested in all reports related to panics, things not working > > as expected, etc. The driver still has debug enabled so expect a few > > messages to be dumped to the screen whilst in use. > > > > Finally, many thanks to all those that have been helping debug the > > driver along the way. > > > > Cheers, > > Benjamin > > Good to know that someone is still working on it. > However, it doesn't work for me. I cannot load the firmware: > > lars@ttyp3 # kldload wpifw > lars@ttyp3 # dmesg > wpifw: You need to read the LICENSE file in > /usr/share/doc/legal/intel_wpi/. wpifw: If you agree with the license, > set legal.intel_wpi.license_ack=3D1 in /boot/loader.conf. > module_register_init: MOD_LOAD (wpifw_fw, 0xc6d1151c, 0) error 1 > > lars@ttyp3 # grep legal.intel_wpi.license_ack /boot/loader.conf > legal.intel_wpi.license_ack=3D1 > > lars@ttyp3 # sysctl legal > sysctl: unknown oid 'legal' It's not a sysctl it's in kenv, but if it's in loader.conf it should be in= =20 kenv, too. > And I even read the license! ;-) =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1448871.x47iAX1EqJ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHKnTlXyyEoT62BG0RAliyAJ0USnzcHoQRnN/R/6momwSAiQn8rACeNHvy OWqrj8s/fRTsPqASqQgEXD0= =Jbpn -----END PGP SIGNATURE----- --nextPart1448871.x47iAX1EqJ-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 02:42:15 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 674DD16A417; Fri, 2 Nov 2007 02:42:15 +0000 (UTC) (envelope-from mpp@mppsystems.com) Received: from lugdush.gulftel.com (lugdush.gulftel.com [216.231.163.39]) by mx1.freebsd.org (Postfix) with ESMTP id 2CE2213C4A6; Fri, 2 Nov 2007 02:42:14 +0000 (UTC) (envelope-from mpp@mppsystems.com) Received: from localhost (localhost [127.0.0.1]) by lugdush.gulftel.com (Postfix) with ESMTP id 9E51BD664; Thu, 1 Nov 2007 21:40:27 -0500 (CDT) X-Virus-Scanned: amavisd-new at gulftel.com Received: from lugdush.gulftel.com ([127.0.0.1]) by localhost (lugdush.gulftel.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EpKYMuACZU+q; Thu, 1 Nov 2007 21:40:24 -0500 (CDT) Received: from mail.mppsystems.com (unknown [10.17.28.253]) by lugdush.gulftel.com (Postfix) with ESMTP id C22EAD4D5; Thu, 1 Nov 2007 21:36:36 -0500 (CDT) Received: by mail.mppsystems.com (Postfix, from userid 1000) id 15EEC17041; Thu, 1 Nov 2007 21:36:35 -0500 (CDT) Date: Thu, 1 Nov 2007 21:36:34 -0500 From: Mike Pritchard To: John Baldwin Message-ID: <20071102023634.GA48352@mail.mppsystems.com> References: <862892.31020.qm@web27810.mail.ukl.yahoo.com> <20071101013748.GA1116@mail.mppsystems.com> <200711011123.35870.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200711011123.35870.jhb@freebsd.org> User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Mailman-Approved-At: Fri, 02 Nov 2007 03:12:05 +0000 Cc: freebsd-current@freebsd.org, Red Neck , Mike Pritchard Subject: Re: Loader broken in Head? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 02:42:15 -0000 On Thu, Nov 01, 2007 at 11:23:35AM -0400, John Baldwin wrote: > On Wednesday 31 October 2007 09:37:48 pm Mike Pritchard wrote: > > > > I was seeing a similar problem. Booting from a floppy disk twice would > > probably be faster than booting off the hard disk. I had just done > > a makeworld, and updated the boot blocks on the disk (it previously had > > a pretty old install on it). But the system would eventually boot, and > > not hang up. I noticed that Red Necks boot loader build date was the > > same as the version I was having problems with. > > > > Fortunately, I have a 2nd HD in the machine with a 7.0 install, > > and installed the boot blocks from that HD to the one I was having > > problems with, and copied over /boot/loader from that HD. > > No more problems. System boots as fast as ever. > > > > So yes, I think there is something wrong with the current loader. > Did you get the latest loader? For example, do you have this fix which might > result in significantly slower disk I/O since w/o it every disk I/O is > attempted 3 times with 2 drive resets in between: > > jhb 2007-10-25 16:53:35 UTC > > FreeBSD src repository > > Modified files: > sys/boot/i386/libi386 biosdisk.c > Log: > Break out of the I/O retry loop as soon as an I/O operation succeeds rather > than always retrying operations three times. > > Submitted by: nyan > > Revision Changes Path > 1.53 +2 -0 src/sys/boot/i386/libi386/biosdisk.c I'd be glad to try, if you could tell me how to build the loader... or if I'm building it correctly, if someone could fix this compile error I see (see below). And the couple of warnings I see compiling make me nervous too. I don't want to mess around too much until I'm sure I'm building it correctly, because I'd like to leave this machine bootable :) Other than that, if a fresh -current loader still doesn't fix my problem, I'm more than willing to start backing out recent commits to find which commit might be the problem. With 8.0-current sources as of a couple of hours ago, I get the same compile error trying any of these: cd /usr/src/sys && make cd /usr/src/sys && make boot cd /usr/src/sys/boot && make cd /usr/src/sys/boot/i386 && make all fail with: ... ===> i386/gptboot (all) ===> i386/kgzldr (all) ===> i386/libi386 (all) cc -O2 -fno-strict-aliasing -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600 -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=__builtin_alloca -I/shared/src/sys/boot/i386/libi386/../../common -I/shared/src/sys/boot/i386/libi386/../btx/lib -I/shared/src/sys/boot/i386/libi386/../../../contrib/dev/acpica -I/shared/src/sys/boot/i386/libi386/../../.. -I. -I/shared/src/sys/boot/i386/libi386/../../../../lib/libstand/ -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -c /shared/src/sys/boot/i386/libi386/biosmem.c /shared/src/sys/boot/i386/libi386/biosmem.c: In function 'bios_getmem': /shared/src/sys/boot/i386/libi386/biosmem.c:61: error: 'SMAP_TYPE_MEMORY' undeclared (first use in this function) /shared/src/sys/boot/i386/libi386/biosmem.c:61: error: (Each undeclared identifier is reported only once /shared/src/sys/boot/i386/libi386/biosmem.c:61: error: for each function it appears in.) *** Error code 1 Stop in /shared/src/sys/boot/i386/libi386. *** Error code 1 Stop in /shared/src/sys/boot/i386. *** Error code 1 Stop in /shared/src/sys/boot. -- Mike Pritchard mpp @ FreeBSD.org "If tyranny and oppression come to this land, it will be in the guise of fighting a foreign enemy." - James Madison (1787) From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 01:32:11 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B7DE16A420; Fri, 2 Nov 2007 01:32:11 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from ipmail01.adl2.internode.on.net (ipmail01.adl2.internode.on.net [203.16.214.140]) by mx1.freebsd.org (Postfix) with ESMTP id D6EBA13C48D; Fri, 2 Nov 2007 01:32:07 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) X-IronPort-AV: E=Sophos;i="4.21,360,1188743400"; d="scan'208";a="224043007" Received: from ppp121-45-121-213.lns11.adl6.internode.on.net (HELO mail.clearchain.com) ([121.45.121.213]) by ipmail01.adl2.internode.on.net with ESMTP; 02 Nov 2007 11:48:31 +1030 Received: from wolf.clearchain.com (wcl.ml.unisa.edu.au [130.220.166.5]) (authenticated bits=0) by mail.clearchain.com (8.13.8/8.13.8) with ESMTP id lA21ILHU000769 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 2 Nov 2007 11:48:27 +1030 (CST) (envelope-from Benjamin.Close@clearchain.com) Message-ID: <472A7ADD.3010002@clearchain.com> Date: Fri, 02 Nov 2007 11:48:21 +1030 From: Benjamin Close User-Agent: Thunderbird 2.0.0.0 (X11/20070615) MIME-Version: 1.0 To: Max Laier References: <472A6708.9030109@clearchain.com> <20071102004248.GA5253@e.0x20.net> <200711020152.53535.max@love2party.net> In-Reply-To: <200711020152.53535.max@love2party.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on pegasus.clearchain.com X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (mail.clearchain.com [192.168.154.1]); Fri, 02 Nov 2007 11:48:28 +1030 (CST) X-Mailman-Approved-At: Fri, 02 Nov 2007 03:12:23 +0000 Cc: Lars Engels , freebsd-current@freebsd.org, freebsd-drivers@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: [RFT] Intel 3945abg wireless driver (wpi) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 01:32:11 -0000 Max Laier wrote: > On Friday 02 November 2007, Lars Engels wrote: > >> On Fri, Nov 02, 2007 at 10:23:44AM +1030, Benjamin Close wrote: >> >>> Howdy All, I'm pleased to announce the first 'official' >>> experimental version of the wpi wireless driver and hence require >>> your help in making it become stable. >>> Expect a few things not to work (ie bg scanning, setting txpower) but >>> in general the driver should be usable in station mode (hostap is not >>> yet supported). >>> >>> If you've got an Intel 3945abg wireless card, grab the tarball at: >>> >>> >>> http://people.freebsd.org/~benjsc/downloads/wpi/20071102-freebsd-wpi. >>> tar.gz >>> >>> Untar and follow the instructions in the README. >>> If you want more info about the driver, or to checkout the FAQ >>> checkout: >>> >>> http://www.clearchain.com/wiki/Wpi >>> >>> I'm interested in all reports related to panics, things not working >>> as expected, etc. The driver still has debug enabled so expect a few >>> messages to be dumped to the screen whilst in use. >>> >>> Finally, many thanks to all those that have been helping debug the >>> driver along the way. >>> >>> Cheers, >>> Benjamin >>> >> Good to know that someone is still working on it. >> However, it doesn't work for me. I cannot load the firmware: >> >> lars@ttyp3 # kldload wpifw >> lars@ttyp3 # dmesg >> wpifw: You need to read the LICENSE file in >> /usr/share/doc/legal/intel_wpi/. wpifw: If you agree with the license, >> set legal.intel_wpi.license_ack=1 in /boot/loader.conf. >> module_register_init: MOD_LOAD (wpifw_fw, 0xc6d1151c, 0) error 1 >> >> lars@ttyp3 # grep legal.intel_wpi.license_ack /boot/loader.conf >> legal.intel_wpi.license_ack=1 >> >> lars@ttyp3 # sysctl legal >> sysctl: unknown oid 'legal' >> > > It's not a sysctl it's in kenv, but if it's in loader.conf it should be in > kenv, too. > > >> And I even read the license! ;-) >> > > > You shouldn't need to manually kldload the wpifw, wpi will pull it in for you. However, if you have the line in loader.conf it should work - I take it you did reboot for the setting to be grabbed? Cheers, Benjamin From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 04:24:05 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02F4316A418 for ; Fri, 2 Nov 2007 04:24:05 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.231]) by mx1.freebsd.org (Postfix) with ESMTP id 91EE213C465 for ; Fri, 2 Nov 2007 04:24:04 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by wx-out-0506.google.com with SMTP id i29so615479wxd for ; Thu, 01 Nov 2007 21:23:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; bh=g/YRNcv4bsWbEBTHUwjSa1R6WnOfNOyNMPrHWCKCXI0=; b=WSU3vWRel0vhka0w3znJQmf0OM7uPUS2vWjMsYduSCMIQGTas+F+orYGNxqzv2pBay6877hBy28+O87yqyf/WASQkNxW2A3NckoV6BIsQXA3LB+i065MkaKiJ1eVVAq8TOmu2/T1W3P1F9MhXOaV6aRtZOe96875aqtQ45euPzE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=m3MmB2CrA20KlFms0OGDlG7JCA2NNUcbWbw87haLx5vnrV+4Xb0fXUmI5P03lKzyw9nAkPpX+brOmU1ljkOOXBj29z8GRyvGIwcPqiVTbia4NSVWltMSXrGBcdaHRJzjkiTc0NQ/JdHO7aHp6n/zH3L6pi4hbWpCJ9THaeAlfmE= Received: by 10.70.27.5 with SMTP id a5mr1879006wxa.1193975667536; Thu, 01 Nov 2007 20:54:27 -0700 (PDT) Received: from ?192.168.2.2? ( [67.85.89.184]) by mx.google.com with ESMTPS id c29sm2220044elf.2007.11.01.20.54.25 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 01 Nov 2007 20:54:26 -0700 (PDT) Message-ID: <472A66EE.6060407@gmail.com> Date: Thu, 01 Nov 2007 19:53:18 -0400 From: "Aryeh M. Friedman" User-Agent: Thunderbird 2.0.0.6 (X11/20071031) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [PATCH] prevent install(1) from overwritting symlinks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 04:24:05 -0000 The below patch is designed to keep install(1) from overwriting symbolic links. The motivation is if cups is installed some programs still expect lpr to be in /usr/bin thus when I install cups I backlink the /usr/local/bin versions of lp* to /usr/bin. When a build/installworld is done these links are overwritten and the sym links have to be performed again. This patch prevents the overwrite. This is my very first patch (of any kind [not just for FreeBSD]) so can people please tell me what I did right and what I did wrong in making it. Also tell me what improvements (if any) can be made to the patched code. --- src/usr.bin/xinstall/xinstall.c.orig 2007-11-01 18:46:45.000000000 -0400 +++ src/usr.bin/xinstall/xinstall.c 2007-11-01 19:44:43.000000000 -0400 @@ -268,7 +268,7 @@ void install(const char *from_name, const char *to_name, u_long fset, u_int flags) { - struct stat from_sb, temp_sb, to_sb; + struct stat from_sb, temp_sb, to_sb, to_lsb; struct timeval tvb[2]; int devnull, files_match, from_fd, serrno, target; int tempcopy, temp_fd, to_fd; @@ -299,6 +299,13 @@ } target = stat(to_name, &to_sb) == 0; + target = lstat(to_name, &to_lsb) == 0; + + if(S_ISLNK(to_lsb.st_mode)) { + printf("%s is a symbolic link not modified\n",to_name); + errno = EFTYPE; + return; + } /* Only install to regular files. */ if (target && !S_ISREG(to_sb.st_mode)) { From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 04:50:42 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D418616A418 for ; Fri, 2 Nov 2007 04:50:42 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.230]) by mx1.freebsd.org (Postfix) with ESMTP id 8D41513C481 for ; Fri, 2 Nov 2007 04:50:42 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by wx-out-0506.google.com with SMTP id i29so619974wxd for ; Thu, 01 Nov 2007 21:50:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=aFOKAhS7CkDZZy1qEsVsFwAbImycjXylUopjWGWAnUE=; b=eXkuvol8r1lehOBHvRHtZbFxPYW64yFF6gV7kXwaIiwSybwAR0GdJqb3pgfHoUyUctd+Iklo6Z0Bq0NY6lcjUE2tav/6+RF1osX5dlaSKADxzC2SLVO4d+gOy509J3GVB763ZVgAy2LcEyRb7OuAGYlhlAc8JszLr4OyKAi9Dqo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=h9Ika2Va0PZ005WES6klwFGrIjRAt6cBA9kWww96gBOuSv/Levd5esQPnG/0WYCYOJq4UT67ypp/kAc27mfkXNDBbBrCm0ygPUgYAsLKq/sDxIpZhgor0u8Ppj3bPMs13yuEyo/qmYM3/RWoyld+ZTGZJM8P6Nehq0zVDVNztSM= Received: by 10.70.89.11 with SMTP id m11mr1944455wxb.1193978596170; Thu, 01 Nov 2007 21:43:16 -0700 (PDT) Received: from ?192.168.2.2? ( [67.85.89.184]) by mx.google.com with ESMTPS id r28sm4198357ele.2007.11.01.21.43.14 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 01 Nov 2007 21:43:15 -0700 (PDT) Message-ID: <472A725F.6000201@gmail.com> Date: Thu, 01 Nov 2007 20:42:07 -0400 From: "Aryeh M. Friedman" User-Agent: Thunderbird 2.0.0.6 (X11/20071031) MIME-Version: 1.0 To: Dan Nelson References: <472A66EE.6060407@gmail.com> <20071102043043.GI3109@dan.emsphone.com> In-Reply-To: <20071102043043.GI3109@dan.emsphone.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] prevent install(1) from overwritting symlinks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 04:50:42 -0000 Dan Nelson wrote: > In the last episode (Nov 01), Aryeh M. Friedman said: > >> The below patch is designed to keep install(1) from overwriting symbolic >> links. The motivation is if cups is installed some programs still >> expect lpr to be in /usr/bin thus when I install cups I backlink the >> /usr/local/bin versions of lp* to /usr/bin. When a build/installworld >> is done these links are overwritten and the sym links have to be >> performed again. This patch prevents the overwrite. >> > > Why not just set WITHOUT_LPR to skip building the base versions > entirely? > > Because this happens in other cases not covered by WITHOUT_XXX also it does not solve the problem of ports and/or third party install from overwritting.... i.e. this is a general solution to a specific problem (which I think is preferable to a one off solution for each instance of a problem) From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 05:58:36 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D991B16A419 for ; Fri, 2 Nov 2007 05:58:36 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.239]) by mx1.freebsd.org (Postfix) with ESMTP id 4C6C013C48E for ; Fri, 2 Nov 2007 05:58:36 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by wx-out-0506.google.com with SMTP id i29so632078wxd for ; Thu, 01 Nov 2007 22:58:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=0+nHhlNsXMHjSTYFwo7il/dUOaJhASAmLgIjrcsUVLc=; b=PcnUQaIx70Q/7DZ+9aKZtxZcUaVh88Dd7ffNGqEkj42bjJgz7Kai6/Yz005mCi+mNB00fTBFDIsnN5h1pTIxWyg+Vc6JWORRWif1oJllnCPAEyS1oY5rvkNwd1RUyix3yTGncbcwpdj2oebLjZG5PsA4SPvfaT3BLYQU4wDSl1w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=ICKT2qy0sVsRyHyfk6bRst5iKuBnVGSD9AMVFkmg+GD1pg/TJ8tyih9xLC9G8MP/vlmVUzXvbTijfUtarGXyddAF+9+VWsPEkyTZc8fFxsqhKyYJAxFyPdRYgG9KGFSmccGM6ggkda+FSxHtngtN3TAQ913TgYIR4yIIvLlMHZw= Received: by 10.70.34.13 with SMTP id h13mr2043049wxh.1193983095193; Thu, 01 Nov 2007 22:58:15 -0700 (PDT) Received: from ?192.168.2.2? ( [67.85.89.184]) by mx.google.com with ESMTPS id e27sm4252047elf.2007.11.01.22.58.13 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 01 Nov 2007 22:58:14 -0700 (PDT) Message-ID: <472A83F2.4060301@gmail.com> Date: Thu, 01 Nov 2007 21:57:06 -0400 From: "Aryeh M. Friedman" User-Agent: Thunderbird 2.0.0.6 (X11/20071031) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <472A66EE.6060407@gmail.com> <20071102043043.GI3109@dan.emsphone.com> In-Reply-To: <20071102043043.GI3109@dan.emsphone.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PATCH] prevent install(1) from overwritting symlinks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 05:58:36 -0000 Dan Nelson wrote: > In the last episode (Nov 01), Aryeh M. Friedman said: > >> The below patch is designed to keep install(1) from overwriting symbolic >> links. The motivation is if cups is installed some programs still >> expect lpr to be in /usr/bin thus when I install cups I backlink the >> /usr/local/bin versions of lp* to /usr/bin. When a build/installworld >> is done these links are overwritten and the sym links have to be >> performed again. This patch prevents the overwrite. >> I just tested the patch against installworld/kernel and got: % make installworld|grep symbolic /usr/share/locale/sr_YU.UTF-8/LC_MONETARY is a symbolic link not modified /usr/bin/lp is a symbolic link not modified /usr/bin/lpq is a symbolic link not modified /usr/bin/lpr is a symbolic link not modified /usr/bin/lprm is a symbolic link not modified % make installkernel|grep symbolic [no output] Except for the 4 /bin/lp* enteries (which the patch is meant to preserve) the only issue seems to be /usr/share/locale/sr_YU.UTF-8/LC_MONETARY. Thus conclusion so far is the patch will not harm 8-Current. From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 08:22:04 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91B4B16A421; Fri, 2 Nov 2007 08:22:04 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 6461513C480; Fri, 2 Nov 2007 08:22:04 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.8/8.13.8) with ESMTP id lA27NaFD068826; Fri, 2 Nov 2007 03:23:36 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.14.1/8.14.1) with ESMTP id lA27NaK3056545; Fri, 2 Nov 2007 03:23:36 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 5819073068; Fri, 2 Nov 2007 02:23:36 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20071102072336.5819073068@freebsd-current.sentex.ca> Date: Fri, 2 Nov 2007 02:23:36 -0500 (EST) X-Virus-Scanned: ClamAV 0.90.2/3781/Fri Jul 27 07:24:10 2007 clamav-milter version 0.91.1 on news X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 08:22:04 -0000 TB --- 2007-11-02 05:00:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-11-02 05:00:00 - starting HEAD tinderbox run for i386/i386 TB --- 2007-11-02 05:00:00 - cleaning the object tree TB --- 2007-11-02 05:00:33 - checking out the source tree TB --- 2007-11-02 05:00:33 - cd /tinderbox/HEAD/i386/i386 TB --- 2007-11-02 05:00:33 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-11-02 05:09:02 - building world (CFLAGS=-O2 -pipe) TB --- 2007-11-02 05:09:02 - cd /src TB --- 2007-11-02 05:09:02 - /usr/bin/make -B buildworld >>> World build started on Fri Nov 2 05:09:04 UTC 2007 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Nov 2 06:25:06 UTC 2007 TB --- 2007-11-02 06:25:06 - generating LINT kernel config TB --- 2007-11-02 06:25:06 - cd /src/sys/i386/conf TB --- 2007-11-02 06:25:06 - /usr/bin/make -B LINT TB --- 2007-11-02 06:25:07 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-02 06:25:07 - cd /src TB --- 2007-11-02 06:25:07 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Nov 2 06:25:07 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Fri Nov 2 06:53:54 UTC 2007 TB --- 2007-11-02 06:53:54 - building GENERIC kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-02 06:53:54 - cd /src TB --- 2007-11-02 06:53:54 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Nov 2 06:53:54 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Fri Nov 2 07:16:34 UTC 2007 TB --- 2007-11-02 07:16:34 - building PAE kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-02 07:16:34 - cd /src TB --- 2007-11-02 07:16:34 - /usr/bin/make -B buildkernel KERNCONF=PAE >>> Kernel build for PAE started on Fri Nov 2 07:16:34 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] if_zyd.o(.text+0x3a85): In function `zyd_ioctl': /src/sys/dev/usb/if_zyd.c:2390: undefined reference to `ieee80211_ioctl' if_zyd.o(.text+0x3b35): In function `zyd_media_change': /src/sys/dev/usb/if_zyd.c:673: undefined reference to `ieee80211_media_change' if_zyd.o(.text+0x3cc7): In function `zyd_rx_data': /src/sys/dev/usb/if_zyd.c:1942: undefined reference to `ieee80211_find_rxnode' if_zyd.o(.text+0x3d03):/src/sys/dev/usb/if_zyd.c:1943: undefined reference to `ieee80211_input' if_zyd.o(.text+0x3d0b):/src/sys/dev/usb/if_zyd.c:1947: undefined reference to `ieee80211_free_node' *** Error code 1 Stop in /obj/src/sys/PAE. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-11-02 07:23:35 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-11-02 07:23:35 - ERROR: failed to build PAE kernel TB --- 2007-11-02 07:23:35 - tinderbox aborted TB --- 0.68 user 3.20 system 8615.38 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 08:53:32 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF9EE16A417 for ; Fri, 2 Nov 2007 08:53:32 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.freebsd.org (Postfix) with ESMTP id 5E9F213C4B5 for ; Fri, 2 Nov 2007 08:53:32 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.1/8.14.1) id lA24UitR056722; Thu, 1 Nov 2007 23:30:44 -0500 (CDT) (envelope-from dan) Date: Thu, 1 Nov 2007 23:30:44 -0500 From: Dan Nelson To: "Aryeh M. Friedman" Message-ID: <20071102043043.GI3109@dan.emsphone.com> References: <472A66EE.6060407@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <472A66EE.6060407@gmail.com> X-OS: FreeBSD 7.0-BETA1 User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] prevent install(1) from overwritting symlinks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 08:53:32 -0000 In the last episode (Nov 01), Aryeh M. Friedman said: > The below patch is designed to keep install(1) from overwriting symbolic > links. The motivation is if cups is installed some programs still > expect lpr to be in /usr/bin thus when I install cups I backlink the > /usr/local/bin versions of lp* to /usr/bin. When a build/installworld > is done these links are overwritten and the sym links have to be > performed again. This patch prevents the overwrite. Why not just set WITHOUT_LPR to skip building the base versions entirely? -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 09:28:48 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA91B16A417 for ; Fri, 2 Nov 2007 09:28:48 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id 23C9313C4A8 for ; Fri, 2 Nov 2007 09:28:47 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 84478 invoked from network); 2 Nov 2007 12:21:24 +0300 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 2 Nov 2007 12:21:24 +0300 X-AntiVirus: Checked by Dr.Web [version: 4.44, engine: 4.44.0.09170, virus records: 253277, updated: 2.11.2007] Message-ID: <033a01c81d31$bd180490$0c00a8c0@Artem> From: "Artem Kuchin" To: Date: Fri, 2 Nov 2007 12:21:22 +0300 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="koi8-r"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Subject: Cannot buildworkd on the latest cvsup 7-beta (cvsed 2/11/07) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 09:28:49 -0000 Cvsed the times yesterday and today - every time cannot build world Here is the error; /usr/src/bin/csh/../../contrib/tcsh/sh.func.c: In function 'iconv_catgets': /usr/src/bin/csh/../../contrib/tcsh/sh.func.c:2371: error: 'ICONV_CONST' undeclared (first use in this function) /usr/src/bin/csh/../../contrib/tcsh/sh.func.c:2371: error: (Each undeclared identifier is reported only once /usr/src/bin/csh/../../contrib/tcsh/sh.func.c:2371: error: for each function it appears in.) /usr/src/bin/csh/../../contrib/tcsh/sh.func.c:2371: error: expected ';' before 'char' /usr/src/bin/csh/../../contrib/tcsh/sh.func.c:2377: error: 'src' undeclared (first use in this function) *** Error code 1 Stop in /usr/src/bin/csh. *** Error code 1 Stop in /usr/src/bin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- Artem From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 09:44:33 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB02716A417; Fri, 2 Nov 2007 09:44:33 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from gnome.kiev.sovam.com (gnome.kiev.sovam.com [212.109.32.24]) by mx1.freebsd.org (Postfix) with ESMTP id 7334513C465; Fri, 2 Nov 2007 09:44:33 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from relay02.kiev.sovam.com ([62.64.120.197]) by gnome.kiev.sovam.com with esmtp (Exim 4.67 (FreeBSD)) (envelope-from ) id 1Int4B-000BZw-6a; Fri, 02 Nov 2007 11:43:51 +0200 Received: from [212.82.216.226] (helo=deviant.kiev.zoral.com.ua) by relay02.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1Int49-000Kem-Hn; Fri, 02 Nov 2007 11:43:50 +0200 Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.1/8.14.1) with ESMTP id lA29hj4B075964; Fri, 2 Nov 2007 11:43:45 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.1/8.14.1/Submit) id lA29hjQn075963; Fri, 2 Nov 2007 11:43:45 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 2 Nov 2007 11:43:44 +0200 From: Kostik Belousov To: Mike Pritchard Message-ID: <20071102094344.GC37471@deviant.kiev.zoral.com.ua> References: <862892.31020.qm@web27810.mail.ukl.yahoo.com> <20071101013748.GA1116@mail.mppsystems.com> <200711011123.35870.jhb@freebsd.org> <20071102023634.GA48352@mail.mppsystems.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nQHD+3g9yI+EYXJy" Content-Disposition: inline In-Reply-To: <20071102023634.GA48352@mail.mppsystems.com> User-Agent: Mutt/1.4.2.3i X-Scanner-Signature: f2683d8df775da069012ccac6e6e6321 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 1728 [Nov 02 2007] X-SpamTest-Info: helo_type=3 X-SpamTest-Info: {received from trusted relay: not dialup} X-SpamTest-Method: none X-SpamTest-Method: Local Lists X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0255], KAS30/Release Cc: freebsd-current@freebsd.org, Red Neck Subject: Re: Loader broken in Head? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 09:44:33 -0000 --nQHD+3g9yI+EYXJy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 01, 2007 at 09:36:34PM -0500, Mike Pritchard wrote: > =3D=3D=3D> i386/gptboot (all) > =3D=3D=3D> i386/kgzldr (all) > =3D=3D=3D> i386/libi386 (all) > cc -O2 -fno-strict-aliasing -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=3D0x3f8= -DCOMSPEED=3D9600 -DSMBIOS_SERIAL_NUMBERS -DTERM_EMU -Dalloca=3D__builtin_= alloca -I/shared/src/sys/boot/i386/libi386/../../common -I/shared/src/sys/b= oot/i386/libi386/../btx/lib -I/shared/src/sys/boot/i386/libi386/../../../c= ontrib/dev/acpica -I/shared/src/sys/boot/i386/libi386/../../.. -I. -I/shar= ed/src/sys/boot/i386/libi386/../../../../lib/libstand/ -ffreestanding -mpre= ferred-stack-boundary=3D2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3= -c /shared/src/sys/boot/i386/libi386/biosmem.c > /shared/src/sys/boot/i386/libi386/biosmem.c: In function 'bios_getmem': > /shared/src/sys/boot/i386/libi386/biosmem.c:61: error: 'SMAP_TYPE_MEMORY'= undeclared (first use in this function) > /shared/src/sys/boot/i386/libi386/biosmem.c:61: error: (Each undeclared i= dentifier is reported only once > /shared/src/sys/boot/i386/libi386/biosmem.c:61: error: for each function = it appears in.) > *** Error code 1 >=20 > Stop in /shared/src/sys/boot/i386/libi386. > *** Error code 1 >=20 > Stop in /shared/src/sys/boot/i386. > *** Error code 1 >=20 > Stop in /shared/src/sys/boot. I think that (cd src/include && make all install) shall help. --nQHD+3g9yI+EYXJy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHKvFQC3+MBN1Mb4gRApH7AJ9fs2MTOf0bI94tL42LndEj+ZW8DQCgtYbJ F8HCYjAezr6xclSRDg3o1yQ= =aMJB -----END PGP SIGNATURE----- --nQHD+3g9yI+EYXJy-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 09:46:48 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 971BA16A418 for ; Fri, 2 Nov 2007 09:46:48 +0000 (UTC) (envelope-from ianf@clue.co.za) Received: from munchkin.clue.co.za (munchkin.clue.co.za [66.219.59.160]) by mx1.freebsd.org (Postfix) with ESMTP id 64F8313C48A for ; Fri, 2 Nov 2007 09:46:48 +0000 (UTC) (envelope-from ianf@clue.co.za) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=20070313; d=clue.co.za; h=Received:Received:Received:To:Subject:From:X-Attribution:Date:Message-Id; b=Ecf1SjzXOImgFxIEIFnvDMWn7/EhoAsolZK4XbaXxxGdIQVcLgLcNaGJOCq1/bjKWdmgaBoFKp9qU7925rBXov948PbhoJCsP9so+ZLZIaCngyU0euW3zmYyDXWJ1Gfi2fqhBMJTzZ22JTod7xQdyvkLBwHt03Np3cWhqDWUNOz2w1B43QfxHqO8cfXjZ2uUSJtoLAC9OlQ+6Ki5XIUs/JmTET9dAAXuicUrw1vig/Gd2VbR/L9XkrOwYNdNrfk6; Received: from uucp by munchkin.clue.co.za with local-rmail (Exim 4.67) (envelope-from ) id 1Int6Q-0007Zb-N0 for current@freebsd.org; Fri, 02 Nov 2007 09:46:10 +0000 Received: from ianf.clue.co.za ([10.0.0.6] helo=clue.co.za) by urchin.clue.co.za with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.66) (envelope-from ) id 1Int6C-000558-01 for current@freebsd.org; Fri, 02 Nov 2007 09:45:56 +0000 Received: from localhost ([127.0.0.1] helo=clue.co.za) by clue.co.za with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1Int69-0000bA-NO for current@freebsd.org; Fri, 02 Nov 2007 11:45:53 +0200 To: current@freebsd.org From: Ian FREISLICH X-Attribution: BOFH Date: Fri, 02 Nov 2007 11:45:53 +0200 Message-Id: Cc: Subject: sendfile() not detecting closed connections. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 09:46:48 -0000 Hi System is 8.0-CURRENT. I have the following piece of code: rename(path, data); stat(data, &sb); len = snprintf(buffer, MAXBUFLEN, "BYTES %lld\r\n", sb.st_size); write(connection, buffer, len); sleep(10); if ((sendfile(fd, connection, 0, sb.st_size, NULL, &sbytes, 0)) == -1 || sbytes != sb.st_size) { syslog(facility, "Problem writing data: %s, wrote %lld", strerror(errno), sbytes); respool(fd, path); unlink(data) close(fd); return(-1); } else syslog(facility, "Download successful %ld", sbytes); close(fd); unlink(data); If, during the sleep, I terminate the connection so that netstat reports: tcp4 0 0 127.0.0.1.666 127.0.0.1.58239 CLOSE_WAIT tcp4 0 0 127.0.0.1.58239 127.0.0.1.666 FIN_WAIT_2 sendfile() reports success for files less than about 64k in size, but I haven't been able to figure out where the threshold is. It erroneously reports that 41000 of the 64k were sent, but will say the whole file was transferred up to about 64k. The connection filedescriptor is blocking. Any ideas? Ian -- Ian Freislich From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 10:21:22 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 53C0716A420 for ; Fri, 2 Nov 2007 10:21:22 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id EB98313C4A8 for ; Fri, 2 Nov 2007 10:21:21 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 4F2E845E90; Fri, 2 Nov 2007 10:55:12 +0100 (CET) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id EF4A545EEB; Fri, 2 Nov 2007 10:55:07 +0100 (CET) Date: Fri, 2 Nov 2007 10:55:07 +0100 From: Pawel Jakub Dawidek To: Dag-Erling Sm??rgrav Message-ID: <20071102095506.GC24455@garage.freebsd.pl> References: <0fbb01c81be1$37e698f0$0c00a8c0@Artem> <863avptzir.fsf@ds4.des.no> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="raC6veAxrt5nqIoY" Content-Disposition: inline In-Reply-To: <863avptzir.fsf@ds4.des.no> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: Artem Kuchin , freebsd-current@freebsd.org Subject: Re: BIO_FLUSH on twe driver. Why is it not there? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 10:21:22 -0000 --raC6veAxrt5nqIoY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 01, 2007 at 10:41:00PM +0100, Dag-Erling Sm??rgrav wrote: > "Artem Kuchin" writes: > > However, twe is working via scsi subsystem and the authour of gjournal > > said somewhere that he has had implemeneted BIO_FLISH for scsi and he > > specifically mentioned that he has tested twe and twa and they both > > support BIO_FLUSH. >=20 > twa(4) uses CAM, but twe(4) doesn't (and never has). That was my mistake. Someone told me (I think it was jhb@), that twe(4) turns off write cache automatically when there is no battery, so BIO_FLUSH isn't really needed and if there is a battery, it also isn't really needed. It would be nice to hide the warning in this case somehow, but for now you should be safe by simply ignoring the warning. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --raC6veAxrt5nqIoY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHKvP6ForvXbEpPzQRArC1AKDYt++IZRHMNGw34YSCRYP/PcyPMACfdYfZ wKmuBESlc++ufx3fCI8vh9k= =gA6r -----END PGP SIGNATURE----- --raC6veAxrt5nqIoY-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 10:21:22 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5574C16A421 for ; Fri, 2 Nov 2007 10:21:22 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id ADB3C13C4A3 for ; Fri, 2 Nov 2007 10:21:21 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id C3FDF45E93; Fri, 2 Nov 2007 10:52:11 +0100 (CET) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id C3C28456AB; Fri, 2 Nov 2007 10:52:07 +0100 (CET) Date: Fri, 2 Nov 2007 10:52:06 +0100 From: Pawel Jakub Dawidek To: Thierry Herbelot Message-ID: <20071102095206.GB24455@garage.freebsd.pl> References: <200711011509.46094.thierry@herbelot.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TakKZr9L6Hm6aLOc" Content-Disposition: inline In-Reply-To: <200711011509.46094.thierry@herbelot.com> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-current@freebsd.org Subject: Re: regression with gmirror, Promise SATA and 7.0 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 10:21:22 -0000 --TakKZr9L6Hm6aLOc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 01, 2007 at 03:09:45PM +0100, Thierry Herbelot wrote: > Hello, >=20 > I have tried to switch my home server from a 6.3-PRERELEASE to the latest= =20 > 7.0-BETA1.5-i386-disc1.iso. >=20 > I have loopback-mounted the iso and unarchived the base and kernel to a n= ew=20 > gmirrored partition hosted on two "Seagate ST3250823AS" SATA disks connec= ted=20 > via a "Promise PDC40518 SATA150" controller. >=20 > after rebooting to the new "current" gmirror partition, any disk access g= ives=20 > errors such as : > ad6: WARNING - READ_DMA UDMA ICRC error (retrying request) LBA=3D58616578 > ad6: FAILURE - device detached > subdisk6: detached > ad6: detached > GEOM_MIRROR: Cannot write metadata on ad6s3 (device=3Dgm0s3, error=3D6). > GEOM_MIRROR: Cannot update metadata on disk ad6s3 (error=3D6). > GEOM_MIRROR: Device gm0s4: provider ad6s4 disconnected. > GEOM_MIRROR: Device gm0s2: provider ad6s2 disconnected. > GEOM_MIRROR: Device gm0s1: provider ad6s1 disconnected. > ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - complet= ing=20 > request directly > ad10: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - complet= ing=20 > request directly > ad10: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing= =20 > request directly > ad10: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing= =20 > request directly > ad10: WARNING - SET_MULTI taskqueue timeout - completing request directly > ad10: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=3D62894473 > GEOM_MIRROR: Cannot update metadata on disk ad6s3 (error=3D6). > GEOM_MIRROR: Device gm0s3: provider ad6s3 disconnected. > g_vfs_done():mirror/gm0s3f[READ(offset=3D5429510144, length=3D65536)]erro= r =3D 6 > vnode_pager_getpages: I/O read error >=20 > The same ad6 and ad10 disks are presently used under 6.x without any (vis= bile)=20 > errors (and have been for more than one year). >=20 > Thus, it seems that the combination of this Promise controller and the SA= TA=20 > disks has issues (there was a thread about Promise controllers and ZFS, b= ut=20 > with no clear conclusion). Just to clarify. There is no regression in gmirror. This is ATA problem/bug, which was reported so many times already. > PS : I was also burnt by the forced conversion of gmirror metadata from v= 3 to=20 > v4, which makes it tricky to backtrack to 6.x, once a 7.x kernel + gmirro= r=20 > has been booted once. I'm not happy with with metadata auto-upgrade, but it just makes things so much easier. You can always boot your 6.x to single-user mode using disk directly (it should not change anything on disk) and just run 'gmirror label' again. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --TakKZr9L6Hm6aLOc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHKvNGForvXbEpPzQRAh4+AJ0Rw7RgR2JNTyZfyOCHZwHjqDREsQCgy3Su CNKYQV6v1pI8dr9GO2CwPH8= =aFsv -----END PGP SIGNATURE----- --TakKZr9L6Hm6aLOc-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 10:25:22 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A61DD16A46B for ; Fri, 2 Nov 2007 10:25:22 +0000 (UTC) (envelope-from freebsd@superhero.nl) Received: from superman.superhero.nl (superhero.nl [82.95.198.17]) by mx1.freebsd.org (Postfix) with ESMTP id 114E013C4AA for ; Fri, 2 Nov 2007 10:25:21 +0000 (UTC) (envelope-from freebsd@superhero.nl) Received: (qmail 71117 invoked by uid 80); 2 Nov 2007 10:17:35 -0000 Received: from 195.50.100.20 (SquirrelMail authenticated user gelsemap) by www.superhero.nl with HTTP; Fri, 2 Nov 2007 11:17:35 +0100 (CET) Message-ID: <15769.195.50.100.20.1193998655.squirrel@www.superhero.nl> In-Reply-To: <472A063B.1030201@samsco.org> References: <1154.80.127.127.95.1193916692.squirrel@webmail.superhero.nl> <20071101154109.GA59070@eos.sc1.parodius.com> <63660.195.50.100.20.1193931900.squirrel@www.superhero.nl> <472A063B.1030201@samsco.org> Date: Fri, 2 Nov 2007 11:17:35 +0100 (CET) From: "Gelsema, P \(Patrick\) - FreeBSD" To: "Scott Long" User-Agent: SquirrelMail/1.4.8 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: Jeremy Chadwick , freebsd-current@freebsd.org, "Gelsema, P \(Patrick\) - FreeBSD" Subject: Re: da0 detection garbled: da0: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 10:25:22 -0000 On Thu, November 1, 2007 18:00, Scott Long wrote: > Gelsema, P (Patrick) - FreeBSD wrote: >> On Thu, November 1, 2007 16:41, Jeremy Chadwick wrote: >>> On Thu, Nov 01, 2007 at 12:31:32PM +0100, Gelsema, P (Patrick) - >>> FreeBSD >>> wrote: >>>> da0: >>>> >>>> Please let me know if more information is required. >>> This was discussed in October. See the thread here: >>> >>> http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078145.html >>> >> >> I did check the lists as I am subscribed. Must have missed this :( >> >> Anyways.. I still got the issue where the disks are detected as only >> 160.00 MB instead as 320.00MB as in RELENG_6_3. >> > > The speed issue is a big one that I haven't had time to address, and I > don't know if I'll be able to address it before 7.0 is released since it > involves some pretty significant and delicate work. In the mean time, > try running the following after the system is up: > > camcontrol negotiate da0 -a -R 160 > No change between current Parameters and New paramaters. When I am at the console again I can turn off the domain validation on the Adaptec card in the bios. Any use for trying this? Rgds, Patrick > Scott > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 10:27:37 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81CCD16A417; Fri, 2 Nov 2007 10:27:37 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from spider.deepcore.dk (cpe.atm2-0-70484.0x50a6c9a6.abnxx16.customer.tele.dk [80.166.201.166]) by mx1.freebsd.org (Postfix) with ESMTP id 0307D13C4A8; Fri, 2 Nov 2007 10:27:36 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from ws.local (ws.deepcore.dk [194.192.25.137]) by spider.deepcore.dk (8.13.8/8.13.8) with ESMTP id lA2AR1sA063797; Fri, 2 Nov 2007 11:27:01 +0100 (CET) (envelope-from sos@deepcore.dk) Message-ID: <472AFB75.1070207@deepcore.dk> Date: Fri, 02 Nov 2007 11:27:01 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Alexander Sabourenkov References: <472A548B.50406@lxnt.info> In-Reply-To: <472A548B.50406@lxnt.info> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@FreeBSD.ORG, sos@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, "Matthew D. Fuller" , Thierry Herbelot Subject: Re: Patch RFC: Promise SATA300 TX4 hardware bug workaround. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 10:27:37 -0000 Alexander Sabourenkov wrote: > Hello. > > I have ported the workaround for the hardware bug that causes data > corruption on Promise SATA300 TX4 cards to RELENG_7. > > Bug description: > SATA300 TX4 hardware chokes if last PRD entry (in a dma transfer) is > larger than 164 bytes. This was found while analysing vendor-supplied > linux driver. > > Workaround: > Split trailing PRD entry if it's larger that 164 bytes. > > Two supplied patches do fix problem on my machine. > > There is, however, a style problem with them. It seems like PRD entry > count is limited at 256. I have not found a good way to guarantee that > one entry is always available to do the split, thus the ugly solution o= f > patching ata-dma.c. > =20 Good catch! However from my quick glimpse at the Promise sources the limit seems to=20 be 32 Dwords ie 32*4 =3D 128bytes. I'll investigate further and ask Promise for the gory details, stay tuned= =2E.. I dont think the PRD count limitation is a real problem, I've newer seen = that long a list and IIRC we newer do more than 64K transfers in one go=20 (yet). Anyhow I need to get checks in for that not just here... Give me a few days and I'll get this figured out for 7-rel... -S=F8ren > > Patches, patched and original files are at http://lxnt.info/tx4/freebsd= /. > > > --- ata-chipset.c.orig 2007-11-02 01:05:49.000000000 +0300 > +++ ata-chipset.c 2007-11-02 01:05:49.000000000 +0300 > @@ -142,6 +142,7 @@ > static int ata_promise_mio_command(struct ata_request *request); > static void ata_promise_mio_reset(device_t dev); > static void ata_promise_mio_dmainit(device_t dev); > +static void ata_promise_mio_dmasetprd(void *xsc, bus_dma_segment_t > *segs, int nsegs, int error); > static void ata_promise_mio_setmode(device_t dev, int mode); > static void ata_promise_sx4_intr(void *data); > static int ata_promise_sx4_command(struct ata_request *request); > @@ -185,7 +186,6 @@ > static int ata_check_80pin(device_t dev, int mode); > static int ata_mode2idx(int mode); > > - > /* > * generic ATA support functions > */ > @@ -3759,8 +3759,44 @@ > static void > ata_promise_mio_dmainit(device_t dev) > { > + struct ata_channel *ch =3D device_get_softc(dev); > +=09 > /* note start and stop are not used here */ > ata_dmainit(dev); > + > + if (ch->dma) > + ch->dma->setprd =3D ata_promise_mio_dmasetprd; > +} > + > +static void > +ata_promise_mio_dmasetprd(void *xsc, bus_dma_segment_t *segs, int > nsegs, int error) > +{ > + #define PDC_MAXLASTSGSIZE 41*4 > + struct ata_dmasetprd_args *args =3D xsc; > + struct ata_dma_prdentry *prd =3D args->dmatab; > + int i; > + > + if ((args->error =3D error)) > + return; > + > + for (i =3D 0; i < nsegs; i++) { > + prd[i].addr =3D htole32(segs[i].ds_addr); > + prd[i].count =3D htole32(segs[i].ds_len); > + } > + > + if (segs[i - 1].ds_len > PDC_MAXLASTSGSIZE) { > + /* > + printf("splitting trailing PRD of %ld (limit %d)\n", segs[i - > 1].ds_len, PDC_MAXLASTSGSIZE); > + */ > + prd[i - 1].count =3D htole32(segs[i - 1].ds_len - PDC_MAXLASTSGSIZE);= > + prd[i].count =3D htole32(PDC_MAXLASTSGSIZE); > + prd[i].addr =3D htole32(segs[i - 1].ds_addr + PDC_MAXLASTSGSIZE); > + i ++; > + nsegs ++; > + } > + > + prd[i - 1].count |=3D htole32(ATA_DMA_EOT); > + args->nsegs =3D nsegs; > } > > static void > > --- ata-dma.c.orig 2007-11-02 01:05:53.000000000 +0300 > +++ ata-dma.c 2007-11-02 01:05:53.000000000 +0300 > @@ -113,7 +113,7 @@ > if > (bus_dma_tag_create(ch->dma->dmatag,ch->dma->alignment,ch->dma->boundar= y, > ch->dma->max_address, BUS_SPACE_MAXADDR, > NULL, NULL, ch->dma->max_iosize, > - ATA_DMA_ENTRIES, ch->dma->segsize, > + ATA_DMA_ENTRIES - 1, ch->dma->segsize, > 0, NULL, NULL, &ch->dma->data_tag)) > goto error; > > > =20 From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 10:31:40 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92B7916A41B for ; Fri, 2 Nov 2007 10:31:40 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id BCA5113C4A6 for ; Fri, 2 Nov 2007 10:31:39 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 86746 invoked from network); 2 Nov 2007 13:30:45 +0300 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 2 Nov 2007 13:30:45 +0300 X-AntiVirus: Checked by Dr.Web [version: 4.44, engine: 4.44.0.09170, virus records: 253279, updated: 2.11.2007] Message-ID: <038501c81d3b$6d6460b0$0c00a8c0@Artem> From: "Artem Kuchin" To: "Pawel Jakub Dawidek" , "Dag-Erling Sm??rgrav" References: <0fbb01c81be1$37e698f0$0c00a8c0@Artem> <863avptzir.fsf@ds4.des.no> <20071102095506.GC24455@garage.freebsd.pl> Date: Fri, 2 Nov 2007 13:15:51 +0300 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Cc: freebsd-current@freebsd.org Subject: Re: BIO_FLUSH on twe driver. Why is it not there? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 10:31:40 -0000 >> > However, twe is working via scsi subsystem and the authour of gjournal >> > said somewhere that he has had implemeneted BIO_FLISH for scsi and he >> > specifically mentioned that he has tested twe and twa and they both >> > support BIO_FLUSH. >> >> twa(4) uses CAM, but twe(4) doesn't (and never has). > >That was my mistake. Someone told me (I think it was jhb@), that twe(4) >turns off write cache automatically when there is no battery, so >BIO_FLUSH isn't really needed and if there is a battery, it also isn't >really needed. It would be nice to hide the warning in this case >somehow, but for now you should be safe by simply ignoring the warning. Um.. If battry is not installed write can be enabled easily. Here is my setting: Unit Write Cache (Controller ID 0) Unit 2 [RAID 1] Enabled Is your phrase "it also isn't really needed' related to this case too? 'Cause you said if BIO_FLUSH is not there and write cache is bigger than gjorunal's cache there could be trouble. Cache on my controller is 64MB, what;s the size of gjournal's cache? -- Artem From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 10:42:07 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7565B16A417; Fri, 2 Nov 2007 10:42:07 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from spider.deepcore.dk (cpe.atm2-0-70484.0x50a6c9a6.abnxx16.customer.tele.dk [80.166.201.166]) by mx1.freebsd.org (Postfix) with ESMTP id 0C6AE13C447; Fri, 2 Nov 2007 10:42:06 +0000 (UTC) (envelope-from sos@deepcore.dk) Received: from ws.local (ws.deepcore.dk [194.192.25.137]) by spider.deepcore.dk (8.13.8/8.13.8) with ESMTP id lA2Af7Ij063961; Fri, 2 Nov 2007 11:41:07 +0100 (CET) (envelope-from sos@deepcore.dk) Message-ID: <472AFEC3.7090001@deepcore.dk> Date: Fri, 02 Nov 2007 11:41:07 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Alexander Sabourenkov References: <472A548B.50406@lxnt.info> <472AFB75.1070207@deepcore.dk> In-Reply-To: <472AFB75.1070207@deepcore.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@FreeBSD.ORG, sos@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, "Matthew D. Fuller" , Thierry Herbelot Subject: Re: Patch RFC: Promise SATA300 TX4 hardware bug workaround. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 10:42:07 -0000 S=F8ren Schmidt wrote: > Good catch! > > However from my quick glimpse at the Promise sources the limit seems=20 > to be 32 Dwords ie 32*4 =3D 128bytes. > I'll investigate further and ask Promise for the gory details, stay=20 > tuned... > I dont think the PRD count limitation is a real problem, I've newer=20 > seen that long a list and IIRC we newer do more than 64K transfers in=20 > one go (yet). > Anyhow I need to get checks in for that not just here... > > Give me a few days and I'll get this figured out for 7-rel... Oh, and I forgot, do you have a surefire way to reproduce the problem so = the fix can be tested ? I've newer been able to trigger this problem myself so far. -S=F8ren From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 10:57:53 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86D7416A417; Fri, 2 Nov 2007 10:57:53 +0000 (UTC) (envelope-from screwdriver@lxnt.info) Received: from mail.lxnt.info (mail.lxnt.info [217.23.143.142]) by mx1.freebsd.org (Postfix) with ESMTP id 426D813C4A5; Fri, 2 Nov 2007 10:57:53 +0000 (UTC) (envelope-from screwdriver@lxnt.info) Received: from [217.23.131.8] (helo=lxnt.inside.caravan.ru) by mail.lxnt.info with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1InuDX-000OY8-2f; Fri, 02 Nov 2007 13:57:35 +0300 Message-ID: <472B02B5.9020502@lxnt.info> Date: Fri, 02 Nov 2007 13:57:57 +0300 From: Alexander Sabourenkov User-Agent: Thunderbird 2.0.0.6 (X11/20071024) MIME-Version: 1.0 To: =?UTF-8?B?U8O4cmVuIFNjaG1pZHQ=?= References: <472A548B.50406@lxnt.info> <472AFB75.1070207@deepcore.dk> <472AFEC3.7090001@deepcore.dk> In-Reply-To: <472AFEC3.7090001@deepcore.dk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-hackers@FreeBSD.ORG, sos@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, "Matthew D. Fuller" , Thierry Herbelot Subject: Re: Patch RFC: Promise SATA300 TX4 hardware bug workaround. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 10:57:53 -0000 Søren Schmidt wrote: > Søren Schmidt wrote: >> Good catch! >> >> However from my quick glimpse at the Promise sources the limit seems >> to be 32 Dwords ie 32*4 = 128bytes. Please see driver named 4_sataii150-300_linux2.6-src_x86-64_v1.01.0.23 >> I'll investigate further and ask Promise for the gory details, stay >> tuned... >> I dont think the PRD count limitation is a real problem, I've newer >> seen that long a list and IIRC we newer do more than 64K transfers in >> one go (yet). In (current) practice, yes, but check should be there even if only to document the limit. >> Anyhow I need to get checks in for that not just here... >> >> Give me a few days and I'll get this figured out for 7-rel... > Oh, and I forgot, do you have a surefire way to reproduce the problem so > the fix can be tested ? dd if=/dev/ad8 of=/dev/null bs=1048576 count=1000 works every time. I have tested it on my home machine: without the patch first timeouts and errors appear about 10 seconds into the read. with the patch a read of entire disk (320G) completed without errors. Previous tests of analogous linux driver fix shown no errors and no data corruption on two write-whole-drive, read-whole-drive cycles. > > I've newer been able to trigger this problem myself so far. > Seems like the bug is highly configuration-dependent, or pci-chiset-depended, or just present in some production runs and not other. -- ./lxnt From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 11:25:51 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9FE816A417 for ; Fri, 2 Nov 2007 11:25:51 +0000 (UTC) (envelope-from root@solink.ru) Received: from solink.academ.org (solink.academ.org [85.118.228.14]) by mx1.freebsd.org (Postfix) with ESMTP id 4B3A613C4B3 for ; Fri, 2 Nov 2007 11:25:50 +0000 (UTC) (envelope-from root@solink.ru) Received: from bocha.solink.office (bocha.solink.office [192.168.1.100]) by solink.academ.org (8.13.8/8.13.8) with ESMTP id lA29uoKJ081663 for ; Fri, 2 Nov 2007 15:56:51 +0600 (NOVT) (envelope-from root@solink.ru) From: Bachilo Dmitry Organization: Solink Ltd To: current@freebsd.org User-Agent: KMail/1.9.6 MIME-Version: 1.0 Content-Disposition: inline Date: Fri, 2 Nov 2007 15:54:49 +0600 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Message-Id: <200711021554.49567.root@solink.ru> Cc: Subject: PCMCIA RS232 card X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 11:25:52 -0000 Good day, All. I wonder if there can something be done to make the subject work. When I plug it in it says: cardbus0: at device 0.0 (no driver attached) As far as I know, FreeBSD supports this type of cards (with puc driver?), b= ut=20 I've tried hard and got nowhere. It is an "STlab RS232 Serial adapter".=20 What additional information from me is required? Thanks in advance. Best regards, Dmitry Bachilo (I think my previous message was lost somehow, so i've repeated it, if it's= =20 doubled, please excuse me) =2D-=20 =F3 =D5=D7=C1=D6=C5=CE=C9=C5=CD,=20 =E2=C1=DE=C9=CC=CF =E4=CD=C9=D4=D2=C9=CA =F2=D5=CB=CF=D7=CF=C4=C9=D4=C5=CC=D8 =CF=D4=C4=C5=CC=C1 =D3=C9=D3=D4=C5=CD= =CE=CF=CA =C9=CE=D4=C5=C7=D2=C1=C3=C9=C9 =EF=EF=EF "=EB=CF=CD=D0=C1=CE=C9=D1 =F3=CF=CC=C9=CE=CB" root@solink.ru From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 11:25:53 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D06B16A419 for ; Fri, 2 Nov 2007 11:25:53 +0000 (UTC) (envelope-from root@solink.ru) Received: from solink.academ.org (solink.academ.org [85.118.228.14]) by mx1.freebsd.org (Postfix) with ESMTP id B1ED313C4B6 for ; Fri, 2 Nov 2007 11:25:52 +0000 (UTC) (envelope-from root@solink.ru) Received: from bocha.solink.office (bocha.solink.office [192.168.1.100]) by solink.academ.org (8.13.8/8.13.8) with ESMTP id lA29rVVY081594 for ; Fri, 2 Nov 2007 15:53:31 +0600 (NOVT) (envelope-from root@solink.ru) From: Bachilo Dmitry Organization: Solink Ltd To: current@freebsd.org User-Agent: KMail/1.9.6 MIME-Version: 1.0 Content-Disposition: inline Date: Fri, 2 Nov 2007 15:51:29 +0600 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: base64 Message-Id: <200711021551.29545.root@solink.ru> Cc: Subject: PCMCIA RS232 card X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 11:25:53 -0000 R29vZCBkYXksIEFsbC4KSSB3b25kZXIgaWYgdGhlcmUgY2FuIHNvbWV0aGluZyBiZSBkb25lIHRv IG1ha2UgdGhlIHN1YmplY3Qgd29yay4KV2hlbiBJIHBsdWcgaXQgaW4gaXQgc2F5czoKY2FyZGJ1 czA6IDxzaW1wbGUgY29tbXMsIFVBUlQ+IGF0IGRldmljZSAwLjAgKG5vIGRyaXZlciBhdHRhY2hl ZCkKQXMgZmFyIGFzIEkga25vdywgRnJlZUJTRCBzdXBwb3J0cyB0aGlzIHR5cGUgb2YgY2FyZHMg KHdpdGggcHVjIGRyaXZlcj8pLCBidXQgCkkndmUgdHJpZWQgaGFyZCBhbmQgZ290IG5vd2hlcmUu IEl0IGlzIGFuICJTVGxhYiBSUzIzMiBTZXJpYWwgYWRhcHRlciIuIApXaGF0IGFkZGl0aW9uYWwg aW5mb3JtYXRpb24gZnJvbSBtZSBpcyByZXF1aXJlZD8KVGhhbmtzIGluIGFkdmFuY2UuCkJlc3Qg cmVnYXJkcywgRG1pdHJ5IEJhY2hpbG8KLS0gCvMg1dfB1sXOycXNLCAK4sHeyczPIOTNydTSycoK 8tXLz9fPxMnUxczYIM/UxMXMwSDTydPUxc3Oz8ogyc7UxcfSwcPJyQrv7+8gIuvPzdDBzsnRIPPP zMnOyyIKcm9vdEBzb2xpbmsucnUK From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 08:18:42 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B277916A421; Fri, 2 Nov 2007 08:18:42 +0000 (UTC) (envelope-from mpp@mppsystems.com) Received: from mail4.gulftel.com (mail4.gulftel.com [216.231.163.45]) by mx1.freebsd.org (Postfix) with ESMTP id 8AA2813C4A6; Fri, 2 Nov 2007 08:18:42 +0000 (UTC) (envelope-from mpp@mppsystems.com) Received: from localhost (localhost [127.0.0.1]) by mail4.gulftel.com (Postfix) with ESMTP id 0B196F1F6; Fri, 2 Nov 2007 02:09:01 -0500 (CDT) X-Virus-Scanned: amavisd-new at gulftel.com Received: from mail4.gulftel.com ([127.0.0.1]) by localhost (mail4.gulftel.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P9AZ8AFGtNM0; Fri, 2 Nov 2007 02:09:00 -0500 (CDT) Received: from mail.mppsystems.com (unknown [10.17.28.253]) by mail4.gulftel.com (Postfix) with ESMTP id 1276011A39; Thu, 1 Nov 2007 23:13:38 -0500 (CDT) Received: by mail.mppsystems.com (Postfix, from userid 1000) id 5927A17025; Thu, 1 Nov 2007 23:13:38 -0500 (CDT) Date: Thu, 1 Nov 2007 23:13:38 -0500 From: Mike Pritchard To: John Baldwin Message-ID: <20071102041338.GA1064@mail.mppsystems.com> References: <862892.31020.qm@web27810.mail.ukl.yahoo.com> <20071101013748.GA1116@mail.mppsystems.com> <200711011123.35870.jhb@freebsd.org> <20071102023634.GA48352@mail.mppsystems.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20071102023634.GA48352@mail.mppsystems.com> User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Mailman-Approved-At: Fri, 02 Nov 2007 11:44:09 +0000 Cc: freebsd-current@freebsd.org, Red Neck , Mike Pritchard Subject: Re: Loader broken in Head? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 08:18:42 -0000 On Thu, Nov 01, 2007 at 09:36:34PM -0500, Mike Pritchard wrote: > > I'd be glad to try, if you could tell me how to build the loader... > or if I'm building it correctly, if someone could fix this compile > error I see (see below). And the couple of warnings I see compiling make > me nervous too. I don't want to mess around too much until I'm sure > I'm building it correctly, because I'd like to leave this machine bootable :) > > Other than that, if a fresh -current loader still doesn't fix my > problem, I'm more than willing to start backing out recent commits > to find which commit might be the problem. > > With 8.0-current sources as of a couple of hours ago, I > get the same compile error trying any of these: Nevermind about the compiling part. Pilot error. Stale includes are to blame. a make world fixed all that. And a -current loader as of today works just fine. I'd suggest that to Red Neck also to see if it clears up his problem. Now where did I put that pointy hat... -- Mike Pritchard mpp @ FreeBSD.org "If tyranny and oppression come to this land, it will be in the guise of fighting a foreign enemy." - James Madison (1787) From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 12:57:17 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 462C016A418; Fri, 2 Nov 2007 12:57:17 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id F29A313C48A; Fri, 2 Nov 2007 12:57:16 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: by blah.sun-fish.com (Postfix, from userid 1002) id BF8071B10EE9; Fri, 2 Nov 2007 13:56:54 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on blah.cmotd.com X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.3 Received: from [10.1.1.3] (unknown [192.168.25.14]) by blah.sun-fish.com (Postfix) with ESMTP id 6991B1B10EE6; Fri, 2 Nov 2007 13:56:50 +0100 (CET) Message-ID: <472B1E89.5080006@moneybookers.com> Date: Fri, 02 Nov 2007 14:56:41 +0200 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.91.2/4660/Fri Nov 2 13:13:54 2007 on blah.cmotd.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: rtfree: 0xc741ee88 has 1 refs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 12:57:17 -0000 Hi, I see rtfree: 0xc741ee88 has 1 refs with freebsd releng_7 (i386) from today. I think it's easy reproducible. What I have is: releng_7 (10.1.1.2) -> default GW (10.1.1.1) on default GW I have route to 10.10.1.1/24 -> 10.1.1.3 so everytime when 10.1.1.2 try to contact someone from 10.10.1.1/24 I see: rtfree: 0xc741ee88 has 1 refs if I add direct route on 10.1.1.2 to 10.10.1.1/24 through 10.1.1.3 the message will go away. Should I ignore this msg for now, or should I expect kernel panic soon? :) From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 19:17:12 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB54A16A46C; Fri, 2 Nov 2007 19:17:12 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id 3DCBE13C4C2; Fri, 2 Nov 2007 19:17:05 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.14.1/8.13.8) with ESMTP id lA2Em8h3023218; Fri, 2 Nov 2007 10:48:08 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.14.1/8.14.1) with ESMTP id lA2Em7vY076309; Fri, 2 Nov 2007 10:48:07 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id AA14C73068; Fri, 2 Nov 2007 09:48:07 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20071102144807.AA14C73068@freebsd-current.sentex.ca> Date: Fri, 2 Nov 2007 09:48:07 -0500 (EST) X-Virus-Scanned: ClamAV 0.91.2/4641/Tue Oct 30 15:59:09 2007 clamav-milter version 0.91.2 on clamscanner5 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 19:17:12 -0000 TB --- 2007-11-02 12:25:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-11-02 12:25:00 - starting HEAD tinderbox run for i386/i386 TB --- 2007-11-02 12:25:01 - cleaning the object tree TB --- 2007-11-02 12:25:31 - checking out the source tree TB --- 2007-11-02 12:25:31 - cd /tinderbox/HEAD/i386/i386 TB --- 2007-11-02 12:25:31 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-11-02 12:34:00 - building world (CFLAGS=-O2 -pipe) TB --- 2007-11-02 12:34:00 - cd /src TB --- 2007-11-02 12:34:00 - /usr/bin/make -B buildworld >>> World build started on Fri Nov 2 12:34:02 UTC 2007 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Nov 2 13:49:58 UTC 2007 TB --- 2007-11-02 13:49:58 - generating LINT kernel config TB --- 2007-11-02 13:49:58 - cd /src/sys/i386/conf TB --- 2007-11-02 13:49:58 - /usr/bin/make -B LINT TB --- 2007-11-02 13:49:58 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-02 13:49:58 - cd /src TB --- 2007-11-02 13:49:58 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Nov 2 13:49:58 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Fri Nov 2 14:18:42 UTC 2007 TB --- 2007-11-02 14:18:42 - building GENERIC kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-02 14:18:42 - cd /src TB --- 2007-11-02 14:18:42 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Nov 2 14:18:43 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Fri Nov 2 14:41:01 UTC 2007 TB --- 2007-11-02 14:41:01 - building PAE kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-02 14:41:01 - cd /src TB --- 2007-11-02 14:41:01 - /usr/bin/make -B buildkernel KERNCONF=PAE >>> Kernel build for PAE started on Fri Nov 2 14:41:02 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] if_zyd.o(.text+0x3a85): In function `zyd_ioctl': /src/sys/dev/usb/if_zyd.c:2390: undefined reference to `ieee80211_ioctl' if_zyd.o(.text+0x3b35): In function `zyd_media_change': /src/sys/dev/usb/if_zyd.c:673: undefined reference to `ieee80211_media_change' if_zyd.o(.text+0x3cc7): In function `zyd_rx_data': /src/sys/dev/usb/if_zyd.c:1942: undefined reference to `ieee80211_find_rxnode' if_zyd.o(.text+0x3d03):/src/sys/dev/usb/if_zyd.c:1943: undefined reference to `ieee80211_input' if_zyd.o(.text+0x3d0b):/src/sys/dev/usb/if_zyd.c:1947: undefined reference to `ieee80211_free_node' *** Error code 1 Stop in /obj/src/sys/PAE. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-11-02 14:48:07 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-11-02 14:48:07 - ERROR: failed to build PAE kernel TB --- 2007-11-02 14:48:07 - tinderbox aborted TB --- 0.85 user 3.10 system 8586.48 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 19:30:28 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B2EF16A417 for ; Fri, 2 Nov 2007 19:30:28 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [IPv6:2001:770:10:300::86e2:510b]) by mx1.freebsd.org (Postfix) with SMTP id 6046113C4A3 for ; Fri, 2 Nov 2007 19:30:27 +0000 (UTC) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 2 Nov 2007 15:55:35 +0000 (GMT) Date: Fri, 2 Nov 2007 15:55:35 +0000 From: David Malone To: Ian FREISLICH Message-ID: <20071102155535.GA88062@walton.maths.tcd.ie> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: current@freebsd.org Subject: Re: setitimer() odd timing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 19:30:28 -0000 On Thu, Nov 01, 2007 at 03:38:11PM +0200, Ian FREISLICH wrote: > I'm not sure where to start looking. If someone points me at what > needs instrumenting, I'll see if I can narrow the problem space. I'd have a look at the output of "vmstat -i" and compare it to the working machines. It might also be worth checking what timecounter hardware is in use: "sysctl kern.timecounter.hardware". David. From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 19:36:42 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 43D3716A420 for ; Fri, 2 Nov 2007 19:36:42 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id AD79713C48E for ; Fri, 2 Nov 2007 19:36:41 +0000 (UTC) (envelope-from andre@freebsd.org) Received: (qmail 66807 invoked from network); 2 Nov 2007 18:13:02 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 2 Nov 2007 18:13:02 -0000 Message-ID: <472B6E24.20200@freebsd.org> Date: Fri, 02 Nov 2007 19:36:20 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: Ian FREISLICH References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: sendfile() not detecting closed connections. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 19:36:42 -0000 Ian FREISLICH wrote: > Hi > > System is 8.0-CURRENT. I have the following piece of code: > > rename(path, data); > stat(data, &sb); > len = snprintf(buffer, MAXBUFLEN, "BYTES %lld\r\n", sb.st_size); > write(connection, buffer, len); > sleep(10); > if ((sendfile(fd, connection, 0, sb.st_size, NULL, > &sbytes, 0)) == -1 || sbytes != sb.st_size) { > syslog(facility, "Problem writing data: %s, wrote %lld", > strerror(errno), sbytes); > respool(fd, path); > unlink(data) > close(fd); > return(-1); > } > else > syslog(facility, "Download successful %ld", sbytes); > close(fd); > unlink(data); > > If, during the sleep, I terminate the connection so that netstat > reports: > > tcp4 0 0 127.0.0.1.666 127.0.0.1.58239 CLOSE_WAIT > tcp4 0 0 127.0.0.1.58239 127.0.0.1.666 FIN_WAIT_2 > > sendfile() reports success for files less than about 64k in size, > but I haven't been able to figure out where the threshold is. It > erroneously reports that 41000 of the 64k were sent, but will say > the whole file was transferred up to about 64k. The connection > filedescriptor is blocking. > > Any ideas? sendfile() reports the bytes written into the send socket buffer. If there is a connection error it doesn't (and never did) look at how much data was still in the socket buffer. The sendfile(2) man page says: "[sbytes] If non-NULL, the system will write the total number of bytes sent on the socket to the variable pointed to by sbytes." This could be changed to subtract the remaining data in the socket buffer before reporting back. One has to be careful though about other writes so that the number never goes negative. There may be more data remaining in the socket buffer than from this write attempt alone. -- Andre From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 19:51:16 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E7AA16A46E for ; Fri, 2 Nov 2007 19:51:16 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 55E7213C48D for ; Fri, 2 Nov 2007 19:51:16 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Io2FS-00051c-P4 for freebsd-current@freebsd.org; Fri, 02 Nov 2007 12:32:06 -0700 Message-ID: <13554587.post@talk.nabble.com> Date: Fri, 2 Nov 2007 12:32:06 -0700 (PDT) From: oreverb To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: clxxiv@gmail.com X-Mailman-Approved-At: Fri, 02 Nov 2007 19:55:30 +0000 Subject: 7.0-CURRENT-200710-i386 not getting to sysinstall X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 19:51:16 -0000 Hi, newbie here, trying out the latest version on an AMD athlon 64 3200, NV nforce4 mobo, ATI graphics. Tried to boot with: - default or safe mode -> labels for acd0 and ad4 are found (GEOM_LABEL) - acpi off -> only label for acd0 if found (GEOM_LABEL) GEOM_LABELs are the last lines shown, then it stops. But it doesn't hang, scroll lock / pgup / pgdown work for browsing the Device Probe. Something to do with SATA (ad4 is SATA150/ata2, acd0 is PIO4/ata1)? -- View this message in context: http://www.nabble.com/7.0-CURRENT-200710-i386-not-getting-to-sysinstall-tf4739962.html#a13554587 Sent from the freebsd-current mailing list archive at Nabble.com. From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 20:14:45 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3682A16A418 for ; Fri, 2 Nov 2007 20:14:45 +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 099A313C4B2 for ; Fri, 2 Nov 2007 20:14:44 +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 DB11546CBE; Fri, 2 Nov 2007 10:26:45 -0500 (EST) Date: Fri, 2 Nov 2007 16:26:45 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Ian FREISLICH In-Reply-To: Message-ID: <20071102162523.A47979@fledge.watson.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@freebsd.org Subject: Re: sendfile() not detecting closed connections. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 20:14:45 -0000 On Fri, 2 Nov 2007, Ian FREISLICH wrote: > sendfile() reports success for files less than about 64k in size, but I > haven't been able to figure out where the threshold is. It erroneously > reports that 41000 of the 64k were sent, but will say the whole file was > transferred up to about 64k. The connection filedescriptor is blocking. Probably what is happening is that sendfile() is counting bytes successfully inserted into the send socket buffer, rather than bytes sent on the wire. This is consistent with what happens when you write a file to a TCP socket, though, as you only know the bytes made it into the buffer, not to the remote destination. I'd guess the threshold size you're seeing above is the size of the default send socket buffer. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 20:17:59 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FA0116A41A for ; Fri, 2 Nov 2007 20:17:59 +0000 (UTC) (envelope-from frankstaals@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id A4A1213C48A for ; Fri, 2 Nov 2007 20:17:58 +0000 (UTC) (envelope-from frankstaals@gmx.net) Received: (qmail invoked by alias); 02 Nov 2007 19:17:35 -0000 Received: from ip176-173-59-62.adsl.versatel.nl (EHLO Rena.FStaals.net) [62.59.173.176] by mail.gmx.net (mp047) with SMTP; 02 Nov 2007 20:17:35 +0100 X-Authenticated: #25365336 X-Provags-ID: V01U2FsdGVkX1/OANdROuHO5L5+r5K6W37T69ADNVUKVD0sWCnvvp ybCU5ctroAVtsS Message-ID: <472B779B.9060002@gmx.net> Date: Fri, 02 Nov 2007 20:16:43 +0100 From: Frank Staals User-Agent: Thunderbird 2.0.0.6 (X11/20070929) MIME-Version: 1.0 To: Benjamin Close References: <472A6708.9030109@clearchain.com> In-Reply-To: <472A6708.9030109@clearchain.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Mailman-Approved-At: Fri, 02 Nov 2007 20:20:13 +0000 Cc: freebsd-current , freebsd-drivers@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: [RFT] Intel 3945abg wireless driver (wpi) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 20:17:59 -0000 Benjamin Close wrote: > Howdy All, I'm pleased to announce the first 'official' > experimental version of the wpi wireless driver and hence require your > help in making it become stable. > Expect a few things not to work (ie bg scanning, setting txpower) but > in general the driver should be usable in station mode (hostap is not > yet supported). > > If you've got an Intel 3945abg wireless card, grab the tarball at: > > > http://people.freebsd.org/~benjsc/downloads/wpi/20071102-freebsd-wpi.tar.gz > > > Untar and follow the instructions in the README. > If you want more info about the driver, or to checkout the FAQ checkout: > > http://www.clearchain.com/wiki/Wpi > > I'm interested in all reports related to panics, things not working as > expected, etc. > The driver still has debug enabled so expect a few messages to be > dumped to the screen whilst in use. > > Finally, many thanks to all those that have been helping debug the > driver along the way. > > Cheers, > Benjamin > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" > Woei ! It's working for me so far :) Allthough I still have issues when switching from one tty to one other. Here the output of the script I am using to do the connecting : loaded the module at boot ran my script which does: ( output snipped ) wlannic=wpi0 # clear the selected gateway: route flush # Set the interface ifconfig ${wlannic} 192.168.5.5 ssid # Set a new gateway route add default 192.168.5.1 # make sure to give the LAN-NIC an other IP-address ifconfig ${lannic} 192.168.200.2 ifconfig ${wlannic} up # test connection ping -c 1 192.168.5.1 # start a screen session with ssh connection for authentication screen -d -m ssh -l wifi 192.168.5.1 # wait a while before testing the connection sleep 3 # test conn: ping -c 1 google.nl Everything works fine with the connection itself. Allthough sometimes when switching from tty9 to tty0 and back the system locks up. I've had it before when switching from tty1 to tty0. Anyone with the same problems ? Anyway; Great work on the driver so far :D -- -Frank Staals From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 20:29:13 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 52BD616A419 for ; Fri, 2 Nov 2007 20:29:13 +0000 (UTC) (envelope-from avleeuwen@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.224]) by mx1.freebsd.org (Postfix) with ESMTP id 1AB9D13C4B9 for ; Fri, 2 Nov 2007 20:29:11 +0000 (UTC) (envelope-from avleeuwen@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so687351nzf for ; Fri, 02 Nov 2007 13:28:50 -0700 (PDT) Received: by 10.115.106.7 with SMTP id i7mr1902466wam.1194011134767; Fri, 02 Nov 2007 06:45:34 -0700 (PDT) Received: by 10.114.131.10 with HTTP; Fri, 2 Nov 2007 06:45:34 -0700 (PDT) Message-ID: Date: Fri, 2 Nov 2007 14:45:34 +0100 From: "Arjan van Leeuwen" To: "current@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 Cc: Subject: Size of C++ debug binaries with gcc 4.2.1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: avleeuwen@piwebs.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 20:29:13 -0000 Hi, Since updating to FreeBSD 7.0, the size of my C++ binaries with debug symbols has quadrupled (on a specific binary I have to work with a lot, it increased from around 200MB to 860MB). If I use gcc 4.1 from ports, the debug size is only a bit bigger than what I used to have with gcc 3.4 on FreeBSD 6. The big size slows me down: linking is a lot slower, and loading the file into the debugger also takes a lot more time. - Why is there such a big difference in size between gcc 4.1 and gcc 4.2? What extra information is included? - How do I turn it off, so I can go back to fast linking and stop fiddling my thumbs a few minutes every time I want to start the debugger? Thanks, Arjan From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 20:52:15 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9A1E16A417 for ; Fri, 2 Nov 2007 20:52:15 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id BFF7B13C481 for ; Fri, 2 Nov 2007 20:52:15 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Io3UK-0007Oc-O4 for freebsd-current@freebsd.org; Fri, 02 Nov 2007 13:51:32 -0700 Message-ID: <13555729.post@talk.nabble.com> Date: Fri, 2 Nov 2007 13:51:32 -0700 (PDT) From: oreverb To: freebsd-current@freebsd.org In-Reply-To: <13554587.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: clxxiv@gmail.com References: <13554587.post@talk.nabble.com> X-Mailman-Approved-At: Fri, 02 Nov 2007 20:53:54 +0000 Subject: Re: 7.0-CURRENT-200710-i386 not getting to sysinstall X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 20:52:15 -0000 oreverb wrote: > > Tried to boot with: > > - default or safe mode -> labels for acd0 and ad4 are found (GEOM_LABEL) > - acpi off -> only label for acd0 if found (GEOM_LABEL) > > GEOM_LABELs are the last lines shown, then it stops. But it doesn't hang, > scroll lock / pgup / pgdown work for browsing the Device Probe. > Now tried with FreeBSD 7.0-BETA1.5 - result is the same. -- View this message in context: http://www.nabble.com/7.0-CURRENT-200710-i386-not-getting-to-sysinstall-tf4739962.html#a13555729 Sent from the freebsd-current mailing list archive at Nabble.com. From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 21:08:46 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 557F916A419 for ; Fri, 2 Nov 2007 21:08:46 +0000 (UTC) (envelope-from davids@webmaster.com) Received: from mail1.webmaster.com (mail1.webmaster.com [216.152.64.169]) by mx1.freebsd.org (Postfix) with ESMTP id 3F53813C481 for ; Fri, 2 Nov 2007 21:08:46 +0000 (UTC) (envelope-from davids@webmaster.com) Received: from however by webmaster.com (MDaemon.PRO.v8.1.3.R) with ESMTP id md50001756346.msg for ; Fri, 02 Nov 2007 13:58:14 -0700 From: "David Schwartz" To: "Ian FREISLICH" Date: Fri, 2 Nov 2007 13:57:18 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <20071102162523.A47979@fledge.watson.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Importance: Normal X-Authenticated-Sender: joelkatz@webmaster.com X-Spam-Processed: mail1.webmaster.com, Fri, 02 Nov 2007 13:58:14 -0700 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 206.171.168.138 X-Return-Path: davids@webmaster.com X-MDaemon-Deliver-To: current@freebsd.org X-MDAV-Processed: mail1.webmaster.com, Fri, 02 Nov 2007 13:58:17 -0700 Cc: current@freebsd.org Subject: RE: sendfile() not detecting closed connections. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: davids@webmaster.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 21:08:46 -0000 > Probably what is happening is that sendfile() is counting bytes > successfully > inserted into the send socket buffer, rather than bytes sent on the wire. > This is consistent with what happens when you write a file to a > TCP socket, > though, as you only know the bytes made it into the buffer, not > to the remote > destination. I'd guess the threshold size you're seeing above is > the size of > the default send socket buffer. Don't think so. After all, the connection was known to be closed (on both ends) before he called 'sendfile'. So how could any bytes have successfully been put into the send buffer? DS From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 21:20:08 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E869E16A510 for ; Fri, 2 Nov 2007 21:20:08 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from smtp800.mail.ukl.yahoo.com (smtp800.mail.ukl.yahoo.com [217.12.12.142]) by mx1.freebsd.org (Postfix) with SMTP id 6860913C481 for ; Fri, 2 Nov 2007 21:20:08 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: (qmail 14555 invoked from network); 2 Nov 2007 15:52:56 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btinternet.com; h=Received:X-YMail-OSG:From:To:Subject:Date:Message-ID:MIME-Version:Content-Type:X-Mailer:Content-language:Thread-index; b=wYPH1xlufFIlACMUWa7375hzDwvcUz1EC26H8kmMNWAQzYIKPW8aAhCmtsIc+rl+7sJ9L0Zfs/fnr3lKUxqiTOGMyM6/8ZG7Ew7NQpXBGJ72CJcjmJZQTpYtrtFk+MAkAgb9ZVMj14/ZAmR3aw4y+k6LAxm1OglmNVNrfFTO7Ms= ; Received: from unknown (HELO ThomasPC) (thomas.sparrevohn@btinternet.com@86.133.212.97 with login) by smtp800.mail.ukl.yahoo.com with SMTP; 2 Nov 2007 15:52:56 -0000 X-YMail-OSG: jCpM0TkVM1kaT9qzkETirvTHhbXN1pBU8mJp7Lc_AFKtFbFDPyXB1CosIOlGhGWGLzUpJ1vkWA-- From: "Thomas Sparrevohn" To: Date: Fri, 2 Nov 2007 15:52:55 -0000 Message-ID: <008001c81d68$6f69ad20$4e3d0760$@Sparrevohn@btinternet.com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Content-language: en-gb Thread-index: AcgdaG7kuc6Gv1ZnQYuX7xoGyvT5oQ== Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ZFS hangs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 21:20:09 -0000 Hi I having problems with ZFS - It randomly hangs in a wait state "zfs:(&zio->io_cv)" - The problem is recent e.g. it was not there before the 28/10 - I CVS'uped this morning - Has anybody else encountered this problem? From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 21:20:28 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8AB3916A418 for ; Fri, 2 Nov 2007 21:20:28 +0000 (UTC) (envelope-from ravna@nerdshack.com) Received: from karen.lavabit.com (karen.lavabit.com [72.249.41.33]) by mx1.freebsd.org (Postfix) with ESMTP id 7105313C4B9 for ; Fri, 2 Nov 2007 21:20:28 +0000 (UTC) (envelope-from ravna@nerdshack.com) Received: from dispatchd.nerdshack.com (julie.lavabit.com [72.249.41.31]) by karen.lavabit.com (Postfix) with SMTP id 77B5BC7B61 for ; Fri, 2 Nov 2007 05:54:58 -0500 (CDT) Received: from toy.firlefanz.org (p54ABDAAF.dip.t-dialin.net [84.171.218.175]) by mail.nerdshack.com with ESMTP Fri, 02 Nov 2007 05:54:58 -0500 Message-ID: <472B01FA.7030008@nerdshack.com> Date: Fri, 02 Nov 2007 11:54:50 +0100 From: Ravna User-Agent: Thunderbird 2.0.0.6 (X11/20071101) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: ZFS broken ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 21:20:28 -0000 I'm tying to build world for 7-Beta on a i386 for the last 4 days, always with fresh sources. The build fails at: /contrib/opensolaris/lib/libzfs/common/libzfs_dataset.c:64: error: 'TEXT_DOMAIN' undeclared Since I'm not using ZFS, I have a WITHOUT_MODULES= zfs in my make.conf, but what do I have to put in make.conf to not build ZFS at all ? From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 21:32:17 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1CDD16A46E; Fri, 2 Nov 2007 21:32:17 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from ipmail01.adl2.internode.on.net (ipmail01.adl2.internode.on.net [203.16.214.140]) by mx1.freebsd.org (Postfix) with ESMTP id 177EB13C4B2; Fri, 2 Nov 2007 21:32:14 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aq4HAOYwK0d5LYjs/2dsb2JhbACBW45c X-IronPort-AV: E=Sophos;i="4.21,364,1188743400"; d="scan'208";a="224636654" Received: from ppp121-45-136-236.lns11.adl6.internode.on.net (HELO mail.clearchain.com) ([121.45.136.236]) by ipmail01.adl2.internode.on.net with ESMTP; 03 Nov 2007 07:54:48 +1030 Received: from [192.168.155.249] (draco.internal.clearchain.com [192.168.155.249]) (authenticated bits=0) by mail.clearchain.com (8.13.8/8.13.8) with ESMTP id lA2LOjjb009753 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 3 Nov 2007 07:54:46 +1030 (CST) (envelope-from Benjamin.Close@clearchain.com) Message-ID: <472B9597.2050108@clearchain.com> Date: Sat, 03 Nov 2007 07:54:39 +1030 From: Benjamin Close User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Frank Staals References: <472A6708.9030109@clearchain.com> <472B779B.9060002@gmx.net> In-Reply-To: <472B779B.9060002@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on pegasus.clearchain.com X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (mail.clearchain.com [192.168.154.1]); Sat, 03 Nov 2007 07:54:46 +1030 (CST) Cc: freebsd-current , freebsd-drivers@freebsd.org, freebsd-mobile@freebsd.org Subject: Re: [RFT] Intel 3945abg wireless driver (wpi) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 21:32:18 -0000 Frank Staals wrote: > Benjamin Close wrote: >> Howdy All, I'm pleased to announce the first 'official' >> experimental version of the wpi wireless driver and hence require >> your help in making it become stable. >> Expect a few things not to work (ie bg scanning, setting txpower) but >> in general the driver should be usable in station mode (hostap is not >> yet supported). >> >> If you've got an Intel 3945abg wireless card, grab the tarball at: >> >> >> http://people.freebsd.org/~benjsc/downloads/wpi/20071102-freebsd-wpi.tar.gz >> >> >> Untar and follow the instructions in the README. >> If you want more info about the driver, or to checkout the FAQ checkout: >> >> http://www.clearchain.com/wiki/Wpi >> >> I'm interested in all reports related to panics, things not working >> as expected, etc. >> The driver still has debug enabled so expect a few messages to be >> dumped to the screen whilst in use. >> >> Finally, many thanks to all those that have been helping debug the >> driver along the way. >> >> Cheers, >> Benjamin >> _______________________________________________ >> freebsd-mobile@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-mobile >> To unsubscribe, send any mail to >> "freebsd-mobile-unsubscribe@freebsd.org" >> > Woei ! It's working for me so far :) Allthough I still have issues > when switching from one tty to one other. Here the output of the > script I am using to do the connecting : > > loaded the module at boot > > ran my script which does: ( output snipped ) > > wlannic=wpi0 > > # clear the selected gateway: > route flush > > # Set the interface ifconfig ${wlannic} 192.168.5.5 ssid > > > # Set a new gateway > route add default 192.168.5.1 > # make sure to give the LAN-NIC an other IP-address > ifconfig ${lannic} 192.168.200.2 > > ifconfig ${wlannic} up > > # test connection > ping -c 1 192.168.5.1 > # start a screen session with ssh connection for > authentication > screen -d -m ssh -l wifi 192.168.5.1 > # wait a while before testing the connection > sleep 3 > > # test conn: > ping -c 1 google.nl > > > > Everything works fine with the connection itself. Allthough sometimes > when switching from tty9 to tty0 and back the system locks up. I've > had it before when switching from tty1 to tty0. Anyone with the same > problems ? > > Anyway; Great work on the driver so far :D > I've similar issues and believe it might be due to the amount of kernel printfs that are happening. Can you sysctl debug.wpi=0 and see if the problem still exists? By chance are you using ZFS? I caught a memory modified after free panic in zfs the other day pid was from syslogd. I'm trying to work out if it's related. Cheers, Benjamin From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 21:39:57 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D580516A419 for ; Fri, 2 Nov 2007 21:39:57 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.freebsd.org (Postfix) with ESMTP id 16C4513C48D for ; Fri, 2 Nov 2007 21:39:56 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A736E.dip.t-dialin.net [84.154.115.110]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id lA2GDm9H083176; Fri, 2 Nov 2007 17:13:49 +0100 (CET) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by js.berklix.net (8.13.8/8.13.8) with ESMTP id lA2GFi5M089102; Fri, 2 Nov 2007 17:15:45 +0100 (CET) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (localhost.js.berklix.net [127.0.0.1]) by fire.js.berklix.net (8.13.8/8.13.8) with ESMTP id lA2GFibO026191; Fri, 2 Nov 2007 17:15:44 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200711021615.lA2GFibO026191@fire.js.berklix.net> To: Bachilo Dmitry In-reply-to: <200711021554.49567.root@solink.ru> References: <200711021554.49567.root@solink.ru> Comments: In-reply-to Bachilo Dmitry message dated "Fri, 02 Nov 2007 15:54:49 +0600." Date: Fri, 02 Nov 2007 17:15:44 +0100 From: "Julian H. Stacey" Cc: current@freebsd.org Subject: Re: PCMCIA RS232 card X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 21:39:57 -0000 Bachilo Dmitry wrote: > Good day, All. > I wonder if there can something be done to make the subject work. > When I plug it in it says: > cardbus0: at device 0.0 (no driver attached) > As far as I know, FreeBSD supports this type of cards (with puc driver?), but > I've tried hard and got nowhere. It is an "STlab RS232 Serial adapter". > What additional information from me is required? > Thanks in advance. > Best regards, Dmitry Bachilo Some PCMCIA support got abandoned between FreeBSD-4.* & -6.*, some developers have said they will try to fix pcmcia in -7.* (thus current), but if you don't want to wait, try your card on FreeBSD-4.11 (despite 4.11 is officially deprecated, still used on lots of machines, especially old laptops :-) Hopefully you can get a better answer from list mobile@freebsd.org > (I think my previous message was lost somehow, so i've repeated it, if it's > doubled, please excuse me) I got both Message-id: <200711021551.29545.root@solink.ru> Message-id: <200711021554.49567.root@solink.ru> -- Julian Stacey. Munich Computer Consultant, BSD Unix C Linux. http://berklix.com Ihr Rauch=mein allergischer Kopfschmerz. Dump cigs 4 snuff. Q: Global warming,pollution,water,fish,fuel shortages etc. A: Contraception. From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 21:40:18 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6C4616A469 for ; Fri, 2 Nov 2007 21:40:18 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: from smtp802.mail.ird.yahoo.com (smtp802.mail.ird.yahoo.com [217.146.188.62]) by mx1.freebsd.org (Postfix) with SMTP id 457AA13C48A for ; Fri, 2 Nov 2007 21:40:17 +0000 (UTC) (envelope-from Thomas.Sparrevohn@btinternet.com) Received: (qmail 7651 invoked from network); 2 Nov 2007 12:08:27 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=btinternet.com; h=Received:X-YMail-OSG:From:To:Subject:Date:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding:Content-Disposition:Message-Id; b=m9GLfpoHsMkJperzSx1AoXq/dgVQn5D5OlvMxV9OK7zQ+NksqFGdjV/hFsKoypzbUrSva9h6bLT1rnrtKY0FKQ8oQPp5ptWnVcf72YH+oP1BvonkG9VsGTA/eY02DTeJAfR/G8dmU8cHh5hkv73y24EOlmgOQ6s7u5+qXWl/VPk= ; Received: from unknown (HELO w2fzz0vc03.aah-go-on.com) (thomas.sparrevohn@btinternet.com@86.133.212.97 with login) by smtp802.mail.ird.yahoo.com with SMTP; 2 Nov 2007 12:08:27 -0000 X-YMail-OSG: qH7JEbcVM1nVnnNERWQPiY3Jn0SPfS7O16.Qztlc9nQrn3ptgXQSYH8_wH3Bz.vmD3pyYhFnPg-- From: Thomas Sparrevohn To: freebsd-current@freebsd.org Date: Fri, 2 Nov 2007 12:08:25 +0000 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711021208.25913.Thomas.Sparrevohn@btinternet.com> Subject: ZFS Hangs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 21:40:19 -0000 Hi One of the recent changes (after 28/10) has started making CURRENT hang in a wait state called zfs:(&zio->io_cv) - As the machine just has been rebuild I cannot narrow it down any more than that Does anybody else see that issue? From owner-freebsd-current@FreeBSD.ORG Fri Nov 2 23:42:27 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CA9816A41B for ; Fri, 2 Nov 2007 23:42:27 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.bluestop.org (muon.bluestop.org [IPv6:2001:41c8:1:548a::2]) by mx1.freebsd.org (Postfix) with ESMTP id B42EE13C4AA for ; Fri, 2 Nov 2007 23:42:26 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.draftnet (unknown [IPv6:2a01:348:10f:1::5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTP id 8E5D23017A; Fri, 2 Nov 2007 23:42:25 +0000 (GMT) Message-ID: <472BB5DB.5000701@cran.org.uk> Date: Fri, 02 Nov 2007 23:42:19 +0000 From: Bruce Cran User-Agent: Thunderbird 2.0.0.6 (X11/20070809) MIME-Version: 1.0 To: Stefan Lambrev References: <4956a5e50710301848i50fa9b19ube28113cf29c13d5@mail.gmail.com> <4728756B.4020609@moneybookers.com> <4956a5e50710310645v2ff11ftc51065fdf35d09a4@mail.gmail.com> <47288B67.8030600@moneybookers.com> In-Reply-To: <47288B67.8030600@moneybookers.com> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Nenhum_de_Nos Subject: Re: problems: nvidia latest driver and 7.0-BETA1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Nov 2007 23:42:27 -0000 Stefan Lambrev wrote: > Hi, > > Nenhum_de_Nos wrote: >> On 10/31/07, Stefan Lambrev wrote: >> >>> add to /boot/loader.conf >>> nvidia_load="YES" >>> and reboot. >>> May be you have device vga which blocks access to the card, so if you >>> load nvidia module before the kernel .. >>> >> >> i did it, and no good :( >> >> Michal Varga : >> >> this is a GeForce Go 7600 PCIe from an asus F3T notebook. when I >> installed the port, I didnt marl to use FreeBSD agp driver. so by this >> info I assume I'm using nvidia's. is that right ? >> >> it is really annoying using without the driver, I cant even watch a >> video. frame dropping and everything is slow :( >> >> I also tried the 97xx driver and no luck also :( >> >> matheus >> >> > Well I'm not sure what exactly is your problem, but this is how I get my > driver working: > /boot/loader.conf > nvidia_load="YES" > linux_load="YES" > > cd /usr/ports/x11/nvidia-driver && make config > everything except AGP is selected. > > I'm using and this sysctl - compat.linux.osrelease=2.6.16 > but nvidia driver should work without problems with default 2.4.2. > > And your card is too new to use legacy driver :) just go for the latest. > > Also if your card is detected you should have hw.nvidia.cards.0.XX too. > > can you provide dmesg and pciconf -vl ? > I was just about to post saying that I had the same problem, but before doing so I made sure I'd got a recent kernel+world and upgraded all the ports. As I was running the script session to capture all the data I realised it had worked this time. My card's now detected and Xorg seems to be running fine. Loading the driver once the system has booted doesn't seem to work (nothing gets shown in dmesg) but having the lines in /boot/loader.conf works for me. -- Bruce From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 00:04:56 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE7DD16A41A; Sat, 3 Nov 2007 00:04:56 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id C4A5713C4B0; Sat, 3 Nov 2007 00:04:56 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.14.1/8.13.8) with ESMTP id lA2MDVNg076998; Fri, 2 Nov 2007 18:13:31 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.14.1/8.14.1) with ESMTP id lA2MDVbr021816; Fri, 2 Nov 2007 18:13:31 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 2FE0D73068; Fri, 2 Nov 2007 17:13:31 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20071102221331.2FE0D73068@freebsd-current.sentex.ca> Date: Fri, 2 Nov 2007 17:13:31 -0500 (EST) X-Virus-Scanned: ClamAV 0.91.2/4641/Tue Oct 30 15:59:09 2007 clamav-milter version 0.91.2 on clamscanner5 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 00:04:57 -0000 TB --- 2007-11-02 19:50:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-11-02 19:50:00 - starting HEAD tinderbox run for i386/i386 TB --- 2007-11-02 19:50:00 - cleaning the object tree TB --- 2007-11-02 19:50:27 - checking out the source tree TB --- 2007-11-02 19:50:27 - cd /tinderbox/HEAD/i386/i386 TB --- 2007-11-02 19:50:27 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-11-02 19:58:57 - building world (CFLAGS=-O2 -pipe) TB --- 2007-11-02 19:58:57 - cd /src TB --- 2007-11-02 19:58:57 - /usr/bin/make -B buildworld >>> World build started on Fri Nov 2 19:58:58 UTC 2007 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Fri Nov 2 21:15:17 UTC 2007 TB --- 2007-11-02 21:15:17 - generating LINT kernel config TB --- 2007-11-02 21:15:17 - cd /src/sys/i386/conf TB --- 2007-11-02 21:15:17 - /usr/bin/make -B LINT TB --- 2007-11-02 21:15:17 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-02 21:15:17 - cd /src TB --- 2007-11-02 21:15:17 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Nov 2 21:15:17 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Fri Nov 2 21:44:02 UTC 2007 TB --- 2007-11-02 21:44:02 - building GENERIC kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-02 21:44:02 - cd /src TB --- 2007-11-02 21:44:02 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Nov 2 21:44:02 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Fri Nov 2 22:06:41 UTC 2007 TB --- 2007-11-02 22:06:41 - building PAE kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-02 22:06:41 - cd /src TB --- 2007-11-02 22:06:41 - /usr/bin/make -B buildkernel KERNCONF=PAE >>> Kernel build for PAE started on Fri Nov 2 22:06:41 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] if_zyd.o(.text+0x3a85): In function `zyd_ioctl': /src/sys/dev/usb/if_zyd.c:2390: undefined reference to `ieee80211_ioctl' if_zyd.o(.text+0x3b35): In function `zyd_media_change': /src/sys/dev/usb/if_zyd.c:673: undefined reference to `ieee80211_media_change' if_zyd.o(.text+0x3cc7): In function `zyd_rx_data': /src/sys/dev/usb/if_zyd.c:1942: undefined reference to `ieee80211_find_rxnode' if_zyd.o(.text+0x3d03):/src/sys/dev/usb/if_zyd.c:1943: undefined reference to `ieee80211_input' if_zyd.o(.text+0x3d0b):/src/sys/dev/usb/if_zyd.c:1947: undefined reference to `ieee80211_free_node' *** Error code 1 Stop in /obj/src/sys/PAE. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-11-02 22:13:30 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-11-02 22:13:30 - ERROR: failed to build PAE kernel TB --- 2007-11-02 22:13:30 - tinderbox aborted TB --- 0.66 user 3.23 system 8610.52 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 01:06:23 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C466016A418 for ; Sat, 3 Nov 2007 01:06:23 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: from corpmail.itlegion.ru (corpmail.itlegion.ru [84.21.226.211]) by mx1.freebsd.org (Postfix) with SMTP id EBA5A13C4A5 for ; Sat, 3 Nov 2007 01:06:22 +0000 (UTC) (envelope-from matrix@itlegion.ru) Received: (qmail 7072 invoked from network); 3 Nov 2007 00:01:27 +0300 Received: from unknown (HELO Artem) (192.168.0.12) by 84.21.226.211 with SMTP; 3 Nov 2007 00:01:27 +0300 X-AntiVirus: Checked by Dr.Web [version: 4.44, engine: 4.44.0.09170, virus records: 253682, updated: 2.11.2007] Message-ID: <01ac01c81d93$88e842e0$0c00a8c0@Artem> From: "Artem Kuchin" To: References: <033a01c81d31$bd180490$0c00a8c0@Artem> Date: Sat, 3 Nov 2007 00:01:16 +0300 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="koi8-r"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Subject: Re: Cannot buildworkd 7-beta (tcsh borken?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 01:06:23 -0000 Cvsed minutes ago and try builworld did cd /usr/src make clean rm -rf /usr/obj make buildworld got '"/bin/csh"' -DHAVE_ICONV -Wno-pointer-sign -c /usr/src/bin/csh/../../contrib/tcsh/sh.func.c /usr/src/bin/csh/../../contrib/tcsh/sh.func.c: In function 'iconv_catgets': /usr/src/bin/csh/../../contrib/tcsh/sh.func.c:2371: error: 'ICONV_CONST' undeclared (first use in this function) /usr/src/bin/csh/../../contrib/tcsh/sh.func.c:2371: error: (Each undeclared identifier is reported only once /usr/src/bin/csh/../../contrib/tcsh/sh.func.c:2371: error: for each function it appears in.) /usr/src/bin/csh/../../contrib/tcsh/sh.func.c:2371: error: expected ';' before 'char' /usr/src/bin/csh/../../contrib/tcsh/sh.func.c:2377: error: 'src' undeclared (first use in this function) so, tcsh is broken? For how long? -- Artem From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 02:56:51 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB76F16A41A for ; Sat, 3 Nov 2007 02:56:51 +0000 (UTC) (envelope-from thierry@herbelot.com) Received: from postfix2-g20.free.fr (postfix2-g20.free.fr [212.27.60.43]) by mx1.freebsd.org (Postfix) with ESMTP id 52A4813C494 for ; Sat, 3 Nov 2007 02:56:51 +0000 (UTC) (envelope-from thierry@herbelot.com) Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30]) by postfix2-g20.free.fr (Postfix) with ESMTP id B15761DB2F25; Fri, 2 Nov 2007 16:50:48 +0100 (CET) Received: from smtp4-g19.free.fr (localhost.localdomain [127.0.0.1]) by smtp4-g19.free.fr (Postfix) with ESMTP id A3A073EA0FB; Fri, 2 Nov 2007 18:51:15 +0100 (CET) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp4-g19.free.fr (Postfix) with ESMTP id 6EEFA3EA0BD; Fri, 2 Nov 2007 18:51:15 +0100 (CET) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.14.0/8.14.0) with ESMTP id lA2HpDgg011986; Fri, 2 Nov 2007 18:51:14 +0100 (CET) From: Thierry Herbelot To: Pawel Jakub Dawidek Date: Fri, 2 Nov 2007 18:51:05 +0100 User-Agent: KMail/1.9.7 References: <200711011509.46094.thierry@herbelot.com> <20071102095206.GB24455@garage.freebsd.pl> In-Reply-To: <20071102095206.GB24455@garage.freebsd.pl> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200711021851.07043.thierry@herbelot.com> Cc: freebsd-current@freebsd.org Subject: Re: regression with gmirror, Promise SATA and 7.0 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 02:56:51 -0000 Le Friday 02 November 2007, Pawel Jakub Dawidek a écrit : > > Thus, it seems that the combination of this Promise controller and the > > SATA disks has issues (there was a thread about Promise controllers and > > ZFS, but with no clear conclusion). > > Just to clarify. There is no regression in gmirror. This is ATA > problem/bug, which was reported so many times already. agreed (as I said initially : the Promise+SATA combination seems suspicious) > > > PS : I was also burnt by the forced conversion of gmirror metadata from > > v3 to v4, which makes it tricky to backtrack to 6.x, once a 7.x kernel + > > gmirror has been booted once. > > I'm not happy with with metadata auto-upgrade, but it just makes things > so much easier. You can always boot your 6.x to single-user mode using > disk directly (it should not change anything on disk) and just run > 'gmirror label' again. This is exactly what I did after remembering that initial "providers" are still bootable (I could also have prepared a non-gmirrored install for Releng_7, but this was not mentioned in UPDATING) Thanks for your good work TfH From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 06:27:27 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D7D6616A417; Sat, 3 Nov 2007 06:27:27 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id B04B513C48A; Sat, 3 Nov 2007 06:27:27 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.14.1/8.13.8) with ESMTP id lA35Y3W8099664; Sat, 3 Nov 2007 01:34:03 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.14.1/8.14.1) with ESMTP id lA35Y2pj061407; Sat, 3 Nov 2007 01:34:02 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 9F01D73068; Sat, 3 Nov 2007 00:34:02 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20071103053402.9F01D73068@freebsd-current.sentex.ca> Date: Sat, 3 Nov 2007 00:34:02 -0500 (EST) X-Virus-Scanned: ClamAV 0.90.2/3781/Fri Jul 27 07:24:10 2007 clamav-milter version 0.91.1 on clamscanner1 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 06:27:28 -0000 TB --- 2007-11-03 03:10:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-11-03 03:10:00 - starting HEAD tinderbox run for i386/i386 TB --- 2007-11-03 03:10:00 - cleaning the object tree TB --- 2007-11-03 03:10:30 - checking out the source tree TB --- 2007-11-03 03:10:30 - cd /tinderbox/HEAD/i386/i386 TB --- 2007-11-03 03:10:30 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-11-03 03:19:13 - building world (CFLAGS=-O2 -pipe) TB --- 2007-11-03 03:19:13 - cd /src TB --- 2007-11-03 03:19:13 - /usr/bin/make -B buildworld >>> World build started on Sat Nov 3 03:19:14 UTC 2007 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Sat Nov 3 04:35:41 UTC 2007 TB --- 2007-11-03 04:35:41 - generating LINT kernel config TB --- 2007-11-03 04:35:41 - cd /src/sys/i386/conf TB --- 2007-11-03 04:35:41 - /usr/bin/make -B LINT TB --- 2007-11-03 04:35:41 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-03 04:35:41 - cd /src TB --- 2007-11-03 04:35:41 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Nov 3 04:35:41 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Sat Nov 3 05:04:25 UTC 2007 TB --- 2007-11-03 05:04:25 - building GENERIC kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-03 05:04:25 - cd /src TB --- 2007-11-03 05:04:25 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sat Nov 3 05:04:25 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Sat Nov 3 05:27:10 UTC 2007 TB --- 2007-11-03 05:27:10 - building PAE kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-03 05:27:10 - cd /src TB --- 2007-11-03 05:27:10 - /usr/bin/make -B buildkernel KERNCONF=PAE >>> Kernel build for PAE started on Sat Nov 3 05:27:11 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] if_zyd.o(.text+0x3a85): In function `zyd_ioctl': /src/sys/dev/usb/if_zyd.c:2390: undefined reference to `ieee80211_ioctl' if_zyd.o(.text+0x3b35): In function `zyd_media_change': /src/sys/dev/usb/if_zyd.c:673: undefined reference to `ieee80211_media_change' if_zyd.o(.text+0x3cc7): In function `zyd_rx_data': /src/sys/dev/usb/if_zyd.c:1942: undefined reference to `ieee80211_find_rxnode' if_zyd.o(.text+0x3d03):/src/sys/dev/usb/if_zyd.c:1943: undefined reference to `ieee80211_input' if_zyd.o(.text+0x3d0b):/src/sys/dev/usb/if_zyd.c:1947: undefined reference to `ieee80211_free_node' *** Error code 1 Stop in /obj/src/sys/PAE. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-11-03 05:34:02 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-11-03 05:34:02 - ERROR: failed to build PAE kernel TB --- 2007-11-03 05:34:02 - tinderbox aborted TB --- 0.82 user 3.11 system 8642.12 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 06:27:30 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6A8C16A419 for ; Sat, 3 Nov 2007 06:27:30 +0000 (UTC) (envelope-from simias.n@gmail.com) Received: from simias.hd.free.fr (vit94-5-82-243-51-8.fbx.proxad.net [82.243.51.8]) by mx1.freebsd.org (Postfix) with ESMTP id 7698413C491 for ; Sat, 3 Nov 2007 06:27:29 +0000 (UTC) (envelope-from simias.n@gmail.com) Received: from simias.hd.free.fr (localhost [127.0.0.1]) by simias.hd.free.fr (8.14.1/8.14.1) with ESMTP id lA36Qdil017891 for ; Sat, 3 Nov 2007 07:26:39 +0100 (CET) (envelope-from simias.n@gmail.com) Received: (from simias@localhost) by simias.hd.free.fr (8.14.1/8.14.1/Submit) id lA36QSvW017890; Sat, 3 Nov 2007 07:26:28 +0100 (CET) (envelope-from simias.n@gmail.com) X-Authentication-Warning: simias.hd.free.fr: simias set sender to simias.n@gmail.com using -f From: Simias To: freebsd-current@freebsd.org Date: Sat, 03 Nov 2007 07:26:12 +0100 Message-ID: <86lk9fetff.fsf@simias.hd.free.fr> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/23.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: X crash with radeon driver - AGP broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 06:27:31 -0000 Hi Since I csup'd 7.0-BETA1, my computer reboots when I startx with the (open source) radeon driver -- I also tried with a fresh -CURRENT with the same result. It's probably not the place for asking X related questions, however it worked fine till then with a -CURRENT from mid-september (with the same Xorg 7.3), and here's the last output I get before it reboots: ,----[ startx -- -verbose 10 -config back/xorg.conf.radeon ] | [...] | (==) RADEON(0): Using 24 bit depth buffer | (II) RADEON(0): RADEONInitMemoryMap() : | (II) RADEON(0): mem_size : 0x10000000 | (II) RADEON(0): MC_FB_LOCATION : 0xcfffc000 | (II) RADEON(0): MC_AGP_LOCATION : 0xffffffc0 | (II) RADEON(0): Depth moves disabled by default | (II) RADEON(0): Setting up initial surfaces | (II) RADEON(0): Setting up accel memmap | (II) RADEON(0): CP in BM mode | (II) RADEON(0): Using 8 MB GART aperture | (II) RADEON(0): Using 1 MB for the ring buffer | (II) RADEON(0): Using 2 MB for vertex/indirect buffers | (II) RADEON(0): Using 5 MB for GART textures | (II) RADEON(0): Memory manager initialized to (0,0) (3072,8191) | (II) RADEON(0): Reserved area from (0,1440) to (3072,1442) | (II) RADEON(0): Largest offscreen area available: 3072 x 6749 | (II) RADEON(0): Will use front buffer at offset 0x0 | (II) RADEON(0): Will use back buffer at offset 0x4620000 | (II) RADEON(0): Will use depth buffer at offset 0x5700000 | (II) RADEON(0): Will use 155648 kb for textures at offset 0x67e0000 | drmOpenDevice: node name is /dev/dri/card0 | drmOpenDevice: open result is 8, (OK) | drmOpenDevice: node name is /dev/dri/card0 | drmOpenDevice: open result is 8, (OK) | drmOpenByBusid: Searching for BusID pci:0000:03:00.0 | drmOpenDevice: node name is /dev/dri/card0 | drmOpenDevice: open result is 8, (OK) | drmOpenByBusid: drmOpenMinor returns 8 | drmOpenByBusid: drmGetBusid reports pci:0000:03:00.0 | (II) [drm] DRM interface version 1.2 | (II) [drm] DRM open master succeeded. | (II) RADEON(0): [drm] Using the DRM lock SAREA also for drawables. | (II) RADEON(0): [drm] framebuffer handle = 0xc0000000 | (II) RADEON(0): [drm] added 1 reserved context for kernel | (II) RADEON(0): X context handle = 0x1 | (II) RADEON(0): [drm] installed DRM signal handler | (==) RADEON(0): Using AGP 8x | (II) RADEON(0): [agp] Mode 0x1f00420a [AGP 0x0000/0x0000; Card 0x1002/0x4150] | (II) RADEON(0): [agp] 8192 kB allocated with handle 0xc4128700 `---- It seems to break in AGP related init (or just after that, I don't know). It works fine with VESA, so I wonder if I'm the only one with this problem and if you have any idea about how to fix this or to investigate further the problem. (I tried to rebuild everything that could possibly be rebuilt). ,---- | $ uname -a FreeBSD simias.hd.free.fr 7.0-BETA1 FreeBSD 7.0-BETA1 #0: Mon | Oct 29 07:16:53 CET 2007 | root@simias.hd.free.fr:/usr/obj/usr/src/sys/HOMEBOX_ATHLON i386 | | $ X -version | X.Org X Server 1.4.0 | Release Date: 5 September 2007 | X Protocol Version 11, Revision 0 | Build Operating System: FreeBSD 7.0-BETA1 i386 | Current Operating System: FreeBSD simias.hd.free.fr 7.0-BETA1 FreeBSD | 7.0-BETA1 #0: Mon Oct 29 07:16:53 CET 2007 | root@simias.hd.free.fr:/usr/obj/usr/src/sys/HOMEBOX_ATHLON i386 | Build Date: 27 October 2007 10:45:02AM | | Before reporting problems, check http://wiki.x.org | to make sure that you have the latest version. | Module Loader present `---- My radeon is a 9600 Pro. Any clue ? -- Simias From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 12:18:51 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EFBEE16A421 for ; Sat, 3 Nov 2007 12:18:51 +0000 (UTC) (envelope-from samira.nox@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by mx1.freebsd.org (Postfix) with ESMTP id 342B713C4B3 for ; Sat, 3 Nov 2007 12:18:49 +0000 (UTC) (envelope-from samira.nox@gmail.com) Received: by ug-out-1314.google.com with SMTP id y2so846291uge for ; Sat, 03 Nov 2007 05:18:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:date:to:subject:from:content-type:mime-version:content-transfer-encoding:message-id:user-agent; bh=zC8J60WEX339DPDshE/94qvOYpjDuwU/iuPo4JV7Ps0=; b=YcfR7b9kRj7WlOSr+S9IV6cjy4TZNAmtKa9Sh3a8g+wpB2RDZqIc8aqJwaietSgg+t8FdXR4NplT1UnW+4TL6NI2m2reDsOc7toKVAvW+nMeeHxs+pRgTk2fhBGiHtULyIa9wY4NZbnQiWc9QlI5vTFvL9yvgKmPdO7NfHYLj1E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:to:subject:from:content-type:mime-version:content-transfer-encoding:message-id:user-agent; b=QEPfa93cf9NfKPgzzim+vd2I7CKh0AFf8nw5prUtZfWIOEHi2/ZY/9b6QzopCDzI3Saov35skN9QBwDboMXwBCvDqPQfJmwJUQ+e4jEARqHhrHwk8qL7KrLYFXFYy/WkZxysU/HpQTgcj16yIz9hlY4jz75OuEBoIo3AGc36vBA= Received: by 10.66.225.9 with SMTP id x9mr823968ugg.1194090728467; Sat, 03 Nov 2007 04:52:08 -0700 (PDT) Received: from localhost ( [85.3.101.178]) by mx.google.com with ESMTPS id e1sm10161753ugf.2007.11.03.04.52.06 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 03 Nov 2007 04:52:07 -0700 (PDT) Date: Sat, 03 Nov 2007 12:52:06 +0100 To: freebsd-current@freebsd.org From: samira Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Message-ID: User-Agent: Opera Mail/9.24 (Linux) Subject: sata atapi on ich9r X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 12:18:52 -0000 hi I have some problem using sata atapi devices on my gigabyte p35-ds4. The controller is in ahci mode. There are two kinds of dvd-devices 1). DVDROM 2). DVDR System is a 7.0-BETA2. If I have "atapicam" in the kernel, the system freezes at boot, well not exactly freezing, but giving acd0: FAILURE - INQURY timed out acd0: FAILURE - INQURY timed out over and over, where acd0 is one of the asus dvd drives. Removing atapicam from kernel does help. I can boot, provided there are no cds/dvds in the drives. But trying to play a dvd fails with acd0: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly acd0: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly acd0: FAILURE - SEND_KEY timed out acd0: FAILURE - MODE_SENSE_BIG timed out no matter, if I try on optiarc/asus. I can mount data cds. But the system freezes for about one minute when doing so. sam -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 12:48:06 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA1A516A419 for ; Sat, 3 Nov 2007 12:48:06 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.233]) by mx1.freebsd.org (Postfix) with ESMTP id 8501313C4B3 for ; Sat, 3 Nov 2007 12:48:05 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by wx-out-0506.google.com with SMTP id i29so933160wxd for ; Sat, 03 Nov 2007 05:47:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=DjWF12fGDWbS7M+mO/PCokRi8C2Zz0AjjH16VRhgEIw=; b=kWFd/C725z3yDho9R1AjabzAZ+isVuZkoPPXT28fr+oonxYmUecQSg/U7PJPEp3A4hfp4wM8vBJ4i3HXFeIu0VlfahOcNbsuYcj6DNRUd2yUrcMimskcVGJLSg62uvzi/7KaHdC/oasYC16kQyJ+Gzb/Ctn2LiD+eosVFabl6r8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=ofDmDUEHww2jnrxxIBAqA2FpXgaBKWenBcd8eSwXyFx1RtQ+Wb7pUvfnbPfYw45hBINcFLNxJHp1hsz5H3IdlLtcGpGMLzEcfscjvPAKHhCbNEkce0NZ6qhRAFI3ri2+Y7qT4X4WBhjpjw8XOiQ2wYYVRlqWciiZoc1u/TItVSk= Received: by 10.70.72.11 with SMTP id u11mr4428729wxa.1194094062210; Sat, 03 Nov 2007 05:47:42 -0700 (PDT) Received: from ?192.168.2.2? ( [67.85.89.184]) by mx.google.com with ESMTPS id u25sm6228556ele.2007.11.03.05.47.41 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 03 Nov 2007 05:47:41 -0700 (PDT) Message-ID: <472C3569.3050301@gmail.com> Date: Sat, 03 Nov 2007 04:46:33 -0400 From: "Aryeh M. Friedman" User-Agent: Thunderbird 2.0.0.6 (X11/20071101) MIME-Version: 1.0 To: samira References: In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: sata atapi on ich9r X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 12:48:06 -0000 samira wrote: > hi > > > I have some problem using sata atapi devices on my gigabyte p35-ds4. First of all p35 (ihc9r) have many known problems in this area (just for reference I have a msi neon-f p35 mobo w/ e6850, 4 gig and 2 sata + 1 pata device). When I first got the machine back in august it had all kinds of issues (do a search of -questions and -current to see them all). Most of the critical ones have been resolved post -current version fork. > > The controller is in ahci mode. There are two kinds of dvd-devices > 1). DVDROM > 2). DVDR > System is a 7.0-BETA2. What kind of processor and is the kernel/bases system i386 or amd64? Are you SATA/300 devices reported as SATA/150 and/or UDMA33? Does it reconize any PATA devices you may have? The only solution I was found was to use 8-current (i.e. from late sept on wards stuff worked fine [but only after the version fork]). BTW my SATA/300 devices are still reported as SATA/150 and the PATA device is not seen at all. > > If I have "atapicam" in the kernel, the system freezes at boot, well > not exactly freezing, but giving > acd0: FAILURE - INQURY timed out > acd0: FAILURE - INQURY timed out > over and over, where acd0 is one of the asus dvd drives. Same issue on amd64 beta 1.5 for me (but i386 worked fine [I had to do open heart surgery to switch it to amd64 [note 1]]) > > Removing atapicam from kernel does help. I can boot, provided there > are no cds/dvds in the drives. > > But trying to play a dvd fails with > acd0: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - > completing request directly > acd0: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - > completing request directly > acd0: FAILURE - SEND_KEY timed out > acd0: FAILURE - MODE_SENSE_BIG timed out > no matter, if I try on optiarc/asus. Is this true even if you have boot from cd in the cmos? > > I can mount data cds. But the system freezes for about one minute > when doing so. I have not experienced this but then again I never tried it ;-) Note to the development team: No I was not tripping when I reported these same issues just unable to provide proof Note to sam: Do you have any development experience if so I invite you to help me in my current project to patch the ata driver to fix all these issues (the ata developer told me since he doesn't have access to a ich9r/p35 system no patch and/or cvsup would be forth coming on these issues)... I am also a developer but at the moment am very tied up with making a living so I will give what help I can but can't do the whole project alone Notes: 1. Procedure: Downgrade to 6.2 amd64 FTP the distfiles for base and kernel (networking is completely broken so you have do some very creative tricks to get transfers to complete [note to the "no evidence" crowd on this list this is my ONLY machine and since it was so @#$@#$'ed up before the reupgrade to 8-current I was not able to record any proof of this]) overwrite the base and kernel with the distfiles reboot do the stay current procedure in the handbook From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 13:12:05 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2170316A419 for ; Sat, 3 Nov 2007 13:12:05 +0000 (UTC) (envelope-from samira.nox@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.freebsd.org (Postfix) with ESMTP id 98AC013C4B8 for ; Sat, 3 Nov 2007 13:12:04 +0000 (UTC) (envelope-from samira.nox@gmail.com) Received: by ug-out-1314.google.com with SMTP id y2so850250uge for ; Sat, 03 Nov 2007 06:11:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:date:to:subject:from:cc:content-type:mime-version:references:content-transfer-encoding:message-id:in-reply-to:user-agent; bh=kuskVaOo+mq2D8ey7wYDwOnwObCzK+l520007lg6yDQ=; b=Q5YY55+blYV0FMO+UpCS9uuwF5jQ4PUDqWBwF/9sBaQkGZr3w6LlRHUbdDLGtn6hZX2AvgUtTgra5za9q6DFLdRSgmJ9+jJgVjzeyYoKX8ZCetYk4Gi51JA85smPKjwNGGunsk1wjzMF3F3srOfsClM9f7oCsVHtGR9jtm4Jz/w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:to:subject:from:cc:content-type:mime-version:references:content-transfer-encoding:message-id:in-reply-to:user-agent; b=Zc6FdV1jAHlnPO/dEGKIdylIrqdZXecP1ABhZGLmUXDgVrpC38GPxXcBjnOpdoU6G5EHbzH6+aTjn8HpDi0ryHZVd/SHtsuQBMz2eJHTMMmVe/g9YBF/FYF27VBKNv/arUJdZ9ALyjKkTavrLU3PIa+70bMLTh64cnrmNFqMv/g= Received: by 10.66.218.15 with SMTP id q15mr1336164ugg.1194095083178; Sat, 03 Nov 2007 06:04:43 -0700 (PDT) Received: from localhost ( [85.3.101.178]) by mx.google.com with ESMTPS id y7sm10290170ugc.2007.11.03.06.04.41 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 03 Nov 2007 06:04:41 -0700 (PDT) Date: Sat, 03 Nov 2007 14:04:40 +0100 To: "Aryeh M. Friedman" From: sam Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 MIME-Version: 1.0 References: <472C3569.3050301@gmail.com> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <472C3569.3050301@gmail.com> User-Agent: Opera Mail/9.24 (Linux) Cc: freebsd-current@freebsd.org Subject: Re: sata atapi on ich9r X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 13:12:05 -0000 On Sat, 03 Nov 2007 09:46:33 +0100, Aryeh M. Friedman wrote: > samira wrote: >> hi >> >> >> I have some problem using sata atapi devices on my gigabyte p35-ds4. > > First of all p35 (ihc9r) have many known problems in this area (just for > reference I have a msi neon-f p35 mobo w/ e6850, 4 gig and 2 sata + 1 > pata device). > > When I first got the machine back in august it had all kinds of issues > (do a search of -questions and -current to see them all). Most of the > critical ones have been resolved post -current version fork. >> >> The controller is in ahci mode. There are two kinds of dvd-devices >> 1). DVDROM >> 2). DVDR >> System is a 7.0-BETA2. > > What kind of processor and is the kernel/bases system i386 or amd64? > The cpu is CPU: Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz (2666.68-MHz 686-class CPU) installed bsd is a i386. > Are you SATA/300 devices reported as SATA/150 and/or UDMA33? > ad4: 305244MB at ata2-master SATA300 ad6: 305244MB at ata3-master SATA300 ad8: 238475MB at ata4-master SATA300 acd0: DVDROM at ata5-master SATA150 acd1: DVDROM at ata6-master SATA150 acd2: DVDR at ata7-master SATA150 What I find kind of strange too, is that the first harddisk, which is plugged into sata0, is called ad4.. but never mind. If I enable the jmicron controller, which is also on the bord, the harddisk gets even ad10... > Does it reconize any PATA devices you may have? > Don't have any. > The only solution I was found was to use 8-current (i.e. from late sept > on wards stuff worked fine [but only after the version fork]). BTW my > SATA/300 devices are still reported as SATA/150 and the PATA device is > not seen at all. >> >> If I have "atapicam" in the kernel, the system freezes at boot, well >> not exactly freezing, but giving >> acd0: FAILURE - INQURY timed out >> acd0: FAILURE - INQURY timed out >> over and over, where acd0 is one of the asus dvd drives. > > Same issue on amd64 beta 1.5 for me (but i386 worked fine [I had to do > open heart surgery to switch it to amd64 [note 1]]) >> >> Removing atapicam from kernel does help. I can boot, provided there >> are no cds/dvds in the drives. >> >> But trying to play a dvd fails with >> acd0: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - >> completing request directly >> acd0: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - >> completing request directly >> acd0: FAILURE - SEND_KEY timed out >> acd0: FAILURE - MODE_SENSE_BIG timed out >> no matter, if I try on optiarc/asus. > > Is this true even if you have boot from cd in the cmos? Will try this. >> >> I can mount data cds. But the system freezes for about one minute >> when doing so. > > I have not experienced this but then again I never tried it ;-) > > Note to the development team: No I was not tripping when I reported > these same issues just unable to provide proof > > Note to sam: Do you have any development experience if so I invite you > to help me in my current project to patch the ata driver to fix all > these issues (the ata developer told me since he doesn't have access to > a ich9r/p35 system no patch and/or cvsup would be forth coming on these > issues)... I am also a developer but at the moment am very tied up with > making a living so I will give what help I can but can't do the whole > project alone > Unfortunately I haven't any experience in this kind of development. > Notes: > > 1. Procedure: > > Downgrade to 6.2 amd64 > FTP the distfiles for base and kernel (networking is completely broken > so you have do some very creative tricks to get transfers to complete > [note to the "no evidence" crowd on this list this is my ONLY machine > and since it was so @#$@#$'ed up before the reupgrade to 8-current I was > not able to record any proof of this]) > overwrite the base and kernel with the distfiles > reboot > do the stay current procedure in the handbook -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 14:40:41 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9D9D16A41A; Sat, 3 Nov 2007 14:40:41 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id 4495813C491; Sat, 3 Nov 2007 14:40:41 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.14.1/8.13.8) with ESMTP id lA3Cx3WV021271; Sat, 3 Nov 2007 08:59:03 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.14.1/8.14.1) with ESMTP id lA3Cx3a4053674; Sat, 3 Nov 2007 08:59:03 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 02EF373068; Sat, 3 Nov 2007 07:59:02 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20071103125903.02EF373068@freebsd-current.sentex.ca> Date: Sat, 3 Nov 2007 07:59:02 -0500 (EST) X-Virus-Scanned: ClamAV 0.90.2/3781/Fri Jul 27 07:24:10 2007 clamav-milter version 0.91.1 on news X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 14:40:41 -0000 TB --- 2007-11-03 10:35:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-11-03 10:35:00 - starting HEAD tinderbox run for i386/i386 TB --- 2007-11-03 10:35:00 - cleaning the object tree TB --- 2007-11-03 10:35:29 - checking out the source tree TB --- 2007-11-03 10:35:29 - cd /tinderbox/HEAD/i386/i386 TB --- 2007-11-03 10:35:29 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-11-03 10:44:15 - building world (CFLAGS=-O2 -pipe) TB --- 2007-11-03 10:44:15 - cd /src TB --- 2007-11-03 10:44:15 - /usr/bin/make -B buildworld >>> World build started on Sat Nov 3 10:44:16 UTC 2007 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Sat Nov 3 12:00:27 UTC 2007 TB --- 2007-11-03 12:00:27 - generating LINT kernel config TB --- 2007-11-03 12:00:27 - cd /src/sys/i386/conf TB --- 2007-11-03 12:00:27 - /usr/bin/make -B LINT TB --- 2007-11-03 12:00:27 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-03 12:00:27 - cd /src TB --- 2007-11-03 12:00:27 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Nov 3 12:00:27 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Sat Nov 3 12:29:11 UTC 2007 TB --- 2007-11-03 12:29:11 - building GENERIC kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-03 12:29:11 - cd /src TB --- 2007-11-03 12:29:11 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sat Nov 3 12:29:12 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Sat Nov 3 12:52:12 UTC 2007 TB --- 2007-11-03 12:52:12 - building PAE kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-03 12:52:12 - cd /src TB --- 2007-11-03 12:52:12 - /usr/bin/make -B buildkernel KERNCONF=PAE >>> Kernel build for PAE started on Sat Nov 3 12:52:12 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /src/sys/dev/usb/if_rum.c:2420: undefined reference to `ieee80211_amrr_choose' if_rum.o(.text+0x3692): In function `rum_rxeof': /src/sys/dev/usb/if_rum.c:936: undefined reference to `ieee80211_find_rxnode' if_rum.o(.text+0x377a):/src/sys/dev/usb/if_rum.c:956: undefined reference to `ieee80211_input' if_rum.o(.text+0x3785):/src/sys/dev/usb/if_rum.c:959: undefined reference to `ieee80211_free_node' if_rum.o(.text+0x37e4):/src/sys/dev/usb/if_rum.c:936: undefined reference to `ieee80211_find_rxnode' if_rum.o(.text+0x2240): In function `rum_start': /src/sys/dev/usb/if_rum.c:1395: undefined reference to `ieee80211_free_node' *** Error code 1 Stop in /obj/src/sys/PAE. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-11-03 12:59:02 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-11-03 12:59:02 - ERROR: failed to build PAE kernel TB --- 2007-11-03 12:59:02 - tinderbox aborted TB --- 0.61 user 3.33 system 8642.03 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 15:00:24 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3298B16A418 for ; Sat, 3 Nov 2007 15:00:24 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.freebsd.org (Postfix) with ESMTP id E8E7C13C4B0 for ; Sat, 3 Nov 2007 15:00:23 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from thor.farley.org (thor.farley.org [192.168.1.5]) by mail.farley.org (8.14.1/8.14.1) with ESMTP id lA3ExeiJ062030; Sat, 3 Nov 2007 09:59:40 -0500 (CDT) (envelope-from scf@FreeBSD.org) Date: Sat, 3 Nov 2007 09:59:40 -0500 (CDT) From: "Sean C. Farley" To: "Aryeh M. Friedman" In-Reply-To: <472C3569.3050301@gmail.com> Message-ID: References: <472C3569.3050301@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on mail.farley.org Cc: freebsd-current@FreeBSD.org, samira Subject: Re: sata atapi on ich9r X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 15:00:24 -0000 On Sat, 3 Nov 2007, Aryeh M. Friedman wrote: *snip* > Note to the development team: No I was not tripping when I reported > these same issues just unable to provide proof I guarantee you are not tripping. :( > Note to sam: Do you have any development experience if so I invite you > to help me in my current project to patch the ata driver to fix all > these issues (the ata developer told me since he doesn't have access to > a ich9r/p35 system no patch and/or cvsup would be forth coming on these > issues)... I am also a developer but at the moment am very tied up with > making a living so I will give what help I can but can't do the whole > project alone I can try to help, but I am also busy (crunch-time at work). My system is an Asus P5K-E/WiFi with a DVDR . It has 4GB RAM and two SATA hard drives. I have no PATA drives in it. It is running in RAID mode. Unfortunately, this is my only workstation at home, so I will not be changing versions. I am willing to make changes to the driver. Here is a patch[1] to recognize and print the ICH9R during boot. It does not change anything functionally. My current notes: 1. burncd (without atapicam loaded), cdrecord and dd can all produce warnings. dd if=/dev/acd0 of=/dev/null bs=10M count=1 2. sysinstall will fail during install when copying GENERIC kernel. This was on my work computer in a Dell Optiplex 745 with 1GB RAM. atapci0: acd0: CDRW at ata3-master SATA150 3. Do not detach a channel with atacontrol. I tried that on the channel with the DVD drive. Panic. 4. I am thinking about writing a program to perform simple tests on the ATAPI ioctl's. Maybe one exists? 5. PATA is not related since I have no PATA drives in my computer. *downgrade to 6.2 AMD64 snipped* Sean 1. http://www.farley.org/freebsd/tmp/ata-chipset.c.diff -- scf@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 16:07:25 2007 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36D1E16A418 for ; Sat, 3 Nov 2007 16:07:25 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.freebsd.org (Postfix) with ESMTP id C6A2013C4B6 for ; Sat, 3 Nov 2007 16:07:24 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from thor.farley.org (thor.farley.org [192.168.1.5]) by mail.farley.org (8.14.1/8.14.1) with ESMTP id lA3EdxlG061760; Sat, 3 Nov 2007 09:39:59 -0500 (CDT) (envelope-from scf@FreeBSD.org) Date: Sat, 3 Nov 2007 09:39:59 -0500 (CDT) From: "Sean C. Farley" To: samira In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on mail.farley.org Cc: freebsd-current@FreeBSD.org Subject: Re: sata atapi on ich9r X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 16:07:25 -0000 On Sat, 3 Nov 2007, samira wrote: > hi > > I have some problem using sata atapi devices on my gigabyte p35-ds4. > The controller is in ahci mode. There are two kinds of dvd-devices > 1). DVDROM > 2). DVDR > System is a 7.0-BETA2. I have a Asus P5K-E/WiFi with a DVDR . > If I have "atapicam" in the kernel, the system freezes at boot, well > not exactly freezing, but giving > acd0: FAILURE - INQURY timed out > acd0: FAILURE - INQURY timed out > over and over, where acd0 is one of the asus dvd drives. > > Removing atapicam from kernel does help. I can boot, provided there > are no cds/dvds in the drives. I have heard that blank CD's during boot will prevent booting. > But trying to play a dvd fails with > acd0: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing > request directly > acd0: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing > request directly > acd0: FAILURE - SEND_KEY timed out > acd0: FAILURE - MODE_SENSE_BIG timed out > no matter, if I try on optiarc/asus. I have seen similar messages on my work computer with a different SATA DVD drive. I can get other warnings with: dd if=/dev/acd0 of=/dev/null bs=10M count=1 With verbose boot: Nov 2 23:09:31 thor kernel: ata7: reiniting channel .. Nov 2 23:09:31 thor kernel: ata7: SATA connect time=0ms Nov 2 23:09:31 thor kernel: ata7: SIGNATURE: eb140101 Nov 2 23:09:31 thor kernel: ata7: ahci_reset devices=0x4 Nov 2 23:09:31 thor kernel: ata7: reinit done .. Nov 2 23:09:31 thor kernel: acd0: TIMEOUT - READ_BIG retrying (1 retry left) Nov 2 23:10:03 thor kernel: ata7: reiniting channel .. Nov 2 23:10:03 thor kernel: ata7: SATA connect time=0ms Nov 2 23:10:03 thor kernel: ata7: SIGNATURE: eb140101 Nov 2 23:10:03 thor kernel: ata7: ahci_reset devices=0x4 Nov 2 23:10:03 thor kernel: ata7: reinit done .. Nov 2 23:10:03 thor kernel: acd0: TIMEOUT - READ_BIG retrying (0 retries left) Nov 2 23:10:34 thor kernel: ata7: reiniting channel .. Nov 2 23:10:34 thor kernel: ata7: SATA connect time=0ms Nov 2 23:10:34 thor kernel: ata7: SIGNATURE: eb140101 Nov 2 23:10:34 thor kernel: ata7: ahci_reset devices=0x4 Nov 2 23:10:34 thor kernel: ata7: reinit done .. Nov 2 23:10:34 thor kernel: acd0: FAILURE - READ_BIG timed out > I can mount data cds. But the system freezes for about one minute > when doing so. Unfortunately, I can only confirm your problems. Sean -- scf@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 16:29:00 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82AF716A417 for ; Sat, 3 Nov 2007 16:29:00 +0000 (UTC) (envelope-from jachmann@unitix.org) Received: from wm2.todt.org (wm2.todt.org [82.149.245.21]) by mx1.freebsd.org (Postfix) with SMTP id C5AA413C4BB for ; Sat, 3 Nov 2007 16:28:59 +0000 (UTC) (envelope-from jachmann@unitix.org) Received: (qmail 73408 invoked from network); 3 Nov 2007 17:01:38 +0100 Received: from unknown (HELO hurx.thc) (84.59.105.204) by 0 with SMTP; 3 Nov 2007 17:01:38 +0100 Received: (qmail 1260 invoked by uid 1001); 3 Nov 2007 16:01:37 -0000 Date: Sat, 3 Nov 2007 17:01:37 +0100 From: Christian Jachmann To: Simias Message-ID: <20071103160137.GA1182@hurx.thc> References: <86lk9fetff.fsf@simias.hd.free.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86lk9fetff.fsf@simias.hd.free.fr> User-Agent: Mutt/1.4.2.3i X-Mailman-Approved-At: Sat, 03 Nov 2007 16:35:01 +0000 Cc: freebsd-current@freebsd.org Subject: Re: X crash with radeon driver - AGP broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 16:29:00 -0000 Sat, Nov 03, 2007 at 07:26:12AM +0100, Simias : > > Hi > > Since I csup'd 7.0-BETA1, my computer reboots when I startx with the > (open source) radeon driver -- I also tried with a fresh -CURRENT with the > same result. > > My radeon is a 9600 Pro. > > Any clue ? Same here: jachmann@hurx:~>Xorg -version X.Org X Server 1.4.0 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: FreeBSD 7.0-BETA2 i386 Current Operating System: FreeBSD hurx.thc 7.0-BETA2 FreeBSD 7.0-BETA2 #0: Fri N ov 2 21:15:25 CET 2007 root@hurx.thc:/usr/obj/usr/src/sys/GENERIC i386 Build Date: 02 November 2007 10:02:24PM crashes. From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 17:13:51 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03C4516A468 for ; Sat, 3 Nov 2007 17:13:51 +0000 (UTC) (envelope-from aturetta@commit.it) Received: from aa002msb.fastweb.it (aa002msb.fastweb.it [85.18.95.81]) by mx1.freebsd.org (Postfix) with ESMTP id 737A413C4B2 for ; Sat, 3 Nov 2007 17:13:50 +0000 (UTC) (envelope-from aturetta@commit.it) Received: from mail.logital.it (85.18.201.99) by aa002msb.fastweb.it (7.3.118.6) id 46657813084F08CF for freebsd-current@freebsd.org; Sat, 3 Nov 2007 17:21:37 +0100 Received: from [192.168.44.145] (adsl-ull-241-22.51-151.net24.it [151.51.22.241]) (authenticated bits=0) by mail.logital.it (8.14.1/8.14.1) with ESMTP id lA3GLSam073159 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 3 Nov 2007 17:21:32 +0100 (CET) (envelope-from aturetta@commit.it) Message-ID: <472C9FFE.8090201@commit.it> Date: Sat, 03 Nov 2007 17:21:18 +0100 From: Angelo Turetta User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Ed Maste References: <469881E4.3000808@commit.it> <20071031215739.GA20915@sandvine.com> In-Reply-To: <20071031215739.GA20915@sandvine.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on mail.logital.it X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Compiling multiple kernels broken (was: Build error (make related?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 17:13:51 -0000 Ed Maste wrote: > On Sat, Jul 14, 2007 at 09:57:24AM +0200, Angelo Turetta wrote: >> This morning I'm trying to update my current system >> (7.0-CURRENT #14: Mon Jul 9 21:55:06 CEST 2007) >> >> and when I issue the usual >> >> #make buildworld KERNCONF="GENERIC VIDEO VIDEODBG" buildkernel > > I just ran into the same failure. It seems that somehow specifying > multiple entries in KERNCONF= has been broken; try building just one > at a time. Thanks, Ed !!! I think it's something that should be fixed before 7.0-RELEASE. Angelo. From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 17:23:25 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0B8A16A418 for ; Sat, 3 Nov 2007 17:23:25 +0000 (UTC) (envelope-from davidt@yadt.co.uk) Received: from outcold.yadt.co.uk (outcold.yadt.co.uk [81.187.204.178]) by mx1.freebsd.org (Postfix) with ESMTP id 6D51513C48D for ; Sat, 3 Nov 2007 17:23:25 +0000 (UTC) (envelope-from davidt@yadt.co.uk) Received: from localhost (localhost [127.0.0.1]) by outcold.yadt.co.uk (Postfix) with ESMTP id E0BC4668A for ; Sat, 3 Nov 2007 16:39:34 +0000 (GMT) X-Virus-Scanned: amavisd-new at yadt.co.uk Received: from outcold.yadt.co.uk ([127.0.0.1]) by localhost (outcold.yadt.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sNDHRD+bVtBm for ; Sat, 3 Nov 2007 16:39:31 +0000 (GMT) Received: by outcold.yadt.co.uk (Postfix, from userid 1001) id 2646C667C; Sat, 3 Nov 2007 16:39:31 +0000 (GMT) Date: Sat, 3 Nov 2007 16:39:31 +0000 From: David Taylor To: freebsd-current@freebsd.org Message-ID: <20071103163931.GA23714@outcold.yadt.co.uk> Mail-Followup-To: freebsd-current@freebsd.org References: <472A66EE.6060407@gmail.com> <20071102043043.GI3109@dan.emsphone.com> <472A725F.6000201@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <472A725F.6000201@gmail.com> User-Agent: Mutt/1.4.2.3i Subject: Re: [PATCH] prevent install(1) from overwritting symlinks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 17:23:25 -0000 On Thu, 01 Nov 2007, Aryeh M. Friedman wrote: > Dan Nelson wrote: > > In the last episode (Nov 01), Aryeh M. Friedman said: > > > >> The below patch is designed to keep install(1) from overwriting symbolic > >> links. The motivation is if cups is installed some programs still > >> expect lpr to be in /usr/bin thus when I install cups I backlink the > >> /usr/local/bin versions of lp* to /usr/bin. When a build/installworld > >> is done these links are overwritten and the sym links have to be > >> performed again. This patch prevents the overwrite. > >> > > > > Why not just set WITHOUT_LPR to skip building the base versions > > entirely? > > > > > Because this happens in other cases not covered by WITHOUT_XXX also it > does not solve the problem of ports and/or third party install from > overwritting.... If a port overwrites anything under /usr/bin then that is generally a bug. > i.e. this is a general solution to a specific problem > (which I think is preferable to a one off solution for each instance of > a problem) The WITHOUT_ knobs are a reasonably general solution -- if you wish to replace part of the base system, set WITHOUT_xxx and the base system will stop overwriting your replacement. Whether it is in the form of a symlink or a regular file. -- David Taylor From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 18:38:33 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ABBF416A469 for ; Sat, 3 Nov 2007 18:38:33 +0000 (UTC) (envelope-from davidt@yadt.co.uk) Received: from outcold.yadt.co.uk (outcold.yadt.co.uk [81.187.204.178]) by mx1.freebsd.org (Postfix) with ESMTP id 5B32913C4B5 for ; Sat, 3 Nov 2007 18:38:33 +0000 (UTC) (envelope-from davidt@yadt.co.uk) Received: from localhost (localhost [127.0.0.1]) by outcold.yadt.co.uk (Postfix) with ESMTP id E50FF6708 for ; Sat, 3 Nov 2007 16:42:34 +0000 (GMT) X-Virus-Scanned: amavisd-new at yadt.co.uk Received: from outcold.yadt.co.uk ([127.0.0.1]) by localhost (outcold.yadt.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Q9x1cticLyE for ; Sat, 3 Nov 2007 16:42:31 +0000 (GMT) Received: by outcold.yadt.co.uk (Postfix, from userid 1001) id 8DC286700; Sat, 3 Nov 2007 16:42:31 +0000 (GMT) Date: Sat, 3 Nov 2007 16:42:31 +0000 From: David Taylor To: freebsd-current@freebsd.org Message-ID: <20071103164231.GB23714@outcold.yadt.co.uk> Mail-Followup-To: freebsd-current@freebsd.org References: <200711021208.25913.Thomas.Sparrevohn@btinternet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <200711021208.25913.Thomas.Sparrevohn@btinternet.com> User-Agent: Mutt/1.4.2.3i Subject: Re: ZFS Hangs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 18:38:33 -0000 On Fri, 02 Nov 2007, Thomas Sparrevohn wrote: > > Hi > > One of the recent changes (after 28/10) has started making CURRENT hang in a wait state called zfs:(&zio->io_cv) - As the machine just has been rebuild > I cannot narrow it down any more than that I have seen a number of processes appear to hang in that state. For example, pkg_delete seems to be _extremely_ slow and ^T reports that it is stuck waiting on zfs:(&zio->io_cv) for an unreasonable (IMO) amount of time. I may once have been forced to reboot the system due to this problem "spreading" to other processes, but I had no time nor ability to investigate it further, so I'm not even sure it was the same problem. -- David Taylor From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 18:51:38 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B72816A475 for ; Sat, 3 Nov 2007 18:51:38 +0000 (UTC) (envelope-from h.skuhra@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.190]) by mx1.freebsd.org (Postfix) with ESMTP id 2AB2513C4BD for ; Sat, 3 Nov 2007 18:51:37 +0000 (UTC) (envelope-from h.skuhra@gmail.com) Received: by mu-out-0910.google.com with SMTP id i10so1224046mue for ; Sat, 03 Nov 2007 11:51:11 -0700 (PDT) Received: by 10.86.50.8 with SMTP id x8mr1643280fgx.1194090322214; Sat, 03 Nov 2007 04:45:22 -0700 (PDT) Received: from oslo.ath.cx ( [213.47.80.26]) by mx.google.com with ESMTPS id 13sm7472798fks.2007.11.03.04.45.19 (version=SSLv3 cipher=OTHER); Sat, 03 Nov 2007 04:45:20 -0700 (PDT) Date: Sat, 3 Nov 2007 12:45:19 +0100 From: "Herbert J. Skuhra" To: freebsd-current@freebsd.org Message-ID: <20071103114519.GA801@oslo.ath.cx> References: <472B01FA.7030008@nerdshack.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <472B01FA.7030008@nerdshack.com> User-Agent: Mutt/1.5.16 (2007-06-09) Subject: Re: ZFS broken ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 18:51:38 -0000 On Fri, Nov 02, 2007 at 11:54:50AM +0100, Ravna wrote: > I'm tying to build world for 7-Beta on a i386 for the last 4 days, always > with fresh sources. > The build fails at: > /contrib/opensolaris/lib/libzfs/common/libzfs_dataset.c:64: error: > 'TEXT_DOMAIN' undeclared > > Since I'm not using ZFS, I have a WITHOUT_MODULES= zfs in my make.conf, > but what do I have to put in make.conf to not build ZFS at all ? man 5 src.conf - Herbert From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 19:51:04 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9DE6716A417; Sat, 3 Nov 2007 19:51:04 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id 49EE713C4A5; Sat, 3 Nov 2007 19:51:04 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.14.1/8.13.8) with ESMTP id lA3JGUGA042911; Sat, 3 Nov 2007 15:16:30 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.14.1/8.14.1) with ESMTP id lA3JGU9S082404; Sat, 3 Nov 2007 15:16:30 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id B75F07302F; Sat, 3 Nov 2007 14:16:29 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20071103191629.B75F07302F@freebsd-current.sentex.ca> Date: Sat, 3 Nov 2007 14:16:29 -0500 (EST) X-Virus-Scanned: ClamAV 0.90.2/3781/Fri Jul 27 07:24:10 2007 clamav-milter version 0.91.1 on clamscanner2 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on arm/arm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 19:51:04 -0000 TB --- 2007-11-03 18:00:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-11-03 18:00:00 - starting HEAD tinderbox run for arm/arm TB --- 2007-11-03 18:00:00 - mkdir /tinderbox/HEAD/arm TB --- 2007-11-03 18:00:00 - mkdir /tinderbox/HEAD/arm/arm TB --- 2007-11-03 18:00:00 - cleaning the object tree TB --- 2007-11-03 18:00:00 - checking out the source tree TB --- 2007-11-03 18:00:00 - cd /tinderbox/HEAD/arm/arm TB --- 2007-11-03 18:00:00 - /usr/bin/cvs -f -R -q -d/home/ncvs checkout -P -A src TB --- 2007-11-03 18:08:59 - building world (CFLAGS=-O2 -pipe) TB --- 2007-11-03 18:08:59 - cd /src TB --- 2007-11-03 18:08:59 - /usr/bin/make -B buildworld >>> World build started on Sat Nov 3 18:08:59 UTC 2007 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -DINET6 -c /src/usr.bin/systat/main.c cc -O2 -pipe -DINET6 -c /src/usr.bin/systat/mbufs.c cc -O2 -pipe -DINET6 -c /src/usr.bin/systat/netcmds.c /src/usr.bin/systat/netcmds.c: In function 'netcmd': /src/usr.bin/systat/netcmds.c:127: internal compiler error: internal consistency failure Please submit a full bug report, with preprocessed source if appropriate. See for instructions. *** Error code 1 Stop in /src/usr.bin/systat. *** Error code 1 Stop in /src/usr.bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-11-03 19:16:29 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-11-03 19:16:29 - ERROR: failed to build world TB --- 2007-11-03 19:16:29 - tinderbox aborted TB --- 0.04 user 0.00 system 4589.20 real http://tinderbox.des.no/tinderbox-head-HEAD-arm-arm.full From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 20:34:17 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8BD916A420 for ; Sat, 3 Nov 2007 20:34:17 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.freebsd.org (Postfix) with ESMTP id 6089813C481 for ; Sat, 3 Nov 2007 20:34:17 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so880234nfb for ; Sat, 03 Nov 2007 13:33:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; bh=OdjlHV92eN5f3a0WuBph8ZVPEazYLw0a/bndkbPNbIo=; b=P+kRgLe3XMb48Gb9oKRwgH3v+gkkIKBhuDmec4BdNSBIWKzwLwjIydf0nmGu8fn+0DKlVFgri6KNxhJuBMMBftlGGkdFEGh8JiCZSjCMspLl5SJSOgUNlBJDTMfdMxS25ftjWtrwrJQV34K4vmlBnOaxNz6gafpmfYSYGicA7UY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=f1zbZqJl1h0RFrJ9rRugmXgYuQmJr0EBvBKzMPomfOMketspDO3kYQfML/nsOCGOGTeL2emylFc413jtPk0OYA7w/24w2h+ApG/KT+Av6HpoTC1Mx5Ft7lWfFe8XvstCYa/DM2fULj6QiR+6AahX8G6lITxie0+w1zH6P9/g3f8= Received: by 10.78.130.6 with SMTP id c6mr2470869hud.1194122037619; Sat, 03 Nov 2007 13:33:57 -0700 (PDT) Received: from 195-241-214-37.dsl.ip.tiscali.nl ( [195.241.214.37]) by mx.google.com with ESMTPS id f8sm4584692nfh.2007.11.03.13.33.54 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 03 Nov 2007 13:33:55 -0700 (PDT) Message-ID: <472CDB31.9060306@gmail.com> Date: Sat, 03 Nov 2007 21:33:53 +0100 From: Rene Ladan User-Agent: Thunderbird 2.0.0.6 (X11/20071031) MIME-Version: 1.0 To: Benjamin Close , current@freebsd.org References: <469536D5.3010701@gmail.com> <4699DEEC.3080806@clearchain.com> <4699FC0A.40207@gmail.com> <469A09D4.4050005@clearchain.com> <46BA2509.8090002@gmail.com> <46BADF8A.7020504@clearchain.com> <46BB732F.2030300@gmail.com> <46C35674.3030506@gmail.com> <46D6A203.7080002@clearchain.com> <46D883E6.5070607@gmail.com> <46DEA569.8050101@clearchain.com> <46DF1510.80602@gmail.com> <46DF15A4.9010508@gmail.com> <46F67C39.4050109@clearchain.com> <46F6AD16.80503@gmail.com> <472A7CE9.6060900@clearchain.com> In-Reply-To: <472A7CE9.6060900@clearchain.com> X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: wpi doesn't associate :( X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 20:34:18 -0000 Benjamin Close schreef: > Hi Rene, > There's a new version up if you want to give it a go. > > http://people.freebsd.org/~benjsc/downloads/ > I tested the new tarball on my laptop but dhclient still refuses to associate (it keeps stuck in the DHCPDISCOVER state). I temporarily switched of the MAC address check of the router so that any client which knows the WEP password can connect, but that didn't help either. I also got some messages about memory not being properly aligned when loading if_wpi. Laptop : Asus A6JE. lspci -vv gives: 03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) Subsystem: Intel Corporation Unknown device 1001 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F133116A468; Sat, 3 Nov 2007 22:21:51 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id C408C13C4B3; Sat, 3 Nov 2007 22:21:51 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.14.1/8.13.8) with ESMTP id lA3LnATp050789; Sat, 3 Nov 2007 17:49:10 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.14.1/8.14.1) with ESMTP id lA3LnA9a060747; Sat, 3 Nov 2007 17:49:10 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 4FB397302F; Sat, 3 Nov 2007 16:49:10 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20071103214910.4FB397302F@freebsd-current.sentex.ca> Date: Sat, 3 Nov 2007 16:49:10 -0500 (EST) X-Virus-Scanned: ClamAV 0.91.2/4641/Tue Oct 30 15:59:09 2007 clamav-milter version 0.91.2 on clamscanner5 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 22:21:52 -0000 TB --- 2007-11-03 19:16:29 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2007-11-03 19:16:29 - starting HEAD tinderbox run for i386/i386 TB --- 2007-11-03 19:16:29 - cleaning the object tree TB --- 2007-11-03 19:16:54 - checking out the source tree TB --- 2007-11-03 19:16:54 - cd /tinderbox/HEAD/i386/i386 TB --- 2007-11-03 19:16:54 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2007-11-03 19:24:18 - building world (CFLAGS=-O2 -pipe) TB --- 2007-11-03 19:24:18 - cd /src TB --- 2007-11-03 19:24:18 - /usr/bin/make -B buildworld >>> World build started on Sat Nov 3 19:24:20 UTC 2007 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Sat Nov 3 20:49:05 UTC 2007 TB --- 2007-11-03 20:49:05 - generating LINT kernel config TB --- 2007-11-03 20:49:05 - cd /src/sys/i386/conf TB --- 2007-11-03 20:49:05 - /usr/bin/make -B LINT TB --- 2007-11-03 20:49:05 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-03 20:49:05 - cd /src TB --- 2007-11-03 20:49:05 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Nov 3 20:49:05 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Sat Nov 3 21:19:25 UTC 2007 TB --- 2007-11-03 21:19:25 - building GENERIC kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-03 21:19:25 - cd /src TB --- 2007-11-03 21:19:25 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sat Nov 3 21:19:25 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Sat Nov 3 21:41:53 UTC 2007 TB --- 2007-11-03 21:41:53 - building PAE kernel (COPTFLAGS=-O2 -pipe) TB --- 2007-11-03 21:41:53 - cd /src TB --- 2007-11-03 21:41:53 - /usr/bin/make -B buildkernel KERNCONF=PAE >>> Kernel build for PAE started on Sat Nov 3 21:41:54 UTC 2007 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /src/sys/dev/usb/if_rum.c:2420: undefined reference to `ieee80211_amrr_choose' if_rum.o(.text+0x3692): In function `rum_rxeof': /src/sys/dev/usb/if_rum.c:936: undefined reference to `ieee80211_find_rxnode' if_rum.o(.text+0x377a):/src/sys/dev/usb/if_rum.c:956: undefined reference to `ieee80211_input' if_rum.o(.text+0x3785):/src/sys/dev/usb/if_rum.c:959: undefined reference to `ieee80211_free_node' if_rum.o(.text+0x37e4):/src/sys/dev/usb/if_rum.c:936: undefined reference to `ieee80211_find_rxnode' if_rum.o(.text+0x2240): In function `rum_start': /src/sys/dev/usb/if_rum.c:1395: undefined reference to `ieee80211_free_node' *** Error code 1 Stop in /obj/src/sys/PAE. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2007-11-03 21:49:09 - WARNING: /usr/bin/make returned exit code 1 TB --- 2007-11-03 21:49:09 - ERROR: failed to build PAE kernel TB --- 2007-11-03 21:49:09 - tinderbox aborted TB --- 0.85 user 3.16 system 9160.10 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 23:38:30 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D30F816A420 for ; Sat, 3 Nov 2007 23:38:30 +0000 (UTC) (envelope-from kps@ucsb.edu) Received: from smtp.ucsb.edu (smtp.ucsb.edu [128.111.24.45]) by mx1.freebsd.org (Postfix) with ESMTP id BFD8013C4AA for ; Sat, 3 Nov 2007 23:38:30 +0000 (UTC) (envelope-from kps@ucsb.edu) Received: from splat.oit.ucsb.edu ([128.111.12.20]) by smtp.ucsb.edu with esmtpsa TLSv1:AES256-SHA:256 id 1IoS23-000MeH-FM; Sat, 03 Nov 2007 16:03:59 -0700 From: Kevin Schmidt Organization: University of California, Santa Barbara To: Freddie Cash Date: Sat, 3 Nov 2007 16:03:50 -0700 User-Agent: KMail/1.9.7 References: <48344.172.16.9.1.1192472836.squirrel@www.xtra-net.be> <200710281319.33309.kps@ucsb.edu> <200710291012.38130.fjwcash+freebsd@gmail.com> In-Reply-To: <200710291012.38130.fjwcash+freebsd@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711031603.52584.kps@ucsb.edu> Cc: current@freebsd.org Subject: Re: Xen Status : FreeBSD-current as Dom/U. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kps@ucsb.edu List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 23:38:30 -0000 On Monday 29 October 2007, Freddie Cash wrote: > On October 28, 2007 01:19 pm Kevin Schmidt wrote: ... > > FWIW, I've tried FreeBSD as an HVM guest on several Linux distros > > as Dom0, Xen 3.0 (3.0.3, 3.0.4) and 3.1 (3.1.0), using Xen packages > > and manual compiles. Linux distros included Ubuntu 7.04 and Debian > > 4. FreeBSD 6.2 and 7.0 -- release and snapshots -- consistently > > fail to boot with a looping "BTX halted" and register dump. If > > there's a way to install stock FreeBSD under Xen HVM, I haven't > > seen it. Without saying whether this is properly a Xen problem or > > FBSD BTX problem, my guess is this type of installation will not > > work until there are BTX changes. > > Crap, that's not what I want to hear. :( > > Any chance you would be willing/able to test using XenEnterprise 4 as > the Dom0 (there's a free version available at: > http://www.citrixxenserver.com/products/Pages/XenExpress.aspx). I don't have appropriate hardware available at the moment. The previous test boxes (Supermicro X7DBE+ motherboards w/Intel procs) are now in use for other purposes, including running Ubuntu 7.10 Xen Dom0 with CentOS5 DomU HVM. -- Kevin Schmidt Office of Information Technology University of California, Santa Barbara North Hall 2124 Santa Barbara, CA 93106-3201 805-893-7779 805-893-5051 FAX kps@ucsb.edu From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 23:42:00 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3478316A41B for ; Sat, 3 Nov 2007 23:42:00 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from ag-out-0708.google.com (ag-out-0708.google.com [72.14.246.249]) by mx1.freebsd.org (Postfix) with ESMTP id E4A5313C4A7 for ; Sat, 3 Nov 2007 23:41:59 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by ag-out-0708.google.com with SMTP id 35so693436aga for ; Sat, 03 Nov 2007 16:41:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=0l329KKRkLwCMeQ2tKujHccSX7edGpsNkuEXw65wp8A=; b=EiTAjnk/jTCU3rP4eFih6m7o1APWSlDN7vBxWlForY53lIkpUCJHNbJ7p1xM5Dr84s7dsPmYLRpPrNcxA0wU3l8WjUrGTFstCD9LoaN3vNwmUWIyiYYGzKfJroETFj90E7itzcPkkenh8t4RGLHZXYOB+LYBPFgEYdvO87p1F/s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=Uc7ojgG8dU0sCSyaTzPujLoodtzIVXcyIG8E9Q9+vO37lxhrfERJGW1bp+Wn+EOdbRWXNQx/MZuRF76T/ev51EMnDjws1kD4Bxe9Tu/L67xGvoJ87jdODQvAxwWz8Eft1JgzcmadRv+12sUlQsw3SfrjhffbKCuijiUUTtPmxQQ= Received: by 10.70.49.1 with SMTP id w1mr4778619wxw.1194133301477; Sat, 03 Nov 2007 16:41:41 -0700 (PDT) Received: from ?192.168.2.2? ( [67.85.89.184]) by mx.google.com with ESMTPS id u25sm6860706ele.2007.11.03.16.41.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 03 Nov 2007 16:41:39 -0700 (PDT) Message-ID: <472CCEAF.8080006@gmail.com> Date: Sat, 03 Nov 2007 15:40:31 -0400 From: "Aryeh M. Friedman" User-Agent: Thunderbird 2.0.0.6 (X11/20071101) MIME-Version: 1.0 To: sam References: <472C3569.3050301@gmail.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: sata atapi on ich9r X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 23:42:00 -0000 >> > The cpu is > CPU: Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz (2666.68-MHz > 686-class CPU) > installed bsd is a i386. How much RAM? > >> Are you SATA/300 devices reported as SATA/150 and/or UDMA33? >> > ad4: 305244MB at ata2-master SATA300 > ad6: 305244MB at ata3-master SATA300 > ad8: 238475MB at ata4-master SATA300 > acd0: DVDROM at ata5-master SATA150 > acd1: DVDROM at ata6-master SATA150 > acd2: DVDR at ata7-master SATA150 Are the acd's 150 or 300 in real life? > > What I find kind of strange too, is that the first harddisk, which > is plugged into sata0, is called ad4.. but never mind. If I enable > the jmicron controller, which is also on the bord, the harddisk gets > even ad10... I will have to play with this because I get: acd0: DVDR at ata4-master SATA150 ad10: 476940MB at ata5-master SATA150 both are SATA/300 (perhaps it has something with what ATA port they are plugged into but as far I know I have them on the first SATA port) > > >> Does it reconize any PATA devices you may have? >> > Don't have any. > >> The only solution I was found was to use 8-current (i.e. from late sept >> on wards stuff worked fine [but only after the version fork]). BTW my >> SATA/300 devices are still reported as SATA/150 and the PATA device is >> not seen at all. > >> >>> >>> Removing atapicam from kernel does help. I can boot, provided there >>> are no cds/dvds in the drives. >>> >>> But trying to play a dvd fails with >>> acd0: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - >>> completing request directly >>> acd0: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - >>> completing request directly >>> acd0: FAILURE - SEND_KEY timed out >>> acd0: FAILURE - MODE_SENSE_BIG timed out >>> no matter, if I try on optiarc/asus. >> >> Is this true even if you have boot from cd in the cmos? > Will try this. Results? From owner-freebsd-current@FreeBSD.ORG Sat Nov 3 23:51:03 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 268A516A417 for ; Sat, 3 Nov 2007 23:51:03 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.235]) by mx1.freebsd.org (Postfix) with ESMTP id CE98E13C481 for ; Sat, 3 Nov 2007 23:51:02 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by wx-out-0506.google.com with SMTP id i29so1046811wxd for ; Sat, 03 Nov 2007 16:50:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=L4JK808BpHJTt35OUV08NIeFokYSjSMxlDJagAWr4y4=; b=NYrR3wDzFORcUKYZ+Q6MXhizcGYSMyHgiMfADjtGcyow406BeVWiGkK38YBGOt0rnBenvksR7wch4IQPOX9SRrg1fdn7n4O40v0hkm9ohscn+8RM1URB5Y9UxPYjRbDFLDE61ZgwAOqCVvDTs5v0GzDRs7vPsBMkaid/tF5Is3A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=PlarlzKPoz2w61ciK4H6Ctq585MpJZl3r3oRGXt8n4g7RH59zYz+G+w/2gua81yQGc6WJPeo+XBNbYT6J0amAK9yhOoNmCLqg1BGjcein799pexMFL0zqjrwC9EWUR2EQRBTPvUT0TKiVLwWBPlEmYWSrvoNDWylSbAVOlpeOYc= Received: by 10.70.39.5 with SMTP id m5mr5309239wxm.1194133845565; Sat, 03 Nov 2007 16:50:45 -0700 (PDT) Received: from ?192.168.2.2? ( [67.85.89.184]) by mx.google.com with ESMTPS id t26sm6884557ele.2007.11.03.16.50.43 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 03 Nov 2007 16:50:44 -0700 (PDT) Message-ID: <472CD0CF.1020909@gmail.com> Date: Sat, 03 Nov 2007 15:49:35 -0400 From: "Aryeh M. Friedman" User-Agent: Thunderbird 2.0.0.6 (X11/20071101) MIME-Version: 1.0 To: "Sean C. Farley" References: <472C3569.3050301@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, samira Subject: Re: sata atapi on ich9r X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Nov 2007 23:51:03 -0000 >> Note to the development team: No I was not tripping when I reported >> these same issues just unable to provide proof > > I guarantee you are not tripping. :( Please inform the my doctors (certain "a not repeatable issue" people on this list) of that fact > >> Note to sam: Do you have any development experience if so I invite you >> to help me in my current project to patch the ata driver to fix all >> these issues (the ata developer told me since he doesn't have access to >> a ich9r/p35 system no patch and/or cvsup would be forth coming on these >> issues)... I am also a developer but at the moment am very tied up with >> making a living so I will give what help I can but can't do the whole >> project alone > > I can try to help, but I am also busy (crunch-time at work). Later tonight I am going to set up an informal clearinghouse list/wiki for this issue so we can be more systematic about it. > > My system is an Asus P5K-E/WiFi with a DVDR LH-20A1S/9L08>. It has 4GB RAM and two SATA hard drives. I have no > PATA drives in it. It is running in RAID mode. I assume amd64 right? > > Unfortunately, this is my only workstation at home, so I will not be > changing versions. I am willing to make changes to the driver. Here is > a patch[1] to recognize and print the ICH9R during boot. It does not > change anything functionally. > > My current notes: > 1. burncd (without atapicam loaded), cdrecord and dd can all produce > warnings. > dd if=/dev/acd0 of=/dev/null bs=10M count=1 burncd gives me no warnings (except on fixate [read time outs]) so this is cosmetics I think (a local issue for you) > > 2. sysinstall will fail during install when copying GENERIC kernel. > This was on my work computer in a Dell Optiplex 745 with 1GB RAM. > atapci0: > acd0: CDRW at ata3-master > SATA150 Like I asked the other person what is the actual performence of acd0 (150 or 300)? > > 3. Do not detach a channel with atacontrol. I tried that on the channel > with the DVD drive. Panic. I will have to look at this. > > 4. I am thinking about writing a program to perform simple tests on the > ATAPI ioctl's. Maybe one exists? Don't know but this is defently a good starting place to gather base data with (have sam run it also) > > 5. PATA is not related since I have no PATA drives in my computer. Ideally I should see the following on my machine (bios sees it) but the above dmesg snip shows I don't: 500 GB HDD SATA/300 OEM DVDR,-RW,+R SATA/300 250 GB HDD PATA UDMA/133 (I have an other 250 GB I want to install as soon this one is reconized) > > Sean > 1. http://www.farley.org/freebsd/tmp/ata-chipset.c.diff I will try it tonight.