From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 00:57:10 2006 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 9F35916A420 for ; Sun, 22 Jan 2006 00:57:10 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 430F643D78 for ; Sun, 22 Jan 2006 00:57:05 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 3383072DD9; Sat, 21 Jan 2006 16:57:05 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 314F272DCB for ; Sat, 21 Jan 2006 16:57:05 -0800 (PST) Date: Sat, 21 Jan 2006 16:57:05 -0800 (PST) From: Doug White To: current@freebsd.org Message-ID: <20060121163238.C62962@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Subject: i386 EFI loader -- need help X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 00:57:10 -0000 Hey folks, I've done some work to try to get the EFI loader to work on i386 and have run into some snags and gaps in my knowledge and could use a hand from people who have more experience with the boot process and toolchains and assembly code. There are 3 prinicipal parts that I need help with: 1. libefi elf32 exec() -- The code that actually goes between exiting EFI and jumping into the kernel image itself needs to be written. src/sys/boot/efi/libefi/elf_freebsd.c has the EFI part already taken care of. But from just after the call to ExitBootServices() down needs to do the necessary dance on i386 to start the kernel. I don't know what the expected environment is supposed to be and whether it needs to change from how EFI leaves things. EFI uses a flat space and disables paging when it exits. More details are in the EFI spec which is freely downloadable from Intel. 2. ELF32 self-relocator -- The self-relocation code in src/sys/boot/ia64/efi/start.S is in ia64 assembly and needs to be converted into i386 so the PE32+-wrapped-ELF-objects loader.efi binary can function. I'm not well versed enough in ia64 assembly or ELF in general to undertake this without going really, really slowly. :) 3. efi-app-ia32 toolchain target -- The spec defines PE32+ as the official binary format (32-bit PE with 64-bit relocations). Both us (via NetBSD?) and GNU cheat by having objcopy build a PE32+ binary but with a small shim that performs the ELF relocations. Our libbfd on i386 isn't configured with the efi-app-ia32 target. We include the efi-app-ia64 target on ia64 so this should just require adding some bits to the Makefile and building. _Should_. (This doesn't actually look so horrible so I'll give it a try.) After loader.efi is functional there is still the big job of conditionalizing BIOS calls in the kernel and providing EFI replacements where needed. A module to perform EFI calls from the kernel is also needed to allow access to the nvram variables and use the EFI ResetSystem() call if needed. If you need a test environment you can download the Sample Implementation from Intel which will give you a boot floppy you can pop in any PC and start up into EFI. I also have real hardware to test on that is big, white, and has a certain fruit for its logo. :) -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 04:25:56 2006 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 ED01416A420 for ; Sun, 22 Jan 2006 04:25:56 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69C2143D46 for ; Sun, 22 Jan 2006 04:25:56 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01a ([66.130.198.54]) by VL-MH-MR002.ip.videotron.ca (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTP id <0ITH00DN88B6ST80@VL-MH-MR002.ip.videotron.ca> for freebsd-current@freebsd.org; Sat, 21 Jan 2006 23:25:56 -0500 (EST) Date: Sat, 21 Jan 2006 23:25:46 -0500 From: Nicolas Blais To: freebsd-current@freebsd.org Message-id: <200601212325.54004.nb_root@videotron.ca> MIME-version: 1.0 Content-type: multipart/signed; boundary=nextPart2147917.GbglsLkB0D; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit User-Agent: KMail/1.9.1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Radeon 9550 + R300 DRM + Xorg 6.9 = freeze X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 04:25:57 -0000 --nextPart2147917.GbglsLkB0D Content-Type: multipart/mixed; boundary="Boundary-01=_Klw0DJaOBLFIzuu" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-01=_Klw0DJaOBLFIzuu Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Not my lucky day :) After upgrading my Xorg port to 6.9.0, my -CURRENT freezes at launch of kdm= =2E=20 I'm able to do nothing with the system (can't exit to debugger, can't ssh t= o=20 it). Running top in another tty while loading X at the same time shows tha= t=20 Xorg uses 99.9% of WCPU. =20 Checking around, I found that the actual freeze was due to Xorg using the R= 300=20 microcode (commenting out the Load "glx" and Load "dri" in xorg.conf makes = X=20 work again). =20 I'm lost as to where to start debugging this as I cannot ssh,=20 Ctrl-Alt-Backspace or get a dump during that freeze. Since it causes a cras= h,=20 anything logged on the harddrive is lost (no sync done...) I tried running xorgcfg (graphic mode) to see if it would record something= =20 useful in Xorg.8.log and I have it attached. For some reason, X detects my= =20 lcd as having a max res of 1280x1024, but tries to open a display for=20 1600x1200 which only makes my screen show an "Out of Resolution" message. M= y=20 console shows a message similar to "R300 Microcode loaded". I can=20 Ctrl-Alt-Backspace out of X. I've tried both dri and dri-devel with no luck. So I resume: 1. Xorg 6.9.0 + R300 DRM + dri causes freeze 2. Disable dri+glx in Xorg.conf makes X work again (without drm) 3. xorgcfg tries to start in 1600x1200 for a screen capable of only=20 1280x1024, rendering it useless. Anyone using a R300 powered card (Radeon 9550/9600) with DRM+Xorg 6.9.0 out= =20 there? dmesg: vgapci0: port 0xe000-0xe0ff mem=20 0xe8000000-0xefffffff,0xfbe00000-0xfbe0ffff irq 16 at device 0.0 on pci1 drm0: on vgapci0 info: [drm] AGP at 0xe0000000 64MB info: [drm] Initialized radeon 1.19.0 20050911 vgapci1: mem=20 0xf0000000-0xf7ffffff,0xfbf00000-0xfbf0ffff at device 0.1 on pci1 Thanks, Nicolas =2D-=20 =46reeBSD 7.0-CURRENT #0: Sat Jan 21 11:33:22 EST 2006 =20 root@clk01a:/usr/obj/usr/src/sys/CLK01A=20 PGP? (updated 16 Nov 05) : http://www.clkroot.net/security/nb_root.asc --Boundary-01=_Klw0DJaOBLFIzuu-- --nextPart2147917.GbglsLkB0D Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBD0wlR4wTBlvcsbJURAruOAJ4wMnE7XsC6aZYVk7ZoZXorROBRqwCgv4C7 idZ0bKOsMR8KVWnwEa2N/HM= =ShDc -----END PGP SIGNATURE----- --nextPart2147917.GbglsLkB0D-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 04:40:12 2006 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 A6C4D16A420 for ; Sun, 22 Jan 2006 04:40:12 +0000 (GMT) (envelope-from mcdouga9@daemon.egr.msu.edu) Received: from daemon.egr.msu.edu (daemon.egr.msu.edu [35.9.44.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 613D343D4C for ; Sun, 22 Jan 2006 04:40:12 +0000 (GMT) (envelope-from mcdouga9@daemon.egr.msu.edu) Received: by daemon.egr.msu.edu (Postfix, from userid 21281) id E84FC1CC28; Sat, 21 Jan 2006 23:40:17 -0500 (EST) Date: Sat, 21 Jan 2006 23:40:17 -0500 From: Adam McDougall To: Nicolas Blais Message-ID: <20060122044017.GT6233@egr.msu.edu> References: <200601212325.54004.nb_root@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200601212325.54004.nb_root@videotron.ca> User-Agent: Mutt/1.5.11 Cc: freebsd-current@freebsd.org Subject: Re: Radeon 9550 + R300 DRM + Xorg 6.9 = freeze X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 04:40:12 -0000 On Sat, Jan 21, 2006 at 11:25:46PM -0500, Nicolas Blais wrote: Not my lucky day :) After upgrading my Xorg port to 6.9.0, my -CURRENT freezes at launch of kdm. Anyone using a R300 powered card (Radeon 9550/9600) with DRM+Xorg 6.9.0 out there? I have the same problem but I use gnome, and X seems to freeze partway through starting X but before any apps show up in my start order. I have a Dell Latitude D810 with an X600 ati. I actually noticed this when I upgraded to xorg-server-6.9rc3 from the snap port. Disabling dri let X start for me and I did not investigate further since I never got dri to work before that anyway. I did not investigate as far as Nicolas. I did notice I could hit the power button and the HD led would flash some but not shut down, so I had to hard poweroff the laptop. From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 05:11:49 2006 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 CB9CC16A41F for ; Sun, 22 Jan 2006 05:11:49 +0000 (GMT) (envelope-from dejan.lesjak@ijs.si) Received: from mail.ijs.si (mailman.ijs.si [193.2.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5174A43D45 for ; Sun, 22 Jan 2006 05:11:49 +0000 (GMT) (envelope-from dejan.lesjak@ijs.si) Received: from localhost (mail.ijs.si [193.2.4.66]) by patsy.ijs.si (Postfix) with ESMTP id 861FF17B910; Sun, 22 Jan 2006 06:11:48 +0100 (CET) Received: from mail.ijs.si ([193.2.4.66]) by localhost (patsy.ijs.si [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 04705-14; Sun, 22 Jan 2006 06:11:46 +0100 (CET) Received: from radagast.ijs.si (radagast.ijs.si [193.2.4.168]) by patsy.ijs.si (Postfix) with ESMTP id 3B4A417B8FD; Sun, 22 Jan 2006 06:11:46 +0100 (CET) Received: from localhost.ijs.si (localhost.ijs.si [127.0.0.1]) by radagast.ijs.si (Postfix) with ESMTP id ED3D017033; Sun, 22 Jan 2006 06:11:45 +0100 (CET) From: Dejan Lesjak To: Nicolas Blais , freebsd-current@freebsd.org Date: Sun, 22 Jan 2006 06:11:45 +0100 References: <200601212325.54004.nb_root@videotron.ca> Lines: 54 User-Agent: KNode/0.10 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit Message-Id: <20060122051145.ED3D017033@radagast.ijs.si> Cc: Subject: Re: Radeon 9550 + R300 DRM + Xorg 6.9 = freeze X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 05:11:49 -0000 Nicolas Blais wrote: > Not my lucky day :) > > After upgrading my Xorg port to 6.9.0, my -CURRENT freezes at launch of > kdm. I'm able to do nothing with the system (can't exit to debugger, can't > ssh to > it). Running top in another tty while loading X at the same time shows > that Xorg uses 99.9% of WCPU. > > Checking around, I found that the actual freeze was due to Xorg using the > R300 microcode (commenting out the Load "glx" and Load "dri" in xorg.conf > makes X work again). > > I'm lost as to where to start debugging this as I cannot ssh, > Ctrl-Alt-Backspace or get a dump during that freeze. Since it causes a > crash, anything logged on the harddrive is lost (no sync done...) > > I tried running xorgcfg (graphic mode) to see if it would record something > useful in Xorg.8.log and I have it attached. For some reason, X detects my > lcd as having a max res of 1280x1024, but tries to open a display for > 1600x1200 which only makes my screen show an "Out of Resolution" message. > My console shows a message similar to "R300 Microcode loaded". I can > Ctrl-Alt-Backspace out of X. > > I've tried both dri and dri-devel with no luck. > > So I resume: > 1. Xorg 6.9.0 + R300 DRM + dri causes freeze > 2. Disable dri+glx in Xorg.conf makes X work again (without drm) > 3. xorgcfg tries to start in 1600x1200 for a screen capable of only > 1280x1024, rendering it useless. > > Anyone using a R300 powered card (Radeon 9550/9600) with DRM+Xorg 6.9.0 > out there? > > dmesg: > vgapci0: port 0xe000-0xe0ff mem > 0xe8000000-0xefffffff,0xfbe00000-0xfbe0ffff irq 16 at device 0.0 on pci1 > drm0: on vgapci0 > info: [drm] AGP at 0xe0000000 64MB > info: [drm] Initialized radeon 1.19.0 20050911 > vgapci1: mem > 0xf0000000-0xf7ffffff,0xfbf00000-0xfbf0ffff at device 0.1 on pci1 Somewhat like this: http://lists.freedesktop.org/archives/xorg/2006-January/012303.html ? You can try the mentioned patch by putting patch-radeon from here: http://www.ijs.si/~lesi/xorg/patch-radeon in x11-servers/xorg-server/files directory and reinstalling xorg-server port. Dejan From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 06:18:25 2006 Return-Path: X-Original-To: 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 1083416A420; Sun, 22 Jan 2006 06:18:23 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <43D323C3.7050004@freebsd.org> Date: Sun, 22 Jan 2006 14:18:43 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.12) Gecko/20060117 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Julian Elischer References: <43D1F384.7080406@elischer.org> In-Reply-To: <43D1F384.7080406@elischer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: kernel threads as threads. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 06:18:25 -0000 Julian Elischer wrote: > > I have made a first set of changes to allow threads to be 'forked' > within the kernel. > > I have run on the resulting kernel for some of today with no problems > other than > some statistics oddness in top which I plan on looking at next week. > > The current patch doen't remove the ability to make kernel processes, > however it does > add the ability to make threads under process 0 and alters nearly all > the users of > kernel threads to actually do this.. The exception is the aio threads, > as they seem to require > separate address spaces to work with and that requires separate proc > structures. > > I was thinking that they could act as extra threads on the calling > processes but that > is more of a rewrite than I plan right now. > > Anyhow the diffs so far are at: > > http://www.freebsd.org/~julian/kthread.diff. > > more later. > > julian in vfs_aio.c, we have to borrow user process's vmspace, creating all kthread in proc0 breaks this. David Xu From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 06:45:57 2006 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 80BA016A41F; Sun, 22 Jan 2006 06:45:57 +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 A3F0D43D55; Sun, 22 Jan 2006 06:45: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 k0M6hlls075874; Sat, 21 Jan 2006 23:43:47 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 21 Jan 2006 23:44:04 -0700 (MST) Message-Id: <20060121.234404.95801924.imp@bsdimp.com> To: deischen@freebsd.org From: "M. Warner Losh" In-Reply-To: References: <43D138C0.9040801@samsco.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]); Sat, 21 Jan 2006 23:43:50 -0700 (MST) Cc: current@freebsd.org, glebius@freebsd.org, julian@elischer.org, kris@obsecurity.org Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 06:45:57 -0000 In message: Daniel Eischen writes: : On Fri, 20 Jan 2006, Scott Long wrote: : > : > Does pthreads allow the programmer to name threads in a user and/or : > kernel visible way? Is this something that is really all that : > important? : : Only in a non-portable way. See pthread_set_name_np(3). This 'non-portable' way is in heavy use in at least one user of FreeBSD's software base. Warner From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 06:48:49 2006 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 5A4CA16A41F for ; Sun, 22 Jan 2006 06:48:49 +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 DE51043D53 for ; Sun, 22 Jan 2006 06:48:48 +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 k0M6m5Wp075894; Sat, 21 Jan 2006 23:48:05 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 21 Jan 2006 23:48:22 -0700 (MST) Message-Id: <20060121.234822.107142930.imp@bsdimp.com> To: PeterJeremy@optushome.com.au From: "M. Warner Losh" In-Reply-To: <20060121070706.GA32444@cirb503493.alcatel.com.au> References: <20060121070706.GA32444@cirb503493.alcatel.com.au> 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]); Sat, 21 Jan 2006 23:48:05 -0700 (MST) Cc: freebsd-current@freebsd.org Subject: Re: Panic due to deleting devices twice X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 06:48:49 -0000 In message: <20060121070706.GA32444@cirb503493.alcatel.com.au> Peter Jeremy writes: : When deleting a device (using device_delete_child()), all its child : devices are recursively deleted and then device_detach() is called. I think that order is backwards. We should detach the device prior to deleting the device... : Looking at device_detach(), it appears that the solution is to create : a bus_child_detached method to inform the parent that a child is being : destroyed so it can invalidate cached pointers to that child. In : practice, there are only 5 bus_child_detached methods (isa, ed, : pccard, cbb and usb), though there are far more device types attached : as children. We have this problem in a number of places in the tree (mostly network drivers). However, most of the real bus drivers don't cache pointers to children, so we've not seen this much at the present time. : Looking at the iicsmb code, it appears that iicbb and iicsmb both : cache and explicitly delete child devices and therefore both need : bus_child_detached methods. Is this correct? Is there a simpler : alternative? Yes. This is how ed deals: static void ed_child_detached(device_t dev, device_t child) { struct ed_softc *sc; sc = device_get_softc(dev); if (child == sc->miibus) sc->miibus = NULL; } Warner From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 13:38:49 2006 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 060E016A41F for ; Sun, 22 Jan 2006 13:38:49 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D5E643D45 for ; Sun, 22 Jan 2006 13:38:48 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01a ([66.130.198.54]) by VL-MO-MR001.ip.videotron.ca (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTP id <0ITH00FBZXWNUI90@VL-MO-MR001.ip.videotron.ca> for freebsd-current@freebsd.org; Sun, 22 Jan 2006 08:38:48 -0500 (EST) Date: Sun, 22 Jan 2006 08:38:41 -0500 From: Nicolas Blais In-reply-to: <20060122051145.ED3D017033@radagast.ijs.si> To: freebsd-current@freebsd.org Message-id: <200601220838.47543.nb_root@videotron.ca> MIME-version: 1.0 Content-type: multipart/signed; boundary=nextPart1137956315.4zZTazhtxx; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit References: <200601212325.54004.nb_root@videotron.ca> <20060122051145.ED3D017033@radagast.ijs.si> User-Agent: KMail/1.9.1 Cc: Dejan Lesjak Subject: Re: Radeon 9550 + R300 DRM + Xorg 6.9 = freeze X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 13:38:49 -0000 --nextPart1137956315.4zZTazhtxx Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline > > So I resume: > > 1. Xorg 6.9.0 + R300 DRM + dri causes freeze > > 2. Disable dri+glx in Xorg.conf makes X work again (without drm) > > 3. xorgcfg tries to start in 1600x1200 for a screen capable of only > > 1280x1024, rendering it useless. > > > > Anyone using a R300 powered card (Radeon 9550/9600) with DRM+Xorg 6.9.0 > > out there? > > > > dmesg: > > vgapci0: port 0xe000-0xe0ff mem > > 0xe8000000-0xefffffff,0xfbe00000-0xfbe0ffff irq 16 at device 0.0 on pci1 > > drm0: on vgapci0 > > info: [drm] AGP at 0xe0000000 64MB > > info: [drm] Initialized radeon 1.19.0 20050911 > > vgapci1: mem > > 0xf0000000-0xf7ffffff,0xfbf00000-0xfbf0ffff at device 0.1 on pci1 > > Somewhat like this: > http://lists.freedesktop.org/archives/xorg/2006-January/012303.html ? > You can try the mentioned patch by putting patch-radeon from here: > http://www.ijs.si/~lesi/xorg/patch-radeon > in x11-servers/xorg-server/files directory and reinstalling xorg-server > port. Thanks,=20 I'll give it a try right now and post results. Nicolas. =2D-=20 =46reeBSD 7.0-CURRENT #0: Sat Jan 21 11:33:22 EST 2006 =20 root@clk01a:/usr/obj/usr/src/sys/CLK01A=20 PGP? (updated 16 Nov 05) : http://www.clkroot.net/security/nb_root.asc --nextPart1137956315.4zZTazhtxx Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBD04rn4wTBlvcsbJURAuRqAJ9U3oHQiPAvaQlzqshfxrIYtqWB/ACeIsT1 53HQBHTcI/klOVU5XGLiuwY= =l4ai -----END PGP SIGNATURE----- --nextPart1137956315.4zZTazhtxx-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 14:21:19 2006 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 3E45F16A41F for ; Sun, 22 Jan 2006 14:21: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 D004043D46 for ; Sun, 22 Jan 2006 14:21:13 +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 k0MEL5Ns011087; Sun, 22 Jan 2006 09:21:05 -0500 (EST) Date: Sun, 22 Jan 2006 09:21:05 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: "M. Warner Losh" In-Reply-To: <20060121.234404.95801924.imp@bsdimp.com> 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: current@freebsd.org Subject: Re: kernel thread as real threads.. 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, 22 Jan 2006 14:21:19 -0000 On Sat, 21 Jan 2006, M. Warner Losh wrote: > In message: > Daniel Eischen writes: > : On Fri, 20 Jan 2006, Scott Long wrote: > : > > : > Does pthreads allow the programmer to name threads in a user and/or > : > kernel visible way? Is this something that is really all that > : > important? > : > : Only in a non-portable way. See pthread_set_name_np(3). > > This 'non-portable' way is in heavy use in at least one user of > FreeBSD's software base. Well, I'm not advocating its removal, just clarifying that there is no POSIX interface for setting a thread's name. I originally added that interface as a debugging aid for application developers after finding it useful myself in debugging the library. I'm not sure you want to reuse the same interface for setting kernel thread names. For KSE or libc_r type threads, it wouldn't work too well. -- DE From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 14:36:44 2006 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 57A1D16A422 for ; Sun, 22 Jan 2006 14:36:44 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1884843D58 for ; Sun, 22 Jan 2006 14:36:41 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01a ([66.130.198.54]) by VL-MO-MR002.ip.videotron.ca (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTP id <0ITI00KB70L45R70@VL-MO-MR002.ip.videotron.ca> for freebsd-current@freebsd.org; Sun, 22 Jan 2006 09:36:40 -0500 (EST) Date: Sun, 22 Jan 2006 09:36:34 -0500 From: Nicolas Blais In-reply-to: <20060122051145.ED3D017033@radagast.ijs.si> To: freebsd-current@freebsd.org Message-id: <200601220936.39652.nb_root@videotron.ca> MIME-version: 1.0 Content-type: multipart/signed; boundary=nextPart1993822.iLPNaFUaAB; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit References: <200601212325.54004.nb_root@videotron.ca> <20060122051145.ED3D017033@radagast.ijs.si> User-Agent: KMail/1.9.1 Cc: Dejan Lesjak Subject: Re: Radeon 9550 + R300 DRM + Xorg 6.9 = freeze X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 14:36:44 -0000 --nextPart1993822.iLPNaFUaAB Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline > > So I resume: > > 1. Xorg 6.9.0 + R300 DRM + dri causes freeze > > 2. Disable dri+glx in Xorg.conf makes X work again (without drm) > > 3. xorgcfg tries to start in 1600x1200 for a screen capable of only > > 1280x1024, rendering it useless. > > > > Anyone using a R300 powered card (Radeon 9550/9600) with DRM+Xorg 6.9.0 > > out there? > > > > dmesg: > > vgapci0: port 0xe000-0xe0ff mem > > 0xe8000000-0xefffffff,0xfbe00000-0xfbe0ffff irq 16 at device 0.0 on pci1 > > drm0: on vgapci0 > > info: [drm] AGP at 0xe0000000 64MB > > info: [drm] Initialized radeon 1.19.0 20050911 > > vgapci1: mem > > 0xf0000000-0xf7ffffff,0xfbf00000-0xfbf0ffff at device 0.1 on pci1 > > Somewhat like this: > http://lists.freedesktop.org/archives/xorg/2006-January/012303.html ? > You can try the mentioned patch by putting patch-radeon from here: > http://www.ijs.si/~lesi/xorg/patch-radeon > in x11-servers/xorg-server/files directory and reinstalling xorg-server > port. > > > Dejan Ok, just reinstalled xorg-server with the patch, and unfortunatly this patc= h=20 did nothing for me.=20 Same symptoms. I even checked to se if the patch was really applied and it= =20 was. I wish I knew where to start with this problem, but I can't do anything dur= ing=20 that freeze. I'm also starting to hate write_caching... Since I lived without dri before= ,=20 It's not really critical, but being able to get more than 80fps in glxgears= =20 and being able to use an OpenGL app/screensaver would be nice :) Nicolas. =2D-=20 =46reeBSD 7.0-CURRENT #0: Sat Jan 21 11:33:22 EST 2006 =20 root@clk01a:/usr/obj/usr/src/sys/CLK01A=20 PGP? (updated 16 Nov 05) : http://www.clkroot.net/security/nb_root.asc --nextPart1993822.iLPNaFUaAB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBD05h34wTBlvcsbJURAvo4AJ41ld/8HlAd4pI84cLsnS9yzfWozwCgltdb zR14pOSElSrPuC7kgdZaQMI= =jH0a -----END PGP SIGNATURE----- --nextPart1993822.iLPNaFUaAB-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 15:09:23 2006 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 7ADB916A420 for ; Sun, 22 Jan 2006 15:09:23 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (mail.gmx.de [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 318D443D5F for ; Sun, 22 Jan 2006 15:09:15 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 22 Jan 2006 15:09:14 -0000 Received: from h081217094006.dyn.cm.kabsi.at (EHLO something.pepperland) [81.217.94.6] by mail.gmx.net (mp027) with SMTP; 22 Jan 2006 16:09:14 +0100 X-Authenticated: #16703784 From: Stefan Ehmann To: Alexander Leidinger In-Reply-To: <20060120105424.m384aenq0ck4g088@netchild.homeip.net> References: <1137681189.672.4.camel@localhost> <20060120105424.m384aenq0ck4g088@netchild.homeip.net> Content-Type: text/plain Date: Sun, 22 Jan 2006 16:09:12 +0100 Message-Id: <1137942552.893.4.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: current@freebsd.org Subject: Re: panic: kmem_malloc(171642880): kmem_map too small: 31387648 total allocated X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 15:09:23 -0000 On Fri, 2006-01-20 at 10:54 +0100, Alexander Leidinger wrote: > Stefan Ehmann wrote: > > > I got this panic when trying to make -j4 buildworld. > > > > If this is relevant: My userland is some weeks old, I just had time to > > upgrade kernel yesterday (because of the ieee802.11 insecurity) and wanted > > to update the rest of the world today: > > > panic: kmem_malloc(171642880): kmem_map too small: 31387648 total allocated > > I had a similar panic yesterday, but with a negative value to kmem_malloc(). > This is with kernel & userland in sync. I hadn't time do look further. > > Another problem is a panic/hang (occured 1:3 times, booting in "Safe mode" > works) while detecting the CDROM's (atapicam). In case you're using atapicam > try to boot without it (I hadn't time yet to test it). I had similar problems. removing atatpicam fixed this. Also I could run a buildworld without a panic. Might be only by chance though (don't know how easily the panic was reproducible). From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 15:52:02 2006 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 3E0F516A41F for ; Sun, 22 Jan 2006 15:52:02 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id C35B943D46 for ; Sun, 22 Jan 2006 15:52:01 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from localhost (localhost [127.0.0.1]) by people.fsn.hu (Postfix) with ESMTP id C45B584458 for ; Sun, 22 Jan 2006 16:51:54 +0100 (CET) Received: from people.fsn.hu ([127.0.0.1]) by localhost (people.fsn.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 84489-05-11 for ; Sun, 22 Jan 2006 16:51:49 +0100 (CET) Received: from [172.16.164.71] (fw.axelero.hu [195.228.243.120]) by people.fsn.hu (Postfix) with ESMTP id 906A484452 for ; Sun, 22 Jan 2006 16:51:49 +0100 (CET) Message-ID: <43D3AA14.9090800@fsn.hu> Date: Sun, 22 Jan 2006 16:51:48 +0100 From: Attila Nagy User-Agent: Thunderbird 1.5 (Windows/20051201) 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: amavisd-new at fsn.hu Subject: SCSI target mode LOR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 15:52:02 -0000 Hello, I'm doing some experiments with FreeBSD target mode support on Fibre Channel and thought that I should give CURRENT a try too. The machine itself is an HP BL25p with 8 GB of RAM (but hw.physmem set to under 4G, it seems the isp driver needs this) and dual Opterons. Running amd64 code. This is what I get after issuing scsi_target -A -S -T -W 32 2:0:0 /data/file1 lock order reversal: (sleepable after non-sleepable) 1st 0xffffffff808ce680 targ global (targ global) @ /usr/src/sys/cam/scsi/scsi_target.c:418 2nd 0xffffffff808e98c0 kernel environment (kernel environment) @ /usr/src/sys/kern/subr_hints.c:117 KDB: stack backtrace: witness_checkorder() at witness_checkorder+0x4f9 _sx_slock() at _sx_slock+0x4d res_find() at res_find+0x41a resource_find() at resource_find+0x7e resource_find_dev() at resource_find_dev+0x5f cam_periph_alloc() at cam_periph_alloc+0x1df targioctl() at targioctl+0x3a7 giant_ioctl() at giant_ioctl+0x65 devfs_ioctl_f() at devfs_ioctl_f+0x6f ioctl() at ioctl+0x147 syscall() at syscall+0x517 Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800909aac, rsp = 0x7fffffffbb98, rbp = 0x7fffffffe700 --- Thanks, -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone: +3630 306 6758 http://www.fsn.hu/ From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 16:59:23 2006 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 19CD916A41F for ; Sun, 22 Jan 2006 16:59:23 +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 8ADA343D48 for ; Sun, 22 Jan 2006 16:59:21 +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 k0MGpIbE004460; Sun, 22 Jan 2006 09:51:18 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43D3B806.4020006@samsco.org> Date: Sun, 22 Jan 2006 09:51:18 -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: Attila Nagy References: <43D3AA14.9090800@fsn.hu> In-Reply-To: <43D3AA14.9090800@fsn.hu> 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: SCSI target mode LOR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 16:59:23 -0000 Attila Nagy wrote: > Hello, > > I'm doing some experiments with FreeBSD target mode support on Fibre > Channel and thought that I should give CURRENT a try too. > > The machine itself is an HP BL25p with 8 GB of RAM (but hw.physmem set > to under 4G, it seems the isp driver needs this) and dual Opterons. > Running amd64 code. > > This is what I get after issuing > scsi_target -A -S -T -W 32 2:0:0 /data/file1 > > lock order reversal: (sleepable after non-sleepable) > 1st 0xffffffff808ce680 targ global (targ global) @ > /usr/src/sys/cam/scsi/scsi_target.c:418 > 2nd 0xffffffff808e98c0 kernel environment (kernel environment) @ > /usr/src/sys/kern/subr_hints.c:117 > KDB: stack backtrace: > witness_checkorder() at witness_checkorder+0x4f9 > _sx_slock() at _sx_slock+0x4d > res_find() at res_find+0x41a > resource_find() at resource_find+0x7e > resource_find_dev() at resource_find_dev+0x5f > cam_periph_alloc() at cam_periph_alloc+0x1df > targioctl() at targioctl+0x3a7 > giant_ioctl() at giant_ioctl+0x65 > devfs_ioctl_f() at devfs_ioctl_f+0x6f > ioctl() at ioctl+0x147 > syscall() at syscall+0x517 > Xfast_syscall() at Xfast_syscall+0xa8 > --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800909aac, rsp = > 0x7fffffffbb98, rbp = 0x7fffffffe700 --- > > Thanks, > Hi, Please file a PR on this and assign it to me. I'll be working in this area soon. Scott From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 17:03:52 2006 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 A905816A41F for ; Sun, 22 Jan 2006 17:03:52 +0000 (GMT) (envelope-from pawel.worach@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22DA143D60 for ; Sun, 22 Jan 2006 17:03:45 +0000 (GMT) (envelope-from pawel.worach@gmail.com) Received: by uproxy.gmail.com with SMTP id j3so430764ugf for ; Sun, 22 Jan 2006 09:03:44 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=KON0Uppn3Dpx+wSG6A3ad5L//kdmAlhpoO3pEksXdw3Rzrw/ewWyUEK/CV0DodAlVDwQyiR0FS3iaUf0/bMWZDde1loCm76LcG9dR4y8K3c+EFFPsgYQLPbKohhTFwrOJX+isemOt2ncCBu2HwM8AttXB28Yzv4zDn/ebZ4w6pw= Received: by 10.67.23.13 with SMTP id a13mr1904200ugj; Sun, 22 Jan 2006 09:03:44 -0800 (PST) Received: from ?192.168.0.107? ( [80.217.193.226]) by mx.gmail.com with ESMTP id q40sm367747ugc.2006.01.22.09.03.43; Sun, 22 Jan 2006 09:03:44 -0800 (PST) Message-ID: <43D3BAE9.6080501@gmail.com> Date: Sun, 22 Jan 2006 18:03:37 +0100 From: Pawel Worach User-Agent: Thunderbird 1.5 (X11/20060107) MIME-Version: 1.0 To: Stefan Ehmann References: <1137681189.672.4.camel@localhost> <20060120105424.m384aenq0ck4g088@netchild.homeip.net> <1137942552.893.4.camel@localhost> In-Reply-To: <1137942552.893.4.camel@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Leidinger , current@freebsd.org Subject: Re: panic: kmem_malloc(171642880): kmem_map too small: 31387648 total allocated X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 17:03:52 -0000 Stefan Ehmann wrote: > I had similar problems. removing atatpicam fixed this. > > Also I could run a buildworld without a panic. Might be only by chance > though (don't know how easily the panic was reproducible). > I have a similar panic here, seems like ATAPICAM finds a bogus CD in the drive and then GEOM_ELI tries to taste it. cd0 at ata1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: \M-@:\M-W\M-D\^P panic: kmem_malloc(536870912): kmem_map too small: 14929920 total allocated KDB: stack backtrace: kdb_backtrace(c071ee05,c0774e20,c072fcb3,e35a85ac,100) at kdb_backtrace+0x2e panic(c072fcb3,20000000,e3d000,e35a85dc,c070cfed) at panic+0xb7 kmem_malloc(c104c0a8,20000000,2,e35a862c,c068e532) at kmem_malloc+0xab page_alloc(0,20000000,e35a861f,2,c56d47bc) at page_alloc+0x27 uma_large_malloc(20000000,2,e35a8650,c04ead43,20000000) at uma_large_malloc+0x52malloc(20000000,c0746c80,2,0,c56ef9c0) at malloc+0x9e g_read_data(c56ef9c0,0,200000,20000000,0) at g_read_data+0x50 g_eli_read_metadata(c0746980,c56e0600,e35a8a7c,c0719b38,c56e0658) at g_eli_read_metadata+0xe1 g_eli_taste(c0746980,c56e0600,0,c56e0700,4) at g_eli_taste+0xdc g_new_provider_event(c56e0600,0,0,c072c28d,0) at g_new_provider_event+0x7a one_event(66666667,c4aa1bd0,0,e35a8d00,c04eb955) at one_event+0x219 g_run_events(c0772c90,0,4c,c072c28d,64) at g_run_events+0x15 g_event_procbody(0,e35a8d38,0,0,0) at g_event_procbody+0x85 fork_exit(c04eb8d0,0,e35a8d38) at fork_exit+0x7f fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe35a8d6c, ebp = 0 --- Uptime: 16m5s Dumping 1023 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 1023MB (261728 pages) 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 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:166 166 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:166 #1 0xc0534438 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399 #2 0xc05347ad in panic ( fmt=0xc072fcb3 "kmem_malloc(%ld): kmem_map too small: %ld total allocated") at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xc069660b in kmem_malloc (map=0xc104c0a8, size=536870912, flags=2) at /usr/src/sys/vm/vm_kern.c:299 #4 0xc068b867 in page_alloc (zone=0x0, bytes=0, pflag=0x0, wait=0) at /usr/src/sys/vm/uma_core.c:956 #5 0xc068e532 in uma_large_malloc (size=536870912, wait=2) at /usr/src/sys/vm/uma_core.c:2698 #6 0xc0525a4e in malloc (size=536870912, mtp=0xc0746c80, flags=2) at /usr/src/sys/kern/kern_malloc.c:322 #7 0xc04eb610 in g_read_data (cp=0x0, offset=Unhandled dwarf expression opcode 0x93 ) at geom.h:290 #8 0xc04e2e81 in g_eli_read_metadata (mp=0x0, pp=0xc56e0600, md=0xe35a8a7c) at /usr/src/sys/geom/eli/g_eli.c:575 #9 0xc04e407c in g_eli_taste (mp=0xc0746980, pp=0xc56e0600, flags=0) at /usr/src/sys/geom/eli/g_eli.c:917 #10 0xc04ed56a in g_new_provider_event (arg=0xc56e0600, flag=0) at /usr/src/sys/geom/geom_subr.c:459 #11 0xc04ea5a9 in one_event () at /usr/src/sys/geom/geom_event.c:206 #12 0xc04ea6c5 in g_run_events () at /usr/src/sys/geom/geom_event.c:226 #13 0xc04eb955 in g_event_procbody () at /usr/src/sys/geom/geom_kern.c:141 #14 0xc051528f in fork_exit (callout=0xc04eb8d0 , arg=0x0, ---Type to continue, or q to quit--- frame=0x0) at /usr/src/sys/kern/kern_fork.c:790 #15 0xc06d5a8c in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:198 (kgdb) frame 10 #10 0xc04ed56a in g_new_provider_event (arg=0xc56e0600, flag=0) at /usr/src/sys/geom/geom_subr.c:459 459 mp->taste(mp, pp, 0); (kgdb) print *mp $1 = {name = 0xc0719b38 "ELI", version = 537137671, taste = 0xc04e3fa0 , config = 0, ctlreq = 0xc04e6c10 , init = 0, fini = 0, destroy_geom = 0xc04e3f80 , start = 0, spoiled = 0, dumpconf = 0, access = 0, orphan = 0, ioctl = 0, class = { le_next = 0xc07432c0, le_prev = 0xc0747058}, geom = { lh_first = 0xc56e0580}} (kgdb) print *pp $2 = {name = 0xc56e0658 "cd0", provider = {le_next = 0x0, le_prev = 0xc56e0694}, geom = 0xc56e0680, consumers = { lh_first = 0xc56ef9c0}, acr = 1, acw = 0, ace = 0, error = 0, orphan = { tqe_next = 0x0, tqe_prev = 0x0}, mediasize = 9007199791611904, sectorsize = 536870912, stripesize = 0, stripeoffset = 0, stat = 0xc4d88960, nstart = 0, nend = 0, flags = 0, private = 0x0, index = 0} full dmesg: GEOM_ELI[1]: Start tasting. Copyright (c) 1992-2006 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 #0: Sun Jan 22 15:36:23 CET 2006 root@ibm-se82151:/usr/obj/usr/src/sys/IBMT41 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) M processor 1700MHz (1698.56-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x695 Stepping = 5 Features=0xa7e9f9bf Features2=0x180 real memory = 1073086464 (1023 MB) avail memory = 1041051648 (992 MB) ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413) ACPI: Overriding _OS definition with "Windows 2001" npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi_ec0: port 0x62,0x66 on acpi0 acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 est0: on cpu0 p4tcc0: on cpu0 acpi_lid0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: on hostb0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0x3000-0x30ff mem 0xe0000000-0xe7ffffff,0xc0100000-0xc010ffff irq 11 at device 0.0 on pci1 drm0: on vgapci0 info: [drm] AGP at 0xd0000000 256MB info: [drm] Initialized radeon 1.19.0 20050911 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 ehci0: mem 0xc0000000-0xc00003ff 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 pcib2: at device 30.0 on pci0 pci2: on pcib2 pci2: at device 0.0 (no driver attached) pci2: at device 0.1 (no driver attached) em0: port 0x8000-0x803f mem 0xc0240000-0xc025ffff,0xc0200000-0xc020ffff irq 11 at device 1.0 on pci2 em0: Ethernet address: 00:11:25:d4:9c:ec em0: [FAST] ath0: mem 0xc0210000-0xc021ffff irq 11 at device 2.0 on pci2 ath0: Ethernet address: 00:05:4e:4b:76:13 ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1860-0x186f 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 0xc0000c00-0xc0000dff,0xc0000800-0xc00008ff irq 11 at device 31.5 on pci0 pcm0: pci0: at device 31.6 (no driver attached) 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 sio1: port 0x2f8-0x2ff irq 3 drq 3 on acpi0 sio1: type 16550A battery0: on acpi0 acpi_acad0: on acpi0 acpi_ibm0: on acpi0 vpd0: Unable to allocate memory resource. pmtimer0 on isa0 orm0: at iomem 0xd0000-0xd0fff,0xd1000-0xd1fff,0xdc000-0xdffff 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 1698563791 Hz quality 800 Timecounters tick every 1.000 msec Fast IPsec: Initialized Security Association Processing. battery0: battery initialization start acpi_acad0: acline initialization start battery0: battery initialization done, tried 1 times acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times ad0: 57231MB at ata0-master UDMA100 acd0: CDRW at ata1-master UDMA33 GEOM_LABEL: Label for provider ad0s2a is ufs/root. Enter passphrase for ad0s2d: GEOM_ELI[1]: Using Master Key 0 for ad0s2d. GEOM_ELI[1]: Creating device ad0s2d.eli. GEOM_ELI[0]: Device ad0s2d.eli created. GEOM_ELI[0]: Cipher: AES GEOM_ELI[0]: Key length: 256 GEOM_ELI[0]: Crypto: software GEOM_ELI[1]: Thread g_eli[0] ad0s2d started. GEOM_LABEL: Label for provider ad0s2d.eli is ufs/usr. Trying to mount root from ufs:/dev/ufs/root GEOM_LABEL: Label for provider ad0s2d.eli is ufs/usr. ath0: [00:05:5d:eb:62:94] recv auth frame with algorithm 0 seq 2 ath0: [00:05:5d:eb:62:94] assoc success: long preamble, long slot time info: [drm] Loading R200 Microcode cd0 at ata1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: \M-@:\M-W\M-D\^P acpi_acad0: Off Line -- Pawel From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 17:11:44 2006 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 533E616A41F for ; Sun, 22 Jan 2006 17:11:44 +0000 (GMT) (envelope-from joe@tao.org.uk) Received: from mailhost.tao.org.uk (transwarp.tao.org.uk [87.74.4.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2B4643D45 for ; Sun, 22 Jan 2006 17:11:43 +0000 (GMT) (envelope-from joe@tao.org.uk) Received: from genius.tao.org.uk (genius.tao.org.uk [87.74.4.41]) by mailhost.tao.org.uk (Postfix) with ESMTP id A44805CAC; Sun, 22 Jan 2006 17:11:41 +0000 (GMT) Received: by genius.tao.org.uk (Postfix, from userid 100) id 2455240DC; Sun, 22 Jan 2006 17:11:40 +0000 (GMT) Date: Sun, 22 Jan 2006 17:11:40 +0000 From: Josef Karthauser To: Nicolas Blais Message-ID: <20060122171140.GB3532@genius.tao.org.uk> Mail-Followup-To: Josef Karthauser , Nicolas Blais , freebsd-current@freebsd.org References: <200601211159.50768.nb_root@videotron.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="98e8jtXdkpgskNou" Content-Disposition: inline In-Reply-To: <200601211159.50768.nb_root@videotron.ca> User-Agent: Mutt/1.5.11 Cc: freebsd-current@freebsd.org Subject: Re: -CURRENT freeze at boot after update X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jan 2006 17:11:44 -0000 --98e8jtXdkpgskNou Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 21, 2006 at 11:59:45AM -0500, Nicolas Blais wrote: >=20 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=3D0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/11.10, addr 2, iclass 3/1 > ums0: 3 buttons and Z dir. > Timecounter "TSC" frequency 2493036546 Hz quality 800 > Timecounters tick every 1.000 msec > ad0: 78167MB at ata0-master UDMA133 > acd0: DVDR at ata1-master UDMA33 > ad4: 76319MB at ata2-master SATA150 > >=20 > Booting my kernel.old works fine (fortunatly!). I'm now looking at recen= t=20 > changes that could be the cause between Jan 7 and now. >=20 I have a similar problem, the machine did freeze, but eventually would continue and start normally. I eventually tied it down to the floppy disk driver (the floppy light was on for the duration of the hang). I removed the floppy driver from the kernel and it works ok now. Joe --98e8jtXdkpgskNou Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iEYEARECAAYFAkPTvMsACgkQXVIcjOaxUBaXFwCglSIz3INH9Op09kfalIr8GfTJ oMkAn0LKjjuilFCeOuSLBNB56e1WqkjL =amc6 -----END PGP SIGNATURE----- --98e8jtXdkpgskNou-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 17:34:22 2006 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 415BB16A41F for ; Sun, 22 Jan 2006 17:34:22 +0000 (GMT) (envelope-from dunstan@zsno.ids.czest.pl) Received: from zsno.ids.czest.pl (zsno.ids.czest.pl [212.87.237.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7624343D5A for ; Sun, 22 Jan 2006 17:34:21 +0000 (GMT) (envelope-from dunstan@zsno.ids.czest.pl) Received: from zsno.ids.czest.pl (localhost [127.0.0.1]) by zsno.ids.czest.pl (8.13.4/8.13.3) with ESMTP id k0MJEAAQ084614 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 22 Jan 2006 20:14:10 +0100 (CET) (envelope-from dunstan@zsno.ids.czest.pl) Received: (from dunstan@localhost) by zsno.ids.czest.pl (8.13.4/8.13.3/Submit) id k0MJE9BK084613; Sun, 22 Jan 2006 20:14:09 +0100 (CET) (envelope-from dunstan) Date: Sun, 22 Jan 2006 20:14:09 +0100 From: "Wojciech A. Koszek" To: Maxim.Sobolev@portaone.com Message-ID: <20060122191409.GB84400@zsno.ids.czest.pl> References: <20060114223019.GA99634@FreeBSD.czest.pl> <43CC168D.9080708@portaone.com> <20060118082804.GC4846@FreeBSD.czest.pl> <43CF22AD.3080702@portaone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <43CF22AD.3080702@portaone.com> User-Agent: Mutt/1.4.2.1i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (zsno.ids.czest.pl [127.0.0.1]); Sun, 22 Jan 2006 20:14:10 +0100 (CET) X-Spam-Status: No, score=-2.8 required=4.0 tests=ALL_TRUSTED autolearn=ham version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on zsno.ids.czest.pl X-Virus-Scanned: ClamAV version 0.87, clamav-milter version 0.87 on zsno.ids.czest.pl X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Support for large number of md(4) disks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 17:34:22 -0000 On Wed, Jan 18, 2006 at 09:25:01PM -0800, Maxim Sobolev wrote: > Wojciech A. Koszek wrote: > >On Mon, Jan 16, 2006 at 01:56:29PM -0800, Maxim Sobolev wrote: > >>Hi, > > > >Hi Maxim, > > > >>IMHO there is better approach to fetch unknown amount of data from the > >>kernel using ioctl(2) facility. The main idea is that you allocate some > >>buffer of size sufficient in 95% of cases (for md(4) I think 8-16 > >>entries are enough), attach it to some structure which has size of the > >>buffer as one of its members and send pointer to that structure as an > >>argument to ioctl(2). [..] > Yes, there is a difference. I don't like your approach when you are > trying to win the race fixed amount of times (5) and then just bailing > out, asymptotic approach is better IMHO. Especially considering that > memory is cheap nowadays and you won't have any problems with allocating > space for many thousand configuration entries, even in the case when you > are really going to use only few of them. > > Regarding you assumption that meeting the situation when total number of > devices changes quickly I don't quite agree. A simple script can make > number of md(4) devices going up/down by few hundred per second easily, > your approach will behave erratically in such case. > I got some feedback from people who use md(4) in such cases. Looking at bugs@ gives me a feel there is also a real need for mdconfig -l working properly.. ...this is why updated patch is here: http://zsno.ids.czest.pl/~dunstan/FreeBSD/mdconfig-list.3.patch It starts with 16 entries in the user-space. Thanks! -- * Wojciech Koszek && From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 17:54:43 2006 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 089D016A41F for ; Sun, 22 Jan 2006 17:54:43 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A9B443D49 for ; Sun, 22 Jan 2006 17:54:42 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from localhost (localhost [127.0.0.1]) by people.fsn.hu (Postfix) with ESMTP id 8149F8444E; Sun, 22 Jan 2006 18:54:40 +0100 (CET) Received: from people.fsn.hu ([127.0.0.1]) by localhost (people.fsn.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 06351-03-2; Sun, 22 Jan 2006 18:54:35 +0100 (CET) Received: from [172.16.164.71] (fw.axelero.hu [195.228.243.120]) by people.fsn.hu (Postfix) with ESMTP id 8F31C84458; Sun, 22 Jan 2006 18:54:35 +0100 (CET) Message-ID: <43D3C6DD.4090702@fsn.hu> Date: Sun, 22 Jan 2006 18:54:37 +0100 From: Attila Nagy User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Scott Long References: <43D3AA14.9090800@fsn.hu> <43D3B806.4020006@samsco.org> In-Reply-To: <43D3B806.4020006@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at fsn.hu Cc: freebsd-current@freebsd.org Subject: Re: SCSI target mode LOR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 17:54:43 -0000 Hello, Scott Long wrote: >> lock order reversal: (sleepable after non-sleepable) > Please file a PR on this and assign it to me. I'll be working in this > area soon. kern/92164 Thank you. BTW, will you work on CAM, target mode support, or 4G/MP safety of any of the two? -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone: +3630 306 6758 http://www.fsn.hu/ From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 19:12:26 2006 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 ED34F16A41F for ; Sun, 22 Jan 2006 19:12:26 +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 4D46843D45 for ; Sun, 22 Jan 2006 19:12:25 +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 k0MJCN7S005088; Sun, 22 Jan 2006 12:12:24 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43D3D917.30200@samsco.org> Date: Sun, 22 Jan 2006 12:12:23 -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: Attila Nagy References: <43D3AA14.9090800@fsn.hu> <43D3B806.4020006@samsco.org> <43D3C6DD.4090702@fsn.hu> In-Reply-To: <43D3C6DD.4090702@fsn.hu> 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: SCSI target mode LOR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 19:12:27 -0000 Attila Nagy wrote: > Hello, > > Scott Long wrote: > >>> lock order reversal: (sleepable after non-sleepable) >> >> Please file a PR on this and assign it to me. I'll be working in this >> area soon. > > kern/92164 > > Thank you. > > BTW, will you work on CAM, target mode support, or 4G/MP safety of any > of the two? > CAM: yes target mode: yes 4G/SMP: yes From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 19:28:16 2006 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 40EDB16A41F for ; Sun, 22 Jan 2006 19:28:16 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4D8643D48 for ; Sun, 22 Jan 2006 19:28:15 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from localhost (localhost [127.0.0.1]) by people.fsn.hu (Postfix) with ESMTP id A37508444C; Sun, 22 Jan 2006 20:28:13 +0100 (CET) Received: from people.fsn.hu ([127.0.0.1]) by localhost (people.fsn.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 19985-02-2; Sun, 22 Jan 2006 20:28:07 +0100 (CET) Received: from [172.16.164.71] (fw.axelero.hu [195.228.243.120]) by people.fsn.hu (Postfix) with ESMTP id B546B84420; Sun, 22 Jan 2006 20:28:07 +0100 (CET) Message-ID: <43D3DCCA.50100@fsn.hu> Date: Sun, 22 Jan 2006 20:28:10 +0100 From: Attila Nagy User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Scott Long References: <43D3AA14.9090800@fsn.hu> <43D3B806.4020006@samsco.org> <43D3C6DD.4090702@fsn.hu> <43D3D917.30200@samsco.org> In-Reply-To: <43D3D917.30200@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at fsn.hu Cc: freebsd-current@freebsd.org Subject: Re: SCSI target mode LOR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 19:28:16 -0000 Scott Long wrote: >> BTW, will you work on CAM, target mode support, or 4G/MP safety of any >> of the two? > CAM: yes > target mode: yes > 4G/SMP: yes Hmm. Is it christmas, or something? :) This is absolutely great news! Do you have any deeper details? BTW, this is what I got on 6-STABLE with two HP BL25p connected to each other with a single FC loop: target: CPU states: 3.0% user, 0.0% nice, 59.9% system, 15.4% interrupt, 21.7% idle initiator: dT: 0.502 flag_I 500000us sizeof 288 i -1 L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name 2 261 147 18869 6.7 114 14534 8.6 99.5| da1 2 265 149 19124 6.7 116 14789 8.6 100.9| da2 2 275 157 20144 6.3 118 15044 8.3 100.0| da3 2 273 155 19889 6.3 118 15044 8.4 100.0| da4 2 267 153 19634 6.4 114 14534 8.6 100.0| da5 2 277 157 20144 6.3 120 15299 8.3 100.7| da6 2 263 151 19379 6.6 112 14279 8.7 99.9| da7 2 267 153 19634 6.5 114 14534 8.7 100.2| da8 The machines have two Opteron 252, 8G of RAM (running with 4G because of isp (I guess)) and a Qlogic 2312 dual port 2G FC adapter (only one port utilized). On the target I did 8 malloc backed RAM disks and shared them with scsi_target. On the initiator, I do this (just blindly testing for now): dd if=/dev/zero of=/dev/daX bs=1024k dd if=/dev/daX of=/dev/zero bs=1024k simultaneously for the 8 LUNs. -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone: +3630 306 6758 http://www.fsn.hu/ From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 19:42:35 2006 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 31EE916A422 for ; Sun, 22 Jan 2006 19:42:35 +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 B228443D6A for ; Sun, 22 Jan 2006 19:42:28 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (n82fs442qy1ad7nf@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id k0MJfTpM041080 for ; Sun, 22 Jan 2006 11:41:29 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id k0MJfTla041079 for current@FreeBSD.org; Sun, 22 Jan 2006 11:41:29 -0800 (PST) (envelope-from jmg) Date: Sun, 22 Jan 2006 11:41:29 -0800 From: John-Mark Gurney To: current@FreeBSD.org Message-ID: <20060122194129.GZ69162@funkthat.com> Mail-Followup-To: current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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: Subject: memory corruption in recent -current? 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, 22 Jan 2006 19:42:35 -0000 I've been working on a BT878 audio driver (first crack is available in p4), and with a recent -current (you can sync to my -current as it's the one in my workspace, jmg_carbon), I get memory corruption: Memory modified after free 0xc2fb1050(12) val=1c @ 0xc2fb1050 panic: Most recently used by ioctlops or: Memory modified after free 0xc2ba2b90(12) val=1c @ 0xc2ba2b90 panic: Most recently used by Unitno I went back to a kerenl that is pre-Dec 21st, and I haven't had a single panic yet. I will admit I haven't done a builtworld between the these two (the last buildworld matched with the pre-Dec 21st kernel)... I am using kld modules for my testing, so I was building modules against an old world, but I don't know of anything that has changed that would cause problems.. Anyone else seeing this? -- 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 Jan 22 20:08:38 2006 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 D2E4016A434 for ; Sun, 22 Jan 2006 20:08:38 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1250F43D45 for ; Sun, 22 Jan 2006 20:08:36 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: by xproxy.gmail.com with SMTP id t12so574473wxc for ; Sun, 22 Jan 2006 12:08:36 -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=rTT/K15BotLHOTmvIhKwZIQsSSVQzvH0/H/c9JL47C12mhiMJe5UJCTo/QCRqwOC4jX/tV29ZXXdDIo70TPkTbz4/CYs4E16up4M0Vgq0WA8v/ZTj7fTxflrPif4yWK+FEayNXjPW+vj638podzgynL8f07CgoVItrfFLmsTELA= Received: by 10.70.132.1 with SMTP id f1mr782122wxd; Sun, 22 Jan 2006 12:08:36 -0800 (PST) Received: by 10.70.36.7 with HTTP; Sun, 22 Jan 2006 12:08:36 -0800 (PST) Message-ID: <70e8236f0601221208u2cd66a39u19ed6d573f76a53c@mail.gmail.com> Date: Sun, 22 Jan 2006 20:08:36 +0000 From: Joao Barros To: Attila Nagy In-Reply-To: <43D3DCCA.50100@fsn.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <43D3AA14.9090800@fsn.hu> <43D3B806.4020006@samsco.org> <43D3C6DD.4090702@fsn.hu> <43D3D917.30200@samsco.org> <43D3DCCA.50100@fsn.hu> Cc: freebsd-current@freebsd.org Subject: Re: SCSI target mode LOR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 20:08:39 -0000 On 1/22/06, Attila Nagy wrote: > Scott Long wrote: > >> BTW, will you work on CAM, target mode support, or 4G/MP safety of any > >> of the two? > > CAM: yes > > target mode: yes > > 4G/SMP: yes > Hmm. Is it christmas, or something? :) Put Multipath into that and it will definitely be ;) -- Joao Barros From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 20:12:34 2006 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 9737516A41F for ; Sun, 22 Jan 2006 20:12:34 +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 5BB9643D46 for ; Sun, 22 Jan 2006 20:12:34 +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 33FDC1A3C1C for ; Sun, 22 Jan 2006 12:12:34 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5B43F512CE; Sun, 22 Jan 2006 15:12:33 -0500 (EST) Date: Sun, 22 Jan 2006 15:12:33 -0500 From: Kris Kennaway To: current@FreeBSD.org Message-ID: <20060122201233.GA59053@xor.obsecurity.org> References: <20060122194129.GZ69162@funkthat.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mP3DRpeJDSE+ciuQ" Content-Disposition: inline In-Reply-To: <20060122194129.GZ69162@funkthat.com> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: memory corruption in recent -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: Sun, 22 Jan 2006 20:12:34 -0000 --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 22, 2006 at 11:41:29AM -0800, John-Mark Gurney wrote: > I've been working on a BT878 audio driver (first crack is available > in p4), and with a recent -current (you can sync to my -current as > it's the one in my workspace, jmg_carbon), I get memory corruption: > Memory modified after free 0xc2fb1050(12) val=3D1c @ 0xc2fb1050 > panic: Most recently used by ioctlops > or: > Memory modified after free 0xc2ba2b90(12) val=3D1c @ 0xc2ba2b90 > panic: Most recently used by Unitno >=20 > I went back to a kerenl that is pre-Dec 21st, and I haven't had a single > panic yet. I will admit I haven't done a builtworld between the these > two (the last buildworld matched with the pre-Dec 21st kernel)... I am > using kld modules for my testing, so I was building modules against an > old world, but I don't know of anything that has changed that would > cause problems.. >=20 > Anyone else seeing this? Use memguard to track down the cause. Kris --mP3DRpeJDSE+ciuQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD0+cwWry0BWjoQKURArF1AKDw0PDjCugWDWu+g/NdB0QratpWGgCdHi/L r/WiJfqnoCNlpgvHOAcv34o= =NVRM -----END PGP SIGNATURE----- --mP3DRpeJDSE+ciuQ-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 20:13:04 2006 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 E94AD16A41F for ; Sun, 22 Jan 2006 20:13:04 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7324D43D48 for ; Sun, 22 Jan 2006 20:13:04 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from localhost (localhost [127.0.0.1]) by people.fsn.hu (Postfix) with ESMTP id 5C1A18444E for ; Sun, 22 Jan 2006 21:13:03 +0100 (CET) Received: from people.fsn.hu ([127.0.0.1]) by localhost (people.fsn.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 23971-02-7 for ; Sun, 22 Jan 2006 21:12:58 +0100 (CET) Received: from [172.16.164.71] (fw.axelero.hu [195.228.243.120]) by people.fsn.hu (Postfix) with ESMTP id 7A1E084452 for ; Sun, 22 Jan 2006 21:12:58 +0100 (CET) Message-ID: <43D3E74C.3000808@fsn.hu> Date: Sun, 22 Jan 2006 21:13:00 +0100 From: Attila Nagy User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <43D3AA14.9090800@fsn.hu> <43D3B806.4020006@samsco.org> <43D3C6DD.4090702@fsn.hu> <43D3D917.30200@samsco.org> <43D3DCCA.50100@fsn.hu> <70e8236f0601221208u2cd66a39u19ed6d573f76a53c@mail.gmail.com> In-Reply-To: <70e8236f0601221208u2cd66a39u19ed6d573f76a53c@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at fsn.hu Subject: Re: SCSI target mode LOR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 20:13:05 -0000 Joao Barros wrote: > On 1/22/06, Attila Nagy wrote: >> Scott Long wrote: >>>> BTW, will you work on CAM, target mode support, or 4G/MP safety of any >>>> of the two? >>> CAM: yes >>> target mode: yes >>> 4G/SMP: yes >> Hmm. Is it christmas, or something? :) > Put Multipath into that and it will definitely be ;) And ZFS (or ZFS like FS) with clustering capabilities. :) BTW, did you try geom_fox? -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone: +3630 306 6758 http://www.fsn.hu/ From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 20:21:39 2006 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 381EB16A420 for ; Sun, 22 Jan 2006 20:21:39 +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 8433C43D46 for ; Sun, 22 Jan 2006 20:21:37 +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 k0MKLYFc005523; Sun, 22 Jan 2006 13:21:34 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43D3E94D.6090503@samsco.org> Date: Sun, 22 Jan 2006 13:21:33 -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: Joao Barros References: <43D3AA14.9090800@fsn.hu> <43D3B806.4020006@samsco.org> <43D3C6DD.4090702@fsn.hu> <43D3D917.30200@samsco.org> <43D3DCCA.50100@fsn.hu> <70e8236f0601221208u2cd66a39u19ed6d573f76a53c@mail.gmail.com> In-Reply-To: <70e8236f0601221208u2cd66a39u19ed6d573f76a53c@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: Attila Nagy , freebsd-current@freebsd.org Subject: Re: SCSI target mode LOR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 20:21:39 -0000 Joao Barros wrote: > On 1/22/06, Attila Nagy wrote: > >>Scott Long wrote: >> >>>>BTW, will you work on CAM, target mode support, or 4G/MP safety of any >>>>of the two? >>> >>>CAM: yes >>>target mode: yes >>>4G/SMP: yes >> >>Hmm. Is it christmas, or something? :) > > > Put Multipath into that and it will definitely be ;) > > -- > Joao Barros That will hopefully come with SAS, which is also being worked on. Scott From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 21:43:20 2006 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 8124116A41F for ; Sun, 22 Jan 2006 21:43:20 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB1A743D7B for ; Sun, 22 Jan 2006 21:43:12 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: by xproxy.gmail.com with SMTP id t12so581322wxc for ; Sun, 22 Jan 2006 13:43:11 -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=ha82IZ/JuvjTJdNyfx0Ac8yHXENsUFmf79oWtW2DEuq/y1TFoMN4zCd3PFiIre83D+1jX1WIl2/hSksqb9J3yNkqgsLNoMRH41icqMONeBS5DWXwLh8UElr4KF/B7fYoObR/F9iLqH7YKo/vqufkONyrwmzpUOkDodEM56ElzBU= Received: by 10.70.11.14 with SMTP id 14mr5253201wxk; Sun, 22 Jan 2006 13:43:11 -0800 (PST) Received: by 10.70.36.7 with HTTP; Sun, 22 Jan 2006 13:43:11 -0800 (PST) Message-ID: <70e8236f0601221343w7a44a997uaa3b8fa93971d4a8@mail.gmail.com> Date: Sun, 22 Jan 2006 21:43:11 +0000 From: Joao Barros To: Scott Long In-Reply-To: <43D3E94D.6090503@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <43D3AA14.9090800@fsn.hu> <43D3B806.4020006@samsco.org> <43D3C6DD.4090702@fsn.hu> <43D3D917.30200@samsco.org> <43D3DCCA.50100@fsn.hu> <70e8236f0601221208u2cd66a39u19ed6d573f76a53c@mail.gmail.com> <43D3E94D.6090503@samsco.org> Cc: Attila Nagy , freebsd-current@freebsd.org Subject: Re: SCSI target mode LOR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 21:43:20 -0000 On 1/22/06, Scott Long wrote: > Joao Barros wrote: > > > On 1/22/06, Attila Nagy wrote: > > > >>Scott Long wrote: > >> > >>>>BTW, will you work on CAM, target mode support, or 4G/MP safety of an= y > >>>>of the two? > >>> > >>>CAM: yes > >>>target mode: yes > >>>4G/SMP: yes > >> > >>Hmm. Is it christmas, or something? :) > > > > > > Put Multipath into that and it will definitely be ;) > > > > -- > > Joao Barros > > That will hopefully come with SAS, which is also being worked on. I saw the recent commit on mpt(4) ;) -- Joao Barros From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 21:45:49 2006 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 5116916A41F for ; Sun, 22 Jan 2006 21:45:49 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6842743D60 for ; Sun, 22 Jan 2006 21:45:48 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: by xproxy.gmail.com with SMTP id t12so581480wxc for ; Sun, 22 Jan 2006 13:45:47 -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=L3ejrvM7yUkqfH0pHOle+4STylkcoBOO9dkNkYB4JJYIIsYNHHGQapU5oOf1QPCqe6+0dBPdEFFzMUf39p6FH0B/V0S8xLdamXsY/KbTvXpUJTYC/khKh4xmU1tjQnyU/ndecwisWky6HXw1uy5AO2jhnwLHam9JswinEOYgWS8= Received: by 10.70.80.10 with SMTP id d10mr5303374wxb; Sun, 22 Jan 2006 13:45:47 -0800 (PST) Received: by 10.70.36.7 with HTTP; Sun, 22 Jan 2006 13:45:47 -0800 (PST) Message-ID: <70e8236f0601221345l4d1c4568x42c76288e7a9c40a@mail.gmail.com> Date: Sun, 22 Jan 2006 21:45:47 +0000 From: Joao Barros To: Attila Nagy In-Reply-To: <43D3E74C.3000808@fsn.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <43D3AA14.9090800@fsn.hu> <43D3B806.4020006@samsco.org> <43D3C6DD.4090702@fsn.hu> <43D3D917.30200@samsco.org> <43D3DCCA.50100@fsn.hu> <70e8236f0601221208u2cd66a39u19ed6d573f76a53c@mail.gmail.com> <43D3E74C.3000808@fsn.hu> Cc: freebsd-current@freebsd.org Subject: Re: SCSI target mode LOR X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 21:45:49 -0000 On 1/22/06, Attila Nagy wrote: > Joao Barros wrote: > > On 1/22/06, Attila Nagy wrote: > >> Scott Long wrote: > >>>> BTW, will you work on CAM, target mode support, or 4G/MP safety of a= ny > >>>> of the two? > >>> CAM: yes > >>> target mode: yes > >>> 4G/SMP: yes > >> Hmm. Is it christmas, or something? :) > > Put Multipath into that and it will definitely be ;) > And ZFS (or ZFS like FS) with clustering capabilities. :) > > BTW, did you try geom_fox? No, haven't had the opportunity yet. -- Joao Barros From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 21:59:20 2006 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 767A616A41F; Sun, 22 Jan 2006 21:59:20 +0000 (GMT) (envelope-from dunstan@zsno.ids.czest.pl) Received: from zsno.ids.czest.pl (zsno.ids.czest.pl [212.87.237.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id B54E943D49; Sun, 22 Jan 2006 21:59:18 +0000 (GMT) (envelope-from dunstan@zsno.ids.czest.pl) Received: from zsno.ids.czest.pl (localhost [127.0.0.1]) by zsno.ids.czest.pl (8.13.4/8.13.3) with ESMTP id k0MNd7Bt087892 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Jan 2006 00:39:07 +0100 (CET) (envelope-from dunstan@zsno.ids.czest.pl) Received: (from dunstan@localhost) by zsno.ids.czest.pl (8.13.4/8.13.3/Submit) id k0MNd6EL087891; Mon, 23 Jan 2006 00:39:06 +0100 (CET) (envelope-from dunstan) Date: Mon, 23 Jan 2006 00:39:06 +0100 From: "Wojciech A. Koszek" To: freebsd-current@freebsd.org Message-ID: <20060122233906.GA87779@zsno.ids.czest.pl> References: <20051221031526.31ABC290@mx2.synetsystems.com> <200512211111.44268.jhb@freebsd.org> <20051227173434.GA53513@FreeBSD.czest.pl> <20060101182227.GB17837@FreeBSD.czest.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <20060101182227.GB17837@FreeBSD.czest.pl> User-Agent: Mutt/1.4.2.1i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (zsno.ids.czest.pl [127.0.0.1]); Mon, 23 Jan 2006 00:39:07 +0100 (CET) X-Spam-Status: No, score=-2.8 required=4.0 tests=ALL_TRUSTED autolearn=ham version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on zsno.ids.czest.pl X-Virus-Scanned: ClamAV version 0.87, clamav-milter version 0.87 on zsno.ids.czest.pl X-Virus-Status: Clean Cc: Richard Todd , rwatson@freebsd.org Subject: Re: Bug in latest rev kern_acct.c: panic: Trying sleep, but thread marked as sleeping prohibited X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 21:59:20 -0000 On Sun, Jan 01, 2006 at 06:22:27PM +0000, Wojciech A. Koszek wrote: > On Sat, Dec 31, 2005 at 06:39:31PM -0600, Richard Todd wrote: > > "Wojciech A. Koszek" writes: > > > > > On Wed, Dec 21, 2005 at 11:11:43AM -0500, John Baldwin wrote: > > >> acctwatch() probably isn't a good thing to do from a callout since it wants to > > >> do VOPs and such. Probably the easiest fix is to stick acctwatch() in its > > >> own kthread. > > > > > > I think I didn't break current behaviour. Patch is here: > > > > > > http://freebsd.czest.pl/dunstan/FreeBSD/kern_acct.0.patch > > > > > > Richard, could you try to repeat your problem with my patch? > > > > Got a chance to try a new kernel today with your patch. I tried to reproduce > > the panic by repeatedly copying a bunch of stuff onto /usr and deleting it > > in one window, and in another repeatedly doing "make configure; make clean" > > in one rather large port. Lots of "Accounting suspended/resumed" messages > > in the logs and no panics. So it's looking good from here. > > Thanks for testing this. I couldn't crash my box either. I belive that > KASSERT() before suspend/resume handling will always be true, just like > ACCT_ENABLED state. In the final version of the patch I'll include some > cosmetic changes suggested by Robert Watson (thanks!). (Sorry for late response. I'm having terrible problems with DNS server for freebsd.czest.pl. I'll try to get them fixed this week). Updated patch for accouting is here: http://zsno.ids.czest.pl/~dunstan/FreeBSD/kern_acct.2.patch -- * Wojciech A. Koszek && From owner-freebsd-current@FreeBSD.ORG Sun Jan 22 23:53:28 2006 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 5516B16A420 for ; Sun, 22 Jan 2006 23:53:28 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C8C043D5C for ; Sun, 22 Jan 2006 23:53:27 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: by xproxy.gmail.com with SMTP id t12so592331wxc for ; Sun, 22 Jan 2006 15:53:26 -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:content-transfer-encoding:content-disposition; b=TlgqIfNQQMlOM5wyJl2sBFsX9jrz4Sl5QL074LJLX58xVDNULugbwllg7qI0alsm1hXctPQlVQyrrxCUGTzhp4xZ4iPCuKl/nDwYubw7z865rS2OYOqNtrhEsCWe7X+HijMDiT/U05gMOjl5Ly4P1mu1PeGlOO7yRSAGjfuRRa0= Received: by 10.70.26.13 with SMTP id 13mr4710262wxz; Sun, 22 Jan 2006 15:53:26 -0800 (PST) Received: by 10.70.36.7 with HTTP; Sun, 22 Jan 2006 15:53:26 -0800 (PST) Message-ID: <70e8236f0601221553r503bc43ds295d3a72ad879afb@mail.gmail.com> Date: Sun, 22 Jan 2006 23:53:26 +0000 From: Joao Barros To: Scott Long MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: freebsd-current@freebsd.org Subject: amr: duplicated "delete logical drives supported by controller" on attach X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Jan 2006 23:53:28 -0000 I recently updated and installed CURRENT and now on a "kldload amr" I get t= his: amr0: mem 0xf0000000-0xf3ffffff irq 10 at device 0.0 on pci3 amr0: delete logical drives supported by controller amr0: delete logical drives supported by controller amr0: Firmware 198U, BIOS 3.35, 64MB RAM amrd0: on amr0 amrd0: 104040MB (213073920 sectors) RAID 5 (optimal) I tracked it to amr.c on amr_query_controller() which is called by at least amr_startup() and amr_attach() src/sys/dev/amr/amr.c,v 1.73 2006/01/14 17:59:28 scottl -- Joao Barros From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 01:19:44 2006 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 6218116A41F; Mon, 23 Jan 2006 01:19:44 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22FB843D45; Mon, 23 Jan 2006 01:19:43 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [192.168.2.4]) ([10.251.60.12]) by a50.ironport.com with ESMTP; 22 Jan 2006 17:19:42 -0800 X-IronPort-Anti-Spam-Filtered: true Message-ID: <43D42F2E.6020501@elischer.org> Date: Sun, 22 Jan 2006 17:19:42 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Xu References: <43D1F384.7080406@elischer.org> <43D323C3.7050004@freebsd.org> In-Reply-To: <43D323C3.7050004@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: kernel threads as threads. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 01:19:44 -0000 David Xu wrote: > Julian Elischer wrote: > >> >> I have made a first set of changes to allow threads to be 'forked' >> within the kernel. >> >> I have run on the resulting kernel for some of today with no problems >> other than >> some statistics oddness in top which I plan on looking at next week. >> >> The current patch doen't remove the ability to make kernel processes, >> however it does >> add the ability to make threads under process 0 and alters nearly all >> the users of >> kernel threads to actually do this.. The exception is the aio >> threads, as they seem to require >> separate address spaces to work with and that requires separate proc >> structures. >> >> I was thinking that they could act as extra threads on the calling >> processes but that >> is more of a rewrite than I plan right now. >> >> Anyhow the diffs so far are at: >> >> http://www.freebsd.org/~julian/kthread.diff. >> >> more later. >> >> julian > > > in vfs_aio.c, we have to borrow user process's vmspace, creating all > kthread in > proc0 breaks this. yes you should find that the newest patches revert this change. (if they do not then I have not uploaded the newest patches..) I just looked.... The newest patches are at http://people.freebsd.org/~julian/kthread.diff They retain the ability to make a kernel process as well as a kernel thread, and they use the process ability to make the process for aio. I found this on friday ;-) However the abiolity to make a thread shoudl ebused in the following manner.. an aio request shouild spawn a separate KSEGRP on teh calling process and make a separate thread that is actually owned by the requesting process. The calling process doesn't know about the new thread. It makes AIO extensible to as many processes as you want and if ther ei more work you can even make multiple working threads in the ksegrp (maybe one per filesystem ) just an idea. It's gotta be better than grafting a thread onto processes VMs on the fly. > > David Xu > > _______________________________________________ > 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 Mon Jan 23 08:15:28 2006 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 8280216A41F for ; Mon, 23 Jan 2006 08:15:28 +0000 (GMT) (envelope-from dunstan@zsno.ids.czest.pl) Received: from zsno.ids.czest.pl (zsno.ids.czest.pl [212.87.237.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADFB343D48 for ; Mon, 23 Jan 2006 08:15:27 +0000 (GMT) (envelope-from dunstan@zsno.ids.czest.pl) Received: from zsno.ids.czest.pl (localhost [127.0.0.1]) by zsno.ids.czest.pl (8.13.4/8.13.3) with ESMTP id k0N9tEG3095192 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Jan 2006 10:55:14 +0100 (CET) (envelope-from dunstan@zsno.ids.czest.pl) Received: (from dunstan@localhost) by zsno.ids.czest.pl (8.13.4/8.13.3/Submit) id k0N9tDdD095191; Mon, 23 Jan 2006 10:55:13 +0100 (CET) (envelope-from dunstan) Date: Mon, 23 Jan 2006 10:55:13 +0100 From: "Wojciech A. Koszek" To: Pawel Worach Message-ID: <20060123095513.GA95040@zsno.ids.czest.pl> References: <1137681189.672.4.camel@localhost> <20060120105424.m384aenq0ck4g088@netchild.homeip.net> <1137942552.893.4.camel@localhost> <43D3BAE9.6080501@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <43D3BAE9.6080501@gmail.com> User-Agent: Mutt/1.4.2.1i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (zsno.ids.czest.pl [127.0.0.1]); Mon, 23 Jan 2006 10:55:14 +0100 (CET) X-Spam-Status: No, score=-2.8 required=4.0 tests=ALL_TRUSTED autolearn=ham version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on zsno.ids.czest.pl X-Virus-Scanned: ClamAV version 0.87, clamav-milter version 0.87 on zsno.ids.czest.pl X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: panic: kmem_malloc(171642880): kmem_map too small: 31387648 total allocated X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 08:15:28 -0000 On Sun, Jan 22, 2006 at 08:03:52AM +0000, Pawel Worach wrote: > Stefan Ehmann wrote: > > I had similar problems. removing atatpicam fixed this. > > > > Also I could run a buildworld without a panic. Might be only by chance > > though (don't know how easily the panic was reproducible). > > > > I have a similar panic here, seems like ATAPICAM finds a bogus CD in the > drive and then GEOM_ELI tries to taste it. > > cd0@ata1 bus 0 target 0 lun 0 > cd0: Removable CD-ROM SCSI-0 device > cd0: 33.000MB/s transfers > cd0: \M-@:\M-W\M-D\^P > > panic: kmem_malloc(536870912): kmem_map too small: 14929920 total allocated > KDB: stack backtrace: > kdb_backtrace(c071ee05,c0774e20,c072fcb3,e35a85ac,100)@kdb_backtrace+0x2e > panic(c072fcb3,20000000,e3d000,e35a85dc,c070cfed)@panic+0xb7 > kmem_malloc(c104c0a8,20000000,2,e35a862c,c068e532)@kmem_malloc+0xab > page_alloc(0,20000000,e35a861f,2,c56d47bc)@page_alloc+0x27 > uma_large_malloc(20000000,2,e35a8650,c04ead43,20000000)@ > uma_large_malloc+0x52malloc(20000000,c0746c80,2,0,c56ef9c0)@malloc+0x9e > g_read_data(c56ef9c0,0,200000,20000000,0)@g_read_data+0x50 > g_eli_read_metadata(c0746980,c56e0600,e35a8a7c,c0719b38,c56e0658)@ > g_eli_read_metadata+0xe1 > g_eli_taste(c0746980,c56e0600,0,c56e0700,4)@g_eli_taste+0xdc > g_new_provider_event(c56e0600,0,0,c072c28d,0)@g_new_provider_event+0x7a > one_event(66666667,c4aa1bd0,0,e35a8d00,c04eb955)@one_event+0x219 > g_run_events(c0772c90,0,4c,c072c28d,64)@g_run_events+0x15 > g_event_procbody(0,e35a8d38,0,0,0)@g_event_procbody+0x85 > fork_exit(c04eb8d0,0,e35a8d38)@fork_exit+0x7f > fork_trampoline()@fork_trampoline+0x8 > --- trap 0x1, eip = 0, esp = 0xe35a8d6c, ebp = 0 --- > Uptime: 16m5s > Dumping 1023 MB (2 chunks) > chunk 0: 1MB (159 pages) ... ok > chunk 1: 1023MB (261728 pages) 1007 991 975 959 943 927 911 895 879 > 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 > 575 559 543 527 511 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 ()@pcpu.h:166 > 166 pcpu.h: No such file or directory. > in pcpu.h [..] I have had similar problem on my laptop few weeks ago, ASUS A4D. Unfortunately I didn't have opportunity to obtain more information. Although I don't have dmesg -v output, traces are here: http://zsno.ids.czest.pl/~dunstan/FreeBSD/kmem01.log http://zsno.ids.czest.pl/~dunstan/FreeBSD/kmem02.log Some information about an environment: FreeBSD-CURRENT from the middle of December, filesystem with softupdates, snapshots, ACLs, MAC enabled. My case was somehow different: I was able to build world, but system got a panic while starting X environment. -- * Wojciech A. Koszek && From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 11:37:27 2006 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 B53C416A41F for ; Mon, 23 Jan 2006 11:37:27 +0000 (GMT) (envelope-from cbh-freebsd-current@groups.chrishedley.com) Received: from lon-mail-1.gradwell.net (lon-mail-1.gradwell.net [193.111.201.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id E65DF43D49 for ; Mon, 23 Jan 2006 11:37:26 +0000 (GMT) (envelope-from cbh-freebsd-current@groups.chrishedley.com) Received: from 53-233.adsl.zetnet.co.uk ([194.247.53.233] helo=mail.chrishedley.com ident=postmaster#pop3#chrishedley#com) by lon-mail-1.gradwell.net with esmtpa (Gradwell gwh-smtpd 1.207) id 43d4bff5.fc7a.2cbb for current@freebsd.org; Mon, 23 Jan 2006 11:37:25 +0000 (envelope-sender ) Received: from localhost (localhost [127.0.0.1]) by mail.chrishedley.com (Postfix) with ESMTP id 1CA91BC43 for ; Mon, 23 Jan 2006 11:37:24 +0000 (GMT) Received: from mail.chrishedley.com ([127.0.0.1]) by localhost (mail.chrishedley.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 80193-03 for ; Mon, 23 Jan 2006 11:37:22 +0000 (GMT) Received: from teapot.cbhnet (teapot.cbhnet [192.168.1.1]) by mail.chrishedley.com (Postfix) with ESMTP id 6E539BC3F for ; Mon, 23 Jan 2006 11:37:22 +0000 (GMT) Date: Mon, 23 Jan 2006 11:37:22 +0000 (GMT) From: Chris Hedley X-X-Sender: cbh@teapot.cbhnet To: current@freebsd.org Message-ID: <20060123112629.F79825@teapot.cbhnet> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: amavisd-new at chrishedley.com Cc: Subject: -CURRENT spontaneously rebooting when using X X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 11:37:27 -0000 Could someone advise how I can get a bit more information to report? :) I've just installed a fresh 6.0-RELEASE and immediately upgraded it to -CURRENT (most recent yesterday evening) and installed the latest xorg servers. When I start X, usually within a few seconds to a couple of minutes the system falls over, but unfortauntely it doesn't leave me at the kernel debugger and doesn't do a kernel dump for some reason or other, it just goes back to the BIOS and reboots. Can anyone donate a clue to me for what I need to do to find out what's going wrong? I'm using the amd64 compilation, if that makes any difference, and I've had the same problems with both the generic configuration as well as my customised one. I've experienced one or two other panics when not using X, but I was left in the debugger on those occasions so I don't know if they're related or not (I saved the kernel dump from one of them but have since overwritten the kernel, so it's probably not terribly helpful; not doing too well so far, am I!) Cheers, Chris. From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 14:35:38 2006 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 9E4E416A41F for ; Mon, 23 Jan 2006 14:35:38 +0000 (GMT) (envelope-from delphij@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 762B6447D8 for ; Mon, 23 Jan 2006 14:35:37 +0000 (GMT) (envelope-from delphij@gmail.com) Received: by uproxy.gmail.com with SMTP id o2so886903uge for ; Mon, 23 Jan 2006 06:35:35 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=mPvfYeG59immZFgg7DT/GeS7Ntx3PIQ69r1KOSC4lNUjLH0QQN18o6a6FRDojnLVk8N9eRCeygEwhFPgb+e1QTfFI8mGWOxIzHF14W283bTfi0H1dX9f9Qv7Jj0D7R2pS2FrrdruQdbYBEntHt1jwzB+Z7TZldDMJx1U5Zvc9tw= Received: by 10.66.241.1 with SMTP id o1mr2340745ugh; Mon, 23 Jan 2006 06:35:34 -0800 (PST) Received: by 10.66.216.17 with HTTP; Mon, 23 Jan 2006 06:35:34 -0800 (PST) Message-ID: Date: Mon, 23 Jan 2006 22:35:34 +0800 From: Xin LI To: Chris Hedley In-Reply-To: <20060123112629.F79825@teapot.cbhnet> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060123112629.F79825@teapot.cbhnet> Cc: current@freebsd.org Subject: Re: -CURRENT spontaneously rebooting when using X X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: delphij@delphij.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2006 14:35:38 -0000 Hi, On 1/23/06, Chris Hedley wrote= : > Could someone advise how I can get a bit more information to report? :) Which scheduler are you using? BTW. Try KDB_UNATTENDED which will force a crash dump when console is not accessable, yet allowing you to break into DDB using hot key. Cheers, -- Xin LI http://www.delphij.net From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 14:38:06 2006 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 8BF4616A4F8 for ; Mon, 23 Jan 2006 14:37:54 +0000 (GMT) (envelope-from cbh-freebsd-current@groups.chrishedley.com) Received: from lon-mail-4.gradwell.net (lon-mail-4.gradwell.net [193.111.201.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37C73445FE for ; Mon, 23 Jan 2006 14:13:51 +0000 (GMT) (envelope-from cbh-freebsd-current@groups.chrishedley.com) Received: from 53-233.adsl.zetnet.co.uk ([194.247.53.233] helo=mail.chrishedley.com ident=postmaster$pop3*chrishedley^com) by lon-mail-4.gradwell.net with esmtpa (Gradwell gwh-smtpd 1.207) id 43d4e49e.278d.d for current@freebsd.org; Mon, 23 Jan 2006 14:13:50 +0000 (envelope-sender ) Received: from localhost (localhost [127.0.0.1]) by mail.chrishedley.com (Postfix) with ESMTP id B301DC0B0 for ; Mon, 23 Jan 2006 14:13:42 +0000 (GMT) Received: from mail.chrishedley.com ([127.0.0.1]) by localhost (mail.chrishedley.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 80193-09 for ; Mon, 23 Jan 2006 14:13:40 +0000 (GMT) Received: from teapot.cbhnet (teapot.cbhnet [192.168.1.1]) by mail.chrishedley.com (Postfix) with ESMTP id CF373C0AF for ; Mon, 23 Jan 2006 14:13:40 +0000 (GMT) Date: Mon, 23 Jan 2006 14:13:40 +0000 (GMT) From: Chris Hedley X-X-Sender: cbh@teapot.cbhnet To: current@freebsd.org In-Reply-To: <20060123112629.F79825@teapot.cbhnet> Message-ID: <20060123140937.Q81165@teapot.cbhnet> References: <20060123112629.F79825@teapot.cbhnet> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: amavisd-new at chrishedley.com Cc: Subject: Re: -CURRENT spontaneously rebooting when using X X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 14:38:07 -0000 On Mon, 23 Jan 2006, Chris Hedley wrote: > Could someone advise how I can get a bit more information to report? :) > > I've just installed a fresh 6.0-RELEASE and immediately upgraded it to > -CURRENT (most recent yesterday evening) and installed the latest xorg > servers. When I start X, usually within a few seconds to a couple of minutes > the system falls over, but unfortauntely it doesn't leave me at the kernel > debugger and doesn't do a kernel dump for some reason or other, it just goes ... Thanks to David Wolfskill for talking me through setting up a serial console, I'm able to extract some debugging information from my system now. Some initial bits (retyped by me, hopefully not too many mistakes) follow: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0x48 fault code = supervisor read, page not present instruction pointer = 0x8:0xffffffff802b14fa stack pointer = 0x10:0xffffffffa263b9d0 frame pointer = 0x10:0xffffffffa263ba10 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = resume, IOPL = 0 current process = 38 (syncer) [thread pid 38 tid 100042 ] Stopped at propagate_priority+0x6a movq 0x48(%r15),%rbx Tracing pid 38 tid 100042 td 0xffffff003db4a000 propagate_priority() at propagate_priority+0x6a turnstile_wait() at turnstile_wait+0x20e _mtx_lock_sleep() at _mtx_lock_sleep+0x89 vfs_busy_pages() at vfs_busy_pages+0xd4 bufwrite() at burwrite+0x7b vfs_bio_awrite() at vfs_bio_awrite+0x5a vop_stdfsync() at vop_stdfsync+0x28c VOP_FSYNC_APV() at VOP_FSYNC+APV+0x3d sched_sync() at sched_sync+0x415 fork_exit() at fork_exit+0x86 form_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffffffa263bd40, rbp = 0 --- Is there anything else that might be useful in tracking down this problem? If it's anything that's very involved I may need to be pointed at an instruction manual! Cheers, Chris. From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 16:00:41 2006 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 21F6D16A474; Mon, 23 Jan 2006 16:00:41 +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 24FB544126; Mon, 23 Jan 2006 15:43:27 +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 k0NFhPG0099059; Mon, 23 Jan 2006 10:43:25 -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 k0NFhPxR095542; Mon, 23 Jan 2006 10:43:25 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 9A3CA7302F; Mon, 23 Jan 2006 10:43:25 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20060123154325.9A3CA7302F@freebsd-current.sentex.ca> Date: Mon, 23 Jan 2006 10:43:25 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner1 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2006 16:00:43 -0000 TB --- 2006-01-23 14:14:17 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-01-23 14:14:17 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2006-01-23 14:14:17 - cleaning the object tree TB --- 2006-01-23 14:14:49 - checking out the source tree TB --- 2006-01-23 14:14:49 - cd /tinderbox/HEAD/sparc64/sparc64 TB --- 2006-01-23 14:14:49 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-01-23 14:21:50 - building world (CFLAGS=-O2 -pipe) TB --- 2006-01-23 14:21:50 - cd /src TB --- 2006-01-23 14:21:50 - /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 --- 2006-01-23 15:27:41 - generating LINT kernel config TB --- 2006-01-23 15:27:41 - cd /src/sys/sparc64/conf TB --- 2006-01-23 15:27:41 - /usr/bin/make -B LINT TB --- 2006-01-23 15:27:41 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2006-01-23 15:27:41 - cd /src TB --- 2006-01-23 15:27:41 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Jan 23 15:27:41 UTC 2006 >>> 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 [...] @/dev/isp/isp_inline.h:450: warning: inlining failed in call to 'isp_copy_in_hdr': --param large-function-growth limit reached while inlining the caller /src/sys/modules/isp/../../dev/isp/isp_target.c:1482: warning: called from here @/dev/isp/isp_inline.h:450: warning: inlining failed in call to 'isp_copy_in_hdr': --param large-function-growth limit reached while inlining the caller /src/sys/modules/isp/../../dev/isp/isp_target.c:1553: warning: called from here @/dev/isp/isp_inline.h:1837: warning: inlining failed in call to 'isp_get_notify_ack_fc_e': --param large-function-growth limit reached /src/sys/modules/isp/../../dev/isp/isp_target.c:254: warning: called from here @/dev/isp/isp_inline.h:1816: warning: inlining failed in call to 'isp_get_notify_ack_fc': --param large-function-growth limit reached /src/sys/modules/isp/../../dev/isp/isp_target.c:257: warning: called from here *** Error code 1 Stop in /src/sys/modules/isp. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-01-23 15:43:25 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-01-23 15:43:25 - ERROR: failed to build lint kernel TB --- 2006-01-23 15:43:25 - tinderbox aborted TB --- 1.08 user 4.94 system 5347.78 real From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 18:36:15 2006 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 38FDB16A41F for ; Mon, 23 Jan 2006 18:36:15 +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 9A552442E1 for ; Mon, 23 Jan 2006 18:36:11 +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 k0NIa6ar027173 for ; Mon, 23 Jan 2006 21:36:06 +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 k0NIa5fR027171 for current@freebsd.org; Mon, 23 Jan 2006 21:36:05 +0300 (MSK) (envelope-from yar) Date: Mon, 23 Jan 2006 21:36:04 +0300 From: Yar Tikhiy To: current@freebsd.org Message-ID: <20060123183604.GB99678@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i Cc: Subject: panic: vm_page_free_toq: freeing mapped page X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 18:36:15 -0000 Hi there, I'm afraid something got broken in BIO/VFS since January, 19. I'm getting the following panic at system shutdown, after flushing buffers, and then at fsck run. I have to load a Jan 19 kernel to be able to run fsck. The panicing kernel, as well as userland, were built last night. This trace is from an fsck-time panic. panic: vm_page_free_toq: freeing mapped page 0xc0db3920 ... #11 0xc04e0213 in panic ( fmt=0xc067644c "vm_page_free_toq: freeing mapped page %p") at /usr/src/sys/kern/kern_shutdown.c:539 #12 0xc0603ab6 in vm_page_free_toq (m=0xc0db3920) at /usr/src/sys/vm/vm_page.c:1015 #13 0xc0603081 in vm_page_free (m=0xc0db3920) at /usr/src/sys/vm/vm_page.c:403 #14 0xc05286dd in vfs_vmio_release (bp=0xc6ff1768) at /usr/src/sys/kern/vfs_bio.c:1521 #15 0xc0527ecd in brelse (bp=0xc6ff1768) at /usr/src/sys/kern/vfs_bio.c:1307 #16 0xc05363ca in flushbuflist (bufv=0x12, flags=0, bo=0xc1f5d0b4, slpflag=0, slptimeo=0) at /usr/src/sys/kern/vfs_subr.c:1129 #17 0xc0535fc1 in bufobj_invalbuf (bo=0xc1f5d0b4, flags=0, td=0xc1da0680, slpflag=0, slptimeo=0) at /usr/src/sys/kern/vfs_subr.c:1006 #18 0xc05361c1 in vinvalbuf (vp=0xc1f5d000, flags=0, td=0xc1da0680, slpflag=0, slptimeo=0) at /usr/src/sys/kern/vfs_subr.c:1065 #19 0xc05e121d in ffs_reload (mp=0xc1e4e400, td=0xc1da0680) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:553 #20 0xc05e0710 in ffs_mount (mp=0xc1e4e400, td=0xc1da0680) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:252 #21 0xc0532fb7 in vfs_domount (td=0xc1da0680, fstype=0xc1e4c9e0 "ufs", fspath=0xc1e4e400 "", fsflags=331777, fsdata=0xc1e4c9b0) at /usr/src/sys/kern/vfs_mount.c:858 #22 0xc05328ac in vfs_donmount (td=0xc1da0680, fsflags=331777, fsoptions=0xcbde1ba8) at /usr/src/sys/kern/vfs_mount.c:611 #23 0xc0534c89 in kernel_mount (ma=0xc1e4c990, flags=331777) at pcpu.h:163 #24 0xc05e0d91 in ffs_cmount (ma=0xc1e4c990, data=0xc0c15000, flags=331777, td=0xc1da0680) at /usr/src/sys/ufs/ffs/ffs_vfsops.c:427 #25 0xc0532a9a in mount (td=0xc1da0680, uap=0xcbde1d04) at /usr/src/sys/kern/vfs_mount.c:689 At shutdown time, the trace looks similarly (got it on the screen only): panic vm_page_free_toq vm_page_free vfs_vmio_release brelse flushbuflist bufobj_invalbuf vinvalbuf vgonel vflush ffs_flushfiles ffs_unmount dounmount vfs_unmountall boot reboot Yar From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 18:48:06 2006 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 74BC216A49E; Mon, 23 Jan 2006 18:48:05 +0000 (GMT) (envelope-from mich@FreeBSD.org) Received: from mail2.itxmarket.com (fw.itxmarket.com [213.11.40.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id A359244191; Mon, 23 Jan 2006 18:26:08 +0000 (GMT) (envelope-from mich@FreeBSD.org) Received: from icommerce.fr (mich2.itxmarket.com [192.168.2.26]) by mail2.itxmarket.com (Postfix) with ESMTP id 6D85337C00; Mon, 23 Jan 2006 19:26:07 +0100 (CET) Received: by icommerce.fr (Postfix, from userid 1001) id 66BB62281F; Mon, 23 Jan 2006 19:26:07 +0100 (CET) Date: Mon, 23 Jan 2006 19:26:07 +0100 From: Michael Landin Hostbaek To: Nicolas Blais Message-ID: <20060123182607.GR99407@mich2.itxmarket.com> Mail-Followup-To: Michael Landin Hostbaek , Nicolas Blais , freebsd-current@freebsd.org, sos@FreeBSD.org References: <200601211159.50768.nb_root@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200601211159.50768.nb_root@videotron.ca> X-Operating-System: FreeBSD 6.0-STABLE i386 X-PGP-Key: http://www.freebsdcluster.org/~mich/ User-Agent: Mutt/1.5.11 Cc: freebsd-current@freebsd.org, sos@FreeBSD.org Subject: Re: -CURRENT freeze at boot after update X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2006 18:48:10 -0000 Nicolas Blais (nb_root) writes: > Hi, > > I did my usual saturday -CURRENT sync (buildworld/kernel) this morning and my > machine freezes at boot. The freeze occurs right after HD detection, and > before (or during) mounting partitions : > > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x300> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/11.10, addr 2, iclass 3/1 > ums0: 3 buttons and Z dir. > Timecounter "TSC" frequency 2493036546 Hz quality 800 > Timecounters tick every 1.000 msec > ad0: 78167MB at ata0-master UDMA133 > acd0: DVDR at ata1-master UDMA33 > ad4: 76319MB at ata2-master SATA150 > Just a quick me too ! Disabling dma for my cd/dvd drive gets it rolling again. I spoke briefly to sos@ about it, and he has been unable to reproduce this, so someone with time / knowledge should dig deeper and send him a mail with the findings. /mich From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 19:04:18 2006 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 E630916A41F; Mon, 23 Jan 2006 19:04:18 +0000 (GMT) (envelope-from sos@deepcore.dk) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E37E43D49; Mon, 23 Jan 2006 19:04:17 +0000 (GMT) (envelope-from sos@deepcore.dk) Received: from [194.192.25.142] (spider.deepcore.dk [194.192.25.142]) by spider.deepcore.dk (8.13.4/8.13.4) with ESMTP id k0NJ4DCA040223; Mon, 23 Jan 2006 20:04:14 +0100 (CET) (envelope-from sos@deepcore.dk) Message-ID: <43D528AD.7020309@deepcore.dk> Date: Mon, 23 Jan 2006 20:04:13 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Landin Hostbaek References: <200601211159.50768.nb_root@videotron.ca> <20060123182607.GR99407@mich2.itxmarket.com> In-Reply-To: <20060123182607.GR99407@mich2.itxmarket.com> Content-Type: multipart/mixed; boundary="------------000806000505090308050607" X-mail-scanned: by DeepCore Virus & Spam killer v1.16 Cc: freebsd-current@FreeBSD.ORG, Nicolas Blais Subject: Re: -CURRENT freeze at boot after update X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2006 19:04:19 -0000 This is a multi-part message in MIME format. --------------000806000505090308050607 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Michael Landin Hostbaek wrote: > Nicolas Blais (nb_root) writes: > >>Hi, >> >>I did my usual saturday -CURRENT sync (buildworld/kernel) this morning and my >>machine freezes at boot. The freeze occurs right after HD detection, and >>before (or during) mounting partitions : >> >>sc0: at flags 0x100 on isa0 >>sc0: VGA <16 virtual consoles, flags=0x300> >>vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 >>ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/11.10, addr 2, iclass 3/1 >>ums0: 3 buttons and Z dir. >>Timecounter "TSC" frequency 2493036546 Hz quality 800 >>Timecounters tick every 1.000 msec >>ad0: 78167MB at ata0-master UDMA133 >>acd0: DVDR at ata1-master UDMA33 >>ad4: 76319MB at ata2-master SATA150 >> > > > Just a quick me too ! > > Disabling dma for my cd/dvd drive gets it rolling again. > > I spoke briefly to sos@ about it, and he has been unable to reproduce > this, so someone with time / knowledge should dig deeper and send him a > mail with the findings. The only thing that comes to mind is the below patch, please try that out and let me know. However that way the legacy ports (those stuck at irq14 & irq15) cannot share interrupt with *anything*, which I did want to fix as a side effect of this actually... -Søren --------------000806000505090308050607 Content-Type: text/plain; name="dma-fix-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dma-fix-1" Index: ata-pci.c =================================================================== RCS file: /export/ncvs/src/sys/dev/ata/ata-pci.c,v retrieving revision 1.112 diff -u -r1.112 ata-pci.c --- ata-pci.c 18 Jan 2006 13:10:17 -0000 1.112 +++ ata-pci.c 23 Jan 2006 19:00:35 -0000 @@ -439,8 +439,8 @@ { struct ata_channel *ch = device_get_softc(dev); - if (ch->dma && ((ch->flags & ATA_ALWAYS_DMASTAT) || - (ch->dma->flags & ATA_DMA_ACTIVE))) { + if (!ata_legacy(dev) && ch->dma && ((ch->flags & ATA_ALWAYS_DMASTAT) || + (ch->dma->flags & ATA_DMA_ACTIVE))) { int bmstat = ATA_IDX_INB(ch, ATA_BMSTAT_PORT) & ATA_BMSTAT_MASK; if ((bmstat & (ATA_BMSTAT_ACTIVE | ATA_BMSTAT_INTERRUPT)) != --------------000806000505090308050607-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 19:14:45 2006 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 4C5D716A41F for ; Mon, 23 Jan 2006 19:14:45 +0000 (GMT) (envelope-from alexjeffburke@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id D981343D46 for ; Mon, 23 Jan 2006 19:14:44 +0000 (GMT) (envelope-from alexjeffburke@gmail.com) Received: by zproxy.gmail.com with SMTP id z3so928245nzf for ; Mon, 23 Jan 2006 11:14:44 -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=a80ACzVePMTmWOuuNBnwZ5GGeiYMCvhcAq46A7q717J1CRicA/7oBxc49vhGWOK8cR/5E6AvUubs7rLCr7+O0VueWX5w08wrDN4qcBIRISe9q08iOwYHgRvahl3Rrm75Qk6053q2+oOWkaMTK0V8PrylRX7a/CK4wAfJhkgoW94= Received: by 10.64.250.1 with SMTP id x1mr1025244qbh; Mon, 23 Jan 2006 11:14:43 -0800 (PST) Received: by 10.65.253.6 with HTTP; Mon, 23 Jan 2006 11:14:43 -0800 (PST) Message-ID: Date: Mon, 23 Jan 2006 19:14:43 +0000 From: Alex Burke To: FreeBSD CURRENT MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline Subject: Swap_pager and modified after free console messages X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 19:14:45 -0000 SGksCgpGaXJzdCwgYXBvbG9naWVzIEkgZG9udCBoYXZlIGFueSBleHRyYSBpbmZvcm1hdGlvbiAt IHRoYXQgaXMgcGFydGx5CndoYXQgbXkgcG9zdCBpcyBhYm91dC4gSSBoYXZlIGJlZW4gZ2V0dGlu ZyBhIGNvdXBsZSBvZiBtZXNzYWdlcyBJIGhhdmUKbm90IHNlZW4gYmVmb3JlIHJ1bm5pbmcgLUNV UlJFTlQsIGFuZCB3YW50ZWQgdG8gYXNrIHdoZXRoZXIgdGhlcmUgYXJlCmFueSBzdGVwcyBJIGNv dWxkIHRha2UgdG8gaGVscCBkZWJ1Z2dpbmcgaWYgcGVvcGxlIHRoaW5rIHRoYXQgaXMgd29ydGgK dHlpbmcuCgpUaGlzIGlzIHdoYXQgSSBoYXZlIHNlZW4gb3ZlciB0aGUgcGFzdCBmZXcgZGF5czoK MSkga2VybmVsOiBtZW1vZXJ5IG1vZGlmaWVkIGFmdGVyIGZyZWUgYW5kIHRoZW4gd2hhdCBhcHBl YXJzIHRvIGJlIGEKbWVtb3J5IGFkZHJlc3MKCkkgc2F3IGFub3RoZXIgcG9zdCBtZW50aW9uaW5n IGEgY29uc29sZSBtZXNzYWdlIGxpa2UgdGhpcyB0aGF0CmFwcGVhcmVkIHRvIGJlIHJlbGF0ZWQg dG8gdGhlIHN1YnNlcXVlbnQgcGFuaWMsIGJ1dCBtaW5lIGhhc250IGNhdXNlZAp0aGUgbWFjaGlu ZSB0byBwYW5pYy4gSSBhbSBub3Qgc3VyZSBpZiB0aGlzIGlzIGJlY2F1c2UgSSBoYXZlIHRoZQpz dGFuZGFyZCAtQ1VSUkVOVCBHRU5FUklDIGtlcm5lbCBydW5uaW5nICh3aXRoIFdJVE5FU1MsIElO VkFSSUFOVFMKc3RpbGwgZW5hYmxlZCksIGJ1dCBhIHJlcGx5IHNhaWQgdXNlIG1lbWdhdXJkIHRv IHRyYWNrIGRvd24gdGhlIGlzc3VlLgpIb3cgc2hvdWxkIEkgY29uZmlndXJlIHRoaXM/CgoyKSBh IHN3YXBfcGFnZXIgbWVzc2FnZSBhYm91dCBub3QgYmVpbmcgYWJsZSB0byBhbGxvY2F0ZSBhbnkg bW9yZSBzcGFjZS4KCk15IC91c3IgZmlsZXN5c3RlbSB3YXMgZnVsbCAoZXhjZXB0IGZvciB0aGUg bGFzdCA4JSByZXNlcnZlZCBmb3Igcm9vdApvbmx5KSwgYW5kIEkgaGFkIGJlZW4gZG9pbmcgc29t ZSBoZWF2eSBwb3J0cyB0cmVlIGNvbXBpbGluZy4gSSBhbSBqdXN0Cm5vdCBzdXJlIGlmIHRoYXQg bWVzc2FnZSBpcyBub3JtYWwgYW5kIHRoYXQgc3dhcCB3YXMgUkVBTExZIDEwMCUgdXNlZAp1cCwg b3Igd2hldGhlciBpdCB3YXMgaW5kaWNhdGl2ZSBvZiBzb21ldGhpbmcgZWxzZSBhbmQgSSBzaG91 bGQgdHJ5IHRvCnJlcGxpY2F0ZSB0aGUgaXNzdWUuCgpBZ2FpbiwgYXBvbG9naWVzIGlmIHRoaXMg cG9zdCBzZWVtcyB2ZXJ5IHNwYXJzZS4uLkkgaGF2ZSB2ZXJ5IGxpdHRsZQppZGVhIHdoZXJlIHRv IGdvIHdpdGggdGhlc2UgdGhpbmdzLgoKVGhhbmtzIGZvciB5b3VyIHBhdGllbmNlLCBBbGV4IEog QnVya2UuCg== From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 19:21:59 2006 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 154D116A41F for ; Mon, 23 Jan 2006 19:21:59 +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 B358943D46 for ; Mon, 23 Jan 2006 19:21:58 +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 DB83BBC74 for ; Mon, 23 Jan 2006 19:21:56 +0000 (UTC) To: current@freebsd.org From: Poul-Henning Kamp Date: Mon, 23 Jan 2006 20:21:56 +0100 Message-ID: <14054.1138044116@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Subject: Speeding up cpu-time accounting (rerun) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 19:21:59 -0000 http://www.freebsd.org/cgi/getmsg.cgi?fetch=239010+242520+/usr/local/www/db/text/2005/freebsd-current/20051204.freebsd-current I can't really say I have gotten much feedback on this. Given that there may be 2-10% speedup of context-switches in it I would have expected more interest ? -- 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 Jan 23 20:10:39 2006 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 07DC316A465 for ; Mon, 23 Jan 2006 20:10:39 +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 9784D43EEE for ; Mon, 23 Jan 2006 19:41:32 +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 59F856E875 for ; Mon, 23 Jan 2006 20:41:30 +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 k0NJfQic025959 for ; Mon, 23 Jan 2006 20:41:29 +0100 (CET) From: Thierry Herbelot To: current@freebsd.org Date: Mon, 23 Jan 2006 20:41:17 +0100 User-Agent: KMail/1.9.1 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: <200601232041.19159.thierry@herbelot.com> Cc: Subject: softdep panic at reboot (and restart) 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: Mon, 23 Jan 2006 20:10:41 -0000 Hello, I'm getting a new panic while rebooting after make buildworld && mergemaster : # reboot Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...3 2 2 2 1 0 0 0 done All buffers synced. panic: vm_page_free_toq: freeing mapped page 0xc11fae58 cpuid = 0 KDB: enter: panic [thread pid 18926 tid 100089 ] Stopped at kdb_enter+0x2b: nop db> where Tracing pid 18926 tid 100089 td 0xc1bf4820 kdb_enter(c0882826) at kdb_enter+0x2b panic(c089ec94,c11fae58,c11fae58,0,c76a4994) at panic+0x127 vm_page_free_toq(c11fae58,c11fae58,40,c11fae58,c76a49ac) at vm_page_free_toq+0x32 vm_page_free(c11fae58) at vm_page_free+0x15 vfs_vmio_release(c3372c40) at vfs_vmio_release+0x95 brelse(c3372c40,c3372c40) at brelse+0x489 flushbuflist(c1de45cc,1,c1de45c8,0,0) at flushbuflist+0x206 bufobj_invalbuf(c1de45c8,1,c1bf4820,0,0) at bufobj_invalbuf+0x111 vinvalbuf(c1de4514,1,c1bf4820,0,0) at vinvalbuf+0x1d vgonel(c1de4514) at vgonel+0x75 vflush(c18c1800,0,2,c1bf4820,4ae) at vflush+0x2d2 ffs_flushfiles(c18c1800,2,c1bf4820) at ffs_flushfiles+0x56 softdep_flushfiles(c18c1800,2,c1bf4820,c06ac6ee,c0934bc0) at softdep_flushfiles+0x1e ffs_unmount(c18c1800,80000,c1bf4820,0,c18d8b2c) at ffs_unmount+0x32 dounmount(c18c1800,80000,c1bf4820,c33360b8,0) at dounmount+0x204 vfs_unmountall(0,8,c088284a,0,c1bf4820) at vfs_unmountall+0x46 boot(0,c094e988,0,c088284a,a1) at boot+0x3c6 reboot(c1bf4820,c76a4d04,c1bf4820,0,2) at reboot+0x32 syscall(3b,3b,3b,0,2) at syscall+0x27e Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (55, FreeBSD ELF32, reboot), eip = 0x280add0f, esp = 0xbfbfedcc, ebp = 0xbfbfee18 --- db> db> ps pid proc uid ppid pgrp flag stat wmesg wchan cmd 18926 c1bf3ac8 0 1 18926 0004002 [CPU 0] reboot 41 c18a4ac8 0 0 0 0000204 [SLPQ m:w1 0xc18a8100][SLP] g_mirror files1 40 c18a4cf0 0 0 0 0000204 [SLPQ - 0xc72ccd04][SLP] schedcpu 39 c18a6000 0 0 0 0000204 [SLPQ - 0xc09a2dec][SLP] nfsiod 3 38 c17a8cf0 0 0 0 0000204 [SLPQ - 0xc09a2de8][SLP] nfsiod 2 37 c182b000 0 0 0 0000204 [SLPQ - 0xc09a2de4][SLP] nfsiod 1 36 c182b228 0 0 0 0000204 [SLPQ - 0xc09a2de0][SLP] nfsiod 0 35 c182b450 0 0 0 0000204 [SLPQ ktsusp 0xc182b4d4][SLP] vnlru 34 c182b678 0 0 0 0000204 [SLPQ ktsusp 0xc182b6fc][SLP] syncer 33 c182b8a0 0 0 0 0000204 [SLPQ ktsusp 0xc182b924][SLP] bufdaemon 32 c182bac8 0 0 0 000020c [CPU 1] pagezero 31 c182bcf0 0 0 0 0000204 [SLPQ psleep 0xc09a8c3c][SLP] vmdaemon 9 c182e000 0 0 0 0000204 [SLPQ psleep 0xc09a8bfc][SLP] pagedaemon 8 c182e228 0 0 0 0000204 [SLPQ m:w1 0xc1830300][SLP] g_mirror gm0s1 30 c182e450 0 0 0 0000204 [IWAIT] irq5: pcm1 7 c16f5678 0 0 0 0000204 [SLPQ - 0xc16cbe3c][SLP] fdc0 29 c16f58a0 0 0 0 0000204 [IWAIT] swi0: sio 28 c16f5ac8 0 0 0 0000204 [IWAIT] irq7: ppc0 27 c16f5cf0 0 0 0 0000204 [IWAIT] irq1: atkbd0 26 c17a8000 0 0 0 0000204 [IWAIT] irq17: atapci1 25 c17a8228 0 0 0 0000204 [IWAIT] irq18: pcm0++ 24 c17a8450 0 0 0 0000204 [SLPQ usbtsk 0xc094c744][SLP] usbtask 23 c17a8678 0 0 0 0000204 [SLPQ usbevt 0xc17b1210][SLP] usb0 22 c17a88a0 0 0 0 0000204 [IWAIT] irq19: dc0 uhci0 21 c17a8ac8 0 0 0 0000204 [IWAIT] irq15: ata1 20 c16e2228 0 0 0 0000204 [IWAIT] irq14: ata0 6 c16e2450 0 0 0 0000204 [SLPQ - 0xc1792300][SLP] thread taskq 19 c16e2678 0 0 0 0000204 [IWAIT] swi6: Giant taskq 18 c16e28a0 0 0 0 0000204 [IWAIT] swi6: task queue 5 c16e2ac8 0 0 0 0000204 [SLPQ - 0xc1792580][SLP] kqueue taskq 17 c16e2cf0 0 0 0 0000204 [IWAIT] swi2: cambio 16 c16f5000 0 0 0 0000204 [IWAIT] swi5: + 15 c16f5228 0 0 0 0000204 [SLPQ - 0xc094a3a0][SLP] yarrow 4 c16f5450 0 0 0 0000204 [SLPQ - 0xc094cebc][SLP] g_down 3 c16dd000 0 0 0 0000204 [SLPQ - 0xc094ceb8][SLP] g_up 2 c16dd228 0 0 0 0000204 [SLPQ - 0xc094ceb0][SLP] g_event 14 c16dd450 0 0 0 0000204 [IWAIT] swi1: net 13 c16dd678 0 0 0 0000204 [IWAIT] swi3: vm 12 c16dd8a0 0 0 0 000020c [RUNQ] swi4: clock sio 11 c16ddac8 0 0 0 000020c [Can run] idle: cpu0 10 c16ddcf0 0 0 0 000020c [Can run] idle: cpu1 1 c16e2000 0 0 1 0004200 [SLPQ wait 0xc16e2000][SLP] init 0 c094cfc0 0 0 0 0000200 [IWAIT] swapper db> db> show thread 100089 (0xc1bf4820) kdb_enter(c0882826) at kdb_enter+0x2b 100047 (0xc18a5680) sched_switch(c18a5680,0,1) at sched_switch+0x183 100048 (0xc18a54e0) sched_switch(c18a54e0,0,1) at sched_switch+0x183 100049 (0xc18a5340) sched_switch(c18a5340,0,1) at sched_switch+0x183 100027 (0xc16e3d00) sched_switch(c16e3d00,0,1) at sched_switch+0x183 100028 (0xc16e3b60) sched_switch(c16e3b60,0,1) at sched_switch+0x183 100029 (0xc16e39c0) sched_switch(c16e39c0,0,1) at sched_switch+0x183 100030 (0xc16e3820) sched_switch(c16e3820,0,1) at sched_switch+0x183 100031 (0xc16e3680) sched_switch(c16e3680,0,1) at sched_switch+0x183 100032 (0xc16e34e0) sched_switch(c16e34e0,0,1) at sched_switch+0x183 100033 (0xc182d000) cpustop_handler(c72a6c74,c0814bb1,317,c182d000,0) at cpustop_handler+0x31 100034 (0xc182cd00) sched_switch(c182cd00,0,1) at sched_switch+0x183 100035 (0xc182cb60) sched_switch(c182cb60,0,1) at sched_switch+0x183 100036 (0xc182c9c0) sched_switch(c182c9c0,0,1) at sched_switch+0x183 100037 (0xc182c820) fork_trampoline() at fork_trampoline 100017 (0xc16df680) sched_switch(c16df680,0,1) at sched_switch+0x183 100018 (0xc16df4e0) sched_switch(c16df4e0,0,1) at sched_switch+0x183 100019 (0xc16df340) fork_trampoline() at fork_trampoline 100020 (0xc16df1a0) fork_trampoline() at fork_trampoline 100021 (0xc17a9820) fork_trampoline() at fork_trampoline 100022 (0xc17a9680) sched_switch(c17a9680,0,1) at sched_switch+0x183 100023 (0xc17a94e0) sched_switch(c17a94e0,0,1) at sched_switch+0x183 100024 (0xc17a9340) sched_switch(c17a9340,0,1) at sched_switch+0x183 100025 (0xc17a91a0) fork_trampoline() at fork_trampoline 100026 (0xc17a9000) sched_switch(c17a9000,0,1) at sched_switch+0x183 100008 (0xc16de1a0) sched_switch(c16de1a0,0,1) at sched_switch+0x183 100009 (0xc16de000) sched_switch(c16de000,0,1) at sched_switch+0x183 100010 (0xc16e3340) fork_trampoline() at fork_trampoline 100011 (0xc16e31a0) sched_switch(c16e31a0,0,1) at sched_switch+0x183 100012 (0xc16e3000) sched_switch(c16e3000,0,1) at sched_switch+0x183 100013 (0xc16dfd00) fork_trampoline() at fork_trampoline 100014 (0xc16dfb60) fork_trampoline() at fork_trampoline 100015 (0xc16df9c0) sched_switch(c16df9c0,0,1) at sched_switch+0x183 100016 (0xc16df820) sched_switch(c16df820,0,1) at sched_switch+0x183 100000 (0xc16df000) sched_switch(c16df000,0,1) at sched_switch+0x183 100001 (0xc16ded00) sched_switch(c16ded00,0,1) at sched_switch+0x183 100002 (0xc16deb60) fork_trampoline() at fork_trampoline 100003 (0xc16de9c0) fork_trampoline() at fork_trampoline 100004 (0xc16de820) sched_switch(c16de820,0,1) at sched_switch+0x183 100005 (0xc16de680) sched_switch(c16de680,c17a9000,6) at sched_switch+0x183 100006 (0xc16de4e0) sched_switch(c16de4e0,0,1) at sched_switch+0x183 100007 (0xc16de340) sched_switch(c16de340,0,1) at sched_switch+0x183 0 (0xc094d200) sched_switch(c094d200,0,1) at sched_switch+0x183 I get a similar panic at startup : GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2006 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 #1059: Mon Jan 23 12:22:22 CET 2006 XXX@YYYfiles1/obj/files1/src/sys/GENERIC WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium II/Pentium II Xeon/Celeron (334.09-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183fbff ..... Starting file system checks: /dev/mirror/gm0s1a: 2349 files, 47905 used, 51158 free (2478 frags, 6085 blocks, 2.5% fragmentation) panic: vm_page_free_toq: freeing mapped page 0xc11b6a88 cpuid = 0 KDB: enter: panic [thread pid 80 tid 100039 ] Stopped at kdb_enter+0x2b: nop db> where Tracing pid 80 tid 100039 td 0xc182c4e0 kdb_enter(c0882826) at kdb_enter+0x2b panic(c089ec94,c11b6a88,c11b6a88,0,c7294780) at panic+0x127 vm_page_free_toq(c11b6a88,c11b6a88,40,c11b6a88,c7294798) at vm_page_free_toq+0x32 vm_page_free(c11b6a88) at vm_page_free+0x15 vfs_vmio_release(c3337b98) at vfs_vmio_release+0x95 brelse(c3337b98,c3337b98) at brelse+0x489 flushbuflist(c18f94c8,0,c18f94c4,0,0) at flushbuflist+0x206 bufobj_invalbuf(c18f94c4,0,c182c4e0,0,0) at bufobj_invalbuf+0x111 vinvalbuf(c18f9410,0,c182c4e0,0,0) at vinvalbuf+0x1d ffs_reload(c188cc00,c182c4e0,c18b1c80,c18e5200,c1904104) at ffs_reload+0x481 ffs_mount(c188cc00,c182c4e0,20000000,5001,c106c788) at ffs_mount+0x570 vfs_domount(c182c4e0,c18b5380,c18b5440,51001,c18b52c0) at vfs_domount+0x50b vfs_donmount(c182c4e0,51001,c7294ba8,c1902b80,c) at vfs_donmount+0x374 kernel_mount(c18b5270,51001,0,0,0) at kernel_mount+0x6d ffs_cmount(c18b5270,bfbfed80,51001,c182c4e0,c09251e0) at ffs_cmount+0x5d mount(c182c4e0,c7294d04,c0813aca,82,c0666d37) at mount+0x156 syscall(3b,3b,3b,0,a000050) at syscall+0x27e Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (21, FreeBSD ELF32, mount), eip = 0x280cd047, esp = 0xbfbfec9c, ebp = 0xbfbfee08 --- db> From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 20:35:00 2006 Return-Path: X-Original-To: freebsd-current@www.freebsd.org Delivered-To: freebsd-current@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4ACD16A41F for ; Mon, 23 Jan 2006 20:35:00 +0000 (GMT) (envelope-from ggajic@afrodita.rcub.bg.ac.yu) Received: from afrodita.rcub.bg.ac.yu (afrodita.rcub.bg.ac.yu [147.91.1.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE88943D55 for ; Mon, 23 Jan 2006 20:34:54 +0000 (GMT) (envelope-from ggajic@afrodita.rcub.bg.ac.yu) Received: from afrodita.rcub.bg.ac.yu (localhost.localdomain [127.0.0.1]) by afrodita.rcub.bg.ac.yu (8.13.4/8.13.4) with ESMTP id k0NKYnHV012315 for ; Mon, 23 Jan 2006 21:34:49 +0100 Received: from localhost (ggajic@localhost) by afrodita.rcub.bg.ac.yu (8.13.4/8.13.4/Submit) with ESMTP id k0NKYmC7012308 for ; Mon, 23 Jan 2006 21:34:48 +0100 Date: Mon, 23 Jan 2006 21:34:47 +0100 (CET) From: Goran Gajic To: freebsd-current@www.freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-RCUB-MailScanner-Information: Please contact the RCUB if you have problem with mail X-RCUB-MailScanner: Found to be clean X-RCUB-MailScanner-From: ggajic@afrodita.rcub.bg.ac.yu X-Mailman-Approved-At: Mon, 23 Jan 2006 20:37:48 +0000 Cc: Subject: olvwm crash 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, 23 Jan 2006 20:35:00 -0000 Hi, It seems like change to malloc also causes olvwm to crash on amd64 (7.0-CURRENT): 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 "amd64-marcel-freebsd"... (gdb) run Starting program: /usr/ports/x11-wm/olvwm/work/olvwm Program received signal SIGSEGV, Segmentation fault. MakeOpenButton (dpy=0x802ffc550, scrInfo=0x802fef0e0) at images.c:739 739 *b = openButton; (gdb) where #0 MakeOpenButton (dpy=0x802ffc550, scrInfo=0x802fef0e0) at images.c:739 #1 0x000000000042ff18 in initMenuButtons (dpy=0x802ffc550, scrInfo=0x802fef0e0) at usermenu.c:2022 #2 0x0000000000430101 in InitMenus (dpy=0x802ffc550, scrInfo=0x802fef0e0) at usermenu.c:2061 #3 0x0000000000427176 in initScreenInfo (dpy=0x802ffc550, screenno=0, visInfo=0x7fffffffe010, nvis=1) at screen.c:2589 #4 0x0000000000427adc in InitScreens (dpy=0x802ffc550) at screen.c:2653 #5 0x00000000004203d5 in main (argc=1, argv=0x0) at olwm.c:331 (gdb) Regards, gg. From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 20:58:11 2006 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 E813516A423 for ; Mon, 23 Jan 2006 20:58:11 +0000 (GMT) (envelope-from air.lightz@gmail.com) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F3B843D5A for ; Mon, 23 Jan 2006 20:58:10 +0000 (GMT) (envelope-from air.lightz@gmail.com) Received: by uproxy.gmail.com with SMTP id o2so60227uge for ; Mon, 23 Jan 2006 12:58:09 -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=F5SFYtWJjA0YTmbmmi5kGvEhekmTRlSZx8LUrxQZ4+PYr8X9M33mZc45ZFgK1Vy6+3r+hYwc4gUfktI6TIh4TlMcdKOgwJsJPGimr/+E263FaeQjOwiFJHUueEqdgUwjzSPYfOf8z7UNfXiC67qtfCT5/1WmiPQsuutwZvxJeOo= Received: by 10.48.216.2 with SMTP id o2mr380750nfg; Mon, 23 Jan 2006 12:58:08 -0800 (PST) Received: by 10.49.28.16 with HTTP; Mon, 23 Jan 2006 12:58:08 -0800 (PST) Message-ID: <1b62a7390601231258o7bf43126rc977ff00f374e2e6@mail.gmail.com> Date: Mon, 23 Jan 2006 15:58:08 -0500 From: resonant evil 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: Novice user with really easy question regarding atheros compatibility on 3com wireless card X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jan 2006 20:58:12 -0000 Hi all.. Novice user, but I love BSD and any free OS compared to Windows, but I have a pretty easy question regarding a card I am about to go out and purchase. Right now I have a Dell D600 Laptop which uses a Broadcomm BCM4306 wireless card (which makes setting up wireless a REAL pain under any OS other than Windows.) I am totally sick and tired of always having to use a NDISwrappe= r tool to use 3rd Party windows drivers, so I want to go out and buy a much better wireless card that will work without me having to do so much manual configuration.. I just want the thing to be detected and ready to go when = I install things like FreeBSD or Linux.. (Obviously mainly FreeBSD) So I visited the hardware compatibility list at www.freebsd.org/releases/and checked for cards with the ath(4) compatibility (EVERYONE on #freebsd on irc.freenode.net reccomended getting an Atheros card).. My selection of cards here in Canada is quite limited, but luckily according to the hardwar= e compatibility list it says "3COM 3CRPAG175" Here at my local store I was able to find THIS CARD: http://www.compusmart.com/Product/Default.aspx?CatalogID=3D0&SupplierPartNo= =3D334098&ShowStoreInv=3DTrue But the Part # has an additional letter than the one on the compatibility list! This PART # is "3COM 3CRPAG175B" (note the extra B on the end).. No= w generally I would think that it wouldn't or shouldn't make a difference and its probably just a revision or something, but this is alot of money to blo= w on a card if it isn't backwards compatible. I desperately need a bit of help knowing if this card is going to compatibl= e with ath before I go out and drop $119 on it, so if ANYONE could help get the information or the answer I need it would be GREATLY appreciated Thank you so much in advance, I really appreciate help on groups like this as a new user :) Seeya -Ryan From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 21:00:03 2006 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 1B22C16A420 for ; Mon, 23 Jan 2006 21:00:03 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4643043D4C for ; Mon, 23 Jan 2006 21:00:02 +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 6790125 for multiple; Mon, 23 Jan 2006 16:01:07 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k0NKxsoB003319; Mon, 23 Jan 2006 15:59:56 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: thierry@herbelot.com Date: Mon, 23 Jan 2006 15:51:07 -0500 User-Agent: KMail/1.9.1 References: <200601040806.37953.thierry@herbelot.com> <200601040838.49663.jhb@freebsd.org> <200601210705.11539.thierry@herbelot.com> In-Reply-To: <200601210705.11539.thierry@herbelot.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200601231551.08474.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1247/Sat Jan 21 05:24:51 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-current@freebsd.org Subject: Re: panic: spin lock held too long (while rebooting) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 21:00:03 -0000 On Saturday 21 January 2006 01:05, Thierry Herbelot wrote: > Le Wednesday 4 January 2006 14:38, John Baldwin a =E9crit : > > On Wednesday 04 January 2006 02:06 am, Thierry Herbelot wrote: > > [SNIP previous similar panic] > > > Next time you get this, can you use 'show threads' to figure out the tid > > for the thread whose pointer is in the printf (0xc16de480 in this case) > > and then do a trace of that thread? > > Hello, > > Here is a more detailed crash session : > > is this (zomb) problematic ? (in ps) : > 8 c182e228 0 1 0 0002204 zomb[INACTIVE] g_mirror gm0s1 > > I keep the machine in DDB, if there are more detailed commands to > investigate the panic (the machine is an SMP BP6, runs a GENERIC current > kernel, and stores its local files in two g_mirror partitions). > > The problematic spinlock is held by 0xc16de340 which is cpustop_handler. > > TfH > > PS : printout of the crash : > > # reboot > Waiting (max 60 seconds) for system process `vnlru' to stop...done > Waiting (max 60 seconds) for system process `bufdaemon' to stop...done > Waiting (max 60 seconds) for system process `syncer' to stop... > Syncing disks, vnodes remaining...3 2 2 2 0 0 done > All buffers synced. > Uptime: 39m52s > GEOM_MIRROR: Device files1: provider mirror/files1 destroyed. > GEOM_MIRROR: Device files1 destroyed. > GEOM_MIRROR: Device gm0s1: provider mirror/gm0s1 destroyed. > GEOM_MIRROR: Device gm0s1 destroyed. > Rebooting... > cpu_reset: Stopping other CPUs > spin lock sched lock held by 0xc16de340 for > 5 seconds > panic: spin lock held too long Ok, it's not a fatal panic in that your disks should already be clean at th= is=20 point, etc. You can try this hack to see if it fixes it: Index: vm_machdep.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/cvs/src/sys/i386/i386/vm_machdep.c,v retrieving revision 1.267 diff -u -r1.267 vm_machdep.c =2D-- vm_machdep.c 14 Nov 2005 00:43:44 -0000 1.267 +++ vm_machdep.c 23 Jan 2006 20:49:21 -0000 @@ -533,6 +533,7 @@ ; /* Wait for other cpu to see that we've started */ stop_cpus((1< <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 21:23:31 2006 Return-Path: X-Original-To: freebsd-current@www.freebsd.org Delivered-To: freebsd-current@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8617116A420 for ; Mon, 23 Jan 2006 21:23:31 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail13.syd.optusnet.com.au (mail13.syd.optusnet.com.au [211.29.132.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1CB044586 for ; Mon, 23 Jan 2006 21:23:30 +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 mail13.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k0NLNM51015259 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 24 Jan 2006 08:23:23 +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 k0NLNMHh037350; Tue, 24 Jan 2006 08:23:22 +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 k0NLNMV0037349; Tue, 24 Jan 2006 08:23:22 +1100 (EST) (envelope-from pjeremy) Date: Tue, 24 Jan 2006 08:23:22 +1100 From: Peter Jeremy To: Goran Gajic Message-ID: <20060123212322.GM25397@cirb503493.alcatel.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-current@www.freebsd.org Subject: Re: olvwm crash 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, 23 Jan 2006 21:23:31 -0000 On Mon, 2006-Jan-23 21:34:47 +0100, Goran Gajic wrote: >It seems like change to malloc also causes olvwm to crash on amd64 >(7.0-CURRENT): ,,, >Program received signal SIGSEGV, Segmentation fault. >MakeOpenButton (dpy=0x802ffc550, scrInfo=0x802fef0e0) at images.c:739 >739 *b = openButton; You might like to have a look at the current value of 'b' and how it was initialised. The most likely problem is that is has been truncated to an 'int' at some time since is was allocated (possibly due to a missing function prototype). -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 21:23:47 2006 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 4544316A420; Mon, 23 Jan 2006 21:23:47 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id A77F5445CA; Mon, 23 Jan 2006 21:23: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 6791610 for multiple; Mon, 23 Jan 2006 16:24:53 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k0NLNhrw003516; Mon, 23 Jan 2006 16:23:43 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 23 Jan 2006 16:24:12 -0500 User-Agent: KMail/1.9.1 References: <20060123112629.F79825@teapot.cbhnet> <20060123140937.Q81165@teapot.cbhnet> In-Reply-To: <20060123140937.Q81165@teapot.cbhnet> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601231624.14321.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1247/Sat Jan 21 05:24:51 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: current@freebsd.org, Chris Hedley Subject: Re: -CURRENT spontaneously rebooting when using X X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 21:23:47 -0000 On Monday 23 January 2006 09:13, Chris Hedley wrote: > On Mon, 23 Jan 2006, Chris Hedley wrote: > > Could someone advise how I can get a bit more information to report? :) > > > > I've just installed a fresh 6.0-RELEASE and immediately upgraded it to > > -CURRENT (most recent yesterday evening) and installed the latest xorg > > servers. When I start X, usually within a few seconds to a couple of > > minutes the system falls over, but unfortauntely it doesn't leave me at > > the kernel debugger and doesn't do a kernel dump for some reason or > > other, it just goes > > ... > > Thanks to David Wolfskill for talking me through setting up a serial > console, I'm able to extract some debugging information from my system > now. Some initial bits (retyped by me, hopefully not too many mistakes) > follow: > > kernel trap 12 with interrupts disabled > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x48 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xffffffff802b14fa > stack pointer = 0x10:0xffffffffa263b9d0 > frame pointer = 0x10:0xffffffffa263ba10 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = resume, IOPL = 0 > current process = 38 (syncer) > [thread pid 38 tid 100042 ] > Stopped at propagate_priority+0x6a movq 0x48(%r15),%rbx > > Tracing pid 38 tid 100042 td 0xffffff003db4a000 > propagate_priority() at propagate_priority+0x6a > turnstile_wait() at turnstile_wait+0x20e > _mtx_lock_sleep() at _mtx_lock_sleep+0x89 > vfs_busy_pages() at vfs_busy_pages+0xd4 > bufwrite() at burwrite+0x7b > vfs_bio_awrite() at vfs_bio_awrite+0x5a > vop_stdfsync() at vop_stdfsync+0x28c > VOP_FSYNC_APV() at VOP_FSYNC+APV+0x3d > sched_sync() at sched_sync+0x415 > fork_exit() at fork_exit+0x86 > form_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffffffa263bd40, rbp = 0 --- > > Is there anything else that might be useful in tracking down this problem? > If it's anything that's very involved I may need to be pointed at an > instruction manual! It's a bug, but you can try this workaround: Index: kern/subr_turnstile.c =================================================================== RCS file: /usr/cvs/src/sys/kern/subr_turnstile.c,v retrieving revision 1.155 diff -u -r1.155 subr_turnstile.c --- kern/subr_turnstile.c 17 Jan 2006 16:47:42 -0000 1.155 +++ kern/subr_turnstile.c 23 Jan 2006 21:23:42 -0000 @@ -228,6 +228,13 @@ ts->ts_lockobj->lo_name)); /* + * Add a safety net for production kernels (non-INVARIANTS). + * If the thread isn't blocked on a lock, just bail. + */ + if (!TD_ON_LOCK(td)) + return; + + /* * Pick up the lock that td is blocked on. */ ts = td->td_blocked; -- 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 Jan 23 21:23:47 2006 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 4544316A420; Mon, 23 Jan 2006 21:23:47 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id A77F5445CA; Mon, 23 Jan 2006 21:23: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 6791610 for multiple; Mon, 23 Jan 2006 16:24:53 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k0NLNhrw003516; Mon, 23 Jan 2006 16:23:43 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 23 Jan 2006 16:24:12 -0500 User-Agent: KMail/1.9.1 References: <20060123112629.F79825@teapot.cbhnet> <20060123140937.Q81165@teapot.cbhnet> In-Reply-To: <20060123140937.Q81165@teapot.cbhnet> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601231624.14321.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1247/Sat Jan 21 05:24:51 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: current@freebsd.org, Chris Hedley Subject: Re: -CURRENT spontaneously rebooting when using X X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 21:23:47 -0000 On Monday 23 January 2006 09:13, Chris Hedley wrote: > On Mon, 23 Jan 2006, Chris Hedley wrote: > > Could someone advise how I can get a bit more information to report? :) > > > > I've just installed a fresh 6.0-RELEASE and immediately upgraded it to > > -CURRENT (most recent yesterday evening) and installed the latest xorg > > servers. When I start X, usually within a few seconds to a couple of > > minutes the system falls over, but unfortauntely it doesn't leave me at > > the kernel debugger and doesn't do a kernel dump for some reason or > > other, it just goes > > ... > > Thanks to David Wolfskill for talking me through setting up a serial > console, I'm able to extract some debugging information from my system > now. Some initial bits (retyped by me, hopefully not too many mistakes) > follow: > > kernel trap 12 with interrupts disabled > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x48 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xffffffff802b14fa > stack pointer = 0x10:0xffffffffa263b9d0 > frame pointer = 0x10:0xffffffffa263ba10 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = resume, IOPL = 0 > current process = 38 (syncer) > [thread pid 38 tid 100042 ] > Stopped at propagate_priority+0x6a movq 0x48(%r15),%rbx > > Tracing pid 38 tid 100042 td 0xffffff003db4a000 > propagate_priority() at propagate_priority+0x6a > turnstile_wait() at turnstile_wait+0x20e > _mtx_lock_sleep() at _mtx_lock_sleep+0x89 > vfs_busy_pages() at vfs_busy_pages+0xd4 > bufwrite() at burwrite+0x7b > vfs_bio_awrite() at vfs_bio_awrite+0x5a > vop_stdfsync() at vop_stdfsync+0x28c > VOP_FSYNC_APV() at VOP_FSYNC+APV+0x3d > sched_sync() at sched_sync+0x415 > fork_exit() at fork_exit+0x86 > form_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffffffa263bd40, rbp = 0 --- > > Is there anything else that might be useful in tracking down this problem? > If it's anything that's very involved I may need to be pointed at an > instruction manual! It's a bug, but you can try this workaround: Index: kern/subr_turnstile.c =================================================================== RCS file: /usr/cvs/src/sys/kern/subr_turnstile.c,v retrieving revision 1.155 diff -u -r1.155 subr_turnstile.c --- kern/subr_turnstile.c 17 Jan 2006 16:47:42 -0000 1.155 +++ kern/subr_turnstile.c 23 Jan 2006 21:23:42 -0000 @@ -228,6 +228,13 @@ ts->ts_lockobj->lo_name)); /* + * Add a safety net for production kernels (non-INVARIANTS). + * If the thread isn't blocked on a lock, just bail. + */ + if (!TD_ON_LOCK(td)) + return; + + /* * Pick up the lock that td is blocked on. */ ts = td->td_blocked; -- 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 Jan 23 21:27:28 2006 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 99D5716A41F for ; Mon, 23 Jan 2006 21:27:28 +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 B71FC445C8 for ; Mon, 23 Jan 2006 21:27:26 +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 k0NLROPC023955 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 24 Jan 2006 08:27:24 +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 k0NLRNHh037364; Tue, 24 Jan 2006 08:27:23 +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 k0NLRNlD037363; Tue, 24 Jan 2006 08:27:23 +1100 (EST) (envelope-from pjeremy) Date: Tue, 24 Jan 2006 08:27:23 +1100 From: Peter Jeremy To: Thierry Herbelot Message-ID: <20060123212723.GN25397@cirb503493.alcatel.com.au> References: <200601232041.19159.thierry@herbelot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200601232041.19159.thierry@herbelot.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: current@freebsd.org Subject: Re: softdep panic at reboot (and restart) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 21:27:28 -0000 On Mon, 2006-Jan-23 20:41:17 +0100, Thierry Herbelot wrote: >panic: vm_page_free_toq: freeing mapped page 0xc11fae58 Sam Leffler has suggested that Alan Cox's latest sys/kern/vfs_bio.c change is at fault here. You could try backing out v1.502 and see if the problem goes away. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 21:34:01 2006 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 F3BCC16A485 for ; Mon, 23 Jan 2006 21:33:58 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail08.syd.optusnet.com.au (mail08.syd.optusnet.com.au [211.29.132.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EDD543F7D for ; Mon, 23 Jan 2006 21:05:09 +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 mail08.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k0NL58U8001754 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 24 Jan 2006 08:05:08 +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 k0NL57Hh037305; Tue, 24 Jan 2006 08:05:07 +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 k0NL57Aj037304; Tue, 24 Jan 2006 08:05:07 +1100 (EST) (envelope-from pjeremy) Date: Tue, 24 Jan 2006 08:05:07 +1100 From: Peter Jeremy To: Alex Burke Message-ID: <20060123210507.GK25397@cirb503493.alcatel.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: FreeBSD CURRENT Subject: Re: Swap_pager and modified after free console messages X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 21:34:02 -0000 On Mon, 2006-Jan-23 19:14:43 +0000, Alex Burke wrote: [I can't help with point 1] >2) a swap_pager message about not being able to allocate any more space. > >My /usr filesystem was full (except for the last 8% reserved for root >only), and I had been doing some heavy ports tree compiling. I am just >not sure if that message is normal and that swap was REALLY 100% used >up, or whether it was indicative of something else and I should try to >replicate the issue. Unless you have a fairly unusual setup (swapping into a file in /usr), /usr being full has nothing to do with swap being full. You can check swap usage with "swapinfo". There's no simple way to identify how much swap space is being used by each process but VSZ reported by 'ps -axl' might suggest the culprit(s) - a few excessively large processes or an excessive number of small ones. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 21:34:03 2006 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 6001A16A4C1 for ; Mon, 23 Jan 2006 21:34:02 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DB5A44538 for ; Mon, 23 Jan 2006 21:17:08 +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 6791217 for multiple; Mon, 23 Jan 2006 16:18:16 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k0NLH2cd003463; Mon, 23 Jan 2006 16:17:07 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 23 Jan 2006 16:18:03 -0500 User-Agent: KMail/1.9.1 References: <20060121070706.GA32444@cirb503493.alcatel.com.au> In-Reply-To: <20060121070706.GA32444@cirb503493.alcatel.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601231618.04949.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1247/Sat Jan 21 05:24:51 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Peter Jeremy Subject: Re: Panic due to deleting devices twice X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 21:34:04 -0000 On Saturday 21 January 2006 02:07, Peter Jeremy wrote: > When deleting a device (using device_delete_child()), all its child > devices are recursively deleted and then device_detach() is called. > > In the case of iicsmb, this causes a panic because iicsmb_detach() > also calls device_delete_child() on the smbus child it has cached in > its softc. By this time that child has been destroyed. > > Looking at device_detach(), it appears that the solution is to create > a bus_child_detached method to inform the parent that a child is being > destroyed so it can invalidate cached pointers to that child. In > practice, there are only 5 bus_child_detached methods (isa, ed, > pccard, cbb and usb), though there are far more device types attached > as children. > > Looking at the iicsmb code, it appears that iicbb and iicsmb both > cache and explicitly delete child devices and therefore both need > bus_child_detached methods. Is this correct? Is there a simpler > alternative? Can they just call bus_generic_detach() instead and not call device_delete_child()? -- 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 Jan 23 21:34:04 2006 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 63A4216A496 for ; Mon, 23 Jan 2006 21:34:02 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DCD8445AD for ; Mon, 23 Jan 2006 21:17:08 +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 6791216 for multiple; Mon, 23 Jan 2006 16:18:16 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k0NLH2cc003463; Mon, 23 Jan 2006 16:17:02 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 23 Jan 2006 16:16:47 -0500 User-Agent: KMail/1.9.1 References: <43D05151.5070409@elischer.org> In-Reply-To: <43D05151.5070409@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601231616.49140.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1247/Sat Jan 21 05:24:51 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Julian Elischer Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 21:34:04 -0000 On Thursday 19 January 2006 21:56, Julian Elischer wrote: > some progrsss.. > as the first few lines show, it's not quite perfect yet but it's most of > the way there.. > (Like proc 1 isn't init) One other note, watch out for the AIO daemons. They have to be kernel procs and not kthreads because they borrow the vmspace of the user process when performing AIO on another process' behalf. -- 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 Jan 23 21:34:13 2006 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 DB95C16A51F for ; Mon, 23 Jan 2006 21:34:04 +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 9F46C4459F for ; Mon, 23 Jan 2006 21:16:58 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (9en8hf0ps675kpep@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id k0NLFuOQ075777; Mon, 23 Jan 2006 13:15:56 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id k0NLFtOl075776; Mon, 23 Jan 2006 13:15:55 -0800 (PST) (envelope-from jmg) Date: Mon, 23 Jan 2006 13:15:55 -0800 From: John-Mark Gurney To: Alex Burke Message-ID: <20060123211555.GA69162@funkthat.com> Mail-Followup-To: Alex Burke , FreeBSD CURRENT References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i 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: FreeBSD CURRENT Subject: Re: Swap_pager and modified after free console messages 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: Mon, 23 Jan 2006 21:34:13 -0000 Alex Burke wrote this message on Mon, Jan 23, 2006 at 19:14 +0000: > This is what I have seen over the past few days: > 1) kernel: memoery modified after free and then what appears to be a > memory address complete kernel message is necessary... there is other info than just kernel address in that message... > I saw another post mentioning a console message like this that > appeared to be related to the subsequent panic, but mine hasnt caused > the machine to panic. I am not sure if this is because I have the > standard -CURRENT GENERIC kernel running (with WITNESS, INVARIANTS > still enabled), but a reply said use memgaurd to track down the issue. > How should I configure this? memguard(9) -- 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 Mon Jan 23 21:34:39 2006 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 DE11716A5F8 for ; Mon, 23 Jan 2006 21:34:12 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from pinus.cc.fer.hr (pinus.cc.fer.hr [161.53.73.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC43043EE0 for ; Mon, 23 Jan 2006 21:03:50 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [161.53.72.113] (lara.cc.fer.hr [161.53.72.113]) by pinus.cc.fer.hr (8.12.2/8.12.2) with ESMTP id k0NL3hFx012738; Mon, 23 Jan 2006 22:03:44 +0100 (MET) Message-ID: <43D5449D.6050001@fer.hr> Date: Mon, 23 Jan 2006 22:03:25 +0100 From: Ivan Voras User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050921) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <14054.1138044116@critter.freebsd.dk> In-Reply-To: <14054.1138044116@critter.freebsd.dk> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: Speeding up cpu-time accounting (rerun) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 21:34:39 -0000 Poul-Henning Kamp wrote: > http://www.freebsd.org/cgi/getmsg.cgi?fetch=239010+242520+/usr/local/www/db/text/2005/freebsd-current/20051204.freebsd-current > > I can't really say I have gotten much feedback on this. You have my results, but here's an addition: it was ultimately unstable. I applied it mostly cleanly on RELENG-6, but I've had spontaneus reboots until I reverted to normal kernel. The reboots were very random and sporadic - about once every few days or so (always under X11, in case it's important). I have KDB and dumps configured but to no use. From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 21:41:57 2006 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 3730216A41F; Mon, 23 Jan 2006 21:41:57 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail21.syd.optusnet.com.au (mail21.syd.optusnet.com.au [211.29.133.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4022043D7B; Mon, 23 Jan 2006 21:41:53 +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 mail21.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k0NLfpcE004033 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 24 Jan 2006 08:41:52 +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 k0NLfpHh037393; Tue, 24 Jan 2006 08:41:51 +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 k0NLfpw6037392; Tue, 24 Jan 2006 08:41:51 +1100 (EST) (envelope-from pjeremy) Date: Tue, 24 Jan 2006 08:41:51 +1100 From: Peter Jeremy To: John Baldwin Message-ID: <20060123214151.GO25397@cirb503493.alcatel.com.au> References: <20060121070706.GA32444@cirb503493.alcatel.com.au> <200601231618.04949.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200601231618.04949.jhb@freebsd.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-current@freebsd.org Subject: Re: Panic due to deleting devices twice X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 21:41:57 -0000 On Mon, 2006-Jan-23 16:18:03 -0500, John Baldwin wrote: >On Saturday 21 January 2006 02:07, Peter Jeremy wrote: >> Looking at the iicsmb code, it appears that iicbb and iicsmb both >> cache and explicitly delete child devices and therefore both need >> bus_child_detached methods. Is this correct? Is there a simpler >> alternative? > >Can they just call bus_generic_detach() instead and not call >device_delete_child()? The existing code does both: static int iicbb_detach(device_t dev) { struct iicbb_softc *sc = (struct iicbb_softc *)device_get_softc(dev); if (sc->iicbus) { bus_generic_detach(dev); device_delete_child(dev, sc->iicbus); } return (0); } static int iicsmb_detach(device_t dev) { struct iicsmb_softc *sc = (struct iicsmb_softc *)device_get_softc(dev); bus_generic_detach(dev); if (sc->smbus) { device_delete_child(dev, sc->smbus); } return (0); } Maybe a better solution in both cases is to just map device_detach to bus_generic_detach() - in which case my patch in kern/92092 is overly baroque. I was hoping that someone might shed some insight into why it was done that way in the first case. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 21:59:26 2006 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 44ADC16A41F for ; Mon, 23 Jan 2006 21:59:26 +0000 (GMT) (envelope-from reuf_m@hotmail.com) Received: from obelix.sunrise.ch (mailrelay3.sunrise.ch [194.158.229.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E20C43D48 for ; Mon, 23 Jan 2006 21:59:24 +0000 (GMT) (envelope-from reuf_m@hotmail.com) Received: from localhost (adsl-62-167-45-126.adslplus.ch [62.167.45.126]) by obelix.sunrise.ch (8.12.10/8.12.10) with ESMTP id k0NLxMF3005623 for ; Mon, 23 Jan 2006 22:59:22 +0100 Date: Mon, 23 Jan 2006 22:59:20 +0100 To: current@freebsd.org References: <14054.1138044116@critter.freebsd.dk> From: reuf_m@hotmail.com Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <14054.1138044116@critter.freebsd.dk> User-Agent: Opera M2/8.51 (FreeBSD, build 1462) Cc: Subject: Re: Speeding up cpu-time accounting (rerun) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 21:59:26 -0000 --------------------- WITHOUT patch ! --------------------- BYTE UNIX Benchmarks (Version 4.1.0) System -- amd64.home.org Start Benchmark Run: Mon Jan 23 20:42:46 CET 2006 1 interactive users. 8:42PM up 10:52, 0 users, load averages: 0.09, 0.32, 0.22 -r-xr-xr-x 1 root wheel 110016 Jan 16 04:14 /bin/sh /bin/sh: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked (uses shared libs), stripped /dev/ad4s1f 30462636 9590954 18434672 34% /usr Pipe-based Context Switching 74486.6 lps (10.0 secs, 10 samples) INDEX VALUES TEST BASELINE RESULT INDEX Pipe-based Context Switching 4000.0 74486.6 186.2 ========= FINAL SCORE 186.2 ----------------- WITH patch ------------------ BYTE UNIX Benchmarks (Version 4.1.0) System -- amd64.home.org Start Benchmark Run: Mon Jan 23 21:39:20 CET 2006 1 interactive users. 9:39PM up 2 mins, 0 users, load averages: 0.48, 0.34, 0.15 -r-xr-xr-x 1 root wheel 110016 Jan 16 04:14 /bin/sh /bin/sh: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked (uses shared libs), stripped /dev/ad4s1f 30462636 9676890 18348736 35% /usr Pipe-based Context Switching 228917.1 lps (10.0 secs, 10 samples) INDEX VALUES TEST BASELINE RESULT INDEX Pipe-based Context Switching 4000.0 228917.1 572.3 ========= FINAL SCORE 572.3 =================================================================== /var/log/messages after booting: ..... calcru: runtime went backwards from 8196122686 usec to 812 usec for pid 700 (usbd) calcru: runtime went backwards from 4520 usec to 3819 usec for pid 56 (vnlru) calcru: runtime went backwards from 5953 usec to 5372 usec for pid 54 (bufdaemon) calcru: runtime went backwards from 8196122686 usec to 812 usec for pid 700 (usbd) calcru: runtime went backwards from 4520 usec to 3819 usec for pid 56 (vnlru) calcru: runtime went backwards from 5953 usec to 5372 usec for pid 54 (bufdaemon) calcru: runtime went backwards from 594140172 usec to 594139363 usec for pid 11 (idle: cpu1) calcru: runtime went backwards from 8196122686 usec to 812 usec for pid 700 (usbd) ...... #pciconf -vl none0@pci0:0:0: class=0x058000 card=0x00000000 chip=0x005e10de rev=0xa3 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce4 Memory Controller' class = memory isab0@pci0:1:0: class=0x060100 card=0xcb8410de chip=0x005010de rev=0xa3 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce4 PCI to ISA Bridge' class = bridge subclass = PCI-ISA none1@pci0:1:1: class=0x0c0500 card=0xcb8410de chip=0x005210de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce4 SMBus' class = serial bus subclass = SMBus ohci0@pci0:2:0: class=0x0c0310 card=0xcb8410de chip=0x005a10de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce4 USB Controller' class = serial bus subclass = USB ehci0@pci0:2:1: class=0x0c0320 card=0xcb8410de chip=0x005b10de rev=0xa3 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce4 USB 2.0 Controller' class = serial bus subclass = USB pcm0@pci0:4:0: class=0x040100 card=0xcb8410de chip=0x005910de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce4 AC'97 Audio Controller' class = multimedia subclass = audio atapci0@pci0:6:0: class=0x01018a card=0xcb8410de chip=0x005310de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce4 Parallel ATA Controller' class = mass storage subclass = ATA atapci1@pci0:7:0: class=0x010185 card=0xcb8410de chip=0x005410de rev=0xa3 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce4 Serial ATA Controller' class = mass storage subclass = ATA atapci2@pci0:8:0: class=0x010185 card=0xcb8410de chip=0x005510de rev=0xa3 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce4 Serial ATA Controller' class = mass storage subclass = ATA pcib1@pci0:9:0: class=0x060401 card=0x00000000 chip=0x005c10de rev=0xa2 hdr=0x01 vendor = 'NVIDIA Corporation' device = 'nForce4 PCI Bridge' class = bridge subclass = PCI-PCI nve0@pci0:10:0: class=0x068000 card=0xcb8410de chip=0x005710de rev=0xa3 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce4 Ethernet Controller' class = bridge pcib2@pci0:11:0: class=0x060400 card=0x00000040 chip=0x005d10de rev=0xa3 hdr=0x01 vendor = 'NVIDIA Corporation' device = 'nForce4 PCI Express Bridge' class = bridge subclass = PCI-PCI pcib3@pci0:12:0: class=0x060400 card=0x00000040 chip=0x005d10de rev=0xa3 hdr=0x01 vendor = 'NVIDIA Corporation' device = 'nForce4 PCI Express Bridge' class = bridge subclass = PCI-PCI pcib4@pci0:13:0: class=0x060400 card=0x00000040 chip=0x005d10de rev=0xa3 hdr=0x01 vendor = 'NVIDIA Corporation' device = 'nForce4 PCI Express Bridge' class = bridge subclass = PCI-PCI pcib5@pci0:14:0: class=0x060400 card=0x00000040 chip=0x005d10de rev=0xa3 hdr=0x01 vendor = 'NVIDIA Corporation' device = 'nForce4 PCI Express Bridge' class = bridge subclass = PCI-PCI hostb0@pci0:24:0: class=0x060000 card=0x00000000 chip=0x11001022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron HyperTransport Technology Configuration' class = bridge subclass = HOST-PCI hostb1@pci0:24:1: class=0x060000 card=0x00000000 chip=0x11011022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron Address Map' class = bridge subclass = HOST-PCI hostb2@pci0:24:2: class=0x060000 card=0x00000000 chip=0x11021022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron DRAM Controller' class = bridge subclass = HOST-PCI hostb3@pci0:24:3: class=0x060000 card=0x00000000 chip=0x11031022 rev=0x00 hdr=0x00 vendor = 'Advanced Micro Devices (AMD)' device = 'Athlon 64 / Opteron Miscellaneous Control' class = bridge subclass = HOST-PCI skc0@pci1:10:0: class=0x020000 card=0x100a15bd chip=0x432011ab rev=0x13 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = '88E8001/8003/8010 Gigabit Ethernet Controller with Integrated PHY (copper)' class = network subclass = ethernet nvidia0@pci5:0:0: class=0x030000 card=0x0000196d chip=0x014110de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'NV43 NVIDIA GeForce 6600' class = display subclass = VGA #dmesg FreeBSD 6.0-STABLE #0: Mon Jan 23 20:52:14 CET 2006 reuf@amd64.home.org:/usr/obj/usr/src/sys/OPTERON Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Dual Core AMD Opteron(tm) Processor 165 (2250.67-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x20f32 Stepping = 2 Features=0x178bfbff Features2=0x1 AMD Features=0xe2500800,LM,3DNow+,3DNow> real memory = 535691264 (510 MB) avail memory = 510484480 (486 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.0 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xfe02f000-0xfe02ffff irq 21 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 10 ports with 10 removable, self powered ehci0: mem 0xfeb00000-0xfeb000ff irq 22 at device 2.1 on pci0 ehci0: [GIANT-LOCKED] usb1: waiting for BIOS to give up control usb1: timed out waiting for BIOS usb1: EHCI version 1.0 usb1: companion controller, 4 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub1: 10 ports with 10 removable, self powered umass0: ICSI USB2.0 Card Reader, rev 2.00/1.6b, addr 2 pcm0: port 0xf000-0xf0ff,0xec00-0xecff mem 0xfe02d000-0xfe02dfff irq 23 at device 4.0 on pci0 pcm0: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe800-0xe80f at device 6.0 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd400-0xd40f mem 0xfe02c000-0xfe02cfff irq 21 at device 7 .0 on pci0 ata2: on atapci1 ata3: on atapci1 atapci2: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc000-0xc00f mem 0xfe02b000-0xfe02bfff irq 22 at device 8 .0 on pci0 ata4: on atapci2 ata5: on atapci2 pcib1: at device 9.0 on pci0 pci1: on pcib1 skc0: port 0xac00-0xacff mem 0xfdefc000-0xfdefffff irq 18 at device 10.0 on pci1 skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) sk0: on skc0 sk0: Ethernet address: 00:01:29:d2:a2:62 miibus0: on sk0 e1000phy0: on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto nve0: port 0xbc00-0xbc07 mem 0xfe02a000-0xfe02afff irq 23 at device 10.0 on pci0 nve0: Ethernet address 00:01:29:d2:a2:cb miibus1: on nve0 ciphy0: on miibus1 ciphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto nve0: Ethernet address: 00:01:29:d2:a2:cb pcib2: at device 11.0 on pci0 pci2: on pcib2 pcib3: at device 12.0 on pci0 pci3: on pcib3 pcib4: at device 13.0 on pci0 pci4: on pcib4 pcib5: at device 14.0 on pci0 pci5: on pcib5 nvidia0: mem 0xf4000000-0xf7ffffff,0xd0000000-0xdfffffff,0xfa000000-0xfaffffff irq 18 at device 0.0 on pci5 nvidia0: [GIANT-LOCKED] acpi_tz0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 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-0xcefff 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 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] ppc0: parallel port not found. sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ucom0: FTDI USB <-> Serial, rev 1.10/2.00, addr 2 uhub2: vendor 0x0451 General Purpose USB Hub, class 9/0, rev 1.10/1.01, addr 3 uhub2: 2 ports with 1 removable, bus powered ukbd0: Logitech USB Receiver, rev 1.10/22.40, addr 4, iclass 3/1 kbd2 at ukbd0 ums0: Logitech USB Receiver, rev 1.10/22.40, addr 4, iclass 3/1 ums0: 7 buttons and Z dir. Timecounters tick every 1.000 msec acd0: DVDR at ata0-master UDMA33 acd1: DVDR at ata0-slave UDMA66 ad4: 70910MB at ata2-master SATA150 ad6: 152627MB at ata3-master SATA150 cd0 at ata0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [22358 x 2048 byte records] SMP: AP CPU #1 Launched! cd1 at ata0 bus 0 target 1 lun 0 cd1: Removable CD-ROM SCSI-0 device cd1: 66.000MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present - tray closed da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 122MB (250368 512 byte sectors: 64H 32S/T 122C) (da1:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 (da1:umass-sim0:0:0:1): ILLEGAL REQUEST asc:25,0 (da1:umass-sim0:0:0:1): Logical unit not supported (da1:umass-sim0:0:0:1): fatal error, failed to attach to device (da1:umass-sim0:0:0:1): lost device (da1:umass-sim0:0:0:1): removing device entry (da2:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 0 0 0 (da2:umass-sim0:0:0:2): ILLEGAL REQUEST asc:25,0 (da2:umass-sim0:0:0:2): Logical unit not supported (da2:umass-sim0:0:0:2): fatal error, failed to attach to device (da2:umass-sim0:0:0:2): lost device (da2:umass-sim0:0:0:2): removing device entry da3 at umass-sim0 bus 0 target 0 lun 3 da3: Removable Direct Access SCSI-0 device da3: 40.000MB/s transfers da3: 15MB (32000 512 byte sectors: 64H 32S/T 15C) uhid0: Logitech Desktop USB stand, rev 1.10/41.02, addr 5, iclass 3/0 Trying to mount root from ufs:/dev/ad4s1a On Mon, 23 Jan 2006 20:21:56 +0100, Poul-Henning Kamp wrote: > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=239010+242520+/usr/local/www/db/text/2005/freebsd-current/20051204.freebsd-current > > I can't really say I have gotten much feedback on this. > > Given that there may be 2-10% speedup of context-switches in it > I would have expected more interest ? > From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 22:19:46 2006 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 2383516A41F for ; Mon, 23 Jan 2006 22:19:46 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from pinus.cc.fer.hr (pinus.cc.fer.hr [161.53.73.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72E9043D4C for ; Mon, 23 Jan 2006 22:19:45 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [161.53.72.113] (lara.cc.fer.hr [161.53.72.113]) by pinus.cc.fer.hr (8.12.2/8.12.2) with ESMTP id k0NMJcFx019050 for ; Mon, 23 Jan 2006 23:19:39 +0100 (MET) Message-ID: <43D55668.4050408@fer.hr> Date: Mon, 23 Jan 2006 23:19:20 +0100 From: Ivan Voras User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050921) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org References: <14054.1138044116@critter.freebsd.dk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Speeding up cpu-time accounting (rerun) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 22:19:46 -0000 reuf_m@hotmail.com wrote: > calcru: runtime went backwards from 8196122686 usec to 812 usec for pid > 700 (usbd) > calcru: runtime went backwards from 4520 usec to 3819 usec for pid 56 > (vnlru) Just want to also confirm this - I had it on my machine also, and it's a single processor Athlon64 running as i386. From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 22:22:50 2006 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 1BDB816A41F; Mon, 23 Jan 2006 22:22:50 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id D33FF43D48; Mon, 23 Jan 2006 22:22:49 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.17.229]) ([10.251.17.229]) by a50.ironport.com with ESMTP; 23 Jan 2006 14:22:49 -0800 X-IronPort-Anti-Spam-Filtered: true Message-ID: <43D55739.80608@elischer.org> Date: Mon, 23 Jan 2006 14:22:49 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <43D05151.5070409@elischer.org> <200601231616.49140.jhb@freebsd.org> In-Reply-To: <200601231616.49140.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 22:22:50 -0000 John Baldwin wrote: >On Thursday 19 January 2006 21:56, Julian Elischer wrote: > > >>some progrsss.. >>as the first few lines show, it's not quite perfect yet but it's most of >>the way there.. >>(Like proc 1 isn't init) >> >> > >One other note, watch out for the AIO daemons. They have to be kernel procs >and not kthreads because they borrow the vmspace of the user process when >performing AIO on another process' behalf. > > > yeah I found that and the patches account for that. However I would like to suggest that we change the way that aio works.. My suggestion is that when a process does AIO, that we "fork a ksegroup" and attach it to the process, and assign it a (or some) worker thread to do the aio work. The userland process would be oblivious of the extra (kernel) threads in that kseg and they would be independently schedulable. They would however automatically have full access to the correct address space. From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 22:45:47 2006 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 27A0E16A41F; Mon, 23 Jan 2006 22:45:47 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFEB544330; Mon, 23 Jan 2006 22:45:46 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.17.229]) ([10.251.17.229]) by a50.ironport.com with ESMTP; 23 Jan 2006 14:45:46 -0800 X-IronPort-Anti-Spam-Filtered: true Message-ID: <43D55C9A.9010801@elischer.org> Date: Mon, 23 Jan 2006 14:45:46 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <43D05151.5070409@elischer.org> <200601231616.49140.jhb@freebsd.org> <43D55739.80608@elischer.org> <200601231739.02247.jhb@freebsd.org> In-Reply-To: <200601231739.02247.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 22:45:47 -0000 John Baldwin wrote: >On Monday 23 January 2006 17:22, Julian Elischer wrote: > > >>John Baldwin wrote: >> >> >>>On Thursday 19 January 2006 21:56, Julian Elischer wrote: >>> >>> >>>>some progrsss.. >>>>as the first few lines show, it's not quite perfect yet but it's most of >>>>the way there.. >>>>(Like proc 1 isn't init) >>>> >>>> >>>One other note, watch out for the AIO daemons. They have to be kernel >>>procs and not kthreads because they borrow the vmspace of the user >>>process when performing AIO on another process' behalf. >>> >>> >>yeah I found that and the patches account for that. >> >>However I would like to suggest that we change the way that aio works.. >> >>My suggestion is that when a process does AIO, that we "fork a ksegroup" >>and attach it to the >>process, and assign it a (or some) worker thread to do the aio work. >>The userland process would >>be oblivious of the extra (kernel) threads in that kseg and they would >>be independently schedulable. >>They would however automatically have full access to the correct address >>space. >> >> > >That's probably a better model, yes. One thing I would prefer though is if we >could limit the knowledge of ksegroups to the scheduler as much as possible >and let the rest of the kernel just deal with threads and processes. >Ideally, we'd reach the point where you have an API to say "create a thread >for process p" and kthreads just use a kernel process for 'p' and maybe the >API takes a flag to say if a thread is separate or not. Really, aio should >probably just be separate system scope threads, and you could almost do that >in userland now. > > the aim of ksegroups is simply as containers sothat you can group threads from a scheduler perspective. The kernel threads code I have in the patch automatically creates system sscope threads by associating them each with a separate kseg (ksegs are small) however it might by fairer to group multiple aio threads into a single ksegrp so that you don't flood the system if you make a lot of them.. of course that brings up teh question as to whether a process doing AIO would require just a single thread or a bunch if them.. (do you want a separate thread per aio request or to multiplex them?) multiplexing them saves resources (and may be more extensible) but having a single blocking thread per request would be really simple and easy to debug.... I guess the current multiplexeing code would work for multiplexed threads. you could just drop the vm futzing code. From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 22:49:20 2006 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 99FD716A41F; Mon, 23 Jan 2006 22:49:20 +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 EDAD244345; Mon, 23 Jan 2006 22:49:09 +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 3CD4E46B0C; Mon, 23 Jan 2006 17:49:03 -0500 (EST) Date: Mon, 23 Jan 2006 22:50:17 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Julian Elischer In-Reply-To: <43D55739.80608@elischer.org> Message-ID: <20060123224756.R48094@fledge.watson.org> References: <43D05151.5070409@elischer.org> <200601231616.49140.jhb@freebsd.org> <43D55739.80608@elischer.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 22:49:20 -0000 On Mon, 23 Jan 2006, Julian Elischer wrote: > John Baldwin wrote: > >> On Thursday 19 January 2006 21:56, Julian Elischer wrote: >> >>> some progrsss.. >>> as the first few lines show, it's not quite perfect yet but it's most of >>> the way there.. >>> (Like proc 1 isn't init) >> >> One other note, watch out for the AIO daemons. They have to be kernel >> procs and not kthreads because they borrow the vmspace of the user process >> when performing AIO on another process' behalf. >> > yeah I found that and the patches account for that. > > However I would like to suggest that we change the way that aio works.. > > My suggestion is that when a process does AIO, that we "fork a ksegroup" and > attach it to the process, and assign it a (or some) worker thread to do the > aio work. The userland process would be oblivious of the extra (kernel) > threads in that kseg and they would be independently schedulable. They would > however automatically have full access to the correct address space. While I think that, in principle, this is the right thing to do, I'm a bit worried about doing it in practice. One of the things I like about the current aio code is the degree to which the the aio daemon processes are independent of the original requesting process -- we acquire references to vmspaces, creds, file descriptors, etc, but don't keep accessing the ones of the process. This means that if a process changes its uid, changes its threading, etc, while aio is running, aio is relatively unaffected. I worry that if we allow tighter integration of the two, we open up the door to security related race conditions. Also, we introduce concerns about the run-down when single-threading, exiting, execing, etc. Robert N M Watson From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 22:57:22 2006 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 3C52116A465 for ; Mon, 23 Jan 2006 22:57:22 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82BF144287 for ; Mon, 23 Jan 2006 22:38:24 +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 6795870 for multiple; Mon, 23 Jan 2006 17:39:24 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k0NMcBQb003976; Mon, 23 Jan 2006 17:38:12 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Julian Elischer Date: Mon, 23 Jan 2006 17:39:00 -0500 User-Agent: KMail/1.9.1 References: <43D05151.5070409@elischer.org> <200601231616.49140.jhb@freebsd.org> <43D55739.80608@elischer.org> In-Reply-To: <43D55739.80608@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601231739.02247.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1247/Sat Jan 21 05:24:51 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-current@freebsd.org Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 22:57:23 -0000 On Monday 23 January 2006 17:22, Julian Elischer wrote: > John Baldwin wrote: > >On Thursday 19 January 2006 21:56, Julian Elischer wrote: > >>some progrsss.. > >>as the first few lines show, it's not quite perfect yet but it's most of > >>the way there.. > >>(Like proc 1 isn't init) > > > >One other note, watch out for the AIO daemons. They have to be kernel > > procs and not kthreads because they borrow the vmspace of the user > > process when performing AIO on another process' behalf. > > yeah I found that and the patches account for that. > > However I would like to suggest that we change the way that aio works.. > > My suggestion is that when a process does AIO, that we "fork a ksegroup" > and attach it to the > process, and assign it a (or some) worker thread to do the aio work. > The userland process would > be oblivious of the extra (kernel) threads in that kseg and they would > be independently schedulable. > They would however automatically have full access to the correct address > space. That's probably a better model, yes. One thing I would prefer though is if we could limit the knowledge of ksegroups to the scheduler as much as possible and let the rest of the kernel just deal with threads and processes. Ideally, we'd reach the point where you have an API to say "create a thread for process p" and kthreads just use a kernel process for 'p' and maybe the API takes a flag to say if a thread is separate or not. Really, aio should probably just be separate system scope threads, and you could almost do that in userland now. -- 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 Jan 23 22:57:24 2006 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 D51FB16A4A9; Mon, 23 Jan 2006 22:57:23 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CA5F441EC; Mon, 23 Jan 2006 22:35:49 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 56B8B2087; Mon, 23 Jan 2006 23:35:42 +0100 (CET) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -3.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 3DE062086; Mon, 23 Jan 2006 23:35:42 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id 2212B33C1D; Mon, 23 Jan 2006 23:35:42 +0100 (CET) To: Julian Elischer References: <43D05151.5070409@elischer.org> <200601231616.49140.jhb@freebsd.org> <43D55739.80608@elischer.org> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Mon, 23 Jan 2006 23:35:42 +0100 In-Reply-To: <43D55739.80608@elischer.org> (Julian Elischer's message of "Mon, 23 Jan 2006 14:22:49 -0800") Message-ID: <86lkx6tvwh.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 22:57:24 -0000 Julian Elischer writes: > However I would like to suggest that we change the way that aio > works.. > > My suggestion is that when a process does AIO, that we "fork a > ksegroup" and attach it to the process, and assign it a (or some) > worker thread to do the aio work. The userland process would be > oblivious of the extra (kernel) threads in that kseg and they would > be independently schedulable. They would however automatically have > full access to the correct address space. Agreed. This would actually greatly simplify the aio code (getting rid of all the vm monkeying), and reduce the likelihood of future security or stability issues with it. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 22:57:53 2006 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 63BC916A614 for ; Mon, 23 Jan 2006 22:57:38 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D2D24427E for ; Mon, 23 Jan 2006 22:38:20 +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 6795869 for multiple; Mon, 23 Jan 2006 17:39:22 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k0NMcBQa003976; Mon, 23 Jan 2006 17:38:12 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Peter Jeremy Date: Mon, 23 Jan 2006 17:36:01 -0500 User-Agent: KMail/1.9.1 References: <20060121070706.GA32444@cirb503493.alcatel.com.au> <200601231618.04949.jhb@freebsd.org> <20060123214151.GO25397@cirb503493.alcatel.com.au> In-Reply-To: <20060123214151.GO25397@cirb503493.alcatel.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601231736.03028.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1247/Sat Jan 21 05:24:51 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-current@freebsd.org Subject: Re: Panic due to deleting devices twice X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 22:57:53 -0000 On Monday 23 January 2006 16:41, Peter Jeremy wrote: > On Mon, 2006-Jan-23 16:18:03 -0500, John Baldwin wrote: > >On Saturday 21 January 2006 02:07, Peter Jeremy wrote: > >> Looking at the iicsmb code, it appears that iicbb and iicsmb both > >> cache and explicitly delete child devices and therefore both need > >> bus_child_detached methods. Is this correct? Is there a simpler > >> alternative? > > > >Can they just call bus_generic_detach() instead and not call > >device_delete_child()? > > The existing code does both: > > static int iicbb_detach(device_t dev) > { > struct iicbb_softc *sc = (struct iicbb_softc > *)device_get_softc(dev); > > if (sc->iicbus) { > bus_generic_detach(dev); > device_delete_child(dev, sc->iicbus); > } > > return (0); > } > > static int > iicsmb_detach(device_t dev) > { > struct iicsmb_softc *sc = (struct iicsmb_softc > *)device_get_softc(dev); > > bus_generic_detach(dev); > if (sc->smbus) { > device_delete_child(dev, sc->smbus); > } > > return (0); > } > > Maybe a better solution in both cases is to just map device_detach to > bus_generic_detach() - in which case my patch in kern/92092 is overly > baroque. I was hoping that someone might shed some insight into why > it was done that way in the first case. Yeah, they should probably just use bus_generic_detach(), and they probably don't even need the smbus and iicbus pointers in their softc for that matter. Well, that might not be true. I think some of the drivers that use device_delete_child() only use the pointer to call that function, but some drivers use child devices to handle requests (smb comes to mind IIRC). If the drivers in question just use the device_t so they can call device_delete_child(), then I think you can axe the member from the softc and just use bus_generic_detach(). If they use the reference for other things, then the bus_device_detached route as in your patch in the PR is the way to go. This is assuming that this is a device whose parent will delete it when it is detached (this is true for many 'psuedo-bus' devices like smb). If a device isn't like that, then it may need to always use a bus_device_detached hook and call device_delete_child() conditionally in its detach routine. -- 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 Jan 23 23:19:06 2006 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 171D216A420; Mon, 23 Jan 2006 23:19:06 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id C53FC43D48; Mon, 23 Jan 2006 23:19:05 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.23.146]) ([10.251.23.146]) by a50.ironport.com with ESMTP; 23 Jan 2006 15:19:04 -0800 X-IronPort-Anti-Spam-Filtered: true Message-ID: <43D56468.1060101@elischer.org> Date: Mon, 23 Jan 2006 15:19:04 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: <43D05151.5070409@elischer.org> <200601231616.49140.jhb@freebsd.org> <43D55739.80608@elischer.org> <20060123224756.R48094@fledge.watson.org> In-Reply-To: <20060123224756.R48094@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 23:19:06 -0000 Robert Watson wrote: > > On Mon, 23 Jan 2006, Julian Elischer wrote: > >> John Baldwin wrote: >> >>> On Thursday 19 January 2006 21:56, Julian Elischer wrote: >>> >>>> some progrsss.. >>>> as the first few lines show, it's not quite perfect yet but it's >>>> most of >>>> the way there.. >>>> (Like proc 1 isn't init) >>> >>> >>> One other note, watch out for the AIO daemons. They have to be >>> kernel procs and not kthreads because they borrow the vmspace of the >>> user process when performing AIO on another process' behalf. >>> >> yeah I found that and the patches account for that. >> >> However I would like to suggest that we change the way that aio works.. >> >> My suggestion is that when a process does AIO, that we "fork a >> ksegroup" and attach it to the process, and assign it a (or some) >> worker thread to do the aio work. The userland process would be >> oblivious of the extra (kernel) threads in that kseg and they would >> be independently schedulable. They would however automatically have >> full access to the correct address space. > > > While I think that, in principle, this is the right thing to do, I'm a > bit worried about doing it in practice. One of the things I like > about the current aio code is the degree to which the the aio daemon > processes are independent of the original requesting process -- we > acquire references to vmspaces, creds, file descriptors, etc, but > don't keep accessing the ones of the process. One might consider this a bug :-) of course the creds would be held until the operation finishes, but there is a linit as to how separate an aio request from a process should be from that process. > This means that if a process changes its uid, changes its threading, > etc, while aio is running, aio is relatively unaffected. I worry that > if we allow tighter integration of the two, we open up the door to > security related race conditions. Also, we introduce concerns about > the run-down when single-threading, exiting, execing, etc. it would be no different from when a threaded process exits now.. With the current setup you have a whole set of worries about what to do about the thread responds when the process has already died. These worries are aqctually simplified if the thread is part of the process. (at least I believe this to be the case). > > 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" From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 23:27:08 2006 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 D759D16A41F; Mon, 23 Jan 2006 23:27: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 5760843D4C; Mon, 23 Jan 2006 23:27: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 350F746C2E; Mon, 23 Jan 2006 18:27:02 -0500 (EST) Date: Mon, 23 Jan 2006 23:28:17 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: John Baldwin In-Reply-To: <200601231739.02247.jhb@freebsd.org> Message-ID: <20060123232315.O48094@fledge.watson.org> References: <43D05151.5070409@elischer.org> <200601231616.49140.jhb@freebsd.org> <43D55739.80608@elischer.org> <200601231739.02247.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org, Julian Elischer Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 23:27:09 -0000 On Mon, 23 Jan 2006, John Baldwin wrote: > That's probably a better model, yes. One thing I would prefer though is if > we could limit the knowledge of ksegroups to the scheduler as much as > possible and let the rest of the kernel just deal with threads and > processes. Ideally, we'd reach the point where you have an API to say > "create a thread for process p" and kthreads just use a kernel process for > 'p' and maybe the API takes a flag to say if a thread is separate or not. > Really, aio should probably just be separate system scope threads, and you > could almost do that in userland now. That was my hope also when we originally talked about KSE support -- really what you want the application to do is simply create kernel execution sessions, in effect kernel thread stacks, as required to avoid interrupting application execution. I identified three reasons why I ended up concluding it should stay in kernel (regardless of the kernel details -- kprocs, kthreads, etc): (1) I wasn't sure what the POSIX requirements for completing I/O after a process exits. Are we obligated to try and commit them asynchronously from process exit, stall process exit waiting on the I/O, or can we actually drop the I/O work? I'm pretty sure the last of these is undesirable, but we should find out. (2) Right now we can actually run aio code in kernel without dedicating a thread stack to it -- we have to use a full kernel thread stack for the duration of VFS operations, but for sockets we can perform queued I/O and use socket upcalls to pick up the competion event, avoiding committing a full aio daemon. This is sort of like Mach continuations, and should conserve kernel memory and other state (pid slots, etc) nicely. This cannot be replicated easily from user space using the normal I/O system calls, as those all commit kernel threads to the work, at least, if you do it the easy way. Even if you do it the complicated way, there's potentially a lot more transition in and out of user space. (3) When emulating systems that provide AIO via the kernel, we'll end up simply implemnting AIO all over again for those ABI layers, even if it's not used for FreeBSD. If we would like to change the threading model for aio, my leaning is to try to keep it all inside the kernel. Robert N M Watson From owner-freebsd-current@FreeBSD.ORG Mon Jan 23 23:28:28 2006 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 606BD16A41F for ; Mon, 23 Jan 2006 23:28:28 +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 EEE3A43D5F for ; Mon, 23 Jan 2006 23:28:27 +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 0A53946C69; Mon, 23 Jan 2006 18:28:22 -0500 (EST) Date: Mon, 23 Jan 2006 23:29:36 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Julian Elischer In-Reply-To: <43D56468.1060101@elischer.org> Message-ID: <20060123232836.M48094@fledge.watson.org> References: <43D05151.5070409@elischer.org> <200601231616.49140.jhb@freebsd.org> <43D55739.80608@elischer.org> <20060123224756.R48094@fledge.watson.org> <43D56468.1060101@elischer.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Jan 2006 23:28:28 -0000 On Mon, 23 Jan 2006, Julian Elischer wrote: > it would be no different from when a threaded process exits now.. > > With the current setup you have a whole set of worries about what to do > about the thread responds when the process has already died. These worries > are aqctually simplified if the thread is part of the process. (at least I > believe this to be the case). It would be good to know what the aio specs say (and what real applications expect) to happen on the current set of "single threading" events: - exec - fork (although davidxu is changing that) - exit And any others I don't remember. We may find we need to perform an aio drain wait there if we switch to doing AIO in the process context. Robert N M Watson From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 00:20:43 2006 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 DDE7016A476; Tue, 24 Jan 2006 00:20:38 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 447B84441D; Tue, 24 Jan 2006 00:02:03 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.23.146]) ([10.251.23.146]) by a50.ironport.com with ESMTP; 23 Jan 2006 16:02:02 -0800 X-IronPort-Anti-Spam-Filtered: true Message-ID: <43D56E79.60504@elischer.org> Date: Mon, 23 Jan 2006 16:02:01 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: <43D05151.5070409@elischer.org> <200601231616.49140.jhb@freebsd.org> <43D55739.80608@elischer.org> <20060123224756.R48094@fledge.watson.org> <43D56468.1060101@elischer.org> <20060123232836.M48094@fledge.watson.org> In-Reply-To: <20060123232836.M48094@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 00:20:43 -0000 Robert Watson wrote: > > On Mon, 23 Jan 2006, Julian Elischer wrote: > >> it would be no different from when a threaded process exits now.. >> >> With the current setup you have a whole set of worries about what to >> do about the thread responds when the process has already died. >> These worries are aqctually simplified if the thread is part of the >> process. (at least I believe this to be the case). > > > It would be good to know what the aio specs say (and what real > applications expect) to happen on the current set of "single > threading" events: > > - exec the outstanding operation must be aborted.. the address space it is aimed at is being wiped.. > - fork (although davidxu is changing that) well, the operation woudll continue for the parent only I woudl assume. > (although davidxu is changing that) I'm not convinced that that multiple threads should be allowed to proceed during a fork but I can see that not allowing it is more a "foot shooting avoidance" than a requirement. it could be allowed that if you do a fork and allow multipel threads to runat the same time and end up with an inconsistant address space in the child, then you get what you deserve. :-) > - exit I think that's it.. It's certainly the 3 places we try single-thread. For exit, you allow the operation to complete as far as the buffer cache but you don't allow the thread to write it back to the address space. Writing back to the buffer cache (or whatever we call it now) should proceeed even if the thread has died. > > And any others I don't remember. We may find we need to perform an > aio drain wait there if we switch to doing AIO in the process context. I don't think so.. IO is really 2 stage: for read, data is read into the cache by standard async kernel code. then the thread wakes up and writes it to the user space. if the thread has died the async request is still allowed to complete. I believe this is the current state of affairs if a process gets a signal after requesting data from the filesystem, but before the filesystem has delivered it from teh device. The IO operation os not aborted, but the data is not used after it has been deleivered to the buffer cache. > > 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" From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 00:31:03 2006 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 DAF4816A420; Tue, 24 Jan 2006 00:31:03 +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 A0D4E43D46; Tue, 24 Jan 2006 00:31:03 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (root@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k0O0V0d9019380; Tue, 24 Jan 2006 00:31:01 GMT (envelope-from davidxu@freebsd.org) Message-ID: <43D5753D.8060102@freebsd.org> Date: Tue, 24 Jan 2006 08:30:53 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060107 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Julian Elischer References: <43D05151.5070409@elischer.org> <200601231616.49140.jhb@freebsd.org> <43D55739.80608@elischer.org> In-Reply-To: <43D55739.80608@elischer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 00:31:04 -0000 Julian Elischer wrote: > > John Baldwin wrote: > >> On Thursday 19 January 2006 21:56, Julian Elischer wrote: >> >> >>> some progrsss.. >>> as the first few lines show, it's not quite perfect yet but it's >>> most of >>> the way there.. >>> (Like proc 1 isn't init) >>> >> >> >> One other note, watch out for the AIO daemons. They have to be >> kernel procs and not kthreads because they borrow the vmspace of the >> user process when performing AIO on another process' behalf. >> >> >> > yeah I found that and the patches account for that. > > However I would like to suggest that we change the way that aio works.. > > My suggestion is that when a process does AIO, that we "fork a > ksegroup" and attach it to the > process, and assign it a (or some) worker thread to do the aio work. > The userland process would > be oblivious of the extra (kernel) threads in that kseg and they would > be independently schedulable. > They would however automatically have full access to the correct > address space. > These threads should be invisible to userland debugger, and other code current unknown, for example, signal code ? The idea seems simply but we may in fact encounter problem, because you inject unknown threads to a process. :-) I still prefer current model, also the aiod threads can be reused for multiple processes. From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 00:31:27 2006 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 E56B116A41F for ; Tue, 24 Jan 2006 00:31:27 +0000 (GMT) (envelope-from freebsd@contexthosting.net) Received: from mail.contexthosting.net (inception.contexthosting.net [209.120.245.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFF3F43D49 for ; Tue, 24 Jan 2006 00:31:26 +0000 (GMT) (envelope-from freebsd@contexthosting.net) Received: (qmail 29591 invoked by uid 89); 24 Jan 2006 00:31:25 -0000 Received: by simscan 1.0.7 ppid: 29583, pid: 29589, t: 0.0504s scanners:none Received: from unknown (HELO ?192.168.1.100?) (jim@contexthosting.net@68.80.252.242) by mail.contexthosting.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 24 Jan 2006 00:31:25 -0000 Message-ID: <43D5754E.9010804@contexthosting.net> Date: Mon, 23 Jan 2006 19:31:10 -0500 From: Jim Keller User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: FreeBSD 4.9 won't upgrade ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 00:31:28 -0000 Hey all, I have a FreeBSD 4.9 machine here that simply doesn't want to upgrade, though the buildworld/installworld process seems to go successfully. I'm just trying to go to 4.11 at the moment. I've done the installworld process on more than a few machines before without any problems (following the steps outlined in the handbook). However, on this machine, I go through the whole process, and although it does appear to recompile the system (my openssl went from the original distro to the newest version, for example), uname -a is still reporting the distro as 4.9-RELEASE. Also, it will not install a custom kernel, it always goes to GENERIC, even when I specify KERNCONF= in the buildkernel process. I've CVSUP'd my source twice (currently my tag is RELENG_4_11) and run the whole process twice, including starting with removing /usr/obj and doing a double make cleandir in /usr/src. Any ideas? Thanks. -Jim Keller From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 00:59:05 2006 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 90EB416A41F; Tue, 24 Jan 2006 00:59:05 +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 31C2443D46; Tue, 24 Jan 2006 00:59:04 +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 k0O0x23x028638; Mon, 23 Jan 2006 19:59:02 -0500 (EST) Date: Mon, 23 Jan 2006 19:59:02 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Julian Elischer In-Reply-To: <43D56E79.60504@elischer.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: freebsd-current@freebsd.org, Robert Watson Subject: Re: kernel thread as real threads.. 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: Tue, 24 Jan 2006 00:59:05 -0000 On Mon, 23 Jan 2006, Julian Elischer wrote: > Robert Watson wrote: > > > well, the operation woudll continue for the parent only I woudl assume. > > > (although davidxu is changing that) > > I'm not convinced that that multiple threads should be allowed to > proceed during a fork > but I can see that not allowing it is more a "foot shooting avoidance" > than a requirement. > it could be allowed that if you do a fork and allow multipel threads to > runat the same time > and end up with an inconsistant address space in the child, then you get > what you deserve. > :-) POSIX specifies that only 1 thread (the forking thread) is present after a fork. If you want all (or some subset) of the parent's threads to exist after a fork(), you must call it something else (use a flag to rfork?) and ensure it is not the default behavior. -- DE From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 00:59:13 2006 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 1A55016A41F; Tue, 24 Jan 2006 00:59:13 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB9CC43D48; Tue, 24 Jan 2006 00:59:12 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.23.146]) ([10.251.23.146]) by a50.ironport.com with ESMTP; 23 Jan 2006 16:59:11 -0800 X-IronPort-Anti-Spam-Filtered: true Message-ID: <43D57BDF.6010308@elischer.org> Date: Mon, 23 Jan 2006 16:59:11 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Xu References: <43D05151.5070409@elischer.org> <200601231616.49140.jhb@freebsd.org> <43D55739.80608@elischer.org> <43D5753D.8060102@freebsd.org> In-Reply-To: <43D5753D.8060102@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 00:59:13 -0000 David Xu wrote: > Julian Elischer wrote: > >> >> John Baldwin wrote: >> >>> On Thursday 19 January 2006 21:56, Julian Elischer wrote: >>> >>> >>>> some progrsss.. >>>> as the first few lines show, it's not quite perfect yet but it's >>>> most of >>>> the way there.. >>>> (Like proc 1 isn't init) >>>> >>> >>> >>> >>> One other note, watch out for the AIO daemons. They have to be >>> kernel procs and not kthreads because they borrow the vmspace of the >>> user process when performing AIO on another process' behalf. >>> >>> >>> >> yeah I found that and the patches account for that. >> >> However I would like to suggest that we change the way that aio works.. >> >> My suggestion is that when a process does AIO, that we "fork a >> ksegroup" and attach it to the >> process, and assign it a (or some) worker thread to do the aio work. >> The userland process would >> be oblivious of the extra (kernel) threads in that kseg and they >> would be independently schedulable. >> They would however automatically have full access to the correct >> address space. >> > These threads should be invisible to userland debugger, and other code > current unknown, for example, signal code ? The idea seems simply but we > may in fact encounter problem, because you inject unknown threads to a > process. :-) If the userland doesn't know about them, how would it affect it? As a kernel thread it wouldn't take part in signals, other than to abort when the process exits. it WOULD accumulate cpu time for the process.. but that is just fair. currently I think that aio is "free". Anyhow I'm not ready to try do it now.. As the current patches leave the status-quo for aio. > I still prefer current model, also the aiod threads can be reused for > multiple > processes. that is both a positive and a negative when it comes to accounting. From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 01:09:13 2006 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 C4F0E16A422 for ; Tue, 24 Jan 2006 01:09:13 +0000 (GMT) (envelope-from sbruno@miralink.com) Received: from mazo.miralink.com (mail.miralink.com [70.103.185.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id E59C343D55 for ; Tue, 24 Jan 2006 01:09:12 +0000 (GMT) (envelope-from sbruno@miralink.com) Received: from [10.1.1.47] (unknown [10.1.1.47]) by mazo.miralink.com (Postfix) with ESMTP id DE25B36A30 for ; Wed, 18 Jan 2006 17:37:17 -0800 (PST) From: Sean Bruno To: current@freebsd.org Content-Type: text/plain Date: Wed, 18 Jan 2006 17:36:50 -0800 Message-Id: <1137634610.16906.22.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Content-Transfer-Encoding: 7bit Cc: Subject: 4.11 b_iodone callback 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, 24 Jan 2006 01:09:13 -0000 I just inherited some older code that runs under 4.11 ... the core of software is a device driver that writes data to two separate disks(da1/da2). It appears that the authors are using a call back function to handle some interesting behavior related to the second disk being a circular buffer. So a couple of questions: 1. Does the call back routine set in b_iodone(disk writes are handled by VOP_STRATEGY) get invoked in a separate thread of execution, i.e. is simultaneous with the main code path? 2. Is it o.k. to have the callback routine invoke itself vi b_iodone(more VOP_STRATEGY) without locking the buffers used for the disk writes? Sean Bruno From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 01:12:51 2006 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 1D43F16A41F; Tue, 24 Jan 2006 01:12:51 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail20.syd.optusnet.com.au (mail20.syd.optusnet.com.au [211.29.132.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A14F43D45; Tue, 24 Jan 2006 01:12: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 mail20.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k0O1CiIj020012 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 24 Jan 2006 12:12:44 +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 k0O1ChHh037656; Tue, 24 Jan 2006 12:12:44 +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 k0O1Chfb037655; Tue, 24 Jan 2006 12:12:43 +1100 (EST) (envelope-from pjeremy) Date: Tue, 24 Jan 2006 12:12:43 +1100 From: Peter Jeremy To: Julian Elischer Message-ID: <20060124011243.GT25397@cirb503493.alcatel.com.au> References: <43D05151.5070409@elischer.org> <200601231616.49140.jhb@freebsd.org> <43D55739.80608@elischer.org> <20060123224756.R48094@fledge.watson.org> <43D56468.1060101@elischer.org> <20060123232836.M48094@fledge.watson.org> <43D56E79.60504@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43D56E79.60504@elischer.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-current@freebsd.org, Robert Watson Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 01:12:51 -0000 On Mon, 2006-Jan-23 16:02:01 -0800, Julian Elischer wrote: >>And any others I don't remember. We may find we need to perform an >>aio drain wait there if we switch to doing AIO in the process context. > >I don't think so.. >IO is really 2 stage: > >for read, data is read into the cache by standard async kernel code. >then the thread wakes up and writes it to the user space. >if the thread has died the async request is still allowed to complete. Is this done as a one-off event, or will data be copied from kernel to userland as the data arrives in the kernel? The former implies that the userland buffer is (pretty much) atomically updated - it is unchanged until all the available data arrives, at which point it is all copied into userland and the aio flagged as complete. The latter implies that parts of the userland buffer will update gradually. The difference primarily affects large requests (and the latter approach implies that less kernel resources will be tied up by the I/O). What about the write case? -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 01:22:40 2006 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 3D2AC16A41F; Tue, 24 Jan 2006 01:22:40 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail27.syd.optusnet.com.au (mail27.syd.optusnet.com.au [211.29.133.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id C95C943D48; Tue, 24 Jan 2006 01:22:38 +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 mail27.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k0O1MacB030022 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 24 Jan 2006 12:22:37 +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 k0O1MaHh037679; Tue, 24 Jan 2006 12:22:36 +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 k0O1Ma49037678; Tue, 24 Jan 2006 12:22:36 +1100 (EST) (envelope-from pjeremy) Date: Tue, 24 Jan 2006 12:22:36 +1100 From: Peter Jeremy To: Daniel Eischen Message-ID: <20060124012236.GU25397@cirb503493.alcatel.com.au> References: <43D56E79.60504@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-current@freebsd.org Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 01:22:40 -0000 On Mon, 2006-Jan-23 19:59:02 -0500, Daniel Eischen wrote: >POSIX specifies that only 1 thread (the forking thread) is present >after a fork. Just to clarify, I presume you are talking about only one thread existing in the child process and the parent's threads still exist as they did before the fork(). If fork() arbitrarily killed all the threads in the parent process, that would be a real PITA. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 01:38:51 2006 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 F318116A420 for ; Tue, 24 Jan 2006 01:38:50 +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 A14EA43D69 for ; Tue, 24 Jan 2006 01:38:47 +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 k0O1ckTs003977; Mon, 23 Jan 2006 20:38:46 -0500 (EST) Date: Mon, 23 Jan 2006 20:38:46 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Peter Jeremy In-Reply-To: <20060124012236.GU25397@cirb503493.alcatel.com.au> 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: freebsd-current@freebsd.org Subject: Re: kernel thread as real threads.. 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: Tue, 24 Jan 2006 01:38:51 -0000 On Tue, 24 Jan 2006, Peter Jeremy wrote: > On Mon, 2006-Jan-23 19:59:02 -0500, Daniel Eischen wrote: > >POSIX specifies that only 1 thread (the forking thread) is present > >after a fork. > > Just to clarify, I presume you are talking about only one thread > existing in the child process and the parent's threads still exist as > they did before the fork(). If fork() arbitrarily killed all the > threads in the parent process, that would be a real PITA. Correct, I assumed we were talking about the child process. -- DE From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 02:01:40 2006 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 CF42416A41F; Tue, 24 Jan 2006 02:01:40 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail16.syd.optusnet.com.au (mail16.syd.optusnet.com.au [211.29.132.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28A4443D45; Tue, 24 Jan 2006 02:01:39 +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 mail16.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k0O21bni029426 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 24 Jan 2006 13:01:38 +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 k0O21bHh037750; Tue, 24 Jan 2006 13:01:37 +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 k0O21bj3037749; Tue, 24 Jan 2006 13:01:37 +1100 (EST) (envelope-from pjeremy) Date: Tue, 24 Jan 2006 13:01:37 +1100 From: Peter Jeremy To: Daniel Eischen Message-ID: <20060124020137.GW25397@cirb503493.alcatel.com.au> References: <20060124012236.GU25397@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: freebsd-current@freebsd.org Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 02:01:41 -0000 On Mon, 2006-Jan-23 20:38:46 -0500, Daniel Eischen wrote: >On Tue, 24 Jan 2006, Peter Jeremy wrote: > >> On Mon, 2006-Jan-23 19:59:02 -0500, Daniel Eischen wrote: >> >POSIX specifies that only 1 thread (the forking thread) is present >> >after a fork. >> >> Just to clarify, I presume you are talking about only one thread >> existing in the child process and the parent's threads still exist as >> they did before the fork(). If fork() arbitrarily killed all the >> threads in the parent process, that would be a real PITA. > >Correct, I assumed we were talking about the child process. My understanding of Robert's issue was the case where a parent has multiple threads, one thread does a fork() whilst the remaining threads are not blocked. If the remaining threads are executing whilst fork() is copying the process address space, then the child will could inherit a confused (partially indeterminate) copy of the parent's address space, depending on what the other threads have been doing. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 02:02:37 2006 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 23D6416A41F; Tue, 24 Jan 2006 02:02:37 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id C005A43D45; Tue, 24 Jan 2006 02:02:36 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01a ([66.130.198.54]) by VL-MO-MR003.ip.videotron.ca (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTP id <0ITK00EO4R0BCR2C@VL-MO-MR003.ip.videotron.ca>; Mon, 23 Jan 2006 21:02:36 -0500 (EST) Date: Mon, 23 Jan 2006 21:02:14 -0500 From: Nicolas Blais In-reply-to: <43D528AD.7020309@deepcore.dk> To: freebsd-current@freebsd.org Message-id: <200601232102.35528.nb_root@videotron.ca> MIME-version: 1.0 Content-type: multipart/signed; boundary=nextPart1833565.EKVu9xeOav; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit References: <200601211159.50768.nb_root@videotron.ca> <20060123182607.GR99407@mich2.itxmarket.com> <43D528AD.7020309@deepcore.dk> User-Agent: KMail/1.9.1 Cc: Michael Landin Hostbaek , =?iso-8859-1?q?S=F8ren_Schmidt?= Subject: Re: -CURRENT freeze at boot after update X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2006 02:02:37 -0000 --nextPart1833565.EKVu9xeOav Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline > > I spoke briefly to sos@ about it, and he has been unable to reproduce > > this, so someone with time / knowledge should dig deeper and send him a > > mail with the findings. > > The only thing that comes to mind is the below patch, please try that > out and let me know. However that way the legacy ports (those stuck at > irq14 & irq15) cannot share interrupt with *anything*, which I did want > to fix as a side effect of this actually... > > -S=F8ren Hi, sorry for the wait. I recompiled my kernel with your patch, unfortunatly it does nothing to=20 prevent the freeze. =20 If you have any patches, I'm willing to try it. Thanks, Nicolas. =2D-=20 =46reeBSD 7.0-CURRENT #2: Mon Jan 23 17:24:42 EST 2006 =20 nicblais@clk01a:/usr/obj/usr/src/sys/CLK01A=20 PGP? (updated 16 Nov 05) : http://www.clkroot.net/security/nb_root.asc --nextPart1833565.EKVu9xeOav Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBD1Yq74wTBlvcsbJURAmjeAKCiArYITfiTgmHacSoGUDwUq0I4wQCffLCY AyjtQSqYWBBS+kwTt8ZgxtY= =GZKH -----END PGP SIGNATURE----- --nextPart1833565.EKVu9xeOav-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 02:11:27 2006 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 1FC1C16A41F for ; Tue, 24 Jan 2006 02:11:27 +0000 (GMT) (envelope-from crapsh@monkeybrains.net) Received: from mail.monkeybrains.net (mail1.monkeybrains.NET [207.7.142.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 817C643D45 for ; Tue, 24 Jan 2006 02:11:26 +0000 (GMT) (envelope-from crapsh@monkeybrains.net) Received: from [192.168.0.111] (busymonkey.monkeybrains.net [66.92.187.117]) (authenticated bits=0) by mail.monkeybrains.net (8.13.4/8.13.4) with ESMTP id k0O2BPiA063878 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 23 Jan 2006 18:11:26 -0800 (PST) (envelope-from crapsh@monkeybrains.net) Message-ID: <43D58CCE.6010002@monkeybrains.net> Date: Mon, 23 Jan 2006 18:11:26 -0800 From: Rudy Rucker User-Agent: Thunderbird 1.5 (X11/20060120) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20060123120028.9F3F016A422@hub.freebsd.org> In-Reply-To: <20060123120028.9F3F016A422@hub.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on mail.monkeybrains.net X-Virus-Status: Clean Subject: Boot problem (hangs at/in loader) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 02:11:27 -0000 I installed FreeBSD on a disk and have this problem: The boot manager comes up and shows: F1: FreeBSD F5: Disk 2 If I hit F1 (or wait a few seconds), The 'puter drops down a line, shows a minus (-) sign in the bottom left hand corner and stays there until I hit any key on the keyboard. I ran: boot0cfg -B /dev/ad0 and the problem did not go away. What else could I try so that the computer will boot/reboot unattended? Rudy > fdisk ad0 ******* Working on device /dev/ad0 ******* parameters extracted from in-core disklabel are: cylinders=387621 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=387621 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 390716802 (190779 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 768/ head 254/ sector 63 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: > bsdlabel ad0s1 # /dev/ad0s1: 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 1048576 16 4.2BSD 2048 16384 8 b: 1048576 1048592 swap c: 390716802 0 unused 0 0 # "raw" part, don't edit d: 20971520 2097168 4.2BSD 2048 16384 28552 e: 2097152 23068688 4.2BSD 2048 16384 28552 f: 16777216 25165840 4.2BSD 2048 16384 28552 g: 348773746 41943056 4.2BSD 2048 16384 28552 > uname -a FreeBSD 6.0-STABLE FreeBSD 6.0-STABLE #3: Tue Jan 17 09:22:44 PST ... > df -h (don't you love that h) Filesystem Size Used Avail Capacity Mounted on /dev/ad0s1a 496M 51M 405M 11% / devfs 1.0K 1.0K 0B 100% /dev /dev/ad2s1d 15G 518M 14G 4% /var /dev/ad0s1e 989M 1.0M 909M 0% /tmp /dev/ad0s1f 7.7G 3.3G 3.9G 46% /usr /dev/ad0s1g 161G 4.0K 148G 0% /data procfs 4.0K 4.0K 0B 100% /proc devfs 1.0K 1.0K 0B 100% /var/named/dev From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 02:24:46 2006 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 A59DC16A420; Tue, 24 Jan 2006 02:24:46 +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 4FED943D48; Tue, 24 Jan 2006 02:24:46 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (root@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k0O2OhqW065261; Tue, 24 Jan 2006 02:24:45 GMT (envelope-from davidxu@freebsd.org) Message-ID: <43D58FF6.6050605@freebsd.org> Date: Tue, 24 Jan 2006 10:24:54 +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: Julian Elischer References: <43D05151.5070409@elischer.org> <200601231616.49140.jhb@freebsd.org> <43D55739.80608@elischer.org> <43D5753D.8060102@freebsd.org> <43D57BDF.6010308@elischer.org> In-Reply-To: <43D57BDF.6010308@elischer.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 02:24:46 -0000 Julian Elischer wrote: > >>> However I would like to suggest that we change the way that aio works.. >>> >>> My suggestion is that when a process does AIO, that we "fork a >>> ksegroup" and attach it to the >>> process, and assign it a (or some) worker thread to do the aio work. >>> The userland process would >>> be oblivious of the extra (kernel) threads in that kseg and they >>> would be independently schedulable. >>> They would however automatically have full access to the correct >>> address space. >>> >> These threads should be invisible to userland debugger, and other code >> current unknown, for example, signal code ? The idea seems simply but we >> may in fact encounter problem, because you inject unknown threads to a > > >> process. :-) > > > If the userland doesn't know about them, how would it affect it? I said it should be invisible to userland debugger, but ptrace interface will expose it to userland, you have to calculate actually threads number for PT_GETNUMLWPS, you also have to filter aio threads out for PT_GETLWPLIST, you also have to figure out first threads which is meanful to userland for PT_LWPINFO, others I don't know yet. I didn't say that injecting unknown threads into process is not practical, but it should be carefully to not break current stable code. > As a kernel thread it wouldn't take part in signals, other than to abort > when the process exits. Also, process suspension should suspend these aio threads. > it WOULD accumulate cpu time for the process.. but that is just fair. > currently I think that > aio is "free". > Yes, you are right. > Anyhow I'm not ready to try do it now.. As the current patches leave the > status-quo for aio. > > OK. > > > > > >> I still prefer current model, also the aiod threads can be reused for >> multiple >> processes. > > > that is both a positive and a negative when it comes to accounting. > > > From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 02:30:26 2006 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 835C916A41F; Tue, 24 Jan 2006 02:30:26 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42D7A43D46; Tue, 24 Jan 2006 02:30:26 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.23.146]) ([10.251.23.146]) by a50.ironport.com with ESMTP; 23 Jan 2006 18:30:25 -0800 X-IronPort-Anti-Spam-Filtered: true Message-ID: <43D59141.4030701@elischer.org> Date: Mon, 23 Jan 2006 18:30:25 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 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: freebsd-current@freebsd.org, Robert Watson Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 02:30:26 -0000 Daniel Eischen wrote: >On Mon, 23 Jan 2006, Julian Elischer wrote: > > > >>Robert Watson wrote: >> >> >>well, the operation woudll continue for the parent only I woudl assume. >> >> >> >>>(although davidxu is changing that) >>> >>> >>I'm not convinced that that multiple threads should be allowed to >>proceed during a fork >>but I can see that not allowing it is more a "foot shooting avoidance" >>than a requirement. >>it could be allowed that if you do a fork and allow multipel threads to >>runat the same time >>and end up with an inconsistant address space in the child, then you get >>what you deserve. >>:-) >> >> > >POSIX specifies that only 1 thread (the forking thread) is present >after a fork. If you want all (or some subset) of the parent's >threads to exist after a fork(), you must call it something >else (use a flag to rfork?) and ensure it is not the default >behavior. > > I'm not saying the others would survive, but that if they are running on other processors at the moment when we duplicate the address space, we may get a rather inconsistent address space.. The current code handles this by forcing all other threads into a suspended state before allowing the fork() to proceeed and then allowing them to continue (on the parent only) when the fork has completed. There aer some cases when this behaviour has been seen to cause problems and it has been suggested that this is not a requirement. From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 02:35:05 2006 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 5927F16A41F; Tue, 24 Jan 2006 02:35:05 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FF0443D48; Tue, 24 Jan 2006 02:35:04 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.23.146]) ([10.251.23.146]) by a50.ironport.com with ESMTP; 23 Jan 2006 18:35:04 -0800 X-IronPort-Anti-Spam-Filtered: true Message-ID: <43D59258.1060705@elischer.org> Date: Mon, 23 Jan 2006 18:35:04 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Jeremy References: <43D05151.5070409@elischer.org> <200601231616.49140.jhb@freebsd.org> <43D55739.80608@elischer.org> <20060123224756.R48094@fledge.watson.org> <43D56468.1060101@elischer.org> <20060123232836.M48094@fledge.watson.org> <43D56E79.60504@elischer.org> <20060124011243.GT25397@cirb503493.alcatel.com.au> In-Reply-To: <20060124011243.GT25397@cirb503493.alcatel.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Robert Watson Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 02:35:05 -0000 Peter Jeremy wrote: >On Mon, 2006-Jan-23 16:02:01 -0800, Julian Elischer wrote: > > >>>And any others I don't remember. We may find we need to perform an >>>aio drain wait there if we switch to doing AIO in the process context. >>> >>> >>I don't think so.. >>IO is really 2 stage: >> >>for read, data is read into the cache by standard async kernel code. >>then the thread wakes up and writes it to the user space. >>if the thread has died the async request is still allowed to complete. >> >> > >Is this done as a one-off event, or will data be copied from kernel >to userland as the data arrives in the kernel? The former implies >that the userland buffer is (pretty much) atomically updated - it is >unchanged until all the available data arrives, at which point it is >all copied into userland and the aio flagged as complete. The latter >implies that parts of the userland buffer will update gradually. The >difference primarily affects large requests (and the latter approach >implies that less kernel resources will be tied up by the I/O). > > I sugest reading the code.. I don't know the answer.. But I'm interested to hear the answer. I believe it's done in (largeish) chunks but I may be wrong. :-) >What about the write case? > > I believe it's symetrical with read., In either case. If the requestor is not around at completion of the physical IO it is not much of a problem. From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 03:01:44 2006 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 E12C316A41F; Tue, 24 Jan 2006 03:01:44 +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 4164243D45; Tue, 24 Jan 2006 03:01: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 k0O2xleU006484; Mon, 23 Jan 2006 19:59:47 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 23 Jan 2006 20:00:08 -0700 (MST) Message-Id: <20060123.200008.84910888.imp@bsdimp.com> To: julian@elischer.org From: "M. Warner Losh" In-Reply-To: <43D56E79.60504@elischer.org> References: <43D56468.1060101@elischer.org> <20060123232836.M48094@fledge.watson.org> <43D56E79.60504@elischer.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, 23 Jan 2006 19:59:47 -0700 (MST) Cc: freebsd-current@freebsd.org, rwatson@freebsd.org Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 03:01:45 -0000 In message: <43D56E79.60504@elischer.org> Julian Elischer writes: : > - fork (although davidxu is changing that) : : well, the operation woudll continue for the parent only I woudl assume. : : > (although davidxu is changing that) : : I'm not convinced that that multiple threads should be allowed to : proceed during a fork : but I can see that not allowing it is more a "foot shooting avoidance" : than a requirement. : it could be allowed that if you do a fork and allow multipel threads to : runat the same time : and end up with an inconsistant address space in the child, then you get : what you deserve. : :-) Why not? It is a race no matter what... And if you do single thread things, you can run into a bunch of different dead-lock scenarios. I helped to find one recently with nfs. Warner From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 03:04:18 2006 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 7BDDC16A41F; Tue, 24 Jan 2006 03:04:18 +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 B156F43D4C; Tue, 24 Jan 2006 03:04:17 +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 k0O31TWo006558; Mon, 23 Jan 2006 20:01:29 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 23 Jan 2006 20:01:51 -0700 (MST) Message-Id: <20060123.200151.127094205.imp@bsdimp.com> To: deischen@freebsd.org From: "M. Warner Losh" In-Reply-To: References: <43D56E79.60504@elischer.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, 23 Jan 2006 20:01:29 -0700 (MST) Cc: freebsd-current@freebsd.org, rwatson@freebsd.org, julian@elischer.org Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 03:04:18 -0000 In message: Daniel Eischen writes: : On Mon, 23 Jan 2006, Julian Elischer wrote: : : > Robert Watson wrote: : > : > : > well, the operation woudll continue for the parent only I woudl assume. : > : > > (although davidxu is changing that) : > : > I'm not convinced that that multiple threads should be allowed to : > proceed during a fork : > but I can see that not allowing it is more a "foot shooting avoidance" : > than a requirement. : > it could be allowed that if you do a fork and allow multipel threads to : > runat the same time : > and end up with an inconsistant address space in the child, then you get : > what you deserve. : > :-) : : POSIX specifies that only 1 thread (the forking thread) is present : after a fork. If you want all (or some subset) of the parent's : threads to exist after a fork(), you must call it something : else (use a flag to rfork?) and ensure it is not the default : behavior. The problem that we have today is that single_thread suspends most, but not all, of the threads. There are many scenarios where one could get deadlock if you are sleeping uninterruptably in one thread, but interruptably in another. Warner From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 04:01:11 2006 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 0706616A41F for ; Tue, 24 Jan 2006 04:01:11 +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 9A3C643D53 for ; Tue, 24 Jan 2006 04:01:10 +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.60 (FreeBSD)) (envelope-from ) id 1F1FMj-000Oib-PT; Tue, 24 Jan 2006 04:01:10 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1F1FMi-00051F-Do; Tue, 24 Jan 2006 13:01:08 +0900 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17365.42627.914349.894764@roam.psg.com> Date: Tue, 24 Jan 2006 13:01:07 +0900 To: FreeBSD Current Subject: t41 zzz X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 04:01:11 -0000 thinkpad t41 running current as of a few hours ago xorg, gnome 2.21, ... if i execute zzz it suspends s3 seemingly quite happily when i open lid, there is disk activity, the numlock and shiftlock lights flash a bit (this was normal behavior when zzz last worked some weeks back), and the screen comes back on. but ... it never completes the zzz script, i.e. no shell prompt. if i put an echo in /etc/rc.resume it shows it has been executed. though i can move the cursor with the touchpad, focus never grabs any window. and there is no response to keyboard. at kevin oberman's recommendation, i added radionctl hacks a la if [ -x /usr/local/bin/radeontool ]; then /usr/local/bin/radeontool light on fi to suspend/resume. no effect. suggestions on how to fix or even how to debug would be appreciated. randy From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 04:06:43 2006 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 673BC16A41F; Tue, 24 Jan 2006 04:06:43 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BE7E43D58; Tue, 24 Jan 2006 04:06:42 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id E7C9BAD; Mon, 23 Jan 2006 22:06:41 -0600 (CST) Received: by draco.over-yonder.net (Postfix, from userid 100) id 0814161C32; Mon, 23 Jan 2006 22:06:41 -0600 (CST) Date: Mon, 23 Jan 2006 22:06:40 -0600 From: "Matthew D. Fuller" To: Jim Keller Message-ID: <20060124040640.GB34914@over-yonder.net> References: <43D5754E.9010804@contexthosting.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43D5754E.9010804@contexthosting.net> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.2 X-Mailman-Approved-At: Tue, 24 Jan 2006 04:10:43 +0000 Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 4.9 won't upgrade ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 04:06:43 -0000 [ Redirecting to -stable, where it's more appropriate ] On Mon, Jan 23, 2006 at 07:31:10PM -0500 I heard the voice of Jim Keller, and lo! it spake thus: > > I go through the whole process, and although it does appear to > recompile the system (my openssl went from the original distro to > the newest version, for example), uname -a is still reporting the > distro as 4.9-RELEASE. That's because you haven't installed the new kernel. > Also, it will not install a custom kernel, it always goes to > GENERIC, even when I specify KERNCONF= in the buildkernel process. This I dunno about. Were I you, I'd just go ahead and get GENERIC installed and running so that your kernel matches your userland at least, then worry about why your can't seem to build your own kernel. -- 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 Tue Jan 24 04:32:30 2006 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 AB71116A41F for ; Tue, 24 Jan 2006 04:32:30 +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 4E2DA43D45 for ; Tue, 24 Jan 2006 04:32:30 +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 k0O4WSY9004097; Mon, 23 Jan 2006 23:32:29 -0500 (EST) Date: Mon, 23 Jan 2006 23:32:28 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Peter Jeremy In-Reply-To: <20060124020137.GW25397@cirb503493.alcatel.com.au> 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: freebsd-current@freebsd.org Subject: Re: kernel thread as real threads.. 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: Tue, 24 Jan 2006 04:32:30 -0000 On Tue, 24 Jan 2006, Peter Jeremy wrote: > On Mon, 2006-Jan-23 20:38:46 -0500, Daniel Eischen wrote: > >On Tue, 24 Jan 2006, Peter Jeremy wrote: > > > >> On Mon, 2006-Jan-23 19:59:02 -0500, Daniel Eischen wrote: > >> >POSIX specifies that only 1 thread (the forking thread) is present > >> >after a fork. > >> > >> Just to clarify, I presume you are talking about only one thread > >> existing in the child process and the parent's threads still exist as > >> they did before the fork(). If fork() arbitrarily killed all the > >> threads in the parent process, that would be a real PITA. > > > >Correct, I assumed we were talking about the child process. > > My understanding of Robert's issue was the case where a parent has > multiple threads, one thread does a fork() whilst the remaining > threads are not blocked. If the remaining threads are executing > whilst fork() is copying the process address space, then the child > will could inherit a confused (partially indeterminate) copy of the > parent's address space, depending on what the other threads have > been doing. I think that's OK. The only thing that is guaranteed safe (in the child) after a fork from a multi-threaded process are the async-signal-safe functions. If a process has aio active, it shouldn't assume anything about the childs state after a fork. I think it's only important that the forking thread continues on normally in the child. OTOH, if there is a possibility of some inconsistent kernel state that will affect the child if it calls any of the async-signal-safe functions or one of the exec() functions, that should be avoided. -- DE From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 05:38:57 2006 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 CB86A16A41F; Tue, 24 Jan 2006 05:38:57 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FA7B43D48; Tue, 24 Jan 2006 05:38:57 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [192.168.2.4]) ([10.251.60.33]) by a50.ironport.com with ESMTP; 23 Jan 2006 21:38:56 -0800 X-IronPort-Anti-Spam-Filtered: true Message-ID: <43D5BD70.6080503@elischer.org> Date: Mon, 23 Jan 2006 21:38:56 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Eischen References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Peter Jeremy , freebsd-current@freebsd.org Subject: Re: kernel thread as real threads.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 05:38:57 -0000 Daniel Eischen wrote: >On Tue, 24 Jan 2006, Peter Jeremy wrote: > > > >>On Mon, 2006-Jan-23 20:38:46 -0500, Daniel Eischen wrote: >> >> >>>On Tue, 24 Jan 2006, Peter Jeremy wrote: >>> >>> >>> >>>>On Mon, 2006-Jan-23 19:59:02 -0500, Daniel Eischen wrote: >>>> >>>> >>>>>POSIX specifies that only 1 thread (the forking thread) is present >>>>>after a fork. >>>>> >>>>> >>>>Just to clarify, I presume you are talking about only one thread >>>>existing in the child process and the parent's threads still exist as >>>>they did before the fork(). If fork() arbitrarily killed all the >>>>threads in the parent process, that would be a real PITA. >>>> >>>> >>>Correct, I assumed we were talking about the child process. >>> >>> >>My understanding of Robert's issue was the case where a parent has >>multiple threads, one thread does a fork() whilst the remaining >>threads are not blocked. If the remaining threads are executing >>whilst fork() is copying the process address space, then the child >>will could inherit a confused (partially indeterminate) copy of the >>parent's address space, depending on what the other threads have >>been doing. >> >> > >I think that's OK. The only thing that is guaranteed safe (in the >child) after a fork from a multi-threaded process are the >async-signal-safe functions. If a process has aio active, >it shouldn't assume anything about the childs state after a >fork. I think it's only important that the forking thread >continues on normally in the child. OTOH, if there is a >possibility of some inconsistent kernel state that will affect >the child if it calls any of the async-signal-safe functions >or one of the exec() functions, that should be avoided. > > It's not a case of kernel state so much as the state of user space. Of course there is some course kernel state involved, such as if one thread does a fork while the other is mmaping pages or setting signals. From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 06:58:51 2006 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 7D3C716A41F; Tue, 24 Jan 2006 06:58:51 +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 122C243D45; Tue, 24 Jan 2006 06:58:50 +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 2FC5A10466; Tue, 24 Jan 2006 07:58:49 +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 k0O6wUxE015501; Tue, 24 Jan 2006 07:58:33 +0100 (CET) From: Thierry Herbelot To: freebsd-current@freebsd.org Date: Tue, 24 Jan 2006 07:58:21 +0100 User-Agent: KMail/1.9.1 References: <200601232041.19159.thierry@herbelot.com> <20060123212723.GN25397@cirb503493.alcatel.com.au> In-Reply-To: <20060123212723.GN25397@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: <200601240758.24323.thierry@herbelot.com> Cc: Peter Jeremy , current@freebsd.org Subject: Re: softdep panic at reboot (and restart) 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: Tue, 24 Jan 2006 06:58:51 -0000 Le Monday 23 January 2006 22:27, Peter Jeremy a écrit : > On Mon, 2006-Jan-23 20:41:17 +0100, Thierry Herbelot wrote: > >panic: vm_page_free_toq: freeing mapped page 0xc11fae58 > > Sam Leffler has suggested that Alan Cox's latest sys/kern/vfs_bio.c > change is at fault here. You could try backing out v1.502 and see if > the problem goes away. Thanks for the tip : it seems to have disappeared (at least a more recent kernel, with the indicated file revision boots correctly and is building its world) TfH From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 06:58:51 2006 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 7D3C716A41F; Tue, 24 Jan 2006 06:58:51 +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 122C243D45; Tue, 24 Jan 2006 06:58:50 +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 2FC5A10466; Tue, 24 Jan 2006 07:58:49 +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 k0O6wUxE015501; Tue, 24 Jan 2006 07:58:33 +0100 (CET) From: Thierry Herbelot To: freebsd-current@freebsd.org Date: Tue, 24 Jan 2006 07:58:21 +0100 User-Agent: KMail/1.9.1 References: <200601232041.19159.thierry@herbelot.com> <20060123212723.GN25397@cirb503493.alcatel.com.au> In-Reply-To: <20060123212723.GN25397@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: <200601240758.24323.thierry@herbelot.com> Cc: Peter Jeremy , current@freebsd.org Subject: Re: softdep panic at reboot (and restart) 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: Tue, 24 Jan 2006 06:58:51 -0000 Le Monday 23 January 2006 22:27, Peter Jeremy a écrit : > On Mon, 2006-Jan-23 20:41:17 +0100, Thierry Herbelot wrote: > >panic: vm_page_free_toq: freeing mapped page 0xc11fae58 > > Sam Leffler has suggested that Alan Cox's latest sys/kern/vfs_bio.c > change is at fault here. You could try backing out v1.502 and see if > the problem goes away. Thanks for the tip : it seems to have disappeared (at least a more recent kernel, with the indicated file revision boots correctly and is building its world) TfH From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 08:29:01 2006 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 B2FCC16A41F for ; Tue, 24 Jan 2006 08:29:01 +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 4853543D55 for ; Tue, 24 Jan 2006 08:29:01 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (2qiz3ssuqqrujakm@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id k0O8Ru5d092320; Tue, 24 Jan 2006 00:27:57 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id k0O8RtdE092319; Tue, 24 Jan 2006 00:27:56 -0800 (PST) (envelope-from jmg) Date: Tue, 24 Jan 2006 00:27:55 -0800 From: John-Mark Gurney To: Kris Kennaway Message-ID: <20060124082755.GB69162@funkthat.com> Mail-Followup-To: Kris Kennaway , current@FreeBSD.org References: <20060122194129.GZ69162@funkthat.com> <20060122201233.GA59053@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060122201233.GA59053@xor.obsecurity.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: current@FreeBSD.org Subject: Re: memory corruption in recent -current? 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: Tue, 24 Jan 2006 08:29:01 -0000 Kris Kennaway wrote this message on Sun, Jan 22, 2006 at 15:12 -0500: > On Sun, Jan 22, 2006 at 11:41:29AM -0800, John-Mark Gurney wrote: > > I've been working on a BT878 audio driver (first crack is available > > in p4), and with a recent -current (you can sync to my -current as > > it's the one in my workspace, jmg_carbon), I get memory corruption: > > Memory modified after free 0xc2fb1050(12) val=1c @ 0xc2fb1050 > > panic: Most recently used by ioctlops > > or: > > Memory modified after free 0xc2ba2b90(12) val=1c @ 0xc2ba2b90 > > panic: Most recently used by Unitno > > > > I went back to a kerenl that is pre-Dec 21st, and I haven't had a single > > panic yet. I will admit I haven't done a builtworld between the these > > two (the last buildworld matched with the pre-Dec 21st kernel)... I am > > using kld modules for my testing, so I was building modules against an > > old world, but I don't know of anything that has changed that would > > cause problems.. > > > > Anyone else seeing this? > > Use memguard to track down the cause. Well, looks like memguard is broken? I just ran it, and got this panic: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x800 fault code = supervisor write, page not present instruction pointer = 0x20:0xc0611c46 stack pointer = 0x28:0xd1d36c28 frame pointer = 0x28:0xd1d36c3c 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 = 868 (bktrautest) [thread pid 868 tid 100088 ] Stopped at memguard_free+0x12: movl $0xd34dc0d3,0x800(%esi) db> tr Tracing pid 868 tid 100088 td 0xc3916820 memguard_free(2e,e,80044105,4,d1d36c80) at memguard_free+0x12 free(2e,c06d4360,2e,2e,0) at free+0x27 ioctl(c3916820,d1d36d04,c3916820,0,2) at ioctl+0x272 syscall(3b,3b,3b,2804fa28,bfbfe8c8) at syscall+0x27e Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x28131e53, esp = 0xbfbfe6ec, ebp = 0xbfbfe828 --- ok, the backtrace: #11 0xc064a9fa in calltrap () at ../../../i386/i386/exception.s:137 #12 0xc0611c46 in memguard_free (addr=0x0) at ../../../vm/memguard.c:272 #13 0xc04eb2df in free (addr=0x2e, mtp=0xc06d4360) at ../../../kern/kern_malloc.c:356 #14 0xc051c98a in ioctl (td=0xc3916820, uap=0xd1d36d04) at ../../../kern/sys_generic.c:589 #15 0xc065e296 in syscall (frame= {tf_fs = 59, tf_es = 59, tf_ds = 59, tf_edi = 671414824, tf_esi = -1077942072, tf_ebp = -1077942232, tf_isp = -774673052, tf_ebx = 6, tf_edx = 6, tf_ecx = 0, tf_eax = 54, tf_trapno = 12, tf_err = 2, tf_eip = 672341587, tf_cs = 51, tf_eflags = 662, tf_esp = -1077942548, tf_ss = 59}) at ../../../i386/i386/trap.c:1008 #16 0xc064aa4f in Xint0x80_syscall () at ../../../i386/i386/exception.s:190 It's wierd that free is free'ing an address of 0x2e, and it looks like the copyin faulted w/ EFAULT probably because of the bad address in kernel space, not userland... though the memory address shouldn't be invalid, as the size (4) should of been allocated by: 580 memp = malloc((u_long)size, M_IOCTLOPS, M_WAITOK); and should of waited as necessary... Comments anyone? I have the dump around if anyone needs more information. -- 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 Tue Jan 24 08:34:58 2006 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 E8EC216A41F for ; Tue, 24 Jan 2006 08:34:58 +0000 (GMT) (envelope-from ihsan@dogan.ch) Received: from mail.blastwave.org (mail.blastwave.org [147.87.98.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5507043D49 for ; Tue, 24 Jan 2006 08:34:51 +0000 (GMT) (envelope-from ihsan@dogan.ch) Received: from localhost (localhost [127.0.0.1]) by mail.blastwave.org (Postfix) with ESMTP id E28A9F8B3 for ; Tue, 24 Jan 2006 09:34:48 +0100 (MET) Received: from mail.blastwave.org ([127.0.0.1]) by localhost (enterprise.blastwave.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 23526-01-8 for ; Tue, 24 Jan 2006 09:34:46 +0100 (MET) Received: from defiant.dogan.ch (defiant.dogan.ch [213.144.141.146]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by mail.blastwave.org (Postfix) with ESMTP id 89708F8AF for ; Tue, 24 Jan 2006 09:34:46 +0100 (MET) Received: by defiant.dogan.ch (Postfix, from userid 1000) id C3601179C3; Tue, 24 Jan 2006 09:34:45 +0100 (CET) Date: Tue, 24 Jan 2006 09:34:45 +0100 From: Ihsan Dogan To: freebsd-current@freebsd.org Message-ID: <20060124083445.GK5114@dogan.ch> Mail-Followup-To: freebsd-current@freebsd.org References: <17358.59598.606852.426971@roam.psg.com> <20060119112211.24ce1a86.lists@yazzy.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060119112211.24ce1a86.lists@yazzy.org> X-Operating-System: NetBSD/i386 1.6.2 X-Binford: 6100 (more power) X-Editor: Vim-603 http://www.vim.org User-Agent: Mutt/1.5.10i X-Virus-Scanned: amavisd-new at blastwave.org Subject: Re: thinkpad suspend X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 08:34:59 -0000 On Thursday, 19 Jan 2006 11:22 +0100, Marcin Jessa wrote: > > what are the tricks of the week for t41s? i removed the hacks > > to > > > > /etc/rc.suspend > > /usr/X11R6/bin/xset -display :0 dpms force off > > sleep 3 > > sysctl hw.acpi.video.lcd0.active=0 > > > > /etc/rc.resume > > /usr/X11R6/bin/xset -display :0 dpms force on > > sysctl hw.acpi.video.lcd0.active=1 > > > > now it comes back, but never exits zzz and ignores keyboard, ... > > it has the symptoms of x sickness, but i am not sure. > > I'm not sure if this will apply to your T41s but you can give it a shot: > http://www.yazzy.org/configs/freebsd/thinkpad/ Does it also work with the T42? Ihsan -- ihsan@dogan.ch http://ihsan.dogan.ch/ From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 08:40:02 2006 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 2F15F16A41F for ; Tue, 24 Jan 2006 08:40:02 +0000 (GMT) (envelope-from freebsd@contexthosting.net) Received: from mail.contexthosting.net (inception.contexthosting.net [209.120.245.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AB0443D49 for ; Tue, 24 Jan 2006 08:40:01 +0000 (GMT) (envelope-from freebsd@contexthosting.net) Received: (qmail 49248 invoked by uid 89); 24 Jan 2006 08:40:00 -0000 Received: by simscan 1.0.7 ppid: 49241, pid: 49246, t: 0.0325s scanners:none Received: from unknown (HELO ?192.168.1.100?) (jim@contexthosting.net@68.80.252.242) by mail.contexthosting.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 24 Jan 2006 08:40:00 -0000 Message-ID: <43D5E7DE.7020206@contexthosting.net> Date: Tue, 24 Jan 2006 03:39:58 -0500 From: Jim Keller User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <43D5754E.9010804@contexthosting.net> In-Reply-To: <43D5754E.9010804@contexthosting.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD 4.9 won't upgrade ? [solution] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 08:40:02 -0000 On a suggestion from Andrew Atrens (thanks!), I checked to verify that my boot and root partitions were in sync, and, as it turns out, they weren't. The kernel was loading from ad0, but my system is located on a 3ware device, twe0. ad0 was an old BSD install that made its way into the system as an extra drive (I hadn't concerned myself with it since this machine is not in production anyway), and the kernel was loading from that one. I went into my BIOS and got rid of the IDE hard drive from the boot device list, forcing it to boot from the SCSI first. Everything came up correctly after that, my system and kernel are now in sync. -Jim Keller Jim Keller wrote: > Hey all, > I have a FreeBSD 4.9 machine here that simply doesn't want to > upgrade, though the buildworld/installworld process seems to go > successfully. I'm just trying to go to 4.11 at the moment. I've done > the installworld process on more than a few machines before without > any problems (following the steps outlined in the handbook). However, > on this machine, I go through the whole process, and although it does > appear to recompile the system (my openssl went from the original > distro to the newest version, for example), uname -a is still > reporting the distro as 4.9-RELEASE. Also, it will not install a > custom kernel, it always goes to GENERIC, even when I specify > KERNCONF= in the buildkernel process. I've CVSUP'd my source twice > (currently my tag is RELENG_4_11) and run the whole process twice, > including starting with removing /usr/obj and doing a double make > cleandir in /usr/src. Any ideas? Thanks. > > -Jim Keller > _______________________________________________ > 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 Jan 24 08:51:04 2006 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 E1F8716A425 for ; Tue, 24 Jan 2006 08:51:04 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from mail.yazzy.org (mail.yazzy.org [217.8.140.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57C5D43D55 for ; Tue, 24 Jan 2006 08:51:04 +0000 (GMT) (envelope-from lists@yazzy.org) Received: from [84.247.144.144] (helo=marcin) by mail.yazzy.org with esmtps (TLSv1:AES256-SHA:256) (YazzY.org) id 1F1Jso-0000px-83; Tue, 24 Jan 2006 09:50:35 +0100 Date: Tue, 24 Jan 2006 09:51:06 +0100 From: Marcin Jessa To: Ihsan Dogan Message-Id: <20060124095106.3f10d839.lists@yazzy.org> In-Reply-To: <20060124083445.GK5114@dogan.ch> References: <17358.59598.606852.426971@roam.psg.com> <20060119112211.24ce1a86.lists@yazzy.org> <20060124083445.GK5114@dogan.ch> Organization: YazzY.org X-Mailer: Sylpheed version 2.0.4 (GTK+ 2.8.9; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Score: -2.2 (--) Cc: freebsd-current@freebsd.org Subject: Re: thinkpad suspend X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 08:51:05 -0000 On Tue, 24 Jan 2006 09:34:45 +0100 Ihsan Dogan wrote: > On Thursday, 19 Jan 2006 11:22 +0100, Marcin Jessa wrote: > > > > what are the tricks of the week for t41s? i removed the hacks > > > to > > > > > > /etc/rc.suspend > > > /usr/X11R6/bin/xset -display :0 dpms force off > > > sleep 3 > > > sysctl hw.acpi.video.lcd0.active=0 > > > > > > /etc/rc.resume > > > /usr/X11R6/bin/xset -display :0 dpms force on > > > sysctl hw.acpi.video.lcd0.active=1 > > > > > > now it comes back, but never exits zzz and ignores keyboard, ... > > > it has the symptoms of x sickness, but i am not sure. > > > > I'm not sure if this will apply to your T41s but you can give it a > > shot: http://www.yazzy.org/configs/freebsd/thinkpad/ > > Does it also work with the T42? You tell me... Check also out: http://www.mathematik.uni-marburg.de/~schmidtm/ibm/ and http://gerda.univie.ac.at/freebsd-laptops/index.pl?action=list_laptop_mf&mfid=1 From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 09:47:36 2006 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 67DAC16A41F for ; Tue, 24 Jan 2006 09:47:36 +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 D6C4743D48 for ; Tue, 24 Jan 2006 09:47:35 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (es7bo0tqbzfu21lc@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id k0O9kWdT094294 for ; Tue, 24 Jan 2006 01:46:32 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id k0O9kVIZ094293 for current@FreeBSD.org; Tue, 24 Jan 2006 01:46:31 -0800 (PST) (envelope-from jmg) Date: Tue, 24 Jan 2006 01:46:31 -0800 From: John-Mark Gurney To: current@FreeBSD.org Message-ID: <20060124094631.GE69162@funkthat.com> Mail-Followup-To: current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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: Subject: panic: vm_page_insert: page already inserted 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: Tue, 24 Jan 2006 09:47:36 -0000 Ok, now another panic that doesn't involve my code. Simply loading the bktr module causes this: login: bktr_mem: memory holder loaded bktr0: mem 0xe7005000-0xe7005fff irq 11 at device 11.0 on pci0 bktr0: [GIANT-LOCKED] smbus0: on bktr0 iicbb0: on bktr0 iicbus0: on iicbb0 master-only panic: vm_page_insert: page already inserted cpuid = 0 KDB: enter: panic [thread pid 662 tid 100090 ] Stopped at kdb_enter+0x2b: nop db> tr Tracing pid 662 tid 100090 td 0xc3916510 kdb_enter(c0694489) at kdb_enter+0x2b panic(c06abef1,0,0,c1655fb8,d1d30a90) at panic+0x127 vm_page_insert(c1655fb8,c075a440,11eb1,0) at vm_page_insert+0x36 contigmalloc2(c1655fb8,8,0,1,c1655fb8) at contigmalloc2+0x106 contigmalloc(8000,c06ce020,1,0,ffffffff) at contigmalloc+0x95 get_bktr_mem(0,8000,11,36e109e,36e109e) at get_bktr_mem+0x20 common_bktr_attach(c3959000,0,36e109e,11,0) at common_bktr_attach+0x34 bktr_attach(c366d200) at bktr_attach+0x37a device_attach(c366d200,c366d200,c366d200,a,c3670300) at device_attach+0x58 device_probe_and_attach(c366d200,c366d200,c3670300) at device_probe_and_attach+0xe0 pci_driver_added(c3661880,c3ac85b4) at pci_driver_added+0xd1 devclass_add_driver(c35ad840,c3ac85b4,c3949900,c3ac8594,c390fc20) at devclass_add_driver+0xb7 driver_module_handler(c3949900,0,c3ac85a0,c06fad00,c069362f) at driver_module_handler+0x59 module_register_init(c3ac8594) at module_register_init+0x52 linker_file_sysinit(c39acc00,c39acc00,1,c39acc00,c390fc20) at linker_file_sysinit+0x7d linker_load_file(c390fc20,d1d30c44,400,0,c378ec00) at linker_load_file+0xce linker_load_module(0,c378ec00,0,0,d1d30c70) at linker_load_module+0xb7 kldload(c3916510,d1d30d04,c,c3916510,d1d30d30) at kldload+0xcb syscall(3b,3b,3b,0,bfbfe8e8) at syscall+0x27e Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (304, FreeBSD ELF32, kldload), eip = 0x280baf83, esp = 0xbfbfe85c, ebp = 0xbfbfe898 --- db> I thought it was reproducable, but I haven't been able to reproduce it, though it happened to be before.. and unluckily the dump failed.. Dumping 375 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 375MB (95984 pages) 359 343 327 311 295 279 263 247 231 215 199 183 167 151ad0: FAILURE - out of memory in start ... fail ** DUMP FAILED (ERROR 12) ** Though w/ the new ata DMA dumping code, it went a bit faster.. -- 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 Tue Jan 24 10:04:18 2006 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 8CD4D16A41F; Tue, 24 Jan 2006 10:04:18 +0000 (GMT) (envelope-from cbh-freebsd-current@groups.chrishedley.com) Received: from lon-mail-4.gradwell.net (lon-mail-4.gradwell.net [193.111.201.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC10B43D58; Tue, 24 Jan 2006 10:04:13 +0000 (GMT) (envelope-from cbh-freebsd-current@groups.chrishedley.com) Received: from 53-233.adsl.zetnet.co.uk ([194.247.53.233] helo=mail.chrishedley.com ident=postmaster$pop3^chrishedley#com) by lon-mail-4.gradwell.net with esmtpa (Gradwell gwh-smtpd 1.207) id 43d5fb9c.6d85.5; Tue, 24 Jan 2006 10:04:12 +0000 (envelope-sender ) Received: from localhost (localhost [127.0.0.1]) by mail.chrishedley.com (Postfix) with ESMTP id 11FC2BCB5; Tue, 24 Jan 2006 10:03:56 +0000 (GMT) Received: from mail.chrishedley.com ([127.0.0.1]) by localhost (mail.chrishedley.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 91995-01; Tue, 24 Jan 2006 10:03:54 +0000 (GMT) Received: from teapot.cbhnet (teapot.cbhnet [192.168.1.1]) by mail.chrishedley.com (Postfix) with ESMTP id EEF4FBB5B; Tue, 24 Jan 2006 10:03:53 +0000 (GMT) Date: Tue, 24 Jan 2006 10:03:53 +0000 (GMT) From: Chris Hedley X-X-Sender: cbh@teapot.cbhnet To: John Baldwin In-Reply-To: <200601231624.14321.jhb@freebsd.org> Message-ID: <20060124100055.B84257@teapot.cbhnet> References: <20060123112629.F79825@teapot.cbhnet> <20060123140937.Q81165@teapot.cbhnet> <200601231624.14321.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: amavisd-new at chrishedley.com Cc: freebsd-current@freebsd.org, current@freebsd.org Subject: Re: -CURRENT spontaneously rebooting when using X X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 10:04:18 -0000 On Mon, 23 Jan 2006, John Baldwin wrote: > It's a bug, but you can try this workaround: Unfortunately that caused my system to lock up at (presumably) the same point it was crashing before; testing it a couple of times produced the same result. Is there anything you want me to do to try to extract some more details from it? Chris. From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 10:04:18 2006 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 8CD4D16A41F; Tue, 24 Jan 2006 10:04:18 +0000 (GMT) (envelope-from cbh-freebsd-current@groups.chrishedley.com) Received: from lon-mail-4.gradwell.net (lon-mail-4.gradwell.net [193.111.201.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC10B43D58; Tue, 24 Jan 2006 10:04:13 +0000 (GMT) (envelope-from cbh-freebsd-current@groups.chrishedley.com) Received: from 53-233.adsl.zetnet.co.uk ([194.247.53.233] helo=mail.chrishedley.com ident=postmaster$pop3^chrishedley#com) by lon-mail-4.gradwell.net with esmtpa (Gradwell gwh-smtpd 1.207) id 43d5fb9c.6d85.5; Tue, 24 Jan 2006 10:04:12 +0000 (envelope-sender ) Received: from localhost (localhost [127.0.0.1]) by mail.chrishedley.com (Postfix) with ESMTP id 11FC2BCB5; Tue, 24 Jan 2006 10:03:56 +0000 (GMT) Received: from mail.chrishedley.com ([127.0.0.1]) by localhost (mail.chrishedley.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 91995-01; Tue, 24 Jan 2006 10:03:54 +0000 (GMT) Received: from teapot.cbhnet (teapot.cbhnet [192.168.1.1]) by mail.chrishedley.com (Postfix) with ESMTP id EEF4FBB5B; Tue, 24 Jan 2006 10:03:53 +0000 (GMT) Date: Tue, 24 Jan 2006 10:03:53 +0000 (GMT) From: Chris Hedley X-X-Sender: cbh@teapot.cbhnet To: John Baldwin In-Reply-To: <200601231624.14321.jhb@freebsd.org> Message-ID: <20060124100055.B84257@teapot.cbhnet> References: <20060123112629.F79825@teapot.cbhnet> <20060123140937.Q81165@teapot.cbhnet> <200601231624.14321.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: amavisd-new at chrishedley.com Cc: freebsd-current@freebsd.org, current@freebsd.org Subject: Re: -CURRENT spontaneously rebooting when using X X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 10:04:18 -0000 On Mon, 23 Jan 2006, John Baldwin wrote: > It's a bug, but you can try this workaround: Unfortunately that caused my system to lock up at (presumably) the same point it was crashing before; testing it a couple of times produced the same result. Is there anything you want me to do to try to extract some more details from it? Chris. From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 10:19:08 2006 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 421FF16A41F for ; Tue, 24 Jan 2006 10:19:08 +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 25E5643D55 for ; Tue, 24 Jan 2006 10:19:06 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 88115 invoked from network); 24 Jan 2006 10:19:26 -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 ; 24 Jan 2006 10:19:26 -0000 Message-ID: <43D5FF19.7090903@freebsd.org> Date: Tue, 24 Jan 2006 11:19:05 +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, net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Marvell/SysKonnect YukonII source code available X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 10:19:08 -0000 Marvell/SysKonnect made the source code to the YukonII chips available today under a BSD license: http://people.freebsd.org/~andre/mykbsd60x86-8.12.1.3-src.tgz I haven't tested the driver yet and I don't know if it available directly from the their website already. Many thanks to Gerald and Frank at SysKonnect for working with us and making this possible! -- Andre From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 10:53:35 2006 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 62AE416A41F; Tue, 24 Jan 2006 10:53:35 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id D439F43D49; Tue, 24 Jan 2006 10:53:34 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01a ([66.130.198.54]) by VL-MO-MR002.ip.videotron.ca (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTP id <0ITL00BFTFL96JG0@VL-MO-MR002.ip.videotron.ca>; Tue, 24 Jan 2006 05:53:33 -0500 (EST) Date: Tue, 24 Jan 2006 05:53:24 -0500 From: Nicolas Blais In-reply-to: <82eac8c60601240107t5750571xa70b95e439dab9b0@mail.gmail.com> To: =?iso-8859-1?q?S=F8ren_Schmidt?= Message-id: <200601240553.33402.nb_root@videotron.ca> MIME-version: 1.0 Content-type: multipart/signed; boundary=nextPart1402524.S27pdcrO89; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit References: <200601211159.50768.nb_root@videotron.ca> <200601232102.35528.nb_root@videotron.ca> <82eac8c60601240107t5750571xa70b95e439dab9b0@mail.gmail.com> User-Agent: KMail/1.9.1 Cc: Michael Landin Hostbaek , freebsd-current@freebsd.org Subject: Re: -CURRENT freeze at boot after update X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jan 2006 10:53:35 -0000 --nextPart1402524.S27pdcrO89 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 24 January 2006 04:07, S=F8ren Schmidt wrote: > OK, the patch was flawed actually, find two new attached below. > Please try first dma-p1 then dma-p2 and finally both and let me know if > that changes anything. > Thanks! > > -S=F8ren > > > > The only thing that comes to mind is the below patch, please try that > > > out and let me know. However that way the legacy ports (those stuck at > > > irq14 & irq15) cannot share interrupt with *anything*, which I did wa= nt > > > to fix as a side effect of this actually... > > > > > > -S=F8ren > > > > Hi, sorry for the wait. > > > > I recompiled my kernel with your patch, unfortunatly it does nothing to > > prevent the freeze. > > > > If you have any patches, I'm willing to try it. > > > > Thanks, > > Nicolas. > > Hi again, I've tested your patches (very early this morning if you look my sig :) : dma-p1 alone : still freezes dma-p2 alone : no freeze, cdrom now has good ol' dma access back :) both : untested as p2 solved the problem. Good work, if you need anything else tested feel free to ask. Nicolas. =2D-=20 =46reeBSD 7.0-CURRENT #4: Tue Jan 24 05:47:18 EST 2006 =20 nicblais@clk01a:/usr/obj/usr/src/sys/CLK01A=20 PGP? (updated 16 Nov 05) : http://www.clkroot.net/security/nb_root.asc --nextPart1402524.S27pdcrO89 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBD1gct4wTBlvcsbJURAimuAJ9nPHawQaRmZ8GgT/Wdg/78Hn+V8wCcCLMD VLAp9FvxnRLh8F6iPfp9jEs= =U9TC -----END PGP SIGNATURE----- --nextPart1402524.S27pdcrO89-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 11:01:17 2006 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 3D55416A41F; Tue, 24 Jan 2006 11:01:17 +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 D5B6243D45; Tue, 24 Jan 2006 11:01: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.60 (FreeBSD)) (envelope-from ) id 1F1LvG-0006hU-Oa; Tue, 24 Jan 2006 11:01:15 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1F1LvF-0000RN-HJ; Tue, 24 Jan 2006 20:01:13 +0900 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17366.2296.896827.946579@roam.psg.com> Date: Tue, 24 Jan 2006 20:01:12 +0900 To: FreeBSD Current References: <17365.42627.914349.894764@roam.psg.com> Cc: FreeBSD Laptoppers Subject: Re: t41 zzz X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 11:01:17 -0000 > thinkpad t41 running current as of a few hours ago > xorg, gnome 2.21, ... > > if i execute zzz it suspends s3 seemingly quite happily > > when i open lid, there is disk activity, the numlock and > shiftlock lights flash a bit (this was normal behavior > when zzz last worked some weeks back), and the screen > comes back on. but ... > > it never completes the zzz script, i.e. no shell prompt. > if i put an echo in /etc/rc.resume it shows it has been > executed. > > though i can move the cursor with the touchpad, focus > never grabs any window. > > and there is no response to keyboard. > > at kevin oberman's recommendation, i added radionctl > hacks a la > > if [ -x /usr/local/bin/radeontool ]; then > /usr/local/bin/radeontool light on > fi > > to suspend/resume. no effect. > > suggestions on how to fix or even how to debug would > be appreciated. this was fixed, thanks to tobias roth, by removing dri from /etc/XF86Config randy From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 11:46:53 2006 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 F31D116A41F for ; Tue, 24 Jan 2006 11:46:52 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id E7E9D43D45 for ; Tue, 24 Jan 2006 11:46:51 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 24 Jan 2006 11:46:50 -0000 Received: from v208-017.vps.tuwien.ac.at (EHLO v208-017.vps.tuwien.ac.at) [128.131.208.17] by mail.gmx.net (mp035) with SMTP; 24 Jan 2006 12:46:50 +0100 X-Authenticated: #16703784 From: Stefan Ehmann To: John-Mark Gurney In-Reply-To: <20060124094631.GE69162@funkthat.com> References: <20060124094631.GE69162@funkthat.com> Content-Type: text/plain Date: Tue, 24 Jan 2006 12:46:49 +0100 Message-Id: <1138103209.815.6.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: current@FreeBSD.org Subject: Re: panic: vm_page_insert: page already inserted X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 11:46:53 -0000 On Tue, 2006-01-24 at 01:46 -0800, John-Mark Gurney wrote: > Ok, now another panic that doesn't involve my code. Simply loading > the bktr module causes this: I got a similar panic when loading iwi. Unfortunately I have no backtrace right now, just panic message. Panic String: vm_page_insert: page already inserted Little background: I need to unload the if_iwi module before suspend, otherwise resuming sometimes takes very long. So I need to reload it on resume. Sometimes (maybe once in 5 resumes) the kernel panics. I don't know if it's the same panic every time since I'm in X most of the time and the system simply resets. I'll provide a backtrace if I'm able to get a good dump. From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 11:47:21 2006 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 2C88D16A41F for ; Tue, 24 Jan 2006 11:47:21 +0000 (GMT) (envelope-from cbh-freebsd-current@groups.chrishedley.com) Received: from lon-mail-3.gradwell.net (lon-mail-3.gradwell.net [193.111.201.127]) by mx1.FreeBSD.org (Postfix) with ESMTP id 618B943D45 for ; Tue, 24 Jan 2006 11:47:20 +0000 (GMT) (envelope-from cbh-freebsd-current@groups.chrishedley.com) Received: from 53-233.adsl.zetnet.co.uk ([194.247.53.233] helo=mail.chrishedley.com ident=postmaster$pop3*chrishedley#com) by lon-mail-3.gradwell.net with esmtpa (Gradwell gwh-smtpd 1.207) id 43d613c7.a0d7.95 for current@freebsd.org; Tue, 24 Jan 2006 11:47:19 +0000 (envelope-sender ) Received: from localhost (localhost [127.0.0.1]) by mail.chrishedley.com (Postfix) with ESMTP id 9A07BC38D for ; Tue, 24 Jan 2006 11:47:17 +0000 (GMT) Received: from mail.chrishedley.com ([127.0.0.1]) by localhost (mail.chrishedley.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 91995-07 for ; Tue, 24 Jan 2006 11:47:16 +0000 (GMT) Received: from teapot.cbhnet (teapot.cbhnet [192.168.1.1]) by mail.chrishedley.com (Postfix) with ESMTP id D63C8BB40 for ; Tue, 24 Jan 2006 11:47:15 +0000 (GMT) Date: Tue, 24 Jan 2006 11:47:15 +0000 (GMT) From: Chris Hedley X-X-Sender: cbh@teapot.cbhnet To: current@freebsd.org Message-ID: <20060124113647.W84257@teapot.cbhnet> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: amavisd-new at chrishedley.com Cc: Subject: login, telnetd not updating utmp etc 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: Tue, 24 Jan 2006 11:47:21 -0000 I've noticed on recent versions of -CURRENT that utmp, wtmp and lastlog aren't being updated by login and telnetd; however, sshd still seems to be working as expected. This is happening on both my systems so I'm guessing it's not something weird that I'm doing (although I'm open to the possibility that it might be!) I've only noticed this recently as prior to a few days back I'd only been using sshd on my FreeBSD systems, but the older one's telnetd is of 13-Oct-2005 vintage, if that's of any use. Cheers, Chris. From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 12:00:13 2006 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 7230E16A427 for ; Tue, 24 Jan 2006 12:00:13 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail15.syd.optusnet.com.au (mail15.syd.optusnet.com.au [211.29.132.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96CBB43D46 for ; Tue, 24 Jan 2006 12:00:12 +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 mail15.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k0OC0ArJ023508 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 24 Jan 2006 23:00:10 +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 k0OC0AHh038358 for ; Tue, 24 Jan 2006 23:00:10 +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 k0OC09Gi038357 for current@FreeBSD.org; Tue, 24 Jan 2006 23:00:09 +1100 (EST) (envelope-from pjeremy) Date: Tue, 24 Jan 2006 23:00:09 +1100 From: Peter Jeremy To: current@FreeBSD.org Message-ID: <20060124120009.GX25397@cirb503493.alcatel.com.au> References: <20060124094631.GE69162@funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060124094631.GE69162@funkthat.com> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: Subject: Re: panic: vm_page_insert: page already inserted X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Jan 2006 12:00:13 -0000 On Tue, 2006-Jan-24 01:46:31 -0800, John-Mark Gurney wrote: >Ok, now another panic that doesn't involve my code. Simply loading >the bktr module causes this: >panic: vm_page_insert: page already inserted ... >vm_page_insert(c1655fb8,c075a440,11eb1,0) at vm_page_insert+0x36 >contigmalloc2(c1655fb8,8,0,1,c1655fb8) at contigmalloc2+0x106 If you have a crashdump, can you print the vm_page_t at 0xc1655fb8, it's object, the address of kernel_object_store and the vm_object_t at 0xc075a440 if it's not kernel_object_store. I've been seeing these panics with a patched version contigmalloc() and it would be nice to know if there's a bug outside these patches. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Tue Jan 24 08:21:46 2006 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 0AEEB16A41F for ; Tue, 24 Jan 2006 08:21:46 +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 906C743D4C for ; Tue, 24 Jan 2006 08:21:45 +0000 (GMT) (envelope-from samspeedu@mail.ru) Received: from [80.82.44.194] (port=28301 helo=192.168.168.7) by mx3.mail.ru with esmtp id 1F1JQs-000A6F-00 for freebsd-current@freebsd.org; Tue, 24 Jan 2006 11:21:42 +0300 Date: Tue, 24 Jan 2006 11:19:01 +0300 From: Andrey Smagin X-Mailer: The Bat! (v1.62r) Organization: DiP X-Priority: 3 (Normal) Message-ID: <683203400.20060124111901@mail.ru> To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 24 Jan 2006 12:22:09 +0000 Subject: atapicam with DVD drive hang boot 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: Tue, 24 Jan 2006 08:21:46 -0000 Hi, from few days Current to today morning Current, if load atapicam in boot time system freeze, after some minutes repeats: acd0: req=0xc5b10524 TEST_UNIT_READY semaphore timeout !! DANGER Will Robinson !! after about half hour system continues boot. /var/log/messages output Copyright (c) 1992-2006 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 #0: Tue Jan 24 04:43:14 MSK 2006 root@sam.vvt:/usr/src/sys/i386/compile/SAM acpi_alloc_wakeup_handler: can't alloc wake memory Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3000+ (1809.28-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x20ff2 Stepping = 2 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800 AMD Features2=0x1 real memory = 1073676288 (1023 MB) avail memory = 1041211392 (992 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard lockmgr: thread 0xc09dbe40 unlocking unheld lock netsmb_dev: loaded npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.0 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xd2104000-0xd2104fff irq 21 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 8 ports with 8 removable, self powered ehci0: mem 0xd2105000-0xd21050ff irq 22 at device 2.1 on pci0 ehci0: [GIANT-LOCKED] usb1: EHCI version 1.0 usb1: companion controller, 4 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub1: 8 ports with 8 removable, self powered pcm0: port 0xdc00-0xdcff,0xe000-0xe0ff mem 0xd2103000-0xd2103fff irq 23 at device 4.0 on pci0 pcm0: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 6.0 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd800-0xd80f mem 0xd2102000-0xd2102fff irq 21 at device 7.0 on pci0 ata2: on atapci1 ata3: on atapci1 atapci2: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xc400-0xc40f mem 0xd2101000-0xd2101fff irq 22 at device 8.0 on pci0 ata4: on atapci2 ata5: on atapci2 pcib1: at device 9.0 on pci0 pci5: on pcib1 fwohci0: port 0xa000-0xa07f mem 0xd2000000-0xd20007ff irq 19 at device 2.0 on pci5 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:11:d8:00:00:4a:69:61 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:11:d8:4a:69:61 fwe0: Ethernet address: 02:11:d8:4a:69:61 fwe0: if_start running deferred for Giant sbp0: on firewire0 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) emu10kx0: port 0xa400-0xa41f irq 18 at device 5.0 on pci5 pcm1: on emu10kx0 pcm1: pci5: