From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 3 00:11:44 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7607916A403 for ; Sun, 3 Dec 2006 00:11:44 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03D3543CC2 for ; Sun, 3 Dec 2006 00:11:11 +0000 (GMT) (envelope-from kip.macy@gmail.com) Received: by nf-out-0910.google.com with SMTP id x37so3759974nfc for ; Sat, 02 Dec 2006 16:11:34 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BXya03v8EgM3YTCwLrqBNtvZQewMmj8r/2S3XUbaIOHAuSM/Mso4Ou1gTrmv9uBeK2Go9ahuJ7p3aFRRM1Xcespw4KAjLFuSBF3WRQshYOj3c78v6dfaeqwyAI2ivNzh6eIr7nTxBkqWx5K+9j8jHQqsKZp6aGlMUW1QX0Reo3Q= Received: by 10.82.113.6 with SMTP id l6mr1257218buc.1165104693492; Sat, 02 Dec 2006 16:11:33 -0800 (PST) Received: by 10.82.191.20 with HTTP; Sat, 2 Dec 2006 16:11:33 -0800 (PST) Message-ID: Date: Sat, 2 Dec 2006 16:11:33 -0800 From: "Kip Macy" To: "Vishal Patil" , freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: Subject: Re: Tools for FreeBSD development X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 00:11:44 -0000 Qemu / vmware is probably the best way to go at the moment. On 12/2/06, Vishal Patil wrote: > I have recently moved over from Linux to FreeBSD and would like to if there > is something similar to UML (User Mode Linux) for doing kernel development > for FreeBSD. Reading different mailing lists, wikis etc it seems that "qemu" > seems to be the best option. Is this tool used by most of the FreeBSD > developers? > Thanks. > > - Vishal > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 3 00:36:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D4A3716A403 for ; Sun, 3 Dec 2006 00:36:41 +0000 (UTC) (envelope-from stanislav.ochotnicky@kmit.sk) Received: from alibaba.kmit.sk (alibaba.kmit.sk [194.160.28.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8139F43CB7 for ; Sun, 3 Dec 2006 00:36:15 +0000 (GMT) (envelope-from stanislav.ochotnicky@kmit.sk) Received: from localhost (localhost.localdomain [127.0.0.1]) by alibaba.kmit.sk (Postfix) with ESMTP id 4FA8B7F94 for ; Sun, 3 Dec 2006 01:36:37 +0100 (CET) Received: from [10.10.0.6] (gw.kmit.sk [194.160.28.62]) by alibaba.kmit.sk (Postfix) with ESMTP id 84A8F7F84 for ; Sun, 3 Dec 2006 01:36:35 +0100 (CET) Message-ID: <45721C0D.2000101@kmit.sk> Date: Sun, 03 Dec 2006 01:36:29 +0100 From: Stanislav Ochotnicky MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <4571AA86.1060303@kmit.sk> <20061202194840.GD35681@deviant.kiev.zoral.com.ua> In-Reply-To: <20061202194840.GD35681@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit Subject: Re: tracing AND intercepting syscalls? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 00:36:42 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Kostik Belousov wrote: > On Sat, Dec 02, 2006 at 05:32:06PM +0100, Stanislav Ochotnicky wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA256 >> >> Hi >> >> I'm doing some research concerning tracing and intercepting of syscalls. >> Ideally this would be done in userspace. It doesn't have to be >> system-wide. It would be enough if I could fork/exec new process, and >> somehow be noticed every time it makes syscall, with ability to alter >> arguments/return values. I (more or less) need similar interface like >> linux ptrace when called with PTRACE_SYSCALL. systrace utility does the >> same thing in OpenBSD/linux. I've been through some mailing lists and >> their archives, read FreeBSD developers guide,TrustedBSD's MAC framework >> intro, man pages, asked on IRC and god knows what else and couldn't find >> a solution. Here's what I have found out so far about interfaces that >> resemble what I need: >> >> ptrace: unable to trace syscalls, only singlestep, this would be too >> slow imho, not mentioning problems with identifying syscalls. >> > Did you look at PT_SYSCALL, PT_TO_SCE and PT_TO_SCX ptrace(2) facilities ? Cant believe I missed them, although they are not in man page of ptrace. At least on my FreeBSD 6.1. Citing from http://www.freebsd.org/projects/ideas/ "Someone needs to finish the support for PT_SYSCALL in the ptrace() subsystem, and add support for another ptrace() command that will replace the PIOCWAIT and PIOCSTATUS ioctls of procfs (should probably be named PT_WAIT), in order for truss(1) to be able to work without procfs(5). Removing the procfs(5) dependency from ps -e is also desirable." But I'll have a look. >> /proc interface: more or less like ptrace, better with modifying memory >> of process etc. but also unable to trace syscalls > Read the man pages and code of the truss(1) and strace(1) utilities. > Truss is available in base system, strace is in the ports. > Truss is a no way because it can't intercept syscalls. But I really don't understand how I could miss strace, since it's available also on other OSes. Will definitely look into it. Since it's done in userspace, there has to be a way(even if it would be obscure), for me to do the same.Maybe it uses mentioned PT_SYSCALL or such. Anyway this will be enough for me to start. Thanks a lot. >> ktrace: almost there, able to trace syscalls, but it only writes them to >> file, and thus i cannot intercept them. >> >> trustedbsd's MAC framework: i've read manual, looked at source etc. And >> I couldn't find a way to stop at every syscall certain process has made. >> There is mac_syscall() function but as far as I could tell, it only >> registers new syscall. All in all, it seems that it should have some way >> to do this, maybe I just couldn't find it. >> >> If kernel module/change is needed I would appreciate push in right >> direction. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFchwNul7h5FTXf/MRCPkUAJ9gSCjlHd0NFY76p4/eWq+OMoXHEgCeNVAZ AutEBjcAdcvswiYHEC9CdhM= =OWZG -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 3 02:07:51 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AAB2D16A403 for ; Sun, 3 Dec 2006 02:07:51 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 279D843CA8 for ; Sun, 3 Dec 2006 02:07:27 +0000 (GMT) (envelope-from kabaev@gmail.com) Received: by wx-out-0506.google.com with SMTP id s18so3117113wxc for ; Sat, 02 Dec 2006 18:07:50 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type; b=XxrjKeMOEcNaf3gfz/b3/wkDE+3DVQSXn5iAgx8OoC5DFSNs/B8JTvbhN94JFJhcAkRUx+MLdycnHIi1w8XzOWUyfeDjG71SsxssL13gIFEjgMqNuQRxaixPYfzzAVsM/ZEEZGQINcFytBfM+lkIHRZoGD5ncUOYWx0kKyeTiW4= Received: by 10.70.116.1 with SMTP id o1mr12013898wxc.1165111669777; Sat, 02 Dec 2006 18:07:49 -0800 (PST) Received: from kan.dnsalias.net ( [24.34.98.164]) by mx.google.com with ESMTP id 15sm825856wrl.2006.12.02.18.07.48; Sat, 02 Dec 2006 18:07:49 -0800 (PST) Date: Sat, 2 Dec 2006 21:07:41 -0500 From: Alexander Kabaev To: "Vishal Patil" Message-ID: <20061202210741.02e0728a@kan.dnsalias.net> In-Reply-To: References: X-Mailer: Sylpheed-Claws 2.5.2 (GTK+ 2.10.6; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_ColPRB3L16HY_VKOE7RD8Wh; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Tools for FreeBSD development X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 02:07:51 -0000 --Sig_ColPRB3L16HY_VKOE7RD8Wh Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 2 Dec 2006 18:28:57 -0500 "Vishal Patil" wrote: > I have recently moved over from Linux to FreeBSD and would like to if > there is something similar to UML (User Mode Linux) for doing kernel > development for FreeBSD. Reading different mailing lists, wikis etc > it seems that "qemu" seems to be the best option. Is this tool used > by most of the FreeBSD developers? > Thanks. >=20 I personally think that having a dedicated box in disk-less configuration is the best option out there. The ability to quickly go through series of hands/reboots without any associated fsck runs and without the risk of terminally damaging any local FS is priceless. If qemu can be tricked into disk-less booting, it should be just as good though. --=20 Alexander Kabaev --Sig_ColPRB3L16HY_VKOE7RD8Wh Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFcjFyQ6z1jMm+XZYRAmgNAJ9RllE/S6RMevV4UhkHIoYiUc2PbQCfdwcU A5TU8c/eEQyHqASv6PM12Kw= =1Rvd -----END PGP SIGNATURE----- --Sig_ColPRB3L16HY_VKOE7RD8Wh-- From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 3 04:05:16 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F10CC16A403 for ; Sun, 3 Dec 2006 04:05:15 +0000 (UTC) (envelope-from newroswell@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id D216343C9D for ; Sun, 3 Dec 2006 04:04:50 +0000 (GMT) (envelope-from newroswell@gmail.com) Received: by nf-out-0910.google.com with SMTP id x37so3799599nfc for ; Sat, 02 Dec 2006 20:05:13 -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=VQsoyy6jNsg87XxtDuRKtAsDnbGK6+b4+UGXgDKMuSx3jO2UDWDSVELnypkgX65ihrnThafEYh9FKrki9Vfe+L4Ip9jR9CdggnfFIHq/QXMOlLqF1DV4YMIh8GkYn6S8o9vhrnRN+itjdSfG4xRQViKezcHVIkV69KLclY/2k30= Received: by 10.78.57.11 with SMTP id f11mr6332942hua.1165118713526; Sat, 02 Dec 2006 20:05:13 -0800 (PST) Received: by 10.78.192.15 with HTTP; Sat, 2 Dec 2006 20:05:13 -0800 (PST) Message-ID: <375baf50612022005i6b9a174w5d251e710d8cefc@mail.gmail.com> Date: Sat, 2 Dec 2006 20:05:13 -0800 From: "Kevin Sanders" To: "Alexander Kabaev" In-Reply-To: <20061202210741.02e0728a@kan.dnsalias.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20061202210741.02e0728a@kan.dnsalias.net> Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org, Vishal Patil Subject: Re: Tools for FreeBSD development X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 04:05:17 -0000 On 12/2/06, Alexander Kabaev wrote: > I personally think that having a dedicated box in disk-less > configuration is the best option out there. The ability to quickly go > through series of hands/reboots without any associated fsck runs and > without the risk of terminally damaging any local FS is priceless. If > qemu can be tricked into disk-less booting, it should be just as good > though. > > -- > Alexander Kabaev Alexander, when you say disk-less configuration, are you referring to booting from a network image/server? That's an interesting idea. I'm fairly new to FreeBSD development also, and prefer the speed of a dedicated box, but recently suffered my first corrupted beyond repair system. Kevin From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 3 04:43:01 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7B97116A416 for ; Sun, 3 Dec 2006 04:43:01 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outQ.internet-mail-service.net (outQ.internet-mail-service.net [216.240.47.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD25443CA3 for ; Sun, 3 Dec 2006 04:42:36 +0000 (GMT) (envelope-from julian@elischer.org) Received: from shell.idiom.com (HELO idiom.com) (216.240.47.20) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Sat, 02 Dec 2006 20:29:25 -0800 Received: from [192.168.2.4] (home.elischer.org [216.240.48.38]) by idiom.com (8.12.11/8.12.11) with ESMTP id kB34gxov099702; Sat, 2 Dec 2006 20:43:00 -0800 (PST) (envelope-from julian@elischer.org) Message-ID: <457255D3.7070806@elischer.org> Date: Sat, 02 Dec 2006 20:42:59 -0800 From: Julian Elischer User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025) MIME-Version: 1.0 To: Vishal Patil References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Tools for FreeBSD development X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 04:43:01 -0000 Vishal Patil wrote: > I have recently moved over from Linux to FreeBSD and would like to know if > there is something similar to UML (User Mode Linux) for doing kernel > development for FreeBSD. Reading different mailing lists, wikis etc it > seems > that "qemu" seems to be the best option. Is this tool used by most of the > FreeBSD developers? I have used vmware in the past but I think that it probably isn't running at the moment.. qemu is probably the closest... Couurently I use a separate machine connected via serial console and a debugging serial connection for gdb. (you can pick up an old headless pentium PC good enough for this sort of thing for about 200 dollars if you look around.. You can probably get one for free if you try hard enough.. it doesn't have to be fast.. > Thanks. > > - Vishal > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 3 06:26:35 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5B9EE16A412 for ; Sun, 3 Dec 2006 06:26:35 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.FreeBSD.org (Postfix) with SMTP id 9A92243CA2 for ; Sun, 3 Dec 2006 06:26:09 +0000 (GMT) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 8256 invoked by uid 1001); 3 Dec 2006 06:26:48 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Sun, 03 Dec 2006 01:26:48 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17778.28199.840536.382017@bhuda.mired.org> Date: Sun, 3 Dec 2006 01:26:47 -0500 To: Julian Elischer In-Reply-To: <457255D3.7070806@elischer.org> References: <457255D3.7070806@elischer.org> X-Mailer: VM 7.17 under 21.4 (patch 19) "Constant Variable" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.1.5 (Fettercairn) From: Mike Meyer Cc: freebsd-hackers@freebsd.org, Vishal Patil Subject: Re: Tools for FreeBSD development X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 06:26:35 -0000 In <457255D3.7070806@elischer.org>, Julian Elischer typed: > Vishal Patil wrote: > > I have recently moved over from Linux to FreeBSD and would like to know if > > there is something similar to UML (User Mode Linux) for doing kernel > > development for FreeBSD. Reading different mailing lists, wikis etc it > > seems > > that "qemu" seems to be the best option. Is this tool used by most of the > > FreeBSD developers? > I have used vmware in the past but I think that it probably > isn't running at the moment.. qemu is probably the closest... > Couurently I use a separate machine connected via serial console > and a debugging serial connection for gdb. (you can pick up an > old headless pentium PC good enough for this sort of thing for > about 200 dollars if you look around.. You can probably get one > for free if you try hard enough.. it doesn't have to be fast.. $200?! How about $50? Assuming you're not 1) outside the US, 2) talking about some $s other than US$s, or 3) have a lot higher idea of what's "good enough for this sort of thing" than I do. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 3 06:50:38 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 99BD916A407; Sun, 3 Dec 2006 06:50:38 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE4F743C9D; Sun, 3 Dec 2006 06:50:11 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (evge.static.otenet.gr [212.205.236.117]) (authenticated bits=128) by igloo.linux.gr (8.13.8/8.13.8/Debian-2) with ESMTP id kB36o7qh022874 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 3 Dec 2006 08:50:16 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.13.8/8.13.8) with ESMTP id kB36nvx4002562; Sun, 3 Dec 2006 08:49:58 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by kobe.laptop (8.13.8/8.13.8/Submit) id kB36nvDU002561; Sun, 3 Dec 2006 08:49:57 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Sun, 3 Dec 2006 08:49:56 +0200 From: Giorgos Keramidas To: Kevin Sanders Message-ID: <20061203064956.GB2405@kobe.laptop> References: <20061202210741.02e0728a@kan.dnsalias.net> <375baf50612022005i6b9a174w5d251e710d8cefc@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <375baf50612022005i6b9a174w5d251e710d8cefc@mail.gmail.com> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.469, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.73, BAYES_00 -2.60, DNS_FROM_RFC_ABUSE 0.20) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-hackers@freebsd.org, Vishal Patil , freebsd-questions@freebsd.org Subject: Re: Tools for FreeBSD development X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 06:50:38 -0000 On 2006-12-02 20:05, Kevin Sanders wrote: >On 12/2/06, Alexander Kabaev wrote: >> I personally think that having a dedicated box in disk-less >> configuration is the best option out there. [...] > > Alexander, when you say disk-less configuration, are you > referring to booting from a network image/server? That's an > interesting idea. I'm fairly new to FreeBSD development also, > and prefer the speed of a dedicated box, but recently suffered > my first corrupted beyond repair system. Yes, a "diskless" boot is a network-based boot :-) From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 3 08:26:04 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7E8C816A40F for ; Sun, 3 Dec 2006 08:26:04 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2B0E43CA8 for ; Sun, 3 Dec 2006 08:25:38 +0000 (GMT) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.141] (may be forged)) by mxout3.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW06.09) with ESMTP id kB38Q3I3019088 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Sun, 3 Dec 2006 00:26:03 -0800 X-Auth-Received: from [192.168.0.101] (dsl254-013-145.sea1.dsl.speakeasy.net [216.254.13.145]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW06.09) with ESMTP id kB38Q2wK012595 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sun, 3 Dec 2006 00:26:03 -0800 Message-ID: <45728A19.7050300@u.washington.edu> Date: Sun, 03 Dec 2006 00:26:01 -0800 From: Garrett Cooper User-Agent: Thunderbird 1.5.0.8 (X11/20061116) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <20061202210741.02e0728a@kan.dnsalias.net> <375baf50612022005i6b9a174w5d251e710d8cefc@mail.gmail.com> <20061203064956.GB2405@kobe.laptop> In-Reply-To: <20061203064956.GB2405@kobe.laptop> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.2.2.285561, Antispam-Engine: 2.5.0.283055, Antispam-Data: 2006.12.3.1433 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_MEDIA_BODY 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' Subject: Re: Tools for FreeBSD development X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 08:26:04 -0000 Giorgos Keramidas wrote: > On 2006-12-02 20:05, Kevin Sanders wrote: >> On 12/2/06, Alexander Kabaev wrote: >>> I personally think that having a dedicated box in disk-less >>> configuration is the best option out there. [...] >> Alexander, when you say disk-less configuration, are you >> referring to booting from a network image/server? That's an >> interesting idea. I'm fairly new to FreeBSD development also, >> and prefer the speed of a dedicated box, but recently suffered >> my first corrupted beyond repair system. > > Yes, a "diskless" boot is a network-based boot :-) Look into BOOTP for that: . You may want to just use vmware (best reliable solution, IMO but it costs money), depending on what resources you have on hand and what you're trying to accomplish. -Garrett From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 3 10:08:42 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C313616A403 for ; Sun, 3 Dec 2006 10:08:42 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id E635B43CAE for ; Sun, 3 Dec 2006 10:08:15 +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 C62FA46D49; Sun, 3 Dec 2006 05:08:39 -0500 (EST) Date: Sun, 3 Dec 2006 10:08:39 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Stanislav Ochotnicky In-Reply-To: <4571AA86.1060303@kmit.sk> Message-ID: <20061203100714.H40536@fledge.watson.org> References: <4571AA86.1060303@kmit.sk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: tracing AND intercepting syscalls? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 10:08:42 -0000 On Sat, 2 Dec 2006, Stanislav Ochotnicky wrote: > trustedbsd's MAC framework: i've read manual, looked at source etc. And I > couldn't find a way to stop at every syscall certain process has made. There > is mac_syscall() function but as far as I could tell, it only registers new > syscall. All in all, it seems that it should have some way to do this, maybe > I just couldn't find it. As discussed elsewhere in the thread, ptrace() has a syscall trapping facility, although I've not used it so can't speak to how well it works. There are patches to add system call entry and exit hooks to the MAC Framework, but they've not yet been merged. I anticipate that they will ship in FreeBSD 7.0, and may get MFC'd, depending on schedule, etc. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 3 10:13:35 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 352AD16A407; Sun, 3 Dec 2006 10:13:35 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F10A43CA7; Sun, 3 Dec 2006 10:13: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 64B5446D65; Sun, 3 Dec 2006 05:13:34 -0500 (EST) Date: Sun, 3 Dec 2006 10:13:34 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Kevin Sanders In-Reply-To: <375baf50612022005i6b9a174w5d251e710d8cefc@mail.gmail.com> Message-ID: <20061203101026.E40536@fledge.watson.org> References: <20061202210741.02e0728a@kan.dnsalias.net> <375baf50612022005i6b9a174w5d251e710d8cefc@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, Vishal Patil , freebsd-questions@freebsd.org Subject: Re: Tools for FreeBSD development X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 10:13:35 -0000 On Sat, 2 Dec 2006, Kevin Sanders wrote: > On 12/2/06, Alexander Kabaev wrote: >> I personally think that having a dedicated box in disk-less configuration >> is the best option out there. The ability to quickly go through series of >> hands/reboots without any associated fsck runs and without the risk of >> terminally damaging any local FS is priceless. If qemu can be tricked into >> disk-less booting, it should be just as good though. > > Alexander, when you say disk-less configuration, are you referring to > booting from a network image/server? That's an interesting idea. I'm > fairly new to FreeBSD development also, and prefer the speed of a dedicated > box, but recently suffered my first corrupted beyond repair system. This is exactly the setup I use also. Most typically, the setup involves a central development server running -STABLE, with a private network link to a series of crash boxes. The development server NFS exports a file system to use as an NFS root and for file sharing, as well as running tftp and dhcp servers. The test boxes use PXE to boot fom the central server. Each test system has its own exported root, so I can use individual loader.conf's to tell test systems to boot off NFS, boot off local disks, etc. I always load the kernel over NFS using pxeboot, regardless of whether I boot boxes with a local root. You get some very nice effects -- you can easily move boxes between FreeBSD versions by switching out root file system symlinks, you can be building the next kernel while the previous one dumps core, etc. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 3 10:15:08 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B7C6C16A415 for ; Sun, 3 Dec 2006 10:15:08 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 137B543CB0 for ; Sun, 3 Dec 2006 10:14:31 +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 292A546DA0; Sun, 3 Dec 2006 05:14:57 -0500 (EST) Date: Sun, 3 Dec 2006 10:14:57 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Garrett Cooper In-Reply-To: <45728A19.7050300@u.washington.edu> Message-ID: <20061203101352.K40536@fledge.watson.org> References: <20061202210741.02e0728a@kan.dnsalias.net> <375baf50612022005i6b9a174w5d251e710d8cefc@mail.gmail.com> <20061203064956.GB2405@kobe.laptop> <45728A19.7050300@u.washington.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: Tools for FreeBSD development X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 10:15:08 -0000 On Sun, 3 Dec 2006, Garrett Cooper wrote: > Giorgos Keramidas wrote: >> On 2006-12-02 20:05, Kevin Sanders wrote: >>> On 12/2/06, Alexander Kabaev wrote: >>>> I personally think that having a dedicated box in disk-less >>>> configuration is the best option out there. [...] >>> Alexander, when you say disk-less configuration, are you referring to >>> booting from a network image/server? That's an interesting idea. I'm >>> fairly new to FreeBSD development also, and prefer the speed of a >>> dedicated box, but recently suffered my first corrupted beyond repair >>> system. >> >> Yes, a "diskless" boot is a network-based boot :-) > > Look into BOOTP for that: > . > You may want to just use vmware (best reliable solution, IMO but it costs > money), depending on what resources you have on hand and what you're trying > to accomplish. If using FreeBSD on i386/amd64 boxes, use PXE. There are quite a few "instant setup" web pages out there that tell you how to get it running. pxeboot makes life incredibly easy, as you can load kernels, modules, configurations, etc, over NFS. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 3 11:58:42 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3E94816A403 for ; Sun, 3 Dec 2006 11:58:42 +0000 (UTC) (envelope-from stanislav.ochotnicky@kmit.sk) Received: from alibaba.kmit.sk (alibaba.kmit.sk [194.160.28.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AF6943CA2 for ; Sun, 3 Dec 2006 11:58:15 +0000 (GMT) (envelope-from stanislav.ochotnicky@kmit.sk) Received: from localhost (localhost.localdomain [127.0.0.1]) by alibaba.kmit.sk (Postfix) with ESMTP id 3325E7F94 for ; Sun, 3 Dec 2006 12:58:40 +0100 (CET) Received: from [10.10.0.6] (gw.kmit.sk [194.160.28.62]) by alibaba.kmit.sk (Postfix) with ESMTP id 6D81E7F84 for ; Sun, 3 Dec 2006 12:58:39 +0100 (CET) Message-ID: <4572BBE3.7020903@kmit.sk> Date: Sun, 03 Dec 2006 12:58:27 +0100 From: Stanislav Ochotnicky MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <4571AA86.1060303@kmit.sk> <20061203100714.H40536@fledge.watson.org> In-Reply-To: <20061203100714.H40536@fledge.watson.org> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: tracing AND intercepting syscalls? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 11:58:42 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Robert Watson wrote: > As discussed elsewhere in the thread, ptrace() has a syscall trapping > facility, although I've not used it so can't speak to how well it works. As I mentioned earlier, I didn't find any info about ptrace() syscall trapping facility(PT_SYSCALL, PT_TO_SCE and PT_TO_SCX) because it wasn't in the man nor info page about ptrace(). When I was noticeed about theese interfaces, I checked the source and It looks like it should solve my problem. Maybe the man page should be updated accordingly? > There are patches to add system call entry and exit hooks to the MAC > Framework, but they've not yet been merged. I anticipate that they will > ship in FreeBSD 7.0, and may get MFC'd, depending on schedule, etc. That would be certainly nice, if this could be done at system level. There would be certainly lots of tools that could use this (Dtrace perhaps?) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFcrvjul7h5FTXf/MRCCjLAJ9wgU4s8Juvu0GXRD8ck1R0gcQ4HACfeSGU QpRT3q9PBBx2I8/9RMJCMkw= =CTRr -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 3 13:12:20 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CB49F16A40F; Sun, 3 Dec 2006 13:12:20 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2F3C43CAD; Sun, 3 Dec 2006 13:11:53 +0000 (GMT) (envelope-from daichi@freebsd.org) Received: from [192.168.1.101] (dullmdaler.ongs.co.jp [202.216.232.62]) by natial.ongs.co.jp (Postfix) with ESMTP id E8FDD244C19; Sun, 3 Dec 2006 22:12:18 +0900 (JST) Message-ID: <4572CD32.4070708@freebsd.org> Date: Sun, 03 Dec 2006 22:12:18 +0900 From: Daichi GOTO User-Agent: Thunderbird 1.5.0.8 (X11/20061118) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, freebsd-fs@freebsd.org, rodrigc@crodrigues.org References: <4570305A.4010908@freebsd.org> In-Reply-To: <4570305A.4010908@freebsd.org> Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit Cc: Daichi GOTO , ozawa@ongs.co.jp Subject: Re: [ANN] unionfs patchset-17 release, lock mechanism changed for robust working X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 13:12:20 -0000 Hi guys, it's congratulations! It is a red-letter day for new FreeBSD unionfs. The unionfs-17.diff (without patch for sys/kern/vfs_lookup.c) was committed to FreeBSD 7-current of 2006-12-02 19:35:56 UTC by rodrigc, my src mentor. > Current English document of web has some Japanese contents. We > need a translator ;-) Hiroharu TAMARU-san gave us good English text. Thanks. And we added some text around committed of current. http://people.freebsd.org/~daichi/unionfs/ (English) http://people.freebsd.org/~daichi/unionfs/index-ja.html (Japanese) Hopefully we can get more feedback from testers :) -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 3 16:23:34 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E072216A47E for ; Sun, 3 Dec 2006 16:23:34 +0000 (UTC) (envelope-from newroswell@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0E4D43CB8 for ; Sun, 3 Dec 2006 16:22:58 +0000 (GMT) (envelope-from newroswell@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so2490635uge for ; Sun, 03 Dec 2006 08:23:25 -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=YzgF3SDV4pFMvihReUxlgc8x5NDIUXaYWmFdClZ29hWxtHVAl5r53uBoSmBKDBgZARgIOtwrUFiasCZgJfHY4bwoVE7a5WNSuo3JK9vgiogKog69V4LzCBVolvPzglpF0f1DlcsLqxY5uRdpc85p45BQ49SR5Yz68bUElEtdzwY= Received: by 10.78.136.9 with SMTP id j9mr6845547hud.1165163004347; Sun, 03 Dec 2006 08:23:24 -0800 (PST) Received: by 10.78.192.15 with HTTP; Sun, 3 Dec 2006 08:23:24 -0800 (PST) Message-ID: <375baf50612030823p189d30f8j88507c058ce03e1f@mail.gmail.com> Date: Sun, 3 Dec 2006 08:23:24 -0800 From: "Kevin Sanders" To: "Robert Watson" In-Reply-To: <20061203101352.K40536@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20061202210741.02e0728a@kan.dnsalias.net> <375baf50612022005i6b9a174w5d251e710d8cefc@mail.gmail.com> <20061203064956.GB2405@kobe.laptop> <45728A19.7050300@u.washington.edu> <20061203101352.K40536@fledge.watson.org> Cc: freebsd-hackers@freebsd.org, Garrett Cooper Subject: Re: Tools for FreeBSD development X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 16:23:35 -0000 On 12/3/06, Robert Watson wrote: > If using FreeBSD on i386/amd64 boxes, use PXE. There are quite a few "instant > setup" web pages out there that tell you how to get it running. pxeboot makes > life incredibly easy, as you can load kernels, modules, configurations, etc, > over NFS. > > Robert N M Watson > Computer Laboratory > University of Cambridge Thanks for th tips everyone. My shop has all the VMware tools, and I've used QEMU, but I prefer to develop on a real box and debug over a serial port on a second box. I'll give pxeboot a shot tomorrow. While we're on this topic, what is the best way to debug kernel modules. I would like the ability to kldload my kernel module, set a couple break points and single step through a section of code (at least). I've read Greg Lehey's http://www.lemis.com/papers/Taiwan/tutorial.pdf but it seems a little out of date. From what I gather, the situation with the kernel debugger has changed since he wrote it. Kevin From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 3 18:43:37 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 83C0416A412 for ; Sun, 3 Dec 2006 18:43:37 +0000 (UTC) (envelope-from freebsd-jobs@bebik.net) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 392D943C9D for ; Sun, 3 Dec 2006 18:43:09 +0000 (GMT) (envelope-from freebsd-jobs@bebik.net) Received: from [192.168.0.19] (gam75-4-82-235-223-127.fbx.proxad.net [82.235.223.127]) by smtp5-g19.free.fr (Postfix) with ESMTP id 6B4ED27A32 for ; Sun, 3 Dec 2006 19:43:35 +0100 (CET) Message-ID: <45731AAE.1080904@bebik.net> Date: Sun, 03 Dec 2006 19:42:54 +0100 From: ros User-Agent: Thunderbird 1.5.0.2 (X11/20060613) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Error burning CD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 18:43:37 -0000 Trying to burn a RW CDROM, I notice the CD-ROM device was freeze and nothing happen. After a hard reboot (I turn off completly the computer), I find this message on the /var/log/message file Dec 3 19:04:40 bill kernel: acd0: req=0xc24e5258 SEND_OPC_INFO semaphore timeout !! DANGER Will Robinson !! Dec 3 19:04:42 bill kernel: acd0: req=0xc2063258 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 3 18:40:06 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5ED7516A403 for ; Sun, 3 Dec 2006 18:40:06 +0000 (UTC) (envelope-from ros@bebik.net) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BDE843CAB for ; Sun, 3 Dec 2006 18:39:37 +0000 (GMT) (envelope-from ros@bebik.net) Received: from [192.168.0.19] (gam75-4-82-235-223-127.fbx.proxad.net [82.235.223.127]) by smtp5-g19.free.fr (Postfix) with ESMTP id A009B27B58 for ; Sun, 3 Dec 2006 19:40:04 +0100 (CET) Message-ID: <457319DC.7030403@bebik.net> Date: Sun, 03 Dec 2006 19:39:24 +0100 From: ros User-Agent: Thunderbird 1.5.0.2 (X11/20060613) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 03 Dec 2006 19:31:31 +0000 Subject: Burning RW cdrom error message X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 18:40:06 -0000 Trying to burn a RW CDROM, I notice the CD-ROM device was freeze and nothing happen. After a hard reboot (I turn off completly the computer), I find this message on the /var/log/message file Dec 3 19:04:40 bill kernel: acd0: req=0xc24e5258 SEND_OPC_INFO semaphore timeout !! DANGER Will Robinson !! Dec 3 19:04:42 bill kernel: acd0: req=0xc2063258 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 3 19:07:36 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4E9C916A4FC for ; Sun, 3 Dec 2006 19:07:36 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE20543D77 for ; Sun, 3 Dec 2006 19:06:42 +0000 (GMT) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (p54A5D756.dip.t-dialin.net [84.165.215.86]) by redbull.bpaserver.net (Postfix) with ESMTP id E36392E0A7; Sun, 3 Dec 2006 20:07:02 +0100 (CET) Received: from Magellan.Leidinger.net (Magellan.Leidinger.net [192.168.1.1]) by outgoing.leidinger.net (Postfix) with ESMTP id BE1135B4C6C; Sun, 3 Dec 2006 20:06:39 +0100 (CET) Date: Sun, 3 Dec 2006 20:07:34 +0100 From: Alexander Leidinger To: "Kevin Sanders" Message-ID: <20061203200734.4a678cdc@Magellan.Leidinger.net> In-Reply-To: <375baf50612030823p189d30f8j88507c058ce03e1f@mail.gmail.com> References: <20061202210741.02e0728a@kan.dnsalias.net> <375baf50612022005i6b9a174w5d251e710d8cefc@mail.gmail.com> <20061203064956.GB2405@kobe.laptop> <45728A19.7050300@u.washington.edu> <20061203101352.K40536@fledge.watson.org> <375baf50612030823p189d30f8j88507c058ce03e1f@mail.gmail.com> X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.10.6; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-14.787, required 6, autolearn=not spam, BAYES_00 -15.00, DK_POLICY_SIGNSOME 0.00, FORGED_RCVD_HELO 0.14, TW_PX 0.08) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No X-Mailman-Approved-At: Sun, 03 Dec 2006 19:31:41 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: Tools for FreeBSD development X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 19:07:36 -0000 Quoting "Kevin Sanders" (Sun, 3 Dec 2006 08:23:24 -0800): > On 12/3/06, Robert Watson wrote: > > If using FreeBSD on i386/amd64 boxes, use PXE. There are quite a few "instant > > setup" web pages out there that tell you how to get it running. pxeboot makes > > life incredibly easy, as you can load kernels, modules, configurations, etc, > > over NFS. > > > > Robert N M Watson > > Computer Laboratory > > University of Cambridge > > Thanks for th tips everyone. My shop has all the VMware tools, and > I've used QEMU, but I prefer to develop on a real box and debug over a > serial port on a second box. I'll give pxeboot a shot tomorrow. > > While we're on this topic, what is the best way to debug kernel > modules. I would like the ability to kldload my kernel module, set a > couple break points and single step through a section of code (at > least). cd # I'm using the old way of building make gdbinit In kgdb you can now use "getsyms" if you debug remotely (I haven't tested this) or "kldsyms" if you debug locally to load the debug symbols. Bye, Alexander. -- Groundskeepers stole the root password http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 3 20:16:44 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7948016A415; Sun, 3 Dec 2006 20:16:44 +0000 (UTC) (envelope-from tataz@tataz.chchile.org) Received: from smtp8-g19.free.fr (smtp8-g19.free.fr [212.27.42.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id B06D943CBC; Sun, 3 Dec 2006 20:16:10 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (tataz.chchile.org [82.233.239.98]) by smtp8-g19.free.fr (Postfix) with ESMTP id ABF5853F8; Sun, 3 Dec 2006 21:16:37 +0100 (CET) Received: from obiwan.tataz.chchile.org (unknown [192.168.1.25]) by tatooine.tataz.chchile.org (Postfix) with ESMTP id 9D8989B465; Sun, 3 Dec 2006 20:17:30 +0000 (UTC) Received: by obiwan.tataz.chchile.org (Postfix, from userid 1000) id 6F520408C; Sun, 3 Dec 2006 21:17:30 +0100 (CET) Date: Sun, 3 Dec 2006 21:17:30 +0100 From: Jeremie Le Hen To: Matteo Riondato , freesbie@gufi.org, varie@gufi.org, freebsd-small@freebsd.org, freebsd-hackers@freebsd.org Message-ID: <20061203201730.GA4369@obiwan.tataz.chchile.org> References: <20061126195124.GA2636@kaiser.sig11.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0F1p//8PRICkK4MW" Content-Disposition: inline In-Reply-To: <20061126195124.GA2636@kaiser.sig11.org> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: Subject: Re: Announce: FreeSBIE 2.0-RC1 is available X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 20:16:44 -0000 --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi Matteo, On Sun, Nov 26, 2006 at 08:51:24PM +0100, Matteo Riondato wrote: > if you followed the development of FreeSBIE 2.0 a bit, you should > remember that, back in Semptember, I said that FreeSBIE 2.0 would have > been the last of a series of four ISO images. Three images were > already published: FreeSBIE GMV back in August, FreeSBIE LVC in > October, FreeSBIE 2.0-BETA in November. Well, circustamces make > me release a fourth ISO image which is *not* FreeSBIE 2.0, but > FreeSBIE 2.0-RC1 (Release Candidate 1). This is due to the number of > bugs which had been fixed after 2.0-BETA was release. > If no major bugs are found, FreeSBIE 2.0 is going to be released not > too long after FreeBSD 6.2-RELEASE has been released. Hopefully you > will be able to put a FreeSBIE 2.0 CD-ROM under your Christmas tree. > :) > > FreeSBIE 2.0-RC1 is based on the RELENG_6_2 branch of the FreeBSD > source tree and on the RELEASE_6_2_0 branch of the ports tree. > > Testing the ISO image, finding bugs and reporting them back to me or > to the freesbie@gufi.org mailing list are the foci for those who want > to give this ISO image a try, and I hope many of you will. There is > still a lot of free space on the ISO image, so feel free to suggest > additional software to include. First, thank you for the work on FreeSBIE. I've just booted it, and it is simply neat. I like it. Unfortunately, I can't get X to work. It seems to be correctly launched but the screen is blank. I've attached Xorg.0.log and my dmesg output. Please, feel free to ask for more informations. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="Xorg.0.log" X Window System Version 6.9.0 Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 6.9 Build Operating System: FreeBSD 6.2 i386 [ELF] Current Operating System: FreeBSD FreeSBIE.LiveCD 6.2-RC1 FreeBSD 6.2-RC1 #26: Thu Nov 23 22:49:20 UTC 2006 root@kaiser.sig11.org:/usr/obj.gmv-i386/usr/src/sys/FREESBIE i386 Build Date: 25 October 2006 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Sun Dec 3 20:10:45 2006 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Layout0" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Input Device "Keyboard0" (**) Option "XkbModel" "pc105" (**) XKB: model: "pc105" (**) Option "XkbLayout" "us" (**) XKB: layout: "us" (==) Keyboard: CustomKeycode disabled (**) |-->Input Device "Mouse0" (WW) The directory "/usr/X11R6/lib/X11/fonts/Type1/" does not exist. Entry deleted from font path. (**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/,/usr/X11R6/lib/X11/fonts/bitstream-vera/,/usr/X11R6/lib/X11/fonts/URW,/usr/X11R6/lib/X11/fonts/urwfonts-ttf/" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" (**) ModulePath set to "/usr/X11R6/lib/modules" (II) Module ABI versions: X.Org ANSI C Emulation: 0.2 X.Org Video Driver: 0.8 X.Org XInput driver : 0.5 X.Org Server Extension : 0.2 X.Org Font Renderer : 0.4 (II) Loader running on freebsd (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.so (II) Module bitmap: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/X11R6/lib/modules/libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.8 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x00000000, mode1Res1 = 0x80000000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2590 card 1025,0066 rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,2591 card 0000,0000 rev 03 class 06,04,00 hdr 01 (II) PCI: 00:1c:0: chip 8086,2660 card 0000,0000 rev 04 class 06,04,00 hdr 81 (II) PCI: 00:1c:1: chip 8086,2662 card 0000,0000 rev 04 class 06,04,00 hdr 81 (II) PCI: 00:1c:2: chip 8086,2664 card 0000,0000 rev 04 class 06,04,00 hdr 81 (II) PCI: 00:1d:0: chip 8086,2658 card 1025,0066 rev 04 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,2659 card 1025,0066 rev 04 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,265a card 1025,0066 rev 04 class 0c,03,00 hdr 00 (II) PCI: 00:1d:3: chip 8086,265b card 1025,0066 rev 04 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,265c card 1025,0066 rev 04 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,2448 card 0000,0000 rev d4 class 06,04,01 hdr 81 (II) PCI: 00:1e:2: chip 8086,266e card 1025,0066 rev 04 class 04,01,00 hdr 00 (II) PCI: 00:1e:3: chip 8086,266d card 1025,0066 rev 04 class 07,03,00 hdr 00 (II) PCI: 00:1f:0: chip 8086,2641 card 1025,0066 rev 04 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,266f card 1025,0066 rev 04 class 01,01,8a hdr 00 (II) PCI: 00:1f:3: chip 8086,266a card 1025,0066 rev 04 class 0c,05,00 hdr 00 (II) PCI: 01:00:0: chip 1002,5653 card 1025,0066 rev 00 class 03,00,00 hdr 00 (II) PCI: 06:01:0: chip 104c,8031 card fffc,ffff rev 00 class 06,07,00 hdr 82 (II) PCI: 06:01:2: chip 104c,8032 card 1025,0066 rev 00 class 0c,00,10 hdr 80 (II) PCI: 06:01:3: chip 104c,8033 card 1025,0066 rev 00 class 01,80,00 hdr 80 (II) PCI: 06:03:0: chip 8086,4220 card 8086,2701 rev 05 class 02,80,00 hdr 00 (II) PCI: 06:08:0: chip 14e4,169c card 1025,0066 rev 03 class 02,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,10), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set) (II) Bus 1 I/O range: [0] -1 0 0x00003000 - 0x000030ff (0x100) IX[B] [1] -1 0 0x00003400 - 0x000034ff (0x100) IX[B] [2] -1 0 0x00003800 - 0x000038ff (0x100) IX[B] [3] -1 0 0x00003c00 - 0x00003cff (0x100) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xc8100000 - 0xc81fffff (0x100000) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0 0xd0000000 - 0xd7ffffff (0x8000000) MX[B] (II) PCI-to-PCI bridge: (II) Bus 9: bridge is at (0:28:0), (0,9,9), BCTRL: 0x0004 (VGA_EN is cleared) (II) PCI-to-PCI bridge: (II) Bus 10: bridge is at (0:28:1), (0,10,10), BCTRL: 0x0004 (VGA_EN is cleared) (II) PCI-to-PCI bridge: (II) Bus 2: bridge is at (0:28:2), (0,2,4), BCTRL: 0x0004 (VGA_EN is cleared) (II) Subtractive PCI-to-PCI bridge: (II) Bus 6: bridge is at (0:30:0), (0,6,7), BCTRL: 0x0004 (VGA_EN is cleared) (II) Bus 6 non-prefetchable memory range: [0] -1 0 0xc8200000 - 0xc82fffff (0x100000) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (II) PCI-to-CardBus bridge: (II) Bus 7: bridge is at (6:1:0), (6,7,7), BCTRL: 0x0744 (VGA_EN is cleared) (--) PCI:*(1:0:0) ATI Technologies Inc Radeon Mobility X700 (PCIE) rev 0, Mem @ 0xd0000000/27, 0xc8100000/16, I/O @ 0x3000/8 (II) Addressable bus resource ranges are [0] -1 0 0x00000000 - 0xffffffff (0x0) MX[B] [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) PCI Memory resource overlap reduced 0xc8000000 from 0xcfffffff to 0xc80fffff (II) Active PCI resource ranges: [0] -1 0 0xc8200000 - 0xc83fffff (0x200000) MX[B]E [1] -1 0 0xc8218000 - 0xc821ffff (0x8000) MX[B]E [2] -1 0 0xc8214000 - 0xc8217fff (0x4000) MX[B]E [3] -1 0 0xc8210000 - 0xc821ffff (0x10000) MX[B]E [4] -1 0 0xc8217000 - 0xc8217fff (0x1000) MX[B]E [5] -1 0 0xc8000400 - 0xc80007ff (0x400) MX[B]E [6] -1 0 0xc8000800 - 0xc8000fff (0x800) MX[B]E [7] -1 0 0xc8000000 - 0xc80fffff (0x100000) MX[B]E [8] -1 0 0xc8100000 - 0xc810ffff (0x10000) MX[B](B) [9] -1 0 0xd0000000 - 0xd7ffffff (0x8000000) MX[B](B) [10] -1 0 0x000020a0 - 0x000020bf (0x20) IX[B]E [11] -1 0 0x000018c0 - 0x000018ff (0x40) IX[B]E [12] -1 0 0x00002000 - 0x000020ff (0x100) IX[B]E [13] -1 0 0x00002400 - 0x000024ff (0x100) IX[B]E [14] -1 0 0x00001880 - 0x000018ff (0x80) IX[B]E [15] -1 0 0x00001c00 - 0x00001cff (0x100) IX[B]E [16] -1 0 0x00001860 - 0x0000187f (0x20) IX[B]E [17] -1 0 0x00001840 - 0x0000187f (0x40) IX[B]E [18] -1 0 0x00001820 - 0x0000183f (0x20) IX[B]E [19] -1 0 0x00001800 - 0x000018ff (0x100) IX[B]E [20] -1 0 0x00003000 - 0x000030ff (0x100) IX[B](B) (II) PCI Memory resource overlap reduced 0xc8200000 from 0xc83fffff to 0xc820ffff (II) PCI Memory resource overlap reduced 0xc8214000 from 0xc8217fff to 0xc8215fff (II) PCI Memory resource overlap reduced 0xc8210000 from 0xc821ffff to 0xc8213fff (II) PCI I/O resource overlap reduced 0x00002000 from 0x000020ff to 0x0000207f (II) PCI I/O resource overlap reduced 0x00001880 from 0x000018ff to 0x000018bf (II) PCI Memory resource overlap reduced 0xc8000000 from 0xc80fffff to 0xc80003ff (II) PCI I/O resource overlap reduced 0x00001840 from 0x0000187f to 0x0000185f (II) PCI I/O resource overlap reduced 0x00001800 from 0x000018ff to 0x0000181f (II) Active PCI resource ranges after removing overlaps: [0] -1 0 0xc8200000 - 0xc820ffff (0x10000) MX[B]E [1] -1 0 0xc8218000 - 0xc821ffff (0x8000) MX[B]E [2] -1 0 0xc8214000 - 0xc8215fff (0x2000) MX[B]E [3] -1 0 0xc8210000 - 0xc8213fff (0x4000) MX[B]E [4] -1 0 0xc8217000 - 0xc8217fff (0x1000) MX[B]E [5] -1 0 0xc8000400 - 0xc80007ff (0x400) MX[B]E [6] -1 0 0xc8000800 - 0xc8000fff (0x800) MX[B]E [7] -1 0 0xc8000000 - 0xc80003ff (0x400) MX[B]E [8] -1 0 0xc8100000 - 0xc810ffff (0x10000) MX[B](B) [9] -1 0 0xd0000000 - 0xd7ffffff (0x8000000) MX[B](B) [10] -1 0 0x000020a0 - 0x000020bf (0x20) IX[B]E [11] -1 0 0x000018c0 - 0x000018ff (0x40) IX[B]E [12] -1 0 0x00002000 - 0x0000207f (0x80) IX[B]E [13] -1 0 0x00002400 - 0x000024ff (0x100) IX[B]E [14] -1 0 0x00001880 - 0x000018bf (0x40) IX[B]E [15] -1 0 0x00001c00 - 0x00001cff (0x100) IX[B]E [16] -1 0 0x00001860 - 0x0000187f (0x20) IX[B]E [17] -1 0 0x00001840 - 0x0000185f (0x20) IX[B]E [18] -1 0 0x00001820 - 0x0000183f (0x20) IX[B]E [19] -1 0 0x00001800 - 0x0000181f (0x20) IX[B]E [20] -1 0 0x00003000 - 0x000030ff (0x100) IX[B](B) (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [6] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) All system resource ranges: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xc8200000 - 0xc820ffff (0x10000) MX[B]E [6] -1 0 0xc8218000 - 0xc821ffff (0x8000) MX[B]E [7] -1 0 0xc8214000 - 0xc8215fff (0x2000) MX[B]E [8] -1 0 0xc8210000 - 0xc8213fff (0x4000) MX[B]E [9] -1 0 0xc8217000 - 0xc8217fff (0x1000) MX[B]E [10] -1 0 0xc8000400 - 0xc80007ff (0x400) MX[B]E [11] -1 0 0xc8000800 - 0xc8000fff (0x800) MX[B]E [12] -1 0 0xc8000000 - 0xc80003ff (0x400) MX[B]E [13] -1 0 0xc8100000 - 0xc810ffff (0x10000) MX[B](B) [14] -1 0 0xd0000000 - 0xd7ffffff (0x8000000) MX[B](B) [15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [16] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [17] -1 0 0x000020a0 - 0x000020bf (0x20) IX[B]E [18] -1 0 0x000018c0 - 0x000018ff (0x40) IX[B]E [19] -1 0 0x00002000 - 0x0000207f (0x80) IX[B]E [20] -1 0 0x00002400 - 0x000024ff (0x100) IX[B]E [21] -1 0 0x00001880 - 0x000018bf (0x40) IX[B]E [22] -1 0 0x00001c00 - 0x00001cff (0x100) IX[B]E [23] -1 0 0x00001860 - 0x0000187f (0x20) IX[B]E [24] -1 0 0x00001840 - 0x0000185f (0x20) IX[B]E [25] -1 0 0x00001820 - 0x0000183f (0x20) IX[B]E [26] -1 0 0x00001800 - 0x0000181f (0x20) IX[B]E [27] -1 0 0x00003000 - 0x000030ff (0x100) IX[B](B) (II) LoadModule: "freetype" (II) Loading /usr/X11R6/lib/modules/fonts/libfreetype.so (II) Module freetype: vendor="X.Org Foundation & the After X-TT Project" compiled for 6.9.0, module version = 2.1.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font FreeType (II) LoadModule: "extmod" (II) Loading /usr/X11R6/lib/modules/extensions/libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.2 (II) Loading extension SHAPE (II) Loading extension MIT-SUNDRY-NONSTANDARD (II) Loading extension BIG-REQUESTS (II) Loading extension SYNC (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XC-MISC (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-Misc (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension TOG-CUP (II) Loading extension Extended-Visual-Information (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "type1" (II) Loading /usr/X11R6/lib/modules/fonts/libtype1.so (II) Module type1: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.2 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Type1 (II) Loading font CID (II) LoadModule: "ati" (II) Loading /usr/X11R6/lib/modules/drivers/ati_drv.so (II) Module ati: vendor="X.Org Foundation" compiled for 6.9.0, module version = 6.5.7 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 0.8 (II) LoadModule: "keyboard" (II) Loading /usr/X11R6/lib/modules/input/keyboard_drv.so (II) Module keyboard: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.5 (II) LoadModule: "mouse" (II) Loading /usr/X11R6/lib/modules/input/mouse_drv.so (II) Module mouse: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.3 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.5 (II) ATI: ATI driver (version 6.5.7) for chipsets: ati, ativga (II) R128: Driver for ATI Rage 128 chipsets: ATI Rage 128 Mobility M3 LE (PCI), ATI Rage 128 Mobility M3 LF (AGP), ATI Rage 128 Mobility M4 MF (AGP), ATI Rage 128 Mobility M4 ML (AGP), ATI Rage 128 Pro GL PA (PCI/AGP), ATI Rage 128 Pro GL PB (PCI/AGP), ATI Rage 128 Pro GL PC (PCI/AGP), ATI Rage 128 Pro GL PD (PCI), ATI Rage 128 Pro GL PE (PCI/AGP), ATI Rage 128 Pro GL PF (AGP), ATI Rage 128 Pro VR PG (PCI/AGP), ATI Rage 128 Pro VR PH (PCI/AGP), ATI Rage 128 Pro VR PI (PCI/AGP), ATI Rage 128 Pro VR PJ (PCI/AGP), ATI Rage 128 Pro VR PK (PCI/AGP), ATI Rage 128 Pro VR PL (PCI/AGP), ATI Rage 128 Pro VR PM (PCI/AGP), ATI Rage 128 Pro VR PN (PCI/AGP), ATI Rage 128 Pro VR PO (PCI/AGP), ATI Rage 128 Pro VR PP (PCI), ATI Rage 128 Pro VR PQ (PCI/AGP), ATI Rage 128 Pro VR PR (PCI), ATI Rage 128 Pro VR PS (PCI/AGP), ATI Rage 128 Pro VR PT (PCI/AGP), ATI Rage 128 Pro VR PU (PCI/AGP), ATI Rage 128 Pro VR PV (PCI/AGP), ATI Rage 128 Pro VR PW (PCI/AGP), ATI Rage 128 Pro VR PX (PCI/AGP), ATI Rage 128 GL RE (PCI), ATI Rage 128 GL RF (AGP), ATI Rage 128 RG (AGP), ATI Rage 128 VR RK (PCI), ATI Rage 128 VR RL (AGP), ATI Rage 128 4X SE (PCI/AGP), ATI Rage 128 4X SF (PCI/AGP), ATI Rage 128 4X SG (PCI/AGP), ATI Rage 128 4X SH (PCI/AGP), ATI Rage 128 4X SK (PCI/AGP), ATI Rage 128 4X SL (PCI/AGP), ATI Rage 128 4X SM (AGP), ATI Rage 128 4X SN (PCI/AGP), ATI Rage 128 Pro ULTRA TF (AGP), ATI Rage 128 Pro ULTRA TL (AGP), ATI Rage 128 Pro ULTRA TR (AGP), ATI Rage 128 Pro ULTRA TS (AGP?), ATI Rage 128 Pro ULTRA TT (AGP?), ATI Rage 128 Pro ULTRA TU (AGP?) (II) RADEON: Driver for ATI Radeon chipsets: ATI Radeon QD (AGP), ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP), ATI Radeon VE/7000 QY (AGP/PCI), ATI Radeon VE/7000 QZ (AGP/PCI), ATI ES1000 515E (PCI), ATI ES1000 5969 (PCI), ATI Radeon Mobility M7 LW (AGP), ATI Mobility FireGL 7800 M7 LX (AGP), ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP), ATI Radeon IGP320 (A3) 4136, ATI Radeon IGP320M (U1) 4336, ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon IGP330M/340M/350M (U2) 4337, ATI Radeon 7000 IGP (A4+) 4237, ATI Radeon Mobility 7000 IGP 4437, ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP), ATI Radeon 9100 QM (AGP), ATI Radeon 8500 AIW BB (AGP), ATI Radeon 8500 AIW BC (AGP), ATI Radeon 7500 QW (AGP/PCI), ATI Radeon 7500 QX (AGP/PCI), ATI Radeon 9000/PRO If (AGP/PCI), ATI Radeon 9000 Ig (AGP/PCI), ATI FireGL Mobility 9000 (M9) Ld (AGP), ATI Radeon Mobility 9000 (M9) Lf (AGP), ATI Radeon Mobility 9000 (M9) Lg (AGP), ATI Radeon 9100 IGP (A5) 5834, ATI Radeon Mobility 9100 IGP (U3) 5835, ATI Radeon 9100 PRO IGP 7834, ATI Radeon Mobility 9200 IGP 7835, ATI Radeon 9200PRO 5960 (AGP), ATI Radeon 9200 5961 (AGP), ATI Radeon 9200 5962 (AGP), ATI Radeon 9200SE 5964 (AGP), ATI FireMV 2200 (PCI), ATI Radeon Mobility 9200 (M9+) 5C61 (AGP), ATI Radeon Mobility 9200 (M9+) 5C63 (AGP), ATI Radeon 9500 AD (AGP), ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP), ATI FireGL Z1 AG (AGP), ATI Radeon 9700 Pro ND (AGP), ATI Radeon 9700/9500Pro NE (AGP), ATI Radeon 9700 NF (AGP), ATI FireGL X1 NG (AGP), ATI Radeon 9600 AP (AGP), ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP), ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP), ATI FireGL RV360 AV (AGP), ATI Radeon Mobility 9600/9700 (M10/M11) NP (AGP), ATI Radeon Mobility 9600 (M10) NQ (AGP), ATI Radeon Mobility 9600 (M11) NR (AGP), ATI Radeon Mobility 9600 (M10) NS (AGP), ATI FireGL Mobility T2 (M10) NT (AGP), ATI FireGL Mobility T2e (M11) NV (AGP), ATI Radeon 9650, ATI Radeon 9800SE AH (AGP), ATI Radeon 9800 AI (AGP), ATI Radeon 9800 AJ (AGP), ATI FireGL X2 AK (AGP), ATI Radeon 9800PRO NH (AGP), ATI Radeon 9800 NI (AGP), ATI FireGL X2 NK (AGP), ATI Radeon 9800XT NJ (AGP), ATI Radeon X600 (RV380) 3E50 (PCIE), ATI FireGL V3200 (RV380) 3E54 (PCIE), ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireGL M24 GL 3154 (PCIE), ATI Radeon X300 (RV370) 5B60 (PCIE), ATI Radeon X600 (RV370) 5B62 (PCIE), ATI FireGL V3100 (RV370) 5B64 (PCIE), ATI FireGL D1100 (RV370) 5B65 (PCIE), ATI Radeon Mobility M300 (M22) 5460 (PCIE), ATI FireGL M22 GL 5464 (PCIE), ATI Radeon XPRESS 200 5A41 (PCIE), ATI Radeon XPRESS 200M 5A42 (PCIE), ATI Radeon XPRESS 200 5A61 (PCIE), ATI Radeon XPRESS 200M 5A62 (PCIE), ATI Radeon XPRESS 200 5954 (PCIE), ATI Radeon XPRESS 200M 5955 (PCIE), ATI Radeon XPRESS 200 5974 (PCIE), ATI Radeon XPRESS 200M 5975 (PCIE), ATI FireGL V5000 (RV410) (PCIE), ATI Mobility FireGL V5000 (M26) (PCIE), ATI Mobility FireGL V5000 (M26) (PCIE), ATI Mobility Radeon X700 (M26) (PCIE), ATI Mobility Radeon X700 (M26) (PCIE), ATI Radeon X700 PRO (RV410) (PCIE), ATI Radeon X700 XT (RV410) (PCIE), ATI Radeon X700 (RV410) (PCIE), ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X800 (R420) JH (AGP), ATI Radeon X800PRO (R420) JI (AGP), ATI Radeon X800SE (R420) JJ (AGP), ATI Radeon X800 (R420) JK (AGP), ATI Radeon X800 (R420) JL (AGP), ATI FireGL X3 (R420) JM (AGP), ATI Radeon Mobility 9800 (M18) JN (AGP), ATI Radeon X800XT (R420) JP (AGP), ATI Radeon X800 SE (R420) (AGP), ATI Radeon X800 (R423) UH (PCIE), ATI Radeon X800PRO (R423) UI (PCIE), ATI Radeon X800LE (R423) UJ (PCIE), ATI Radeon X800SE (R423) UK (PCIE), ATI FireGL V7200 (R423) UQ (PCIE), ATI FireGL V5100 (R423) UR (PCIE), ATI FireGL V7100 (R423) UT (PCIE), ATI Radeon X800XT (R423) 5D57 (PCIE), ATI FireGL V7100 (R423) (PCIE), ATI Mobility FireGL V5100 (M28) (PCIE), ATI Mobility Radeon X800 (M28) (PCIE), ATI Mobility Radeon X800 XT (M28) (PCIE), ATI Radeon X800 (R430) (PCIE), ATI Radeon X800 XL (R430) (PCIE), ATI Radeon X800 SE (R430) (PCIE), ATI Radeon X800 XTP (R430) (PCIE), ATI Radeon X850 5D4C (PCIE), ATI Radeon FireGL (R480) GL 5D50 (PCIE), ATI Radeon X850 SE (R480) (PCIE), ATI Radeon X850 PRO (R480) (PCIE), ATI Radeon X850 XT (R480) (PCIE), ATI Radeon X850 XT PE (R480) (PCIE), ATI Radeon X850 PRO (R480) (AGP), ATI Radeon X850 SE (R480) (AGP), ATI Radeon X850 XT (R480) (AGP), ATI Radeon X850 XT PE (R480) (AGP) (II) Primary Device is: PCI 01:00:0 (II) ATI: Candidate "Device" section "Card0". (--) Assigning device section with no busID to primary device (--) Chipset ATI Mobility Radeon X700 (M26) (PCIE) found (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xc8200000 - 0xc820ffff (0x10000) MX[B]E [6] -1 0 0xc8218000 - 0xc821ffff (0x8000) MX[B]E [7] -1 0 0xc8214000 - 0xc8215fff (0x2000) MX[B]E [8] -1 0 0xc8210000 - 0xc8213fff (0x4000) MX[B]E [9] -1 0 0xc8217000 - 0xc8217fff (0x1000) MX[B]E [10] -1 0 0xc8000400 - 0xc80007ff (0x400) MX[B]E [11] -1 0 0xc8000800 - 0xc8000fff (0x800) MX[B]E [12] -1 0 0xc8000000 - 0xc80003ff (0x400) MX[B]E [13] -1 0 0xc8100000 - 0xc810ffff (0x10000) MX[B](B) [14] -1 0 0xd0000000 - 0xd7ffffff (0x8000000) MX[B](B) [15] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [16] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [17] -1 0 0x000020a0 - 0x000020bf (0x20) IX[B]E [18] -1 0 0x000018c0 - 0x000018ff (0x40) IX[B]E [19] -1 0 0x00002000 - 0x0000207f (0x80) IX[B]E [20] -1 0 0x00002400 - 0x000024ff (0x100) IX[B]E [21] -1 0 0x00001880 - 0x000018bf (0x40) IX[B]E [22] -1 0 0x00001c00 - 0x00001cff (0x100) IX[B]E [23] -1 0 0x00001860 - 0x0000187f (0x20) IX[B]E [24] -1 0 0x00001840 - 0x0000185f (0x20) IX[B]E [25] -1 0 0x00001820 - 0x0000183f (0x20) IX[B]E [26] -1 0 0x00001800 - 0x0000181f (0x20) IX[B]E [27] -1 0 0x00003000 - 0x000030ff (0x100) IX[B](B) (II) Loading sub module "radeon" (II) LoadModule: "radeon" (II) Loading /usr/X11R6/lib/modules/drivers/radeon_drv.so (II) Module radeon: vendor="X.Org Foundation" compiled for 6.9.0, module version = 4.0.3 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 0.8 (II) resource ranges after probing: [0] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [1] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [2] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [3] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [4] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [5] -1 0 0xc8200000 - 0xc820ffff (0x10000) MX[B]E [6] -1 0 0xc8218000 - 0xc821ffff (0x8000) MX[B]E [7] -1 0 0xc8214000 - 0xc8215fff (0x2000) MX[B]E [8] -1 0 0xc8210000 - 0xc8213fff (0x4000) MX[B]E [9] -1 0 0xc8217000 - 0xc8217fff (0x1000) MX[B]E [10] -1 0 0xc8000400 - 0xc80007ff (0x400) MX[B]E [11] -1 0 0xc8000800 - 0xc8000fff (0x800) MX[B]E [12] -1 0 0xc8000000 - 0xc80003ff (0x400) MX[B]E [13] -1 0 0xc8100000 - 0xc810ffff (0x10000) MX[B](B) [14] -1 0 0xd0000000 - 0xd7ffffff (0x8000000) MX[B](B) [15] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [16] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [17] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [18] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [19] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [20] -1 0 0x000020a0 - 0x000020bf (0x20) IX[B]E [21] -1 0 0x000018c0 - 0x000018ff (0x40) IX[B]E [22] -1 0 0x00002000 - 0x0000207f (0x80) IX[B]E [23] -1 0 0x00002400 - 0x000024ff (0x100) IX[B]E [24] -1 0 0x00001880 - 0x000018bf (0x40) IX[B]E [25] -1 0 0x00001c00 - 0x00001cff (0x100) IX[B]E [26] -1 0 0x00001860 - 0x0000187f (0x20) IX[B]E [27] -1 0 0x00001840 - 0x0000185f (0x20) IX[B]E [28] -1 0 0x00001820 - 0x0000183f (0x20) IX[B]E [29] -1 0 0x00001800 - 0x0000181f (0x20) IX[B]E [30] -1 0 0x00003000 - 0x000030ff (0x100) IX[B](B) [31] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [32] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Setting vga for screen 0. (II) RADEON(0): MMIO registers at 0xc8100000 (==) RADEON(0): Write-combining range (0xc8100000,0x80000) was already clear (II) RADEON(0): PCI bus 1 card 0 func 0 (==) RADEON(0): Depth 16, (==) framebuffer bpp 16 (II) RADEON(0): Pixel depth = 16 bits stored in 2 bytes (16 bpp pixmaps) (==) RADEON(0): Default visual is TrueColor (II) Loading sub module "vgahw" (II) LoadModule: "vgahw" (II) Loading /usr/X11R6/lib/modules/libvgahw.so (II) Module vgahw: vendor="X.Org Foundation" compiled for 6.9.0, module version = 0.1.0 ABI class: X.Org Video Driver, version 0.8 (II) RADEON(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000 (==) RADEON(0): RGB weight 565 (II) RADEON(0): Using 6 bits per RGB (8 bit DAC) (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/X11R6/lib/modules/libint10.so (II) Module int10: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.8 (II) RADEON(0): initializing int10 (==) RADEON(0): Write-combining range (0xa0000,0x20000) was already clear (==) RADEON(0): Write-combining range (0xc0000,0x40000) was already clear (II) RADEON(0): Primary V_BIOS segment is: 0xc000 (==) RADEON(0): Write-combining range (0x0,0x1000) was already clear (--) RADEON(0): Chipset: "ATI Mobility Radeon X700 (M26) (PCIE)" (ChipID = 0x5653) (--) RADEON(0): Linear framebuffer at 0xd0000000 (--) RADEON(0): VideoRAM: 131072 kByte (128 bit DDR SDRAM) (II) RADEON(0): PCIE card detected (II) RADEON(0): Color tiling disabled (II) Loading sub module "ddc" (II) LoadModule: "ddc" (II) Loading /usr/X11R6/lib/modules/libddc.so (II) Module ddc: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.8 (II) Loading sub module "i2c" (II) LoadModule: "i2c" (II) Loading /usr/X11R6/lib/modules/libi2c.so (II) Module i2c: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.2.0 ABI class: X.Org Video Driver, version 0.8 (II) RADEON(0): I2C bus "DDC" initialized. (II) RADEON(0): ATOM BIOS detected (II) RADEON(0): Port0: DDCType-0, DACType-0, TMDSType--1, ConnectorType-1 (II) RADEON(0): Port1: DDCType-0, DACType--1, TMDSType--1, ConnectorType-7 (II) RADEON(0): (II) RADEON(0): Primary: Monitor -- CRT Connector -- VGA DAC Type -- Primary TMDS Type -- NONE DDC Type -- NONE (II) RADEON(0): Secondary: Monitor -- NONE Connector -- LVDS DAC Type -- Unknown TMDS Type -- NONE DDC Type -- NONE (II) RADEON(0): ref_freq: 2700, min_pll: 20000, max_pll: 50000, xclk: 40000, sclk: 358.000000, mclk: 345.000000 (II) RADEON(0): PLL parameters: rf=2700 rd=7 min=20000 max=50000; xclk=40000 (WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode disabled (==) RADEON(0): Using gamma correction (1.0, 1.0, 1.0) (II) RADEON(0): Validating modes on Primary head --------- (II) RADEON(0): Monitor0: Using default hsync range of 28.00-33.00 kHz (II) RADEON(0): Monitor0: Using default vrefresh range of 43.00-72.00 Hz (II) RADEON(0): Clock range: 20.00 to 500.00 MHz (II) RADEON(0): Not using default mode "640x350" (hsync out of range) (II) RADEON(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "640x400" (hsync out of range) (II) RADEON(0): Not using default mode "320x200" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "720x400" (hsync out of range) (II) RADEON(0): Not using default mode "360x200" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "640x480" (hsync out of range) (II) RADEON(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "640x480" (hsync out of range) (II) RADEON(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "640x480" (hsync out of range) (II) RADEON(0): Not using default mode "320x240" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "800x600" (hsync out of range) (II) RADEON(0): Not using default mode "400x300" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "800x600" (hsync out of range) (II) RADEON(0): Not using default mode "400x300" (hsync out of range) (II) RADEON(0): Not using default mode "800x600" (hsync out of range) (II) RADEON(0): Not using default mode "400x300" (hsync out of range) (II) RADEON(0): Not using default mode "800x600" (hsync out of range) (II) RADEON(0): Not using default mode "400x300" (hsync out of range) (II) RADEON(0): Not using default mode "800x600" (hsync out of range) (II) RADEON(0): Not using default mode "400x300" (hsync out of range) (II) RADEON(0): Not using default mode "1024x768" (hsync out of range) (II) RADEON(0): Not using default mode "512x384" (hsync out of range) (II) RADEON(0): Not using default mode "1024x768" (hsync out of range) (II) RADEON(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1024x768" (hsync out of range) (II) RADEON(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1024x768" (hsync out of range) (II) RADEON(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1024x768" (hsync out of range) (II) RADEON(0): Not using default mode "512x384" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1152x864" (hsync out of range) (II) RADEON(0): Not using default mode "576x432" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1280x960" (hsync out of range) (II) RADEON(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1280x960" (hsync out of range) (II) RADEON(0): Not using default mode "640x480" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1280x1024" (hsync out of range) (II) RADEON(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1280x1024" (hsync out of range) (II) RADEON(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1280x1024" (hsync out of range) (II) RADEON(0): Not using default mode "640x512" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1600x1200" (hsync out of range) (II) RADEON(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1600x1200" (hsync out of range) (II) RADEON(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1600x1200" (hsync out of range) (II) RADEON(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1600x1200" (hsync out of range) (II) RADEON(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1600x1200" (hsync out of range) (II) RADEON(0): Not using default mode "800x600" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1792x1344" (hsync out of range) (II) RADEON(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1792x1344" (hsync out of range) (II) RADEON(0): Not using default mode "896x672" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1856x1392" (hsync out of range) (II) RADEON(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1856x1392" (hsync out of range) (II) RADEON(0): Not using default mode "928x696" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1920x1440" (hsync out of range) (II) RADEON(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1920x1440" (hsync out of range) (II) RADEON(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "832x624" (hsync out of range) (II) RADEON(0): Not using default mode "416x312" (hsync out of range) (II) RADEON(0): Not using default mode "1152x768" (hsync out of range) (II) RADEON(0): Not using default mode "576x384" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1400x1050" (hsync out of range) (II) RADEON(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1400x1050" (hsync out of range) (II) RADEON(0): Not using default mode "700x525" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1600x1024" (hsync out of range) (II) RADEON(0): Not using default mode "800x512" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "1920x1440" (hsync out of range) (II) RADEON(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "2048x1536" (hsync out of range) (II) RADEON(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "2048x1536" (hsync out of range) (II) RADEON(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using default mode "2048x1536" (hsync out of range) (II) RADEON(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan) (II) RADEON(0): Not using mode "1024x768" (no mode of this name) (II) RADEON(0): Not using mode "800x600" (no mode of this name) (--) RADEON(0): Virtual size is 640x480 (pitch 640) (**) RADEON(0): Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz (II) RADEON(0): Modeline "640x480" 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (==) RADEON(0): DPI set to (75, 75) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/X11R6/lib/modules/libfb.so (II) Module fb: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.2 (II) Loading sub module "ramdac" (II) LoadModule: "ramdac" (II) Loading /usr/X11R6/lib/modules/libramdac.so (II) Module ramdac: vendor="X.Org Foundation" compiled for 6.9.0, module version = 0.1.0 ABI class: X.Org Video Driver, version 0.8 (==) RADEON(0): Using XAA acceleration architecture (II) Loading sub module "xaa" (II) LoadModule: "xaa" (II) Loading /usr/X11R6/lib/modules/libxaa.so (II) Module xaa: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.2.0 ABI class: X.Org Video Driver, version 0.8 (II) Loading sub module "shadowfb" (II) LoadModule: "shadowfb" (II) Loading /usr/X11R6/lib/modules/libshadowfb.so (II) Module shadowfb: vendor="X.Org Foundation" compiled for 6.9.0, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.2 (II) RADEON(0): Page flipping disabled (II) RADEON(0): Will try to use DMA for Xv image transfers (II) RADEON(0): No MM_TABLE found - assuming CARD is not TV-in capable. (==) RADEON(0): Write-combining range (0x0,0x1000) was already clear (!!) RADEON(0): For information on using the multimedia capabilities of this adapter, please see http://gatos.sf.net. (II) do I need RAC? No, I don't. (II) resource ranges after preInit: [0] 0 0 0xc8100000 - 0xc810ffff (0x10000) MX[B] [1] 0 0 0xd0000000 - 0xd7ffffff (0x8000000) MX[B] [2] -1 0 0xffe00000 - 0xffffffff (0x200000) MX[B](B) [3] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [4] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [5] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [6] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [7] -1 0 0xc8200000 - 0xc820ffff (0x10000) MX[B]E [8] -1 0 0xc8218000 - 0xc821ffff (0x8000) MX[B]E [9] -1 0 0xc8214000 - 0xc8215fff (0x2000) MX[B]E [10] -1 0 0xc8210000 - 0xc8213fff (0x4000) MX[B]E [11] -1 0 0xc8217000 - 0xc8217fff (0x1000) MX[B]E [12] -1 0 0xc8000400 - 0xc80007ff (0x400) MX[B]E [13] -1 0 0xc8000800 - 0xc8000fff (0x800) MX[B]E [14] -1 0 0xc8000000 - 0xc80003ff (0x400) MX[B]E [15] -1 0 0xc8100000 - 0xc810ffff (0x10000) MX[B](B) [16] -1 0 0xd0000000 - 0xd7ffffff (0x8000000) MX[B](B) [17] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprU) [18] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprU) [19] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprU) [20] 0 0 0x00003000 - 0x000030ff (0x100) IX[B] [21] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [22] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [23] -1 0 0x000020a0 - 0x000020bf (0x20) IX[B]E [24] -1 0 0x000018c0 - 0x000018ff (0x40) IX[B]E [25] -1 0 0x00002000 - 0x0000207f (0x80) IX[B]E [26] -1 0 0x00002400 - 0x000024ff (0x100) IX[B]E [27] -1 0 0x00001880 - 0x000018bf (0x40) IX[B]E [28] -1 0 0x00001c00 - 0x00001cff (0x100) IX[B]E [29] -1 0 0x00001860 - 0x0000187f (0x20) IX[B]E [30] -1 0 0x00001840 - 0x0000185f (0x20) IX[B]E [31] -1 0 0x00001820 - 0x0000183f (0x20) IX[B]E [32] -1 0 0x00001800 - 0x0000181f (0x20) IX[B]E [33] -1 0 0x00003000 - 0x000030ff (0x100) IX[B](B) [34] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU) [35] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU) (==) RADEON(0): Write-combining range (0xc8100000,0x80000) was already clear (==) RADEON(0): Write-combining range (0xd0000000,0x8000000) (==) RADEON(0): Write-combining range (0xa0000,0x10000) was already clear (II) RADEON(0): Dynamic Clock Scaling Disabled (WW) RADEON(0): Enabling DRM support *** Direct rendering support is highly experimental for Radeon 9500 *** and newer cards. The 3d mesa driver is not provided in this tree. *** A very experimental (and incomplete) version is available from Mesa CVS. *** Additional information can be found on http://r300.sourceforge.net *** This message has been last modified on 2005-08-07. (II) RADEON(0): Depth moves disabled by default (II) RADEON(0): Memory manager initialized to (0,0) (640,8191) (II) RADEON(0): Reserved area from (0,480) to (640,482) (II) RADEON(0): Largest offscreen area available: 640 x 7709 (II) RADEON(0): Render acceleration unsupported on Radeon 9500/9700 and newer. (II) RADEON(0): Render acceleration disabled (II) RADEON(0): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles 8x8 mono pattern filled rectangles Indirect CPU to Screen color expansion Solid Lines Scanline Image Writes Offscreen Pixmaps Setting up tile and stipple cache: 32 128x128 slots 24 256x256 slots 9 512x512 slots (II) RADEON(0): Acceleration enabled (==) RADEON(0): Backing store disabled (==) RADEON(0): Silken mouse enabled (II) RADEON(0): Using hardware cursor (scanline 482) (II) RADEON(0): Largest offscreen area available: 640 x 7696 (II) RADEON(0): No video input capabilities detected and no information is provided - disabling multimedia i2c (II) Loading sub module "theatre_detect" (II) LoadModule: "theatre_detect" (II) Loading /usr/X11R6/lib/modules/multimedia/theatre_detect_drv.so (II) Module theatre_detect: vendor="X.Org Foundation" compiled for 4.3.99.902, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.8 (II) RADEON(0): no multimedia table present, disabling Rage Theatre. (WW) RADEON(0): Direct rendering disabled (==) RandR enabled (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFIXES (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE (II) Initializing built-in extension XEVIE (**) Option "CoreKeyboard" (**) Keyboard0: Core Keyboard (**) Option "Protocol" "standard" (**) Keyboard0: Protocol: standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xorg" (**) Keyboard0: XkbRules: "xorg" (**) Keyboard0: XkbModel: "pc105" (**) Option "XkbLayout" "us" (**) Keyboard0: XkbLayout: "us" (**) Option "CustomKeycodes" "off" (**) Keyboard0: CustomKeycodes disabled (**) Option "Protocol" "Auto" (**) Mouse0: Device: "/dev/sysmouse" (**) Mouse0: Protocol: "Auto" (**) Option "CorePointer" (**) Mouse0: Core Pointer (**) Option "Device" "/dev/sysmouse" (==) Mouse0: Emulate3Buttons, Emulate3Timeout: 50 (**) Option "ZAxisMapping" "4 5" (**) Mouse0: ZAxisMapping: buttons 4 and 5 (**) Mouse0: Buttons: 9 (II) XINPUT: Adding extended input device "Mouse0" (type: MOUSE) (II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD) (II) Mouse0: SetupAuto: hw.iftype is 4, hw.model is 0 (II) Mouse0: SetupAuto: protocol is SysMouse (==) RADEON(0): Write-combining range (0xa0000,0x10000) was already clear --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=dmesg 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-RC1 #26: Thu Nov 23 22:49:20 UTC 2006 root@kaiser.sig11.org:/usr/obj.gmv-i386/usr/src/sys/FREESBIE ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) M processor 1.73GHz (1729.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6d8 Stepping = 8 Features=0xafe9fbff Features2=0x180 AMD Features=0x100000 real memory = 1072168960 (1022 MB) avail memory = 1040191488 (992 MB) ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard ACPI-0438: *** Error: Looking up [Z00C] in namespace, AE_NOT_FOUND SearchNode 0xc4af81c0 StartNode 0xc4af81c0 ReturnNode 0 ACPI-0438: *** Error: Looking up [Z00C] in namespace, AE_NOT_FOUND SearchNode 0xc4af6d40 StartNode 0xc4af6d40 ReturnNode 0 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 acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) unknown: I/O range not supported Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 cpu0: on acpi0 acpi_perf0: on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 acpi_perf0: on cpu0 acpi_perf0: failed in PERF_STATUS attach device_attach: acpi_perf0 attach returned 6 acpi_throttle0: on cpu0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pcib2: irq 17 at device 28.0 on pci0 pci9: on pcib2 pcib3: irq 16 at device 28.1 on pci0 pci10: on pcib3 pcib4: irq 18 at device 28.2 on pci0 pci2: on pcib4 uhci0: port 0x1800-0x181f irq 23 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 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x1840-0x185f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0x1860-0x187f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xc8000000-0xc80003ff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered umass0: SONY Storage Media, rev 2.00/1.00, addr 2 pcib5: at device 30.0 on pci0 pci6: on pcib5 cbb0: mem 0xc8216000-0xc8216fff irq 18 at device 1.0 on pci6 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 fwohci0: <1394 Open Host Controller Interface> mem 0xc8217000-0xc82177ff,0xc8210000-0xc8213fff irq 18 at device 1.2 on pci6 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:c0:9f:00:00:4b:f0:82 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:c0:9f:4b:f0:82 fwe0: Ethernet address: 02:c0:9f:4b:f0:82 fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc000ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) pci6: at device 1.3 (no driver attached) pci6: at device 3.0 (no driver attached) bge0: mem 0xc8200000-0xc820ffff irq 16 at device 8.0 on pci6 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:c0:9f:94:39:8f pcm0: port 0x1c00-0x1cff,0x1880-0x18bf mem 0xc8000800-0xc80009ff,0xc8000400-0xc80004ff irq 17 at device 30.2 on pci0 pcm0: pci0: at device 30.3 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x18c0-0x18cf at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 31.3 (no driver attached) acpi_acad0: on acpi0 battery0: on acpi0 battery1: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: flags 0x1000 irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 sio0 port 0x2f8-0x2ff irq 3 drq 1 flags 0x10 on acpi0 sio0: type 16550A pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcdfff,0xce000-0xcf7ff,0xe0000-0xe17ff 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 1729011960 Hz quality 800 Timecounters tick every 1.000 msec ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to accept, logging unlimited ad0: DMA limited to UDMA33, controller found non-ATA66 cable ACPI-0438: *** Error: Looking up [Z00C] in namespace, AE_NOT_FOUND SearchNode 0xc4af81c0 StartNode 0xc4af81c0 ReturnNode 0 ACPI-1304: *** Error: Method execution failed [\\_SB_.BAT1._BST] (Node 0xc4af80c0), AE_NOT_FOUND ad0: 76319MB at ata0-master UDMA33 cpu0: Cx states changed acd0: DVDR at ata0-slave UDMA33 GEOM_LABEL: Label for provider ad0s2 is ntfs/Disque local. GEOM_LABEL: Label for provider ad0s5 is msdosfs/ . acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 GEOM_LABEL: Label for provider acd0 is iso9660/FreeSBIE. acd0: FAILURE - READ_BIG ILLEGAL REQUEST asc=0x64 ascq=0x00 cd0 at ata0 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [325392 x 2048 byte records] da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-2 device da0: 40.000MB/s transfers da0: 62MB (126976 512 byte sectors: 64H 32S/T 62C) (cd0:ata0:0:1:0): READ(10). CDB: 28 0 0 4 f7 f 0 0 1 0 (cd0:ata0:0:1:0): CAM Status: SCSI Status Error (cd0:ata0:0:1:0): SCSI Status: Check Condition (cd0:ata0:0:1:0): ILLEGAL REQUEST csi:0,1d,0,0 asc:64,0 (cd0:ata0:0:1:0): Illegal mode for this track (cd0:ata0:0:1:0): Unretryable error (cd0:ata0:0:1:0): cddone: got error 0x6 back Trying to mount root from cd9660:/dev/iso9660/FreeSBIE ACPI-0438: *** Error: Looking up [Z00C] in namespace, AE_NOT_FOUND SearchNode 0xc4af81c0 StartNode 0xc4af81c0 ReturnNode 0 ACPI-1304: *** Error: Method execution failed [\\_SB_.BAT1._BST] (Node 0xc4af80c0), AE_NOT_FOUND ACPI-0438: *** Error: Looking up [Z00C] in namespace, AE_NOT_FOUND SearchNode 0xc4af81c0 StartNode 0xc4af81c0 ReturnNode 0 ACPI-1304: *** Error: Method execution failed [\\_SB_.BAT1._BST] (Node 0xc4af80c0), AE_NOT_FOUND ACPI-0438: *** Error: Looking up [Z00C] in namespace, AE_NOT_FOUND SearchNode 0xc4af81c0 StartNode 0xc4af81c0 ReturnNode 0 ACPI-1304: *** Error: Method execution failed [\\_SB_.BAT1._BST] (Node 0xc4af80c0), AE_NOT_FOUND ACPI-0438: *** Error: Looking up [Z00C] in namespace, AE_NOT_FOUND SearchNode 0xc4af81c0 StartNode 0xc4af81c0 ReturnNode 0 ACPI-1304: *** Error: Method execution failed [\\_SB_.BAT1._BST] (Node 0xc4af80c0), AE_NOT_FOUND ACPI-0438: *** Error: Looking up [Z00C] in namespace, AE_NOT_FOUND SearchNode 0xc4af81c0 StartNode 0xc4af81c0 ReturnNode 0 ACPI-1304: *** Error: Method execution failed [\\_SB_.BAT1._BST] (Node 0xc4af80c0), AE_NOT_FOUND ACPI-0438: *** Error: Looking up [Z00C] in namespace, AE_NOT_FOUND SearchNode 0xc4af81c0 StartNode 0xc4af81c0 ReturnNode 0 ACPI-1304: *** Error: Method execution failed [\\_SB_.BAT1._BST] (Node 0xc4af80c0), AE_NOT_FOUND md0.uzip: 31238 x 65536 blocks --0F1p//8PRICkK4MW-- From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 3 21:52:44 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0EEF716A4C8 for ; Sun, 3 Dec 2006 21:52:44 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F6DD43CA6 for ; Sun, 3 Dec 2006 21:52:14 +0000 (GMT) (envelope-from freebsd-hackers@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GqzGC-0006hM-ID for freebsd-hackers@freebsd.org; Sun, 03 Dec 2006 22:52:32 +0100 Received: from 89-172-58-206.adsl.net.t-com.hr ([89.172.58.206]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 03 Dec 2006 22:52:32 +0100 Received: from ivoras by 89-172-58-206.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 03 Dec 2006 22:52:32 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Ivan Voras Date: Sun, 03 Dec 2006 22:52:32 +0100 Lines: 20 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 89-172-58-206.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) In-Reply-To: Sender: news Subject: Re: BootCache for FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Dec 2006 21:52:44 -0000 Vishal Patil wrote: > Is anyone working on the idea of implementing BootCache for FreeBSD? MacOS > has this idea implemented > http://www.osxbook.com/book/bonus/misc/optimizations and I was wondering if > FreeBSD had such an implementation. I think it would be especially usefull > for laptops and desktops with slow drives that run FreeBSD. It would be easy to do as a GEOM class, but for real-life usage it would have to be directly in GEOM. Actually, I've done the logging part twice before, but it's not convenient to stop the geoms to insert a logging class in front of them. PJD has talked for some time about making a sort-of "hot-pluggable" mechanism in GEOM in which classes could be inserted in between two other classes without stopping them, but this will take time... There's another consideration: Apple can do it because OSX is shipped "as-is" and doesn't change much when you install it, but FreeBSD is always customized after installing. This doesn't prevent the mechanism to be implemented, but it would require it to be very easy to use. From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 4 12:20:17 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 50E9616A407 for ; Mon, 4 Dec 2006 12:20:17 +0000 (UTC) (envelope-from umka@sevcity.net) Received: from mail.sevcity.net (ns.sevcity.net [193.47.166.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id F000343CA6 for ; Mon, 4 Dec 2006 12:19:43 +0000 (GMT) (envelope-from umka@sevcity.net) Received: from mail.sevcity.net (service.sevcity [127.0.0.1]) by mail.sevcity.net (Postfix) with ESMTP id C8EA0170029; Mon, 4 Dec 2006 14:22:12 +0200 (EET) Received: from berloga.shadowland (umka.sevcity.net [193.47.166.138]) by mail.sevcity.net (Postfix) with ESMTP id AF50E170009; Mon, 4 Dec 2006 14:22:12 +0200 (EET) Received: from berloga.shadowland (berloga.shadowland [127.0.0.1]) by berloga.shadowland (8.12.11.20060308/8.12.11) with ESMTP id kB4CKDDg008591; Mon, 4 Dec 2006 14:20:13 +0200 Received: (from root@localhost) by berloga.shadowland (8.12.11.20060308/8.12.11/Submit) id kB4CKAxk008589; Mon, 4 Dec 2006 14:20:10 +0200 From: Alex Lyashkov To: Steven Hartland In-Reply-To: <00c001c71535$7e7d7670$b3db87d4@multiplay.co.uk> References: <00c001c71535$7e7d7670$b3db87d4@multiplay.co.uk> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: quoted-printable Organization: SevcityNet Message-Id: <1165234810.2827.2.camel@berloga.shadowland> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 (1.4.5-17) Date: Mon, 04 Dec 2006 14:20:10 +0200 X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-hackers@freebsd.org Subject: Re: Unable to stop a jail X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2006 12:20:17 -0000 Sorry for later response, this not are corruption - in difference with jail, jail2 need to be call jctl --ctx $id --destroy for destroy kernel context. =F7 =F0=D4=CE, 01.12.2006, =D7 12:43, Steven Hartland =D0=C9=DB=C5=D4: > We've got a jail here which we cant stop with either killall > jexec or jkill all return success but jls still reports > the jail as running. >=20 > The machines running several other jails which I cant restart > at this time so I ended up starting the jail again jls > now reports: > jls > JID IP Address Hostname Path > 9 10.10.0.5 jail6 /usr/local/jails/jail6 > 7 10.10.0.5 jail6 /usr/local/jails/jail6 > 6 10.10.0.4 jail5 /usr/local/jails/jail5 > 5 10.10.0.39 jail4 /usr/local/jails/jail4 > 3 10.10.0.6 jail3 /usr/local/jails/jail3 > 2 10.10.0.8 jail2 /usr/local/jails/jail2 > 1 10.10.0.7 jail1 /usr/local/jails/jail1 >=20 > Host machine is running FreeBSD-6.1-P10 >=20 > Any ideas some sort of kernel data corruption? >=20 > Steve >=20 >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > This e.mail is private and confidential between Multiplay (UK) Ltd. and t= he person or entity to whom it is addressed. In the event of misdirection, = the recipient is prohibited from using, copying, printing or otherwise diss= eminating it or any information contained in it.=20 >=20 > In the event of misdirection, illegible or incomplete transmission please= telephone +44 845 868 1337 > or return the E.mail to postmaster@multiplay.co.uk. >=20 > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 4 13:12:53 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6296216A492 for ; Mon, 4 Dec 2006 13:12:53 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01D2943CA5 for ; Mon, 4 Dec 2006 13:12:19 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([85.236.96.60]) by multiplay.co.uk (multiplay.co.uk [85.236.96.23]) (MDaemon PRO v9.0.1) with ESMTP id md50003278653.msg for ; Mon, 04 Dec 2006 13:12:02 +0000 Message-ID: <015301c717a5$c93e8970$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: "Alex Lyashkov" References: <00c001c71535$7e7d7670$b3db87d4@multiplay.co.uk> <1165234810.2827.2.camel@berloga.shadowland> Date: Mon, 4 Dec 2006 13:11:53 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="koi8-r"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Spam-Processed: multiplay.co.uk, Mon, 04 Dec 2006 13:12:02 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 85.236.96.60 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-hackers@freebsd.org X-MDAV-Processed: multiplay.co.uk, Mon, 04 Dec 2006 13:12:04 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: Unable to stop a jail X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2006 13:12:53 -0000 Alex Lyashkov wrote: > Sorry for later response, > > this not are corruption - in difference with jail, jail2 need to be > call > jctl --ctx $id --destroy for destroy kernel context. jctl is not a valid command here, perhaps its a thirdparty addon you have there? Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 4 13:19:49 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CDEE216A412 for ; Mon, 4 Dec 2006 13:19:49 +0000 (UTC) (envelope-from root@Neo-Vortex.net) Received: from mail.rawnet.com.au (mail.rawnet.com.au [124.152.1.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id C988343CC5 for ; Mon, 4 Dec 2006 13:19:09 +0000 (GMT) (envelope-from root@Neo-Vortex.net) Received: from Neo-Vortex.net (124-152-12-12.rawnet.com.au [124.152.12.12] (may be forged)) by mail.rawnet.com.au (8.12.11.20060308/8.12.11) with ESMTP id kB4DJNKx016242; Mon, 4 Dec 2006 23:19:23 +1000 Received: from localhost.Neo-Vortex.net (Neo-Vortex@localhost.Neo-Vortex.net [127.0.0.1]) by Neo-Vortex.net (8.13.3/8.13.3) with ESMTP id kB4DJM5n032156; Mon, 4 Dec 2006 23:19:22 +1000 (EST) (envelope-from root@Neo-Vortex.net) Date: Mon, 4 Dec 2006 23:19:22 +1000 (EST) From: Neo-Vortex To: killing@multiplay.co.uk Message-ID: <20061204231750.W31853@Neo-Vortex.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-ria-MailScanner-Information: Please contact the ISP for more information X-ria-MailScanner: Found to be clean X-ria-MailScanner-From: root@neo-vortex.net X-Spam-Status: No Cc: freebsd-hackers@freebsd.org Subject: Re: Unable to stop a jail X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2006 13:19:49 -0000 Steven Hartland Wrote, > jctl is not a valid command here, perhaps its a thirdparty addon > you have there? > Steve # whereis jail jail: /usr/sbin/jail /usr/share/man/man8/jail.8.gz /usr/src/usr.sbin/jail Its stock on my machine... Perhaps your path is bad? From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 4 13:39:06 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6013816A4C2 for ; Mon, 4 Dec 2006 13:39:06 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74D3343DEC for ; Mon, 4 Dec 2006 13:30:44 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([85.236.96.60]) by multiplay.co.uk (multiplay.co.uk [85.236.96.23]) (MDaemon PRO v9.0.1) with ESMTP id md50003278695.msg for ; Mon, 04 Dec 2006 13:30:13 +0000 Message-ID: <017201c717a8$51cc8150$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: "Neo-Vortex" References: <20061204231750.W31853@Neo-Vortex.net> Date: Mon, 4 Dec 2006 13:30:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 X-Spam-Processed: multiplay.co.uk, Mon, 04 Dec 2006 13:30:13 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 85.236.96.60 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-hackers@freebsd.org X-MDAV-Processed: multiplay.co.uk, Mon, 04 Dec 2006 13:30:14 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: Unable to stop a jail X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2006 13:39:06 -0000 Neo-Vortex wrote: > Steven Hartland Wrote, >> jctl is not a valid command here, perhaps its a thirdparty addon >> you have there? > # whereis jail > jail: /usr/sbin/jail /usr/share/man/man8/jail.8.gz > /usr/src/usr.sbin/jail > > Its stock on my machine... Perhaps your path is bad? Thats jail not jctl which was the command referenced Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 4 13:50:23 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1BA6A16A40F for ; Mon, 4 Dec 2006 13:50:23 +0000 (UTC) (envelope-from umka@sevcity.net) Received: from mail.sevcity.net (ns.sevcity.net [193.47.166.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65B8743CAF for ; Mon, 4 Dec 2006 13:49:37 +0000 (GMT) (envelope-from umka@sevcity.net) Received: from mail.sevcity.net (service.sevcity [127.0.0.1]) by mail.sevcity.net (Postfix) with ESMTP id 5E267170029; Mon, 4 Dec 2006 15:26:50 +0200 (EET) Received: from berloga.shadowland (umka.sevcity.net [193.47.166.138]) by mail.sevcity.net (Postfix) with ESMTP id 2D019170009; Mon, 4 Dec 2006 15:26:50 +0200 (EET) Received: from berloga.shadowland (berloga.shadowland [127.0.0.1]) by berloga.shadowland (8.12.11.20060308/8.12.11) with ESMTP id kB4DOpNX008829; Mon, 4 Dec 2006 15:24:51 +0200 Received: (from root@localhost) by berloga.shadowland (8.12.11.20060308/8.12.11/Submit) id kB4DOpwX008827; Mon, 4 Dec 2006 15:24:51 +0200 From: Alex Lyashkov To: Steven Hartland In-Reply-To: <015301c717a5$c93e8970$b3db87d4@multiplay.co.uk> References: <00c001c71535$7e7d7670$b3db87d4@multiplay.co.uk> <1165234810.2827.2.camel@berloga.shadowland> <015301c717a5$c93e8970$b3db87d4@multiplay.co.uk> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: quoted-printable Organization: SevcityNet Message-Id: <1165238690.2827.15.camel@berloga.shadowland> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 (1.4.5-17) Date: Mon, 04 Dec 2006 15:24:50 +0200 X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-hackers@freebsd.org Subject: Re: Unable to stop a jail X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2006 13:50:23 -0000 At jail2 homepage has link to jail2 tools. http://docs.freevps.com/doku.php?id=3Dfreebsd:index link to=20 http://docs.freevps.com/doku.php?id=3Dfreebsd:tools Tools allow some resource control. =F7 =F0=CE=C4, 04.12.2006, =D7 15:11, Steven Hartland =D0=C9=DB=C5=D4: > Alex Lyashkov wrote: > > Sorry for later response, > >=20 > > this not are corruption - in difference with jail, jail2 need to be > > call=20 > > jctl --ctx $id --destroy for destroy kernel context. >=20 > jctl is not a valid command here, perhaps its a thirdparty addon > you have there? >=20 > Steve >=20 >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > This e.mail is private and confidential between Multiplay (UK) Ltd. and t= he person or entity to whom it is addressed. In the event of misdirection, = the recipient is prohibited from using, copying, printing or otherwise diss= eminating it or any information contained in it.=20 >=20 > In the event of misdirection, illegible or incomplete transmission please= telephone +44 845 868 1337 > or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 5 06:17:22 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 020F816A416; Tue, 5 Dec 2006 06:17:22 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (pool-71-245-104-192.ptldor.fios.verizon.net [71.245.104.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73B1043C9D; Tue, 5 Dec 2006 06:16:42 +0000 (GMT) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (localhost.home.localnet [127.0.0.1]) by schitzo.solgatos.com (8.13.8/8.13.6) with ESMTP id kB56HIM5028157; Mon, 4 Dec 2006 22:17:18 -0800 Received: from sopwith.solgatos.com (uucp@localhost) by schitzo.solgatos.com (8.13.8/8.13.4/Submit) with UUCP id kB56HIHa028154; Mon, 4 Dec 2006 22:17:18 -0800 Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id GAA25710; Tue, 5 Dec 2006 06:15:43 GMT Message-Id: <200612050615.GAA25710@sopwith.solgatos.com> To: freebsd-hackers@FreeBSD.org In-reply-to: Your message of "Mon, 04 Dec 2006 20:29:55 GMT." <200612042029.kB4KTtAD005077@freefall.freebsd.org> Date: Mon, 04 Dec 2006 22:15:43 +0000 From: Dieter X-Mailman-Approved-At: Tue, 05 Dec 2006 12:57:44 +0000 Cc: Remko Lodder , freebsd-bugs@FreeBSD.org Subject: Re: kern/106343: Need SATA NCQ support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Dec 2006 06:17:22 -0000 In message <200612042029.kB4KTtAD005077@freefall.freebsd.org>, Remko Lodder writes: > Synopsis: Need SATA NCQ support > > State-Changed-From-To: open->closed > State-Changed-By: remko > State-Changed-When: Mon Dec 4 20:29:54 UTC 2006 > State-Changed-Why: > Hello, this is not a PRoblem but a request for assistance. Please reask > this on the -hackers mailinglist (findable via > http://lists.freebsd.org/mailman/listinfo). They might be able to help > you quicker and sooner then via a PR (Which is not really a PR yet). If > after discussion people think you should file a PR, notify me and I will > reopen it with all the recent information involved. Anyway: Thanks for > taking the time to report this issue and for using FreeBSD > > http://www.freebsd.org/cgi/query-pr.cgi?pr=106343 I asked on -questions a year ago. No response. IMO the man page(s) should include things like how to turn SATA NCQ on/off. And if the device drivers don't provide the functionality, they should. So IMO this is a PR. But we can run it past -hackers, that's fine. So, for those of you on -hackers just tuning in, can someone please tell me how to turn SATA NCQ on? Thanks! Here's the PR in question: atacontrol cap ad4 reports: Feature Support Enable Value Vendor Native Command Queuing (NCQ) yes - 31/0x1F I have looked in the atacontrol(8) man page, the ata(4) man page, I grepped all the section 4 & 8 man pages, and I did an online search, but I cannot find how to turn on SATA NCQ. Write performance without NCQ is unacceptable. NCQ would improve write performance significantly. It is not obvious if this is "just" a documentation problem, or if NCQ support needs to be added to the various SATA controller device drivers. (nforce4 ultra in my case) atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xcc00-0xcc0f mem 0xfebfb0\ 00-0xfebfbfff irq 10 at device 7.0 on pci0 ata2: on atapci1 ad4: 238475MB at ata2-master SATA150 From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 5 15:39:11 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2790416A4CE for ; Tue, 5 Dec 2006 15:39:11 +0000 (UTC) (envelope-from m.jakeman@lancaster.ac.uk) Received: from pigwidgeon.lancs.ac.uk (pigwidgeon.lancs.ac.uk [148.88.0.67]) by mx1.FreeBSD.org (Postfix) with ESMTP id A70DF43CF8 for ; Tue, 5 Dec 2006 15:38:17 +0000 (GMT) (envelope-from m.jakeman@lancaster.ac.uk) Received: from mail01.lancs.ac.uk ([148.88.1.53] helo=marl.lancs.ac.uk) by pigwidgeon.lancs.ac.uk with esmtp (Exim 4.60) (envelope-from ) id 1GrcNX-0004i4-UX for freebsd-hackers@freebsd.org; Tue, 05 Dec 2006 15:38:43 +0000 Received: from ina044000004.lancs.ac.uk ([148.88.224.46]) by marl.lancs.ac.uk with esmtp (Exim 4.63) (envelope-from ) id 1GrcNX-0002B5-C0 for freebsd-hackers@freebsd.org; Tue, 05 Dec 2006 15:38:43 +0000 From: Matthew Jakeman Organization: Lancaster University To: freebsd-hackers@freebsd.org Date: Tue, 5 Dec 2006 15:26:00 +0000 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612051526.00434.m.jakeman@lancaster.ac.uk> Subject: RFC 3095 Robust Header Compression/IPv6 Header Compression X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: m.jakeman@lancaster.ac.uk List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Dec 2006 15:39:11 -0000 Hi all, Is there an implementation of RFC3095, Robust Header Compression, available for FreeBSD, if not, does anyone know of any IPv6 header compression available, all I can find so far is net/slcompress.c which will compress the TCP headers, I am looking to integrate an IPv6 header comrpession scheme into some other code I am writing if there is some out there? Thanks in advance Matt From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 5 22:34:35 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7BB8716A407 for ; Tue, 5 Dec 2006 22:34:35 +0000 (UTC) (envelope-from FreeBSD@insightbb.com) Received: from asav01.insightbb.com (gateway.insightbb.com [74.128.0.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69AFA43CAD for ; Tue, 5 Dec 2006 22:33:53 +0000 (GMT) (envelope-from FreeBSD@insightbb.com) Received: from dhcp-74-130-161-48.insightbb.com (HELO lightning) ([74.130.161.48]) by asav01.insightbb.com with ESMTP; 05 Dec 2006 17:34:34 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAK6CdUVKgqEwYWdsb2JhbACNJRUOCSE From: Steven Friedrich To: freebsd-hackers@freebsd.org Date: Tue, 5 Dec 2006 17:34:32 -0500 User-Agent: KMail/1.9.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612051734.32992.FreeBSD@insightbb.com> X-Mailman-Approved-At: Tue, 05 Dec 2006 23:23:00 +0000 Subject: can't connect to cvsup.freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Dec 2006 22:34:35 -0000 but I'm able to connect to cvsup5 and cvsup6. The main ftp site says: Cannot connect to data port: Connection refused This started around the time of the cut-overs. -- i386 FreeBSD 4.11-STABLE There are 10 types of people in this world. Ones that understand binary and then, the others. From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 6 09:27:42 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AF82416A417 for ; Wed, 6 Dec 2006 09:27:42 +0000 (UTC) (envelope-from remko@redqueen.evilcoder-services.org) Received: from redqueen.evilcoder-services.org (redqueen.evilcoder-services.org [217.148.169.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F58B43CBC for ; Wed, 6 Dec 2006 09:26:58 +0000 (GMT) (envelope-from remko@redqueen.evilcoder-services.org) Received: by redqueen.evilcoder-services.org (Postfix, from userid 1001) id 16577657D; Wed, 6 Dec 2006 10:27:41 +0100 (CET) Date: Wed, 6 Dec 2006 10:27:41 +0100 From: Remko Lodder To: Steven Friedrich Message-ID: <20061206092740.GI12800@elvandar.org> References: <200612051734.32992.FreeBSD@insightbb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200612051734.32992.FreeBSD@insightbb.com> User-Agent: Mutt/1.5.13 (2006-08-11) Cc: freebsd-hackers@freebsd.org Subject: Re: can't connect to cvsup.freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 09:27:42 -0000 I dont have any problems here, get a maximum connections exceeded message though. Hope this helps! On Tue, Dec 05, 2006 at 05:34:32PM -0500, Steven Friedrich wrote: > but I'm able to connect to cvsup5 and cvsup6. > > The main ftp site says: Cannot connect to data port: Connection refused > > This started around the time of the cut-overs. > > -- > i386 FreeBSD 4.11-STABLE > There are 10 types of people in this world. Ones that understand binary and > then, the others. -- Kind regards, Remko Lodder ** remko@elvandar.org FreeBSD ** remko@FreeBSD.org /* Quis custodiet ipsos custodes */ From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 6 09:31:02 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6BB4916A412 for ; Wed, 6 Dec 2006 09:31:02 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [63.240.77.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1701E43CD6 for ; Wed, 6 Dec 2006 09:30:12 +0000 (GMT) (envelope-from josh@tcbug.org) Received: from gimpy (c-24-118-173-219.hsd1.mn.comcast.net[24.118.173.219]) by comcast.net (sccrmhc13) with ESMTP id <2006120609305601300lolf4e>; Wed, 6 Dec 2006 09:30:56 +0000 From: Josh Paetzel To: freebsd-hackers@freebsd.org Date: Wed, 6 Dec 2006 03:30:55 -0600 User-Agent: KMail/1.9.4 References: <200612051734.32992.FreeBSD@insightbb.com> In-Reply-To: <200612051734.32992.FreeBSD@insightbb.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612060330.55759.josh@tcbug.org> Cc: Steven Friedrich Subject: Re: can't connect to cvsup.freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 09:31:02 -0000 On Tuesday 05 December 2006 16:34, Steven Friedrich wrote: > but I'm able to connect to cvsup5 and cvsup6. > > The main ftp site says: Cannot connect to data port: Connection > refused > > This started around the time of the cut-overs. *default host=cvsup.FreeBSD.org gimpy# csup /usr/local/etc/ports-supfile Connected to 198.104.69.57 Updating collection ports-all/cvs Edit ports/LEGAL ... gimpy# dig a ftp.freebsd.org ... ftp.freebsd.org. 180 IN A 62.243.72.50 ftp.freebsd.org. 180 IN A 204.152.184.73 .... gimpy# dig a cvsup.freebsd.org ..... cvsup.freebsd.org. 3535 IN CNAME n.cwu.edu. n.cwu.edu. 86335 IN A 198.104.69.57 .... My point, in case you don't understand the ouput of all these commands is that cvsup.freebsd.org and ftp.freebsd.org are presumably two different machines, and it's entirely possible that ftp.freebsd.org isn't a cvsup server. -- Thanks, Josh Paetzel From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 6 09:45:19 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5830716A417 for ; Wed, 6 Dec 2006 09:45:19 +0000 (UTC) (envelope-from niclas.zeising@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3011A43CC0 for ; Wed, 6 Dec 2006 09:44:23 +0000 (GMT) (envelope-from niclas.zeising@gmail.com) Received: by nf-out-0910.google.com with SMTP id x37so480267nfc for ; Wed, 06 Dec 2006 01:45:06 -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=GGXIB6lIiKEQRfz8UZ78KLOH4K8tL3by1EV2XFDOi/oXw/DsdUw6yrTdkENEKdwFjJ8UbbbsQZZbkR2GJ7zpcF9o8EGp0UNPeKdusdKlpPzJsywFrmGMPTjEgvIOH5ihkknqCUGl9EGwL7tyqgxkdf7snoYy6Zd37ANd6CmOL2s= Received: by 10.48.48.18 with SMTP id v18mr1900484nfv.1165396853747; Wed, 06 Dec 2006 01:20:53 -0800 (PST) Received: by 10.48.12.15 with HTTP; Wed, 6 Dec 2006 01:20:53 -0800 (PST) Message-ID: Date: Wed, 6 Dec 2006 10:20:53 +0100 From: "Niclas Zeising" To: "Steven Friedrich" In-Reply-To: <200612051734.32992.FreeBSD@insightbb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200612051734.32992.FreeBSD@insightbb.com> Cc: freebsd-hackers@freebsd.org Subject: Re: can't connect to cvsup.freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 09:45:19 -0000 On 12/5/06, Steven Friedrich wrote: > but I'm able to connect to cvsup5 and cvsup6. > > The main ftp site says: Cannot connect to data port: Connection refused > > This started around the time of the cut-overs. > > -- > i386 FreeBSD 4.11-STABLE > There are 10 types of people in this world. Ones that understand binary and > then, the others. Are you using cvsup or csup to connect to cvsup[5,6] or an ftp client? Just courius since you mention that the main ftp site says you can't connect. Regards! //Niclas -- From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 6 14:29:01 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9DC8D16A407 for ; Wed, 6 Dec 2006 14:29:01 +0000 (UTC) (envelope-from niclas.zeising@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A87C43CAE for ; Wed, 6 Dec 2006 14:28:14 +0000 (GMT) (envelope-from niclas.zeising@gmail.com) Received: by nf-out-0910.google.com with SMTP id x37so542268nfc for ; Wed, 06 Dec 2006 06:28:59 -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=KtSP6y6lV26NRkvn1HhsmhVMzqcv78VaQ/8pgV8qBuIlmUY2EnMqrZyiSxFaJpolq01RQGPfM4IAJYMipEbPoleS7Hm+/rn4mSJfdem1BWuQ69vNKS5OempeQLJPewStJ4agmznot+N2JFw0csNTs0gYLWeT9tJRVABEmnVgbDU= Received: by 10.49.26.18 with SMTP id d18mr2286627nfj.1165413740923; Wed, 06 Dec 2006 06:02:20 -0800 (PST) Received: by 10.48.12.15 with HTTP; Wed, 6 Dec 2006 06:02:20 -0800 (PST) Message-ID: Date: Wed, 6 Dec 2006 15:02:20 +0100 From: "Niclas Zeising" To: ros In-Reply-To: <457319DC.7030403@bebik.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <457319DC.7030403@bebik.net> Cc: freebsd-hackers@freebsd.org Subject: Re: Burning RW cdrom error message X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 14:29:01 -0000 On 12/3/06, ros wrote: > Trying to burn a RW CDROM, I notice the CD-ROM device was freeze and > nothing happen. After a hard reboot (I turn off completly the computer), > I find this message on the /var/log/message file > > Dec 3 19:04:40 bill kernel: acd0: req=0xc24e5258 SEND_OPC_INFO > semaphore timeout !! DANGER Will Robinson !! > Dec 3 19:04:42 bill kernel: acd0: req=0xc2063258 SETFEATURES SET > TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! > This is an old bug, I think. I've seen the message before. Which version of FreeBSD do you use? Try googling around for the error message and look through the list archives, you'll probably find something about the error there. Regards! //Niclas -- From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 6 16:48:24 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3106316A494 for ; Wed, 6 Dec 2006 16:48:24 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E79443CC6 for ; Wed, 6 Dec 2006 16:47:06 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id kB6GlWcQ061387; Wed, 6 Dec 2006 11:47:38 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Wed, 6 Dec 2006 11:35:55 -0500 User-Agent: KMail/1.9.1 References: <1164842336.1066.6.camel@WarHeaD.OTEL.net> In-Reply-To: <1164842336.1066.6.camel@WarHeaD.OTEL.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612061135.55487.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Wed, 06 Dec 2006 11:47:38 -0500 (EST) X-Virus-Scanned: ClamAV 0.88.3/2293/Wed Dec 6 09:00:31 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Iasen Kostoff Subject: Re: Driver not unset properly after kldunload X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 16:48:24 -0000 On Wednesday 29 November 2006 18:18, Iasen Kostoff wrote: > Hi, > It seems that after I load and then unload a driver its name stays > linked to the device e.g: > > nfe0@pci0:10:0: class=0x068000 card=0x81411043 chip=0x005710de rev=0xa3 > hdr=0x00 > > but of course if_nfe is neither compiled in kernel nor is loaded as > module anymore. > I digged around in kernel and saw this in device_detach(): > > if (!(dev->flags & DF_FIXEDCLASS)) > devclass_delete_device(dev->devclass, dev); > > dev->state = DS_NOTPRESENT; > device_set_driver(dev, NULL); > device_set_desc(dev, NULL); > device_sysctl_fini(dev); > > I've put some device_printf()s around and then looked at > devclass_delete_device(). It destroys (frees) a lot of the info about > the device and so the device_printf() prints device name as > "unknown" (NULL). That seems to be a problem for at least > device_set_driver(dev, NULL) - it doesn't unset the driver. I'm not so > sure about the other 2 but I guess it's same there. So when I changed the > order of this funcs everything worked fine (at least it looks like it > worked fine :) I'm not absolutely sure that this won't broke something > else). I've attached a patch for review. I don't see why this patch changes things. devclass_delete_device() only clears dev->unit, dev->devclass, and dev->nameunit. device_set_driver() doesn't check or clear any of those. In fact, your change does make device_set_driver() not work at all since the device state will still be DS_ATTACHED when you call device_set_driver() now. So, I guess your patch actually makes the device _not_ be detached from the driver. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 6 19:23:53 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9AD0D16A4CA for ; Wed, 6 Dec 2006 19:23:53 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE585446B7 for ; Wed, 6 Dec 2006 19:02:10 +0000 (GMT) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139] (may be forged)) by mxout5.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW06.09) with ESMTP id kB6J2bxd003303 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 6 Dec 2006 11:02:37 -0800 X-Auth-Received: from [128.208.4.96] (dzihan.cs.washington.edu [128.208.4.96]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW06.09) with ESMTP id kB6J2WwK011953 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 6 Dec 2006 11:02:36 -0800 Message-ID: <457713C8.6020204@u.washington.edu> Date: Wed, 06 Dec 2006 11:02:32 -0800 From: Garrett Cooper User-Agent: Thunderbird 1.5.0.8 (X11/20061108) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.2.2.285561, Antispam-Engine: 2.5.0.283055, Antispam-Data: 2006.12.6.104932 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' Subject: Forcing C program to core dump X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 19:23:53 -0000 Hello, This may be obvious to some, but after some Googling (apparently with the wrong search terms, perhaps) and reading the gcc/gdb manpages, I can't seem to find out how to get a program to produce core dumps. So I was wondering, is there some simple means to produce core dumps or a set of conditions that I need to adhere to in order to get the OS to core dump the progrdam??? Thanks, -Garrett From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 6 19:43:31 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 207EF16A500 for ; Wed, 6 Dec 2006 19:43:31 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout1.cac.washington.edu (mxout1.cac.washington.edu [140.142.32.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C79943D9F for ; Wed, 6 Dec 2006 19:33:13 +0000 (GMT) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout1.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW06.09) with ESMTP id kB6JXZNi004580 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 6 Dec 2006 11:33:35 -0800 X-Auth-Received: from [128.208.1.158] (sfrench.cs.washington.edu [128.208.1.158]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW06.09) with ESMTP id kB6JXYd5018783 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 6 Dec 2006 11:33:35 -0800 Message-ID: <45771B0E.7090907@u.washington.edu> Date: Wed, 06 Dec 2006 11:33:34 -0800 From: Garrett Cooper User-Agent: Thunderbird 1.5.0.8 (X11/20061108) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <457713C8.6020204@u.washington.edu> In-Reply-To: <457713C8.6020204@u.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.2.2.285561, Antispam-Engine: 2.5.0.283055, Antispam-Data: 2006.12.6.111932 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' Subject: Re: Forcing C program to core dump X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 19:43:31 -0000 Garrett Cooper wrote: > Hello, > This may be obvious to some, but after some Googling (apparently > with the wrong search terms, perhaps) and reading the gcc/gdb > manpages, I can't seem to find out how to get a program to produce > core dumps. > So I was wondering, is there some simple means to produce core > dumps or a set of conditions that I need to adhere to in order to get > the OS to core dump the progrdam??? > Thanks, > -Garrett > Did a bit more poking around and determined how to do it. It wasn't core dumping because I didn't set the maximum limit for the coredump size to unlimited ("ulimit -c unlimited"). Good page about this topic: . -Garrett From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 6 19:47:51 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A1A5516A4D0 for ; Wed, 6 Dec 2006 19:47:51 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 062D143E6C for ; Wed, 6 Dec 2006 19:42:07 +0000 (GMT) (envelope-from max@love2party.net) Received: from [88.66.4.3] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu3) with ESMTP (Nemesis), id 0MKxQS-1Gs2es0I0s-0004eM; Wed, 06 Dec 2006 20:42:22 +0100 From: Max Laier Organization: FreeBSD To: freebsd-hackers@freebsd.org Date: Wed, 6 Dec 2006 20:42:14 +0100 User-Agent: KMail/1.9.4 References: <457713C8.6020204@u.washington.edu> In-Reply-To: <457713C8.6020204@u.washington.edu> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1192689.acAocZHPKI"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200612062042.20791.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: Garrett Cooper Subject: Re: Forcing C program to core dump X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 19:47:51 -0000 --nextPart1192689.acAocZHPKI Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 06 December 2006 20:02, Garrett Cooper wrote: > Hello, > This may be obvious to some, but after some Googling (apparently > with the wrong search terms, perhaps) and reading the gcc/gdb manpages, > I can't seem to find out how to get a program to produce core dumps. > So I was wondering, is there some simple means to produce core > dumps or a set of conditions that I need to adhere to in order to get > the OS to core dump the progrdam??? See gcore(1) and abort(3). sysctl -a | grep core might turn up some=20 interesting sysctls. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1192689.acAocZHPKI Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQBFdx0cXyyEoT62BG0RAhUlAJ4qO6Ss8b5ymlj0wRV+VJ3Ne/m9sACfSZdZ AEVEk9LXmtVZqzwQcAeeWhc= =1If4 -----END PGP SIGNATURE----- --nextPart1192689.acAocZHPKI-- From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 6 19:52:04 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C380E16A50A for ; Wed, 6 Dec 2006 19:52:04 +0000 (UTC) (envelope-from viktor.vasilev@stud.tu-darmstadt.de) Received: from lnx131.hrz.tu-darmstadt.de (lnx131.hrz.tu-darmstadt.de [130.83.174.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEB0143EA5 for ; Wed, 6 Dec 2006 19:46:31 +0000 (GMT) (envelope-from viktor.vasilev@stud.tu-darmstadt.de) Received: from mailserver3.hrz.tu-darmstadt.de (lnx115.hrz.tu-darmstadt.de [130.83.174.27]) by lnx131.hrz.tu-darmstadt.de (8.13.4/8.12.10) with ESMTP id kB6Jjitg019186 for ; Wed, 6 Dec 2006 20:45:44 +0100 Received: from [89.48.34.240] (helo=noname) by mailserver3.hrz.tu-darmstadt.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1Gs2i3-0006n6-OB for freebsd-hackers@freebsd.org; Wed, 06 Dec 2006 20:45:43 +0100 From: Viktor Vasilev To: freebsd-hackers@freebsd.org Date: Wed, 6 Dec 2006 20:45:07 +0100 User-Agent: KMail/1.9.4 References: <457713C8.6020204@u.washington.edu> In-Reply-To: <457713C8.6020204@u.washington.edu> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2038530.FYutxRTgzK"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200612062045.15184.viktor.vasilev@stud.tu-darmstadt.de> X-TUD-HRZ-MailScanner: Found to be clean X-TUD-HRZ-MailScanner-SpamCheck: X-MailScanner-From: viktor.vasilev@stud.tu-darmstadt.de Subject: Re: Forcing C program to core dump X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 19:52:04 -0000 --nextPart2038530.FYutxRTgzK Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 06 December 2006 20:02 Garrett Cooper wrote: > Hello, > This may be obvious to some, but after some Googling (apparently > with the wrong search terms, perhaps) and reading the gcc/gdb manpages, > I can't seem to find out how to get a program to produce core dumps. > So I was wondering, is there some simple means to produce core dumps > or a set of conditions that I need to adhere to in order to get the OS > to core dump the progrdam??? Some signals default action is to cause the program to dump core,=20 when they're delivered. You can see the list in the signal(3) man=20 page. libc also provides the abort(3) function, which does what=20 you want. The code is here: /usr/src/lib/libc/stdlib/abort.c Cheers, Vik =2D-=20 PGP Key: 0xE09DC8D8/6799 4011 EBDE 6412 05A1 090C DBDF 5887 E09D C8D8 Signed/encrypted mail welcome! --nextPart2038530.FYutxRTgzK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQBFdx3L299Yh+CdyNgRArFeAJ9RuJAW4b9BYps1fWh4VaIHMgksmgCeJXyR RClm1OThsTlFCLpE+Ng9mv0= =oCBt -----END PGP SIGNATURE----- --nextPart2038530.FYutxRTgzK-- From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 6 19:56:31 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id ACA9E16A4D8 for ; Wed, 6 Dec 2006 19:56:31 +0000 (UTC) (envelope-from niclas.zeising@gmail.com) Received: from pne-smtpout2-sn1.fre.skanova.net (pne-smtpout2-sn1.fre.skanova.net [81.228.11.159]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3766043DAE for ; Wed, 6 Dec 2006 19:52:05 +0000 (GMT) (envelope-from niclas.zeising@gmail.com) Received: from [81.229.125.150] (81.229.125.150) by pne-smtpout2-sn1.fre.skanova.net (7.2.075) id 456CB2C8001C411B; Wed, 6 Dec 2006 20:52:40 +0100 Message-ID: <45771F7D.8070006@gmail.com> Date: Wed, 06 Dec 2006 20:52:29 +0100 From: Niclas Zeising User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Garrett Cooper References: <457713C8.6020204@u.washington.edu> In-Reply-To: <457713C8.6020204@u.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Forcing C program to core dump X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 19:56:31 -0000 Garrett Cooper wrote: > Hello, > This may be obvious to some, but after some Googling (apparently with > the wrong search terms, perhaps) and reading the gcc/gdb manpages, I > can't seem to find out how to get a program to produce core dumps. > So I was wondering, is there some simple means to produce core dumps > or a set of conditions that I need to adhere to in order to get the OS > to core dump the progrdam??? > Thanks, > -Garrett Just kill it with the abort signal (SIGABRT) or some other signal that makes the program dump core. Be aware though that if you are catching or ignoring the signal, this won't work. Regards! //Niclas -- From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 6 22:08:15 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4BFA016A40F for ; Wed, 6 Dec 2006 22:08:15 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C0C043CD6 for ; Wed, 6 Dec 2006 22:06:58 +0000 (GMT) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout7.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW06.09) with ESMTP id kB6Juuh6017375 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 6 Dec 2006 11:56:56 -0800 X-Auth-Received: from [128.208.1.158] (sfrench.cs.washington.edu [128.208.1.158]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW06.09) with ESMTP id kB6Juu9f023768 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 6 Dec 2006 11:56:56 -0800 Message-ID: <45772088.4090402@u.washington.edu> Date: Wed, 06 Dec 2006 11:56:56 -0800 From: Garrett Cooper User-Agent: Thunderbird 1.5.0.8 (X11/20061108) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <457713C8.6020204@u.washington.edu> <45771F7D.8070006@gmail.com> In-Reply-To: <45771F7D.8070006@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.2.2.285561, Antispam-Engine: 2.5.0.283055, Antispam-Data: 2006.12.6.114432 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' Subject: Re: Forcing C program to core dump X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Dec 2006 22:08:15 -0000 Niclas Zeising wrote: > Garrett Cooper wrote: >> Hello, >> This may be obvious to some, but after some Googling (apparently >> with the wrong search terms, perhaps) and reading the gcc/gdb >> manpages, I can't seem to find out how to get a program to produce >> core dumps. >> So I was wondering, is there some simple means to produce core >> dumps or a set of conditions that I need to adhere to in order to get >> the OS to core dump the progrdam??? >> Thanks, >> -Garrett > > Just kill it with the abort signal (SIGABRT) or some other signal that > makes the program dump core. Be aware though that if you are catching > or ignoring the signal, this won't work. > Regards! > //Niclas Wow. I got a lot of interesting ways to kill and force a coredump. Haha... Not quite what I had in mind, but I guess that's what I get for improperly wording the question. Thank you all, the information I've gotten recently is definitely educational and it'll probably end up being useful later! -Garrett From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 7 00:11:09 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4B65B16A403 for ; Thu, 7 Dec 2006 00:11:09 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD2C743CA5 for ; Thu, 7 Dec 2006 00:10:19 +0000 (GMT) (envelope-from freebsd-hackers@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Gs6qu-00016F-GN for freebsd-hackers@freebsd.org; Thu, 07 Dec 2006 01:11:04 +0100 Received: from anthonychavez.org ([166.70.126.66]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 07 Dec 2006 01:11:04 +0100 Received: from acc by anthonychavez.org with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 07 Dec 2006 01:11:04 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Anthony Chavez Date: Wed, 06 Dec 2006 17:10:43 -0700 Lines: 143 Message-ID: <871wncin0c.fsf@hephaistos.aegaeum.anthonychavez.org> References: <87odrpr48i.fsf@hephaistos.aegaeum.anthonychavez.org> <200611021712.32665.jhb@freebsd.org> <87lkmsmbt9.fsf@hephaistos.aegaeum.anthonychavez.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: anthonychavez.org User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.90 (gnu/linux) Cancel-Lock: sha1:QLPfLS7XUaNTZNgcWldA5rl0eJM= Sender: news Subject: Re: Panic on 6.1-RELEASE-p3 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Dec 2006 00:11:09 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable Anthony Chavez writes: > John Baldwin writes: > >> On Thursday 02 November 2006 15:19, Anthony Chavez wrote: >>> freebsd-hackers: >>>=20 >>> I have attached the backtraces of 17 core dumps from one of my >>> machines. I have several deployments of this same FreeBSD version in >>> the wild, and this is the only machine exhibiting this behavior. >>>=20 >>> Initially, the cause of these panics seemed to be related to some >>> component in the FreeBSD toolchain, as they would occur when >>> attempting to install a port. net/samba3 was the one we'd usually >>> test with, but the system would panic with most other larger packages >>> as well. >>>=20 >>> However, the system is panicking at irrgeular intervals, ranging >>> between 1-3 weeks apart. This is mostly happening in the off-hours >>> when no human users are actively using the machine, but there have >>> been 1 or 2 incidences where the machine has panicked during prime >>> time. >> >> Have you ran a memory checker or other diags to check for failing hardwa= re? > > I ran sysutils/memtest twice. Both times, it failed to panic the > system. I have yet to bring the system down and boot into a "real" > memory/hardware checker, however. I usually just go with > ultimatebootcd.com when testing, but if you have other suggestions for > tools, I'd welcome your input before we schedule to do the testing. Rather than pay us to debug the problem, our client opted to simply replace the memory, and it only took them 17 more panics to move on it until it started becoming a daily issue. What follows is yet another backtrace from a panic that occurred after about 20.5 hours of uptime. I would appreciate any further assistance in addressing this problem. =2D-=20 Anthony Chavez http://anthonychavez.org/ mailto:acc@anthonychavez.org jabber:acc@jabber.anthonychavez.org mybox% kgdb /usr/obj/usr/src/sys/WITFW/kernel.debug vmcore.37 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:= Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain condition= s. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0x0 fault code =3D supervisor read, page not present instruction pointer =3D 0x20:0xc06809c4 stack pointer =3D 0x28:0xe9606bb4 frame pointer =3D 0x28:0xe9606bbc code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D resume, IOPL =3D 0 current process =3D 42888 (nagios) trap number =3D 12 panic: page fault Uptime: 20h27m59s Dumping 1023 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 1023MB (261808 pages) 1007 991 975 959 943 927 911 895 879 863 8= 47 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:165 165 pcpu.h: No such file or directory. in pcpu.h (kgdb) backtrace #0 doadump () at pcpu.h:165 #1 0xc065ff79 in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:4= 02 #2 0xc0660240 in panic (fmt=3D0xc08b378a "%s") at /usr/src/sys/kern/kern_shutdown.c:558 #3 0xc087a09e in trap_fatal (frame=3D0xe9606b74, eva=3D0) at /usr/src/sys/i386/i386/trap.c:836 #4 0xc087979a in trap (frame=3D {tf_fs =3D 8, tf_es =3D 40, tf_ds =3D 40, tf_edi =3D -987783168, tf_e= si =3D 0, tf_ebp =3D -379556932, tf_isp =3D -379556960, tf_ebx =3D -9854330= 88, tf_edx =3D -985433088, tf_ecx =3D -985433088, tf_eax =3D 4, tf_trapno = =3D 12, tf_err =3D 0, tf_eip =3D -1066923580, tf_cs =3D 32, tf_eflags =3D 6= 5539, tf_esp =3D 0, tf_ss =3D -987818712}) at /usr/src/sys/i386/i386/trap.c:269 #5 0xc08689aa in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #6 0xc06809c4 in turnstile_broadcast (ts=3D0x0) at /usr/src/sys/kern/subr_turnstile.c:717 #7 0xc0657587 in _mtx_unlock_sleep (m=3D0xc51f1528, opts=3D0, file=3D0x0, = line=3D0) at /usr/src/sys/kern/kern_mutex.c:676 #8 0xc07fef0c in vnode_pager_lock (first_object=3D0xc5dcfa50) at /usr/src/sys/vm/vnode_pager.c:1198 #9 0xc07eb572 in vm_fault (map=3D0xc591da8c, vaddr=3D134918144,=20 fault_type=3D2 '\002', fault_flags=3D8) at /usr/src/sys/vm/vm_fault.c:2= 99 #10 0xc0879cff in trap_pfault (frame=3D0xe9606d38, usermode=3D1, eva=3D1349= 21272) at /usr/src/sys/i386/i386/trap.c:721 #11 0xc087988f in trap (frame=3D {tf_fs =3D 59, tf_es =3D 59, tf_ds =3D 59, tf_edi =3D 134921272, tf_e= si =3D 672508804, tf_ebp =3D -1077961820, tf_isp =3D -379556508, tf_ebx =3D= 671912920, tf_edx =3D 0, tf_ecx =3D 134534302, tf_eax =3D 671941632, tf_tr= apno =3D 12, tf_err =3D 7, tf_eip =3D 671814244, tf_cs =3D 51, tf_eflags = =3D 66054, tf_esp =3D -1077961844, tf_ss =3D 59}) at /usr/src/sys/i386/i386/trap.c:333 #12 0xc08689aa in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #13 0x280b1264 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) quit --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iQEVAwUBRXdcB/AIdTFWAbdTAQKkswf7Bdp/+qsRQm2UhW3hl7vwidwl+GZv25qO pIcd3+GpwEmMZhfC4h4+CKJyTGfx+qkW8Or3maCqU2mrY5pkOXdxZXEo92w4v15R ae1z3hTvrCAauwQB+ibobdUERYqO3Pp1byY7MJwwVmQgdBJypNoupGXlp3mlvq6o j+7yTieGP9WcsuYqbZGYhyO7+URs+bX3Uy6qL0DbAkjtVVc8u69igJzF+OpD67gc o98uvHkK9+4FLOXPmP03bk3/dO15JM2CN9yJDzOLKj80Vb35Our46aLCgzKzO0oa GCyPd/ihPjMO2UMwYs0cl9F0u/r+m3h3wiSyRQQHP+ugrmdJL97skg== =GZ1D -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 7 11:22:31 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C301316A4FB for ; Thu, 7 Dec 2006 11:22:31 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk [195.188.213.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4953743E9A for ; Thu, 7 Dec 2006 11:16:47 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.147] (helo=anti-virus03-10) by smtp-out4.blueyonder.co.uk with smtp (Exim 4.52) id 1GsHFx-0000CL-Bi; Thu, 07 Dec 2006 11:17:37 +0000 Received: from [82.41.32.99] (helo=[192.168.0.2]) by asmtp-out5.blueyonder.co.uk with esmtp (Exim 4.52) id 1GsHFw-0003Dh-Pj; Thu, 07 Dec 2006 11:17:36 +0000 Message-ID: <4577F850.3080707@dial.pipex.com> Date: Thu, 07 Dec 2006 11:17:36 +0000 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.13) Gecko/20061205 X-Accept-Language: en MIME-Version: 1.0 To: Garrett Cooper References: <457713C8.6020204@u.washington.edu> <45771F7D.8070006@gmail.com> In-Reply-To: <45771F7D.8070006@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Forcing C program to core dump X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Dec 2006 11:22:31 -0000 Niclas Zeising wrote: > Garrett Cooper wrote: > >> Hello, >> This may be obvious to some, but after some Googling (apparently >> with the wrong search terms, perhaps) and reading the gcc/gdb >> manpages, I can't seem to find out how to get a program to produce >> core dumps. >> So I was wondering, is there some simple means to produce core >> dumps or a set of conditions that I need to adhere to in order to get >> the OS to core dump the progrdam??? >> Thanks, >> -Garrett > > > Just kill it with the abort signal (SIGABRT) or some other signal that > makes the program dump core. Be aware though that if you are catching > or ignoring the signal, this won't work. > Regards! > //Niclas Which usually defaults to ctl-\ from the shell so it's easy to kill a foreground program with bothering to find process id's etc. OK, not what you actually wanted to do, but for completeness :-) --Alex From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 7 16:00:27 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C9CC416A403; Thu, 7 Dec 2006 16:00:27 +0000 (UTC) (envelope-from tbyte@otel.net) Received: from mail.otel.net (gw3.OTEL.net [212.36.8.151]) by mx1.FreeBSD.org (Postfix) with ESMTP id A99C044549; Thu, 7 Dec 2006 15:53:49 +0000 (GMT) (envelope-from tbyte@otel.net) Received: from dragon.otel.net ([212.36.8.135]) by mail.otel.net with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1GsLa1-0006Nr-97; Thu, 07 Dec 2006 17:54:38 +0200 From: Iasen Kostov To: John Baldwin In-Reply-To: <200612061135.55487.jhb@freebsd.org> References: <1164842336.1066.6.camel@WarHeaD.OTEL.net> <200612061135.55487.jhb@freebsd.org> Content-Type: multipart/mixed; boundary="=-JzvqiRaU8sheWlcGbKlB" Date: Thu, 07 Dec 2006 17:54:36 +0200 Message-Id: <1165506876.37590.12.camel@DraGoN.OTEL.net> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2.1 FreeBSD GNOME Team Port Cc: freebsd-hackers@freebsd.org Subject: Re: Driver not unset properly after kldunload X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Dec 2006 16:00:27 -0000 --=-JzvqiRaU8sheWlcGbKlB Content-Type: text/plain Content-Transfer-Encoding: 7bit On Wed, 2006-12-06 at 11:35 -0500, John Baldwin wrote: ... > I don't see why this patch changes things. devclass_delete_device() only > clears dev->unit, dev->devclass, and dev->nameunit. device_set_driver() > doesn't check or clear any of those. In fact, your change does make > device_set_driver() not work at all since the device state will still be > DS_ATTACHED when you call device_set_driver() now. So, I guess your patch > actually makes the device _not_ be detached from the driver. > Forgive me for being so lazy :). I've analized the problem as I should have done the first time and I hope I found the solution. First time I was missleaded by sys/dev/pci/pci_user.c and the way it sets pd_name[] in pci_devinfo struct (You actualy need to use pciconf atleast once after loading the driver) ... It's only set when you use PCIOCGETCONF ioctl on /dev/pci and it only sets it once (which is not very clever) and never unset it. But one can unload the current driver and load another (as in if_nfe, if_nve case) or just unload the driver and pd_name[] will always show the first driver attached on that device. So I hope this new patch is better one. --=-JzvqiRaU8sheWlcGbKlB Content-Disposition: attachment; filename=pci_user.c.diff Content-Type: text/x-patch; name=pci_user.c.diff; charset=UTF-8 Content-Transfer-Encoding: 7bit --- sys/dev/pci/pci_user.c.old Thu Dec 7 02:26:12 2006 +++ sys/dev/pci/pci_user.c Thu Dec 7 02:52:23 2006 @@ -303,14 +303,18 @@ /* Populate pd_name and pd_unit */ name = NULL; - if (dinfo->cfg.dev && dinfo->conf.pd_name[0] == '\0') + if (dinfo->cfg.dev) { name = device_get_name(dinfo->cfg.dev); - if (name) { - strncpy(dinfo->conf.pd_name, name, - sizeof(dinfo->conf.pd_name)); - dinfo->conf.pd_name[PCI_MAXNAMELEN] = 0; - dinfo->conf.pd_unit = - device_get_unit(dinfo->cfg.dev); + if (name) { + strncpy(dinfo->conf.pd_name, name, + sizeof(dinfo->conf.pd_name)); + dinfo->conf.pd_name[PCI_MAXNAMELEN] = 0; + dinfo->conf.pd_unit = + device_get_unit(dinfo->cfg.dev); + } else { + dinfo->conf.pd_name[0] = '\0'; + dinfo->conf.pd_unit = 0; + } } if ((pattern_buf == NULL) || --=-JzvqiRaU8sheWlcGbKlB-- From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 9 00:01:05 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1F30916A407 for ; Sat, 9 Dec 2006 00:01:05 +0000 (UTC) (envelope-from FreeBSD@insightbb.com) Received: from asav04.insightbb.com (gateway.insightbb.com [74.128.0.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3604B43C9D for ; Sat, 9 Dec 2006 00:00:03 +0000 (GMT) (envelope-from FreeBSD@insightbb.com) Received: from dhcp-74-130-161-48.insightbb.com (HELO lightning) ([74.130.161.48]) by asav04.insightbb.com with ESMTP; 08 Dec 2006 19:01:03 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAMeLeUVKgqEwYWdsb2JhbACNMxUOCSE From: Steven Friedrich To: freebsd-hackers@freebsd.org Date: Fri, 8 Dec 2006 19:01:02 -0500 User-Agent: KMail/1.9.4 References: <200612051734.32992.FreeBSD@insightbb.com> <200612060330.55759.josh@tcbug.org> In-Reply-To: <200612060330.55759.josh@tcbug.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612081901.02618.FreeBSD@insightbb.com> Subject: Re: can't connect to cvsup.freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Dec 2006 00:01:05 -0000 On Wednesday 06 December 2006 04:30, Josh Paetzel wrote: > On Tuesday 05 December 2006 16:34, Steven Friedrich wrote: > > but I'm able to connect to cvsup5 and cvsup6. > > > > The main ftp site says: Cannot connect to data port: Connection > > refused > > > > This started around the time of the cut-overs. > > *default host=cvsup.FreeBSD.org > > > gimpy# csup /usr/local/etc/ports-supfile > Connected to 198.104.69.57 > Updating collection ports-all/cvs > Edit ports/LEGAL > ... > > gimpy# dig a ftp.freebsd.org > ... > ftp.freebsd.org. 180 IN A 62.243.72.50 > ftp.freebsd.org. 180 IN A 204.152.184.73 > .... > > gimpy# dig a cvsup.freebsd.org > ..... > cvsup.freebsd.org. 3535 IN CNAME n.cwu.edu. > n.cwu.edu. 86335 IN A 198.104.69.57 > .... > > My point, in case you don't understand the ouput of all these commands > is that cvsup.freebsd.org and ftp.freebsd.org are presumably two > different machines, and it's entirely possible that ftp.freebsd.org > isn't a cvsup server. Sorry, I should have been more precise. Here's the output: root@lightning(p2)/usr/src 107% make update -------------------------------------------------------------- >>> Running /usr/local/bin/cvsup -------------------------------------------------------------- Parsing supfile "/usr/home/admin/cvsup/stable-supfile" Connecting to cvsup.FreeBSD.org Connected to cvsup.FreeBSD.org Server software version: SNAP_16_1h Negotiating file attribute support Exchanging collection information Establishing passive-mode data connection Cannot connect to data port: Connection refused I'm using cvsup (via make update) and this error doesn't occur if I set SUPHOST= cvsup5.FreeBSD.org in /etc/make.conf I've been using cvsup.FreeBSD.org for years... -- i386 FreeBSD 4.11-STABLE There are 10 types of people in this world. Ones that understand binary and then, the others. From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 9 20:18:25 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4625F16A415 for ; Sat, 9 Dec 2006 20:18:25 +0000 (UTC) (envelope-from bsd.devil@gmail.com) Received: from nz-out-0102.google.com (nz-out-0506.google.com [64.233.162.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id B542843CA0 for ; Sat, 9 Dec 2006 20:17:18 +0000 (GMT) (envelope-from bsd.devil@gmail.com) Received: by nz-out-0102.google.com with SMTP id i11so627963nzh for ; Sat, 09 Dec 2006 12:18:23 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=WM7VA7JDz/vS8sxHK0jVyYUrU6+ShhC5mmatok42gUYK/vYvmWLnLD0lgGZQ+tA2vcqNtfsio5m+UHkMAT1CZlglUy2hkuSLNhbNWUOzZZ7pkhcqGvRV7N+Hifwh3rHMWQx3j5Aq4+KHGC/UtBeGqsqzBPf16RMCZyomvfWawAw= Received: by 10.65.251.1 with SMTP id d1mr8110593qbs.1165695503700; Sat, 09 Dec 2006 12:18:23 -0800 (PST) Received: by 10.65.224.17 with HTTP; Sat, 9 Dec 2006 12:18:23 -0800 (PST) Message-ID: Date: Sat, 9 Dec 2006 15:18:23 -0500 From: "Vishal Patil" To: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org. MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Example network protocol implementation X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Dec 2006 20:18:25 -0000 Could someone point me to an example that shows a SIMPLE network protocol implemented over TCP/IP inside the FreeBSD kernel. I think I could look at the NFS client driver but is there an example simpler than that. Also is there a guide explaining how to go about developing TCP/IP based network protocols for FreeBSD. Thanks - Vishal From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 9 21:02:37 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E95C216A4CE; Sat, 9 Dec 2006 21:02:37 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [199.26.172.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67B5743CA6; Sat, 9 Dec 2006 21:01:24 +0000 (GMT) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id kB9L2TqR096658 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 9 Dec 2006 13:02:29 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id kB9L2Tmt096657; Sat, 9 Dec 2006 13:02:29 -0800 (PST) Received: from fbsd61 ([192.168.200.61]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA05503; Sat, 9 Dec 06 12:52:00 PST Date: Sat, 09 Dec 2006 12:53:38 -0800 From: perryh@pluto.rain.com To: bsd.devil@gmail.com Message-Id: <457b2252.FSOx8QPMmmbOnRoI%perryh@pluto.rain.com> References: In-Reply-To: User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Example network protocol implementation X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Dec 2006 21:02:38 -0000 "Vishal Patil" wrote: > Could someone point me to an example that shows a SIMPLE network > protocol implemented over TCP/IP inside the FreeBSD kernel. > I think I could look at the NFS client driver but is there an > example simpler than that. NFS normally runs over UDP, not TCP. Telnet is one of the simpler TCP-based applications, but it is not done in the kernel (nor are most network apps). Is there some particular reason why you need an example that is implemented inside the kernel, vs in userland? From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 9 22:43:20 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2D16116A412 for ; Sat, 9 Dec 2006 22:43:20 +0000 (UTC) (envelope-from dmw@unete.cl) Received: from qmail0.ifxnetworks.com (qmail0.ifxnetworks.com [200.110.128.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFD9E43CC6 for ; Sat, 9 Dec 2006 22:41:55 +0000 (GMT) (envelope-from dmw@unete.cl) Received: (qmail 483 invoked from network); 9 Dec 2006 22:43:00 -0000 X-Spam-DCC: CTc-dcc2: qmail0.ifxnetworks.com 1031; Body=1 Fuz1=1 Fuz2=1 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on qmail0.ifxnetworks.com X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.1.7 Received: from host74.200.73.29.dynamic.ifxnw.cl (HELO daemon) (dmw@unete.cl@[200.73.29.74]) (envelope-sender ) by qmail0.ifxnetworks.com (qmail-ldap-1.03) with SMTP for ; 9 Dec 2006 22:43:00 -0000 From: Daniel Molina Wegener Organization: DMW To: freebsd-hackers@freebsd.org Date: Sat, 9 Dec 2006 19:42:59 -0300 User-Agent: KMail/1.9.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612091943.00201.dmw@unete.cl> Cc: freebsd-questions@freebsd.org, Vishal Patil Subject: Re: Example network protocol implementation X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dmw@unete.cl List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Dec 2006 22:43:20 -0000 On Saturday 09 December 2006 17:18, Vishal Patil wrote: > Could someone point me to an example that shows a SIMPLE > network protocol implemented over TCP/IP inside the FreeBSD > kernel. I think I could look at the NFS client driver but is > there an example simpler than that. Also is there a guide > explaining how to go about developing TCP/IP based network > protocols for FreeBSD. Try looking at telnet(1) and telnetd(8) source code, also fetch(1) should works too... > Thanks > > - Vishal > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to > "freebsd-hackers-unsubscribe@freebsd.org" Best regards, -- . 0 . | Daniel Molina Wegener . . 0 | dmw at unete dot cl 0 0 0 | FreeBSD User