From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 00:34:34 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B87416A4CE for ; Sun, 16 Jan 2005 00:34:34 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92AEF43D2F for ; Sun, 16 Jan 2005 00:34:33 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 112BF513CE; Sat, 15 Jan 2005 16:34:33 -0800 (PST) Date: Sat, 15 Jan 2005 16:34:32 -0800 From: Kris Kennaway To: Kris Kennaway Message-ID: <20050116003432.GA448@xor.obsecurity.org> References: <20050115083847.GA47466@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZPt4rx8FFjLCG7dd" Content-Disposition: inline In-Reply-To: <20050115083847.GA47466@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i cc: current@FreeBSD.org Subject: Re: fstat triggered INVARIANTS panic in memrw() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 00:34:34 -0000 --ZPt4rx8FFjLCG7dd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 15, 2005 at 12:38:47AM -0800, Kris Kennaway wrote: > The full panic string is >=20 > panic: vm_fault: fault on nofault entry, addr: deae2000 >=20 > ----- Forwarded message from Kris Kennaway ----- >=20 > Date: Fri, 24 Dec 2004 17:42:08 -0800 > From: Kris Kennaway > To: current@FreeBSD.org > Cc: phk@FreeBSD.org > Subject: fstat triggered INVARIANTS panic > User-Agent: Mutt/1.4.2.1i >=20 > I ran fstat | more on a SMP 6.0 machine with kernel from about a month > ago, which had a lot of files open. It panicked with: >=20 > panic: vm_fault: fau >=20 > and got no further on the console, but I was able to break to DBB and > obtain the following traceback from fstat: >=20 > db> tr 94874 > Tracing pid 94874 tid 100815 td 0xc9ec1780 > sched_switch(c9ec1780,c34dc480,1,11a,88a1da96) at sched_switch+0x105 > mi_switch(6,c34dc480,c06d4ca0,271,c34dc5d0) at mi_switch+0x1d3 > maybe_preempt(c34dc480,1,c06d4c85,3d6,46) at maybe_preempt+0x11d > sched_add(c34dc480,4,c06d4ca0,1ce,c9ec1780,0,c06d11f3,197,197,c06d11f3) a= t sched_add+0x299 > setrunqueue(c34dc480,4,c06d11f3,197,c077a900) at setrunqueue+0x109 > ithread_schedule(c34d4380,0,eed96788,a0f1b,c9ec1780) at ithread_schedule+= 0xaf > intr_execute_handlers(c34d2ea8,eed967b8,eed96810,c0686583,45) at intr_exe= cute_handlers+0x74 > lapic_handle_intr(45) at lapic_handle_intr+0x2d > Xapic_isr2() at Xapic_isr2+0x33 > --- interrupt, eip =3D 0xc0519495, esp =3D 0xeed967fc, ebp =3D 0xeed96810= --- > critical_exit(c0768120,0,c06ea261,a23,1) at critical_exit+0x75 > siocnputc(c071b960,75,5,75,eed9696c) at siocnputc+0x9b > cnputc(75,10,1,0,c06d396c) at cnputc+0x65 > putchar(75,eed9696c,c0524e6c,30,13) at putchar+0xa8 > kvprintf(c06d3963,c0524780,eed9696c,a,eed96990) at kvprintf+0x87d > printf(c06d3963,c072c680,c06e688a,eed969bc,c9ec1780) at printf+0x54 > panic(c06e688a,deae6000,1,eed96aa8,eed96a98) at panic+0xe1 > vm_fault(c1059000,deae6000,1,0,c9ec1780) at vm_fault+0x1327 > trap_pfault(deae6000,c9ec1780,eed96ba8,c050e2c3,deae6000) at trap_pfault+= 0x82 > trap(c06e0018,10,c1050010,8058f20,deae5ffe) at trap+0x363 > calltrap() at calltrap+0x5 > --- trap 0xc, eip =3D 0xc0697f2a, esp =3D 0xeed96bcc, ebp =3D 0xeed96c04 = --- > generic_copyout(deadc0de,7ab7037c,eed96c84,54,5964d000) at generic_copyou= t+0x36 (kgdb) l *memrw+0x36 0xc06e3486 is in memrw (../../../i386/i386/mem.c:128). 123 124 if (!kernacc((caddr_t)(int)uio->uio_offset,= c, 125 uio->uio_rw =3D=3D UIO_READ ? 126 VM_PROT_READ : VM_PROT_WRITE)) 127 return (EFAULT); 128 error =3D uiomove((caddr_t)(int)uio->uio_of= fset, (int)c, uio); 129 continue; 130 } 131 /* else panic! */ 132 } > memrw(c34fad00,eed96c84,0,398,7ab7037c) at memrw+0x18a > devfs_read_f(c51773b8,eed96c84,ca75c800,0,c9ec1780) at devfs_read_f+0x142 > dofileread(4,804f000,7ab7037c,ffffffff,ffffffff) at dofileread+0x92 > read(c9ec1780,eed96d14,c,3ff,3) at read+0x75 > syscall(2f,2f,2f,7ab7037c,80b1078) at syscall+0x137 > Xint0x80_syscall() at Xint0x80_syscall+0x1f > --- syscall (3, FreeBSD ELF32, read), eip =3D 0x280d347f, esp =3D 0xbfbfe= 34c, ebp =3D 0xbfbfe378 --- >=20 > Note the deadc0de in generic_copyout(). >=20 > There seem to be several other bugs here that show off the well-known > brokenness of panic() and related code on SMP machines. >=20 > Kris >=20 >=20 >=20 > ----- End forwarded message ----- --ZPt4rx8FFjLCG7dd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB6baYWry0BWjoQKURAiG3AKCGx5g0UBT87jVpifbZHjlgW9sWBgCdGhM7 5SwlueIAd/aYuCJ9+NqjAOo= =+/+k -----END PGP SIGNATURE----- --ZPt4rx8FFjLCG7dd-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 01:02:16 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D8B516A4CE for ; Sun, 16 Jan 2005 01:02:16 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE83A43D39 for ; Sun, 16 Jan 2005 01:02:15 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id j0G12Fi8001631 for ; Sat, 15 Jan 2005 17:02:15 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j0G12Fvh001630 for freebsd-current@freebsd.org; Sat, 15 Jan 2005 17:02:15 -0800 (PST) (envelope-from obrien) Date: Sat, 15 Jan 2005 17:02:15 -0800 From: "David O'Brien" To: freebsd-current@freebsd.org Message-ID: <20050116010215.GA1616@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Subject: [PANIC] handle_written_inodeblock: live inodedep X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 01:02:16 -0000 Anyone want to claim ownership of this one? FreeBSD dragon.nuxi.com 6.0-CURRENT FreeBSD 6.0-CURRENT #463: Fri Jan 14 09:57:44 PST 2005 rootk@dragon.nuxi.com:/FBSD/src/sys/i386/compile/DRAGON i386 Script started on Sat Jan 15 16:58:16 2005 kgdb -c vmcore.2 kernel.debug.2 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". doadump () at pcpu.h:159 (kgdb) where #0 doadump () at pcpu.h:159 #1 0xc04d869a in boot (howto=260) at ../../../kern/kern_shutdown.c:398 #2 0xc04d8a53 in panic ( fmt=0xc066ee02 "handle_written_inodeblock: live inodedep") at ../../../kern/kern_shutdown.c:554 #3 0xc05c2b7d in handle_written_inodeblock (inodedep=0xcd2b4b00, bp=0xd8034480) at ../../../ufs/ffs/ffs_softdep.c:4458 #4 0xc05c1fb9 in softdep_disk_write_complete (bp=0xd8034480) at ../../../ufs/ffs/ffs_softdep.c:4013 #5 0xc052c8de in bufdone (bp=0xd8034480) at buf.h:428 #6 0xc04a3791 in g_vfs_done (bip=0xcccaa18c) at ../../../geom/geom_vfs.c:82 #7 0xc052c3b0 in biodone (bp=0xcccaa18c) at ../../../kern/vfs_bio.c:3034 #8 0xc04a0106 in g_io_schedule_up (tp=0xc3dc68a0) at ../../../geom/geom_io.c:489 #9 0xc04a04d8 in g_up_procbody () at ../../../geom/geom_kern.c:95 #10 0xc04c0f06 in fork_exit (callout=0xc04a0440 , arg=0x0, frame=0x0) at ../../../kern/kern_fork.c:790 #11 0xc061dedc in fork_trampoline () at ../../../i386/i386/exception.s:208 (kgdb) quit Script done on Sat Jan 15 16:58:36 2005 From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 01:04:38 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 11A8416A4CE for ; Sun, 16 Jan 2005 01:04:38 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id E41F943D49 for ; Sun, 16 Jan 2005 01:04:36 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id j0G14Ruv076377; Sun, 16 Jan 2005 11:34:27 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Sun, 16 Jan 2005 11:34:18 +1030 User-Agent: KMail/1.7.1 References: <20050115155538.GA36629@obiwan.tataz.chchile.org> In-Reply-To: <20050115155538.GA36629@obiwan.tataz.chchile.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4731777.ULLO5UKFEr"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501161134.25828.doconnor@gsoft.com.au> X-Spam-Score: -5.4 () IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: Jeremie Le Hen Subject: Re: no /dev/ums0 when module loaded X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 01:04:38 -0000 --nextPart4731777.ULLO5UKFEr Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sun, 16 Jan 2005 02:25, Jeremie Le Hen wrote: > I was playing a bit with devd(8) to have ums.ko automatically loaded > when I plug my USB mouse. This works quite well except that it seems > that ums0 is NOT detected when the module is loaded when the mouse is > already plugged. Thus, when I match against the uhid(4) device to get > the ums(4) module loaded, it cannot work since the module is inevitably > loaded after the moused is plugged. > > Is this a bug or a feature ? I've been told that whenever an USB device > is not grabbed by any driver on attach, it uses ugen(4) and it won't be > possible to ``move'' it from ugen(4) to ums(4) later. This is a problem with the USB stack - devices are not reprobed when a new= =20 module is loaded. I preload all the USB modules I plan to use (a bit annoying I admit). I=20 believe there is ongoing work in this area though. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart4731777.ULLO5UKFEr Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBB6b2Z5ZPcIHs/zowRAi+GAJ9Zi0LDGuFRNy9CHbTWWjsgKTlpuQCfWZhw 67qsHbb/jECfpdyf8lS+Hg8= =lGyT -----END PGP SIGNATURE----- --nextPart4731777.ULLO5UKFEr-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 01:14:12 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8221C16A4CE for ; Sun, 16 Jan 2005 01:14:12 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56EE243D2D for ; Sun, 16 Jan 2005 01:14:12 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1Cpyzb-0007BD-N4 for freebsd-current@freebsd.org; Sat, 15 Jan 2005 17:14:11 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16873.49123.305335.391160@ran.psg.com> Date: Sat, 15 Jan 2005 17:14:11 -0800 To: FreeBSD Current Subject: panic: handle_written_inodeblock: live inodedep X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 01:14:12 -0000 thinkpad t41 cvsup of 20:46 current handle_written_inodeblock: live inodedep no serial console, so dig pic of trace is at randy From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 02:40:52 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12C0C16A4CE for ; Sun, 16 Jan 2005 02:40:52 +0000 (GMT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4B5743D49 for ; Sun, 16 Jan 2005 02:40:51 +0000 (GMT) (envelope-from bsdaemon@comcast.net) Received: from fw.home (pcp05404374pcs.norstn01.pa.comcast.net[68.80.144.252]) by comcast.net (rwcrmhc12) with SMTP id <20050116024051014000tb2se>; Sun, 16 Jan 2005 02:40:51 +0000 Received: (qmail 64718 invoked from network); 16 Jan 2005 02:40:51 -0000 Received: from kris.home (HELO ?192.168.0.251?) (192.168.0.251) by fw.home with SMTP; 16 Jan 2005 02:40:51 -0000 Message-ID: <41E9D575.2010209@comcast.net> Date: Sat, 15 Jan 2005 21:46:13 -0500 From: Kris Maglione User-Agent: Mozilla Thunderbird 1.0 (X11/20041212) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <41E984AB.7060205@comcast.net> In-Reply-To: <41E984AB.7060205@comcast.net> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig41639BF6A4F1BBC326724840" Subject: [located] Laptop won't boot -CURRENT after 2004-27-08 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 02:40:52 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig41639BF6A4F1BBC326724840 Content-Type: multipart/mixed; boundary="------------090401090409060509080502" This is a multi-part message in MIME format. --------------090401090409060509080502 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Removing the call to "ata_catch_inflight" in dev/ata/ata-all.c fixed my problem. I'm hoping/guessing that this will fix it for the latest stable too, but I'm so tired of burning CDs that I'm not going to test it first, I'm just going to build it and hope. Should I report this as a bug? Does anyone know if a report has been filed for something similar? I searched freebsd-bugs for "inflight" and found nothing relevant. --------------090401090409060509080502 Content-Type: application/pgp-signature; name="signature.asc" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="signature.asc" LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KVmVyc2lvbjogR251UEcgdjEuMi42IChG cmVlQlNEKQpDb21tZW50OiBVc2luZyBHbnVQRyB3aXRoIFRodW5kZXJiaXJkIC0gaHR0cDov L2VuaWdtYWlsLm1vemRldi5vcmcKCmlEOERCUUZCNmRVY21jWGpjMVhCckFRUkFrU1hBS0NL Z0x3bGM0ZkRocEtaTGFzcnF2U0cvTmxXY0FDZmRLeXoKWEF3bXpVM2Z6NWVyc1JuWUxjUVFW dU09Cj1uanAvCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQoK --------------090401090409060509080502-- --------------enig41639BF6A4F1BBC326724840 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB6dV1mcXjc1XBrAQRAqgwAJ0fcV5fxwDe2/fx7Q0jKoieEXl7DQCeOuX4 3O8vSiJwd7Lt2NKtkCN5sqk= =EGo5 -----END PGP SIGNATURE----- --------------enig41639BF6A4F1BBC326724840-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 05:04:35 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C68B16A4CE; Sun, 16 Jan 2005 05:04:35 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C650543D48; Sun, 16 Jan 2005 05:04:34 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id DBAEB5180C; Sat, 15 Jan 2005 21:04:33 -0800 (PST) Date: Sat, 15 Jan 2005 21:04:33 -0800 From: Kris Kennaway To: Kris Kennaway Message-ID: <20050116050433.GA65733@xor.obsecurity.org> References: <20050115083847.GA47466@xor.obsecurity.org> <20050116003432.GA448@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6c2NcOVqGQ03X4Wi" Content-Disposition: inline In-Reply-To: <20050116003432.GA448@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i cc: alc@FreeBSD.org cc: current@FreeBSD.org Subject: Re: fstat triggered INVARIANTS panic in memrw() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 05:04:35 -0000 --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 15, 2005 at 04:34:32PM -0800, Kris Kennaway wrote: > > generic_copyout(deadc0de,7ab7037c,eed96c84,54,5964d000) at generic_copy= out+0x36 >=20 > (kgdb) l *memrw+0x36 > 0xc06e3486 is in memrw (../../../i386/i386/mem.c:128). > 123 > 124 if (!kernacc((caddr_t)(int)uio->uio_offse= t, c, > 125 uio->uio_rw =3D=3D UIO_READ ? > 126 VM_PROT_READ : VM_PROT_WRITE)) > 127 return (EFAULT); > 128 error =3D uiomove((caddr_t)(int)uio->uio_= offset, (int)c, uio); > 129 continue; > 130 } > 131 /* else panic! */ > 132 } >=20 > > memrw(c34fad00,eed96c84,0,398,7ab7037c) at memrw+0x18a > > devfs_read_f(c51773b8,eed96c84,ca75c800,0,c9ec1780) at devfs_read_f+0x1= 42 > > dofileread(4,804f000,7ab7037c,ffffffff,ffffffff) at dofileread+0x92 > > read(c9ec1780,eed96d14,c,3ff,3) at read+0x75 > > syscall(2f,2f,2f,7ab7037c,80b1078) at syscall+0x137 > > Xint0x80_syscall() at Xint0x80_syscall+0x1f > > --- syscall (3, FreeBSD ELF32, read), eip =3D 0x280d347f, esp =3D 0xbfb= fe34c, ebp =3D 0xbfbfe378 --- > >=20 > > Note the deadc0de in generic_copyout(). BTW, this is now wreaking havoc with my ability to finish building packages for 4.11-RELEASE (together with the softupdates panic also being reported), so anything someone can do to track this down is appreciated. Kris --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB6fXhWry0BWjoQKURAqM3AJwI7lLxpwGWhNNpD96gmJNbYbkJFQCfWXHl 7vii9+/tncBCFqyTEAGISZc= =iNC0 -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 05:06:17 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE60616A4CE; Sun, 16 Jan 2005 05:06:17 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 164C543D48; Sun, 16 Jan 2005 05:06:17 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6CD925180C; Sat, 15 Jan 2005 21:06:16 -0800 (PST) Date: Sat, 15 Jan 2005 21:06:16 -0800 From: Kris Kennaway To: David O'Brien Message-ID: <20050116050616.GA68089@xor.obsecurity.org> References: <20050116010215.GA1616@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="C7zPtVaVf+AK4Oqc" Content-Disposition: inline In-Reply-To: <20050116010215.GA1616@dragon.nuxi.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: [PANIC] handle_written_inodeblock: live inodedep X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 05:06:17 -0000 --C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 15, 2005 at 05:02:15PM -0800, David O'Brien wrote: > Anyone want to claim ownership of this one? >=20 > FreeBSD dragon.nuxi.com 6.0-CURRENT FreeBSD 6.0-CURRENT #463: Fri Jan 14 = 09:57:44 PST 2005 rootk@dragon.nuxi.com:/FBSD/src/sys/i386/compile/DRAGON = i386 >=20 > Script started on Sat Jan 15 16:58:16 2005 > kgdb -c vmcore.2 kernel.debug.2 > [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.s= o: 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 conditi= ons. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for detail= s. > This GDB was configured as "i386-marcel-freebsd". > doadump () at pcpu.h:159 > (kgdb) where > #0 doadump () at pcpu.h:159 > #1 0xc04d869a in boot (howto=3D260) at ../../../kern/kern_shutdown.c:398 > #2 0xc04d8a53 in panic ( > fmt=3D0xc066ee02 "handle_written_inodeblock: live inodedep") > at ../../../kern/kern_shutdown.c:554 > #3 0xc05c2b7d in handle_written_inodeblock (inodedep=3D0xcd2b4b00,=20 > bp=3D0xd8034480) at ../../../ufs/ffs/ffs_softdep.c:4458 > #4 0xc05c1fb9 in softdep_disk_write_complete (bp=3D0xd8034480) > at ../../../ufs/ffs/ffs_softdep.c:4013 > #5 0xc052c8de in bufdone (bp=3D0xd8034480) at buf.h:428 > #6 0xc04a3791 in g_vfs_done (bip=3D0xcccaa18c) at ../../../geom/geom_vfs= .c:82 > #7 0xc052c3b0 in biodone (bp=3D0xcccaa18c) at ../../../kern/vfs_bio.c:30= 34 > #8 0xc04a0106 in g_io_schedule_up (tp=3D0xc3dc68a0) > at ../../../geom/geom_io.c:489 > #9 0xc04a04d8 in g_up_procbody () at ../../../geom/geom_kern.c:95 > #10 0xc04c0f06 in fork_exit (callout=3D0xc04a0440 , arg=3D= 0x0,=20 > frame=3D0x0) at ../../../kern/kern_fork.c:790 > #11 0xc061dedc in fork_trampoline () at ../../../i386/i386/exception.s:208 Here's a variant: dev =3D ad0d, block =3D 579936, fs =3D panic: ffs_blkfree: freeing free block KDB: enter: panic [thread pid 37 tid 100023 ] Stopped at kdb_enter+0x32: leal 0(%esi),%esi db> tr Tracing pid 37 tid 100023 td 0xc1965450 kdb_enter(c071a867,c077cb40,c072dd1b,d4116ae4,c1965450) at kdb_enter+0x32 panic(c072dd1b,c1d97480,8d960,0,c1f3d0d4) at panic+0x14d ffs_blkfree(c1f3d000,c1f95cf0,8d960,0,8000) at ffs_blkfree+0x539 indir_trunc(46ca80,0,0,c,0) at indir_trunc+0x20a handle_workitem_freeblocks(0,c1a02c00,2,634,0) at handle_workitem_freeblock= s+0x354 process_worklist_item(1,41e9f527,0,c1965450,c0722d8e) at process_worklist_i= tem+0x207 softdep_process_worklist(0,0,c0722d8e,634,0) at softdep_process_worklist+0x= 62 sched_sync(0,d4116d48,c07180ca,30e,65722064) at sched_sync+0x571 fork_exit(c058b2a0,0,d4116d48) at fork_exit+0xa9 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip =3D 0, esp =3D 0xd4116d7c, ebp =3D 0 --- --C7zPtVaVf+AK4Oqc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB6fZIWry0BWjoQKURAhXaAJ4jUx7MV5zo9WYVBphqZFQ1adjXfgCeOxpE keSu8WEz963kuDdiCQmkn18= =e75h -----END PGP SIGNATURE----- --C7zPtVaVf+AK4Oqc-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 05:14:13 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 758B616A4CE for ; Sun, 16 Jan 2005 05:14:13 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E18D43D46 for ; Sun, 16 Jan 2005 05:14:13 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1Cq2js-000DMK-Li for freebsd-current@freebsd.org; Sat, 15 Jan 2005 21:14:12 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16873.63524.262634.74964@ran.psg.com> Date: Sat, 15 Jan 2005 21:14:12 -0800 To: FreeBSD Current Subject: panic: ffs_blkfree: freeing free block X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 05:14:13 -0000 second panic on today's current. related. both are now at randy From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 07:01:01 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E1ED216A4CE for ; Sun, 16 Jan 2005 07:01:01 +0000 (GMT) Received: from lakermmtao04.cox.net (lakermmtao04.cox.net [68.230.240.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 620FA43D41 for ; Sun, 16 Jan 2005 07:01:01 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.14.122.164]) by lakermmtao04.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP <20050116070059.EERF22354.lakermmtao04.cox.net@dolphin.local.net>; Sun, 16 Jan 2005 02:00:59 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with ESMTP id j0G7103i001678; Sun, 16 Jan 2005 01:01:00 -0600 (CST) (envelope-from conrads@cox.net) Date: Sun, 16 Jan 2005 01:00:55 -0600 From: "Conrad J. Sabatier" To: Randy Bush Message-ID: <20050116010055.6de4377b@dolphin.local.net> In-Reply-To: <16873.63524.262634.74964@ran.psg.com> References: <16873.63524.262634.74964@ran.psg.com> X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: FreeBSD Current Subject: Re: panic: ffs_blkfree: freeing free block X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 07:01:02 -0000 On Sat, 15 Jan 2005 21:14:12 -0800, Randy Bush wrote: > second panic on today's current. related. both are now at > > > > randy I just upgraded, and have also already seen the ffs_blkfree panic several times in a row. :-( -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 08:08:54 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 49A9E16A4CE for ; Sun, 16 Jan 2005 08:08:54 +0000 (GMT) Received: from av9-2-sn4.m-sp.skanova.net (av9-2-sn4.m-sp.skanova.net [81.228.10.107]) by mx1.FreeBSD.org (Postfix) with ESMTP id F018F43D2F for ; Sun, 16 Jan 2005 08:08:53 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av9-2-sn4.m-sp.skanova.net (Postfix, from userid 502) id 540ED37E7A; Sun, 16 Jan 2005 09:08:53 +0100 (CET) Received: from smtp2-2-sn4.m-sp.skanova.net (smtp2-2-sn4.m-sp.skanova.net [81.228.10.182]) by av9-2-sn4.m-sp.skanova.net (Postfix) with ESMTP id 4328137E61 for ; Sun, 16 Jan 2005 09:08:53 +0100 (CET) Received: from sentinel (h217n1fls11o822.telia.com [213.64.66.217]) by smtp2-2-sn4.m-sp.skanova.net (Postfix) with ESMTP id 2939337E44 for ; Sun, 16 Jan 2005 09:08:53 +0100 (CET) From: "Daniel Eriksson" To: Date: Sun, 16 Jan 2005 09:08:48 +0100 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Thread-Index: AcT7iWzwBlk9oW4EQVqT9F2y7ERcTAAF804g In-Reply-To: <20050116050616.GA68089@xor.obsecurity.org> Subject: RE: [PANIC] handle_written_inodeblock: live inodedep X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 08:08:54 -0000 Just got this on a newly updated 6-CURRENT (2005.01.15.21.30.00) machine while running portupgrade: panic: handle_written_inodeblock: live inodedep cpuid = 1 KDB: enter: panic [thread pid 3 tid 100044 ] Stopped at kdb_enter+0x32: leave db> where Tracing pid 3 tid 100044 td 0xc1eb75c0 kdb_enter(c0753ed6,1,c07608f9,e06c5bec,d187a350) at kdb_enter+0x32 panic(c07608f9,9af91,c0787680,2,0) at panic+0x1e9 softdep_disk_write_complete(d187a350,e06c5cb8,c05296de,c20c2960,c07aaac4) at softdep_disk_write_complete+0xb8b bufdone(d187a350,c31757bc,e06c5ccc,c052c2af,c07aaac4) at bufdone+0x2c2 g_vfs_done(c31757bc,c07aa9e8,24c,c0750053,64) at g_vfs_done+0x69 g_io_schedule_up(c1eb75c0,4c,0,0,0) at g_io_schedule_up+0x70 g_up_procbody(0,e06c5d48,0,0,0) at g_up_procbody+0x98 fork_exit(c0529dd0,0,e06c5d48) at fork_exit+0x62 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe06c5d7c, ebp = 0 --- /Daniel Eriksson From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 08:57:41 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BD4216A4CE for ; Sun, 16 Jan 2005 08:57:41 +0000 (GMT) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BA0D43D4C for ; Sun, 16 Jan 2005 08:57:40 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received-SPF: pass (eva.fit.vutbr.cz: domain of xdivac02@eva.fit.vutbr.cz designates 127.0.0.1 as permitted sender) receiver=eva.fit.vutbr.cz; client_ip=127.0.0.1; envelope-from=xdivac02@eva.fit.vutbr.cz; Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (8.12.11/8.12.11) with ESMTP id j0G8vYxh027052 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 16 Jan 2005 09:57:34 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.12.11/8.12.5/Submit) id j0G8vYNM027051; Sun, 16 Jan 2005 09:57:34 +0100 (CET) Date: Sun, 16 Jan 2005 09:57:34 +0100 From: Divacky Roman To: Kris Maglione Message-ID: <20050116085734.GA26922@stud.fit.vutbr.cz> References: <20050112092641.GA61635@stud.fit.vutbr.cz> <20050115134715.GA769@zaphod.nitro.dk> <41E94650.2060609@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41E94650.2060609@comcast.net> User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: freebsd-current@freebsd.org Subject: Re: non-killable process X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 08:57:41 -0000 On Sat, Jan 15, 2005 at 11:35:28AM -0500, Kris Maglione wrote: > Simon L. Nielsen wrote: > > >On 2005.01.12 10:26:41 +0100, Divacky Roman wrote: > > > > > >>hi, > >> > >>I have CFLAGS=-Os (dunno if it matters) compiled ports/net/iftop. and > >>whenever > >>I run it on recent 6-current it "hangs": > >> 880 v4 R+ 0:00.05 iftop > >>(ps ax output) > >> > >>and it cannot be killed - I can repeat it, so this might reveal some bug. > >>I use > >>sched_ule. > >> > >From > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/basics-daemons.htm > > SIGKILL can not be ignored by a process. This is the ``I do not care > what you are doing, stop right now'' signal. If you send SIGKILL to a > process then FreeBSD will stop that process there and then[1]. > > [1] > > Not quite true--there are a few things that can not be interrupted. For > example, if the process is trying to read from a file that is on another > computer on the network, and the other computer has gone away for some > reason (been turned off, or the network has a fault), then the process > is said to be ``uninterruptible''. Eventually the process will time out, > typically after two minutes. As soon as this time out occurs the process > will be killed. this is not the case... 1) it doesnt time out (I've tried to wait for some hours - no change) 2) it doesnt wait on anything (no [tm]sleep or something) ps axl: 0 652 589 0 20 0 2320 1792 - R+ p2 0:00.05 iftop (as you can see mwchan is -) 3) it didnt behave this way $sometime ago hence I think this is a bug roman From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 08:57:50 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DFB716A4D6 for ; Sun, 16 Jan 2005 08:57:50 +0000 (GMT) Received: from lakermmtao12.cox.net (lakermmtao12.cox.net [68.230.240.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7E9E43D49 for ; Sun, 16 Jan 2005 08:57:49 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.14.122.164]) by lakermmtao12.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20050116085748.BUBV1656.lakermmtao12.cox.net@dolphin.local.net>; Sun, 16 Jan 2005 03:57:48 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with ESMTP id j0G8vmkS003382; Sun, 16 Jan 2005 02:57:48 -0600 (CST) (envelope-from conrads@cox.net) Date: Sun, 16 Jan 2005 02:57:43 -0600 From: "Conrad J. Sabatier" To: "Conrad J. Sabatier" Message-ID: <20050116025743.47b08be1@dolphin.local.net> In-Reply-To: <20050116010055.6de4377b@dolphin.local.net> References: <16873.63524.262634.74964@ran.psg.com> <20050116010055.6de4377b@dolphin.local.net> X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: Randy Bush cc: FreeBSD Current Subject: Re: panic: ffs_blkfree: freeing free block X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 08:57:50 -0000 On Sun, 16 Jan 2005 01:00:55 -0600, "Conrad J. Sabatier" wrote: > On Sat, 15 Jan 2005 21:14:12 -0800, Randy Bush wrote: > > > second panic on today's current. related. both are now at > > > > > > > > randy > > I just upgraded, and have also already seen the ffs_blkfree panic > several times in a row. :-( Hmm, after running fsck a few times to make sure all my file systems were in top condition, the panic has yet to occur. -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 09:15:10 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3783616A4CE for ; Sun, 16 Jan 2005 09:15:10 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6587243D2D for ; Sun, 16 Jan 2005 09:15:09 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 4CC4B1FF9AB for ; Sun, 16 Jan 2005 10:15:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 2B9501FF931; Sun, 16 Jan 2005 10:15:05 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id DC73315698; Sun, 16 Jan 2005 09:13:28 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id D1AEE15653 for ; Sun, 16 Jan 2005 09:13:28 +0000 (UTC) Date: Sun, 16 Jan 2005 09:13:28 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: FreeBSD current mailing list Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Subject: panic: biodone: bp 0xcbe9c9e9 already done X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 09:15:10 -0000 Hi, following is hand transcriped because the box hadn't had a serial console for historical reasons :( Unfortunately I also couldn't get a core. The machine is MP with HEAD from around Jan 12 19:38 UTC, with PREEMPTION and SU. panic: biodone: bp 0xcbe9c9e9 already done cpuid = 1 KBD: enter: panic [thread pid 3 tid 100045 ] Stopped at kdb_enter+0x2c: leav db> where Tracing pid 3 tid 100045 td 0xc1a0773 kdb_enter panic bufdone(cbe9c0e0,c1adc18c,d53dad0c,c05f90cb,c1adcdec) at bufdone+0x364 bufdonebio(c1adcdec,d53dacd4,8,c08ac1f2,1e4) at bufdonebio+0x4e g_io_schedule_up(c1a07730,c05f9320,d53dad34,c0628f76,0) at g_io_schedule_up+0xab g_up_procbody(0,d53dad48,0,c05f9320,0) at g_up_procbody+0x5a fork_exit() at fork_exit+0x7e fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd53dad7c, ebp = 0 --- db> show locks exlusive sleep mutx Giant r = 0 (0xc09b04c0) locked @ /local/building/FreeBSD/HEAD/sys/kern/vfs_bio.c:3109 exlusive sleep mutx g_xup r = 0 (0xd53dacd4) locked @ /local/building/FreeBSD/HEAD/sys/geom/geom_io.c:484 -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 09:27:44 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A52F16A4CE for ; Sun, 16 Jan 2005 09:27:44 +0000 (GMT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9A3C43D3F for ; Sun, 16 Jan 2005 09:27:43 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.1/8.13.1) with ESMTP id j0G9Raci037056; Sun, 16 Jan 2005 01:27:40 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200501160927.j0G9Raci037056@gw.catspoiler.org> Date: Sun, 16 Jan 2005 01:27:36 -0800 (PST) From: Don Lewis To: phk@phk.freebsd.dk In-Reply-To: <200501152329.j0FNTqrf035987@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT cc: current@FreeBSD.org Subject: Re: reproduced: ffs_blkfree: freeing free block X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 09:27:44 -0000 On 15 Jan, Don Lewis wrote: > On 15 Jan, Poul-Henning Kamp wrote: >> >> Quite by accident my test-machine here can now reliably reproduce >> the dreaded "panic: ffs_blkfree: freeing free block" in a few minutes >> of time. >> >> It is very interesting that the location of the actual error is a >> very narrow stripe of the filesystem: >> >> dev = ad8, block = 13456368, fs = /hex >> dev = ad8, block = 13455888, fs = /hex >> dev = ad8, block = 13454688, fs = /hex >> dev = ad8, block = 13455040, fs = /hex >> dev = ad8, block = 13455200, fs = /hex >> dev = ad8, block = 13455880, fs = /hex >> >> The application I'm running at the time adds/modifies records in a >> db(3) hash file and nothing much besides. >> >> Before I start implementing complete I/O traces and spend days >> groveling over UFS/FFS on-disk bits, are there anybody who has >> suggestions for things I should try to enable/disable to narrow >> this down ? > > I'm reasonably certain that the on-disk bits are ok. I'm seeing it in > the case where a freshly written file is being re-written. If I unmount > the file system after the file is initially created, the file system > fsck's clean, and if I then remount the file system, I am unable to > reproduce the problem. Fsdb lists the block causing the panic as one > that was initially allocated to the file. It looks like the in-core > block bitmap is getting corrupted. > > In my openoffice build example, the following final step is sufficient > to trigger the panic: > jot -b x 174113 > \ > /mnt/usr/ports/editors/openoffice-1.1/work/config_office/configure > Merely truncating the file with "cat /dev/null" does not appear to be > sufficient to trigger the panic. If I run the openoffice-1.1 make targets from extract through patch-autotools, then truncate and rewrite teh configure script, I can reproduce the panic: fsync /mnt/usr/ports/editors/openoffice-1.1/work/config_office/configure ls -li /mnt/usr/ports/editors/openoffice-1.1/work/config_office/configure 1274809 -rwxr-xr-x 1 root wheel 348277 Aug 27 03:03 /mnt/usr/ports/editors/openoffice-1.1/work/config_office/configure fsdb -r /dev/da0s2a ** /dev/da0s2a (NO WRITE) Examining file system `/dev/da0s2a' Last Mounted on /mnt current inode: directory I=2 MODE=40755 SIZE=512 MTIME=Feb 14 11:55:43 2004 [0 nsec] CTIME=Feb 14 11:55:43 2004 [0 nsec] ATIME=Jan 14 18:24:05 2005 [0 nsec] OWNER=root GRP=wheel LINKCNT=7 FLAGS=0 BLKCNT=4 GEN=53557245 fsdb (inum: 2)> inode 1274809 current inode: regular file I=1274809 MODE=100755 SIZE=348277 MTIME=Aug 27 03:03:28 2004 [0 nsec] CTIME=Jan 16 00:47:00 2005 [0 nsec] ATIME=Dec 31 16:00:00 1969 [0 nsec] OWNER=root GRP=wheel LINKCNT=1 FLAGS=0 BLKCNT=2e0 GEN=791e742c fsdb (inum: 1274809)> blocks Blocks for inode 1274809: Direct blocks: 5089312, 5089320, 5089328, 5089336, 5089344, 5089352, 5089360, 5089368, 5089424, 5089432, 5089440, 5089448 Indirect blocks: 5089456, 5089464, 5089472, 5089480, 5089488, 5089496, 5089504, 5089512, 5089520, 5089528, fsdb (inum: 1274809)> q cat /dev/null > /mnt/usr/ports/editors/openoffice-1.1/work/config_office/configure sleep 120 jot -b x 174113 > /mnt/usr/ports/editors/openoffice-1.1/work/config_office/configure sleep 120 The system panics during this final sleep: dev = da0s2a, block = 5089472, fs = /mnt panic: ffs_blkfree: freeing free block cpuid = 0 KDB: enter: panic The block number in question is one that was initially allocated to the configure file. Because of the sleep command, I would think that the free block bitmap should have been updated to mark this block free sometime between when the configure file was truncated by "cat /dev/null" and when the configure file was re-written by jot, so it looks like block 5089472 is being freed twice. Without the final jot command to rewrite the file, I can wait an arbitrarily long time and the system will not panic. GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". doadump () at pcpu.h:159 (kgdb) where #0 doadump () at pcpu.h:159 #1 0xc04661e6 in db_fncall (dummy1=-1065580187, dummy2=0, dummy3=-455755064, dummy4=0xe4d5ba60 "\224Кеф") at /usr/src/sys/ddb/db_command.c:531 #2 0xc046657c in db_command_loop () at /usr/src/sys/ddb/db_command.c:349 #3 0xc0467fa8 in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_main.c:221 #4 0xc063baee in kdb_trap (type=3, code=0, tf=0xe4d5bb88) at /usr/src/sys/kern/subr_kdb.c:421 #5 0xc07dba6c in trap (frame= {tf_fs = 24, tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi = 1, tf_ebp = -455754808, tf_isp = -455754828, tf_ebx = -455754764, tf_edx = -1065055680, tf_ecx = -1064242016, tf_eax = -1065046973, tf_trapno = 3, tf_err = 0, tf_eip = -1067206872, tf_cs = 8, tf_eflags = 646, tf_esp = -455754776, tf_ss = -1067304789}) at /usr/src/sys/i386/i386/trap.c:573 #6 0xc07ca3da in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0x00000018 in ?? () #8 0x00000010 in ?? () #9 0x00000010 in ?? () #10 0x00000000 in ?? () #11 0x00000001 in ?? () #12 0xe4d5bbc8 in ?? () #13 0xe4d5bbb4 in ?? () #14 0xe4d5bbf4 in ?? () #15 0xc0848a40 in ?? () #16 0xc090f4a0 in shutdown_howto () #17 0xc084ac43 in ?? () #18 0x00000003 in ?? () #19 0x00000000 in ?? () #20 0xc063b728 in kdb_enter (msg=0x0) at cpufunc.h:56 #21 0xc06238ab in panic (fmt=0x0) at /usr/src/sys/kern/kern_shutdown.c:538 #22 0xc0753f58 in ffs_blkfree (fs=0xc2861800, devvp=0xc298e114, bno=5089472, size=16384, inum=1274809) at /usr/src/sys/ufs/ffs/ffs_alloc.c:1791 #23 0xc0762dae in handle_workitem_freefrag (freefrag=0xc63ae540) at /usr/src/sys/ufs/ffs/ffs_softdep.c:1588 #24 0xc0765a38 in process_worklist_item (matchmnt=0x0, flags=0) at /usr/src/sys/ufs/ffs/ffs_softdep.c:768 #25 0xc076a3aa in softdep_process_worklist (matchmnt=0x0) at /usr/src/sys/ufs/ffs/ffs_softdep.c:623 #26 0xc0677f12 in sched_sync () at /usr/src/sys/kern/vfs_subr.c:1595 #27 0xc0610ba2 in fork_exit (callout=0xc0677b60 , arg=0x0, frame=0xe4d5bd48) at /usr/src/sys/kern/kern_fork.c:787 #28 0xc07ca43c in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:208 Note that the inum parameter to ffs_blkfree() matches the inode number of the configure file. I would not expect softupdates to be freeing blocks for this inode at the time when the machine paniced. At the time of the panic, there is one more item on the worklist, another struct freefrag that points to block #5089464. (kgdb) frame 25 #25 0xc076a3aa in softdep_process_worklist (matchmnt=0x0) at /usr/src/sys/ufs/ffs/ffs_softdep.c:623 623 if ((cnt = process_worklist_item(matchmnt, 0)) == -1) (kgdb) print num_on_worklist $2 = 2 (kgdb) frame 24 #24 0xc0765a38 in process_worklist_item (matchmnt=0x0, flags=0) at /usr/src/sys/ufs/ffs/ffs_softdep.c:768 768 handle_workitem_freefrag(WK_FREEFRAG(wk)); print *(struct freefrag *)wk->wk_list->le_next $8 = {ff_list = {wk_list = {le_next = 0xc57cd9e0, le_prev = 0xc096a018}, wk_type = 7, wk_state = 32768}, ff_mnt = 0xc26a9800, ff_blkno = 5089464, ff_fragsize = 16384, ff_inum = 1274809} From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 09:36:21 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67B1216A4CE for ; Sun, 16 Jan 2005 09:36:21 +0000 (GMT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17BB943D39 for ; Sun, 16 Jan 2005 09:36:21 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.1/8.13.1) with ESMTP id j0G9a8Ao037080; Sun, 16 Jan 2005 01:36:12 -0800 (PST) (envelope-from truckman@FreeBSD.org) Message-Id: <200501160936.j0G9a8Ao037080@gw.catspoiler.org> Date: Sun, 16 Jan 2005 01:36:08 -0800 (PST) From: Don Lewis To: conrads@cox.net In-Reply-To: <20050116025743.47b08be1@dolphin.local.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii cc: randy@psg.com cc: freebsd-current@FreeBSD.org Subject: Re: panic: ffs_blkfree: freeing free block X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 09:36:21 -0000 On 16 Jan, Conrad J. Sabatier wrote: > On Sun, 16 Jan 2005 01:00:55 -0600, "Conrad J. Sabatier" > wrote: > >> On Sat, 15 Jan 2005 21:14:12 -0800, Randy Bush wrote: >> >> > second panic on today's current. related. both are now at >> > >> > >> > >> > randy >> >> I just upgraded, and have also already seen the ffs_blkfree panic >> several times in a row. :-( > > Hmm, after running fsck a few times to make sure all my file systems > were in top condition, the panic has yet to occur. Don't get your hopes up. I can reliably reproduce this problem on a freshly fsck'ed file system. From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 10:06:57 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4344816A4CE for ; Sun, 16 Jan 2005 10:06:57 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD8C243D2D for ; Sun, 16 Jan 2005 10:06:56 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from error404.nls.net (ketrien@error404.nls.net [216.144.36.24]) by error404.nls.net (8.13.1/8.13.1) with ESMTP id j0GAAceI034983 for ; Sun, 16 Jan 2005 05:10:38 -0500 (EST) (envelope-from ketrien@error404.nls.net) Date: Sun, 16 Jan 2005 05:10:38 -0500 (EST) From: "Ketrien I. Saihr-Kenchedra" X-X-Sender: ketrien@bahre.achedra.org To: current@freebsd.org Message-ID: <20050116044737.B13189@bahre.achedra.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV 0.80/631/Wed Dec 15 09:01:14 2004 clamav-milter version 0.80j on bahre.achedra.org X-Virus-Status: Clean Subject: LOR in Jan16 -CUR, ACPI related possibly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 10:06:57 -0000 Apologies for the lack of debug, but the workspace around here is really a disaster area, and console's acting up. I tried to get a dump, no go even w/call doadump. kgdb's not working again either, go figure. (I have related work that gave occasion to find this LOR.) Sorry for the seeming lack of detail; I really have no way to accurately transcribe this at the moment. It is 100% reproducible at least, but does not panic() the system. It's as simple as kldload if_pcn, kldunload if_pcn, LOR. 1st pcn (Network driver) sys/pci/if_pcn.c:1385 2nd ACPI root bus sys/dev/acpica/acpi.c:1050 witness_checkorder _sx_xlock acpi_release_resource bus_generic_release_resource bus_release_resource pcn_detach device_detach devclass_delete_driver driver_module_handler module_unload linker_file_unload kern_kldunload syscall Xint0x80_syscall Now, on a similar note, I'm currently working on the pcn(4) driver, and encountered a not-dissimilar LOR versus ACPI again, this on load. I was able to debug that one somewhat, but not scribble much down. This LOR does panic() the system. 1st pcn 2nd ACPI root bus pcn_attach device_attach pci_driver_added devclass_add_driver driver_module_handler module_register_init linker_load_module My code uses mdodd@'s changes to probe(), which, contrary to wording, does still lock out of necessity, but has not exhibited LOR before. The flow is unchaged up to the LOR occurance, which appears to occur at ether_ifattach(). I'm still rooting around to see if it _is_ occuring earlier, but it doesn't look like it. This one, I can't reproduce so well, due to a panic in uma that keeps popping up. Afraid I'm a little stuck on this one; I'm still trying to get gdb working without success. Any chance someone could take a look at this? Thanks, as usual. -Ketrien I. Saihr-Kenchedra caps lock is not your friend. In fact, it is your mortal enemy and it made very disparaging remarks about your mother. From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 11:38:16 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C7E716A4CE for ; Sun, 16 Jan 2005 11:38:16 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63D2143D31 for ; Sun, 16 Jan 2005 11:38:16 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1Cq8jX-000NG5-Nk; Sun, 16 Jan 2005 03:38:15 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16874.21031.225539.158812@ran.psg.com> Date: Sun, 16 Jan 2005 03:38:15 -0800 To: "Conrad J. Sabatier" References: <16873.63524.262634.74964@ran.psg.com> <20050116010055.6de4377b@dolphin.local.net> cc: FreeBSD Current Subject: Re: panic: ffs_blkfree: freeing free block X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 11:38:16 -0000 > On Sat, 15 Jan 2005 21:14:12 -0800, Randy Bush wrote: >> second panic on today's current. related. both are now at >> > I just upgraded, and have also already seen the ffs_blkfree panic > several times in a row. :-( there is no extra charge for the repeats :-) it is repeatable enough, as is its friend the ffs_blkfree panic, that i have frozen that machine waiting for a fix. randy From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 11:57:04 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3292216A4CE for ; Sun, 16 Jan 2005 11:57:04 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04A9A43D3F for ; Sun, 16 Jan 2005 11:57:04 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1Cq91j-000Nkm-Io; Sun, 16 Jan 2005 03:57:03 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16874.22159.69806.417323@ran.psg.com> Date: Sun, 16 Jan 2005 03:57:03 -0800 To: "Conrad J. Sabatier" References: <16873.63524.262634.74964@ran.psg.com> <20050116010055.6de4377b@dolphin.local.net> <20050116025743.47b08be1@dolphin.local.net> cc: FreeBSD Current Subject: Re: panic: ffs_blkfree: freeing free block X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 11:57:04 -0000 > Hmm, after running fsck a few times to make sure all my file systems > were in top condition, the panic has yet to occur. i think you need goat and chicken entrails to go with the crossed fingers. i fscked three times in single user, booted multi, did portupgrade -rf -o emulators/linux_base-8 emulators/linux_base and had the handle_written_inodeblock: live inodedep panic within two minutes randy From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 12:22:35 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27D8916A4CE for ; Sun, 16 Jan 2005 12:22:35 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FFB943D2D for ; Sun, 16 Jan 2005 12:22:34 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id j0GCINJN060976 for ; Sun, 16 Jan 2005 07:18:23 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)j0GCIMki060973 for ; Sun, 16 Jan 2005 12:18:23 GMT (envelope-from robert@fledge.watson.org) Date: Sun, 16 Jan 2005 12:18:22 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: current@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: gratuitous gcc warnings: unused function arguments? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 12:22:35 -0000 At some point in the relatively recent past, we began to generate warnings for unused arguments in function definitions. This is a fairly irritating practice, as it interacts poorly with function implementations plugged into pluggable function interfaces, such as PAM, main(), etc. Here's an example of a particularly irritating instance of the warning: static void usage(void) { fprintf(errno, "program: too many arguments\n"); exit(-1); } int main(int argc, char *argv[]) { if (argc != 1) usage(); dostuff(); } Just to be clear: this program accepts no arguments, and is considered to be used in error if passed an argument. This is because someday the program will likely accept arguments and not consider them to be no-ops, so in the interests of command line compatibility, we reject arguments today as an error in usage. If compiled with WARNS=3, the following error occurs: cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c program.c program.c:48: warning: unused parameter 'argv' *** Error code 1 However, gcc also knows that correct use of the C language doesn't permit us to only declare argc as an argument, resulting in a similar warning if argv is removed: cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -c program.c program.c:49: warning: 'main' takes only zero or two arguments *** Error code 1 Graffiting large piles of code with "__unused" strikes me as equally high up there on the irritating scale, as we have a non-trivial number of situations where functions implement APIs where some of the arguments provided to the API are not required for a full implementation of the API. For example, PAM entry points for PAM modules contain many arguments, and not all of those arguments are used by every implementation -- pam_kerberosIV doesn't need all the information passed, for example, to the session management interface. One of the reasons why I find __unused irritating is the following sort of situation: int dummyfunction(int arg1, int arg2, char *argv) { #ifdef DUMMY_USES_ARGV if (argv != NULL) printf("dummyfunction: %s\n", argv); #endif return (arg1 + arg2); } With the new world order, we would have to ifdef the function definition to conditionally use __unused in order to allow the function to compile with or without the #ifdef. I'm not sure what is required to disable this warning, but I'd like to see us make it optional and not keyed to lower warning levels (such as 3). Robert N M Watson From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 14:03:09 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93AD616A4CE for ; Sun, 16 Jan 2005 14:03:09 +0000 (GMT) Received: from lakermmtao10.cox.net (lakermmtao10.cox.net [68.230.240.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C70043D3F for ; Sun, 16 Jan 2005 14:03:09 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.14.122.164]) by lakermmtao10.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20050116140306.HIQZ1657.lakermmtao10.cox.net@dolphin.local.net>; Sun, 16 Jan 2005 09:03:06 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with ESMTP id j0GE35vB009508; Sun, 16 Jan 2005 08:03:05 -0600 (CST) (envelope-from conrads@cox.net) Date: Sun, 16 Jan 2005 08:03:00 -0600 From: "Conrad J. Sabatier" To: Randy Bush Message-ID: <20050116080300.056b4e6e@dolphin.local.net> In-Reply-To: <16874.22159.69806.417323@ran.psg.com> References: <16873.63524.262634.74964@ran.psg.com> <20050116010055.6de4377b@dolphin.local.net> <20050116025743.47b08be1@dolphin.local.net> <16874.22159.69806.417323@ran.psg.com> X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: FreeBSD Current Subject: Re: panic: ffs_blkfree: freeing free block X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 14:03:09 -0000 On Sun, 16 Jan 2005 03:57:03 -0800, Randy Bush wrote: > > Hmm, after running fsck a few times to make sure all my file systems > > were in top condition, the panic has yet to occur. > fingers> > > i think you need goat and chicken entrails to go with the crossed > fingers. i fscked three times in single user, booted multi, did > portupgrade -rf -o emulators/linux_base-8 emulators/linux_base > and had the > handle_written_inodeblock: live inodedep > panic within two minutes > > randy > Sho 'nuff, just happened again. :-) -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 14:41:34 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55D5D16A4D3; Sun, 16 Jan 2005 14:41:34 +0000 (GMT) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8858E43D1F; Sun, 16 Jan 2005 14:41:33 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from gothmog.gr (patr530-a016.otenet.gr [212.205.215.16]) j0GEfKZj010868; Sun, 16 Jan 2005 16:41:27 +0200 Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.13.1/8.13.1) with ESMTP id j0GEfDcX067035; Sun, 16 Jan 2005 16:41:13 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from giorgos@localhost) by gothmog.gr (8.13.1/8.13.1/Submit) id j0GEfDwX067034; Sun, 16 Jan 2005 16:41:13 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Sun, 16 Jan 2005 16:41:13 +0200 From: Giorgos Keramidas To: Robert Watson Message-ID: <20050116144113.GB66854@gothmog.gr> Mail-Followup-To: freebsd-current@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: cc: freebsd-current@freebsd.org Subject: Re: gratuitous gcc warnings: unused function arguments? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 14:41:34 -0000 On 2005-01-16 12:18, Robert Watson wrote: > At some point in the relatively recent past, we began to generate > warnings for unused arguments in function definitions. This is a > fairly irritating practice, as it interacts poorly with function > implementations plugged into pluggable function interfaces, such as > PAM, main(), etc. Here's an example of a particularly irritating > instance of the warning: > > static void > usage(void) > { > > fprintf(errno, "program: too many arguments\n"); > exit(-1); > } > > int > main(int argc, char *argv[]) > { > > if (argc != 1) > usage(); > > dostuff(); > } In this case, using __unused is a GCC-specific but commonly used way to specify that argv is unused and we know it's ok. There is also a more portable way to specify within the body of the function that argv is unused: % int % main(int argc, char *argv[]) % { % % (void)argv; % if (argc != 1) % usage(); % return (0); % } This allows the main() function to keep being compliant with the ANSI standard that specifies only two valid prototypes for main(): int main(void); int main(int argc, char *argv[]); But it also inhibits the warning from GCC, because argv is 'used', even though the value of the void expression is immediately thrown away. I'm not sure if this is "better" than __unused, but it works both on GCC and on the Forte C/C++ compilers of Sun that I've tried it with. - Giorgos From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 15:41:45 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADB8616A4CE; Sun, 16 Jan 2005 15:41:45 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2475B43D55; Sun, 16 Jan 2005 15:41:45 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id j0GFfiBM063212; Sun, 16 Jan 2005 10:41:44 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.1/8.13.1) with ESMTP id j0GFfihg028426; Sun, 16 Jan 2005 10:41:44 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 678057306E; Sun, 16 Jan 2005 10:41:44 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050116154144.678057306E@freebsd-current.sentex.ca> Date: Sun, 16 Jan 2005 10:41:44 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/663/Tue Jan 11 17:44:48 2005 clamav-milter version 0.80j on clamscanner3 X-Virus-Status: Clean Subject: [current tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 15:41:46 -0000 TB --- 2005-01-16 13:55:59 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-01-16 13:55:59 - starting CURRENT tinderbox run for ia64/ia64 TB --- 2005-01-16 13:55:59 - checking out the source tree TB --- 2005-01-16 13:55:59 - cd /home/tinderbox/CURRENT/ia64/ia64 TB --- 2005-01-16 13:55:59 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-01-16 14:01:34 - building world (CFLAGS=-O2 -pipe) TB --- 2005-01-16 14:01:34 - cd /home/tinderbox/CURRENT/ia64/ia64/src TB --- 2005-01-16 14:01:34 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-01-16 15:32:20 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-01-16 15:32:20 - cd /home/tinderbox/CURRENT/ia64/ia64/src TB --- 2005-01-16 15:32:20 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sun Jan 16 15:32:20 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c: In function `bus_dmamap_load_uio': /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c:784: warning: passing arg 1 of `_bus_dmamap_load_buffer' from incompatible pointer type /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c:784: warning: passing arg 2 of `_bus_dmamap_load_buffer' makes integer from pointer without a cast /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c:784: error: too many arguments to function `_bus_dmamap_load_buffer' /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c: In function `_bus_dmamap_load_buffer': /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c:496: error: prior parameter's size depends on 'map' /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c:496: error: prior parameter's size depends on 'map' /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c:514: confused by earlier errors, bailing out *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/obj/ia64/tinderbox/CURRENT/ia64/ia64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src. TB --- 2005-01-16 15:41:44 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-01-16 15:41:44 - ERROR: failed to build generic kernel TB --- 2005-01-16 15:41:44 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 17:24:45 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E9CD16A4CE; Sun, 16 Jan 2005 17:24:45 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94F2A43D54; Sun, 16 Jan 2005 17:24:44 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.3] (pool-68-160-208-232.ny325.east.verizon.net [68.160.208.232]) by pi.codefab.com (8.12.11/8.12.11) with ESMTP id j0GHOdce043242 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 16 Jan 2005 12:24:40 -0500 (EST) Message-ID: <41EAA3CD.1000903@mac.com> Date: Sun, 16 Jan 2005 12:26:37 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: In-Reply-To: X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=1.9 required=5.5 tests=AWL,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=disabled version=3.0.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on pi.codefab.com cc: current@FreeBSD.org Subject: Re: gratuitous gcc warnings: unused function arguments? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 17:24:45 -0000 Robert Watson wrote: [ ...with regard to GCC errors like... ] > cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Wno-uninitialized -c program.c > program.c:48: warning: unused parameter 'argv' > *** Error code 1 ...and... > cc -O -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith > -Wno-uninitialized -c program.c > program.c:49: warning: 'main' takes only zero or two arguments > *** Error code 1 [ ... ] > I'm not sure what is required to disable this warning, but I'd like to see > us make it optional and not keyed to lower warning levels (such as 3). Apparently, -Wunused-parameter is now being inferred from the combination of -W and -Wall. The second error message is only generated when GCC thinks it is compiling main() (or a moral equivalent thereof), so it doesn't seem likely that that error would be generated for dummyfunction(int arg1, int arg2, char *argv). However, I'll try to offer a patch which does what you've asked for and let someone else (hopefully a GCC expert/language pedant :-) second guess whether the following is a good idea: --- contrib/gcc/opts.c_orig Sun Jan 16 12:02:19 2005 +++ contrib/gcc/opts.c Sun Jan 16 12:15:23 2005 @@ -127,9 +127,6 @@ bool warn_unused_variable; bool warn_unused_value; -/* Hack for cooperation between set_Wunused and set_Wextra. */ -static bool maybe_warn_unused_parameter; - /* Type(s) of debugging information we are producing (if any). See flags.h for the definitions of the different possible types of debugging information. */ @@ -1559,7 +1556,6 @@ { extra_warnings = setting; warn_unused_value = setting; - warn_unused_parameter = (setting && maybe_warn_unused_parameter); /* We save the value of warn_uninitialized, since if they put -Wuninitialized on the command line, we need to generate a @@ -1576,13 +1572,7 @@ { warn_unused_function = setting; warn_unused_label = setting; - /* Unused function parameter warnings are reported when either - ``-Wextra -Wunused'' or ``-Wunused-parameter'' is specified. - Thus, if -Wextra has already been seen, set warn_unused_parameter; - otherwise set maybe_warn_extra_parameter, which will be picked up - by set_Wextra. */ - maybe_warn_unused_parameter = setting; - warn_unused_parameter = (setting && extra_warnings); + warn_unused_parameter = setting; warn_unused_variable = setting; warn_unused_value = setting; } --- contrib/gcc/c-decl.c_orig Sun Jan 16 11:39:32 2005 +++ contrib/gcc/c-decl.c Sun Jan 16 11:59:11 2005 @@ -5602,8 +5602,8 @@ /* It is intentional that this message does not mention the third argument because it's only mentioned in an appendix of the standard. */ - if (argct > 0 && (argct < 2 || argct > 3)) - pedwarn ("%J'%D' takes only zero or two arguments", decl1, decl1); + if (argct && (argct != 2)) + warning ("%J'%D' takes only zero or two arguments", decl1, decl1); if (! TREE_PUBLIC (decl1)) pedwarn ("%J'%D' is normally a non-static function", decl1, decl1); [ This was made on 5.3-STABLE. ] -- -Chuck From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 18:44:14 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8A1F16A4CE; Sun, 16 Jan 2005 18:44:14 +0000 (GMT) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 764BB43D1F; Sun, 16 Jan 2005 18:44:14 +0000 (GMT) (envelope-from kientzle@freebsd.org) Received: from freebsd.org (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id j0GIiEOZ042511; Sun, 16 Jan 2005 10:44:14 -0800 (PST) (envelope-from kientzle@freebsd.org) Message-ID: <41EAB5FE.30603@freebsd.org> Date: Sun, 16 Jan 2005 10:44:14 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Giorgos Keramidas References: <20050116144113.GB66854@gothmog.gr> In-Reply-To: <20050116144113.GB66854@gothmog.gr> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: Robert Watson Subject: Re: gratuitous gcc warnings: unused function arguments? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 18:44:15 -0000 Robert Watson complained that: > >>At some point in the relatively recent past, we began to generate >>warnings for unused arguments in function definitions. .... >> >>int >>main(int argc, char *argv[]) >>{ >> >> if (argc != 1)ut >> usage(); >> >> dostuff(); >>} Giorgos Keramidas suggested: > > % (void)argv; I first saw this idiom for marking unused arguments over 10 years ago and have used it extensively since then. Very portable; highly recommended. Tim From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 19:37:59 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F8A216A4CE for ; Sun, 16 Jan 2005 19:37:59 +0000 (GMT) Received: from saltmine.radix.net (saltmine.radix.net [207.192.128.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F28F43D1D for ; Sun, 16 Jan 2005 19:37:59 +0000 (GMT) (envelope-from dickey@saltmine.radix.net) Received: from saltmine.radix.net (localhost [127.0.0.1]) by saltmine.radix.net (8.12.2/8.12.2) with ESMTP id j0GJbvNb011237 for ; Sun, 16 Jan 2005 14:37:58 -0500 (EST) Received: (from dickey@localhost) by saltmine.radix.net (8.12.2/8.12.2/Submit) id j0GJbvi1011235 for freebsd-current@freebsd.org; Sun, 16 Jan 2005 14:37:57 -0500 (EST) Date: Sun, 16 Jan 2005 14:37:57 -0500 From: Thomas Dickey To: freebsd-current@freebsd.org Message-ID: <20050116193757.GA10974@saltmine.radix.net> References: <20050116144113.GB66854@gothmog.gr> <41EAB5FE.30603@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41EAB5FE.30603@freebsd.org> User-Agent: Mutt/1.3.27i Subject: Re: gratuitous gcc warnings: unused function arguments? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 19:37:59 -0000 On Sun, Jan 16, 2005 at 10:44:14AM -0800, Tim Kientzle wrote: > Giorgos Keramidas suggested: > > > >% (void)argv; > > I first saw this idiom for marking unused > arguments over 10 years ago and have used > it extensively since then. Very portable; > highly recommended. except of course for the compilers that warn about no effect... -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 19:47:49 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8496216A4CF for ; Sun, 16 Jan 2005 19:47:49 +0000 (GMT) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 440FD43D48 for ; Sun, 16 Jan 2005 19:47:49 +0000 (GMT) (envelope-from kientzle@freebsd.org) Received: from freebsd.org (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id j0GJlmOZ042813; Sun, 16 Jan 2005 11:47:49 -0800 (PST) (envelope-from kientzle@freebsd.org) Message-ID: <41EAC4E4.5020809@freebsd.org> Date: Sun, 16 Jan 2005 11:47:48 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Thomas Dickey References: <20050116144113.GB66854@gothmog.gr> <41EAB5FE.30603@freebsd.org> <20050116193757.GA10974@saltmine.radix.net> In-Reply-To: <20050116193757.GA10974@saltmine.radix.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: gratuitous gcc warnings: unused function arguments? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 19:47:49 -0000 Thomas Dickey wrote: > On Sun, Jan 16, 2005 at 10:44:14AM -0800, Tim Kientzle wrote: > >>Giorgos Keramidas suggested: >> >>>% (void)argv; >> >>I first saw this idiom for marking unused >>arguments over 10 years ago and have used >>it extensively since then. Very portable; >>highly recommended. > > > except of course for the compilers that warn about no effect... I've not seen that issue with this particular idiom. The compilers I've seen seem to recognize this as a special case. No doubt there are exceptions. Tim From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 20:46:16 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D9DB16A4CE for ; Sun, 16 Jan 2005 20:46:16 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id B61E643D2F for ; Sun, 16 Jan 2005 20:46:15 +0000 (GMT) (envelope-from avleeuwen@gmail.com) Received: by rproxy.gmail.com with SMTP id 34so709969rns for ; Sun, 16 Jan 2005 12:46:15 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=EQgHCRGeivapQmTOpkRmn/dEr302GaLpz9sfi1RIT0s4LcaS9eJoCVMAkXLb19yyRNDMZhQ+L08ZWn3eUJoc3PQ38u6ox3mZHKkCe+RnwtCpQOLK2FNgDIT36/5057q3d16MOL3F+8Wc5etvuARQDQ1PcTZqixYzT7U3RbRWoeE= Received: by 10.38.206.10 with SMTP id d10mr13266rng; Sun, 16 Jan 2005 12:46:15 -0800 (PST) Received: by 10.38.206.16 with HTTP; Sun, 16 Jan 2005 12:46:15 -0800 (PST) Message-ID: Date: Sun, 16 Jan 2005 21:46:15 +0100 From: Arjan Van Leeuwen To: John Baldwin In-Reply-To: <200501141546.31386.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200501141546.31386.jhb@FreeBSD.org> cc: current@freebsd.org Subject: Re: [PATCH] Use local APIC timer to drive kernel clocks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Arjan Van Leeuwen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 20:46:16 -0000 On Fri, 14 Jan 2005 15:46:31 -0500, John Baldwin wrote: > I have a patch that uses the local APIC timer to drive the kernel clocks > (hardclock, statclock, and profclock) instead of the ISA timer and RTC. The > advantage of this change is that SMP machines can stop using IPIs to bounce > clock interrupts around all the time. Currently the code will always use the > local APIC timer if an APIC is being used, but it might be desirable to only > use the timer if we have more than one CPU. Some caveats and details: > (...) > > Please test and let me know if there are any regressions. Thanks. Patch is > at http://www.FreeBSD.org/~jhb/patches/lapic_timer.patch Yes! My SMP system had a big problem with the clock (it did 500Hz when it should do 1000Hz, 50Hz when it should do 100Hz, etc...) that caused all kinds of weird problems and miscalculations. This patch fixes it! Thanks, Arjan > > -- > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve" = http://www.FreeBSD.org > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 20:49:51 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CF5B16A4CE; Sun, 16 Jan 2005 20:49:51 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3872143D45; Sun, 16 Jan 2005 20:49:51 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id j0GKnnlW053683; Sun, 16 Jan 2005 12:49:49 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j0GKnnTv053682; Sun, 16 Jan 2005 12:49:49 -0800 (PST) (envelope-from obrien) Date: Sun, 16 Jan 2005 12:49:49 -0800 From: "David O'Brien" To: Chuck Swiger Message-ID: <20050116204949.GA53539@dragon.nuxi.com> References: <41EAA3CD.1000903@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41EAA3CD.1000903@mac.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-current@FreeBSD.org cc: Robert Watson Subject: Re: gratuitous gcc warnings: unused function arguments? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 20:49:51 -0000 On Sun, Jan 16, 2005 at 12:26:37PM -0500, Chuck Swiger wrote: > >program.c:49: warning: 'main' takes only zero or two arguments > >*** Error code 1 > [ ... ] > >I'm not sure what is required to disable this warning, but I'd like to see > >us make it optional and not keyed to lower warning levels (such as 3). > > Apparently, -Wunused-parameter is now being inferred from the combination > of -W and -Wall. The second error message is only generated when GCC > thinks it is compiling main() (or a moral equivalent thereof), so it > doesn't seem likely that that error would be generated for > dummyfunction(int arg1, int arg2, char *argv). > > However, I'll try to offer a patch which does what you've asked for and let > someone else (hopefully a GCC expert/language pedant :-) second guess > whether the following is a good idea: We're not going to hack GCC to deal with this. That is going way too far. This is coming up because people are using high WARNS values in Makefiles. Either back them down to a lower WARNS value; or we should add -Wno-unused-parameter to WARNS level 3. -- -- David (obrien@FreeBSD.org) From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 21:05:03 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CBAF916A4CE; Sun, 16 Jan 2005 21:05:03 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A05C43D4C; Sun, 16 Jan 2005 21:05:03 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id j0GL51Rc087237; Sun, 16 Jan 2005 16:05:01 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)j0GL51A2087234; Sun, 16 Jan 2005 21:05:01 GMT (envelope-from robert@fledge.watson.org) Date: Sun, 16 Jan 2005 21:05:01 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "David O'Brien" In-Reply-To: <20050116204949.GA53539@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@FreeBSD.org Subject: Re: gratuitous gcc warnings: unused function arguments? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 21:05:04 -0000 On Sun, 16 Jan 2005, David O'Brien wrote: > We're not going to hack GCC to deal with this. That is going way too > far. This is coming up because people are using high WARNS values in > Makefiles. Either back them down to a lower WARNS value; or we should > add -Wno-unused-parameter to WARNS level 3. I'd be fine with simply pushing threshold for unused parameters up a few notches on the warning scale. I'd like to have access to the other interesting warnings are WARNS=3 and WARNS=4 relating to qualifiers, strings, etc. Robert N M Watson From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 21:14:24 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B67316A4CE; Sun, 16 Jan 2005 21:14:24 +0000 (GMT) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id E22E343D39; Sun, 16 Jan 2005 21:14:23 +0000 (GMT) (envelope-from alc@cs.rice.edu) Received: from localhost (calypso.cs.rice.edu [128.42.1.127]) by cs.rice.edu (Postfix) with ESMTP id 4CE0C4A9B0; Sun, 16 Jan 2005 15:14:23 -0600 (CST) Received: from cs.rice.edu ([128.42.1.30]) by localhost (calypso.cs.rice.edu [128.42.1.127]) (amavisd-new, port 10024) with LMTP id 00776-01-31; Sun, 16 Jan 2005 15:14:22 -0600 (CST) Received: from noel.cs.rice.edu (noel.cs.rice.edu [128.42.1.136]) by cs.rice.edu (Postfix) with ESMTP id B28F04A9AD; Sun, 16 Jan 2005 15:14:22 -0600 (CST) Received: (from alc@localhost) by noel.cs.rice.edu (8.12.10+Sun/8.12.9/Submit) id j0GLDnQs003183; Sun, 16 Jan 2005 15:13:49 -0600 (CST) Date: Sun, 16 Jan 2005 15:13:49 -0600 From: Alan Cox To: Kris Kennaway Message-ID: <20050116211349.GG26214@noel.cs.rice.edu> References: <20050115083847.GA47466@xor.obsecurity.org> <20050116003432.GA448@xor.obsecurity.org> <20050116050433.GA65733@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050116050433.GA65733@xor.obsecurity.org> User-Agent: Mutt/1.3.28i X-Virus-Scanned: by amavis-20030616-p7 at cs.rice.edu cc: alc@freebsd.org cc: current@freebsd.org Subject: Re: fstat triggered INVARIANTS panic in memrw() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 21:14:24 -0000 On Sat, Jan 15, 2005 at 09:04:33PM -0800, Kris Kennaway wrote: > On Sat, Jan 15, 2005 at 04:34:32PM -0800, Kris Kennaway wrote: > > > > generic_copyout(deadc0de,7ab7037c,eed96c84,54,5964d000) at generic_copyout+0x36 > > > > (kgdb) l *memrw+0x36 > > 0xc06e3486 is in memrw (../../../i386/i386/mem.c:128). > > 123 > > 124 if (!kernacc((caddr_t)(int)uio->uio_offset, c, > > 125 uio->uio_rw == UIO_READ ? > > 126 VM_PROT_READ : VM_PROT_WRITE)) > > 127 return (EFAULT); > > 128 error = uiomove((caddr_t)(int)uio->uio_offset, (int)c, uio); > > 129 continue; > > 130 } > > 131 /* else panic! */ > > 132 } > > > > > memrw(c34fad00,eed96c84,0,398,7ab7037c) at memrw+0x18a > > > devfs_read_f(c51773b8,eed96c84,ca75c800,0,c9ec1780) at devfs_read_f+0x142 > > > dofileread(4,804f000,7ab7037c,ffffffff,ffffffff) at dofileread+0x92 > > > read(c9ec1780,eed96d14,c,3ff,3) at read+0x75 > > > syscall(2f,2f,2f,7ab7037c,80b1078) at syscall+0x137 > > > Xint0x80_syscall() at Xint0x80_syscall+0x1f > > > --- syscall (3, FreeBSD ELF32, read), eip = 0x280d347f, esp = 0xbfbfe34c, ebp = 0xbfbfe378 --- > > > > > > Note the deadc0de in generic_copyout(). > > BTW, this is now wreaking havoc with my ability to finish building > packages for 4.11-RELEASE (together with the softupdates panic also > being reported), so anything someone can do to track this down is > appreciated. > The "deadc0de" passed to generic_copyout() comes from the following lines in devfs_read_f(c51773b8,eed96c84,ca75c800,flags=0): if ((flags & FOF_OFFSET) == 0) uio->uio_offset = fp->f_offset; Can you print the contents of the file structure? Alan From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 21:33:17 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC34F16A4CF for ; Sun, 16 Jan 2005 21:33:17 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75DE843D46 for ; Sun, 16 Jan 2005 21:33:17 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from error404.nls.net (ketrien@error404.nls.net [216.144.36.24]) by error404.nls.net (8.13.1/8.13.1) with ESMTP id j0GLb2Y0037077 for ; Sun, 16 Jan 2005 16:37:02 -0500 (EST) (envelope-from ketrien@error404.nls.net) Date: Sun, 16 Jan 2005 16:37:02 -0500 (EST) From: "Ketrien I. Saihr-Kenchedra" X-X-Sender: ketrien@bahre.achedra.org To: current@freebsd.org In-Reply-To: <20050116044737.B13189@bahre.achedra.org> Message-ID: <20050116163107.R13189@bahre.achedra.org> References: <20050116044737.B13189@bahre.achedra.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV 0.80/631/Wed Dec 15 09:01:14 2004 clamav-milter version 0.80j on bahre.achedra.org X-Virus-Status: Clean Subject: Re: LOR in Jan16 -CUR, ACPI related possibly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 21:33:18 -0000 Yes yes, bad form to reply to myself, I know. Managed to salvage the LOR from logs. (Filesystems were an unholy mess.) ukphy0: detached miibus0: detached lock order reversal 1st 0xc1f3a790 pcn0 (network driver) @ /usr/src/sys/modules/pcn/../../pci/if_pcn.c:1385 2nd 0xc08b02c0 ACPI root bus (ACPI root bus) @ /usr/src/sys/modules/acpi/acpi/../../../dev/acpica/acpi.c:1050 KDB: stack backtrace: witness_checkorder(c08b02c0,9,c08aa6b7,41a,c0700795) at witness_checkorder+0x5c6 _sx_xlock(c08b02c0,c08aa6b7,41a,1,c1c59380) at _sx_xlock+0x5d acpi_release_resource(c1c58600,c1c59380,1,0,c1d13a00) at acpi_release_resource+0x30 resource_list_release(c1c59a84,c1ccf100,c1c59380,1,0,c1d13a00) at resource_list_release+0x125 bus_generic_rl_release_resource(c1ccf100,c1c59380,1,0,c1d13a00) at bus_generic_rl_release_resource+0x7b bus_release_resource(c1c59380,1,0,c1d13a00,c1c59380) at bus_release_resource+0x6b pcn_detach(c1c59380,c1cb2850,c073606c,933,c3e5b9f0) at pcn_detach+0x17b device_detach(c1c59380,c3e5a759,c1e79540,1,c1c1fa00) at device_detach+0x99 devclass_delete_driver(c1c1fa00,c3e5b9f0,1f2,0,c212db80) at devclass_delete_driver+0xd1 driver_module_handler(c212db80,1,c3e5b9dc) at driver_module_handler+0xe2 module_unload(c212db80,0,1f2,c21a5400,c07001e5) at module_unload+0x68 linker_file_unload(c21a5400,0,c07001ee,31e,bfbfe8a0) at linker_file_unload+0x29d kern_kldunload(0,db2f7d14,8,3ff,2) at kern_kldunload+0x8c syscall(2f,2f,2f,3,bfbfee16) at syscall+0x137 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (444, FreeBSD ELF32, kldunloadf), eip = 0x280c459f, esp = 0xbfbfe89c, ebp = 0xbfbfed10 --- pcn0: detached -ksaihr From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 21:44:06 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1623616A4CE for ; Sun, 16 Jan 2005 21:44:06 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id B22E543D5D for ; Sun, 16 Jan 2005 21:44:05 +0000 (GMT) (envelope-from chiahsing@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so675300wri for ; Sun, 16 Jan 2005 13:44:05 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=FmuZbAERh6CNCOt0ffp4KCNwQaSsjVaDDEkP6BfncoNEUeI9cz1u8wn2biS3qfX+u1xpSIKaI1WuzMLoRPwIeDKoFSQ7Ki0nBqnKcuGkEfFG9Q3CNkz1mn711mkKqvNkHr1D/wfWrChV2XX0bnO6HlbHQXVjMlcSuXHoi/1vMnU= Received: by 10.54.32.35 with SMTP id f35mr156378wrf; Sun, 16 Jan 2005 13:44:04 -0800 (PST) Received: by 10.54.31.21 with HTTP; Sun, 16 Jan 2005 13:44:04 -0800 (PST) Message-ID: Date: Sun, 16 Jan 2005 13:44:04 -0800 From: David Yu To: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: NTFS unicode converting problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Yu List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 21:44:06 -0000 Hi, it seems that NTFS in FreeBSD uses a 16-bit long wchar to store filename. When I wanted to convert some Chinese filename into UTF-8, the conversion was failed because a single Chinese character needs 3 bytes in UTF-8. Is anyone already working on this problem? If not, I would like to do something about it. Any suggestions? David From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 21:50:34 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A61916A4CE for ; Sun, 16 Jan 2005 21:50:34 +0000 (GMT) Received: from alpha.bprarchitects.com (punt-1.bprarchitects.com [62.49.190.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id F312243D41 for ; Sun, 16 Jan 2005 21:50:32 +0000 (GMT) (envelope-from cam@macaroon.net) Received: from alpha.bprarchitects.com (alpha [192.168.1.1]) j0GLoRo0040181 for ; Sun, 16 Jan 2005 21:50:28 GMT (envelope-from cam@macaroon.net) Received: from hawksmoor.bprarchitects.com ([192.168.1.174]) by alpha (MailMonitor for SMTP v1.2.2 ) ; Sun, 16 Jan 2005 21:50:27 +0000 (GMT) Message-ID: <41EAE1A2.4010308@macaroon.net> Date: Sun, 16 Jan 2005 21:50:26 +0000 From: Cameron Murdoch User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_10,UPPERCASE_25_50 autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on alpha.bprarchitects.com Subject: Adaptec 39320A "Card was not paused" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 21:50:34 -0000 I am having a problem with an adaptec 39320A SCSI card accessing an external raid box, (JetStor III 416S). Host computer is a Dell PowerEdge2650 with a single processor. 6-CURRENT from Saturday has the following relevant dmesg: **snip** Jan 16 21:13:35 kernel: ahd0: port 0xd800-0xd8ff,0xdc00-0xdcff mem 0xfcf02000-0xfcf03fff irq 20 at device 8.0 on pci1 Jan 16 21:13:35 kernel: ahd0: [GIANT-LOCKED] Jan 16 21:13:35 kernel: aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 101-133Mhz, 512 SCBs Jan 16 21:13:35 kernel: ahd1: port 0xd000-0xd0ff,0xd400-0xd4ff mem 0xfcf00000-0xfcf01fff irq 21 at device 8.1 on pci1 Jan 16 21:13:35 kernel: ahd1: [GIANT-LOCKED] Jan 16 21:13:35 kernel: aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI-X 101-133Mhz, 512 SCBs **snip** Jan 16 21:13:35 kernel: da0 at ahd0 bus 0 target 0 lun 0 Jan 16 21:13:35 kernel: da0: Fixed Direct Access SCSI-3 device Jan 16 21:13:35 kernel: da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit), Tagged Queueing Enabled Jan 16 21:13:35 kernel: da0: 1192092MB (2441405440 512 byte sectors: 255H 63S/T 151970C) Attempts to newfs a bsdlabeled slice results in the following errors: Jan 16 21:20:21 kernel: ahd0: Recovery Initiated - Card was not paused Jan 16 21:20:21 kernel: >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< Jan 16 21:20:21 kernel: ahd0: Dumping Card State at program address 0x81 Mode 0x22 Jan 16 21:20:21 kernel: INTSTAT[0x0] SELOID[0x0] SELID[0x0] HS_MAILBOX[0x0] Jan 16 21:20:21 kernel: INTCTL[0x80]:(SWTMINTMASK) SEQINTSTAT[0x0] SAVED_MODE[0x11] Jan 16 21:20:21 kernel: DFFSTAT[0x33]:(CURRFIFO_NONE|FIFO0FREE|FIFO1FREE) Jan 16 21:20:21 kernel: SCSISIGI[0x25]:(P_DATAOUT_DT|ACKI|BSYI) SCSIPHASE[0x0] Jan 16 21:20:21 kernel: SCSIBUS[0x0] LASTPHASE[0x1]:(P_DATAOUT|P_BUSFREE) Jan 16 21:20:21 kernel: SCSISEQ0[0x40]:(ENSELO) SCSISEQ1[0x12]:(ENAUTOATNP|ENRSELI) Jan 16 21:20:21 kernel: SEQCTL0[0x0] SEQINTCTL[0x0] SEQ_FLAGS[0x0] SEQ_FLAGS2[0x0] Jan 16 21:20:21 kernel: QFREEZE_COUNT[0x0] KERNEL_QFREEZE_COUNT[0x0] MK_MESSAGE_SCB[0xff00] Jan 16 21:20:21 kernel: MK_MESSAGE_SCSIID[0xff] SSTAT0[0x10]:(SELINGO) SSTAT1[0x8]:(BUSFREE) Jan 16 21:20:21 kernel: SSTAT2[0x0] SSTAT3[0x0] PERRDIAG[0xc0]:(HIPERR|HIZERO) Jan 16 21:20:21 kernel: SIMODE1[0xa4]:(ENSCSIPERR|ENSCSIRST|ENSELTIMO) LQISTAT0[0x0] Jan 16 21:20:21 kernel: LQISTAT1[0x0] LQISTAT2[0x80]:(PACKETIZED) LQOSTAT0[0x0] Jan 16 21:20:21 kernel: LQOSTAT1[0x0] LQOSTAT2[0x40] **snip (lots of debugging output)** The same thing occurs in both 5.3 RELEASE and 6-CURRENT. Newfs will actually finish though it takes a while, however, attempts to write to the resulting filesystem produce the same debugging output as above. Is this a bug or is there something I need to turn off, etc? I can provide the full output to anybody who is interested. Cameron Murdoch From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 21:53:30 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 729A716A4CE for ; Sun, 16 Jan 2005 21:53:30 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C234B43D2D for ; Sun, 16 Jan 2005 21:53:29 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.12] (g4.samsco.home [192.168.254.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id j0GLvV1L017114; Sun, 16 Jan 2005 14:57:31 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41EAE255.6080203@freebsd.org> Date: Sun, 16 Jan 2005 14:53:25 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Cameron Murdoch References: <41EAE1A2.4010308@macaroon.net> In-Reply-To: <41EAE1A2.4010308@macaroon.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.3 required=3.8 tests=UPPERCASE_25_50 autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: current@freebsd.org Subject: Re: Adaptec 39320A "Card was not paused" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 21:53:30 -0000 Cameron Murdoch wrote: > I am having a problem with an adaptec 39320A SCSI card accessing an > external raid box, (JetStor III 416S). > > Host computer is a Dell PowerEdge2650 with a single processor. > > 6-CURRENT from Saturday has the following relevant dmesg: > > **snip** > Jan 16 21:13:35 kernel: ahd0: > port 0xd800-0xd8ff,0xdc00-0xdcff mem 0xfcf02000-0xfcf03fff irq 20 at > device 8.0 on pci1 > Jan 16 21:13:35 kernel: ahd0: [GIANT-LOCKED] > Jan 16 21:13:35 kernel: aic7902: Ultra320 Wide Channel A, SCSI Id=7, > PCI-X 101-133Mhz, 512 SCBs > Jan 16 21:13:35 kernel: ahd1: > port 0xd000-0xd0ff,0xd400-0xd4ff mem 0xfcf00000-0xfcf01fff irq 21 at > device 8.1 on pci1 > Jan 16 21:13:35 kernel: ahd1: [GIANT-LOCKED] > Jan 16 21:13:35 kernel: aic7902: Ultra320 Wide Channel B, SCSI Id=7, > PCI-X 101-133Mhz, 512 SCBs > **snip** > Jan 16 21:13:35 kernel: da0 at ahd0 bus 0 target 0 lun 0 > Jan 16 21:13:35 kernel: da0: Fixed > Direct Access SCSI-3 device > Jan 16 21:13:35 kernel: da0: 320.000MB/s transfers (160.000MHz, offset > 127, 16bit), Tagged Queueing Enabled > Jan 16 21:13:35 kernel: da0: 1192092MB (2441405440 512 byte sectors: > 255H 63S/T 151970C) > > Attempts to newfs a bsdlabeled slice results in the following errors: > > Jan 16 21:20:21 kernel: ahd0: Recovery Initiated - Card was not paused > Jan 16 21:20:21 kernel: >>>>>>>>>>>>>>>>>> Dump Card State Begins > <<<<<<<<<<<<<<<<< > Jan 16 21:20:21 kernel: ahd0: Dumping Card State at program address > 0x81 Mode 0x22 > Jan 16 21:20:21 kernel: INTSTAT[0x0] SELOID[0x0] SELID[0x0] > HS_MAILBOX[0x0] > Jan 16 21:20:21 kernel: INTCTL[0x80]:(SWTMINTMASK) SEQINTSTAT[0x0] > SAVED_MODE[0x11] > Jan 16 21:20:21 kernel: DFFSTAT[0x33]:(CURRFIFO_NONE|FIFO0FREE|FIFO1FREE) > Jan 16 21:20:21 kernel: SCSISIGI[0x25]:(P_DATAOUT_DT|ACKI|BSYI) > SCSIPHASE[0x0] > Jan 16 21:20:21 kernel: SCSIBUS[0x0] LASTPHASE[0x1]:(P_DATAOUT|P_BUSFREE) > Jan 16 21:20:21 kernel: SCSISEQ0[0x40]:(ENSELO) > SCSISEQ1[0x12]:(ENAUTOATNP|ENRSELI) > Jan 16 21:20:21 kernel: SEQCTL0[0x0] SEQINTCTL[0x0] SEQ_FLAGS[0x0] > SEQ_FLAGS2[0x0] > Jan 16 21:20:21 kernel: QFREEZE_COUNT[0x0] KERNEL_QFREEZE_COUNT[0x0] > MK_MESSAGE_SCB[0xff00] > Jan 16 21:20:21 kernel: MK_MESSAGE_SCSIID[0xff] SSTAT0[0x10]:(SELINGO) > SSTAT1[0x8]:(BUSFREE) > Jan 16 21:20:21 kernel: SSTAT2[0x0] SSTAT3[0x0] > PERRDIAG[0xc0]:(HIPERR|HIZERO) > Jan 16 21:20:21 kernel: SIMODE1[0xa4]:(ENSCSIPERR|ENSCSIRST|ENSELTIMO) > LQISTAT0[0x0] > Jan 16 21:20:21 kernel: LQISTAT1[0x0] LQISTAT2[0x80]:(PACKETIZED) > LQOSTAT0[0x0] > Jan 16 21:20:21 kernel: LQOSTAT1[0x0] LQOSTAT2[0x40] > **snip (lots of debugging output)** You snipped off the output that was important. Send a complete log, please. Scott From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 22:12:03 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 61AB616A4CE; Sun, 16 Jan 2005 22:12:03 +0000 (GMT) Received: from alpha.bprarchitects.com (punt-1.bprarchitects.com [62.49.190.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6480443D3F; Sun, 16 Jan 2005 22:12:02 +0000 (GMT) (envelope-from cam@macaroon.net) Received: from alpha.bprarchitects.com (alpha [192.168.1.1]) j0GMBto0040215; Sun, 16 Jan 2005 22:11:56 GMT (envelope-from cam@macaroon.net) Received: from hawksmoor.bprarchitects.com ([192.168.1.174]) by alpha (MailMonitor for SMTP v1.2.2 ) ; Sun, 16 Jan 2005 22:11:55 +0000 (GMT) Message-ID: <41EAE6AB.9040407@macaroon.net> Date: Sun, 16 Jan 2005 22:11:55 +0000 From: Cameron Murdoch User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <41EAE1A2.4010308@macaroon.net> <41EAE255.6080203@freebsd.org> In-Reply-To: <41EAE255.6080203@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-4.7 required=5.0 tests=AWL,BAYES_00,UPPERCASE_25_50 autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on alpha.bprarchitects.com cc: current@freebsd.org Subject: Re: Adaptec 39320A "Card was not paused" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 22:12:03 -0000 Scott Long wrote: > Cameron Murdoch wrote: > >> I am having a problem with an adaptec 39320A SCSI card accessing an >> external raid box, (JetStor III 416S). >> >> Host computer is a Dell PowerEdge2650 with a single processor. >> >> 6-CURRENT from Saturday has the following relevant dmesg: >> >> **snip** > > > You snipped off the output that was important. Send a complete log, > please. > > > Scott Apologies, here is a more complete error message: Jan 16 21:20:21 kernel: ahd0: Recovery Initiated - Card was not paused Jan 16 21:20:21 kernel: >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< Jan 16 21:20:21 kernel: ahd0: Dumping Card State at program address 0x81 Mode 0x22 Jan 16 21:20:21 kernel: INTSTAT[0x0] SELOID[0x0] SELID[0x0] HS_MAILBOX[0x0] Jan 16 21:20:21 kernel: INTCTL[0x80]:(SWTMINTMASK) SEQINTSTAT[0x0] SAVED_MODE[0x11] Jan 16 21:20:21 kernel: DFFSTAT[0x33]:(CURRFIFO_NONE|FIFO0FREE|FIFO1FREE) Jan 16 21:20:21 kernel: SCSISIGI[0x25]:(P_DATAOUT_DT|ACKI|BSYI) SCSIPHASE[0x0] Jan 16 21:20:21 kernel: SCSIBUS[0x0] LASTPHASE[0x1]:(P_DATAOUT|P_BUSFREE) Jan 16 21:20:21 kernel: SCSISEQ0[0x40]:(ENSELO) SCSISEQ1[0x12]:(ENAUTOATNP|ENRSELI) Jan 16 21:20:21 kernel: SEQCTL0[0x0] SEQINTCTL[0x0] SEQ_FLAGS[0x0] SEQ_FLAGS2[0x0] Jan 16 21:20:21 kernel: QFREEZE_COUNT[0x0] KERNEL_QFREEZE_COUNT[0x0] MK_MESSAGE_SCB[0xff00] Jan 16 21:20:21 kernel: MK_MESSAGE_SCSIID[0xff] SSTAT0[0x10]:(SELINGO) SSTAT1[0x8]:(BUSFREE) Jan 16 21:20:21 kernel: SSTAT2[0x0] SSTAT3[0x0] PERRDIAG[0xc0]:(HIPERR|HIZERO) Jan 16 21:20:21 kernel: SIMODE1[0xa4]:(ENSCSIPERR|ENSCSIRST|ENSELTIMO) LQISTAT0[0x0] Jan 16 21:20:21 kernel: LQISTAT1[0x0] LQISTAT2[0x80]:(PACKETIZED) LQOSTAT0[0x0] Jan 16 21:20:21 kernel: LQOSTAT1[0x0] LQOSTAT2[0x40] Jan 16 21:20:21 kernel: Jan 16 21:20:21 kernel: SCB Count = 16 CMDS_PENDING = 1 LASTSCB 0xffff CURRSCB 0xf NEXTSCB 0xff00 Jan 16 21:20:21 kernel: qinstart = 342 qinfifonext = 342 Jan 16 21:20:21 kernel: QINFIFO: Jan 16 21:20:21 kernel: WAITING_TID_QUEUES: Jan 16 21:20:21 kernel: 0 ( 0xf ) Jan 16 21:20:21 kernel: Pending list: Jan 16 21:20:21 kernel: 15 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x7] Jan 16 21:20:21 kernel: Total 1 Jan 16 21:20:21 kernel: Kernel Free SCB list: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 0 Jan 16 21:20:21 kernel: Sequencer Complete DMA-inprog list: Jan 16 21:20:21 kernel: Sequencer Complete list: Jan 16 21:20:21 kernel: Sequencer DMA-Up and Complete list: Jan 16 21:20:21 kernel: Sequencer On QFreeze and Complete list: Jan 16 21:20:21 kernel: Jan 16 21:20:21 kernel: Jan 16 21:20:21 kernel: ahd0: FIFO0 Free, LONGJMP == 0x8276, SCB 0xf Jan 16 21:20:21 kernel: SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS) Jan 16 21:20:21 kernel: SEQINTSRC[0x0] DFCNTRL[0x4]:(DIRECTION) DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) Jan 16 21:20:21 kernel: SG_CACHE_SHADOW[0x2]:(LAST_SEG) SG_STATE[0x0] DFFSXFRCTL[0x0] Jan 16 21:20:21 kernel: SOFFCNT[0x0] MDFFSTAT[0x5]:(FIFOFREE|DLZERO) SHADDR = 0x00, SHCNT = 0x0 Jan 16 21:20:21 kernel: HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]:(SG_CACHE_AVAIL) Jan 16 21:20:21 kernel: Jan 16 21:20:21 kernel: ahd0: FIFO1 Free, LONGJMP == 0x8063, SCB 0xf Jan 16 21:20:21 kernel: SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS) Jan 16 21:20:21 kernel: SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) Jan 16 21:20:21 kernel: SG_CACHE_SHADOW[0x2]:(LAST_SEG) SG_STATE[0x0] DFFSXFRCTL[0x0] Jan 16 21:20:21 kernel: SOFFCNT[0x0] MDFFSTAT[0x5]:(FIFOFREE|DLZERO) SHADDR = 0x00, SHCNT = 0x0 Jan 16 21:20:21 kernel: HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]:(SG_CACHE_AVAIL) Jan 16 21:20:21 kernel: LQIN: 0x8 0x0 0x0 0xf 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 Jan 16 21:20:21 kernel: ahd0: LQISTATE = 0x1, LQOSTATE = 0x1a, OPTIONMODE = 0x42 Jan 16 21:20:21 kernel: ahd0: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x0 Jan 16 21:20:21 kernel: ahd0: SAVED_SCSIID = 0x0 SAVED_LUN = 0x0 Jan 16 21:20:21 kernel: Jan 16 21:20:21 kernel: SIMODE0[0xc]:(ENOVERRUN|ENIOERR) Jan 16 21:20:21 kernel: CCSCBCTL[0x4]:(CCSCBDIR) Jan 16 21:20:21 kernel: ahd0: REG0 == 0xf, SINDEX = 0x102, DINDEX = 0x102 Jan 16 21:20:21 kernel: ahd0: SCBPTR == 0xff0f, SCB_NEXT == 0xff00, SCB_NEXT2 == 0x0 Jan 16 21:20:21 kernel: CDB f 1 0 0 0 0 Jan 16 21:20:21 kernel: STACK: 0x24 0x0 0x0 0x0 0x0 0x0 0x0 0x0 Jan 16 21:20:21 kernel: <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> Jan 16 21:20:21 kernel: (da0:ahd0:0:0:0): SCB 0xf - timed out Jan 16 21:20:21 kernel: (da0:ahd0:0:0:0): BDR message in message buffer Jan 16 21:20:23 kernel: ahd0: Recovery Initiated - Card was not paused Jan 16 21:20:23 kernel: >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< Jan 16 21:20:23 kernel: ahd0: Dumping Card State at program address 0x23 Mode 0x11 Jan 16 21:20:23 kernel: INTSTAT[0x0] SELOID[0x0] SELID[0x0] HS_MAILBOX[0x0] Jan 16 21:20:23 kernel: INTCTL[0x80]:(SWTMINTMASK) SEQINTSTAT[0x0] SAVED_MODE[0x11] Jan 16 21:20:23 kernel: DFFSTAT[0x33]:(CURRFIFO_NONE|FIFO0FREE|FIFO1FREE) Jan 16 21:20:23 kernel: SCSISIGI[0x35]:(P_DATAOUT_DT|ACKI|BSYI|ATNI) SCSIPHASE[0x0] Jan 16 21:20:23 kernel: SCSIBUS[0x0] LASTPHASE[0x1]:(P_DATAOUT|P_BUSFREE) Jan 16 21:20:23 kernel: SCSISEQ0[0x40]:(ENSELO) SCSISEQ1[0x12]:(ENAUTOATNP|ENRSELI) Jan 16 21:20:23 kernel: SEQCTL0[0x0] SEQINTCTL[0x0] SEQ_FLAGS[0x0] SEQ_FLAGS2[0x4]:(SELECTOUT_QFROZEN) Jan 16 21:20:23 kernel: QFREEZE_COUNT[0x0] KERNEL_QFREEZE_COUNT[0x0] MK_MESSAGE_SCB[0xff00] Jan 16 21:20:23 kernel: MK_MESSAGE_SCSIID[0xff] SSTAT0[0x10]:(SELINGO) SSTAT1[0x0] Jan 16 21:20:23 kernel: SSTAT2[0x0] SSTAT3[0x0] PERRDIAG[0xc0]:(HIPERR|HIZERO) Jan 16 21:20:23 kernel: SIMODE1[0xa4]:(ENSCSIPERR|ENSCSIRST|ENSELTIMO) LQISTAT0[0x0] Jan 16 21:20:23 kernel: LQISTAT1[0x0] LQISTAT2[0x80]:(PACKETIZED) LQOSTAT0[0x0] Jan 16 21:20:23 kernel: LQOSTAT1[0x0] LQOSTAT2[0x40] Jan 16 21:20:23 kernel: Jan 16 21:20:23 kernel: SCB Count = 16 CMDS_PENDING = 1 LASTSCB 0xffff CURRSCB 0xf NEXTSCB 0xff00 Jan 16 21:20:23 kernel: qinstart = 342 qinfifonext = 342 Jan 16 21:20:23 kernel: QINFIFO: Jan 16 21:20:23 kernel: WAITING_TID_QUEUES: Jan 16 21:20:23 kernel: 0 ( 0xf ) Jan 16 21:20:23 kernel: Pending list: Jan 16 21:20:23 kernel: 15 FIFO_USE[0x0] SCB_CONTROL[0x60]:(TAG_ENB|DISCENB) SCB_SCSIID[0x7] Jan 16 21:20:23 kernel: Total 1 Jan 16 21:20:23 kernel: Kernel Free SCB list: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 0 Jan 16 21:20:23 kernel: Sequencer Complete DMA-inprog list: Jan 16 21:20:23 kernel: Sequencer Complete list: Jan 16 21:20:23 kernel: Sequencer DMA-Up and Complete list: Jan 16 21:20:23 kernel: Sequencer On QFreeze and Complete list: Jan 16 21:20:23 kernel: Jan 16 21:20:23 kernel: Jan 16 21:20:23 kernel: ahd0: FIFO0 Free, LONGJMP == 0x8276, SCB 0xf Jan 16 21:20:23 kernel: SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS) Jan 16 21:20:23 kernel: SEQINTSRC[0x0] DFCNTRL[0x4]:(DIRECTION) DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) Jan 16 21:20:23 kernel: SG_CACHE_SHADOW[0x2]:(LAST_SEG) SG_STATE[0x0] DFFSXFRCTL[0x0] Jan 16 21:20:23 kernel: SOFFCNT[0x0] MDFFSTAT[0x5]:(FIFOFREE|DLZERO) SHADDR = 0x00, SHCNT = 0x0 Jan 16 21:20:23 kernel: HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]:(SG_CACHE_AVAIL) Jan 16 21:20:23 kernel: Jan 16 21:20:23 kernel: ahd0: FIFO1 Free, LONGJMP == 0x8063, SCB 0xf Jan 16 21:20:23 kernel: SEQIMODE[0x3f]:(ENCFG4TCMD|ENCFG4ICMD|ENCFG4TSTAT|ENCFG4ISTAT|ENCFG4DATA|ENSAVEPTRS) Jan 16 21:20:23 kernel: SEQINTSRC[0x0] DFCNTRL[0x0] DFSTATUS[0x89]:(FIFOEMP|HDONE|PRELOAD_AVAIL) Jan 16 21:20:23 kernel: SG_CACHE_SHADOW[0x2]:(LAST_SEG) SG_STATE[0x0] DFFSXFRCTL[0x0] Jan 16 21:20:23 kernel: SOFFCNT[0x0] MDFFSTAT[0x5]:(FIFOFREE|DLZERO) SHADDR = 0x00, SHCNT = 0x0 Jan 16 21:20:23 kernel: HADDR = 0x00, HCNT = 0x0 CCSGCTL[0x10]:(SG_CACHE_AVAIL) Jan 16 21:20:23 kernel: LQIN: 0x8 0x0 0x0 0xf 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 Jan 16 21:20:23 kernel: ahd0: LQISTATE = 0x1, LQOSTATE = 0x1a, OPTIONMODE = 0x42 Jan 16 21:20:23 kernel: ahd0: OS_SPACE_CNT = 0x20 MAXCMDCNT = 0x0 Jan 16 21:20:23 kernel: ahd0: SAVED_SCSIID = 0x0 SAVED_LUN = 0x0 Jan 16 21:20:23 kernel: Jan 16 21:20:23 kernel: SIMODE0[0xc]:(ENOVERRUN|ENIOERR) Jan 16 21:20:23 kernel: CCSCBCTL[0x4]:(CCSCBDIR) Jan 16 21:20:23 kernel: ahd0: REG0 == 0xf, SINDEX = 0x102, DINDEX = 0x102 Jan 16 21:20:23 kernel: ahd0: SCBPTR == 0xf, SCB_NEXT == 0xff00, SCB_NEXT2 == 0xff96 Jan 16 21:20:23 kernel: CDB 2a 0 3 35 22 df Jan 16 21:20:23 kernel: STACK: 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 Jan 16 21:20:23 kernel: <<<<<<<<<<<<<<<<< Dump Card State Ends >>>>>>>>>>>>>>>>>> Jan 16 21:20:23 kernel: (da0:ahd0:0:0:0): SCB 0xf - timed out Jan 16 21:20:23 kernel: (da0:ahd0:0:0:0): no longer in timeout, status = 24b Jan 16 21:20:23 kernel: ahd0: Issued Channel A Bus Reset. 1 SCBs aborted Cameron From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 23:16:51 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DED2616A4CE; Sun, 16 Jan 2005 23:16:51 +0000 (GMT) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 636BE43D2F; Sun, 16 Jan 2005 23:16:51 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.13.0/8.13.0) with ESMTP id j0GNGoDF005411; Sun, 16 Jan 2005 18:16:50 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Sun, 16 Jan 2005 18:16:49 -0500 To: Robert Watson , current@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) Subject: Re: gratuitous gcc warnings: unused function arguments? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 23:16:52 -0000 At 12:18 PM +0000 1/16/05, Robert Watson wrote: >One of the reasons why I find __unused irritating is the >following sort of situation: > >int >dummyfunction(int arg1, int arg2, char *argv) >{ > >#ifdef DUMMY_USES_ARGV > if (argv != NULL) > printf("dummyfunction: %s\n", argv); >#endif > return (arg1 + arg2); >} > >With the new world order, we would have to ifdef the function >definition to conditionally use __unused in order to allow the >function to compile with or without the #ifdef. In this specific case, would it make sense to change the code to be: int dummyfunction(int arg1, int arg2, char *argv) { if (DUMMY_USES_ARGV && (argv != NULL)) printf("dummyfunction: %s\n", argv); return (arg1 + arg2); } ? This does mean you must always define DUMMY_USES_ARGV to be 0 or 1 (which is easy enough to do by using an #ifndef check up at the start of the file). But it does remove the warning message (at least in gcc), and in my testing it also seems to produce the same-size object-code as the #ifdef version. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 00:42:11 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 63E8F16A4CE; Mon, 17 Jan 2005 00:42:11 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 290B343D5E; Mon, 17 Jan 2005 00:42:11 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id j0H0gA68062445; Sun, 16 Jan 2005 16:42:10 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j0H0g91h062444; Sun, 16 Jan 2005 16:42:09 -0800 (PST) (envelope-from obrien) Date: Sun, 16 Jan 2005 16:42:09 -0800 From: "David O'Brien" To: Garance A Drosihn Message-ID: <20050117004209.GA62371@dragon.nuxi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-current@freebsd.org cc: Robert Watson Subject: Re: gratuitous gcc warnings: unused function arguments? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 00:42:11 -0000 On Sun, Jan 16, 2005 at 06:16:49PM -0500, Garance A Drosihn wrote: > In this specific case, would it make sense to change the code to be: > int > dummyfunction(int arg1, int arg2, char *argv) > { > > if (DUMMY_USES_ARGV && (argv != NULL)) > printf("dummyfunction: %s\n", argv); > return (arg1 + arg2); > } > > ? > > This does mean you must always define DUMMY_USES_ARGV to be 0 or 1 > (which is easy enough to do by using an #ifndef check up at the start > of the file). But it does remove the warning message (at least in gcc), > and in my testing it also seems to produce the same-size object-code > as the #ifdef version. I like this version much better. Requiring a #define symbol to be a set value isn't so bad. In fact it is a requirement in GCC'ville -- along with not using #ifdef, but rather "if(SYMBOL && )" so that all(most) code will be syntax checked an a build on arch system has less chance of breaking the build for another arch. -- -- David (obrien@FreeBSD.org) From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 00:51:38 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F6F416A4CE; Mon, 17 Jan 2005 00:51:38 +0000 (GMT) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1B0C43D2D; Mon, 17 Jan 2005 00:51:37 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.13.0/8.13.0) with ESMTP id j0H0pa77015260; Sun, 16 Jan 2005 19:51:36 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Sun, 16 Jan 2005 19:51:35 -0500 To: Robert Watson , "David O'Brien" From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) cc: freebsd-current@freebsd.org Subject: Re: gratuitous gcc warnings: unused function arguments? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 00:51:38 -0000 At 9:05 PM +0000 1/16/05, Robert Watson wrote: >On Sun, 16 Jan 2005, David O'Brien wrote: > > > We're not going to hack GCC to deal with this. That is going way > > too far. This is coming up because people are using high WARNS > > values in Makefiles. Either back them down to a lower WARNS value; > > or we should add -Wno-unused-parameter to WARNS level 3. > >I'd be fine with simply pushing threshold for unused parameters up >a few notches on the warning scale. I'd like to have access to the >other interesting warnings are WARNS=3 and WARNS=4 relating to >qualifiers, strings, etc. I think it would be useful to keep that warning "in general", but have an option to turn it off. The following seems to work for me, assuming we can decide on the best name for a new NO_WUNUSED_ARGS option: Index: bsd.sys.mk =================================================================== RCS file: /usr/cvs/free/depot/src/share/mk/bsd.sys.mk,v retrieving revision 1.35 diff -u -r1.35 bsd.sys.mk --- bsd.sys.mk 12 Mar 2004 21:36:12 -0000 1.35 +++ bsd.sys.mk 17 Jan 2005 00:32:14 -0000 @@ -29,6 +29,9 @@ . if ${WARNS} > 5 CWARNFLAGS += -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls . endif +. if defined(NO_WUNUSED_ARGS) && ${WARNS} < 5 +CWARNFLAGS += -Wno-unused-parameter +. endif . if ${WARNS} > 1 && ${WARNS} < 5 # XXX Delete -Wuninitialized by default for now -- the compiler doesn't # XXX always get it right. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 01:47:48 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F64816A4CE; Mon, 17 Jan 2005 01:47:48 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3056A43D2F; Mon, 17 Jan 2005 01:47:47 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6BB6A51506; Sun, 16 Jan 2005 17:47:46 -0800 (PST) Date: Sun, 16 Jan 2005 17:47:46 -0800 From: Kris Kennaway To: Alan Cox Message-ID: <20050117014746.GA96797@xor.obsecurity.org> References: <20050115083847.GA47466@xor.obsecurity.org> <20050116003432.GA448@xor.obsecurity.org> <20050116050433.GA65733@xor.obsecurity.org> <20050116211349.GG26214@noel.cs.rice.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5vNYLRcllDrimb99" Content-Disposition: inline In-Reply-To: <20050116211349.GG26214@noel.cs.rice.edu> User-Agent: Mutt/1.4.2.1i cc: alc@freebsd.org cc: current@freebsd.org cc: Kris Kennaway Subject: Re: fstat triggered INVARIANTS panic in memrw() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 01:47:48 -0000 --5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 16, 2005 at 03:13:49PM -0600, Alan Cox wrote: > The "deadc0de" passed to generic_copyout() comes from the following > lines in devfs_read_f(c51773b8,eed96c84,ca75c800,flags=3D0): >=20 > if ((flags & FOF_OFFSET) =3D=3D 0) > uio->uio_offset =3D fp->f_offset; >=20 > Can you print the contents of the file structure? Hmm, I tried with gdb53 but it gave me a weird trace: (kgdb) bt #0 doadump () at pcpu.h:159 #1 0xc0528567 in boot (howto=3D260) at ../../../kern/kern_shutdown.c:398 #2 0xc0528037 in panic (fmt=3D0xc071abe1 "../../../kern/kern_shutdown.c") = at ../../../kern/kern_shutdown.c:554 #3 0xc068921a in vm_fault (map=3D0xc103b000, vaddr=3D3735928832, fault_typ= e=3D1 '\001', fault_flags=3D0) at ../../../vm/vm_fault.c:875 #4 0xc06deef2 in trap_pfault (frame=3D0xe7275b8c, usermode=3D0, eva=3D3735= 929054) at ../../../i386/i386/trap.c:713 #5 0xc06df3e3 in trap (frame=3D {tf_fs =3D -1066205160, tf_es =3D 16, tf_ds =3D -1056767984, tf_edi = =3D 134545408, tf_esi =3D -559038242, tf_ebp =3D -416850940, tf_isp =3D -41= 6851016, tf_ebx =3D 2058814332, tf_edx =3D 1966776, tf_ecx =3D 514703583, t= f_eax =3D -2101607556, tf_trapno =3D 12, tf_err =3D 0, tf_eip =3D -10665435= 58, tf_cs =3D 8, tf_eflags =3D 66050, tf_esp =3D 2058814332, tf_ss =3D -416= 850812}) at ../../../i386/i386/trap.c:414 #6 0xc06dd63a in generic_copyout () at ../../../i386/i386/support.s:760 #7 0xc06d8aba in memrw (dev=3D0xc22f8200, uio=3D0x8050000, flags=3D0) at .= ./../../i386/i386/mem.c:128 #8 0xc04d8d91 in devfs_read_f (fp=3D0x8050000, uio=3D0xdeadc0de, cred=3D0x= c3540380, flags=3D0, td=3D0xc3c34170) at ../../../fs/devfs/devfs_vnops.c:931 #9 0xc0552632 in dofileread (td=3D0x8050000, fp=3D0x7ab7037c, fd=3D0, buf= =3D0x0, nbyte=3D2058814332, offset=3D0, flags=3D0) at file.h:234 #10 0xc05527f5 in read (td=3D0xc3c34170, uap=3D0xdeadc0de) at ../../../kern= /sys_generic.c:107 #11 0xc06df7d7 in syscall (frame=3D {tf_fs =3D 47, tf_es =3D 47, tf_ds =3D 47, tf_edi =3D 2058814332, tf_= esi =3D 0, tf_ebp =3D -1077943512, tf_isp =3D -416850572, tf_ebx =3D 671608= 356, tf_edx =3D 134549504, tf_ecx =3D 0, tf_eax =3D 3, tf_trapno =3D 12, tf= _err =3D 2, tf_eip =3D 671899359, tf_cs =3D 31, tf_eflags =3D 514, tf_esp = =3D -1077943556, tf_ss =3D 47}) at ../../../i386/i386/trap.c:951 (kgdb) frame 8 #8 0xc04d8d91 in devfs_read_f (fp=3D0x8050000, uio=3D0xdeadc0de, cred=3D0x= c3540380, flags=3D0, td=3D0xc3c34170) at ../../../fs/devfs/devfs_vnops.c:931 931 error =3D dsw->d_read(dev, uio, ioflag); (kgdb) print fp $1 =3D (struct file *) 0x8050000 (kgdb) print *fp ---Can't read userspace from dump, or kernel process--- kgdb gave a different kind of weird trace, but at least I could access something that claimed to be a struct file*: (kgdb) bt #0 doadump () at pcpu.h:159 #1 0xc0528567 in boot (howto=3D260) at ../../../kern/kern_shutdown.c:398 #2 0xc0528037 in panic (fmt=3D0xc071abe1 "../../../kern/kern_shutdown.c") = at ../../../kern/kern_shutdown.c:554 #3 0xc068921a in vm_fault (map=3D0xc103b000, vaddr=3D3735928832, fault_typ= e=3D1 '\001', fault_flags=3D0) at ../../../vm/vm_fault.c:875 #4 0xc06deef2 in trap_pfault (frame=3D0xe7275b8c, usermode=3D0, eva=3D3735= 929054) at ../../../i386/i386/trap.c:713 #5 0xc06df3e3 in trap (frame=3D {tf_fs =3D -1066205160, tf_es =3D 16, tf_ds =3D -1056767984, tf_edi = =3D 134545408, tf_esi =3D -559038242, tf_ebp =3D -416850940, tf_isp =3D -41= 6851016, tf_ebx =3D 2058814332, tf_edx =3D 1966776, tf_ecx =3D 514703583, t= f_eax =3D -2101607556, tf_trapno =3D 12, tf_err =3D 0, tf_eip =3D -10665435= 58, tf_cs =3D 8, tf_eflags =3D 66050, tf_esp =3D 2058814332, tf_ss =3D -416= 850812}) at ../../../i386/i386/trap.c:414 #6 0xc06d0eaa in calltrap () at ../../../i386/i386/exception.s:139 #7 0xc0730018 in ?? () #8 0x00000010 in ?? () #9 0xc1030010 in ?? () #10 0x08050000 in ?? () #11 0xdeadc0de in ?? () #12 0xe7275c04 in ?? () #13 0xe7275bb8 in ?? () #14 0x7ab7037c in ?? () #15 0x001e02b8 in ?? () #16 0x1eadc0df in ?? () #17 0x82bc037c in ?? () #18 0x0000000c in ?? () #19 0x00000000 in ?? () #20 0xc06dd63a in generic_copyout () at ../../../i386/i386/support.s:760 #21 0x00000008 in ?? () #22 0x00010202 in ?? () #23 0x7ab7037c in ?? () #24 0xe7275c84 in ?? () #25 0xe7275c7c in ?? () #26 0xc052e709 in uiomove (cp=3D0xdeadc0de, n=3D2058814332, uio=3D0x8050000= ) at ../../../kern/kern_subr.c:171 #27 0xc06d8aba in memrw (dev=3D0xc22f8200, uio=3D0xe7275c84, flags=3D0) at = ../../../i386/i386/mem.c:128 #28 0xc04d8d91 in devfs_read_f (fp=3D0xc25f5dd0, uio=3D0xe7275c84, cred=3D0= xc3540380, flags=3D0, td=3D0xc3c34170) at ../../../fs/devfs/devfs_vnops.c:931 #29 0xc0552632 in dofileread (td=3D0xc3c34170, fp=3D0xc25f5dd0, fd=3D0, buf= =3D0x0, nbyte=3D2058814332, offset=3DUnhandled dwarf expression opcode 0x93 ) at file.h:234 #30 0xc05527f5 in read (td=3D0xc3c34170, uap=3D0xe7275d14) at ../../../kern= /sys_generic.c:107 #31 0xc06df7d7 in syscall (frame=3D ---Type to continue, or q to quit---q {tf_fs =3D 47, tf_es =3D 47, tf_ds =3D 47, tf_edi =3D 2058814332, tf_esi = =3D 0, tf_ebp =3D -Quit ) at ../../../i386/i386/trap.c:951 #32 0xc06d0eff in Xint0x80_syscall () at ../../../i386/i386/exception.s:200 #33 0x0000002f in ?? () #34 0x0000002f in ?? () #35 0x0000002f in ?? () #36 0x7ab7037c in ?? () #37 0x00000000 in ?? () #38 0xbfbfe328 in ?? () #39 0xe7275d74 in ?? () #40 0x2807ee24 in ?? () #41 0x08051000 in ?? () #42 0x00000000 in ?? () #43 0x00000003 in ?? () #44 0x0000000c in ?? () #45 0x00000002 in ?? () #46 0x280c5edf in ?? () #47 0x0000001f in ?? () #48 0x00000202 in ?? () #49 0xbfbfe2fc in ?? () #50 0x0000002f in ?? () #51 0x0809e8c8 in ?? () #52 0x0000001f in ?? () #53 0x0809e8b2 in ?? () #54 0x0809e89f in ?? () #55 0x2b550000 in ?? () #56 0xc3c32bd0 in ?? () #57 0xc3c34170 in ?? () #58 0xe7275c84 in ?? () #59 0xe7275c60 in ?? () #60 0xc2264170 in ?? () #61 0xc053c495 in sched_switch (td=3D0x0, newtd=3D0x2807ee24, flags=3DCanno= t access memory at address 0xbfbfe338 ) at ../../../kern/sched_4bsd.c:963 Previous frame inner to this frame (corrupt stack?) (kgdb) frame 28 #28 0xc04d8d91 in devfs_read_f (fp=3D0xc25f5dd0, uio=3D0xe7275c84, cred=3D0= xc3540380, flags=3D0, td=3D0xc3c34170) at ../../../fs/devfs/devfs_vnops.c:931 931 error =3D dsw->d_read(dev, uio, ioflag); (kgdb) print *fp $1 =3D {f_list =3D {le_next =3D 0xc25f5bf4, le_prev =3D 0xc25f52a8}, f_type= =3D 1, f_data =3D 0xc22f8200, f_flag =3D 1, f_mtxp =3D 0xc2251fd0, f_ops =3D 0xc074c140, f_cred =3D 0xc2b2a900, f_cou= nt =3D 2, f_vnode =3D 0xc3c6fbdc, f_offset =3D 3735929054, f_gcflag =3D 0, f_msgcount =3D 0, f_seqcount =3D= 1, f_nextoff =3D 3263609792} Kris --5vNYLRcllDrimb99 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB6xlCWry0BWjoQKURApVzAKC4p8QoueNwxVbjWGLnAAOVzp9M+wCgle0v NtIOMXZWnkI22l4MatJUs/Q= =41x/ -----END PGP SIGNATURE----- --5vNYLRcllDrimb99-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 02:18:17 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 375DA16A4CF; Mon, 17 Jan 2005 02:18:17 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C89F643D46; Mon, 17 Jan 2005 02:18:16 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B084351505; Sun, 16 Jan 2005 18:18:15 -0800 (PST) Date: Sun, 16 Jan 2005 18:18:15 -0800 From: Kris Kennaway To: Kris Kennaway Message-ID: <20050117021815.GA8953@xor.obsecurity.org> References: <20050115083847.GA47466@xor.obsecurity.org> <20050116003432.GA448@xor.obsecurity.org> <20050116050433.GA65733@xor.obsecurity.org> <20050116211349.GG26214@noel.cs.rice.edu> <20050117014746.GA96797@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YiEDa0DAkWCtVeE4" Content-Disposition: inline In-Reply-To: <20050117014746.GA96797@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i cc: alc@freebsd.org cc: Alan Cox cc: current@freebsd.org Subject: Re: fstat triggered INVARIANTS panic in memrw() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 02:18:17 -0000 --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 16, 2005 at 05:47:46PM -0800, Kris Kennaway wrote: > On Sun, Jan 16, 2005 at 03:13:49PM -0600, Alan Cox wrote: >=20 > > The "deadc0de" passed to generic_copyout() comes from the following > > lines in devfs_read_f(c51773b8,eed96c84,ca75c800,flags=3D0): > >=20 > > if ((flags & FOF_OFFSET) =3D=3D 0) > > uio->uio_offset =3D fp->f_offset; > >=20 > > Can you print the contents of the file structure? >=20 > (kgdb) frame 28 > #28 0xc04d8d91 in devfs_read_f (fp=3D0xc25f5dd0, uio=3D0xe7275c84, cred= =3D0xc3540380, flags=3D0, td=3D0xc3c34170) > at ../../../fs/devfs/devfs_vnops.c:931 > 931 error =3D dsw->d_read(dev, uio, ioflag); > (kgdb) print *fp > $1 =3D {f_list =3D {le_next =3D 0xc25f5bf4, le_prev =3D 0xc25f52a8}, f_ty= pe =3D 1, f_data =3D 0xc22f8200, f_flag =3D 1, > f_mtxp =3D 0xc2251fd0, f_ops =3D 0xc074c140, f_cred =3D 0xc2b2a900, f_c= ount =3D 2, f_vnode =3D 0xc3c6fbdc, > f_offset =3D 3735929054, f_gcflag =3D 0, f_msgcount =3D 0, f_seqcount = =3D 1, f_nextoff =3D 3263609792} 3735929054 =3D 0xdeadc0de. This same struct file appears all the way back to the syscall frame. I wonder if fstat is racing with a tty device removal or something (it's certainly racing with something, e.g.: [...] Jan 17 09:06:14 e450 kernel: pid 21313 (fstat), uid 0: exited on signal 11 Jan 17 10:27:15 e450 kernel: pid 81280 (fstat), uid 0: exited on signal 11 Jan 17 10:27:15 e450 kernel: pid 81287 (fstat), uid 0: exited on signal 11 Jan 17 10:27:15 e450 kernel: pid 81294 (fstat), uid 0: exited on signal 11 Jan 17 10:38:55 e450 kernel: pid 93203 (fstat), uid 0: exited on signal 11 Jan 17 10:38:55 e450 kernel: pid 93210 (fstat), uid 0: exited on signal 11 Kris --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB6yBnWry0BWjoQKURAkn/AKCWE97Y5J0/5T3c44B6tWuPw45WegCgn2yP LXJMlIWyJ/OHYLBtdad2rpY= =CvkD -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 02:25:55 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DE9116A4CF for ; Mon, 17 Jan 2005 02:25:55 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6291843D39 for ; Mon, 17 Jan 2005 02:25:54 +0000 (GMT) (envelope-from chiahsing@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so690166wri for ; Sun, 16 Jan 2005 18:25:53 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=rBsAioiUN7SUoILomxWUv/zVhcowg1+NR1vSzbQvM2iOGNj0R8w1ePojBG5unW+Xe3gyQLufSdOAvb/8yTIB7Z55JfgPw1ia18izH1de2KpupfsB/3Ggc2UO37OeSJVB3tMMyApW2hvLg1J48Lt2CL23EwPTbe6tvZQ7JWrjhj8= Received: by 10.54.52.40 with SMTP id z40mr71151wrz; Sun, 16 Jan 2005 18:25:52 -0800 (PST) Received: by 10.54.31.21 with HTTP; Sun, 16 Jan 2005 18:25:52 -0800 (PST) Message-ID: Date: Sun, 16 Jan 2005 18:25:52 -0800 From: David Yu To: Christopher Vance In-Reply-To: <20050117020039.GB630@nu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050117020039.GB630@nu.org> cc: freebsd-fs@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: NTFS unicode converting problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Yu List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 02:25:55 -0000 In my case, those Chinese filenames are still in UCS-2LE, and all characters are in plane 0. I tried to modify codes so that it can directly store the conversion result into the dirent structure, but the convchr() funtion failed everytime for Chinese character while there is no problem with Ascii characters. I thought converting from UCS-2 to UTF-8 should be very easy? On Mon, 17 Jan 2005 13:00:39 +1100, Christopher Vance wrote: > On Sun, Jan 16, 2005 at 01:44:04PM -0800, David Yu wrote: > >Hi, it seems that NTFS in FreeBSD uses a 16-bit long wchar to store > >filename. When I wanted to convert some Chinese filename into UTF-8, > >the conversion was failed because a single Chinese character needs 3 > >bytes in UTF-8. Is anyone already working on this problem? If not, I > >would like to do something about it. Any suggestions? > > From memory, old Windows used UCS-2, while newer Windows uses UTF-16. > Was the bad character in plane 0 or higher? > > -- > Christopher Vance > From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 02:30:33 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D5C316A4CE; Mon, 17 Jan 2005 02:30:33 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA60F43D48; Mon, 17 Jan 2005 02:30:32 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id BE1DE512C2; Sun, 16 Jan 2005 18:30:31 -0800 (PST) Date: Sun, 16 Jan 2005 18:30:31 -0800 From: Kris Kennaway To: Kris Kennaway Message-ID: <20050117023031.GA12825@xor.obsecurity.org> References: <20050115083847.GA47466@xor.obsecurity.org> <20050116003432.GA448@xor.obsecurity.org> <20050116050433.GA65733@xor.obsecurity.org> <20050116211349.GG26214@noel.cs.rice.edu> <20050117014746.GA96797@xor.obsecurity.org> <20050117021815.GA8953@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ew6BAiZeqk4r7MaW" Content-Disposition: inline In-Reply-To: <20050117021815.GA8953@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i cc: alc@freebsd.org cc: Alan Cox cc: current@freebsd.org Subject: Re: fstat triggered INVARIANTS panic in memrw() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 02:30:33 -0000 --ew6BAiZeqk4r7MaW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jan 16, 2005 at 06:18:15PM -0800, Kris Kennaway wrote: > On Sun, Jan 16, 2005 at 05:47:46PM -0800, Kris Kennaway wrote: > > On Sun, Jan 16, 2005 at 03:13:49PM -0600, Alan Cox wrote: > >=20 > > > The "deadc0de" passed to generic_copyout() comes from the following > > > lines in devfs_read_f(c51773b8,eed96c84,ca75c800,flags=3D0): > > >=20 > > > if ((flags & FOF_OFFSET) =3D=3D 0) > > > uio->uio_offset =3D fp->f_offset; > > >=20 > > > Can you print the contents of the file structure? > >=20 > > (kgdb) frame 28 > > #28 0xc04d8d91 in devfs_read_f (fp=3D0xc25f5dd0, uio=3D0xe7275c84, cred= =3D0xc3540380, flags=3D0, td=3D0xc3c34170) > > at ../../../fs/devfs/devfs_vnops.c:931 > > 931 error =3D dsw->d_read(dev, uio, ioflag); > > (kgdb) print *fp > > $1 =3D {f_list =3D {le_next =3D 0xc25f5bf4, le_prev =3D 0xc25f52a8}, f_= type =3D 1, f_data =3D 0xc22f8200, f_flag =3D 1, > > f_mtxp =3D 0xc2251fd0, f_ops =3D 0xc074c140, f_cred =3D 0xc2b2a900, f= _count =3D 2, f_vnode =3D 0xc3c6fbdc, > > f_offset =3D 3735929054, f_gcflag =3D 0, f_msgcount =3D 0, f_seqcount= =3D 1, f_nextoff =3D 3263609792} >=20 > 3735929054 =3D 0xdeadc0de. This same struct file appears all the way > back to the syscall frame. I wonder if fstat is racing with a tty > device removal or something (it's certainly racing with something, > e.g.: Devices may not be to blame; I was able to trigger this by running fstat in a loop and then running 'make' in /usr/ports/misc/screen (with the idea of testing the tty hypothesis :) An interesting datapoint is that none of the non-i386 package machines have hit this problem, but the i386 machines can't stay up for more than a few minutes under load (which translates to only a few fstat invocations). Kris --ew6BAiZeqk4r7MaW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB6yNHWry0BWjoQKURAkAUAJ9i0k20MWc3+u8Cqt+bPkMXanQ04ACg2Y96 fYTN7UI3l6P9oXoGllh2C4I= =SMSE -----END PGP SIGNATURE----- --ew6BAiZeqk4r7MaW-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 05:28:21 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9DD116A4CF for ; Mon, 17 Jan 2005 05:28:21 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 746D443D41 for ; Mon, 17 Jan 2005 05:28:21 +0000 (GMT) (envelope-from chiahsing@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so700848wri for ; Sun, 16 Jan 2005 21:28:20 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=CvYPal2nDlp9tRlNbzAI1FNClwPoSA/qUWFqQ7nPQ0y0aBlVYwFXnaO7lSv2wJfERufC76rDz1zNxpDAll1j/BtliHYRPFZWT8garqfVmFuUNi7gWWU9NSPgH1e0E3MeAGQHPkC0+CFJZ3AtixZJeag8rG7LqVrOELKGzy7hCyI= Received: by 10.54.40.34 with SMTP id n34mr131592wrn; Sun, 16 Jan 2005 21:28:20 -0800 (PST) Received: by 10.54.31.21 with HTTP; Sun, 16 Jan 2005 21:28:20 -0800 (PST) Message-ID: Date: Sun, 16 Jan 2005 21:28:20 -0800 From: David Yu To: Christopher Vance In-Reply-To: <20050117032255.GC630@nu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050117020039.GB630@nu.org> <20050117032255.GC630@nu.org> cc: freebsd-fs@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: NTFS unicode converting problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Yu List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 05:28:22 -0000 The problem is that I have to default XLAT16_ACCEPT_3BYTE_CHR in both libkiconv and module/libiconv.ko. Though it works, I don't it is a good way to use translation table since UCS-2 to UTF-8 is so straightforward. Maybe we need to write a new kernel side iconv converter for this? I have no idea about those iconv codes in the kernel at all. On Mon, 17 Jan 2005 14:22:55 +1100, Christopher Vance wrote: > On Sun, Jan 16, 2005 at 06:25:52PM -0800, David Yu wrote: > >In my case, those Chinese filenames are still in UCS-2LE, and all > >characters are in plane 0. I tried to modify codes so that it can > >directly store the conversion result into the dirent structure, but > >the convchr() funtion failed everytime for Chinese character while > >there is no problem with Ascii characters. I thought converting from > >UCS-2 to UTF-8 should be very easy? > > Maybe the conversion routine disagrees with you about byte order? > > -- > Christopher Vance > From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 05:36:57 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C5DE16A4CE; Mon, 17 Jan 2005 05:36:57 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB55B43D3F; Mon, 17 Jan 2005 05:36:56 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id j0H5atl9096410; Sun, 16 Jan 2005 21:36:55 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id j0H5atPh096409; Sun, 16 Jan 2005 21:36:55 -0800 (PST) (envelope-from obrien) Date: Sun, 16 Jan 2005 21:36:55 -0800 From: "David O'Brien" To: Garance A Drosihn Message-ID: <20050117053655.GA96378@dragon.nuxi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-current@freebsd.org cc: Robert Watson Subject: Re: gratuitous gcc warnings: unused function arguments? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 05:36:57 -0000 On Sun, Jan 16, 2005 at 07:51:35PM -0500, Garance A Drosihn wrote: > At 9:05 PM +0000 1/16/05, Robert Watson wrote: > >On Sun, 16 Jan 2005, David O'Brien wrote: > > > We're not going to hack GCC to deal with this. That is going way > > > too far. This is coming up because people are using high WARNS > > > values in Makefiles. Either back them down to a lower WARNS value; > > > or we should add -Wno-unused-parameter to WARNS level 3. > > > >I'd be fine with simply pushing threshold for unused parameters up > >a few notches on the warning scale. I'd like to have access to the > >other interesting warnings are WARNS=3 and WARNS=4 relating to > >qualifiers, strings, etc. > > I think it would be useful to keep that warning "in general", but > have an option to turn it off. The following seems to work for me, > assuming we can decide on the best name for a new NO_WUNUSED_ARGS > option: Do you have a piece of code that exhibits this warning but otherwise could pass at higher warning level? I'm reisitance to adding a lot of NO_FOO_WARNING knobs. Otherwise we might as well as remove the whole WARNS thing and set each warning a Makefile wants. -- -- David (obrien@FreeBSD.org) From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 06:30:28 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4153216A4CE for ; Mon, 17 Jan 2005 06:30:28 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4773B43D31 for ; Mon, 17 Jan 2005 06:30:26 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id j0H6TB4g023492 for ; Mon, 17 Jan 2005 16:59:11 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Mon, 17 Jan 2005 17:00:16 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id j0H6KRQ21727 for ; Mon, 17 Jan 2005 16:50:28 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id YK38HR0L; Mon, 17 Jan 2005 16:50:04 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id j0H6LIol062696 for ; Mon, 17 Jan 2005 16:51:18 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id j0H6LIWq062695 for freebsd-current@freebsd.org; Mon, 17 Jan 2005 16:51:18 +1030 (CST) (envelope-from wilkinsa) Date: Mon, 17 Jan 2005 16:51:18 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20050117062118.GA62565@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: [DDB] show pcpu .... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 06:30:28 -0000 Can anyone point me to an explanation of 'show pcpu' ? It is first introduced here: http://www.freebsd.org/releases/5.0R/DP1/relnotes-i386.html With a link to ddb(4) man page: http://www.freebsd.org/cgi/man.cgi?query=ddb&sektion=4&manpath=FreeBSD+5.0-current However, the man page says nothing whatsoever about 'show pcpu'. Anyone ? - aW From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 06:38:18 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F058016A4CE for ; Mon, 17 Jan 2005 06:38:18 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DE5443D46 for ; Mon, 17 Jan 2005 06:38:18 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j0H6ahFW038696; Sun, 16 Jan 2005 23:36:48 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 16 Jan 2005 23:37:45 -0700 (MST) Message-Id: <20050116.233745.102654477.imp@bsdimp.com> To: doconnor@gsoft.com.au From: "M. Warner Losh" In-Reply-To: <200501161134.25828.doconnor@gsoft.com.au> References: <20050115155538.GA36629@obiwan.tataz.chchile.org> <200501161134.25828.doconnor@gsoft.com.au> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: jeremie@le-hen.org Subject: Re: no /dev/ums0 when module loaded X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 06:38:19 -0000 In message: <200501161134.25828.doconnor@gsoft.com.au> "Daniel O'Connor" writes: : > Is this a bug or a feature ? I've been told that whenever an USB device : > is not grabbed by any driver on attach, it uses ugen(4) and it won't be : > possible to ``move'' it from ugen(4) to ums(4) later. : : This is a problem with the USB stack - devices are not reprobed when a new : module is loaded. : : I preload all the USB modules I plan to use (a bit annoying I admit). I : believe there is ongoing work in this area though. There is indeed ongoing work in this area. Unless you need ugen, don't load it is the best answer for now. I have some work that I'm migrating to the tree, but this will take a while to get into the tree... Warner From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 06:45:42 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5EE616A4CE for ; Mon, 17 Jan 2005 06:45:42 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FC9A43D1D for ; Mon, 17 Jan 2005 06:45:41 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id j0H6jNiM008027; Mon, 17 Jan 2005 17:15:24 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: "M. Warner Losh" Date: Mon, 17 Jan 2005 17:15:06 +1030 User-Agent: KMail/1.7.1 References: <20050115155538.GA36629@obiwan.tataz.chchile.org> <200501161134.25828.doconnor@gsoft.com.au> <20050116.233745.102654477.imp@bsdimp.com> In-Reply-To: <20050116.233745.102654477.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1113670.EeWOSFGBmM"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501171715.22761.doconnor@gsoft.com.au> X-Spam-Score: -5.7 () IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_01_02,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: freebsd-current@freebsd.org cc: jeremie@le-hen.org Subject: Re: no /dev/ums0 when module loaded X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 06:45:42 -0000 --nextPart1113670.EeWOSFGBmM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Mon, 17 Jan 2005 17:07, M. Warner Losh wrote: > : I preload all the USB modules I plan to use (a bit annoying I admit). I > : believe there is ongoing work in this area though. > > There is indeed ongoing work in this area. Unless you need ugen, > don't load it is the best answer for now. I have some work that I'm > migrating to the tree, but this will take a while to get into the > tree... Does not having ugen make this stuff work? Hmm actually let me try.. No doesn't seem to :( ie.. unplug mouse kldunload ums kldunload ugen plug in mouse kldload ums nothing :) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1113670.EeWOSFGBmM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBB618C5ZPcIHs/zowRAjLbAJ9MEAekWsX7a7L92BOmEX1RV10ieACgqrJ6 3KM8GzOYLSxSST0Gv/TXpEE= =59Ij -----END PGP SIGNATURE----- --nextPart1113670.EeWOSFGBmM-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 06:53:15 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 725EC16A4CE for ; Mon, 17 Jan 2005 06:53:15 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 029E343D1F for ; Mon, 17 Jan 2005 06:53:15 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j0H6pxD6038890; Sun, 16 Jan 2005 23:51:59 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 16 Jan 2005 23:53:01 -0700 (MST) Message-Id: <20050116.235301.05622144.imp@bsdimp.com> To: doconnor@gsoft.com.au From: "M. Warner Losh" In-Reply-To: <200501171715.22761.doconnor@gsoft.com.au> References: <200501161134.25828.doconnor@gsoft.com.au> <20050116.233745.102654477.imp@bsdimp.com> <200501171715.22761.doconnor@gsoft.com.au> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: jeremie@le-hen.org Subject: Re: no /dev/ums0 when module loaded X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 06:53:15 -0000 In message: <200501171715.22761.doconnor@gsoft.com.au> "Daniel O'Connor" writes: : On Mon, 17 Jan 2005 17:07, M. Warner Losh wrote: : > : I preload all the USB modules I plan to use (a bit annoying I admit). I : > : believe there is ongoing work in this area though. : > : > There is indeed ongoing work in this area. Unless you need ugen, : > don't load it is the best answer for now. I have some work that I'm : > migrating to the tree, but this will take a while to get into the : > tree... : : Does not having ugen make this stuff work? : Hmm actually let me try.. No doesn't seem to :( : : ie.. : unplug mouse : kldunload ums : kldunload ugen : plug in mouse : kldload ums : nothing :) Works for me. However, it seems that I have a bunch of stuff outside the tree that needs to be brought in. And that stuff is mixed in with some other stuff that's not ready for prime time, so I have to be careful about what I bring in... And there's at least one bug in newbus that I need to find and fix before some things (like anything that implements ucom) will work, and another before ugen will autodetach... Warner From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 07:02:13 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 979C116A4CF for ; Mon, 17 Jan 2005 07:02:13 +0000 (GMT) Received: from pimout3-ext.prodigy.net (pimout3-ext.prodigy.net [207.115.63.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DEE543D45 for ; Mon, 17 Jan 2005 07:02:10 +0000 (GMT) (envelope-from julian@elischer.org) Received: from [192.168.1.102] (adsl-216-100-134-143.dsl.snfc21.pacbell.net [216.100.134.143])j0H71eoB234910; Mon, 17 Jan 2005 02:01:51 -0500 Message-ID: <41EB62D2.10101@elischer.org> Date: Sun, 16 Jan 2005 23:01:38 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8a3) Gecko/20041017 X-Accept-Language: en, hu MIME-Version: 1.0 To: "Wilkinson, Alex" References: <20050117062118.GA62565@squash.dsto.defence.gov.au> In-Reply-To: <20050117062118.GA62565@squash.dsto.defence.gov.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: [DDB] show pcpu .... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 07:02:13 -0000 Wilkinson, Alex wrote: > Can anyone point me to an explanation of 'show pcpu' ? > > It is first introduced here: > > http://www.freebsd.org/releases/5.0R/DP1/relnotes-i386.html Each processor has a memory section that contains a separate and different copy of the per-cpu structure (struct pcpu). The fields of this structure are usually accessed via the PCPU_GET() and PCPU_SET() macros. curthread (or curproc in earlier systems) is defined in terms of thiese macros. "show pcpu" shows the values of the particular insatanc of this structure for the cpu on which the ddb is running. > > With a link to ddb(4) man page: > > http://www.freebsd.org/cgi/man.cgi?query=ddb&sektion=4&manpath=FreeBSD+5.0-current > > However, the man page says nothing whatsoever about 'show pcpu'. > > Anyone ? > > - aW > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 07:04:39 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97D3016A4CF for ; Mon, 17 Jan 2005 07:04:39 +0000 (GMT) Received: from pimout3-ext.prodigy.net (pimout3-ext.prodigy.net [207.115.63.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0456743D53 for ; Mon, 17 Jan 2005 07:04:39 +0000 (GMT) (envelope-from julian@elischer.org) Received: from [192.168.1.102] (adsl-216-100-134-143.dsl.snfc21.pacbell.net [216.100.134.143])j0H74UoB276528; Mon, 17 Jan 2005 02:04:33 -0500 Message-ID: <41EB637D.5010702@elischer.org> Date: Sun, 16 Jan 2005 23:04:29 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8a3) Gecko/20041017 X-Accept-Language: en, hu MIME-Version: 1.0 To: "Daniel O'Connor" References: <20050115155538.GA36629@obiwan.tataz.chchile.org> <200501161134.25828.doconnor@gsoft.com.au> <20050116.233745.102654477.imp@bsdimp.com> <200501171715.22761.doconnor@gsoft.com.au> In-Reply-To: <200501171715.22761.doconnor@gsoft.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: jeremie@le-hen.org cc: "M. Warner Losh" Subject: Re: no /dev/ums0 when module loaded X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 07:04:39 -0000 Daniel O'Connor wrote: > On Mon, 17 Jan 2005 17:07, M. Warner Losh wrote: > >>: I preload all the USB modules I plan to use (a bit annoying I admit). I >>: believe there is ongoing work in this area though. >> >>There is indeed ongoing work in this area. Unless you need ugen, >>don't load it is the best answer for now. I have some work that I'm >>migrating to the tree, but this will take a while to get into the >>tree... > > > Does not having ugen make this stuff work? > Hmm actually let me try.. No doesn't seem to :( > > ie.. > unplug mouse > kldunload ums > kldunload ugen > plug in mouse > kldload ums > nothing :) > no, because the USB system doesn't have an interface to allow a new driver to taste all the unattached devices.. in the case of ugen, it would have to allow new drivers to get tentative information from ugen about its devices and a method for requesting ugen to give up a device. hopefully we can grow such a capability with time. From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 07:14:46 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4159916A4CE for ; Mon, 17 Jan 2005 07:14:46 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A26B43D49 for ; Mon, 17 Jan 2005 07:14:43 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id j0H7EYxs008326; Mon, 17 Jan 2005 17:44:38 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: "M. Warner Losh" Date: Mon, 17 Jan 2005 17:44:33 +1030 User-Agent: KMail/1.7.1 References: <200501161134.25828.doconnor@gsoft.com.au> <200501171715.22761.doconnor@gsoft.com.au> <20050116.235301.05622144.imp@bsdimp.com> In-Reply-To: <20050116.235301.05622144.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2212942.oZUaJRgcJC"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501171744.34103.doconnor@gsoft.com.au> X-Spam-Score: -5.4 () IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: freebsd-current@freebsd.org cc: jeremie@le-hen.org Subject: Re: no /dev/ums0 when module loaded X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 07:14:46 -0000 --nextPart2212942.oZUaJRgcJC Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Mon, 17 Jan 2005 17:23, M. Warner Losh wrote: > Works for me. However, it seems that I have a bunch of stuff outside > the tree that needs to be brought in. And that stuff is mixed in with > some other stuff that's not ready for prime time, so I have to be > careful about what I bring in... And there's at least one bug in Understood. > newbus that I need to find and fix before some things (like anything > that implements ucom) will work, and another before ugen will > autodetach... It never ends.. :) Thanks for working on it. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart2212942.oZUaJRgcJC Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBB62Xa5ZPcIHs/zowRAsq5AKCZziPvT49mYU7s3o73zZiwu1naAACglWZj nH+55Qv65YDz/rpPFkMKhJQ= =ArnS -----END PGP SIGNATURE----- --nextPart2212942.oZUaJRgcJC-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 07:17:22 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A722B16A4CE for ; Mon, 17 Jan 2005 07:17:22 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E86643D2F for ; Mon, 17 Jan 2005 07:17:22 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j0H7G8ni039077; Mon, 17 Jan 2005 00:16:08 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 17 Jan 2005 00:17:11 -0700 (MST) Message-Id: <20050117.001711.44155805.imp@bsdimp.com> To: julian@elischer.org From: "M. Warner Losh" In-Reply-To: <41EB637D.5010702@elischer.org> References: <20050116.233745.102654477.imp@bsdimp.com> <200501171715.22761.doconnor@gsoft.com.au> <41EB637D.5010702@elischer.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: jeremie@le-hen.org Subject: Re: no /dev/ums0 when module loaded X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 07:17:22 -0000 In message: <41EB637D.5010702@elischer.org> Julian Elischer writes: : Daniel O'Connor wrote: : > On Mon, 17 Jan 2005 17:07, M. Warner Losh wrote: : > : >>: I preload all the USB modules I plan to use (a bit annoying I admit). I : >>: believe there is ongoing work in this area though. : >> : >>There is indeed ongoing work in this area. Unless you need ugen, : >>don't load it is the best answer for now. I have some work that I'm : >>migrating to the tree, but this will take a while to get into the : >>tree... : > : > : > Does not having ugen make this stuff work? : > Hmm actually let me try.. No doesn't seem to :( : > : > ie.. : > unplug mouse : > kldunload ums : > kldunload ugen : > plug in mouse : > kldload ums : > nothing :) : > : : no, because the USB system doesn't have an interface to allow a new driver to : taste all the unattached devices.. in the case of ugen, it would have to : allow new drivers to get tentative information from ugen about its devices : and a method for requesting ugen to give up a device. Yes. That method is called detach :-) Probe is supposed to be non-destructive, so I'm working on a way to cope with that too (eg, for the perverse ones that aren't idempotent). Warner From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 07:40:47 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E50F16A4CE for ; Mon, 17 Jan 2005 07:40:47 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7B9A43D39 for ; Mon, 17 Jan 2005 07:40:46 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j0H7ZhHX039265; Mon, 17 Jan 2005 00:35:43 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 17 Jan 2005 00:36:45 -0700 (MST) Message-Id: <20050117.003645.73085084.imp@bsdimp.com> To: doconnor@gsoft.com.au From: "M. Warner Losh" In-Reply-To: <200501171744.34103.doconnor@gsoft.com.au> References: <200501171715.22761.doconnor@gsoft.com.au> <20050116.235301.05622144.imp@bsdimp.com> <200501171744.34103.doconnor@gsoft.com.au> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: jeremie@le-hen.org Subject: Re: no /dev/ums0 when module loaded X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 07:40:47 -0000 In message: <200501171744.34103.doconnor@gsoft.com.au> "Daniel O'Connor" writes: : On Mon, 17 Jan 2005 17:23, M. Warner Losh wrote: : > Works for me. However, it seems that I have a bunch of stuff outside : > the tree that needs to be brought in. And that stuff is mixed in with : > some other stuff that's not ready for prime time, so I have to be : > careful about what I bring in... And there's at least one bug in : : Understood. : : > newbus that I need to find and fix before some things (like anything : > that implements ucom) will work, and another before ugen will : > autodetach... : : It never ends.. :) : : Thanks for working on it. Yup. If I do a naive fix for the ugen problem, it breaks acpi. Warner From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 08:40:55 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 497DA16A4CE; Mon, 17 Jan 2005 08:40:55 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2FFC43D2D; Mon, 17 Jan 2005 08:40:53 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.12] (g4.samsco.home [192.168.254.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id j0H8ivSq018844; Mon, 17 Jan 2005 01:44:57 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41EB7A11.7030602@freebsd.org> Date: Mon, 17 Jan 2005 01:40:49 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@freebsd.org, current@freebsd.org, stable@freebsd.org Content-Type: multipart/mixed; boundary="------------030205060202020502090801" X-Spam-Status: No, hits=0.6 required=3.8 tests=DOMAIN_4U2 autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org Subject: FreeBSD Status Report July-December 2004 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 08:40:55 -0000 This is a multi-part message in MIME format. --------------030205060202020502090801 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit --------------030205060202020502090801 Content-Type: text/plain; x-mac-type="0"; x-mac-creator="0"; name="report-july-2004-dec-2004.txt" Content-Transfer-Encoding: 8bit Content-Disposition: inline; filename="report-july-2004-dec-2004.txt" July-December 2004 Status Report Introduction The FreeBSD status report is back again after another small break. The second half of 2004 was incredibly busy; FreeBSD 5.3 was released, the 6-CURRENT development branch started, and EuroBSDCon 2004 was a huge success, just to name a few events. This report is packed with an impressive 44 submissions, the most of any report ever! It's also my pleasure to welcome Max Laier and Tom Rhodes to the status report team. They kindly volunteered to help keep the reports on time and help improve their quality. Max in particular is responsible for the reports being divided up into topics for easier browsing. Many thanks to both for their help! _________________________________________________________________ Projects * Common Address Redundancy Protocol - CARP * Dingo Monthly Report * FreeBSD profile.sh * FreeBSD Release Engineering * FreeSBIE Status Report * Funded FreeBSD kernel development * Improved Multibyte/Wide Character Support * Project Frenzy (FreeBSD-based Live-CD) * Secure Updating Documentation * Hardware Notes * The FreeBSD Dutch Documentation Team Kernel * ATA Driver Status Report * CPU Cache Prefetching * i386 Interrupt Code & PCI Interrupt Routing * kgi4BSD * Layer 2 PFIL_HOOKS * Low-overhead performance monitoring for FreeBSD * Move ARP out of routing table * Network Stack Locking * New Modular Input Device Layer * SMPng Status Report * Sync Protocols (SPPP and NETGRAPH) * TCP Cleanup and Optimizations * TCP Reassembly Rewrite and Optimization * TTCPv2: Transactional TCP version 2 Architectures * FreeBSD on Xen * FreeBSD/arm status report * PowerPC Port Ports * FreeBSD GNOME Project Status Report * OpenOffice.org port status * Ports Collection * Update of the Linux userland infrastructure Vendor / 3rd Party Software * ALTQ * Cronyx Adapters Drivers * OpenBSD packet filter - pf Miscellaneous * EuroBSDCon 2004 submitted papers are online * EuroBSDCon 2005 - Basel / Switzerland * FreeBSD Security Officer and Security Team * FreeBSD Source Repository Mirror for svn/svk * Wiki with new software * Atheros Wireless Support * ifconfig Overhaul * New DHCP Client * Wireless Networking Support _________________________________________________________________ ALTQ URL: http://people.freebsd.org/~mlaier/ALTQ_driver/ URL: http://www.freebsd.org/cgi/man.cgi?query=altq&manpath=FreeBSD+6.0-curr ent&format=html Contact: Max Laier ALTQ is part of FreeBSD 5.3 release and can be used to do traffic shaping and classification with PF. In CURRENT IPFW gained the ability to do ALTQ classification as well. A steadily increasing number of NIC drivers has been converted to support ALTQ. For details see the ALTQ(4) man-page. Open tasks: 1. Convert/test more NIC drivers. 2. Write documentation. _________________________________________________________________ ATA Driver Status Report Contact: Sјren Schmidt The ATA driver is undergoing quite a few important changes, mainly it is being converted into modules so it can be loaded/unloaded at will, and just the pieces for wanted functionality need be present. This calls for ata-raid to finally be rewritten. This is almost done for reading metadata so arrays defined in the BIOS can be used, and its grown quite a few new metadata formats. This also paves the way for ataraid to finally be able to take advantage of some of the newer controllers "RAID" abilities. However this needs more work to materialize but now its finally possible There is also support coming for a few new chipsets as usual. The work is just about finished enough that it can be released as patches to sort out eventual problems before hitting current. The changes are pretty massive as this touches all over the driver infrastructure, so lots of old bugs and has also been spotted and fixed during this journey _________________________________________________________________ Atheros Wireless Support Contact: Sam Leffler The ath driver was updated to support all the new features added to the net80211 layer. As part of this work a new version of the Hardware Access Layer (HAL) module was brought in; this version supports all available Atheros parts found in PCI and Cardbus products. Otherwise, adhoc mode should now be usable, antenna management has been significantly improved, and soft LED support now identifies traffic patterns. The transmit rate control algorithm was split out of the driver into an independent module. Two different algorithms are available with other algorithms (hopefully) to be added. Work is actively going on to add Atheros' SuperG capabilities. _________________________________________________________________ Common Address Redundancy Protocol - CARP URL: http://people.freebsd.org/~mlaier/CARP/ Contact: Max Laier CARP is an alternative to VRRP. In contrast to VRRP it has full support for IPv6 and uses crypto to protect the advertisements. It was developed by OpenBSD due to concerns that the HSRP patent might cover VRRP and CISCO might defend its patent. CARP has, since then, improved a lot over VRRP. CARP is implemented as an in-kernel multicast protocol and displays itself as a pseudo interface to the user. This makes configuration and administration very simple. CARP also incorporates MAC based load-balancing. Patches for RELENG_5 and recent HEAD are available from the URL above. I plan to import these patches in the course of the next two to four month. RELENG_5 has all necessary ABI to support CARP and I might MFC it for release 5.4 or 5.5 - depending how well the HEAD import goes. Open tasks: 1. Please test and send feedback! 2. Write documentation. 3. Import newest OpenBSD changes. _________________________________________________________________ CPU Cache Prefetching URL: http://www.nrg4u.com/freebsd/tcp_reass+prefetch-20041216.patch Contact: Andre Oppermann Modern CPU's can only perform to their maximum if their working code is in fast L1-3 cache memory instead of the bulk main memory. All of today's CPU's support certain L1-3 cache prefetching instructions which cause data to be retrieved from main memory to the cache ahead of the time that it is already in place when it is eventually accessed by the CPU. CPU Cache Prefetching however is not a golden bullet and has to be used with extreme care and only in very specific places to be beneficial. Incorrect usage can lead to massive cache pollution and a drop in effective performance. Correct and very carefully usage on the other can lead to drastic performance increases in common operations. In the linked patch CPU cache prefetching has been used to prefetch the packet header (OSI layer 2 to 4) into the CPU caches right after entering into the network stack. This avoids a complete CPU stall on the first access to the packet header because packets get DMA'd into main memory and thus never are already pre-cache in the CPU caches. A second use in the patch is in the TCP input code to prefetch the entire struct tcpcb which is very large and used with a very high probability. Use in both of these places show a very significant performance gain but not yet fully quantified. The final patch will include documentation and a guide to evaluate and assess the use of CPU cache prefetch instructions in the kernel. _________________________________________________________________ Cronyx Adapters Drivers URL: http://www.cronyx.ru/software Contact: Roman Kurakin Currently FreeBSD supports three family of Cronyx sync adapters: Tau-PCI - cp(4), Tau-ISA - ctau(4) and Sigma - cx(4). All these drivers were updated (in 6.current) and now they are Giant free. However, this is true only for sppp(4). If you are using Netgraph or async mode (for Sigma) you may need to turn mpsafenet off for that driver with appropriate kernel variable. Open tasks: 1. Now all these drivers and sppp(4) are using recursive lock. So the first task is to make these locks non recursive. 2. Second task is to check/make drivers workable in netgraph/async mode. 3. I think about ability to switch between sppp/netgraph mode at runtime. For now you should recompile module/kernel to change mode. _________________________________________________________________ Dingo Monthly Report URL: http://www.freebsd.org/projects/dingo/index.html Contact: George Neville-Neil In the last month we set up the project page noted above and also created a p4 branch for those of us who use p4 to do work outside of CVS. _________________________________________________________________ EuroBSDCon 2004 submitted papers are online URL: http://www.eurobsdcon2004.de/papers.html Contact: Patrick M. Hausen Finally all of the papers and presentations are online for download from our conference website. Thanks again to all who helped make EuroBSDCon 2004 a success. _________________________________________________________________ EuroBSDCon 2005 - Basel / Switzerland URL: http://www.eurobsdcon.org/ Contact: Max Laier This year's EuroBSDCon will be held at the University of Basel, Switzerland from 25th through 27th November. The call for papers should happen shortly. Please consider attending or even presenting. Check the conference homepage for more information. _________________________________________________________________ FreeBSD GNOME Project Status Report URL: http://www.FreeBSD.org/gnome/ Contact: Joe Marcus We haven't produced a status report in a while, but that's just because we've been busy. Since our last report in March 2004, we have added three new team members: Koop Mast (kwm), Jeremy Messenger (mezz), and Michael Johnson (ahze). Jeremy has been quite helpful in GNOME development porting while Michael and Koop have been focusing on improving GNOME multimedia, especially GStreamer. The stable release of GNOME is now up to 2.8.2, and we are actively working on the GNOME 2.9 development branch with is slated to become 2.10 on March 9 of this year. The GNOME Tinderbox is still cranking away, and producing packages for both the stable and development releases of GNOME for all supported i386 versions of FreeBSD. Thanks to Michael Johnson, the FreeBSD GNOME team has recently been given permission to use the Firefox and Thunderbird names , official icons, and to produce officially branded builds. Mozilla has also been very interested in merging our local patches back into the official source tree. This should greatly improve the quality of Firefox and Thunderbird on FreeBSD moving forward. Finally, Adam Weinberger (adamw) has been pestering the team for photos so that we can finally show the community who we are. It is still unclear as to whether or not this will attract more FreeBSD GNOME users, or land us on the Homeland Security no-fly list. Open tasks: 1. Need help porting HAL to FreeBSD (contact marcus@FreeBSD.org ) 2. Need help porting libburn to FreeBSD (contact bland@FreeBSD.org ) 3. Anyone interested in reviving Gnome Meeting should contact kwm@FreeBSD.org _________________________________________________________________ FreeBSD on Xen URL: http://www.fsmware.com/xenofreebsd/ URL: http://www.cl.cam.ac.uk/Research/SRG/netos/xen/ Contact: Kip Macy FreeBSD 5.2.1 is stable on the stable branch of Xen as a guest. FreeBSD 5.3 runs on the stable branch of Xen as a guest, but a couple of bugs need to be tracked down. Open tasks: 1. FreeBSD support for running in Domain 0 (host) 2. FreeBSD support for VM checkpoint and migration _________________________________________________________________ FreeBSD profile.sh URL: https://projects.fsck.ch/profile Contact: Tobias Roth FreeBSD profile.sh is targeted at laptops. It allows to define multiple network environments (eg, home, work), and will then detect in which environment the laptop is started and configure it accordingly. Almost everything from under /etc can be configured per environment, and only the overrides to the default /etc have to be defined. Suspending in one environment and resuming in a different one is also supported. Proper integration into the acpi/apm and several small improvements are underway. More testing with different system configurations is needed. _________________________________________________________________ FreeBSD Release Engineering URL: http://www.FreeBSD.org/releng Contact: Scott Long At long last, FreeBSD 5.3 was released in November of 2004. This marked the start of the RELENG_5/5-STABLE branch and the beginning of the 6-CURRENT development branch. Many thanks to the tireless efforts of the FreeBSD developer and user community for making this release a success. FreeBSD 4.11 release engineering is also now in progress. This will be the final release from the 4.x series and is mainly incremental bug fixes and a handful of feature additions. Of note is that the IBM ServeRAID 'IPS' driver is now supported on 4.x and will be included in this release, and the Linux emulation layer has been updated to support a RedHat 8.0 userland. The release is expected to be available on January 24. Looking forward, there will be several FreeBSD 5.x releases in the coming year. FreeBSD 5.4 release engineering will start in March, and FreeBSD 5.5 release engineering will likely start in June. These releases are expected to be more conservative than previous 5.x releases and will follow the same philosophy as previous -STABLE branches of fixing bugs and adding incremental improvements while maintaining API stability. For the 6-CURRENT development branch as well as all future development and stable branches, we are planning to move to a schedule with fixed timelines that move away from the uncertainty and wild schedule fluctuations of the previous 5.x releases. This means that major branches will happen at 18 month intervals, and releases from those branches will happen at 4 month intervals. There will also be a dedicated period of testing and bug fixing at the beginning of each branch before the first release is cut from that branch. With the shorter and more defined release schedules, we hope to lessen the problem of needed features not reaching users in a reasonable time, as happened too often with 5.x. This is a significant change in our strategy, and we look forward to realizing the benefits of it. This will kick off with the RELENG_6 branch happing in June of 2005, followed by the 6.0 release in August of 2005. Also on the roadmap is a plan to combine the live-iso disk2 and the install distributions of disk1 into a single disk which can be used for both installation and for recovery. 3rd party packages that currently reside on disc1 will be moved to a disk2 that will be dedicated to these packages. This move will allow us to deal with the ever growing size of packages and also provide more flexibility to vendors that wish to add their own packages to the releases. It also opens the door to more advanced installers being put in place of sysinstall. Anyone interested in helping with this is encouraged to contact us. _________________________________________________________________ FreeBSD Security Officer and Security Team URL: http://www.freebsd.org/security/ URL: http://www.freebsd.org/security/charter.html URL: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/staff -listing.html#STAFF-SECTEAM URL: http://vuxml.freebsd.org/ URL: http://cvsweb.freebsd.org/ports/security/portaudit/ Contact: Jacques Vidrine Contact: Security Officer Contact: Security Team During 2004, there were several notable changes and events related to the FreeBSD Security Officer role and Security Team. The charter for the Security Officer (SO) as approved by Core in 2002 was finally published on the web site. This document describes the mission, responsibilities, and authorities of the SO. (The current SO is Jacques Vidrine.) The SO is supported by a Deputy SO and the Security Team. In April, Chris Faulhaber resigned as Deputy SO and Dag-Erling Smorgrav was appointed in his place. Also during the year, the following team members resigned: Julian Elischer, Bill Fumerola, Daniel Harris, Trevor Johnson, Kris Kennaway, Mark Murray, Wes Peters, Bruce Simpson, and Bill Swingle; while the following became new members: Josef El-Rayes, Simon L. Nielsen, Colin Percival, and Tom Rhodes. A huge thanks is due to all past and current members! The current Security Team membership is published on the web site. With the release of FreeBSD 4.8, the SO began extended support for some FreeBSD releases and their corresponding security branches. "Early adopter" branches, such as FreeBSD 5.0 (RELENG_5_0), are supported for at least six months. "Normal" branches are supported for at least one year. "Extended" branches, such as FreeBSD 5.3 (RELENG_5_3), are supported for at least two years. The currently supported branches and their estimated "end of life" (EoL) dates are published on the FreeBSD Security Information web page. In 2004, four releases "expired": 4.7, 4.9, 5.1, and 5.2. With the releases of FreeBSD 4.10 and 5.3, the SO and the Release Engineering team extended the scope of security branches to incorporate critical bug fixes unrelated to security issues. Currently, separate Errata Notices are published for such fixes. In the future, Security Advisories and Errata Notices will be merged and handled uniformly. 17 Security Advisories were published in 2004, covering 8 issues specific to FreeBSD and 9 general issues. 2004 also saw the introduction of the Vulnerabilities and Exposures Markup Language (VuXML). VuXML is a markup language designed for the documentation of security issues within a single package collection. Over 325 security issues in the Ports Collection have been documented already in the FreeBSD Project's VuXML document by the Security Team and other committers. This document is currently maintained in the ports repository, path ports/security/vuxml/vuln.xml. The contents of the document are made available in a human-readable form at the FreeBSD VuXML web site. The "portaudit" tool can be used to audit your local system against the listed issues. Starting in November, the popular FreshPorts.org web site also tracks issues documented in VuXML. _________________________________________________________________ FreeBSD Source Repository Mirror for svn/svk URL: http://svn.clkao.org/svnweb/freebsd/ URL: http://svn.clkao.org/svnweb/freebsd/rss/fromcvs/branches/RELENG_5/ URL: http://svn.clkao.org/svnweb/freebsd/rss/fromcvs/trunk/ URL: http://svk.elixus.org/ Contact: Kao Chia-liang A public Subversion mirror of the FreeBSD repository is provided at svn://svn.clkao.org/freebsd/. This is intended for people who would like to try the svk distributed version control system. svk allows you to mirror the whole repository and commit when offline. It also provides history-sensitive branching, merging, and patches. Non-committers can easily maintain their own branch and track upstream changes while their patches are being reviewed. _________________________________________________________________ FreeBSD/arm status report URL: http://www.freebsd.org/platforms/arm Contact: Olivier Houchard FreeBSD/arm made some huge progress. It can boot multiuser, and run things like "make world" and perl on the IQ31244 board. It also now has support for various things, including DDB, KTR, ptrace and kernel modules. A patch is available for early gdb support, and the libpthread almost works. _________________________________________________________________ FreeSBIE Status Report URL: http://www.FreeSBIE.org URL: http://liste.gufi.org/mailman/listinfo/freesbie Contact: FreeSBIE Staff FreeSBIE is a Live-CD based on the FreeBSD Operating system, or even easier, a FreeBSD-based operating system that works directly from a CD, without touching your hard drive. On December, 6th, 2004, FreeSBIE Staff released FreeSBIE 1.1, based on FreeBSD 5.3-RELEASE. Some of the innovations are: a renewed series of scripts to support power users in the use of FreeSBIE 1.1, an installer to let users install FreeSBIE 1.1 on their hard drives, thus having a powerful operating system such as FreeBSD, but with all the personalizations FreeSBIE 1.1 carries, the presence of the best open source software, chosen and personalized, such as X.Org 6.7, XFCE 4.2RC1, Firefox 1.0 and Thunderbird 0.9.2. For a complete list of the included software, please consult: http://www.freesbie.org/doc/1.1/FreeSBIE-1.1-i386.pkg_info.txt At EuroBSDCon 2004 in Karlsruhe, Germany, people from the FreeSBIE staff gave a talk, deeping into FreeSBIE scripts implementation and use. Open tasks: 1. Translating website and documentation _________________________________________________________________ Funded FreeBSD kernel development URL: http://lists.freebsd.org/pipermail/freebsd-announce/2004-December/0009 71.html Contact: Poul-Henning Kamp A longish status report for the 6 months of funded development was posted on announce, rather than repeat it here, you can find it at the link provided. _________________________________________________________________ Hardware Notes URL: http://www.FreeBSD.org/releases/5.3R/hardware-i386.html URL: http://www.freebsd.org/relnotes/CURRENT/hardware/i386/article.html Contact: Simon L. Nielsen Contact: Christian Brueffer The FreeBSD Hardware Notes have been (mostly) converted to being directly generated from the driver manual pages. This makes it much simpler to maintain the Hardware Notes, so they should be more accurate. The Hardware Notes for FreeBSD 5.3 use this new system. _________________________________________________________________ i386 Interrupt Code & PCI Interrupt Routing Contact: John Baldwin The ACPI PCI link support code was reworked to work around some limitations in the previous implementation. The new version more closely matches the current non-ACPI $PIR link support. Enhancements include disabling unused link devices during boot and using a simpler and more reliable algorithm for choosing ISA IRQs for unrouted link devices. Support for using the local APIC timer to drive the kernel clocks instead of the ISA timer and i8254 clock is currently being worked on in the jhb_clock perforce branch. It is mostly complete and will probably hit the tree in the near future. By letting each CPU use its own private timer to drive the kernel clocks, the kernel no longer has to IPI all the other CPUs in the system every time a clock interrupt occurs. _________________________________________________________________ ifconfig Overhaul Contact: Sam Leffler The ifconfig program used to configure network interfaces was overhauled. Over the years ifconfig has grown into a complex and often contorted piece of software that is hard to understand and difficult to maintain. The primary motivation for this work was to enable minimal configurations (for embedded use) without changing the code and to support future additions in a modular way. Functionality is now broken out into separate files and operations are registered with the central ifconfig code base. Features are configured simply by specifying which code is to be included when building the program. In the future the plan is for ifconfig to auto-load functionality through dynamic libraries. This mechanism will allow, for example, third party software packages to provide kernel services and ifconfig add-on code without changing the base system. _________________________________________________________________ Improved Multibyte/Wide Character Support Contact: Tim Robbins Support for multibyte characters has been added to many more base system utilities, including basename, col, colcrt, colrm, column, fmt, look, nl, od, rev, sed, tr, and ul. As a result of changes to the C library (see below), most utilities that perform regular expression matching or pathname globbing now support multibyte characters in these aspects. The regular expression matching and pathname globbing routines in the C library have been improved and now recognize multibyte characters. Various performance improvements have been made to the wide character I/O functions. The obsolete 4.4BSD "rune" interface and UTF2 encoding have been removed from the 6-CURRENT branch. Work is progressing on implementations of the POSIX iconv and localedef interfaces for potential inclusion into the FreeBSD 6.0 release. _________________________________________________________________ kgi4BSD URL: http://www.freebsd.org/~nsouch/kgi4BSD URL: http://wiki.daemon.li/moin.cgi/KGI Contact: Nicholas Souchu The project was very quiet (but still alive!) and mostly dedicated to testing by volunteers. New documentation at http://wiki.daemon.li/moin.cgi/KGI . Open tasks: 1. Help improving the documentation _________________________________________________________________ Layer 2 PFIL_HOOKS URL: http://lists.freebsd.org/pipermail/cvs-all/2004-August/079811.html Contact: Andre Oppermann IPFW2 has been converted to use PFIL_HOOKS for the IP[46] in/output path. (See link.) Not converted yet is the Layer 2 Etherfilter functionality of IPFW2. It is still directly called from the ether_input/output and bridging code. Layer 2 PFIL_HOOKS provide a general abstraction for packet filters to hook into the Layer 2 packet path and filter or manipulate such packets. This makes it possible to use not only IPFW2 but also PF and others for Layer 2 filtering. _________________________________________________________________ Low-overhead performance monitoring for FreeBSD URL: http://people.freebsd.org/~jkoshy/projects/perf-measurement/ Contact: Joseph Koshy System-wide and process-virtual counting-mode performance monitoring counters are now supported for the AMD Athlon and Intel P4 CPUs. SMP works, but is prone to freezes. Immediate next steps include: (1) implementing the system-wide and process-virtual sampling modes, (2) debugging, (3) writing a test suite and (4) improving the project's documentation. _________________________________________________________________ Move ARP out of routing table URL: http://lists.freebsd.org/pipermail/freebsd-current/2004-April/026380.h tml Contact: Andre Oppermann Contact: Qing Li The ARP IP address to MAC address mapping does not belong into the routing table (FIB) as it is currently done. This will move it to its own hash based structure which will be instantiated per each 802.1 broadcast domain. With this change it is possible to have more than one interface in the same IP subnet and layer 2 broadcast domain. The ARP handling and the routing table will be quite a bit simplified afterwards. As an additional benefit full MAC address based accounting will be provided. Qing Li has become the driver and implementor of this project and is expected to post a first patch for comments shortly in February 2005. _________________________________________________________________ Network Stack Locking URL: http://www.freebsd.org/projects/netperf/ URL: http://www.watson.org/~robert/freebsd/netperf/ Contact: Robert Watson The netperf project is working to enhance the performance of the FreeBSD network stack. This work grew out of the SMPng Project, which moved the FreeBSD kernel from a "Giant Lock" to more fine-grained locking and multi-threading. SMPng offered both performance improvement and degradation for the network stack, improving parallelism and preemption, but substantially increasing per-packet processing costs. The netperf project is primarily focused on further improving parallelism in network processing while reducing the SMP synchronization overhead. This in turn will lead to higher processing throughput and lower processing latency. Tasks include completing the locking work, optimizing locking strategies, amortizing locking costs, introducing new synchronization primitives, adopting non-locking synchronization strategies, and improving opportunities for parallelism through additional threading. Between July, 2004, and December, 2004, the Netperf project did a great deal of work, for which there is room only to include limited information. Much more information is available by visiting the URLS above, including information on a variety of on-going activities. Accomplishments include: July, 2004: A variety of improvements to PCB locking in the IPv6 implementation; locking for the if_xl driver; socket locking for the NFS client; cleanup of the soreceive() code path including structural improvements, assertions, and locking fixes; cleanup of the IPX/SPX code in preparation for locking; additional locking and locking assertions for the TCP implementation; bug fixes for locking and memory allocation in raw IP; netatalk cleanup and locking merged to FreeBSD CVS ; locking for many netgraph nodes merged to FreeBSD CVS ; SLIP structural improvements; experimental locking for netatalk ifaddrs; BPF locking optimizations (merged); Giant assertions for VFS to check VFS/network stack boundaries; UNIX domain socket locking optimizations; expansion of lock order documentation in WITNESS, additional NFS server code running MPSAFE; pipe locking optimizations to improve pipe allocation performance; Giant no longer required for fstat on sockets and pipes (merged); Giant no longer required for socket and pipe file descriptor closes (merged); IFF_NEEDSGIANT interface flag added to support compatibility operation for unlocked device drivers (merged) ; merged accept filter locking to FreeBSD CVS; documented uidinfo locking strategy (merged); Giant use reduced in fcntl(). August, 2004: UMA KTR tracing (merged); UDP broadcast receive locking optimizations (merged); TCP locking cleanup and documentation; IPv6 inpcb locking, cleanup, and structural improvements; IPv6 inpcb locking merged to FreeBSD CVS ; KTR for systems calls added to i386; substantial optimizations of entropy harvesting synchronization (merged) ; callout(9) sampling converted to KTR (merged); inpcb socket option locking (merged); GIANT_REQUIRED removed from netatalk in FreeBSD CVS; merged ADAPTIVE_GIANT to FreeBSD CVS, resulting in substantial performance improvements in many kernel IPC-intensive benchmarks ; prepend room for link layer headers to the UDP header mbuf to avoid one allocation per UDP send (merged); a variety of UDP bug fixes (merged); additional network interfaces marked MPSAFE; UNIX domain socket locking reformulated to protect so_pcb pointers; MP_WATCHDOG, a facility to dedicate additional HTT logical CPUs as watchdog CPUs developed (merged) ; annotation of UNIX domain socket locking merged to FreeBSD CVS; kqueue locking developed and merged by John-Mark Gurney ; task list for netinet6 locking created; conditional locking relating to kqueues and socket buffers eliminated (merged); NFS server locking bugfixes (merged); in6_prefix code removed from netinet6 by George Neville-Neil, lowering the work load for netinet6 (merged); unused random tick code in netinet6 removed (merged); ng_tty, IPX, KAME IPSEC now declare dependence on Giant using compile-time declaration NET_NEEDS_GIANT("component") permitting the kernel to detect unsafe components and automatically acquire the Giant lock over network stack operation if needed (merged) ; additional locking optimizations for entropy code (merged); Giant disabled by default in the netperf development branch (merged). September, 2004: bugs fixed relating to Netgraph's use of the kernel linker while not holding Giant (merged); merged removal of Giant over the network stack by default to FreeBSD CVS ; races relating to netinet6 and if_afdata corrected (merged); annotation of possible races in the BPF code; BPF code converted to queue(3) (merged); race in sopoll() corrected (merged). October, 2004: IPv6 netisr marked as MPSAFE; TCP timers locked, annotated, and asserted (merged); IP socket option locking and cleanup (merged); Netgraph ISR marked MPSAFE; netatalk ISR marked MPSAFE (merged); some interface list locking cleanup (merged); use after free bug relating to entropy harvesting and ethernet fixed (merged); soclose()/sofree() race fixed (merged); IFF_LOCKGIANT() and IFF_UNLOCKGIANT() added to acquire Giant as needed when entering the ioctls of non-MPSAFE network interfaces. November, 2004: cleanup of UDPv6 static global variables (merged); FreeBSD 5.3 released! First release of FreeBSD with an MPSAFE and Giant-free network stack as the default configuration! ; additional TCP locking documentation and cleanup (merged); optimization to use file descriptor reference counts instead of socket reference counts for frequent operations results in substantial performance optimizations for high-volume send/receive (merged) ; an accept bug is fixed (merged) experimental network polling locking introduced; substantial measurement and optimization of mutex and locking primitives (merged) ; experimental modifications to UMA to use critical sections to protect per-CPU caches instead of mutexes yield substantial micro-benchmark benefits when combined with experimental critical section optimizations ; FreeBSD Project Netperf page launched; performance micro-benchmarks benchmarks reveal IP forwarding latency in 5.x is measurably better than 4.x on UP when combined with optional network stack direct dispatch; several NFS server locking bugfixes (merged); development of new mbufqueue primitives and substantial experimentation with them permits development of amortized cost locking APIs for handoff between the network stack and network device drivers (work in collaboration with Sandvine, Inc) ; Linux TCP_INFO API added to allow user-space monitoring of TCP state (merged); SMPng task list updated; UDP static/global fixes merged to RELENG_5. December, 2004: UDP static/global fixes developed for multi-threaded in-bound UDP processing (merged); socket buffer locking fixes for urgent TCP input processing (merged); lockless read optimizations for IF_DEQUEUE() and IF_DRAIN(); Giant-free close for sockets/pipes/... merged to FreeBSD CVS; optimize mass-dequeues of mbuf chains in netisr processing; netrate tool merged to RELENG_5; TCP locking fixes merged to RELENG_5; "show alllocks" added to DDB (merged); IPX locking bugfixes (merged); IPX/SPX __packed fixes (merged); IPX/SPX moved to queue(9) (merged); TCP locking fixes and annotations merged to FreeBSD CVS; IPX/SPX globals and pcb locking (merged); IPX/SPX marked MPSAFE (merged) ; IP socket options locking merged to FreeBSD; SPPP locked by Roman Kurakin (merged); UNIX domain socket locking fixes by Alan Cox (merged). On-going work continues with regard to locking down network stack components, including additional netinet6 locking, mbuf queue facilities and operations; benchmarking; moving to critical sections or per-CPU mutexes for UMA per-CPU caches; moving to critical sections or per-CPU mutexes for malloc(9) statistics; elimination of separate mbuf allocator statistics; additional interface locking; a broad variety of cleanups and documentation of locking; a broad range of optimizations. _________________________________________________________________ New DHCP Client Contact: Sam Leffler The OpenBSD dhcp client program has been ported and enhanced to listen for 802.11-related events from the kernel. This enables immediate IP address acquisition when roaming (as opposed to the polling done by the old code). The main change from the previous client is that there is one dhclient process per interface as opposed to one for the entire system. This necessitates changes to the system startup scripts. Incorporation into the base system is waiting on a volunteer who will shepherd the changes into the tree and deal with bugs. _________________________________________________________________ New Modular Input Device Layer URL: http://lists.freebsd.org/pipermail/cvs-src/2004-November/035462.html Contact: Philip Paeps Following a number of mailing lists discussions on the topic, work has been progressing on the development of a new modular input device layer for FreeBSD. The purpose of this is twofold: * Easier development of new input device drivers. * Support for concurrent use of multiple input devices, particularly the hot-pluggable kind. Currently, implementing support for new input devices is a painful process and there is great potential for code-duplication. The new input device layer will provide a simple API for developers to send events from their hardware on to the higher regions of the kernel in a consistent way, much like the 'input-core' driver in the Linux kernel. Using multiple input devices at the moment is painful at best. With the new input device layer, events from different devices will be properly serialized before they are sent to other parts of the kernel. This will allow one to easily use, for instance, multiple USB keyboards in a virtual terminal. The work on this is still in very rudimentary state. It is expected that the first visible changes will be committed to -CURRENT around late February or early March. _________________________________________________________________ OpenBSD packet filter - pf URL: http://pf4freebsd.love2party.net/ Contact: Max Laier Contact: Daniel Hartmeier FreeBSD 5.3 is the first release to include PF. It went out okay, but some bugs were discovered too late to make it on the CD. It is recommend to update `src/sys/contrib/pf' to RELENG_5. The specific issues addressed are: * Possible NULL-deref with user/group rules. * Crash with binat on dynamic interfaces. * Silent dropping of IPv6 packets with option headers. * Endless loops with `static-port' rules. Most of these issues were discovered by FreeBSD users and got fed back to OpenBSD. This is a prime example of open source at work. The Handbook's Firewall section was modified to mention PF as an alternative to IPFW and IPF. Open tasks: 1. Write more documentation/articles. 2. Write an IPFilter to PF migration guide/tool. _________________________________________________________________ OpenOffice.org port status URL: http://porting.openoffice.org/freebsd/ URL: http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/Free BSD/ URL: http://sourceforge.jp/projects/waooo/files/ Contact: Maho Nakata OpenOffice.org 2.0 status * OpenOffice.org 2.0 is planned to be released in March 2005. Currently developer snapshot versions are available. Now one of the developer version has been ported, and committed to ports tree (/usr/ports/editors/openoffice-2.0-devel). * Packages for 5.3-RELEASE are available at http://sourceforge.jp/projects/waooo/files/asOOo_1.9m71_FreeBSD53I ntel_install_en-US.tbz etc., and soon it will also available at : http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/ FreeBSD/ with the language pack. * Almost all of the patches required to build will be integrated to master. http://www.openoffice.org/issues/show_bug.cgi?id=40187 * Now we have three external ports : lang/gcc-ooo, devel/bison-devel and devel/epm. To avoid regressions and bugs of gcc, we use the exactly same gcc as Hamburg team (former StarDivision) uses. We need bison later than 1.785a. Note this port CONFLICTS with devel/bison. Epm is a package manager which now OpenOffice.org uses. OpenOffice.org 1.1 status * 1.1.4 has been ported and committed to ports tree. * Packages are available at http://ooomisc.services.openoffice.org/pub/OpenOffice.org/ooomisc/ FreeBSD/ . * Now recognizes Linux version of Java JDKs. General * Invoking OpenOffice.org from command line has been changed. Now `.org' is mandatory. e.g. openoffice-1.1.4 -> openoffice.org-1.1.4. Since the name of the software is OpenOffice.org, not OpenOffice. We are also considering the name of the ports (/usr/ports/editors/openoffice-2.0-devel -> openoffice.org2-devel etc) * Now marked as BROKEN OOo ports for prior than 5.3-RELEASE and 4.11-RELEASE. These ports have been suffering from a minor implementation difference of rtld.c between FreeBSD and Linux, Solaris, NetBSD. We have been applying a patch adding _end in mapfile. We need this since rtld depend on existence of _end symbol in obj_from_addr_end, unfortunately this seem to induce hard-to-solve errors. A great progress has been made kan, rtld now do not depend on _end. A fix was committed 2004/02/25 17:06:16, http://www.freebsd.org/cgi/cvsweb.cgi/src/libexec/rtld-elf/rtld.c. diff?r1=1.91&r2=1.92&f=h . * Benchmark test! Building OOo requires huge resources. We just would like to know the build timings, so that how your machine is well tuned for demanding jobs. http://porting.openoffice.org/freebsd/benchmark.html . Currently, GOTO daichi (daichi)'s Pentium 4 3.0GHz machine build fastest. Just 1h25m22.42s for second build of OOo 1.1.4, using ccache. * SDK tutorial is available at http://porting.openoffice.org/freebsd/sdk.html * Still implementation test and quality assurance have not yet been done. Even systematic documentations are not yet available for FreeBSD. http://porting.openoffice.org/freebsd/testing.html and http://porting.openoffice.org/freebsd/QA.html for details. Acknowledgments Two persons contributed in many aspects. Pavel Janik (reviewing and giving me much advice) and Kris Kennaway (extremely patient builder). and (then, alphabetical order by first name). daichi, Eric Bachard, kan, lofi, Martin Hollmichel, nork, obrien, Sander Vesik, sem, Stefan Taxhet, and volunteers of OpenOffice.org developers (esp. SUN Microsystems, Inc.) for cooperation and warm encouragements. _________________________________________________________________ Ports Collection URL: http://www.FreeBSD.org/ports/ URL: http://portsmon.firepipe.net/index.html Contact: Mark Linimon Contact: Erwin Lansing Since the last report on the Ports Collection, much has changed. Organizationally, the portmgr team saw the departure of some of the long-term members, and the addition of some newer members, Oliver Eikemeier, Kirill Ponomarew and Mark Linimon. Later on, portmgr also had to say goodbye to Will Andrews. In addition, we have gained quite a few new ports committers during this time period, and their contributions are quite welcome! Most effort was devoted to two releases. The 5.3 release saw an especially long freeze period, but due to the good shape of the ports tree, the freeze for the 4.11 could be kept to a minimum. Several iterations of new infrastructure changes were tested on the cluster and committed. Also, the cluster now builds packages for 6-CURRENT, increasing the total number of different build environment to 10. Additionally, several sweeps through the ports tree were made to bring more uniformity in variables used in the different ports and their values, e.g. BROKEN , IGNORE , DEPRECATED , USE_GCC , and and others. In technical terms, the largest change was moving to the X.org codebase as our default X11 implementation. At the same time, code was committed to be able to select either the X.org code or the XFree86 code, which also saw an update during that time. Due to some hard work by Eric Anholt, new committer Dejan Lesjak, and Joe Marcus Clarke, all of this happened more smoothly than could have reasonably been expected. As well, GNOME and KDE saw updates during this time, as did Perl and the Java framework. Further, there were some updates to the Porter's Handbook, but more sections are still in need of updates to include recent changes in practices. Also, during this time, Bill Fenner was able to fix a bug in his distfile survey . Shortly before the release for 4.11 our existing linux_base was marked forbidden due to security issues. A lot of effort was spent to upgrade the default version to 8 from 7 to ship 4.11 with a working linuxolator. Due to stability problems in the April-May timeframe, the package builds for the Alpha were dropped. After Ken Smith and others put some work into the Alphas in the build cluster, package builds for 4.X were reenabled late in 2004. Ports QA reminders -- portmgr team members are now sending out periodic email about problems in the Ports Collection. The current set includes: * a public list of all ports to be removed due to security problems, build failures, or general obsolescence, unless they are fixed first * private email to all maintainers of the affected ports (including ports dependent on the above) * private email to all maintainers of ports that are marked BROKEN and/or FORBIDDEN * private email to maintainers who aren't committers, who have PRs filed against their ports (to flag PRs that might never have been Cc:ed to them) * public email about port commits that break building of INDEX * public email about port commits that send the revision metadata backwards (and thus confuse tools like portupgrade) The idea behind each of these reminders is to try to increase the visibility of problems in the Ports Collection so that problems can be fixed faster. Finally, it should be noted that we passed yet another milestone and the Ports Collection now contains over 12,000 ports. Open tasks: 1. The majority of our build errors are still due to compilation problems, primarily from the gcc upgrades. Thanks to the efforts of many volunteers, these are decreasing, but there is still much more work to be done. 2. The next highest number of build errors are caused by code that does not build on our 64-bit architectures due to the assumption that "all the world's a PC." Here is the entire list ; the individual bars are clickable. This will become more and more important now that the amd64 port has been promoted to tier-1 status. 3. A lot of progress has been meed to crack down on ports that install files outside the approved directories and/or do not de-install cleanly (see "Extra files not listed in PLIST" on pointyhat ) and this will remain a focus area. _________________________________________________________________ PowerPC Port URL: http://www.freebsd.org/~grehan/miniinst.iso URL: http://www.freebsd.org/~grehan/miniinst.txt Contact: Peter Grehan A natively built 6.0-CURRENT miniinst ISO is available at the above link. It runs best on G4 Powermacs, but may run on other Newworld machines. See the release notes for full details. As usual, lots of help is needed. This is a great project for those who want to delve deeply into FreeBSD kernel internals. _________________________________________________________________ Project Frenzy (FreeBSD-based Live-CD) URL: http://frenzy.osdn.org.ua/ URL: http://frenzy.osdn.org.ua/eng/ Contact: Sergei Mozhaisky Frenzy is a "portable system administrator toolkit," Live-CD based on FreeBSD. It generally contains software for hardware tests, file system check, security check and network setup and analysis. Current version 0.3, based on FreeBSD 5.2.1-RELEASE, contains almost 400 applications in 200MB ISO-image. Tasks for next release: script for installation to HDD; unified system configuration tool; updating of software collection. _________________________________________________________________ Secure Updating URL: http://www.daemonology.net/portsnap/ URL: http://www.daemonology.net/freebsd-update/ Contact: Colin Percival In my continuing quest to secure the mechanisms by which FreeBSD users keep their systems up to date, I've added a new tool: Portsnap. Available as sysutils/portsnap in the ports tree, this utility securely downloads and updates a compressed snapshot of the ports tree; this can then be used to extract or update an uncompressed ports tree. In addition to operating in an end-to-end secure manner thanks to RSA signatures, portsnap operates entirely over HTTP and can use under one tenth of the bandwidth of cvsup for users who update their ports tree more than once a week. FreeBSD Update -- my utility for secure and efficient binary tracking of the Security/Errata branches -- continues to be widely used, with over 100 machines downloading security or errata updates daily. At some point in the future I intend to bring both of these utilities into the FreeBSD base system, probably starting with portsnap. _________________________________________________________________ SMPng Status Report URL: http://www.FreeBSD.org/smp/ Contact: John Baldwin Contact: Lots of changes happened inside the network stack that will hopefully be covered by a separate report. Outside of the network stack, several changes were made however including changes to proc locking, making the kernel thread scheduler preemptive, fixing several priority inversion bugs in the scheduler, and a few performance tweaks in the mutex implementation. Locking work on struct proc and its various substructures continued with locking added where needed for struct uprof, struct rusage, and struct pstats. This also included reworking how the kernel stores process time statistics to store the raw struct bintime and tick counts internally and only compute the more user friendly values when requested via getrusage() or wait4(). Support for kernel thread preemption was added to the scheduler. Basically, when a thread makes another thread runnable, it may yield the current CPU to the new thread if the new thread has a more important priority. Previously, only interrupt threads preempted other threads and the implementation would occasionally trigger spurious context switches. This change exposed bugs in other parts of the kernel and was turned off by default in RELENG_5. Currently, only the i386, amd64, and alpha platforms support native preemption. Several priority inversion bugs present in the scheduler due to various changes to the kernel from SMPng were also fixed. Most of the credit for these fixes belongs Stephan Uphoff who has recently been added as a new committer. Fixes include: closing a race in the turnstile wakeup code, changing the sleep queue code to store threads in FIFO order so that the sleep queue wakeup code properly handles having a thread's priority changes, and abstracting the concept of priority lending so that the thread scheduler is now able to properly track priority inheritance and handle priority changes for threads blocked on a turnstile. Works in progress include separating critical sections from spin mutexes some so that bare critical sections become very cheap as well as continuing to change the various ABI compatibility layers to use in-kernel versions of system calls to reduce stackgap usage and make the system call wrappers MPSAFE. _________________________________________________________________ Sync Protocols (SPPP and NETGRAPH) URL: http://www.freebsd.org/~rik Contact: Roman Kurakin sppp(4) was updated (in 6.current) to be able to work in mpsafe mode. For compatibility if an interface is unable to work in mpsafe mode, sppp will not use mpsafe locks. Support of FrameRelay AnnexD was added as a historical commit. Many of Cronyx users were expecting this commit for a long long time, and most of them still prefer sppp vs netgraph because of simplicity of its configuration (especially for ppp (vs mpd) and fr (vs a couple of netgraph modules). After MFCing this I'll finally close a PR 21771, from 2000/10/05 _________________________________________________________________ TCP Cleanup and Optimizations URL: http://people.freebsd.org/~andre/tcpcleanup.html Contact: Andre Oppermann The TCP code in FreeBSD has evolved significantly since the fork from 4.4BSD-Lite2 in 1994 primarily due to new features and refinements of the TCP specifications. The TCP code now needs a general overhaul, streamlining a cleanup to make it easily comprehensible, maintainable and extensible again. In addition there are many little optimizations that can be done during such an operation propelling FreeBSD back at the top of the best performing TCP/IP stacks again, a position it has held for the longest time in the 90's. This overhaul is a very involved and delicate matter and needs extensive formal and actual testing to ensure no regressions compared to the current code. The effort needed for this work is about two man-month of fully focused and dedicated time. To get it done I need funding to take time off my day job and to dedicate me to FreeBSD work much the way PHK did with his buffer cache and vnode rework projects. In February 2005 I will officially announce the funding request with a detailed description of the work and how the funding works. In general I can write invoices for companies wishing to sponsor this work on expenses. Tax exempt donations can probably be arranged through the FreeBSD foundation. Solicitations of money are already welcome, please contact me on the email address above. Open tasks: 1. Funding for two man-month equivalents of my time. 2. If you want or intend to sponsor US$1k or more please contact me in advance already now. _________________________________________________________________ TCP Reassembly Rewrite and Optimization URL: http://www.nrg4u.com/freebsd/tcp_reass-20041213.patch URL: http://lists.freebsd.org/pipermail/freebsd-net/2004-December/005918.ht ml Contact: Andre Oppermann Currently TCP segment reassembly is implemented as a linked list of segments. With today's high bandwidth links and large bandwidth*delay products this doesn't scale and perform well. The rewrite optimizes a large number of operational aspects of the segments reassembly process. For example it is very likely that the just arrived segment attaches to the end of the reassembly queue, so we check that first. Second we check if it is the missing segment or alternatively attaches to the start of the reassembly queue. Third consecutive segments are merged together (logically) and are skipped over in one jump for linear searches instead of each segment at a time. Further optimizations prototyped merge consecutive segments on the mbuf level instead of only logically. This is expected to give another significant performance gain. The new reassembly queue is tracking all holes in the queue and it may be beneficial to integrate this with the scratch pad of SACK in the future. Andrew Gallatin was able to get 3.7Gb/sec TCP performance on dual-2Gbit Myrinet cards with severe packet reordering (due to a firmware bug) with the new TCP reassembly code. See second link. _________________________________________________________________ The FreeBSD Dutch Documentation Team URL: http://www.evilcoder.org/content/section/6/39/ URL: http://www.FreeBSD.org/doc/nl/books/handbook/ URL: http://www.evilcoder.org/freebsd_html/ Contact: Remko Lodder The FreeBSD Dutch Documentation Project is a ongoing project to translate the documentation into the Dutch language. Currently we are mainly focused on the Handbook, which is progressing pretty well. However, lots need to be translated and checked before we have a 'complete' translation ready. So if you are willing to help out, please checkout our website and/or contact me. Open tasks: 1. Translating the Handbook 2. Checking the grammar of the Dutch Handbook 3. Translate the rest of the documentation _________________________________________________________________ TTCPv2: Transactional TCP version 2 URL: http://lists.freebsd.org/pipermail/cvs-all/2004-November/089939.html Contact: Andre Oppermann The old TTCP according to RFC1644 was insecure, intrusive, complicated and has been removed from FreeBSD >= 5.3. Although the idea and semantics behind it are still sound and valid. The rewrite uses a much easier and more secure system with 24bit long client and server cookies which are transported in the TCP options. Client cookies protect against various kinds of blind injection attacks and can be used as well to generally secure TCP sessions (for BGP for example). Server cookies are only exchanged during the SYN-SYN/ACK phase and allow a server to ensure that it has communicated with this particular client before. The first connection is always performing a 3WHS and assigning a server cookie to a client. Subsequent connections can send the cookie back to the server and short-cut the 3WHS to SYN->OPEN on the server. TTCPv2 is fully configurable per-socket via the setsockopt() system call. Clients and server not capable of TTCPv2 remain fully compatible and just continue using the normal 3WHS without any delay or other complications. Work on implementing TTCPv2 is done to 90% and expected to be available by early February 2005. Writing the implementation specification (RFC Draft) has just started. _________________________________________________________________ Update of the Linux userland infrastructure Contact: Alexander Leidinger The default linux_base port port was changed from the RedHat 7 based emulators/linux_base to the RedHat 8 based emulators/linux_base-8 just in time for FreeBSD 4.11-Release because of a security problem in emulators/linux_base. In the conversion process several problems where fixed in some Linux ports. Both RedHat 7 and 8 are at their end of life, so expect an update to a more recent Linux distribution in the future. For QA reasons this update wasn't scheduled before FreeBSD 4.11-Release. _________________________________________________________________ Wiki with new software URL: http://wikitest.freebsd.org/ Contact: Josef El-Rayes After experiencing spam attacks on the old wiki-engine caused by non-existent authentification mechanism, I had to replace it with a more advanced software. Instead of usemod, we now run moinmoin. As a consequence it's no longer just a 'browse & edit', but you have to sign up and let someone who is already in the ACL group 'developers' add you to the group. So it is a 'developers-only' resource now. The old wiki is found at http://wiki2.daemon.li Open tasks: 1. Move content from old wiki to new one. _________________________________________________________________ Wireless Networking Support Contact: Sam Leffler The wireless networking layer was updated to support the 802.1x, WPA, and 802.11i security protocols, and the WME/WMM multi-media protocol. As part of this work extensible frameworks were added for cryptographic methods, authentication, and access control. Extensions are implemented as loadable kernel modules that hook into the net80211 layer. This mechanism is used, for example, to implement WEP, TKIP, and CCMP crypto protocols. The Atheros driver (ath) is currently the only driver that uses the full set of features. Adding support to other drivers is simple but waiting on volunteers. Ports of the wpa_supplicant and hostapd programs enable use of the new security protocols. The support for tracking stations in a bss (managed or adhoc) and stations found when scanning was overhauled. Multiple tables are now used, each with different management policies, reference counting is now done consistently, and inactivity processing is done more intelligently (e.g. associated stations are probed before removal). This is the first step towards proper roaming support and other advanced features. AP power save support was added. Associated stations may now operate in power save mode; frames sent to them will be buffered while they are sleeping and multicast traffic will be deferred until after the next beacon (per the 802.11 protocol). Power save support is required in a standards-compliant access point. Only the ath driver currently implements power save support. Work is actively going on to add Atheros' SuperG capabilities, WDS, and for multi-bss support (ssid and/or bssid) on a single device. Open tasks: 1. Drivers other than ath need updates to support the new security protocols 2. hostapd needs work to support the IAPP and 802.11i preauthentication protocols (these are simple conversion of existing Linux code) _________________________________________________________________ Copyright 1995-2005 the FreeBSD Project. All rights reserved. --------------030205060202020502090801-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 12:42:54 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C14FE16A4CE; Mon, 17 Jan 2005 12:42:54 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F32F43D31; Mon, 17 Jan 2005 12:42:54 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id j0HCgrAj009766; Mon, 17 Jan 2005 07:42:53 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.1/8.13.1) with ESMTP id j0HCgqXM087116; Mon, 17 Jan 2005 07:42:52 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 0EA8A7306E; Mon, 17 Jan 2005 07:42:52 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050117124252.0EA8A7306E@freebsd-current.sentex.ca> Date: Mon, 17 Jan 2005 07:42:52 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/649/Sun Jan 2 18:02:22 2005 clamav-milter version 0.80j on clamscanner2 X-Virus-Status: Clean Subject: [current tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 12:42:55 -0000 TB --- 2005-01-17 10:56:45 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-01-17 10:56:45 - starting CURRENT tinderbox run for ia64/ia64 TB --- 2005-01-17 10:56:45 - checking out the source tree TB --- 2005-01-17 10:56:45 - cd /home/tinderbox/CURRENT/ia64/ia64 TB --- 2005-01-17 10:56:45 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-01-17 11:02:21 - building world (CFLAGS=-O2 -pipe) TB --- 2005-01-17 11:02:21 - cd /home/tinderbox/CURRENT/ia64/ia64/src TB --- 2005-01-17 11:02:21 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-01-17 12:33:17 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-01-17 12:33:17 - cd /home/tinderbox/CURRENT/ia64/ia64/src TB --- 2005-01-17 12:33:17 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Mon Jan 17 12:33:18 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c: In function `bus_dmamap_load_uio': /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c:784: warning: passing arg 1 of `_bus_dmamap_load_buffer' from incompatible pointer type /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c:784: warning: passing arg 2 of `_bus_dmamap_load_buffer' makes integer from pointer without a cast /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c:784: error: too many arguments to function `_bus_dmamap_load_buffer' /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c: In function `_bus_dmamap_load_buffer': /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c:496: error: prior parameter's size depends on 'map' /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c:496: error: prior parameter's size depends on 'map' /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c:514: confused by earlier errors, bailing out *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/obj/ia64/tinderbox/CURRENT/ia64/ia64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src. TB --- 2005-01-17 12:42:52 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-01-17 12:42:52 - ERROR: failed to build generic kernel TB --- 2005-01-17 12:42:52 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Jan 16 19:15:29 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 003E916A4CE for ; Sun, 16 Jan 2005 19:15:28 +0000 (GMT) Received: from h33.erkki.ton.tut.fi (h33.erkki.ton.tut.fi [193.166.84.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEAF743D1F for ; Sun, 16 Jan 2005 19:15:27 +0000 (GMT) (envelope-from chu@h33.erkki.ton.tut.fi) Received: from localhost (chu.h33.erkki.ton.tut.fi [10.10.1.242]) j0GJMcpB002446 for ; Sun, 16 Jan 2005 21:22:38 +0200 (EET) (envelope-from chu@h33.erkki.ton.tut.fi) Date: Sun, 16 Jan 2005 21:15:28 +0200 To: freebsd-current@freebsd.org From: "Vladimir Chukharev" Organization: @home Content-Type: text/plain; format=flowed; delsp=yes; charset=koi8-r MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: User-Agent: Opera M2/7.54u1 (FreeBSD, build 892) X-Mailman-Approved-At: Mon, 17 Jan 2005 12:59:02 +0000 Subject: Re: do YOU have one of these USB devices? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jan 2005 19:15:29 -0000 Julian Elischer wrote: > > If so, let me know if it crashes the system, or works > > (or just does nothing :-) ) > > Julian > > (working through the USB PRs) > of course forgot to include the devices.. > kensington mouse-in-a-box optical pro, > as seen in: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/32713 > or > "Logitech Wingman Digital 3D" > (product 0xc207 vendor 0x046d release 0x0104) > as seen in: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/30502 I have an Extreme version of the last. Not sure about the codes though. When I connect it to my notebook PC, I get these on the console: Jan 16 20:49:46 chu kernel: uhid0: Logitech Inc. WingMan Extreme Digital 3D, rev 1.00/1.04, addr 3, iclass 3/0 Jan 16 20:50:00 chu /usr/sbin/cron[61768]: (root) CMD (/usr/libexec/atrun) Jan 16 20:50:19 chu kernel: uhid0: at uhub0 port 1 (addr 3) disconnected Jan 16 20:50:19 chu kernel: uhid0: detached Jan 16 20:50:33 chu kernel: uhid0: Logitech Inc. WingMan Extreme Digital 3D, rev 1.00/1.04, addr 3, iclass 3/0 After a reboot with it connected, my dmesg is chu@chu:~ 20:58:57 $ dmesg Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #9: Mon Dec 20 20:53:04 EET 2004 root@chu.h33.erkki.ton.tut.fi:/usr/obj/usr/src/sys/CHU Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) M processor 1500MHz (1500.06-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x695 Stepping = 5 Features=0xa7e9fbbf real memory = 527695872 (503 MB) avail memory = 506720256 (483 MB) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) acpi_ec0: port 0x66,0x62 on acpi0 Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 cpu0: on acpi0 acpi_tz0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.1 (no driver attached) pci0: at device 0.3 (no driver attached) agp0: port 0xdc00-0xdc07 mem 0xfeb00000-0xfeb7ffff,0xf0000000-0xf7ffffff irq 11 at device 2.0 on pci0 agp0: detected 8060k stolen memory agp0: aperture size is 128M pci0: at device 2.1 (no driver attached) uhci0: port 0xd480-0xd49f irq 11 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhid0: Logitech Inc. WingMan Extreme Digital 3D, rev 1.00/1.04, addr 2, iclass 3/0 ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. uhci1: port 0xd800-0xd81f irq 5 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 0xd880-0xd89f irq 4 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: at device 29.7 (no driver attached) pcib1: at device 30.0 on pci0 pci1: on pcib1 pci1: at device 4.0 (no driver attached) cbb0: at device 5.0 on pci1 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 fwohci0: mem 0xfe8ff000-0xfe8ff7ff irq 11 at device 5.1 on pci1 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:e0:18:00:03:18:13:e4 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:e0:18:18:13:e4 fwe0: Ethernet address: 02:e0:18:18:13:e4 fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) fxp0: port 0xcc00-0xcc3f mem 0xfe8fe000-0xfe8fefff irq 11 at device 8.0 on pci1 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:0e:a6:8e:a9:ae isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 31.5 (no driver attached) pci0: at device 31.6 (no driver attached) acpi_button0: on acpi0 acpi_lid0: on acpi0 acpi_acad0: on acpi0 acpi_cmbat0: on acpi0 acpi_cmbat1: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 sio0: configured irq 3 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 port 0x2f8-0x2ff irq 3 drq 1 flags 0x10 on acpi0 sio0: type 16550A ppc0: port 0x778-0x77f,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: at iomem 0xc0000-0xccfff on isa0 pmtimer0 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 1500058241 Hz quality 800 Timecounters tick every 10.000 msec acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% ad0: 57231MB [116280/16/63] at ata0-master UDMA100 acd0: DVDR at ata1-master UDMA33 Mounting root from ufs:/dev/ad0s2a pcm0: port 0xe100-0xe13f,0xe000-0xe0ff at device 31.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: iwi0: mem 0xfe8fd000-0xfe8fdfff irq 4 at device 4.0 on pci1 iwi0: Ethernet address: 00:0e:35:1a:84:71 iwi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps iwi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps chu@chu:~ 21:01:58 $ All action by the joystick result in nothing. Is there any game or other program which uses the joystick? What else can I check about it? Best regards, -- V.Chukharev From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 13:59:59 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EC9016A4CE for ; Mon, 17 Jan 2005 13:59:59 +0000 (GMT) Received: from mail.iinet.net.au (mail-05.iinet.net.au [203.59.3.37]) by mx1.FreeBSD.org (Postfix) with SMTP id E79E743D58 for ; Mon, 17 Jan 2005 13:59:55 +0000 (GMT) (envelope-from shinjii@virusinfo.rdksupportinc.com) Received: (qmail 26381 invoked from network); 17 Jan 2005 13:59:54 -0000 Received: from unknown (HELO ?10.100.6.10?) (203.206.228.76) by mail.iinet.net.au with SMTP; 17 Jan 2005 13:59:54 -0000 From: Warren To: freebsd-current@freebsd.org Date: Mon, 17 Jan 2005 23:58:13 +1000 User-Agent: KMail/1.7.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501172358.13311.shinjii@virusinfo.rdksupportinc.com> Subject: Qtorrent X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 13:59:59 -0000 Has anyone else noticed that QTorrent now refuses to connect to any Torrent Tracker ? If i could get some sort of Bug reports i send it in, but since GDB dosent like it and the program runs fine untill you want to use it to d/l anything using as torrent i mnot sure how to find out whats happening. -- Yours Sincerely Shinjii http://www.shinji.nq.nu From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 14:42:25 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E959C16A4CE for ; Mon, 17 Jan 2005 14:42:25 +0000 (GMT) Received: from mail-gw1.york.ac.uk (mail-gw1.york.ac.uk [144.32.128.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB09E43D48 for ; Mon, 17 Jan 2005 14:42:24 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy.york.ac.uk [144.32.226.160]) by mail-gw1.york.ac.uk (8.12.10/8.12.10) with ESMTP id j0HEgK9F003005; Mon, 17 Jan 2005 14:42:20 GMT Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.1/8.13.1) with ESMTP id j0HEgKkj011495; Mon, 17 Jan 2005 14:42:20 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.1/8.13.1/Submit) id j0HEgJlI011494; Mon, 17 Jan 2005 14:42:19 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: Kris Maglione In-Reply-To: <41E984AB.7060205@comcast.net> References: <41E984AB.7060205@comcast.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Mon, 17 Jan 2005 14:42:19 +0000 Message-Id: <1105972939.10350.25.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk cc: freebsd-current@freebsd.org Subject: Re: Laptop won't boot -CURRENT after 8/04 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 14:42:26 -0000 On Sat, 2005-01-15 at 16:01 -0500, Kris Maglione wrote: > I am in the process of narrowing down the exact date that it stops > booting, but my laptop won't boot any stable past an early BETA of 5.3 > and it won't boot with -CURRENT from sometime in late 8/04. The latest > date I tried was 1/14/05, I believe. The boot stops after detecting acd0 > (cdrw/dvd-rom). In verbose mode, it stops at: > GEOM: Configure ad0s1 start ... length ... end ... > GEOM: Configure ad0s2[a-f] start ... length ... end ... > > The laptop doesn't have a serial port, and I've been testing with a > FreesBIE CD, since the laptop has a slow HD, so I can't post the entire > dmesg, though I can type out anything important. Hanging here often relates to floppy drive or floppy disk related issues. Late August corresponds to the GEOMification of the floppy device. Try setting debug.fdc.debugflags=255 from the loader, then posting the bits of the dmesg relating to the floppy drive. If it looks like it is getting stuck in the floppy probe, try applying the patch at http://www.devrandom.co.uk/freebsd/fdc_debug.c to an up-to-date current tree and replying with the output. > Can someone post an easy way to find all CVS changes between two dates? > That would be extremely helpful in narrowing the source of the problem. It's quite easy if you have a local CVS repository. (It should also be possible against the FreeBSD anoncvs server). Something like the following: cd /var/tmp cvs co src/sys cvs -q diff -u -D 2003-10-20 -D 2003-11-20 src/sys Will check out the current source then compare all files within src/sys between October 20th and November 20th. Gavin From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 14:54:28 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C48516A4CE for ; Mon, 17 Jan 2005 14:54:28 +0000 (GMT) Received: from mail.bluetone.cz (ns1.bluetone.cz [212.158.128.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id C855D43D45 for ; Mon, 17 Jan 2005 14:54:27 +0000 (GMT) (envelope-from varga@stonehenge.sk) Received: from [192.168.0.103] (angel2-153-99-82-tvpm.bluetone.cz [82.99.153.2]) by mail.bluetone.cz (Postfix) with ESMTP id 62EAE1A66A5 for ; Mon, 17 Jan 2005 15:54:25 +0100 (CET) From: Michal Varga To: freebsd-current@freebsd.org Content-Type: text/plain Organization: Stonehenge Date: Mon, 17 Jan 2005 15:51:59 +0100 Message-Id: <1105973519.29213.89.camel@andrasta.4net.local> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: FlashMX now freezing under wine-20050111 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 14:54:28 -0000 Hi folks, is there anyone still running FlashMX after [port]upgrade from wine-20041201 to wine-20050111? I have two recent -current workstations where FlashMX now freezes right after start, before (or during) the splash screen is drawn (visible window borders). No configuration changes between 20041201 and 20050111 made. Setting up clean wine environment from scratch also solves nothing. Is this just me, or there are others experiencing this? m. -- Michal Varga Stonehenge From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 15:57:32 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7ED1116A4CE for ; Mon, 17 Jan 2005 15:57:32 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E46643D39 for ; Mon, 17 Jan 2005 15:57:32 +0000 (GMT) (envelope-from bsdaemon@comcast.net) Received: from fw.home (pcp05404374pcs.norstn01.pa.comcast.net[68.80.144.252]) by comcast.net (sccrmhc12) with SMTP id <20050117155711012000pn2re>; Mon, 17 Jan 2005 15:57:11 +0000 Received: (qmail 36043 invoked from network); 17 Jan 2005 15:57:20 -0000 Received: from kris.home (HELO ?192.168.0.251?) (192.168.0.251) by fw.home with SMTP; 17 Jan 2005 15:57:20 -0000 Message-ID: <41EBE1A0.8090001@comcast.net> Date: Mon, 17 Jan 2005 11:02:41 -0500 From: Kris Maglione User-Agent: Mozilla Thunderbird 1.0 (X11/20041212) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <41E984AB.7060205@comcast.net> <1105972939.10350.25.camel@buffy.york.ac.uk> In-Reply-To: <1105972939.10350.25.camel@buffy.york.ac.uk> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigCE6FA9C5E6B24C37D305CF55" Subject: Re: Laptop won't boot -CURRENT after 8/04 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 15:57:32 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigCE6FA9C5E6B24C37D305CF55 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Gavin Atkinson wrote: >On Sat, 2005-01-15 at 16:01 -0500, Kris Maglione wrote: > > >>I am in the process of narrowing down the exact date that it stops >>booting, but my laptop won't boot any stable past an early BETA of 5.3 >>and it won't boot with -CURRENT from sometime in late 8/04. The latest >>date I tried was 1/14/05, I believe. The boot stops after detecting acd0 >>(cdrw/dvd-rom). In verbose mode, it stops at: >>GEOM: Configure ad0s1 start ... length ... end ... >>GEOM: Configure ad0s2[a-f] start ... length ... end ... >> >>The laptop doesn't have a serial port, and I've been testing with a >>FreesBIE CD, since the laptop has a slow HD, so I can't post the entire >>dmesg, though I can type out anything important. >> >> > >Hanging here often relates to floppy drive or floppy disk related >issues. Late August corresponds to the GEOMification of the floppy >device. > >Try setting debug.fdc.debugflags=255 from the loader, then posting the >bits of the dmesg relating to the floppy drive. If it looks like it is >getting stuck in the floppy probe, try applying the patch at >http://www.devrandom.co.uk/freebsd/fdc_debug.c to an up-to-date current >tree and replying with the output. > > I read about the possible relation to a floppy, so I compiled without fdc support (my laptop doesn't have one anyway), though I still had the problem. I found one problem, there's another, though. I have one configuration file that will boot and one that won't. I haven't found what causes it yet, although the file that will boot is far less than optimal. > > >>Can someone post an easy way to find all CVS changes between two dates? >>That would be extremely helpful in narrowing the source of the problem. >> >> > >It's quite easy if you have a local CVS repository. (It should also be >possible against the FreeBSD anoncvs server). > >Something like the following: > >cd /var/tmp >cvs co src/sys >cvs -q diff -u -D 2003-10-20 -D 2003-11-20 src/sys > >Will check out the current source then compare all files within src/sys >between October 20th and November 20th. > > Thanks, I figured that out already, although I used rdiff. I do have a local copy of the repository. --------------enigCE6FA9C5E6B24C37D305CF55 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB6+GkmcXjc1XBrAQRAlHmAKCCMkt3JCuOKYe/WetXkOMO9tkd+QCfXZfe EuhPPzGDgGI+USlv1s9UVtM= =nTa+ -----END PGP SIGNATURE----- --------------enigCE6FA9C5E6B24C37D305CF55-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 16:01:35 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D215116A4CE; Mon, 17 Jan 2005 16:01:35 +0000 (GMT) Received: from elrond.anembo.nu.org (dsl-202-173-130-73.nsw.westnet.com.au [202.173.130.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC6BE43D2F; Mon, 17 Jan 2005 16:01:33 +0000 (GMT) (envelope-from cjsv@elrond.anembo.nu.org) Received: from elrond.anembo.nu.org (localhost [127.0.0.1]) by elrond (8.13.1/8.13.1) with ESMTP id j0H3Mvvj002376; Mon, 17 Jan 2005 14:22:57 +1100 (EST) (envelope-from cjsv@elrond.anembo.nu.org) Received: (from cjsv@localhost) by elrond.anembo.nu.org (8.13.1/8.13.1/Submit) id j0H3MtlY002375; Mon, 17 Jan 2005 14:22:55 +1100 (EST) (envelope-from cjsv) Date: Mon, 17 Jan 2005 14:22:55 +1100 From: Christopher Vance To: David Yu Message-ID: <20050117032255.GC630@nu.org> References: <20050117020039.GB630@nu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: cc: freebsd-fs@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: NTFS unicode converting problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 16:01:36 -0000 On Sun, Jan 16, 2005 at 06:25:52PM -0800, David Yu wrote: >In my case, those Chinese filenames are still in UCS-2LE, and all >characters are in plane 0. I tried to modify codes so that it can >directly store the conversion result into the dirent structure, but >the convchr() funtion failed everytime for Chinese character while >there is no problem with Ascii characters. I thought converting from >UCS-2 to UTF-8 should be very easy? Maybe the conversion routine disagrees with you about byte order? -- Christopher Vance From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 17:42:16 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3DE2816A4CE for ; Mon, 17 Jan 2005 17:42:16 +0000 (GMT) Received: from shim2.irt.drexel.edu (shim2.irt.drexel.edu [144.118.29.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEB2843D46 for ; Mon, 17 Jan 2005 17:42:15 +0000 (GMT) (envelope-from jsmith@drexel.edu) Received: from conversion-daemon.shim2.irt.drexel.edu by shim2.irt.drexel.edu (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) freebsd-current@freebsd.org; Mon, 17 Jan 2005 12:42:15 -0500 (EST) Received: from vorpal.math.drexel.edu (vorpal.math.drexel.edu [129.25.6.250]) by shim2.irt.drexel.edu (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0IAH00B4Q2IEP3@shim2.irt.drexel.edu> for freebsd-current@freebsd.org; Mon, 17 Jan 2005 12:42:15 -0500 (EST) Received: from [IPv6:::1] (vorpal.math.drexel.edu [129.25.6.250]) j0HHcdsL001751 for ; Mon, 17 Jan 2005 12:38:40 -0500 (EST envelope-from jsmith@drexel.edu) Date: Mon, 17 Jan 2005 12:40:51 -0500 From: "Justin R. Smith" To: freebsd-current@freebsd.org Message-id: <41EBF8A3.5030009@drexel.edu> Organization: Drexel University MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0 (X11/20041228) X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Subject: Sound doesn't work X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 17:42:16 -0000 My profile: FreeBSD jsmith.org 5.3-STABLE FreeBSD 5.3-STABLE #0: Mon Jan 17 11:14:19 EST 2005 jsmith@jsmith.org:/usr/obj/usr/src/sys/MYKERNEL i386 Sound worked perfectly in 5.3-release. After upgrading to the stable release, it stopped working. Output of sndstat (with maximum verbosity): FreeBSD Audio Driver (newpcm) Installed devices: pcm0: at io 0xa800 irq 17 kld snd_cmi (1p/1r/0v channels duplex default) [pcm0:play:0]: spd 44100, fmt 0x10000010, flags 0x00000000, 0x00000000 interrupts 0, underruns 0, ready 0 {userland} -> feeder_root(0x10000010) -> {hardware} [pcm0:record:0]: spd 0, fmt 0x00000000/0x00000008, flags 0x00000000, 0x00000000 interrupts 0, overruns 0, hfree 16384, sfree 0 {hardware} -> feeder_root(0x00000000) -> {userland} File Versions: $FreeBSD: src/sys/dev/sound/pci/cmi.c,v 1.29 2004/07/16 03:59:27 tanimura Exp $ $FreeBSD: src/sys/dev/sound/isa/sndbuf_dma.c,v 1.2 2003/09/07 16:28:02 cg Exp $ $FreeBSD: src/sys/dev/sound/pcm/vchan.c,v 1.16 2004/01/28 08:02:15 truckman Exp $ $FreeBSD: src/sys/dev/sound/pcm/sound.c,v 1.92 2004/07/16 03:59:09 tanimura Exp $ $FreeBSD: src/sys/dev/sound/pcm/sndstat.c,v 1.17.2.1 2004/09/14 06:43:46 truckma n Exp $ $FreeBSD: src/sys/dev/sound/pcm/mixer.c,v 1.40 2004/06/25 16:34:33 josef Exp $ $FreeBSD: src/sys/dev/sound/pcm/feeder_rate.c,v 1.10 2003/04/20 17:08:56 orion E xp $ $FreeBSD: src/sys/dev/sound/pcm/feeder_fmt.c,v 1.13 2003/09/07 16:28:03 cg Exp $ $FreeBSD: src/sys/dev/sound/pcm/feeder.c,v 1.32 2003/09/07 16:28:03 cg Exp $ $FreeBSD: src/sys/dev/sound/pcm/fake.c,v 1.13 2003/09/07 16:28:03 cg Exp $ $FreeBSD: src/sys/dev/sound/pcm/dsp.c,v 1.77 2004/07/02 15:31:44 netchild Exp $ $FreeBSD: src/sys/dev/sound/pcm/channel.c,v 1.97 2004/02/28 19:47:02 truckman Ex p $ $FreeBSD: src/sys/dev/sound/pcm/buffer.c,v 1.23.2.1 2004/11/23 07:13:33 yongari Exp $ $FreeBSD: src/sys/dev/sound/pcm/ac97_patch.c,v 1.2 2003/08/21 15:44:55 orion Exp $ $FreeBSD: src/sys/dev/sound/pcm/ac97.c,v 1.51 2004/05/08 03:41:40 sanpei Exp $ --------------------------------------------------------------------------------------------- It looks as though the system identifies the device, but no actual sound comes out of the speakers. (Sound continues to work fine in Windoze). Any suggestions? From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 17:49:44 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BCE1116A4CE for ; Mon, 17 Jan 2005 17:49:44 +0000 (GMT) Received: from makeworld.com (makeworld.com [198.92.228.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87F0343D3F for ; Mon, 17 Jan 2005 17:49:43 +0000 (GMT) (envelope-from racerx@makeworld.com) Received: from localhost (localhost.com [127.0.0.1]) by makeworld.com (Postfix) with ESMTP id 2D50A6128; Mon, 17 Jan 2005 11:49:39 -0600 (CST) Received: from makeworld.com ([127.0.0.1]) by localhost (makeworld.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 55483-04; Mon, 17 Jan 2005 11:49:34 -0600 (CST) Received: from [127.0.0.1] (unknown [63.117.97.221]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by makeworld.com (Postfix) with ESMTP id 5E57660EA; Mon, 17 Jan 2005 11:49:10 -0600 (CST) Message-ID: <41EBFA86.6060502@makeworld.com> Date: Mon, 17 Jan 2005 11:48:54 -0600 From: Chris User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Justin R. Smith" References: <41EBF8A3.5030009@drexel.edu> In-Reply-To: <41EBF8A3.5030009@drexel.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by ClamAV 0.75.1/amavisd-new-2.2.1 (20041222) at makeworld.com - Isn't it ironic cc: freebsd-current@freebsd.org Subject: Re: Sound doesn't work X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 17:49:44 -0000 Justin R. Smith wrote: > My profile: > > FreeBSD jsmith.org 5.3-STABLE FreeBSD 5.3-STABLE #0: Mon Jan 17 > 11:14:19 EST 2005 jsmith@jsmith.org:/usr/obj/usr/src/sys/MYKERNEL > i386 > > > Sound worked perfectly in 5.3-release. After upgrading to the stable > release, it stopped working. > > Output of sndstat (with maximum verbosity): > > FreeBSD Audio Driver (newpcm) > Installed devices: > pcm0: at io 0xa800 irq 17 kld snd_cmi (1p/1r/0v > channels duplex > default) > [pcm0:play:0]: spd 44100, fmt 0x10000010, flags 0x00000000, > 0x00000000 > interrupts 0, underruns 0, ready 0 > {userland} -> feeder_root(0x10000010) -> {hardware} > [pcm0:record:0]: spd 0, fmt 0x00000000/0x00000008, flags > 0x00000000, 0x00000000 > interrupts 0, overruns 0, hfree 16384, sfree 0 > {hardware} -> feeder_root(0x00000000) -> {userland} > > File Versions: > $FreeBSD: src/sys/dev/sound/pci/cmi.c,v 1.29 2004/07/16 03:59:27 > tanimura Exp $ > $FreeBSD: src/sys/dev/sound/isa/sndbuf_dma.c,v 1.2 2003/09/07 16:28:02 > cg Exp $ > $FreeBSD: src/sys/dev/sound/pcm/vchan.c,v 1.16 2004/01/28 08:02:15 > truckman Exp > $ > $FreeBSD: src/sys/dev/sound/pcm/sound.c,v 1.92 2004/07/16 03:59:09 > tanimura Exp > $ > $FreeBSD: src/sys/dev/sound/pcm/sndstat.c,v 1.17.2.1 2004/09/14 > 06:43:46 truckma > n Exp $ > $FreeBSD: src/sys/dev/sound/pcm/mixer.c,v 1.40 2004/06/25 16:34:33 > josef Exp $ > $FreeBSD: src/sys/dev/sound/pcm/feeder_rate.c,v 1.10 2003/04/20 > 17:08:56 orion E > xp $ > $FreeBSD: src/sys/dev/sound/pcm/feeder_fmt.c,v 1.13 2003/09/07 > 16:28:03 cg Exp $ > $FreeBSD: src/sys/dev/sound/pcm/feeder.c,v 1.32 2003/09/07 16:28:03 cg > Exp $ > $FreeBSD: src/sys/dev/sound/pcm/fake.c,v 1.13 2003/09/07 16:28:03 cg > Exp $ > $FreeBSD: src/sys/dev/sound/pcm/dsp.c,v 1.77 2004/07/02 15:31:44 > netchild Exp $ > $FreeBSD: src/sys/dev/sound/pcm/channel.c,v 1.97 2004/02/28 19:47:02 > truckman Ex > p $ > $FreeBSD: src/sys/dev/sound/pcm/buffer.c,v 1.23.2.1 2004/11/23 > 07:13:33 yongari > Exp $ > $FreeBSD: src/sys/dev/sound/pcm/ac97_patch.c,v 1.2 2003/08/21 15:44:55 > orion Exp > $ > $FreeBSD: src/sys/dev/sound/pcm/ac97.c,v 1.51 2004/05/08 03:41:40 > sanpei Exp $ > --------------------------------------------------------------------------------------------- > > > It looks as though the system identifies the device, but no actual > sound comes out of the speakers. (Sound continues to work fine in > Windoze). > > Any suggestions? One of two things - 1. compile sound back into your kernel 2. Install sound as a module from bootup -- Best regards, Chris PGP Fingerprint = D976 2575 D0B4 E4B0 45CC AA09 0F93 FF80 C01B C363 From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 17:59:32 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1439116A4CE for ; Mon, 17 Jan 2005 17:59:32 +0000 (GMT) Received: from smtp-out.hotpop.com (smtp-out.hotpop.com [38.113.3.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B49A43D39 for ; Mon, 17 Jan 2005 17:59:31 +0000 (GMT) (envelope-from bitchat@hotpop.com) Received: from hotpop.com (kubrick.hotpop.com [38.113.3.103]) by smtp-out.hotpop.com (Postfix) with SMTP id 1B5E0134F605 for ; Mon, 17 Jan 2005 17:59:25 +0000 (UTC) Received: from [10.1.1.7] (c90618ac.virtua.com.br [201.6.24.172]) by smtp-1.hotpop.com (Postfix) with ESMTP id BC40A1A012D for ; Mon, 17 Jan 2005 17:59:21 +0000 (UTC) From: "Adolfo B. Ferreira" To: current@freebsd.org Date: Mon, 17 Jan 2005 15:55:08 -0200 Message-Id: <1105984508.950.7.camel@notebook> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 X-HotPOP: ----------------------------------------------- Sent By HotPOP.com FREE Email Get your FREE POP email at www.HotPOP.com ----------------------------------------------- Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Maildrop X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 17:59:32 -0000 Hello Folks, Could some one help me with maildrop? I'm using FreeBSD 5.3 with all updated from CVS. I'm trying to use maildrop with MYSQL and QUOTA but maildrop is not connecting in MySQL. I installed maildrop with cd /usr/ports/mail/maildrop make deinstall distclean WITH_MAILDIRQUOTA=yes WITH_TRASHQUOTA=yes WITH_MYSQL=yes install clean then i typed rehash and maildrop -v maildrop 1.6.3 Copyright 1998-2003 Double Precision, Inc. Maildir quota extension enabled. Virtual user database via MySQL extension enabled. This program is distributed under the terms of the GNU General Public License. See COPYING for additional information. When I try to run maildrop with echo "test" | maildrop -V 5 -d adolfo@anderung.com.br I got: Invalid user specified. but when I try with echo "test" | maildrop -V 5 -d root maildrop: Changing to /root Message start at 0 bytes, envelope sender=root /usr/local/etc/maildrop/maildroprc(1): Opening logfile /var/log/maildrop.log maildrop: Attempting .mailfilter maildrop: Delivering to /var/mail/root maildrop: Appending to /var/mail/root. maildrop: Delivery complete. So what I could understand is that maildrop is delivering only for users from /etc/passwd. My maildropmysql.config is located in /usr/locall/etc/maildrop/maildropmysql.config and I set it in Makefile of maildrop port. anderung# cat maildropmysql.config hostname localhost port 3306 socket /tmp/mysql.sock database postfix dbuser DBUSER dbpw DBPASSWD dbtable mailbox uid_field username uidnumber_field uid gidnumber_field gid maildir_field maildir homedirectory_field home quota_field quota mailstatus_field active where_clause AND active = '1' I have the user in the mailbox mysql table and the dbuser and dbpasswd is correct. What am I doing wrong with maildrop? Thanks for all, Adolfo Bravo Ferreira Admninistrador de Redes / Analista de Seguranчa / Desenvolvedor Grupo Ferreira Limitada Telefone: 11 50628877 From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 18:00:22 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E59AB16A4CE for ; Mon, 17 Jan 2005 18:00:22 +0000 (GMT) Received: from shim1.irt.drexel.edu (shim1.irt.drexel.edu [144.118.29.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83E6143D4C for ; Mon, 17 Jan 2005 18:00:22 +0000 (GMT) (envelope-from jsmith@drexel.edu) Received: from conversion-daemon.shim1.irt.drexel.edu by shim1.irt.drexel.edu (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) freebsd-current@freebsd.org; Mon, 17 Jan 2005 13:00:21 -0500 (EST) Received: from vorpal.math.drexel.edu (vorpal.math.drexel.edu [129.25.6.250]) by shim1.irt.drexel.edu (iPlanet Messaging Server 5.2 HotFix 1.17 (built Jun 23 2003)) with ESMTP id <0IAH0082M3CJLG@shim1.irt.drexel.edu> for freebsd-current@freebsd.org; Mon, 17 Jan 2005 13:00:19 -0500 (EST) Received: from [IPv6:::1] (vorpal.math.drexel.edu [129.25.6.250]) j0HHuiLU001796 for ; Mon, 17 Jan 2005 12:56:45 -0500 (EST envelope-from jsmith@drexel.edu) Date: Mon, 17 Jan 2005 12:58:56 -0500 From: "Justin R. Smith" To: freebsd-current@freebsd.org Message-id: <41EBFCE0.5050907@drexel.edu> Organization: Drexel University MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0 (X11/20041228) X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Subject: Re: Sound doesn't work X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 18:00:23 -0000 My loader.conf has sound_load="YES" snd_driver_load="YES" Isn't this enough? From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 18:03:10 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D72C816A4CE for ; Mon, 17 Jan 2005 18:03:10 +0000 (GMT) Received: from makeworld.com (makeworld.com [198.92.228.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 221FE43D48 for ; Mon, 17 Jan 2005 18:03:10 +0000 (GMT) (envelope-from racerx@makeworld.com) Received: from localhost (localhost.com [127.0.0.1]) by makeworld.com (Postfix) with ESMTP id 89D5D6128; Mon, 17 Jan 2005 12:03:07 -0600 (CST) Received: from makeworld.com ([127.0.0.1]) by localhost (makeworld.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 55483-07; Mon, 17 Jan 2005 12:03:05 -0600 (CST) Received: from [127.0.0.1] (unknown [63.117.97.221]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by makeworld.com (Postfix) with ESMTP id C2ED560EA; Mon, 17 Jan 2005 12:03:00 -0600 (CST) Message-ID: <41EBFDD1.5010700@makeworld.com> Date: Mon, 17 Jan 2005 12:02:57 -0600 From: Chris User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Justin R. Smith" References: <41EBFCE0.5050907@drexel.edu> In-Reply-To: <41EBFCE0.5050907@drexel.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by ClamAV 0.75.1/amavisd-new-2.2.1 (20041222) at makeworld.com - Isn't it ironic cc: freebsd-current@freebsd.org Subject: Re: Sound doesn't work X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 18:03:11 -0000 Justin R. Smith wrote: > My loader.conf has > > sound_load="YES" > snd_driver_load="YES" > > Isn't this enough? Well yes however, why are you loading ALL the drivers? -- Best regards, Chris PGP Fingerprint = D976 2575 D0B4 E4B0 45CC AA09 0F93 FF80 C01B C363 From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 18:05:08 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD60216A4CF for ; Mon, 17 Jan 2005 18:05:07 +0000 (GMT) Received: from makeworld.com (makeworld.com [198.92.228.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6631943D2F for ; Mon, 17 Jan 2005 18:05:06 +0000 (GMT) (envelope-from racerx@makeworld.com) Received: from localhost (localhost.com [127.0.0.1]) by makeworld.com (Postfix) with ESMTP id D102D6130; Mon, 17 Jan 2005 12:04:57 -0600 (CST) Received: from makeworld.com ([127.0.0.1]) by localhost (makeworld.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 55485-08; Mon, 17 Jan 2005 12:04:47 -0600 (CST) Received: from [127.0.0.1] (unknown [63.117.97.221]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by makeworld.com (Postfix) with ESMTP id 41B2D60EA; Mon, 17 Jan 2005 12:04:39 -0600 (CST) Message-ID: <41EBFE33.4090703@makeworld.com> Date: Mon, 17 Jan 2005 12:04:35 -0600 From: Chris User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Adolfo B. Ferreira" References: <1105984508.950.7.camel@notebook> In-Reply-To: <1105984508.950.7.camel@notebook> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by ClamAV 0.75.1/amavisd-new-2.2.1 (20041222) at makeworld.com - Isn't it ironic cc: current@freebsd.org Subject: Re: Maildrop X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 18:05:08 -0000 Adolfo B. Ferreira wrote: >Hello Folks, > >Could some one help me with maildrop? > >I'm using FreeBSD 5.3 with all updated from CVS. >I'm trying to use maildrop with MYSQL and QUOTA but maildrop is not >connecting in MySQL. >I installed maildrop with >cd /usr/ports/mail/maildrop >make deinstall distclean WITH_MAILDIRQUOTA=yes WITH_TRASHQUOTA=yes >WITH_MYSQL=yes install clean >then i typed rehash and maildrop -v >maildrop 1.6.3 Copyright 1998-2003 Double Precision, Inc. >Maildir quota extension enabled. >Virtual user database via MySQL extension enabled. >This program is distributed under the terms of the GNU General Public >License. See COPYING for additional information. > >When I try to run maildrop with echo "test" | maildrop -V 5 -d >adolfo@anderung.com.br I got: >Invalid user specified. >but when I try with echo "test" | maildrop -V 5 -d root >maildrop: Changing to /root >Message start at 0 bytes, envelope sender=root >/usr/local/etc/maildrop/maildroprc(1): Opening >logfile /var/log/maildrop.log >maildrop: Attempting .mailfilter >maildrop: Delivering to /var/mail/root >maildrop: Appending to /var/mail/root. >maildrop: Delivery complete. > >So what I could understand is that maildrop is delivering only for users >from /etc/passwd. >My maildropmysql.config is located >in /usr/locall/etc/maildrop/maildropmysql.config and I set it in >Makefile of maildrop port. >anderung# cat maildropmysql.config >hostname localhost >port 3306 >socket /tmp/mysql.sock >database postfix >dbuser DBUSER >dbpw DBPASSWD >dbtable mailbox >uid_field username >uidnumber_field uid >gidnumber_field gid >maildir_field maildir >homedirectory_field home >quota_field quota >mailstatus_field active >where_clause AND active = '1' > >I have the user in the mailbox mysql table and the dbuser and dbpasswd >is correct. > >What am I doing wrong with maildrop? > >Thanks for all, > > >Adolfo Bravo Ferreira >Admninistrador de Redes / Analista de Seguranчa / Desenvolvedor >Grupo Ferreira Limitada >Telefone: 11 50628877 >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > You might have better luck asking in Questions or even Ports - I thought CURRENT (in this case) was for FBSD 6.0 and not 5.3 -- Best regards, Chris PGP Fingerprint = D976 2575 D0B4 E4B0 45CC AA09 0F93 FF80 C01B C363 From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 18:57:55 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A5A016A4CE for ; Mon, 17 Jan 2005 18:57:55 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03F1343D1D for ; Mon, 17 Jan 2005 18:57:55 +0000 (GMT) (envelope-from zbeeble@gmail.com) Received: by wproxy.gmail.com with SMTP id 58so114088wri for ; Mon, 17 Jan 2005 10:57:54 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=jqhw8daqUoR1m8dccoHK6VMcCBn5VNOLuruwh3VojmJq8r1JppJLLc1L7gXlaXOQaijUm/trXBKyPOAeFYt5MOPpbmxwYGIfJSYF7CeMso1i8sw8BS/ytz2vsOGDXUqR0pygL05ylLDC4rw3FQjRFjfxcu2U1dkRJ4U4GDLFAMk= Received: by 10.54.54.71 with SMTP id c71mr224363wra; Mon, 17 Jan 2005 10:57:54 -0800 (PST) Received: by 10.54.45.13 with HTTP; Mon, 17 Jan 2005 10:57:54 -0800 (PST) Message-ID: <5f67a8c405011710571d280068@mail.gmail.com> Date: Mon, 17 Jan 2005 13:57:54 -0500 From: Zaphod Beeblebrox To: Warren In-Reply-To: <200501172358.13311.shinjii@virusinfo.rdksupportinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200501172358.13311.shinjii@virusinfo.rdksupportinc.com> cc: freebsd-current@freebsd.org Subject: Re: Qtorrent X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Zaphod Beeblebrox List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 18:57:55 -0000 Torrent trackers seem to change the versions of software they require rather frequently and the error messages are often somewhat obtuse. It may be that the qtorrent author hasn't caught up with recent changes. On Mon, 17 Jan 2005 23:58:13 +1000, Warren wrote: > Has anyone else noticed that QTorrent now refuses to connect to any Torrent > Tracker ? From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 20:06:14 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D038816A4CE; Mon, 17 Jan 2005 20:06:14 +0000 (GMT) Received: from relay.bestcom.ru (relay.bestcom.ru [217.72.144.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0245743D53; Mon, 17 Jan 2005 20:06:14 +0000 (GMT) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (root@cell.sick.ru [217.72.144.68]) by relay.bestcom.ru (8.13.1/8.12.9) with ESMTP id j0HK6BCO043812 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 17 Jan 2005 23:06:12 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.11/8.12.8) with ESMTP id j0HK6BKi090882 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Jan 2005 23:06:11 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id j0HK6B45090881; Mon, 17 Jan 2005 23:06:11 +0300 (MSK) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@freebsd.org using -f Date: Mon, 17 Jan 2005 23:06:10 +0300 From: Gleb Smirnoff To: current@freebsd.org, net@freebsd.org Message-ID: <20050117200610.GA90866@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Mutt/1.5.6i X-Virus-Scanned: clamd / ClamAV version devel-20041013, clamav-milter version 0.75l on 127.0.0.1 X-Virus-Status: Clean Subject: [TEST/REVIEW] ng_ipfw: node to glue together ipfw(4) and netgraph(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 20:06:15 -0000 Dear collegues, here is quite a simple node for direct interaction between ipfw(4) and netgraph(4). It is going to be more effective and error-prone than a complicated construction around divert socket and ng_ksocket[1]. The semantics of node operation are quite simple. There is one node per system, which accepts any hooks with numeric names. Packets can be sent to netgraph(4) using ipfw 'netgraph' action, followed by a numeric cookie. Matched packets are sent out from corresponding hook of ng_ipfw node. These packets are tagged with information which helps them later to reenter ipfw processing. Tagged packets received on any node hook reenter IP stack. If net.inet.ip.fw.one_pass sysctl is non zero they are accepted, otherwise they continue with next rule. Non-tagged packets (not originating from ng_ipfw node) are discarded. Here is sample configuration. ng_echo(4) echoes packets back from netgraph to ipfw thru a tee node, which allows to sniff traffic. ngctl + ls There are 4 total nodes: Name: ngctl6138 Type: socket ID: 0000000c Num hooks: 0 Name: ipfw Type: ipfw ID: 00000009 Num hooks: 1 Name: Type: echo ID: 00000006 Num hooks: 1 Name: tee Type: tee ID: 00000005 Num hooks: 2 + show ipfw: Name: ipfw Type: ipfw ID: 00000009 Num hooks: 1 Local hook Peer name Peer type Peer ID Peer hook ---------- --------- --------- ------- --------- 666 tee tee 00000005 left + show tee: Name: tee Type: tee ID: 00000005 Num hooks: 2 Local hook Peer name Peer type Peer ID Peer hook ---------- --------- --------- ------- --------- left ipfw ipfw 00000009 666 right echo 00000006 echi root@jujik:/usr/src:|>ipfw show 00100 292 40304 allow ip from any to any via lo0 00200 0 0 deny ip from any to 127.0.0.0/8 00300 0 0 deny ip from 127.0.0.0/8 to any 00350 290730 661428793 netgraph 666 ip from any to any 65000 627921 1896034399 allow ip from any to any 65535 0 0 deny ip from any to any The patch [2] is applicable only to HEAD, sorry. The target users are the ones, who are now running ip_accounting/netflow using diverted ng_ksocket, and just netgraph geeks. Any kind of feedback is welcome via email with cc: net@. [1] http://freebsd.rambler.ru/bsdmail/freebsd-net_2004/msg03199.html [2] http://people.freebsd.org/~glebius/totest/ng_ipfw.patch -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 21:24:32 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D963216A4CE for ; Mon, 17 Jan 2005 21:24:32 +0000 (GMT) Received: from roma.ldjcs.com.au (dsl2-62.gw1.adl1.airnet.com.au [202.174.37.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id A110143D55 for ; Mon, 17 Jan 2005 21:24:31 +0000 (GMT) (envelope-from Lucas.James@LDJcs.Com.Au) Received: from roma.ldjcs.com.au (localhost [127.0.0.1]) by roma.ldjcs.com.au (8.13.1/8.13.1) with ESMTP id j0HLNvW4013800; Tue, 18 Jan 2005 07:53:57 +1030 (CST) (envelope-from Lucas.James@LDJcs.Com.Au) Received: from localhost (localhost [[UNIX: localhost]]) by roma.ldjcs.com.au (8.13.1/8.13.1/Submit) id j0HLNvGR013799; Tue, 18 Jan 2005 07:53:57 +1030 (CST) (envelope-from Lucas.James@LDJcs.Com.Au) X-Authentication-Warning: roma.ldjcs.com.au: lucas set sender to Lucas.James@LDJcs.Com.Au using -f From: Lucas James To: freebsd-current@freebsd.org Date: Tue, 18 Jan 2005 07:53:55 +1030 User-Agent: KMail/1.7 References: <41E0D550.1050608@elischer.org> <41E0D614.4000305@elischer.org> In-Reply-To: <41E0D614.4000305@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501180753.56671.Lucas.James@LDJcs.Com.Au> Subject: Re: do YOU have one of these USB devices? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 21:24:33 -0000 On Sun, 9 Jan 2005 05:28 pm, Julian Elischer wrote: > Julian Elischer wrote: > > If so, let me know if it crashes the system, or works > > (or just does nothing :-) ) > "Logitech Wingman Digital 3D" > (product 0xc207 vendor 0x046d release 0x0104) > as seen in: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/30502 I have one of those. uhci2: port 0xec00-0xec1f 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 uhid1: Logitech Inc. WingMan Extreme Digital 3D, rev 1.00/1.04, addr 2, iclass 3/0 usbdevs -v Controller /dev/usb2: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 addr 2: low speed, power 20 mA, config 1, WingMan Extreme Digital 3D(0xc207), Logitech Inc.(0x046d), rev 1.04 It doesn't crash the system, even using usbhidctl to read values. (I don't currently have any programs that use a joystick installed) Lucas -- PISCES (Feb. 19 to Mar. 20) Take the high road, look for the good things, carry the American Express card and a weapon. The world is yours today, as nobody else wants it. Your mortgage will be foreclosed. You will probably get run over by a bus. From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 22:07:35 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF57116A4D0 for ; Mon, 17 Jan 2005 22:07:35 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15C8943D39 for ; Mon, 17 Jan 2005 22:07:35 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 28B9A1FF9AF for ; Mon, 17 Jan 2005 23:07:33 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 26E0A1FF9AD; Mon, 17 Jan 2005 23:07:31 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 454DF1537B; Mon, 17 Jan 2005 22:07:20 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 3A7A015329 for ; Mon, 17 Jan 2005 22:07:21 +0000 (UTC) Date: Mon, 17 Jan 2005 22:07:21 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: FreeBSD current mailing list Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Subject: LOR: kern_descrip.c:2277,2278 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 22:07:36 -0000 Hi, I have added the following as LOR #055 to "the LOR page"[1]. lock order reversal 1st 0xffffffff80c3a9e8 sleep mtxpool (sleep mtxpool) @ sys/kern/kern_descrip.c:2277 2nd 0xffffff00222d8a48 filedesc structure (filedesc structure) @ sys/kern/kern_descrip.c:2278 KDB: stack backtrace: witness_checkorder() at witness_checkorder+0x5f1 _mtx_lock_flags() at _mtx_lock_flags+0x4a dupfdopen() at dupfdopen+0x320 kern_open() at kern_open+0x5de syscall() at syscall+0x4ab Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (5, FreeBSD ELF64, open), rip = 0x80077e7d0, rsp = 0x7fffffffe6f8, rbp = 0x7fffffffec70 --- I can easily reproduce it every boot. It seems to be triggered by Capi4BSD[2] framework which I incorporated in my private tree. Can someone please comment on this ? [1] http://sources.zabbadoz.net/freebsd/lor.html#055 [2] http://lists.freebsd.org/pipermail/freebsd-isdn/2004-December/000308.html -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 22:16:59 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2355B16A4CE; Mon, 17 Jan 2005 22:16:59 +0000 (GMT) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 821F543D41; Mon, 17 Jan 2005 22:16:58 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.13.0/8.13.0) with ESMTP id j0HMGvVG027352; Mon, 17 Jan 2005 17:16:57 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: <20050117053655.GA96378@dragon.nuxi.com> References: <20050117053655.GA96378@dragon.nuxi.com> Date: Mon, 17 Jan 2005 17:16:56 -0500 To: obrien@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) cc: freebsd-current@freebsd.org cc: Robert Watson Subject: Re: gratuitous gcc warnings: unused function arguments? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 22:16:59 -0000 At 9:36 PM -0800 1/16/05, David O'Brien wrote: >On Sun, Jan 16, 2005, Garance A Drosihn wrote: > > At 9:05 PM +0000 1/16/05, Robert Watson wrote: >> >On Sun, 16 Jan 2005, David O'Brien wrote: >> > > We're not going to hack GCC to deal with this. That is going way >> > > too far. This is coming up because people are using high WARNS > > > > values in Makefiles. Either back them down to a lower WARNS > > > > value; or we should add -Wno-unused-parameter to WARNS level 3. > > > > > > I'd be fine with simply pushing threshold for unused parameters > > > up a few notches on the warning scale. I'd like to have access > > > to the other interesting warnings are WARNS=3 and WARNS=4 relating > > > to qualifiers, strings, etc. > > >> I think it would be useful to keep that warning "in general", but >> have an option to turn it off. The following seems to work for me, >> assuming we can decide on the best name for a new NO_WUNUSED_ARGS >> option: > >Do you have a piece of code that exhibits this warning but otherwise >could pass at higher warning level? Who? Robert? Or me? I might, but I can't think of any at the moment. However, I have had cases where this warning has pointed out bugs to me -- such as a routine using a global variable because it had misspelled a reference to one of its own parameters. So, "in general" I do think this is a useful warning. And I (personally) prefer using __unused or the '(void)some_arg;' trick to silence the warning. >I'm resistant to adding a lot of NO_FOO_WARNING knobs. Otherwise we >might as well as remove the whole WARNS thing and set each warning a >Makefile wants. If developers would prefer to always turn it off for WARNS=3 and WARNS=4, that is certainly fine with me too. I agree that we do not want a lot of NO_WARN_FOO options, but I can see where this warning might be very annoying for a few (otherwise clean) source files. I wouldn't want those source files to be compiled with WARNS=2 (or to avoid -Werror) for no other reason than to avoid hassles with this one check. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 22:26:10 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4540A16A4CF for ; Mon, 17 Jan 2005 22:26:10 +0000 (GMT) Received: from mail.stonehenge.sk (otana.stonehenge.sk [81.0.222.209]) by mx1.FreeBSD.org (Postfix) with SMTP id AA41243D4C for ; Mon, 17 Jan 2005 22:26:08 +0000 (GMT) (envelope-from spaceman@stonehenge.sk) Received: (qmail 65729 invoked by uid 1000); 17 Jan 2005 22:27:34 -0000 Date: Mon, 17 Jan 2005 23:27:34 +0100 From: Michal Varga To: freebsd-current@freebsd.org Message-ID: <20050117222734.GB94722@stonehenge.sk> References: <41E0D550.1050608@elischer.org> <41E0D614.4000305@elischer.org> <200501180753.56671.Lucas.James@LDJcs.Com.Au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200501180753.56671.Lucas.James@LDJcs.Com.Au> User-Agent: Mutt/1.4.2.1i X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on otana.stonehenge.sk X-Spam-Level: X-Spam-Status: No, hits=0.0 required=7.0 tests=none autolearn=no version=2.64 Subject: Re: do YOU have one of these USB devices? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 22:26:10 -0000 Still not working here: uhid0: Logitech product 0xc207, rev 1.00/1.04, addr 2, iclass 3/0 uhid0: no report descriptor device_attach: uhid0 attach returned 6 uhid0: at uhub1 port 2 (addr 2) disconnected uhub1: device problem (SET_ADDR_FAILED), disabling port 2 # usbdevs addr 1: UHCI root hub, VIA addr 2: USB Optical Mouse, A4Tech addr 1: UHCI root hub, VIA addr 0 should never happen! - - - FreeBSD 6.0-CURRENT #0: Sun Jan 9 03:29:05 CET 2005 i386 uhci0: port 0xe400-0xe41f irq 21 at device 17.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: A4Tech USB Optical Mouse, rev 1.10/0.01, addr 2, iclass 3/1 ums0: 7 buttons and Z dir. uhci1: port 0xe800-0xe81f irq 21 at device 17.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered m. On Tue, 2005-Jan-18 at 07:53:55 +1030, Lucas James wrote: > > I have one of those. > uhid1: Logitech Inc. WingMan Extreme Digital 3D, rev 1.00/1.04, addr 2, iclass [...] > > It doesn't crash the system, even using usbhidctl to read values. (I don't > currently have any programs that use a joystick installed) > > Lucas From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 22:27:13 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E581F16A4CF for ; Mon, 17 Jan 2005 22:27:13 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68CF843D1D for ; Mon, 17 Jan 2005 22:27:13 +0000 (GMT) (envelope-from peadar.edwards@gmail.com) Received: by wproxy.gmail.com with SMTP id 58so137334wri for ; Mon, 17 Jan 2005 14:27:12 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=N47XQJdIz1cxjBErPthwCUwJY3PVdtDB3ShNETeHGE14RYs37Huqn2NYEPwfTP8QJXvP8jqDUO8wlA4HLhb9KrKxPgAIb6sxqAGzJC6tKDVSJyf/dWOihijYaYNsjQWVCdkpOTdb5N+BmqIn4yeNTt+tgNt522fqscyO9vggJXM= Received: by 10.54.49.36 with SMTP id w36mr384732wrw; Mon, 17 Jan 2005 14:27:12 -0800 (PST) Received: by 10.54.57.76 with HTTP; Mon, 17 Jan 2005 14:27:12 -0800 (PST) Message-ID: <34cb7c840501171427779900b@mail.gmail.com> Date: Mon, 17 Jan 2005 22:27:12 +0000 From: Peter Edwards To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: softdep panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Peter Edwards List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 22:27:14 -0000 I haven't seen this one reported, so this is just a datapoint. I was running in X, no dump, no traceback: just the following left in the message buffer after reboot: panic: softdep_setup_inomapdep: found inode KDB: enter: panic Followed by a hundred or so instances of the following, with various values for sp/fp: Fatal trap 3: breakpoint instruction fault while in kernel mode instruction pointer = 0x8:0xc04b49b4 stack pointer = 0x10:0xda60777c frame pointer = 0x10:0xda60777c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, IOPL = 0 current process = 23309 (vim) trap number = 3 panic: breakpoint instruction fault KDB: enter: panic This was with a kernel from sources in or around the 11th/12th, and its using vfs_subr 1.559, so predates the bug phk says was introduced in 1.561. This is a UP system with SCHED_ULE and PREEMPTION, with WITNESS disabled. From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 23:16:11 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 851A216A4CE for ; Mon, 17 Jan 2005 23:16:11 +0000 (GMT) Received: from roma.ldjcs.com.au (dsl2-62.gw1.adl1.airnet.com.au [202.174.37.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E92343D41 for ; Mon, 17 Jan 2005 23:16:09 +0000 (GMT) (envelope-from Lucas.James@LDJcs.Com.Au) Received: from roma.ldjcs.com.au (localhost [127.0.0.1]) by roma.ldjcs.com.au (8.13.1/8.13.1) with ESMTP id j0HNFXbQ014120; Tue, 18 Jan 2005 09:45:34 +1030 (CST) (envelope-from Lucas.James@LDJcs.Com.Au) Received: from localhost (localhost [[UNIX: localhost]]) by roma.ldjcs.com.au (8.13.1/8.13.1/Submit) id j0HNFXu2014119; Tue, 18 Jan 2005 09:45:33 +1030 (CST) (envelope-from Lucas.James@LDJcs.Com.Au) X-Authentication-Warning: roma.ldjcs.com.au: lucas set sender to Lucas.James@LDJcs.Com.Au using -f From: Lucas James To: freebsd-current@freebsd.org Date: Tue, 18 Jan 2005 09:45:32 +1030 User-Agent: KMail/1.7 References: <41E0D550.1050608@elischer.org> <200501180753.56671.Lucas.James@LDJcs.Com.Au> <20050117222734.GB94722@stonehenge.sk> In-Reply-To: <20050117222734.GB94722@stonehenge.sk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501180945.32984.Lucas.James@LDJcs.Com.Au> Subject: Re: do YOU have one of these USB devices? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 23:16:11 -0000 On Tue, 18 Jan 2005 08:57 am, Michal Varga wrote: > Still not working here: It looks like a VIA problem.. It works with the desktop machine (Intel), but on my laptop it's broke: -- Last yeer I kudn't spel Engineer. Now I are won. From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 23:18:56 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C858616A4CF for ; Mon, 17 Jan 2005 23:18:56 +0000 (GMT) Received: from roma.ldjcs.com.au (dsl2-62.gw1.adl1.airnet.com.au [202.174.37.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A67D43D46 for ; Mon, 17 Jan 2005 23:18:53 +0000 (GMT) (envelope-from Lucas.James@LDJcs.Com.Au) Received: from roma.ldjcs.com.au (localhost [127.0.0.1]) by roma.ldjcs.com.au (8.13.1/8.13.1) with ESMTP id j0HNIKPL014164; Tue, 18 Jan 2005 09:48:20 +1030 (CST) (envelope-from Lucas.James@LDJcs.Com.Au) Received: from localhost (localhost [[UNIX: localhost]]) by roma.ldjcs.com.au (8.13.1/8.13.1/Submit) id j0HNIJ7D014163; Tue, 18 Jan 2005 09:48:19 +1030 (CST) (envelope-from Lucas.James@LDJcs.Com.Au) X-Authentication-Warning: roma.ldjcs.com.au: lucas set sender to Lucas.James@LDJcs.Com.Au using -f From: Lucas James To: freebsd-current@freebsd.org Date: Tue, 18 Jan 2005 09:48:18 +1030 User-Agent: KMail/1.7 References: <41E0D550.1050608@elischer.org> <20050117222734.GB94722@stonehenge.sk> <200501180945.32984.Lucas.James@LDJcs.Com.Au> In-Reply-To: <200501180945.32984.Lucas.James@LDJcs.Com.Au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501180948.19599.Lucas.James@LDJcs.Com.Au> Subject: Re: do YOU have one of these USB devices? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 23:18:56 -0000 On Tue, 18 Jan 2005 09:45 am, Lucas James wrote: > On Tue, 18 Jan 2005 08:57 am, Michal Varga wrote: > > Still not working here: > > It looks like a VIA problem.. > > It works with the desktop machine (Intel), but on my laptop it's broke: try again: uhci1: port 0x1300-0x131f irq 10 at device 17.3 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered [...] uhid0: Logitech product 0xc207, rev 1.00/1.04, addr 2, iclass 3/0 uhid0: no report descriptor device_attach: uhid0 attach returned 6 uhid0: at uhub1 port 1 (addr 2) disconnected uhub1: device problem (SET_ADDR_FAILED), disabling port 1 usbdevs -v: Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), VIA(0x0000), rev 1.00 port 1 addr 0 should never happen! port 2 powered -- It is easier to be a "humanitarian" than to render your own country its proper due; it is easier to be a "patriot" than to make your community a better place to live in; it is easier to be a "civic leader" than to treat your own family with loving understanding; for the smaller the focus of attention, the harder the task. -- Sydney J. Harris From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 05:02:41 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4EF4E16A4CE for ; Tue, 18 Jan 2005 05:02:41 +0000 (GMT) Received: from webhost1.tasman.net (webhost1.tasman.net [202.49.92.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D423D43D31 for ; Tue, 18 Jan 2005 05:02:40 +0000 (GMT) (envelope-from marcos@ThePacific.Net) Received: from [203.86.192.98] (helo=[172.16.20.10]) by webhost1.tasman.net with esmtpa (Exim 4.43 (FreeBSD)) id 1CqlTR-000Fuv-UW for freebsd-current@freebsd.org; Tue, 18 Jan 2005 18:00:13 +1300 Message-ID: <41ED4EAA.4030407@ThePacific.Net> Date: Tue, 18 Jan 2005 18:00:10 +0000 From: "Marcos Biscaysaqu - ThePacific.net" User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040910) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus-Scanner: Clean mail though you should still use an Antivirus X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - webhost1.tasman.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [26 6] X-AntiAbuse: Sender Address Domain - ThePacific.Net X-Source: X-Source-Args: X-Source-Dir: Subject: ath0 doesn't work in turbo mode 11a X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 05:02:41 -0000 Hi there. Im trying to setup my wireless card on Freebsd-5.3 stable, Im runing an commercial AP in 11a turbo mode but I can't connect my atheros card to it. work perfect in 5Ghz but doesn't in turbo mode. it is any special setting to do this, or is just a driver problem? I tried all the channels, different ifconfig options but I can't get an associated status in turbo mode. ath0: mem 0x42000000-0x4200ffff irq 11 at device 14.0 on pci0 ath0: [GIANT-LOCKED] ath0: mac 4.2 phy 3.0 5ghz radio 1.7 2ghz radio 2.3 ath0: Ethernet address: 00:01:24:70:54:a9 ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ath0: turbo rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps `ifconfig ath0 ssid XXX media OFDM/54 Mbps mode 11a mediaopt turbo` thanks Marcos Biscaysaqu From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 06:55:17 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4F2616A4CE for ; Tue, 18 Jan 2005 06:55:17 +0000 (GMT) Received: from www.mmlab.cse.yzu.edu.tw (www.mmlab.cse.yzu.edu.tw [140.138.150.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 193BE43D2F for ; Tue, 18 Jan 2005 06:55:12 +0000 (GMT) (envelope-from avatar@mmlab.cse.yzu.edu.tw) Received: by www.mmlab.cse.yzu.edu.tw (qmail, from userid 1000) id 892794EFCD6; Tue, 18 Jan 2005 14:55:09 +0800 (CST) Received: from localhost (localhost [127.0.0.1]) by www.mmlab.cse.yzu.edu.tw (qmail) with ESMTP id 6CA584EFCD3; Tue, 18 Jan 2005 14:55:09 +0800 (CST) Date: Tue, 18 Jan 2005 14:55:09 +0800 (CST) From: Tai-hwa Liang To: Peter Edwards In-Reply-To: <34cb7c840501171427779900b@mail.gmail.com> Message-ID: <050118145042E.25486@www.mmlab.cse.yzu.edu.tw> References: <34cb7c840501171427779900b@mail.gmail.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1978010320-1106031309=:25486" cc: current@freebsd.org Subject: Re: softdep panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 06:55:17 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1978010320-1106031309=:25486 Content-Type: TEXT/PLAIN; charset=big5; format=flowed Content-Transfer-Encoding: 8BIT On Mon, 17 Jan 2005, Peter Edwards wrote: > I haven't seen this one reported, so this is just a datapoint. I was > running in X, no dump, no traceback: just the following left in the > message buffer after reboot: > > panic: softdep_setup_inomapdep: found inode > KDB: enter: panic > > Followed by a hundred or so instances of the following, with various > values for sp/fp: > Fatal trap 3: breakpoint instruction fault while in kernel mode > instruction pointer = 0x8:0xc04b49b4 > stack pointer = 0x10:0xda60777c > frame pointer = 0x10:0xda60777c > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, IOPL = 0 > current process = 23309 (vim) > trap number = 3 > panic: breakpoint instruction fault > KDB: enter: panic > > This was with a kernel from sources in or around the 11th/12th, and > its using vfs_subr 1.559, so predates the bug phk says was introduced > in 1.561. > This is a UP system with SCHED_ULE and PREEMPTION, with WITNESS disabled. I ran into the same panic with -CURRENT cvsup'ed around Jan-10-2005. It's An UP system with SCHED_4BSD, no PREEMPTION, no WITNESS. If I remembered correctly, the panic was triggered by making module(which creates symlink) on a filesystem where the background fsck is running on. #0 doadump () at pcpu.h:159 #1 0xc045568a in db_fncall (dummy1=-1067591643, dummy2=0, dummy3=-422627384, dummy4=0xe6cf3760 "\2247Яц") at ../../../ddb/db_command.c:531 #2 0xc0455a20 in db_command_loop () at ../../../ddb/db_command.c:349 #3 0xc0457474 in db_trap (type=3, code=0) at ../../../ddb/db_main.c:221 #4 0xc04f9e82 in kdb_trap (type=3, code=0, tf=0xe6cf3888) at ../../../kern/subr_kdb.c:421 #5 0xc05f0e10 in trap (frame= {tf_fs = 24, tf_es = 16, tf_ds = 16, tf_edi = 1, tf_esi = 1, tf_ebp = -422627128, tf_isp = -422627148, tf_ebx = -422627084, tf_edx = -1067328525, tf_ecx = -1067012256, tf_eax = -1067322373, tf_trapno = 3, tf_err = 0, tf_eip = -1068524868, tf_cs = 8, tf_eflags = 646, tf_esp = -422627096, tf_ss = -1068628830}) at ../../../i386/i386/trap.c:573 #6 0xc05df29a in calltrap () at ../../../i386/i386/exception.s:139 #7 0x00000018 in ?? () #8 0x00000010 in ?? () #9 0x00000010 in ?? () #10 0x00000001 in ?? () #11 0x00000001 in ?? () #12 0xe6cf38c8 in ?? () #13 0xe6cf38b4 in ?? () #14 0xe6cf38f4 in ?? () #15 0xc061dbf3 in ?? () #16 0xc066af60 in shutdown_howto () #17 0xc061f3fb in ?? () #18 0x00000003 in ?? () #19 0x00000000 in ?? () #20 0xc04f9abc in kdb_enter (msg=0x0) at cpufunc.h:56 #21 0xc04e04a2 in panic (fmt=0x1
) at ../../../kern/kern_shutdown.c:538 #22 0xc058b732 in softdep_setup_inomapdep (bp=0xd5f357a8, ip=0x0, newinum=70995) at ../../../ufs/ffs/ffs_softdep.c:1279 #23 0xc057768a in ffs_nodealloccg (ip=0xc26b271c, cg=3, ipref=339, mode=41453) at ../../../ufs/ffs/ffs_alloc.c:1634 #24 0xc057646c in ffs_hashalloc (ip=0xc26b271c, cg=3, pref=72997, size=41453, allocator=0xc0577338 ) at ../../../ufs/ffs/ffs_alloc.c:1178 #25 0xc0576b26 in ffs_valloc (pvp=0xc26a8564, mode=41453, cred=0xc268d680, vpp=0xe6cf3a54) at ../../../ufs/ffs/ffs_alloc.c:880 #26 0xc059fb72 in ufs_makeinode (mode=41453, dvp=0xc26a8564, vpp=0xe6cf3c1c, cnp=0xe6cf3c30) at ../../../ufs/ufs/ufs_vnops.c:2218 #27 0xc05a0e24 in ufs_symlink (ap=0xe6cf3bc8) at ../../../ufs/ufs/ufs_vnops.c:1750 #28 0xc0540217 in kern_symlink (td=0xe6cf3be8, path=0xbfbfe912
, link=0x0, segflg=UIO_USERSPACE) at vnode_if.h:1074 #29 0xc05402b5 in symlink (td=0xc26b72e0, uap=0x0) at ../../../kern/vfs_syscalls.c:1448 #30 0xc05f12b3 in syscall (frame= {tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 0, tf_esi = -1077941998, tf_ebp = -1077942552, tf_isp = -422625932, tf_ebx = -1077941985, tf_edx = 0, tf_ecx = 2, tf_eax = 57, tf_trapno = 12, tf_err = 2, tf_eip = 671877051, tf_cs = 31, tf_eflags = 658, tf_esp = -1077943716, tf_ss = 47}) at ../../../i386/i386/trap.c:951 #31 0xc05df2ef in Xint0x80_syscall () at ../../../i386/i386/exception.s:200 #32 0x0000002f in ?? () #33 0x0000002f in ?? () #34 0x0000002f in ?? () #35 0x00000000 in ?? () #36 0xbfbfe912 in ?? () #37 0xbfbfe6e8 in ?? () #38 0xe6cf3d74 in ?? () #39 0xbfbfe91f in ?? () #40 0x00000000 in ?? () #41 0x00000002 in ?? () #42 0x00000039 in ?? () #43 0x0000000c in ?? () #44 0x00000002 in ?? () #45 0x280c07bb in ?? () #46 0x0000001f in ?? () #47 0x00000292 in ?? () #48 0xbfbfe25c in ?? () #49 0x0000002f in ?? () #50 0x00000000 in ?? () #51 0x00000000 in ?? () #52 0x00000000 in ?? () #53 0x00000000 in ?? () #54 0x2ff65000 in ?? () #55 0x00000003 in ?? () #56 0xc26b72e0 in ?? () #57 0xe6cf3ca8 in ?? () #58 0xe6cf3c90 in ?? () #59 0xc1eab2e0 in ?? () #60 0xc04f2c08 in sched_switch (td=0xbfbfe912, newtd=0xbfbfe91f, flags=Cannot access memory at address 0xbfbfe6f8 ) at ../../../kern/sched_4bsd.c:963 Previous frame inner to this frame (corrupt stack?) (kgdb) f 22 #22 0xc058b732 in softdep_setup_inomapdep (bp=0xd5f357a8, ip=0x0, newinum=70995) at ../../../ufs/ffs/ffs_softdep.c:1279 1279 panic("softdep_setup_inomapdep: found inode"); (kgdb) l 1274 * the cylinder group map from which it was allocated. 1275 */ 1276 ACQUIRE_LOCK(&lk); 1277 if ((inodedep_lookup(ip->i_fs, newinum, DEPALLOC|NODELAY, &inodedep))) { 1278 FREE_LOCK(&lk); 1279 panic("softdep_setup_inomapdep: found inode"); 1280 } 1281 inodedep->id_buf = bp; 1282 inodedep->id_state &= ~DEPCOMPLETE; 1283 bmsafemap = bmsafemap_lookup(bp); (kgdb) up #23 0xc057768a in ffs_nodealloccg (ip=0xc26b271c, cg=3, ipref=339, mode=41453) at ../../../ufs/ffs/ffs_alloc.c:1634 1634 softdep_setup_inomapdep(bp, ip, cg * fs->fs_ipg + ipref); (kgdb) print cg $1 = 3 (kgdb) print newinum $2 = 70995 (kgdb) print *ip $3 = {i_hash = {le_next = 0x0, le_prev = 0xc21b94b8}, i_nextsnap = { tqe_next = 0x0, tqe_prev = 0x0}, i_vnode = 0xc26a8564, i_ump = 0xc227d100, i_flag = 46, i_dev = 0xc2224900, i_number = 72997, i_effnlink = 2, i_fs = 0xc21ff800, i_dquot = {0x0, 0x0}, i_modrev = 207041322030, i_lockf = 0x0, i_count = 68, i_endoff = 512, i_diroff = 0, i_offset = 12, i_ino = 71068, i_reclen = 300, i_un = {dirhash = 0x0, snapblklist = 0x0}, i_ea_area = 0x0, i_ea_len = 0, i_ea_error = 0, i_mode = 16877, i_nlink = 2, i_size = 512, i_flags = 0, i_gen = 480111649, i_uid = 0, i_gid = 0, dinode_u = {din1 = 0xc26afd00, din2 = 0xc26afd00}} --0-1978010320-1106031309=:25486-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 09:53:13 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DD7016A4CE; Tue, 18 Jan 2005 09:53:13 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id E30A243D3F; Tue, 18 Jan 2005 09:53:12 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id j0I9rC2k085932; Tue, 18 Jan 2005 04:53:12 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.1/8.13.1) with ESMTP id j0I9rCkb055140; Tue, 18 Jan 2005 04:53:12 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 5592B7306E; Tue, 18 Jan 2005 04:53:12 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050118095312.5592B7306E@freebsd-current.sentex.ca> Date: Tue, 18 Jan 2005 04:53:12 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/671/Mon Jan 17 09:16:31 2005 clamav-milter version 0.80j on clamscanner3 X-Virus-Status: Clean Subject: [current tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 09:53:13 -0000 TB --- 2005-01-18 07:57:27 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-01-18 07:57:27 - starting CURRENT tinderbox run for ia64/ia64 TB --- 2005-01-18 07:57:27 - checking out the source tree TB --- 2005-01-18 07:57:27 - cd /home/tinderbox/CURRENT/ia64/ia64 TB --- 2005-01-18 07:57:27 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-01-18 08:05:50 - building world (CFLAGS=-O2 -pipe) TB --- 2005-01-18 08:05:50 - cd /home/tinderbox/CURRENT/ia64/ia64/src TB --- 2005-01-18 08:05:50 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-01-18 09:43:21 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-01-18 09:43:21 - cd /home/tinderbox/CURRENT/ia64/ia64/src TB --- 2005-01-18 09:43:21 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Tue Jan 18 09:43:21 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c: In function `bus_dmamap_load_uio': /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c:784: warning: passing arg 1 of `_bus_dmamap_load_buffer' from incompatible pointer type /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c:784: warning: passing arg 2 of `_bus_dmamap_load_buffer' makes integer from pointer without a cast /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c:784: error: too many arguments to function `_bus_dmamap_load_buffer' /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c: In function `_bus_dmamap_load_buffer': /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c:496: error: prior parameter's size depends on 'map' /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c:496: error: prior parameter's size depends on 'map' /tinderbox/CURRENT/ia64/ia64/src/sys/ia64/ia64/busdma_machdep.c:514: confused by earlier errors, bailing out *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/obj/ia64/tinderbox/CURRENT/ia64/ia64/src/sys/GENERIC. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src. *** Error code 1 Stop in /tinderbox/CURRENT/ia64/ia64/src. TB --- 2005-01-18 09:53:12 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-01-18 09:53:12 - ERROR: failed to build generic kernel TB --- 2005-01-18 09:53:12 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 12:07:00 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA1E116A4CE for ; Tue, 18 Jan 2005 12:07:00 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id A8D8643D31 for ; Tue, 18 Jan 2005 12:06:59 +0000 (GMT) (envelope-from emanuel.strobl@gmx.net) Received: (qmail invoked by alias); 18 Jan 2005 12:06:58 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp013) with SMTP; 18 Jan 2005 13:06:58 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org Date: Tue, 18 Jan 2005 13:06:43 +0100 User-Agent: KMail/1.7.2 X-Birthday: 10/06/72 X-CelPhone: +49 173 9967781 X-Tel: +49 89 18947781 X-Country: Germany X-Address: Munich, 80686 X-OS: FreeBSD MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart23613036.DmIMnPQQud"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501181306.49120.emanuel.strobl@gmx.net> X-Y-GMX-Trusted: 0 Subject: strange ucom (uplcom) error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 12:07:00 -0000 --nextPart23613036.DmIMnPQQud Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Dear experts, I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working the= =20 other one not (I hate to say it but both are working under win). The not working (more expensive) one gets recognized as ucom0 and I have=20 ucom0, also I can receive signal but not transmit. When I connect the (more expensive) adopter to a serial console (FreeBSD=20 comconsole) I can see all kernel messages but I can't type any charecter wh= en=20 I see the login. If I change to the cheaper adopter everything is working=20 fine. I compared 'stty -a -f /dev/ucom0' and both adaptors show the same=20 settings. I'm using tip (ucom0:dv=3D/dev/ucom0:br#115200:pa=3Dnone:) on RELENG_5 (fro= m this=20 weekend) Here is usbdevfs output and the corresponding dmesg line for both adapters,= =20 the 2nd (ATEN) is the working one (cheaper one), the first the more expensi= ve=20 not working one! port 1 addr 2: full speed, power 100 mA, config 1, USB-Serial=20 Controller(0x2303), Prolific Technology Inc.(0x067b), rev 3.00 __dmesg: ucom0: Prolific Technology Inc. USB-Serial Controller, rev 1.10/3.00, addr 2 port 1 addr 2: full speed, power 100 mA, config 1, PL2303 Serial adapter=20 (ATEN/IOGEAR UC232A)(0x2303), Prolific Technology(0x067b), rev 2.02 __dmesg: ucom0: Prolific Technology PL2303 Serial adapter (ATEN/IOGEAR UC232A), rev= =20 1.10/2.02, addr 2 Any help highly appreciated! =2DHarry --nextPart23613036.DmIMnPQQud Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB7PvZBylq0S4AzzwRAjCkAKCCri7KwY8+7JAn7aTt5UP9+hVX6QCfcZxh gRhSQuXa99ombtpDErz3mSA= =AcCK -----END PGP SIGNATURE----- --nextPart23613036.DmIMnPQQud-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 12:19:16 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF0FB16A4CE for ; Tue, 18 Jan 2005 12:19:16 +0000 (GMT) Received: from bsd.dino.sk (bsd.dino.sk [213.215.72.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB15543D3F for ; Tue, 18 Jan 2005 12:19:15 +0000 (GMT) (envelope-from bsd@dino.sk) Received: from [213.215.72.59] ([213.215.72.59]) by bsd.dino.sk with esmtp; Tue, 18 Jan 2005 13:19:10 +0100 id 000000F4.41ECFEBF.00000E0F From: Milan Obuch To: freebsd-current@freebsd.org Date: Tue, 18 Jan 2005 13:18:54 +0100 User-Agent: KMail/1.7.2 References: <200501181306.49120.emanuel.strobl@gmx.net> In-Reply-To: <200501181306.49120.emanuel.strobl@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501181318.57177.bsd@dino.sk> Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 12:19:17 -0000 On Tuesday 18 January 2005 13:06, Emanuel Strobl wrote: > Dear experts, > > I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working the > other one not (I hate to say it but both are working under win). > > The not working (more expensive) one gets recognized as ucom0 and I have > ucom0, also I can receive signal but not transmit. > > When I connect the (more expensive) adopter to a serial console (FreeBSD > comconsole) I can see all kernel messages but I can't type any charecter > when I see the login. If I change to the cheaper adopter everything is > working fine. I compared 'stty -a -f /dev/ucom0' and both adaptors show the > same settings. > > I'm using tip (ucom0:dv=/dev/ucom0:br#115200:pa=none:) on RELENG_5 (from > this weekend) > Hi, I am by no means an expert here, just couple of my observations. I have two Prolific2303 adapters and they exhibit both some peculiarity. I use minicom for serial communication. With my pl2303 based adapters, I must first start minicom, change something (toggle harware flow control as an example) and after that, I can use the adapter. Without this, no characters are seen, however, what I type is send to the other side. There is something incorrect in USB stack maybe, but with this workaround I can live with this. I have no possibility to investigate further, if someone, however, makes a path to be tested, I can do it. Regards, Milan From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 14:27:44 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE4E016A4CE for ; Mon, 17 Jan 2005 14:27:44 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 501FD43D45 for ; Mon, 17 Jan 2005 14:27:44 +0000 (GMT) (envelope-from buhnux@gmail.com) Received: by rproxy.gmail.com with SMTP id f1so240398rne for ; Mon, 17 Jan 2005 06:27:43 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:subject:date:to:x-pgp-agent:x-mailer:from; b=BTIRmpUosU5977NY3iVMckMQyauWgut3BaVOwxqipvxFVMHPfB19MhPDKgmGkv0xgH3McHhVWCYIuebu7L9urfNR5JxSaoNyvaQ9hXzl/sIRglzEGgBj3SBDVrZQrrf/ytRYjhjSKPNxeu6jw95iQbdwAQkFUghQvWPMVVmqvuc= Received: by 10.38.158.11 with SMTP id g11mr243159rne; Mon, 17 Jan 2005 06:27:43 -0800 (PST) Received: from ?10.61.32.103? ([68.187.162.8]) by smtp.gmail.com with ESMTP id 58sm440rnc.2005.01.17.06.27.43; Mon, 17 Jan 2005 06:27:43 -0800 (PST) In-Reply-To: <200501172358.13311.shinjii@virusinfo.rdksupportinc.com> References: <200501172358.13311.shinjii@virusinfo.rdksupportinc.com> Mime-Version: 1.0 Content-Type: text/plain; Message-Id: Date: Mon, 17 Jan 2005 09:27:40 -0500 To: Warren X-Pgp-Agent: GPGMail 1.0.2 X-Mailer: Apple Mail (2.619) From: Michael Johnson X-Mailman-Approved-At: Tue, 18 Jan 2005 13:17:05 +0000 cc: freebsd-current@freebsd.org Subject: Re: Qtorrent X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 14:27:44 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 it's a bit out dated and trackers are probably blocking QTorrent because it doesn't have X feature. It works with some trackers. Michael On Jan 17, 2005, at 8:58 AM, Warren wrote: > Has anyone else noticed that QTorrent now refuses to connect to any > Torrent > Tracker ? > > If i could get some sort of Bug reports i send it in, but since GDB > dosent > like it and the program runs fine untill you want to use it to d/l > anything > using as torrent i mnot sure how to find out whats happening. > -- > Yours Sincerely > Shinjii > http://www.shinji.nq.nu > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFB68tdn4uqfTwEb9YRAliFAKC5OwxlaOH6t0rZVaw8rv7uNkvA2wCggOcb Tq/xp0x7DVj/A2dZBJMkz+o= =qXf6 -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 16:01:37 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 177FF16A4CE; Mon, 17 Jan 2005 16:01:37 +0000 (GMT) Received: from elrond.anembo.nu.org (dsl-202-173-130-73.nsw.westnet.com.au [202.173.130.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3942543D1D; Mon, 17 Jan 2005 16:01:36 +0000 (GMT) (envelope-from cjsv@elrond.anembo.nu.org) Received: from elrond.anembo.nu.org (localhost [127.0.0.1]) by elrond (8.13.1/8.13.1) with ESMTP id j0H20fJ3002089; Mon, 17 Jan 2005 13:00:41 +1100 (EST) (envelope-from cjsv@elrond.anembo.nu.org) Received: (from cjsv@localhost) by elrond.anembo.nu.org (8.13.1/8.13.1/Submit) id j0H20dml002088; Mon, 17 Jan 2005 13:00:39 +1100 (EST) (envelope-from cjsv) Date: Mon, 17 Jan 2005 13:00:39 +1100 From: Christopher Vance To: David Yu Message-ID: <20050117020039.GB630@nu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: X-Mailman-Approved-At: Tue, 18 Jan 2005 13:17:05 +0000 cc: freebsd-fs@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: NTFS unicode converting problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 16:01:37 -0000 On Sun, Jan 16, 2005 at 01:44:04PM -0800, David Yu wrote: >Hi, it seems that NTFS in FreeBSD uses a 16-bit long wchar to store >filename. When I wanted to convert some Chinese filename into UTF-8, >the conversion was failed because a single Chinese character needs 3 >bytes in UTF-8. Is anyone already working on this problem? If not, I >would like to do something about it. Any suggestions? >From memory, old Windows used UCS-2, while newer Windows uses UTF-16. Was the bad character in plane 0 or higher? -- Christopher Vance From owner-freebsd-current@FreeBSD.ORG Mon Jan 17 19:43:33 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 304AF16A4CE; Mon, 17 Jan 2005 19:43:33 +0000 (GMT) Received: from vampextream.com (vampextream.com [65.102.125.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF87B43D31; Mon, 17 Jan 2005 19:43:32 +0000 (GMT) (envelope-from whitevamp@vampextream.com) Received: from localhost (localhost.vampextream [127.0.0.1]) by vampextream.com (Postfix) with ESMTP id ADB4054BB; Mon, 17 Jan 2005 11:47:24 -0800 (PST) Received: from vampextream.com ([127.0.0.1]) by localhost (vampextream.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02270-02; Mon, 17 Jan 2005 11:47:04 -0800 (PST) Received: from vampextream.com (localhost.vampextream [127.0.0.1]) by vampextream.com (Postfix) with ESMTP id 424DC54BA; Mon, 17 Jan 2005 11:47:00 -0800 (PST) From: "whitevamp" To: freebsd-current@freebsd.org;, ports@freebsd.org Date: Mon, 17 Jan 2005 11:46:59 -0800 Message-Id: <20050117193702.M21416@vampextream.com> X-Mailer: Open WebMail 2.41 20040926 X-OriginatingIP: 65.102.125.195 (whitevamp@vampextream.com) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailman-Approved-At: Tue, 18 Jan 2005 13:17:05 +0000 Subject: ruby and portupgrade X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Jan 2005 19:43:33 -0000 i am trying to do a portupgrade and after it running for 7 hrs and not doing anything it quits with this error message. black-buity# portupgrade -aRrcCv ---> Reading default options: -v -D -l /var/tmp/portupgrade.results -L /var/tmp/portupgrade-%s::%s.log ---> Session started at: Sat, 15 Jan 2005 12:07:25 -0800 [Updating the pkgdb in /var/db/pkg ... - 110 packages found (-0 +23) ....................... done] ---> Session ended at: Sat, 15 Jan 2005 19:13:25 -0800 (consumed 07:05:59) /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:323:in `deorigin': cannot convert nil into String (PkgDB::DBError) from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:916:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `each' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:929:in `sort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:933:in `sort_build!' from /usr/local/sbin/portupgrade:674:in `main' from /usr/local/sbin/portupgrade:207:in `initialize' from /usr/local/sbin/portupgrade:207:in `new' from /usr/local/sbin/portupgrade:207:in `main' from /usr/local/sbin/portupgrade:1845 black-buity# black-buity# ruby --version ruby 1.8.2 (2004-07-29) [i386-freebsd5] black-buity# uname -a FreeBSD black-buity.vampextream.com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Dec 10 14:50:33 PST 2004 root@black-buity.vampextream.com:/usr/src/sys/i386/compile/VAMPEXTREAM i386 black-buity# i have read UPDATEING and didnt find any thing on 1.8 just updateing ruby from 1.6 to 1.8 .. so my quistions are 1. what would be causeing this?? 2. how do i fix this? and thanks inadvance for any help on this issue/ error message If you play the WindowsXP CD backwards, you get a Satanic message . That's nothing. If you play it forwards, it installs WindowsXP! From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 08:31:22 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70EE116A4CE for ; Tue, 18 Jan 2005 08:31:22 +0000 (GMT) Received: from mx.nsu.ru (mx.nsu.ru [212.192.164.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38DAA43D1F for ; Tue, 18 Jan 2005 08:31:21 +0000 (GMT) (envelope-from danfe@regency.nsu.ru) Received: from regency.nsu.ru ([193.124.210.26]) by mx.nsu.ru with esmtp (Exim 4.34) id 1CqozK-00079h-EF for freebsd-current@freebsd.org; Tue, 18 Jan 2005 14:45:22 +0600 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.13.1/8.13.1) with ESMTP id j0I8YvOh060782 for ; Tue, 18 Jan 2005 14:34:57 +0600 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.13.1/8.13.1/Submit) id j0I8Yv4G060772 for freebsd-current@freebsd.org; Tue, 18 Jan 2005 14:34:57 +0600 (NOVT) (envelope-from danfe) Date: Tue, 18 Jan 2005 14:34:57 +0600 From: Alexey Dokuchaev To: freebsd-current@freebsd.org Message-ID: <20050118083457.GA57902@regency.nsu.ru> References: <20050116144113.GB66854@gothmog.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050116144113.GB66854@gothmog.gr> User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Tue, 18 Jan 2005 13:17:05 +0000 Subject: Re: gratuitous gcc warnings: unused function arguments? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 08:31:22 -0000 On Sun, Jan 16, 2005 at 04:41:13PM +0200, Giorgos Keramidas wrote: > > This allows the main() function to keep being compliant with the ANSI > standard that specifies only two valid prototypes for main(): > > int main(void); > int main(int argc, char *argv[]); Hmm, I might sound wrong, but I also recall seeing ``int main(int argc, char *argv[], char *envp[]);'' as valid main() prototype as well. ./danfe From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 13:29:32 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC90E16A4CE for ; Tue, 18 Jan 2005 13:29:32 +0000 (GMT) Received: from av5-2-sn1.fre.skanova.net (av5-2-sn1.fre.skanova.net [81.228.11.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7E6343D54 for ; Tue, 18 Jan 2005 13:29:31 +0000 (GMT) (envelope-from ertr1013@student.uu.se) Received: by av5-2-sn1.fre.skanova.net (Postfix, from userid 502) id 3351237F2A; Tue, 18 Jan 2005 14:29:31 +0100 (CET) Received: from smtp2-2-sn2.hy.skanova.net (smtp2-2-sn2.hy.skanova.net [81.228.8.178]) by av5-2-sn1.fre.skanova.net (Postfix) with ESMTP id 238CD37EA1 for ; Tue, 18 Jan 2005 14:29:31 +0100 (CET) Received: from falcon.midgard.homeip.net (h201n1fls24o1048.bredband.comhem.se [212.181.162.201]) by smtp2-2-sn2.hy.skanova.net (Postfix) with SMTP id E87AF37E47 for ; Tue, 18 Jan 2005 14:29:30 +0100 (CET) Received: (qmail 97893 invoked by uid 1001); 18 Jan 2005 13:29:30 -0000 Date: Tue, 18 Jan 2005 14:29:30 +0100 From: Erik Trulsson To: Alexey Dokuchaev Message-ID: <20050118132930.GA97874@falcon.midgard.homeip.net> Mail-Followup-To: Alexey Dokuchaev , freebsd-current@freebsd.org References: <20050116144113.GB66854@gothmog.gr> <20050118083457.GA57902@regency.nsu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050118083457.GA57902@regency.nsu.ru> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: gratuitous gcc warnings: unused function arguments? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 13:29:33 -0000 On Tue, Jan 18, 2005 at 02:34:57PM +0600, Alexey Dokuchaev wrote: > On Sun, Jan 16, 2005 at 04:41:13PM +0200, Giorgos Keramidas wrote: > > > > This allows the main() function to keep being compliant with the ANSI > > standard that specifies only two valid prototypes for main(): > > > > int main(void); > > int main(int argc, char *argv[]); > > Hmm, I might sound wrong, but I also recall seeing ``int main(int argc, > char *argv[], char *envp[]);'' as valid main() prototype as well. That is not correct according to the ANSI/ISO C standard. It is a very common extension on Unix systems, but it is not standard C. -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 15:07:40 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECB8216A4CE for ; Tue, 18 Jan 2005 15:07:40 +0000 (GMT) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.FreeBSD.org (Postfix) with SMTP id 6440943D46 for ; Tue, 18 Jan 2005 15:07:40 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 35439 invoked from network); 18 Jan 2005 15:07:39 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 18 Jan 2005 15:07:39 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id j0IF7cIr018311 for ; Tue, 18 Jan 2005 16:07:38 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id j0IF7cVu018310 for current@freebsd.org; Tue, 18 Jan 2005 16:07:38 +0100 (CET) (envelope-from pho) Date: Tue, 18 Jan 2005 16:07:38 +0100 From: Peter Holm To: current@freebsd.org Message-ID: <20050118150738.GA18298@peter.osted.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: panic: receive: m == 0 so->so_rcv.sb_cc == 4294967295 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 15:07:41 -0000 With GENERIC HEAD from Jan 17 03:57 UTC I got a panic: receive: m == 0 so->so_rcv.sb_cc == 4294967295 in kern/uipc_socket.c:1017 panic(c0829941,0,ffffffff,c1e28578,c0826e09) at panic+0xd8 soreceive(c1e28510,0,cf6f0c90,0,0) at soreceive+0x54c fifo_read_f(c2182044,cf6f0c90,c203f800,0,c25235c0) at fifo_read_f+0x47 dofileread(3,bfbfdaf7,1,ffffffff,ffffffff) at dofileread+0x82 read(c25235c0,cf6f0d14,3,10,202) at read+0x44 syscall(2f,2f,2f,bfbfdb30,80a1c00) at syscall+0x128 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (3, FreeBSD ELF32, read), eip = 0x8064c77, esp = 0xbfbfdadc, ebp = 0xbfbfdaf8 --- More info at http://www.holm.cc/stress/log/cons108.html -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 15:12:20 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D045416A4CE; Tue, 18 Jan 2005 15:12:20 +0000 (GMT) Received: from dgap-gw.mipt.ru (dgap-gw.mipt.ru [194.85.81.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 485C743D41; Tue, 18 Jan 2005 15:12:20 +0000 (GMT) (envelope-from nepal@nas.dgap.mipt.ru) Received: from localhost (unknown [127.0.0.1]) by dgap-gw.mipt.ru (Postfix) with ESMTP id 7DC9A60D9A06; Tue, 18 Jan 2005 18:08:16 +0300 (MSK) Received: from dgap-gw.mipt.ru ([127.0.0.1]) by localhost (dgap-gw.mipt.ru [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16331-09; Tue, 18 Jan 2005 18:08:07 +0300 (MSK) Received: from nas.dgap.mipt.ru (nas.dgap.mipt.ru [194.85.81.203]) by dgap-gw.mipt.ru (Postfix) with ESMTP id E80CA60D9A01; Tue, 18 Jan 2005 18:08:07 +0300 (MSK) Received: from nas.dgap.mipt.ru (localhost [127.0.0.1]) by nas.dgap.mipt.ru (8.12.9p2/8.12.9) with ESMTP id j0IFH8f3026727; Tue, 18 Jan 2005 18:17:08 +0300 (MSK) (envelope-from nepal@nas.dgap.mipt.ru) Received: (from nepal@localhost) by nas.dgap.mipt.ru (8.12.9p2/8.12.9/Submit) id j0IFH8vL026726; Tue, 18 Jan 2005 18:17:08 +0300 (MSK) (envelope-from nepal) Date: Tue, 18 Jan 2005 18:17:07 +0300 From: "Andrew L. Neporada" To: Emanuel Strobl Message-ID: <20050118151707.GA26651@nas.dgap.mipt.ru> References: <200501181306.49120.emanuel.strobl@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200501181306.49120.emanuel.strobl@gmx.net> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new-20030616-p8 (Gentoo) at dgap.mipt.ru X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=7.5 tests= X-Spam-Level: cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 15:12:21 -0000 On Tue, Jan 18, 2005 at 01:06:43PM +0100, Emanuel Strobl wrote: > Dear experts, > > I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working the > other one not (I hate to say it but both are working under win). > > The not working (more expensive) one gets recognized as ucom0 and I have > ucom0, also I can receive signal but not transmit. > [skip] Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch http://gate.intercaf.ru/~lesha/6100/pl2303x.patch It can break old (working) PL2303 chip, but it works for me with newer revision chip (tested under 4.10). > > -Harry Andrew. From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 18:08:43 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D70716A54A for ; Tue, 18 Jan 2005 18:08:41 +0000 (GMT) Received: from mail27.sea5.speakeasy.net (mail25.sea5.speakeasy.net [69.17.117.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F6F943D39 for ; Tue, 18 Jan 2005 18:08:41 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 30895 invoked from network); 18 Jan 2005 18:08:41 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) AES256-SHA encrypted SMTP for ; 18 Jan 2005 18:08:40 -0000 Received: from [10.50.40.202] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j0II8W6J097728; Tue, 18 Jan 2005 13:08:37 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Tue, 18 Jan 2005 11:12:55 -0500 User-Agent: KMail/1.6.2 References: <20050116044737.B13189@bahre.achedra.org> <20050116163107.R13189@bahre.achedra.org> In-Reply-To: <20050116163107.R13189@bahre.achedra.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501181112.55266.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: "Ketrien I. Saihr-Kenchedra" cc: current@FreeBSD.org Subject: Re: LOR in Jan16 -CUR, ACPI related possibly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 18:08:44 -0000 On Sunday 16 January 2005 04:37 pm, Ketrien I. Saihr-Kenchedra wrote: > Yes yes, bad form to reply to myself, I know. Managed to salvage the LOR > from logs. (Filesystems were an unholy mess.) > > ukphy0: detached > miibus0: detached > lock order reversal > 1st 0xc1f3a790 pcn0 (network driver) @ > /usr/src/sys/modules/pcn/../../pci/if_pcn.c:1385 2nd 0xc08b02c0 ACPI root > bus (ACPI root bus) @ > /usr/src/sys/modules/acpi/acpi/../../../dev/acpica/acpi.c:1050 KDB: stack > backtrace: > witness_checkorder(c08b02c0,9,c08aa6b7,41a,c0700795) at > witness_checkorder+0x5c6 _sx_xlock(c08b02c0,c08aa6b7,41a,1,c1c59380) at > _sx_xlock+0x5d > acpi_release_resource(c1c58600,c1c59380,1,0,c1d13a00) at > acpi_release_resource+0x30 > resource_list_release(c1c59a84,c1ccf100,c1c59380,1,0,c1d13a00) at > resource_list_release+0x125 > bus_generic_rl_release_resource(c1ccf100,c1c59380,1,0,c1d13a00) at > bus_generic_rl_release_resource+0x7b > bus_release_resource(c1c59380,1,0,c1d13a00,c1c59380) at > bus_release_resource+0x6b > pcn_detach(c1c59380,c1cb2850,c073606c,933,c3e5b9f0) at pcn_detach+0x17b > device_detach(c1c59380,c3e5a759,c1e79540,1,c1c1fa00) at device_detach+0x99 > devclass_delete_driver(c1c1fa00,c3e5b9f0,1f2,0,c212db80) at > devclass_delete_driver+0xd1 driver_module_handler(c212db80,1,c3e5b9dc) at > driver_module_handler+0xe2 module_unload(c212db80,0,1f2,c21a5400,c07001e5) > at module_unload+0x68 linker_file_unload(c21a5400,0,c07001ee,31e,bfbfe8a0) > at linker_file_unload+0x29d kern_kldunload(0,db2f7d14,8,3ff,2) at > kern_kldunload+0x8c > syscall(2f,2f,2f,3,bfbfee16) at syscall+0x137 > Xint0x80_syscall() at Xint0x80_syscall+0x1f > --- syscall (444, FreeBSD ELF32, kldunloadf), eip = 0x280c459f, esp = > 0xbfbfe89c, ebp = 0xbfbfed10 --- pcn0: detached This is because the driver (pcn) in this case is holding a lock across bus_release_resoruce() when it probably should not be. I get the same LOR with radeondrm because it holds the lock across bus_teardown_intr() (which is definitely wrong since that can sleep). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 18:08:43 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B1ED16A4EC for ; Tue, 18 Jan 2005 18:08:41 +0000 (GMT) Received: from mail27.sea5.speakeasy.net (mail25.sea5.speakeasy.net [69.17.117.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F86443D49 for ; Tue, 18 Jan 2005 18:08:41 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 30895 invoked from network); 18 Jan 2005 18:08:41 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) AES256-SHA encrypted SMTP for ; 18 Jan 2005 18:08:40 -0000 Received: from [10.50.40.202] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j0II8W6J097728; Tue, 18 Jan 2005 13:08:37 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Tue, 18 Jan 2005 11:12:55 -0500 User-Agent: KMail/1.6.2 References: <20050116044737.B13189@bahre.achedra.org> <20050116163107.R13189@bahre.achedra.org> In-Reply-To: <20050116163107.R13189@bahre.achedra.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501181112.55266.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: "Ketrien I. Saihr-Kenchedra" cc: current@FreeBSD.org Subject: Re: LOR in Jan16 -CUR, ACPI related possibly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 18:08:44 -0000 On Sunday 16 January 2005 04:37 pm, Ketrien I. Saihr-Kenchedra wrote: > Yes yes, bad form to reply to myself, I know. Managed to salvage the LOR > from logs. (Filesystems were an unholy mess.) > > ukphy0: detached > miibus0: detached > lock order reversal > 1st 0xc1f3a790 pcn0 (network driver) @ > /usr/src/sys/modules/pcn/../../pci/if_pcn.c:1385 2nd 0xc08b02c0 ACPI root > bus (ACPI root bus) @ > /usr/src/sys/modules/acpi/acpi/../../../dev/acpica/acpi.c:1050 KDB: stack > backtrace: > witness_checkorder(c08b02c0,9,c08aa6b7,41a,c0700795) at > witness_checkorder+0x5c6 _sx_xlock(c08b02c0,c08aa6b7,41a,1,c1c59380) at > _sx_xlock+0x5d > acpi_release_resource(c1c58600,c1c59380,1,0,c1d13a00) at > acpi_release_resource+0x30 > resource_list_release(c1c59a84,c1ccf100,c1c59380,1,0,c1d13a00) at > resource_list_release+0x125 > bus_generic_rl_release_resource(c1ccf100,c1c59380,1,0,c1d13a00) at > bus_generic_rl_release_resource+0x7b > bus_release_resource(c1c59380,1,0,c1d13a00,c1c59380) at > bus_release_resource+0x6b > pcn_detach(c1c59380,c1cb2850,c073606c,933,c3e5b9f0) at pcn_detach+0x17b > device_detach(c1c59380,c3e5a759,c1e79540,1,c1c1fa00) at device_detach+0x99 > devclass_delete_driver(c1c1fa00,c3e5b9f0,1f2,0,c212db80) at > devclass_delete_driver+0xd1 driver_module_handler(c212db80,1,c3e5b9dc) at > driver_module_handler+0xe2 module_unload(c212db80,0,1f2,c21a5400,c07001e5) > at module_unload+0x68 linker_file_unload(c21a5400,0,c07001ee,31e,bfbfe8a0) > at linker_file_unload+0x29d kern_kldunload(0,db2f7d14,8,3ff,2) at > kern_kldunload+0x8c > syscall(2f,2f,2f,3,bfbfee16) at syscall+0x137 > Xint0x80_syscall() at Xint0x80_syscall+0x1f > --- syscall (444, FreeBSD ELF32, kldunloadf), eip = 0x280c459f, esp = > 0xbfbfe89c, ebp = 0xbfbfed10 --- pcn0: detached This is because the driver (pcn) in this case is holding a lock across bus_release_resoruce() when it probably should not be. I get the same LOR with radeondrm because it holds the lock across bus_teardown_intr() (which is definitely wrong since that can sleep). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 18:08:44 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C2FE16A4D4 for ; Tue, 18 Jan 2005 18:08:44 +0000 (GMT) Received: from mail15.speakeasy.net (mail23.sea5.speakeasy.net [69.17.117.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 458C843D55 for ; Tue, 18 Jan 2005 18:08:44 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 28230 invoked from network); 18 Jan 2005 18:08:44 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 18 Jan 2005 18:08:43 -0000 Received: from [10.50.40.202] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j0II8W6K097728; Tue, 18 Jan 2005 13:08:39 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Tue, 18 Jan 2005 11:24:19 -0500 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501181124.19323.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: "Bjoern A. Zeeb" cc: FreeBSD current mailing list Subject: Re: LOR: kern_descrip.c:2277,2278 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 18:08:44 -0000 On Monday 17 January 2005 05:07 pm, Bjoern A. Zeeb wrote: > Hi, > > I have added the following as LOR #055 to "the LOR page"[1]. > > lock order reversal > 1st 0xffffffff80c3a9e8 sleep mtxpool (sleep mtxpool) @ > sys/kern/kern_descrip.c:2277 2nd 0xffffff00222d8a48 filedesc structure > (filedesc structure) @ sys/kern/kern_descrip.c:2278 KDB: stack backtrace: > witness_checkorder() at witness_checkorder+0x5f1 > _mtx_lock_flags() at _mtx_lock_flags+0x4a > dupfdopen() at dupfdopen+0x320 > kern_open() at kern_open+0x5de > syscall() at syscall+0x4ab > Xfast_syscall() at Xfast_syscall+0xa8 > --- syscall (5, FreeBSD ELF64, open), rip = 0x80077e7d0, rsp = > 0x7fffffffe6f8, rbp = 0x7fffffffec70 --- > > I can easily reproduce it every boot. It seems to be triggered by > Capi4BSD[2] framework which I incorporated in my private tree. > > Can someone please comment on this ? The problem is that FILEDESC_UNLOCK() actually includes an entirely separate lock of its own (it's like an sx lock sort of). One possible fix might be to change struct file to either use a dedicated mutex pool (instead of the more generic mtxpool_sleep one that is intended only for leaf-lock usage) or to have each struct file include its own mutex rather than using a pool lock. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 18:08:44 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F1A916A4DD for ; Tue, 18 Jan 2005 18:08:44 +0000 (GMT) Received: from mail15.speakeasy.net (mail23.sea5.speakeasy.net [69.17.117.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45A3843D58 for ; Tue, 18 Jan 2005 18:08:44 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 28230 invoked from network); 18 Jan 2005 18:08:44 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 18 Jan 2005 18:08:43 -0000 Received: from [10.50.40.202] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id j0II8W6K097728; Tue, 18 Jan 2005 13:08:39 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Tue, 18 Jan 2005 11:24:19 -0500 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501181124.19323.jhb@FreeBSD.org> X-Spam-Status: No, score=-102.8 required=4.2 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx cc: "Bjoern A. Zeeb" cc: FreeBSD current mailing list Subject: Re: LOR: kern_descrip.c:2277,2278 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 18:08:45 -0000 On Monday 17 January 2005 05:07 pm, Bjoern A. Zeeb wrote: > Hi, > > I have added the following as LOR #055 to "the LOR page"[1]. > > lock order reversal > 1st 0xffffffff80c3a9e8 sleep mtxpool (sleep mtxpool) @ > sys/kern/kern_descrip.c:2277 2nd 0xffffff00222d8a48 filedesc structure > (filedesc structure) @ sys/kern/kern_descrip.c:2278 KDB: stack backtrace: > witness_checkorder() at witness_checkorder+0x5f1 > _mtx_lock_flags() at _mtx_lock_flags+0x4a > dupfdopen() at dupfdopen+0x320 > kern_open() at kern_open+0x5de > syscall() at syscall+0x4ab > Xfast_syscall() at Xfast_syscall+0xa8 > --- syscall (5, FreeBSD ELF64, open), rip = 0x80077e7d0, rsp = > 0x7fffffffe6f8, rbp = 0x7fffffffec70 --- > > I can easily reproduce it every boot. It seems to be triggered by > Capi4BSD[2] framework which I incorporated in my private tree. > > Can someone please comment on this ? The problem is that FILEDESC_UNLOCK() actually includes an entirely separate lock of its own (it's like an sx lock sort of). One possible fix might be to change struct file to either use a dedicated mutex pool (instead of the more generic mtxpool_sleep one that is intended only for leaf-lock usage) or to have each struct file include its own mutex rather than using a pool lock. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 18:31:53 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 768BF16A4CE; Tue, 18 Jan 2005 18:31:53 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1727043D1D; Tue, 18 Jan 2005 18:31:53 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j0IIZxHT019848; Tue, 18 Jan 2005 10:35:59 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j0IIZxuN019847; Tue, 18 Jan 2005 10:35:59 -0800 Date: Tue, 18 Jan 2005 10:35:59 -0800 From: Brooks Davis To: Gleb Smirnoff Message-ID: <20050118183558.GA15150@odin.ac.hmc.edu> References: <20050117200610.GA90866@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050117200610.GA90866@cell.sick.ru> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: current@freebsd.org cc: net@freebsd.org Subject: Re: [TEST/REVIEW] ng_ipfw: node to glue together ipfw(4) and netgraph(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 18:31:53 -0000 On Mon, Jan 17, 2005 at 11:06:10PM +0300, Gleb Smirnoff wrote: > Dear collegues, > > here is quite a simple node for direct interaction between ipfw(4) > and netgraph(4). It is going to be more effective and error-prone > than a complicated construction around divert socket and ng_ksocket[1]. > > The semantics of node operation are quite simple. There is one node > per system, which accepts any hooks with numeric names. Packets > can be sent to netgraph(4) using ipfw 'netgraph' action, followed > by a numeric cookie. Matched packets are sent out from corresponding > hook of ng_ipfw node. These packets are tagged with information which > helps them later to reenter ipfw processing. Tagged packets received on > any node hook reenter IP stack. If net.inet.ip.fw.one_pass sysctl is non > zero they are accepted, otherwise they continue with next rule. Non-tagged > packets (not originating from ng_ipfw node) are discarded. > > Here is sample configuration. ng_echo(4) echoes packets back from netgraph > to ipfw thru a tee node, which allows to sniff traffic. > > ngctl > + ls > There are 4 total nodes: > Name: ngctl6138 Type: socket ID: 0000000c Num hooks: 0 > Name: ipfw Type: ipfw ID: 00000009 Num hooks: 1 > Name: Type: echo ID: 00000006 Num hooks: 1 > Name: tee Type: tee ID: 00000005 Num hooks: 2 > + show ipfw: > Name: ipfw Type: ipfw ID: 00000009 Num hooks: 1 > Local hook Peer name Peer type Peer ID Peer hook > ---------- --------- --------- ------- --------- > 666 tee tee 00000005 left > + show tee: > Name: tee Type: tee ID: 00000005 Num hooks: 2 > Local hook Peer name Peer type Peer ID Peer hook > ---------- --------- --------- ------- --------- > left ipfw ipfw 00000009 666 > right echo 00000006 echi > > root@jujik:/usr/src:|>ipfw show > 00100 292 40304 allow ip from any to any via lo0 > 00200 0 0 deny ip from any to 127.0.0.0/8 > 00300 0 0 deny ip from 127.0.0.0/8 to any > 00350 290730 661428793 netgraph 666 ip from any to any > 65000 627921 1896034399 allow ip from any to any > 65535 0 0 deny ip from any to any > > The patch [2] is applicable only to HEAD, sorry. The target users are > the ones, who are now running ip_accounting/netflow using diverted > ng_ksocket, and just netgraph geeks. I like the idea and I've glanced at the patch. You should put the new op-code at the end of the list to avoid breaking the IPFW ABI. There should probably be a comment about this in ip_fw.h. -- Brooks From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 19:22:17 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F81A16A4CE; Tue, 18 Jan 2005 19:22:17 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECEAF43D53; Tue, 18 Jan 2005 19:22:16 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from error404.nls.net (ketrien@error404.nls.net [216.144.36.24]) by error404.nls.net (8.13.1/8.13.1) with ESMTP id j0IJNO06004483; Tue, 18 Jan 2005 14:23:24 -0500 (EST) (envelope-from ketrien@error404.nls.net) Date: Tue, 18 Jan 2005 14:23:24 -0500 (EST) From: "Ketrien I. Saihr-Kenchedra" X-X-Sender: ketrien@bahre.achedra.org To: John Baldwin In-Reply-To: <200501181112.55266.jhb@FreeBSD.org> Message-ID: <20050118141527.B1832@bahre.achedra.org> References: <20050116044737.B13189@bahre.achedra.org> <20050116163107.R13189@bahre.achedra.org> <200501181112.55266.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV 0.80/671/Mon Jan 17 09:16:31 2005 clamav-milter version 0.80j on bahre.achedra.org X-Virus-Status: Clean cc: freebsd-current@FreeBSD.org cc: current@FreeBSD.org Subject: Re: LOR in Jan16 -CUR, ACPI related possibly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 19:22:17 -0000 On Tue, 18 Jan 2005, John Baldwin wrote: > This is because the driver (pcn) in this case is holding a lock across > bus_release_resoruce() when it probably should not be. I get the same LOR > with radeondrm because it holds the lock across bus_teardown_intr() (which is > definitely wrong since that can sleep). Indeed, this patch will fix it. I should've seen it, but I've been fighting a timing issue in probe() on the Am79C975's. *** if_pcn.c.orig Tue Jan 18 14:17:54 2005 --- if_pcn.c Tue Jan 18 14:18:26 2005 *************** *** 619,624 **** --- 619,626 ---- pcn_stop(sc); ether_ifdetach(ifp); } + PCN_UNLOCK(sc); + if (sc->pcn_miibus) device_delete_child(dev, sc->pcn_miibus); bus_generic_detach(dev); *************** *** 634,640 **** contigfree(sc->pcn_ldata, sizeof(struct pcn_list_data), M_DEVBUF); } - PCN_UNLOCK(sc); mtx_destroy(&sc->pcn_mtx); --- 636,641 ---- -Ketrien I. Saihr-Kenchedra From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 19:22:17 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F81A16A4CE; Tue, 18 Jan 2005 19:22:17 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECEAF43D53; Tue, 18 Jan 2005 19:22:16 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from error404.nls.net (ketrien@error404.nls.net [216.144.36.24]) by error404.nls.net (8.13.1/8.13.1) with ESMTP id j0IJNO06004483; Tue, 18 Jan 2005 14:23:24 -0500 (EST) (envelope-from ketrien@error404.nls.net) Date: Tue, 18 Jan 2005 14:23:24 -0500 (EST) From: "Ketrien I. Saihr-Kenchedra" X-X-Sender: ketrien@bahre.achedra.org To: John Baldwin In-Reply-To: <200501181112.55266.jhb@FreeBSD.org> Message-ID: <20050118141527.B1832@bahre.achedra.org> References: <20050116044737.B13189@bahre.achedra.org> <20050116163107.R13189@bahre.achedra.org> <200501181112.55266.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV 0.80/671/Mon Jan 17 09:16:31 2005 clamav-milter version 0.80j on bahre.achedra.org X-Virus-Status: Clean cc: freebsd-current@FreeBSD.org cc: current@FreeBSD.org Subject: Re: LOR in Jan16 -CUR, ACPI related possibly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 19:22:17 -0000 On Tue, 18 Jan 2005, John Baldwin wrote: > This is because the driver (pcn) in this case is holding a lock across > bus_release_resoruce() when it probably should not be. I get the same LOR > with radeondrm because it holds the lock across bus_teardown_intr() (which is > definitely wrong since that can sleep). Indeed, this patch will fix it. I should've seen it, but I've been fighting a timing issue in probe() on the Am79C975's. *** if_pcn.c.orig Tue Jan 18 14:17:54 2005 --- if_pcn.c Tue Jan 18 14:18:26 2005 *************** *** 619,624 **** --- 619,626 ---- pcn_stop(sc); ether_ifdetach(ifp); } + PCN_UNLOCK(sc); + if (sc->pcn_miibus) device_delete_child(dev, sc->pcn_miibus); bus_generic_detach(dev); *************** *** 634,640 **** contigfree(sc->pcn_ldata, sizeof(struct pcn_list_data), M_DEVBUF); } - PCN_UNLOCK(sc); mtx_destroy(&sc->pcn_mtx); --- 636,641 ---- -Ketrien I. Saihr-Kenchedra From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 19:32:47 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CA2416A4CE for ; Tue, 18 Jan 2005 19:32:47 +0000 (GMT) Received: from aslan.scsiguy.com (mail.scsiguy.com [63.229.232.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59E6D43D1D for ; Tue, 18 Jan 2005 19:32:46 +0000 (GMT) (envelope-from gibbs@scsiguy.com) Received: from [10.0.0.90] (oriondc.dsl.frii.net [216.17.137.18]) (authenticated bits=0) by aslan.scsiguy.com (8.13.1/8.13.1) with ESMTP id j0IJWhWC092220 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Jan 2005 12:32:45 -0700 (MST) (envelope-from gibbs@scsiguy.com) Date: Tue, 18 Jan 2005 12:32:38 -0700 From: "Justin T. Gibbs" To: Cameron Murdoch , current@freebsd.org Message-ID: <68E667C50A598BCADAE91247@[10.0.0.90]> In-Reply-To: <41EAE1A2.4010308@macaroon.net> References: <41EAE1A2.4010308@macaroon.net> X-Mailer: Mulberry/3.1.6 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: Adaptec 39320A "Card was not paused" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: "Justin T. Gibbs" List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 19:32:47 -0000 > I am having a problem with an adaptec 39320A SCSI card accessing an > external raid box, (JetStor III 416S). > > Host computer is a Dell PowerEdge2650 with a single processor. > > 6-CURRENT from Saturday has the following relevant dmesg: The card state dump indicates that the controller is stuck with ACK asserted. In packetized operation, this should not normally occur. Without a SCSI bus trace, however, it will be difficult to diagnose the error. I don't suppose you can borrow or rent a U320 analyzer? -- Justin From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 20:32:29 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59C2816A4CE for ; Tue, 18 Jan 2005 20:32:29 +0000 (GMT) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AF5943D2D for ; Tue, 18 Jan 2005 20:32:29 +0000 (GMT) (envelope-from alc@cs.rice.edu) Received: from localhost (calypso.cs.rice.edu [128.42.1.127]) by cs.rice.edu (Postfix) with ESMTP id DC3C74A9B4; Tue, 18 Jan 2005 14:32:28 -0600 (CST) Received: from cs.rice.edu ([128.42.1.30]) by localhost (calypso.cs.rice.edu [128.42.1.127]) (amavisd-new, port 10024) with LMTP id 31872-01-54; Tue, 18 Jan 2005 14:32:28 -0600 (CST) Received: from noel.cs.rice.edu (noel.cs.rice.edu [128.42.1.136]) by cs.rice.edu (Postfix) with ESMTP id 5C0304A99D; Tue, 18 Jan 2005 14:32:28 -0600 (CST) Received: (from alc@localhost) by noel.cs.rice.edu (8.12.10+Sun/8.12.9/Submit) id j0IKVrF7009074; Tue, 18 Jan 2005 14:31:53 -0600 (CST) Date: Tue, 18 Jan 2005 14:31:53 -0600 From: Alan Cox To: Kris Kennaway Message-ID: <20050118203153.GM3194@noel.cs.rice.edu> References: <20050115083847.GA47466@xor.obsecurity.org> <20050116003432.GA448@xor.obsecurity.org> <20050116050433.GA65733@xor.obsecurity.org> <20050116211349.GG26214@noel.cs.rice.edu> <20050117014746.GA96797@xor.obsecurity.org> <20050117021815.GA8953@xor.obsecurity.org> <20050117023031.GA12825@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050117023031.GA12825@xor.obsecurity.org> User-Agent: Mutt/1.3.28i X-Virus-Scanned: by amavis-20030616-p7 at cs.rice.edu cc: Alan Cox cc: current@freebsd.org Subject: Re: fstat triggered INVARIANTS panic in memrw() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 20:32:29 -0000 On Sun, Jan 16, 2005 at 06:30:31PM -0800, Kris Kennaway wrote: > On Sun, Jan 16, 2005 at 06:18:15PM -0800, Kris Kennaway wrote: > > On Sun, Jan 16, 2005 at 05:47:46PM -0800, Kris Kennaway wrote: > > > On Sun, Jan 16, 2005 at 03:13:49PM -0600, Alan Cox wrote: > > > > > > > The "deadc0de" passed to generic_copyout() comes from the following > > > > lines in devfs_read_f(c51773b8,eed96c84,ca75c800,flags=0): > > > > > > > > if ((flags & FOF_OFFSET) == 0) > > > > uio->uio_offset = fp->f_offset; > > > > > > > > Can you print the contents of the file structure? > > > > > > (kgdb) frame 28 > > > #28 0xc04d8d91 in devfs_read_f (fp=0xc25f5dd0, uio=0xe7275c84, cred=0xc3540380, flags=0, td=0xc3c34170) > > > at ../../../fs/devfs/devfs_vnops.c:931 > > > 931 error = dsw->d_read(dev, uio, ioflag); > > > (kgdb) print *fp > > > $1 = {f_list = {le_next = 0xc25f5bf4, le_prev = 0xc25f52a8}, f_type = 1, f_data = 0xc22f8200, f_flag = 1, > > > f_mtxp = 0xc2251fd0, f_ops = 0xc074c140, f_cred = 0xc2b2a900, f_count = 2, f_vnode = 0xc3c6fbdc, > > > f_offset = 3735929054, f_gcflag = 0, f_msgcount = 0, f_seqcount = 1, f_nextoff = 3263609792} > > > > 3735929054 = 0xdeadc0de. This same struct file appears all the way > > back to the syscall frame. I wonder if fstat is racing with a tty > > device removal or something (it's certainly racing with something, > > e.g.: > > Devices may not be to blame; I was able to trigger this by running > fstat in a loop and then running 'make' in /usr/ports/misc/screen > (with the idea of testing the tty hypothesis :) > > An interesting datapoint is that none of the non-i386 package machines > have hit this problem, but the i386 machines can't stay up for more > than a few minutes under load (which translates to only a few fstat > invocations). The field f_offset is 64 bits wide. If this were a race between use and deallocation of the file structure within the kernel, then I would expect f_offset's value to be 0xdeadc0dedeadc0de, not 0x00000000deadc0de. More likely than not, the 0xdeadc0de is being passed in from user level. The i386 kernel is just not handling it gracefully. Alan From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 21:37:06 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B46D16A4CE for ; Tue, 18 Jan 2005 21:37:06 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 4B92E43D64 for ; Tue, 18 Jan 2005 21:37:05 +0000 (GMT) (envelope-from emanuel.strobl@gmx.net) Received: (qmail invoked by alias); 18 Jan 2005 21:37:04 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp027) with SMTP; 18 Jan 2005 22:37:04 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-current@freebsd.org, akiyama@jp.FreeBSD.org Date: Tue, 18 Jan 2005 22:36:48 +0100 User-Agent: KMail/1.7.2 References: <200501181306.49120.emanuel.strobl@gmx.net> <20050118151707.GA26651@nas.dgap.mipt.ru> In-Reply-To: <20050118151707.GA26651@nas.dgap.mipt.ru> X-Birthday: 10/06/72 X-CelPhone: +49 173 9967781 X-Tel: +49 89 18947781 X-Country: Germany X-Address: Munich, 80686 X-OS: FreeBSD MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1855474.mkKBfakOLZ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501182236.54005.emanuel.strobl@gmx.net> X-Y-GMX-Trusted: 0 cc: freebsd-stable@freebsd.org Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 21:37:06 -0000 --nextPart1855474.mkKBfakOLZ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Dienstag, 18. Januar 2005 16:17 schrieb Andrew L. Neporada: > On Tue, Jan 18, 2005 at 01:06:43PM +0100, Emanuel Strobl wrote: > > Dear experts, > > > > I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working > > the other one not (I hate to say it but both are working under win). > > > > The not working (more expensive) one gets recognized as ucom0 and I have > > ucom0, also I can receive signal but not transmit. > > [skip] > > Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch > http://gate.intercaf.ru/~lesha/6100/pl2303x.patch > > It can break old (working) PL2303 chip, but it works for me with newer Thanks a lot, this indeed fixes the revision 3.0 adaptor but unfortunately= =20 also breakes the 2.02 version :( Perhaps there's a goog guy out there who can refurbish the uplcom driver wi= th=20 this information (akiyama?)? Thanks a lot, =2DHarry > revision chip (tested under 4.10). > > > -Harry > > Andrew. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" --nextPart1855474.mkKBfakOLZ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB7YF1Bylq0S4AzzwRAtrNAJ9OsLjuDIEayzEDk/l7JavN57NaXwCgg0dK IAZzcVHZEq3kHRaKohgwnGQ= =VwDM -----END PGP SIGNATURE----- --nextPart1855474.mkKBfakOLZ-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 22:27:49 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BD7816A4CE; Tue, 18 Jan 2005 22:27:49 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A8D943D39; Tue, 18 Jan 2005 22:27:48 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id DCE507A403; Tue, 18 Jan 2005 14:27:47 -0800 (PST) Message-ID: <41ED8D63.8090205@elischer.org> Date: Tue, 18 Jan 2005 14:27:47 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Brooks Davis References: <20050117200610.GA90866@cell.sick.ru> <20050118183558.GA15150@odin.ac.hmc.edu> In-Reply-To: <20050118183558.GA15150@odin.ac.hmc.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Gleb Smirnoff cc: current@freebsd.org cc: net@freebsd.org Subject: Re: [TEST/REVIEW] ng_ipfw: node to glue together ipfw(4) and netgraph(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 22:27:49 -0000 Brooks Davis wrote: >On Mon, Jan 17, 2005 at 11:06:10PM +0300, Gleb Smirnoff wrote: > > >> Dear collegues, >> >>here is quite a simple node for direct interaction between ipfw(4) >>and netgraph(4). It is going to be more effective and error-prone >>than a complicated construction around divert socket and ng_ksocket[1]. >> >> >> firstly.. I was thinking that there are several good ways to mesh the ipfw/divert/netgraph stuff. Firstly there is the possibility of making the ipfw stuff a netgraph node itself.. (yes I know there is such a node (based on ipfw-1) out there.) then as for getting stuff out of ipfw, maybe divert itself could be changed to be a netgraph method. In this way, you'd open netgtraph sockets instead of divert sockets. Alternatively there could be a possibility where netgraph could open hooks of a particular number and that would be the equivalant of openning a divert hook of that number.. Looks good but I'm not convinced that it needs a whole new keyword of we tap in through the divert mechanism. From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 22:55:33 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA35C16A4CF; Tue, 18 Jan 2005 22:55:33 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 938C443D49; Tue, 18 Jan 2005 22:55:33 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j0IMxeZJ003664; Tue, 18 Jan 2005 14:59:40 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j0IMxe41003663; Tue, 18 Jan 2005 14:59:40 -0800 Date: Tue, 18 Jan 2005 14:59:40 -0800 From: Brooks Davis To: Julian Elischer Message-ID: <20050118225940.GA31663@odin.ac.hmc.edu> References: <20050117200610.GA90866@cell.sick.ru> <20050118183558.GA15150@odin.ac.hmc.edu> <41ED8D63.8090205@elischer.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ReaqsoxgOBHFXBhH" Content-Disposition: inline In-Reply-To: <41ED8D63.8090205@elischer.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: Gleb Smirnoff cc: current@freebsd.org cc: net@freebsd.org Subject: Re: [TEST/REVIEW] ng_ipfw: node to glue together ipfw(4) and netgraph(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 22:55:34 -0000 --ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 18, 2005 at 02:27:47PM -0800, Julian Elischer wrote: >=20 > Looks good but I'm not convinced that it needs a whole new keyword of > we tap in through the divert mechanism. FWIW, keywords are very cheap and generally quite clean in ipfw2. I'd be more concerned in ipfw1. -- Brooks --ReaqsoxgOBHFXBhH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFB7ZTbXY6L6fI4GtQRAsqNAJ0TRSokXVosZRrdYcpjj5kvf5IO0wCePJMA gOYqFLchzlOuvNrWr8Ro8zM= =5sTQ -----END PGP SIGNATURE----- --ReaqsoxgOBHFXBhH-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 19 02:46:59 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4625216A4CE for ; Wed, 19 Jan 2005 02:46:59 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E91DC43D60 for ; Wed, 19 Jan 2005 02:46:58 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7B6CC512CB; Tue, 18 Jan 2005 18:46:57 -0800 (PST) Date: Tue, 18 Jan 2005 18:46:57 -0800 From: Kris Kennaway To: Alan Cox Message-ID: <20050119024657.GA78197@xor.obsecurity.org> References: <20050115083847.GA47466@xor.obsecurity.org> <20050116003432.GA448@xor.obsecurity.org> <20050116050433.GA65733@xor.obsecurity.org> <20050116211349.GG26214@noel.cs.rice.edu> <20050117014746.GA96797@xor.obsecurity.org> <20050117021815.GA8953@xor.obsecurity.org> <20050117023031.GA12825@xor.obsecurity.org> <20050118203153.GM3194@noel.cs.rice.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jI8keyz6grp/JLjh" Content-Disposition: inline In-Reply-To: <20050118203153.GM3194@noel.cs.rice.edu> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org cc: Kris Kennaway Subject: Re: fstat triggered INVARIANTS panic in memrw() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 02:46:59 -0000 --jI8keyz6grp/JLjh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 18, 2005 at 02:31:53PM -0600, Alan Cox wrote: > > An interesting datapoint is that none of the non-i386 package machines > > have hit this problem, but the i386 machines can't stay up for more > > than a few minutes under load (which translates to only a few fstat > > invocations). >=20 > The field f_offset is 64 bits wide. If this were a race between use > and deallocation of the file structure within the kernel, then I would > expect f_offset's value to be 0xdeadc0dedeadc0de, not > 0x00000000deadc0de. More likely than not, the 0xdeadc0de is being > passed in from user level. The i386 kernel is just not handling it > gracefully. =20 Shouldn't this at least be hitting the check in memrw(): if (!kernacc((caddr_t)(int)uio->uio_offset, c, uio->uio_rw =3D=3D UIO_READ ? VM_PROT_READ : VM_PROT_WRITE)) return (EFAULT); error =3D uiomove((caddr_t)(int)uio->uio_offset, (i= nt)c, uio); (kgdb) print uio->uio_offset $2 =3D 3735929054 (kgdb) print uio->uio_rw $3 =3D UIO_READ (kgdb) print c $4 =3D 2058814332 Kris --jI8keyz6grp/JLjh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB7cohWry0BWjoQKURApooAJ9KlFXGpVSqaiYJ28IFnnb57i0SIgCeIOO0 wAYlZUacSlbFtFmnt51b5Vo= =Spg/ -----END PGP SIGNATURE----- --jI8keyz6grp/JLjh-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 19 05:02:57 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E17DB16A4CE for ; Wed, 19 Jan 2005 05:02:57 +0000 (GMT) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id B220A43D5A for ; Wed, 19 Jan 2005 05:02:57 +0000 (GMT) (envelope-from alc@cs.rice.edu) Received: from localhost (calypso.cs.rice.edu [128.42.1.127]) by cs.rice.edu (Postfix) with ESMTP id DB87B4AA7B; Tue, 18 Jan 2005 23:02:56 -0600 (CST) Received: from cs.rice.edu ([128.42.1.30]) by localhost (calypso.cs.rice.edu [128.42.1.127]) (amavisd-new, port 10024) with LMTP id 17748-01-24; Tue, 18 Jan 2005 23:02:56 -0600 (CST) Received: from noel.cs.rice.edu (noel.cs.rice.edu [128.42.1.136]) by cs.rice.edu (Postfix) with ESMTP id E3FC94AA78; Tue, 18 Jan 2005 23:02:55 -0600 (CST) Received: (from alc@localhost) by noel.cs.rice.edu (8.12.10+Sun/8.12.9/Submit) id j0J52K9G009898; Tue, 18 Jan 2005 23:02:20 -0600 (CST) Date: Tue, 18 Jan 2005 23:02:20 -0600 From: Alan Cox To: Kris Kennaway Message-ID: <20050119050220.GU3194@noel.cs.rice.edu> References: <20050115083847.GA47466@xor.obsecurity.org> <20050116003432.GA448@xor.obsecurity.org> <20050116050433.GA65733@xor.obsecurity.org> <20050116211349.GG26214@noel.cs.rice.edu> <20050117014746.GA96797@xor.obsecurity.org> <20050117021815.GA8953@xor.obsecurity.org> <20050117023031.GA12825@xor.obsecurity.org> <20050118203153.GM3194@noel.cs.rice.edu> <20050119024657.GA78197@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050119024657.GA78197@xor.obsecurity.org> User-Agent: Mutt/1.3.28i X-Virus-Scanned: by amavis-20030616-p7 at cs.rice.edu cc: Alan Cox cc: current@freebsd.org cc: krentel@dreamscape.com Subject: Re: fstat triggered INVARIANTS panic in memrw() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 05:02:58 -0000 On Tue, Jan 18, 2005 at 06:46:57PM -0800, Kris Kennaway wrote: > On Tue, Jan 18, 2005 at 02:31:53PM -0600, Alan Cox wrote: > > > > An interesting datapoint is that none of the non-i386 package machines > > > have hit this problem, but the i386 machines can't stay up for more > > > than a few minutes under load (which translates to only a few fstat > > > invocations). > > > > The field f_offset is 64 bits wide. If this were a race between use > > and deallocation of the file structure within the kernel, then I would > > expect f_offset's value to be 0xdeadc0dedeadc0de, not > > 0x00000000deadc0de. More likely than not, the 0xdeadc0de is being > > passed in from user level. The i386 kernel is just not handling it > > gracefully. > > Shouldn't this at least be hitting the check in memrw(): > > if (!kernacc((caddr_t)(int)uio->uio_offset, c, > uio->uio_rw == UIO_READ ? > VM_PROT_READ : VM_PROT_WRITE)) > return (EFAULT); > error = uiomove((caddr_t)(int)uio->uio_offset, (int)c, uio); > > (kgdb) print uio->uio_offset > $2 = 3735929054 > (kgdb) print uio->uio_rw > $3 = UIO_READ > (kgdb) print c > $4 = 2058814332 Yes, it should. :-) The problem is two-fold. First, kernacc() unlike useracc() doesn't check for address wrap, i.e., end < start. Presumably the author of kernacc() assumed that kernel code would never call kernacc() with such dubious arguments. Second, vm_map_check_protection() returns "success" whenever address wrap occurs. Alan From owner-freebsd-current@FreeBSD.ORG Wed Jan 19 05:32:22 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D23A16A4CE for ; Wed, 19 Jan 2005 05:32:22 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id B55C343D2F for ; Wed, 19 Jan 2005 05:32:21 +0000 (GMT) (envelope-from kjelderg@gmail.com) Received: by rproxy.gmail.com with SMTP id j1so9365rnf for ; Tue, 18 Jan 2005 21:32:21 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references; b=nmjYBKCOE9hbHy4HooVaeSwqudQj5If0B2dfdx6HXsfmC9xLzuz6xaRmq62lZOMRr26Qf2yxvbmDijaG+frxCP3M6G70ND3oFcuWVdtWO4WEAOYQpYo8CpyFDiqJWpAYHgaEl/Y1HZyz1DPuXTPt4jL5XVvo6PNr1fnjkjBvoA0= Received: by 10.38.11.19 with SMTP id 19mr134711rnk; Tue, 18 Jan 2005 21:32:21 -0800 (PST) Received: by 10.38.101.3 with HTTP; Tue, 18 Jan 2005 21:32:20 -0800 (PST) Message-ID: Date: Tue, 18 Jan 2005 23:32:20 -0600 From: Eric Kjeldergaard To: current@freebsd.org In-Reply-To: <20050110131529.GA716@loge.nixsys.be> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_710_33516875.1106112740992" References: <20050110131529.GA716@loge.nixsys.be> Subject: Re: [PLEASE TEST] Many improvements to Synaptics support in psm(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Eric Kjeldergaard List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 05:32:22 -0000 ------=_Part_710_33516875.1106112740992 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline > I just committed a patch to -current which greatly improves support in psm(4) > for Synaptics touchpads. Owners of these gadgets are encouraged to test this. > If it turns out to work well, I'll enable support by default. > > For now, to get the new behaviour, you need to set hw.psm.synaptics_support=1 > in /boot/loader.conf. > > Please also fiddle with the stickiness sysctls. The quest for finding perfect > values is still on... [snip] > o Add a number of sysctls allowing one to tune the driver to taste in > a simple way: > > # Should the extra buttons act as axes or as middle button > hw.psm.synaptics.directional_scrolls Well, trying to test this little setting here. Seems like it would be great to get horiz and vert scroll working, and since I saw this mail message go through, I thought I'd help test. Perhaps I'm doing something really dumb, but I can't seem to get scrolling going on this with the new psm at all. I'm attaching my xorg.conf in case it's something in there. I've got the directional_scrolls variable set to 1. The mouse works and the other settings have been acting exactly as expected. I've tried to get scrolling working both the way that's in the xorg.conf and just "Buttons" "5", "ZAxisMapping" "4 5" which is what I use with more "traditional" scrolling mice. Any hints would be much appreciated. I can send any other information that is desired. -- If I write a signature, my emails will appear more personalised. ------=_Part_710_33516875.1106112740992 Content-Type: application/octet-stream; name="xorg.conf" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="xorg.conf" IyBGaWxlIGdlbmVyYXRlZCBieSB4Zjg2Y29uZmlnLgoKIwojIENvcHlyaWdodCAoYykgMjAwNCwg YnkgdGhlIFguT3JnCiMKIyBQZXJtaXNzaW9uIGlzIGhlcmVieSBncmFudGVkLCBmcmVlIG9mIGNo YXJnZSwgdG8gYW55IHBlcnNvbiBvYnRhaW5pbmcgYQojIGNvcHkgb2YgdGhpcyBzb2Z0d2FyZSBh bmQgYXNzb2NpYXRlZCBkb2N1bWVudGF0aW9uIGZpbGVzICh0aGUgIlNvZnR3YXJlIiksCiMgdG8g ZGVhbCBpbiB0aGUgU29mdHdhcmUgd2l0aG91dCByZXN0cmljdGlvbiwgaW5jbHVkaW5nIHdpdGhv dXQgbGltaXRhdGlvbgojIHRoZSByaWdodHMgdG8gdXNlLCBjb3B5LCBtb2RpZnksIG1lcmdlLCBw dWJsaXNoLCBkaXN0cmlidXRlLCBzdWJsaWNlbnNlLAojIGFuZC9vciBzZWxsIGNvcGllcyBvZiB0 aGUgU29mdHdhcmUsIGFuZCB0byBwZXJtaXQgcGVyc29ucyB0byB3aG9tIHRoZQojIFNvZnR3YXJl IGlzIGZ1cm5pc2hlZCB0byBkbyBzbywgc3ViamVjdCB0byB0aGUgZm9sbG93aW5nIGNvbmRpdGlv bnM6CiMgCiMgVGhlIGFib3ZlIGNvcHlyaWdodCBub3RpY2UgYW5kIHRoaXMgcGVybWlzc2lvbiBu b3RpY2Ugc2hhbGwgYmUgaW5jbHVkZWQgaW4KIyBhbGwgY29waWVzIG9yIHN1YnN0YW50aWFsIHBv cnRpb25zIG9mIHRoZSBTb2Z0d2FyZS4KIyAKIyBUSEUgU09GVFdBUkUgSVMgUFJPVklERUQgIkFT IElTIiwgV0lUSE9VVCBXQVJSQU5UWSBPRiBBTlkgS0lORCwgRVhQUkVTUyBPUgojIElNUExJRUQs IElOQ0xVRElORyBCVVQgTk9UIExJTUlURUQgVE8gVEhFIFdBUlJBTlRJRVMgT0YgTUVSQ0hBTlRB QklMSVRZLAojIEZJVE5FU1MgRk9SIEEgUEFSVElDVUxBUiBQVVJQT1NFIEFORCBOT05JTkZSSU5H RU1FTlQuICBJTiBOTyBFVkVOVCBTSEFMTAojIFRIRSBYRlJFRTg2IFBST0pFQ1QgQkUgTElBQkxF IEZPUiBBTlkgQ0xBSU0sIERBTUFHRVMgT1IgT1RIRVIgTElBQklMSVRZLAojIFdIRVRIRVIgSU4g QU4gQUNUSU9OIE9GIENPTlRSQUNULCBUT1JUIE9SIE9USEVSV0lTRSwgQVJJU0lORyBGUk9NLCBP VVQgT0YKIyBPUiBJTiBDT05ORUNUSU9OIFdJVEggVEhFIFNPRlRXQVJFIE9SIFRIRSBVU0UgT1Ig T1RIRVIgREVBTElOR1MgSU4gVEhFCiMgU09GVFdBUkUuCiMgCiMgRXhjZXB0IGFzIGNvbnRhaW5l ZCBpbiB0aGlzIG5vdGljZSwgdGhlIG5hbWUgb2YgWC5Pcmcgc2hhbGwKIyBub3QgYmUgdXNlZCBp biBhZHZlcnRpc2luZyBvciBvdGhlcndpc2UgdG8gcHJvbW90ZSB0aGUgc2FsZSwgdXNlIG9yIG90 aGVyCiMgZGVhbGluZ3MgaW4gdGhpcyBTb2Z0d2FyZSB3aXRob3V0IHByaW9yIHdyaXR0ZW4gYXV0 aG9yaXphdGlvbiBmcm9tIHRoZQojIFguT3JnLgojCgojICoqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioKIyBSZWZlciB0 byB0aGUgWEY4NkNvbmZpZyg0LzUpIG1hbiBwYWdlIGZvciBkZXRhaWxzIGFib3V0IHRoZSBmb3Jt YXQgb2YgCiMgdGhpcyBmaWxlLgojICoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioKCiMgKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKgojIE1v ZHVsZSBzZWN0aW9uIC0tIHRoaXMgIHNlY3Rpb24gIGlzIHVzZWQgdG8gc3BlY2lmeQojIHdoaWNo IGR5bmFtaWNhbGx5IGxvYWRhYmxlIG1vZHVsZXMgdG8gbG9hZC4KIyAqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqCiMK U2VjdGlvbiAiTW9kdWxlIgoKIyBUaGlzIGxvYWRzIHRoZSBEQkUgZXh0ZW5zaW9uIG1vZHVsZS4K CiAgICBMb2FkICAgICAgICAiZGJlIiAgCSMgRG91YmxlIGJ1ZmZlciBleHRlbnNpb24KCiMgVGhp cyBsb2FkcyB0aGUgbWlzY2VsbGFuZW91cyBleHRlbnNpb25zIG1vZHVsZSwgYW5kIGRpc2FibGVz CiMgaW5pdGlhbGlzYXRpb24gb2YgdGhlIFhGcmVlODYtREdBIGV4dGVuc2lvbiB3aXRoaW4gdGhh dCBtb2R1bGUuCiAgICBTdWJTZWN0aW9uICAiZXh0bW9kIgogICAgICBPcHRpb24gICAgIm9taXQg eGZyZWU4Ni1kZ2EiICAgIyBkb24ndCBpbml0aWFsaXNlIHRoZSBER0EgZXh0ZW5zaW9uCiAgICBF bmRTdWJTZWN0aW9uCgojIFRoaXMgbG9hZHMgdGhlIFR5cGUxIGFuZCBGcmVlVHlwZSBmb250IG1v ZHVsZXMKICAgIExvYWQgICAgICAgICJ0eXBlMSIKIyAgICBMb2FkICAgICAgICAic3BlZWRvIgog ICAgTG9hZCAgICAgICAgImZyZWV0eXBlIgojICAgIExvYWQgICAgICAgICJ4dHQiCgojIFRoaXMg bG9hZHMgdGhlIEdMWCBtb2R1bGUKICAgIExvYWQgICAgICAgImdseCIKIyBUaGlzIGxvYWRzIHRo ZSBEUkkgbW9kdWxlCiAgICBMb2FkICAgICAgICJkcmkiCgpFbmRTZWN0aW9uCgpTZWN0aW9uICJF eHRlbnNpb25zIgoJT3B0aW9uICJDb21wb3NpdGUiICJFbmFibGUiCglPcHRpb24gIlJFTkRFUiIg IkVuYWJsZSIKRW5kU2VjdGlvbgoKIyAqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqCiMgRmlsZXMgc2VjdGlvbi4gIFRo aXMgYWxsb3dzIGRlZmF1bHQgZm9udCBhbmQgcmdiIHBhdGhzIHRvIGJlIHNldAojICoqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioKClNlY3Rpb24gIkZpbGVzIgoKIyBUaGUgbG9jYXRpb24gb2YgdGhlIFJHQiBkYXRhYmFz ZS4gIE5vdGUsIHRoaXMgaXMgdGhlIG5hbWUgb2YgdGhlCiMgZmlsZSBtaW51cyB0aGUgZXh0ZW5z aW9uIChsaWtlICIudHh0IiBvciAiLmRiIikuICBUaGVyZSBpcyBub3JtYWxseQojIG5vIG5lZWQg dG8gY2hhbmdlIHRoZSBkZWZhdWx0LgoKICAgIFJnYlBhdGgJIi91c3IvWDExUjYvbGliL1gxMS9y Z2IiCgojIE11bHRpcGxlIEZvbnRQYXRoIGVudHJpZXMgYXJlIGFsbG93ZWQgKHdoaWNoIGFyZSBj b25jYXRlbmF0ZWQgdG9nZXRoZXIpLAojIGFzIHdlbGwgYXMgc3BlY2lmeWluZyBtdWx0aXBsZSBj b21tYS1zZXBhcmF0ZWQgZW50cmllcyBpbiBvbmUgRm9udFBhdGgKIyBjb21tYW5kIChvciBhIGNv bWJpbmF0aW9uIG9mIGJvdGggbWV0aG9kcykKIyAKIyBJZiB5b3UgZG9uJ3QgaGF2ZSBhIGZsb2F0 aW5nIHBvaW50IGNvcHJvY2Vzc29yIGFuZCBlbWFjcywgTW9zYWljIG9yIG90aGVyCiMgcHJvZ3Jh bXMgdGFrZSBsb25nIHRvIHN0YXJ0IHVwLCB0cnkgbW92aW5nIHRoZSBUeXBlMSBhbmQgU3BlZWRv IGRpcmVjdG9yeQojIHRvIHRoZSBlbmQgb2YgdGhpcyBsaXN0IChvciBjb21tZW50IHRoZW0gb3V0 KS4KIyAKCiAgICBGb250UGF0aCAgICIvdXNyL1gxMVI2L2xpYi9YMTEvZm9udHMvbG9jYWwvIgog ICAgRm9udFBhdGggICAiL3Vzci9YMTFSNi9saWIvWDExL2ZvbnRzL21pc2MvIgogICAgRm9udFBh dGggICAiL3Vzci9YMTFSNi9saWIvWDExL2ZvbnRzLzc1ZHBpLzp1bnNjYWxlZCIKICAgIEZvbnRQ YXRoICAgIi91c3IvWDExUjYvbGliL1gxMS9mb250cy8xMDBkcGkvOnVuc2NhbGVkIgogICAgRm9u dFBhdGggICAiL3Vzci9YMTFSNi9saWIvWDExL2ZvbnRzL1NwZWVkby8iCiAgICBGb250UGF0aCAg ICIvdXNyL1gxMVI2L2xpYi9YMTEvZm9udHMvVHlwZTEvIgogICAgRm9udFBhdGggICAiL3Vzci9Y MTFSNi9saWIvWDExL2ZvbnRzL1RydWVUeXBlLyIKIyAgICBGb250UGF0aCAgICIvdXNyL1gxMVI2 L2xpYi9YMTEvZm9udHMvZnJlZWZvbnQvIgogICAgRm9udFBhdGggICAiL3Vzci9YMTFSNi9saWIv WDExL2ZvbnRzLzc1ZHBpLyIKICAgIEZvbnRQYXRoICAgIi91c3IvWDExUjYvbGliL1gxMS9mb250 cy8xMDBkcGkvIgoKIyBUaGUgbW9kdWxlIHNlYXJjaCBwYXRoLiAgVGhlIGRlZmF1bHQgcGF0aCBp cyBzaG93biBoZXJlLgoKIyAgICBNb2R1bGVQYXRoICIvdXNyL1gxMVI2L2xpYi9tb2R1bGVzIgoK RW5kU2VjdGlvbgoKIyAqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqCiMgU2VydmVyIGZsYWdzIHNlY3Rpb24uCiMgKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKgoKU2VjdGlvbiAiU2VydmVyRmxhZ3MiCgojIFVuY29tbWVudCB0aGlzIHRvIGNh dXNlIGEgY29yZSBkdW1wIGF0IHRoZSBzcG90IHdoZXJlIGEgc2lnbmFsIGlzIAojIHJlY2VpdmVk LiAgVGhpcyBtYXkgbGVhdmUgdGhlIGNvbnNvbGUgaW4gYW4gdW51c2FibGUgc3RhdGUsIGJ1dCBt YXkKIyBwcm92aWRlIGEgYmV0dGVyIHN0YWNrIHRyYWNlIGluIHRoZSBjb3JlIGR1bXAgdG8gYWlk IGluIGRlYnVnZ2luZwoKIyAgICBPcHRpb24gIk5vVHJhcFNpZ25hbHMiCgojIFVuY29tbWVudCB0 aGlzIHRvIGRpc2FibGUgdGhlIDxDcnRsPjxBbHQ+PEZuPiBWVCBzd2l0Y2ggc2VxdWVuY2UKIyAo d2hlcmUgbiBpcyAxIHRocm91Z2ggMTIpLiAgVGhpcyBhbGxvd3MgY2xpZW50cyB0byByZWNlaXZl IHRoZXNlIGtleQojIGV2ZW50cy4KCiMgICAgT3B0aW9uICJEb250VlRTd2l0Y2giCgojIFVuY29t bWVudCB0aGlzIHRvIGRpc2FibGUgdGhlIDxDcnRsPjxBbHQ+PEJTPiBzZXJ2ZXIgYWJvcnQgc2Vx dWVuY2UKIyBUaGlzIGFsbG93cyBjbGllbnRzIHRvIHJlY2VpdmUgdGhpcyBrZXkgZXZlbnQuCgoj ICAgIE9wdGlvbiAiRG9udFphcCIKCiMgVW5jb21tZW50IHRoaXMgdG8gZGlzYWJsZSB0aGUgPENy dGw+PEFsdD48S1BfKz4vPEtQXy0+IG1vZGUgc3dpdGNoaW5nCiMgc2VxdWVuY2VzLiAgVGhpcyBh bGxvd3MgY2xpZW50cyB0byByZWNlaXZlIHRoZXNlIGtleSBldmVudHMuCgojICAgIE9wdGlvbiAi RG9udCBab29tIgoKIyBVbmNvbW1lbnQgdGhpcyB0byBkaXNhYmxlIHR1bmluZyB3aXRoIHRoZSB4 dmlkdHVuZSBjbGllbnQuIFdpdGgKIyBpdCB0aGUgY2xpZW50IGNhbiBzdGlsbCBydW4gYW5kIGZl dGNoIGNhcmQgYW5kIG1vbml0b3IgYXR0cmlidXRlcywKIyBidXQgaXQgd2lsbCBub3QgYmUgYWxs b3dlZCB0byBjaGFuZ2UgdGhlbS4gSWYgaXQgdHJpZXMgaXQgd2lsbAojIHJlY2VpdmUgYSBwcm90 b2NvbCBlcnJvci4KCiMgICAgT3B0aW9uICJEaXNhYmxlVmlkTW9kZUV4dGVuc2lvbiIKCiMgVW5j b21tZW50IHRoaXMgdG8gZW5hYmxlIHRoZSB1c2Ugb2YgYSBub24tbG9jYWwgeHZpZHR1bmUgY2xp ZW50LiAKCiMgICAgT3B0aW9uICJBbGxvd05vbkxvY2FsWHZpZHR1bmUiCgojIFVuY29tbWVudCB0 aGlzIHRvIGRpc2FibGUgZHluYW1pY2FsbHkgbW9kaWZ5aW5nIHRoZSBpbnB1dCBkZXZpY2UKIyAo bW91c2UgYW5kIGtleWJvYXJkKSBzZXR0aW5ncy4gCgojICAgIE9wdGlvbiAiRGlzYWJsZU1vZElu RGV2IgoKIyBVbmNvbW1lbnQgdGhpcyB0byBlbmFibGUgdGhlIHVzZSBvZiBhIG5vbi1sb2NhbCBj bGllbnQgdG8KIyBjaGFuZ2UgdGhlIGtleWJvYXJkIG9yIG1vdXNlIHNldHRpbmdzIChjdXJyZW50 bHkgb25seSB4c2V0KS4KCiMgICAgT3B0aW9uICJBbGxvd05vbkxvY2FsTW9kSW5EZXYiCgpFbmRT ZWN0aW9uCgojICoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioKIyBJbnB1dCBkZXZpY2VzCiMgKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKgoK IyAqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqCiMgQ29yZSBrZXlib2FyZCdzIElucHV0RGV2aWNlIHNlY3Rpb24KIyAq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqCgpTZWN0aW9uICJJbnB1dERldmljZSIKCiAgICBJZGVudGlmaWVyCSJLZXli b2FyZDEiCiAgICBEcml2ZXIJImtleWJvYXJkIgoKIyBGb3IgbW9zdCBPU3MgdGhlIHByb3RvY29s IGNhbiBiZSBvbWl0dGVkIChpdCBkZWZhdWx0cyB0byAiU3RhbmRhcmQiKS4KIyBXaGVuIHVzaW5n IFhRVUVVRSAob25seSBmb3IgU1ZSMyBhbmQgU1ZSNCwgYnV0IG5vdCBTb2xhcmlzKSwKIyB1bmNv bW1lbnQgdGhlIGZvbGxvd2luZyBsaW5lLgoKIyAgICBPcHRpb24gICAgICJQcm90b2NvbCIgICAg ICAiWHF1ZXVlIgoKICAgIE9wdGlvbiAiQXV0b1JlcGVhdCIgIjUwMCAzMCIKCiMgU3BlY2lmeSB3 aGljaCBrZXlib2FyZCBMRURzIGNhbiBiZSB1c2VyLWNvbnRyb2xsZWQgKGVnLCB3aXRoIHhzZXQo MSkpCiMgICAgT3B0aW9uCSJYbGVkcyIgICAgICAiMSAyIDMiCgojICAgIE9wdGlvbiAiTGVmdEFs dCIgICAgICJNZXRhIgojICAgIE9wdGlvbiAiUmlnaHRBbHQiICAgICJNb2RlU2hpZnQiCgojIFRv IGN1c3RvbWlzZSB0aGUgWEtCIHNldHRpbmdzIHRvIHN1aXQgeW91ciBrZXlib2FyZCwgbW9kaWZ5 IHRoZQojIGxpbmVzIGJlbG93ICh3aGljaCBhcmUgdGhlIGRlZmF1bHRzKS4gIEZvciBleGFtcGxl LCBmb3IgYSBub24tVS5TLgojIGtleWJvYXJkLCB5b3Ugd2lsbCBwcm9iYWJseSB3YW50IHRvIHVz ZToKIyAgICBPcHRpb24gIlhrYk1vZGVsIiAgICAicGMxMDIiCiMgSWYgeW91IGhhdmUgYSBVUyBN aWNyb3NvZnQgTmF0dXJhbCBrZXlib2FyZCwgeW91IGNhbiB1c2U6CiMgICAgT3B0aW9uICJYa2JN b2RlbCIgICAgIm1pY3Jvc29mdCIKIwojIFRoZW4gdG8gY2hhbmdlIHRoZSBsYW5ndWFnZSwgY2hh bmdlIHRoZSBMYXlvdXQgc2V0dGluZy4KIyBGb3IgZXhhbXBsZSwgYSBnZXJtYW4gbGF5b3V0IGNh biBiZSBvYnRhaW5lZCB3aXRoOgojICAgIE9wdGlvbiAiWGtiTGF5b3V0IiAgICJkZSIKIyBvcjoK IyAgICBPcHRpb24gIlhrYkxheW91dCIgICAiZGUiCiMgICAgT3B0aW9uICJYa2JWYXJpYW50IiAg Im5vZGVhZGtleXMiCiMKIyBJZiB5b3UnZCBsaWtlIHRvIHN3aXRjaCB0aGUgcG9zaXRpb25zIG9m IHlvdXIgY2Fwc2xvY2sgYW5kCiMgY29udHJvbCBrZXlzLCB1c2U6CiMgICAgT3B0aW9uICJYa2JP cHRpb25zIiAgImN0cmw6c3dhcGNhcHMiCgojIFRoZXNlIGFyZSB0aGUgZGVmYXVsdCBYS0Igc2V0 dGluZ3MgZm9yIFguT3JnCiMgICAgT3B0aW9uICJYa2JSdWxlcyIgICAgIl9fWEtCREVGUlVMRVNf XyIKIyAgICBPcHRpb24gIlhrYk1vZGVsIiAgICAicGMxMDEiCiMgICAgT3B0aW9uICJYa2JMYXlv dXQiICAgInVzIgojICAgIE9wdGlvbiAiWGtiVmFyaWFudCIgICIiCiMgICAgT3B0aW9uICJYa2JP cHRpb25zIiAgIiIKCiMgICAgT3B0aW9uICJYa2JEaXNhYmxlIgoKICAgIE9wdGlvbiAiWGtiUnVs ZXMiCSJ4b3JnIgogICAgT3B0aW9uICJYa2JNb2RlbCIJInBjMTAxIgogICAgT3B0aW9uICJYa2JM YXlvdXQiCSJ1cyIKCkVuZFNlY3Rpb24KCgojICoqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioKIyBDb3JlIFBvaW50ZXIn cyBJbnB1dERldmljZSBzZWN0aW9uCiMgKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKgoKU2VjdGlvbiAiSW5wdXREZXZp Y2UiCgojIElkZW50aWZpZXIgYW5kIGRyaXZlcgoKICAgIElkZW50aWZpZXIJIk1vdXNlMSIKICAg IERyaXZlcgkibW91c2UiCiAgICBPcHRpb24gIlByb3RvY29sIiAgICAiYXV0byIKICAgIE9wdGlv biAiRGV2aWNlIiAgICAgICIvZGV2L3BzbTAiCgojIE1vdXNlLXNwZWVkIHNldHRpbmcgZm9yIFBT LzIgbW91c2UuCgojICAgIE9wdGlvbiAiUmVzb2x1dGlvbiIJIjI1NiIKCiMgV2hlbiB1c2luZyBY UVVFVUUsIGNvbW1lbnQgb3V0IHRoZSBhYm92ZSB0d28gbGluZXMsIGFuZCB1bmNvbW1lbnQKIyB0 aGUgZm9sbG93aW5nIGxpbmUuCgojICAgIE9wdGlvbiAiUHJvdG9jb2wiCSJYcXVldWUiCgojIEJh dWRyYXRlIGFuZCBTYW1wbGVSYXRlIGFyZSBvbmx5IGZvciBzb21lIExvZ2l0ZWNoIG1pY2UuIElu CiMgYWxtb3N0IGV2ZXJ5IGNhc2UgdGhlc2UgbGluZXMgc2hvdWxkIGJlIG9taXR0ZWQuCgojICAg IE9wdGlvbiAiQmF1ZFJhdGUiCSI5NjAwIgojICAgIE9wdGlvbiAiU2FtcGxlUmF0ZSIJIjE1MCIK CiMgRW11bGF0ZTNCdXR0b25zIGlzIGFuIG9wdGlvbiBmb3IgMi1idXR0b24gTWljcm9zb2Z0IG1p Y2UKIyBFbXVsYXRlM1RpbWVvdXQgaXMgdGhlIHRpbWVvdXQgaW4gbWlsbGlzZWNvbmRzIChkZWZh dWx0IGlzIDUwbXMpCgogICAgT3B0aW9uICJFbXVsYXRlM0J1dHRvbnMiICJubyIKCSBPcHRpb24g IlpBeGlzTWFwcGluZyIgIjQgNSA2IDciCgkgT3B0aW9uICJCdXR0b25zIiAiNyIKIyAgICBPcHRp b24gIkVtdWxhdGUzVGltZW91dCIgICAgIjUwIgoKIyBDaG9yZE1pZGRsZSBpcyBhbiBvcHRpb24g Zm9yIHNvbWUgMy1idXR0b24gTG9naXRlY2ggbWljZQoKIyAgICBPcHRpb24gIkNob3JkTWlkZGxl IgoKRW5kU2VjdGlvbgoKCiMgKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKgojIE90aGVyIGlucHV0IGRldmljZSBzZWN0 aW9ucyAKIyB0aGlzIGlzIG9wdGlvbmFsIGFuZCBpcyByZXF1aXJlZCBvbmx5IGlmIHlvdQojIGFy ZSB1c2luZyBleHRlbmRlZCBpbnB1dCBkZXZpY2VzLiAgVGhpcyBpcyBmb3IgZXhhbXBsZSBvbmx5 LiAgUmVmZXIKIyB0byB0aGUgWEY4NkNvbmZpZyBtYW4gcGFnZSBmb3IgYSBkZXNjcmlwdGlvbiBv ZiB0aGUgb3B0aW9ucy4KIyAqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqCiMKIyBTZWN0aW9uICJJbnB1dERldmljZSIg CiMgICAgSWRlbnRpZmllciAgIk1vdXNlMiIKIyAgICBEcml2ZXIgICAgICAibW91c2UiCiMgICAg T3B0aW9uICAgICAgIlByb3RvY29sIiAgICAgICJNb3VzZU1hbiIKIyAgICBPcHRpb24gICAgICAi RGV2aWNlIiAgICAgICAgIi9kZXYvbW91c2UyIgojIEVuZFNlY3Rpb24KIwojIFNlY3Rpb24gIklu cHV0RGV2aWNlIgojICAgIElkZW50aWZpZXIgInNwYWNlYmFsbCIKIyAgICBEcml2ZXIgICAgICJt YWdlbGxhbiIKIyAgICBPcHRpb24gICAgICJEZXZpY2UiICAgICAgICAiL2Rldi9jdWEwIgojIEVu ZFNlY3Rpb24KIwojIFNlY3Rpb24gIklucHV0RGV2aWNlIgojICAgIElkZW50aWZpZXIgInNwYWNl YmFsbDIiCiMgICAgRHJpdmVyICAgICAic3BhY2VvcmIiCiMgICAgT3B0aW9uICAgICAiRGV2aWNl IiAgICAgICAgIi9kZXYvY3VhMCIKIyBFbmRTZWN0aW9uCiMKIyBTZWN0aW9uICJJbnB1dERldmlj ZSIKIyAgICBJZGVudGlmaWVyICJ0b3VjaHNjcmVlbjAiCiMgICAgRHJpdmVyICAgICAibWljcm90 b3VjaCIKIyAgICBPcHRpb24gICAgICJEZXZpY2UiICAgICAgICAiL2Rldi90dHlTMCIKIyAgICBP cHRpb24gICAgICJNaW5YIiAgICAgICAgICAiMTQxMiIKIyAgICBPcHRpb24gICAgICJNYXhYIiAg ICAgICAgICAiMTUxODQiCiMgICAgT3B0aW9uICAgICAiTWluWSIgICAgICAgICAgIjE1MzcyIgoj ICAgIE9wdGlvbiAgICAgIk1heFkiICAgICAgICAgICIxMjMwIgojICAgIE9wdGlvbiAgICAgIlNj cmVlbk51bWJlciIgICIwIgojICAgIE9wdGlvbiAgICAgIlJlcG9ydGluZ01vZGUiICJTY2FsZWQi CiMgICAgT3B0aW9uICAgICAiQnV0dG9uTnVtYmVyIiAgIjEiCiMgICAgT3B0aW9uICAgICAiU2Vu ZENvcmVFdmVudHMiCiMgRW5kU2VjdGlvbgojCiMgU2VjdGlvbiAiSW5wdXREZXZpY2UiCiMgICAg SWRlbnRpZmllciAidG91Y2hzY3JlZW4xIgojICAgIERyaXZlciAgICAgImVsbzIzMDAiCiMgICAg T3B0aW9uICAgICAiRGV2aWNlIiAgICAgICAgIi9kZXYvdHR5UzAiCiMgICAgT3B0aW9uICAgICAi TWluWCIgICAgICAgICAgIjIzMSIKIyAgICBPcHRpb24gICAgICJNYXhYIiAgICAgICAgICAiMzg2 OCIKIyAgICBPcHRpb24gICAgICJNaW5ZIiAgICAgICAgICAiMzg1OCIKIyAgICBPcHRpb24gICAg ICJNYXhZIiAgICAgICAgICAiMjcyIgojICAgIE9wdGlvbiAgICAgIlNjcmVlbk51bWJlciIgICIw IgojICAgIE9wdGlvbiAgICAgIlJlcG9ydGluZ01vZGUiICJTY2FsZWQiCiMgICAgT3B0aW9uICAg ICAiQnV0dG9uVGhyZXNob2xkIiAgICAgICAiMTciCiMgICAgT3B0aW9uICAgICAiQnV0dG9uTnVt YmVyIiAgIjEiCiMgICAgT3B0aW9uICAgICAiU2VuZENvcmVFdmVudHMiCiMgRW5kU2VjdGlvbgoK IyAqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqCiMgTW9uaXRvciBzZWN0aW9uCiMgKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKgoKIyBBbnkg bnVtYmVyIG9mIG1vbml0b3Igc2VjdGlvbnMgbWF5IGJlIHByZXNlbnQKClNlY3Rpb24gIk1vbml0 b3IiCgogICAgSWRlbnRpZmllciAgImxjZCIKCiMgSG9yaXpTeW5jIGlzIGluIGtIeiB1bmxlc3Mg dW5pdHMgYXJlIHNwZWNpZmllZC4KIyBIb3JpelN5bmMgbWF5IGJlIGEgY29tbWEgc2VwYXJhdGVk IGxpc3Qgb2YgZGlzY3JldGUgdmFsdWVzLCBvciBhCiMgY29tbWEgc2VwYXJhdGVkIGxpc3Qgb2Yg cmFuZ2VzIG9mIHZhbHVlcy4KIyBOT1RFOiBUSEUgVkFMVUVTIEhFUkUgQVJFIEVYQU1QTEVTIE9O TFkuICBSRUZFUiBUTyBZT1VSIE1PTklUT1InUwojIFVTRVIgTUFOVUFMIEZPUiBUSEUgQ09SUkVD VCBOVU1CRVJTLgoKICAgIEhvcml6U3luYyAgIDMxLjUgLSA0OC41CgojICAgIEhvcml6U3luYwkz MC02NCAgICAgICAgICMgbXVsdGlzeW5jCiMgICAgSG9yaXpTeW5jCTMxLjUsIDM1LjIgICAgIyBt dWx0aXBsZSBmaXhlZCBzeW5jIGZyZXF1ZW5jaWVzCiMgICAgSG9yaXpTeW5jCTE1LTI1LCAzMC01 MCAgIyBtdWx0aXBsZSByYW5nZXMgb2Ygc3luYyBmcmVxdWVuY2llcwoKIyBWZXJ0UmVmcmVzaCBp cyBpbiBIeiB1bmxlc3MgdW5pdHMgYXJlIHNwZWNpZmllZC4KIyBWZXJ0UmVmcmVzaCBtYXkgYmUg YSBjb21tYSBzZXBhcmF0ZWQgbGlzdCBvZiBkaXNjcmV0ZSB2YWx1ZXMsIG9yIGEKIyBjb21tYSBz ZXBhcmF0ZWQgbGlzdCBvZiByYW5nZXMgb2YgdmFsdWVzLgojIE5PVEU6IFRIRSBWQUxVRVMgSEVS RSBBUkUgRVhBTVBMRVMgT05MWS4gIFJFRkVSIFRPIFlPVVIgTU9OSVRPUidTCiMgVVNFUiBNQU5V QUwgRk9SIFRIRSBDT1JSRUNUIE5VTUJFUlMuCgogICAgVmVydFJlZnJlc2ggNTAtMTAwCgpFbmRT ZWN0aW9uCgoKIyAqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqCiMgR3JhcGhpY3MgZGV2aWNlIHNlY3Rpb24KIyAqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqCgojIEFueSBudW1iZXIgb2YgZ3JhcGhpY3MgZGV2aWNlIHNlY3Rpb25zIG1heSBi ZSBwcmVzZW50CgojIFN0YW5kYXJkIFZHQSBEZXZpY2U6CgpTZWN0aW9uICJEZXZpY2UiCiAgICBJ ZGVudGlmaWVyCSJTdGFuZGFyZCBWR0EiCiAgICBWZW5kb3JOYW1lCSJVbmtub3duIgogICAgQm9h cmROYW1lCSJVbmtub3duIgoKIyBUaGUgY2hpcHNldCBsaW5lIGlzIG9wdGlvbmFsIGluIG1vc3Qg Y2FzZXMuICBJdCBjYW4gYmUgdXNlZCB0byBvdmVycmlkZQojIHRoZSBkcml2ZXIncyBjaGlwc2V0 IGRldGVjdGlvbiwgYW5kIHNob3VsZCBub3Qgbm9ybWFsbHkgYmUgc3BlY2lmaWVkLgoKIyAgICBD aGlwc2V0CSJnZW5lcmljIgoKIyBUaGUgRHJpdmVyIGxpbmUgbXVzdCBiZSBwcmVzZW50LiAgV2hl biB1c2luZyBydW4tdGltZSBsb2FkYWJsZSBkcml2ZXIKIyBtb2R1bGVzLCB0aGlzIGxpbmUgaW5z dHJ1Y3RzIHRoZSBzZXJ2ZXIgdG8gbG9hZCB0aGUgc3BlY2lmaWVkIGRyaXZlcgojIG1vZHVsZS4g IEV2ZW4gd2hlbiBub3QgdXNpbmcgbG9hZGFibGUgZHJpdmVyIG1vZHVsZXMsIHRoaXMgbGluZQoj IGluZGljYXRlcyB3aGljaCBkcml2ZXIgc2hvdWxkIGludGVycHJldCB0aGUgaW5mb3JtYXRpb24g aW4gdGhpcyBzZWN0aW9uLgoKICAgIERyaXZlciAgICAgInZnYSIKIyBUaGUgQnVzSUQgbGluZSBp cyB1c2VkIHRvIHNwZWNpZnkgd2hpY2ggb2YgcG9zc2libHkgbXVsdGlwbGUgZGV2aWNlcwojIHRo aXMgc2VjdGlvbiBpcyBpbnRlbmRlZCBmb3IuICBXaGVuIHRoaXMgbGluZSBpc24ndCBwcmVzZW50 LCBhIGRldmljZQojIHNlY3Rpb24gY2FuIG9ubHkgbWF0Y2ggdXAgd2l0aCB0aGUgcHJpbWFyeSB2 aWRlbyBkZXZpY2UuICBGb3IgUENJCiMgZGV2aWNlcyBhIGxpbmUgbGlrZSB0aGUgZm9sbG93aW5n IGNvdWxkIGJlIHVzZWQuICBUaGlzIGxpbmUgc2hvdWxkIG5vdAojIG5vcm1hbGx5IGJlIGluY2x1 ZGVkIHVubGVzcyB0aGVyZSBpcyBtb3JlIHRoYW4gb25lIHZpZGVvIGRldmljZQojIGludGFsbGVk LgoKIyAgICBCdXNJRCAgICAgICJQQ0k6MDoxMDowIgoKIyAgICBWaWRlb1JhbQkyNTYKCiMgICAg Q2xvY2tzCTI1LjIgMjguMwoKRW5kU2VjdGlvbgoKIyBEZXZpY2UgY29uZmlndXJlZCBieSB4Zjg2 Y29uZmlnOgoKU2VjdGlvbiAiRGV2aWNlIgogICAgSWRlbnRpZmllciAgInJhZGVvbiIKIyAgICBE cml2ZXIgInZtd2FyZSIgCiAgICBEcml2ZXIgICAgICAicmFkZW9uIgogICAgI1ZpZGVvUmFtICAg IDY1NTM2CiAgICAjIEluc2VydCBDbG9ja3MgbGluZXMgaGVyZSBpZiBhcHByb3ByaWF0ZQpFbmRT ZWN0aW9uCgoKIyAqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqCiMgU2NyZWVuIHNlY3Rpb25zCiMgKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KgoKIyBBbnkgbnVtYmVyIG9mIHNjcmVlbiBzZWN0aW9ucyBtYXkgYmUgcHJlc2VudC4gIEVhY2gg ZGVzY3JpYmVzCiMgdGhlIGNvbmZpZ3VyYXRpb24gb2YgYSBzaW5nbGUgc2NyZWVuLiAgQSBzaW5n bGUgc3BlY2lmaWMgc2NyZWVuIHNlY3Rpb24KIyBtYXkgYmUgc3BlY2lmaWVkIGZyb20gdGhlIFgg c2VydmVyIGNvbW1hbmQgbGluZSB3aXRoIHRoZSAiLXNjcmVlbiIKIyBvcHRpb24uClNlY3Rpb24g IlNjcmVlbiIKICAgIElkZW50aWZpZXIgICJTY3JlZW4gMSIKICAgIERldmljZSAgICAgICJyYWRl b24iCiAgICBNb25pdG9yICAgICAibGNkIgogICAgRGVmYXVsdERlcHRoIDI0CgogICAgU3Vic2Vj dGlvbiAiRGlzcGxheSIKICAgICAgICBEZXB0aCAgICAgICA4CiAgICAgICAgTW9kZXMgICAgICAg IjEyODB4MTAyNCIgIjEwMjR4NzY4IiAiODAweDYwMCIgIjY0MHg0ODAiCiAgICAgICAgVmlld1Bv cnQgICAgMCAwCiAgICBFbmRTdWJzZWN0aW9uCiAgICBTdWJzZWN0aW9uICJEaXNwbGF5IgogICAg ICAgIERlcHRoICAgICAgIDE2CiAgICAgICAgTW9kZXMgICAgICAgIjEyODB4MTAyNCIgIjEwMjR4 NzY4IiAiODAweDYwMCIgIjY0MHg0ODAiCiAgICAgICAgVmlld1BvcnQgICAgMCAwCiAgICBFbmRT dWJzZWN0aW9uCiAgICBTdWJzZWN0aW9uICJEaXNwbGF5IgogICAgICAgIERlcHRoICAgICAgIDI0 CiAgICAgICAgTW9kZXMgICAgICAgIjEyODB4MTAyNCIgIjEwMjR4NzY4IiAiODAweDYwMCIgIjY0 MHg0ODAiCiAgICAgICAgVmlld1BvcnQgICAgMCAwCiAgICBFbmRTdWJzZWN0aW9uCkVuZFNlY3Rp b24KCiMgKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKgojIFNlcnZlckxheW91dCBzZWN0aW9ucy4KIyAqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqCgojIEFueSBudW1iZXIgb2YgU2VydmVyTGF5b3V0IHNlY3Rpb25zIG1heSBiZSBwcmVzZW50 LiAgRWFjaCBkZXNjcmliZXMKIyB0aGUgd2F5IG11bHRpcGxlIHNjcmVlbnMgYXJlIG9yZ2FuaXNl ZC4gIEEgc3BlY2lmaWMgU2VydmVyTGF5b3V0CiMgc2VjdGlvbiBtYXkgYmUgc3BlY2lmaWVkIGZy b20gdGhlIFggc2VydmVyIGNvbW1hbmQgbGluZSB3aXRoIHRoZQojICItbGF5b3V0IiBvcHRpb24u ICBJbiB0aGUgYWJzZW5jZSBvZiB0aGlzLCB0aGUgZmlyc3Qgc2VjdGlvbiBpcyB1c2VkLgojIFdo ZW4gbm93IFNlcnZlckxheW91dCBzZWN0aW9uIGlzIHByZXNlbnQsIHRoZSBmaXJzdCBTY3JlZW4g c2VjdGlvbgojIGlzIHVzZWQgYWxvbmUuCgpTZWN0aW9uICJTZXJ2ZXJMYXlvdXQiCgojIFRoZSBJ ZGVudGlmaWVyIGxpbmUgbXVzdCBiZSBwcmVzZW50CiAgICBJZGVudGlmaWVyICAiU2ltcGxlIExh eW91dCIKCiMgRWFjaCBTY3JlZW4gbGluZSBzcGVjaWZpZXMgYSBTY3JlZW4gc2VjdGlvbiBuYW1l LCBhbmQgb3B0aW9uYWxseQojIHRoZSByZWxhdGl2ZSBwb3NpdGlvbiBvZiBvdGhlciBzY3JlZW5z LiAgVGhlIGZvdXIgbmFtZXMgYWZ0ZXIKIyBwcmltYXJ5IHNjcmVlbiBuYW1lIGFyZSB0aGUgc2Ny ZWVucyB0byB0aGUgdG9wLCBib3R0b20sIGxlZnQgYW5kIHJpZ2h0CiMgb2YgdGhlIHByaW1hcnkg c2NyZWVuLiAgSW4gdGhpcyBleGFtcGxlLCBzY3JlZW4gMiBpcyBsb2NhdGVkIHRvIHRoZQojIHJp Z2h0IG9mIHNjcmVlbiAxLgoKICAgIFNjcmVlbiAiU2NyZWVuIDEiCgojIEVhY2ggSW5wdXREZXZp Y2UgbGluZSBzcGVjaWZpZXMgYW4gSW5wdXREZXZpY2Ugc2VjdGlvbiBuYW1lIGFuZAojIG9wdGlv bmFsbHkgc29tZSBvcHRpb25zIHRvIHNwZWNpZnkgdGhlIHdheSB0aGUgZGV2aWNlIGlzIHRvIGJl CiMgdXNlZC4gIFRob3NlIG9wdGlvbnMgaW5jbHVkZSAiQ29yZVBvaW50ZXIiLCAiQ29yZUtleWJv YXJkIiBhbmQKIyAiU2VuZENvcmVFdmVudHMiLgoKICAgIElucHV0RGV2aWNlICJNb3VzZTEiICJD b3JlUG9pbnRlciIKICAgIElucHV0RGV2aWNlICJLZXlib2FyZDEiICJDb3JlS2V5Ym9hcmQiCgpF bmRTZWN0aW9uCgojU2VjdGlvbiAiRFJJIgojICAgTW9kZSAwNjY2CiNFbmRTZWN0aW9uCgo= ------=_Part_710_33516875.1106112740992-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 19 08:12:01 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1627E16A4CE for ; Wed, 19 Jan 2005 08:12:01 +0000 (GMT) Received: from mx04.mdcs.at (mx04.mdcs.at [193.110.28.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DFF643D1F for ; Wed, 19 Jan 2005 08:12:00 +0000 (GMT) (envelope-from nikolay.nenchev@rbb-sofia.raiffeisen.at) To: freebsd-current@freebsd.org MIME-Version: 1.0 Message-ID: From: nikolay.nenchev@rbb-sofia.raiffeisen.at Date: Wed, 19 Jan 2005 10:07:36 +0200 X-Priority: 3 (Normal) Content-Type: text/plain; charset="US-ASCII" X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Bind 9.3 rndc? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 08:12:01 -0000 Hi, have installed FreeBSD 5.3 with Bind integrated in it. named is running in chroot, with user bind, so every file in /etc/namedb is owned by bind:wheel, exept rndc.key. (i have also rndc.conf with owner bind) and it is impossible to start make rndc reload. if i change owner on rndc.key it is working but is it a security issue, user who is running named (bind) to have acceess to rndc.key. A another thing, if i make " sudo named stop/start" the own of my master folder is change to root:wheel (before bind:wheel)? Any comment is appreciated. Nikolay Nenchev From owner-freebsd-current@FreeBSD.ORG Wed Jan 19 08:25:43 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0E1916A4CE for ; Wed, 19 Jan 2005 08:25:43 +0000 (GMT) Received: from picard.newmillennium.net.au (220-245-208-145-act.tpgi.com.au [220.245.208.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7581F43D5D for ; Wed, 19 Jan 2005 08:25:42 +0000 (GMT) (envelope-from alastair@newmillennium.net.au) Received: from riker (riker.nmn.cafn [10.0.1.2])j0J8PetO054332 for ; Wed, 19 Jan 2005 19:25:40 +1100 (EST) (envelope-from alastair@newmillennium.net.au) From: Sender: "Alastair D'Silva" To: Date: Wed, 19 Jan 2005 19:25:40 +1100 Organization: New Millennium Networking Message-ID: <004501c4fe00$76180fc0$0201000a@riker> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal Subject: IPFW problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 08:25:43 -0000 I have recently (the last week or so, but possible longer as I had updated the system prior to going on a 3 week holiday) been having some problems with IPFW under -CURRENT. I am running: bash-2.05b$ uname -a FreeBSD picard.newmillennium.net.au 6.0-CURRENT FreeBSD 6.0-CURRENT #38: Sun Jan 16 18:27:30 EST 2005 root@picard.newmillennium.net.au:/usr/obj/usr/src/sys/PICARD i386 What happens is that I occasionally (every 5 minutes or so) get the following: Jan 19 16:54:41 picard kernel: ipfw: ouch!, skip past end of rules, denying packet And then a (random) TCP connection is dropped. What is interesting is that every possible path through the firewall matches a rule. I can provide a copy of the firewall rules on request. My firewall uses the following features, in addition to the standard allow/deny rules: Dummynet Stateful rules (check-state, keep-state) Skipto's Forwarding (fwd) Some more stuff from the system, in case it helps: bash-2.05b$ sysctl -a | grep ip\.fw net.inet.ip.fw.enable: 1 net.inet.ip.fw.autoinc_step: 100 net.inet.ip.fw.one_pass: 0 net.inet.ip.fw.debug: 1 net.inet.ip.fw.verbose: 1 net.inet.ip.fw.verbose_limit: 0 net.inet.ip.fw.dyn_buckets: 256 net.inet.ip.fw.curr_dyn_buckets: 256 net.inet.ip.fw.dyn_count: 343 net.inet.ip.fw.dyn_max: 4096 net.inet.ip.fw.static_count: 184 net.inet.ip.fw.dyn_ack_lifetime: 1800 net.inet.ip.fw.dyn_syn_lifetime: 20 net.inet.ip.fw.dyn_fin_lifetime: 1 net.inet.ip.fw.dyn_rst_lifetime: 1 net.inet.ip.fw.dyn_udp_lifetime: 10 net.inet.ip.fw.dyn_short_lifetime: 5 net.inet.ip.fw.dyn_keepalive: 1 My kernel options regarding the firewall are: options IPFIREWALL options IPDIVERT options IPFIREWALL_FORWARD options DUMMYNET options HZ=1000 -- Alastair D'Silva mob: 0413 485 733 Networking Consultant fax: 0413 181 661 New Millennium Networking web: http://www.newmillennium.net.au From owner-freebsd-current@FreeBSD.ORG Wed Jan 19 09:19:37 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CCFD16A4CE for ; Wed, 19 Jan 2005 09:19:37 +0000 (GMT) Received: from mail.ntmk.ru (mail.ntmk.ru [217.114.241.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 906BD43D41 for ; Wed, 19 Jan 2005 09:19:35 +0000 (GMT) (envelope-from boris@ntmk.ru) Received: from boris.nikom.ru ([10.1.16.195]) by mail.ntmk.ru with esmtp (Exim 4.34) id 1CrBzx-0007iJ-BJ for freebsd-current@freebsd.org; Wed, 19 Jan 2005 14:19:33 +0500 Message-ID: <41EE2625.4090609@ntmk.ru> Date: Wed, 19 Jan 2005 14:19:33 +0500 From: Boris Kovalenko User-Agent: Mozilla Thunderbird 1.0 (X11/20041228) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: multipart/mixed; boundary="------------060408090903080102040103" Subject: [PATCH] 802.1p priority X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 09:19:37 -0000 This is a multi-part message in MIME format. --------------060408090903080102040103 Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Hello! I want to implement 802.1p priority tagging for VLAN. I made this dirty patch and wonder - it works for me. May somebody look at it and tell me is this enough for BSD community or should I look and patch something more? -- With respect, Boris --------------060408090903080102040103 Content-Type: text/plain; name="patch-8021p.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="patch-8021p.diff" --- sbin/ifconfig/ifconfig.h.orig Wed Jan 19 10:44:20 2005 +++ sbin/ifconfig/ifconfig.h Wed Jan 19 10:09:57 2005 @@ -49,6 +49,7 @@ extern void setvlantag(const char *, int, int, const struct afswtch *rafp); extern void setvlandev(const char *, int, int, const struct afswtch *rafp); +extern void setvlanpri(const char *, int, int, const struct afswtch *rafp); extern void unsetvlandev(const char *, int, int, const struct afswtch *rafp); extern void vlan_status(int s, struct rt_addrinfo *); --- sbin/ifconfig/ifvlan.c.orig Thu Apr 18 23:14:09 2002 +++ sbin/ifconfig/ifvlan.c Wed Jan 19 10:46:52 2005 @@ -59,6 +59,7 @@ "$FreeBSD: src/sbin/ifconfig/ifvlan.c,v 1.5 2002/04/18 17:14:09 imp Exp $"; #endif static int __tag = 0; +static int __pri = 0; static int __have_tag = 0; void @@ -72,9 +73,9 @@ if (ioctl(s, SIOCGETVLAN, (caddr_t)&ifr) == -1) return; - printf("\tvlan: %d parent interface: %s\n", - vreq.vlr_tag, vreq.vlr_parent[0] == '\0' ? - "" : vreq.vlr_parent); + printf("\tvlan: %d parent interface: %s 802.1p: %d\n", + EVL_VLANOFTAG(vreq.vlr_tag), vreq.vlr_parent[0] == '\0' ? + "" : vreq.vlr_parent, EVL_PRIOFTAG(vreq.vlr_tag)); return; } @@ -94,7 +95,29 @@ if (ioctl(s, SIOCGETVLAN, (caddr_t)&ifr) == -1) err(1, "SIOCGETVLAN"); - vreq.vlr_tag = tag; + vreq.vlr_tag = EVL_MAKETAG(tag, __pri); + + if (ioctl(s, SIOCSETVLAN, (caddr_t)&ifr) == -1) + err(1, "SIOCSETVLAN"); + + return; +} + +void +setvlanpri(const char *val, int d, int s, const struct afswtch *afp) +{ + u_int16_t pri; + struct vlanreq vreq; + + __pri = pri = atoi(val); + + bzero((char *)&vreq, sizeof(struct vlanreq)); + ifr.ifr_data = (caddr_t)&vreq; + + if (ioctl(s, SIOCGETVLAN, (caddr_t)&ifr) == -1) + err(1, "SIOCGETVLAN"); + + vreq.vlr_tag = EVL_MAKETAG(EVL_VLANOFTAG(vreq.vlr_tag), pri); if (ioctl(s, SIOCSETVLAN, (caddr_t)&ifr) == -1) err(1, "SIOCSETVLAN"); @@ -117,7 +140,7 @@ err(1, "SIOCGETVLAN"); strncpy(vreq.vlr_parent, val, sizeof(vreq.vlr_parent)); - vreq.vlr_tag = __tag; + vreq.vlr_tag = EVL_MAKETAG(__tag, __pri); if (ioctl(s, SIOCSETVLAN, (caddr_t)&ifr) == -1) err(1, "SIOCSETVLAN"); --- sys/net/if_vlan_var.h.orig Mon Jan 19 00:29:04 2004 +++ sys/net/if_vlan_var.h Wed Jan 19 10:42:04 2005 @@ -43,6 +43,7 @@ #define EVL_VLID_MASK 0x0FFF #define EVL_VLANOFTAG(tag) ((tag) & EVL_VLID_MASK) #define EVL_PRIOFTAG(tag) (((tag) >> 13) & 7) +#define EVL_MAKETAG(tag,pri) ((((pri) & 7) << 13) | ((tag) & EVL_VLID_MASK)) /* sysctl(3) tags, for compatibility purposes */ #define VLANCTL_PROTO 1 @@ -52,8 +53,8 @@ * Configuration structure for SIOCSETVLAN and SIOCGETVLAN ioctls. */ struct vlanreq { - char vlr_parent[IFNAMSIZ]; - u_short vlr_tag; + char vlr_parent[IFNAMSIZ]; + u_int16_t vlr_tag; }; #define SIOCSETVLAN SIOCSIFGENERIC #define SIOCGETVLAN SIOCGIFGENERIC --- sys/net/if_vlan.c.orig Wed Jan 19 10:40:32 2005 +++ sys/net/if_vlan.c Wed Jan 19 10:42:22 2005 @@ -930,15 +930,6 @@ error = ENOENT; break; } - /* - * Don't let the caller set up a VLAN tag with - * anything except VLID bits. - */ - - if (vlr.vlr_tag & ~EVL_VLID_MASK) { - error = EINVAL; - break; - } VLAN_LOCK(); error = vlan_config(ifv, p); --- sbin/ifconfig/ifconfig.c.orig Wed Jan 19 10:56:44 2005 +++ sbin/ifconfig/ifconfig.c Wed Jan 19 10:56:24 2005 @@ -248,6 +248,7 @@ #ifdef USE_VLANS { "vlan", NEXTARG, setvlantag }, { "vlandev", NEXTARG, setvlandev }, + { "vlanpri", NEXTARG, setvlandev }, { "-vlandev", NEXTARG, unsetvlandev }, #endif #if 0 --------------060408090903080102040103-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 19 10:34:12 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D97016A4CE for ; Wed, 19 Jan 2005 10:34:12 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7237F43D46 for ; Wed, 19 Jan 2005 10:34:11 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id j0JAY2qr033204; Wed, 19 Jan 2005 05:34:02 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)j0JAY2nc033201; Wed, 19 Jan 2005 10:34:02 GMT (envelope-from robert@fledge.watson.org) Date: Wed, 19 Jan 2005 10:34:02 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: freebsd@newmillennium.net.au In-Reply-To: <004501c4fe00$76180fc0$0201000a@riker> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: IPFW problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 10:34:12 -0000 On Wed, 19 Jan 2005 freebsd@newmillennium.net.au wrote: > I have recently (the last week or so, but possible longer as I had > updated the system prior to going on a 3 week holiday) been having some > problems with IPFW under -CURRENT. > > I am running: > bash-2.05b$ uname -a > FreeBSD picard.newmillennium.net.au 6.0-CURRENT FreeBSD 6.0-CURRENT #38: > Sun Jan 16 18:27:30 EST 2005 > root@picard.newmillennium.net.au:/usr/obj/usr/src/sys/PICARD i386 > > What happens is that I occasionally (every 5 minutes or so) get the > following: Jan 19 16:54:41 picard kernel: ipfw: ouch!, skip past end of > rules, denying packet This error message seems to occur when the end of the rule chain is reached without hitting a packet. The one scenario I can think of where this might happen is if the rule set somehow skips past the end of the chain. Could you confirm two things: - That your ipfw rule set contains no skiptos that push past the last rule? - That your user space ipfw(8) binary is in sync with your kernel? If there's no obvious source of a potential issue of that sort, it may be we're looking at an ipfw bug. The error message should be cleaned up/clarified even if you're seeing the results of a bug, since it's a bit unclear on what actually happened. Robert N M Watson > > And then a (random) TCP connection is dropped. What is interesting is > that every possible path through the firewall matches a rule. I can > provide a copy of the firewall rules on request. > > My firewall uses the following features, in addition to the standard > allow/deny rules: > > Dummynet > Stateful rules (check-state, keep-state) > Skipto's > Forwarding (fwd) > > Some more stuff from the system, in case it helps: > bash-2.05b$ sysctl -a | grep ip\.fw > net.inet.ip.fw.enable: 1 > net.inet.ip.fw.autoinc_step: 100 > net.inet.ip.fw.one_pass: 0 > net.inet.ip.fw.debug: 1 > net.inet.ip.fw.verbose: 1 > net.inet.ip.fw.verbose_limit: 0 > net.inet.ip.fw.dyn_buckets: 256 > net.inet.ip.fw.curr_dyn_buckets: 256 > net.inet.ip.fw.dyn_count: 343 > net.inet.ip.fw.dyn_max: 4096 > net.inet.ip.fw.static_count: 184 > net.inet.ip.fw.dyn_ack_lifetime: 1800 > net.inet.ip.fw.dyn_syn_lifetime: 20 > net.inet.ip.fw.dyn_fin_lifetime: 1 > net.inet.ip.fw.dyn_rst_lifetime: 1 > net.inet.ip.fw.dyn_udp_lifetime: 10 > net.inet.ip.fw.dyn_short_lifetime: 5 > net.inet.ip.fw.dyn_keepalive: 1 > > My kernel options regarding the firewall are: > options IPFIREWALL > options IPDIVERT > options IPFIREWALL_FORWARD > options DUMMYNET > options HZ=1000 > > -- > Alastair D'Silva mob: 0413 485 733 > Networking Consultant fax: 0413 181 661 > New Millennium Networking web: http://www.newmillennium.net.au > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Wed Jan 19 10:42:04 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A66916A4CF; Wed, 19 Jan 2005 10:42:04 +0000 (GMT) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id E192E43D39; Wed, 19 Jan 2005 10:42:03 +0000 (GMT) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.12.8) with ESMTP id j0JAg3vD001639; Wed, 19 Jan 2005 02:42:03 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id j0JAg3xn001638; Wed, 19 Jan 2005 02:42:03 -0800 (PST) (envelope-from rizzo) Date: Wed, 19 Jan 2005 02:42:03 -0800 From: Luigi Rizzo To: Robert Watson Message-ID: <20050119024203.A1604@xorpc.icir.org> References: <004501c4fe00$76180fc0$0201000a@riker> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from rwatson@freebsd.org on Wed, Jan 19, 2005 at 10:34:02AM +0000 cc: freebsd@newmillennium.net.au cc: current@freebsd.org Subject: Re: IPFW problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 10:42:04 -0000 On Wed, Jan 19, 2005 at 10:34:02AM +0000, Robert Watson wrote: ... > > What happens is that I occasionally (every 5 minutes or so) get the > > following: Jan 19 16:54:41 picard kernel: ipfw: ouch!, skip past end of > > rules, denying packet there was a bugfix posted for this bug a few months ago, don't remember who did it or whether it was committed i think the ipfw mailing list archives should have the msg. cheers luigi > This error message seems to occur when the end of the rule chain is > reached without hitting a packet. The one scenario I can think of where > this might happen is if the rule set somehow skips past the end of the > chain. Could you confirm two things: > > - That your ipfw rule set contains no skiptos that push past the last > rule? > > - That your user space ipfw(8) binary is in sync with your kernel? > > If there's no obvious source of a potential issue of that sort, it may be > we're looking at an ipfw bug. The error message should be cleaned > up/clarified even if you're seeing the results of a bug, since it's > a bit unclear on what actually happened. > > Robert N M Watson > > > > > > And then a (random) TCP connection is dropped. What is interesting is > > that every possible path through the firewall matches a rule. I can > > provide a copy of the firewall rules on request. > > > > My firewall uses the following features, in addition to the standard > > allow/deny rules: > > > > Dummynet > > Stateful rules (check-state, keep-state) > > Skipto's > > Forwarding (fwd) > > > > Some more stuff from the system, in case it helps: > > bash-2.05b$ sysctl -a | grep ip\.fw > > net.inet.ip.fw.enable: 1 > > net.inet.ip.fw.autoinc_step: 100 > > net.inet.ip.fw.one_pass: 0 > > net.inet.ip.fw.debug: 1 > > net.inet.ip.fw.verbose: 1 > > net.inet.ip.fw.verbose_limit: 0 > > net.inet.ip.fw.dyn_buckets: 256 > > net.inet.ip.fw.curr_dyn_buckets: 256 > > net.inet.ip.fw.dyn_count: 343 > > net.inet.ip.fw.dyn_max: 4096 > > net.inet.ip.fw.static_count: 184 > > net.inet.ip.fw.dyn_ack_lifetime: 1800 > > net.inet.ip.fw.dyn_syn_lifetime: 20 > > net.inet.ip.fw.dyn_fin_lifetime: 1 > > net.inet.ip.fw.dyn_rst_lifetime: 1 > > net.inet.ip.fw.dyn_udp_lifetime: 10 > > net.inet.ip.fw.dyn_short_lifetime: 5 > > net.inet.ip.fw.dyn_keepalive: 1 > > > > My kernel options regarding the firewall are: > > options IPFIREWALL > > options IPDIVERT > > options IPFIREWALL_FORWARD > > options DUMMYNET > > options HZ=1000 > > > > -- > > Alastair D'Silva mob: 0413 485 733 > > Networking Consultant fax: 0413 181 661 > > New Millennium Networking web: http://www.newmillennium.net.au > > > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Jan 19 11:26:56 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F312C16A4CE; Wed, 19 Jan 2005 11:26:55 +0000 (GMT) Received: from ss.eunet.cz (ss.eunet.cz [193.85.228.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28D6443D5A; Wed, 19 Jan 2005 11:26:55 +0000 (GMT) (envelope-from mime@traveller.cz) Received: from localhost.i.cz (ss.eunet.cz. [193.85.228.13]) by ss.eunet.cz (8.13.1/8.13.1) with ESMTP id j0JBR8MJ035149; Wed, 19 Jan 2005 12:27:08 +0100 (CET) (envelope-from mime@traveller.cz) From: Michal Mertl To: Emanuel Strobl Content-Type: text/plain Date: Wed, 19 Jan 2005 12:26:46 +0100 Message-Id: <1106134006.1132.12.camel@genius2.i.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: akiyama@jp.FreeBSD.org cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org cc: bernd@bwct.de Subject: [Fwd: Re: strange ucom (uplcom) error] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 11:26:56 -0000 Emanuel Strobl wrote: > Am Dienstag, 18. Januar 2005 16:17 schrieb Andrew L. Neporada: > > On Tue, Jan 18, 2005 at 01:06:43PM +0100, Emanuel Strobl wrote: > > > Dear experts, > > > > > > I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working > > > the other one not (I hate to say it but both are working under win). > > > > > > The not working (more expensive) one gets recognized as ucom0 and I have > > > ucom0, also I can receive signal but not transmit. > > > > [skip] > > > > Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch > > http://gate.intercaf.ru/~lesha/6100/pl2303x.patch > > > > It can break old (working) PL2303 chip, but it works for me with newer > > Thanks a lot, this indeed fixes the revision 3.0 adaptor but unfortunately > also breakes the 2.02 version :( > > Perhaps there's a goog guy out there who can refurbish the uplcom driver with > this information (akiyama?)? > > Thanks a lot, I've just recently been looking into this too. I used the mentioned patch and also linux driver source and have come with the attached patch. It contains one more change but I don't know if it's correct. It works for both chips on CURRENT for serial console. It detects if the chip is rev 3.00 and aplies the patch only for it. The author of the patch mentions it isn't binary safe - sometimes the chip stops working. I planned to test it with binary transfers (ppp) today, check if it's working and submit it (with some cleanup) for inclusion in FreeBSD. Michal Mertl From owner-freebsd-current@FreeBSD.ORG Tue Jan 18 20:08:47 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D502016A4CE; Tue, 18 Jan 2005 20:08:47 +0000 (GMT) Received: from dave.horsfall.org (mrdavi2.lnk.telstra.net [139.130.75.233]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43BB543D1D; Tue, 18 Jan 2005 20:08:45 +0000 (GMT) (envelope-from dave@horsfall.org) Received: from localhost (dave@localhost) by dave.horsfall.org (8.11.4/8.11.4) with ESMTP id j0IK8gt16746; Wed, 19 Jan 2005 07:08:42 +1100 (EST) Date: Wed, 19 Jan 2005 07:08:41 +1100 (EST) From: Dave Horsfall To: FreeBSD STABLE list , freebsd-current@freebsd.org In-Reply-To: <20050118151707.GA26651@nas.dgap.mipt.ru> Message-ID: References: <200501181306.49120.emanuel.strobl@gmx.net> <20050118151707.GA26651@nas.dgap.mipt.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Wed, 19 Jan 2005 13:22:32 +0000 Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Jan 2005 20:08:48 -0000 On Tue, 18 Jan 2005, Andrew L. Neporada wrote: > > The not working (more expensive) one gets recognized as ucom0 and I have > > ucom0, also I can receive signal but not transmit. > > > [skip] > > Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch > http://gate.intercaf.ru/~lesha/6100/pl2303x.patch > > It can break old (working) PL2303 chip, but it works for me with newer > revision chip (tested under 4.10). Hmmm... That could explain something I saw. I've got two cables, bought from different vendors (same chipset). Both worked under 4.10, only one under 5.3 (different platforms). I'll try it when I get a moment. -- Dave From owner-freebsd-current@FreeBSD.ORG Wed Jan 19 11:44:23 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFDEE16A4CE; Wed, 19 Jan 2005 11:44:23 +0000 (GMT) Received: from picard.newmillennium.net.au (220-245-208-145-act.tpgi.com.au [220.245.208.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84E1743D49; Wed, 19 Jan 2005 11:44:22 +0000 (GMT) (envelope-from alastair@newmillennium.net.au) Received: from riker (riker.nmn.cafn [10.0.1.2])j0JBiJ3I063936; Wed, 19 Jan 2005 22:44:19 +1100 (EST) (envelope-from alastair@newmillennium.net.au) From: "Alastair D'Silva" To: "'Luigi Rizzo'" , "'Robert Watson'" Date: Wed, 19 Jan 2005 22:44:19 +1100 Organization: New Millennium Networking Message-ID: <000201c4fe1c$36b29870$0201000a@riker> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 In-Reply-To: <20050119024203.A1604@xorpc.icir.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Mailman-Approved-At: Wed, 19 Jan 2005 13:22:32 +0000 cc: current@freebsd.org Subject: RE: IPFW problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 11:44:24 -0000 > -----Original Message----- > From: Luigi Rizzo [mailto:rizzo@icir.org] > Sent: Wednesday, 19 January 2005 9:42 PM > To: Robert Watson > Cc: freebsd@newmillennium.net.au; current@freebsd.org > Subject: Re: IPFW problems > > there was a bugfix posted for this bug a few months > ago, don't remember who did it or whether it was committed > i think the ipfw mailing list archives should have the msg. Luigi, was this the patch you are referring to? If so, I'll recompile and test it tomorrow. http://lists.freebsd.org/pipermail/freebsd-ipfw/2004-May/001095.html Robert, I've verified that my kernel and userland are in sync. The highest skipto target in my rules is 6500 (which doesn't actually exist) and the highest rule I have is 6599 (deny all from any to any). -- Alastair D'Silva mob: 0413 485 733 Networking Consultant fax: 0413 181 661 New Millennium Networking web: http://www.newmillennium.net.au From owner-freebsd-current@FreeBSD.ORG Wed Jan 19 14:26:03 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0BB1816A4CE for ; Wed, 19 Jan 2005 14:26:03 +0000 (GMT) Received: from relay.pair.com (relay00.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 7819A43D5C for ; Wed, 19 Jan 2005 14:26:02 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 18404 invoked from network); 19 Jan 2005 14:26:01 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 19 Jan 2005 14:26:01 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id j0JEQ02m023007 for ; Wed, 19 Jan 2005 15:26:00 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id j0JEQ0ku023006 for current@freebsd.org; Wed, 19 Jan 2005 15:26:00 +0100 (CET) (envelope-from pho) Date: Wed, 19 Jan 2005 15:25:59 +0100 From: Peter Holm To: current@freebsd.org Message-ID: <20050119142559.GA22981@peter.osted.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Freeze X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 14:26:03 -0000 With GENERIC HEAD from Jan 18 19:27 UTC I got a freeze ~KDB: enter: Line break on console [thread pid 14589 tid 100259 ] Stopped at kdb_enter+0x2b: nop db> show pcpu cpuid = 0 curthread = 0xc2139170: pid 14589 "swap" curpcb = 0xcf406da0 fpcurthread = none idlethread = 0xc151f5c0: pid 11 "idle: cpu0" APIC ID = 0 currentldt = 0x30 spin locks held: db> where Tracing pid 14589 tid 100259 td 0xc2139170 kdb_enter(c0845129) at kdb_enter+0x2b siointr1(c1695400,c0953900,0,c0844f39,56f) at siointr1+0xce siointr(c1695400) at siointr+0x21 intr_execute_handlers(c1510090,cf406d44,4,bfbfea58,c07a7b53) at intr_execute_handlers+0x9d lapic_handle_intr(34) at lapic_handle_intr+0x2e Xapic_isr1() at Xapic_isr1+0x33 --- interrupt, eip = 0x8048ef9, esp = 0xbfbfea40, ebp = 0xbfbfea58 --- db> show alllocks Process 14660 (sh) thread 0xc2817450 (101123) exclusive sleep mutex process lock r = 0 (0xc1c58458) locked @ kern/kern_fork.c:300 exclusive sx allproc r = 0 (0xc08eb8a0) locked @ kern/kern_fork.c:287 shared sx proctree r = 0 (0xc08eb8e0) locked @ kern/kern_fork.c:278 Process 14580 (thr1) thread 0xc24db450 (100443) exclusive sx user map r = 0 (0xc1ce4ad0) locked @ vm/vm_map.c:2994 Process 14573 (syscall) thread 0xc24e8450 (100493) exclusive sx user map r = 0 (0xc253b4f4) locked @ vm/vm_glue.c:171 Process 2173 (top) thread 0xc17595c0 (100074) exclusive sx sysctl lock r = 0 (0xc08ebe60) locked @ kern/kern_sysctl.c:1335 Process 2033 (cron) thread 0xc162a5c0 (100054) shared sx proctree r = 0 (0xc08eb8e0) locked @ kern/kern_fork.c:278 More info at http://www.holm.cc/stress/log/cons109.html -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Wed Jan 19 18:57:34 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9019216A4CE for ; Wed, 19 Jan 2005 18:57:34 +0000 (GMT) Received: from portpc-design.spb.ru (ns2.portpc-design.spb.ru [195.161.118.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id C97B543D45 for ; Wed, 19 Jan 2005 18:57:32 +0000 (GMT) (envelope-from mcsi@mcsi.pp.ru) Received: from [83.237.61.135] (ppp83-237-61-135.pppoe.mtu-net.ru [83.237.61.135]) (authenticated bits=0) by portpc-design.spb.ru (8.13.3/8.13.3) with ESMTP id j0JIvUPX098233 for ; Wed, 19 Jan 2005 21:57:30 +0300 (MSK) (envelope-from mcsi@mcsi.pp.ru) Message-ID: <41EEAD95.5080706@mcsi.pp.ru> Date: Wed, 19 Jan 2005 21:57:25 +0300 From: Maxim Maximov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20041224 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: kernel panic (ACPI/fdc/sysctl) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 18:57:34 -0000 Hi. Current frshly built kernel paniced: Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-CURRENT #1: Wed Jan 19 20:38:38 MSK 2005 mcsi@ultra.domain:/usr/obj/usr/src/sys/ULTRA WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (2992.52-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 536674304 (511 MB) avail memory = 514953216 (491 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) acpi_ec0: port 0x66,0x62 on acpi0 acpi_ec0: can't allocate data port device_attach: acpi_ec0 attach returned 6 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_ec0: port 0x66,0x62 on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xf8000000-0xfbffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) uhci0: port 0xe000-0xe01f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xe400-0xe41f 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 ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. ukbd0: Alcor Micro product 0x3002, rev 1.10/1.00, addr 3, iclass 3/1 kbd1 at ukbd0 uhid0: Alcor Micro product 0x3002, rev 1.10/1.00, addr 3, iclass 3/1 uhci2: port 0xe800-0xe81f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 ...skipping... e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto cbb0: irq 16 at device 1.0 on pci2 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb1: irq 17 at device 1.1 on pci2 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 fwohci0: mem 0xfeafb000-0xfeafb7ff irq 18 at device 1.2 on pci2 fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:e0:18:00:03:18:f3:bc fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:e0:18:18:f3:bc fwe0: Ethernet address: 02:e0:18:18:f3:bc fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) pci2: at device 1.3 (no driver attached) pci2: at device 1.4 (no driver attached) ndis0: mem 0xfeaf8000-0xfeaf9fff irq 17 at device 2.0 on pci2 ndis0: NDIS API version: 5.0 ndis0: Ethernet address: 00:0e:a6:c2:00:e4 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pcm0: port 0xd000-0xd03f,0xd400-0xd4ff mem 0xfebff400-0xfebff4ff,0xfebff800-0xfebff9ff irq 17 at device 31.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: pci0: at device 31.6 (no driver attached) acpi_button0: on acpi0 acpi_lid0: on acpi0 acpi_button1: on acpi0 pci_link0: irq 9 on acpi0 pci_link1: irq 5 on acpi0 pci_link2: irq 5 on acpi0 pci_link3: irq 0 on acpi0 pci_link4: irq 0 on acpi0 pci_link5: irq 0 on acpi0 pci_link6: irq 0 on acpi0 pci_link7: irq 5 on acpi0 acpi_tz0: on acpi0 acpi_acad0: on acpi0 acpi_cmbat0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Synaptics Touchpad, device ID 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 device_attach: fdc0 attach returned 6 ppc0: port 0x778-0x77f,0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 device_attach: fdc0 attach returned 6 Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x19 fault code = supervisor read, page not present instruction pointer = 0x8:0xc065cf4d stack pointer = 0x10:0xc0c20c34 frame pointer = 0x10:0xc0c20c40 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) sysctl_find_oidname+0x15: pushl 0x18 sysctl_add_oid acpi_wake_sysctl_walk acpi_attach ... -- Maxim Maximov From owner-freebsd-current@FreeBSD.ORG Wed Jan 19 20:39:22 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3762D16A4CE for ; Wed, 19 Jan 2005 20:39:22 +0000 (GMT) Received: from postfix3-2.free.fr (postfix3-2.free.fr [213.228.0.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7F7243D1F for ; Wed, 19 Jan 2005 20:39:21 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix3-2.free.fr (Postfix) with ESMTP id 134B7C2BB; Wed, 19 Jan 2005 21:39:18 +0100 (CET) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 122E9407C; Wed, 19 Jan 2005 21:39:10 +0100 (CET) Date: Wed, 19 Jan 2005 21:39:10 +0100 From: Jeremie Le Hen To: nikolay.nenchev@rbb-sofia.raiffeisen.at Message-ID: <20050119203910.GD36629@obiwan.tataz.chchile.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: Bind 9.3 rndc? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 20:39:22 -0000 You should use freebsd-net@ for this kind of questions I think. > have installed FreeBSD 5.3 with Bind integrated in it. named is running in > chroot, with user bind, so every file in /etc/namedb is owned by > bind:wheel, exept rndc.key. (i have also rndc.conf with owner bind) > and it is impossible to start make rndc reload. if i change owner on > rndc.key it is working but is it a security issue, user who is running > named (bind) to have acceess to rndc.key. How does named(8) could know that the secret provided by rndc(8) is the correct one if it does not have access to it ? This is a shared secret. Either user running named(8) and the one running rndc(8) must have access to the secret. Let's say you have named(8) running under user "bind" and the rndc user running under user "rndc" and both belongs to group "bind". Make rndc.key owned my "root:bind" and use the mode 0640. Therefore only root will be able to modify the key whereas named(8) and rndc(8) will be able to read it. Anyway, if your bind(8) is compromised, whether th attacker can read your shared secret or not is pointless : you will have to change it anyway. Best regards, -- Jeremie Le Hen jeremie@le-hen.org From owner-freebsd-current@FreeBSD.ORG Wed Jan 19 21:06:03 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE80D16A4CE for ; Wed, 19 Jan 2005 21:06:03 +0000 (GMT) Received: from gateway.nixsys.be (gateway.nixsys.be [195.144.77.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EEAC43D3F for ; Wed, 19 Jan 2005 21:06:03 +0000 (GMT) (envelope-from philip@paeps.cx) Received: from wotan.home.paeps.cx (wotan.home.paeps.cx [IPv6:2001:838:37f:10:a00:20ff:fe9b:138c]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "wotan.home.paeps.cx", Issuer "NixSys CA" (verified OK)) by gateway.nixsys.be (Postfix) with ESMTP id 978EDC171; Wed, 19 Jan 2005 22:06:02 +0100 (CET) Received: from fasolt.home.paeps.cx (fasolt.home.paeps.cx [IPv6:2001:838:37f:10:20a:e6ff:fe7d:c08]) by wotan.home.paeps.cx (Postfix) with ESMTP id 381E8618B; Wed, 19 Jan 2005 22:06:01 +0100 (CET) Received: from fasolt.home.paeps.cx (philip@localhost [127.0.0.1]) by fasolt.home.paeps.cx (8.13.1/8.13.1) with ESMTP id j0JL5ueI022878; Wed, 19 Jan 2005 22:05:56 +0100 (CET) (envelope-from philip@fasolt.home.paeps.cx) Received: (from philip@localhost) by fasolt.home.paeps.cx (8.13.1/8.13.1/Submit) id j0JL5tfR022877; Wed, 19 Jan 2005 22:05:55 +0100 (CET) (envelope-from philip) Date: Wed, 19 Jan 2005 22:05:55 +0100 From: Philip Paeps To: Eric Kjeldergaard Message-ID: <20050119210555.GF14706@fasolt.home.paeps.cx> Mail-Followup-To: Eric Kjeldergaard , current@freebsd.org References: <20050110131529.GA716@loge.nixsys.be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Date-in-Rome: ante diem XIV Kalendas Februarias MMDCCLVIII ab Urbe Condida X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3 FC53 BF4B D0E6 049D B879 X-Message-Flag: Get a proper mailclient! Organization: Happily Disorganized User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: [PLEASE TEST] Many improvements to Synaptics support in psm(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 21:06:04 -0000 On 2005-01-18 23:32:20 (-0600), Eric Kjeldergaard wrote: > > I just committed a patch to -current which greatly improves support in > > psm(4) for Synaptics touchpads. Owners of these gadgets are encouraged to > > test this. If it turns out to work well, I'll enable support by default. > > > > # Should the extra buttons act as axes or as middle button > > hw.psm.synaptics.directional_scrolls > > Well, trying to test this little setting here. Seems like it would be great > to get horiz and vert scroll working, and since I saw this mail message go > through, I thought I'd help test. Thanks :-) > Perhaps I'm doing > something really dumb, but I can't seem to get scrolling going on this > with the new psm at all. Do you actually have scroll buttons on your touchpad? As in, some extra buttons that don't appear to do anything? Or are you trying the gesture bit, tapping twice then holding? I'm aware of the fact that the gesture isn't working yet, and that there's some 'funny stuff' if you try to tap with more than one finger. Work on the gestures is ongoing and should be done Real Soon Now[tm]. If you have buttons that aren't working, it would be nice to know what psm tells you when it's probing with a hint debug.psm.loglevel=2. Particularly the capa and info lines would be useful. Thanks! - Philip -- Philip Paeps Please don't Cc me, I am philip@freebsd.org subscribed to the list. Duncan: I've forgotten every thing I used to know about Z80 assembler. Ann: Congratulations you're cured. From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 01:06:21 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E4ED816A4CE for ; Thu, 20 Jan 2005 01:06:21 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7539943D31 for ; Thu, 20 Jan 2005 01:06:21 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from error404.nls.net (ketrien@error404.nls.net [216.144.36.24]) by error404.nls.net (8.13.1/8.13.1) with ESMTP id j0K17aAw010598 for ; Wed, 19 Jan 2005 20:07:37 -0500 (EST) (envelope-from ketrien@error404.nls.net) Date: Wed, 19 Jan 2005 20:07:36 -0500 (EST) From: "Ketrien I. Saihr-Kenchedra" X-X-Sender: ketrien@bahre.achedra.org To: current@freebsd.org Message-ID: <20050119200215.J1832@bahre.achedra.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV 0.80/671/Mon Jan 17 09:16:31 2005 clamav-milter version 0.80j on bahre.achedra.org X-Virus-Status: Clean Subject: LOR - pcn vs radix node head (Jan16 -CUR) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 01:06:22 -0000 This one comes from the same Jan16 -CUR. pcn(4) has the patch I sent earlier this week applied. It's non-fatal, and I can't seem to reproduce it now. (Multiple attach/detach cycles have not exposed the ACPI LOR again, hooray!) ukphy0: detached miibus0: detached lock order reversal 1st 0xc214bf90 pcn0 (network driver) @ /usr/src/sys/modules/pcn/../../pci/if_pcn.c:1386 2nd 0xc1d0be7c radix node head (radix node head) @ net/route.c:1171 KDB: stack backtrace: witness_checkorder(c1d0be7c,9,c070bfd9,493,9) at witness_checkorder+0x5c6 _mtx_lock_flags(c1d0be7c,0,c070bfd0,493,c1d0be7c) at _mtx_lock_flags+0x54 rtinit(c1f5f900,2,0,c1f5f900,c0745200) at rtinit+0x165 in_ifscrub(c214b800,c1f5f900,c0745200,c07452dc,db26cb38) at in_ifscrub+0x117 rip_ctlinput(0,c1f5f9c4,0,c1f5f900,c214b800) at rip_ctlinput+0x4b pfctlinput(0,c1f5f9c4,c0767840,0,c214b800) at pfctlinput+0x63 if_down(c214b800,12b,0,c0743440,c0743464) at if_down+0x35 if_detach(c214b800,c214b800,db26cbf8,c2179706,c214b800) at if_detach+0x10e ether_ifdetach(c214b800,8,c217a7a3,299,c1c59380) at ether_ifdetach+0x23 pcn_detach(c1c59380,c214c850,c073606c,933,c217b990) at pcn_detach+0xd6 device_detach(c1c59380,c217a6f9,c2123740,1,c1c1fa00) at device_detach+0x99 devclass_delete_driver(c1c1fa00,c217b990,1f2,0,c21237c0) at devclass_delete_driver+0xd1 driver_module_handler(c21237c0,1,c217b97c) at driver_module_handler+0xe2 module_unload(c21237c0,0,1f2,c1f5e000,c07001e5) at module_unload+0x68 linker_file_unload(c1f5e000,0,c07001ee,31e,bfbfe8b0) at linker_file_unload+0x29d kern_kldunload(0,db26cd14,8,3ff,2) at kern_kldunload+0x8c syscall(2f,2f,2f,3,bfbfee2a) at syscall+0x137 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (444, FreeBSD ELF32, kldunloadf), eip = 0x280c459f, esp = 0xbfbfe8ac, ebp = 0xbfbfed24 --- pcn0: detached -ksaihr From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 02:00:01 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D53B616A4CE for ; Thu, 20 Jan 2005 02:00:01 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2368243D41 for ; Thu, 20 Jan 2005 02:00:01 +0000 (GMT) (envelope-from chiahsing@gmail.com) Received: by wproxy.gmail.com with SMTP id 50so69115wri for ; Wed, 19 Jan 2005 17:59:57 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=EIXRhWi+s9IRtAVhkk43lGjZKnkMVnYj+yCSOO/7ygBmcFb4NxFsvSChBIkdUN9K1XrDZEGOaj9RgjmgyDhsympXL8Mo0WsLBEtzrJjmNzJJaQx0j9FeavwkDNpLm39bK12C0Uk5WTfOxAHGhgXDt+E5I8Jk7cBHu+SkB2EhPzY= Received: by 10.54.13.43 with SMTP id 43mr287799wrm; Wed, 19 Jan 2005 17:59:57 -0800 (PST) Received: by 10.54.31.21 with HTTP; Wed, 19 Jan 2005 17:59:57 -0800 (PST) Message-ID: Date: Wed, 19 Jan 2005 17:59:57 -0800 From: David Yu To: freebsd-fs@freebsd.org, freebsd-current@freebsd.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050117020039.GB630@nu.org> <20050117032255.GC630@nu.org> Subject: Re: NTFS unicode converting problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Yu List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 02:00:02 -0000 I wrote a patch for mounting NTFS as UTF-8. The patch is at http://www.cse.ucsd.edu/~chyu/ntfs-utf8.diff . After patch, you need to recompile the kernel module libiconv and ntfs (or the whole kernel if you do not use kernel module). This patch should solve the problem that the original libiconv in the kernel cannot convert characters to UTF-8 longer than 2 bytes per char. I ported the UTF-8 <-> UCS-2 converter from GNU libiconv into the kernel. However, I don't know how to implement "casetype" in the conversion function, this may cause some problem in case insensitive matching used in msdosfs. I think this patch should just be a temporary workaround. The libiconv in the kernel should be rewritten for a good structure. From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 03:26:49 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 741F616A4CE for ; Thu, 20 Jan 2005 03:26:49 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id F356443D58 for ; Thu, 20 Jan 2005 03:26:48 +0000 (GMT) (envelope-from kjelderg@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so40648rnf for ; Wed, 19 Jan 2005 19:26:48 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=iVLpUKf+1LU3Pn4yDYZar5liXpti6B4wBFzVsifDjNwtKhQmqazSUHITP9Moad6tdyHGc30HwJvfnOU2nDObAD5CpCbvJwQTR/Xn77f/EwpBzyHszLcmhdOXFCHzTJjqQYhGYkcOHVHNyCwUlUDwElmi0pxFeuO6MVLAkc2QI/Y= Received: by 10.38.11.55 with SMTP id 55mr36164rnk; Wed, 19 Jan 2005 19:26:48 -0800 (PST) Received: by 10.38.101.3 with HTTP; Wed, 19 Jan 2005 19:26:48 -0800 (PST) Message-ID: Date: Wed, 19 Jan 2005 21:26:48 -0600 From: Eric Kjeldergaard To: current@freebsd.org In-Reply-To: <20050119210555.GF14706@fasolt.home.paeps.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20050110131529.GA716@loge.nixsys.be> <20050119210555.GF14706@fasolt.home.paeps.cx> Subject: Re: [PLEASE TEST] Many improvements to Synaptics support in psm(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Eric Kjeldergaard List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 03:26:49 -0000 > > Perhaps I'm doing > > something really dumb, but I can't seem to get scrolling going on this > > with the new psm at all. > > Do you actually have scroll buttons on your touchpad? As in, some extra > buttons that don't appear to do anything? Or are you trying the gesture bit, > tapping twice then holding? I'm aware of the fact that the gesture isn't > working yet, and that there's some 'funny stuff' if you try to tap with more > than one finger. Well, I fear misunderstanding may be the source of my problems. I was thinking of "edge scrolling" or whatever you choose to call it. Scrolling by running my finger along the right or bottom edge of the touchpad. Not an external jog dial as I've seen, or even a particularly split pad. Is this just for the mice with external dials? -- If I write a signature, my emails will appear more personalised. From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 07:16:40 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB51516A562; Thu, 20 Jan 2005 07:16:38 +0000 (GMT) Received: from picard.newmillennium.net.au (220-245-208-145-act.tpgi.com.au [220.245.208.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42B9443D55; Thu, 20 Jan 2005 07:16:37 +0000 (GMT) (envelope-from alastair@newmillennium.net.au) Received: from riker (riker.nmn.cafn [10.0.1.2])j0K7GYS0001306; Thu, 20 Jan 2005 18:16:35 +1100 (EST) (envelope-from alastair@newmillennium.net.au) From: Sender: "Alastair D'Silva" To: "'Luigi Rizzo'" , "'Robert Watson'" Date: Thu, 20 Jan 2005 18:16:35 +1100 Organization: New Millennium Networking Message-ID: <000201c4febf$fa421560$0201000a@riker> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <000201c4fe1c$36b29870$0201000a@riker> Importance: Normal cc: current@freebsd.org Subject: RE: IPFW problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 07:16:40 -0000 > > there was a bugfix posted for this bug a few months > > ago, don't remember who did it or whether it was committed > > i think the ipfw mailing list archives should have the msg. > > Luigi, was this the patch you are referring to? If so, I'll > recompile and test it tomorrow. > > http://lists.freebsd.org/pipermail/freebsd-ipfw/2004-May/001095.html I've applied the above patch (with some modifications) and the TCP connections are still being dropped. No "Ouch!" messages have yet appeared, but the machine has only been up for 15 minutes or so. -- Alastair D'Silva mob: 0413 485 733 Networking Consultant fax: 0413 181 661 New Millennium Networking web: http://www.newmillennium.net.au From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 08:00:35 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C894216A4CF; Thu, 20 Jan 2005 08:00:35 +0000 (GMT) Received: from picard.newmillennium.net.au (220-245-208-145-act.tpgi.com.au [220.245.208.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3A0B43D4C; Thu, 20 Jan 2005 08:00:34 +0000 (GMT) (envelope-from alastair@newmillennium.net.au) Received: from riker (riker.nmn.cafn [10.0.1.2])j0K80Xwt001759; Thu, 20 Jan 2005 19:00:33 +1100 (EST) (envelope-from alastair@newmillennium.net.au) From: Sender: "Alastair D'Silva" To: "'Luigi Rizzo'" , "'Robert Watson'" Date: Thu, 20 Jan 2005 19:00:32 +1100 Organization: New Millennium Networking Message-ID: <000901c4fec6$1dcf2170$0201000a@riker> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <000201c4febf$fa421560$0201000a@riker> Importance: Normal cc: current@freebsd.org Subject: RE: IPFW problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 08:00:35 -0000 > I've applied the above patch (with some modifications) and > the TCP connections are still being dropped. No "Ouch!" > messages have yet appeared, but the machine has only been up > for 15 minutes or so. > A quick update, I have now had 5 of the "Ouch!" messages. -- Alastair D'Silva mob: 0413 485 733 Networking Consultant fax: 0413 181 661 New Millennium Networking web: http://www.newmillennium.net.au From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 08:43:24 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 234FA16A4CE for ; Thu, 20 Jan 2005 08:43:24 +0000 (GMT) Received: from mx04.mdcs.at (mx04.mdcs.at [193.110.28.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8F5443D58 for ; Thu, 20 Jan 2005 08:43:22 +0000 (GMT) (envelope-from nikolay.nenchev@rbb-sofia.raiffeisen.at) To: freebsd-current@freebsd.org MIME-Version: 1.0 Message-ID: From: nikolay.nenchev@rbb-sofia.raiffeisen.at Date: Thu, 20 Jan 2005 09:54:23 +0200 X-Priority: 3 (Normal) Content-Type: text/plain; charset="US-ASCII" X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: DNS reverse zone problem? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 08:43:24 -0000 I have problems with reverse zone. I have classless adress from 0-63, so I'm wiht mask /26. My reverse zone file: $TTL 3600 $ORIGIN 0/26.XXX.XXX.XXX.in-addr.arpa. @ IN SOA ns1.example.com. root.example.com. ( 2005011901 ; Serial 10800 ; Refresh 3600 ; Retry 604800 ; Expire 3600 ) ; Minimum @ IN NS ns1.exapmle.com. 1 IN PTR ns1.example.com. 7 IN PTR mail1.example.com. 5 IN PTR example.com. Error messages: named[96142]: client SOURCE_IP#4981: query (cache) 'MY_DNS_IP_ADDRESS.in-addr.arpa/PTR/IN' denied it is a little bit strange because the dns server is with internal ip address 10.0.0.1, and the firewall in front it is making NAT for the extarnal IP address (XXX.XXX.XXX.1). i haven't zone for network 10.0.0.0. and the hosts file is: 127.0.0.1 localhost 10.0.0.1 ns1.example.com Any comment is appreciated. nikolay nenchev From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 11:00:55 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B893016A4CE for ; Thu, 20 Jan 2005 11:00:55 +0000 (GMT) Received: from mail.vdsoft.org (poseidon.vdsoft.org [193.85.147.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22D9A43D2D for ; Thu, 20 Jan 2005 11:00:55 +0000 (GMT) (envelope-from dvorakv@vdsoft.org) Received: from [10.0.0.132] (unknown [10.0.0.132]) by mail.vdsoft.org (Postfix) with ESMTP id 26CA147E020; Thu, 20 Jan 2005 12:00:49 +0100 (CET) Message-ID: <41EF8FB4.3090406@vdsoft.org> Date: Thu, 20 Jan 2005 12:02:12 +0100 From: Vladimir Dvorak User-Agent: Debian Thunderbird 1.0 (X11/20050116) X-Accept-Language: en-us, en MIME-Version: 1.0 To: nikolay.nenchev@rbb-sofia.raiffeisen.at References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: DNS reverse zone problem? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 11:00:55 -0000 nikolay.nenchev@rbb-sofia.raiffeisen.at wrote: >I have problems with reverse zone. I have classless adress from 0-63, so >I'm wiht mask /26. > > If you have /26 network, is has no sense to set up reverse zone, because no nameserver will query it. You can up only classfull (like /24 ) in-addra.arpa zones. Ask your provider. Vladimir From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 11:02:03 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CDC216A4CE for ; Thu, 20 Jan 2005 11:02:03 +0000 (GMT) Received: from mx04.mdcs.at (mx04.mdcs.at [193.110.28.61]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A32043D45 for ; Thu, 20 Jan 2005 11:02:02 +0000 (GMT) (envelope-from nikolay.nenchev@rbb-sofia.raiffeisen.at) To: freebsd-current@freebsd.org MIME-Version: 1.0 Message-ID: From: nikolay.nenchev@rbb-sofia.raiffeisen.at Date: Thu, 20 Jan 2005 12:26:33 +0200 X-Priority: 3 (Normal) Content-Type: multipart/mixed; boundary="=_mixed 00394D7942256F8F_=" X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: ceri@submonkey.net Subject: Fw: DNS reverse zone problem? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 11:02:03 -0000 --=_mixed 00394D7942256F8F_= Content-Type: text/plain; charset="US-ASCII" from named.conf: zone "0/26.XXX.XXX.XXX.in-addr.arpa." { type master; file "master/example.com.rev" allow-query { any; } ; allow-transfer { myslave server; } ; }; ceri@submonkey.net Sent by: setantae@submonkey.net 20.01.2005 11:21 To nikolay.nenchev@rbb-sofia.raiffeisen.at cc ceri@submonkey.net Subject Re: DNS reverse zone problem? On Thu, Jan 20, 2005 at 09:54:23AM +0200, nikolay.nenchev@rbb-sofia.raiffeisen.at wrote: > I have problems with reverse zone. I have classless adress from 0-63, so > I'm wiht mask /26. > My reverse zone file: > $TTL 3600 > $ORIGIN 0/26.XXX.XXX.XXX.in-addr.arpa. > @ IN SOA ns1.example.com. root.example.com. ( > 2005011901 ; Serial > 10800 ; Refresh > 3600 ; Retry > 604800 ; Expire > 3600 ) ; Minimum > > @ IN NS ns1.exapmle.com. "example" is spelt incorrectly there, but it's not the cause of your problem. > 1 IN PTR ns1.example.com. > 7 IN PTR mail1.example.com. > 5 IN PTR example.com. > > Error messages: > > named[96142]: client SOURCE_IP#4981: query (cache) > 'MY_DNS_IP_ADDRESS.in-addr.arpa/PTR/IN' denied Make sure that SOURCE_IP is allowed to query in the server's named.conf (the allow-query statement). Ceri -- Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. -- Einstein (attrib.) --=_mixed 00394D7942256F8F_= Content-Type: application/octet-stream; name="att203be.dat" Content-Disposition: attachment; filename="att203be.dat" Content-Transfer-Encoding: base64 LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0NClZlcnNpb246IEdudVBHIHYxLjQuMCAoRnJl ZUJTRCkNCg0KaUQ4REJRRkI3M2czb2NmY3dUUzNKRjhSQXFYL0FKNGxVNVVpbkozdXZvQlJoeEE2 NDdVdi95ZjBzZ0NnbFdmdw0KU09saU9aaTZCc2ljU2hXaGZmcGd2OW89DQo9TUlITQ0KLS0tLS1F TkQgUEdQIFNJR05BVFVSRS0tLS0tDQo= --=_mixed 00394D7942256F8F_=-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 11:13:43 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9587D16A4CE for ; Thu, 20 Jan 2005 11:13:43 +0000 (GMT) Received: from shrike.submonkey.net (cpc2-cdif3-6-0-cust204.cdif.cable.ntl.com [81.103.67.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CDB143D1D for ; Thu, 20 Jan 2005 11:13:43 +0000 (GMT) (envelope-from setantae@submonkey.net) Received: from setantae by shrike.submonkey.net with local (Exim 4.43 (FreeBSD)) id 1CraFx-000J3F-Ji; Thu, 20 Jan 2005 11:13:41 +0000 Date: Thu, 20 Jan 2005 11:13:41 +0000 From: Ceri Davies To: Vladimir Dvorak Message-ID: <20050120111341.GM49329@submonkey.net> Mail-Followup-To: Ceri Davies , Vladimir Dvorak , nikolay.nenchev@rbb-sofia.raiffeisen.at, freebsd-current@freebsd.org References: <41EF8FB4.3090406@vdsoft.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cqPFywB/e6uXot/h" Content-Disposition: inline In-Reply-To: <41EF8FB4.3090406@vdsoft.org> X-PGP: finger ceri@FreeBSD.org User-Agent: Mutt/1.5.6i Sender: Ceri Davies cc: freebsd-current@freebsd.org cc: nikolay.nenchev@rbb-sofia.raiffeisen.at Subject: Re: DNS reverse zone problem? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 11:13:43 -0000 --cqPFywB/e6uXot/h Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 20, 2005 at 12:02:12PM +0100, Vladimir Dvorak wrote: > nikolay.nenchev@rbb-sofia.raiffeisen.at wrote: >=20 > >I have problems with reverse zone. I have classless adress from 0-63, so= =20 > >I'm wiht mask /26. > >=20 > > > If you have /26 network, is has no sense to set up reverse zone, because= =20 > no nameserver will query it. You can up only classfull (like /24 )=20 > in-addra.arpa zones. Ask your provider. That's not strictly true, there are ways of delegating subnets of /24s. Ceri --=20 Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. -- Einstein (attrib.) --cqPFywB/e6uXot/h Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB75JlocfcwTS3JF8RAh/AAJoDTmjKfJo22Hgr/ZK+LI4UVo+KZQCgq6qC BkkPco+uupgjhN9pUq+PHCM= =AHH3 -----END PGP SIGNATURE----- --cqPFywB/e6uXot/h-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 11:21:15 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CA2B16A4CE for ; Thu, 20 Jan 2005 11:21:15 +0000 (GMT) Received: from shrike.submonkey.net (cpc2-cdif3-6-0-cust204.cdif.cable.ntl.com [81.103.67.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FBD443D49 for ; Thu, 20 Jan 2005 11:21:15 +0000 (GMT) (envelope-from setantae@submonkey.net) Received: from setantae by shrike.submonkey.net with local (Exim 4.43 (FreeBSD)) id 1CraNG-000JTh-Cz; Thu, 20 Jan 2005 11:21:14 +0000 Date: Thu, 20 Jan 2005 11:21:14 +0000 From: Ceri Davies To: nikolay.nenchev@rbb-sofia.raiffeisen.at Message-ID: <20050120112114.GN49329@submonkey.net> Mail-Followup-To: Ceri Davies , nikolay.nenchev@rbb-sofia.raiffeisen.at, freebsd-current@freebsd.org References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ufBapV6AXnt9KAs/" Content-Disposition: inline In-Reply-To: X-PGP: finger ceri@FreeBSD.org User-Agent: Mutt/1.5.6i Sender: Ceri Davies cc: freebsd-current@freebsd.org Subject: Re: Fw: DNS reverse zone problem? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 11:21:15 -0000 --ufBapV6AXnt9KAs/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 20, 2005 at 12:26:33PM +0200, nikolay.nenchev@rbb-sofia.raiffei= sen.at wrote: > from named.conf:=20 >=20 > zone "0/26.XXX.XXX.XXX.in-addr.arpa." { > type master; > file "master/example.com.rev" > allow-query { any; } ; > allow-transfer { > myslave server; > } ; > }; That's a very strange zone declaration. You'd normally have a zone named 0.z.y.x.in-addr.arpa with PTR records from 1-62 therein, and the above zone delegated to you. Then the z.y.x.in-addr.arpa zone would include CNAMEs such as: $ORIGIN z.y.x.in-addr.arpa. 1 IN CNAME 1.0.z.y.x.in-addr.arpa. 2 IN CNAME 2.0.z.y.x.in-addr.arpa. Anyway, I think the zone name above is your problem. Failing that, please explain how your reverse DNS is delegated (note: at times like this, obfuscation of IP addresses is likely to make it harder for me to understand your situation, so I may just give up if you continue to do this). Ceri PS. This is *way* off-topic for current@. --=20 Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. -- Einstein (attrib.) --ufBapV6AXnt9KAs/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB75QqocfcwTS3JF8RAukyAJ9RNq2/PwHwpNhONOtpuQq5ycb7rACgxqfv 5TswL/wII6woyIOYesoJnEM= =Vn7y -----END PGP SIGNATURE----- --ufBapV6AXnt9KAs/-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 19 23:14:44 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86C1516A4CE for ; Wed, 19 Jan 2005 23:14:44 +0000 (GMT) Received: from SMTP02.INFOAVE.NET (smtp02.infoave.net [165.166.0.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BA7C43D46 for ; Wed, 19 Jan 2005 23:14:41 +0000 (GMT) (envelope-from brantonc@comporium.net) Received: from [10.0.0.195] ([206.74.30.148]) by SMTP00.InfoAve.Net (PMDF V6.2-X31 #30986) with ESMTP id <01LJSMSB7X9W9DBADU@SMTP00.InfoAve.Net> for freebsd-current@freebsd.org; Wed, 19 Jan 2005 18:14:33 -0500 (EST) Date: Wed, 19 Jan 2005 18:14:28 -0500 From: chris branton To: freebsd-current@freebsd.org Message-id: <41EEE9D4.5090607@comporium.net> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Mailman-Approved-At: Thu, 20 Jan 2005 12:52:06 +0000 Subject: Dummynet with IPv6 freezes the box X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Jan 2005 23:14:44 -0000 Karl, I'm working with FreeBSD 4.10 and hf6to4. Every time I start up hf6to4 I get the message that I need to add INIT6 and or stf 1 to the kernel. IPv6 is active and when I add the interface stf to the kernel it still doesn't work. I have read the man pages but I can not see what I'm doing wrong. Is there something else that has to be done that is not in the man pages. Chris From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 13:18:39 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 031B116A4CE; Thu, 20 Jan 2005 13:18:39 +0000 (GMT) Received: from ss.eunet.cz (ss.eunet.cz [193.85.228.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id E794B43D4C; Thu, 20 Jan 2005 13:18:37 +0000 (GMT) (envelope-from mime@traveller.cz) Received: from localhost.i.cz (ss.eunet.cz. [193.85.228.13]) by ss.eunet.cz (8.13.1/8.13.1) with ESMTP id j0KDIrmi073375; Thu, 20 Jan 2005 14:18:54 +0100 (CET) (envelope-from mime@traveller.cz) From: Michal Mertl To: Emanuel Strobl In-Reply-To: <1106134006.1132.12.camel@genius2.i.cz> References: <1106134006.1132.12.camel@genius2.i.cz> Content-Type: multipart/mixed; boundary="=-k3av6U01ybkct5I0WZMD" Date: Thu, 20 Jan 2005 14:18:30 +0100 Message-Id: <1106227110.716.11.camel@genius2.i.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port cc: akiyama@jp.FreeBSD.org cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org cc: bernd@bwct.de Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 13:18:39 -0000 --=-k3av6U01ybkct5I0WZMD Content-Type: text/plain Content-Transfer-Encoding: 7bit I wrote: > Emanuel Strobl wrote: > > Am Dienstag, 18. Januar 2005 16:17 schrieb Andrew L. Neporada: > > > On Tue, Jan 18, 2005 at 01:06:43PM +0100, Emanuel Strobl wrote: > > > > Dear experts, > > > > > > > > I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working > > > > the other one not (I hate to say it but both are working under win). > > > > > > > > The not working (more expensive) one gets recognized as ucom0 and I have > > > > ucom0, also I can receive signal but not transmit. > > > > > > [skip] > > > > > > Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch > > > http://gate.intercaf.ru/~lesha/6100/pl2303x.patch > > > > > > It can break old (working) PL2303 chip, but it works for me with newer > > > > Thanks a lot, this indeed fixes the revision 3.0 adaptor but unfortunately > > also breakes the 2.02 version :( > > > > Perhaps there's a goog guy out there who can refurbish the uplcom driver with > > this information (akiyama?)? > > > > Thanks a lot, > > I've just recently been looking into this too. I used the mentioned > patch and also linux driver source and have come with the attached > patch. It contains one more change but I don't know if it's correct. It > works for both chips on CURRENT for serial console. It detects if the > chip is rev 3.00 and aplies the patch only for it. > > The author of the patch mentions it isn't binary safe - sometimes the > chip stops working. I planned to test it with binary transfers (ppp) > today, check if it's working and submit it (with some cleanup) for > inclusion in FreeBSD. > > Michal Mertl I tested my patch for binary safety on CURRENT yesterday (dialed with ppp) and didn't notice any problem. I'm attaching my patch again because some recipients didn't probably receive it yesterday. Michal --=-k3av6U01ybkct5I0WZMD Content-Disposition: attachment; filename=uplcom.c.pl2303x.diff Content-Type: text/x-patch; name=uplcom.c.pl2303x.diff; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit Index: uplcom.c =================================================================== RCS file: /home/fcvs/cvs/src/sys/dev/usb/uplcom.c,v retrieving revision 1.25 diff -u -r1.25 uplcom.c --- uplcom.c 6 Jan 2005 01:43:29 -0000 1.25 +++ uplcom.c 20 Jan 2005 13:15:40 -0000 @@ -97,10 +97,13 @@ #include #include +#include + #include #include #include +#include #include #include "usbdevs.h" #include @@ -113,30 +116,34 @@ SYSCTL_INT(_hw_usb_uplcom, OID_AUTO, debug, CTLFLAG_RW, &uplcomdebug, 0, "uplcom debug level"); -#define DPRINTFN(n, x) do { \ +#define DPRINTFN(n, x) do { \ if (uplcomdebug > (n)) \ logprintf x; \ } while (0) #else -#define DPRINTFN(n, x) +#define DPRINTFN(n, x) #endif -#define DPRINTF(x) DPRINTFN(0, x) +#define DPRINTF(x) DPRINTFN(0, x) -#define UPLCOM_MODVER 1 /* module version */ +#define UPLCOM_MODVER 1 /* module version */ #define UPLCOM_CONFIG_INDEX 0 #define UPLCOM_IFACE_INDEX 0 #define UPLCOM_SECOND_IFACE_INDEX 1 #ifndef UPLCOM_INTR_INTERVAL -#define UPLCOM_INTR_INTERVAL 100 /* ms */ +#define UPLCOM_INTR_INTERVAL 100 /* ms */ #endif #define UPLCOM_SET_REQUEST 0x01 #define UPLCOM_SET_CRTSCTS 0x41 -#define RSAQ_STATUS_CTS 0x80 -#define RSAQ_STATUS_DSR 0x02 -#define RSAQ_STATUS_DCD 0x01 +#define UPLCOM_SET_CRTSCTS_2303X 0x61 +#define RSAQ_STATUS_CTS 0x80 +#define RSAQ_STATUS_DSR 0x02 +#define RSAQ_STATUS_DCD 0x01 + +#define CHIPTYPE_PL2303 0 +#define CHIPTYPE_PL2303X 1 struct uplcom_softc { struct ucom_softc sc_ucom; @@ -156,14 +163,15 @@ u_char sc_lsr; /* Local status register */ u_char sc_msr; /* uplcom status register */ + int sc_chiptype; }; /* * These are the maximum number of bytes transferred per frame. * The output buffer size cannot be increased due to the size encoding. */ -#define UPLCOMIBUFSIZE 256 -#define UPLCOMOBUFSIZE 256 +#define UPLCOMIBUFSIZE 256 +#define UPLCOMOBUFSIZE 256 Static usbd_status uplcom_reset(struct uplcom_softc *); Static usbd_status uplcom_set_line_coding(struct uplcom_softc *, @@ -299,6 +307,7 @@ char *devinfo; const char *devname; usbd_status err; + usb_device_descriptor_t *udd; int i; devinfo = malloc(1024, M_USBDEV, M_WAITOK); @@ -374,7 +383,14 @@ sc->sc_isize = UGETW(ed->wMaxPacketSize); } } - + udd = &dev->ddesc; + if (UGETW(udd->bcdDevice) == 0x300) { + DPRINTF(("chiptype 2303X\n")); + sc->sc_chiptype = CHIPTYPE_PL2303X; + } else { + DPRINTF(("chiptype 2303\n")); + sc->sc_chiptype = CHIPTYPE_PL2303; + } if (sc->sc_intr_number == -1) { printf("%s: Could not find interrupt in\n", USBDEVNAME(ucom->sc_dev)); @@ -617,7 +633,10 @@ req.bmRequestType = UT_WRITE_VENDOR_DEVICE; req.bRequest = UPLCOM_SET_REQUEST; USETW(req.wValue, 0); - USETW(req.wIndex, UPLCOM_SET_CRTSCTS); + if (sc->sc_chiptype == CHIPTYPE_PL2303X) + USETW(req.wIndex, UPLCOM_SET_CRTSCTS_2303X); + else + USETW(req.wIndex, UPLCOM_SET_CRTSCTS); USETW(req.wLength, 0); err = usbd_do_request(sc->sc_ucom.sc_udev, &req, 0); @@ -713,6 +732,43 @@ return (0); } +#define DO_REQ(type, reQ, wVal, wInd) do { \ + req.bmRequestType = (type); \ + req.bRequest = (reQ); \ + USETW(req.wValue, (wVal)); \ + USETW(req.wIndex, (wInd)); \ + USETW(req.wLength, 0); \ + err = usbd_do_request(sc->sc_ucom.sc_udev, &req, 0); \ + if (err) { /* XXX - shouldn't happen */ \ + printf("%s: uplcom_initPL2303X_%d: %s\n", \ + USBDEVNAME(sc->sc_ucom.sc_dev), i++, usbd_errstr(err)); \ + return (EIO); \ + } \ + } while (0); + +Static usbd_status +uplcom_initPL2303X(struct uplcom_softc *sc) +{ + usb_device_request_t req; + usbd_status err; + int i = 0; + + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0x40, 0x1, 0x0404, 0); + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0xc0, 0x1, 0x8383, 0); + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0x40, 0x1, 0x0404, 1); + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0xc0, 0x1, 0x8383, 0); + DO_REQ(0x40, 0x1, 0x0000, 1); + DO_REQ(0x40, 0x1, 0x0001, 0); + DO_REQ(0x40, 0x1, 0x0002, 0x44); + return (0); +} + +#undef DO_REQ + Static int uplcom_open(void *addr, int portno) { @@ -743,7 +799,8 @@ return (EIO); } } - + if (sc->sc_chiptype == CHIPTYPE_PL2303X) + return (uplcom_initPL2303X(sc)); return (0); } --=-k3av6U01ybkct5I0WZMD-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 13:41:30 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0412116A4CE for ; Thu, 20 Jan 2005 13:41:30 +0000 (GMT) Received: from electra.nolink.net (electra.nolink.net [195.139.204.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1E0443D41 for ; Thu, 20 Jan 2005 13:41:28 +0000 (GMT) (envelope-from lerik@nolink.net) Received: (qmail 48399 invoked by uid 1000); 20 Jan 2005 13:41:25 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 20 Jan 2005 13:41:25 -0000 Date: Thu, 20 Jan 2005 14:41:25 +0100 (CET) From: Lars Erik Gullerud To: Vladimir Dvorak In-Reply-To: <41EF8FB4.3090406@vdsoft.org> Message-ID: <20050120143901.X47843@electra.nolink.net> References: <41EF8FB4.3090406@vdsoft.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-current@freebsd.org Subject: Re: DNS reverse zone problem? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 13:41:30 -0000 On Thu, 20 Jan 2005, Vladimir Dvorak wrote: > nikolay.nenchev@rbb-sofia.raiffeisen.at wrote: > >> I have problems with reverse zone. I have classless adress from 0-63, so >> I'm wiht mask /26. >> > If you have /26 network, is has no sense to set up reverse zone, because no > nameserver will query it. You can up only classfull (like /24 ) in-addra.arpa > zones. Ask your provider. _Clueful_ providers have been doing classless in-addr.arpa delegation for years. http://www.ietf.org/rfc/rfc2317.txt (there are other ways too). /leg From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 14:13:09 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E05E16A4CE for ; Thu, 20 Jan 2005 14:13:08 +0000 (GMT) Received: from mail.vdsoft.org (poseidon.vdsoft.org [193.85.147.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1558643D46 for ; Thu, 20 Jan 2005 14:13:08 +0000 (GMT) (envelope-from dvorakv@vdsoft.org) Received: from [10.0.0.132] (unknown [10.0.0.132]) by mail.vdsoft.org (Postfix) with ESMTP id 3174847E01C; Thu, 20 Jan 2005 15:13:03 +0100 (CET) Message-ID: <41EFBCC5.9060503@vdsoft.org> Date: Thu, 20 Jan 2005 15:14:29 +0100 From: Vladimir Dvorak User-Agent: Debian Thunderbird 1.0 (X11/20050116) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lars Erik Gullerud References: <41EF8FB4.3090406@vdsoft.org> <20050120143901.X47843@electra.nolink.net> In-Reply-To: <20050120143901.X47843@electra.nolink.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: DNS reverse zone problem? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 14:13:09 -0000 Lars Erik Gullerud wrote: > On Thu, 20 Jan 2005, Vladimir Dvorak wrote: > >> nikolay.nenchev@rbb-sofia.raiffeisen.at wrote: >> >>> I have problems with reverse zone. I have classless adress from >>> 0-63, so I'm wiht mask /26. >>> >> If you have /26 network, is has no sense to set up reverse zone, >> because no nameserver will query it. You can up only classfull (like >> /24 ) in-addra.arpa zones. Ask your provider. > > > _Clueful_ providers have been doing classless in-addr.arpa delegation > for years. > > http://www.ietf.org/rfc/rfc2317.txt (there are other ways too). Thank you for your notice guys, sorry for my mistake. V. From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 14:29:01 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B07016A4CE for ; Thu, 20 Jan 2005 14:29:01 +0000 (GMT) Received: from relay.bestcom.ru (relay.bestcom.ru [217.72.144.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81D5E43D5C for ; Thu, 20 Jan 2005 14:29:00 +0000 (GMT) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (root@cell.sick.ru [217.72.144.68]) by relay.bestcom.ru (8.13.1/8.12.9) with ESMTP id j0KESw2e052640 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 20 Jan 2005 17:28:59 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.11/8.12.8) with ESMTP id j0KESv3e019243 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Jan 2005 17:28:58 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id j0KESuOK019242; Thu, 20 Jan 2005 17:28:56 +0300 (MSK) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@freebsd.org using -f Date: Thu, 20 Jan 2005 17:28:56 +0300 From: Gleb Smirnoff To: freebsd@newmillennium.net.au Message-ID: <20050120142856.GA19120@cell.sick.ru> References: <004501c4fe00$76180fc0$0201000a@riker> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <004501c4fe00$76180fc0$0201000a@riker> User-Agent: Mutt/1.5.6i X-Virus-Scanned: ClamAV version devel-20050119, clamav-milter version 0.80ff on relay.bestcom.ru X-Virus-Status: Clean cc: current@freebsd.org Subject: Re: IPFW problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 14:29:01 -0000 On Wed, Jan 19, 2005 at 07:25:40PM +1100, freebsd@newmillennium.net.au wrote: f> I have recently (the last week or so, but possible longer as I had f> updated the system prior to going on a 3 week holiday) been having some f> problems with IPFW under -CURRENT. f> I am running: f> bash-2.05b$ uname -a f> FreeBSD picard.newmillennium.net.au 6.0-CURRENT FreeBSD 6.0-CURRENT #38: f> Sun Jan 16 18:27:30 EST 2005 f> root@picard.newmillennium.net.au:/usr/obj/usr/src/sys/PICARD i386 Do I understand correct, that previous snapshot of CURRENT didn't have this problem? Does backing out these [1,2] commits help? [1] http://lists.freebsd.org/pipermail/cvs-src/2005-January/038564.html [2] http://lists.freebsd.org/pipermail/cvs-src/2005-January/038701.html -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 17:51:34 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3837C16A4CE for ; Thu, 20 Jan 2005 17:51:34 +0000 (GMT) Received: from omoikane.mb.skyweb.ca (64-42-246-34.mb.skyweb.ca [64.42.246.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80C3043D2D for ; Thu, 20 Jan 2005 17:51:33 +0000 (GMT) (envelope-from mark@skyweb.ca) Received: by omoikane.mb.skyweb.ca (Postfix, from userid 1001) id 4A42661DA8; Thu, 20 Jan 2005 11:51:36 -0600 (CST) From: Mark Johnston To: current@freebsd.org, freebsd-cvs-summary@lists.enderunix.org Date: Thu, 20 Jan 2005 11:51:35 -0600 User-Agent: KMail/1.6.1 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200501201151.35683.mjohnston@skyweb.ca> Subject: cvs-src summary for January 10-17 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 17:51:34 -0000 Sorry that this is late and a little sparse; I've been way too busy lately. Mark FreeBSD cvs-src summary for 2005-01-11 to 2005-01-17 ++++++++++++++++++++++++++++++++++++++++++++++++++++ This is a regular weekly summary of FreeBSD's cutting-edge development. It is intended to help the FreeBSD community keep up with the fast-paced work going on in FreeBSD-CURRENT by distilling the deluge of data from the CVS mailing list into a (hopefully) easy-to-read newsletter. You can get old summaries, and an HTML version of this one, at http://www.xl0.org/FreeBSD/. An RSS feed is available from http://excel.xl0.org/cgi-bin/rss.py. If you would like to receive the summary without subscribing to current@, send a blank message to freebsd-cvs-summary-subscribe@lists.enderunix.org; thanks to Omer Faruk Sen and EnderUNIX for hosting this list. Please send any comments to Mark Johnston (mark at xl0.org). ============ New Features ============ GEOM Shared Secret class added ------------------------------ Pawel Jakub Dawidek (pjd) committed a new GEOM class, named SHSEC, that configures a group of GEOM devices with a shared secret. If any of the providers is missing, no useful data can be gotten from any of the others. This work was sponsored by Wheel Sp. z o.o. (http://www.wheel.pl). http://www.freebsd.org/cgi/mid.cgi?200501111806.j0BI6iv3095929 IBM/Adaptec ServeRAID driver merged to 4.x ------------------------------------------ Scott Long (scottl) MFC'ed to 4.x the ips[1] driver, which supports the IBM/Adaptec ServeRAID series of SCSI controllers. This supports the ServeRAID 3H as well as most 4, 5, and 6 series cards. [1] http://www.freebsd.org/cgi/man.cgi?query=ips&apropos=0&sektion=4&manpath=FreeBSD+6.0-current&format=html http://www.freebsd.org/cgi/mid.cgi?200501130046.j0D0keNs023032 =============== Notable Changes =============== Abbreviations of ipfw options deprecated ---------------------------------------- Brooks Davis (brooks) changed the ipfw[1] command-line utility to remove support for abbreviating command-line options, which was causing major maintenance headaches in the code. Old abbreviations are still accepted, but warnings will be produced. Brooks may add a few specific abbreviations based on user feedback. [1] http://www.freebsd.org/cgi/man.cgi?query=ipfw&apropos=0&sektion=8&manpath=FreeBSD+6.0-current&format=html http://www.freebsd.org/cgi/mid.cgi?200501150146.j0F1kfXf026648 ================= Discussion Topics ================= Setuid checks for various kinds of filesystems ---------------------------------------------- Gleb Smirnoff (glebius) changed the security checks to bypass setuid checks on filesystems mounted with the noexec (no executables allowed) option. This spurred a discussion about what should and shouldn't be checked, covering noexec as well as nosuid filesystems and remotely-mounted ones. In the end, it was suggested that special provisions for excluding given filesystems should be added to the configuration. http://www.freebsd.org/cgi/mid.cgi?200501131507.j0DF7ZAr081525 =================== Important Bug Fixes =================== ACL bypass on the root filesystem corrected ------------------------------------------- Pawel Jakub Dawidek (pjd) fixed a bug that would cause ACLs on the root filesystem, when set with tunefs[1] to be ignored on system boot. This was a result of the way mount[2] was called. With the change, it is no longer possible to remove ACLs configured with tunefs by using mount -a or mount -o noacls. [1] http://www.freebsd.org/cgi/man.cgi?query=tunefs&apropos=0&sektion=8&manpath=FreeBSD+6.0-current&format=html [2] http://www.freebsd.org/cgi/man.cgi?query=mount&apropos=0&sektion=8&manpath=FreeBSD+6.0-current&format=html Reported by: Lech Lorens http://www.freebsd.org/cgi/mid.cgi?200501151709.j0FH9rL5084363 =============== Other Bug Fixes =============== Paul Saab (ps) fixed a possible crash in the TCP Selective ACK code. The bug was due to a GCC optimization issue. http://www.freebsd.org/cgi/mid.cgi?200501122140.j0CLepDJ011394 Bill Paul (wpaul) fixed a possible panic in the NDIS support code when the INVARIANTS kernel option is enabled. http://www.freebsd.org/cgi/mid.cgi?200501142239.j0EMdidD013684 Alan Cox (alc) fixed a VM race condition that could result in a panic. This bug was uncovered by Peter Holm's stress testing[1] of the kernel. [1] http://www.holm.cc/stress/ Reported by: Peter Holm http://www.freebsd.org/cgi/mid.cgi?200501152112.j0FLClQx099793 From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 18:03:29 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E7F9216A4CE for ; Thu, 20 Jan 2005 18:03:29 +0000 (GMT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 0595843D54 for ; Thu, 20 Jan 2005 18:03:29 +0000 (GMT) (envelope-from emanuel.strobl@gmx.net) Received: (qmail invoked by alias); 20 Jan 2005 18:03:27 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp022) with SMTP; 20 Jan 2005 19:03:27 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-current@freebsd.org Date: Thu, 20 Jan 2005 19:03:19 +0100 User-Agent: KMail/1.7.2 References: <1106134006.1132.12.camel@genius2.i.cz> <1106227110.716.11.camel@genius2.i.cz> In-Reply-To: <1106227110.716.11.camel@genius2.i.cz> X-Birthday: 10/06/72 X-CelPhone: +49 173 9967781 X-Tel: +49 89 18947781 X-Country: Germany X-Address: Munich, 80686 X-OS: FreeBSD MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1144706.gKzGBK3ITW"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501201903.24020.emanuel.strobl@gmx.net> X-Y-GMX-Trusted: 0 cc: Michal Mertl cc: freebsd-stable@freebsd.org cc: bernd@bwct.de Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 18:03:30 -0000 --nextPart1144706.gKzGBK3ITW Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Donnerstag, 20. Januar 2005 14:18 schrieb Michal Mertl: > > works for both chips on CURRENT for serial console. It detects if the > > chip is rev 3.00 and aplies the patch only for it. > > > > The author of the patch mentions it isn't binary safe - sometimes the > > chip stops working. I planned to test it with binary transfers (ppp) > > today, check if it's working and submit it (with some cleanup) for > > inclusion in FreeBSD. > > > > Michal Mertl > > I tested my patch for binary safety on CURRENT yesterday (dialed with > ppp) and didn't notice any problem. Thanks a lot, unfortunately my notebook died (the display mechanic) so I=20 cannot test it at the moment (my workstation box is too far away from my=20 servers with serial stuff). But I think this should be commited, otherwiese more people like me go=20 shopping, testing the adaptor, seeing that it gets recognized as Prolific=20 2303, purchasing some of them and then at home find out that there is also = a=20 unsupported version of the 2303 :( I'm sure someone (bernd?) will commit it for you. Thanks a lot for your work, I'll test it asap and let you know if I find=20 anything unusual. Best regards, =2DHarry > > I'm attaching my patch again because some recipients didn't probably > receive it yesterday. > > Michal --nextPart1144706.gKzGBK3ITW Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB7/JrBylq0S4AzzwRAkbZAJ9Om883mEQNCCbkKw4QwMoF/A/7+wCdH/K+ sYwjb9wGiN1x6F5bLahnPSI= =9Pcs -----END PGP SIGNATURE----- --nextPart1144706.gKzGBK3ITW-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 19:06:03 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6468816A4CE for ; Thu, 20 Jan 2005 19:06:03 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF3ED43D1F for ; Thu, 20 Jan 2005 19:06:02 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j0KJ3Dax029371; Thu, 20 Jan 2005 12:03:18 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 20 Jan 2005 12:04:23 -0700 (MST) Message-Id: <20050120.120423.94248425.imp@bsdimp.com> To: mcsi@mcsi.pp.ru From: "M. Warner Losh" In-Reply-To: <41EEAD95.5080706@mcsi.pp.ru> References: <41EEAD95.5080706@mcsi.pp.ru> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: current@FreeBSD.org Subject: Re: kernel panic (ACPI/fdc/sysctl) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 19:06:03 -0000 In message: <41EEAD95.5080706@mcsi.pp.ru> Maxim Maximov writes: : fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 : on acpi0 : device_attach: fdc0 attach returned 6 I think that I've fixed this. Please try again. Sorry for the hassle. Warner From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 19:08:27 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 33AF816A4CE for ; Thu, 20 Jan 2005 19:08:27 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id A492B43D75 for ; Thu, 20 Jan 2005 19:08:26 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from error404.nls.net (ketrien@error404.nls.net [216.144.36.24]) by error404.nls.net (8.13.1/8.13.1) with ESMTP id j0KJ9jmd014403 for ; Thu, 20 Jan 2005 14:09:45 -0500 (EST) (envelope-from ketrien@error404.nls.net) Date: Thu, 20 Jan 2005 14:09:45 -0500 (EST) From: "Ketrien I. Saihr-Kenchedra" X-X-Sender: ketrien@bahre.achedra.org To: current@freebsd.org Message-ID: <20050120140300.F1832@bahre.achedra.org> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-2071622897-1106248185=:1832" X-Virus-Scanned: ClamAV 0.80/671/Mon Jan 17 09:16:31 2005 clamav-milter version 0.80j on bahre.achedra.org X-Virus-Status: Clean Subject: Memory modified after free - Jan20 -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 19:08:27 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-2071622897-1106248185=:1832 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Screen transcription attached. In a nutshell; fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 device_attach: fdc0 returned 6 sio0: <16550A-compatible COM port> port0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A Memory modified after free 0xc1cde200(252) val=0 @ 0xc1cde228 panic: Most recently used by none System was fine with Jan16 srcs, fdc returning 6 is new. Looks like a uma problem to me, but odd enough that I'm honestly not sure. Need ips(4) for dumpdev, so no dump again. (Argh.) -Ketrien I. Saihr-Kenchedra Yeah, except starbucks sucks for some reason you can getevery color of coffee except black --0-2071622897-1106248185=:1832 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="panic.Jan202004" Content-Transfer-Encoding: BASE64 Content-ID: <20050120140945.K1832@bahre.achedra.org> Content-Description: Content-Disposition: attachment; filename="panic.Jan202004" ZmRjMDogPGZsb3BweSBkcml2ZSBjb250cm9sbGVyPiBwb3J0IDB4M2Y3LDB4 M2YwLTB4M2Y1IGlycSA2IGRycSAyIG9uIGFjcGkwDQpkZXZpY2VfYXR0YWNo OiBmZGMwIHJldHVybmVkIDYNCnNpbzA6IDwxNjU1MEEtY29tcGF0aWJsZSBD T00gcG9ydD4gcG9ydDB4M2Y4LTB4M2ZmIGlycSA0IGZsYWdzIDB4MTAgb24g YWNwaTANCnNpbzA6IHR5cGUgMTY1NTBBDQpNZW1vcnkgbW9kaWZpZWQgYWZ0 ZXIgZnJlZSAweGMxY2RlMjAwKDI1MikgdmFsPTAgQCAweGMxY2RlMjI4DQpw YW5pYzogTW9zdCByZWNlbnRseSB1c2VkIGJ5IG5vbmUNCg0KDQpjcHVpZCA9 IDANCktEQjogZW50ZXI6IHBhbmljDQpbdGhyZWFkIHBpZDAgdGlkIDAgXQ0K U3RvcHBlZCBhdCBrZGJfZW50ZXIrMHgzMDogbGVhdmUNCmRiPg0KZGI+IHRy YWNlDQpUcmFjaW5nIHBpZCAwIHRpZCAwIHRkIDB4YzA3NGRlNDANCmtkYl9l bnRlcihjMDZmMDJhOCwwLGMwNzA0NjU0LGMwYzIwOTY0LGMwNzRkZTQwKSBh dCBrZGJfZW50ZXIrMHgzMA0KcGFuaWMoYzA3MDQ2NTQsYzA2ZTQ0OWMsZmMs MCxjMWNkZTIyOCkgYXQgcGFuaWMrMHgxNGUNCm10cmFzaF9jdG9yKGMxY2Rl MjAwLDEwMCwwLDEwMixjMWNkZTIwMCkgYXQgbXRyYXNoX2N0b3IrMHg2NQ0K dW1hX3phbGxvY19hcmcoYzEwNTI4NDAsMCwxMDIsYzEwNjRiNDAsYzFjZjI3 MzApIGF0IHVtYV96YWxsb2NfYXJnKzB4MWM4DQptYWxsb2MoZDgsYzA3Mjc3 NjAsMTAyLGMwYzIwYTA0LGMwNTBiNDA5KSBhdCBtYWxsb2MrMHhkNg0KcHN0 YXRzX2FsbG9jKGMxY2YxYzM4LGMwNmVmOTYwLDAsMjAsNikgYXQgcHN0YXRz X2FsbG9jKzB4MjINCnByb2NfaW5pdChjMWNmMWJkMCwxZjgsMTAzLDEwMyxj MWNmMTAwMCkgYXQgcHJvY19pbml0KzB4NjkNCnNsYWJfemFsbG9jKGMxMDNl MTYwLDEwMyxjMDY1ZDhhZixjMTAzZTE2MCxjMWNmMGZjNCkgYXQgc2xhYl96 YWxsb2MrMHgyYzANCnVtYV96b25lX3NsYWIoYzEwM2UxNjAsMyxjMDUwOTc4 YSxjMDdhYjEwMCwyKSBhdCB1bWFfem9uZV9zbGFiKzB4MTE3DQp1bWFfemFs bG9jX2J1Y2tldChjMTAzZTE2MCwzLGMwNzA0MDE3LDc2ZCxjMDUwOTk5ZCkg YXQgdW1hX3phbGxvY19idWNrZXQrMHgxNmYNCnVtYV96YWxsb2NfYXJnKGMx MDNlMTYwLDAsMixjMDZmM2EwZiw0ZWUpIGF0IHVtYV96YWxsb2NfYXJnKzB4 MzZkDQpmb3JrMShjMDc0ZGU0MCw2MDAzNCwwLGMwYzIwYjFjLGMxY2M4ZGRh KSBhdCBmb3JrMSsweDE0Mw0Ka3RocmVhZF9jcmVhdGUoYzA0ZmMzOTAsYzFj YzhkODAsYzBjMjBiNGMsNjAwMDAsMCkgYXQga3RocmVhZF9jcmVhdGUrMHg0 OA0KaXRocmVhZF9jcmVhdGUoYzBjMjBiODAsMCwxLDAsMCkgYXQgaXRocmVh ZF9jcmVhdGUrMHhkNA0Kc3dpX2FkZChjMDc0ZTYyNCxjMDcwN2RmNSxjMDY4 N2I4MCwwLDApIGF0IHN3aV9hZGQrMHg4Mw0Kc2lvYXR0YWNoKGMxY2JlMzgw LDAsMCxjMGMyMGMxYyxjMDUyZDA3YSkgYXQgc2lvYXR0YWNoKzB4NDkxDQpz aW9faXNhX2F0dGFjaChjMWNiZTM4MCxjMWM2OTA0YyxjMDcyMmM5NCxjMWNi ZTM4MCxjMWNiZTM4MCkgYXQgc2lvX2lzYV9hdHRhY2grMHgyMQ0KZGV2aWNl X2F0dGFjaChjMWNiZTM4MGMxY2JlMzgwLGMwNmYxZDFhLDhkYSxjMGMyMGM1 NCkgYXQgZGV2aWNlX2F0dGFjaCsweDZhDQpkZXZpY2VfcHJvYmVfYW5kX2F0 dGFjaChjMWNiZTM4MCxlZTliLGMwYzIwY2FjLGMwODgzMGY0LGMxYzU3NjAw KSBhdCBkZXZpY2VfcHJvYmVfYW5kX2F0dGFjaCsweDExMQ0KYnVzX2dlbmVy aWNfYXR0YWNoKGMxYzU3NjAwLGVlOWIsZWU5YixjMWNiN2JjOCxlZTliKSBh dCBidXNfZ2VuZXJpY19hdHRhY2grMHgyOA0KYWNwaV9hdHRhY2goYzFjNTc2 MDAsYzFjOTIwNGMsYzA3MjJjOTQsYzFjNTc2MDAsYzFjNTc2MDApIGF0IGFj cGlfYXR0YWNoKzB4OTA0DQpkZXZpY2VfYXR0YWNoKGMxYzU3NjAwMCxjMWM1 NzYwMCxjMDZmMWQxYSw4ZGEsYzBjMjBkMDQpIGF0IGRldmljZV9hdHRhY2gr MHg2YQ0KZGV2aWNlX3Byb2JlX2FuZF9hdHRhY2goYzFjNTc2MDAsYzFjNTc3 ODAsYzBjMjBkMTQsYzA2YWUxOGEsYzFjNTc3ODApIGF0IGRldmljZV9wcm9i ZV9hbmRfYXR0YWNoKzB4MTExDQpidXNfZ2VuZXJpY19hdHRhY2goYzFjNTc3 ODAsYzFjNTc3ODAsYzBjMjBkMzQsYzA1MmQwN2EsYzFjNTc3ODApIGF0IGJ1 c19nZW5lcmljX2F0dGFjaCsweDI4DQpuZXh1c19hdHRhY2goYzFjNTc3ODAs YzFjODM4NGMsYzA3MjJjOTQsYzFjNTc3ODAsYzFjNTc3ODApIGF0IG5leHVz X2F0dGFjaCsweDFhDQpkZXZpY2VfYXR0YWNoKGMxYzU3NzgwLGMxYzU3Nzgw LGMwNmYxZDFhLDhkYSxjMDczOWEzMCkgYXQgZGV2aWNlX2F0dGFjaCsweDZh DQpkZXZpY2VfcHJvYmVfYW5kX2F0dGFjaChjMWM1Nzc4MCxjMWJjOTdhYyxj MGMyMGQ4MCxjMDY5OWFlOSxjMWM1N2QwMCkgYXQgZGV2aWNlX3Byb2JlX2Fu ZF9hdHRhY2grMHgxMTENCnJvb3RfYnVzX2NvbmZpZ3VyZShjMWM1N2QwMCxj MDcwYjMxZiwwLGMwYzIwZDk4LGMwNGU0MGY1KSBhdCByb290X2J1c19jb25m aWd1cmUrMHgyOA0KY29uZmlndXJlKDAsYzFlMDAwLGMxZWMwMCxjMWUwMDAs MCkgYXQgY29uZmlndXJlKzB4MjkNCm1pX3N0YXJ0dXAoKSBhdCBtaV9zdGFy dHVwKzB4YjUNCmJlZ2luKCkgYXQgYmVnaW4rMHgyYw0KZGI+DQoNCg== --0-2071622897-1106248185=:1832-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 19:21:13 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DE2A16A4CE for ; Thu, 20 Jan 2005 19:21:13 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1426B43D4C for ; Thu, 20 Jan 2005 19:21:13 +0000 (GMT) (envelope-from chrcoluk@gmail.com) Received: by rproxy.gmail.com with SMTP id b11so21685rne for ; Thu, 20 Jan 2005 11:21:12 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=Vyco7VWYITxNEETuo77QaN1BxhpdhtuSBpizYykfHMDjB6gj2ZH6XY24sx4zl/ujVS8TnP/rUYxADN6e8R0lvewgFMn6kOsYGQC8BnU1ECNfnQo4aw3Vh5rrvq9mjQqDB1QjTmegl+Hj6FLXo5S4VinaC8zE7Mg6iK1drb+dEyw= Received: by 10.38.157.1 with SMTP id f1mr114986rne; Thu, 20 Jan 2005 11:21:12 -0800 (PST) Received: by 10.39.1.45 with HTTP; Thu, 20 Jan 2005 11:21:12 -0800 (PST) Message-ID: <3aaaa3a050120112197b3555@mail.gmail.com> Date: Thu, 20 Jan 2005 19:21:12 +0000 From: Chris To: Gleb Smirnoff In-Reply-To: <20050120142856.GA19120@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <004501c4fe00$76180fc0$0201000a@riker> <20050120142856.GA19120@cell.sick.ru> cc: freebsd@newmillennium.net.au cc: current@freebsd.org Subject: Re: IPFW problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Chris List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 19:21:13 -0000 I have suffered from this bug on occasions, I do use skiptos but none past my catch all rule at the end which is rule 65000 deny all from any to any Chris On Thu, 20 Jan 2005 17:28:56 +0300, Gleb Smirnoff wrote: > On Wed, Jan 19, 2005 at 07:25:40PM +1100, freebsd@newmillennium.net.au wrote: > f> I have recently (the last week or so, but possible longer as I had > f> updated the system prior to going on a 3 week holiday) been having some > f> problems with IPFW under -CURRENT. > f> I am running: > f> bash-2.05b$ uname -a > f> FreeBSD picard.newmillennium.net.au 6.0-CURRENT FreeBSD 6.0-CURRENT #38: > f> Sun Jan 16 18:27:30 EST 2005 > f> root@picard.newmillennium.net.au:/usr/obj/usr/src/sys/PICARD i386 > > Do I understand correct, that previous snapshot of CURRENT didn't have this > problem? Does backing out these [1,2] commits help? > > [1] http://lists.freebsd.org/pipermail/cvs-src/2005-January/038564.html > [2] http://lists.freebsd.org/pipermail/cvs-src/2005-January/038701.html > > -- > Totus tuus, Glebius. > GLEBIUS-RIPN GLEB-RIPE > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 19:29:31 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2F0416A4CE; Thu, 20 Jan 2005 19:29:31 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 357FF43D31; Thu, 20 Jan 2005 19:29:31 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.12] (g4.samsco.home [192.168.254.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id j0KJXuMH036439; Thu, 20 Jan 2005 12:33:56 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41F00697.7010000@freebsd.org> Date: Thu, 20 Jan 2005 12:29:27 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Ketrien I. Saihr-Kenchedra" References: <20050120140300.F1832@bahre.achedra.org> In-Reply-To: <20050120140300.F1832@bahre.achedra.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: current@freebsd.org cc: Bosko Milekic Subject: Re: Memory modified after free - Jan20 -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 19:29:31 -0000 Ketrien I. Saihr-Kenchedra wrote: > Screen transcription attached. In a nutshell; > > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 > device_attach: fdc0 returned 6 > sio0: <16550A-compatible COM port> port0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio0: type 16550A > Memory modified after free 0xc1cde200(252) val=0 @ 0xc1cde228 > panic: Most recently used by none > > System was fine with Jan16 srcs, fdc returning 6 is new. Looks like a uma > problem to me, but odd enough that I'm honestly not sure. Need ips(4) for > dumpdev, so no dump again. (Argh.) > I'm seeing this quite often too. I'm hoping that Bosko will make his memguard changes available soon as I'm sure it could quickly be tracked down with them. Scott From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 19:46:28 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D99A16A4CE; Thu, 20 Jan 2005 19:46:28 +0000 (GMT) Received: from smtp1.server.rpi.edu (smtp1.server.rpi.edu [128.113.2.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5D3F43D1F; Thu, 20 Jan 2005 19:46:27 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp1.server.rpi.edu (8.13.0/8.13.0) with ESMTP id j0KJkPiQ017909; Thu, 20 Jan 2005 14:46:25 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: <41F00697.7010000@freebsd.org> References: <20050120140300.F1832@bahre.achedra.org> <41F00697.7010000@freebsd.org> Date: Thu, 20 Jan 2005 14:46:24 -0500 To: Scott Long , "Ketrien I. Saihr-Kenchedra" From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) cc: current@freebsd.org Subject: Re: Memory modified after free - Jan20 -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 19:46:28 -0000 At 12:29 PM -0700 1/20/05, Scott Long wrote: >Ketrien I. Saihr-Kenchedra wrote: > >>Screen transcription attached. In a nutshell; >> >>fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 >>device_attach: fdc0 returned 6 >>sio0: <16550A-compatible COM port> port0x3f8-0x3ff irq 4 flags 0x10 on acpi0 >>sio0: type 16550A >>Memory modified after free 0xc1cde200(252) val=0 @ 0xc1cde228 >>panic: Most recently used by none >> >>System was fine with Jan16 srcs, fdc returning 6 is new. Looks >>like a uma problem to me, but odd enough that I'm honestly not >>sure. Need ips(4) for dumpdev, so no dump again. (Argh.) >> > >I'm seeing this quite often too. I'm hoping that Bosko will make >his memguard changes available soon as I'm sure it could quickly >be tracked down with them. Ugh. I see this too, immediately at bootup. The system can't even make it into single-user mode. Right now I can't get a dump of it, since doadump() complaints that it doesn't know my dump device. How do I set the dump-device from the boot-loader? Will a dump of this be of any help to someone, or does the panic happen too late to have any useful information? -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 20:39:53 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0579F16A4CE for ; Thu, 20 Jan 2005 20:39:53 +0000 (GMT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3944443D1D for ; Thu, 20 Jan 2005 20:39:52 +0000 (GMT) (envelope-from j@uriah.heep.sax.de) Received: from sax.sax.de (localhost [127.0.0.1]) by sax.sax.de (8.12.10/8.12.10) with ESMTP id j0KKdpYu052710 for ; Thu, 20 Jan 2005 21:39:51 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.12.10/8.12.10/Submit) with UUCP id j0KKdpk5052709 for current@freebsd.org; Thu, 20 Jan 2005 21:39:51 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: from uriah.heep.sax.de (localhost [127.0.0.1]) by uriah.heep.sax.de (8.13.1/8.13.1) with ESMTP id j0KKcZv6033025 for ; Thu, 20 Jan 2005 21:38:35 +0100 (MET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.13.1/8.13.1/Submit) id j0KKcZ9K033024 for current@freebsd.org; Thu, 20 Jan 2005 21:38:35 +0100 (MET) (envelope-from j) Resent-Message-Id: <200501202038.j0KKcZ9K033024@uriah.heep.sax.de> Date: Thu, 20 Jan 2005 20:23:24 +0100 From: Joerg Wunsch To: current@freebsd.org Message-ID: <20050120192324.GA30862@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-GPG-Fingerprint: 5E84 F980 C3CA FD4B B584 1070 F48C A81B 69A8 5873 Resent-From: j@uriah.heep.sax.de Resent-Date: Thu, 20 Jan 2005 21:38:34 +0100 Resent-To: current@freebsd.org X-Spam-Status: No, score=-2.6 required=7.5 tests=BAYES_00 autolearn=ham version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on uriah.heep.sax.de cc: bde@freebsd.org Subject: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joerg Wunsch List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 20:39:53 -0000 While analyzing an implementation of strtol() for the AVR microcontroller (as part of the opensource C library for it), I noticed a few violations of the C standard in FreeBSD's implementation. I didn't check, but I'd expect similar issues to apply to related functions. While the standard explicitly states that empty (or whitespace-only) input strings cause an empty subject sequence, which will in turn cause no conversion to be performed, single signs ("+" or "-") would contain a non-empty subject sequence, so a conversion has to take place. FreeBSD erroneously returns EINVAL in that case. As EINVAL is not covered by the standard at all, of course this is debatable, but I clearly read the standard the way that "" or " " are not convertible, while "+" and "-" are. Second (and much more of an issue), sequences consisting solely of a "0x" (with any permutations of leading white space and/or sign) are *always* convertible, as the leading 0 is always a valid number, so conversion only has to stop at the "x". This is a clear bug in my opinion. Btw., what's the position of the C standard for errno values that are not covered by the C standard itself? I see SUSPv2 supports the notion of EINVAL, but it's not clear to me whether the C standard would allow non-standard extension for functions where the standard describes the possible errno changes. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 20:47:25 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2F3616A4CE; Thu, 20 Jan 2005 20:47:25 +0000 (GMT) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77D7E43D39; Thu, 20 Jan 2005 20:47:25 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.13.0/8.13.0) with ESMTP id j0KKlLau003249; Thu, 20 Jan 2005 15:47:23 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: References: <20050120140300.F1832@bahre.achedra.org> <41F00697.7010000@freebsd.org> Date: Thu, 20 Jan 2005 15:47:20 -0500 To: Scott Long , "Ketrien I. Saihr-Kenchedra" From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) cc: current@freebsd.org Subject: Re: Memory modified after free - Jan20 -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 20:47:25 -0000 At 2:46 PM -0500 1/20/05, Garance A Drosihn wrote: >At 12:29 PM -0700 1/20/05, Scott Long wrote: >>Ketrien I. Saihr-Kenchedra wrote: >> >>>Screen transcription attached. In a nutshell; >>> >>> Memory modified after free 0xc1cde200(252) val=0 @ 0xc1cde228 >>> panic: Most recently used by none >> >>I'm seeing this quite often too. > >Ugh. I see this too, immediately at bootup. The system can't >even make it into single-user mode. Well, it happened that I was in the middle of doing another buildworld when I wrote my previous message. I had just done a cleanworld, another 'cvsup', and then rebuilt everything. This time the new system had no trouble booting up, and I had no trouble doing the installworld. I've been running it for about a half-hour now, and haven't seen any panics. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 20:55:04 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D1BC16A4CE; Thu, 20 Jan 2005 20:55:04 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0EEE43D45; Thu, 20 Jan 2005 20:55:02 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id j0KKt1Bg069360; Thu, 20 Jan 2005 23:55:01 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id j0KKt1jq069359; Thu, 20 Jan 2005 23:55:01 +0300 (MSK) (envelope-from ache) Date: Thu, 20 Jan 2005 23:55:01 +0300 From: Andrey Chernov To: Joerg Wunsch Message-ID: <20050120205501.GA69123@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Joerg Wunsch , current@FreeBSD.ORG, bde@FreeBSD.ORG References: <20050120192324.GA30862@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050120192324.GA30862@uriah.heep.sax.de> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.8; VDF: 6.29.0.71; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [0.0.0.0]); Thu, 20 Jan 2005 23:55:01 +0300 (MSK) cc: current@FreeBSD.ORG cc: bde@FreeBSD.ORG Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 20:55:04 -0000 On Thu, Jan 20, 2005 at 08:23:24PM +0100, Joerg Wunsch wrote: > While the standard explicitly states that empty (or whitespace-only) > input strings cause an empty subject sequence, which will in turn > cause no conversion to be performed, single signs ("+" or "-") would > contain a non-empty subject sequence, so a conversion has to take > place. FreeBSD erroneously returns EINVAL in that case. As EINVAL is Just what is eye-catching: +- can't be compared to whitespace at all. Whitespace is not subject sequence (2) but initial sequence (1) according to POSIX. Moreover, POSIX clearly allows EINVAL for strtol(): "If no conversion could be performed, 0 shall be returned and errno may be set to [EINVAL]" Reading POSIX will really help you with this issue. -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 21:20:07 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93B7C16A4CE; Thu, 20 Jan 2005 21:20:07 +0000 (GMT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id C43FE43D53; Thu, 20 Jan 2005 21:20:06 +0000 (GMT) (envelope-from j@uriah.heep.sax.de) Received: from sax.sax.de (localhost [127.0.0.1]) by sax.sax.de (8.12.10/8.12.10) with ESMTP id j0KLK5Yu054488; Thu, 20 Jan 2005 22:20:05 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.12.10/8.12.10/Submit) with UUCP id j0KLK50f054487; Thu, 20 Jan 2005 22:20:05 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: from uriah.heep.sax.de (localhost [127.0.0.1]) by uriah.heep.sax.de (8.13.1/8.13.1) with ESMTP id j0KLEnio034096; Thu, 20 Jan 2005 22:14:49 +0100 (MET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.13.1/8.13.1/Submit) id j0KLEnXg034095; Thu, 20 Jan 2005 22:14:49 +0100 (MET) (envelope-from j) Date: Thu, 20 Jan 2005 22:14:49 +0100 From: Joerg Wunsch To: current@FreeBSD.ORG Message-ID: <20050120211449.GC30862@uriah.heep.sax.de> References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20050120205501.GA69123@nagual.pp.ru> User-Agent: Mutt/1.4.2.1i X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-GPG-Fingerprint: 5E84 F980 C3CA FD4B B584 1070 F48C A81B 69A8 5873 X-Spam-Status: No, score=-2.6 required=7.5 tests=BAYES_00 autolearn=ham version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on uriah.heep.sax.de cc: Andrey Chernov cc: bde@FreeBSD.ORG Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joerg Wunsch List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 21:20:07 -0000 As Andrey Chernov wrote: > > While the standard explicitly states that empty (or > > whitespace-only) input strings cause an empty subject sequence, > > which will in turn cause no conversion to be performed, single > > signs ("+" or "-") would contain a non-empty subject sequence, so > > a conversion has to take place. FreeBSD erroneously returns > > EINVAL in that case. As EINVAL is > Just what is eye-catching: > +- can't be compared to whitespace at all. Whitespace is not subject > sequence (2) but initial sequence (1) according to POSIX. That's correct, and doesn't contradict to what I wrote. It only means there's no difference in " " vs. "". > Moreover, POSIX clearly allows EINVAL for strtol(): > "If no conversion could be performed, 0 shall be returned and errno > may be set to [EINVAL]" Yes, I know. Anyway, how could POSIX (or the Single UNIX Specification, for that matter) possibly contradict to the C standard? In reading the C standard, I get the impression that for functions where the standard describes their possible modifications to errno, no further modifications are permissible. Paragraph 3 of section 7.5 ЛErrors Ћ says: ``The value of errno is zero at program startup, but is never set to zero by any library function.170) The value of errno may be set to nonzero by a library function call whether or not there is an error, provided the use of errno is not documented in the description of the function in this International Standard.'' I read this as an explicit prohibition of setting errno to anything else (as strtol has a documented behaviour for setting errno), and just wondered how POSIX could get away with its (IMHO) violation of that statement. Still, my major point was that "0x" sequences are falsely rejected as conversion errors, and that strings consisting solely of a plus or minus sign should not throw an error either, as I read the C standard. I confess that I'm operating on a prerelease version of the C standard, in case that matters. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 21:44:09 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AF1916A4CE; Thu, 20 Jan 2005 21:44:09 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EDA143D53; Thu, 20 Jan 2005 21:44:08 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id j0KLi7cR070596; Fri, 21 Jan 2005 00:44:07 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id j0KLi6DC070595; Fri, 21 Jan 2005 00:44:06 +0300 (MSK) (envelope-from ache) Date: Fri, 21 Jan 2005 00:44:06 +0300 From: Andrey Chernov To: Joerg Wunsch Message-ID: <20050120214406.GA70088@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Joerg Wunsch , current@FreeBSD.ORG, bde@FreeBSD.ORG References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050120211449.GC30862@uriah.heep.sax.de> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.8; VDF: 6.29.0.73; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [0.0.0.0]); Fri, 21 Jan 2005 00:44:07 +0300 (MSK) cc: current@FreeBSD.ORG cc: bde@FreeBSD.ORG Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 21:44:09 -0000 On Thu, Jan 20, 2005 at 10:14:49PM +0100, Joerg Wunsch wrote: > Yes, I know. Anyway, how could POSIX (or the Single UNIX > Specification, for that matter) possibly contradict to the C standard? There is common practice for both POSIX and SUS to extend errno values beyond C standard, see lots of other functions. Personally I do not research the reason of their decision, just point to the fact. > ``The value of errno is zero at program startup, but is never set to > zero by any library function.170) The value of errno may be set to ^^^^^^^^^^^^^^^^ > nonzero by a library function call whether or not there is an error, > provided the use of errno is not documented in the description of the ^^^^^^^^^^^^^^^^^ > function in this International Standard.'' Errno may be set in case of error with not documented errno. Thats how I read it, but I may miss something. > Still, my major point was that "0x" sequences are falsely rejected as It clearly should be rejected with EINVAL in case base == 16, because 0 alone is not valid HEX sequence and no valid sequence found at this point. I am not sure about other bases. > conversion errors, and that strings consisting solely of a plus or > minus sign should not throw an error either, as I read the C standard. +- may produce EINVAL, as POSIX says. In general please don't forget that strtol(), atol() etc. supposed to parse user input and _detect_ syntax errors, it is their purpose. If they not do it or do it in half, each program forced to use its own parser instead. -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 21:57:56 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C1E116A4CE; Thu, 20 Jan 2005 21:57:56 +0000 (GMT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id C961E43D39; Thu, 20 Jan 2005 21:57:55 +0000 (GMT) (envelope-from clint@0lsen.net) Received: from 0lsen.net ([24.20.127.157]) by comcast.net (rwcrmhc12) with ESMTP id <200501202157530140015eqce>; Thu, 20 Jan 2005 21:57:55 +0000 Received: by 0lsen.net (Postfix, from userid 1001) id 143FF17AB0; Thu, 20 Jan 2005 13:57:53 -0800 (PST) Date: Thu, 20 Jan 2005 13:57:53 -0800 From: Clint Olsen To: Andrey Chernov , Joerg Wunsch , current@FreeBSD.ORG, bde@FreeBSD.ORG Message-ID: <20050120215753.GF54711@0lsen.net> References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050120214406.GA70088@nagual.pp.ru> User-Agent: Mutt/1.4.2.1i Organization: NULlsen Network X-Disclaimer: Mutt Bites! Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 21:57:56 -0000 On Jan 21, Andrey Chernov wrote: > In general please don't forget that strtol(), atol() etc. supposed to > parse user input and _detect_ syntax errors, it is their purpose. If they > not do it or do it in half, each program forced to use its own parser > instead. If you want to be sure about your interpretation of the standard, you could inquire on comp.lang.c. I'm sure you will get a complete answer on that forum. -Clint From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 21:58:11 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 177C916A4CE; Thu, 20 Jan 2005 21:58:11 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E56043D53; Thu, 20 Jan 2005 21:58:10 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id j0KLw8OS070859; Fri, 21 Jan 2005 00:58:08 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id j0KLw86u070858; Fri, 21 Jan 2005 00:58:08 +0300 (MSK) (envelope-from ache) Date: Fri, 21 Jan 2005 00:58:07 +0300 From: Andrey Chernov To: Joerg Wunsch , current@FreeBSD.ORG, bde@FreeBSD.ORG Message-ID: <20050120215807.GA70629@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Joerg Wunsch , current@FreeBSD.ORG, bde@FreeBSD.ORG References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050120214406.GA70088@nagual.pp.ru> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.8; VDF: 6.29.0.73; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [0.0.0.0]); Fri, 21 Jan 2005 00:58:09 +0300 (MSK) Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 21:58:11 -0000 On Fri, Jan 21, 2005 at 12:44:06AM +0300, Andrey Chernov wrote: > > Still, my major point was that "0x" sequences are falsely rejected as > > It clearly should be rejected with EINVAL in case base == 16, > because 0 alone is not valid HEX sequence and no valid sequence found at > this point. I am not sure about other bases. It seems I am wrong here and you are right. POSIX says that 0x is optional even for base 16. So "0xZ" with base 16 means just 0. If our strtol() produce error here, it should be fixed: "If the value of base is 16, the characters 0x or 0X may optionally ^^^^^^^^^^^ precede the sequence of letters and digits, following the sign if present." -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 22:02:32 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C904A16A4CE; Thu, 20 Jan 2005 22:02:32 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12C8243D4C; Thu, 20 Jan 2005 22:02:32 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id j0KM2Ubj071061; Fri, 21 Jan 2005 01:02:30 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id j0KM2UEi071053; Fri, 21 Jan 2005 01:02:30 +0300 (MSK) (envelope-from ache) Date: Fri, 21 Jan 2005 01:02:28 +0300 From: Andrey Chernov To: Joerg Wunsch , current@FreeBSD.ORG, bde@FreeBSD.ORG Message-ID: <20050120220227.GB70629@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Joerg Wunsch , current@FreeBSD.ORG, bde@FreeBSD.ORG References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050120214406.GA70088@nagual.pp.ru> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.8; VDF: 6.29.0.73; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [0.0.0.0]); Fri, 21 Jan 2005 01:02:31 +0300 (MSK) Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 22:02:32 -0000 On Fri, Jan 21, 2005 at 12:44:06AM +0300, Andrey Chernov wrote: > +- may produce EINVAL, as POSIX says. Because "no conversion could be performed", i.e. no single digit found. -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 22:11:56 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 79B3216A4CE; Thu, 20 Jan 2005 22:11:56 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8566043D1F; Thu, 20 Jan 2005 22:11:55 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id j0KMBsD6071265; Fri, 21 Jan 2005 01:11:54 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id j0KMBsWm071264; Fri, 21 Jan 2005 01:11:54 +0300 (MSK) (envelope-from ache) Date: Fri, 21 Jan 2005 01:11:54 +0300 From: Andrey Chernov To: Joerg Wunsch , current@FreeBSD.ORG, bde@FreeBSD.ORG Message-ID: <20050120221154.GC70629@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Joerg Wunsch , current@FreeBSD.ORG, bde@FreeBSD.ORG References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120215807.GA70629@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050120215807.GA70629@nagual.pp.ru> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.8; VDF: 6.29.0.73; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [0.0.0.0]); Fri, 21 Jan 2005 01:11:54 +0300 (MSK) Subject: [patch] Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 22:11:56 -0000 On Fri, Jan 21, 2005 at 12:58:07AM +0300, Andrey Chernov wrote: > "If the value of base is 16, the characters 0x or 0X may optionally > ^^^^^^^^^^^ > precede the sequence of letters and digits, following the sign if > present." Here is untested patch to fix the problem: --- strtol.c.bak Fri Jan 21 01:06:06 2005 +++ strtol.c Fri Jan 21 01:09:30 2005 @@ -76,7 +76,11 @@ c = *s++; } if ((base == 0 || base == 16) && - c == '0' && (*s == 'x' || *s == 'X')) { + c == '0' && (*s == 'x' || *s == 'X') && + (s[1] >= 'a' && s[1] <= 'f' || + s[1] >= 'A' && s[1] <= 'F' || + s[1] >= '0' && s[1] <= '9') + ) { c = s[1]; s += 2; base = 16; -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 22:30:08 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58FA716A4CF; Thu, 20 Jan 2005 22:30:08 +0000 (GMT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3BBC43D39; Thu, 20 Jan 2005 22:30:07 +0000 (GMT) (envelope-from j@uriah.heep.sax.de) Received: from sax.sax.de (localhost [127.0.0.1]) by sax.sax.de (8.12.10/8.12.10) with ESMTP id j0KMU6Yu057169; Thu, 20 Jan 2005 23:30:06 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.12.10/8.12.10/Submit) with UUCP id j0KMU6Pg057168; Thu, 20 Jan 2005 23:30:06 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: from uriah.heep.sax.de (localhost [127.0.0.1]) by uriah.heep.sax.de (8.13.1/8.13.1) with ESMTP id j0KMLbjD035872; Thu, 20 Jan 2005 23:21:37 +0100 (MET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.13.1/8.13.1/Submit) id j0KMLbxk035871; Thu, 20 Jan 2005 23:21:37 +0100 (MET) (envelope-from j) Date: Thu, 20 Jan 2005 23:21:37 +0100 From: Joerg Wunsch To: current@FreeBSD.ORG Message-ID: <20050120222137.GE30862@uriah.heep.sax.de> References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050120214406.GA70088@nagual.pp.ru> User-Agent: Mutt/1.4.2.1i X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-GPG-Fingerprint: 5E84 F980 C3CA FD4B B584 1070 F48C A81B 69A8 5873 X-Spam-Status: No, score=-2.6 required=7.5 tests=BAYES_00 autolearn=ham version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on uriah.heep.sax.de cc: Andrey Chernov cc: bde@FreeBSD.ORG Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joerg Wunsch List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 22:30:08 -0000 As Andrey Chernov wrote: > Errno may be set in case of error with not documented errno. Thats > how I read it, but I may miss something. I read that a bit differently. > > Still, my major point was that "0x" sequences are falsely rejected as > It clearly should be rejected with EINVAL in case base == 16, > because 0 alone is not valid HEX sequence Nope. "0" alone is a completely valid hexadecimal number, representing the value 0. Conversion has to start at the 0 (as it is not invalid), and to stop at the x. The string "0x" simply means there is *no* optional 0x prefix, but just a number 0 without a prefix (followed by a letter that cannot be converted, so it has to be passed as final string). > > conversion errors, and that strings consisting solely of a plus or > > minus sign should not throw an error either, as I read the C standard. > +- may produce EINVAL, as POSIX says. Where? Again, I'd value the C standard higher than Posix. C says they form a valid subject sequence. Thus, no error may be flagged. I don't have Posix at hand, but SUSPv2 completely follows the C standard, with the only addition that EINVAL might be flagged in the case of a conversion error. As a subject sequence consisting of a sign only (+ or -) does not constitute an empty subject sequence, thus no conversion error is permissible. This implies EINVAL must not be set. > In general please don't forget that strtol(), atol() etc. supposed > to parse user input and _detect_ syntax errors, it is their > purpose. If they not do it or do it in half, each program forced to > use its own parser instead. This is no excuse for violating standards. If a user feels that a single sign must not be interpreted as a valid 0, they indeed have to apply their own checks. It would be no use to them if FreeBSD's strtoul (erroneously) flagged it as an error, while any standard-compliant implementation would not fulfill their expectations anyway. As a demonstration, consider this test program: #include #include #include const char *s[] = { "", "+", "-", "0x", "-0x" }; int main(void) { size_t i; char *p; long l; for (i = 0; i < sizeof s / sizeof s[0]; i++) { errno = 0; l = strtol(s[i], &p, 16); printf("\"%s\" -> %ld, len %u, errno %d\n", s[i], l, p - s[i], errno); } return 0; } Below are the results for Solaris 8, FreeBSD 5, Linux 2.x, and HP-UX 10.20. helios% ./foo "" -> 0, len 0, errno 0 "+" -> 0, len 0, errno 0 "-" -> 0, len 0, errno 0 "0x" -> 0, len 1, errno 0 "-0x" -> 0, len 2, errno 0 j@uriah 1259% ./foo "" -> 0, len 0, errno 22 "+" -> 0, len 0, errno 22 "-" -> 0, len 0, errno 22 "0x" -> 0, len 0, errno 22 "-0x" -> 0, len 0, errno 22 j@lux 344% ./foo "" -> 0, len 0, errno 0 "+" -> 0, len 0, errno 0 "-" -> 0, len 0, errno 0 "0x" -> 0, len 1, errno 0 "-0x" -> 0, len 2, errno 0 j@king 105% ./foo "" -> 0, len 0, errno 0 "+" -> 0, len 0, errno 0 "-" -> 0, len 0, errno 0 "0x" -> 0, len 0, errno 0 "-0x" -> 0, len 0, errno 0 It's quite obvious that any other system differs from FreeBSD here. (OK, HP-UX doesn't throw EINVAL at all, even for clearly inconvertible strings. But then, it's a pretty old system, more than ten years.) As the Posix/SUSPv2 standard say ``may set to EINVAL'', I'd even go with the majority and not set EINVAL for an empty string even though it technically constitutes a conversion error according to the C standard. It's quite pointless to handle a single plus or minus sign differently than an empty string, and as both the C and Posix/SUSP standards mandate that +/- must not cause a conversion error, just don't flag the error for the empty string either. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 22:40:09 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0317516A4CF; Thu, 20 Jan 2005 22:40:09 +0000 (GMT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AF8743D3F; Thu, 20 Jan 2005 22:40:08 +0000 (GMT) (envelope-from j@uriah.heep.sax.de) Received: from sax.sax.de (localhost [127.0.0.1]) by sax.sax.de (8.12.10/8.12.10) with ESMTP id j0KMe7Yu057562; Thu, 20 Jan 2005 23:40:07 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.12.10/8.12.10/Submit) with UUCP id j0KMe7Ow057561; Thu, 20 Jan 2005 23:40:07 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: from uriah.heep.sax.de (localhost [127.0.0.1]) by uriah.heep.sax.de (8.13.1/8.13.1) with ESMTP id j0KMWXxS036215; Thu, 20 Jan 2005 23:32:33 +0100 (MET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.13.1/8.13.1/Submit) id j0KMWWjV036195; Thu, 20 Jan 2005 23:32:32 +0100 (MET) (envelope-from j) Date: Thu, 20 Jan 2005 23:32:32 +0100 From: Joerg Wunsch To: current@FreeBSD.ORG Message-ID: <20050120223232.GF30862@uriah.heep.sax.de> References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120220227.GB70629@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050120220227.GB70629@nagual.pp.ru> User-Agent: Mutt/1.4.2.1i X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-GPG-Fingerprint: 5E84 F980 C3CA FD4B B584 1070 F48C A81B 69A8 5873 X-Spam-Status: No, score=-2.6 required=7.5 tests=AWL,BAYES_00 autolearn=ham version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on uriah.heep.sax.de cc: Andrey Chernov cc: bde@FreeBSD.ORG Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joerg Wunsch List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 22:40:09 -0000 As Andrey Chernov wrote: > > +- may produce EINVAL, as POSIX says. > Because "no conversion could be performed", i.e. no single digit > found. No, sorry. You can perform a conversion on any valid subject sequence (that ``has the expected form''). The optional sign is part of the valid sequence. ``The subject sequence contains no characters if the input string is empty or consists entirely of white-space characters, or if the first non-white-space character is other than a sign or a permissible letter or digit.'' That clearly doesn't apply to a string consisting of a single sign only, as its first non-white-space character is the sign (so it cannot be ``other than a sign''). Thus, we do not have a no-character subject sequence (which would constitute an empty subject sequence that in turn cannot be converted). Thus, we do have a subject sequence of the ``expected form''. Any such sequence is convertible per definitionem. An empty subject sequence would cause no conversion to be performed. Yet see the comparision to Solaris and Linux, they both don't flag it with an EINVAL. As Posix/SUSP doesn't make EINVAL mandatory, I'd rather go with not setting it in that case either. Well, as *I* read it, a single sign would cause that sign to become part of the number to be (successfully) converted, so it cannot be part of the final string. Yet, both the Solaris and the Linux implementation treat a single sign as becoming the final string. This is indeed a question for the language lawyers on comp.lang.c ... Are you going to ask there, Andrey, or do you want me to ask? -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 22:40:40 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C512716A4CF; Thu, 20 Jan 2005 22:40:40 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD66F43D53; Thu, 20 Jan 2005 22:40:19 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id j0KMeIPD071723; Fri, 21 Jan 2005 01:40:18 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id j0KMeIEO071722; Fri, 21 Jan 2005 01:40:18 +0300 (MSK) (envelope-from ache) Date: Fri, 21 Jan 2005 01:40:18 +0300 From: Andrey Chernov To: Joerg Wunsch Message-ID: <20050120224017.GA71573@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Joerg Wunsch , current@FreeBSD.ORG, bde@FreeBSD.ORG References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120222137.GE30862@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050120222137.GE30862@uriah.heep.sax.de> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.8; VDF: 6.29.0.73; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [0.0.0.0]); Fri, 21 Jan 2005 01:40:18 +0300 (MSK) cc: current@FreeBSD.ORG cc: bde@FreeBSD.ORG Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 22:40:41 -0000 On Thu, Jan 20, 2005 at 11:21:37PM +0100, Joerg Wunsch wrote: > Nope. "0" alone is a completely valid hexadecimal number, > representing the value 0. Conversion has to start at the 0 (as it is I agree with you in this part, see my patch with POSIX quote. > > +- may produce EINVAL, as POSIX says. > > Where? 1) "If the subject sequence is empty or does not have the expected form, no conversion is performed;" 2) "If no conversion could be performed, 0 shall be returned and errno may be set to [EINVAL]." All "expected forms" (integer, octal, hex, other bases constants) are perfectly described at the start and +- alone is not among them. > Again, I'd value the C standard higher than Posix. C says they form a > valid subject sequence. Thus, no error may be flagged. But FreeBSD always tends to follow POSIX as final judge. At least in the past... > I don't have Posix at hand, but SUSPv2 completely follows the C You can download free PDF copy at their site, just register there. > This is no excuse for violating standards. If a user feels that a This is just their intehtions explanation, not excuse. If several standards are in contradiction, POSIX vote is final. It may surprise you, but it covers and changes lots of cases comparing to minimalistic C standard. Such additions/changes are specially marked with different color (gray). -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 22:47:55 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF96516A4CE; Thu, 20 Jan 2005 22:47:55 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29B5943D54; Thu, 20 Jan 2005 22:47:55 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id j0KMlsIM071857; Fri, 21 Jan 2005 01:47:54 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id j0KMlsuf071856; Fri, 21 Jan 2005 01:47:54 +0300 (MSK) (envelope-from ache) Date: Fri, 21 Jan 2005 01:47:53 +0300 From: Andrey Chernov To: Joerg Wunsch Message-ID: <20050120224753.GB71573@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Joerg Wunsch , current@FreeBSD.ORG, bde@FreeBSD.ORG References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120220227.GB70629@nagual.pp.ru> <20050120223232.GF30862@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050120223232.GF30862@uriah.heep.sax.de> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.8; VDF: 6.29.0.73; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [0.0.0.0]); Fri, 21 Jan 2005 01:47:54 +0300 (MSK) cc: current@FreeBSD.ORG cc: bde@FreeBSD.ORG Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 22:47:56 -0000 On Thu, Jan 20, 2005 at 11:32:32PM +0100, Joerg Wunsch wrote: > You can perform a conversion on any valid subject sequence (that ``has > the expected form''). The optional sign is part of the valid > sequence. As you (and POSIX) say, it is only PART of the valid sequence, but not whole valid sequence which could be converted. > Thus, we do have a subject sequence of the ``expected form''. Any > such sequence is convertible per definitionem. This is just your speculation about what "expected form" is. But POSIX clearly says, what expected form is: "If the value of base is 0, the expected form of the subject sequence is ^^^^^^^^^^^^^^^^^^^ that of a decimal constant, octal constant, or hexadecimal constant, any of which may be preceded by a .+. or .-. sign." No CONSTANT found in just +- case. Next, lets see what expected form is, if base is nonzero: "If the value of base is between 2 and 36, the expected form of the ^^^^^^^^^^^^^^^^^ subject sequence is a sequence of letters and digits representing an integer with the radix specified by base, optionally preceded by a .+. or .-. sign." The same no SEQUENCE OF LETTERS AND DIGITS found in just +- case. As I say, read POSIX, please. -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 23:05:39 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FC0616A4CE for ; Thu, 20 Jan 2005 23:05:39 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEF7443D1D for ; Thu, 20 Jan 2005 23:05:36 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C01EE511C1; Thu, 20 Jan 2005 15:05:26 -0800 (PST) Date: Thu, 20 Jan 2005 15:05:26 -0800 From: Kris Kennaway To: "Mark W. Krentel" Message-ID: <20050120230526.GA76209@xor.obsecurity.org> References: <20050119050220.GU3194@noel.cs.rice.edu> <200501202247.j0KMlvJH032907@blue.mwk.domain> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6c2NcOVqGQ03X4Wi" Content-Disposition: inline In-Reply-To: <200501202247.j0KMlvJH032907@blue.mwk.domain> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org cc: Alan Cox cc: Kris Kennaway Subject: Re: fstat triggered INVARIANTS panic in memrw() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 23:05:39 -0000 --6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 20, 2005 at 05:47:57PM -0500, Mark W. Krentel wrote: > First, let me check that your panic requires three things to trigger: > (1) heavy load, in your case ports building, (2) INVARIANTS compiled > into the kernel, and (3) many calls to fstat(1). Is that right? I didn't try without INVARIANTS, but it doesn't require heavy load. In fact I can panic the UP boxes just by running fstat in a loop (typically panics within a few seconds). SMP often panics on the first try. > Also, you're running 6.0-current on an x86 SMP machine?=20 I think it also happens on 5.x, but I'm not sure. I first noticed the problem some time in early December, but it might be older (I previously did not run fstat on these machines). > Can you bound > the problem between two dates, that is, you compiled kernel/world on > date X and it was ok, and updated on date Y and it panicked? Are you > changing the default kernel address space (3 Gig user and 1 Gig > kernel) via KVA_PAGES? Not on all affected machines (i.e. it happens on machines with the default KVA_PAGES). > arguments to kernacc() and vm_map_check_protection(). I didn't get a > panic, but I can confirm that kernacc() is being called with arguments > that constitute address wrap. My tests were on a single-CPU P3-933. > I ran buildworld along with a loop of fstat(1)s, and the address wrap > happened within seconds. It required both (1) and (3) above, > INVARIANTS may be a red herring, I'm not sure. >=20 > How long did it take for your machine to panic? Mine didn't panic, > but maybe I didn't run the test long enough, or maybe I don't have > enough open files. >=20 > Anyway, try this patch, see if it avoids the panic for you. >=20 > --Mark Thanks, it sounds promising! Kris --6c2NcOVqGQ03X4Wi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB8Dk2Wry0BWjoQKURAspDAKD7bQ26qJAeXt312kpQ1uD8sFytKQCfVeYa W+sTEjcdvXni4bKKcFS40Kc= =J89l -----END PGP SIGNATURE----- --6c2NcOVqGQ03X4Wi-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 23:54:46 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25FB716A4CE; Thu, 20 Jan 2005 23:54:46 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DFB843D2F; Thu, 20 Jan 2005 23:54:45 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id j0KNshmD072929; Fri, 21 Jan 2005 02:54:43 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id j0KNshNh072928; Fri, 21 Jan 2005 02:54:43 +0300 (MSK) (envelope-from ache) Date: Fri, 21 Jan 2005 02:54:42 +0300 From: Andrey Chernov To: Matthias Andree Message-ID: <20050120235441.GA72814@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Matthias Andree , Joerg Wunsch , current@FreeBSD.ORG, bde@FreeBSD.ORG References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120222137.GE30862@uriah.heep.sax.de> <20050120224017.GA71573@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.8; VDF: 6.29.0.73; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [0.0.0.0]); Fri, 21 Jan 2005 02:54:44 +0300 (MSK) cc: Joerg Wunsch cc: current@FreeBSD.ORG cc: bde@FreeBSD.ORG Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 23:54:46 -0000 On Fri, Jan 21, 2005 at 12:18:07AM +0100, Matthias Andree wrote: > > This is just their intehtions explanation, not excuse. If several > > standards are in contradiction, POSIX vote is final. It may surprise you, > > but it covers and changes lots of cases comparing to minimalistic C > > standard. Such additions/changes are specially marked with different color > > (gray). > > I do not have a place of discovery handy, but wasn't POSIX explicitly > deferring in to the C standard and giving it precedence for any > conflicts between the C standard library and POSIX? What really happens is more complex thing. POSIX tries to follow C standard as close as possible. If POSIX makes an addition not mentioned in the relatively minimalistic C or SUS standards (because such case even was not considered there but vital enough to system level), this addition not contradicts with C standard _directly_ i.e. not opposite it, but from now two example cases handled equaly by minimalistic standards handled now differently by POSIX due to additional (non-described previously) treatement. -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 00:09:20 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75C8D16A4D0; Fri, 21 Jan 2005 00:09:20 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF8AC43D2F; Fri, 21 Jan 2005 00:09:19 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id j0L09IKR073407; Fri, 21 Jan 2005 03:09:18 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id j0L09I8b073406; Fri, 21 Jan 2005 03:09:18 +0300 (MSK) (envelope-from ache) Date: Fri, 21 Jan 2005 03:09:17 +0300 From: Andrey Chernov To: Joerg Wunsch Message-ID: <20050121000916.GA73235@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Joerg Wunsch , current@FreeBSD.ORG, bde@FreeBSD.ORG References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120222137.GE30862@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050120222137.GE30862@uriah.heep.sax.de> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.8; VDF: 6.29.0.73; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [0.0.0.0]); Fri, 21 Jan 2005 03:09:18 +0300 (MSK) cc: current@FreeBSD.ORG cc: bde@FreeBSD.ORG Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 00:09:20 -0000 On Thu, Jan 20, 2005 at 11:21:37PM +0100, Joerg Wunsch wrote: > As Andrey Chernov wrote: > > > Errno may be set in case of error with not documented errno. Thats > > how I read it, but I may miss something. > > I read that a bit differently. People please, I want to make it clear, personally I not from POSIX commitee. If you disagree with POSIX, please discuss it on their forums, not with me. All I can is to make some loosely assumptions about their logic. If you disagree that FreeBSD must follow POSIX (as united and superseded things among all several other standards related to the subject), this should be CORE decision. Because in the past POSIX word was final thing for FreeBSD implemetations, not C, not SUS. -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 00:31:57 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FE9716A4CE; Fri, 21 Jan 2005 00:31:57 +0000 (GMT) Received: from stephanie.unixdaemons.com (stephanie.unixdaemons.com [67.18.111.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA36D43D48; Fri, 21 Jan 2005 00:31:56 +0000 (GMT) (envelope-from bmilekic@technokratis.com) Received: from stephanie.unixdaemons.com (bmilekic@localhost.unixdaemons.com [127.0.0.1])j0L0Vqig045736; Thu, 20 Jan 2005 19:31:52 -0500 (EST) Received: (from bmilekic@localhost) by stephanie.unixdaemons.com (8.13.2/8.12.1/Submit) id j0L0Vq3x045735; Thu, 20 Jan 2005 19:31:52 -0500 (EST) (envelope-from bmilekic@technokratis.com) X-Authentication-Warning: stephanie.unixdaemons.com: bmilekic set sender to bmilekic@technokratis.com using -f Date: Thu, 20 Jan 2005 19:31:52 -0500 From: Bosko Milekic To: Scott Long Message-ID: <20050121003152.GA44244@technokratis.com> References: <20050120140300.F1832@bahre.achedra.org> <41F00697.7010000@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41F00697.7010000@freebsd.org> User-Agent: Mutt/1.4.2.1i cc: "Ketrien I. Saihr-Kenchedra" cc: current@freebsd.org cc: Bosko Milekic Subject: Re: Memory modified after free - Jan20 -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 00:31:57 -0000 http://bmilekic.unixdaemons.com/MemGuard.diff put options DEBUG_MEMGUARD in your kernel config, and look at the DEBUG_MEMGUARD ifdefs in malloc(), free(), and realloc() inside kern/kern_malloc.c; the short of it is that you'll have to manually modify those ifdef'd portions of code referring to M_SUBPROC in the diff to M_WHATEVER. I'm going to commit a version of this soon. Don't run the patch unless you know what you're doing. Later, Bosko. On Thu, Jan 20, 2005 at 12:29:27PM -0700, Scott Long wrote: > Ketrien I. Saihr-Kenchedra wrote: > > >Screen transcription attached. In a nutshell; > > > >fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 > >device_attach: fdc0 returned 6 > >sio0: <16550A-compatible COM port> port0x3f8-0x3ff irq 4 flags 0x10 on > >acpi0 > >sio0: type 16550A > >Memory modified after free 0xc1cde200(252) val=0 @ 0xc1cde228 > >panic: Most recently used by none > > > >System was fine with Jan16 srcs, fdc returning 6 is new. Looks like a uma > >problem to me, but odd enough that I'm honestly not sure. Need ips(4) for > >dumpdev, so no dump again. (Argh.) > > > > I'm seeing this quite often too. I'm hoping that Bosko will make his > memguard changes available soon as I'm sure it could quickly be tracked > down with them. > > Scott > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Bosko Milekic bmilekic@technokratis.com bmilekic@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 05:38:07 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BC9E16A4F6; Fri, 21 Jan 2005 05:38:07 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B690543D2D; Fri, 21 Jan 2005 05:38:06 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id j0L5c5jc065439; Fri, 21 Jan 2005 00:38:05 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.1/8.13.1) with ESMTP id j0L5c53L053811; Fri, 21 Jan 2005 00:38:05 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 7CC3E7306E; Fri, 21 Jan 2005 00:38:05 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20050121053805.7CC3E7306E@freebsd-current.sentex.ca> Date: Fri, 21 Jan 2005 00:38:05 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/625/Fri Dec 10 12:41:57 2004 clamav-milter version 0.80j on clamscanner2 X-Virus-Scanned: ClamAV 0.80/671/Mon Jan 17 09:16:31 2005 clamav-milter version 0.80j on clamscanner4 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 05:38:07 -0000 TB --- 2005-01-21 04:02:42 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-01-21 04:02:42 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2005-01-21 04:02:42 - checking out the source tree TB --- 2005-01-21 04:02:42 - cd /home/tinderbox/CURRENT/sparc64/sparc64 TB --- 2005-01-21 04:02:42 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-01-21 04:08:26 - building world (CFLAGS=-O2 -pipe) TB --- 2005-01-21 04:08:26 - cd /home/tinderbox/CURRENT/sparc64/sparc64/src TB --- 2005-01-21 04:08:26 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-01-21 05:18:17 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-01-21 05:18:17 - cd /home/tinderbox/CURRENT/sparc64/sparc64/src TB --- 2005-01-21 05:18:17 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Jan 21 05:18:18 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Fri Jan 21 05:32:53 UTC 2005 TB --- 2005-01-21 05:32:53 - generating LINT kernel config TB --- 2005-01-21 05:32:53 - cd /home/tinderbox/CURRENT/sparc64/sparc64/src/sys/sparc64/conf TB --- 2005-01-21 05:32:53 - /usr/bin/make -B LINT TB --- 2005-01-21 05:32:53 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-01-21 05:32:53 - cd /home/tinderbox/CURRENT/sparc64/sparc64/src TB --- 2005-01-21 05:32:53 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Jan 21 05:32:54 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/altq -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/pf -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/en/if_en_pci.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/altq -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/pf -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/en/midway.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/altq -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/pf -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/esp/ncr53c9x.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/altq -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/pf -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/exca/exca.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/altq -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/pf -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/fatm/if_fatm.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/altq -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/pf -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/fe/if_fe.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/altq -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/pf -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/fe/if_fe_pccard.c /tinderbox/CURRENT/sparc64/sparc64/src/sys/dev/fe/if_fe_pccard.c:64: warning: 'fe_pccard_mem_ether' declared `static' but never defined *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/tinderbox/CURRENT/sparc64/sparc64/src/sys/LINT. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src. TB --- 2005-01-21 05:38:04 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-01-21 05:38:04 - ERROR: failed to build lint kernel TB --- 2005-01-21 05:38:04 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 06:46:23 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCE0E16A4FE for ; Fri, 21 Jan 2005 06:46:20 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id A12A743D1F for ; Fri, 21 Jan 2005 06:46:20 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D3541519E7; Thu, 20 Jan 2005 22:46:19 -0800 (PST) Date: Thu, 20 Jan 2005 22:46:19 -0800 From: Kris Kennaway To: "Mark W. Krentel" Message-ID: <20050121064619.GA1125@xor.obsecurity.org> References: <20050119050220.GU3194@noel.cs.rice.edu> <200501202247.j0KMlvJH032907@blue.mwk.domain> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ikeVEW9yuYc//A+q" Content-Disposition: inline In-Reply-To: <200501202247.j0KMlvJH032907@blue.mwk.domain> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org cc: Alan Cox cc: Kris Kennaway Subject: Re: fstat triggered INVARIANTS panic in memrw() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 06:46:23 -0000 --ikeVEW9yuYc//A+q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jan 20, 2005 at 05:47:57PM -0500, Mark W. Krentel wrote: > Anyway, try this patch, see if it avoids the panic for you. Preliminary testing looks good. I'll deploy it on the rest of the machines when they become free and give it a more intensive spin. Thanks very much! Kris --ikeVEW9yuYc//A+q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB8KU7Wry0BWjoQKURArRKAKCfwZ1Pkr5JDHMwWYgOFFurpZuzYACfQJys ccTLuLktn2XZ+TGDVpTriKY= =Rvip -----END PGP SIGNATURE----- --ikeVEW9yuYc//A+q-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 07:33:17 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 539AA16A4CE for ; Fri, 21 Jan 2005 07:33:17 +0000 (GMT) Received: from hetzner.co.za (lfw.hetzner.co.za [196.7.18.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E8B843D48 for ; Fri, 21 Jan 2005 07:33:15 +0000 (GMT) (envelope-from ianf@hetzner.co.za) Received: from localhost ([127.0.0.1]) by hetzner.co.za with esmtp (Exim 3.36 #1) id 1CrtI9-0000ed-00 for freebsd-current@freebsd.org; Fri, 21 Jan 2005 09:33:13 +0200 To: freebsd-current@freebsd.org From: Ian FREISLICH X-Attribution: BOFH Date: Fri, 21 Jan 2005 09:33:13 +0200 Sender: ianf@hetzner.co.za Message-Id: Subject: LOR and boot time lockups X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 07:33:17 -0000 Hi I've been unable to successfully boot a kernel since Jan 19. The offending change happened between Jan 10 and Jan 19. I will do the binary search for the change if nobody has any ideas, but I want to ask first; it takes little over an hour to compile a kernel on this system. It fails at the ATA probe, or if I remove ata from the kernel, the last message is from somewhere in the SCSI probe: "Waiting 15 seconds for SCSI devices to settle". I can't reasonably remove the SCSI stuff from the kernel to see what happens next because the ufs root is on a SCSI disk. At least the debugger is avalable. I don't really know what is useful information so here's what I can think of off the top of my head. Timecounters tick every 1.000 msec ipfw2 initialized, divert loadable, rule-based forwarding enabled, default to deny, logging unlimited Waiting 15 seconds for SCSI devices to settle *** Waited 1 minute then sent a line break*** KDB: enter: Line break on console [thread pid 45 tid 100061 ] Stopped at kdb_enter+0x2b: nop db> ce Tracing pid 45 tid 100061 td 0xc10b8170 kdb_enter(c062c0eb) at kdb_enter+0x2b siointr1(c10d8400) at siointr1+0xce siointr(c10d8400) at siointr+0x5e intr_execute_handlers(c1018090,d0e98cdc,4,d0e98d28,c05d0633) at intr_execute_han dlers+0x7d lapic_handle_intr(34) at lapic_handle_intr+0x2e Xapic_isr1() at Xapic_isr1+0x33 --- interrupt, eip = 0xc04dd1aa, esp = 0xd0e98d20, ebp = 0xd0e98d28 --- critical_exit(c10afa80,0,c05d02dc,c04b639c,c10afa80) at critical_exit+0xd2 fork_exit(c04b639c,c10afa80,d0e98d48) at fork_exit+0x6c fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xd0e98d7c, ebp = 0 --- db> sho pcpu 0 cpuid = 0 curthread = 0xc10b8170: pid 45 "swi0: sio" curpcb = 0xd0e98da0 fpcurthread = none idlethread = 0xc0fe1730: pid 12 "idle: cpu0" APIC ID = 0 currentldt = 0x28 db> sho pcpu 1 cpuid = 1 curthread = 0xc0fe15c0: pid 11 "idle: cpu1" curpcb = 0 fpcurthread = none idlethread = 0xc0fe15c0: pid 11 "idle: cpu1" APIC ID = 1 currentldt = 0x28 db> ps pid proc uid ppid pgrp flag stat wmesg wchan cmd 45 c10b59d8 0 0 0 0000204 [CPU 0] swi0: sio 8 c10b5bd0 0 0 0 0000204 [RUNQ] aic_recovery0 7 c102bbd0 0 0 0 0000204 [RUNQ] aic_recovery0 44 c102bdc8 0 0 0 0000204 [RUNQ] usbtask 43 c103d000 0 0 0 0000204 [RUNQ] usb0 6 c103d1f8 0 0 0 0000204 [RUNQ] kqueue taskq 42 c103d3f0 0 0 0 0000204 [IWAIT] swi2: cambio 41 c103d5e8 0 0 0 0000204 [IWAIT] swi5:+ 5 c103d7e0 0 0 0 0000204 [RUNQ] thread taskq 40 c103d9d8 0 0 0 0000204 [IWAIT] swi6:+ 39 c103dbd0 0 0 0 0000204 [IWAIT] swi6: task queue 38 c103ddc8 0 0 0 0000204 [RUNQ] yarrow 4 c103f000 0 0 0 0000204 [RUNQ] g_down 3 c103f1f8 0 0 0 0000204 [RUNQ] g_up 2 c10225e8 0 0 0 0000204 [RUNQ] g_event 37 c10227e0 0 0 0 0000204 [IWAIT] swi1: net 36 c10229d8 0 0 0 0000204 [IWAIT] swi3: vm 35 c1022bd0 0 0 0 000020c [RUNQ] swi4: clock sio 34 c1022dc8 0 0 0 0000204 [IWAIT] irq0: clk 33 c102b000 0 0 0 0000204 [IWAIT] irq22: 32 c102b1f8 0 0 0 0000204 [IWAIT] irq21: 31 c102b3f0 0 0 0 0000204 [IWAIT] irq20: 30 c102b5e8 0 0 0 0000204 [IWAIT] irq19: 29 c102b7e0 0 0 0 0000204 [IWAIT] irq18: 28 c102b9d8 0 0 0 0000204 [IWAIT] irq17: 27 c0fea1f8 0 0 0 0000204 [IWAIT] irq16: xl0 ahc0 26 c0fea3f0 0 0 0 0000204 [IWAIT] irq15: 25 c0fea5e8 0 0 0 0000204 [IWAIT] irq14: 24 c0fea7e0 0 0 0 0000204 [IWAIT] irq13: 23 c0fea9d8 0 0 0 0000204 [IWAIT] irq12: 22 c0feabd0 0 0 0 0000204 [IWAIT] irq11: uhci0 21 c0feadc8 0 0 0 0000204 [IWAIT] irq10: 20 c1022000 0 0 0 0000204 [IWAIT] irq9: intpm0 19 c10221f8 0 0 0 0000204 [IWAIT] irq8: rtc 18 c10223f0 0 0 0 0000204 [IWAIT] irq7: ppc0 17 c0fe0000 0 0 0 0000204 [IWAIT] irq6: 16 c0fe01f8 0 0 0 0000204 [IWAIT] irq5: 15 c0fe03f0 0 0 0 0000204 [IWAIT] irq4: sio0 14 c0fe05e8 0 0 0 0000204 [IWAIT] irq3: sio1 13 c0fe07e0 0 0 0 0000204 [IWAIT] irq1: atkbd0 12 c0fe09d8 0 0 0 000020c [Can run] idle: cpu0 11 c0fe0bd0 0 0 0 000020c [Can run] idle: cpu1 1 c0fe0dc8 0 0 0 0000200 [INACTIVE] swapper 10 c0fea000 0 0 0 0000204 [RUNQ] ktrace 0 c0667980 0 0 0 0000200 [SLPQ conifhk 0xc0648f6c][SLP] swapper I then recompiled with witness and invarients and got the following LOR earlier in the boot process. I'm not sure if it's related, but I couldn't find a reference it this particular LOR at http://sources.zabbadoz.net/freebsd/lor.html. lock order reversal 1st 0xc0c64968 32 (UMA zone) @ /usr/src/sys/vm/uma_core.c:1842 2nd 0xc0c59084 system map (system map) @ /usr/src/sys/vm/vm_map.c:2998 KDB: stack backtrace: kdb_backtrace(0,ffffffff,c0672c88,c0672b70,c063dee8) at kdb_backtrace+0x29 witness_checkorder(c0c59084,9,c061f340,bb6) at witness_checkorder+0x54c _mtx_lock_flags(c0c59084,0,c061f340,bb6) at _mtx_lock_flags+0x5b _vm_map_lock_read(c0c59000,c061f340,bb6,200007d,c) at _vm_map_lock_read+0x24 vm_map_lookup(c0820ad8,c7057000,2,c0820adc,c0820acc) at vm_map_lookup+0x28 vm_fault(c0c59000,c7057000,2,0,c065fea0) at vm_fault+0x66 trap_pfault(c0820ba0,0,c7057a69) at trap_pfault+0x11b trap(c0820018,c04e0010,c0610010,c0fd8620,c0c52420) at trap+0x30d calltrap() at calltrap+0x5 --- trap 0xc, eip = 0xc0595100, esp = 0xc0820be0, ebp = 0xc0820bec --- uma_dbg_alloc(c0c52420,0,c0fd8620,c0c64968,0) at uma_dbg_alloc+0x54 uma_zalloc_arg(c0c52420,0,1) at uma_zalloc_arg+0xfe malloc(1c,c0640820,1,4,0) at malloc+0xae resource_list_add(c10ad880,4,0,378,37f) at resource_list_add+0x2e isa_set_resource(c1042580,c1095e00,4,0,378,8) at isa_set_resource+0x8d bus_set_resource(c1095e00,4,0,378,8) at bus_set_resource+0x67 ppc_probe(c1095e00,c1095e00,c0fc7270,c1095e00,c0820d30) at ppc_probe+0xd7 ppc_isa_probe(c1095e00) at ppc_isa_probe+0x72 device_probe_child(c1042580,c1095e00,c10af000,c1095e00,1d) at device_probe_child +0xf8 device_probe_and_attach(c1095e00) at device_probe_and_attach+0x7d isa_probe_children(c1042580) at isa_probe_children+0x103 configure(0,81ec00,81e000,0,c042da65) at configure+0x32 mi_startup() at mi_startup+0x96 begin() at begin+0x2c Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xc7057a69 fault code = supervisor write, page not present instruction pointer = 0x8:0xc0595100 stack pointer = 0x10:0xc0820be0 frame pointer = 0x10:0xc0820bec code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) [thread pid 0 tid 0 ] Stopped at uma_dbg_alloc+0x54: movb $0xff,0x18(%eax,%ecx,1) db> sho proc p = 0xc065fca0, vmspace = 0xc0660000, map = 0xc0660000, pmap = 0xc06600c0 Task map 0xc0660000: pmap=0xc06600c0, nentries=0, version=1 db> ps pid proc uid ppid pgrp flag stat wmesg wchan cmd 8 c10b5bd0 0 0 0 0000204 [RUNQ] aic_recovery0 7 c102bbd0 0 0 0 0000204 [RUNQ] aic_recovery0 44 c102bdc8 0 0 0 0000204 [RUNQ] usbtask 43 c103d000 0 0 0 0000204 [RUNQ] usb0 42 c103d1f8 0 0 0 0000204 [IWAIT] swi2: cambio 41 c103d3f0 0 0 0 0000204 [IWAIT] swi5:+ 6 c103d5e8 0 0 0 0000204 [RUNQ] thread taskq 40 c103d7e0 0 0 0 0000204 [IWAIT] swi6:+ 39 c103d9d8 0 0 0 0000204 [IWAIT] swi6: task queue 5 c103dbd0 0 0 0 0000204 [RUNQ] kqueue taskq 38 c103ddc8 0 0 0 0000204 [RUNQ] yarrow 4 c103f000 0 0 0 0000204 [RUNQ] g_down 3 c103f1f8 0 0 0 0000204 [RUNQ] g_up 2 c10225e8 0 0 0 0000204 [RUNQ] g_event 37 c10227e0 0 0 0 0000204 [IWAIT] swi1: net 36 c10229d8 0 0 0 0000204 [IWAIT] swi3: vm 35 c1022bd0 0 0 0 000020c [IWAIT] swi4: clock 34 c1022dc8 0 0 0 0000204 [IWAIT] irq0: 33 c102b000 0 0 0 0000204 [IWAIT] irq22: 32 c102b1f8 0 0 0 0000204 [IWAIT] irq21: 31 c102b3f0 0 0 0 0000204 [IWAIT] irq20: 30 c102b5e8 0 0 0 0000204 [IWAIT] irq19: 29 c102b7e0 0 0 0 0000204 [IWAIT] irq18: 28 c102b9d8 0 0 0 0000204 [IWAIT] irq17: 27 c0fea1f8 0 0 0 0000204 [IWAIT] irq16: xl0 ahc0 26 c0fea3f0 0 0 0 0000204 [IWAIT] irq15: 25 c0fea5e8 0 0 0 0000204 [IWAIT] irq14: 24 c0fea7e0 0 0 0 0000204 [IWAIT] irq13: 23 c0fea9d8 0 0 0 0000204 [IWAIT] irq12: 22 c0feabd0 0 0 0 0000204 [RUNQ] irq11: uhci0 21 c0feadc8 0 0 0 0000204 [IWAIT] irq10: 20 c1022000 0 0 0 0000204 [IWAIT] irq9: intpm0 19 c10221f8 0 0 0 0000204 [IWAIT] irq8: 18 c10223f0 0 0 0 0000204 [IWAIT] irq7: 17 c0fe0000 0 0 0 0000204 [IWAIT] irq6: 16 c0fe01f8 0 0 0 0000204 [IWAIT] irq5: 15 c0fe03f0 0 0 0 0000204 [IWAIT] irq4: 14 c0fe05e8 0 0 0 0000204 [IWAIT] irq3: 13 c0fe07e0 0 0 0 0000204 [IWAIT] irq1: atkbd0 12 c0fe09d8 0 0 0 000020c [Can run] idle: cpu0 11 c0fe0bd0 0 0 0 000020c [Can run] idle: cpu1 1 c0fe0dc8 0 0 0 0000200 [INACTIVE] swapper 10 c0fea000 0 0 0 0000204 [RUNQ] ktrace 0 c065fca0 0 0 0 0000200 [CPU 0] swapper db> show pcpu cpuid = 0 curthread = 0xc065fea0: pid 0 "swapper" curpcb = 0xc0820da0 fpcurthread = none idlethread = 0xc0fe1730: pid 12 "idle: cpu0" APIC ID = 0 currentldt = 0x28 spin locks held: db> show pcpu 1 cpuid = 1 curthread = 0xc0fe15c0: pid 11 "idle: cpu1" curpcb = 0 fpcurthread = none idlethread = 0xc0fe15c0: pid 11 "idle: cpu1" APIC ID = 1 currentldt = 0x28 spin locks held: -- Ian Freislich From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 07:54:03 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 749FD16A4CE for ; Fri, 21 Jan 2005 07:54:03 +0000 (GMT) Received: from zombie.ezone.ru (zombie.ezone.ru [195.128.162.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2B1D43D41 for ; Fri, 21 Jan 2005 07:54:01 +0000 (GMT) (envelope-from mcsi@mcsi.pp.ru) Received: from [172.16.4.26] (ultra.domain [172.16.4.26] (may be forged)) by zombie.ezone.ru (8.13.2/8.12.11) with ESMTP id j0L7riDa020349; Fri, 21 Jan 2005 10:53:45 +0300 (MSK) (envelope-from mcsi@mcsi.pp.ru) Message-ID: <41F0B4D0.1050504@mcsi.pp.ru> Date: Fri, 21 Jan 2005 10:52:48 +0300 From: Maxim Maximov User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.1) Gecko/20040707 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <41EEAD95.5080706@mcsi.pp.ru> <20050120.120423.94248425.imp@bsdimp.com> In-Reply-To: <20050120.120423.94248425.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@FreeBSD.org Subject: Re: kernel panic (ACPI/fdc/sysctl) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 07:54:03 -0000 M. Warner Losh wrote: > In message: <41EEAD95.5080706@mcsi.pp.ru> > Maxim Maximov writes: > : fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 > : on acpi0 > : device_attach: fdc0 attach returned 6 > > I think that I've fixed this. Please try again. Sorry for the hassle. > Yes, indeed. Your yesterday's patch fixes the problem. Thanks! -- Maxim Maximov From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 09:09:19 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E95CF16A4CE for ; Fri, 21 Jan 2005 09:09:19 +0000 (GMT) Received: from ada.url.com.tw (ada.url.com.tw [210.59.228.108]) by mx1.FreeBSD.org (Postfix) with SMTP id 3BC2743D1D for ; Fri, 21 Jan 2005 09:09:19 +0000 (GMT) (envelope-from lihong@ms93.url.com.tw) Received: (qmail 13837 invoked from network); 21 Jan 2005 09:09:17 -0000 Received: from unknown (HELO phoenix.url.com.tw) ([210.59.228.23]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 21 Jan 2005 09:09:17 -0000 Received: (qmail 24393 invoked from network); 21 Jan 2005 09:09:21 -0000 X-AccFilter: gw2-level 4 #C1#P7#M0#o1#x0 Received: from unknown (HELO localhost.localdomain) ([61.221.58.28]) (envelope-sender ) by ms93.url.com.tw (qmail-ldap-1.03) with SMTP; 21 Jan 2005 17:09:19 +0800 From: Chen Lihong To: freebsd-current@freebsd.org Content-Type: text/plain Date: Fri, 21 Jan 2005 17:09:13 +0800 Message-Id: <1106298553.753.6.camel@OmniBook.accton.com.tw> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: pthread_testcancel() seems always cause core dump X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 09:09:20 -0000 Hi! I cvsuped code few days ago. Many application core dump often. totem, screem and epiphany etc... I use gdb to trace stack all of them are stop at pthread-testcancel(). $ ls *.core screem.core totem.core gdb screem screem.coreGNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. ... ... Loaded symbols for /usr/X11R6/lib/gtk-2.0/2.4.0/filesystems/libgnome-vfs.so Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done.Loaded symbols for /libexec/ld-elf.so.1 #0 0x28e4d22b in pthread_testcancel () from /usr/lib/libpthread.so.1 (gdb) q $ gdb totem totem.core GNU gdb 6.1.1 [FreeBSD] ... ...Loaded symbols for /usr/X11R6/lib/gstreamer-0.8/libgstelements.so Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x28d9822b in pthread_testcancel () from /usr/lib/libpthread.so.1 (gdb) q From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 11:14:19 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F7E016A4CE for ; Fri, 21 Jan 2005 11:14:19 +0000 (GMT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id D329043D49 for ; Fri, 21 Jan 2005 11:14:17 +0000 (GMT) (envelope-from emanuel.strobl@gmx.net) Received: (qmail invoked by alias); 21 Jan 2005 11:14:16 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp022) with SMTP; 21 Jan 2005 12:14:16 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-stable@freebsd.org Date: Fri, 21 Jan 2005 12:14:14 +0100 User-Agent: KMail/1.7.2 References: <1106134006.1132.12.camel@genius2.i.cz> <1106227110.716.11.camel@genius2.i.cz> In-Reply-To: <1106227110.716.11.camel@genius2.i.cz> X-Birthday: 10/06/72 X-CelPhone: +49 173 9967781 X-Tel: +49 89 18947781 X-Country: Germany X-Address: Munich, 80686 X-OS: FreeBSD MIME-Version: 1.0 Content-Disposition: inline Content-Type: Multipart/Mixed; boundary="Boundary-00=_HQO8B7C8ZC4Yjnp" Message-Id: <200501211214.15327.emanuel.strobl@gmx.net> X-Y-GMX-Trusted: 0 cc: bernd@bwct.de cc: Michal Mertl cc: freebsd-current@freebsd.org Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 11:14:19 -0000 --Boundary-00=_HQO8B7C8ZC4Yjnp Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Am Donnerstag, 20. Januar 2005 14:18 schrieb Michal Mertl: > I tested my patch for binary safety on CURRENT yesterday (dialed with > ppp) and didn't notice any problem. > > I'm attaching my patch again because some recipients didn't probably > receive it yesterday. This didn't apply cleanly against my -stable from today. Attached is a cleaned version (#define RSAQ_STATUS_CTS doesn't exist in -stable uplcom.c) for -stable which compiles for me. > > Michal --Boundary-00=_HQO8B7C8ZC4Yjnp Content-Type: text/x-diff; charset="iso-8859-15"; name="uplcom.c.2303x.patch" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="uplcom.c.2303x.patch" --- sys/dev/usb/uplcom.c Fri Jan 21 10:49:09 2005 +++ sys/dev/usb/uplcom.c Fri Jan 21 11:01:33 2005 @@ -96,10 +96,13 @@ #include #include +#include + #include #include #include +#include #include #include "usbdevs.h" #include @@ -112,29 +115,34 @@ SYSCTL_INT(_hw_usb_uplcom, OID_AUTO, debug, CTLFLAG_RW, &uplcomdebug, 0, "uplcom debug level"); -#define DPRINTFN(n, x) do { \ +#define DPRINTFN(n, x) do { \ if (uplcomdebug > (n)) \ logprintf x; \ } while (0) #else -#define DPRINTFN(n, x) +#define DPRINTFN(n, x) #endif -#define DPRINTF(x) DPRINTFN(0, x) +#define DPRINTF(x) DPRINTFN(0, x) -#define UPLCOM_MODVER 1 /* module version */ +#define UPLCOM_MODVER 1 /* module version */ #define UPLCOM_CONFIG_INDEX 0 #define UPLCOM_IFACE_INDEX 0 #define UPLCOM_SECOND_IFACE_INDEX 1 #ifndef UPLCOM_INTR_INTERVAL -#define UPLCOM_INTR_INTERVAL 100 /* ms */ +#define UPLCOM_INTR_INTERVAL 100 /* ms */ #endif #define UPLCOM_SET_REQUEST 0x01 #define UPLCOM_SET_CRTSCTS 0x41 -#define RSAQ_STATUS_DSR 0x02 -#define RSAQ_STATUS_DCD 0x01 +#define UPLCOM_SET_CRTSCTS_2303X 0x61 +#define RSAQ_STATUS_CTS 0x80 +#define RSAQ_STATUS_DSR 0x02 +#define RSAQ_STATUS_DCD 0x01 + +#define CHIPTYPE_PL2303 0 +#define CHIPTYPE_PL2303X 1 struct uplcom_softc { struct ucom_softc sc_ucom; @@ -154,14 +162,15 @@ u_char sc_lsr; /* Local status register */ u_char sc_msr; /* uplcom status register */ + int sc_chiptype; }; /* * These are the maximum number of bytes transferred per frame. * The output buffer size cannot be increased due to the size encoding. */ -#define UPLCOMIBUFSIZE 256 -#define UPLCOMOBUFSIZE 256 +#define UPLCOMIBUFSIZE 256 +#define UPLCOMOBUFSIZE 256 Static usbd_status uplcom_reset(struct uplcom_softc *); Static usbd_status uplcom_set_line_coding(struct uplcom_softc *, @@ -297,6 +306,7 @@ char *devinfo; const char *devname; usbd_status err; + usb_device_descriptor_t *udd; int i; devinfo = malloc(1024, M_USBDEV, M_WAITOK); @@ -372,7 +382,14 @@ sc->sc_isize = UGETW(ed->wMaxPacketSize); } } - + udd = &dev->ddesc; + if (UGETW(udd->bcdDevice) == 0x300) { + DPRINTF(("chiptype 2303X\n")); + sc->sc_chiptype = CHIPTYPE_PL2303X; + } else { + DPRINTF(("chiptype 2303\n")); + sc->sc_chiptype = CHIPTYPE_PL2303; + } if (sc->sc_intr_number == -1) { printf("%s: Could not find interrupt in\n", USBDEVNAME(ucom->sc_dev)); @@ -615,7 +632,10 @@ req.bmRequestType = UT_WRITE_VENDOR_DEVICE; req.bRequest = UPLCOM_SET_REQUEST; USETW(req.wValue, 0); - USETW(req.wIndex, UPLCOM_SET_CRTSCTS); + if (sc->sc_chiptype == CHIPTYPE_PL2303X) + USETW(req.wIndex, UPLCOM_SET_CRTSCTS_2303X); + else + USETW(req.wIndex, UPLCOM_SET_CRTSCTS); USETW(req.wLength, 0); err = usbd_do_request(sc->sc_ucom.sc_udev, &req, 0); @@ -711,6 +731,43 @@ return (0); } +#define DO_REQ(type, reQ, wVal, wInd) do { \ + req.bmRequestType = (type); \ + req.bRequest = (reQ); \ + USETW(req.wValue, (wVal)); \ + USETW(req.wIndex, (wInd)); \ + USETW(req.wLength, 0); \ + err = usbd_do_request(sc->sc_ucom.sc_udev, &req, 0); \ + if (err) { /* XXX - shouldn't happen */ \ + printf("%s: uplcom_initPL2303X_%d: %s\n", \ + USBDEVNAME(sc->sc_ucom.sc_dev), i++, usbd_errstr(err)); \ + return (EIO); \ + } \ + } while (0); + +Static usbd_status +uplcom_initPL2303X(struct uplcom_softc *sc) +{ + usb_device_request_t req; + usbd_status err; + int i = 0; + + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0x40, 0x1, 0x0404, 0); + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0xc0, 0x1, 0x8383, 0); + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0x40, 0x1, 0x0404, 1); + DO_REQ(0xc0, 0x1, 0x8484, 0); + DO_REQ(0xc0, 0x1, 0x8383, 0); + DO_REQ(0x40, 0x1, 0x0000, 1); + DO_REQ(0x40, 0x1, 0x0001, 0); + DO_REQ(0x40, 0x1, 0x0002, 0x44); + return (0); +} + +#undef DO_REQ + Static int uplcom_open(void *addr, int portno) { @@ -741,7 +798,8 @@ return (EIO); } } - + if (sc->sc_chiptype == CHIPTYPE_PL2303X) + return (uplcom_initPL2303X(sc)); return (0); } --Boundary-00=_HQO8B7C8ZC4Yjnp-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 12:19:41 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC13D16A4CE for ; Fri, 21 Jan 2005 12:19:41 +0000 (GMT) Received: from lakermmtao07.cox.net (lakermmtao07.cox.net [68.230.240.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DF6A43D46 for ; Fri, 21 Jan 2005 12:19:41 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.14.122.164]) by lakermmtao07.cox.net (InterMail vM.6.01.03.04 201-2131-111-106-20040729) with ESMTP id <20050121121940.SEJG20686.lakermmtao07.cox.net@dolphin.local.net> for ; Fri, 21 Jan 2005 07:19:40 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with ESMTP id j0LCJdHD000834 for ; Fri, 21 Jan 2005 06:19:40 -0600 (CST) (envelope-from conrads@cox.net) Date: Fri, 21 Jan 2005 06:19:34 -0600 From: "Conrad J. Sabatier" To: freebsd-current@freebsd.org Message-ID: <20050121061934.31df999a@dolphin.local.net> X-Mailer: Sylpheed-Claws 0.9.13 (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: ffs-related panics fixed yet? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 12:19:41 -0000 I've been reluctant to try upgrading for the last week or so, due to the ffs-related panics we were seeing. Have these been taken care of yet? -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 12:22:36 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5639B16A4CE for ; Fri, 21 Jan 2005 12:22:36 +0000 (GMT) Received: from critter.freebsd.dk (f170.freebsd.dk [212.242.86.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AAD243D53 for ; Fri, 21 Jan 2005 12:22:35 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id j0LCMSJC021696; Fri, 21 Jan 2005 13:22:28 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Conrad J. Sabatier" From: "Poul-Henning Kamp" In-Reply-To: Your message of "Fri, 21 Jan 2005 06:19:34 CST." <20050121061934.31df999a@dolphin.local.net> Date: Fri, 21 Jan 2005 13:22:28 +0100 Message-ID: <21695.1106310148@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-current@freebsd.org Subject: Re: ffs-related panics fixed yet? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 12:22:36 -0000 In message <20050121061934.31df999a@dolphin.local.net>, "Conrad J. Sabatier" wr ites: >I've been reluctant to try upgrading for the last week or so, due to the >ffs-related panics we were seeing. Have these been taken care of yet? At least the major source has. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 22:45:02 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C095316A4CE for ; Thu, 20 Jan 2005 22:45:02 +0000 (GMT) Received: from mail3.dreamscape.com (mail3.dreamscape.com [206.64.128.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DBA743D45 for ; Thu, 20 Jan 2005 22:45:02 +0000 (GMT) (envelope-from krentel@dreamscape.com) Received: from blue.mwk.domain (syr-mdm-04-216-171-177-130.dreamscape.com [216.171.177.130]) by mail3.dreamscape.com (8.12.9/8.12.9) with ESMTP id j0KMisVL014023; Thu, 20 Jan 2005 17:44:57 -0500 (EST) Received: from blue.mwk.domain (localhost [127.0.0.1]) by blue.mwk.domain (8.12.9p2/8.12.9) with ESMTP id j0KMlvJH032907; Thu, 20 Jan 2005 17:47:58 -0500 (EST) (envelope-from krentel@blue.mwk.domain) Message-Id: <200501202247.j0KMlvJH032907@blue.mwk.domain> To: Kris Kennaway , freebsd-current@freebsd.org In-Reply-To: Your message of "Tue, 18 Jan 2005 23:02:20 CST." <20050119050220.GU3194@noel.cs.rice.edu> Date: Thu, 20 Jan 2005 17:47:57 -0500 From: "Mark W. Krentel" X-Mailman-Approved-At: Fri, 21 Jan 2005 12:34:44 +0000 cc: Alan Cox Subject: Re: fstat triggered INVARIANTS panic in memrw() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 22:45:02 -0000 First, let me check that your panic requires three things to trigger: (1) heavy load, in your case ports building, (2) INVARIANTS compiled into the kernel, and (3) many calls to fstat(1). Is that right? Also, you're running 6.0-current on an x86 SMP machine? Can you bound the problem between two dates, that is, you compiled kernel/world on date X and it was ok, and updated on date Y and it panicked? Are you changing the default kernel address space (3 Gig user and 1 Gig kernel) via KVA_PAGES? Following Alan's diagnosis, I added some printf()s to check the arguments to kernacc() and vm_map_check_protection(). I didn't get a panic, but I can confirm that kernacc() is being called with arguments that constitute address wrap. My tests were on a single-CPU P3-933. I ran buildworld along with a loop of fstat(1)s, and the address wrap happened within seconds. It required both (1) and (3) above, INVARIANTS may be a red herring, I'm not sure. How long did it take for your machine to panic? Mine didn't panic, but maybe I didn't run the test long enough, or maybe I don't have enough open files. Anyway, try this patch, see if it avoids the panic for you. --Mark Index: vm_glue.c =================================================================== RCS file: /data/ncvs/src/sys/vm/vm_glue.c,v retrieving revision 1.209 diff -u -r1.209 vm_glue.c --- vm_glue.c 7 Jan 2005 02:29:27 -0000 1.209 +++ vm_glue.c 20 Jan 2005 22:01:21 -0000 @@ -133,6 +133,11 @@ KASSERT((rw & ~VM_PROT_ALL) == 0, ("illegal ``rw'' argument to kernacc (%x)\n", rw)); + + if ((vm_offset_t)addr + len > kernel_map->max_offset || + (vm_offset_t)addr + len < (vm_offset_t)addr) + return (FALSE); + prot = rw; saddr = trunc_page((vm_offset_t)addr); eaddr = round_page((vm_offset_t)addr + len); From owner-freebsd-current@FreeBSD.ORG Thu Jan 20 23:18:20 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CD5E16A4CE; Thu, 20 Jan 2005 23:18:20 +0000 (GMT) Received: from mail.dt.e-technik.uni-dortmund.de (mail.dt.e-technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id A770B43D2D; Thu, 20 Jan 2005 23:18:19 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from localhost (localhost [127.0.0.1])BDE4A44235; Fri, 21 Jan 2005 00:18:18 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 19748-02; Fri, 21 Jan 2005 00:18:13 +0100 (CET) Received: from m2a2.dyndns.org (pD9FFBDED.dip.t-dialin.net [217.255.189.237]) 2FF4844234; Fri, 21 Jan 2005 00:18:10 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 969B7790A3; Fri, 21 Jan 2005 00:18:08 +0100 (CET) Received: from merlin.emma.line.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 26071-08; Fri, 21 Jan 2005 00:18:07 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id 9DEED79104; Fri, 21 Jan 2005 00:18:07 +0100 (CET) From: Matthias Andree To: Andrey Chernov In-Reply-To: <20050120224017.GA71573@nagual.pp.ru> (Andrey Chernov's message of "Fri, 21 Jan 2005 01:40:18 +0300") References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120222137.GE30862@uriah.heep.sax.de> <20050120224017.GA71573@nagual.pp.ru> Date: Fri, 21 Jan 2005 00:18:07 +0100 Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at dt.e-technik.uni-dortmund.de X-Mailman-Approved-At: Fri, 21 Jan 2005 12:34:44 +0000 cc: Joerg Wunsch cc: current@FreeBSD.ORG cc: bde@FreeBSD.ORG Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 23:18:20 -0000 Andrey Chernov writes: > This is just their intehtions explanation, not excuse. If several > standards are in contradiction, POSIX vote is final. It may surprise you, > but it covers and changes lots of cases comparing to minimalistic C > standard. Such additions/changes are specially marked with different color > (gray). I do not have a place of discovery handy, but wasn't POSIX explicitly deferring in to the C standard and giving it precedence for any conflicts between the C standard library and POSIX? -- Matthias Andree From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 10:15:43 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41AF016A4CE; Fri, 21 Jan 2005 10:15:43 +0000 (GMT) Received: from mail.dt.e-technik.uni-dortmund.de (mail.dt.e-technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD10D43D1F; Fri, 21 Jan 2005 10:15:42 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from localhost (localhost [127.0.0.1])AE51C44234; Fri, 21 Jan 2005 11:15:41 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 17151-02; Fri, 21 Jan 2005 11:15:36 +0100 (CET) Received: from m2a2.dyndns.org (p508EFC32.dip.t-dialin.net [80.142.252.50]) 5FC2144232; Fri, 21 Jan 2005 11:15:36 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 3D2C1774D3; Fri, 21 Jan 2005 11:15:35 +0100 (CET) Received: from merlin.emma.line.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 14537-01-2; Fri, 21 Jan 2005 11:15:34 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id 4F0A277751; Fri, 21 Jan 2005 11:15:34 +0100 (CET) From: Matthias Andree To: Andrey Chernov In-Reply-To: <20050121000916.GA73235@nagual.pp.ru> (Andrey Chernov's message of "Fri, 21 Jan 2005 03:09:17 +0300") References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120222137.GE30862@uriah.heep.sax.de> <20050121000916.GA73235@nagual.pp.ru> Date: Fri, 21 Jan 2005 11:15:34 +0100 Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at dt.e-technik.uni-dortmund.de X-Mailman-Approved-At: Fri, 21 Jan 2005 12:34:44 +0000 cc: Joerg Wunsch cc: current@FreeBSD.ORG cc: bde@FreeBSD.ORG Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 10:15:43 -0000 Andrey Chernov writes: > If you disagree that FreeBSD must follow POSIX (as united and superseded > things among all several other standards related to the subject), this > should be CORE decision. Because in the past POSIX word was final thing > for FreeBSD implemetations, not C, not SUS. Is not SUS v3 == "POSIX" 2001 edition (IEEE Std 1003.1-2001)? -- Matthias Andree From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 12:49:39 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C39816A4CF for ; Fri, 21 Jan 2005 12:49:39 +0000 (GMT) Received: from lakermmtao01.cox.net (lakermmtao01.cox.net [68.230.240.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB39743D4C for ; Fri, 21 Jan 2005 12:49:38 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.14.122.164]) by lakermmtao01.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP <20050121124938.DPGF27357.lakermmtao01.cox.net@dolphin.local.net>; Fri, 21 Jan 2005 07:49:38 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with ESMTP id j0LCnbqd070728; Fri, 21 Jan 2005 06:49:37 -0600 (CST) (envelope-from conrads@cox.net) Date: Fri, 21 Jan 2005 06:49:32 -0600 From: "Conrad J. Sabatier" To: "Poul-Henning Kamp" Message-ID: <20050121064932.32c6aa5d@dolphin.local.net> In-Reply-To: <21695.1106310148@critter.freebsd.dk> References: <20050121061934.31df999a@dolphin.local.net> <21695.1106310148@critter.freebsd.dk> X-Mailer: Sylpheed-Claws 1.0.0 (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: ffs-related panics fixed yet? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 12:49:39 -0000 On Fri, 21 Jan 2005 13:22:28 +0100, "Poul-Henning Kamp" wrote: > In message <20050121061934.31df999a@dolphin.local.net>, "Conrad J. > Sabatier" wr ites: > > >I've been reluctant to try upgrading for the last week or so, due to > >the ffs-related panics we were seeing. Have these been taken care of > >yet? > > At least the major source has. Ah, good. Guess I'll dip my toe back in the water again. :-) Thanks. -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 12:52:47 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 551EF16A4CE for ; Fri, 21 Jan 2005 12:52:47 +0000 (GMT) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.FreeBSD.org (Postfix) with SMTP id BDF9E43D41 for ; Fri, 21 Jan 2005 12:52:46 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 23529 invoked from network); 21 Jan 2005 12:52:45 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 21 Jan 2005 12:52:45 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id j0LCqihP039271 for ; Fri, 21 Jan 2005 13:52:44 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id j0LCqikV039270 for current@freebsd.org; Fri, 21 Jan 2005 13:52:44 +0100 (CET) (envelope-from pho) Date: Fri, 21 Jan 2005 13:52:44 +0100 From: Peter Holm To: current@freebsd.org Message-ID: <20050121125244.GA39251@peter.osted.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Deadlock (swap related?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 12:52:47 -0000 With GENERIC HEAD from Jan 18 19:27 UTC I got a freeze. Details at http://www.holm.cc/stress/log/cons110.html -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 12:58:05 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3288516A4CE; Fri, 21 Jan 2005 12:58:05 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66D4E43D58; Fri, 21 Jan 2005 12:58:04 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id j0LCw3xU095533; Fri, 21 Jan 2005 15:58:03 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id j0LCw26m095532; Fri, 21 Jan 2005 15:58:02 +0300 (MSK) (envelope-from ache) Date: Fri, 21 Jan 2005 15:58:02 +0300 From: Andrey Chernov To: Matthias Andree Message-ID: <20050121125801.GA94152@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Matthias Andree , Joerg Wunsch , current@FreeBSD.ORG, bde@FreeBSD.ORG References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120222137.GE30862@uriah.heep.sax.de> <20050121000916.GA73235@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.8; VDF: 6.29.0.73; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [0.0.0.0]); Fri, 21 Jan 2005 15:58:03 +0300 (MSK) cc: Joerg Wunsch cc: current@FreeBSD.ORG cc: bde@FreeBSD.ORG Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 12:58:05 -0000 On Fri, Jan 21, 2005 at 11:15:34AM +0100, Matthias Andree wrote: > Is not SUS v3 == "POSIX" 2001 edition (IEEE Std 1003.1-2001)? Yes, with two technical corrigendum, as I read their announce. But Joerg mention older SUSv2 and I mean it too. As I just found, they makes SUSv3 searcheable and browseable in the HTML form. All that needed is just registration at http://www.unix.org/single_unix_specification/ BTW, back to the subj, their text about strtol() is equal to POSIX, so both POSIX and SUSv3 finally agrees. Back yo your question about contradictions, I found explaining quote: "Extension to the ISO C standard The functionality described is an extension to the ISO C standard. Application writers may make use of an extension as it is supported on all IEEE Std 1003.1-2001-conforming systems. With each function or header from the ISO C standard, a statement to the effect that ``any conflict is unintentional'' is included. That is intended to refer to a direct conflict. IEEE Std 1003.1-2001 acts in part as a profile of the ISO C standard, and it may choose to further constrain behaviors allowed to vary by the ISO C standard. Such limitations are not considered conflicts. Where additional semantics apply to a function or header, the material is identified by use of the CX margin legend." -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 14:50:11 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96FED16A4CE; Fri, 21 Jan 2005 14:50:11 +0000 (GMT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id E07AA43D46; Fri, 21 Jan 2005 14:50:10 +0000 (GMT) (envelope-from j@uriah.heep.sax.de) Received: from sax.sax.de (localhost [127.0.0.1]) by sax.sax.de (8.12.10/8.12.10) with ESMTP id j0LEo9Yu007200; Fri, 21 Jan 2005 15:50:09 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.12.10/8.12.10/Submit) with UUCP id j0LEo93a007199; Fri, 21 Jan 2005 15:50:09 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: from uriah.heep.sax.de (localhost [127.0.0.1]) by uriah.heep.sax.de (8.13.1/8.13.1) with ESMTP id j0LEjXOg059576; Fri, 21 Jan 2005 15:45:33 +0100 (MET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.13.1/8.13.1/Submit) id j0LEjXHZ059575; Fri, 21 Jan 2005 15:45:33 +0100 (MET) (envelope-from j) Resent-Message-Id: <200501211445.j0LEjXHZ059575@uriah.heep.sax.de> Date: Fri, 21 Jan 2005 15:44:28 +0100 From: Joerg Wunsch To: current@freebsd.org Message-ID: <20050121144428.GK30862@uriah.heep.sax.de> References: <20050120223232.GF30862@uriah.heep.sax.de> <20050120224753.GB71573@nagual.pp.ru> <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120222137.GE30862@uriah.heep.sax.de> <20050121000916.GA73235@nagual.pp.ru> <20050121125801.GA94152@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050120222137.GE30862@uriah.heep.sax.de> <20050120224753.GB71573@nagual.pp.ru> <20050121125801.GA94152@nagual.pp.ru> User-Agent: Mutt/1.4.2.1i X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-GPG-Fingerprint: 5E84 F980 C3CA FD4B B584 1070 F48C A81B 69A8 5873 Resent-From: j@uriah.heep.sax.de Resent-Date: Fri, 21 Jan 2005 15:45:33 +0100 Resent-To: current@freebsd.org, bde@freebsd.org, ache@nagual.pp.ru X-Spam-Status: No, score=-2.6 required=7.5 tests=BAYES_00 autolearn=ham version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on uriah.heep.sax.de cc: Andrey Chernov cc: bde@freebsd.org Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joerg Wunsch List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 14:50:11 -0000 As Joerg Wunsch wrote: > As a demonstration, consider this test program: ... > Below are the results for Solaris 8, FreeBSD 5, Linux 2.x, and HP-UX > 10.20. ... > It's quite obvious that any other system differs from FreeBSD here. > (OK, HP-UX doesn't throw EINVAL at all, even for clearly > inconvertible strings. But then, it's a pretty old system, more > than ten years.) Btw., I have re-checked HP-UX once more. They do set errno to EINVAL in the case of an unacceptable value for base, as required by Posix/SUSP. They only never set it to EINVAL for a conversion error. So they are *fully* compliant with Posix/SUSP. Hmm, maybe not. For "0x", they do not set endptr to point to the `x', so they're still in violation. Seems they are using the old BSD code which had the same bug. But that's another matter. Btw., Solaris never sets errno to EINVAL except for the unacceptable base case (where SUSP requires it). This is the best demonstration that the entire ``may set to EINVAL'' thing in SUSP is pointless crap, sorry. As no application developer can rely on it, they could as well have left this option completely out. If someone wants to use strot() to verify their input data, they'd be best to follow the advise from the FreeBSD manpage: ``(Thus, if *nptr is not `\0' but **endptr is `\0' on return, the entire string was valid.)'' This is the only reliable method. (OK, if you care, you can then check for errno being set to ERANGE in order to detect an under-/overflow situation.) As Andrey Chernov wrote: > This is just your speculation about what "expected form" is. But > POSIX clearly says, what expected form is: > "If the value of base is 0, the expected form of the subject > sequence is ^^^^^^^^^^^^^^^^^^^ that of a decimal constant, octal > constant, or hexadecimal constant, any of which may be preceded by a > .+. or .-. sign." > No CONSTANT found in just +- case. OK, I agree on this. I still find the wording of the standard ambiguous, as some forms of conversion errors (the empty string) are explicitly mentioned, while other forms (a single sign) have to be derived, but I agree. It of course makes most sense that way anyway, I've only been surprised about the mentioned ambiguity in the standard. > > Is not SUS v3 == "POSIX" 2001 edition (IEEE Std 1003.1-2001)? > Yes, with two technical corrigendum, as I read their announce. But > Joerg mention older SUSv2 and I mean it too. I didn't have SUSPv3 handy, so I referred to v2 (where I have been registering years ago). Thanks for the v3 pointer, that might be handy as well. The question about whether the C standard allows setting errno to EINVAL was merely out of curiosity. I still think that the C standard forbids it, but I do find that stupid as well, and never meant to change that part of the FreeBSD behaviour. I agree that fixing the 0x problem would fix the part were FreeBSD currently violates the standard. However, as the majority of other SUSP compliant systems seem to prefer to not set errno in the empty string case, I suggest we follow that instead of our current behaviour. Maybe we should even follow the Solaris behaviour, and not mess with EINVAL at all except where required by SUSP. See above, EINVAL is completely pointless for error checking as it is not portable. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 15:10:04 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE4A116A4CE; Fri, 21 Jan 2005 15:10:04 +0000 (GMT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 366C843D2D; Fri, 21 Jan 2005 15:10:04 +0000 (GMT) (envelope-from j@uriah.heep.sax.de) Received: from sax.sax.de (localhost [127.0.0.1]) by sax.sax.de (8.12.10/8.12.10) with ESMTP id j0LFA3Yu008036; Fri, 21 Jan 2005 16:10:03 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.12.10/8.12.10/Submit) with UUCP id j0LFA3nQ008035; Fri, 21 Jan 2005 16:10:03 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: from uriah.heep.sax.de (localhost [127.0.0.1]) by uriah.heep.sax.de (8.13.1/8.13.1) with ESMTP id j0LF79ur060200; Fri, 21 Jan 2005 16:07:09 +0100 (MET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.13.1/8.13.1/Submit) id j0LF79Ww060199; Fri, 21 Jan 2005 16:07:09 +0100 (MET) (envelope-from j) Date: Fri, 21 Jan 2005 16:07:09 +0100 From: Joerg Wunsch To: current@FreeBSD.ORG Message-ID: <20050121150709.GA60180@uriah.heep.sax.de> References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120215807.GA70629@nagual.pp.ru> <20050120221154.GC70629@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050120221154.GC70629@nagual.pp.ru> User-Agent: Mutt/1.4.2.1i X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-GPG-Fingerprint: 5E84 F980 C3CA FD4B B584 1070 F48C A81B 69A8 5873 X-Spam-Status: No, score=-2.6 required=7.5 tests=AWL,BAYES_00 autolearn=ham version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on uriah.heep.sax.de cc: Andrey Chernov cc: bde@FreeBSD.ORG Subject: Re: [patch] Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joerg Wunsch List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 15:10:05 -0000 As Andrey Chernov wrote: > Here is untested patch to fix the problem: Apart of the stylistic problems mentioned by Bruce: uriah # make cc -O -pipe -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/i386 -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6 -I/usr/obj/usr/src/lib/libc -DPOSIX_MISTAKE -I/usr/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -DHESIOD -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/lib/libc/stdlib/strtol.c /usr/src/lib/libc/stdlib/strtol.c: In function `strtol': /usr/src/lib/libc/stdlib/strtol.c:81: warning: suggest parentheses around && within || /usr/src/lib/libc/stdlib/strtol.c:82: warning: suggest parentheses around && within || *** Error code 1 -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 15:18:00 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67BC116A4CE for ; Fri, 21 Jan 2005 15:18:00 +0000 (GMT) Received: from postfix4-2.free.fr (postfix4-2.free.fr [213.228.0.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF79E43D58 for ; Fri, 21 Jan 2005 15:17:59 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix4-2.free.fr (Postfix) with ESMTP id B90652A8056 for ; Fri, 21 Jan 2005 16:17:58 +0100 (CET) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id DB85B408E; Fri, 21 Jan 2005 16:17:48 +0100 (CET) Date: Fri, 21 Jan 2005 16:17:47 +0100 From: Jeremie Le Hen To: freebsd-current@freebsd.org Message-ID: <20050121151747.GA36660@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: Cannot install kernel as user X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 15:18:00 -0000 Hi, my laptop is a very slow beast but this is the only computer I can actually run -CURRENT on. In order to parallelize task, when my laptop is fsck'ing after a panic, I use a collegue's computer on which I have a shell to build the new kernel. Everything works quite well, except that when I install the kernel, install(8) will stop on chown(2) : %%% propane:Z6PO$ make KERNEL=kernel.test DESTDIR=$HOME/export install [...] mkdir -p /home/tataz/export/boot/kernel.test install -p -m 555 -o root -g wheel kernel /home/tataz/export/boot/kernel.test install: /home/tataz/export/boot/kernel.test/kernel: chown/chgrp: Operation not permitted *** Error code 71 Stop in /usr/home/tataz/FreeBSD/CURRENT/src/sys/i386/compile/Z6PO. %%% I thought about adding a flag such as NO_INSTALLCHOWN in both kern.post.mk and kmod.mk. What do you think of the idea ? I saw there are KMODOWN and KMODGRP in kmod.mk, but it seems there is no similar facility in kern.post.mk. Maybe it would be worth having KERNOWN and KERNGRP as well. I can submit a patch if asked. Regards, -- Jeremie Le Hen jeremie@le-hen.org From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 16:00:50 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66D4D16A4CE for ; Fri, 21 Jan 2005 16:00:50 +0000 (GMT) Received: from mailserv1.neuroflux.com (ns2.neuroflux.com [204.228.228.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1495C43D4C for ; Fri, 21 Jan 2005 16:00:50 +0000 (GMT) (envelope-from ryans@gamersimpact.com) Received: (qmail 37152 invoked by uid 89); 21 Jan 2005 15:59:35 -0000 Received: from unknown (HELO www2.neuroflux.com) (127.0.0.1) by localhost with SMTP; 21 Jan 2005 15:59:35 -0000 Received: from 208.4.77.66 (SquirrelMail authenticated user ryans@gamersimpact.com); by www2.neuroflux.com with HTTP; Fri, 21 Jan 2005 08:59:35 -0700 (MST) Message-ID: <50158.208.4.77.66.1106323175.squirrel@208.4.77.66> In-Reply-To: <20050121151747.GA36660@obiwan.tataz.chchile.org> References: <20050121151747.GA36660@obiwan.tataz.chchile.org> Date: Fri, 21 Jan 2005 08:59:35 -0700 (MST) From: "Ryan Sommers" To: "Jeremie Le Hen" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal cc: freebsd-current@freebsd.org Subject: Re: Cannot install kernel as user X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 16:00:50 -0000 Jeremie Le Hen said: > Hi, > > my laptop is a very slow beast but this is the only computer I can > actually run -CURRENT on. In order to parallelize task, when my laptop > is fsck'ing after a panic, I use a collegue's computer on which I have > a shell to build the new kernel. Everything works quite well, except > that when I install the kernel, install(8) will stop on chown(2) : > > %%% > propane:Z6PO$ make KERNEL=kernel.test DESTDIR=$HOME/export install > [...] > mkdir -p /home/tataz/export/boot/kernel.test > install -p -m 555 -o root -g wheel kernel > /home/tataz/export/boot/kernel.test > install: /home/tataz/export/boot/kernel.test/kernel: chown/chgrp: > Operation not permitted > *** Error code 71 > > Stop in /usr/home/tataz/FreeBSD/CURRENT/src/sys/i386/compile/Z6PO. > %%% > > I thought about adding a flag such as NO_INSTALLCHOWN in both > kern.post.mk and kmod.mk. What do you think of the idea ? > > I saw there are KMODOWN and KMODGRP in kmod.mk, but it seems there is > no similar facility in kern.post.mk. Maybe it would be worth having > KERNOWN and KERNGRP as well. > > I can submit a patch if asked. I'm trying to think where this would be useful outside your particular situation. I'm not sure there is a lot of use. The official way to do what you are looking to do is to mount it the other way. On the build machine export the src/obj directories and mount them on the target machine. Then execute your make install from the target machine. Otherwise you run into problems like you are running into. Especially if you're running an install as a non-root user. -- Ryan Sommers ryans@gamersimpact.com From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 16:01:04 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 910B116A4CE for ; Fri, 21 Jan 2005 16:01:04 +0000 (GMT) Received: from osi2.gua.net (osi2.gua.net [205.161.188.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD4A343D55 for ; Fri, 21 Jan 2005 16:01:03 +0000 (GMT) (envelope-from kuuse@redantigua.com) Received: (qmail 58102 invoked by uid 89); 21 Jan 2005 16:01:03 -0000 Received: from kuuse@redantigua.com by osi2 by uid 89 with qmail-scanner-1.20 ( Clear:RC:0(205.161.188.16):. Processed in 0.137862 secs); 21 Jan 2005 16:01:03 -0000 Received: from unknown (HELO widserver1) (kuuse@osint.net@205.161.188.16) by 0 with SMTP; 21 Jan 2005 16:01:02 -0000 Message-ID: <000a01c4ffd2$86d5cc70$10bca1cd@widserver1> From: "Johan Kuuse - Red Antigua" To: Date: Fri, 21 Jan 2005 10:01:52 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 Subject: Problem with crt1.o and init tls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 16:01:04 -0000 Hi, I'm trying to upgrade from 5.2.1 to 6.0 current. # make buildworld # make buildkernel # make installkernel # reboot all went fine. uname -a now shows FreeBSD 6.0-CURRENT ... With # mergemaster -p # make installworld the problems started. When I try to start over again with # chflags -R noschg /usr/obj/usr # rm -rf /usr/obj/usr # cd /usr/src # make cleandir -DALWAYS_CHECK_MAKE (as indicated at the bottom of http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html 19.4.16.6. What do I do if something goes wrong?) 'make cleandir' casues the following error message: /usr/lib/crt1.o: In function '_start': /usr/lib/crt1.o(.text+0x64): undefined reference to '_init_tls' *** Error code 1 Stop in /usr/src/usr.bin/make *** Error code 1 Stop in /usr/src *** Error code 1 Stop in /usr/src If I try # make buildworld the error message is the same (undefined reference to '_init_tls') If I omit the flag -DALWAYS_CHECK_MAKE the error message from 'make cleandir' is: +for: not found *** Error code 127 Stop in /usr/src *** Error 1 Stop in /usr/src I would be really grateful if someone could give a hint. Best Regards, Johan Kuuse kuuse@redantigua.com From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 16:11:11 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93DB316A4CE for ; Fri, 21 Jan 2005 16:11:11 +0000 (GMT) Received: from critter.freebsd.dk (f170.freebsd.dk [212.242.86.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3BD243D54 for ; Fri, 21 Jan 2005 16:11:10 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id j0LGB9F7030925 for ; Fri, 21 Jan 2005 17:11:09 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org From: Poul-Henning Kamp Date: Fri, 21 Jan 2005 17:11:09 +0100 Message-ID: <30924.1106323869@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Subject: Anybody involved with ISO C standardization ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 16:11:11 -0000 I just read another brain-dead proposal for a new timeformat which appearantly is in the ISO C queue and I would really like if we can avoid having another damn mistake in that area. (http://david.tribble.com/text/c0xlongtime.html) If we have anybody who's actively involved in the ISO C standardization who are willing to push and champion a a proposal that makes sense then I would love to hear from them. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 16:23:39 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 415F316A4CE for ; Fri, 21 Jan 2005 16:23:39 +0000 (GMT) Received: from mailserv1.neuroflux.com (ns2.neuroflux.com [204.228.228.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id E78D043D2F for ; Fri, 21 Jan 2005 16:23:38 +0000 (GMT) (envelope-from ryans@gamersimpact.com) Received: (qmail 40749 invoked by uid 89); 21 Jan 2005 16:22:24 -0000 Received: from unknown (HELO www2.neuroflux.com) (127.0.0.1) by localhost with SMTP; 21 Jan 2005 16:22:24 -0000 Received: from 208.4.77.66 (SquirrelMail authenticated user ryans@gamersimpact.com); by www2.neuroflux.com with HTTP; Fri, 21 Jan 2005 09:22:24 -0700 (MST) Message-ID: <50177.208.4.77.66.1106324544.squirrel@208.4.77.66> In-Reply-To: <000a01c4ffd2$86d5cc70$10bca1cd@widserver1> References: <000a01c4ffd2$86d5cc70$10bca1cd@widserver1> Date: Fri, 21 Jan 2005 09:22:24 -0700 (MST) From: "Ryan Sommers" To: "Johan Kuuse - Red Antigua" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal cc: current@freebsd.org Subject: Re: Problem with crt1.o and init tls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 16:23:39 -0000 Johan Kuuse - Red Antigua said: > Hi, > > I'm trying to upgrade from 5.2.1 to 6.0 current. > > # make buildworld > # make buildkernel > # make installkernel > # reboot > > all went fine. > > uname -a now shows > FreeBSD 6.0-CURRENT ... > > With > # mergemaster -p > # make installworld > the problems started. What problems? At this point, removing your object files might have been a bad idea. Your kernel and world are out of sync and trying to build a new world with an out of sync userland might be asking for disaster. -- Ryan Sommers ryans@gamersimpact.com From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 16:31:37 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD3EF16A4CE for ; Fri, 21 Jan 2005 16:31:37 +0000 (GMT) Received: from postfix3-1.free.fr (postfix3-1.free.fr [213.228.0.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id A007C43D2F for ; Fri, 21 Jan 2005 16:31:37 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix3-1.free.fr (Postfix) with ESMTP id DA9A91734E9; Fri, 21 Jan 2005 17:31:35 +0100 (CET) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 8E43E407C; Fri, 21 Jan 2005 17:31:26 +0100 (CET) Date: Fri, 21 Jan 2005 17:31:25 +0100 From: Jeremie Le Hen To: Ryan Sommers Message-ID: <20050121163125.GB36660@obiwan.tataz.chchile.org> References: <20050121151747.GA36660@obiwan.tataz.chchile.org> <50158.208.4.77.66.1106323175.squirrel@208.4.77.66> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50158.208.4.77.66.1106323175.squirrel@208.4.77.66> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org cc: Jeremie Le Hen Subject: Re: Cannot install kernel as user X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 16:31:38 -0000 > I'm trying to think where this would be useful outside your particular > situation. I'm not sure there is a lot of use. > > The official way to do what you are looking to do is to mount it the other > way. On the build machine export the src/obj directories and mount them on > the target machine. Then execute your make install from the target > machine. Otherwise you run into problems like you are running into. > Especially if you're running an install as a non-root user. Sounds good indeed. Thanks. -- Jeremie Le Hen jeremie@le-hen.org From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 16:32:25 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB00816A4CE; Fri, 21 Jan 2005 16:32:25 +0000 (GMT) Received: from ss.eunet.cz (ss.eunet.cz [193.85.228.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id C777443D41; Fri, 21 Jan 2005 16:32:24 +0000 (GMT) (envelope-from mime@traveller.cz) Received: from localhost.i.cz (ss.eunet.cz. [193.85.228.13]) by ss.eunet.cz (8.13.1/8.13.1) with ESMTP id j0LGWh7h025864; Fri, 21 Jan 2005 17:32:43 +0100 (CET) (envelope-from mime@traveller.cz) From: Michal Mertl To: Emanuel Strobl In-Reply-To: <200501211214.15327.emanuel.strobl@gmx.net> References: <1106134006.1132.12.camel@genius2.i.cz> <1106227110.716.11.camel@genius2.i.cz> <200501211214.15327.emanuel.strobl@gmx.net> Content-Type: text/plain Date: Fri, 21 Jan 2005 17:32:19 +0100 Message-Id: <1106325139.754.6.camel@genius2.i.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org cc: bernd@bwct.de Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 16:32:25 -0000 Emanuel Strobl wrote: > Am Donnerstag, 20. Januar 2005 14:18 schrieb Michal Mertl: > > > I tested my patch for binary safety on CURRENT yesterday (dialed with > > ppp) and didn't notice any problem. > > > > I'm attaching my patch again because some recipients didn't probably > > receive it yesterday. > > This didn't apply cleanly against my -stable from today. > Attached is a cleaned version (#define RSAQ_STATUS_CTS doesn't exist in > -stable uplcom.c) for -stable which compiles for me. > Thank you. I found I can't run getty on the converter. I see some output on the remote computer but it stops pretty soon. If I issue "setty -f /dev/cuaU0 crtscts" I get some more output. It works really realiably in the other direction (running getty on real serial and connecting to it with cu through the converter). I will try to find out more. > > > > > Michal From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 16:54:30 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B78816A4CE for ; Fri, 21 Jan 2005 16:54:30 +0000 (GMT) Received: from osi2.gua.net (osi2.gua.net [205.161.188.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75F1743D58 for ; Fri, 21 Jan 2005 16:54:29 +0000 (GMT) (envelope-from kuuse@redantigua.com) Received: (qmail 88798 invoked by uid 89); 21 Jan 2005 16:54:28 -0000 Received: from kuuse@redantigua.com by osi2 by uid 89 with qmail-scanner-1.20 ( Clear:RC:0(205.161.188.16):. Processed in 0.361447 secs); 21 Jan 2005 16:54:28 -0000 Received: from unknown (HELO widserver1) (kuuse@osint.net@205.161.188.16) by 0 with SMTP; 21 Jan 2005 16:54:27 -0000 Message-ID: <00ba01c4ffd9$fd5e7a70$10bca1cd@widserver1> From: "Johan Kuuse - Red Antigua" To: "Ryan Sommers" References: <000a01c4ffd2$86d5cc70$10bca1cd@widserver1> <50177.208.4.77.66.1106324544.squirrel@208.4.77.66> Date: Fri, 21 Jan 2005 10:55:17 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 cc: current@freebsd.org Subject: Re: Problem with crt1.o and init tls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 16:54:30 -0000 OK, any suggestion? I admit I'm having a disaster. What I think about now (the ultimate case) is to get another HDD, install 5.3 on that HDD, mount this disaster as a second HDD to recover data. But I really wanted to get some experience in source updating, so if there is someway to get rid of this disaster, I would really appreciate som hints. Best Regards, Johan Kuuse kuuse@redantigua.com ----- Original Message ----- From: "Ryan Sommers" To: "Johan Kuuse - Red Antigua" Cc: Sent: Friday, January 21, 2005 10:22 AM Subject: Re: Problem with crt1.o and init tls Johan Kuuse - Red Antigua said: > Hi, > > I'm trying to upgrade from 5.2.1 to 6.0 current. > > # make buildworld > # make buildkernel > # make installkernel > # reboot > > all went fine. > > uname -a now shows > FreeBSD 6.0-CURRENT ... > > With > # mergemaster -p > # make installworld > the problems started. What problems? At this point, removing your object files might have been a bad idea. Your kernel and world are out of sync and trying to build a new world with an out of sync userland might be asking for disaster. -- Ryan Sommers ryans@gamersimpact.com _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 17:03:34 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2732D16A4CE for ; Fri, 21 Jan 2005 17:03:34 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B34D43D31 for ; Fri, 21 Jan 2005 17:03:33 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so736wri for ; Fri, 21 Jan 2005 09:03:32 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=iH22djQBMWQRCK43gsRLkKlbezBt4kd2VE0aJmtF5wyAI1t05pxmnK1DcGwiyEReFnOav2p+n093P7QFUmJ8UgNNMN3OvTC9gYaofYELVjaPn2Xl+zJSW4DPqa7kESz0/DR6Gfun/XiA+c53v4cS3cGa3RlCGyMunmSqty4ycw4= Received: by 10.54.4.31 with SMTP id 31mr202119wrd; Fri, 21 Jan 2005 09:03:32 -0800 (PST) Received: by 10.54.29.4 with HTTP; Fri, 21 Jan 2005 09:03:31 -0800 (PST) Message-ID: <790a9fff05012109032d01e68@mail.gmail.com> Date: Fri, 21 Jan 2005 11:03:31 -0600 From: Scot Hetzel To: Johan Kuuse - Red Antigua In-Reply-To: <00ba01c4ffd9$fd5e7a70$10bca1cd@widserver1> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <000a01c4ffd2$86d5cc70$10bca1cd@widserver1> <50177.208.4.77.66.1106324544.squirrel@208.4.77.66> <00ba01c4ffd9$fd5e7a70$10bca1cd@widserver1> cc: current@freebsd.org Subject: Re: Problem with crt1.o and init tls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Scot Hetzel List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 17:03:34 -0000 On Fri, 21 Jan 2005 10:55:17 -0600, Johan Kuuse - Red Antigua wrote: > OK, any suggestion? > I admit I'm having a disaster. > What I think about now (the ultimate case) is to get another HDD, install > 5.3 on that HDD, mount this disaster as a second HDD to recover data. > But I really wanted to get some experience in source updating, so if there > is someway to get rid of this disaster, I would really appreciate som hints. > Try booting with kernel.old by breaking in to the loader, then execute the following: boot kernel.old Then try buildworld, buildkernel, installkernel, & installworld steps again. From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 17:28:44 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3EFB816A4F9 for ; Fri, 21 Jan 2005 17:28:44 +0000 (GMT) Received: from www.centralpets.com (www.centralpets.com [216.15.161.2]) by mx1.FreeBSD.org (Postfix) with SMTP id 82C8643D5C for ; Fri, 21 Jan 2005 17:28:43 +0000 (GMT) (envelope-from delll@centralpets.com) Received: (qmail 21806 invoked from network); 21 Jan 2005 17:28:46 -0000 Received: from bark.centralpets.com (unknown [127.0.0.1]) by centralpets.com ([127.0.0.1]) with ESMTP via TCP; 21 Jan 2005 17:28:46 -0000 Received: from 219.118.190.154 (unverified [219.118.190.154]) by bark.centralpets.com (VisualMail 4.0) with WEBMAIL id 21799; Fri, 21 Jan 2005 17:28:45 +0000 From: "Livingston Dell" To: hackers@freebsd.org Importance: Normal Sensitivity: Normal Message-ID: X-Mailer: Mintersoft VisualMail, Build 4.0.111601 X-Originating-IP: [219.118.190.154] Date: Fri, 21 Jan 2005 17:28:45 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: HEADSUP: ahc driver will be retired! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 17:28:44 -0000 In article <73462.975440383@critter.freebsd.dk> PHK writes: > >Maybe we should put a special marker in -currents sendmail and >reject all email to the current list if they don't originate >from such a system. > >I'll tell you in case you can't figure out the answer to that rather >simple question: You're annoying people and wasting developer >time. That's what. And further evidence that FreeBSD is turning into PHKBSD: what PHK wants, despite objections from other people, PHK does, and damn any consequences, whether they be social, political, or technical. Several people have raised valid objections to PHK's actions (again -- at least he bothered warning people this time), and have proposed an alternate solution, which PHK has ignored (again -- at least this time he bothered saying so). And, once again, PHK's response is: shut up and go away. --------------------------------------------- This e-mail was sent using a CentralPets WebMail account Get yours at: http://mail.centralpets.com From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 17:30:51 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2287616A4CE for ; Fri, 21 Jan 2005 17:30:51 +0000 (GMT) Received: from osi2.gua.net (osi2.gua.net [205.161.188.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38ACD43D39 for ; Fri, 21 Jan 2005 17:30:50 +0000 (GMT) (envelope-from kuuse@redantigua.com) Received: (qmail 51486 invoked by uid 89); 21 Jan 2005 17:30:49 -0000 Received: from kuuse@redantigua.com by osi2 by uid 89 with qmail-scanner-1.20 ( Clear:RC:0(168.234.207.100):. Processed in 0.227564 secs); 21 Jan 2005 17:30:49 -0000 Received: from unknown (HELO qc.gua.net) (kuuse@osint.net@168.234.207.100) by 0 with SMTP; 21 Jan 2005 17:30:48 -0000 From: Johan Kuuse Organization: Red Antigua To: freebsd-current@freebsd.org, Scot Hetzel Date: Fri, 21 Jan 2005 11:30:43 -0600 User-Agent: KMail/1.7.2 References: <000a01c4ffd2$86d5cc70$10bca1cd@widserver1> <00ba01c4ffd9$fd5e7a70$10bca1cd@widserver1> <790a9fff05012109032d01e68@mail.gmail.com> In-Reply-To: <790a9fff05012109032d01e68@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501211130.43893.kuuse@redantigua.com> cc: current@freebsd.org Subject: Re: Problem with crt1.o and init tls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 17:30:51 -0000 Probably the best tip I could get, thanks. boot kernel.old now gives uname -a FreeBSD qc.gua.net 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE ... and I'm now able to answer this mail from the FreeBSD box, but make buildworld causes the same error message: /usr/lib/crt1.o: In function '_start': /usr/lib/crt1.o(.text+0x64): undefined reference to '_init_tls' *** Error code 1 Stop in /usr/src/usr.bin/make *** Error code 1 Stop in /usr/src *** Error code 1 Stop in /usr/src Q1. Should I start all over syncing the source code? or Q2. Should it be enough to 'make cleandir'and the 'make buildworld'? Q3. Should the flag -DALWAYS_CHECK_MAKE be used with 'make ', that is, not only with 'make cleandir'? Q4. Should I try using the old kernel in single user mode? boot -s kernel.old Thanks in advance. Best Regards, Johan Kuuse kuuse@redantigua.com On Friday 21 January 2005 11:03, Scot Hetzel wrote: > On Fri, 21 Jan 2005 10:55:17 -0600, Johan Kuuse - Red Antigua > > wrote: > > OK, any suggestion? > > I admit I'm having a disaster. > > What I think about now (the ultimate case) is to get another HDD, install > > 5.3 on that HDD, mount this disaster as a second HDD to recover data. > > But I really wanted to get some experience in source updating, so if > > there is someway to get rid of this disaster, I would really appreciate > > som hints. > > Try booting with kernel.old by breaking in to the loader, then execute > the following: > boot kernel.old > > Then try buildworld, buildkernel, installkernel, & installworld steps > again. _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 17:30:51 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 239B416A4CF for ; Fri, 21 Jan 2005 17:30:51 +0000 (GMT) Received: from osi2.gua.net (osi2.gua.net [205.161.188.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38C3143D45 for ; Fri, 21 Jan 2005 17:30:50 +0000 (GMT) (envelope-from kuuse@redantigua.com) Received: (qmail 51486 invoked by uid 89); 21 Jan 2005 17:30:49 -0000 Received: from kuuse@redantigua.com by osi2 by uid 89 with qmail-scanner-1.20 ( Clear:RC:0(168.234.207.100):. Processed in 0.227564 secs); 21 Jan 2005 17:30:49 -0000 Received: from unknown (HELO qc.gua.net) (kuuse@osint.net@168.234.207.100) by 0 with SMTP; 21 Jan 2005 17:30:48 -0000 From: Johan Kuuse Organization: Red Antigua To: freebsd-current@freebsd.org, Scot Hetzel Date: Fri, 21 Jan 2005 11:30:43 -0600 User-Agent: KMail/1.7.2 References: <000a01c4ffd2$86d5cc70$10bca1cd@widserver1> <00ba01c4ffd9$fd5e7a70$10bca1cd@widserver1> <790a9fff05012109032d01e68@mail.gmail.com> In-Reply-To: <790a9fff05012109032d01e68@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501211130.43893.kuuse@redantigua.com> cc: current@freebsd.org Subject: Re: Problem with crt1.o and init tls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 17:30:51 -0000 Probably the best tip I could get, thanks. boot kernel.old now gives uname -a FreeBSD qc.gua.net 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE ... and I'm now able to answer this mail from the FreeBSD box, but make buildworld causes the same error message: /usr/lib/crt1.o: In function '_start': /usr/lib/crt1.o(.text+0x64): undefined reference to '_init_tls' *** Error code 1 Stop in /usr/src/usr.bin/make *** Error code 1 Stop in /usr/src *** Error code 1 Stop in /usr/src Q1. Should I start all over syncing the source code? or Q2. Should it be enough to 'make cleandir'and the 'make buildworld'? Q3. Should the flag -DALWAYS_CHECK_MAKE be used with 'make ', that is, not only with 'make cleandir'? Q4. Should I try using the old kernel in single user mode? boot -s kernel.old Thanks in advance. Best Regards, Johan Kuuse kuuse@redantigua.com On Friday 21 January 2005 11:03, Scot Hetzel wrote: > On Fri, 21 Jan 2005 10:55:17 -0600, Johan Kuuse - Red Antigua > > wrote: > > OK, any suggestion? > > I admit I'm having a disaster. > > What I think about now (the ultimate case) is to get another HDD, install > > 5.3 on that HDD, mount this disaster as a second HDD to recover data. > > But I really wanted to get some experience in source updating, so if > > there is someway to get rid of this disaster, I would really appreciate > > som hints. > > Try booting with kernel.old by breaking in to the loader, then execute > the following: > boot kernel.old > > Then try buildworld, buildkernel, installkernel, & installworld steps > again. _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 17:56:45 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81DF216A4CE for ; Fri, 21 Jan 2005 17:56:45 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D3C443D1D for ; Fri, 21 Jan 2005 17:56:45 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wproxy.gmail.com with SMTP id 68so11491wra for ; Fri, 21 Jan 2005 09:56:44 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=PdPbBGkNRx/UlChufzCw+jpRR3eO99YE+vBH9Zgd9ib9YqH28LGbxZuDPCCprK5ixKhJAICg1vc7YsSr+Thf23BME2gCA12qULPbJe3s5+dUuhmipRq/+h2ujZUSUS7DasWxG/QkhWmxIdTYFPKUOF70EpfNHf3lVJgF0ek0ELw= Received: by 10.54.39.41 with SMTP id m41mr97724wrm; Fri, 21 Jan 2005 09:56:44 -0800 (PST) Received: by 10.54.29.4 with HTTP; Fri, 21 Jan 2005 09:56:44 -0800 (PST) Message-ID: <790a9fff05012109562ba31a32@mail.gmail.com> Date: Fri, 21 Jan 2005 11:56:44 -0600 From: Scot Hetzel To: Johan Kuuse In-Reply-To: <200501211130.43893.kuuse@redantigua.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <000a01c4ffd2$86d5cc70$10bca1cd@widserver1> <00ba01c4ffd9$fd5e7a70$10bca1cd@widserver1> <790a9fff05012109032d01e68@mail.gmail.com> <200501211130.43893.kuuse@redantigua.com> cc: freebsd-current@freebsd.org cc: current@freebsd.org Subject: Re: Problem with crt1.o and init tls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Scot Hetzel List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 17:56:45 -0000 On Fri, 21 Jan 2005 11:30:43 -0600, Johan Kuuse wrote: > Probably the best tip I could get, thanks. > boot kernel.old > now gives > uname -a > FreeBSD qc.gua.net 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE ... > and I'm now able to answer this mail from the FreeBSD box, but > make buildworld > causes the same error message: > > /usr/lib/crt1.o: In function '_start': > /usr/lib/crt1.o(.text+0x64): undefined reference to '_init_tls' > *** Error code 1 > > Q1. Should I start all over syncing the source code? A resync of the source code wouldn't hurt. But it won'e fix the problem either. > Q2. Should it be enough to 'make cleandir'and the 'make buildworld'? > Q3. Should the flag -DALWAYS_CHECK_MAKE be used with 'make ', that > is, not only with 'make cleandir'? > Q4. Should I try using the old kernel in single user mode? boot -s kernel.old > The problem is that you have some 6-CURRENT libraries that replaced your 5.2 libraries. You need to reinstall the 5.2 libraries and remove the 6-CURRENT libraries. If you have the install CD for 5.2.1, just mount it, and the change to where the library distribution is and run the install.sh script. You may also have to do this for the bin, sbin, usr.bin, and usr.sbin distributions also. Then try building 6x with: make OSRELDATE=0 buildworld Scot From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 17:56:49 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 469F816A505 for ; Fri, 21 Jan 2005 17:56:49 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F86C43D31 for ; Fri, 21 Jan 2005 17:56:48 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wproxy.gmail.com with SMTP id 37so14928wra for ; Fri, 21 Jan 2005 09:56:44 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=PdPbBGkNRx/UlChufzCw+jpRR3eO99YE+vBH9Zgd9ib9YqH28LGbxZuDPCCprK5ixKhJAICg1vc7YsSr+Thf23BME2gCA12qULPbJe3s5+dUuhmipRq/+h2ujZUSUS7DasWxG/QkhWmxIdTYFPKUOF70EpfNHf3lVJgF0ek0ELw= Received: by 10.54.39.41 with SMTP id m41mr97724wrm; Fri, 21 Jan 2005 09:56:44 -0800 (PST) Received: by 10.54.29.4 with HTTP; Fri, 21 Jan 2005 09:56:44 -0800 (PST) Message-ID: <790a9fff05012109562ba31a32@mail.gmail.com> Date: Fri, 21 Jan 2005 11:56:44 -0600 From: Scot Hetzel To: Johan Kuuse In-Reply-To: <200501211130.43893.kuuse@redantigua.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <000a01c4ffd2$86d5cc70$10bca1cd@widserver1> <00ba01c4ffd9$fd5e7a70$10bca1cd@widserver1> <790a9fff05012109032d01e68@mail.gmail.com> <200501211130.43893.kuuse@redantigua.com> cc: freebsd-current@freebsd.org cc: current@freebsd.org Subject: Re: Problem with crt1.o and init tls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Scot Hetzel List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 17:56:49 -0000 On Fri, 21 Jan 2005 11:30:43 -0600, Johan Kuuse wrote: > Probably the best tip I could get, thanks. > boot kernel.old > now gives > uname -a > FreeBSD qc.gua.net 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE ... > and I'm now able to answer this mail from the FreeBSD box, but > make buildworld > causes the same error message: > > /usr/lib/crt1.o: In function '_start': > /usr/lib/crt1.o(.text+0x64): undefined reference to '_init_tls' > *** Error code 1 > > Q1. Should I start all over syncing the source code? A resync of the source code wouldn't hurt. But it won'e fix the problem either. > Q2. Should it be enough to 'make cleandir'and the 'make buildworld'? > Q3. Should the flag -DALWAYS_CHECK_MAKE be used with 'make ', that > is, not only with 'make cleandir'? > Q4. Should I try using the old kernel in single user mode? boot -s kernel.old > The problem is that you have some 6-CURRENT libraries that replaced your 5.2 libraries. You need to reinstall the 5.2 libraries and remove the 6-CURRENT libraries. If you have the install CD for 5.2.1, just mount it, and the change to where the library distribution is and run the install.sh script. You may also have to do this for the bin, sbin, usr.bin, and usr.sbin distributions also. Then try building 6x with: make OSRELDATE=0 buildworld Scot From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 18:11:02 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4375316A4D0 for ; Fri, 21 Jan 2005 18:11:02 +0000 (GMT) Received: from osi2.gua.net (osi2.gua.net [205.161.188.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 389C543D2D for ; Fri, 21 Jan 2005 18:11:01 +0000 (GMT) (envelope-from kuuse@redantigua.com) Received: (qmail 90958 invoked by uid 89); 21 Jan 2005 18:11:00 -0000 Received: from kuuse@redantigua.com by osi2 by uid 89 with qmail-scanner-1.20 ( Clear:RC:0(168.234.207.100):. Processed in 0.233968 secs); 21 Jan 2005 18:11:00 -0000 Received: from unknown (HELO qc.gua.net) (kuuse@osint.net@168.234.207.100) by 0 with SMTP; 21 Jan 2005 18:10:59 -0000 From: Johan Kuuse Organization: Red Antigua To: Scot Hetzel Date: Fri, 21 Jan 2005 12:10:54 -0600 User-Agent: KMail/1.7.2 References: <000a01c4ffd2$86d5cc70$10bca1cd@widserver1> <200501211130.43893.kuuse@redantigua.com> <790a9fff05012109562ba31a32@mail.gmail.com> In-Reply-To: <790a9fff05012109562ba31a32@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501211210.54960.kuuse@redantigua.com> cc: freebsd-current@freebsd.org cc: current@freebsd.org Subject: Re: Problem with crt1.o and init tls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 18:11:02 -0000 I mounted the 5.2.1 CD, there are actually a few install.sh's there: ./base/install.sh ./catpages/install.sh ./compat1x/install.sh ./compat20/install.sh ./compat21/install.sh ./compat22/install.sh ./compat3x/install.sh ./compat4x/install.sh ./crypto/install.sh ./dict/install.sh ./doc/install.sh ./games/install.sh ./info/install.sh ./manpages/install.sh ./ports/install.sh ./proflibs/install.sh ./src/install.sh Do you refer to base/install.sh or to src/install.sh? Sorry for asking all over, but I just want to be 100% sure I get you right, to don't get things worse. Best Regards, Johan Kuuse > > A resync of the source code wouldn't hurt. But it won'e fix the problem > either. > > > Q2. Should it be enough to 'make cleandir'and the 'make buildworld'? > > Q3. Should the flag -DALWAYS_CHECK_MAKE be used with 'make ', > > that is, not only with 'make cleandir'? > > Q4. Should I try using the old kernel in single user mode? boot -s > > kernel.old > > The problem is that you have some 6-CURRENT libraries that replaced > your 5.2 libraries. You need to reinstall the 5.2 libraries and > remove the 6-CURRENT libraries. > > If you have the install CD for 5.2.1, just mount it, and the change to > where the library distribution is and run the install.sh script. > > You may also have to do this for the bin, sbin, usr.bin, and usr.sbin > distributions also. > > Then try building 6x with: > > make OSRELDATE=0 buildworld > > Scot From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 18:11:02 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 366AA16A4CE for ; Fri, 21 Jan 2005 18:11:02 +0000 (GMT) Received: from osi2.gua.net (osi2.gua.net [205.161.188.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3885943D1F for ; Fri, 21 Jan 2005 18:11:01 +0000 (GMT) (envelope-from kuuse@redantigua.com) Received: (qmail 90958 invoked by uid 89); 21 Jan 2005 18:11:00 -0000 Received: from kuuse@redantigua.com by osi2 by uid 89 with qmail-scanner-1.20 ( Clear:RC:0(168.234.207.100):. Processed in 0.233968 secs); 21 Jan 2005 18:11:00 -0000 Received: from unknown (HELO qc.gua.net) (kuuse@osint.net@168.234.207.100) by 0 with SMTP; 21 Jan 2005 18:10:59 -0000 From: Johan Kuuse Organization: Red Antigua To: Scot Hetzel Date: Fri, 21 Jan 2005 12:10:54 -0600 User-Agent: KMail/1.7.2 References: <000a01c4ffd2$86d5cc70$10bca1cd@widserver1> <200501211130.43893.kuuse@redantigua.com> <790a9fff05012109562ba31a32@mail.gmail.com> In-Reply-To: <790a9fff05012109562ba31a32@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501211210.54960.kuuse@redantigua.com> cc: freebsd-current@freebsd.org cc: current@freebsd.org Subject: Re: Problem with crt1.o and init tls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 18:11:02 -0000 I mounted the 5.2.1 CD, there are actually a few install.sh's there: ./base/install.sh ./catpages/install.sh ./compat1x/install.sh ./compat20/install.sh ./compat21/install.sh ./compat22/install.sh ./compat3x/install.sh ./compat4x/install.sh ./crypto/install.sh ./dict/install.sh ./doc/install.sh ./games/install.sh ./info/install.sh ./manpages/install.sh ./ports/install.sh ./proflibs/install.sh ./src/install.sh Do you refer to base/install.sh or to src/install.sh? Sorry for asking all over, but I just want to be 100% sure I get you right, to don't get things worse. Best Regards, Johan Kuuse > > A resync of the source code wouldn't hurt. But it won'e fix the problem > either. > > > Q2. Should it be enough to 'make cleandir'and the 'make buildworld'? > > Q3. Should the flag -DALWAYS_CHECK_MAKE be used with 'make ', > > that is, not only with 'make cleandir'? > > Q4. Should I try using the old kernel in single user mode? boot -s > > kernel.old > > The problem is that you have some 6-CURRENT libraries that replaced > your 5.2 libraries. You need to reinstall the 5.2 libraries and > remove the 6-CURRENT libraries. > > If you have the install CD for 5.2.1, just mount it, and the change to > where the library distribution is and run the install.sh script. > > You may also have to do this for the bin, sbin, usr.bin, and usr.sbin > distributions also. > > Then try building 6x with: > > make OSRELDATE=0 buildworld > > Scot From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 18:12:09 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7440616A4CE for ; Fri, 21 Jan 2005 18:12:09 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09F1043D53 for ; Fri, 21 Jan 2005 18:12:09 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.3] (pool-68-160-236-186.ny325.east.verizon.net [68.160.236.186]) by pi.codefab.com (8.12.11/8.12.11) with ESMTP id j0LIC2H1068105 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Jan 2005 13:12:04 -0500 (EST) Message-ID: <41F14659.8040003@mac.com> Date: Fri, 21 Jan 2005 13:13:45 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <30924.1106323869@critter.freebsd.dk> In-Reply-To: <30924.1106323869@critter.freebsd.dk> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=1.9 required=5.5 tests=AWL,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=disabled version=3.0.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on pi.codefab.com cc: current@freebsd.org Subject: Re: Anybody involved with ISO C standardization ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 18:12:09 -0000 Poul-Henning Kamp wrote: > I just read another brain-dead proposal for a new timeformat > which appearantly is in the ISO C queue and I would really > like if we can avoid having another damn mistake in that area. > (http://david.tribble.com/text/c0xlongtime.html) I tried to figure out what was wrong with the proposal, and came up with this: "The longtime_t type represents a system time as an integral number of ticks elaped since the beginning of the long time epoch. Each tick is two nanoseconds in length. The epoch begins at {AD 2001-01-01 00:00:00.000 Z}. Long time values represent dates across the range of {AD 1601-01-01 00:00:00 Z} to {AD 2401-01-01 00:00:00 Z} within the proleptic Gregorian calendar." [ Ugh. :-) ] -- -Chuck From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 18:13:11 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFE3B16A4CE for ; Fri, 21 Jan 2005 18:13:11 +0000 (GMT) Received: from ss.eunet.cz (ss.eunet.cz [193.85.228.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 21F9E43D2F for ; Fri, 21 Jan 2005 18:13:11 +0000 (GMT) (envelope-from mime@traveller.cz) Received: from localhost.i.cz (ss.eunet.cz. [193.85.228.13]) by ss.eunet.cz (8.13.1/8.13.1) with ESMTP id j0LIDWKO040707 for ; Fri, 21 Jan 2005 19:13:32 +0100 (CET) (envelope-from mime@traveller.cz) From: Michal Mertl To: freebsd-current@freebsd.org Content-Type: multipart/mixed; boundary="=-zxsr8VmMdu8RYd2K44pu" Date: Fri, 21 Jan 2005 19:13:08 +0100 Message-Id: <1106331188.713.13.camel@genius2.i.cz> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Subject: Can't run getty on usb to serial converters and workaround X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 18:13:12 -0000 --=-zxsr8VmMdu8RYd2K44pu Content-Type: text/plain Content-Transfer-Encoding: 7bit Hello, I have got several usb to serial convertors supported by FreeBSD (uftdi(4) and uplcom(4) based) and for some reason getty doesn't work with them. I can use them for outgoing communication without problem. While researching the issue I connected two computers with rollover serial cable. When I connect normal serial ports, I can run getty on both computers. When I connect uftdi(4) or uplcom(4) provided serial port to regular serial port getty works when running only on the computer with regular serial. When I start getty on usb serial (and stop in on the regular) I can connect to it from the computer with regular serial but after printing banner and login prompt it doesn't accept any input. I have ucom and uplcom built with USB_DEBUG so look at the debugging output. When comparing the debug from cu and getty's usage of the device I see that getty seems to stop device after each received newline character (in the debug output I see calls to ucomstop). If I issue some stty commands (stty -f /dev/cuaU0 dtrflow and sometimes crtscts) ucom will read some more characters (up to the next "\n"). Once login is completed (after "fixing up" the port several times with stty) communication works fine. I can't find any way to stop getty from calling ucomstop. Ucomstop is probably called as a result of getty initialization of a tty (port) but I can't find a way to disable it. The importance of newlines is probably because getty(8) reads just a username than changes into login(1) and does the reinitialization. Maybe login does some initialization too. Getty does it again when login refuses the password and getty is respawned. Workaround which works for me is to ingore the calls to ucomstop. I don't know what are these calls supposed to achieve but just from reading the names of the calls makes me wonder. We want to _stop reading_ - why should we? On the contrary - we are expecting some input. Attached patch fixes the problem for me. Better fix probably involves modifying getty(8). The situation is the same on 5-STABLE as on 6-CURRENT. Michal Mertl --=-zxsr8VmMdu8RYd2K44pu Content-Disposition: attachment; filename=ucom.getty.diff Content-Type: text/x-patch; name=ucom.getty.diff; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit Index: ucom.c =================================================================== RCS file: /home/fcvs/cvs/src/sys/dev/usb/ucom.c,v retrieving revision 1.55 diff -u -r1.55 ucom.c --- ucom.c 6 Jan 2005 01:43:28 -0000 1.55 +++ ucom.c 21 Jan 2005 18:03:07 -0000 @@ -623,7 +623,12 @@ if (flag & FREAD) { DPRINTF(("ucomstop: read\n")); +#ifdef notdef + /* The following call makes ucom to stop accept input. When ucom(4) + is used for console access with getty(8) this call breaks it. For + unknown reason getty(8) calls it. */ ucomstopread(sc); +#endif } if (flag & FWRITE) { --=-zxsr8VmMdu8RYd2K44pu-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 18:18:11 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 397BF16A4CE for ; Fri, 21 Jan 2005 18:18:11 +0000 (GMT) Received: from critter.freebsd.dk (f170.freebsd.dk [212.242.86.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C14043D3F for ; Fri, 21 Jan 2005 18:18:10 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id j0LII96U033042; Fri, 21 Jan 2005 19:18:09 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Chuck Swiger From: "Poul-Henning Kamp" In-Reply-To: Your message of "Fri, 21 Jan 2005 13:13:45 EST." <41F14659.8040003@mac.com> Date: Fri, 21 Jan 2005 19:18:09 +0100 Message-ID: <33041.1106331489@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@freebsd.org Subject: Re: Anybody involved with ISO C standardization ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 18:18:11 -0000 In message <41F14659.8040003@mac.com>, Chuck Swiger writes: >Poul-Henning Kamp wrote: >> I just read another brain-dead proposal for a new timeformat >> which appearantly is in the ISO C queue and I would really >> like if we can avoid having another damn mistake in that area. >> (http://david.tribble.com/text/c0xlongtime.html) > >I tried to figure out what was wrong with the proposal, and came up with this: > >"The longtime_t type represents a system time as an integral number of ticks >elaped since the beginning of the long time epoch. Each tick is two >nanoseconds in length. The epoch begins at {AD 2001-01-01 00:00:00.000 Z}. > >Long time values represent dates across the range of {AD 1601-01-01 00:00:00 >Z} to {AD 2401-01-01 00:00:00 Z} within the proleptic Gregorian calendar." Lets take just the two worst mistakes: Resolution of 2 nanoseconds. To get seconds you have to do a 64 bit divide by 500000000 ? Anyone here heard about binary computers ? Binary fractions please, that we we can simply shift way the bits we don't want: seconds = longtime >> 29; (For some value of 29.) Optional leap seconds. As if leap seconds are not enough trouble already, the last thing we need to do is to make them optional. Either the seconds are on the UTC timescale, in which case they contain leap seconds, or they are on TAI and don't. The world has plenty of bad homegrown timescales already, we do not need another one. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 18:22:21 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74F1016A4CE for ; Fri, 21 Jan 2005 18:22:21 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBC4443D48 for ; Fri, 21 Jan 2005 18:22:20 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wproxy.gmail.com with SMTP id 36so13325wra for ; Fri, 21 Jan 2005 10:22:20 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=T+KH74cFVGtjt44Sp9/m0X9XLNs7/Bg31p1wyEM6NjzQGiSHjOOuSDdP8GmZCwG5tketBoOSdEn/MfKdwMWHB3ZIvDBwhJwgi+V33ULo1BgQE0P5/8kBLwPMugYkVZ3IgmA9a8YMIWmoxjy107nTay+BV5N0BQ5ujFXs+7N5wnA= Received: by 10.54.49.20 with SMTP id w20mr301099wrw; Fri, 21 Jan 2005 10:22:20 -0800 (PST) Received: by 10.54.29.4 with HTTP; Fri, 21 Jan 2005 10:22:20 -0800 (PST) Message-ID: <790a9fff05012110223252212a@mail.gmail.com> Date: Fri, 21 Jan 2005 12:22:20 -0600 From: Scot Hetzel To: Johan Kuuse In-Reply-To: <200501211210.54960.kuuse@redantigua.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <000a01c4ffd2$86d5cc70$10bca1cd@widserver1> <200501211130.43893.kuuse@redantigua.com> <790a9fff05012109562ba31a32@mail.gmail.com> <200501211210.54960.kuuse@redantigua.com> cc: freebsd-current@freebsd.org cc: current@freebsd.org Subject: Re: Problem with crt1.o and init tls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Scot Hetzel List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 18:22:21 -0000 On Fri, 21 Jan 2005 12:10:54 -0600, Johan Kuuse wrote: > I mounted the 5.2.1 CD, there are actually a few install.sh's there: > > Do you refer to base/install.sh or to src/install.sh? > Sorry for asking all over, but I just want to be 100% sure I get you right, to > don't get things worse. > base/install.sh you should see a bunch of sbin.??, bin.??, ubin.??, usbin.?? files in there. Look at the base\install.sh and see if it also extracts the etc.?? files. If it does, then you'll need to copy all theses files to a temp dir and remove etc from the install.sh script so that it doesn't overwrite your setup. Also, you should do this in single user mode with all filesystems mounted rw. Scot From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 18:22:21 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9151616A4CF for ; Fri, 21 Jan 2005 18:22:21 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20EC143D49 for ; Fri, 21 Jan 2005 18:22:20 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wproxy.gmail.com with SMTP id 37so20781wra for ; Fri, 21 Jan 2005 10:22:20 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=T+KH74cFVGtjt44Sp9/m0X9XLNs7/Bg31p1wyEM6NjzQGiSHjOOuSDdP8GmZCwG5tketBoOSdEn/MfKdwMWHB3ZIvDBwhJwgi+V33ULo1BgQE0P5/8kBLwPMugYkVZ3IgmA9a8YMIWmoxjy107nTay+BV5N0BQ5ujFXs+7N5wnA= Received: by 10.54.49.20 with SMTP id w20mr301099wrw; Fri, 21 Jan 2005 10:22:20 -0800 (PST) Received: by 10.54.29.4 with HTTP; Fri, 21 Jan 2005 10:22:20 -0800 (PST) Message-ID: <790a9fff05012110223252212a@mail.gmail.com> Date: Fri, 21 Jan 2005 12:22:20 -0600 From: Scot Hetzel To: Johan Kuuse In-Reply-To: <200501211210.54960.kuuse@redantigua.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <000a01c4ffd2$86d5cc70$10bca1cd@widserver1> <200501211130.43893.kuuse@redantigua.com> <790a9fff05012109562ba31a32@mail.gmail.com> <200501211210.54960.kuuse@redantigua.com> cc: freebsd-current@freebsd.org cc: current@freebsd.org Subject: Re: Problem with crt1.o and init tls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Scot Hetzel List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 18:22:21 -0000 On Fri, 21 Jan 2005 12:10:54 -0600, Johan Kuuse wrote: > I mounted the 5.2.1 CD, there are actually a few install.sh's there: > > Do you refer to base/install.sh or to src/install.sh? > Sorry for asking all over, but I just want to be 100% sure I get you right, to > don't get things worse. > base/install.sh you should see a bunch of sbin.??, bin.??, ubin.??, usbin.?? files in there. Look at the base\install.sh and see if it also extracts the etc.?? files. If it does, then you'll need to copy all theses files to a temp dir and remove etc from the install.sh script so that it doesn't overwrite your setup. Also, you should do this in single user mode with all filesystems mounted rw. Scot From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 18:33:54 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62BCF16A4CE for ; Fri, 21 Jan 2005 18:33:54 +0000 (GMT) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E9AE43D1F for ; Fri, 21 Jan 2005 18:33:53 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from orion.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226])j0LIXn69019105; Fri, 21 Jan 2005 20:33:49 +0200 Received: by orion.daedalusnetworks.priv (Postfix, from userid 1001) id E89BC2A475; Fri, 21 Jan 2005 20:33:48 +0200 (EET) Date: Fri, 21 Jan 2005 20:33:48 +0200 From: Giorgos Keramidas To: Chuck Swiger , Poul-Henning Kamp Message-ID: <20050121183348.GA3624@orion.daedalusnetworks.priv> References: <30924.1106323869@critter.freebsd.dk> <41F14659.8040003@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41F14659.8040003@mac.com> cc: current@freebsd.org Subject: Re: Anybody involved with ISO C standardization ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 18:33:54 -0000 On 2005-01-21 13:13, Chuck Swiger wrote: >Poul-Henning Kamp wrote: >> I just read another brain-dead proposal for a new timeformat which >> appearantly is in the ISO C queue and I would really like if we can >> avoid having another damn mistake in that area. >> (http://david.tribble.com/text/c0xlongtime.html) > > I tried to figure out what was wrong with the proposal, and came up > with this: > > "The longtime_t type represents a system time as an integral number > of ticks elaped since the beginning of the long time epoch. Each > tick is two nanoseconds in length. The epoch begins at {AD > 2001-01-01 00:00:00.000 Z}. I don't like the name very much either. Are we also going to have longlongtime_t when 128-bit computers are more common? - Giorgos From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 18:35:52 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC16616A4CE for ; Fri, 21 Jan 2005 18:35:52 +0000 (GMT) Received: from mail02.syd.optusnet.com.au (mail02.syd.optusnet.com.au [211.29.132.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 172A043D54 for ; Fri, 21 Jan 2005 18:35:52 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) j0LIZlM0006613 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 22 Jan 2005 05:35:48 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])j0LIZkxP072616; Sat, 22 Jan 2005 05:35:46 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost)j0LIZkT6072615; Sat, 22 Jan 2005 05:35:46 +1100 (EST) (envelope-from pjeremy) Date: Sat, 22 Jan 2005 05:35:46 +1100 From: Peter Jeremy To: Ryan Sommers Message-ID: <20050121183546.GC68808@cirb503493.alcatel.com.au> References: <20050121151747.GA36660@obiwan.tataz.chchile.org> <50158.208.4.77.66.1106323175.squirrel@208.4.77.66> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50158.208.4.77.66.1106323175.squirrel@208.4.77.66> User-Agent: Mutt/1.4.2i cc: freebsd-current@freebsd.org cc: Jeremie Le Hen Subject: Re: Cannot install kernel as user X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 18:35:53 -0000 On Fri, 2005-Jan-21 08:59:35 -0700, Ryan Sommers wrote: >> I thought about adding a flag such as NO_INSTALLCHOWN in both >> kern.post.mk and kmod.mk. What do you think of the idea ? >> >> I saw there are KMODOWN and KMODGRP in kmod.mk, but it seems there is >> no similar facility in kern.post.mk. Maybe it would be worth having >> KERNOWN and KERNGRP as well. >> >> I can submit a patch if asked. Yes please. >I'm trying to think where this would be useful outside your particular >situation. I'm not sure there is a lot of use. > >The official way to do what you are looking to do is to mount it the other >way. On the build machine export the src/obj directories and mount them on >the target machine. Then execute your make install from the target >machine. Otherwise you run into problems like you are running into. >Especially if you're running an install as a non-root user. Except that this is only guaranteed to work if the build machine and target machine are running the same kernel and the build machine's userland is executable on the target machine. (This is because the first part of the buildworld builds tools against the current userland). As an example, if my build machine is a PIII (build with CPUTYPE=p3) then I can't mount src/obj onto an i486 and run installworld - it will try to execute non-i486 instructions. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 18:36:18 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7CCB16A4E2 for ; Fri, 21 Jan 2005 18:36:18 +0000 (GMT) Received: from osi2.gua.net (osi2.gua.net [205.161.188.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAF8E43D31 for ; Fri, 21 Jan 2005 18:36:17 +0000 (GMT) (envelope-from kuuse@redantigua.com) Received: (qmail 53680 invoked by uid 89); 21 Jan 2005 18:36:17 -0000 Received: from kuuse@redantigua.com by osi2 by uid 89 with qmail-scanner-1.20 ( Clear:RC:0(168.234.207.100):. Processed in 0.175669 secs); 21 Jan 2005 18:36:17 -0000 Received: from unknown (HELO qc.gua.net) (kuuse@osint.net@168.234.207.100) by 0 with SMTP; 21 Jan 2005 18:36:16 -0000 From: Johan Kuuse Organization: Red Antigua To: Scot Hetzel Date: Fri, 21 Jan 2005 12:36:11 -0600 User-Agent: KMail/1.7.2 References: <000a01c4ffd2$86d5cc70$10bca1cd@widserver1> <200501211210.54960.kuuse@redantigua.com> <790a9fff05012110223252212a@mail.gmail.com> In-Reply-To: <790a9fff05012110223252212a@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501211236.11923.kuuse@redantigua.com> cc: freebsd-current@freebsd.org Subject: Re: Problem with crt1.o and init tls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 18:36:18 -0000 The base/ directory: CHECKSUM.MD5 base.af base.al base.ar base.ax base.aa base.ag base.am base.as base.ay base.ab base.ah base.an base.at base.az base.ac base.ai base.ao base.au base.inf base.ad base.aj base.ap base.av base.mtree base.ae base.ak base.aq base.aw install.sh No sbin, bin, ubin, nor usbin whatsoever. :-( base/install.sh: ---------------------------------------------------------------------------------- #!/bin/sh # # $FreeBSD: src/release/scripts/base-install.sh,v 1.6 2002/04/30 09:57:21 ru Exp $ # if [ "`id -u`" != "0" ]; then echo "Sorry, this must be done as root." exit 1 fi echo "You are about to extract the base distribution into ${DESTDIR:-/} - are you SURE" echo -n "you want to do this over your installed system (y/n)? " read ans if [ "$ans" = "y" ]; then cat base.?? | tar --unlink -xpzf - -C ${DESTDIR:-/} fi ---------------------------------------------------------------------------------- This is the one to run? Best Regards, Johan > > base/install.sh > > you should see a bunch of sbin.??, bin.??, ubin.??, usbin.?? files in > there. > > Look at the base\install.sh and see if it also extracts the etc.?? > files. If it does, then you'll need to copy all theses files to a > temp dir and remove etc from the install.sh script so that it doesn't > overwrite your setup. > > Also, you should do this in single user mode with all filesystems mounted > rw. > > Scot > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 18:44:36 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C47B16A4CE for ; Fri, 21 Jan 2005 18:44:36 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id D039443D49 for ; Fri, 21 Jan 2005 18:44:35 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by wproxy.gmail.com with SMTP id 58so17455wri for ; Fri, 21 Jan 2005 10:44:32 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=UeQbQMMukRY1NCBsMovBoHCBMwKbvnRPmXBcDvWW04lFL6S2DsOm2bddYKIGg/VthGjYCDCd4rjnhPmcILvDwX144K2CQLo22io97uHLmLiWR7Q3zTgBlTjjGnoKM6pv7baakJjQiGeEq4G+sPyqGVfyfSLOk78sXMZT4oA41LU= Received: by 10.54.27.4 with SMTP id a4mr15357wra; Fri, 21 Jan 2005 10:44:31 -0800 (PST) Received: by 10.54.29.4 with HTTP; Fri, 21 Jan 2005 10:44:31 -0800 (PST) Message-ID: <790a9fff050121104465cba292@mail.gmail.com> Date: Fri, 21 Jan 2005 12:44:31 -0600 From: Scot Hetzel To: Johan Kuuse In-Reply-To: <200501211236.11923.kuuse@redantigua.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <000a01c4ffd2$86d5cc70$10bca1cd@widserver1> <200501211210.54960.kuuse@redantigua.com> <790a9fff05012110223252212a@mail.gmail.com> <200501211236.11923.kuuse@redantigua.com> cc: freebsd-current@freebsd.org Subject: Re: Problem with crt1.o and init tls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Scot Hetzel List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 18:44:36 -0000 On Fri, 21 Jan 2005 12:36:11 -0600, Johan Kuuse wrote: > The base/ directory: > > No sbin, bin, ubin, nor usbin whatsoever. :-( > Ok, I thought they were split that way at one time. To be safe run the base/install.sh script as follows: cd /cdrom/base mkdir /tmp/base <- someplace to hold the files DESTDIR=/tmp/base install.sh cd /tmp/base mv lib/* /lib mv usr/lib/* /usr/lib mv bin/* /bin mv sbin/* /sbin mv usr/bin/* /usr/bin mv usr/sbin/* /usr/sbin Scot From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 19:00:11 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2063016A4D0 for ; Fri, 21 Jan 2005 19:00:11 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99B6E43D53 for ; Fri, 21 Jan 2005 19:00:10 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.3] (pool-68-160-236-186.ny325.east.verizon.net [68.160.236.186]) by pi.codefab.com (8.12.11/8.12.11) with ESMTP id j0LJ06im095047 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Jan 2005 14:00:08 -0500 (EST) Message-ID: <41F1519C.1090600@mac.com> Date: Fri, 21 Jan 2005 14:01:48 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <33041.1106331489@critter.freebsd.dk> In-Reply-To: <33041.1106331489@critter.freebsd.dk> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=1.9 required=5.5 tests=AWL,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=disabled version=3.0.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on pi.codefab.com cc: current@freebsd.org Subject: Re: Anybody involved with ISO C standardization ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 19:00:11 -0000 Poul-Henning Kamp wrote: > In message <41F14659.8040003@mac.com>, Chuck Swiger writes: [ ... ] > Resolution of 2 nanoseconds. > > To get seconds you have to do a 64 bit divide by 500000000 ? > > Anyone here heard about binary computers ? > > Binary fractions please, that we we can simply shift way the bits > we don't want: > > seconds = longtime >> 29; > > (For some value of 29.) Indeed. Some clever person might decide to power of two which was a multiple of 8 or 16 or so, so that you don't even have to shift bits, and you end up with something that resembles (struct timeval). An integral timer with a resolution of 1 tick = 1 second has a lot going right for it. And of course, there is the issue of choosing yet another epoch that nobody else has heard of. If you talk to an astronomer, they really want to standardarize on J2000. -- -Chuck From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 19:05:48 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2018816A4CE for ; Fri, 21 Jan 2005 19:05:48 +0000 (GMT) Received: from critter.freebsd.dk (f170.freebsd.dk [212.242.86.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5223043D2D for ; Fri, 21 Jan 2005 19:05:47 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id j0LJ5jO2034098; Fri, 21 Jan 2005 20:05:45 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Chuck Swiger From: "Poul-Henning Kamp" In-Reply-To: Your message of "Fri, 21 Jan 2005 14:01:48 EST." <41F1519C.1090600@mac.com> Date: Fri, 21 Jan 2005 20:05:45 +0100 Message-ID: <34097.1106334345@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@freebsd.org Subject: Re: Anybody involved with ISO C standardization ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 19:05:48 -0000 In message <41F1519C.1090600@mac.com>, Chuck Swiger writes: >Poul-Henning Kamp wrote: >> In message <41F14659.8040003@mac.com>, Chuck Swiger writes: >[ ... ] >> Resolution of 2 nanoseconds. >> >> To get seconds you have to do a 64 bit divide by 500000000 ? >> >> Anyone here heard about binary computers ? >> >> Binary fractions please, that we we can simply shift way the bits >> we don't want: >> >> seconds = longtime >> 29; >> >> (For some value of 29.) > >Indeed. Some clever person might decide to power of two which was a multiple >of 8 or 16 or so, so that you don't even have to shift bits, and you end up >with something that resembles (struct timeval). An integral timer with a >resolution of 1 tick = 1 second has a lot going right for it. The problem is that if you use 32 bits, then 64 bits don't stretch far enough, and if you use 24 bits you don't get enough resolution. My personal preference would be struct { signed 64+ bits: integer part. unsigned 32+ bits: fraction part. } -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 19:26:26 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BA1816A4CE; Fri, 21 Jan 2005 19:26:26 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D4CE43D46; Fri, 21 Jan 2005 19:26:25 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id j0LJQNtL019206; Fri, 21 Jan 2005 22:26:23 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id j0LJQNHP019205; Fri, 21 Jan 2005 22:26:23 +0300 (MSK) (envelope-from ache) Date: Fri, 21 Jan 2005 22:26:22 +0300 From: Andrey Chernov To: Joerg Wunsch Message-ID: <20050121192622.GA19150@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Joerg Wunsch , current@FreeBSD.ORG, bde@FreeBSD.ORG References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120215807.GA70629@nagual.pp.ru> <20050120221154.GC70629@nagual.pp.ru> <20050121150709.GA60180@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050121150709.GA60180@uriah.heep.sax.de> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.8; VDF: 6.29.0.73; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [0.0.0.0]); Fri, 21 Jan 2005 22:26:24 +0300 (MSK) cc: current@FreeBSD.ORG cc: bde@FreeBSD.ORG Subject: Re: [patch] Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 19:26:26 -0000 On Fri, Jan 21, 2005 at 04:07:09PM +0100, Joerg Wunsch wrote: > As Andrey Chernov wrote: > > > Here is untested patch to fix the problem: > > Apart of the stylistic problems mentioned by Bruce: Already fixed in the first commit as part of testing. Second commit fixes style problems. -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 19:28:47 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B21A16A4CE for ; Fri, 21 Jan 2005 19:28:47 +0000 (GMT) Received: from schlepper.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52EDD43D55 for ; Fri, 21 Jan 2005 19:28:46 +0000 (GMT) (envelope-from stb@lassitu.de) Received: from [IPv6:::1] (schlepper [212.12.50.230]) by schlepper.zs64.net (8.13.1/8.11.1) with ESMTP id j0LJSivG070110; Fri, 21 Jan 2005 20:28:44 +0100 (CET) (envelope-from stb@lassitu.de) In-Reply-To: <33041.1106331489@critter.freebsd.dk> References: <33041.1106331489@critter.freebsd.dk> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Stefan Bethke Date: Fri, 21 Jan 2005 20:28:46 +0100 To: "Poul-Henning Kamp" X-Mailer: Apple Mail (2.619) cc: current@freebsd.org Subject: Re: Anybody involved with ISO C standardization ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 19:28:47 -0000 Am 21.01.2005 um 19:18 schrieb Poul-Henning Kamp: > In message <41F14659.8040003@mac.com>, Chuck Swiger writes: >> Poul-Henning Kamp wrote: >>> I just read another brain-dead proposal for a new timeformat >>> which appearantly is in the ISO C queue and I would really >>> like if we can avoid having another damn mistake in that area. >>> (http://david.tribble.com/text/c0xlongtime.html) >> >> I tried to figure out what was wrong with the proposal, and came up >> with this: >> >> "The longtime_t type represents a system time as an integral number >> of ticks >> elaped since the beginning of the long time epoch. Each tick is two >> nanoseconds in length. The epoch begins at {AD 2001-01-01 >> 00:00:00.000 Z}. >> >> Long time values represent dates across the range of {AD 1601-01-01 >> 00:00:00 >> Z} to {AD 2401-01-01 00:00:00 Z} within the proleptic Gregorian >> calendar." > > Lets take just the two worst mistakes: Maybe the author of these proposals hasn't had the opportunity to enjoy Calendrical Calculations by Reingold and Dershowitz. (Their homepage is at http://emr.cs.iit.edu/home/reingold/calendar-book/index.shtml) Stefan -- Stefan Bethke Fon +49 170 346 0140 From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 19:31:10 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6535B16A4CE; Fri, 21 Jan 2005 19:31:10 +0000 (GMT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id D259F43D53; Fri, 21 Jan 2005 19:31:09 +0000 (GMT) (envelope-from clint@0lsen.net) Received: from 0lsen.net ([24.20.127.157]) by comcast.net (sccrmhc13) with ESMTP id <20050121193108016006pd0ee>; Fri, 21 Jan 2005 19:31:09 +0000 Received: by 0lsen.net (Postfix, from userid 1001) id 25A2D17ABA; Fri, 21 Jan 2005 11:31:08 -0800 (PST) Date: Fri, 21 Jan 2005 11:31:08 -0800 From: Clint Olsen To: Andrey Chernov , Joerg Wunsch , current@FreeBSD.ORG, bde@FreeBSD.ORG Message-ID: <20050121193108.GC70592@0lsen.net> References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120215807.GA70629@nagual.pp.ru> <20050120221154.GC70629@nagual.pp.ru> <20050121150709.GA60180@uriah.heep.sax.de> <20050121192622.GA19150@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050121192622.GA19150@nagual.pp.ru> User-Agent: Mutt/1.4.2.1i Organization: NULlsen Network X-Disclaimer: Mutt Bites! Subject: Re: [patch] Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 19:31:10 -0000 On Jan 21, Andrey Chernov wrote: > Already fixed in the first commit as part of testing. Second commit fixes > style problems. The question is, was it really a style problem or a gcc problem? The comp.lang.c folks might suggest the latter. Whining about missing extraneous parentheses encourages people to write code to shut up gcc, not necessarily good code. -Clint From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 19:39:27 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FF6616A4CE for ; Fri, 21 Jan 2005 19:39:27 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 994B643D1F for ; Fri, 21 Jan 2005 19:39:26 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.3] (pool-68-160-236-186.ny325.east.verizon.net [68.160.236.186]) by pi.codefab.com (8.12.11/8.12.11) with ESMTP id j0LJdKbJ016793 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Jan 2005 14:39:22 -0500 (EST) Message-ID: <41F15ACE.70301@mac.com> Date: Fri, 21 Jan 2005 14:41:02 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <34097.1106334345@critter.freebsd.dk> In-Reply-To: <34097.1106334345@critter.freebsd.dk> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=1.9 required=5.5 tests=AWL,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=disabled version=3.0.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on pi.codefab.com cc: current@freebsd.org Subject: Re: Anybody involved with ISO C standardization ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 19:39:27 -0000 Poul-Henning Kamp wrote: > In message <41F1519C.1090600@mac.com>, Chuck Swiger writes: [ ... ] >>Indeed. Some clever person might decide to power of two which was a multiple >>of 8 or 16 or so, so that you don't even have to shift bits, and you end up >>with something that resembles (struct timeval). An integral timer with a >>resolution of 1 tick = 1 second has a lot going right for it. > > The problem is that if you use 32 bits, then 64 bits don't stretch far > enough, and if you use 24 bits you don't get enough resolution. > > My personal preference would be > > struct { > signed 64+ bits: integer part. > unsigned 32+ bits: fraction part. > } I would agree with this completely. A timescale that used: struct { int64_t seconds; u_int64_t fract; } ...would have native alignment and be capable of representing any reasonable time with excessive precision. If the hardware only updated 32-bits or so worth of fractional second precision, that would be just fine, too. I don't have any problems with a 64-bit representation which uses a 32-bit unsigned seconds value being backwards compatible with a traditional 32-bit time(3) (which is still good for another thirty years), but you do have point that the range is too short. But you could use 32 bits on backwards compatible seconds, 16 bits for a fractional second value (down to tenths of milliseconds), a 16 bits for a signed year value: struct { u_int32_t seconds; u_int16_t fract; int16_t year; } If year = 1970, seconds is equivalent to Unix epoch. Otherwise, the range is big enough to handle calendars which have a non-Gregorian year and also fit the 26,000 year precession of the earth's wobble of the celestial north pole. :-) -- -Chuck From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 19:41:06 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1AC0616A4CF; Fri, 21 Jan 2005 19:41:06 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E85E43D49; Fri, 21 Jan 2005 19:41:05 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id j0LJf4fd019464; Fri, 21 Jan 2005 22:41:04 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id j0LJf4Qb019463; Fri, 21 Jan 2005 22:41:04 +0300 (MSK) (envelope-from ache) Date: Fri, 21 Jan 2005 22:41:03 +0300 From: Andrey Chernov To: Joerg Wunsch Message-ID: <20050121194103.GB19150@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Joerg Wunsch , current@freebsd.org, bde@freebsd.org References: <20050120224753.GB71573@nagual.pp.ru> <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120222137.GE30862@uriah.heep.sax.de> <20050121000916.GA73235@nagual.pp.ru> <20050121125801.GA94152@nagual.pp.ru> <20050121144428.GK30862@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050121144428.GK30862@uriah.heep.sax.de> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.8; VDF: 6.29.0.73; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [0.0.0.0]); Fri, 21 Jan 2005 22:41:04 +0300 (MSK) cc: current@freebsd.org cc: bde@freebsd.org Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 19:41:06 -0000 On Fri, Jan 21, 2005 at 03:44:28PM +0100, Joerg Wunsch wrote: > Btw., Solaris never sets errno to EINVAL except for the unacceptable > base case (where SUSP requires it). This is _recent_ "Extension to the ISO C standard" as POSIX/SUSv3 names it. No wonder that some systems with old code base not implement it yet. Also see about "may" words tendency at the end of the message. > This is the best demonstration that the entire ``may set to EINVAL'' > thing in SUSP is pointless crap, sorry. As no application developer > can rely on it, they could as well have left this option completely > out. Portability is another subject there. From portability point of view there is no difference, is this feature implemented in some systems or not, because they should consider _both_ cases anyway, since _both_ cases mentioned in the standard. > If someone wants to use strot() to verify their input data, > they'd be best to follow the advise from the FreeBSD manpage: > > ``(Thus, if *nptr is not `\0' but **endptr is `\0' on return, the > entire string was valid.)'' > > This is the only reliable method. (OK, if you care, you can then > check for errno being set to ERANGE in order to detect an > under-/overflow situation.) POSIX/SUSv3 suggestion here is different for this function and for many others which not return indicating value. They suggest to set errno = 0 and check it afterwards. Your method above is not overflow-proof: "Since 0, {LONG_MIN} or {LLONG_MIN}, and {LONG_MAX} or {LLONG_MAX} are returned on error and are also valid returns on success, an application wishing to check for error situations should set errno to 0, then call strtol() or strtoll(), then check errno." > I agree that fixing the 0x problem would fix the part were FreeBSD > currently violates the standard. However, as the majority of other > SUSP compliant systems seem to prefer to not set errno in the empty > string case, I suggest we follow that instead of our current > behaviour. Maybe we should even follow the Solaris behaviour, and not > mess with EINVAL at all except where required by SUSP. See above, > EINVAL is completely pointless for error checking as it is not > portable. There is tendence in POSIX standards showing for years. What is "may" in first edition becomes "must" after few years. IMHO it will be better to keep the system already prepared. >From practical point of view, EINVAL here helps to catch errors. I even remember some errors are catched in the FreeBSD code base after that commit was made first time. -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 19:44:25 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 727C416A4CE; Fri, 21 Jan 2005 19:44:25 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C11C43D2D; Fri, 21 Jan 2005 19:44:24 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id j0LJiKOM019538; Fri, 21 Jan 2005 22:44:20 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id j0LJiKHd019537; Fri, 21 Jan 2005 22:44:20 +0300 (MSK) (envelope-from ache) Date: Fri, 21 Jan 2005 22:44:20 +0300 From: Andrey Chernov To: Clint Olsen Message-ID: <20050121194420.GC19150@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Clint Olsen , Joerg Wunsch , current@FreeBSD.ORG, bde@FreeBSD.ORG References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120215807.GA70629@nagual.pp.ru> <20050120221154.GC70629@nagual.pp.ru> <20050121150709.GA60180@uriah.heep.sax.de> <20050121192622.GA19150@nagual.pp.ru> <20050121193108.GC70592@0lsen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050121193108.GC70592@0lsen.net> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.8; VDF: 6.29.0.73; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [0.0.0.0]); Fri, 21 Jan 2005 22:44:20 +0300 (MSK) cc: Joerg Wunsch cc: current@FreeBSD.ORG cc: bde@FreeBSD.ORG Subject: Re: [patch] Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 19:44:25 -0000 On Fri, Jan 21, 2005 at 11:31:08AM -0800, Clint Olsen wrote: > The question is, was it really a style problem or a gcc problem? The > comp.lang.c folks might suggest the latter. Whining about missing > extraneous parentheses encourages people to write code to shut up gcc, not > necessarily good code. Missing parentheses error here is intentional due to corresponding WARN level set for gcc. Just not do it and got no error. -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 20:20:08 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E47AD16A4CE for ; Fri, 21 Jan 2005 20:20:07 +0000 (GMT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 135BB43D41 for ; Fri, 21 Jan 2005 20:20:07 +0000 (GMT) (envelope-from j@uriah.heep.sax.de) Received: from sax.sax.de (localhost [127.0.0.1]) by sax.sax.de (8.12.10/8.12.10) with ESMTP id j0LKK5Yu022614; Fri, 21 Jan 2005 21:20:05 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.12.10/8.12.10/Submit) with UUCP id j0LKK5oo022613; Fri, 21 Jan 2005 21:20:05 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: from uriah.heep.sax.de (localhost [127.0.0.1]) by uriah.heep.sax.de (8.13.1/8.13.1) with ESMTP id j0LKE0jm004563; Fri, 21 Jan 2005 21:14:00 +0100 (MET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.13.1/8.13.1/Submit) id j0LKE0v0004562; Fri, 21 Jan 2005 21:14:00 +0100 (MET) (envelope-from j) Date: Fri, 21 Jan 2005 21:14:00 +0100 From: Joerg Wunsch To: current@freebsd.org Message-ID: <20050121201400.GQ30862@uriah.heep.sax.de> References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120222137.GE30862@uriah.heep.sax.de> <20050121000916.GA73235@nagual.pp.ru> <20050121125801.GA94152@nagual.pp.ru> <20050121144428.GK30862@uriah.heep.sax.de> <20050121194103.GB19150@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050121194103.GB19150@nagual.pp.ru> User-Agent: Mutt/1.4.2.1i X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-GPG-Fingerprint: 5E84 F980 C3CA FD4B B584 1070 F48C A81B 69A8 5873 X-Spam-Status: No, score=-2.6 required=7.5 tests=AWL,BAYES_00 autolearn=ham version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on uriah.heep.sax.de cc: Andrey Chernov Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joerg Wunsch List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 20:20:08 -0000 As Andrey Chernov wrote: > > Btw., Solaris never sets errno to EINVAL except for the > > unacceptable base case (where SUSP requires it). > This is _recent_ "Extension to the ISO C standard" as POSIX/SUSv3 > names it. No wonder that some systems with old code base not > implement it yet. Solaris is anything else but an ``old code base'', and it's not all that recent, as SUSPv2 is many years old. > Also see about "may" words tendency at the end of the message. Sure, that's why I think the entire EINVAL issue is quite pointless. As long as an application ``may'' support it, there's no guarantee about it, thus a conformant application cannot rely on it, and is forced to have their own validity checks. This defeats the entire idea behind setting errno to EINVAL completely. (This is made even worse in that many systems simply quote the SUSP man page as their system's man page, including the `may', so you cannot even be sure about their particular behaviour by reading their docs. This applies to both, Linux and Solaris.) > Portability is another subject there. From portability point of view > there is no difference, ... My point is: from a portability point of view, EINVAL is completely crap. You can as well drop it. > There is tendence in POSIX standards showing for years. What is > "may" in first edition becomes "must" after few years. IMHO it will > be better to keep the system already prepared. I still disagree. This hasn't been changed over years, as the line from Posix to SUSPv2 through SUSPv3 shows. Well, according to Bruce it's even been just the opposite in the first Posix drafts, where EINVAL was required for conversion errors and optional for bad values of base, so you could infer that they are phasing the feature out instead of in. ;-) Do whatever you want, I think it's silly and should rather be dropped as it is a useless feature, which could only lead people to write unportable code. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 22:01:43 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBDF416A4D0 for ; Fri, 21 Jan 2005 22:01:43 +0000 (GMT) Received: from osi2.gua.net (osi2.gua.net [205.161.188.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id F187643D45 for ; Fri, 21 Jan 2005 22:01:42 +0000 (GMT) (envelope-from kuuse@redantigua.com) Received: (qmail 88618 invoked by uid 89); 21 Jan 2005 22:01:42 -0000 Received: from kuuse@redantigua.com by osi2 by uid 89 with qmail-scanner-1.20 ( Clear:RC:0(168.234.207.100):. Processed in 0.254615 secs); 21 Jan 2005 22:01:42 -0000 Received: from unknown (HELO qc.gua.net) (kuuse@osint.net@168.234.207.100) by 0 with SMTP; 21 Jan 2005 22:01:41 -0000 From: Johan Kuuse Organization: Red Antigua To: Scot Hetzel Date: Fri, 21 Jan 2005 16:01:36 -0600 User-Agent: KMail/1.7.2 References: <000a01c4ffd2$86d5cc70$10bca1cd@widserver1> <200501211236.11923.kuuse@redantigua.com> <790a9fff050121104465cba292@mail.gmail.com> In-Reply-To: <790a9fff050121104465cba292@mail.gmail.com> MIME-Version: 1.0 Content-Disposition: inline X-UID: 40 X-Length: 1442 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200501211601.36583.kuuse@redantigua.com> cc: freebsd-current@freebsd.org Subject: Re: Problem with crt1.o and init tls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 22:01:44 -0000 > To be safe run the base/install.sh script as follows: > > cd /cdrom/base > mkdir /tmp/base <- someplace to hold the files > DESTDIR=/tmp/base install.sh > cd /tmp/base > mv lib/* /lib > mv usr/lib/* /usr/lib > mv bin/* /bin > mv sbin/* /sbin > mv usr/bin/* /usr/bin > mv usr/sbin/* /usr/sbin > > Scot OK, I restored the 5.2.1 base. Almost. :-( Moving the directories went all fine, except /tmp/base/lib/libcrypt.so.2 -> /lib/libcrypt.so.2 "Operation not permitted" I did succeed with cp -p /tmp/base/lib/libcrypt.so.2 /lib/libcrypt.so.2.521 but I can't find a way to delete /lib/libcrypt.so.2 chmod 644 /lib/libcrypt.so.2 - fails unlink /lib/libcrypt.so.2 - fails I tried both in single-user- and in multi-user-mode. I also tried changing securelevel (after http://lists.freebsd.org/pipermail/freebsd-questions/2003-July/013601.html): i.e. adding this to /etc/rc.conf: kern_securelevel_enable="YES" # kernel security level (see init(8)), kern_securelevel="-1" which gives $ sysctl -a|grep securelevel kern.securelevel: -1 but I can't still get rid of /lib/libcrypt.so.2 Any hints? Best Regards, Johan Kuuse From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 22:10:20 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9097D16A4CE for ; Fri, 21 Jan 2005 22:10:20 +0000 (GMT) Received: from cicero0.cybercity.dk (cicero0.cybercity.dk [212.242.40.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7FB943D58 for ; Fri, 21 Jan 2005 22:10:19 +0000 (GMT) (envelope-from tom@motd.dk) Received: from bart.motd.dk (port95.ds1-ro.adsl.cybercity.dk [212.242.60.98]) by cicero0.cybercity.dk (Postfix) with ESMTP id 45AC32A672; Fri, 21 Jan 2005 23:10:18 +0100 (CET) Received: from localhost (localhost.motd.dk [127.0.0.1]) by bart.motd.dk (Postfix) with ESMTP id 13723630E; Fri, 21 Jan 2005 23:09:56 +0100 (CET) Received: from bart.motd.dk ([127.0.0.1]) by localhost (bart.motd.dk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06259-02; Fri, 21 Jan 2005 23:09:54 +0100 (CET) Received: from home03 (unknown [192.168.10.3]) by bart.motd.dk (Postfix) with ESMTP id 804F662DF; Fri, 21 Jan 2005 23:09:54 +0100 (CET) From: "Tom Jensen" To: "'Johan Kuuse'" , "'Scot Hetzel'" Date: Fri, 21 Jan 2005 23:10:18 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <200501211601.36583.kuuse@redantigua.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcUABNVlcjSARwiqRdqqbqNnwvEJxwAAQN/g Message-Id: <20050121220954.804F662DF@bart.motd.dk> X-Virus-Scanned: by amavisd-new at motd.dk cc: freebsd-current@freebsd.org Subject: RE: Problem with crt1.o and init tls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 22:10:20 -0000 My system: -bash-2.05b$ ls -lor /lib/libcrypt.so.2 -r--r--r-- 1 root wheel schg 28644 Nov 9 21:13 /lib/libcrypt.so.2 Se chflags(1) man page for details about removing the flags. - T -----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Johan Kuuse Sent: 21. januar 2005 23:02 To: Scot Hetzel Cc: freebsd-current@freebsd.org Subject: Re: Problem with crt1.o and init tls > To be safe run the base/install.sh script as follows: > > cd /cdrom/base > mkdir /tmp/base <- someplace to hold the files > DESTDIR=/tmp/base install.sh > cd /tmp/base > mv lib/* /lib > mv usr/lib/* /usr/lib > mv bin/* /bin > mv sbin/* /sbin > mv usr/bin/* /usr/bin > mv usr/sbin/* /usr/sbin > > Scot OK, I restored the 5.2.1 base. Almost. :-( Moving the directories went all fine, except /tmp/base/lib/libcrypt.so.2 -> /lib/libcrypt.so.2 "Operation not permitted" I did succeed with cp -p /tmp/base/lib/libcrypt.so.2 /lib/libcrypt.so.2.521 but I can't find a way to delete /lib/libcrypt.so.2 chmod 644 /lib/libcrypt.so.2 - fails unlink /lib/libcrypt.so.2 - fails I tried both in single-user- and in multi-user-mode. I also tried changing securelevel (after http://lists.freebsd.org/pipermail/freebsd-questions/2003-July/013601.html): i.e. adding this to /etc/rc.conf: kern_securelevel_enable="YES" # kernel security level (see init(8)), kern_securelevel="-1" which gives $ sysctl -a|grep securelevel kern.securelevel: -1 but I can't still get rid of /lib/libcrypt.so.2 Any hints? Best Regards, Johan Kuuse _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 22:12:00 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBE0716A4CE for ; Fri, 21 Jan 2005 22:12:00 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1042F43D4C for ; Fri, 21 Jan 2005 22:12:00 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id j0LMBwlm021946; Sat, 22 Jan 2005 01:11:58 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id j0LMBwRC021945; Sat, 22 Jan 2005 01:11:58 +0300 (MSK) (envelope-from ache) Date: Sat, 22 Jan 2005 01:11:57 +0300 From: Andrey Chernov To: Joerg Wunsch Message-ID: <20050121221156.GA21459@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Joerg Wunsch , current@freebsd.org References: <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120222137.GE30862@uriah.heep.sax.de> <20050121000916.GA73235@nagual.pp.ru> <20050121125801.GA94152@nagual.pp.ru> <20050121144428.GK30862@uriah.heep.sax.de> <20050121194103.GB19150@nagual.pp.ru> <20050121201400.GQ30862@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050121201400.GQ30862@uriah.heep.sax.de> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.8; VDF: 6.29.0.75; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [0.0.0.0]); Sat, 22 Jan 2005 01:11:59 +0300 (MSK) cc: current@freebsd.org Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 22:12:01 -0000 On Fri, Jan 21, 2005 at 09:14:00PM +0100, Joerg Wunsch wrote: > My point is: from a portability point of view, EINVAL is completely > crap. You can as well drop it. It simple means we can't rely on portability as the reason for or opposite to this change. > Do whatever you want, I think it's silly and should rather be dropped > as it is a useless feature, which could only lead people to write > unportable code. The code which _not_ expect this feature present is _equally_ unportable. If we decide this change stay or not we can't rely on portability, all things are equal there. I repeat: portable application must always consider _both_ cases since both are mentioned in the standard as possible ones. Portable application can't stay with one variant only. Even if FreeBSD not implement "may" clause, some other system can do it at any moment. Moreover, portable application must consider non-POSIX conformant systems too, it additionly complicates subject. Since we can't rely on portability, we can rely on practical reason to detect syntax errors which is hardly implemented by other methods (f.e. method you suggest can't detect overflows). Of course, such applications will be unportable per definition, but still POSIX conformant. We already have a lot of such things in our own codebase. BTW, where was you when this change was discussed and commited by first time long ago? At those time I don't remember any "against" votes. All those times passed and nobody complain until this moment. It is good sign for this change to stay. -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 22:13:50 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB23716A4CE for ; Fri, 21 Jan 2005 22:13:50 +0000 (GMT) Received: from pacha.mail.bishopston.net (pacha.mail.bishopston.net [66.221.209.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05E2143D41 for ; Fri, 21 Jan 2005 22:13:50 +0000 (GMT) (envelope-from jamie@bishopston.net) X-Catflap-Envelope-From: Received: from catflap.bishopston.net (smmsp@localhost [127.0.0.1]) j0LMDist075264; Fri, 21 Jan 2005 22:13:44 GMT (envelope-from jamie@catflap.bishopston.net) Received: (from root@localhost) by catflap.bishopston.net (8.13.3/8.12.9/Submit) id j0LMDgiq075263; Fri, 21 Jan 2005 22:13:42 GMT Date: Fri, 21 Jan 2005 22:13:42 GMT From: Jamie Jones Message-Id: <200501212213.j0LMDgiq075263@catflap.bishopston.net> To: freebsd-current@freebsd.org, jay@esuna.co.uk In-Reply-To: <41BC33B6.50505@esuna.co.uk> X-Scanned-By: milter-sender/0.62.837 (localhost [127.0.0.1]); Fri, 21 Jan 2005 22:13:44 +0000 cc: jamie@bishopston.net cc: kris@obsecurity.org Subject: Re: bugs in ugen.h (and fix) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 22:13:50 -0000 > > Hopefully Jay can shed some more light on it ? > > I can indeed. I think the rest of that conversation went into private > mail, before I posted a confirmed fix and justification the following > month, beginning in this thread: > > http://lists.freebsd.org/pipermail/freebsd-current/2004-January/017967.html > > It then took a while to get somebody with CVS commit rights to respond, > which led to the submission of a PR: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/62309 > > And... not much happened after that, unfortunately. The PR can be closed > now if the issue is resolved on the 5.x branch. Jay, apologies for not responding sooner - due to circumstances, I've not been around for a month or so :( But I'd like to say, I'm grateful for the work you did - if it wasn't for that, I'd still be unable to use my adsl modem.. Due to your fixes, everything is working like a charm. I'll ensure that your patches are properly merged into 5-Stable. Cheers, Jamie From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 22:15:05 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C56A16A4CE for ; Fri, 21 Jan 2005 22:15:05 +0000 (GMT) Received: from pacha.mail.bishopston.net (pacha.mail.bishopston.net [66.221.209.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id A83FF43D2F for ; Fri, 21 Jan 2005 22:15:04 +0000 (GMT) (envelope-from jamie@bishopston.net) X-Catflap-Envelope-From: Received: from catflap.bishopston.net (smmsp@localhost [127.0.0.1]) j0LMF2gt076671; Fri, 21 Jan 2005 22:15:02 GMT (envelope-from jamie@catflap.bishopston.net) Received: (from root@localhost) by catflap.bishopston.net (8.13.3/8.12.9/Submit) id j0LMF2F7076670; Fri, 21 Jan 2005 22:15:02 GMT Date: Fri, 21 Jan 2005 22:15:02 GMT From: Jamie Jones Message-Id: <200501212215.j0LMF2F7076670@catflap.bishopston.net> To: freebsd-current@freebsd.org, jay@esuna.co.uk In-Reply-To: <41BC33B6.50505@esuna.co.uk> X-Scanned-By: milter-sender/0.62.837 (localhost [127.0.0.1]); Fri, 21 Jan 2005 22:15:02 +0000 cc: jamie@bishopston.net cc: kris@obsecurity.org Subject: Re: bugs in ugen.h (and fix) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 22:15:05 -0000 Damn me for drinking before writing emails. Apologies all, that last email was meant for Jay only :blush: From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 22:22:36 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99B7316A4CE for ; Fri, 21 Jan 2005 22:22:36 +0000 (GMT) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D9F343D1D for ; Fri, 21 Jan 2005 22:22:36 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp4.server.rpi.edu (8.13.0/8.13.0) with ESMTP id j0LMMSMo014307; Fri, 21 Jan 2005 17:22:29 -0500 Mime-Version: 1.0 Message-Id: Date: Fri, 21 Jan 2005 17:22:27 -0500 To: freebsd-current@FreeBSD.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) cc: Ian Dowse cc: =?iso-8859-1?Q?S=F8ren_Schmidt?= Subject: panic: Duplicate free of item 0xc433e420 from zone 0xc1045c00(g_bio) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 22:22:36 -0000 I got another panic. This time I got a clean core-dump, and I also have a kernel with all the debugging symbols if that would help. Here is some of the info. The system had been up about 18 hours before the panic. The system was basically idle at the time of the panic. This is a snapshot of current which I started to build at about 2pm EST on January 20th. Note that I have no idea when those WRITE_DMA messages came out, so I do not know if they are related to the panic, or if those messages were written hours earlier. Let me know if anyone wants to pursue this further. ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=42098457 ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=42098457 ad4: FAILURE - WRITE_DMA timed out g_vfs_done():ad4s2d[WRITE(offset=320405504, length=16384)]error = 5 Slab at 0xc433ef70, freei 8 = 0. panic: Duplicate free of item 0xc433e420 from zone 0xc1045c00(g_bio) KDB: enter: panic [thread pid 3 tid 100044 ] Stopped at kdb_enter+0x2b: nop db> call doadump() Dumping 959 MB 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 3 52 368 384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624 640 656 6 72 688 704 720 736 752 768 784 800 816 832 848 864 880 896 912 928 944 Dump complete 0xf db> trace Tracing pid 3 tid 100044 td 0xc21da5c0 kdb_enter(c0696bbb) at kdb_enter+0x2b panic(c06a9988,c433e420,c1045c00,c0691d35,c06a996c) at panic+0xbb uma_dbg_free(c1045c00,0,c433e420) at uma_dbg_free+0x110 uma_zfree_arg(c1045c00,c433e420,0) at uma_zfree_arg+0xf3 g_destroy_bio(c433e420,c433e420,c223f800,e3c0ccd4,c053d2a3) at g_destroy_bio+0x13 g_disk_done(c433e420) at g_disk_done+0x62 biodone(c433e420,c24b2198,e3c0ccf8,c0461e92,c24b2198) at biodone+0x57 ad_done(c24b2198) at ad_done+0x2d ata_completed(c24b2198,c06f3320) at ata_completed+0x376 g_io_schedule_up(c21da5c0) at g_io_schedule_up+0x31 g_up_procbody(0,e3c0cd48,0,c04c99d8,0) at g_up_procbody+0x5a fork_exit(c04c99d8,0,e3c0cd48) at fork_exit+0xa4 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe3c0cd7c, ebp = 0 --- -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 22:27:12 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED09716A4CE for ; Fri, 21 Jan 2005 22:27:12 +0000 (GMT) Received: from osi2.gua.net (osi2.gua.net [205.161.188.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3852643D4C for ; Fri, 21 Jan 2005 22:27:12 +0000 (GMT) (envelope-from kuuse@redantigua.com) Received: (qmail 89132 invoked by uid 89); 21 Jan 2005 22:27:11 -0000 Received: from kuuse@redantigua.com by osi2 by uid 89 with qmail-scanner-1.20 ( Clear:RC:0(168.234.207.100):. Processed in 0.198617 secs); 21 Jan 2005 22:27:11 -0000 Received: from unknown (HELO qc.gua.net) (kuuse@osint.net@168.234.207.100) by 0 with SMTP; 21 Jan 2005 22:27:11 -0000 From: Johan Kuuse Organization: Red Antigua To: freebsd-current@freebsd.org Date: Fri, 21 Jan 2005 16:27:05 -0600 User-Agent: KMail/1.7.2 References: <20050121220954.804F662DF@bart.motd.dk> In-Reply-To: <20050121220954.804F662DF@bart.motd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501211627.06193.kuuse@redantigua.com> cc: 'Scot Hetzel' cc: Tom Jensen Subject: Re: Problem with crt1.o and init tls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 22:27:13 -0000 Excellent! Thanks! Now I got libcrypt.so.2 from 5.2.1, with flags and everything: bash-2.05b$ ls -lor /lib/libcrypt.so.2 -r--r--r-- 1 root wheel schg 32740 Feb 23 2004 /lib/libcrypt.so.2 Johan On Friday 21 January 2005 16:10, Tom Jensen wrote: > My system: > > -bash-2.05b$ ls -lor /lib/libcrypt.so.2 > -r--r--r-- 1 root wheel schg 28644 Nov 9 21:13 /lib/libcrypt.so.2 > > Se chflags(1) man page for details about removing the flags. > > - T > > -----Original Message----- > From: owner-freebsd-current@freebsd.org > [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Johan Kuuse > Sent: 21. januar 2005 23:02 > To: Scot Hetzel > Cc: freebsd-current@freebsd.org > Subject: Re: Problem with crt1.o and init tls > > > To be safe run the base/install.sh script as follows: > > > > cd /cdrom/base > > mkdir /tmp/base <- someplace to hold the files > > DESTDIR=/tmp/base install.sh > > cd /tmp/base > > mv lib/* /lib > > mv usr/lib/* /usr/lib > > mv bin/* /bin > > mv sbin/* /sbin > > mv usr/bin/* /usr/bin > > mv usr/sbin/* /usr/sbin > > > > Scot > > OK, I restored the 5.2.1 base. > Almost. :-( > Moving the directories went all fine, except > /tmp/base/lib/libcrypt.so.2 -> /lib/libcrypt.so.2 "Operation not permitted" > I did succeed with > cp -p /tmp/base/lib/libcrypt.so.2 /lib/libcrypt.so.2.521 but I can't find a > way to delete /lib/libcrypt.so.2 > > chmod 644 /lib/libcrypt.so.2 - fails > unlink /lib/libcrypt.so.2 - fails > > I tried both in single-user- and in multi-user-mode. > > I also tried changing securelevel (after > http://lists.freebsd.org/pipermail/freebsd-questions/2003-July/013601.html) >: > > i.e. adding this to /etc/rc.conf: > kern_securelevel_enable="YES" # kernel security level (see init(8)), > kern_securelevel="-1" > > which gives > $ sysctl -a|grep securelevel > kern.securelevel: -1 > > but I can't still get rid of /lib/libcrypt.so.2 > > Any hints? > > Best Regards, > Johan Kuuse > > > > > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 22:34:34 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C667316A4CE for ; Fri, 21 Jan 2005 22:34:34 +0000 (GMT) Received: from osi2.gua.net (osi2.gua.net [205.161.188.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id A39B943D31 for ; Fri, 21 Jan 2005 22:34:32 +0000 (GMT) (envelope-from kuuse@redantigua.com) Received: (qmail 76156 invoked by uid 89); 21 Jan 2005 22:34:32 -0000 Received: from kuuse@redantigua.com by osi2 by uid 89 with qmail-scanner-1.20 ( Clear:RC:0(168.234.207.100):. Processed in 0.137728 secs); 21 Jan 2005 22:34:32 -0000 Received: from unknown (HELO qc.gua.net) (kuuse@osint.net@168.234.207.100) by 0 with SMTP; 21 Jan 2005 22:34:31 -0000 From: Johan Kuuse Organization: Red Antigua To: freebsd-current@freebsd.org, Scot Hetzel Date: Fri, 21 Jan 2005 16:34:26 -0600 User-Agent: KMail/1.7.2 References: <000a01c4ffd2$86d5cc70$10bca1cd@widserver1> <200501211130.43893.kuuse@redantigua.com> <790a9fff05012109562ba31a32@mail.gmail.com> In-Reply-To: <790a9fff05012109562ba31a32@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501211634.26766.kuuse@redantigua.com> cc: Tom Jensen Subject: Re: Problem with crt1.o and init tls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 22:34:34 -0000 OK, before I ruin everything again...: Should I use the same flags for *all* 'make' statements? i.e. is it important to use OSRELDATE=0 everywhere? # make OSRELDATE=0 buildworld # make OSRELDATE=0 buildkernel # make OSRELDATE=0 installkernel # reboot boot -s # mergemaster -p # make OSRELDATE=0 installworld # mergemaster # reboot Johan On Friday 21 January 2005 11:56, Scot Hetzel wrote: > Then try building 6x with: > > make OSRELDATE=0 buildworld From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 22:51:27 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E59C916A4CE for ; Fri, 21 Jan 2005 22:51:27 +0000 (GMT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2183D43D31 for ; Fri, 21 Jan 2005 22:51:27 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id j0LMpKAg088560; Fri, 21 Jan 2005 23:51:22 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <41F18768.4050809@DeepCore.dk> Date: Fri, 21 Jan 2005 23:51:20 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 1.0 (X11/20050116) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Garance A Drosihn References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.6 cc: Ian Dowse cc: freebsd-current@FreeBSD.org Subject: Re: panic: Duplicate free of item 0xc433e420 from zone 0xc1045c00(g_bio) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 22:51:28 -0000 Garance A Drosihn wrote: > I got another panic. This time I got a clean core-dump, and I also > have a kernel with all the debugging symbols if that would help. > Here is some of the info. The system had been up about 18 hours > before the panic. The system was basically idle at the time of the > panic. This is a snapshot of current which I started to build at > about 2pm EST on January 20th. The duplicate free on failed ATA retry is known. I have a fix here=20 locally but it doesnt apply to whats in -current.. However, -current has severe problems that provokes those timeouts for=20 no good reason and in all my cases locks up hard. I just vasted last=20 nights sleep hunting for what I thought was a bug in my WIP. I had=20 PREEMPTION turned of etc, but it sitll failed in odd ways. Going back to Jan 10 00:00 UTC sources make things "just work" with=20 PREEMPTION and all. My testbox has now moved around some 800 GB's of=20 data with no problems with above backstep, on -current it fails within=20 the first few Mbytes.. > Note that I have no idea when those WRITE_DMA messages came out, so > I do not know if they are related to the panic, or if those messages > were written hours earlier. >=20 > Let me know if anyone wants to pursue this further. >=20 > ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=3D42098457 > ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=3D42098457 > ad4: FAILURE - WRITE_DMA timed out --=20 -S=F8ren From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 22:56:59 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8341116A4CE for ; Fri, 21 Jan 2005 22:56:59 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id F388C43D5D for ; Fri, 21 Jan 2005 22:56:52 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 512B051342; Fri, 21 Jan 2005 14:56:31 -0800 (PST) Date: Fri, 21 Jan 2005 14:56:31 -0800 From: Kris Kennaway To: S?ren Schmidt Message-ID: <20050121225631.GA56201@xor.obsecurity.org> References: <41F18768.4050809@DeepCore.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zYM0uCDKw75PZbzx" Content-Disposition: inline In-Reply-To: <41F18768.4050809@DeepCore.dk> User-Agent: Mutt/1.4.2.1i cc: Ian Dowse cc: freebsd-current@FreeBSD.org cc: Garance A Drosihn Subject: Re: panic: Duplicate free of item 0xc433e420 from zone 0xc1045c00(g_bio) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 22:56:59 -0000 --zYM0uCDKw75PZbzx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 21, 2005 at 11:51:20PM +0100, S?ren Schmidt wrote: > Garance A Drosihn wrote: > >I got another panic. This time I got a clean core-dump, and I also > >have a kernel with all the debugging symbols if that would help. > >Here is some of the info. The system had been up about 18 hours > >before the panic. The system was basically idle at the time of the > >panic. This is a snapshot of current which I started to build at > >about 2pm EST on January 20th. >=20 > The duplicate free on failed ATA retry is known. I have a fix here=20 > locally but it doesnt apply to whats in -current.. >=20 > However, -current has severe problems that provokes those timeouts for=20 > no good reason and in all my cases locks up hard. I just vasted last=20 > nights sleep hunting for what I thought was a bug in my WIP. I had=20 > PREEMPTION turned of etc, but it sitll failed in odd ways. > Going back to Jan 10 00:00 UTC sources make things "just work" with=20 > PREEMPTION and all. My testbox has now moved around some 800 GB's of=20 > data with no problems with above backstep, on -current it fails within=20 > the first few Mbytes.. Are you sure you have an up-to-date kernel? The bug phk fixed last week might be related. Kris --zYM0uCDKw75PZbzx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB8YieWry0BWjoQKURAtd6AJ9qDBJqDEG1+PjVtEF3eXmqBVfWrgCg4uGW gYntzCYELZKNGvGk+bV45Zc= =Cx4/ -----END PGP SIGNATURE----- --zYM0uCDKw75PZbzx-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 23:03:17 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 887BE16A4CF for ; Fri, 21 Jan 2005 23:03:17 +0000 (GMT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE6D043D4C for ; Fri, 21 Jan 2005 23:03:16 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id j0LN3CxN088714; Sat, 22 Jan 2005 00:03:14 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <41F18A30.3060109@DeepCore.dk> Date: Sat, 22 Jan 2005 00:03:12 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 1.0 (X11/20050116) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <41F18768.4050809@DeepCore.dk> <20050121225631.GA56201@xor.obsecurity.org> In-Reply-To: <20050121225631.GA56201@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.6 cc: Ian Dowse cc: freebsd-current@FreeBSD.org cc: Garance A Drosihn Subject: Re: panic: Duplicate free of item 0xc433e420 from zone 0xc1045c00(g_bio) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 23:03:17 -0000 Kris Kennaway wrote: > On Fri, Jan 21, 2005 at 11:51:20PM +0100, S?ren Schmidt wrote: >=20 >>Garance A Drosihn wrote: >> >>>I got another panic. This time I got a clean core-dump, and I also >>>have a kernel with all the debugging symbols if that would help. >>>Here is some of the info. The system had been up about 18 hours >>>before the panic. The system was basically idle at the time of the >>>panic. This is a snapshot of current which I started to build at >>>about 2pm EST on January 20th. >> >>The duplicate free on failed ATA retry is known. I have a fix here=20 >>locally but it doesnt apply to whats in -current.. >> >>However, -current has severe problems that provokes those timeouts for = >>no good reason and in all my cases locks up hard. I just vasted last=20 >>nights sleep hunting for what I thought was a bug in my WIP. I had=20 >>PREEMPTION turned of etc, but it sitll failed in odd ways. >>Going back to Jan 10 00:00 UTC sources make things "just work" with=20 >>PREEMPTION and all. My testbox has now moved around some 800 GB's of=20 >>data with no problems with above backstep, on -current it fails within = >>the first few Mbytes.. >=20 >=20 > Are you sure you have an up-to-date kernel? The bug phk fixed last > week might be related. I'm positive, latest tried sources from 2000 CET today. The bug phk=20 fixed was fs related, I'm not convinced this is.. --=20 -S=F8ren From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 23:10:23 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CABA16A4D1; Fri, 21 Jan 2005 23:10:23 +0000 (GMT) Received: from VARK.MIT.EDU (VARK.MIT.EDU [18.95.3.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id 908E043D4C; Fri, 21 Jan 2005 23:10:14 +0000 (GMT) (envelope-from das@FreeBSD.ORG) Received: from VARK.MIT.EDU (localhost [127.0.0.1]) by VARK.MIT.EDU (8.13.1/8.13.1) with ESMTP id j0LN9oaR034541; Fri, 21 Jan 2005 18:09:50 -0500 (EST) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.MIT.EDU (8.13.1/8.13.1/Submit) id j0LN9nKe034540; Fri, 21 Jan 2005 18:09:49 -0500 (EST) (envelope-from das@FreeBSD.ORG) Date: Fri, 21 Jan 2005 18:09:49 -0500 From: David Schultz To: Joerg Wunsch Message-ID: <20050121230949.GA34313@VARK.MIT.EDU> Mail-Followup-To: Joerg Wunsch , current@freebsd.org, Andrey Chernov , bde@freebsd.org References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120222137.GE30862@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050120222137.GE30862@uriah.heep.sax.de> cc: Andrey Chernov cc: current@FreeBSD.ORG cc: bde@FreeBSD.ORG Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 23:10:23 -0000 Regarding the interpretation of sequences such as "0x" and "+": These are disallowed by the BNF in section 6.4.4.1 of the C99 standard. The specification of strtol() says: 7.20.1.4.3 If the value of base is zero, the expected form of the subject sequence is that of an integer constant as described in 6.4.4.1 [...] If the value of base is between 2 and 36 (inclusive), the expected form of the subject sequence is a sequence of letters and digits representing an integer 7.20.1.4.7 If the subject sequence is empty or does not have the expected form, no conversion is performed; the value of nptr is stored in the object pointed to by endptr, provided that endptr is not a null pointer. The specification of the base != 0 case is less precise, but it is logical to assume that the authors intended it to be the similar in spirit to the base == 0 case, particularly wrt invalid sequences such as "+". Regarding the use of errno: The ISO C standard allows any library function to set errno to EFOO unless it explicitly says EFOO is used to mean something else for that function. So setting errno to EINVAL in strtol() is allowed by the C standard. POSIX says strtol() may set errno to EINVAL if no conversion is performed, and this is explicitly annotated as an extension to the C standard. However, the implementation is also free to *not* set errno in this case. Therefore, the errno issue is more about pragmatics than standards-compliance. I think the two important questions are: o Is there lots of broken software out there that expects errno to not be set? o Is there FreeBSD software out there that would break if we broke POLA and stopped setting errno? From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 23:24:35 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93D6F16A4CE; Fri, 21 Jan 2005 23:24:35 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4D4C43D1D; Fri, 21 Jan 2005 23:24:34 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id j0LNOXA8023326; Sat, 22 Jan 2005 02:24:33 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id j0LNOXYB023325; Sat, 22 Jan 2005 02:24:33 +0300 (MSK) (envelope-from ache) Date: Sat, 22 Jan 2005 02:24:32 +0300 From: Andrey Chernov To: Joerg Wunsch , current@freebsd.org, bde@freebsd.org Message-ID: <20050121232432.GA23273@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Joerg Wunsch , current@freebsd.org, bde@freebsd.org References: <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120222137.GE30862@uriah.heep.sax.de> <20050121230949.GA34313@VARK.MIT.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050121230949.GA34313@VARK.MIT.EDU> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.8; VDF: 6.29.0.75; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [0.0.0.0]); Sat, 22 Jan 2005 02:24:34 +0300 (MSK) Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 23:24:35 -0000 On Fri, Jan 21, 2005 at 06:09:49PM -0500, David Schultz wrote: > Therefore, the errno issue is more about pragmatics than > standards-compliance. I think the two important questions are: > > o Is there lots of broken software out there that expects > errno to not be set? We have this errno setting since 2001, so any of broken software should already manifest itself but none I know of yet found. -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 23:28:57 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5773916A4CF for ; Fri, 21 Jan 2005 23:28:57 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6769743D45 for ; Fri, 21 Jan 2005 23:28:56 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id j0LNSsZg023382; Sat, 22 Jan 2005 02:28:55 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id j0LNSsDh023381; Sat, 22 Jan 2005 02:28:54 +0300 (MSK) (envelope-from ache) Date: Sat, 22 Jan 2005 02:28:54 +0300 From: Andrey Chernov To: Joerg Wunsch , current@freebsd.org Message-ID: <20050121232854.GB23273@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Joerg Wunsch , current@freebsd.org References: <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120222137.GE30862@uriah.heep.sax.de> <20050121000916.GA73235@nagual.pp.ru> <20050121125801.GA94152@nagual.pp.ru> <20050121144428.GK30862@uriah.heep.sax.de> <20050121194103.GB19150@nagual.pp.ru> <20050121201400.GQ30862@uriah.heep.sax.de> <20050121221156.GA21459@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050121221156.GA21459@nagual.pp.ru> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.8; VDF: 6.29.0.75; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [0.0.0.0]); Sat, 22 Jan 2005 02:28:55 +0300 (MSK) Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 23:28:57 -0000 On Sat, Jan 22, 2005 at 01:11:57AM +0300, Andrey Chernov wrote: > BTW, where was you when this change was discussed and commited by first > time long ago? At those time I don't remember any "against" votes. All > those times passed and nobody complain until this moment. It is good sign > for this change to stay. According to the logs, we have this errno setting since 2001 and no incompatible soft yet found. To late to change rules without an urgent demand. -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 23:32:34 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76CEF16A4CE for ; Fri, 21 Jan 2005 23:32:34 +0000 (GMT) Received: from postfix3-2.free.fr (postfix3-2.free.fr [213.228.0.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id B77BF43D1F for ; Fri, 21 Jan 2005 23:32:33 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix3-2.free.fr (Postfix) with ESMTP id 026E9C010; Sat, 22 Jan 2005 00:32:31 +0100 (CET) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 6BCA8407C; Sat, 22 Jan 2005 00:32:21 +0100 (CET) Date: Sat, 22 Jan 2005 00:32:21 +0100 From: Jeremie Le Hen To: Peter Jeremy Message-ID: <20050121233221.GE36660@obiwan.tataz.chchile.org> References: <20050121151747.GA36660@obiwan.tataz.chchile.org> <50158.208.4.77.66.1106323175.squirrel@208.4.77.66> <20050121183546.GC68808@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="2fHTh5uZTiUOsy+g" Content-Disposition: inline In-Reply-To: <20050121183546.GC68808@cirb503493.alcatel.com.au> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org cc: Jeremie Le Hen Subject: Re: Cannot install kernel as user X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 23:32:34 -0000 --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Jan 22, 2005 at 05:35:46AM +1100, Peter Jeremy wrote: > On Fri, 2005-Jan-21 08:59:35 -0700, Ryan Sommers wrote: > >> I thought about adding a flag such as NO_INSTALLCHOWN in both > >> kern.post.mk and kmod.mk. What do you think of the idea ? > >> > >> I saw there are KMODOWN and KMODGRP in kmod.mk, but it seems there is > >> no similar facility in kern.post.mk. Maybe it would be worth having > >> KERNOWN and KERNGRP as well. > >> > >> I can submit a patch if asked. > > Yes please. Well, firstly I wanted to introduced the NO_INSTALLCHOWN variable as I said in my previous mail, preventing install(8) from doing a chown(2) on the installed file (kernel or module). But I finally decided to use a variable named INSTALLCHOWN which will contain "-o user -g group". This is more flexible and reduces the patch to its simplest form. As Ryan Sommers stated, this patch is not mandatory but I will leave it online [1] as it can be useful for some people. Regards, [1] http://jeremie.le-hen.org/~tataz/patches/FreeBSD/sys.INSTALLCHOWN.patch -- Jeremie Le Hen jeremie@le-hen.org --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="sys.INSTALLCHOWN.patch" Index: conf/kern.post.mk =================================================================== RCS file: /home/ncvs/src/sys/conf/kern.post.mk,v retrieving revision 1.74 diff -u -p -u -p -r1.74 kern.post.mk --- conf/kern.post.mk 1 Dec 2004 23:16:31 -0000 1.74 +++ conf/kern.post.mk 21 Jan 2005 23:18:49 -0000 @@ -14,6 +14,9 @@ MKMODULESENV+= DESTDIR="${DESTDIR}" .endif MKMODULESENV+= KERNBUILDDIR="${.CURDIR}" +# Default to install as root:wheel. +INSTALLCHOWN?= -o root -g wheel + .MAIN: all .for target in all clean cleandepend cleandir clobber depend install \ @@ -211,17 +214,17 @@ kernel-install: .endif mkdir -p ${DESTDIR}${KODIR} .if defined(DEBUG) && defined(INSTALL_DEBUG) - ${INSTALL} -p -m 555 -o root -g wheel ${FULLKERNEL} ${DESTDIR}${KODIR} + ${INSTALL} -p -m 555 ${INSTALLCHOWN} ${FULLKERNEL} ${DESTDIR}${KODIR} .else - ${INSTALL} -p -m 555 -o root -g wheel ${KERNEL_KO} ${DESTDIR}${KODIR} + ${INSTALL} -p -m 555 ${INSTALLCHOWN} ${KERNEL_KO} ${DESTDIR}${KODIR} .endif kernel-reinstall: @-chflags -R noschg ${DESTDIR}${KODIR} .if defined(DEBUG) && defined(INSTALL_DEBUG) - ${INSTALL} -p -m 555 -o root -g wheel ${FULLKERNEL} ${DESTDIR}${KODIR} + ${INSTALL} -p -m 555 ${INSTALLCHOWN} ${FULLKERNEL} ${DESTDIR}${KODIR} .else - ${INSTALL} -p -m 555 -o root -g wheel ${KERNEL_KO} ${DESTDIR}${KODIR} + ${INSTALL} -p -m 555 ${INSTALLCHOWN} ${KERNEL_KO} ${DESTDIR}${KODIR} .endif config.o env.o hints.o majors.o vers.o vnode_if.o: Index: conf/kmod.mk =================================================================== RCS file: /home/ncvs/src/sys/conf/kmod.mk,v retrieving revision 1.176 diff -u -p -u -p -r1.176 kmod.mk --- conf/kmod.mk 8 Dec 2004 07:23:12 -0000 1.176 +++ conf/kmod.mk 21 Jan 2005 23:18:41 -0000 @@ -225,6 +225,8 @@ _INSTALLFLAGS:= ${INSTALLFLAGS} _INSTALLFLAGS:= ${_INSTALLFLAGS${ie}} .endfor +INSTALLCHOWN?= -o ${KMODOWN} -g ${KMODGRP} + .if !target(install.debug) && defined(DEBUG_FLAGS) install.debug: cd ${.CURDIR}; ${MAKE} -DINSTALL_DEBUG install @@ -235,10 +237,10 @@ realinstall: _kmodinstall .ORDER: beforeinstall _kmodinstall _kmodinstall: .if defined(DEBUG_FLAGS) && defined(INSTALL_DEBUG) - ${INSTALL} -o ${KMODOWN} -g ${KMODGRP} -m ${KMODMODE} \ + ${INSTALL} ${INSTALLCHOWN} -m ${KMODMODE} \ ${_INSTALLFLAGS} ${FULLPROG} ${DESTDIR}${KMODDIR} .else - ${INSTALL} -o ${KMODOWN} -g ${KMODGRP} -m ${KMODMODE} \ + ${INSTALL} ${INSTALLCHOWN} -m ${KMODMODE} \ ${_INSTALLFLAGS} ${PROG} ${DESTDIR}${KMODDIR} .include --2fHTh5uZTiUOsy+g-- From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 00:39:31 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 735E916A4CE; Sat, 22 Jan 2005 00:39:31 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id D948243D2D; Sat, 22 Jan 2005 00:39:30 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j0M0d0dx050332; Fri, 21 Jan 2005 17:39:00 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 21 Jan 2005 17:40:14 -0700 (MST) Message-Id: <20050121.174014.26534401.imp@bsdimp.com> To: scottl@freebsd.org From: "M. Warner Losh" In-Reply-To: <41F00697.7010000@freebsd.org> References: <20050120140300.F1832@bahre.achedra.org> <41F00697.7010000@freebsd.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: ketrien@error404.nls.net cc: current@freebsd.org cc: bmilekic@freebsd.org Subject: Re: Memory modified after free - Jan20 -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 00:39:31 -0000 In message: <41F00697.7010000@freebsd.org> Scott Long writes: : Ketrien I. Saihr-Kenchedra wrote: : : > Screen transcription attached. In a nutshell; : > : > fdc0: port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 : > device_attach: fdc0 returned 6 : > sio0: <16550A-compatible COM port> port0x3f8-0x3ff irq 4 flags 0x10 on : > acpi0 : > sio0: type 16550A : > Memory modified after free 0xc1cde200(252) val=0 @ 0xc1cde228 : > panic: Most recently used by none : > : > System was fine with Jan16 srcs, fdc returning 6 is new. Looks like a uma : > problem to me, but odd enough that I'm honestly not sure. Need ips(4) for : > dumpdev, so no dump again. (Argh.) : > : : I'm seeing this quite often too. I'm hoping that Bosko will make his : memguard changes available soon as I'm sure it could quickly be tracked : down with them. This one is mine, and was in the tree for only about 9 hours and should be fixed now. Warner From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 00:41:56 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DE7A16A4D0 for ; Sat, 22 Jan 2005 00:41:56 +0000 (GMT) Received: from postfix3-1.free.fr (postfix3-1.free.fr [213.228.0.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 434E143D2F for ; Sat, 22 Jan 2005 00:41:56 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix3-1.free.fr (Postfix) with ESMTP id 171FD173495; Sat, 22 Jan 2005 01:41:54 +0100 (CET) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id C6651407C; Sat, 22 Jan 2005 01:41:45 +0100 (CET) Date: Sat, 22 Jan 2005 01:41:45 +0100 From: Jeremie Le Hen To: Peter Jeremy Message-ID: <20050122004145.GF36660@obiwan.tataz.chchile.org> References: <20050121151747.GA36660@obiwan.tataz.chchile.org> <50158.208.4.77.66.1106323175.squirrel@208.4.77.66> <20050121183546.GC68808@cirb503493.alcatel.com.au> <20050121233221.GE36660@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050121233221.GE36660@obiwan.tataz.chchile.org> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org cc: Jeremie Le Hen Subject: Re: Cannot install kernel as user X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 00:41:56 -0000 > Well, firstly I wanted to introduced the NO_INSTALLCHOWN variable as I > said in my previous mail, preventing install(8) from doing a chown(2) > on the installed file (kernel or module). But I finally decided to > use a variable named INSTALLCHOWN which will contain "-o user -g group". > This is more flexible and reduces the patch to its simplest form. Sorry I'm quite tired, I realize I didn't give a good explanation. INSTALLCHOWN will default to o "-o root -g wheel" when installing kernel, o "-o ${KMODOWN} -g {KMODGRP}" when installing module. It can be overrided to whatever you want and in particular, it may be set to nothing when you want to install as user (no chown(2) performed). -- Jeremie Le Hen jeremie@le-hen.org From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 00:56:17 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2FBA16A4D0 for ; Sat, 22 Jan 2005 00:56:17 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 246BC43D46 for ; Sat, 22 Jan 2005 00:56:09 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 2872B51194; Fri, 21 Jan 2005 16:56:01 -0800 (PST) Date: Fri, 21 Jan 2005 16:56:01 -0800 From: Kris Kennaway To: current@FreeBSD.org Message-ID: <20050122005600.GA88488@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qMm9M+Fa2AknHoGS" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: panic: Assertion td->td_sleepqueue != NULL failed at ../../../kern/subr_sleepqueue.c:270 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 00:56:18 -0000 --qMm9M+Fa2AknHoGS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 6.0 from yesterday with 4BSD, PREEMPTION on (yes, I know :-) panic: Assertion td->td_sleepqueue !=3D NULL failed at ../../../kern/subr_s= leepqueue.c:270 cpuid =3D 1 KDB: enter: panic KDB: stack backtrace: kdb_backtrace(c0750a20,0,c06f1644,13b,25d3eb11) at kdb_backtrace+0x2f mi_switch(2,0,c06f253c,252,0) at mi_switch+0x1d8 critical_exit(c07456e0,250,0,ea0a1c9c,0) at critical_exit+0xb0 intr_execute_handlers(c07456e0,ea0a1cb4,0,ea0a1cac,1) at intr_execute_handl= ers+0xcc atpic_handle_intr(0) at atpic_handle_intr+0xd0 Xatpic_intr0() at Xatpic_intr0+0x20 --- interrupt, eip =3D 0xc0531d06, esp =3D 0xea0a1cf8, ebp =3D 0xea0a1d14 -= -- sched_runnable(0,ea0a1d48,c06ee6c7,30e,0) at sched_runnable fork_exit(c050876b,0,ea0a1d48) at fork_exit+0xc7 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip =3D 0, esp =3D 0xea0a1d7c, ebp =3D 0 --- It hung here, as usual for SMP panics.=20 Kris --qMm9M+Fa2AknHoGS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB8aSgWry0BWjoQKURAnxNAKCJZ/y7Wc0FxAQNZz9iiJf8xJnGWwCgw2l0 /qJ5M4hDMv43ie1bNyye474= =EQUS -----END PGP SIGNATURE----- --qMm9M+Fa2AknHoGS-- From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 01:18:54 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7624716A4CE for ; Sat, 22 Jan 2005 01:18:54 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0E5343D1D for ; Sat, 22 Jan 2005 01:18:53 +0000 (GMT) (envelope-from bbunch@gmail.com) Received: by wproxy.gmail.com with SMTP id 71so174231wra for ; Fri, 21 Jan 2005 17:18:49 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=uuzzQZo8s6d7BPDZsgu1VQuJgVFVPvdq5z2RwkixYL9K/hH8l9tq7Hxxy3svAI9kDoKxD7WyDAkFaAifxeHQ+g1Se6Rz8xyfUhfUf80KWYCEzfIS5Ty5pEmRY8WyOmEZ4utKaOnHhuIsivE5vmreknPk7t9NqhdsMT0o75eQwcc= Received: by 10.54.52.40 with SMTP id z40mr361091wrz; Fri, 21 Jan 2005 17:18:49 -0800 (PST) Received: by 10.54.13.30 with HTTP; Fri, 21 Jan 2005 17:18:47 -0800 (PST) Message-ID: Date: Fri, 21 Jan 2005 19:18:47 -0600 From: Bryan Bunch To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: WPA with ath X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bryan Bunch List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 01:18:54 -0000 Hello All, I am having a little trouble getting my WiFi card to work properly. --Card - Netgear WGS511T -- I am running FreeBSD 6.0-CURRENT #0: Fri Jan 21 16:03:10 CST 2005 . -- The latest port of wpa_supplicant. My kernel has the following necessary lines: # Wireless NIC cards device wlan # 802.11 support device ath device ath_hal device ath_rate_onoe Below is the process I am using: -- Boot machine -- kldload wlan_tkip -- Put card in PCMCIA slot and I get the message saying that it sees the card. -- do a ifconfig ath0 up -- wpa_supplicant -iath0 -c /usr/local/etc/wpa_supplicant.conf Below is some of the output I get: ========================= Trying to associate with 00:0c:41:f3:bd:a2 (SSID='1024' freq=2437 MHz) Associated with 00:0c:41:f3:bd:a2 WPA: Key negotiation completed with 00:0c:41:f3:bd:a2 [PTK=TKIP GTK=TKIP] WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] Disconnect event - remove keys Associated with 00:0c:41:f3:bd:a2 WPA: Key negotiation completed with 00:0c:41:f3:bd:a2 [PTK=TKIP GTK=TKIP] WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] Disconnect event - remove keys Associated with 00:0c:41:f3:bd:a2 WPA: Key negotiation completed with 00:0c:41:f3:bd:a2 [PTK=TKIP GTK=TKIP] WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] ============================= I keep getting the same thing over and over. I'm assuming it's working since if I go to a terminal window and do a ifconfig, I get: ================== ath0: flags=8843 mtu 1500 inet6 fe80::209:5bff:fec8:2255%ath0 prefixlen 64 scopeid 0x4 ether 00:09:5b:c8:22:55 media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/36Mbps) status: associated ssid 1024 channel 6 bssid 00:0c:41:f3:bd:a2 authmode WPA1+WPA2/802.11i privacy ON deftxkey 1 TKIP 1:128-bit <0a718f0eeaef5e32086fcccaca5ba6ba> rsc 3 tsc 1 TKIP 3:128-bit <86d5577cc68329ad2fb6f9e7a212fb49> rsc 16 tsc 1 txpowmax 43 protmode CTS roaming MANUAL bintval 100 ================== BUT when I try and do a: ifconfig ath0 inet 192.168.1.40 netmask 255.255.255.0 The address appears under the ifconfig, but I cannot go anywhere. I can ping the local interface, but nothing outside of it. What am I doing wrong? Thanks for any help/guidance. Bryan From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 01:21:32 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 57C9E16A4D6 for ; Sat, 22 Jan 2005 01:21:32 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27E3543D2F for ; Sat, 22 Jan 2005 01:21:32 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id BB55A7A425; Fri, 21 Jan 2005 17:21:31 -0800 (PST) Message-ID: <41F1AA9B.4070603@elischer.org> Date: Fri, 21 Jan 2005 17:21:31 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Ryan Sommers References: <20050121151747.GA36660@obiwan.tataz.chchile.org> <50158.208.4.77.66.1106323175.squirrel@208.4.77.66> In-Reply-To: <50158.208.4.77.66.1106323175.squirrel@208.4.77.66> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: Jeremie Le Hen Subject: Re: Cannot install kernel as user X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 01:21:32 -0000 Ryan Sommers wrote: >Jeremie Le Hen said: > > >>Hi, >> >>my laptop is a very slow beast but this is the only computer I can >>actually run -CURRENT on. In order to parallelize task, when my laptop >>is fsck'ing after a panic, I use a collegue's computer on which I have >>a shell to build the new kernel. Everything works quite well, except >>that when I install the kernel, install(8) will stop on chown(2) : >> >>%%% >> propane:Z6PO$ make KERNEL=kernel.test DESTDIR=$HOME/export install >> [...] >> mkdir -p /home/tataz/export/boot/kernel.test >> install -p -m 555 -o root -g wheel kernel >>/home/tataz/export/boot/kernel.test >> install: /home/tataz/export/boot/kernel.test/kernel: chown/chgrp: >>Operation not permitted >> *** Error code 71 >> >> Stop in /usr/home/tataz/FreeBSD/CURRENT/src/sys/i386/compile/Z6PO. >>%%% >> >>I thought about adding a flag such as NO_INSTALLCHOWN in both >>kern.post.mk and kmod.mk. What do you think of the idea ? >> >>I saw there are KMODOWN and KMODGRP in kmod.mk, but it seems there is >>no similar facility in kern.post.mk. Maybe it would be worth having >>KERNOWN and KERNGRP as well. >> >>I can submit a patch if asked. >> >> > >I'm trying to think where this would be useful outside your particular >situation. I'm not sure there is a lot of use. > It's also useful when doing a build inside a jail as flags cannot be changed insode a jail. I got around it by replacing 'chflags' in the jail by a shell script the does nothing :-). > >The official way to do what you are looking to do is to mount it the other >way. On the build machine export the src/obj directories and mount them on >the target machine. Then execute your make install from the target >machine. Otherwise you run into problems like you are running into. >Especially if you're running an install as a non-root user. > > > From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 05:19:23 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9F0C216A4CE for ; Sat, 22 Jan 2005 05:19:23 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5337043D5F for ; Sat, 22 Jan 2005 05:19:23 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.92] ([66.127.85.92]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id j0M5JMWi089736 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Jan 2005 21:19:22 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <41F1E26E.8030200@errno.com> Date: Fri, 21 Jan 2005 21:19:42 -0800 From: Sam Leffler Organization: Errno Consulting User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bryan Bunch References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: WPA with ath X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 05:19:23 -0000 Bryan Bunch wrote: > Hello All, > > I am having a little trouble getting my WiFi card to work properly. > > --Card - Netgear WGS511T > -- I am running FreeBSD 6.0-CURRENT #0: Fri Jan 21 16:03:10 CST 2005 . > -- The latest port of wpa_supplicant. > > My kernel has the following necessary lines: > # Wireless NIC cards > device wlan # 802.11 support > device ath > device ath_hal > device ath_rate_onoe > > Below is the process I am using: > -- Boot machine > -- kldload wlan_tkip > -- Put card in PCMCIA slot and I get the message saying that it sees the card. > -- do a ifconfig ath0 up > -- wpa_supplicant -iath0 -c /usr/local/etc/wpa_supplicant.conf > > Below is some of the output I get: > ========================= > Trying to associate with 00:0c:41:f3:bd:a2 (SSID='1024' freq=2437 MHz) > Associated with 00:0c:41:f3:bd:a2 > WPA: Key negotiation completed with 00:0c:41:f3:bd:a2 [PTK=TKIP GTK=TKIP] > WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] > WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] > WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] > Disconnect event - remove keys > Associated with 00:0c:41:f3:bd:a2 > WPA: Key negotiation completed with 00:0c:41:f3:bd:a2 [PTK=TKIP GTK=TKIP] > WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] > WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] > WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] > Disconnect event - remove keys > Associated with 00:0c:41:f3:bd:a2 > WPA: Key negotiation completed with 00:0c:41:f3:bd:a2 [PTK=TKIP GTK=TKIP] > WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] > WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] > WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] > ============================= "Disconnect event" means the AP sent the station a disconnect message. You need to figure out why; there's nothing here to explain what happened. > > I keep getting the same thing over and over. I'm assuming it's working > since if I go to a terminal window and do a ifconfig, I get: > > ================== > ath0: flags=8843 mtu 1500 > inet6 fe80::209:5bff:fec8:2255%ath0 prefixlen 64 scopeid 0x4 > ether 00:09:5b:c8:22:55 > media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/36Mbps) > status: associated > ssid 1024 channel 6 bssid 00:0c:41:f3:bd:a2 > authmode WPA1+WPA2/802.11i privacy ON deftxkey 1 > TKIP 1:128-bit <0a718f0eeaef5e32086fcccaca5ba6ba> rsc 3 tsc 1 > TKIP 3:128-bit <86d5577cc68329ad2fb6f9e7a212fb49> rsc 16 tsc 1 > txpowmax 43 protmode CTS roaming MANUAL bintval 100 > > ================== > > BUT when I try and do a: > > ifconfig ath0 inet 192.168.1.40 netmask 255.255.255.0 > > The address appears under the ifconfig, but I cannot go anywhere. I > can ping the local interface, but nothing outside of it. > > What am I doing wrong? What's the AP? Try running wpa_supplicant with a -d option to get more debug info (though it's not clear there'll be anything useful to see). Sam From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 06:09:00 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02D2516A4CE for ; Sat, 22 Jan 2005 06:09:00 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 503A943D41 for ; Sat, 22 Jan 2005 06:08:59 +0000 (GMT) (envelope-from bbunch@gmail.com) Received: by wproxy.gmail.com with SMTP id 71so190509wra for ; Fri, 21 Jan 2005 22:08:58 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=aF9li7dn0D4lwFk+lFituQ2cmccbDrPwrQCx3zHcKYe2ScZHcESwMraCN+4zMEd8cYCIZjXD51BY+tbRFqLKUfXq/xo5SF+qqY9fcRWZcl26hkbyp8x4sZOvaaTVvZgkg6ImTX/vPw9HfAAsBwNfU/iXryMe3CU8PbR6cFCaWxc= Received: by 10.54.40.55 with SMTP id n55mr556800wrn; Fri, 21 Jan 2005 22:08:58 -0800 (PST) Received: by 10.54.13.30 with HTTP; Fri, 21 Jan 2005 22:08:58 -0800 (PST) Message-ID: Date: Sat, 22 Jan 2005 00:08:58 -0600 From: Bryan Bunch To: freebsd-current@freebsd.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <41F1E26E.8030200@errno.com> Subject: Re: WPA with ath X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bryan Bunch List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 06:09:00 -0000 I'm trying to connect to a Linksys WRT54G. I have tested the card on the computer when booting up in XP and it connects fine via WPA. I also tested the card in CURRENT with WPA disabled and the card connected fine. > What's the AP? Try running wpa_supplicant with a -d option to get more > debug info (though it's not clear there'll be anything useful to see). > > Sam > Below is some output from -d (I can provide more if needed): ============================= Initializing interface 'ath0' conf '/usr/local/etc/wpa_supplicant.conf' driver 'default' Configuration file '/usr/local/etc/wpa_supplicant.conf' -> '/usr/local/etc/wpa_supplicant.conf' Reading configuration file '/usr/local/etc/wpa_supplicant.conf' ctrl_interface='/var/run/wpa_supplicant' ctrl_interface_group=0 eapol_version=1 ap_scan=1 fast_reauth=1 Priority group 5 id=0 ssid='1024' Initializing interface (2) 'ath0' EAPOL: SUPP_PAE entering state DISCONNECTED EAPOL: KEY_RX entering state NO_KEY_RECEIVE EAPOL: SUPP_BE entering state INITIALIZE EAP: EAP entering state DISABLED EAPOL: External notification - portEnabled=0 EAPOL: External notification - portValid=0 Own MAC address: 00:09:5b:c8:22:55 wpa_driver_bsd_set_wpa: enabled=1 wpa_driver_bsd_del_key: keyidx=0 wpa_driver_bsd_del_key: keyidx=1 wpa_driver_bsd_del_key: keyidx=2 wpa_driver_bsd_del_key: keyidx=3 wpa_driver_bsd_set_countermeasures: enabled=0 wpa_driver_bsd_set_drop_unencrypted: enabled=1 Setting scan request: 0 sec 100000 usec Starting AP scan (broadcast SSID) Received 0 bytes of scan results (1 BSSes) Scan results: 1 Selecting BSS from priority group 5 0: 00:0c:41:f3:bd:a2 ssid='1024' wpa_ie_len=24 rsn_ie_len=0 selected Trying to associate with 00:0c:41:f3:bd:a2 (SSID='1024' freq=2437 MHz) Cancelling scan request Automatic auth_alg selection: 0x1 WPA: using IEEE 802.11i/D3.0 WPA: using GTK TKIP WPA: using PTK TKIP WPA: using KEY_MGMT WPA-PSK WPA: Own WPA IE - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 No keys have been configured - skip key clearing wpa_driver_bsd_set_drop_unencrypted: enabled=1 wpa_driver_bsd_associate Setting authentication timeout: 5 sec 0 usec EAPOL: External notification - EAP success=0 EAPOL: External notification - EAP fail=0 EAPOL: External notification - portControl=Auto Association event - clear replay counter Associated to a new BSS: BSSID=00:0c:41:f3:bd:a2 No keys have been configured - skip key clearing Associated with 00:0c:41:f3:bd:a2 EAPOL: External notification - portValid=0 EAPOL: External notification - EAP success=0 EAPOL: External notification - portEnabled=1 EAPOL: SUPP_PAE entering state CONNECTING EAPOL: txStart WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0) EAPOL: SUPP_BE entering state IDLE EAP: EAP entering state INITIALIZE EAP: EAP entering state IDLE Setting authentication timeout: 10 sec 0 usec RX EAPOL from 00:0c:41:f3:bd:a2 Setting authentication timeout: 10 sec 0 usec EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines IEEE 802.1X RX: version=1 type=3 length=95 EAPOL-Key type=254 WPA: RX message 1 of 4-Way Handshake from 00:0c:41:f3:bd:a2 (ver=1) WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 WPA: Renewed SNonce - hexdump(len=32): d8 2d 91 f5 90 5b 9c 0d ca 85 a4 97 97 a7 ae e8 07 01 69 28 f4 2c e3 9d 5d 6e 65 47 db 51 79 01 WPA: PMK - hexdump(len=32): [REMOVED] WPA: PTK - hexdump(len=64): [REMOVED] WPA: EAPOL-Key MIC - hexdump(len=16): 42 04 40 a5 9d 57 01 20 ce d4 11 d5 4d 14 56 aa WPA: Sending EAPOL-Key 2/4 RX EAPOL from 00:0c:41:f3:bd:a2 EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines IEEE 802.1X RX: version=1 type=3 length=119 EAPOL-Key type=254 WPA: RX message 3 of 4-Way Handshake from 00:0c:41:f3:bd:a2 (ver=1) WPA: IE KeyData - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 WPA: Sending EAPOL-Key 4/4 WPA: Installing PTK to the driver. WPA: RSC - hexdump(len=6): 00 00 00 00 00 00 wpa_driver_bsd_set_key: alg=TKIP key_idx=0 set_tx=1 seq_len=6 key_len=32 RX EAPOL from 00:0c:41:f3:bd:a2 EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines IEEE 802.1X RX: version=1 type=3 length=127 EAPOL-Key type=254 WPA: RX message 1 of Group Key Handshake from 00:0c:41:f3:bd:a2 (ver=1) WPA: Group Key - hexdump(len=32): [REMOVED] WPA: Installing GTK to the driver (keyidx=2 tx=0). WPA: RSC - hexdump(len=6): a0 01 00 00 00 00 wpa_driver_bsd_set_key: alg=TKIP key_idx=2 set_tx=0 seq_len=6 key_len=32 WPA: Sending EAPOL-Key 2/2 WPA: Key negotiation completed with 00:0c:41:f3:bd:a2 [PTK=TKIP GTK=TKIP] Cancelling authentication timeout EAPOL: External notification - portValid=1 EAPOL: External notification - EAP success=1 EAPOL: SUPP_PAE entering state AUTHENTICATING EAPOL: SUPP_BE entering state SUCCESS EAPOL: SUPP_PAE entering state AUTHENTICATED EAPOL: SUPP_BE entering state IDLE RX EAPOL from 00:0c:41:f3:bd:a2 EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines IEEE 802.1X RX: version=1 type=3 length=127 EAPOL-Key type=254 WPA: RX message 1 of Group Key Handshake from 00:0c:41:f3:bd:a2 (ver=1) WPA: Group Key - hexdump(len=32): [REMOVED] WPA: Installing GTK to the driver (keyidx=2 tx=0). WPA: RSC - hexdump(len=6): a0 01 00 00 00 00 wpa_driver_bsd_set_key: alg=TKIP key_idx=2 set_tx=0 seq_len=6 key_len=32 WPA: Sending EAPOL-Key 2/2 WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] RX EAPOL from 00:0c:41:f3:bd:a2 EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines IEEE 802.1X RX: version=1 type=3 length=127 EAPOL-Key type=254 WPA: RX message 1 of Group Key Handshake from 00:0c:41:f3:bd:a2 (ver=1) WPA: Group Key - hexdump(len=32): [REMOVED] WPA: Installing GTK to the driver (keyidx=2 tx=0). WPA: RSC - hexdump(len=6): a0 01 00 00 00 00 wpa_driver_bsd_set_key: alg=TKIP key_idx=2 set_tx=0 seq_len=6 key_len=32 WPA: Sending EAPOL-Key 2/2 WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] Setting scan request: 0 sec 100000 usec EAPOL: External notification - portEnabled=0 EAPOL: SUPP_PAE entering state DISCONNECTED EAPOL: SUPP_BE entering state INITIALIZE EAP: EAP entering state DISABLED EAPOL: External notification - portValid=0 EAPOL: External notification - EAP success=0 Disconnect event - remove keys wpa_driver_bsd_del_key: keyidx=0 wpa_driver_bsd_del_key: keyidx=1 wpa_driver_bsd_del_key: keyidx=2 wpa_driver_bsd_del_key: keyidx=3 wpa_driver_bsd_del_key: keyidx=0 Association event - clear replay counter Associated to a new BSS: BSSID=00:0c:41:f3:bd:a2 No keys have been configured - skip key clearing Associated with 00:0c:41:f3:bd:a2 EAPOL: External notification - portValid=0 EAPOL: External notification - EAP success=0 EAPOL: External notification - portEnabled=1 EAPOL: SUPP_PAE entering state CONNECTING EAPOL: txStart WPA: drop TX EAPOL in non-IEEE 802.1X mode (type=1 len=0) EAPOL: SUPP_BE entering state IDLE EAP: EAP entering state INITIALIZE EAP: EAP entering state IDLE Setting authentication timeout: 10 sec 0 usec RX EAPOL from 00:0c:41:f3:bd:a2 Setting authentication timeout: 10 sec 0 usec EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines IEEE 802.1X RX: version=1 type=3 length=95 EAPOL-Key type=254 WPA: RX message 1 of 4-Way Handshake from 00:0c:41:f3:bd:a2 (ver=1) WPA: WPA IE for msg 2/4 - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 WPA: Renewed SNonce - hexdump(len=32): a8 fd 94 f8 09 5b cf b6 da b5 97 b2 7f 5d 87 d8 29 b5 1f 0c b9 2c 53 4e bf ad 84 9f bd 2f 71 1c WPA: PMK - hexdump(len=32): [REMOVED] WPA: PTK - hexdump(len=64): [REMOVED] WPA: EAPOL-Key MIC - hexdump(len=16): 3b d6 c6 20 7a 54 5b 84 89 93 50 df 46 8d 04 d6 WPA: Sending EAPOL-Key 2/4 RX EAPOL from 00:0c:41:f3:bd:a2 EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines IEEE 802.1X RX: version=1 type=3 length=119 EAPOL-Key type=254 WPA: RX message 3 of 4-Way Handshake from 00:0c:41:f3:bd:a2 (ver=1) WPA: IE KeyData - hexdump(len=24): dd 16 00 50 f2 01 01 00 00 50 f2 02 01 00 00 50 f2 02 01 00 00 50 f2 02 WPA: Sending EAPOL-Key 4/4 WPA: Installing PTK to the driver. WPA: RSC - hexdump(len=6): 00 00 00 00 00 00 wpa_driver_bsd_set_key: alg=TKIP key_idx=0 set_tx=1 seq_len=6 key_len=32 RX EAPOL from 00:0c:41:f3:bd:a2 EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines IEEE 802.1X RX: version=1 type=3 length=127 EAPOL-Key type=254 WPA: RX message 1 of Group Key Handshake from 00:0c:41:f3:bd:a2 (ver=1) WPA: Group Key - hexdump(len=32): [REMOVED] WPA: Installing GTK to the driver (keyidx=2 tx=0). WPA: RSC - hexdump(len=6): a0 01 00 00 00 00 wpa_driver_bsd_set_key: alg=TKIP key_idx=2 set_tx=0 seq_len=6 key_len=32 WPA: Sending EAPOL-Key 2/2 WPA: Key negotiation completed with 00:0c:41:f3:bd:a2 [PTK=TKIP GTK=TKIP] Cancelling authentication timeout EAPOL: External notification - portValid=1 EAPOL: External notification - EAP success=1 EAPOL: SUPP_PAE entering state AUTHENTICATING EAPOL: SUPP_BE entering state SUCCESS EAPOL: SUPP_PAE entering state AUTHENTICATED EAPOL: SUPP_BE entering state IDLE RX EAPOL from 00:0c:41:f3:bd:a2 EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines IEEE 802.1X RX: version=1 type=3 length=127 EAPOL-Key type=254 WPA: RX message 1 of Group Key Handshake from 00:0c:41:f3:bd:a2 (ver=1) WPA: Group Key - hexdump(len=32): [REMOVED] WPA: Installing GTK to the driver (keyidx=2 tx=0). WPA: RSC - hexdump(len=6): a0 01 00 00 00 00 wpa_driver_bsd_set_key: alg=TKIP key_idx=2 set_tx=0 seq_len=6 key_len=32 WPA: Sending EAPOL-Key 2/2 WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] RX EAPOL from 00:0c:41:f3:bd:a2 EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines IEEE 802.1X RX: version=1 type=3 length=127 EAPOL-Key type=254 WPA: RX message 1 of Group Key Handshake from 00:0c:41:f3:bd:a2 (ver=1) WPA: Group Key - hexdump(len=32): [REMOVED] WPA: Installing GTK to the driver (keyidx=2 tx=0). WPA: RSC - hexdump(len=6): a0 01 00 00 00 00 wpa_driver_bsd_set_key: alg=TKIP key_idx=2 set_tx=0 seq_len=6 key_len=32 WPA: Sending EAPOL-Key 2/2 WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] RX EAPOL from 00:0c:41:f3:bd:a2 EAPOL: Ignoring WPA EAPOL-Key frame in EAPOL state machines IEEE 802.1X RX: version=1 type=3 length=127 EAPOL-Key type=254 WPA: RX message 1 of Group Key Handshake from 00:0c:41:f3:bd:a2 (ver=1) WPA: Group Key - hexdump(len=32): [REMOVED] WPA: Installing GTK to the driver (keyidx=2 tx=0). WPA: RSC - hexdump(len=6): a0 01 00 00 00 00 wpa_driver_bsd_set_key: alg=TKIP key_idx=2 set_tx=0 seq_len=6 key_len=32 WPA: Sending EAPOL-Key 2/2 WPA: Group rekeying completed with 00:0c:41:f3:bd:a2 [GTK=TKIP] Setting scan request: 0 sec 100000 usec EAPOL: External notification - portEnabled=0 EAPOL: SUPP_PAE entering state DISCONNECTED EAPOL: SUPP_BE entering state INITIALIZE EAP: EAP entering state DISABLED EAPOL: External notification - portValid=0 EAPOL: External notification - EAP success=0 Disconnect event - remove keys wpa_driver_bsd_del_key: keyidx=0 wpa_driver_bsd_del_key: keyidx=1 wpa_driver_bsd_del_key: keyidx=2 wpa_driver_bsd_del_key: keyidx=3 wpa_driver_bsd_del_key: keyidx=0 Association event - clear replay counter Associated to a new BSS: BSSID=00:0c:41:f3:bd:a2 No keys have been configured - skip key clearing Associated with 00:0c:41:f3:bd:a2 EAPOL: External notification - portValid=0 EAPOL: External notification - EAP success=0 EAPOL: External notification - portEnabled=1 EAPOL: SUPP_PAE entering state CONNECTING EAPOL: txStart ====================== Thanks for your help. Bryan From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 09:45:11 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C7C916A4CE; Sat, 22 Jan 2005 09:45:11 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0B0443D1D; Sat, 22 Jan 2005 09:45:09 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id A76AD1FFDD8; Sat, 22 Jan 2005 10:45:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id CAABC1FFDD4; Sat, 22 Jan 2005 10:45:05 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id B0F601538F; Sat, 22 Jan 2005 09:41:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id AD9D315380; Sat, 22 Jan 2005 09:41:25 +0000 (UTC) Date: Sat, 22 Jan 2005 09:41:25 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: FreeBSD current mailing list Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: FreeBSD net mailing list Subject: Re: mem leak in mii ? (fwd) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 09:45:11 -0000 Hi, third and last call for review and comments. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT ---------- Forwarded message ---------- Date: Mon, 20 Dec 2004 12:23:39 +0000 (UTC) From: Bjoern A. Zeeb To: FreeBSD current mailing list Cc: FreeBSD net mailing list Subject: Re: mem leak in mii ? (fwd) Hi, haven't had any feedback on this.... Can someone please review? Also answers to the questions would be welcome. Thanks. ---------- Forwarded message ---------- Date: Tue, 23 Nov 2004 19:31:10 +0000 (UTC) From: Bjoern A. Zeeb To: John Baldwin Cc: Bjoern A. Zeeb , freebsd-current@FreeBSD.org Subject: Re: mem leak in mii ? On Mon, 22 Nov 2004, John Baldwin wrote: Hi, hope you won't get it twice; the first one didn't seem to go out... > On Friday 19 November 2004 06:49 pm, Bjoern A. Zeeb wrote: > > Hi, > > > > in sys/dev/mii/mii.c there are two calls to malloc for ivars; > > see for example mii_phy_probe: .. > > Where is the free for this malloc ? I cannot find it. > > > > analogous: miibus_probe ? > > It's a leak. It should be free'd when the miibus device is destroyed. Here's > a possible fix: could you please review this one ? Should plug both of the memleaks; also for more error cases. notes: * mii doesn't ssem to be very error corrective and reporting; as others currently also seem to be debugging problems with undetectable PHYs I added some error handling in those places that I touched anyway. * in miibus_probe in the loop there is the possibility - and the comment above the functions also talks about this - that we find more than one PHY ? I currrently doubt that but I don't know for sure. As device_add_child may return NULL we cannot check for that; I had seen some inconsistency while debugging the BMSR_MEDIAMASK check so I added the count variable for this to have a reliable state. * all PHY drivers currently seem to use mii_phy_detach for device_detach. If any implements his own function it will be responsible for freeing the ivars allocated in miibus_probe. This should perhaps be documented somewhere ? patch can also be found at http://sources.zabbadoz.net/freebsd/patchset/mii-memleaks.diff Index: mii.c =================================================================== RCS file: /local/mirror/FreeBSD/r/ncvs/src/sys/dev/mii/mii.c,v retrieving revision 1.20 diff -u -p -r1.20 mii.c --- mii.c 15 Aug 2004 06:24:40 -0000 1.20 +++ mii.c 23 Nov 2004 17:08:58 -0000 @@ -111,7 +111,7 @@ miibus_probe(dev) struct mii_attach_args ma, *args; struct mii_data *mii; device_t child = NULL, parent; - int bmsr, capmask = 0xFFFFFFFF; + int count = 0, bmsr, capmask = 0xFFFFFFFF; mii = device_get_softc(dev); parent = device_get_parent(dev); @@ -145,12 +145,26 @@ miibus_probe(dev) args = malloc(sizeof(struct mii_attach_args), M_DEVBUF, M_NOWAIT); + if (args == NULL) { + device_printf(dev, "%s: memory allocation failure, " + "phyno %d", __func__, ma.mii_phyno); + continue; + } bcopy((char *)&ma, (char *)args, sizeof(ma)); child = device_add_child(dev, NULL, -1); + if (child == NULL) { + free(args, M_DEVBUF); + device_printf(dev, "%s: device_add_child failed", + __func__); + continue; + } device_set_ivars(child, args); + count++; + /* XXX should we break here or is it really possible + * to find more then one PHY ? */ } - if (child == NULL) + if (count == 0) return(ENXIO); device_set_desc(dev, "MII bus"); @@ -173,12 +187,15 @@ miibus_attach(dev) */ mii->mii_ifp = device_get_softc(device_get_parent(dev)); v = device_get_ivars(dev); + if (v == NULL) + return (ENXIO); ifmedia_upd = v[0]; ifmedia_sts = v[1]; + device_set_ivars(dev, NULL); + free(v, M_DEVBUF); ifmedia_init(&mii->mii_media, IFM_IMASK, ifmedia_upd, ifmedia_sts); - bus_generic_attach(dev); - return(0); + return (bus_generic_attach(dev)); } int @@ -186,8 +203,14 @@ miibus_detach(dev) device_t dev; { struct mii_data *mii; + void *v; bus_generic_detach(dev); + v = device_get_ivars(dev); + if (v != NULL) { + device_set_ivars(dev, NULL); + free(v, M_DEVBUF); + } mii = device_get_softc(dev); ifmedia_removeall(&mii->mii_media); mii->mii_ifp = NULL; @@ -305,12 +328,15 @@ mii_phy_probe(dev, child, ifmedia_upd, i int bmsr, i; v = malloc(sizeof(vm_offset_t) * 2, M_DEVBUF, M_NOWAIT); - if (v == 0) { + if (v == NULL) return (ENOMEM); - } v[0] = ifmedia_upd; v[1] = ifmedia_sts; *child = device_add_child(dev, "miibus", -1); + if (*child == NULL) { + free(v, M_DEVBUF); + return (ENXIO); + } device_set_ivars(*child, v); for (i = 0; i < MII_NPHY; i++) { @@ -324,14 +350,22 @@ mii_phy_probe(dev, child, ifmedia_upd, i } if (i == MII_NPHY) { + device_set_ivars(dev, NULL); + free(v, M_DEVBUF); device_delete_child(dev, *child); *child = NULL; return(ENXIO); } - bus_generic_attach(dev); + i = bus_generic_attach(dev); - return(0); + v = device_get_ivars(*child); + if (v != NULL) { + device_set_ivars(*child, NULL); + free(v, M_DEVBUF); + } + + return (i); } /* Index: mii_physubr.c =================================================================== RCS file: /local/mirror/FreeBSD/r/ncvs/src/sys/dev/mii/mii_physubr.c,v retrieving revision 1.21 diff -u -p -r1.21 mii_physubr.c --- mii_physubr.c 29 May 2004 18:09:10 -0000 1.21 +++ mii_physubr.c 23 Nov 2004 17:07:30 -0000 @@ -522,7 +522,13 @@ int mii_phy_detach(device_t dev) { struct mii_softc *sc; + void *args; + args = device_get_ivars(dev); + if (args != NULL) { + device_set_ivars(dev, NULL); + free(args, M_DEVBUF); + } sc = device_get_softc(dev); mii_phy_down(sc); sc->mii_dev = NULL; From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 11:07:29 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A8E316A4CE for ; Sat, 22 Jan 2005 11:07:29 +0000 (GMT) Received: from mailout07.sul.t-online.com (mailout07.sul.t-online.com [194.25.134.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FADA43D2F for ; Sat, 22 Jan 2005 11:07:28 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from fwd09.aul.t-online.de by mailout07.sul.t-online.com with smtp id 1CsJ71-0001V9-01; Sat, 22 Jan 2005 12:07:27 +0100 Received: from Andro-Beta.Leidinger.net (EfJI8eZeoeNzWYWTMhA2e8IKcoc7rrXe6CyTTq54I-kjSDM+G8Zm8g@[217.83.21.140]) by fmrl09.sul.t-online.com with esmtp id 1CsJ6r-1J2kgS0; Sat, 22 Jan 2005 12:07:17 +0100 Received: from Magellan.Leidinger.net (Magellan.Leidinger.net [192.168.1.1]) j0MB6IfN089518 for ; Sat, 22 Jan 2005 12:06:18 +0100 (CET) (envelope-from Alexander@Leidinger.net) Date: Sat, 22 Jan 2005 12:08:10 +0100 From: Alexander Leidinger To: current@freebsd.org Message-ID: <20050122120810.05b8a0e3@Magellan.Leidinger.net> X-Mailer: Sylpheed-Claws 1.0.0 (GTK+ 1.2.10; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-ID: EfJI8eZeoeNzWYWTMhA2e8IKcoc7rrXe6CyTTq54I-kjSDM+G8Zm8g@t-dialin.net X-TOI-MSGID: 6de2246e-acbb-43e3-913b-98106cbb23c4 Subject: Strange behavior of "top" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 11:07:29 -0000 Hi, since my CPU monitor displayed a unexpected CPU usage I wanted to hunt down the problem. But top displays a strange output. It tells me that 23% of CPU are used by userland processes. But I only see 1.5% used in the process listing. The galeon-bin process shows alot of used CPU time (for this small uptime), and I wouldn't be surprised if it is the galeon process which is eating the majority of the CPU resources (I have ~85 tabs open with content), but I object to the 0% CPU display then. The galeon process spends alot of time in the kserel state. This is -current as of yesterday. Any ideas? ---snip--- last pid: 11906; load averages: 0.19, 0.29, 0.30 up 0+01:27:11 11:58:54 74 processes: 2 running, 72 sleeping CPU states: 23.2% user, 0.0% nice, 4.8% system, 0.2% interrupt, 71.8% idle Mem: 269M Active, 78M Inact, 68M Wired, 656K Cache, 60M Buf, 78M Free Swap: 1024M Total, 1024M Free Username to show: PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 641 root 96 0 232M 229M RUN 2:03 1.56% 1.56% Xorg 1168 netchild 20 0 127M 115M kserel 23:10 0.00% 0.00% galeon-bin 1159 netchild 96 0 24068K 22120K select 0:34 0.00% 0.00% sylpheed-claw 1157 netchild -8 0 2580K 1176K piperd 0:21 0.00% 0.00% libgtop_serve 1150 netchild 96 0 14364K 11504K select 0:09 0.00% 0.00% clock-applet 1103 netchild 96 0 18284K 15280K select 0:04 0.00% 0.00% gaim 1088 netchild 96 0 9188K 5880K select 0:04 0.00% 0.00% sawfish 1093 netchild 8 0 7000K 4488K nanslp 0:03 0.00% 0.00% chbg 1156 netchild 96 0 13552K 10596K select 0:03 0.00% 0.00% multiload-app 1148 netchild 96 0 15768K 11876K select 0:03 0.00% 0.00% mixer_applet2 1146 netchild 96 0 16016K 13052K select 0:02 0.00% 0.00% wnck-applet 1091 netchild 96 0 18456K 15140K select 0:02 0.00% 0.00% gnome-panel 615 root 8 0 1532K 1112K wait 0:02 0.00% 0.00% sh 576 ganglia 20 0 2224K 1572K kserel 0:02 0.00% 0.00% gmond 719 netchild 96 0 7620K 6540K select 0:01 0.00% 0.00% gconfd-2 247 root 96 0 1616K 1204K select 0:01 0.00% 0.00% dhclient 728 netchild 96 0 17648K 12976K select 0:01 0.00% 0.00% gnome-setting 1152 netchild 20 0 16216K 12952K kserel 0:01 0.00% 0.00% gweather-appl 1107 netchild 96 0 2416K 1828K select 0:01 0.00% 0.00% xmbmon 698 netchild 96 0 16048K 12020K select 0:01 0.00% 0.00% gnome-session 1109 netchild 20 0 2816K 2608K pause 0:01 0.00% 0.00% zsh 279 root 96 0 1136K 752K select 0:01 0.00% 0.00% moused 1097 netchild 96 0 4404K 3860K select 0:01 0.00% 0.00% xterm-static ---snip-- Bye, Alexander. -- The computer revolution is over. The computers won. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 11:40:05 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2195916A4CF for ; Sat, 22 Jan 2005 11:40:05 +0000 (GMT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F63243D2D for ; Sat, 22 Jan 2005 11:40:04 +0000 (GMT) (envelope-from j@uriah.heep.sax.de) Received: from sax.sax.de (localhost [127.0.0.1]) by sax.sax.de (8.12.10/8.12.10) with ESMTP id j0MBe3Yu068141; Sat, 22 Jan 2005 12:40:03 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.12.10/8.12.10/Submit) with UUCP id j0MBe3Lg068140; Sat, 22 Jan 2005 12:40:03 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: from uriah.heep.sax.de (localhost [127.0.0.1]) by uriah.heep.sax.de (8.13.1/8.13.1) with ESMTP id j0MBUFOq026190; Sat, 22 Jan 2005 12:30:15 +0100 (MET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.13.1/8.13.1/Submit) id j0MBUF1v026189; Sat, 22 Jan 2005 12:30:15 +0100 (MET) (envelope-from j) Date: Sat, 22 Jan 2005 12:30:15 +0100 From: Joerg Wunsch To: current@freebsd.org Message-ID: <20050122113015.GV30862@uriah.heep.sax.de> References: <20050121144428.GK30862@uriah.heep.sax.de> <20050121194103.GB19150@nagual.pp.ru> <20050121201400.GQ30862@uriah.heep.sax.de> <20050121221156.GA21459@nagual.pp.ru> <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120222137.GE30862@uriah.heep.sax.de> <20050121230949.GA34313@VARK.MIT.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050121221156.GA21459@nagual.pp.ru> <20050121230949.GA34313@VARK.MIT.EDU> User-Agent: Mutt/1.4.2.1i X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-GPG-Fingerprint: 5E84 F980 C3CA FD4B B584 1070 F48C A81B 69A8 5873 X-Spam-Status: No, score=-2.6 required=7.5 tests=AWL,BAYES_00 autolearn=ham version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on uriah.heep.sax.de cc: Andrey Chernov Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joerg Wunsch List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 11:40:05 -0000 As Andrey Chernov wrote: > > Do whatever you want, I think it's silly and should rather be > > dropped as it is a useless feature, which could only lead people > > to write unportable code. > The code which _not_ expect this feature present is _equally_ > unportable. Nope. Just think about it: code which doesn't take this feature into account needs to check for conversion errors by means of verifying endptr. It simply wouldn't care about errno at all, except for possibly checking for overflows -- which only needs to be verified after it is already clear from checking endptr that the conversion was OK. Thus, errno could not possibly be EINVAL anymore in that case. Consequently, implementing EINVAL might cause an innocent programmer to rely on it for finding conversion errors, as opposed to properly checking endptr instead. Thus it has the negative impact that it might cause people to rely on non-portable features of a particular implementation, the more in that the FreeBSD man page (unlike systems like Solaris or Linux that simply quote the SUSP man page) explicitly states that EINVAL is returned for conversion errors, without mentioning that this feature is not portable as it employs a ``may'' clause from SUSP. Thus we should at least document in the man page that EINVAL for conversion errors is a FreeBSD extension that is allowable by the SUSP but not guaranteed, and thus cannot be relied on. I still think that Posix/SUSP is bogus in that respect, but that probably applies to any usage of `may' in a standard. > I repeat: portable application must always consider _both_ cases > since both are mentioned in the standard as possible ones. Nope, properly checking endptr is sufficient to detect conversion errors, so a portable application simply doesn't need to care for errno in that case. > BTW, where was you when this change was discussed and commited by > first time long ago? I probably wasn't much interested in it by that time. See the introduction in my first article in this thread, the problem only became apparent to me now that I have to verify another strtol() implementation for a completely different system. > At those time I don't remember any "against" votes. Well, Bruce wrote me that he was opposed to it even by that time. As David Schultz wrote: > Regarding the interpretation of sequences such as "0x" and "+": > These are disallowed by the BNF in section 6.4.4.1 of the C99 > standard. Ah, that's the trick I've been missing. Thanks for explaining this. > 7.20.1.4.7 > If the subject sequence is empty or does not have the expected > form, no conversion is performed; ... It rather confused me that this special case is explicitly mentioned as a ``no conversion'' case, while anything else has to rely on implied statements. > Regarding the use of errno: > The ISO C standard allows any library function to set errno to > EFOO unless it explicitly says EFOO is used to mean something else > for that function. ... Do you have a quote for that? I know that Posix/SUSP basically interprets it that way, but I think the second sentence in paragraph 3 of 7.5 is ambiguous, as that I would interpret it as an explicit statement that for any function where the use of errno is documented as part of the [C] standard, errno must not be set in another way than documented. This would prohibit setting errno to EINVAL for strtol(), as the possible errno modifications are documented for strtol() (either undmodified, or set to ERANGE). Again, I didn't meant to change this in FreeBSD, I just wondered about it. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 11:49:52 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBC0116A4CE for ; Sat, 22 Jan 2005 11:49:52 +0000 (GMT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC89943D54 for ; Sat, 22 Jan 2005 11:49:51 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de (cicely5.cicely.de [10.1.1.7]) (authenticated bits=0)j0MBnlHo071125 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Sat, 22 Jan 2005 12:49:49 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (cicely12.cicely.de [IPv6:3ffe:400:8d0:301::12]) by cicely5.cicely.de (8.12.10/8.12.10) with ESMTP id j0MBnNU3070993 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 22 Jan 2005 12:49:24 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.12.11/8.12.11) with ESMTP id j0MBnNLg025092; Sat, 22 Jan 2005 12:49:23 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.12.11/8.12.11/Submit) id j0MBnMWL025091; Sat, 22 Jan 2005 12:49:22 +0100 (CET) (envelope-from ticso) Date: Sat, 22 Jan 2005 12:49:22 +0100 From: Bernd Walter To: Alexander Leidinger Message-ID: <20050122114921.GX8860@cicely12.cicely.de> References: <20050122120810.05b8a0e3@Magellan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050122120810.05b8a0e3@Magellan.Leidinger.net> X-Operating-System: FreeBSD cicely12.cicely.de 5.2-CURRENT alpha User-Agent: Mutt/1.5.6i X-Spam-Status: No, hits=-4.9 required=3.0 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Report: * -4.9 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on cicely12.cicely.de cc: current@freebsd.org Subject: Re: Strange behavior of "top" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 11:49:53 -0000 On Sat, Jan 22, 2005 at 12:08:10PM +0100, Alexander Leidinger wrote: > Hi, > > since my CPU monitor displayed a unexpected CPU usage I wanted to hunt > down the problem. But top displays a strange output. It tells me that > 23% of CPU are used by userland processes. But I only see 1.5% used in > the process listing. The galeon-bin process shows alot of used CPU time > (for this small uptime), and I wouldn't be surprised if it is the galeon > process which is eating the majority of the CPU resources (I have ~85 > tabs open with content), but I object to the 0% CPU display then. > > The galeon process spends alot of time in the kserel state. > > This is -current as of yesterday. Any ideas? Don't know your case, but this usually happens for me if the processes taking the CPU time are already gone. e.g. during GNU configure where lots of short running process are used. You may keep an eye on last pid value. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 12:04:10 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6B3616A4CE for ; Sat, 22 Jan 2005 12:04:10 +0000 (GMT) Received: from mailout02.sul.t-online.com (mailout02.sul.t-online.com [194.25.134.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BFC843D1D for ; Sat, 22 Jan 2005 12:04:10 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from fwd06.aul.t-online.de by mailout02.sul.t-online.com with smtp id 1CsJzt-0001lv-00; Sat, 22 Jan 2005 13:04:09 +0100 Received: from Andro-Beta.Leidinger.net (V+h68eZToe0GP-HLsIFD5cQiA+j7IOxnuq7HqnyZnPjPP185gE6tYp@[217.83.21.140]) by fmrl06.sul.t-online.com with esmtp id 1CsJzj-0hNsPY0; Sat, 22 Jan 2005 13:03:59 +0100 Received: from Magellan.Leidinger.net (Magellan.Leidinger.net [192.168.1.1]) j0MC2w91097513; Sat, 22 Jan 2005 13:02:58 +0100 (CET) (envelope-from Alexander@Leidinger.net) Date: Sat, 22 Jan 2005 13:04:50 +0100 From: Alexander Leidinger To: ticso@cicely.de Message-ID: <20050122130450.48f3c9c3@Magellan.Leidinger.net> In-Reply-To: <20050122114921.GX8860@cicely12.cicely.de> References: <20050122120810.05b8a0e3@Magellan.Leidinger.net> <20050122114921.GX8860@cicely12.cicely.de> X-Mailer: Sylpheed-Claws 1.0.0 (GTK+ 1.2.10; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-ID: V+h68eZToe0GP-HLsIFD5cQiA+j7IOxnuq7HqnyZnPjPP185gE6tYp@t-dialin.net X-TOI-MSGID: f1d404a4-97f8-4ce6-8b92-dbfbe46ef0a8 cc: current@freebsd.org Subject: Re: Strange behavior of "top" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 12:04:11 -0000 On Sat, 22 Jan 2005 12:49:22 +0100 Bernd Walter wrote: > On Sat, Jan 22, 2005 at 12:08:10PM +0100, Alexander Leidinger wrote: > > Hi, > > > > since my CPU monitor displayed a unexpected CPU usage I wanted to hunt > > down the problem. But top displays a strange output. It tells me that > > 23% of CPU are used by userland processes. But I only see 1.5% used in > > the process listing. The galeon-bin process shows alot of used CPU time > > (for this small uptime), and I wouldn't be surprised if it is the galeon > > process which is eating the majority of the CPU resources (I have ~85 > > tabs open with content), but I object to the 0% CPU display then. > > > > The galeon process spends alot of time in the kserel state. > > > > This is -current as of yesterday. Any ideas? > > Don't know your case, but this usually happens for me if the processes > taking the CPU time are already gone. > e.g. during GNU configure where lots of short running process are used. > You may keep an eye on last pid value. Ah, yes, I know about this too (and you may be able to catch the cause of the load in this case by repeatedly hitting the space key very fast). Sorry, I forgot to tell that no such action was running in the background. Bye, Alexander. -- The computer revolution is over. The computers won. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 12:40:34 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E143416A4CE for ; Sat, 22 Jan 2005 12:40:34 +0000 (GMT) Received: from saltmine.radix.net (saltmine.radix.net [207.192.128.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7604143D1F for ; Sat, 22 Jan 2005 12:40:34 +0000 (GMT) (envelope-from dickey@saltmine.radix.net) Received: from saltmine.radix.net (localhost [127.0.0.1]) by saltmine.radix.net (8.12.2/8.12.2) with ESMTP id j0MCeXNb026896 for ; Sat, 22 Jan 2005 07:40:33 -0500 (EST) Received: (from dickey@localhost) by saltmine.radix.net (8.12.2/8.12.2/Submit) id j0MCeXe4026885 for current@freebsd.org; Sat, 22 Jan 2005 07:40:33 -0500 (EST) Date: Sat, 22 Jan 2005 07:40:33 -0500 From: Thomas Dickey To: current@freebsd.org Message-ID: <20050122124032.GA26006@saltmine.radix.net> References: <20050121194103.GB19150@nagual.pp.ru> <20050121201400.GQ30862@uriah.heep.sax.de> <20050121221156.GA21459@nagual.pp.ru> <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120222137.GE30862@uriah.heep.sax.de> <20050121230949.GA34313@VARK.MIT.EDU> <20050122113015.GV30862@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/" Content-Disposition: inline In-Reply-To: <20050122113015.GV30862@uriah.heep.sax.de> User-Agent: Mutt/1.3.27i Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 12:40:35 -0000 --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jan 22, 2005 at 12:30:15PM +0100, Joerg Wunsch wrote: > As Andrey Chernov wrote: >=20 > > > Do whatever you want, I think it's silly and should rather be > > > dropped as it is a useless feature, which could only lead people > > > to write unportable code. >=20 > > The code which _not_ expect this feature present is _equally_ > > unportable. >=20 > Nope. Just think about it: code which doesn't take this feature into > account needs to check for conversion errors by means of verifying > endptr. It simply wouldn't care about errno at all, except for That's what I always do - that's the way strtol was first documented. Adding errno tweaks on top of that is (as noted) neither portable nor necessary. --=20 Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net --TB36FDmn/VVEgNH/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (SunOS) Comment: For info see http://www.gnupg.org iD8DBQFB8km+tIqByHxlDocRAtiyAJwKL+XkZxsQhfqtXX9X6Kzkmwbw6wCgpRzE 7/bmaZ/raoPWY8/+A4wvPbE= =yf0V -----END PGP SIGNATURE----- --TB36FDmn/VVEgNH/-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 17:42:25 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42F7516A4CE for ; Fri, 21 Jan 2005 17:42:25 +0000 (GMT) Received: from mxc.rambler.ru (mxc.rambler.ru [81.19.66.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9008143D1F for ; Fri, 21 Jan 2005 17:42:24 +0000 (GMT) (envelope-from capt.nem@rambler.ru) Received: from mailc.rambler.ru (mailc.rambler.ru [81.19.66.27]) by mxc.rambler.ru (Postfix) with ESMTP id 441A7CD8A0 for ; Fri, 21 Jan 2005 20:42:23 +0300 (MSK) Received: from denis.ftr.ru (ns.ftr.ru [212.96.97.73]) (authenticated bits=0) by mailc.rambler.ru (8.12.10/8.12.10) with ESMTP id j0LHgMYl056506 for ; Fri, 21 Jan 2005 20:42:22 +0300 (MSK) Date: Fri, 21 Jan 2005 20:41:54 +0300 From: DenisN X-Mailer: The Bat! (v2.10.01) Personal X-Priority: 3 (Normal) Message-ID: <369661239.20050121204154@rambler.ru> To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Auth-User: capt.nemo, whoson: (null) X-Mailman-Approved-At: Sat, 22 Jan 2005 12:44:14 +0000 Subject: uplcom driver and USB modem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: DenisN List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 17:42:25 -0000 Hello. Have solved you problem? http://lists.freebsd.org/pipermail/freebsd-current/2003-September/011286.html DenisN mailto:capt.nem@rambler.ru From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 22:03:26 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA4C416A4CE for ; Fri, 21 Jan 2005 22:03:26 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43EE243D2F for ; Fri, 21 Jan 2005 22:03:26 +0000 (GMT) (envelope-from imp@harmony.village.org) Received: from localhost (localhost [IPv6:::1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j0LM0oB4048734; Fri, 21 Jan 2005 15:00:50 -0700 (MST) (envelope-from imp@harmony.village.org) Date: Fri, 21 Jan 2005 15:00:50 -0700 (MST) Message-Id: <20050121.150050.74701505.imp@harmony.village.org> To: cswiger@mac.com From: Warner Losh In-Reply-To: <41F14659.8040003@mac.com> References: <30924.1106323869@critter.freebsd.dk> <41F14659.8040003@mac.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 22 Jan 2005 12:44:14 +0000 cc: phk@phk.freebsd.dk cc: current@freebsd.org Subject: Re: Anybody involved with ISO C standardization ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 22:03:27 -0000 > Poul-Henning Kamp wrote: > > I just read another brain-dead proposal for a new timeformat > > which appearantly is in the ISO C queue and I would really > > like if we can avoid having another damn mistake in that area. > > (http://david.tribble.com/text/c0xlongtime.html) > > I tried to figure out what was wrong with the proposal, and came up with this: > > "The longtime_t type represents a system time as an integral number of ticks > elaped since the beginning of the long time epoch. Each tick is two > nanoseconds in length. The epoch begins at {AD 2001-01-01 00:00:00.000 Z}. > > Long time values represent dates across the range of {AD 1601-01-01 00:00:00 > Z} to {AD 2401-01-01 00:00:00 Z} within the proleptic Gregorian calendar." > > [ Ugh. :-) ] There's problems with leap seconds too. Sometimes they are swizzled in, and sometimes not. The #define is confusingly backwards. There's no provision for knowing if you have leap seconds or not. There's a cavalier attitude towards them. They say you don't normally need them, but if you want to know the actual elapsed time you do (think what happens over a leap second where time replays). There's no way to convert from internal to external to internal again (because the external represenation, whatever that means, maps positive leap seconds to the same value). It is a complete trainwreck. Warner From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 13:05:32 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3291416A4CE for ; Sat, 22 Jan 2005 13:05:32 +0000 (GMT) Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id F071A43D45 for ; Sat, 22 Jan 2005 13:05:30 +0000 (GMT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id 114B43B8BB; Sat, 22 Jan 2005 14:05:28 +0100 (CET) Received: from hal9000.schweikhardt.net (localhost [127.0.0.1]) j0MCZOMc005387; Sat, 22 Jan 2005 13:35:24 +0100 (CET) (envelope-from schweikh@hal9000.schweikhardt.net) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.13.1/8.13.1/Submit) id j0MCZOBl005386; Sat, 22 Jan 2005 13:35:24 +0100 (CET) (envelope-from schweikh) Date: Sat, 22 Jan 2005 13:35:24 +0100 From: Jens Schweikhardt To: Poul-Henning Kamp Message-ID: <20050122123524.GA1951@schweikhardt.net> References: <30924.1106323869@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <30924.1106323869@critter.freebsd.dk> User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: Anybody involved with ISO C standardization ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 13:05:32 -0000 On Fri, Jan 21, 2005 at 05:11:09PM +0100, Poul-Henning Kamp wrote: # # I just read another brain-dead proposal for a new timeformat # which appearantly is in the ISO C queue and I would really # like if we can avoid having another damn mistake in that area. # (http://david.tribble.com/text/c0xlongtime.html) # # If we have anybody who's actively involved in the ISO C standardization # who are willing to push and champion a a proposal that makes sense # then I would love to hear from them. Tribble et al are active on comp.std.c, where this discussion would have more (THE!) visibility among the powers that influcence the C standard. Did you discuss the issues with Tribble? He appears to be a reasonable guy. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 13:05:34 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 265D616A4D0 for ; Sat, 22 Jan 2005 13:05:34 +0000 (GMT) Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id 949F343D1F for ; Sat, 22 Jan 2005 13:05:33 +0000 (GMT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id 71FE73B8D3; Sat, 22 Jan 2005 14:05:32 +0100 (CET) Received: from hal9000.schweikhardt.net (localhost [127.0.0.1]) j0MD5DuM005888; Sat, 22 Jan 2005 14:05:13 +0100 (CET) (envelope-from schweikh@hal9000.schweikhardt.net) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.13.1/8.13.1/Submit) id j0MD5DZg005887; Sat, 22 Jan 2005 14:05:13 +0100 (CET) (envelope-from schweikh) Date: Sat, 22 Jan 2005 14:05:13 +0100 From: Jens Schweikhardt To: Thomas Dickey Message-ID: <20050122130513.GB1951@schweikhardt.net> References: <20050116144113.GB66854@gothmog.gr> <41EAB5FE.30603@freebsd.org> <20050116193757.GA10974@saltmine.radix.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050116193757.GA10974@saltmine.radix.net> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: gratuitous gcc warnings: unused function arguments? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 13:05:34 -0000 On Sun, Jan 16, 2005 at 02:37:57PM -0500, Thomas Dickey wrote: # On Sun, Jan 16, 2005 at 10:44:14AM -0800, Tim Kientzle wrote: # > Giorgos Keramidas suggested: # > > # > >% (void)argv; # > # > I first saw this idiom for marking unused # > arguments over 10 years ago and have used # > it extensively since then. Very portable; # > highly recommended. # # except of course for the compilers that warn about no effect... All compilers I have used (which includes embedded compilers) would warn about "no effect" only for argv; but shut up for (void)argv; The most portable solution involves some redundancy, e.g. simply using all args. May look ugly to some eyes and may be outright confusing for ten arg functions where you only "use" the last one. if (argc != 1 || argv[1] != 0) { ... } and variations thereof. Note that argc != 1 catches the "impossible" case of argc == 0. On a more philosophical note, it could be argued that a function using its second arg implicitly uses its first arg :-) Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 14:12:33 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6617116A4CE for ; Sat, 22 Jan 2005 14:12:33 +0000 (GMT) Received: from gateway.nixsys.be (gateway.nixsys.be [195.144.77.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8286443D41 for ; Sat, 22 Jan 2005 14:12:32 +0000 (GMT) (envelope-from philip@paeps.cx) Received: from wotan.home.paeps.cx (wotan.home.paeps.cx [IPv6:2001:838:37f:10:a00:20ff:fe9b:138c]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "wotan.home.paeps.cx", Issuer "NixSys CA" (verified OK)) by gateway.nixsys.be (Postfix) with ESMTP id AB434C11D; Sat, 22 Jan 2005 15:12:30 +0100 (CET) Received: from fasolt.home.paeps.cx (fasolt.home.paeps.cx [IPv6:2001:838:37f:10:20a:e6ff:fe7d:c08]) by wotan.home.paeps.cx (Postfix) with ESMTP id 749D4618D; Sat, 22 Jan 2005 15:12:29 +0100 (CET) Received: from fasolt.home.paeps.cx (philip@localhost [127.0.0.1]) by fasolt.home.paeps.cx (8.13.1/8.13.1) with ESMTP id j0MECT1I044249; Sat, 22 Jan 2005 15:12:29 +0100 (CET) (envelope-from philip@fasolt.home.paeps.cx) Received: (from philip@localhost) by fasolt.home.paeps.cx (8.13.1/8.13.1/Submit) id j0MECRpI044248; Sat, 22 Jan 2005 15:12:27 +0100 (CET) (envelope-from philip) Date: Sat, 22 Jan 2005 15:12:27 +0100 From: Philip Paeps To: current@freebsd.org Message-ID: <20050122141227.GA33663@fasolt.home.paeps.cx> Mail-Followup-To: current@freebsd.org, Eric Kjeldergaard References: <20050110131529.GA716@loge.nixsys.be> <20050119210555.GF14706@fasolt.home.paeps.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Date-in-Rome: ante diem XI Kalendas Februarias MMDCCLVIII ab Urbe Condida X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3 FC53 BF4B D0E6 049D B879 X-Message-Flag: Get a proper mailclient! Organization: Happily Disorganized User-Agent: Mutt/1.5.6i cc: Eric Kjeldergaard Subject: Re: [PLEASE TEST] Many improvements to Synaptics support in psm(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 14:12:33 -0000 On 2005-01-19 21:26:48 (-0600), Eric Kjeldergaard wrote: > > > Perhaps I'm doing something really dumb, but I can't seem to get > > > scrolling going on this with the new psm at all. > > > > Do you actually have scroll buttons on your touchpad? As in, some extra > > buttons that don't appear to do anything? Or are you trying the gesture > > bit, tapping twice then holding? I'm aware of the fact that the gesture > > isn't working yet, and that there's some 'funny stuff' if you try to tap > > with more than one finger. > > Well, I fear misunderstanding may be the source of my problems. I was > thinking of "edge scrolling" or whatever you choose to call it. Scrolling > by running my finger along the right or bottom edge of the touchpad. That's not implemented yet. I have some patches in progress that implement this (and the other gestures that are still missing), but there's not fit for human consumption yet. As soon as they are, they'll be committed :-) - Philip -- Philip Paeps Please don't Cc me, I am philip@freebsd.org subscribed to the list. Some errors will always go unnoticed until the book is in print. From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 14:52:41 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C9B516A4CE; Sat, 22 Jan 2005 14:52:41 +0000 (GMT) Received: from castle.jp.FreeBSD.org (castle.jp.FreeBSD.org [210.226.20.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08E9043D45; Sat, 22 Jan 2005 14:52:41 +0000 (GMT) (envelope-from akiyama@jp.FreeBSD.org) Received: from localhost (castle.jp.FreeBSD.org [2001:218:422:1::15]) ESMTP/inet6 id j0MEqa866008; Sat, 22 Jan 2005 23:52:37 +0900 (JST) (envelope-from akiyama@jp.FreeBSD.org) Date: Sat, 22 Jan 2005 23:52:33 +0900 From: Shunsuke Akiyama To: Michal Mertl In-Reply-To: <1106227110.716.11.camel@genius2.i.cz> References: <1106134006.1132.12.camel@genius2.i.cz> <1106227110.716.11.camel@genius2.i.cz> User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: multipart/mixed; boundary="Multipart_Sat_Jan_22_23:52:33_2005-1" Message-Id: <20050122235234K.akiyama@jp.FreeBSD.org> X-Dispatcher: imput version 20040704(IM147) Lines: 216 cc: Emanuel Strobl cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org cc: bernd@bwct.de Subject: Re: strange ucom (uplcom) error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 14:52:41 -0000 --Multipart_Sat_Jan_22_23:52:33_2005-1 Content-Type: text/plain; charset=US-ASCII At Thu, 20 Jan 2005 14:18:30 +0100, Michal Mertl wrote: > > I wrote: > > Emanuel Strobl wrote: > > > Am Dienstag, 18. Januar 2005 16:17 schrieb Andrew L. Neporada: > > > > On Tue, Jan 18, 2005 at 01:06:43PM +0100, Emanuel Strobl wrote: > > > > > Dear experts, > > > > > > > > > > I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working > > > > > the other one not (I hate to say it but both are working under win). > > > > > > > > > > The not working (more expensive) one gets recognized as ucom0 and I have > > > > > ucom0, also I can receive signal but not transmit. > > > > > > > > [skip] > > > > > > > > Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch > > > > http://gate.intercaf.ru/~lesha/6100/pl2303x.patch > > > > > > > > It can break old (working) PL2303 chip, but it works for me with newer > > > > > > Thanks a lot, this indeed fixes the revision 3.0 adaptor but unfortunately > > > also breakes the 2.02 version :( > > > > > > Perhaps there's a goog guy out there who can refurbish the uplcom driver with > > > this information (akiyama?)? > > > > > > Thanks a lot, > > > > I've just recently been looking into this too. I used the mentioned > > patch and also linux driver source and have come with the attached > > patch. It contains one more change but I don't know if it's correct. It > > works for both chips on CURRENT for serial console. It detects if the > > chip is rev 3.00 and aplies the patch only for it. > > > > The author of the patch mentions it isn't binary safe - sometimes the > > chip stops working. I planned to test it with binary transfers (ppp) > > today, check if it's working and submit it (with some cleanup) for > > inclusion in FreeBSD. > > > > Michal Mertl > > I tested my patch for binary safety on CURRENT yesterday (dialed with > ppp) and didn't notice any problem. > > I'm attaching my patch again because some recipients didn't probably > receive it yesterday. > > Michal Good work! I've updated your patch. If attached patch works correctly with new revision chip, I'll commit this. Please test attached patch, and tell me the result. Regards, -- Shunsuke Akiyama akiyama@jp.FreeBSD.org akiyama@FreeBSD.org --Multipart_Sat_Jan_22_23:52:33_2005-1 Content-Type: application/octet-stream Content-Disposition: attachment; filename="uplcom.c-diff" Content-Transfer-Encoding: 7bit Index: uplcom.c =================================================================== RCS file: /home/ncvs/src/sys/dev/usb/uplcom.c,v retrieving revision 1.25 diff -u -r1.25 uplcom.c --- uplcom.c 6 Jan 2005 01:43:29 -0000 1.25 +++ uplcom.c 22 Jan 2005 14:39:45 -0000 @@ -97,10 +97,13 @@ #include #include +#include + #include #include #include +#include #include #include "usbdevs.h" #include @@ -138,6 +141,9 @@ #define RSAQ_STATUS_DSR 0x02 #define RSAQ_STATUS_DCD 0x01 +#define CHIPTYPE_PL2303 0 +#define CHIPTYPE_PL2303X 1 + struct uplcom_softc { struct ucom_softc sc_ucom; @@ -156,6 +162,8 @@ u_char sc_lsr; /* Local status register */ u_char sc_msr; /* uplcom status register */ + + int sc_chiptype; /* Type of chip */ }; /* @@ -293,6 +301,7 @@ USB_ATTACH_START(uplcom, sc, uaa); usbd_device_handle dev = uaa->device; struct ucom_softc *ucom; + usb_device_descriptor_t *udd; usb_config_descriptor_t *cdesc; usb_interface_descriptor_t *id; usb_endpoint_descriptor_t *ed; @@ -320,6 +329,16 @@ DPRINTF(("uplcom attach: sc = %p\n", sc)); + /* determine chip type */ + udd = &dev->ddesc; + if (UGETW(udd->bcdDevice) >= 0x300) { + DPRINTF(("uplcom_attach: chiptype 2303X\n")); + sc->sc_chiptype = CHIPTYPE_PL2303X; + } else { + DPRINTF(("uplcom_attach: chiptype 2303\n")); + sc->sc_chiptype = CHIPTYPE_PL2303; + } + /* initialize endpoints */ ucom->sc_bulkin_no = ucom->sc_bulkout_no = -1; sc->sc_intr_number = -1; @@ -521,6 +540,54 @@ return (0); } +struct pl2303x_init { + uint8_t req_type; + uint8_t request; + uint16_t value; + uint16_t index; + uint16_t length; +}; + +Static const struct pl2303x_init pl2303x[] = { + { UT_READ_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 0x8484, 0, 0 }, + { UT_WRITE_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 0x0404, 0, 0 }, + { UT_READ_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 0x8484, 0, 0 }, + { UT_READ_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 0x8383, 0, 0 }, + { UT_READ_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 0x8484, 0, 0 }, + { UT_WRITE_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 0x0404, 1, 0 }, + { UT_READ_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 0x8484, 0, 0 }, + { UT_READ_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 0x8383, 0, 0 }, + { UT_WRITE_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 0, 1, 0 }, + { UT_WRITE_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 1, 0, 0 }, + { UT_WRITE_VENDOR_DEVICE, UPLCOM_SET_REQUEST, 2, 0x44, 0 } +}; + +Static usbd_status +uplcom_pl2303x_init(struct uplcom_softc *sc) +{ + usb_device_request_t req; + usbd_status err; + int i; + + for (i = 0; i < 11; i++) { + req.bmRequestType = pl2303x[i].req_type; + req.bRequest = pl2303x[i].request; + USETW(req.wValue, pl2303x[i].value); + USETW(req.wIndex, pl2303x[i].index); + USETW(req.wLength, pl2303x[i].length); + + err = usbd_do_request(sc->sc_ucom.sc_udev, &req, 0); + if (err) { + printf("%s: uplcom_pl2303x_init: %d: %s\n", + USBDEVNAME(sc->sc_ucom.sc_dev), i, + usbd_errstr(err)); + return (EIO); + } + } + + return (0); +} + Static void uplcom_set_line_state(struct uplcom_softc *sc) { @@ -617,7 +684,10 @@ req.bmRequestType = UT_WRITE_VENDOR_DEVICE; req.bRequest = UPLCOM_SET_REQUEST; USETW(req.wValue, 0); - USETW(req.wIndex, UPLCOM_SET_CRTSCTS); + if (sc->sc_chiptype == CHIPTYPE_PL2303X) + USETW(req.wIndex, 0x61); + else + USETW(req.wIndex, UPLCOM_SET_CRTSCTS); USETW(req.wLength, 0); err = usbd_do_request(sc->sc_ucom.sc_udev, &req, 0); @@ -744,6 +814,9 @@ } } + if (sc->sc_chiptype == CHIPTYPE_PL2303X) + return (uplcom_pl2303x_init(sc)); + return (0); } --Multipart_Sat_Jan_22_23:52:33_2005-1-- From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 16:57:46 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 39B9616A4CE for ; Sat, 22 Jan 2005 16:57:46 +0000 (GMT) Received: from osi2.gua.net (osi2.gua.net [205.161.188.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FD6743D49 for ; Sat, 22 Jan 2005 16:57:45 +0000 (GMT) (envelope-from kuuse@redantigua.com) Received: (qmail 57870 invoked by uid 89); 22 Jan 2005 16:57:45 -0000 Received: from kuuse@redantigua.com by osi2 by uid 89 with qmail-scanner-1.20 ( Clear:RC:0(205.161.188.16):. Processed in 0.209072 secs); 22 Jan 2005 16:57:45 -0000 Received: from unknown (HELO widserver1) (kuuse@osint.net@205.161.188.16) by 0 with SMTP; 22 Jan 2005 16:57:44 -0000 Message-ID: <007c01c500a3$9e1b36a0$10bca1cd@widserver1> From: "Johan Kuuse - Red Antigua" To: , "Scot Hetzel" References: <000a01c4ffd2$86d5cc70$10bca1cd@widserver1><200501211130.43893.kuuse@redantigua.com><790a9fff05012109562ba31a32@mail.gmail.com> <200501211634.26766.kuuse@redantigua.com> Date: Sat, 22 Jan 2005 10:58:37 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1478 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 cc: Tom Jensen Subject: Re: Problem with crt1.o and init tls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 16:57:46 -0000 # make OSRELDATE=0 buildworld worked fine now, no errors. What's next? # make OSRELDATE=0 buildkernel or just # make buildkernel (Sorry for being tedious, but I don't want to screw things up again.) Regards, Johan ----- Original Message ----- From: "Johan Kuuse" To: ; "Scot Hetzel" Cc: "Tom Jensen" Sent: Friday, January 21, 2005 4:34 PM Subject: Re: Problem with crt1.o and init tls OK, before I ruin everything again...: Should I use the same flags for *all* 'make' statements? i.e. is it important to use OSRELDATE=0 everywhere? # make OSRELDATE=0 buildworld # make OSRELDATE=0 buildkernel # make OSRELDATE=0 installkernel # reboot boot -s # mergemaster -p # make OSRELDATE=0 installworld # mergemaster # reboot Johan On Friday 21 January 2005 11:56, Scot Hetzel wrote: > Then try building 6x with: > > make OSRELDATE=0 buildworld _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 17:17:46 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 365AC16A4CE for ; Sat, 22 Jan 2005 17:17:46 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 503E943D39 for ; Sat, 22 Jan 2005 17:17:45 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id j0MHHiMj040481; Sat, 22 Jan 2005 20:17:44 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id j0MHHiSp040480; Sat, 22 Jan 2005 20:17:44 +0300 (MSK) (envelope-from ache) Date: Sat, 22 Jan 2005 20:17:43 +0300 From: Andrey Chernov To: Joerg Wunsch Message-ID: <20050122171743.GB39943@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Joerg Wunsch , current@freebsd.org References: <20050121194103.GB19150@nagual.pp.ru> <20050121201400.GQ30862@uriah.heep.sax.de> <20050121221156.GA21459@nagual.pp.ru> <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120222137.GE30862@uriah.heep.sax.de> <20050121230949.GA34313@VARK.MIT.EDU> <20050122113015.GV30862@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050122113015.GV30862@uriah.heep.sax.de> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.8; VDF: 6.29.0.75; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [0.0.0.0]); Sat, 22 Jan 2005 20:17:44 +0300 (MSK) cc: current@freebsd.org Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 17:17:46 -0000 On Sat, Jan 22, 2005 at 12:30:15PM +0100, Joerg Wunsch wrote: > Nope. Just think about it: code which doesn't take this feature into > account needs to check for conversion errors by means of verifying > endptr. It simply wouldn't care about errno at all, except for > possibly checking for overflows -- which only needs to be verified > after it is already clear from checking endptr that the conversion was > OK. Thus, errno could not possibly be EINVAL anymore in that case. I know portable way of doing that. You describe one case from two. The another case you miss is more indirect: portable application which set "errno = 0" before calling strtol() to detect overflows (it is only method) even after checking that endptr moved can't check just if (errno) { ... } but must check if (errno == ERANGE) { ... } instead. That is, what I mean, saying that portable application should consider _both_ cases. > implementation, the more in that the FreeBSD man page (unlike systems > like Solaris or Linux that simply quote the SUSP man page) explicitly > states that EINVAL is returned for conversion errors, without > mentioning that this feature is not portable as it employs a ``may'' > clause from SUSP. This situation could be improved. I'll look into that. > > At those time I don't remember any "against" votes. > > Well, Bruce wrote me that he was opposed to it even by that time. Strangely, my memory says me other things - he will help me with polishing strtol() at those time with that and other aspects. Perhaps his opposition was too soft to be detected? > I know that Posix/SUSP basically interprets it that way, but I think > the second sentence in paragraph 3 of 7.5 is ambiguous, as that I > would interpret it as an explicit statement that for any function > where the use of errno is documented as part of the [C] standard, > errno must not be set in another way than documented. This would > prohibit setting errno to EINVAL for strtol(), as the possible errno > modifications are documented for strtol() (either undmodified, or set > to ERANGE). POSIX pretends to be part of C standard (sort of), saying that conflict you may see is not a conflict :-) Here is full quote: "Extension to the ISO C standard The functionality described is an extension to the ISO C standard. Application writers may make use of an extension as it is supported on all IEEE Std 1003.1-2001-conforming systems. With each function or header from the ISO C standard, a statement to the effect that ``any conflict is unintentional'' is included. That is intended to refer to a direct conflict. IEEE Std 1003.1-2001 acts in part as a profile of the ISO C standard, and it may choose to further constrain behaviors allowed to vary by the ISO C standard. Such limitations are not considered conflicts. Where additional semantics apply to a function or header, the material is identified by use of the CX margin legend." -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 17:20:02 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3A1816A4CF for ; Sat, 22 Jan 2005 17:20:02 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD4B143D46 for ; Sat, 22 Jan 2005 17:20:01 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id j0MHK03f040535; Sat, 22 Jan 2005 20:20:00 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id j0MHK0Ow040534; Sat, 22 Jan 2005 20:20:00 +0300 (MSK) (envelope-from ache) Date: Sat, 22 Jan 2005 20:20:00 +0300 From: Andrey Chernov To: Thomas Dickey Message-ID: <20050122172000.GC39943@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Thomas Dickey , current@FreeBSD.ORG References: <20050121201400.GQ30862@uriah.heep.sax.de> <20050121221156.GA21459@nagual.pp.ru> <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120222137.GE30862@uriah.heep.sax.de> <20050121230949.GA34313@VARK.MIT.EDU> <20050122113015.GV30862@uriah.heep.sax.de> <20050122124032.GA26006@saltmine.radix.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="ZGiS0Q5IWpPtfppv" Content-Disposition: inline In-Reply-To: <20050122124032.GA26006@saltmine.radix.net> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.8; VDF: 6.29.0.75; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [0.0.0.0]); Sat, 22 Jan 2005 20:20:00 +0300 (MSK) cc: current@FreeBSD.ORG Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 17:20:02 -0000 --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Jan 22, 2005 at 07:40:33AM -0500, Thomas Dickey wrote: > > Nope. Just think about it: code which doesn't take this feature into > > account needs to check for conversion errors by means of verifying > > endptr. It simply wouldn't care about errno at all, except for > > That's what I always do - that's the way strtol was first documented. > Adding errno tweaks on top of that is (as noted) neither portable nor > necessary. The story not ends here. After checking endptr you should check for overflow, and there you need to consider both cases. See my detailed reply to Joerg. -- http://ache.pp.ru/ --ZGiS0Q5IWpPtfppv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iQCVAwUBQfKLQOJgpPLZnQjrAQGF1QP/TXhEOwTp9IKWk4rMfdy87/Dbdaoz5mIv nwVOb9irlGcOP6VCBqpUo9asGleV5kVPXaENzliNR+ifwVsG2f8WM76AwhWAWzxX 26u8miXSXl7DP5r170muCft2NakM3AdtHBXV90h9uCy3Q+8EjSAcFnQ9zIXKgXmn mPS9QOyZ5es= =PQbv -----END PGP SIGNATURE----- --ZGiS0Q5IWpPtfppv-- From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 17:35:28 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CAF5116A4CE for ; Sat, 22 Jan 2005 17:35:28 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11FF343D41 for ; Sat, 22 Jan 2005 17:35:28 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id j0MHZROt040741; Sat, 22 Jan 2005 20:35:27 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id j0MHZQIx040740; Sat, 22 Jan 2005 20:35:26 +0300 (MSK) (envelope-from ache) Date: Sat, 22 Jan 2005 20:35:26 +0300 From: Andrey Chernov To: Joerg Wunsch , current@freebsd.org Message-ID: <20050122173526.GD39943@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Joerg Wunsch , current@freebsd.org References: <20050121201400.GQ30862@uriah.heep.sax.de> <20050121221156.GA21459@nagual.pp.ru> <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120222137.GE30862@uriah.heep.sax.de> <20050121230949.GA34313@VARK.MIT.EDU> <20050122113015.GV30862@uriah.heep.sax.de> <20050122171743.GB39943@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050122171743.GB39943@nagual.pp.ru> User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.8; VDF: 6.29.0.75; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [0.0.0.0]); Sat, 22 Jan 2005 20:35:27 +0300 (MSK) Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 17:35:28 -0000 On Sat, Jan 22, 2005 at 08:17:43PM +0300, Andrey Chernov wrote: > even after checking that endptr moved can't check just I mean that another case still possible where errno check placed _before_ endptr checking, to detect, say, wrong user-entered "base" by EINVAL. It can't be detected by portable application in 100% cases, because EINVAL can be returned in other cases too. -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 17:50:05 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D80416A4CE for ; Sat, 22 Jan 2005 17:50:05 +0000 (GMT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 916DA43D1F for ; Sat, 22 Jan 2005 17:50:04 +0000 (GMT) (envelope-from j@uriah.heep.sax.de) Received: from sax.sax.de (localhost [127.0.0.1]) by sax.sax.de (8.12.10/8.12.10) with ESMTP id j0MHo3Yu086662; Sat, 22 Jan 2005 18:50:03 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.12.10/8.12.10/Submit) with UUCP id j0MHo3Qq086661; Sat, 22 Jan 2005 18:50:03 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: from uriah.heep.sax.de (localhost [127.0.0.1]) by uriah.heep.sax.de (8.13.1/8.13.1) with ESMTP id j0MHlXO2035067; Sat, 22 Jan 2005 18:47:33 +0100 (MET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.13.1/8.13.1/Submit) id j0MHlX69035066; Sat, 22 Jan 2005 18:47:33 +0100 (MET) (envelope-from j) Date: Sat, 22 Jan 2005 18:47:33 +0100 From: Joerg Wunsch To: current@freebsd.org Message-ID: <20050122174733.GZ30862@uriah.heep.sax.de> References: <20050121221156.GA21459@nagual.pp.ru> <20050120192324.GA30862@uriah.heep.sax.de> <20050120205501.GA69123@nagual.pp.ru> <20050120211449.GC30862@uriah.heep.sax.de> <20050120214406.GA70088@nagual.pp.ru> <20050120222137.GE30862@uriah.heep.sax.de> <20050121230949.GA34313@VARK.MIT.EDU> <20050122113015.GV30862@uriah.heep.sax.de> <20050122171743.GB39943@nagual.pp.ru> <20050122173526.GD39943@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050122173526.GD39943@nagual.pp.ru> User-Agent: Mutt/1.4.2.1i X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-GPG-Fingerprint: 5E84 F980 C3CA FD4B B584 1070 F48C A81B 69A8 5873 X-Spam-Status: No, score=-2.6 required=7.5 tests=AWL,BAYES_00 autolearn=ham version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on uriah.heep.sax.de cc: Andrey Chernov Subject: Re: Implementation errors in strtol() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joerg Wunsch List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 17:50:05 -0000 As Andrey Chernov wrote: > > even after checking that endptr moved can't check just > I mean that another case still possible where errno check placed > _before_ endptr checking, to detect, say, wrong user-entered "base" > by EINVAL. It can't be detected by portable application in 100% > cases, because EINVAL can be returned in other cases too. But you'll probably agree that in 99.99 % of all cases, strtol() is used using a fixed, developer-given value for base. ;-) Btw., first checking for a valid conversion (using endptr), and then checking errno would still work fine in that case, as after the conversion was identified to be valid, the only source for errno == EINVAL remaining is a wrong value for `base'. So there's still no need to explicitly consider EINVAL in any other context... But I guess we are really starting to bore anyone else, so if you still disagree with the above, let's take that privately, poshalujsta. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 18:00:05 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC32B16A4CE; Sat, 22 Jan 2005 18:00:05 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FAC843D46; Sat, 22 Jan 2005 17:57:44 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id j0MHu5IG060908; Sat, 22 Jan 2005 10:56:05 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 22 Jan 2005 10:57:19 -0700 (MST) Message-Id: <20050122.105719.62254847.imp@bsdimp.com> To: bzeeb-lists@lists.zabbadoz.net From: "M. Warner Losh" In-Reply-To: References: X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: current@freebsd.org cc: net@freebsd.org Subject: Re: mem leak in mii ? (fwd) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 18:00:06 -0000 In message: "Bjoern A. Zeeb" writes: : * all PHY drivers currently seem to use mii_phy_detach for : device_detach. If any implements his own function it will be : responsible for freeing the ivars allocated in miibus_probe. This : should perhaps be documented somewhere ? I think that the current patches are incorrect from a newbus point of view. They may solve the problem, but just smell wrong... : : patch can also be found at : http://sources.zabbadoz.net/freebsd/patchset/mii-memleaks.diff : : : Index: mii.c : =================================================================== : RCS file: /local/mirror/FreeBSD/r/ncvs/src/sys/dev/mii/mii.c,v : retrieving revision 1.20 : diff -u -p -r1.20 mii.c : --- mii.c 15 Aug 2004 06:24:40 -0000 1.20 : +++ mii.c 23 Nov 2004 17:08:58 -0000 : @@ -111,7 +111,7 @@ miibus_probe(dev) : struct mii_attach_args ma, *args; : struct mii_data *mii; : device_t child = NULL, parent; : - int bmsr, capmask = 0xFFFFFFFF; : + int count = 0, bmsr, capmask = 0xFFFFFFFF; : : mii = device_get_softc(dev); : parent = device_get_parent(dev); : @@ -145,12 +145,26 @@ miibus_probe(dev) : : args = malloc(sizeof(struct mii_attach_args), : M_DEVBUF, M_NOWAIT); : + if (args == NULL) { : + device_printf(dev, "%s: memory allocation failure, " : + "phyno %d", __func__, ma.mii_phyno); : + continue; : + } : bcopy((char *)&ma, (char *)args, sizeof(ma)); : child = device_add_child(dev, NULL, -1); : + if (child == NULL) { : + free(args, M_DEVBUF); : + device_printf(dev, "%s: device_add_child failed", : + __func__); : + continue; : + } : device_set_ivars(child, args); : + count++; : + /* XXX should we break here or is it really possible : + * to find more then one PHY ? */ : } : : - if (child == NULL) : + if (count == 0) : return(ENXIO); : : device_set_desc(dev, "MII bus"); : @@ -173,12 +187,15 @@ miibus_attach(dev) : */ : mii->mii_ifp = device_get_softc(device_get_parent(dev)); : v = device_get_ivars(dev); : + if (v == NULL) : + return (ENXIO); : ifmedia_upd = v[0]; : ifmedia_sts = v[1]; : + device_set_ivars(dev, NULL); : + free(v, M_DEVBUF); : ifmedia_init(&mii->mii_media, IFM_IMASK, ifmedia_upd, ifmedia_sts); : - bus_generic_attach(dev); : : - return(0); : + return (bus_generic_attach(dev)); : } newbusly, this is bogus. device foo should never set its own ivars. Nor should it ever get its own ivars to do anything with. parent accessor functions are needed here. : int : @@ -186,8 +203,14 @@ miibus_detach(dev) : device_t dev; : { : struct mii_data *mii; : + void *v; : : bus_generic_detach(dev); : + v = device_get_ivars(dev); : + if (v != NULL) { : + device_set_ivars(dev, NULL); : + free(v, M_DEVBUF); : + } : mii = device_get_softc(dev); : ifmedia_removeall(&mii->mii_media); : mii->mii_ifp = NULL; Newbusly, this is incorrect. The parent bus should be freeing the ivars, since it is the one that should have put the ivars there in the first place. : @@ -305,12 +328,15 @@ mii_phy_probe(dev, child, ifmedia_upd, i : int bmsr, i; : : v = malloc(sizeof(vm_offset_t) * 2, M_DEVBUF, M_NOWAIT); : - if (v == 0) { : + if (v == NULL) : return (ENOMEM); : - } : v[0] = ifmedia_upd; : v[1] = ifmedia_sts; : *child = device_add_child(dev, "miibus", -1); : + if (*child == NULL) { : + free(v, M_DEVBUF); : + return (ENXIO); : + } : device_set_ivars(*child, v); : : for (i = 0; i < MII_NPHY; i++) { This appears to be correct, because the ivars are set on the child that's added. : @@ -324,14 +350,22 @@ mii_phy_probe(dev, child, ifmedia_upd, i : } : : if (i == MII_NPHY) { : + device_set_ivars(dev, NULL); : + free(v, M_DEVBUF); : device_delete_child(dev, *child); : *child = NULL; : return(ENXIO); : } : : - bus_generic_attach(dev); : + i = bus_generic_attach(dev); : : - return(0); : + v = device_get_ivars(*child); : + if (v != NULL) { : + device_set_ivars(*child, NULL); : + free(v, M_DEVBUF); : + } : + : + return (i); : } This appears to be correct, since it is the bus managing the child's ivars. : /* : Index: mii_physubr.c : =================================================================== : RCS file: /local/mirror/FreeBSD/r/ncvs/src/sys/dev/mii/mii_physubr.c,v : retrieving revision 1.21 : diff -u -p -r1.21 mii_physubr.c : --- mii_physubr.c 29 May 2004 18:09:10 -0000 1.21 : +++ mii_physubr.c 23 Nov 2004 17:07:30 -0000 : @@ -522,7 +522,13 @@ int : mii_phy_detach(device_t dev) : { : struct mii_softc *sc; : + void *args; : : + args = device_get_ivars(dev); : + if (args != NULL) { : + device_set_ivars(dev, NULL); : + free(args, M_DEVBUF); : + } : sc = device_get_softc(dev); : mii_phy_down(sc); : sc->mii_dev = NULL; This looks bogus from a newbus perspective. Warner From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 18:04:45 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0401D16A4CE for ; Sat, 22 Jan 2005 18:04:45 +0000 (GMT) Received: from postfix3-1.free.fr (postfix3-1.free.fr [213.228.0.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id A16BF43D31 for ; Sat, 22 Jan 2005 18:04:44 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix3-1.free.fr (Postfix) with ESMTP id 7BE2A173482 for ; Sat, 22 Jan 2005 19:04:43 +0100 (CET) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id C3536407C; Sat, 22 Jan 2005 19:04:33 +0100 (CET) Date: Sat, 22 Jan 2005 19:04:33 +0100 From: Jeremie Le Hen To: freebsd-current@freebsd.org Message-ID: <20050122180433.GH36660@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: panic: mutex Giant not owned (ffs_vnops.c) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 18:04:45 -0000 Hi, on a very -CURRENT system, I cannot use a vnode-based mdconfig(8) any longer, the following panic (sorry but this is hand-written) occured when I performed this command : %%% # mdconfig -a -t vnode -f /boot/profile/home panic: mutex Giant not owned at ../../../ufs/ffs/ffs_vnops.c:350 KDB: stack backtrace: kdb_backtrace() panic() _mtx_assert() ffs_read() VOP_READ_AP() mdstart_vnode() md_kthread() fork_exit() fork_trampoline() -- trap 0x1, eip = 0, ... db> show alllocks db> %%% I think I can get a kernel dump if needed (doadump() seems to work). All I can say is that I'm pretty sure this was working around Christmas. IIRC, I tried various kernel dates and the earliest one (2004.01.01) is panic()'ing as well, but I'm would not bet too much on it (I had a few unwanted kernel source changes when I tried). Note that I'm sending this report now because I made a `cvs up -C' so I *know* my kernel tree is clean today. Please, don't hesitate to ask me for deeper debugging informations. Regards, -- Jeremie Le Hen jeremie@le-hen.org From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 18:55:38 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2566716A4CE; Sat, 22 Jan 2005 18:55:38 +0000 (GMT) Received: from hetzner.co.za (lfw.hetzner.co.za [196.7.18.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3651043D31; Sat, 22 Jan 2005 18:55:36 +0000 (GMT) (envelope-from ianf@hetzner.co.za) Received: from localhost ([127.0.0.1]) by hetzner.co.za with esmtp (Exim 3.36 #1) id 1CsQQ2-0007IA-00; Sat, 22 Jan 2005 20:55:34 +0200 To: jhb@freebsd.org From: Ian FREISLICH In-reply-to: Your message of "Fri, 21 Jan 2005 09:33:13 +0200." X-Attribution: BOFH Date: Sat, 22 Jan 2005 20:55:34 +0200 Sender: ianf@hetzner.co.za Message-Id: cc: freebsd-current@freebsd.org Subject: Re: LOR and boot time lockups X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 18:55:38 -0000 Ian FREISLICH wrote: > Hi > > I've been unable to successfully boot a kernel since Jan 19. The > offending change happened between Jan 10 and Jan 19. I will do the > binary search for the change if nobody has any ideas, but I want to > ask first; it takes little over an hour to compile a kernel on this > system. > > It fails at the ATA probe, or if I remove ata from the kernel, the > last message is from somewhere in the SCSI probe: "Waiting 15 seconds > for SCSI devices to settle". I can't reasonably remove the SCSI > stuff from the kernel to see what happens next because the ufs root > is on a SCSI disk. I narrowed it down to this change (it boots with 1.238, but not 1.239): Index: mptable.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/mptable.c,v retrieving revision 1.238 retrieving revision 1.239 diff -u -d -r1.238 -r1.239 --- mptable.c 12 Jan 2005 18:24:32 -0000 1.238 +++ mptable.c 18 Jan 2005 20:27:24 -0000 1.239 @@ -25,7 +25,7 @@ */ #include -__FBSDID("$FreeBSD: src/sys/i386/i386/mptable.c,v 1.238 2005/01/12 18:24:32 jhb Exp $"); +__FBSDID("$FreeBSD: src/sys/i386/i386/mptable.c,v 1.239 2005/01/18 20:27:24 jhb Exp $"); #include "opt_mptable_force_htt.h" #include @@ -580,12 +580,18 @@ KASSERT(src_bus <= mptable_maxbusid, ("bus id %d too large", src_bus)); switch (busses[src_bus].bus_type) { case ISA: - return (INTR_TRIGGER_EDGE); +#ifndef PC98 + if (elcr_found) + return (elcr_read_trigger(src_bus_irq)); + else +#endif + return (INTR_TRIGGER_EDGE); case PCI: return (INTR_TRIGGER_LEVEL); #ifndef PC98 case EISA: KASSERT(src_bus_irq < 16, ("Invalid EISA IRQ %d", src_bus_irq)); + KASSERT(elcr_found, ("Missing ELCR")); return (elcr_read_trigger(src_bus_irq)); #endif default: > At least the debugger is avalable. I don't really know what is > useful information so here's what I can think of off the top of my > head. > > Timecounters tick every 1.000 msec > ipfw2 initialized, divert loadable, rule-based forwarding enabled, default to deny, logging unlimited > Waiting 15 seconds for SCSI devices to settle > *** Waited 1 minute then sent a line break*** > KDB: enter: Line break on console > [thread pid 45 tid 100061 ] > Stopped at kdb_enter+0x2b: nop > db> ce > Tracing pid 45 tid 100061 td 0xc10b8170 > kdb_enter(c062c0eb) at kdb_enter+0x2b > siointr1(c10d8400) at siointr1+0xce > siointr(c10d8400) at siointr+0x5e > intr_execute_handlers(c1018090,d0e98cdc,4,d0e98d28,c05d0633) at intr_execute_ han > dlers+0x7d > lapic_handle_intr(34) at lapic_handle_intr+0x2e > Xapic_isr1() at Xapic_isr1+0x33 > --- interrupt, eip = 0xc04dd1aa, esp = 0xd0e98d20, ebp = 0xd0e98d28 --- > critical_exit(c10afa80,0,c05d02dc,c04b639c,c10afa80) at critical_exit+0xd2 > fork_exit(c04b639c,c10afa80,d0e98d48) at fork_exit+0x6c > fork_trampoline() at fork_trampoline+0x8 > --- trap 0x1, eip = 0, esp = 0xd0e98d7c, ebp = 0 --- > db> sho pcpu 0 > cpuid = 0 > curthread = 0xc10b8170: pid 45 "swi0: sio" > curpcb = 0xd0e98da0 > fpcurthread = none > idlethread = 0xc0fe1730: pid 12 "idle: cpu0" > APIC ID = 0 > currentldt = 0x28 > db> sho pcpu 1 > cpuid = 1 > curthread = 0xc0fe15c0: pid 11 "idle: cpu1" > curpcb = 0 > fpcurthread = none > idlethread = 0xc0fe15c0: pid 11 "idle: cpu1" > APIC ID = 1 > currentldt = 0x28 > db> ps > pid proc uid ppid pgrp flag stat wmesg wchan cmd > 45 c10b59d8 0 0 0 0000204 [CPU 0] swi0: sio > 8 c10b5bd0 0 0 0 0000204 [RUNQ] aic_recovery0 > 7 c102bbd0 0 0 0 0000204 [RUNQ] aic_recovery0 > 44 c102bdc8 0 0 0 0000204 [RUNQ] usbtask > 43 c103d000 0 0 0 0000204 [RUNQ] usb0 > 6 c103d1f8 0 0 0 0000204 [RUNQ] kqueue taskq > 42 c103d3f0 0 0 0 0000204 [IWAIT] swi2: cambio > 41 c103d5e8 0 0 0 0000204 [IWAIT] swi5:+ > 5 c103d7e0 0 0 0 0000204 [RUNQ] thread taskq > 40 c103d9d8 0 0 0 0000204 [IWAIT] swi6:+ > 39 c103dbd0 0 0 0 0000204 [IWAIT] swi6: task queue > 38 c103ddc8 0 0 0 0000204 [RUNQ] yarrow > 4 c103f000 0 0 0 0000204 [RUNQ] g_down > 3 c103f1f8 0 0 0 0000204 [RUNQ] g_up > 2 c10225e8 0 0 0 0000204 [RUNQ] g_event > 37 c10227e0 0 0 0 0000204 [IWAIT] swi1: net > 36 c10229d8 0 0 0 0000204 [IWAIT] swi3: vm > 35 c1022bd0 0 0 0 000020c [RUNQ] swi4: clock sio > 34 c1022dc8 0 0 0 0000204 [IWAIT] irq0: clk > 33 c102b000 0 0 0 0000204 [IWAIT] irq22: > 32 c102b1f8 0 0 0 0000204 [IWAIT] irq21: > 31 c102b3f0 0 0 0 0000204 [IWAIT] irq20: > 30 c102b5e8 0 0 0 0000204 [IWAIT] irq19: > 29 c102b7e0 0 0 0 0000204 [IWAIT] irq18: > 28 c102b9d8 0 0 0 0000204 [IWAIT] irq17: > 27 c0fea1f8 0 0 0 0000204 [IWAIT] irq16: xl0 ahc0 > 26 c0fea3f0 0 0 0 0000204 [IWAIT] irq15: > 25 c0fea5e8 0 0 0 0000204 [IWAIT] irq14: > 24 c0fea7e0 0 0 0 0000204 [IWAIT] irq13: > 23 c0fea9d8 0 0 0 0000204 [IWAIT] irq12: > 22 c0feabd0 0 0 0 0000204 [IWAIT] irq11: uhci0 > 21 c0feadc8 0 0 0 0000204 [IWAIT] irq10: > 20 c1022000 0 0 0 0000204 [IWAIT] irq9: intpm0 > 19 c10221f8 0 0 0 0000204 [IWAIT] irq8: rtc > 18 c10223f0 0 0 0 0000204 [IWAIT] irq7: ppc0 > 17 c0fe0000 0 0 0 0000204 [IWAIT] irq6: > 16 c0fe01f8 0 0 0 0000204 [IWAIT] irq5: > 15 c0fe03f0 0 0 0 0000204 [IWAIT] irq4: sio0 > 14 c0fe05e8 0 0 0 0000204 [IWAIT] irq3: sio1 > 13 c0fe07e0 0 0 0 0000204 [IWAIT] irq1: atkbd0 > 12 c0fe09d8 0 0 0 000020c [Can run] idle: cpu0 > 11 c0fe0bd0 0 0 0 000020c [Can run] idle: cpu1 > 1 c0fe0dc8 0 0 0 0000200 [INACTIVE] swapper > 10 c0fea000 0 0 0 0000204 [RUNQ] ktrace > 0 c0667980 0 0 0 0000200 [SLPQ conifhk 0xc0648f6c][SLP] swappe r > > > I then recompiled with witness and invarients and got the following > LOR earlier in the boot process. I'm not sure if it's related, but > I couldn't find a reference it this particular LOR at > http://sources.zabbadoz.net/freebsd/lor.html. > > lock order reversal > 1st 0xc0c64968 32 (UMA zone) @ /usr/src/sys/vm/uma_core.c:1842 > 2nd 0xc0c59084 system map (system map) @ /usr/src/sys/vm/vm_map.c:2998 > KDB: stack backtrace: > kdb_backtrace(0,ffffffff,c0672c88,c0672b70,c063dee8) at kdb_backtrace+0x29 > witness_checkorder(c0c59084,9,c061f340,bb6) at witness_checkorder+0x54c > _mtx_lock_flags(c0c59084,0,c061f340,bb6) at _mtx_lock_flags+0x5b > _vm_map_lock_read(c0c59000,c061f340,bb6,200007d,c) at _vm_map_lock_read+0x24 > vm_map_lookup(c0820ad8,c7057000,2,c0820adc,c0820acc) at vm_map_lookup+0x28 > vm_fault(c0c59000,c7057000,2,0,c065fea0) at vm_fault+0x66 > trap_pfault(c0820ba0,0,c7057a69) at trap_pfault+0x11b > trap(c0820018,c04e0010,c0610010,c0fd8620,c0c52420) at trap+0x30d > calltrap() at calltrap+0x5 > --- trap 0xc, eip = 0xc0595100, esp = 0xc0820be0, ebp = 0xc0820bec --- > uma_dbg_alloc(c0c52420,0,c0fd8620,c0c64968,0) at uma_dbg_alloc+0x54 > uma_zalloc_arg(c0c52420,0,1) at uma_zalloc_arg+0xfe > malloc(1c,c0640820,1,4,0) at malloc+0xae > resource_list_add(c10ad880,4,0,378,37f) at resource_list_add+0x2e > isa_set_resource(c1042580,c1095e00,4,0,378,8) at isa_set_resource+0x8d > bus_set_resource(c1095e00,4,0,378,8) at bus_set_resource+0x67 > ppc_probe(c1095e00,c1095e00,c0fc7270,c1095e00,c0820d30) at ppc_probe+0xd7 > ppc_isa_probe(c1095e00) at ppc_isa_probe+0x72 > device_probe_child(c1042580,c1095e00,c10af000,c1095e00,1d) at device_probe_ch ild > +0xf8 > device_probe_and_attach(c1095e00) at device_probe_and_attach+0x7d > isa_probe_children(c1042580) at isa_probe_children+0x103 > configure(0,81ec00,81e000,0,c042da65) at configure+0x32 > mi_startup() at mi_startup+0x96 > begin() at begin+0x2c > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xc7057a69 > fault code = supervisor write, page not present > instruction pointer = 0x8:0xc0595100 > stack pointer = 0x10:0xc0820be0 > frame pointer = 0x10:0xc0820bec > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 0 (swapper) > [thread pid 0 tid 0 ] > Stopped at uma_dbg_alloc+0x54: movb $0xff,0x18(%eax,%ecx,1) > db> sho proc > p = 0xc065fca0, vmspace = 0xc0660000, map = 0xc0660000, pmap = 0xc06600c0 > Task map 0xc0660000: pmap=0xc06600c0, nentries=0, version=1 > db> ps > pid proc uid ppid pgrp flag stat wmesg wchan cmd > 8 c10b5bd0 0 0 0 0000204 [RUNQ] aic_recovery0 > 7 c102bbd0 0 0 0 0000204 [RUNQ] aic_recovery0 > 44 c102bdc8 0 0 0 0000204 [RUNQ] usbtask > 43 c103d000 0 0 0 0000204 [RUNQ] usb0 > 42 c103d1f8 0 0 0 0000204 [IWAIT] swi2: cambio > 41 c103d3f0 0 0 0 0000204 [IWAIT] swi5:+ > 6 c103d5e8 0 0 0 0000204 [RUNQ] thread taskq > 40 c103d7e0 0 0 0 0000204 [IWAIT] swi6:+ > 39 c103d9d8 0 0 0 0000204 [IWAIT] swi6: task queue > 5 c103dbd0 0 0 0 0000204 [RUNQ] kqueue taskq > 38 c103ddc8 0 0 0 0000204 [RUNQ] yarrow > 4 c103f000 0 0 0 0000204 [RUNQ] g_down > 3 c103f1f8 0 0 0 0000204 [RUNQ] g_up > 2 c10225e8 0 0 0 0000204 [RUNQ] g_event > 37 c10227e0 0 0 0 0000204 [IWAIT] swi1: net > 36 c10229d8 0 0 0 0000204 [IWAIT] swi3: vm > 35 c1022bd0 0 0 0 000020c [IWAIT] swi4: clock > 34 c1022dc8 0 0 0 0000204 [IWAIT] irq0: > 33 c102b000 0 0 0 0000204 [IWAIT] irq22: > 32 c102b1f8 0 0 0 0000204 [IWAIT] irq21: > 31 c102b3f0 0 0 0 0000204 [IWAIT] irq20: > 30 c102b5e8 0 0 0 0000204 [IWAIT] irq19: > 29 c102b7e0 0 0 0 0000204 [IWAIT] irq18: > 28 c102b9d8 0 0 0 0000204 [IWAIT] irq17: > 27 c0fea1f8 0 0 0 0000204 [IWAIT] irq16: xl0 ahc0 > 26 c0fea3f0 0 0 0 0000204 [IWAIT] irq15: > 25 c0fea5e8 0 0 0 0000204 [IWAIT] irq14: > 24 c0fea7e0 0 0 0 0000204 [IWAIT] irq13: > 23 c0fea9d8 0 0 0 0000204 [IWAIT] irq12: > 22 c0feabd0 0 0 0 0000204 [RUNQ] irq11: uhci0 > 21 c0feadc8 0 0 0 0000204 [IWAIT] irq10: > 20 c1022000 0 0 0 0000204 [IWAIT] irq9: intpm0 > 19 c10221f8 0 0 0 0000204 [IWAIT] irq8: > 18 c10223f0 0 0 0 0000204 [IWAIT] irq7: > 17 c0fe0000 0 0 0 0000204 [IWAIT] irq6: > 16 c0fe01f8 0 0 0 0000204 [IWAIT] irq5: > 15 c0fe03f0 0 0 0 0000204 [IWAIT] irq4: > 14 c0fe05e8 0 0 0 0000204 [IWAIT] irq3: > 13 c0fe07e0 0 0 0 0000204 [IWAIT] irq1: atkbd0 > 12 c0fe09d8 0 0 0 000020c [Can run] idle: cpu0 > 11 c0fe0bd0 0 0 0 000020c [Can run] idle: cpu1 > 1 c0fe0dc8 0 0 0 0000200 [INACTIVE] swapper > 10 c0fea000 0 0 0 0000204 [RUNQ] ktrace > 0 c065fca0 0 0 0 0000200 [CPU 0] swapper > db> show pcpu > cpuid = 0 > curthread = 0xc065fea0: pid 0 "swapper" > curpcb = 0xc0820da0 > fpcurthread = none > idlethread = 0xc0fe1730: pid 12 "idle: cpu0" > APIC ID = 0 > currentldt = 0x28 > spin locks held: > db> show pcpu 1 > cpuid = 1 > curthread = 0xc0fe15c0: pid 11 "idle: cpu1" > curpcb = 0 > fpcurthread = none > idlethread = 0xc0fe15c0: pid 11 "idle: cpu1" > APIC ID = 1 > currentldt = 0x28 > spin locks held: > > > -- > Ian Freislich > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Ian Freislich From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 19:02:13 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E95AB16A4CF for ; Sat, 22 Jan 2005 19:02:13 +0000 (GMT) Received: from mortis.over-yonder.net (adsl-222-86-182.jan.bellsouth.net [68.222.86.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36D7B43D3F for ; Sat, 22 Jan 2005 19:02:13 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: by mortis.over-yonder.net (Postfix, from userid 100) id A46AF21012; Sat, 22 Jan 2005 13:02:11 -0600 (CST) Date: Sat, 22 Jan 2005 13:02:11 -0600 From: "Matthew D. Fuller" To: Alexander Leidinger Message-ID: <20050122190211.GA2081@over-yonder.net> References: <20050122120810.05b8a0e3@Magellan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050122120810.05b8a0e3@Magellan.Leidinger.net> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.6i-fullermd.2 cc: current@freebsd.org Subject: Re: Strange behavior of "top" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 19:02:14 -0000 On Sat, Jan 22, 2005 at 12:08:10PM +0100 I heard the voice of Alexander Leidinger, and lo! it spake thus: > > It tells me that 23% of CPU are used by userland processes. But I > only see 1.5% used in the process listing. The galeon-bin process > shows alot of used CPU time (for this small uptime), and I wouldn't > be surprised if it is the galeon process which is eating the > majority of the CPU resources (I have ~85 tabs open with content), > but I object to the 0% CPU display then. Aren't threaded processes still not showing CPU usage stats? -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 19:33:15 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9248B16A4CE for ; Sat, 22 Jan 2005 19:33:15 +0000 (GMT) Received: from mail.snowfall.se (guldivar.globalwire.se [212.112.184.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5D4343D39 for ; Sat, 22 Jan 2005 19:33:14 +0000 (GMT) (envelope-from stefan@snowfall.se) Received: from [213.136.48.102] (unknown [213.136.48.102]) by mail.snowfall.se (Postfix) with ESMTP id 4A2B551EA for ; Sat, 22 Jan 2005 20:33:12 +0100 (CET) Message-ID: <41F2AA80.3030408@snowfall.se> Date: Sat, 22 Jan 2005 20:33:20 +0100 From: Stefan Cars User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Boot / Install freeze with Dell PE1850 5.3 and amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 19:33:15 -0000 Hi! I'm experiencing about the same problems as written before regarding 5.3-BETA3 (said to be fixed in BETA4) (http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2004-09/0826.html, http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2004-09/1528.html). My box just freezes and does not show any error message after the error message below. The thing is that I was able to install the system on a single processor 1850 with the exact same RAID and disk configuration. The troubling machine is a Dell 1850 with 2x2.8GHZ Noncona, 4GB of RAM The working machine is a Dell 1850 with 2.2.8GHZ Noncona, 1GB of RAM, which installs fine with amd64. Installing the i386 version works fine, amd64 is not. It hangs initializing the ATA CD-ROMs: acd: CDROM at ata2-slave BIOSPIO Kind Regards, Stefan Cars From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 20:03:40 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CFCE16A4CE for ; Sat, 22 Jan 2005 20:03:40 +0000 (GMT) Received: from s1.vhost.cz (s1.vhost.cz [82.208.27.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B70D43D46 for ; Sat, 22 Jan 2005 20:03:39 +0000 (GMT) (envelope-from konfer@mikulas.com) Received: (qmail 25832 invoked by alias); 22 Jan 2005 21:03:38 +0100 Received: from unknown (HELO localhost) (127.10.10.10) by s1.vhost.cz with SMTP; 22 Jan 2005 21:03:38 +0100 Received: from unknown ([127.0.0.1]) by localhost (s1.vhost.cz [127.0.0.1]) (amavisd-new, port 10628) id 25818-01 for ; Sat, 22 Jan 2005 21:03:37 +0100 (CET) Received: from unknown (HELO ?195.122.218.78?) (jiri@mikulas.com@195.122.218.78) by s1.vhost.cz with AES256-SHA encrypted SMTP; 22 Jan 2005 21:03:37 +0100 Message-ID: <41F2B1A6.5090006@mikulas.com> Date: Sat, 22 Jan 2005 21:03:50 +0100 From: Jiri Mikulas User-Agent: Mozilla Thunderbird 1.0 (X11/20050101) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at vhost.cz Subject: LOR if_ath.c:842 ieee80211_node.c:1488 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 20:03:40 -0000 Hello FYI in AP mode ifconfig ath0 channel 42 media autoselect mode 11a mediaopt hostap platan6# uname -a FreeBSD platan6.praha12.czf 6.0-CURRENT FreeBSD 6.0-CURRENT #1: Sat Jan 22 01:19:19 CET 2005 root@platan6.praha12.czf:/usr/obj/usr/src/sys/ROUTER-IPFW-PF i386 ~~~~~~~~~~~~~~~~~ ath0@pci0:10:0: class=0x020000 card=0x7005144f chip=0x0013168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5213 802.11a/b/g Wireless Adapter' class = network subclass = ethernet ath0: mem 0xd4800000-0xd480ffff irq 12 at device 10.0 on pci0 ath0: Ethernet address: 00:90:4b:ca:33:19 ath0: mac 5.9 phy 4.3 radio 3.6 ath0: flags=8843 mtu 1500 inet6 fe80::290:4bff:feca:3319%ath0 prefixlen 64 scopeid 0x2 inet 192.168.2.2 netmask 0xffffff00 broadcast 192.168.2.255 ether 00:90:4b:ca:33:19 media: IEEE 802.11 Wireless Ethernet autoselect mode 11a status: associated ssid A channel 42 bssid 00:90:4b:ca:33:19 authmode OPEN privacy OFF txpowmax 54 dtimperiod 1 bintval 100 ~~~~~~~~~~~~~~~~~ device ath_rate_onoe ~~~~~~~~~~~~~~~~~ lock order reversal 1st 0xc1a9de28 ath0 (network driver) @ /usr/src/sys/dev/ath/if_ath.c:842 2nd 0xc1e89eb4 ath0 (802.11 scangen) @ /usr/src/sys/net80211/ieee80211_node.c:1488 KDB: stack backtrace: kdb_backtrace(0,ffffffff,c0809c30,c0809b68,c07a7d28) at kdb_backtrace+0x29 witness_checkorder(c1e89eb4,9,c0766c6e,5d0) at witness_checkorder+0x54c _mtx_lock_flags(c1e89eb4,0,c0766c6e,5d0,c1a9d3f4) at _mtx_lock_flags+0x5b ieee80211_iterate_nodes(c1e89e00,c04a0034,0) at ieee80211_iterate_nodes+0x21 ath_rate_newstate(c1a9d000,4) at ath_rate_newstate+0x7f ath_newstate(c1a9d3f4,4,ffffffff,c1a9d3f4,c1a9d3f4) at ath_newstate+0x1bf ieee80211_create_ibss(c1a9d3f4,c1a9d6c6) at ieee80211_create_ibss+0x1ff ieee80211_newstate(c1a9d3f4,1,ffffffff,d865cbc4,c0730b20) at ieee80211_newstate+0x2e4 ath_newstate(c1a9d3f4,1,ffffffff) at ath_newstate+0x2a3 ath_init(c1a9d000) at ath_init+0x167 ath_ioctl(c1a9d000,801c69ea,c1c67020,d865cc48,c05582a4) at ath_ioctl+0x19e in_control(c1e5d000,801c69ea,c1c67020,c1a9d000,c1bfb730) at in_control+0xabd ifioctl(c1e5d000,801c69ea,c1c67020,c1bfb730,0) at ifioctl+0x198 soo_ioctl(c1c259d4,801c69ea,c1c67020,c1e3fb80,c1bfb730) at soo_ioctl+0x2db ioctl(c1bfb730,d865cd14,3,2,282) at ioctl+0x370 syscall(2f,2f,2f,bfbfe40c,9) at syscall+0x213 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x280c4853, esp = 0xbfbfe3cc, ebp = 0xbfbfe428 --- From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 20:24:46 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 07B4F16A4CE for ; Sat, 22 Jan 2005 20:24:46 +0000 (GMT) Received: from web26808.mail.ukl.yahoo.com (web26808.mail.ukl.yahoo.com [217.146.176.84]) by mx1.FreeBSD.org (Postfix) with SMTP id 3D70143D2D for ; Sat, 22 Jan 2005 20:24:45 +0000 (GMT) (envelope-from cguttesen@yahoo.dk) Received: (qmail 2292 invoked by uid 60001); 22 Jan 2005 20:24:44 -0000 Message-ID: <20050122202444.2290.qmail@web26808.mail.ukl.yahoo.com> Received: from [194.248.174.50] by web26808.mail.ukl.yahoo.com via HTTP; Sat, 22 Jan 2005 21:24:44 CET Date: Sat, 22 Jan 2005 21:24:44 +0100 (CET) From: Claus Guttesen To: Stefan Cars , current@freebsd.org In-Reply-To: <41F2AA80.3030408@snowfall.se> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: Boot / Install freeze with Dell PE1850 5.3 and amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 20:24:46 -0000 > The troubling machine is a Dell 1850 with 2x2.8GHZ > Noncona, 4GB of RAM > The working machine is a Dell 1850 with 2.2.8GHZ > Noncona, 1GB of RAM, > which installs fine with amd64. > > It hangs initializing the ATA CD-ROMs: Had the same problem with a Dell 2850 and 4 GB RAM. Found the following hints on freebsd.org: 1. Press 6 to enter boot prompt. 2. Type 'set hw.physmem="2G" 3. Enter boot to boot :D 4. Cvsup to latest 5.3-stable by adding *default release=cvs tag=RELENG_5 to your sup-file 5. Rebuild world and kernel as normal. 6. Reboot. This made my Dell 2850 work without hw.physmem. If you need to reboot before you have installed new world/kernel don't forget to enter ph.physmem again. Important that the cvs tag is *not* RELENG_5_3. HTH Claus From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 20:44:57 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4772316A4CE for ; Sat, 22 Jan 2005 20:44:57 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C562143D41 for ; Sat, 22 Jan 2005 20:44:56 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id j0MKid7q034688 for ; Sat, 22 Jan 2005 15:44:39 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)j0MKidVg034685 for ; Sat, 22 Jan 2005 20:44:39 GMT (envelope-from robert@fledge.watson.org) Date: Sat, 22 Jan 2005 20:44:39 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: current@FreeBSD.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Notebook fan stuck on? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 20:44:57 -0000 I'm not sure when this began, but I noticed recently that, once my notebook's fan gets turned on due to the temperature rising, it seems never to get turned off. I'm not sure how to begin debugging this -- in particular, how to decide if it's because the notebook isn't cooling properly (perhaps due to ACPI or hardware?) or if we're failing to turn it back down against once it is cooled (perhaps also due to ACPI?). Regardless, it actually has the effect of generating quite a bit more noise, and using moderately more battery, so any pointers on where to start looking for helpful. Thanks, Robert N M Watson From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 20:49:18 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A898416A4CE for ; Sat, 22 Jan 2005 20:49:18 +0000 (GMT) Received: from mail.snowfall.se (guldivar.globalwire.se [212.112.184.140]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8F9143D2D for ; Sat, 22 Jan 2005 20:49:17 +0000 (GMT) (envelope-from stefan@snowfall.se) Received: from [83.226.130.184] (c-b882e253.014-349-7570701.cust.bredbandsbolaget.se [83.226.130.184]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.snowfall.se (Postfix) with ESMTP id 0020F51F1; Sat, 22 Jan 2005 21:49:15 +0100 (CET) Message-ID: <41F2BC4B.3060901@snowfall.se> Date: Sat, 22 Jan 2005 21:49:15 +0100 From: Stefan Cars User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Claus Guttesen References: <20050122202444.2290.qmail@web26808.mail.ukl.yahoo.com> In-Reply-To: <20050122202444.2290.qmail@web26808.mail.ukl.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: Boot / Install freeze with Dell PE1850 5.3 and amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 20:49:18 -0000 Hi! Thanks very much, is RELENG_5 very stable then ? Is it recommended do use on RELENG_5 on a production system, not RELENG_5_3 ? Kind Regards, Stefan Crs Claus Guttesen wrote: >>The troubling machine is a Dell 1850 with 2x2.8GHZ >>Noncona, 4GB of RAM >>The working machine is a Dell 1850 with 2.2.8GHZ >>Noncona, 1GB of RAM, >>which installs fine with amd64. >> >>It hangs initializing the ATA CD-ROMs: > > > Had the same problem with a Dell 2850 and 4 GB RAM. > Found the following hints on freebsd.org: > > 1. Press 6 to enter boot prompt. > 2. Type 'set hw.physmem="2G" > 3. Enter boot to boot :D > 4. Cvsup to latest 5.3-stable by adding > *default release=cvs tag=RELENG_5 > to your sup-file > 5. Rebuild world and kernel as normal. > 6. Reboot. > > This made my Dell 2850 work without hw.physmem. If you > need to reboot before you have installed new > world/kernel don't forget to enter ph.physmem again. > > Important that the cvs tag is *not* RELENG_5_3. > > HTH > Claus > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 20:53:45 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8086716A4CE; Sat, 22 Jan 2005 20:53:45 +0000 (GMT) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61C9643D41; Sat, 22 Jan 2005 20:53:45 +0000 (GMT) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.12.8) with ESMTP id j0MKrjHp023932; Sat, 22 Jan 2005 12:53:45 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id j0MKrj0d023931; Sat, 22 Jan 2005 12:53:45 -0800 (PST) (envelope-from rizzo) Date: Sat, 22 Jan 2005 12:53:45 -0800 From: Luigi Rizzo To: Robert Watson Message-ID: <20050122125345.B23672@xorpc.icir.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from rwatson@freebsd.org on Sat, Jan 22, 2005 at 08:44:39PM +0000 cc: current@freebsd.org Subject: Re: Notebook fan stuck on? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 20:53:45 -0000 On Sat, Jan 22, 2005 at 08:44:39PM +0000, Robert Watson wrote: > > I'm not sure when this began, but I noticed recently that, once my > notebook's fan gets turned on due to the temperature rising, it seems > never to get turned off. I'm not sure how to begin debugging this -- in Robert, i think it is because it was too warm in Cambridge last week; the GPS in the notebook thinks it is in britain and it is January, so it turns on the hidden x1.5 overclocking mode that CPU manufacturers have to perform well in benchmarks. This setting is not under control of ACPI, which indeed tries to cool down the CPU by turning the fan ON, and possibly throttling the clock (which however is faster than ACPI believes). ok just kidding :) luigi > particular, how to decide if it's because the notebook isn't cooling > properly (perhaps due to ACPI or hardware?) or if we're failing to turn it > back down against once it is cooled (perhaps also due to ACPI?). > Regardless, it actually has the effect of generating quite a bit more > noise, and using moderately more battery, so any pointers on where to > start looking for helpful. > > Thanks, > > Robert N M Watson > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 20:58:04 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B569D16A4CE for ; Sat, 22 Jan 2005 20:58:04 +0000 (GMT) Received: from web26804.mail.ukl.yahoo.com (web26804.mail.ukl.yahoo.com [217.146.176.80]) by mx1.FreeBSD.org (Postfix) with SMTP id F3F3943D2D for ; Sat, 22 Jan 2005 20:58:03 +0000 (GMT) (envelope-from cguttesen@yahoo.dk) Received: (qmail 76357 invoked by uid 60001); 22 Jan 2005 20:58:03 -0000 Message-ID: <20050122205803.76355.qmail@web26804.mail.ukl.yahoo.com> Received: from [194.248.174.50] by web26804.mail.ukl.yahoo.com via HTTP; Sat, 22 Jan 2005 21:58:03 CET Date: Sat, 22 Jan 2005 21:58:03 +0100 (CET) From: Claus Guttesen To: Stefan Cars In-Reply-To: <41F2BC4B.3060901@snowfall.se> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: current@freebsd.org Subject: Re: Boot / Install freeze with Dell PE1850 5.3 and amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 20:58:04 -0000 > Thanks very much, is RELENG_5 very stable then ? Is > it recommended do > use on RELENG_5 on a production system, not > RELENG_5_3 ? I'm running RELENG_5 (stable) on some webservers, one nfs-server and one db-server (postgresql). Works very nice. According to the current-list RELENG_5 has some enhancements to smp (amongst others) which aren't found in 5_3 and makes it better suited as a server. Claus From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 22:52:13 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59CCA16A4CE for ; Sat, 22 Jan 2005 22:52:13 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0523643D41 for ; Sat, 22 Jan 2005 22:52:13 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id j0MMq7gW024665; Sat, 22 Jan 2005 16:52:07 -0600 (CST) (envelope-from dan) Date: Sat, 22 Jan 2005 16:52:07 -0600 From: Dan Nelson To: "Matthew D. Fuller" Message-ID: <20050122225207.GB33972@dan.emsphone.com> References: <20050122120810.05b8a0e3@Magellan.Leidinger.net> <20050122190211.GA2081@over-yonder.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050122190211.GA2081@over-yonder.net> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: Alexander Leidinger cc: current@freebsd.org Subject: Re: Strange behavior of "top" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 22:52:13 -0000 In the last episode (Jan 22), Matthew D. Fuller said: > On Sat, Jan 22, 2005 at 12:08:10PM +0100 I heard the voice of > Alexander Leidinger, and lo! it spake thus: > > It tells me that 23% of CPU are used by userland processes. But I > > only see 1.5% used in the process listing. The galeon-bin process > > shows alot of used CPU time (for this small uptime), and I wouldn't > > be surprised if it is the galeon process which is eating the > > majority of the CPU resources (I have ~85 tabs open with content), > > but I object to the 0% CPU display then. > > Aren't threaded processes still not showing CPU usage stats? Yes. The only way to tell whether a libpthread-threaded process is consuming CPU is to watch the TIME column in top or ps and see if it's incrementing. You can also switch to libc_r or libthr via libmap.conf, both of which should correctly report CPU (although libc_r is going to be slower, and libthr is not as stable as libpthread). A possible workaround for this might be to have top inspect the process' rusage struct and display that in the CPU% column. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 23:16:05 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9219716A4CE; Sat, 22 Jan 2005 23:16:05 +0000 (GMT) Received: from out006.verizon.net (out006pub.verizon.net [206.46.170.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2EEA43D41; Sat, 22 Jan 2005 23:16:04 +0000 (GMT) (envelope-from Alex.Kovalenko@verizon.net) Received: from RabbitsDen ([70.21.161.195]) by out006.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20050122231604.OCSJ7873.out006.verizon.net@RabbitsDen>; Sat, 22 Jan 2005 17:16:04 -0600 From: "Alexandre \"Sunny\" Kovalenko" To: Robert Watson In-Reply-To: References: Content-Type: text/plain; charset=iso-8859-5 Date: Sat, 22 Jan 2005 18:15:19 -0500 Message-Id: <1106435719.659.6.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit X-Authentication-Info: Submitted using SMTP AUTH at out006.verizon.net from [70.21.161.195] at Sat, 22 Jan 2005 17:16:04 -0600 cc: current@FreeBSD.org Subject: Re: Notebook fan stuck on? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 23:16:05 -0000 On Sat, 2005-01-22 at 20:44 +0000, Robert Watson wrote: > I'm not sure when this began, but I noticed recently that, once my > notebook's fan gets turned on due to the temperature rising, it seems > never to get turned off. I'm not sure how to begin debugging this -- in > particular, how to decide if it's because the notebook isn't cooling > properly (perhaps due to ACPI or hardware?) or if we're failing to turn it > back down against once it is cooled (perhaps also due to ACPI?). > Regardless, it actually has the effect of generating quite a bit more > noise, and using moderately more battery, so any pointers on where to > start looking for helpful. > > Thanks, > > Robert N M Watson > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" What does sysctl hw.acpi.thermal say? Starting point would be looking at whether sysctl hw.acpi.thermal.tzN.temperature changes with time. (for all N your notebook provided). -- Alexandre "Sunny" Kovalenko (Олександр Коваленко) From owner-freebsd-current@FreeBSD.ORG Sat Jan 22 23:17:42 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 971D516A4CE; Sat, 22 Jan 2005 23:17:42 +0000 (GMT) Received: from top.daemonsecurity.com (FW-182-254.go.retevision.es [62.174.254.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id E67A443D31; Sat, 22 Jan 2005 23:17:41 +0000 (GMT) (envelope-from norgaard@locolomo.org) Received: from [192.168.0.32] (charm.daemonsecurity.com [192.168.0.32]) by top.daemonsecurity.com (Postfix) with ESMTP id A1312FD020; Sun, 23 Jan 2005 00:17:40 +0100 (CET) Message-ID: <41F2DF11.5060109@locolomo.org> Date: Sun, 23 Jan 2005 00:17:37 +0100 From: Erik Norgaard User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20041114 X-Accept-Language: en, en-us, da, it, es MIME-Version: 1.0 To: Robert Watson References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@FreeBSD.org Subject: Re: Notebook fan stuck on? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Jan 2005 23:17:42 -0000 Robert Watson wrote: > I'm not sure when this began, but I noticed recently that, once my > notebook's fan gets turned on due to the temperature rising, it seems > never to get turned off. I'm not sure how to begin debugging this -- in > particular, how to decide if it's because the notebook isn't cooling > properly (perhaps due to ACPI or hardware?) or if we're failing to turn it > back down against once it is cooled (perhaps also due to ACPI?). > Regardless, it actually has the effect of generating quite a bit more > noise, and using moderately more battery, so any pointers on where to > start looking for helpful. Hi Robert, I had just that problem with my Asus. Then I cleaned my fan, and now the cooling works fine, and the notebook is silent. Cheers, Erik -- Ph: +34.666334818 web: http://www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 From owner-freebsd-current@FreeBSD.ORG Sun Jan 23 00:00:29 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 255AE16A4CF for ; Sun, 23 Jan 2005 00:00:29 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB32443D39 for ; Sun, 23 Jan 2005 00:00:28 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.12] (g4.samsco.home [192.168.254.12]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id j0N054SA046294; Sat, 22 Jan 2005 17:05:08 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41F2E917.4060208@freebsd.org> Date: Sat, 22 Jan 2005 17:00:23 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040514 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stefan Cars References: <20050122202444.2290.qmail@web26808.mail.ukl.yahoo.com> <41F2BC4B.3060901@snowfall.se> In-Reply-To: <41F2BC4B.3060901@snowfall.se> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: Claus Guttesen cc: current@freebsd.org Subject: Re: Boot / Install freeze with Dell PE1850 5.3 and amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Jan 2005 00:00:29 -0000 Stefan Cars wrote: > Hi! > > Thanks very much, is RELENG_5 very stable then ? Is it recommended do > use on RELENG_5 on a production system, not RELENG_5_3 ? > > Kind Regards, > Stefan Crs > For this 4GB+ problem, you should be using RELENG_5. I've considered merging the fixes for it back to RELENG_5_3, but I'm not 100% satified with them yet. Scott