From owner-freebsd-stable@FreeBSD.ORG Sun Jan 23 00:23:34 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F9A516A4CE for ; Sun, 23 Jan 2005 00:23:34 +0000 (GMT) Received: from correo.novusordo.net (cdjj.org [216.194.85.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 486E543D41 for ; Sun, 23 Jan 2005 00:23:34 +0000 (GMT) (envelope-from cdjones@novusordo.net) Received: from [127.0.0.1] (cdjj.org [216.194.85.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by correo.novusordo.net (Postfix) with ESMTP id 5D8B92E0BC; Sat, 22 Jan 2005 17:23:29 -0700 (MST) Message-ID: <41F2EE7F.5030500@novusordo.net> Date: Sat, 22 Jan 2005 17:23:27 -0700 From: Chris Jones Organization: Novus Ordo Systems User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Forrest Aldrich References: <41F2D93C.60503@forrie.com> In-Reply-To: <41F2D93C.60503@forrie.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: PF rule statistics (hits) on individual rules.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 00:23:34 -0000 Forrest Aldrich wrote: > I've not been able to determine that there is an equivalent in PF - > though I imagine there must be some method to accomplish this. > > I'd appreciate if someone could help point in the right direction. You want to label rules; a 'pfctl -sl' will then get you information on each label. See Schwartz' article in Sys Admin magazine from March '04. From owner-freebsd-stable@FreeBSD.ORG Sun Jan 23 00:51:56 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8128A16A4CE for ; Sun, 23 Jan 2005 00:51:56 +0000 (GMT) Received: from smtp02.syd.iprimus.net.au (smtp02.syd.iprimus.net.au [210.50.76.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4295943D1D for ; Sun, 23 Jan 2005 00:51:56 +0000 (GMT) (envelope-from tim@robbins.dropbear.id.au) Received: from robbins.dropbear.id.au (210.50.249.169) by smtp02.syd.iprimus.net.au (7.0.036) id 41A76DCB0186F63B; Sun, 23 Jan 2005 11:51:50 +1100 Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id 62925433E; Sun, 23 Jan 2005 11:52:07 +1100 (EST) Date: Sun, 23 Jan 2005 11:52:07 +1100 From: Tim Robbins To: Bj?rn K?nig Message-ID: <20050123005207.GA83787@cat.robbins.dropbear.id.au> References: <41F276CD.8020907@cs.tu-berlin.de> <200501221807.48299.michaelnottebrock@gmx.net> <41F28D79.8080102@cs.tu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41F28D79.8080102@cs.tu-berlin.de> User-Agent: Mutt/1.4.1i cc: freebsd-stable@freebsd.org Subject: Re: correct value for LANG variable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 00:51:56 -0000 On Sat, Jan 22, 2005 at 06:29:29PM +0100, Bj?rn K?nig wrote: > Michael Nottebrock schrieb: > > > > >Use tr [:lower:] [:upper:] instead. > > > I was wondering about a third-party script which always > worked for years with Solaris. I just didn't realized that > this issue concerns a difference between SysV and BSD. The current behaviour of range expressions in tr was required by the Single Unix Specification Version 2 (SUSv2). Version 3 loosened this requirement by making these expressions "unspecified" in locales other than "POSIX". This means you can't use tr with range expressions in any script intending to be portable without first setting LANG to "POSIX". For reference, the systems I know of that sort range expressions according to the current locale are FreeBSD 5 (and later), AIX, and Tru64. The systems I know of that don't sort are FreeBSD 4 (and earlier), GNU (coreutils), and NetBSD. Tim From owner-freebsd-stable@FreeBSD.ORG Sun Jan 23 12:22:22 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02D6816A4CE for ; Sun, 23 Jan 2005 12:22:22 +0000 (GMT) Received: from acheron.ne.client2.attbi.com (acheron.ne.client2.attbi.com [66.31.145.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 842AD43D2F for ; Sun, 23 Jan 2005 12:22:21 +0000 (GMT) (envelope-from msh@blisses.org) Received: from acheron.ne.client2.attbi.com (localhost [127.0.0.1]) j0NCMKAA005321 for ; Sun, 23 Jan 2005 07:22:20 -0500 (EST) Received: (from msh@localhost)j0NCMKf3018417 for freebsd-stable@freebsd.org; Sun, 23 Jan 2005 07:22:20 -0500 (EST) Date: Sun, 23 Jan 2005 07:22:20 -0500 From: Matt Herzog To: freebsd-stable@freebsd.org Message-ID: <20050123122220.GF253@acheron.in.hades> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.4 (acheron.ne.client2.attbi.com [127.0.0.1]); Sun, 23 Jan 2005 07:22:20 -0500 (EST) Subject: loader.conf examples X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 12:22:22 -0000 Can anyone point me to a loader.conf file that's full of a wide range of options? I just want to see some syntax for stuff like video hardware acceleration, audio chipset support etc. I'm confused about how and why modules are built and (seemingly loaded without my having specified any to load) when I have not told my kernel conf file to build anything as a module. As a former NetBSD user, I had expected a monolitic kernel . . . From owner-freebsd-stable@FreeBSD.ORG Sun Jan 23 12:43:07 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4111D16A4CF for ; Sun, 23 Jan 2005 12:43:07 +0000 (GMT) Received: from mail.iinet.net.au (mail-09.iinet.net.au [203.59.3.41]) by mx1.FreeBSD.org (Postfix) with SMTP id C10CF43D1F for ; Sun, 23 Jan 2005 12:43:05 +0000 (GMT) (envelope-from shinjii@virusinfo.rdksupportinc.com) Received: (qmail 2309 invoked from network); 23 Jan 2005 12:43:04 -0000 Received: from unknown (HELO ?10.100.6.10?) (203.206.228.43) by mail.iinet.net.au with SMTP; 23 Jan 2005 12:43:04 -0000 From: Warren To: freebsd-stable@freebsd.org User-Agent: KMail/1.7.2 MIME-Version: 1.0 Content-Disposition: inline Date: Sun, 23 Jan 2005 22:41:34 +1000 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501232241.34900.shinjii@virusinfo.rdksupportinc.com> Subject: 5.3 prob reading 4.11 hdd X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 12:43:07 -0000 I recently took my primary hdd running FreeBSD 4.11-STABLE out of my main machine leaving my 2ndry hdd in the machine and installing FreeBSD5.3-STABLE on it to use as the new primary. When everything was done and i plugged in the 2nd hdd that originally had 4.11-STABLE on it, i was unable to find the individual partitions/slices on there to mount so i could access all the old data i had. I have a basic understanding of FreeBSD but am still not quite proficent when it comes to this sort of thing. Fdisk only shows 1 partition so does disklabel. Below is the disklabel output of the drive im wanting to get all the data from... #ad1s1 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 234436482 0 unused 0 0 # "raw" part, don't edit e: 234436482 0 4.2BSD 2048 16384 89 ================== # /dev/ad1s1c: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 234436482 63 unused 0 0 # "raw" part, don't edit e: 234436482 63 4.2BSD 2048 16384 89 partition c: partition extends past end of unit disklabel: partition c doesn't start at 0! disklabel: An incorrect partition c may cause problems for standard system utilities partition e: partition extends past end of unit ========== # /dev/ad1s1e: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 234436482 63 unused 0 0 # "raw" part, don't edit e: 234436482 63 4.2BSD 2048 16384 89 partition c: partition extends past end of unit disklabel: partition c doesn't start at 0! disklabel: An incorrect partition c may cause problems for standard system utilities partition e: partition extends past end of unit =============== Any help in recovering the copius amounts of data would be greatly appreciated. -- Yours Sincerely Shinjii http://www.shinji.nq.nu From owner-freebsd-stable@FreeBSD.ORG Sun Jan 23 13:02:28 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 361EB16A4CE for ; Sun, 23 Jan 2005 13:02:28 +0000 (GMT) Received: from smtp14.wxs.nl (smtp14.wxs.nl [195.121.6.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE81643D67 for ; Sun, 23 Jan 2005 13:02:27 +0000 (GMT) (envelope-from saffisme@Planet.nl) Received: from planet.nl (ipd50af075.speed.planet.nl [213.10.240.117]) by smtp14.wxs.nl (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0IAR0038OTK242@smtp14.wxs.nl> for freebsd-stable@freebsd.org; Sun, 23 Jan 2005 14:02:26 +0100 (CET) Content-return: allowed Date: Sun, 23 Jan 2005 14:02:36 +0100 From: Jorma Dooper In-reply-to: <20050123122220.GF253@acheron.in.hades> To: Matt Herzog Mail-Followup-To: Matt Herzog , freebsd-stable@freebsd.org Message-id: <20050123130236.GA68315@dvorak.lan> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.4.2.1i References: <20050123122220.GF253@acheron.in.hades> cc: freebsd-stable@freebsd.org Subject: Re: loader.conf examples X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 13:02:28 -0000 On Sun, Jan 23, 2005 at 07:22:20AM -0500, Matt Herzog wrote: > Can anyone point me to a loader.conf file that's full of a wide > range of options? I just want to see some syntax for stuff like > video hardware acceleration, audio chipset support etc. > Try /boot/defaults/loader.conf and loader.conf(5) manual. From owner-freebsd-stable@FreeBSD.ORG Sun Jan 23 13:58:03 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B582416A4CE for ; Sun, 23 Jan 2005 13:58:03 +0000 (GMT) Received: from net-virtual.com (net-virtual.com [69.55.238.186]) by mx1.FreeBSD.org (Postfix) with SMTP id 2FFF943D45 for ; Sun, 23 Jan 2005 13:58:03 +0000 (GMT) (envelope-from mailinglists@net-virtual.com) Received: (qmail 53855 invoked by uid 0); 23 Jan 2005 13:57:58 -0000 Received: from unknown (HELO ?192.168.1.100?) (gregs%net-virtual.com@67.169.110.208) by net-virtual.com with SMTP; 23 Jan 2005 13:57:58 -0000 From: "Net Virtual Mailing Lists" To: Date: Sun, 23 Jan 2005 05:57:53 -0800 Message-Id: <20050123135753.14384@mail.net-virtual.com> X-Mailer: CTM PowerMail 4.2.1 us Carbon MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: NIC card problems.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 13:58:03 -0000 Hello, I regret that I have never posted to this list before, despite the fact I have been using FreeBSD in one form or another for many years now (since 2.x era). I'm a bit cranky, so please do not take any of this wrong. I have a system running FreeBSD 4.10-STABLE (bites tongue). In any event, I just have to ask: what the heck is up with support for network cards?... I mean, seriously, no offense intended to all of the folks who work so hard on this stuff, but every single FreeBSD system I have installed has at one time or another encountered *some* problem relating to its network card. It would be nice if somewhere there was some statement of a "fact" that NIC ____ is known to work well with FreeBSD. I'm aware of all of the FUD out there, about people beating their chests saying how wonderful NIC-A is or NIC-B is, and I've tried 'em all and had problems with each and every one of them so far. Surely someone out there must use FreeBSD in an environment where the "network is the bottleneck"^2 - right?.... By this I mean it is a development system which runs 4 simultaneous processes which run 24x7 (and use network bandwidth in spades - most across a 100mb pipe), a web server, postgres, and nfs server -- some of these processes needed to have MAXDSIZ increased to support up to 1gb (I set MAXDSIZ="(1024*1024*1024)") (and yes, this excessive memory consumption is beyond my control)... The system has 2gb of ram with 8gb of swap (just to make sure!) and is a 600Mhz AMD K6... I've ensured that all of these "memory intensive" processes are forked so that they are able to release their memory when finished. I don't really care how slow it runs -- as long as it runs reliably. I know that this may not be an ideal configuration given what I'm asking from this limited hardware, but I did not experience any reliability problems prior to installing FreeBSD on this exact same hardware (more about this later) with similar tweaks to just make sure everything is able to run (regardless of actual performance). My latest problem is with a: dc0: port 0xe800-0xe8ff mem 0xe6080000- 0xe60803ff irq 11 at device 10.0 on pci0 dc0: Ethernet address: 00:0c:41:ed:ae:85 ... after several hours of *HEAVY* (I'm probably understating this) utilization I get: dc0: TX underrun -- increasing TX threshold dc0: TX underrun -- increasing TX threshold .. repeats numerous times.. dc0: TX underrun -- using store and forward mode .. at this point the system simply reboots. I have attempted to apply a patch () which I found which patches sys/pci/if_dcreg.h and sys/pci/if_dc.c. The patch file was not correct for my version and it looks to me as if sys/pci/ if_dcreg.h already had the changes applied, but I went ahead and added the few minor changes it had for pci/sys/if_dc.c, just on a whim (I should probably note that my version of if_dc.c before the patch was: "$FreeBSD: src/sys/pci/if_dc.c,v 1.9.2.56 2004/04/22 22:03:27 ru Exp"). .. In any event, my pager just went off again, the system rebooted, again with the exact same symptom. You know, I don't really care what NIC I use - I really don't. I'm not so much interested in trying to figure out why this NIC is giving me grief as much as I am in finding one that will work. I would just like someone somewhere to tell me what is a stable NIC to use for FreeBSD, minus all the speculation as to what might or might not work correctly. Just tell me what to buy and I'll go buy it, really I will! If I need a specific chipset with a specific revision that's fine too just please tell me what it is. Hell at this point I'll even look for NICs from specific lot numbers. I'm getting ready to roll out a production version of what I've been testing the last few months and I simply would like to know what NIC I can depend on to not give me these sort of fits.... Thanks and again sorry if I seem frustrated, but you are getting a 10 second summary of 8 years of frustration. Maybe I just have bad luck and always get the "bad NIC", I dunno. Other than this repeating issue with the support for NIC cards, I've found FreeBSd to be absolutely rock solid. It is a real shame that you guys don't get more support from the hardware manufacturers. I truly wish that I were savvy enough to even know where to begin debugging something like this or to help with the development effort. Perhaps someday I will be, who knows. For whatever its worth this exact system has been running Solaris 2.6 (x86 of course) for the last couple of years and has never crashed for any reason, ever. I installed FreeBSD 4.10 because it is what I had laying around and it is what this client wants to use for their project. Over the past week these crashes occur several times throughout the day and obviously I can't release this project until I am satisfied that it will run reliably. ..God you have no idea how much I hated writing 90% this, I hope nobody takes it too negatively -- I am just quite frustrated at the moment. This really almost brought a tear to my eye -- I like FreeBSD that much. .. perhaps NIC cards, FreeBSD, and I simply are incapable of living in harmony.. - Greg From owner-freebsd-stable@FreeBSD.ORG Sun Jan 23 16:51:34 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E92016A4CE; Sun, 23 Jan 2005 16:51:34 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B32543D48; Sun, 23 Jan 2005 16:51:34 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id j0NGpFC7049713; Sun, 23 Jan 2005 11:51:15 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)j0NGpFTc049710; Sun, 23 Jan 2005 16:51:15 GMT (envelope-from robert@fledge.watson.org) Date: Sun, 23 Jan 2005 16:51:14 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: stable@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: imp@FreeBSD.org Subject: NULL pointer deref in sioopen() suggests a close/open race on sio device? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 16:51:34 -0000 Ran into the following panic on a 5-STABLE box this morning, which occurred after hitting Ctrl-D to close a login session on a serial console (ttyd0 at 9600 bps): login: Jan 23 10:43:27 fledge login: 2 LOGIN FAILURES ON ttyd0 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x1c fault code = supervisor write, page not present instruction pointer = 0x8:0xc051537b stack pointer = 0x10:0xe7345988 frame pointer = 0x10:0xe7345994 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 = 45092 (getty) [thread pid 45092 tid 100201 ] Stopped at knote+0x27: cmpxchgl %ecx,0x1c(%edx) db> show pcpu cpuid = 0 curthread = 0xc290d190: pid 45092 "getty" curpcb = 0xe7345da0 fpcurthread = 0xc290d190: pid 45092 "getty" idlethread = 0xc22644b0: pid 11 "idle" APIC ID = 0 currentldt = 0x30 db> trace Tracing pid 45092 tid 100201 td 0xc290d190 knote(c264e098,0,0,c290d190,e73459c4) at knote+0x27 ttwwakeup(c264e000) at ttwwakeup+0xc8 comstart(c264e000) at comstart+0x385 comparam(c264e000,c264e0a4,c264e000,3,0) at comparam+0x253 sioopen(c079f060,3,2000,c290d190,c078e6a0) at sioopen+0x1df spec_open(e7345a84,e7345b40,c058d585,e7345a84,180) at spec_open+0x2b6 spec_vnoperate(e7345a84) at spec_vnoperate+0x13 vn_open_cred(e7345be4,e7345ce4,c08,c2261d80,0) at vn_open_cred+0x419 vn_open(e7345be4,e7345ce4,c08,0,c4289b58) at vn_open+0x1e kern_open(c290d190,804f8e0,0,3,bfbfee18) at kern_open+0xe3 open(c290d190,e7345d14,3,0,292) at open+0x18 syscall(2f,2f,2f,804f8e0,0) at syscall+0x27b Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (5, FreeBSD ELF32, open), eip = 0x280d155b, esp = 0xbfbfedec, ebp = 0xbfbfee18 --- The ps list is a bit boring, but the primary interesting thing is that it looks like the close was going on in one thread just about when the sio swi was scheduled to run also: db> ps pid proc uarea uid ppid pgrp flag stat wmesg wchan cmd 45092 c6762388 e7387000 0 1 1 0004000 [CPU 0] getty ... 132 c235954c e4fbf000 0 0 0 000020c [RUNQ] swi5: clock sio I didn't have a kernel with debugging symbols on-hand, but the above address in knote() is a cmpxchg early in the function, which means it's likely the conditional call to mtx_lock() hitting a NULL mutex pointer for kl_lock. This in turn suggests that something has called ttyrel/tty_close on the TTY in a race with the open, or otherwise NULL'd that pointer via knlist_destroy(). Anyone have any pointers on this one? The TTY code is not my forte... Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Sun Jan 23 17:34:27 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5ACC216A4E7 for ; Sun, 23 Jan 2005 17:34:27 +0000 (GMT) Received: from mx1.highperformance.net (ip30.gte215.dsl-acs2.sea.iinet.com [209.20.215.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBCCE43D55 for ; Sun, 23 Jan 2005 17:34:26 +0000 (GMT) (envelope-from jcw@highperformance.net) Received: from [192.168.1.16] (w16.stradamotorsports.com [192.168.1.16]) j0NHXnH1032881; Sun, 23 Jan 2005 09:33:59 -0800 (PST) (envelope-from jcw@highperformance.net) Date: Sun, 23 Jan 2005 09:33:49 -0800 From: "Jason C. Wells" To: Matt Herzog , freebsd-stable@freebsd.org Message-ID: <6F709B5731DBCBF01573E733@[192.168.1.16]> In-Reply-To: <20050123122220.GF253@acheron.in.hades> References: <20050123122220.GF253@acheron.in.hades> X-Mailer: Mulberry/3.1.5 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Status: No, score=-5.9 required=4.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on s4.stradamotorsports.com Subject: Re: loader.conf examples X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 17:34:27 -0000 --On Sunday, January 23, 2005 7:22 AM -0500 Matt Herzog wrote: > I'm confused about how and why modules are built and (seemingly > loaded without my having specified any to load) when I have not > told my kernel conf file to build anything as a module. As a former > NetBSD user, I had expected a monolitic kernel . . . You can still run a monolithic kernel as I do. You can also use NO_MODULES as a make option to prevent the build and installation of modules. See also MODULES_OVERRIDE is /sys/conf/NOTES. If you never specified a module to load, then no modules should be loaded. (Ref kldstat) Maybe the default behavior has changed. I wouldn't know though since I don't use the default behavior. There are two ways to build a kernel. There is 'make buildkernel' and there is 'config KERNEL; make depend; make' Take care which options apply to which method. Later, Jason C. Wells From owner-freebsd-stable@FreeBSD.ORG Sun Jan 23 17:41:34 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F340F16A4CE for ; Sun, 23 Jan 2005 17:41:33 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9652443D49 for ; Sun, 23 Jan 2005 17:41:33 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id j0NHfD6J050236; Sun, 23 Jan 2005 12:41:13 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)j0NHf5Nt050233; Sun, 23 Jan 2005 17:41:13 GMT (envelope-from robert@fledge.watson.org) Date: Sun, 23 Jan 2005 17:41:04 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Jason C. Wells" In-Reply-To: <6F709B5731DBCBF01573E733@[192.168.1.16]> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Matt Herzog cc: freebsd-stable@freebsd.org Subject: Re: loader.conf examples X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 17:41:34 -0000 On Sun, 23 Jan 2005, Jason C. Wells wrote: > --On Sunday, January 23, 2005 7:22 AM -0500 Matt Herzog > wrote: > > > I'm confused about how and why modules are built and (seemingly > > loaded without my having specified any to load) when I have not > > told my kernel conf file to build anything as a module. As a former > > NetBSD user, I had expected a monolitic kernel . . . > > You can still run a monolithic kernel as I do. You can also use > NO_MODULES as a make option to prevent the build and installation of > modules. See also MODULES_OVERRIDE is /sys/conf/NOTES. > > If you never specified a module to load, then no modules should be > loaded. (Ref kldstat) Maybe the default behavior has changed. I > wouldn't know though since I don't use the default behavior. Modules will sometimes be auto-loaded on demand -- typically this occurs in the following sorts of situations: - Modules will be auto-loaded of another module that depends on the module is loaded. - acpi.ko will be auto-loaded during the boot process if ACPI is enabled. - The kernel will auto-load modules necessary to mount a requested file system if the necessary modules are not already present. - If certain features are enabled in rc.conf, the modules will be loaded to support them if not already present in the kernel, including modules for various ABI compatibility layers (linux, etc), firewalls, ATM-related network pieces, NFS, and some MAC modules. - The ppp(8) command will auto-load modules to support PPPoE if required. The user process requested loading of modules is blocked if the securelevel is > 0. Likewise for the auto-loading of modules relating to file system mounts. The loader will still load modules during the early boot process before the securelevel is available for inspection, however. Robert N M Watson From owner-freebsd-stable@FreeBSD.ORG Sun Jan 23 19:35:37 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53FDC16A4CE for ; Sun, 23 Jan 2005 19:35:37 +0000 (GMT) Received: from cpc2-cove3-6-0-cust88.brhm.cable.ntl.com (cpc2-cove3-6-0-cust88.brhm.cable.ntl.com [81.107.10.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 726B043D3F for ; Sun, 23 Jan 2005 19:35:36 +0000 (GMT) (envelope-from ianjhart@ntlworld.com) Received: from gamma.private.lan (gamma.private.lan [192.168.0.12]) ESMTP id j0NJZXxS008020 for ; Sun, 23 Jan 2005 19:35:34 GMT (envelope-from ianjhart@ntlworld.com) From: ianjhart To: freebsd-stable@freebsd.org Date: Sun, 23 Jan 2005 19:35:32 +0000 User-Agent: KMail/1.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501231935.33147.ianjhart@ntlworld.com> Subject: sendmail failure X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 19:35:37 -0000 That post about AAAA lookups reminds me; the one 5.x box I'm running at work, refuses to deliver it's log files to our mail hub. I know that there are about a million different ways for me to have stuffed this up myself, so please be gentle. That other post reminds me about this because we have broken (i.e. MS) DNS servers. The 4.10 boxes we have all deliver okay though. I'm wondering if WorkAroundBrokenAAAA is okay in 5-STABLE. Anyway I've done side by side comparisons of two servers. They look similar up to the point where the 4.x server opens a network connection and gets the 220 reply. The 5 box apparently does nothing. Using tcpdump, It looks like the A request is never sent, so there's no connection opened. If I run #echo test | sendmail -Am -v -d16.10 root on the 4.10 box the output includes makeconnection: WorkAroundBrokenAAAA: Trying AF_INET lookup (AF_INET6 failed) makeconnection (mail.lan.cardinalnewman.coventry.sch.uk. [10.248.192.10].25 (2)) makeconnection: fd=7 My workstation at home (with 4.10 DNS) shows makeconnection (alpha.private.lan. [192.168.0.2].25 (2)) makeconnection: fd=7 but the 5.3 box at work shows no makeconnection output at all. #uname -a FreeBSD client.lan.cardinalnewman.coventry.sch.uk 5.3-STABLE FreeBSD 5.3-STABLE #8: Thu Dec 23 00:45:38 GMT 2004 ict@client.lan.cardinalnewman.coventry.sch.uk:/usr/obj/usr/src/sys/GENERIC i386 Box was built Aug 2nd and updated from source. stock sendmail AFAIR; rebuilding everything just in case. Version 8.13.1 Compiled with: DNSMAP LOG MAP_REGEX MATCHGECOS MILTER MIME7TO8 MIME8TO7 NAMED_BIND NETINET NETINET6 NETUNIX NEWDB NIS PIPELINING SCANF STARTTLS TCPWRAPPERS USERDB XDEBUG Cheers -- ian j hart From owner-freebsd-stable@FreeBSD.ORG Sun Jan 23 20:05:20 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25DB716A4CE for ; Sun, 23 Jan 2005 20:05:20 +0000 (GMT) Received: from mail09.syd.optusnet.com.au (mail09.syd.optusnet.com.au [211.29.132.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D43A43D2D for ; Sun, 23 Jan 2005 20:05:19 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j0NK5HtA023126 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 24 Jan 2005 07:05:18 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j0NK5G7l030145; Mon, 24 Jan 2005 07:05:17 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j0NK5Glc030144; Mon, 24 Jan 2005 07:05:16 +1100 (EST) (envelope-from pjeremy) Date: Mon, 24 Jan 2005 07:05:16 +1100 From: Peter Jeremy To: Net Virtual Mailing Lists Message-ID: <20050123200515.GB241@cirb503493.alcatel.com.au> References: <20050123135753.14384@mail.net-virtual.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050123135753.14384@mail.net-virtual.com> User-Agent: Mutt/1.4.2i cc: freebsd-stable@freebsd.org Subject: Re: NIC card problems.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 20:05:20 -0000 On Sun, 2005-Jan-23 05:57:53 -0800, Net Virtual Mailing Lists wrote: > It would be nice if somewhere there was >some statement of a "fact" that NIC ____ is known to work well with >FreeBSD. I recall seeing quite a few such statements about different cards over the years. In general, such statements have a limited lifetime because NIC vendors have an ongoing tendency to "improve" their NICs to the point of incompatibility. There are often useful comments about the NICs at the top of the driver code for that NIC (though there's nothing about your AN985). >... after several hours of *HEAVY* (I'm probably understating this) >utilization I get: > >dc0: TX underrun -- increasing TX threshold >dc0: TX underrun -- increasing TX threshold >.. repeats numerous times.. >dc0: TX underrun -- using store and forward mode Real DEC Tulip cards do this when running Tru64 as well. My guess is that it's a bug in the NIC. (And it looks like AMDtek have copied it). >.. at this point the system simply reboots. This is undesirable. However, you have not provided any information that would allow anyone to assist you. Please have a look at http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/article.html > I have attempted to apply a >patch () which I >found which patches sys/pci/if_dcreg.h and sys/pci/if_dc.c. This PR is closed which means that the patches (or functional equivalents) should have already been applied. > I would just like >someone somewhere to tell me what is a stable NIC to use for FreeBSD, I've been using Intel EtherExpress Pro/100+ cards (fxp driver) in some systems where the network gets hammered and haven't had any problems. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Sun Jan 23 20:31:34 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4130516A4CE for ; Sun, 23 Jan 2005 20:31:34 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03DDD43D1F for ; Sun, 23 Jan 2005 20:31:34 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id D580C5EEC; Sun, 23 Jan 2005 15:31:32 -0500 (EST) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 81678-06; Sun, 23 Jan 2005 15:31:31 -0500 (EST) Received: from [192.168.1.3] (pool-68-160-236-186.ny325.east.verizon.net [68.160.236.186]) by pi.codefab.com (Postfix) with ESMTP id 91E335EBF; Sun, 23 Jan 2005 15:31:31 -0500 (EST) Message-ID: <41F4099C.1070807@mac.com> Date: Sun, 23 Jan 2005 15:31:24 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Net Virtual Mailing Lists References: <20050123135753.14384@mail.net-virtual.com> In-Reply-To: <20050123135753.14384@mail.net-virtual.com> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com cc: freebsd-stable@freebsd.org Subject: Re: NIC card problems.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 20:31:34 -0000 Net Virtual Mailing Lists wrote: [ ... ] > [ ... ] It would be nice if somewhere there was > some statement of a "fact" that NIC ____ is known to work well with > FreeBSD. I'm aware of all of the FUD out there, about people beating > their chests saying how wonderful NIC-A is or NIC-B is, and I've tried > 'em all and had problems with each and every one of them so far. Surely > someone out there must use FreeBSD in an environment where the "network > is the bottleneck"^2 - right?.... I have never had a problem with a Intel fxp0 NIC. My company probably has used over fifty of them. I have never had a problem with the 3com 9xx xl0 NICs. About ten of those are in proximity to me over the years. -------- DEC-branded 21x4x Tulip cards have also been good, but I've had three out of 4 Asante cards using a PNIC Tulip lookalike have failed, and I'm dubious about the last one. Avoid Tulip clones. -------- I've not had problems with a sis0 (NatSemi DP83815), but not enough of them to generalize. I've seen mild problems with the vr0 (VIA chipsets) & Broadcom chips, and the Realtek and NE2000 clones that ISPs give to their customers for free may not be worth even that much. -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Sun Jan 23 22:31:20 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A12BF16A4CE for ; Sun, 23 Jan 2005 22:31:20 +0000 (GMT) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35C6D43D1D for ; Sun, 23 Jan 2005 22:31:20 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk) by mail.ticketswitch.com with esmtp (Exim 4.43 (FreeBSD)) id 1CsqGH-0008OS-OB; Sun, 23 Jan 2005 22:31:13 +0000 Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim 4.43 (FreeBSD)) id 1CsqGH-0001yJ-KX; Sun, 23 Jan 2005 22:31:13 +0000 To: freebsd-stable@freebsd.org, mailinglists@net-virtual.com In-Reply-To: <20050123135753.14384@mail.net-virtual.com> Message-Id: From: Pete French Date: Sun, 23 Jan 2005 22:31:13 +0000 Subject: Re: NIC card problems.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 22:31:20 -0000 > You know, I don't really care what NIC I use - I really don't. I'm not > so much interested in trying to figure out why this NIC is giving me > grief as much as I am in finding one that will work. I would just like > someone somewhere to tell me what is a stable NIC to use for FreeBSD, As several other people have mentioned, Intel fxp cards work. I have used a wide variety of these on several system and they all perform excellently and I have never had a problem. Am currently running them in a number of production environments. -pcf. From owner-freebsd-stable@FreeBSD.ORG Sun Jan 23 23:27:42 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A925D16A4CE for ; Sun, 23 Jan 2005 23:27:42 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 240DD43D31 for ; Sun, 23 Jan 2005 23:27:42 +0000 (GMT) (envelope-from se@freebsd.org) Received: from [212.227.126.207] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1Csr8u-0006wD-00; Mon, 24 Jan 2005 00:27:40 +0100 Received: from [80.132.251.245] (helo=Gatekeeper.FreeBSD.org) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1Csr8u-00073L-00; Mon, 24 Jan 2005 00:27:40 +0100 Received: from StefanEsser.FreeBSD.org (StefanEsser [192.168.0.10]) by Gatekeeper.FreeBSD.org (Postfix) with ESMTP id 159665F1B; Mon, 24 Jan 2005 00:27:38 +0100 (CET) Received: by StefanEsser.FreeBSD.org (Postfix, from userid 200) id 513FC2308; Mon, 24 Jan 2005 00:27:38 +0100 (CET) Date: Mon, 24 Jan 2005 00:27:38 +0100 From: Stefan =?iso-8859-1?Q?E=DFer?= To: Net Virtual Mailing Lists Message-ID: <20050123232738.GA78226@StefanEsser.FreeBSD.org> Mail-Followup-To: Stefan =?iso-8859-1?Q?E=DFer?= , Net Virtual Mailing Lists , freebsd-stable@freebsd.org References: <20050123135753.14384@mail.net-virtual.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050123135753.14384@mail.net-virtual.com> User-Agent: Mutt/1.5.6i X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:fa3fae9b6ca38d745862a668565919f6 cc: freebsd-stable@freebsd.org Subject: Re: NIC card problems.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 23:27:42 -0000 On 2005-01-23 05:57 -0800, Net Virtual Mailing Lists wrote: > My latest problem is with a: > > dc0: port 0xe800-0xe8ff mem 0xe6080000- > 0xe60803ff irq 11 at device 10.0 on pci0 > dc0: Ethernet address: 00:0c:41:ed:ae:85 > > ... after several hours of *HEAVY* (I'm probably understating this) > utilization I get: > > dc0: TX underrun -- increasing TX threshold > dc0: TX underrun -- increasing TX threshold > .. repeats numerous times.. > dc0: TX underrun -- using store and forward mode Well, that's nothing to worry too much about ... The device has a data FIFO that is filled with data words fetched by its bus-master DMA engine via the PCI bus. As an optimization, sending the Ethernet frame may optionally start, before all data for the frame has been put into the FIFO. Normally, data is fetched faster by DMA then sent by Ethernet, but if there are a significant number of simultanous PCI data transfers by other devices, there is the risk that the FIFO runs out of data (buffer underflow). In such a case, the current Ethernet frame can't be finished (dummy data and a bogus CRC are added to have the receiving party discard the frame). If such a sittuation exists, the driver will increase the amount of data required in the FIFO, before transmission of the next Ethernet frame starts. After multiple underruns, the driver will configure the Ethernet chip to buffer the full contents of each frame (store and forward mode) and will avoid the early transmission start, since the hardware apparently is not capable of providing data fast enough. > .. at this point the system simply reboots. I have attempted to apply a Then there definitely is a bug somewhere, but not neccessarily in the dc driver. Instead of switching Ethernet cards, you may want to check the PCI performance of your mainboard. The PCI latency timers (master latency timer and individual timers in each device) may play a role. They decide about the maximum "time slice" assigned to each bus-master in turn. Too small a value causes the PCI bus throughput to suffer (because of a few PCI bus clocks are lost each time the next bus-master takes over), while too high a value may cause a device to starve waiting to get access to the bus granted. A master latency timer value of 32 (0x20) should keep the bus-master switch overhead down to 20% (i.e. 80% left for data transfers) and should keep the latency in the range of 1 microsecond per bus-master (i.e. 5 microseconds if there are 2 Ethernet cards, 2 disk controllers and one host bridge active at the same time). In that case, each PCI device could expect to transfer 100 bytes every 5 microseconds. A buffer of 128 bytes ought to suffice for a fast Ethernet card, in that case. But this is a simplified view and calculation. Devices may keep the PCI bus longer than the granted time slice, if there are (what used to be called) "wait cycles" inserted by slow devices. (And some sound cards have been reported to cause high PCI load, even when idle.) The TX threshold messages issued by the dc driver appear more as an indication that the PCI bus is under severe load, than as a hint that the dc driver is causing the reboots, IMHO. Regards, STefan From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 00:00:36 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3351E16A4D4 for ; Mon, 24 Jan 2005 00:00:36 +0000 (GMT) Received: from net-virtual.com (net-virtual.com [69.55.238.186]) by mx1.FreeBSD.org (Postfix) with SMTP id DB92A43D49 for ; Mon, 24 Jan 2005 00:00:35 +0000 (GMT) (envelope-from mailinglists@net-virtual.com) Received: (qmail 82959 invoked by uid 0); 24 Jan 2005 00:00:35 -0000 Received: from unknown (HELO ?192.168.1.100?) (gregs%net-virtual.com@67.169.110.208) by net-virtual.com with SMTP; 24 Jan 2005 00:00:35 -0000 From: "Net Virtual Mailing Lists" To: =?ISO-8859-1?Q?Stefan=20E=DFer?= , Date: Sun, 23 Jan 2005 16:00:32 -0800 Message-Id: <20050124000032.8308@mail.net-virtual.com> In-Reply-To: <20050123232738.GA78226@StefanEsser.FreeBSD.org> References: <20050123232738.GA78226@StefanEsser.FreeBSD.org> X-Mailer: CTM PowerMail 4.2.1 us Carbon MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: NIC card problems.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 00:00:36 -0000 Hello Stefan (and everyone else!), Thank you for your great comments! I think I have a 3c9xx card around here somewhere, I will give that a shot when it reboots the next time (just to see). It looks like for future systems I'll standardize on the Intel fxp-based cards, I really appreciate that advice! As for what might actually be causing this crash: I just checked the PCI configuration and don't see anything in the BIOS which would suggest that anything you mentioned is something I can modify - is that correct? Or are you saying that I am simply pushing past the limits of what this hardware (and PCI bus) is capable of? For whatever it is worth, all I have in terms of PCI cards is this NIC and VGA card (which doesn't run anything gui-like). I am using the onboard IDE controller, not sure if that is considered a "PCI card" for this purpose. There are no sound cards or anything like that installed. The motherboard has no built-in audio. I can copy all of the possible PCI settings I have in my bios setup and what they are set to, if you think that would be helpful here (I would have done it, but I just am not sure if you are hinting at the possibility there may be something wrong with the BIOS configuration here)? I will say that what you are describing could very well be the case, I've got two disks (one on each of the two built-in controllers) running pretty hot-and-heavy during most of this too. - Greg >A master latency timer value of 32 (0x20) should keep the bus-master >switch overhead down to 20% (i.e. 80% left for data transfers) and >should keep the latency in the range of 1 microsecond per bus-master >(i.e. 5 microseconds if there are 2 Ethernet cards, 2 disk controllers >and one host bridge active at the same time). In that case, each PCI >device could expect to transfer 100 bytes every 5 microseconds. A >buffer of 128 bytes ought to suffice for a fast Ethernet card, in >that case. > ... > >The TX threshold messages issued by the dc driver appear more as an >indication that the PCI bus is under severe load, than as a hint that >the dc driver is causing the reboots, IMHO. > >Regards, STefan > From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 00:14:29 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61B1F16A4CE; Mon, 24 Jan 2005 00:14:29 +0000 (GMT) Received: from mail16.syd.optusnet.com.au (mail16.syd.optusnet.com.au [211.29.132.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D7E643D2D; Mon, 24 Jan 2005 00:14:28 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j0O0EQD3017170 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 24 Jan 2005 11:14:27 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j0O0EQ7l030440; Mon, 24 Jan 2005 11:14:26 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j0O0EQV6030439; Mon, 24 Jan 2005 11:14:26 +1100 (EST) (envelope-from pjeremy) Date: Mon, 24 Jan 2005 11:14:26 +1100 From: Peter Jeremy To: Stefan =?iso-8859-1?Q?E=DFer?= , freebsd-stable@FreeBSD.org Message-ID: <20050124001425.GD241@cirb503493.alcatel.com.au> References: <20050123135753.14384@mail.net-virtual.com> <20050123232738.GA78226@StefanEsser.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20050123232738.GA78226@StefanEsser.FreeBSD.org> User-Agent: Mutt/1.4.2i Subject: Re: NIC card problems.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 00:14:29 -0000 On Mon, 2005-Jan-24 00:27:38 +0100, Stefan Eßer wrote: >The TX threshold messages issued by the dc driver appear more as an >indication that the PCI bus is under severe load, than as a hint that >the dc driver is causing the reboots, IMHO. Under Tru64, I've seen Tulip cards report backoff to 1024 byte FIFO and then switching to store-and-forward. That's about 100µsec latency and nothing should be holding the PCI bus that long. I am inclined to believe that something is stuffed in the PCI interface logic in the NIC. -- Peter Jeremy From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 00:19:11 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4530F16A4CE; Mon, 24 Jan 2005 00:19:11 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE12F43D1F; Mon, 24 Jan 2005 00:19:10 +0000 (GMT) (envelope-from imp@harmony.village.org) Received: from localhost (localhost [IPv6:::1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j0O0Hqj7079127; Sun, 23 Jan 2005 17:17:52 -0700 (MST) (envelope-from imp@harmony.village.org) Date: Sun, 23 Jan 2005 17:17:52 -0700 (MST) Message-Id: <20050123.171752.74671507.imp@harmony.village.org> To: se@freebsd.org From: Warner Losh In-Reply-To: <20050123232738.GA78226@StefanEsser.FreeBSD.org> References: <20050123135753.14384@mail.net-virtual.com> <20050123232738.GA78226@StefanEsser.FreeBSD.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org cc: mailinglists@net-virtual.com Subject: Re: NIC card problems.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 00:19:11 -0000 > The TX threshold messages issued by the dc driver appear more as an > indication that the PCI bus is under severe load, than as a hint that > the dc driver is causing the reboots, IMHO. I've also seen them when the card is a CardBus card, which may indicate some slightly pessimal performance parameters are set at the pci cardbus bridge... Warner From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 01:25:53 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BE2B16A4CE; Mon, 24 Jan 2005 01:25:53 +0000 (GMT) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B47A43D31; Mon, 24 Jan 2005 01:25:49 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.13.0/8.13.0) with ESMTP id j0O1Pkgl022743; Sun, 23 Jan 2005 20:25:47 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Sun, 23 Jan 2005 20:25:45 -0500 To: Robert Watson , stable@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) cc: imp@freebsd.org Subject: Re: NULL pointer deref in sioopen() suggests a close/open race on sio device? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 01:25:54 -0000 At 4:51 PM +0000 1/23/05, Robert Watson wrote: > >The ps list is a bit boring, but the primary interesting thing is >that it looks like the close was going on in one thread just about >when the sio swi was scheduled to run also: [...] > This in turn suggests that something has called ttyrel/tty_close >on the TTY in a race with the open, or otherwise NULL'd that pointer >via knlist_destroy(). Anyone have any pointers on this one? The >TTY code is not my forte... FWIW, I just recently setup some of my freebsd boxes with serial consoles. It *seems* to me that if I type in 'shutdown -r now' when I am logged into a serial console, there's often some long delay before the reboot happens. It's long enough to be annoying, but not long enough to motivate me to look into it. My machines usually have a monitor/keyboard also setup on them, so my solution has been to avoid using the serial console... -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 08:11:34 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1DC116A4CE for ; Mon, 24 Jan 2005 08:11:34 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 7CB7E43D6A for ; Mon, 24 Jan 2005 08:11:33 +0000 (GMT) (envelope-from emanuel.strobl@gmx.net) Received: (qmail invoked by alias); 24 Jan 2005 08:11:32 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp001) with SMTP; 24 Jan 2005 09:11:32 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-stable@freebsd.org Date: Mon, 24 Jan 2005 09:11:27 +0100 User-Agent: KMail/1.7.2 X-Birthday: 10/06/72 X-CelPhone: +49 173 9967781 X-Tel: +49 89 18947781 X-Country: Germany X-Address: Munich, 80686 X-OS: FreeBSD MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1329756.RDoxekAvrG"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501240911.31608.emanuel.strobl@gmx.net> X-Y-GMX-Trusted: 0 Subject: watchdogd panic when shutdown -p X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 08:11:35 -0000 --nextPart1329756.RDoxekAvrG Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello, I have a kernel with SW_WATCHDOG and simply enabled watchdog in rc.conf. I haven't found much info on that topic but I guess when the machine hangs= =20 (watchdogd doesn't get a result from the trivial fsck (what's that btw?)) t= he=20 kernel will reset the machine. Best would be if I never see watchdog in=20 action but I'm seeing a panic message after some interrupt statistics (see= =20 below) and the machine doesn't power off (like it does without watchdogd=20 enabled). Any hints? I played a bit with setting the -t timeoutseconds but this didn'= t=20 change anything, the machine doesn't power off. Is it correct that the=20 trivials filesystem check of watchdogd is really done every second by=20 default? Thanks a lot, =2DHarry Uptime: 25m6s interrupt total irq0: clk 771518 irq3: sio1 740 irq8: rtc 192856 irq10: fxp0 103 irq11: atapci1 21 irq12: fwohci0++ 69 irq13: npx0 1 irq14: ata0 51 irq15: ata1 17284 Total 982643 panic: watchdog timeout Uptime: 25m7s --nextPart1329756.RDoxekAvrG Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB9K2zBylq0S4AzzwRAoRIAJ47AKyAF1QRZ4Ej2ZuLZdH4840yzgCfTAAF DunrL8t+9c/KOsILQEUgkwE= =TZb6 -----END PGP SIGNATURE----- --nextPart1329756.RDoxekAvrG-- From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 08:54:25 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C216816A4CF for ; Mon, 24 Jan 2005 08:54:25 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 987EF43D58 for ; Mon, 24 Jan 2005 08:54:24 +0000 (GMT) (envelope-from emanuel.strobl@gmx.net) Received: (qmail invoked by alias); 24 Jan 2005 08:54:23 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp007) with SMTP; 24 Jan 2005 09:54:23 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-current@freebsd.org Date: Mon, 24 Jan 2005 09:54:20 +0100 User-Agent: KMail/1.7.2 References: <1106134006.1132.12.camel@genius2.i.cz> <1106227110.716.11.camel@genius2.i.cz> <20050122235234K.akiyama@jp.FreeBSD.org> In-Reply-To: <20050122235234K.akiyama@jp.FreeBSD.org> X-Birthday: 10/06/72 X-CelPhone: +49 173 9967781 X-Tel: +49 89 18947781 X-Country: Germany X-Address: Munich, 80686 X-OS: FreeBSD MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1242613.vfDoILstTx"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501240954.25511.emanuel.strobl@gmx.net> X-Y-GMX-Trusted: 0 cc: Shunsuke Akiyama cc: Michal Mertl cc: freebsd-stable@freebsd.org Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 08:54:25 -0000 --nextPart1242613.vfDoILstTx Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Samstag, 22. Januar 2005 15:52 schrieb Shunsuke Akiyama: [...] > Good work! > > I've updated your patch. If attached patch works correctly with new > revision chip, I'll commit this. Please test attached patch, and tell > me the result. I tested it (after removing the DOS ^M characters) against uplcom.c 1.25 wi= th=20 my RELENG_5 system. Everything seems fine, I just cannot ~p (put) files with cu/tip, but that=20 doesn't work with a real serial cable either. So committing and MFC (1.26) after 3 days would be great for me. Thank you all a lot, =2DHarry > > Regards, --nextPart1242613.vfDoILstTx Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB9LfBBylq0S4AzzwRAouvAJ92Kr29Y5Rv1heyLGG6SodIO+Q1tgCgiZxi D800zPpDeTlCrKUHJ8Yct6g= =3Bsq -----END PGP SIGNATURE----- --nextPart1242613.vfDoILstTx-- From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 09:25:55 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53ACA16A4CE; Mon, 24 Jan 2005 09:25:55 +0000 (GMT) Received: from mailhost.catholic.org (mailhost.catholic.org [66.122.14.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC21743D1D; Mon, 24 Jan 2005 09:25:54 +0000 (GMT) (envelope-from wsk@catholic.org) Received: from webmail.catholic.org (webmail.catholic.org [66.122.14.27]) j0O9Pqh6024422; Mon, 24 Jan 2005 01:25:52 -0800 Received: from 211.96.21.195 (SquirrelMail authenticated user wsk) by webmail.catholic.org with HTTP; Mon, 24 Jan 2005 09:25:52 -0000 (GMT) Message-ID: <57062.211.96.21.195.1106558752.squirrel@webmail.catholic.org> Date: Mon, 24 Jan 2005 09:25:52 -0000 (GMT) From: "wsk" To: current@freebsd.org User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal cc: support@comtrol.com cc: stable@freebsd.org cc: questions@freebsd.org Subject: Rocketport uPCI ioaddr mapping failed under FreeBSD-5.3&CURRENT X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 09:25:55 -0000 hi,folks: after installed RocketPort uPCI card into my box;it dumps the follow eror msgs: rp0: port 0xde00-0xdeff,0xdd80-0xddff mem 0xfcedff80-0xfcedffff irq 19 at device 10.0 on pci2 rp0: failed: rid 0x10 is memory, requested 4 rp0: ioaddr mapping failed for RocketPort(PCI). device_attach: rp0 attach returned 6 and pciconfig the rp0: rp0@pci2:10:0: class=0x078000 card=0x080511fe chip=0x080511fe rev=0x01 hdr=0x00 vendor = 'Comtrol Corp' class = simple comms and downloaded the 1800255A file and follwed the README from www.comtrol.com. During the buildkernel, I got errors: cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I../../.. -I../../../contrib/dev/acpica -I../../../contrib/altq -I../../../contrib/ipfilter -I../../../contrib/pf -I../../../contrib/dev/ath -I../../../contrib/dev/ath/freebsd -I../../../contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror ../../../dev/rp/rp.c ../../../dev/rp/rp.c: In function `rp_do_receive': ../../../dev/rp/rp.c:772: error: request for member `l_rint' in something not a structure or union ../../../dev/rp/rp.c:820: error: request for member `l_rint' in something not a structure or union ../../../dev/rp/rp.c: In function `rp_handle_port': ../../../dev/rp/rp.c:850: error: request for member `l_modem' in something not a structure or union ../../../dev/rp/rp.c:854: error: request for member `l_modem' in something not a structure or union ../../../dev/rp/rp.c:855: error: request for member `l_modem' in something not a structure or union ../../../dev/rp/rp.c: In function `rp_do_poll': ../../../dev/rp/rp.c:903: error: request for member `l_start' in something not a structure or union ../../../dev/rp/rp.c: In function `rp_attachcommon': ../../../dev/rp/rp.c:982: warning: assignment makes integer from pointer without a cast ../../../dev/rp/rp.c:985: warning: assignment makes integer from pointer without a cast ../../../dev/rp/rp.c:988: warning: assignment makes integer from pointer without a cast ../../../dev/rp/rp.c:991: warning: assignment makes integer from pointer without a cast ../../../dev/rp/rp.c:994: warning: assignment makes integer from pointer without a cast ../../../dev/rp/rp.c:997: warning: assignment makes integer from pointer without a cast ../../../dev/rp/rp.c: In function `rp_releaseresource': ../../../dev/rp/rp.c:1077: warning: passing arg 1 of `destroy_dev' makes pointer from integer without a cast ../../../dev/rp/rp.c: In function `rpopen': ../../../dev/rp/rp.c:1088: error: argument "dev" doesn't match prototype ../../../dev/rp/rp.c:672: error: prototype declaration ../../../dev/rp/rp.c:1096: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1097: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1102: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1108: error: invalid type argument of `->' ../../../dev/rp/rp.c:1120: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1145: warning: assignment makes pointer from integer without a cast ../../../dev/rp/rp.c:1150: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1200: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1201: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1202: error: request for member `l_modem' in something not a structure or union ../../../dev/rp/rp.c:1212: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1221: error: request for member `l_open' in something not a structure or union ../../../dev/rp/rp.c:1224: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c: In function `rpclose': ../../../dev/rp/rp.c:1246: error: argument "dev" doesn't match prototype ../../../dev/rp/rp.c:673: error: prototype declaration ../../../dev/rp/rp.c:1252: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1253: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1257: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1264: error: request for member `l_close' in something not a structure or union ../../../dev/rp/rp.c:1271: warning: implicit declaration of function `ttyclose' ../../../dev/rp/rp.c:1271: warning: nested extern declaration of `ttyclose' ../../../dev/rp/rp.c: In function `rpread': ../../../dev/rp/rp.c:1321: error: argument "dev" doesn't match prototype ../../../dev/rp/rp.c:676: error: prototype declaration ../../../dev/rp/rp.c:1326: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1327: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1331: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1335: error: request for member `l_read' in something not a structure or union ../../../dev/rp/rp.c: In function `rpwrite': ../../../dev/rp/rp.c:1345: error: argument "dev" doesn't match prototype ../../../dev/rp/rp.c:674: error: prototype declaration ../../../dev/rp/rp.c:1351: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1352: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1356: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1367: error: request for member `l_write' in something not a structure or union ../../../dev/rp/rp.c: In function `rpioctl': ../../../dev/rp/rp.c:1388: error: argument "dev" doesn't match prototype ../../../dev/rp/rp.c:675: error: prototype declaration ../../../dev/rp/rp.c:1403: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1404: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1410: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1413: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1415: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1418: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1460: warning: passing arg 1 of `minor' makes pointer from integer without a cast ../../../dev/rp/rp.c:1482: error: request for member `l_ioctl' in something not a structure or union ../../../dev/rp/rp.c: In function `rp_disc_optim': ../../../dev/rp/rp.c:1763: error: request for member `l_rint' in something not a structure or union ../../../dev/rp/rp.c: At top level: ../../../dev/rp/rp.c:2364: error: syntax error before "rp_pci_mod" ../../../dev/rp/rp.c:2364: warning: type defaults to `int' in declaration of `rp_pci_mod' ../../../dev/rp/rp.c:2364: warning: initialization makes integer from pointer without a cast ../../../dev/rp/rp.c:2364: warning: excess elements in scalar initializer ../../../dev/rp/rp.c:2364: warning: (near initialization for `rp_pci_mod') ../../../dev/rp/rp.c:2364: warning: excess elements in scalar initializer ../../../dev/rp/rp.c:2364: warning: (near initialization for `rp_pci_mod') ../../../dev/rp/rp.c:2364: warning: data definition has no type or storage class../../../dev/rp/rp.c:2364: warning: type defaults to `int' in declaration of `DECLARE_MODULE' ../../../dev/rp/rp.c:2364: warning: parameter names (without types) in function declaration ../../../dev/rp/rp.c:2364: warning: data definition has no type or storage class../../../dev/rp/rp.c:2809: error: syntax error before "rp_isa_mod" ../../../dev/rp/rp.c:2809: warning: type defaults to `int' in declaration of `rp_isa_mod' ../../../dev/rp/rp.c:2809: warning: initialization makes integer from pointer without a cast ../../../dev/rp/rp.c:2809: warning: excess elements in scalar initializer ../../../dev/rp/rp.c:2809: warning: (near initialization for `rp_isa_mod') ../../../dev/rp/rp.c:2809: warning: excess elements in scalar initializer ../../../dev/rp/rp.c:2809: warning: (near initialization for `rp_isa_mod') ../../../dev/rp/rp.c:2809: warning: data definition has no type or storage class../../../dev/rp/rp.c:2809: warning: type defaults to `int' in declaration of `DECLARE_MODULE' ../../../dev/rp/rp.c:2809: warning: parameter names (without types) in function declaration ../../../dev/rp/rp.c:2809: warning: redundant redeclaration of 'DECLARE_MODULE' ../../../dev/rp/rp.c:2364: warning: previous declaration of 'DECLARE_MODULE' was here ../../../dev/rp/rp.c:2809: warning: data definition has no type or storage class*** Error code 1 Stop in /usr/src/sys/i386/compile/WSK. thinks in any Re with appresiates! ----------------------------------------- This email was sent using FREE Catholic Online Webmail! http://webmail.catholic.org/ From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 09:42:44 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DF4216A4CE for ; Mon, 24 Jan 2005 09:42:44 +0000 (GMT) Received: from smradoch.ath.cx (r2g224.chello.upc.cz [62.245.70.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93ED543D5C for ; Mon, 24 Jan 2005 09:42:43 +0000 (GMT) (envelope-from neuhauser@chello.cz) Received: by smradoch.ath.cx (Postfix, from userid 1001) id 56D021F87BED; Mon, 24 Jan 2005 10:42:41 +0100 (CET) Date: Mon, 24 Jan 2005 10:42:41 +0100 From: Roman Neuhauser To: Darryl Okahata Message-ID: <20050124094241.GA1723@isis.wad.cz> References: <20050120163734.B38962@Denninger.Net> <200501202326.PAA16070@mina.soco.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200501202326.PAA16070@mina.soco.agilent.com> User-Agent: Mutt/1.5.6i cc: freebsd-stable@freebsd.org cc: Karl Denninger Subject: Re: Bad disk or kernel (ATA Driver) problem? - SOLVED X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 09:42:44 -0000 # darrylo@soco.agilent.com / 2005-01-20 15:26:21 -0800: > Karl Denninger wrote: > > > Seagate's have been getting very poor performance reviews of late..... > > Do you have any URLs? While I haven't been following disk drives > closely, I haven't seen anything that points at "very poor" performance > ("average"/boring performance, yes, but nothing really bad). I had a Barracuda IV or V that the Samsung I bought as a replacement outperforms (e. g. opening a Maildir in mutt) by an order of magnitude. I had to wait *minutes* to get into some of my larger maildirs with the Seagate whereas now it's a matter of seconds. A test at xbitlabs.com (http://www.xbitlabs.com/articles/storage/display/21hdd-160_18.html) relates large performance differences between Seagate disks to firmware revisions. If you buy a drive with the right firmware, you'll get decent performance. If you miss, you'll suffer greatly. -- FreeBSD 4.10-STABLE 10:19AM up 3:02, 4 users, load averages: 0.00, 0.01, 0.00 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 09:43:02 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B452116A4CF for ; Mon, 24 Jan 2005 09:43:02 +0000 (GMT) Received: from raven.ravenbrook.com (raven.ravenbrook.com [193.82.131.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C52C43D39 for ; Mon, 24 Jan 2005 09:43:01 +0000 (GMT) (envelope-from nb@ravenbrook.com) Received: from thrush.ravenbrook.com (thrush.ravenbrook.com [193.112.141.145]) by raven.ravenbrook.com (8.12.6p3/8.12.6) with ESMTP id j0O9gwuo089007 for ; Mon, 24 Jan 2005 09:42:58 GMT (envelope-from nb@ravenbrook.com) Received: from thrush.ravenbrook.com (localhost [127.0.0.1]) j0O9gwrB035318 for ; Mon, 24 Jan 2005 09:42:58 GMT (envelope-from nb@thrush.ravenbrook.com) From: Nick Barnes To: freebsd-stable@FreeBSD.org In-Reply-To: <20050124000032.8308@mail.net-virtual.com> from "Net Virtual Mailing Lists" of "Sun, 23 Jan 2005 16:00:32 -0800" Date: Mon, 24 Jan 2005 09:42:58 +0000 Message-ID: <35317.1106559778@thrush.ravenbrook.com> Sender: nb@ravenbrook.com Subject: Re: NIC card problems.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 09:43:02 -0000 At 2005-01-24 00:00:32+0000, "Net Virtual Mailing Lists" writes: > Hello Stefan (and everyone else!), > > Thank you for your great comments! I think I have a 3c9xx card around > here somewhere, I will give that a shot when it reboots the next time > (just to see). It looks like for future systems I'll standardize on the > Intel fxp-based cards, I really appreciate that advice! A last piece of advice: get real EtherExpress cards. A number of Intel motherboards come with onboard Ethernet interfaces (maybe they all do now), which the fxp driver understands, but the performance of such interfaces is reputed to be much lower. Nick Barnes From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 09:51:02 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35B2016A4CE; Mon, 24 Jan 2005 09:51:02 +0000 (GMT) Received: from smtp-vbr8.xs4all.nl (smtp-vbr8.xs4all.nl [194.109.24.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93B2F43D62; Mon, 24 Jan 2005 09:50:59 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr8.xs4all.nl (8.12.11/8.12.11) with ESMTP id j0O9ouqK050837; Mon, 24 Jan 2005 10:50:57 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.1/8.12.9) with ESMTP id j0O9ot4n040179; Mon, 24 Jan 2005 10:50:55 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.1/8.13.1/Submit) id j0O9otKa040178; Mon, 24 Jan 2005 10:50:55 +0100 (CET) (envelope-from wb) Date: Mon, 24 Jan 2005 10:50:55 +0100 From: Wilko Bulte To: Peter Jeremy Message-ID: <20050124095055.GC40050@freebie.xs4all.nl> References: <20050123135753.14384@mail.net-virtual.com> <20050123232738.GA78226@StefanEsser.FreeBSD.org> <20050124001425.GD241@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20050124001425.GD241@cirb503493.alcatel.com.au> X-OS: FreeBSD 4.11-RC2 User-Agent: Mutt/1.5.6i X-Virus-Scanned: by XS4ALL Virus Scanner cc: freebsd-stable@freebsd.org Subject: Re: NIC card problems.... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 09:51:02 -0000 On Mon, Jan 24, 2005 at 11:14:26AM +1100, Peter Jeremy wrote.. > On Mon, 2005-Jan-24 00:27:38 +0100, Stefan Eßer wrote: > >The TX threshold messages issued by the dc driver appear more as an > >indication that the PCI bus is under severe load, than as a hint that > >the dc driver is causing the reboots, IMHO. > > Under Tru64, I've seen Tulip cards report backoff to 1024 byte FIFO and > then switching to store-and-forward. That's about 100µsec latency and > nothing should be holding the PCI bus that long. I am inclined to > believe that something is stuffed in the PCI interface logic in the NIC. According to my Tru64 colleagues not all Tulip chip versions are born equal, some are better than others. I do not have more detail here. -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 11:22:07 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A955416A4CE for ; Mon, 24 Jan 2005 11:22:07 +0000 (GMT) Received: from web14824.mail.yahoo.com (web14824.mail.yahoo.com [216.136.225.195]) by mx1.FreeBSD.org (Postfix) with SMTP id 75E5143D39 for ; Mon, 24 Jan 2005 11:22:07 +0000 (GMT) (envelope-from rosti_bsd@yahoo.com) Received: (qmail 2444 invoked by uid 60001); 24 Jan 2005 11:22:07 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=eDZxBWDpTS3nzW9APxbIkFxWQP2V4b93p7tpr9CyhyCxcBSs/3y1FAwooZ/iaCI4FkHRIeZkqE/iXRlJF0RRvtE9wdc2SDh7IPHepy79LLiSmkODxq5WCz49EapvVA0eITFP+VVmHhi65PcHHHNitiMa0oFjJhAxkETkjlrfc64= ; Message-ID: <20050124112207.2442.qmail@web14824.mail.yahoo.com> Received: from [212.143.154.227] by web14824.mail.yahoo.com via HTTP; Mon, 24 Jan 2005 03:22:07 PST Date: Mon, 24 Jan 2005 03:22:07 -0800 (PST) From: Rostislav Krasny To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: sometimes 5.3-RELEASE-p5 is stuck at the last steps of shutdown X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 11:22:07 -0000 Hello all. I use FreeBSD 5.3-RELEASE-p5 on i386. Sometimes my system is stuck at the last steps of shutdown. Following quoting is what I saw yesterday when my system was stuck again (the last lines): init: some processes would not die; ps axl advised Waiting (max 60 seconds) for system process `vnlru' to stop... done Waiting (max 60 seconds) for system process `bufdaemon' to stop... done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining... 2 1 0 0 0 done No buffers busy after final sync I've experienced such system stucks after short and also not so short uptimes. I don't know how to reproduce it for sure. Before that specific shutdown I ran Xorg 6.8.1 with KDE 3.3.2 but then I quit KDE, quit X and logged out. I don't use either xdm nor kdm. On the next boot '/', '/tmp' and '/usr' were declared as not properly dismounted. How could the shutdown processing be fixed so it will never stuck? __________________________________ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 12:31:03 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B1D116A4CE; Mon, 24 Jan 2005 12:31:03 +0000 (GMT) Received: from osiris.itlegion.ru (osiris.itlegion.ru [84.21.226.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EE1143D55; Mon, 24 Jan 2005 12:31:01 +0000 (GMT) (envelope-from matrix@itlegion.ru) Received: from artem ([192.168.0.12]) by osiris.itlegion.ru (8.13.1/8.13.1) with SMTP id j0OCUmAP098861; Mon, 24 Jan 2005 15:30:48 +0300 (MSK) (envelope-from matrix@itlegion.ru) X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 63725, updated: 22.01.2005] Message-ID: <00ba01c50211$23389ee0$0c00a8c0@artem> From: "Artem Kuchin" To: "Robert Watson" References: Date: Mon, 24 Jan 2005 15:26:42 +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.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 cc: freebsd-stable@freebsd.org Subject: Lock up problems with 5.3-STABLE (was: Cannot build kernel with options WITNESS) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 12:31:03 -0000 > On Sun, 23 Jan 2005, Artem Kuchin wrote: > >> > On Sat, 22 Jan 2005, Artem Kuchin wrote: >> > >> >> I cvssed just an hour ago. 5.3-STABLE and cannot build kernel with >> >> WITNES. It complains: >> > >> > This occurs when building WITNESS without DDB in the kernel, which was not >> > a tested build case when I added "show alllocks", and apparently is a >> > relatively uncommon configuration as you're the first person to bump into >> > it. I've just committed the fix as subr_witness.c:1.187 in HEAD, and >> > subr_witness.c:1.178.2.4 in RELENG_5. Please let me know if this doesn't >> > fix the problem for you. >> >> It fixed the problem. I am actually stuggling with unpredictable weird >> lock ups, when the host can be pinged but i cannot connect via >> ssh/telnet or httpd or anything else. It happens w/o any visible reason. >> I am running several jails with mysql and apache in each and canot make >> the whole system stable yet. > > This is typically a sign of one of two problems: > > - The system is live locked due to very high load, so the ithread, > netisrs, etc, in the kernel run fine, but user processes don't get a > chance to run. > > - The system is dead locked due to user space processes getting wedged on > common locks, but the kernel ithreads and netisrs can keep on > responding. > > I generally assume that it's a deadlock as opposed to a live lock. I'd > compile a kernel with DDB, KDB, WITNESS, and BREAK_TO_DEBUGGER. When the > system appears to wedge, break into the debugger using a console or serial > break (FYI: serial break is more reliable, and you get the benefit of > being able to easily copy and paste debugging output using the serial > console for DDB). Use "show alllocks" and "show lockedvnods" to examine > most of the system's locking state. Changes are, either all the > interesting processes are stacked up on VFS or VM locks, since those kinds > of deadlocks produce the exact symptoms you describe: ping works fine > because it only hits the netisr, but when you open TCP connections, the > sshd (etc) block on VM or VFS locks attempting to fork new children or > access a file in the file system name space. At first, the TCP > connections will establish but there will be no application data; after a > bit, they will not even return a SYN/ACK because the listen queue for the > listen socket has filled. > Well, i cvsed and reconpiled the kernel with WITNESS, INVARINATS, turned off adaptive giant and got a lock today at 7 am. Since the server is remotely controlled i took my digital camera because i cannot connect serial console to it and went to the server. I expetced to see some special message about something going wrong, break into debugger (CTRL+ALT+ESC) and to take some pictures of dumps of console. But, i saw nothing. The lasrt message on th screen was about ssh loging last evening and the last message in /var/log/all.log was about entropy save from cron. I could not break into debugger usinmg CTRL-ALT+ESC. I did nothing. So, it looked like a hard lock. At this point i would like to tell the whole story. We bought this server in may 2004 and decided to extemsively test the hardware while there were not 5.3. We actually expected it around august. SO, we installed 5-CURRENT and ran high load tests (cpu, memory, disk storage, network) from /usr/ports/benchmark at the same time and one-by-one several weeks. There were not a glitch. After that we turned it off and waited for RELEASE. RELEASE has come and we begun to setup the servre as it should work. As the server's primary mission is to host a buch of site we decided to setup jails for each site, So we did in december and put the server on prividers co-location severals kilometer away from the office. Next day the server locked up. We were surprised but just rebooted it, It locked up the next day gain. We cvsupped and rebuild the system and the jails. The server locked up the next day. During the new year break i have figureed that if there are more that one jail running the server locks withun 24 hours with very hight probablity and within 48 hours with 100% probability. I wrote into freebsd-stable about it. You have asked for debugger dump (pcpu, list of lock, e.t.c). I could not do it at that time, so, i did not reply and just cvsupped in the beginning of january and rebuilt the system and the jails again. Magically, after that i could run 5 jails (did not tried more) for over a week and i already decided that the bug was fixed and I could host the site. Alas, the next glitch did not wait to long. After a few more days i saw a srange situatuon - i could not connect to server using SSH. SSH replied about auth key or something like that. I rebootied the system and ssh worked fine. Still have no idea what that was, but i setuo IPFIREWALL and a telnet server for accept connection only from one ip address, so, if ssh fails I could use telnet. After that i moved a real site with perl scripts, 1GB database, mail account (using qmail+vpopmail) into one of the jails and the next day got the next problem: I could ping server, but could not connect using ssh, www, telnet (110,25,23). I tried to recompile the kernel with INVARINATS, WITNESS and disable the adaptive giant. I could not, so I wrote about it to you. You fixed the source and now i recompliled the source again and today got a lock again with all those options enabled and this time i could not ping the server. I could thing that there is semething wrong with the hardware, but it passed many days of testing. Anyway, my current idea are 1) Something wrong with jail code 2) Something wrong with SMP code 3) Something wrong with HYPERTHREADING code 4) Something wrong with Memory disk code (md device, which i use) 5) Something wrong with the hardware So, today, i opened bios, truned off hyperthreaading, fast strinmg operations and all other 'more advanced' features in the bios. Turned off IDE controller the motherboard. This rule out HYPERTHREADING code problem and somewaht hardware problem. I turned off MD usage (not more memory disk, but actually i need it very badly). So i rule out the md code problem. Now, i will run some web access test (simulation of browsing for a week). It the sever does not lock up, i will consider that i have found a workaround for some hidden bug and the bug is somewere in md, ht code or hardware. If it locks up again the i will giveup jails and try for one more week. If it does not lock up - jail code is the problem. If it locks up without jails, then i will turn off SMP and try again. If it locks up without nothing, then hardware if faulty and will have futher choice of hanging myself or shooting in the head. I would like to see your and others' comments on the story and i have one more question: what does options _KPOSIX_PRIORITY_SCHEDULING do? May it be somehow related to the problem? The hardware is: MB dual xeon Supermicro X5DPE-G2 CPU P4 XEON 2,667Ghz 512Kb cache 533mhz socket 604 2 Gb 266Mhz, DDR, ECC, Reg, 1GB dimm 4 HDDs 120Gb (seagate baracuda 7200.7) 3Ware Escalade 8506-4LP Case Supermicro SC822T-550LP Slim DVD/CD-RW Toshiba SD-R2412B IDE (OEM) The todays kernel CONFIG wich got locked: machine i386 cpu I486_CPU cpu I586_CPU cpu I686_CPU ident OMNI2 options SMP options QUOTA options SCHED_4BSD # 4BSD scheduler options INET # InterNETworking options INET6 # IPv6 communications protocols 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 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_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 #options SCSI_DELAY=15000 # 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 device apic # I/O APIC # Bus support. Do not remove isa, even if you have no isa slots device isa 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 peripherals device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device pass # Passthrough device (direct SCSI access) 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 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 # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. #device pmtimer # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device ppi # Parallel port interface device #device vpo # Requires scbus and da device miibus # MII bus support device fxp # Intel EtherExpress PRO/100B (82557, 82558) device em device loop # Network loopback device mem # Memory and kernel memory devices device io # I/O device 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 bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # "Human Interface Devices" device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da # FireWire support device firewire # FireWire bus code #device sbp # SCSI over FireWire (Requires scbus and da) #device fwe # Ethernet over FireWire (non-standard!) options IPFIREWALL options IPFIREWALL_VERBOSE options IPFIREWALL_VERBOSE_LIMIT=10000 options IPFIREWALL_DEFAULT_TO_ACCEPT device snp device speaker options DDB options KDB options BREAK_TO_DEBUGGER options INVARIANT_SUPPORT options INVARIANTS options WITNESS options WITNESS_KDB options WITNESS_SKIPSPIN #options ADAPTIVE_GIANT # Giant mutex is adaptive. DMESG (the config which got locked): Copyright (c) 1992-2005 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 5.3-STABLE #3: Sun Jan 23 01:04:00 MSK 2005 matrix@omni2.itlegion.ru:/usr/obj/usr/src/sys/OMNI2 WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.66GHz (2665.93-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf25 Stepping = 5 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 4160225280 (3967 MB) avail memory = 4077486080 (3888 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 6 cpu3 (AP): APIC ID: 7 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard ioapic3 irqs 72-95 on motherboard ioapic4 irqs 96-119 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.1 (no driver attached) pcib1: at device 2.0 on pci0 pci1: on pcib1 pci1: at device 28.0 (no driver attached) pcib2: at device 29.0 on pci1 pci2: on pcib2 pci1: at device 30.0 (no driver attached) pcib3: at device 31.0 on pci1 pci3: on pcib3 em0: port 0x3000-0x303f mem 0xfc200000-0xfc21ffff irq 28 at device 2 .0 on pci3 em0: Ethernet address: 00:30:48:2a:2d:bc em0: Speed:N/A Duplex:N/A em1: port 0x3040-0x307f mem 0xfc220000-0xfc23ffff irq 29 at device 2 .1 on pci3 em1: Ethernet address: 00:30:48:2a:2d:bd em1: Speed:N/A Duplex:N/A pcib4: at device 3.0 on pci0 pci4: on pcib4 pci4: at device 28.0 (no driver attached) pcib5: at device 29.0 on pci4 pci5: on pcib5 pci4: at device 30.0 (no driver attached) pcib6: at device 31.0 on pci4 pci6: on pcib6 twe0: <3ware Storage Controller. Driver version 1.50.01.002> port 0x4000-0x400f mem 0xfc800000-0xfcffffff irq 72 at device 1. 0 on pci6 twe0: [GIANT-LOCKED] twe0: 4 ports, Firmware FE7S 1.05.00.063, BIOS BE7X 1.08.00.048 uhci0: port 0x2000-0x201f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x2020-0x203f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x2040-0x205f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pcib7: at device 30.0 on pci0 pci7: on pcib7 pci7: at device 1.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x2060-0x206f,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata2: channel #1 on atapci0 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 speaker0: port 0x61 on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 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 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 orm0: at iomem 0xe0000-0xe3fff,0xc9000-0xc9fff,0xc8000-0xc8fff,0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 10.000 msec ipfw2 initialized, divert disabled, rule-based forwarding disabled, default to accept, logging limited to 10000 packets/entry by default acd0: CDRW at ata0-slave UDMA33 twed0: on twe0 twed0: 343417MB (703318656 sectors) SMP: AP CPU #2 Launched! SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! Mounting root from ufs:/dev/twed0s1a em0: Link is up 100 Mbps Full Duplex From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 13:49:09 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 659B216A4CF for ; Mon, 24 Jan 2005 13:49:09 +0000 (GMT) Received: from mailhub.sweetdreamsracing.biz (mailhub.sweetdreamsracing.biz [66.92.171.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11F0F43D46 for ; Mon, 24 Jan 2005 13:49:09 +0000 (GMT) (envelope-from culverk@sweetdreamsracing.biz) Received: by mailhub.sweetdreamsracing.biz (Postfix, from userid 80) id 6444061C8; Mon, 24 Jan 2005 08:48:58 -0500 (EST) Received: from hachigo.sweetdreamsracing.biz (hachigo.sweetdreamsracing.biz [66.92.171.91]) by www.sweetdreamsracing.biz (Horde) with HTTP for ; Mon, 24 Jan 2005 08:48:58 -0500 Message-ID: <20050124084858.9rdtie0wsg8o4css@www.sweetdreamsracing.biz> Date: Mon, 24 Jan 2005 08:48:58 -0500 From: Kenneth Culver To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs Subject: problem with ugen and canon camera (panic) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 13:49:09 -0000 Hi, Recently (within the last 2 weeks or so) something was committed which messed up my ability to grab pics off my canon PowerShot S200. I type "gphoto2 --auto-detect --get-all-files" on the commandline, and the following (roughly, since it's from memory) message pops up: WARNING: device_destroy called on 231/1 Panic: don't do that And then of course the machine panics. When I get a chance I'm going to try to pinpoint which commit caused this to start happening, but I thought I'd report the problem first anyway. Thanks. Ken From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 14:08:41 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D7AD16A4CE for ; Mon, 24 Jan 2005 14:08:41 +0000 (GMT) Received: from smtp4.wanadoo.fr (smtp4.wanadoo.fr [193.252.22.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3BB143D5A for ; Mon, 24 Jan 2005 14:08:40 +0000 (GMT) (envelope-from saut.olivier@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0408.wanadoo.fr (SMTP Server) with ESMTP id 981211C00190; Mon, 24 Jan 2005 15:08:39 +0100 (CET) Received: from banquo.homeip.net (AToulouse-152-1-56-100.w82-125.abo.wanadoo.fr [82.125.143.100]) by mwinf0408.wanadoo.fr (SMTP Server) with ESMTP id 683991C00101; Mon, 24 Jan 2005 15:08:39 +0100 (CET) X-ME-UUID: 20050124140839427.683991C00101@mwinf0408.wanadoo.fr Received: by banquo.homeip.net (Postfix, from userid 1001) id 7CC77D4; Mon, 24 Jan 2005 15:08:39 +0100 (CET) Date: Mon, 24 Jan 2005 15:08:39 +0100 From: Olivier Saut To: Kenneth Culver Message-ID: <20050124140839.GA7128@banquo.homeip.net> References: <20050124084858.9rdtie0wsg8o4css@www.sweetdreamsracing.biz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050124084858.9rdtie0wsg8o4css@www.sweetdreamsracing.biz> User-Agent: Mutt/1.4.2.1i cc: freebsd-stable@freebsd.org Subject: Re: problem with ugen and canon camera (panic) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: saut@mip.ups-tlse.fr List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 14:08:41 -0000 On Mon, 24 Jan 2005, Kenneth Culver wrote: > Hi, > Recently (within the last 2 weeks or so) something was committed which > messed up my ability to grab pics off my canon PowerShot S200. I type "gphoto2 > --auto-detect --get-all-files" on the commandline, and the following (roughly, > since it's from memory) message pops up: > > WARNING: device_destroy called on 231/1 > Panic: don't do that > I think this has been fixed. See http://www.freebsd.org/cgi/query-pr.cgi?pr=76240 and http://lists.freebsd.org/pipermail/cvs-src/2005-January/039069.html julian 2005-01-23 06:48:06 UTC FreeBSD src repository Modified files: (Branch: RELENG_5) sys/dev/usb ugen.c Log: MFC to bring in line with -current version PR: usb/76240 Submitted by: Claude Buisson Revision Changes Path 1.88.2.3 +106 -41 src/sys/dev/usb/ugen.c You should cvsup again to see if it solves your problem. Hope this helps, - Olivier From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 16:07:00 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97C9516A4CE for ; Mon, 24 Jan 2005 16:07:00 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 81B9F43D3F for ; Mon, 24 Jan 2005 16:06:59 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail invoked by alias); 24 Jan 2005 16:06:57 -0000 Received: from pD955F3D7.dip.t-dialin.net (EHLO lofi.dyndns.org) (217.85.243.215) by mail.gmx.net (mp002) with SMTP; 24 Jan 2005 17:06:57 +0100 X-Authenticated: #443188 Received: from [192.168.8.4] (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id j0OG6rqr068210 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Jan 2005 17:06:54 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) Message-ID: <41F51D1C.3030400@gmx.net> Date: Mon, 24 Jan 2005 17:06:52 +0100 From: Michael Nottebrock User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en, de-de MIME-Version: 1.0 To: Rostislav Krasny References: <20050124112207.2442.qmail@web14824.mail.yahoo.com> In-Reply-To: <20050124112207.2442.qmail@web14824.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new X-Y-GMX-Trusted: 0 cc: freebsd-stable@freebsd.org Subject: Re: sometimes 5.3-RELEASE-p5 is stuck at the last steps of shutdown X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 16:07:00 -0000 Rostislav Krasny wrote: > Hello all. > > I use FreeBSD 5.3-RELEASE-p5 on i386. Sometimes my system is stuck at the > last steps of shutdown. Following quoting is what I saw yesterday when my > system was stuck again (the last lines): > > init: some processes would not die; ps axl advised You should try to find out what's causing that. I personally got this a few times, too, when a mount command got badly stuck because trouble with the hdd. -- ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 16:43:06 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F4C816A4CE for ; Mon, 24 Jan 2005 16:43:06 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8956F43D2D for ; Mon, 24 Jan 2005 16:43:05 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wproxy.gmail.com with SMTP id 58so264977wri for ; Mon, 24 Jan 2005 08:43:03 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=ILtLs9iSVOZLmi49XKTjdKEnJWaBHWP8RG/08Uj1DJPru39PRV2E31Cqp06I5N3QcjnCV32t+AVCuFmZPWWoxfnKFEOKonmotWi4B0RcAyOhUpGf1rHgz+WKt/IUTFAEF9s9F+4dAV/sNbtVGp4Mu4Ai6E7M+8Ah29GHe9hs2fA= Received: by 10.54.29.20 with SMTP id c20mr314227wrc; Mon, 24 Jan 2005 08:43:03 -0800 (PST) Received: by 10.54.29.48 with HTTP; Mon, 24 Jan 2005 08:43:03 -0800 (PST) Message-ID: <790a9fff05012408431642f384@mail.gmail.com> Date: Mon, 24 Jan 2005 10:43:03 -0600 From: Scot Hetzel To: Warren In-Reply-To: <200501232241.34900.shinjii@virusinfo.rdksupportinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200501232241.34900.shinjii@virusinfo.rdksupportinc.com> cc: freebsd-stable@freebsd.org Subject: Re: 5.3 prob reading 4.11 hdd X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Scot Hetzel List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 16:43:06 -0000 On Sun, 23 Jan 2005 22:41:34 +1000, Warren wrote: > I recently took my primary hdd running FreeBSD 4.11-STABLE out of my main > machine leaving my 2ndry hdd in the machine and installing FreeBSD5.3-STABLE > on it to use as the new primary. When everything was done and i plugged in > the 2nd hdd that originally had 4.11-STABLE on it, i was unable to find the > individual partitions/slices on there to mount so i could access all the old > data i had. I have a basic understanding of FreeBSD but am still not quite > proficent when it comes to this sort of thing. Fdisk only shows 1 partition > so does disklabel. Below is the disklabel output > of the drive im wanting to get all the data from... > > #ad1s1 > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > c: 234436482 0 unused 0 0 # "raw" part, don't > edit > e: 234436482 0 4.2BSD 2048 16384 89 > Do you have any files on ad1s1e? mount /dev/ad1s1e /mnt ls -lR /mnt Scot From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 18:29:38 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C14CE16A4CE for ; Mon, 24 Jan 2005 18:29:38 +0000 (GMT) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F96643D3F for ; Mon, 24 Jan 2005 18:29:38 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 273E7B831; Mon, 24 Jan 2005 13:29:38 -0500 (EST) In-Reply-To: <200501240911.31608.emanuel.strobl@gmx.net> References: <200501240911.31608.emanuel.strobl@gmx.net> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Mon, 24 Jan 2005 13:29:38 -0500 To: Emanuel Strobl X-Mailer: Apple Mail (2.619) cc: freebsd-stable@freebsd.org Subject: Re: watchdogd panic when shutdown -p X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 18:29:38 -0000 On Jan 24, 2005, at 3:11 AM, Emanuel Strobl wrote: > kernel will reset the machine. Best would be if I never see watchdog in > action but I'm seeing a panic message after some interrupt statistics > (see > below) and the machine doesn't power off (like it does without > watchdogd > enabled). > Interesting... Can you compare your experience with mine as described in PR 71800? http://www.freebsd.org/cgi/query-pr.cgi?pr=71800 I hadn't attributed this to the watchdog. I'll try that, but I have two boxes with watchdog enabled (FreeBSD 5.3 and 5.2.1) which don't exhibit any failure to shutdown, and I have two boxes with 5.3 that do exhibit (one ever since 5.3 BETA) the kernel IRQ messages on any type of shutdown. All have the watchdog on. Vivek Khera, Ph.D. +1-301-869-4449 x806 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 18:44:05 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8302D16A4CE for ; Mon, 24 Jan 2005 18:44:05 +0000 (GMT) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5111243D53 for ; Mon, 24 Jan 2005 18:44:05 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id C5EB4B87A for ; Mon, 24 Jan 2005 13:44:04 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <20050119004858.GA46389@xor.obsecurity.org> References: <6.2.0.14.0.20050112173437.089758a0@64.7.153.2> <20050113225145.GA781@galgenberg.net> <6.2.0.14.0.20050113193132.042966c8@64.7.153.2> <20050117193844.GB1110@galgenberg.net> <20050117224809.GC31463@xor.obsecurity.org> <6.2.0.14.0.20050117210539.08489c28@64.7.153.2> <41ECBED0.8000704@incubus.de> <3aaaa3a0501181530975fecf@mail.gmail.com> <20050119004858.GA46389@xor.obsecurity.org> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Mon, 24 Jan 2005 13:44:04 -0500 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.619) Subject: Re: CFLAGS=-O2 -pipe problems in RELENG_5 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 18:44:05 -0000 On Jan 18, 2005, at 7:48 PM, Kris Kennaway wrote: > Do yourself a favour and use -O2 -fno-strict-alias instead, because > some ports *are broken* with plain -O2. > I just tried this on a 5-STABLE dual opteron, and it complained about unknown option. I had to specify the full option -fno-strict-aliasing to make gcc recognize it. Now we'll see just how many things it breaks building world... :-) Vivek Khera, Ph.D. +1-301-869-4449 x806 From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 18:44:15 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1D4016A4D9 for ; Mon, 24 Jan 2005 18:44:15 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 8360443D5A for ; Mon, 24 Jan 2005 18:44:14 +0000 (GMT) (envelope-from emanuel.strobl@gmx.net) Received: (qmail invoked by alias); 24 Jan 2005 18:44:13 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp015) with SMTP; 24 Jan 2005 19:44:13 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-stable@freebsd.org Date: Mon, 24 Jan 2005 19:44:09 +0100 User-Agent: KMail/1.7.2 References: <200501240911.31608.emanuel.strobl@gmx.net> In-Reply-To: X-Birthday: 10/06/72 X-CelPhone: +49 173 9967781 X-Tel: +49 89 18947781 X-Country: Germany X-Address: Munich, 80686 X-OS: FreeBSD MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart33533785.W3HslYoBRf"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501241944.13307.emanuel.strobl@gmx.net> X-Y-GMX-Trusted: 0 cc: Vivek Khera cc: smkelly@FreeBSD.org Subject: Re: watchdogd panic when shutdown -p X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 18:44:15 -0000 --nextPart33533785.W3HslYoBRf Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Montag, 24. Januar 2005 19:29 schrieb Vivek Khera: > On Jan 24, 2005, at 3:11 AM, Emanuel Strobl wrote: > > kernel will reset the machine. Best would be if I never see watchdog in > > action but I'm seeing a panic message after some interrupt statistics > > (see > > below) and the machine doesn't power off (like it does without > > watchdogd > > enabled). > > Interesting... Can you compare your experience with mine as described > in PR 71800? Hmm, I don't have the problem when rebooting, just when shutting down with= =20 power off. I also have never seen any loop as you describe. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D71800 > > I hadn't attributed this to the watchdog. I'll try that, but I have > two boxes with watchdog enabled (FreeBSD 5.3 and 5.2.1) which don't > exhibit any failure to shutdown, and I have two boxes with 5.3 that do > exhibit (one ever since 5.3 BETA) the kernel IRQ messages on any type > of shutdown. All have the watchdog on. I think it's a ACPI interaction problem with watchdog, so depending on your= =20 motherborads ACPI implementation you see the error or not, but I'm complete= ly=20 new to SW_WATCHDOG so I can't tell much when and why these irq statistics a= re=20 generated. Maybe Sean Kelly can tell us how SW_WATCHDOG interacts with ACPI, since I=20 think the problem occurs when the kernel disables ACPI, right? (just my=20 "feeling") =2DHarry > > > Vivek Khera, Ph.D. > +1-301-869-4449 x806 > > _______________________________________________ > 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" --nextPart33533785.W3HslYoBRf Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB9UH9Bylq0S4AzzwRAvxNAJ9j+qG0QiaWjgj107UhRKjn/ZFeQQCfeHTN F7BBk1V7IgFzvA3EmmTmtsk= =3YKA -----END PGP SIGNATURE----- --nextPart33533785.W3HslYoBRf-- From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 18:55:27 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5204F16A4CE for ; Mon, 24 Jan 2005 18:55:27 +0000 (GMT) Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180]) by mx1.FreeBSD.org (Postfix) with ESMTP id 219AC43D48 for ; Mon, 24 Jan 2005 18:55:27 +0000 (GMT) (envelope-from vivek@khera.org) Received: from [192.168.7.103] (host-103.int.kcilink.com [192.168.7.103]) by yertle.kcilink.com (Postfix) with ESMTP id 6275EB831 for ; Mon, 24 Jan 2005 13:55:26 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <200501241944.13307.emanuel.strobl@gmx.net> References: <200501240911.31608.emanuel.strobl@gmx.net> <200501241944.13307.emanuel.strobl@gmx.net> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <826E7D69-6E39-11D9-802F-000A9578CFCC@khera.org> Content-Transfer-Encoding: 7bit From: Vivek Khera Date: Mon, 24 Jan 2005 13:55:26 -0500 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.619) Subject: Re: watchdogd panic when shutdown -p X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 18:55:27 -0000 On Jan 24, 2005, at 1:44 PM, Emanuel Strobl wrote: > Maybe Sean Kelly can tell us how SW_WATCHDOG interacts with ACPI, > since I > think the problem occurs when the kernel disables ACPI, right? (just my > "feeling") > Next chance I get I'll play with the SW_WATCHDOG and see if that stops the problem on my boxes. Out of sheer luck, the two that have the problem are at my office, and the two that do not are at my co-lo. None of the dozen 4.x boxes ever fail to reboot at the co-lo, either, the once or twice a year I upgrade them. From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 19:29:34 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0CD316A4CE for ; Mon, 24 Jan 2005 19:29:34 +0000 (GMT) Received: from rader.servnow.com (rader.servnow.com [69.93.129.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B05443D1D for ; Mon, 24 Jan 2005 19:29:34 +0000 (GMT) (envelope-from mikes@siralan.org) Received: from 12-210-221-89.client.insightbb.com ([12.210.221.89] helo=familysquires.net) by rader.servnow.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.43) id 1Ct9tw-0004Ur-S7 for freebsd-stable@freebsd.org; Mon, 24 Jan 2005 14:29:29 -0500 Date: Mon, 24 Jan 2005 14:29:31 -0500 (EST) From: "Michael L. Squires" X-X-Sender: mikes@familysquires.net To: freebsd-stable@freebsd.org In-Reply-To: <826E7D69-6E39-11D9-802F-000A9578CFCC@khera.org> Message-ID: <20050124140403.C42212@familysquires.net> References: <200501240911.31608.emanuel.strobl@gmx.net> <200501241944.13307.emanuel.strobl@gmx.net> <826E7D69-6E39-11D9-802F-000A9578CFCC@khera.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - rader.servnow.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - siralan.org X-Source: X-Source-Args: X-Source-Dir: Subject: Starting gvinum/vinum with RAID 5 and Compaq 39160 - 5.3-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 19:29:34 -0000 I've been playing with vinum and gvinum with a RAID-1 boot setup (now abandoned, hardware RAID was $29 - SM P4DC6+ with Adaptec 2005S) and with a RAID5 array using a Compaq version of the Adaptec 39160 card. I've found that only "geom_vinum_load="YES" works in order to get the RAID 5 array mounted at boot time; "vinum_load" with or without "vinum.autostart" doesn't work. (Doesn't work means that the boot fails when /dev/vinum/raid can't be mounted as per /etc/fstab, and I have to execute "vinum" before I can mount it while running single user after the crash). I've seen one other message that "vinum_load" didn't work for one other 5.3-R user, but I don't know if we both made the same mistake or if something else is wrong. (The Compaq card won't configure on my system; I found that I could flash it using the v2.57 Adaptec BIOS update and after that I could set the bus speed and turn off the BIOS (otherwise the disks are all attached "async" and the system tries to boot off the 39160). Adaptec warns of dire consequences, and the flash does not remove the identification of the card as a Compaq OEM version, but I haven't had problems after the BIOS update). Mike Squires From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 19:38:28 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D8E816A4CE for ; Mon, 24 Jan 2005 19:38:28 +0000 (GMT) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.49.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1AEA43D1D for ; Mon, 24 Jan 2005 19:38:27 +0000 (GMT) (envelope-from paul@gromit.dlib.vt.edu) Received: from zappa.Chelsea-Ct.Org (pool-151-199-113-125.roa.east.verizon.net [151.199.113.125]) by gromit.dlib.vt.edu (8.13.1/8.13.1) with ESMTP id j0OJcQmf022673 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 24 Jan 2005 14:38:27 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) Received: from zappa.Chelsea-Ct.Org (localhost.Chelsea-Ct.Org [127.0.0.1]) by zappa.Chelsea-Ct.Org (8.13.1/8.13.1) with ESMTP id j0OJcLJY065379 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 24 Jan 2005 14:38:21 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) Received: (from paul@localhost) by zappa.Chelsea-Ct.Org (8.13.1/8.13.1/Submit) id j0OJcKfg065378; Mon, 24 Jan 2005 14:38:20 -0500 (EST) (envelope-from paul@gromit.dlib.vt.edu) X-Authentication-Warning: zappa.Chelsea-Ct.Org: paul set sender to paul@gromit.dlib.vt.edu using -f From: Paul Mather To: "Michael L. Squires" In-Reply-To: <20050124140403.C42212@familysquires.net> References: <200501240911.31608.emanuel.strobl@gmx.net> <200501241944.13307.emanuel.strobl@gmx.net> <826E7D69-6E39-11D9-802F-000A9578CFCC@khera.org> <20050124140403.C42212@familysquires.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Mon, 24 Jan 2005 14:38:20 -0500 Message-Id: <1106595500.65280.5.camel@zappa.Chelsea-Ct.Org> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port cc: freebsd-stable@freebsd.org Subject: Re: Starting gvinum/vinum with RAID 5 and Compaq 39160 - 5.3-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 19:38:28 -0000 On Mon, 2005-01-24 at 14:29 -0500, Michael L. Squires wrote: > I've been playing with vinum and gvinum with a RAID-1 boot setup (now > abandoned, hardware RAID was $29 - SM P4DC6+ with Adaptec 2005S) and with > a RAID5 array using a Compaq version of the Adaptec 39160 card. > > I've found that only "geom_vinum_load="YES" works in order to get the RAID > 5 array mounted at boot time; "vinum_load" with or without > "vinum.autostart" doesn't work. (Doesn't work means that the boot fails > when /dev/vinum/raid can't be mounted as per /etc/fstab, and I have to > execute "vinum" before I can mount it while running single user after the > crash). > > I've seen one other message that "vinum_load" didn't work for one other > 5.3-R user, but I don't know if we both made the same mistake or if > something else is wrong. For 5.3-STABLE you should be using geom_vinum. That means having 'geom_vinum_load="YES"' in /boot/loader.conf; /dev/gvinum/raid... in /etc/fstab (in your case); and using gvinum for userland control, not vinum. The vinum /etc/rc.conf knobs are not applicable to geom_vinum. Mixing vinum and gvinum is not recommended. If you just want a RAID-1 boot setup, you might consider geom_mirror instead. Cheers, Paul. -- e-mail: paul@gromit.dlib.vt.edu "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." --- Frank Vincent Zappa From owner-freebsd-stable@FreeBSD.ORG Mon Jan 24 21:16:50 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3190316A4CE for ; Mon, 24 Jan 2005 21:16:50 +0000 (GMT) Received: from mail.iinet.net.au (mail-05.iinet.net.au [203.59.3.37]) by mx1.FreeBSD.org (Postfix) with SMTP id 295DD43D54 for ; Mon, 24 Jan 2005 21:16:47 +0000 (GMT) (envelope-from shinjii@virusinfo.rdksupportinc.com) Received: (qmail 14497 invoked from network); 24 Jan 2005 21:16:46 -0000 Received: from unknown (HELO ?10.100.6.10?) (203.206.228.43) by mail.iinet.net.au with SMTP; 24 Jan 2005 21:16:45 -0000 From: Warren To: Scot Hetzel Date: Tue, 25 Jan 2005 07:15:16 +1000 User-Agent: KMail/1.7.2 References: <200501232241.34900.shinjii@virusinfo.rdksupportinc.com> <790a9fff05012408431642f384@mail.gmail.com> In-Reply-To: <790a9fff05012408431642f384@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501250715.17029.shinjii@virusinfo.rdksupportinc.com> cc: freebsd-stable@freebsd.org Subject: Re: 5.3 prob reading 4.11 hdd X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jan 2005 21:16:50 -0000 > Do you have any files on ad1s1e? > > mount /dev/ad1s1e /mnt > ls -lR /mnt > > Scot no, there arent any files there. -- Yours Sincerely Shinjii http://www.shinji.nq.nu From owner-freebsd-stable@FreeBSD.ORG Tue Jan 25 06:57:57 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B27A16A4CE for ; Tue, 25 Jan 2005 06:57:57 +0000 (GMT) Received: from mx1.mail.bg (mx1.mail.bg [193.201.172.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15A5243D5A for ; Tue, 25 Jan 2005 06:57:56 +0000 (GMT) (envelope-from ianchov@mail.bg) Received: from localhost (web1.mail.bg [193.201.172.98]) by mx1.mail.bg (Postfix) with ESMTP id E6C9442588 for ; Tue, 25 Jan 2005 08:57:43 +0200 (EET) Received: from 213-240-218-145.1699773.ddns.cablebg.netmail.bg (mail.bG Webmail 4.0.1) with HTTP for ; Tue, 25 Jan 2005 08:57:43 +0200 Message-ID: <1106636263.6fc262c4691ed@mail.bg> Date: Tue, 25 Jan 2005 08:57:43 +0200 From: ianchov@mail.bg To: freebsd-stable@freebsd.org References: <20050123122220.GF253@acheron.in.hades> In-Reply-To: <20050123122220.GF253@acheron.in.hades> MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1251" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: mail.bG Webmail 4.0-cvs X-Originating-IP: 213.240.218.145 Subject: Re: loader.conf examples X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 06:57:57 -0000 >>> ----- =CF=E8=F1=EC=EE =EE=F2 msh@blisses.org --------- >>> =C4=E0=F2=E0: Sun, 23 Jan 2005 07:22:20 -0500 >>> =CF=EE=E4=E0=F2=E5=EB: Matt Herzog >>> =CE=F2=E3=EE=E2=EE=F0-=C4=EE:Matt Herzog >>> =CE=F2=ED=EE=F1=ED=EE: loader.conf examples >>> =CF=EE=EB=F3=F7=E0=F2=E5=EB:freebsd-stable@freebsd.org >>> >>> Can anyone point me to a loader.conf file that's full of a wide >>> range of options? I just want to see some syntax for stuff like >>> video hardware acceleration, audio chipset support etc. >>> >>> I'm confused about how and why modules are built and (seemingly >>> loaded without my having specified any to load) when I have not >>> told my kernel conf file to build anything as a module. As a former >>> NetBSD user, I had expected a monolitic kernel . . . >>> _______________________________________________ >>> 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= " >>> >>> >>> ----- =CA=F0=E0=E9 =ED=E0 =EF=E8=F1=EC=EE=F2=EE =EE=F2 msh@blisses.org -= ---- did you see /boot/defaults/loader.conf ----------------------------- http://www.atol.bg - =CD=E0=EC=E5=F0=E8 =E1=E8=E2=F8=E8=F2=E5 =F1=E8 =F1=FA= =F3=F7=E5=ED=E8=F6=E8 =E8 =F1=F2=E0=F0=E8 =EF=F0=E8=FF=F2=E5=EB=E8! From owner-freebsd-stable@FreeBSD.ORG Tue Jan 25 07:52:08 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BB3816A4CF for ; Tue, 25 Jan 2005 07:52:08 +0000 (GMT) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8847643D41 for ; Tue, 25 Jan 2005 07:52:05 +0000 (GMT) (envelope-from parv@pair.com) Received: from default.chvlva.adelphia.net ([69.160.74.226]) by mta13.adelphia.netESMTP <20050125065243.QPSH14597.mta13.adelphia.net@default.chvlva.adelphia.net>; Tue, 25 Jan 2005 01:52:43 -0500 Received: by default.chvlva.adelphia.net (Postfix, from userid 1000) id B29DDB4FC; Tue, 25 Jan 2005 01:52:49 -0500 (EST) Date: Tue, 25 Jan 2005 01:52:49 -0500 From: Parv To: Rostislav Krasny Message-ID: <20050125065249.GB807@holestein.holy.cow> Mail-Followup-To: Rostislav Krasny , freebsd-stable@freebsd.org References: <20050124112207.2442.qmail@web14824.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050124112207.2442.qmail@web14824.mail.yahoo.com> cc: freebsd-stable@freebsd.org Subject: Re: sometimes 5.3-RELEASE-p5 is stuck at the last steps of shutdown X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 07:52:08 -0000 in message <20050124112207.2442.qmail@web14824.mail.yahoo.com>, wrote Rostislav Krasny thusly... > > I use FreeBSD 5.3-RELEASE-p5 on i386. Sometimes my system is stuck > at the last steps of shutdown. Following quoting is what I saw > yesterday when my system was stuck again (the last lines): > > init: some processes would not die; ps axl advised I did not have seen or notice this message. > Waiting (max 60 seconds) for system process `vnlru' to stop... done > Waiting (max 60 seconds) for system process `bufdaemon' to stop... done > Waiting (max 60 seconds) for system process `syncer' to stop... > Syncing disks, vnodes remaining... 2 1 0 0 0 done > No buffers busy after final sync I am using the same version as above on IBM ThinkPad T42 (2373-5TU). Before i removed the, well, removable CD/DVD drive, system would either turn off the power or bring up "System halted ... Press a key to reboot or turn off power" like message, depending upon the command issued (apm or acpi). After removing the CD/DVD drive (while the computer was turned off), system refused to shutdown (or bring up the message "System halted ..."), or to respond to Ctrl-Alt-Esc or Ctrl-Alt-Del keys. It just stuck at the above mentioned message, "No buffers busy ...". I tried 2-3 times, w/ acpi only, both in console and X. (I did not see anything interesting in the logs later.) (Yes, after reinserting the drive, system halts/shuts down as expected.) - Parv -- From owner-freebsd-stable@FreeBSD.ORG Tue Jan 25 09:08:11 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DF5216A4DF for ; Tue, 25 Jan 2005 09:08:11 +0000 (GMT) Received: from shaolin.comnet.co.nz (shaolin.comnet.co.nz [131.203.96.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5E2943D2D for ; Tue, 25 Jan 2005 09:08:10 +0000 (GMT) (envelope-from r.mahoney@comnet.net.nz) Received: from 131-203-240-72.remote.comnet.co.nz (131-203-240-72.remote.comnet.co.nz [131.203.240.72]) id j0P986ZW031946; Tue, 25 Jan 2005 22:08:07 +1300 From: Richard MAHONEY To: FreeBSD Stable Content-Type: text/plain Date: Tue, 25 Jan 2005 22:08:15 +1300 Message-Id: <1106644095.8792.14.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Need presompiled binaries of Sablotron 0.90 and 0.95 for Index Data's Keystone DLS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: r.mahoney@comnet.net.nz List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 09:08:11 -0000 Dear All, I'm trying to implement a digital portal using Index Data's Keystone Digital Library Suite ( http://www.indexdata.dk/keystone/ ). Unfortunately Keystone doesn't run well with the latest port of Sablotron (1.0.1). Sablot-0.98 has problems as well: http://www.indexdata.dk/keystone/doc/xslt.tkl This has been discussed on the Keystone mailing list ( http://www.indexdata.dk/mailman/listinfo/tkl ) but the issue has not been resolved. As a last resort, I've tried to compile 0.90 and 0.95 on 5.3 Stable but without success. I've also been unable to locate precompiled binaries of either. Does any one have access to precompiled versions. Apparently Sablotron 0.90 and 0.95 both work without issue. Best regards, Richard Mahoney -- Richard MAHONEY | www: homepages.comnet.net.nz/~r-mahoney Littledene | phone/fax (man.): +64 3 312 1699 Bay Road | cell: +64 25 829 986 OXFORD, NZ | email: r.mahoney@comnet.net.nz From owner-freebsd-stable@FreeBSD.ORG Tue Jan 25 17:13:56 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A156E16A4CE for ; Tue, 25 Jan 2005 17:13:56 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B28643D2D for ; Tue, 25 Jan 2005 17:13:56 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wproxy.gmail.com with SMTP id 58so425383wri for ; Tue, 25 Jan 2005 09:13:54 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=U9PN0g4FEBh6vKdZWllsX7GtmjboHAUH4A0y3HV0/EWcw5hLgMSqDXOxL2ni3XqdPsGtw2Fpjw2XVGAfZVdJ7yuiMFaOgk0eu6l1x0lwVeMy/cVVUtpIl2Iho8H/ct1QwX2IWKHyuLU65jfDhQ3Idg3rnTK85Et7UVuivXDhDlg= Received: by 10.54.48.14 with SMTP id v14mr184979wrv; Tue, 25 Jan 2005 09:13:53 -0800 (PST) Received: by 10.54.29.48 with HTTP; Tue, 25 Jan 2005 09:13:53 -0800 (PST) Message-ID: <790a9fff05012509136ea58eba@mail.gmail.com> Date: Tue, 25 Jan 2005 11:13:53 -0600 From: Scot Hetzel To: Warren In-Reply-To: <200501250715.17029.shinjii@virusinfo.rdksupportinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200501232241.34900.shinjii@virusinfo.rdksupportinc.com> <790a9fff05012408431642f384@mail.gmail.com> <200501250715.17029.shinjii@virusinfo.rdksupportinc.com> cc: freebsd-stable@freebsd.org Subject: Re: 5.3 prob reading 4.11 hdd X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Scot Hetzel List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 17:13:56 -0000 On Tue, 25 Jan 2005 07:15:16 +1000, Warren wrote: > > Do you have any files on ad1s1e? > > > > mount /dev/ad1s1e /mnt > > ls -lR /mnt > > > > Scot > > no, there arent any files there. Looks like you actually installed 5.3 on your 4.11 drive instead of your spare drive. Unless you had recently disklabeled ad1s1. Scot From owner-freebsd-stable@FreeBSD.ORG Tue Jan 25 17:25:55 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B190316A4CE for ; Tue, 25 Jan 2005 17:25:55 +0000 (GMT) Received: from rader.servnow.com (rader.servnow.com [69.93.129.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D97D43D45 for ; Tue, 25 Jan 2005 17:25:55 +0000 (GMT) (envelope-from mikes@siralan.org) Received: from 12-210-221-89.client.insightbb.com ([12.210.221.89] helo=familysquires.net) by rader.servnow.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.43) id 1CtURr-0001Rw-HW for freebsd-stable@freebsd.org; Tue, 25 Jan 2005 12:25:51 -0500 Date: Tue, 25 Jan 2005 12:25:50 -0500 (EST) From: "Michael L. Squires" X-X-Sender: mikes@familysquires.net To: freebsd-stable@freebsd.org Message-ID: <20050125120751.K46900@familysquires.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - rader.servnow.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - siralan.org X-Source: X-Source-Args: X-Source-Dir: Subject: Possible 5.3-STABLE tar bug X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 17:25:55 -0000 I have an NFS exported directory "/share" which contains "/share/Mac"; the "Mac" directory is itself exported vi netatalk, and contains several GB of Macintosh files. If I execute tar cf /dev/null Mac when "/share" is my current directory on the 4.10 box nothing happens, other than consuming a lot of machine cycles. On a 5.3-STABLE box, where the /share directory is NFS-mounted, when I execute tar cvf /dev/null Mac when /share is my current directory I get p4dc6# tar cf /dev/null Mac archive_write_pax_header: 'x' header failed?! This can't happen. p4dc6# This is reproducible, and happens after a specific file in an Apple network software installation directory. There is nothing in /var/log/messages. A Google search found only a reference to one message in the "perforce" FreeBSD mailing list (change 66084) which appears to show that this error message was added on 11/30/2004. dmesg header is (there are two physical CPUs, the kernel is SMP): FreeBSD 5.3-STABLE #0: Sun Jan 23 21:24:20 EST 2005 root@p4dc6.familysquires.net:/usr/obj/usr/src/sys/XEON Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) XEON(TM) CPU 1.80GHz (1784.28-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf24 Stepping = 4 Features=0x3febfbff Hyperthreading: 2 logical CPUs I can provide additional information, assuming that this is something as yet uncorrected. Mike Squires From owner-freebsd-stable@FreeBSD.ORG Tue Jan 25 17:38:57 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 725A516A4CE for ; Tue, 25 Jan 2005 17:38:57 +0000 (GMT) Received: from bloom.cse.buffalo.edu (bloom.cse.Buffalo.EDU [128.205.32.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id D958143D39 for ; Tue, 25 Jan 2005 17:38:56 +0000 (GMT) (envelope-from kensmith@FreeBSD.org) Received: from bloom.cse.buffalo.edu (localhost.cse.buffalo.edu [127.0.0.1]) by bloom.cse.buffalo.edu (8.13.1/8.12.4) with ESMTP id j0PHcuPR050148 for ; Tue, 25 Jan 2005 12:38:56 -0500 (EST) Received: (from kensmith@localhost) by bloom.cse.buffalo.edu (8.13.1/8.13.1/Submit) id j0PHcuO6050147 for freebsd-stable@freebsd.org; Tue, 25 Jan 2005 12:38:56 -0500 (EST) (envelope-from kensmith) Date: Tue, 25 Jan 2005 12:38:56 -0500 From: Ken Smith To: freebsd-stable@freebsd.org Message-ID: <20050125173856.GB50042@bloom.cse.buffalo.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TRYliJ5NKNqkz5bu" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: FreeBSD 4.11-RELEASE is now available X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 17:38:57 -0000 --TRYliJ5NKNqkz5bu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline The Release Engineering Team is happy to announce the availability of FreeBSD 4.11-RELEASE, the latest release of the FreeBSD Legacy development branch. Since FreeBSD 4.10-RELEASE in May 2004 we have made conservative updates to a number of software programs in the base system, dealt with known security issues, and made many bugfixes. For a complete list of new features, known problems, and late-breaking news, please see the release notes and errata list, available here: http://www.FreeBSD.org/releases/4.11R/relnotes.html http://www.FreeBSD.org/releases/4.11R/errata.html FreeBSD 4.11 will become an "Errata Branch". In addition to Security fixes other well-tested fixes to basic functionality will be committed to the RELENG_4_11 branch after the release. Both Security Advisories and Errata Notices are announced on the freebsd-announce@freebsd.org mailing list. This is expected to be the last release from the RELENG_4 branch. Most of the Developers are now focused on the RELENG_5 branch, or on the cutting edge development in HEAD. For more information about FreeBSD release engineering activities, please see: http://www.FreeBSD.org/releng/ Availability ------------ FreeBSD 4.11-RELEASE supports the i386 and alpha architectures and can be installed directly over the net, using bootable media, or copied to a local NFS/FTP server. Distributions for both architectures are available now. Please continue to support the FreeBSD Project by purchasing media from one of our supporting vendors. The following companies will be offering FreeBSD 4.11 based products: FreeBSD Mall, Inc. http://www.freebsdmall.com/ Daemonnews, Inc. http://www.bsdmall.com/freebsd1.html If you can not afford FreeBSD on media, are impatient, or just want to use it for evangelism purposes, then by all means download the ISO images. We can not promise that all the mirror sites will carry the larger ISO images. At the time of this announcement they are available from the following sites. MD5 checksums for the release images are included at the bottom of this message. Bittorrent ---------- As with the 5.3 release we are experimenting with Bittorrent. A collection of trackers for the release ISO images is available at http://people.freebsd.org/~kensmith/4.11-torrent/ FTP --- ftp://ftp.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.FreeBSD.org/pub/FreeBSD/ ftp://ftp3.FreeBSD.org/pub/FreeBSD/ ftp://ftp5.FreeBSD.org/pub/FreeBSD/ ftp://ftp11.FreeBSD.org/pub/FreeBSD/ ftp://ftp.at.FreeBSD.org/pub/FreeBSD/ ftp://ftp.au.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.ca.FreeBSD.org/ ftp://ftp2.ch.FreeBSD.org/pub/FreeBSD/ ftp://ftp.cz.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.de.FreeBSD.org/pub/FreeBSD/ ftp://ftp.ee.FreeBSD.org/pub/FreeBSD/ ftp://ftp.es.FreeBSD.org/pub/FreeBSD/ ftp://ftp.fi.FreeBSD.org/pub/FreeBSD/ ftp://ftp.fr.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.ie.FreeBSD.org/pub/FreeBSD/ ftp://ftp.is.FreeBSD.org/pub/FreeBSD/ ftp://ftp.jp.FreeBSD.org/pub/FreeBSD/ ftp://ftp8.jp.FreeBSD.org/pub/FreeBSD/ ftp://ftp.kr.FreeBSD.org/pub/FreeBSD/ ftp://ftp.lt.FreeBSD.org/pub/FreeBSD/ ftp://ftp.nl.FreeBSD.org/pub/FreeBSD/ ftp://ftp.no.FreeBSD.org/pub/FreeBSD/ ftp://ftp5.pl.FreeBSD.org/pub/FreeBSD/ ftp://ftp3.ru.FreeBSD.org/pub/FreeBSD/ ftp://ftp.se.FreeBSD.org/pub/FreeBSD/ ftp://ftp.sg.FreeBSD.org/pub/FreeBSD/ ftp://ftp.si.FreeBSD.org/pub/FreeBSD/ ftp://ftp.sk.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.tw.FreeBSD.org/pub/FreeBSD/ ftp://ftp6.tw.FreeBSD.org/pub/FreeBSD/ ftp://ftp.uk.FreeBSD.org/pub/FreeBSD/ ftp://ftp6.us.FreeBSD.org/pub/FreeBSD/ ftp://ftp10.us.FreeBSD.org/pub/FreeBSD/ FreeBSD is also available via anonymous FTP from mirror sites in the following countries and territories: Argentina, Australia, Austria, Brazil, Canada, China, Croatia, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hong Kong, Hungary, Iceland, Indonesia, Ireland, Italy, Japan, Korea, Lithuania, Netherlands, New Zealand, Norway, Poland, Portugal, Romania, Russia, Saudi Arabia, Singapore, Slovak Republic, Slovenia, South Africa, Spain, Sweden, Switzerland, Taiwan, Turkey, Ukraine, United Kingdom, and the United States. Before trying the central FTP site, please check your regional mirror(s) first by going to: ftp://ftp..FreeBSD.org/pub/FreeBSD Any additional mirror sites will be labeled ftp2, ftp3 and so on. More information about FreeBSD mirror sites and the current list of all active mirror sites can be found at: http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html For instructions on installing FreeBSD, please see Chapter 2 of The FreeBSD Handbook. It provides a complete installation walk-through for users new to FreeBSD, and can be found online at: http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html Acknowledgments --------------- The FreeBSD Developers deserve the most thanks. Without their efforts FreeBSD would not exist. Many companies donated equipment, network access, or man-hours to finance the release engineering activities for FreeBSD 4.11 including The FreeBSD Mall, Hewlett Packard, Yahoo!, Sentex Communications, and NTT/Verio. The release engineering team for 4.11-RELEASE includes: Scott Long Release Engineering Robert Watson Release Engineering, Security John Baldwin Release Engineering Ken Smith Release Engineering, I386 Release Building, Mirror Site Coordination Hiroki Sato Release Engineering, Documentation Wilko Bulte Alpha Release Building Kris Kennaway Package Building Joe Marcus Clarke Package Building Jacques A. Vidrine Security Officer Paul Saab Bittorrent Coordination A few people put in more than their fair share of last-minute work. This includes Alexander Leidinger who did a lot of work on the linux_base-8 package integration, and Kris Kennaway who did a lot of package rebuilding thanks to a few recent security issues in some key packages. CD Image Checksums ------------------ For Alpha: MD5 (4.11-RELEASE-alpha-disc1-gnome.iso) = 3f0f49a9c7067f398ca0b47fd21234eb MD5 (4.11-RELEASE-alpha-disc1-kde.iso) = b4c83df8e979741c7972f379154360aa MD5 (4.11-RELEASE-alpha-disc2.iso) = 8fd241bab99fed226ef71184ed0b0b38 MD5 (4.11-RELEASE-alpha-miniinst.iso) = 3280b9e34fd26db7ce0dd24f1a05e7b4 For i386: MD5 (4.11-RELEASE-i386-disc1-gnome.iso) = 80c6b06b83432efc6cbe1cff3ebd893f MD5 (4.11-RELEASE-i386-disc1-kde.iso) = 84921fe6b6b4bfd3f7011788985d34e2 MD5 (4.11-RELEASE-i386-disc2.iso) = 73553999f9f8e2e49222ba14e8ecbde5 MD5 (4.11-RELEASE-i386-miniinst.iso) = 28b006bcdf5df8b8b7e8f1831085cdae -ken --TRYliJ5NKNqkz5bu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB9oQv/G14VSmup/YRAmSXAKCRYReFE/0fPlfFVPP11aW/Uza/xwCfb20b rr5IsQvADAcl7u2//XxxT2A= =D/UQ -----END PGP SIGNATURE----- --TRYliJ5NKNqkz5bu-- From owner-freebsd-stable@FreeBSD.ORG Tue Jan 25 18:43:03 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C415B16A4CE for ; Tue, 25 Jan 2005 18:43:03 +0000 (GMT) Received: from smtp3.Stanford.EDU (smtp3.Stanford.EDU [171.67.16.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CDFD43D39 for ; Tue, 25 Jan 2005 18:43:03 +0000 (GMT) (envelope-from richw@richw.org) Received: from whodunit.richw.org (SW-90-716-276-1.Stanford.EDU [171.66.155.243]) by smtp3.Stanford.EDU (8.12.11/8.12.11) with ESMTP id j0PIh2Qg030257 for ; Tue, 25 Jan 2005 10:43:02 -0800 Received: from whodunit.richw.org (localhost [127.0.0.1]) by whodunit.richw.org (8.13.1/8.13.1) with ESMTP id j0PIh1nJ010129; Tue, 25 Jan 2005 10:43:01 -0800 (PST) (envelope-from richw@whodunit.richw.org) Received: (from richw@localhost) by whodunit.richw.org (8.13.1/8.13.1/Submit) id j0PIh1cf010128; Tue, 25 Jan 2005 10:43:01 -0800 (PST) (envelope-from richw) Date: Tue, 25 Jan 2005 10:43:01 -0800 (PST) From: Rich Wales To: freebsd-stable@freebsd.org Message-ID: <20050125180025.S04220.richw@whodunit.richw.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: NIC acting promiscuously -- how to fix? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 18:43:03 -0000 I'm running 5.3-RELEASE-p5 on a system that is functioning as a NAT router/firewall using "pf". It works just fine, but . . . . The external (Internet) network connection is giving me incoming traffic addressed to other users all over my neighborhood (not just the packets intended for me). The external NIC (an Accton MPX 5030/5038, handled via the "rl" driver) appears to be running promiscuously; it's accepting all these incoming packets, whether addressed to me or not. The flags shown for the NIC by the "ifconfig" command are: rl0: flags=8843 mtu 1500 Note that the PROMISC flag is =not= set, but the NIC seems to be acting in a promiscuous fashion nevertheless. Although my firewall (an old 800-MHz Athlon system) is able to handle this extra load, I'd really like to configure it so that the packets not intended for my site are silently dropped and never seen by FreeBSD at all. (Aside from simple neatness, I'm aware of the failings of the RealTek 8129/8139 and am hoping to reduce overhead by filtering out the extraneous traffic before the driver would see it.) Any suggestions as to what I should do? Or is what I'm asking simply impossible (and if so, why)? Thanks for any help. Rich Wales richw@richw.org http://www.richw.org From owner-freebsd-stable@FreeBSD.ORG Tue Jan 25 19:11:32 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67E1116A4CE for ; Tue, 25 Jan 2005 19:11:32 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED38243D2D for ; Tue, 25 Jan 2005 19:11:31 +0000 (GMT) (envelope-from fehwalker@gmail.com) Received: by wproxy.gmail.com with SMTP id 40so90798wri for ; Tue, 25 Jan 2005 11:11:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=sZc2vTh1OktFM+d2B12lgw84MJ9IffgqmiLKzw6uc+EqF+cqSl4iD6EUWm8uMgD2z82TAUwqGKMQmL7M9PK4KW7vyefcusRFSIspP03LjzdNgWc5Q8xGt2N7x8G6uczJSDnqDf9YQbroZq9kaapeI2PmFeeFfXEOneLghdQfNzs= Received: by 10.54.20.25 with SMTP id 25mr19247wrt; Tue, 25 Jan 2005 11:11:28 -0800 (PST) Received: by 10.54.19.52 with HTTP; Tue, 25 Jan 2005 11:11:28 -0800 (PST) Message-ID: <35de0c3005012511113be88ff3@mail.gmail.com> Date: Tue, 25 Jan 2005 14:11:28 -0500 From: Bryan Fullerton To: freebsd-stable@freebsd.org In-Reply-To: <20050125120751.K46900@familysquires.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050125120751.K46900@familysquires.net> Subject: Re: Possible 5.3-STABLE tar bug X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bryan Fullerton List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 19:11:32 -0000 On Tue, 25 Jan 2005 12:25:50 -0500 (EST), Michael L. Squires wrote: > p4dc6# tar cf /dev/null Mac > archive_write_pax_header: 'x' header failed?! This can't happen. > p4dc6# This appears to have been fixed, but not sure if it's MFC'ed yet. http://www.freebsd.org/cgi/query-pr.cgi?pr=74385 Bryan From owner-freebsd-stable@FreeBSD.ORG Tue Jan 25 19:13:56 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1153316A4CE for ; Tue, 25 Jan 2005 19:13:56 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAC8843D49 for ; Tue, 25 Jan 2005 19:13:55 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j0PJEkMm026953; Tue, 25 Jan 2005 11:14:46 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j0PJEklG026952; Tue, 25 Jan 2005 11:14:46 -0800 Date: Tue, 25 Jan 2005 11:14:46 -0800 From: Brooks Davis To: Rich Wales Message-ID: <20050125191446.GA26504@odin.ac.hmc.edu> References: <20050125180025.S04220.richw@whodunit.richw.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mP3DRpeJDSE+ciuQ" Content-Disposition: inline In-Reply-To: <20050125180025.S04220.richw@whodunit.richw.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-stable@freebsd.org Subject: Re: NIC acting promiscuously -- how to fix? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 19:13:56 -0000 --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 25, 2005 at 10:43:01AM -0800, Rich Wales wrote: > I'm running 5.3-RELEASE-p5 on a system that is functioning as a > NAT router/firewall using "pf". It works just fine, but . . . . >=20 > The external (Internet) network connection is giving me incoming > traffic addressed to other users all over my neighborhood (not > just the packets intended for me). The external NIC (an Accton > MPX 5030/5038, handled via the "rl" driver) appears to be running > promiscuously; it's accepting all these incoming packets, whether > addressed to me or not. >=20 > The flags shown for the NIC by the "ifconfig" command are: >=20 > rl0: flags=3D8843 mtu 1500 >=20 > Note that the PROMISC flag is =3Dnot=3D set, but the NIC seems to > be acting in a promiscuous fashion nevertheless. >=20 > Although my firewall (an old 800-MHz Athlon system) is able to > handle this extra load, I'd really like to configure it so that > the packets not intended for my site are silently dropped and > never seen by FreeBSD at all. (Aside from simple neatness, I'm > aware of the failings of the RealTek 8129/8139 and am hoping to > reduce overhead by filtering out the extraneous traffic before > the driver would see it.) >=20 > Any suggestions as to what I should do? Or is what I'm asking > simply impossible (and if so, why)? Thanks for any help. Without a dump of the traffic I can't really say what you're seeing, but on a broadcast network like Ethernet of any size containing windows machines, half a dozen packets per second of broadcast noise is pretty normal. Are the packets addressed to your MAC address, but to another non-broadcast IP? I can conceive of configurations bugs in emulated broadcast domains that could cause that. If so it's an interesting bug in your ISPs config. If not, you may have found a bug in your NICs driver or it's chipset/firmware. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --mP3DRpeJDSE+ciuQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFB9pqiXY6L6fI4GtQRAmnhAKCAM7YhA7bZqsnP7VdfNXSXHIswxACfdjud gBFB7KKVH19HnmsAuIg8r4A= =gasC -----END PGP SIGNATURE----- --mP3DRpeJDSE+ciuQ-- From owner-freebsd-stable@FreeBSD.ORG Tue Jan 25 20:05:59 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1206B16A4CE for ; Tue, 25 Jan 2005 20:05:59 +0000 (GMT) Received: from mailhub.sweetdreamsracing.biz (mailhub.sweetdreamsracing.biz [66.92.171.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6E2D43D53 for ; Tue, 25 Jan 2005 20:05:58 +0000 (GMT) (envelope-from culverk@sweetdreamsracing.biz) Received: by mailhub.sweetdreamsracing.biz (Postfix, from userid 80) id 065C561BA; Tue, 25 Jan 2005 15:05:39 -0500 (EST) Received: from 141.156.69.109 ([141.156.69.109]) by www.sweetdreamsracing.biz (Horde) with HTTP for ; Tue, 25 Jan 2005 15:05:38 -0500 Message-ID: <20050125150538.4j7ujd0miogwkoc4@www.sweetdreamsracing.biz> Date: Tue, 25 Jan 2005 15:05:38 -0500 From: Kenneth Culver To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs Subject: problem with ugen and canon camera (panic) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 20:05:59 -0000 Hi, Recently (within the last 2 weeks or so) something was committed which messed up my ability to grab pics off my canon PowerShot S200. I type "gphoto2 --auto-detect --get-all-files" on the commandline, and the following (roughly, since it's from memory) message pops up: WARNING: device_destroy called on 231/1 Panic: don't do that And then of course the machine panics. When I get a chance I'm going to try to pinpoint which commit caused this to start happening, but I thought I'd report the problem first anyway. Thanks. Ken From owner-freebsd-stable@FreeBSD.ORG Tue Jan 25 20:07:21 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E49716A4CE for ; Tue, 25 Jan 2005 20:07:21 +0000 (GMT) Received: from zoot.lafn.org (zoot.lafn.ORG [206.117.18.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC63743D45 for ; Tue, 25 Jan 2005 20:07:20 +0000 (GMT) (envelope-from bc979@lafn.org) Received: from [10.0.1.90] ([4.28.157.47]) (authenticated bits=0) by zoot.lafn.org (8.12.3p3/8.12.3) with ESMTP id j0PK6d5T001762 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Tue, 25 Jan 2005 12:07:20 -0800 (PST) (envelope-from bc979@lafn.org) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <20050125191446.GA26504@odin.ac.hmc.edu> References: <20050125180025.S04220.richw@whodunit.richw.org> <20050125191446.GA26504@odin.ac.hmc.edu> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Doug Hardie Date: Tue, 25 Jan 2005 12:07:19 -0800 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.619) X-Virus-Scanned: ClamAV 0.80/680/Sun Jan 23 15:16:15 2005 clamav-milter version 0.80j on zoot.lafn.org X-Virus-Status: Clean Subject: Re: NIC acting promiscuously -- how to fix? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 20:07:21 -0000 > On Tue, Jan 25, 2005 at 10:43:01AM -0800, Rich Wales wrote: >> I'm running 5.3-RELEASE-p5 on a system that is functioning as a >> NAT router/firewall using "pf". It works just fine, but . . . . >> >> The external (Internet) network connection is giving me incoming >> traffic addressed to other users all over my neighborhood (not >> just the packets intended for me). The external NIC (an Accton >> MPX 5030/5038, handled via the "rl" driver) appears to be running >> promiscuously; it's accepting all these incoming packets, whether >> addressed to me or not. How are you determining that? If you are using tcpdump without the -p then keep in mind it will put the interface into promiscous mode and you will see everything on the network regardless of who its addressed to. To verify what your interface is accepting use: tcpdump -pei rl0 That will show the packets that it accepts including the ethernet headers. Those headers should all have your MAC address in them (send or receive). From owner-freebsd-stable@FreeBSD.ORG Tue Jan 25 20:11:18 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1503416A4CE for ; Tue, 25 Jan 2005 20:11:18 +0000 (GMT) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id C444743D3F for ; Tue, 25 Jan 2005 20:11:17 +0000 (GMT) (envelope-from kirk@strauser.com) Received: from localhost (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id B559221D4CB for ; Tue, 25 Jan 2005 14:11:16 -0600 (CST) Received: from kanga.honeypot.net ([127.0.0.1]) by localhost (kanga.honeypot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 33539-02 for ; Tue, 25 Jan 2005 14:11:16 -0600 (CST) Received: from janus.daycos.com (janus.daycos.com [204.26.70.77]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTP id 4541021D1C6 for ; Tue, 25 Jan 2005 14:11:16 -0600 (CST) From: Kirk Strauser To: freebsd-stable@freebsd.org Date: Tue, 25 Jan 2005 14:11:12 -0600 User-Agent: KMail/1.7.2 References: <3aaaa3a0501181530975fecf@mail.gmail.com> <1106256780.582.5.camel@zappa.Chelsea-Ct.Org> <52406.207.219.213.162.1106257499.squirrel@207.219.213.162> In-Reply-To: <52406.207.219.213.162.1106257499.squirrel@207.219.213.162> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart10659206.U6YYOUS4z9"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501251411.15397.kirk@strauser.com> X-Virus-Scanned: amavisd-new at honeypot.net Subject: Re: CFLAGS=-O2 -pipe problems in RELENG_5 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 20:11:18 -0000 --nextPart10659206.U6YYOUS4z9 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 20 January 2005 15:44, Mike Jakubik wrote: > Wouldn't we want strict aliasing then? Strict aliasing is a feature of the code being compiled, not the compiler. = =20 The "-fstrict-aliasing" flag basically means "this code follows the=20 strictest aliasing rules, so you can use extra optimizations on it that=20 depend on adherence to those rules". =2D-=20 Kirk Strauser --nextPart10659206.U6YYOUS4z9 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iD8DBQBB9qfj5sRg+Y0CpvERAoauAJ90PPbiRdwsNBWXqgBC1rmeC9uZXACfYDkg hhlQFTjBBgqyTZgIW0AaSDY= =N0l4 -----END PGP SIGNATURE----- --nextPart10659206.U6YYOUS4z9-- From owner-freebsd-stable@FreeBSD.ORG Tue Jan 25 21:24:48 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9D0716A4CE; Tue, 25 Jan 2005 21:24:48 +0000 (GMT) Received: from manor.msen.com (manor.msen.com [148.59.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63F5943D39; Tue, 25 Jan 2005 21:24:48 +0000 (GMT) (envelope-from wayne@manor.msen.com) Received: from manor.msen.com (localhost [127.0.0.1]) by manor.msen.com (8.12.9p2/8.12.9) with ESMTP id j0PLOjTA054629; Tue, 25 Jan 2005 16:24:47 -0500 (EST) (envelope-from wayne@manor.msen.com) Received: (from wayne@localhost) by manor.msen.com (8.12.9p2/8.12.9/Submit) id j0PLOjAI054628; Tue, 25 Jan 2005 16:24:45 -0500 (EST) (envelope-from wayne) Date: Tue, 25 Jan 2005 16:24:45 -0500 From: "Michael R. Wayne" To: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org Message-ID: <20050125212445.GY1168@manor.msen.com> Mail-Followup-To: freebsd-stable@freebsd.org, freebsd-amd64@freebsd.org References: <20050119214229.GE1168@manor.msen.com> <20050119191813.H78340@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050119191813.H78340@carver.gumbysoft.com> User-Agent: Mutt/1.4.2.1i Subject: Re: Failure on today's CVS (stable, AMD) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 21:24:49 -0000 On Wed, Jan 19, 2005 at 07:19:49PM -0800, Doug White wrote: > On Wed, 19 Jan 2005, Michael R. Wayne wrote: > > > CVS today. Dual Opteron running > > 5.3-STABLE #3: Tue Nov 30 01:44:05 EST 2004 > > > > Following the instructions in UPDATING, I get the following, > > indicating a bad kernel. 2 questions: > > > > 1) Is this a known, corrected issue as of today? I ran another > > CVSUP and did not see any changed to src. > > Looks like your SCSi controller stopped probing. You'll need to look at > the dmesg more closely to identify why. Followup for the archives. The twa driver has known issues right now, a fix is being worked on. I received a patch and applied it, which did indeed solve the problem. My understanding is that this patch should be committed later this week so if you are reading this thread much after Feb 1, 2005 it likely does not apply. /\/\ \/\/ From owner-freebsd-stable@FreeBSD.ORG Tue Jan 25 22:05:46 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76CE416A4CE for ; Tue, 25 Jan 2005 22:05:46 +0000 (GMT) Received: from smtp2.Stanford.EDU (smtp2.Stanford.EDU [171.67.16.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5270B43D2F for ; Tue, 25 Jan 2005 22:05:46 +0000 (GMT) (envelope-from richw@richw.org) Received: from whodunit.richw.org (SW-90-716-276-1.Stanford.EDU [171.66.155.243]) by smtp2.Stanford.EDU (8.12.11/8.12.11) with ESMTP id j0PM5jX6020563 for ; Tue, 25 Jan 2005 14:05:45 -0800 Received: from whodunit.richw.org (localhost [127.0.0.1]) by whodunit.richw.org (8.13.1/8.13.1) with ESMTP id j0PM5iSn036419; Tue, 25 Jan 2005 14:05:44 -0800 (PST) (envelope-from richw@whodunit.richw.org) Received: (from richw@localhost) by whodunit.richw.org (8.13.1/8.13.1/Submit) id j0PM5iS3036418; Tue, 25 Jan 2005 14:05:44 -0800 (PST) (envelope-from richw) Date: Tue, 25 Jan 2005 14:05:44 -0800 (PST) From: Rich Wales To: freebsd-stable@freebsd.org Message-ID: <20050125215609.C30917.richw@whodunit.richw.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: NIC acting promiscuously -- how to fix? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 22:05:46 -0000 Doug Hardie wrote: > To verify what your interface is accepting use: tcpdump -pei rl0 > That will show the packets that it accepts including the ethernet > headers. Those headers should all have your MAC address in them > (send or receive). Very good suggestion. Thanks. After running the above command for a while, and examining the output, it turns out that the large amount of traffic on my external net is mostly ARP "who-has" requests (sent to the broadcast MAC address). These are, of course, legitimate. There is also a relatively small number of multicast packets -- most of which are MDNS (multicast DNS). So, I was mistaken; my NIC doesn't have a "promiscuity" problem after all. Sorry for raising a needless alarm. Rich Wales richw@richw.org http://www.richw.org From owner-freebsd-stable@FreeBSD.ORG Tue Jan 25 22:26:32 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 195D216A4CE for ; Tue, 25 Jan 2005 22:26:32 +0000 (GMT) Received: from shiva.nextrials.com (shiva.nextrials.com [64.81.74.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7202B43D54 for ; Tue, 25 Jan 2005 22:26:31 +0000 (GMT) (envelope-from dannyman@toldme.com) Received: from [192.168.1.102] (mito.sr.nextrials.com [192.168.1.102]) by shiva.nextrials.com (Postfix) with ESMTP id 8A2BE3C282A; Tue, 25 Jan 2005 14:26:30 -0800 (PST) Message-ID: <41F6C72C.9080400@toldme.com> Date: Tue, 25 Jan 2005 14:24:44 -0800 From: Danny Howard User-Agent: Mozilla Thunderbird 1.0 (X11/20041209) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Karl Denninger References: <20050119082319.A17451@Denninger.Net> In-Reply-To: <20050119082319.A17451@Denninger.Net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: OK, it appears to be running, but what's this?! (gmirror) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 22:26:32 -0000 Karl Denninger wrote: >Gen2# bsdlabel /dev/mirror/m0s1 >[...] > >Uh, no, I didn't do that. The original label was put there during >system installation, and I absolutely did not offset "c" > >Is this still ok, or am I asking for a (bogus) hard error some day when the >system attempts access beyond the end of the physical disk? > Karl, From my research, it had looked like the gmirror setup stuff will rearrange your disk a bit to make room for the metadata, and otherwise leave space at the beginning of the disk for various, presumably good reasons. Some spelunking around the archives may score you a more verbose answer. -danny From owner-freebsd-stable@FreeBSD.ORG Tue Jan 25 22:35:41 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5459516A4CE for ; Tue, 25 Jan 2005 22:35:41 +0000 (GMT) Received: from shiva.nextrials.com (shiva.nextrials.com [64.81.74.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2519143D2F for ; Tue, 25 Jan 2005 22:35:41 +0000 (GMT) (envelope-from dannyman@toldme.com) Received: from [192.168.1.102] (mito.sr.nextrials.com [192.168.1.102]) by shiva.nextrials.com (Postfix) with ESMTP id DF74B3C282A; Tue, 25 Jan 2005 14:35:40 -0800 (PST) Message-ID: <41F6C953.9040205@toldme.com> Date: Tue, 25 Jan 2005 14:33:55 -0800 From: Danny Howard User-Agent: Mozilla Thunderbird 1.0 (X11/20041209) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Michael R. Wayne" References: <20050119151301.A22310@Denninger.Net> <8eea040805011913334b140af6@mail.gmail.com> <8eea04080501191506237fc762@mail.gmail.com> <20050119171504.A23623@Denninger.Net> <41EF22F0.7010009@errno.com> <20050119213605.B26294@Denninger.Net> <20050120210923.GJ1168@manor.msen.com> In-Reply-To: <20050120210923.GJ1168@manor.msen.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org Subject: Re: Bad disk or kernel (ATA Driver) problem? - SOLVED X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2005 22:35:41 -0000 Michael R. Wayne wrote: >On Wed, Jan 19, 2005 at 09:36:05PM -0600, Karl Denninger wrote: > >>What 'other vendor' have you found that makes RELIABLE SATA disks in the >>high capacity (e.g. 200-300gb) arena? >> > >WD now makes a SATA RAID line. HIGHLY recommended by 3ware. > I read with some alarm about trouble with SuperMicro servers and ATA, because that is my new box. I'll chime in a data point saying that I have not seen any errors with the SuperMicro 1U and my 250G Western Digital SATA drives: atapci0: port 0x4000-0x400f,0x4020-0x4023,0x4028-0x402f,0x4024-0x4027,0x4030-0x4037 mem 0xfc300000-0xfc3001ff irq 26 at device 2.0 on pci3 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 atapci1: port 0x4010-0x401f,0x4038-0x403b,0x4040-0x4047,0x403c-0x403f,0x4048-0x404f mem 0xfc300400-0xfc3005ff irq 27 at device 3.0 on pci3 ata4: channel #0 on atapci1 ata5: channel #1 on atapci1 atapci2: port 0x2060-0x206f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci2 ata1: channel #1 on atapci2 acd0: CDROM at ata1-master UDMA33 ad4: 238475MB [484521/16/63] at ata2-master SATA150 ad6: 238475MB [484521/16/63] at ata3-master SATA150 The vendor (ASA) were initially reluctant to send me this box because they were keen to issues with FreeBSD's SATA chipset compatability, but I did some research and convinced them not to fret. I am saving money and probably some hassle by replacing 3ware with gmirror. My cheat sheet is posted at http://dannyman.toldme.com/2005/01/24/freebsd-howto-gmirror-system/ . Thanks, -danny From owner-freebsd-stable@FreeBSD.ORG Wed Jan 26 04:48:44 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6660116A4CE for ; Wed, 26 Jan 2005 04:48:44 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 007F543D2F for ; Wed, 26 Jan 2005 04:48:41 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: by rproxy.gmail.com with SMTP id f1so6835rne for ; Tue, 25 Jan 2005 20:48:40 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=ZyuJGZgQ8B7IWEyBsNXcI0BlvrCNtgnL/ovrkwIU3KK6DMUPkx7s0HZDtrV1kKwhDZ4jfusrOCNrbo6e6Z6HrLQr7tzISS2XhiwyuDf6zfUAuB+k/TBNN0JXMf1VXxHPCPbSoGOB+TEtV55ZSBOc8gukAy+7mSAfVDVxXIS5HwU= Received: by 10.38.71.4 with SMTP id t4mr21987rna; Tue, 25 Jan 2005 20:48:40 -0800 (PST) Received: by 10.39.1.45 with HTTP; Tue, 25 Jan 2005 20:48:40 -0800 (PST) Message-ID: <3aaaa3a05012520483adb5de6@mail.gmail.com> Date: Wed, 26 Jan 2005 04:48:40 +0000 From: Chris To: Artem Kuchin In-Reply-To: <00ba01c50211$23389ee0$0c00a8c0@artem> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <00ba01c50211$23389ee0$0c00a8c0@artem> cc: freebsd-stable@freebsd.org cc: Robert Watson Subject: Re: Lock up problems with 5.3-STABLE (was: Cannot build kernel with options WITNESS) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Chris List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2005 04:48:44 -0000 I would suspect the jail code at this point here is my kernel config for my smp machine Dual Athlon-mp 40 gig ide hd 1024 Ram xl0 nic device 100mbit fdx machine i386 cpu I686_CPU ident WEB1 # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. options SCHED_4BSD # 4BSD scheduler options INET # InterNETworking #options INET6 # IPv6 communications protocols 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 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_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options SCSI_DELAY=15000 # 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 extension s options KBD_INSTALL_CDEV # install a CDEV entry in /dev #options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. #options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. device apic # I/O APIC options SMP # SMP # Bus support. Do not remove isa, even if you have no isa slots device isa 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 #device ahd # AHA39320/29320 and onboard AIC79xx devices #device amd # AMD 53C974 (Tekram DC-390(T)) #device isp # Qlogic family #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 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 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 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 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 # Enable this for the pcvt (VT220 compatible) console driver #device vt #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor device agp # support several AGP chipsets # Floating point support - do not disable. device npx # 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 # 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 the sio 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 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 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 nge # NatSemi DP83820 gigabit ethernet #device pcn # AMD Am79C97x PCI 10/100 (precedence over 'lnc' ) #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 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 lnc # NE2100, NE32-VL Lance Ethernet cards #device sn # SMC's 9000 series of Ethernet chips #device xe # Xircom pccard Ethernet # ISA devices that use the old ISA shims #device le # Wireless NIC cards #device wlan # 802.11 support #device an # Aironet 4500/4800 802.11 wireless NICs. #device awi # BayStack 660 and others #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 mem # Memory and kernel memory devices device io # I/O device 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 snp # snoop device # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface 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 urio # Diamond Rio 500 MP3 player #device uscanner # Scanners # USB Ethernet, requires mii #device aue # ADMtek USB Ethernet #device axe # ASIX Electronics USB 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!) options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #enable logging to syslogd(8) options IPFIREWALL_VERBOSE_LIMIT=50 options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPFIREWALL_FORWARD options IPDIVERT options IPSTEALTH #support for stealth forwarding options DUMMYNET options TCP_DROP_SYNFIN #options PREEMPTION options HZ=1000 options QUOTA options ACCEPT_FILTER_DATA options ACCEPT_FILTER_HTTP and dmesg.boot FreeBSD 5.3-RELEASE-p5 #1: Sat Jan 22 02:43:33 UTC 2005 root@web1.hostingfreak.net:/usr/obj/usr/src/sys/WEB1 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(TM) MP 2000+ (1666.73-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x662 Stepping = 2 Features=0x383fbff AMD Features=0xc0480000 real memory = 1073741824 (1024 MB) avail memory = 1045397504 (996 MB) MPTable: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Assuming intbase of 0 ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: pcibus 0 on motherboard pci0: on pcib0 agp0: port 0xe800-0xe803 mem 0xfb800000-0xfb800fff, 0xfc000000-0xfdffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 5.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f,0x376,0x170-0x177,0x3f6 ,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 7.3 (no driver attached) xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xd400-0xd47f mem 0xf8000000-0xf800 007f irq 16 at device 8.0 on pci0 miibus0: on xl0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:e0:18:da:fa:c1 pcib2: at device 16.0 on pci0 pci2: on pcib2 cpu0 on motherboard cpu1 on motherboard orm0: at iomem 0xc0000-0xc7fff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A 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 unknown: can't assign resources (port) Timecounters tick every 1.000 msec ipfw2 initialized, divert enabled, rule-based forwarding enabled, default to acc ept, logging limited to 50 packets/entry by default ad0: 39083MB [79408/16/63] at ata0-master UDMA100 acd0: CDROM at ata1-master PIO4 SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/ad0s1a Only thing that concerns me with my config is I see no "SMP: AP CPU #2 Launched!" is this normal for a 2 cpu machine? The box is stable. 4:48AM up 4 days, 26 mins, 2 users, load averages: 0.00, 0.01, 0.00 5.3-RELEASE-p5 Chris On Mon, 24 Jan 2005 15:26:42 +0300, Artem Kuchin wrote: > > > On Sun, 23 Jan 2005, Artem Kuchin wrote: > > > >> > On Sat, 22 Jan 2005, Artem Kuchin wrote: > >> > > >> >> I cvssed just an hour ago. 5.3-STABLE and cannot build kernel with > >> >> WITNES. It complains: > >> > > >> > This occurs when building WITNESS without DDB in the kernel, which was not > >> > a tested build case when I added "show alllocks", and apparently is a > >> > relatively uncommon configuration as you're the first person to bump into > >> > it. I've just committed the fix as subr_witness.c:1.187 in HEAD, and > >> > subr_witness.c:1.178.2.4 in RELENG_5. Please let me know if this doesn't > >> > fix the problem for you. > >> > >> It fixed the problem. I am actually stuggling with unpredictable weird > >> lock ups, when the host can be pinged but i cannot connect via > >> ssh/telnet or httpd or anything else. It happens w/o any visible reason. > >> I am running several jails with mysql and apache in each and canot make > >> the whole system stable yet. > > > > This is typically a sign of one of two problems: > > > > - The system is live locked due to very high load, so the ithread, > > netisrs, etc, in the kernel run fine, but user processes don't get a > > chance to run. > > > > - The system is dead locked due to user space processes getting wedged on > > common locks, but the kernel ithreads and netisrs can keep on > > responding. > > > > I generally assume that it's a deadlock as opposed to a live lock. I'd > > compile a kernel with DDB, KDB, WITNESS, and BREAK_TO_DEBUGGER. When the > > system appears to wedge, break into the debugger using a console or serial > > break (FYI: serial break is more reliable, and you get the benefit of > > being able to easily copy and paste debugging output using the serial > > console for DDB). Use "show alllocks" and "show lockedvnods" to examine > > most of the system's locking state. Changes are, either all the > > interesting processes are stacked up on VFS or VM locks, since those kinds > > of deadlocks produce the exact symptoms you describe: ping works fine > > because it only hits the netisr, but when you open TCP connections, the > > sshd (etc) block on VM or VFS locks attempting to fork new children or > > access a file in the file system name space. At first, the TCP > > connections will establish but there will be no application data; after a > > bit, they will not even return a SYN/ACK because the listen queue for the > > listen socket has filled. > > > > Well, i cvsed and reconpiled the kernel with WITNESS, INVARINATS, turned off > adaptive giant and got a lock today at 7 am. Since the server is remotely controlled > i took my digital camera because i cannot connect serial console to it and went to the server. > I expetced to see some special message about something going wrong, break > into debugger (CTRL+ALT+ESC) and to take some pictures of dumps of console. > But, i saw nothing. The lasrt message on th screen was about ssh loging last evening > and the last message in /var/log/all.log was about entropy save from cron. > I could not break into debugger usinmg CTRL-ALT+ESC. I did nothing. So, > it looked like a hard lock. > > At this point i would like to tell the whole story. > We bought this server in may 2004 and decided to extemsively test the hardware > while there were not 5.3. We actually expected it around august. SO, we installed > 5-CURRENT and ran high load tests (cpu, memory, disk storage, network) from > /usr/ports/benchmark at the same time and one-by-one several weeks. There were > not a glitch. After that we turned it off and waited for RELEASE. RELEASE has > come and we begun to setup the servre as it should work. As the server's > primary mission is to host a buch of site we decided to setup jails for each site, > So we did in december and put the server on prividers co-location severals > kilometer away from the office. Next day the server locked up. We were surprised > but just rebooted it, It locked up the next day gain. We cvsupped and rebuild the > system and the jails. The server locked up the next day. During the new year break > i have figureed that if there are more that one jail running the server locks withun > 24 hours with very hight probablity and within 48 hours with 100% probability. I > wrote into freebsd-stable about it. You have asked for debugger dump (pcpu, list of > lock, e.t.c). I could not do it at that time, so, i did not reply and just cvsupped in > the beginning of january and rebuilt the system and the jails again. Magically, after > that i could run 5 jails (did not tried more) for over a week and i already decided that > the bug was fixed and I could host the site. Alas, the next glitch did not wait to long. > After a few more days i saw a srange situatuon - i could not connect to server using > SSH. SSH replied about auth key or something like that. I rebootied the system and > ssh worked fine. Still have no idea what that was, but i setuo IPFIREWALL and a telnet > server for accept connection only from one ip address, so, if ssh fails I could use telnet. > After that i moved a real site with perl scripts, 1GB database, mail account (using qmail+vpopmail) > into one of the jails and the next day got the next problem: I could ping server, but could not > connect using ssh, www, telnet (110,25,23). I tried to recompile the kernel with INVARINATS, > WITNESS and disable the adaptive giant. I could not, so I wrote about it to you. You fixed > the source and now i recompliled the source again and today got a lock again with all those > options enabled and this time i could not ping the server. > I could thing that there is semething wrong with the hardware, but it passed > many days of testing. Anyway, my current idea are > > 1) Something wrong with jail code > 2) Something wrong with SMP code > 3) Something wrong with HYPERTHREADING code > 4) Something wrong with Memory disk code (md device, which i use) > 5) Something wrong with the hardware > > So, today, i opened bios, truned off hyperthreaading, fast strinmg operations and > all other 'more advanced' features in the bios. Turned off IDE controller the motherboard. > This rule out HYPERTHREADING code problem and somewaht hardware problem. > > I turned off MD usage (not more memory disk, but actually i need it very badly). > So i rule out the md code problem. > > Now, i will run some web access test (simulation of browsing for a week). It the > sever does not lock up, i will consider that i have found a workaround for some > hidden bug and the bug is somewere in md, ht code or hardware. > > If it locks up again the i will giveup jails and try for one more week. If it does not > lock up - jail code is the problem. > > If it locks up without jails, then i will turn off SMP and try again. > > If it locks up without nothing, then hardware if faulty and will have futher > choice of hanging myself or shooting in the head. > > I would like to see your and others' comments on the story and i have one > more question: what does options _KPOSIX_PRIORITY_SCHEDULING > do? May it be somehow related to the problem? > > The hardware is: > > MB dual xeon Supermicro X5DPE-G2 > CPU P4 XEON 2,667Ghz 512Kb cache 533mhz socket 604 > 2 Gb 266Mhz, DDR, ECC, Reg, 1GB dimm > 4 HDDs 120Gb (seagate baracuda 7200.7) > 3Ware Escalade 8506-4LP > Case Supermicro SC822T-550LP > Slim DVD/CD-RW Toshiba SD-R2412B IDE (OEM) > > The todays kernel CONFIG wich got locked: > > machine i386 > cpu I486_CPU > cpu I586_CPU > cpu I686_CPU > ident OMNI2 > > options SMP > > options QUOTA > > options SCHED_4BSD # 4BSD scheduler > options INET # InterNETworking > options INET6 # IPv6 communications protocols > 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 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_GPT # GUID Partition Tables. > options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] > options COMPAT_FREEBSD4 # Compatible with FreeBSD4 > #options SCSI_DELAY=15000 # 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 > > device apic # I/O APIC > > # Bus support. Do not remove isa, even if you have no isa slots > device isa > 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 peripherals > device scbus # SCSI bus (required for SCSI) > device da # Direct Access (disks) > device pass # Passthrough device (direct SCSI access) > 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 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 > > # Floating point support - do not disable. > device npx > > # Power management support (see NOTES for more options) > #device apm > # Add suspend/resume support for the i8254. > #device pmtimer > > # Serial (COM) ports > device sio # 8250, 16[45]50 based serial ports > > # Parallel port > device ppc > device ppbus # Parallel port bus (required) > device lpt # Printer > device ppi # Parallel port interface device > #device vpo # Requires scbus and da > > device miibus # MII bus support > device fxp # Intel EtherExpress PRO/100B (82557, 82558) > device em > > device loop # Network loopback > device mem # Memory and kernel memory devices > device io # I/O device > 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 bpf # Berkeley packet filter > # USB support > device uhci # UHCI PCI->USB interface > device ohci # OHCI PCI->USB interface > device usb # USB Bus (required) > #device udbp # USB Double Bulk Pipe devices > device ugen # Generic > device uhid # "Human Interface Devices" > device ulpt # Printer > device umass # Disks/Mass storage - Requires scbus and da > > # FireWire support > device firewire # FireWire bus code > #device sbp # SCSI over FireWire (Requires scbus and da) > #device fwe # Ethernet over FireWire (non-standard!) > > options IPFIREWALL > options IPFIREWALL_VERBOSE > options IPFIREWALL_VERBOSE_LIMIT=10000 > options IPFIREWALL_DEFAULT_TO_ACCEPT > > device snp > device speaker > > options DDB > options KDB > options BREAK_TO_DEBUGGER > options INVARIANT_SUPPORT > options INVARIANTS > options WITNESS > options WITNESS_KDB > options WITNESS_SKIPSPIN > #options ADAPTIVE_GIANT # Giant mutex is adaptive. > > DMESG (the config which got locked): > > Copyright (c) 1992-2005 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 5.3-STABLE #3: Sun Jan 23 01:04:00 MSK 2005 > matrix@omni2.itlegion.ru:/usr/obj/usr/src/sys/OMNI2 > WARNING: WITNESS option enabled, expect reduced performance. > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(TM) CPU 2.66GHz (2665.93-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf25 Stepping = 5 > Features=0xbfebfbff SE2,SS,HTT,TM,PBE> > Hyperthreading: 2 logical CPUs > real memory = 4160225280 (3967 MB) > avail memory = 4077486080 (3888 MB) > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > cpu2 (AP): APIC ID: 6 > cpu3 (AP): APIC ID: 7 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-47 on motherboard > ioapic2 irqs 48-71 on motherboard > ioapic3 irqs 72-95 on motherboard > ioapic4 irqs 96-119 on motherboard > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > cpu2: on acpi0 > cpu3: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pci0: at device 0.1 (no driver attached) > pcib1: at device 2.0 on pci0 > pci1: on pcib1 > pci1: at device 28.0 (no driver attached) > pcib2: at device 29.0 on pci1 > pci2: on pcib2 > pci1: at device 30.0 (no driver attached) > pcib3: at device 31.0 on pci1 > pci3: on pcib3 > em0: port 0x3000-0x303f mem 0xfc200000-0xfc21ffff irq 28 at device 2 > .0 on pci3 > em0: Ethernet address: 00:30:48:2a:2d:bc > em0: Speed:N/A Duplex:N/A > em1: port 0x3040-0x307f mem 0xfc220000-0xfc23ffff irq 29 at device 2 > .1 on pci3 > em1: Ethernet address: 00:30:48:2a:2d:bd > em1: Speed:N/A Duplex:N/A > pcib4: at device 3.0 on pci0 > pci4: on pcib4 > pci4: at device 28.0 (no driver attached) > pcib5: at device 29.0 on pci4 > pci5: on pcib5 > pci4: at device 30.0 (no driver attached) > pcib6: at device 31.0 on pci4 > pci6: on pcib6 > twe0: <3ware Storage Controller. Driver version 1.50.01.002> port 0x4000-0x400f mem 0xfc800000-0xfcffffff irq 72 at device 1. > 0 on pci6 > twe0: [GIANT-LOCKED] > twe0: 4 ports, Firmware FE7S 1.05.00.063, BIOS BE7X 1.08.00.048 > uhci0: port 0x2000-0x201f irq 16 at device 29.0 on pci0 > uhci0: [GIANT-LOCKED] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0x2020-0x203f irq 19 at device 29.1 on pci0 > uhci1: [GIANT-LOCKED] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 2 ports with 2 removable, self powered > uhci2: port 0x2040-0x205f irq 18 at device 29.2 on pci0 > uhci2: [GIANT-LOCKED] > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub2: 2 ports with 2 removable, self powered > pcib7: at device 30.0 on pci0 > pci7: on pcib7 > pci7: at device 1.0 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port 0x2060-0x206f,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 > ata0: channel #0 on atapci0 > ata2: channel #1 on atapci0 > pci0: at device 31.3 (no driver attached) > acpi_button0: on acpi0 > speaker0: port 0x61 on acpi0 > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > 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 > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 > fdc0: [FAST] > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > orm0: at iomem 0xe0000-0xe3fff,0xc9000-0xc9fff,0xc8000-0xc8fff,0xc0000-0xc7fff on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounters tick every 10.000 msec > ipfw2 initialized, divert disabled, rule-based forwarding disabled, default to accept, logging limited to 10000 packets/entry > by default > acd0: CDRW at ata0-slave UDMA33 > twed0: on twe0 > twed0: 343417MB (703318656 sectors) > SMP: AP CPU #2 Launched! > SMP: AP CPU #1 Launched! > SMP: AP CPU #3 Launched! > Mounting root from ufs:/dev/twed0s1a > em0: Link is up 100 Mbps Full Duplex > > _______________________________________________ > 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-stable@FreeBSD.ORG Wed Jan 26 08:13:40 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A26B716A4CE for ; Wed, 26 Jan 2005 08:13:40 +0000 (GMT) Received: from osiris.itlegion.ru (osiris.itlegion.ru [84.21.226.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F32643D3F for ; Wed, 26 Jan 2005 08:13:39 +0000 (GMT) (envelope-from matrix@itlegion.ru) Received: from artem ([192.168.0.12]) by osiris.itlegion.ru (8.13.1/8.13.1) with SMTP id j0Q8DTOo011610; Wed, 26 Jan 2005 11:13:30 +0300 (MSK) (envelope-from matrix@itlegion.ru) X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 63885, updated: 25.01.2005] Message-ID: <009301c5037f$858282e0$0c00a8c0@artem> From: "Artem Kuchin" To: "Chris" References: <00ba01c50211$23389ee0$0c00a8c0@artem> <3aaaa3a05012520483adb5de6@mail.gmail.com> Date: Wed, 26 Jan 2005 11:17:47 +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.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 cc: freebsd-stable@freebsd.org Subject: Re: Lock up problems with 5.3-STABLE (was: Cannot build kernel withoptions WITNESS) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2005 08:13:40 -0000 >I would suspect the jail code at this point here is my kernel config > for my smp machine > > Dual Athlon-mp > 40 gig ide hd > 1024 Ram > xl0 nic device 100mbit fdx Well, i am currently suspecting Hyperthreading code. I have disabled it and turned back memory disk and all jails. The box is running stable for last 3 days. You dont' have HT cpus, so you have only 2 logical, but i HAD 4. Now i have 2 logical cpus, which are real cpus. Let's see what happens in the next 4 days. Regards, Artem Kuchin IT Legion Ltd. Moscow, Russia www.itlegion.ru matrix@itlegion.ru +7 095 232-0338 From owner-freebsd-stable@FreeBSD.ORG Wed Jan 26 10:48:02 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E319916A4CE for ; Wed, 26 Jan 2005 10:48:02 +0000 (GMT) Received: from web54008.mail.yahoo.com (web54008.mail.yahoo.com [206.190.36.232]) by mx1.FreeBSD.org (Postfix) with SMTP id 3E06143D46 for ; Wed, 26 Jan 2005 10:48:02 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: (qmail 30645 invoked by uid 60001); 26 Jan 2005 10:48:01 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=fXk002vaABGK9wdiGfLOIUhhvS4m8JdjvzM0uBbnu/9hAmQKk/RysArpFJIbMJJj9HE1KMbYECcr/QNpIh2emIDBMc6U6AAnd62OdTDtXTxrC8YY3TJNx7BfBY+61rZLiSNwIacjz+OpknfNQE3llR1xKoozPzD5kxFLTEOX6QM= ; Message-ID: <20050126104801.30643.qmail@web54008.mail.yahoo.com> Received: from [147.46.44.181] by web54008.mail.yahoo.com via HTTP; Wed, 26 Jan 2005 02:48:01 PST Date: Wed, 26 Jan 2005 02:48:01 -0800 (PST) From: Rob To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Linking problems with gcc 3.4.2 and glibc on 5.3-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2005 10:48:03 -0000 Hi, There seems to be a bug with the gcc version of 5.3 STABLE (gcc 3.4.2), when using: #define _GLIBCXX_DEBUG #define _GLIBCXX_DEBUG_PEDANTIC I discovered this when compiling the LyX sources, and the LyX mailing list pointed out that this is gcc/OS FreeBSD issue. The linking ends with errors that complain about "__gnu_norm::....", for example: BranchList.o(.gnu.linkonce.t._ZN10__gnu_norm4listI6BranchSaIS1_EE9_M_insertENS_14_List_iteratorIS1_EERKS1_+0x19): In function `__gnu_norm::list>>::_M_insert(__gnu_norm::_List_iterator, Branch const&)': /usr/include/c++/3.4/bits/locale_facets.tcc:2443: undefined reference to `__gnu_norm::_List_node_base::hook(__gnu_norm::_List_node_base*)' BranchList.o(.gnu.linkonce.t._ZN10__gnu_norm4listI6BranchSaIS1_EE8_M_eraseENS_14_List_iteratorIS1_EE+0xd): In function `__gnu_norm::list>>::_M_erase(__gnu_norm::_List_iterator)': /usr/include/c++/3.4/debug/list:122: undefined reference to `__gnu_norm::_List_node_base::unhook()' [...cut...] /usr/include/c++/3.4/bits/stl_algobase.h:155: undefined reference to `__gnu_norm::_List_node_base::transfer(__gnu_norm::_List_node_base*, __gnu_norm::_List_node_base*)' ../boost/libs/signals/src/.libs/libboost_signals.a(trackable.o)(.gnu.linkonce.t._ZN10__gnu_norm4listIN5boost7signals10connectionESaIS3_EE9_M_insertENS_14_List_iteratorIS3_EERKS3_+0x28): In function `__gnu_norm::list>>::_M_insert(__gnu_norm::_List_iterator, boost::signals::connection const&)': /usr/include/c++/3.4/debug/formatter.h:359: undefined reference to `__gnu_norm::_List_node_base::hook(__gnu_norm::_List_node_base*)' Is this a known issue? Rob. __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com From owner-freebsd-stable@FreeBSD.ORG Wed Jan 26 11:44:18 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 584E216A4CE for ; Wed, 26 Jan 2005 11:44:18 +0000 (GMT) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id F07D443D2D for ; Wed, 26 Jan 2005 11:44:17 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk) by mail.ticketswitch.com with esmtp (Exim 4.43 (FreeBSD)) id 1Ctlaq-000PG2-Ef for stable@freebsd.org; Wed, 26 Jan 2005 11:44:16 +0000 Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim 4.43 (FreeBSD)) id 1Ctlaq-000M7b-0Q for stable@freebsd.org; Wed, 26 Jan 2005 11:44:16 +0000 To: stable@freebsd.org Message-Id: From: Pete French Date: Wed, 26 Jan 2005 11:44:16 +0000 Subject: supping the ports for 4.11 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2005 11:44:18 -0000 I understand that recent changes mean that when I cvsup the ports I also need to do a 'make fetchindex' to get the index file right ? But that will give me the most recent index file will it not ? So if I am supping the ports with a tag of tag=RELEASE_4_11_0 to get the 4.11 ports, how do I fetch the index file that goes with them ? -pcf. From owner-freebsd-stable@FreeBSD.ORG Wed Jan 26 11:52:31 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CAEA16A4CE for ; Wed, 26 Jan 2005 11:52:31 +0000 (GMT) Received: from gate.xbsd.org (xbsd.org [82.233.2.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 110D543D4C for ; Wed, 26 Jan 2005 11:52:31 +0000 (GMT) (envelope-from flz@xbsd.org) Received: from localhost (localhost.xbsd.org [127.0.0.1]) by gate.xbsd.org (Postfix) with ESMTP id 10EA411860; Wed, 26 Jan 2005 12:53:12 +0100 (CET) Received: from gate.xbsd.org ([127.0.0.1]) by localhost (gate.xbsd.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 89243-09; Wed, 26 Jan 2005 12:53:07 +0100 (CET) Received: from [192.168.20.107] (ALagny-109-1-7-162.w81-50.abo.wanadoo.fr [81.50.48.162]) by gate.xbsd.org (Postfix) with ESMTP id 9C8F611737; Wed, 26 Jan 2005 12:53:06 +0100 (CET) Message-ID: <41F78467.3000403@xbsd.org> Date: Wed, 26 Jan 2005 12:52:07 +0100 From: Florent Thoumie User-Agent: Mozilla Thunderbird 1.0 (X11/20050107) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pete French References: In-Reply-To: X-Enigmail-Version: 0.89.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig20E41611D7E3D4EB3CB26769" X-Virus-Scanned: amavisd-new at xbsd.org cc: stable@freebsd.org Subject: Re: supping the ports for 4.11 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2005 11:52:31 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig20E41611D7E3D4EB3CB26769 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Pete French wrote: > I understand that recent changes mean that when I cvsup the > ports I also need to do a 'make fetchindex' to get the index > file right ? You can also build your own, but that's obviously longer. > But that will give me the most recent index file will it not ? > So if I am supping the ports with a tag of tag=RELEASE_4_11_0 > to get the 4.11 ports, how do I fetch the index file that goes > with them ? You can find it here [1]. [1] ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4.11-release/INDEX -- Florent Thoumie flz@xbsd.org --------------enig20E41611D7E3D4EB3CB26769 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.0 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB94RxMxEkbVFH3PQRApPEAKCMtTZyp6UUemXHUBEtCfqjPpIwrwCeOLrC WUBFgNs837wVPuNJ+VgMNbI= =yvc/ -----END PGP SIGNATURE----- --------------enig20E41611D7E3D4EB3CB26769-- From owner-freebsd-stable@FreeBSD.ORG Wed Jan 26 12:03:30 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0591F16A4CE for ; Wed, 26 Jan 2005 12:03:30 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61B9443D41 for ; Wed, 26 Jan 2005 12:03:29 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: by rproxy.gmail.com with SMTP id f1so46414rne for ; Wed, 26 Jan 2005 04:03:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=omIjJ7T6A20KX38AaWC/ZoU+S5H3PHp2Ew3sBejMe8eO2CHjJq8nh4tU3YE44iK1QpJx4QImu1EVpb5f5rs+d94O4YVb/I6ON+uO+L4he3SiYEXZ/oTuDsFuSzdT2vT/tD+vpO9MiKmTAvweCDUlaWfQPB1LoiXfGeDuyjn+3tc= Received: by 10.38.76.50 with SMTP id y50mr27867rna; Wed, 26 Jan 2005 04:03:28 -0800 (PST) Received: by 10.39.1.45 with HTTP; Wed, 26 Jan 2005 04:03:28 -0800 (PST) Message-ID: <3aaaa3a0501260403611abe49@mail.gmail.com> Date: Wed, 26 Jan 2005 12:03:28 +0000 From: Chris To: Rob In-Reply-To: <20050126104801.30643.qmail@web54008.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050126104801.30643.qmail@web54008.mail.yahoo.com> cc: freebsd-stable@freebsd.org Subject: Re: Linking problems with gcc 3.4.2 and glibc on 5.3-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Chris List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2005 12:03:30 -0000 there is also a bug which prevents compiling of ezbounce and psybnc, I wonder how much testing went into the new gcc compiler or was it just bundled into the release, considering this is the reccommended release for production server's now this is a bad oversight, I think the gcc should be changed in the next patch level back to 3.3.6. Chris On Wed, 26 Jan 2005 02:48:01 -0800 (PST), Rob wrote: > > Hi, > > There seems to be a bug with the gcc version of 5.3 > STABLE (gcc 3.4.2), when using: > > #define _GLIBCXX_DEBUG > #define _GLIBCXX_DEBUG_PEDANTIC > > I discovered this when compiling the LyX sources, and > the LyX mailing list pointed out that this is gcc/OS > FreeBSD issue. > > The linking ends with errors that complain about > "__gnu_norm::....", for example: > > BranchList.o(.gnu.linkonce.t._ZN10__gnu_norm4listI6BranchSaIS1_EE9_M_insertENS_14_List_iteratorIS1_EERKS1_+0x19): > In function `__gnu_norm::list std::allocator>>::_M_insert(__gnu_norm::_List_iterator, > Branch const&)': > > /usr/include/c++/3.4/bits/locale_facets.tcc:2443: > undefined reference to > `__gnu_norm::_List_node_base::hook(__gnu_norm::_List_node_base*)' > BranchList.o(.gnu.linkonce.t._ZN10__gnu_norm4listI6BranchSaIS1_EE8_M_eraseENS_14_List_iteratorIS1_EE+0xd): > In function `__gnu_norm::list std::allocator>>::_M_erase(__gnu_norm::_List_iterator)': > > /usr/include/c++/3.4/debug/list:122: undefined > reference to > `__gnu_norm::_List_node_base::unhook()' > > [...cut...] > > /usr/include/c++/3.4/bits/stl_algobase.h:155: > undefined reference to > `__gnu_norm::_List_node_base::transfer(__gnu_norm::_List_node_base*, > __gnu_norm::_List_node_base*)' > ../boost/libs/signals/src/.libs/libboost_signals.a(trackable.o)(.gnu.linkonce.t._ZN10__gnu_norm4listIN5boost7signals10connectionESaIS3_EE9_M_insertENS_14_List_iteratorIS3_EERKS3_+0x28): > > In function > `__gnu_norm::list std::allocator>>::_M_insert(__gnu_norm::_List_iterator, > > boost::signals::connection const&)': > > /usr/include/c++/3.4/debug/formatter.h:359: undefined > reference to > `__gnu_norm::_List_node_base::hook(__gnu_norm::_List_node_base*)' > > Is this a known issue? > > Rob. > > __________________________________ > Do you Yahoo!? > Meet the all-new My Yahoo! - Try it today! > http://my.yahoo.com > > _______________________________________________ > 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-stable@FreeBSD.ORG Wed Jan 26 12:10:29 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B941216A4CE for ; Wed, 26 Jan 2005 12:10:29 +0000 (GMT) Received: from mail.ticketswitch.com (mail.ticketswitch.com [194.200.93.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B6C643D46 for ; Wed, 26 Jan 2005 12:10:29 +0000 (GMT) (envelope-from petefrench@ticketswitch.com) Received: from [172.16.1.6] (helo=dilbert.firstcallgroup.co.uk) by mail.ticketswitch.com with esmtp (Exim 4.43 (FreeBSD)) id 1Ctm0C-000Pdn-BS; Wed, 26 Jan 2005 12:10:28 +0000 Received: from petefrench by dilbert.firstcallgroup.co.uk with local (Exim 4.43 (FreeBSD)) id 1Ctm0B-000Iwr-V0; Wed, 26 Jan 2005 12:10:27 +0000 To: flz@xbsd.org, petefrench@ticketswitch.com In-Reply-To: <41F78467.3000403@xbsd.org> Message-Id: From: Pete French Date: Wed, 26 Jan 2005 12:10:27 +0000 cc: stable@freebsd.org Subject: Re: supping the ports for 4.11 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2005 12:10:29 -0000 > > So if I am supping the ports with a tag of tag=RELEASE_4_11_0 > > to get the 4.11 ports, how do I fetch the index file that goes > > with them ? > > You can find it here [1]. > [1] ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-4.11-release/INDEX Stupid me! Should have thought of that. Thanks! -pcf. From owner-freebsd-stable@FreeBSD.ORG Wed Jan 26 12:25:05 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20A6716A4CE for ; Wed, 26 Jan 2005 12:25:05 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 1EC9443D45 for ; Wed, 26 Jan 2005 12:25:04 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail invoked by alias); 26 Jan 2005 12:25:02 -0000 Received: from pD95D8C64.dip.t-dialin.net (EHLO lofi.dyndns.org) (217.93.140.100) by mail.gmx.net (mp009) with SMTP; 26 Jan 2005 13:25:02 +0100 X-Authenticated: #443188 Received: from [192.168.8.4] (lofi@kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id j0QCOrqr007513 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 26 Jan 2005 13:24:54 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: freebsd-stable@freebsd.org, Chris Date: Wed, 26 Jan 2005 13:24:44 +0100 User-Agent: KMail/1.7.2 References: <20050126104801.30643.qmail@web54008.mail.yahoo.com> <3aaaa3a0501260403611abe49@mail.gmail.com> In-Reply-To: <3aaaa3a0501260403611abe49@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart16521308.0WrTZLDu7E"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501261324.49050.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new X-Y-GMX-Trusted: 0 cc: Rob Subject: Re: Linking problems with gcc 3.4.2 and glibc on 5.3-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2005 12:25:05 -0000 --nextPart16521308.0WrTZLDu7E Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday, 26. January 2005 13:03, Chris wrote: > there is also a bug which prevents compiling of ezbounce and psybnc, I > wonder how much testing went into the new gcc compiler or was it just > bundled into the release, considering this is the reccommended release > for production server's now this is a bad oversight, I think the gcc > should be changed in the next patch level back to 3.3.6. Not gonna happen (would break binary compat). If you think you have found b= ugs=20 in gcc, try to get them fixed upstream, preferably in the gcc-branch -STABL= E=20 is currently using (i.e., right now 3.4). Updates of the base-gcc within th= e=20 same branch are possible if warranted. =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart16521308.0WrTZLDu7E Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB94wQXhc68WspdLARArSdAKCMd+mpaU70JP981N45ftCGKQWq1wCfWavZ jttm612JkTSYsawykw0RRto= =Au6A -----END PGP SIGNATURE----- --nextPart16521308.0WrTZLDu7E-- From owner-freebsd-stable@FreeBSD.ORG Wed Jan 26 07:48:45 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E500116A4CE for ; Wed, 26 Jan 2005 07:48:45 +0000 (GMT) Received: from hotmail.com (bay15-f13.bay15.hotmail.com [65.54.185.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E01C43D1F for ; Wed, 26 Jan 2005 07:48:45 +0000 (GMT) (envelope-from ppmmssgg@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 25 Jan 2005 23:48:01 -0800 Message-ID: Received: from 220.194.103.228 by by15fd.bay15.hotmail.msn.com with HTTP; Wed, 26 Jan 2005 07:47:27 GMT X-Originating-IP: [220.194.103.228] X-Originating-Email: [ppmmssgg@hotmail.com] X-Sender: ppmmssgg@hotmail.com From: =?gb2312?B?wfUg0e8=?= To: freebsd-stable@freebsd.org Date: Wed, 26 Jan 2005 07:47:27 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312; format=flowed X-OriginalArrivalTime: 26 Jan 2005 07:48:01.0407 (UTC) FILETIME=[5C48E8F0:01C5037B] X-Mailman-Approved-At: Wed, 26 Jan 2005 14:17:54 +0000 Subject: Use loader to load kernel.gz and mfsroot.gz in ext2 filesystem? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2005 07:48:46 -0000 Hi,sorry to bother you^-^ I have a problem about the loader of freebsd I put loader,kernel.gz and mfsroot.gz in an ext2(dos) file system on harddisk,and hope to directly use grub or use grub and loader(or other means?) to boot the system. When I use grub to transfer loader,I find it(freebsd loader) can't read files in ext2(dos) file system,and when i use grub 0.93 of redhat 9.0 to directly load mfsroot.gz by "initrd /mfsroot.gz",it fails with "linux kernel must be loaded before initrd". My goal is to put install.cfg,freebsd kernel and mfsroot on harddisk,then boot from harddisk into freebsd,and install it from original freebsd cd. Any one helps? any answers are appreciated.^-^ _________________________________________________________________ ÓëÁª»úµÄÅóÓѽøÐн»Á÷£¬ÇëʹÓà MSN Messenger: http://messenger.msn.com/cn From owner-freebsd-stable@FreeBSD.ORG Wed Jan 26 14:27:49 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F27AA16A4CF for ; Wed, 26 Jan 2005 14:27:48 +0000 (GMT) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 179B343D2D for ; Wed, 26 Jan 2005 14:27:48 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (ncvkbc@localhost [127.0.0.1]) by lurza.secnetix.de (8.12.11/8.12.11) with ESMTP id j0QERjrh060889 for ; Wed, 26 Jan 2005 15:27:46 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.12.11/8.12.11/Submit) id j0QERjmA060888; Wed, 26 Jan 2005 15:27:45 +0100 (CET) (envelope-from olli) Date: Wed, 26 Jan 2005 15:27:45 +0100 (CET) Message-Id: <200501261427.j0QERjmA060888@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG In-Reply-To: X-Newsgroups: list.freebsd-stable User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.10-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: Use loader to load kernel.gz and mfsroot.gz in ext2 filesystem? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2005 14:27:49 -0000 ?? ?? wrote: > I put loader,kernel.gz and mfsroot.gz in an ext2(dos) file system on > harddisk,and hope to directly use grub or use grub and loader(or other > means?) to boot the system. > > When I use grub to transfer loader,I find it(freebsd loader) can't read > files in ext2(dos) file system,and when i use grub 0.93 of redhat 9.0 to > directly load mfsroot.gz by "initrd /mfsroot.gz",it fails with "linux > kernel must be loaded before initrd". > > My goal is to put install.cfg,freebsd kernel and mfsroot on harddisk,then > boot from harddisk into freebsd,and install it from original freebsd cd. Why are you trying to use ext2fs (or msdosfs)? Is there a reason why you cannot use UFS? I suggest you use UFS. There's no need to use GRUB at all. I also wonder why you don't boot the installation from CD in the first place. Since you use a CD anyway ... Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 München Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "Clear perl code is better than unclear awk code; but NOTHING comes close to unclear perl code" (taken from comp.lang.awk FAQ) From owner-freebsd-stable@FreeBSD.ORG Wed Jan 26 15:52:02 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B948116A4CF; Wed, 26 Jan 2005 15:52:02 +0000 (GMT) Received: from rocky.mintel.co.uk (rocky2.mintel.com [217.206.187.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id 738A743D55; Wed, 26 Jan 2005 15:52:01 +0000 (GMT) (envelope-from jason.thomson@mintel.com) Received: from [10.0.62.5] ([10.0.62.5]) by rocky.mintel.co.uk (8.12.8p1/8.12.8) with ESMTP id j0QFpxaj029052; Wed, 26 Jan 2005 15:51:59 GMT (envelope-from jason.thomson@mintel.com) Message-ID: <41F7BC9F.9040905@mintel.com> Date: Wed, 26 Jan 2005 15:51:59 +0000 From: Jason Thomson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en, en-us MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.28 (www . roaringpenguin . com / mimedefang) cc: Vinod Kashyap Subject: 3ware 9500S problem in newly updated 4.x box. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Jan 2005 15:52:02 -0000 Recently CVSupped and rebuilt a releng4 box. This box has a 9500S in RAID10 configuration. On reboot, it failed to find da0, so it couldn't mount root. If you wait a few seconds, and then type to specify the root filesystem again, then the da0 device is found (the message is printed as you type), and on hitting return, the machine continues booting. (See dmesg below). The twa driver and firmware are up to date. This is a DELL 1600SC SMP. HyperThreading is enabled (but it's not a big deal to us one way or the other, so if it's a good idea to turn it off, we could). If you don't type on the keyboard, then the message doesn't appear. I haven't tried this without SMP. It's a production box I just upgraded, and can only mess around with it early in the morning. Before today, it was running FreeBSD 4-STABLE from September 24th. Has anyone else seen this? Does anyone have any ideas? Is there anything I can try to debug this? Copyright (c) 1992-2005 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 4.11-STABLE #3: Wed Jan 26 14:03:18 GMT 2005 jason@baldrick.mintel.co.uk:/usr/obj/usr/src/sys/BALDRICK Timecounter "i8254" frequency 1193182 Hz CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2790.72-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 3757965312 (3669888K bytes) avail memory = 3659362304 (3573596K bytes) Changing APIC ID for IO APIC #0 from 0 to 8 on chip Changing APIC ID for IO APIC #1 from 0 to 9 on chip Changing APIC ID for IO APIC #2 from 0 to 10 on chip Programming 16 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 Programming 16 pins in IOAPIC #1 Programming 16 pins in IOAPIC #2 FreeBSD/SMP: Multiprocessor motherboard: 4 CPUs cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00050014, at 0xfee00000 cpu2 (AP): apic id: 6, version: 0x00050014, at 0xfee00000 cpu3 (AP): apic id: 7, version: 0x00050014, at 0xfee00000 io0 (APIC): apic id: 8, version: 0x000f0011, at 0xfec00000 io1 (APIC): apic id: 9, version: 0x000f0011, at 0xfec01000 io2 (APIC): apic id: 10, version: 0x000f0011, at 0xfec02000 pnpbios: Bad PnP BIOS data checksum Preloaded elf kernel "kernel" at 0xa03f0000. Warning: Pentium 4 CPU: PSE disabled Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 9 entries at 0xa00fc200 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard IOAPIC #1 intpin 0 -> irq 2 IOAPIC #1 intpin 9 -> irq 3 pci0: on pcib0 em0: port 0xecc0-0xecff mem 0xfe100000-0xfe11ffff irq 2 at device 2.0 on pci0 em0: Speed:N/A Duplex:N/A sis0: port 0xe800-0xe8ff mem 0xfe122000-0xfe122fff irq 3 at device 4.0 on pci0 sis0: Ethernet address: 00:02:e3:02:6e:10 miibus0: on sis0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci0: at 14.0 atapci0: port 0x8b0-0x8bf,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 15.2 irq 5 isab0: at device 15.3 on pci0 isa0: on isab0 pcib1: on motherboard IOAPIC #1 intpin 4 -> irq 10 pci1: on pcib1 3ware device driver for 9000 series storage controllers, version: 2.40.02.011 twa0: <3ware 9000 series Storage Controller> port 0xdc00-0xdcff mem 0xfc000000-0xfc7fffff,0xfcf00000-0xfcf000ff irq 10 at device 6.0 on pci1 twa0: 4 ports, Firmware FE9X 2.04.00.005, BIOS BE9X 2.03.01.047 pcib2: on motherboard pci2: on pcib2 pcib3: on motherboard pci3: on pcib3 pcib4: on motherboard pci4: on pcib4 orm0: