From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 03:51:44 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A79CB16A420; Sun, 30 Oct 2005 03:51:44 +0000 (GMT) (envelope-from vkushnir@i.kiev.ua) Received: from horse.iptelecom.net.ua (horse.iptelecom.net.ua [212.9.224.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id A909F43D46; Sun, 30 Oct 2005 03:51:43 +0000 (GMT) (envelope-from vkushnir@i.kiev.ua) Received: from h54.241.159.dialup.iptcom.net ([213.159.241.54]:39366 "EHLO kushnir1.kiev.ua" ident: "SOCKFAULT1" whoson: "vkushnir") by horse.iptelecom.net.ua with ESMTP id S1219346AbVJ3Dvl (ORCPT + 1 other); Sun, 30 Oct 2005 05:51:41 +0200 Received: from kushnir1.kiev.ua (kushnir1.kiev.ua [10.0.0.1]) by kushnir1.kiev.ua (8.13.4/8.13.3) with ESMTP id j9U3paMq030741; Sun, 30 Oct 2005 05:51:36 +0200 (EET) (envelope-from vkushnir@i.kiev.ua) Date: Sun, 30 Oct 2005 05:51:36 +0200 (EET) From: Vladimir Kushnir X-X-Sender: vkushnir@kushnir1.kiev.ua To: John Baldwin In-Reply-To: <200510281404.33462.jhb@freebsd.org> Message-ID: <20051030052435.J646@kushnir1.kiev.ua> References: <20051027022313.R675@kushnir1.kiev.ua> <43602F2F.7080500@samsco.org> <200510281404.33462.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 03:51:44 -0000 OK, here it is. It's happened between 2005.10.21.19.42.50 and 2005.10.22.05.07.00. Since then, panic is absolutely reproducible. Regards, Vladimir From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 06:25:11 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A30916A420; Sun, 30 Oct 2005 06:25:11 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [65.170.254.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E21743D45; Sun, 30 Oct 2005 06:25:08 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mortis.over-yonder.net (adsl-152-91-180.jan.bellsouth.net [70.152.91.180]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id 22F6A2A; Sun, 30 Oct 2005 01:25:08 -0500 (CDT) Received: by mortis.over-yonder.net (Postfix, from userid 100) id 5B27920FFE; Sun, 30 Oct 2005 01:25:06 -0500 (CDT) Date: Sun, 30 Oct 2005 01:25:05 -0500 From: "Matthew D. Fuller" To: John Baldwin Message-ID: <20051030062505.GA1367@over-yonder.net> References: <20051023044115.7050216A421@hub.freebsd.org> <200510251521.03036.jhb@freebsd.org> <20051025224508.GB74484@over-yonder.net> <200510261321.50623.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200510261321.50623.jhb@freebsd.org> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.9i-fullermd.2 Cc: freebsd-current@freebsd.org Subject: Re: The case of the missing USB controllers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 06:25:11 -0000 On Wed, Oct 26, 2005 at 01:21:49PM -0400 I heard the voice of John Baldwin, and lo! it spake thus: > > > > 2) Does it work ok if you disable APIC? > > > > > > 3) Do you have a verbose dmesg and mptable output available > > > somewhere? > > > > mptable -verbose attached. The dmesg will probably have to wait > > for the weekend; I really hate losing my state :| > > Ok. I kind of need both of them to make sense of things, but I can > wait, no rush. OK. Here we go. I updated another box to this afternoon's RELENG_4, and tried both a GENERIC[0] kernel, and a GENERIC+SMP+APIC[1]. I also booted my current -CURRENT kernel (~Oct 1) with APIC disabled[2] and normal[3]. Note the minor difference that for the RELENG_4 boots I had to enable the ATA controller, which is normally disabled. With the non-APIC/SMP, on both 4 and 7, the [onboard] USB worked. It took interrupts, the mouse responded. Unplugging and replugging it worked just fine. With APIC/SMP, on both 4 and 7, it failed to work and never took an interrupt. Note in the 4.smp dmesg there's a "No debugger in kernel" line where I Ctrl-Alt-Esc'd, right between the CPU1 launch and the uhub0 SET_ADDR_FAILED. It froze there for a long time (minute+). That same message comes up in 7 when I try to hotplug stuff; it shuts off power to that port, and so it won't probe anything plugged in after boot. Stuff plugged in at boot stays powered up, though (so at least I get to play with the LED on the mouse ;). But on 4 it didn't last that long. In none of the 4 combinations did the USB2 card (Adaptec AUA-4000, the package says) probe at all, other than perhaps in the bus enumeration (vendor 0x9004==Adaptec? There's 2 2940's in other PCI slots, so that sounds right). So, without the APIC, it seems to work well enough. Unfortunately, with this staggering CPU muscle, I can't really afford to lose half my processing power, even to get away from a terrifyingly nasty RS232 serial mouse... [0] [1] [2] [3] -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 06:39:37 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 11ABE16A422; Sun, 30 Oct 2005 06:39:36 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <43646AAC.2080107@freebsd.org> Date: Sun, 30 Oct 2005 14:39:40 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.10) Gecko/20050806 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <30595.1130493297@critter.freebsd.dk> <20051028153457.d0wqgn2ask4sgw4k@netchild.homeip.net> <20051029195703.GB39253@dragon.NUXI.org> In-Reply-To: <20051029195703.GB39253@dragon.NUXI.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Leidinger Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 06:39:37 -0000 David O'Brien wrote: >On Fri, Oct 28, 2005 at 03:34:57PM +0200, Alexander Leidinger wrote: > > >>I don't have the message at hand. I just had time to write the mail, but I >>don't have my laptop with me to reproduce the message. But it's easy to >>reproduce, just take a PC which is able to make use of powerd and switch to >>using TSC as the timecounter. >> >> > >What is the motivation to use the TSC as a timecounter? > > > TSC is faster than any others, on many systems, so-called ACPI-fast timer is really a slow chip, at least far slower than reading from RAM, manufactories just lie on this. Regards, David Xu From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 07:39:18 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 65C9616A41F for ; Sun, 30 Oct 2005 07:39:18 +0000 (GMT) (envelope-from chad@shire.net) Received: from hobbiton.shire.net (hobbiton.shire.net [166.70.252.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA6A243D49 for ; Sun, 30 Oct 2005 07:39:16 +0000 (GMT) (envelope-from chad@shire.net) Received: from [67.161.222.227] (helo=[192.168.99.68]) by hobbiton.shire.net with esmtpa (Exim 4.51) id 1EW7md-000DbZ-Pf; Sun, 30 Oct 2005 01:39:15 -0600 In-Reply-To: <200510191623.j9JGNSfr007356@magus.nostrum.com> References: <200510191623.j9JGNSfr007356@magus.nostrum.com> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: "Chad Leigh -- Shire.Net LLC" Date: Sun, 30 Oct 2005 01:39:14 -0600 To: Philip Kizer X-Mailer: Apple Mail (2.734) X-SA-Exim-Connect-IP: 67.161.222.227 X-SA-Exim-Mail-From: chad@shire.net X-SA-Exim-Scanned: No (on hobbiton.shire.net); SAEximRunCond expanded to false Cc: freebsd-current@freebsd.org Subject: Re: Problem remains with FreeBSD 6.0-RC1 as seen in RELENG_5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 07:39:18 -0000 On Oct 19, 2005, at 10:23 AM, Philip Kizer wrote: > I have a problem I reported on freebsd-stable several weeks ago in: > > http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=47770+187449+/usr/ > local/www/db/text/2005/freebsd-stable/20051009.freebsd-stable > > > I upgraded a test box to see if all of the reports were true that > threading > and most other major problems were better in the 6.x branch, but I > have had > the same kind of hangs with 6.0-RC1 that I was having with RELENG_5. > > I get notified that some of my services are unavailable and I > verify that > new connection attempts from remote just hang. Attempts at issuing > commands from my existing ssh connections will let me send a > and > see a new prompt generated, but any attempt at execing/etc will > then hang > that process. > > > Moving to the console, I get the same behaviour such that if it is > already > logged in, I can hit return in the shell and get a new shell > prompt, but > any command I try (i.e. 'uptime' or 'uname') then results in the > same lack > of any further response. [Though, obviously from below, sending a > break to > activate DDB still works.] > > If the console is not already logged in and I hit return at > "login:", I get > a new "login:" prompt; but, as soon as I enter a username+^M or > even Ctrl-D > it, I cease to receive any feedback besides terminal echo from my > input. > I won't be much help in debugging this, but one of my main production servers was having this exact set of symptoms (all of them), about once a month. It started with 5.3-REL (happened once with 5.3-REL right as I was getting ready to upgrade to 5.4-REL after several months of running -- during a bunch of "dump" commands to files of md based filesystems). Happened several times, about every 2-6 weeks, until I upgraded to 5.4-STABLE a few weeks ago. Has not happened since but I am not sure it was "fixed." One interesting thing: When it would happen, I would have to do a hard boot by pushing the reset button. The problem would happen 2 or 3 more times after rebooting within 10-20 minutes of finishing the boot (and would have to be hard reset each time), then would no longer happen for 2-6 weeks. The machine is a Tyan 2882 dual Opteron running the i386 version of FreeBSD and has an Adaptec 2200S controller (aac). One time I saw an aac error on the console but usually not. It has lots of md based file systems mounted (disk backed). Has many jails mostly all running out of the md filesystems. Except for ssh, has no services running on the base install -- everything happens inside a jail. I will try and contribute but this is a major production machine and cannot be screwed around with until such time as an upgrade or planned reboot happens or the problem happens and we have to reboot anyway. # uname -a FreeBSD bywater.shire.net 5.4-STABLE FreeBSD 5.4-STABLE #7: Sun Oct 2 13:27:37 MDT 2005 chad@bywater.shire.net:/usr/obj/usr/src/sys/ BYWATER-SMP i386 Thanks Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad@shire.net From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 07:57:28 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D978916A41F; Sun, 30 Oct 2005 07:57:28 +0000 (GMT) (envelope-from stefan@snowfall.se) Received: from mail.snowfall.se (pluring.snowfallnet.com [82.99.34.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FB4343D46; Sun, 30 Oct 2005 07:57:27 +0000 (GMT) (envelope-from stefan@snowfall.se) Received: from [192.168.0.100] (c-1785e253.02-332-7570701.cust.bredbandsbolaget.se [83.226.133.23]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.snowfall.se (Postfix) with ESMTP id 7B2D874; Sun, 30 Oct 2005 08:57:25 +0100 (CET) Message-ID: <43647CE6.1080703@snowfall.se> Date: Sun, 30 Oct 2005 08:57:26 +0100 From: Stefan Cars User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stefan Cars References: <434CBAD5.10306@snowfall.se> <20051013010014.GG49168@wantadilla.lemis.com> <434E839B.2020209@snowfall.se> <20051014001038.GX49168@wantadilla.lemis.com> <4363DA8D.7000204@snowfall.se> In-Reply-To: <4363DA8D.7000204@snowfall.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Greg 'groggy' Lehey , current@freebsd.org Subject: Re: MySQL crashes on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 07:57:29 -0000 Stefan Cars wrote: > Greg 'groggy' Lehey wrote: > >> [Sequence recovered--see http://www.lemis.com/email/email-format.html] >> >> On Thursday, 13 October 2005 at 17:56:11 +0200, Stefan Cars wrote: >> >>> Greg 'groggy' Lehey wrote: >>> >>>> On Wednesday, 12 October 2005 at 9:27:17 +0200, Stefan Cars wrote: >>>> >>>> >>>>> Hi! >>>>> >>>>> We are having troubles with MySQL 4.1 on a amd64 (it's crashing >>>>> randomly with Seg fault, signal 11. gdb bt says: Cannot access >>>>> memory at address 0x800000000000). We have got information saying >>>>> this is a 64bit related issue and should be fixed by using the i386 >>>>> version instead of amd64 (this is an Intel Xeon). >>>> >>>> >>>> Where did you get that information from? >> >> >> >> I'd still like to know an answer to this question. > > > I got information from a guy working on the floor below us, although his > thoughts were only that "amd64 is a bit unstable so that should be the > problem" > >> >> >>>>> What is the way to go when moving from amd64 to i386 ? >>>> >>>> >>>> If you mean "how do I install an i386 kernel on this machine", I can't >>>> think of any way except to start from scratch. It would be a good >>>> idea to install a separate disk, so you can access the configuration >>>> files and the database on the old disk. But before doing this, I'd be >>>> very interested in knowing what the problem is. Is the backtrace >>>> always the same? Where does it crash? >>> >>> >>> After doing some testing this is what I found out: >>> >>> 1) Exchanging memory on the machine did not work. Same error. >>> 2) Trying it on another 64 bit machine with same FreeBSD (RC1) creates >>> EXACT same problem >>> 3) Installing the i386 version of RC1 instead of amd64 on the same >>> machines and it works terrific. No crash. >> >> >> >> Hmm. That's interesting. This is obviously not a hardware issue. >> >> >>> The bt is always the same and it always crash the same, look here: >>> >>> #784 0x0000000000000000 in ?? () >>> #785 0x247c8d48002454ff in ?? () >>> #786 0x01a1c0c748006a10 in ?? () >>> #787 0x66fdebf4050f0000 in ?? () >>> #788 0x9066669066669066 in ?? () >>> #789 0x00007fffffffe778 in ?? () >>> #790 0x0000000000000006 in ?? () >>> #791 0x00007fffffffe7b0 in ?? () >>> #792 0x0000000000000017 in ?? () >>> Cannot access memory at address 0x800000000000 >> >> >> >> Without function names instead of ??, it's impossible to say what's >> happening here. You'd need to build with debug symbols. >> >> Since you've been told that this is an issue, it would be good to know >> more. As we've mentioned on other threads, there are reasons to >> believe that there are problems with the threading libraries, but >> currently we don't have enough information to investigate them. Note >> that the other recent thread refers to problems running in the >> configuration you have just installed: see >> http://bugs.mysql.com/bug.php?id=12251 for more details. If you see >> anything similar, please let us know. >> > > > After doing alot of testing and trying this is some more new information: > > It actually DO crash on i386 FreeBSD 6.0-RC1 aswell, but very seldom > (around once every 4-5th hour, this time we get a Signal 10 instead, see > below). The errors are reproducable for MySQL 4.1.15 and MySQL 5.0.15 so > the problem still exists on 5.0.15. Of course we have tried on different > machines aswell to make sure it's not hardware related. On a FreeBSD > 5.3 machine Mysql 4.1.15 works fine. > > > mysqld got signal 10; > This could be because you hit a bug. It is also possible that this binary > or one of the libraries it was linked against is corrupt, improperly built, > or misconfigured. This error can also be caused by malfunctioning hardware. > We will try our best to scrape up some info that will hopefully help > diagnose > the problem, but since we have already crashed, something is definitely > wrong > and this may fail. > > key_buffer_size=1048576 > read_buffer_size=131072 > max_used_connections=99 > max_connections=400 > threads_connected=44 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections > = 461820 K > bytes of memory > Hope that's ok; if not, decrease some variables in the equation. Adding to this, using the following in libmap.conf fixes the problems: libpthread.so libthr.so libpthread.so.1 libthr.so.2 libpthread.so.2 libthr.so.2 From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 08:23:14 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6748716A41F for ; Sun, 30 Oct 2005 08:23:14 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25C0A43D46 for ; Sun, 30 Oct 2005 08:23:14 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 034081A3C25; Sun, 30 Oct 2005 01:23:14 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8474B51BF0; Sun, 30 Oct 2005 03:23:12 -0500 (EST) Date: Sun, 30 Oct 2005 03:23:11 -0500 From: Kris Kennaway To: "Chad Leigh -- Shire.Net LLC" Message-ID: <20051030082309.GA83399@xor.obsecurity.org> References: <200510191623.j9JGNSfr007356@magus.nostrum.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: Problem remains with FreeBSD 6.0-RC1 as seen in RELENG_5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 08:23:14 -0000 --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 30, 2005 at 01:39:14AM -0600, Chad Leigh -- Shire.Net LLC wrote: > I will try and contribute but this is a major production machine and =20 > cannot be screwed around with until such time as an upgrade or =20 > planned reboot happens or the problem happens and we have to reboot =20 > anyway. You need to configure DDB, and when the hang occurs, break to DDB on the console and trigger a dump (see the chapter on kernel debugging in the developers' handbook). A developer may then be able to begin to help you. Kris --envbJBWh7q8WU6mo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDZILsWry0BWjoQKURArOWAJ9GNS3WoZVHSH0/qiri0EKwMzdI+gCgzjaG oQuD6RMDomykXBleIKatgow= =vJDN -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 09:37:20 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D238016A41F; Sun, 30 Oct 2005 09:37:20 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75ED543D45; Sun, 30 Oct 2005 09:37:20 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.4/8.13.4) with ESMTP id j9U9bJO5043252; Sun, 30 Oct 2005 01:37:19 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id j9U9bIkX043251; Sun, 30 Oct 2005 01:37:18 -0800 (PST) (envelope-from obrien) Date: Sun, 30 Oct 2005 01:37:18 -0800 From: "David O'Brien" To: David Xu Message-ID: <20051030093718.GE39253@dragon.NUXI.org> Mail-Followup-To: freebsd-current@freebsd.org, David Xu , Alexander Leidinger References: <30595.1130493297@critter.freebsd.dk> <20051028153457.d0wqgn2ask4sgw4k@netchild.homeip.net> <20051029195703.GB39253@dragon.NUXI.org> <43646AAC.2080107@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43646AAC.2080107@freebsd.org> X-Operating-System: FreeBSD 7.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i Cc: Alexander Leidinger , freebsd-current@freebsd.org Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 09:37:20 -0000 On Sun, Oct 30, 2005 at 02:39:40PM +0800, David Xu wrote: > David O'Brien wrote: > >On Fri, Oct 28, 2005 at 03:34:57PM +0200, Alexander Leidinger wrote: > >>I don't have the message at hand. I just had time to write the mail, but I > >>don't have my laptop with me to reproduce the message. But it's easy to > >>reproduce, just take a PC which is able to make use of powerd and switch > >>to > >>using TSC as the timecounter. > > > >What is the motivation to use the TSC as a timecounter? > > TSC is faster than any others, on many systems, so-called ACPI-fast > timer is really a slow chip, Correct, but why is it felt the latency of the ACPI timer is an issue? Of course we all want things to as fast as possible, but is that just an abstract desire, or a real issue was run into? -- -- David (obrien@FreeBSD.org) From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 09:40:10 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C978616A41F for ; Sun, 30 Oct 2005 09:40:10 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5697643D45 for ; Sun, 30 Oct 2005 09:40:09 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id AAAFF1FFACC for ; Sun, 30 Oct 2005 10:40:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 1E34F1FFACA; Sun, 30 Oct 2005 10:40:05 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id AEBED157F2; Sun, 30 Oct 2005 09:37:54 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id A48361538C for ; Sun, 30 Oct 2005 09:37:54 +0000 (UTC) Date: Sun, 30 Oct 2005 09:37:54 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: FreeBSD current mailing list Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: Subject: LOR on kldunload nve/radix node head (v6?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 09:40:10 -0000 Hi, upon kldunload if_nve I got this. I added it with LOR ID # 166: http://sources.zabbadoz.net/freebsd/lor.html#166 lock order reversal: 1st 0xffffff00009a7180 nve0 (network driver) @ sys/modules/nve/../../dev/nve/if_nve.c:674 2nd 0xffffff0000b234f0 radix node head (radix node head) @ sys/net/route.c:148 KDB: stack backtrace: kdb_backtrace() at kdb_backtrace+0x37 witness_checkorder() at witness_checkorder+0x6f2 _mtx_lock_flags() at _mtx_lock_flags+0x7a rtalloc1() at rtalloc1+0x94 in6_ifremloop() at in6_ifremloop+0x6d in6_purgeaddr() at in6_purgeaddr+0x8b if_purgeaddrs() at if_purgeaddrs+0xba if_detach() at if_detach+0x31 ether_ifdetach() at ether_ifdetach+0x79 nve_detach() at nve_detach+0x240 device_detach() at device_detach+0x85 devclass_delete_driver() at devclass_delete_driver+0xb7 driver_module_handler() at driver_module_handler+0xec module_unload() at module_unload+0x56 linker_file_unload() at linker_file_unload+0x93 kern_kldunload() at kern_kldunload+0xa2 kldunloadf() at kldunloadf+0x19 syscall() at syscall+0x350 Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (444, FreeBSD ELF64, kldunloadf), rip = 0x800678c9c, rsp = 0x7fffffffe4d8, rbp = 0x7fffffffe980 --- -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 10:02:28 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 3A94D16A41F; Sun, 30 Oct 2005 10:02:28 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <436499B8.8000304@freebsd.org> Date: Sun, 30 Oct 2005 18:00:24 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.10) Gecko/20050806 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <30595.1130493297@critter.freebsd.dk> <20051028153457.d0wqgn2ask4sgw4k@netchild.homeip.net> <20051029195703.GB39253@dragon.NUXI.org> <43646AAC.2080107@freebsd.org> <20051030093718.GE39253@dragon.NUXI.org> In-Reply-To: <20051030093718.GE39253@dragon.NUXI.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Leidinger Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 10:02:28 -0000 David O'Brien wrote: >>TSC is faster than any others, on many systems, so-called ACPI-fast >>timer is really a slow chip, >> >> > >Correct, but why is it felt the latency of the ACPI timer is an issue? >Of course we all want things to as fast as possible, but is that just an >abstract desire, or a real issue was run into? > > > mysql benchmark - supersmack already told us this is an issue, this is the reason why mysql runs slower on FreeBSD than on Linux: ACPI-fast timecounter: alona# super-smack ./select-key-local.smack 10 1000 Query Barrel Report for client smacker1 connect: max=4ms min=3ms avg= 3ms from 10 clients Query_type num_queries max_time min_time q_per_s select_index 20000 1 0 7210.39 TSC timecounter: alona# super-smack ./select-key-local.smack 10 1000 Query Barrel Report for client smacker1 connect: max=3ms min=2ms avg= 2ms from 10 clients Query_type num_queries max_time min_time q_per_s select_index 20000 0 0 9301.19 From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 13:32:49 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8106616A41F; Sun, 30 Oct 2005 13:32:49 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id D64E843D46; Sun, 30 Oct 2005 13:32:48 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.5/8.13.5/NETPLEX) with ESMTP id j9UDWlZB011510; Sun, 30 Oct 2005 08:32:47 -0500 (EST) Date: Sun, 30 Oct 2005 08:32:47 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Stefan Cars In-Reply-To: <43647CE6.1080703@snowfall.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: Greg 'groggy' Lehey , current@freebsd.org Subject: Re: MySQL crashes on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 13:32:49 -0000 On Sun, 30 Oct 2005, Stefan Cars wrote: > > Adding to this, using the following in libmap.conf fixes the problems: > > libpthread.so libthr.so > libpthread.so.1 libthr.so.2 > libpthread.so.2 libthr.so.2 If you need both of those, then you're using multiple versions of libpthread in the same application. You need to rebuild everything mysql depends on, most likely all ports or you will have problems elsewhere. If you think you have done this, then move libpthread.so.1 out of the way and see if you have any problems. -- DE From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 13:46:08 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA90916A41F; Sun, 30 Oct 2005 13:46:08 +0000 (GMT) (envelope-from stefan@snowfall.se) Received: from mail.snowfall.se (pluring.snowfallnet.com [82.99.34.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 443B443D46; Sun, 30 Oct 2005 13:46:07 +0000 (GMT) (envelope-from stefan@snowfall.se) Received: from [10.16.193.66] (gprs2.vodafone.se [217.174.67.69]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.snowfall.se (Postfix) with ESMTP id 21A001D; Sun, 30 Oct 2005 14:46:02 +0100 (CET) Message-ID: <4364CE95.9030107@snowfall.se> Date: Sun, 30 Oct 2005 14:45:57 +0100 From: Stefan Cars User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Eischen References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Greg 'groggy' Lehey , current@freebsd.org Subject: Re: MySQL crashes on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 13:46:08 -0000 Hi No. I don't need both. Removed libpthread.so.1 and still the same problem. /S Daniel Eischen wrote: > On Sun, 30 Oct 2005, Stefan Cars wrote: > >>Adding to this, using the following in libmap.conf fixes the problems: >> >>libpthread.so libthr.so >>libpthread.so.1 libthr.so.2 >>libpthread.so.2 libthr.so.2 > > > If you need both of those, then you're using multiple versions > of libpthread in the same application. You need to rebuild > everything mysql depends on, most likely all ports or you will > have problems elsewhere. If you think you have done this, then > move libpthread.so.1 out of the way and see if you have any > problems. > From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 14:04:01 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00DC516A44B; Sun, 30 Oct 2005 14:04:01 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A9A643D45; Sun, 30 Oct 2005 14:04:00 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id j9UE3weH046223; Sun, 30 Oct 2005 07:03:58 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4364D2CD.6020406@samsco.org> Date: Sun, 30 Oct 2005 07:03:57 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Xu References: <30595.1130493297@critter.freebsd.dk> <20051028153457.d0wqgn2ask4sgw4k@netchild.homeip.net> <20051029195703.GB39253@dragon.NUXI.org> <43646AAC.2080107@freebsd.org> In-Reply-To: <43646AAC.2080107@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: Alexander Leidinger , freebsd-current@freebsd.org Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 14:04:01 -0000 David Xu wrote: > David O'Brien wrote: > >> On Fri, Oct 28, 2005 at 03:34:57PM +0200, Alexander Leidinger wrote: >> >> >>> I don't have the message at hand. I just had time to write the mail, >>> but I >>> don't have my laptop with me to reproduce the message. But it's easy to >>> reproduce, just take a PC which is able to make use of powerd and >>> switch to >>> using TSC as the timecounter. >>> >> >> >> What is the motivation to use the TSC as a timecounter? >> >> >> > TSC is faster than any others, on many systems, so-called ACPI-fast > timer is > really a slow chip, at least far slower than reading from RAM, > manufactories > just lie on this. > > Regards, > David Xu > Kind of. The TSC is internal to the CPU and can be read without any memory accesses or synchronization. The ACPI-faster counter needs to be read with an ioport instruction, which is exceedingly slow on modern hardware. ACPI-safe needs _three_ ioport reads. Scott From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 14:11:53 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 811EE16A41F; Sun, 30 Oct 2005 14:11:53 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2706A43D46; Sun, 30 Oct 2005 14:11:52 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id 02339BC50; Sun, 30 Oct 2005 14:11:45 +0000 (UTC) To: Scott Long From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sun, 30 Oct 2005 07:03:57 MST." <4364D2CD.6020406@samsco.org> Date: Sun, 30 Oct 2005 15:11:45 +0100 Message-ID: <50270.1130681505@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Alexander Leidinger , freebsd-current@freebsd.org, David Xu Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 14:11:53 -0000 In message <4364D2CD.6020406@samsco.org>, Scott Long writes: >ACPI-safe needs _three_ ioport reads. It's worse than that: s/needs/needs 3N (N >= 1)/ -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 14:30:41 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E13E16A41F; Sun, 30 Oct 2005 14:30:41 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E675843D45; Sun, 30 Oct 2005 14:30:40 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id j9UEUdAr049204; Sun, 30 Oct 2005 07:30:39 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4364D90F.3090205@samsco.org> Date: Sun, 30 Oct 2005 07:30:39 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <30595.1130493297@critter.freebsd.dk> <20051028153457.d0wqgn2ask4sgw4k@netchild.homeip.net> <20051029195703.GB39253@dragon.NUXI.org> <43646AAC.2080107@freebsd.org> <20051030093718.GE39253@dragon.NUXI.org> In-Reply-To: <20051030093718.GE39253@dragon.NUXI.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: Alexander Leidinger , David Xu Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 14:30:41 -0000 David O'Brien wrote: > On Sun, Oct 30, 2005 at 02:39:40PM +0800, David Xu wrote: > >>David O'Brien wrote: >> >>>On Fri, Oct 28, 2005 at 03:34:57PM +0200, Alexander Leidinger wrote: >>> >>>>I don't have the message at hand. I just had time to write the mail, but I >>>>don't have my laptop with me to reproduce the message. But it's easy to >>>>reproduce, just take a PC which is able to make use of powerd and switch >>>>to >>>>using TSC as the timecounter. >>> >>>What is the motivation to use the TSC as a timecounter? >> >>TSC is faster than any others, on many systems, so-called ACPI-fast >>timer is really a slow chip, > > > Correct, but why is it felt the latency of the ACPI timer is an issue? > Of course we all want things to as fast as possible, but is that just an > abstract desire, or a real issue was run into? > ACPI-fast requires an ioport read which takes about 1us (according to Google). Do that 1000 times a second and you have each CPU spending 1% of its time doing nothing but reading the clock. Yikes. Scott From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 16:19:16 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6285E16A41F for ; Sun, 30 Oct 2005 16:19:16 +0000 (GMT) (envelope-from kirk@strauser.com) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF39743D4C for ; Sun, 30 Oct 2005 16:19:15 +0000 (GMT) (envelope-from kirk@strauser.com) Received: from localhost (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id 4A7A421FFFE for ; Sun, 30 Oct 2005 10:19:14 -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 66770-19 for ; Sun, 30 Oct 2005 10:19:03 -0600 (CST) Received: from kanga.honeypot.net (unknown [IPv6:2001:470:1f01:224:1::2]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTP id ADBB621FF3A for ; Sun, 30 Oct 2005 10:19:03 -0600 (CST) From: Kirk Strauser To: freebsd-current@freebsd.org Date: Sun, 30 Oct 2005 10:18:56 -0600 User-Agent: KMail/1.8.2 References: <20051028045457.GA44396@polands.org> <20051028140301.X20147@fledge.watson.org> In-Reply-To: <20051028140301.X20147@fledge.watson.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2144255.DbIXRQx3Md"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200510301019.01843.kirk@strauser.com> X-Virus-Scanned: amavisd-new at honeypot.net Subject: Re: 6.0 and "options PREEMPTION" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 16:19:16 -0000 --nextPart2144255.DbIXRQx3Md Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 28 October 2005 08:04 am, Robert Watson wrote: > With the advent of "include" support in newer FreeBSD versions, I find I= =20 > generally have my own include file include GENERIC, then add=20 > nodevice/nooptions to remove things I don't want, and device/options to a= dd=20 > things I do want. =20 I'd like to move to such a setup, too. How do you disable the "cpu=20 I486_CPU" (etc.) lines from an included file? =2D-=20 Kirk Strauser --nextPart2144255.DbIXRQx3Md Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDZPJ15sRg+Y0CpvERAoigAJsFd7ESmGQOQwcCLverIp1FYg/pTACgn4el Pl5BUeW+KnEnAYjiCjUZHck= =RzWH -----END PGP SIGNATURE----- --nextPart2144255.DbIXRQx3Md-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 16:30:19 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A02016A41F for ; Sun, 30 Oct 2005 16:30:19 +0000 (GMT) (envelope-from konfer@mikulas.com) Received: from s1.vhost.cz (s1.vhost.cz [82.208.27.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FF5A43D53 for ; Sun, 30 Oct 2005 16:30:09 +0000 (GMT) (envelope-from konfer@mikulas.com) Received: (qmail 30437 invoked by alias); 30 Oct 2005 17:30:08 +0100 Received: from unknown (HELO localhost) (127.10.10.10) by s1.vhost.cz with SMTP; 30 Oct 2005 17:30:08 +0100 Received: from unknown ([127.0.0.1]) by localhost (s1.vhost.cz [127.0.0.1]) (amavisd-new, port 10628) id 30093-04 for ; Sun, 30 Oct 2005 17:30:07 +0100 (CET) Received: from unknown (HELO ?195.122.218.78?) (jiri@mikulas.com@195.122.218.78) by s1.vhost.cz with AES256-SHA encrypted SMTP; 30 Oct 2005 17:30:07 +0100 Message-ID: <4364F50E.2040509@mikulas.com> Date: Sun, 30 Oct 2005 17:30:06 +0100 From: Jiri Mikulas User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051004) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at vhost.cz Cc: Subject: new ath_hal X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 16:30:19 -0000 Hello does anybody know if these cards (chipset) will be supported in new ath_hal, please ? Mini PCI Atheros: WNC CM10 miniPCI 5 GHz (AR5006X) http://www.i4shop.net/cz/iObchod/Catalog.asp?ca=1633&it=9398 or Atheros: AR5006X miniPCI 5 GHz (AR5414A) http://www.i4shop.net/cz/iObchod/Catalog.asp?ca=1633&it=9335 and when will be released the new HAL ? Thanks for reply. Jiri From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 17:04:38 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9576D16A41F for ; Sun, 30 Oct 2005 17:04:38 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C77343D46 for ; Sun, 30 Oct 2005 17:04:38 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.200] ([10.0.0.200]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j9UH4ZpU050035 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 30 Oct 2005 09:04:37 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <4364FD15.1040703@errno.com> Date: Sun, 30 Oct 2005 09:04:21 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050927) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jiri Mikulas References: <4364F50E.2040509@mikulas.com> In-Reply-To: <4364F50E.2040509@mikulas.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: new ath_hal X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 17:04:38 -0000 Jiri Mikulas wrote: > Hello > does anybody know if these cards (chipset) will be supported in new ath_hal, please ? > > Mini PCI Atheros: WNC CM10 miniPCI 5 GHz (AR5006X) > http://www.i4shop.net/cz/iObchod/Catalog.asp?ca=1633&it=9398 > > or > > Atheros: AR5006X miniPCI 5 GHz (AR5414A) > http://www.i4shop.net/cz/iObchod/Catalog.asp?ca=1633&it=9335 > > and when will be released the new HAL ? The new hal was "released" ~2 months ago. These parts are supported. No idea when it'll get committed. You can find the bits in www.freebsd.org/~sam; don't forget to apply the ath and net80211 patches. Sam From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 19:51:33 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5162C16A41F for ; Sun, 30 Oct 2005 19:51:33 +0000 (GMT) (envelope-from vincent@xtra-net.org) Received: from relay.xtra-net.org (cable-195-162-200-89.customer.tvd.be [195.162.200.89]) by mx1.FreeBSD.org (Postfix) with SMTP id 7968C43D62 for ; Sun, 30 Oct 2005 19:51:27 +0000 (GMT) (envelope-from vincent@xtra-net.org) Received: (qmail 78945 invoked from network); 30 Oct 2005 19:51:26 -0000 Received: from wbegna01.xtra-net.org (HELO WBEAW0001512) (192.168.1.20) by 0 with SMTP; 30 Oct 2005 19:51:26 -0000 From: "Vincent Blondel" To: Date: Sun, 30 Oct 2005 20:53:44 +0100 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0007_01C5DD94.047D5C70" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-MS-TNEF-Correlator: Importance: Normal X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Evolution 2.2.3 crash X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 19:51:33 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C5DD94.047D5C70 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hello all, I just finished compiling gnome2 (2.10) on my FreeBSD current (7.0) sytem. The whole system is currently compiled without any optimisation ( CFLAGS= -O -pipe , COPTFLAGS= -O -pipe) without any problem encountered. I created an account and when I try to configure the "Receiving Email" part, evolution crashes and this (text below) is what I see on the console. %/usr/X11R6/bin/evolution es menu class init adding hook target 'source' (evolution:59298): evolution-mail-WARNING **: couldn't get service : No provider available for protocol `' BBDB spinning up... (evolution:59298): Gtk-CRITICAL **: gtk_tree_sortable_set_sort_column_id: assertion `GTK_IS_TREE_SORTABLE (sortable)' failed (evolution:59298): Gtk-CRITICAL **: gtk_entry_set_text: assertion `text != NULL' failed (evolution:59298): Gtk-CRITICAL **: gtk_entry_set_text: assertion `text != NULL' failed Thanks to help me ... Regards, Vincent. ------=_NextPart_000_0007_01C5DD94.047D5C70-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 19:59:46 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E7CC16A41F; Sun, 30 Oct 2005 19:59:46 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0277D43D55; Sun, 30 Oct 2005 19:59:45 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id j9UJxfvq030607; Sun, 30 Oct 2005 11:59:41 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id j9UJxaFp030606; Sun, 30 Oct 2005 11:59:36 -0800 (PST) (envelope-from jmg) Date: Sun, 30 Oct 2005 11:59:36 -0800 From: John-Mark Gurney To: Scott Long Message-ID: <20051030195936.GZ4115@funkthat.com> Mail-Followup-To: Scott Long , freebsd-current@freebsd.org, Alexander Leidinger , David Xu References: <30595.1130493297@critter.freebsd.dk> <20051028153457.d0wqgn2ask4sgw4k@netchild.homeip.net> <20051029195703.GB39253@dragon.NUXI.org> <43646AAC.2080107@freebsd.org> <20051030093718.GE39253@dragon.NUXI.org> <4364D90F.3090205@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4364D90F.3090205@samsco.org> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: Alexander Leidinger , freebsd-current@freebsd.org, David Xu Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 19:59:46 -0000 Scott Long wrote this message on Sun, Oct 30, 2005 at 07:30 -0700: > >Correct, but why is it felt the latency of the ACPI timer is an issue? > >Of course we all want things to as fast as possible, but is that just an > >abstract desire, or a real issue was run into? > > > > ACPI-fast requires an ioport read which takes about 1us (according to > Google). Do that 1000 times a second and you have each CPU spending > 1% of its time doing nothing but reading the clock. Yikes. Math correction: .1%... 1us * 1000 = 1ms, 1ms = .001s, .001 * 100% = .1% -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 20:00:37 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C14D16A4CC for ; Sun, 30 Oct 2005 20:00:36 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1584D43D69 for ; Sun, 30 Oct 2005 20:00:21 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5FA81.dip.t-dialin.net [84.165.250.129]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id j9UJdgYZ084467; Sun, 30 Oct 2005 20:39:47 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from localhost (localhost [127.0.0.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id j9UL06t0005068; Sun, 30 Oct 2005 22:00:07 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (Andro-Beta.Leidinger.net [192.168.1.42]) by webmail.leidinger.net (Horde MIME library) with HTTP; Sun, 30 Oct 2005 22:00:06 +0100 Message-ID: <20051030220006.nz9hh788f4ock0o8@netchild.homeip.net> X-Priority: 3 (Normal) Date: Sun, 30 Oct 2005 22:00:06 +0100 From: Alexander Leidinger To: Nate Lawson References: <200510172310.j9HNAVPL013057@repoman.freebsd.org> <20051018094402.A29138@grasshopper.cs.duke.edu> <435501B9.4070401@samsco.org> <43553162.5040802@root.org> <20051020141023.0ejwdv4dss48wko0@netchild.homeip.net> <4357E137.5090703@root.org> <20051023121338.3e253c97@Magellan.Leidinger.net> <435BD088.30205@root.org> In-Reply-To: <435BD088.30205@root.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.3) / FreeBSD-4.11 X-Virus-Scanned: by amavisd-new Cc: current@freebsd.org Subject: Re: 1kHz noise from C3 sleep X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 20:00:37 -0000 Nate Lawson wrote: >>>> My laptop makes noises when being (more or less) idle (I think I enabled >>>> C3...). Does this mean I should try to change HZ? >>> >>> Sure, you can do it from a tunable (kern.hz I think), you don't >>> have to recompile. >> >> >> No, a HZ of 100 doesn't work, the laptop still makes noises. And it >> only has C2, no C3... > > > Change to C1 (which is just HLT). If it still makes noise, it's not > your C2 or C3 sleep. It's the C2 sleep. Any ideas? Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 You can no more win a war than you can win an earthquake. -- Jeannette Rankin From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 20:23:37 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C052A16A41F for ; Sun, 30 Oct 2005 20:23:37 +0000 (GMT) (envelope-from marcus@marcuscom.com) Received: from creme-brulee.marcuscom.com (creme-brulee.marcuscom.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4AE6A43D4C for ; Sun, 30 Oct 2005 20:23:37 +0000 (GMT) (envelope-from marcus@marcuscom.com) Received: from shumai.marcuscom.com (shumai.marcuscom.com [192.168.1.4]) by creme-brulee.marcuscom.com (8.13.4/8.13.4) with ESMTP id j9UKONDG089305; Sun, 30 Oct 2005 15:24:23 -0500 (EST) (envelope-from marcus@marcuscom.com) From: Joe Marcus Clarke To: Vincent Blondel In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-yuJli33bYuzjRkJJdUed" Organization: MarcusCom, Inc. Date: Sun, 30 Oct 2005 15:23:35 -0500 Message-Id: <1130703815.44162.18.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Cc: current@freebsd.org Subject: Re: Evolution 2.2.3 crash X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 20:23:37 -0000 --=-yuJli33bYuzjRkJJdUed Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2005-10-30 at 20:53 +0100, Vincent Blondel wrote: > Hello all, >=20 > I just finished compiling gnome2 (2.10) on my FreeBSD current (7.0) > sytem.=20 >=20 > The whole system is currently compiled without any optimisation ( > CFLAGS=3D -O -pipe , COPTFLAGS=3D -O -pipe) without any problem encounter= ed. >=20 > I created an account and when I try to configure the "Receiving > Email" part, evolution crashes and this (text below) is what I see on the > console. >=20 > %/usr/X11R6/bin/evolution > es menu class init > adding hook target 'source' >=20 > (evolution:59298): evolution-mail-WARNING **: couldn't get > service : No provider available for protocol `' >=20 > BBDB spinning up... >=20 > (evolution:59298): Gtk-CRITICAL **: > gtk_tree_sortable_set_sort_column_id: assertion `GTK_IS_TREE_SORTABLE > (sortable)' failed >=20 > (evolution:59298): Gtk-CRITICAL **: gtk_entry_set_text: > assertion `text !=3D NULL' failed >=20 > (evolution:59298): Gtk-CRITICAL **: gtk_entry_set_text: > assertion `text !=3D NULL' failed >=20 > Thanks to help me ... Known issue. See http://www.freebsd.org/gnome/docs/faq210.html#q5. Joe --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-yuJli33bYuzjRkJJdUed Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDZSvHb2iPiv4Uz4cRAhUsAKCkuAmN5UpqUK/HV9fGWQNLr1wlewCgoYfP +KbGnTFnaM0A2hZPI5KP74A= =oY6d -----END PGP SIGNATURE----- --=-yuJli33bYuzjRkJJdUed-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 20:41:21 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C424E16A420; Sun, 30 Oct 2005 20:41:21 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82EA543D46; Sun, 30 Oct 2005 20:41:21 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 66A5D1A3C28; Sun, 30 Oct 2005 12:41:21 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D9B5E512CE; Sun, 30 Oct 2005 15:41:20 -0500 (EST) Date: Sun, 30 Oct 2005 15:41:20 -0500 From: Kris Kennaway To: Stefan Cars Message-ID: <20051030204120.GB99588@xor.obsecurity.org> References: <4364CE95.9030107@snowfall.se> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3lcZGd9BuhuYXNfi" Content-Disposition: inline In-Reply-To: <4364CE95.9030107@snowfall.se> User-Agent: Mutt/1.4.2.1i Cc: Daniel Eischen , Greg 'groggy' Lehey , current@freebsd.org Subject: Re: MySQL crashes on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 20:41:21 -0000 --3lcZGd9BuhuYXNfi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 30, 2005 at 02:45:57PM +0100, Stefan Cars wrote: > Hi >=20 > No. I don't need both. Removed libpthread.so.1 and still the same problem. You removed the mapping entry, or the file itself? Daniel asked for the latter. Kris --3lcZGd9BuhuYXNfi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDZS/wWry0BWjoQKURAp+AAKDRNF4Lj7BTlvvK7I60WmoWbFGnjgCeOuV/ iH/qQ7i1FP/MmgiCGr4oAac= =dPiq -----END PGP SIGNATURE----- --3lcZGd9BuhuYXNfi-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 20:52:43 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C540416A41F; Sun, 30 Oct 2005 20:52:43 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D92043D46; Sun, 30 Oct 2005 20:52:43 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.5/8.13.5/NETPLEX) with ESMTP id j9UKqgve010205; Sun, 30 Oct 2005 15:52:42 -0500 (EST) Date: Sun, 30 Oct 2005 15:52:42 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Stefan Cars In-Reply-To: <20051030204120.GB99588@xor.obsecurity.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: Greg 'groggy' Lehey , current@freebsd.org, Kris Kennaway Subject: Re: MySQL crashes on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 20:52:43 -0000 On Sun, 30 Oct 2005, Kris Kennaway wrote: > On Sun, Oct 30, 2005 at 02:45:57PM +0100, Stefan Cars wrote: > > Hi > > > > No. I don't need both. Removed libpthread.so.1 and still the same problem. > > You removed the mapping entry, or the file itself? Daniel asked for > the latter. Or perhaps try using libmap.conf to map libpthread.so.1 to libpthread.so.2 without any other mappings: libpthread.so.1 libpthread.so.2 -- DE From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 20:56:03 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF5B016A41F; Sun, 30 Oct 2005 20:56:03 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BB0E43D45; Sun, 30 Oct 2005 20:56:03 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 6F3F91A3C25; Sun, 30 Oct 2005 12:56:03 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C895251337; Sun, 30 Oct 2005 15:56:02 -0500 (EST) Date: Sun, 30 Oct 2005 15:56:02 -0500 From: Kris Kennaway To: Daniel Eischen Message-ID: <20051030205602.GB201@xor.obsecurity.org> References: <20051030204120.GB99588@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XOIedfhf+7KOe/yw" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: Greg 'groggy' Lehey , Kris Kennaway , current@freebsd.org, Stefan Cars Subject: Re: MySQL crashes on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 20:56:03 -0000 --XOIedfhf+7KOe/yw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Oct 30, 2005 at 03:52:42PM -0500, Daniel Eischen wrote: > On Sun, 30 Oct 2005, Kris Kennaway wrote: >=20 > > On Sun, Oct 30, 2005 at 02:45:57PM +0100, Stefan Cars wrote: > > > Hi > > > > > > No. I don't need both. Removed libpthread.so.1 and still the same pro= blem. > > > > You removed the mapping entry, or the file itself? Daniel asked for > > the latter. >=20 > Or perhaps try using libmap.conf to map libpthread.so.1 to > libpthread.so.2 without any other mappings: >=20 > libpthread.so.1 libpthread.so.2 This is just a partial workaround, of course, and any of your binaries that are also linked to two versions of other libraries may still experience crashes (or may start to crash later when the new libraries change further). You really want to track down and fix the root cause now, to save you hours of pain later when the problem recurs elsewhere. Kris --XOIedfhf+7KOe/yw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDZTNiWry0BWjoQKURAoqqAJ9wquTF7G5BXiV/RSkWMpXc9MPKqACg4ZVC foKGY8wzpQFOIZT8WK4xMJk= =XE8w -----END PGP SIGNATURE----- --XOIedfhf+7KOe/yw-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 20:59:36 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A7DB16A41F for ; Sun, 30 Oct 2005 20:59:36 +0000 (GMT) (envelope-from vincent@xtra-net.org) Received: from relay.xtra-net.org (cable-195-162-200-89.customer.tvd.be [195.162.200.89]) by mx1.FreeBSD.org (Postfix) with SMTP id 699F643D48 for ; Sun, 30 Oct 2005 20:59:35 +0000 (GMT) (envelope-from vincent@xtra-net.org) Received: (qmail 79693 invoked from network); 30 Oct 2005 20:59:34 -0000 Received: from wbedllfs.xtra-net.org (192.168.1.21) by 0 with SMTP; 30 Oct 2005 20:59:34 -0000 From: Vincent Blondel To: current@freebsd.org In-Reply-To: <1130703815.44162.18.camel@shumai.marcuscom.com> References: <1130703815.44162.18.camel@shumai.marcuscom.com> Content-Type: text/plain Date: Sun, 30 Oct 2005 21:58:09 +0100 Message-Id: <1130705889.59492.2.camel@wbedllfs.xtra-net.org> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Subject: Re: Evolution 2.2.3 crash X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vincent@xtra-net.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 20:59:36 -0000 Thanks a lot, it is working now :) Vincent On Sun, 2005-10-30 at 15:23 -0500, Joe Marcus Clarke wrote: > On Sun, 2005-10-30 at 20:53 +0100, Vincent Blondel wrote: > > Hello all, > > > > I just finished compiling gnome2 (2.10) on my FreeBSD current (7.0) > > sytem. > > > > The whole system is currently compiled without any optimisation ( > > CFLAGS= -O -pipe , COPTFLAGS= -O -pipe) without any problem encountered. > > > > I created an account and when I try to configure the "Receiving > > Email" part, evolution crashes and this (text below) is what I see on the > > console. > > > > %/usr/X11R6/bin/evolution > > es menu class init > > adding hook target 'source' > > > > (evolution:59298): evolution-mail-WARNING **: couldn't get > > service : No provider available for protocol `' > > > > BBDB spinning up... > > > > (evolution:59298): Gtk-CRITICAL **: > > gtk_tree_sortable_set_sort_column_id: assertion `GTK_IS_TREE_SORTABLE > > (sortable)' failed > > > > (evolution:59298): Gtk-CRITICAL **: gtk_entry_set_text: > > assertion `text != NULL' failed > > > > (evolution:59298): Gtk-CRITICAL **: gtk_entry_set_text: > > assertion `text != NULL' failed > > > > Thanks to help me ... > > Known issue. See http://www.freebsd.org/gnome/docs/faq210.html#q5. > > Joe > From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 22:17:13 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9389816A41F; Sun, 30 Oct 2005 22:17:13 +0000 (GMT) (envelope-from vkushnir@i.kiev.ua) Received: from horse.iptelecom.net.ua (horse.iptelecom.net.ua [212.9.224.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B25F43D49; Sun, 30 Oct 2005 22:17:12 +0000 (GMT) (envelope-from vkushnir@i.kiev.ua) Received: from h111.242.159.dialup.iptcom.net ([213.159.242.111]:27367 "EHLO kushnir1.kiev.ua" ident: "SOCKFAULT1" whoson: "vkushnir") by horse.iptelecom.net.ua with ESMTP id S1219933AbVJ3WRK (ORCPT + 1 other); Mon, 31 Oct 2005 00:17:10 +0200 Received: from kushnir1.kiev.ua (kushnir1.kiev.ua [10.0.0.1]) by kushnir1.kiev.ua (8.13.4/8.13.3) with ESMTP id j9UMH7WA001244; Mon, 31 Oct 2005 00:17:07 +0200 (EET) (envelope-from vkushnir@i.kiev.ua) Date: Mon, 31 Oct 2005 00:17:07 +0200 (EET) From: Vladimir Kushnir X-X-Sender: vkushnir@kushnir1.kiev.ua To: freebsd-current@freebsd.org In-Reply-To: <20051030052435.J646@kushnir1.kiev.ua> Message-ID: <20051031000217.F636@kushnir1.kiev.ua> References: <20051027022313.R675@kushnir1.kiev.ua> <43602F2F.7080500@samsco.org> <200510281404.33462.jhb@freebsd.org> <20051030052435.J646@kushnir1.kiev.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 22:17:13 -0000 A bit further. On Sun, 30 Oct 2005, Vladimir Kushnir wrote: > OK, here it is. It's happened between 2005.10.21.19.42.50 and > 2005.10.22.05.07.00. > Since then, panic is absolutely reproducible. > Actually, when I took INET6 from kernel (once again, it's GENERIC) these panics stop. Regards, Vladimir From owner-freebsd-current@FreeBSD.ORG Sun Oct 30 23:19:45 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B9FB16A41F; Sun, 30 Oct 2005 23:19:45 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB66943D45; Sun, 30 Oct 2005 23:19:44 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j9UNG0Bq092535; Sun, 30 Oct 2005 16:16:00 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 30 Oct 2005 16:16:06 -0700 (MST) Message-Id: <20051030.161606.65680605.imp@bsdimp.com> To: gurney_j@resnet.uoregon.edu From: "M. Warner Losh" In-Reply-To: <20051030195936.GZ4115@funkthat.com> References: <20051030093718.GE39253@dragon.NUXI.org> <4364D90F.3090205@samsco.org> <20051030195936.GZ4115@funkthat.com> 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 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sun, 30 Oct 2005 16:16:09 -0700 (MST) Cc: Alexander@Leidinger.net, freebsd-current@FreeBSD.org, davidxu@FreeBSD.org Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Oct 2005 23:19:45 -0000 In message: <20051030195936.GZ4115@funkthat.com> John-Mark Gurney writes: : Scott Long wrote this message on Sun, Oct 30, 2005 at 07:30 -0700: : > >Correct, but why is it felt the latency of the ACPI timer is an issue? : > >Of course we all want things to as fast as possible, but is that just an : > >abstract desire, or a real issue was run into? : > > : > : > ACPI-fast requires an ioport read which takes about 1us (according to : > Google). Do that 1000 times a second and you have each CPU spending : > 1% of its time doing nothing but reading the clock. Yikes. : : Math correction: .1%... 1us * 1000 = 1ms, 1ms = .001s, .001 * 100% = .1% Actually, ioport reads can be faster than the 1us that's widely quoted. ioport reads can be as fast as ~125ns (2 cycles at 16MHz). However, experience has shown that they are rarely this fast. I've seen 8MB/s pio over the pci bus on some custom hardware we have, which 2Mreads/sec which is about 500ns per read. I think that the pci hardware that I was reading had a few extra wait states... The 1us/read is for devices on the ISA bus or for hardware that emulates this timing. Warner From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 00:37:06 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7EC2E16A41F; Mon, 31 Oct 2005 00:37:05 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <43656735.7080505@freebsd.org> Date: Mon, 31 Oct 2005 08:37:09 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.10) Gecko/20050806 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <20051030093718.GE39253@dragon.NUXI.org> <4364D90F.3090205@samsco.org> <20051030195936.GZ4115@funkthat.com> <20051030.161606.65680605.imp@bsdimp.com> In-Reply-To: <20051030.161606.65680605.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander@Leidinger.net, gurney_j@resnet.uoregon.edu, freebsd-current@FreeBSD.org Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 00:37:06 -0000 M. Warner Losh wrote: >Actually, ioport reads can be faster than the 1us that's widely >quoted. ioport reads can be as fast as ~125ns (2 cycles at 16MHz). >However, experience has shown that they are rarely this fast. I've >seen 8MB/s pio over the pci bus on some custom hardware we have, which >2Mreads/sec which is about 500ns per read. I think that the pci >hardware that I was reading had a few extra wait states... > >The 1us/read is for devices on the ISA bus or for hardware that >emulates this timing. > >Warner > > > > The ioport speed is also unstable, on my IBM T43 thinkpad notebook, if I load wireless driver, the gettimeofday syscall will be 4 times slower than no wireless driver loaded, though I am not using the wireless network. David Xu From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 06:31:57 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24DCB16A41F for ; Mon, 31 Oct 2005 06:31:57 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id C28AD43D46 for ; Mon, 31 Oct 2005 06:31:56 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.250] (ppp-71-139-0-107.dsl.snfc21.pacbell.net [71.139.0.107]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j9V6Vnxq011744 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 30 Oct 2005 22:31:55 -0800 Message-ID: <4365AC20.1090607@root.org> Date: Sun, 30 Oct 2005 21:31:12 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alexander Leidinger References: <200510172310.j9HNAVPL013057@repoman.freebsd.org> <20051018094402.A29138@grasshopper.cs.duke.edu> <435501B9.4070401@samsco.org> <43553162.5040802@root.org> <20051020141023.0ejwdv4dss48wko0@netchild.homeip.net> <4357E137.5090703@root.org> <20051023121338.3e253c97@Magellan.Leidinger.net> <435BD088.30205@root.org> <20051030220006.nz9hh788f4ock0o8@netchild.homeip.net> In-Reply-To: <20051030220006.nz9hh788f4ock0o8@netchild.homeip.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: 1kHz noise from C3 sleep X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 06:31:57 -0000 Alexander Leidinger wrote: > Nate Lawson wrote: > >>>>> My laptop makes noises when being (more or less) idle (I think I >>>>> enabled >>>>> C3...). Does this mean I should try to change HZ? >>>> >>>> >>>> Sure, you can do it from a tunable (kern.hz I think), you don't have >>>> to recompile. >>> >>> >>> >>> No, a HZ of 100 doesn't work, the laptop still makes noises. And it >>> only has C2, no C3... >> >> >> >> Change to C1 (which is just HLT). If it still makes noise, it's not >> your C2 or C3 sleep. > > > It's the C2 sleep. Any ideas? Try C3, different values of kern.hz. Or earplugs. -- Nate From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 07:22:56 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 582AF16A421 for ; Mon, 31 Oct 2005 07:22:56 +0000 (GMT) (envelope-from konfer@mikulas.com) Received: from s1.vhost.cz (s1.vhost.cz [82.208.27.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 585C743D46 for ; Mon, 31 Oct 2005 07:22:54 +0000 (GMT) (envelope-from konfer@mikulas.com) Received: (qmail 55605 invoked by alias); 31 Oct 2005 08:22:53 +0100 Received: from unknown (HELO localhost) (127.10.10.10) by s1.vhost.cz with SMTP; 31 Oct 2005 08:22:53 +0100 Received: from unknown ([127.0.0.1]) by localhost (s1.vhost.cz [127.0.0.1]) (amavisd-new, port 10628) id 53786-20; Mon, 31 Oct 2005 08:22:53 +0100 (CET) Received: from unknown (HELO ?195.122.218.78?) (jiri@mikulas.com@195.122.218.78) by s1.vhost.cz with AES256-SHA encrypted SMTP; 31 Oct 2005 08:22:52 +0100 Message-ID: <4365C64B.1040803@mikulas.com> Date: Mon, 31 Oct 2005 08:22:51 +0100 From: Jiri Mikulas User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051004) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sam Leffler References: <4364F50E.2040509@mikulas.com> <4364FD15.1040703@errno.com> In-Reply-To: <4364FD15.1040703@errno.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at vhost.cz Cc: current@freebsd.org Subject: Re: new ath_hal X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 07:22:56 -0000 Thaks :) Jiri Sam Leffler wrote: > Jiri Mikulas wrote: > >> Hello >> does anybody know if these cards (chipset) will be supported in new >> ath_hal, please ? >> >> Mini PCI Atheros: WNC CM10 miniPCI 5 GHz (AR5006X) >> http://www.i4shop.net/cz/iObchod/Catalog.asp?ca=1633&it=9398 >> >> or >> >> Atheros: AR5006X miniPCI 5 GHz (AR5414A) >> http://www.i4shop.net/cz/iObchod/Catalog.asp?ca=1633&it=9335 >> >> and when will be released the new HAL ? > > > The new hal was "released" ~2 months ago. These parts are supported. No > idea when it'll get committed. You can find the bits in > www.freebsd.org/~sam; don't forget to apply the ath and net80211 patches. > > Sam From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 07:58:52 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FDD016A41F; Mon, 31 Oct 2005 07:58:52 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EC7F43D46; Mon, 31 Oct 2005 07:58:51 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.4/8.13.4) with ESMTP id j9V7wmsB010818; Sun, 30 Oct 2005 23:58:49 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id j9V7whTP010805; Sun, 30 Oct 2005 23:58:43 -0800 (PST) (envelope-from obrien) Date: Sun, 30 Oct 2005 23:58:43 -0800 From: "David O'Brien" To: Scott Long Message-ID: <20051031075843.GF39253@dragon.NUXI.org> Mail-Followup-To: freebsd-current@freebsd.org, Scott Long , Alexander Leidinger , David Xu References: <30595.1130493297@critter.freebsd.dk> <20051028153457.d0wqgn2ask4sgw4k@netchild.homeip.net> <20051029195703.GB39253@dragon.NUXI.org> <43646AAC.2080107@freebsd.org> <20051030093718.GE39253@dragon.NUXI.org> <4364D90F.3090205@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4364D90F.3090205@samsco.org> X-Operating-System: FreeBSD 7.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i Cc: Alexander Leidinger , freebsd-current@freebsd.org, David Xu Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 07:58:52 -0000 On Sun, Oct 30, 2005 at 07:30:39AM -0700, Scott Long wrote: > David O'Brien wrote: > >On Sun, Oct 30, 2005 at 02:39:40PM +0800, David Xu wrote: > >>David O'Brien wrote: > >>>On Fri, Oct 28, 2005 at 03:34:57PM +0200, Alexander Leidinger wrote: > >>> > >>>>I don't have the message at hand. I just had time to write the mail, > >>>>but I > >>>>don't have my laptop with me to reproduce the message. But it's easy to > >>>>reproduce, just take a PC which is able to make use of powerd and > >>>>switch to > >>>>using TSC as the timecounter. > >>> > >>>What is the motivation to use the TSC as a timecounter? > >> > >>TSC is faster than any others, on many systems, so-called ACPI-fast > >>timer is really a slow chip, > > > >Correct, but why is it felt the latency of the ACPI timer is an issue? > >Of course we all want things to as fast as possible, but is that just an > >abstract desire, or a real issue was run into? > > ACPI-fast requires an ioport read which takes about 1us (according to > Google). Do that 1000 times a second and you have each CPU spending > 1% of its time doing nothing but reading the clock. Yikes. But we've lived with using the ACPI timercounter (vs. TSC) for quite a while now. Why all of a sudden are the authors of this thread having an issue with it now. I know about the recent MySQL thread - but with the TSC being untrustable on MP and power managed systems, why is there such a desire to use the TSC? -- -- David (obrien@FreeBSD.org) From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 08:24:02 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDC9816A41F; Mon, 31 Oct 2005 08:24:02 +0000 (GMT) (envelope-from delphij@frontfree.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [210.51.165.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33D5043D48; Mon, 31 Oct 2005 08:24:02 +0000 (GMT) (envelope-from delphij@frontfree.net) Received: from localhost (tarsier.geekcn.org [210.51.165.229]) by tarsier.geekcn.org (Postfix) with ESMTP id 3134AEB0FD5; Mon, 31 Oct 2005 16:24:00 +0800 (CST) Received: from tarsier.geekcn.org ([210.51.165.229]) by localhost (mail.geekcn.org [210.51.165.229]) (amavisd-new, port 10024) with ESMTP id 37929-20; Mon, 31 Oct 2005 16:23:53 +0800 (CST) Received: from beastie.frontfree.net (unknown [211.71.95.7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id 93BA4EB0FCE; Mon, 31 Oct 2005 16:23:52 +0800 (CST) Received: from localhost (localhost.frontfree.net [127.0.0.1]) by beastie.frontfree.net (Postfix) with ESMTP id 23CAD1322CB; Mon, 31 Oct 2005 16:23:45 +0800 (CST) Received: from beastie.frontfree.net ([127.0.0.1]) by localhost (beastie.frontfree.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22544-06; Mon, 31 Oct 2005 16:23:44 +0800 (CST) Received: from [10.217.12.68] (sina152-194.staff.sina.com.cn [61.135.152.194]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by beastie.frontfree.net (Postfix) with ESMTP id CA3B41322C3; Mon, 31 Oct 2005 16:23:43 +0800 (CST) From: Xin LI To: FreeBSD-Current Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-C8cxPlSduIB4hFKkGn+d" Organization: The FreeBSD Simplified Chinese Project Date: Mon, 31 Oct 2005 16:23:14 +0800 Message-Id: <1130746994.920.3.camel@spirit> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port X-Virus-Scanned: amavisd-new at frontfree.net X-Virus-Scanned: amavisd-new at geekcn.org Cc: Xin LI Subject: [PATCH FOR REVIEW] kqueue'ify inetd(8) and some cleanups X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 08:24:02 -0000 --=-C8cxPlSduIB4hFKkGn+d Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi, Here is a patchset that teaches inetd(8) to make use of kqueue: http://www.delphij.net/patchset/patch-inetd.diff It was derived from John-Mark's patch that was documented here: http://people.freebsd.org/~jmg/inetd.kq.html Cheers, --=20 Xin LI http://www.delphij.net/ --=20 Xin LI http://www.delphij.net/ --=-C8cxPlSduIB4hFKkGn+d Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDZdRy/cVsHxFZiIoRAvMoAKCQwJSHkOcyMrS7CAL++TvoAbxgBgCghFdx G7DRaC3yNnDO0tUH9kQRpUk= =jE53 -----END PGP SIGNATURE----- --=-C8cxPlSduIB4hFKkGn+d-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 09:26:13 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2AD3916A41F; Mon, 31 Oct 2005 09:26:13 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFCFF43D45; Mon, 31 Oct 2005 09:26:12 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id B435546B9B; Mon, 31 Oct 2005 04:26:11 -0500 (EST) Date: Mon, 31 Oct 2005 09:26:11 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: freebsd-current@freebsd.org In-Reply-To: <20051031075843.GF39253@dragon.NUXI.org> Message-ID: <20051031083447.Y11619@fledge.watson.org> References: <30595.1130493297@critter.freebsd.dk> <20051028153457.d0wqgn2ask4sgw4k@netchild.homeip.net> <20051029195703.GB39253@dragon.NUXI.org> <43646AAC.2080107@freebsd.org> <20051030093718.GE39253@dragon.NUXI.org> <4364D90F.3090205@samsco.org> <20051031075843.GF39253@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Alexander Leidinger , David Xu Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 09:26:13 -0000 On Sun, 30 Oct 2005, David O'Brien wrote: >> ACPI-fast requires an ioport read which takes about 1us (according to >> Google). Do that 1000 times a second and you have each CPU spending 1% >> of its time doing nothing but reading the clock. Yikes. > > But we've lived with using the ACPI timercounter (vs. TSC) for quite a > while now. Why all of a sudden are the authors of this thread having an > issue with it now. I know about the recent MySQL thread - but with the > TSC being untrustable on MP and power managed systems, why is there such > a desire to use the TSC? Because in the past few weeks, several developers have noticed that if you change timercounters from ACPI-fast to TSC, you get significant performance boosts on real-world workloads. Drew reported this a couple of weeks ago on net@ after looking at loopback network performance, and I suggested he frob the timecounter on his system, which resulted in a significant measured performance increase. Then recently it was reported that MySQL also saw a significant boost from faster timekeeping, as it performs frequent time measurement. So we have at least two interesting cases: (1) We perform time measurement in the kernel context switch code for every context switch. Using cheaper time measurement here can make a big different in performance for a broad range of workloads involving frequent context switches -- high interrupt rates, loopback or local IPC, etc. (2) Many applications measure the time in order to self-profile, measure network timeouts, etc; it's quite possible that self-instrumentation with frequent time measurements is increasing due to the relatively low cost of time measurement on Linux, which has the effect of significantly reducing FreeBSD performance, where time measurement is much more expensive. For example, it was reported that MySQL is measuring time with every IPC operation. It has been suggested that the former can operate quite well with significantly reduced quality. It has alos been suggested that most applications could operate fine with somewhat reduced quality, but that the API definitions don't say anything about how to specify application quality requirements vs performance requirements for time measurement. Some performance results for loopback TCP on a UP kernel attached below. In the default case, a 12.8% performance improvement on loopback TCP is observed by switching from ACPI fast to TSC. With local changes to disable some unwise preemptions, I'm able to improve performance by about 29%, and adding on top of that the TSC change, 35.2%. In the nopreempt case, I've reduced the number of context switches, so the effect of changing time counters is reduced, as there are fewer time measurements. In this scenario, the performance improvement from nopreempt to nopreempt.tsc is 4.7%. These are non-trivial performance changes. FYI: measured on SMP, moving to TSC for this benchmark gives a 4.9% improvement in the preempt case, and a 2.5% improvement in the nopreempt case. On SMP, the preemption changes I'm working with reduce performance rather than improving it, possibly because the effects of preemption are still cheaper than the effects of migration. Regardless, the timecounter change is significant, although less so than on UP. Robert N M Watson x preempt + preempt.tsc * nopreempt % nopreempt.tsc +--------------------------------------------------------------------------+ | xx + * %% | | xx + ** %% | | xx ++ ** %% | |x xx +++ * ** **** %%% %%%| | |_A_| |A |__AM_| |_AM_|| +--------------------------------------------------------------------------+ N Min Max Median Avg Stddev x 12 2123.5 2194.31 2186.03 2181.4983 19.144156 + 12 2444.03 2468.44 2463.22 2460.1725 6.5242305 Difference at 95.0% confidence 278.674 +/- 12.1092 12.7744% +/- 0.555084% (Student's t, pooled s = 14.3015) * 12 2750.12 2845.31 2829.98 2816.2325 31.188601 Difference at 95.0% confidence 634.734 +/- 21.9101 29.0962% +/- 1.00436% (Student's t, pooled s = 25.8769) % 12 2902.27 2979.3 2954.93 2949.0792 25.48312 Difference at 95.0% confidence 767.581 +/- 19.0828 35.1859% +/- 0.874755% (Student's t, pooled s = 22.5376) From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 10:18:35 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2AB6016A422; Mon, 31 Oct 2005 10:18:35 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E111B43D48; Mon, 31 Oct 2005 10:18:34 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j9VAIWS0004169; Mon, 31 Oct 2005 10:18:33 GMT (envelope-from davidxu@freebsd.org) Message-ID: <4365EF7B.1020706@freebsd.org> Date: Mon, 31 Oct 2005 18:18:35 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20050928 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: <30595.1130493297@critter.freebsd.dk> <20051028153457.d0wqgn2ask4sgw4k@netchild.homeip.net> <20051029195703.GB39253@dragon.NUXI.org> <43646AAC.2080107@freebsd.org> <20051030093718.GE39253@dragon.NUXI.org> <4364D90F.3090205@samsco.org> <20051031075843.GF39253@dragon.NUXI.org> <20051031083447.Y11619@fledge.watson.org> In-Reply-To: <20051031083447.Y11619@fledge.watson.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Leidinger , freebsd-current@freebsd.org Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 10:18:35 -0000 Robert Watson wrote: > > > It has been suggested that the former can operate quite well with > significantly reduced quality. It has alos been suggested that most > applications could operate fine with somewhat reduced quality, but that > the API definitions don't say anything about how to specify application > quality requirements vs performance requirements for time measurement. Can we change gettimeofday and clock_gettime to lower resolution now? I think 1000hz/s is enough for most applications, since a thread can never sleep shorter than a tick for years. We can introduce hrtime_t clock_gethrtime(clockid_t clock) to get hi-resolution time as the one seen in RTLinux, or gethrtime() as seen in Solaris (Daniel Eischen said?) David Xu From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 10:26:41 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEEC616A41F; Mon, 31 Oct 2005 10:26:41 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id D181043D49; Mon, 31 Oct 2005 10:26:40 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id AB805BC84; Mon, 31 Oct 2005 10:26:38 +0000 (UTC) To: David Xu From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 31 Oct 2005 18:18:35 +0800." <4365EF7B.1020706@freebsd.org> Date: Mon, 31 Oct 2005 11:26:38 +0100 Message-ID: <81213.1130754398@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Alexander Leidinger , freebsd-current@freebsd.org, Robert Watson Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 10:26:42 -0000 In message <4365EF7B.1020706@freebsd.org>, David Xu writes: >Robert Watson wrote: >> >> >> It has been suggested that the former can operate quite well with >> significantly reduced quality. It has alos been suggested that most >> applications could operate fine with somewhat reduced quality, but that >> the API definitions don't say anything about how to specify application >> quality requirements vs performance requirements for time measurement. > >Can we change gettimeofday and clock_gettime to lower resolution now? I can live with gettimeofday(2) and time(3) being degraded. I am going to insist that clock_gettime(CLOCK_REALTIME, CLOCK_UPTIME) remain precise. >I think 1000hz/s is enough for most applications, since a thread can >never sleep shorter than a tick for years. (Famous last words!) Time is not just a matter of sleeping. >We can introduce >hrtime_t clock_gethrtime(clockid_t clock) to get hi-resolution time >as the one seen in RTLinux, or gethrtime() as seen in Solaris (Daniel >Eischen said?) You know ? This is just a great example of why people feel the autocrap tools is the way to write portable code :-( The open group specifically allow clock_gettime() to implement more timescales, so what did those fools go and invent even more library functions for ? Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 10:33:06 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FE9016A41F; Mon, 31 Oct 2005 10:33:06 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id E33B143D46; Mon, 31 Oct 2005 10:33:05 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 0874F46B81; Mon, 31 Oct 2005 05:33:05 -0500 (EST) Date: Mon, 31 Oct 2005 10:33:04 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: David Xu In-Reply-To: <4365EF7B.1020706@freebsd.org> Message-ID: <20051031102424.V11619@fledge.watson.org> References: <30595.1130493297@critter.freebsd.dk> <20051028153457.d0wqgn2ask4sgw4k@netchild.homeip.net> <20051029195703.GB39253@dragon.NUXI.org> <43646AAC.2080107@freebsd.org> <20051030093718.GE39253@dragon.NUXI.org> <4364D90F.3090205@samsco.org> <20051031075843.GF39253@dragon.NUXI.org> <20051031083447.Y11619@fledge.watson.org> <4365EF7B.1020706@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Alexander Leidinger , freebsd-current@freebsd.org Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 10:33:06 -0000 On Mon, 31 Oct 2005, David Xu wrote: > Robert Watson wrote: >> >> It has been suggested that the former can operate quite well with >> significantly reduced quality. It has alos been suggested that most >> applications could operate fine with somewhat reduced quality, but that >> the API definitions don't say anything about how to specify application >> quality requirements vs performance requirements for time measurement. > > Can we change gettimeofday and clock_gettime to lower resolution now? I > think 1000hz/s is enough for most applications, since a thread can never > sleep shorter than a tick for years. We can introduce hrtime_t > clock_gethrtime(clockid_t clock) to get hi-resolution time as the one > seen in RTLinux, or gethrtime() as seen in Solaris (Daniel Eischen > said?) Not being a time person, I may be misrepresenting matters, but we do need to be a bit careful: while Linux relies on a lower quality time source (TSC), it continues to offer a high resolution without lots of stepping. I don't understand the issues well enough to reason about how these two compare from a time consumer perspective, but we need to be a little careful not to select the wrong way to lower quality, as that will needlessly hurt applications. And in the case of things like network protocols implemented in user space, I think the fear is real: by reducing the accuracy of (for example) network round trip time measurements, a significant performance impact can result due to miscalculating available bandwidth, timing out lost packets, etc. So far, my leaning has been: - Modify time(3) so that it relies on a timer-driven clock, since it needs to provide only one second granularity. Applications using second granularity are probably not all that concerned with high resolution timing. - Leave clock_gettime(2) as-is, since applications making use of this clock are likely looking for high resolution. - I'm not sure what to do about gettimeofday(). My leaning is to look at lowering the quality to improve performance. - Add an interface for extracting high resolution time data, such as the Solaris interface, and start migrating applications that care to that interface. - Further investigate the TSC issue. For example, allowing multiple time counters to be used depending on the API. Right now, all APIs source from the same timecounter, but you could imagine gettimeofday() using the TSC (with synchronization added?), and having clock_gettime() continue to use the higher quality source. I think this is the thrust of the Solaris approach -- allow direct access to timecounters of varying quality. - Investigate the quality offered by various other systems. One of the claims made is that we offer better time keeping than Linux systems, which sounds like a nice feature. If all systems offer low quality time sources for the POSIX APIs, then applications will be written to that assumption, meaning that offering high quality time there doesn't necessarily help them (does this follow?). Something to watch out for: while the default HZ is now 1000, it's easy to imagine HZ being different in different environments. There's been talk of revisiting the 1000HZ decision to lower overhead, for example, on SMP systems. We should be careful not to lock ourselves into a high HZ at this point. If HZ became 100, I think we'd be less happy with clock_gettime() returning the result of that method of time keeping, even though time(3) would be fine. Robert N M Watson From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 10:41:22 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25F9416A41F; Mon, 31 Oct 2005 10:41:22 +0000 (GMT) (envelope-from stefan@snowfall.se) Received: from mail.snowfall.se (pluring.snowfallnet.com [82.99.34.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF64543D5C; Mon, 31 Oct 2005 10:41:21 +0000 (GMT) (envelope-from stefan@snowfall.se) Received: from [192.168.0.109] (unknown [87.96.144.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.snowfall.se (Postfix) with ESMTP id EB37E62; Mon, 31 Oct 2005 11:41:18 +0100 (CET) Message-ID: <4365F4D1.6020809@snowfall.se> Date: Mon, 31 Oct 2005 11:41:21 +0100 From: Stefan Cars User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <20051030204120.GB99588@xor.obsecurity.org> <20051030205602.GB201@xor.obsecurity.org> In-Reply-To: <20051030205602.GB201@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Daniel Eischen , Greg 'groggy' Lehey , current@freebsd.org Subject: Re: MySQL crashes on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 10:41:22 -0000 Kris Kennaway wrote: > On Sun, Oct 30, 2005 at 03:52:42PM -0500, Daniel Eischen wrote: > >>On Sun, 30 Oct 2005, Kris Kennaway wrote: >> >> >>>On Sun, Oct 30, 2005 at 02:45:57PM +0100, Stefan Cars wrote: >>> >>>>Hi >>>> >>>>No. I don't need both. Removed libpthread.so.1 and still the same problem. >>> >>>You removed the mapping entry, or the file itself? Daniel asked for >>>the latter. >> >>Or perhaps try using libmap.conf to map libpthread.so.1 to >>libpthread.so.2 without any other mappings: >> >> libpthread.so.1 libpthread.so.2 > > > This is just a partial workaround, of course, and any of your binaries > that are also linked to two versions of other libraries may still > experience crashes (or may start to crash later when the new libraries > change further). You really want to track down and fix the root cause > now, to save you hours of pain later when the problem recurs > elsewhere. The thing is I don't need the libpthread.so.1 to libpthread.so.2 mapping, it works anyway (although mysql crashes) but when mapping libpthread.so* to libthr* it works perfectly. /S From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 10:48:39 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5EB2916A420; Mon, 31 Oct 2005 10:48:39 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2592243D45; Mon, 31 Oct 2005 10:48:39 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j9VAmaC0006665; Mon, 31 Oct 2005 10:48:37 GMT (envelope-from davidxu@freebsd.org) Message-ID: <4365F687.3070105@freebsd.org> Date: Mon, 31 Oct 2005 18:48:39 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20050928 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <81213.1130754398@critter.freebsd.dk> In-Reply-To: <81213.1130754398@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Leidinger , freebsd-current@freebsd.org, Robert Watson Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 10:48:39 -0000 Poul-Henning Kamp wrote: > In message <4365EF7B.1020706@freebsd.org>, David Xu writes: >>Can we change gettimeofday and clock_gettime to lower resolution now? > > > I can live with gettimeofday(2) and time(3) being degraded. > > I am going to insist that clock_gettime(CLOCK_REALTIME, CLOCK_UPTIME) > remain precise. > In thread program, we have to use clock_gettime, for example a thread wants to wait for condition variable for two seconds, it has to: struct timespec ts; clock_gettime(CLOCK_REALTIME, &ts); ts.tv_sec += 2; pthread_cond_wait(&cond, &mtx); problem is who really cares time precise? how many people are really handling realtime critical tasks? this is really an unpleasant side effect that a simple syscall can stall cpu. > >>I think 1000hz/s is enough for most applications, since a thread can >>never sleep shorter than a tick for years. > > > (Famous last words!) > > Time is not just a matter of sleeping. > > >>We can introduce >>hrtime_t clock_gethrtime(clockid_t clock) to get hi-resolution time >>as the one seen in RTLinux, or gethrtime() as seen in Solaris (Daniel >>Eischen said?) > > > You know ? > > This is just a great example of why people feel the autocrap tools > is the way to write portable code :-( > > The open group specifically allow clock_gettime() to implement > more timescales, so what did those fools go and invent even more > library functions for ? > > Poul-Henning > You can introduce other CLOCK_..., but auto tools won't detect them too, this means nobody will use them except us, probably worse then gethrtime. :-( From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 10:52:44 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6E3316A420; Mon, 31 Oct 2005 10:52:44 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77B5343D48; Mon, 31 Oct 2005 10:52:44 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j9VAqfIB006831; Mon, 31 Oct 2005 10:52:42 GMT (envelope-from davidxu@freebsd.org) Message-ID: <4365F77C.4000702@freebsd.org> Date: Mon, 31 Oct 2005 18:52:44 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20050928 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Xu References: <81213.1130754398@critter.freebsd.dk> <4365F687.3070105@freebsd.org> In-Reply-To: <4365F687.3070105@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Leidinger , Poul-Henning Kamp , freebsd-current@freebsd.org, Robert Watson Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 10:52:44 -0000 David Xu wrote: > > In thread program, we have to use clock_gettime, for example a thread > wants to wait for condition variable for two seconds, it has to: > > struct timespec ts; > > clock_gettime(CLOCK_REALTIME, &ts); > ts.tv_sec += 2; > pthread_cond_wait(&cond, &mtx); > Should be: pthread_cond_timedwait(&cond, &mtx, &ts); From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 10:53:46 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 864C816A41F; Mon, 31 Oct 2005 10:53:46 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CFCA43D4C; Mon, 31 Oct 2005 10:53:46 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id B977046B03; Mon, 31 Oct 2005 05:53:45 -0500 (EST) Date: Mon, 31 Oct 2005 10:53:45 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: David Xu In-Reply-To: <4365F687.3070105@freebsd.org> Message-ID: <20051031104949.D11619@fledge.watson.org> References: <81213.1130754398@critter.freebsd.dk> <4365F687.3070105@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Alexander Leidinger , Poul-Henning Kamp , freebsd-current@freebsd.org Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 10:53:46 -0000 On Mon, 31 Oct 2005, David Xu wrote: > In thread program, we have to use clock_gettime, for example a thread > wants to wait for condition variable for two seconds, it has to: > > struct timespec ts; > > clock_gettime(CLOCK_REALTIME, &ts); > ts.tv_sec += 2; > pthread_cond_wait(&cond, &mtx); > > problem is who really cares time precise? how many people are really > handling realtime critical tasks? this is really an unpleasant side > effect that a simple syscall can stall cpu. The questions are: how good is good enough? And for what? The problem here is that while pthread_cond_wait() can afford to accept low resolution, the same clock retrieval interface is also used for things like scientific measurement. So it sounds like the real mistake was the specification for the thread API: while timespec is the New Way for time-related interfaces, this approach has coalesced precision time measurement and "how long to sleep for" time measurement. Moving to HZ incrementing of the clock probably exceeds the quality reduction that makes sense for clock_gettime(), but moving to a roughly sync'd TSC clock (such as the Linux approach) probably doesn't. Robert N M Watson From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 10:59:58 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 623F216A425 for ; Mon, 31 Oct 2005 10:59:58 +0000 (GMT) (envelope-from caiquanqing@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC42843D49 for ; Mon, 31 Oct 2005 10:59:57 +0000 (GMT) (envelope-from caiquanqing@gmail.com) Received: by xproxy.gmail.com with SMTP id i28so18043wxd for ; Mon, 31 Oct 2005 02:59:56 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:mime-version:content-type; b=mldXNAg17BwJKBujDNyhbc+ETvOuz9DLlECkgq1VfgvtOlkbHaaDNdwJWrOjGqcDO4UX9kb8TChMdu9E8ji62UIIkpw3q42e/yEnE3V6M2mReTzNrGITVIUkG5EUb7eSEafIDk2egUv1UerMEzAgWyV1HHi2I7qED1ZwuEUr4TM= Received: by 10.70.131.6 with SMTP id e6mr1521276wxd; Sun, 30 Oct 2005 21:28:22 -0800 (PST) Received: by 10.70.11.18 with HTTP; Sun, 30 Oct 2005 21:28:22 -0800 (PST) Message-ID: <2b22951e0510302128q571a3c1se111262e88ae19bb@mail.gmail.com> Date: Sun, 30 Oct 2005 21:28:22 -0800 From: "Cai, Quanqing" To: freebsd-current@freebsd.org, bug-followup@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Edwin Groothuis , Igor Sysoev , Uwe Doering Subject: Re: kern/67919: Why nobody take serious to fix this bug? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 10:59:58 -0000 Today I happened to read this message on freebsd-stable: http://lists.freebsd.org/pipermail/freebsd-stable/2005-October/019086.html After I read all messages and related links, I feel so frustrating, why nobody take serious to fix this bug even we have a patch for it? I can repeat this bug on 7.0-CURRENT and 6.0-RC1 easily as a normal user! System goes no response so I have to power cycle it. The patch made by Uwe Doering actually works well. This bug looks like a security hole to me:( If you guy= s don't like this patch, please give out a reason and come out a better patch or solution. For impatience, you can run this to crush your system(7.x, 6.x, 5.x), you have to increase FILELEN to a size greater than your /tmp partition: =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D #include #include #include #include #include #include #define FILENAME "/tmp/test" /* where to put the test file */ #define FILELEN 710 /* test file length in MB */ main() { int fd; size_t len; char *buf, *p, *lim; len =3D FILELEN * 1024 * 1024; if ((fd =3D open(FILENAME, O_RDWR|O_CREAT|O_TRUNC, 0666)) =3D=3D -1) err(2, "open() failed"); if (ftruncate(fd, len) =3D=3D -1) err(2, "ftruncate() failed"); buf =3D mmap(NULL, len, PROT_WRITE, MAP_SHARED, fd, 0); if (buf =3D=3D MAP_FAILED) err(2, "mmap() failed"); (void)close(fd); for (p =3D buf, lim =3D p + len; p < lim; p +=3D 4096) *p =3D '0'; if (munmap(buf, len) =3D=3D -1) err(2, "munmap() failed"); exit(0); } =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Cai, Quanqing From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 11:03:51 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 761FD16A420; Mon, 31 Oct 2005 11:03:51 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECA0D43D72; Mon, 31 Oct 2005 11:03:50 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id 1F713BC50; Mon, 31 Oct 2005 11:03:48 +0000 (UTC) To: Robert Watson From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 31 Oct 2005 10:33:04 GMT." <20051031102424.V11619@fledge.watson.org> Date: Mon, 31 Oct 2005 12:03:48 +0100 Message-ID: <81484.1130756628@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Alexander Leidinger , freebsd-current@freebsd.org, David Xu Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 11:03:51 -0000 In message <20051031102424.V11619@fledge.watson.org>, Robert Watson writes: >- Modify time(3) so that it relies on a timer-driven clock, since it needs > to provide only one second granularity. Applications using second > granularity are probably not all that concerned with high resolution > timing. Provided we are ok with clock_gettime(CLOCK_REALTIME) and time(3) not agreeing at all times, then I have no objections to this one. >- Leave clock_gettime(2) as-is, since applications making use of this > clock are likely looking for high resolution. Here we have to be more specific, we could add more CLOCK_FOO values without affecting the existing. CLOCK_REALTIME and CLOCK_MONOTONIC should return precise results IMO. >- I'm not sure what to do about gettimeofday(). My leaning is to look at > lowering the quality to improve performance. An entirely different take on this is to make it a per-process (per-thread ?) option if timestamps are precise or not. We'd just need to give the processes a bit to flip to state their preference. This makes for far smaller patches to applications than anything which adds new timescales or functions. >- Add an interface for extracting high resolution time data, such as the > Solaris interface, and start migrating applications that care to that > interface. No opinion yet, I havn't studied the solaris interface. >- Further investigate the TSC issue. For example, allowing multiple > time counters to be used depending on the API. Right now, all APIs > source from the same timecounter, but you could imagine gettimeofday() > using the TSC (with synchronization added?), and having clock_gettime() > continue to use the higher quality source. I think this is the thrust > of the Solaris approach -- allow direct access to timecounters of > varying quality. Ok, let me get one thing very clear: As long as we are talking timestamps out of the timecounter code, there is by design and definition only one piece of hardware that controls. To change that would require somebody to dump a couple of months into the code. If we are talking timestamps in the sense of calling rdtsc(), then it is an entirely different matter. >- Investigate the quality offered by various other systems. One of the > claims made is that we offer better time keeping than Linux systems, It's more that we default to known safe configs where Linux takes a more "it worked for me" attitude to their hardware selection. If somebody with access to the necessary docs (ie: Intel + AMD NDAs) writes a piece of code that can tell us if using the TSC is safe, then we can also use the TSC in those cases. But lacking that function, enabling the TSC by default when so many machines has trouble with it would be counter to our normal attitude to system stability. > If all systems offer low quality time > sources for the POSIX APIs, then applications will be written to that > assumption, meaning that offering high quality time there doesn't > necessarily help them (does this follow?). Just because Linux doesn't see major problems in timekeeping doesn't really guarantee that their timekeeping isn't causing major problems. Problems originating in timekeeping tend to be classified as heisenbugs because they are hard to reproduce. As recently as a couple of weeks ago, I saw how a commercial UNIX make a dent in a project plan because the kernel jumped a few milliseconds when a lot of text scrolled by in an Xterm. You get to guess how many weird theories they had tried out before I nailed that diagnosis. Another thing to remember is that the TSC and ACPI hardware is not the only thing we have to deal with: Any solution we implement needs to also work on other architectures, including i486 with only i8254 timecounters etc. And finally, WinTel know that the ACPI timer sucks, thats why more recent hardware has HPET timers, I'm working on support for that. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 11:42:06 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1CE216A420; Mon, 31 Oct 2005 11:42:06 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0833F43D45; Mon, 31 Oct 2005 11:42:05 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost [127.0.0.1]) by mp2.macomnet.net (8.13.3/8.13.3) with ESMTP id j9VBg35h092456; Mon, 31 Oct 2005 14:42:03 +0300 (MSK) (envelope-from maxim@macomnet.ru) Date: Mon, 31 Oct 2005 14:42:03 +0300 (MSK) From: Maxim Konovalov To: "Cai, Quanqing" In-Reply-To: <2b22951e0510302128q571a3c1se111262e88ae19bb@mail.gmail.com> Message-ID: <20051031144056.A92356@mp2.macomnet.net> References: <2b22951e0510302128q571a3c1se111262e88ae19bb@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Igor Sysoev , Edwin Groothuis , freebsd-current@freebsd.org, Uwe Doering , bug-followup@freebsd.org Subject: Re: kern/67919: Why nobody take serious to fix this bug? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 11:42:06 -0000 On Sun, 30 Oct 2005, 21:28-0800, Cai, Quanqing wrote: > Today I happened to read this message on freebsd-stable: > http://lists.freebsd.org/pipermail/freebsd-stable/2005-October/019086.html > > After I read all messages and related links, I feel so frustrating, > why nobody take serious to fix this bug even we have a patch for it? > I can repeat this bug on 7.0-CURRENT and 6.0-RC1 easily as a normal > user! System goes no response so I have to power cycle it. The patch > made by Uwe Doering actually works well. This bug looks like a > security hole to me:( If you guys don't like this patch, please give > out a reason and come out a better patch or solution. I was told the patch is incorrect. It works in certain cases but incorrect in general. -- Maxim Konovalov From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 02:52:10 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1281616A41F; Mon, 31 Oct 2005 02:52:10 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from deadcafe.de (deadcafe.de [81.169.162.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FC4843D49; Mon, 31 Oct 2005 02:52:09 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from dialin.t-online.de (p54A5CAB2.dip.t-dialin.net [84.165.202.178]) by deadcafe.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id j9V2paHY024613 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 31 Oct 2005 03:51:39 +0100 (CET) Received: from [172.23.7.254] (doom.rock.net [172.23.7.254]) by dialin.t-online.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id j9V2pJSH042483; Mon, 31 Oct 2005 03:51:20 +0100 (CET) Message-ID: <436586A6.4090907@deadcafe.de> Date: Mon, 31 Oct 2005 03:51:18 +0100 From: Daniel Rock User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <20051030093718.GE39253@dragon.NUXI.org> <4364D90F.3090205@samsco.org> <20051030195936.GZ4115@funkthat.com> <20051030.161606.65680605.imp@bsdimp.com> In-Reply-To: <20051030.161606.65680605.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=1.8 required=5.5 tests=FORGED_RCVD_HELO, RCVD_IN_NJABL_DUL,RCVD_IN_SORBS_DUL autolearn=disabled version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on deadcafe.de X-Spam-Level: * X-Mailman-Approved-At: Mon, 31 Oct 2005 12:48:04 +0000 Cc: Alexander@Leidinger.net, gurney_j@resnet.uoregon.edu, freebsd-current@freebsd.org, davidxu@freebsd.org Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 02:52:10 -0000 M. Warner Losh schrieb: > Actually, ioport reads can be faster than the 1us that's widely > quoted. ioport reads can be as fast as ~125ns (2 cycles at 16MHz). > However, experience has shown that they are rarely this fast. I've > seen 8MB/s pio over the pci bus on some custom hardware we have, which > 2Mreads/sec which is about 500ns per read. I think that the pci > hardware that I was reading had a few extra wait states... According to "Software Optimization Guide for AMD64 Processors": http://www.amd.com/us-en/assets/content_type/white_papers_and_tech_docs/25112.PDF the "in" machine instructions have a latency of ~180 clock cycles. But this will be only the lower theoretical limit. Daniel From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 12:59:33 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F3C1216A420 for ; Mon, 31 Oct 2005 12:59:32 +0000 (GMT) (envelope-from kuba@server.roztocze.com.pl) Received: from roztocze.com.pl (server.roztocze.com.pl [217.96.30.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35F5A43D67 for ; Mon, 31 Oct 2005 12:59:25 +0000 (GMT) (envelope-from kuba@server.roztocze.com.pl) Received: from server.roztocze.com.pl (localhost [127.0.0.1]) by roztocze.com.pl (8.13.5/8.13.5) with ESMTP id j9VCxLOH027075 for ; Mon, 31 Oct 2005 13:59:21 +0100 Received: (from kuba@localhost) by server.roztocze.com.pl (8.13.5/8.13.4/Submit) id j9VCxLWj032685 for freebsd-current@freebsd.org; Mon, 31 Oct 2005 13:59:21 +0100 Date: Mon, 31 Oct 2005 13:59:21 +0100 From: KubaTyszko To: freebsd-current@freebsd.org Message-ID: <20051031125921.GA24820@lbl.pl> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="VbJkn9YxBvnuCH5J" Content-Disposition: inline User-Agent: Mutt/1.4.2i X-Virus-Scanned: by amavisd-new Subject: 7.0-CURRENT (31oct 05) freezes - (ppp and probabl xorg) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kuba@lbl.pl List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 12:59:33 -0000 --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline hi. a few days ago i upgraded to latest -current and after that when i use ppp connection (any kind inluding rfconn_pppd, pptp, pppoe) when using Xorg, system hangs after establishing session and agreeing ip addresses. (when i use ppp in only console - everything works fine). the same issue occurs with today -CURRENT. i attached backtrace. moreover, when u run Xorg by startx it takes some time to start up x - when i run startx for first time - nothing happens, but after ctrl+c and startx again it finally does start. - maybe this is all connected. can anybody help with this ? --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=bt [root@kubal:/usr/obj/usr/src/sys/KUBA:#] kgdb kernel.debug /var/crash/vmcore.0 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0x5f042f64 fault code = supervisor read, page not present instruction pointer = 0x20:0xc052b0ee stack pointer = 0x28:0xd4440ca4 frame pointer = 0x28:0xd4440cd0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 12 (swi4: clock sio) trap number = 12 panic: page fault Uptime: 14m50s Dumping 511 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 511MB (130656 pages) 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:165 165 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); (kgdb) list *0xc052b0ee 0xc052b0ee is in softclock (/usr/src/sys/kern/kern_timeout.c:220). 215 curticks = softticks; 216 bucket = &callwheel[curticks & callwheelmask]; 217 c = TAILQ_FIRST(bucket); 218 while (c) { 219 depth++; 220 if (c->c_time != curticks) { 221 c = TAILQ_NEXT(c, c_links.tqe); 222 ++steps; 223 if (steps >= MAX_SOFTCLOCK_STEPS) { 224 nextsoftcheck = c; (kgdb) bt #0 doadump () at pcpu.h:165 #1 0xc051d62b in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399 #2 0xc051d8c4 in panic (fmt=0xc06bec49 "%s") at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xc069cc10 in trap_fatal (frame=0xd4440c64, eva=1594109796) at /usr/src/sys/i386/i386/trap.c:855 #4 0xc069c33e in trap (frame= {tf_fs = 8, tf_es = -733741016, tf_ds = -1068302296, tf_edi = -1046977280, tf_esi = 4, tf_ebp = -733737776, tf_isp = -733737840, tf_ebx = 1, tf_edx = -874293032, tf_ecx = 1594109788, tf_eax = 889177, tf_trapno = 12, tf_err = 0, tf_eip = -1068322578, tf_cs = 32, tf_eflags = 65538, tf_esp = -1046963968, tf_ss = 0}) at /usr/src/sys/i386/i386/trap.c:269 #5 0xc068c2ca in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #6 0xc052b0ee in softclock (dummy=0x0) at /usr/src/sys/kern/kern_timeout.c:220 #7 0xc0509421 in ithread_execute_handlers (p=0xc1988890, ie=0xc1986500) at /usr/src/sys/kern/kern_intr.c:662 #8 0xc0509538 in ithread_loop (arg=0xc19705a0) at /usr/src/sys/kern/kern_intr.c:745 #9 0xc0508458 in fork_exit (callout=0xc05094e4 , arg=0xc19705a0, frame=0xd4440d38) at /usr/src/sys/kern/kern_fork.c:789 #10 0xc068c32c in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:208 (kgdb) quit [root@kubal:/usr/obj/usr/src/sys/KUBA:#] --VbJkn9YxBvnuCH5J-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 13:18:49 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9EB816A41F for ; Mon, 31 Oct 2005 13:18:49 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from indor.net.tomline.ru (indor.net.tomline.ru [213.183.100.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BF8D43D53 for ; Mon, 31 Oct 2005 13:18:48 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from SNEZHKO by indorsoft.ru (MDaemon.PRO.v7.2.2.R) with ESMTP id md50000026812.msg for ; Mon, 31 Oct 2005 19:18:44 +0600 X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 87583, updated: 30.10.2005] To: freebsd-current@freebsd.org From: Victor Snezhko Date: Mon, 31 Oct 2005 19:18:39 +0600 Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Processed: indor.net.tomline.ru, Mon, 31 Oct 2005 19:18:44 +0600 (not processed: spam filter disabled) X-Return-Path: snezhko@indorsoft.ru X-MDaemon-Deliver-To: freebsd-current@freebsd.org X-VVS-Spam: false Subject: 7.0-CURRENT (31oct 05) freezes - (ppp and probabl xorg) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 13:18:49 -0000 KubaTyszko kuba at lbl.pl wrote: > a few days ago i upgraded to latest -current and after that when i > use ppp connection (any kind inluding rfconn_pppd, pptp, pppoe) when > using Xorg, system hangs after establishing session and agreeing ip > addresses. (when i use ppp in only console - everything works > fine). the same issue occurs with today -CURRENT. > i attached backtrace. This issue was discussed here some days ago: http://lists.freebsd.org/pipermail/freebsd-current/2005-October/057217.html Yesterday Vladimir Kushnir found a workaround - You can try to disable INET6 in the kernel config. You can also try to rollback to the 2005.10.21.19.42.50 CURRENT. I experience the same problem, system crashes even without initiating a connection, approximately three seconds after I start /usr/sbin/ppp -- WBR, Victor V. Snezhko EMail: snezhko@indorsoft.ru From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 13:19:42 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 734A416A41F for ; Mon, 31 Oct 2005 13:19:42 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EFBE43D48 for ; Mon, 31 Oct 2005 13:19:32 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5FCD1.dip.t-dialin.net [84.165.252.209]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id j9VCwn9q092940; Mon, 31 Oct 2005 13:58:54 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from localhost (localhost [127.0.0.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id j9VEJL05052817; Mon, 31 Oct 2005 15:19:21 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (Andro-Beta.Leidinger.net [192.168.1.42]) by webmail.leidinger.net (Horde MIME library) with HTTP; Mon, 31 Oct 2005 15:19:21 +0100 Message-ID: <20051031151921.r4cwus3wuo8c8sgk@netchild.homeip.net> X-Priority: 3 (Normal) Date: Mon, 31 Oct 2005 15:19:21 +0100 From: Alexander Leidinger To: Nate Lawson References: <200510172310.j9HNAVPL013057@repoman.freebsd.org> <20051018094402.A29138@grasshopper.cs.duke.edu> <435501B9.4070401@samsco.org> <43553162.5040802@root.org> <20051020141023.0ejwdv4dss48wko0@netchild.homeip.net> <4357E137.5090703@root.org> <20051023121338.3e253c97@Magellan.Leidinger.net> <435BD088.30205@root.org> <20051030220006.nz9hh788f4ock0o8@netchild.homeip.net> <4365AC20.1090607@root.org> In-Reply-To: <4365AC20.1090607@root.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.3) / FreeBSD-4.11 X-Virus-Scanned: by amavisd-new Cc: current@freebsd.org Subject: Re: 1kHz noise from C3 sleep X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 13:19:42 -0000 Nate Lawson wrote: > Alexander Leidinger wrote: >> Nate Lawson wrote: >> >>>>>> My laptop makes noises when being (more or less) idle (I think I enabled >>>>>> C3...). Does this mean I should try to change HZ? >>>>> >>>>> >>>>> Sure, you can do it from a tunable (kern.hz I think), you don't >>>>> have to recompile. >>>> >>>> >>>> >>>> No, a HZ of 100 doesn't work, the laptop still makes noises. And it >>>> only has C2, no C3... >>> >>> >>> >>> Change to C1 (which is just HLT). If it still makes noise, it's >>> not your C2 or C3 sleep. >> >> >> It's the C2 sleep. Any ideas? > > Try C3, different values of kern.hz. Or earplugs. No C3, I already tried HZ=100 (after having HZ=1000), so I take the earplugs (or only C1)... ;-) Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 //GO.SYSIN DD *, DOODAH, DOODAH From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 13:26:07 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 766E816A41F for ; Mon, 31 Oct 2005 13:26:07 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from indor.net.tomline.ru (indor.net.tomline.ru [213.183.100.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1AAA43D48 for ; Mon, 31 Oct 2005 13:26:06 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from SNEZHKO by indorsoft.ru (MDaemon.PRO.v7.2.2.R) with ESMTP id md50000026816.msg for ; Mon, 31 Oct 2005 19:26:00 +0600 X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 87583, updated: 30.10.2005] To: freebsd-current@freebsd.org References: From: Victor Snezhko Date: Mon, 31 Oct 2005 19:25:55 +0600 In-Reply-To: (Victor Snezhko's message of "Mon, 31 Oct 2005 19:18:39 +0600") Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Processed: indor.net.tomline.ru, Mon, 31 Oct 2005 19:26:00 +0600 (not processed: spam filter disabled) X-Return-Path: snezhko@indorsoft.ru X-MDaemon-Deliver-To: freebsd-current@freebsd.org X-VVS-Spam: false Subject: Re: 7.0-CURRENT (31oct 05) freezes - (ppp and probabl xorg) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 13:26:07 -0000 Victor Snezhko writes: > KubaTyszko kuba at lbl.pl wrote: > >> a few days ago i upgraded to latest -current and after that when i >> use ppp connection (any kind inluding rfconn_pppd, pptp, pppoe) when >> using Xorg, system hangs after establishing session and agreeing ip >> addresses. (when i use ppp in only console - everything works Oops, issue is not the same exactly - console fails for me too. But anyway, this can be caused by similar problems. -- WBR, Victor V. Snezhko EMail: snezhko@indorsoft.ru From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 13:27:05 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B1F816A41F; Mon, 31 Oct 2005 13:27:05 +0000 (GMT) (envelope-from is@rambler-co.ru) Received: from yam.park.rambler.ru (yam.park.rambler.ru [81.19.64.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4A3A43D4C; Mon, 31 Oct 2005 13:27:03 +0000 (GMT) (envelope-from is@rambler-co.ru) Received: from is.park.rambler.ru (is.park.rambler.ru [81.19.64.102]) by yam.park.rambler.ru (8.13.3/8.13.3) with ESMTP id j9VDQuPd087067; Mon, 31 Oct 2005 16:26:56 +0300 (MSK) (envelope-from is@rambler-co.ru) Date: Mon, 31 Oct 2005 16:26:56 +0300 (MSK) From: Igor Sysoev X-X-Sender: is@is.park.rambler.ru To: Maxim Konovalov In-Reply-To: <20051031144056.A92356@mp2.macomnet.net> Message-ID: <20051031162438.I554@is.park.rambler.ru> References: <2b22951e0510302128q571a3c1se111262e88ae19bb@mail.gmail.com> <20051031144056.A92356@mp2.macomnet.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Edwin Groothuis , "Cai, Quanqing" , Uwe Doering , bug-followup@freebsd.org, freebsd-current@freebsd.org Subject: Re: kern/67919: Why nobody take serious to fix this bug? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 13:27:05 -0000 On Mon, 31 Oct 2005, Maxim Konovalov wrote: > On Sun, 30 Oct 2005, 21:28-0800, Cai, Quanqing wrote: > >> Today I happened to read this message on freebsd-stable: >> http://lists.freebsd.org/pipermail/freebsd-stable/2005-October/019086.html >> >> After I read all messages and related links, I feel so frustrating, >> why nobody take serious to fix this bug even we have a patch for it? >> I can repeat this bug on 7.0-CURRENT and 6.0-RC1 easily as a normal >> user! System goes no response so I have to power cycle it. The patch >> made by Uwe Doering actually works well. This bug looks like a >> security hole to me:( If you guys don't like this patch, please give >> out a reason and come out a better patch or solution. > > I was told the patch is incorrect. It works in certain cases but > incorrect in general. Why is it incorrect ? I'm using it for year. Igor Sysoev http://sysoev.ru/en/ From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 13:29:57 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFD3F16A41F; Mon, 31 Oct 2005 13:29:57 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91CAC43D7D; Mon, 31 Oct 2005 13:29:45 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id j9VDTiSs027235; Mon, 31 Oct 2005 06:29:44 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43661C49.6090802@samsco.org> Date: Mon, 31 Oct 2005 06:29:45 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: <30595.1130493297@critter.freebsd.dk> <20051028153457.d0wqgn2ask4sgw4k@netchild.homeip.net> <20051029195703.GB39253@dragon.NUXI.org> <43646AAC.2080107@freebsd.org> <20051030093718.GE39253@dragon.NUXI.org> <4364D90F.3090205@samsco.org> <20051031075843.GF39253@dragon.NUXI.org> <20051031083447.Y11619@fledge.watson.org> In-Reply-To: <20051031083447.Y11619@fledge.watson.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-current@FreeBSD.org, David O'Brien Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 13:29:57 -0000 Robert Watson wrote: > > On Sun, 30 Oct 2005, David O'Brien wrote: > >>> ACPI-fast requires an ioport read which takes about 1us (according to >>> Google). Do that 1000 times a second and you have each CPU spending >>> 1% of its time doing nothing but reading the clock. Yikes. >> >> >> But we've lived with using the ACPI timercounter (vs. TSC) for quite a >> while now. Why all of a sudden are the authors of this thread having >> an issue with it now. I know about the recent MySQL thread - but with >> the TSC being untrustable on MP and power managed systems, why is >> there such a desire to use the TSC? > > > Because in the past few weeks, several developers have noticed that if > you change timercounters from ACPI-fast to TSC, you get significant > performance boosts on real-world workloads. Drew reported this a couple > of weeks ago on net@ after looking at loopback network performance, and > I suggested he frob the timecounter on his system, which resulted in a > significant measured performance increase. Then recently it was > reported that MySQL also saw a significant boost from faster > timekeeping, as it performs frequent time measurement. > [...] Another thing to keep in mind is that now is an excellent time to start thinking about 7.0 and experimenting and validating possible improvements. Maybe we'll come to the conclusion that the TSC still isn't appropriate to use, or is only appropriate for certain scenarios, but unless we work with it now, we'll never know. Scott From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 14:18:21 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0F7E16A41F; Mon, 31 Oct 2005 14:18:21 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB1A543D45; Mon, 31 Oct 2005 14:18:20 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost [127.0.0.1]) by mp2.macomnet.net (8.13.3/8.13.3) with ESMTP id j9VEII1Z094908; Mon, 31 Oct 2005 17:18:18 +0300 (MSK) (envelope-from maxim@macomnet.ru) Date: Mon, 31 Oct 2005 17:18:18 +0300 (MSK) From: Maxim Konovalov To: Igor Sysoev In-Reply-To: <20051031162438.I554@is.park.rambler.ru> Message-ID: <20051031170805.T94695@mp2.macomnet.net> References: <2b22951e0510302128q571a3c1se111262e88ae19bb@mail.gmail.com> <20051031144056.A92356@mp2.macomnet.net> <20051031162438.I554@is.park.rambler.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Edwin Groothuis , "Cai, Quanqing" , Uwe Doering , bug-followup@freebsd.org, freebsd-current@freebsd.org Subject: Re: kern/67919: Why nobody take serious to fix this bug? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 14:18:21 -0000 [...] > > I was told the patch is incorrect. It works in certain cases but > > incorrect in general. > > Why is it incorrect ? I'm using it for year. Because you can't just throw away any chunk of data (e.g. it could be a meta-data) without a risk to damage a filesystem. -- Maxim Konovalov From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 15:20:46 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C224616A41F; Mon, 31 Oct 2005 15:20:46 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DFE743D45; Mon, 31 Oct 2005 15:20:46 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.4/8.13.4) with ESMTP id j9VFKjwr019540; Mon, 31 Oct 2005 07:20:45 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id j9VFKiLb019539; Mon, 31 Oct 2005 07:20:44 -0800 (PST) (envelope-from obrien) Date: Mon, 31 Oct 2005 07:20:43 -0800 From: "David O'Brien" To: Robert Watson Message-ID: <20051031152043.GA19167@dragon.NUXI.org> Mail-Followup-To: freebsd-current@freebsd.org, Robert Watson , Alexander Leidinger , David Xu References: <30595.1130493297@critter.freebsd.dk> <20051028153457.d0wqgn2ask4sgw4k@netchild.homeip.net> <20051029195703.GB39253@dragon.NUXI.org> <43646AAC.2080107@freebsd.org> <20051030093718.GE39253@dragon.NUXI.org> <4364D90F.3090205@samsco.org> <20051031075843.GF39253@dragon.NUXI.org> <20051031083447.Y11619@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051031083447.Y11619@fledge.watson.org> X-Operating-System: FreeBSD 7.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i Cc: Alexander Leidinger , freebsd-current@FreeBSD.org, David Xu Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-current@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 15:20:46 -0000 On Mon, Oct 31, 2005 at 09:26:11AM +0000, Robert Watson wrote: > > On Sun, 30 Oct 2005, David O'Brien wrote: > > >>ACPI-fast requires an ioport read which takes about 1us (according to > >>Google). Do that 1000 times a second and you have each CPU spending 1% > >>of its time doing nothing but reading the clock. Yikes. > > > >But we've lived with using the ACPI timercounter (vs. TSC) for quite a > >while now. Why all of a sudden are the authors of this thread having an > >issue with it now. I know about the recent MySQL thread - but with the > >TSC being untrustable on MP and power managed systems, why is there such > >a desire to use the TSC? > > Because in the past few weeks, several developers have noticed that if you > change timercounters from ACPI-fast to TSC, you get significant > performance boosts on real-world workloads. Setting sysctl kern.timecounter.hardware=tsc isn't a great idea. PHK has mentioned several times how it seems many are wanting to play it fast and loose with the time source to the kernel. Providing some alternate loose time answers to an application such as MySQL that doesn't need accurate timing and presumable can handle variation would be a good thing. But that is different than simply setting kern.timecounter.hardware=tsc -- -- David (obrien@FreeBSD.org) From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 16:03:08 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E5C416A41F; Mon, 31 Oct 2005 16:03:08 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id A489843D45; Mon, 31 Oct 2005 16:03:07 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.4/8.13.4) with ESMTP id j9VG36P8020228; Mon, 31 Oct 2005 08:03:06 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id j9VG35UZ020227; Mon, 31 Oct 2005 08:03:05 -0800 (PST) (envelope-from obrien) Date: Mon, 31 Oct 2005 08:03:05 -0800 From: "David O'Brien" To: Poul-Henning Kamp Message-ID: <20051031160305.GA20092@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, Poul-Henning Kamp , Robert Watson , Alexander Leidinger , freebsd-current@freebsd.org, David Xu References: <20051031102424.V11619@fledge.watson.org> <81484.1130756628@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <81484.1130756628@critter.freebsd.dk> X-Operating-System: FreeBSD 7.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i Cc: Alexander Leidinger , freebsd-current@FreeBSD.org, Robert Watson , David Xu Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 16:03:08 -0000 On Mon, Oct 31, 2005 at 12:03:48PM +0100, Poul-Henning Kamp wrote: > If somebody with access to the necessary docs (ie: Intel + AMD NDAs) > writes a piece of code that can tell us if using the TSC is safe, > then we can also use the TSC in those cases. There are cases where the TSC will count slower while the processor is HTL'ed on AMD64 CPU's. This can make TSC's get out of sync on dual core processors. There has been an on-going thread on the x86-64 mailing list on the issue affecting Linux. Linux developers assumed dual-core CPU's had a synced TSC between cores. Ensuring the use of the ACPI (PMTIMER) or HPET has been recommended. To help the situation, AMD has publicly announced the RDTSCP (read TSCP pair) instruction. Also that future AMD64 processors will have a P-state (power state) invariant TSC. -- -- David (obrien@FreeBSD.org) From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 16:43:19 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3663D16A4C0 for ; Mon, 31 Oct 2005 16:43:19 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8BAC43D62 for ; Mon, 31 Oct 2005 16:43:15 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from [10.50.41.234] (Not Verified[10.50.41.234]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Mon, 31 Oct 2005 11:59:56 -0500 From: John Baldwin To: Vladimir Kushnir Date: Mon, 31 Oct 2005 12:31:32 -0500 User-Agent: KMail/1.8.2 References: <20051027022313.R675@kushnir1.kiev.ua> <20051030052435.J646@kushnir1.kiev.ua> <20051031000217.F636@kushnir1.kiev.ua> In-Reply-To: <20051031000217.F636@kushnir1.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510311231.33322.jhb@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 16:43:20 -0000 On Sunday 30 October 2005 05:17 pm, Vladimir Kushnir wrote: > A bit further. > > On Sun, 30 Oct 2005, Vladimir Kushnir wrote: > > OK, here it is. It's happened between 2005.10.21.19.42.50 and > > 2005.10.22.05.07.00. > > Since then, panic is absolutely reproducible. > > Actually, when I took INET6 from kernel (once again, it's GENERIC) these > panics stop. Hmmm. Are those timestamps UTC? If so, there's nothing worthwhile that changed in there: imp 2005-10-22 05:01:11 UTC FreeBSD src repository Modified files: sys/dev/re if_re.c Log: The controller -> device switch happened in 4.0, fix comment Revision Changes Path 1.59 +1 -1 src/sys/dev/re/if_re.c imp 2005-10-22 05:06:55 UTC FreeBSD src repository Modified files: sys/dev/bfe if_bfe.c sys/dev/bge if_bge.c sys/dev/lge if_lge.c sys/dev/nge if_nge.c sys/dev/vge if_vge.c sys/dev/usb if_aue.c if_axe.c if_rue.c if_udav.c sys/pci if_rl.c if_sf.c if_sis.c if_sk.c if_ste.c if_tl.c if_vr.c if_wb.c Log: Replace FreeBSD 3.x syntax (controller miibus0) with 4.x syntax (device miibus) in time for 7.0 :-) However, there were some INET6 changes just before and just after that window: suz 2005-10-21 15:45:13 UTC FreeBSD src repository Modified files: sys/netinet6 ip6_output.c ip6_var.h nd6_nbr.c Log: sync with KAME (renamed a macro IPV6_DADOUTPUT to IPV6_UNSPECSRC) Obtained from: KAME Revision Changes Path 1.99 +1 -1 src/sys/netinet6/ip6_output.c 1.36 +1 -1 src/sys/netinet6/ip6_var.h 1.38 +1 -1 src/sys/netinet6/nd6_nbr.c suz 2005-10-21 15:59:00 UTC FreeBSD src repository Modified files: sys/netinet6 nd6.c Log: perform NUD on an IPv6-aware point-to-point interface Obtained from: KAME MFC after: 1 week Revision Changes Path 1.60 +2 -0 src/sys/netinet6/nd6.c suz 2005-10-21 16:23:01 UTC FreeBSD src repository Modified files: sys/netinet icmp6.h sys/netinet6 icmp6.c in6.c in6.h in6_ifattach.c in6_ifattach.h in6_var.h ip6_output.c mld6.c mld6_var.h nd6.c nd6.h nd6_nbr.c nd6_rtr.c share/doc/IPv6 IMPLEMENTATION Log: sync with KAME regarding NDP - introduced fine-grain-timer to manage ND-caches and IPv6 Multicast-Listeners - supports Router-Preference - better prefix lifetime management - more spec-comformant DAD advertisement - updated RFC/internet-draft revisions Obtained from: KAME Reviewed by: ume, gnn MFC after: 2 month Revision Changes Path 1.9 +157 -83 src/share/doc/IPv6/IMPLEMENTATION 1.20 +5 -1 src/sys/netinet/icmp6.h 1.69 +2 -2 src/sys/netinet6/icmp6.c 1.57 +322 -80 src/sys/netinet6/in6.c 1.42 +6 -4 src/sys/netinet6/in6.h 1.31 +7 -21 src/sys/netinet6/in6_ifattach.c 1.7 +1 -1 src/sys/netinet6/in6_ifattach.h 1.27 +15 -4 src/sys/netinet6/in6_var.h 1.100 +14 -13 src/sys/netinet6/ip6_output.c 1.24 +116 -46 src/sys/netinet6/mld6.c 1.7 +1 -0 src/sys/netinet6/mld6_var.h 1.61 +337 -209 src/sys/netinet6/nd6.c 1.21 +32 -21 src/sys/netinet6/nd6.h 1.39 +37 -30 src/sys/netinet6/nd6_nbr.c 1.31 +479 -282 src/sys/netinet6/nd6_rtr.c and later: suz 2005-10-22 05:07:16 UTC FreeBSD src repository Modified files: sys/netinet6 in6.c nd6.c Log: fixed a compilation failure on amd64/sparc64/ia64 Submitted by: max MFC after: 2 month Revision Changes Path 1.58 +2 -2 src/sys/netinet6/in6.c 1.62 +4 -2 src/sys/netinet6/nd6.c -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 17:08:01 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60A9B16A422 for ; Mon, 31 Oct 2005 17:08:01 +0000 (GMT) (envelope-from WillS@housing.ufl.edu) Received: from smtp.housing.ufl.edu (smtp2.housing.ufl.edu [128.227.47.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id B006043D53 for ; Mon, 31 Oct 2005 17:07:59 +0000 (GMT) (envelope-from WillS@housing.ufl.edu) Received: (qmail 32357 invoked by uid 98); 31 Oct 2005 17:07:58 -0000 Received: from 128.227.47.18 by smtp1.housing.ufl.edu (envelope-from , uid 82) with qmail-scanner-1.25 (clamdscan: 0.87/1082. spamassassin: 3.0.4. Clear:RC:1(128.227.47.18):. Processed in 0.078945 secs); 31 Oct 2005 17:07:58 -0000 X-Qmail-Scanner-Mail-From: WillS@housing.ufl.edu via smtp1.housing.ufl.edu X-Qmail-Scanner: 1.25 (Clear:RC:1(128.227.47.18):. Processed in 0.078945 secs) Received: from bragi.housing.ufl.edu (128.227.47.18) by smtp.housing.ufl.edu with SMTP; 31 Oct 2005 17:07:57 -0000 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 31 Oct 2005 12:04:29 -0500 Message-ID: <0E972CEE334BFE4291CD07E056C76ED808DC30A8@bragi.housing.ufl.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: MySQL Performance 6.0rc1 Thread-Index: AcXbjGyTn6ln4dWURlWYnFhKG8rxUgCsF+LA From: "Will Saxon" To: "Greg 'groggy' Lehey" , "Robert Watson" Cc: current@FreeBSD.org, Marian Hettwer Subject: RE: MySQL Performance 6.0rc1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 17:08:01 -0000 >=20 > This kind of issue, but also performance differences, are a > disadvantage for both groups. One of my tasks at MySQL is to do > something about that, but I'm spread pretty thin. If anybody has > input on this kind of topic, I'd be interested to hear from you. Well I would like to see a HOWTO or something about proper configuration of MySQL for FreeBSD systems.=20 I have a quad opteron that I am currently struggling with using 6.0-RC1, and I am staring at some of the benchmarks in this thread with disbelief as I can only pull about 9K qps where others are getting 18-20K qps with lesser hardware.=20 I may just not be very good at searching through list archives, but it's difficult to find up to date information including suggested kernel configurations, gotchas for high memory configurations, etc. -Will From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 17:10:10 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DABBF16A41F for ; Mon, 31 Oct 2005 17:10:10 +0000 (GMT) (envelope-from konfer@mikulas.com) Received: from s1.vhost.cz (s1.vhost.cz [82.208.27.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0374F43D45 for ; Mon, 31 Oct 2005 17:10:09 +0000 (GMT) (envelope-from konfer@mikulas.com) Received: (qmail 77055 invoked by alias); 31 Oct 2005 18:10:07 +0100 Received: from unknown (HELO localhost) (127.10.10.10) by s1.vhost.cz with SMTP; 31 Oct 2005 18:10:07 +0100 Received: from unknown ([127.0.0.1]) by localhost (s1.vhost.cz [127.0.0.1]) (amavisd-new, port 10628) id 76983-02; Mon, 31 Oct 2005 18:10:06 +0100 (CET) Received: from unknown (HELO ?172.19.13.144?) (jiri@mikulas.com@195.122.204.153) by s1.vhost.cz with AES256-SHA encrypted SMTP; 31 Oct 2005 18:10:06 +0100 Message-ID: <43664FEB.9020502@mikulas.com> Date: Mon, 31 Oct 2005 18:10:03 +0100 From: Jiri Mikulas User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050429) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sam Leffler References: <4364F50E.2040509@mikulas.com> <4364FD15.1040703@errno.com> In-Reply-To: <4364FD15.1040703@errno.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at vhost.cz Cc: current@freebsd.org Subject: Re: new ath_hal X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 17:10:11 -0000 Hello After I applied patches on RELENG_6 I got this panic after about, Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x20:0xc06dcbb5 stack pointer = 0x28:0xdc9a3c04 frame pointer = 0x28:0xc1f3a000 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 = 40 (swi6: task queue) trap number = 12 panic: page fault Uptime: 4m50s Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... I have this kernel on Flash card, so I can't debug it now, but I'll try to reproduce this panic on lab machine. Do you thik that this panic is ath related ? further when I started compiling of kernel, I got this warning WARNING: unknown option `AH_SUPPORT_5413' removed from /usr/obj/usr/src/sys/ROUTER-IPFW-PF/opt_ah.h WARNING: unknown option `AH_SUPPORT_DFS' removed from /usr/obj/usr/src/sys/ROUTER-IPFW-PF/opt_ah.h ..is this warning ok ? there is ath_hal: 0.9.16.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413, DFS) in dmesg also there are lot of messages like ath0: discard oversize frame (ether type 5e4 flags 3 len 1522 > max 1514) do you know why ? Thanks for reply Jiri Sam Leffler wrote: > Jiri Mikulas wrote: > >> Hello >> does anybody know if these cards (chipset) will be supported in new >> ath_hal, please ? >> >> Mini PCI Atheros: WNC CM10 miniPCI 5 GHz (AR5006X) >> http://www.i4shop.net/cz/iObchod/Catalog.asp?ca=1633&it=9398 >> >> or >> >> Atheros: AR5006X miniPCI 5 GHz (AR5414A) >> http://www.i4shop.net/cz/iObchod/Catalog.asp?ca=1633&it=9335 >> >> and when will be released the new HAL ? > > > The new hal was "released" ~2 months ago. These parts are supported. > No idea when it'll get committed. You can find the bits in > www.freebsd.org/~sam; don't forget to apply the ath and net80211 patches. > > Sam From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 17:21:08 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3034A16A41F; Mon, 31 Oct 2005 17:21:08 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id D61C543D45; Mon, 31 Oct 2005 17:21:07 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 1CBF346B4B; Mon, 31 Oct 2005 12:21:07 -0500 (EST) Date: Mon, 31 Oct 2005 17:21:06 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Will Saxon In-Reply-To: <0E972CEE334BFE4291CD07E056C76ED808DC30A8@bragi.housing.ufl.edu> Message-ID: <20051031171123.U80645@fledge.watson.org> References: <0E972CEE334BFE4291CD07E056C76ED808DC30A8@bragi.housing.ufl.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Greg 'groggy' Lehey , current@FreeBSD.org, Marian Hettwer Subject: RE: MySQL Performance 6.0rc1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 17:21:08 -0000 On Mon, 31 Oct 2005, Will Saxon wrote: >> This kind of issue, but also performance differences, are a >> disadvantage for both groups. One of my tasks at MySQL is to do >> something about that, but I'm spread pretty thin. If anybody has input >> on this kind of topic, I'd be interested to hear from you. > > Well I would like to see a HOWTO or something about proper configuration > of MySQL for FreeBSD systems. > > I have a quad opteron that I am currently struggling with using 6.0-RC1, > and I am staring at some of the benchmarks in this thread with disbelief > as I can only pull about 9K qps where others are getting 18-20K qps with > lesser hardware. > > I may just not be very good at searching through list archives, but it's > difficult to find up to date information including suggested kernel > configurations, gotchas for high memory configurations, etc. Well, I'm happy to do a bit of gathering of information. So far the main two recommendations have been: - Look at time counting -- if TSC is safe for your host, it can significantly improve performance. - Use libthr in FreEBSD 6.x, or linuxthreads in earlier versions. - Make sure you're using UNIX domain sockets for local traffic. Any other things to add to the list? I've created a page here: http://wikitest.freebsd.org/moin.cgi/MySQL Eventually we might want to turn this into a more formal document. Robert N M Watson From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 17:22:08 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38E2B16A41F; Mon, 31 Oct 2005 17:22:08 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id C18F543D49; Mon, 31 Oct 2005 17:22:07 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j9VHKAVj005348; Mon, 31 Oct 2005 10:20:10 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 31 Oct 2005 10:20:10 -0700 (MST) Message-Id: <20051031.102010.41632281.imp@bsdimp.com> To: jhb@freebsd.org From: Warner Losh In-Reply-To: <200510311231.33322.jhb@freebsd.org> References: <20051030052435.J646@kushnir1.kiev.ua> <20051031000217.F636@kushnir1.kiev.ua> <200510311231.33322.jhb@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 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 31 Oct 2005 10:20:10 -0700 (MST) Cc: freebsd-current@freebsd.org Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 17:22:08 -0000 From: John Baldwin Subject: Re: CURRENT + amd64 + user-ppp = panic Date: Mon, 31 Oct 2005 12:31:32 -0500 > On Sunday 30 October 2005 05:17 pm, Vladimir Kushnir wrote: > > A bit further. > > > > On Sun, 30 Oct 2005, Vladimir Kushnir wrote: > > > OK, here it is. It's happened between 2005.10.21.19.42.50 and > > > 2005.10.22.05.07.00. > > > Since then, panic is absolutely reproducible. > > > > Actually, when I took INET6 from kernel (once again, it's GENERIC) these > > panics stop. > > Hmmm. Are those timestamps UTC? If so, there's nothing worthwhile that > changed in there: > > imp 2005-10-22 05:01:11 UTC > > FreeBSD src repository > > Modified files: > sys/dev/re if_re.c > Log: > The controller -> device switch happened in 4.0, fix comment > > Revision Changes Path > 1.59 +1 -1 src/sys/dev/re/if_re.c > > imp 2005-10-22 05:06:55 UTC > > FreeBSD src repository > > Modified files: > sys/dev/bfe if_bfe.c > sys/dev/bge if_bge.c > sys/dev/lge if_lge.c > sys/dev/nge if_nge.c > sys/dev/vge if_vge.c > sys/dev/usb if_aue.c if_axe.c if_rue.c if_udav.c > sys/pci if_rl.c if_sf.c if_sis.c if_sk.c if_ste.c > if_tl.c if_vr.c if_wb.c > Log: > Replace FreeBSD 3.x syntax (controller miibus0) with 4.x syntax > (device miibus) in time for 7.0 :-) Further, the above changes are only comments! Warner From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 17:41:14 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FD7416A41F; Mon, 31 Oct 2005 17:41:14 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85AA243D53; Mon, 31 Oct 2005 17:41:13 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id j9VHnt08052201; Mon, 31 Oct 2005 12:49:56 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: dawnshade Date: Mon, 31 Oct 2005 12:40:52 -0500 User-Agent: KMail/1.6.2 References: <200510281103.38622.jkim@FreeBSD.org> <1886562656.20051029184945@mail.ru> In-Reply-To: <1886562656.20051029184945@mail.ru> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200510311240.54845.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV devel-20050919/1150/Sun Oct 30 06:20:38 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-acpi@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: Re[4]: [PATCH] ACPICA 20051021 import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 17:41:14 -0000 On Saturday 29 October 2005 10:49 am, dawnshade wrote: > Thank you, i didn't metioned that patch create new files. > After removing (and dl new patch) all compiled and install fine. > dmesg nothing differ from previous boot, all devices present exept > not working before it (like est, acpi_perf0 and psm). At first look > all work fine, system boots, X11 started and power indicator works > (i tested on laptop) plugged and unplugged. > > Can you tell me what i need more test? (unfortunatly i usually > perform antiviral and antispam solutions tests :) If there's no regression, that's good enough for now. ;-) > btw, my system is Acer TM 4151LMi (Pentium M 730 1.6GHz, i915, > ICH6+SATA150) unfortunalty i can test kernel only w/o 'device > apic', because with this dev i give many IDE timeouts and as result > system freeze. I believe that's a separate issue. > P.S. Sorry for poor english and email client. Thanks for the report, Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 18:00:43 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0ED416A420; Mon, 31 Oct 2005 18:00:43 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail26.syd.optusnet.com.au (mail26.syd.optusnet.com.au [211.29.133.167]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8A5D43D46; Mon, 31 Oct 2005 18:00:42 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail26.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id j9VI0cJo008855 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 1 Nov 2005 05:00:40 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id j9VI0cHh058565; Tue, 1 Nov 2005 05:00:38 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id j9VI0ciB058564; Tue, 1 Nov 2005 05:00:38 +1100 (EST) (envelope-from pjeremy) Date: Tue, 1 Nov 2005 05:00:37 +1100 From: Peter Jeremy To: Poul-Henning Kamp Message-ID: <20051031180037.GA39882@cirb503493.alcatel.com.au> References: <4365EF7B.1020706@freebsd.org> <81213.1130754398@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <81213.1130754398@critter.freebsd.dk> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: freebsd-current@freebsd.org, David Xu Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 18:00:44 -0000 On Mon, 2005-Oct-31 11:26:38 +0100, Poul-Henning Kamp wrote: >In message <4365EF7B.1020706@freebsd.org>, David Xu writes: >>We can introduce >>hrtime_t clock_gethrtime(clockid_t clock) to get hi-resolution time >>as the one seen in RTLinux, or gethrtime() as seen in Solaris (Daniel >>Eischen said?) ... >The open group specifically allow clock_gettime() to implement >more timescales, so what did those fools go and invent even more >library functions for ? gethrtime() dates back to SunOS 4.x and (AFAIK) predates TOG's work. ISTR it's not really a syscall but just reads the HR clock out of the magic page with the timer. I'd also support a move to make gettimeofday() a cheaper syscall that counts in 1/hz and require the use of clock_gettime() for accurate timestamps. This still leaves the issue of the scheduler - do we need an accurate (and expensive) record of how long a particular process executes? We can probably make the timestamps slightly cheaper to obtain since we only need to keep track of a time difference on a single CPU - there's no need for inter-CPU synchronisation (because a thread can't migrate from from CPU to CPU without the scheduler knowing). It probably doesn't even matter if the time intervals provided to the scheduler are inaccurate by a few percent or differ slightly between CPUs. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 18:35:01 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DABA216A41F; Mon, 31 Oct 2005 18:35:01 +0000 (GMT) (envelope-from drbrain@segment7.net) Received: from toxic.magnesium.net (toxic.magnesium.net [207.154.84.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E30643D5C; Mon, 31 Oct 2005 18:35:01 +0000 (GMT) (envelope-from drbrain@segment7.net) Received: from [192.168.1.70] (coop.robotcoop.com [216.231.59.167]) by toxic.magnesium.net (Postfix) with ESMTP id 3A68CDA8A0; Mon, 31 Oct 2005 10:35:01 -0800 (PST) In-Reply-To: <20051031171123.U80645@fledge.watson.org> References: <0E972CEE334BFE4291CD07E056C76ED808DC30A8@bragi.housing.ufl.edu> <20051031171123.U80645@fledge.watson.org> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Eric Hodel Date: Mon, 31 Oct 2005 10:34:55 -0800 To: current@FreeBSD.org X-Mailer: Apple Mail (2.734) Cc: Robert Watson Subject: Re: MySQL Performance 6.0rc1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 18:35:02 -0000 On Oct 31, 2005, at 9:21 AM, Robert Watson wrote: > Well, I'm happy to do a bit of gathering of information. So far > the main two recommendations have been: > > - Look at time counting -- if TSC is safe for your host, it can > significantly improve performance. It seems that, from this thread: http://lists.freebsd.org/pipermail/freebsd-current/2004-August/ 034073.html The question "is my TSC safe?" has the same answer as "am I using SMP?" Is this correct? > - Use libthr in FreEBSD 6.x, or linuxthreads in earlier versions. > > - Make sure you're using UNIX domain sockets for local traffic. > > Any other things to add to the list? I've created a page here: > > http://wikitest.freebsd.org/moin.cgi/MySQL > > Eventually we might want to turn this into a more formal document. I can't seem to edit this page, even after logging in.. -- Eric Hodel - drbrain@segment7.net - http://segment7.net FEC2 57F1 D465 EB15 5D6E 7C11 332A 551C 796C 9F04 From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 18:55:24 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59B8416A41F; Mon, 31 Oct 2005 18:55:24 +0000 (GMT) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94D7543D53; Mon, 31 Oct 2005 18:55:23 +0000 (GMT) (envelope-from max@love2party.net) Received: from p54A3EDB3.dip.t-dialin.net [84.163.237.179] (helo=donor.laier.local) by mrelayeu.kundenserver.de (node=mrelayeu7) with ESMTP (Nemesis), id 0ML2Dk-1EWeoN1pfw-0003to; Mon, 31 Oct 2005 19:55:15 +0100 From: Max Laier To: freebsd-current@freebsd.org Date: Mon, 31 Oct 2005 19:54:53 +0100 User-Agent: KMail/1.8.2 References: <20051027022313.R675@kushnir1.kiev.ua> <43602F2F.7080500@samsco.org> <200510281404.33462.jhb@freebsd.org> In-Reply-To: <200510281404.33462.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1298973.9I7Ud9geTj"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200510311955.13137.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 18:55:24 -0000 --nextPart1298973.9I7Ud9geTj Content-Type: multipart/mixed; boundary="Boundary-01=_MimZDv6xdU755fY" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-01=_MimZDv6xdU755fY Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 28 October 2005 20:04, John Baldwin wrote: > On Wednesday 26 October 2005 09:36 pm, Scott Long wrote: > > Vladimir Kushnir wrote: > > > Hello, > > > For a couple of days already my -CURRENT amd64 reliably panicks > > > whenever I'm trying to connect via ppp (nothing fancy - playn dialup, > > > no firewall). It's 100% reproducible both with custom kernel and with > > > GENERIC. A typescript of kgdb is attached. > > > > > > I'm running now on the kernel from Oct 19 which also panicks, BTW, wi= th > > > "kmem_map too small" on an attempt to run something like Linux > > > OpenOffice or Mathematica (neither kern.ipc.nmbclusters nor > > > vm.kmem_size_max tweaking helps; besides, I've only 512 MB RAM) > > > > > > Regards, > > > Vladimir > > > > I think that this is a result of the interrupt handler changes that John > > Baldwin made yesterday. Can you step your source back in time and see > > where it stops panicing? > > Actually, it can't be if softclock() is called directly from > ithread_loop(). In the new code ithread_loop() calls > ithread_execute_handlers() which would call softclock(). > > > > #0 doadump () at pcpu.h:172 > > > > > > 172 pcpu.h: No such file or directory. > > > > > > in pcpu.h > > > > > > (kgdb) where > > > > > > #0 doadump () at pcpu.h:172 > > > #1 0xffffffff803c65fc in boot (howto=3D260) > > > at /usr/src/sys/kern/kern_shutdown.c:399 > > > #2 0xffffffff803c609b in panic (fmt=3D0xffffffff805f2f46 "from > > > debugger") at /usr/src/sys/kern/kern_shutdown.c:555 > > > #3 0xffffffff801a8a32 in db_panic (addr=3D0, have_addr=3D0, count=3D= 0, > > > modif=3D0x0) > > > at /usr/src/sys/ddb/db_command.c:435 > > > #4 0xffffffff801a8f75 in db_command_loop () > > > at /usr/src/sys/ddb/db_command.c:404 > > > #5 0xffffffff801aae83 in db_trap (type=3D-1794574032, code=3D0) > > > at /usr/src/sys/ddb/db_main.c:221 > > > #6 0xffffffff803e5279 in kdb_trap (type=3D9, code=3D0, > > > tf=3D0xffffffff9508fb10) > > > at /usr/src/sys/kern/subr_kdb.c:445 > > > #7 0xffffffff8058d84e in trap_fatal (frame=3D0xffffffff9508fb10, > > > eva=3D18446742974715243568) at /usr/src/sys/amd64/amd64/trap.c:672 > > > #8 0xffffffff8058ddb1 in trap (frame=3D > > > {tf_rdi =3D 1, tf_rsi =3D 70876, tf_rdx =3D -240105096286740457= 8, > > > tf_rcx =3D 70876, tf_r8 =3D 0, tf_r9 =3D 1, tf_rax =3D 5340, tf_rbx = =3D 1, tf_rbp > > > =3D -1794573296, tf_r10 =3D 1, tf_r11 =3D 4, tf_r12 =3D -109951114368= 0, tf_r13 > > > =3D -1099035903488, tf_r14 =3D -1964245152, tf_r15 =3D 2, tf_trapno = =3D 9, > > > tf_addr =3D 0, tf_flags =3D 0, tf_err =3D 0, tf_rip =3D -2143462195, = tf_cs =3D 8, > > > tf_rflags =3D 65538, tf_rsp =3D -1794573360, tf_ss =3D 16}) at > > > /usr/src/sys/amd64/amd64/trap.c:488 > > > #9 0xffffffff8057b3bb in calltrap () > > > at /usr/src/sys/amd64/amd64/exception.S:168 > > This looks like a page fault rather than a 'kmem_map too small' panic. > > > > ---Type to continue, or q to quit--- > > > > > > #10 0xffffffff803d5ccd in softclock (dummy=3D0x1) > > > at /usr/src/sys/kern/kern_timeout.c:220 > > This is here: > while (c) { > depth++; > =3D=3D> if (c->c_time !=3D curticks) { > c =3D TAILQ_NEXT(c, c_links.tqe); > > c can't be NULL due to the while loop. Are any kernel modules being > unloaded when this happens? It isn't a NULL deref as "eva" is clearly non-NULL above. This makes me th= ink=20 of a callout list inconsistency. Most likely - due to the rest of the thre= ad=20 =2D this was introduced via "tn_timer_ch" in struct llinfo_nd6. I am think= ing=20 of a double callout_stop() or something like that. The callout_stop/reset(= )=20 calls on that callout are clearly over-nested to get things from a quick=20 glance :-\ The easiest seems to be to put some good old printf() debugging in=20 nd6_llinfo_settimer() and see what it does. Vladimir, could you try that? = =20 "Patch" attached. > > > #11 0xffffffff803b05cc in ithread_loop (arg=3D0xffffff0000031780) > > > at /usr/src/sys/kern/kern_intr.c:662 > > > #12 0xffffffff803af3cb in fork_exit ( > > > callout=3D0xffffffff803b0480 , arg=3D0xffffff000003= 1780, > > > frame=3D0xffffffff9508fc90) at /usr/src/sys/kern/kern_fork.c:789 > > > #13 0xffffffff8057b71e in fork_trampoline () > > > at /usr/src/sys/amd64/amd64/exception.S:394 > > > #14 0x0000000000000000 in ?? () =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --Boundary-01=_MimZDv6xdU755fY Content-Type: text/x-diff; charset="iso-8859-1"; name="nd6_llinfo_settimer.printf.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="nd6_llinfo_settimer.printf.diff" Index: nd6.c =================================================================== RCS file: /usr/store/mlaier/fcvs/src/sys/netinet6/nd6.c,v retrieving revision 1.62 diff -u -p -r1.62 nd6.c --- nd6.c 22 Oct 2005 05:07:16 -0000 1.62 +++ nd6.c 31 Oct 2005 18:49:58 -0000 @@ -395,6 +395,7 @@ nd6_llinfo_settimer(ln, tick) struct llinfo_nd6 *ln; long tick; { + printf("For %p %ld ticks\n", ln, tick); if (tick < 0) { ln->ln_expire = 0; ln->ln_ntick = 0; --Boundary-01=_MimZDv6xdU755fY-- --nextPart1298973.9I7Ud9geTj Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD4DBQBDZmiRXyyEoT62BG0RAjIrAJjItg/4+0B3ox15ov2Xtf40Lf6GAJ4kCzFh gs3UpibqAh3jo7KIqnoRkA== =38Pu -----END PGP SIGNATURE----- --nextPart1298973.9I7Ud9geTj-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 20:40:36 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2FBA16A41F for ; Mon, 31 Oct 2005 20:40:35 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F80243D46; Mon, 31 Oct 2005 20:40:35 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from [10.50.41.234] (Not Verified[10.50.41.234]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Mon, 31 Oct 2005 15:57:28 -0500 From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 31 Oct 2005 16:42:09 -0500 User-Agent: KMail/1.8.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510311642.10824.jhb@freebsd.org> Cc: "Bjoern A. Zeeb" , motminh@freebsd.org Subject: Re: LOR on kldunload nve/radix node head (v6?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 20:40:36 -0000 X-List-Received-Date: Mon, 31 Oct 2005 20:40:36 -0000 On Sunday 30 October 2005 04:37 am, Bjoern A. Zeeb wrote: > Hi, > > upon kldunload if_nve I got this. I added it with LOR ID # 166: > http://sources.zabbadoz.net/freebsd/lor.html#166 > > lock order reversal: > 1st 0xffffff00009a7180 nve0 (network driver) @ > sys/modules/nve/../../dev/nve/if_nve.c:674 2nd 0xffffff0000b234f0 radix > node head (radix node head) @ sys/net/route.c:148 KDB: stack backtrace: > kdb_backtrace() at kdb_backtrace+0x37 > witness_checkorder() at witness_checkorder+0x6f2 > _mtx_lock_flags() at _mtx_lock_flags+0x7a > rtalloc1() at rtalloc1+0x94 > in6_ifremloop() at in6_ifremloop+0x6d > in6_purgeaddr() at in6_purgeaddr+0x8b > if_purgeaddrs() at if_purgeaddrs+0xba > if_detach() at if_detach+0x31 > ether_ifdetach() at ether_ifdetach+0x79 > nve_detach() at nve_detach+0x240 > device_detach() at device_detach+0x85 > devclass_delete_driver() at devclass_delete_driver+0xb7 > driver_module_handler() at driver_module_handler+0xec > module_unload() at module_unload+0x56 > linker_file_unload() at linker_file_unload+0x93 > kern_kldunload() at kern_kldunload+0xa2 > kldunloadf() at kldunloadf+0x19 > syscall() at syscall+0x350 > Xfast_syscall() at Xfast_syscall+0xa8 > --- syscall (444, FreeBSD ELF64, kldunloadf), > rip = 0x800678c9c, rsp = 0x7fffffffe4d8, rbp = 0x7fffffffe980 --- The locking in this driver is broken. This LOR is just one symptom. Let me work up a patch. BTW, this driver probably should not be using a spin lock since it doesn't have an INTR_FAST handler. Actually, this driver has _lots_ of locking issues. It wasn't even locking the driver when transmitting packets handed to it by the stack! Try this patch: http://www.FreeBSD.org/~jhb/patches/nve_locking.patch Also, I have some debug printf()s in there because I think we can stub out the osmtx entirely. Let me know if you get any printf's on the console that include "normal mutex not held". Thanks! -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 20:40:36 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B83E16A421; Mon, 31 Oct 2005 20:40:36 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26FAB43D45; Mon, 31 Oct 2005 20:40:35 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from [10.50.41.234] (Not Verified[10.50.41.234]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Mon, 31 Oct 2005 15:57:27 -0500 From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 31 Oct 2005 15:47:05 -0500 User-Agent: KMail/1.8.2 References: <20051027233636.GA39380@dmw.hopto.org> <20051028105057.J20147@fledge.watson.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510311547.07571.jhb@freebsd.org> Cc: freebsd , Vaibhave Agarwal , Robert Watson , current@freebsd.org Subject: Re: How to call a function in the kernel from Local APIC timer handler X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 20:40:36 -0000 On Friday 28 October 2005 07:39 pm, Vaibhave Agarwal wrote: > Hi, I need some help with the new local APIC functionality added in > FreeBSD 6.0 and above. > > All the code which I am writing is in FreeBSD kernel. > > I was using LAPIC one shot timer for scheduling some events in the kernel. > The problem is that I cannot call the function in my code, directly from > the APIC timer handler, because all the interrupts are disabled in the > APIC timer handler ( function is lapic_handle_timer() ), and my function > uses a sleep mutex to protect the kernel code I have written. > Therefore, I schedule a software interrupt thread, which calls my function > later in time. > Is there a way, I can call my function instantly from the > lapic_handle_timer, bcoz using the software interrupt thread, decreases > the accuracy of the scheduler i am using. You can use spin mutexes rather than sleep mutexes in the lapic_handle_timer() context. If you need msleep/wakeup() functionality you can provide that using the sleepq(9) interface directly. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 20:40:36 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B83E16A421; Mon, 31 Oct 2005 20:40:36 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26FAB43D45; Mon, 31 Oct 2005 20:40:35 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from [10.50.41.234] (Not Verified[10.50.41.234]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Mon, 31 Oct 2005 15:57:27 -0500 From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 31 Oct 2005 15:47:05 -0500 User-Agent: KMail/1.8.2 References: <20051027233636.GA39380@dmw.hopto.org> <20051028105057.J20147@fledge.watson.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510311547.07571.jhb@freebsd.org> Cc: freebsd , Vaibhave Agarwal , Robert Watson , current@freebsd.org Subject: Re: How to call a function in the kernel from Local APIC timer handler X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 20:40:36 -0000 On Friday 28 October 2005 07:39 pm, Vaibhave Agarwal wrote: > Hi, I need some help with the new local APIC functionality added in > FreeBSD 6.0 and above. > > All the code which I am writing is in FreeBSD kernel. > > I was using LAPIC one shot timer for scheduling some events in the kernel. > The problem is that I cannot call the function in my code, directly from > the APIC timer handler, because all the interrupts are disabled in the > APIC timer handler ( function is lapic_handle_timer() ), and my function > uses a sleep mutex to protect the kernel code I have written. > Therefore, I schedule a software interrupt thread, which calls my function > later in time. > Is there a way, I can call my function instantly from the > lapic_handle_timer, bcoz using the software interrupt thread, decreases > the accuracy of the scheduler i am using. You can use spin mutexes rather than sleep mutexes in the lapic_handle_timer() context. If you need msleep/wakeup() functionality you can provide that using the sleepq(9) interface directly. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 20:40:36 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D8A616A41F for ; Mon, 31 Oct 2005 20:40:36 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id D415643D48 for ; Mon, 31 Oct 2005 20:40:35 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from [10.50.41.234] (Not Verified[10.50.41.234]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Mon, 31 Oct 2005 15:57:28 -0500 From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 31 Oct 2005 15:47:36 -0500 User-Agent: KMail/1.8.2 References: <4363A1B2.30603.18FC1576@localhost> <20051029202821.GA50470@xor.obsecurity.org> <20051029203436.GA12221@troutmask.apl.washington.edu> In-Reply-To: <20051029203436.GA12221@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510311547.38014.jhb@freebsd.org> Cc: Dan Langille , Steve Kargl , Kris Kennaway Subject: Re: amd64 6% slower than i386? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 20:40:36 -0000 On Saturday 29 October 2005 04:34 pm, Steve Kargl wrote: > On Sat, Oct 29, 2005 at 04:28:21PM -0400, Kris Kennaway wrote: > > On Sat, Oct 29, 2005 at 04:22:10PM -0400, Dan Langille wrote: > > > Build world is consistly 6% slower running an amd64 world than an > > > i386 world. > > > > > > In both cases, I'm using the default install of 6.0 RC-1 on the same > > > AMD 64 3000+ with 1GB of RAM. I'm finding that build world takes 48 > > > minutes under i386 and 51 minutes under amd64. > > > > > > Is this expected? > > > > You're comparing two different things (different compilers, some > > amount of different code being compiled), so you shouldn't expect them > > to be the same. > > He also may be building lib32 on amd64. Yep, that is on by default. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 20:43:49 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 529D916A41F; Mon, 31 Oct 2005 20:43:49 +0000 (GMT) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D90243D62; Mon, 31 Oct 2005 20:43:43 +0000 (GMT) (envelope-from mike@sentex.net) Received: from pumice3.sentex.ca (pumice3.sentex.ca [64.7.153.26]) by smarthost1.sentex.ca (8.13.4/8.13.4) with ESMTP id j9VKheCl086764; Mon, 31 Oct 2005 15:43:40 -0500 (EST) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by pumice3.sentex.ca (8.13.4/8.13.4) with ESMTP id j9VKheL9090513; Mon, 31 Oct 2005 15:43:40 -0500 (EST) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3/8.13.3) with ESMTP id j9VKhdvW071920 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 31 Oct 2005 15:43:39 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20051031154030.04ac4310@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Mon, 31 Oct 2005 15:42:53 -0500 To: John Baldwin , current@freebsd.org From: Mike Tancsa In-Reply-To: <200510281548.34796.jhb@freebsd.org> References: <200510281548.34796.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 X-Scanned-By: MIMEDefang 2.53 on 64.7.153.26 Cc: Subject: Re: [PATCH] Locking fixes for vr(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 20:43:49 -0000 At 02:48 PM 28/10/2005, John Baldwin wrote: >- Fix vr(4) to use callout_*() so that its callout runs without Giant. >- Fix locking in detach. > >Please test, thanks! > >http://www.FreeBSD.org/~jhb/patches/vr_locking.patch Its been running fine over the weekend. I have a DSL link over it and didnt see any dropped connections or odd issues. This is on a mini-itx board with built in rl and vr NICs vr0: port 0xd800-0xd8ff mem 0xfc003000-0xfc0030ff irq 10 at device 18.0 on pci0 miibus1: on vr0 ukphy0: on miibus1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: Ethernet address: 00:03:1d:02:0a:ee. I patched against 6.0.RC1 from Friday. ---Mike From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 20:57:46 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DA2816A41F for ; Mon, 31 Oct 2005 20:57:46 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45F8443D46 for ; Mon, 31 Oct 2005 20:57:46 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.54 (FreeBSD)) id 1EWgiv-000EOo-Na for freebsd-current@freebsd.org; Mon, 31 Oct 2005 20:57:46 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.53 (FreeBSD)) id 1EWgit-00020g-Ff for freebsd-current@freebsd.org; Mon, 31 Oct 2005 12:57:43 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17254.34119.81378.589992@roam.psg.com> Date: Mon, 31 Oct 2005 10:57:43 -1000 To: FreeBSD Current Subject: make kernel "kldxref: file isn't dynamically-linked" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 20:57:46 -0000 very current gets ===> xl (install) install -o root -g wheel -m 555 if_xl.ko /boot/kernel install -o root -g wheel -m 555 if_xl.ko.symbols /boot/kernel kldxref /boot/kernel kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked kldxref: file isn't dynamically-linked this is after buildworld to get correct config randy From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 21:09:40 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1BC916A420 for ; Mon, 31 Oct 2005 21:09:39 +0000 (GMT) (envelope-from Philippe.Pegon@crc.u-strasbg.fr) Received: from mailhost.u-strasbg.fr (mailhost.u-strasbg.fr [130.79.200.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6AD643DA6 for ; Mon, 31 Oct 2005 21:09:19 +0000 (GMT) (envelope-from Philippe.Pegon@crc.u-strasbg.fr) Received: from baal.u-strasbg.fr (baal.u-strasbg.fr [IPv6:2001:660:2402::41]) by mailhost.u-strasbg.fr (8.13.3/jtpda-5.5pre1) with ESMTP id j9VL9HSo073979 for ; Mon, 31 Oct 2005 22:09:17 +0100 (CET) Received: from [127.0.0.1] (crc.u-strasbg.fr [IPv6:2001:660:2402:1001::1]) by baal.u-strasbg.fr (8.13.4/jtpda-5.5pre1) with ESMTP id j9VL9HwE032529 for ; Mon, 31 Oct 2005 22:09:17 +0100 Message-ID: <4366879A.7090603@crc.u-strasbg.fr> Date: Mon, 31 Oct 2005 22:07:38 +0100 From: Philippe PEGON User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051016) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87/1151/Mon Oct 31 19:34:04 2005 on mr6.u-strasbg.fr X-Virus-Scanned: ClamAV 0.87/1151/Mon Oct 31 19:34:04 2005 on baal.u-strasbg.fr X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (mailhost.u-strasbg.fr [IPv6:2001:660:2402::156]); Mon, 31 Oct 2005 22:09:17 +0100 (CET) X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RELAYS autolearn=disabled version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mr6.u-strasbg.fr Subject: show stopper for FreeBSD 6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 21:09:40 -0000 Hi, I know that it's a bit late for FreeBSD 6 release, but I think this issue is a significant problem for FreeBSD : http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/83375 our productions servers with FreeBSD 5.4 reboots every week with this panic and we are not alone. We hoped that FreeBSD 6 would have solved this problem after this thread on freebsd-stable : http://lists.freebsd.org/mailman/htdig/freebsd-stable/2005-June/016154.html I have just tested with FreeBSD 6-RC1 and the problem remains here. Moreover, I think it's also a security issue because a single user, with a shell account on an FreeBSD SMP box, could trigger a panic with a simple shell script like that one (posted by Marc Olzheim in PR 83375), it's annoying particularly in a multi-user environment : #!/bin/sh count=0 while true do screen -d -m -c "${PWD}/.screenrc.crashpts" & count=$(($count+1)) if [ $(($count%100)) = 0 ] then killall screen sleep 2 killall -9 screen fi done -- Philippe PEGON From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 21:10:30 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4359B16A43B for ; Mon, 31 Oct 2005 21:10:29 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id B892F43D9C for ; Mon, 31 Oct 2005 21:10:11 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from [10.50.41.234] (Not Verified[10.50.41.234]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Mon, 31 Oct 2005 16:27:04 -0500 From: John Baldwin To: current@freebsd.org Date: Mon, 31 Oct 2005 17:11:49 -0500 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510311711.49927.jhb@freebsd.org> Cc: Subject: [PATCH] move exec_free_args() into do_execve() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 21:10:30 -0000 This patch removes some duplicate cleanup code from do_execve() failure cases and also moves the responsibility for exec_free_args() out of the callers of kern_execve() and into do_execve() instead: http://www.FreeBSD.org/~jhb/patches/exec_free_args.patch Please test, especially with various ABI binaries and with MAC policies enabled to make sure it doesn't break anything. Thanks! -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 21:15:37 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AF3A16A41F for ; Mon, 31 Oct 2005 21:15:37 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EF5E43D45 for ; Mon, 31 Oct 2005 21:15:36 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from [10.50.41.234] (Not Verified[10.50.41.234]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Mon, 31 Oct 2005 16:32:29 -0500 From: John Baldwin To: current@freebsd.org Date: Mon, 31 Oct 2005 17:17:12 -0500 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510311717.13419.jhb@freebsd.org> Cc: Subject: [PATCH] push Giant down into fdfree() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 21:15:37 -0000 This patches pushes Giant down into fdfree() by using VFS_LOCK_GIANT for the occasional VOP_ADVLOCK() and moving various vrele() calls out from under the FILEDESC_LOCK. Note that about half the calls to fdfree() (either directly or indirectly via fdunshare()) didn't lock Giant anyway. Please review and/or test, thanks! http://www.FreeBSD.org/~jhb/patches/fdfree.patch -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 21:48:24 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7118C16A41F; Mon, 31 Oct 2005 21:48:24 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF23443D45; Mon, 31 Oct 2005 21:48:23 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id 40410BC50; Mon, 31 Oct 2005 21:48:21 +0000 (UTC) From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 31 Oct 2005 12:03:48 +0100." <81484.1130756628@critter.freebsd.dk> Date: Mon, 31 Oct 2005 22:48:20 +0100 Message-ID: <84718.1130795300@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Alexander Leidinger , freebsd-current@freebsd.org, Robert Watson , David Xu Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 21:48:24 -0000 In message <81484.1130756628@critter.freebsd.dk>, "Poul-Henning Kamp" writes: >And finally, WinTel know that the ACPI timer sucks, thats why more >recent hardware has HPET timers, I'm working on support for that. OK, I've added a rudimentary HPET support that gives us a timecounter. It has quality -200, so it will not be used unless manually configured with the sysctl. Here is the short summary of the two machines I could test it on: TSC ACPI-fast HPET i8254 dual Xeon: 580 nsec 1429 nsec 1120 nsec 3980 nsec dual Opteron: 212 nsec 1270 nsec 1760 nsec 4420 nsec So while AMD is better at TSC and ACPI-fast, Intel is better at HPET and i8254. And yes, this probably depends on just about everything on the motherboard so your mileage will vary... Fortunately we can choose timecounter based on its speed, once we have convinced ourselves that the quality is OK. We don't currently do this, but the code can be resurrected. Poul-Henning Full results (HEX = Opteron, Y = Xeon) critter phk> ministat HEX/*.[AHT]* Y/*.[AHT]* x HEX/_.tc.ACPI-fast + HEX/_.tc.HPET * HEX/_.tc.TSC % Y/_.tc.ACPI-fast # Y/_.tc.HPET @ Y/_.tc.TSC +--------------------------------------------------------------------------+ | @ # % | | @ # % | | @ # % | |* @ # % | |* @ # x % + | |* @ # x % + | |* @ # x % + | |* @ # x % ++ | |** @ # xxx % ++ | |*** @ # xxx % +++| |MA A A |A| A MA | +--------------------------------------------------------------------------+ N Min Max Median Avg Stddev x 10 1.257e-06 1.299e-06 1.265e-06 1.2705e-06 1.5042532e-08 + 10 1.752e-06 1.794e-06 1.76e-06 1.7637e-06 1.2543701e-08 Difference at 95.0% confidence 4.932e-07 +/- 1.3013e-08 38.8194% +/- 1.02424% (Student's t, pooled s = 1.38496e-08) * 10 2.11e-07 2.45e-07 2.12e-07 2.189e-07 1.1551335e-08 Difference at 95.0% confidence -1.0516e-06 +/- 1.26009e-08 -82.7706% +/- 0.99181% (Student's t, pooled s = 1.3411e-08) % 10 1.429e-06 1.431e-06 1.429e-06 1.4295e-06 8.4983659e-10 Difference at 95.0% confidence 1.59e-07 +/- 1.00101e-08 12.5148% +/- 0.787888% (Student's t, pooled s = 1.06536e-08) # 10 1.12e-06 1.121e-06 1.12e-06 1.1201e-06 3.1622777e-10 Difference at 95.0% confidence -1.504e-07 +/- 9.99638e-09 -11.8379% +/- 0.786807% (Student's t, pooled s = 1.0639e-08) @ 10 5.79e-07 5.8e-07 5.8e-07 5.796e-07 5.1639778e-10 Difference at 95.0% confidence -6.909e-07 +/- 1.00001e-08 -54.3802% +/- 0.787097% (Student's t, pooled s = 1.06429e-08) critter phk> ministat HEX/* x HEX/_.tc.ACPI-fast + HEX/_.tc.HPET * HEX/_.tc.TSC % HEX/_.tc.i8254 +--------------------------------------------------------------------------+ | %| |* + %| |* x + %| |* x + %| |* x + %| |* x + %| |* x + %| |* x + %| |* xx + %| |** xx + %| |A A| A A| +--------------------------------------------------------------------------+ N Min Max Median Avg Stddev x 10 1.257e-06 1.299e-06 1.265e-06 1.2705e-06 1.5042532e-08 + 10 1.752e-06 1.794e-06 1.76e-06 1.7637e-06 1.2543701e-08 Difference at 95.0% confidence 4.932e-07 +/- 1.3013e-08 38.8194% +/- 1.02424% (Student's t, pooled s = 1.38496e-08) * 10 2.11e-07 2.45e-07 2.12e-07 2.189e-07 1.1551335e-08 Difference at 95.0% confidence -1.0516e-06 +/- 1.26009e-08 -82.7706% +/- 0.99181% (Student's t, pooled s = 1.3411e-08) % 10 4.418e-06 4.439e-06 4.424e-06 4.4264e-06 7.5894664e-09 Difference at 95.0% confidence 3.1559e-06 +/- 1.11942e-08 248.398% +/- 0.881084% (Student's t, pooled s = 1.19138e-08) critter phk> ministat Y/* x Y/_.tc.ACPI-fast + Y/_.tc.HPET * Y/_.tc.TSC % Y/_.tc.i8254 +--------------------------------------------------------------------------+ |* + x %| |* + x %| |* + x %| |* + x %| |* + x %| |* + x %| |* + x %| |* + x %| |* + x %| |* + x %| |A A A A| +--------------------------------------------------------------------------+ N Min Max Median Avg Stddev x 10 1.429e-06 1.431e-06 1.429e-06 1.4295e-06 8.4983659e-10 + 10 1.12e-06 1.121e-06 1.12e-06 1.1201e-06 3.1622777e-10 Difference at 95.0% confidence -3.094e-07 +/- 6.0245e-10 -21.6439% +/- 0.0421441% (Student's t, pooled s = 6.41179e-10) * 10 5.79e-07 5.8e-07 5.8e-07 5.796e-07 5.1639778e-10 Difference at 95.0% confidence -8.499e-07 +/- 6.60693e-10 -59.4544% +/- 0.0462185% (Student's t, pooled s = 7.03167e-10) % 10 3.973e-06 3.986e-06 3.98e-06 3.9791e-06 3.4140234e-09 Difference at 95.0% confidence 2.5496e-06 +/- 2.33748e-09 178.356% +/- 0.163517% (Student's t, pooled s = 2.48775e-09) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 21:53:06 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9920016A41F; Mon, 31 Oct 2005 21:53:06 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12BDC43D46; Mon, 31 Oct 2005 21:53:05 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from [10.50.41.234] (Not Verified[10.50.41.234]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Mon, 31 Oct 2005 17:09:59 -0500 From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 31 Oct 2005 17:54:43 -0500 User-Agent: KMail/1.8.2 References: <200510311717.13419.jhb@freebsd.org> In-Reply-To: <200510311717.13419.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510311754.44010.jhb@freebsd.org> Cc: current@freebsd.org Subject: Re: [PATCH] push Giant down into fdfree() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 21:53:06 -0000 On Monday 31 October 2005 05:17 pm, John Baldwin wrote: > This patches pushes Giant down into fdfree() by using VFS_LOCK_GIANT for > the occasional VOP_ADVLOCK() and moving various vrele() calls out from > under the FILEDESC_LOCK. Note that about half the calls to fdfree() > (either directly or indirectly via fdunshare()) didn't lock Giant anyway. > Please review and/or test, thanks! > > http://www.FreeBSD.org/~jhb/patches/fdfree.patch Nm on this one. :) Looks like csjp@ already has this mostly done (I thought I had seen this talked about on IRC). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 21:53:06 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9920016A41F; Mon, 31 Oct 2005 21:53:06 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12BDC43D46; Mon, 31 Oct 2005 21:53:05 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from [10.50.41.234] (Not Verified[10.50.41.234]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Mon, 31 Oct 2005 17:09:59 -0500 From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 31 Oct 2005 17:54:43 -0500 User-Agent: KMail/1.8.2 References: <200510311717.13419.jhb@freebsd.org> In-Reply-To: <200510311717.13419.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510311754.44010.jhb@freebsd.org> Cc: current@freebsd.org Subject: Re: [PATCH] push Giant down into fdfree() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 21:53:06 -0000 On Monday 31 October 2005 05:17 pm, John Baldwin wrote: > This patches pushes Giant down into fdfree() by using VFS_LOCK_GIANT for > the occasional VOP_ADVLOCK() and moving various vrele() calls out from > under the FILEDESC_LOCK. Note that about half the calls to fdfree() > (either directly or indirectly via fdunshare()) didn't lock Giant anyway. > Please review and/or test, thanks! > > http://www.FreeBSD.org/~jhb/patches/fdfree.patch Nm on this one. :) Looks like csjp@ already has this mostly done (I thought I had seen this talked about on IRC). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 23:24:13 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4468916A41F; Mon, 31 Oct 2005 23:24:13 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [65.170.254.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id B602C43D46; Mon, 31 Oct 2005 23:24:12 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mortis.over-yonder.net (unknown [70.152.101.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id 4FFB82A; Mon, 31 Oct 2005 17:24:12 -0600 (CST) Received: by mortis.over-yonder.net (Postfix, from userid 100) id EC09420FFE; Mon, 31 Oct 2005 17:24:10 -0600 (CST) Date: Mon, 31 Oct 2005 17:24:10 -0600 From: "Matthew D. Fuller" To: Robert Watson Message-ID: <20051031232410.GC1367@over-yonder.net> References: <30595.1130493297@critter.freebsd.dk> <20051028153457.d0wqgn2ask4sgw4k@netchild.homeip.net> <20051029195703.GB39253@dragon.NUXI.org> <43646AAC.2080107@freebsd.org> <20051030093718.GE39253@dragon.NUXI.org> <4364D90F.3090205@samsco.org> <20051031075843.GF39253@dragon.NUXI.org> <20051031083447.Y11619@fledge.watson.org> <4365EF7B.1020706@freebsd.org> <20051031102424.V11619@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051031102424.V11619@fledge.watson.org> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.9i-fullermd.2 Cc: Alexander Leidinger , freebsd-current@freebsd.org, David Xu Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 23:24:13 -0000 On Mon, Oct 31, 2005 at 10:33:04AM +0000 I heard the voice of Robert Watson, and lo! it spake thus: > > Something to watch out for: while the default HZ is now 1000, it's > easy to imagine HZ being different in different environments. And some of us (particularly with somewhat less shiny hardware) have kept it at 100 already. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 23:27:13 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0C8E16A420; Mon, 31 Oct 2005 23:27:13 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [65.170.254.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F89943D48; Mon, 31 Oct 2005 23:27:13 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mortis.over-yonder.net (unknown [70.152.101.39]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id 29C112A; Mon, 31 Oct 2005 17:27:13 -0600 (CST) Received: by mortis.over-yonder.net (Postfix, from userid 100) id CFAC420FA3; Mon, 31 Oct 2005 17:27:11 -0600 (CST) Date: Mon, 31 Oct 2005 17:27:11 -0600 From: "Matthew D. Fuller" To: Poul-Henning Kamp Message-ID: <20051031232711.GD1367@over-yonder.net> References: <20051031102424.V11619@fledge.watson.org> <81484.1130756628@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <81484.1130756628@critter.freebsd.dk> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.9i-fullermd.2 Cc: Alexander Leidinger , freebsd-current@freebsd.org, Robert Watson , David Xu Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 23:27:14 -0000 On Mon, Oct 31, 2005 at 12:03:48PM +0100 I heard the voice of Poul-Henning Kamp, and lo! it spake thus: > > Another thing to remember is that the TSC and ACPI hardware is not > the only thing we have to deal with: Any solution we implement > needs to also work on other architectures, including i486 with only > i8254 timecounters etc. Boy, I'm just becoming the voice of not-so-new hardware, aren't I? ;) My PPro uses the i8254. So does my P133 laptop. I presume most other Pentium-era machines, and probably PII's, do as well. When DID ACPI become the common case? -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 23:37:16 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C98F516A41F; Mon, 31 Oct 2005 23:37:16 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5729E43D45; Mon, 31 Oct 2005 23:37:16 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j9VNaKBR008992; Mon, 31 Oct 2005 16:36:20 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 31 Oct 2005 16:36:19 -0700 (MST) Message-Id: <20051031.163619.59657502.imp@bsdimp.com> To: fullermd@over-yonder.net From: Warner Losh In-Reply-To: <20051031232711.GD1367@over-yonder.net> References: <20051031102424.V11619@fledge.watson.org> <81484.1130756628@critter.freebsd.dk> <20051031232711.GD1367@over-yonder.net> 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 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 31 Oct 2005 16:36:20 -0700 (MST) Cc: Alexander@Leidinger.net, phk@phk.freebsd.dk, freebsd-current@FreeBSD.org, rwatson@FreeBSD.org, davidxu@FreeBSD.org Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 23:37:16 -0000 > > Another thing to remember is that the TSC and ACPI hardware is not > > the only thing we have to deal with: Any solution we implement > > needs to also work on other architectures, including i486 with only > > i8254 timecounters etc. > > Boy, I'm just becoming the voice of not-so-new hardware, aren't I? ;) > > My PPro uses the i8254. So does my P133 laptop. I presume most other > Pentium-era machines, and probably PII's, do as well. When DID ACPI > become the common case? Most pentium-era meachine use the tsc timecounter UNLESS ACPI or APM are configured.... Warner From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 03:07:16 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 966EA16A421 for ; Tue, 1 Nov 2005 03:07:16 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9032443D60 for ; Tue, 1 Nov 2005 03:07:15 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.54 (FreeBSD)) id 1EWmUU-000NoY-5e for freebsd-current@freebsd.org; Tue, 01 Nov 2005 03:07:14 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.53 (FreeBSD)) id 1EWmUR-000AbQ-OR for freebsd-current@freebsd.org; Mon, 31 Oct 2005 19:07:11 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17254.56287.352910.314361@roam.psg.com> Date: Mon, 31 Oct 2005 17:07:11 -1000 To: FreeBSD Current References: <17254.34119.81378.589992@roam.psg.com> Subject: Re: make kernel "kldxref: file isn't dynamically-linked" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 03:07:17 -0000 > very current gets > > ===> xl (install) > install -o root -g wheel -m 555 if_xl.ko /boot/kernel > install -o root -g wheel -m 555 if_xl.ko.symbols /boot/kernel > kldxref /boot/kernel > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > kldxref: file isn't dynamically-linked > > this is after buildworld to get correct config fwiw, there had been a change in GENERIC since my build last week, so my custom kernel changed as follows 19c19 < # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.432 2005/08/06 23:05:48 davidxu Exp $ --- > # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.433 2005/10/27 17:34:35 jhb Exp $ 83,84c83 < # Bus support. Do not remove isa, even if you have no isa slots < device isa --- > # Bus support. 170,172d168 < # Floating point support - do not disable. < device npx < 263,264d258 < device mem # Memory and kernel memory devices < device io # I/O device randy From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 03:13:07 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0386416A41F for ; Tue, 1 Nov 2005 03:13:07 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A44B43D48 for ; Tue, 1 Nov 2005 03:13:06 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: by xproxy.gmail.com with SMTP id i28so333444wxd for ; Mon, 31 Oct 2005 19:13:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ldoWRSaEEWiny2FvsJKNy+I7xlvhBmEFViuuD7rt1ijPknXNAxWsEQybTleUkUtkRR1UVPwf5qWvlAyTrdiSu4Q27Z0GcKDGVbCkjqT/DNkzq62iH92MVPlKTgKGJQ0btJHAUd/8Cz3WK737mJ4selps4XvWcAQqQzn1f66CMA8= Received: by 10.65.150.15 with SMTP id c15mr727213qbo; Mon, 31 Oct 2005 19:13:04 -0800 (PST) Received: by 10.65.105.11 with HTTP; Mon, 31 Oct 2005 19:13:03 -0800 (PST) Message-ID: Date: Tue, 1 Nov 2005 11:13:04 +0800 From: Jiawei Ye To: Randy Bush In-Reply-To: <17254.56287.352910.314361@roam.psg.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <17254.34119.81378.589992@roam.psg.com> <17254.56287.352910.314361@roam.psg.com> Cc: FreeBSD Current Subject: Re: make kernel "kldxref: file isn't dynamically-linked" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 03:13:07 -0000 On 11/1/05, Randy Bush wrote: > > very current gets > > > > =3D=3D=3D> xl (install) > > install -o root -g wheel -m 555 if_xl.ko /boot/kernel > > install -o root -g wheel -m 555 if_xl.ko.symbols /boot/kernel > > kldxref /boot/kernel > > kldxref: file isn't dynamically-linked It's the .symbols files problem. Not really harmful IMO. Jiawei -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 04:54:00 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7CC1716A41F for ; Tue, 1 Nov 2005 04:54:00 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from indor.net.tomline.ru (indor.net.tomline.ru [213.183.100.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id B848543D45 for ; Tue, 1 Nov 2005 04:53:59 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from SNEZHKO by indorsoft.ru (MDaemon.PRO.v7.2.2.R) with ESMTP id md50000026947.msg for ; Tue, 01 Nov 2005 10:53:49 +0600 X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 87696, updated: 31.10.2005] To: freebsd-current@freebsd.org From: Victor Snezhko Date: Tue, 01 Nov 2005 10:53:44 +0600 Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Processed: indor.net.tomline.ru, Tue, 01 Nov 2005 10:53:49 +0600 (not processed: spam filter disabled) X-Return-Path: snezhko@indorsoft.ru X-MDaemon-Deliver-To: freebsd-current@freebsd.org X-VVS-Spam: false Subject: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 04:54:00 -0000 Sorry for breaking the thread, I don't have message-id for message I'm replying to (neither a mailman interface, mor mailing list browser don't provide ids for recent messages). John Baldwin wrote on Mon Oct 31 08:43:20 PST 2005: > > A bit further. > > > > On Sun, 30 Oct 2005, Vladimir Kushnir wrote: > > > OK, here it is. It's happened between 2005.10.21.19.42.50 and > > > 2005.10.22.05.07.00. > > > Since then, panic is absolutely reproducible. > > > > Actually, when I took INET6 from kernel (once again, it's GENERIC) these > > panics stop. > Hmmm. Are those timestamps UTC? If so, there's nothing worthwhile that > changed in there: I experience the same problem, just wanted to report - when I cvsupped to the kernel as of 2005.10.21.19.42.50, problem remained. nooption INET6 actually helps. > imp 2005-10-22 05:01:11 UTC > ... -- WBR, Victor V. Snezhko EMail: snezhko@indorsoft.ru From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 04:55:13 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DCBB16A41F for ; Tue, 1 Nov 2005 04:55:13 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F3B043D45 for ; Tue, 1 Nov 2005 04:55:12 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jA14rJOA011221; Mon, 31 Oct 2005 21:53:19 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 31 Oct 2005 21:53:29 -0700 (MST) Message-Id: <20051031.215329.115777034.imp@bsdimp.com> To: phk@phk.freebsd.dk From: "M. Warner Losh" In-Reply-To: <81213.1130754398@critter.freebsd.dk> References: <4365EF7B.1020706@freebsd.org> <81213.1130754398@critter.freebsd.dk> 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 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 31 Oct 2005 21:53:19 -0700 (MST) Cc: freebsd-current@freebsd.org Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 04:55:13 -0000 In message: <81213.1130754398@critter.freebsd.dk> "Poul-Henning Kamp" writes: : I am going to insist that clock_gettime(CLOCK_REALTIME, CLOCK_UPTIME) : remain precise. 1ms is way too imprecise for the stuff we do at work. We need 3-4 more orders of magnitude at a minimum from the time keeping system. Ideally, through well documented interfaces. Warner From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 05:13:27 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F79016A421; Tue, 1 Nov 2005 05:13:27 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 653B343D6D; Tue, 1 Nov 2005 05:13:23 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jA15AOIo011334; Mon, 31 Oct 2005 22:10:24 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 31 Oct 2005 22:10:35 -0700 (MST) Message-Id: <20051031.221035.122314541.imp@bsdimp.com> To: rwatson@freebsd.org From: "M. Warner Losh" In-Reply-To: <20051031102424.V11619@fledge.watson.org> References: <20051031083447.Y11619@fledge.watson.org> <4365EF7B.1020706@freebsd.org> <20051031102424.V11619@fledge.watson.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 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 31 Oct 2005 22:10:24 -0700 (MST) Cc: freebsd-current@freebsd.org Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 05:13:27 -0000 In message: <20051031102424.V11619@fledge.watson.org> Robert Watson writes: : - Modify time(3) so that it relies on a timer-driven clock, since it needs : to provide only one second granularity. Applications using second : granularity are probably not all that concerned with high resolution : timing. It also needs to tick close to top of second. That is, it should tick 'soon' (< 1-3/hz) after gettimeofday/clock_gettime does. : - Leave clock_gettime(2) as-is, since applications making use of this : clock are likely looking for high resolution. Some of the calls we have use this itnerface. : - I'm not sure what to do about gettimeofday(). My leaning is to look at : lowering the quality to improve performance. Others use this interface. There's really no indication in the documentation which one provides better time. These two interfaces need to produce coherent timestamps between them, I think. Since many applications are a mix of third party libraries, those libraries will likely make different decisions about which API to use based on the whim of the developer and other intangible concerns. : - Add an interface for extracting high resolution time data, such as the : Solaris interface, and start migrating applications that care to that : interface. clock_gettime() remaining as it like is fine. : - Further investigate the TSC issue. For example, allowing multiple : time counters to be used depending on the API. Right now, all APIs : source from the same timecounter, but you could imagine gettimeofday() : using the TSC (with synchronization added?), and having clock_gettime() : continue to use the higher quality source. I think this is the thrust : of the Solaris approach -- allow direct access to timecounters of : varying quality. "The man with two wrist watches never knows what time it is." Be very careful here, since you need things to produce coherent results between the different methods of getting time. Synchronizing multiple clocks can be tricky. You cannot use TSC with power saving since it changes frequencies at times unknown to you to any real degree of accuracy. The bigger the frequency change, the larger the error you'll have using TSC. Likewise if there are steps in TSC due to other conditions, as has been reported, there's another source of error. : - Investigate the quality offered by various other systems. One of the : claims made is that we offer better time keeping than Linux systems, : which sounds like a nice feature. If all systems offer low quality time : sources for the POSIX APIs, then applications will be written to that : assumption, meaning that offering high quality time there doesn't : necessarily help them (does this follow?). It all depends on what you are trying to do with time. Most applications tolerate errors of 1ms or even 10ms without batting an eye. A minority care a great deal about errors in the us range. : Something to watch out for: while the default HZ is now 1000, it's easy to : imagine HZ being different in different environments. There's been talk : of revisiting the 1000HZ decision to lower overhead, for example, on SMP : systems. We should be careful not to lock ourselves into a high HZ at : this point. If HZ became 100, I think we'd be less happy with : clock_gettime() returning the result of that method of time keeping, even : though time(3) would be fine. We run HZ=1000 at work, except for slow systems that don't have to have low serial port latency. Those we run at HZ=100. I recently ran a AMD 586 (486 class machine at 133MHz) with -current. It was horrible at HZ=1000, but decent at HZ=100. Warner From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 07:03:02 2005 Return-Path: X-Original-To: FreeBSD-current@FreeBSD.ORG Delivered-To: FreeBSD-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20D8B16A41F for ; Tue, 1 Nov 2005 07:03:02 +0000 (GMT) (envelope-from grog@lemis.com) Received: from ext-gw.lemis.com (ext-gw.lemis.com [150.101.14.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9021C43D45 for ; Tue, 1 Nov 2005 07:03:01 +0000 (GMT) (envelope-from grog@lemis.com) Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.135]) by ext-gw.lemis.com (Postfix) with ESMTP id D0C4F1310AB for ; Tue, 1 Nov 2005 17:32:59 +1030 (CST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 9966084F8C; Tue, 1 Nov 2005 17:32:59 +1030 (CST) Date: Tue, 1 Nov 2005 17:32:59 +1030 From: Greg 'groggy' Lehey To: FreeBSD current users Message-ID: <20051101070259.GC18710@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="iFRdW5/EC4oqxDHL" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Cc: Subject: Really poor performance on /dev/ttyv* only X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 07:03:02 -0000 --iFRdW5/EC4oqxDHL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I've just installed -CURRENT on a Dell Inspiron 6000, and I discover that the keyboard response on virtual terminals (/dev/ttyv*) is very slow. If I keyboard repeat, the echo to the terminal is jerky, about 3 or 4 characters at a time with a marked delay in between. Under X or over the network there's no problem. Has anybody else seen this? The kernel isn't 100% GENERIC (I've disabled WITNESS and WITNESS_SKIPSPIN, for example), but I can't see anything that would explain this behaviour. Greg -- See complete headers for address and phone numbers. --iFRdW5/EC4oqxDHL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFDZxMjIubykFB6QiMRAj3hAKCHD4VJOLqM/rpye3BJCfGpMTZGggCeJvwK 5CIR10/AuZBQstMgs27jd4Q= =JqxS -----END PGP SIGNATURE----- --iFRdW5/EC4oqxDHL-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 07:11:17 2005 Return-Path: X-Original-To: FreeBSD-current@FreeBSD.org Delivered-To: FreeBSD-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44E3C16A41F; Tue, 1 Nov 2005 07:11:17 +0000 (GMT) (envelope-from fbsd-current@mawer.org) Received: from mail04.syd.optusnet.com.au (mail04.syd.optusnet.com.au [211.29.132.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4E1143D46; Tue, 1 Nov 2005 07:11:16 +0000 (GMT) (envelope-from fbsd-current@mawer.org) Received: from [127.0.0.1] (c220-237-120-88.thorn1.nsw.optusnet.com.au [220.237.120.88]) by mail04.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jA17B80J025603; Tue, 1 Nov 2005 18:11:09 +1100 Message-ID: <4367150C.4030508@mawer.org> Date: Tue, 01 Nov 2005 18:11:08 +1100 From: Antony Mawer User-Agent: Thunderbird 1.4 (Windows/20050908) MIME-Version: 1.0 To: "Greg 'groggy' Lehey" References: <20051101070259.GC18710@wantadilla.lemis.com> In-Reply-To: <20051101070259.GC18710@wantadilla.lemis.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD-current@FreeBSD.org Subject: Re: Really poor performance on /dev/ttyv* only X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 07:11:17 -0000 On 1/11/2005 6:02 PM, Greg 'groggy' Lehey wrote: > I've just installed -CURRENT on a Dell Inspiron 6000, and I discover > that the keyboard response on virtual terminals (/dev/ttyv*) is very > slow. If I keyboard repeat, the echo to the terminal is jerky, about > 3 or 4 characters at a time with a marked delay in between. Under X > or over the network there's no problem. Has anybody else seen this? > The kernel isn't 100% GENERIC (I've disabled WITNESS and > WITNESS_SKIPSPIN, for example), but I can't see anything that would > explain this behaviour. I've seen this on two FreeBSD 4.7 systems connected via a KVM (sharing with two Windows 2003 servers)... typing at the console of them was almost like typing via ssh on a satellite connection. Connecting via ssh was fine, it was only locally that it was a problem. Resetting the keyboard repeat rate on BSD had no discernible impact. I put it down to some sort of interaction between the KVM, the Windows servers and FreeBSD and put up with it... Cheers Antony From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 07:31:58 2005 Return-Path: X-Original-To: FreeBSD-current@FreeBSD.org Delivered-To: FreeBSD-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA41516A41F for ; Tue, 1 Nov 2005 07:31:58 +0000 (GMT) (envelope-from grog@lemis.com) Received: from ext-gw.lemis.com (ext-gw.lemis.com [150.101.14.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 438CE43D45 for ; Tue, 1 Nov 2005 07:31:58 +0000 (GMT) (envelope-from grog@lemis.com) Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.135]) by ext-gw.lemis.com (Postfix) with ESMTP id 4495F1310AB; Tue, 1 Nov 2005 18:01:57 +1030 (CST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 28D2984F8C; Tue, 1 Nov 2005 18:01:57 +1030 (CST) Date: Tue, 1 Nov 2005 18:01:57 +1030 From: Greg 'groggy' Lehey To: Antony Mawer Message-ID: <20051101073157.GE18710@wantadilla.lemis.com> References: <20051101070259.GC18710@wantadilla.lemis.com> <4367150C.4030508@mawer.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wTWi5aaYRw9ix9vO" Content-Disposition: inline In-Reply-To: <4367150C.4030508@mawer.org> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Cc: FreeBSD-current@FreeBSD.org Subject: Re: Really poor performance on /dev/ttyv* only X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 07:31:59 -0000 --wTWi5aaYRw9ix9vO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tuesday, 1 November 2005 at 18:11:08 +1100, Antony Mawer wrote: > On 1/11/2005 6:02 PM, Greg 'groggy' Lehey wrote: >> I've just installed -CURRENT on a Dell Inspiron 6000, and I discover >> that the keyboard response on virtual terminals (/dev/ttyv*) is very >> slow. If I keyboard repeat, the echo to the terminal is jerky, about >> 3 or 4 characters at a time with a marked delay in between. Under X >> or over the network there's no problem. Has anybody else seen this? >> The kernel isn't 100% GENERIC (I've disabled WITNESS and >> WITNESS_SKIPSPIN, for example), but I can't see anything that would >> explain this behaviour. > > I've seen this on two FreeBSD 4.7 systems connected via a KVM (sharing > with two Windows 2003 servers)... typing at the console of them was > almost like typing via ssh on a satellite connection. Connecting via ssh > was fine, it was only locally that it was a problem. Resetting the > keyboard repeat rate on BSD had no discernible impact. I'd guess that this is a different situation. FWIW, the Inspiron series are laptops, and this is at the keyboard. The machine is brand new, and I've never had another version of FreeBSD on it, but I suspect it's -CURRENT rather than the laptop. Greg -- See complete headers for address and phone numbers. --wTWi5aaYRw9ix9vO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFDZxntIubykFB6QiMRAqdkAKCKpwx549XBxtLpsS9JbSFWiW87UwCeI4/P b5l+ht6PSZufiwpxpHuB1+c= =cY82 -----END PGP SIGNATURE----- --wTWi5aaYRw9ix9vO-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 08:02:04 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DCE416A41F for ; Tue, 1 Nov 2005 08:02:04 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 932CC43D48 for ; Tue, 1 Nov 2005 08:02:03 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 83C2C46B17; Tue, 1 Nov 2005 03:02:02 -0500 (EST) Date: Tue, 1 Nov 2005 08:02:02 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "M. Warner Losh" In-Reply-To: <20051031.215329.115777034.imp@bsdimp.com> Message-ID: <20051101080018.R18382@fledge.watson.org> References: <4365EF7B.1020706@freebsd.org> <81213.1130754398@critter.freebsd.dk> <20051031.215329.115777034.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: phk@phk.freebsd.dk, freebsd-current@freebsd.org Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 08:02:04 -0000 On Mon, 31 Oct 2005, M. Warner Losh wrote: > In message: <81213.1130754398@critter.freebsd.dk> > "Poul-Henning Kamp" writes: > : I am going to insist that clock_gettime(CLOCK_REALTIME, CLOCK_UPTIME) > : remain precise. > > 1ms is way too imprecise for the stuff we do at work. We need 3-4 more > orders of magnitude at a minimum from the time keeping system. Ideally, > through well documented interfaces. While I agree that for many consumers, sub-1ms accuracy is too low, I suggest that as a vendor of atomic clocks, your company is in fact not the average consumer of timing information. :-). One nice thing about the Linux TSC model, despite its limitations, is that it provides a middle ground between incrementing the clock in ticks and providing a more continuous measure of time, by allowing interpolation between ticks. Robert N M Watson From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 08:11:45 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C14DB16A43C; Tue, 1 Nov 2005 08:11:45 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6729843D48; Tue, 1 Nov 2005 08:11:45 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id 427ACBC84; Tue, 1 Nov 2005 08:11:41 +0000 (UTC) To: Robert Watson From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 01 Nov 2005 08:02:02 GMT." <20051101080018.R18382@fledge.watson.org> Date: Tue, 01 Nov 2005 09:11:40 +0100 Message-ID: <87252.1130832700@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: freebsd-current@freebsd.org, "M. Warner Losh" Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 08:11:45 -0000 In message <20051101080018.R18382@fledge.watson.org>, Robert Watson writes: >One nice thing about the Linux TSC model, despite its limitations, is that >it provides a middle ground between incrementing the clock in ticks and >providing a more continuous measure of time, by allowing interpolation >between ticks. Which is also exactly what we do. The only real difference is that Linux trusts the TSC in cases where we don't. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 08:30:01 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EB7D16A422 for ; Tue, 1 Nov 2005 08:30:01 +0000 (GMT) (envelope-from roger@gwch.net) Received: from smtp.hispeed.ch (mxout.hispeed.ch [62.2.95.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41ECF43D49 for ; Tue, 1 Nov 2005 08:29:59 +0000 (GMT) (envelope-from roger@gwch.net) Received: from mail.gwch.net (84-73-90-203.dclient.hispeed.ch [84.73.90.203]) (authenticated bits=0) by smtp.hispeed.ch (8.12.6/8.12.6/taifun-1.0) with ESMTP id jA18TrLZ004093; Tue, 1 Nov 2005 09:29:54 +0100 Received: from localhost (link [127.0.0.1]) by mail.gwch.net (Postfix) with ESMTP id 5118A40595; Tue, 1 Nov 2005 09:29:53 +0100 (CET) Received: from mail.gwch.net ([127.0.0.1]) by localhost (mail.gwch.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22936-08; Tue, 1 Nov 2005 09:29:48 +0100 (CET) Received: from www.gwch.net (pluto.gwch.net [192.168.2.103]) by mail.gwch.net (Postfix) with ESMTP id 133104058E; Tue, 1 Nov 2005 09:29:48 +0100 (CET) Received: from 62.2.21.164 (SquirrelMail authenticated user rogerg) by www.gwch.net with HTTP; Tue, 1 Nov 2005 09:29:48 +0100 (CET) Message-ID: <33928.62.2.21.164.1130833788.squirrel@www.gwch.net> Date: Tue, 1 Nov 2005 09:29:48 +0100 (CET) From: "Roger Grosswiler" To: "Jayton Garnett" User-Agent: SquirrelMail/1.4.6 [CVS]-0.cvs20050812.1.fc4 MIME-Version: 1.0 X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: ClamAV version 0.87, clamav-milter version 0.87 on smtp-04.tornado.cablecom.ch X-Virus-Scanned: amavisd-new at gwch.net X-Virus-Status: Clean X-DCC-spamcheck-01.tornado.cablecom.ch-Metrics: smtp-04.tornado.cablecom.ch 32700; Body=2 Fuz1=2 Fuz2=2 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: [Partially Solved] Re: FreeBSD 6.0RC1 and WLAN X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 08:30:01 -0000 >>>Or type man ndisgen on your machine and see if it has the manpages. >>> > > Jayton, to use ndis successful on freebsd 6.0, you just have to make sure: - having your windows-drivers for your card - that you can read - only use ndisgen ...ndisgen did the trick! great stuff. i could contact yesterday without any problem my access-point. Unfortunately, ifconfig....authmode wpa did not work, so i created a wpa.conf and used wpa_supplicant -indis0 -c/etc/wpa.conf -Bw -> ifconfig then recognized itself, that there exists a wpa-secured connection. BTW. i was not able to change the channel, it stayed on channel 1 with ifconfig. Also, i could not leave my network, perhaps of pf or routing, but the wlan-card must work, because i could connect via wireless the access-point. Thanks again, Roger From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 09:50:02 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 1538B16A420; Tue, 1 Nov 2005 09:50:02 +0000 (GMT) In-Reply-To: <33928.62.2.21.164.1130833788.squirrel@www.gwch.net> from Roger Grosswiler at "Nov 1, 2005 09:29:48 am" To: roger@gwch.net (Roger Grosswiler) Date: Tue, 1 Nov 2005 09:50:02 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20051101095002.1538B16A420@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Cc: freebsd-current@freebsd.org Subject: Re: [Partially Solved] Re: FreeBSD 6.0RC1 and WLAN X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 09:50:02 -0000 Boy, you are all about the excess linefeeds, aren't you. > >>>Or type man ndisgen on your machine and see if it has the > manpages. > > > Jayton, > > to use ndis successful on freebsd 6.0, you just have to make sure: > > - having your windows-drivers for your card > - that you can read > - only use ndisgen > > ...ndisgen did the trick! great stuff. i could contact yesterday without > any problem my access-point. > > Unfortunately, ifconfig....authmode wpa did not work, so i created a > wpa.conf and used wpa_supplicant -indis0 -c/etc/wpa.conf -Bw -> > ifconfig then recognized itself, that there exists a wpa-secured > connection. ifconfig foo0 authmode wpa will never work. You must use wpa_supplicant to use WPA. The process of negotiating an encrypted link takes several steps, and afterwards more steps are required to periodically update the keys. It's much easier to drive this process from a user-mode daemon than from inside the kernel. Note that you may need to use the "-D ndis" option to wpa_supplicant to use WPA2. > BTW. i was not able to change the channel, it stayed on channel 1 with > ifconfig. The rule is that NDIS drivers only allow channel changing in ad-hoc mode. In infrastructure mode, you automatically end up on whatever channel the access point is using. Also, there was a bug in if_ndis.c that prevented ifconfig(8) from displaying the correct channel for the current association. This has been fixed in -current. > Also, i could not leave my network, perhaps of pf or routing, but the > wlan-card must work, because i could connect via wireless the > access-point. Can't help you there. If your access point is set up to do DHCP and your network's routing is correctly configured, things should 'just work.' -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 10:40:00 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 213D816A41F for ; Tue, 1 Nov 2005 10:40:00 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B62343D4C for ; Tue, 1 Nov 2005 10:39:59 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: by wproxy.gmail.com with SMTP id 71so544722wra for ; Tue, 01 Nov 2005 02:39:58 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=lR1F9QJfDT4G6iWfmXGDav70GTKdXqnWunm5xPYe+WsfWlkYzoWo7WnOkslmhGIbIS2KKoqwIwNsfXS0QQA13n4hl0FRWWBuHm5X/Nkw82XFXQcJuOzqtw4jiipkaUMWArpbfOTtzm9/qdvWqrtSWFaX75UOPqsbi86UpUv85dM= Received: by 10.54.117.16 with SMTP id p16mr1339105wrc; Tue, 01 Nov 2005 02:39:58 -0800 (PST) Received: by 10.54.113.17 with HTTP; Tue, 1 Nov 2005 02:39:58 -0800 (PST) Message-ID: <3aaaa3a0511010239o2777743dh@mail.gmail.com> Date: Tue, 1 Nov 2005 10:39:58 +0000 From: Chris To: Michael VInce In-Reply-To: <4361EE53.80603@roq.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <435F48DA.6060009@kernel32.de> <20051026105411.L32255@fledge.watson.org> <435F6B01.5020003@kernel32.de> <4361DDBB.4060903@roq.com> <4361EE53.80603@roq.com> Cc: current@freebsd.org, Marian Hettwer Subject: Re: MySQL Performance 6.0rc1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 10:40:00 -0000 Interesting thread I ran super-smack on my production server. It is an amd64 but using i386 kernel 32bit binaries mysql is optimised fairly well, mysql 4.0.x compiled with static but not optimised. in make.conf -O2. I am using libpthread I believe the new threading library introduced to 5.x, os is Freebsd 5.4. super-smack-1.2 # super-smack /usr/share/smacks/select-key.smack 10 10000 Query Barrel Report for client smacker1 connect: max=3D45ms min=3D0ms avg=3D 31ms from 10 clients Query_type num_queries max_time min_time q_per_s select_index 200000 0 0 29222.26 so I had a high average ms but my queries per second is impressive seeing as what has been posted, also bear in mind this box is under load since it is a production web server, I have a high cache hit efficiency like I said I optimised it. It is probable the default's are just more suited for linux but I think once tweaked it works just as well on bsd. Chris From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 10:58:43 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 72AD516A41F for ; Tue, 1 Nov 2005 10:58:43 +0000 (GMT) (envelope-from nge@cs.hmc.edu) Received: from turing.cs.hmc.edu (turing.cs.hmc.edu [134.173.42.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDBF043D77 for ; Tue, 1 Nov 2005 10:58:39 +0000 (GMT) (envelope-from nge@cs.hmc.edu) Received: by turing.cs.hmc.edu (Postfix, from userid 26983) id EE62A53271; Tue, 1 Nov 2005 02:58:38 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by turing.cs.hmc.edu (Postfix) with ESMTP id 4FDA15A8DE; Tue, 1 Nov 2005 02:58:36 -0800 (PST) Date: Tue, 1 Nov 2005 02:58:36 -0800 (PST) From: Nate Eldredge X-X-Sender: nate@turing To: Philippe PEGON In-Reply-To: <4366879A.7090603@crc.u-strasbg.fr> Message-ID: References: <4366879A.7090603@crc.u-strasbg.fr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: show stopper for FreeBSD 6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 10:58:43 -0000 On Mon, 31 Oct 2005, Philippe PEGON wrote: > Hi, > > I know that it's a bit late for FreeBSD 6 release, but I think this > issue is a significant problem for FreeBSD : > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/83375 > > our productions servers with FreeBSD 5.4 reboots every week with this > panic and we are not alone. We hoped that FreeBSD 6 would have solved > this problem after this thread on freebsd-stable : > > http://lists.freebsd.org/mailman/htdig/freebsd-stable/2005-June/016154.html > > I have just tested with FreeBSD 6-RC1 and the problem remains here. > Moreover, I think it's also a security issue because a single user, with > a shell account on an FreeBSD SMP box, could trigger a panic with a > simple shell script like that one (posted by Marc Olzheim in PR 83375), > it's annoying particularly in a multi-user environment : I am looking at this. I have a good idea what the problem is and will update tomorrow. -- Nate Eldredge nge@cs.hmc.edu From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 11:23:13 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A97416A41F for ; Tue, 1 Nov 2005 11:23:13 +0000 (GMT) (envelope-from sziszi@bsd.hu) Received: from mta02.mail.t-online.hu (mta02.mail.t-online.hu [195.228.240.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF61D43D45 for ; Tue, 1 Nov 2005 11:23:12 +0000 (GMT) (envelope-from sziszi@bsd.hu) Received: from momo.buza.adamsfamily.xx (catv3EC94453.pool.t-online.hu [62.201.68.83]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.t-online.hu (Postfix) with ESMTP for ; Tue, 1 Nov 2005 12:23:10 +0100 (CET) Received: from momo.buza.adamsfamily.xx (localhost.buza.adamsfamily.xx [127.0.0.1]) by momo.buza.adamsfamily.xx (8.13.4/8.13.4) with ESMTP id jA1BN8S8074628 for ; Tue, 1 Nov 2005 12:23:09 +0100 (CET) (envelope-from sziszi@bsd.hu) Received: (from sziszi@localhost) by momo.buza.adamsfamily.xx (8.13.4/8.13.4/Submit) id jA1BN5CB074627 for freebsd-current@freebsd.org; Tue, 1 Nov 2005 12:23:06 +0100 (CET) (envelope-from sziszi@bsd.hu) X-Authentication-Warning: momo.buza.adamsfamily.xx: sziszi set sender to sziszi@bsd.hu using -f Date: Tue, 1 Nov 2005 12:23:04 +0100 From: Szilveszter Adam To: freebsd-current@freebsd.org Message-ID: <20051101112303.GB51552@momo.buza.adamsfamily.xx> Mail-Followup-To: Szilveszter Adam , freebsd-current@freebsd.org References: <20051101070259.GC18710@wantadilla.lemis.com> <4367150C.4030508@mawer.org> <20051101073157.GE18710@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051101073157.GE18710@wantadilla.lemis.com> User-Agent: Mutt/1.5.11 Subject: Re: Really poor performance on /dev/ttyv* only X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 11:23:13 -0000 On Tue, Nov 01, 2005 at 06:01:57PM +1030, Greg 'groggy' Lehey wrote: > I'd guess that this is a different situation. FWIW, the Inspiron > series are laptops, and this is at the keyboard. The machine is brand > new, and I've never had another version of FreeBSD on it, but I > suspect it's -CURRENT rather than the laptop. FWIW, I also see slugishness on my Toshiba Satellite Pro 4200 series with yesterday's -CURRENT, it concerns not only keyboard input but also eg sorting of my mail spool (mbox format) in mutt and changing between messages etc. Interestingly enough, network activity is not affected. However, this isn't new, I have seen it also with -CURRENT from September. I use SCHED_ULE as the scheduler, if that matters. -- Regards: Szilveszter ADAM Budapest Hungary From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 11:25:31 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1CD916A420; Tue, 1 Nov 2005 11:25:30 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60E5C43D45; Tue, 1 Nov 2005 11:25:30 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.4/8.13.4) with ESMTP id jA1BPTVq057950; Tue, 1 Nov 2005 06:25:29 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.3/8.13.3) with ESMTP id jA1BPShM072763; Tue, 1 Nov 2005 06:25:28 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id B689E7302F; Tue, 1 Nov 2005 06:25:28 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051101112528.B689E7302F@freebsd-current.sentex.ca> Date: Tue, 1 Nov 2005 06:25:28 -0500 (EST) X-Virus-Scanned: ClamAV version 0.86, clamav-milter version 0.86 on clamscanner1 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 11:25:31 -0000 TB --- 2005-11-01 09:26:32 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-11-01 09:26:32 - starting HEAD tinderbox run for amd64/amd64 TB --- 2005-11-01 09:26:32 - cleaning the object tree TB --- 2005-11-01 09:27:13 - checking out the source tree TB --- 2005-11-01 09:27:13 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2005-11-01 09:27:13 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-11-01 09:34:18 - building world (CFLAGS=-O2 -pipe) TB --- 2005-11-01 09:34:18 - cd /src TB --- 2005-11-01 09:34:18 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries TB --- 2005-11-01 11:05:13 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-11-01 11:05:13 - cd /src TB --- 2005-11-01 11:05:13 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Tue Nov 1 11:05:13 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Tue Nov 1 11:21:20 UTC 2005 TB --- 2005-11-01 11:21:21 - generating LINT kernel config TB --- 2005-11-01 11:21:21 - cd /src/sys/amd64/conf TB --- 2005-11-01 11:21:21 - /usr/bin/make -B LINT TB --- 2005-11-01 11:21:21 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-11-01 11:21:21 - cd /src TB --- 2005-11-01 11:21:21 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Nov 1 11:21:21 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /src/sys/dev/acpica/acpi_hpet.c: In function `acpi_hpet_attach': /src/sys/dev/acpica/acpi_hpet.c:94: error: `_COMPONENT' undeclared (first use in this function) /src/sys/dev/acpica/acpi_hpet.c:94: error: (Each undeclared identifier is reported only once /src/sys/dev/acpica/acpi_hpet.c:94: error: for each function it appears in.) /src/sys/dev/acpica/acpi_hpet.c:94: error: `_THIS_MODULE' undeclared (first use in this function) /src/sys/dev/acpica/acpi_hpet.c: In function `acpi_hpet_detach': /src/sys/dev/acpica/acpi_hpet.c:159: error: `_COMPONENT' undeclared (first use in this function) /src/sys/dev/acpica/acpi_hpet.c:159: error: `_THIS_MODULE' undeclared (first use in this function) *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-01 11:25:28 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-01 11:25:28 - ERROR: failed to build lint kernel TB --- 2005-11-01 11:25:28 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 11:43:09 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 262D316A41F for ; Tue, 1 Nov 2005 11:43:09 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id D028043D48 for ; Tue, 1 Nov 2005 11:43:08 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id C6E9146B04; Tue, 1 Nov 2005 06:43:07 -0500 (EST) Date: Tue, 1 Nov 2005 11:43:07 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Szilveszter Adam In-Reply-To: <20051101112303.GB51552@momo.buza.adamsfamily.xx> Message-ID: <20051101114237.L45155@fledge.watson.org> References: <20051101070259.GC18710@wantadilla.lemis.com> <4367150C.4030508@mawer.org> <20051101073157.GE18710@wantadilla.lemis.com> <20051101112303.GB51552@momo.buza.adamsfamily.xx> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: Really poor performance on /dev/ttyv* only X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 11:43:09 -0000 On Tue, 1 Nov 2005, Szilveszter Adam wrote: > On Tue, Nov 01, 2005 at 06:01:57PM +1030, Greg 'groggy' Lehey wrote: >> I'd guess that this is a different situation. FWIW, the Inspiron >> series are laptops, and this is at the keyboard. The machine is brand >> new, and I've never had another version of FreeBSD on it, but I >> suspect it's -CURRENT rather than the laptop. > > FWIW, I also see slugishness on my Toshiba Satellite Pro 4200 series > with yesterday's -CURRENT, it concerns not only keyboard input but also > eg sorting of my mail spool (mbox format) in mutt and changing between > messages etc. Interestingly enough, network activity is not affected. > However, this isn't new, I have seen it also with -CURRENT from > September. > > I use SCHED_ULE as the scheduler, if that matters. I guess it matters primarily if the problem doesn't occur if you use SCHED_4BSD. :-) Could you give that a try and see? Robert N M Watson From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 13:00:22 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 303F916A421; Tue, 1 Nov 2005 13:00:22 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA07443D49; Tue, 1 Nov 2005 13:00:21 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id jA1D0KpW030238; Tue, 1 Nov 2005 08:00:20 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id jA1D0K7J032237; Tue, 1 Nov 2005 08:00:20 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 5AA677302F; Tue, 1 Nov 2005 08:00:20 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051101130020.5AA677302F@freebsd-current.sentex.ca> Date: Tue, 1 Nov 2005 08:00:20 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 13:00:22 -0000 TB --- 2005-11-01 11:25:28 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-11-01 11:25:28 - starting HEAD tinderbox run for i386/i386 TB --- 2005-11-01 11:25:28 - cleaning the object tree TB --- 2005-11-01 11:26:02 - checking out the source tree TB --- 2005-11-01 11:26:02 - cd /tinderbox/HEAD/i386/i386 TB --- 2005-11-01 11:26:02 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-11-01 11:32:42 - building world (CFLAGS=-O2 -pipe) TB --- 2005-11-01 11:32:42 - cd /src TB --- 2005-11-01 11:32:42 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-11-01 12:37:22 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-11-01 12:37:22 - cd /src TB --- 2005-11-01 12:37:22 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Tue Nov 1 12:37:22 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Tue Nov 1 12:55:42 UTC 2005 TB --- 2005-11-01 12:55:42 - generating LINT kernel config TB --- 2005-11-01 12:55:42 - cd /src/sys/i386/conf TB --- 2005-11-01 12:55:42 - /usr/bin/make -B LINT TB --- 2005-11-01 12:55:43 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-11-01 12:55:43 - cd /src TB --- 2005-11-01 12:55:43 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Nov 1 12:55:43 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /src/sys/dev/acpica/acpi_hpet.c: In function `acpi_hpet_attach': /src/sys/dev/acpica/acpi_hpet.c:94: error: `_COMPONENT' undeclared (first use in this function) /src/sys/dev/acpica/acpi_hpet.c:94: error: (Each undeclared identifier is reported only once /src/sys/dev/acpica/acpi_hpet.c:94: error: for each function it appears in.) /src/sys/dev/acpica/acpi_hpet.c:94: error: `_THIS_MODULE' undeclared (first use in this function) /src/sys/dev/acpica/acpi_hpet.c: In function `acpi_hpet_detach': /src/sys/dev/acpica/acpi_hpet.c:159: error: `_COMPONENT' undeclared (first use in this function) /src/sys/dev/acpica/acpi_hpet.c:159: error: `_THIS_MODULE' undeclared (first use in this function) *** Error code 1 Stop in /obj/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-01 13:00:20 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-01 13:00:20 - ERROR: failed to build lint kernel TB --- 2005-11-01 13:00:20 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 14:53:38 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F6EA16A420; Mon, 31 Oct 2005 14:53:38 +0000 (GMT) (envelope-from toli@proact.no) Received: from nospam.internal.proact.no (mail.proact.no [81.191.140.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B5AD43D46; Mon, 31 Oct 2005 14:53:36 +0000 (GMT) (envelope-from toli@proact.no) Received: by noexchange55.internal.proact.no with Internet Mail Service (5.5.2653.19)id ; Mon, 31 Oct 2005 15:51:59 +0100 Received: from TOM ([193.71.23.93]) by nopro01.internal.proact.no with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)id L5AXHAW7; Mon, 31 Oct 2005 15:53:25 +0100 Date: Mon, 31 Oct 2005 15:53:25 +0100 (CET) From: Tom.Lislegaard@proact.no X-X-Sender: tl@tom.internal.proact.no To: freebsd-current@freebsd.org, freebsd-mobile@freebsd.org Message-ID: <20051031154521.G3650@tom.internal.proact.no> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-imss-version: 2.033 X-imss-result: Passed X-imss-scores: Clean:63.00514 C:2 M:3 S:5 R:5 X-imss-settings: Baseline:3 C:1 M:1 S:1 R:1 (0.5000 0.5000) X-Mailman-Approved-At: Tue, 01 Nov 2005 13:15:03 +0000 Cc: Subject: 6.0RC1 - enabling synaptics touchpad freezes machine X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 14:53:38 -0000 I try to enable touchpad support on an Acer Travelmate 8104 by setting hw.psm.synaptics_support="1" in loader.conf. After that any access to psm0 seems to hang the machine solid. For instance running 'moused -p /dev/psm0' or starting Xorg with psm0 as mousedevice freezes the machine immediately, and I have to use the power button to recover. This is an out-of-the-box 6.0RC1 Generic kernel. The only other change I've done is to disable acpi, though that doesn't change anything regarding the touchpad problem. Is anyone else seeing something similar (and preferably have a solution)? Output of dmesg is found below. -tom 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 6.0-RC1 #0: Sun Oct 9 20:32:57 UTC 2005 root@x64.samsco.home:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) M processor 2.00GHz (1995.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6d8 Stepping = 8 Features=0xafe9fbff Features2=0x180 AMD Features=0x100000 real memory = 1072168960 (1022 MB) avail memory = 1040318464 (992 MB) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: pcibus 0 on motherboard pci0: on pcib0 pcib1: irq 10 at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pci0: at device 27.0 (no driver attached) pcib2: irq 10 at device 28.0 on pci0 pci9: on pcib2 pcib3: irq 10 at device 28.1 on pci0 pci10: on pcib3 pcib4: irq 11 at device 28.2 on pci0 pci2: on pcib4 uhci0: port 0x1800-0x181f irq 11 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 0x1820-0x183f irq 11 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 0x1840-0x185f irq 11 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 uhci3: port 0x1860-0x187f irq 10 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xc8004000-0xc80043ff irq 11 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered pcib5: at device 30.0 on pci0 pci6: on pcib5 pci6: at device 3.0 (no driver attached) bge0: mem 0xc8200000-0xc820ffff irq 10 at device 6.0 on pci6 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:c0:9f:c0:73:7a fwohci0: mem 0xc8215000-0xc82157ff,0xc8210000-0xc8213fff irq 11 at device 7.0 on pci6 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:c0:9f:00:00:67:04:ee fwohci0: Phy 1394a available S400, 1 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:c0:9f:67:04:ee fwe0: Ethernet address: 02:c0:9f:67:04:ee fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc000ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) cbb0: mem 0xc8216000-0xc8216fff irq 11 at device 9.0 on pci6 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb1: mem 0xc8217000-0xc8217fff irq 10 at device 9.1 on pci6 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 pci6: at device 9.2 (no driver attached) cbb2: at device 9.3 on pci6 cardbus2: on cbb2 pccard2: <16-bit PCCard bus> on cbb2 cbb: Unable to map IRQ... device_attach: cbb2 attach returned 12 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x18a0-0x18af at device 31.2 on pci0 atapci0: failed to enable memory mapping! ata0: on atapci0 ata1: on atapci0 pci0: at device 31.3 (no driver attached) pmtimer0 on isa0 orm0: at iomem 0xe0000-0xe17ff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Synaptics Touchpad, device ID 0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 8250 or not responding sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (port) unknown: can't assign resources (memory) unknown: can't assign resources (memory) unknown: can't assign resources (irq) unknown: can't assign resources (port) ppc1: parallel port not found. ugen0: Broadcom BCM2035, rev 1.10/1.00, addr 2 Timecounter "TSC" frequency 1995015913 Hz quality 800 Timecounters tick every 1.000 msec ad0: 95396MB at ata0-master SATA150 acd0: FAILURE - MODE_SENSE_BIG timed out acd0: DVDR at ata1-master UDMA33 Trying to mount root from ufs:/dev/ad0s2a bge0: link state changed to UP From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 15:08:43 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AAB816A41F; Mon, 31 Oct 2005 15:08:43 +0000 (GMT) (envelope-from gemini@geminix.org) Received: from gen129.n001.c02.escapebox.net (gen129.n001.c02.escapebox.net [213.73.91.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF77143D48; Mon, 31 Oct 2005 15:08:42 +0000 (GMT) (envelope-from gemini@geminix.org) Message-ID: <4366336E.8070601@geminix.org> Date: Mon, 31 Oct 2005 16:08:30 +0100 From: Uwe Doering Organization: Private UNIX Site User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051029 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Maxim Konovalov References: <2b22951e0510302128q571a3c1se111262e88ae19bb@mail.gmail.com> <20051031144056.A92356@mp2.macomnet.net> <20051031162438.I554@is.park.rambler.ru> <20051031170805.T94695@mp2.macomnet.net> In-Reply-To: <20051031170805.T94695@mp2.macomnet.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Received: from gemini by geminix.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.52 (FreeBSD)) id 1EWbGx-0001Um-My; Mon, 31 Oct 2005 16:08:31 +0100 X-Mailman-Approved-At: Tue, 01 Nov 2005 13:15:03 +0000 Cc: Edwin Groothuis , Igor Sysoev , bug-followup@freebsd.org, "Cai, Quanqing" , freebsd-current@freebsd.org Subject: Re: kern/67919: Why nobody take serious to fix this bug? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Oct 2005 15:08:43 -0000 Maxim Konovalov wrote: > [...] > >>>I was told the patch is incorrect. It works in certain cases but >>>incorrect in general. >> >>Why is it incorrect ? I'm using it for year. > > Because you can't just throw away any chunk of data (e.g. it could be > a meta-data) without a risk to damage a filesystem. I wonder, could it really be meta-data? I was under the impression that meta-data is a filesystem property and is therefore dealt with in the filesystem code, through i/o buffers. Isn't the VM pager responsible for handling object contents (files etc.), only? If so, it would be unfortunate to throw away pages of data but it certainly wouldn't damage the filesystem. As to our own experience: Since I provided the patch a year ago or so we've had tons of users bumping against the space limit of their respective disk containers (with the VM pager involved: Berkeley DB 3, for instance) but not a single instance where the filesystem had been damaged by this incident. This is on the 4.x branch. Uwe -- Uwe Doering | EscapeBox - Managed On-Demand UNIX Servers gemini@geminix.org | http://www.escapebox.net From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 13:53:58 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C599616A421 for ; Tue, 1 Nov 2005 13:53:58 +0000 (GMT) (envelope-from vincent@xtra-net.org) Received: from relay.xtra-net.org (cable-195-162-200-89.customer.tvd.be [195.162.200.89]) by mx1.FreeBSD.org (Postfix) with SMTP id ABB3F43D6B for ; Tue, 1 Nov 2005 13:53:45 +0000 (GMT) (envelope-from vincent@xtra-net.org) Received: (qmail 97058 invoked from network); 1 Nov 2005 13:53:42 -0000 Received: from wbedllfs.xtra-net.org (192.168.1.21) by 0 with SMTP; 1 Nov 2005 13:53:42 -0000 From: Vincent Blondel To: current@freebsd.org Content-Type: text/plain Date: Tue, 01 Nov 2005 14:52:15 +0100 Message-Id: <1130853135.5987.18.camel@wbedllfs.xtra-net.org> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Subject: kernel question ??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vincent@xtra-net.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 13:53:58 -0000 Hello all, Sorry for this, maybe stupid, question but I more often compile kernels on Linux platforms. So, in linux world, there is a very simple way to compile devices as modules and I am now trying to do this same feature in my FreeBSD kernel ( 7.0-current ) for all network devices ( all /boot/kernel/if_xxx.so ) that I would like to (un)load when it is necessary. I don't know if it is the right way to do it but I removed all network devices from my kernel config file (see below) but I get some problems when compiling the kernel (see below). Could you please help me to solve this problem ? Regards Vincent ----- kernel config file RELENG_6_i686 machine i386 cpu I686_CPU ident RELENG_6_i686 # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols options SC_DISABLE_REBOOT #options SCHED_ULE # ULE scheduler options SCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption 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 COMPAT_FREEBSD5 # Compatible with FreeBSD5 options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING 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. # Debugging for use in -current options KDB # Enable kernel debugger support. options DDB # Support DDB. options GDB # Support remote GDB. options INVARIANTS # Enable calls of extra sanity checking options INVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS options WITNESS # Enable checks to detect deadlocks and cycles options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed # To make an SMP kernel, the next two lines are needed #options SMP # Symmetric MultiProcessor Kernel device apic # I/O APIC # Bus support. 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 ispfw # Firmware for QLogic HBAs- normally a module device mpt # LSI-Logic MPT-Fusion #device ncr # NCR/Symbios Logic device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') device trm # Tekram DC395U/UW/F DC315U adapters device adv # Advansys SCSI adapters device adw # Advansys wide SCSI adapters device aha # Adaptec 154x SCSI adapters device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. device bt # Buslogic/Mylex MultiMaster SCSI adapters device ncv # NCR 53C500 device nsp # Workbit Ninja SCSI-3 device stg # TMC 18C30/18C50 # SCSI peripherals device scbus # SCSI bus (required for SCSI) device ch # SCSI media changers device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) device ses # SCSI Environmental Services (and SAF-TE) # RAID controllers interfaced to the SCSI subsystem device amr # AMI MegaRAID device arcmsr # Areca SATA II RAID device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID device ciss # Compaq Smart RAID 5* device dpt # DPT Smartcache III, IV - See NOTES for options device hptmv # Highpoint RocketRAID 182x device 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 # 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 # ISA devices that use the old ISA shims #device le # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support device sl # Kernel SLIP device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device ural # Ralink Technology RT2500USB wireless NICs device urio # Diamond Rio 500 MP3 player device uscanner # Scanners # USB Ethernet, requires miibus device aue # ADMtek USB Ethernet device axe # ASIX Electronics USB Ethernet device cdce # Generic USB over Ethernet device cue # CATC USB Ethernet device kue # Kawasaki LSI USB Ethernet device rue # RealTek RTL8150 USB Ethernet # FireWire support device firewire # FireWire bus code device sbp # SCSI over FireWire (Requires scbus and da) device fwe # Ethernet over FireWire (non-standard!) ----- make buildkernel KERNCONF=RELENG_6_i686 MAKE=/usr/obj/usr/src/make.i386/make sh /usr/src/sys/conf/newvers.sh RELENG_6_i686 cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -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 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror vers.c linking kernel.debug if_aue.o(.text+0x96d): In function `aue_attach': /usr/src/sys/dev/usb/if_aue.c:749: undefined reference to `mii_phy_probe' if_aue.o(.text+0xcfe): In function `aue_tick': /usr/src/sys/dev/usb/if_aue.c:1032: undefined reference to `mii_tick' if_aue.o(.text+0x1051): In function `aue_init': /usr/src/sys/dev/usb/if_aue.c:1198: undefined reference to `mii_mediachg' if_aue.o(.text+0x1156): In function `aue_ifmedia_upd': /usr/src/sys/dev/usb/if_aue.c:1263: undefined reference to `mii_phy_reset' if_aue.o(.text+0x1166):/usr/src/sys/dev/usb/if_aue.c:1265: undefined reference to `mii_mediachg' if_aue.o(.text+0x1191): In function `aue_ifmedia_sts': /usr/src/sys/dev/usb/if_aue.c:1279: undefined reference to `mii_pollstat' if_aue.o(.data+0x90): In function `aue_csr_read_2': /usr/src/sys/dev/usb/if_aue.c:294: undefined reference to `miibus_readreg_desc' if_aue.o(.data+0x98):/usr/src/sys/dev/usb/if_aue.c:295: undefined reference to `miibus_writereg_desc' if_aue.o(.data+0xa0):/usr/src/sys/dev/usb/if_aue.c:296: undefined reference to `miibus_statchg_desc' if_aue.o(.data+0x114): In function `aue_csr_write_1': /usr/src/sys/dev/usb/if_aue.c:325: undefined reference to `miibus_driver' if_aue.o(.data+0x118):/usr/src/sys/dev/usb/if_aue.c:325: undefined reference to `miibus_devclass' if_axe.o(.text+0x1fe): In function `axe_ifmedia_upd': /usr/src/sys/dev/usb/if_axe.c:296: undefined reference to `mii_phy_reset' if_axe.o(.text+0x20e):/usr/src/sys/dev/usb/if_axe.c:298: undefined reference to `mii_mediachg' if_axe.o(.text+0x239): In function `axe_ifmedia_sts': /usr/src/sys/dev/usb/if_axe.c:312: undefined reference to `mii_pollstat' if_axe.o(.text+0x6a1): In function `axe_attach': /usr/src/sys/dev/usb/if_axe.c:509: undefined reference to `mii_phy_probe' if_axe.o(.text+0x9ea): In function `axe_tick': /usr/src/sys/dev/usb/if_axe.c:739: undefined reference to `mii_tick' if_axe.o(.data+0x70): In function `axe_cmd': /usr/src/sys/dev/usb/if_axe.c:198: undefined reference to `miibus_readreg_desc' if_axe.o(.data+0x78):/usr/src/sys/dev/usb/if_axe.c:201: undefined reference to `miibus_writereg_desc' if_axe.o(.data+0x80):/usr/src/sys/dev/usb/if_axe.c:204: undefined reference to `miibus_statchg_desc' if_axe.o(.data+0xf4): In function `axe_miibus_readreg': /usr/src/sys/dev/usb/if_axe.c:234: undefined reference to `miibus_driver' if_axe.o(.data+0xf8):/usr/src/sys/dev/usb/if_axe.c:234: undefined reference to `miibus_devclass' if_ural.o(.text+0x3bb): In function `ural_attach': /usr/src/sys/dev/usb/if_ural.c:458: undefined reference to `ieee80211_ieee2mhz' if_ural.o(.text+0x3ef):/usr/src/sys/dev/usb/if_ural.c:463: undefined reference to `ieee80211_ieee2mhz' if_ural.o(.text+0x427):/usr/src/sys/dev/usb/if_ural.c:468: undefined reference to `ieee80211_ieee2mhz' if_ural.o(.text+0x4bb):/usr/src/sys/dev/usb/if_ural.c:480: undefined reference to `ieee80211_ieee2mhz' if_ural.o(.text+0x4e2):/usr/src/sys/dev/usb/if_ural.c:487: undefined reference to `ieee80211_ifattach' if_ural.o(.text+0x513):/usr/src/sys/dev/usb/if_ural.c:493: undefined reference to `ieee80211_media_status' if_ural.o(.text+0x51e):/usr/src/sys/dev/usb/if_ural.c:493: undefined reference to `ieee80211_media_init' if_ural.o(.text+0x580):/usr/src/sys/dev/usb/if_ural.c:507: undefined reference to `ieee80211_announce' if_ural.o(.text+0x628): In function `ural_detach': /usr/src/sys/dev/usb/if_ural.c:535: undefined reference to `ieee80211_ifdetach' if_ural.o(.text+0x73a): In function `ural_free_tx_list': /usr/src/sys/dev/usb/if_ural.c:595: undefined reference to `ieee80211_free_node' if_ural.o(.text+0x8da): In function `ural_media_change': /usr/src/sys/dev/usb/if_ural.c:673: undefined reference to `ieee80211_media_change' if_ural.o(.text+0x954): In function `ural_next_scan': /usr/src/sys/dev/usb/if_ural.c:699: undefined reference to `ieee80211_next_scan' if_ural.o(.text+0xabf): In function `ural_task': /usr/src/sys/dev/usb/if_ural.c:756: undefined reference to `ieee80211_beacon_alloc' if_ural.o(.text+0xc1f): In function `ural_txeof': /usr/src/sys/dev/usb/if_ural.c:826: undefined reference to `ieee80211_free_node' if_ural.o(.text+0xd45): In function `ural_rxeof': /usr/src/sys/dev/usb/if_ural.c:890: undefined reference to `ieee80211_find_rxnode' if_ural.o(.text+0xd5b):/usr/src/sys/dev/usb/if_ural.c:893: undefined reference to `ieee80211_input' if_ural.o(.text+0xd63):/usr/src/sys/dev/usb/if_ural.c:896: undefined reference to `ieee80211_free_node' if_ural.o(.text+0x130c): In function `ural_tx_data': /usr/src/sys/dev/usb/if_ural.c:1218: undefined reference to `ieee80211_crypto_encap' if_ural.o(.text+0x179c): In function `ural_start': /usr/src/sys/dev/usb/if_ural.c:1321: undefined reference to `ieee80211_find_txnode' if_ural.o(.text+0x17eb):/usr/src/sys/dev/usb/if_ural.c:1328: undefined reference to `ieee80211_encap' if_ural.o(.text+0x17fa):/usr/src/sys/dev/usb/if_ural.c:1330: undefined reference to `ieee80211_free_node' if_ural.o(.text+0x1833):/usr/src/sys/dev/usb/if_ural.c:1338: undefined reference to `ieee80211_free_node' if_ural.o(.text+0x18e8): In function `ural_watchdog': /usr/src/sys/dev/usb/if_ural.c:1370: undefined reference to `ieee80211_watchdog' if_ural.o(.text+0x19c4): In function `ural_ioctl': /usr/src/sys/dev/usb/if_ural.c:1417: undefined reference to `ieee80211_ioctl' if_ural.o(.text+0x1e30): In function `ural_set_chan': /usr/src/sys/dev/usb/if_ural.c:1606: undefined reference to `ieee80211_chan2ieee' if_rue.o(.text+0x833): In function `rue_attach': /usr/src/sys/dev/usb/if_rue.c:689: undefined reference to `mii_phy_probe' if_rue.o(.text+0xc8a): In function `rue_tick': /usr/src/sys/dev/usb/if_rue.c:970: undefined reference to `mii_tick' if_rue.o(.text+0xfa4): In function `rue_init': /usr/src/sys/dev/usb/if_rue.c:1145: undefined reference to `mii_mediachg' if_rue.o(.text+0x10f6): In function `rue_ifmedia_upd': /usr/src/sys/dev/usb/if_rue.c:1210: undefined reference to `mii_phy_reset' if_rue.o(.text+0x1106):/usr/src/sys/dev/usb/if_rue.c:1212: undefined reference to `mii_mediachg' if_rue.o(.text+0x1131): In function `rue_ifmedia_sts': /usr/src/sys/dev/usb/if_rue.c:1227: undefined reference to `mii_pollstat' if_rue.o(.data+0x50): In function `rue_read_mem': /usr/src/sys/dev/usb/if_rue.c:231: undefined reference to `miibus_readreg_desc' if_rue.o(.data+0x58):/usr/src/sys/dev/usb/if_rue.c:241: undefined reference to `miibus_writereg_desc' if_rue.o(.data+0x60):/usr/src/sys/dev/usb/if_rue.c:235: undefined reference to `miibus_statchg_desc' if_rue.o(.data+0xd4): In function `rue_write_mem': /usr/src/sys/dev/usb/if_rue.c:261: undefined reference to `miibus_driver' if_rue.o(.data+0xd8):/usr/src/sys/dev/usb/if_rue.c:261: undefined reference to `miibus_devclass' *** Error code 1 Stop in /usr/obj/usr/src/sys/RELENG_6_i686. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 14:04:10 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CDC2116A420 for ; Tue, 1 Nov 2005 14:04:10 +0000 (GMT) (envelope-from konfer@mikulas.com) Received: from s1.vhost.cz (s1.vhost.cz [82.208.27.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49D7843D49 for ; Tue, 1 Nov 2005 14:04:02 +0000 (GMT) (envelope-from konfer@mikulas.com) Received: (qmail 57130 invoked by alias); 1 Nov 2005 15:04:00 +0100 Received: from unknown (HELO localhost) (127.10.10.10) by s1.vhost.cz with SMTP; 1 Nov 2005 15:04:00 +0100 Received: from unknown ([127.0.0.1]) by localhost (s1.vhost.cz [127.0.0.1]) (amavisd-new, port 10628) id 56387-08 for ; Tue, 1 Nov 2005 15:03:56 +0100 (CET) Received: from unknown (HELO ?172.19.13.144?) (jiri@mikulas.com@195.122.204.153) by s1.vhost.cz with AES256-SHA encrypted SMTP; 1 Nov 2005 15:03:56 +0100 Message-ID: <436775CC.7070402@mikulas.com> Date: Tue, 01 Nov 2005 15:03:56 +0100 From: Jiri Mikulas User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050429) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org References: <1130853135.5987.18.camel@wbedllfs.xtra-net.org> In-Reply-To: <1130853135.5987.18.camel@wbedllfs.xtra-net.org> Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at vhost.cz Cc: Subject: Re: kernel question ??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 14:04:10 -0000 hello there are still USB network devices # USB Ethernet, requires miibus device aue # ADMtek USB Ethernet device axe # ASIX Electronics USB Ethernet device cdce # Generic USB over Ethernet device cue # CATC USB Ethernet device kue # Kawasaki LSI USB Ethernet device rue # RealTek RTL8150 USB Ethernet try to comment them out maybe also device fwe # Ethernet over FireWire (non-standard!) don't forget to compile required miibus module Jiri Vincent Blondel wrote: >Hello all, > >Sorry for this, maybe stupid, question but I more often compile kernels >on Linux platforms. > >So, in linux world, there is a very simple way to compile devices as >modules and I am now trying to do this same feature in my FreeBSD kernel >( 7.0-current ) for all network devices ( all /boot/kernel/if_xxx.so ) >that I would like to (un)load when it is necessary. > >I don't know if it is the right way to do it but I removed all network >devices from my kernel config file (see below) but I get some problems >when compiling the kernel (see below). > >Could you please help me to solve this problem ? > >Regards >Vincent > >----- > >kernel config file RELENG_6_i686 > >machine i386 >cpu I686_CPU >ident RELENG_6_i686 > ># To statically compile in device wiring instead of /boot/device.hints >#hints "GENERIC.hints" # Default places to look for devices. > >makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols > >options SC_DISABLE_REBOOT > >#options SCHED_ULE # ULE scheduler >options SCHED_4BSD # 4BSD scheduler >options PREEMPTION # Enable kernel thread preemption >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 COMPAT_FREEBSD5 # Compatible with FreeBSD5 >options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI >options KTRACE # ktrace(1) support >options SYSVSHM # SYSV-style shared memory >options SYSVMSG # SYSV-style message queues >options SYSVSEM # SYSV-style semaphores >options _KPOSIX_PRIORITY_SCHEDULING >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. > ># Debugging for use in -current >options KDB # Enable kernel debugger support. >options DDB # Support DDB. >options GDB # Support remote GDB. >options INVARIANTS # Enable calls of extra sanity checking >options INVARIANT_SUPPORT # Extra sanity checks of internal structures, >required by INVARIANTS >options WITNESS # Enable checks to detect deadlocks and cycles >options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed > ># To make an SMP kernel, the next two lines are needed >#options SMP # Symmetric MultiProcessor Kernel >device apic # I/O APIC > ># Bus support. >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 ispfw # Firmware for QLogic HBAs- normally a module >device mpt # LSI-Logic MPT-Fusion >#device ncr # NCR/Symbios Logic >device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') >device trm # Tekram DC395U/UW/F DC315U adapters > >device adv # Advansys SCSI adapters >device adw # Advansys wide SCSI adapters >device aha # Adaptec 154x SCSI adapters >device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. >device bt # Buslogic/Mylex MultiMaster SCSI adapters > >device ncv # NCR 53C500 >device nsp # Workbit Ninja SCSI-3 >device stg # TMC 18C30/18C50 > ># SCSI peripherals >device scbus # SCSI bus (required for SCSI) >device ch # SCSI media changers >device da # Direct Access (disks) >device sa # Sequential Access (tape etc) >device cd # CD >device pass # Passthrough device (direct SCSI access) >device ses # SCSI Environmental Services (and SAF-TE) > ># RAID controllers interfaced to the SCSI subsystem >device amr # AMI MegaRAID >device arcmsr # Areca SATA II RAID >device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID >device ciss # Compaq Smart RAID 5* >device dpt # DPT Smartcache III, IV - See NOTES for options >device hptmv # Highpoint RocketRAID 182x >device 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 > ># 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 > ># ISA devices that use the old ISA shims >#device le > ># Pseudo devices. >device loop # Network loopback >device random # Entropy device >device ether # Ethernet support >device sl # Kernel SLIP >device ppp # Kernel PPP >device tun # Packet tunnel. >device pty # Pseudo-ttys (telnet etc) >device md # Memory "disks" >device gif # IPv6 and IPv4 tunneling >device faith # IPv6-to-IPv4 relaying (translation) > ># The `bpf' device enables the Berkeley Packet Filter. ># Be aware of the administrative consequences of enabling this! ># Note that 'bpf' is required for DHCP. >device bpf # Berkeley packet filter > ># USB support >device uhci # UHCI PCI->USB interface >device ohci # OHCI PCI->USB interface >device ehci # EHCI PCI->USB interface (USB 2.0) >device usb # USB Bus (required) >#device udbp # USB Double Bulk Pipe devices >device ugen # Generic >device uhid # "Human Interface Devices" >device ukbd # Keyboard >device ulpt # Printer >device umass # Disks/Mass storage - Requires scbus and da >device ums # Mouse >device ural # Ralink Technology RT2500USB wireless NICs >device urio # Diamond Rio 500 MP3 player >device uscanner # Scanners ># USB Ethernet, requires miibus >device aue # ADMtek USB Ethernet >device axe # ASIX Electronics USB Ethernet >device cdce # Generic USB over Ethernet >device cue # CATC USB Ethernet >device kue # Kawasaki LSI USB Ethernet >device rue # RealTek RTL8150 USB Ethernet > ># FireWire support >device firewire # FireWire bus code >device sbp # SCSI over FireWire (Requires scbus and da) >device fwe # Ethernet over FireWire (non-standard!) > >----- > >make buildkernel KERNCONF=RELENG_6_i686 > >MAKE=/usr/obj/usr/src/make.i386/make sh /usr/src/sys/conf/newvers.sh >RELENG_6_i686 >cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs >-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline >-Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. >-I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL >-DHAVE_KERNEL_OPTION_HEADERS -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 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 >-mno-sse3 -ffreestanding -Werror vers.c >linking kernel.debug >if_aue.o(.text+0x96d): In function `aue_attach': >/usr/src/sys/dev/usb/if_aue.c:749: undefined reference to >`mii_phy_probe' >if_aue.o(.text+0xcfe): In function `aue_tick': >/usr/src/sys/dev/usb/if_aue.c:1032: undefined reference to `mii_tick' >if_aue.o(.text+0x1051): In function `aue_init': >/usr/src/sys/dev/usb/if_aue.c:1198: undefined reference to >`mii_mediachg' >if_aue.o(.text+0x1156): In function `aue_ifmedia_upd': >/usr/src/sys/dev/usb/if_aue.c:1263: undefined reference to >`mii_phy_reset' >if_aue.o(.text+0x1166):/usr/src/sys/dev/usb/if_aue.c:1265: undefined >reference to `mii_mediachg' >if_aue.o(.text+0x1191): In function `aue_ifmedia_sts': >/usr/src/sys/dev/usb/if_aue.c:1279: undefined reference to >`mii_pollstat' >if_aue.o(.data+0x90): In function `aue_csr_read_2': >/usr/src/sys/dev/usb/if_aue.c:294: undefined reference to >`miibus_readreg_desc' >if_aue.o(.data+0x98):/usr/src/sys/dev/usb/if_aue.c:295: undefined >reference to `miibus_writereg_desc' >if_aue.o(.data+0xa0):/usr/src/sys/dev/usb/if_aue.c:296: undefined >reference to `miibus_statchg_desc' >if_aue.o(.data+0x114): In function `aue_csr_write_1': >/usr/src/sys/dev/usb/if_aue.c:325: undefined reference to >`miibus_driver' >if_aue.o(.data+0x118):/usr/src/sys/dev/usb/if_aue.c:325: undefined >reference to `miibus_devclass' >if_axe.o(.text+0x1fe): In function `axe_ifmedia_upd': >/usr/src/sys/dev/usb/if_axe.c:296: undefined reference to >`mii_phy_reset' >if_axe.o(.text+0x20e):/usr/src/sys/dev/usb/if_axe.c:298: undefined >reference to `mii_mediachg' >if_axe.o(.text+0x239): In function `axe_ifmedia_sts': >/usr/src/sys/dev/usb/if_axe.c:312: undefined reference to `mii_pollstat' >if_axe.o(.text+0x6a1): In function `axe_attach': >/usr/src/sys/dev/usb/if_axe.c:509: undefined reference to >`mii_phy_probe' >if_axe.o(.text+0x9ea): In function `axe_tick': >/usr/src/sys/dev/usb/if_axe.c:739: undefined reference to `mii_tick' >if_axe.o(.data+0x70): In function `axe_cmd': >/usr/src/sys/dev/usb/if_axe.c:198: undefined reference to >`miibus_readreg_desc' >if_axe.o(.data+0x78):/usr/src/sys/dev/usb/if_axe.c:201: undefined >reference to `miibus_writereg_desc' >if_axe.o(.data+0x80):/usr/src/sys/dev/usb/if_axe.c:204: undefined >reference to `miibus_statchg_desc' >if_axe.o(.data+0xf4): In function `axe_miibus_readreg': >/usr/src/sys/dev/usb/if_axe.c:234: undefined reference to >`miibus_driver' >if_axe.o(.data+0xf8):/usr/src/sys/dev/usb/if_axe.c:234: undefined >reference to `miibus_devclass' >if_ural.o(.text+0x3bb): In function `ural_attach': >/usr/src/sys/dev/usb/if_ural.c:458: undefined reference to >`ieee80211_ieee2mhz' >if_ural.o(.text+0x3ef):/usr/src/sys/dev/usb/if_ural.c:463: undefined >reference to `ieee80211_ieee2mhz' >if_ural.o(.text+0x427):/usr/src/sys/dev/usb/if_ural.c:468: undefined >reference to `ieee80211_ieee2mhz' >if_ural.o(.text+0x4bb):/usr/src/sys/dev/usb/if_ural.c:480: undefined >reference to `ieee80211_ieee2mhz' >if_ural.o(.text+0x4e2):/usr/src/sys/dev/usb/if_ural.c:487: undefined >reference to `ieee80211_ifattach' >if_ural.o(.text+0x513):/usr/src/sys/dev/usb/if_ural.c:493: undefined >reference to `ieee80211_media_status' >if_ural.o(.text+0x51e):/usr/src/sys/dev/usb/if_ural.c:493: undefined >reference to `ieee80211_media_init' >if_ural.o(.text+0x580):/usr/src/sys/dev/usb/if_ural.c:507: undefined >reference to `ieee80211_announce' >if_ural.o(.text+0x628): In function `ural_detach': >/usr/src/sys/dev/usb/if_ural.c:535: undefined reference to >`ieee80211_ifdetach' >if_ural.o(.text+0x73a): In function `ural_free_tx_list': >/usr/src/sys/dev/usb/if_ural.c:595: undefined reference to >`ieee80211_free_node' >if_ural.o(.text+0x8da): In function `ural_media_change': >/usr/src/sys/dev/usb/if_ural.c:673: undefined reference to >`ieee80211_media_change' >if_ural.o(.text+0x954): In function `ural_next_scan': >/usr/src/sys/dev/usb/if_ural.c:699: undefined reference to >`ieee80211_next_scan' >if_ural.o(.text+0xabf): In function `ural_task': >/usr/src/sys/dev/usb/if_ural.c:756: undefined reference to >`ieee80211_beacon_alloc' >if_ural.o(.text+0xc1f): In function `ural_txeof': >/usr/src/sys/dev/usb/if_ural.c:826: undefined reference to >`ieee80211_free_node' >if_ural.o(.text+0xd45): In function `ural_rxeof': >/usr/src/sys/dev/usb/if_ural.c:890: undefined reference to >`ieee80211_find_rxnode' >if_ural.o(.text+0xd5b):/usr/src/sys/dev/usb/if_ural.c:893: undefined >reference to `ieee80211_input' >if_ural.o(.text+0xd63):/usr/src/sys/dev/usb/if_ural.c:896: undefined >reference to `ieee80211_free_node' >if_ural.o(.text+0x130c): In function `ural_tx_data': >/usr/src/sys/dev/usb/if_ural.c:1218: undefined reference to >`ieee80211_crypto_encap' >if_ural.o(.text+0x179c): In function `ural_start': >/usr/src/sys/dev/usb/if_ural.c:1321: undefined reference to >`ieee80211_find_txnode' >if_ural.o(.text+0x17eb):/usr/src/sys/dev/usb/if_ural.c:1328: undefined >reference to `ieee80211_encap' >if_ural.o(.text+0x17fa):/usr/src/sys/dev/usb/if_ural.c:1330: undefined >reference to `ieee80211_free_node' >if_ural.o(.text+0x1833):/usr/src/sys/dev/usb/if_ural.c:1338: undefined >reference to `ieee80211_free_node' >if_ural.o(.text+0x18e8): In function `ural_watchdog': >/usr/src/sys/dev/usb/if_ural.c:1370: undefined reference to >`ieee80211_watchdog' >if_ural.o(.text+0x19c4): In function `ural_ioctl': >/usr/src/sys/dev/usb/if_ural.c:1417: undefined reference to >`ieee80211_ioctl' >if_ural.o(.text+0x1e30): In function `ural_set_chan': >/usr/src/sys/dev/usb/if_ural.c:1606: undefined reference to >`ieee80211_chan2ieee' >if_rue.o(.text+0x833): In function `rue_attach': >/usr/src/sys/dev/usb/if_rue.c:689: undefined reference to >`mii_phy_probe' >if_rue.o(.text+0xc8a): In function `rue_tick': >/usr/src/sys/dev/usb/if_rue.c:970: undefined reference to `mii_tick' >if_rue.o(.text+0xfa4): In function `rue_init': >/usr/src/sys/dev/usb/if_rue.c:1145: undefined reference to >`mii_mediachg' >if_rue.o(.text+0x10f6): In function `rue_ifmedia_upd': >/usr/src/sys/dev/usb/if_rue.c:1210: undefined reference to >`mii_phy_reset' >if_rue.o(.text+0x1106):/usr/src/sys/dev/usb/if_rue.c:1212: undefined >reference to `mii_mediachg' >if_rue.o(.text+0x1131): In function `rue_ifmedia_sts': >/usr/src/sys/dev/usb/if_rue.c:1227: undefined reference to >`mii_pollstat' >if_rue.o(.data+0x50): In function `rue_read_mem': >/usr/src/sys/dev/usb/if_rue.c:231: undefined reference to >`miibus_readreg_desc' >if_rue.o(.data+0x58):/usr/src/sys/dev/usb/if_rue.c:241: undefined >reference to `miibus_writereg_desc' >if_rue.o(.data+0x60):/usr/src/sys/dev/usb/if_rue.c:235: undefined >reference to `miibus_statchg_desc' >if_rue.o(.data+0xd4): In function `rue_write_mem': >/usr/src/sys/dev/usb/if_rue.c:261: undefined reference to >`miibus_driver' >if_rue.o(.data+0xd8):/usr/src/sys/dev/usb/if_rue.c:261: undefined >reference to `miibus_devclass' >*** Error code 1 > >Stop in /usr/obj/usr/src/sys/RELENG_6_i686. >*** Error code 1 > >Stop in /usr/src. >*** Error code 1 > >Stop in /usr/src. > >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 14:13:00 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25F3416A41F for ; Tue, 1 Nov 2005 14:13:00 +0000 (GMT) (envelope-from lofi@freebsd.org) Received: from mail-in-01.arcor-online.net (mail-in-01.arcor-online.net [151.189.21.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B6BD43D45 for ; Tue, 1 Nov 2005 14:12:59 +0000 (GMT) (envelope-from lofi@freebsd.org) Received: from mail-in-04-z2.arcor-online.net (mail-in-04-z2.arcor-online.net [151.189.8.16]) by mail-in-01.arcor-online.net (Postfix) with ESMTP id 3F9AE4BFB1; Tue, 1 Nov 2005 15:12:58 +0100 (CET) Received: from mail-in-01.arcor-online.net (mail-in-01.arcor-online.net [151.189.21.41]) by mail-in-04-z2.arcor-online.net (Postfix) with ESMTP id 69952138C43; Tue, 1 Nov 2005 15:12:51 +0100 (CET) Received: from lofi.dyndns.org (dslb-084-061-136-063.pools.arcor-ip.net [84.61.136.63]) by mail-in-01.arcor-online.net (Postfix) with ESMTP id DBFBE4BFB1; Tue, 1 Nov 2005 15:12:57 +0100 (CET) Received: from kiste.my.domain (root@kiste.my.domain [192.168.8.4]) by lofi.dyndns.org (8.13.4/8.13.3) with ESMTP id jA1ECoJM013737 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 1 Nov 2005 15:12:51 +0100 (CET) (envelope-from lofi@freebsd.org) Received: from kiste.my.domain (lofi@localhost [127.0.0.1]) by kiste.my.domain (8.13.1/8.13.1) with ESMTP id jA1ECm48075119; Tue, 1 Nov 2005 15:12:48 +0100 (CET) (envelope-from lofi@freebsd.org) Received: from localhost (localhost [[UNIX: localhost]]) by kiste.my.domain (8.13.1/8.13.1/Submit) id jA1ECjdA074676; Tue, 1 Nov 2005 15:12:45 +0100 (CET) (envelope-from lofi@freebsd.org) X-Authentication-Warning: kiste.my.domain: lofi set sender to lofi@freebsd.org using -f From: Michael Nottebrock To: freebsd-current@freebsd.org, vincent@xtra-net.org Date: Tue, 1 Nov 2005 15:12:41 +0100 User-Agent: KMail/1.8.2 References: <1130853135.5987.18.camel@wbedllfs.xtra-net.org> In-Reply-To: <1130853135.5987.18.camel@wbedllfs.xtra-net.org> X-Face: =Ym$`&q\+S2X$4`X%x%6"L4>Y,$]<":'L%c9"#7#`2tb&E&wsN31on!N\)3BD[g<=?utf-8?q?=2EjnfV=5B=0A=093=23?=>XchLK,o; >bD>c:]^; :>0>vyZ.X[,63GW`&M>}nYnr]-Fp``,[[@lJ!QL|sfW!s)=?utf-8?q?A2!*=0A=09vNkB/=7CL-?=>&QdSbQg X-Virus-Scanned: by amavisd-new Cc: Subject: Re: kernel question ??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 14:13:00 -0000 --nextPart1534072.2tsUWG5fDW Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday, 1. November 2005 14:52, Vincent Blondel wrote: > I don't know if it is the right way to do it but I removed all network > devices from my kernel config file (see below) but I get some problems > when compiling the kernel (see below). > > Could you please help me to solve this problem ? Quoting from GENERIC: # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! =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 --nextPart1534072.2tsUWG5fDW Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDZ3fdXhc68WspdLARAsOcAJ9EISuIzf8WrQQseRahWGMubtCU9QCfbCdh BKLiafVGy4zl6R/YP8y9JAo= =7h/n -----END PGP SIGNATURE----- --nextPart1534072.2tsUWG5fDW-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 14:23:42 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7020F16A41F for ; Tue, 1 Nov 2005 14:23:42 +0000 (GMT) (envelope-from brian@aljex.com) Received: from s1tank.virtdom.com (s1tank.virtdom.com [216.240.101.50]) by mx1.FreeBSD.org (Postfix) with SMTP id E664E43D49 for ; Tue, 1 Nov 2005 14:23:41 +0000 (GMT) (envelope-from brian@aljex.com) Received: (qmail 79667 invoked by uid 89); 1 Nov 2005 14:51:06 -0000 Received: from ool-4355e580.dyn.optonline.net (HELO venti) (brian@aljex.com@67.85.229.128) by s1tank.virtdom.com with SMTP; 1 Nov 2005 14:51:06 -0000 Message-ID: <00cb01c5deef$d8d19110$931fa8c0@venti> From: "Brian K. White" To: References: <1130853135.5987.18.camel@wbedllfs.xtra-net.org> Date: Tue, 1 Nov 2005 09:23:36 -0500 Organization: Aljex Software 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: Subject: Re: kernel question ??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 14:23:42 -0000 ----- Original Message ----- From: "Vincent Blondel" To: Sent: Tuesday, November 01, 2005 8:52 AM Subject: kernel question ??? > Hello all, > > Sorry for this, maybe stupid, question but I more often compile kernels > on Linux platforms. > > So, in linux world, there is a very simple way to compile devices as > modules and I am now trying to do this same feature in my FreeBSD kernel > ( 7.0-current ) for all network devices ( all /boot/kernel/if_xxx.so ) > that I would like to (un)load when it is necessary. > > I don't know if it is the right way to do it but I removed all network > devices from my kernel config file (see below) but I get some problems > when compiling the kernel (see below). > > Could you please help me to solve this problem ? You took out device miibus Yet you left in these nic devices which require miibus, as stated right in the comment: # USB Ethernet, requires miibus device aue # ADMtek USB Ethernet device axe # ASIX Electronics USB Ethernet device cdce # Generic USB over Ethernet device cue # CATC USB Ethernet device kue # Kawasaki LSI USB Ethernet device rue # RealTek RTL8150 USB Ethernet Either take _all_ nic devices out and load what you want as modules in /boot/loader.conf (The modules still get built when you remove the devices from the kernel config.) /boot/loader.conf: miibus_load="YES" if_fxp_load="YES" Or put "device miibus" back in, along with any nic devices you'll actually use. I think it's even possible to load the nic driver as a module even when you are pxe booting via that nic. Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/ +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! > Regards > Vincent > > ----- > > kernel config file RELENG_6_i686 > > machine i386 > cpu I686_CPU > ident RELENG_6_i686 > > # To statically compile in device wiring instead of /boot/device.hints > #hints "GENERIC.hints" # Default places to look for devices. > > makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols > > options SC_DISABLE_REBOOT > > #options SCHED_ULE # ULE scheduler > options SCHED_4BSD # 4BSD scheduler > options PREEMPTION # Enable kernel thread preemption > 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 COMPAT_FREEBSD5 # Compatible with FreeBSD5 > options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI > options KTRACE # ktrace(1) support > options SYSVSHM # SYSV-style shared memory > options SYSVMSG # SYSV-style message queues > options SYSVSEM # SYSV-style semaphores > options _KPOSIX_PRIORITY_SCHEDULING > 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. > > # Debugging for use in -current > options KDB # Enable kernel debugger support. > options DDB # Support DDB. > options GDB # Support remote GDB. > options INVARIANTS # Enable calls of extra sanity checking > options INVARIANT_SUPPORT # Extra sanity checks of internal structures, > required by INVARIANTS > options WITNESS # Enable checks to detect deadlocks and cycles > options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed > > # To make an SMP kernel, the next two lines are needed > #options SMP # Symmetric MultiProcessor Kernel > device apic # I/O APIC > > # Bus support. > 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 ispfw # Firmware for QLogic HBAs- normally a module > device mpt # LSI-Logic MPT-Fusion > #device ncr # NCR/Symbios Logic > device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') > device trm # Tekram DC395U/UW/F DC315U adapters > > device adv # Advansys SCSI adapters > device adw # Advansys wide SCSI adapters > device aha # Adaptec 154x SCSI adapters > device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. > device bt # Buslogic/Mylex MultiMaster SCSI adapters > > device ncv # NCR 53C500 > device nsp # Workbit Ninja SCSI-3 > device stg # TMC 18C30/18C50 > > # SCSI peripherals > device scbus # SCSI bus (required for SCSI) > device ch # SCSI media changers > device da # Direct Access (disks) > device sa # Sequential Access (tape etc) > device cd # CD > device pass # Passthrough device (direct SCSI access) > device ses # SCSI Environmental Services (and SAF-TE) > > # RAID controllers interfaced to the SCSI subsystem > device amr # AMI MegaRAID > device arcmsr # Areca SATA II RAID > device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID > device ciss # Compaq Smart RAID 5* > device dpt # DPT Smartcache III, IV - See NOTES for options > device hptmv # Highpoint RocketRAID 182x > device 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 > > # 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 > > # ISA devices that use the old ISA shims > #device le > > # Pseudo devices. > device loop # Network loopback > device random # Entropy device > device ether # Ethernet support > device sl # Kernel SLIP > device ppp # Kernel PPP > device tun # Packet tunnel. > device pty # Pseudo-ttys (telnet etc) > device md # Memory "disks" > device gif # IPv6 and IPv4 tunneling > device faith # IPv6-to-IPv4 relaying (translation) > > # The `bpf' device enables the Berkeley Packet Filter. > # Be aware of the administrative consequences of enabling this! > # Note that 'bpf' is required for DHCP. > device bpf # Berkeley packet filter > > # USB support > device uhci # UHCI PCI->USB interface > device ohci # OHCI PCI->USB interface > device ehci # EHCI PCI->USB interface (USB 2.0) > device usb # USB Bus (required) > #device udbp # USB Double Bulk Pipe devices > device ugen # Generic > device uhid # "Human Interface Devices" > device ukbd # Keyboard > device ulpt # Printer > device umass # Disks/Mass storage - Requires scbus and da > device ums # Mouse > device ural # Ralink Technology RT2500USB wireless NICs > device urio # Diamond Rio 500 MP3 player > device uscanner # Scanners > # USB Ethernet, requires miibus > device aue # ADMtek USB Ethernet > device axe # ASIX Electronics USB Ethernet > device cdce # Generic USB over Ethernet > device cue # CATC USB Ethernet > device kue # Kawasaki LSI USB Ethernet > device rue # RealTek RTL8150 USB Ethernet > > # FireWire support > device firewire # FireWire bus code > device sbp # SCSI over FireWire (Requires scbus and da) > device fwe # Ethernet over FireWire (non-standard!) > > ----- > > make buildkernel KERNCONF=RELENG_6_i686 > > MAKE=/usr/obj/usr/src/make.i386/make sh /usr/src/sys/conf/newvers.sh > RELENG_6_i686 > cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. > -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL > -DHAVE_KERNEL_OPTION_HEADERS -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 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 > -mno-sse3 -ffreestanding -Werror vers.c > linking kernel.debug > if_aue.o(.text+0x96d): In function `aue_attach': > /usr/src/sys/dev/usb/if_aue.c:749: undefined reference to > `mii_phy_probe' > if_aue.o(.text+0xcfe): In function `aue_tick': > /usr/src/sys/dev/usb/if_aue.c:1032: undefined reference to `mii_tick' > if_aue.o(.text+0x1051): In function `aue_init': > /usr/src/sys/dev/usb/if_aue.c:1198: undefined reference to > `mii_mediachg' > if_aue.o(.text+0x1156): In function `aue_ifmedia_upd': > /usr/src/sys/dev/usb/if_aue.c:1263: undefined reference to > `mii_phy_reset' > if_aue.o(.text+0x1166):/usr/src/sys/dev/usb/if_aue.c:1265: undefined > reference to `mii_mediachg' > if_aue.o(.text+0x1191): In function `aue_ifmedia_sts': > /usr/src/sys/dev/usb/if_aue.c:1279: undefined reference to > `mii_pollstat' > if_aue.o(.data+0x90): In function `aue_csr_read_2': > /usr/src/sys/dev/usb/if_aue.c:294: undefined reference to > `miibus_readreg_desc' > if_aue.o(.data+0x98):/usr/src/sys/dev/usb/if_aue.c:295: undefined > reference to `miibus_writereg_desc' > if_aue.o(.data+0xa0):/usr/src/sys/dev/usb/if_aue.c:296: undefined > reference to `miibus_statchg_desc' > if_aue.o(.data+0x114): In function `aue_csr_write_1': > /usr/src/sys/dev/usb/if_aue.c:325: undefined reference to > `miibus_driver' > if_aue.o(.data+0x118):/usr/src/sys/dev/usb/if_aue.c:325: undefined > reference to `miibus_devclass' > if_axe.o(.text+0x1fe): In function `axe_ifmedia_upd': > /usr/src/sys/dev/usb/if_axe.c:296: undefined reference to > `mii_phy_reset' > if_axe.o(.text+0x20e):/usr/src/sys/dev/usb/if_axe.c:298: undefined > reference to `mii_mediachg' > if_axe.o(.text+0x239): In function `axe_ifmedia_sts': > /usr/src/sys/dev/usb/if_axe.c:312: undefined reference to `mii_pollstat' > if_axe.o(.text+0x6a1): In function `axe_attach': > /usr/src/sys/dev/usb/if_axe.c:509: undefined reference to > `mii_phy_probe' > if_axe.o(.text+0x9ea): In function `axe_tick': > /usr/src/sys/dev/usb/if_axe.c:739: undefined reference to `mii_tick' > if_axe.o(.data+0x70): In function `axe_cmd': > /usr/src/sys/dev/usb/if_axe.c:198: undefined reference to > `miibus_readreg_desc' > if_axe.o(.data+0x78):/usr/src/sys/dev/usb/if_axe.c:201: undefined > reference to `miibus_writereg_desc' > if_axe.o(.data+0x80):/usr/src/sys/dev/usb/if_axe.c:204: undefined > reference to `miibus_statchg_desc' > if_axe.o(.data+0xf4): In function `axe_miibus_readreg': > /usr/src/sys/dev/usb/if_axe.c:234: undefined reference to > `miibus_driver' > if_axe.o(.data+0xf8):/usr/src/sys/dev/usb/if_axe.c:234: undefined > reference to `miibus_devclass' > if_ural.o(.text+0x3bb): In function `ural_attach': > /usr/src/sys/dev/usb/if_ural.c:458: undefined reference to > `ieee80211_ieee2mhz' > if_ural.o(.text+0x3ef):/usr/src/sys/dev/usb/if_ural.c:463: undefined > reference to `ieee80211_ieee2mhz' > if_ural.o(.text+0x427):/usr/src/sys/dev/usb/if_ural.c:468: undefined > reference to `ieee80211_ieee2mhz' > if_ural.o(.text+0x4bb):/usr/src/sys/dev/usb/if_ural.c:480: undefined > reference to `ieee80211_ieee2mhz' > if_ural.o(.text+0x4e2):/usr/src/sys/dev/usb/if_ural.c:487: undefined > reference to `ieee80211_ifattach' > if_ural.o(.text+0x513):/usr/src/sys/dev/usb/if_ural.c:493: undefined > reference to `ieee80211_media_status' > if_ural.o(.text+0x51e):/usr/src/sys/dev/usb/if_ural.c:493: undefined > reference to `ieee80211_media_init' > if_ural.o(.text+0x580):/usr/src/sys/dev/usb/if_ural.c:507: undefined > reference to `ieee80211_announce' > if_ural.o(.text+0x628): In function `ural_detach': > /usr/src/sys/dev/usb/if_ural.c:535: undefined reference to > `ieee80211_ifdetach' > if_ural.o(.text+0x73a): In function `ural_free_tx_list': > /usr/src/sys/dev/usb/if_ural.c:595: undefined reference to > `ieee80211_free_node' > if_ural.o(.text+0x8da): In function `ural_media_change': > /usr/src/sys/dev/usb/if_ural.c:673: undefined reference to > `ieee80211_media_change' > if_ural.o(.text+0x954): In function `ural_next_scan': > /usr/src/sys/dev/usb/if_ural.c:699: undefined reference to > `ieee80211_next_scan' > if_ural.o(.text+0xabf): In function `ural_task': > /usr/src/sys/dev/usb/if_ural.c:756: undefined reference to > `ieee80211_beacon_alloc' > if_ural.o(.text+0xc1f): In function `ural_txeof': > /usr/src/sys/dev/usb/if_ural.c:826: undefined reference to > `ieee80211_free_node' > if_ural.o(.text+0xd45): In function `ural_rxeof': > /usr/src/sys/dev/usb/if_ural.c:890: undefined reference to > `ieee80211_find_rxnode' > if_ural.o(.text+0xd5b):/usr/src/sys/dev/usb/if_ural.c:893: undefined > reference to `ieee80211_input' > if_ural.o(.text+0xd63):/usr/src/sys/dev/usb/if_ural.c:896: undefined > reference to `ieee80211_free_node' > if_ural.o(.text+0x130c): In function `ural_tx_data': > /usr/src/sys/dev/usb/if_ural.c:1218: undefined reference to > `ieee80211_crypto_encap' > if_ural.o(.text+0x179c): In function `ural_start': > /usr/src/sys/dev/usb/if_ural.c:1321: undefined reference to > `ieee80211_find_txnode' > if_ural.o(.text+0x17eb):/usr/src/sys/dev/usb/if_ural.c:1328: undefined > reference to `ieee80211_encap' > if_ural.o(.text+0x17fa):/usr/src/sys/dev/usb/if_ural.c:1330: undefined > reference to `ieee80211_free_node' > if_ural.o(.text+0x1833):/usr/src/sys/dev/usb/if_ural.c:1338: undefined > reference to `ieee80211_free_node' > if_ural.o(.text+0x18e8): In function `ural_watchdog': > /usr/src/sys/dev/usb/if_ural.c:1370: undefined reference to > `ieee80211_watchdog' > if_ural.o(.text+0x19c4): In function `ural_ioctl': > /usr/src/sys/dev/usb/if_ural.c:1417: undefined reference to > `ieee80211_ioctl' > if_ural.o(.text+0x1e30): In function `ural_set_chan': > /usr/src/sys/dev/usb/if_ural.c:1606: undefined reference to > `ieee80211_chan2ieee' > if_rue.o(.text+0x833): In function `rue_attach': > /usr/src/sys/dev/usb/if_rue.c:689: undefined reference to > `mii_phy_probe' > if_rue.o(.text+0xc8a): In function `rue_tick': > /usr/src/sys/dev/usb/if_rue.c:970: undefined reference to `mii_tick' > if_rue.o(.text+0xfa4): In function `rue_init': > /usr/src/sys/dev/usb/if_rue.c:1145: undefined reference to > `mii_mediachg' > if_rue.o(.text+0x10f6): In function `rue_ifmedia_upd': > /usr/src/sys/dev/usb/if_rue.c:1210: undefined reference to > `mii_phy_reset' > if_rue.o(.text+0x1106):/usr/src/sys/dev/usb/if_rue.c:1212: undefined > reference to `mii_mediachg' > if_rue.o(.text+0x1131): In function `rue_ifmedia_sts': > /usr/src/sys/dev/usb/if_rue.c:1227: undefined reference to > `mii_pollstat' > if_rue.o(.data+0x50): In function `rue_read_mem': > /usr/src/sys/dev/usb/if_rue.c:231: undefined reference to > `miibus_readreg_desc' > if_rue.o(.data+0x58):/usr/src/sys/dev/usb/if_rue.c:241: undefined > reference to `miibus_writereg_desc' > if_rue.o(.data+0x60):/usr/src/sys/dev/usb/if_rue.c:235: undefined > reference to `miibus_statchg_desc' > if_rue.o(.data+0xd4): In function `rue_write_mem': > /usr/src/sys/dev/usb/if_rue.c:261: undefined reference to > `miibus_driver' > if_rue.o(.data+0xd8):/usr/src/sys/dev/usb/if_rue.c:261: undefined > reference to `miibus_devclass' > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/RELENG_6_i686. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 15:30:01 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0D2A16A423 for ; Tue, 1 Nov 2005 15:30:00 +0000 (GMT) (envelope-from robin.blanchard@gactr.uga.edu) Received: from mail.gactr.uga.edu (mail.gactr.uga.edu [128.192.37.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1946843D46 for ; Tue, 1 Nov 2005 15:29:59 +0000 (GMT) (envelope-from robin.blanchard@gactr.uga.edu) Received: from localhost (localhost [127.0.0.1]) by mail.gactr.uga.edu (Postfix) with ESMTP id 41BA35C102 for ; Tue, 1 Nov 2005 10:29:53 -0500 (EST) Received: from mail.gactr.uga.edu ([127.0.0.1]) by localhost (mail.gactr.uga.edu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 83659-02-8 for ; Tue, 1 Nov 2005 10:29:52 -0500 (EST) Received: from EXCHANGE.gc.nat (EXCHANGE1.gc.nat [10.10.11.17]) by mail.gactr.uga.edu (Postfix) with ESMTP id F10EE5C100 for ; Tue, 1 Nov 2005 10:29:52 -0500 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 1 Nov 2005 10:29:58 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: LORs on this morning's RELENG_6 Thread-Index: AcXe+R3tzXQQcxxxTJej8rCzZ3Y+eg== From: "Robin P. Blanchard" To: X-Virus-Scanned: by amavisd-new at gactr.uga.edu Cc: Subject: LORs on this morning's RELENG_6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 15:30:01 -0000 During startup: lock order reversal 1st 0xc16faa7c radix node head (radix node head) @ /usr/src/sys/net/route.c:662 2nd 0xc06ecb20 ifnet (ifnet) @ /usr/src/sys/net/if.c:802 KDB: stack backtrace: witness_checkorder(c06ecb20,9,c0650acd,322,c15f9640) at 0xc04fc2b6 =3D witness_checkorder+0x526 _mtx_lock_flags(c06ecb20,0,c0650acd,322,c17b716c) at 0xc04c5054 =3D _mtx_lock_flags+0x54 ifa_ifwithdstaddr(c17b716c,cca0ba84,246,c06ebd20,cca0bb40) at 0xc0550880 = =3D ifa_ifwithdstaddr+0x30 ifa_ifwithroute(803,c17b715c,c17b716c,c17b716c,c06519a8) at 0xc055d778 = =3D ifa_ifwithroute+0x78 rt_getifa(cca0bb40,8,c06519a8,296,c155da80) at 0xc055d89d =3D = rt_getifa+0x7d rtrequest1(1,cca0bb40,cca0bb2c,c17b7180,c17b7180) at 0xc055ccb5 =3D rtrequest1+0x475 route_output(c1784600,c1898000,80,c1784600,1f80) at 0xc055f26a =3D route_output+0x6fa raw_usend(c1898000,0,c1784600,0,0) at 0xc055bd1d =3D raw_usend+0x5d sosend(c1898000,0,cca0bcb0,c1784600,0) at 0xc0518e8b =3D sosend+0x73b soo_write(c17cb3a8,cca0bcb0,c155da80,0,c15f9640) at 0xc0504590 =3D soo_write+0x50 dofilewrite(c17cb3a8,cca0bcb0,ffffffff,ffffffff,0) at 0xc04fd489 =3D dofilewrite+0x79 kern_writev(c15f9640,3,cca0bcb0,804ec60,0) at 0xc04fd7a1 =3D = kern_writev+0x61 write(c15f9640,cca0bd04,c,c15f9640,3) at 0xc04fd89d =3D write+0x4d syscall(3b,3b,3b,804ef40,80) at 0xc061382c =3D syscall+0x14c Xint0x80_syscall() at 0xc05fe73f =3D Xint0x80_syscall+0x1f --- syscall (4, FreeBSD ELF32, write), eip =3D 0x280c18cf, esp =3D = 0xbfbfedfc, ebp =3D 0xbfbfee18 --- lock order reversal 1st 0xc189adec inp (udpinp) @ /usr/src/sys/netinet/udp_usrreq.c:976 2nd 0xc06ecb20 ifnet (ifnet) @ /usr/src/sys/net/if.c:772 KDB: stack backtrace: witness_checkorder(c06ecb20,9,c0650acd,304,c04e4a97) at 0xc04fc2b6 =3D witness_checkorder+0x526 _mtx_lock_flags(c06ecb20,0,c0650acd,304,c16d73e0) at 0xc04c5054 =3D _mtx_lock_flags+0x54 ifa_ifwithaddr(c16d73e0,8,c16d73e4,11d,c0653f4c) at 0xc0550790 =3D ifa_ifwithaddr+0x30 in_pcbbind_setup(c189ad5c,c16d73e0,c189ad94,c189ad76,c155da80) at = 0xc05667b2 =3D in_pcbbind_setup+0x5f2 in_pcbbind(c189ad5c,c16d73e0,c155da80,3d0,0) at 0xc0566f47 =3D = in_pcbbind+0xd7 udp_bind(c1899590,c16d73e0,c15f9af0,c16d73e0,c17cbab0) at 0xc057f16c =3D udp_bind+0x7c kern_bind(c15f9af0,5,c16d73e0,c16d73e0) at 0xc051f35e =3D kern_bind+0x4e bind(c15f9af0,cca14d04,c,418,3) at 0xc0521a38 =3D bind+0x48 syscall(3b,3b,3b,8092fec,5) at 0xc061382c =3D syscall+0x14c Xint0x80_syscall() at 0xc05fe73f =3D Xint0x80_syscall+0x1f --- syscall (104, FreeBSD ELF32, bind), eip =3D 0x282300af, esp =3D = 0xbfbfeb2c, ebp =3D 0xbfbfec18 --- lock order reversal 1st 0xc0698e60 polling (polling) @ /usr/src/sys/kern/kern_poll.c:333 2nd 0xc06ee38c tcp (tcp) @ /usr/src/sys/netinet/tcp_input.c:615 KDB: stack backtrace: witness_checkorder(c06ee38c,9,c0653166,267,cc9f6aa8) at 0xc04fc2b6 =3D witness_checkorder+0x526 _mtx_lock_flags(c06ee38c,0,c0653166,267,cc9f6ad8) at 0xc04c5054 =3D _mtx_lock_flags+0x54 tcp_input(c168c800,14,c1597af0,15e6f2c,c1626c00) at 0xc0571f84 =3D tcp_input+0x1d4 ip_input(c168c800,c168c800,3,0,0) at 0xc056bc02 =3D ip_input+0x122 ether_demux(c1626c00,c168c800,3,0,3) at 0xc055538a =3D ether_demux+0x2ca ether_input(c1626c00,c168c800,c078730d,6a7,c1630018) at 0xc055568b =3D ether_input+0x22b fxp_intr_body(e0,5,c078730d,5b4,c1597af0) at 0xc0785905 =3D = fxp_intr_body+0x1f5 fxp_poll(c1626c00,0,5,14d,ff) at 0xc0785b8c =3D fxp_poll+0x6c ether_poll(5,0,c0646088,253,1d4c) at 0xc04c6d8b =3D ether_poll+0x7b poll_idle(0,cc9f6d38,c0643d54,30d,33e8988b) at 0xc04c76ec =3D = poll_idle+0xdc fork_exit(c04c7610,0,cc9f6d38) at 0xc04b6124 =3D fork_exit+0xa4 fork_trampoline() at 0xc05fe74c =3D fork_trampoline+0x8 --- trap 0x1, eip =3D 0, esp =3D 0xcc9f6d6c, ebp =3D 0 --- --------------------------------------- Robin P. Blanchard Systems Integration Specialist Georgia Center for Continuing Education fon: 706.542.2404 < > fax: 706.542.6546 --------------------------------------- From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 15:51:29 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3EC416A422 for ; Tue, 1 Nov 2005 15:51:29 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from mv.twc.weather.com (mv.twc.weather.com [65.212.71.225]) by mx1.FreeBSD.org (Postfix) with ESMTP id 162A543D75 for ; Tue, 1 Nov 2005 15:51:24 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from [10.50.41.234] (Not Verified[10.50.41.234]) by mv.twc.weather.com with NetIQ MailMarshal (v6, 0, 3, 8) id ; Tue, 01 Nov 2005 11:08:19 -0500 From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 1 Nov 2005 10:30:05 -0500 User-Agent: KMail/1.8.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511011030.06028.jhb@freebsd.org> Cc: Victor Snezhko Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 15:51:30 -0000 On Monday 31 October 2005 11:53 pm, Victor Snezhko wrote: > Sorry for breaking the thread, I don't have message-id for message I'm > replying to (neither a mailman interface, mor mailing list browser > don't provide ids for recent messages). > > John Baldwin wrote on Mon Oct 31 08:43:20 PST 2005: > > > A bit further. > > > > > > On Sun, 30 Oct 2005, Vladimir Kushnir wrote: > > > > OK, here it is. It's happened between 2005.10.21.19.42.50 and > > > > 2005.10.22.05.07.00. > > > > Since then, panic is absolutely reproducible. > > > > > > Actually, when I took INET6 from kernel (once again, it's GENERIC) > > > these panics stop. > > > > Hmmm. Are those timestamps UTC? If so, there's nothing worthwhile that > > changed in there: > > I experience the same problem, just wanted to report - when I > cvsupped to the kernel as of 2005.10.21.19.42.50, problem remained. > > nooption INET6 actually helps. What about 2005.10.21.16.00.00? Does that fail or break? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 16:01:34 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF10916A41F; Tue, 1 Nov 2005 16:01:34 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6ABE843D70; Tue, 1 Nov 2005 16:01:29 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jA1FxcnR020622; Tue, 1 Nov 2005 08:59:38 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 01 Nov 2005 08:59:48 -0700 (MST) Message-Id: <20051101.085948.112718728.imp@bsdimp.com> To: rwatson@FreeBSD.org From: "M. Warner Losh" In-Reply-To: <20051101080018.R18382@fledge.watson.org> References: <81213.1130754398@critter.freebsd.dk> <20051031.215329.115777034.imp@bsdimp.com> <20051101080018.R18382@fledge.watson.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 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Tue, 01 Nov 2005 08:59:39 -0700 (MST) Cc: phk@phk.freebsd.dk, freebsd-current@FreeBSD.org Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 16:01:34 -0000 In message: <20051101080018.R18382@fledge.watson.org> Robert Watson writes: : On Mon, 31 Oct 2005, M. Warner Losh wrote: : : > In message: <81213.1130754398@critter.freebsd.dk> : > "Poul-Henning Kamp" writes: : > : I am going to insist that clock_gettime(CLOCK_REALTIME, CLOCK_UPTIME) : > : remain precise. : > : > 1ms is way too imprecise for the stuff we do at work. We need 3-4 more : > orders of magnitude at a minimum from the time keeping system. Ideally, : > through well documented interfaces. : : While I agree that for many consumers, sub-1ms accuracy is too low, I : suggest that as a vendor of atomic clocks, your company is in fact not the : average consumer of timing information. :-). For the atomic clocks, we use much better hardware to get timing. The requirements for better than 1ms time keeping comes from the process control aspects of our code, not measuring atomic clocks. : One nice thing about the Linux TSC model, despite its limitations, is that : it provides a middle ground between incrementing the clock in ticks and : providing a more continuous measure of time, by allowing interpolation : between ticks. That's a non-sequitor to what I'm talking about.. :-) Warner From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 16:28:48 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B69C16A420 for ; Tue, 1 Nov 2005 16:28:48 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9516D43D48 for ; Tue, 1 Nov 2005 16:28:47 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by xproxy.gmail.com with SMTP id s13so985462wxc for ; Tue, 01 Nov 2005 08:28:46 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=R7SjRH2i3taq4AuYcPM+LJjBNflf/c9JqVV2d2fUpvXOltYpwB/fMba3dzy9g2G88hdVMYgmcE/n7KlD7tc5VJYMFS/nM9yvBHrHvj5HVn+o7UrVDeRQBrs/hp957LNJhliy1nRL4lGUYQwVMVDLrnrFV8H8kctQtLwkdmJZt98= Received: by 10.70.72.15 with SMTP id u15mr2609480wxa; Tue, 01 Nov 2005 08:28:46 -0800 (PST) Received: by 10.70.53.4 with HTTP; Tue, 1 Nov 2005 08:28:46 -0800 (PST) Message-ID: <790a9fff0511010828u43c87d67vb1967a0191498469@mail.gmail.com> Date: Tue, 1 Nov 2005 10:28:46 -0600 From: Scot Hetzel To: Randy Bush In-Reply-To: <17254.56287.352910.314361@roam.psg.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <17254.34119.81378.589992@roam.psg.com> <17254.56287.352910.314361@roam.psg.com> Cc: FreeBSD Current Subject: Re: make kernel "kldxref: file isn't dynamically-linked" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 16:28:48 -0000 > fwiw, there had been a change in GENERIC since my build last > week, so my custom kernel changed as follows > > 19c19 > < # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.432 2005/08/06 23:05:48 david= xu Exp > $ > --- > > # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.433 2005/10/27 17:34:35 jhb E= xp $ > 83,84c83 > < # Bus support. Do not remove isa, even if you have no isa slots > < device isa > --- > > # Bus support. > 170,172d168 > < # Floating point support - do not disable. > < device npx > < > 263,264d258 > < device mem # Memory and kernel memory device= s > < device io # I/O device > These entries were moved to the file DEFAULT, which is now automaticaly included in any kernel that is built. This change to how kernels are built was to prevent novices from shooting them selfs in the foot when building a custom kernel. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 16:55:47 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF5F916A420 for ; Tue, 1 Nov 2005 16:55:47 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A2CC43D5F for ; Tue, 1 Nov 2005 16:55:45 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.3/8.13.3) with ESMTP id jA1GtfoC058019; Tue, 1 Nov 2005 19:55:41 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.3/8.13.3/Submit) id jA1GtZDO058018; Tue, 1 Nov 2005 19:55:35 +0300 (MSK) (envelope-from yar) Date: Tue, 1 Nov 2005 19:55:34 +0300 From: Yar Tikhiy To: Scott Long Message-ID: <20051101165534.GB56709@comp.chem.msu.su> References: <436116D3.908@samsco.org> <621b657f0510280654j56d4a823n5237f89ccc96b1e9@mail.gmail.com> <436246C1.3030108@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <436246C1.3030108@samsco.org> User-Agent: Mutt/1.5.9i Cc: openglx@starbyte.net, current@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 16:55:47 -0000 On Fri, Oct 28, 2005 at 09:41:53AM -0600, Scott Long wrote: > Felipe openglx wrote: > > > >I had a few issues with SiS 630 video driver, already related in > >thread > >http://docs.freebsd.org/cgi/getmsg.cgi?fetch=815881+0+/usr/local/www/db/text/2005/freebsd-current/20051016.freebsd-current > > > >Are those corrected already? I did compile the latest kernel (after a > >cvsup on src-sys*) and X.org still reboots my machine if I enable the > >SiS driver. > > You'll need to work with the X11 developers. X is only something that > FreeBSD includes as a 3rd party package, it's not something that we > work on as part of the OS. When a 3rd party package crashes our OS, we should care about the issue, too. However, this case seems to require more investigation by developers who have similar hardware. -- Yar From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 17:01:02 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F171816A41F for ; Tue, 1 Nov 2005 17:01:02 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1317D43D49 for ; Tue, 1 Nov 2005 17:01:01 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.201] ([192.168.254.201]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jA1H0fxM003404; Tue, 1 Nov 2005 10:00:42 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43679F3C.4040702@samsco.org> Date: Tue, 01 Nov 2005 10:00:44 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.5) Gecko/20050321 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Yar Tikhiy References: <436116D3.908@samsco.org> <621b657f0510280654j56d4a823n5237f89ccc96b1e9@mail.gmail.com> <436246C1.3030108@samsco.org> <20051101165534.GB56709@comp.chem.msu.su> In-Reply-To: <20051101165534.GB56709@comp.chem.msu.su> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: openglx@starbyte.net, current@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 17:01:03 -0000 Yar Tikhiy wrote: > On Fri, Oct 28, 2005 at 09:41:53AM -0600, Scott Long wrote: > >>Felipe openglx wrote: >> >>>I had a few issues with SiS 630 video driver, already related in >>>thread >>>http://docs.freebsd.org/cgi/getmsg.cgi?fetch=815881+0+/usr/local/www/db/text/2005/freebsd-current/20051016.freebsd-current >>> >>>Are those corrected already? I did compile the latest kernel (after a >>>cvsup on src-sys*) and X.org still reboots my machine if I enable the >>>SiS driver. >> >>You'll need to work with the X11 developers. X is only something that >>FreeBSD includes as a 3rd party package, it's not something that we >>work on as part of the OS. > > > When a 3rd party package crashes our OS, we should care about the > issue, too. However, this case seems to require more investigation > by developers who have similar hardware. > The fact that X has access to /dev/io means that it can do whatever it wants to corrupt the machine, and there isn't much the OS can do about it. Scott From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 17:09:15 2005 Return-Path: X-Original-To: FreeBSD-current@freebsd.org Delivered-To: FreeBSD-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 836E616A41F; Tue, 1 Nov 2005 17:09:15 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E795243D49; Tue, 1 Nov 2005 17:09:10 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.201] ([192.168.254.201]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jA1H98as004082; Tue, 1 Nov 2005 10:09:08 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4367A137.6020005@samsco.org> Date: Tue, 01 Nov 2005 10:09:11 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.5) Gecko/20050321 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Antony Mawer References: <20051101070259.GC18710@wantadilla.lemis.com> <4367150C.4030508@mawer.org> In-Reply-To: <4367150C.4030508@mawer.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: Greg 'groggy' Lehey , FreeBSD-current@freebsd.org Subject: Re: Really poor performance on /dev/ttyv* only X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 17:09:15 -0000 Antony Mawer wrote: > On 1/11/2005 6:02 PM, Greg 'groggy' Lehey wrote: > >> I've just installed -CURRENT on a Dell Inspiron 6000, and I discover >> that the keyboard response on virtual terminals (/dev/ttyv*) is very >> slow. If I keyboard repeat, the echo to the terminal is jerky, about >> 3 or 4 characters at a time with a marked delay in between. Under X >> or over the network there's no problem. Has anybody else seen this? >> The kernel isn't 100% GENERIC (I've disabled WITNESS and >> WITNESS_SKIPSPIN, for example), but I can't see anything that would >> explain this behaviour. > > > I've seen this on two FreeBSD 4.7 systems connected via a KVM (sharing > with two Windows 2003 servers)... typing at the console of them was > almost like typing via ssh on a satellite connection. Connecting via ssh > was fine, it was only locally that it was a problem. Resetting the > keyboard repeat rate on BSD had no discernible impact. > > I put it down to some sort of interaction between the KVM, the Windows > servers and FreeBSD and put up with it... > > Cheers > Antony > I have a USB KVM that violates the USB protocol and results in a storm on the USB controller once in a while. This can result in really sluggish console performance. I can imagine scenarios where PS/2 KVM could do similarily silly things with the same results. Scott From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 17:25:13 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C23F16A41F for ; Tue, 1 Nov 2005 17:25:13 +0000 (GMT) (envelope-from felipegrazziotin@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 318CD43D72 for ; Tue, 1 Nov 2005 17:25:05 +0000 (GMT) (envelope-from felipegrazziotin@gmail.com) Received: by zproxy.gmail.com with SMTP id 40so964091nzk for ; Tue, 01 Nov 2005 09:25:05 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=rKd04QRz8rjNW9KAi48/jSH/DgLFqOAnd99XJ4FqxdkzM1fc12Y89e32yXJX0TgKBPrtLkU50oRgVGMxTFKEPDhqF3blsBUjp9MptvyRN2rL80Kpcvey6pbjt2dr8mzRoWgdBnfplye1fV5Mv/EH4UiU2GkSTy25ufHL7N44gH4= Received: by 10.36.145.16 with SMTP id s16mr833868nzd; Tue, 01 Nov 2005 09:25:05 -0800 (PST) Received: by 10.36.160.18 with HTTP; Tue, 1 Nov 2005 09:25:05 -0800 (PST) Message-ID: <621b657f0511010925t578a5df7nd82040b71e104478@mail.gmail.com> Date: Tue, 1 Nov 2005 15:25:05 -0200 From: Felipe openglx Sender: felipegrazziotin@gmail.com To: Scott Long In-Reply-To: <43679F3C.4040702@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <436116D3.908@samsco.org> <621b657f0510280654j56d4a823n5237f89ccc96b1e9@mail.gmail.com> <436246C1.3030108@samsco.org> <20051101165534.GB56709@comp.chem.msu.su> <43679F3C.4040702@samsco.org> Cc: Yar Tikhiy , current@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 17:25:13 -0000 In fact I agree with Scott. There isn't much the OS can do. As for that bug, I'm already in contact with the X.org developers and trying to do a deeper debugging on what's going on. The driver developer himself said he cannot test that on FreeBSD, thus not assuring it full functionality. So it looks much more to be a X.org problem than FreeBSD one. On 11/1/05, Scott Long wrote: > Yar Tikhiy wrote: > > When a 3rd party package crashes our OS, we should care about the > > issue, too. However, this case seems to require more investigation > > by developers who have similar hardware. > > > > The fact that X has access to /dev/io means that it can do whatever it > wants to corrupt the machine, and there isn't much the OS can do about > it. > > Scott > -- openglx@StarByte.net From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 17:31:57 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AAFE316A41F for ; Tue, 1 Nov 2005 17:31:57 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from freebee.digiware.nl (dsl439.iae.nl [212.61.63.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 152A543D45 for ; Tue, 1 Nov 2005 17:31:53 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.71] (dual.digiware.nl [212.61.27.71]) by freebee.digiware.nl (Postfix) with ESMTP id 9BBA82AAA8 for ; Tue, 1 Nov 2005 18:31:51 +0100 (CET) Message-ID: <4367A781.2090103@withagen.nl> Date: Tue, 01 Nov 2005 18:36:01 +0100 From: Willem Jan Withagen User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "freebsd-current@freebsd.org" Content-Type: multipart/mixed; boundary="------------020101050603060603010901" Subject: 6.0-RC1 problems with ahc and Quantum Atlas disk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 17:31:57 -0000 This is a multi-part message in MIME format. --------------020101050603060603010901 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi, 't might be a rather old disk, but uptill now I only got complaints that ik could only take 64 tagged commands (under 5.4) and nothing serious happened. more or less like the first spurt of 'Request Requeued' stuff Trying 6.0-RC1 makes in bark a bit more. And it dumps het ahc0 card After all this it keeps on functioning. First I thought is was an enhancement with verbose booting, but disableing all that still makes it bark. Errors from dmesg: (dmesg.boot attached) (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. ahc0: Selection Timeout on A:1. 0 SCBs aborted ahc0: Selection Timeout on A:3. 0 SCBs aborted ahc0: Selection Timeout on A:5. 0 SCBs aborted ahc0: Selection Timeout on A:8. 0 SCBs aborted ahc0: Selection Timeout on A:10. 0 SCBs aborted ahc0: Selection Timeout on A:12. 0 SCBs aborted ahc0: Selection Timeout on A:14. 0 SCBs aborted ahc0: Selection Timeout on A:2. 0 SCBs aborted ahc0: Selection Timeout on A:4. 0 SCBs aborted ahc0: Selection Timeout on A:6. 0 SCBs aborted ahc0: Selection Timeout on A:9. 0 SCBs aborted ahc0: Selection Timeout on A:11. 0 SCBs aborted ahc0: Selection Timeout on A:13. 0 SCBs aborted ahc0: Selection Timeout on A:15. 0 SCBs aborted (probe0:ahc0:0:0:0): Retrying Command (ahc0:A:0:0): Sending WDTR 1 (ahc0:A:0:0): Received WDTR 1 filtered to 1 ahc0: target 0 using 16bit transfers (ahc0:A:0:0): Sending SDTR period 2b, offset 8 (ahc0:A:0:0): Received SDTR period 2b, offset 8 Filtered to period 2b, offset 8 ahc0: target 0 synchronous at 5.7MHz, offset = 0x8 pass0 at ahc0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-3 device pass0: Serial Number 369007730326 pass0: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: Serial Number 369007730326 da0: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) GEOM: new disk da0 Trying to mount root from ufs:/dev/da0s1a start_init: trying /sbin/init (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Queue Full (da0:ahc0:0:0:0): tagged openings now 64 (da0:ahc0:0:0:0): Retrying Command ahc0: Recovery Initiated >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< ahc0: Dumping Card State while idle, at SEQADDR 0x7 Card was paused ACCUM = 0x5, SINDEX = 0x64, DINDEX = 0x65, ARG_2 = 0x6 HCNT = 0x0 SCBPTR = 0x9 SCSISIGI[0x0] ERROR[0x0] SCSIBUSL[0x0] LASTPHASE[0x1]:(P_BUSFREE) SCSISEQ[0x12]:(ENAUTOATNP|ENRSELI) SBLKCTL[0x2]:(SELWIDE) SCSIRATE[0x0] SEQCTL[0x10]:(FASTMODE) SEQ_FLAGS[0xc0]:(NO_CDB_SENT|NOT_IDENTIFIED) SSTAT0[0x5]:(DMADONE|SDONE) SSTAT1[0xb]:(REQINIT|PHASECHG|BUSFREE) SSTAT2[0x0] SSTAT3[0x0] SIMODE0[0x0] SIMODE1[0xa4]:(ENSCSIPERR|ENSCSIRST|ENSELTIMO) SXFRCTL0[0x80]:(DFON) DFCNTRL[0x0] DFSTATUS[0x2d]:(FIFOEMP|DFTHRESH|HDONE|FIFOQWDEMP) STACK: 0x0 0x151 0x192 0x3 SCB count = 90 Kernel NEXTQSCB = 16 Card NEXTQSCB = 16 QINFIFO entries: Waiting Queue entries: Disconnected Queue entries: 9:26 12:7 QOUTFIFO entries: Sequencer Free SCB List: 10 7 14 4 5 1 15 2 0 6 13 8 11 3 Sequencer SCB Info: 0 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x7] SCB_LUN[0x0] SCB_TAG[0xff] 1 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x7] SCB_LUN[0x0] SCB_TAG[0xff] 2 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x7] SCB_LUN[0x0] SCB_TAG[0xff] 3 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x7] SCB_LUN[0x0] SCB_TAG[0xff] 4 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x7] SCB_LUN[0x0] SCB_TAG[0xff] 5 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x7] SCB_LUN[0x0] SCB_TAG[0xff] 6 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x7] SCB_LUN[0x0] SCB_TAG[0xff] 7 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x7] SCB_LUN[0x0] SCB_TAG[0xff] 8 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x7] SCB_LUN[0x0] SCB_TAG[0xff] 9 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x7] SCB_LUN[0x0] SCB_TAG[0x1a] 10 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x7] SCB_LUN[0x0] SCB_TAG[0xff] 11 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x7] SCB_LUN[0x0] SCB_TAG[0xff] 12 SCB_CONTROL[0x64]:(DISCONNECTED|TAG_ENB|DISCENB) SCB_SCSIID[0x7] SCB_LUN[0x0] SCB_TAG[0x7] 13 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x7] SCB_LUN[0x0] SCB_TAG[0xff] 14 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x7] SCB_LUN[0x0] SCB_TAG[0xff] 15 SCB_CONTROL[0xe0]:(TAG_ENB|DISCENB|TARGET_SCB) SCB_SCSIID[0x7] SCB_LUN[0x0] SCB_TAG[0xff] Pending list: 26 SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x7] SCB_LUN[0x0] 7 SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x7] SCB_LUN[0x0] Kernel Free SCB list: 29 33 20 47 46 62 34 28 0 4 17 44 14 13 12 39 23 22 11 3 65 25 2 35 24 32 38 8 66 64 51 52 53 67 68 69 50 54 63 56 57 55 19 21 31 37 45 42 9 6 36 58 59 43 40 41 5 49 30 10 27 18 61 81 82 83 84 85 86 87 88 89 70 71 72 73 74 75 76 77 78 79 60 15 48 1 80 <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> (pass0:ahc0:0:0:0): SCB 0x1a - timed out sg[0] - Addr 0x1d69990 : Length 18 (pass0:ahc0:0:0:0): Queuing a BDR SCB ahc0: Timedout SCBs already complete. Interrupts may not be functioning. (pass0:ahc0:0:0:0): Bus Device Reset Message Sent (pass0:ahc0:0:0:0): no longer in timeout, status = 24b ahc0: target 0 using 8bit transfers ahc0: target 0 using asynchronous transfers ahc0: Bus Device Reset on A:0. 1 SCBs aborted (ahc0:A:0:0): Sending WDTR 1 (ahc0:A:0:0): Received WDTR 1 filtered to 1 ahc0: target 0 using 16bit transfers (ahc0:A:0:0): Sending SDTR period 2b, offset 8 (ahc0:A:0:0): Received SDTR period 2b, offset 8 Filtered to period 2b, offset 8 ahc0: target 0 synchronous at 5.7MHz, offset = 0x8 (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (da0:ahc0:0:0:0): Request Requeued (da0:ahc0:0:0:0): Retrying Command (ahc0:A:0:0): Sending WDTR 1 (ahc0:A:0:0): Received WDTR 1 filtered to 1 ahc0: target 0 using 16bit transfers (ahc0:A:0:0): Sending SDTR period 2b, offset 8 (ahc0:A:0:0): Received SDTR period 2b, offset 8 Filtered to period 2b, offset 8 ahc0: target 0 synchronous at 5.7MHz, offset = 0x8 --------------020101050603060603010901 Content-Type: text/plain; name="dmesg.boot" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.boot" 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 6.0-RC1 #0: Tue Nov 1 14:51:34 CET 2005 root@freebee.digiware.nl:/usr/obj/usr/src6/src/sys/FREEBEE Preloaded elf kernel "/boot/kernel/kernel" at 0xc079c000. Calibrating clock(s) ... i8254 clock: 1193276 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 400911688 Hz CPU: Pentium III/Pentium III Xeon/Celeron (400.91-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x387f9ff real memory = 268369920 (255 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009ffff, 651264 bytes (159 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000000825000 - 0x000000000fb37fff, 254881792 bytes (62227 pages) avail memory = 257355776 (245 MB) bios32: Found BIOS32 Service Directory header at 0xc00fafc0 bios32: Entry = 0xfb440 (c00fb440) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0xb470 pnpbios: Found PnP BIOS data at 0xc00fc020 pnpbios: Entry = f0000:c048 Rev = 1.0 Other BIOS signatures found: random: nfslock: pseudo-device mem: Pentium Pro MTRR support enabled io: null: ACPI disabled by blacklist. Contact your BIOS vendor. npx0: [FAST] npx0: on motherboard npx0: INT 16 interface cpu0 on motherboard pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) pcibios: BIOS version 2.10 Found $PIR table, 7 entries at 0xc00fdea0 PCI-Only Interrupts: 10 11 Location Bus Device Pin Link IRQs slot 1 0 12 A 0x60 3 4 5 6 7 9 10 11 12 14 15 slot 1 0 12 B 0x61 3 4 5 6 7 9 10 11 12 14 15 slot 1 0 12 C 0x62 3 4 5 6 7 9 10 11 12 14 15 slot 1 0 12 D 0x63 3 4 5 6 7 9 10 11 12 14 15 slot 2 0 11 A 0x61 3 4 5 6 7 9 10 11 12 14 15 slot 2 0 11 B 0x62 3 4 5 6 7 9 10 11 12 14 15 slot 2 0 11 C 0x63 3 4 5 6 7 9 10 11 12 14 15 slot 2 0 11 D 0x60 3 4 5 6 7 9 10 11 12 14 15 slot 3 0 10 A 0x62 3 4 5 6 7 9 10 11 12 14 15 slot 3 0 10 B 0x63 3 4 5 6 7 9 10 11 12 14 15 slot 3 0 10 C 0x60 3 4 5 6 7 9 10 11 12 14 15 slot 3 0 10 D 0x61 3 4 5 6 7 9 10 11 12 14 15 slot 4 0 9 A 0x63 3 4 5 6 7 9 10 11 12 14 15 slot 4 0 9 B 0x60 3 4 5 6 7 9 10 11 12 14 15 slot 4 0 9 C 0x61 3 4 5 6 7 9 10 11 12 14 15 slot 4 0 9 D 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 0 17 A 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded 0 17 B 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 0 17 C 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 0 17 D 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 0 7 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 0 7 B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 0 7 C 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 0 7 D 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded 0 1 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 0 1 B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 0 1 C 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 0 1 D 0x63 3 4 5 6 7 9 10 11 12 14 15 pcib0: pcibus 0 on motherboard pir0: on motherboard $PIR: Links after initial probe: Link IRQ Rtd Ref IRQs 0x60 255 N 7 3 4 5 6 7 9 10 11 12 14 15 0x61 255 N 7 3 4 5 6 7 9 10 11 12 14 15 0x62 255 N 7 3 4 5 6 7 9 10 11 12 14 15 0x63 255 N 7 3 4 5 6 7 9 10 11 12 14 15 $PIR: Found matching pin for 0.11.INTA at func 0: 11 $PIR: Found matching pin for 0.17.INTA at func 0: 10 $PIR: Found matching pin for 0.7.INTD at func 2: 255 $PIR: Links after initial IRQ discovery: Link IRQ Rtd Ref IRQs 0x60 255 N 7 3 4 5 6 7 9 10 11 12 14 15 0x61 11 Y 7 3 4 5 6 7 9 10 11 12 14 15 0x62 255 N 7 3 4 5 6 7 9 10 11 12 14 15 0x63 10 Y 7 3 4 5 6 7 9 10 11 12 14 15 $PIR: IRQs used by BIOS: 10 11 $PIR: Interrupt Weights: [ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ] [ 0 0 0 0 0 0 0 0 0 0 7 7 0 0 0 0 ] pci0: on pcib0 pci0: physical bus=0 found-> vendor=0x8086, dev=0x7190, revid=0x03 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x2210, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 3, range 32, base e0000000, size 26, enabled found-> vendor=0x8086, dev=0x7191, revid=0x03 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0220, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x88 (34000 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x7110, revid=0x02 bus=0, slot=7, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x7111, revid=0x01 bus=0, slot=7, func=1 class=01-01-80, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base 0000f000, size 4, enabled found-> vendor=0x8086, dev=0x7112, revid=0x01 bus=0, slot=7, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=255 map[20]: type 4, range 32, base 00006400, size 5, enabled found-> vendor=0x8086, dev=0x7113, revid=0x02 bus=0, slot=7, func=3 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0003, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[90]: type 4, range 32, base 00005000, size 4, enabled found-> vendor=0x8086, dev=0x1229, revid=0x04 bus=0, slot=11, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x08 (2000 ns), maxlat=0x38 (14000 ns) intpin=a, irq=11 powerspec 1 supports D0 D1 D2 D3 current D0 map[10]: type 3, range 32, base ea101000, size 12, enabled map[14]: type 4, range 32, base 00006800, size 5, enabled map[18]: type 1, range 32, base ea000000, size 20, enabled $PIR: 0:11 INTA routed to irq 11 found-> vendor=0x9004, dev=0x8078, revid=0x01 bus=0, slot=17, func=0 class=01-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x08 (2000 ns), maxlat=0x08 (2000 ns) intpin=a, irq=10 powerspec 1 supports D0 D3 current D0 map[10]: type 4, range 32, base 00006c00, size 8, enabled map[14]: type 1, range 32, base ea100000, size 12, enabled $PIR: 0:17 INTA routed to irq 10 agp0: mem 0xe0000000-0xe3ffffff at device 0.0 on pci0 agp0: Reserved 0x4000000 bytes for rid 0x10 type 3 at 0xe0000000 agp0: allocating GATT for aperture of size 64M pcib1: at device 1.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xe000-0xefff pcib1: memory decode 0xe4000000-0xe7ffffff pcib1: prefetched decode 0xfff00000-0xfffff pci1: on pcib1 pci1: physical bus=1 found-> vendor=0x1002, dev=0x4742, revid=0x5c bus=1, slot=0, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0087, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 map[10]: type 1, range 32, base e4000000, size 24, enabled pcib1: (null) requested memory range 0xe4000000-0xe4ffffff: good map[14]: type 4, range 32, base 0000e000, size 8, enabled pcib1: (null) requested I/O range 0xe000-0xe0ff: in range map[18]: type 1, range 32, base e6000000, size 12, enabled pcib1: (null) requested memory range 0xe6000000-0xe6000fff: good pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 pci0: at device 7.1 (no driver attached) pci0: at device 7.2 (no driver attached) intpm0: port 0x5000-0x500f irq 9 at device 7.3 on pci0 intpm0: Reserved 0x10 bytes for rid 0x90 type 4 at 0x5000 intpm0: I/O mapped 5000 intpm0: intr IRQ 9 enabled revision 0 intpm0: [GIANT-LOCKED] intsmb0: on intpm0 smbus1: on intsmb0 smb0: on smbus1 intpm0: PM I/O mapped 4000 fxp0: port 0x6800-0x681f mem 0xea101000-0xea101fff,0xea000000-0xea0fffff irq 11 at device 11.0 on pci0 fxp0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xea101000 fxp0: using memory space register mapping fxp0: PCI IDs: 8086 1229 8086 0009 0004 fxp0: Dynamic Standby mode is disabled miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: bpf attached fxp0: Ethernet address: 00:a0:c9:96:d6:c7 fxp0: [MPSAFE] ahc0: port 0x6c00-0x6cff mem 0xea100000-0xea100fff irq 10 at device 17.0 on pci0 ahc0: Defaulting to MEMIO off ahc0: Reserved 0x100 bytes for rid 0x10 type 4 at 0x6c00 ahc0: Reading SEEPROM...done. ahc0: Low byte termination Enabled ahc0: High byte termination Enabled ahc0: Downloading Sequencer Program... 441 instructions downloaded ahc0: Features 0x10005, Bugs 0x11, Flags 0x20481560 ahc0: [GIANT-LOCKED] aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs ahc_isa_probe 6: ioport 0x6c00 alloc failed pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete pnpbios: 14 devices, largest 69 bytes PNP0200: adding dma mask 0x10 PNP0200: adding io range 0-0xf, size=0x10, align=0 PNP0200: adding io range 0x81-0x83, size=0x3, align=0 PNP0200: adding io range 0x87-0x87, size=0x1, align=0 PNP0200: adding io range 0x89-0x8b, size=0x3, align=0 PNP0200: adding io range 0x8f-0x91, size=0x3, align=0 PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0 pnpbios: handle 1 device ID PNP0200 (0002d041) PNP0100: adding irq mask 0x1 PNP0100: adding io range 0x40-0x43, size=0x4, align=0 pnpbios: handle 2 device ID PNP0100 (0001d041) PNP0b00: adding irq mask 0x100 PNP0b00: adding io range 0x70-0x71, size=0x2, align=0 pnpbios: handle 3 device ID PNP0b00 (000bd041) PNP0303: adding irq mask 0x2 PNP0303: adding io range 0x60-0x60, size=0x1, align=0 PNP0303: adding io range 0x64-0x64, size=0x1, align=0 pnpbios: handle 4 device ID PNP0303 (0303d041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0 pnpbios: handle 5 device ID PNP0800 (0008d041) PNP0c04: adding irq mask 0x2000 PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0 pnpbios: handle 6 device ID PNP0c04 (040cd041) PNP0c01: adding fixed memory32 range 0-0x9ffff, size=0xa0000 PNP0c01: adding fixed memory32 range 0xfffe0000-0xffffffff, size=0x20000 PNP0c01: adding fixed memory32 range 0x100000-0xfffffff, size=0xff00000 pnpbios: handle 7 device ID PNP0c01 (010cd041) PNP0c02: adding fixed memory32 range 0xf0000-0xf3fff, size=0x4000 PNP0c02: adding fixed memory32 range 0xf4000-0xf7fff, size=0x4000 PNP0c02: adding fixed memory32 range 0xf8000-0xfffff, size=0x8000 PNP0c02: adding fixed memory32 range 0xcd000-0xcffff, size=0x3000 pnpbios: handle 8 device ID PNP0c02 (020cd041) PNP0a03: adding io range 0x4d0-0x4d1, size=0x2, align=0 PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0 PNP0a03: adding io range 0x480-0x48f, size=0x10, align=0 PNP0a03: adding io range 0x4000-0x403f, size=0x40, align=0 PNP0a03: adding io range 0x5000-0x501f, size=0x20, align=0 pnpbios: handle 9 device ID PNP0a03 (030ad041) PNP0501: adding irq mask 0x10 PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0 pnpbios: handle 12 device ID PNP0501 (0105d041) PNP0700: adding dma mask 0x4 PNP0700: adding io range 0x3f2-0x3f5, size=0x4, align=0 PNP0700: adding irq mask 0x40 pnpbios: handle 13 device ID PNP0700 (0007d041) PNP0400: adding irq mask 0x80 PNP0400: adding io range 0x378-0x37f, size=0x8, align=0 pnpbios: handle 14 device ID PNP0400 (0004d041) PNP0501: adding irq mask 0x8 PNP0501: adding io range 0x2f8-0x2ff, size=0x8, align=0 pnpbios: handle 15 device ID PNP0501 (0105d041) sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xccfff on isa0 adv0: not probed (disabled) aha0: not probed (disabled) aic0: not probed (disabled) ata0 failed to probe at port 0x1f0 irq 14 on isa0 ata1 failed to probe at port 0x170 irq 15 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0067 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 atkbd0: [GIANT-LOCKED] psm0: current command byte:0067 psm0: failed to reset the aux device. bt0: not probed (disabled) cs0: not probed (disabled) ed0: not probed (disabled) fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 fe0: not probed (disabled) ie0: not probed (disabled) lnc0: not probed (disabled) pcic0 failed to probe at port 0x3e0 iomem 0xd0000 on isa0 pcic1: not probed (disabled) ppc0 failed to probe at irq 7 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) sn0: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 vt0: not probed (disabled) isa_probe_children: probing PnP devices unknown: can't assign resources (port) unknown: at port 0x60 on isa0 unknown: failed to probe at port 0x61 on isa0 unknown: can't assign resources (memory) unknown: at iomem 0-0x9ffff on isa0 unknown: can't assign resources (port) unknown: at port 0x4d0-0x4d1,0xcf8-0xcff,0x480-0x48f,0x4000-0x403f,0x5000-0x501f on isa0 unknown: can't assign resources (port) unknown: at port 0x3f8-0x3ff on isa0 unknown: failed to probe at port 0x3f2-0x3f5 irq 6 drq 2 on isa0 unknown: failed to probe at port 0x378-0x37f irq 7 on isa0 unknown: can't assign resources (port) unknown: at port 0x2f8-0x2ff on isa0 Device configuration finished. procfs registered Timecounter "TSC" frequency 400911688 Hz quality 800 Timecounters tick every 1.000 msec Linux ELF exec handler installed lo0: bpf attached Waiting 5 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. ahc0: Selection Timeout on A:1. 0 SCBs aborted ahc0: Selection Timeout on A:3. 0 SCBs aborted ahc0: Selection Timeout on A:5. 0 SCBs aborted ahc0: Selection Timeout on A:8. 0 SCBs aborted ahc0: Selection Timeout on A:10. 0 SCBs aborted ahc0: Selection Timeout on A:12. 0 SCBs aborted ahc0: Selection Timeout on A:14. 0 SCBs aborted ahc0: Selection Timeout on A:2. 0 SCBs aborted ahc0: Selection Timeout on A:4. 0 SCBs aborted ahc0: Selection Timeout on A:6. 0 SCBs aborted ahc0: Selection Timeout on A:9. 0 SCBs aborted ahc0: Selection Timeout on A:11. 0 SCBs aborted ahc0: Selection Timeout on A:13. 0 SCBs aborted ahc0: Selection Timeout on A:15. 0 SCBs aborted (probe0:ahc0:0:0:0): Retrying Command (ahc0:A:0:0): Sending WDTR 1 (ahc0:A:0:0): Received WDTR 1 filtered to 1 ahc0: target 0 using 16bit transfers (ahc0:A:0:0): Sending SDTR period 2b, offset 8 (ahc0:A:0:0): Received SDTR period 2b, offset 8 Filtered to period 2b, offset 8 ahc0: target 0 synchronous at 5.7MHz, offset = 0x8 pass0 at ahc0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-3 device pass0: Serial Number 369007730326 pass0: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: Serial Number 369007730326 da0: 11.626MB/s transfers (5.813MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) GEOM: new disk da0 Trying to mount root from ufs:/dev/da0s1a start_init: trying /sbin/init --------------020101050603060603010901-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 17:32:41 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B0D016A41F for ; Tue, 1 Nov 2005 17:32:41 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9D4943D64 for ; Tue, 1 Nov 2005 17:32:40 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jA1HWUAj006438; Tue, 1 Nov 2005 10:32:30 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4367A6AF.7030805@samsco.org> Date: Tue, 01 Nov 2005 10:32:31 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Felipe openglx References: <436116D3.908@samsco.org> <621b657f0510280654j56d4a823n5237f89ccc96b1e9@mail.gmail.com> <436246C1.3030108@samsco.org> <20051101165534.GB56709@comp.chem.msu.su> <43679F3C.4040702@samsco.org> <621b657f0511010925t578a5df7nd82040b71e104478@mail.gmail.com> In-Reply-To: <621b657f0511010925t578a5df7nd82040b71e104478@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: Yar Tikhiy , current@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 17:32:41 -0000 Felipe openglx wrote: > In fact I agree with Scott. There isn't much the OS can do. > > As for that bug, I'm already in contact with the X.org developers and > trying to do a deeper debugging on what's going on. The driver > developer himself said he cannot test that on FreeBSD, thus not > assuring it full functionality. So it looks much more to be a X.org > problem than FreeBSD one. > > On 11/1/05, Scott Long wrote: > >>Yar Tikhiy wrote: >> >>>When a 3rd party package crashes our OS, we should care about the >>>issue, too. However, this case seems to require more investigation >>>by developers who have similar hardware. >>> >> >>The fact that X has access to /dev/io means that it can do whatever it >>wants to corrupt the machine, and there isn't much the OS can do about >>it. >> >>Scott >> > > > > -- > openglx@StarByte.net One caveat that I forgot is that there are SiS AGP and DRI/DRM modules that operate in the kernel and come with the stock FreeBSD sources. You should isolate these out before looking any further. For AGP, make sure that 'device agp' is not in your kernel or loaded as a module, and for DRM make sure that your X config file omits the DRI/DRM options. If it still fails then it's almost certainly an X bug and not a FreeBSD bug. If it's a DRM problem then you'll still want to contact the X folks since that code is maintained outside of the FreeBSD project. If it's an AGP problem then we'll mark is as something that needs fixing for 6.1. Scott From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 18:21:38 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D4AF16A41F for ; Tue, 1 Nov 2005 18:21:38 +0000 (GMT) (envelope-from therion@ninth-art.de) Received: from mail.ninth-art.de (coruscant.ninth-art.de [81.169.134.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9739443D4C for ; Tue, 1 Nov 2005 18:21:36 +0000 (GMT) (envelope-from therion@ninth-art.de) Received: (qmail 19505 invoked from network); 1 Nov 2005 19:21:35 +0100 Received: from 10.8.0.2 by coruscant (envelope-from , uid 201) with qmail-scanner-1.25st (clamdscan: 0.87/1151. spamassassin: 3.0.4. perlscan: 1.25st. Clear:RC:0(10.8.0.2):SA:0(-2.8/5.0):. Processed in 15.594319 secs); 01 Nov 2005 18:21:35 -0000 X-Spam-Status: No, hits=-2.8 required=5.0 Received: from fortuna.ninth-art.net (HELO ?10.8.0.2?) (therion@ninth-art.de@10.8.0.2) by coruscant.ninth-art.net with AES256-SHA encrypted SMTP; 1 Nov 2005 19:21:19 +0100 Message-ID: <4367B217.3030802@ninth-art.de> Date: Tue, 01 Nov 2005 19:21:11 +0100 From: Georg Bege User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051003) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Willem Jan Withagen References: <4367A781.2090103@withagen.nl> In-Reply-To: <4367A781.2090103@withagen.nl> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: 6.0-RC1 problems with ahc and Quantum Atlas disk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: therion@ninth-art.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 18:21:38 -0000 Hey I've got an Quantum Atlas disk too: da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 127, 16bit), Tagged Queueing Enabled da0: 17510MB (35860910 512 byte sectors: 255H 63S/T 2232C) and with controller: ahc0: port 0xac00-0xacff mem 0xf3000000-0xf3000fff irq 23 at device 9.0 on pci2 ahc0: [GIANT-LOCKED] da0 at ahc0 bus 0 target 0 lun 0 And it works very well (atm Im running 6.0-RC1). I know that doesnt solve your problem just wanted to say that your problem might has more sth todo with your controller instead of your disk. Maybe this will kill some possibilities. Willem Jan Withagen wrote: > Hi, > > 't might be a rather old disk, but uptill now I only got complaints > that ik could only take 64 tagged commands (under 5.4) and nothing > serious happened. > more or less like the first spurt of 'Request Requeued' stuff > Trying 6.0-RC1 makes in bark a bit more. And it dumps het ahc0 card > After all this it keeps on functioning. First I thought is was an > enhancement with verbose booting, but disableing all that still makes > it bark. > > From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 18:46:56 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA30D16A41F; Tue, 1 Nov 2005 18:46:56 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from indor.net.tomline.ru (indor.net.tomline.ru [213.183.100.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF48343D49; Tue, 1 Nov 2005 18:46:55 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from SNEZHKO by indorsoft.ru (MDaemon.PRO.v7.2.2.R) with ESMTP id md50000027121.msg; Wed, 02 Nov 2005 00:46:52 +0600 X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 87696, updated: 31.10.2005] To: John Baldwin References: <200511011030.06028.jhb@freebsd.org> From: Victor Snezhko Date: Wed, 02 Nov 2005 00:46:48 +0600 In-Reply-To: <200511011030.06028.jhb@freebsd.org> (John Baldwin's message of "Tue, 1 Nov 2005 10:30:05 -0500") Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Processed: indor.net.tomline.ru, Wed, 02 Nov 2005 00:46:52 +0600 (not processed: spam filter disabled) X-Return-Path: snezhko@indorsoft.ru X-VVS-Spam: false Cc: freebsd-current@freebsd.org Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 18:46:57 -0000 John Baldwin writes: >> > > Actually, when I took INET6 from kernel (once again, it's GENERIC) >> > > these panics stop. >> > >> > Hmmm. Are those timestamps UTC? If so, there's nothing worthwhile that >> > changed in there: >> >> I experience the same problem, just wanted to report - when I >> cvsupped to the kernel as of 2005.10.21.19.42.50, problem remained. >> >> nooption INET6 actually helps. > > What about 2005.10.21.16.00.00? Does that fail or break? Beginning to cvsup and compile it. I have just begun to narrow my search - 2005.10.01.19.42.50 doesn't panic. Can I do something to increase speed of narrowing? At the moment I recompile the kernel after each cvsup, this procedure takes 80-140 minutes depending on what else I do with my machine. -- WBR, Victor V. Snezhko EMail: snezhko@indorsoft.ru From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 20:02:32 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D96616A41F for ; Tue, 1 Nov 2005 20:02:32 +0000 (GMT) (envelope-from Philippe.Pegon@crc.u-strasbg.fr) Received: from mailhost.u-strasbg.fr (mailhost.u-strasbg.fr [130.79.200.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4EF443D46 for ; Tue, 1 Nov 2005 20:02:31 +0000 (GMT) (envelope-from Philippe.Pegon@crc.u-strasbg.fr) Received: from baal.u-strasbg.fr (baal.u-strasbg.fr [IPv6:2001:660:2402::41]) by mailhost.u-strasbg.fr (8.13.3/jtpda-5.5pre1) with ESMTP id jA1K2QZR078610 ; Tue, 1 Nov 2005 21:02:26 +0100 (CET) Received: from [127.0.0.1] (crc.u-strasbg.fr [IPv6:2001:660:2402:1001::1]) by baal.u-strasbg.fr (8.13.4/jtpda-5.5pre1) with ESMTP id jA1K2PB8006597 ; Tue, 1 Nov 2005 21:02:26 +0100 Message-ID: <4367C971.5070400@crc.u-strasbg.fr> Date: Tue, 01 Nov 2005 21:00:49 +0100 From: Philippe PEGON User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051016) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nate Eldredge References: <4366879A.7090603@crc.u-strasbg.fr> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87/1153/Tue Nov 1 17:58:51 2005 on mr8.u-strasbg.fr X-Virus-Scanned: ClamAV 0.87/1153/Tue Nov 1 17:58:51 2005 on baal.u-strasbg.fr X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (mailhost.u-strasbg.fr [IPv6:2001:660:2402::158]); Tue, 01 Nov 2005 21:02:26 +0100 (CET) X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RELAYS autolearn=disabled version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mr8.u-strasbg.fr Cc: freebsd-current@freebsd.org Subject: Re: show stopper for FreeBSD 6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 20:02:32 -0000 Nate Eldredge wrote: > On Mon, 31 Oct 2005, Philippe PEGON wrote: > >> Hi, >> >> I know that it's a bit late for FreeBSD 6 release, but I think this >> issue is a significant problem for FreeBSD : >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/83375 >> >> our productions servers with FreeBSD 5.4 reboots every week with this >> panic and we are not alone. We hoped that FreeBSD 6 would have solved >> this problem after this thread on freebsd-stable : >> >> http://lists.freebsd.org/mailman/htdig/freebsd-stable/2005-June/016154.html >> >> >> I have just tested with FreeBSD 6-RC1 and the problem remains here. >> Moreover, I think it's also a security issue because a single user, with >> a shell account on an FreeBSD SMP box, could trigger a panic with a >> simple shell script like that one (posted by Marc Olzheim in PR 83375), >> it's annoying particularly in a multi-user environment : > > > I am looking at this. I have a good idea what the problem is and will > update tomorrow. I'll be happy to test some patchs if that can help. -- Philippe PEGON From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 20:20:14 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA7FA16A41F for ; Tue, 1 Nov 2005 20:20:14 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13D4D43D46 for ; Tue, 1 Nov 2005 20:20:13 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.54 (FreeBSD)) id 1EX2c9-000Mjj-3s; Tue, 01 Nov 2005 20:20:13 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.53 (FreeBSD)) id 1EX2c6-000PCZ-4S; Tue, 01 Nov 2005 12:20:10 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17255.52729.630674.419999@roam.psg.com> Date: Tue, 1 Nov 2005 10:20:09 -1000 To: Scot Hetzel References: <17254.34119.81378.589992@roam.psg.com> <17254.56287.352910.314361@roam.psg.com> <790a9fff0511010828u43c87d67vb1967a0191498469@mail.gmail.com> Cc: FreeBSD Current Subject: Re: make kernel "kldxref: file isn't dynamically-linked" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 20:20:14 -0000 >> fwiw, there had been a change in GENERIC since my build last >> week, so my custom kernel changed as follows >> >> 19c19 >> < # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.432 2005/08/06 23:05:48 davidxu Exp >> $ >> --- >>> # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.433 2005/10/27 17:34:35 jhb Exp $ >> 83,84c83 >> < # Bus support. Do not remove isa, even if you have no isa slots >> < device isa >> --- >>> # Bus support. >> 170,172d168 >> < # Floating point support - do not disable. >> < device npx >> < >> 263,264d258 >> < device mem # Memory and kernel memory devices >> < device io # I/O device >> > These entries were moved to the file DEFAULT, which is now > automaticaly included in any kernel that is built. This change to how > kernels are built was to prevent novices from shooting them selfs in > the foot when building a custom kernel. no problem with that. i was just 'fessing up to changes i had made which might have influenced the make it's the kldxref: file isn't dynamically-linked that worries me randy From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 21:40:11 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5697F16A41F; Tue, 1 Nov 2005 21:40:11 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from indor.net.tomline.ru (indor.net.tomline.ru [213.183.100.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7F5C43D73; Tue, 1 Nov 2005 21:40:02 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from SNEZHKO by indorsoft.ru (MDaemon.PRO.v7.2.2.R) with ESMTP id md50000027143.msg; Wed, 02 Nov 2005 03:39:56 +0600 X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 87696, updated: 31.10.2005] To: John Baldwin References: <200511011030.06028.jhb@freebsd.org> From: Victor Snezhko Date: Wed, 02 Nov 2005 03:39:53 +0600 In-Reply-To: <200511011030.06028.jhb@freebsd.org> (John Baldwin's message of "Tue, 1 Nov 2005 10:30:05 -0500") Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Processed: indor.net.tomline.ru, Wed, 02 Nov 2005 03:39:56 +0600 (not processed: spam filter disabled) X-Return-Path: snezhko@indorsoft.ru X-VVS-Spam: false Cc: freebsd-current@freebsd.org Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 21:40:11 -0000 John Baldwin writes: >> > > > OK, here it is. It's happened between 2005.10.21.19.42.50 and >> > > > 2005.10.22.05.07.00. >> > > > Since then, panic is absolutely reproducible. >> > > >> > > Actually, when I took INET6 from kernel (once again, it's GENERIC) >> > > these panics stop. >> > >> > Hmmm. Are those timestamps UTC? If so, there's nothing worthwhile that >> > changed in there: >> >> I experience the same problem, just wanted to report - when I >> cvsupped to the kernel as of 2005.10.21.19.42.50, problem remained. >> >> nooption INET6 actually helps. > > What about 2005.10.21.16.00.00? Does that fail or break? No, that doesn't trap. So, we found a narrow timeslice at which things broken. -- WBR, Victor V. Snezhko EMail: snezhko@indorsoft.ru From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 22:01:47 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E17816A41F; Tue, 1 Nov 2005 22:01:47 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0D5643D46; Tue, 1 Nov 2005 22:01:44 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id jA1MAWW9093817; Tue, 1 Nov 2005 17:10:32 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-acpi@FreeBSD.org, freebsd-current@FreeBSD.org Date: Tue, 1 Nov 2005 17:01:27 -0500 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200511011701.31444.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV devel-20050919/1154/Tue Nov 1 16:23:22 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Subject: [HEADSUP] ACPI-CA 20051021 import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 22:01:47 -0000 ACPI-CA 20051021 will be imported any minute now. I will let you know when completed. Thanks, Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 22:10:27 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A66316A423 for ; Tue, 1 Nov 2005 22:10:27 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9BE643D5D for ; Tue, 1 Nov 2005 22:10:25 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jA1MA2E4023769; Tue, 1 Nov 2005 15:10:06 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 01 Nov 2005 15:10:02 -0700 (MST) Message-Id: <20051101.151002.74726277.imp@bsdimp.com> To: randy@psg.com From: Warner Losh In-Reply-To: <17255.52729.630674.419999@roam.psg.com> References: <17254.56287.352910.314361@roam.psg.com> <790a9fff0511010828u43c87d67vb1967a0191498469@mail.gmail.com> <17255.52729.630674.419999@roam.psg.com> 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 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Tue, 01 Nov 2005 15:10:09 -0700 (MST) Cc: swhetzel@gmail.com, freebsd-current@freebsd.org Subject: Re: make kernel "kldxref: file isn't dynamically-linked" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 22:10:27 -0000 From: Randy Bush Subject: Re: make kernel "kldxref: file isn't dynamically-linked" Date: Tue, 1 Nov 2005 10:20:09 -1000 > >> fwiw, there had been a change in GENERIC since my build last > >> week, so my custom kernel changed as follows > >> > >> 19c19 > >> < # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.432 2005/08/06 23:05:48 davidxu Exp > >> $ > >> --- > >>> # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.433 2005/10/27 17:34:35 jhb Exp $ > >> 83,84c83 > >> < # Bus support. Do not remove isa, even if you have no isa slots > >> < device isa > >> --- > >>> # Bus support. > >> 170,172d168 > >> < # Floating point support - do not disable. > >> < device npx > >> < > >> 263,264d258 > >> < device mem # Memory and kernel memory devices > >> < device io # I/O device > >> > > These entries were moved to the file DEFAULT, which is now > > automaticaly included in any kernel that is built. This change to how > > kernels are built was to prevent novices from shooting them selfs in > > the foot when building a custom kernel. > > no problem with that. i was just 'fessing up to changes i had > made which might have influenced the make > > it's the > > kldxref: file isn't dynamically-linked > > that worries me Don't worry. Be happy. This hs nothing to do with DEFAULT. Instead it is a -current only wanring based on work that Ru@ did to install the symbols for the modules and kernel. It really is a harmless warning. Warner From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 22:13:56 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC1A016A41F; Tue, 1 Nov 2005 22:13:56 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64A2043D45; Tue, 1 Nov 2005 22:13:56 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jA1MAkp1023783; Tue, 1 Nov 2005 15:10:46 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 01 Nov 2005 15:10:45 -0700 (MST) Message-Id: <20051101.151045.41655388.imp@bsdimp.com> To: jkim@freebsd.org From: Warner Losh In-Reply-To: <200511011701.31444.jkim@FreeBSD.org> References: <200511011701.31444.jkim@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 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Tue, 01 Nov 2005 15:10:46 -0700 (MST) Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: [HEADSUP] ACPI-CA 20051021 import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 22:13:57 -0000 > ACPI-CA 20051021 will be imported any minute now. I will let you know > when completed. Thanks for the heads up! Wanrer From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 22:50:14 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5951016A423; Tue, 1 Nov 2005 22:50:14 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57AF143D68; Tue, 1 Nov 2005 22:50:10 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id jA1MwmE0095227; Tue, 1 Nov 2005 17:58:48 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-current@FreeBSD.org Date: Tue, 1 Nov 2005 17:49:44 -0500 User-Agent: KMail/1.6.2 References: <200511011701.31444.jkim@FreeBSD.org> In-Reply-To: <200511011701.31444.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200511011749.46273.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV devel-20050919/1154/Tue Nov 1 16:23:22 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-acpi@FreeBSD.org Subject: Re: [HEADSUP] ACPI-CA 20051021 import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 22:50:14 -0000 On Tuesday 01 November 2005 05:01 pm, Jung-uk Kim wrote: > ACPI-CA 20051021 will be imported any minute now. I will let you > know when completed. ACPI-CA 20051021 import is completed. Thanks! Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 23:15:34 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58C1E16A420; Tue, 1 Nov 2005 23:15:34 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7B8C43D46; Tue, 1 Nov 2005 23:15:33 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.33] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id jA1NFWxq007839 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 1 Nov 2005 15:15:32 -0800 Message-ID: <4367F6E8.9030600@root.org> Date: Tue, 01 Nov 2005 15:14:48 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jung-uk Kim References: <200511011701.31444.jkim@FreeBSD.org> <200511011749.46273.jkim@FreeBSD.org> In-Reply-To: <200511011749.46273.jkim@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: [HEADSUP] ACPI-CA 20051021 import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 23:15:34 -0000 Jung-uk Kim wrote: > On Tuesday 01 November 2005 05:01 pm, Jung-uk Kim wrote: > >>ACPI-CA 20051021 will be imported any minute now. I will let you >>know when completed. > > ACPI-CA 20051021 import is completed. > > Thanks! > > Jung-uk Kim Thanks for working on this. (Note: work was reviewed by njl@ and marks@ so this does not mean open season on ACPI). -- Nate From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 23:46:31 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1BA6B16A41F; Tue, 1 Nov 2005 23:46:31 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 951C643D49; Tue, 1 Nov 2005 23:46:30 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id jA1NtIWB096749; Tue, 1 Nov 2005 18:55:18 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-current@FreeBSD.org Date: Tue, 1 Nov 2005 18:46:14 -0500 User-Agent: KMail/1.6.2 References: <200511011701.31444.jkim@FreeBSD.org> <200511011749.46273.jkim@FreeBSD.org> <4367F6E8.9030600@root.org> In-Reply-To: <4367F6E8.9030600@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200511011846.16238.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV devel-20050919/1156/Tue Nov 1 17:40:51 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-acpi@FreeBSD.org, Nate Lawson Subject: Re: [HEADSUP] ACPI-CA 20051021 import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 23:46:31 -0000 On Tuesday 01 November 2005 06:14 pm, Nate Lawson wrote: > (Note: work was reviewed by njl@ and marks@ so this does not mean > open season on ACPI). Sorry, I forgot to mention the great help from you guys. Thanks a bunch! Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Tue Nov 1 23:53:50 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D95616A41F; Tue, 1 Nov 2005 23:53:50 +0000 (GMT) (envelope-from vkushnir@i.kiev.ua) Received: from horse.iptelecom.net.ua (horse.iptelecom.net.ua [212.9.224.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62ACB43D45; Tue, 1 Nov 2005 23:53:49 +0000 (GMT) (envelope-from vkushnir@i.kiev.ua) Received: from h43.241.159.dialup.iptcom.net ([213.159.241.43]:5837 "EHLO kushnir1.kiev.ua" ident: "SOCKFAULT1" whoson: "vkushnir") by horse.iptelecom.net.ua with ESMTP id S1219694AbVKAXxr (ORCPT + 1 other); Wed, 2 Nov 2005 01:53:47 +0200 Received: from kushnir1.kiev.ua (kushnir1.kiev.ua [10.0.0.1]) by kushnir1.kiev.ua (8.13.4/8.13.3) with ESMTP id jA1Nrhid001580; Wed, 2 Nov 2005 01:53:43 +0200 (EET) (envelope-from vkushnir@i.kiev.ua) Date: Wed, 2 Nov 2005 01:53:43 +0200 (EET) From: Vladimir Kushnir X-X-Sender: vkushnir@kushnir1.kiev.ua To: John Baldwin In-Reply-To: <200510311231.33322.jhb@freebsd.org> Message-ID: <20051102014239.O654@kushnir1.kiev.ua> References: <20051027022313.R675@kushnir1.kiev.ua> <20051030052435.J646@kushnir1.kiev.ua> <20051031000217.F636@kushnir1.kiev.ua> <200510311231.33322.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 23:53:50 -0000 On Mon, 31 Oct 2005, John Baldwin wrote: > On Sunday 30 October 2005 05:17 pm, Vladimir Kushnir wrote: >> A bit further. >> >> On Sun, 30 Oct 2005, Vladimir Kushnir wrote: >>> OK, here it is. It's happened between 2005.10.21.19.42.50 and >>> 2005.10.22.05.07.00. >>> Since then, panic is absolutely reproducible. >> >> Actually, when I took INET6 from kernel (once again, it's GENERIC) these >> panics stop. > > Hmmm. Are those timestamps UTC? If so, there's nothing worthwhile that > changed in there: > Sorry I was a bit vague. > > suz 2005-10-21 16:23:01 UTC > > FreeBSD src repository > > Modified files: > sys/netinet icmp6.h > sys/netinet6 icmp6.c in6.c in6.h in6_ifattach.c > in6_ifattach.h in6_var.h ip6_output.c > mld6.c mld6_var.h nd6.c nd6.h nd6_nbr.c > nd6_rtr.c > share/doc/IPv6 IMPLEMENTATION This was when panics begun. And they're still here. Regards, Vladimir From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 00:08:45 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BFD616A41F; Wed, 2 Nov 2005 00:08:45 +0000 (GMT) (envelope-from grog@lemis.com) Received: from ext-gw.lemis.com (ext-gw.lemis.com [150.101.14.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4E4B43D45; Wed, 2 Nov 2005 00:08:44 +0000 (GMT) (envelope-from grog@lemis.com) Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.135]) by ext-gw.lemis.com (Postfix) with ESMTP id 42A981310DF; Wed, 2 Nov 2005 10:38:43 +1030 (CST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 1DFE3855EA; Wed, 2 Nov 2005 10:38:43 +1030 (CST) Date: Wed, 2 Nov 2005 10:38:43 +1030 From: Greg 'groggy' Lehey To: Stefan Cars Message-ID: <20051102000843.GO56043@wantadilla.lemis.com> References: <20051030204120.GB99588@xor.obsecurity.org> <20051030205602.GB201@xor.obsecurity.org> <4365F4D1.6020809@snowfall.se> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xiprIVX1FSGBv8kC" Content-Disposition: inline In-Reply-To: <4365F4D1.6020809@snowfall.se> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Cc: Daniel Eischen , current@freebsd.org, Kris Kennaway Subject: Re: MySQL crashes on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 00:08:45 -0000 --xiprIVX1FSGBv8kC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Monday, 31 October 2005 at 11:41:21 +0100, Stefan Cars wrote: > Kris Kennaway wrote: >> On Sun, Oct 30, 2005 at 03:52:42PM -0500, Daniel Eischen wrote: >>> On Sun, 30 Oct 2005, Kris Kennaway wrote: >>>> On Sun, Oct 30, 2005 at 02:45:57PM +0100, Stefan Cars wrote: >>>>> No. I don't need both. Removed libpthread.so.1 and still the same >>>>> problem. >>>> >>>> You removed the mapping entry, or the file itself? Daniel asked for >>>> the latter. >>> >>> Or perhaps try using libmap.conf to map libpthread.so.1 to >>> libpthread.so.2 without any other mappings: >>> >>> libpthread.so.1 libpthread.so.2 >> >> This is just a partial workaround, of course, and any of your >> binaries that are also linked to two versions of other libraries >> may still experience crashes (or may start to crash later when the >> new libraries change further). You really want to track down and >> fix the root cause now, to save you hours of pain later when the >> problem recurs elsewhere. > > The thing is I don't need the libpthread.so.1 to libpthread.so.2 > mapping, it works anyway (although mysql crashes) but when mapping > libpthread.so* to libthr* it works perfectly. It would be nice to find the bug rather than a workaround. Can you get a stack dump of the server? Greg -- See complete headers for address and phone numbers. --xiprIVX1FSGBv8kC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFDaAOLIubykFB6QiMRAmZuAJ4yBPxBMVPml9au6/EI9eOkWg/bFgCfS98U 1k3SJvAnZ5h+ls5599shszg= =srqr -----END PGP SIGNATURE----- --xiprIVX1FSGBv8kC-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 00:11:00 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6D4B16A41F for ; Wed, 2 Nov 2005 00:11:00 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id A23AB43D45 for ; Wed, 2 Nov 2005 00:11:00 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by mail.ambrisko.com with ESMTP; 01 Nov 2005 16:11:00 -0800 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.12.11/8.12.9) with ESMTP id jA20B0ss039655 for ; Tue, 1 Nov 2005 16:11:00 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.12.11/8.12.11/Submit) id jA20B0S4039654 for current@freebsd.org; Tue, 1 Nov 2005 16:11:00 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200511020011.jA20B0S4039654@ambrisko.com> To: current@freebsd.org Date: Tue, 1 Nov 2005 16:11:00 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: Subject: Rocket Port update patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 00:11:01 -0000 I've brought in the changes to the driver from the Comtrol web site. This greatly improves the RocketPort HW support for those devices. The changes are at: http://www.ambrisko.com/doug/rp_current.patch I'd like to commit it so things just work out of the box. I tried to maintain all the various FreeBSD & Comtrol changes. It works here on my previously unsupported card. Thanks, Doug A. From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 00:24:46 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31D7216A41F for ; Wed, 2 Nov 2005 00:24:46 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9326A43D46 for ; Wed, 2 Nov 2005 00:24:45 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jA20OMJC044784; Tue, 1 Nov 2005 17:24:22 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43680737.6080108@samsco.org> Date: Tue, 01 Nov 2005 17:24:23 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug Ambrisko References: <200511020011.jA20B0S4039654@ambrisko.com> In-Reply-To: <200511020011.jA20B0S4039654@ambrisko.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: current@freebsd.org Subject: Re: Rocket Port update patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 00:24:46 -0000 Doug Ambrisko wrote: > I've brought in the changes to the driver from the Comtrol web site. > This greatly improves the RocketPort HW support for those devices. > The changes are at: > http://www.ambrisko.com/doug/rp_current.patch > > I'd like to commit it so things just work out of the box. I tried to > maintain all the various FreeBSD & Comtrol changes. > > It works here on my previously unsupported card. > > Thanks, > > Doug A. One thing stands out on the brief skim. Why on earth does the code need to keep a global count of the number of adapters, and why does it bail if there are more than 4 adapters? Scott From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 00:40:07 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 706BF16A41F; Wed, 2 Nov 2005 00:40:07 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8E6943D45; Wed, 2 Nov 2005 00:40:06 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id CC4181A3C2A; Tue, 1 Nov 2005 16:40:06 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id F39C551370; Tue, 1 Nov 2005 19:40:03 -0500 (EST) Date: Tue, 1 Nov 2005 19:40:03 -0500 From: Kris Kennaway To: Greg 'groggy' Lehey Message-ID: <20051102004003.GA42673@xor.obsecurity.org> References: <20051030204120.GB99588@xor.obsecurity.org> <20051030205602.GB201@xor.obsecurity.org> <4365F4D1.6020809@snowfall.se> <20051102000843.GO56043@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="envbJBWh7q8WU6mo" Content-Disposition: inline In-Reply-To: <20051102000843.GO56043@wantadilla.lemis.com> User-Agent: Mutt/1.4.2.1i Cc: Daniel Eischen , Kris Kennaway , current@freebsd.org, Stefan Cars Subject: Re: MySQL crashes on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 00:40:07 -0000 --envbJBWh7q8WU6mo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 02, 2005 at 10:38:43AM +1030, Greg 'groggy' Lehey wrote: > On Monday, 31 October 2005 at 11:41:21 +0100, Stefan Cars wrote: > > Kris Kennaway wrote: > >> On Sun, Oct 30, 2005 at 03:52:42PM -0500, Daniel Eischen wrote: > >>> On Sun, 30 Oct 2005, Kris Kennaway wrote: > >>>> On Sun, Oct 30, 2005 at 02:45:57PM +0100, Stefan Cars wrote: > >>>>> No. I don't need both. Removed libpthread.so.1 and still the same > >>>>> problem. > >>>> > >>>> You removed the mapping entry, or the file itself? Daniel asked for > >>>> the latter. > >>> > >>> Or perhaps try using libmap.conf to map libpthread.so.1 to > >>> libpthread.so.2 without any other mappings: > >>> > >>> libpthread.so.1 libpthread.so.2 > >> > >> This is just a partial workaround, of course, and any of your > >> binaries that are also linked to two versions of other libraries > >> may still experience crashes (or may start to crash later when the > >> new libraries change further). You really want to track down and > >> fix the root cause now, to save you hours of pain later when the > >> problem recurs elsewhere. > > > > The thing is I don't need the libpthread.so.1 to libpthread.so.2 > > mapping, it works anyway (although mysql crashes) but when mapping > > libpthread.so* to libthr* it works perfectly. >=20 > It would be nice to find the bug rather than a workaround. Can you > get a stack dump of the server? The bug is well understood and is solely on the user end (operator did not upgrade software correctly, and caused it to be linked to two versions of the same library), it's not a software or FreeBSD bug. Kris --envbJBWh7q8WU6mo Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDaArjWry0BWjoQKURAgaDAJ9hF1EfPrrCt8Fjq0JbSog6A7YueACfQYzC Zubtc+jn89ebErlCku6RigQ= =s4LW -----END PGP SIGNATURE----- --envbJBWh7q8WU6mo-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 00:44:39 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D758916A41F for ; Wed, 2 Nov 2005 00:44:38 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 887A943D45 for ; Wed, 2 Nov 2005 00:44:38 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by mail.ambrisko.com with ESMTP; 01 Nov 2005 16:44:38 -0800 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.12.11/8.12.9) with ESMTP id jA20ibR4041465; Tue, 1 Nov 2005 16:44:37 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.12.11/8.12.11/Submit) id jA20ibXV041464; Tue, 1 Nov 2005 16:44:37 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200511020044.jA20ibXV041464@ambrisko.com> In-Reply-To: <43680737.6080108@samsco.org> To: Scott Long Date: Tue, 1 Nov 2005 16:44:37 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: current@freebsd.org Subject: Re: Rocket Port update patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 00:44:39 -0000 Scott Long writes: | Doug Ambrisko wrote: | > I've brought in the changes to the driver from the Comtrol web site. | > This greatly improves the RocketPort HW support for those devices. | > The changes are at: | > http://www.ambrisko.com/doug/rp_current.patch | > | > I'd like to commit it so things just work out of the box. I tried to | > maintain all the various FreeBSD & Comtrol changes. | > | > It works here on my previously unsupported card. | | One thing stands out on the brief skim. Why on earth does the code need | to keep a global count of the number of adapters, and why does it bail | if there are more than 4 adapters? I don't know. Do we have a contact there to ask questions? I don't have more then one 16 port adapter to see if there is a problem. That brings up a point, we need to scope the functions and stuff so they don't conflict with other stuff. I kind-of hate to change all the names to make it easier to merge in changes later. Should we change all the sFlushRxFIFO type stuff to rp_s_flush_rx_fifo and put the globals into the softc's? Obviously they've put some effort into supporting FreeBSD which is a good thing. I don't know how things go between them and us. Thanks, Doug A. From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 02:12:28 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3749016A41F for ; Wed, 2 Nov 2005 02:12:28 +0000 (GMT) (envelope-from nocool@263.net) Received: from smtp.263.net (smtp.263.net [211.150.96.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77BA843D45; Wed, 2 Nov 2005 02:12:26 +0000 (GMT) (envelope-from nocool@263.net) Received: from iscas-zfw728iit (smtp1 [127.0.0.1]) by smtp.263.net (Postfix) with ESMTP id B1542E5E; Wed, 2 Nov 2005 10:12:26 +0800 (CST) (envelope-from nocool@263.net) X-Originating-IP: [159.226.5.225] Date: Wed, 2 Nov 2005 10:13:08 +0800 From: "nocool" To: "freebsd-current" X-mailer: Foxmail 5.0 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit Message-Id: <20051102021226.B1542E5E@smtp.263.net> Cc: freebsd-hacker Subject: Why INVARIANTS option and sanity checking? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 02:12:28 -0000 Hi, I need some explanation about INVARIANTS compile option. This option has the description that enable calls of extra sanity checking. What does sanity mean here? Where and why we need to use this option? I find some codes in kern/kern_malloc.c in 5.4 kernel: 511 kmemzones[indx].kz_zone = uma_zcreate(name, size, 512 #ifdef INVARIANTS 513 mtrash_ctor, mtrash_dtor, mtrash_init, mtrash_fini, 514 #else 515 NULL, NULL, NULL, NULL, 516 #endif 517 UMA_ALIGN_PTR, UMA_ZONE_MALLOC); In the case INVARIANTS is defined, kz_zone will be set up with the constructor function mtrash_ctor and destructor function mtrash_dtor. When kz_zone free some items, kernel will call mtrash_dtor(), every item will be filled with the value of uma_junk. When some items will be reallocated, kernel calls mtrash_ctor() and makes sure the constructing item has'nt been overwritten since it was freed through comparing every int of the item with uma_junk. Why kmemzones need this check, while other zones and memory areas need't? Where comes the danger that the memory item will be overwritted after its free? Thanks From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 02:59:09 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D09EB16A41F; Wed, 2 Nov 2005 02:59:09 +0000 (GMT) (envelope-from nge@cs.hmc.edu) Received: from turing.cs.hmc.edu (turing.cs.hmc.edu [134.173.42.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9200043D45; Wed, 2 Nov 2005 02:59:09 +0000 (GMT) (envelope-from nge@cs.hmc.edu) Received: by turing.cs.hmc.edu (Postfix, from userid 26983) id 2058253286; Tue, 1 Nov 2005 18:59:09 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by turing.cs.hmc.edu (Postfix) with ESMTP id 0AB2F5A8DE; Tue, 1 Nov 2005 18:59:08 -0800 (PST) Date: Tue, 1 Nov 2005 18:59:08 -0800 (PST) From: Nate Eldredge X-X-Sender: nate@turing To: bug-followup@FreeBSD.org, marcolz@stack.nl Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org, rwatson@freebsd.org, Philippe.Pegon@crc.u-strasbg.fr Subject: Re: kern/83375: Fatal trap 12 cloning a pty (was: show stopper for FreeBSD 6) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 02:59:10 -0000 Okay, well I have made some progress here. The problem, at least on 7.0-CURRENT, occurs when you revoke() somebody's controlling tty, and then they try to clone it by opening /dev/tty. revoke() will set the vnode's type to VBAD and ->v_rdev to NULL. However ctty_clone() assumes that if the P_CONTROLT flag is set and p_session->s_ttyvp is non-null then s_ttyvp->v_rdev is non-null as well, and it passes it to dev_ref which dereferences the pointer. One way to fix this is to have ctty_clone check for v_type == VBAD and/or v_rdev == NULL, and treat it like the case of s_ttyvp == NULL (give them the dummy /dev/ctty instead). Does that seem reasonable? I am not very familiar with the kernel, just trying to learn through fixing bugs. When I do that, the screen testcase works until the machine runs out of memory :) The dumps posted from 5.x look very different and this may be a separate bug. Unfortunately I don't have a 5.x test box. Here is a simpler test case. I use /dev/ttyv9 as the terminal device, so you have to be root to run it, but it should also work with a pty. So a regular user could exploit this. ------------------------snip--------------------- #include #include #include #include #include #include #include #define TTY "/dev/ttyv9" /* should be totally unused */ #define CTTY "/dev/tty" int main(void) { int ttyfd; pid_t pid; /* Get rid of my ctty. */ printf("Parent starting: pid %d\n", getpid()); pid = fork(); if (pid < 0) { perror("fork"); exit(1); } else if (pid > 0) { int status; /* parent */ waitpid(pid, &status, 0); exit(0); } /* child */ printf("Child: pid %d\n", getpid()); if (setsid() < 0) { perror("setsid"); exit(1); } ttyfd = open(TTY, O_RDWR); if (ttyfd < 0) { perror(TTY); exit(1); } if (ioctl(ttyfd, TIOCSCTTY) < 0) { perror("ioctl(TIOCSCTTY)"); exit(1); } if (revoke(TTY) < 0) { perror("revoke"); exit(1); } if (open(CTTY, O_RDWR) < 0) { perror(CTTY); exit(1); } return 0; } -----------------------------snip------------------- -- Nate Eldredge nge@cs.hmc.edu From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 03:46:19 2005 Return-Path: X-Original-To: FreeBSD-current@FreeBSD.org Delivered-To: FreeBSD-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 159BF16A41F; Wed, 2 Nov 2005 03:46:19 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id C38BC43D46; Wed, 2 Nov 2005 03:46:18 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from smiley (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id DF62A19F2C; Tue, 1 Nov 2005 19:52:21 -0800 (PST) From: "Darren Pilgrim" To: "'Greg 'groggy' Lehey'" Date: Tue, 1 Nov 2005 19:46:09 -0800 Message-ID: <002301c5df5f$fa16e9e0$652a15ac@smiley> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <20051101073157.GE18710@wantadilla.lemis.com> Importance: Normal Cc: FreeBSD-current@FreeBSD.org Subject: RE: Really poor performance on /dev/ttyv* only X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 03:46:19 -0000 From: Greg 'groggy' Lehey > I've just installed -CURRENT on a Dell Inspiron 6000, and I discover > that the keyboard response on virtual terminals (/dev/ttyv*) is very > slow. If I keyboard repeat, the echo to the terminal is jerky, about > 3 or 4 characters at a time with a marked delay in between. Under X > or over the network there's no problem. Has anybody else seen this? > The kernel isn't 100% GENERIC (I've disabled WITNESS and > WITNESS_SKIPSPIN, for example), but I can't see anything that would > explain this behaviour. FWIW, I also have an i6k and have a few-months-old -CURRENT running on = it and said problem is not present. I'm not 100% sure of the date, but it = was shortly after the wpa_supplicant import and Brooks Davis' big rc fix-up. = If it's important, I'll grab the sup date and post the assorted = world/kernel configs. From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 09:22:45 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF99E16A4B3; Wed, 2 Nov 2005 09:22:44 +0000 (GMT) (envelope-from mjsaarin@cc.helsinki.fi) Received: from sender-01.it.helsinki.fi (sender-01.it.helsinki.fi [128.214.205.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E15243D48; Wed, 2 Nov 2005 09:22:43 +0000 (GMT) (envelope-from mjsaarin@cc.helsinki.fi) Received: from lagavulin.it.helsinki.fi (lagavulin.it.helsinki.fi [128.214.38.143]) by sender-01.it.helsinki.fi (8.13.3/8.13.3) with ESMTP id jA29MfPr029861 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 2 Nov 2005 11:22:41 +0200 Received: (from mjs@localhost) by lagavulin.it.helsinki.fi (8.13.4/8.13.1/Submit) id jA29MeT6048087; Wed, 2 Nov 2005 11:22:40 +0200 (EET) (envelope-from mjsaarin@cc.helsinki.fi) X-Authentication-Warning: lagavulin.it.helsinki.fi: mjs set sender to mjsaarin@cc.helsinki.fi using -f From: Matti Saarinen To: freebsd-current@freebsd.org, freebsd-acpi@freebsd.org Organization: University of Helsinki References: <200511011701.31444.jkim@FreeBSD.org> <200511011749.46273.jkim@FreeBSD.org> Date: Wed, 02 Nov 2005 11:22:40 +0200 In-Reply-To: <200511011749.46273.jkim@FreeBSD.org> (Jung-uk Kim's message of "Tue, 1 Nov 2005 17:49:44 -0500") Message-ID: User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Subject: Re: [HEADSUP] ACPI-CA 20051021 import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 09:22:45 -0000 Jung-uk Kim writes: > On Tuesday 01 November 2005 05:01 pm, Jung-uk Kim wrote: >> ACPI-CA 20051021 will be imported any minute now. I will let you >> know when completed. > > ACPI-CA 20051021 import is completed. Thank you. My T41 running (now) 6.0-RC1 has had several lock-ups when using wlan card before I applied ACPI-CA 20051021 patch. Now, I can use wlan without any trouble. Great. -- - Matti - From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 09:35:27 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F46016A41F; Wed, 2 Nov 2005 09:35:27 +0000 (GMT) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7662043D45; Wed, 2 Nov 2005 09:35:26 +0000 (GMT) (envelope-from max@love2party.net) Received: from p54A3D440.dip.t-dialin.net [84.163.212.64] (helo=donor.laier.local) by mrelayeu.kundenserver.de (node=mrelayeu0) with ESMTP (Nemesis), id 0MKwh2-1EXF1g1qDY-0003Cy; Wed, 02 Nov 2005 10:35:24 +0100 From: Max Laier To: freebsd-current@freebsd.org Date: Wed, 2 Nov 2005 10:35:05 +0100 User-Agent: KMail/1.8.2 References: <20051027022313.R675@kushnir1.kiev.ua> <200510311231.33322.jhb@freebsd.org> <20051102014239.O654@kushnir1.kiev.ua> In-Reply-To: <20051102014239.O654@kushnir1.kiev.ua> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1390064.oq2c42BgXM"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200511021035.22990.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 09:35:27 -0000 --nextPart1390064.oq2c42BgXM Content-Type: multipart/mixed; boundary="Boundary-01=_VhIaDzu6rsEyaMB" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-01=_VhIaDzu6rsEyaMB Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 02 November 2005 00:53, Vladimir Kushnir wrote: > On Mon, 31 Oct 2005, John Baldwin wrote: > > On Sunday 30 October 2005 05:17 pm, Vladimir Kushnir wrote: > >> A bit further. > >> > >> On Sun, 30 Oct 2005, Vladimir Kushnir wrote: > >>> OK, here it is. It's happened between 2005.10.21.19.42.50 and > >>> 2005.10.22.05.07.00. > >>> Since then, panic is absolutely reproducible. > >> > >> Actually, when I took INET6 from kernel (once again, it's GENERIC) the= se > >> panics stop. > > > > Hmmm. Are those timestamps UTC? If so, there's nothing worthwhile that > > changed in there: > > Sorry I was a bit vague. > > > suz 2005-10-21 16:23:01 UTC > > > > FreeBSD src repository > > > > Modified files: > > sys/netinet icmp6.h > > sys/netinet6 icmp6.c in6.c in6.h in6_ifattach.c > > in6_ifattach.h in6_var.h ip6_output.c > > mld6.c mld6_var.h nd6.c nd6.h nd6_nbr.c > > nd6_rtr.c > > share/doc/IPv6 IMPLEMENTATION > > This was when panics begun. And they're still here. That brings me back to ln_timer_ch as the culprit. Could you please build= =20 with this patch and get me the console output shortly before the panic? =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --Boundary-01=_VhIaDzu6rsEyaMB Content-Type: text/x-diff; charset="iso-8859-1"; name="nd6_llinfo_settimer.printf.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="nd6_llinfo_settimer.printf.diff" Index: nd6.c =================================================================== RCS file: /usr/store/mlaier/fcvs/src/sys/netinet6/nd6.c,v retrieving revision 1.62 diff -u -p -r1.62 nd6.c --- nd6.c 22 Oct 2005 05:07:16 -0000 1.62 +++ nd6.c 31 Oct 2005 18:49:58 -0000 @@ -395,6 +395,7 @@ nd6_llinfo_settimer(ln, tick) struct llinfo_nd6 *ln; long tick; { + printf("For %p %ld ticks\n", ln, tick); if (tick < 0) { ln->ln_expire = 0; ln->ln_ntick = 0; --Boundary-01=_VhIaDzu6rsEyaMB-- --nextPart1390064.oq2c42BgXM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDaIhaXyyEoT62BG0RAuGbAJ4vu9uChMsO/Fw0oEdQN0ZWjaPsFgCeKwh1 P59fwxcHYlhC1perv+8Wo/Y= =FGYB -----END PGP SIGNATURE----- --nextPart1390064.oq2c42BgXM-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 10:34:40 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C98016A41F; Wed, 2 Nov 2005 10:34:40 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C95E43D46; Wed, 2 Nov 2005 10:34:38 +0000 (GMT) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost [127.0.0.1]) by mp2.macomnet.net (8.13.3/8.13.3) with ESMTP id jA2AYVe5007983; Wed, 2 Nov 2005 13:34:32 +0300 (MSK) (envelope-from maxim@macomnet.ru) Date: Wed, 2 Nov 2005 13:34:31 +0300 (MSK) From: Maxim Konovalov To: Uwe Doering In-Reply-To: <4366336E.8070601@geminix.org> Message-ID: <20051102132937.Y7915@mp2.macomnet.net> References: <2b22951e0510302128q571a3c1se111262e88ae19bb@mail.gmail.com> <20051031144056.A92356@mp2.macomnet.net> <20051031162438.I554@is.park.rambler.ru> <20051031170805.T94695@mp2.macomnet.net> <4366336E.8070601@geminix.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Edwin Groothuis , Igor Sysoev , bug-followup@freebsd.org, "Cai, Quanqing" , freebsd-current@freebsd.org Subject: Re: kern/67919: Why nobody take serious to fix this bug? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 10:34:40 -0000 On Mon, 31 Oct 2005, 16:08+0100, Uwe Doering wrote: > Maxim Konovalov wrote: > > [...] > > > > > >I was told the patch is incorrect. It works in certain cases but > > > >incorrect in general. > > > > > >Why is it incorrect ? I'm using it for year. > > > > Because you can't just throw away any chunk of data (e.g. it could be > > a meta-data) without a risk to damage a filesystem. > > I wonder, could it really be meta-data? I was under the impression > that meta-data is a filesystem property and is therefore dealt with > in the filesystem code, through i/o buffers. Isn't the VM pager > responsible for handling object contents (files etc.), only? If so, > it would be unfortunate to throw away pages of data but it certainly > wouldn't damage the filesystem. I'm under different (perhaps incorrect) impression. For the record: ps@ just committed to HEAD a rate limit part of your patch with a slightly different implementation. -- Maxim Konovalov From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 10:43:16 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8B9716A41F for ; Wed, 2 Nov 2005 10:43:16 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E63543D46; Wed, 2 Nov 2005 10:43:16 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 0831B46B14; Wed, 2 Nov 2005 05:43:13 -0500 (EST) Date: Wed, 2 Nov 2005 10:43:12 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: nocool In-Reply-To: <20051102021226.B1542E5E@smtp.263.net> Message-ID: <20051102103112.J45155@fledge.watson.org> References: <20051102021226.B1542E5E@smtp.263.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current , freebsd-hacker Subject: Re: Why INVARIANTS option and sanity checking? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 10:43:16 -0000 On Wed, 2 Nov 2005, nocool wrote: > Hi, I need some explanation about INVARIANTS compile option. This option > has the description that enable calls of extra sanity checking. What > does sanity mean here? Where and why we need to use this option? There are a number of debugging kernel options available in the kernel, including INVARIANTS, WITNESS, SOCKBUF_DEBUG, etc. They all exchange performance for checking of programmer belief about the invariants of the source code. The goal is to have the programmer document their beliefs about the state of the system as a series of tests, which are then validated at run time. These tests can be cheap (extra NULL checks), or they can be very expensive (clearing and checking memory on free and allocate, run-time lock order verification). As such, they are used extensively during development, but get turned off in production for performance reasons. For example, for some workloads, we've had reports of 70%+ loss in performance due to running with WITNESS turned on. Part of the goal of an invariants test is to fail-stop the system before it goes from violating a low-level assumption to wide-spread data corruption and hard-to-track bugs. This makes it much easier to analyze the bug and fix it (or for that matter, fix the assertion). As such, most invariant violations will result in a panic and optionally a core dump for diagnostic purposes. However, some invariants testing, such as lock order analysis, is configurable to either generate a warning with debugging trace, or to panic, depending on desired usage. > I find some codes in kern/kern_malloc.c in 5.4 kernel: > > 511 kmemzones[indx].kz_zone = uma_zcreate(name, size, > 512 #ifdef INVARIANTS > 513 mtrash_ctor, mtrash_dtor, mtrash_init, mtrash_fini, > 514 #else > 515 NULL, NULL, NULL, NULL, > 516 #endif > 517 UMA_ALIGN_PTR, UMA_ZONE_MALLOC); > > In the case INVARIANTS is defined, kz_zone will be set up with the > constructor function mtrash_ctor and destructor function mtrash_dtor. > When kz_zone free some items, kernel will call mtrash_dtor(), every item > will be filled with the value of uma_junk. When some items will be > reallocated, kernel calls mtrash_ctor() and makes sure the constructing > item has'nt been overwritten since it was freed through comparing every > int of the item with uma_junk. Why kmemzones need this check, while > other zones and memory areas need't? Where comes the danger that the > memory item will be overwritted after its free? The UMA slab allocator implement an object life cycle, in which memory moves between three states: --zone_init--> --zone_ctor--> [uninitialized] [initialized] [allocated] <--zone_fini-- <--zone_dtor-- This allows the reuse of memory for the same type of object repeatedly, allowing some state to be reused across allocations. For example, threads are always associated with thread stacks. Rather than reallocating the stack separately from the thread, the zone caches the stack with the thread in its initialized state, allowing less work to occur each time a thread is allocated and free'd. As such, there will be data in the memory object that can't be trashed on its destructor and tested on its constructor -- if this were done, the persistent state would be lost. So zones are individually configured to perform memory trashing and testing based on whether or not they take advantage of persistent state between allocations. With regard to why this is helpful -- since the C language is not type safe, nothing in the language prevents touching memory after it has been free'd. Therefore, it is a ripe opportunity for nasty bugs -- things like the following: crfree(cred); cred->cr_uid = 0; These bugs are notoriously hard to catch, as in a multi-threaded, multi-processing kernel, it's possibly that the memory may actually be allocated to another thread as soon as it is free'd, resulting in the above assignment occuring on valid, allocated memory. The ctor and dtor tests are designed to help identify when an access has happened after free, and if so, to memory owned by what zone. MEMGUARD is another similar notion, only it uses the VM system to help detect references to memory using page protections. The above bug example is one of the more simple of its class -- often the bug occurs due to a stray uncleared pointer in another data structure, which may persist for a long time before it is used. Basically, it all comes down to this: invariants and sanity checking allow programmers to test that their assumptions about the source code they (or someone else) has implemented. This helps find bugs faster, and in a way that makes them much easier to debug. Robert N M Watson From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 10:44:41 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDB3416A41F for ; Wed, 2 Nov 2005 10:44:41 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0233E43D45 for ; Wed, 2 Nov 2005 10:44:40 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.3/8.13.3) with ESMTP id jA2AicR3004830; Wed, 2 Nov 2005 13:44:38 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.3/8.13.3/Submit) id jA2AiXBZ004829; Wed, 2 Nov 2005 13:44:34 +0300 (MSK) (envelope-from yar) Date: Wed, 2 Nov 2005 13:44:33 +0300 From: Yar Tikhiy To: Scott Long Message-ID: <20051102104433.GC2465@comp.chem.msu.su> References: <436116D3.908@samsco.org> <621b657f0510280654j56d4a823n5237f89ccc96b1e9@mail.gmail.com> <436246C1.3030108@samsco.org> <20051101165534.GB56709@comp.chem.msu.su> <43679F3C.4040702@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43679F3C.4040702@samsco.org> User-Agent: Mutt/1.5.9i Cc: openglx@starbyte.net, current@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 10:44:41 -0000 On Tue, Nov 01, 2005 at 10:00:44AM -0700, Scott Long wrote: > Yar Tikhiy wrote: > >On Fri, Oct 28, 2005 at 09:41:53AM -0600, Scott Long wrote: > >>Felipe openglx wrote: > >> > >>>I had a few issues with SiS 630 video driver, already related in > >>>thread > >>>http://docs.freebsd.org/cgi/getmsg.cgi?fetch=815881+0+/usr/local/www/db/text/2005/freebsd-current/20051016.freebsd-current > >>> > >>>Are those corrected already? I did compile the latest kernel (after a > >>>cvsup on src-sys*) and X.org still reboots my machine if I enable the > >>>SiS driver. > >> > >>You'll need to work with the X11 developers. X is only something that > >>FreeBSD includes as a 3rd party package, it's not something that we > >>work on as part of the OS. > > > > > >When a 3rd party package crashes our OS, we should care about the > >issue, too. However, this case seems to require more investigation > >by developers who have similar hardware. > > > > The fact that X has access to /dev/io means that it can do whatever it > wants to corrupt the machine, and there isn't much the OS can do about > it. I see, sorry for the noise. -- Yar From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 11:44:19 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B27E16A41F; Wed, 2 Nov 2005 11:44:19 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE76C43D55; Wed, 2 Nov 2005 11:44:18 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.4/8.13.4) with ESMTP id jA2BiHw4096941; Wed, 2 Nov 2005 06:44:17 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id jA2BiHBT055465; Wed, 2 Nov 2005 06:44:17 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id CEDE57302F; Wed, 2 Nov 2005 06:44:16 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051102114416.CEDE57302F@freebsd-current.sentex.ca> Date: Wed, 2 Nov 2005 06:44:16 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 11:44:19 -0000 TB --- 2005-11-02 10:36:20 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-11-02 10:36:20 - starting HEAD tinderbox run for amd64/amd64 TB --- 2005-11-02 10:36:20 - cleaning the object tree TB --- 2005-11-02 10:37:01 - checking out the source tree TB --- 2005-11-02 10:37:01 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2005-11-02 10:37:01 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-11-02 10:44:11 - building world (CFLAGS=-O2 -pipe) TB --- 2005-11-02 10:44:11 - cd /src TB --- 2005-11-02 10:44:11 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -I/src/usr.sbin/acpi/acpiconf/../../../sys -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -o acpiconf acpiconf.o gzip -cn /src/usr.sbin/acpi/acpiconf/acpiconf.8 > acpiconf.8.gz ===> usr.sbin/acpi/acpidb (all) cc -O2 -pipe -DACPI_APPLICATION -DACPI_DEBUG_OUTPUT -DACPI_DEBUGGER -DACPI_DISASSEMBLER -I/src/usr.sbin/acpi/acpidb/../../../sys -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/usr.sbin/acpi/acpidb/acpidb.c cc -O2 -pipe -DACPI_APPLICATION -DACPI_DEBUG_OUTPUT -DACPI_DEBUGGER -DACPI_DISASSEMBLER -I/src/usr.sbin/acpi/acpidb/../../../sys -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/osunixxf.c cc -O2 -pipe -DACPI_APPLICATION -DACPI_DEBUG_OUTPUT -DACPI_DEBUGGER -DACPI_DISASSEMBLER -I/src/usr.sbin/acpi/acpidb/../../../sys -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/dbcmds.c /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/dbcmds.c: In function `AcpiDbBusWalk': /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/dbcmds.c:1741: warning: dereferencing type-punned pointer will break strict-aliasing rules *** Error code 1 Stop in /src/usr.sbin/acpi/acpidb. *** Error code 1 Stop in /src/usr.sbin/acpi. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-02 11:44:16 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-02 11:44:16 - ERROR: failed to build world TB --- 2005-11-02 11:44:16 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 12:50:31 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D61716A41F; Wed, 2 Nov 2005 12:50:31 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D311643D46; Wed, 2 Nov 2005 12:50:30 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id jA2CoTWH059715; Wed, 2 Nov 2005 07:50:29 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id jA2CoTvL016870; Wed, 2 Nov 2005 07:50:29 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 749F37302F; Wed, 2 Nov 2005 07:50:29 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051102125029.749F37302F@freebsd-current.sentex.ca> Date: Wed, 2 Nov 2005 07:50:29 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 12:50:31 -0000 TB --- 2005-11-02 11:44:17 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-11-02 11:44:17 - starting HEAD tinderbox run for i386/i386 TB --- 2005-11-02 11:44:17 - cleaning the object tree TB --- 2005-11-02 11:44:52 - checking out the source tree TB --- 2005-11-02 11:44:52 - cd /tinderbox/HEAD/i386/i386 TB --- 2005-11-02 11:44:52 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-11-02 11:51:29 - building world (CFLAGS=-O2 -pipe) TB --- 2005-11-02 11:51:29 - cd /src TB --- 2005-11-02 11:51:29 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -I/src/usr.sbin/acpi/acpiconf/../../../sys -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -o acpiconf acpiconf.o gzip -cn /src/usr.sbin/acpi/acpiconf/acpiconf.8 > acpiconf.8.gz ===> usr.sbin/acpi/acpidb (all) cc -O2 -pipe -DACPI_APPLICATION -DACPI_DEBUG_OUTPUT -DACPI_DEBUGGER -DACPI_DISASSEMBLER -I/src/usr.sbin/acpi/acpidb/../../../sys -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/usr.sbin/acpi/acpidb/acpidb.c cc -O2 -pipe -DACPI_APPLICATION -DACPI_DEBUG_OUTPUT -DACPI_DEBUGGER -DACPI_DISASSEMBLER -I/src/usr.sbin/acpi/acpidb/../../../sys -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/osunixxf.c cc -O2 -pipe -DACPI_APPLICATION -DACPI_DEBUG_OUTPUT -DACPI_DEBUGGER -DACPI_DISASSEMBLER -I/src/usr.sbin/acpi/acpidb/../../../sys -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/dbcmds.c /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/dbcmds.c: In function `AcpiDbBusWalk': /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/dbcmds.c:1741: warning: dereferencing type-punned pointer will break strict-aliasing rules *** Error code 1 Stop in /src/usr.sbin/acpi/acpidb. *** Error code 1 Stop in /src/usr.sbin/acpi. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-02 12:50:29 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-02 12:50:29 - ERROR: failed to build world TB --- 2005-11-02 12:50:29 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 12:58:21 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8A8C16A430 for ; Wed, 2 Nov 2005 12:58:21 +0000 (GMT) (envelope-from vincent@xtra-net.org) Received: from relay.xtra-net.org (cable-195-162-200-89.customer.tvd.be [195.162.200.89]) by mx1.FreeBSD.org (Postfix) with SMTP id 6616D43D45 for ; Wed, 2 Nov 2005 12:58:16 +0000 (GMT) (envelope-from vincent@xtra-net.org) Received: (qmail 7318 invoked from network); 2 Nov 2005 12:58:15 -0000 Received: from sbegfxab.xtra-net.org (HELO mail.xtra-net.org) (192.168.1.19) by 0 with SMTP; 2 Nov 2005 12:58:15 -0000 Received: from 192.168.1.25 (proxying for 193.178.209.194) (SquirrelMail authenticated user jlang); by mail.xtra-net.org with HTTP; Wed, 2 Nov 2005 13:58:15 +0100 (CET) Message-ID: <46067.192.168.1.25.1130936295.squirrel@192.168.1.25> In-Reply-To: <00cb01c5deef$d8d19110$931fa8c0@venti> References: <1130853135.5987.18.camel@wbedllfs.xtra-net.org> <00cb01c5deef$d8d19110$931fa8c0@venti> Date: Wed, 2 Nov 2005 13:58:15 +0100 (CET) From: "Vincent Blondel" To: current@freebsd.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: Subject: Re: kernel question ??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 12:58:21 -0000 Thanks for your reply ... Everything is working fine now. Regards Vincent > ----- Original Message ----- > From: "Vincent Blondel" > To: > Sent: Tuesday, November 01, 2005 8:52 AM > Subject: kernel question ??? > > >> Hello all, >> >> Sorry for this, maybe stupid, question but I more often compile kernels >> on Linux platforms. >> >> So, in linux world, there is a very simple way to compile devices as >> modules and I am now trying to do this same feature in my FreeBSD kernel >> ( 7.0-current ) for all network devices ( all /boot/kernel/if_xxx.so ) >> that I would like to (un)load when it is necessary. >> >> I don't know if it is the right way to do it but I removed all network >> devices from my kernel config file (see below) but I get some problems >> when compiling the kernel (see below). >> >> Could you please help me to solve this problem ? > > You took out device miibus > Yet you left in these nic devices which require miibus, as stated right in > the comment: > > # USB Ethernet, requires miibus > device aue # ADMtek USB Ethernet > device axe # ASIX Electronics USB Ethernet > device cdce # Generic USB over Ethernet > device cue # CATC USB Ethernet > device kue # Kawasaki LSI USB Ethernet > device rue # RealTek RTL8150 USB Ethernet > > > Either take _all_ nic devices out and load what you want as modules in > /boot/loader.conf > (The modules still get built when you remove the devices from the kernel > config.) > > /boot/loader.conf: > miibus_load="YES" > if_fxp_load="YES" > > Or put "device miibus" back in, along with any nic devices you'll actually > use. > > I think it's even possible to load the nic driver as a module even when you > are pxe booting via that nic. > > Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/ > +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. > filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! > > >> Regards >> Vincent >> >> ----- >> >> kernel config file RELENG_6_i686 >> >> machine i386 >> cpu I686_CPU >> ident RELENG_6_i686 >> >> # To statically compile in device wiring instead of /boot/device.hints >> #hints "GENERIC.hints" # Default places to look for devices. >> >> makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols >> >> options SC_DISABLE_REBOOT >> >> #options SCHED_ULE # ULE scheduler >> options SCHED_4BSD # 4BSD scheduler >> options PREEMPTION # Enable kernel thread preemption >> 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 COMPAT_FREEBSD5 # Compatible with FreeBSD5 >> options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI >> options KTRACE # ktrace(1) support >> options SYSVSHM # SYSV-style shared memory >> options SYSVMSG # SYSV-style message queues >> options SYSVSEM # SYSV-style semaphores >> options _KPOSIX_PRIORITY_SCHEDULING >> 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. >> >> # Debugging for use in -current >> options KDB # Enable kernel debugger support. >> options DDB # Support DDB. >> options GDB # Support remote GDB. >> options INVARIANTS # Enable calls of extra sanity checking >> options INVARIANT_SUPPORT # Extra sanity checks of internal structures, >> required by INVARIANTS >> options WITNESS # Enable checks to detect deadlocks and cycles >> options WITNESS_SKIPSPIN # Don't run witness on spinlocks for speed >> >> # To make an SMP kernel, the next two lines are needed >> #options SMP # Symmetric MultiProcessor Kernel >> device apic # I/O APIC >> >> # Bus support. >> 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 ispfw # Firmware for QLogic HBAs- normally a module >> device mpt # LSI-Logic MPT-Fusion >> #device ncr # NCR/Symbios Logic >> device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') >> device trm # Tekram DC395U/UW/F DC315U adapters >> >> device adv # Advansys SCSI adapters >> device adw # Advansys wide SCSI adapters >> device aha # Adaptec 154x SCSI adapters >> device aic # Adaptec 15[012]x SCSI adapters, AIC-6[23]60. >> device bt # Buslogic/Mylex MultiMaster SCSI adapters >> >> device ncv # NCR 53C500 >> device nsp # Workbit Ninja SCSI-3 >> device stg # TMC 18C30/18C50 >> >> # SCSI peripherals >> device scbus # SCSI bus (required for SCSI) >> device ch # SCSI media changers >> device da # Direct Access (disks) >> device sa # Sequential Access (tape etc) >> device cd # CD >> device pass # Passthrough device (direct SCSI access) >> device ses # SCSI Environmental Services (and SAF-TE) >> >> # RAID controllers interfaced to the SCSI subsystem >> device amr # AMI MegaRAID >> device arcmsr # Areca SATA II RAID >> device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID >> device ciss # Compaq Smart RAID 5* >> device dpt # DPT Smartcache III, IV - See NOTES for options >> device hptmv # Highpoint RocketRAID 182x >> device 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 >> >> # 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 >> >> # ISA devices that use the old ISA shims >> #device le >> >> # Pseudo devices. >> device loop # Network loopback >> device random # Entropy device >> device ether # Ethernet support >> device sl # Kernel SLIP >> device ppp # Kernel PPP >> device tun # Packet tunnel. >> device pty # Pseudo-ttys (telnet etc) >> device md # Memory "disks" >> device gif # IPv6 and IPv4 tunneling >> device faith # IPv6-to-IPv4 relaying (translation) >> >> # The `bpf' device enables the Berkeley Packet Filter. >> # Be aware of the administrative consequences of enabling this! >> # Note that 'bpf' is required for DHCP. >> device bpf # Berkeley packet filter >> >> # USB support >> device uhci # UHCI PCI->USB interface >> device ohci # OHCI PCI->USB interface >> device ehci # EHCI PCI->USB interface (USB 2.0) >> device usb # USB Bus (required) >> #device udbp # USB Double Bulk Pipe devices >> device ugen # Generic >> device uhid # "Human Interface Devices" >> device ukbd # Keyboard >> device ulpt # Printer >> device umass # Disks/Mass storage - Requires scbus and da >> device ums # Mouse >> device ural # Ralink Technology RT2500USB wireless NICs >> device urio # Diamond Rio 500 MP3 player >> device uscanner # Scanners >> # USB Ethernet, requires miibus >> device aue # ADMtek USB Ethernet >> device axe # ASIX Electronics USB Ethernet >> device cdce # Generic USB over Ethernet >> device cue # CATC USB Ethernet >> device kue # Kawasaki LSI USB Ethernet >> device rue # RealTek RTL8150 USB Ethernet >> >> # FireWire support >> device firewire # FireWire bus code >> device sbp # SCSI over FireWire (Requires scbus and da) >> device fwe # Ethernet over FireWire (non-standard!) >> >> ----- >> >> make buildkernel KERNCONF=RELENG_6_i686 >> >> MAKE=/usr/obj/usr/src/make.i386/make sh /usr/src/sys/conf/newvers.sh >> RELENG_6_i686 >> cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs >> -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline >> -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. >> -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL >> -DHAVE_KERNEL_OPTION_HEADERS -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 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 >> -mno-sse3 -ffreestanding -Werror vers.c >> linking kernel.debug >> if_aue.o(.text+0x96d): In function `aue_attach': >> /usr/src/sys/dev/usb/if_aue.c:749: undefined reference to >> `mii_phy_probe' >> if_aue.o(.text+0xcfe): In function `aue_tick': >> /usr/src/sys/dev/usb/if_aue.c:1032: undefined reference to `mii_tick' >> if_aue.o(.text+0x1051): In function `aue_init': >> /usr/src/sys/dev/usb/if_aue.c:1198: undefined reference to >> `mii_mediachg' >> if_aue.o(.text+0x1156): In function `aue_ifmedia_upd': >> /usr/src/sys/dev/usb/if_aue.c:1263: undefined reference to >> `mii_phy_reset' >> if_aue.o(.text+0x1166):/usr/src/sys/dev/usb/if_aue.c:1265: undefined >> reference to `mii_mediachg' >> if_aue.o(.text+0x1191): In function `aue_ifmedia_sts': >> /usr/src/sys/dev/usb/if_aue.c:1279: undefined reference to >> `mii_pollstat' >> if_aue.o(.data+0x90): In function `aue_csr_read_2': >> /usr/src/sys/dev/usb/if_aue.c:294: undefined reference to >> `miibus_readreg_desc' >> if_aue.o(.data+0x98):/usr/src/sys/dev/usb/if_aue.c:295: undefined >> reference to `miibus_writereg_desc' >> if_aue.o(.data+0xa0):/usr/src/sys/dev/usb/if_aue.c:296: undefined >> reference to `miibus_statchg_desc' >> if_aue.o(.data+0x114): In function `aue_csr_write_1': >> /usr/src/sys/dev/usb/if_aue.c:325: undefined reference to >> `miibus_driver' >> if_aue.o(.data+0x118):/usr/src/sys/dev/usb/if_aue.c:325: undefined >> reference to `miibus_devclass' >> if_axe.o(.text+0x1fe): In function `axe_ifmedia_upd': >> /usr/src/sys/dev/usb/if_axe.c:296: undefined reference to >> `mii_phy_reset' >> if_axe.o(.text+0x20e):/usr/src/sys/dev/usb/if_axe.c:298: undefined >> reference to `mii_mediachg' >> if_axe.o(.text+0x239): In function `axe_ifmedia_sts': >> /usr/src/sys/dev/usb/if_axe.c:312: undefined reference to `mii_pollstat' >> if_axe.o(.text+0x6a1): In function `axe_attach': >> /usr/src/sys/dev/usb/if_axe.c:509: undefined reference to >> `mii_phy_probe' >> if_axe.o(.text+0x9ea): In function `axe_tick': >> /usr/src/sys/dev/usb/if_axe.c:739: undefined reference to `mii_tick' >> if_axe.o(.data+0x70): In function `axe_cmd': >> /usr/src/sys/dev/usb/if_axe.c:198: undefined reference to >> `miibus_readreg_desc' >> if_axe.o(.data+0x78):/usr/src/sys/dev/usb/if_axe.c:201: undefined >> reference to `miibus_writereg_desc' >> if_axe.o(.data+0x80):/usr/src/sys/dev/usb/if_axe.c:204: undefined >> reference to `miibus_statchg_desc' >> if_axe.o(.data+0xf4): In function `axe_miibus_readreg': >> /usr/src/sys/dev/usb/if_axe.c:234: undefined reference to >> `miibus_driver' >> if_axe.o(.data+0xf8):/usr/src/sys/dev/usb/if_axe.c:234: undefined >> reference to `miibus_devclass' >> if_ural.o(.text+0x3bb): In function `ural_attach': >> /usr/src/sys/dev/usb/if_ural.c:458: undefined reference to >> `ieee80211_ieee2mhz' >> if_ural.o(.text+0x3ef):/usr/src/sys/dev/usb/if_ural.c:463: undefined >> reference to `ieee80211_ieee2mhz' >> if_ural.o(.text+0x427):/usr/src/sys/dev/usb/if_ural.c:468: undefined >> reference to `ieee80211_ieee2mhz' >> if_ural.o(.text+0x4bb):/usr/src/sys/dev/usb/if_ural.c:480: undefined >> reference to `ieee80211_ieee2mhz' >> if_ural.o(.text+0x4e2):/usr/src/sys/dev/usb/if_ural.c:487: undefined >> reference to `ieee80211_ifattach' >> if_ural.o(.text+0x513):/usr/src/sys/dev/usb/if_ural.c:493: undefined >> reference to `ieee80211_media_status' >> if_ural.o(.text+0x51e):/usr/src/sys/dev/usb/if_ural.c:493: undefined >> reference to `ieee80211_media_init' >> if_ural.o(.text+0x580):/usr/src/sys/dev/usb/if_ural.c:507: undefined >> reference to `ieee80211_announce' >> if_ural.o(.text+0x628): In function `ural_detach': >> /usr/src/sys/dev/usb/if_ural.c:535: undefined reference to >> `ieee80211_ifdetach' >> if_ural.o(.text+0x73a): In function `ural_free_tx_list': >> /usr/src/sys/dev/usb/if_ural.c:595: undefined reference to >> `ieee80211_free_node' >> if_ural.o(.text+0x8da): In function `ural_media_change': >> /usr/src/sys/dev/usb/if_ural.c:673: undefined reference to >> `ieee80211_media_change' >> if_ural.o(.text+0x954): In function `ural_next_scan': >> /usr/src/sys/dev/usb/if_ural.c:699: undefined reference to >> `ieee80211_next_scan' >> if_ural.o(.text+0xabf): In function `ural_task': >> /usr/src/sys/dev/usb/if_ural.c:756: undefined reference to >> `ieee80211_beacon_alloc' >> if_ural.o(.text+0xc1f): In function `ural_txeof': >> /usr/src/sys/dev/usb/if_ural.c:826: undefined reference to >> `ieee80211_free_node' >> if_ural.o(.text+0xd45): In function `ural_rxeof': >> /usr/src/sys/dev/usb/if_ural.c:890: undefined reference to >> `ieee80211_find_rxnode' >> if_ural.o(.text+0xd5b):/usr/src/sys/dev/usb/if_ural.c:893: undefined >> reference to `ieee80211_input' >> if_ural.o(.text+0xd63):/usr/src/sys/dev/usb/if_ural.c:896: undefined >> reference to `ieee80211_free_node' >> if_ural.o(.text+0x130c): In function `ural_tx_data': >> /usr/src/sys/dev/usb/if_ural.c:1218: undefined reference to >> `ieee80211_crypto_encap' >> if_ural.o(.text+0x179c): In function `ural_start': >> /usr/src/sys/dev/usb/if_ural.c:1321: undefined reference to >> `ieee80211_find_txnode' >> if_ural.o(.text+0x17eb):/usr/src/sys/dev/usb/if_ural.c:1328: undefined >> reference to `ieee80211_encap' >> if_ural.o(.text+0x17fa):/usr/src/sys/dev/usb/if_ural.c:1330: undefined >> reference to `ieee80211_free_node' >> if_ural.o(.text+0x1833):/usr/src/sys/dev/usb/if_ural.c:1338: undefined >> reference to `ieee80211_free_node' >> if_ural.o(.text+0x18e8): In function `ural_watchdog': >> /usr/src/sys/dev/usb/if_ural.c:1370: undefined reference to >> `ieee80211_watchdog' >> if_ural.o(.text+0x19c4): In function `ural_ioctl': >> /usr/src/sys/dev/usb/if_ural.c:1417: undefined reference to >> `ieee80211_ioctl' >> if_ural.o(.text+0x1e30): In function `ural_set_chan': >> /usr/src/sys/dev/usb/if_ural.c:1606: undefined reference to >> `ieee80211_chan2ieee' >> if_rue.o(.text+0x833): In function `rue_attach': >> /usr/src/sys/dev/usb/if_rue.c:689: undefined reference to >> `mii_phy_probe' >> if_rue.o(.text+0xc8a): In function `rue_tick': >> /usr/src/sys/dev/usb/if_rue.c:970: undefined reference to `mii_tick' >> if_rue.o(.text+0xfa4): In function `rue_init': >> /usr/src/sys/dev/usb/if_rue.c:1145: undefined reference to >> `mii_mediachg' >> if_rue.o(.text+0x10f6): In function `rue_ifmedia_upd': >> /usr/src/sys/dev/usb/if_rue.c:1210: undefined reference to >> `mii_phy_reset' >> if_rue.o(.text+0x1106):/usr/src/sys/dev/usb/if_rue.c:1212: undefined >> reference to `mii_mediachg' >> if_rue.o(.text+0x1131): In function `rue_ifmedia_sts': >> /usr/src/sys/dev/usb/if_rue.c:1227: undefined reference to >> `mii_pollstat' >> if_rue.o(.data+0x50): In function `rue_read_mem': >> /usr/src/sys/dev/usb/if_rue.c:231: undefined reference to >> `miibus_readreg_desc' >> if_rue.o(.data+0x58):/usr/src/sys/dev/usb/if_rue.c:241: undefined >> reference to `miibus_writereg_desc' >> if_rue.o(.data+0x60):/usr/src/sys/dev/usb/if_rue.c:235: undefined >> reference to `miibus_statchg_desc' >> if_rue.o(.data+0xd4): In function `rue_write_mem': >> /usr/src/sys/dev/usb/if_rue.c:261: undefined reference to >> `miibus_driver' >> if_rue.o(.data+0xd8):/usr/src/sys/dev/usb/if_rue.c:261: undefined >> reference to `miibus_devclass' >> *** Error code 1 >> >> Stop in /usr/obj/usr/src/sys/RELENG_6_i686. >> *** Error code 1 >> >> Stop in /usr/src. >> *** Error code 1 >> >> Stop in /usr/src. >> >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 08:49:55 2005 Return-Path: X-Original-To: FreeBSD-current@FreeBSD.org Delivered-To: FreeBSD-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1BC8716A41F for ; Wed, 2 Nov 2005 08:49:55 +0000 (GMT) (envelope-from samspeedu@mail.ru) Received: from mx3.mail.ru (mx3.mail.ru [194.67.23.149]) by mx1.FreeBSD.org (Postfix) with ESMTP id B49E743D45 for ; Wed, 2 Nov 2005 08:49:54 +0000 (GMT) (envelope-from samspeedu@mail.ru) Received: from [80.82.44.194] (port=12413 helo=192.168.168.7) by mx3.mail.ru with esmtp id 1EXEJc-000B3s-00 for FreeBSD-current@FreeBSD.org; Wed, 02 Nov 2005 11:49:52 +0300 Date: Wed, 2 Nov 2005 11:48:23 +0300 From: Andrey Smagin X-Mailer: The Bat! (v1.62r) Organization: DiP X-Priority: 3 (Normal) Message-ID: <3410224838.20051102114823@mail.ru> To: FreeBSD-current@FreeBSD.org In-Reply-To: <002301c5df5f$fa16e9e0$652a15ac@smiley> References: <002301c5df5f$fa16e9e0$652a15ac@smiley> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 02 Nov 2005 14:27:29 +0000 Cc: Subject: From CURRENT-i386 -> CURRENT amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: SAMU List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 08:49:55 -0000 Hi ALL. How I can safe switch platform ? -- Best regards, Andrey mailto:samspeedu@mail.ru From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 09:14:29 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50DF316A41F for ; Wed, 2 Nov 2005 09:14:29 +0000 (GMT) (envelope-from ndenev@icdsoft.com) Received: from office.suresupport.com (office.suresupport.com [213.145.98.15]) by mx1.FreeBSD.org (Postfix) with SMTP id 4AE6D43D45 for ; Wed, 2 Nov 2005 09:14:27 +0000 (GMT) (envelope-from ndenev@icdsoft.com) Received: (qmail 14347 invoked by uid 1026); 2 Nov 2005 09:19:11 -0000 Received: from 213.145.98.14 by office.suresupport.com (envelope-from , uid 1004) with qmail-scanner-1.23 (f-prot: 4.4.2/3.14.11. Clear:RC:1(213.145.98.14):. Processed in 0.129481 secs); 02 Nov 2005 09:19:11 -0000 Received: from unknown (HELO 14.98.145.213.in-addr.arpa) (213.145.98.14) by office.suresupport.com with SMTP; 2 Nov 2005 09:19:11 -0000 From: Niki Denev Organization: ICD Soft To: freebsd-current@freebsd.org Date: Wed, 2 Nov 2005 11:14:25 +0200 User-Agent: KMail/1.8 References: <200510191647.10254.nike_d@cytexbg.com> In-Reply-To: <200510191647.10254.nike_d@cytexbg.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2527784.GI0tsGTi7U"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200511021114.25375.ndenev@icdsoft.com> X-Mailman-Approved-At: Wed, 02 Nov 2005 14:27:29 +0000 Subject: Re: devctl man page is out of date X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 09:14:29 -0000 --nextPart2527784.GI0tsGTi7U Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Wednesday 19 October 2005 16:47, Niki Denev wrote: > Shouldn't the devctl(4) man page be updated to include the notify events > "!"? Right now it lists only "+", "-", "?" resp. attach, detach and > nomatch. > > Should a PR be filed for this? Well.... i filed it as docs/88390 -- --Niki Denev PGP KeyId: 0xF2DB7EB9 --nextPart2527784.GI0tsGTi7U Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBDaINxHNAJ/fLbfrkRAip3AJ9bTcMaXYfNFOx5Aqcm1vmL2IgN8gCeLRkL hsieF4eVlHaWkHlO+/+RIac= =bxyn -----END PGP SIGNATURE----- --nextPart2527784.GI0tsGTi7U-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 14:58:50 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 256BA16A41F; Wed, 2 Nov 2005 14:58:50 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw1.york.ac.uk (mail-gw1.york.ac.uk [144.32.128.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3610F43D70; Wed, 2 Nov 2005 14:58:44 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy-128.york.ac.uk [144.32.128.160]) by mail-gw1.york.ac.uk (8.12.10/8.12.10) with ESMTP id jA2Ewba2006984; Wed, 2 Nov 2005 14:58:37 GMT Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.4/8.13.4) with ESMTP id jA2Ewa2S052113; Wed, 2 Nov 2005 14:58:36 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.4/8.13.4/Submit) id jA2Ewa1o052112; Wed, 2 Nov 2005 14:58:36 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: freebsd-current@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Wed, 02 Nov 2005 14:58:36 +0000 Message-Id: <1130943516.51544.34.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Cc: rwatson@freebsd.org Subject: Poor NFS server performance in 6.0 with SMP and mpsafenet=1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 14:58:50 -0000 Hi, I'm seeing incredibly poor performance when serving files from an SMP FreeBSD 6.0RC1 server to a Solaris 10 client. I've done some experimenting and have discovered that either removing SMP from the kernel, or setting debug.mpsafenet=0 in loader.conf massively improves the speed. Switching preemption off seems to also help. A quick summary of my findings: switching SMP off and setting mpsafenet=0 gives more than 700% boost in performance. PREEMPTION is a pessimisation in the SMP case, mpsafenet=1 is a pessimisation in all cases. Given these are three of the major new features in 6.0, this doesn't seem ideal :) The following are average times, in seconds, to serve a 512meg file over NFS to the Solaris host. Each experiment was performed immediately after a reboot of the FreeBSD host, and after one untimed transfer (in order to warm the FreeBSD vfs cache). No SMP, mpsafenet=1 59.4 No SMP, mpsafenet=0 49.4 No SMP, mpsafenet=1, no PREEMPTION 53.1 No SMP, mpsafenet=0, no PREEMPTION 51.9 SMP, mpsafenet=1 351.7 SMP, mpsafenet=0 74.5 SMP, mpsafenet=1, no PREEMPTION 264.9 SMP, mpsafenet=0, no PREEMPTION 53.7 Obviously this is not ideal, but at least I have a usable workaround. I'm just worried that the default SMP configuration performs so poorly (although I appreciate that GENERIC does not include SMP, anyone with a multiprocessor machine presumably would want to use it...) The FreeBSD machine is a twin 866MHz P3, running 6.-RC1 with ACPI enabled. The network cards are 64bit/66MHz em(4) cards using checksum offloading etc. Apart from the changes mentioned above, the kernel is GENERIC. I'll get a dmesg online somewhere. I'll also recreate the experiment, serving to a FreeBSD machine as opposed to Solaris, just to compare. I'm happy to do any more investigating to get to the bottom of this, although the machines in question will be going live at the end of the month. Gavin From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 15:07:41 2005 Return-Path: X-Original-To: FreeBSD-current@freebsd.org Delivered-To: FreeBSD-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FB2A16A41F; Wed, 2 Nov 2005 15:07:41 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DC6B43D45; Wed, 2 Nov 2005 15:07:40 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jA2F5BKO035791; Wed, 2 Nov 2005 08:05:11 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 02 Nov 2005 08:05:25 -0700 (MST) Message-Id: <20051102.080525.63054093.imp@bsdimp.com> To: grog@freebsd.org From: "M. Warner Losh" In-Reply-To: <20051101073157.GE18710@wantadilla.lemis.com> References: <20051101070259.GC18710@wantadilla.lemis.com> <4367150C.4030508@mawer.org> <20051101073157.GE18710@wantadilla.lemis.com> 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 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 02 Nov 2005 08:05:12 -0700 (MST) Cc: FreeBSD-current@freebsd.org, fbsd-current@mawer.org Subject: Re: Really poor performance on /dev/ttyv* only X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 15:07:41 -0000 In message: <20051101073157.GE18710@wantadilla.lemis.com> "Greg 'groggy' Lehey" writes: : On Tuesday, 1 November 2005 at 18:11:08 +1100, Antony Mawer wrote: : > On 1/11/2005 6:02 PM, Greg 'groggy' Lehey wrote: : >> I've just installed -CURRENT on a Dell Inspiron 6000, and I discover : >> that the keyboard response on virtual terminals (/dev/ttyv*) is very : >> slow. If I keyboard repeat, the echo to the terminal is jerky, about : >> 3 or 4 characters at a time with a marked delay in between. Under X : >> or over the network there's no problem. Has anybody else seen this? : >> The kernel isn't 100% GENERIC (I've disabled WITNESS and : >> WITNESS_SKIPSPIN, for example), but I can't see anything that would : >> explain this behaviour. : > : > I've seen this on two FreeBSD 4.7 systems connected via a KVM (sharing : > with two Windows 2003 servers)... typing at the console of them was : > almost like typing via ssh on a satellite connection. Connecting via ssh : > was fine, it was only locally that it was a problem. Resetting the : > keyboard repeat rate on BSD had no discernible impact. : : I'd guess that this is a different situation. FWIW, the Inspiron : series are laptops, and this is at the keyboard. The machine is brand : new, and I've never had another version of FreeBSD on it, but I : suspect it's -CURRENT rather than the laptop. I don't see it on my current laptop. It must at least be a combination. Maybe you could track down what the problem is? Warner From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 15:08:06 2005 Return-Path: X-Original-To: FreeBSD-current@freebsd.org Delivered-To: FreeBSD-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC52816A420 for ; Wed, 2 Nov 2005 15:08:06 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BDD443D49 for ; Wed, 2 Nov 2005 15:08:06 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id jA2F85K6076023; Wed, 2 Nov 2005 07:08:05 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id jA2F85u6076022; Wed, 2 Nov 2005 07:08:05 -0800 (PST) (envelope-from sgk) Date: Wed, 2 Nov 2005 07:08:05 -0800 From: Steve Kargl To: Andrey Smagin Message-ID: <20051102150805.GA75891@troutmask.apl.washington.edu> References: <002301c5df5f$fa16e9e0$652a15ac@smiley> <3410224838.20051102114823@mail.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3410224838.20051102114823@mail.ru> User-Agent: Mutt/1.4.2.1i Cc: FreeBSD-current@freebsd.org Subject: Re: From CURRENT-i386 -> CURRENT amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 15:08:06 -0000 On Wed, Nov 02, 2005 at 11:48:23AM +0300, Andrey Smagin wrote: > > How I can safe switch platform ? > Assuming you have an athlon64 or opteron system that is currently running i386 FreeBSD. You need to backup user data, get a list of install ports, and the amd64 ISO images. Now, install amd64 over the top of i386, restore user data, and install the ports. -- Steve From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 15:08:36 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 933DB16A41F for ; Wed, 2 Nov 2005 15:08:36 +0000 (GMT) (envelope-from haro@h4.dion.ne.jp) Received: from smtp1.dcns.ne.jp (smtp1.dcns.ne.jp [203.178.100.134]) by mx1.FreeBSD.org (Postfix) with SMTP id BF94143D48 for ; Wed, 2 Nov 2005 15:08:33 +0000 (GMT) (envelope-from haro@h4.dion.ne.jp) Received: (qmail 9945 invoked by uid 503); 3 Nov 2005 00:08:31 +0900 Received: from unknown (HELO localhost) (211.10.184.118) by smtp1.dcns.ne.jp with SMTP; 3 Nov 2005 00:08:31 +0900 Date: Thu, 03 Nov 2005 00:08:24 +0900 (JST) Message-Id: <20051103.000824.74756516.haro@h4.dion.ne.jp> To: jkim@FreeBSD.org From: Munehiro Matsuda In-Reply-To: <200511011749.46273.jkim@FreeBSD.org> References: <200511011701.31444.jkim@FreeBSD.org> <200511011749.46273.jkim@FreeBSD.org> X-Mailer: Mew version 3.3 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Panic on boot with new ACPI-CA (Re: [HEADSUP] ACPI-CA 20051021 import) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 15:08:36 -0000 From: Jung-uk Kim Date: Tue, 1 Nov 2005 17:49:44 -0500 ::On Tuesday 01 November 2005 05:01 pm, Jung-uk Kim wrote: ::> ACPI-CA 20051021 will be imported any minute now. I will let you ::> know when completed. :: ::ACPI-CA 20051021 import is completed. :: ::Thanks! :: ::Jung-uk Kim Hi, After the import of new ACPI-CA code, I get system panic on boot, where I used to get "can't fetch resources for \\_SB_.PCI0.FNC0.PRT_ - AE_BAD_DATA" message. If you need more info, please let me know. Here's hand written down panic messages. =-------------------------------------------------------------------------- npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 10 on acpi0 pci_link1: irq 11 on acpi0 pci_link2: irq 11 on acpi0 pci_link3: irq 11 on acpi0 pci_link4: irq 11 on acpi0 pci_link5: irq 11 on acpi0 pci_link6: irq 11 on acpi0 pci_link7: irq 11 on acpi0 Memory modified after free 0xc1ee1600(124) val=c @ 0xc1ee1600 panic: Most recently used by acpica cpuid = 0 KDB: enter: panic [thread pid 0 tid 0] Stopped at kbt_enter+0x2b: nop db> bt Tracing pid 0 tid 0 td 0xc0736780 kdb_enter(c06cc93e) at kdb_enter+0x2b panic(c06e42e7,c089c1a8,c06e42b8,c1ee1600,8c) at panic+0x127 mtrash_ctor(c1ee1600,80,0,1) at mtrash_ctor+0x4d uma_zalloc_arg(c104a1e0,0,1) at uma_zalloc_arg+0x10f malloc(68,c089ef00,1,c0c20bb4,c087e562) at malloc+0xb2 AcpiOsAllocate(68,0,c1ece1e0,4,c0c20be0) at AcpiOsAllocate+0x12 AcpiUtCallocate(68,10,c089b337,157,c0c20bec) at AcpiUtCallocate+0x16 AcpiGetObjectInfo(c1ece1e0,c0c20bf8,0,c1ece1e0,ffffffff) at AcpiGetObjectInfo+0x5b acpi_MatchHid(0,c089f740,6,c1ece1e0,0) at acpi_MatchHid+0x32 acpi_probe_child(c1ece1e0,4,c1e9c800,0,0) at acpi_probe_child+0x94 AcpiNsWalkNamespace(0,ffffffff,64,1,c0883c98) at AcpiNsWalkNamespace+0xa1 AcpiWalkNamespace(0,ffffffff,64,c0883c98,c1e9c800) at AcpiWalkNamespace+0x3b acpi_attach(c1e9c800) at acpi_attach+0x4ff device_attach(c1e9c800,0,c1e9c800,c1e9d300,0) at device_attach+0x58 device_probe_and attach(c1e9c800) at device_probe_and_attach+0xe0 bus_generic_attach(c1e9d300,c1e9d300,c1e9d300,c0c20d40,c0529340) at bus_generic_attach+0x16 nexus_attach(c1e9d300) at nexus_attach+0x13 device_attach(c1e9d300,c0533914,c1e9d300,c0721bb0,c28000) at device_attach+0x58 device_probe_and_attach(c1e9d300) at device_probe_and_attach+0xe0 root_bus_configure(c0c20d88,c04eb592,0,c1ec00,c1e000) at root_bus_configure+0x16configure(0,c1ec00,c1e000,0,c04392f5) at configure+0x9 mi_startup() at mi_startup+0x96 begin() at begine+0x2c =-------------------------------------------------------------------------- Following is boot message from the last kernel, just before the import of new code. =-------------------------------------------------------------------------- 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 7.0-CURRENT #135: Mon Oct 31 21:33:52 JST 2005 haro@legacy.ttr.kubota.co.jp:/home/haro/tmp/sys-7/i386/compile/LEGACY WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) M processor 1.10GHz (1097.26-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6d6 Stepping = 6 Features=0xafe9f9bf Features2=0x180 real memory = 787808256 (751 MB) avail memory = 761475072 (726 MB) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 10 on acpi0 pci_link1: irq 11 on acpi0 pci_link2: irq 11 on acpi0 pci_link3: irq 11 on acpi0 pci_link4: irq 11 on acpi0 pci_link5: irq 11 on acpi0 pci_link6: irq 11 on acpi0 pci_link7: irq 11 on acpi0 can't fetch resources for \\_SB_.PCI0.FNC0.PRT_ - AE_BAD_DATA Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xd808-0xd80b on acpi0 cpu0: on acpi0 est0: on cpu0 p4tcc0: on cpu0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.1 (no driver attached) pci0: at device 0.3 (no driver attached) agp0: port 0xeff8-0xefff mem 0xd8000000-0xdfffffff,0xd0000000-0xd007ffff irq 10 at device 2.0 on pci0 agp0: detected 16252k stolen memory agp0: aperture size is 128M pci0: at device 2.1 (no driver attached) uhci0: port 0xcfe0-0xcfff irq 10 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 0xcf80-0xcf9f irq 11 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 0xcf60-0xcf7f irq 11 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 ehci0: mem 0xcffffc00-0xcfffffff irq 11 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered pcib1: at device 30.0 on pci0 pci1: on pcib1 iwi0: mem 0xcfeff000-0xcfefffff irq 11 at device 5.0 on pci1 iwi0: Ethernet address: 00:0e:35:c2:a2:7b fxp0: port 0xcf00-0xcf3f mem 0xcfefe000-0xcfefefff irq 11 at device 8.0 on pci1 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:0e:7b:eb:71:23 cbb0: at device 11.0 on pci1 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb1: at device 11.1 on pci1 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 fwohci0: <1394 Open Host Controller Interface> mem 0xcfefd800-0xcfefdfff,0xcfef8000-0xcfefbfff irq 11 at device 11.2 on pci1 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:00:39:00:00:72:41:eb fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 sbp0: on firewire0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:00:39:72:41:eb fwe0: Ethernet address: 02:00:39:72:41:eb fwe0: if_start running deferred for Giant fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) pci1: at device 11.4 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xbfa0-0xbfaf irq 11 at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 pcm0: port 0xbe00-0xbeff,0xbdc0-0xbdff mem 0xcfdffe00-0xcfdfffff,0xcfdffd00-0xcfdffdff irq 11 at device 31.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: pci0: at device 31.6 (no driver attached) acpi_lid0: on acpi0 battery0: on acpi0 acpi_button0: on acpi0 acpi_acad0: on acpi0 acpi_toshiba0: on acpi0 acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcffff,0xe0000-0xeffff pnpid ORM0000 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1097256406 Hz quality 800 Timecounters tick every 1.000 msec ad0: 57231MB at ata0-master UDMA100 acd0: DVDR at ata1-master UDMA33 pccard1: Allocation failed for cfe 1 sio4: at port 0x2f8-0x2ff irq 11 function 0 config 2 on pccard1 sio4: type 16550A sio4: unable to activate interrupt in fast mode - using normal mode Trying to mount root from ufs:/dev/ad0s4a =-------------------------------------------------------------------------- Thanks in advance, Haro =------------------------------------------------------------------------------ _ _ Munehiro (haro) Matsuda -|- /_\ |_|_| Internet Solution Dept., Kubota Graphics Technologies Inc. /|\ |_| |_|_| 2-8-8 Shinjuku Shinjuku-ku Tokyo 160-0022, Japan Tel: +81-3-3225-0767 Fax: +81-3-3225-0740 From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 15:17:03 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9714C16A41F for ; Wed, 2 Nov 2005 15:17:03 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail5.speedfactory.net [66.23.216.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2797F43D7F for ; Wed, 2 Nov 2005 15:16:50 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 1239540 for multiple; Wed, 02 Nov 2005 10:14:50 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jA2FGaGi057602; Wed, 2 Nov 2005 10:16:43 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 2 Nov 2005 10:10:30 -0500 User-Agent: KMail/1.8.2 References: <200511020044.jA20ibXV041464@ambrisko.com> In-Reply-To: <200511020044.jA20ibXV041464@ambrisko.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511021010.31248.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=100 Cc: Subject: Re: Rocket Port update patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 15:17:03 -0000 On Tuesday 01 November 2005 07:44 pm, Doug Ambrisko wrote: > Scott Long writes: > | Doug Ambrisko wrote: > | > I've brought in the changes to the driver from the Comtrol web site. > | > This greatly improves the RocketPort HW support for those devices. > | > The changes are at: > | > http://www.ambrisko.com/doug/rp_current.patch > | > > | > I'd like to commit it so things just work out of the box. I tried to > | > maintain all the various FreeBSD & Comtrol changes. > | > > | > It works here on my previously unsupported card. > | > | One thing stands out on the brief skim. Why on earth does the code need > | to keep a global count of the number of adapters, and why does it bail > | if there are more than 4 adapters? > > I don't know. Do we have a contact there to ask questions? I don't have > more then one 16 port adapter to see if there is a problem. > > That brings up a point, we need to scope the functions and stuff so > they don't conflict with other stuff. I kind-of hate to change > all the names to make it easier to merge in changes later. > Should we change all the sFlushRxFIFO type stuff to rp_s_flush_rx_fifo > and put the globals into the softc's? Obviously they've put some > effort into supporting FreeBSD which is a good thing. I don't know > how things go between them and us. It seems odd that they want to use explicit bzero() rather than M_ZERO as well. Is that to support really old versions of FreeBSD that didn't have M_ZERO? (I think that's <= 4.2 or some such). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 15:23:52 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E638D16A421; Wed, 2 Nov 2005 15:23:51 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from ant.bwct.de (ant.bwct.de [85.159.14.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBEA643D48; Wed, 2 Nov 2005 15:23:37 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by ant.bwct.de (8.12.11/8.12.11) with ESMTP id jA2FNUmv000589; Wed, 2 Nov 2005 16:23:33 +0100 (CET) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id jA2FNQU2080328 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Nov 2005 16:23:26 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id jA2FNPdL093838; Wed, 2 Nov 2005 16:23:25 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id jA2FNNAM093837; Wed, 2 Nov 2005 16:23:23 +0100 (CET) (envelope-from ticso) Date: Wed, 2 Nov 2005 16:23:23 +0100 From: Bernd Walter To: Gavin Atkinson Message-ID: <20051102152322.GF93549@cicely12.cicely.de> References: <1130943516.51544.34.camel@buffy.york.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1130943516.51544.34.camel@buffy.york.ac.uk> X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 X-Spam-Report: * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on cicely12.cicely.de Cc: freebsd-current@freebsd.org, rwatson@freebsd.org Subject: Re: Poor NFS server performance in 6.0 with SMP and mpsafenet=1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 15:23:52 -0000 On Wed, Nov 02, 2005 at 02:58:36PM +0000, Gavin Atkinson wrote: > Hi, > > I'm seeing incredibly poor performance when serving files from an SMP > FreeBSD 6.0RC1 server to a Solaris 10 client. I've done some > experimenting and have discovered that either removing SMP from the > kernel, or setting debug.mpsafenet=0 in loader.conf massively improves > the speed. Switching preemption off seems to also help. > > A quick summary of my findings: switching SMP off and setting > mpsafenet=0 gives more than 700% boost in performance. PREEMPTION is a > pessimisation in the SMP case, mpsafenet=1 is a pessimisation in all > cases. Given these are three of the major new features in 6.0, this > doesn't seem ideal :) > > The following are average times, in seconds, to serve a 512meg file over > NFS to the Solaris host. Each experiment was performed immediately > after a reboot of the FreeBSD host, and after one untimed transfer (in > order to warm the FreeBSD vfs cache). > > No SMP, mpsafenet=1 59.4 > No SMP, mpsafenet=0 49.4 > No SMP, mpsafenet=1, no PREEMPTION 53.1 > No SMP, mpsafenet=0, no PREEMPTION 51.9 > SMP, mpsafenet=1 351.7 > SMP, mpsafenet=0 74.5 > SMP, mpsafenet=1, no PREEMPTION 264.9 > SMP, mpsafenet=0, no PREEMPTION 53.7 Which scheduler? -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 15:28:06 2005 Return-Path: X-Original-To: FreeBSD-current@freebsd.org Delivered-To: FreeBSD-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D5E316A41F for ; Wed, 2 Nov 2005 15:28:06 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B7EB43D75 for ; Wed, 2 Nov 2005 15:28:06 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id jA2FS5KZ076163; Wed, 2 Nov 2005 07:28:05 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id jA2FS5ia076162; Wed, 2 Nov 2005 07:28:05 -0800 (PST) (envelope-from sgk) Date: Wed, 2 Nov 2005 07:28:05 -0800 From: Steve Kargl To: Andrey Smagin Message-ID: <20051102152805.GA76084@troutmask.apl.washington.edu> References: <002301c5df5f$fa16e9e0$652a15ac@smiley> <3410224838.20051102114823@mail.ru> <20051102150805.GA75891@troutmask.apl.washington.edu> <1849285973.20051102181842@mail.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1849285973.20051102181842@mail.ru> User-Agent: Mutt/1.4.2.1i Cc: FreeBSD-current@freebsd.org Subject: Re: From CURRENT-i386 -> CURRENT amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 15:28:06 -0000 On Wed, Nov 02, 2005 at 06:18:42PM +0300, Andrey Smagin wrote: > > How can I avoid using ISO images for this? I don't remember if amd64 has install floppies. If so you can re-install over the internet. > Build and install from sources ? > It's possible ? Yes, it's possible. Peter Wemm wrote a fairly detailed email on the method he used long ago. I don't know if it still applies. The method isn't for novice FreeBSD users or even for more experienced users. -- Steve From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 15:30:51 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7236A16A41F; Wed, 2 Nov 2005 15:30:51 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C52BE43D45; Wed, 2 Nov 2005 15:30:50 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jA2FUKWg032436; Wed, 2 Nov 2005 08:30:21 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4368DB8C.3030207@samsco.org> Date: Wed, 02 Nov 2005 08:30:20 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <200511020044.jA20ibXV041464@ambrisko.com> <200511021010.31248.jhb@freebsd.org> In-Reply-To: <200511021010.31248.jhb@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-current@freebsd.org Subject: Re: Rocket Port update patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 15:30:51 -0000 John Baldwin wrote: > On Tuesday 01 November 2005 07:44 pm, Doug Ambrisko wrote: > >>Scott Long writes: >>| Doug Ambrisko wrote: >>| > I've brought in the changes to the driver from the Comtrol web site. >>| > This greatly improves the RocketPort HW support for those devices. >>| > The changes are at: >>| > http://www.ambrisko.com/doug/rp_current.patch >>| > >>| > I'd like to commit it so things just work out of the box. I tried to >>| > maintain all the various FreeBSD & Comtrol changes. >>| > >>| > It works here on my previously unsupported card. >>| >>| One thing stands out on the brief skim. Why on earth does the code need >>| to keep a global count of the number of adapters, and why does it bail >>| if there are more than 4 adapters? >> >>I don't know. Do we have a contact there to ask questions? I don't have >>more then one 16 port adapter to see if there is a problem. >> >>That brings up a point, we need to scope the functions and stuff so >>they don't conflict with other stuff. I kind-of hate to change >>all the names to make it easier to merge in changes later. >>Should we change all the sFlushRxFIFO type stuff to rp_s_flush_rx_fifo >>and put the globals into the softc's? Obviously they've put some >>effort into supporting FreeBSD which is a good thing. I don't know >>how things go between them and us. > > > It seems odd that they want to use explicit bzero() rather than M_ZERO as > well. Is that to support really old versions of FreeBSD that didn't have > M_ZERO? (I think that's <= 4.2 or some such). > The usual answer to these kinds of questions is that most driver developers at hardware companies are more accustomed to Solaris and especially Linux. Since the global counts were added somewhat recently, my guess is that it's more a mirror of the linux way of thinking. Scott From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 15:32:56 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A47C16A41F for ; Wed, 2 Nov 2005 15:32:56 +0000 (GMT) (envelope-from db@nipsi.de) Received: from mr01.hansenet.de (mr01.hansenet.de [213.191.74.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C2C143D58 for ; Wed, 2 Nov 2005 15:32:53 +0000 (GMT) (envelope-from db@nipsi.de) Received: from depression.metaspinner.local (213.39.242.178) by mr01.hansenet.de (7.2.060.1) id 4358A57200064CED for freebsd-current@freebsd.org; Wed, 2 Nov 2005 16:32:52 +0100 Received: from depression.metaspinner.local (localhost [127.0.0.1]) by depression.metaspinner.local (Postfix) with ESMTP id 6EA4C7B281; Wed, 2 Nov 2005 13:16:39 +0100 (CET) Received: from [192.168.1.162] (unknown [192.168.1.162]) by depression.metaspinner.local (Postfix) with ESMTP id 3624A78C0D; Wed, 2 Nov 2005 13:16:39 +0100 (CET) Message-ID: <4368AEE3.6030206@nipsi.de> Date: Wed, 02 Nov 2005 13:19:47 +0100 From: Dennis berger User-Agent: Mozilla Thunderbird 1.0.6-1.1.fc3 (X11/20050720) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Philippe PEGON References: <4366879A.7090603@crc.u-strasbg.fr> In-Reply-To: <4366879A.7090603@crc.u-strasbg.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AV-Checked: checked Cc: freebsd-current@freebsd.org Subject: Re: show stopper for FreeBSD 6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 15:32:56 -0000 Philippe PEGON wrote: > Hi, > > I know that it's a bit late for FreeBSD 6 release, but I think this > issue is a significant problem for FreeBSD : > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/83375 > > our productions servers with FreeBSD 5.4 reboots every week with this > panic and we are not alone. We hoped that FreeBSD 6 would have solved > this problem after this thread on freebsd-stable : > > http://lists.freebsd.org/mailman/htdig/freebsd-stable/2005-June/016154.html > > > I have just tested with FreeBSD 6-RC1 and the problem remains here. > Moreover, I think it's also a security issue because a single user, with > a shell account on an FreeBSD SMP box, could trigger a panic with a > simple shell script like that one (posted by Marc Olzheim in PR 83375), > it's annoying particularly in a multi-user environment : > > #!/bin/sh > > count=0 > while true > do > screen -d -m -c "${PWD}/.screenrc.crashpts" & > count=$(($count+1)) > if [ $(($count%100)) = 0 ] > then > killall screen > sleep 2 > killall -9 screen > fi > done > > -- > Philippe PEGON > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" i'm currently running this script on freebsd 6.0RC1 with SMP kernel and I got page fault while in kernel mode... after running this script for 5-10 minutes... i'll test it on a releng_6_0 from today. regards, Dennis From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 15:36:35 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA69016A41F for ; Wed, 2 Nov 2005 15:36:35 +0000 (GMT) (envelope-from sven@dmv.com) Received: from smtp-gw-cl-c.dmv.com (smtp-gw-cl-c.dmv.com [216.240.97.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E74C43D46 for ; Wed, 2 Nov 2005 15:36:34 +0000 (GMT) (envelope-from sven@dmv.com) Received: from mail-gw-cl-b.dmv.com (mail-gw-cl-b.dmv.com [216.240.97.39]) by smtp-gw-cl-c.dmv.com (8.12.10/8.12.10) with ESMTP id jA2FaWQb049286 for ; Wed, 2 Nov 2005 10:36:32 -0500 (EST) (envelope-from sven@dmv.com) Received: from lanshark.dmv.com (lanshark.dmv.com [216.240.97.46]) by mail-gw-cl-b.dmv.com (8.12.9/8.12.9) with ESMTP id jA2FaWGC072093 for ; Wed, 2 Nov 2005 10:36:32 -0500 (EST) (envelope-from sven@dmv.com) From: Sven Willenberger To: current@freebsd.org Content-Type: text/plain Date: Wed, 02 Nov 2005 10:36:33 -0500 Message-Id: <1130945793.7893.27.camel@lanshark.dmv.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.39 X-Scanned-By: MIMEDefang 2.48 on 216.240.97.39 Cc: Subject: Tracking down em problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 15:36:36 -0000 FreeBSD6.0-RC1 (Wed Oct 26 13:31:21 EDT 2005) I seem to have an issue with losing connections to an em interface during process of heavy IO load. There are several variables here so I am hoping for some guidelines to help troubleshoot this. I have a postgresql server (8.0.4) set up on an i386 system. The data directory is on its own partition (which is actually a gstripe/gmirror setup -- see the footnote after my problem description). I have enabled a replication system from another server. When I started relication there was a large amount of data that had to be fed to this server via the em0 interface. During this process, while ssh'ed to the box, my connection would just hang for a few moments, then it would recover. However, if I cd to the data directory (stripe/mirror) and start ls -alrt several times, the connection actually gets broken; not only my ssh connection but the replication connection from the master server is broken. I have tried to set debug.mpsafenet=0 in /boot/loader.conf to no avail -- the same issue happens. Preemption is enabled in the kernel, as is sched_4bsd. I don't really know how to proceed at this point to try and troubleshoot this issue: as it stands now, it is most definitely a show stopper for the purposes of this server. Thanks, Sven *footnote: here is the gstripe/gmirror config: a) the mirrors: Geom name: pg1 State: COMPLETE Components: 2 Balance: split Slice: 8192 Flags: NONE GenID: 0 SyncID: 1 ID: 1606567834 Providers: 1. Name: mirror/pg1 Mediasize: 36703949312 (34G) Sectorsize: 512 Mode: r1w1e2 Consumers: 1. Name: da1 Mediasize: 36703949824 (34G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Priority: 0 Flags: DIRTY GenID: 0 SyncID: 1 ID: 2976581887 2. Name: da2 Mediasize: 36703949824 (34G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Priority: 1 Flags: DIRTY GenID: 0 SyncID: 1 ID: 3738898587 Geom name: pg2 State: COMPLETE Components: 2 Balance: split Slice: 8192 Flags: NONE GenID: 0 SyncID: 1 ID: 2419201320 Providers: 1. Name: mirror/pg2 Mediasize: 36703949312 (34G) Sectorsize: 512 Mode: r1w1e2 Consumers: 1. Name: da3 Mediasize: 36703949824 (34G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Priority: 0 Flags: DIRTY GenID: 0 SyncID: 1 ID: 4053765902 2. Name: da4 Mediasize: 36703949824 (34G) Sectorsize: 512 Mode: r1w1e1 State: ACTIVE Priority: 1 Flags: DIRTY GenID: 0 SyncID: 1 ID: 2784554060 b) the stripes (using the mirrors): Geom name: pgdata State: UP Status: Total=2, Online=2 Type: AUTOMATIC Stripesize: 65536 ID: 2329725949 Providers: 1. Name: stripe/pgdata Mediasize: 73407791104 (68G) Sectorsize: 512 Mode: r1w1e1 Consumers: 1. Name: mirror/pg1 Mediasize: 36703949312 (34G) Sectorsize: 512 Mode: r1w1e2 Number: 0 2. Name: mirror/pg2 Mediasize: 36703949312 (34G) Sectorsize: 512 Mode: r1w1e2 Number: 1 This is then mounted as: /dev/stripe/pgdata /usr/local/pgsql ufs rw,noatime 2 2 From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 15:37:39 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1898B16A41F; Wed, 2 Nov 2005 15:37:39 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 540DF43D46; Wed, 2 Nov 2005 15:37:38 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy-128.york.ac.uk [144.32.128.160]) by mail-gw0.york.ac.uk (8.12.10/8.12.10) with ESMTP id jA2FbU6a020334; Wed, 2 Nov 2005 15:37:31 GMT Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.4/8.13.4) with ESMTP id jA2FbUDu052270; Wed, 2 Nov 2005 15:37:30 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.4/8.13.4/Submit) id jA2FbUJT052269; Wed, 2 Nov 2005 15:37:30 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: ticso@cicely.de In-Reply-To: <20051102152322.GF93549@cicely12.cicely.de> References: <1130943516.51544.34.camel@buffy.york.ac.uk> <20051102152322.GF93549@cicely12.cicely.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Wed, 02 Nov 2005 15:37:29 +0000 Message-Id: <1130945849.51544.42.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Cc: freebsd-current@freebsd.org, rwatson@freebsd.org Subject: Re: Poor NFS server performance in 6.0 with SMP and mpsafenet=1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 15:37:39 -0000 On Wed, 2005-11-02 at 16:23 +0100, Bernd Walter wrote: > On Wed, Nov 02, 2005 at 02:58:36PM +0000, Gavin Atkinson wrote: > > I'm seeing incredibly poor performance when serving files from an SMP > > FreeBSD 6.0RC1 server to a Solaris 10 client. I've done some > > experimenting and have discovered that either removing SMP from the > > kernel, or setting debug.mpsafenet=0 in loader.conf massively improves > > the speed. Switching preemption off seems to also help. > > > > No SMP, mpsafenet=1 59.4 > > No SMP, mpsafenet=0 49.4 > > No SMP, mpsafenet=1, no PREEMPTION 53.1 > > No SMP, mpsafenet=0, no PREEMPTION 51.9 > > SMP, mpsafenet=1 351.7 > > SMP, mpsafenet=0 74.5 > > SMP, mpsafenet=1, no PREEMPTION 264.9 > > SMP, mpsafenet=0, no PREEMPTION 53.7 > > Which scheduler? BSD. As I say, I'm running 6.0-RC1 with the standard GENERIC kernel, apart from the options I have listed as being changed above. Polling is therefore also not enabled. When I get home, I'll have a play with both ULE and POLLING to see what difference they make, however ideally I'd like to not use polling in production if possible. Gavin From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 15:45:23 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 779A016A41F for ; Wed, 2 Nov 2005 15:45:23 +0000 (GMT) (envelope-from corwin@pleiades.aeternal.net) Received: from pleiades.aeternal.net (pleiades.in.markiza.sk [62.168.76.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id C438943D46 for ; Wed, 2 Nov 2005 15:45:22 +0000 (GMT) (envelope-from corwin@pleiades.aeternal.net) Received: by pleiades.aeternal.net (Postfix, from userid 1001) id F1FAF11444; Wed, 2 Nov 2005 16:45:52 +0100 (CET) Date: Wed, 2 Nov 2005 16:45:52 +0100 From: Martin Hudec To: freebsd-current@freebsd.org Message-ID: <20051102154552.GE32554@pleiades.aeternal.net> References: <1130943516.51544.34.camel@buffy.york.ac.uk> <20051102152322.GF93549@cicely12.cicely.de> <1130945849.51544.42.camel@buffy.york.ac.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZInfyf7laFu/Kiw7" Content-Disposition: inline In-Reply-To: <1130945849.51544.42.camel@buffy.york.ac.uk> X-Copyright: (C) 2005 Martin Hudec X-Operating-System: FreeBSD pleiades.aeternal.net 7.0-CURRENT i386 X-PGP-Key: https://aeternal.net/corwin_aeternal.asc User-Agent: mutt-ng/devel-r535 (FreeBSD) Subject: Re: Poor NFS server performance in 6.0 with SMP and mpsafenet=1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Martin Hudec List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 15:45:23 -0000 --ZInfyf7laFu/Kiw7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, On Wed, Nov 02, 2005 at 03:37:29PM +0000 or thereabouts, Gavin Atkinson wro= te: > When I get home, I'll have a play with both ULE and POLLING to see what > difference they make, however ideally I'd like to not use polling in > production if possible. What's wrong with polling on production in your current environment if I may ask? --=20 Martin Hudec * 421 907 303 393 * corwin@aeternal.net * https://aeternal.net "Nothing travels faster than the speed of light with the possible=20 exception of bad news, which obeys its own special laws." Douglas Adams, "The Hitchhiker's Guide to the Galaxy" --ZInfyf7laFu/Kiw7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDaN8wZYEZIv+rgggRAvHVAJ49RThWNAuC1RYU15HKqmyYqE/a+gCff2oC ipWpAGkprEj+jqPwpvFlfeA= =gif6 -----END PGP SIGNATURE----- --ZInfyf7laFu/Kiw7-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 15:47:58 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12FB116A41F for ; Wed, 2 Nov 2005 15:47:58 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68E9C43D49 for ; Wed, 2 Nov 2005 15:47:57 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id jA2Flkxb098908 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Nov 2005 18:47:46 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id jA2Fljjd098907; Wed, 2 Nov 2005 18:47:45 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 2 Nov 2005 18:47:45 +0300 From: Gleb Smirnoff To: Sven Willenberger Message-ID: <20051102154745.GJ91530@cell.sick.ru> References: <1130945793.7893.27.camel@lanshark.dmv.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <1130945793.7893.27.camel@lanshark.dmv.com> User-Agent: Mutt/1.5.6i Cc: current@FreeBSD.org Subject: Re: Tracking down em problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 15:47:58 -0000 On Wed, Nov 02, 2005 at 10:36:33AM -0500, Sven Willenberger wrote: S> I seem to have an issue with losing connections to an em interface S> during process of heavy IO load. There are several variables here so I S> am hoping for some guidelines to help troubleshoot this. Please update to latest RELENG_6, RELENG_6_0 or RELENG_6_0_0_RELEASE. Your problem should have been fixed already. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 15:51:39 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF1F416A41F for ; Wed, 2 Nov 2005 15:51:39 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 008DF43D73 for ; Wed, 2 Nov 2005 15:51:33 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id jA2FpQau047849; Wed, 2 Nov 2005 09:51:27 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <4368E07C.6050003@centtech.com> Date: Wed, 02 Nov 2005 09:51:24 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051021 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sven Willenberger References: <1130945793.7893.27.camel@lanshark.dmv.com> In-Reply-To: <1130945793.7893.27.camel@lanshark.dmv.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1158/Wed Nov 2 07:29:56 2005 on mh1.centtech.com X-Virus-Status: Clean Cc: current@freebsd.org Subject: Re: Tracking down em problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 15:51:39 -0000 Sven Willenberger wrote: > FreeBSD6.0-RC1 (Wed Oct 26 13:31:21 EDT 2005) > > I seem to have an issue with losing connections to an em interface > during process of heavy IO load. There are several variables here so I > am hoping for some guidelines to help troubleshoot this. > > I have a postgresql server (8.0.4) set up on an i386 system. The data > directory is on its own partition (which is actually a gstripe/gmirror > setup -- see the footnote after my problem description). > > I have enabled a replication system from another server. When I started > relication there was a large amount of data that had to be fed to this > server via the em0 interface. During this process, while ssh'ed to the > box, my connection would just hang for a few moments, then it would > recover. However, if I cd to the data directory (stripe/mirror) and > start ls -alrt several times, the connection actually gets broken; not > only my ssh connection but the replication connection from the master > server is broken. > > I have tried to set debug.mpsafenet=0 in /boot/loader.conf to no avail > -- the same issue happens. Preemption is enabled in the kernel, as is > sched_4bsd. I don't really know how to proceed at this point to try and > troubleshoot this issue: as it stands now, it is most definitely a show > stopper for the purposes of this server. I've seen something similar on recent 5.4-STABLE, also using emX devices. I have 3 Dell 1850's showing the same exact issue, and a few 1850's that are not. The ones that are not, are 5.4-RELEASE, and the ones that do, are running 5.4-STABLE. In dmesg, I see a warning like this: Nov 1 19:56:06 hal kernel: em1: Link is up 1000 Mbps Full Duplex I don't see a 'link is down', just 'Link is up'. One machine I've seen this on repeatedly is from about August 16th. I'm using SCHED_4BSD, SMP, and most of the other GENERIC settings. If anyone wants more details, let me know. I have a spare Dell 1850 I can play with. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 15:58:23 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5107D16A42B; Wed, 2 Nov 2005 15:58:23 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E6C743DB8; Wed, 2 Nov 2005 15:58:00 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id jA2FvxgG031681; Wed, 2 Nov 2005 09:57:59 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <4368E205.1000304@centtech.com> Date: Wed, 02 Nov 2005 09:57:57 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051021 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gleb Smirnoff References: <1130945793.7893.27.camel@lanshark.dmv.com> <20051102154745.GJ91530@cell.sick.ru> In-Reply-To: <20051102154745.GJ91530@cell.sick.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1158/Wed Nov 2 07:29:56 2005 on mh2.centtech.com X-Virus-Status: Clean Cc: current@freebsd.org Subject: Re: Tracking down em problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 15:58:23 -0000 Gleb Smirnoff wrote: > On Wed, Nov 02, 2005 at 10:36:33AM -0500, Sven Willenberger wrote: > S> I seem to have an issue with losing connections to an em interface > S> during process of heavy IO load. There are several variables here so I > S> am hoping for some guidelines to help troubleshoot this. > > Please update to latest RELENG_6, RELENG_6_0 or RELENG_6_0_0_RELEASE. > Your problem should have been fixed already. > Did those changes get MFC'ed to 5-STABLE too? Thanks.. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 15:58:23 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 735F916A433 for ; Wed, 2 Nov 2005 15:58:23 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 2247A43DBA for ; Wed, 2 Nov 2005 15:58:00 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 02 Nov 2005 15:57:58 -0000 Received: from h081217094006.dyn.cm.kabsi.at (EHLO h081217094006.dyn.cm.kabsi.at) [81.217.94.6] by mail.gmx.net (mp021) with SMTP; 02 Nov 2005 16:57:58 +0100 X-Authenticated: #16703784 From: Stefan Ehmann To: current@freebsd.org Content-Type: text/plain Date: Wed, 02 Nov 2005 16:57:53 +0100 Message-Id: <1130947073.1076.12.camel@taxman.pepperland> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: Subject: panic in devfs_populate_loop() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 15:58:25 -0000 After todays cvsup and buildworld/kernel I get a panic during boot. Kernel from October 29th works fine. Maybe related to the latest ACPI-CA import. Panic string and backtrace hand-transcribed. Fatal trap 12: page fault while in kernel mode devfs_populate_loop() devfs_populate() devfs_lookup() VOP_LOOKUP_APV() lookup() namei() kern_symlink() devfs_first() vfs_mountroot() start_init fork_exit() fork_trampoline() dmesg from kernel.old: 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 7.0-CURRENT #41: Sat Oct 29 12:46:27 CEST 2005 stefan@something.pepperland:/usr/obj/usr/src/sys/SOMETHING Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) M processor 1.60GHz (1598.65-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6d6 Stepping = 6 Features=0xafe9fbbf Features2=0x180 real memory = 502136832 (478 MB) avail memory = 481828864 (459 MB) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 10 on acpi0 pci_link1: irq 11 on acpi0 pci_link2: irq 5 on acpi0 pci_link3: irq 7 on acpi0 pci_link4: irq 4 on acpi0 pci_link5: irq 11 on acpi0 pci_link6: irq 11 on acpi0 pci_link7: irq 3 on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 est0: on cpu0 p4tcc0: on cpu0 acpi_lid0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.1 (no driver attached) pci0: at device 0.3 (no driver attached) agp0: port 0x1800-0x1807 mem 0xe8000000-0xefffffff,0xe0000000-0xe007ffff irq 10 at device 2.0 on pci0 agp0: detected 32636k stolen memory agp0: aperture size is 128M pci0: at device 2.1 (no driver attached) uhci0: port 0x1820-0x183f irq 10 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 0x1840-0x185f irq 7 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 0x1860-0x187f irq 5 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 pci0: at device 29.7 (no driver attached) pcib1: at device 30.0 on pci0 pci2: on pcib1 fwohci0: port 0x3400-0x347f mem 0xe0201000-0xe02017ff irq 4 at device 0.0 on pci2 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:02:3f:4c:65:40:8a:64 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwohci0: Initiate bus reset fwohci0: node_id=0xc000ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) rl0: port 0x3000-0x30ff mem 0xe0201800-0xe02018ff irq 11 at device 1.0 on pci2 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:0f:b0:3c:bd:b9 iwi0: mem 0xe0200000-0xe0200fff irq 10 at device 2.0 on pci2 iwi0: Ethernet address: 00:0e:35:ac:9b:f0 cbb0: at device 4.0 on pci2 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pci2: at device 4.1 (no driver attached) pci2: at device 4.2 (no driver attached) pci2: at device 4.3 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1810-0x181f at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 31.3 (no driver attached) pcm0: port 0x1c00-0x1cff,0x18c0-0x18ff mem 0xe0100c00-0xe0100dff,0xe0100800-0xe01008ff irq 11 at device 31.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: pci0: at device 31.6 (no driver attached) acpi_acad0: on acpi0 battery0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model GlidePoint, device ID 0 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xccfff,0xcd000-0xcdfff,0xd6000-0xd67ff,0xe0000-0xe3fff pnpid ORM0000 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 Timecounter "TSC" frequency 1598648877 Hz quality 800 Timecounters tick every 1.000 msec ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to accept, logging limited to 100 packets/entry by default ad0: 76319MB at ata0-master UDMA100 acd0: DVDR at ata1-master UDMA33 Trying to mount root from ufs:/dev/ad0s1a cd0 at ata1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present iwi0: Please load firmware rl0: link state changed to DOWN iwi0: link state changed to UP From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 15:20:13 2005 Return-Path: X-Original-To: FreeBSD-current@freebsd.org Delivered-To: FreeBSD-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00AA916A41F for ; Wed, 2 Nov 2005 15:20:12 +0000 (GMT) (envelope-from samspeedu@mail.ru) Received: from mx3.mail.ru (mx3.mail.ru [194.67.23.149]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3316843D64 for ; Wed, 2 Nov 2005 15:20:11 +0000 (GMT) (envelope-from samspeedu@mail.ru) Received: from [80.82.44.194] (port=39126 helo=192.168.168.7) by mx3.mail.ru with esmtp id 1EXKPK-000C5K-00; Wed, 02 Nov 2005 18:20:10 +0300 Date: Wed, 2 Nov 2005 18:18:42 +0300 From: Andrey Smagin X-Mailer: The Bat! (v1.62r) Organization: DiP X-Priority: 3 (Normal) Message-ID: <1849285973.20051102181842@mail.ru> To: Steve Kargl In-Reply-To: <20051102150805.GA75891@troutmask.apl.washington.edu> References: <002301c5df5f$fa16e9e0$652a15ac@smiley> <3410224838.20051102114823@mail.ru> <20051102150805.GA75891@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 02 Nov 2005 16:00:03 +0000 Cc: FreeBSD-current@freebsd.org Subject: Re[2]: From CURRENT-i386 -> CURRENT amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: SAMU List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 15:20:13 -0000 How can I avoid using ISO images for this? Build and install from sources ? It's possible ? -- Best regards, Andrey mailto:samspeedu@mail.ru From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 16:00:33 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 026A816A42C for ; Wed, 2 Nov 2005 16:00:32 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 677FC43D8B for ; Wed, 2 Nov 2005 16:00:25 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id jA2G0F7q099154 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 2 Nov 2005 19:00:15 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id jA2G0FLa099153; Wed, 2 Nov 2005 19:00:15 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Wed, 2 Nov 2005 19:00:15 +0300 From: Gleb Smirnoff To: Eric Anderson Message-ID: <20051102160015.GK91530@cell.sick.ru> References: <1130945793.7893.27.camel@lanshark.dmv.com> <20051102154745.GJ91530@cell.sick.ru> <4368E205.1000304@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <4368E205.1000304@centtech.com> User-Agent: Mutt/1.5.6i Cc: current@FreeBSD.org Subject: Re: Tracking down em problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 16:00:33 -0000 On Wed, Nov 02, 2005 at 09:57:57AM -0600, Eric Anderson wrote: E> >On Wed, Nov 02, 2005 at 10:36:33AM -0500, Sven Willenberger wrote: E> >S> I seem to have an issue with losing connections to an em interface E> >S> during process of heavy IO load. There are several variables here so I E> >S> am hoping for some guidelines to help troubleshoot this. E> > E> >Please update to latest RELENG_6, RELENG_6_0 or RELENG_6_0_0_RELEASE. E> >Your problem should have been fixed already. E> E> Did those changes get MFC'ed to 5-STABLE too? Not yet. In next two weeks probably. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 16:01:32 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F180F16A41F; Wed, 2 Nov 2005 16:01:31 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5F0D43D92; Wed, 2 Nov 2005 16:01:16 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id jA2G1Ggw031779; Wed, 2 Nov 2005 10:01:16 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <4368E2CA.2010507@centtech.com> Date: Wed, 02 Nov 2005 10:01:14 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051021 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gleb Smirnoff References: <1130945793.7893.27.camel@lanshark.dmv.com> <20051102154745.GJ91530@cell.sick.ru> <4368E205.1000304@centtech.com> <20051102160015.GK91530@cell.sick.ru> In-Reply-To: <20051102160015.GK91530@cell.sick.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1158/Wed Nov 2 07:29:56 2005 on mh2.centtech.com X-Virus-Status: Clean Cc: current@FreeBSD.org Subject: Re: Tracking down em problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 16:01:32 -0000 Gleb Smirnoff wrote: > On Wed, Nov 02, 2005 at 09:57:57AM -0600, Eric Anderson wrote: > E> >On Wed, Nov 02, 2005 at 10:36:33AM -0500, Sven Willenberger wrote: > E> >S> I seem to have an issue with losing connections to an em interface > E> >S> during process of heavy IO load. There are several variables here so I > E> >S> am hoping for some guidelines to help troubleshoot this. > E> > > E> >Please update to latest RELENG_6, RELENG_6_0 or RELENG_6_0_0_RELEASE. > E> >Your problem should have been fixed already. > E> > E> Did those changes get MFC'ed to 5-STABLE too? > > Not yet. In next two weeks probably. Thanks! I'll watch for it.. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 16:46:59 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7E0F16A41F for ; Wed, 2 Nov 2005 16:46:59 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E93D43D46 for ; Wed, 2 Nov 2005 16:46:59 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 4E45C46B4F; Wed, 2 Nov 2005 11:46:54 -0500 (EST) Date: Wed, 2 Nov 2005 16:46:54 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Gavin Atkinson In-Reply-To: <1130945849.51544.42.camel@buffy.york.ac.uk> Message-ID: <20051102164157.A18382@fledge.watson.org> References: <1130943516.51544.34.camel@buffy.york.ac.uk> <20051102152322.GF93549@cicely12.cicely.de> <1130945849.51544.42.camel@buffy.york.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org, ticso@cicely.de Subject: Re: Poor NFS server performance in 6.0 with SMP and mpsafenet=1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 16:46:59 -0000 On Wed, 2 Nov 2005, Gavin Atkinson wrote: > On Wed, 2005-11-02 at 16:23 +0100, Bernd Walter wrote: >> On Wed, Nov 02, 2005 at 02:58:36PM +0000, Gavin Atkinson wrote: >>> I'm seeing incredibly poor performance when serving files from an SMP >>> FreeBSD 6.0RC1 server to a Solaris 10 client. I've done some >>> experimenting and have discovered that either removing SMP from the >>> kernel, or setting debug.mpsafenet=0 in loader.conf massively improves >>> the speed. Switching preemption off seems to also help. >>> >>> No SMP, mpsafenet=1 59.4 >>> No SMP, mpsafenet=0 49.4 >>> No SMP, mpsafenet=1, no PREEMPTION 53.1 >>> No SMP, mpsafenet=0, no PREEMPTION 51.9 >>> SMP, mpsafenet=1 351.7 >>> SMP, mpsafenet=0 74.5 >>> SMP, mpsafenet=1, no PREEMPTION 264.9 >>> SMP, mpsafenet=0, no PREEMPTION 53.7 >> >> Which scheduler? > > BSD. As I say, I'm running 6.0-RC1 with the standard GENERIC kernel, > apart from the options I have listed as being changed above. Polling is > therefore also not enabled. > > When I get home, I'll have a play with both ULE and POLLING to see what > difference they make, however ideally I'd like to not use polling in > production if possible. This does sound like a scheduling problem. I realize it's time-consuming, but would it be possible to have you run each of the above test cases twice more (or maybe even once) to confirm that in each case, the result is reproduceable? I've recently been looking at a scheduling problem relating to PREEMPTION and the netisr for loopback traffic, and is basically a result of poorly timed context switching ending up being a worst cast scenario. I suspect something similar is likely here. Have you tried varying the number of nfsd worker threads on the server to see how that changes matters? Robert N M Watson From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 17:08:55 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A82616A41F for ; Wed, 2 Nov 2005 17:08:55 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from indor.net.tomline.ru (indor.net.tomline.ru [213.183.100.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB20A43D49 for ; Wed, 2 Nov 2005 17:08:53 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from SNEZHKO by indorsoft.ru (MDaemon.PRO.v7.2.2.R) with ESMTP id md50000027338.msg for ; Wed, 02 Nov 2005 23:08:48 +0600 X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 87853, updated: 1.11.2005] To: Max Laier References: <20051027022313.R675@kushnir1.kiev.ua> <200510311231.33322.jhb@freebsd.org> <20051102014239.O654@kushnir1.kiev.ua> <200511021035.22990.max@love2party.net> From: Victor Snezhko Date: Wed, 02 Nov 2005 23:08:45 +0600 In-Reply-To: <200511021035.22990.max@love2party.net> (Max Laier's message of "Wed, 2 Nov 2005 10:35:05 +0100") Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Processed: indor.net.tomline.ru, Wed, 02 Nov 2005 23:08:48 +0600 (not processed: spam filter disabled) X-Return-Path: snezhko@indorsoft.ru X-MDaemon-Deliver-To: freebsd-current@freebsd.org X-VVS-Spam: false Cc: freebsd-current@freebsd.org Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 17:08:55 -0000 Max Laier writes: >> > suz 2005-10-21 16:23:01 UTC >> > >> > FreeBSD src repository >> > >> > Modified files: >> > sys/netinet icmp6.h >> > sys/netinet6 icmp6.c in6.c in6.h in6_ifattach.c >> > in6_ifattach.h in6_var.h ip6_output.c >> > mld6.c mld6_var.h nd6.c nd6.h nd6_nbr.c >> > nd6_rtr.c >> > share/doc/IPv6 IMPLEMENTATION >> >> This was when panics begun. And they're still here. > > That brings me back to ln_timer_ch as the culprit. Could you please build > with this patch and get me the console output shortly before the panic? I built with this patch and have two identical kernel output strings before the panic (and one more during bootup): For 0xc188ee80 1 ticks For 0xc188ee80 1 ticks Sorry, can't analyze a crashdump yet to show what 0xc188ee80 is. When I synchronize my world with the new kernel I probably will be able to. -- WBR, Victor V. Snezhko EMail: snezhko@indorsoft.ru From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 17:36:54 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 285F016A41F for ; Wed, 2 Nov 2005 17:36:53 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from indor.net.tomline.ru (indor.net.tomline.ru [213.183.100.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BF4843D46 for ; Wed, 2 Nov 2005 17:36:52 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from SNEZHKO by indorsoft.ru (MDaemon.PRO.v7.2.2.R) with ESMTP id md50000027343.msg for ; Wed, 02 Nov 2005 23:36:45 +0600 X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 87853, updated: 1.11.2005] To: Max Laier References: <20051027022313.R675@kushnir1.kiev.ua> <200510311231.33322.jhb@freebsd.org> <20051102014239.O654@kushnir1.kiev.ua> <200511021035.22990.max@love2party.net> From: Victor Snezhko Date: Wed, 02 Nov 2005 23:36:44 +0600 In-Reply-To: (Victor Snezhko's message of "Wed, 02 Nov 2005 23:08:45 +0600") Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Processed: indor.net.tomline.ru, Wed, 02 Nov 2005 23:36:45 +0600 (not processed: spam filter disabled) X-Return-Path: snezhko@indorsoft.ru X-MDaemon-Deliver-To: freebsd-current@freebsd.org X-VVS-Spam: false Cc: freebsd-current@freebsd.org Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 17:36:54 -0000 Victor Snezhko writes: > For 0xc188ee80 1 ticks > For 0xc188ee80 1 ticks Aargh... Not 1 but -1 in both cases. -- WBR, Victor V. Snezhko EMail: snezhko@indorsoft.ru From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 18:07:37 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1460916A41F for ; Wed, 2 Nov 2005 18:07:37 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64B3843D45 for ; Wed, 2 Nov 2005 18:07:36 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy-128.york.ac.uk [144.32.128.160]) by mail-gw0.york.ac.uk (8.12.10/8.12.10) with ESMTP id jA2I7N6a012945; Wed, 2 Nov 2005 18:07:23 GMT Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.4/8.13.4) with ESMTP id jA2I7MrU052751; Wed, 2 Nov 2005 18:07:22 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.4/8.13.4/Submit) id jA2I7MrT052750; Wed, 2 Nov 2005 18:07:22 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: Martin Hudec In-Reply-To: <20051102154552.GE32554@pleiades.aeternal.net> References: <1130943516.51544.34.camel@buffy.york.ac.uk> <20051102152322.GF93549@cicely12.cicely.de> <1130945849.51544.42.camel@buffy.york.ac.uk> <20051102154552.GE32554@pleiades.aeternal.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Wed, 02 Nov 2005 18:07:21 +0000 Message-Id: <1130954841.51544.57.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Cc: freebsd-current@freebsd.org Subject: Re: Poor NFS server performance in 6.0 with SMP and mpsafenet=1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 18:07:37 -0000 On Wed, 2005-11-02 at 16:45 +0100, Martin Hudec wrote: > Hello, > > > On Wed, Nov 02, 2005 at 03:37:29PM +0000 or thereabouts, Gavin Atkinson wrote: > > When I get home, I'll have a play with both ULE and POLLING to see what > > difference they make, however ideally I'd like to not use polling in > > production if possible. > > What's wrong with polling on production in your current environment if > I may ask? Certainly. For heavily loaded machines, polling seems to significantly improve performance, but in my experience on lightly loaded machines it seems to increase latency on response to packets. For the particular workloads it will be used for, (serving web content and databases), the latency can be noticeable. IMHO, polling is great for lower-spec boxes or highly loaded machines, but can hinder performance when the machine is lightly loaded. I have a few machines which run with polling on, and for those usage patterns it really helps. I just don't believe this is one of those cases. Gavin From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 19:17:03 2005 Return-Path: X-Original-To: FreeBSD-current@FreeBSD.ORG Delivered-To: FreeBSD-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97DAA16A41F for ; Wed, 2 Nov 2005 19:17:03 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C26143D46 for ; Wed, 2 Nov 2005 19:17:02 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jA2JE5Px038157; Wed, 2 Nov 2005 12:14:06 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 02 Nov 2005 12:14:05 -0700 (MST) Message-Id: <20051102.121405.41670789.imp@bsdimp.com> To: sgk@troutmask.apl.washington.edu From: Warner Losh In-Reply-To: <20051102150805.GA75891@troutmask.apl.washington.edu> References: <002301c5df5f$fa16e9e0$652a15ac@smiley> <3410224838.20051102114823@mail.ru> <20051102150805.GA75891@troutmask.apl.washington.edu> 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 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 02 Nov 2005 12:14:06 -0700 (MST) Cc: FreeBSD-current@FreeBSD.ORG, samspeedu@mail.ru Subject: Re: From CURRENT-i386 -> CURRENT amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 19:17:03 -0000 From: Steve Kargl Subject: Re: From CURRENT-i386 -> CURRENT amd64 Date: Wed, 2 Nov 2005 07:08:05 -0800 > On Wed, Nov 02, 2005 at 11:48:23AM +0300, Andrey Smagin wrote: > > > > How I can safe switch platform ? > > > > Assuming you have an athlon64 or opteron system > that is currently running i386 FreeBSD. You > need to backup user data, get a list of install > ports, and the amd64 ISO images. Now, install > amd64 over the top of i386, restore user data, > and install the ports. Alternatively, you can do an installworld into a DESTDIR and then boot off of that and then back-copy. But that can be a pita if done incorrectly... Warner From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 19:39:30 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75F0816A41F for ; Wed, 2 Nov 2005 19:39:30 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail5.speedfactory.net [66.23.216.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CE9343D4C for ; Wed, 2 Nov 2005 19:39:23 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 1254181 for multiple; Wed, 02 Nov 2005 14:37:22 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jA2JdIAu059028; Wed, 2 Nov 2005 14:39:18 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 2 Nov 2005 14:32:27 -0500 User-Agent: KMail/1.8.2 References: <20051027022313.R675@kushnir1.kiev.ua> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511021432.29119.jhb@freebsd.org> X-Spam-Status: No, score=-2.2 required=4.2 tests=ALL_TRUSTED,URIBL_SBL autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=100 Cc: Max Laier , Victor Snezhko Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 19:39:30 -0000 On Wednesday 02 November 2005 12:36 pm, Victor Snezhko wrote: > Victor Snezhko writes: > > For 0xc188ee80 1 ticks > > For 0xc188ee80 1 ticks > > Aargh... Not 1 but -1 in both cases. -1 ticks would be bad. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 20:05:12 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBBAC16A41F for ; Wed, 2 Nov 2005 20:05:12 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id A815A43D46 for ; Wed, 2 Nov 2005 20:05:12 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 89F621A3C2D; Wed, 2 Nov 2005 12:05:12 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D3A69514A3; Wed, 2 Nov 2005 15:05:11 -0500 (EST) Date: Wed, 2 Nov 2005 15:05:11 -0500 From: Kris Kennaway To: Stefan Ehmann Message-ID: <20051102200511.GA86903@xor.obsecurity.org> References: <1130947073.1076.12.camel@taxman.pepperland> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+HP7ph2BbKc20aGI" Content-Disposition: inline In-Reply-To: <1130947073.1076.12.camel@taxman.pepperland> User-Agent: Mutt/1.4.2.1i Cc: current@freebsd.org Subject: Re: panic in devfs_populate_loop() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 20:05:13 -0000 --+HP7ph2BbKc20aGI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 02, 2005 at 04:57:53PM +0100, Stefan Ehmann wrote: > After todays cvsup and buildworld/kernel I get a panic during boot. >=20 > Kernel from October 29th works fine. Maybe related to the latest ACPI-CA > import. >=20 > Panic string and backtrace hand-transcribed. >=20 > Fatal trap 12: page fault while in kernel mode >=20 > devfs_populate_loop() > devfs_populate() > devfs_lookup() > VOP_LOOKUP_APV() > lookup() > namei() > kern_symlink() > devfs_first() > vfs_mountroot() > start_init > fork_exit() > fork_trampoline() You'll need to obtain further debugging information (i.e. crash dump) Kris --+HP7ph2BbKc20aGI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDaRv3Wry0BWjoQKURAoTVAJ9qRsguXVWDRUbaQ8PP3Qp0WvJjnQCgwwV/ 9vwLfpQLRVVopoW0EtNbsR8= =9gJw -----END PGP SIGNATURE----- --+HP7ph2BbKc20aGI-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 20:55:20 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 858FB16A41F for ; Wed, 2 Nov 2005 20:55:20 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 811CE43D45 for ; Wed, 2 Nov 2005 20:55:16 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 02 Nov 2005 20:55:12 -0000 Received: from h081217094006.dyn.cm.kabsi.at (EHLO h081217094006.dyn.cm.kabsi.at) [81.217.94.6] by mail.gmx.net (mp015) with SMTP; 02 Nov 2005 21:55:12 +0100 X-Authenticated: #16703784 From: Stefan Ehmann To: Kris Kennaway In-Reply-To: <20051102200511.GA86903@xor.obsecurity.org> References: <1130947073.1076.12.camel@taxman.pepperland> <20051102200511.GA86903@xor.obsecurity.org> Content-Type: text/plain Date: Wed, 02 Nov 2005 21:55:13 +0100 Message-Id: <1130964913.1076.19.camel@taxman.pepperland> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: current@freebsd.org Subject: Re: panic in devfs_populate_loop() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 20:55:20 -0000 On Wed, 2005-11-02 at 15:05 -0500, Kris Kennaway wrote: > On Wed, Nov 02, 2005 at 04:57:53PM +0100, Stefan Ehmann wrote: > > After todays cvsup and buildworld/kernel I get a panic during boot. > > > > Kernel from October 29th works fine. Maybe related to the latest ACPI-CA > > import. > > > > Panic string and backtrace hand-transcribed. > > > > Fatal trap 12: page fault while in kernel mode > > > > devfs_populate_loop() > > devfs_populate() > > devfs_lookup() > > VOP_LOOKUP_APV() > > lookup() > > namei() > > kern_symlink() > > devfs_first() > > vfs_mountroot() > > start_init > > fork_exit() > > fork_trampoline() > > You'll need to obtain further debugging information (i.e. crash dump) I cannot get a dump because the panic happens before dumpon is executed. The handbook says this about obtaining a crash dump: "Alternatively, the dump device can be hard-coded via the dump clause in the config(5) line of a kernel configuration file. This approach is deprecated and should be used only if a kernel is crashing before dumpon(8) can be executed." Unfortunately I could not figure out how to do this. Google only found http://lists.freebsd.org/pipermail/freebsd-current/2005-April/049465.html but that's not very helpful. From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 22:20:53 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E0E616A41F; Wed, 2 Nov 2005 22:20:53 +0000 (GMT) (envelope-from vkushnir@i.kiev.ua) Received: from horse.iptelecom.net.ua (horse.iptelecom.net.ua [212.9.224.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26D3943D49; Wed, 2 Nov 2005 22:20:51 +0000 (GMT) (envelope-from vkushnir@i.kiev.ua) Received: from h127.243.159.dialup.iptcom.net ([213.159.243.127]:38395 "EHLO kushnir1.kiev.ua" ident: "SOCKFAULT1" whoson: "vkushnir") by horse.iptelecom.net.ua with ESMTP id S1219391AbVKBWUt (ORCPT + 2 others); Thu, 3 Nov 2005 00:20:49 +0200 Received: from kushnir1.kiev.ua (kushnir1.kiev.ua [10.0.0.1]) by kushnir1.kiev.ua (8.13.4/8.13.3) with ESMTP id jA2MKkl8005842; Thu, 3 Nov 2005 00:20:46 +0200 (EET) (envelope-from vkushnir@i.kiev.ua) Date: Thu, 3 Nov 2005 00:20:46 +0200 (EET) From: Vladimir Kushnir X-X-Sender: vkushnir@kushnir1.kiev.ua To: Max Laier In-Reply-To: <200511021035.22990.max@love2party.net> Message-ID: <20051103001509.C85422@kushnir1.kiev.ua> References: <20051027022313.R675@kushnir1.kiev.ua> <200510311231.33322.jhb@freebsd.org> <20051102014239.O654@kushnir1.kiev.ua> <200511021035.22990.max@love2party.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 22:20:53 -0000 On Wed, 2 Nov 2005, Max Laier wrote: > > That brings me back to ln_timer_ch as the culprit. Could you please build > with this patch and get me the console output shortly before the panic? > Here it is: right before panic it prints For 0xffffff0017531100 -1 ticks For 0xffffff0017531100 -1 ticks (with yesterday's GENERIC). Regards, Vladimir P.S. Oh, incidentally, this (yesterday's) GENERIC plus my usual modules (atapicam, snd_ich, {cd9660, ntfs}_iconv and ext2fs) falls at mid-boot with "memory modified after free" :-( Non of these modules by itself caused any problem. From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 23:15:38 2005 Return-Path: X-Original-To: FreeBSD-current@FreeBSD.ORG Delivered-To: FreeBSD-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A421A16A41F for ; Wed, 2 Nov 2005 23:15:38 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [65.170.254.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51A5743D45 for ; Wed, 2 Nov 2005 23:15:35 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mortis.over-yonder.net (adsl-12-34-209.jan.bellsouth.net [65.12.34.209]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id 393322A for ; Wed, 2 Nov 2005 17:15:35 -0600 (CST) Received: by mortis.over-yonder.net (Postfix, from userid 100) id 4385620FA3; Wed, 2 Nov 2005 17:15:33 -0600 (CST) Date: Wed, 2 Nov 2005 17:15:32 -0600 From: "Matthew D. Fuller" To: Warner Losh Message-ID: <20051102231532.GM1367@over-yonder.net> References: <002301c5df5f$fa16e9e0$652a15ac@smiley> <3410224838.20051102114823@mail.ru> <20051102150805.GA75891@troutmask.apl.washington.edu> <20051102.121405.41670789.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051102.121405.41670789.imp@bsdimp.com> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.9i-fullermd.2 Cc: FreeBSD-current@FreeBSD.ORG, samspeedu@mail.ru, sgk@troutmask.apl.washington.edu Subject: Re: From CURRENT-i386 -> CURRENT amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 23:15:38 -0000 On Wed, Nov 02, 2005 at 12:14:05PM -0700 I heard the voice of Warner Losh, and lo! it spake thus: > > Alternatively, you can do an installworld into a DESTDIR and then > boot off of that and then back-copy. But that can be a pita if done > incorrectly... I did this by "borrowing" a swap partition temporarily, newfs'ing it, and using that as the amd64 boot partition, then doing another installworld onto the real partitions. Of course, I think cvsup was the only port I had installed at the time... You could just do a portupgrade -af after booting back to the main drives to rebuild 'em all. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 23:59:15 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2BEB16A41F; Wed, 2 Nov 2005 23:59:15 +0000 (GMT) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A58243D45; Wed, 2 Nov 2005 23:59:15 +0000 (GMT) (envelope-from max@love2party.net) Received: from p54A3C2E4.dip.t-dialin.net [84.163.194.228] (helo=donor.laier.local) by mrelayeu.kundenserver.de (node=mrelayeu2) with ESMTP (Nemesis), id 0MKwtQ-1EXSVX2FdC-0002um; Thu, 03 Nov 2005 00:59:07 +0100 From: Max Laier To: Vladimir Kushnir Date: Thu, 3 Nov 2005 00:58:48 +0100 User-Agent: KMail/1.8.2 References: <20051027022313.R675@kushnir1.kiev.ua> <200511021035.22990.max@love2party.net> <20051103001509.C85422@kushnir1.kiev.ua> In-Reply-To: <20051103001509.C85422@kushnir1.kiev.ua> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1974503.iN126KmLRX"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200511030059.05946.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: freebsd-current@freebsd.org Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 23:59:16 -0000 --nextPart1974503.iN126KmLRX Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 02 November 2005 23:20, Vladimir Kushnir wrote: > On Wed, 2 Nov 2005, Max Laier wrote: > > That brings me back to ln_timer_ch as the culprit. Could you please > > build with this patch and get me the console output shortly before the > > panic? > > Here it is: right before panic it prints > > For 0xffffff0017531100 -1 ticks > For 0xffffff0017531100 -1 ticks This results in two consecutive callout_stop() calls, but shouldn't hurt as= =20 callout_stop is protected against that. Do you get a dump for this? Can you compare this pointer to the global=20 llinfo_nd6 and see if "c" from the softclock() frame is related (or maybe t= he=20 previous item in the list TAILQ). > (with yesterday's GENERIC). > P.S. > Oh, incidentally, this (yesterday's) GENERIC plus my usual > modules (atapicam, snd_ich, {cd9660, ntfs}_iconv and ext2fs) falls at > mid-boot with "memory modified after free" :-( Non of these modules by > itself caused any problem. Let's take this one thing at a time and provide more details for this probl= em=20 in a separate thread. Thanks. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1974503.iN126KmLRX Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDaVLJXyyEoT62BG0RAmxsAJ0ZWvuQxoR4EFJHwetQexd3xtMvuACfaZKm S1kw07MTdKJATJb2/DBo2es= =06bv -----END PGP SIGNATURE----- --nextPart1974503.iN126KmLRX-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 00:08:58 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61FB616A41F; Thu, 3 Nov 2005 00:08:58 +0000 (GMT) (envelope-from vkushnir@i.kiev.ua) Received: from horse.iptelecom.net.ua (horse.iptelecom.net.ua [212.9.224.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5651E43D46; Thu, 3 Nov 2005 00:08:56 +0000 (GMT) (envelope-from vkushnir@i.kiev.ua) Received: from h52.240.159.dialup.iptcom.net ([213.159.240.52]:36567 "EHLO kushnir1.kiev.ua" ident: "SOCKFAULT1" whoson: "vkushnir") by horse.iptelecom.net.ua with ESMTP id S1219345AbVKCAIy (ORCPT + 2 others); Thu, 3 Nov 2005 02:08:54 +0200 Received: from kushnir1.kiev.ua (kushnir1.kiev.ua [10.0.0.1]) by kushnir1.kiev.ua (8.13.4/8.13.3) with ESMTP id jA308qXQ020077; Thu, 3 Nov 2005 02:08:52 +0200 (EET) (envelope-from vkushnir@i.kiev.ua) Date: Thu, 3 Nov 2005 02:08:51 +0200 (EET) From: Vladimir Kushnir X-X-Sender: vkushnir@kushnir1.kiev.ua To: Max Laier In-Reply-To: <200511030059.05946.max@love2party.net> Message-ID: <20051103020404.J85422@kushnir1.kiev.ua> References: <20051027022313.R675@kushnir1.kiev.ua> <200511021035.22990.max@love2party.net> <20051103001509.C85422@kushnir1.kiev.ua> <200511030059.05946.max@love2party.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 00:08:58 -0000 On Thu, 3 Nov 2005, Max Laier wrote: >> >> Here it is: right before panic it prints >> >> For 0xffffff0017531100 -1 ticks >> For 0xffffff0017531100 -1 ticks > > This results in two consecutive callout_stop() calls, but shouldn't hurt as > callout_stop is protected against that. > > Do you get a dump for this? Can you compare this pointer to the global > llinfo_nd6 and see if "c" from the softclock() frame is related (or maybe the > previous item in the list TAILQ). > Sorry I'm not very goot at debugging. Would you please give me some instructions (lamer's level, preferably :-)). And anyway I'll be able to do it tomorrow only. TIA, Vladimir From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 00:47:02 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7CA0C16A41F for ; Thu, 3 Nov 2005 00:47:02 +0000 (GMT) (envelope-from haro@h4.dion.ne.jp) Received: from smtp1.dcns.ne.jp (smtp1.dcns.ne.jp [203.178.100.134]) by mx1.FreeBSD.org (Postfix) with SMTP id 05BF643D49 for ; Thu, 3 Nov 2005 00:47:00 +0000 (GMT) (envelope-from haro@h4.dion.ne.jp) Received: (qmail 6260 invoked by uid 503); 3 Nov 2005 09:46:59 +0900 Received: from unknown (HELO localhost) (211.10.184.118) by smtp1.dcns.ne.jp with SMTP; 3 Nov 2005 09:46:59 +0900 Date: Thu, 03 Nov 2005 09:46:43 +0900 (JST) Message-Id: <20051103.094643.74756456.haro@h4.dion.ne.jp> To: jkim@freebsd.org, robert.moore@intel.com From: Munehiro Matsuda In-Reply-To: <971FCB6690CD0E4898387DBF7552B90E0346CAFB@orsmsx403.amr.corp.intel.com> References: <971FCB6690CD0E4898387DBF7552B90E0346CAFB@orsmsx403.amr.corp.intel.com> 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-acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: Panic on boot with new ACPI-CA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 00:47:02 -0000 Hi, Thanks for looking. I've put the output dsdt/asl file from following command onto the URL below. command: # acpidump -t -d -o Dynabook_MX190R.dsdt > Dynabook_MX190R.asl URL: http://wwwb.dcns.ne.jp/~haro01/Dynabook_MX190R.dsdt http://wwwb.dcns.ne.jp/~haro01/Dynabook_MX190R.asl Thanks in advance, Haro From: "Moore, Robert" Date: Wed, 2 Nov 2005 09:51:23 -0800 ::If you will send me the acpidump for the machine, I will take a look at ::the problem. :: ::Thanks, ::Bob :: :: ::> -----Original Message----- ::> From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- ::> acpi@freebsd.org] On Behalf Of Munehiro Matsuda ::> Sent: Wednesday, November 02, 2005 7:08 AM ::> To: jkim@freebsd.org ::> Cc: freebsd-acpi@freebsd.org; freebsd-current@freebsd.org ::> Subject: Panic on boot with new ACPI-CA (Re: [HEADSUP] ACPI-CA ::20051021 ::> import) ::> ::> From: Jung-uk Kim ::> Date: Tue, 1 Nov 2005 17:49:44 -0500 ::> ::On Tuesday 01 November 2005 05:01 pm, Jung-uk Kim wrote: ::> ::> ACPI-CA 20051021 will be imported any minute now. I will let you ::> ::> know when completed. ::> :: ::> ::ACPI-CA 20051021 import is completed. ::> :: ::> ::Thanks! ::> :: ::> ::Jung-uk Kim ::> ::> Hi, ::> ::> After the import of new ACPI-CA code, I get system panic on boot, ::> where I used to get "can't fetch resources for \\_SB_.PCI0.FNC0.PRT_ - ::> AE_BAD_DATA" message. ::> ::> If you need more info, please let me know. ::> ::> Here's hand written down panic messages. ::> ::=----------------------------------------------------------------------- ::-- ::> - ::> npx0: [FAST] ::> npx0: on motherboard ::> npx0: INT 16 interface ::> acpi0: on motherboard ::> acpi0: Power Button (fixed) ::> pci_link0: irq 10 on acpi0 ::> pci_link1: irq 11 on acpi0 ::> pci_link2: irq 11 on acpi0 ::> pci_link3: irq 11 on acpi0 ::> pci_link4: irq 11 on acpi0 ::> pci_link5: irq 11 on acpi0 ::> pci_link6: irq 11 on acpi0 ::> pci_link7: irq 11 on acpi0 ::> Memory modified after free 0xc1ee1600(124) val=c @ 0xc1ee1600 ::> panic: Most recently used by acpica ::> ::> cpuid = 0 ::> KDB: enter: panic ::> [thread pid 0 tid 0] ::> Stopped at kbt_enter+0x2b: nop ::> db> bt ::> Tracing pid 0 tid 0 td 0xc0736780 ::> kdb_enter(c06cc93e) at kdb_enter+0x2b ::> panic(c06e42e7,c089c1a8,c06e42b8,c1ee1600,8c) at panic+0x127 ::> mtrash_ctor(c1ee1600,80,0,1) at mtrash_ctor+0x4d ::> uma_zalloc_arg(c104a1e0,0,1) at uma_zalloc_arg+0x10f ::> malloc(68,c089ef00,1,c0c20bb4,c087e562) at malloc+0xb2 ::> AcpiOsAllocate(68,0,c1ece1e0,4,c0c20be0) at AcpiOsAllocate+0x12 ::> AcpiUtCallocate(68,10,c089b337,157,c0c20bec) at AcpiUtCallocate+0x16 ::> AcpiGetObjectInfo(c1ece1e0,c0c20bf8,0,c1ece1e0,ffffffff) at ::> AcpiGetObjectInfo+0x5b ::> acpi_MatchHid(0,c089f740,6,c1ece1e0,0) at acpi_MatchHid+0x32 ::> acpi_probe_child(c1ece1e0,4,c1e9c800,0,0) at acpi_probe_child+0x94 ::> AcpiNsWalkNamespace(0,ffffffff,64,1,c0883c98) at ::AcpiNsWalkNamespace+0xa1 ::> AcpiWalkNamespace(0,ffffffff,64,c0883c98,c1e9c800) at ::> AcpiWalkNamespace+0x3b ::> acpi_attach(c1e9c800) at acpi_attach+0x4ff ::> device_attach(c1e9c800,0,c1e9c800,c1e9d300,0) at device_attach+0x58 ::> device_probe_and attach(c1e9c800) at device_probe_and_attach+0xe0 ::> bus_generic_attach(c1e9d300,c1e9d300,c1e9d300,c0c20d40,c0529340) at ::> bus_generic_attach+0x16 ::> nexus_attach(c1e9d300) at nexus_attach+0x13 ::> device_attach(c1e9d300,c0533914,c1e9d300,c0721bb0,c28000) at ::> device_attach+0x58 ::> device_probe_and_attach(c1e9d300) at device_probe_and_attach+0xe0 ::> root_bus_configure(c0c20d88,c04eb592,0,c1ec00,c1e000) at ::> root_bus_configure+0x16configure(0,c1ec00,c1e000,0,c04392f5) at ::> configure+0x9 ::> mi_startup() at mi_startup+0x96 ::> begin() at begine+0x2c ::> ::=----------------------------------------------------------------------- ::-- ::> - ::> ::> Following is boot message from the last kernel, just before the ::> import of new code. ::> ::=----------------------------------------------------------------------- ::-- ::> - ::> 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 7.0-CURRENT #135: Mon Oct 31 21:33:52 JST 2005 ::> ::haro@legacy.ttr.kubota.co.jp:/home/haro/tmp/sys-7/i386/compile/LEGACY ::> WARNING: WITNESS option enabled, expect reduced performance. ::> Timecounter "i8254" frequency 1193182 Hz quality 0 ::> CPU: Intel(R) Pentium(R) M processor 1.10GHz (1097.26-MHz 686-class ::CPU) ::> Origin = "GenuineIntel" Id = 0x6d6 Stepping = 6 ::> ::> ::Features=0xafe9f9bf AT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE> ::> Features2=0x180 ::> real memory = 787808256 (751 MB) ::> avail memory = 761475072 (726 MB) ::> npx0: [FAST] ::> npx0: on motherboard ::> npx0: INT 16 interface ::> acpi0: on motherboard ::> acpi0: Power Button (fixed) ::> pci_link0: irq 10 on acpi0 ::> pci_link1: irq 11 on acpi0 ::> pci_link2: irq 11 on acpi0 ::> pci_link3: irq 11 on acpi0 ::> pci_link4: irq 11 on acpi0 ::> pci_link5: irq 11 on acpi0 ::> pci_link6: irq 11 on acpi0 ::> pci_link7: irq 11 on acpi0 ::> can't fetch resources for \\_SB_.PCI0.FNC0.PRT_ - AE_BAD_DATA ::> Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 ::> acpi_timer0: <24-bit timer at 3.579545MHz> port 0xd808-0xd80b on acpi0 ::> cpu0: on acpi0 ::> est0: on cpu0 ::> p4tcc0: on cpu0 ::> pcib0: port 0xcf8-0xcff on acpi0 ::> pci0: on pcib0 ::> pci0: at device 0.1 (no driver attached) ::> pci0: at device 0.3 (no driver attached) ::> agp0: port ::0xeff8-0xefff ::> mem 0xd8000000-0xdfffffff,0xd0000000-0xd007ffff irq 10 at device 2.0 ::on ::> pci0 ::> agp0: detected 16252k stolen memory ::> agp0: aperture size is 128M ::> pci0: at device 2.1 (no driver attached) ::> uhci0: port 0xcfe0-0xcfff ::irq ::> 10 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 0xcf80-0xcf9f ::irq ::> 11 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 0xcf60-0xcf7f ::irq ::> 11 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 ::> ehci0: mem 0xcffffc00- ::> 0xcfffffff irq 11 at device 29.7 on pci0 ::> ehci0: [GIANT-LOCKED] ::> usb3: EHCI version 1.0 ::> usb3: companion controllers, 2 ports each: usb0 usb1 usb2 ::> usb3: on ehci0 ::> usb3: USB revision 2.0 ::> uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 ::> uhub3: 6 ports with 6 removable, self powered ::> pcib1: at device 30.0 on pci0 ::> pci1: on pcib1 ::> iwi0: mem 0xcfeff000-0xcfefffff irq 11 ::at ::> device 5.0 on pci1 ::> iwi0: Ethernet address: 00:0e:35:c2:a2:7b ::> fxp0: port 0xcf00-0xcf3f ::mem ::> 0xcfefe000-0xcfefefff irq 11 at device 8.0 on pci1 ::> miibus0: on fxp0 ::> inphy0: on miibus0 ::> inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ::> fxp0: Ethernet address: 00:0e:7b:eb:71:23 ::> cbb0: at device 11.0 on pci1 ::> cardbus0: on cbb0 ::> pccard0: <16-bit PCCard bus> on cbb0 ::> cbb1: at device 11.1 on pci1 ::> cardbus1: on cbb1 ::> pccard1: <16-bit PCCard bus> on cbb1 ::> fwohci0: <1394 Open Host Controller Interface> mem 0xcfefd800- ::> 0xcfefdfff,0xcfef8000-0xcfefbfff irq 11 at device 11.2 on pci1 ::> fwohci0: OHCI version 1.10 (ROM=1) ::> fwohci0: No. of Isochronous channels is 4. ::> fwohci0: EUI64 00:00:39:00:00:72:41:eb ::> fwohci0: Phy 1394a available S400, 2 ports. ::> fwohci0: Link S400, max_rec 2048 bytes. ::> firewire0: on fwohci0 ::> sbp0: on firewire0 ::> fwe0: on firewire0 ::> if_fwe0: Fake Ethernet address: 02:00:39:72:41:eb ::> fwe0: Ethernet address: 02:00:39:72:41:eb ::> fwe0: if_start running deferred for Giant ::> fwohci0: Initiate bus reset ::> fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode ::> firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) ::> firewire0: bus manager 0 (me) ::> pci1: at device 11.4 (no driver attached) ::> isab0: at device 31.0 on pci0 ::> isa0: on isab0 ::> atapci0: port 0x1f0-0x1f7,0x3f6,0x170- ::> 0x177,0x376,0xbfa0-0xbfaf irq 11 at device 31.1 on pci0 ::> ata0: on atapci0 ::> ata1: on atapci0 ::> pcm0: port 0xbe00-0xbeff,0xbdc0-0xbdff mem ::> 0xcfdffe00-0xcfdfffff,0xcfdffd00-0xcfdffdff irq 11 at device 31.5 on ::pci0 ::> pcm0: [GIANT-LOCKED] ::> pcm0: ::> pci0: at device 31.6 (no driver ::attached) ::> acpi_lid0: on acpi0 ::> battery0: on acpi0 ::> acpi_button0: on acpi0 ::> acpi_acad0: on acpi0 ::> acpi_toshiba0: on acpi0 ::> acpi_tz0: on acpi0 ::> atkbdc0: port 0x60,0x64 irq 1 on acpi0 ::> atkbd0: irq 1 on atkbdc0 ::> kbd0 at atkbd0 ::> atkbd0: [GIANT-LOCKED] ::> psm0: irq 12 on atkbdc0 ::> psm0: [GIANT-LOCKED] ::> psm0: model Generic PS/2 mouse, device ID 0 ::> sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 ::on ::> acpi0 ::> sio0: type 16550A ::> pmtimer0 on isa0 ::> orm0: at iomem 0xc0000-0xcffff,0xe0000-0xeffff pnpid ::> ORM0000 on isa0 ::> sc0: at flags 0x100 on isa0 ::> sc0: VGA <16 virtual consoles, flags=0x300> ::> sio1: configured irq 3 not in bitmap of probed irqs 0 ::> sio1: port may not be enabled ::> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on ::isa0 ::> Timecounter "TSC" frequency 1097256406 Hz quality 800 ::> Timecounters tick every 1.000 msec ::> ad0: 57231MB at ata0-master UDMA100 ::> acd0: DVDR at ata1-master UDMA33 ::> pccard1: Allocation failed for cfe 1 ::> sio4: at port 0x2f8-0x2ff irq 11 function 0 config 2 on ::> pccard1 ::> sio4: type 16550A ::> sio4: unable to activate interrupt in fast mode - using normal mode ::> Trying to mount root from ufs:/dev/ad0s4a ::> ::=----------------------------------------------------------------------- ::-- ::> - ::> ::> Thanks in advance, ::> Haro ::> ::=----------------------------------------------------------------------- ::-- ::> ----- ::> _ _ Munehiro (haro) Matsuda ::> -|- /_\ |_|_| Internet Solution Dept., Kubota Graphics ::Technologies ::> Inc. ::> /|\ |_| |_|_| 2-8-8 Shinjuku Shinjuku-ku Tokyo 160-0022, Japan ::> Tel: +81-3-3225-0767 Fax: +81-3-3225-0740 ::> ::> ::> _______________________________________________ ::> freebsd-acpi@freebsd.org mailing list ::> http://lists.freebsd.org/mailman/listinfo/freebsd-acpi ::> To unsubscribe, send any mail to ::"freebsd-acpi-unsubscribe@freebsd.org" :: From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 01:04:43 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04D5516A41F; Thu, 3 Nov 2005 01:04:43 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83EB743D45; Thu, 3 Nov 2005 01:04:42 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.33] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id jA314dxq024218 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 2 Nov 2005 17:04:40 -0800 Message-ID: <436961FD.3040605@root.org> Date: Wed, 02 Nov 2005 17:03:57 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Munehiro Matsuda References: <971FCB6690CD0E4898387DBF7552B90E0346CAFB@orsmsx403.amr.corp.intel.com> <20051103.094643.74756456.haro@h4.dion.ne.jp> In-Reply-To: <20051103.094643.74756456.haro@h4.dion.ne.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org, robert.moore@intel.com, jkim@freebsd.org Subject: Re: Panic on boot with new ACPI-CA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 01:04:43 -0000 As I mentioned to Jung-uk, the problem is likely an error in acpi-ca modifying memory after it has freed it. The way to track this down is to enable memguard(9). See the man page for info. You need to add options DEBUG_MEMGUARD to your kernel, set the malloc type to watch to M_ACPICA, and rebuild your kernel and modules. Memguard sets page permissions so we can catch the culprit who is modifying the memory. http://www.freebsd.org/cgi/man.cgi?query=memguard&apropos=0&sektion=0&manpath=FreeBSD+6.0-current&format=html If you need a kernel to keep running in production while debugging the other kernel, disable options INVARIANTS to get rid of the diagnostic panic. -Nate Munehiro Matsuda wrote: > Hi, > > Thanks for looking. > I've put the output dsdt/asl file from following command onto the > URL below. > > command: > # acpidump -t -d -o Dynabook_MX190R.dsdt > Dynabook_MX190R.asl > > URL: > http://wwwb.dcns.ne.jp/~haro01/Dynabook_MX190R.dsdt > http://wwwb.dcns.ne.jp/~haro01/Dynabook_MX190R.asl > > Thanks in advance, > Haro > > From: "Moore, Robert" > Date: Wed, 2 Nov 2005 09:51:23 -0800 > ::If you will send me the acpidump for the machine, I will take a look at > ::the problem. > :: > ::Thanks, > ::Bob > :: > :: > ::> -----Original Message----- > ::> From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- > ::> acpi@freebsd.org] On Behalf Of Munehiro Matsuda > ::> Sent: Wednesday, November 02, 2005 7:08 AM > ::> To: jkim@freebsd.org > ::> Cc: freebsd-acpi@freebsd.org; freebsd-current@freebsd.org > ::> Subject: Panic on boot with new ACPI-CA (Re: [HEADSUP] ACPI-CA > ::20051021 > ::> import) > ::> > ::> From: Jung-uk Kim > ::> Date: Tue, 1 Nov 2005 17:49:44 -0500 > ::> ::On Tuesday 01 November 2005 05:01 pm, Jung-uk Kim wrote: > ::> ::> ACPI-CA 20051021 will be imported any minute now. I will let you > ::> ::> know when completed. > ::> :: > ::> ::ACPI-CA 20051021 import is completed. > ::> :: > ::> ::Thanks! > ::> :: > ::> ::Jung-uk Kim > ::> > ::> Hi, > ::> > ::> After the import of new ACPI-CA code, I get system panic on boot, > ::> where I used to get "can't fetch resources for \\_SB_.PCI0.FNC0.PRT_ - > ::> AE_BAD_DATA" message. > ::> > ::> If you need more info, please let me know. > ::> > ::> Here's hand written down panic messages. > ::> > ::=----------------------------------------------------------------------- > ::-- > ::> - > ::> npx0: [FAST] > ::> npx0: on motherboard > ::> npx0: INT 16 interface > ::> acpi0: on motherboard > ::> acpi0: Power Button (fixed) > ::> pci_link0: irq 10 on acpi0 > ::> pci_link1: irq 11 on acpi0 > ::> pci_link2: irq 11 on acpi0 > ::> pci_link3: irq 11 on acpi0 > ::> pci_link4: irq 11 on acpi0 > ::> pci_link5: irq 11 on acpi0 > ::> pci_link6: irq 11 on acpi0 > ::> pci_link7: irq 11 on acpi0 > ::> Memory modified after free 0xc1ee1600(124) val=c @ 0xc1ee1600 > ::> panic: Most recently used by acpica > ::> > ::> cpuid = 0 > ::> KDB: enter: panic > ::> [thread pid 0 tid 0] > ::> Stopped at kbt_enter+0x2b: nop > ::> db> bt > ::> Tracing pid 0 tid 0 td 0xc0736780 > ::> kdb_enter(c06cc93e) at kdb_enter+0x2b > ::> panic(c06e42e7,c089c1a8,c06e42b8,c1ee1600,8c) at panic+0x127 > ::> mtrash_ctor(c1ee1600,80,0,1) at mtrash_ctor+0x4d > ::> uma_zalloc_arg(c104a1e0,0,1) at uma_zalloc_arg+0x10f > ::> malloc(68,c089ef00,1,c0c20bb4,c087e562) at malloc+0xb2 > ::> AcpiOsAllocate(68,0,c1ece1e0,4,c0c20be0) at AcpiOsAllocate+0x12 > ::> AcpiUtCallocate(68,10,c089b337,157,c0c20bec) at AcpiUtCallocate+0x16 > ::> AcpiGetObjectInfo(c1ece1e0,c0c20bf8,0,c1ece1e0,ffffffff) at > ::> AcpiGetObjectInfo+0x5b > ::> acpi_MatchHid(0,c089f740,6,c1ece1e0,0) at acpi_MatchHid+0x32 > ::> acpi_probe_child(c1ece1e0,4,c1e9c800,0,0) at acpi_probe_child+0x94 > ::> AcpiNsWalkNamespace(0,ffffffff,64,1,c0883c98) at > ::AcpiNsWalkNamespace+0xa1 > ::> AcpiWalkNamespace(0,ffffffff,64,c0883c98,c1e9c800) at > ::> AcpiWalkNamespace+0x3b > ::> acpi_attach(c1e9c800) at acpi_attach+0x4ff > ::> device_attach(c1e9c800,0,c1e9c800,c1e9d300,0) at device_attach+0x58 > ::> device_probe_and attach(c1e9c800) at device_probe_and_attach+0xe0 > ::> bus_generic_attach(c1e9d300,c1e9d300,c1e9d300,c0c20d40,c0529340) at > ::> bus_generic_attach+0x16 > ::> nexus_attach(c1e9d300) at nexus_attach+0x13 > ::> device_attach(c1e9d300,c0533914,c1e9d300,c0721bb0,c28000) at > ::> device_attach+0x58 > ::> device_probe_and_attach(c1e9d300) at device_probe_and_attach+0xe0 > ::> root_bus_configure(c0c20d88,c04eb592,0,c1ec00,c1e000) at > ::> root_bus_configure+0x16configure(0,c1ec00,c1e000,0,c04392f5) at > ::> configure+0x9 > ::> mi_startup() at mi_startup+0x96 > ::> begin() at begine+0x2c > ::> > ::=----------------------------------------------------------------------- > ::-- > ::> - > ::> > ::> Following is boot message from the last kernel, just before the > ::> import of new code. > ::> > ::=----------------------------------------------------------------------- > ::-- > ::> - > ::> 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 7.0-CURRENT #135: Mon Oct 31 21:33:52 JST 2005 > ::> > ::haro@legacy.ttr.kubota.co.jp:/home/haro/tmp/sys-7/i386/compile/LEGACY > ::> WARNING: WITNESS option enabled, expect reduced performance. > ::> Timecounter "i8254" frequency 1193182 Hz quality 0 > ::> CPU: Intel(R) Pentium(R) M processor 1.10GHz (1097.26-MHz 686-class > ::CPU) > ::> Origin = "GenuineIntel" Id = 0x6d6 Stepping = 6 > ::> > ::> > ::Features=0xafe9f9bf ::,P > ::> AT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE> > ::> Features2=0x180 > ::> real memory = 787808256 (751 MB) > ::> avail memory = 761475072 (726 MB) > ::> npx0: [FAST] > ::> npx0: on motherboard > ::> npx0: INT 16 interface > ::> acpi0: on motherboard > ::> acpi0: Power Button (fixed) > ::> pci_link0: irq 10 on acpi0 > ::> pci_link1: irq 11 on acpi0 > ::> pci_link2: irq 11 on acpi0 > ::> pci_link3: irq 11 on acpi0 > ::> pci_link4: irq 11 on acpi0 > ::> pci_link5: irq 11 on acpi0 > ::> pci_link6: irq 11 on acpi0 > ::> pci_link7: irq 11 on acpi0 > ::> can't fetch resources for \\_SB_.PCI0.FNC0.PRT_ - AE_BAD_DATA > ::> Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > ::> acpi_timer0: <24-bit timer at 3.579545MHz> port 0xd808-0xd80b on acpi0 > ::> cpu0: on acpi0 > ::> est0: on cpu0 > ::> p4tcc0: on cpu0 > ::> pcib0: port 0xcf8-0xcff on acpi0 > ::> pci0: on pcib0 > ::> pci0: at device 0.1 (no driver attached) > ::> pci0: at device 0.3 (no driver attached) > ::> agp0: port > ::0xeff8-0xefff > ::> mem 0xd8000000-0xdfffffff,0xd0000000-0xd007ffff irq 10 at device 2.0 > ::on > ::> pci0 > ::> agp0: detected 16252k stolen memory > ::> agp0: aperture size is 128M > ::> pci0: at device 2.1 (no driver attached) > ::> uhci0: port 0xcfe0-0xcfff > ::irq > ::> 10 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 0xcf80-0xcf9f > ::irq > ::> 11 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 0xcf60-0xcf7f > ::irq > ::> 11 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 > ::> ehci0: mem 0xcffffc00- > ::> 0xcfffffff irq 11 at device 29.7 on pci0 > ::> ehci0: [GIANT-LOCKED] > ::> usb3: EHCI version 1.0 > ::> usb3: companion controllers, 2 ports each: usb0 usb1 usb2 > ::> usb3: on ehci0 > ::> usb3: USB revision 2.0 > ::> uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 > ::> uhub3: 6 ports with 6 removable, self powered > ::> pcib1: at device 30.0 on pci0 > ::> pci1: on pcib1 > ::> iwi0: mem 0xcfeff000-0xcfefffff irq 11 > ::at > ::> device 5.0 on pci1 > ::> iwi0: Ethernet address: 00:0e:35:c2:a2:7b > ::> fxp0: port 0xcf00-0xcf3f > ::mem > ::> 0xcfefe000-0xcfefefff irq 11 at device 8.0 on pci1 > ::> miibus0: on fxp0 > ::> inphy0: on miibus0 > ::> inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ::> fxp0: Ethernet address: 00:0e:7b:eb:71:23 > ::> cbb0: at device 11.0 on pci1 > ::> cardbus0: on cbb0 > ::> pccard0: <16-bit PCCard bus> on cbb0 > ::> cbb1: at device 11.1 on pci1 > ::> cardbus1: on cbb1 > ::> pccard1: <16-bit PCCard bus> on cbb1 > ::> fwohci0: <1394 Open Host Controller Interface> mem 0xcfefd800- > ::> 0xcfefdfff,0xcfef8000-0xcfefbfff irq 11 at device 11.2 on pci1 > ::> fwohci0: OHCI version 1.10 (ROM=1) > ::> fwohci0: No. of Isochronous channels is 4. > ::> fwohci0: EUI64 00:00:39:00:00:72:41:eb > ::> fwohci0: Phy 1394a available S400, 2 ports. > ::> fwohci0: Link S400, max_rec 2048 bytes. > ::> firewire0: on fwohci0 > ::> sbp0: on firewire0 > ::> fwe0: on firewire0 > ::> if_fwe0: Fake Ethernet address: 02:00:39:72:41:eb > ::> fwe0: Ethernet address: 02:00:39:72:41:eb > ::> fwe0: if_start running deferred for Giant > ::> fwohci0: Initiate bus reset > ::> fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode > ::> firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) > ::> firewire0: bus manager 0 (me) > ::> pci1: at device 11.4 (no driver attached) > ::> isab0: at device 31.0 on pci0 > ::> isa0: on isab0 > ::> atapci0: port 0x1f0-0x1f7,0x3f6,0x170- > ::> 0x177,0x376,0xbfa0-0xbfaf irq 11 at device 31.1 on pci0 > ::> ata0: on atapci0 > ::> ata1: on atapci0 > ::> pcm0: port 0xbe00-0xbeff,0xbdc0-0xbdff mem > ::> 0xcfdffe00-0xcfdfffff,0xcfdffd00-0xcfdffdff irq 11 at device 31.5 on > ::pci0 > ::> pcm0: [GIANT-LOCKED] > ::> pcm0: > ::> pci0: at device 31.6 (no driver > ::attached) > ::> acpi_lid0: on acpi0 > ::> battery0: on acpi0 > ::> acpi_button0: on acpi0 > ::> acpi_acad0: on acpi0 > ::> acpi_toshiba0: on acpi0 > ::> acpi_tz0: on acpi0 > ::> atkbdc0: port 0x60,0x64 irq 1 on acpi0 > ::> atkbd0: irq 1 on atkbdc0 > ::> kbd0 at atkbd0 > ::> atkbd0: [GIANT-LOCKED] > ::> psm0: irq 12 on atkbdc0 > ::> psm0: [GIANT-LOCKED] > ::> psm0: model Generic PS/2 mouse, device ID 0 > ::> sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 > ::on > ::> acpi0 > ::> sio0: type 16550A > ::> pmtimer0 on isa0 > ::> orm0: at iomem 0xc0000-0xcffff,0xe0000-0xeffff pnpid > ::> ORM0000 on isa0 > ::> sc0: at flags 0x100 on isa0 > ::> sc0: VGA <16 virtual consoles, flags=0x300> > ::> sio1: configured irq 3 not in bitmap of probed irqs 0 > ::> sio1: port may not be enabled > ::> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on > ::isa0 > ::> Timecounter "TSC" frequency 1097256406 Hz quality 800 > ::> Timecounters tick every 1.000 msec > ::> ad0: 57231MB at ata0-master UDMA100 > ::> acd0: DVDR at ata1-master UDMA33 > ::> pccard1: Allocation failed for cfe 1 > ::> sio4: at port 0x2f8-0x2ff irq 11 function 0 config 2 on > ::> pccard1 > ::> sio4: type 16550A > ::> sio4: unable to activate interrupt in fast mode - using normal mode > ::> Trying to mount root from ufs:/dev/ad0s4a From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 02:09:15 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F0E016A41F; Thu, 3 Nov 2005 02:09:15 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6B3B43D45; Thu, 3 Nov 2005 02:09:12 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from flame.pc (patr530-a063.otenet.gr [212.205.215.63]) by rosebud.otenet.gr (8.13.4/8.13.4/Debian-1) with ESMTP id jA3299Cr017102; Thu, 3 Nov 2005 04:09:09 +0200 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id jA3293KH030404; Thu, 3 Nov 2005 04:09:03 +0200 (EET) (envelope-from keramida@linux.gr) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id jA3292PD030395; Thu, 3 Nov 2005 04:09:02 +0200 (EET) (envelope-from keramida@linux.gr) Date: Thu, 3 Nov 2005 04:09:02 +0200 From: Giorgos Keramidas To: Nate Lawson Message-ID: <20051103020902.GA29536@flame.pc> References: <971FCB6690CD0E4898387DBF7552B90E0346CAFB@orsmsx403.amr.corp.intel.com> <20051103.094643.74756456.haro@h4.dion.ne.jp> <436961FD.3040605@root.org> <20051103014740.GA1586@flame.pc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051103014740.GA1586@flame.pc> Cc: Munehiro Matsuda , freebsd-acpi@freebsd.org, freebsd-current@freebsd.org, robert.moore@intel.com, jkim@freebsd.org Subject: Re: Panic on boot with new ACPI-CA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 02:09:15 -0000 On 2005-11-03 03:47, Giorgos Keramidas wrote: > On 2005-11-02 17:03, Nate Lawson wrote: > > As I mentioned to Jung-uk, the problem is likely an error in > > acpi-ca modifying memory after it has freed it. The way to > > track this down is to enable memguard(9). See the man page for > > info. You need to add options DEBUG_MEMGUARD to your kernel, > > set the malloc type to watch to M_ACPICA, and rebuild your > > kernel and modules. Memguard sets page permissions so we can > > catch the culprit who is modifying the memory. > > This is exactly the messgae printed on my console at panic time > -- of memory modified after free. I'm building a kernel with > MEMGUARD now, but it's probably going to be a bit hard to get a > kernel dump, because the panic happens before disks are available > and I don't have a serial console here. Does the following look ok for using memguard(9) with M_ACPICA? %%% begin acpica-memguard.patch Index: kern/kern_malloc.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_malloc.c,v retrieving revision 1.148 diff -u -r1.148 kern_malloc.c --- kern/kern_malloc.c 20 Oct 2005 21:28:31 -0000 1.148 +++ kern/kern_malloc.c 3 Nov 2005 02:04:02 -0000 @@ -62,6 +62,8 @@ #include #include +MALLOC_DECLARE(M_ACPICA); + #ifdef DEBUG_MEMGUARD #include #endif @@ -305,7 +307,7 @@ #ifdef DEBUG_MEMGUARD /* XXX CHANGEME! */ - if (mtp == M_SUBPROC) + if (mtp == M_ACPICA) return memguard_alloc(size, flags); #endif %%% end acpica-memguard.patch From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 02:47:17 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1731E16A41F for ; Thu, 3 Nov 2005 02:47:17 +0000 (GMT) (envelope-from haro@h4.dion.ne.jp) Received: from smtp1.dcns.ne.jp (smtp1.dcns.ne.jp [203.178.100.134]) by mx1.FreeBSD.org (Postfix) with SMTP id 21A1843D55 for ; Thu, 3 Nov 2005 02:47:13 +0000 (GMT) (envelope-from haro@h4.dion.ne.jp) Received: (qmail 22714 invoked by uid 503); 3 Nov 2005 11:47:12 +0900 Received: from unknown (HELO localhost) (211.10.184.118) by smtp1.dcns.ne.jp with SMTP; 3 Nov 2005 11:47:12 +0900 Date: Thu, 03 Nov 2005 11:47:12 +0900 (JST) Message-Id: <20051103.114712.74756421.haro@h4.dion.ne.jp> To: keramida@linux.gr From: Munehiro Matsuda In-Reply-To: <20051103020902.GA29536@flame.pc> References: <436961FD.3040605@root.org> <20051103014740.GA1586@flame.pc> <20051103020902.GA29536@flame.pc> 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-acpi@freebsd.org, freebsd-current@freebsd.org, robert.moore@intel.com, jkim@freebsd.org, nate@root.org Subject: Re: Panic on boot with new ACPI-CA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 02:47:17 -0000 From: Giorgos Keramidas Date: Thu, 3 Nov 2005 04:09:02 +0200 ::On 2005-11-03 03:47, Giorgos Keramidas wrote: ::> On 2005-11-02 17:03, Nate Lawson wrote: ::> > As I mentioned to Jung-uk, the problem is likely an error in ::> > acpi-ca modifying memory after it has freed it. The way to ::> > track this down is to enable memguard(9). See the man page for ::> > info. You need to add options DEBUG_MEMGUARD to your kernel, ::> > set the malloc type to watch to M_ACPICA, and rebuild your ::> > kernel and modules. Memguard sets page permissions so we can ::> > catch the culprit who is modifying the memory. ::> ::> This is exactly the messgae printed on my console at panic time ::> -- of memory modified after free. I'm building a kernel with ::> MEMGUARD now, but it's probably going to be a bit hard to get a ::> kernel dump, because the panic happens before disks are available ::> and I don't have a serial console here. :: ::Does the following look ok for using memguard(9) with M_ACPICA? :: ::%%% begin acpica-memguard.patch ::Index: kern/kern_malloc.c ::=================================================================== ::RCS file: /home/ncvs/src/sys/kern/kern_malloc.c,v ::retrieving revision 1.148 ::diff -u -r1.148 kern_malloc.c ::--- kern/kern_malloc.c 20 Oct 2005 21:28:31 -0000 1.148 ::+++ kern/kern_malloc.c 3 Nov 2005 02:04:02 -0000 ::@@ -62,6 +62,8 @@ :: #include :: #include :: ::+MALLOC_DECLARE(M_ACPICA); ::+ :: #ifdef DEBUG_MEMGUARD :: #include :: #endif ::@@ -305,7 +307,7 @@ :: :: #ifdef DEBUG_MEMGUARD :: /* XXX CHANGEME! */ ::- if (mtp == M_SUBPROC) ::+ if (mtp == M_ACPICA) :: return memguard_alloc(size, flags); :: #endif :: ::%%% end acpica-memguard.patch :: Hi, There are few more "CHANGEME!" places. I used following: @@ -64,6 +64,7 @@ #ifdef DEBUG_MEMGUARD #include +MALLOC_DECLARE(M_ACPICA); #endif #if defined(INVARIANTS) && defined(__i386__) @@ -305,7 +306,7 @@ #ifdef DEBUG_MEMGUARD /* XXX CHANGEME! */ - if (mtp == M_SUBPROC) + if (mtp == M_ACPICA) return memguard_alloc(size, flags); #endif @@ -360,7 +361,7 @@ #ifdef DEBUG_MEMGUARD /* XXX CHANGEME! */ - if (mtp == M_SUBPROC) { + if (mtp == M_ACPICA) { memguard_free(addr); return; } @@ -424,7 +425,7 @@ #ifdef DEBUG_MEMGUARD /* XXX: CHANGEME! */ -if (mtp == M_SUBPROC) { +if (mtp == M_ACPICA) { slab = NULL; alloc = size; } else { =------------------------------------------------------------------------------ _ _ Munehiro (haro) Matsuda -|- /_\ |_|_| Internet Solution Dept., KGT Inc. /|\ |_| |_|_| 2-8-8 Shinjuku Shinjuku-ku Tokyo 160-0022, Japan Tel: +81-3-3225-0767 Fax: +81-3-3225-0740 From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 03:24:08 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF15F16A426 for ; Thu, 3 Nov 2005 03:24:08 +0000 (GMT) (envelope-from haro@h4.dion.ne.jp) Received: from smtp1.dcns.ne.jp (smtp1.dcns.ne.jp [203.178.100.134]) by mx1.FreeBSD.org (Postfix) with SMTP id 6804843D53 for ; Thu, 3 Nov 2005 03:24:07 +0000 (GMT) (envelope-from haro@h4.dion.ne.jp) Received: (qmail 27914 invoked by uid 503); 3 Nov 2005 12:24:06 +0900 Received: from unknown (HELO localhost) (211.10.184.118) by smtp1.dcns.ne.jp with SMTP; 3 Nov 2005 12:24:06 +0900 Date: Thu, 03 Nov 2005 12:24:04 +0900 (JST) Message-Id: <20051103.122404.74756296.haro@h4.dion.ne.jp> To: nate@root.org From: Munehiro Matsuda In-Reply-To: <436961FD.3040605@root.org> References: <971FCB6690CD0E4898387DBF7552B90E0346CAFB@orsmsx403.amr.corp.intel.com> <20051103.094643.74756456.haro@h4.dion.ne.jp> <436961FD.3040605@root.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-acpi@freebsd.org, freebsd-current@freebsd.org, robert.moore@intel.com, jkim@freebsd.org Subject: Re: Panic on boot with new ACPI-CA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 03:24:08 -0000 Hi Nate, Thanks for memguard tip. But now, I'm confuse with the outcome. :-( 1) With memguard enabled, system boots up just fine, even acpi compiled into kernel or loaded as a module. 2) Without memguard, but with acpi compiled into kernel, system boots up past the reported point. But this time, npanics with page fault further into the booting process, just as Marcel reported yesterday. 3) Without memguard and with acpi loaded as module, system panics as reported in my original mail. So, the memguard works as workaround for me, but not as debuging aid. ;-P If you need more info or any other way to debug, please let me know. Thanks in advance, Haro From: Nate Lawson Date: Wed, 02 Nov 2005 17:03:57 -0800 ::As I mentioned to Jung-uk, the problem is likely an error in acpi-ca ::modifying memory after it has freed it. The way to track this down is ::to enable memguard(9). See the man page for info. You need to add ::options DEBUG_MEMGUARD to your kernel, set the malloc type to watch to ::M_ACPICA, and rebuild your kernel and modules. Memguard sets page ::permissions so we can catch the culprit who is modifying the memory. :: ::http://www.freebsd.org/cgi/man.cgi?query=memguard&apropos=0&sektion=0&manpath=FreeBSD+6.0-current&format=html :: ::If you need a kernel to keep running in production while debugging the ::other kernel, disable options INVARIANTS to get rid of the diagnostic panic. :: ::-Nate :: ::Munehiro Matsuda wrote: ::> Hi, ::> ::> Thanks for looking. ::> I've put the output dsdt/asl file from following command onto the ::> URL below. ::> ::> command: ::> # acpidump -t -d -o Dynabook_MX190R.dsdt > Dynabook_MX190R.asl ::> ::> URL: ::> http://wwwb.dcns.ne.jp/~haro01/Dynabook_MX190R.dsdt ::> http://wwwb.dcns.ne.jp/~haro01/Dynabook_MX190R.asl ::> ::> Thanks in advance, ::> Haro ::> ::> From: "Moore, Robert" ::> Date: Wed, 2 Nov 2005 09:51:23 -0800 ::> ::If you will send me the acpidump for the machine, I will take a look at ::> ::the problem. ::> :: ::> ::Thanks, ::> ::Bob ::> :: ::> :: ::> ::> -----Original Message----- ::> ::> From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- ::> ::> acpi@freebsd.org] On Behalf Of Munehiro Matsuda ::> ::> Sent: Wednesday, November 02, 2005 7:08 AM ::> ::> To: jkim@freebsd.org ::> ::> Cc: freebsd-acpi@freebsd.org; freebsd-current@freebsd.org ::> ::> Subject: Panic on boot with new ACPI-CA (Re: [HEADSUP] ACPI-CA ::> ::20051021 ::> ::> import) ::> ::> ::> ::> From: Jung-uk Kim ::> ::> Date: Tue, 1 Nov 2005 17:49:44 -0500 ::> ::> ::On Tuesday 01 November 2005 05:01 pm, Jung-uk Kim wrote: ::> ::> ::> ACPI-CA 20051021 will be imported any minute now. I will let you ::> ::> ::> know when completed. ::> ::> :: ::> ::> ::ACPI-CA 20051021 import is completed. ::> ::> :: ::> ::> ::Thanks! ::> ::> :: ::> ::> ::Jung-uk Kim ::> ::> ::> ::> Hi, ::> ::> ::> ::> After the import of new ACPI-CA code, I get system panic on boot, ::> ::> where I used to get "can't fetch resources for \\_SB_.PCI0.FNC0.PRT_ - ::> ::> AE_BAD_DATA" message. ::> ::> ::> ::> If you need more info, please let me know. ::> ::> ::> ::> Here's hand written down panic messages. ::> ::> ::> ::=----------------------------------------------------------------------- ::> ::-- ::> ::> - ::> ::> npx0: [FAST] ::> ::> npx0: on motherboard ::> ::> npx0: INT 16 interface ::> ::> acpi0: on motherboard ::> ::> acpi0: Power Button (fixed) ::> ::> pci_link0: irq 10 on acpi0 ::> ::> pci_link1: irq 11 on acpi0 ::> ::> pci_link2: irq 11 on acpi0 ::> ::> pci_link3: irq 11 on acpi0 ::> ::> pci_link4: irq 11 on acpi0 ::> ::> pci_link5: irq 11 on acpi0 ::> ::> pci_link6: irq 11 on acpi0 ::> ::> pci_link7: irq 11 on acpi0 ::> ::> Memory modified after free 0xc1ee1600(124) val=c @ 0xc1ee1600 ::> ::> panic: Most recently used by acpica ::> ::> ::> ::> cpuid = 0 ::> ::> KDB: enter: panic ::> ::> [thread pid 0 tid 0] ::> ::> Stopped at kbt_enter+0x2b: nop ::> ::> db> bt ::> ::> Tracing pid 0 tid 0 td 0xc0736780 ::> ::> kdb_enter(c06cc93e) at kdb_enter+0x2b ::> ::> panic(c06e42e7,c089c1a8,c06e42b8,c1ee1600,8c) at panic+0x127 ::> ::> mtrash_ctor(c1ee1600,80,0,1) at mtrash_ctor+0x4d ::> ::> uma_zalloc_arg(c104a1e0,0,1) at uma_zalloc_arg+0x10f ::> ::> malloc(68,c089ef00,1,c0c20bb4,c087e562) at malloc+0xb2 ::> ::> AcpiOsAllocate(68,0,c1ece1e0,4,c0c20be0) at AcpiOsAllocate+0x12 ::> ::> AcpiUtCallocate(68,10,c089b337,157,c0c20bec) at AcpiUtCallocate+0x16 ::> ::> AcpiGetObjectInfo(c1ece1e0,c0c20bf8,0,c1ece1e0,ffffffff) at ::> ::> AcpiGetObjectInfo+0x5b ::> ::> acpi_MatchHid(0,c089f740,6,c1ece1e0,0) at acpi_MatchHid+0x32 ::> ::> acpi_probe_child(c1ece1e0,4,c1e9c800,0,0) at acpi_probe_child+0x94 ::> ::> AcpiNsWalkNamespace(0,ffffffff,64,1,c0883c98) at ::> ::AcpiNsWalkNamespace+0xa1 ::> ::> AcpiWalkNamespace(0,ffffffff,64,c0883c98,c1e9c800) at ::> ::> AcpiWalkNamespace+0x3b ::> ::> acpi_attach(c1e9c800) at acpi_attach+0x4ff ::> ::> device_attach(c1e9c800,0,c1e9c800,c1e9d300,0) at device_attach+0x58 ::> ::> device_probe_and attach(c1e9c800) at device_probe_and_attach+0xe0 ::> ::> bus_generic_attach(c1e9d300,c1e9d300,c1e9d300,c0c20d40,c0529340) at ::> ::> bus_generic_attach+0x16 ::> ::> nexus_attach(c1e9d300) at nexus_attach+0x13 ::> ::> device_attach(c1e9d300,c0533914,c1e9d300,c0721bb0,c28000) at ::> ::> device_attach+0x58 ::> ::> device_probe_and_attach(c1e9d300) at device_probe_and_attach+0xe0 ::> ::> root_bus_configure(c0c20d88,c04eb592,0,c1ec00,c1e000) at ::> ::> root_bus_configure+0x16configure(0,c1ec00,c1e000,0,c04392f5) at ::> ::> configure+0x9 ::> ::> mi_startup() at mi_startup+0x96 ::> ::> begin() at begine+0x2c ::> ::> ::> ::=----------------------------------------------------------------------- ::> ::-- ::> ::> - ::> ::> ::> ::> Following is boot message from the last kernel, just before the ::> ::> import of new code. ::> ::> ::> ::=----------------------------------------------------------------------- ::> ::-- ::> ::> - ::> ::> 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 7.0-CURRENT #135: Mon Oct 31 21:33:52 JST 2005 ::> ::> ::> ::haro@legacy.ttr.kubota.co.jp:/home/haro/tmp/sys-7/i386/compile/LEGACY ::> ::> WARNING: WITNESS option enabled, expect reduced performance. ::> ::> Timecounter "i8254" frequency 1193182 Hz quality 0 ::> ::> CPU: Intel(R) Pentium(R) M processor 1.10GHz (1097.26-MHz 686-class ::> ::CPU) ::> ::> Origin = "GenuineIntel" Id = 0x6d6 Stepping = 6 ::> ::> ::> ::> ::> ::Features=0xafe9f9bf ::,P ::> ::> AT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE> ::> ::> Features2=0x180 ::> ::> real memory = 787808256 (751 MB) ::> ::> avail memory = 761475072 (726 MB) ::> ::> npx0: [FAST] ::> ::> npx0: on motherboard ::> ::> npx0: INT 16 interface ::> ::> acpi0: on motherboard ::> ::> acpi0: Power Button (fixed) ::> ::> pci_link0: irq 10 on acpi0 ::> ::> pci_link1: irq 11 on acpi0 ::> ::> pci_link2: irq 11 on acpi0 ::> ::> pci_link3: irq 11 on acpi0 ::> ::> pci_link4: irq 11 on acpi0 ::> ::> pci_link5: irq 11 on acpi0 ::> ::> pci_link6: irq 11 on acpi0 ::> ::> pci_link7: irq 11 on acpi0 ::> ::> can't fetch resources for \\_SB_.PCI0.FNC0.PRT_ - AE_BAD_DATA ::> ::> Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 ::> ::> acpi_timer0: <24-bit timer at 3.579545MHz> port 0xd808-0xd80b on acpi0 ::> ::> cpu0: on acpi0 ::> ::> est0: on cpu0 ::> ::> p4tcc0: on cpu0 ::> ::> pcib0: port 0xcf8-0xcff on acpi0 ::> ::> pci0: on pcib0 ::> ::> pci0: at device 0.1 (no driver attached) ::> ::> pci0: at device 0.3 (no driver attached) ::> ::> agp0: port ::> ::0xeff8-0xefff ::> ::> mem 0xd8000000-0xdfffffff,0xd0000000-0xd007ffff irq 10 at device 2.0 ::> ::on ::> ::> pci0 ::> ::> agp0: detected 16252k stolen memory ::> ::> agp0: aperture size is 128M ::> ::> pci0: at device 2.1 (no driver attached) ::> ::> uhci0: port 0xcfe0-0xcfff ::> ::irq ::> ::> 10 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 0xcf80-0xcf9f ::> ::irq ::> ::> 11 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 0xcf60-0xcf7f ::> ::irq ::> ::> 11 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 ::> ::> ehci0: mem 0xcffffc00- ::> ::> 0xcfffffff irq 11 at device 29.7 on pci0 ::> ::> ehci0: [GIANT-LOCKED] ::> ::> usb3: EHCI version 1.0 ::> ::> usb3: companion controllers, 2 ports each: usb0 usb1 usb2 ::> ::> usb3: on ehci0 ::> ::> usb3: USB revision 2.0 ::> ::> uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 ::> ::> uhub3: 6 ports with 6 removable, self powered ::> ::> pcib1: at device 30.0 on pci0 ::> ::> pci1: on pcib1 ::> ::> iwi0: mem 0xcfeff000-0xcfefffff irq 11 ::> ::at ::> ::> device 5.0 on pci1 ::> ::> iwi0: Ethernet address: 00:0e:35:c2:a2:7b ::> ::> fxp0: port 0xcf00-0xcf3f ::> ::mem ::> ::> 0xcfefe000-0xcfefefff irq 11 at device 8.0 on pci1 ::> ::> miibus0: on fxp0 ::> ::> inphy0: on miibus0 ::> ::> inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ::> ::> fxp0: Ethernet address: 00:0e:7b:eb:71:23 ::> ::> cbb0: at device 11.0 on pci1 ::> ::> cardbus0: on cbb0 ::> ::> pccard0: <16-bit PCCard bus> on cbb0 ::> ::> cbb1: at device 11.1 on pci1 ::> ::> cardbus1: on cbb1 ::> ::> pccard1: <16-bit PCCard bus> on cbb1 ::> ::> fwohci0: <1394 Open Host Controller Interface> mem 0xcfefd800- ::> ::> 0xcfefdfff,0xcfef8000-0xcfefbfff irq 11 at device 11.2 on pci1 ::> ::> fwohci0: OHCI version 1.10 (ROM=1) ::> ::> fwohci0: No. of Isochronous channels is 4. ::> ::> fwohci0: EUI64 00:00:39:00:00:72:41:eb ::> ::> fwohci0: Phy 1394a available S400, 2 ports. ::> ::> fwohci0: Link S400, max_rec 2048 bytes. ::> ::> firewire0: on fwohci0 ::> ::> sbp0: on firewire0 ::> ::> fwe0: on firewire0 ::> ::> if_fwe0: Fake Ethernet address: 02:00:39:72:41:eb ::> ::> fwe0: Ethernet address: 02:00:39:72:41:eb ::> ::> fwe0: if_start running deferred for Giant ::> ::> fwohci0: Initiate bus reset ::> ::> fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode ::> ::> firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) ::> ::> firewire0: bus manager 0 (me) ::> ::> pci1: at device 11.4 (no driver attached) ::> ::> isab0: at device 31.0 on pci0 ::> ::> isa0: on isab0 ::> ::> atapci0: port 0x1f0-0x1f7,0x3f6,0x170- ::> ::> 0x177,0x376,0xbfa0-0xbfaf irq 11 at device 31.1 on pci0 ::> ::> ata0: on atapci0 ::> ::> ata1: on atapci0 ::> ::> pcm0: port 0xbe00-0xbeff,0xbdc0-0xbdff mem ::> ::> 0xcfdffe00-0xcfdfffff,0xcfdffd00-0xcfdffdff irq 11 at device 31.5 on ::> ::pci0 ::> ::> pcm0: [GIANT-LOCKED] ::> ::> pcm0: ::> ::> pci0: at device 31.6 (no driver ::> ::attached) ::> ::> acpi_lid0: on acpi0 ::> ::> battery0: on acpi0 ::> ::> acpi_button0: on acpi0 ::> ::> acpi_acad0: on acpi0 ::> ::> acpi_toshiba0: on acpi0 ::> ::> acpi_tz0: on acpi0 ::> ::> atkbdc0: port 0x60,0x64 irq 1 on acpi0 ::> ::> atkbd0: irq 1 on atkbdc0 ::> ::> kbd0 at atkbd0 ::> ::> atkbd0: [GIANT-LOCKED] ::> ::> psm0: irq 12 on atkbdc0 ::> ::> psm0: [GIANT-LOCKED] ::> ::> psm0: model Generic PS/2 mouse, device ID 0 ::> ::> sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 ::> ::on ::> ::> acpi0 ::> ::> sio0: type 16550A ::> ::> pmtimer0 on isa0 ::> ::> orm0: at iomem 0xc0000-0xcffff,0xe0000-0xeffff pnpid ::> ::> ORM0000 on isa0 ::> ::> sc0: at flags 0x100 on isa0 ::> ::> sc0: VGA <16 virtual consoles, flags=0x300> ::> ::> sio1: configured irq 3 not in bitmap of probed irqs 0 ::> ::> sio1: port may not be enabled ::> ::> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on ::> ::isa0 ::> ::> Timecounter "TSC" frequency 1097256406 Hz quality 800 ::> ::> Timecounters tick every 1.000 msec ::> ::> ad0: 57231MB at ata0-master UDMA100 ::> ::> acd0: DVDR at ata1-master UDMA33 ::> ::> pccard1: Allocation failed for cfe 1 ::> ::> sio4: at port 0x2f8-0x2ff irq 11 function 0 config 2 on ::> ::> pccard1 ::> ::> sio4: type 16550A ::> ::> sio4: unable to activate interrupt in fast mode - using normal mode ::> ::> Trying to mount root from ufs:/dev/ad0s4a :: From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 04:33:50 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CD6516A421 for ; Thu, 3 Nov 2005 04:33:50 +0000 (GMT) (envelope-from mbsd@pacbell.net) Received: from ylpvm12.prodigy.net (ylpvm12-ext.prodigy.net [207.115.57.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E9D043D48 for ; Thu, 3 Nov 2005 04:33:47 +0000 (GMT) (envelope-from mbsd@pacbell.net) Received: from ylpvm01.prodigy.net (ylpvm01-int.prodigy.net [207.115.5.207]) by ylpvm12.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id jA34YAin015315 for ; Wed, 2 Nov 2005 23:34:10 -0500 X-ORBL: [71.139.33.193] Received: from inspiron.home (ppp-71-139-33-193.dsl.snfc21.pacbell.net [71.139.33.193]) by ylpvm01.prodigy.net (8.13.4 dk-milter linux/8.13.4) with ESMTP id jA34boBp005402; Wed, 2 Nov 2005 23:37:53 -0500 Date: Wed, 2 Nov 2005 20:33:39 -0800 (PST) From: =?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= X-X-Sender: mikko@inspiron.home To: Scott Long In-Reply-To: <4367A6AF.7030805@samsco.org> Message-ID: <20051102203028.T20004@inspiron.home> References: <436116D3.908@samsco.org> <621b657f0510280654j56d4a823n5237f89ccc96b1e9@mail.gmail.com> <436246C1.3030108@samsco.org> <20051101165534.GB56709@comp.chem.msu.su> <43679F3C.4040702@samsco.org> <621b657f0511010925t578a5df7nd82040b71e104478@mail.gmail.com> <4367A6AF.7030805@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Felipe openglx , Yar Tikhiy , current@freebsd.org Subject: Re: HEADS UP! 6.0-RELEASE coming X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 04:33:50 -0000 On Tue, 1 Nov 2005, Scott Long wrote: > Felipe openglx wrote: >> In fact I agree with Scott. There isn't much the OS can do. >> >> As for that bug, I'm already in contact with the X.org developers and >> trying to do a deeper debugging on what's going on. The driver >> developer himself said he cannot test that on FreeBSD, thus not >> assuring it full functionality. So it looks much more to be a X.org >> problem than FreeBSD one. >> >> On 11/1/05, Scott Long wrote: >> >>> Yar Tikhiy wrote: >>> >>>> When a 3rd party package crashes our OS, we should care about the >>>> issue, too. However, this case seems to require more investigation >>>> by developers who have similar hardware. >>>> >>> >>> The fact that X has access to /dev/io means that it can do whatever it >>> wants to corrupt the machine, and there isn't much the OS can do about >>> it. >>> >>> Scott >>> >> >> >> >> -- >> openglx@StarByte.net > > One caveat that I forgot is that there are SiS AGP and DRI/DRM modules > that operate in the kernel and come with the stock FreeBSD sources. > You should isolate these out before looking any further. For AGP, > make sure that 'device agp' is not in your kernel or loaded as a > module, and for DRM make sure that your X config file omits the DRI/DRM > options. If it still fails then it's almost certainly an X bug and not > a FreeBSD bug. If it's a DRM problem then you'll still want to contact > the X folks since that code is maintained outside of the FreeBSD > project. If it's an AGP problem then we'll mark is as something that > needs fixing for 6.1. I had this problem. Making X not reboot the machine required removing the "sis" module, as it would be unconditionally loaded by the X server even without drm configured. I no longer have the hardware, and so can't do any further experiments. $.02, /Mikko From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 05:40:57 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C64A16A424 for ; Thu, 3 Nov 2005 05:40:57 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from indor.net.tomline.ru (indor.net.tomline.ru [213.183.100.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACC0E43D46 for ; Thu, 3 Nov 2005 05:40:56 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from SNEZHKO by indorsoft.ru (MDaemon.PRO.v7.2.2.R) with ESMTP id md50000027442.msg for ; Thu, 03 Nov 2005 11:40:47 +0600 X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 88046, updated: 3.11.2005] To: freebsd-current@freebsd.org References: <20051027022313.R675@kushnir1.kiev.ua> <200511021035.22990.max@love2party.net> <20051103001509.C85422@kushnir1.kiev.ua> <200511030059.05946.max@love2party.net> <20051103020404.J85422@kushnir1.kiev.ua> From: Victor Snezhko Date: Thu, 03 Nov 2005 11:40:45 +0600 In-Reply-To: <20051103020404.J85422@kushnir1.kiev.ua> (Vladimir Kushnir's message of "Thu, 3 Nov 2005 02:08:51 +0200 (EET)") Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Processed: indor.net.tomline.ru, Thu, 03 Nov 2005 11:40:47 +0600 (not processed: spam filter disabled) X-Return-Path: snezhko@indorsoft.ru X-MDaemon-Deliver-To: freebsd-current@freebsd.org X-VVS-Spam: false Cc: Max Laier Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 05:40:57 -0000 Vladimir Kushnir writes: > On Thu, 3 Nov 2005, Max Laier wrote: > >>> >>> Here it is: right before panic it prints >>> >>> For 0xffffff0017531100 -1 ticks >>> For 0xffffff0017531100 -1 ticks >> >> This results in two consecutive callout_stop() calls, but shouldn't hurt as >> callout_stop is protected against that. >> >> Do you get a dump for this? Can you compare this pointer to the global >> llinfo_nd6 and see if "c" from the softclock() frame is related (or >> maybe the previous item in the list TAILQ). > Sorry I'm not very goot at debugging. Would you please give me some > instructions (lamer's level, preferably :-)). And anyway I'll be able > to do it tomorrow only. In the meantime, I want to debug this too. I would insert a panic() call somewhere in the beginning of nd6_llinfo_settimer(), but there is a problem. nd6_llinfo_settimer() is called not only when I start ppp, but at bootup too (at bootup - once, I think that this is due to initializing lo0 interface, which has a default ipv6 address). Could I somehow make the kernel not panic at boot time and panic later, when I call ppp? E.g, how can I know uptime from the kernel mode? -- WBR, Victor V. Snezhko EMail: snezhko@indorsoft.ru From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 06:28:38 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BF6D16A41F for ; Thu, 3 Nov 2005 06:28:38 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from indor.net.tomline.ru (indor.net.tomline.ru [213.183.100.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6245E43D46 for ; Thu, 3 Nov 2005 06:28:37 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from SNEZHKO by indorsoft.ru (MDaemon.PRO.v7.2.2.R) with ESMTP id md50000027449.msg for ; Thu, 03 Nov 2005 12:28:31 +0600 X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 88046, updated: 3.11.2005] To: freebsd-current@freebsd.org From: Victor Snezhko Date: Thu, 03 Nov 2005 12:28:30 +0600 Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Processed: indor.net.tomline.ru, Thu, 03 Nov 2005 12:28:31 +0600 (not processed: spam filter disabled) X-Return-Path: snezhko@indorsoft.ru X-MDaemon-Deliver-To: freebsd-current@freebsd.org X-VVS-Spam: false Subject: kgdb strange behaviour on current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 06:28:38 -0000 Some days ago I analysed the crashdump of a panic triggered by ipv6 changes on 2005.10.21.16.23.xx, and noticed a strange thing. See: /home/vvs # kgdb /usr/obj/usr/src/sys/VVS/kernel.debug /var/crash/vmcore.1 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xdeadc0e6 fault code = supervisor read, page not present instruction pointer = 0x20:0xc066e0c2 stack pointer = 0x28:0xcbfd3cac frame pointer = 0x28:0xcbfd3cd4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 12 (swi4: clock sio) panic: from debugger cpuid = 0 Uptime: 1m26s Dumping 255 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 255MB (65264 pages) 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:165 165 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:165 #1 0xc06613fc in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399 #2 0xc0661711 in panic (fmt=0xc0859480 "from debugger") at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xc046d151 in db_panic (addr=-1066999614, have_addr=0, count=-1, modif=0xcbfd3aa8 "") at /usr/src/sys/ddb/db_command.c:435 #4 0xc046d0e8 in db_command (last_cmdp=0xc094a164, cmd_table=0x0, aux_cmd_tablep=0xc08c0048, aux_cmd_tablep_end=0xc08c0064) at /usr/src/sys/ddb/db_command.c:404 #5 0xc046d1b0 in db_command_loop () at /usr/src/sys/ddb/db_command.c:455 ---Type to continue, or q to quit--- #6 0xc046edc9 in db_trap (type=12, code=0) at /usr/src/sys/ddb/db_main.c:221 #7 0xc067b408 in kdb_trap (type=12, code=0, tf=0xcbfd3c6c) at /usr/src/sys/kern/subr_kdb.c:485 #8 0xc0823f68 in trap_fatal (frame=0xcbfd3c6c, eva=3735929062) at /usr/src/sys/i386/i386/trap.c:846 #9 0xc08235f2 in trap (frame= {tf_fs = 8, tf_es = -872611800, tf_ds = -1067122648, tf_edi = -1049930560, tf_esi = -1051228800, tf_ebp = -872596268, tf_isp = -872596328, tf_ebx = 1, tf_edx = -966778392, tf_ecx = -559038242, tf_eax = 85115, tf_trapno = 12, tf_err = 0, tf_eip = -1066999614, tf_cs = 32, tf_eflags = 589826, tf_esp = -1051359088, tf_ss = 0}) ---Type to continue, or q to quit--- at /usr/src/sys/i386/i386/trap.c:269 #10 0xc0810e2a in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #11 0xc066e0c2 in softclock (dummy=0x0) at /usr/src/sys/kern/kern_timeout.c:220 #12 0xc064ed32 in ithread_execute_handlers (p=0xc1558890, ie=0xc1578580) at /usr/src/sys/kern/kern_intr.c:662 #13 0xc064ee63 in ithread_loop (arg=0xc151f8e0) at /usr/src/sys/kern/kern_intr.c:745 #14 0xc064dfc4 in fork_exit (callout=0xc064edfc , arg=0xc151f8e0, frame=0xcbfd3d38) at /usr/src/sys/kern/kern_fork.c:789 #15 0xc0810e8c in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:208 (kgdb) up 11 #11 0xc066e0c2 in softclock (dummy=0x0) at /usr/src/sys/kern/kern_timeout.c:220 220 if (c->c_time != curticks) { (kgdb) list 215 curticks = softticks; 216 bucket = &callwheel[curticks & callwheelmask]; 217 c = TAILQ_FIRST(bucket); 218 while (c) { 219 depth++; 220 if (c->c_time != curticks) { 221 c = TAILQ_NEXT(c, c_links.tqe); 222 ++steps; 223 if (steps >= MAX_SOFTCLOCK_STEPS) { 224 nextsoftcheck = c; (kgdb) print c $1 = (struct callout *) 0xdeadc0de (kgdb) print bucket->tqh_first $2 = (struct callout *) 0xc18eb520 (kgdb) print *(bucket->tqh_first) $3 = {c_links = {sle = {sle_next = 0xdeadc0de}, tqe = {tqe_next = 0xdeadc0de, tqe_prev = 0xdeadc0de}}, c_time = -559038242, c_arg = 0xdeadc0de, c_func = 0xdeadc0de, c_mtx = 0xdeadc0de, c_flags = -559038242} (kgdb) print bucket $4 = (struct callout_tailq *) 0xc66021e8 (kgdb) quit /home/vvs # grep "#define.*[^S]TAILQ_FIRST" /usr/src/sys/sys/queue.h #define TAILQ_FIRST(head) ((head)->tqh_first) bucket->tqh_first seems to be a valid pointer, but points to garbage. But c should be the same pointer, and debugger shows a distinct value for it! Do we need to debug this further? What can I do? -- WBR, Victor V. Snezhko EMail: snezhko@indorsoft.ru From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 06:35:32 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4CBF716A41F for ; Thu, 3 Nov 2005 06:35:32 +0000 (GMT) (envelope-from bsam@bsam.ru) Received: from bsam.ru (gw.ipt.ru [80.253.10.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id D528C43D45 for ; Thu, 3 Nov 2005 06:35:28 +0000 (GMT) (envelope-from bsam@bsam.ru) Received: from bsam by bsam.ru with local (Exim 4.30; FreeBSD) id 1EXYfy-0007xg-PD; Thu, 03 Nov 2005 09:34:18 +0300 To: Victor Snezhko References: <20051027022313.R675@kushnir1.kiev.ua> <200511021035.22990.max@love2party.net> <20051103001509.C85422@kushnir1.kiev.ua> <200511030059.05946.max@love2party.net> <20051103020404.J85422@kushnir1.kiev.ua> From: Boris Samorodov Date: Thu, 03 Nov 2005 09:34:18 +0300 In-Reply-To: (Victor Snezhko's message of "Thu, 03 Nov 2005 11:40:45 +0600") Message-ID: <05980805@srv.sem.ipt.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: "Boris B. Samorodov" Cc: Max Laier , freebsd-current@freebsd.org Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 06:35:32 -0000 On Thu, 03 Nov 2005 11:40:45 +0600 Victor Snezhko wrote: > In the meantime, I want to debug this too. I would insert a panic() > call somewhere in the beginning of nd6_llinfo_settimer(), but there is > a problem. nd6_llinfo_settimer() is called not only when I start ppp, > but at bootup too (at bootup - once, I think that this is due to > initializing lo0 interface, which has a default ipv6 address). Could I > somehow make the kernel not panic at boot time and panic later, when I > call ppp? You may use a flag. Touch /var/run/.boot file. If the flag presents, your panic() doesn't occur. After booting remove the flag and start ppp again. > E.g, how can I know uptime from the kernel mode? WBR -- Boris B. Samorodov, Research Engineer InPharmTech Co, http://www.ipt.ru Telephone & Internet Service Provider From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 07:22:17 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE93E16A41F for ; Thu, 3 Nov 2005 07:22:17 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from linda-5.paradise.net.nz (bm-5a.paradise.net.nz [203.96.152.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E3FD43D45 for ; Thu, 3 Nov 2005 07:22:17 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-1.paradise.net.nz (tclsnelb2-src-1.paradise.net.nz [203.96.152.177]) by linda-5.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IPD00B2ZB54I5@linda-5.paradise.net.nz> for freebsd-current@freebsd.org; Thu, 03 Nov 2005 20:22:16 +1300 (NZDT) Received: from [192.168.1.11] (218-101-28-143.dsl.clear.net.nz [218.101.28.143]) by smtp-1.paradise.net.nz (Postfix) with ESMTP id 287F81D2E24 for ; Thu, 03 Nov 2005 20:22:16 +1300 (NZDT) Date: Thu, 03 Nov 2005 20:22:13 +1300 From: Mark Kirkwood To: freebsd-current@freebsd.org Message-id: <4369BAA5.5040107@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050726) Subject: 6.0-RC1 on Promise SX4060 (SETFEATURES FAILURE, READ timed out) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 07:22:17 -0000 Hi, I am trying to install 6.0-RC1 on a system with a Promise SX4060 (PDC20621) + 4 Maxtor ATA-133 drives (6E040L0). The mobo is a Tyan Thunder LE (S2510). The card appears to be detected ok : atapci2: port 0xe800-0xe8ff,0xe400-0xe4ff, 0xe000-0xe0ff mem 0xfea00000-0xfeafffff,0xfebd8000-0xfebdffff irq 23 at device 3 .0 on pci1 atapci2: rid 0x20 is memory, requested 4 atapci2: Reserved 0x8000 bytes for rid 0x20 type 3 at 0xfebd8000 atapci2: Reserved 0x100000 bytes for rid 0x1c type 3 at 0xfea00000 atapci2: [MPSAFE] atapci2: DIMM size 1024MB @ 0x00000000 but the drive probing fails completely: ad4 : FAILURE - SET FEATURES TRANSFER MODE timed out. ad4 : FAILURE - SET FEATURES RCACHE timed out. ad4 : FAILURE - SET FEATURES WCACHE timed out. ad4 : FAILURE - SET FEATURES SET_MULTI. ad4 : FAILURE - READ timed out (LBA = 80293185) ad4 : FAILURE - READ retrying (0 retries left) LBA = 0 .. ad4 : req = 0xc3b78960 SET FEATURES SET TRANSFER MODE semaphore timeout !!DANGER WILL ROBINSON!! .. .. (hand copied as I don't have a serial console) These drives seem ok (work with a TX2000 and a 2Ware 7506). In order to eliminate the drives, I have tried a seagate ST340014A as well - same result. Any suggestions about how to proceed (I would like to get this going) Cheers Mark From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 07:26:21 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E934C16A41F for ; Thu, 3 Nov 2005 07:26:21 +0000 (GMT) (envelope-from delphij@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 828C843D46 for ; Thu, 3 Nov 2005 07:26:21 +0000 (GMT) (envelope-from delphij@gmail.com) Received: by xproxy.gmail.com with SMTP id i27so546537wxd for ; Wed, 02 Nov 2005 23:26:20 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Ixj+oFeZKcAQoaN5+8s2b2th/81TwrtDbRSnncD4+A7MUvzyKjdSnTBZKndXasI3qqeaKFkWkxVddzTejlnJzrPEo/045mIuIju9GGajXaK79P9vll3mJ6tddHmROLiCOSKg6G2pzJZWDgpYUcQkIwrdm/qI/2gyBgaEhjzY5SA= Received: by 10.65.20.5 with SMTP id x5mr414187qbi; Wed, 02 Nov 2005 23:26:20 -0800 (PST) Received: by 10.65.191.18 with HTTP; Wed, 2 Nov 2005 23:26:20 -0800 (PST) Message-ID: Date: Thu, 3 Nov 2005 15:26:20 +0800 From: Xin LI To: Mark Kirkwood In-Reply-To: <4369BAA5.5040107@paradise.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline References: <4369BAA5.5040107@paradise.net.nz> Cc: freebsd-current@freebsd.org Subject: Re: 6.0-RC1 on Promise SX4060 (SETFEATURES FAILURE, READ timed out) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 07:26:22 -0000 T24gMTEvMy8wNSwgTWFyayBLaXJrd29vZCA8bWFya2lyQHBhcmFkaXNlLm5ldC5uej4gd3JvdGU6 Cj4gSGksIEkgYW0gdHJ5aW5nIHRvIGluc3RhbGwgNi4wLVJDMSBvbiBhIHN5c3RlbSB3aXRoIGEg UHJvbWlzZSBTWDQwNjAKPiAoUERDMjA2MjEpICsgNCBNYXh0b3IgQVRBLTEzMyBkcml2ZXMgKDZF MDQwTDApLiBUaGUgbW9ibyBpcyBhIFR5YW4KPiBUaHVuZGVyIExFIChTMjUxMCkuCltzbmlwXQo+ IFRoZXNlIGRyaXZlcyBzZWVtIG9rICh3b3JrIHdpdGggYSBUWDIwMDAgYW5kIGEgMldhcmUgNzUw NikuCj4KPiBJbiBvcmRlciB0byBlbGltaW5hdGUgdGhlIGRyaXZlcywgSSBoYXZlIHRyaWVkIGEg c2VhZ2F0ZSBTVDM0MDAxNEEgYXMKPiB3ZWxsIC0gc2FtZSByZXN1bHQuCj4KPiBBbnkgc3VnZ2Vz dGlvbnMgYWJvdXQgaG93IHRvIHByb2NlZWQgKEkgd291bGQgbGlrZSB0byBnZXQgdGhpcyBnb2lu ZykKCldvdWxkIHlvdSBwbGVhc2UgY29uc2lkZXIgdHJ5aW5nICJzYWZlIG1vZGUiLCBpZiB5b3Ug ZGlkIG5vdCB0cmllZD8gCklmIHBvc3NpYmxlLCBwbGVhc2UgYWxzbyBjb25zaWRlciBnaXZlIDUu NC1SRUxFQVNFIGEgdHJ5IHRvIHNlZSBpZgp0aGlzIGlzIGEgcmVncmVzc2lvbi4KCkNoZWVycywK From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 07:35:06 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B3AA16A41F for ; Thu, 3 Nov 2005 07:35:06 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from linda-3.paradise.net.nz (bm-3a.paradise.net.nz [203.96.152.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FB0D43D45 for ; Thu, 3 Nov 2005 07:35:05 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-3.paradise.net.nz (tclsnelb2-src-1.paradise.net.nz [203.96.152.177]) by linda-3.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IPD003P8BQGVR@linda-3.paradise.net.nz> for freebsd-current@freebsd.org; Thu, 03 Nov 2005 20:35:04 +1300 (NZDT) Received: from [192.168.1.11] (218-101-28-143.dsl.clear.net.nz [218.101.28.143]) by smtp-3.paradise.net.nz (Postfix) with ESMTP id 69C909E130; Thu, 03 Nov 2005 20:35:04 +1300 (NZDT) Date: Thu, 03 Nov 2005 20:35:02 +1300 From: Mark Kirkwood In-reply-to: To: Xin LI Message-id: <4369BDA6.2050008@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050726) References: <4369BAA5.5040107@paradise.net.nz> Cc: freebsd-current@freebsd.org Subject: Re: 6.0-RC1 on Promise SX4060 (SETFEATURES FAILURE, READ timed out) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 07:35:06 -0000 Xin LI wrote: > On 11/3/05, Mark Kirkwood wrote: > >>Hi, I am trying to install 6.0-RC1 on a system with a Promise SX4060 >>(PDC20621) + 4 Maxtor ATA-133 drives (6E040L0). The mobo is a Tyan >>Thunder LE (S2510). > > [snip] > > Would you please consider trying "safe mode", if you did not tried? > If possible, please also consider give 5.4-RELEASE a try to see if > this is a regression. > Hadn't thought of trying 5.4 - excellent suggestion - will do! Cheers Mark From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 08:36:07 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32FF916A41F; Thu, 3 Nov 2005 08:36:07 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9618943D48; Thu, 3 Nov 2005 08:36:06 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.250] (ppp-71-139-0-107.dsl.snfc21.pacbell.net [71.139.0.107]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id jA38a3xq028698 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 3 Nov 2005 00:36:04 -0800 Message-ID: <4369CBCA.7050501@root.org> Date: Thu, 03 Nov 2005 00:35:22 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Munehiro Matsuda References: <971FCB6690CD0E4898387DBF7552B90E0346CAFB@orsmsx403.amr.corp.intel.com> <20051103.094643.74756456.haro@h4.dion.ne.jp> <436961FD.3040605@root.org> <20051103.122404.74756296.haro@h4.dion.ne.jp> In-Reply-To: <20051103.122404.74756296.haro@h4.dion.ne.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org, robert.moore@intel.com, jkim@freebsd.org Subject: Re: Panic on boot with new ACPI-CA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 08:36:07 -0000 Munehiro Matsuda wrote: > Hi Nate, > > Thanks for memguard tip. > But now, I'm confuse with the outcome. :-( > > 1) With memguard enabled, system boots up just fine, even acpi compiled > into kernel or loaded as a module. > > 2) Without memguard, but with acpi compiled into kernel, system boots up > past the reported point. > But this time, npanics with page fault further into the booting process, > just as Marcel reported yesterday. > > 3) Without memguard and with acpi loaded as module, system panics as > reported in my original mail. > > So, the memguard works as workaround for me, but not as debuging aid. ;-P > > If you need more info or any other way to debug, please let me know. Judging from your dmesg, the use after free happens somewhere just after probing of PCI LNKH. Something likely changed in how acpi-ca deals with pci links or resources (due to your failure message on PRT_). Since memguard affects the malloc pool enough to hide the problem, you'll have to trace it down differently with memguard disabled. My procedure for hunting these problems is a little more time consuming but nearly always works. Compile in DDB and type "boot -d" at the loader prompt. This will pop into the debugger early. Then type "w 0xc1ee1600" to set a watchpoint for this address. Now you'll break to the debugger each time this memory is written to. Type "tr" to get a trace each time you hit the debugger and see what call stack was the very last one to write to that region, just before the panic. -Nate > From: Nate Lawson > Date: Wed, 02 Nov 2005 17:03:57 -0800 > ::As I mentioned to Jung-uk, the problem is likely an error in acpi-ca > ::modifying memory after it has freed it. The way to track this down is > ::to enable memguard(9). See the man page for info. You need to add > ::options DEBUG_MEMGUARD to your kernel, set the malloc type to watch to > ::M_ACPICA, and rebuild your kernel and modules. Memguard sets page > ::permissions so we can catch the culprit who is modifying the memory. > :: > ::http://www.freebsd.org/cgi/man.cgi?query=memguard&apropos=0&sektion=0&manpath=FreeBSD+6.0-current&format=html > :: > ::If you need a kernel to keep running in production while debugging the > ::other kernel, disable options INVARIANTS to get rid of the diagnostic panic. > :: > ::-Nate From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 08:56:24 2005 Return-Path: X-Original-To: current@FreeBSD.ORG Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D29C16A41F; Thu, 3 Nov 2005 08:56:24 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vbook.fbsd.ru (swsoft-mipt-nat.sw.ru [195.214.233.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 091EC43D46; Thu, 3 Nov 2005 08:56:23 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.54 (FreeBSD)) id 1EXatR-000EfS-QB; Thu, 03 Nov 2005 11:56:21 +0300 From: Vladimir Grebenschikov To: "Matthew N. Dodd" In-Reply-To: <20050323154642.J37251@sasami.jurai.net> References: <1110800717.1296.19.camel@localhost> <200503231411.46948.jhb@FreeBSD.org> <1111610025.1471.6.camel@localhost> <20050323154642.J37251@sasami.jurai.net> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Thu, 03 Nov 2005 11:56:20 +0300 Message-Id: <1131008180.1295.10.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: "current@freebsd.org" , John Baldwin , freebsd-mobile@FreeBSD.ORG Subject: Re: Reattach/redetect allways connected umass device - is it possible ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 08:56:24 -0000 =F7 =D3=D2, 23/03/2005 =D7 15:48 -0500, Matthew N. Dodd =D0=C9=DB=C5=D4: > You want this: >=20 > ftp://ftp.jurai.net/users/winter/cam-detach.patch >=20 > You will then be able to perform a 'camcontrol detach daX', swap cards,=20 > and run 'camcontrol rescan'. Is there any chance to get this patch commited ? It is useful and I am using it for half year. --=20 Vladimir B. Grebenschikov vova@fbsd.ru From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 09:37:49 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB69A16A41F; Thu, 3 Nov 2005 09:37:49 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from smtp6-g19.free.fr (smtp6-g19.free.fr [212.27.42.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id B92C443D4C; Thu, 3 Nov 2005 09:37:48 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp6-g19.free.fr (Postfix) with ESMTP id A2A91965D; Thu, 3 Nov 2005 10:37:47 +0100 (CET) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.13.3/8.13.3) with ESMTP id jA39bfBl008271; Thu, 3 Nov 2005 10:37:45 +0100 (CET) From: Thierry Herbelot To: freebsd-current@freebsd.org Date: Thu, 3 Nov 2005 10:37:33 +0100 User-Agent: KMail/1.8.2 X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511031037.35130.thierry@herbelot.com> Cc: andre@freebsd.org Subject: Broken NFS ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 09:37:49 -0000 Hello, the latest current kernel seems to have a broken NFS : it can't get a listing for a shared directory (itself hosted on a just recompiled 6-STABLE server) : # ls /files2/netnfs server tfh:/files2: not responding -cvs A pcap trace of the NFS messages is : http://thierry.herbelot.free.fr/nfs-broken/nfs-broken.pcap tfh# tcpdump -n -t -r nfs-broken.pcap reading from file nfs-broken.pcap, link-type EN10MB (Ethernet) IP 192.168.2.12.855699310 > 192.168.2.1.2049: 104 access fh 1056,330756/2 003f IP 192.168.2.1.2049 > 192.168.2.12.855699310: reply ok 120 access c 003f IP 192.168.2.12.855699311 > 192.168.2.1.2049: 104 access fh 1056,330756/2 003f IP 192.168.2.1.2049 > 192.168.2.12.855699311: reply ok 120 access c 003f IP 192.168.2.12.855699312 > 192.168.2.1.2049: 100 fsstat fh 1056,330756/2 IP 192.168.2.1.2049 > 192.168.2.12.855699312: reply ok 168 fsstat tbytes 161358067712 fbytes 9270075392 abytes 2815754240 IP 192.168.2.12.855699313 > 192.168.2.1.2049: 104 access fh 1056,330756/10633216 003f IP 192.168.2.1.2049 > 192.168.2.12.855699313: reply ok 120 access c 003f IP 192.168.2.12.855699314 > 192.168.2.1.2049: 104 access fh 1056,330756/2 003f IP 192.168.2.1.2049 > 192.168.2.12.855699314: reply ok 120 access c 003f IP 192.168.2.12.855699315 > 192.168.2.1.2049: 104 access fh 1056,330756/2 003f IP 192.168.2.1.2049 > 192.168.2.12.855699315: reply ok 120 access c 003f IP 192.168.2.12.855699316 > 192.168.2.1.2049: 100 fsstat fh 1056,330756/2 IP 192.168.2.1.2049 > 192.168.2.12.855699316: reply ok 168 fsstat tbytes 161358067712 fbytes 9270075392 abytes 2815754240 IP 192.168.2.12.855699317 > 192.168.2.1.2049: 112 lookup fh 1056,330756/2 "net-cvs" IP 192.168.2.1.2049 > 192.168.2.12.855699317: reply ok 236 lookup fh 1056,330756/18202624 IP 192.168.2.12.855699317 > 192.168.2.1.2049: 112 lookup fh 1056,330756/2 "net-cvs" IP 192.168.2.1.2049 > 192.168.2.12.855699317: reply ok 236 lookup fh 1056,330756/18202624 IP 192.168.2.12.855699317 > 192.168.2.1.2049: 112 lookup fh 1056,330756/2 "net-cvs" IP 192.168.2.1.2049 > 192.168.2.12.855699317: reply ok 236 lookup fh 1056,330756/18202624 IP 192.168.2.12.855699317 > 192.168.2.1.2049: 112 lookup fh 1056,330756/2 "net-cvs" IP 192.168.2.1.2049 > 192.168.2.12.855699317: reply ok 236 lookup fh 1056,330756/18202624 IP 192.168.2.12.855699317 > 192.168.2.1.2049: 112 lookup fh 1056,330756/2 "net-cvs" IP 192.168.2.1.2049 > 192.168.2.12.855699317: reply ok 236 lookup fh 1056,330756/18202624 IP 192.168.2.12.855699317 > 192.168.2.1.2049: 112 lookup fh 1056,330756/2 "net-cvs" IP 192.168.2.1.2049 > 192.168.2.12.855699317: reply ok 236 lookup fh 1056,330756/18202624 IP 192.168.2.12.855699317 > 192.168.2.1.2049: 112 lookup fh 1056,330756/2 "net-cvs" IP 192.168.2.1.2049 > 192.168.2.12.855699317: reply ok 236 lookup fh 1056,330756/18202624 IP 192.168.2.12.855699317 > 192.168.2.1.2049: 112 lookup fh 1056,330756/2 "net-cvs" IP 192.168.2.1.2049 > 192.168.2.12.855699317: reply ok 236 lookup fh 1056,330756/18202624 IP 192.168.2.12.855699317 > 192.168.2.1.2049: 112 lookup fh 1056,330756/2 "net-cvs" IP 192.168.2.1.2049 > 192.168.2.12.855699317: reply ok 236 lookup fh 1056,330756/18202624 IP 192.168.2.12.855699317 > 192.168.2.1.2049: 112 lookup fh 1056,330756/2 "net-cvs" IP 192.168.2.1.2049 > 192.168.2.12.855699317: reply ok 236 lookup fh 1056,330756/18202624 IP 192.168.2.12.855699317 > 192.168.2.1.2049: 112 lookup fh 1056,330756/2 "net-cvs" IP 192.168.2.1.2049 > 192.168.2.12.855699317: reply ok 236 lookup fh 1056,330756/18202624 the kernel needs 10 tries to read the directory listing ? the kernel has been built via the make buildworld/make buildkernel procedure (the kernel is a straight GENERIC : FreeBSD XXX 7.0-CURRENT FreeBSD 7.0-CURRENT #65: Thu Nov 3 09:22:29 CET 2005 ZZZ@XXX:/files1/obj/files1/src/sys/GENERIC i386) the latest diffs I have in the non-working kernel include : (kernel.good.ident are all the idents for the last working kernel, kernel.ident is the same for the first non-working kernel) multi-cur# diff kernel.good.ident kernel.ident 1c1 < /boot/kernel.good/kernel: --- > /boot/kernel/kernel: 336c336 < src/sys/kern/kern_mbuf.c,v 1.11 2005/09/27 20:28:43 rwatson Exp $ --- > src/sys/kern/kern_mbuf.c,v 1.12 2005/11/02 16:20:35 andre Exp $ 410c410 < src/sys/kern/uipc_mbuf.c,v 1.155 2005/08/30 21:31:42 andre Exp $ --- > src/sys/kern/uipc_mbuf.c,v 1.156 2005/11/02 16:20:35 andre Exp $ 413,414c413,414 < src/sys/kern/uipc_socket.c,v 1.251 2005/10/30 19:44:38 rwatson Exp $ < src/sys/kern/uipc_socket2.c,v 1.149 2005/10/30 19:44:39 rwatson Exp $ --- > src/sys/kern/uipc_socket.c,v 1.252 2005/11/02 13:46:31 andre Exp $ > src/sys/kern/uipc_socket2.c,v 1.150 2005/11/02 13:46:31 andre Exp $ 463c463 < src/sys/net80211/ieee80211_freebsd.c,v 1.8 2005/08/08 18:46:35 sam Exp $ --- > src/sys/net80211/ieee80211_freebsd.c,v 1.9 2005/11/02 13:46:31 andre Exp $ 467c467 < src/sys/net80211/ieee80211_output.c,v 1.34 2005/08/10 16:22:29 sam Exp $ --- > src/sys/net80211/ieee80211_output.c,v 1.35 2005/11/02 13:46:31 andre Exp $ I have re-synced the sources and recompiled the kernel to avoid a partial commit, but the bug is still there. TfH PS : kernel modules loaded : # kldstat Id Refs Address Size Name 1 6 0xc0400000 698da0 kernel 2 1 0xc0a99000 70ec snd_es137x.ko 3 6 0xc0aa1000 23aa4 sound.ko 4 1 0xc0ac5000 b59c snd_mss.ko 5 1 0xc0ad1000 2d14 joy.ko 6 1 0xc0ad4000 147c0 geom_mirror.ko PS2 : CC'd to andre@ as he was the latest commiter on the kernel From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 09:55:10 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B81B16A41F; Thu, 3 Nov 2005 09:55:10 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0534943D46; Thu, 3 Nov 2005 09:55:09 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 8A3521FFAD5; Thu, 3 Nov 2005 10:55:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 196AE1FFDBC; Thu, 3 Nov 2005 10:55:05 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 33CD2158B4; Thu, 3 Nov 2005 09:52:23 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 296C9157A8; Thu, 3 Nov 2005 09:52:24 +0000 (UTC) Date: Thu, 3 Nov 2005 09:52:24 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Mauritz Sundell In-Reply-To: <2156358.1131010803308.JavaMail.tomcat@pne-ps1-sn2> Message-ID: References: <2156358.1131010803308.JavaMail.tomcat@pne-ps1-sn2> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-current@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: CURRENT Safemode does not boot but ACPI-mode does X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 09:55:10 -0000 On Thu, 3 Nov 2005, Mauritz Sundell wrote: > 27 october I cvsuped and build kernel and world > since then I cant boot without ACPI > when I boot without there looks to be problems with resource- > allocations > drivers cannot attach, cannot map interrupt, and finally Mount root > fail > due to no harddisk found. > > My previous kernel was from the 26th october. > > Im running CURRENT on an HP Pavilion zv5000 (laptop) with amd64. > > Do someone have any tips where I should look? There had been more changes in that timeframe. Try re-adding device atpic to your kernel config file if it's missing. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 11:26:57 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8ABA516A41F; Thu, 3 Nov 2005 11:26:57 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF02B43D46; Thu, 3 Nov 2005 11:26:56 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.4/8.13.4) with ESMTP id jA3BQtTt049776; Thu, 3 Nov 2005 06:26:56 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id jA3BQthQ008633; Thu, 3 Nov 2005 06:26:55 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id A264C7302F; Thu, 3 Nov 2005 06:26:55 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051103112655.A264C7302F@freebsd-current.sentex.ca> Date: Thu, 3 Nov 2005 06:26:55 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 11:26:57 -0000 TB --- 2005-11-03 10:19:16 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-11-03 10:19:16 - starting HEAD tinderbox run for amd64/amd64 TB --- 2005-11-03 10:19:16 - cleaning the object tree TB --- 2005-11-03 10:19:34 - checking out the source tree TB --- 2005-11-03 10:19:34 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2005-11-03 10:19:34 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-11-03 10:26:30 - building world (CFLAGS=-O2 -pipe) TB --- 2005-11-03 10:26:30 - cd /src TB --- 2005-11-03 10:26:30 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -I/src/usr.sbin/acpi/acpiconf/../../../sys -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -o acpiconf acpiconf.o gzip -cn /src/usr.sbin/acpi/acpiconf/acpiconf.8 > acpiconf.8.gz ===> usr.sbin/acpi/acpidb (all) cc -O2 -pipe -DACPI_APPLICATION -DACPI_DEBUG_OUTPUT -DACPI_DEBUGGER -DACPI_DISASSEMBLER -I/src/usr.sbin/acpi/acpidb/../../../sys -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/usr.sbin/acpi/acpidb/acpidb.c cc -O2 -pipe -DACPI_APPLICATION -DACPI_DEBUG_OUTPUT -DACPI_DEBUGGER -DACPI_DISASSEMBLER -I/src/usr.sbin/acpi/acpidb/../../../sys -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/osunixxf.c cc -O2 -pipe -DACPI_APPLICATION -DACPI_DEBUG_OUTPUT -DACPI_DEBUGGER -DACPI_DISASSEMBLER -I/src/usr.sbin/acpi/acpidb/../../../sys -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/dbcmds.c /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/dbcmds.c: In function `AcpiDbBusWalk': /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/dbcmds.c:1741: warning: dereferencing type-punned pointer will break strict-aliasing rules *** Error code 1 Stop in /src/usr.sbin/acpi/acpidb. *** Error code 1 Stop in /src/usr.sbin/acpi. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-03 11:26:55 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-03 11:26:55 - ERROR: failed to build world TB --- 2005-11-03 11:26:55 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 11:27:56 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3DB616A41F for ; Thu, 3 Nov 2005 11:27:56 +0000 (GMT) (envelope-from toxahost@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3099243D48 for ; Thu, 3 Nov 2005 11:27:53 +0000 (GMT) (envelope-from toxahost@gmail.com) Received: by wproxy.gmail.com with SMTP id i4so45690wra for ; Thu, 03 Nov 2005 03:27:53 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=a7Ysk7hyJITCQMZHXhVr2IOX22XvyOe8XITO9FDO+TUw2qBT2bEeedIGouq5sJMxwth7d2XsWcO2qOxgVOU7LkcqJqfezsX4MgjOyBo8AI74MYP2ipo4wonmf1SYnJwub2Fd+IrlTpf50y0tRABPy0yTyjbOyehz/gawmMJsDpQ= Received: by 10.64.242.2 with SMTP id p2mr585773qbh; Thu, 03 Nov 2005 03:21:45 -0800 (PST) Received: by 10.64.209.14 with HTTP; Thu, 3 Nov 2005 03:21:45 -0800 (PST) Message-ID: Date: Thu, 3 Nov 2005 14:21:45 +0300 From: Anton Karpov To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: where is the BEASTIE??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 11:27:57 -0000 I've just cvsuped and rebuilt my system from 6.0-RC1 to 6.0-STABLE, and I've noticed "FreeBSD" ASCII logo in bootloader menu instead of good old red Beastie... How can I take the Beastie back? ;) From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 11:31:38 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1E3116A41F for ; Thu, 3 Nov 2005 11:31:38 +0000 (GMT) (envelope-from taras.savchuk@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EE6743D48 for ; Thu, 3 Nov 2005 11:31:38 +0000 (GMT) (envelope-from taras.savchuk@gmail.com) Received: by zproxy.gmail.com with SMTP id 14so151139nzn for ; Thu, 03 Nov 2005 03:31:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=ezGBtuF6vZUDCQiecjF4KiFd/aw8vEeYMArWicJfZYUDDxosTVbhRptsWYLz23HChvBk0J0tlbxBNQ2VupcU3qU2Bm6ixP4N+Lq5PsG/39tvl+d91IOyQD5J4qqbdD+8bY7HDc7qggOfxUuFqvotT6hKQdgK7f2xdqkfVxPJA2k= Received: by 10.65.100.10 with SMTP id c10mr576713qbm; Thu, 03 Nov 2005 03:25:07 -0800 (PST) Received: by 10.65.160.16 with HTTP; Thu, 3 Nov 2005 03:25:07 -0800 (PST) Message-ID: <84099c3d0511030325q6d1df92ag77310ff1b03a2d15@mail.gmail.com> Date: Thu, 3 Nov 2005 14:25:07 +0300 From: Taras Savchuk To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: May be a bug in fsck [ after super block crash on 5.4-STABLE ] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 11:31:38 -0000 My SATA HDD with UFS2 crashed. While checking HDD fsck said, that alternate super block at block 32 is not present. In 'man fsck' I saw, that in UFS2 (my file system) alternate super block is usually located in block 160 (For UFS1 - in 32). So the question is: why fsck trying to find alternate superblock in wrong block for UFS2? I can suppose, that fsck dont know file system type (UFS1 or UFS2) while checking, but such assumption seems to be wrong. From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 11:35:35 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDB3416A41F for ; Thu, 3 Nov 2005 11:35:35 +0000 (GMT) (envelope-from oleg@core.zp.ua) Received: from core.zp.ua (core.zp.ua [193.108.112.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 856B943D4C for ; Thu, 3 Nov 2005 11:35:34 +0000 (GMT) (envelope-from oleg@core.zp.ua) Received: from core.zp.ua (oleg@localhost [127.0.0.1]) by core.zp.ua with ESMTPœ id jA3BgY7d095769 for ; Thu, 3 Nov 2005 13:42:35 +0200 (EET) (envelope-from oleg@core.zp.ua)œ Received: (from oleg@localhost) by core.zp.ua id jA3BgYov095768 for freebsd-current@freebsd.org; Thu, 3 Nov 2005 13:42:34 +0200 (EET) Date: Thu, 3 Nov 2005 13:42:34 +0200 From: "Oleg V. Nauman" To: freebsd-current@freebsd.org Message-ID: <20051103114234.GB1716@core.zp.ua> Mail-Followup-To: freebsd-current@freebsd.org References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="3lcZGd9BuhuYXNfi" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i Subject: Re: where is the BEASTIE??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 11:35:36 -0000 --3lcZGd9BuhuYXNfi Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 03, 2005 at 02:21:45PM +0300, Anton Karpov wrote: > I've just cvsuped and rebuilt my system from 6.0-RC1 to 6.0-STABLE, > and I've noticed "FreeBSD" ASCII logo in bootloader menu instead of > good old red Beastie... How can I take the Beastie back? ;) echo 'loader_logo=3D"beastie"' >> /boot/loader.conf --=20 NO37-RIPE --3lcZGd9BuhuYXNfi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: PGP 6.5.8 iQCVAwUBQ2n3ovC2y8Tb/5DvAQFp+AQAmMP78BDxMFYqm+8VGWBNbfvbCSqQD2Ox rTzD4H87SVoYsoC3jbKBQTCfb0Tv0d2jdhpW7MEOBTYT/rAS/PWG1oSrldhtvf41 U9kjJSr+EKBeIZZd9zG2p1B+xM1O1oU1Ny1rmXGNAhHUJsmN2gtwlNhB0LDbuNZn 74QYI5rONy8= =z5o/ -----END PGP SIGNATURE----- --3lcZGd9BuhuYXNfi-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 11:47:22 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20FDC16A41F for ; Thu, 3 Nov 2005 11:47:22 +0000 (GMT) (envelope-from toxahost@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F47A43D45 for ; Thu, 3 Nov 2005 11:47:19 +0000 (GMT) (envelope-from toxahost@gmail.com) Received: by wproxy.gmail.com with SMTP id 57so215111wri for ; Thu, 03 Nov 2005 03:47:18 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=mY9wm5ap7IpBFHsk988c9+7+YoHEpjGGTsFc/1JT8E38Ba6fw6ieVhhrm+N6JZCN4d6Ieuwqb5YV51T15y7GhO5BDAGcDzBcJnFpZQTZ286ec7+puOcR8TQALbJhPLPwxXucxnUuIbndtg2yyQkS7XTFicIw5Y60Du0DtqH7J4s= Received: by 10.65.215.4 with SMTP id s4mr589912qbq; Thu, 03 Nov 2005 03:47:18 -0800 (PST) Received: by 10.64.209.14 with HTTP; Thu, 3 Nov 2005 03:47:18 -0800 (PST) Message-ID: Date: Thu, 3 Nov 2005 14:47:18 +0300 From: Anton Karpov To: freebsd-current@freebsd.org In-Reply-To: <20051103114234.GB1716@core.zp.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051103114234.GB1716@core.zp.ua> Subject: Re: where is the BEASTIE??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 11:47:22 -0000 great, thanks > echo 'loader_logo=3D"beastie"' >> /boot/loader.conf From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 12:25:32 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E02B16A420 for ; Thu, 3 Nov 2005 12:25:32 +0000 (GMT) (envelope-from taras.savchuk@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id A659843D5C for ; Thu, 3 Nov 2005 12:25:29 +0000 (GMT) (envelope-from taras.savchuk@gmail.com) Received: by xproxy.gmail.com with SMTP id t10so638966wxc for ; Thu, 03 Nov 2005 04:25:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=jb+a8cWmmOeUKXFw90YH18SFjK8HgiYM/YgC0Pttx5x4z33dDS2ZNK/VqrzhETyWfgTgwzPFRXhIJnkxKukF+C6IlCroiEU23zjP1hhQ5f1WIFRsh3LZxYzVGPBxufJgk6TKeVtnJ9yvExESSPg7K8UGvAdyIUCcrw6haa+jZM0= Received: by 10.65.147.10 with SMTP id z10mr617473qbn; Thu, 03 Nov 2005 04:25:28 -0800 (PST) Received: by 10.65.160.16 with HTTP; Thu, 3 Nov 2005 04:25:28 -0800 (PST) Message-ID: <84099c3d0511030425q3592a288he254cb5f97f976b6@mail.gmail.com> Date: Thu, 3 Nov 2005 15:25:28 +0300 From: Taras Savchuk To: freebsd-current@freebsd.org In-Reply-To: <84099c3d0511030325q6d1df92ag77310ff1b03a2d15@mail.gmail.com> MIME-Version: 1.0 References: <84099c3d0511030325q6d1df92ag77310ff1b03a2d15@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: May be a bug in fsck [ after super block crash on 5.4-STABLE ] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 12:25:32 -0000 On 11/3/05, Taras Savchuk wrote: > > My SATA HDD with UFS2 crashed. While checking HDD fsck said, that > alternate super block at block 32 is not present. In 'man fsck' I saw, th= at > in UFS2 (my file system) alternate super block is usually located in bloc= k > 160 (For UFS1 - in 32). So the question is: why fsck trying to find > alternate superblock in wrong block for UFS2? I can suppose, that fsck do= nt > know file system type (UFS1 or UFS2) while checking, but such assumption > seems to be wrong. PS: With '-b 160' option fsck done work well. From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 12:33:25 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 874F616A41F; Thu, 3 Nov 2005 12:33:25 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25A5D43D45; Thu, 3 Nov 2005 12:33:25 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id jA3CXNDq093528; Thu, 3 Nov 2005 07:33:23 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id jA3CXOka069150; Thu, 3 Nov 2005 07:33:24 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id CDDAA7302F; Thu, 3 Nov 2005 07:33:23 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051103123323.CDDAA7302F@freebsd-current.sentex.ca> Date: Thu, 3 Nov 2005 07:33:23 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 12:33:25 -0000 TB --- 2005-11-03 11:26:55 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-11-03 11:26:55 - starting HEAD tinderbox run for i386/i386 TB --- 2005-11-03 11:26:55 - cleaning the object tree TB --- 2005-11-03 11:27:18 - checking out the source tree TB --- 2005-11-03 11:27:18 - cd /tinderbox/HEAD/i386/i386 TB --- 2005-11-03 11:27:18 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-11-03 11:33:52 - building world (CFLAGS=-O2 -pipe) TB --- 2005-11-03 11:33:52 - cd /src TB --- 2005-11-03 11:33:52 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything [...] cc -O2 -pipe -I/src/usr.sbin/acpi/acpiconf/../../../sys -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -o acpiconf acpiconf.o gzip -cn /src/usr.sbin/acpi/acpiconf/acpiconf.8 > acpiconf.8.gz ===> usr.sbin/acpi/acpidb (all) cc -O2 -pipe -DACPI_APPLICATION -DACPI_DEBUG_OUTPUT -DACPI_DEBUGGER -DACPI_DISASSEMBLER -I/src/usr.sbin/acpi/acpidb/../../../sys -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/usr.sbin/acpi/acpidb/acpidb.c cc -O2 -pipe -DACPI_APPLICATION -DACPI_DEBUG_OUTPUT -DACPI_DEBUGGER -DACPI_DISASSEMBLER -I/src/usr.sbin/acpi/acpidb/../../../sys -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/osunixxf.c cc -O2 -pipe -DACPI_APPLICATION -DACPI_DEBUG_OUTPUT -DACPI_DEBUGGER -DACPI_DISASSEMBLER -I/src/usr.sbin/acpi/acpidb/../../../sys -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/dbcmds.c /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/dbcmds.c: In function `AcpiDbBusWalk': /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/dbcmds.c:1741: warning: dereferencing type-punned pointer will break strict-aliasing rules *** Error code 1 Stop in /src/usr.sbin/acpi/acpidb. *** Error code 1 Stop in /src/usr.sbin/acpi. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-03 12:33:23 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-03 12:33:23 - ERROR: failed to build world TB --- 2005-11-03 12:33:23 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 12:40:36 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCF8C16A41F; Thu, 3 Nov 2005 12:40:36 +0000 (GMT) (envelope-from ceri@submonkey.net) Received: from shrike.submonkey.net (cpc2-cdif2-3-1-cust208.cdif.cable.ntl.com [82.31.78.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5503443D45; Thu, 3 Nov 2005 12:40:34 +0000 (GMT) (envelope-from ceri@submonkey.net) Received: from ceri by shrike.submonkey.net with local (Exim 4.54 (FreeBSD)) id 1EXeOJ-000PY8-N1; Thu, 03 Nov 2005 12:40:27 +0000 Date: Thu, 3 Nov 2005 12:40:27 +0000 From: Ceri Davies To: Brooks Davis , bushman@rsu.ru Message-ID: <20051103124027.GE29387@submonkey.net> Mail-Followup-To: Ceri Davies , Brooks Davis , bushman@rsu.ru, hackers@FreeBSD.org, current@FreeBSD.org References: <20051102001507.GB14638@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rE45P3aZNSuYx5ND" Content-Disposition: inline In-Reply-To: <20051102001507.GB14638@odin.ac.hmc.edu> X-PGP: finger ceri@FreeBSD.org User-Agent: Mutt/1.5.11 Sender: Ceri Davies Cc: hackers@FreeBSD.org, current@FreeBSD.org Subject: Re: nsswitch reviewer wanted X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 12:40:37 -0000 --rE45P3aZNSuYx5ND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In the list that shall not be cc'd to, on Tue, Nov 01, 2005 at 04:15:07PM -0800, Brooks Davis wrote: > Michael Bushkov disk some interesting work for use under the Google > Summer of Code and I'd like to see the appropriate parts committed. > Unfortunately, this isn't an area I have great depths of knowledge so > I'm hoping someone one else is interested in working on this. I realise that you weren't asking for comments, but I took a quick look at http://www.rsu.ru/~bushman/nsswitch_cached/nss_cached.patch and have some. I'll send this to the original lists too. o There aren't nearly enough comments. Granted, I'm not a C aficionado, but it's ~ line 3200 of that patch before we come to a new non-trivial comment, and there aren't many after that. o cached/config.c has magic numbers in create_def_configuration_entry(), which probably belong as #defines in config.h instead. I'm not sure what style(9) says about that though, so am happy to be ignored. o There is a single mention of a ssh_hostkeys cache in include/nsswitch.h, and no code to implement it. o On line 15448, there is a whitespace nit. Also, in this area, are we sure that there is no benefit in continuing to key by euid/egid if perform_actual_lookup is enabled; can we send the euid/egid with the lookup request? o A user should be able to invalidate one of their caches (e.g., "cached -i hosts" to flush their hosts cache). Root should be able to do it for all users with a single command (e.g., "cached -I hosts" to flush all hosts caches). o The manual for cached.conf is unclear over whether it's OK to name an "unknown" cache in cached.conf. o The location of cached.conf is defaulted to /usr/local/etc in cached/cached.c and should be changed on commit. Ceri --=20 Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. -- Einstein (attrib.) --rE45P3aZNSuYx5ND Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDagU7ocfcwTS3JF8RAqJkAKCmjV5v4UrUzWyCsJ9i/8u+zXZGAgCdHgCJ 0KhNqHhqRKr6oXxXBa/qtFE= =tJO2 -----END PGP SIGNATURE----- --rE45P3aZNSuYx5ND-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 13:06:32 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B125C16A41F; Thu, 3 Nov 2005 13:06:32 +0000 (GMT) (envelope-from bushman@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EAA743D5D; Thu, 3 Nov 2005 13:06:28 +0000 (GMT) (envelope-from bushman@rsu.ru) Received: from [195.208.252.201] (celsius.cc.rsu.ru [195.208.252.201]) by mail.r61.net (8.13.4/8.13.4) with ESMTP id jA3D6QNu067009; Thu, 3 Nov 2005 16:06:26 +0300 (MSK) (envelope-from bushman@rsu.ru) Message-ID: <436A0C73.3010405@rsu.ru> Date: Thu, 03 Nov 2005 16:11:15 +0300 From: Michael Bushkov User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051018) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ceri Davies References: <20051102001507.GB14638@odin.ac.hmc.edu> <20051103124027.GE29387@submonkey.net> In-Reply-To: <20051103124027.GE29387@submonkey.net> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on asterix.r61.net X-Virus-Status: Clean Cc: hackers@FreeBSD.org, current@FreeBSD.org Subject: Re: nsswitch reviewer wanted X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 13:06:32 -0000 Hello, Ceri! Ceri Davies wrote: >I realise that you weren't asking for comments, but I took a quick look >at http://www.rsu.ru/~bushman/nsswitch_cached/nss_cached.patch and have >some. I'll send this to the original lists too. > > Thanks for comments! I need them much. >o There aren't nearly enough comments. Granted, I'm not a C aficionado, > but it's ~ line 3200 of that patch before we come to a new non-trivial > comment, and there aren't many after that. > > Ok - I'll comment the code. >o cached/config.c has magic numbers in create_def_configuration_entry(), > which probably belong as #defines in config.h instead. I'm not sure > what style(9) says about that though, so am happy to be ignored. > > Yes, that's right - I guess, the most correct way is to move them to config.h >o There is a single mention of a ssh_hostkeys cache in > include/nsswitch.h, and no code to implement it. > > I've implemented the patch for OpenSSH, which allows it to use nsswitch for the hostkeys. It should be committed by the OpenSSH team. That's why the ssh_hostkeys cache is mentioned in the nsswitch.h. This line can easialy be removed - as it doesn't affect anything. >o On line 15448, there is a whitespace nit. Also, in this area, are we > sure that there is no benefit in continuing to key by euid/egid if > perform_actual_lookup is enabled; can we send the euid/egid with the > lookup request? > > You are talking about passing euid/egid to the underlying nsswitch modules, right? This will require significant changes in these modules, and, as far as I'm converned, won't gain us any benefits. I can't see any benefit of keying by euid/egud when the 'perform_actual_lookups' mode is enabled. By ignoring them, we make the cache common for all users, and no user can poison it - because all requests are made solely by ourselves. If we won't ignore the euid/egid, then for every user, we'll have to make similar requests, this will also affect the cache size. When perform_actual_lookups mode is off, cache should be certainly separated by eud/egid for (basically) security reasons. >o A user should be able to invalidate one of their caches (e.g., > "cached -i hosts" to flush their hosts cache). Root should be able > to do it for all users with a single command (e.g., "cached -I hosts" > to flush all hosts caches). > > > Ok - I'll do that. >o The manual for cached.conf is unclear over whether it's OK to name > an "unknown" cache in cached.conf. > > > I'll corect this. In fact, it's ok to do that. >o The location of cached.conf is defaulted to /usr/local/etc in > cached/cached.c and should be changed on commit. > > > Will be corrected. >Ceri > > -- Michael From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 18:02:17 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC4CB16A41F; Wed, 2 Nov 2005 18:02:17 +0000 (GMT) (envelope-from robert.moore@intel.com) Received: from orsfmr004.jf.intel.com (fmr19.intel.com [134.134.136.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20DCF43D48; Wed, 2 Nov 2005 18:02:16 +0000 (GMT) (envelope-from robert.moore@intel.com) Received: from orsfmr100.jf.intel.com (orsfmr100.jf.intel.com [10.7.209.16]) by orsfmr004.jf.intel.com (8.12.10/8.12.10/d: major-outer.mc,v 1.1 2004/09/17 17:50:56 root Exp $) with ESMTP id jA2I2GL5012278; Wed, 2 Nov 2005 18:02:16 GMT Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206]) by orsfmr100.jf.intel.com (8.12.10/8.12.10/d: major-inner.mc,v 1.2 2004/09/17 18:05:01 root Exp $) with SMTP id jA2I29i7020641; Wed, 2 Nov 2005 18:02:10 GMT Received: from orsmsx332.amr.corp.intel.com ([192.168.65.60]) by orsmsxvs040.jf.intel.com (SAVSMTP 3.1.7.47) with SMTP id M2005110209514931789 ; Wed, 02 Nov 2005 09:51:52 -0800 Received: from orsmsx403.amr.corp.intel.com ([192.168.65.209]) by orsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 2 Nov 2005 09:51:24 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 2 Nov 2005 09:51:23 -0800 Message-ID: <971FCB6690CD0E4898387DBF7552B90E0346CAFB@orsmsx403.amr.corp.intel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Panic on boot with new ACPI-CA (Re: [HEADSUP] ACPI-CA 20051021 import) thread-index: AcXfv3TOuDKSqrsLQjWP0qHokUQQ/wAFogKA From: "Moore, Robert" To: "Munehiro Matsuda" , X-OriginalArrivalTime: 02 Nov 2005 17:51:24.0455 (UTC) FILETIME=[0AA5A370:01C5DFD6] X-Scanned-By: MIMEDefang 2.52 on 10.7.209.16 X-Mailman-Approved-At: Thu, 03 Nov 2005 13:23:19 +0000 Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org Subject: RE: Panic on boot with new ACPI-CA (Re: [HEADSUP] ACPI-CA 20051021 import) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 18:02:18 -0000 If you will send me the acpidump for the machine, I will take a look at the problem. Thanks, Bob > -----Original Message----- > From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- > acpi@freebsd.org] On Behalf Of Munehiro Matsuda > Sent: Wednesday, November 02, 2005 7:08 AM > To: jkim@freebsd.org > Cc: freebsd-acpi@freebsd.org; freebsd-current@freebsd.org > Subject: Panic on boot with new ACPI-CA (Re: [HEADSUP] ACPI-CA 20051021 > import) >=20 > From: Jung-uk Kim > Date: Tue, 1 Nov 2005 17:49:44 -0500 > ::On Tuesday 01 November 2005 05:01 pm, Jung-uk Kim wrote: > ::> ACPI-CA 20051021 will be imported any minute now. I will let you > ::> know when completed. > :: > ::ACPI-CA 20051021 import is completed. > :: > ::Thanks! > :: > ::Jung-uk Kim >=20 > Hi, >=20 > After the import of new ACPI-CA code, I get system panic on boot, > where I used to get "can't fetch resources for \\_SB_.PCI0.FNC0.PRT_ - > AE_BAD_DATA" message. >=20 > If you need more info, please let me know. >=20 > Here's hand written down panic messages. > =3D----------------------------------------------------------------------= - -- > - > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > acpi0: Power Button (fixed) > pci_link0: irq 10 on acpi0 > pci_link1: irq 11 on acpi0 > pci_link2: irq 11 on acpi0 > pci_link3: irq 11 on acpi0 > pci_link4: irq 11 on acpi0 > pci_link5: irq 11 on acpi0 > pci_link6: irq 11 on acpi0 > pci_link7: irq 11 on acpi0 > Memory modified after free 0xc1ee1600(124) val=3Dc @ 0xc1ee1600 > panic: Most recently used by acpica >=20 > cpuid =3D 0 > KDB: enter: panic > [thread pid 0 tid 0] > Stopped at kbt_enter+0x2b: nop > db> bt > Tracing pid 0 tid 0 td 0xc0736780 > kdb_enter(c06cc93e) at kdb_enter+0x2b > panic(c06e42e7,c089c1a8,c06e42b8,c1ee1600,8c) at panic+0x127 > mtrash_ctor(c1ee1600,80,0,1) at mtrash_ctor+0x4d > uma_zalloc_arg(c104a1e0,0,1) at uma_zalloc_arg+0x10f > malloc(68,c089ef00,1,c0c20bb4,c087e562) at malloc+0xb2 > AcpiOsAllocate(68,0,c1ece1e0,4,c0c20be0) at AcpiOsAllocate+0x12 > AcpiUtCallocate(68,10,c089b337,157,c0c20bec) at AcpiUtCallocate+0x16 > AcpiGetObjectInfo(c1ece1e0,c0c20bf8,0,c1ece1e0,ffffffff) at > AcpiGetObjectInfo+0x5b > acpi_MatchHid(0,c089f740,6,c1ece1e0,0) at acpi_MatchHid+0x32 > acpi_probe_child(c1ece1e0,4,c1e9c800,0,0) at acpi_probe_child+0x94 > AcpiNsWalkNamespace(0,ffffffff,64,1,c0883c98) at AcpiNsWalkNamespace+0xa1 > AcpiWalkNamespace(0,ffffffff,64,c0883c98,c1e9c800) at > AcpiWalkNamespace+0x3b > acpi_attach(c1e9c800) at acpi_attach+0x4ff > device_attach(c1e9c800,0,c1e9c800,c1e9d300,0) at device_attach+0x58 > device_probe_and attach(c1e9c800) at device_probe_and_attach+0xe0 > bus_generic_attach(c1e9d300,c1e9d300,c1e9d300,c0c20d40,c0529340) at > bus_generic_attach+0x16 > nexus_attach(c1e9d300) at nexus_attach+0x13 > device_attach(c1e9d300,c0533914,c1e9d300,c0721bb0,c28000) at > device_attach+0x58 > device_probe_and_attach(c1e9d300) at device_probe_and_attach+0xe0 > root_bus_configure(c0c20d88,c04eb592,0,c1ec00,c1e000) at > root_bus_configure+0x16configure(0,c1ec00,c1e000,0,c04392f5) at > configure+0x9 > mi_startup() at mi_startup+0x96 > begin() at begine+0x2c > =3D----------------------------------------------------------------------= - -- > - >=20 > Following is boot message from the last kernel, just before the > import of new code. > =3D----------------------------------------------------------------------= - -- > - > 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 7.0-CURRENT #135: Mon Oct 31 21:33:52 JST 2005 > haro@legacy.ttr.kubota.co.jp:/home/haro/tmp/sys-7/i386/compile/LEGACY > WARNING: WITNESS option enabled, expect reduced performance. > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Pentium(R) M processor 1.10GHz (1097.26-MHz 686-class CPU) > Origin =3D "GenuineIntel" Id =3D 0x6d6 Stepping =3D 6 >=20 > Features=3D0xafe9f9bf AT,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,TM,PBE> > Features2=3D0x180 > real memory =3D 787808256 (751 MB) > avail memory =3D 761475072 (726 MB) > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > acpi0: Power Button (fixed) > pci_link0: irq 10 on acpi0 > pci_link1: irq 11 on acpi0 > pci_link2: irq 11 on acpi0 > pci_link3: irq 11 on acpi0 > pci_link4: irq 11 on acpi0 > pci_link5: irq 11 on acpi0 > pci_link6: irq 11 on acpi0 > pci_link7: irq 11 on acpi0 > can't fetch resources for \\_SB_.PCI0.FNC0.PRT_ - AE_BAD_DATA > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0xd808-0xd80b on acpi0 > cpu0: on acpi0 > est0: on cpu0 > p4tcc0: on cpu0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > pci0: at device 0.1 (no driver attached) > pci0: at device 0.3 (no driver attached) > agp0: port 0xeff8-0xefff > mem 0xd8000000-0xdfffffff,0xd0000000-0xd007ffff irq 10 at device 2.0 on > pci0 > agp0: detected 16252k stolen memory > agp0: aperture size is 128M > pci0: at device 2.1 (no driver attached) > uhci0: port 0xcfe0-0xcfff irq > 10 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 0xcf80-0xcf9f irq > 11 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 0xcf60-0xcf7f irq > 11 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 > ehci0: mem 0xcffffc00- > 0xcfffffff irq 11 at device 29.7 on pci0 > ehci0: [GIANT-LOCKED] > usb3: EHCI version 1.0 > usb3: companion controllers, 2 ports each: usb0 usb1 usb2 > usb3: on ehci0 > usb3: USB revision 2.0 > uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 > uhub3: 6 ports with 6 removable, self powered > pcib1: at device 30.0 on pci0 > pci1: on pcib1 > iwi0: mem 0xcfeff000-0xcfefffff irq 11 at > device 5.0 on pci1 > iwi0: Ethernet address: 00:0e:35:c2:a2:7b > fxp0: port 0xcf00-0xcf3f mem > 0xcfefe000-0xcfefefff irq 11 at device 8.0 on pci1 > miibus0: on fxp0 > inphy0: on miibus0 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > fxp0: Ethernet address: 00:0e:7b:eb:71:23 > cbb0: at device 11.0 on pci1 > cardbus0: on cbb0 > pccard0: <16-bit PCCard bus> on cbb0 > cbb1: at device 11.1 on pci1 > cardbus1: on cbb1 > pccard1: <16-bit PCCard bus> on cbb1 > fwohci0: <1394 Open Host Controller Interface> mem 0xcfefd800- > 0xcfefdfff,0xcfef8000-0xcfefbfff irq 11 at device 11.2 on pci1 > fwohci0: OHCI version 1.10 (ROM=3D1) > fwohci0: No. of Isochronous channels is 4. > fwohci0: EUI64 00:00:39:00:00:72:41:eb > fwohci0: Phy 1394a available S400, 2 ports. > fwohci0: Link S400, max_rec 2048 bytes. > firewire0: on fwohci0 > sbp0: on firewire0 > fwe0: on firewire0 > if_fwe0: Fake Ethernet address: 02:00:39:72:41:eb > fwe0: Ethernet address: 02:00:39:72:41:eb > fwe0: if_start running deferred for Giant > fwohci0: Initiate bus reset > fwohci0: node_id=3D0xc800ffc0, gen=3D1, CYCLEMASTER mode > firewire0: 1 nodes, maxhop <=3D 0, cable IRM =3D 0 (me) > firewire0: bus manager 0 (me) > pci1: at device 11.4 (no driver attached) > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci0: port 0x1f0-0x1f7,0x3f6,0x170- > 0x177,0x376,0xbfa0-0xbfaf irq 11 at device 31.1 on pci0 > ata0: on atapci0 > ata1: on atapci0 > pcm0: port 0xbe00-0xbeff,0xbdc0-0xbdff mem > 0xcfdffe00-0xcfdfffff,0xcfdffd00-0xcfdffdff irq 11 at device 31.5 on pci0 > pcm0: [GIANT-LOCKED] > pcm0: > pci0: at device 31.6 (no driver attached) > acpi_lid0: on acpi0 > battery0: on acpi0 > acpi_button0: on acpi0 > acpi_acad0: on acpi0 > acpi_toshiba0: on acpi0 > acpi_tz0: on acpi0 > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: model Generic PS/2 mouse, device ID 0 > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio0: type 16550A > pmtimer0 on isa0 > orm0: at iomem 0xc0000-0xcffff,0xe0000-0xeffff pnpid > ORM0000 on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=3D0x300> > 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 > Timecounter "TSC" frequency 1097256406 Hz quality 800 > Timecounters tick every 1.000 msec > ad0: 57231MB at ata0-master UDMA100 > acd0: DVDR at ata1-master UDMA33 > pccard1: Allocation failed for cfe 1 > sio4: at port 0x2f8-0x2ff irq 11 function 0 config 2 on > pccard1 > sio4: type 16550A > sio4: unable to activate interrupt in fast mode - using normal mode > Trying to mount root from ufs:/dev/ad0s4a > =3D----------------------------------------------------------------------= - -- > - >=20 > Thanks in advance, > Haro > =3D----------------------------------------------------------------------= - -- > ----- > _ _ Munehiro (haro) Matsuda > -|- /_\ |_|_| Internet Solution Dept., Kubota Graphics Technologies > Inc. > /|\ |_| |_|_| 2-8-8 Shinjuku Shinjuku-ku Tokyo 160-0022, Japan > Tel: +81-3-3225-0767 Fax: +81-3-3225-0740 >=20 >=20 > _______________________________________________ > freebsd-acpi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-acpi > To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Nov 2 18:31:54 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A78116A420; Wed, 2 Nov 2005 18:31:54 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95E6B43D58; Wed, 2 Nov 2005 18:31:51 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by rosebud.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id jA2IVRRw031183; Wed, 2 Nov 2005 20:31:49 +0200 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id jA2HZHsP001000; Wed, 2 Nov 2005 19:35:17 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id jA2HZG5W000999; Wed, 2 Nov 2005 19:35:16 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Wed, 2 Nov 2005 19:35:16 +0200 From: Giorgos Keramidas To: Vladimir Kushnir Message-ID: <20051102173516.GA958@flame.pc> References: <20051027022313.R675@kushnir1.kiev.ua> <20051030052435.J646@kushnir1.kiev.ua> <20051031000217.F636@kushnir1.kiev.ua> <200510311231.33322.jhb@freebsd.org> <20051102014239.O654@kushnir1.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051102014239.O654@kushnir1.kiev.ua> X-Mailman-Approved-At: Thu, 03 Nov 2005 13:23:19 +0000 Cc: freebsd-current@freebsd.org Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Nov 2005 18:31:54 -0000 On 2005-11-02 01:53, Vladimir Kushnir wrote: >On Mon, 31 Oct 2005, John Baldwin wrote: >>On Sunday 30 October 2005 05:17 pm, Vladimir Kushnir wrote: >>> >>> A bit further. >>> >>>On Sun, 30 Oct 2005, Vladimir Kushnir wrote: >>>> >>>> OK, here it is. It's happened between 2005.10.21.19.42.50 and >>>> 2005.10.22.05.07.00. Since then, panic is absolutely reproducible. I have built an amd64 kernel and world and ran with it today. An insta-panic still exists with sources from: cvs -qR up -APd -D '2005/10/21 16:00:00 UTC' From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 01:49:03 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3EB2716A41F; Thu, 3 Nov 2005 01:49:03 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D2F043D45; Thu, 3 Nov 2005 01:49:01 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from flame.pc (patr530-a063.otenet.gr [212.205.215.63]) by kane.otenet.gr (8.13.4/8.13.4/Debian-1) with ESMTP id jA31mwNf025773; Thu, 3 Nov 2005 03:48:59 +0200 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id jA31mpFD001646; Thu, 3 Nov 2005 03:48:51 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id jA31lec1001629; Thu, 3 Nov 2005 03:47:40 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Thu, 3 Nov 2005 03:47:40 +0200 From: Giorgos Keramidas To: Nate Lawson Message-ID: <20051103014740.GA1586@flame.pc> References: <971FCB6690CD0E4898387DBF7552B90E0346CAFB@orsmsx403.amr.corp.intel.com> <20051103.094643.74756456.haro@h4.dion.ne.jp> <436961FD.3040605@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <436961FD.3040605@root.org> X-Mailman-Approved-At: Thu, 03 Nov 2005 13:23:19 +0000 Cc: Munehiro Matsuda , freebsd-acpi@freebsd.org, freebsd-current@freebsd.org, robert.moore@intel.com, jkim@freebsd.org Subject: Re: Panic on boot with new ACPI-CA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 01:49:03 -0000 On 2005-11-02 17:03, Nate Lawson wrote: > As I mentioned to Jung-uk, the problem is likely an error in > acpi-ca modifying memory after it has freed it. The way to > track this down is to enable memguard(9). See the man page for > info. You need to add options DEBUG_MEMGUARD to your kernel, > set the malloc type to watch to M_ACPICA, and rebuild your > kernel and modules. Memguard sets page permissions so we can > catch the culprit who is modifying the memory. This is exactly the messgae printed on my console at panic time -- of memory modified after free. I'm building a kernel with MEMGUARD now, but it's probably going to be a bit hard to get a kernel dump, because the panic happens before disks are available and I don't have a serial console here. From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 08:46:49 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 488F316A41F for ; Thu, 3 Nov 2005 08:46:49 +0000 (GMT) (envelope-from geir.egeland@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8FC243D45 for ; Thu, 3 Nov 2005 08:46:48 +0000 (GMT) (envelope-from geir.egeland@gmail.com) Received: by nproxy.gmail.com with SMTP id o25so78421nfa for ; Thu, 03 Nov 2005 00:46:47 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:subject:x-enigmail-version:content-type:content-transfer-encoding; b=fumLtDeBky+SLGEevf+x4sPvHVxWy31eXtwXOLQPhSn4o6VrPUH/937KZrsShGORjnUPGiN0rkDjV6CkhTbzdodcCODjIewVs2sGJiTMeUxw3p5CL72niI7sw0H9iXHqWyL4x45TAAoki74GELPwqI6Bn5Rqa8CUIVP3TuLkUtg= Received: by 10.48.226.12 with SMTP id y12mr117104nfg; Thu, 03 Nov 2005 00:46:47 -0800 (PST) Received: from ?128.39.21.12? ( [128.39.21.12]) by mx.gmail.com with ESMTP id z73sm755694nfb.2005.11.03.00.46.46; Thu, 03 Nov 2005 00:46:46 -0800 (PST) Message-ID: <4369EA8D.4000506@gmail.com> Date: Thu, 03 Nov 2005 11:46:37 +0100 From: Geir Egeland User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.91.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 03 Nov 2005 13:23:19 +0000 Subject: wireless Media Extensions (wme) and freebsd 6.0-rc1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 08:46:49 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've been playing around with freebsd 6.0-rc1, and I noticed that ifconfig has support for Wireless Media Extensions (WME). Has anyone tested this functionality, and are there any WME enabled pcmcia cards available that also are supported by FreeBSD ? Geir -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDaeqNAsOHgqjtXwERAuWuAJ98hKqVX86Hrmq7sODEYIIBLofEogCg11sp tj7r/B+5DdLRFfqA/ehvVw0= =NdUl -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 09:40:11 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F64416A420; Thu, 3 Nov 2005 09:40:11 +0000 (GMT) (envelope-from mauritz.sundell@telia.com) Received: from pne-smtpout2-sn1.fre.skanova.net (pne-smtpout2-sn1.fre.skanova.net [81.228.11.159]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BDA243D77; Thu, 3 Nov 2005 09:40:04 +0000 (GMT) (envelope-from mauritz.sundell@telia.com) Received: from pne-ps1-sn2 (81.228.8.118) by pne-smtpout2-sn1.fre.skanova.net (7.2.060.1) id 4368D3FE000355D3; Thu, 3 Nov 2005 10:40:03 +0100 Message-ID: <2156358.1131010803308.JavaMail.tomcat@pne-ps1-sn2> Date: Thu, 3 Nov 2005 10:40:03 +0100 (MET) From: Mauritz Sundell To: freebsd-current@freebsd.org, freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain;charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: CP Presentation Server X-clientstamp: [192.71.194.213] X-Mailman-Approved-At: Thu, 03 Nov 2005 13:23:19 +0000 Cc: Subject: CURRENT Safemode does not boot but ACPI-mode does X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mauritz Sundell List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 09:40:11 -0000 27 october I cvsuped and build kernel and world since then I cant boot without ACPI when I boot without there looks to be problems with resource- allocations drivers cannot attach, cannot map interrupt, and finally Mount root fail due to no harddisk found. My previous kernel was from the 26th october. Im running CURRENT on an HP Pavilion zv5000 (laptop) with amd64. Do someone have any tips where I should look? Mauritz Sundell mauritz.sundell@telia.com From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 14:02:30 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E15C516A41F; Thu, 3 Nov 2005 14:02:29 +0000 (GMT) (envelope-from ceri@submonkey.net) Received: from shrike.submonkey.net (cpc2-cdif2-3-1-cust208.cdif.cable.ntl.com [82.31.78.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B0B443D5C; Thu, 3 Nov 2005 14:02:25 +0000 (GMT) (envelope-from ceri@submonkey.net) Received: from ceri by shrike.submonkey.net with local (Exim 4.54 (FreeBSD)) id 1EXffZ-00082v-7Y; Thu, 03 Nov 2005 14:02:21 +0000 Date: Thu, 3 Nov 2005 14:02:21 +0000 From: Ceri Davies To: Michael Bushkov Message-ID: <20051103140221.GF29387@submonkey.net> Mail-Followup-To: Ceri Davies , Michael Bushkov , Brooks Davis , hackers@FreeBSD.org, current@FreeBSD.org References: <20051102001507.GB14638@odin.ac.hmc.edu> <20051103124027.GE29387@submonkey.net> <436A0C73.3010405@rsu.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TYoqghpzCwoKvQG2" Content-Disposition: inline In-Reply-To: <436A0C73.3010405@rsu.ru> X-PGP: finger ceri@FreeBSD.org User-Agent: Mutt/1.5.11 Sender: Ceri Davies Cc: hackers@FreeBSD.org, current@FreeBSD.org Subject: Re: nsswitch reviewer wanted X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 14:02:30 -0000 --TYoqghpzCwoKvQG2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Michael, On Thu, Nov 03, 2005 at 04:11:15PM +0300, Michael Bushkov wrote: > Ceri Davies wrote: >=20 > >I realise that you weren't asking for comments, but I took a quick look > >at http://www.rsu.ru/~bushman/nsswitch_cached/nss_cached.patch and have > >some. I'll send this to the original lists too. > > Thanks for comments! I need them much. Glad to be of some help. Don't take anything I say as any kind of authority though. > >o There aren't nearly enough comments. Granted, I'm not a C aficionado, > > but it's ~ line 3200 of that patch before we come to a new non-trivial > > comment, and there aren't many after that. > > > Ok - I'll comment the code. Thanks. > >o cached/config.c has magic numbers in create_def_configuration_entry(), > > which probably belong as #defines in config.h instead. I'm not sure > > what style(9) says about that though, so am happy to be ignored. > > > Yes, that's right - I guess, the most correct way is to move them to=20 > config.h As I mentioned, I'm no guru, but that seems to be conventional. > >o There is a single mention of a ssh_hostkeys cache in > > include/nsswitch.h, and no code to implement it. > > > I've implemented the patch for OpenSSH, which allows it to use nsswitch= =20 > for the hostkeys. It should be committed by the OpenSSH team. That's why= =20 > the ssh_hostkeys cache is mentioned in the nsswitch.h. This line can=20 > easialy be removed - as it doesn't affect anything. I hadn't realised that. I'd be interested to see that patch if you still have a copy, as it would answer the question of how much work doing such a thing would be. So far as I'm concerned there is no issue leaving that in there, I just wanted to make sure that it hadn't slipped in by mistake. > >o On line 15448, there is a whitespace nit. Also, in this area, are we > > sure that there is no benefit in continuing to key by euid/egid if > > perform_actual_lookup is enabled; can we send the euid/egid with the > > lookup request? > > > You are talking about passing euid/egid to the underlying nsswitch=20 > modules, right? This will require significant changes in these modules,= =20 > and, as far as I'm converned, won't gain us any benefits. >=20 > I can't see any benefit of keying by euid/egud when the=20 > 'perform_actual_lookups' mode is enabled. By ignoring them, we make the= =20 > cache common for all users, and no user can poison it - because all=20 > requests are made solely by ourselves. If we won't ignore the euid/egid,= =20 > then for every user, we'll have to make similar requests, this will also= =20 > affect the cache size. > When perform_actual_lookups mode is off, cache should be certainly=20 > separated by eud/egid for (basically) security reasons. OK, that's an good enough explanation for me. Thanks. > >o A user should be able to invalidate one of their caches (e.g., > > "cached -i hosts" to flush their hosts cache). Root should be able > > to do it for all users with a single command (e.g., "cached -I hosts" > > to flush all hosts caches). > > > Ok - I'll do that. Superb! > >o The manual for cached.conf is unclear over whether it's OK to name > > an "unknown" cache in cached.conf. > > > I'll corect this. In fact, it's ok to do that. I thought that was the intended meaning. That's great. > >o The location of cached.conf is defaulted to /usr/local/etc in > > cached/cached.c and should be changed on commit. > > > Will be corrected. Cool. Thanks again for working on this. Ceri --=20 Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. -- Einstein (attrib.) --TYoqghpzCwoKvQG2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDahhsocfcwTS3JF8RAp9mAJ9LXX2xeqhRiRcQry9t/wkZaHLxXQCeJ+S1 w1i53+FbA0vZ3qBsiHfEAVs= =X2nz -----END PGP SIGNATURE----- --TYoqghpzCwoKvQG2-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 14:03:41 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E80316A41F for ; Thu, 3 Nov 2005 14:03:41 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50D2543D5C for ; Thu, 3 Nov 2005 14:03:39 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1EXfeN-00079j-8K for freebsd-current@freebsd.org; Thu, 03 Nov 2005 15:01:07 +0100 Received: from 72.11.2.113 ([72.11.2.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 03 Nov 2005 15:01:02 +0100 Received: from lynnr.junk by 72.11.2.113 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 03 Nov 2005 15:01:02 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: "Lynn A. Roth" Date: Thu, 03 Nov 2005 07:55:56 -0500 Lines: 851 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 72.11.2.113 User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en Sender: news Subject: Problems Installing to PowerEdge 850 with SATA Drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 14:03:41 -0000 I have two new Dell Poweredge 850 machines. They have an Intel ICH7 chipset. When I boot FreeBSD 6 RC1, the controller is identified, but any drives connected to the SATA ports are not detected. The drive that is included with the system is a Seagate 7200.7 drive. I also tried a Maxtor. Copied below is dmesg -a after booting verbose (it's from a version of pfsense from early this week). There are no BIOS options for selecting the type of SATA, just ATA and OFF. I would appreciate any help in getting FreeBSD installed on these machines. Thanks, Lynn A. Roth Network Adminstrator Interactive Financial Solutions, Inc. Here is dmesg -a after booting verbose. The drive is connected to Channel 0 on the SATA controller. -------------------------------------------------------------- P: ID: 0x00000000 VER: 0x00050014 LDR: 0x01000000 DFR: 0x0fffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 crypto: ath_rate: version 1.2 wlan: <802.11 MAC ACL support> wlan: mac acl policy registered wlan: <802.11 Link Layer> mem: Pentium Pro MTRR support enabled nfslock: pseudo-device null: io: random: ath_hal: 0.9.16.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413, DFS) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: [MPSAFE] pci_open(1): mode 1 addr port (0x0cf8) is 0x80000090 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=27788086) pcibios: BIOS version 2.10 Found $PIR table, 9 entries at 0xc00fb840 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded 0 1 A 0x60 3 4 5 6 10 11 14 15 embedded 0 29 A 0x68 3 4 5 6 10 11 14 15 embedded 0 29 B 0x69 3 4 5 6 10 11 14 15 embedded 0 29 C 0x6a 3 4 5 6 10 11 14 15 embedded 0 29 D 0x6b 3 4 5 6 10 11 14 15 embedded 0 28 A 0x69 3 4 5 6 10 11 14 15 embedded 0 28 B 0x6a 3 4 5 6 10 11 14 15 embedded 0 28 C 0x6b 3 4 5 6 10 11 14 15 embedded 0 28 D 0x63 3 4 5 6 10 11 14 15 embedded 0 31 A 0x60 3 4 5 6 10 11 14 15 embedded 0 31 B 0x62 3 4 5 6 10 11 14 15 embedded 0 31 C 0x68 3 4 5 6 10 11 14 15 embedded 0 31 D 0x63 3 4 5 6 10 11 14 15 embedded 5 0 A 0x60 3 4 5 6 10 11 14 15 embedded 5 0 B 0x61 3 4 5 6 10 11 14 15 embedded 5 0 C 0x62 3 4 5 6 10 11 14 15 embedded 5 0 D 0x63 3 4 5 6 10 11 14 15 embedded 6 0 A 0x61 3 4 5 6 10 11 14 15 embedded 6 0 B 0x62 3 4 5 6 10 11 14 15 embedded 6 0 C 0x63 3 4 5 6 10 11 14 15 embedded 6 0 D 0x60 3 4 5 6 10 11 14 15 slot 1 2 0 A 0x60 3 4 5 6 10 11 14 15 slot 1 2 0 B 0x61 3 4 5 6 10 11 14 15 slot 1 2 0 C 0x62 3 4 5 6 10 11 14 15 slot 1 2 0 D 0x63 3 4 5 6 10 11 14 15 slot 2 1 0 A 0x60 3 4 5 6 10 11 14 15 slot 2 1 0 B 0x61 3 4 5 6 10 11 14 15 slot 2 1 0 C 0x62 3 4 5 6 10 11 14 15 slot 2 1 0 D 0x63 3 4 5 6 10 11 14 15 embedded 7 5 A 0x63 3 4 5 6 10 11 14 15 AcpiOsDerivePciId: bus 0 dev 31 func 0 AcpiOsDerivePciId: bus 0 dev 31 func 0 acpi0: Power Button (fixed) pci_link0: irq 5 on acpi0 pci_link0: Links after initial probe: Index IRQ Rtd Ref IRQs 0 5 N 0 3 4 5 6 7 9 10 11 12 pci_link0: Links after initial validation: Index IRQ Rtd Ref IRQs 0 5 N 0 3 4 5 6 7 9 10 11 12 pci_link0: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 pci_link1: irq 3 on acpi0 pci_link1: Links after initial probe: Index IRQ Rtd Ref IRQs 0 3 N 0 3 4 5 6 7 9 10 11 12 pci_link1: Links after initial validation: Index IRQ Rtd Ref IRQs 0 3 N 0 3 4 5 6 7 9 10 11 12 pci_link1: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 pci_link2: on acpi0 pci_link2: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 pci_link2: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 pci_link2: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 pci_link3: on acpi0 pci_link3: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 pci_link3: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 pci_link3: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 pci_link4: irq 11 on acpi0 pci_link4: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 6 7 9 10 11 12 pci_link4: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 6 7 9 10 11 12 pci_link4: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 pci_link5: irq 10 on acpi0 pci_link5: Links after initial probe: Index IRQ Rtd Ref IRQs 0 10 N 0 3 4 5 6 7 9 10 11 12 pci_link5: Links after initial validation: Index IRQ Rtd Ref IRQs 0 10 N 0 3 4 5 6 7 9 10 11 12 pci_link5: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 pci_link6: irq 6 on acpi0 pci_link6: Links after initial probe: Index IRQ Rtd Ref IRQs 0 6 N 0 3 4 5 6 7 9 10 11 12 pci_link6: Links after initial validation: Index IRQ Rtd Ref IRQs 0 6 N 0 3 4 5 6 7 9 10 11 12 pci_link6: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 pci_link7: on acpi0 pci_link7: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 pci_link7: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 pci_link7: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 ACPI timer: 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: physical bus=0 found-> vendor=0x8086, dev=0x2778, revid=0x00 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x2090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x2779, revid=0x00 bus=0, slot=1, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0047, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x07 (1750 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 found-> vendor=0x8086, dev=0x27d0, revid=0x01 bus=0, slot=28, func=0 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x06 (1500 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 found-> vendor=0x8086, dev=0x27e0, revid=0x01 bus=0, slot=28, func=4 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0047, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x07 (1750 ns), maxlat=0x00 (0 ns) intpin=b, irq=255 found-> vendor=0x8086, dev=0x27e2, revid=0x01 bus=0, slot=28, func=5 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0047, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x07 (1750 ns), maxlat=0x00 (0 ns) intpin=c, irq=255 found-> vendor=0x8086, dev=0x27c8, revid=0x01 bus=0, slot=29, func=0 class=0c-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 map[20]: type 4, range 32, base 0000ace0, size 5, enabled pcib0: matched entry for 0.29.INTA pcib0: slot 29 INTA hardwired to IRQ 20 found-> vendor=0x8086, dev=0x27c9, revid=0x01 bus=0, slot=29, func=1 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=10 map[20]: type 4, range 32, base 0000acc0, size 5, enabled pcib0: matched entry for 0.29.INTB pcib0: slot 29 INTB hardwired to IRQ 21 found-> vendor=0x8086, dev=0x27ca, revid=0x01 bus=0, slot=29, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=6 map[20]: type 4, range 32, base 0000aca0, size 5, enabled pcib0: matched entry for 0.29.INTC pcib0: slot 29 INTC hardwired to IRQ 22 found-> vendor=0x8086, dev=0x27cc, revid=0x01 bus=0, slot=29, func=7 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type 1, range 32, base feb00400, size 10, enabled pcib0: matched entry for 0.29.INTA pcib0: slot 29 INTA hardwired to IRQ 20 found-> vendor=0x8086, dev=0x244e, revid=0xe1 bus=0, slot=30, func=0 class=06-04-01, hdrtype=0x01, mfdev=0 cmdreg=0x0147, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x0b (2750 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x27b8, revid=0x01 bus=0, slot=31, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0147, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x27df, revid=0x01 bus=0, slot=31, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0288, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 map[20]: type 4, range 32, base 0000fc00, size 4, enabled found-> vendor=0x8086, dev=0x27c0, revid=0x01 bus=0, slot=31, func=2 class=01-01-8f, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x02b0, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type 4, range 32, base 0000ac98, size 3, enabled map[14]: type 4, range 32, base 0000ac90, size 2, enabled map[18]: type 4, range 32, base 0000ac80, size 3, enabled map[1c]: type 4, range 32, base 0000ac78, size 2, enabled map[20]: type 4, range 32, base 0000ac60, size 4, enabled map[24]: type 1, range 32, base feb00000, size 10, enabled pcib0: matched entry for 0.31.INTC pcib0: slot 31 INTC hardwired to IRQ 20 found-> vendor=0x8086, dev=0x27da, revid=0x01 bus=0, slot=31, func=3 class=0c-05-00, hdrtype=0x00, mfdev=0 cmdreg=0x0001, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=255 map[20]: type 4, range 32, base 000008c0, size 5, enabled pcib1: at device 1.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xf000-0xfff pcib1: memory decode 0xfff00000-0xfffff pcib1: prefetched decode 0xfff00000-0xfffff pci1: on pcib1 pci1: physical bus=1 pcib2: at device 28.0 on pci0 pcib2: secondary bus 2 pcib2: subordinate bus 4 pcib2: I/O decode 0xe000-0xefff pcib2: memory decode 0xfe800000-0xfeafffff pcib2: prefetched decode 0xfff00000-0xfffff pci2: on pcib2 pci2: physical bus=2 found-> vendor=0x8086, dev=0x0340, revid=0x09 bus=2, slot=0, func=0 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x06 (1500 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x0341, revid=0x09 bus=2, slot=0, func=2 class=06-04-00, hdrtype=0x01, mfdev=1 cmdreg=0x0007, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x06 (1500 ns), maxlat=0x00 (0 ns) pcib3: at device 0.0 on pci2 pcib3: secondary bus 3 pcib3: subordinate bus 3 pcib3: I/O decode 0xe000-0xefff pcib3: memory decode 0xfe900000-0xfeafffff pcib3: prefetched decode 0xfff00000-0xfffff pci3: on pcib3 pci3: physical bus=3 found-> vendor=0x8086, dev=0x108a, revid=0x03 bus=3, slot=4, func=0 class=02-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0117, statreg=0x0230, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0xff (63750 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type 1, range 64, base fe9e0000, size 17, enabled pcib3: (null) requested memory range 0xfe9e0000-0xfe9fffff: good pcib2: (null) requested memory range 0xfe9e0000-0xfe9fffff: good map[20]: type 4, range 32, base 0000ecc0, size 6, enabled pcib3: (null) requested I/O range 0xecc0-0xecff: in range pcib2: (null) requested I/O range 0xecc0-0xecff: in range pcib2: matched entry for 2.0.INTA pcib2: slot 0 INTA hardwired to IRQ 16 pcib3: slot 4 INTA is routed to irq 16 found-> vendor=0x8086, dev=0x108a, revid=0x03 bus=3, slot=4, func=1 class=02-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0117, statreg=0x0230, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0xff (63750 ns), maxlat=0x00 (0 ns) intpin=b, irq=3 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type 1, range 64, base fe9c0000, size 17, enabled pcib3: (null) requested memory range 0xfe9c0000-0xfe9dffff: good pcib2: (null) requested memory range 0xfe9c0000-0xfe9dffff: good map[20]: type 4, range 32, base 0000ec80, size 6, enabled pcib3: (null) requested I/O range 0xec80-0xecbf: in range pcib2: (null) requested I/O range 0xec80-0xecbf: in range pcib2: matched entry for 2.0.INTB pcib2: slot 0 INTB hardwired to IRQ 17 pcib3: slot 4 INTB is routed to irq 17 em0: port 0xecc0-0xecff mem 0xfe9e0000-0xfe9fffff irq 16 at device 4.0 on pci3 em0: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xfe9e0000 em0: Reserved 0x40 bytes for rid 0x20 type 4 at 0xecc0 em0: [MPSAFE] em0: bpf attached em0: Ethernet address: 00:0e:0c:a0:a6:90 em0: Speed:N/A Duplex:N/A em1: port 0xec80-0xecbf mem 0xfe9c0000-0xfe9dffff irq 17 at device 4.1 on pci3 em1: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xfe9c0000 em1: Reserved 0x40 bytes for rid 0x20 type 4 at 0xec80 em1: [MPSAFE] em1: bpf attached em1: Ethernet address: 00:0e:0c:a0:a6:91 em1: Speed:N/A Duplex:N/A pcib4: at device 0.2 on pci2 pcib4: secondary bus 4 pcib4: subordinate bus 4 pcib4: I/O decode 0xf000-0xfff pcib4: memory decode 0xfff00000-0xfffff pcib4: prefetched decode 0xfff00000-0xfffff pci4: on pcib4 pci4: physical bus=4 pcib5: at device 28.4 on pci0 pcib5: secondary bus 5 pcib5: subordinate bus 5 pcib5: I/O decode 0xd000-0xdfff pcib5: memory decode 0xfe600000-0xfe7fffff pcib5: prefetched decode 0xfff00000-0xfffff pci5: on pcib5 pci5: physical bus=5 found-> vendor=0x14e4, dev=0x1659, revid=0x11 bus=5, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 powerspec 2 supports D0 D3 current D0 MSI supports 8 messages, 64 bit map[10]: type 1, range 64, base fe6f0000, size 16, enabled pcib5: (null) requested memory range 0xfe6f0000-0xfe6fffff: good pcib5: matched entry for 5.0.INTA pcib5: slot 0 INTA hardwired to IRQ 16 bge0: mem 0xfe6f0000-0xfe6fffff irq 16 at device 0.0 on pci5 bge0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xfe6f0000 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: bpf attached bge0: Ethernet address: 00:14:22:7b:c7:e5 bge0: [MPSAFE] pcib6: at device 28.5 on pci0 pcib6: secondary bus 6 pcib6: subordinate bus 6 pcib6: I/O decode 0xc000-0xcfff pcib6: memory decode 0xfe400000-0xfe5fffff pcib6: prefetched decode 0xfff00000-0xfffff pci6: on pcib6 pci6: physical bus=6 found-> vendor=0x14e4, dev=0x1659, revid=0x11 bus=6, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0010, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=3 powerspec 2 supports D0 D3 current D0 MSI supports 8 messages, 64 bit map[10]: type 1, range 64, base fe4f0000, size 16, enabled pcib6: (null) requested memory range 0xfe4f0000-0xfe4fffff: good pcib6: matched entry for 6.0.INTA pcib6: slot 0 INTA hardwired to IRQ 17 bge1: mem 0xfe4f0000-0xfe4fffff irq 17 at device 0.0 on pci6 bge1: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xfe4f0000 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: bpf attached bge1: Ethernet address: 00:14:22:7b:c7:e6 bge1: [MPSAFE] uhci0: port 0xace0-0xacff irq 20 at device 29.0 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0xace0 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 0xacc0-0xacdf irq 21 at device 29.1 on pci0 uhci1: Reserved 0x20 bytes for rid 0x20 type 4 at 0xacc0 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 0xaca0-0xacbf irq 22 at device 29.2 on pci0 uhci2: Reserved 0x20 bytes for rid 0x20 type 4 at 0xaca0 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 ehci0: mem 0xfeb00400-0xfeb007ff irq 20 at device 29.7 on pci0 ehci0: Reserved 0x400 bytes for rid 0x10 type 3 at 0xfeb00400 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: wrong number of companions (7 != 3) usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered pcib7: at device 30.0 on pci0 pcib7: secondary bus 7 pcib7: subordinate bus 7 pcib7: I/O decode 0xb000-0xbfff pcib7: memory decode 0xfe200000-0xfe3fffff pcib7: prefetched decode 0xfd000000-0xfdffffff pcib7: Subtractively decoded bridge. pci7: on pcib7 pci7: physical bus=7 found-> vendor=0x18ca, dev=0x0020, revid=0x00 bus=7, slot=5, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0023, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 3, range 32, base fd000000, size 24, enabled pcib7: (null) requested memory range 0xfd000000-0xfdffffff: good map[14]: type 1, range 32, base fe2c0000, size 18, enabled pcib7: (null) requested memory range 0xfe2c0000-0xfe2fffff: good map[18]: type 4, range 32, base 0000bc80, size 7, enabled pcib7: (null) requested I/O range 0xbc80-0xbcff: in range pci7: at device 5.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 31.1 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xfc00 ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x04 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=00 stat1=00 devices=0x4 ata0: [MPSAFE] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=00 ostat0=ff ostat1=ff ata1: [MPSAFE] atapci1: port 0xac98-0xac9f,0xac90-0xac93,0xac80-0xac87,0xac78-0xac7b,0xac60-0xac6f mem 0xfeb00000-0xfeb003ff irq 20 at device 31.2 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0xac60 atapci1: [MPSAFE] atapci1: Reserved 0x400 bytes for rid 0x24 type 3 at 0xfeb00000 atapci1: [MPSAFE] ata2: on atapci1 ata2: SATA connect status=00000000 ata2: [MPSAFE] ata3: on atapci1 ata3: SATA connect status=00000000 ata3: [MPSAFE] ata4: on atapci1 ata4: SATA connect status=00000000 ata4: [MPSAFE] ata5: on atapci1 ata5: SATA connect status=00000000 ata5: [MPSAFE] pci0: at device 31.3 (no driver attached) speaker0: port 0x61 on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 sio0: irq maps: 0x4c69 0x4c79 0x4c69 0x4c69 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: does not respond device_attach: fdc0 attach returned 6 ex_isa_identify() unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff ahc_isa_probe 0: ioport 0xc00 alloc failed ahc_isa_probe 10: ioport 0xac00 alloc failed ahc_isa_probe 11: ioport 0xbc00 alloc failed ahc_isa_probe 14: ioport 0xec00 alloc failed ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it fdc: fdc0 already exists; skipping it sio: sio0 already exists; skipping it pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff,0xec000-0xeffff on isa0 adv0: not probed (disabled) aha0: not probed (disabled) aic0: not probed (disabled) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 kbd0: atkbd0, generic (0), config:0x0, flags:0x3f0000 atkbd0: [GIANT-LOCKED] bt0: not probed (disabled) cs0: not probed (disabled) ed0: not probed (disabled) fe0: not probed (disabled) ie0: not probed (disabled) lnc0: not probed (disabled) ppc0: parallel port not found. ppc0: failed to probe at irq 7 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: irq maps: 0x4c69 0x4c69 0x4c69 0x4c69 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) sn0: not probed (disabled) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 vt0: not probed (disabled) isa_probe_children: probing PnP devices ukbd0: DELL DELL USB Keyboard, rev 1.10/1.04, addr 2, iclass 3/1 kbd: new array size 4 kbd1 at ukbd0 kbd1: ukbd0, generic (0), config:0x0, flags:0x1d0000 Device configuration finished. procfs registered lapic: Divisor 2, Frequency 100003758 hz Timecounter "TSC" frequency 2800121513 Hz quality 800 Timecounters tick every 1.000 msec crypto: assign driver 0, flags 6 crypto: driver 0 registers alg 1 flags 0 maxoplen 0 crypto: driver 0 registers alg 2 flags 0 maxoplen 0 crypto: driver 0 registers alg 3 flags 0 maxoplen 0 crypto: driver 0 registers alg 4 flags 0 maxoplen 0 crypto: driver 0 registers alg 5 flags 0 maxoplen 0 crypto: driver 0 registers alg 17 flags 0 maxoplen 0 crypto: driver 0 registers alg 6 flags 0 maxoplen 0 crypto: driver 0 registers alg 7 flags 0 maxoplen 0 crypto: driver 0 registers alg 15 flags 0 maxoplen 0 crypto: driver 0 registers alg 8 flags 0 maxoplen 0 crypto: driver 0 registers alg 16 flags 0 maxoplen 0 crypto: driver 0 registers alg 9 flags 0 maxoplen 0 crypto: driver 0 registers alg 10 flags 0 maxoplen 0 crypto: driver 0 registers alg 13 flags 0 maxoplen 0 crypto: driver 0 registers alg 14 flags 0 maxoplen 0 crypto: driver 0 registers alg 11 flags 0 maxoplen 0 crypto: driver 0 registers alg 18 flags 0 maxoplen 0 BRIDGE 031224 loaded crypto: Fast IPsec: Initialized Security Association Processing. pfsync0: bpf attached lo0: bpf attached pflog0: bpf attached md0: Preloaded image 14483456 bytes at 0xc0ab1208 g_pc98_taste: guessing 17 sectors g_pc98_taste: guessing 8 heads g_pc98_taste: guessing 17 sectors g_pc98_taste: guessing 8 heads ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire acd0: setting PIO4 on Intel ICH7 chip acd0: setting UDMA33 on Intel ICH7 chip acd0: CDROM drive at ata0 as master acd0: read 4125KB/s (4125KB/s), 128KB buffer, UDMA33 acd0: Reads: CDR, CDRW, CDDA stream, packet acd0: Writes: acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: CD-ROM 120mm data disc ATA PseudoRAID loaded ioapic0: routing intpin 1 (ISA IRQ 1) to cluster 0 ioapic0: routing intpin 4 (ISA IRQ 4) to cluster 0 ioapic0: routing intpin 9 (ISA IRQ 9) to cluster 0 ioapic0: routing intpin 13 (ISA IRQ 13) to cluster 0 ioapic0: routing intpin 14 (ISA IRQ 14) to cluster 0 ioapic0: routing intpin 15 (ISA IRQ 15) to cluster 0 ioapic0: routing intpin 16 (PCI IRQ 16) to cluster 0 ioapic0: routing intpin 17 (PCI IRQ 17) to cluster 0 ioapic0: routing intpin 20 (PCI IRQ 20) to cluster 0 ioapic0: routing intpin 21 (PCI IRQ 21) to cluster 0 ioapic0: routing intpin 22 (PCI IRQ 22) to cluster 0 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4 GEOM_LABEL: Label for provider acd0 is iso9660/FreeSBIE. g_pc98_taste: guessing 17 sectors g_pc98_taste: guessing 8 heads acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4 acd0: FAILURE - READ_BIG MEDIUM ERROR asc=0x11 ascq=0x06 error=4 g_pc98_taste: guessing 17 sectors g_pc98_taste: guessing 8 heads acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4 acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 error=4 Trying to mount root from ufs:/dev/md0 start_init: trying /sbin/init ___ ___/ f \\ / p \\___/ Sense \\___/ \\ \\___/ Welcome to pfSense 0.90 on the 'cdrom' platform... Running CDROM routines... Mounting /FreeSBIE... (ignore error messages) Mounting /usr... WARNING: opening backing store: /FreeSBIE/uzip/usr.uzip readonly md1.uzip: 1359 x 65536 blocks g_pc98_taste: guessing 17 sectors g_pc98_taste: guessing 8 heads Memory devices: g_pc98_taste: guessing 17 sectors g_pc98_taste: guessing 8 heads g_pc98_taste: guessing 17 sectors g_pc98_taste: guessing 8 heads /tmp Starting pfi... Looking for pfi.conf on /dev/acd0c... Copying /FreeSBIE/cf/conf/* /cf/conf/ Copying config.xml to /conf.default/conf/ No swap on cdrom Removing /etc/rc.conf... Starting USB... kbd1 ukbd0, type:generic (0) done. Starting device manager (devd)... done. Loading configuration... done. LAN sis0 interface mismatch. -- Running interface assignment option. Valid interfaces are: em0 00:0e:0c:a0:a6:90 em1 00:0e:0c:a0:a6:91 bge0 00:14:22:7b:c7:e5 bge1 00:14:22:7b:c7:e6 Do you want to set up VLANs first? If you are not going to use VLANs, or only for optional interfaces, you should say no here and use the webGUI to configure VLANs later, if required. Do you want to set up VLANs now [y|n]? Enter the parent interface name for the new VLAN (or nothing if finished): Enter the VLAN tag (1-4094): Enter the parent interface name for the new VLAN (or nothing if finished): VLAN interfaces: vlan0 VLAN tag 40, interface em0 *NOTE* pfSense requires *ATLEAST* 2 assigned interfaces to function. If you do not have two interfaces turn off the machine until you do. If you do not know the names of your interfaces, you may choose to use auto-detection... In that case, disconnect all interfaces now before hitting a. The system will then prompt you to plug in each nic to autodetect. Enter the LAN interface name or 'a' for auto-detection: Enter the WAN interface name or 'a' for auto-detection: Enter the Optional 1 interface name or 'a' for auto-detection (or nothing if finished): The interfaces will be assigned as follows: LAN -> vlan0 WAN -> em1 Do you want to proceed [y|n]? Updating configuration... done. Cleaning backup cache... done. Setting up extended sysctls... done. Syncing user passwords... done. Setting timezone... done. Starting syslog... done. vlan0: bpf attached Configuring LAN interface... bge0: link state changed to UP bge1: link state changed to DOWN done. Configuring WAN interface... em0: Link is up 1000 Mbps Full Duplex em0: link state changed to UP vlan0: link state changed to UP em1: Link is up 1000 Mbps Full Duplex em1: link state changed to UP em1: Link is up 1000 Mbps Full Duplex done. Configuring OPT interfaces... done. pflog0: promiscuous mode enabled Configuring CARP interfaces... done. Configuring firewall... aliases rules filtering done. Starting webConfigurator... done Starting DNS forwarder... done. Starting DHCP service... done. Warning: Invalid argument supplied for foreach() in /etc/inc/services.inc on line 308 Starting NTP client... done. Starting FTP helpers... done. Starting Secure Shell Services... Generating Keys: Generating public/private rsa1 key pair. Your identification has been saved in /etc/ssh/ssh_host_key. Your public key has been saved in /etc/ssh/ssh_host_key.pub. The key fingerprint is: c0:39:10:fd:37:b6:a2:bd:0d:81:fc:2b:24:6f:2c:76 root@pfSense.local Generating public/private rsa key pair. Your identification has been saved in /etc/ssh/ssh_host_rsa_key. Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub. The key fingerprint is: 1c:42:e8:9b:ae:6d:6d:17:cc:1a:70:80:81:c8:66:70 root@pfSense.local Generating public/private dsa key pair. Your identification has been saved in /etc/ssh/ssh_host_dsa_key. Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub. The key fingerprint is: 40:53:92:dc:77:90:d6:8c:7a:9d:4c:4b:7c:4e:65:15 root@pfSense.local Starting SSH... done. Starting CRON... done. Bootup complete FreeBSD/i386 (pfSense.local) (console) login: From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 14:21:03 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9E5916A41F; Thu, 3 Nov 2005 14:21:03 +0000 (GMT) (envelope-from bushman@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E5D143D53; Thu, 3 Nov 2005 14:21:02 +0000 (GMT) (envelope-from bushman@rsu.ru) Received: from [195.208.252.201] (celsius.cc.rsu.ru [195.208.252.201]) by mail.r61.net (8.13.4/8.13.4) with ESMTP id jA3EL0SS083874; Thu, 3 Nov 2005 17:21:00 +0300 (MSK) (envelope-from bushman@rsu.ru) Message-ID: <436A1DED.9090805@rsu.ru> Date: Thu, 03 Nov 2005 17:25:49 +0300 From: Michael Bushkov User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051018) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ceri Davies References: <20051102001507.GB14638@odin.ac.hmc.edu> <20051103124027.GE29387@submonkey.net> <436A0C73.3010405@rsu.ru> <20051103140221.GF29387@submonkey.net> In-Reply-To: <20051103140221.GF29387@submonkey.net> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on asterix.r61.net X-Virus-Status: Clean Cc: hackers@FreeBSD.org, current@FreeBSD.org Subject: Re: nsswitch reviewer wanted X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 14:21:04 -0000 Hello, Ceri! I'll do all the necessary changes and will send the updated patch to you and to the lists. >I hadn't realised that. I'd be interested to see that patch if you >still have a copy, as it would answer the question of how much work >doing such a thing would be. So far as I'm concerned there is no issue >leaving that in there, I just wanted to make sure that it hadn't slipped >in by mistake. > > > There is a patch for the openssh-portable port here: http://www.rsu.ru/~bushman/nsswitch_cached/openssh-portable_port.patch I'll make a patch to the standard openssh distribution to commit it to the official openssh source-tree and will send you a copy. Actually, It's not hard to add nsswitch support to the particular application - we need to find the places in the code, where lookups are done and substitute them with nsdispatch calls. The old code is refactored to meet the nsswitch module standards. >Thanks again for working on this. > > I'm really enjoying doing it :) >Ceri > > -- Michael From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 14:21:39 2005 Return-Path: X-Original-To: current@FreeBSD.ORG Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75D4516A41F; Thu, 3 Nov 2005 14:21:39 +0000 (GMT) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [70.88.158.93]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAD8043D46; Thu, 3 Nov 2005 14:21:38 +0000 (GMT) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [70.88.158.93]) by sasami.jurai.net (8.13.1/8.13.1) with ESMTP id jA3ELMUp079998; Thu, 3 Nov 2005 09:21:28 -0500 (EST) (envelope-from mdodd@FreeBSD.ORG) Date: Thu, 3 Nov 2005 09:21:22 -0500 (EST) From: "Matthew N. Dodd" X-X-Sender: winter@sasami.jurai.net To: Vladimir Grebenschikov In-Reply-To: <1131008180.1295.10.camel@localhost> Message-ID: <20051103092055.W84465@sasami.jurai.net> References: <1110800717.1296.19.camel@localhost> <200503231411.46948.jhb@FreeBSD.org> <1111610025.1471.6.camel@localhost> <20050323154642.J37251@sasami.jurai.net> <1131008180.1295.10.camel@localhost> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-247358547-1131027682=:84465" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (sasami.jurai.net [70.88.158.93]); Thu, 03 Nov 2005 09:21:29 -0500 (EST) Cc: "current@freebsd.org" , John Baldwin , freebsd-mobile@FreeBSD.ORG Subject: Re: Reattach/redetect allways connected umass device - is it possible ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 14:21:39 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-247358547-1131027682=:84465 Content-Type: TEXT/PLAIN; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8BIT On Thu, 3 Nov 2005, Vladimir Grebenschikov wrote: > ÷ ÓÒ, 23/03/2005 × 15:48 -0500, Matthew N. Dodd ÐÉÛÅÔ: >> You want this: >> >> ftp://ftp.jurai.net/users/winter/cam-detach.patch >> >> You will then be able to perform a 'camcontrol detach daX', swap cards, >> and run 'camcontrol rescan'. > > Is there any chance to get this patch commited ? > It is useful and I am using it for half year. Its got really bad race conditions. --0-247358547-1131027682=:84465-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 14:24:51 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF44616A41F; Thu, 3 Nov 2005 14:24:51 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail5.speedfactory.net [66.23.216.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id D375C43D7C; Thu, 3 Nov 2005 14:24:45 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 1302099 for multiple; Thu, 03 Nov 2005 09:22:44 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jA3EOXk7065500; Thu, 3 Nov 2005 09:24:33 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Thu, 3 Nov 2005 08:57:56 -0500 User-Agent: KMail/1.8.2 References: <436961FD.3040605@root.org> <20051103020902.GA29536@flame.pc> <20051103.114712.74756421.haro@h4.dion.ne.jp> In-Reply-To: <20051103.114712.74756421.haro@h4.dion.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511030857.58338.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=100 Cc: Munehiro Matsuda , jkim@freebsd.org, freebsd-current@freebsd.org, robert.moore@intel.com, keramida@linux.gr Subject: Re: Panic on boot with new ACPI-CA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 14:24:52 -0000 On Wednesday 02 November 2005 09:47 pm, Munehiro Matsuda wrote: > From: Giorgos Keramidas > Date: Thu, 3 Nov 2005 04:09:02 +0200 > > ::On 2005-11-03 03:47, Giorgos Keramidas wrote: > ::> On 2005-11-02 17:03, Nate Lawson wrote: > ::> > As I mentioned to Jung-uk, the problem is likely an error in > ::> > acpi-ca modifying memory after it has freed it. The way to > ::> > track this down is to enable memguard(9). See the man page for > ::> > info. You need to add options DEBUG_MEMGUARD to your kernel, > ::> > set the malloc type to watch to M_ACPICA, and rebuild your > ::> > kernel and modules. Memguard sets page permissions so we can > ::> > catch the culprit who is modifying the memory. > ::> > ::> This is exactly the messgae printed on my console at panic time > ::> -- of memory modified after free. I'm building a kernel with > ::> MEMGUARD now, but it's probably going to be a bit hard to get a > ::> kernel dump, because the panic happens before disks are available > ::> and I don't have a serial console here. > :: > ::Does the following look ok for using memguard(9) with M_ACPICA? > :: > ::%%% begin acpica-memguard.patch > ::Index: kern/kern_malloc.c > ::=================================================================== > ::RCS file: /home/ncvs/src/sys/kern/kern_malloc.c,v > ::retrieving revision 1.148 > ::diff -u -r1.148 kern_malloc.c > ::--- kern/kern_malloc.c 20 Oct 2005 21:28:31 -0000 1.148 > ::+++ kern/kern_malloc.c 3 Nov 2005 02:04:02 -0000 > ::@@ -62,6 +62,8 @@ > :: #include > :: #include > :: > ::+MALLOC_DECLARE(M_ACPICA); > ::+ > :: #ifdef DEBUG_MEMGUARD > :: #include > :: #endif > ::@@ -305,7 +307,7 @@ > :: > :: #ifdef DEBUG_MEMGUARD > :: /* XXX CHANGEME! */ > ::- if (mtp == M_SUBPROC) > ::+ if (mtp == M_ACPICA) > :: return memguard_alloc(size, flags); > :: #endif > :: > ::%%% end acpica-memguard.patch > > Hi, > > There are few more "CHANGEME!" places. > I used following: > > @@ -64,6 +64,7 @@ > > #ifdef DEBUG_MEMGUARD > #include > +MALLOC_DECLARE(M_ACPICA); > #endif > > #if defined(INVARIANTS) && defined(__i386__) > @@ -305,7 +306,7 @@ > > #ifdef DEBUG_MEMGUARD > /* XXX CHANGEME! */ > - if (mtp == M_SUBPROC) > + if (mtp == M_ACPICA) > return memguard_alloc(size, flags); > #endif > > @@ -360,7 +361,7 @@ > > #ifdef DEBUG_MEMGUARD > /* XXX CHANGEME! */ > - if (mtp == M_SUBPROC) { > + if (mtp == M_ACPICA) { > memguard_free(addr); > return; > } > @@ -424,7 +425,7 @@ > > #ifdef DEBUG_MEMGUARD > /* XXX: CHANGEME! */ > -if (mtp == M_SUBPROC) { > +if (mtp == M_ACPICA) { > slab = NULL; > alloc = size; > } else { Someone should fix it so that the type is a kernel option so you can do: options MEMGUARD=M_ACPICA or some such. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 14:25:02 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0CEC16A421; Thu, 3 Nov 2005 14:25:02 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4064243D6E; Thu, 3 Nov 2005 14:25:00 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by rosebud.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id jA3EOrD9031590; Thu, 3 Nov 2005 16:24:58 +0200 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id jA3EOlFV001833; Thu, 3 Nov 2005 16:24:47 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id jA3EOkcl001832; Thu, 3 Nov 2005 16:24:46 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Thu, 3 Nov 2005 16:24:46 +0200 From: Giorgos Keramidas To: Nate Lawson Message-ID: <20051103142446.GA1787@flame.pc> References: <971FCB6690CD0E4898387DBF7552B90E0346CAFB@orsmsx403.amr.corp.intel.com> <20051103.094643.74756456.haro@h4.dion.ne.jp> <436961FD.3040605@root.org> <20051103014740.GA1586@flame.pc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051103014740.GA1586@flame.pc> Cc: Munehiro Matsuda , freebsd-acpi@freebsd.org, freebsd-current@freebsd.org, robert.moore@intel.com, jkim@freebsd.org Subject: Re: Panic on boot with new ACPI-CA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 14:25:02 -0000 On 2005-11-03 03:47, Giorgos Keramidas wrote: >On 2005-11-02 17:03, Nate Lawson wrote: >> As I mentioned to Jung-uk, the problem is likely an error in >> acpi-ca modifying memory after it has freed it. The way to >> track this down is to enable memguard(9). See the man page for >> info. You need to add options DEBUG_MEMGUARD to your kernel, >> set the malloc type to watch to M_ACPICA, and rebuild your >> kernel and modules. Memguard sets page permissions so we can >> catch the culprit who is modifying the memory. > > This is exactly the messgae printed on my console at panic time > -- of memory modified after free. I'm building a kernel with > MEMGUARD now, but it's probably going to be a bit hard to get a > kernel dump, because the panic happens before disks are > available and I don't have a serial console here. This is definitely something that is ACPI-related. I updated my sources to the last commit before the start of the ACPI import: build@flame:/home/build/src$ cvs -qR up -APd -D '2005/11/01 22:00:00 UTC' Rebuilt everything and I see no panics now. I'll use the watchpoint trick Nate posted when I have a new build to test. - Giorgos From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 14:40:18 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0E4616A422 for ; Thu, 3 Nov 2005 14:40:18 +0000 (GMT) (envelope-from pho@holm.cc) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.FreeBSD.org (Postfix) with SMTP id 760BF43D5A for ; Thu, 3 Nov 2005 14:40:16 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 19315 invoked from network); 3 Nov 2005 14:40:14 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 3 Nov 2005 14:40:14 -0000 X-pair-Authenticated: 80.161.118.233 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id jA3EeEFh043150; Thu, 3 Nov 2005 15:40:14 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id jA3EeDOU043149; Thu, 3 Nov 2005 15:40:13 +0100 (CET) (envelope-from pho) Date: Thu, 3 Nov 2005 15:40:13 +0100 From: Peter Holm To: Giorgos Keramidas Message-ID: <20051103144013.GA43086@peter.osted.lan> References: <971FCB6690CD0E4898387DBF7552B90E0346CAFB@orsmsx403.amr.corp.intel.com> <20051103.094643.74756456.haro@h4.dion.ne.jp> <436961FD.3040605@root.org> <20051103014740.GA1586@flame.pc> <20051103142446.GA1787@flame.pc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051103142446.GA1787@flame.pc> User-Agent: Mutt/1.4.2.1i Cc: Munehiro Matsuda , freebsd-acpi@freebsd.org, robert.moore@intel.com, freebsd-current@freebsd.org, Nate Lawson , jkim@freebsd.org Subject: Re: Panic on boot with new ACPI-CA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 14:40:18 -0000 On Thu, Nov 03, 2005 at 04:24:46PM +0200, Giorgos Keramidas wrote: > On 2005-11-03 03:47, Giorgos Keramidas wrote: > >On 2005-11-02 17:03, Nate Lawson wrote: > >> As I mentioned to Jung-uk, the problem is likely an error in > >> acpi-ca modifying memory after it has freed it. The way to > >> track this down is to enable memguard(9). See the man page for > >> info. You need to add options DEBUG_MEMGUARD to your kernel, > >> set the malloc type to watch to M_ACPICA, and rebuild your > >> kernel and modules. Memguard sets page permissions so we can > >> catch the culprit who is modifying the memory. > > > > This is exactly the messgae printed on my console at panic time > > -- of memory modified after free. I'm building a kernel with > > MEMGUARD now, but it's probably going to be a bit hard to get a > > kernel dump, because the panic happens before disks are > > available and I don't have a serial console here. > > This is definitely something that is ACPI-related. I updated my > sources to the last commit before the start of the ACPI import: > > build@flame:/home/build/src$ cvs -qR up -APd -D '2005/11/01 22:00:00 UTC' > > Rebuilt everything and I see no panics now. > > I'll use the watchpoint trick Nate posted when I have a new build > to test. > I've had the same problem with two of my boxes. Here's the result of a watchpoint: http://people.freebsd.org/~pho/stress/log/acpi.html I too came to the conclusion that the damage happened between 2005-11-01 22:00:00 UTC OK 2005-11-01 22:45:00 UTC panic - Peter > - Giorgos > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 14:50:01 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59F8616A41F for ; Thu, 3 Nov 2005 14:50:01 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail5.speedfactory.net [66.23.216.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B02743D48 for ; Thu, 3 Nov 2005 14:50:00 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 1303365 for multiple; Thu, 03 Nov 2005 09:48:00 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jA3EnpCO065662; Thu, 3 Nov 2005 09:49:54 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Thu, 3 Nov 2005 09:49:00 -0500 User-Agent: KMail/1.8.2 References: <20051027022313.R675@kushnir1.kiev.ua> <20051103020404.J85422@kushnir1.kiev.ua> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511030949.01726.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=100 Cc: Max Laier , Victor Snezhko Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 14:50:01 -0000 On Thursday 03 November 2005 12:40 am, Victor Snezhko wrote: > Vladimir Kushnir writes: > > On Thu, 3 Nov 2005, Max Laier wrote: > >>> Here it is: right before panic it prints > >>> > >>> For 0xffffff0017531100 -1 ticks > >>> For 0xffffff0017531100 -1 ticks > >> > >> This results in two consecutive callout_stop() calls, but shouldn't hurt > >> as callout_stop is protected against that. > >> > >> Do you get a dump for this? Can you compare this pointer to the global > >> llinfo_nd6 and see if "c" from the softclock() frame is related (or > >> maybe the previous item in the list TAILQ). > > > > Sorry I'm not very goot at debugging. Would you please give me some > > instructions (lamer's level, preferably :-)). And anyway I'll be able > > to do it tomorrow only. > > In the meantime, I want to debug this too. I would insert a panic() > call somewhere in the beginning of nd6_llinfo_settimer(), but there is > a problem. nd6_llinfo_settimer() is called not only when I start ppp, > but at bootup too (at bootup - once, I think that this is due to > initializing lo0 interface, which has a default ipv6 address). Could I > somehow make the kernel not panic at boot time and panic later, when I > call ppp? You can either add a sysctl that starts off as 0 and only panic if the sysctl is 1. You can then boot, change the sysctl to 1, and then run ppp. Alternatively, you could use kdb_enter() to enter the debugger instead of panic(). You could then just continue using 'c' when you drop into ddb during boot. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 15:33:32 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E67B616A41F for ; Thu, 3 Nov 2005 15:33:32 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 479FC43D67 for ; Thu, 3 Nov 2005 15:33:29 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 03 Nov 2005 15:33:28 -0000 Received: from fwswe.rise-s.com (EHLO dhcp151.swe) [83.65.168.194] by mail.gmx.net (mp004) with SMTP; 03 Nov 2005 16:33:28 +0100 X-Authenticated: #16703784 From: Stefan Ehmann To: Giorgos Keramidas In-Reply-To: <20051103142446.GA1787@flame.pc> References: <971FCB6690CD0E4898387DBF7552B90E0346CAFB@orsmsx403.amr.corp.intel.com> <20051103.094643.74756456.haro@h4.dion.ne.jp> <436961FD.3040605@root.org> <20051103014740.GA1586@flame.pc> <20051103142446.GA1787@flame.pc> Content-Type: text/plain Date: Thu, 03 Nov 2005 16:33:26 +0100 Message-Id: <1131032006.648.4.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: Munehiro Matsuda , freebsd-acpi@freebsd.org, robert.moore@intel.com, freebsd-current@freebsd.org, Nate Lawson , jkim@freebsd.org Subject: Re: Panic on boot with new ACPI-CA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 15:33:33 -0000 On Thu, 2005-11-03 at 16:24 +0200, Giorgos Keramidas wrote: > On 2005-11-03 03:47, Giorgos Keramidas wrote: > >On 2005-11-02 17:03, Nate Lawson wrote: > >> As I mentioned to Jung-uk, the problem is likely an error in > >> acpi-ca modifying memory after it has freed it. The way to > >> track this down is to enable memguard(9). See the man page for > >> info. You need to add options DEBUG_MEMGUARD to your kernel, > >> set the malloc type to watch to M_ACPICA, and rebuild your > >> kernel and modules. Memguard sets page permissions so we can > >> catch the culprit who is modifying the memory. > > > > This is exactly the messgae printed on my console at panic time > > -- of memory modified after free. I'm building a kernel with > > MEMGUARD now, but it's probably going to be a bit hard to get a > > kernel dump, because the panic happens before disks are > > available and I don't have a serial console here. > > This is definitely something that is ACPI-related. I updated my > sources to the last commit before the start of the ACPI import: > > build@flame:/home/build/src$ cvs -qR up -APd -D '2005/11/01 22:00:00 UTC' > > Rebuilt everything and I see no panics now. > > I'll use the watchpoint trick Nate posted when I have a new build > to test. > Just tried reverting, and my problem reported in http://lists.freebsd.org/pipermail/freebsd-current/2005-November/057596.html is also ACPI-related. It also happens early on boot but panic is different (in devfs_populate_loop()). Don't know if it's related or a different bug introduced by the ACPI-CA import. From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 15:43:24 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5B0016A41F; Thu, 3 Nov 2005 15:43:24 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail5.speedfactory.net [66.23.216.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2A5043D45; Thu, 3 Nov 2005 15:43:23 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 1306560 for multiple; Thu, 03 Nov 2005 10:41:22 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jA3FhHjv065953; Thu, 3 Nov 2005 10:43:17 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-acpi@freebsd.org Date: Thu, 3 Nov 2005 10:43:10 -0500 User-Agent: KMail/1.8.2 References: <971FCB6690CD0E4898387DBF7552B90E0346CAFB@orsmsx403.amr.corp.intel.com> <20051103142446.GA1787@flame.pc> <20051103144013.GA43086@peter.osted.lan> In-Reply-To: <20051103144013.GA43086@peter.osted.lan> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511031043.13285.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=100 Cc: freebsd-current@freebsd.org, Giorgos Keramidas , jkim@freebsd.org, robert.moore@intel.com Subject: Re: Panic on boot with new ACPI-CA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 15:43:25 -0000 On Thursday 03 November 2005 09:40 am, Peter Holm wrote: > On Thu, Nov 03, 2005 at 04:24:46PM +0200, Giorgos Keramidas wrote: > > On 2005-11-03 03:47, Giorgos Keramidas wrote: > > >On 2005-11-02 17:03, Nate Lawson wrote: > > >> As I mentioned to Jung-uk, the problem is likely an error in > > >> acpi-ca modifying memory after it has freed it. The way to > > >> track this down is to enable memguard(9). See the man page for > > >> info. You need to add options DEBUG_MEMGUARD to your kernel, > > >> set the malloc type to watch to M_ACPICA, and rebuild your > > >> kernel and modules. Memguard sets page permissions so we can > > >> catch the culprit who is modifying the memory. > > > > > > This is exactly the messgae printed on my console at panic time > > > -- of memory modified after free. I'm building a kernel with > > > MEMGUARD now, but it's probably going to be a bit hard to get a > > > kernel dump, because the panic happens before disks are > > > available and I don't have a serial console here. > > > > This is definitely something that is ACPI-related. I updated my > > sources to the last commit before the start of the ACPI import: > > > > build@flame:/home/build/src$ cvs -qR up -APd -D '2005/11/01 22:00:00 > > UTC' > > > > Rebuilt everything and I see no panics now. > > > > I'll use the watchpoint trick Nate posted when I have a new build > > to test. > > I've had the same problem with two of my boxes. Here's the result of a > watchpoint: > > http://people.freebsd.org/~pho/stress/log/acpi.html > > I too came to the conclusion that the damage happened between > > 2005-11-01 22:00:00 UTC OK > 2005-11-01 22:45:00 UTC panic Does this diff make a difference perhaps? Index: acpi_resource.c =================================================================== RCS file: /usr/cvs/src/sys/dev/acpica/acpi_resource.c,v retrieving revision 1.35 diff -u -r1.35 acpi_resource.c --- acpi_resource.c 11 Sep 2005 18:39:01 -0000 1.35 +++ acpi_resource.c 3 Nov 2005 15:42:14 -0000 @@ -168,6 +168,7 @@ /* Fetch the device's current resources. */ buf.Length = ACPI_ALLOCATE_BUFFER; + buf.Pointer = NULL; if (ACPI_FAILURE((status = AcpiGetCurrentResources(handle, &buf)))) { if (status != AE_NOT_FOUND) printf("can't fetch resources for %s - %s\n", -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 16:14:15 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 484CD16A422 for ; Thu, 3 Nov 2005 16:14:15 +0000 (GMT) (envelope-from pho@holm.cc) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.FreeBSD.org (Postfix) with SMTP id E5B7143D49 for ; Thu, 3 Nov 2005 16:14:12 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 47766 invoked from network); 3 Nov 2005 16:14:11 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 3 Nov 2005 16:14:11 -0000 X-pair-Authenticated: 80.161.118.233 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id jA3GEAp7043564; Thu, 3 Nov 2005 17:14:10 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id jA3GEANk043563; Thu, 3 Nov 2005 17:14:10 +0100 (CET) (envelope-from pho) Date: Thu, 3 Nov 2005 17:14:10 +0100 From: Peter Holm To: John Baldwin Message-ID: <20051103161410.GA43544@peter.osted.lan> References: <971FCB6690CD0E4898387DBF7552B90E0346CAFB@orsmsx403.amr.corp.intel.com> <20051103142446.GA1787@flame.pc> <20051103144013.GA43086@peter.osted.lan> <200511031043.13285.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200511031043.13285.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org, Giorgos Keramidas , jkim@freebsd.org, robert.moore@intel.com Subject: Re: Panic on boot with new ACPI-CA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 16:14:15 -0000 On Thu, Nov 03, 2005 at 10:43:10AM -0500, John Baldwin wrote: > On Thursday 03 November 2005 09:40 am, Peter Holm wrote: > > On Thu, Nov 03, 2005 at 04:24:46PM +0200, Giorgos Keramidas wrote: > > > On 2005-11-03 03:47, Giorgos Keramidas wrote: > > > >On 2005-11-02 17:03, Nate Lawson wrote: > > > >> As I mentioned to Jung-uk, the problem is likely an error in > > > >> acpi-ca modifying memory after it has freed it. The way to > > > >> track this down is to enable memguard(9). See the man page for > > > >> info. You need to add options DEBUG_MEMGUARD to your kernel, > > > >> set the malloc type to watch to M_ACPICA, and rebuild your > > > >> kernel and modules. Memguard sets page permissions so we can > > > >> catch the culprit who is modifying the memory. > > > > > > > > This is exactly the messgae printed on my console at panic time > > > > -- of memory modified after free. I'm building a kernel with > > > > MEMGUARD now, but it's probably going to be a bit hard to get a > > > > kernel dump, because the panic happens before disks are > > > > available and I don't have a serial console here. > > > > > > This is definitely something that is ACPI-related. I updated my > > > sources to the last commit before the start of the ACPI import: > > > > > > build@flame:/home/build/src$ cvs -qR up -APd -D '2005/11/01 22:00:00 > > > UTC' > > > > > > Rebuilt everything and I see no panics now. > > > > > > I'll use the watchpoint trick Nate posted when I have a new build > > > to test. > > > > I've had the same problem with two of my boxes. Here's the result of a > > watchpoint: > > > > http://people.freebsd.org/~pho/stress/log/acpi.html > > > > I too came to the conclusion that the damage happened between > > > > 2005-11-01 22:00:00 UTC OK > > 2005-11-01 22:45:00 UTC panic > > Does this diff make a difference perhaps? > It did not make any difference as far as I can tell. - Peter > Index: acpi_resource.c > =================================================================== > RCS file: /usr/cvs/src/sys/dev/acpica/acpi_resource.c,v > retrieving revision 1.35 > diff -u -r1.35 acpi_resource.c > --- acpi_resource.c 11 Sep 2005 18:39:01 -0000 1.35 > +++ acpi_resource.c 3 Nov 2005 15:42:14 -0000 > @@ -168,6 +168,7 @@ > > /* Fetch the device's current resources. */ > buf.Length = ACPI_ALLOCATE_BUFFER; > + buf.Pointer = NULL; > if (ACPI_FAILURE((status = AcpiGetCurrentResources(handle, &buf)))) { > if (status != AE_NOT_FOUND) > printf("can't fetch resources for %s - %s\n", > > > -- > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 16:21:30 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5F0E16A41F for ; Thu, 3 Nov 2005 16:21:30 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A04743D45 for ; Thu, 3 Nov 2005 16:21:30 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.200] ([10.0.0.200]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id jA3GLSpU081163 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Nov 2005 08:21:29 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <436A38FA.1020203@errno.com> Date: Thu, 03 Nov 2005 08:21:14 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050927) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Geir Egeland References: <4369EA8D.4000506@gmail.com> In-Reply-To: <4369EA8D.4000506@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: wireless Media Extensions (wme) and freebsd 6.0-rc1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 16:21:31 -0000 Geir Egeland wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > I've been playing around with freebsd 6.0-rc1, and I noticed that > ifconfig has support for Wireless Media Extensions (WME). Has anyone > tested this functionality, and are there any WME enabled pcmcia cards > available that also are supported by FreeBSD ? I have verified basic functionality. I'm not aware of any apps that make use of it. All atheros-5212-based cards do wme correctly though you may hit snags if you do wme and wpa together on some cards. Sam From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 16:27:23 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 851BF16A41F; Thu, 3 Nov 2005 16:27:23 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail5.speedfactory.net [66.23.216.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A5C543D49; Thu, 3 Nov 2005 16:27:21 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 1309179 for multiple; Thu, 03 Nov 2005 11:25:18 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jA3GRDWI066215; Thu, 3 Nov 2005 11:27:13 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Peter Holm Date: Thu, 3 Nov 2005 11:25:27 -0500 User-Agent: KMail/1.8.2 References: <971FCB6690CD0E4898387DBF7552B90E0346CAFB@orsmsx403.amr.corp.intel.com> <200511031043.13285.jhb@freebsd.org> <20051103161410.GA43544@peter.osted.lan> In-Reply-To: <20051103161410.GA43544@peter.osted.lan> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511031125.29771.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=100 Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org, Giorgos Keramidas , jkim@freebsd.org, robert.moore@intel.com Subject: Re: Panic on boot with new ACPI-CA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 16:27:23 -0000 On Thursday 03 November 2005 11:14 am, Peter Holm wrote: > On Thu, Nov 03, 2005 at 10:43:10AM -0500, John Baldwin wrote: > > On Thursday 03 November 2005 09:40 am, Peter Holm wrote: > > > On Thu, Nov 03, 2005 at 04:24:46PM +0200, Giorgos Keramidas wrote: > > > > On 2005-11-03 03:47, Giorgos Keramidas wrote: > > > > >On 2005-11-02 17:03, Nate Lawson wrote: > > > > >> As I mentioned to Jung-uk, the problem is likely an error in > > > > >> acpi-ca modifying memory after it has freed it. The way to > > > > >> track this down is to enable memguard(9). See the man page for > > > > >> info. You need to add options DEBUG_MEMGUARD to your kernel, > > > > >> set the malloc type to watch to M_ACPICA, and rebuild your > > > > >> kernel and modules. Memguard sets page permissions so we can > > > > >> catch the culprit who is modifying the memory. > > > > > > > > > > This is exactly the messgae printed on my console at panic time > > > > > -- of memory modified after free. I'm building a kernel with > > > > > MEMGUARD now, but it's probably going to be a bit hard to get a > > > > > kernel dump, because the panic happens before disks are > > > > > available and I don't have a serial console here. > > > > > > > > This is definitely something that is ACPI-related. I updated my > > > > sources to the last commit before the start of the ACPI import: > > > > > > > > build@flame:/home/build/src$ cvs -qR up -APd -D '2005/11/01 > > > > 22:00:00 UTC' > > > > > > > > Rebuilt everything and I see no panics now. > > > > > > > > I'll use the watchpoint trick Nate posted when I have a new build > > > > to test. > > > > > > I've had the same problem with two of my boxes. Here's the result of a > > > watchpoint: > > > > > > http://people.freebsd.org/~pho/stress/log/acpi.html > > > > > > I too came to the conclusion that the damage happened between > > > > > > 2005-11-01 22:00:00 UTC OK > > > 2005-11-01 22:45:00 UTC panic > > > > Does this diff make a difference perhaps? > > It did not make any difference as far as I can tell. Ok, it was more of a guess anyway that perhaps ACPICA was reusing the garbage in buf.Pointer. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 17:29:31 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2320B16A41F for ; Thu, 3 Nov 2005 17:29:31 +0000 (GMT) (envelope-from incmc@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 4E32A43D45 for ; Thu, 3 Nov 2005 17:29:29 +0000 (GMT) (envelope-from incmc@gmx.de) Received: (qmail invoked by alias); 03 Nov 2005 17:29:28 -0000 Received: from dslb-084-061-054-040.pools.arcor-ip.net (EHLO ms.homeip.net) [84.61.54.40] by mail.gmx.net (mp002) with SMTP; 03 Nov 2005 18:29:28 +0100 X-Authenticated: #15946415 Received: from id4cc1774.versanet.de ([212.204.23.116] helo=nix-rechnername-auspaehen-hier) by ms.homeip.net with esmtpsa (SSLv3:RC4-MD5:128) id 1EXiu4-000BO1-8U for freebsd-current@freebsd.org; Thu, 03 Nov 2005 18:29:32 +0100 From: Jochen Gensch To: freebsd-current@freebsd.org Date: Thu, 3 Nov 2005 18:29:08 +0100 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511031829.09155.incmc@gmx.de> X-Y-GMX-Trusted: 0 Subject: Re: where is the BEASTIE??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 17:29:31 -0000 > I've just cvsuped and rebuilt my system from 6.0-RC1 to 6.0-STABLE, > and I've noticed "FreeBSD" ASCII logo in bootloader menu instead of > good old red Beastie... How can I take the Beastie back? ;) Where do you see any menu? I don't see anything of that kind here!? Jochen From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 17:42:32 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F61616A41F for ; Thu, 3 Nov 2005 17:42:32 +0000 (GMT) (envelope-from freebsd@powered.net) Received: from valimar.ibest.com.br (mx11.ibest.com.br [200.181.68.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3C3043D48 for ; Thu, 3 Nov 2005 17:42:30 +0000 (GMT) (envelope-from freebsd@powered.net) Received: from [127.0.0.1] (centaurus.ibest.com.br [200.181.68.107]) by valimar.ibest.com.br (Postfix) with ESMTP id 133C917BE2D; Thu, 3 Nov 2005 15:42:11 -0200 (BRDT) Message-ID: <436A4BE5.8090109@powered.net> Date: Thu, 03 Nov 2005 15:41:57 -0200 From: Rainer Alves User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050930) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jochen Gensch References: <200511031829.09155.incmc@gmx.de> In-Reply-To: <200511031829.09155.incmc@gmx.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-iBEST-MailScanner-Information: Please contact the ISP for more information X-MailScanner-From: freebsd@powered.net Cc: freebsd-current@freebsd.org Subject: Re: where is the BEASTIE??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 17:42:32 -0000 Jochen Gensch wrote: >>I've just cvsuped and rebuilt my system from 6.0-RC1 to 6.0-STABLE, >>and I've noticed "FreeBSD" ASCII logo in bootloader menu instead of >>good old red Beastie... How can I take the Beastie back? ;) >> >> > >Where do you see any menu? I don't see anything of that kind here!? > > Build/install world, you'll have a /boot/beastie.4th with the new ASCII logo. The diff is here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/boot/forth/beastie.4th.diff?r1=1.10&r2=1.11 --- Rainer Alves BrasilTelecom From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 18:39:07 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4460516A41F; Thu, 3 Nov 2005 18:39:07 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail5.speedfactory.net [66.23.216.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE68943D46; Thu, 3 Nov 2005 18:39:06 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 1316624 for multiple; Thu, 03 Nov 2005 13:37:05 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jA3Id2Lq066865; Thu, 3 Nov 2005 13:39:02 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org, lonnie.vanzandt@ngc.com Date: Thu, 3 Nov 2005 13:27:13 -0500 User-Agent: KMail/1.8.2 References: <200509220742.10364.lonnie.vanzandt@ngc.com> In-Reply-To: <200509220742.10364.lonnie.vanzandt@ngc.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511031327.18011.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=100 Cc: marcel@freebsd.org Subject: Re: Cdiff patch for kernel gdb and mi_switch panic in freebsd 5.4 STABLE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 18:39:07 -0000 On Sunday 09 October 2005 05:49 pm, Lonnie VanZandt wrote: > Attached is the patch for the revised subr_kdb.c from FreeBSD 5.4 STABLE. > (the rcsid is __FBSDID("$FreeBSD: src/sys/kern/subr_kdb.c,v 1.5.2.2.2.1 > 2005/05/01 05:38:14 dwhite Exp $"); ) I've looked at this, but I think t could maybe be done slightly differently. Here's a suggested patch that would close the race you are seeing I think while allowing semantics such that if two CPUs try to enter KDB at the same time, they would serialize and the second CPU would enter kdb after the first had exited. Could you at least test it to see if it addresses your race condition? --- //depot/projects/smpng/sys/kern/subr_kdb.c 2005/10/27 19:51:50 +++ //depot/user/jhb/ktrace/kern/subr_kdb.c 2005/11/03 18:24:38 @@ -39,6 +39,7 @@ #include #include +#include #include #include @@ -462,12 +463,21 @@ return (0); /* We reenter the debugger through kdb_reenter(). */ - if (kdb_active) + if (kdb_active == PCPU_GET(cpuid) + 1) return (0); critical_enter(); - kdb_active++; + /* + * If more than one CPU tries to enter KDB at the same time + * then force them to serialize and go one at a time. + */ + while (!atomic_cmpset_int(&kdb_active, 0, PCPU_GET(cpuid) + 1)) { + critical_exit(); + while (kdb_active) + cpu_spinwait(); + critical_enter(); + } #ifdef SMP if ((did_stop_cpus = kdb_stop_cpus) != 0) @@ -484,13 +494,17 @@ handled = kdb_dbbe->dbbe_trap(type, code); + /* + * We have to exit KDB before resuming the other CPUs so that they + * may run in a debugger-less context. + */ + kdb_active = 0; + #ifdef SMP if (did_stop_cpus) restart_cpus(stopped_cpus); #endif - kdb_active--; - critical_exit(); return (handled); -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 19:19:08 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 63DB116A41F for ; Thu, 3 Nov 2005 19:19:08 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from indor.net.tomline.ru (indor.net.tomline.ru [213.183.100.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93BDA43D45 for ; Thu, 3 Nov 2005 19:19:06 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from SNEZHKO by indorsoft.ru (MDaemon.PRO.v7.2.2.R) with ESMTP id md50000027564.msg for ; Fri, 04 Nov 2005 01:18:59 +0600 X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 88046, updated: 3.11.2005] To: freebsd-current@freebsd.org References: From: Victor Snezhko Date: Fri, 04 Nov 2005 01:18:54 +0600 In-Reply-To: (Victor Snezhko's message of "Thu, 03 Nov 2005 12:28:30 +0600") Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Processed: indor.net.tomline.ru, Fri, 04 Nov 2005 01:18:59 +0600 (not processed: spam filter disabled) X-Return-Path: snezhko@indorsoft.ru X-MDaemon-Deliver-To: freebsd-current@freebsd.org X-VVS-Spam: false Subject: [SOLVED] kgdb strange behaviour on current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 19:19:08 -0000 Victor Snezhko writes: > (kgdb) list > 215 curticks = softticks; > 216 bucket = &callwheel[curticks & callwheelmask]; > 217 c = TAILQ_FIRST(bucket); > 218 while (c) { > 219 depth++; > 220 if (c->c_time != curticks) { > 221 c = TAILQ_NEXT(c, c_links.tqe); > 222 ++steps; > 223 if (steps >= MAX_SOFTCLOCK_STEPS) { > 224 nextsoftcheck = c; > (kgdb) print c > $1 = (struct callout *) 0xdeadc0de > (kgdb) print bucket->tqh_first > $2 = (struct callout *) 0xc18eb520 > (kgdb) print *(bucket->tqh_first) > $3 = {c_links = {sle = {sle_next = 0xdeadc0de}, tqe = {tqe_next = 0xdeadc0de, > tqe_prev = 0xdeadc0de}}, c_time = -559038242, c_arg = 0xdeadc0de, > c_func = 0xdeadc0de, c_mtx = 0xdeadc0de, c_flags = -559038242} > (kgdb) print bucket > $4 = (struct callout_tailq *) 0xc66021e8 > (kgdb) quit > > /home/vvs # grep "#define.*[^S]TAILQ_FIRST" /usr/src/sys/sys/queue.h > #define TAILQ_FIRST(head) ((head)->tqh_first) > > bucket->tqh_first seems to be a valid pointer, but points to > garbage. But c should be the same pointer, and debugger shows a > distinct value for it! kgdb works fine, I misunderstood the moment of time when crash occured. -- WBR, Victor V. Snezhko EMail: snezhko@indorsoft.ru From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 19:28:55 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F93C16A41F for ; Thu, 3 Nov 2005 19:28:55 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from indor.net.tomline.ru (indor.net.tomline.ru [213.183.100.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6079343D45 for ; Thu, 3 Nov 2005 19:28:54 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from SNEZHKO by indorsoft.ru (MDaemon.PRO.v7.2.2.R) with ESMTP id md50000027567.msg for ; Fri, 04 Nov 2005 01:28:44 +0600 X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 88046, updated: 3.11.2005] To: freebsd-current@freebsd.org References: <20051027022313.R675@kushnir1.kiev.ua> <200511021035.22990.max@love2party.net> <20051103001509.C85422@kushnir1.kiev.ua> <200511030059.05946.max@love2party.net> From: Victor Snezhko Date: Fri, 04 Nov 2005 01:28:39 +0600 In-Reply-To: <200511030059.05946.max@love2party.net> (Max Laier's message of "Thu, 3 Nov 2005 00:58:48 +0100") Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Processed: indor.net.tomline.ru, Fri, 04 Nov 2005 01:28:45 +0600 (not processed: spam filter disabled) X-Return-Path: snezhko@indorsoft.ru X-MDaemon-Deliver-To: freebsd-current@freebsd.org X-VVS-Spam: false Cc: Max Laier Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 19:28:55 -0000 Max Laier writes: >> > That brings me back to ln_timer_ch as the culprit. Could you please >> > build with this patch and get me the console output shortly before the >> > panic? >> >> Here it is: right before panic it prints >> >> For 0xffffff0017531100 -1 ticks >> For 0xffffff0017531100 -1 ticks > > This results in two consecutive callout_stop() calls, but shouldn't hurt as > callout_stop is protected against that. > > Do you get a dump for this? Can you compare this pointer to the global > llinfo_nd6 and see if "c" from the softclock() frame is related (or > maybe the previous item in the list TAILQ). I have finally analysed this. Applied the following patch with more verbose printf against 1.62: --- nd6-1.62.c Fri Nov 4 01:14:50 2005 +++ nd6.c Fri Nov 4 01:02:30 2005 @@ -1,4 +1,4 @@ -/* $FreeBSD: /repoman/r/ncvs/src/sys/netinet6/nd6.c,v 1.62 2005/10/22 05:07:16 suz Exp $ */ +/* $FreeBSD: src/sys/netinet6/nd6.c,v 1.62 2005/10/22 05:07:16 suz Exp $ */ /* $KAME: nd6.c,v 1.144 2001/05/24 07:44:00 itojun Exp $ */ /*- @@ -49,6 +49,7 @@ #include #include #include +#include #include #include @@ -395,6 +396,9 @@ struct llinfo_nd6 *ln; long tick; { + printf("For %p %ld (llinfo_nd6=%p, prev=%p, next=%p)\n", \ + ln, tick, &llinfo_nd6, llinfo_nd6.ln_prev, llinfo_nd6.ln_next); + kdb_enter("in nd6_llinfo_settimer"); if (tick < 0) { ln->ln_expire = 0; ln->ln_ntick = 0; Thanks to John Baldwin, kdb_enter is really helpful. Here are the results of the first call (at lo0 initialization): For 0xc17722c0 -1 (llinfo_nd6 = 0xc090eac0, prev=0xc17722c0, next=0xc17722c0) And here - the results of two consecutive calls (at ppp startup, later in the same session): For 0xc188e840 -1 (llinfo_nd6 = 0xc090eac0, prev=0xc17722c0, next=0xc188e840) For 0xc188e840 -1 (llinfo_nd6 = 0xc090eac0, prev=0xc17722c0, next=0xc17722c0) As we can see, ln formal parameter is certainly related to the global llinfo_nd6, but (see crashdump below) I can't find any relation to the "c" from softclock(), pointers there are distinct from any of llinfo_nd6 members I have seen. I can obtain crashdumps for both consecutive calls if somebody thinks there is something broken here, but it seems unrelated to the trap in question. What else can I do? Here is brief softclock() crashdump brief analysis: ~ # kgdb /usr/obj/usr/src/sys/VVS/kernel.debug /var/crash/vmcore.7 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xdeadc0e6 fault code = supervisor read, page not present instruction pointer = 0x20:0xc066e0c2 stack pointer = 0x28:0xcbfd3cac frame pointer = 0x28:0xcbfd3cd4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 12 (swi4: clock sio) panic: from debugger cpuid = 0 Uptime: 45s Dumping 255 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 255MB (65264 pages) 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:165 165 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:165 #1 0xc06613fc in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399 #2 0xc0661711 in panic (fmt=0xc08594a0 "from debugger") at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xc046d151 in db_panic (addr=-1066999614, have_addr=0, count=-1, modif=0xcbfd3aa8 "") at /usr/src/sys/ddb/db_command.c:435 #4 0xc046d0e8 in db_command (last_cmdp=0xc094a1a4, cmd_table=0x0, aux_cmd_tablep=0xc08c009c, aux_cmd_tablep_end=0xc08c00b8) at /usr/src/sys/ddb/db_command.c:404 #5 0xc046d1b0 in db_command_loop () at /usr/src/sys/ddb/db_command.c:455 #6 0xc046edc9 in db_trap (type=12, code=0) at /usr/src/sys/ddb/db_main.c:221 #7 0xc067b408 in kdb_trap (type=12, code=0, tf=0xcbfd3c6c) at /usr/src/sys/kern/subr_kdb.c:485 #8 0xc0823f88 in trap_fatal (frame=0xcbfd3c6c, eva=3735929062) at /usr/src/sys/i386/i386/trap.c:846 #9 0xc0823612 in trap (frame= {tf_fs = 8, tf_es = -872611800, tf_ds = -1067122648, tf_edi = -1049930560, tf_esi = -1051228800, tf_ebp = -872596268, tf_isp = -872596328, tf_ebx = 1, tf_edx = -966781544, tf_ecx = -559038242, tf_eax = 43761, tf_trapno = 12, tf_err = 0, tf_eip = -1066999614, tf_cs = 32, tf_eflags = 589826, tf_esp = -1051359088, tf_ss = 0}) at /usr/src/sys/i386/i386/trap.c:269 #10 0xc0810e4a in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #11 0xc066e0c2 in softclock (dummy=0x0) at /usr/src/sys/kern/kern_timeout.c:220 #12 0xc064ed32 in ithread_execute_handlers (p=0xc1558890, ie=0xc1578580) at /usr/src/sys/kern/kern_intr.c:662 #13 0xc064ee63 in ithread_loop (arg=0xc151f8e0) at /usr/src/sys/kern/kern_intr.c:745 #14 0xc064dfc4 in fork_exit (callout=0xc064edfc , arg=0xc151f8e0, frame=0xcbfd3d38) at /usr/src/sys/kern/kern_fork.c:789 #15 0xc0810eac in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:208 (kgdb) up 11 #11 0xc066e0c2 in softclock (dummy=0x0) at /usr/src/sys/kern/kern_timeout.c:220 220 if (c->c_time != curticks) { (kgdb) list 215 curticks = softticks; 216 bucket = &callwheel[curticks & callwheelmask]; 217 c = TAILQ_FIRST(bucket); 218 while (c) { 219 depth++; 220 if (c->c_time != curticks) { 221 c = TAILQ_NEXT(c, c_links.tqe); 222 ++steps; 223 if (steps >= MAX_SOFTCLOCK_STEPS) { 224 nextsoftcheck = c; (kgdb) print *bucket $1 = {tqh_first = 0xc1891d80, tqh_last = 0xc1891d80} (kgdb) print c $2 = (struct callout *) 0xdeadc0de (kgdb) print *(bucket->tqh_first) $3 = {c_links = {sle = {sle_next = 0xdeadc0de}, tqe = {tqe_next = 0xdeadc0de, tqe_prev = 0xdeadc0de}}, c_time = -559038242, c_arg = 0xdeadc0de, c_func = 0xdeadc0de, c_mtx = 0xdeadc0de, c_flags = -559038242} (kgdb) print steps $4 = 1 -- WBR, Victor V. Snezhko EMail: snezhko@indorsoft.ru From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 19:31:58 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 047A516A43E; Thu, 3 Nov 2005 19:31:58 +0000 (GMT) (envelope-from Lonnie.Vanzandt@ngc.com) Received: from xcgmd812.northgrum.com (xcgmd812.northgrum.com [155.104.240.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3615743D46; Thu, 3 Nov 2005 19:31:56 +0000 (GMT) (envelope-from Lonnie.Vanzandt@ngc.com) Received: from xbhm0001.northgrum.com ([155.104.118.90]) by xcgmd812.northgrum.com with InterScan Messaging Security Suite; Thu, 03 Nov 2005 11:32:52 -0800 Received: from xcgco501.northgrum.com ([158.114.104.53]) by xbhm0001.northgrum.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 3 Nov 2005 11:31:54 -0800 Received: from [192.168.170.128] ([158.114.106.12]) by xcgco501.northgrum.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 3 Nov 2005 12:30:33 -0700 From: Lonnie VanZandt Organization: Northrop Grumman To: John Baldwin Date: Thu, 3 Nov 2005 12:29:52 -0700 User-Agent: KMail/1.8.1 References: <200509220742.10364.lonnie.vanzandt@ngc.com> <200511031327.18011.jhb@freebsd.org> In-Reply-To: <200511031327.18011.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511031229.53501.lonnie.vanzandt@ngc.com> X-OriginalArrivalTime: 03 Nov 2005 19:30:33.0452 (UTC) FILETIME=[0EF04AC0:01C5E0AD] Cc: freebsd-current@freebsd.org, marcel@freebsd.org Subject: Re: Cdiff patch for kernel gdb and mi_switch panic in freebsd 5.4 STABLE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lonnie.vanzandt@ngc.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 19:31:58 -0000 I think I follow the proposal. Sure, I'll apply your patch and run with it on my SMP box. It may take a while to reach a conclusion on its merits due to the racy nature of the crash. On Thursday 03 November 2005 11:27 am, John Baldwin wrote: > On Sunday 09 October 2005 05:49 pm, Lonnie VanZandt wrote: > > Attached is the patch for the revised subr_kdb.c from FreeBSD 5.4 STABLE. > > (the rcsid is __FBSDID("$FreeBSD: src/sys/kern/subr_kdb.c,v 1.5.2.2.2.1 > > 2005/05/01 05:38:14 dwhite Exp $"); ) > > I've looked at this, but I think t could maybe be done slightly > differently. Here's a suggested patch that would close the race you are > seeing I think while allowing semantics such that if two CPUs try to enter > KDB at the same time, they would serialize and the second CPU would enter > kdb after the first had exited. Could you at least test it to see if it > addresses your race condition? > > --- //depot/projects/smpng/sys/kern/subr_kdb.c 2005/10/27 19:51:50 > +++ //depot/user/jhb/ktrace/kern/subr_kdb.c 2005/11/03 18:24:38 > @@ -39,6 +39,7 @@ > #include > #include > > +#include > #include > #include > > @@ -462,12 +463,21 @@ > return (0); > > /* We reenter the debugger through kdb_reenter(). */ > - if (kdb_active) > + if (kdb_active == PCPU_GET(cpuid) + 1) > return (0); > > critical_enter(); > > - kdb_active++; > + /* > + * If more than one CPU tries to enter KDB at the same time > + * then force them to serialize and go one at a time. > + */ > + while (!atomic_cmpset_int(&kdb_active, 0, PCPU_GET(cpuid) + 1)) { > + critical_exit(); > + while (kdb_active) > + cpu_spinwait(); > + critical_enter(); > + } > > #ifdef SMP > if ((did_stop_cpus = kdb_stop_cpus) != 0) > @@ -484,13 +494,17 @@ > > handled = kdb_dbbe->dbbe_trap(type, code); > > + /* > + * We have to exit KDB before resuming the other CPUs so that they > + * may run in a debugger-less context. > + */ > + kdb_active = 0; > + > #ifdef SMP > if (did_stop_cpus) > restart_cpus(stopped_cpus); > #endif > > - kdb_active--; > - > critical_exit(); > > return (handled); From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 20:00:38 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 65D0216A439 for ; Thu, 3 Nov 2005 20:00:38 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail5.speedfactory.net [66.23.216.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C6ED43D75 for ; Thu, 3 Nov 2005 20:00:17 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 1320983 for multiple; Thu, 03 Nov 2005 14:58:13 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jA3K066j067322; Thu, 3 Nov 2005 15:00:06 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Thu, 3 Nov 2005 14:59:59 -0500 User-Agent: KMail/1.8.2 References: <20051027022313.R675@kushnir1.kiev.ua> <200511030059.05946.max@love2party.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511031500.00839.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=100 Cc: Max Laier , Victor Snezhko Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 20:00:38 -0000 On Thursday 03 November 2005 02:28 pm, Victor Snezhko wrote: > Max Laier writes: > >> > That brings me back to ln_timer_ch as the culprit. Could you please > >> > build with this patch and get me the console output shortly before the > >> > panic? > >> > >> Here it is: right before panic it prints > >> > >> For 0xffffff0017531100 -1 ticks > >> For 0xffffff0017531100 -1 ticks > > > > This results in two consecutive callout_stop() calls, but shouldn't hurt > > as callout_stop is protected against that. > > > > Do you get a dump for this? Can you compare this pointer to the global > > llinfo_nd6 and see if "c" from the softclock() frame is related (or > > maybe the previous item in the list TAILQ). > > I have finally analysed this. > > Applied the following patch with more verbose printf against 1.62: > > --- nd6-1.62.c Fri Nov 4 01:14:50 2005 > +++ nd6.c Fri Nov 4 01:02:30 2005 > @@ -1,4 +1,4 @@ > -/* $FreeBSD: /repoman/r/ncvs/src/sys/netinet6/nd6.c,v 1.62 2005/10/22 > 05:07:16 suz Exp $ */ +/* $FreeBSD: src/sys/netinet6/nd6.c,v 1.62 > 2005/10/22 05:07:16 suz Exp $ */ /* $KAME: nd6.c,v 1.144 2001/05/24 > 07:44:00 itojun Exp $ */ > > /*- > @@ -49,6 +49,7 @@ > #include > #include > #include > +#include > > #include > #include > @@ -395,6 +396,9 @@ > struct llinfo_nd6 *ln; > long tick; > { > + printf("For %p %ld (llinfo_nd6=%p, prev=%p, next=%p)\n", \ > + ln, tick, &llinfo_nd6, llinfo_nd6.ln_prev, llinfo_nd6.ln_next); > + kdb_enter("in nd6_llinfo_settimer"); > if (tick < 0) { > ln->ln_expire = 0; > ln->ln_ntick = 0; > > Thanks to John Baldwin, kdb_enter is really helpful. > > Here are the results of the first call (at lo0 initialization): > For 0xc17722c0 -1 (llinfo_nd6 = 0xc090eac0, prev=0xc17722c0, > next=0xc17722c0) > > And here - the results of two consecutive calls (at ppp startup, later > in the same session): > For 0xc188e840 -1 (llinfo_nd6 = 0xc090eac0, prev=0xc17722c0, > next=0xc188e840) For 0xc188e840 -1 (llinfo_nd6 = 0xc090eac0, > prev=0xc17722c0, next=0xc17722c0) > > As we can see, ln formal parameter is certainly related to the global > llinfo_nd6, but (see crashdump below) I can't find any relation to the > "c" from softclock(), pointers there are distinct from any of > llinfo_nd6 members I have seen. > > I can obtain crashdumps for both consecutive calls if somebody thinks > there is something broken here, but it seems unrelated to the trap in > question. > > What else can I do? > > Here is brief softclock() crashdump brief analysis: > > ~ # kgdb /usr/obj/usr/src/sys/VVS/kernel.debug /var/crash/vmcore.7 > [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: > Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you > are welcome to change it and/or distribute copies of it under certain > conditions. Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-marcel-freebsd". > > Unread portion of the kernel message buffer: > kernel trap 12 with interrupts disabled > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xdeadc0e6 > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc066e0c2 > stack pointer = 0x28:0xcbfd3cac > frame pointer = 0x28:0xcbfd3cd4 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 12 (swi4: clock sio) > panic: from debugger > cpuid = 0 > Uptime: 45s > Dumping 255 MB (2 chunks) > chunk 0: 1MB (159 pages) ... ok > chunk 1: 255MB (65264 pages) 239 223 207 191 175 159 143 127 111 95 79 63 > 47 31 15 > > #0 doadump () at pcpu.h:165 > 165 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) bt > #0 doadump () at pcpu.h:165 > #1 0xc06613fc in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399 > #2 0xc0661711 in panic (fmt=0xc08594a0 "from debugger") > at /usr/src/sys/kern/kern_shutdown.c:555 > #3 0xc046d151 in db_panic (addr=-1066999614, have_addr=0, count=-1, > modif=0xcbfd3aa8 "") at /usr/src/sys/ddb/db_command.c:435 > #4 0xc046d0e8 in db_command (last_cmdp=0xc094a1a4, cmd_table=0x0, > aux_cmd_tablep=0xc08c009c, aux_cmd_tablep_end=0xc08c00b8) > at /usr/src/sys/ddb/db_command.c:404 > #5 0xc046d1b0 in db_command_loop () at /usr/src/sys/ddb/db_command.c:455 > #6 0xc046edc9 in db_trap (type=12, code=0) at > /usr/src/sys/ddb/db_main.c:221 #7 0xc067b408 in kdb_trap (type=12, code=0, > tf=0xcbfd3c6c) > at /usr/src/sys/kern/subr_kdb.c:485 > #8 0xc0823f88 in trap_fatal (frame=0xcbfd3c6c, eva=3735929062) > at /usr/src/sys/i386/i386/trap.c:846 > #9 0xc0823612 in trap (frame= > {tf_fs = 8, tf_es = -872611800, tf_ds = -1067122648, tf_edi = > -1049930560, tf_esi = -1051228800, tf_ebp = -872596268, tf_isp = > -872596328, tf_ebx = 1, tf_edx = -966781544, tf_ecx = -559038242, tf_eax = > 43761, tf_trapno = 12, tf_err = 0, tf_eip = -1066999614, tf_cs = 32, > tf_eflags = 589826, tf_esp = -1051359088, tf_ss = 0}) at > /usr/src/sys/i386/i386/trap.c:269 #10 0xc0810e4a in calltrap () at > /usr/src/sys/i386/i386/exception.s:139 #11 0xc066e0c2 in softclock > (dummy=0x0) at /usr/src/sys/kern/kern_timeout.c:220 #12 0xc064ed32 in > ithread_execute_handlers (p=0xc1558890, ie=0xc1578580) at > /usr/src/sys/kern/kern_intr.c:662 > #13 0xc064ee63 in ithread_loop (arg=0xc151f8e0) > at /usr/src/sys/kern/kern_intr.c:745 > #14 0xc064dfc4 in fork_exit (callout=0xc064edfc , > arg=0xc151f8e0, frame=0xcbfd3d38) at /usr/src/sys/kern/kern_fork.c:789 > #15 0xc0810eac in fork_trampoline () at > /usr/src/sys/i386/i386/exception.s:208 (kgdb) up 11 > #11 0xc066e0c2 in softclock (dummy=0x0) at > /usr/src/sys/kern/kern_timeout.c:220 220 if (c->c_time != curticks) { > (kgdb) list > 215 curticks = softticks; > 216 bucket = &callwheel[curticks & callwheelmask]; > 217 c = TAILQ_FIRST(bucket); > 218 while (c) { > 219 depth++; > 220 if (c->c_time != curticks) { > 221 c = TAILQ_NEXT(c, c_links.tqe); > 222 ++steps; > 223 if (steps >= MAX_SOFTCLOCK_STEPS) { > 224 nextsoftcheck = c; > (kgdb) print *bucket > $1 = {tqh_first = 0xc1891d80, tqh_last = 0xc1891d80} > (kgdb) print c > $2 = (struct callout *) 0xdeadc0de > (kgdb) print *(bucket->tqh_first) > $3 = {c_links = {sle = {sle_next = 0xdeadc0de}, tqe = {tqe_next = > 0xdeadc0de, tqe_prev = 0xdeadc0de}}, c_time = -559038242, c_arg = > 0xdeadc0de, c_func = 0xdeadc0de, c_mtx = 0xdeadc0de, c_flags = -559038242} > (kgdb) print steps > $4 = 1 Well, from thus it seems that a callout was free'd while it was still on the list. Perhaps there is a case wehre callout_stop() isn't called. Also, callout_drain() should really be used. If the callout function is rearming, then it might have been running when callout_stop() is called, and it could have rearmed itself and then been overwritten when it was freed. In fact, that is likely your problem. You can try this patch, but there might be lock order problems that would require the callout_drain() to happen later when locks aren't held: Index: nd6.c =================================================================== RCS file: /usr/cvs/src/sys/netinet6/nd6.c,v retrieving revision 1.62 diff -u -r1.62 nd6.c --- nd6.c 22 Oct 2005 05:07:16 -0000 1.62 +++ nd6.c 3 Nov 2005 19:56:42 -0000 @@ -398,7 +398,7 @@ if (tick < 0) { ln->ln_expire = 0; ln->ln_ntick = 0; - callout_stop(&ln->ln_timer_ch); + callout_drain(&ln->ln_timer_ch); } else { ln->ln_expire = time_second + tick / hz; if (tick > INT_MAX) { -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 20:45:22 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0448216A41F; Thu, 3 Nov 2005 20:45:22 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 880D543D46; Thu, 3 Nov 2005 20:45:18 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id jA3KsEXo057954; Thu, 3 Nov 2005 15:54:14 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-current@FreeBSD.org Date: Thu, 3 Nov 2005 15:45:03 -0500 User-Agent: KMail/1.6.2 References: <20051103112655.A264C7302F@freebsd-current.sentex.ca> In-Reply-To: <20051103112655.A264C7302F@freebsd-current.sentex.ca> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200511031545.05339.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV devel-20050919/1162/Thu Nov 3 12:15:03 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: FreeBSD Tinderbox , freebsd-amd64@FreeBSD.org, freebsd-i386@FreeBSD.org Subject: Re: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 20:45:22 -0000 On Thursday 03 November 2005 06:26 am, FreeBSD Tinderbox wrote: > cc -O2 -pipe -DACPI_APPLICATION -DACPI_DEBUG_OUTPUT > -DACPI_DEBUGGER -DACPI_DISASSEMBLER > -I/src/usr.sbin/acpi/acpidb/../../../sys -Wsystem-headers -Werror > -Wall -Wno-format-y2k -Wno-uninitialized -c > /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/dbcmds.c > /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/dbcmds.c: > In function `AcpiDbBusWalk': > /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/dbcmds.c: >1741: warning: dereferencing type-punned pointer will break > strict-aliasing rules *** Error code 1 Fix committed: http://docs.freebsd.org/cgi/mid.cgi?200511032027.jA3KRcgC022617 BTW, '-fno-strict-aliasing' is missing in CFLAGS and that's how I missed it. Why tinderbox uses different CFLAGS is beyond me though. :-( Sorry for the breakage. Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 21:14:54 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B25216A41F; Thu, 3 Nov 2005 21:14:54 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (fw1.wmptl.com [216.8.159.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97E6543D49; Thu, 3 Nov 2005 21:14:53 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from [10.0.0.104] (r3140ca.wmptl.net [10.0.0.104]) by wmptl.net (8.13.1/8.13.1) with ESMTP id jA3LEqDr086573; Thu, 3 Nov 2005 16:14:52 -0500 (EST) (envelope-from nvidican@wmptl.com) Message-ID: <436A7DCC.3000306@wmptl.com> Date: Thu, 03 Nov 2005 16:14:52 -0500 From: Nathan Vidican User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.111 () RATWR10_MESSID X-Scanned-By: MIMEDefang 2.44 Cc: current@freebsd.org Subject: nssswitch - anyone using nss_X ? nss/freebsd complete? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 21:14:54 -0000 Anyone using any sort of nss_X.so module? Are there any open issues with FreeBSD/amd64 and nssswitch? I've been reading a good deal of archived mailing list messages regarding development/threading issues, but to no avail have I found any definitive answer as to if nssswitch works correctly and completely under FreeBSD. Personal interest being drawn from my own issues using, configuring, and updating/compiling nss_ldap. Issues in the code, issues with making new versions, and apparently just issues all-together :( Thinking perhaps someone else out there is using without problem some sort of nss solution? Sparing one problem, current version from FreeBSD/ports/current seems to work correctly, but problem is quite an issue and potential security risk - the likes of which I am still unsure of. I have posted a few times to various mailing lists, and am a member of freebsd-questions, freebsd-current, freebsd-hackers, freebsd-amd64, and nssldap/padl.com - all to no resolution thus far. I'd ideally just like to do the wrench-work and get new(er) version of nss_ldap to compile/function properly under FreeBSD. -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 21:24:23 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFF4D16A41F for ; Thu, 3 Nov 2005 21:24:23 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from linda-4.paradise.net.nz (bm-4a.paradise.net.nz [203.96.152.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 855A343D45 for ; Thu, 3 Nov 2005 21:24:23 +0000 (GMT) (envelope-from markir@paradise.net.nz) Received: from smtp-1.paradise.net.nz (tclsnelb2-src-1.paradise.net.nz [203.96.152.177]) by linda-4.paradise.net.nz (Paradise.net.nz) with ESMTP id <0IPE00DB9E4M59@linda-4.paradise.net.nz> for freebsd-current@freebsd.org; Fri, 04 Nov 2005 10:24:22 +1300 (NZDT) Received: from [192.168.1.11] (218-101-28-65.dsl.clear.net.nz [218.101.28.65]) by smtp-1.paradise.net.nz (Postfix) with ESMTP id 5200C73895E; Fri, 04 Nov 2005 10:24:22 +1300 (NZDT) Date: Fri, 04 Nov 2005 10:24:20 +1300 From: Mark Kirkwood In-reply-to: To: Xin LI Message-id: <436A8004.7000401@paradise.net.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=UTF-8 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050726) References: <4369BAA5.5040107@paradise.net.nz> Cc: freebsd-current@freebsd.org Subject: Re: 6.0-RC1 on Promise SX4060 (SETFEATURES FAILURE, READ timed out) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 21:24:24 -0000 Xin LI wrote: > On 11/3/05, Mark Kirkwood wrote: > >>Hi, I am trying to install 6.0-RC1 on a system with a Promise SX4060 >>(PDC20621) + 4 Maxtor ATA-133 drives (6E040L0). The mobo is a Tyan >>Thunder LE (S2510). > > [snip] > >>These drives seem ok (work with a TX2000 and a 2Ware 7506). >> >>In order to eliminate the drives, I have tried a seagate ST340014A as >>well - same result. >> >>Any suggestions about how to proceed (I would like to get this going) > > > Would you please consider trying "safe mode", if you did not tried? > If possible, please also consider give 5.4-RELEASE a try to see if > this is a regression. > > Cheers, Tried Safe mode with 6.0-RC1 (no boot menu so had to read beastie.4th to figure out how to do that): (loader) set hint.acpi.0.disabled = 1 set loader.acpi_disabled_by_user = 1 set hint.apic.0.disabled = 1 set hw.ata.ata_dma = 0 set hw.ata.atapi_dma = 0 set hw.ata.wc = 0 #set hw.eisa_slots = 0 (forgot to type this one... I'll try again with it in) and get exactly the same errors. Also tried 5.4-RELEASE CD booted in safe mode: acd0: CDRW at ata1-master PIO4 ad4: FAILURE - ATA_IDENTIFY timed out ad4: FAILURE - ATA_IDENTIFY timed out Fatal trap 12: page fault while in kernel mode fault virtual address = 0x8 fault code = supervisor write, page not present instruction pointer = 0x8:0xc05db50d stack pointer = 0x10:0xe6befc94 frame pointer = 0x10:0xe6befc9c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = intrupt enabled, resume, IOPL = 0 current process = 5 (thread taskq) trap number = 12 panic: page fault Cheers Mark From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 21:59:44 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1424416A41F; Thu, 3 Nov 2005 21:59:44 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from indor.net.tomline.ru (indor.net.tomline.ru [213.183.100.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECADB43D46; Thu, 3 Nov 2005 21:59:42 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from SNEZHKO by indorsoft.ru (MDaemon.PRO.v7.2.2.R) with ESMTP id md50000027601.msg; Fri, 04 Nov 2005 03:59:35 +0600 X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 88046, updated: 3.11.2005] To: freebsd-current@freebsd.org References: <20051027022313.R675@kushnir1.kiev.ua> <200511030059.05946.max@love2party.net> <200511031500.00839.jhb@freebsd.org> From: Victor Snezhko Date: Fri, 04 Nov 2005 03:59:32 +0600 In-Reply-To: <200511031500.00839.jhb@freebsd.org> (John Baldwin's message of "Thu, 3 Nov 2005 14:59:59 -0500") Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Processed: indor.net.tomline.ru, Fri, 04 Nov 2005 03:59:35 +0600 (not processed: spam filter disabled) X-Return-Path: snezhko@indorsoft.ru X-VVS-Spam: false Cc: Max Laier Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 21:59:44 -0000 John Baldwin writes: >> (kgdb) up 11 >> #11 0xc066e0c2 in softclock (dummy=0x0) at >> /usr/src/sys/kern/kern_timeout.c:220 220 if (c->c_time != curticks) { >> (kgdb) list >> 215 curticks = softticks; >> 216 bucket = &callwheel[curticks & callwheelmask]; >> 217 c = TAILQ_FIRST(bucket); >> 218 while (c) { >> 219 depth++; >> 220 if (c->c_time != curticks) { >> 221 c = TAILQ_NEXT(c, c_links.tqe); >> 222 ++steps; >> 223 if (steps >= MAX_SOFTCLOCK_STEPS) { >> 224 nextsoftcheck = c; >> (kgdb) print *bucket >> $1 = {tqh_first = 0xc1891d80, tqh_last = 0xc1891d80} >> (kgdb) print c >> $2 = (struct callout *) 0xdeadc0de >> (kgdb) print *(bucket->tqh_first) >> $3 = {c_links = {sle = {sle_next = 0xdeadc0de}, tqe = {tqe_next = >> 0xdeadc0de, tqe_prev = 0xdeadc0de}}, c_time = -559038242, c_arg = >> 0xdeadc0de, c_func = 0xdeadc0de, c_mtx = 0xdeadc0de, c_flags = -559038242} >> (kgdb) print steps >> $4 = 1 > > Well, from thus it seems that a callout was free'd while it was still on the > list. Perhaps there is a case wehre callout_stop() isn't called. Also, > callout_drain() should really be used. If the callout function is rearming, > then it might have been running when callout_stop() is called, and it could > have rearmed itself and then been overwritten when it was freed. In fact, > that is likely your problem. You can try this patch, but there might be lock > order problems that would require the callout_drain() to happen later when > locks aren't held: > > Index: nd6.c > =================================================================== > RCS file: /usr/cvs/src/sys/netinet6/nd6.c,v > retrieving revision 1.62 > diff -u -r1.62 nd6.c > --- nd6.c 22 Oct 2005 05:07:16 -0000 1.62 > +++ nd6.c 3 Nov 2005 19:56:42 -0000 > @@ -398,7 +398,7 @@ > if (tick < 0) { > ln->ln_expire = 0; > ln->ln_ntick = 0; > - callout_stop(&ln->ln_timer_ch); > + callout_drain(&ln->ln_timer_ch); > } else { > ln->ln_expire = time_second + tick / hz; > if (tick > INT_MAX) { Hmmm, no, this patch didn't change anything for me. The same trap, the same bucket full of garbage. Tomorrow I'll try to trace all callout-related operations in nd6 and/or the whole netinet6. If there are more thoughts - I'll be happy to test. -- WBR, Victor V. Snezhko EMail: snezhko@indorsoft.ru From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 22:06:43 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62D3416A41F; Thu, 3 Nov 2005 22:06:43 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail5.speedfactory.net [66.23.216.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96CC843D45; Thu, 3 Nov 2005 22:06:42 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 1327632 for multiple; Thu, 03 Nov 2005 17:04:41 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jA3M6cYh068010; Thu, 3 Nov 2005 17:06:38 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Thu, 3 Nov 2005 15:59:58 -0500 User-Agent: KMail/1.8.2 References: <20051103112655.A264C7302F@freebsd-current.sentex.ca> <200511031545.05339.jkim@FreeBSD.org> In-Reply-To: <200511031545.05339.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511031600.01220.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=100 Cc: freebsd-amd64@freebsd.org, FreeBSD Tinderbox , Jung-uk Kim , freebsd-i386@freebsd.org Subject: Re: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 22:06:43 -0000 On Thursday 03 November 2005 03:45 pm, Jung-uk Kim wrote: > On Thursday 03 November 2005 06:26 am, FreeBSD Tinderbox wrote: > > cc -O2 -pipe -DACPI_APPLICATION -DACPI_DEBUG_OUTPUT > > -DACPI_DEBUGGER -DACPI_DISASSEMBLER > > -I/src/usr.sbin/acpi/acpidb/../../../sys -Wsystem-headers -Werror > > -Wall -Wno-format-y2k -Wno-uninitialized -c > > /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/dbcmds.c > > /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/dbcmds.c: > > In function `AcpiDbBusWalk': > > /src/usr.sbin/acpi/acpidb/../../../sys/contrib/dev/acpica/dbcmds.c: > >1741: warning: dereferencing type-punned pointer will break > > strict-aliasing rules *** Error code 1 > > Fix committed: > > http://docs.freebsd.org/cgi/mid.cgi?200511032027.jA3KRcgC022617 > > BTW, '-fno-strict-aliasing' is missing in CFLAGS and that's how I > missed it. Why tinderbox uses different CFLAGS is beyond me > though. :-( > > Sorry for the breakage. The tinderbox runs with -O2 just for fun I think. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Nov 3 22:22:53 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA1F916A41F for ; Thu, 3 Nov 2005 22:22:53 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A42143D45 for ; Thu, 3 Nov 2005 22:22:53 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by mail.ambrisko.com with ESMTP; 03 Nov 2005 14:22:53 -0800 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.12.11/8.12.9) with ESMTP id jA3MMqQs087798; Thu, 3 Nov 2005 14:22:52 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.12.11/8.12.11/Submit) id jA3MMq4a087797; Thu, 3 Nov 2005 14:22:52 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200511032222.jA3MMq4a087797@ambrisko.com> In-Reply-To: To: "Lynn A. Roth" Date: Thu, 3 Nov 2005 14:22:52 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: freebsd-current@freebsd.org Subject: Re: Problems Installing to PowerEdge 850 with SATA Drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Nov 2005 22:22:53 -0000 Lynn A. Roth writes: | I have two new Dell Poweredge 850 machines. They have an Intel ICH7 | chipset. When I boot FreeBSD 6 RC1, the controller is identified, but | any drives connected to the SATA ports are not detected. The drive that | is included with the system is a Seagate 7200.7 drive. I also tried a | Maxtor. I can confirm the problem on the PE850. I have it working with my latest 4.X SATA patches (which I haven't published yet). I might be able to look into this. FWIW, I my code these SATA registers in 4.X before the become alive: ata2: Intel SATA P0 status 0 error 4050000 scontrol 0 0 1 ata2: Intel SATA P0 status 113 error 4050000 scontrol 0 0 1 ata2: Intel SATA P0 status 113 error 0 scontrol 0 0 1 ata3: Intel SATA P1 status 0 error 4050000 scontrol 0 1 1 ata3: Intel SATA P1 status 113 error 4050000 scontrol 0 1 1 ata3: Intel SATA P1 status 113 error 0 scontrol 0 1 1 On other Intel controllers they I don't have to acknowledge the errors off the bat. Doug A. From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 01:09:01 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 152E016A41F; Fri, 4 Nov 2005 01:09:01 +0000 (GMT) (envelope-from csaba@beastie.creo.hu) Received: from beastie.creo.hu (www.creo.hu [217.113.62.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 185CD43D45; Fri, 4 Nov 2005 01:08:59 +0000 (GMT) (envelope-from csaba@beastie.creo.hu) Received: from beastie.creo.hu (localhost [127.0.0.1]) by beastie.creo.hu (8.13.3/8.13.3) with ESMTP id jA417W9a011110 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Nov 2005 02:07:32 +0100 (CET) (envelope-from csaba@beastie.creo.hu) Received: (from csaba@localhost) by beastie.creo.hu (8.13.3/8.13.3/Submit) id jA417RPl011109; Fri, 4 Nov 2005 02:07:27 +0100 (CET) (envelope-from csaba) Date: Fri, 4 Nov 2005 02:07:27 +0100 From: Csaba Henk To: fuse-devel@lists.sourceforge.net, current@freebsd.org Message-ID: <20051104010727.GV16050@beastie.creo.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i Cc: brennan.stehling@offwhite.net, ivoras@gmail.com, scottl@freebsd.org, Anish Mistry , Simon Barner Subject: "Fuse for FreeBSD" homepage, ports X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 01:09:01 -0000 Hi! Fuse for FreeBSD has got real a homepage now at http://fuse4bsd.creo.hu with source browser, mailing list, documentation in various formats and RSS feed. And in the meantime, the sysutils/fusefs-{kmod,libs,sshfs} ports has been integrated into the ports tree, thus now it's easily accessible for people on FreeBSD 6.x or -CURRENT. -- Csaba Henk My sense of humour is often too subtle to cope with getting smileyd. Please don't take it personal. From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 01:28:14 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A9AD16A41F; Fri, 4 Nov 2005 01:28:14 +0000 (GMT) (envelope-from nocool@263.net) Received: from smtp.263.net (smtp.x263.net [211.150.96.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 007B843D46; Fri, 4 Nov 2005 01:28:11 +0000 (GMT) (envelope-from nocool@263.net) Received: from iscas-zfw728iit (smtp1 [127.0.0.1]) by smtp.263.net (Postfix) with ESMTP id 04472B28; Fri, 4 Nov 2005 09:28:09 +0800 (CST) (envelope-from nocool@263.net) X-Originating-IP: [159.226.5.225] Date: Fri, 4 Nov 2005 09:28:52 +0800 From: "nocool" To: "Robert Watson" X-mailer: Foxmail 5.0 [cn] Mime-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit Message-Id: <20051104012809.04472B28@smtp.263.net> Cc: freebsd-current , freebsd-hacker Subject: Re: Why INVARIANTS option and sanity checking? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 01:28:14 -0000 Thanks for your answer. On Wed, 2 Nov 2005, Watson wrote: >There are a number of debugging kernel options available in the kernel, >... >analysis, is configurable to either generate a warning with debugging >trace, or to panic, depending on desired usage. >... >Basically, it all comes down to this: invariants and sanity checking allow >programmers to test that their assumptions about the source code they (or >someone else) has implemented. This helps find bugs faster, and in a way >that makes them much easier to debug. > >Robert N M Watson >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > In my apprehension, these debugging options aim to help developers detect and locate program's error or exception. In view of efficiency and usability, will be turned off in release. That is to say, these option will not be used to resist intrusion. Part of my work is to review the object reuse protection of FreeBSD 5.4 release. Object reuse come from the Trusted Computer System Evaluation Criteria as "The reassignment to some subject of a storage medium (e.g., page frame, disk sector, magnetic tape) that contained one or more objects. To be securely reassigned, no residual data can be available to the new subject through standard system mechanisms." In review object reuse, should we take kernel area memory management into account? To clean the kernel memory during reassignment using vm_page_alloc and ctor or dtor and set up MEMGUARD to insulate the memory between freeing and reallocating? Thank again. From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 03:37:07 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3B8816A41F for ; Fri, 4 Nov 2005 03:37:07 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from S1.cableone.net (s1.cableone.net [24.116.0.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CA9543D45 for ; Fri, 4 Nov 2005 03:37:07 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: from vixen42.vulpes (unverified [24.119.122.41]) by S1.cableone.net (CableOne SMTP Service S1) with ESMTP id 36227187 for ; Thu, 03 Nov 2005 20:37:28 -0700 Date: Thu, 3 Nov 2005 21:42:01 -0600 From: Vulpes Velox To: Message-ID: <20051103214201.5536951d@vixen42.vulpes> X-Mailer: Sylpheed-Claws 1.9.15 (GTK+ 2.6.10; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-NotAscii: charset=us-ascii X-IP-stats: Incoming Last 3, First 169, in=278, out=0, spam=0 X-External-IP: 24.119.122.41 X-Abuse-Info: Send abuse complaints to abuse@cableone.net Cc: Subject: quake 4 oddity with hardlocking during install on 6.0-rc1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 03:37:07 -0000 Well have run into a odd problem. I got linux-gtk, linux-dri, and the nvidia driver installed and providing linux libs for it. The problem I am running into is as soon as I run the linux install program for it, it hardlocks a little after extracting and loading the program. Any one else successfully get it working on releng_6? From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 07:04:25 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2578E16A41F for ; Fri, 4 Nov 2005 07:04:25 +0000 (GMT) (envelope-from delphij@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABF9943D45 for ; Fri, 4 Nov 2005 07:04:24 +0000 (GMT) (envelope-from delphij@gmail.com) Received: by wproxy.gmail.com with SMTP id 50so139443wri for ; Thu, 03 Nov 2005 23:04:23 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Lu2PtjC6dnv4JJZtZlKzjkwphrqU7qB9QjeVp74Zsgqjn6b6wKZXAKE22x0h+vMK15ZmK6ONgCqnPufrHMN1Oq39vUFMkYRqnzG81lPmcETQQln0wcpUaPPHS/gFf+uTXqABF4oCdrdJXKeqEdPcRKH2ndYw32CtYY77FW1BPeg= Received: by 10.65.215.4 with SMTP id s4mr1748155qbq; Thu, 03 Nov 2005 23:04:23 -0800 (PST) Received: by 10.65.191.18 with HTTP; Thu, 3 Nov 2005 23:04:23 -0800 (PST) Message-ID: Date: Fri, 4 Nov 2005 15:04:23 +0800 From: Xin LI To: Mark Kirkwood In-Reply-To: <436A8004.7000401@paradise.net.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline References: <4369BAA5.5040107@paradise.net.nz> <436A8004.7000401@paradise.net.nz> Cc: freebsd-current@freebsd.org, sos@FreeBSD.org Subject: Re: 6.0-RC1 on Promise SX4060 (SETFEATURES FAILURE, READ timed out) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 07:04:25 -0000 SGksIE1hcmssCgpPbiAxMS80LzA1LCBNYXJrIEtpcmt3b29kIDxtYXJraXJAcGFyYWRpc2UubmV0 Lm56PiB3cm90ZToKW3NuaXBdCj4gVHJpZWQgU2FmZSBtb2RlIHdpdGggNi4wLVJDMSAobm8gYm9v dCBtZW51IHNvIGhhZCB0byByZWFkIGJlYXN0aWUuNHRoIHRvCj4gZmlndXJlIG91dCBob3cgdG8g ZG8gdGhhdCk6Cj4KPiAobG9hZGVyKQo+IHNldCBoaW50LmFjcGkuMC5kaXNhYmxlZCA9IDEKPiBz ZXQgbG9hZGVyLmFjcGlfZGlzYWJsZWRfYnlfdXNlciA9IDEKPiBzZXQgaGludC5hcGljLjAuZGlz YWJsZWQgPSAxCj4gc2V0IGh3LmF0YS5hdGFfZG1hID0gMAo+IHNldCBody5hdGEuYXRhcGlfZG1h ID0gMAo+IHNldCBody5hdGEud2MgPSAwCj4gI3NldCBody5laXNhX3Nsb3RzID0gMCAoZm9yZ290 IHRvIHR5cGUgdGhpcyBvbmUuLi4gSSdsbCB0cnkgYWdhaW4gd2l0aAo+IGl0IGluKQo+Cj4gYW5k IGdldCBleGFjdGx5IHRoZSBzYW1lIGVycm9ycy4KPgo+IEFsc28gdHJpZWQgNS40LVJFTEVBU0Ug Q0QgYm9vdGVkIGluIHNhZmUgbW9kZToKPgo+IGFjZDA6IENEUlcgPENSRUFUSVZFIENELVJXIFJX ODQzOUUvMVIwOT4gYXQgYXRhMS1tYXN0ZXIgUElPNAo+IGFkNDogRkFJTFVSRSAtIEFUQV9JREVO VElGWSB0aW1lZCBvdXQKPiBhZDQ6IEZBSUxVUkUgLSBBVEFfSURFTlRJRlkgdGltZWQgb3V0Cj4K PiBGYXRhbCB0cmFwIDEyOiBwYWdlIGZhdWx0IHdoaWxlIGluIGtlcm5lbCBtb2RlCj4gZmF1bHQg dmlydHVhbCBhZGRyZXNzID0gMHg4Cj4gZmF1bHQgY29kZSAgICAgICAgICAgID0gc3VwZXJ2aXNv ciB3cml0ZSwgcGFnZSBub3QgcHJlc2VudAo+IGluc3RydWN0aW9uIHBvaW50ZXIgICA9IDB4ODow eGMwNWRiNTBkCj4gc3RhY2sgcG9pbnRlciAgICAgICAgID0gMHgxMDoweGU2YmVmYzk0Cj4gZnJh bWUgcG9pbnRlciAgICAgICAgID0gMHgxMDoweGU2YmVmYzljCj4gY29kZSBzZWdtZW50ICAgICAg ICAgID0gYmFzZSAweDAsIGxpbWl0IDB4ZmZmZmYsIHR5cGUgMHgxYgo+ICAgICAgICAgICAgICAg ICAgICAgICA9IERQTCAwLCBwcmVzIDEsIGRlZjMyIDEsIGdyYW4gMQo+IHByb2Nlc3NvciBlZmxh Z3MgICAgICA9IGludHJ1cHQgZW5hYmxlZCwgcmVzdW1lLCBJT1BMID0gMAo+IGN1cnJlbnQgcHJv Y2VzcyAgICAgICA9IDUgKHRocmVhZCB0YXNrcSkKPiB0cmFwIG51bWJlciAgICAgICAgICAgPSAx Mgo+IHBhbmljOiBwYWdlIGZhdWx0CgpPb3BzLCB0aGlzIGlzIGJleW9uZCBteSBrbm93bGVkZ2Uu ICBJZiB5b3UgaGF2ZSBhIHNlcmlhbCBjb25zb2xlIGxpbmUKdG8gY29ubmVjdCB0byB5b3VyIGJv eCwgdGhlbiBkbyBpdCBhbmQgdHJ5IHRvIHJlY29yZCB0aGUgb3V0cHV0IG9mCiJib290IC12IiB3 b3VsZCBiZSBoZWxwZnVsLgoKSSBoYXZlIENjJ2VkIHRoaXMgbWFpbCB0byBTb3JlbiAob3VyIEFU QSBndXJ1KSBhbmQgaGUgbWF5IGhhdmUgc29tZSBzdWdnZXN0aW9ucy4KCkNoZWVycywK From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 08:45:40 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C1B716A421; Fri, 4 Nov 2005 08:45:40 +0000 (GMT) (envelope-from Hartmut.Brandt@dlr.de) Received: from smtp-3.dlr.de (smtp-3.dlr.de [195.37.61.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id C807843D53; Fri, 4 Nov 2005 08:45:39 +0000 (GMT) (envelope-from Hartmut.Brandt@dlr.de) Received: from beagle.kn.op.dlr.de ([129.247.173.6]) by smtp-3.dlr.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.211); Fri, 4 Nov 2005 09:45:37 +0100 Date: Fri, 4 Nov 2005 09:45:36 +0100 (CET) From: Harti Brandt X-X-Sender: brandt_h@beagle.kn.op.dlr.de To: Nathan Vidican In-Reply-To: <436A7DCC.3000306@wmptl.com> Message-ID: <20051104094414.J3669@beagle.kn.op.dlr.de> References: <436A7DCC.3000306@wmptl.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 04 Nov 2005 08:45:37.0234 (UTC) FILETIME=[209BC320:01C5E11C] Cc: questions@freebsd.org, current@freebsd.org Subject: Re: nssswitch - anyone using nss_X ? nss/freebsd complete? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Harti Brandt List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 08:45:40 -0000 On Thu, 3 Nov 2005, Nathan Vidican wrote: NV>Anyone using any sort of nss_X.so module? Are there any open issues with NV>FreeBSD/amd64 and nssswitch? I've been reading a good deal of archived NV>mailing list messages regarding development/threading issues, but to no avail NV>have I found any definitive answer as to if nssswitch works correctly and NV>completely under FreeBSD. I'm using nss_winbind. Seems to work. No idea if there are 64bit issues - I'm currently running it in 32bit only. harti From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 09:19:03 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 581AD16A41F; Fri, 4 Nov 2005 09:19:03 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB91643D45; Fri, 4 Nov 2005 09:19:02 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id D94AD46B8D; Fri, 4 Nov 2005 04:19:01 -0500 (EST) Date: Fri, 4 Nov 2005 09:19:01 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: nocool In-Reply-To: <20051104012809.04472B28@smtp.263.net> Message-ID: <20051104091034.A9692@fledge.watson.org> References: <20051104012809.04472B28@smtp.263.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers , freebsd-current Subject: Re: Why INVARIANTS option and sanity checking? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 09:19:03 -0000 On Fri, 4 Nov 2005, nocool wrote: > In my apprehension, these debugging options aim to help developers > detect and locate program's error or exception. In view of efficiency > and usability, will be turned off in release. That is to say, these > option will not be used to resist intrusion. That is correct. While some users do run with INVARIANTS turned on in production, this is not the recommended configuration for performance reasons. The benefit to running with INVARIANTS on is that, in principle, if you do run into a bug, the system may fail stop faster, rather than perhaps allowing kernel memory corruption to persist. I'm not sure this is likely in a number of cases (often you get a panic immediately afterwards because the invariant is violated), but it does make bugs easier to track down. Because INVARIANTS does perform kernel memory scrubbing, it is quite expensive in terms of CPU. > Part of my work is to review the object reuse protection of FreeBSD 5.4 > release. Object reuse come from the Trusted Computer System Evaluation > Criteria as "The reassignment to some subject of a storage medium (e.g., > page frame, disk sector, magnetic tape) that contained one or more > objects. To be securely reassigned, no residual data can be available to > the new subject through standard system mechanisms." > > In review object reuse, should we take kernel area memory management > into account? To clean the kernel memory during reassignment using > vm_page_alloc and ctor or dtor and set up MEMGUARD to insulate the > memory between freeing and reallocating? The design for FreeBSD calls for all memory and other resources provided to unprivileged processes to be scrubbed before being made available. Only using privilege should a process be able to gain access to unscrubbed resources through allocation. For example: - When a process allocates a new file, it will be created as zero-length. When extended using ftruncate(), any data read or pages mapped from the file will be zero-filled. - When new memory is allocated to the process at time of exec(), using brk(), or using anonymous mmap(), zero'd pages are provided to the process (often optimized using copy-on-write). - When kernel data structures are returned to user space, they are zero'd. This is necessary even when a structure is filled out explicitly, as the padding in the structure introduced by the compiler must also be zero'd. For example, with data structures returned by ioctl(), sysctl(), etc. When using privilege, it is possible to bypass these protections by directly accessing the disk device (allowing reading outside of allocated file space), direct access to allocated and unallocated kernel memory (/dev/mem, /dev/kmem), direct access to swap devices, and so on. If you are aware of bugs in the implementation that result in improper scrubbing of objects on reuse, please let us know by submitting a bug report. While we do optimize reuse scrubbing in a number of situations (copy-on-write from zero'd pages, for example), the semantics should be consistent for the user process. This is especially important with the advent of services like IPSEC, where valuable keying material persists in the kernel for extended periods. Robert N M Watson From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 09:27:28 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 09D7F16A421 for ; Fri, 4 Nov 2005 09:27:28 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id B11EB43D6B for ; Fri, 4 Nov 2005 09:27:25 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 8E5891A3C2F for ; Fri, 4 Nov 2005 01:27:25 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C91E3511F2; Fri, 4 Nov 2005 04:27:24 -0500 (EST) Date: Fri, 4 Nov 2005 04:27:24 -0500 From: Kris Kennaway To: current@FreeBSD.org Message-ID: <20051104092724.GA33945@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 09:27:28 -0000 --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I got this panic shortly after boot on a freshly-updated amd64 machine: FreeBSD/amd64 (fbsd-amd64.isc.org) (ttyd0) login: panic: mb_dtor_pack: ref_cnt != 1 cpuid = 3 KDB: enter: panic [thread pid 1021 tid 100131 ] Stopped at kdb_enter+0x31: leave db> wh Tracing pid 1021 tid 100131 td 0xffffff0323816a40 kdb_enter() at kdb_enter+0x31 panic() at panic+0x1e6 mb_dtor_pack() at mb_dtor_pack+0x103 uma_zfree_arg() at uma_zfree_arg+0x34 mb_free_ext() at mb_free_ext+0xe9 soreceive() at soreceive+0xafb soo_read() at soo_read+0x5e dofileread() at dofileread+0x9e kern_readv() at kern_readv+0x4f read() at read+0x4b syscall() at syscall+0x350 Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (3, FreeBSD ELF64, read), rip = 0x800b7e23c, rsp = 0x7fffffffe1a8, rbp = 0x400 --- Kris --TB36FDmn/VVEgNH/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDayl8Wry0BWjoQKURAsYEAKD4vA8J7ioOCowCPwq0S0ZYXjbMRACeI5Sz HhMqAtR0hS7foT1dQSN/9DQ= =XDVb -----END PGP SIGNATURE----- --TB36FDmn/VVEgNH/-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 10:05:22 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B96616A41F for ; Fri, 4 Nov 2005 10:05:22 +0000 (GMT) (envelope-from pho@holm.cc) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.FreeBSD.org (Postfix) with SMTP id BA61343D45 for ; Fri, 4 Nov 2005 10:05:21 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 184 invoked from network); 4 Nov 2005 10:05:20 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 4 Nov 2005 10:05:20 -0000 X-pair-Authenticated: 80.161.118.233 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id jA4A5Ja8002257; Fri, 4 Nov 2005 11:05:19 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id jA4A5JrX002256; Fri, 4 Nov 2005 11:05:19 +0100 (CET) (envelope-from pho) Date: Fri, 4 Nov 2005 11:05:19 +0100 From: Peter Holm To: Kris Kennaway Message-ID: <20051104100519.GA2203@peter.osted.lan> References: <20051104092724.GA33945@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051104092724.GA33945@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i Cc: current@freebsd.org Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 10:05:22 -0000 On Fri, Nov 04, 2005 at 04:27:24AM -0500, Kris Kennaway wrote: > I got this panic shortly after boot on a freshly-updated amd64 > machine: > Me too: http://people.freebsd.org/~pho/stress/log/cons171.html - Peter > FreeBSD/amd64 (fbsd-amd64.isc.org) (ttyd0) > > login: panic: mb_dtor_pack: ref_cnt != 1 > cpuid = 3 > KDB: enter: panic > [thread pid 1021 tid 100131 ] > Stopped at kdb_enter+0x31: leave > db> wh > Tracing pid 1021 tid 100131 td 0xffffff0323816a40 > kdb_enter() at kdb_enter+0x31 > panic() at panic+0x1e6 > mb_dtor_pack() at mb_dtor_pack+0x103 > uma_zfree_arg() at uma_zfree_arg+0x34 > mb_free_ext() at mb_free_ext+0xe9 > soreceive() at soreceive+0xafb > soo_read() at soo_read+0x5e > dofileread() at dofileread+0x9e > kern_readv() at kern_readv+0x4f > read() at read+0x4b > syscall() at syscall+0x350 > Xfast_syscall() at Xfast_syscall+0xa8 > --- syscall (3, FreeBSD ELF64, read), rip = 0x800b7e23c, rsp = 0x7fffffffe1a8, rbp = 0x400 --- > > Kris > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2 (FreeBSD) > > iD8DBQFDayl8Wry0BWjoQKURAsYEAKD4vA8J7ioOCowCPwq0S0ZYXjbMRACeI5Sz > HhMqAtR0hS7foT1dQSN/9DQ= > =XDVb > -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 10:48:04 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC18216A41F for ; Fri, 4 Nov 2005 10:48:04 +0000 (GMT) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2887B43D45 for ; Fri, 4 Nov 2005 10:48:03 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 71305 invoked from network); 4 Nov 2005 10:50:47 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 4 Nov 2005 10:50:47 -0000 Message-ID: <436B3C93.4000905@freebsd.org> Date: Fri, 04 Nov 2005 11:48:51 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: Kris Kennaway References: <20051104092724.GA33945@xor.obsecurity.org> In-Reply-To: <20051104092724.GA33945@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@FreeBSD.org Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 10:48:05 -0000 Kris Kennaway wrote: > I got this panic shortly after boot on a freshly-updated amd64 > machine: > > FreeBSD/amd64 (fbsd-amd64.isc.org) (ttyd0) > > login: panic: mb_dtor_pack: ref_cnt != 1 > cpuid = 3 > KDB: enter: panic > [thread pid 1021 tid 100131 ] > Stopped at kdb_enter+0x31: leave > db> wh > Tracing pid 1021 tid 100131 td 0xffffff0323816a40 > kdb_enter() at kdb_enter+0x31 > panic() at panic+0x1e6 > mb_dtor_pack() at mb_dtor_pack+0x103 > uma_zfree_arg() at uma_zfree_arg+0x34 > mb_free_ext() at mb_free_ext+0xe9 > soreceive() at soreceive+0xafb > soo_read() at soo_read+0x5e > dofileread() at dofileread+0x9e > kern_readv() at kern_readv+0x4f > read() at read+0x4b > syscall() at syscall+0x350 > Xfast_syscall() at Xfast_syscall+0xa8 > --- syscall (3, FreeBSD ELF64, read), rip = 0x800b7e23c, rsp = 0x7fffffffe1a8, rbp = 0x400 --- There is some modify-after-free going on with that mbuf cluster. The mandatory mbuf cluster refcounting bringing it to the light. Something is smelly in the socket buffer code and we have to out what exactly goes wrong. -- Andre From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 11:02:00 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8887816A41F; Fri, 4 Nov 2005 11:02:00 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from indor.net.tomline.ru (indor.net.tomline.ru [213.183.100.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 289EE43D45; Fri, 4 Nov 2005 11:01:58 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from SNEZHKO by indorsoft.ru (MDaemon.PRO.v7.2.2.R) with ESMTP id md50000027675.msg; Fri, 04 Nov 2005 17:01:52 +0600 X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 88046, updated: 3.11.2005] To: freebsd-current@freebsd.org References: <20051027022313.R675@kushnir1.kiev.ua> <200511030059.05946.max@love2party.net> <200511031500.00839.jhb@freebsd.org> From: Victor Snezhko Date: Fri, 04 Nov 2005 17:01:46 +0600 In-Reply-To: (Victor Snezhko's message of "Fri, 04 Nov 2005 03:59:32 +0600") Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Processed: indor.net.tomline.ru, Fri, 04 Nov 2005 17:01:52 +0600 (not processed: spam filter disabled) X-Return-Path: snezhko@indorsoft.ru X-VVS-Spam: false Cc: Max Laier Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 11:02:00 -0000 Victor Snezhko writes: >>> (kgdb) up 11 >>> #11 0xc066e0c2 in softclock (dummy=0x0) at >>> /usr/src/sys/kern/kern_timeout.c:220 220 if (c->c_time != curticks) { >>> (kgdb) list >>> 215 curticks = softticks; >>> 216 bucket = &callwheel[curticks & callwheelmask]; >>> 217 c = TAILQ_FIRST(bucket); >>> 218 while (c) { >>> 219 depth++; >>> 220 if (c->c_time != curticks) { >>> 221 c = TAILQ_NEXT(c, c_links.tqe); >>> 222 ++steps; >>> 223 if (steps >= MAX_SOFTCLOCK_STEPS) { >>> 224 nextsoftcheck = c; >>> (kgdb) print *bucket >>> $1 = {tqh_first = 0xc1891d80, tqh_last = 0xc1891d80} >>> (kgdb) print c >>> $2 = (struct callout *) 0xdeadc0de >>> (kgdb) print *(bucket->tqh_first) >>> $3 = {c_links = {sle = {sle_next = 0xdeadc0de}, tqe = {tqe_next = >>> 0xdeadc0de, tqe_prev = 0xdeadc0de}}, c_time = -559038242, c_arg = >>> 0xdeadc0de, c_func = 0xdeadc0de, c_mtx = 0xdeadc0de, c_flags = -559038242} >>> (kgdb) print steps >>> $4 = 1 >> >> Well, from thus it seems that a callout was free'd while it was still on the >> list. Perhaps there is a case wehre callout_stop() isn't called. Also, >> callout_drain() should really be used. If the callout function is rearming, >> then it might have been running when callout_stop() is called, and it could >> have rearmed itself and then been overwritten when it was freed. In fact, >> that is likely your problem. You can try this patch, but there might be lock >> order problems that would require the callout_drain() to happen later when >> locks aren't held: >> >> Index: nd6.c >> =================================================================== >> RCS file: /usr/cvs/src/sys/netinet6/nd6.c,v >> retrieving revision 1.62 >> diff -u -r1.62 nd6.c >> --- nd6.c 22 Oct 2005 05:07:16 -0000 1.62 >> +++ nd6.c 3 Nov 2005 19:56:42 -0000 >> @@ -398,7 +398,7 @@ >> if (tick < 0) { >> ln->ln_expire = 0; >> ln->ln_ntick = 0; >> - callout_stop(&ln->ln_timer_ch); >> + callout_drain(&ln->ln_timer_ch); >> } else { >> ln->ln_expire = time_second + tick / hz; >> if (tick > INT_MAX) { > > Hmmm, no, this patch didn't change anything for me. The same trap, the > same bucket full of garbage. > > Tomorrow I'll try to trace all callout-related operations in nd6 > and/or the whole netinet6. Hmmm... trace shows that the callout_stop/callout_drain call always receives a pointer that has not been initialized via callout_init, at least not in /usr/src/sys/netinet6/* I'll debug this further and report the results. -- WBR, Victor V. Snezhko EMail: snezhko@indorsoft.ru From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 11:05:06 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1818816A426; Fri, 4 Nov 2005 11:05:06 +0000 (GMT) (envelope-from uwe@laverenz.de) Received: from natfrord.rzone.de (natfrord.rzone.de [81.169.145.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id A346643D46; Fri, 4 Nov 2005 11:04:59 +0000 (GMT) (envelope-from uwe@laverenz.de) Received: from athena.laverenz.de (p5480EFDD.dip.t-dialin.net [84.128.239.221]) by post.webmailer.de (8.13.1/8.13.1) with ESMTP id jA4B4tBR028177; Fri, 4 Nov 2005 12:04:57 +0100 (MET) Received: from localhost (localhost.localdomain [127.0.0.1]) by athena.laverenz.de (Postfix) with ESMTP id 9C3B9E38C779; Fri, 4 Nov 2005 12:04:54 +0100 (CET) Received: from athena.laverenz.de ([127.0.0.1]) by localhost (athena [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 17218-04; Fri, 4 Nov 2005 12:04:53 +0100 (CET) Received: by athena.laverenz.de (Postfix, from userid 2000) id BDDD8E38C778; Fri, 4 Nov 2005 12:04:53 +0100 (CET) Date: Fri, 4 Nov 2005 12:04:53 +0100 From: Uwe Laverenz To: questions@freebsd.org, current@freebsd.org Message-ID: <20051104110453.GC17199@laverenz.de> Mail-Followup-To: questions@freebsd.org, current@freebsd.org References: <436A7DCC.3000306@wmptl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <436A7DCC.3000306@wmptl.com> Organization: private site Sender: uwe@laverenz.de User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at laverenz.de Cc: Subject: Re: nssswitch - anyone using nss_X ? nss/freebsd complete? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 11:05:06 -0000 On Thu, Nov 03, 2005 at 04:14:52PM -0500, Nathan Vidican wrote: > avail have I found any definitive answer as to if nssswitch works correctly > and completely under FreeBSD. I use nss_ldap (and pam_ldap), it is supported since 5.1_RELEASE. At this time only passwd and group can be used via nsswitch. It works without problems. > Personal interest being drawn from my own issues using, configuring, and > updating/compiling nss_ldap. Issues in the code, issues with making new I never tried to compile them on my own, I always use nss_ldap and pam_ldap from the ports. > Sparing one problem, current version from FreeBSD/ports/current seems to > work correctly, but problem is quite an issue and potential security risk - Do you have an URL about this security risk? Uwe From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 11:13:22 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56B5C16A41F for ; Fri, 4 Nov 2005 11:13:22 +0000 (GMT) (envelope-from rosti.bsd@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 845B743D53 for ; Fri, 4 Nov 2005 11:13:21 +0000 (GMT) (envelope-from rosti.bsd@gmail.com) Received: by nproxy.gmail.com with SMTP id b2so92406nfe for ; Fri, 04 Nov 2005 03:13:20 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:x-mailer:mime-version:content-type:content-transfer-encoding; b=XZUu468lg6AYfMnMha7RTuRZy9J5VIbUYMd872S9SsXi17jhY7SWO4L/2GW+lRFhkWBAfsFl69dJ1pMJDz2vHrZaVvYZgMZITCzuWPzQOGW37WqbGzKt0Wll1hK26Fd65a1MJzKigfJHemmqKOlExuR8p66jQ16sUHW7Ydk1Xy0= Received: by 10.48.240.8 with SMTP id n8mr841875nfh; Fri, 04 Nov 2005 03:13:20 -0800 (PST) Received: from saturn.lan ( [212.143.154.227]) by mx.gmail.com with ESMTP id q28sm1408075nfc.2005.11.04.03.13.16; Fri, 04 Nov 2005 03:13:20 -0800 (PST) Date: Fri, 4 Nov 2005 13:16:53 +0200 From: Rostislav Krasny To: Jochen Gensch Message-Id: <20051104131653.4cce215b.rosti.bsd@gmail.com> X-Mailer: Sylpheed version 2.0.3 (GTK+ 2.6.10; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Anton Karpov Subject: Re: where is the BEASTIE??? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 11:13:22 -0000 > > I've just cvsuped and rebuilt my system from 6.0-RC1 to 6.0-STABLE, > > and I've noticed "FreeBSD" ASCII logo in bootloader menu instead of > > good old red Beastie... How can I take the Beastie back? ;) > Where do you see any menu? I don't see anything of that kind here!? If you already have a /boot/loader.rc file it wouldn't be updated during the system rebuilding. This is because all platforms' loader Makefiles have lines like following: .if !exists(${DESTDIR}/boot/loader.rc) FILES+= loader.rc .endif There are two versions of default loader.rc file: for i386 and pc98 it is src/sys/boot/i386/loader/loader.rc and for the rest it is src/sys/boot/forth/loader.rc Only the first version loads the boot menu. You can copy that file to the /boot directory manually. And to get the old Beastie on the boot menu you should set a loader_logo variable to 'beastiebw' or to 'beastie' before 'beastie-start' command there: \ Load in the boot menu include /boot/beastie.4th \ Set the loader logo set loader_logo=beastiebw \ Start the boot menu beastie-start From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 11:51:10 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9863216A420 for ; Fri, 4 Nov 2005 11:51:10 +0000 (GMT) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id D572343D5E for ; Fri, 4 Nov 2005 11:51:08 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 71742 invoked from network); 4 Nov 2005 11:53:51 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 4 Nov 2005 11:53:51 -0000 Message-ID: <436B4B5B.3010106@freebsd.org> Date: Fri, 04 Nov 2005 12:51:55 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: Andre Oppermann References: <20051104092724.GA33945@xor.obsecurity.org> <436B3C93.4000905@freebsd.org> In-Reply-To: <436B3C93.4000905@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@FreeBSD.org, Kris Kennaway Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 11:51:10 -0000 Andre Oppermann wrote: > Kris Kennaway wrote: > >> I got this panic shortly after boot on a freshly-updated amd64 >> machine: >> >> FreeBSD/amd64 (fbsd-amd64.isc.org) (ttyd0) >> >> login: panic: mb_dtor_pack: ref_cnt != 1 >> cpuid = 3 >> KDB: enter: panic >> [thread pid 1021 tid 100131 ] >> Stopped at kdb_enter+0x31: leave >> db> wh >> Tracing pid 1021 tid 100131 td 0xffffff0323816a40 >> kdb_enter() at kdb_enter+0x31 >> panic() at panic+0x1e6 >> mb_dtor_pack() at mb_dtor_pack+0x103 >> uma_zfree_arg() at uma_zfree_arg+0x34 >> mb_free_ext() at mb_free_ext+0xe9 >> soreceive() at soreceive+0xafb >> soo_read() at soo_read+0x5e >> dofileread() at dofileread+0x9e >> kern_readv() at kern_readv+0x4f >> read() at read+0x4b >> syscall() at syscall+0x350 >> Xfast_syscall() at Xfast_syscall+0xa8 >> --- syscall (3, FreeBSD ELF64, read), rip = 0x800b7e23c, rsp = >> 0x7fffffffe1a8, rbp = 0x400 --- > > There is some modify-after-free going on with that mbuf cluster. > The mandatory mbuf cluster refcounting bringing it to the light. > > Something is smelly in the socket buffer code and we have to out > what exactly goes wrong. Actually it's a logic bug in the mb_free_ext() code. Damn. Patch in an hour. -- Andre From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 00:07:21 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C49516A41F; Fri, 4 Nov 2005 00:07:21 +0000 (GMT) (envelope-from mauritz.sundell@telia.com) Received: from pne-smtpout1-sn2.hy.skanova.net (pne-smtpout1-sn2.hy.skanova.net [81.228.8.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0219843D46; Fri, 4 Nov 2005 00:07:20 +0000 (GMT) (envelope-from mauritz.sundell@telia.com) Received: from pne-ps2-sn1 (81.228.11.132) by pne-smtpout1-sn2.hy.skanova.net (7.2.060.1) id 436A3A5300016CC3; Fri, 4 Nov 2005 01:07:18 +0100 Message-ID: <14401715.1131062838696.JavaMail.tomcat@pne-ps2-sn1> Date: Fri, 4 Nov 2005 01:07:18 +0100 (MET) From: Mauritz Sundell To: bzeeb-lists@lists.zabbadoz.net Mime-Version: 1.0 Content-Type: text/plain;charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: CP Presentation Server X-clientstamp: [217.211.26.85] X-Mailman-Approved-At: Fri, 04 Nov 2005 13:08:16 +0000 Cc: freebsd-current@freebsd.org, freebsd-amd64@freebsd.org Subject: Re: Re: CURRENT Safemode does not boot but ACPI-mode does [SOLVED] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mauritz Sundell List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 00:07:21 -0000 On Thu, 3 Nov 2005, Bjoern A. Zeeb wrote: >On Thu, 3 Nov 2005, Mauritz Sundell wrote: > >> 27 october I cvsuped and build kernel and world >> since then I cant boot without ACPI >> when I boot without there looks to be problems with resource- >> allocations >> drivers cannot attach, cannot map interrupt, and finally Mount root >> fail >> due to no harddisk found. >> >> My previous kernel was from the 26th october. >> >> Im running CURRENT on an HP Pavilion zv5000 (laptop) with amd64. >> >> Do someone have any tips where I should look? > >There had been more changes in that timeframe. > >Try re-adding > device atpic >to your kernel config file if it's missing. Thanks Bjoern adding atpic solved the problem Mauritz Sundell From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 11:17:30 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C48016A41F for ; Fri, 4 Nov 2005 11:17:30 +0000 (GMT) (envelope-from mauritz.sundell@freebsd.viem.se) Received: from av9-2-sn3.vrr.skanova.net (av9-2-sn3.vrr.skanova.net [81.228.9.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CBAD43D45 for ; Fri, 4 Nov 2005 11:17:29 +0000 (GMT) (envelope-from mauritz.sundell@freebsd.viem.se) Received: by av9-2-sn3.vrr.skanova.net (Postfix, from userid 502) id 2C1DA37F5E; Fri, 4 Nov 2005 12:17:28 +0100 (CET) Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net [81.228.9.101]) by av9-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 0ECCD37F3F for ; Fri, 4 Nov 2005 12:17:28 +0100 (CET) Received: from viem.se (h85n1fls35o847.telia.com [217.211.26.85]) by smtp3-1-sn3.vrr.skanova.net (Postfix) with SMTP id 96B7437E42 for ; Fri, 4 Nov 2005 12:16:59 +0100 (CET) To: freebsd-current@freebsd.org From: mauritz.sundell@freebsd.viem.se Message-Id: <20051104111659.96B7437E42@smtp3-1-sn3.vrr.skanova.net> Date: Fri, 4 Nov 2005 12:16:59 +0100 (CET) X-Mailman-Approved-At: Fri, 04 Nov 2005 13:08:16 +0000 Subject: Cannot boot pccard with ACPI enabled on amd64 laptop X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 11:17:30 -0000 Hi, I have a wlan-pccard (device pccard0+wi0) that works good in current without acpi, but with acpi enabled the machine freeze with the card inserted. I have an HP Pavilion zv5000 (laptop) with amd64. If I enable acpi and use the builtin wired lan-adapter (device rl0) everything works good. I really want ACPI to work, do anyone have any ideas? I have a diffuse memory of that I was able to boot with both ACPI and the same pccard at the beginning of the year, but I am not sure. dmesg and other files is available at: http://viem.se/freebsd/hp-pavilion-zv5000/2005.11.03.23.57.20/ -- Mauritz Sundell From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 13:49:07 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F081316A41F for ; Fri, 4 Nov 2005 13:49:07 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18A3243D48 for ; Fri, 4 Nov 2005 13:49:06 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by kane.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id jA4Dn4wN020941; Fri, 4 Nov 2005 15:49:05 +0200 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id jA4DmuGT002405; Fri, 4 Nov 2005 15:48:56 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id jA4DmusC002404; Fri, 4 Nov 2005 15:48:56 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Fri, 4 Nov 2005 15:48:56 +0200 From: Giorgos Keramidas To: mauritz.sundell@freebsd.viem.se Message-ID: <20051104134856.GA2362@flame.pc> References: <20051104111659.96B7437E42@smtp3-1-sn3.vrr.skanova.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051104111659.96B7437E42@smtp3-1-sn3.vrr.skanova.net> X-Mailman-Approved-At: Fri, 04 Nov 2005 13:56:45 +0000 Cc: freebsd-current@freebsd.org Subject: Re: Cannot boot pccard with ACPI enabled on amd64 laptop X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 13:49:08 -0000 On 2005-11-04 12:16, mauritz.sundell@freebsd.viem.se wrote: > I have a wlan-pccard (device pccard0+wi0) that works good in > current without acpi, but with acpi enabled the machine freeze > with the card inserted. > > I have an HP Pavilion zv5000 (laptop) with amd64. > > If I enable acpi and use the builtin wired lan-adapter (device > rl0) everything works good. > > I really want ACPI to work, do anyone have any ideas? Roll back to the sources before the latest ACPI import, as there have been problems with the latest CURRENT and ACPI. A known good timestamp to use for updating is: cvs -qR up -APd -D '2005/11/01 22:00:00 UTC' See if the kernel from that date works fine for you. If it does, watch this list carefully as the ACPI issues are tracked down and solved. - Giorgos From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 14:09:20 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 723D916A41F for ; Fri, 4 Nov 2005 14:09:20 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1141543D45 for ; Fri, 4 Nov 2005 14:09:19 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp3-g19.free.fr (Postfix) with ESMTP id CEF3F3754F for ; Fri, 4 Nov 2005 15:09:18 +0100 (CET) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.13.3/8.13.3) with ESMTP id jA4E9EYL000126 for ; Fri, 4 Nov 2005 15:09:17 +0100 (CET) From: Thierry Herbelot To: freebsd-current@freebsd.org Date: Fri, 4 Nov 2005 15:09:05 +0100 User-Agent: KMail/1.8.2 X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511041509.07205.thierry@herbelot.com> Subject: /boot/kernel/kernel.debug on 6.0-RELEASE-i386-bootonly.iso ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 14:09:20 -0000 Hello, It seems that the new ISOs are here ;-) I was initrigued by the large size of 6.0-RELEASE-i386-bootonly.iso (43MB) relative to 5.4-RELEASE-i386-bootonly.iso (21MB) The increase seems to come from a kernel.debug : is it intended ? thanks for the good bits TfH From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 14:31:41 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50B9716A41F for ; Fri, 4 Nov 2005 14:31:41 +0000 (GMT) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56A2243D58 for ; Fri, 4 Nov 2005 14:31:39 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 74873 invoked from network); 4 Nov 2005 14:34:20 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 4 Nov 2005 14:34:20 -0000 Message-ID: <436B70FA.3080401@freebsd.org> Date: Fri, 04 Nov 2005 15:32:26 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: Kris Kennaway References: <20051104092724.GA33945@xor.obsecurity.org> In-Reply-To: <20051104092724.GA33945@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: glebius@freebsd.org, current@FreeBSD.org Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 14:31:41 -0000 Kris Kennaway wrote: > I got this panic shortly after boot on a freshly-updated amd64 > machine: > > FreeBSD/amd64 (fbsd-amd64.isc.org) (ttyd0) > > login: panic: mb_dtor_pack: ref_cnt != 1 > cpuid = 3 > KDB: enter: panic > [thread pid 1021 tid 100131 ] > Stopped at kdb_enter+0x31: leave > db> wh > Tracing pid 1021 tid 100131 td 0xffffff0323816a40 > kdb_enter() at kdb_enter+0x31 > panic() at panic+0x1e6 > mb_dtor_pack() at mb_dtor_pack+0x103 > uma_zfree_arg() at uma_zfree_arg+0x34 > mb_free_ext() at mb_free_ext+0xe9 > soreceive() at soreceive+0xafb > soo_read() at soo_read+0x5e > dofileread() at dofileread+0x9e > kern_readv() at kern_readv+0x4f > read() at read+0x4b > syscall() at syscall+0x350 > Xfast_syscall() at Xfast_syscall+0xa8 > --- syscall (3, FreeBSD ELF64, read), rip = 0x800b7e23c, rsp = 0x7fffffffe1a8, rbp = 0x400 --- This should fix it. Commit in half an hour. -- Andre Index: kern/uipc_mbuf.c =================================================================== RCS file: /home/ncvs/src/sys/kern/uipc_mbuf.c,v retrieving revision 1.156 diff -u -p -r1.156 uipc_mbuf.c --- kern/uipc_mbuf.c 2 Nov 2005 16:20:35 -0000 1.156 +++ kern/uipc_mbuf.c 4 Nov 2005 14:28:31 -0000 @@ -215,9 +215,11 @@ mb_free_ext(struct mbuf *m) /* Free attached storage if this mbuf is the only reference to it. */ if (*(m->m_ext.ref_cnt) == 1 || - atomic_fetchadd_int(m->m_ext.ref_cnt, -1) == 1) { + atomic_fetchadd_int(m->m_ext.ref_cnt, -1) == 0) { switch (m->m_ext.ext_type) { - case EXT_CLUSTER: + case EXT_CLUSTER: /* The packet zone is special. */ + if (*(m->m_ext.ref_cnt) == 0) + *(m->m_ext.ref_cnt) = 1; uma_zfree(zone_pack, m); return; /* Job done. */ break; Index: kern/kern_mbuf.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_mbuf.c,v retrieving revision 1.12 diff -u -p -r1.12 kern_mbuf.c --- kern/kern_mbuf.c 2 Nov 2005 16:20:35 -0000 1.12 +++ kern/kern_mbuf.c 4 Nov 2005 14:28:31 -0000 @@ -395,11 +395,10 @@ mb_ctor_clust(void *mem, int size, void static void mb_dtor_clust(void *mem, int size, void *arg) { - u_int *refcnt; - refcnt = uma_find_refcnt(zone_clust, mem); - KASSERT(*refcnt == 1, ("%s: refcnt incorrect %u", __func__, *refcnt)); - *refcnt = 0; + KASSERT(*(uma_find_refcnt(zone_clust, mem)) == 0 && + *(uma_find_refcnt(zone_clust, mem)) == 1, + ("%s: refcnt incorrect %u", __func__, *refcnt)); #ifdef INVARIANTS trash_dtor(mem, size, arg); #endif From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 15:14:24 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A7A516A41F for ; Fri, 4 Nov 2005 15:14:24 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 038C243D45 for ; Fri, 4 Nov 2005 15:14:23 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1EY3DK-0003LK-B2 for freebsd-current@freebsd.org; Fri, 04 Nov 2005 16:10:46 +0100 Received: from 72.11.2.113 ([72.11.2.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 04 Nov 2005 16:10:46 +0100 Received: from lynnr.junk by 72.11.2.113 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 04 Nov 2005 16:10:46 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: "Lynn A. Roth" Date: Fri, 04 Nov 2005 10:06:31 -0500 Lines: 29 Message-ID: <436B78F7.3010300@interactivefs.com> References: <200511032222.jA3MMq4a087797@ambrisko.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 72.11.2.113 User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en In-Reply-To: <200511032222.jA3MMq4a087797@ambrisko.com> Sender: news Subject: Re: Problems Installing to PowerEdge 850 with SATA Drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 15:14:24 -0000 Doug Ambrisko wrote: > Lynn A. Roth writes: > | I have two new Dell Poweredge 850 machines. They have an Intel ICH7 > | chipset. When I boot FreeBSD 6 RC1, the controller is identified, but > | any drives connected to the SATA ports are not detected. The drive that > | is included with the system is a Seagate 7200.7 drive. I also tried a > | Maxtor. > > I can confirm the problem on the PE850. I have it working with my > latest 4.X SATA patches (which I haven't published yet). I might > be able to look into this. > > FWIW, I my code these SATA registers in 4.X before the become alive: > ata2: Intel SATA P0 status 0 error 4050000 scontrol 0 0 1 > ata2: Intel SATA P0 status 113 error 4050000 scontrol 0 0 1 > ata2: Intel SATA P0 status 113 error 0 scontrol 0 0 1 > ata3: Intel SATA P1 status 0 error 4050000 scontrol 0 1 1 > ata3: Intel SATA P1 status 113 error 4050000 scontrol 0 1 1 > ata3: Intel SATA P1 status 113 error 0 scontrol 0 1 1 > On other Intel controllers they I don't have to acknowledge the > errors off the bat. > > Doug A. If there is anything I can do to help, let me know. If there is a place you can point me to start working with it, that would be great too. Thanks, Lynn From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 15:41:02 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 268C416A421; Fri, 4 Nov 2005 15:41:02 +0000 (GMT) (envelope-from scottl@FreeBSD.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80CA243D45; Fri, 4 Nov 2005 15:41:01 +0000 (GMT) (envelope-from scottl@FreeBSD.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jA4FexKL050601; Fri, 4 Nov 2005 08:40:59 -0700 (MST) (envelope-from scottl@FreeBSD.org) Message-ID: <436B810A.7040908@FreeBSD.org> Date: Fri, 04 Nov 2005 08:40:58 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD Current , freebsd-stable@FreeBSD.org X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Content-Type: text/plain; name="6.0-announce.txt.asc" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="6.0-announce.txt.asc" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: FreeBSD 6.0 Released X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 15:41:02 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It is my great pleasure and privilege to announce the availability of FreeBSD 6.0-RELEASE. This release is the next step in delivering the high performance and enterprise features that have been under development in the FreeBSD 5.x series for that last several years. Some of the many changes since 5.4 include: ~ Significant performance improvements to the filesystem and direct disk access layers of the OS. The filesystem is now multithreaded and can take full advantage of multiple CPU systems. ~ Expanded support for wireless networking adapters and new support for the WPA wireless security protocol. ~ Experimental support for the PowerPC platform. For a complete list of new features and known problems, please see the release notes and errata list, available at: http://www.FreeBSD.org/releases/6.0R/relnotes.html http://www.FreeBSD.org/releases/6.0R/errata.html For more information about FreeBSD release engineering activities, please see: http://www.FreeBSD.org/releng Availability ------------- FreeBSD 6.0-RELEASE supports the i386, pc98, alpha, sparc64, amd64, powerpc, and ia64 architectures and can be installed directly over the net using bootable media or copied to a local NFS/FTP server. Distributions for all 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 6.0 based products: ~ FreeBSD Mall, Inc. http://www.freebsdmall.com/ ~ Daemonnews, Inc. http://www.bsdmall.com/freebsd1.html If you can't 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't promise that all the mirror sites will carry the larger ISO images, but they will at least be available from the following sites. MD5 and SHA256 checksums for the release images are included at the bottom of this message. Bittorrent ---------- The FreeBSD project encourages the use of BitTorrent for distributing the release ISO images. A collection of torrent files to download the images is available at ftp://ftp.freebsd.org/pub/FreeBSD/torrents/6.0-RELEASE FTP --- At the time of this announcement the following FTP sites have FreeBSD 6.0-RELEASE available. 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://ftp.at.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.ch.FreeBSD.org/pub/FreeBSD/ ftp://ftp.cz.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://ftp5.pl.FreeBSD.org/pub/FreeBSD/ ftp://ftp3.ru.FreeBSD.org/pub/FreeBSD/ ftp://ftp.se.FreeBSD.org/pub/FreeBSD/ ftp://ftp.si.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.tw.FreeBSD.org/pub/FreeBSD/ ftp://ftp.uk.FreeBSD.org/pub/FreeBSD/ ftp://ftp2.us.FreeBSD.org/pub/FreeBSD/ ftp://ftp5.us.FreeBSD.org/pub/FreeBSD/ FreeBSD is also available via anonymous FTP from mirror sites in the following countries: Argentina, Australia, Brazil, Bulgaria, Canada, China, Czech Republic, Denmark, Estonia, Finland, France, Germany, Hong Kong, Hungary, Iceland, Ireland, Japan, Korea, Lithuania, Amylonia, the Netherlands, New Zealand, Poland, Portugal, Romania, Russia, Saudi Arabia, South Africa, Slovak Republic, Slovenia, Spain, Sweden, Taiwan, Thailand, Ukraine, and the United Kingdom. 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 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 ---------------- Many companies donated equipment, network access, or man-hours to finance the release engineering activities for FreeBSD 6.0 including The FreeBSD Foundation, FreeBSD Systems, Hewlett-Packard, Yahoo!, Sentex Communications, and SPARTA. The release engineering team for 6.0-RELEASE includes: Scott Long Release Engineering, I386 and AMD64 Release Building Ken Smith Sparc64 Release Building, Mirror Site Coordination Robert Watson Release Engineering, Security Doug White Release Engineering Murray Stokely Release Engineering Marcel Moolenaar IA64 Release Building Takahashi Yoshihiro PC98 Release Building Wilko Bulte Alpha Release Building Peter Grehan PowerPC Release Building Kris Kennaway Package Building Joe Marcus Clark Package Building Kiril Ponomarew Package Building Colin Percival Security Officer CD Image Checksums ------------------ For Alpha: MD5 (6.0-RELEASE-alpha-bootonly.iso) = 98499535a511e85ae5afe4542b6fd7f3 MD5 (6.0-RELEASE-alpha-disc1.iso) = c8f316202b221035086a08709bc011a6 SHA256 (6.0-RELEASE-alpha-bootonly.iso) = 2fcc391dc123baaeaba34f4f925a22223f209d63260d9283d6ba77227bb23dbd SHA256 (6.0-RELEASE-alpha-disc1.iso) = c71d06359a0dc0c6efb3aa9b40c80df62e359716454aaaf672556638b81b498a For amd64: MD5 (6.0-RELEASE-amd64-bootonly.iso) = 4328c66c900ef6e6ddc1daf9dd8b731f MD5 (6.0-RELEASE-amd64-disc1.iso) = a4e427adaa2bfef868e2bc62d57fbf8d MD5 (6.0-RELEASE-amd64-disc2.iso) = 2f46d344681c1a82b146b3ed1df68e61 SHA256 (6.0-RELEASE-amd64-bootonly.iso) = afa6eb02845185d1968cce02e752614394f8b9c09fc519ae1b61356c583d6df0 SHA256 (6.0-RELEASE-amd64-disc1.iso) = 449b08c98acc73508219e2a19de0787334fd9237123346b2c7949c3009540170 SHA256 (6.0-RELEASE-amd64-disc2.iso) = 25c3e3da1f2e0a0ecb8a23dd78f35f969cc17eba6072db6a41edab3ecfc2e2d4 For i386: MD5 (6.0-RELEASE-i386-bootonly.iso) = d71afd22be9ea7fe28e026575cbbb878 MD5 (6.0-RELEASE-i386-disc1.iso) = cfe3c1a2b4991edd6a294ca9b422b9d5 MD5 (6.0-RELEASE-i386-disc2.iso) = 1003806d98cd60ba4b672f4ca546ced3 SHA256 (6.0-RELEASE-i386-bootonly.iso) = 97ee1c1ffc2774c1c2cdc63ed8820fd3aedf7f0b5bb6273b87e40a05e00b2d1f SHA256 (6.0-RELEASE-i386-disc1.iso) = 0ad601dae704e941beb7d4617bf96b04055849a24835275c716f518eee7a12f1 SHA256 (6.0-RELEASE-i386-disc2.iso) = 1a82de4ff6733ee782da8df80cf66cf47266eefdb9f76cd19bf08063539c1aa0 For ia64: MD5 (6.0-RELEASE-ia64-bootonly.iso) = 3246ae501dac0067d4085e216fcf376a MD5 (6.0-RELEASE-ia64-disc1.iso) = e2fbb0e3b19a26e0b2e72bb8c13a57e9 MD5 (6.0-RELEASE-ia64-disc2.iso) = 2f5bbe94ec1438ecaa0b08915500d605 MD5 (6.0-RELEASE-ia64-livefs.iso) = cb227ea0e1db6873dbcb56249bf45418 SHA256 (6.0-RELEASE-ia64-bootonly.iso) = 9e6d502f32b5dc2cfc3d2af69d1512eb0476e6320851b3ecb5918977780c3cda SHA256 (6.0-RELEASE-ia64-disc1.iso) = fd9aaee8417a1701ebc72db6cd86d15f23738e743149f8a8cb9f6547ab5f336d SHA256 (6.0-RELEASE-ia64-disc2.iso) = 65618e4547ef7f5238a4987622d34e3f05200b4d6d9c0affbca8931b317197d1 SHA256 (6.0-RELEASE-ia64-livefs.iso) = 3e2e689318f05e9946ad24f443019256e73459bb2000be6b9aaf96c7ec1eaae8 For pc98: MD5 (6.0-RELEASE-pc98-disc1.iso) = 5ec7737af58ed3a2618523721dc17cec For powerpc: MD5 (6.0-RELEASE-powerpc-bootonly.iso) = 09219f4db3d3b94528413901757d2e49 MD5 (6.0-RELEASE-powerpc-disc1.iso) = 2ad675f7e4010c51f173e6c636b18b76 SHA256 (6.0-RELEASE-powerpc-bootonly.iso) = 530db1240a5fc4ae4e91b589630ad74c04eab9113b752c0d101f8dc9d14236ba SHA256 (6.0-RELEASE-powerpc-disc1.iso) = a7242065cca689d95c0c3611b1d8fdc38bb1c8b5207bc985289c46bcf75e7e00 For sparc64: MD5 (6.0-RELEASE-sparc64-bootonly.iso) = cf6423fe3c344827fc4a0fb179e0e375 MD5 (6.0-RELEASE-sparc64-disc1.iso) = 5ef7031b720f18bad2e216fb373c8da7 MD5 (6.0-RELEASE-sparc64-disc2.iso) = 31045ae89c097003fe06f77d0ee97227 SHA256 (6.0-RELEASE-sparc64-bootonly.iso) = 17f1849d89bc98107bddc2b86c5b18f33dbc33351e388ea7003efadda6c575b4 SHA256 (6.0-RELEASE-sparc64-disc1.iso) = a212e35e8d016908ec9bc431c66c393ca7e43823aeb7b3333266420ef1b7380c SHA256 (6.0-RELEASE-sparc64-disc2.iso) = 66ed27a2cb202b4249e00bad73609bfc4ffea4fcae8f941a30eb4b90bc0e43a9 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDa35dHTr20QF8Xr8RAt7CAJ4riJYL86TdkABalT/tYtCE8KkHlgCdHaMt 1b/M8EpWPpGZf7wH7KC07Zs= =7uAG -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 16:11:28 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60BF416A41F for ; Fri, 4 Nov 2005 16:11:28 +0000 (GMT) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15C7B43D69 for ; Fri, 4 Nov 2005 16:11:23 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 75523 invoked from network); 4 Nov 2005 16:14:04 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 4 Nov 2005 16:14:04 -0000 Message-ID: <436B885B.6010609@freebsd.org> Date: Fri, 04 Nov 2005 17:12:11 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: current@FreeBSD.org References: <20051104092724.GA33945@xor.obsecurity.org> <436B70FA.3080401@freebsd.org> In-Reply-To: <436B70FA.3080401@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: glebius@freebsd.org, Kris Kennaway Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 16:11:28 -0000 Andre Oppermann wrote: > Kris Kennaway wrote: > >> I got this panic shortly after boot on a freshly-updated amd64 >> machine: >> >> FreeBSD/amd64 (fbsd-amd64.isc.org) (ttyd0) >> >> login: panic: mb_dtor_pack: ref_cnt != 1 >> cpuid = 3 >> KDB: enter: panic >> [thread pid 1021 tid 100131 ] >> Stopped at kdb_enter+0x31: leave >> db> wh >> Tracing pid 1021 tid 100131 td 0xffffff0323816a40 >> kdb_enter() at kdb_enter+0x31 >> panic() at panic+0x1e6 >> mb_dtor_pack() at mb_dtor_pack+0x103 >> uma_zfree_arg() at uma_zfree_arg+0x34 >> mb_free_ext() at mb_free_ext+0xe9 >> soreceive() at soreceive+0xafb >> soo_read() at soo_read+0x5e >> dofileread() at dofileread+0x9e >> kern_readv() at kern_readv+0x4f >> read() at read+0x4b >> syscall() at syscall+0x350 >> Xfast_syscall() at Xfast_syscall+0xa8 >> --- syscall (3, FreeBSD ELF64, read), rip = 0x800b7e23c, rsp = >> 0x7fffffffe1a8, rbp = 0x400 --- > > > This should fix it. Commit in half an hour. Ok, thanks to Danny Braniss and Peter Holm the KASSERT is working now. -- Andre Index: kern/uipc_mbuf.c =================================================================== RCS file: /home/ncvs/src/sys/kern/uipc_mbuf.c,v retrieving revision 1.156 diff -u -p -r1.156 uipc_mbuf.c --- kern/uipc_mbuf.c 2 Nov 2005 16:20:35 -0000 1.156 +++ kern/uipc_mbuf.c 4 Nov 2005 16:09:07 -0000 @@ -215,9 +215,11 @@ mb_free_ext(struct mbuf *m) /* Free attached storage if this mbuf is the only reference to it. */ if (*(m->m_ext.ref_cnt) == 1 || - atomic_fetchadd_int(m->m_ext.ref_cnt, -1) == 1) { + atomic_fetchadd_int(m->m_ext.ref_cnt, -1) == 0) { switch (m->m_ext.ext_type) { - case EXT_CLUSTER: + case EXT_CLUSTER: /* The packet zone is special. */ + if (*(m->m_ext.ref_cnt) == 0) + *(m->m_ext.ref_cnt) = 1; uma_zfree(zone_pack, m); return; /* Job done. */ break; Index: kern/kern_mbuf.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_mbuf.c,v retrieving revision 1.12 diff -u -p -r1.12 kern_mbuf.c --- kern/kern_mbuf.c 2 Nov 2005 16:20:35 -0000 1.12 +++ kern/kern_mbuf.c 4 Nov 2005 16:09:07 -0000 @@ -395,11 +395,10 @@ mb_ctor_clust(void *mem, int size, void static void mb_dtor_clust(void *mem, int size, void *arg) { - u_int *refcnt; - refcnt = uma_find_refcnt(zone_clust, mem); - KASSERT(*refcnt == 1, ("%s: refcnt incorrect %u", __func__, *refcnt)); - *refcnt = 0; + KASSERT(*(uma_find_refcnt(zone_clust, mem)) <= 1, + ("%s: refcnt incorrect %u", __func__, + *(uma_find_refcnt(zone_clust, mem))) ); #ifdef INVARIANTS trash_dtor(mem, size, arg); #endif From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 16:36:04 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 829F716A41F; Fri, 4 Nov 2005 16:36:04 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9F0B43D45; Fri, 4 Nov 2005 16:35:59 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by rosebud.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id jA4GZvV2002637; Fri, 4 Nov 2005 18:35:58 +0200 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id jA4GZnaE088041; Fri, 4 Nov 2005 18:35:49 +0200 (EET) (envelope-from keramida@linux.gr) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id jA4GZQMS086109; Fri, 4 Nov 2005 18:35:26 +0200 (EET) (envelope-from keramida@linux.gr) Date: Fri, 4 Nov 2005 18:35:26 +0200 From: Giorgos Keramidas To: Andre Oppermann Message-ID: <20051104163526.GC82727@flame.pc> References: <20051104092724.GA33945@xor.obsecurity.org> <436B70FA.3080401@freebsd.org> <436B885B.6010609@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <436B885B.6010609@freebsd.org> Cc: glebius@freebsd.org, current@freebsd.org, Kris Kennaway Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 16:36:04 -0000 On 2005-11-04 17:12, Andre Oppermann wrote: > Ok, thanks to Danny Braniss and Peter Holm the KASSERT is working now. Very fast fix. Thanks. I barely had the time to build a kernel and read Peter's warning about a broken build, before the fix was ready :) > Index: kern/uipc_mbuf.c > =================================================================== > RCS file: /home/ncvs/src/sys/kern/uipc_mbuf.c,v > retrieving revision 1.156 > diff -u -p -r1.156 uipc_mbuf.c > --- kern/uipc_mbuf.c 2 Nov 2005 16:20:35 -0000 1.156 > +++ kern/uipc_mbuf.c 4 Nov 2005 16:09:07 -0000 > @@ -215,9 +215,11 @@ mb_free_ext(struct mbuf *m) > > /* Free attached storage if this mbuf is the only reference to it. > */ > if (*(m->m_ext.ref_cnt) == 1 || > - atomic_fetchadd_int(m->m_ext.ref_cnt, -1) == 1) { > + atomic_fetchadd_int(m->m_ext.ref_cnt, -1) == 0) { > switch (m->m_ext.ext_type) { > - case EXT_CLUSTER: > + case EXT_CLUSTER: /* The packet zone is special. */ > + if (*(m->m_ext.ref_cnt) == 0) > + *(m->m_ext.ref_cnt) = 1; > uma_zfree(zone_pack, m); > return; /* Job done. */ > break; > Index: kern/kern_mbuf.c > =================================================================== > RCS file: /home/ncvs/src/sys/kern/kern_mbuf.c,v > retrieving revision 1.12 > diff -u -p -r1.12 kern_mbuf.c > --- kern/kern_mbuf.c 2 Nov 2005 16:20:35 -0000 1.12 > +++ kern/kern_mbuf.c 4 Nov 2005 16:09:07 -0000 > @@ -395,11 +395,10 @@ mb_ctor_clust(void *mem, int size, void > static void > mb_dtor_clust(void *mem, int size, void *arg) > { > - u_int *refcnt; > > - refcnt = uma_find_refcnt(zone_clust, mem); > - KASSERT(*refcnt == 1, ("%s: refcnt incorrect %u", __func__, > *refcnt)); > - *refcnt = 0; > + KASSERT(*(uma_find_refcnt(zone_clust, mem)) <= 1, > + ("%s: refcnt incorrect %u", __func__, > + *(uma_find_refcnt(zone_clust, mem))) ); > #ifdef INVARIANTS > trash_dtor(mem, size, arg); > #endif > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 16:50:36 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEF2216A41F; Fri, 4 Nov 2005 16:50:36 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (fw1.wmptl.com [216.8.159.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2830543D58; Fri, 4 Nov 2005 16:50:35 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from [10.0.0.104] (r3140ca.wmptl.net [10.0.0.104]) by wmptl.net (8.13.1/8.13.1) with ESMTP id jA4GoYQB004449; Fri, 4 Nov 2005 11:50:34 -0500 (EST) (envelope-from nvidican@wmptl.com) Message-ID: <436B915A.2070805@wmptl.com> Date: Fri, 04 Nov 2005 11:50:34 -0500 From: Nathan Vidican User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.111 () RATWR10_MESSID X-Scanned-By: MIMEDefang 2.44 Cc: current@freebsd.org Subject: new filesystem improvements in 6.0-RELEASE, require newfs? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 16:50:36 -0000 Most notably amongst the improvements/additions to 6.0-RELEASE, are those in the filesystem area. In performing a system upgrade, does one need to newfs/format a given partition with a new file system to make use of these optimizations, or is the bonus simply in the kernel/filesystem support and sticking with the current UFS2 partition (5.3-RELEASE/amd64) will step-up to it? -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 16:53:34 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5B2216A420 for ; Fri, 4 Nov 2005 16:53:34 +0000 (GMT) (envelope-from vincent@xtra-net.org) Received: from relay.xtra-net.org (cable-195-162-200-89.customer.tvd.be [195.162.200.89]) by mx1.FreeBSD.org (Postfix) with SMTP id 924FC43D5A for ; Fri, 4 Nov 2005 16:53:24 +0000 (GMT) (envelope-from vincent@xtra-net.org) Received: (qmail 31778 invoked from network); 4 Nov 2005 16:53:21 -0000 Received: from wbedllfs.xtra-net.org (192.168.1.21) by 0 with SMTP; 4 Nov 2005 16:53:21 -0000 From: Vincent Blondel To: current@freebsd.org Content-Type: text/plain Date: Fri, 04 Nov 2005 17:51:51 +0100 Message-Id: <1131123111.2379.14.camel@wbedllfs.xtra-net.org> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Subject: Cant load plugin libjavaplugin_oji.so X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vincent@xtra-net.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 16:53:34 -0000 Dears, I get a cisco PIX firewall and to access the built-in web interface (PDM - PIX Cisco Device Manager), it is highly recommended to use Netscape Navigator 4.78 and Linux JVM 1.4.1_02. So I downloaded these two softwares on my current (7.0) FreeBSD system and installed them in /opt as : /opt/netscape-4.78 /opt/jre1.4.1_02 I configured my system by setting : COMPAT="/usr/compat/linux" JAVA_HOME="/opt/j2re1.4.1_02" export COMPAT JAVA_HOME PATH=$JAVA_HOME/bin:$COMPAT/sbin:$COMPAT/bin:$COMPAT/usr/sbin:$ COMPAT/usr/bin:$COMPAT/usr/X11R6/bin:$PATH LD_LIBRARY_PATH=$COMPAT/lib:$COMPAT/usr/lib:$COMPAT/usr/X11R6/lib DISPLAY=:0.0 export PATH LD_LIBRARY_PATH DISPLAY I also created a symbolic link in my home dir to the right JVM with : /root/.netscape/plugins/libjavaplugin_oji.so -> /opt/j2re1.4.1_02/plugin/i386/ns600/libjavaplugin_oji.so Netscape runs correctly but it can't load the JVM plugin. You get below the resulted output from the 'truss' command. Can somebody help me ? Regards --------------- linux_open("/root/.netscape/plugins",0x18800,00) = 14 (0xe) linux_fstat64(0xe,0xbfbf77b0,0x289d9160) = 0 (0x0) linux_fcntl64(0xe,0x2,0x1) = 0 (0x0) linux_getdents64(0xe,0x8b86030,0x1000) = 88 (0x58) linux_stat64(0xbfbf7858,0xbfbf7708,0xbfbf7858) = 0 (0x0) linux_stat64(0xbfbf7858,0xbfbf76f0,0xbfbf7858) = 0 (0x0) linux_open("/root/.netscape/plugins/libjavaplugin_oji.so",0x0,011773) = 15 (0xf) read(0xf,0xbfbf7240,0x200) = 512 (0x200) linux_fstat64(0xf,0xbfbf715c,0x286a2bfc) = 0 (0x0) linux_mmap(0xbfbf708c) = 681594880 (0x28a05000) linux_mmap(0xbfbf708c) = 681775104 (0x28a31000) close(15) = 0 (0x0) mprotect(0x28a05000,180224,(0x3)PROT_READ|PROT_WRITE) = 0 (0x0) SIGNAL 14 (SIGALRM) SIGNAL 14 (SIGALRM) gettimeofday({1131122073 697734},0x0) = 0 (0x0) linux_sigreturn(0xbfbf70a0) = 0 (0x0) munmap(0x28a05000,0x3446c) = 0 (0x0) ERROR: /root/.netscape/plugins/libjavaplugin_oji.so: undefined symbol: GetGlobalServiceManager__16nsServiceManagerPP17nsIServiceManager Cant load plugin /root/.netscape/plugins/libjavaplugin_oji.so. Ignored. write(2,0xbfbf50fc,208) = 208 (0xd0) linux_getdents64(0xe,0x8b86030,0x1000) = 0 (0x0) close(14) = 0 (0x0) From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 16:57:04 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D66716A41F; Fri, 4 Nov 2005 16:57:04 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from aiolos.otenet.gr (aiolos.otenet.gr [195.170.0.93]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B4B543D6B; Fri, 4 Nov 2005 16:57:03 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by aiolos.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id jA4GusRn009334; Fri, 4 Nov 2005 18:57:01 +0200 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id jA4GukqE022902; Fri, 4 Nov 2005 18:56:46 +0200 (EET) (envelope-from keramida@linux.gr) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id jA4GukDh022895; Fri, 4 Nov 2005 18:56:46 +0200 (EET) (envelope-from keramida@linux.gr) Date: Fri, 4 Nov 2005 18:56:46 +0200 From: Giorgos Keramidas To: Nathan Vidican Message-ID: <20051104165646.GB15136@flame.pc> References: <436B915A.2070805@wmptl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <436B915A.2070805@wmptl.com> Cc: questions@freebsd.org, current@freebsd.org Subject: Re: new filesystem improvements in 6.0-RELEASE, require newfs? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 16:57:04 -0000 On 2005-11-04 11:50, Nathan Vidican wrote: > Most notably amongst the improvements/additions to 6.0-RELEASE, > are those in the filesystem area. In performing a system > upgrade, does one need to newfs/format a given partition with a > new file system to make use of these optimizations, or is the > bonus simply in the kernel/filesystem support and sticking with > the current UFS2 partition (5.3-RELEASE/amd64) will step-up to it? The VFS optimizations and improvements in the SMP & locking don't really depend on having a particular file system type, AFAIK, so you shouldn't need to newfs for the performance gains they implement. From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 17:03:31 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D25816A41F; Fri, 4 Nov 2005 17:03:31 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5F5A43D53; Fri, 4 Nov 2005 17:03:26 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id jA4HCQPG085650; Fri, 4 Nov 2005 12:12:26 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-acpi@FreeBSD.org, freebsd-current@FreeBSD.org Date: Fri, 4 Nov 2005 12:03:12 -0500 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200511041203.13837.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV devel-20050919/1162/Thu Nov 3 12:15:03 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Subject: [PATCH] Please test ACPI-CA 20051021 fix X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 17:03:31 -0000 If you have booting problems *after* ACPI-CA 20051021 import, please try this patch and let me know: http://people.freebsd.org/~jkim/acpica/rscalc.c.diff Thanks, Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 17:07:37 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B4FE16A41F for ; Fri, 4 Nov 2005 17:07:37 +0000 (GMT) (envelope-from incmc@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id BFABC43D5C for ; Fri, 4 Nov 2005 17:07:35 +0000 (GMT) (envelope-from incmc@gmx.de) Received: (qmail invoked by alias); 04 Nov 2005 17:07:33 -0000 Received: from dslb-084-061-012-075.pools.arcor-ip.net (EHLO ms.homeip.net) [84.61.12.75] by mail.gmx.net (mp029) with SMTP; 04 Nov 2005 18:07:33 +0100 X-Authenticated: #15946415 Received: from id4cc1a79.versanet.de ([212.204.26.121] helo=nix-rechnername-auspaehen-hier) by ms.homeip.net with esmtpsa (SSLv3:RC4-MD5:128) id 1EY52O-000692-NQ for freebsd-current@freebsd.org; Fri, 04 Nov 2005 18:07:36 +0100 From: Jochen Gensch To: freebsd-current@freebsd.org Date: Fri, 4 Nov 2005 18:07:07 +0100 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200511041807.07477.incmc@gmx.de> X-Y-GMX-Trusted: 0 Subject: Problems with Atheros 108Mbit cards X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 17:07:37 -0000 Hi, I recently bought a Netgear WG511T. However the connection always breaks do= wn=20 after a few seconds. It worked fine with an Atheros 54 Mbit chip before and= I=20 haven't changed the config.=20 I can see a valid turbo mode via ifconfig -m ath0. But if I run wpa_supplic= ant=20 manually I shows the following output: wpa_supplicant -i ath0 -d -c /etc/wpa_supplicant.conf Initializing interface 'ath0' conf '/etc/wpa_supplicant.conf' driver 'defau= lt' Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf' Reading configuration file '/etc/wpa_supplicant.conf' ctrl_interface=3D'/var/run/wpa_supplicant' ctrl_interface_group=3D0 (from group name 'wheel') Priority group 0 =A0 =A0id=3D0 ssid=3D'DA-BUTZE-COE' Initializing interface (2) 'ath0' Own MAC address: 00:0f:b5:26:a9:e5 wpa_driver_bsd_set_wpa: enabled=3D1 wpa_driver_bsd_set_wpa_internal: wpa=3D3 privacy=3D1 wpa_driver_bsd_del_key: keyidx=3D0 wpa_driver_bsd_del_key: keyidx=3D1 wpa_driver_bsd_del_key: keyidx=3D2 wpa_driver_bsd_del_key: keyidx=3D3 wpa_driver_bsd_set_countermeasures: enabled=3D0 wpa_driver_bsd_set_drop_unencrypted: enabled=3D1 Setting scan request: 0 sec 100000 usec Using existing control interface directory. Starting AP scan (broadcast SSID) Received 0 bytes of scan results (1 BSSes) Scan results: 1 Selecting BSS from priority group 0 0: 00:0f:b5:e7:17:90 ssid=3D'DA-BUTZE-COE' wpa_ie_len=3D24 rsn_ie_len=3D0 =A0 =A0selected Trying to associate with 00:0f:b5:e7:17:90 (SSID=3D'DA-BUTZE-COE' freq=3D24= 37 MHz) Cancelling scan request Automatic auth_alg selection: 0x1 WPA: using IEEE 802.11i/D3.0 WPA: Selected cipher suites: group 8 pairwise 8 key_mgmt 2 WPA: using GTK TKIP WPA: using PTK TKIP WPA: using KEY_MGMT WPA-PSK WPA: Own WPA IE - hexdump(len=3D24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01= 00=20 00 50 f2 02 01 00 00 50 f2 02 No keys have been configured - skip key clearing wpa_driver_bsd_set_drop_unencrypted: enabled=3D1 wpa_driver_bsd_associate: ssid 'DA-BUTZE-COE' wpa ie len 24 pairwise 2 grou= p 2=20 key mgmt 1 wpa_driver_bsd_associate: set PRIVACY 1 Setting authentication timeout: 5 sec 0 usec Association event - clear replay counter Associated to a new BSS: BSSID=3D00:0f:b5:e7:17:90 No keys have been configured - skip key clearing Associated with 00:0f:b5:e7:17:90 Setting authentication timeout: 10 sec 0 usec RX EAPOL from 00:0f:b5:e7:17:90 Setting authentication timeout: 10 sec 0 usec IEEE 802.1X RX: version=3D1 type=3D3 length=3D95 =A0 EAPOL-Key type=3D254 WPA: RX message 1 of 4-Way Handshake from 00:0f:b5:e7:17:90 (ver=3D1) WPA: Renewed SNonce - hexdump(len=3D32): 56 11 5b 20 7a fe 58 40 bd de 36 9= 4 b3=20 10 4b 02 74 eb 76 22 6e e4 c8 c6 1f fc 58 76 6a 11 12 de WPA: PMK - hexdump(len=3D32): [REMOVED] WPA: PTK - hexdump(len=3D64): [REMOVED] WPA: EAPOL-Key MIC - hexdump(len=3D16): 21 59 6d c1 21 5a 8d 7a 84 c7 bc 3e= e0=20 23 ee f8 WPA: Sending EAPOL-Key 2/4 RX EAPOL from 00:0f:b5:e7:17:90 IEEE 802.1X RX: version=3D1 type=3D3 length=3D95 =A0 EAPOL-Key type=3D254 WPA: RX message 1 of 4-Way Handshake from 00:0f:b5:e7:17:90 (ver=3D1) WPA: PMK - hexdump(len=3D32): [REMOVED] WPA: PTK - hexdump(len=3D64): [REMOVED] WPA: EAPOL-Key MIC - hexdump(len=3D16): 0c b4 7f 79 85 a6 c5 dd 6a 6b a7 7d= 47=20 83 77 81 WPA: Sending EAPOL-Key 2/4 RX EAPOL from 00:0f:b5:e7:17:90 IEEE 802.1X RX: version=3D1 type=3D3 length=3D95 =A0 EAPOL-Key type=3D254 WPA: RX message 1 of 4-Way Handshake from 00:0f:b5:e7:17:90 (ver=3D1) WPA: PMK - hexdump(len=3D32): [REMOVED] WPA: PTK - hexdump(len=3D64): [REMOVED] WPA: EAPOL-Key MIC - hexdump(len=3D16): c7 77 0c 48 71 d8 b2 7e 1e 7f 64 fb= eb=20 3c 26 51 WPA: Sending EAPOL-Key 2/4 RX EAPOL from 00:0f:b5:e7:17:90 IEEE 802.1X RX: version=3D1 type=3D3 length=3D95 =A0 EAPOL-Key type=3D254 WPA: RX message 1 of 4-Way Handshake from 00:0f:b5:e7:17:90 (ver=3D1) WPA: PMK - hexdump(len=3D32): [REMOVED] WPA: PTK - hexdump(len=3D64): [REMOVED] WPA: EAPOL-Key MIC - hexdump(len=3D16): cc 40 2b 73 50 b3 21 e5 85 f3 1c 48= 45=20 e9 3a 35 WPA: Sending EAPOL-Key 2/4 Setting scan request: 0 sec 100000 usec Added BSSID 00:0f:b5:e7:17:90 into blacklist Disconnect event - remove keys wpa_driver_bsd_del_key: keyidx=3D0 wpa_driver_bsd_del_key: keyidx=3D1 wpa_driver_bsd_del_key: keyidx=3D2 wpa_driver_bsd_del_key: keyidx=3D3 wpa_driver_bsd_del_key: addr=3D00:00:00:00:00:00 keyidx=3D0 ioctl[SIOCS80211, op 20, len 7]: Can't assign requested address And after that last message the connection breaks down again... thanks for = any=20 help. Jochen From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 17:23:46 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFF5A16A441 for ; Fri, 4 Nov 2005 17:23:46 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5624543D45 for ; Fri, 4 Nov 2005 17:23:46 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: by xproxy.gmail.com with SMTP id t14so916902wxc for ; Fri, 04 Nov 2005 09:23:45 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GMpwfAvZ64OzbYHdBJCAdwxDpkUv133z5+coEx6jq1wKEjseAr1/XQ9iu/owFIobK/ZjkncDI3uHG8rYpQl/OIX1j1myAHXWDGbIr/B54EgJNifzqD3TTZTwcW0VS3KlevKWv5Yj8zBmRxehNtFOEB1x5GkyAOBU3eGsS9sjzLk= Received: by 10.70.24.6 with SMTP id 6mr2189168wxx; Fri, 04 Nov 2005 08:56:24 -0800 (PST) Received: by 10.70.9.10 with HTTP; Fri, 4 Nov 2005 08:56:24 -0800 (PST) Message-ID: <70e8236f0511040856gc2b6c07vf65277d2bd5f4e75@mail.gmail.com> Date: Fri, 4 Nov 2005 16:56:24 +0000 From: Joao Barros To: Nathan Vidican In-Reply-To: <436B915A.2070805@wmptl.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <436B915A.2070805@wmptl.com> Cc: questions@freebsd.org, current@freebsd.org Subject: Re: new filesystem improvements in 6.0-RELEASE, require newfs? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 17:23:46 -0000 On 11/4/05, Nathan Vidican wrote: > Most notably amongst the improvements/additions to 6.0-RELEASE, are those= in the > filesystem area. In performing a system upgrade, does one need to newfs/f= ormat a > given partition with a new file system to make use of these optimizations= , or is > the bonus simply in the kernel/filesystem support and sticking with the > current UFS2 partition (5.3-RELEASE/amd64) will step-up to it? As you nicely put it: the bonus is simply in the kernel :) -- Joao Barros From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 17:25:29 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71B2D16A420 for ; Fri, 4 Nov 2005 17:25:29 +0000 (GMT) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id E61E943D62 for ; Fri, 4 Nov 2005 17:25:26 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 76067 invoked from network); 4 Nov 2005 17:28:07 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 4 Nov 2005 17:28:07 -0000 Message-ID: <436B99B6.2090009@freebsd.org> Date: Fri, 04 Nov 2005 18:26:14 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: Giorgos Keramidas References: <20051104092724.GA33945@xor.obsecurity.org> <436B70FA.3080401@freebsd.org> <436B885B.6010609@freebsd.org> <20051104163526.GC82727@flame.pc> In-Reply-To: <20051104163526.GC82727@flame.pc> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: glebius@freebsd.org, current@freebsd.org, Kris Kennaway Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 17:25:29 -0000 Giorgos Keramidas wrote: > On 2005-11-04 17:12, Andre Oppermann wrote: >>Ok, thanks to Danny Braniss and Peter Holm the KASSERT is working now. > > Very fast fix. Thanks. I barely had the time to build a kernel and > read Peter's warning about a broken build, before the fix was ready :) Fix committed a minute ago. -- Andre From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 17:33:43 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6002B16A41F; Fri, 4 Nov 2005 17:33:43 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 752CB43D53; Fri, 4 Nov 2005 17:33:42 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp3-g19.free.fr (Postfix) with ESMTP id B1BD33752F; Fri, 4 Nov 2005 18:33:41 +0100 (CET) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.13.3/8.13.3) with ESMTP id jA4HXbQ7007369; Fri, 4 Nov 2005 18:33:40 +0100 (CET) From: Thierry Herbelot To: freebsd-current@freebsd.org Date: Fri, 4 Nov 2005 18:33:29 +0100 User-Agent: KMail/1.8.2 References: <20051104092724.GA33945@xor.obsecurity.org> <436B885B.6010609@freebsd.org> <20051104163526.GC82727@flame.pc> In-Reply-To: <20051104163526.GC82727@flame.pc> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200511041833.30955.thierry@herbelot.com> Cc: Andre Oppermann Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 17:33:43 -0000 Le Friday 4 November 2005 17:35, Giorgos Keramidas a écrit : > On 2005-11-04 17:12, Andre Oppermann wrote: > > Ok, thanks to Danny Braniss and Peter Holm the KASSERT is working now. > > Very fast fix. Thanks. I barely had the time to build a kernel and > read Peter's warning about a broken build, before the fix was ready :) > Hello, I have applied your second patch, to solve an mbuf exhaustion which I see with NFS traffic. I still have the same symptoms : after launching over an ssh session a recusrive 'ls' over an NFS disk, the -current NFS client is blocked (and complains with 'nfs server truc:/files: not responding') - I first saw this when cvs-ing the sources from the same shared disk. I have enclosed the trace showing the mbuf stats : multi-cur% while (1) while? sleep 10 while? netstat -m | head -2 while? end 65/460/525 mbufs in use (current/cache/total) 64/210/274/3776 mbuf clusters in use (current/cache/total/max) 66/2124/2190 mbufs in use (current/cache/total) 64/2016/2080/3776 mbuf clusters in use (current/cache/total/max) 68/3652/3720 mbufs in use (current/cache/total) 65/3439/3504/3776 mbuf clusters in use (current/cache/total/max) 67/3908/3975 mbufs in use (current/cache/total) 64/3712/3776/3776 mbuf clusters in use (current/cache/total/max) 67/3908/3975 mbufs in use (current/cache/total) 64/3712/3776/3776 mbuf clusters in use (current/cache/total/max) This isssue is seen on 3 different PCs running recent -current, clients for a FreeBSD-6 NFS server (same problem when the NFS server is NetBSD). All 3 clients have a small RAM, which may be a cause for faster apparition of the issue. TfH From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 17:45:02 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCDE316A41F for ; Fri, 4 Nov 2005 17:45:02 +0000 (GMT) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C1E343D45 for ; Fri, 4 Nov 2005 17:45:01 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 76208 invoked from network); 4 Nov 2005 17:47:42 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 4 Nov 2005 17:47:42 -0000 Message-ID: <436B9E4C.1030506@freebsd.org> Date: Fri, 04 Nov 2005 18:45:48 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: thierry@herbelot.com References: <20051104092724.GA33945@xor.obsecurity.org> <436B885B.6010609@freebsd.org> <20051104163526.GC82727@flame.pc> <200511041833.30955.thierry@herbelot.com> In-Reply-To: <200511041833.30955.thierry@herbelot.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 17:45:03 -0000 Thierry Herbelot wrote: > Le Friday 4 November 2005 17:35, Giorgos Keramidas a écrit : > >>On 2005-11-04 17:12, Andre Oppermann wrote: >> >>>Ok, thanks to Danny Braniss and Peter Holm the KASSERT is working now. >> >>Very fast fix. Thanks. I barely had the time to build a kernel and >>read Peter's warning about a broken build, before the fix was ready :) >> > > Hello, > > I have applied your second patch, to solve an mbuf exhaustion which I see with > NFS traffic. > I still have the same symptoms : > after launching over an ssh session a recusrive 'ls' over an NFS disk, the > -current NFS client is blocked (and complains with 'nfs server truc:/files: > not responding') - I first saw this when cvs-ing the sources from the same > shared disk. > > I have enclosed the trace showing the mbuf stats : > > multi-cur% while (1) > while? sleep 10 > while? netstat -m | head -2 > while? end > 65/460/525 mbufs in use (current/cache/total) > 64/210/274/3776 mbuf clusters in use (current/cache/total/max) > 66/2124/2190 mbufs in use (current/cache/total) > 64/2016/2080/3776 mbuf clusters in use (current/cache/total/max) > 68/3652/3720 mbufs in use (current/cache/total) > 65/3439/3504/3776 mbuf clusters in use (current/cache/total/max) > 67/3908/3975 mbufs in use (current/cache/total) > 64/3712/3776/3776 mbuf clusters in use (current/cache/total/max) > 67/3908/3975 mbufs in use (current/cache/total) > 64/3712/3776/3776 mbuf clusters in use (current/cache/total/max) > > This isssue is seen on 3 different PCs running recent -current, clients for a > FreeBSD-6 NFS server (same problem when the NFS server is NetBSD). All 3 > clients have a small RAM, which may be a cause for faster apparition of the > issue. Hmmm... There are way too many in the packet cache (zone). Normally they should get free'd back into the mbuf and cluster zones if there are too many. I have to track down why UMA isn't doing that. -- Andre From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 18:29:27 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D486116A44A for ; Fri, 4 Nov 2005 18:29:27 +0000 (GMT) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A80DA43D45 for ; Fri, 4 Nov 2005 18:29:25 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 76587 invoked from network); 4 Nov 2005 18:32:05 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 4 Nov 2005 18:32:05 -0000 Message-ID: <436BA8B5.9070104@freebsd.org> Date: Fri, 04 Nov 2005 19:30:13 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: thierry@herbelot.com References: <20051104092724.GA33945@xor.obsecurity.org> <436B885B.6010609@freebsd.org> <20051104163526.GC82727@flame.pc> <200511041833.30955.thierry@herbelot.com> In-Reply-To: <200511041833.30955.thierry@herbelot.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 18:29:28 -0000 Thierry Herbelot wrote: > Le Friday 4 November 2005 17:35, Giorgos Keramidas a écrit : > >>On 2005-11-04 17:12, Andre Oppermann wrote: >> >>>Ok, thanks to Danny Braniss and Peter Holm the KASSERT is working now. >> >>Very fast fix. Thanks. I barely had the time to build a kernel and >>read Peter's warning about a broken build, before the fix was ready :) >> > > Hello, > > I have applied your second patch, to solve an mbuf exhaustion which I see with > NFS traffic. > I still have the same symptoms : > after launching over an ssh session a recusrive 'ls' over an NFS disk, the > -current NFS client is blocked (and complains with 'nfs server truc:/files: > not responding') - I first saw this when cvs-ing the sources from the same > shared disk. > > I have enclosed the trace showing the mbuf stats : > > multi-cur% while (1) > while? sleep 10 > while? netstat -m | head -2 > while? end > 65/460/525 mbufs in use (current/cache/total) > 64/210/274/3776 mbuf clusters in use (current/cache/total/max) > 66/2124/2190 mbufs in use (current/cache/total) > 64/2016/2080/3776 mbuf clusters in use (current/cache/total/max) > 68/3652/3720 mbufs in use (current/cache/total) > 65/3439/3504/3776 mbuf clusters in use (current/cache/total/max) > 67/3908/3975 mbufs in use (current/cache/total) > 64/3712/3776/3776 mbuf clusters in use (current/cache/total/max) > 67/3908/3975 mbufs in use (current/cache/total) > 64/3712/3776/3776 mbuf clusters in use (current/cache/total/max) > > This isssue is seen on 3 different PCs running recent -current, clients for a > FreeBSD-6 NFS server (same problem when the NFS server is NetBSD). All 3 > clients have a small RAM, which may be a cause for faster apparition of the > issue. Please try the attached patch to see whether it makes a difference. -- Andre Index: kern/uipc_mbuf.c =================================================================== RCS file: /home/ncvs/src/sys/kern/uipc_mbuf.c,v retrieving revision 1.157 diff -u -p -r1.157 uipc_mbuf.c --- kern/uipc_mbuf.c 4 Nov 2005 17:20:53 -0000 1.157 +++ kern/uipc_mbuf.c 4 Nov 2005 18:28:02 -0000 @@ -218,10 +218,11 @@ mb_free_ext(struct mbuf *m) atomic_fetchadd_int(m->m_ext.ref_cnt, -1) == 0) { switch (m->m_ext.ext_type) { case EXT_CLUSTER: /* The packet zone is special. */ - if (*(m->m_ext.ref_cnt) == 0) - *(m->m_ext.ref_cnt) = 1; - uma_zfree(zone_pack, m); - return; /* Job done. */ + /* if (*(m->m_ext.ref_cnt) == 0) */ + /* *(m->m_ext.ref_cnt) = 1; */ + /* uma_zfree(zone_pack, m); */ + /* return; */ /* Job done. */ + uma_zfree(zone_clust, m->m_ext.ext_buf); break; case EXT_JUMBO9: uma_zfree(zone_jumbo9, m->m_ext.ext_buf); From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 18:43:04 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A90616A41F; Fri, 4 Nov 2005 18:43:04 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from aiolos.otenet.gr (aiolos.otenet.gr [195.170.0.93]) by mx1.FreeBSD.org (Postfix) with ESMTP id C51AB43D46; Fri, 4 Nov 2005 18:43:02 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by aiolos.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id jA4IgvDL026740; Fri, 4 Nov 2005 20:42:58 +0200 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id jA4IfjgB073242; Fri, 4 Nov 2005 20:41:46 +0200 (EET) (envelope-from keramida@linux.gr) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id jA4IffXt073178; Fri, 4 Nov 2005 20:41:41 +0200 (EET) (envelope-from keramida@linux.gr) Date: Fri, 4 Nov 2005 20:41:41 +0200 From: Giorgos Keramidas To: Jung-uk Kim Message-ID: <20051104184141.GA50612@flame.pc> References: <200511041203.13837.jkim@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200511041203.13837.jkim@FreeBSD.org> Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: [PATCH] Please test ACPI-CA 20051021 fix X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 18:43:04 -0000 On 2005-11-04 12:03, Jung-uk Kim wrote: > If you have booting problems *after* ACPI-CA 20051021 import, please > try this patch and let me know: > > http://people.freebsd.org/~jkim/acpica/rscalc.c.diff Thanks so much! Other unrelated UMA/mbuf problems exist too. Hopefully, patches from Andre will solve those, but I'm unable to run CURRENT since a few days ago (Nov 1), so it may take a while before I have vefiried that this is the fix. Peter Holms has mailed me the same diff a while ago, but I've been unsuccessful building a kernel with both patches applied so far. It's a bit sad that CURRENT is broken for more than 3 days in the row now, so thanks for mailing this fix :) From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 18:46:00 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A521A16A41F for ; Fri, 4 Nov 2005 18:46:00 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id F026843D5D for ; Fri, 4 Nov 2005 18:45:58 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 04 Nov 2005 18:45:57 -0000 Received: from h081217094006.dyn.cm.kabsi.at (EHLO h081217094006.dyn.cm.kabsi.at) [81.217.94.6] by mail.gmx.net (mp012) with SMTP; 04 Nov 2005 19:45:57 +0100 X-Authenticated: #16703784 From: Stefan Ehmann To: Jung-uk Kim In-Reply-To: <200511041203.13837.jkim@FreeBSD.org> References: <200511041203.13837.jkim@FreeBSD.org> Content-Type: text/plain Date: Fri, 04 Nov 2005 19:45:56 +0100 Message-Id: <1131129956.1076.0.camel@taxman.pepperland> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-acpi@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: [PATCH] Please test ACPI-CA 20051021 fix X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 18:46:00 -0000 On Fri, 2005-11-04 at 12:03 -0500, Jung-uk Kim wrote: > http://people.freebsd.org/~jkim/acpica/rscalc.c.diff No more panic here, thanks! From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 19:06:57 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 036D216A41F for ; Fri, 4 Nov 2005 19:06:57 +0000 (GMT) (envelope-from pho@holm.cc) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.FreeBSD.org (Postfix) with SMTP id D211643D46 for ; Fri, 4 Nov 2005 19:06:55 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 12244 invoked from network); 4 Nov 2005 19:06:54 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 4 Nov 2005 19:06:54 -0000 X-pair-Authenticated: 80.161.118.233 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id jA4J6rjv013095; Fri, 4 Nov 2005 20:06:53 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id jA4J6rfQ013094; Fri, 4 Nov 2005 20:06:53 +0100 (CET) (envelope-from pho) Date: Fri, 4 Nov 2005 20:06:53 +0100 From: Peter Holm To: Giorgos Keramidas Message-ID: <20051104190653.GA13074@peter.osted.lan> References: <200511041203.13837.jkim@FreeBSD.org> <20051104184141.GA50612@flame.pc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051104184141.GA50612@flame.pc> User-Agent: Mutt/1.4.2.1i Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org, Jung-uk Kim Subject: Re: [PATCH] Please test ACPI-CA 20051021 fix X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 19:06:57 -0000 On Fri, Nov 04, 2005 at 08:41:41PM +0200, Giorgos Keramidas wrote: > On 2005-11-04 12:03, Jung-uk Kim wrote: > > If you have booting problems *after* ACPI-CA 20051021 import, please > > try this patch and let me know: > > > > http://people.freebsd.org/~jkim/acpica/rscalc.c.diff > > Thanks so much! > > Other unrelated UMA/mbuf problems exist too. Hopefully, patches > from Andre will solve those, but I'm unable to run CURRENT since > a few days ago (Nov 1), so it may take a while before I have > vefiried that this is the fix. Peter Holms has mailed me the > same diff a while ago, but I've been unsuccessful building a > kernel with both patches applied so far. > Oh, no. It not the same patch. Mine was just a work around. I've been running HEAD all day, so ... what's your showstopper? - Peter > It's a bit sad that CURRENT is broken for more than 3 days in the > row now, so thanks for mailing this fix :) > > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 19:07:16 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 22A0016A456; Fri, 4 Nov 2005 19:07:16 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from smtp1-g19.free.fr (smtp1-g19.free.fr [212.27.42.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0A9143D48; Fri, 4 Nov 2005 19:07:15 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp1-g19.free.fr (Postfix) with ESMTP id 936AA5E2E8; Fri, 4 Nov 2005 20:07:14 +0100 (CET) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.13.3/8.13.3) with ESMTP id jA4J7BwJ012306; Fri, 4 Nov 2005 20:07:12 +0100 (CET) From: Thierry Herbelot To: freebsd-current@freebsd.org Date: Fri, 4 Nov 2005 20:06:59 +0100 User-Agent: KMail/1.8.2 References: <20051104092724.GA33945@xor.obsecurity.org> <200511041833.30955.thierry@herbelot.com> <436BA8B5.9070104@freebsd.org> In-Reply-To: <436BA8B5.9070104@freebsd.org> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200511042007.02526.thierry@herbelot.com> Cc: Andre Oppermann Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 19:07:16 -0000 Le Friday 4 November 2005 19:30, Andre Oppermann a écrit : > > Please try the attached patch to see whether it makes a difference. [SNIP] with the same test (ls -lR /share_disk) : the mbufs are better managed : ... 70/63680/63750 mbufs in use (current/cache/total) 64/404/468/3776 mbuf clusters in use (current/cache/total/max) 65/65095/65160 mbufs in use (current/cache/total) 64/404/468/3776 mbuf clusters in use (current/cache/total/max) but : panic: kmem_malloc(200704): kmem_map too small: 29900800 total allocated cpuid = 1 KDB: enter: panic [thread pid 730 tid 100096 ] Stopped at kdb_enter+0x2b: nop db> trace Tracing pid 730 tid 100096 td 0xc1595600 kdb_enter(c086a633) at kdb_enter+0x2b panic(c088597c,31000,1c84000,c19afd80,31000) at panic+0x127 kmem_malloc(c10600c0,31000,102,cb63cabc,c079047b) at kmem_malloc+0x89 page_alloc(0,31000,cb63caaf,102,29332e0) at page_alloc+0x1a uma_large_malloc(31000,102,c0636662,be,30fd1) at uma_large_malloc+0x3b malloc(30fd1,c08cf1a0,102,c0652867,c0934a20) at malloc+0xf5 sysctl_kern_malloc_stats(c08cf520,0,0,cb63cb98,c08cf520) at sysctl_kern_malloc_stats+0x76 sysctl_root(0,cb63cc18,2,cb63cb98,c1595600) at sysctl_root+0x11b userland_sysctl(c1595600,cb63cc18,2,8077000,bfbfea18) at userland_sysctl+0xf4 __sysctl(c1595600,cb63cd04,c,c1595600,cb63cd30) at __sysctl+0x77 syscall(2809003b,2809003b,bfbf003b,2,bfbfea18) at syscall+0x27e Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (202, FreeBSD ELF32, __sysctl), eip = 0x281494ef, esp = 0xbfbfe8cc, ebp = 0xbfbfe908 --- db> TfH From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 19:23:59 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE6D416A41F for ; Fri, 4 Nov 2005 19:23:59 +0000 (GMT) (envelope-from incmc@gmx.de) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id B180C43D48 for ; Fri, 4 Nov 2005 19:23:56 +0000 (GMT) (envelope-from incmc@gmx.de) Received: (qmail invoked by alias); 04 Nov 2005 19:23:56 -0000 Received: from dslb-084-061-012-075.pools.arcor-ip.net (EHLO ms.homeip.net) [84.61.12.75] by mail.gmx.net (mp034) with SMTP; 04 Nov 2005 20:23:56 +0100 X-Authenticated: #15946415 Received: from id4cc1a79.versanet.de ([212.204.26.121] helo=nix-rechnername-auspaehen-hier) by ms.homeip.net with esmtpsa (SSLv3:RC4-MD5:128) id 1EY7AO-0007GN-S4 for freebsd-current@freebsd.org; Fri, 04 Nov 2005 20:24:01 +0100 From: Jochen Gensch To: freebsd-current@freebsd.org Date: Fri, 4 Nov 2005 20:23:35 +0100 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511042023.36498.incmc@gmx.de> X-Y-GMX-Trusted: 0 Subject: Filesystem panic - one hd inaccessable under 6-STABLE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 19:23:59 -0000 Hi! I've encountered a very bad thing here. I was compiling openoffice, when the system suddenly paniced and rebooted. When it was booting again it said: Nov 4 19:53:15 incmc kernel: Trying to mount root from ufs:/dev/ad0s3a Nov 4 19:53:15 incmc savecore: reboot after panic: ufs_dirbad: bad dir Nov 4 19:53:15 incmc savecore: writing core to vmcore.0 The bad news is, one harddisk, which was attached via firewire lost its superblock and cannot be used any more. This is my backup drive :-(. A fsck -t uds /device ends up with: fsck -t ufs /dev/da0s1 ** /dev/da0s1 Cannot find file system superblock ioctl (GCINFO): Inappropriate ioctl for device fsck_ufs: /dev/da0s1: can't read disk label both harddrives are running with ufs2 + softupdates I'm scared :-( Cheers, Jochen From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 19:33:52 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77AE016A41F for ; Fri, 4 Nov 2005 19:33:52 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail24.syd.optusnet.com.au (mail24.syd.optusnet.com.au [211.29.133.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E89D43D49 for ; Fri, 4 Nov 2005 19:33:50 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail24.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jA4JXmYa029747 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 5 Nov 2005 06:33:48 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id jA4JXlHh072443; Sat, 5 Nov 2005 06:33:48 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jA4JXlBF072442; Sat, 5 Nov 2005 06:33:47 +1100 (EST) (envelope-from pjeremy) Date: Sat, 5 Nov 2005 06:33:47 +1100 From: Peter Jeremy To: Thierry Herbelot Message-ID: <20051104193347.GM39882@cirb503493.alcatel.com.au> References: <200511041509.07205.thierry@herbelot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <200511041509.07205.thierry@herbelot.com> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: freebsd-current@freebsd.org Subject: Re: /boot/kernel/kernel.debug on 6.0-RELEASE-i386-bootonly.iso ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 19:33:52 -0000 On Fri, 2005-Nov-04 15:09:05 +0100, Thierry Herbelot wrote: >It seems that the new ISOs are here ;-) The ISOs will always appear slightly before the official announcement - this ensures that they have a chance to propogate before people start looking for them. The Project has also stated that they are subject to change without notice at any time prior to the official announcement. (The final build has to be marked -RELEASE and get pushed to the master website. If a problem is found with it, then it will get fixed and rebuilt with the same name). [And, yes, I realise 6.0-RELEASE has been officially announced but that was about ½hr after this mail] >I was initrigued by the large size of 6.0-RELEASE-i386-bootonly.iso (43MB) >relative to 5.4-RELEASE-i386-bootonly.iso (21MB) > >The increase seems to come from a kernel.debug : is it intended ? There was a recent thread about installing kernel.debug to ensure that correct debugging symbols were available even if someone had rebuilt their kernel. I think it's an excellent idea to distribute kernel.debug because it should allow users to provide better quality problem reports. (Though I'm less certain about / being the best place to store the kernel.debug file). -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 19:41:33 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DF6F16A41F; Fri, 4 Nov 2005 19:41:33 +0000 (GMT) (envelope-from scottro@nyc.rr.com) Received: from mail.rk.net (rknet.biz [64.106.205.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0976043D48; Fri, 4 Nov 2005 19:41:32 +0000 (GMT) (envelope-from scottro@nyc.rr.com) Received: from uws1.starlofashions.com ([12.44.50.124]) by rknet.biz with MailEnable ESMTP; Fri, 04 Nov 2005 14:35:45 -0500 Received: by uws1.starlofashions.com (sSMTP sendmail emulation); Fri, 4 Nov 2005 14:41:30 -0500 Date: Fri, 4 Nov 2005 14:41:30 -0500 From: Scott Robbins To: FreeBSD Current , freebsd-stable@freebsd.org Message-ID: <20051104194130.GA95823@uws1.starlofashions.com> Mail-Followup-To: FreeBSD Current , freebsd-stable@freebsd.org References: <436B810A.7040908@FreeBSD.org> <747dc8f30511041033q71048dd3hc6a6cbaca40c2e67@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <747dc8f30511041033q71048dd3hc6a6cbaca40c2e67@mail.gmail.com> User-Agent: mutt-ng/devel-r535 (FreeBSD) Cc: Subject: Re: FreeBSD 6.0 Released X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 19:41:33 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, Nov 04, 2005 at 04:33:10PM -0200, Renato Botelho wrote: > On 11/4/05, Scott Long wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > > > It is my great pleasure and privilege to announce the availability of > > FreeBSD 6.0-RELEASE. This release is the next step in delivering the > > high performance and enterprise features that have been under > > development in the FreeBSD 5.x series for that last several years. > > Some of the many changes since 5.4 include: > > I'm having some troubles with locale after upgrade to RELENG_6. > > one example, perl warning me about my locale: There were some issues with a library upgrade at some point, it was awhile ago, and the details are hazy. (Please note that I am a different Scott and far less knowledgeable than Mr. Long, but I have a need for Japanese and got bitten by this.) There is a port, /usr/misc/localedata that was designed to fix this problem. In your shell's rc file you add PATH_LOCALE=/usr/local/share/compat/locale; export PATH_LOCAL (That's for a Bourne style shell, I am not sure of the csh syntax.) That should solve the problem. As your ports are gradually upgraded, the problem should disappear. (Or you can always do a portupgrade -af, which might not be a bad idea, as some other libraries have changed.) - -- Scott Robbins GPG KeyID EB3467D6 ( 1B848 077D 66F6 9DB0 FDC2 A409 FA54 D575 EB34 67D6) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Giles: I suspect your mother would want to... put it on the refrigerator. Buffy: Yeah. She saw these scores and her head spun around and exploded. Giles: I've been on the Hellmouth too long, that was metaphorical, yes? Buffy: Yes. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDa7lq+lTVdes0Z9YRAtIyAKC0QEPjbRwWf5a4IZcG08u7idYQigCcDIsn 2Nl5QWB3rFVRFyZNFj66pLM= =r9xW -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 19:46:30 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 79FFF16A41F for ; Fri, 4 Nov 2005 19:46:30 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0ED0743D46 for ; Fri, 4 Nov 2005 19:46:30 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp4-g19.free.fr (Postfix) with ESMTP id F1FDA401BA for ; Fri, 4 Nov 2005 20:46:28 +0100 (CET) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.13.3/8.13.3) with ESMTP id jA4JkDAm003374; Fri, 4 Nov 2005 20:46:15 +0100 (CET) From: Thierry Herbelot To: freebsd-current@freebsd.org Date: Fri, 4 Nov 2005 20:46:04 +0100 User-Agent: KMail/1.8.2 References: <200511041509.07205.thierry@herbelot.com> <20051104193347.GM39882@cirb503493.alcatel.com.au> In-Reply-To: <20051104193347.GM39882@cirb503493.alcatel.com.au> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200511042046.06753.thierry@herbelot.com> Cc: Peter Jeremy Subject: Re: /boot/kernel/kernel.debug on 6.0-RELEASE-i386-bootonly.iso ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 19:46:30 -0000 Le Friday 4 November 2005 20:33, Peter Jeremy a écrit : > > > >The increase seems to come from a kernel.debug : is it intended ? > > There was a recent thread about installing kernel.debug to ensure that > correct debugging symbols were available even if someone had rebuilt > their kernel. I think it's an excellent idea to distribute kernel.debug > because it should allow users to provide better quality problem reports. > (Though I'm less certain about / being the best place to store the > kernel.debug file). I was not precise enough : should the debug kernel be shipped also on the installation CD-ROM ? (one can easily understand why a debug kernel is installed - afterwards - with the full O.S., but it *seems* superfluous on the installation CD-ROM) my 2 euro-cents TfH From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 19:48:50 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B236016A41F for ; Fri, 4 Nov 2005 19:48:50 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BEA043D45 for ; Fri, 4 Nov 2005 19:48:49 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id jA4JmlbG076428; Fri, 4 Nov 2005 13:48:48 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <436BBB1C.1030900@centtech.com> Date: Fri, 04 Nov 2005 13:48:44 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051021 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jochen Gensch References: <200511042023.36498.incmc@gmx.de> In-Reply-To: <200511042023.36498.incmc@gmx.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1162/Thu Nov 3 11:15:03 2005 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: Filesystem panic - one hd inaccessable under 6-STABLE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 19:48:50 -0000 Jochen Gensch wrote: > Hi! > > I've encountered a very bad thing here. I was compiling openoffice, when the > system suddenly paniced and rebooted. When it was booting again it said: > > Nov 4 19:53:15 incmc kernel: Trying to mount root from ufs:/dev/ad0s3a > Nov 4 19:53:15 incmc savecore: reboot after panic: ufs_dirbad: bad dir > Nov 4 19:53:15 incmc savecore: writing core to vmcore.0 > > The bad news is, one harddisk, which was attached via firewire lost its > superblock and cannot be used any more. This is my backup drive :-(. A fsck > -t uds /device ends up with: > > fsck -t ufs /dev/da0s1 > ** /dev/da0s1 > Cannot find file system superblock > ioctl (GCINFO): Inappropriate ioctl for device > fsck_ufs: /dev/da0s1: can't read disk label > > both harddrives are running with ufs2 + softupdates > > I'm scared :-( try: fsck -b 160 /dev/da0s1 Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 19:48:57 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5000E16A43C for ; Fri, 4 Nov 2005 19:48:57 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70F5A43D45 for ; Fri, 4 Nov 2005 19:48:54 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by kane.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id jA4Jmqtd032744; Fri, 4 Nov 2005 21:48:53 +0200 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id jA4Jmhpd085311; Fri, 4 Nov 2005 21:48:43 +0200 (EET) (envelope-from keramida@linux.gr) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id jA4JmhgG085310; Fri, 4 Nov 2005 21:48:43 +0200 (EET) (envelope-from keramida@linux.gr) Date: Fri, 4 Nov 2005 21:48:43 +0200 From: Giorgos Keramidas To: Peter Holm Message-ID: <20051104194842.GA85295@flame.pc> References: <200511041203.13837.jkim@FreeBSD.org> <20051104184141.GA50612@flame.pc> <20051104190653.GA13074@peter.osted.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051104190653.GA13074@peter.osted.lan> Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Please test ACPI-CA 20051021 fix X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 19:48:57 -0000 On 2005-11-04 20:06, Peter Holm wrote: > On Fri, Nov 04, 2005 at 08:41:41PM +0200, Giorgos Keramidas wrote: > > On 2005-11-04 12:03, Jung-uk Kim wrote: > > > If you have booting problems *after* ACPI-CA 20051021 import, please > > > try this patch and let me know: > > > > > > http://people.freebsd.org/~jkim/acpica/rscalc.c.diff > > > > Thanks so much! > > > > Other unrelated UMA/mbuf problems exist too. Hopefully, patches > > from Andre will solve those, but I'm unable to run CURRENT since > > a few days ago (Nov 1), so it may take a while before I have > > vefiried that this is the fix. Peter Holms has mailed me the > > same diff a while ago, but I've been unsuccessful building a > > kernel with both patches applied so far. > > Oh, no. It not the same patch. Mine was just a work around. > I've been running HEAD all day, so ... what's your showstopper? This error message on FreeBSD/amd64: % cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -Wall \ % -Wredundant-decls -Wnested-externs -Wstrict-prototypes \ % -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual \ % -fformat-extensions -std=c99 -g -nostdinc -I- \ % -I. -I/home/build/src/sys -I/home/build/src/sys/contrib/altq \ % -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h \ % -fno-common -finline-limit=8000 --param inline-unit-growth=100 \ % --param large-function-growth=1000 -fno-omit-frame-pointer \ % -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 \ % -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables \ % -ffreestanding -Werror \ % /home/build/src/sys/amd64/ia32/ia32_signal.c % /home/build/src/sys/amd64/ia32/ia32_signal.c: In function `siginfo_to_ia32siginfo': % /home/build/src/sys/amd64/ia32/ia32_signal.c:755: error: union has no member named `sigval_int' % *** Error code 1 % % Stop in /home/build/obj/home/build/src/sys/FLAME. % *** Error code 1 % % Stop in /home/build/src. % *** Error code 1 % % Stop in /home/build/src. From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 20:09:20 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9705116A41F for ; Fri, 4 Nov 2005 20:09:20 +0000 (GMT) (envelope-from incmc@gmx.de) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id BBB1A43D48 for ; Fri, 4 Nov 2005 20:09:19 +0000 (GMT) (envelope-from incmc@gmx.de) Received: (qmail invoked by alias); 04 Nov 2005 20:09:17 -0000 Received: from dslb-084-061-012-075.pools.arcor-ip.net (EHLO ms.homeip.net) [84.61.12.75] by mail.gmx.net (mp014) with SMTP; 04 Nov 2005 21:09:17 +0100 X-Authenticated: #15946415 Received: from id4cc1a79.versanet.de ([212.204.26.121] helo=nix-rechnername-auspaehen-hier) by ms.homeip.net with esmtpsa (SSLv3:RC4-MD5:128) id 1EY7sI-0007bR-Dm; Fri, 04 Nov 2005 21:09:22 +0100 From: Jochen Gensch To: Eric Anderson , freebsd-current@freebsd.org Date: Fri, 4 Nov 2005 21:08:53 +0100 User-Agent: KMail/1.8.2 References: <200511042023.36498.incmc@gmx.de> <436BBB1C.1030900@centtech.com> In-Reply-To: <436BBB1C.1030900@centtech.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511042108.54527.incmc@gmx.de> X-Y-GMX-Trusted: 0 Cc: Subject: Re: Filesystem panic - one hd inaccessable under 6-STABLE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 20:09:20 -0000 Am Freitag 04 November 2005 20:48 schrieben Sie: > fsck -b 160 /dev/da0s1 That option doesn't exist. Jochen From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 20:18:16 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0FCA16A420; Fri, 4 Nov 2005 20:18:16 +0000 (GMT) (envelope-from nate@root.org) Received: from ylpvm12.prodigy.net (ylpvm12-ext.prodigy.net [207.115.57.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 084C243D4C; Fri, 4 Nov 2005 20:18:15 +0000 (GMT) (envelope-from nate@root.org) Received: from ylpvm01.prodigy.net (ylpvm01-int.prodigy.net [207.115.5.207]) by ylpvm12.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id jA4KIbil014365; Fri, 4 Nov 2005 15:18:37 -0500 X-ORBL: [67.119.74.222] Received: from [10.0.0.33] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by ylpvm01.prodigy.net (8.13.4 dk-milter linux/8.13.4) with ESMTP id jA4KMIGB010194; Fri, 4 Nov 2005 15:22:19 -0500 Message-ID: <436BC1D6.3080302@root.org> Date: Fri, 04 Nov 2005 12:17:26 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050723) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jung-uk Kim References: <200511041203.13837.jkim@FreeBSD.org> In-Reply-To: <200511041203.13837.jkim@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: [PATCH] Please test ACPI-CA 20051021 fix X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 20:18:17 -0000 Jung-uk Kim wrote: > If you have booting problems *after* ACPI-CA 20051021 import, please > try this patch and let me know: > > http://people.freebsd.org/~jkim/acpica/rscalc.c.diff Sorry, I had already committed the critical part of this patch just now when I saw that it worked for Peter Holm. Feel free to commit the rest of this patch whenever. It doesn't need more testing before committing. -- Nate From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 20:19:17 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D32E616A41F; Fri, 4 Nov 2005 20:19:17 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1512A43D45; Fri, 4 Nov 2005 20:19:16 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jA4KJETr085581; Fri, 4 Nov 2005 22:19:14 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 45283-03; Fri, 4 Nov 2005 22:19:12 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jA4KEUmV085500 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Nov 2005 22:14:30 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.4/8.13.4) id jA4KEZIq096731; Fri, 4 Nov 2005 22:14:35 +0200 (EET) (envelope-from ru) Date: Fri, 4 Nov 2005 22:14:35 +0200 From: Ruslan Ermilov To: Jung-uk Kim Message-ID: <20051104201435.GC63539@ip.net.ua> References: <200511041203.13837.jkim@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uBaQ+BsiqpBBIRFI" Content-Disposition: inline In-Reply-To: <200511041203.13837.jkim@FreeBSD.org> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua Cc: freebsd-acpi@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: [PATCH] Please test ACPI-CA 20051021 fix X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 20:19:18 -0000 --uBaQ+BsiqpBBIRFI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 04, 2005 at 12:03:12PM -0500, Jung-uk Kim wrote: > If you have booting problems *after* ACPI-CA 20051021 import, please=20 > try this patch and let me know: >=20 > http://people.freebsd.org/~jkim/acpica/rscalc.c.diff >=20 Doesn't fix a problem for me, still the same "memory modified after free ... val=3Dc". This is on amd64, FWIW. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --uBaQ+BsiqpBBIRFI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD4DBQFDa8EqqRfpzJluFF4RAgomAKCD9+Nc0khO/IqkfOIukbA39XnkgACXVYVB 4kgYuRXJjBTKg7fv9GJiBg== =t/Fe -----END PGP SIGNATURE----- --uBaQ+BsiqpBBIRFI-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 20:23:52 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A59E16A41F; Fri, 4 Nov 2005 20:23:52 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id D278743D45; Fri, 4 Nov 2005 20:23:51 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id B877A1A3C19; Fri, 4 Nov 2005 12:23:51 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 1CA6F51376; Fri, 4 Nov 2005 15:23:51 -0500 (EST) Date: Fri, 4 Nov 2005 15:23:51 -0500 From: Kris Kennaway To: Nathan Vidican Message-ID: <20051104202350.GA24947@xor.obsecurity.org> References: <436B915A.2070805@wmptl.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WIyZ46R2i8wDzkSu" Content-Disposition: inline In-Reply-To: <436B915A.2070805@wmptl.com> User-Agent: Mutt/1.4.2.1i Cc: questions@freebsd.org, current@freebsd.org Subject: Re: new filesystem improvements in 6.0-RELEASE, require newfs? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 20:23:52 -0000 --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 04, 2005 at 11:50:34AM -0500, Nathan Vidican wrote: > Most notably amongst the improvements/additions to 6.0-RELEASE, are those= =20 > in the filesystem area. In performing a system upgrade, does one need to= =20 > newfs/format a given partition with a new file system to make use of thes= e=20 > optimizations, or is the bonus simply in the kernel/filesystem support an= d=20 > sticking with the current UFS2 partition (5.3-RELEASE/amd64) will step-u= p=20 > to it? The latter. Kris --WIyZ46R2i8wDzkSu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDa8NWWry0BWjoQKURArE5AKC8fKBdkDQGk47i9EWZQq4Olj+c3gCg4xWP jbG38u/J7ksTSIKUliKnryc= =4FzS -----END PGP SIGNATURE----- --WIyZ46R2i8wDzkSu-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 20:26:13 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 666D016A41F; Fri, 4 Nov 2005 20:26:13 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id C769943D46; Fri, 4 Nov 2005 20:26:12 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id jA4KZ9fj094273; Fri, 4 Nov 2005 15:35:09 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: Nate Lawson Date: Fri, 4 Nov 2005 15:25:55 -0500 User-Agent: KMail/1.6.2 References: <200511041203.13837.jkim@FreeBSD.org> <436BC1D6.3080302@root.org> In-Reply-To: <436BC1D6.3080302@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200511041525.56697.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV devel-20050919/1162/Thu Nov 3 12:15:03 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-acpi@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: [PATCH] Please test ACPI-CA 20051021 fix X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 20:26:13 -0000 On Friday 04 November 2005 03:17 pm, Nate Lawson wrote: > Jung-uk Kim wrote: > > If you have booting problems *after* ACPI-CA 20051021 import, > > please try this patch and let me know: > > > > http://people.freebsd.org/~jkim/acpica/rscalc.c.diff > > Sorry, I had already committed the critical part of this patch just > now when I saw that it worked for Peter Holm. No problem. > Feel free to commit the rest of this patch whenever. It doesn't need > more testing before committing. Since you have committed the most important part and there are other problem reports, I'll wait little bit longer. ;-) Thanks, Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 20:40:09 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6C5516A421; Fri, 4 Nov 2005 20:40:09 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A94A43D58; Fri, 4 Nov 2005 20:40:08 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 90F181FF9AB; Fri, 4 Nov 2005 21:40:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 21A351FF9A7; Fri, 4 Nov 2005 21:40:05 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 7C71815839; Fri, 4 Nov 2005 20:36:24 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 7965115380; Fri, 4 Nov 2005 20:36:24 +0000 (UTC) Date: Fri, 4 Nov 2005 20:36:24 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Ruslan Ermilov In-Reply-To: <20051104201435.GC63539@ip.net.ua> Message-ID: References: <200511041203.13837.jkim@FreeBSD.org> <20051104201435.GC63539@ip.net.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-acpi@FreeBSD.org, freebsd-current@FreeBSD.org, Jung-uk Kim Subject: Re: [PATCH] Please test ACPI-CA 20051021 fix X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 20:40:10 -0000 On Fri, 4 Nov 2005, Ruslan Ermilov wrote: > On Fri, Nov 04, 2005 at 12:03:12PM -0500, Jung-uk Kim wrote: > > If you have booting problems *after* ACPI-CA 20051021 import, please > > try this patch and let me know: > > > > http://people.freebsd.org/~jkim/acpica/rscalc.c.diff > > > Doesn't fix a problem for me, still the same "memory modified > after free ... val=c". This is on amd64, FWIW. does it go away when you re0add option atpic ? -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 20:44:35 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A815316A41F; Fri, 4 Nov 2005 20:44:35 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E1AE43D6A; Fri, 4 Nov 2005 20:44:35 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id jA4KrYO9095037; Fri, 4 Nov 2005 15:53:34 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: "Moore, Robert" Date: Fri, 4 Nov 2005 15:44:20 -0500 User-Agent: KMail/1.6.2 References: <971FCB6690CD0E4898387DBF7552B90E03518C0F@orsmsx403.amr.corp.intel.com> In-Reply-To: <971FCB6690CD0E4898387DBF7552B90E03518C0F@orsmsx403.amr.corp.intel.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200511041544.22224.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV devel-20050919/1162/Thu Nov 3 12:15:03 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-acpi@FreeBSD.org, freebsd-current@FreeBSD.org, Ruslan Ermilov Subject: Re: [PATCH] Please test ACPI-CA 20051021 fix X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 20:44:35 -0000 On Friday 04 November 2005 03:37 pm, Moore, Robert wrote: > There is also this part of the patch in rsmisc, did you apply that? > > > +++ source/components/resources/rsmisc.c 3 Nov 2005 22:59:44 > -0000 > @@ -329,7 +329,7 @@ > ItemCount = AcpiRsDecodeBitmask (*((UINT8 *) Source), > Destination); > if (ItemCount) > { > - Resource->Length += Resource->Length + (ItemCount > - 1); + Resource->Length += (ItemCount - 1); > } I didn't put rsmisc.c patch. I'll update it soon. Thanks! Jung-uk Kim > > -----Original Message----- > > From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- > > acpi@freebsd.org] On Behalf Of Ruslan Ermilov > > Sent: Friday, November 04, 2005 12:15 PM > > To: Jung-uk Kim > > Cc: freebsd-acpi@freebsd.org; freebsd-current@freebsd.org > > Subject: Re: [PATCH] Please test ACPI-CA 20051021 fix > > > > On Fri, Nov 04, 2005 at 12:03:12PM -0500, Jung-uk Kim wrote: > > > If you have booting problems *after* ACPI-CA 20051021 import, > > > please try this patch and let me know: > > > > > > http://people.freebsd.org/~jkim/acpica/rscalc.c.diff > > > > Doesn't fix a problem for me, still the same "memory modified > > after free ... val=c". This is on amd64, FWIW. > > > > > > Cheers, > > -- > > Ruslan Ermilov > > ru@FreeBSD.org > > FreeBSD committer From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 20:53:50 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5480616A41F; Fri, 4 Nov 2005 20:53:50 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBA5843D46; Fri, 4 Nov 2005 20:53:49 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id jA4L2nL2095383; Fri, 4 Nov 2005 16:02:49 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-current@FreeBSD.org Date: Fri, 4 Nov 2005 15:53:34 -0500 User-Agent: KMail/1.6.2 References: <200511041203.13837.jkim@FreeBSD.org> In-Reply-To: <200511041203.13837.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200511041553.36559.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV devel-20050919/1162/Thu Nov 3 12:15:03 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-acpi@FreeBSD.org Subject: [PATCH#2] Please test ACPI-CA 20051021 fix X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 20:53:50 -0000 On Friday 04 November 2005 12:03 pm, Jung-uk Kim wrote: > If you have booting problems *after* ACPI-CA 20051021 import, > please try this patch and let me know: > > http://people.freebsd.org/~jkim/acpica/rscalc.c.diff And here is another patch: http://people.freebsd.org/~jkim/acpica/rsmisc.c.diff Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 21:05:45 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA21316A41F; Fri, 4 Nov 2005 21:05:45 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id E686C43D48; Fri, 4 Nov 2005 21:05:44 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jA4L5hY5086878; Fri, 4 Nov 2005 23:05:43 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 45594-06-3; Fri, 4 Nov 2005 23:05:43 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jA4L4RwA086828 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Nov 2005 23:04:27 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.4/8.13.4) id jA4L4ViE090466; Fri, 4 Nov 2005 23:04:31 +0200 (EET) (envelope-from ru) Date: Fri, 4 Nov 2005 23:04:31 +0200 From: Ruslan Ermilov To: "Bjoern A. Zeeb" Message-ID: <20051104210431.GE63539@ip.net.ua> References: <200511041203.13837.jkim@FreeBSD.org> <20051104201435.GC63539@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Iy2CUD6FdotTkhwY" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua Cc: freebsd-acpi@FreeBSD.org, freebsd-current@FreeBSD.org, Jung-uk Kim Subject: Re: [PATCH] Please test ACPI-CA 20051021 fix X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 21:05:45 -0000 --Iy2CUD6FdotTkhwY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 04, 2005 at 08:36:24PM +0000, Bjoern A. Zeeb wrote: > On Fri, 4 Nov 2005, Ruslan Ermilov wrote: >=20 > > On Fri, Nov 04, 2005 at 12:03:12PM -0500, Jung-uk Kim wrote: > > > If you have booting problems *after* ACPI-CA 20051021 import, please > > > try this patch and let me know: > > > > > > http://people.freebsd.org/~jkim/acpica/rscalc.c.diff > > > > > Doesn't fix a problem for me, still the same "memory modified > > after free ... val=3Dc". This is on amd64, FWIW. >=20 > does it go away when you re0add option atpic ? >=20 I don't care to test this because the above patch (not what's in CVS now) plus a fix to rsmisc.c made the problem go away. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --Iy2CUD6FdotTkhwY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDa8zfqRfpzJluFF4RAsDGAJ9RDhk9PZcpl1u8RyyrQOPQA+1RlwCfal/X z09OWnaSBZCmLmwtAzuoMBg= =AAII -----END PGP SIGNATURE----- --Iy2CUD6FdotTkhwY-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 21:11:54 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9A8216A420; Fri, 4 Nov 2005 21:11:54 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C08043D66; Fri, 4 Nov 2005 21:11:52 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id jA4LKr1g096069; Fri, 4 Nov 2005 16:20:53 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: Ruslan Ermilov Date: Fri, 4 Nov 2005 16:11:38 -0500 User-Agent: KMail/1.6.2 References: <200511041203.13837.jkim@FreeBSD.org> <20051104210431.GE63539@ip.net.ua> In-Reply-To: <20051104210431.GE63539@ip.net.ua> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200511041611.40545.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV devel-20050919/1162/Thu Nov 3 12:15:03 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: "Bjoern A. Zeeb" , freebsd-acpi@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: [PATCH] Please test ACPI-CA 20051021 fix X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 21:11:55 -0000 On Friday 04 November 2005 04:04 pm, Ruslan Ermilov wrote: > On Fri, Nov 04, 2005 at 08:36:24PM +0000, Bjoern A. Zeeb wrote: > > On Fri, 4 Nov 2005, Ruslan Ermilov wrote: > > > On Fri, Nov 04, 2005 at 12:03:12PM -0500, Jung-uk Kim wrote: > > > > If you have booting problems *after* ACPI-CA 20051021 import, > > > > please try this patch and let me know: > > > > > > > > http://people.freebsd.org/~jkim/acpica/rscalc.c.diff > > > > > > Doesn't fix a problem for me, still the same "memory modified > > > after free ... val=c". This is on amd64, FWIW. > > > > does it go away when you re0add option atpic ? > > I don't care to test this because the above patch (not what's in > CVS now) plus a fix to rsmisc.c made the problem go away. I'll commit them soon, then. Thanks! Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 21:28:42 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9415816A421 for ; Fri, 4 Nov 2005 21:28:42 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from ant.bwct.de (ant.bwct.de [85.159.14.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A1E243D6D for ; Fri, 4 Nov 2005 21:28:37 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by ant.bwct.de (8.12.11/8.12.11) with ESMTP id jA4LSPrg020971; Fri, 4 Nov 2005 22:28:29 +0100 (CET) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id jA4LSDJs007957 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Nov 2005 22:28:14 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id jA4LSDQV005728; Fri, 4 Nov 2005 22:28:13 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id jA4LRwgG005727; Fri, 4 Nov 2005 22:27:58 +0100 (CET) (envelope-from ticso) Date: Fri, 4 Nov 2005 22:27:58 +0100 From: Bernd Walter To: Eric Anderson Message-ID: <20051104212757.GD4813@cicely12.cicely.de> References: <200511042023.36498.incmc@gmx.de> <436BBB1C.1030900@centtech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <436BBB1C.1030900@centtech.com> X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 X-Spam-Report: * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on cicely12.cicely.de Cc: Jochen Gensch , freebsd-current@freebsd.org Subject: Re: Filesystem panic - one hd inaccessable under 6-STABLE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 21:28:42 -0000 On Fri, Nov 04, 2005 at 01:48:44PM -0600, Eric Anderson wrote: > Jochen Gensch wrote: > >Hi! > > > >I've encountered a very bad thing here. I was compiling openoffice, when > >the system suddenly paniced and rebooted. When it was booting again it > >said: > > > >Nov 4 19:53:15 incmc kernel: Trying to mount root from ufs:/dev/ad0s3a > >Nov 4 19:53:15 incmc savecore: reboot after panic: ufs_dirbad: bad dir > >Nov 4 19:53:15 incmc savecore: writing core to vmcore.0 > > > >The bad news is, one harddisk, which was attached via firewire lost its > >superblock and cannot be used any more. This is my backup drive :-(. A > >fsck -t uds /device ends up with: > > > >fsck -t ufs /dev/da0s1 > >** /dev/da0s1 > >Cannot find file system superblock > >ioctl (GCINFO): Inappropriate ioctl for device > >fsck_ufs: /dev/da0s1: can't read disk label If you have the filesystem on a slice (e.g. da0s1) and not a partition (e.g. da0s1e) it shouldn't be an UFS one. > >both harddrives are running with ufs2 + softupdates Then check with disklabel da0s1 what partitions you have and use the 4.2BSD ones. > >I'm scared :-( > > try: > > fsck -b 160 /dev/da0s1 fsck_ufs - fsck won't pass -b option I think, but that requires a 4.2BSD partition as well. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 21:42:33 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3367E16A41F; Fri, 4 Nov 2005 21:42:33 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF82443D49; Fri, 4 Nov 2005 21:42:32 +0000 (GMT) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.1/8.13.1) with ESMTP id jA4LpWFb097221; Fri, 4 Nov 2005 16:51:33 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-acpi@FreeBSD.org Date: Fri, 4 Nov 2005 16:42:18 -0500 User-Agent: KMail/1.6.2 References: <200511041203.13837.jkim@FreeBSD.org> <200511041553.36559.jkim@FreeBSD.org> In-Reply-To: <200511041553.36559.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200511041642.19865.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV devel-20050919/1162/Thu Nov 3 12:15:03 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-current@FreeBSD.org Subject: Re: [PATCH#2] Please test ACPI-CA 20051021 fix X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 21:42:33 -0000 On Friday 04 November 2005 03:53 pm, Jung-uk Kim wrote: > On Friday 04 November 2005 12:03 pm, Jung-uk Kim wrote: > > If you have booting problems *after* ACPI-CA 20051021 import, > > please try this patch and let me know: > > > > http://people.freebsd.org/~jkim/acpica/rscalc.c.diff > > And here is another patch: > > http://people.freebsd.org/~jkim/acpica/rsmisc.c.diff These two patches are committed. Big thanks to Robert Moore for analyzing and fixing these issues so quickly! Cheers, Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 21:51:58 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3767816A41F for ; Fri, 4 Nov 2005 21:51:58 +0000 (GMT) (envelope-from incmc@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 5808D43D45 for ; Fri, 4 Nov 2005 21:51:56 +0000 (GMT) (envelope-from incmc@gmx.de) Received: (qmail invoked by alias); 04 Nov 2005 21:51:55 -0000 Received: from dslb-084-061-012-075.pools.arcor-ip.net (EHLO ms.homeip.net) [84.61.12.75] by mail.gmx.net (mp016) with SMTP; 04 Nov 2005 22:51:55 +0100 X-Authenticated: #15946415 Received: from id4cc1a79.versanet.de ([212.204.26.121] helo=nix-rechnername-auspaehen-hier) by ms.homeip.net with esmtpsa (SSLv3:RC4-MD5:128) id 1EY9Tb-0008QZ-M7; Fri, 04 Nov 2005 22:51:59 +0100 From: Jochen Gensch To: ticso@cicely.de, freebsd-current@freebsd.org Date: Fri, 4 Nov 2005 22:51:33 +0100 User-Agent: KMail/1.8.2 References: <200511042023.36498.incmc@gmx.de> <436BBB1C.1030900@centtech.com> <20051104212757.GD4813@cicely12.cicely.de> In-Reply-To: <20051104212757.GD4813@cicely12.cicely.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511042251.33902.incmc@gmx.de> X-Y-GMX-Trusted: 0 Cc: Subject: Re: Filesystem panic - one hd inaccessable under 6-STABLE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 21:51:58 -0000 Am Freitag 04 November 2005 22:27 schrieb Bernd Walter: > If you have the filesystem on a slice (e.g. da0s1) and not a partition > (e.g. da0s1e) it shouldn't be an UFS one. I simply use the whole harddrive without subdividing partitions. Why souldn't that slice be ufs? > Then check with disklabel da0s1 what partitions you have and use the > 4.2BSD ones. disklabel da0s1 # /dev/da0s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 320159322 0 unused 0 0 # "raw" part, don't edit As you can see, nothing left. However I don't know what it looked like before. I was able to mount da0s1 directly, so maybe there wasn't any partition anyway since I used the entire disk at once (I'm not that used to filesystem issues)? Jochen From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 23:53:32 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 194FA16A41F; Fri, 4 Nov 2005 23:53:32 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id A728643D75; Fri, 4 Nov 2005 23:53:26 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id jA4NrOCm030835 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Nov 2005 02:53:24 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id jA4NrI1Y030834; Sat, 5 Nov 2005 02:53:18 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Sat, 5 Nov 2005 02:53:18 +0300 From: Gleb Smirnoff To: Andre Oppermann Message-ID: <20051104235318.GL91530@cell.sick.ru> References: <20051104092724.GA33945@xor.obsecurity.org> <436B885B.6010609@freebsd.org> <20051104163526.GC82727@flame.pc> <200511041833.30955.thierry@herbelot.com> <436B9E4C.1030506@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <436B9E4C.1030506@freebsd.org> User-Agent: Mutt/1.5.6i Cc: freebsd-current@FreeBSD.org, thierry@herbelot.com Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 23:53:32 -0000 On Fri, Nov 04, 2005 at 06:45:48PM +0100, Andre Oppermann wrote: A> >This isssue is seen on 3 different PCs running recent -current, clients A> >for a FreeBSD-6 NFS server (same problem when the NFS server is NetBSD). A> >All 3 clients have a small RAM, which may be a cause for faster apparition A> >of the issue. A> A> Hmmm... There are way too many in the packet cache (zone). Normally they A> should get free'd back into the mbuf and cluster zones if there are too A> many. A> I have to track down why UMA isn't doing that. I can easily reproduce the following situation: glebius@morannon:~:|>vmstat -z | grep mbuf mbuf_packet: 256, 0, 18446744073709526976, 24896, 68208 mbuf: 256, 0, 25026, 68, 470970 mbuf_cluster: 2048, 25280, 25280, 0, 25280 mbuf_jumbo_9k: 9216, 0, 0, 0, 0 mbuf_jumbo_16k: 16384, 0, 0, 0, 0 mbuf_ext_refcnt: 4, 0, 0, 0, 0 glebius@morannon:~:|>netstat -m 386/24964/25350 mbufs in use (current/cache/total) 384/24896/25280/25280 mbuf clusters in use (current/cache/total/max) 0/5/6576 sfbufs in use (current/peak/max) 864K/56033K/56897K bytes allocated to network (current/cache/total) 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 0 calls to protocol drain routines In this state any cluster allocations fail. All I need to do is to download several Mb via bge(4) NIC. Backing out your changes fixes the problem. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 00:23:24 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25AFF16A41F for ; Sat, 5 Nov 2005 00:23:24 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5E4443D48 for ; Sat, 5 Nov 2005 00:23:23 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by mail.ambrisko.com with ESMTP; 04 Nov 2005 16:23:24 -0800 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.12.11/8.12.9) with ESMTP id jA50NNIJ069959; Fri, 4 Nov 2005 16:23:23 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.12.11/8.12.11/Submit) id jA50NMbr069958; Fri, 4 Nov 2005 16:23:22 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200511050023.jA50NMbr069958@ambrisko.com> In-Reply-To: To: lynnr.junk@interactivefs.com Date: Fri, 4 Nov 2005 16:23:22 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: freebsd-current@freebsd.org Subject: Re: Problems Installing to PowerEdge 850 with SATA Drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 00:23:24 -0000 ambrisko writes: | Lynn A. Roth writes: | | I have two new Dell Poweredge 850 machines. They have an Intel ICH7 | | chipset. When I boot FreeBSD 6 RC1, the controller is identified, but | | any drives connected to the SATA ports are not detected. The drive that | | is included with the system is a Seagate 7200.7 drive. I also tried a | | Maxtor. | | I can confirm the problem on the PE850. I have it working with my | latest 4.X SATA patches (which I haven't published yet). I might | be able to look into this. | | FWIW, I my code these SATA registers in 4.X before the become alive: | ata2: Intel SATA P0 status 0 error 4050000 scontrol 0 0 1 | ata2: Intel SATA P0 status 113 error 4050000 scontrol 0 0 1 | ata2: Intel SATA P0 status 113 error 0 scontrol 0 0 1 | ata3: Intel SATA P1 status 0 error 4050000 scontrol 0 1 1 | ata3: Intel SATA P1 status 113 error 4050000 scontrol 0 1 1 | ata3: Intel SATA P1 status 113 error 0 scontrol 0 1 1 | On other Intel controllers they I don't have to acknowledge the | errors off the bat. This is sort-of the clue indirectly. The issue is that the ICH7 and maybe ICH6 have a hybrid AHCI mode in which the SATA status, error, control registers are present in AHCI for compatibility but that's all. The reset of the AHCI registers are not there so then you have to wack the registers in PCI space 0x92 to reset the controller. Doing an AHCI reset won't work since it isn't running full AHCI mode. I don't have a fix but this is the problem that I see. If we don't do the channel reset via PCI space then it can never get out of that state so no drives are found. Doug A. From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 00:34:22 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B6C0516A43D; Sat, 5 Nov 2005 00:34:22 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22A2B43D48; Sat, 5 Nov 2005 00:34:21 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id jA50YKxp031690 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Nov 2005 03:34:20 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id jA50YKoB031689; Sat, 5 Nov 2005 03:34:20 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Sat, 5 Nov 2005 03:34:20 +0300 From: Gleb Smirnoff To: Andre Oppermann Message-ID: <20051105003420.GM91530@cell.sick.ru> References: <20051104092724.GA33945@xor.obsecurity.org> <436B885B.6010609@freebsd.org> <20051104163526.GC82727@flame.pc> <200511041833.30955.thierry@herbelot.com> <436BA8B5.9070104@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="R3G7APHDIzY6R/pk" Content-Disposition: inline In-Reply-To: <436BA8B5.9070104@freebsd.org> User-Agent: Mutt/1.5.6i Cc: freebsd-current@FreeBSD.org, sam@FreeBSD.org, thierry@herbelot.com Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 00:34:23 -0000 --R3G7APHDIzY6R/pk Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Andre, Thierry, Sam, this patch should fix the problems You can't retire EXT_PACKET, because without its help we can't differ packets allocated from UMA secondary zone from clusters allocated directly from cluster zone. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE --R3G7APHDIzY6R/pk Content-Type: text/plain; charset=koi8-r Content-Disposition: attachment; filename="mbuma.patch" Index: sys/mbuf.h =================================================================== RCS file: /home/ncvs/src/sys/sys/mbuf.h,v retrieving revision 1.179 diff -u -r1.179 mbuf.h --- sys/mbuf.h 2 Nov 2005 16:20:35 -0000 1.179 +++ sys/mbuf.h 5 Nov 2005 00:29:17 -0000 @@ -185,8 +185,9 @@ */ #define EXT_CLUSTER 1 /* mbuf cluster */ #define EXT_SFBUF 2 /* sendfile(2)'s sf_bufs */ -#define EXT_JUMBO9 3 /* jumbo cluster 9216 bytes */ -#define EXT_JUMBO16 4 /* jumbo cluster 16184 bytes */ +#define EXT_PACKET 3 /* came out of Packet zone */ +#define EXT_JUMBO9 4 /* jumbo cluster 9216 bytes */ +#define EXT_JUMBO16 5 /* jumbo cluster 16184 bytes */ #define EXT_NET_DRV 100 /* custom ext_buf provided by net driver(s) */ #define EXT_MOD_TYPE 200 /* custom module's ext_buf type */ #define EXT_DISPOSABLE 300 /* can throw this buffer away w/page flipping */ Index: kern/kern_mbuf.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_mbuf.c,v retrieving revision 1.13 diff -u -r1.13 kern_mbuf.c --- kern/kern_mbuf.c 4 Nov 2005 17:20:53 -0000 1.13 +++ kern/kern_mbuf.c 5 Nov 2005 00:11:49 -0000 @@ -470,6 +470,7 @@ m->m_len = 0; m->m_flags = (flags | M_EXT); m->m_type = type; + m->m_ext.ext_type = EXT_PACKET; if (flags & M_PKTHDR) { m->m_pkthdr.rcvif = NULL; Index: kern/uipc_mbuf.c =================================================================== RCS file: /home/ncvs/src/sys/kern/uipc_mbuf.c,v retrieving revision 1.157 diff -u -r1.157 uipc_mbuf.c --- kern/uipc_mbuf.c 4 Nov 2005 17:20:53 -0000 1.157 +++ kern/uipc_mbuf.c 5 Nov 2005 00:23:41 -0000 @@ -217,12 +217,13 @@ if (*(m->m_ext.ref_cnt) == 1 || atomic_fetchadd_int(m->m_ext.ref_cnt, -1) == 0) { switch (m->m_ext.ext_type) { - case EXT_CLUSTER: /* The packet zone is special. */ - if (*(m->m_ext.ref_cnt) == 0) - *(m->m_ext.ref_cnt) = 1; + case EXT_PACKET: /* The packet zone is special. */ uma_zfree(zone_pack, m); return; /* Job done. */ break; + case EXT_CLUSTER: + uma_zfree(zone_clust, m->m_ext.ext_buf); + break; case EXT_JUMBO9: uma_zfree(zone_jumbo9, m->m_ext.ext_buf); break; --R3G7APHDIzY6R/pk-- From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 01:46:47 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 64B1E16A41F; Sat, 5 Nov 2005 01:46:47 +0000 (GMT) (envelope-from green@green.homeunix.org) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.4/8.13.1) with ESMTP id jA51kkLZ051584; Fri, 4 Nov 2005 20:46:46 -0500 (EST) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.4/8.13.1/Submit) id jA51kjvK051582; Fri, 4 Nov 2005 20:46:45 -0500 (EST) (envelope-from green) Date: Fri, 4 Nov 2005 20:46:45 -0500 From: Brian Fundakowski Feldman To: Jochen Gensch Message-ID: <20051105014645.GB37350@green.homeunix.org> References: <200511042023.36498.incmc@gmx.de> <436BBB1C.1030900@centtech.com> <20051104212757.GD4813@cicely12.cicely.de> <200511042251.33902.incmc@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200511042251.33902.incmc@gmx.de> User-Agent: Mutt/1.5.11 Cc: freebsd-current@freebsd.org, ticso@cicely.de Subject: Re: Filesystem panic - one hd inaccessable under 6-STABLE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 01:46:47 -0000 On Fri, Nov 04, 2005 at 10:51:33PM +0100, Jochen Gensch wrote: > Am Freitag 04 November 2005 22:27 schrieb Bernd Walter: > > > If you have the filesystem on a slice (e.g. da0s1) and not a partition > > (e.g. da0s1e) it shouldn't be an UFS one. > > I simply use the whole harddrive without subdividing partitions. Why souldn't > that slice be ufs? > > > > Then check with disklabel da0s1 what partitions you have and use the > > 4.2BSD ones. > > disklabel da0s1 > # /dev/da0s1: > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > c: 320159322 0 unused 0 0 # "raw" part, don't > edit > > > As you can see, nothing left. However I don't know what it looked like before. > I was able to mount da0s1 directly, so maybe there wasn't any partition > anyway since I used the entire disk at once (I'm not that used to filesystem > issues)? Well then da0s1 wouldn't have a disklabel. So try fsck_ufs -b 160 on /dev/da0s1 itself? -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 03:54:46 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D17016A41F for ; Sat, 5 Nov 2005 03:54:46 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from nic.ach.sch.gr (nic.sch.gr [194.63.238.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2659C43D70 for ; Sat, 5 Nov 2005 03:54:35 +0000 (GMT) (envelope-from keramida@linux.gr) Received: (qmail 21551 invoked by uid 207); 5 Nov 2005 03:54:34 -0000 Received: from keramida@linux.gr by nic by uid 201 with qmail-scanner-1.21 (sophie: 3.04/2.30/3.97. Clear:RC:1(81.186.70.125):. Processed in 0.640463 secs); 05 Nov 2005 03:54:34 -0000 Received: from dialup125.ach.sch.gr (HELO flame.pc) ([81.186.70.125]) (envelope-sender ) by nic.sch.gr (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 5 Nov 2005 03:54:32 -0000 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id jA53f9lU000951; Sat, 5 Nov 2005 05:41:09 +0200 (EET) (envelope-from keramida@linux.gr) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id jA53f5QQ000950; Sat, 5 Nov 2005 05:41:05 +0200 (EET) (envelope-from keramida@linux.gr) Date: Sat, 5 Nov 2005 05:41:05 +0200 From: Giorgos Keramidas To: Gleb Smirnoff Message-ID: <20051105034105.GA906@flame.pc> References: <20051104092724.GA33945@xor.obsecurity.org> <436B885B.6010609@freebsd.org> <20051104163526.GC82727@flame.pc> <200511041833.30955.thierry@herbelot.com> <436BA8B5.9070104@freebsd.org> <20051105003420.GM91530@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051105003420.GM91530@cell.sick.ru> Cc: sam@freebsd.org, freebsd-current@freebsd.org, Andre Oppermann , thierry@herbelot.com Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 03:54:46 -0000 On 2005-11-05 03:34, Gleb Smirnoff wrote: > Andre, Thierry, Sam, > > this patch should fix the problems But it panics in mb_dtor_pack() because ext_type != EXT_CLUSTER when my ath0 interface tries to associate with an AP. I had to change this too, to make things work: %%% Index: kern/kern_mbuf.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_mbuf.c,v retrieving revision 1.13 diff -u -r1.13 kern_mbuf.c --- kern/kern_mbuf.c 4 Nov 2005 17:20:53 -0000 1.13 +++ kern/kern_mbuf.c 5 Nov 2005 03:27:06 -0000 @@ -332,7 +332,7 @@ KASSERT(m->m_ext.ext_free == NULL, ("%s: ext_free != NULL", __func__)); KASSERT(m->m_ext.ext_args == NULL, ("%s: ext_args != NULL", __func__)); KASSERT(m->m_ext.ext_size == MCLBYTES, ("%s: ext_size != MCLBYTES", __func__)); - KASSERT(m->m_ext.ext_type == EXT_CLUSTER, ("%s: ext_type != EXT_CLUSTER", __func__)); + KASSERT(m->m_ext.ext_type == EXT_PACKET, ("%s: ext_type != EXT_PACKET", __func__)); KASSERT(*m->m_ext.ref_cnt == 1, ("%s: ref_cnt != 1", __func__)); #ifdef INVARIANTS trash_dtor(m->m_ext.ext_buf, MCLBYTES, arg); %%% From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 05:36:36 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C201716A420 for ; Sat, 5 Nov 2005 05:36:36 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from smtp102.rog.mail.re2.yahoo.com (smtp102.rog.mail.re2.yahoo.com [206.190.36.80]) by mx1.FreeBSD.org (Postfix) with SMTP id 1C18143D46 for ; Sat, 5 Nov 2005 05:36:35 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 14073 invoked from network); 5 Nov 2005 05:36:35 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding; b=vO7eYUu5sm2n5vJurlOFao/53HXDreTr9UTXSdI0Ct8/fCt6AFBXPsfM1r/Gs9koinsIUnctQHRmMkzgrooUie6/+R99mvXNC/OY/1J3BuEwLFByvD9gIr1/9KqjZUv0K4CCGhMvFgdhY9MEqPmvkJDRtA6sQNNORVkR07GZshA= ; Received: from unknown (HELO ?172.16.0.199?) (mikej@rogers.com@70.31.50.81 with plain) by smtp102.rog.mail.re2.yahoo.com with SMTP; 5 Nov 2005 05:36:35 -0000 Message-ID: <436C44F4.5000601@rogers.com> Date: Sat, 05 Nov 2005 00:36:52 -0500 From: Mike Jakubik User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: make kernel failiure (/usr/src/sys/i386/i386/trap.c) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 05:36:36 -0000 cc -c -O2 -pipe -fno-strict-aliasing -march=athlon -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -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 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror /usr/src/sys/i386/i386/sys_machdep.c cc -c -O2 -pipe -fno-strict-aliasing -march=athlon -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -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 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror /usr/src/sys/i386/i386/trap.c /usr/src/sys/i386/i386/trap.c: In function `trap': /usr/src/sys/i386/i386/trap.c:191: warning: implicit declaration of function `ipi_nmi_handler' /usr/src/sys/i386/i386/trap.c:191: warning: nested extern declaration of `ipi_nmi_handler' *** Error code 1 Stop in /usr/obj/usr/src/sys/DP. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. root@fbsd.local:/usr/src# From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 05:42:03 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D70916A41F for ; Sat, 5 Nov 2005 05:42:03 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA88E43D45 for ; Sat, 5 Nov 2005 05:42:02 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.54 (FreeBSD)) id 1EYGoU-000Ek1-2j for freebsd-current@freebsd.org; Sat, 05 Nov 2005 05:42:02 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.54 (FreeBSD)) id 1EYGoP-0004dN-SS for freebsd-current@freebsd.org; Fri, 04 Nov 2005 19:41:57 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17260.17957.473953.634330@roam.psg.com> Date: Fri, 4 Nov 2005 19:41:57 -1000 To: FreeBSD Current Subject: ipi_nmi_handler X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 05:42:03 -0000 at-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -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 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror /usr/src/sys/i386/i386/trap.c /usr/src/sys/i386/i386/trap.c: In function `trap': /usr/src/sys/i386/i386/trap.c:191: warning: implicit declaration of function `ipi_nmi_handler' /usr/src/sys/i386/i386/trap.c:191: warning: nested extern declaration of `ipi_nmi_handler' *** Error code 1 Stop in /usr/obj/usr/src/sys/ROAM. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. real 5m16.024s user 3m20.656s sys 0m28.480s From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 07:28:40 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55D7116A41F; Sat, 5 Nov 2005 07:28:40 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E97E43D49; Sat, 5 Nov 2005 07:28:39 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id jA57SaUc034287 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Nov 2005 10:28:37 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id jA57SaxW034286; Sat, 5 Nov 2005 10:28:36 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Sat, 5 Nov 2005 10:28:36 +0300 From: Gleb Smirnoff To: Giorgos Keramidas Message-ID: <20051105072836.GQ91530@cell.sick.ru> References: <20051104092724.GA33945@xor.obsecurity.org> <436B885B.6010609@freebsd.org> <20051104163526.GC82727@flame.pc> <200511041833.30955.thierry@herbelot.com> <436BA8B5.9070104@freebsd.org> <20051105003420.GM91530@cell.sick.ru> <20051105034105.GA906@flame.pc> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20051105034105.GA906@flame.pc> User-Agent: Mutt/1.5.6i Cc: freebsd-current@FreeBSD.org, Andre Oppermann , sam@FreeBSD.org, thierry@herbelot.com Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 07:28:40 -0000 On Sat, Nov 05, 2005 at 05:41:05AM +0200, Giorgos Keramidas wrote: G> On 2005-11-05 03:34, Gleb Smirnoff wrote: G> > Andre, Thierry, Sam, G> > G> > this patch should fix the problems G> G> But it panics in mb_dtor_pack() because ext_type != EXT_CLUSTER G> when my ath0 interface tries to associate with an AP. G> G> I had to change this too, to make things work: Yes, you are right, thanks. G> %%% G> Index: kern/kern_mbuf.c G> =================================================================== G> RCS file: /home/ncvs/src/sys/kern/kern_mbuf.c,v G> retrieving revision 1.13 G> diff -u -r1.13 kern_mbuf.c G> --- kern/kern_mbuf.c 4 Nov 2005 17:20:53 -0000 1.13 G> +++ kern/kern_mbuf.c 5 Nov 2005 03:27:06 -0000 G> @@ -332,7 +332,7 @@ G> KASSERT(m->m_ext.ext_free == NULL, ("%s: ext_free != NULL", __func__)); G> KASSERT(m->m_ext.ext_args == NULL, ("%s: ext_args != NULL", __func__)); G> KASSERT(m->m_ext.ext_size == MCLBYTES, ("%s: ext_size != MCLBYTES", __func__)); G> - KASSERT(m->m_ext.ext_type == EXT_CLUSTER, ("%s: ext_type != EXT_CLUSTER", __func__)); G> + KASSERT(m->m_ext.ext_type == EXT_PACKET, ("%s: ext_type != EXT_PACKET", __func__)); G> KASSERT(*m->m_ext.ref_cnt == 1, ("%s: ref_cnt != 1", __func__)); G> #ifdef INVARIANTS G> trash_dtor(m->m_ext.ext_buf, MCLBYTES, arg); G> %%% -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 07:51:57 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44A2116A41F for ; Sat, 5 Nov 2005 07:51:57 +0000 (GMT) (envelope-from sanewo@ba2.so-net.ne.jp) Received: from mx53.ms.so-net.ne.jp (mx53.ms.so-net.ne.jp [202.238.83.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id C17B143D46 for ; Sat, 5 Nov 2005 07:51:56 +0000 (GMT) (envelope-from sanewo@ba2.so-net.ne.jp) Received: from [127.0.0.1] (p622995.tkyoac00.ap.so-net.ne.jp [219.98.41.149]) by mx53.ms.so-net.ne.jp with ESMTP id jA57pi1p006765; Sat, 5 Nov 2005 16:51:52 +0900 (JST) Message-ID: <436C648F.3040804@ba2.so-net.ne.jp> Date: Sat, 05 Nov 2005 16:51:43 +0900 From: SANETO Takanori User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: ja, en-us, en MIME-Version: 1.0 To: Randy Bush References: <17260.17957.473953.634330@roam.psg.com> In-Reply-To: <17260.17957.473953.634330@roam.psg.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: ipi_nmi_handler X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 07:51:57 -0000 It seems that if you put STOP_NMI in your kernel config, you need SMP as well. Randy Bush wrote: > at-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -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 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror /usr/src/sys/i386/i386/trap.c > /usr/src/sys/i386/i386/trap.c: In function `trap': > /usr/src/sys/i386/i386/trap.c:191: warning: implicit declaration of function `ipi_nmi_handler' > /usr/src/sys/i386/i386/trap.c:191: warning: nested extern declaration of `ipi_nmi_handler' > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/ROAM. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > real 5m16.024s > user 3m20.656s > sys 0m28.480s > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 08:01:19 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93AC816A41F; Sat, 5 Nov 2005 08:01:19 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1D9443D46; Sat, 5 Nov 2005 08:01:18 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id jA581H6l034586 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Nov 2005 11:01:17 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id jA581GHw034585; Sat, 5 Nov 2005 11:01:16 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Sat, 5 Nov 2005 11:01:16 +0300 From: Gleb Smirnoff To: Giorgos Keramidas Message-ID: <20051105080116.GR91530@cell.sick.ru> References: <20051104092724.GA33945@xor.obsecurity.org> <436B885B.6010609@freebsd.org> <20051104163526.GC82727@flame.pc> <200511041833.30955.thierry@herbelot.com> <436BA8B5.9070104@freebsd.org> <20051105003420.GM91530@cell.sick.ru> <20051105034105.GA906@flame.pc> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="JWEK1jqKZ6MHAcjA" Content-Disposition: inline In-Reply-To: <20051105034105.GA906@flame.pc> User-Agent: Mutt/1.5.6i Cc: freebsd-current@FreeBSD.org, Andre Oppermann , sam@FreeBSD.org, thierry@herbelot.com Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 08:01:19 -0000 --JWEK1jqKZ6MHAcjA Content-Type: text/plain; charset=koi8-r Content-Disposition: inline On Sat, Nov 05, 2005 at 05:41:05AM +0200, Giorgos Keramidas wrote: G> On 2005-11-05 03:34, Gleb Smirnoff wrote: G> > Andre, Thierry, Sam, G> > G> > this patch should fix the problems G> G> But it panics in mb_dtor_pack() because ext_type != EXT_CLUSTER G> when my ath0 interface tries to associate with an AP. G> G> I had to change this too, to make things work: Updated patch. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE --JWEK1jqKZ6MHAcjA Content-Type: text/plain; charset=koi8-r Content-Disposition: attachment; filename="mbuma.patch" Index: sys/mbuf.h =================================================================== RCS file: /home/ncvs/src/sys/sys/mbuf.h,v retrieving revision 1.179 diff -u -r1.179 mbuf.h --- sys/mbuf.h 2 Nov 2005 16:20:35 -0000 1.179 +++ sys/mbuf.h 5 Nov 2005 00:29:17 -0000 @@ -185,8 +185,9 @@ */ #define EXT_CLUSTER 1 /* mbuf cluster */ #define EXT_SFBUF 2 /* sendfile(2)'s sf_bufs */ -#define EXT_JUMBO9 3 /* jumbo cluster 9216 bytes */ -#define EXT_JUMBO16 4 /* jumbo cluster 16184 bytes */ +#define EXT_PACKET 3 /* came out of Packet zone */ +#define EXT_JUMBO9 4 /* jumbo cluster 9216 bytes */ +#define EXT_JUMBO16 5 /* jumbo cluster 16184 bytes */ #define EXT_NET_DRV 100 /* custom ext_buf provided by net driver(s) */ #define EXT_MOD_TYPE 200 /* custom module's ext_buf type */ #define EXT_DISPOSABLE 300 /* can throw this buffer away w/page flipping */ Index: kern/kern_mbuf.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_mbuf.c,v retrieving revision 1.13 diff -u -r1.13 kern_mbuf.c --- kern/kern_mbuf.c 4 Nov 2005 17:20:53 -0000 1.13 +++ kern/kern_mbuf.c 5 Nov 2005 07:26:47 -0000 @@ -332,7 +332,7 @@ KASSERT(m->m_ext.ext_free == NULL, ("%s: ext_free != NULL", __func__)); KASSERT(m->m_ext.ext_args == NULL, ("%s: ext_args != NULL", __func__)); KASSERT(m->m_ext.ext_size == MCLBYTES, ("%s: ext_size != MCLBYTES", __func__)); - KASSERT(m->m_ext.ext_type == EXT_CLUSTER, ("%s: ext_type != EXT_CLUSTER", __func__)); + KASSERT(m->m_ext.ext_type == EXT_PACKET, ("%s: ext_type != EXT_CLUSTER", __func__)); KASSERT(*m->m_ext.ref_cnt == 1, ("%s: ref_cnt != 1", __func__)); #ifdef INVARIANTS trash_dtor(m->m_ext.ext_buf, MCLBYTES, arg); @@ -470,6 +470,7 @@ m->m_len = 0; m->m_flags = (flags | M_EXT); m->m_type = type; + m->m_ext.ext_type = EXT_PACKET; if (flags & M_PKTHDR) { m->m_pkthdr.rcvif = NULL; Index: kern/uipc_mbuf.c =================================================================== RCS file: /home/ncvs/src/sys/kern/uipc_mbuf.c,v retrieving revision 1.157 diff -u -r1.157 uipc_mbuf.c --- kern/uipc_mbuf.c 4 Nov 2005 17:20:53 -0000 1.157 +++ kern/uipc_mbuf.c 5 Nov 2005 00:23:41 -0000 @@ -217,12 +217,13 @@ if (*(m->m_ext.ref_cnt) == 1 || atomic_fetchadd_int(m->m_ext.ref_cnt, -1) == 0) { switch (m->m_ext.ext_type) { - case EXT_CLUSTER: /* The packet zone is special. */ - if (*(m->m_ext.ref_cnt) == 0) - *(m->m_ext.ref_cnt) = 1; + case EXT_PACKET: /* The packet zone is special. */ uma_zfree(zone_pack, m); return; /* Job done. */ break; + case EXT_CLUSTER: + uma_zfree(zone_clust, m->m_ext.ext_buf); + break; case EXT_JUMBO9: uma_zfree(zone_jumbo9, m->m_ext.ext_buf); break; --JWEK1jqKZ6MHAcjA-- From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 08:45:52 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41D4316A41F for ; Sat, 5 Nov 2005 08:45:52 +0000 (GMT) (envelope-from Peter_Losher@isc.org) Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3F8C43D49 for ; Sat, 5 Nov 2005 08:45:51 +0000 (GMT) (envelope-from Peter_Losher@isc.org) Received: from dalek.isc.org (dalek.isc.org [IPv6:2001:4f8:3:bb::73]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by farside.isc.org (Postfix) with ESMTP id 93E0A677F6; Sat, 5 Nov 2005 08:45:51 +0000 (UTC) (envelope-from Peter_Losher@isc.org) From: Peter Losher Organization: ISC To: freebsd-current@freebsd.org Date: Sat, 5 Nov 2005 00:45:48 -0800 User-Agent: KMail/1.8.2 References: <200511032222.jA3MMq4a087797@ambrisko.com> In-Reply-To: <200511032222.jA3MMq4a087797@ambrisko.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3892116.GWjVDZLOzX"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200511050045.50215.Peter_Losher@isc.org> Cc: "Lynn A. Roth" Subject: Re: Problems Installing to PowerEdge 850 with SATA Drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 08:45:52 -0000 --nextPart3892116.GWjVDZLOzX Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 03 November 2005 02:22 pm, Doug Ambrisko wrote: > I can confirm the problem on the PE850. I have it working with my > latest 4.X SATA patches (which I haven't published yet). I might > be able to look into this. Curious - does this also happen w/ 5.4? Best Wishes - Peter=20 (who has some PE850's coming his way, so is a interested party) =2D-=20 Peter_Losher@isc.org | ISC | OpenPGP 0xE8048D08 | "The bits must flow" --nextPart3892116.GWjVDZLOzX Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDbHE+PtVx9OgEjQgRAsIwAJ92H02N43ey2U1DJLn08Bty1zqn7gCfQnKU Grb7ZOu+g7pGT3EvLoNi+R8= =TXrW -----END PGP SIGNATURE----- --nextPart3892116.GWjVDZLOzX-- From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 08:49:27 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C452516A41F; Sat, 5 Nov 2005 08:49:27 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC60643D49; Sat, 5 Nov 2005 08:49:26 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id jA58nOZT035357 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 5 Nov 2005 11:49:25 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id jA58nOrF035356; Sat, 5 Nov 2005 11:49:24 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Sat, 5 Nov 2005 11:49:24 +0300 From: Gleb Smirnoff To: Giorgos Keramidas Message-ID: <20051105084924.GT91530@cell.sick.ru> References: <20051104092724.GA33945@xor.obsecurity.org> <436B885B.6010609@freebsd.org> <20051104163526.GC82727@flame.pc> <200511041833.30955.thierry@herbelot.com> <436BA8B5.9070104@freebsd.org> <20051105003420.GM91530@cell.sick.ru> <20051105034105.GA906@flame.pc> <20051105080116.GR91530@cell.sick.ru> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="pZs/OQEoSSbxGlYw" Content-Disposition: inline In-Reply-To: <20051105080116.GR91530@cell.sick.ru> User-Agent: Mutt/1.5.6i Cc: freebsd-current@FreeBSD.org, Andre Oppermann , sam@FreeBSD.org, thierry@herbelot.com Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 08:49:27 -0000 --pZs/OQEoSSbxGlYw Content-Type: text/plain; charset=koi8-r Content-Disposition: inline On Sat, Nov 05, 2005 at 11:01:16AM +0300, Gleb Smirnoff wrote: T> On Sat, Nov 05, 2005 at 05:41:05AM +0200, Giorgos Keramidas wrote: T> G> On 2005-11-05 03:34, Gleb Smirnoff wrote: T> G> > Andre, Thierry, Sam, T> G> > T> G> > this patch should fix the problems T> G> T> G> But it panics in mb_dtor_pack() because ext_type != EXT_CLUSTER T> G> when my ath0 interface tries to associate with an AP. T> G> T> G> I had to change this too, to make things work: T> T> Updated patch. One more update. Since I have removed this block: if (*(m->m_ext.ref_cnt) == 0) *(m->m_ext.ref_cnt) = 1; I have also altered KASSERT in mb_dtor_pack(). I don't like inventing an incorrect invariant check and then adding helpers to avoid it being triggered. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE --pZs/OQEoSSbxGlYw Content-Type: text/plain; charset=koi8-r Content-Disposition: attachment; filename="mbuma.patch" Index: sys/mbuf.h =================================================================== RCS file: /home/ncvs/src/sys/sys/mbuf.h,v retrieving revision 1.179 diff -u -r1.179 mbuf.h --- sys/mbuf.h 2 Nov 2005 16:20:35 -0000 1.179 +++ sys/mbuf.h 5 Nov 2005 00:29:17 -0000 @@ -185,8 +185,9 @@ */ #define EXT_CLUSTER 1 /* mbuf cluster */ #define EXT_SFBUF 2 /* sendfile(2)'s sf_bufs */ -#define EXT_JUMBO9 3 /* jumbo cluster 9216 bytes */ -#define EXT_JUMBO16 4 /* jumbo cluster 16184 bytes */ +#define EXT_PACKET 3 /* came out of Packet zone */ +#define EXT_JUMBO9 4 /* jumbo cluster 9216 bytes */ +#define EXT_JUMBO16 5 /* jumbo cluster 16184 bytes */ #define EXT_NET_DRV 100 /* custom ext_buf provided by net driver(s) */ #define EXT_MOD_TYPE 200 /* custom module's ext_buf type */ #define EXT_DISPOSABLE 300 /* can throw this buffer away w/page flipping */ Index: kern/kern_mbuf.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_mbuf.c,v retrieving revision 1.13 diff -u -r1.13 kern_mbuf.c --- kern/kern_mbuf.c 4 Nov 2005 17:20:53 -0000 1.13 +++ kern/kern_mbuf.c 5 Nov 2005 08:47:28 -0000 @@ -332,8 +332,8 @@ KASSERT(m->m_ext.ext_free == NULL, ("%s: ext_free != NULL", __func__)); KASSERT(m->m_ext.ext_args == NULL, ("%s: ext_args != NULL", __func__)); KASSERT(m->m_ext.ext_size == MCLBYTES, ("%s: ext_size != MCLBYTES", __func__)); - KASSERT(m->m_ext.ext_type == EXT_CLUSTER, ("%s: ext_type != EXT_CLUSTER", __func__)); - KASSERT(*m->m_ext.ref_cnt == 1, ("%s: ref_cnt != 1", __func__)); + KASSERT(m->m_ext.ext_type == EXT_PACKET, ("%s: ext_type != EXT_PACKET", __func__)); + KASSERT(*m->m_ext.ref_cnt <= 1, ("%s: ref_cnt > 1", __func__)); #ifdef INVARIANTS trash_dtor(m->m_ext.ext_buf, MCLBYTES, arg); #endif @@ -470,6 +470,7 @@ m->m_len = 0; m->m_flags = (flags | M_EXT); m->m_type = type; + m->m_ext.ext_type = EXT_PACKET; if (flags & M_PKTHDR) { m->m_pkthdr.rcvif = NULL; Index: kern/uipc_mbuf.c =================================================================== RCS file: /home/ncvs/src/sys/kern/uipc_mbuf.c,v retrieving revision 1.157 diff -u -r1.157 uipc_mbuf.c --- kern/uipc_mbuf.c 4 Nov 2005 17:20:53 -0000 1.157 +++ kern/uipc_mbuf.c 5 Nov 2005 00:23:41 -0000 @@ -217,12 +217,13 @@ if (*(m->m_ext.ref_cnt) == 1 || atomic_fetchadd_int(m->m_ext.ref_cnt, -1) == 0) { switch (m->m_ext.ext_type) { - case EXT_CLUSTER: /* The packet zone is special. */ - if (*(m->m_ext.ref_cnt) == 0) - *(m->m_ext.ref_cnt) = 1; + case EXT_PACKET: /* The packet zone is special. */ uma_zfree(zone_pack, m); return; /* Job done. */ break; + case EXT_CLUSTER: + uma_zfree(zone_clust, m->m_ext.ext_buf); + break; case EXT_JUMBO9: uma_zfree(zone_jumbo9, m->m_ext.ext_buf); break; --pZs/OQEoSSbxGlYw-- From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 09:15:54 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C786516A41F for ; Sat, 5 Nov 2005 09:15:54 +0000 (GMT) (envelope-from Jan.Grant@bristol.ac.uk) Received: from dirg.bris.ac.uk (dirg.bris.ac.uk [137.222.10.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 681EC43D46 for ; Sat, 5 Nov 2005 09:15:54 +0000 (GMT) (envelope-from Jan.Grant@bristol.ac.uk) Received: from mail.ilrt.bris.ac.uk ([137.222.16.62]) by dirg.bris.ac.uk with esmtp (Exim 4.54) id 1EYK9P-00065P-O4; Sat, 05 Nov 2005 09:15:53 +0000 Received: from cmjg (helo=localhost) by mail.ilrt.bris.ac.uk with local-esmtp (Exim 4.50) id 1EYK9M-0006R9-DP; Sat, 05 Nov 2005 09:15:48 +0000 Date: Sat, 5 Nov 2005 09:15:48 +0000 (GMT) From: Jan Grant X-X-Sender: cmjg@mail.ilrt.bris.ac.uk To: Vincent Blondel In-Reply-To: <1131123111.2379.14.camel@wbedllfs.xtra-net.org> Message-ID: References: <1131123111.2379.14.camel@wbedllfs.xtra-net.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Jan Grant X-Spam-Score: -1.4 X-Spam-Level: - Cc: current@freebsd.org Subject: Re: Cant load plugin libjavaplugin_oji.so X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 09:15:54 -0000 On Fri, 4 Nov 2005, Vincent Blondel wrote: > Dears, > > I get a cisco PIX firewall and to access the built-in web interface (PDM > - PIX Cisco Device Manager), it is highly recommended to use Netscape > Navigator 4.78 and Linux JVM 1.4.1_02. That's recommended because there was a problem with the PDM that meant it didn't like newer JVMs. FWIW if you're able to update the PDM you should find it'll work with a native firefox and jdk-1.5. Not quite the answer you were after, perhaps, but it's a pretty straightforward process to update the PDM image. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ Engraved runic alphabets should not be multiplied unnecessarily. From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 09:24:53 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A26D516A41F for ; Sat, 5 Nov 2005 09:24:53 +0000 (GMT) (envelope-from dsh@vlink.ru) Received: from deliver.smtp.vlink.ru (vlink-0.avtlg.ru [83.239.142.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F63943D4C for ; Sat, 5 Nov 2005 09:24:51 +0000 (GMT) (envelope-from dsh@vlink.ru) Received: from smtp.smtp.vlink.ru (clamav.smtp.vlink.ru [192.168.4.1]) by deliver.smtp.vlink.ru (Postfix) with ESMTP id 9D63AFECDB8 for ; Sat, 5 Nov 2005 12:24:49 +0300 (MSK) Received: from neva.vlink.ru (neva.vlink.ru [217.107.252.29]) by smtp.smtp.vlink.ru (Postfix) with ESMTP id 5E39C10098B2 for ; Sat, 5 Nov 2005 12:24:49 +0300 (MSK) Received: from neva.vlink.ru (localhost [127.0.0.1]) by neva.vlink.ru (8.13.4/8.13.4) with ESMTP id jA59OgVH025245 for ; Sat, 5 Nov 2005 12:24:47 +0300 (MSK) (envelope-from dsh@vlink.ru) Received: (from dsh@localhost) by neva.vlink.ru (8.13.4/8.13.4/Submit) id jA59OfOJ025242; Sat, 5 Nov 2005 12:24:41 +0300 (MSK) (envelope-from dsh@vlink.ru) To: freebsd-current@freebsd.org From: Denis Shaposhnikov Date: Sat, 05 Nov 2005 12:24:41 +0300 Message-ID: <878xw3bg6e.fsf@neva.vlink.ru> User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.17 (Jumbo Shrimp, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: ClamAV using ClamSMTP Subject: lost a lots of keypresses X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 09:24:53 -0000 Hi! Something strange with fresh HEAD. It lost some of keyboard's keypresses when I typing on the keyboard. I've tried SCHEDULE and SCHED_4BSD, with and without PREEMTION, and different hw.acpi.cpu.cx_lowest. No difference. -- DSS5-RIPE DSS-RIPN 2:550/5068@fidonet 2:550/5069@fidonet mailto:dsh@vlink.ru http://neva.vlink.ru/~dsh/ From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 10:12:13 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A5D016A41F for ; Sat, 5 Nov 2005 10:12:13 +0000 (GMT) (envelope-from incmc@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 4579F43D46 for ; Sat, 5 Nov 2005 10:12:11 +0000 (GMT) (envelope-from incmc@gmx.de) Received: (qmail invoked by alias); 05 Nov 2005 10:12:10 -0000 Received: from dslb-084-061-012-075.pools.arcor-ip.net (EHLO ms.homeip.net) [84.61.12.75] by mail.gmx.net (mp009) with SMTP; 05 Nov 2005 11:12:10 +0100 X-Authenticated: #15946415 Received: from id4cc1a79.versanet.de ([212.204.26.121] helo=nix-rechnername-auspaehen-hier) by ms.homeip.net with esmtpsa (SSLv3:RC4-MD5:128) id 1EYL1w-000GyX-6b; Sat, 05 Nov 2005 11:12:12 +0100 From: Jochen Gensch To: Brian Fundakowski Feldman , freebsd-current@freebsd.org Date: Sat, 5 Nov 2005 11:11:47 +0100 User-Agent: KMail/1.8.2 References: <200511042023.36498.incmc@gmx.de> <200511042251.33902.incmc@gmx.de> <20051105014645.GB37350@green.homeunix.org> In-Reply-To: <20051105014645.GB37350@green.homeunix.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511051111.48295.incmc@gmx.de> X-Y-GMX-Trusted: 0 Cc: Subject: Re: Filesystem panic - one hd inaccessable under 6-STABLE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 10:12:13 -0000 Am Samstag 05 November 2005 02:46 schrieben Sie: > Well then da0s1 wouldn't have a disklabel. So try fsck_ufs -b 160 on > /dev/da0s1 itself? That fixed it. Didn't know there is a second superblock. Thanks for the quick help! Cheers, Jochen From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 12:19:49 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FEBB16A41F for ; Sat, 5 Nov 2005 12:19:49 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0912343D46 for ; Sat, 5 Nov 2005 12:19:48 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.54 (FreeBSD)) id 1EYN1Q-000LEO-AY; Sat, 05 Nov 2005 12:19:48 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.54 (FreeBSD)) id 1EYN1P-0005Bb-6R; Sat, 05 Nov 2005 02:19:47 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17260.41826.683167.533287@roam.psg.com> Date: Sat, 5 Nov 2005 02:19:46 -1000 To: SANETO Takanori References: <17260.17957.473953.634330@roam.psg.com> <436C648F.3040804@ba2.so-net.ne.jp> Cc: FreeBSD Current Subject: Re: ipi_nmi_handler X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 12:19:49 -0000 > It seems that if you put STOP_NMI in your kernel config, you need SMP as > well. is STOP_NMI so wonderful that i should turn on SMP and the apic device? randy From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 12:52:26 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D439216A41F for ; Sat, 5 Nov 2005 12:52:26 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from nic.ach.sch.gr (nic.sch.gr [194.63.238.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3916343D4C for ; Sat, 5 Nov 2005 12:52:24 +0000 (GMT) (envelope-from keramida@linux.gr) Received: (qmail 11059 invoked by uid 207); 5 Nov 2005 12:52:23 -0000 Received: from keramida@linux.gr by nic by uid 201 with qmail-scanner-1.21 (sophie: 3.04/2.30/3.97. Clear:RC:1(81.186.70.43):. Processed in 0.560509 secs); 05 Nov 2005 12:52:23 -0000 Received: from dialup43.ach.sch.gr (HELO flame.pc) ([81.186.70.43]) (envelope-sender ) by nic.sch.gr (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 5 Nov 2005 12:52:22 -0000 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id jA5Cq7Qq001479; Sat, 5 Nov 2005 14:52:07 +0200 (EET) (envelope-from keramida@linux.gr) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id jA5Cq73S001478; Sat, 5 Nov 2005 14:52:07 +0200 (EET) (envelope-from keramida@linux.gr) Date: Sat, 5 Nov 2005 14:52:07 +0200 From: Giorgos Keramidas To: Gleb Smirnoff Message-ID: <20051105125207.GC1219@flame.pc> References: <20051104092724.GA33945@xor.obsecurity.org> <436B885B.6010609@freebsd.org> <20051104163526.GC82727@flame.pc> <200511041833.30955.thierry@herbelot.com> <436BA8B5.9070104@freebsd.org> <20051105003420.GM91530@cell.sick.ru> <20051105034105.GA906@flame.pc> <20051105080116.GR91530@cell.sick.ru> <20051105084924.GT91530@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051105084924.GT91530@cell.sick.ru> Cc: freebsd-current@FreeBSD.org, Andre Oppermann , sam@FreeBSD.org, thierry@herbelot.com Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 12:52:27 -0000 On 2005-11-05 11:49, Gleb Smirnoff wrote: > One more update. Since I have removed this block: > > if (*(m->m_ext.ref_cnt) == 0) > *(m->m_ext.ref_cnt) = 1; > > I have also altered KASSERT in mb_dtor_pack(). I don't like > inventing an incorrect invariant check and then adding helpers > to avoid it being triggered. > > [--- mbuma.patch ---] Very nice, thanks! I'll build the next kernel with the updated patch, later today. From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 12:52:53 2005 Return-Path: X-Original-To: current@FreeBSD.ORG Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A10B16A41F; Sat, 5 Nov 2005 12:52:53 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vbook.fbsd.ru (swsoft-mipt-nat.sw.ru [195.214.233.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 925D343D53; Sat, 5 Nov 2005 12:52:51 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.54 (FreeBSD)) id 1EYNXN-0000Uf-BX; Sat, 05 Nov 2005 15:52:49 +0300 From: Vladimir Grebenschikov To: "Matthew N. Dodd" In-Reply-To: <20051103092055.W84465@sasami.jurai.net> References: <1110800717.1296.19.camel@localhost> <200503231411.46948.jhb@FreeBSD.org> <1111610025.1471.6.camel@localhost> <20050323154642.J37251@sasami.jurai.net> <1131008180.1295.10.camel@localhost> <20051103092055.W84465@sasami.jurai.net> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Sat, 05 Nov 2005 15:52:48 +0300 Message-Id: <1131195168.1230.0.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: "current@freebsd.org" , John Baldwin , freebsd-mobile@FreeBSD.ORG Subject: Re: Reattach/redetect allways connected umass device - is it possible ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 12:52:53 -0000 =F7 =DE=D4, 03/11/2005 =D7 09:21 -0500, Matthew N. Dodd =D0=C9=DB=C5=D4: > On Thu, 3 Nov 2005, Vladimir Grebenschikov wrote: > > =F7 =D3=D2, 23/03/2005 =D7 15:48 -0500, Matthew N. Dodd =D0=C9=DB=C5=D4= : > >> You want this: > >> > >> ftp://ftp.jurai.net/users/winter/cam-detach.patch > >> > >> You will then be able to perform a 'camcontrol detach daX', swap cards= , > >> and run 'camcontrol rescan'. > > > > Is there any chance to get this patch commited ? > > It is useful and I am using it for half year. >=20 > Its got really bad race conditions. What kind of race ? Is it possible to avoid this race ?=20 --=20 Vladimir B. Grebenschikov vova@fbsd.ru From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 18:33:13 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B633716A41F for ; Fri, 4 Nov 2005 18:33:13 +0000 (GMT) (envelope-from rbgarga@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4033F43D5C for ; Fri, 4 Nov 2005 18:33:10 +0000 (GMT) (envelope-from rbgarga@gmail.com) Received: by wproxy.gmail.com with SMTP id i32so429408wra for ; Fri, 04 Nov 2005 10:33:10 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ovGJ6S7vlcCvTAVWqWZdfIcZAUKIyYoXjtRikaRLAcjEnfKfbPXATLOkD2iUlQMRKPznA70MJqiFe1x/JNchskdhyIme68sJuXuGbUv0NYHAZaHHR7f6itoevr42+IK83CI+TwqFF0mIomKAF6Ch3u11KfvlgZAOojqKwXW/JmA= Received: by 10.54.16.57 with SMTP id 57mr1890771wrp; Fri, 04 Nov 2005 10:33:10 -0800 (PST) Received: by 10.54.84.14 with HTTP; Fri, 4 Nov 2005 10:33:10 -0800 (PST) Message-ID: <747dc8f30511041033q71048dd3hc6a6cbaca40c2e67@mail.gmail.com> Date: Fri, 4 Nov 2005 16:33:10 -0200 From: Renato Botelho To: Scott Long In-Reply-To: <436B810A.7040908@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <436B810A.7040908@FreeBSD.org> X-Mailman-Approved-At: Sat, 05 Nov 2005 16:10:27 +0000 Cc: FreeBSD Current , freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.0 Released X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 18:33:13 -0000 On 11/4/05, Scott Long wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > It is my great pleasure and privilege to announce the availability of > FreeBSD 6.0-RELEASE. This release is the next step in delivering the > high performance and enterprise features that have been under > development in the FreeBSD 5.x series for that last several years. > Some of the many changes since 5.4 include: I'm having some troubles with locale after upgrade to RELENG_6. one example, perl warning me about my locale: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LC_ALL =3D "en_US.ISO8859-1", LANG =3D "en_US.ISO8859-1" are supported and installed on your system. perl: warning: Falling back to the standard locale ("C"). And on another machine, when I go to gnome, this start with locale US-ASCII and I can't use acents on OpenOffice. Am I doing anything wrong? -- Renato Botelho From owner-freebsd-current@FreeBSD.ORG Fri Nov 4 20:38:13 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A163116A420; Fri, 4 Nov 2005 20:38:13 +0000 (GMT) (envelope-from robert.moore@intel.com) Received: from orsfmr002.jf.intel.com (fmr17.intel.com [134.134.136.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA27043D5A; Fri, 4 Nov 2005 20:38:01 +0000 (GMT) (envelope-from robert.moore@intel.com) Received: from orsfmr101.jf.intel.com (orsfmr101.jf.intel.com [10.7.209.17]) by orsfmr002.jf.intel.com (8.12.10/8.12.10/d: major-outer.mc,v 1.1 2004/09/17 17:50:56 root Exp $) with ESMTP id jA4Kc120017593; Fri, 4 Nov 2005 20:38:01 GMT Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206]) by orsfmr101.jf.intel.com (8.12.10/8.12.10/d: major-inner.mc,v 1.2 2004/09/17 18:05:01 root Exp $) with SMTP id jA4Kc1hg014539; Fri, 4 Nov 2005 20:38:01 GMT Received: from orsmsx332.amr.corp.intel.com ([192.168.65.60]) by orsmsxvs040.jf.intel.com (SAVSMTP 3.1.7.47) with SMTP id M2005110412380032107 ; Fri, 04 Nov 2005 12:38:00 -0800 Received: from orsmsx403.amr.corp.intel.com ([192.168.65.209]) by orsmsx332.amr.corp.intel.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 4 Nov 2005 12:38:00 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 4 Nov 2005 12:37:59 -0800 Message-ID: <971FCB6690CD0E4898387DBF7552B90E03518C0F@orsmsx403.amr.corp.intel.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [PATCH] Please test ACPI-CA 20051021 fix thread-index: AcXhfx5euihtGj5dReKJCiFtJ7uRBQAAGOhw From: "Moore, Robert" To: "Ruslan Ermilov" , "Jung-uk Kim" X-OriginalArrivalTime: 04 Nov 2005 20:38:00.0862 (UTC) FILETIME=[A5CBCBE0:01C5E17F] X-Scanned-By: MIMEDefang 2.52 on 10.7.209.17 X-Mailman-Approved-At: Sat, 05 Nov 2005 16:10:27 +0000 Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org Subject: RE: [PATCH] Please test ACPI-CA 20051021 fix X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Nov 2005 20:38:14 -0000 There is also this part of the patch in rsmisc, did you apply that? +++ source/components/resources/rsmisc.c 3 Nov 2005 22:59:44 -0000 @@ -329,7 +329,7 @@ ItemCount =3D AcpiRsDecodeBitmask (*((UINT8 *) Source), Destination); if (ItemCount) { - Resource->Length +=3D Resource->Length + (ItemCount - = 1); + Resource->Length +=3D (ItemCount - 1); } > -----Original Message----- > From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- > acpi@freebsd.org] On Behalf Of Ruslan Ermilov > Sent: Friday, November 04, 2005 12:15 PM > To: Jung-uk Kim > Cc: freebsd-acpi@freebsd.org; freebsd-current@freebsd.org > Subject: Re: [PATCH] Please test ACPI-CA 20051021 fix >=20 > On Fri, Nov 04, 2005 at 12:03:12PM -0500, Jung-uk Kim wrote: > > If you have booting problems *after* ACPI-CA 20051021 import, please > > try this patch and let me know: > > > > http://people.freebsd.org/~jkim/acpica/rscalc.c.diff > > > Doesn't fix a problem for me, still the same "memory modified > after free ... val=3Dc". This is on amd64, FWIW. >=20 >=20 > Cheers, > -- > Ruslan Ermilov > ru@FreeBSD.org > FreeBSD committer From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 03:38:40 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4087816A41F for ; Sat, 5 Nov 2005 03:38:40 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE39043D45 for ; Sat, 5 Nov 2005 03:38:39 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 86245F2437 for ; Fri, 4 Nov 2005 19:38:39 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 00811-02 for ; Fri, 4 Nov 2005 19:38:38 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 72D2DF242D for ; Fri, 4 Nov 2005 19:38:38 -0800 (PST) From: Sean McNeil To: current@freebsd.org Content-Type: text/plain Organization: Sean McNeil Consulting, Inc Date: Fri, 04 Nov 2005 19:36:08 -0800 Message-Id: <1131161768.8571.9.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at mcneil.com X-Mailman-Approved-At: Sat, 05 Nov 2005 16:10:27 +0000 Cc: Subject: recent MFC code to 6-STABLE kills ipv6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: sean@mcneil.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 03:38:40 -0000 My IMAP server used to work perfectly fine with IPv6 connections from evolution. Today, there was some MFCd code that has killed it. I can no longer log into my imap server with IPv6. Investigating, I find that the interface I have tied to stf0 will not respond. I have dc0: flags=8843 mtu 1500 options=8 inet6 fe80::203:6dff:fe1a:b19b%dc0 prefixlen 64 scopeid 0x2 inet 24.199.45.54 netmask 0xfffffffc broadcast 24.199.45.55 inet6 2002:18c7:2d36:0:203:6dff:fe1a:b19b prefixlen 64 inet6 2002:18c7:2d36:: prefixlen 64 anycast ether 00:03:6d:1a:b1:9b media: Ethernet autoselect (100baseTX ) status: active sk0: flags=8843 mtu 1500 inet6 fe80::214:85ff:fe85:27b3%sk0 prefixlen 64 scopeid 0x3 inet 10.0.0.1 netmask 0xff000000 broadcast 10.255.255.255 inet6 2002:18c7:2d36:1:214:85ff:fe85:27b3 prefixlen 64 inet6 2002:18c7:2d36:1:: prefixlen 64 anycast ether 00:14:85:85:27:b3 media: Ethernet autoselect (1000baseTX ) status: active lo0: flags=8049 mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff000000 stf0: flags=1 mtu 1280 inet6 2002:18c7:2d36::1 prefixlen 16 ping6 works for www.kame.net going out my dc0 connection. fe80::214:85ff:fe85:27b3%sk0 2002:18c7:2d36:1:214:85ff:fe85:27b3 2002:18c7:2d36:1:: fe80::1%lo0 ::1 2002:18c7:2d36::1 ping6 does NOT work for fe80::203:6dff:fe1a:b19b%dc0 2002:18c7:2d36:0:203:6dff:fe1a:b19b 2002:18c7:2d36:: I have ip6fw setup, but nothing is showing as denied. This worked perfectly fine up until today. Sean From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 17:25:23 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14BC316A41F for ; Sat, 5 Nov 2005 17:25:23 +0000 (GMT) (envelope-from vladimir@math.uic.edu) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA43843D45 for ; Sat, 5 Nov 2005 17:25:22 +0000 (GMT) (envelope-from vladimir@math.uic.edu) Received: from cat.math.uic.edu (c-24-12-126-199.hsd1.il.comcast.net[24.12.126.199]) by comcast.net (sccrmhc12) with SMTP id <2005110517195901200mltc8e>; Sat, 5 Nov 2005 17:20:19 +0000 Received: (qmail 63906 invoked by uid 31415); 5 Nov 2005 17:19:43 -0000 Date: Sat, 5 Nov 2005 11:19:43 -0600 From: Vladimir Egorin To: Mike Jakubik Message-ID: <20051105171943.GA63885@math.uic.edu> References: <436C44F4.5000601@rogers.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <436C44F4.5000601@rogers.com> User-Agent: Mutt/1.5.11 Cc: current@freebsd.org Subject: Re: make kernel failiure (/usr/src/sys/i386/i386/trap.c) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 17:25:23 -0000 On Sat, Nov 05, 2005 at 12:36:52AM -0500, Mike Jakubik wrote: > cc -c -O2 -pipe -fno-strict-aliasing -march=athlon -Wall > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -std=c99 -nostdinc -I- -I. -I/usr/src/sys > -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS > -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 -mno-mmx > -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror > /usr/src/sys/i386/i386/sys_machdep.c > cc -c -O2 -pipe -fno-strict-aliasing -march=athlon -Wall > -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -std=c99 -nostdinc -I- -I. -I/usr/src/sys > -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS > -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 -mno-mmx > -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror > /usr/src/sys/i386/i386/trap.c > /usr/src/sys/i386/i386/trap.c: In function `trap': > /usr/src/sys/i386/i386/trap.c:191: warning: implicit declaration of > function `ipi_nmi_handler' > /usr/src/sys/i386/i386/trap.c:191: warning: nested extern declaration of > `ipi_nmi_handler' > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/DP. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > root@fbsd.local:/usr/src# Do you have all the stuff from DEFAULTS kernel config file included? -- Vladimir From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 17:43:24 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 253FF16A41F; Sat, 5 Nov 2005 17:43:24 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id C332A43D76; Sat, 5 Nov 2005 17:43:10 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp3-g19.free.fr (Postfix) with ESMTP id 1564935F91; Sat, 5 Nov 2005 18:43:09 +0100 (CET) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.13.3/8.13.3) with ESMTP id jA5Hh5lJ008634; Sat, 5 Nov 2005 18:43:08 +0100 (CET) From: Thierry Herbelot To: Gleb Smirnoff , freebsd-current@freebsd.org, Andre Oppermann Date: Sat, 5 Nov 2005 18:42:54 +0100 User-Agent: KMail/1.8.2 References: <20051104092724.GA33945@xor.obsecurity.org> <20051105080116.GR91530@cell.sick.ru> <20051105084924.GT91530@cell.sick.ru> In-Reply-To: <20051105084924.GT91530@cell.sick.ru> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200511051842.58644.thierry@herbelot.com> Cc: Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 17:43:24 -0000 Le Saturday 5 November 2005 09:49, vous avez écrit : > > One more update. Since I have removed this block: > > if (*(m->m_ext.ref_cnt) == 0) > *(m->m_ext.ref_cnt) = 1; > > I have also altered KASSERT in mb_dtor_pack(). I don't like > inventing an incorrect invariant check and then adding helpers > to avoid it being triggered. I have one kernel running with your latest patch : so far, so good - a recursive 'ls' on a shared disk went fine - I'm currently cvs-ing the sources from the same shared disk. TfH From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 18:16:35 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 587B016A41F for ; Sat, 5 Nov 2005 18:16:35 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FA6443D45 for ; Sat, 5 Nov 2005 18:16:35 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 3F37E46B8D; Sat, 5 Nov 2005 13:16:34 -0500 (EST) Date: Sat, 5 Nov 2005 18:16:34 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Randy Bush In-Reply-To: <17260.41826.683167.533287@roam.psg.com> Message-ID: <20051105181517.K22029@fledge.watson.org> References: <17260.17957.473953.634330@roam.psg.com> <436C648F.3040804@ba2.so-net.ne.jp> <17260.41826.683167.533287@roam.psg.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD Current Subject: Re: ipi_nmi_handler X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 18:16:35 -0000 On Sat, 5 Nov 2005, Randy Bush wrote: >> It seems that if you put STOP_NMI in your kernel config, you need SMP as >> well. > > > > is STOP_NMI so wonderful that i should turn on SMP and the apic device? STOP_NMI makes inter-processor interrupts for the debugger (and a few other things) use non-maskable interrupts instead of maskable ones. So it doesn't actually do anything if you don't have an SMP system, as there will be no inter-processor interrupts on a single-processor system. The STOP_NMI option may have been turned on by default without realizing that it wasn't quite implemented right -- it should only affect SMP systems, not be limited to compiling on them. Robert N M Watson From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 18:43:06 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 29B3916A41F for ; Sat, 5 Nov 2005 18:43:06 +0000 (GMT) (envelope-from simsek@istanbul.enderunix.org) Received: from istanbul.enderunix.org (freefall.marmara.edu.tr [193.140.143.23]) by mx1.FreeBSD.org (Postfix) with SMTP id D4D6443D48 for ; Sat, 5 Nov 2005 18:43:04 +0000 (GMT) (envelope-from simsek@istanbul.enderunix.org) Received: (qmail 45117 invoked by uid 1013); 5 Nov 2005 18:43:44 -0000 X-Mail-Scanner: Scanned by qSheff 1.0-r4 (http://www.enderunix.org/qsheff/) Message-ID: <20051105184341.45112.qmail@istanbul.enderunix.org> From: "Baris Simsek" To: FreeBSD Current Date: Sat, 05 Nov 2005 20:43:41 +0200 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-9" Content-Transfer-Encoding: 7bit Cc: Scott Long Subject: Re: FreeBSD 6.0 Released: problem with HP Pavillion X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 18:43:06 -0000 hello, Unfortunately i couldn't booted with any version of FreeBSD on HP pavillion zv5000 notebook. same result with FreeBSD 6.0 It always reboots while loading kernel. I tried latest NetBSD and it also have same problem. I'll try also OpenBSD to make sure about if it is connected to *BSD. 1 hour ago i installed OpenSolaris, and there is no problem. I installed linux before on it without any problem. I tried some boot options such as disabling ACPI. but it didn't effect. Sorry i don't have more details because it goes reboot when start to load kernel. May be, i should make kernel hacking, if i can do. I just want to know that, is there anybody has same problem, or is there anybody using FreeBSD on HP Pavilion? Although, thanks for your efforts to release FreeBSD 6. I hope i'll solve some performance problems (for example MySQL performance problem in 4.X discussed here before) regards, -- Baris Simsek http://www.enderunix.org/simsek/ From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 18:52:51 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEB4516A41F; Sat, 5 Nov 2005 18:52:51 +0000 (GMT) (envelope-from racerx@makeworld.com) Received: from makeworld.com (makeworld.com [216.201.118.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E01043D46; Sat, 5 Nov 2005 18:52:51 +0000 (GMT) (envelope-from racerx@makeworld.com) Received: from localhost (localhost.com [127.0.0.1]) by makeworld.com (Postfix) with ESMTP id 629306102; Sat, 5 Nov 2005 12:52:50 -0600 (CST) Received: from makeworld.com ([127.0.0.1]) by localhost (makeworld.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 24496-09; Sat, 5 Nov 2005 12:52:47 -0600 (CST) Received: from [216.201.118.138] (racerx.makeworld.com [216.201.118.138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by makeworld.com (Postfix) with ESMTP id 908816100; Sat, 5 Nov 2005 12:52:46 -0600 (CST) Message-ID: <436CFF83.6090907@makeworld.com> Date: Sat, 05 Nov 2005 12:52:51 -0600 From: Chris User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050930) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Baris Simsek References: <20051105184341.45112.qmail@istanbul.enderunix.org> In-Reply-To: <20051105184341.45112.qmail@istanbul.enderunix.org> X-Enigmail-Version: 0.93.0.0 OpenPGP: id=C01BC363 Content-Type: text/plain; charset=ISO-8859-9 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-2.3.3 (20050822) at makeworld.com - FreeBSD:The Power To Serve Cc: FreeBSD Current , Scott Long Subject: Re: FreeBSD 6.0 Released: problem with HP Pavillion X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: RacerX@makeworld.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 18:52:51 -0000 Baris Simsek wrote: > hello, > Unfortunately i couldn't booted with any version of FreeBSD on HP > pavillion zv5000 notebook. same result with FreeBSD 6.0 > It always reboots while loading kernel. > I tried latest NetBSD and it also have same problem. I'll try also > OpenBSD to make sure about if it is connected to *BSD. > 1 hour ago i installed OpenSolaris, and there is no problem. I installed > linux before on it without any problem. > I tried some boot options such as disabling ACPI. but it didn't effect. > Sorry i don't have more details because it goes reboot when start to > load kernel. May be, i should make kernel hacking, if i can do. > I just want to know that, is there anybody has same problem, or is there > anybody using FreeBSD on HP Pavilion? > Although, thanks for your efforts to release FreeBSD 6. I hope i'll > solve some performance problems (for example MySQL performance problem > in 4.X discussed here before) > regards, As you may or may not know - HP/Compaq has a habbit of changing/adding things to the firmware of other hardware. IE: take a normal Adaptec SCSI card, give it to HP, and they insert proprietary code. This is one of the main reasons *BSD seems to fail on HP/Compaq devices. Not all mind you, but a fair amount. Sometimes it helps to strip out some of the things in an HP device and install a vanilla chunk of hardware when installing *BSD. IE: - if a certain HP has the above mentioned SCSI card, remove it and install an Adapted. That has worked for me in the past. Just a thought. -- Best regards, Chris Lead, follow, or get the hell out of the way!! From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 19:47:25 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2D5B16A41F for ; Sat, 5 Nov 2005 19:47:25 +0000 (GMT) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8303643D48 for ; Sat, 5 Nov 2005 19:47:24 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 84427 invoked from network); 5 Nov 2005 19:49:52 -0000 Received: from c00l3r.networx.ch (HELO freebsd.org) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 5 Nov 2005 19:49:52 -0000 Message-ID: <436D0C52.7A02137F@freebsd.org> Date: Sat, 05 Nov 2005 20:47:30 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Gleb Smirnoff References: <20051104092724.GA33945@xor.obsecurity.org> <436B885B.6010609@freebsd.org> <20051104163526.GC82727@flame.pc> <200511041833.30955.thierry@herbelot.com> <436BA8B5.9070104@freebsd.org> <20051105003420.GM91530@cell.sick.ru> <20051105034105.GA906@flame.pc> <20051105080116.GR91530@cell.sick.ru> <20051105084924.GT91530@cell.sick.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: sam@FreeBSD.org, freebsd-current@FreeBSD.org, Giorgos Keramidas , thierry@herbelot.com Subject: Re: panic: mb_dtor_pack: ref_cnt != 1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 19:47:25 -0000 Gleb Smirnoff wrote: > > On Sat, Nov 05, 2005 at 11:01:16AM +0300, Gleb Smirnoff wrote: > T> On Sat, Nov 05, 2005 at 05:41:05AM +0200, Giorgos Keramidas wrote: > T> G> On 2005-11-05 03:34, Gleb Smirnoff wrote: > T> G> > Andre, Thierry, Sam, > T> G> > > T> G> > this patch should fix the problems > T> G> > T> G> But it panics in mb_dtor_pack() because ext_type != EXT_CLUSTER > T> G> when my ath0 interface tries to associate with an AP. > T> G> > T> G> I had to change this too, to make things work: > T> > T> Updated patch. > > One more update. Since I have removed this block: > > if (*(m->m_ext.ref_cnt) == 0) > *(m->m_ext.ref_cnt) = 1; > > I have also altered KASSERT in mb_dtor_pack(). I don't like > inventing an incorrect invariant check and then adding helpers > to avoid it being triggered. This block is still required for the packet zone as the refcount is not re-initialized for mbuf+cluster out of the packet zone. You may up with wrong refcounts if you remove this check. It is not directly related to the KASSERT in mb_dtor_pack() but to the way atomic_fetchadd_int() works in concurrency situations. I have committed a fix to the same effect as your proposed patch. When UMA is fixed this may be reverted again. -- Andre From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 19:56:15 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7152416A420; Sat, 5 Nov 2005 19:56:15 +0000 (GMT) (envelope-from stefan@snowfall.se) Received: from mail.snowfall.se (pluring.snowfallnet.com [82.99.34.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id F273A43D45; Sat, 5 Nov 2005 19:56:12 +0000 (GMT) (envelope-from stefan@snowfall.se) Received: from [192.168.0.100] (h73n2fls306o1037.telia.com [81.227.219.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.snowfall.se (Postfix) with ESMTP id DC66224; Sat, 5 Nov 2005 20:56:09 +0100 (CET) Message-ID: <436D0E5A.4040306@snowfall.se> Date: Sat, 05 Nov 2005 20:56:10 +0100 From: Stefan Cars User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <20051030204120.GB99588@xor.obsecurity.org> <20051030205602.GB201@xor.obsecurity.org> <4365F4D1.6020809@snowfall.se> <20051102000843.GO56043@wantadilla.lemis.com> <20051102004003.GA42673@xor.obsecurity.org> In-Reply-To: <20051102004003.GA42673@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Greg 'groggy' Lehey , Daniel Eischen , current@freebsd.org Subject: Re: MySQL crashes on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 19:56:15 -0000 Kris Kennaway wrote: > On Wed, Nov 02, 2005 at 10:38:43AM +1030, Greg 'groggy' Lehey wrote: > >>On Monday, 31 October 2005 at 11:41:21 +0100, Stefan Cars wrote: >> >>>Kris Kennaway wrote: >>> >>>>On Sun, Oct 30, 2005 at 03:52:42PM -0500, Daniel Eischen wrote: >>>> >>>>>On Sun, 30 Oct 2005, Kris Kennaway wrote: >>>>> >>>>>>On Sun, Oct 30, 2005 at 02:45:57PM +0100, Stefan Cars wrote: >>>>>> >>>>>>>No. I don't need both. Removed libpthread.so.1 and still the same >>>>>>>problem. >>>>>> >>>>>>You removed the mapping entry, or the file itself? Daniel asked for >>>>>>the latter. >>>>> >>>>>Or perhaps try using libmap.conf to map libpthread.so.1 to >>>>>libpthread.so.2 without any other mappings: >>>>> >>>>> libpthread.so.1 libpthread.so.2 >>>> >>>>This is just a partial workaround, of course, and any of your >>>>binaries that are also linked to two versions of other libraries >>>>may still experience crashes (or may start to crash later when the >>>>new libraries change further). You really want to track down and >>>>fix the root cause now, to save you hours of pain later when the >>>>problem recurs elsewhere. >>> >>>The thing is I don't need the libpthread.so.1 to libpthread.so.2 >>>mapping, it works anyway (although mysql crashes) but when mapping >>>libpthread.so* to libthr* it works perfectly. >> >>It would be nice to find the bug rather than a workaround. Can you >>get a stack dump of the server? > > > The bug is well understood and is solely on the user end (operator did > not upgrade software correctly, and caused it to be linked to two > versions of the same library), it's not a software or FreeBSD bug. > > Kris I don't think this is the case, if I use libthr.so it works perfectly, If I use libpthread.so it doesn't work. It depends on what lib I link it to. The mysqld was NOT linked to two versions of the same library. /S From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 19:59:17 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB5AB16A41F; Sat, 5 Nov 2005 19:59:17 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from ameno.mahoroba.org (gw4.mahoroba.org [218.45.22.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EEBC43D68; Sat, 5 Nov 2005 19:58:56 +0000 (GMT) (envelope-from ume@mahoroba.org) Received: from kasuga.mahoroba.org (IDENT:XsqPQ15mzA3/4PRPzaPK7+hkRiNW26kWka2Ci+OlYMX/vSnS7l8w2kztQio9/MQc@kasuga.mahoroba.org [IPv6:3ffe:501:185b:8010:20b:97ff:fe2e:b521]) (user=ume mech=CRAM-MD5 bits=0) by ameno.mahoroba.org (8.13.4/8.13.4) with ESMTP/inet6 id jA5JwiAe067435 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 6 Nov 2005 04:58:49 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Sun, 06 Nov 2005 04:58:44 +0900 Message-ID: From: Hajimu UMEMOTO To: sean@mcneil.com In-Reply-To: <1131161768.8571.9.camel@server.mcneil.com> References: <1131161768.8571.9.camel@server.mcneil.com> User-Agent: xcite1.38> Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/22.0.50 (i386-unknown-freebsd6.0) MULE/5.0 (SAKAKI) X-Operating-System: FreeBSD 6.0-STABLE X-PGP-Key: http://www.imasy.or.jp/~ume/publickey.asc X-PGP-Fingerprint: 1F00 0B9E 2164 70FC 6DC5 BF5F 04E9 F086 BF90 71FE Organization: Internet Mutual Aid Society, YOKOHAMA MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (ameno.mahoroba.org [IPv6:3ffe:501:185b:8010::1]); Sun, 06 Nov 2005 04:58:49 +0900 (JST) X-Virus-Scanned: by amavisd-new X-Virus-Status: Clean X-Spam-Status: No, score=-4.1 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on ameno.mahoroba.org Cc: current@freebsd.org Subject: Re: recent MFC code to 6-STABLE kills ipv6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 19:59:17 -0000 Hi, >>>>> On Fri, 04 Nov 2005 19:36:08 -0800 >>>>> Sean McNeil said: sean> My IMAP server used to work perfectly fine with IPv6 connections from sean> evolution. Today, there was some MFCd code that has killed it. I can sean> no longer log into my imap server with IPv6. Investigating, I find that sean> the interface I have tied to stf0 will not respond. When was your working kernel built? sean> ping6 does NOT work for sean> fe80::203:6dff:fe1a:b19b%dc0 sean> 2002:18c7:2d36:0:203:6dff:fe1a:b19b sean> 2002:18c7:2d36:: It seems an IPv6 operation for dc0 is disabled entirely. Don't you see an error message from your kernel like following? dc0: possible hardware address duplication detected, disable IPv6 Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 20:32:30 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C7B716A41F for ; Sat, 5 Nov 2005 20:32:30 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id D09C143D45 for ; Sat, 5 Nov 2005 20:32:29 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id B51871A4D81; Sat, 5 Nov 2005 12:32:29 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D0287512E8; Sat, 5 Nov 2005 15:32:28 -0500 (EST) Date: Sat, 5 Nov 2005 15:32:28 -0500 From: Kris Kennaway To: Randy Bush Message-ID: <20051105203228.GA47086@xor.obsecurity.org> References: <17260.17957.473953.634330@roam.psg.com> <436C648F.3040804@ba2.so-net.ne.jp> <17260.41826.683167.533287@roam.psg.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gKMricLos+KVdGMg" Content-Disposition: inline In-Reply-To: <17260.41826.683167.533287@roam.psg.com> User-Agent: Mutt/1.4.2.1i Cc: FreeBSD Current Subject: Re: ipi_nmi_handler X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 20:32:30 -0000 --gKMricLos+KVdGMg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 05, 2005 at 02:19:46AM -1000, Randy Bush wrote: > > It seems that if you put STOP_NMI in your kernel config, you need SMP as > > well. >=20 > >=20 > is STOP_NMI so wonderful that i should turn on SMP and the apic > device? This was fixed some hours ago. Kris --gKMricLos+KVdGMg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDbRbbWry0BWjoQKURApU0AJ9fmdAZPayn/gEc920OLuU3CNjm6wCfcq35 beUDWEIDrbKnRLFN0GO43t8= =U8s6 -----END PGP SIGNATURE----- --gKMricLos+KVdGMg-- From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 21:37:57 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B79B216A41F for ; Sat, 5 Nov 2005 21:37:57 +0000 (GMT) (envelope-from kuba@server.roztocze.com.pl) Received: from roztocze.com.pl (server.roztocze.com.pl [217.96.30.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A3A643D48 for ; Sat, 5 Nov 2005 21:37:56 +0000 (GMT) (envelope-from kuba@server.roztocze.com.pl) Received: from server.roztocze.com.pl (localhost [127.0.0.1]) by roztocze.com.pl (8.13.5/8.13.5) with ESMTP id jA5Lbrs7027720 for ; Sat, 5 Nov 2005 22:37:53 +0100 Received: (from kuba@localhost) by server.roztocze.com.pl (8.13.5/8.13.4/Submit) id jA5LbrsL027719 for freebsd-current@freebsd.org; Sat, 5 Nov 2005 22:37:53 +0100 Date: Sat, 5 Nov 2005 22:37:53 +0100 From: KubaTyszko To: freebsd-current@freebsd.org Message-ID: <20051105213753.GB26532@lbl.pl> References: <20051027022313.R675@kushnir1.kiev.ua> <43602F2F.7080500@samsco.org> <200510281404.33462.jhb@freebsd.org> <200510311955.13137.max@love2party.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200510311955.13137.max@love2party.net> User-Agent: Mutt/1.4.2i X-Virus-Scanned: by amavisd-new Subject: Re: CURRENT + amd64 + user-ppp = panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kuba@lbl.pl List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 21:37:57 -0000 On Mon, Oct 31, 2005 at 07:54:53PM +0100, Max Laier wrote: > On Friday 28 October 2005 20:04, John Baldwin wrote: > > On Wednesday 26 October 2005 09:36 pm, Scott Long wrote: > > > Vladimir Kushnir wrote: > > > > Hello, > > > > For a couple of days already my -CURRENT amd64 reliably panicks > > > > whenever I'm trying to connect via ppp (nothing fancy - playn dialup, > > > > no firewall). It's 100% reproducible both with custom kernel and with > > > > GENERIC. A typescript of kgdb is attached. > > > > > > > > I'm running now on the kernel from Oct 19 which also panicks, BTW, with > > > > "kmem_map too small" on an attempt to run something like Linux > > > > OpenOffice or Mathematica (neither kern.ipc.nmbclusters nor > > > > vm.kmem_size_max tweaking helps; besides, I've only 512 MB RAM) > > > > > > > > Regards, > > > > Vladimir > > > > > > I think that this is a result of the interrupt handler changes that John > > > Baldwin made yesterday. Can you step your source back in time and see > > > where it stops panicing? > > > > Actually, it can't be if softclock() is called directly from > > ithread_loop(). In the new code ithread_loop() calls > > ithread_execute_handlers() which would call softclock(). > > > > > > #0 doadump () at pcpu.h:172 > > > > > > > > 172 pcpu.h: No such file or directory. > > > > > > > > in pcpu.h > > > > > > > > (kgdb) where > > > > > > > > #0 doadump () at pcpu.h:172 > > > > #1 0xffffffff803c65fc in boot (howto=260) > > > > at /usr/src/sys/kern/kern_shutdown.c:399 > > > > #2 0xffffffff803c609b in panic (fmt=0xffffffff805f2f46 "from > > > > debugger") at /usr/src/sys/kern/kern_shutdown.c:555 > > > > #3 0xffffffff801a8a32 in db_panic (addr=0, have_addr=0, count=0, > > > > modif=0x0) > > > > at /usr/src/sys/ddb/db_command.c:435 > > > > #4 0xffffffff801a8f75 in db_command_loop () > > > > at /usr/src/sys/ddb/db_command.c:404 > > > > #5 0xffffffff801aae83 in db_trap (type=-1794574032, code=0) > > > > at /usr/src/sys/ddb/db_main.c:221 > > > > #6 0xffffffff803e5279 in kdb_trap (type=9, code=0, > > > > tf=0xffffffff9508fb10) > > > > at /usr/src/sys/kern/subr_kdb.c:445 > > > > #7 0xffffffff8058d84e in trap_fatal (frame=0xffffffff9508fb10, > > > > eva=18446742974715243568) at /usr/src/sys/amd64/amd64/trap.c:672 > > > > #8 0xffffffff8058ddb1 in trap (frame= > > > > {tf_rdi = 1, tf_rsi = 70876, tf_rdx = -2401050962867404578, > > > > tf_rcx = 70876, tf_r8 = 0, tf_r9 = 1, tf_rax = 5340, tf_rbx = 1, tf_rbp > > > > = -1794573296, tf_r10 = 1, tf_r11 = 4, tf_r12 = -1099511143680, tf_r13 > > > > = -1099035903488, tf_r14 = -1964245152, tf_r15 = 2, tf_trapno = 9, > > > > tf_addr = 0, tf_flags = 0, tf_err = 0, tf_rip = -2143462195, tf_cs = 8, > > > > tf_rflags = 65538, tf_rsp = -1794573360, tf_ss = 16}) at > > > > /usr/src/sys/amd64/amd64/trap.c:488 > > > > #9 0xffffffff8057b3bb in calltrap () > > > > at /usr/src/sys/amd64/amd64/exception.S:168 > > > > This looks like a page fault rather than a 'kmem_map too small' panic. > > > > > > ---Type to continue, or q to quit--- > > > > > > > > #10 0xffffffff803d5ccd in softclock (dummy=0x1) > > > > at /usr/src/sys/kern/kern_timeout.c:220 > > > > This is here: > > while (c) { > > depth++; > > ==> if (c->c_time != curticks) { > > c = TAILQ_NEXT(c, c_links.tqe); > > > > c can't be NULL due to the while loop. Are any kernel modules being > > unloaded when this happens? > > It isn't a NULL deref as "eva" is clearly non-NULL above. This makes me think > of a callout list inconsistency. Most likely - due to the rest of the thread > - this was introduced via "tn_timer_ch" in struct llinfo_nd6. I am thinking > of a double callout_stop() or something like that. The callout_stop/reset() > calls on that callout are clearly over-nested to get things from a quick > glance :-\ > > The easiest seems to be to put some good old printf() debugging in > nd6_llinfo_settimer() and see what it does. Vladimir, could you try that? > "Patch" attached. > > > > > #11 0xffffffff803b05cc in ithread_loop (arg=0xffffff0000031780) > > > > at /usr/src/sys/kern/kern_intr.c:662 > > > > #12 0xffffffff803af3cb in fork_exit ( > > > > callout=0xffffffff803b0480 , arg=0xffffff0000031780, > > > > frame=0xffffffff9508fc90) at /usr/src/sys/kern/kern_fork.c:789 > > > > #13 0xffffffff8057b71e in fork_trampoline () > > > > at /usr/src/sys/amd64/amd64/exception.S:394 > > > > #14 0x0000000000000000 in ?? () > hi. did we have that fixed or the bug already occurs ? From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 21:58:00 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E76B16A41F; Sat, 5 Nov 2005 21:58:00 +0000 (GMT) (envelope-from grog@lemis.com) Received: from ext-gw.lemis.com (ext-gw.lemis.com [150.101.14.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 958E943D45; Sat, 5 Nov 2005 21:57:59 +0000 (GMT) (envelope-from grog@lemis.com) Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.135]) by ext-gw.lemis.com (Postfix) with ESMTP id 7241C13114C; Sun, 6 Nov 2005 08:27:57 +1030 (CST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 28F40855FB; Sun, 6 Nov 2005 08:27:57 +1030 (CST) Date: Sun, 6 Nov 2005 08:27:57 +1030 From: Greg 'groggy' Lehey To: Stefan Cars Message-ID: <20051105215757.GA85332@wantadilla.lemis.com> References: <20051030204120.GB99588@xor.obsecurity.org> <20051030205602.GB201@xor.obsecurity.org> <4365F4D1.6020809@snowfall.se> <20051102000843.GO56043@wantadilla.lemis.com> <20051102004003.GA42673@xor.obsecurity.org> <436D0E5A.4040306@snowfall.se> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="M9NhX3UHpAaciwkO" Content-Disposition: inline In-Reply-To: <436D0E5A.4040306@snowfall.se> User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Cc: Daniel Eischen , current@freebsd.org, Kris Kennaway Subject: Re: MySQL crashes on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 21:58:00 -0000 --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Saturday, 5 November 2005 at 20:56:10 +0100, Stefan Cars wrote: > Kris Kennaway wrote: >> On Wed, Nov 02, 2005 at 10:38:43AM +1030, Greg 'groggy' Lehey wrote: >>> On Monday, 31 October 2005 at 11:41:21 +0100, Stefan Cars wrote: >>>> Kris Kennaway wrote: >>>>> On Sun, Oct 30, 2005 at 03:52:42PM -0500, Daniel Eischen wrote: >>>>>> On Sun, 30 Oct 2005, Kris Kennaway wrote: >>>>>>> On Sun, Oct 30, 2005 at 02:45:57PM +0100, Stefan Cars wrote: >>>>>>> >>>>>>>> No. I don't need both. Removed libpthread.so.1 and still the same >>>>>>>> problem. >>>>>>> >>>>>>> You removed the mapping entry, or the file itself? Daniel asked for >>>>>>> the latter. >>>>>> >>>>>> Or perhaps try using libmap.conf to map libpthread.so.1 to >>>>>> libpthread.so.2 without any other mappings: >>>>>> >>>>>> libpthread.so.1 libpthread.so.2 >>>>> >>>>> This is just a partial workaround, of course, and any of your >>>>> binaries that are also linked to two versions of other libraries >>>>> may still experience crashes (or may start to crash later when the >>>>> new libraries change further). You really want to track down and >>>>> fix the root cause now, to save you hours of pain later when the >>>>> problem recurs elsewhere. >>>> >>>> The thing is I don't need the libpthread.so.1 to libpthread.so.2 >>>> mapping, it works anyway (although mysql crashes) but when mapping >>>> libpthread.so* to libthr* it works perfectly. >>> >> >> The bug is well understood and is solely on the user end (operator did >> not upgrade software correctly, and caused it to be linked to two >> versions of the same library), it's not a software or FreeBSD bug. > > I don't think this is the case, if I use libthr.so it works perfectly, > If I use libpthread.so it doesn't work. It depends on what lib I link it > to. The mysqld was NOT linked to two versions of the same library. Thanks for the clarification. In that case my statement stands: >>> It would be nice to find the bug rather than a workaround. Can >>> you get a stack dump of the server? Greg -- See complete headers for address and phone numbers. --M9NhX3UHpAaciwkO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFDbSrlIubykFB6QiMRAshGAJ4hC1ew4EoyfLYeWkteGLAMDH/MdQCgk9Op FZ771v0CCF0vVhS4MMUeMGA= =20SG -----END PGP SIGNATURE----- --M9NhX3UHpAaciwkO-- From owner-freebsd-current@FreeBSD.ORG Sat Nov 5 22:33:19 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6832516A41F; Sat, 5 Nov 2005 22:33:19 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AE2843D48; Sat, 5 Nov 2005 22:33:18 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.5/8.13.5/NETPLEX) with ESMTP id jA5MXIP8022338; Sat, 5 Nov 2005 17:33:18 -0500 (EST) Date: Sat, 5 Nov 2005 17:33:17 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Stefan Cars In-Reply-To: <436D0E5A.4040306@snowfall.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: Greg 'groggy' Lehey , current@freebsd.org, Kris Kennaway Subject: Re: MySQL crashes on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Nov 2005 22:33:19 -0000 On Sat, 5 Nov 2005, Stefan Cars wrote: > > Kris Kennaway wrote: > > > > The bug is well understood and is solely on the user end (operator did > > not upgrade software correctly, and caused it to be linked to two > > versions of the same library), it's not a software or FreeBSD bug. > > > > Kris > > > I don't think this is the case, if I use libthr.so it works perfectly, > If I use libpthread.so it doesn't work. It depends on what lib I link it > to. The mysqld was NOT linked to two versions of the same library. You still haven't shown that it isn't using 2 different versions of libpthread. Unless you've done portupgrade -af, or used libmap.conf to map libpthread.so.1 -> libpthread.so.2, then you haven't shown that at all (mysqld may not be linked to 2 different libpthreads, but something it depends on may be). And was it working before you upgraded to 7.0-current? You haven't said if it was _ever_ working with libpthread or not. -- DE