From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 00:22:11 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D60DC16A41F for ; Sun, 20 Nov 2005 00:22:11 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AC4043D49 for ; Sun, 20 Nov 2005 00:22:11 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 5E74F72DD4; Sat, 19 Nov 2005 16:22:11 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 5904B72DCB; Sat, 19 Nov 2005 16:22:11 -0800 (PST) Date: Sat, 19 Nov 2005 16:22:11 -0800 (PST) From: Doug White To: Ulf Kieber In-Reply-To: <200511150403.jAF43B6f001417@jerry.xoo.net> Message-ID: <20051119162011.I88861@carver.gumbysoft.com> References: <200511150403.jAF43B6f001417@jerry.xoo.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-current@freebsd.org Subject: Re: GEOM error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 00:22:11 -0000 On Tue, 15 Nov 2005, Ulf Kieber wrote: > Re, > > on a 6.0-RELEASE I receive the following error since I tried restoring > a large dump > > Nov 14 12:30:11 nexus kernel: g_vfs_done():da1s1d.bde[WRITE(offset=72350695424, length=131072)]error = 1 > > Besides that, no other errors are logged, especially no SCSI errors. > The problem persists even after the restore has completed. errno 1 is EPERM ("Operation not permitted") and is generally returned if you attempt to write somewhere you're not allowed to. Considering the offset is near the end of the disk, GBDE may be trying to prevent you from overwriting metadata blocks at the end of the partition. How or why restore(8) would be writing there I'm not sure. A SCSI error would return as errno 5 (EIO, "Input/output error"). -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 00:41:47 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C7B6816A41F; Sun, 20 Nov 2005 00:41:47 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 924EA43D46; Sun, 20 Nov 2005 00:41:47 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 7947E72DD4; Sat, 19 Nov 2005 16:41:47 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 76F9872DCB; Sat, 19 Nov 2005 16:41:47 -0800 (PST) Date: Sat, 19 Nov 2005 16:41:47 -0800 (PST) From: Doug White To: Alexander Leidinger In-Reply-To: <20051119165631.093b90b9@Magellan.Leidinger.net> Message-ID: <20051119163635.E88861@carver.gumbysoft.com> References: <20051119162854.2656096a@Magellan.Leidinger.net> <13727.1132414598@critter.freebsd.dk> <20051119165631.093b90b9@Magellan.Leidinger.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: delphij@delphij.net, Poul-Henning Kamp , freebsd-current@FreeBSD.org, Robert Watson , Brian Candler Subject: Re: Logical volume management X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 00:41:47 -0000 On Sat, 19 Nov 2005, Alexander Leidinger wrote: > You can define more than one resource pool with ZFS, and as I did > understand it, the pools are distinct. So if you assign disc1 and disc2 > to poolA and disc3 and disc4 to poolB, and you assign just one FS to > each pool, you still have the same separation like in vinum or > g{mirror,raid3,stripe}. You just have a more complex distribution > algorithm. However the ZMU layer doesn't allow you to stack transforms, so you can't do RAID10 by stacking a stripe transform on a mirror. Score a point for GEOM and the oldie-but-goodie SDS. :) The ZFS code and architecture docs imply that the volume-management aspects and the filesystem are abstracted from one another and are bundled only for administrative simplicity. If they wanted to, the ZMU could have been a separate component and you could have layered UFS on top of it. Most of the code is available through OpenSolaris if you want to see how its done. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 00:47:20 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3DEB416A41F for ; Sun, 20 Nov 2005 00:47:20 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1229543D45 for ; Sun, 20 Nov 2005 00:47:20 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id EF03E72DDB; Sat, 19 Nov 2005 16:47:19 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id E9EA072DCB; Sat, 19 Nov 2005 16:47:19 -0800 (PST) Date: Sat, 19 Nov 2005 16:47:19 -0800 (PST) From: Doug White To: "Wojciech A. Koszek" In-Reply-To: <20051119170018.GA75757@freebsd.czest.pl> Message-ID: <20051119164627.R88861@carver.gumbysoft.com> References: <20051119170018.GA75757@freebsd.czest.pl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-current@freebsd.org Subject: Re: Panic after memory dump and machine reboot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 00:47:20 -0000 On Sat, 19 Nov 2005, Wojciech A. Koszek wrote: > Hello, > > I noticed very strange problem on -CURRENT. If I get a panic, system writes > core and reboots. Just after reboot, filesystem check (yes, I sometimes > forget about sync'ing/mounting in read-only mode) kernel gets another panic, > which is not (directly?) related with this first one -- problem lies > somewhere in syscons(4). Can you please explain in more detail what you are doing when you say "filesystem check"? From this, it sounds like you are running fsck while the FS is mounted, which will cause this behavior. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 01:11:55 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B8E916A41F; Sun, 20 Nov 2005 01:11:55 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id D175F43D45; Sun, 20 Nov 2005 01:11:54 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from [192.168.4.250] (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.13.4/8.13.4) with ESMTP id jAK1BsJM025126; Sat, 19 Nov 2005 17:11:54 -0800 (PST) (envelope-from marcel@xcllnt.net) Mime-Version: 1.0 (Apple Message framework v746.2) To: current@freebsd.org Message-Id: <5D4CE421-AC74-40D6-AB53-836630BB8F19@xcllnt.net> Content-Type: multipart/mixed; boundary=Apple-Mail-3--476909085 From: Marcel Moolenaar Date: Sat, 19 Nov 2005 17:11:53 -0800 X-Mailer: Apple Mail (2.746.2) Cc: alpha@freebsd.org, sparc64@freebsd.org Subject: dc(4) related misalignment trap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 01:11:55 -0000 --Apple-Mail-3--476909085 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed All, On alpha this time: : swapon: adding /dev/da0b as swap device Starting file system checks: /dev/da0a: 38800 files, 486252 used, 3308480 free (41816 frags, 408333 blocks, 1.1% fragmentation) Setting hostname: ds10.pn.xcllnt.net. fatal kernel trap: trap entry = 0x4 (unaligned access fault) faulting va = 0xfffffc000096b73b opcode = 0xc register = 0x1 pc = 0xfffffc0000389cd8 ra = 0xfffffc0000389c98 sp = 0xfffffe001a581800 usp = 0x11ffe4f8 curthread = 0xfffffc003eb1d340 pid = 165, comm = ifconfig [thread pid 165 tid 100034 ] Stopped at dc_setfilt_21143+0x368: stl t0,0x9c(s3) <0xfffffc000095879c> db> bt Tracing pid 165 tid 100034 td 0xfffffc003eb1d340 dc_setfilt_21143() at dc_setfilt_21143+0x368 dc_setfilt() at dc_setfilt+0x58 dc_init_locked() at dc_init_locked+0x9c8 dc_init() at dc_init+0x78 ether_ioctl() at ether_ioctl+0xd8 dc_ioctl() at dc_ioctl+0x370 in6_ifinit() at in6_ifinit+0x11c in6_update_ifa() at in6_update_ifa+0x604 in6_ifattach_linklocal() at in6_ifattach_linklocal+0x198 in6_ifattach() at in6_ifattach+0x110 in6_if_up() at in6_if_up+0xa8 if_route() at if_route+0xa4 if_up() at if_up+0x1c ifhwioctl() at ifhwioctl+0x3a8 ifioctl() at ifioctl+0x178 soo_ioctl() at soo_ioctl+0x6e4 ioctl() at ioctl+0x6e8 syscall() at syscall+0x458 XentSys() at XentSys+0x64 --- syscall (54, FreeBSD ELF64, ioctl) --- Note that the faulting instruction is really the instruction before the one shown. In kgdb: 0xfffffc0000389cd4 : ldwu t0,8(t0) 0xfffffc0000389cd8 : stl t0,156(s3) ldwu = load word unsigned. (kgdb) l *dc_setfilt_21143+0x368 0xfffffc0000389cd8 is in dc_setfilt_21143 (../../../dev/dc/if_dc.c: 1129). 1124 h = dc_mchash_le(sc, ifp->if_broadcastaddr); 1125 sp[h >> 4] |= htole32(1 << (h & 0xF)); 1126 } 1127 1128 /* Set our MAC address */ 1129 sp[39] = DC_SP_MAC(((u_int16_t *)IF_LLADDR(sc- >dc_ifp))[0]); 1130 sp[40] = DC_SP_MAC(((u_int16_t *)IF_LLADDR(sc- >dc_ifp))[1]); 1131 sp[41] = DC_SP_MAC(((u_int16_t *)IF_LLADDR(sc- >dc_ifp))[2]); 1132 1133 sframe->dc_status = htole32(DC_TXSTAT_OWN); (kgdb) f 12 #12 0xfffffc0000389cd8 in dc_setfilt_21143 (sc=0xfffffc0000842000) at ../../../dev/dc/if_dc.c:1129 1129 sp[39] = DC_SP_MAC(((u_int16_t *)IF_LLADDR(sc- >dc_ifp))[0]); (kgdb) p sp $2 = (u_int32_t *) 0xfffffc0000958700 (kgdb) p sc->dc_ifp->if_addr->ifa_addr $5 = (struct sockaddr *) 0xfffffc000096b730 (kgdb) p *(struct sockaddr_dl *)$5 $6 = {sdl_len = 56 '8', sdl_family = 18 '\022', sdl_index = 1, sdl_type = 6 '\006', sdl_nlen = 3 '\003', sdl_alen = 6 '\006', sdl_slen = 0 '\0', sdl_data = "dc0\b\000+\206\"J", '\0' } (kgdb) p $6.sdl_data + $6.sdl_nlen $7 = 0xfffffc000096b73b "\b" Register s3 holds the sp variable ($2 in kgdb) Register t0 holds the result the left-hand side of the statement, which is not properly aligned for a 16-bit load ($7 = register t0 + 8). Rough patch to fix the problem attached: --Apple-Mail-3--476909085 Content-Transfer-Encoding: 7bit Content-Type: application/octet-stream; x-unix-mode=0664; name="if_dc.diff" Content-Disposition: attachment; filename=if_dc.diff Index: if_dc.c =================================================================== RCS file: /home/ncvs/src/sys/dev/dc/if_dc.c,v retrieving revision 1.172 diff -u -r1.172 if_dc.c --- if_dc.c 11 Nov 2005 16:04:50 -0000 1.172 +++ if_dc.c 20 Nov 2005 01:08:09 -0000 @@ -1126,9 +1126,9 @@ } /* Set our MAC address */ - sp[39] = DC_SP_MAC(((u_int16_t *)IF_LLADDR(sc->dc_ifp))[0]); - sp[40] = DC_SP_MAC(((u_int16_t *)IF_LLADDR(sc->dc_ifp))[1]); - sp[41] = DC_SP_MAC(((u_int16_t *)IF_LLADDR(sc->dc_ifp))[2]); + sp[39] = DC_SP_MAC((u_int16_t *)IF_LLADDR(sc->dc_ifp) + 0); + sp[40] = DC_SP_MAC((u_int16_t *)IF_LLADDR(sc->dc_ifp) + 1); + sp[41] = DC_SP_MAC((u_int16_t *)IF_LLADDR(sc->dc_ifp) + 2); sframe->dc_status = htole32(DC_TXSTAT_OWN); CSR_WRITE_4(sc, DC_TXSTART, 0xFFFFFFFF); @@ -1324,9 +1324,9 @@ } /* Set our MAC address */ - sp[0] = DC_SP_MAC(((u_int16_t *)IF_LLADDR(sc->dc_ifp))[0]); - sp[1] = DC_SP_MAC(((u_int16_t *)IF_LLADDR(sc->dc_ifp))[1]); - sp[2] = DC_SP_MAC(((u_int16_t *)IF_LLADDR(sc->dc_ifp))[2]); + sp[0] = DC_SP_MAC((u_int16_t *)IF_LLADDR(sc->dc_ifp) + 0); + sp[1] = DC_SP_MAC((u_int16_t *)IF_LLADDR(sc->dc_ifp) + 1); + sp[2] = DC_SP_MAC((u_int16_t *)IF_LLADDR(sc->dc_ifp) + 2); DC_SETBIT(sc, DC_NETCFG, DC_NETCFG_TX_ON); DC_SETBIT(sc, DC_NETCFG, DC_NETCFG_RX_ON); Index: if_dcreg.h =================================================================== RCS file: /home/ncvs/src/sys/dev/dc/if_dcreg.h,v retrieving revision 1.45 diff -u -r1.45 if_dcreg.h --- if_dcreg.h 10 Aug 2005 20:33:46 -0000 1.45 +++ if_dcreg.h 20 Nov 2005 01:07:24 -0000 @@ -473,9 +473,9 @@ (uintptr_t)(sc->dc_ldata->dc_tx_list + i) - (uintptr_t)sc->dc_ldata) #if BYTE_ORDER == BIG_ENDIAN -#define DC_SP_MAC(x) ((x) << 16) +#define DC_SP_MAC(ptr) (be16dec(ptr) << 16) #else -#define DC_SP_MAC(x) (x) +#define DC_SP_MAC(ptr) (le16dec(ptr)) #endif struct dc_list_data { --Apple-Mail-3--476909085 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed FYI, -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net --Apple-Mail-3--476909085-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 01:14:43 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 064BA16A41F for ; Sun, 20 Nov 2005 01:14:43 +0000 (GMT) (envelope-from chris@haakonia.hitnet.rwth-aachen.de) Received: from ms-dienst.rz.rwth-aachen.de (ms-1.rz.RWTH-Aachen.DE [134.130.3.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B5CD43D45 for ; Sun, 20 Nov 2005 01:14:42 +0000 (GMT) (envelope-from chris@haakonia.hitnet.rwth-aachen.de) Received: from r220-1 (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by ms-dienst.rz.rwth-aachen.de (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0IQ800ADNBGGV9@ms-dienst.rz.rwth-aachen.de> for freebsd-current@freebsd.org; Sun, 20 Nov 2005 02:14:40 +0100 (MET) Received: from relay.rwth-aachen.de ([134.130.3.1]) by r220-1 (MailMonitor for SMTP v1.2.2 ) ; Sun, 20 Nov 2005 02:14:39 +0100 (MET) Received: from bigboss.hitnet.rwth-aachen.de (bigspace.hitnet.RWTH-Aachen.DE [137.226.181.2]) by relay.rwth-aachen.de (8.13.3/8.13.3/1) with ESMTP id jAK1EdFC029655; Sun, 20 Nov 2005 02:14:39 +0100 (MET) Received: from lorien.hitnet.rwth-aachen.de ([137.226.181.92] helo=haakonia.hitnet.rwth-aachen.de) by bigboss.hitnet.rwth-aachen.de with esmtp (Exim 3.35 #1 (Debian)) id 1Eddmx-0007qY-00; Sun, 20 Nov 2005 02:14:39 +0100 Received: by haakonia.hitnet.rwth-aachen.de (Postfix, from userid 1001) id 2734928466; Sun, 20 Nov 2005 02:14:39 +0100 (CET) Date: Sun, 20 Nov 2005 02:14:38 +0100 From: Christian Brueffer In-reply-to: <20051119162011.I88861@carver.gumbysoft.com> To: Doug White Message-id: <20051120011438.GA4194@unixpages.org> MIME-version: 1.0 Content-type: multipart/signed; boundary=FL5UXtIhxfXey3p5; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-disposition: inline User-Agent: Mutt/1.5.9i X-Operating-System: FreeBSD 6.0-STABLE X-PGP-Key: http://people.FreeBSD.org/~brueffer/brueffer.key.asc X-PGP-Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D References: <200511150403.jAF43B6f001417@jerry.xoo.net> <20051119162011.I88861@carver.gumbysoft.com> Cc: Ulf Kieber , freebsd-current@freebsd.org Subject: Re: GEOM error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 01:14:43 -0000 --FL5UXtIhxfXey3p5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 19, 2005 at 04:22:11PM -0800, Doug White wrote: > On Tue, 15 Nov 2005, Ulf Kieber wrote: >=20 > > Re, > > > > on a 6.0-RELEASE I receive the following error since I tried restoring > > a large dump > > > > Nov 14 12:30:11 nexus kernel: g_vfs_done():da1s1d.bde[WRITE(offset=3D72= 350695424, length=3D131072)]error =3D 1 > > > > Besides that, no other errors are logged, especially no SCSI errors. > > The problem persists even after the restore has completed. >=20 > errno 1 is EPERM ("Operation not permitted") and is generally returned if > you attempt to write somewhere you're not allowed to. Considering the > offset is near the end of the disk, GBDE may be trying to prevent you from > overwriting metadata blocks at the end of the partition. How or why > restore(8) would be writing there I'm not sure. >=20 > A SCSI error would return as errno 5 (EIO, "Input/output error"). >=20 I get the same messages with my external USB drive from time to time (interestingly also GBDE encrypted). Nov 20 02:03:30 haakonia kernel: g_vfs_done():da3s2c.bde[WRITE(offset=3D383= 341297664, length=3D65536)]error =3D 1 The message repeats every 30 seconds and trying to unmount the file system fails. When I try to shut the system down, the message appears n > 50 times followed by a panic. Is it possible that the system tries to write on a bad sector and consequently fails (provided that the on-disk sector remapping also fails)? The SMART output of the drive looks ok. - Christian --=20 Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D --FL5UXtIhxfXey3p5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFDf83+bHYXjKDtmC0RAmP1AJ9r7ph1xucs4bCmUeVsy6kV6Wge8ACeM/8V 3oz1SIxHohvJYEn5+NFi6JU= =tmbE -----END PGP SIGNATURE----- --FL5UXtIhxfXey3p5-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 01:35:39 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E4C0B16A41F for ; Sun, 20 Nov 2005 01:35:39 +0000 (GMT) (envelope-from craig@xfoil.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66DB043D70 for ; Sun, 20 Nov 2005 01:35:33 +0000 (GMT) (envelope-from craig@xfoil.gank.org) Received: by ion.gank.org (mail, from userid 1001) id 7111E2BF5B; Sat, 19 Nov 2005 19:35:33 -0600 (CST) Date: Sat, 19 Nov 2005 19:35:30 -0600 From: Craig Boston To: Tillman Hodgson Message-ID: <20051120013530.GA55161@nowhere> Mail-Followup-To: Craig Boston , Tillman Hodgson , FreeBSD -CURRENT References: <20051118213407.GD89507@seekingfire.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051118213407.GD89507@seekingfire.com> User-Agent: Mutt/1.4.2.1i Cc: FreeBSD -CURRENT Subject: Re: Compaq ProLiant 1600 server freezes when detecting keyboard controller X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 01:35:40 -0000 On Fri, Nov 18, 2005 at 03:34:07PM -0600, Tillman Hodgson wrote: > In my case, I have a -current kernel from August 20th 2005 that > continues to boot properly. Subsequent kernels, including both Oct 20 > and Nov 17, fail to boot past the atkbdc point. It's an interesting > freeze in that cntrl-alt-del doesn't perform a reboot. The Aug 20 kernel > lines corresponding to that point look like this: > > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 I've seen this freeze on a couple of 1600s with 6.0-RELEASE. Does this system have multiple processors? If not, try changing the "OS Type" setting in the BIOS to "Other". That fixed it for me. I've had success with using Other for non-SMP kernels, and using the UnixWare 2.1 setting for SMP kernels. I didn't have to use this workaround on 5.4, but I'm not sure when it broke. ProLiants in general seem to be finicky beasts with BSD... I also noticed that 6.0 detects a phantom USB controller and when it attempts to allocate resources to it (and fails), the serial port redirection for the console dies. I can't prove that there isn't hardware on the board somewhere, but these boxes have no USB ports and there's no mention of it in the BIOS. Commenting out uhci from the kernel fixes the serial console. Craig From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 04:18:03 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A9D416A420; Sun, 20 Nov 2005 04:18:03 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E888C43D45; Sun, 20 Nov 2005 04:18:02 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jAK4I19M010936; Sat, 19 Nov 2005 21:18:02 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <437FF8F9.8000207@samsco.org> Date: Sat, 19 Nov 2005 21:18:01 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <20051117010651.97608.qmail@web50303.mail.yahoo.com> <437E6AF7.1040402@samsco.org> <200511190018.jAJ0ItTe013855@apollo.backplane.com> <200511182206.49195.jhb@freebsd.org> In-Reply-To: <200511182206.49195.jhb@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: amd64@freebsd.org, freebsd-current@freebsd.org, Peter Wemm Subject: Re: 7-CURRENT-SNAP009-i386-bootonly.iso on Shuttle XPC w/ AMD X2 (was Re: Side note on Shuttle XPC) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 04:18:03 -0000 John Baldwin wrote: > On Friday 18 November 2005 07:18 pm, Matthew Dillon wrote: > >>:So the amd64 snapshot didn't boot but the i386 one did? Interesting. >>:Thanks a lot for investigating this. >>: >>:Scott >> >> Yup. My guess is that the 64-bit boot issue that early in the boot >> sequence is something stupid simple. It looks it from the consistency >> of the crash. > > > Actually, your comments about the stray ICU interrupts led me to it on the way > home tonight. Peter has a hack in amd64 that if you don't include 'device > atpic' in your kernel config (not in GENERIC amd64 by default in HEAD) he > just masks the PICs. However, he doesn't setup handlers for the spurious > interrupts that can still occur (since they are unmaskable). Couple that > with the fact that HEAD (until a few hours ago) didn't print the trap message > for a T_RESERVED trap, and you'll see that your panic on amd64 was caused by > a spurious ICU interrupt. I have part of peter's hack expanded to do a full > reset of the ICUs, and I'll update it for Monday to adjust the base interrupt > such that the spurious ICU vectors get sent to the APIC spurious interrupt > vector. That should fix your issue as well as the same issue reported by > someone else on the amd64@ list recently. > Does this imply that the 'correct' fix involves catching the stray ICU interrupt via a trap handler? How often do these interrupts happen, and therefore what is the performance consequence to having to handle them? Scott From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 04:25:36 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: by hub.freebsd.org (Postfix, from userid 618) id E72D816A421; Sun, 20 Nov 2005 04:25:36 +0000 (GMT) In-Reply-To: <20051120013530.GA55161@nowhere> from Craig Boston at "Nov 19, 2005 07:35:30 pm" To: craig@xfoil.gank.org (Craig Boston) Date: Sun, 20 Nov 2005 04:25:36 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20051120042536.E72D816A421@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Cc: craig@xfoil.gank.org, current@freebsd.org, tillman@seekingfire.com Subject: Re: Compaq ProLiant 1600 server freezes when detecting keyboard controller X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 04:25:37 -0000 > On Fri, Nov 18, 2005 at 03:34:07PM -0600, Tillman Hodgson wrote: > > In my case, I have a -current kernel from August 20th 2005 that > > continues to boot properly. Subsequent kernels, including both Oct 20 > > and Nov 17, fail to boot past the atkbdc point. It's an interesting > > freeze in that cntrl-alt-del doesn't perform a reboot. The Aug 20 kernel > > lines corresponding to that point look like this: > > > > atkbdc0: at port 0x60,0x64 on isa0 > > atkbd0: irq 1 on atkbdc0 > > I've seen this freeze on a couple of 1600s with 6.0-RELEASE. Does this > system have multiple processors? If not, try changing the "OS Type" > setting in the BIOS to "Other". That fixed it for me. What you can also try, if the BIOS doesn't support this option, is to break to the OK prompt in the boot loader and type: OK set hw.pci.enable_io_modes="0" Use "show hw.pci.enable_io_modes" to verify it's been set correctly. When the kernel wedges here, it's likely because of a bad interaction between the PCI code and the vm86 code. The vm86 code (which lets you run 16 bit BIOS code in an emulated environment using a special feature of the Pentium) uses physical page 0 contain the instructions that run when making a vm86 bios call. What can happen sometimes is that the PCI BIOS leaves one of the PCI devices unconfigured, in which case its base address register is set to 0. Our PCI code then comes along and enables all of the devices but doesn't necessarily update the base address registers on some of them, which has the effect of mapping one of the PCI devices at physical address 0. This problem remains more or less hidden until the keyboard driver code goes to make a vm86 bioscall to access the keyboard. The CPU is switched to vm86 mode and tries to jump to the code at page 0, but code execution doesn't work because a PCI device has been mapped here by mistake. The result is the CPU locks up hard. Setting hw.pci.enable_io_modes to 1 prevents the PCI code from unconditionally enabling I/O mode and memory mapped mode of all devices. > I've had success with using Other for non-SMP kernels, and using the > UnixWare 2.1 setting for SMP kernels. I didn't have to use this > workaround on 5.4, but I'm not sure when it broke. > > ProLiants in general seem to be finicky beasts with BSD... I also > noticed that 6.0 detects a phantom USB controller and when it attempts > to allocate resources to it (and fails), the serial port redirection for > the console dies. I can't prove that there isn't hardware on the board > somewhere, but these boxes have no USB ports and there's no mention of > it in the BIOS. Commenting out uhci from the kernel fixes the serial > console. My celeron machine at work also claims to have a USB controller, but it's not wired up to any connectors on the back panel. I suspect it's part of the motherboard chipset but whoever made the motherboard or assembled the system never wired it up. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 08:06:55 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C4D216A41F; Sun, 20 Nov 2005 08:06:55 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3765F43D49; Sun, 20 Nov 2005 08:06:55 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.13.4/8.13.4) with ESMTP id jAK86USJ026004; Sun, 20 Nov 2005 00:06:30 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.13.4/8.13.4/Submit) id jAK86S22026001; Sun, 20 Nov 2005 00:06:28 -0800 (PST) Date: Sun, 20 Nov 2005 00:06:28 -0800 (PST) From: Matthew Dillon Message-Id: <200511200806.jAK86S22026001@apollo.backplane.com> To: Scott Long References: <20051117010651.97608.qmail@web50303.mail.yahoo.com> <437E6AF7.1040402@samsco.org> <200511190018.jAJ0ItTe013855@apollo.backplane.com> <200511182206.49195.jhb@freebsd.org> <437FF8F9.8000207@samsco.org> Cc: amd64@freebsd.org, freebsd-current@freebsd.org, Peter Wemm Subject: Re: 7-CURRENT-SNAP009-i386-bootonly.iso on Shuttle XPC w/ AMD X2 (was Re: Side note on Shuttle XPC) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 08:06:55 -0000 :... :> a spurious ICU interrupt. I have part of peter's hack expanded to do a full :> reset of the ICUs, and I'll update it for Monday to adjust the base interrupt :> such that the spurious ICU vectors get sent to the APIC spurious interrupt :> vector. That should fix your issue as well as the same issue reported by :> someone else on the amd64@ list recently. :> : :Does this imply that the 'correct' fix involves catching the stray ICU :interrupt via a trap handler? How often do these interrupts happen, :and therefore what is the performance consequence to having to handle :them? : :Scott I think John has the right fix in mind. You have to catch the stray interrupt vector for every interrupt controller in the system. This means the 8259 stray vector AND the LAPIC stray vector, even if one or both devices is completely disabled. Whether this represents a performance problem depends on the situation. If any interrupts are routed through the 8259 at all then the BIOS misprogramming bug I mentioned earlier will result in each real interrupt also causing a stray interrupt (due to the double INT A cycle). Clearly this is not desirable. If the 8259 is 100% disabled I think the duplicate stray interrupts will go away. Even under perfect conditions a stray interrupt can occur during programming or reprogramming of the 8259. This would not cause a performance issue, just result in an occassional stray. For example, if the 8259 issues an IRQ to the cpu and the IRQ source is masked while the cpu is doing an INT A cycle, the 8259 will return the stray interrupt vector. With regards to the LAPICs the story is slightly better. The stray interrupt vector can be programmed into the LAPIC and the interrupt service routine basically doesn't have to do a thing, not even EOI. A stray LAPIC interrupt can occur in a number of situations but I do not believe any of them would result in the same braindamage that you get from broken 8259 routing. One example of stray generation here would be if you changed the TPR while the LAPIC is responding to the cpu's INT A cycle. One thing this does imply is that we should never, ever overlap the 8259 interrupt vector space with the LAPIC vector space. I wonder if the LAPIC EOI lockup issue might be explained by an 8259 returning its stray vector that is misinterpreted as an LAPIC interrupt. Since there is no way to determine what IRQ an LAPIC EOI is actually servicing (except by checking the ISR to see what bit actually got cleared), any sort of misinterpretation will result in disaster. That means I have some work to do in DragonFly which is still using the separate FAST/SLOW vector code with the LAPIC 'SLOW' interrupts overlapping the 8259 vector space. The 8259's stray interrupt vector is BASE+7 (usually 0x20 + 7). I suspect that BASE+15 might also occur sometimes. The only way to completely avoid getting stray 8259 vectors would be to *NEVER* mess with the interrupt masks. I don't think that CLI/STI would work here, the INT A cycle is almost guarenteed to be decoupled from the instruction stream. In fact, at least on the AMD, the hypertransport layer will do the cycle and queue a pending vector until it can be delivered to the cpu (from my read). That is clearly a problem since we pretty much have to mess with the masks to deal with level interrupt sources. Or to disable the 8259 completely, which is the solution John mentioned to me. -Matt Matthew Dillon From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 08:52:15 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47CE116A41F for ; Sun, 20 Nov 2005 08:52:15 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABA0A43D45 for ; Sun, 20 Nov 2005 08:52:12 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by freebsd.czest.pl (8.12.10/8.12.9) with ESMTP id jAK8rXPx084388; Sun, 20 Nov 2005 08:53:33 GMT (envelope-from dunstan@freebsd.czest.pl) Received: (from dunstan@localhost) by freebsd.czest.pl (8.13.4/8.12.9/Submit) id jAK8rXo5084387; Sun, 20 Nov 2005 08:53:33 GMT (envelope-from dunstan) Date: Sun, 20 Nov 2005 08:53:33 +0000 From: "Wojciech A. Koszek" To: Doug White Message-ID: <20051120085333.GB84297@freebsd.czest.pl> References: <20051119170018.GA75757@freebsd.czest.pl> <20051119164627.R88861@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <20051119164627.R88861@carver.gumbysoft.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: Panic after memory dump and machine reboot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 08:52:15 -0000 On Sat, Nov 19, 2005 at 04:47:19PM -0800, Doug White wrote: > On Sat, 19 Nov 2005, Wojciech A. Koszek wrote: > > > Hello, > > > > I noticed very strange problem on -CURRENT. If I get a panic, system writes > > core and reboots. Just after reboot, filesystem check (yes, I sometimes > > forget about sync'ing/mounting in read-only mode) kernel gets another panic, > > which is not (directly?) related with this first one -- problem lies > > somewhere in syscons(4). > > Can you please explain in more detail what you are doing when you say > "filesystem check"? From this, it sounds like you are running fsck while > the FS is mounted, which will cause this behavior. No, I don't check mounted filesystem. I'll try to explain it once again. I mean filesystem checking process, since after kernel panic, filesystem isn't clean. Then, it's being checked with fsck(8). I don't use mount(8), since I have no access to login prompt yet. Kernel panics just after fsck(8) finishes, probably when vidcontrol is executed (see dmesg.txt from link). This situation causes continous panics/filesystem checks, thus making system available to normal use. I have to boot from CD and run fsck(8) on root filesystem. If I succeed in repeating this problem, I'll post additional information. -- * Wojciech A. Koszek && dunstan@FreeBSD.czest.pl From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 09:02:34 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8142E16A41F; Sun, 20 Nov 2005 09:02:34 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2345843D46; Sun, 20 Nov 2005 09:02:34 +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.4/8.13.4) with ESMTP id jAK92WOl094101; Sun, 20 Nov 2005 04:02:32 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.3/8.13.3) with ESMTP id jAK92W51082914; Sun, 20 Nov 2005 04:02:32 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id B41657302F; Sun, 20 Nov 2005 04:02:32 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051120090232.B41657302F@freebsd-current.sentex.ca> Date: Sun, 20 Nov 2005 04:02:32 -0500 (EST) X-Virus-Scanned: ClamAV version 0.86, clamav-milter version 0.86 on clamscanner1 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on alpha/alpha X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Nov 2005 09:02:34 -0000 TB --- 2005-11-20 07:30:48 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-11-20 07:30:48 - starting HEAD tinderbox run for alpha/alpha TB --- 2005-11-20 07:30:48 - cleaning the object tree TB --- 2005-11-20 07:31:48 - checking out the source tree TB --- 2005-11-20 07:31:48 - cd /tinderbox/HEAD/alpha/alpha TB --- 2005-11-20 07:31:48 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-11-20 07:38:15 - building world (CFLAGS=-O2 -pipe) TB --- 2005-11-20 07:38:15 - cd /src TB --- 2005-11-20 07:38:15 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-11-20 08:52:14 - generating LINT kernel config TB --- 2005-11-20 08:52:14 - cd /src/sys/alpha/conf TB --- 2005-11-20 08:52:14 - /usr/bin/make -B LINT TB --- 2005-11-20 08:52:14 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-11-20 08:52:14 - cd /src TB --- 2005-11-20 08:52:14 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Nov 20 08:52:14 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 -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/netinet6/udp6_usrreq.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/netipx/ipx.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/netipx/ipx_cksum.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/netipx/ipx_input.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/netipx/ipx_ip.c /src/sys/netipx/ipx_ip.c: In function `ipxip_input': /src/sys/netipx/ipx_ip.c:198: warning: implicit declaration of function `ip_stripoptions' /src/sys/netipx/ipx_ip.c:198: warning: nested extern declaration of `ip_stripoptions' *** Error code 1 Stop in /obj/alpha/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-20 09:02:32 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-20 09:02:32 - ERROR: failed to build lint kernel TB --- 2005-11-20 09:02:32 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 10:12:33 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2E9416A41F for ; Sun, 20 Nov 2005 10:12:32 +0000 (GMT) (envelope-from schweikh@schweikhardt.net) Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63DB943D45 for ; Sun, 20 Nov 2005 10:12:31 +0000 (GMT) (envelope-from schweikh@schweikhardt.net) Received: by bremen.shuttle.de (Postfix, from userid 10) id 53E9F3B9AA; Sun, 20 Nov 2005 11:12:30 +0100 (CET) Received: from hal9000.schweikhardt.net (localhost [127.0.0.1]) by hal9000.schweikhardt.net (8.13.4/8.13.4) with ESMTP id jAKACBYm002533; Sun, 20 Nov 2005 11:12:11 +0100 (CET) (envelope-from schweikh@hal9000.schweikhardt.net) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.13.4/8.13.4/Submit) id jAKACB6o002532; Sun, 20 Nov 2005 11:12:11 +0100 (CET) (envelope-from schweikh) Date: Sun, 20 Nov 2005 11:12:11 +0100 From: Jens Schweikhardt To: Nicolas Blais Message-ID: <20051120101211.GA746@schweikhardt.net> References: <200511141702.45491.nb_root@videotron.ca> <200511151942.04277.nb_root@videotron.ca> <20051116175853.GA899@schweikhardt.net> <200511190843.03660.nb_root@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200511190843.03660.nb_root@videotron.ca> User-Agent: Mutt/1.5.11 Cc: Steve Hodgson , Maxim.Sobolev@portaone.com, michael johnson , freebsd-current@freebsd.org Subject: Re: Using ccache for build{world, kernel} X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 10:12:33 -0000 On Sat, Nov 19, 2005 at 08:42:57AM -0500, Nicolas Blais wrote: ... # Okay, but is /usr/local/share/doc/ccache/ccache-howto-freebsd.txt still valid? # Such as : # To use ccache add the following to /etc/make.conf # # .if !defined(NOCCACHE) # .if ${.CURDIR:M/usr/src*} # CC=/usr/local/libexec/ccache/cc # CXX=/usr/local/libexec/ccache/c++ IIUC, this works only if CCACHE_PATH is unset. That's hard to guarantee from within a Makefile, hence I use a script for buildworlds. # .else # CC=cc # CXX=c++ Probably nothing wrong with that (unless you expect ccache to be used for non-/usr/src builds). # .endif # .else # CC=/usr/bin/cc # CXX=/usr/bin/c++ This does not look right because it ignores PATH. Someone may want to use /usr/local/bin/cc in the NOCCACHE case. I'd also use CC=cc CXX=C++ here. The author of these instructions may have a reason for it, however, that I have not thought of. # .endif # # I'm asking because I'm slightly confused (sorry) as some people tell me to not # put the block in /etc/make.conf. If I don't put anything, my .ccache folder # remains empty (therefore ccache not being used). Do you use any symlinkery to point to your real /usr/src? What does $ cd /usr/src; echo 'all: ; @echo ${.CURDIR}' | make -f - print? It's "/share/HEAD/src" on my system. Another gotcha and reason not to use the make.conf approach... # Whatever the real usage of ccache, it should be mentionned in that file, or # during 'make install' as a pkg-message. I'm thinking of writing an article about the whole issue, but as I'm in the process of moving I don't expect it to be finished this year. Ccache is not trivial to get to DTRT in each and every conceivable case. So you are entitled to your confusion :-) Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 10:51:00 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D844916A41F; Sun, 20 Nov 2005 10:51:00 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 754B243D46; Sun, 20 Nov 2005 10:51:00 +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.4/8.13.4) with ESMTP id jAKAowLJ099440; Sun, 20 Nov 2005 05:50:58 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.3/8.13.3) with ESMTP id jAKAoxGh009041; Sun, 20 Nov 2005 05:50:59 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 2609D7302F; Sun, 20 Nov 2005 05:50:59 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051120105059.2609D7302F@freebsd-current.sentex.ca> Date: Sun, 20 Nov 2005 05:50:59 -0500 (EST) X-Virus-Scanned: ClamAV version 0.86, clamav-milter version 0.86 on clamscanner1 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Nov 2005 10:51:01 -0000 TB --- 2005-11-20 09:02:32 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-11-20 09:02:32 - starting HEAD tinderbox run for amd64/amd64 TB --- 2005-11-20 09:02:32 - cleaning the object tree TB --- 2005-11-20 09:02:48 - checking out the source tree TB --- 2005-11-20 09:02:48 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2005-11-20 09:02:48 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-11-20 09:09:14 - building world (CFLAGS=-O2 -pipe) TB --- 2005-11-20 09:09:14 - cd /src TB --- 2005-11-20 09:09:14 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries TB --- 2005-11-20 10:39:33 - generating LINT kernel config TB --- 2005-11-20 10:39:33 - cd /src/sys/amd64/conf TB --- 2005-11-20 10:39:33 - /usr/bin/make -B LINT TB --- 2005-11-20 10:39:33 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-11-20 10:39:33 - cd /src TB --- 2005-11-20 10:39:33 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Nov 20 10:39:33 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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/netinet6/udp6_usrreq.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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/netipx/ipx.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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/netipx/ipx_cksum.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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/netipx/ipx_input.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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/netipx/ipx_ip.c /src/sys/netipx/ipx_ip.c: In function `ipxip_input': /src/sys/netipx/ipx_ip.c:198: warning: implicit declaration of function `ip_stripoptions' /src/sys/netipx/ipx_ip.c:198: warning: nested extern declaration of `ip_stripoptions' *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-20 10:50:58 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-20 10:50:58 - ERROR: failed to build lint kernel TB --- 2005-11-20 10:50:58 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 10:52:38 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 82DCD16A41F for ; Sun, 20 Nov 2005 10:52:38 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DFBB43D69 for ; Sun, 20 Nov 2005 10:52:28 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from herring.rabson.org (herring [10.0.0.2]) by itchy.rabson.org (8.13.3/8.13.3) with ESMTP id jAKApiCO038795; Sun, 20 Nov 2005 10:51:44 GMT (envelope-from dfr@nlsystems.com) From: Doug Rabson To: freebsd-current@freebsd.org Date: Sun, 20 Nov 2005 10:51:41 +0000 User-Agent: KMail/1.8.2 References: <4352E841.6000601@psam.se> <4353F3D5.6060309@psam.se> <20051017.130631.73017921.imp@bsdimp.com> In-Reply-To: <20051017.130631.73017921.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_+UFgDoNGes6hnxT" Message-Id: <200511201051.42444.dfr@nlsystems.com> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.6 (itchy.rabson.org [80.177.232.242]); Sun, 20 Nov 2005 10:51:51 +0000 (GMT) X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on itchy.rabson.org X-Virus-Scanned: ClamAV 0.83/1179/Fri Nov 18 17:33:40 2005 on itchy.rabson.org X-Virus-Status: Clean Cc: "M. Warner Losh" , freebsd@psam.se Subject: Re: Thoshiba Tecra 8000 with 3com 3CXFE575CT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 10:52:38 -0000 --Boundary-00=_+UFgDoNGes6hnxT Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Monday 17 October 2005 20:06, M. Warner Losh wrote: > : When I start it outside and then connect the card it will detect > : and configure it correctly. > > OK. This is a HUGE clue. One that shouldn't be overlooked :-). > What it is telling me is that FUNCTION interrupts aren't getting > through, but STATUS interrupts ARE getting through. I'll have to go > re-read my two TOPIC data sheets to make sure, but I think that the > TOPIC chips, especially the older ones, have a number of knobs for > function interrupts that are not in the standard bridge chipset. > > Please refresh my recollection: Did this used to work with 5.4? > IIRC, I did some work to fix o2 micro hangs that disabled the > function interrupts during card insertion by routing them via IRQ 1 > (which the o2micro actually doesn't route, so they just disappear). > Maybe that work around had bad effects for the TOPIC95B that you > have? I get this (xl0 watchdog etc) with my little Sony picturebook, trying to run current. I'm getting around it using polling for now. I've attached a verbose dmesg from 7.0 here. This combination works great with 5.4 but getting a dmesg for that configuration would be a bit trickier. As far as I can see from vmstat, some interrupts are getting through to irq9 but not the ones that were intended for xl0. $ vmstat -i interrupt total rate irq0: clk 1145039 999 irq1: atkbd0 2 0 irq8: rtc 146591 127 irq9: cbb0 fwohci* 194 0 irq13: npx0 1 0 irq14: ata0 3980 3 Total 1295807 1130 --Boundary-00=_+UFgDoNGes6hnxT Content-Type: text/plain; charset="iso-8859-1"; name="dmesg-7.0" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="dmesg-7.0" Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 7.0-CURRENT #0: Sat Nov 19 17:02:31 GMT 2005 dfr@herring.rabson.org:/e/obj/g/dfr/src/sys/VAIO WARNING: WITNESS option enabled, expect reduced performance. Preloaded elf kernel "/boot/kernel/kernel" at 0xc08b8000. Preloaded elf module "/boot/kernel/acpi_sony.ko" at 0xc08b8160. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc08b8210. Calibrating clock(s) ... i8254 clock: 1188408 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 597886417 Hz CPU: Transmeta(tm) Crusoe(tm) Processor TM5600 (597.89-MHz 586-class CPU) Origin = "GenuineTMx86" Id = 0x543 Stepping = 3 Features=0x84803f Processor revision 1.3.1.2 Code Morphing Software revision 4.1.4-7-51 20000805 23:30 official release 4.1.4#2 real memory = 184483840 (175 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009afff, 630784 bytes (154 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000000c28000 - 0x000000000ac9ffff, 168263680 bytes (41080 pages) avail memory = 170852352 (162 MB) bios32: Found BIOS32 Service Directory header at 0xc00f6ab0 bios32: Entry = 0xfd870 (c00fd870) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd870+0x11e pnpbios: Found PnP BIOS data at 0xc00f6ae0 pnpbios: Entry = f0000:a3f8 Rev = 1.0 Other BIOS signatures found: wlan: <802.11 Link Layer> nfslock: pseudo-device null: io: random: mem: npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: [MPSAFE] pci_open(1): mode 1 addr port (0x0cf8) is 0x80003904 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=03951279) pcibios: BIOS version 2.10 Found $PIR table, 9 entries at 0xc00fdf30 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded 0 7 D 0x63 9 embedded 0 13 A 0x60 9 embedded 0 8 A 0x63 9 embedded 0 9 A 0x62 9 embedded 0 10 A 0x60 9 embedded 0 12 A 0x61 9 embedded 0 11 A 0x61 9 embedded 0 14 A 0x61 9 AcpiOsDerivePciId: bus 0 dev 7 func 2 AcpiOsDerivePciId: bus 0 dev 7 func 0 AcpiOsDerivePciId: bus 0 dev 0 func 0 AcpiOsDerivePciId: bus 0 dev 0 func 0 acpi_ec0: port 0x62,0x66 on acpi0 AcpiOsDerivePciId: bus 0 dev 7 func 3 pci_link0: irq 9 on acpi0 pci_link0: Links after initial probe: Index IRQ Rtd Ref IRQs 0 9 N 0 9 pci_link0: Links after initial validation: Index IRQ Rtd Ref IRQs 0 9 N 0 9 pci_link0: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 9 pci_link1: on acpi0 pci_link1: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 9 pci_link1: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 9 pci_link1: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 9 pci_link2: on acpi0 pci_link2: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 9 pci_link2: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 9 pci_link2: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 9 pci_link3: irq 9 on acpi0 pci_link3: Links after initial probe: Index IRQ Rtd Ref IRQs 0 9 N 0 9 pci_link3: Links after initial validation: Index IRQ Rtd Ref IRQs 0 9 N 0 9 pci_link3: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 9 ACPI timer: 0/1252 0/7 0/5 0/6 0/4 0/252 0/5 0/4 0/4 0/4 -> 0 Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x8008-0x800b on acpi0 cpu0: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: physical bus=0 found-> vendor=0x1279, dev=0x0395, revid=0x00 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x2200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 1, range 32, base fc000000, size 20, enabled found-> vendor=0x1279, dev=0x0396, revid=0x00 bus=0, slot=0, func=1 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1279, dev=0x0397, revid=0x00 bus=0, slot=0, func=2 class=05-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x7110, revid=0x02 bus=0, slot=7, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x7111, revid=0x01 bus=0, slot=7, func=1 class=01-01-80, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base 00001000, size 4, enabled found-> vendor=0x8086, dev=0x7112, revid=0x01 bus=0, slot=7, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=9 map[20]: type 4, range 32, base 00001020, size 5, enabled pcib0: matched entry for 0.7.INTD (src \\_SB_.LNKD:0) pcib0: slot 7 INTD routed to irq 9 via \\_SB_.LNKD found-> vendor=0x8086, dev=0x7113, revid=0x03 bus=0, slot=7, func=3 class=06-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0003, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[90]: type 4, range 32, base 00001040, size 4, enabled found-> vendor=0x104c, dev=0x8021, revid=0x02 bus=0, slot=8, func=0 class=0c-00-10, hdrtype=0x00, mfdev=0 cmdreg=0x0010, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x03 (750 ns), maxlat=0x04 (1000 ns) intpin=a, irq=255 powerspec 2 supports D0 D2 D3 current D0 map[10]: type 1, range 32, base fc104000, size 11, memory disabled map[14]: type 1, range 32, base fc100000, size 14, enabled found-> vendor=0x1073, dev=0x0012, revid=0x00 bus=0, slot=9, func=0 class=04-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x05 (1250 ns), maxlat=0x19 (6250 ns) intpin=a, irq=9 powerspec 1 supports D0 D2 D3 current D0 map[10]: type 1, range 32, base fc108000, size 15, enabled map[14]: type 4, range 32, base 00001080, size 6, port disabled map[18]: type 4, range 32, base 00001010, size 2, enabled pcib0: matched entry for 0.9.INTA (src \\_SB_.LNKC:0) pci_link2: Picked IRQ 9 with weight 2 pcib0: slot 9 INTA routed to irq 9 via \\_SB_.LNKC found-> vendor=0x136b, dev=0xff01, revid=0x01 bus=0, slot=11, func=0 class=04-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0010, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x03 (750 ns), maxlat=0x06 (1500 ns) intpin=a, irq=255 powerspec 2 supports D0 D3 current D0 map[10]: type 1, range 32, base fc104800, size 9, memory disabled found-> vendor=0x1180, dev=0x0475, revid=0x80 bus=0, slot=12, func=0 class=06-07-00, hdrtype=0x02, mfdev=0 cmdreg=0x0007, statreg=0x0a10, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x80 (32000 ns), maxlat=0x07 (1750 ns) intpin=a, irq=255 powerspec 1 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base 00000000, size 12, enabled found-> vendor=0x1002, dev=0x4c52, revid=0x64 bus=0, slot=13, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0087, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x42 (1980 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) intpin=a, irq=9 powerspec 1 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base fd000000, size 24, enabled map[14]: type 4, range 32, base 00001400, size 8, enabled map[18]: type 1, range 32, base fc105000, size 12, enabled pcib0: matched entry for 0.13.INTA (src \\_SB_.LNKA:0) pcib0: slot 13 INTA routed to irq 9 via \\_SB_.LNKA pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1000-0x100f at device 7.1 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x1000 ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0xd0 err=0xd0 lsb=0xd0 msb=0xd0 ata0: stat0=0xd0 err=0xd0 lsb=0xd0 msb=0xd0 ata0: stat0=0xd0 err=0xd0 lsb=0xd0 msb=0xd0 ata0: stat0=0xd0 err=0xd0 lsb=0xd0 msb=0xd0 ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ata0: [MPSAFE] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=03 ostat1=03 ata1: stat0=0x01 err=0x01 lsb=0x01 msb=0x01 ata1: stat1=0x04 err=0x04 lsb=0x04 msb=0x04 ata1: stat1=0x02 err=0x02 lsb=0x02 msb=0x02 ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=01 stat1=00 devices=0x0 ata1: [MPSAFE] uhci0: port 0x1020-0x103f irq 9 at device 7.2 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1020 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 pci0: at device 7.3 (no driver attached) fwohci0: mem 0xfc104000-0xfc1047ff,0xfc100000-0xfc103fff at device 8.0 on pci0 fwohci0: Reserved 0x800 bytes for rid 0x10 type 3 at 0xfc104000 pcib0: matched entry for 0.8.INTA (src \\_SB_.LNKD:0) pcib0: slot 8 INTA routed to irq 9 via \\_SB_.LNKD fwohci0: [MPSAFE] fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 08:00:46:03:00:b3:d6:b2 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: 0a:00:46:b3:d6:b2 fwe0: bpf attached fwe0: Ethernet address: 0a:00:46:b3:d6:b2 fwe0: if_start running deferred for Giant fwip0: on firewire0 fwip0: bpf attached fwip0: Firewire address: 08:00:46:03:00:b3:d6:b2 @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=0xc000ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) pci0: at device 9.0 (no driver attached) pci0: at device 11.0 (no driver attached) cbb0: at device 12.0 on pci0 cbb0: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0x80000000 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pcib0: matched entry for 0.12.INTA (src \\_SB_.LNKB:0) pci_link1: Picked IRQ 9 with weight 5 pcib0: slot 12 INTA routed to irq 9 via \\_SB_.LNKB cbb0: [MPSAFE] cbb0: PCI Configuration space: 0x00: 0x04751180 0x0a100007 0x06070080 0x00022000 0x10: 0x80000000 0x020000dc 0x20030200 0xfffff000 0x20: 0x00000000 0xfffff000 0x00000000 0xfffffffc 0x30: 0x00000000 0xfffffffc 0x00000000 0x07000109 0x40: 0x80b1104d 0x00000001 0x00000000 0x00000000 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 0x80: 0x00a20001 0x00000000 0x04630463 0x30000000 0x90: 0x00000000 0x00000000 0x00000000 0x00000000 0xa0: 0x00000000 0x00000000 0x000f0000 0x00000000 0xb0: 0x00000000 0x00000000 0x00000000 0x00000000 0xc0: 0x80b1104d 0x00000000 0x00000000 0x00000000 0xd0: 0x00000000 0x00000000 0x00000000 0xfe190001 0xe0: 0x24c04000 0x00000000 0x00000000 0x00000000 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 pci0: at device 13.0 (no driver attached) acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 atkbd0: [GIANT-LOCKED] psm0: unable to allocate IRQ psmcpnp0: irq 12 on acpi0 psm0: current command byte:0047 psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:00000000, flags:00000008, packet size:3 psm0: syncmask:c0, syncbits:00 acpi_sony0: on acpi0 acpi_sony0: PID 1 battery0: on acpi0 acpi_acad0: on acpi0 pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it atkbdc: atkbdc0 already exists; skipping it sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices pmtimer0 on isa0 orm0: at iomem 0xc0000-0xd3fff,0xdc000-0xdffff pnpid ORM0000 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 pcic0 failed to probe at port 0x3e0 iomem 0xd0000 on isa0 pcic1: not probed (disabled) vt0: not probed (disabled) isa_probe_children: probing PnP devices umass0: Sony USB Memory Stick Slot, rev 1.10/1.31, addr 2 umass0:1:0:-1: Attached to scbus1 Device configuration finished. procfs registered Timecounter "TSC" frequency 597886417 Hz quality 800 Timecounters tick every 1.000 msec lo0: bpf attached battery0: battery initialization startacpi_acad0: acline initialization start battery0: battery initialization done, tried 1 times ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA66 cable=80 wire ad0: setting PIO4 on Intel PIIX4 chip acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times ad0: setting UDMA33 on Intel PIIX4 chip ad0: 11513MB at ata0-master UDMA33 ad0: 23579136 sectors [23392C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad0 cardbus0: Resource not specified in CIS: id=14, size=80 cardbus0: Resource not specified in CIS: id=18, size=80 found-> vendor=0x10b7, dev=0x5157, revid=0x01 bus=2, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0xa8 (5040 ns), mingnt=0x0a (2500 ns), maxlat=0x05 (1250 ns) intpin=a, irq=9 powerspec 1 supports D0 D1 D2 D3 current D0 xl0: <3Com 3c575B Fast Etherlink XL> port 0x1100-0x117f mem 0x88000000-0x8800007f,0x88000080-0x880000ff irq 9 at device 0.0 on cardbus0 xl0: using port I/O xl0: media options word: 40 xl0: found MII/AUTO miibus0: on xl0 tdkphy0: on miibus0 tdkphy0: OUI 0x00c039, model 0x0014, rev. 3 tdkphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: bpf attached xl0: Ethernet address: 00:10:4b:f6:82:84 xl0: [MPSAFE] (probe0:sbp0:0:0:0): error 22 (probe0:sbp0:0:0:0): Unretryable Error (probe3:sbp0:0:3:0): error 22 (probe3:sbp0:0:3:0): Unretryable Error (probe4:sbp0:0:4:0): error 22 (probe4:sbp0:0:4:0): Unretryable Error (probe2:sbp0:0:2:0): error 22 (probe2:sbp0:0:2:0): Unretryable Error (probe5:sbp0:0:5:0): error 22 (probe5:sbp0:0:5:0): Unretryable Error (probe6:sbp0:0:6:0): error 22 (probe6:sbp0:0:6:0): Unretryable Error (probe1:sbp0:0:1:0): error 22 (probe1:sbp0:0:1:0): Unretryable Error pass0 at umass-sim0 bus 0 target 0 lun 0 pass0: Removable Direct Access SCSI-0 device pass0: 1.000MB/s transfers GEOM: new disk da0 (da0:umass-sim0:0:0:0): error 6 (da0:umass-sim0:0:0:0): Unretryable Error da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present Unretryable error (da0:umass-sim0:0:0:0): error 6 (da0:umass-sim0:0:0:0): Unretryable Error Opened disk da0 -> 6 (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present Unretryable error (da0:umass-sim0:0:0:0): error 6 (da0:umass-sim0:0:0:0): Unretryable Error Opened disk da0 -> 6 Trying to mount root from ufs:/dev/ad0s2a start_init: trying /sbin/init acpi_ec0: info: new max delay is 10 us --Boundary-00=_+UFgDoNGes6hnxT-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 12:13:20 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BCBAB16A41F; Sun, 20 Nov 2005 12:13:20 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BD4943D4C; Sun, 20 Nov 2005 12:13:19 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.4/8.13.4) with ESMTP id jAKCDIVW089462; Sun, 20 Nov 2005 07:13:18 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.3/8.13.3) with ESMTP id jAKCDIvT030292; Sun, 20 Nov 2005 07:13:18 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 87AEF7302F; Sun, 20 Nov 2005 07:13:18 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051120121318.87AEF7302F@freebsd-current.sentex.ca> Date: Sun, 20 Nov 2005 07:13:18 -0500 (EST) X-Virus-Scanned: ClamAV version 0.86, clamav-milter version 0.86 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Nov 2005 12:13:20 -0000 TB --- 2005-11-20 10:50:59 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-11-20 10:50:59 - starting HEAD tinderbox run for i386/i386 TB --- 2005-11-20 10:50:59 - cleaning the object tree TB --- 2005-11-20 10:51:13 - checking out the source tree TB --- 2005-11-20 10:51:13 - cd /tinderbox/HEAD/i386/i386 TB --- 2005-11-20 10:51:13 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-11-20 10:57:22 - building world (CFLAGS=-O2 -pipe) TB --- 2005-11-20 10:57:22 - cd /src TB --- 2005-11-20 10:57:22 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-11-20 12:01:51 - generating LINT kernel config TB --- 2005-11-20 12:01:51 - cd /src/sys/i386/conf TB --- 2005-11-20 12:01:51 - /usr/bin/make -B LINT TB --- 2005-11-20 12:01:51 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-11-20 12:01:51 - cd /src TB --- 2005-11-20 12:01:51 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Nov 20 12:01:51 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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/netinet6/udp6_usrreq.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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/netipx/ipx.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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/netipx/ipx_cksum.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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/netipx/ipx_input.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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/netipx/ipx_ip.c /src/sys/netipx/ipx_ip.c: In function `ipxip_input': /src/sys/netipx/ipx_ip.c:198: warning: implicit declaration of function `ip_stripoptions' /src/sys/netipx/ipx_ip.c:198: warning: nested extern declaration of `ip_stripoptions' *** Error code 1 Stop in /obj/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-20 12:13:18 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-20 12:13:18 - ERROR: failed to build lint kernel TB --- 2005-11-20 12:13:18 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 12:54:39 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AAEFF16A41F for ; Sun, 20 Nov 2005 12:54:39 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07BB843D5A for ; Sun, 20 Nov 2005 12:54:38 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1EdoiL-000P88-FC for freebsd-current@freebsd.org; Sun, 20 Nov 2005 14:54:37 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 20 Nov 2005 14:54:37 +0200 From: Danny Braniss Message-ID: Subject: panic: lockmgr: upgrade without shared X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 12:54:39 -0000 im getting this, so i guess i can reproduce it: panic: lockmgr: upgrade without shared cpuid = 0 KDB: enter: panic [thread pid 806 tid 100167 ] Stopped at kdb_enter+0x2b: nop db> tr Tracing pid 806 tid 100167 td 0xc9881000 kdb_enter(c087b148) at kdb_enter+0x2b panic(c0879c7b,c9881000,0,c08ddd00,eb9edc08) at panic+0x127 lockmgr(c9706388,2014,c97063ac,c9881000,eb9edbf8) at lockmgr+0x26b vop_stdlock(eb9edc08,c9706330,c9881000,eb9edc34,c069b937) at vop_stdlock+0x1e VOP_LOCK_APV(c961e240,eb9edc08) at VOP_LOCK_APV+0x43 vput(c9706330,1,c9ac9b00,eb9edc30,1) at vput+0xff NDFREE(eb9edc80,0,c9881000,c9706000,0,8057400) at NDFREE+0x104 __acl_get_file(c9881000,eb9edd04,3,89d,206) at __acl_get_file+0x67 syscall(3b,bfbe003b,eb9e003b,805c03c,8057400) at syscall+0x2bf Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (347, FreeBSD ELF32, __acl_get_file), eip = 0x880f8517, esp = 0xbfbec5bc, ebp = 0xbfbec5d8 --- it's 6.0-STABLE from this morning (it also happens with an older one) newfs -U /dev/ad4s1g mount /dev/ad4s1g /mnt cd /mnt tar cf - -C /dist | tar xpf - (/dist is nfs mounted). and after some time it panics. danny From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 12:59:30 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B49916A41F for ; Sun, 20 Nov 2005 12:59:30 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F20543D45 for ; Sun, 20 Nov 2005 12:59:29 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5DCEA.dip.t-dialin.net [84.165.220.234]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id jAKCYiOD001917; Sun, 20 Nov 2005 13:34:46 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Magellan.Leidinger.net (Magellan.Leidinger.net [192.168.1.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id jAKCxFbc034250; Sun, 20 Nov 2005 13:59:15 +0100 (CET) (envelope-from Alexander@Leidinger.net) Date: Sun, 20 Nov 2005 13:59:14 +0100 From: Alexander Leidinger To: Peter Jeremy Message-ID: <20051120135914.5ac63e2d@Magellan.Leidinger.net> In-Reply-To: <20051119050216.GU39882@cirb503493.alcatel.com.au> References: <20051118114308.GA11281@uk.tiscali.com> <437DCB6D.6090400@centtech.com> <20051118125922.GA11684@uk.tiscali.com> <20051119050216.GU39882@cirb503493.alcatel.com.au> X-Mailer: Sylpheed-Claws 1.9.100 (GTK+ 2.8.6; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new Cc: freebsd-current@freebsd.org, Anderson , Eric, Brian Candler Subject: Re: Logical volume management X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 12:59:30 -0000 On Sat, 19 Nov 2005 16:02:16 +1100 Peter Jeremy wrote: > The other disadvantages I see are: > - All the cylinder groups headers are pre-allocated. AFAIK, UFS2 avoids > pre-allocating the inodes but still reserves the space for them. A > large virtual filesystem will have significant overheads even if it > only has a small amount of real data. > - UFS assumes that all the space is physically available and allocates > blocks so as to (hopefully) maximize performance. This is likely to > lead to significant fragmentation with lots of partially utilised > data chunks. I think those are the reasons why Sun decided to integrate the "new" VM and the new FS code into one black box called ZFS (to prevent someone from using a plain UFS with the new VM and then moan because of the non-optimal performance). Bye, Alexander. -- Speak softly and carry a cellular phone. 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 Sun Nov 20 13:33:36 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1386C16A41F; Sun, 20 Nov 2005 13:33:36 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9F4C43D4C; Sun, 20 Nov 2005 13:33:35 +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.4/8.13.4) with ESMTP id jAKDXXPT006405; Sun, 20 Nov 2005 08:33:33 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.3/8.13.3) with ESMTP id jAKDXYa3055192; Sun, 20 Nov 2005 08:33:34 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 6DA077302F; Sun, 20 Nov 2005 08:33:34 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051120133334.6DA077302F@freebsd-current.sentex.ca> Date: Sun, 20 Nov 2005 08:33:34 -0500 (EST) X-Virus-Scanned: ClamAV version 0.86, clamav-milter version 0.86 on clamscanner1 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on i386/pc98 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Nov 2005 13:33:36 -0000 TB --- 2005-11-20 12:13:18 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-11-20 12:13:18 - starting HEAD tinderbox run for i386/pc98 TB --- 2005-11-20 12:13:18 - cleaning the object tree TB --- 2005-11-20 12:13:35 - checking out the source tree TB --- 2005-11-20 12:13:35 - cd /tinderbox/HEAD/i386/pc98 TB --- 2005-11-20 12:13:35 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-11-20 12:19:45 - building world (CFLAGS=-O2 -pipe) TB --- 2005-11-20 12:19:45 - cd /src TB --- 2005-11-20 12:19:45 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-11-20 13:23:53 - generating LINT kernel config TB --- 2005-11-20 13:23:53 - cd /src/sys/pc98/conf TB --- 2005-11-20 13:23:53 - /usr/bin/make -B LINT TB --- 2005-11-20 13:23:53 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-11-20 13:23:53 - cd /src TB --- 2005-11-20 13:23:53 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Nov 20 13:23:53 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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/netinet6/udp6_usrreq.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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/netipx/ipx.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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/netipx/ipx_cksum.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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/netipx/ipx_input.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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/netipx/ipx_ip.c /src/sys/netipx/ipx_ip.c: In function `ipxip_input': /src/sys/netipx/ipx_ip.c:198: warning: implicit declaration of function `ip_stripoptions' /src/sys/netipx/ipx_ip.c:198: warning: nested extern declaration of `ip_stripoptions' *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-20 13:33:34 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-20 13:33:34 - ERROR: failed to build lint kernel TB --- 2005-11-20 13:33:34 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 14:56:02 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3576D16A41F; Sun, 20 Nov 2005 14:56:02 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42AC243D4C; Sun, 20 Nov 2005 14:56:00 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.4/8.13.4) with ESMTP id jAKEtx3L097461; Sun, 20 Nov 2005 09:55:59 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.3/8.13.3) with ESMTP id jAKEtx2n079265; Sun, 20 Nov 2005 09:55:59 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 809E67302F; Sun, 20 Nov 2005 09:55:59 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051120145559.809E67302F@freebsd-current.sentex.ca> Date: Sun, 20 Nov 2005 09:55:59 -0500 (EST) X-Virus-Scanned: ClamAV version 0.86, clamav-milter version 0.86 on clamscanner1 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Nov 2005 14:56:02 -0000 TB --- 2005-11-20 13:33:34 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-11-20 13:33:34 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2005-11-20 13:33:34 - cleaning the object tree TB --- 2005-11-20 13:33:55 - checking out the source tree TB --- 2005-11-20 13:33:55 - cd /tinderbox/HEAD/sparc64/sparc64 TB --- 2005-11-20 13:33:55 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-11-20 13:40:32 - building world (CFLAGS=-O2 -pipe) TB --- 2005-11-20 13:40:32 - cd /src TB --- 2005-11-20 13:40:32 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-11-20 14:45:31 - generating LINT kernel config TB --- 2005-11-20 14:45:31 - cd /src/sys/sparc64/conf TB --- 2005-11-20 14:45:31 - /usr/bin/make -B LINT TB --- 2005-11-20 14:45:31 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-11-20 14:45:31 - cd /src TB --- 2005-11-20 14:45:31 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Nov 20 14:45:32 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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -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 /src/sys/netinet6/udp6_usrreq.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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -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 /src/sys/netipx/ipx.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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -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 /src/sys/netipx/ipx_cksum.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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -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 /src/sys/netipx/ipx_input.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/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -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 /src/sys/netipx/ipx_ip.c /src/sys/netipx/ipx_ip.c: In function `ipxip_input': /src/sys/netipx/ipx_ip.c:198: warning: implicit declaration of function `ip_stripoptions' /src/sys/netipx/ipx_ip.c:198: warning: nested extern declaration of `ip_stripoptions' *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-20 14:55:59 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-20 14:55:59 - ERROR: failed to build lint kernel TB --- 2005-11-20 14:55:59 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 15:33:02 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2460716A41F; Sun, 20 Nov 2005 15:33:02 +0000 (GMT) (envelope-from tillman@seekingfire.com) Received: from mail.seekingfire.com (caliban.seekingfire.com [24.72.123.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1A8543D45; Sun, 20 Nov 2005 15:33:01 +0000 (GMT) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id 79561288; Sun, 20 Nov 2005 09:32:58 -0600 (CST) Date: Sun, 20 Nov 2005 09:32:58 -0600 From: Tillman Hodgson To: Bill Paul Message-ID: <20051120153258.GA91689@seekingfire.com> References: <20051120013530.GA55161@nowhere> <20051120042536.E72D816A421@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051120042536.E72D816A421@hub.freebsd.org> X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/personal/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers X-Tillman-rules: yes he does User-Agent: Mutt/1.5.11 Cc: Craig Boston , current@freebsd.org Subject: Re: Compaq ProLiant 1600 server freezes when detecting keyboard controller X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 15:33:02 -0000 On Sun, Nov 20, 2005 Craig wrote: > > I've seen this freeze on a couple of 1600s with 6.0-RELEASE. Does this > > system have multiple processors? If not, try changing the "OS Type" > > setting in the BIOS to "Other". That fixed it for me. It is indeed a single processor system. I used the system utilities to change the system type to "Other", with no change in behaviour. I watched the boot closely this time and noticed that it complains about too many IRQ 0s and aborts the keyboard controller. I don't have the exact wording for this -- again, I don't have the serial console set up. I'll try the UnixWare setting next, though it's not an SMP kernel. I had been using the Linux setting, for no particular reason. On Sun, Nov 20, 2005 at 04:25:36AM +0000, Bill Paul wrote: > What you can also try, if the BIOS doesn't support this option, is > to break to the OK prompt in the boot loader and type: > > OK set hw.pci.enable_io_modes="0" I tried this next. With this set, it makes it past the keyboard controller, sc0, sio0, sio1 and vga0. Then the following line appears: RTC BIOS diagnostic error 29 Timecounter lines then appear, then IPsec, ipfe2, the delay for SCSI devices to settle, then: sym0: unable to abort current chip operation. sym0: suspicious SCSI data while resetting the BUS. sym0: dp1, d15-8,dp0,d7-0,rst,req,ack,bsy,sel,atn,msg,c/d,i/o = 0x0, expecting 0x100 sym0: unable to abort current chip operation. sym1: suspicious SCSI data while resetting the BUS. sym1: dp1, d15-8,dp0,d7-0,rst,req,ack,bsy,sel,atn,msg,c/d,i/o = 0x0, expecting 0x100 And there it hangs. The Aug 20 kernel doesn't show any SCSI bus errors. > When the kernel wedges here, it's likely because of a bad interaction > between the PCI code and the vm86 code. The vm86 code (which lets > you run 16 bit BIOS code in an emulated environment using a special > feature of the Pentium) uses physical page 0 contain the instructions > that run when making a vm86 bios call. What can happen sometimes > is that the PCI BIOS leaves one of the PCI devices unconfigured, > in which case its base address register is set to 0. Our PCI code > then comes along and enables all of the devices but doesn't necessarily > update the base address registers on some of them, which has the effect > of mapping one of the PCI devices at physical address 0. > > This problem remains more or less hidden until the keyboard driver > code goes to make a vm86 bioscall to access the keyboard. The CPU > is switched to vm86 mode and tries to jump to the code at page 0, > but code execution doesn't work because a PCI device has been > mapped here by mistake. The result is the CPU locks up hard. > > Setting hw.pci.enable_io_modes to 1 prevents the PCI code from > unconditionally enabling I/O mode and memory mapped mode of all > devices. Oh, interesting background, thanks! -T -- "If 'everybody knows' such-and-such, then it ain't so, by at least ten thousand to one." -- Robert Heinlein From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 16:47:56 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD34616A41F; Sun, 20 Nov 2005 16:47:56 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E21C43D45; Sun, 20 Nov 2005 16:47:53 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jAKGlllG014242; Sun, 20 Nov 2005 09:47:47 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4380A8B2.2090008@samsco.org> Date: Sun, 20 Nov 2005 09:47:46 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthew Dillon References: <20051117010651.97608.qmail@web50303.mail.yahoo.com> <437E6AF7.1040402@samsco.org> <200511190018.jAJ0ItTe013855@apollo.backplane.com> <200511182206.49195.jhb@freebsd.org> <437FF8F9.8000207@samsco.org> <200511200806.jAK86S22026001@apollo.backplane.com> In-Reply-To: <200511200806.jAK86S22026001@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: amd64@freebsd.org, freebsd-current@freebsd.org, Peter Wemm Subject: Re: 7-CURRENT-SNAP009-i386-bootonly.iso on Shuttle XPC w/ AMD X2 (was Re: Side note on Shuttle XPC) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 16:47:56 -0000 Matthew Dillon wrote: > :... > :> a spurious ICU interrupt. I have part of peter's hack expanded to do a full > :> reset of the ICUs, and I'll update it for Monday to adjust the base interrupt > :> such that the spurious ICU vectors get sent to the APIC spurious interrupt > :> vector. That should fix your issue as well as the same issue reported by > :> someone else on the amd64@ list recently. > :> > : > :Does this imply that the 'correct' fix involves catching the stray ICU > :interrupt via a trap handler? How often do these interrupts happen, > :and therefore what is the performance consequence to having to handle > :them? > : > :Scott > > I think John has the right fix in mind. You have to catch the stray > interrupt vector for every interrupt controller in the system. This > means the 8259 stray vector AND the LAPIC stray vector, even if one or > both devices is completely disabled. > > Whether this represents a performance problem depends on the situation. > If any interrupts are routed through the 8259 at all then the BIOS > misprogramming bug I mentioned earlier will result in each real > interrupt also causing a stray interrupt (due to the double INT A cycle). > Clearly this is not desirable. If the 8259 is 100% disabled I think > the duplicate stray interrupts will go away. > > Even under perfect conditions a stray interrupt can occur during > programming or reprogramming of the 8259. This would not cause a > performance issue, just result in an occassional stray. For example, > if the 8259 issues an IRQ to the cpu and the IRQ source is masked > while the cpu is doing an INT A cycle, the 8259 will return the stray > interrupt vector. > > With regards to the LAPICs the story is slightly better. The stray > interrupt vector can be programmed into the LAPIC and the interrupt > service routine basically doesn't have to do a thing, not even EOI. > A stray LAPIC interrupt can occur in a number of situations but I > do not believe any of them would result in the same braindamage that > you get from broken 8259 routing. One example of stray generation here > would be if you changed the TPR while the LAPIC is responding to the > cpu's INT A cycle. > > One thing this does imply is that we should never, ever overlap the > 8259 interrupt vector space with the LAPIC vector space. I wonder if > the LAPIC EOI lockup issue might be explained by an 8259 returning its > stray vector that is misinterpreted as an LAPIC interrupt. Since there > is no way to determine what IRQ an LAPIC EOI is actually servicing > (except by checking the ISR to see what bit actually got cleared), any > sort of misinterpretation will result in disaster. That means I have > some work to do in DragonFly which is still using the separate FAST/SLOW > vector code with the LAPIC 'SLOW' interrupts overlapping the 8259 > vector space. > > The 8259's stray interrupt vector is BASE+7 (usually 0x20 + 7). I > suspect that BASE+15 might also occur sometimes. The only way to > completely avoid getting stray 8259 vectors would be to *NEVER* mess > with the interrupt masks. I don't think that CLI/STI would work here, > the INT A cycle is almost guarenteed to be decoupled from the > instruction stream. In fact, at least on the AMD, the hypertransport > layer will do the cycle and queue a pending vector until it can be > delivered to the cpu (from my read). > > That is clearly a problem since we pretty much have to mess with the > masks to deal with level interrupt sources. Or to disable the 8259 > completely, which is the solution John mentioned to me. > > -Matt > Matthew Dillon > It turns out that the T_RESERVED trap only gets hit once, when the second CPU is being started. Looks like an easy fix. Scott From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 17:26:36 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF1BF16A41F for ; Sun, 20 Nov 2005 17:26:36 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DEE543D46 for ; Sun, 20 Nov 2005 17:26:35 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by freebsd.czest.pl (8.12.10/8.12.9) with ESMTP id jAKHRuPx085663 for ; Sun, 20 Nov 2005 17:27:57 GMT (envelope-from dunstan@freebsd.czest.pl) Received: (from dunstan@localhost) by freebsd.czest.pl (8.13.4/8.12.9/Submit) id jAKHRupd085662 for freebsd-current@freebsd.org; Sun, 20 Nov 2005 17:27:56 GMT (envelope-from dunstan) Date: Sun, 20 Nov 2005 17:27:55 +0000 From: "Wojciech A. Koszek" To: freebsd-current@freebsd.org Message-ID: <20051120172755.GA85641@freebsd.czest.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: [PATCH] Specifying alternative file for devd(8) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 17:26:36 -0000 Hello, I've written patch for devd(8) which makes it possible to specify file other than /etc/devd.conf with "-f ". Patch: http://freebsd.czest.pl/dunstan/FreeBSD/diff.0.devd Comments are welcome! -- * Wojciech A. Koszek && dunstan@FreeBSD.czest.pl From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 17:39:26 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3680816A420 for ; Sun, 20 Nov 2005 17:39:26 +0000 (GMT) (envelope-from rc_lenzi@yahoo.com.br) Received: from web51011.mail.yahoo.com (web51011.mail.yahoo.com [68.142.224.81]) by mx1.FreeBSD.org (Postfix) with SMTP id 553B643D5C for ; Sun, 20 Nov 2005 17:39:21 +0000 (GMT) (envelope-from rc_lenzi@yahoo.com.br) Received: (qmail 21587 invoked by uid 60001); 20 Nov 2005 17:39:20 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.br; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=6oAtI3nJ/UZhSn3QylhlZZutHNDOTNWpPSbHkVkO++vrJqf+7DtTxHLxvqLJNHxcKBxyk50fnzHKd9FGugblEkEOdn+jgSCCHsYjT2gdXmO8diklGeAA5yq7PggilVS2RvPN07N6TADuUyTkly4K7OB7DftgznqaESvFtVS2Dvo= ; Message-ID: <20051120173920.21585.qmail@web51011.mail.yahoo.com> Received: from [201.2.211.19] by web51011.mail.yahoo.com via HTTP; Sun, 20 Nov 2005 17:39:20 GMT Date: Sun, 20 Nov 2005 17:39:20 +0000 (GMT) From: Rafael Caesar Lenzi To: current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0-1503902347-1132508360=:17866" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: PPPoE and SATA problems in 7-CURRENT-SNAP009 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 17:39:26 -0000 --0-1503902347-1132508360=:17866 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Id: Content-Disposition: inline Hi, i installed 7-CURRENT-SNAP009 and few problems happens PPPoE connection crash the system: tun0: bpf attached Kernel Trap 12 With interrupts disabled Fatal Trap 12: page fail while in kernel mode Fatal code: supervisor not read, page not present Current process: 12(swi4:clock SIO) Stopped at: soft clock+x86:cmpl %eax, 0x8(%exa) Problem with my SATA controller, the system works fine, then and random operation, the SATA controller is crash: ata2: reiniting channel .. ata2: SATA connect ready time=0ms ata2: sata_connect devices=0x1 ad4: req=0xc41237d0 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! ad4: req=0xc41237d0 SETFEATURES SET TRANSFER MODE semaphore timeout !! DANGER Will Robinson !! I attached the dmesg log on this email PS: The system bootup only with acpi disabled Thanks, Rafael _______________________________________________________ Yahoo! Acesso Grátis: Internet rápida e grátis. Instale o discador agora! http://br.acesso.yahoo.com/ --0-1503902347-1132508360=:17866-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 17:43:59 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56F4816A41F for ; Sun, 20 Nov 2005 17:43:59 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id A79BD43D45 for ; Sun, 20 Nov 2005 17:43:58 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so471711wxc for ; Sun, 20 Nov 2005 09:43:58 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=dM1dBU/pLq5f3qwD3FWuUDkK5Ho9JxQBWZ6ENo3TInTNM5aqizNVOD9QkNk2aQgE19eVt0mgJY29VxPn3/VkbdJ6pGI2x5HB01Al+KHesmXuqBgwzIFR7K+3FNC/gjrpFn2cMvk2JrnoNHf4U5kNW9gGGPocaLj/vHlUNl1QSo0= Received: by 10.70.29.8 with SMTP id c8mr1356785wxc; Sun, 20 Nov 2005 09:43:58 -0800 (PST) Received: by 10.70.105.13 with HTTP; Sun, 20 Nov 2005 09:43:58 -0800 (PST) Message-ID: <84dead720511200943ua2cf8b8y49bff0dcf3e2fa63@mail.gmail.com> Date: Sun, 20 Nov 2005 23:13:58 +0530 From: Joseph Koshy To: "Wojciech A. Koszek" In-Reply-To: <20051120172755.GA85641@freebsd.czest.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051120172755.GA85641@freebsd.czest.pl> Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Specifying alternative file for devd(8) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 17:43:59 -0000 wk> http://freebsd.czest.pl/dunstan/FreeBSD/diff.0.devd wk> Comments are welcome! Manual page comments: -->><<-- +.It Fl f Ar file +Use file as configuration file instead of /etc/devd.conf (default). "Use configuration file .Ar file instead of the default .Pa /etc/devd.conf ." -->><<-- +(or alternative file specified with +.Fl f +flag) and uses that file to drive the rest of the process. While the +format of this file is described in ".Fl f option" is clearer. Flags usually are booleans. Sentences start on a new line. -->><<-- diff -upr /usr/src/sbin/devd/devd.cc src/sbin/devd/devd.cc --- /usr/src/sbin/devd/devd.cc=09Mon Nov 14 03:01:10 2005 +++ src/sbin/devd/devd.cc=09Sun Nov 20 18:07:08 2005 You should probably also mention in the manual page that only one (the last) '-f' option has an effect. The manual page also needs a .Sh FILES section that lists /etc/devd.conf. Otherwise the patch looks fine. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 18:29:18 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25C7216A41F for ; Sun, 20 Nov 2005 18:29:18 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D84E43D45 for ; Sun, 20 Nov 2005 18:29:17 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by freebsd.czest.pl (8.12.10/8.12.9) with ESMTP id jAKIUcPx085944; Sun, 20 Nov 2005 18:30:38 GMT (envelope-from dunstan@freebsd.czest.pl) Received: (from dunstan@localhost) by freebsd.czest.pl (8.13.4/8.12.9/Submit) id jAKIUcHJ085943; Sun, 20 Nov 2005 18:30:38 GMT (envelope-from dunstan) Date: Sun, 20 Nov 2005 18:30:37 +0000 From: "Wojciech A. Koszek" To: Joseph Koshy Message-ID: <20051120183037.GA85917@freebsd.czest.pl> References: <20051120172755.GA85641@freebsd.czest.pl> <84dead720511200943ua2cf8b8y49bff0dcf3e2fa63@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <84dead720511200943ua2cf8b8y49bff0dcf3e2fa63@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Specifying alternative file for devd(8) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 18:29:18 -0000 On Sun, Nov 20, 2005 at 11:13:58PM +0530, Joseph Koshy wrote: > wk> http://freebsd.czest.pl/dunstan/FreeBSD/diff.0.devd > wk> Comments are welcome! > > Manual page comments: > [..] > You should probably also mention in the manual page that > only one (the last) '-f' option has an effect. Every options has an effect and (somehow) modifies application behavour. I don't see a reason why to mention it, since it's already explained. If you think it's really needed, let me know, I'll make another update. > The manual page also needs a .Sh FILES section that > lists /etc/devd.conf. Thanks! I've fixed it. Updated version: http://freebsd.czest.pl/dunstan/FreeBSD/diff.1.devd Since also /var/run/devd.pipe is mentioned, and syslogd(8) has pipes listed, I've also put it in .Sh FILES. -- * Wojciech A. Koszek && dunstan@FreeBSD.czest.pl From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 18:35:44 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B2C916A41F for ; Sun, 20 Nov 2005 18:35:44 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from indor.net.tomline.ru (indor.net.tomline.ru [213.183.100.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE90543D46 for ; Sun, 20 Nov 2005 18:35:43 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from SNEZHKO by indorsoft.ru (MDaemon.PRO.v7.2.2.R) with ESMTP id md50000031313.msg for ; Mon, 21 Nov 2005 00:35:36 +0600 X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 128057, updated: 17.11.2005] To: Rafael Caesar Lenzi References: <20051120173920.21585.qmail@web51011.mail.yahoo.com> From: Victor Snezhko Date: Mon, 21 Nov 2005 00:35:31 +0600 In-Reply-To: <20051120173920.21585.qmail@web51011.mail.yahoo.com> (Rafael Caesar Lenzi's message of "Sun, 20 Nov 2005 17:39:20 +0000 (GMT)") Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Processed: indor.net.tomline.ru, Mon, 21 Nov 2005 00:35:36 +0600 (not processed: spam filter disabled) X-Return-Path: snezhko@indorsoft.ru X-MDaemon-Deliver-To: current@freebsd.org X-VVS-Spam: false Cc: current@freebsd.org Subject: Re: PPPoE and SATA problems in 7-CURRENT-SNAP009 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 18:35:44 -0000 Rafael Caesar Lenzi writes: > Hi, i installed 7-CURRENT-SNAP009 and few problems happens > > PPPoE connection crash the system: > > tun0: bpf attached > Kernel Trap 12 With interrupts disabled > Fatal Trap 12: page fail while in kernel mode > Fatal code: supervisor not read, page not present > Current process: 12(swi4:clock SIO) > Stopped at: soft clock+x86:cmpl %eax, 0x8(%exa) As my telepathy module says, this is an INET6 problem that was fixed 4 days ago, i.e., after the SNAP009 was generated. You can either cvsup to the fresh -current or disable INET6. -- WBR, Victor V. Snezhko EMail: snezhko@indorsoft.ru From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 18:52:52 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B4DC16A41F for ; Sun, 20 Nov 2005 18:52:52 +0000 (GMT) (envelope-from spil.oss@googlemail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00E5343D45 for ; Sun, 20 Nov 2005 18:52:51 +0000 (GMT) (envelope-from spil.oss@googlemail.com) Received: by xproxy.gmail.com with SMTP id s10so656054wxc for ; Sun, 20 Nov 2005 10:52:51 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=mjNTcPmvqxbO/qmWPWluu0Xi19mbNIo7WriXfbZ9t2H0AtU/vJMRIWs6tdWL8f3wlz6V7qX9tYQJINeCXK0/CLCSGbd/2LAw6ET2uzAy0hDPD+ycJY4gVg25nDhG8QhqI11tR+vZshhYbB8DWyryzkd3/Ad8gShNpy0AtRYqVoQ= Received: by 10.64.251.9 with SMTP id y9mr2001303qbh; Sun, 20 Nov 2005 10:52:51 -0800 (PST) Received: by 10.64.178.9 with HTTP; Sun, 20 Nov 2005 10:52:51 -0800 (PST) Message-ID: <5fbf03c20511201052n566858f7m3498db435b4814ca@mail.gmail.com> Date: Sun, 20 Nov 2005 19:52:51 +0100 From: spil oss To: Doug Rabson In-Reply-To: <200511201051.42444.dfr@nlsystems.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4352E841.6000601@psam.se> <4353F3D5.6060309@psam.se> <20051017.130631.73017921.imp@bsdimp.com> <200511201051.42444.dfr@nlsystems.com> Cc: freebsd-current@freebsd.org, Thierry DELHAISE , "M. Warner Losh" , freebsd@psam.se Subject: Re: Thoshiba Tecra 8000 with 3com 3CXFE575CT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 18:52:52 -0000 Doug, Thanks a lot for the reply. This indeed resolved the watchdog timeouts on my 3c575B. Still would be great if this were fixed for non-polling. Now acpi seems to be misbehaving, a fan that used to stop when the CPU < 62C now continuously runs. Spil. On 11/20/05, Doug Rabson wrote: > On Monday 17 October 2005 20:06, M. Warner Losh wrote: > > : When I start it outside and then connect the card it will detect > > : and configure it correctly. > > > > OK. This is a HUGE clue. One that shouldn't be overlooked :-). > > What it is telling me is that FUNCTION interrupts aren't getting > > through, but STATUS interrupts ARE getting through. I'll have to go > > re-read my two TOPIC data sheets to make sure, but I think that the > > TOPIC chips, especially the older ones, have a number of knobs for > > function interrupts that are not in the standard bridge chipset. > > > > Please refresh my recollection: Did this used to work with 5.4? > > IIRC, I did some work to fix o2 micro hangs that disabled the > > function interrupts during card insertion by routing them via IRQ 1 > > (which the o2micro actually doesn't route, so they just disappear). > > Maybe that work around had bad effects for the TOPIC95B that you > > have? > > I get this (xl0 watchdog etc) with my little Sony picturebook, trying to > run current. I'm getting around it using polling for now. I've attached > a verbose dmesg from 7.0 here. This combination works great with 5.4 > but getting a dmesg for that configuration would be a bit trickier. > > As far as I can see from vmstat, some interrupts are getting through to > irq9 but not the ones that were intended for xl0. > > $ vmstat -i > interrupt total rate > irq0: clk 1145039 999 > irq1: atkbd0 2 0 > irq8: rtc 146591 127 > irq9: cbb0 fwohci* 194 0 > irq13: npx0 1 0 > irq14: ata0 3980 3 > Total 1295807 1130 > > > _______________________________________________ > 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 Nov 20 19:04:05 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8ACE16A426 for ; Sun, 20 Nov 2005 19:04:05 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74FED43D45 for ; Sun, 20 Nov 2005 19:04:05 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01a ([66.130.198.54]) by VL-MO-MR003.ip.videotron.ca (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTP id <0IQ900M0QOYPJP90@VL-MO-MR003.ip.videotron.ca> for freebsd-current@freebsd.org; Sun, 20 Nov 2005 14:04:03 -0500 (EST) Date: Sun, 20 Nov 2005 14:03:46 -0500 From: Nicolas Blais To: freebsd-current@freebsd.org Message-id: <200511201403.58634.nb_root@videotron.ca> MIME-version: 1.0 Content-type: multipart/signed; boundary=nextPart1514323.Xxt62qPHd4; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit User-Agent: KMail/1.8.3 Subject: [patch] remove build dependencies in bsd.ports.mk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 19:04:06 -0000 --nextPart1514323.Xxt62qPHd4 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline This may or may not be useful for the FreeBSD community but.... As I 'ls /var/db/pkg', I noticed a lot of ports I didn't use and that didn'= t=20 have a +REQUIRED_BY file. Ports such as ezm3 and gcc-ooo that I could do=20 without. So, what I did is a simple hack in /usr/ports/Mk/bsd.port.mk so th= at=20 I can run 'make deinstall-builddepends' after a port is installed, and it=20 will ask me to remove any build dependencies. So far it works great, but I couldn't use the 'force (-f)' parameter in the= =20 deinstall target so I made a new target called interactivedeinstall. (I fou= nd=20 out the hard way when I 'deinstall-builddepends' in cvsup and it removed my= =20 xorg-libraries...). One could improve my patch by detecting if the port is already +REQUIRED_BY= =20 another port so it would not ask to delete it.=20 You can get the patch here: http://www.clkroot.net/FreeBSD/update/bsd.port.mk.diff All comments are welcomed, Nicolas. =2D-=20 =46reeBSD 7.0-CURRENT #1: Sat Nov 19 12:36:29 EST 2005 =20 root@clk01a:/usr/obj/usr/src/sys/CLK01A=20 PGP? (updated 16 Nov 05) : http://www.clkroot.net/security/nb_root.asc --nextPart1514323.Xxt62qPHd4 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDgMie4wTBlvcsbJURAomqAJ0aMhGa3wt6Byx9SWCYIqh2E9d+zwCcDRzD muk2VBckqPJ5eY9PA2gBsmg= =ltWy -----END PGP SIGNATURE----- --nextPart1514323.Xxt62qPHd4-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 19:16:44 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF4F716A41F for ; Sun, 20 Nov 2005 19:16:44 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6538043D4C for ; Sun, 20 Nov 2005 19:16:44 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01a ([66.130.198.54]) by VL-MO-MR004.ip.videotron.ca (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTP id <0IQ9001JVPJTPS60@VL-MO-MR004.ip.videotron.ca> for freebsd-current@freebsd.org; Sun, 20 Nov 2005 14:16:43 -0500 (EST) Date: Sun, 20 Nov 2005 14:16:38 -0500 From: Nicolas Blais In-reply-to: <20051120190852.GB2963@soaustin.net> To: Mark Linimon Message-id: <200511201416.39125.nb_root@videotron.ca> MIME-version: 1.0 Content-type: multipart/signed; boundary=nextPart1348166.D7DgsPAtJ7; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit References: <200511201403.58634.nb_root@videotron.ca> <20051120190852.GB2963@soaustin.net> User-Agent: KMail/1.8.3 Cc: freebsd-current@freebsd.org Subject: Re: [patch] remove build dependencies in bsd.ports.mk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 19:16:44 -0000 --nextPart1348166.D7DgsPAtJ7 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On November 20, 2005 02:08 pm, you wrote: > On Sun, Nov 20, 2005 at 02:03:46PM -0500, Nicolas Blais wrote: > > As I 'ls /var/db/pkg', I noticed a lot of ports I didn't use and that > > didn't have a +REQUIRED_BY file. Ports such as ezm3 and gcc-ooo that I > > could do without. So, what I did is a simple hack in > > /usr/ports/Mk/bsd.port.mk so that I can run 'make deinstall-builddepend= s' > > after a port is installed, and it will ask me to remove any build > > dependencies. > > A lot of people use sysutils/pkg_cutleaves, which will interactively walk > through all unused ('leaf') ports. > > mcl Hm, I wasn't aware of that port. Thanks! But isn't that an option that=20 should be offered when building a port?=20 I mean, we can deinstall the port or deinstall all ports dependencies but=20 can't deinstall its build dependencies? =20 Maybe I'm too lazy too... I'll give that port a try. Nicolas. =2D-=20 =46reeBSD 7.0-CURRENT #1: Sat Nov 19 12:36:29 EST 2005 =20 root@clk01a:/usr/obj/usr/src/sys/CLK01A=20 PGP? (updated 16 Nov 05) : http://www.clkroot.net/security/nb_root.asc --nextPart1348166.D7DgsPAtJ7 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDgMuX4wTBlvcsbJURAmYsAKCXPt5pYk5RICjJGMmRnsKK/OwPPgCfQAt/ 0WLcDkK8BhjxKXroH9jWEPk= =qzRo -----END PGP SIGNATURE----- --nextPart1348166.D7DgsPAtJ7-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 19:43:03 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E4E5B16A41F; Sun, 20 Nov 2005 19:43:03 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn.pobox.com (thorn.pobox.com [208.210.124.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E51343D45; Sun, 20 Nov 2005 19:43:03 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn (localhost [127.0.0.1]) by thorn.pobox.com (Postfix) with ESMTP id 5ACF271A; Sun, 20 Nov 2005 14:43:24 -0500 (EST) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thorn.sasl.smtp.pobox.com (Postfix) with ESMTP id 2CBF680B; Sun, 20 Nov 2005 14:29:37 -0500 (EST) Received: from brian by mappit.local.linnet.org with local (Exim 4.54 (FreeBSD)) id 1EdusE-000568-53; Sun, 20 Nov 2005 19:29:14 +0000 Date: Sun, 20 Nov 2005 19:29:14 +0000 From: Brian Candler To: Tim Kientzle Message-ID: <20051120192914.GC19572@uk.tiscali.com> References: <20051116161540.GB4383@uk.tiscali.com> <437F7E22.5050800@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <437F7E22.5050800@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: Order of files with 'cp' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 19:43:04 -0000 On Sat, Nov 19, 2005 at 11:33:54AM -0800, Tim Kientzle wrote: > Brian Candler wrote: > >I've noticed on FreeBSD-5.4 and -6.0 that the order in which 'cp' copies > >multiple files does not match the order they're given on the command line. > ... > >I've had a look through the code, and it seems that cp calls fts_open() > >with > >the list of files in argv; fts_open then does a qsort() on the arguments, > >using the comparison function mastercmp() provided by cp: > > My suggestion: Have 'cp' call fts_open once for each > command-line argument, instead of giving fts_open the entire > argv list to muck with. Erm, but that just undoes the reason for calling fts_open with mastercmp in the first place, which is to get it to pick files before directories (or vice versa, as its behaviour seems to be) as an 'optimisation'. If you are happy to drop that behaviour, then you might as well just call fts_open with NULL as the compare function. In that case it will process each element of argv in sequence anyway. From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 19:08:53 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C8E316A41F for ; Sun, 20 Nov 2005 19:08:53 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5484D43D49 for ; Sun, 20 Nov 2005 19:08:53 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 9CC3930E6; Sun, 20 Nov 2005 13:08:52 -0600 (CST) Date: Sun, 20 Nov 2005 13:08:52 -0600 To: Nicolas Blais Message-ID: <20051120190852.GB2963@soaustin.net> References: <200511201403.58634.nb_root@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200511201403.58634.nb_root@videotron.ca> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) X-Mailman-Approved-At: Sun, 20 Nov 2005 20:05:53 +0000 Cc: freebsd-current@freebsd.org Subject: Re: [patch] remove build dependencies in bsd.ports.mk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 19:08:53 -0000 On Sun, Nov 20, 2005 at 02:03:46PM -0500, Nicolas Blais wrote: > As I 'ls /var/db/pkg', I noticed a lot of ports I didn't use and that didn't > have a +REQUIRED_BY file. Ports such as ezm3 and gcc-ooo that I could do > without. So, what I did is a simple hack in /usr/ports/Mk/bsd.port.mk so that > I can run 'make deinstall-builddepends' after a port is installed, and it > will ask me to remove any build dependencies. A lot of people use sysutils/pkg_cutleaves, which will interactively walk through all unused ('leaf') ports. mcl From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 19:49:09 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A40D16A41F; Sun, 20 Nov 2005 19:49:09 +0000 (GMT) (envelope-from keramida@hellug.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80C9C43D5D; Sun, 20 Nov 2005 19:49:07 +0000 (GMT) (envelope-from keramida@hellug.gr) Received: from flame.pc (patr530b-0118.otenet.gr [62.103.226.118]) (authenticated bits=0) by igloo.linux.gr (8.13.5/8.13.5/Debian-3) with ESMTP id jAKJmev6007741; Sun, 20 Nov 2005 21:48:42 +0200 Received: by flame.pc (Postfix, from userid 1001) id CFC9E11763; Sun, 20 Nov 2005 21:34:16 +0200 (EET) Date: Sun, 20 Nov 2005 21:34:16 +0200 From: Giorgos Keramidas To: Tim Kientzle Message-ID: <20051120193416.GB1599@flame.pc> References: <20051116161540.GB4383@uk.tiscali.com> <437F7E22.5050800@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <437F7E22.5050800@freebsd.org> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-4.399, required 5, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@linux.gr X-Mailman-Approved-At: Sun, 20 Nov 2005 20:06:09 +0000 Cc: freebsd-current@freebsd.org, Brian Candler Subject: Re: Order of files with 'cp' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 19:49:09 -0000 On 2005-11-19 11:33, Tim Kientzle wrote: > Brian Candler wrote: > >I've noticed on FreeBSD-5.4 and -6.0 that the order in which 'cp' > >copies multiple files does not match the order they're given on the > >command line. > ... > >I've had a look through the code, and it seems that cp calls > >fts_open() with the list of files in argv; fts_open then does a > >qsort() on the arguments, using the comparison function mastercmp() > >provided by cp: > > My suggestion: Have 'cp' call fts_open once for each command-line > argument, instead of giving fts_open the entire argv list to muck > with. > > Requires faking up an argv array for each single item, but that will > be a lot easier than trying to fix fts. qsort() can be 'stable' enough for our purposes if the comparison function uses something like this: int compare_int32_t(void *pa, void *pb) { int32_t a, b; assert(pa != NULL && pb != NULL); a = *((int32_t *)pa); b = *((int32_t *)pb); if (a < b && pa != pb) return 1; if (a > b && pa != pb) return -1; return 0; } Perhaps we can use that, instead of calling fts_open() once for each command-line argument? From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 20:27:10 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF5CA16A41F for ; Sun, 20 Nov 2005 20:27:10 +0000 (GMT) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id E45C043D46 for ; Sun, 20 Nov 2005 20:27:09 +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 jAKKR9OZ015779; Sun, 20 Nov 2005 12:27:09 -0800 (PST) (envelope-from kientzle@freebsd.org) Message-ID: <4380DC1A.9030201@freebsd.org> Date: Sun, 20 Nov 2005 12:27:06 -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: Brian Candler References: <20051116161540.GB4383@uk.tiscali.com> <437F7E22.5050800@freebsd.org> <20051120192914.GC19572@uk.tiscali.com> In-Reply-To: <20051120192914.GC19572@uk.tiscali.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Order of files with 'cp' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 20:27:11 -0000 Brian Candler wrote: > On Sat, Nov 19, 2005 at 11:33:54AM -0800, Tim Kientzle wrote: >>Brian Candler wrote: >> >>>I've noticed on FreeBSD-5.4 and -6.0 that the order in which 'cp' copies >>>multiple files does not match the order they're given on the command line. >> >>My suggestion: Have 'cp' call fts_open once for each >>command-line argument, .... > > Erm, but that just undoes the reason for calling fts_open with mastercmp in > the first place, which is to get it to pick files before directories (or > vice versa, as its behaviour seems to be) as an 'optimisation'. Why is that an optimization? I thought the whole point of this thread was that users expect utilities to process the command-line arguments in the order they're given. Tim From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 20:49:45 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAB8A16A41F for ; Sun, 20 Nov 2005 20:49:45 +0000 (GMT) (envelope-from rc_lenzi@yahoo.com.br) Received: from web51009.mail.yahoo.com (web51009.mail.yahoo.com [206.190.39.128]) by mx1.FreeBSD.org (Postfix) with SMTP id 2273243D49 for ; Sun, 20 Nov 2005 20:49:44 +0000 (GMT) (envelope-from rc_lenzi@yahoo.com.br) Received: (qmail 47608 invoked by uid 60001); 20 Nov 2005 20:49:44 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.br; h=Message-ID:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=f2ozv0OmnDXITGi+ikDv7/Cs8C+fMA3uI/ZGGb5TTuRrZcrkelY8T+2OJIoA5hB+zO42Jw17i3WaN/fMIg5ZWKBNSssBk4QIouNgOrMdJgIAGDpADZLSNIzMonhEGVwIxiB+4ZTHDWBZtWFSJ2CrCXLECamNyK402C/JwRCwGoc= ; Message-ID: <20051120204944.47606.qmail@web51009.mail.yahoo.com> Received: from [200.180.69.95] by web51009.mail.yahoo.com via HTTP; Sun, 20 Nov 2005 17:49:44 ART Date: Sun, 20 Nov 2005 17:49:44 -0300 (ART) From: Rafael Caesar Lenzi To: current@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0-1296904255-1132519784=:47599" Content-Transfer-Encoding: 8bit Cc: snezhko@indorsoft.ru Subject: Re: PPPoE and SATA problems in 7-CURRENT-SNAP009 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 20:49:46 -0000 --0-1296904255-1132519784=:47599 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Content-Id: Content-Disposition: inline --- Victor Snezhko escreveu: > As my telepathy module says, this is an INET6 problem that was fixed > 4 days ago, i.e., after the SNAP009 was generated. You can either cvsup > to the fresh -current or disable INET6. Well, i make a cvsup and get fresh copy of -current kernel. The pppoe is more stable, but sometimes is happen. Any suggestion for problem of SATA controller? Thanks, Rafael _______________________________________________________ Yahoo! Acesso Grátis: Internet rápida e grátis. Instale o discador agora! http://br.acesso.yahoo.com/ --0-1296904255-1132519784=:47599 Content-Type: application/octet-stream; name=dmesg Content-Transfer-Encoding: base64 Content-Description: 2758069437-dmesg Content-Disposition: attachment; filename=dmesg cGNpMDogPG1lbW9yeSwgUkFNPiBhdCBkZXZpY2UgMC4yIChubyBkcml2ZXIg YXR0YWNoZWQpCnBjaTA6IDxtZW1vcnksIFJBTT4gYXQgZGV2aWNlIDAuMyAo bm8gZHJpdmVyIGF0dGFjaGVkKQpwY2kwOiA8bWVtb3J5LCBSQU0+IGF0IGRl dmljZSAwLjQgKG5vIGRyaXZlciBhdHRhY2hlZCkKcGNpMDogPG1lbW9yeSwg UkFNPiBhdCBkZXZpY2UgMC41IChubyBkcml2ZXIgYXR0YWNoZWQpCmlzYWIw OiA8UENJLUlTQSBicmlkZ2U+IGF0IGRldmljZSAxLjAgb24gcGNpMAppc2Ew OiA8SVNBIGJ1cz4gb24gaXNhYjAKcGNpMDogPHNlcmlhbCBidXMsIFNNQnVz PiBhdCBkZXZpY2UgMS4xIChubyBkcml2ZXIgYXR0YWNoZWQpCm9oY2kwOiA8 T0hDSSAoZ2VuZXJpYykgVVNCIGNvbnRyb2xsZXI+IG1lbSAweGNlMDg1MDAw LTB4Y2UwODVmZmYgaXJxIDUgYXQgZGV2aWNlIDIuMCBvbiBwY2kwCm9oY2kw OiBSZXNlcnZlZCAweDEwMDAgYnl0ZXMgZm9yIHJpZCAweDEwIHR5cGUgMyBh dCAweGNlMDg1MDAwCm9oY2kwOiBbR0lBTlQtTE9DS0VEXQp1c2IwOiBPSENJ IHZlcnNpb24gMS4wLCBsZWdhY3kgc3VwcG9ydAp1c2IwOiA8T0hDSSAoZ2Vu ZXJpYykgVVNCIGNvbnRyb2xsZXI+IG9uIG9oY2kwCnVzYjA6IFVTQiByZXZp c2lvbiAxLjAKdWh1YjA6IG5WaWRpYSBPSENJIHJvb3QgaHViLCBjbGFzcyA5 LzAsIHJldiAxLjAwLzEuMDAsIGFkZHIgMQp1aHViMDogMyBwb3J0cyB3aXRo IDMgcmVtb3ZhYmxlLCBzZWxmIHBvd2VyZWQKb2hjaTE6IDxPSENJIChnZW5l cmljKSBVU0IgY29udHJvbGxlcj4gbWVtIDB4Y2UwODIwMDAtMHhjZTA4MmZm ZiBpcnEgMTIgYXQgZGV2aWNlIDIuMSBvbiBwY2kwCm9oY2kxOiBSZXNlcnZl ZCAweDEwMDAgYnl0ZXMgZm9yIHJpZCAweDEwIHR5cGUgMyBhdCAweGNlMDgy MDAwCm9oY2kxOiBbR0lBTlQtTE9DS0VEXQp1c2IxOiBPSENJIHZlcnNpb24g MS4wLCBsZWdhY3kgc3VwcG9ydAp1c2IxOiA8T0hDSSAoZ2VuZXJpYykgVVNC IGNvbnRyb2xsZXI+IG9uIG9oY2kxCnVzYjE6IFVTQiByZXZpc2lvbiAxLjAK dWh1YjE6IG5WaWRpYSBPSENJIHJvb3QgaHViLCBjbGFzcyA5LzAsIHJldiAx LjAwLzEuMDAsIGFkZHIgMQp1aHViMTogMyBwb3J0cyB3aXRoIDMgcmVtb3Zh YmxlLCBzZWxmIHBvd2VyZWQKZWhjaTA6IDxOVklESUEgbkZvcmNlMiBVU0Ig Mi4wIGNvbnRyb2xsZXI+IG1lbSAweGNlMDgzMDAwLTB4Y2UwODMwZmYgaXJx IDExIGF0IGRldmljZSAyLjIgb24gcGNpMAplaGNpMDogUmVzZXJ2ZWQgMHgx MDAgYnl0ZXMgZm9yIHJpZCAweDEwIHR5cGUgMyBhdCAweGNlMDgzMDAwCmVo Y2kwOiBbR0lBTlQtTE9DS0VEXQp1c2IyOiBFSENJIHZlcnNpb24gMS4wCnVz YjI6IGNvbXBhbmlvbiBjb250cm9sbGVycywgNCBwb3J0cyBlYWNoOiB1c2Iw IHVzYjEKdXNiMjogPE5WSURJQSBuRm9yY2UyIFVTQiAyLjAgY29udHJvbGxl cj4gb24gZWhjaTAKdXNiMjogVVNCIHJldmlzaW9uIDIuMAp1aHViMjogblZp ZGlhIEVIQ0kgcm9vdCBodWIsIGNsYXNzIDkvMCwgcmV2IDIuMDAvMS4wMCwg YWRkciAxCnVodWIyOiA2IHBvcnRzIHdpdGggNiByZW1vdmFibGUsIHNlbGYg cG93ZXJlZApwY2kwOiA8bmV0d29yaywgZXRoZXJuZXQ+IGF0IGRldmljZSA0 LjAgKG5vIGRyaXZlciBhdHRhY2hlZCkKcGNpMDogPG11bHRpbWVkaWEsIGF1 ZGlvPiBhdCBkZXZpY2UgNS4wIChubyBkcml2ZXIgYXR0YWNoZWQpCnBjaTA6 IDxtdWx0aW1lZGlhLCBhdWRpbz4gYXQgZGV2aWNlIDYuMCAobm8gZHJpdmVy IGF0dGFjaGVkKQpwY2liMTogPFBDSUJJT1MgUENJLVBDSSBicmlkZ2U+IGF0 IGRldmljZSA4LjAgb24gcGNpMApwY2liMTogICBzZWNvbmRhcnkgYnVzICAg ICAxCnBjaWIxOiAgIHN1Ym9yZGluYXRlIGJ1cyAgIDEKcGNpYjE6ICAgSS9P IGRlY29kZSAgICAgICAgMHhhMDAwLTB4YmZmZgpwY2liMTogICBtZW1vcnkg ZGVjb2RlICAgICAweGNjMDAwMDAwLTB4Y2RmZmZmZmYKcGNpYjE6ICAgcHJl ZmV0Y2hlZCBkZWNvZGUgMHhmZmYwMDAwMC0weGZmZmZmCnBjaTE6IDxQQ0kg YnVzPiBvbiBwY2liMQpwY2kxOiBwaHlzaWNhbCBidXM9MQpmb3VuZC0+CXZl bmRvcj0weDEwOTUsIGRldj0weDMxMTIsIHJldmlkPTB4MDEKCWJ1cz0xLCBz bG90PTExLCBmdW5jPTAKCWNsYXNzPTAxLTA0LTAwLCBoZHJ0eXBlPTB4MDAs IG1mZGV2PTAKCWNtZHJlZz0weDAwMDcsIHN0YXRyZWc9MHgwMmIwLCBjYWNo ZWxuc3o9OCAoZHdvcmRzKQoJbGF0dGltZXI9MHgyMCAoOTYwIG5zKSwgbWlu Z250PTB4MDAgKDAgbnMpLCBtYXhsYXQ9MHgwMCAoMCBucykKCWludHBpbj1h LCBpcnE9MTEKCXBvd2Vyc3BlYyAyICBzdXBwb3J0cyBEMCBEMSBEMiBEMyAg Y3VycmVudCBEMAoJbWFwWzEwXTogdHlwZSA0LCByYW5nZSAzMiwgYmFzZSAw MDAwYTAwMCwgc2l6ZSAgMywgZW5hYmxlZApwY2liMTogKG51bGwpIHJlcXVl c3RlZCBJL08gcmFuZ2UgMHhhMDAwLTB4YTAwNzogaW4gcmFuZ2UKCW1hcFsx NF06IHR5cGUgNCwgcmFuZ2UgMzIsIGJhc2UgMDAwMGE0MDAsIHNpemUgIDIs IGVuYWJsZWQKcGNpYjE6IChudWxsKSByZXF1ZXN0ZWQgSS9PIHJhbmdlIDB4 YTQwMC0weGE0MDM6IGluIHJhbmdlCgltYXBbMThdOiB0eXBlIDQsIHJhbmdl IDMyLCBiYXNlIDAwMDBhODAwLCBzaXplICAzLCBlbmFibGVkCnBjaWIxOiAo bnVsbCkgcmVxdWVzdGVkIEkvTyByYW5nZSAweGE4MDAtMHhhODA3OiBpbiBy YW5nZQoJbWFwWzFjXTogdHlwZSA0LCByYW5nZSAzMiwgYmFzZSAwMDAwYWMw MCwgc2l6ZSAgMiwgZW5hYmxlZApwY2liMTogKG51bGwpIHJlcXVlc3RlZCBJ L08gcmFuZ2UgMHhhYzAwLTB4YWMwMzogaW4gcmFuZ2UKCW1hcFsyMF06IHR5 cGUgNCwgcmFuZ2UgMzIsIGJhc2UgMDAwMGIwMDAsIHNpemUgIDQsIGVuYWJs ZWQKcGNpYjE6IChudWxsKSByZXF1ZXN0ZWQgSS9PIHJhbmdlIDB4YjAwMC0w eGIwMGY6IGluIHJhbmdlCgltYXBbMjRdOiB0eXBlIDEsIHJhbmdlIDMyLCBi YXNlIGNkMDAwMDAwLCBzaXplICA5LCBlbmFibGVkCnBjaWIxOiAobnVsbCkg cmVxdWVzdGVkIG1lbW9yeSByYW5nZSAweGNkMDAwMDAwLTB4Y2QwMDAxZmY6 IGdvb2QKJFBJUjogMToxMSBJTlRBIHJvdXRlZCB0byBpcnEgMTEKYXRhcGNp MDogPFNpSSAzMTEyIFNBVEExNTAgY29udHJvbGxlcj4gcG9ydCAweGEwMDAt MHhhMDA3LDB4YTQwMC0weGE0MDMsMHhhODAwLTB4YTgwNywweGFjMDAtMHhh YzAzLDB4YjAwMC0weGIwMGYgbWVtIDB4Y2QwMDAwMDAtMHhjZDAwMDFmZiBp cnEgMTEgYXQgZGV2aWNlIDExLjAgb24gcGNpMQphdGFwY2kwOiBSZXNlcnZl ZCAweDEwIGJ5dGVzIGZvciByaWQgMHgyMCB0eXBlIDQgYXQgMHhiMDAwCmF0 YXBjaTA6IFtNUFNBRkVdCmF0YXBjaTA6IFJlc2VydmVkIDB4MjAwIGJ5dGVz IGZvciByaWQgMHgyNCB0eXBlIDMgYXQgMHhjZDAwMDAwMAphdGEyOiA8QVRB IGNoYW5uZWwgMD4gb24gYXRhcGNpMAphdGEyOiBTQVRBIGNvbm5lY3QgcmVh ZHkgdGltZT0wbXMKYXRhMjogc2F0YV9jb25uZWN0IGRldmljZXM9MHgxPEFU QV9NQVNURVI+CmF0YTI6IFtNUFNBRkVdCmF0YTM6IDxBVEEgY2hhbm5lbCAx PiBvbiBhdGFwY2kwCmF0YTM6IFNBVEEgY29ubmVjdCBzdGF0dXM9MDAwMDAw MDAKYXRhMzogW01QU0FGRV0KYXRhcGNpMTogPG5WaWRpYSBuRm9yY2UyIFVE TUExMzMgY29udHJvbGxlcj4gcG9ydCAweDFmMC0weDFmNywweDNmNiwweDE3 MC0weDE3NywweDM3NiwweGYwMDAtMHhmMDBmIGF0IGRldmljZSA5LjAgb24g cGNpMAphdGFwY2kxOiBSZXNlcnZlZCAweDEwIGJ5dGVzIGZvciByaWQgMHgy MCB0eXBlIDQgYXQgMHhmMDAwCmF0YTA6IDxBVEEgY2hhbm5lbCAwPiBvbiBh dGFwY2kxCmF0YXBjaTE6IFJlc2VydmVkIDB4OCBieXRlcyBmb3IgcmlkIDB4 MTAgdHlwZSA0IGF0IDB4MWYwCmF0YXBjaTE6IFJlc2VydmVkIDB4MSBieXRl cyBmb3IgcmlkIDB4MTQgdHlwZSA0IGF0IDB4M2Y2CmF0YTA6IHJlc2V0IHRw MSBtYXNrPTAzIG9zdGF0MD01MCBvc3RhdDE9MDAKYXRhMDogc3RhdDA9MHg1 MCBlcnI9MHgwMSBsc2I9MHgwMCBtc2I9MHgwMAphdGEwOiBzdGF0MT0weDAw IGVycj0weDAxIGxzYj0weDAwIG1zYj0weDAwCmF0YTA6IHJlc2V0IHRwMiBz dGF0MD01MCBzdGF0MT0wMCBkZXZpY2VzPTB4MTxBVEFfTUFTVEVSPgphdGEw OiBbTVBTQUZFXQphdGExOiA8QVRBIGNoYW5uZWwgMT4gb24gYXRhcGNpMQph dGFwY2kxOiBSZXNlcnZlZCAweDggYnl0ZXMgZm9yIHJpZCAweDE4IHR5cGUg NCBhdCAweDE3MAphdGFwY2kxOiBSZXNlcnZlZCAweDEgYnl0ZXMgZm9yIHJp ZCAweDFjIHR5cGUgNCBhdCAweDM3NgphdGExOiByZXNldCB0cDEgbWFzaz0w MyBvc3RhdDA9NTAgb3N0YXQxPTUwCmF0YTE6IHN0YXQwPTB4MDAgZXJyPTB4 MDEgbHNiPTB4MTQgbXNiPTB4ZWIKYXRhMTogc3RhdDE9MHgwMCBlcnI9MHgw MSBsc2I9MHgxNCBtc2I9MHhlYgphdGExOiByZXNldCB0cDIgc3RhdDA9MDAg c3RhdDE9MDAgZGV2aWNlcz0weGM8QVRBUElfU0xBVkUsQVRBUElfTUFTVEVS PgphdGExOiBbTVBTQUZFXQpwY2liMjogPFBDSUJJT1MgUENJLVBDSSBicmlk Z2U+IGF0IGRldmljZSAxMi4wIG9uIHBjaTAKcGNpYjI6ICAgc2Vjb25kYXJ5 IGJ1cyAgICAgMgpwY2liMjogICBzdWJvcmRpbmF0ZSBidXMgICAyCnBjaWIy OiAgIEkvTyBkZWNvZGUgICAgICAgIDB4YzAwMC0weGNmZmYKcGNpYjI6ICAg bWVtb3J5IGRlY29kZSAgICAgMHhjODAwMDAwMC0weGM5ZmZmZmZmCnBjaWIy OiAgIHByZWZldGNoZWQgZGVjb2RlIDB4ZmZmMDAwMDAtMHhmZmZmZgpwY2ky OiA8UENJIGJ1cz4gb24gcGNpYjIKcGNpMjogcGh5c2ljYWwgYnVzPTIKZm91 bmQtPgl2ZW5kb3I9MHgxMGI3LCBkZXY9MHg5MjAxLCByZXZpZD0weDQwCgli dXM9Miwgc2xvdD0xLCBmdW5jPTAKCWNsYXNzPTAyLTAwLTAwLCBoZHJ0eXBl PTB4MDAsIG1mZGV2PTAKCWNtZHJlZz0weDAwMDcsIHN0YXRyZWc9MHgwMjEw LCBjYWNoZWxuc3o9OCAoZHdvcmRzKQoJbGF0dGltZXI9MHgyMCAoOTYwIG5z KSwgbWluZ250PTB4MGEgKDI1MDAgbnMpLCBtYXhsYXQ9MHgwYSAoMjUwMCBu cykKCWludHBpbj1hLCBpcnE9NQoJcG93ZXJzcGVjIDIgIHN1cHBvcnRzIEQw IEQxIEQyIEQzICBjdXJyZW50IEQwCgltYXBbMTBdOiB0eXBlIDQsIHJhbmdl IDMyLCBiYXNlIDAwMDBjMDAwLCBzaXplICA3LCBlbmFibGVkCnBjaWIyOiAo bnVsbCkgcmVxdWVzdGVkIEkvTyByYW5nZSAweGMwMDAtMHhjMDdmOiBpbiBy YW5nZQoJbWFwWzE0XTogdHlwZSAxLCByYW5nZSAzMiwgYmFzZSBjOTAwMDAw MCwgc2l6ZSAgNywgZW5hYmxlZApwY2liMjogKG51bGwpIHJlcXVlc3RlZCBt ZW1vcnkgcmFuZ2UgMHhjOTAwMDAwMC0weGM5MDAwMDdmOiBnb29kCiRQSVI6 IDI6MSBJTlRBIHJvdXRlZCB0byBpcnEgNQpwY2kyOiA8bmV0d29yaywgZXRo ZXJuZXQ+IGF0IGRldmljZSAxLjAgKG5vIGRyaXZlciBhdHRhY2hlZCkKcGNp YjM6IDxQQ0ktUENJIGJyaWRnZT4gYXQgZGV2aWNlIDMwLjAgb24gcGNpMApw Y2liMzogICBzZWNvbmRhcnkgYnVzICAgICAzCnBjaWIzOiAgIHN1Ym9yZGlu YXRlIGJ1cyAgIDMKcGNpYjM6ICAgSS9PIGRlY29kZSAgICAgICAgMHhmMDAw LTB4ZmZmCnBjaWIzOiAgIG1lbW9yeSBkZWNvZGUgICAgIDB4Y2EwMDAwMDAt MHhjYmZmZmZmZgpwY2liMzogICBwcmVmZXRjaGVkIGRlY29kZSAweGMwMDAw MDAwLTB4YzdmZmZmZmYKcGNpMzogPFBDSSBidXM+IG9uIHBjaWIzCnBjaTM6 IHBoeXNpY2FsIGJ1cz0zCmZvdW5kLT4JdmVuZG9yPTB4MTBkZSwgZGV2PTB4 MDExMCwgcmV2aWQ9MHhiMgoJYnVzPTMsIHNsb3Q9MCwgZnVuYz0wCgljbGFz cz0wMy0wMC0wMCwgaGRydHlwZT0weDAwLCBtZmRldj0wCgljbWRyZWc9MHgw MDA3LCBzdGF0cmVnPTB4MDJiMCwgY2FjaGVsbnN6PTAgKGR3b3JkcykKCWxh dHRpbWVyPTB4MjAgKDk2MCBucyksIG1pbmdudD0weDA1ICgxMjUwIG5zKSwg bWF4bGF0PTB4MDEgKDI1MCBucykKCWludHBpbj1hLCBpcnE9MTEKCXBvd2Vy c3BlYyAyICBzdXBwb3J0cyBEMCBEMyAgY3VycmVudCBEMAoJbWFwWzEwXTog dHlwZSAxLCByYW5nZSAzMiwgYmFzZSBjYTAwMDAwMCwgc2l6ZSAyNCwgZW5h YmxlZApwY2liMzogKG51bGwpIHJlcXVlc3RlZCBtZW1vcnkgcmFuZ2UgMHhj YTAwMDAwMC0weGNhZmZmZmZmOiBnb29kCgltYXBbMTRdOiB0eXBlIDMsIHJh bmdlIDMyLCBiYXNlIGMwMDAwMDAwLCBzaXplIDI3LCBlbmFibGVkCnBjaWIz OiAobnVsbCkgcmVxdWVzdGVkIG1lbW9yeSByYW5nZSAweGMwMDAwMDAwLTB4 YzdmZmZmZmY6IGdvb2QKJFBJUjogRm91bmQgSVJRIDEyIGZvciBsaW5rIDB4 NCBmcm9tIDUgMTEgMTIKJFBJUjogUk9VVEVfSU5URVJSVVBUIGZhaWxlZC4K cGNpMzogPGRpc3BsYXksIFZHQT4gYXQgZGV2aWNlIDAuMCAobm8gZHJpdmVy IGF0dGFjaGVkKQpleF9pc2FfaWRlbnRpZnkoKQphdGE6IGF0YTAgYWxyZWFk eSBleGlzdHM7IHNraXBwaW5nIGl0CmF0YTogYXRhMSBhbHJlYWR5IGV4aXN0 czsgc2tpcHBpbmcgaXQKcG5wYmlvczogMTYgZGV2aWNlcywgbGFyZ2VzdCA5 OCBieXRlcwpQTlAwMjAwOiBhZGRpbmcgZG1hIG1hc2sgMHgxMApQTlAwMjAw OiBhZGRpbmcgaW8gcmFuZ2UgMC0weGYsIHNpemU9MHgxMCwgYWxpZ249MApQ TlAwMjAwOiBhZGRpbmcgaW8gcmFuZ2UgMHg4MS0weDgzLCBzaXplPTB4Mywg YWxpZ249MApQTlAwMjAwOiBhZGRpbmcgaW8gcmFuZ2UgMHg4Ny0weDg3LCBz aXplPTB4MSwgYWxpZ249MApQTlAwMjAwOiBhZGRpbmcgaW8gcmFuZ2UgMHg4 OS0weDhiLCBzaXplPTB4MywgYWxpZ249MApQTlAwMjAwOiBhZGRpbmcgaW8g cmFuZ2UgMHg4Zi0weDkxLCBzaXplPTB4MywgYWxpZ249MApQTlAwMjAwOiBh ZGRpbmcgaW8gcmFuZ2UgMHhjMC0weGRmLCBzaXplPTB4MjAsIGFsaWduPTAK cG5wYmlvczogaGFuZGxlIDEgZGV2aWNlIElEIFBOUDAyMDAgKDAwMDJkMDQx KQpQTlAwMTAwOiBhZGRpbmcgaXJxIG1hc2sgMHgxClBOUDAxMDA6IGFkZGlu ZyBpbyByYW5nZSAweDQwLTB4NDMsIHNpemU9MHg0LCBhbGlnbj0wCnBucGJp b3M6IGhhbmRsZSAyIGRldmljZSBJRCBQTlAwMTAwICgwMDAxZDA0MSkKUE5Q MGIwMDogYWRkaW5nIGlycSBtYXNrIDB4MTAwClBOUDBiMDA6IGFkZGluZyBp byByYW5nZSAweDcwLTB4NzEsIHNpemU9MHgyLCBhbGlnbj0wCnBucGJpb3M6 IGhhbmRsZSAzIGRldmljZSBJRCBQTlAwYjAwICgwMDBiZDA0MSkKUE5QMDMw MzogYWRkaW5nIGlycSBtYXNrIDB4MgpQTlAwMzAzOiBhZGRpbmcgaW8gcmFu Z2UgMHg2MC0weDYwLCBzaXplPTB4MSwgYWxpZ249MApQTlAwMzAzOiBhZGRp bmcgaW8gcmFuZ2UgMHg2NC0weDY0LCBzaXplPTB4MSwgYWxpZ249MApwbnBi aW9zOiBoYW5kbGUgNCBkZXZpY2UgSUQgUE5QMDMwMyAoMDMwM2QwNDEpClBO UDA4MDA6IGFkZGluZyBpbyByYW5nZSAweDYxLTB4NjEsIHNpemU9MHgxLCBh bGlnbj0wCnBucGJpb3M6IGhhbmRsZSA1IGRldmljZSBJRCBQTlAwODAwICgw MDA4ZDA0MSkKUE5QMGMwNDogYWRkaW5nIGlycSBtYXNrIDB4MjAwMApQTlAw YzA0OiBhZGRpbmcgaW8gcmFuZ2UgMHhmMC0weGZmLCBzaXplPTB4MTAsIGFs aWduPTAKcG5wYmlvczogaGFuZGxlIDYgZGV2aWNlIElEIFBOUDBjMDQgKDA0 MGNkMDQxKQpQTlAwYzAxOiBhZGRpbmcgZml4ZWQgbWVtb3J5MzIgcmFuZ2Ug MC0weDlmZmZmLCBzaXplPTB4YTAwMDAKUE5QMGMwMTogYWRkaW5nIGZpeGVk IG1lbW9yeTMyIHJhbmdlIDB4ZmZmZTAwMDAtMHhmZmZmZmZmZiwgc2l6ZT0w eDIwMDAwClBOUDBjMDE6IGFkZGluZyBmaXhlZCBtZW1vcnkzMiByYW5nZSAw eGZlYzAwMDAwLTB4ZmVjMGZmZmYsIHNpemU9MHgxMDAwMApQTlAwYzAxOiBh ZGRpbmcgZml4ZWQgbWVtb3J5MzIgcmFuZ2UgMHhmZWUwMDAwMC0weGZlZTBm ZmZmLCBzaXplPTB4MTAwMDAKUE5QMGMwMTogYWRkaW5nIGZpeGVkIG1lbW9y eTMyIHJhbmdlIDB4MTAwMDAwLTB4ZmZmZmZmLCBzaXplPTB4ZjAwMDAwCnBu cGJpb3M6IGhhbmRsZSA3IGRldmljZSBJRCBQTlAwYzAxICgwMTBjZDA0MSkK UE5QMGMwMjogYWRkaW5nIGZpeGVkIG1lbW9yeTMyIHJhbmdlIDB4ZjAwMDAt MHhmM2ZmZiwgc2l6ZT0weDQwMDAKUE5QMGMwMjogYWRkaW5nIGZpeGVkIG1l bW9yeTMyIHJhbmdlIDB4ZjQwMDAtMHhmN2ZmZiwgc2l6ZT0weDQwMDAKUE5Q MGMwMjogYWRkaW5nIGZpeGVkIG1lbW9yeTMyIHJhbmdlIDB4ZjgwMDAtMHhm ZmZmZiwgc2l6ZT0weDgwMDAKUE5QMGMwMjogYWRkaW5nIGZpeGVkIG1lbW9y eTMyIHJhbmdlIDB4ZDc4MDAtMHhkN2ZmZiwgc2l6ZT0weDgwMApwbnBiaW9z OiBoYW5kbGUgOCBkZXZpY2UgSUQgUE5QMGMwMiAoMDIwY2QwNDEpClBOUDBh MDM6IGFkZGluZyBpbyByYW5nZSAweDRkMC0weDRkMSwgc2l6ZT0weDIsIGFs aWduPTAKUE5QMGEwMzogYWRkaW5nIGlvIHJhbmdlIDB4Y2Y4LTB4Y2ZmLCBz aXplPTB4OCwgYWxpZ249MApwbnBiaW9zOiBoYW5kbGUgOSBkZXZpY2UgSUQg UE5QMGEwMyAoMDMwYWQwNDEpClBOUDA1MDE6IGFkZGluZyBpcnEgbWFzayAw eDEwClBOUDA1MDE6IGFkZGluZyBpbyByYW5nZSAweDNmOC0weDNmZiwgc2l6 ZT0weDgsIGFsaWduPTAKcG5wYmlvczogaGFuZGxlIDExIGRldmljZSBJRCBQ TlAwNTAxICgwMTA1ZDA0MSkKUE5QMDcwMDogYWRkaW5nIGRtYSBtYXNrIDB4 NApQTlAwNzAwOiBhZGRpbmcgaW8gcmFuZ2UgMHgzZjAtMHgzZjUsIHNpemU9 MHg2LCBhbGlnbj0wClBOUDA3MDA6IGFkZGluZyBpbyByYW5nZSAweDNmNy0w eDNmNywgc2l6ZT0weDEsIGFsaWduPTAKUE5QMDcwMDogYWRkaW5nIGlycSBt YXNrIDB4NDAKcG5wYmlvczogaGFuZGxlIDEyIGRldmljZSBJRCBQTlAwNzAw ICgwMDA3ZDA0MSkKUE5QMDQwMTogYWRkaW5nIGRtYSBtYXNrIDB4OApQTlAw NDAxOiBhZGRpbmcgaXJxIG1hc2sgMHg4MApQTlAwNDAxOiBhZGRpbmcgaW8g cmFuZ2UgMHgzNzgtMHgzN2YsIHNpemU9MHg4LCBhbGlnbj0wClBOUDA0MDE6 IGFkZGluZyBpbyByYW5nZSAweDc3OC0weDc3Ziwgc2l6ZT0weDgsIGFsaWdu PTAKcG5wYmlvczogaGFuZGxlIDE0IGRldmljZSBJRCBQTlAwNDAxICgwMTA0 ZDA0MSkKUE5QMDUwMTogYWRkaW5nIGlycSBtYXNrIDB4OApQTlAwNTAxOiBh ZGRpbmcgaW8gcmFuZ2UgMHgyZjgtMHgyZmYsIHNpemU9MHg4LCBhbGlnbj0w CnBucGJpb3M6IGhhbmRsZSAxNSBkZXZpY2UgSUQgUE5QMDUwMSAoMDEwNWQw NDEpClBOUGIwMDY6IGFkZGluZyBpcnEgbWFzayAweDQwMApQTlBiMDA2OiBh ZGRpbmcgaW8gcmFuZ2UgMHgzMzAtMHgzMzMsIHNpemU9MHg0LCBhbGlnbj0w CnBucGJpb3M6IGhhbmRsZSAxNiBkZXZpY2UgSUQgUE5QYjAwNiAoMDZiMGQw NDEpClBOUGIwMmY6IGFkZGluZyBpbyByYW5nZSAweDIwMS0weDIwMSwgc2l6 ZT0weDEsIGFsaWduPTAKcG5wYmlvczogaGFuZGxlIDE3IGRldmljZSBJRCBQ TlBiMDJmICgyZmIwZDA0MSkKcG5wX2lkZW50aWZ5OiBUcnlpbmcgUmVhZF9Q b3J0IGF0IDIwMwpwbnBfaWRlbnRpZnk6IFRyeWluZyBSZWFkX1BvcnQgYXQg MjQzCnBucF9pZGVudGlmeTogVHJ5aW5nIFJlYWRfUG9ydCBhdCAyODMKcG5w X2lkZW50aWZ5OiBUcnlpbmcgUmVhZF9Qb3J0IGF0IDJjMwpwbnBfaWRlbnRp Znk6IFRyeWluZyBSZWFkX1BvcnQgYXQgMzAzCnBucF9pZGVudGlmeTogVHJ5 aW5nIFJlYWRfUG9ydCBhdCAzNDMKcG5wX2lkZW50aWZ5OiBUcnlpbmcgUmVh ZF9Qb3J0IGF0IDM4MwpwbnBfaWRlbnRpZnk6IFRyeWluZyBSZWFkX1BvcnQg YXQgM2MzClBOUCBJZGVudGlmeSBjb21wbGV0ZQpzYzogc2MwIGFscmVhZHkg ZXhpc3RzOyBza2lwcGluZyBpdAp2Z2E6IHZnYTAgYWxyZWFkeSBleGlzdHM7 IHNraXBwaW5nIGl0CmlzYV9wcm9iZV9jaGlsZHJlbjogZGlzYWJsaW5nIFBu UCBkZXZpY2VzCmlzYV9wcm9iZV9jaGlsZHJlbjogcHJvYmluZyBub24tUG5Q IGRldmljZXMKcG10aW1lcjAgb24gaXNhMApvcm0wOiA8SVNBIE9wdGlvbiBS T01zPiBhdCBpb21lbSAweGMwMDAwLTB4Y2M3ZmYsMHhkMDAwMC0weGQ0N2Zm LDB4ZDUwMDAtMHhkNjdmZiwweGQ3MDAwLTB4ZDc3ZmYgcG5waWQgT1JNMDAw MCBvbiBpc2EwCmFkdjA6IG5vdCBwcm9iZWQgKGRpc2FibGVkKQphaGEwOiBu b3QgcHJvYmVkIChkaXNhYmxlZCkKYWljMDogbm90IHByb2JlZCAoZGlzYWJs ZWQpCmF0a2JkYzA6IDxLZXlib2FyZCBjb250cm9sbGVyIChpODA0Mik+IGF0 IHBvcnQgMHg2MCwweDY0IG9uIGlzYTAKYXRrYmQwOiA8QVQgS2V5Ym9hcmQ+ IGlycSAxIG9uIGF0a2JkYzAKYXRrYmQ6IHRoZSBjdXJyZW50IGtiZCBjb250 cm9sbGVyIGNvbW1hbmQgYnl0ZSAwMDY3CmF0a2JkOiBrZXlib2FyZCBJRCAw eDQxYWIgKDIpCmtiZDAgYXQgYXRrYmQwCmtiZDA6IGF0a2JkMCwgQVQgMTAx LzEwMiAoMiksIGNvbmZpZzoweDAsIGZsYWdzOjB4M2QwMDAwCmF0a2JkMDog W0dJQU5ULUxPQ0tFRF0KcHNtMDogY3VycmVudCBjb21tYW5kIGJ5dGU6MDA2 Nwpwc20wOiBzdHJhbmdlIHJlc3VsdCBmb3IgdGVzdCBhdXggcG9ydCAoMiku CnBzbTA6IGZhaWxlZCB0byByZXNldCB0aGUgYXV4IGRldmljZS4KYnQwOiBu b3QgcHJvYmVkIChkaXNhYmxlZCkKY3MwOiBub3QgcHJvYmVkIChkaXNhYmxl ZCkKZWQwOiBub3QgcHJvYmVkIChkaXNhYmxlZCkKZmRjMDogaWNfdHlwZSA5 MCBwYXJ0X2lkIDgwCmZkYzA6IDxFbmhhbmNlZCBmbG9wcHkgY29udHJvbGxl cj4gYXQgcG9ydCAweDNmMC0weDNmNSwweDNmNyBpcnEgNiBkcnEgMiBvbiBp c2EwCmZkYzA6IGljX3R5cGUgOTAgcGFydF9pZCA4MApmZGMwOiBbTVBTQUZF XQpmZGMwOiBbRkFTVF0KZmQwOiA8MTQ0MC1LQiAzLjUiIGRyaXZlPiBvbiBm ZGMwIGRyaXZlIDAKZmUwOiBub3QgcHJvYmVkIChkaXNhYmxlZCkKaWUwOiBu b3QgcHJvYmVkIChkaXNhYmxlZCkKbG5jMDogbm90IHByb2JlZCAoZGlzYWJs ZWQpCnBwYzA6IHBhcmFsbGVsIHBvcnQgZm91bmQgYXQgMHgzNzgKcHBjMDog dXNpbmcgZXh0ZW5kZWQgSS9PIHBvcnQgcmFuZ2UKcHBjMDogRUNQIFNQUCBF Q1ArRVBQIFNQUApwcGMwOiA8UGFyYWxsZWwgcG9ydD4gYXQgcG9ydCAweDM3 OC0weDM3ZiBpcnEgNyBvbiBpc2EwCnBwYzA6IFNNQy1saWtlIGNoaXBzZXQg KEVDUC9FUFAvUFMyL05JQkJMRSkgaW4gQ09NUEFUSUJMRSBtb2RlCnBwYzA6 IEZJRk8gd2l0aCAxNi8xNi8xNiBieXRlcyB0aHJlc2hvbGQKcHBidXMwOiA8 UGFyYWxsZWwgcG9ydCBidXM+IG9uIHBwYzAKcGxpcDA6IDxQTElQIG5ldHdv cmsgaW50ZXJmYWNlPiBvbiBwcGJ1czAKcGxpcDA6IGJwZiBhdHRhY2hlZAps cHQwOiA8UHJpbnRlcj4gb24gcHBidXMwCmxwdDA6IEludGVycnVwdC1kcml2 ZW4gcG9ydApwcGkwOiA8UGFyYWxsZWwgSS9PPiBvbiBwcGJ1czAKc2MwOiA8 U3lzdGVtIGNvbnNvbGU+IGF0IGZsYWdzIDB4MTAwIG9uIGlzYTAKc2MwOiBW R0EgPDE2IHZpcnR1YWwgY29uc29sZXMsIGZsYWdzPTB4MzAwPgpzYzA6IGZi MCwga2JkMCwgdGVybWluYWwgZW11bGF0b3I6IHNjIChzeXNjb25zIHRlcm1p bmFsKQpzaW8wOiBpcnEgbWFwczogMHgxODAxIDB4MTgxMSAweDE4MDEgMHgx ODAxCnNpbzAgYXQgcG9ydCAweDNmOC0weDNmZiBpcnEgNCBmbGFncyAweDEw IG9uIGlzYTAKc2lvMDogdHlwZSAxNjU1MEEKc2lvMTogaXJxIG1hcHM6IDB4 MTgwMSAweDE4MDkgMHgxODAxIDB4MTgwMQpzaW8xIGF0IHBvcnQgMHgyZjgt MHgyZmYgaXJxIDMgb24gaXNhMApzaW8xOiB0eXBlIDE2NTUwQQpzaW8yOiBu b3QgcHJvYmVkIChkaXNhYmxlZCkKc2lvMzogbm90IHByb2JlZCAoZGlzYWJs ZWQpCnNuMDogbm90IHByb2JlZCAoZGlzYWJsZWQpCnZnYTA6IDxHZW5lcmlj IElTQSBWR0E+IGF0IHBvcnQgMHgzYzAtMHgzZGYgaW9tZW0gMHhhMDAwMC0w eGJmZmZmIG9uIGlzYTAKdnQwOiBub3QgcHJvYmVkIChkaXNhYmxlZCkKaXNh X3Byb2JlX2NoaWxkcmVuOiBwcm9iaW5nIFBuUCBkZXZpY2VzCnVua25vd246 IDxQTlAwMzAzPiBjYW4ndCBhc3NpZ24gcmVzb3VyY2VzIChwb3J0KQp1bmtu b3duOiA8UE5QMDMwMz4gYXQgcG9ydCAweDYwIHBucGlkIFBOUDAzMDMgb24g aXNhMAp1bmtub3duOiA8UE5QMDgwMD4gZmFpbGVkIHRvIHByb2JlIGF0IHBv cnQgMHg2MSBwbnBpZCBQTlAwODAwIG9uIGlzYTAKdW5rbm93bjogPFBOUDBj MDE+IGNhbid0IGFzc2lnbiByZXNvdXJjZXMgKG1lbW9yeSkKdW5rbm93bjog PFBOUDBjMDE+IGF0IGlvbWVtIDAtMHg5ZmZmZiBwbnBpZCBQTlAwYzAxIG9u IGlzYTAKdW5rbm93bjogPFBOUDA1MDE+IGNhbid0IGFzc2lnbiByZXNvdXJj ZXMgKHBvcnQpCnVua25vd246IDxQTlAwNTAxPiBhdCBwb3J0IDB4M2Y4LTB4 M2ZmIHBucGlkIFBOUDA1MDEgb24gaXNhMAp1bmtub3duOiA8UE5QMDcwMD4g Y2FuJ3QgYXNzaWduIHJlc291cmNlcyAocG9ydCkKdW5rbm93bjogPFBOUDA3 MDA+IGF0IHBvcnQgMHgzZjAtMHgzZjUgcG5waWQgUE5QMDcwMCBvbiBpc2Ew CnVua25vd246IDxQTlAwNDAxPiBjYW4ndCBhc3NpZ24gcmVzb3VyY2VzIChw b3J0KQp1bmtub3duOiA8UE5QMDQwMT4gYXQgcG9ydCAweDM3OC0weDM3ZiBw bnBpZCBQTlAwNDAxIG9uIGlzYTAKdW5rbm93bjogPFBOUDA1MDE+IGNhbid0 IGFzc2lnbiByZXNvdXJjZXMgKHBvcnQpCnVua25vd246IDxQTlAwNTAxPiBh dCBwb3J0IDB4MmY4LTB4MmZmIHBucGlkIFBOUDA1MDEgb24gaXNhMAp1bmtu b3duOiA8UE5QYjAwNj4gZmFpbGVkIHRvIHByb2JlIGF0IHBvcnQgMHgzMzAt MHgzMzMgaXJxIDEwIHBucGlkIFBOUGIwMDYgb24gaXNhMAp1bmtub3duOiA8 UE5QYjAyZj4gZmFpbGVkIHRvIHByb2JlIGF0IHBvcnQgMHgyMDEgcG5waWQg UE5QYjAyZiBvbiBpc2EwCnVnZW4wOiB2ZW5kb3IgMHgwNDZkIENhbWVyYSwg cmV2IDEuMDAvMS4wMCwgYWRkciAyCkRldmljZSBjb25maWd1cmF0aW9uIGZp bmlzaGVkLgpwcm9jZnMgcmVnaXN0ZXJlZApUaW1lY291bnRlciAiVFNDIiBm cmVxdWVuY3kgMjAwNDU1ODYzMSBIeiBxdWFsaXR5IDgwMApUaW1lY291bnRl cnMgdGljayBldmVyeSAxLjAwMCBtc2VjCklQIEZpbHRlcjogdjQuMS44IGlu aXRpYWxpemVkLiAgRGVmYXVsdCA9IHBhc3MgYWxsLCBMb2dnaW5nID0gZGlz YWJsZWQKbG8wOiBicGYgYXR0YWNoZWQKaXBmdzIgKCtpcHY2KSBpbml0aWFs aXplZCwgZGl2ZXJ0IGxvYWRhYmxlLCBydWxlLWJhc2VkIGZvcndhcmRpbmcg ZGlzYWJsZWQsIGRlZmF1bHQgdG8gYWNjZXB0LCBsb2dnaW5nIGRpc2FibGVk CmF0YTAtbWFzdGVyOiBwaW89UElPNCB3ZG1hPVdETUEyIHVkbWE9VURNQTEz MyBjYWJsZT04MCB3aXJlCmF0YXBpY2FtOiBhdGFwaWNhbTAgYWxyZWFkeSBl eGlzdHM7IHNraXBwaW5nIGl0CmFkMDogc2V0dGluZyBQSU80IG9uIG5WaWRp YSBuRm9yY2UyIGNoaXAKYWQwOiBzZXR0aW5nIFVETUExMzMgb24gblZpZGlh IG5Gb3JjZTIgY2hpcAphZDA6IDU4NjQ0TUIgPE1heHRvciA2WTA2MEwwIFlB UjQxVlcwPiBhdCBhdGEwLW1hc3RlciBVRE1BMTMzCmFkMDogMTIwMTAzMjAw IHNlY3RvcnMgWzExOTE1MEMvMTZILzYzU10gMTYgc2VjdG9ycy9pbnRlcnJ1 cHQgMSBkZXB0aCBxdWV1ZQphZDA6IG5WaWRpYSBjaGVjazEgZmFpbGVkCmFk MDogQWRhcHRlYyBjaGVjazEgZmFpbGVkCmFkMDogTFNJICh2MykgY2hlY2sx IGZhaWxlZAphZDA6IExTSSAodjIpIGNoZWNrMSBmYWlsZWQKYWQwOiBGcmVl QlNEIGNoZWNrMSBmYWlsZWQKYXRhMS1zbGF2ZTogcGlvPVBJTzQgd2RtYT1X RE1BMiB1ZG1hPVVETUEzMyBjYWJsZT00MCB3aXJlCmF0YTEtbWFzdGVyOiBw aW89UElPNCB3ZG1hPVdETUEyIHVkbWE9VURNQTMzIGNhYmxlPTgwIHdpcmUK YWNkMDogc2V0dGluZyBQSU80IG9uIG5WaWRpYSBuRm9yY2UyIGNoaXAKYWNk MDogc2V0dGluZyBVRE1BMzMgb24gblZpZGlhIG5Gb3JjZTIgY2hpcAphY2Qw OiA8SEwtRFQtU1QgRFZEUkFNIEdTQS00MTY1Qi9ETDAzPiBEVkRSIGRyaXZl IGF0IGF0YTEgYXMgbWFzdGVyCmFjZDA6IHJlYWQgNjg5MEtCL3MgKDY4OTBL Qi9zKSB3cml0ZSAxNzIyS0IvcyAoMTcyMktCL3MpLCAyMDQ4S0IgYnVmZmVy LCBVRE1BMzMKYWNkMDogUmVhZHM6IENEUiwgQ0RSVywgQ0REQSBzdHJlYW0s IERWRFJPTSwgRFZEUiwgRFZEUkFNLCBwYWNrZXQKYWNkMDogV3JpdGVzOiBD RFIsIENEUlcsIERWRFIsIERWRFJBTSwgdGVzdCB3cml0ZSwgYnVybnByb29m CmFjZDA6IEF1ZGlvOiBwbGF5LCAyNTYgdm9sdW1lIGxldmVscwphY2QwOiBN ZWNoYW5pc206IGVqZWN0YWJsZSB0cmF5LCB1bmxvY2tlZAphY2QwOiBNZWRp dW06IENELVJXIDEyMG1tIGRhdGEgZGlzYwphY2QxOiBzZXR0aW5nIFBJTzQg b24gblZpZGlhIG5Gb3JjZTIgY2hpcAphY2QxOiBzZXR0aW5nIFVETUEzMyBv biBuVmlkaWEgbkZvcmNlMiBjaGlwCmFjZDE6IDxMRyBEVkQtUk9NIERSRC04 MTYwQi8xLjAxPiBEVkRST00gZHJpdmUgYXQgYXRhMSBhcyBzbGF2ZQphY2Qx OiByZWFkIDI3NTBLQi9zICg4MjUwS0IvcyksIDUxMktCIGJ1ZmZlciwgVURN QTMzCmFjZDE6IFJlYWRzOiBDRFIsIENEUlcsIENEREEgc3RyZWFtLCBEVkRS T00sIERWRFIsIHBhY2tldAphY2QxOiBXcml0ZXM6CmFjZDE6IEF1ZGlvOiBw bGF5LCAyNTUgdm9sdW1lIGxldmVscwphY2QxOiBNZWNoYW5pc206IGVqZWN0 YWJsZSB0cmF5LCB1bmxvY2tlZAphY2QxOiBNZWRpdW06IENELVIgMTIwbW0g YXVkaW8gZGlzYwphdGEwLW1hc3RlcjogcGlvPVBJTzQgd2RtYT1XRE1BMiB1 ZG1hPVVETUExMzMgY2FibGU9NDAgd2lyZQphZDQ6IDE5MDc4Mk1CIDxTZWFn YXRlIFNUMzIwMDgyMkFTIDMuMDE+IGF0IGF0YTItbWFzdGVyIFNBVEExNTAK YWQ0OiAzOTA3MjE5Njggc2VjdG9ycyBbMzg3NjIxQy8xNkgvNjNTXSAxNiBz ZWN0b3JzL2ludGVycnVwdCAxIGRlcHRoIHF1ZXVlCmFkNDogU2lsaWNvbiBJ bWFnZSBjaGVjazMgZmFpbGVkCmFkNDogQWRhcHRlYyBjaGVjazEgZmFpbGVk CmFkNDogTFNJICh2MykgY2hlY2sxIGZhaWxlZAphZDQ6IExTSSAodjIpIGNo ZWNrMSBmYWlsZWQKYWQ0OiBGcmVlQlNEIGNoZWNrMSBmYWlsZWQKR0VPTTog bmV3IGRpc2sgYWQwCkdFT006IG5ldyBkaXNrIGFkNAphY2QwOiBGQUlMVVJF IC0gUkVBRF9CSUcgSUxMRUdBTCBSRVFVRVNUIGFzYz0weDY0IGFzY3E9MHgw MCBlcnJvcj00PEFCT1JURUQ+Cihwcm9iZTA6YXRhMTowOjA6MCk6IGVycm9y IDIyCihwcm9iZTA6YXRhMTowOjA6MCk6IFVucmV0cnlhYmxlIEVycm9yCihw cm9iZTE6YXRhMTowOjE6MCk6IGVycm9yIDIyCihwcm9iZTE6YXRhMTowOjE6 MCk6IFVucmV0cnlhYmxlIEVycm9yCihwcm9iZTA6YXRhMTowOjA6MCk6IGVy cm9yIDIyCihwcm9iZTA6YXRhMTowOjA6MCk6IFVucmV0cnlhYmxlIEVycm9y Cihwcm9iZTE6YXRhMTowOjE6MCk6IGVycm9yIDIyCihwcm9iZTE6YXRhMTow OjE6MCk6IFVucmV0cnlhYmxlIEVycm9yCnBhc3MwIGF0IGF0YTEgYnVzIDAg dGFyZ2V0IDAgbHVuIDAKcGFzczA6IDxITC1EVC1TVCBEVkRSQU0gR1NBLTQx NjVCIERMMDM+IFJlbW92YWJsZSBDRC1ST00gU0NTSS0wIGRldmljZSAKcGFz czA6IDMzLjAwME1CL3MgdHJhbnNmZXJzCnBhc3MxIGF0IGF0YTEgYnVzIDAg dGFyZ2V0IDEgbHVuIDAKcGFzczE6IDxMRyBEVkQtUk9NIERSRDgxNjBCIDEu MDE+IFJlbW92YWJsZSBDRC1ST00gU0NTSS0wIGRldmljZSAKcGFzczE6IDMz LjAwME1CL3MgdHJhbnNmZXJzCkFUQSBQc2V1ZG9SQUlEIGxvYWRlZApjZDAg YXQgYXRhMSBidXMgMCB0YXJnZXQgMCBsdW4gMApjZDA6IDxITC1EVC1TVCBE VkRSQU0gR1NBLTQxNjVCIERMMDM+IFJlbW92YWJsZSBDRC1ST00gU0NTSS0w IGRldmljZSAKY2QwOiAzMy4wMDBNQi9zIHRyYW5zZmVycwpjZDA6IGNkIHBy ZXNlbnQgWzMwMzMyMCB4IDIwNDggYnl0ZSByZWNvcmRzXQpjZDEgYXQgYXRh MSBidXMgMCB0YXJnZXQgMSBsdW4gMApjZDE6IDxMRyBEVkQtUk9NIERSRDgx NjBCIDEuMDE+IFJlbW92YWJsZSBDRC1ST00gU0NTSS0wIGRldmljZSAKY2Qx OiAzMy4wMDBNQi9zIHRyYW5zZmVycwpjZDE6IGNkIHByZXNlbnQgWzIzMzk0 MiB4IDIwNDggYnl0ZSByZWNvcmRzXQphY2QwOiBGQUlMVVJFIC0gUkVBRF9C SUcgSUxMRUdBTCBSRVFVRVNUIGFzYz0weDY0IGFzY3E9MHgwMCBlcnJvcj00 PEFCT1JURUQ+CkdFT006IG5ldyBkaXNrIGNkMApHRU9NOiBuZXcgZGlzayBj ZDEKKGNkMDphdGExOjA6MDowKTogUkVBRCgxMCkuIENEQjogMjggMCAwIDQg YTAgZDcgMCAwIDEgMCAKKGNkMDphdGExOjA6MDowKTogQ0FNIFN0YXR1czog U0NTSSBTdGF0dXMgRXJyb3IKKGNkMDphdGExOjA6MDowKTogU0NTSSBTdGF0 dXM6IENoZWNrIENvbmRpdGlvbgooY2QwOmF0YTE6MDowOjApOiBJTExFR0FM IFJFUVVFU1QgY3NpOjI4LDAsMCw5MCBhc2M6NjQsMAooY2QwOmF0YTE6MDow OjApOiBJbGxlZ2FsIG1vZGUgZm9yIHRoaXMgdHJhY2sKKGNkMDphdGExOjA6 MDowKTogKGNkMDphdGExOjA6MDowKTogUkVBRCgxMCkuIENEQjogMjggMCAw IDQgYTAgZDcgMCAwIDEgMCAKKGNkMDphdGExOjA6MDowKTogSUxMRUdBTCBS RVFVRVNUIGNzaToyOCwwLDAsOTAgYXNjOjY0LDAKKGNkMDphdGExOjA6MDow KTogSWxsZWdhbCBtb2RlIGZvciB0aGlzIHRyYWNrClVucmV0cnlhYmxlIGVy cm9yCihjZDA6YXRhMTowOjA6MCk6IGVycm9yIDYKKGNkMDphdGExOjA6MDow KTogVW5yZXRyeWFibGUgRXJyb3IKKGNkMDphdGExOjA6MDowKTogY2Rkb25l OiBnb3QgZXJyb3IgMHg2IGJhY2sKKGNkMTphdGExOjA6MTowKTogUkVBRCgx MCkuIENEQjogMjggMCAwIDAgMCAwIDAgMCAxIDAgCihjZDE6YXRhMTowOjE6 MCk6IENBTSBTdGF0dXM6IFNDU0kgU3RhdHVzIEVycm9yCihjZDE6YXRhMTow OjE6MCk6IFNDU0kgU3RhdHVzOiBDaGVjayBDb25kaXRpb24KKGNkMTphdGEx OjA6MTowKTogSUxMRUdBTCBSRVFVRVNUIGFzYzo2NCwwCihjZDE6YXRhMTow OjE6MCk6IElsbGVnYWwgbW9kZSBmb3IgdGhpcyB0cmFjawooY2QxOmF0YTE6 MDoxOjApOiAoY2QxOmF0YTE6MDoxOjApOiBSRUFEKDEwKS4gQ0RCOiAyOCAw IDAgMCAwIDAgMCAwIDEgMCAKKGNkMTphdGExOjA6MTowKTogSUxMRUdBTCBS RVFVRVNUIGFzYzo2NCwwCihjZDE6YXRhMTowOjE6MCk6IElsbGVnYWwgbW9k ZSBmb3IgdGhpcyB0cmFjawpVbnJldHJ5YWJsZSBlcnJvcgooY2QxOmF0YTE6 MDoxOjApOiBlcnJvciA2CihjZDE6YXRhMTowOjE6MCk6IFVucmV0cnlhYmxl IEVycm9yCihjZDE6YXRhMTowOjE6MCk6IGNkZG9uZTogZ290IGVycm9yIDB4 NiBiYWNrCihjZDE6YXRhMTowOjE6MCk6IFJFQUQoMTApLiBDREI6IDI4IDAg MCAwIDAgMSAwIDAgMSAwIAooY2QxOmF0YTE6MDoxOjApOiBDQU0gU3RhdHVz OiBTQ1NJIFN0YXR1cyBFcnJvcgooY2QxOmF0YTE6MDoxOjApOiBTQ1NJIFN0 YXR1czogQ2hlY2sgQ29uZGl0aW9uCihjZDE6YXRhMTowOjE6MCk6IElMTEVH QUwgUkVRVUVTVCBhc2M6NjQsMAooY2QxOmF0YTE6MDoxOjApOiBJbGxlZ2Fs IG1vZGUgZm9yIHRoaXMgdHJhY2sKKGNkMTphdGExOjA6MTowKTogKGNkMTph dGExOjA6MTowKTogUkVBRCgxMCkuIENEQjogMjggMCAwIDAgMCAxIDAgMCAx IDAgCihjZDE6YXRhMTowOjE6MCk6IElMTEVHQUwgUkVRVUVTVCBhc2M6NjQs MAooY2QxOmF0YTE6MDoxOjApOiBJbGxlZ2FsIG1vZGUgZm9yIHRoaXMgdHJh Y2sKVW5yZXRyeWFibGUgZXJyb3IKKGNkMTphdGExOjA6MTowKTogZXJyb3Ig NgooY2QxOmF0YTE6MDoxOjApOiBVbnJldHJ5YWJsZSBFcnJvcgooY2QxOmF0 YTE6MDoxOjApOiBjZGRvbmU6IGdvdCBlcnJvciAweDYgYmFjawooY2QxOmF0 YTE6MDoxOjApOiBSRUFEKDEwKS4gQ0RCOiAyOCAwIDAgMCAwIDAgMCAwIDEg MCAKKGNkMTphdGExOjA6MTowKTogQ0FNIFN0YXR1czogU0NTSSBTdGF0dXMg RXJyb3IKKGNkMTphdGExOjA6MTowKTogU0NTSSBTdGF0dXM6IENoZWNrIENv bmRpdGlvbgooY2QxOmF0YTE6MDoxOjApOiBJTExFR0FMIFJFUVVFU1QgYXNj OjY0LDAKKGNkMTphdGExOjA6MTowKTogSWxsZWdhbCBtb2RlIGZvciB0aGlz IHRyYWNrCihjZDE6YXRhMTowOjE6MCk6IChjZDE6YXRhMTowOjE6MCk6IFJF QUQoMTApLiBDREI6IDI4IDAgMCAwIDAgMCAwIDAgMSAwIAooY2QxOmF0YTE6 MDoxOjApOiBJTExFR0FMIFJFUVVFU1QgYXNjOjY0LDAKKGNkMTphdGExOjA6 MTowKTogSWxsZWdhbCBtb2RlIGZvciB0aGlzIHRyYWNrClVucmV0cnlhYmxl IGVycm9yCihjZDE6YXRhMTowOjE6MCk6IGVycm9yIDYKKGNkMTphdGExOjA6 MTowKTogVW5yZXRyeWFibGUgRXJyb3IKKGNkMTphdGExOjA6MTowKTogY2Rk b25lOiBnb3QgZXJyb3IgMHg2IGJhY2sKKGNkMTphdGExOjA6MTowKTogUkVB RCgxMCkuIENEQjogMjggMCAwIDAgMCAxIDAgMCAxIDAgCihjZDE6YXRhMTow OjE6MCk6IENBTSBTdGF0dXM6IFNDU0kgU3RhdHVzIEVycm9yCihjZDE6YXRh MTowOjE6MCk6IFNDU0kgU3RhdHVzOiBDaGVjayBDb25kaXRpb24KKGNkMTph dGExOjA6MTowKTogSUxMRUdBTCBSRVFVRVNUIGFzYzo2NCwwCihjZDE6YXRh MTowOjE6MCk6IElsbGVnYWwgbW9kZSBmb3IgdGhpcyB0cmFjawooY2QxOmF0 YTE6MDoxOjApOiAoY2QxOmF0YTE6MDoxOjApOiBSRUFEKDEwKS4gQ0RCOiAy OCAwIDAgMCAwIDEgMCAwIDEgMCAKKGNkMTphdGExOjA6MTowKTogSUxMRUdB TCBSRVFVRVNUIGFzYzo2NCwwCihjZDE6YXRhMTowOjE6MCk6IElsbGVnYWwg bW9kZSBmb3IgdGhpcyB0cmFjawpVbnJldHJ5YWJsZSBlcnJvcgooY2QxOmF0 YTE6MDoxOjApOiBlcnJvciA2CihjZDE6YXRhMTowOjE6MCk6IFVucmV0cnlh YmxlIEVycm9yCihjZDE6YXRhMTowOjE6MCk6IGNkZG9uZTogZ290IGVycm9y IDB4NiBiYWNrClRyeWluZyB0byBtb3VudCByb290IGZyb20gdWZzOi9kZXYv YWQwczJhCnN0YXJ0X2luaXQ6IHRyeWluZyAvc2Jpbi9pbml0CnNwbGFzaDog aW1hZ2UgZGVjb2RlciBmb3VuZDogbG9nb19zYXZlcgpwY2kwOiBkcml2ZXIg YWRkZWQKZm91bmQtPgl2ZW5kb3I9MHgxMGRlLCBkZXY9MHgwMWViLCByZXZp ZD0weGMxCglidXM9MCwgc2xvdD0wLCBmdW5jPTEKCWNsYXNzPTA1LTAwLTAw LCBoZHJ0eXBlPTB4MDAsIG1mZGV2PTEKCWNtZHJlZz0weDAwMDAsIHN0YXRy ZWc9MHgwMDIwLCBjYWNoZWxuc3o9MCAoZHdvcmRzKQoJbGF0dGltZXI9MHgw MCAoMCBucyksIG1pbmdudD0weDAwICgwIG5zKSwgbWF4bGF0PTB4MDAgKDAg bnMpCnBjaTA6MDoxOiByZXByb2Jpbmcgb24gZHJpdmVyIGFkZGVkCmZvdW5k LT4JdmVuZG9yPTB4MTBkZSwgZGV2PTB4MDFlZSwgcmV2aWQ9MHhjMQoJYnVz PTAsIHNsb3Q9MCwgZnVuYz0yCgljbGFzcz0wNS0wMC0wMCwgaGRydHlwZT0w eDAwLCBtZmRldj0xCgljbWRyZWc9MHgwMDAwLCBzdGF0cmVnPTB4MDAyMCwg Y2FjaGVsbnN6PTAgKGR3b3JkcykKCWxhdHRpbWVyPTB4MDAgKDAgbnMpLCBt aW5nbnQ9MHgwMCAoMCBucyksIG1heGxhdD0weDAwICgwIG5zKQpwY2kwOjA6 MjogcmVwcm9iaW5nIG9uIGRyaXZlciBhZGRlZApmb3VuZC0+CXZlbmRvcj0w eDEwZGUsIGRldj0weDAxZWQsIHJldmlkPTB4YzEKCWJ1cz0wLCBzbG90PTAs IGZ1bmM9MwoJY2xhc3M9MDUtMDAtMDAsIGhkcnR5cGU9MHgwMCwgbWZkZXY9 MQoJY21kcmVnPTB4MDAwMCwgc3RhdHJlZz0weDAwMjAsIGNhY2hlbG5zej0w IChkd29yZHMpCglsYXR0aW1lcj0weDAwICgwIG5zKSwgbWluZ250PTB4MDAg KDAgbnMpLCBtYXhsYXQ9MHgwMCAoMCBucykKcGNpMDowOjM6IHJlcHJvYmlu ZyBvbiBkcml2ZXIgYWRkZWQKZm91bmQtPgl2ZW5kb3I9MHgxMGRlLCBkZXY9 MHgwMWVjLCByZXZpZD0weGMxCglidXM9MCwgc2xvdD0wLCBmdW5jPTQKCWNs YXNzPTA1LTAwLTAwLCBoZHJ0eXBlPTB4MDAsIG1mZGV2PTEKCWNtZHJlZz0w eDAwMDAsIHN0YXRyZWc9MHgwMDIwLCBjYWNoZWxuc3o9MCAoZHdvcmRzKQoJ bGF0dGltZXI9MHgwMCAoMCBucyksIG1pbmdudD0weDAwICgwIG5zKSwgbWF4 bGF0PTB4MDAgKDAgbnMpCnBjaTA6MDo0OiByZXByb2Jpbmcgb24gZHJpdmVy IGFkZGVkCmZvdW5kLT4JdmVuZG9yPTB4MTBkZSwgZGV2PTB4MDFlZiwgcmV2 aWQ9MHhjMQoJYnVzPTAsIHNsb3Q9MCwgZnVuYz01CgljbGFzcz0wNS0wMC0w MCwgaGRydHlwZT0weDAwLCBtZmRldj0xCgljbWRyZWc9MHgwMDAwLCBzdGF0 cmVnPTB4MDAyMCwgY2FjaGVsbnN6PTAgKGR3b3JkcykKCWxhdHRpbWVyPTB4 MDAgKDAgbnMpLCBtaW5nbnQ9MHgwMCAoMCBucyksIG1heGxhdD0weDAwICgw IG5zKQpwY2kwOjA6NTogcmVwcm9iaW5nIG9uIGRyaXZlciBhZGRlZApmb3Vu ZC0+CXZlbmRvcj0weDEwZGUsIGRldj0weDAwNjQsIHJldmlkPTB4YTIKCWJ1 cz0wLCBzbG90PTEsIGZ1bmM9MQoJY2xhc3M9MGMtMDUtMDAsIGhkcnR5cGU9 MHgwMCwgbWZkZXY9MQoJY21kcmVnPTB4MDAwMSwgc3RhdHJlZz0weDAwYjAs IGNhY2hlbG5zej0wIChkd29yZHMpCglsYXR0aW1lcj0weDAwICgwIG5zKSwg bWluZ250PTB4MDMgKDc1MCBucyksIG1heGxhdD0weDAxICgyNTAgbnMpCglp bnRwaW49YSwgaXJxPTUKCXBvd2Vyc3BlYyAyICBzdXBwb3J0cyBEMCBEMyAg Y3VycmVudCBEMApwY2kwOjE6MTogcmVwcm9iaW5nIG9uIGRyaXZlciBhZGRl ZApmb3VuZC0+CXZlbmRvcj0weDEwZGUsIGRldj0weDAwNjYsIHJldmlkPTB4 YTEKCWJ1cz0wLCBzbG90PTQsIGZ1bmM9MAoJY2xhc3M9MDItMDAtMDAsIGhk cnR5cGU9MHgwMCwgbWZkZXY9MAoJY21kcmVnPTB4MDAwNywgc3RhdHJlZz0w eDAwYjAsIGNhY2hlbG5zej0wIChkd29yZHMpCglsYXR0aW1lcj0weDAwICgw IG5zKSwgbWluZ250PTB4MDEgKDI1MCBucyksIG1heGxhdD0weDE0ICg1MDAw IG5zKQoJaW50cGluPWEsIGlycT0xMgoJcG93ZXJzcGVjIDIgIHN1cHBvcnRz IEQwIEQxIEQyIEQzICBjdXJyZW50IEQwCnBjaTA6NDowOiByZXByb2Jpbmcg b24gZHJpdmVyIGFkZGVkCmZvdW5kLT4JdmVuZG9yPTB4MTBkZSwgZGV2PTB4 MDA2YiwgcmV2aWQ9MHhhMgoJYnVzPTAsIHNsb3Q9NSwgZnVuYz0wCgljbGFz cz0wNC0wMS0wMCwgaGRydHlwZT0weDAwLCBtZmRldj0wCgljbWRyZWc9MHgw MDA2LCBzdGF0cmVnPTB4MDBiMCwgY2FjaGVsbnN6PTAgKGR3b3JkcykKCWxh dHRpbWVyPTB4MDAgKDAgbnMpLCBtaW5nbnQ9MHgwMSAoMjUwIG5zKSwgbWF4 bGF0PTB4MGMgKDMwMDAgbnMpCglpbnRwaW49YSwgaXJxPTEyCglwb3dlcnNw ZWMgMiAgc3VwcG9ydHMgRDAgRDEgRDIgRDMgIGN1cnJlbnQgRDAKcGNpMDo1 OjA6IHJlcHJvYmluZyBvbiBkcml2ZXIgYWRkZWQKZm91bmQtPgl2ZW5kb3I9 MHgxMGRlLCBkZXY9MHgwMDZhLCByZXZpZD0weGExCglidXM9MCwgc2xvdD02 LCBmdW5jPTAKCWNsYXNzPTA0LTAxLTAwLCBoZHJ0eXBlPTB4MDAsIG1mZGV2 PTAKCWNtZHJlZz0weDAwMDcsIHN0YXRyZWc9MHgwMGIwLCBjYWNoZWxuc3o9 MCAoZHdvcmRzKQoJbGF0dGltZXI9MHgwMCAoMCBucyksIG1pbmdudD0weDAy ICg1MDAgbnMpLCBtYXhsYXQ9MHgwNSAoMTI1MCBucykKCWludHBpbj1hLCBp cnE9NQoJcG93ZXJzcGVjIDIgIHN1cHBvcnRzIEQwIEQxIEQyIEQzICBjdXJy ZW50IEQwCnBjaTA6NjowOiByZXByb2Jpbmcgb24gZHJpdmVyIGFkZGVkCnBj aTE6IGRyaXZlciBhZGRlZApwY2kyOiBkcml2ZXIgYWRkZWQKZm91bmQtPgl2 ZW5kb3I9MHgxMGI3LCBkZXY9MHg5MjAxLCByZXZpZD0weDQwCglidXM9Miwg c2xvdD0xLCBmdW5jPTAKCWNsYXNzPTAyLTAwLTAwLCBoZHJ0eXBlPTB4MDAs IG1mZGV2PTAKCWNtZHJlZz0weDAwMDcsIHN0YXRyZWc9MHgwMjEwLCBjYWNo ZWxuc3o9OCAoZHdvcmRzKQoJbGF0dGltZXI9MHgyMCAoOTYwIG5zKSwgbWlu Z250PTB4MGEgKDI1MDAgbnMpLCBtYXhsYXQ9MHgwYSAoMjUwMCBucykKCWlu dHBpbj1hLCBpcnE9NQoJcG93ZXJzcGVjIDIgIHN1cHBvcnRzIEQwIEQxIEQy IEQzICBjdXJyZW50IEQwCnBjaTI6MTowOiByZXByb2Jpbmcgb24gZHJpdmVy IGFkZGVkCnhsMDogPDNDb20gM2M5MjBCLUVNQiBJbnRlZ3JhdGVkIEZhc3Qg RXRoZXJsaW5rIFhMPiBwb3J0IDB4YzAwMC0weGMwN2YgbWVtIDB4YzkwMDAw MDAtMHhjOTAwMDA3ZiBpcnEgNSBhdCBkZXZpY2UgMS4wIG9uIHBjaTIKeGww OiBSZXNlcnZlZCAweDgwIGJ5dGVzIGZvciByaWQgMHgxNCB0eXBlIDMgYXQg MHhjOTAwMDAwMAp4bDA6IHVzaW5nIG1lbW9yeSBtYXBwZWQgSS9PCnhsMDog bWVkaWEgb3B0aW9ucyB3b3JkOiA0MAp4bDA6IGZvdW5kIE1JSS9BVVRPCm1p aWJ1czA6IDxNSUkgYnVzPiBvbiB4bDAKYWNwaHkwOiA8QUMxMDFMIDEwLzEw MCBtZWRpYSBpbnRlcmZhY2U+IG9uIG1paWJ1czAKYWNwaHkwOiAgMTBiYXNl VCwgMTBiYXNlVC1GRFgsIDEwMGJhc2VUWCwgMTAwYmFzZVRYLUZEWCwgYXV0 bwp4bDA6IGJwZiBhdHRhY2hlZAp4bDA6IEV0aGVybmV0IGFkZHJlc3M6IDAw OjI2OjU0OjEzOjQzOjU2CnhsMDogW01QU0FGRV0KcGNpMzogZHJpdmVyIGFk ZGVkCmZvdW5kLT4JdmVuZG9yPTB4MTBkZSwgZGV2PTB4MDExMCwgcmV2aWQ9 MHhiMgoJYnVzPTMsIHNsb3Q9MCwgZnVuYz0wCgljbGFzcz0wMy0wMC0wMCwg aGRydHlwZT0weDAwLCBtZmRldj0wCgljbWRyZWc9MHgwMDA3LCBzdGF0cmVn PTB4MDJiMCwgY2FjaGVsbnN6PTAgKGR3b3JkcykKCWxhdHRpbWVyPTB4MjAg KDk2MCBucyksIG1pbmdudD0weDA1ICgxMjUwIG5zKSwgbWF4bGF0PTB4MDEg KDI1MCBucykKCWludHBpbj1hLCBpcnE9MTEKCXBvd2Vyc3BlYyAyICBzdXBw b3J0cyBEMCBEMyAgY3VycmVudCBEMApwY2kzOjA6MDogcmVwcm9iaW5nIG9u IGRyaXZlciBhZGRlZAp4bDA6IGxpbmsgc3RhdGUgY2hhbmdlZCB0byBET1dO CnhsMDogbGluayBzdGF0ZSBjaGFuZ2VkIHRvIFVQCnBjaTA6IGRyaXZlciBh ZGRlZApmb3VuZC0+CXZlbmRvcj0weDEwZGUsIGRldj0weDAxZWIsIHJldmlk PTB4YzEKCWJ1cz0wLCBzbG90PTAsIGZ1bmM9MQoJY2xhc3M9MDUtMDAtMDAs IGhkcnR5cGU9MHgwMCwgbWZkZXY9MQoJY21kcmVnPTB4MDAwMCwgc3RhdHJl Zz0weDAwMjAsIGNhY2hlbG5zej0wIChkd29yZHMpCglsYXR0aW1lcj0weDAw ICgwIG5zKSwgbWluZ250PTB4MDAgKDAgbnMpLCBtYXhsYXQ9MHgwMCAoMCBu cykKcGNpMDowOjE6IHJlcHJvYmluZyBvbiBkcml2ZXIgYWRkZWQKZm91bmQt Pgl2ZW5kb3I9MHgxMGRlLCBkZXY9MHgwMWVlLCByZXZpZD0weGMxCglidXM9 MCwgc2xvdD0wLCBmdW5jPTIKCWNsYXNzPTA1LTAwLTAwLCBoZHJ0eXBlPTB4 MDAsIG1mZGV2PTEKCWNtZHJlZz0weDAwMDAsIHN0YXRyZWc9MHgwMDIwLCBj YWNoZWxuc3o9MCAoZHdvcmRzKQoJbGF0dGltZXI9MHgwMCAoMCBucyksIG1p bmdudD0weDAwICgwIG5zKSwgbWF4bGF0PTB4MDAgKDAgbnMpCnBjaTA6MDoy OiByZXByb2Jpbmcgb24gZHJpdmVyIGFkZGVkCmZvdW5kLT4JdmVuZG9yPTB4 MTBkZSwgZGV2PTB4MDFlZCwgcmV2aWQ9MHhjMQoJYnVzPTAsIHNsb3Q9MCwg ZnVuYz0zCgljbGFzcz0wNS0wMC0wMCwgaGRydHlwZT0weDAwLCBtZmRldj0x CgljbWRyZWc9MHgwMDAwLCBzdGF0cmVnPTB4MDAyMCwgY2FjaGVsbnN6PTAg KGR3b3JkcykKCWxhdHRpbWVyPTB4MDAgKDAgbnMpLCBtaW5nbnQ9MHgwMCAo MCBucyksIG1heGxhdD0weDAwICgwIG5zKQpwY2kwOjA6MzogcmVwcm9iaW5n IG9uIGRyaXZlciBhZGRlZApmb3VuZC0+CXZlbmRvcj0weDEwZGUsIGRldj0w eDAxZWMsIHJldmlkPTB4YzEKCWJ1cz0wLCBzbG90PTAsIGZ1bmM9NAoJY2xh c3M9MDUtMDAtMDAsIGhkcnR5cGU9MHgwMCwgbWZkZXY9MQoJY21kcmVnPTB4 MDAwMCwgc3RhdHJlZz0weDAwMjAsIGNhY2hlbG5zej0wIChkd29yZHMpCgls YXR0aW1lcj0weDAwICgwIG5zKSwgbWluZ250PTB4MDAgKDAgbnMpLCBtYXhs YXQ9MHgwMCAoMCBucykKcGNpMDowOjQ6IHJlcHJvYmluZyBvbiBkcml2ZXIg YWRkZWQKZm91bmQtPgl2ZW5kb3I9MHgxMGRlLCBkZXY9MHgwMWVmLCByZXZp ZD0weGMxCglidXM9MCwgc2xvdD0wLCBmdW5jPTUKCWNsYXNzPTA1LTAwLTAw LCBoZHJ0eXBlPTB4MDAsIG1mZGV2PTEKCWNtZHJlZz0weDAwMDAsIHN0YXRy ZWc9MHgwMDIwLCBjYWNoZWxuc3o9MCAoZHdvcmRzKQoJbGF0dGltZXI9MHgw MCAoMCBucyksIG1pbmdudD0weDAwICgwIG5zKSwgbWF4bGF0PTB4MDAgKDAg bnMpCnBjaTA6MDo1OiByZXByb2Jpbmcgb24gZHJpdmVyIGFkZGVkCmZvdW5k LT4JdmVuZG9yPTB4MTBkZSwgZGV2PTB4MDA2NCwgcmV2aWQ9MHhhMgoJYnVz PTAsIHNsb3Q9MSwgZnVuYz0xCgljbGFzcz0wYy0wNS0wMCwgaGRydHlwZT0w eDAwLCBtZmRldj0xCgljbWRyZWc9MHgwMDAxLCBzdGF0cmVnPTB4MDBiMCwg Y2FjaGVsbnN6PTAgKGR3b3JkcykKCWxhdHRpbWVyPTB4MDAgKDAgbnMpLCBt aW5nbnQ9MHgwMyAoNzUwIG5zKSwgbWF4bGF0PTB4MDEgKDI1MCBucykKCWlu dHBpbj1hLCBpcnE9NQoJcG93ZXJzcGVjIDIgIHN1cHBvcnRzIEQwIEQzICBj dXJyZW50IEQwCnBjaTA6MToxOiByZXByb2Jpbmcgb24gZHJpdmVyIGFkZGVk CmZvdW5kLT4JdmVuZG9yPTB4MTBkZSwgZGV2PTB4MDA2NiwgcmV2aWQ9MHhh MQoJYnVzPTAsIHNsb3Q9NCwgZnVuYz0wCgljbGFzcz0wMi0wMC0wMCwgaGRy dHlwZT0weDAwLCBtZmRldj0wCgljbWRyZWc9MHgwMDA3LCBzdGF0cmVnPTB4 MDBiMCwgY2FjaGVsbnN6PTAgKGR3b3JkcykKCWxhdHRpbWVyPTB4MDAgKDAg bnMpLCBtaW5nbnQ9MHgwMSAoMjUwIG5zKSwgbWF4bGF0PTB4MTQgKDUwMDAg bnMpCglpbnRwaW49YSwgaXJxPTEyCglwb3dlcnNwZWMgMiAgc3VwcG9ydHMg RDAgRDEgRDIgRDMgIGN1cnJlbnQgRDAKcGNpMDo0OjA6IHJlcHJvYmluZyBv biBkcml2ZXIgYWRkZWQKbnZlMDogPE5WSURJQSBuRm9yY2UgTUNQMiBOZXR3 b3JraW5nIEFkYXB0ZXI+IHBvcnQgMHhlNDAwLTB4ZTQwNyBtZW0gMHhjZTA4 NDAwMC0weGNlMDg0ZmZmIGlycSAxMiBhdCBkZXZpY2UgNC4wIG9uIHBjaTAK bnZlMDogUmVzZXJ2ZWQgMHgxMDAwIGJ5dGVzIGZvciByaWQgMHgxMCB0eXBl IDMgYXQgMHhjZTA4NDAwMApudmUwOiBFdGhlcm5ldCBhZGRyZXNzIDAwOjBj OjZlOmQ5OjZmOmViCm1paWJ1czE6IDxNSUkgYnVzPiBvbiBudmUwCnJscGh5 MDogPFJUTDgyMDFMIDEwLzEwMCBtZWRpYSBpbnRlcmZhY2U+IG9uIG1paWJ1 czEKcmxwaHkwOiAgMTBiYXNlVCwgMTBiYXNlVC1GRFgsIDEwMGJhc2VUWCwg MTAwYmFzZVRYLUZEWCwgYXV0bwpudmUwOiBicGYgYXR0YWNoZWQKbnZlMDog RXRoZXJuZXQgYWRkcmVzczogMDA6MGM6NmU6ZDk6NmY6ZWIKbnZlMDogW0dJ QU5ULUxPQ0tFRF0KZm91bmQtPgl2ZW5kb3I9MHgxMGRlLCBkZXY9MHgwMDZi LCByZXZpZD0weGEyCglidXM9MCwgc2xvdD01LCBmdW5jPTAKCWNsYXNzPTA0 LTAxLTAwLCBoZHJ0eXBlPTB4MDAsIG1mZGV2PTAKCWNtZHJlZz0weDAwMDYs IHN0YXRyZWc9MHgwMGIwLCBjYWNoZWxuc3o9MCAoZHdvcmRzKQoJbGF0dGlt ZXI9MHgwMCAoMCBucyksIG1pbmdudD0weDAxICgyNTAgbnMpLCBtYXhsYXQ9 MHgwYyAoMzAwMCBucykKCWludHBpbj1hLCBpcnE9MTIKCXBvd2Vyc3BlYyAy ICBzdXBwb3J0cyBEMCBEMSBEMiBEMyAgY3VycmVudCBEMApwY2kwOjU6MDog cmVwcm9iaW5nIG9uIGRyaXZlciBhZGRlZApmb3VuZC0+CXZlbmRvcj0weDEw ZGUsIGRldj0weDAwNmEsIHJldmlkPTB4YTEKCWJ1cz0wLCBzbG90PTYsIGZ1 bmM9MAoJY2xhc3M9MDQtMDEtMDAsIGhkcnR5cGU9MHgwMCwgbWZkZXY9MAoJ Y21kcmVnPTB4MDAwNywgc3RhdHJlZz0weDAwYjAsIGNhY2hlbG5zej0wIChk d29yZHMpCglsYXR0aW1lcj0weDAwICgwIG5zKSwgbWluZ250PTB4MDIgKDUw MCBucyksIG1heGxhdD0weDA1ICgxMjUwIG5zKQoJaW50cGluPWEsIGlycT01 Cglwb3dlcnNwZWMgMiAgc3VwcG9ydHMgRDAgRDEgRDIgRDMgIGN1cnJlbnQg RDAKcGNpMDo2OjA6IHJlcHJvYmluZyBvbiBkcml2ZXIgYWRkZWQKcGNpMTog ZHJpdmVyIGFkZGVkCnBjaTI6IGRyaXZlciBhZGRlZApwY2kzOiBkcml2ZXIg YWRkZWQKZm91bmQtPgl2ZW5kb3I9MHgxMGRlLCBkZXY9MHgwMTEwLCByZXZp ZD0weGIyCglidXM9Mywgc2xvdD0wLCBmdW5jPTAKCWNsYXNzPTAzLTAwLTAw LCBoZHJ0eXBlPTB4MDAsIG1mZGV2PTAKCWNtZHJlZz0weDAwMDcsIHN0YXRy ZWc9MHgwMmIwLCBjYWNoZWxuc3o9MCAoZHdvcmRzKQoJbGF0dGltZXI9MHgy MCAoOTYwIG5zKSwgbWluZ250PTB4MDUgKDEyNTAgbnMpLCBtYXhsYXQ9MHgw MSAoMjUwIG5zKQoJaW50cGluPWEsIGlycT0xMQoJcG93ZXJzcGVjIDIgIHN1 cHBvcnRzIEQwIEQzICBjdXJyZW50IEQwCnBjaTM6MDowOiByZXByb2Jpbmcg b24gZHJpdmVyIGFkZGVkCm52ZTA6IGxpbmsgc3RhdGUgY2hhbmdlZCB0byBE T1dOCnR1bjA6IGJwZiBhdHRhY2hlZApXQVJOSU5HOiBhdHRlbXB0IHRvIG5l dF9hZGRfZG9tYWluKG5ldGdyYXBoKSBhZnRlciBkb21haW5maW5hbGl6ZSgp CmF0YTI6IHJlaW5pdGluZyBjaGFubmVsIC4uCmF0YTI6IFNBVEEgY29ubmVj dCByZWFkeSB0aW1lPTBtcwphdGEyOiBzYXRhX2Nvbm5lY3QgZGV2aWNlcz0w eDE8QVRBX01BU1RFUj4KYWQ0OiByZXE9MHhjNDEyMzdkMCBTRVRGRUFUVVJF UyBTRVQgVFJBTlNGRVIgTU9ERSBzZW1hcGhvcmUgdGltZW91dCAhISBEQU5H RVIgV2lsbCBSb2JpbnNvbiAhIQphZDQ6IHJlcT0weGM0MTIzN2QwIFNFVEZF QVRVUkVTIFNFVCBUUkFOU0ZFUiBNT0RFIHNlbWFwaG9yZSB0aW1lb3V0ICEh IERBTkdFUiBXaWxsIFJvYmluc29uICEhCg== --0-1296904255-1132519784=:47599-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 20:50:30 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D709A16A4D4; Sun, 20 Nov 2005 20:50:30 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn.pobox.com (thorn.pobox.com [208.210.124.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7330743D46; Sun, 20 Nov 2005 20:50:30 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn (localhost [127.0.0.1]) by thorn.pobox.com (Postfix) with ESMTP id 7712A2BB; Sun, 20 Nov 2005 15:50:51 -0500 (EST) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thorn.sasl.smtp.pobox.com (Postfix) with ESMTP id 25354F27; Sun, 20 Nov 2005 15:50:50 -0500 (EST) Received: from brian by mappit.local.linnet.org with local (Exim 4.54 (FreeBSD)) id 1Edw8o-00059W-H1; Sun, 20 Nov 2005 20:50:26 +0000 Date: Sun, 20 Nov 2005 20:50:26 +0000 From: Brian Candler To: Tim Kientzle Message-ID: <20051120205026.GA19791@uk.tiscali.com> References: <20051116161540.GB4383@uk.tiscali.com> <437F7E22.5050800@freebsd.org> <20051120192914.GC19572@uk.tiscali.com> <4380DC1A.9030201@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4380DC1A.9030201@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: Order of files with 'cp' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 20:50:31 -0000 On Sun, Nov 20, 2005 at 12:27:06PM -0800, Tim Kientzle wrote: > >Erm, but that just undoes the reason for calling fts_open with mastercmp in > >the first place, which is to get it to pick files before directories (or > >vice versa, as its behaviour seems to be) as an 'optimisation'. > > Why is that an optimization? I'm only regurgitating what is written in /usr/src/bin/cp/cp.c: /* * mastercmp -- * The comparison function for the copy order. The order is to copy * non-directory files before directory files. The reason for this * is because files tend to be in the same cylinder group as their * parent directory, whereas directories tend not to be. Copying the * files first reduces seeking. */ > I thought the whole point of this thread was that users > expect utilities to process the command-line arguments > in the order they're given. That wasn't the point I made at the start of the thread - somebody else brought up POLA - although I would be happy for cp to process command-line arguments strictly in the order they are given (in which case, you just replace mastercmp with NULL when calling fts_open) I suggested that if the above 'optimisation' makes sense, it should still be possible to make cp copy arguments in the order given if they are all files or all directories. I gave some suggested ways of achieving this. Regards, Brian. From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 20:56:10 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43A3716A41F; Sun, 20 Nov 2005 20:56:10 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from orb.pobox.com (orb.pobox.com [207.8.226.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD15B43D46; Sun, 20 Nov 2005 20:56:09 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from orb (localhost [127.0.0.1]) by orb.pobox.com (Postfix) with ESMTP id 0E84F5AD; Sun, 20 Nov 2005 15:56:31 -0500 (EST) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by orb.sasl.smtp.pobox.com (Postfix) with ESMTP id C75348A; Sun, 20 Nov 2005 15:56:28 -0500 (EST) Received: from brian by mappit.local.linnet.org with local (Exim 4.54 (FreeBSD)) id 1EdwEH-00059w-Al; Sun, 20 Nov 2005 20:56:05 +0000 Date: Sun, 20 Nov 2005 20:56:05 +0000 From: Brian Candler To: Giorgos Keramidas Message-ID: <20051120205605.GB19791@uk.tiscali.com> References: <20051116161540.GB4383@uk.tiscali.com> <437F7E22.5050800@freebsd.org> <20051120193416.GB1599@flame.pc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051120193416.GB1599@flame.pc> User-Agent: Mutt/1.4.2.1i Cc: Tim Kientzle , freebsd-current@freebsd.org Subject: Re: Order of files with 'cp' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 20:56:10 -0000 On Sun, Nov 20, 2005 at 09:34:16PM +0200, Giorgos Keramidas wrote: > qsort() can be 'stable' enough for our purposes if the comparison > function uses something like this: > > int > compare_int32_t(void *pa, void *pb) > { > int32_t a, b; > > assert(pa != NULL && pb != NULL); > a = *((int32_t *)pa); > b = *((int32_t *)pb); > > if (a < b && pa != pb) > return 1; > if (a > b && pa != pb) > return -1; > return 0; > } Care to explain?? For one thing, I don't think qsort() will ever call its comparison function with two equal pointers, as that would be a point(er)less thing to do. Therefore, I can't see why you are testing for pa != pb, since this condition will always be true. (Also, a < b could never be true if pa == pb). Secondly, mastercmp() doesn't compare integers, it compares FTS structures. The comparison function just compares whether one item is a directory and the other a file. How would you have mastercmp() work instead? Regards, Brian. From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 23:12:32 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E87F516A41F for ; Sun, 20 Nov 2005 23:12:32 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4281D43D45 for ; Sun, 20 Nov 2005 23:12:31 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by freebsd.czest.pl (8.12.10/8.12.9) with ESMTP id jAKNDrPx087858 for ; Sun, 20 Nov 2005 23:13:53 GMT (envelope-from dunstan@freebsd.czest.pl) Received: (from dunstan@localhost) by freebsd.czest.pl (8.13.4/8.12.9/Submit) id jAKNDrRP087857 for freebsd-current@freebsd.org; Sun, 20 Nov 2005 23:13:53 GMT (envelope-from dunstan) Date: Sun, 20 Nov 2005 23:13:52 +0000 From: "Wojciech A. Koszek" To: freebsd-current@freebsd.org Message-ID: <20051120231352.GA87809@freebsd.czest.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: [PANIC] lockmgr: locking against myself in ext2fs code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 23:12:33 -0000 Hello, I get easily repeatable problem on ext2fs on -CURRENT (AFAIR, this worked for earlier versions). I use mke2fs(8) from ports/sysutils/e2fsprogs in order to create filesystem. Simple how to repeat: mdconfig -a -t malloc -s 10m mke2fs /dev/md0 mount /dev/md0 /mnt cd /mnt touch 1 2 3 4 5 mkdir 6 mv * 6/ I've obtained trace dump: http://freebsd.czest.pl/dunstan/FreeBSD/ext2fs.log -- * Wojciech A. Koszek && dunstan@FreeBSD.czest.pl From owner-freebsd-current@FreeBSD.ORG Sun Nov 20 23:41:44 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6AFFE16A41F for ; Sun, 20 Nov 2005 23:41:44 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA66B43D46 for ; Sun, 20 Nov 2005 23:41:43 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.25]) (authenticated bits=0) by cain.gsoft.com.au (8.13.4/8.13.4) with ESMTP id jAKNfT7g014411 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 21 Nov 2005 10:11:30 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Mon, 21 Nov 2005 10:11:28 +1030 User-Agent: KMail/1.8.2 References: <20051120172755.GA85641@freebsd.czest.pl> <84dead720511200943ua2cf8b8y49bff0dcf3e2fa63@mail.gmail.com> <20051120183037.GA85917@freebsd.czest.pl> In-Reply-To: <20051120183037.GA85917@freebsd.czest.pl> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2616693.S0zNMJMkYg"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200511211011.29745.doconnor@gsoft.com.au> X-Spam-Score: -2.82 () ALL_TRUSTED X-Scanned-By: MIMEDefang 2.51 on 203.31.81.10 Cc: "Wojciech A. Koszek" Subject: Re: [PATCH] Specifying alternative file for devd(8) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 20 Nov 2005 23:41:44 -0000 --nextPart2616693.S0zNMJMkYg Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Mon, 21 Nov 2005 05:00, Wojciech A. Koszek wrote: > > You should probably also mention in the manual page that > > only one (the last) '-f' option has an effect. > > Every options has an effect and (somehow) modifies application behavour. I > don't see a reason why to mention it, since it's already explained. If you > think it's really needed, let me know, I'll make another update. He means that you should mention that multiple -f options are not additive. ie you can't do devd -f config1 -f config2 and have devd "merge" the 2 configuration files. =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 --nextPart2616693.S0zNMJMkYg Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDgQmp5ZPcIHs/zowRAspJAKCbMqSjAzW5xJTmnUKQMeKoHmhs0wCeJVVi MkL2HZpwSMeqF0DthlC2qT4= =pVhU -----END PGP SIGNATURE----- --nextPart2616693.S0zNMJMkYg-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 00:33:12 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7218A16A41F for ; Mon, 21 Nov 2005 00:33:12 +0000 (GMT) (envelope-from eculp@bafirst.com) Received: from bafirst.com (72-12-2-214.wan.networktel.net [72.12.2.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 906FE43D46 for ; Mon, 21 Nov 2005 00:33:10 +0000 (GMT) (envelope-from eculp@bafirst.com) Received: from localhost (localhost [127.0.0.1]) (uid 80) by bafirst.com with local; Sun, 20 Nov 2005 18:33:09 -0600 id 0009580F.438115C5.000017CF Received: from local1 (local1 [192.168.1.1]) by mail.bafirst.com (Horde MIME library) with HTTP; Sun, 20 Nov 2005 18:33:09 -0600 Message-ID: <20051120183309.ysgk624asksckwow@mail.bafirst.com> Date: Sun, 20 Nov 2005 18:33:09 -0600 From: eculp@bafirst.com To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.1-cvs Cc: Subject: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 00:33:12 -0000 Yesterday I did the full cvsup, build and install world, kernel, mergemaster, etc. on a 6.0-stable MP (2) Dell restarted and noticed on this mornings security run that it is only seeing 3G of the 4G that the box actually has (confirmed by the bios and physically). This is not something new, I saw it on the initial install but it slipped my mind because I had a non-technical doing the initial install over skype. If I had been there I would probably done a bios upgrade to see if that was the problem, but I'm in another country. kernel log messages: +++ /tmp/security.mNF3wyIb Sun Nov 20 03:07:10 2005 +FreeBSD 6.0-STABLE #65: Sat Nov 19 03:58:47 CST 2005 +ACPI APIC Table: +avail memory = 3151134720 (3005 MB) I've never seen this memory issue for years. Could there be a solution through configuration of the kernel, sysctl, etc.? Any and all suggestions appreciated. Thanks, ed P.S. A copy of the dmesg is at http://unixmania.com/dmesg_20051120.txt don't have a verbose one.:( From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 00:47:51 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30E1A16A41F for ; Mon, 21 Nov 2005 00:47:51 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE7B343D45 for ; Mon, 21 Nov 2005 00:47:50 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id C6D751A3C19; Sun, 20 Nov 2005 16:47:50 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id BDE7351390; Sun, 20 Nov 2005 19:47:49 -0500 (EST) Date: Sun, 20 Nov 2005 19:47:49 -0500 From: Kris Kennaway To: eculp@bafirst.com Message-ID: <20051121004749.GA39061@xor.obsecurity.org> References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline In-Reply-To: <20051120183309.ysgk624asksckwow@mail.bafirst.com> User-Agent: Mutt/1.4.2.1i Cc: current@freebsd.org Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 00:47:51 -0000 --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 20, 2005 at 06:33:09PM -0600, eculp@bafirst.com wrote: > Yesterday I did the full cvsup, build and install world, kernel,=20 > mergemaster, etc. on a 6.0-stable MP (2) Dell restarted and noticed on=20 > this mornings security run that it is only seeing 3G of the 4G that the= =20 > box actually has (confirmed by the bios and physically). This is not=20 > something new, I saw it on the initial install but it slipped my mind=20 > because I had a non-technical doing the initial install over skype. If= =20 > I had been there I would probably done a bios upgrade to see if that=20 > was the problem, but I'm in another country. This is a FAQ. Kris --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDgRk1Wry0BWjoQKURAmOtAKC7wIy0buKY0/t64MAGyXoQrdZOMwCg6sxZ U4fAtsULeTlpI/ozbg0bqx8= =wtVm -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 01:45:12 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13FA716A420 for ; Mon, 21 Nov 2005 01:45:12 +0000 (GMT) (envelope-from thomas@FreeBSD.ORG) Received: from melamine.cuivre.fr.eu.org (melusine.cuivre.fr.eu.org [82.225.155.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 806E543D55 for ; Mon, 21 Nov 2005 01:45:11 +0000 (GMT) (envelope-from thomas@FreeBSD.ORG) Received: by melamine.cuivre.fr.eu.org (Postfix, from userid 1000) id B22FD5C0E4; Mon, 21 Nov 2005 02:45:04 +0100 (CET) Date: Mon, 21 Nov 2005 02:45:04 +0100 From: Thomas Quinot To: current@freebsd.org Message-ID: <20051121014504.GA1236@melamine.cuivre.fr.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-message-flag: WARNING! Using Outlook can damage your computer. User-Agent: Mutt/1.5.9i Cc: Subject: 6.0-BETA5 random freeze with rtc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 01:45:12 -0000 On a new Dell Precision 380 box running 6.05-BETA5, I've seen random freezes (apparently not related to specific activities running on the machine, which has web and mail servers and also runs an X server) a few days apart. On the last two instances, the last message recorded in the logs was the same: Nov 21 02:11:22 melamine kernel: rtc: 1000 > kern.hz: Timing will be inaccurate, please increase hz. and this messages does not occur at any other time, so I suspect it's related to the freezes I saw. I might have been running mplayer shortly before the freeze. Could this be related to PR 71536? (i.e. could the rtc bug cause a freeze, and not only an annoying console message?) Thomas. From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 01:55:47 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D92116A41F for ; Mon, 21 Nov 2005 01:55:47 +0000 (GMT) (envelope-from thomas@FreeBSD.ORG) Received: from melamine.cuivre.fr.eu.org (melusine.cuivre.fr.eu.org [82.225.155.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E76C43D46 for ; Mon, 21 Nov 2005 01:55:46 +0000 (GMT) (envelope-from thomas@FreeBSD.ORG) Received: by melamine.cuivre.fr.eu.org (Postfix, from userid 1000) id 704FF5C0E4; Mon, 21 Nov 2005 02:55:40 +0100 (CET) Date: Mon, 21 Nov 2005 02:55:40 +0100 From: Thomas Quinot To: current@freebsd.org Message-ID: <20051121015540.GA1484@melamine.cuivre.fr.eu.org> References: <20051121014504.GA1236@melamine.cuivre.fr.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051121014504.GA1236@melamine.cuivre.fr.eu.org> X-message-flag: WARNING! Using Outlook can damage your computer. User-Agent: Mutt/1.5.9i Cc: Subject: Re: 6.0-BETA5 random freeze with rtc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 01:55:47 -0000 * Thomas Quinot, 2005-11-21 : > On a new Dell Precision 380 box running 6.05-BETA5, I've seen random > freezes (apparently not related to specific activities running on the > machine, which has web and mail servers and also runs an X server) a few > days apart. dmesg output: 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-BETA5 #0: Mon Oct 10 00:16:00 CEST 2005 root@melamine.cuivre.fr.eu.org:/usr/obj/usr/src/sys/NOEHCI Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (2992.59-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf43 Stepping = 3 Features=0xbfebfbff Features2=0x649d> AMD Features=0x20100000 Hyperthreading: 2 logical CPUs real memory = 1072209920 (1022 MB) avail memory = 1040347136 (992 MB) ACPI APIC Table: ioapic0: Changing APIC ID to 8 ioapic0 irqs 0-23 on motherboard lapic0: Forcing LINT1 to edge trigger npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 11 on acpi0 pci_link1: irq 10 on acpi0 pci_link2: irq 3 on acpi0 pci_link3: on acpi0 pci_link4: irq 5 on acpi0 pci_link5: irq 9 on acpi0 pci_link6: irq 5 on acpi0 pci_link7: irq 10 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pci1: at device 0.1 (no driver attached) pci0: at device 27.0 (no driver attached) pcib2: irq 16 at device 28.0 on pci0 pci2: on pcib2 pcib3: irq 16 at device 28.4 on pci0 pci3: on pcib3 pcib4: irq 17 at device 28.5 on pci0 pci4: on pcib4 bge0: mem 0xefbf0000-0xefbfffff irq 17 at device 0.0 on pci4 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:12:3f:75:c0:00 uhci0: port 0xff80-0xff9f irq 21 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 0xff60-0xff7f irq 22 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 0xff40-0xff5f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xff20-0xff3f irq 23 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered pci0: at device 29.7 (no driver attached) pcib5: at device 30.0 on pci0 pci5: on pcib5 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf irq 16 at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfea0-0xfeaf mem 0xefffbc00-0xefffbfff irq 20 at device 31.2 on pci0 ata2: on atapci1 ata3: on atapci1 ata4: on atapci1 ata5: on atapci1 pci0: at device 31.3 (no driver attached) fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: port 0x378-0x37f,0x778-0x77f irq 7 drq 1 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 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcafff,0xcb000-0xccfff,0xcd000-0xcffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ums0: Logitech Optical USB Mouse, rev 2.00/3.40, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. ukbd0: Dell Dell USB Keyboard, rev 1.10/2.00, addr 3, iclass 3/1 kbd0 at ukbd0 Timecounter "TSC" frequency 2992593382 Hz quality 800 Timecounters tick every 1.000 msec acd0: DVDR at ata0-master UDMA33 ad4: 152587MB at ata2-master SATA150 ad6: 152587MB at ata3-master SATA150 ad8: 152587MB at ata4-master SATA150 cd0 at ata0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 33.000MB/s transfers cd0: cd present [282445 x 2048 byte records] GEOM_MIRROR: Device mirror0 created (id=1042513580). GEOM_MIRROR: Device mirror0: provider ad4s1 detected. GEOM_STRIPE: Device stripe0 created (id=1293460592). GEOM_STRIPE: Disk ad4s2 attached to stripe0. GEOM_MIRROR: Device mirror0: provider ad6s1 detected. GEOM_MIRROR: Device mirror0: provider ad6s1 activated. GEOM_MIRROR: Device mirror0: provider ad4s1 activated. GEOM_MIRROR: Device mirror0: provider mirror/mirror0 launched. GEOM_STRIPE: Disk ad6s2 attached to stripe0. GEOM_STRIPE: Device stripe0 activated. Trying to mount root from ufs:/dev/mirror/mirror0a WARNING: / was not properly dismounted /: mount pending error: blocks 4 files 1 WARNING: /usr2 was not properly dismounted WARNING: /data was not properly dismounted From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 02:02:34 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2926016A41F for ; Mon, 21 Nov 2005 02:02:34 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from smtp103.rog.mail.re2.yahoo.com (smtp103.rog.mail.re2.yahoo.com [206.190.36.81]) by mx1.FreeBSD.org (Postfix) with SMTP id 994A243D46 for ; Mon, 21 Nov 2005 02:02:33 +0000 (GMT) (envelope-from mikej@rogers.com) Received: (qmail 70022 invoked from network); 21 Nov 2005 02:02:32 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=5pmk28nzEdN1R3sPkqNuWf95mn5sM8AdXXohiRW8KS5goBEvXrLFXXqneHwh6Q8mqhFI6Fu/4YmVeXtK0FbdYEFxDEOv8O6qJ3fDET+0w+DxY9mwWWFTDWYNrRiIXq5oMAvTplLr0WMW4BQl/nKhx/hYQrBzLnv/bp+QgbTxR5M= ; Received: from unknown (HELO ?172.16.0.199?) (mikej@rogers.com@70.31.50.81 with plain) by smtp103.rog.mail.re2.yahoo.com with SMTP; 21 Nov 2005 02:02:32 -0000 Message-ID: <43812AC7.3020506@rogers.com> Date: Sun, 20 Nov 2005 21:02:47 -0500 From: Mike Jakubik User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: Kris Kennaway References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> <20051121004749.GA39061@xor.obsecurity.org> In-Reply-To: <20051121004749.GA39061@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 02:02:34 -0000 Kris Kennaway wrote: > This is a FAQ. > > Kris > Really? Where is it mentioned in the FAQ? I know this has been discussed on the mail lists, but not everyone reads them religiously. http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/ From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 02:08:25 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10F8D16A421 for ; Mon, 21 Nov 2005 02:08:25 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id EABDC43D6B for ; Mon, 21 Nov 2005 02:08:18 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id C22D81A3C19; Sun, 20 Nov 2005 18:08:18 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6246A51469; Sun, 20 Nov 2005 21:08:17 -0500 (EST) Date: Sun, 20 Nov 2005 21:08:16 -0500 From: Kris Kennaway To: Mike Jakubik Message-ID: <20051121020816.GA19252@xor.obsecurity.org> References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> <20051121004749.GA39061@xor.obsecurity.org> <43812AC7.3020506@rogers.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VS++wcV0S1rZb1Fb" Content-Disposition: inline In-Reply-To: <43812AC7.3020506@rogers.com> User-Agent: Mutt/1.4.2.1i Cc: current@freebsd.org, Kris Kennaway Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 02:08:25 -0000 --VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 20, 2005 at 09:02:47PM -0500, Mike Jakubik wrote: > Kris Kennaway wrote: > >This is a FAQ. > > > >Kris > > =20 > Really? Where is it mentioned in the FAQ? I know this has been discussed= =20 > on the mail lists, but not everyone reads them religiously. >=20 > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/ That document isn't an exclusive list of questions that are asked frequently :-) I don't know off-hand if it's in there, but the OP can also search the mailing list archives for the answer. Kris --VS++wcV0S1rZb1Fb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDgSwOWry0BWjoQKURAqSiAJ9E8KFv62KRjJQAyq65SUKNZODfBQCfdLRF J7Hd3pL9C4+rYK0HAT5U7lE= =xePP -----END PGP SIGNATURE----- --VS++wcV0S1rZb1Fb-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 02:43:34 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36BD016A41F for ; Mon, 21 Nov 2005 02:43:34 +0000 (GMT) (envelope-from chad@shire.net) Received: from hobbiton.shire.net (mail.freestylefund.com [166.70.252.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF30C43D46 for ; Mon, 21 Nov 2005 02:43:33 +0000 (GMT) (envelope-from chad@shire.net) Received: from [67.161.222.227] (helo=[192.168.99.68]) by hobbiton.shire.net with esmtpa (Exim 4.51) id 1Ee1eX-000HHF-1U; Sun, 20 Nov 2005 19:43:33 -0700 In-Reply-To: <20051121020816.GA19252@xor.obsecurity.org> References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> <20051121004749.GA39061@xor.obsecurity.org> <43812AC7.3020506@rogers.com> <20051121020816.GA19252@xor.obsecurity.org> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: "Chad Leigh -- Shire.Net LLC" Date: Sun, 20 Nov 2005 19:43:32 -0700 To: Kris Kennaway X-Mailer: Apple Mail (2.746.2) X-SA-Exim-Connect-IP: 67.161.222.227 X-SA-Exim-Mail-From: chad@shire.net X-SA-Exim-Scanned: No (on hobbiton.shire.net); SAEximRunCond expanded to false Cc: current@freebsd.org Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 02:43:34 -0000 On Nov 20, 2005, at 7:08 PM, Kris Kennaway wrote: > On Sun, Nov 20, 2005 at 09:02:47PM -0500, Mike Jakubik wrote: >> Kris Kennaway wrote: >>> This is a FAQ. >>> >>> Kris >>> >> Really? Where is it mentioned in the FAQ? I know this has been >> discussed >> on the mail lists, but not everyone reads them religiously. >> >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/ > > That document isn't an exclusive list of questions that are asked > frequently :-) I don't know off-hand if it's in there, but the OP can > also search the mailing list archives for the answer. I assume you are talking about the "phenomenon" of RAM "missing" due to PCI and other I/O mapping into the 4GB address space? What struck me about the OP is that the amount of RAM "missing" is more than I have ever seen due to this. My systems are usually 3.4-3.6GB of RAM with 4GB installed, not 2.86GB (3005MB)... So are we sure that the PCI space mapping is the problem? Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad@shire.net From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 01:03:42 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99A0F16A41F for ; Mon, 21 Nov 2005 01:03:42 +0000 (GMT) (envelope-from mi@aldan.algebra.com) Received: from aldan.algebra.com (aldan.algebra.com [216.254.65.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 224A543D4C for ; Mon, 21 Nov 2005 01:03:41 +0000 (GMT) (envelope-from mi@aldan.algebra.com) Received: from aldan.algebra.com (blue [127.0.0.1]) by aldan.algebra.com (8.13.4/8.13.4) with ESMTP id jAL13eNj000857 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 20 Nov 2005 20:03:40 -0500 (EST) (envelope-from mi@aldan.algebra.com) Received: (from mi@localhost) by aldan.algebra.com (8.13.4/8.13.4/Submit) id jAL13e6u000856; Sun, 20 Nov 2005 20:03:40 -0500 (EST) (envelope-from mi) From: "Mikhail T." Message-Id: <200511210103.jAL13e6u000856@aldan.algebra.com> To: current@FreeBSD.org Date: Sun, 20 Nov 2005 20:03:40 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2005 01:03:42 -0000 Hello! I just had a nasty crash, while trying to start a freshly built abiword. Here is my kgdb poking around. The system runs 6.0-STABLE from Nov 13. -mi [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 "amd64-marcel-freebsd". Unread portion of the kernel message buffer: Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x8:0xffffffff803c2236 stack pointer = 0x10:0xffffffffb80075f0 frame pointer = 0x10:0xffffff006ca43000 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 38790 (AbiWord-2.4) trap number = 9 panic: general protection fault cpuid = 0 Uptime: 7d8h13m49s Dumping 4095 MB (3 chunks) chunk 0: 1MB (156 pages) ... ok chunk 1: 2559MB (655088 pages) 2543 2527 2511 2495 2479 2463 2447 2431 2415 2399 2383 2367 2351 2335 2319 2303 2287 2271 2255 2239 2223 2207 2191 2175 2159 2143 2127 2111 2095 2079 2063 2047 2031 2015 1999 1983 1967 1951 1935 1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 ... ok chunk 2: 1536MB (393216 pages) 1521 1505 1489 1473 1457 1441 1425 1409 1393 1377 1361 1345 1329 1313 1297 1281 1265 1249 1233 1217 1201 1185 1169 1153 1137 1121 1105 1089 1073 1057 1041 1025 1009 993 977 961 945 929 913 897 881 865 849 833 817 801 785 769 753 737 721 705 689 673 657 641 625 609 593 577 561 545 529 513 497 481 465 449 433 417 401 385 369 353 337 321 305 289 273 257 241 225 209 193 177 161 145 129 113 97 81 65 49 33 17 1 #0 doadump () at pcpu.h:172 172 __asm __volatile("movq %%gs:0,%0" : "=r" (td)); (kgdb) where #0 doadump () at pcpu.h:172 #1 0x0000000000000004 in ?? () #2 0xffffffff802ac0f7 in boot (howto=260) at ../../../kern/kern_shutdown.c:399 #3 0xffffffff802ac791 in panic (fmt=0xffffff00392a24c0 "Ày\235@") at ../../../kern/kern_shutdown.c:555 #4 0xffffffff804047d7 in trap_fatal (frame=0xffffff00392a24c0, eva=18446742975281985984) at ../../../amd64/amd64/trap.c:655 #5 0xffffffff80404c82 in trap (frame= {tf_rdi = 2272, tf_rsi = -1093962765824, tf_rdx = 207, tf_rcx = 0, tf_r8 = 463, tf_r9 = 6714722, tf_rax = 0, tf_rbx = -1099499642880, tf_rbp = -1097688928256, tf_r10 = 7454421654995730432, tf_r11 = 0, tf_r12 = 512, tf_r13 = 463, tf_r14 = -1099499642880, tf_r15 = -1095121764976, tf_trapno = 9, tf_addr = 0, tf_flags = -1095121764976, tf_err = 0, tf_rip = -2143542730, tf_cs = 8, tf_rflags = 66134, tf_rsp = -1207929344, tf_ss = 16}) at ../../../amd64/amd64/trap.c:467 #6 0xffffffff803f217b in calltrap () at ../../../amd64/amd64/exception.S:168 #7 0xffffffff803c2236 in ufsdirhash_lookup (ip=0xffffff005dc1e3c0, name=0xffffff0089c81c20 "system.profile-uk", namelen=17, offp=0xffffff005dc1e42c, bpp=0xffffffffb80076d0, prevoffp=0x0) at ../../../ufs/ufs/ufs_dirhash.c:394 #8 0xffffffff803c3de9 in ufs_lookup (ap=0xffffffffb80077c0) at ../../../ufs/ufs/ufs_lookup.c:209 #9 0xffffffff80446c6a in VOP_CACHEDLOOKUP_APV (vop=0x0, a=0xffffff014abcea00) at vnode_if.c:150 #10 0xffffffff80307dd5 in vfs_cache_lookup (ap=0x8e0) at vnode_if.h:82 #11 0xffffffff804479ad in VOP_LOOKUP_APV (vop=0xffffffff805e4240, a=0xffffffffb80078a0) at vnode_if.c:99 #12 0xffffffff8030c3c9 in lookup (ndp=0xffffffffb8007a20) at vnode_if.h:56 #13 0xffffffff8030cec5 in namei (ndp=0xffffffffb8007a20) at ../../../kern/vfs_lookup.c:203 #14 0xffffffff8031c894 in kern_stat (td=0xffffff00392a24c0, path=0xffffff014abcea00 "", pathseg=207, sbp=0xffffffffb8007af0) at ../../../kern/vfs_syscalls.c:2053 #15 0xffffffff8031ca17 in stat (td=0x8e0, uap=0xffffffffb8007bc0) at ../../../kern/vfs_syscalls.c:2038 #16 0xffffffff80405631 in syscall (frame= {tf_rdi = 12979200, tf_rsi = 140737488346848, tf_rdx = 13036064, tf_rcx = 12979200, tf_r8 = -56960, tf_r9 = 0, tf_rax = 188, tf_rbx = 140737488347040, tf_rbp = 0, tf_r10 = 0, tf_r11 = 0, tf_r12 = 13036192, tf_r13 = 0, tf_r14 = 77, tf_r15 = 12971008, tf_trapno = 12, tf_addr = 13148160, tf_flags = 0, tf_err = 2, tf_rip = 34421415036, tf_cs = 43, tf_rflags = 514, tf_rsp = 140737488346840, tf_ss = 35}) at ../../../amd64/amd64/trap.c:787 #17 0xffffffff803f2318 in Xfast_syscall () at ../../../amd64/amd64/exception.S:270 #18 0x0000000803ad1c7c in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) frame 7 #7 0xffffffff803c2236 in ufsdirhash_lookup (ip=0xffffff005dc1e3c0, name=0xffffff0089c81c20 "system.profile-uk", namelen=17, offp=0xffffff005dc1e42c, bpp=0xffffffffb80076d0, prevoffp=0x0) at ../../../ufs/ufs/ufs_dirhash.c:394 394 for (i = slot; (offset = DH_ENTRY(dh, i)) != DIRHASH_EMPTY; (kgdb) p dh $1 = (struct dirhash *) 0xffffff006ca43000 (kgdb) p *dh $2 = {dh_mtx = {mtx_object = {lo_class = 0xffffffff805caad0, lo_name = 0xffffffff8048b107 "dirhash", lo_type = 0xffffffff8048b107 "dirhash", lo_flags = 196608, lo_list = { tqe_next = 0x0, tqe_prev = 0x0}, lo_witness = 0x0}, mtx_lock = 18446742975156987072, mtx_recurse = 0}, dh_hash = 0xffffff014abcea00, dh_narrays = 2, dh_hlen = 512, dh_hused = 75, dh_blkfree = 0xffffff0000c747b0 "\001\002\003\001Hcp_time", dh_nblk = 8, dh_dirblks = 5, dh_firstfree = {-1, 0, 1, 2, -1 , 4}, dh_seqopt = 1, dh_seqoff = 2272, dh_score = 64, dh_onlist = 1, dh_list = { tqe_next = 0xffffff0087091400, tqe_prev = 0xffffff00548a8590}} (kgdb) p i $3 = 0 (kgdb) p slot $4 = 463 (kgdb) quit From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 02:53:42 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E454416A41F for ; Mon, 21 Nov 2005 02:53:41 +0000 (GMT) (envelope-from ps@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id B352343D45 for ; Mon, 21 Nov 2005 02:53:41 +0000 (GMT) (envelope-from ps@freebsd.org) Received: from [192.168.1.88] (64-142-76-135.dsl.static.sonic.net [64.142.76.135]) by elvis.mu.org (Postfix) with ESMTP id 8AAB01A3C19; Sun, 20 Nov 2005 18:53:41 -0800 (PST) Message-ID: <438136B5.9030506@freebsd.org> Date: Sun, 20 Nov 2005 18:53:41 -0800 From: Paul Saab User-Agent: Thunderbird 1.5 (Macintosh/20051025) MIME-Version: 1.0 To: "Chad Leigh -- Shire.Net LLC" References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> <20051121004749.GA39061@xor.obsecurity.org> <43812AC7.3020506@rogers.com> <20051121020816.GA19252@xor.obsecurity.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org, Kris Kennaway Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 02:53:42 -0000 Chad Leigh -- Shire.Net LLC wrote: > I assume you are talking about the "phenomenon" of RAM "missing" due > to PCI and other I/O mapping into the 4GB address space? What struck > me about the OP is that the amount of RAM "missing" is more than I > have ever seen due to this. My systems are usually 3.4-3.6GB of RAM > with 4GB installed, not 2.86GB (3005MB)... So are we sure that the > PCI space mapping is the problem? > Enable PAE and you'll get all your ram. From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 02:57:03 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E13716A420; Mon, 21 Nov 2005 02:57:03 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id B410843D45; Mon, 21 Nov 2005 02:57:02 +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 jAL2v0ET012598; Sun, 20 Nov 2005 21:57:01 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: <20051120192914.GC19572@uk.tiscali.com> References: <20051116161540.GB4383@uk.tiscali.com> <437F7E22.5050800@freebsd.org> <20051120192914.GC19572@uk.tiscali.com> Date: Sun, 20 Nov 2005 21:56:58 -0500 To: Brian Candler , Tim Kientzle 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) on 128.113.2.4 Cc: freebsd-current@freebsd.org Subject: Re: Order of files with 'cp' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 02:57:03 -0000 At 7:29 PM +0000 11/20/05, Brian Candler wrote: >On Sat, Nov 19, 2005 at 11:33:54AM -0800, Tim Kientzle wrote: >> Brian Candler wrote: > > > I've noticed on FreeBSD-5.4 and -6.0 that the order in which > > > 'cp' copies multiple files does not match the order they're > > > given on the command line. > > ... > > > I've had a look through the code, and it seems that cp calls > > > fts_open() with the list of files in argv; fts_open then does > > > a qsort() on the arguments, using the comparison function > > > mastercmp() provided by cp: > > >> My suggestion: Have 'cp' call fts_open once for each >> command-line argument, instead of giving fts_open the entire >> argv list to muck with. > >Erm, but that just undoes the reason for calling fts_open with >mastercmp in the first place, which is to get it to pick files >before directories (or vice versa, as its behaviour seems to >be) as an 'optimisation'. If I understand the situation right, the suggestion would not completely undo the optimization that 'cp' is trying to do. Consider the command: cp -rp file1 dir1 file2 dir2 destdir The suggestion would mean the files going into destdir itself would not be sorted, but (if I understand this thread) files copied into destdir/dir1 and destdir/dir2 would still be sorted. Apparently this "sorting optimization" in `cp' goes all the way back to the original version of `cp' from 1994. While I expect we should change it to something better, I don't think we have any urgent reason to fix it immediately. Which is to say, let's figure out what the issues are, and come up with the best fix instead of the "easiest change" which we can rush to implement. *Assuming* the comment is correct, and that there *is* some performance benefit by copying files before directories, then it still seems to me that sorting all the files is a pretty clumsy heavy-handed way to accomplish that. These days some people have directories with tens of thousands of entries in them. Do we really want the overhead of "sorting" all of those entries just so files are copied before directories? I think a better fix might be to add an option to fts_open() which tells it to "process files before directories" (or visa-versa) in any given directory. Then `cp' could turn on that bit, and avoid the fake sort. It seems to me that if fts_open realizes that is wanted, then it could implement that behavior in some manner which is faster than sorting all entries. -- 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 Nov 21 03:09:19 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C3C616A41F; Mon, 21 Nov 2005 03:09:19 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id E544743D46; Mon, 21 Nov 2005 03:09:16 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id jAL39Fu1048371; Sun, 20 Nov 2005 21:09:15 -0600 (CST) (envelope-from dan) Date: Sun, 20 Nov 2005 21:09:15 -0600 From: Dan Nelson To: Paul Saab Message-ID: <20051121030915.GC41629@dan.emsphone.com> References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> <20051121004749.GA39061@xor.obsecurity.org> <43812AC7.3020506@rogers.com> <20051121020816.GA19252@xor.obsecurity.org> <438136B5.9030506@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <438136B5.9030506@freebsd.org> X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: current@freebsd.org, "Chad Leigh -- Shire.Net LLC" , Kris Kennaway Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 03:09:19 -0000 In the last episode (Nov 20), Paul Saab said: > Chad Leigh -- Shire.Net LLC wrote: > >I assume you are talking about the "phenomenon" of RAM "missing" due > >to PCI and other I/O mapping into the 4GB address space? What struck > >me about the OP is that the amount of RAM "missing" is more than I > >have ever seen due to this. My systems are usually 3.4-3.6GB of RAM > >with 4GB installed, not 2.86GB (3005MB)... So are we sure that the > >PCI space mapping is the problem? > > Enable PAE and you'll get all your ram. Anyone know if it's possible for the kernel to determine if any RAM is mapped above the 4gb point and warn the user about how much memory is unaccessable without PAE? -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 03:15:11 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3271316A41F for ; Mon, 21 Nov 2005 03:15:11 +0000 (GMT) (envelope-from ps@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1FDB43D45 for ; Mon, 21 Nov 2005 03:15:10 +0000 (GMT) (envelope-from ps@freebsd.org) Received: from [192.168.1.88] (64-142-76-135.dsl.static.sonic.net [64.142.76.135]) by elvis.mu.org (Postfix) with ESMTP id BFB2F1A3C1A; Sun, 20 Nov 2005 19:15:10 -0800 (PST) Message-ID: <43813BBE.2010302@freebsd.org> Date: Sun, 20 Nov 2005 19:15:10 -0800 From: Paul Saab User-Agent: Thunderbird 1.5 (Macintosh/20051025) MIME-Version: 1.0 To: Dan Nelson References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> <20051121004749.GA39061@xor.obsecurity.org> <43812AC7.3020506@rogers.com> <20051121020816.GA19252@xor.obsecurity.org> <438136B5.9030506@freebsd.org> <20051121030915.GC41629@dan.emsphone.com> In-Reply-To: <20051121030915.GC41629@dan.emsphone.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org, "Chad Leigh -- Shire.Net LLC" , Kris Kennaway Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 03:15:11 -0000 Dan Nelson wrote: > In the last episode (Nov 20), Paul Saab said: > >> Chad Leigh -- Shire.Net LLC wrote: >> >>> I assume you are talking about the "phenomenon" of RAM "missing" due >>> to PCI and other I/O mapping into the 4GB address space? What struck >>> me about the OP is that the amount of RAM "missing" is more than I >>> have ever seen due to this. My systems are usually 3.4-3.6GB of RAM >>> with 4GB installed, not 2.86GB (3005MB)... So are we sure that the >>> PCI space mapping is the problem? >>> >> Enable PAE and you'll get all your ram. >> > > Anyone know if it's possible for the kernel to determine if any RAM is > mapped above the 4gb point and warn the user about how much memory is > unaccessable without PAE? > You mean like it does now? "262144K of memory above 4GB ignored" From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 03:35:49 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9440F16A41F; Mon, 21 Nov 2005 03:35:49 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from smtp3.server.rpi.edu (smtp3.server.rpi.edu [128.113.2.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B42E43D45; Mon, 21 Nov 2005 03:35:49 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp3.server.rpi.edu (8.13.0/8.13.0) with ESMTP id jAL3Zksl009119; Sun, 20 Nov 2005 22:35:47 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: References: <20051116161540.GB4383@uk.tiscali.com> <437F7E22.5050800@freebsd.org> <20051120192914.GC19572@uk.tiscali.com> Date: Sun, 20 Nov 2005 22:35:45 -0500 To: Brian Candler , Tim Kientzle 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) on 128.113.2.3 Cc: freebsd-current@freebsd.org Subject: Re: Order of files with 'cp' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 03:35:49 -0000 At 9:56 PM -0500 11/20/05, Garance A Drosihn wrote: > >*Assuming* the comment is correct, and that there *is* some >performance benefit by copying files before directories, then >it still seems to me that sorting all the files is a pretty >clumsy heavy-handed way to accomplish that. These days some >people have directories with tens of thousands of entries in >them. Do we really want the overhead of "sorting" all of those >entries just so files are copied before directories? It also occurs to me that it might be helpful to know what effect sorting would have when combined with the 'dirhash' processing we have in directories now. If we *are* going to bother to sort the list of entries going into some directory, then maybe there is some other sort-order which would produce better results as far as dirhash is concerned. [disclaimer: I know nothing about how dirhash does it's hashing. It might be completely irrelevant which order is used when adding files to a directory] -- 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 Nov 21 03:40:28 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DA2216A41F; Mon, 21 Nov 2005 03:40:28 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFB4943D55; Mon, 21 Nov 2005 03:40:26 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id jAL3eP0h012375; Sun, 20 Nov 2005 21:40:25 -0600 (CST) (envelope-from dan) Date: Sun, 20 Nov 2005 21:40:25 -0600 From: Dan Nelson To: Paul Saab Message-ID: <20051121034025.GD41629@dan.emsphone.com> References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> <20051121004749.GA39061@xor.obsecurity.org> <43812AC7.3020506@rogers.com> <20051121020816.GA19252@xor.obsecurity.org> <438136B5.9030506@freebsd.org> <20051121030915.GC41629@dan.emsphone.com> <43813BBE.2010302@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43813BBE.2010302@freebsd.org> X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: current@freebsd.org, "Chad Leigh -- Shire.Net LLC" , Kris Kennaway Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 03:40:28 -0000 In the last episode (Nov 20), Paul Saab said: > Dan Nelson wrote: > >In the last episode (Nov 20), Paul Saab said: > >>Chad Leigh -- Shire.Net LLC wrote: > >>>I assume you are talking about the "phenomenon" of RAM "missing" > >>>due to PCI and other I/O mapping into the 4GB address space? What > >>>struck me about the OP is that the amount of RAM "missing" is more > >>>than I have ever seen due to this. My systems are usually > >>>3.4-3.6GB of RAM with 4GB installed, not 2.86GB (3005MB)... So > >>>are we sure that the PCI space mapping is the problem? > >> > >>Enable PAE and you'll get all your ram. > > > >Anyone know if it's possible for the kernel to determine if any RAM > >is mapped above the 4gb point and warn the user about how much > >memory is unaccessable without PAE? > > You mean like it does now? > "262144K of memory above 4GB ignored" That line didn't show up the the original poster's dmesg, though ( http://unixmania.com/dmesg_20051120.txt ). Maybe a verbose boot would shed more light. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 04:05:31 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CF5416A41F; Mon, 21 Nov 2005 04:05:31 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9C9B43D58; Mon, 21 Nov 2005 04:05:30 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jAL44kBU033428; Sun, 20 Nov 2005 21:04:46 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 20 Nov 2005 21:04:57 -0700 (MST) Message-Id: <20051120.210457.109704843.imp@bsdimp.com> To: wpaul@freebsd.org From: "M. Warner Losh" In-Reply-To: <20051120042536.E72D816A421@hub.freebsd.org> References: <20051120013530.GA55161@nowhere> <20051120042536.E72D816A421@hub.freebsd.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sun, 20 Nov 2005 21:04:51 -0700 (MST) Cc: craig@xfoil.gank.org, current@freebsd.org, tillman@seekingfire.com Subject: Re: Compaq ProLiant 1600 server freezes when detecting keyboard controller X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 04:05:31 -0000 In message: <20051120042536.E72D816A421@hub.freebsd.org> wpaul@freebsd.org (Bill Paul) writes: : Our PCI code : then comes along and enables all of the devices but doesn't necessarily : update the base address registers on some of them, which has the effect : of mapping one of the PCI devices at physical address 0. Actually, that bug has been fixed in recent versions of FreeBSD-current, and should be fixed in 6.0. I recall merging changes to 6.0 just before the release. The problem was that the host bridge wasn't properly setting a range. If that's not the case, then I'd like to know about it... Warner From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 04:38:01 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9108E16A41F; Mon, 21 Nov 2005 04:38:01 +0000 (GMT) (envelope-from rainer.alves@gmail.com) Received: from valimar.ibest.com.br (mx11.ibest.com.br [200.181.68.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2799943D45; Mon, 21 Nov 2005 04:38:00 +0000 (GMT) (envelope-from rainer.alves@gmail.com) Received: from [127.0.0.1] (centaurus.ibest.com.br [200.181.68.107]) by valimar.ibest.com.br (Postfix) with ESMTP id C956617BFEC; Mon, 21 Nov 2005 02:37:54 -0200 (BRDT) Message-ID: <43814F05.2010402@gmail.com> Date: Mon, 21 Nov 2005 02:37:25 -0200 From: Rainer Alves User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051105) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Thomas Quinot , current@freebsd.org References: <20051121014504.GA1236@melamine.cuivre.fr.eu.org> In-Reply-To: <20051121014504.GA1236@melamine.cuivre.fr.eu.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-iBEST-MailScanner-Information: Please contact the ISP for more information X-MailScanner-From: rainer.alves@gmail.com Cc: Subject: Re: 6.0-BETA5 random freeze with rtc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 04:38:01 -0000 Thomas Quinot wrote: >On a new Dell Precision 380 box running 6.05-BETA5, I've seen random >freezes (apparently not related to specific activities running on the >machine, which has web and mail servers and also runs an X server) a few >days apart. > >On the last two instances, the last message recorded in the logs was the >same: > >Nov 21 02:11:22 melamine kernel: rtc: 1000 > kern.hz: Timing will be inaccurate, please increase hz. > >and this messages does not occur at any other time, so I suspect it's >related to the freezes I saw. I might have been running mplayer shortly >before the freeze. Could this be related to PR 71536? (i.e. could the >rtc bug cause a freeze, and not only an annoying console message?) > >Thomas. > > I've had the same problem with mplayer+RTC on (5|6).x, the solution was to rebuild the kernel with "options HZ=1160", as well as rebuild the emulators/rtc port after each and every kernel update (reloading rtc.ko before launching mplayer). Messages regarding "inaccurate timing" and weird system freezes disappeared ever since. 7-current doesn't seem to be affected by any of those. -- Rainer Alves BrasilTelecom From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 05:20:09 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 664B516A41F for ; Mon, 21 Nov 2005 05:20:09 +0000 (GMT) (envelope-from dsnofe@yahoo.com.cn) Received: from web15702.mail.cnb.yahoo.com (web15702.mail.cnb.yahoo.com [202.165.102.69]) by mx1.FreeBSD.org (Postfix) with SMTP id 715E643D46 for ; Mon, 21 Nov 2005 05:20:08 +0000 (GMT) (envelope-from dsnofe@yahoo.com.cn) Received: (qmail 75085 invoked by uid 60001); 21 Nov 2005 05:20:07 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.cn; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=tbg0KZTR4qdnO7YArJb/f31IB7eftUMOPh1GuLlp8t2NwdakkutMzFi1xlEiwfjDgPa+7yDDF6hC35SvIa9pYT6OC9ItnqBiZfpEjM6aGyqo+ZJ8nHUQG+pt53w8mxocASg265tK2Kp7iubVKcnsRgnzj0IUVbprs/Ly/Xpwc78= ; Message-ID: <20051121052007.75083.qmail@web15702.mail.cnb.yahoo.com> Received: from [61.152.135.159] by web15702.mail.cnb.yahoo.com via HTTP; Mon, 21 Nov 2005 13:20:06 CST Date: Mon, 21 Nov 2005 13:20:06 +0800 (CST) From: XueFeng Deng To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Mon, 21 Nov 2005 05:23:31 +0000 Cc: Subject: Disk driver have BUGS in 6.0 ?? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 05:20:09 -0000 hey all, On Nov 10, I update one of my server to 6.0. these days I found some error occur in my app, and it seems that the disk driver have some bugs. then i made a test, it show that the disk give the wrong data. I md5 the same file in two times. and get two different Strings. any one meet this problem ? First is freebsd# date Mon Nov 21 00:37:27 CST 2005 freebsd# ll mm.wmv -rw-r--r-- 1 dengxf wheel 9548948 7 30 22:01 mm.wmv freebsd# md5 mm.wmv MD5 (mm.wmv) = 25cb3de0004c817649375978038548f9 freebsd# date Mon Nov 21 00:37:42 CST 2005 Second is freebsd# date Mon Nov 21 11:02:02 CST 2005 freebsd# ll mm.wmv -rw-r--r-- 1 dengxf wheel 9548948 7 30 22:01 mm.wmv freebsd# md5 mm.wmv MD5 (mm.wmv) = 476e82faa10f201e4ebb702054832d91 freebsd# date Mon Nov 21 11:02:05 CST 2005 freebsd# uname -a FreeBSD freebsd.jscz.edu.cn 6.0-STABLE FreeBSD 6.0-STABLE #0: Thu Nov 10 15:04:05 CST 2005 root@freebsd.jscz.edu.cn:/usr/obj/usr/src/sys/dengxf i386 freebsd# dmesg.boot: http://www.dengh.com/patch/dmesg.boot -- Deng XueFeng ___________________________________________________________ ÑÅ»¢Ãâ·ÑGÓÊÏ䣭ÖйúµÚÒ»¾øÎÞÀ¬»øÓʼþɧÈų¬´óÓÊÏä http://cn.mail.yahoo.com From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 05:32:15 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D63016A41F for ; Mon, 21 Nov 2005 05:32:15 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id D822043D46 for ; Mon, 21 Nov 2005 05:32:14 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id B7E1C1A3C19; Sun, 20 Nov 2005 21:32:14 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B4FF851390; Mon, 21 Nov 2005 00:32:13 -0500 (EST) Date: Mon, 21 Nov 2005 00:32:13 -0500 From: Kris Kennaway To: XueFeng Deng Message-ID: <20051121053213.GA42598@xor.obsecurity.org> References: <20051121052007.75083.qmail@web15702.mail.cnb.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EeQfGwPcQSOJBaQU" Content-Disposition: inline In-Reply-To: <20051121052007.75083.qmail@web15702.mail.cnb.yahoo.com> User-Agent: Mutt/1.4.2.1i Cc: current@freebsd.org Subject: Re: Disk driver have BUGS in 6.0 ?? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 05:32:15 -0000 --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 21, 2005 at 01:20:06PM +0800, XueFeng Deng wrote: > hey all, >=20 > On Nov 10, I update one of my server to 6.0. these days I found some= =20 > error occur in my app, and it seems that the disk driver have some bugs. >=20 > then i made a test, it show that the disk give the wrong data. What device is this on? Kris --EeQfGwPcQSOJBaQU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDgVvdWry0BWjoQKURAvIHAJ9gSPXGyquD9zMhlz/bk4MrEL/FLQCfb9dt KhFBIgA8PN+fNe2BBaGpubc= =tj2r -----END PGP SIGNATURE----- --EeQfGwPcQSOJBaQU-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 06:03:32 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B85616A41F for ; Mon, 21 Nov 2005 06:03:32 +0000 (GMT) (envelope-from ps@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id E15C743D45 for ; Mon, 21 Nov 2005 06:03:31 +0000 (GMT) (envelope-from ps@freebsd.org) Received: from [192.168.1.88] (64-142-76-135.dsl.static.sonic.net [64.142.76.135]) by elvis.mu.org (Postfix) with ESMTP id C00511A3C19; Sun, 20 Nov 2005 22:03:31 -0800 (PST) Message-ID: <43816333.4070400@freebsd.org> Date: Sun, 20 Nov 2005 22:03:31 -0800 From: Paul Saab User-Agent: Thunderbird 1.5 (Macintosh/20051025) MIME-Version: 1.0 To: Dan Nelson References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> <20051121004749.GA39061@xor.obsecurity.org> <43812AC7.3020506@rogers.com> <20051121020816.GA19252@xor.obsecurity.org> <438136B5.9030506@freebsd.org> <20051121030915.GC41629@dan.emsphone.com> <43813BBE.2010302@freebsd.org> <20051121034025.GD41629@dan.emsphone.com> In-Reply-To: <20051121034025.GD41629@dan.emsphone.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org, "Chad Leigh -- Shire.Net LLC" , Kris Kennaway Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 06:03:32 -0000 Dan Nelson wrote: > That line didn't show up the the original poster's dmesg, though ( > http://unixmania.com/dmesg_20051120.txt ). Maybe a verbose boot would > shed more light. > > It is too early in the boot process to be put in the dmesg buffer and it most definitely not under bootverbose. The way to see this is either via video console or serial. #ifndef PAE if (smap->base >= 0xffffffff) { printf("%uK of memory above 4GB ignored\n", (u_int)(smap->length / 1024)); continue; } #endif From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 06:06:53 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2090516A41F for ; Mon, 21 Nov 2005 06:06:53 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from indor.net.tomline.ru (indor.net.tomline.ru [213.183.100.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58E4543D53 for ; Mon, 21 Nov 2005 06:06:51 +0000 (GMT) (envelope-from snezhko@indorsoft.ru) Received: from SNEZHKO by indorsoft.ru (MDaemon.PRO.v7.2.2.R) with ESMTP id md50000031445.msg for ; Mon, 21 Nov 2005 12:06:47 +0600 X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 127406, updated: 20.11.2005] To: Rafael Caesar Lenzi References: <20051120204944.47606.qmail@web51009.mail.yahoo.com> From: Victor Snezhko Date: Mon, 21 Nov 2005 12:06:43 +0600 In-Reply-To: <20051120204944.47606.qmail@web51009.mail.yahoo.com> (Rafael Caesar Lenzi's message of "Sun, 20 Nov 2005 17:49:44 -0300 (ART)") Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (windows-nt) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Processed: indor.net.tomline.ru, Mon, 21 Nov 2005 12:06:47 +0600 (not processed: spam filter disabled) X-Return-Path: snezhko@indorsoft.ru X-MDaemon-Deliver-To: current@freebsd.org X-VVS-Spam: false Cc: current@freebsd.org Subject: Re: PPPoE and SATA problems in 7-CURRENT-SNAP009 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 06:06:53 -0000 Rafael Caesar Lenzi writes: > --- Victor Snezhko escreveu: >> As my telepathy module says, this is an INET6 problem that was fixed >> 4 days ago, i.e., after the SNAP009 was generated. You can either > cvsup >> to the fresh -current or disable INET6. > Well, i make a cvsup and get fresh copy of -current kernel. > The pppoe is more stable, but sometimes is happen. Hmm, are you sure the trap is the same after cvsup? > Any suggestion for problem of SATA controller? I have none. Maybe Will Robinson? :) -- WBR, Victor V. Snezhko EMail: snezhko@indorsoft.ru From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 06:10:32 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2462516A41F for ; Mon, 21 Nov 2005 06:10:32 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id D951843D4C for ; Mon, 21 Nov 2005 06:10:31 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id B2D541A3C19; Sun, 20 Nov 2005 22:10:31 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6579551206; Mon, 21 Nov 2005 01:10:30 -0500 (EST) Date: Mon, 21 Nov 2005 01:10:30 -0500 From: Kris Kennaway To: XueFeng Deng Message-ID: <20051121061030.GA11118@xor.obsecurity.org> References: <20051121053213.GA42598@xor.obsecurity.org> <20051121060522.72488.qmail@web15709.mail.cnb.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zYM0uCDKw75PZbzx" Content-Disposition: inline In-Reply-To: <20051121060522.72488.qmail@web15709.mail.cnb.yahoo.com> User-Agent: Mutt/1.4.2.1i Cc: current@freebsd.org, Kris Kennaway Subject: Re: ?????? Re: Disk driver have BUGS in 6.0 ?? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 06:10:32 -0000 --zYM0uCDKw75PZbzx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 21, 2005 at 02:05:22PM +0800, XueFeng Deng wrote: >=20 > da0 at sym0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-3 device=20 > da0: Serial Number ZE0F3285 > da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing > Enabled > da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) > GEOM: new disk da0 > ATA PseudoRAID loaded OK, it wasn't clear whether it was this or the ata disk. I'd say it's unlikely to be a driver problem. You didn't just change the RAM in this machine or make other hardware changes, did you? Kris --zYM0uCDKw75PZbzx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDgWTVWry0BWjoQKURAiBpAKDN7fQVM7QTEKCyG4eKK5R7Zlg6OgCg352Y jyMkeZT3mhlpTiwtrWYsapc= =kY22 -----END PGP SIGNATURE----- --zYM0uCDKw75PZbzx-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 06:45:12 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2052616A41F for ; Mon, 21 Nov 2005 06:45:12 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail01.syd.optusnet.com.au (mail01.syd.optusnet.com.au [211.29.132.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CDAA43D45 for ; Mon, 21 Nov 2005 06:45:11 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail01.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jAL6j8JL013754 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 21 Nov 2005 17:45:08 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id jAL6j0Hh004260; Mon, 21 Nov 2005 17:45:07 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jAL6j018004256; Mon, 21 Nov 2005 17:45:00 +1100 (EST) (envelope-from pjeremy) Date: Mon, 21 Nov 2005 17:44:59 +1100 From: Peter Jeremy To: Garance A Drosihn Message-ID: <20051121064459.GB1395@cirb503493.alcatel.com.au> References: <20051116161540.GB4383@uk.tiscali.com> <437F7E22.5050800@freebsd.org> <20051120192914.GC19572@uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: freebsd-current@freebsd.org Subject: Re: Order of files with 'cp' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 06:45:12 -0000 On Sun, 2005-Nov-20 21:56:58 -0500, Garance A Drosihn wrote: >Apparently this "sorting optimization" in `cp' goes all the way >back to the original version of `cp' from 1994. Looking back further, it appears this (mis)feature was introduced in 4.4BSD. V6 only allows one file. V7 through 4.3BSD (including reno and tahoe) all step through argv an element at a time. >*Assuming* the comment is correct, and that there *is* some >performance benefit by copying files before directories, Since it's fairly easy to disable the "optimisation", it would be fairly easy to check cp both with and without the "optimisation" - if someone can suggest a reasonable test. If the comment is correct, a recursive copy of a large directory comprising a mixture of a files and other directories would seem to be the worst case. >I think a better fix might be to add an option to fts_open() which >tells it to "process files before directories" (or visa-versa) in >any given directory. Then `cp' could turn on that bit, and avoid >the fake sort. Alternatively, make two passes through argv - on the first pass, copy all the directories, on the second pass, copy all the files. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 09:08:18 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83CEC16A41F for ; Mon, 21 Nov 2005 09:08:18 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from orb.pobox.com (orb.pobox.com [207.8.226.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AEDF43D45 for ; Mon, 21 Nov 2005 09:08:18 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from orb (localhost [127.0.0.1]) by orb.pobox.com (Postfix) with ESMTP id D8BA26D4; Mon, 21 Nov 2005 04:08:38 -0500 (EST) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by orb.sasl.smtp.pobox.com (Postfix) with ESMTP id 9D8968A; Mon, 21 Nov 2005 04:08:36 -0500 (EST) Received: from lists by mappit.local.linnet.org with local (Exim 4.54 (FreeBSD)) id 1Ee7en-0005ei-Ml; Mon, 21 Nov 2005 09:08:13 +0000 Date: Mon, 21 Nov 2005 09:08:13 +0000 From: Brian Candler To: Mark Linimon Message-ID: <20051121090813.GD21670@uk.tiscali.com> References: <200511201403.58634.nb_root@videotron.ca> <20051120190852.GB2963@soaustin.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051120190852.GB2963@soaustin.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org, Nicolas Blais Subject: Re: [patch] remove build dependencies in bsd.ports.mk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 09:08:18 -0000 On Sun, Nov 20, 2005 at 01:08:52PM -0600, Mark Linimon wrote: > On Sun, Nov 20, 2005 at 02:03:46PM -0500, Nicolas Blais wrote: > > As I 'ls /var/db/pkg', I noticed a lot of ports I didn't use and that didn't > > have a +REQUIRED_BY file. Ports such as ezm3 and gcc-ooo that I could do > > without. So, what I did is a simple hack in /usr/ports/Mk/bsd.port.mk so that > > I can run 'make deinstall-builddepends' after a port is installed, and it > > will ask me to remove any build dependencies. > > A lot of people use sysutils/pkg_cutleaves, which will interactively walk > through all unused ('leaf') ports. I don't support the ports system is smart enough to remember which ports were installed explicitly, and which were installed only because they were a dependency for another port? From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 09:53:14 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA6E416A41F for ; Mon, 21 Nov 2005 09:53:14 +0000 (GMT) (envelope-from nge@cs.hmc.edu) Received: from turing.cs.hmc.edu (turing.cs.hmc.edu [134.173.42.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77D8543D46 for ; Mon, 21 Nov 2005 09:53:14 +0000 (GMT) (envelope-from nge@cs.hmc.edu) Received: by turing.cs.hmc.edu (Postfix, from userid 26983) id CA5A35323F; Mon, 21 Nov 2005 01:53:13 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by turing.cs.hmc.edu (Postfix) with ESMTP id B4B2A5A8DE; Mon, 21 Nov 2005 01:53:13 -0800 (PST) Date: Mon, 21 Nov 2005 01:53:13 -0800 (PST) From: Nate Eldredge X-X-Sender: nate@turing To: Brian Candler In-Reply-To: <20051121090813.GD21670@uk.tiscali.com> Message-ID: References: <200511201403.58634.nb_root@videotron.ca> <20051120190852.GB2963@soaustin.net> <20051121090813.GD21670@uk.tiscali.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Mark Linimon , freebsd-current@freebsd.org, Nicolas Blais Subject: Re: [patch] remove build dependencies in bsd.ports.mk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 09:53:14 -0000 On Mon, 21 Nov 2005, Brian Candler wrote: > I don't support the ports system is smart enough to remember which ports > were installed explicitly, and which were installed only because they were a > dependency for another port? I don't think so, but this would be a useful feature. Debian's aptitude package manager has a feature like this, which is very convenient. It works as follows. Suppose package Foo requires package Bar, and neither is currently installed. When you request the installation of Foo, Bar is also installed, but an "auto" flag is set for Bar. Any package with the auto flag set is only kept so long as something depends on it. If I remove Foo, Bar is automatically removed as well, provided I haven't in the meantime added anything else which depends on it. The user can toggle the auto flag manually as well. If I decide I really like Bar in itself, I can turn off its auto flag and keep it after I remove Foo. If I am sick of Foo, I can set its auto flag and it will be removed once it is no longer needed (possibly at once). Anyway, AFAIK FreeBSD doesn't have anything like this, but it would be nifty if it did. I would guess build dependencies should be treated like regular dependencies. If they're removed after building, then you would have to reinstall them every time you upgrade the depending package. -- Nate Eldredge nge@cs.hmc.edu From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 10:47:11 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D946A16A41F for ; Mon, 21 Nov 2005 10:47:11 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7818943D4C for ; Mon, 21 Nov 2005 10:47:11 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01a ([66.130.198.54]) by VL-MO-MR002.ip.videotron.ca (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTP id <0IQA006U2WMMI5F0@VL-MO-MR002.ip.videotron.ca> for freebsd-current@freebsd.org; Mon, 21 Nov 2005 05:47:10 -0500 (EST) Date: Mon, 21 Nov 2005 05:46:49 -0500 From: Nicolas Blais In-reply-to: To: freebsd-current@freebsd.org Message-id: <200511210547.10306.nb_root@videotron.ca> MIME-version: 1.0 Content-type: multipart/signed; boundary=nextPart1343507.ohm3DFmO9j; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit References: <200511201403.58634.nb_root@videotron.ca> <20051121090813.GD21670@uk.tiscali.com> User-Agent: KMail/1.8.3 Cc: Nate Eldredge , Brian Candler Subject: Re: [patch] remove build dependencies in bsd.ports.mk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 10:47:12 -0000 --nextPart1343507.ohm3DFmO9j Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On November 21, 2005 04:53 am, Nate Eldredge wrote: > On Mon, 21 Nov 2005, Brian Candler wrote: > > I don't support the ports system is smart enough to remember which ports > > were installed explicitly, and which were installed only because they > > were a dependency for another port? > > I don't think so, but this would be a useful feature. Debian's aptitude > package manager has a feature like this, which is very convenient. It > works as follows. Suppose package Foo requires package Bar, and neither > is currently installed. When you request the installation of Foo, Bar is > also installed, but an "auto" flag is set for Bar. Any package with the > auto flag set is only kept so long as something depends on it. If I > remove Foo, Bar is automatically removed as well, provided I haven't in > the meantime added anything else which depends on it. > > The user can toggle the auto flag manually as well. If I decide I really > like Bar in itself, I can turn off its auto flag and keep it after I > remove Foo. If I am sick of Foo, I can set its auto flag and it will be > removed once it is no longer needed (possibly at once). > > Anyway, AFAIK FreeBSD doesn't have anything like this, but it would be > nifty if it did. > > I would guess build dependencies should be treated like regular > dependencies. If they're removed after building, then you would have to > reinstall them every time you upgrade the depending package. This is why I made the patch. I found it useless to have gcc-ooo and many=20 other ports that could be cleaned out after a build, without having to run = a=20 tier software. =20 It would be a nice thing if the port system did that, as it would be it's j= ob=20 to do so.=20 =2D-=20 =46reeBSD 7.0-CURRENT #1: Sat Nov 19 12:36:29 EST 2005 =20 root@clk01a:/usr/obj/usr/src/sys/CLK01A=20 PGP? (updated 16 Nov 05) : http://www.clkroot.net/security/nb_root.asc --nextPart1343507.ohm3DFmO9j Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDgaWu4wTBlvcsbJURAhXQAJ9EKfl/12OiPCnqOvj5NV9bZ2OSZgCeL4ky 9KAFzTLhTDTSCXHomu/yu9Q= =uOMp -----END PGP SIGNATURE----- --nextPart1343507.ohm3DFmO9j-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 11:05:41 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 749A316A447; Mon, 21 Nov 2005 11:05:39 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA2FD43DDB; Mon, 21 Nov 2005 11:05:25 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id jALB5L5V076137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 Nov 2005 14:05:22 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id jALB5LFC076136; Mon, 21 Nov 2005 14:05:21 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Mon, 21 Nov 2005 14:05:21 +0300 From: Gleb Smirnoff To: Andrey Chernov , current@FreeBSD.org, gnome@FreeBSD.org Message-ID: <20051121110521.GN24212@cell.sick.ru> References: <20051118131131.GA96190@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20051118131131.GA96190@nagual.pp.ru> User-Agent: Mutt/1.5.6i Cc: Subject: Re: KSE: whom to blame, -current SMP or firefox? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 11:05:41 -0000 Andrey, On Fri, Nov 18, 2005 at 04:11:31PM +0300, Andrey Chernov wrote: A> The problem: I got 100% dead loop at 'install' stage of the 'firefox' A> port (after ===> Building Chrome's registry... message). A> '/usr/X11R6/lib/firefox/regchrome' is the program that loops (at the end A> of its task, so kill -9 continues install normally). That is SMP machine. this is not SMP problem, I have observed it on UP. I've faced this problem with firefox, too. I bet that removing the gconf-2 port will allow you to install firefox. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 12:10:57 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1260616A456; Mon, 21 Nov 2005 12:10:57 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn.pobox.com (thorn.pobox.com [208.210.124.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BAB843D49; Mon, 21 Nov 2005 12:10:56 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn (localhost [127.0.0.1]) by thorn.pobox.com (Postfix) with ESMTP id C7F09AE; Mon, 21 Nov 2005 07:11:17 -0500 (EST) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thorn.sasl.smtp.pobox.com (Postfix) with ESMTP id 554A445E; Mon, 21 Nov 2005 07:11:15 -0500 (EST) Received: from brian by mappit.local.linnet.org with local (Exim 4.54 (FreeBSD)) id 1EeAVY-0005oC-4z; Mon, 21 Nov 2005 12:10:52 +0000 Date: Mon, 21 Nov 2005 12:10:52 +0000 From: Brian Candler To: Giorgos Keramidas Message-ID: <20051121121052.GA22309@uk.tiscali.com> References: <20051116161540.GB4383@uk.tiscali.com> <437F7E22.5050800@freebsd.org> <20051120193416.GB1599@flame.pc> <20051120205605.GB19791@uk.tiscali.com> <20051121114614.GA1549@flame.pc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051121114614.GA1549@flame.pc> User-Agent: Mutt/1.4.2.1i Cc: Tim Kientzle , freebsd-current@freebsd.org Subject: Re: Order of files with 'cp' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 12:10:57 -0000 On Mon, Nov 21, 2005 at 01:46:14PM +0200, Giorgos Keramidas wrote: > To return to the problem at hand, the problem is that the > 'sorting' function is allowed to re-arrange the order of argv[] > elements. I'd probably try to write mastercmp() in a way that > satisfies all of the following: > > - All files are sorted before all directories > - Files are arranged by their argv[] order > - Directories are arranged by their argv[] order I think that was my option (1) at http://lists.freebsd.org/pipermail/freebsd-current/2005-November/058098.html Regards, Brian. From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 11:46:39 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8469216A41F; Mon, 21 Nov 2005 11:46:39 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAB7343D45; Mon, 21 Nov 2005 11:46:38 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by rosebud.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id jALBkadm031511; Mon, 21 Nov 2005 13:46:36 +0200 Received: by flame.pc (Postfix, from userid 1001) id 4FD151174D; Mon, 21 Nov 2005 13:46:14 +0200 (EET) Date: Mon, 21 Nov 2005 13:46:14 +0200 From: Giorgos Keramidas To: Brian Candler Message-ID: <20051121114614.GA1549@flame.pc> References: <20051116161540.GB4383@uk.tiscali.com> <437F7E22.5050800@freebsd.org> <20051120193416.GB1599@flame.pc> <20051120205605.GB19791@uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051120205605.GB19791@uk.tiscali.com> X-Mailman-Approved-At: Mon, 21 Nov 2005 12:24:48 +0000 Cc: Tim Kientzle , freebsd-current@freebsd.org Subject: Re: Order of files with 'cp' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 11:46:39 -0000 On 2005-11-20 20:56, Brian Candler wrote: > On Sun, Nov 20, 2005 at 09:34:16PM +0200, Giorgos Keramidas wrote: > > qsort() can be 'stable' enough for our purposes if the comparison > > function uses something like this: > > > > int > > compare_int32_t(void *pa, void *pb) > > { > > int32_t a, b; > > > > assert(pa != NULL && pb != NULL); > > a = *((int32_t *)pa); > > b = *((int32_t *)pb); > > > > if (a < b && pa != pb) > > return 1; > > if (a > b && pa != pb) > > return -1; > > return 0; > > } > > Care to explain?? > > For one thing, I don't think qsort() will ever call its > comparison function with two equal pointers, as that would be a > point(er)less thing to do. Therefore, I can't see why you are > testing for pa != pb, since this condition will always be > true. (Also, a < b could never be true if pa == pb). I see. I was hoping to avoid spurious exchanges of `objects' in cases like: struct object { int obj_value; }; static struct object objvec[] = {{1},{1},{1}}; static struct object *vec[3] = { &(objvec[0]), &(objvec[1]), &(objvec[2]), }; where the comparison function may compare vec[k]->obj_value elements and 'exchange' elements of vec[] because their value is 'equal' anyway. But you're right this won't help, since qsort() never passes equal pointers to the comparison function. > Secondly, mastercmp() doesn't compare integers, it compares FTS > structures. The comparison function just compares whether one > item is a directory and the other a file. How would you have > mastercmp() work instead? To return to the problem at hand, the problem is that the 'sorting' function is allowed to re-arrange the order of argv[] elements. I'd probably try to write mastercmp() in a way that satisfies all of the following: - All files are sorted before all directories - Files are arranged by their argv[] order - Directories are arranged by their argv[] order This would probably require some sort of fts_number hackery, to make sure we save the original order of argv[] elements, but I'm not sure how to write a mastercmp() that works this way yet. I'll have to check this more carefully - Giorgos From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 12:39:07 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E21516A420 for ; Mon, 21 Nov 2005 12:39:07 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn.pobox.com (thorn.pobox.com [208.210.124.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD3B043D95 for ; Mon, 21 Nov 2005 12:38:55 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn (localhost [127.0.0.1]) by thorn.pobox.com (Postfix) with ESMTP id A57EEAB; Mon, 21 Nov 2005 07:39:16 -0500 (EST) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thorn.sasl.smtp.pobox.com (Postfix) with ESMTP id 61AF245E; Mon, 21 Nov 2005 07:39:14 -0500 (EST) Received: from lists by mappit.local.linnet.org with local (Exim 4.54 (FreeBSD)) id 1EeAwd-0005px-4u; Mon, 21 Nov 2005 12:38:51 +0000 Date: Mon, 21 Nov 2005 12:38:51 +0000 From: Brian Candler To: Peter Jeremy Message-ID: <20051121123851.GA22368@uk.tiscali.com> References: <20051116161540.GB4383@uk.tiscali.com> <437F7E22.5050800@freebsd.org> <20051120192914.GC19572@uk.tiscali.com> <20051121064459.GB1395@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051121064459.GB1395@cirb503493.alcatel.com.au> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org, Garance A Drosihn Subject: Re: Order of files with 'cp' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 12:39:07 -0000 On Mon, Nov 21, 2005 at 05:44:59PM +1100, Peter Jeremy wrote: > Alternatively, make two passes through argv - on the first pass, copy > all the directories, on the second pass, copy all the files. Or vice versa :-) The comment says it copies files before directories. However the implementation of mastercmp() returns -1 when comparing directory A to anything else B; therefore it sorts directories before files. So at very least the comment needs changing. I agree that a real-world test is the only way to settle the best behaviour definitively. Also, remember that cp -R can work recursively to any depth. Handling argv[] in two passes as you suggest only affects the first level. Now, perhaps when copying subdirectories we care even less about preserving the 'natural' order of files; but as has been pointed out elsewhere, it's quite likely that we could have 10,000 files and not really want to go to the trouble of sorting them, just to select the subsets of 'all directories' and 'all non-directories'. In this case, implementing the two-pass selection as an option within fts_open makes sense. Regards, Brian. From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 12:34:30 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42D4E16A41F; Mon, 21 Nov 2005 12:34:30 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DCE843D5C; Mon, 21 Nov 2005 12:34:23 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by kane.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id jALCYJX4016144; Mon, 21 Nov 2005 14:34:19 +0200 Received: by flame.pc (Postfix, from userid 1001) id 72AD011763; Mon, 21 Nov 2005 14:33:57 +0200 (EET) Date: Mon, 21 Nov 2005 14:33:57 +0200 From: Giorgos Keramidas To: Brian Candler Message-ID: <20051121123357.GA1918@flame.pc> References: <20051116161540.GB4383@uk.tiscali.com> <437F7E22.5050800@freebsd.org> <20051120193416.GB1599@flame.pc> <20051120205605.GB19791@uk.tiscali.com> <20051121114614.GA1549@flame.pc> <20051121121052.GA22309@uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051121121052.GA22309@uk.tiscali.com> X-Mailman-Approved-At: Mon, 21 Nov 2005 12:39:22 +0000 Cc: Tim Kientzle , freebsd-current@freebsd.org Subject: Re: Order of files with 'cp' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 12:34:30 -0000 On 2005-11-21 12:10, Brian Candler wrote: >On Mon, Nov 21, 2005 at 01:46:14PM +0200, Giorgos Keramidas wrote: >> To return to the problem at hand, the problem is that the >> 'sorting' function is allowed to re-arrange the order of argv[] >> elements. I'd probably try to write mastercmp() in a way that >> satisfies all of the following: >> >> - All files are sorted before all directories >> - Files are arranged by their argv[] order >> - Directories are arranged by their argv[] order > > I think that was my option (1) at > http://lists.freebsd.org/pipermail/freebsd-current/2005-November/058098.html Of course. I just misunderstood you back then :) From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 13:52:44 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 63B4F16A41F for ; Mon, 21 Nov 2005 13:52:44 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD4A143D49 for ; Mon, 21 Nov 2005 13:52:42 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by freebsd.czest.pl (8.12.10/8.12.9) with ESMTP id jALDs2Px094640; Mon, 21 Nov 2005 13:54:03 GMT (envelope-from dunstan@freebsd.czest.pl) Received: (from dunstan@localhost) by freebsd.czest.pl (8.13.4/8.12.9/Submit) id jALDs17Q094639; Mon, 21 Nov 2005 13:54:01 GMT (envelope-from dunstan) Date: Mon, 21 Nov 2005 13:54:01 +0000 From: "Wojciech A. Koszek" To: "Daniel O'Connor" Message-ID: <20051121135401.GA94609@freebsd.czest.pl> References: <20051120172755.GA85641@freebsd.czest.pl> <84dead720511200943ua2cf8b8y49bff0dcf3e2fa63@mail.gmail.com> <20051120183037.GA85917@freebsd.czest.pl> <200511211011.29745.doconnor@gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <200511211011.29745.doconnor@gsoft.com.au> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Specifying alternative file for devd(8) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 13:52:44 -0000 On Mon, Nov 21, 2005 at 10:11:28AM +1030, Daniel O'Connor wrote: > On Mon, 21 Nov 2005 05:00, Wojciech A. Koszek wrote: > > > You should probably also mention in the manual page that > > > only one (the last) '-f' option has an effect. > > > > Every options has an effect and (somehow) modifies application behavour. I > > don't see a reason why to mention it, since it's already explained. If you > > think it's really needed, let me know, I'll make another update. > > He means that you should mention that multiple -f options are not additive. > > ie you can't do > devd -f config1 -f config2 > > and have devd "merge" the 2 configuration files. Sorry and thanks for the explanation. Updated patch: http://freebsd.czest.pl/dunstan/FreeBSD/diff.2.devd -- * Wojciech A. Koszek && dunstan@FreeBSD.czest.pl From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 14:49:07 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1BBBE16A41F; Mon, 21 Nov 2005 14:49:07 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B1DB43D49; Mon, 21 Nov 2005 14:49:06 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2362940 for multiple; Mon, 21 Nov 2005 09:49:15 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jALEn1su069223; Mon, 21 Nov 2005 09:49:01 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-alpha@freebsd.org Date: Mon, 21 Nov 2005 09:49:10 -0500 User-Agent: KMail/1.8.2 References: <5D4CE421-AC74-40D6-AB53-836630BB8F19@xcllnt.net> In-Reply-To: <5D4CE421-AC74-40D6-AB53-836630BB8F19@xcllnt.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511210949.12455.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: sparc64@freebsd.org, alpha@freebsd.org, current@freebsd.org, Marcel Moolenaar Subject: Re: dc(4) related misalignment trap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 14:49:07 -0000 On Saturday 19 November 2005 08:11 pm, Marcel Moolenaar wrote: > All, > > On alpha this time: > > > swapon: adding /dev/da0b as swap device > Starting file system checks: > /dev/da0a: 38800 files, 486252 used, 3308480 free (41816 frags, > 408333 blocks, 1.1% fragmentation) > Setting hostname: ds10.pn.xcllnt.net. > > fatal kernel trap: > > trap entry = 0x4 (unaligned access fault) > faulting va = 0xfffffc000096b73b > opcode = 0xc > register = 0x1 > pc = 0xfffffc0000389cd8 > ra = 0xfffffc0000389c98 > sp = 0xfffffe001a581800 > usp = 0x11ffe4f8 > curthread = 0xfffffc003eb1d340 > pid = 165, comm = ifconfig > > [thread pid 165 tid 100034 ] > Stopped at dc_setfilt_21143+0x368: stl t0,0x9c(s3) > <0xfffffc000095879c> > > db> bt > Tracing pid 165 tid 100034 td 0xfffffc003eb1d340 > dc_setfilt_21143() at dc_setfilt_21143+0x368 > dc_setfilt() at dc_setfilt+0x58 > dc_init_locked() at dc_init_locked+0x9c8 > dc_init() at dc_init+0x78 > ether_ioctl() at ether_ioctl+0xd8 > dc_ioctl() at dc_ioctl+0x370 > in6_ifinit() at in6_ifinit+0x11c > in6_update_ifa() at in6_update_ifa+0x604 > in6_ifattach_linklocal() at in6_ifattach_linklocal+0x198 > in6_ifattach() at in6_ifattach+0x110 > in6_if_up() at in6_if_up+0xa8 > if_route() at if_route+0xa4 > if_up() at if_up+0x1c > ifhwioctl() at ifhwioctl+0x3a8 > ifioctl() at ifioctl+0x178 > soo_ioctl() at soo_ioctl+0x6e4 > ioctl() at ioctl+0x6e8 > syscall() at syscall+0x458 > XentSys() at XentSys+0x64 > --- syscall (54, FreeBSD ELF64, ioctl) --- > > > Note that the faulting instruction is really the instruction before > the one shown. In kgdb: > > 0xfffffc0000389cd4 : ldwu t0,8(t0) > 0xfffffc0000389cd8 : stl t0,156(s3) > > ldwu = load word unsigned. > > > (kgdb) l *dc_setfilt_21143+0x368 > 0xfffffc0000389cd8 is in dc_setfilt_21143 (../../../dev/dc/if_dc.c: > 1129). > 1124 h = dc_mchash_le(sc, ifp->if_broadcastaddr); > 1125 sp[h >> 4] |= htole32(1 << (h & 0xF)); > 1126 } > 1127 > 1128 /* Set our MAC address */ > 1129 sp[39] = DC_SP_MAC(((u_int16_t *)IF_LLADDR(sc- > > >dc_ifp))[0]); > > 1130 sp[40] = DC_SP_MAC(((u_int16_t *)IF_LLADDR(sc- > > >dc_ifp))[1]); > > 1131 sp[41] = DC_SP_MAC(((u_int16_t *)IF_LLADDR(sc- > > >dc_ifp))[2]); > > 1132 > 1133 sframe->dc_status = htole32(DC_TXSTAT_OWN); > > (kgdb) f 12 > #12 0xfffffc0000389cd8 in dc_setfilt_21143 (sc=0xfffffc0000842000) > at ../../../dev/dc/if_dc.c:1129 > 1129 sp[39] = DC_SP_MAC(((u_int16_t *)IF_LLADDR(sc- > > >dc_ifp))[0]); > > (kgdb) p sp > $2 = (u_int32_t *) 0xfffffc0000958700 > (kgdb) p sc->dc_ifp->if_addr->ifa_addr > $5 = (struct sockaddr *) 0xfffffc000096b730 > (kgdb) p *(struct sockaddr_dl *)$5 > $6 = {sdl_len = 56 '8', sdl_family = 18 '\022', sdl_index = 1, > sdl_type = 6 '\006', sdl_nlen = 3 '\003', sdl_alen = 6 '\006', > sdl_slen = 0 '\0', sdl_data = "dc0\b\000+\206\"J", '\0' times>} > (kgdb) p $6.sdl_data + $6.sdl_nlen > $7 = 0xfffffc000096b73b "\b" > > Register s3 holds the sp variable ($2 in kgdb) > Register t0 holds the result the left-hand side of the statement, which > is not properly aligned for a 16-bit load ($7 = register t0 + 8). > > Rough patch to fix the problem attached: I think de(4) would need the same fix as well at least. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 16:24:21 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7762116A41F for ; Mon, 21 Nov 2005 16:24:21 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8F27643D45 for ; Mon, 21 Nov 2005 16:24:20 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by freebsd.czest.pl (8.12.10/8.12.9) with ESMTP id jALGPiPx095154 for ; Mon, 21 Nov 2005 16:25:44 GMT (envelope-from dunstan@freebsd.czest.pl) Received: (from dunstan@localhost) by freebsd.czest.pl (8.13.4/8.12.9/Submit) id jALGPiwR095153 for freebsd-current@freebsd.org; Mon, 21 Nov 2005 16:25:44 GMT (envelope-from dunstan) Date: Mon, 21 Nov 2005 16:25:44 +0000 From: "Wojciech A. Koszek" To: freebsd-current@freebsd.org Message-ID: <20051121162544.GB94958@freebsd.czest.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Linking basesystem with additional libraries. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 16:24:21 -0000 Hello, Is there any reason why we couldn't have LDADD honored in "buildworld" process? If there are no negative implications, I volunteer to do the work. I'd find it really useful. -- * Wojciech A. Koszek && dunstan@FreeBSD.czest.pl From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 17:08:17 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9142116A422 for ; Mon, 21 Nov 2005 17:08:17 +0000 (GMT) (envelope-from chad@shire.net) Received: from hobbiton.shire.net (hobbiton.shire.net [166.70.252.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C74043D62 for ; Mon, 21 Nov 2005 17:08:03 +0000 (GMT) (envelope-from chad@shire.net) Received: from [67.161.222.227] (helo=[192.168.99.68]) by hobbiton.shire.net with esmtpa (Exim 4.51) id 1EeF98-000DjL-B9; Mon, 21 Nov 2005 10:08:02 -0700 In-Reply-To: <4381FE62.5040208@deadcafe.de> References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> <20051121004749.GA39061@xor.obsecurity.org> <43812AC7.3020506@rogers.com> <20051121020816.GA19252@xor.obsecurity.org> <4381FE62.5040208@deadcafe.de> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1513AD48-E08F-4670-A82B-E8D2D363F1E9@shire.net> Content-Transfer-Encoding: 7bit From: "Chad Leigh -- Shire.Net LLC" Date: Mon, 21 Nov 2005 10:08:01 -0700 To: Daniel Rock X-Mailer: Apple Mail (2.746.2) X-SA-Exim-Connect-IP: 67.161.222.227 X-SA-Exim-Mail-From: chad@shire.net X-SA-Exim-Scanned: No (on hobbiton.shire.net); SAEximRunCond expanded to false Cc: current@freebsd.org, Kris Kennaway Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 17:08:17 -0000 On Nov 21, 2005, at 10:05 AM, Daniel Rock wrote: > Chad Leigh -- Shire.Net LLC schrieb: >> I assume you are talking about the "phenomenon" of RAM "missing" >> due to PCI and other I/O mapping into the 4GB address space? >> What struck me about the OP is that the amount of RAM "missing" >> is more than I have ever seen due to this. My systems are >> usually 3.4-3.6GB of RAM with 4GB installed, not 2.86GB >> (3005MB)... So are we sure that the PCI space mapping is the >> problem? > > This is nothing unusual. I have a machine on which over 1.25GB is > mapped "out of the way". It is a Tyan Thunder K8WE (S2895). In BIOS > I can choose between Hardware/Software/Disabled mapping: > > > Hardware (requires E-stepping CPUs): > real memory = 5637144576 (5376 MB) > Physical memory chunk(s): > 0x0000000000001000 - 0x0000000000090fff, 589824 bytes (144 pages) > 0x0000000000985000 - 0x00000000a616ffff, 2776543232 bytes (677867 > pages) > 0x0000000100000000 - 0x000000014ffdffff, 1342046208 bytes (327648 > pages) > avail memory = 4109500416 (3919 MB) > > Software (should work regardless of stepping): > real memory = 6442450944 (6144 MB) > Physical memory chunk(s): > 0x0000000000001000 - 0x0000000000090fff, 589824 bytes (144 pages) > 0x0000000000985000 - 0x000000007ff1ffff, 2136584192 bytes (521627 > pages) > 0x0000000100000000 - 0x0000000174baffff, 1958412288 bytes (478128 > pages) > avail memory = 4085907456 (3896 MB) > > Disabled: > real memory = 2951872512 (2815 MB) > Physical memory chunk(s): > 0x0000000000001000 - 0x0000000000090fff, 589824 bytes (144 pages) > 0x0000000000983000 - 0x00000000aac56fff, 2855092224 bytes (697044 > pages) > avail memory = 2846003200 (2714 MB) Yes, but in your case the real memory is > 4gb so of course the amount mapped would be less. I have never seen on any of my motherboards, > 1Gb getting mapped when the physical memory is only 4GB Chad > > > > Daniel --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad@shire.net From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 18:15:21 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E656A16A420 for ; Mon, 21 Nov 2005 18:15:21 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail04.syd.optusnet.com.au (mail04.syd.optusnet.com.au [211.29.132.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCEA543D46 for ; Mon, 21 Nov 2005 18:15:20 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail04.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jALIF9sL028244 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 22 Nov 2005 05:15:10 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id jALIF9Hh005397; Tue, 22 Nov 2005 05:15:09 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jALIF9ej005396; Tue, 22 Nov 2005 05:15:09 +1100 (EST) (envelope-from pjeremy) Date: Tue, 22 Nov 2005 05:15:09 +1100 From: Peter Jeremy To: Nate Eldredge Message-ID: <20051121181509.GB4267@cirb503493.alcatel.com.au> References: <200511201403.58634.nb_root@videotron.ca> <20051120190852.GB2963@soaustin.net> <20051121090813.GD21670@uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: freebsd-current@freebsd.org Subject: Re: [patch] remove build dependencies in bsd.ports.mk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 18:15:22 -0000 On Mon, 2005-Nov-21 01:53:13 -0800, Nate Eldredge wrote: >works as follows. Suppose package Foo requires package Bar, and neither >is currently installed. When you request the installation of Foo, Bar is >also installed, but an "auto" flag is set for Bar. Any package with the >auto flag set is only kept so long as something depends on it. If I >remove Foo, Bar is automatically removed as well, provided I haven't in >the meantime added anything else which depends on it. This would work OK for runtime dependencies but handling build-time only dependencies would need some careful thought. Whilst it might be reasonable to automatically remove gcc-ooo after installing Openoffice.org, I probably wouldn't want autoconf, automake, imake etc deleted immediately after building something that needed them. >I would guess build dependencies should be treated like regular >dependencies. If they're removed after building, then you would have to >reinstall them every time you upgrade the depending package. They can't be treated totally as runtime dependencies because you don't need (or want) them installed if you install a package (rather than building a port). >Anyway, AFAIK FreeBSD doesn't have anything like this, but it would be >nifty if it did. Agreed. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 18:16:57 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 398CF16A420; Mon, 21 Nov 2005 18:16:57 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01EFD43D45; Mon, 21 Nov 2005 18:16:55 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2371905 for multiple; Mon, 21 Nov 2005 13:17:06 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jALIGkcl070379; Mon, 21 Nov 2005 13:16:51 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 21 Nov 2005 13:07:02 -0500 User-Agent: KMail/1.8.2 References: <20051120013530.GA55161@nowhere> <20051120042536.E72D816A421@hub.freebsd.org> <20051120.210457.109704843.imp@bsdimp.com> In-Reply-To: <20051120.210457.109704843.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511211307.05043.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: wpaul@freebsd.org, tillman@seekingfire.com, current@freebsd.org, "M. Warner Losh" , craig@xfoil.gank.org Subject: Re: Compaq ProLiant 1600 server freezes when detecting keyboard controller X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 18:16:57 -0000 On Sunday 20 November 2005 11:04 pm, M. Warner Losh wrote: > In message: <20051120042536.E72D816A421@hub.freebsd.org> > > wpaul@freebsd.org (Bill Paul) writes: > : Our PCI code > : then comes along and enables all of the devices but doesn't necessarily > : update the base address registers on some of them, which has the effect > : of mapping one of the PCI devices at physical address 0. > > Actually, that bug has been fixed in recent versions of > FreeBSD-current, and should be fixed in 6.0. I recall merging changes > to 6.0 just before the release. The problem was that the host bridge > wasn't properly setting a range. If that's not the case, then I'd > like to know about it... No, the bug was fixed, but that wasn't the fix. The fix was to bail out earlier if a BAR's base was 0 and not enable IO or MEM decoding unless a BAR had a valid base (where 0 and 0xfffffff are both invalid bases). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 18:16:57 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 398CF16A420; Mon, 21 Nov 2005 18:16:57 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01EFD43D45; Mon, 21 Nov 2005 18:16:55 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2371905 for multiple; Mon, 21 Nov 2005 13:17:06 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jALIGkcl070379; Mon, 21 Nov 2005 13:16:51 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 21 Nov 2005 13:07:02 -0500 User-Agent: KMail/1.8.2 References: <20051120013530.GA55161@nowhere> <20051120042536.E72D816A421@hub.freebsd.org> <20051120.210457.109704843.imp@bsdimp.com> In-Reply-To: <20051120.210457.109704843.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511211307.05043.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: wpaul@freebsd.org, tillman@seekingfire.com, current@freebsd.org, "M. Warner Losh" , craig@xfoil.gank.org Subject: Re: Compaq ProLiant 1600 server freezes when detecting keyboard controller X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 18:16:57 -0000 On Sunday 20 November 2005 11:04 pm, M. Warner Losh wrote: > In message: <20051120042536.E72D816A421@hub.freebsd.org> > > wpaul@freebsd.org (Bill Paul) writes: > : Our PCI code > : then comes along and enables all of the devices but doesn't necessarily > : update the base address registers on some of them, which has the effect > : of mapping one of the PCI devices at physical address 0. > > Actually, that bug has been fixed in recent versions of > FreeBSD-current, and should be fixed in 6.0. I recall merging changes > to 6.0 just before the release. The problem was that the host bridge > wasn't properly setting a range. If that's not the case, then I'd > like to know about it... No, the bug was fixed, but that wasn't the fix. The fix was to bail out earlier if a BAR's base was 0 and not enable IO or MEM decoding unless a BAR had a valid base (where 0 and 0xfffffff are both invalid bases). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 18:16:57 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFA5216A41F for ; Mon, 21 Nov 2005 18:16:57 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6326243D45 for ; Mon, 21 Nov 2005 18:16:57 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2371906 for multiple; Mon, 21 Nov 2005 13:17:08 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jALIGkcm070379; Mon, 21 Nov 2005 13:16:54 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org, Hao Chen Date: Mon, 21 Nov 2005 13:08:34 -0500 User-Agent: KMail/1.8.2 References: <20051119141708.GA919@utmail.utmem.edu> In-Reply-To: <20051119141708.GA919@utmail.utmem.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511211308.34961.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Subject: Re: RELENG_6_0: fatal trap 12 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 18:16:58 -0000 On Saturday 19 November 2005 09:17 am, Hao Chen wrote: > Hi, > > I am upgrading from 5.4 to 6.0 and got the following error message: > > > Fatal trap 12: page fault while in kernel mode > cpuid = 1; apic id = 01 > fault virtual address = 0x480008 > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc069c394 > stack pointer = 0x28:0xe10208ac > frame pointer = 0x28:0xe10208ac > 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) > trap number = 12 > > > I have tried booting with or without ACPI, in safe mode, or single user > mode and got the same message on booting. Oh, I am using GENERIC kernel. > > Any suggestions? > > Thanks, > > Hao Can you add 'options KDB' and 'options DDB' and get a stack trace? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 18:32:17 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F04B016A41F; Mon, 21 Nov 2005 18:32:17 +0000 (GMT) (envelope-from hchen@utmem.edu) Received: from hchen.utmem.edu (hchen.utmem.edu [132.192.76.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1426243D66; Mon, 21 Nov 2005 18:32:16 +0000 (GMT) (envelope-from hchen@utmem.edu) Received: from hchen.utmem.edu (localhost.localdomain [127.0.0.1]) by hchen.utmem.edu (8.12.8/8.12.8) with ESMTP id jALIWEpk023043; Mon, 21 Nov 2005 12:32:14 -0600 Received: (from hao@localhost) by hchen.utmem.edu (8.12.8/8.12.8/Submit) id jALIWEvD023041; Mon, 21 Nov 2005 12:32:14 -0600 X-Authentication-Warning: hchen.utmem.edu: hao set sender to hchen@utmem.edu using -f Date: Mon, 21 Nov 2005 12:32:14 -0600 From: Hao Chen To: John Baldwin Message-ID: <20051121183214.GA23031@utmail.utmem.edu> References: <20051119141708.GA919@utmail.utmem.edu> <200511211308.34961.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200511211308.34961.jhb@freebsd.org> User-Agent: Mutt/1.5.10i Cc: freebsd-current@freebsd.org Subject: Re: RELENG_6_0: fatal trap 12 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Hao Chen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Nov 2005 18:32:18 -0000 On Mon, Nov 21, 2005 at 01:08:34PM -0500, John Baldwin wrote: > On Saturday 19 November 2005 09:17 am, Hao Chen wrote: > > Hi, > > > > I am upgrading from 5.4 to 6.0 and got the following error message: > > > > > > Fatal trap 12: page fault while in kernel mode > > cpuid = 1; apic id = 01 > > fault virtual address = 0x480008 > > fault code = supervisor read, page not present > > instruction pointer = 0x20:0xc069c394 > > stack pointer = 0x28:0xe10208ac > > frame pointer = 0x28:0xe10208ac > > 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) > > trap number = 12 > > > > > > I have tried booting with or without ACPI, in safe mode, or single user > > mode and got the same message on booting. Oh, I am using GENERIC kernel. > > > > Any suggestions? > > > > Thanks, > > > > Hao > > Can you add 'options KDB' and 'options DDB' and get a stack trace? I replied earlier but it may not went to the list. As pointed out, it was my nvidia driver that was causing the problem. After commenting out that in the loader.conf, everything went fine. Thanks again for the many replies I got. Hao > -- > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve" = http://www.FreeBSD.org -- - : Hao Chen, Ph.D. : Instructor : Department of Pharmacology : University of Tennessee Health Science Center : Memphis, TN 38163 USA : Office: 901 448 3201 : Mobil: 901 826 1845 Mining PubMed: http://www.chilibot.net - From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 19:11:16 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D85916A41F for ; Mon, 21 Nov 2005 19:11:16 +0000 (GMT) (envelope-from eculp@bafirst.com) Received: from bafirst.com (72-12-2-214.wan.networktel.net [72.12.2.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCF9543D4C for ; Mon, 21 Nov 2005 19:11:15 +0000 (GMT) (envelope-from eculp@bafirst.com) Received: from localhost (localhost [127.0.0.1]) (uid 80) by bafirst.com with local; Mon, 21 Nov 2005 13:11:15 -0600 id 0009580F.43821BD3.0000605E Received: from local4.local.net (local4.local.net [192.168.1.4]) by mail.bafirst.com (Horde MIME library) with HTTP; Mon, 21 Nov 2005 13:11:14 -0600 Message-ID: <20051121131114.p7ed53lnkk4ckk4w@mail.bafirst.com> Date: Mon, 21 Nov 2005 13:11:14 -0600 From: eculp@bafirst.com To: freebsd-current@freebsd.org References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> <20051121004749.GA39061@xor.obsecurity.org> <43812AC7.3020506@rogers.com> <20051121020816.GA19252@xor.obsecurity.org> <438136B5.9030506@freebsd.org> <20051121030915.GC41629@dan.emsphone.com> <43813BBE.2010302@freebsd.org> <20051121034025.GD41629@dan.emsphone.com> In-Reply-To: <20051121034025.GD41629@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.1-cvs Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 19:11:16 -0000 Quoting Dan Nelson : > In the last episode (Nov 20), Paul Saab said: >> Dan Nelson wrote: >> >In the last episode (Nov 20), Paul Saab said: >> >>Chad Leigh -- Shire.Net LLC wrote: >> >>>I assume you are talking about the "phenomenon" of RAM "missing" >> >>>due to PCI and other I/O mapping into the 4GB address space? What >> >>>struck me about the OP is that the amount of RAM "missing" is more >> >>>than I have ever seen due to this. My systems are usually >> >>>3.4-3.6GB of RAM with 4GB installed, not 2.86GB (3005MB)... So >> >>>are we sure that the PCI space mapping is the problem? >> >> >> >>Enable PAE and you'll get all your ram. >> > >> >Anyone know if it's possible for the kernel to determine if any RAM >> >is mapped above the 4gb point and warn the user about how much >> >memory is unaccessable without PAE? >> >> You mean like it does now? >> "262144K of memory above 4GB ignored" > > That line didn't show up the the original poster's dmesg, though ( > http://unixmania.com/dmesg_20051120.txt ). Maybe a verbose boot would > shed more light. Thanks to all who have answered and I apologize for not finding this when searching google. I obviously needed to filter it more. As always now that I know what the problem probably is it is easy. I'm currently building kernel with PAE although it does make me a bit nervious to remotely reboot. I think I will first reboot enabling verbose with the debug.bootverbose sysctl variable since I only have remote access to the machine and no serial console. I will report back this weekend after rebooting with the PAE kernel that will hopefully work as expected. Thanks to everyone and again apologizes for not finding the solution in my searches. ed > > -- > Dan Nelson > dnelson@allantgroup.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 Mon Nov 21 19:17:21 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D64D316A421 for ; Mon, 21 Nov 2005 19:17:21 +0000 (GMT) (envelope-from eculp@bafirst.com) Received: from bafirst.com (72-12-2-214.wan.networktel.net [72.12.2.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F1F943D6E for ; Mon, 21 Nov 2005 19:17:13 +0000 (GMT) (envelope-from eculp@bafirst.com) Received: from localhost (localhost [127.0.0.1]) (uid 80) by bafirst.com with local; Mon, 21 Nov 2005 13:17:13 -0600 id 0009580F.43821D39.0000608F Received: from local4.local.net (local4.local.net [192.168.1.4]) by mail.bafirst.com (Horde MIME library) with HTTP; Mon, 21 Nov 2005 13:17:13 -0600 Message-ID: <20051121131713.bakf4048too0osk0@mail.bafirst.com> Date: Mon, 21 Nov 2005 13:17:13 -0600 From: eculp@bafirst.com To: freebsd-current@freebsd.org References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> <20051121004749.GA39061@xor.obsecurity.org> <43812AC7.3020506@rogers.com> <20051121020816.GA19252@xor.obsecurity.org> <438136B5.9030506@freebsd.org> In-Reply-To: <438136B5.9030506@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.1-cvs Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 19:17:22 -0000 Quoting Paul Saab : > Chad Leigh -- Shire.Net LLC wrote: >> I assume you are talking about the "phenomenon" of RAM "missing" >> due to PCI and other I/O mapping into the 4GB address space? What >> struck me about the OP is that the amount of RAM "missing" is more >> than I have ever seen due to this. My systems are usually 3.4-3.6GB >> of RAM with 4GB installed, not 2.86GB (3005MB)... So are we sure >> that the PCI space mapping is the problem? >> > Enable PAE and you'll get all your ram. Done that but I am going to wait until early tomorrow morning to reboot because I want to get a verbose boot with this kernel and then try the PAE kernel, for whatever. Thanks to all for your help, ed From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 19:27:11 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CB8716A41F; Mon, 21 Nov 2005 19:27:11 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63A3B43D49; Mon, 21 Nov 2005 19:27:10 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jALJOeaV045045; Mon, 21 Nov 2005 12:24:40 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 21 Nov 2005 12:24:40 -0700 (MST) Message-Id: <20051121.122440.85370117.imp@bsdimp.com> To: jhb@freebsd.org From: Warner Losh In-Reply-To: <200511211307.05043.jhb@freebsd.org> References: <20051120042536.E72D816A421@hub.freebsd.org> <20051120.210457.109704843.imp@bsdimp.com> <200511211307.05043.jhb@freebsd.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 21 Nov 2005 12:24:41 -0700 (MST) Cc: wpaul@freebsd.org, craig@xfoil.gank.org, freebsd-current@freebsd.org, current@freebsd.org, tillman@seekingfire.com Subject: Re: Compaq ProLiant 1600 server freezes when detecting keyboard controller X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 19:27:11 -0000 From: John Baldwin Subject: Re: Compaq ProLiant 1600 server freezes when detecting keyboard controller Date: Mon, 21 Nov 2005 13:07:02 -0500 > On Sunday 20 November 2005 11:04 pm, M. Warner Losh wrote: > > In message: <20051120042536.E72D816A421@hub.freebsd.org> > > > > wpaul@freebsd.org (Bill Paul) writes: > > : Our PCI code > > : then comes along and enables all of the devices but doesn't necessarily > > : update the base address registers on some of them, which has the effect > > : of mapping one of the PCI devices at physical address 0. > > > > Actually, that bug has been fixed in recent versions of > > FreeBSD-current, and should be fixed in 6.0. I recall merging changes > > to 6.0 just before the release. The problem was that the host bridge > > wasn't properly setting a range. If that's not the case, then I'd > > like to know about it... > > No, the bug was fixed, but that wasn't the fix. The fix was to bail out > earlier if a BAR's base was 0 and not enable IO or MEM decoding unless a BAR > had a valid base (where 0 and 0xfffffff are both invalid bases). Ah, that's the other bug we fixed... Warner From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 19:27:11 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CB8716A41F; Mon, 21 Nov 2005 19:27:11 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63A3B43D49; Mon, 21 Nov 2005 19:27:10 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jALJOeaV045045; Mon, 21 Nov 2005 12:24:40 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 21 Nov 2005 12:24:40 -0700 (MST) Message-Id: <20051121.122440.85370117.imp@bsdimp.com> To: jhb@freebsd.org From: Warner Losh In-Reply-To: <200511211307.05043.jhb@freebsd.org> References: <20051120042536.E72D816A421@hub.freebsd.org> <20051120.210457.109704843.imp@bsdimp.com> <200511211307.05043.jhb@freebsd.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 21 Nov 2005 12:24:41 -0700 (MST) Cc: wpaul@freebsd.org, craig@xfoil.gank.org, freebsd-current@freebsd.org, current@freebsd.org, tillman@seekingfire.com Subject: Re: Compaq ProLiant 1600 server freezes when detecting keyboard controller X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 19:27:11 -0000 From: John Baldwin Subject: Re: Compaq ProLiant 1600 server freezes when detecting keyboard controller Date: Mon, 21 Nov 2005 13:07:02 -0500 > On Sunday 20 November 2005 11:04 pm, M. Warner Losh wrote: > > In message: <20051120042536.E72D816A421@hub.freebsd.org> > > > > wpaul@freebsd.org (Bill Paul) writes: > > : Our PCI code > > : then comes along and enables all of the devices but doesn't necessarily > > : update the base address registers on some of them, which has the effect > > : of mapping one of the PCI devices at physical address 0. > > > > Actually, that bug has been fixed in recent versions of > > FreeBSD-current, and should be fixed in 6.0. I recall merging changes > > to 6.0 just before the release. The problem was that the host bridge > > wasn't properly setting a range. If that's not the case, then I'd > > like to know about it... > > No, the bug was fixed, but that wasn't the fix. The fix was to bail out > earlier if a BAR's base was 0 and not enable IO or MEM decoding unless a BAR > had a valid base (where 0 and 0xfffffff are both invalid bases). Ah, that's the other bug we fixed... Warner From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 20:01:23 2005 Return-Path: X-Original-To: current@FreeBSD.ORG Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB2A216A41F; Mon, 21 Nov 2005 20:01:23 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (nagual.pp.ru [194.87.13.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA0DF43D45; Mon, 21 Nov 2005 20:01:22 +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.4/8.13.4) with ESMTP id jALK1K3Q075530; Mon, 21 Nov 2005 23:01:20 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.4/8.13.4/Submit) id jALK1KeF075495; Mon, 21 Nov 2005 23:01:20 +0300 (MSK) (envelope-from ache) Date: Mon, 21 Nov 2005 23:01:20 +0300 From: Andrey Chernov To: Gleb Smirnoff Message-ID: <20051121200120.GA42349@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Gleb Smirnoff , current@FreeBSD.ORG, gnome@FreeBSD.ORG References: <20051118131131.GA96190@nagual.pp.ru> <20051121110521.GN24212@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051121110521.GN24212@cell.sick.ru> User-Agent: Mutt/1.5.11 Cc: gnome@FreeBSD.ORG, current@FreeBSD.ORG Subject: gconf2? [was Re: KSE: whom to blame, -current SMP or firefox?] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 20:01:23 -0000 On Mon, Nov 21, 2005 at 02:05:21PM +0300, Gleb Smirnoff wrote: > this is not SMP problem, I have observed it on UP. I've faced this problem > with firefox, too. I bet that removing the gconf-2 port will allow you to > install firefox. Yes, removing 'gconf2' port fix the problem! But... Strange thing remains. Exact the same, recent 'gconf2' port installed on the UP machine where 'firefox' installation not hangs and it not produce any bad effects... -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 20:40:31 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12A6816A422 for ; Mon, 21 Nov 2005 20:40:31 +0000 (GMT) (envelope-from victor@bsdes.net) Received: from alf.dyndns.ws (244.Red-217-126-240.staticIP.rima-tde.net [217.126.240.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07C3743D46 for ; Mon, 21 Nov 2005 20:40:29 +0000 (GMT) (envelope-from victor@bsdes.net) Received: from alf.dyndns.ws (pato.euesrg02.net [192.168.0.3]) by alf.dyndns.ws (8.13.1/8.13.1) with ESMTP id jALKeQcG067000 for ; Mon, 21 Nov 2005 21:40:26 +0100 (CET) (envelope-from victor@bsdes.net) Date: Mon, 21 Nov 2005 21:40:19 +0100 From: Victor Balada Diaz To: freebsd-current@freebsd.org Message-ID: <20051121204018.GC760@pato.euesrg02.net> References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> <20051121004749.GA39061@xor.obsecurity.org> <43812AC7.3020506@rogers.com> <20051121020816.GA19252@xor.obsecurity.org> <438136B5.9030506@freebsd.org> <20051121030915.GC41629@dan.emsphone.com> <43813BBE.2010302@freebsd.org> <20051121034025.GD41629@dan.emsphone.com> <20051121131114.p7ed53lnkk4ckk4w@mail.bafirst.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051121131114.p7ed53lnkk4ckk4w@mail.bafirst.com> User-Agent: Mutt/1.4.2.1i Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 20:40:31 -0000 On Mon, Nov 21, 2005 at 01:11:14PM -0600, eculp@bafirst.com wrote: > Thanks to all who have answered and I apologize for not finding this > when searching google. I obviously needed to filter it more. As > always now that I know what the problem probably is it is easy. > > I'm currently building kernel with PAE although it does make me a bit > nervious to remotely reboot. I think I will first reboot enabling > verbose with the debug.bootverbose sysctl variable since I only have > remote access to the machine and no serial console. > > I will report back this weekend after rebooting with the PAE kernel > that will hopefully work as expected. You can use nextboot(8) to try the new kernel in a 'safe' way. -- La prueba mas fehaciente de que existe vida inteligente en otros planetas, es que no han intentado contactar con nosotros. From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 21:01:30 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3031316A492 for ; Mon, 21 Nov 2005 21:01:30 +0000 (GMT) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA66343D67 for ; Mon, 21 Nov 2005 21:01:24 +0000 (GMT) (envelope-from lists@jnielsen.net) Received: from localhost (ns1 [69.55.238.237]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id jALL1M1f073589; Mon, 21 Nov 2005 13:01:23 -0800 (PST) (envelope-from lists@jnielsen.net) From: John Nielsen To: current@freebsd.org Date: Mon, 21 Nov 2005 16:01:20 -0500 User-Agent: KMail/1.8.3 X-Face: #X5#Y*q>F:]zT!DegL3z5Xo'^MN[$8k\[4^3rN~wm=s=Uw(sW}R?3b^*f1Wu*.<=?utf-8?q?of=5F4NrS=0A=09P*M/9CpxDo!D6?=)IY1w<9B1jB; tBQf[RU-R<,I)e"$q7N7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511211601.21278.lists@jnielsen.net> X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on ns1.jnielsen.net X-Virus-Status: Clean Cc: cyrille.lefevre@laposte.net Subject: Re: kern/71142: [syscons] [patch] add vesa [1024x768] mode support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 21:01:30 -0000 This is great! I recently updated a tablet PC to -CURRENT just so I could use the VESA mode support in syscons, and I'm very pleased with the result. One thing I noticed--there doesn't seem to be a way to change or specify the font size. The font size used seems to depend on the mode and font size being used prior to setting the VESA mode. For instance, on the tablet in question, mode 280 is a 1024x768x32 video mode. I am using cp437 fonts and I have them specified for all three font sizes. If I run: # vidcontrol VGA_80x25 followed by: # vidcontrol MODE_280 I get a 128x48 console using, I presume, the 8x16 font. If I then run: # vidcontrol VGA_80x50 followed by # vidcontrol MODE_280 I get a 128x96 console using, I presume, the 8x8 font. Would it be possible/easy to make the behavior consistent (same result for a given command regardless of prior state) and (ideally) user-controlled? If the -g flag is used, the best behavior might be to automatically select the largest font that will allow the requested geometry within the requested video mode. If the requested geometry is not possible within the requested video mode, either generate an error (and don't change the mode), or automatically select the smallest font and use the highest geometry available within the requested mode. Should I write this up as a bug report? Unfortunately I don't know where to begin as far as an actual patch. I am of course more than happy to test any patches that might appear. Thanks, JN From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 21:15:05 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF80116A420; Mon, 21 Nov 2005 21:15:04 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39F3C43D53; Mon, 21 Nov 2005 21:14:21 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2381085 for multiple; Mon, 21 Nov 2005 16:14:22 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jALLE8Uh071582; Mon, 21 Nov 2005 16:14:08 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-sparc64@freebsd.org Date: Mon, 21 Nov 2005 16:14:14 -0500 User-Agent: KMail/1.8.2 References: <5D4CE421-AC74-40D6-AB53-836630BB8F19@xcllnt.net> <200511210949.12455.jhb@freebsd.org> In-Reply-To: <200511210949.12455.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511211614.16590.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: alpha@freebsd.org, current@freebsd.org, freebsd-alpha@freebsd.org, sparc64@freebsd.org Subject: Re: dc(4) related misalignment trap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 21:15:05 -0000 On Monday 21 November 2005 09:49 am, John Baldwin wrote: > > Register s3 holds the sp variable ($2 in kgdb) > > Register t0 holds the result the left-hand side of the statement, which > > is not properly aligned for a 16-bit load ($7 = register t0 + 8). > > > > Rough patch to fix the problem attached: > > I think de(4) would need the same fix as well at least. Once I fixed another bug with de(4) due to ru@'s recent changes I wasn't able to reproduce an alignment trap with de(4) on my alpha, so although I have a patch for de(4) I can't test it. How are you triggering the alignment fault? Do you have something other than 'ifconfig_dc0="DHCP"' in /etc/rc.conf? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 21:26:29 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D88F716A41F; Mon, 21 Nov 2005 21:26:28 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B0F643E76; Mon, 21 Nov 2005 21:23:38 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2381563 for multiple; Mon, 21 Nov 2005 16:23:41 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jALLNRMM071658; Mon, 21 Nov 2005 16:23:27 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-sparc64@freebsd.org Date: Mon, 21 Nov 2005 16:23:33 -0500 User-Agent: KMail/1.8.2 References: <5D4CE421-AC74-40D6-AB53-836630BB8F19@xcllnt.net> <200511210949.12455.jhb@freebsd.org> <200511211614.16590.jhb@freebsd.org> In-Reply-To: <200511211614.16590.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511211623.35777.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: alpha@freebsd.org, current@freebsd.org, freebsd-alpha@freebsd.org, sparc64@freebsd.org Subject: Re: dc(4) related misalignment trap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 21:26:29 -0000 On Monday 21 November 2005 04:14 pm, John Baldwin wrote: > On Monday 21 November 2005 09:49 am, John Baldwin wrote: > > > Register s3 holds the sp variable ($2 in kgdb) > > > Register t0 holds the result the left-hand side of the statement, which > > > is not properly aligned for a 16-bit load ($7 = register t0 + 8). > > > > > > Rough patch to fix the problem attached: > > > > I think de(4) would need the same fix as well at least. > > Once I fixed another bug with de(4) due to ru@'s recent changes I wasn't > able to reproduce an alignment trap with de(4) on my alpha, so although I > have a patch for de(4) I can't test it. How are you triggering the > alignment fault? Do you have something other than 'ifconfig_dc0="DHCP"' in > /etc/rc.conf? Check that, it would help to let the multiuser boot finish before firing off the e-mail. I did indeed get the alignment fault during dhcp, so I'll be testing that alignment patch in a minute or so. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 21:51:41 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C72F016A41F; Mon, 21 Nov 2005 21:51:41 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9341943D75; Mon, 21 Nov 2005 21:51:33 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2382819 for multiple; Mon, 21 Nov 2005 16:51:43 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jALLpTB3071836; Mon, 21 Nov 2005 16:51:29 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-sparc64@freebsd.org Date: Mon, 21 Nov 2005 16:51:35 -0500 User-Agent: KMail/1.8.2 References: <5D4CE421-AC74-40D6-AB53-836630BB8F19@xcllnt.net> <200511211614.16590.jhb@freebsd.org> <200511211623.35777.jhb@freebsd.org> In-Reply-To: <200511211623.35777.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511211651.36569.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: alpha@freebsd.org, current@freebsd.org Subject: Re: dc(4) related misalignment trap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 21:51:42 -0000 On Monday 21 November 2005 04:23 pm, John Baldwin wrote: > On Monday 21 November 2005 04:14 pm, John Baldwin wrote: > > On Monday 21 November 2005 09:49 am, John Baldwin wrote: > > > > Register s3 holds the sp variable ($2 in kgdb) > > > > Register t0 holds the result the left-hand side of the statement, > > > > which is not properly aligned for a 16-bit load ($7 = register t0 + > > > > 8). > > > > > > > > Rough patch to fix the problem attached: > > > > > > I think de(4) would need the same fix as well at least. > > > > Once I fixed another bug with de(4) due to ru@'s recent changes I wasn't > > able to reproduce an alignment trap with de(4) on my alpha, so although I > > have a patch for de(4) I can't test it. How are you triggering the > > alignment fault? Do you have something other than 'ifconfig_dc0="DHCP"' > > in /etc/rc.conf? > > Check that, it would help to let the multiuser boot finish before firing > off the e-mail. I did indeed get the alignment fault during dhcp, so I'll > be testing that alignment patch in a minute or so. Ok, so the same change Marcel posted for dc(4) fixed de(4) as well, so Marcel, I think you should be good to go to commit your dc(4) patch. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 22:20:07 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA6BD16A41F for ; Mon, 21 Nov 2005 22:20:07 +0000 (GMT) (envelope-from chad@shire.net) Received: from hobbiton.shire.net (mail.shire.net [166.70.252.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 616DD43D5F for ; Mon, 21 Nov 2005 22:20:07 +0000 (GMT) (envelope-from chad@shire.net) Received: from [67.161.222.227] (helo=[192.168.99.68]) by hobbiton.shire.net with esmtpa (Exim 4.51) id 1EeK18-000JXW-8P; Mon, 21 Nov 2005 15:20:06 -0700 In-Reply-To: <4382475D.6080202@deadcafe.de> References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> <20051121004749.GA39061@xor.obsecurity.org> <43812AC7.3020506@rogers.com> <20051121020816.GA19252@xor.obsecurity.org> <4381FE62.5040208@deadcafe.de> <1513AD48-E08F-4670-A82B-E8D2D363F1E9@shire.net> <4382475D.6080202@deadcafe.de> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <3FBF10CD-D4A1-4B00-B84E-4E113F50F0A6@shire.net> Content-Transfer-Encoding: 7bit From: "Chad Leigh -- Shire.Net LLC" Date: Mon, 21 Nov 2005 15:20:06 -0700 To: Daniel Rock X-Mailer: Apple Mail (2.746.2) X-SA-Exim-Connect-IP: 67.161.222.227 X-SA-Exim-Mail-From: chad@shire.net X-SA-Exim-Scanned: No (on hobbiton.shire.net); SAEximRunCond expanded to false Cc: current@freebsd.org Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 22:20:08 -0000 On Nov 21, 2005, at 3:17 PM, Daniel Rock wrote: > Chad Leigh -- Shire.Net LLC schrieb: > > Yes, but in your case the real memory is > 4gb so of course the > amount > > mapped would be less. I have never seen on any of my > motherboards, > > > 1Gb getting mapped when the physical memory is only 4GB > > The real memory is *exactly* 4GB. The FreeBSD boot messages are > confusing: > "real memory" just means "highest memory location". Your real "physical" memory showed in the examples (which I have since deleted) to be in the 5000 or 6000MB range if I read it correctly Chad > > > Daniel --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad@shire.net From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 23:02:40 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D8B116A41F for ; Mon, 21 Nov 2005 23:02:40 +0000 (GMT) (envelope-from eculp@bafirst.com) Received: from bafirst.com (72-12-2-214.wan.networktel.net [72.12.2.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 498D043D46 for ; Mon, 21 Nov 2005 23:02:39 +0000 (GMT) (envelope-from eculp@bafirst.com) Received: from localhost (localhost [127.0.0.1]) (uid 80) by bafirst.com with local; Mon, 21 Nov 2005 17:02:38 -0600 id 00095804.4382520E.00010C04 Received: from local4.local.net (local4.local.net [192.168.1.4]) by mail.bafirst.com (Horde MIME library) with HTTP; Mon, 21 Nov 2005 17:02:38 -0600 Message-ID: <20051121170238.45y62menj4gcgkc0@mail.bafirst.com> Date: Mon, 21 Nov 2005 17:02:38 -0600 From: eculp@bafirst.com To: freebsd-current@freebsd.org References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> <20051121004749.GA39061@xor.obsecurity.org> <43812AC7.3020506@rogers.com> <20051121020816.GA19252@xor.obsecurity.org> <438136B5.9030506@freebsd.org> <20051121030915.GC41629@dan.emsphone.com> <43813BBE.2010302@freebsd.org> <20051121034025.GD41629@dan.emsphone.com> <20051121131114.p7ed53lnkk4ckk4w@mail.bafirst.com> <20051121204018.GC760@pato.euesrg02.net> In-Reply-To: <20051121204018.GC760@pato.euesrg02.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.1-cvs Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 23:02:40 -0000 Quoting Victor Balada Diaz : > On Mon, Nov 21, 2005 at 01:11:14PM -0600, eculp@bafirst.com wrote: >> Thanks to all who have answered and I apologize for not finding this >> when searching google. I obviously needed to filter it more. As >> always now that I know what the problem probably is it is easy. >> >> I'm currently building kernel with PAE although it does make me a bit >> nervious to remotely reboot. I think I will first reboot enabling >> verbose with the debug.bootverbose sysctl variable since I only have >> remote access to the machine and no serial console. >> >> I will report back this weekend after rebooting with the PAE kernel >> that will hopefully work as expected. > > You can use nextboot(8) to try the new kernel in a 'safe' way. I had never seen nexboot. Neat. I'm going to give it a try. Thanks for the tip, Victor. ed From owner-freebsd-current@FreeBSD.ORG Tue Nov 22 01:28:13 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 24E6216A41F; Tue, 22 Nov 2005 01:28:13 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 839B443D6A; Tue, 22 Nov 2005 01:27:50 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from [192.168.4.250] (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.13.4/8.13.4) with ESMTP id jAM1RnDQ039215; Mon, 21 Nov 2005 17:27:49 -0800 (PST) (envelope-from marcel@xcllnt.net) In-Reply-To: <200511211651.36569.jhb@freebsd.org> References: <5D4CE421-AC74-40D6-AB53-836630BB8F19@xcllnt.net> <200511211614.16590.jhb@freebsd.org> <200511211623.35777.jhb@freebsd.org> <200511211651.36569.jhb@freebsd.org> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <5B81B657-00AF-46C7-A94E-1C330435328C@xcllnt.net> Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Mon, 21 Nov 2005 17:27:48 -0800 To: John Baldwin X-Mailer: Apple Mail (2.746.2) Cc: alpha@freebsd.org, freebsd-sparc64@freebsd.org, current@freebsd.org Subject: Re: dc(4) related misalignment trap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Nov 2005 01:28:13 -0000 On Nov 21, 2005, at 1:51 PM, John Baldwin wrote: > On Monday 21 November 2005 04:23 pm, John Baldwin wrote: >> On Monday 21 November 2005 04:14 pm, John Baldwin wrote: >>> On Monday 21 November 2005 09:49 am, John Baldwin wrote: >>>>> Register s3 holds the sp variable ($2 in kgdb) >>>>> Register t0 holds the result the left-hand side of the statement, >>>>> which is not properly aligned for a 16-bit load ($7 = register >>>>> t0 + >>>>> 8). >>>>> >>>>> Rough patch to fix the problem attached: >>>> >>>> I think de(4) would need the same fix as well at least. >>> >>> Once I fixed another bug with de(4) due to ru@'s recent changes I >>> wasn't >>> able to reproduce an alignment trap with de(4) on my alpha, so >>> although I >>> have a patch for de(4) I can't test it. How are you triggering the >>> alignment fault? Do you have something other than >>> 'ifconfig_dc0="DHCP"' >>> in /etc/rc.conf? >> >> Check that, it would help to let the multiuser boot finish before >> firing >> off the e-mail. I did indeed get the alignment fault during dhcp, >> so I'll >> be testing that alignment patch in a minute or so. > > Ok, so the same change Marcel posted for dc(4) fixed de(4) as well, > so Marcel, > I think you should be good to go to commit your dc(4) patch. Will do. Thanks for taking care of de(4). -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 17:05:57 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D38416A41F for ; Mon, 21 Nov 2005 17:05:57 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from deadcafe.de (deadcafe.de [81.169.162.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC45443D49 for ; Mon, 21 Nov 2005 17:05:56 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from dialin.t-online.de (p54A5DBF0.dip.t-dialin.net [84.165.219.240]) by deadcafe.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id jALH5mAo023958 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 21 Nov 2005 18:05:52 +0100 (CET) Received: from [172.23.7.254] (doom.rock.net [172.23.7.254]) by dialin.t-online.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id jALH5ed0014869; Mon, 21 Nov 2005 18:05:40 +0100 (CET) Message-ID: <4381FE62.5040208@deadcafe.de> Date: Mon, 21 Nov 2005 18:05:38 +0100 From: Daniel Rock User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: "Chad Leigh -- Shire.Net LLC" References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> <20051121004749.GA39061@xor.obsecurity.org> <43812AC7.3020506@rogers.com> <20051121020816.GA19252@xor.obsecurity.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.1 required=5.5 tests=FORGED_RCVD_HELO autolearn=disabled version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on deadcafe.de X-Mailman-Approved-At: Tue, 22 Nov 2005 03:00:19 +0000 Cc: current@freebsd.org, Kris Kennaway Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 17:05:57 -0000 Chad Leigh -- Shire.Net LLC schrieb: > I assume you are talking about the "phenomenon" of RAM "missing" due > to PCI and other I/O mapping into the 4GB address space? What struck > me about the OP is that the amount of RAM "missing" is more than I have > ever seen due to this. My systems are usually 3.4-3.6GB of RAM with > 4GB installed, not 2.86GB (3005MB)... So are we sure that the PCI > space mapping is the problem? This is nothing unusual. I have a machine on which over 1.25GB is mapped "out of the way". It is a Tyan Thunder K8WE (S2895). In BIOS I can choose between Hardware/Software/Disabled mapping: Hardware (requires E-stepping CPUs): real memory = 5637144576 (5376 MB) Physical memory chunk(s): 0x0000000000001000 - 0x0000000000090fff, 589824 bytes (144 pages) 0x0000000000985000 - 0x00000000a616ffff, 2776543232 bytes (677867 pages) 0x0000000100000000 - 0x000000014ffdffff, 1342046208 bytes (327648 pages) avail memory = 4109500416 (3919 MB) Software (should work regardless of stepping): real memory = 6442450944 (6144 MB) Physical memory chunk(s): 0x0000000000001000 - 0x0000000000090fff, 589824 bytes (144 pages) 0x0000000000985000 - 0x000000007ff1ffff, 2136584192 bytes (521627 pages) 0x0000000100000000 - 0x0000000174baffff, 1958412288 bytes (478128 pages) avail memory = 4085907456 (3896 MB) Disabled: real memory = 2951872512 (2815 MB) Physical memory chunk(s): 0x0000000000001000 - 0x0000000000090fff, 589824 bytes (144 pages) 0x0000000000983000 - 0x00000000aac56fff, 2855092224 bytes (697044 pages) avail memory = 2846003200 (2714 MB) Daniel From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 22:17:30 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0B3A16A41F for ; Mon, 21 Nov 2005 22:17:30 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from deadcafe.de (deadcafe.de [81.169.162.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1524743D53 for ; Mon, 21 Nov 2005 22:17:29 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from dialin.t-online.de (p54A5E60B.dip.t-dialin.net [84.165.230.11]) by deadcafe.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id jALMHQuD024290 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 21 Nov 2005 23:17:27 +0100 (CET) Received: from [172.23.7.123] (nx7000-wlan.rock.net [172.23.7.123]) by dialin.t-online.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id jALMH1NR002355; Mon, 21 Nov 2005 23:17:01 +0100 (CET) Message-ID: <4382475D.6080202@deadcafe.de> Date: Mon, 21 Nov 2005 23:17:01 +0100 From: Daniel Rock User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: "Chad Leigh -- Shire.Net LLC" References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> <20051121004749.GA39061@xor.obsecurity.org> <43812AC7.3020506@rogers.com> <20051121020816.GA19252@xor.obsecurity.org> <4381FE62.5040208@deadcafe.de> <1513AD48-E08F-4670-A82B-E8D2D363F1E9@shire.net> In-Reply-To: <1513AD48-E08F-4670-A82B-E8D2D363F1E9@shire.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.1 required=5.5 tests=FORGED_RCVD_HELO autolearn=disabled version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on deadcafe.de X-Mailman-Approved-At: Tue, 22 Nov 2005 03:05:17 +0000 Cc: current@freebsd.org, Kris Kennaway Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 22:17:31 -0000 Chad Leigh -- Shire.Net LLC schrieb: > Yes, but in your case the real memory is > 4gb so of course the amount > mapped would be less. I have never seen on any of my motherboards, > > 1Gb getting mapped when the physical memory is only 4GB The real memory is *exactly* 4GB. The FreeBSD boot messages are confusing: "real memory" just means "highest memory location". Daniel From owner-freebsd-current@FreeBSD.ORG Mon Nov 21 22:43:16 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D67A16A41F for ; Mon, 21 Nov 2005 22:43:16 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from deadcafe.de (deadcafe.de [81.169.162.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10C6143D45 for ; Mon, 21 Nov 2005 22:43:13 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from dialin.t-online.de (p54A5E60B.dip.t-dialin.net [84.165.230.11]) by deadcafe.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id jALMhBoj024323 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 21 Nov 2005 23:43:12 +0100 (CET) Received: from [172.23.7.254] (doom.rock.net [172.23.7.254]) by dialin.t-online.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id jALMh6aN003445; Mon, 21 Nov 2005 23:43:06 +0100 (CET) Message-ID: <43824D7A.2050208@deadcafe.de> Date: Mon, 21 Nov 2005 23:43:06 +0100 From: Daniel Rock User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: "Chad Leigh -- Shire.Net LLC" References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> <20051121004749.GA39061@xor.obsecurity.org> <43812AC7.3020506@rogers.com> <20051121020816.GA19252@xor.obsecurity.org> <4381FE62.5040208@deadcafe.de> <1513AD48-E08F-4670-A82B-E8D2D363F1E9@shire.net> <4382475D.6080202@deadcafe.de> <3FBF10CD-D4A1-4B00-B84E-4E113F50F0A6@shire.net> In-Reply-To: <3FBF10CD-D4A1-4B00-B84E-4E113F50F0A6@shire.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.1 required=5.5 tests=FORGED_RCVD_HELO autolearn=disabled version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on deadcafe.de X-Mailman-Approved-At: Tue, 22 Nov 2005 03:05:31 +0000 Cc: current@freebsd.org Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 21 Nov 2005 22:43:16 -0000 Chad Leigh -- Shire.Net LLC schrieb: > > On Nov 21, 2005, at 3:17 PM, Daniel Rock wrote: > >> Chad Leigh -- Shire.Net LLC schrieb: >> > Yes, but in your case the real memory is > 4gb so of course the >> amount >> > mapped would be less. I have never seen on any of my motherboards, > >> > 1Gb getting mapped when the physical memory is only 4GB >> >> The real memory is *exactly* 4GB. The FreeBSD boot messages are >> confusing: >> "real memory" just means "highest memory location". > > > Your real "physical" memory showed in the examples (which I have since > deleted) to be in the 5000 or 6000MB range if I read it correctly Should I repeat my explanation: The real memory is *exactly* 4GB. The FreeBSD boot messages are confusing: "real memory" just means "highest memory location". Daniel From owner-freebsd-current@FreeBSD.ORG Tue Nov 22 00:23:48 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6EEE616A41F; Tue, 22 Nov 2005 00:23:48 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from vms040pub.verizon.net (vms040pub.verizon.net [206.46.252.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0432543D49; Tue, 22 Nov 2005 00:23:48 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from corbulon.video-collage.com ([151.204.231.237]) by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IQB00M1YYFMU8I0@vms040.mailsrvcs.net>; Mon, 21 Nov 2005 18:23:47 -0600 (CST) Received: from mteterin.us.murex.com (195-11.customer.cloud9.net [168.100.195.11]) by corbulon.video-collage.com (8.13.4/8.13.1) with ESMTP id jAM0Nf50068635 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 Nov 2005 19:23:45 -0500 Received: from mteterin.us.murex.com (mteterin@localhost [127.0.0.1]) by mteterin.us.murex.com (8.13.4/8.13.4) with ESMTP id jAM0NZOi098709; Mon, 21 Nov 2005 19:23:35 -0500 Received: from localhost (localhost [[UNIX: localhost]]) by mteterin.us.murex.com (8.13.4/8.13.4/Submit) id jAM0NW3V098708; Mon, 21 Nov 2005 19:23:32 -0500 Date: Mon, 21 Nov 2005 19:23:32 -0500 From: Mikhail Teterin To: current@freebsd.org Message-id: <200511211923.32834.mi+mx@aldan.algebra.com> Organization: Virtual Estates, Inc. MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Content-disposition: inline X-Virus-Scanned: ClamAV devel-20050525/1181/Mon Nov 21 06:10:32 2005 on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 X-Authentication-warning: mteterin.us.murex.com: mteterin set sender to mi+mx@aldan.algebra.com using -f User-Agent: KMail/1.8.2 X-Mailman-Approved-At: Tue, 22 Nov 2005 03:05:49 +0000 Cc: amd64@freebsd.org Subject: recent 7-current broke the devel/tcltls port X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Nov 2005 00:23:48 -0000 Hello! According the pointyhat's build logs, the port started to fail its self-tests recently -- with a SIGBUS :-( Could someone running 7-current on amd64, please, investigate? I don't have such a system. Thanks! -mi From owner-freebsd-current@FreeBSD.ORG Tue Nov 22 13:10:31 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C095916A420; Tue, 22 Nov 2005 13:10:31 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw1.york.ac.uk (mail-gw1.york.ac.uk [144.32.128.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0E4F43D88; Tue, 22 Nov 2005 13:09:59 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy-128.york.ac.uk [144.32.128.160]) by mail-gw1.york.ac.uk (8.12.10/8.12.10) with ESMTP id jAMD9uSR005041; Tue, 22 Nov 2005 13:09:56 GMT Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.4/8.13.4) with ESMTP id jAMD9uLG017455; Tue, 22 Nov 2005 13:09:56 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.4/8.13.4/Submit) id jAMD9tiA017454; Tue, 22 Nov 2005 13:09:55 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: John Baldwin In-Reply-To: <200510061355.56903.jhb@FreeBSD.org> References: <1123588622.893.15.camel@buffy.york.ac.uk> <200509291210.38799.jhb@FreeBSD.org> <1128598440.25106.13.camel@buffy.york.ac.uk> <200510061355.56903.jhb@FreeBSD.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 22 Nov 2005 13:09:55 +0000 Message-Id: <1132664995.12635.8.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Cc: freebsd-current@FreeBSD.org Subject: Re: 6.0-BETA2 DRM/witness panic: Assertion j < 1000 failed at /usr/src/sys/kern/subr_witness.c:1513 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Nov 2005 13:10:32 -0000 [posted to -current rather than stable as the rest of the thread started before 6.0 was released] On Thu, 2005-10-06 at 13:55 -0400, John Baldwin wrote: > On Thursday 06 October 2005 07:34 am, Gavin Atkinson wrote: > > On Thu, 2005-09-29 at 12:10 -0400, John Baldwin wrote: > > > On Tuesday 09 August 2005 12:02 pm, Gavin Atkinson wrote: > > > > On Tue, 2005-08-09 at 10:50 -0400, John Baldwin wrote: > > > > > On Tuesday 09 August 2005 07:57 am, Gavin Atkinson wrote: > > > > > > Hi, > > > > > > > > > > > > I have a regular panic (3 times a day) on a system running > > > > > > 6.0-BETA2 which was very stable under 5.4. dmesg available at > > > > > > http://www.devrandom.co.uk/freebsd/dmesg-buffy-20050809 . The panic > > > > > > seems to relate to DRM, I have a ATI Radeon QY RV100 7000/VE card. > > > > > > > > > > Do a 'show witness', it looks like witness has a cycle somehow. > > > > > Normally these can only occur if there is a cycle in the static lock > > > > > order. > > > > > > > > http://www.devrandom.co.uk/freebsd/sh-witness-buffy-20050809 > > > > > > > > Gavin > > > > > > Do you still get this panic on more recent 6.0? > > > > I've been running a 6.0 from Friday for a week now without seeing this > > panic, so I suspect it's fixed. However, I don't remember seeing any > > commits which look like they were responsible for fixing it, is it > > possible that it's just been masked by some other commit? I'm happy to > > step back and find the responsible commit, unless you're happy that it > > was fixed for certain. > > > > Gavin > > Well, I'm not sure how you could even have triggered the panic in the first > place. If you can't reproduce it that is fine with me for now. Sadly, it looks like I spoke too soon. Since this last email, I was happily running with the kernel mentioned above without any problems, and an uptime of 40 days with the screensavers that used to trigger it running all night. I rebooted my machine a couple of days ago, and since then (and with the exact same kernel/world) the panic is back. I've updated the machine to 6-STABLE but the panic remains. I guess I was just lucky in my month without panics - they definitely still exist. I wonder if the fact that it survived so long means anything - e.g. is it a failure to initialise something that just by chance was initialised correctly that time? I'm happy to do any more investigating that you want. Gavin From owner-freebsd-current@FreeBSD.ORG Tue Nov 22 13:11:04 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B589916A455; Tue, 22 Nov 2005 13:11:03 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CECD43D86; Tue, 22 Nov 2005 13:10:58 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by rosebud.otenet.gr (8.13.4/8.13.4/Debian-1) with SMTP id jAMDAmkn001575; Tue, 22 Nov 2005 15:10:48 +0200 Received: by flame.pc (Postfix, from userid 1001) id E63B5117A2; Tue, 22 Nov 2005 15:10:24 +0200 (EET) Date: Tue, 22 Nov 2005 15:10:24 +0200 From: Giorgos Keramidas To: Mikhail Teterin Message-ID: <20051122131024.GA10161@flame.pc> References: <200511211923.32834.mi+mx@aldan.algebra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200511211923.32834.mi+mx@aldan.algebra.com> Cc: amd64@freebsd.org, current@freebsd.org Subject: Re: recent 7-current broke the devel/tcltls port X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Nov 2005 13:11:06 -0000 On 2005-11-21 19:23, Mikhail Teterin wrote: > Hello! > > According the pointyhat's build logs, the port started to fail its self-tests > recently -- with a SIGBUS :-( > > Could someone running 7-current on amd64, please, investigate? I don't have > such a system. Thanks! Hmm, I just built tcltls here on amd64: * dmesg output % CPU: Mobile AMD Athlon 64 Processor 3000+ (2004.56-MHz K8-class CPU) % Origin = "AuthenticAMD" Id = 0x10fc0 Stepping = 0 % Features=0x78bfbff % AMD Features=0xe2500800 * tcltls build log, final lines % [...] % Tests running in interp: /usr/local/bin/tclsh8.4 % Tests running in working dir: /home/ports/devel/tcltls/work/tls1.5/tests % Only running tests that match: * % Skipping test files that match: l.*.test % Only sourcing test files that match: *.test % Tests began at Tue Nov 22 14:59:07 EET 2005 % tlsIO.test % % Tests ended at Tue Nov 22 14:59:25 EET 2005 % all.tcl: Total 59 Passed 42 Skipped 17 Failed 0 % Sourced 0 Test Files. % Number of tests skipped for each constraint: % 12 doTestsWithRemoteServer % 2 notRoot % 1 testthread % 2 unexplainedFailure % flame# Does this seem ok to you? From owner-freebsd-current@FreeBSD.ORG Tue Nov 22 12:30:59 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5D5816A41F for ; Tue, 22 Nov 2005 12:30:59 +0000 (GMT) (envelope-from dsnofe@yahoo.com.cn) Received: from smtp017.mail.yahoo.com (smtp017.mail.yahoo.com [216.136.174.114]) by mx1.FreeBSD.org (Postfix) with SMTP id D2C0E43D60 for ; Tue, 22 Nov 2005 12:30:58 +0000 (GMT) (envelope-from dsnofe@yahoo.com.cn) Received: (qmail 99204 invoked from network); 22 Nov 2005 12:30:58 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.cn; h=Received:Date:From:To:Subject:Cc:In-Reply-To:References:Message-Id:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer; b=HgLzt69VgCAClVXsi3YqyiOv1qw0pITxHKMlg8LRSmgfSa30oa1wKDlXEFoVAZBkhGad0AYRh/f6xZtIJ06xMiYuNjZgCwMLF6lRoX403Srt958YJfd2JMDFaW3x/7Dno25Q1b1U2fmNPtP7m3ct8klfE3LXpgfT8lQFJBKhPso= ; Received: from unknown (HELO ?220.234.72.80?) (dsnofe@220.234.72.80 with login) by smtp017.mail.yahoo.com with SMTP; 22 Nov 2005 12:30:57 -0000 Date: Tue, 22 Nov 2005 20:30:58 +0800 From: XueFeng Deng To: Gleb Smirnoff In-Reply-To: <20051114091153.GI1647@cell.sick.ru> References: <20051114015710.48094.qmail@web15705.mail.cnb.yahoo.com> <20051114091153.GI1647@cell.sick.ru> Message-Id: <20051122202922.62EC.DSNOFE@yahoo.com.cn> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.20.04 [CN] X-Mailman-Approved-At: Tue, 22 Nov 2005 13:25:52 +0000 Cc: freebsd-current@FreeBSD.org Subject: Re: 6.0 LOR and panic on my laptop X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2005 12:30:59 -0000 hey, the patch works fine for weeks, and no panic again, thank you very much.could you commit this patch? > On Mon, Nov 14, 2005 at 09:57:09AM +0800, XueFeng Deng wrote: > X> hey, > X> yestoday, I update my laptop(HP NX7000) to 6_0, it panic when restarting. > > X> re_rxeof(c1a50000,0,c06d917a,726,c1a94380) at re_rxeof+0x33d > X> re_intr(c1a50000,0,c06e27df,225,d3942d00) at re_intr+0xca > X> ithread_loop(c19bd900,d3942d38,c06e25d6,30d,0) at ithread_loop+0x182 > X> fork_exit(c0524ef0,c19bd900,d3942d38) at fork_exit+0xc1 > X> fork_trampoline() at fork_trampoline+0x8 > > Can you please try out the attached diff? > > -- > Totus tuus, Glebius. > GLEBIUS-RIPN GLEB-RIPE -- XueFeng Deng __________________________________________________ Do You Yahoo!? ÑÅ»¢Ãâ·ÑGÓÊÏ䣭ÖйúµÚÒ»¾øÎÞÀ¬»øÓʼþɧÈų¬´óÓÊÏä http://cn.mail.yahoo.com/?id=77071 From owner-freebsd-current@FreeBSD.ORG Tue Nov 22 14:52:12 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4459D16A420; Tue, 22 Nov 2005 14:52:12 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD01E43D6A; Tue, 22 Nov 2005 14:51:51 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from corbulon.video-collage.com ([151.204.231.237]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IQD00KNR2MC8M31@vms046.mailsrvcs.net>; Tue, 22 Nov 2005 08:51:49 -0600 (CST) Received: from mteterin.us.murex.com (195-11.customer.cloud9.net [168.100.195.11]) by corbulon.video-collage.com (8.13.4/8.13.1) with ESMTP id jAMEpiJX092064 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Nov 2005 09:51:47 -0500 Received: from mteterin.us.murex.com (mteterin@localhost [127.0.0.1]) by mteterin.us.murex.com (8.13.4/8.13.4) with ESMTP id jAMEpcKE002288; Tue, 22 Nov 2005 09:51:38 -0500 Received: from localhost (localhost [[UNIX: localhost]]) by mteterin.us.murex.com (8.13.4/8.13.4/Submit) id jAMEpS0M002287; Tue, 22 Nov 2005 09:51:28 -0500 Date: Tue, 22 Nov 2005 09:51:28 -0500 From: Mikhail Teterin In-reply-to: <20051122131024.GA10161@flame.pc> To: Giorgos Keramidas Message-id: <200511220951.28429.mi+mx@aldan.algebra.com> Organization: Virtual Estates, Inc. MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline X-Virus-Scanned: ClamAV devel-20050525/1182/Mon Nov 21 14:43:47 2005 on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 References: <200511211923.32834.mi+mx@aldan.algebra.com> <20051122131024.GA10161@flame.pc> X-Authentication-warning: mteterin.us.murex.com: mteterin set sender to mi+mx@aldan.algebra.com using -f User-Agent: KMail/1.8.2 X-Mailman-Approved-At: Tue, 22 Nov 2005 15:55:21 +0000 Cc: amd64@freebsd.org, current@freebsd.org Subject: Re: recent 7-current broke the devel/tcltls port X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Nov 2005 14:52:12 -0000 > > According the pointyhat's build logs, the port started to fail its > > self-tests recently -- with a SIGBUS :-( > > > > Could someone running 7-current on amd64, please, investigate? I don't > > have such a system. Thanks! > > Hmm, I just built tcltls here on amd64: Thank you, Giorgos and Tilman, for taking the time to test this. Seems like it builds find for you on a fresh 7-current. Kris, can there be something "funny" about the cluster's amd64-machine? -mi > * dmesg output > > % CPU: Mobile AMD Athlon 64 Processor 3000+ (2004.56-MHz K8-class CPU) > % Origin = "AuthenticAMD" Id = 0x10fc0 Stepping = 0 > % > Features=0x78bfbff,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2> % AMD > Features=0xe2500800 > > * tcltls build log, final lines > > % [...] > % Tests running in interp: /usr/local/bin/tclsh8.4 > % Tests running in working dir: /home/ports/devel/tcltls/work/tls1.5/tests > % Only running tests that match: * > % Skipping test files that match: l.*.test > % Only sourcing test files that match: *.test > % Tests began at Tue Nov 22 14:59:07 EET 2005 > % tlsIO.test > % > % Tests ended at Tue Nov 22 14:59:25 EET 2005 > % all.tcl: Total 59 Passed 42 Skipped 17 Failed 0 > % Sourced 0 Test Files. > % Number of tests skipped for each constraint: > % 12 doTestsWithRemoteServer > % 2 notRoot > % 1 testthread > % 2 unexplainedFailure > % flame# > > Does this seem ok to you? From owner-freebsd-current@FreeBSD.ORG Tue Nov 22 17:52:11 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3EE2E16A41F for ; Tue, 22 Nov 2005 17:52:11 +0000 (GMT) (envelope-from jsmith@drexel.edu) Received: from smtp.mail.drexel.edu (pm2.irt.drexel.edu [144.118.29.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id F108443D6B for ; Tue, 22 Nov 2005 17:52:07 +0000 (GMT) (envelope-from jsmith@drexel.edu) Received: from smtp.mail.drexel.edu (localhost.localdomain [127.0.0.1]) by smtp.mail.drexel.edu (Postfix) with SMTP id A641811667A for ; Tue, 22 Nov 2005 12:52:05 -0500 (EST) Received: from vorpal.math.drexel.edu (vorpal.math.drexel.edu [129.25.6.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mail.drexel.edu (Postfix) with ESMTP id 952B011660A for ; Tue, 22 Nov 2005 12:52:05 -0500 (EST) Received: from [IPv6:::1] (vorpal.math.drexel.edu [127.0.0.1]) by vorpal.math.drexel.edu (8.13.4/8.13.4) with ESMTP id jAMHq1TE013626 for ; Tue, 22 Nov 2005 12:52:02 -0500 Message-ID: <43835AC4.3080002@drexel.edu> Date: Tue, 22 Nov 2005 12:52:04 -0500 From: "Justin R. Smith" Organization: Drexel University User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051122) 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 Cc: Subject: ATAPICAM causes kernel panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2005 17:52:11 -0000 I installed the FreeBSD 6.0 release and it booted fine. Then I upgraded to stable as of yesterday and added the ATAPICAM driver, rebuilt world and kernel. On rebooting, it hung for 15 minutes on creating one of the simulated SCSI CD drives and finally paniced on a insufficient kernel memory. Rebuilding the kernel without the ATAPICAM driver solved the problem. My question: is it possible to use cdrtools without SCSI emulation? In the Linux world, SCSI emulation is depreciated and will be eliminated at some point. The cdrtools work fine using the regular Linux cdrom drivers (which, oddly, treat CD drives as ordinary hard drives). Here's my dmesg 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-STABLE #0: Sun Nov 20 15:06:19 EST 2005 root@jsmith.org:/usr/obj/usr/src/sys/MYKERNEL Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 3.20GHz (3191.19-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf33 Stepping = 3 Features=0xbfebfbff Features2=0x41d Hyperthreading: 2 logical CPUs real memory = 1072889856 (1023 MB) avail memory = 1036771328 (988 MB) ACPI APIC Table: ioapic0: Changing APIC ID to 2 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 irqs 0-23 on motherboard module_register_init: MOD_LOAD (splash_bmp, 0xc0a3f9e4, 0) error 2 module_register_init: MOD_LOAD (splash_pcx, 0xc0a4378c, 0) error 2 npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) pci_link0: irq 11 on acpi0 pci_link1: irq 10 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 0 on acpi0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 nvidia0: mem 0xfd000000-0xfdffffff,0xe0000000-0xe7ffffff irq 16 at device 0.0 on pci1 nvidia0: [GIANT-LOCKED] atapci0: port 0xbc00-0xbc07,0xb800-0xb803,0xb400-0xb407,0xb000-0xb003,0xac00-0xac0f irq 18 at device 10.0 on pci0 ata2: on atapci0 ata3: on atapci0 atapci1: port 0xec00-0xec07,0xe800-0xe803,0xe400-0xe407,0xe000-0xe003,0xdc00-0xdc0f,0xd800-0xd8ff irq 20 at device 15.0 on pci0 ata4: on atapci1 ata5: on atapci1 atapci2: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 15.1 on pci0 ata0: on atapci2 ata1: on atapci2 uhci0: port 0xc000-0xc01f irq 21 at device 16.0 on pci0 uhci0: [GIANT-LOCKED] 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 uhci1: port 0xc400-0xc41f irq 21 at device 16.1 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 uhci2: port 0xc800-0xc81f irq 21 at device 16.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xcc00-0xcc1f irq 21 at device 16.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xfebff800-0xfebff8ff irq 21 at device 16.4 on pci0 ehci0: [GIANT-LOCKED] usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: VIA EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered ugen0: hewlett packard hp scanjet, rev 2.00/1.00, addr 2 isab0: at device 17.0 on pci0 isa0: on isab0 pcm0: port 0xd000-0xd0ff irq 22 at device 17.5 on pci0 pcm0: [GIANT-LOCKED] pcm0: vr0: port 0xd400-0xd4ff mem 0xfebffc00-0xfebffcff irq 23 at device 18.0 on pci0 miibus0: on vr0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto vr0: Ethernet address: 00:0b:6a:a3:e3:52 acpi_button0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 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 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ulpt0: EPSON USB Printer, rev 1.10/1.00, addr 2, iclass 7/1 ulpt0: using bi-directional mode Timecounter "TSC" frequency 3191190952 Hz quality 800 Timecounters tick every 1.000 msec ad0: 38172MB at ata0-master UDMA133 ad2: 38204MB at ata1-master UDMA100 acd0: DMA limited to UDMA33, device found non-ATA66 cable acd0: DVDR at ata2-master UDMA33 acd1: DMA limited to UDMA33, device found non-ATA66 cable acd1: DVDROM at ata3-master UDMA33 ad8: 76319MB at ata4-master SATA150 Trying to mount root from ufs:/dev/ad2s1a $ From owner-freebsd-current@FreeBSD.ORG Tue Nov 22 17:54:09 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CB7A16A41F for ; Tue, 22 Nov 2005 17:54:09 +0000 (GMT) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFE3743D5E for ; Tue, 22 Nov 2005 17:53:56 +0000 (GMT) (envelope-from lists@jnielsen.net) Received: from localhost (ns1 [69.55.238.237]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id jAMHro1f095054; Tue, 22 Nov 2005 09:53:51 -0800 (PST) (envelope-from lists@jnielsen.net) From: John Nielsen To: swildner@gmail.com Date: Tue, 22 Nov 2005 12:53:45 -0500 User-Agent: KMail/1.8.3 References: <200511211601.21278.lists@jnielsen.net> <1132675027.375055.81000@f14g2000cwb.googlegroups.com> In-Reply-To: <1132675027.375055.81000@f14g2000cwb.googlegroups.com> X-Face: #X5#Y*q>F:]zT!DegL3z5Xo'^MN[$8k\[4^3rN~wm=s=Uw(sW}R?3b^*f1Wu*.<=?utf-8?q?of=5F4NrS=0A=09P*M/9CpxDo!D6?=)IY1w<9B1jB; tBQf[RU-R<,I)e"$q7N7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511221253.46662.lists@jnielsen.net> X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on ns1.jnielsen.net X-Virus-Status: Clean Cc: current@freebsd.org, cyrille.lefevre@laposte.net Subject: Re: kern/71142: [syscons] [patch] add vesa [1024x768] mode support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Nov 2005 17:54:09 -0000 On Tuesday 22 November 2005 10:57 am, swildner@gmail.com wrote: > John, > > you can select fonts for vesa modes with vidcontrol's -f option: > > Example: > > # vidcontrol -f 8x14 iso-8x14.fnt MODE_xxx > > For text modes, I don't think you can set a font size. > > Sascha > > P.S. Sorry this is private email only (Google groups is giving me > trouble). Thank you! (And thanks to Eric Kjeldergaard, who also clued me in to this). I've never used -f on the same vidcontrol command with a new video mode; only beforehand as in my original e-mail. The above method works very well. JN From owner-freebsd-current@FreeBSD.ORG Tue Nov 22 17:59:37 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5549016A41F for ; Tue, 22 Nov 2005 17:59:37 +0000 (GMT) (envelope-from thomas@FreeBSD.ORG) Received: from melamine.cuivre.fr.eu.org (melusine.cuivre.fr.eu.org [82.225.155.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40E2E43D45 for ; Tue, 22 Nov 2005 17:59:36 +0000 (GMT) (envelope-from thomas@FreeBSD.ORG) Received: by melamine.cuivre.fr.eu.org (Postfix, from userid 1000) id 000E95C3AB; Tue, 22 Nov 2005 18:59:34 +0100 (CET) Date: Tue, 22 Nov 2005 18:59:34 +0100 From: Thomas Quinot To: "Justin R. Smith" Message-ID: <20051122175934.GA35864@melamine.cuivre.fr.eu.org> References: <43835AC4.3080002@drexel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43835AC4.3080002@drexel.edu> X-message-flag: WARNING! Using Outlook can damage your computer. User-Agent: Mutt/1.5.9i Cc: freebsd-current@FreeBSD.org Subject: Re: ATAPICAM causes kernel panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2005 17:59:37 -0000 * Justin R. Smith, 2005-11-22 : > On rebooting, it hung for 15 minutes on creating one of the simulated > SCSI CD drives and finally paniced on a insufficient kernel memory. > Rebuilding the kernel without the ATAPICAM driver solved the problem. Can you get a backtrace at the panic point? Obviously something is stuck in a loop, allocating memory until exhaustion. Thomas. From owner-freebsd-current@FreeBSD.ORG Tue Nov 22 19:23:30 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 018FF16A41F for ; Tue, 22 Nov 2005 19:23:29 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id B39D343D94 for ; Tue, 22 Nov 2005 19:22:44 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2437290 for multiple; Tue, 22 Nov 2005 14:22:33 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jAMJMH2J079237; Tue, 22 Nov 2005 14:22:17 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 22 Nov 2005 14:15:26 -0500 User-Agent: KMail/1.8.2 References: <1123588622.893.15.camel@buffy.york.ac.uk> <200510061355.56903.jhb@FreeBSD.org> <1132664995.12635.8.camel@buffy.york.ac.uk> In-Reply-To: <1132664995.12635.8.camel@buffy.york.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511221415.27771.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Subject: Re: 6.0-BETA2 DRM/witness panic: Assertion j < 1000 failed at /usr/src/sys/kern/subr_witness.c:1513 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Nov 2005 19:23:30 -0000 On Tuesday 22 November 2005 08:09 am, Gavin Atkinson wrote: > [posted to -current rather than stable as the rest of the thread started > before 6.0 was released] > > On Thu, 2005-10-06 at 13:55 -0400, John Baldwin wrote: > > On Thursday 06 October 2005 07:34 am, Gavin Atkinson wrote: > > > On Thu, 2005-09-29 at 12:10 -0400, John Baldwin wrote: > > > > On Tuesday 09 August 2005 12:02 pm, Gavin Atkinson wrote: > > > > > On Tue, 2005-08-09 at 10:50 -0400, John Baldwin wrote: > > > > > > On Tuesday 09 August 2005 07:57 am, Gavin Atkinson wrote: > > > > > > > Hi, > > > > > > > > > > > > > > I have a regular panic (3 times a day) on a system running > > > > > > > 6.0-BETA2 which was very stable under 5.4. dmesg available at > > > > > > > http://www.devrandom.co.uk/freebsd/dmesg-buffy-20050809 . The > > > > > > > panic seems to relate to DRM, I have a ATI Radeon QY RV100 > > > > > > > 7000/VE card. > > > > > > > > > > > > Do a 'show witness', it looks like witness has a cycle somehow. > > > > > > Normally these can only occur if there is a cycle in the static > > > > > > lock order. > > > > > > > > > > http://www.devrandom.co.uk/freebsd/sh-witness-buffy-20050809 > > > > > > > > > > Gavin > > > > > > > > Do you still get this panic on more recent 6.0? > > > > > > I've been running a 6.0 from Friday for a week now without seeing this > > > panic, so I suspect it's fixed. However, I don't remember seeing any > > > commits which look like they were responsible for fixing it, is it > > > possible that it's just been masked by some other commit? I'm happy to > > > step back and find the responsible commit, unless you're happy that it > > > was fixed for certain. > > > > > > Gavin > > > > Well, I'm not sure how you could even have triggered the panic in the > > first place. If you can't reproduce it that is fine with me for now. > > Sadly, it looks like I spoke too soon. Since this last email, I was > happily running with the kernel mentioned above without any problems, > and an uptime of 40 days with the screensavers that used to trigger it > running all night. I rebooted my machine a couple of days ago, and > since then (and with the exact same kernel/world) the panic is back. > I've updated the machine to 6-STABLE but the panic remains. > > I guess I was just lucky in my month without panics - they definitely > still exist. I wonder if the fact that it survived so long means > anything - e.g. is it a failure to initialise something that just by > chance was initialised correctly that time? I'm happy to do any more > investigating that you want. Have you tried doing a 'show locks' when you get this panic at the db> prompt? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 22 20:10:19 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1B7616A420; Tue, 22 Nov 2005 20:10:19 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B42543D8F; Tue, 22 Nov 2005 20:10:04 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 8FAD51A3C1C; Tue, 22 Nov 2005 12:09:56 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6733351590; Tue, 22 Nov 2005 15:09:55 -0500 (EST) Date: Tue, 22 Nov 2005 15:09:55 -0500 From: Kris Kennaway To: Mikhail Teterin Message-ID: <20051122200953.GB70767@xor.obsecurity.org> References: <200511211923.32834.mi+mx@aldan.algebra.com> <20051122131024.GA10161@flame.pc> <200511220951.28429.mi+mx@aldan.algebra.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ADZbWkCsHQ7r3kzd" Content-Disposition: inline In-Reply-To: <200511220951.28429.mi+mx@aldan.algebra.com> User-Agent: Mutt/1.4.2.1i Cc: amd64@freebsd.org, Giorgos Keramidas , current@freebsd.org Subject: Re: recent 7-current broke the devel/tcltls port X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Nov 2005 20:10:19 -0000 --ADZbWkCsHQ7r3kzd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 22, 2005 at 09:51:28AM -0500, Mikhail Teterin wrote: > > > According the pointyhat's build logs, the port started to fail its > > > self-tests recently -- with a SIGBUS :-( > > > > > > Could someone running 7-current on amd64, please, investigate? I don't > > > have such a system. Thanks! > > > > Hmm, I just built tcltls here on amd64: >=20 > Thank you, Giorgos and Tilman, for taking the time to test this. Seems li= ke it=20 > builds find for you on a fresh 7-current. >=20 > Kris, can there be something "funny" about the cluster's amd64-machine? Perhaps it's not up-to-date enough. Kris --ADZbWkCsHQ7r3kzd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDg3sQWry0BWjoQKURAg24AKCwQfh7u5FjFPdUOtr6443cIfUfvwCfZ8X4 hWBy6ZugNlkioAUqzSWqbNk= =pChd -----END PGP SIGNATURE----- --ADZbWkCsHQ7r3kzd-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 22 21:49:30 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA05716A41F; Tue, 22 Nov 2005 21:49:30 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E3DD43D68; Tue, 22 Nov 2005 21:49:30 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 4199A1A3C24; Tue, 22 Nov 2005 13:49:30 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 792C251585; Tue, 22 Nov 2005 16:49:29 -0500 (EST) Date: Tue, 22 Nov 2005 16:49:29 -0500 From: Kris Kennaway To: Giorgos Keramidas Message-ID: <20051122214929.GA73316@xor.obsecurity.org> References: <200511211923.32834.mi+mx@aldan.algebra.com> <20051122131024.GA10161@flame.pc> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3V7upXqbjpZ4EhLz" Content-Disposition: inline In-Reply-To: <20051122131024.GA10161@flame.pc> User-Agent: Mutt/1.4.2.1i Cc: amd64@freebsd.org, Mikhail Teterin , current@freebsd.org Subject: Re: recent 7-current broke the devel/tcltls port X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Nov 2005 21:49:31 -0000 --3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 22, 2005 at 03:10:24PM +0200, Giorgos Keramidas wrote: > On 2005-11-21 19:23, Mikhail Teterin wrote: > > Hello! > > > > According the pointyhat's build logs, the port started to fail its self= -tests > > recently -- with a SIGBUS :-( > > > > Could someone running 7-current on amd64, please, investigate? I don't = have > > such a system. Thanks! >=20 > Hmm, I just built tcltls here on amd64: Make sure your system is completely up-to-date; this problem is very recent. Kris --3V7upXqbjpZ4EhLz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDg5JpWry0BWjoQKURArdfAJ9oiBBT3qHRB7rUMzXOcJwHoRV8vgCg3ZcN ItJUsxXx5Xou4hOTSlTGzbo= =igy/ -----END PGP SIGNATURE----- --3V7upXqbjpZ4EhLz-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 22 22:11:25 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD49416A423 for ; Tue, 22 Nov 2005 22:11:25 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6A9043D49 for ; Tue, 22 Nov 2005 22:11:23 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 9F2AA72DD4; Tue, 22 Nov 2005 14:11:23 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 9702D72DCB; Tue, 22 Nov 2005 14:11:23 -0800 (PST) Date: Tue, 22 Nov 2005 14:11:23 -0800 (PST) From: Doug White To: Christian Brueffer In-Reply-To: <20051120011438.GA4194@unixpages.org> Message-ID: <20051122141101.G24336@carver.gumbysoft.com> References: <200511150403.jAF43B6f001417@jerry.xoo.net> <20051119162011.I88861@carver.gumbysoft.com> <20051120011438.GA4194@unixpages.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Ulf Kieber , freebsd-current@freebsd.org Subject: Re: GEOM error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Nov 2005 22:11:25 -0000 On Sun, 20 Nov 2005, Christian Brueffer wrote: > On Sat, Nov 19, 2005 at 04:22:11PM -0800, Doug White wrote: > > On Tue, 15 Nov 2005, Ulf Kieber wrote: > > > > > Re, > > > > > > on a 6.0-RELEASE I receive the following error since I tried restoring > > > a large dump > > > > > > Nov 14 12:30:11 nexus kernel: g_vfs_done():da1s1d.bde[WRITE(offset=72350695424, length=131072)]error = 1 > > > > > > Besides that, no other errors are logged, especially no SCSI errors. > > > The problem persists even after the restore has completed. > > > > errno 1 is EPERM ("Operation not permitted") and is generally returned if > > you attempt to write somewhere you're not allowed to. Considering the > > offset is near the end of the disk, GBDE may be trying to prevent you from > > overwriting metadata blocks at the end of the partition. How or why > > restore(8) would be writing there I'm not sure. > > > > A SCSI error would return as errno 5 (EIO, "Input/output error"). > > > > I get the same messages with my external USB drive from time to time > (interestingly also GBDE encrypted). > > Nov 20 02:03:30 haakonia kernel: g_vfs_done():da3s2c.bde[WRITE(offset=383341297664, length=65536)]error = 1 > > The message repeats every 30 seconds and trying to unmount the file > system fails. When I try to shut the system down, the message appears > n > 50 times followed by a panic. > > Is it possible that the system tries to write on a bad sector and > consequently fails (provided that the on-disk sector remapping also > fails)? You would get a SCSI error in that case since usb storage is attached through CAM. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 22 22:13:03 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 230B216A423; Tue, 22 Nov 2005 22:13:03 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD92E43D5C; Tue, 22 Nov 2005 22:13:02 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 82E8835DF; Tue, 22 Nov 2005 16:13:02 -0600 (CST) Date: Tue, 22 Nov 2005 16:13:02 -0600 To: Max Laier Message-ID: <20051122221302.GB6266@soaustin.net> References: <200511181336.59361.max@love2party.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200511181336.59361.max@love2party.net> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) X-Mailman-Approved-At: Tue, 22 Nov 2005 22:50:21 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: FreeBSD Status Report Third Quarter 2005 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 22 Nov 2005 22:13:03 -0000 When I initially wrote the Ports Status report I included information about a project that Edwin Groothuis created. At that time I neglected to get his approval for that text, and that was an oversight and a mistake on my part and I apologize. I did not intend for anyone to get the impression that anyone other than himself should get the credit for this project. mcl From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 01:06:25 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 470E916A41F; Wed, 23 Nov 2005 01:06:25 +0000 (GMT) (envelope-from nate@root.org) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1541A43D53; Wed, 23 Nov 2005 01:06:24 +0000 (GMT) (envelope-from nate@root.org) Received: from pimout7-ext.prodigy.net (pimout7-int.prodigy.net [207.115.4.147]) by ylpvm15.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id jAN16Lug031527; Tue, 22 Nov 2005 20:06:21 -0500 X-ORBL: [71.139.30.140] Received: from [10.0.5.50] (ppp-71-139-30-140.dsl.snfc21.pacbell.net [71.139.30.140]) by pimout7-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id jAN16H0K098214; Tue, 22 Nov 2005 20:06:18 -0500 Message-ID: <4383C083.6010300@root.org> Date: Tue, 22 Nov 2005 17:06:11 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050723) X-Accept-Language: en-us, en MIME-Version: 1.0 To: acpi@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@FreeBSD.org, FreeBSD Current Subject: [Fwd: cvs commit: src/sys/dev/acpica acpi_cmbat.c] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2005 01:06:25 -0000 Here is a patch that should fix the battery hangs on RELENG_6. It was tested to work fine, although I need testing from an affected user to verify it fixes the problem. It was committed to HEAD and will be MFCed if it fixes the problem. I'm a bit disappointed that no one reported this problem in the 2 weeks it was present in 7-current. If you have the time to run -current on at least one partition of your laptop, that would assist me greatly. Thanks, -Nate -------- Original Message -------- Subject: cvs commit: src/sys/dev/acpica acpi_cmbat.c Date: Wed, 23 Nov 2005 00:58:05 +0000 (GMT) From: Nate Lawson To: njl@FreeBSD.ORG njl 2005-11-23 00:57:51 UTC FreeBSD src repository Modified files: sys/dev/acpica acpi_cmbat.c Log: Try to fix problems with periodic hangs by never directly calling _BIF. Instead, re-evaluate _BIF only when we get a notify and use the cached results. We also still evaluate _BIF once on boot. Also, optimize the init loop a little by only querying for a particular info if it's not valid. MFC after: 2 days Revision Changes Path 1.42 +34 -22 src/sys/dev/acpica/acpi_cmbat.c Index: src/sys/dev/acpica/acpi_cmbat.c diff -u src/sys/dev/acpica/acpi_cmbat.c:1.41 src/sys/dev/acpica/acpi_cmbat.c:1.42 --- src/sys/dev/acpica/acpi_cmbat.c:1.41 Sun Sep 11 18:39:01 2005 +++ src/sys/dev/acpica/acpi_cmbat.c Wed Nov 23 00:57:51 2005 @@ -66,7 +66,6 @@ struct acpi_bif bif; struct acpi_bst bst; - struct timespec bif_lastupdated; struct timespec bst_lastupdated; }; @@ -80,8 +79,8 @@ void *context); static int acpi_cmbat_info_expired(struct timespec *lastupdated); static void acpi_cmbat_info_updated(struct timespec *lastupdated); -static void acpi_cmbat_get_bst(device_t dev); -static void acpi_cmbat_get_bif(device_t dev); +static void acpi_cmbat_get_bst(void *arg); +static void acpi_cmbat_get_bif(void *arg); static int acpi_cmbat_bst(device_t dev, struct acpi_bst *bstp); static int acpi_cmbat_bif(device_t dev, struct acpi_bif *bifp); static void acpi_cmbat_init_battery(void *arg); @@ -134,7 +133,6 @@ handle = acpi_get_handle(dev); sc->dev = dev; - timespecclear(&sc->bif_lastupdated); timespecclear(&sc->bst_lastupdated); error = acpi_battery_register(dev); @@ -180,20 +178,22 @@ dev = (device_t)context; sc = device_get_softc(dev); - /* - * Clear the appropriate last updated time. The next call to retrieve - * the battery status will get the new value for us. We don't need to - * acquire a lock since we are only clearing the time stamp and since - * calling _BST/_BIF can trigger a notify, we could deadlock also. - */ switch (notify) { case ACPI_NOTIFY_DEVICE_CHECK: case ACPI_BATTERY_BST_CHANGE: + /* + * Clear the last updated time. The next call to retrieve the + * battery status will get the new value for us. + */ timespecclear(&sc->bst_lastupdated); break; case ACPI_NOTIFY_BUS_CHECK: case ACPI_BATTERY_BIF_CHANGE: - timespecclear(&sc->bif_lastupdated); + /* + * Queue a callback to get the current battery info from thread + * context. It's not safe to block in a notify handler. + */ + AcpiOsQueueForExecution(OSD_PRIORITY_LO, acpi_cmbat_get_bif, dev); break; } @@ -229,16 +229,18 @@ } static void -acpi_cmbat_get_bst(device_t dev) +acpi_cmbat_get_bst(void *arg) { struct acpi_cmbat_softc *sc; ACPI_STATUS as; ACPI_OBJECT *res; ACPI_HANDLE h; ACPI_BUFFER bst_buffer; + device_t dev; ACPI_SERIAL_ASSERT(cmbat); + dev = arg; sc = device_get_softc(dev); h = acpi_get_handle(dev); bst_buffer.Pointer = NULL; @@ -287,24 +289,23 @@ } static void -acpi_cmbat_get_bif(device_t dev) +acpi_cmbat_get_bif(void *arg) { struct acpi_cmbat_softc *sc; ACPI_STATUS as; ACPI_OBJECT *res; ACPI_HANDLE h; ACPI_BUFFER bif_buffer; + device_t dev; ACPI_SERIAL_ASSERT(cmbat); + dev = arg; sc = device_get_softc(dev); h = acpi_get_handle(dev); bif_buffer.Pointer = NULL; bif_buffer.Length = ACPI_ALLOCATE_BUFFER; - if (!acpi_cmbat_info_expired(&sc->bif_lastupdated)) - goto end; - as = AcpiEvaluateObject(h, "_BIF", NULL, &bif_buffer); if (ACPI_FAILURE(as)) { ACPI_VPRINT(dev, acpi_device_get_parent_softc(dev), @@ -346,7 +347,6 @@ goto end; if (acpi_PkgStr(res, 12, sc->bif.oeminfo, ACPI_CMBAT_MAXSTRLEN) != 0) goto end; - acpi_cmbat_info_updated(&sc->bif_lastupdated); end: if (bif_buffer.Pointer != NULL) @@ -360,8 +360,13 @@ sc = device_get_softc(dev); + /* + * Just copy the data. The only value that should change is the + * last-full capacity, so we only update when we get a notify that says + * the info has changed. Many systems apparently take a long time to + * process a _BIF call so we avoid it if possible. + */ ACPI_SERIAL_BEGIN(cmbat); - acpi_cmbat_get_bif(dev); bifp->units = sc->bif.units; bifp->dcap = sc->bif.dcap; bifp->lfcap = sc->bif.lfcap; @@ -422,11 +427,18 @@ if (!acpi_BatteryIsPresent(dev)) continue; + /* + * Only query the battery if this is the first try or the specific + * type of info is still invalid. + */ ACPI_SERIAL_BEGIN(cmbat); - timespecclear(&sc->bst_lastupdated); - timespecclear(&sc->bif_lastupdated); - acpi_cmbat_get_bst(dev); - acpi_cmbat_get_bif(dev); + if (retry == 0 || !acpi_battery_bst_valid(&sc->bst)) { + timespecclear(&sc->bst_lastupdated); + acpi_cmbat_get_bst(dev); + } + if (retry == 0 || !acpi_battery_bif_valid(&sc->bif)) + acpi_cmbat_get_bif(dev); + valid = acpi_battery_bst_valid(&sc->bst) && acpi_battery_bif_valid(&sc->bif); ACPI_SERIAL_END(cmbat); -- Nate From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 02:36:01 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3B6A16A41F; Wed, 23 Nov 2005 02:36:01 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 590B243D62; Wed, 23 Nov 2005 02:35:58 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jAN2ZuQL032449; Tue, 22 Nov 2005 19:35:57 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4383D58C.5040004@samsco.org> Date: Tue, 22 Nov 2005 19:35:56 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nate Lawson References: <4383C083.6010300@root.org> In-Reply-To: <4383C083.6010300@root.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: acpi@freebsd.org, stable@freebsd.org, FreeBSD Current Subject: Re: [Fwd: cvs commit: src/sys/dev/acpica acpi_cmbat.c] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2005 02:36:01 -0000 Nate Lawson wrote: > Here is a patch that should fix the battery hangs on RELENG_6. It was > tested to work fine, although I need testing from an affected user to > verify it fixes the problem. It was committed to HEAD and will be MFCed > if it fixes the problem. Thanks a lot! > > I'm a bit disappointed that no one reported this problem in the 2 weeks > it was present in 7-current. If you have the time to run -current on at > least one partition of your laptop, that would assist me greatly. Don't feel too bad. You committed it right after 6.0 was released, so people were either looking at 6.0 or taking a breather from the release work. Scott From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 02:58:48 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 26EB316A41F; Wed, 23 Nov 2005 02:58:48 +0000 (GMT) (envelope-from djp@polands.org) Received: from corinth.polands.org (CPE-72-129-222-120.new.res.rr.com [72.129.222.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC8BE43DA5; Wed, 23 Nov 2005 02:58:36 +0000 (GMT) (envelope-from djp@polands.org) Received: from jericho.polands.org (jericho.polands.org [172.16.1.35]) by corinth.polands.org (8.13.4/8.13.4) with ESMTP id jAN2wTEM056134; Tue, 22 Nov 2005 20:58:29 -0600 (CST) (envelope-from djp@polands.org) Received: from jericho.polands.org (localhost [127.0.0.1]) by jericho.polands.org (8.13.4/8.13.1) with ESMTP id jAN2wUB0099639; Tue, 22 Nov 2005 20:58:30 -0600 (CST) (envelope-from djp@jericho.polands.org) Received: (from djp@localhost) by jericho.polands.org (8.13.4/8.13.1/Submit) id jAN2nCt4099559; Tue, 22 Nov 2005 20:49:12 -0600 (CST) (envelope-from djp) Date: Tue, 22 Nov 2005 20:49:12 -0600 From: Doug Poland To: Nate Lawson Message-ID: <20051123024911.GA99513@polands.org> References: <4383C083.6010300@root.org> <4383D58C.5040004@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4383D58C.5040004@samsco.org> User-Agent: Mutt/1.5.11 X-Virus-Scanned: ClamAV 0.87/1184/Tue Nov 22 17:10:14 2005 on corinth.polands.org X-Virus-Status: Clean Cc: acpi@freebsd.org, stable@freebsd.org, FreeBSD Current Subject: Re: [Fwd: cvs commit: src/sys/dev/acpica acpi_cmbat.c] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2005 02:58:48 -0000 > Nate Lawson wrote: > >Here is a patch that should fix the battery hangs on RELENG_6. It > >was tested to work fine, although I need testing from an affected > >user to verify it fixes the problem. It was committed to HEAD and > >will be MFCed if it fixes the problem. > > My Dell C600 is affected by this problem. I'm running 6.0-STABLE and would be glad to test the patch. Since I don't run patches often, if someone could point me to a doc on how to apply the patch, I'd appreciate it. > >I'm a bit disappointed that no one reported this problem in the 2 > >weeks it was present in 7-current. If you have the time to run > >-current on at least one partition of your laptop, that would assist > >me greatly. > > My laptop was dedicated to other uses between RC1 and early last week. Too bad I missed it. -- Regards, Doug From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 03:05:46 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56B9616A422; Wed, 23 Nov 2005 03:05:46 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E4CF43DC5; Wed, 23 Nov 2005 03:03:14 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 1D3781A3C1C; Tue, 22 Nov 2005 19:03:06 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6FD505130F; Tue, 22 Nov 2005 22:03:05 -0500 (EST) Date: Tue, 22 Nov 2005 22:03:04 -0500 From: Kris Kennaway To: net@FreeBSD.org Message-ID: <20051123030304.GA84202@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: current@FreeBSD.org Subject: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 03:05:47 -0000 --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I am seeing the em driver undergoing an interrupt storm whenever the amr driver receives interrupts. In this case I was running newfs on the amr array and em0 was not in use: 28 root 1 -68 -187 0K 8K CPU1 1 0:32 53.98% irq16: em0 36 root 1 -64 -183 0K 8K RUN 1 0:37 27.75% irq24: amr0 # vmstat -i interrupt total rate irq1: atkbd0 2 0 irq4: sio0 199 1 irq6: fdc0 32 0 irq13: npx0 1 0 irq14: ata0 47 0 irq15: ata1 931 5 irq16: em0 6321801 37187 irq24: amr0 28023 164 cpu0: timer 337533 1985 cpu1: timer 337285 1984 Total 7025854 41328 When newfs finished (i.e. amr was idle), em0 stopped storming. MPTable: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf34 Stepping = 4 Features=0xbfebfbff Features2=0x441d> AMD Features=0x20000000 Hyperthreading: 2 logical CPUs real memory = 3757965312 (3583 MB) avail memory = 3682967552 (3512 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 ioapic0: Assuming intbase of 0 ioapic1: Assuming intbase of 24 ioapic2: Assuming intbase of 48 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard [...] pcib0: pcibus 0 on motherboard pci0: on pcib0 pci0: at device 0.1 (no driver attached) pci0: at device 1.0 (no driver attached) pcib1: irq 16 at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 0.0 on pci1 pci2: on pcib2 pcib3: at device 3.0 on pci2 pci3: on pcib3 amr0: mem 0xfc3f0000-0xfc3fffff,0xfc780000-0xfc7fffff irq 24 at device 0.0 on pci3 amr0: delete logical drives supported by controller amr0: Firmware 413G, BIOS H414, 128MB RAM pci1: at device 0.1 (no driver attached) pcib4: at device 0.2 on pci1 pci4: on pcib4 pci1: at device 0.3 (no driver attached) pcib5: irq 16 at device 4.0 on pci0 pci5: on pcib5 pcib6: irq 16 at device 5.0 on pci0 pci6: on pcib6 pci6: at device 0.0 (no driver attached) pcib7: irq 16 at device 6.0 on pci0 pci7: on pcib7 pcib8: at device 30.0 on pci0 pci8: on pcib8 em0: port 0xec00-0xec3f mem 0xfeaa0000-0xfeabffff irq 16 at device 4.0 on pci8 em0: Ethernet address: 00:02:b3:e8:fc:8a This is on both 6.0-RELEASE and 6.0-STABLE. Kris --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDg9voWry0BWjoQKURAvVBAKDLYAilotS9+cKdj8u+mfiXT1XErQCg/apy /14slbiEMeGHl8l+gciqxzI= =PZ9L -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 03:38:41 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9626B16A41F for ; Wed, 23 Nov 2005 03:38:41 +0000 (GMT) (envelope-from nils.berzins@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8B3643D45 for ; Wed, 23 Nov 2005 03:38:40 +0000 (GMT) (envelope-from nils.berzins@gmail.com) Received: by wproxy.gmail.com with SMTP id i31so759741wra for ; Tue, 22 Nov 2005 19:38:40 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=B2uAlrit6aJ75MgWhinaPSyot1GDFyO3n2o0x4dHdyEIUnVIapjBPn8aNBGb/6HtJ/xhu+mlsbixxDybOTWqkAk67PNtPOQezmAYxTI7wIruzd8llLvz3cBofhW0xJBfbomEOsS3aVnmK/0IJ3cZJGz7MruLCxDX1oN8rM0mR3Y= Received: by 10.54.86.11 with SMTP id j11mr3254478wrb; Tue, 22 Nov 2005 19:38:40 -0800 (PST) Received: by 10.54.142.12 with HTTP; Tue, 22 Nov 2005 19:38:40 -0800 (PST) Message-ID: Date: Wed, 23 Nov 2005 05:38:40 +0200 From: Nils Berzins To: current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Trouble with amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2005 03:38:41 -0000 Hi ! Few days ago I downloaded release 6.0 ISOs, in hope that I will finally be able to run FreeBSD on my home computer. Unfortunately, booting from CD die= s with: > panic: sym: VTOBUS FAILED ! Is there something I can do to get around this error, or do I just wait for more less stable 7.0 :-( Best Regards Nils Berzins P.S. I have ASUS A8V-E Deluxe with Athlon 64D. From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 04:54:53 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C63C16A41F; Wed, 23 Nov 2005 04:54:53 +0000 (GMT) (envelope-from jdp@polstra.com) Received: from blake.polstra.com (blake.polstra.com [64.81.189.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93B9843D5C; Wed, 23 Nov 2005 04:54:52 +0000 (GMT) (envelope-from jdp@polstra.com) Received: from t30.polstra.com (t30.polstra.com [64.81.189.72]) by blake.polstra.com (8.13.1/8.13.1) with ESMTP id jAN4so4s083855 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 22 Nov 2005 20:54:51 -0800 (PST) (envelope-from jdp@mail.polstra.com) Received: from t30.polstra.com (localhost [127.0.0.1]) by t30.polstra.com (8.12.11/8.12.11) with ESMTP id jAN4soYf000536; Tue, 22 Nov 2005 20:54:50 -0800 (PST) (envelope-from jdp@t30.polstra.com) Received: (from jdp@localhost) by t30.polstra.com (8.12.11/8.12.11/Submit) id jAN4sn8B000535; Tue, 22 Nov 2005 20:54:49 -0800 (PST) (envelope-from jdp) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20051123030304.GA84202@xor.obsecurity.org> Date: Tue, 22 Nov 2005 20:54:49 -0800 (PST) From: John Polstra To: Kris Kennaway Cc: current@freebsd.org, net@freebsd.org Subject: RE: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 04:54:53 -0000 On 23-Nov-2005 Kris Kennaway wrote: > I am seeing the em driver undergoing an interrupt storm whenever the > amr driver receives interrupts. In this case I was running newfs on > the amr array and em0 was not in use: > > 28 root 1 -68 -187 0K 8K CPU1 1 0:32 53.98% irq16: em0 > 36 root 1 -64 -183 0K 8K RUN 1 0:37 27.75% irq24: amr0 > ># vmstat -i > interrupt total rate > irq1: atkbd0 2 0 > irq4: sio0 199 1 > irq6: fdc0 32 0 > irq13: npx0 1 0 > irq14: ata0 47 0 > irq15: ata1 931 5 > irq16: em0 6321801 37187 > irq24: amr0 28023 164 > cpu0: timer 337533 1985 > cpu1: timer 337285 1984 > Total 7025854 41328 > > When newfs finished (i.e. amr was idle), em0 stopped storming. > > MPTable: This is the dreaded interrupt aliasing problem that several of us have experienced with this chipset. High-numbered interrupts alias down to interrupts in the range 16..19 (or maybe 16..23), a multiple of 8 less than the original interupt. Nobody knows what causes it, and nobody knows how to fix it. John From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 08:22:50 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7504416A41F for ; Wed, 23 Nov 2005 08:22:50 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from insomma.datacode.it (ip-152-166.sn2.eutelia.it [83.211.152.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id D304343D45 for ; Wed, 23 Nov 2005 08:22:49 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from localhost (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with SMTP id 6406D2C90B for ; Wed, 23 Nov 2005 09:22:47 +0100 (CET) Received: from insomma.datacode.it (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with ESMTP id 9ADF02C90A for ; Wed, 23 Nov 2005 09:22:46 +0100 (CET) Received: from massimo.datacode.it (massimo.datacode.it [192.168.1.13]) by insomma.datacode.it (Postfix) with ESMTP id 5A6872C906 for ; Wed, 23 Nov 2005 09:22:46 +0100 (CET) From: Massimo Lusetti To: freebsd-current@freebsd.org In-Reply-To: <20051123030304.GA84202@xor.obsecurity.org> References: <20051123030304.GA84202@xor.obsecurity.org> Content-Type: text/plain Organization: CEDOC - Modena Date: Wed, 23 Nov 2005 09:22:45 +0100 Message-Id: <1132734165.4305.3.camel@massimo.datacode.it> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 08:22:50 -0000 On Tue, 2005-11-22 at 22:03 -0500, Kris Kennaway wrote: > I am seeing the em driver undergoing an interrupt storm whenever the > amr driver receives interrupts. In this case I was running newfs on > the amr array and em0 was not in use: [..] > This is on both 6.0-RELEASE and 6.0-STABLE. Wow, I've just ordered a machine with that same hardware to replace a mailserver. -- Massimo.run(); From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 08:31:19 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7EC6716A41F for ; Wed, 23 Nov 2005 08:31:19 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38ACB43D5C for ; Wed, 23 Nov 2005 08:31:19 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 15AC61A3C2D; Wed, 23 Nov 2005 00:31:19 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5851D515B2; Wed, 23 Nov 2005 03:31:18 -0500 (EST) Date: Wed, 23 Nov 2005 03:31:18 -0500 From: Kris Kennaway To: Massimo Lusetti Message-ID: <20051123083118.GA90686@xor.obsecurity.org> References: <20051123030304.GA84202@xor.obsecurity.org> <1132734165.4305.3.camel@massimo.datacode.it> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline In-Reply-To: <1132734165.4305.3.camel@massimo.datacode.it> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 08:31:19 -0000 --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 23, 2005 at 09:22:45AM +0100, Massimo Lusetti wrote: > On Tue, 2005-11-22 at 22:03 -0500, Kris Kennaway wrote: > > I am seeing the em driver undergoing an interrupt storm whenever the > > amr driver receives interrupts. In this case I was running newfs on > > the amr array and em0 was not in use: > [..] > > This is on both 6.0-RELEASE and 6.0-STABLE. >=20 > Wow, I've just ordered a machine with that same hardware to replace a > mailserver. Maybe it'll be OK if you disable the onboard NIC and use a different one. Kris --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhCjVWry0BWjoQKURAhagAJ0UcUjoQFoasdEumoA3DC01wXdReQCcDhUo Rw83DEZTd/2a+bdqUQwEel0= =UxBC -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 08:47:03 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA60E16A41F; Wed, 23 Nov 2005 08:47:03 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FB7A43D6B; Wed, 23 Nov 2005 08:46:58 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 12E651A3C1C; Wed, 23 Nov 2005 00:46:54 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6DE1751593; Wed, 23 Nov 2005 03:46:53 -0500 (EST) Date: Wed, 23 Nov 2005 03:46:53 -0500 From: Kris Kennaway To: John Polstra Message-ID: <20051123084653.GA90927@xor.obsecurity.org> References: <20051123030304.GA84202@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jRHKVT23PllUwdXP" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: net@freebsd.org, current@freebsd.org, Kris Kennaway Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 08:47:04 -0000 --jRHKVT23PllUwdXP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 22, 2005 at 08:54:49PM -0800, John Polstra wrote: >=20 > On 23-Nov-2005 Kris Kennaway wrote: > > I am seeing the em driver undergoing an interrupt storm whenever the > > amr driver receives interrupts. In this case I was running newfs on > > the amr array and em0 was not in use: > >=20 > > 28 root 1 -68 -187 0K 8K CPU1 1 0:32 53.98% irq16= : em0 > > 36 root 1 -64 -183 0K 8K RUN 1 0:37 27.75% irq24= : amr0 > >=20 > ># vmstat -i > > interrupt total rate > > irq1: atkbd0 2 0 > > irq4: sio0 199 1 > > irq6: fdc0 32 0 > > irq13: npx0 1 0 > > irq14: ata0 47 0 > > irq15: ata1 931 5 > > irq16: em0 6321801 37187 > > irq24: amr0 28023 164 > > cpu0: timer 337533 1985 > > cpu1: timer 337285 1984 > > Total 7025854 41328 > >=20 > > When newfs finished (i.e. amr was idle), em0 stopped storming. > >=20 > > MPTable: >=20 > This is the dreaded interrupt aliasing problem that several of us have > experienced with this chipset. High-numbered interrupts alias down to > interrupts in the range 16..19 (or maybe 16..23), a multiple of 8 less > than the original interupt. >=20 > Nobody knows what causes it, and nobody knows how to fix it. This would be good to document somewhere so that people don't either accidentally buy this hardware, or know what to expect when they run it. Kris --jRHKVT23PllUwdXP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhCx8Wry0BWjoQKURAoSZAJ45iXxWGfFc7G8++HwAmr9wAD0OpgCfQp4t pDBtasCrA64KmsHmt8UqJ3M= =2hmE -----END PGP SIGNATURE----- --jRHKVT23PllUwdXP-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 08:50:53 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7956216A41F for ; Wed, 23 Nov 2005 08:50:53 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C596543D62 for ; Wed, 23 Nov 2005 08:50:26 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jAN8o9xC034352; Wed, 23 Nov 2005 01:50:09 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43842D41.1050401@samsco.org> Date: Wed, 23 Nov 2005 01:50:09 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <20051123030304.GA84202@xor.obsecurity.org> <1132734165.4305.3.camel@massimo.datacode.it> <20051123083118.GA90686@xor.obsecurity.org> In-Reply-To: <20051123083118.GA90686@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: Massimo Lusetti , freebsd-current@freebsd.org Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 08:50:53 -0000 Kris Kennaway wrote: > On Wed, Nov 23, 2005 at 09:22:45AM +0100, Massimo Lusetti wrote: > >>On Tue, 2005-11-22 at 22:03 -0500, Kris Kennaway wrote: >> >>>I am seeing the em driver undergoing an interrupt storm whenever the >>>amr driver receives interrupts. In this case I was running newfs on >>>the amr array and em0 was not in use: >> >>[..] >> >>>This is on both 6.0-RELEASE and 6.0-STABLE. >> >>Wow, I've just ordered a machine with that same hardware to replace a >>mailserver. > > > Maybe it'll be OK if you disable the onboard NIC and use a different > one. > > Kris This is apparently a side effect of how we process interupts, which is different from Windows and Linux. Since we mask the interrupt in the APIC while the ithread runs, the Intel hardware tries to outsmart us and continue delivering the interrupt via irq16. There are been rumors on ways to turn off this 'feature', but none of them seem to work. Since ithreads are integral to SMPng, and masking the APIC pins in integral to making ithreads work, the solution will probably be to be more aggressive in adopting MSI, and in doing filtered interrupt handlers that don't require the APIC to be masked. Note that Solaris and Darwin would likely exhibit the same problem since they handle interrupts similar to us. Scott From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 08:55:24 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 802F216A41F for ; Wed, 23 Nov 2005 08:55:24 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from insomma.datacode.it (ip-152-166.sn2.eutelia.it [83.211.152.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id EADD043D45 for ; Wed, 23 Nov 2005 08:55:19 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from localhost (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with SMTP id 48AB42C90B for ; Wed, 23 Nov 2005 09:55:17 +0100 (CET) Received: from insomma.datacode.it (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with ESMTP id 81F682C90A; Wed, 23 Nov 2005 09:55:16 +0100 (CET) Received: from massimo.datacode.it (massimo.datacode.it [192.168.1.13]) by insomma.datacode.it (Postfix) with ESMTP id 41A812C906; Wed, 23 Nov 2005 09:55:16 +0100 (CET) From: Massimo Lusetti To: Kris Kennaway In-Reply-To: <20051123083118.GA90686@xor.obsecurity.org> References: <20051123030304.GA84202@xor.obsecurity.org> <1132734165.4305.3.camel@massimo.datacode.it> <20051123083118.GA90686@xor.obsecurity.org> Content-Type: text/plain Organization: CEDOC - Modena Date: Wed, 23 Nov 2005 09:55:16 +0100 Message-Id: <1132736116.4305.8.camel@massimo.datacode.it> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: freebsd-current@freebsd.org Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 08:55:24 -0000 On Wed, 2005-11-23 at 03:31 -0500, Kris Kennaway wrote: > Maybe it'll be OK if you disable the onboard NIC and use a different > one. Sure, I'll try that, did you have any suggestion for the replacement nic? And do you think something could change if the arch is 64bit? http://www.supermicro.com/products/system/2U/6024/SYS-6024H-82R.cfm -- Massimo.run(); From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 09:03:36 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DCE916A422; Wed, 23 Nov 2005 09:03:36 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18A6543D5A; Wed, 23 Nov 2005 09:03:36 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 4DC201A3C1C; Wed, 23 Nov 2005 01:03:35 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5F1D651593; Wed, 23 Nov 2005 04:03:34 -0500 (EST) Date: Wed, 23 Nov 2005 04:03:34 -0500 From: Kris Kennaway To: current@FreeBSD.org Message-ID: <20051123090334.GA90972@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lrZ03NoBR/3+SXJZ" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: jhb@FreeBSD.org Subject: idle task running on the wrong CPU X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 09:03:36 -0000 --lrZ03NoBR/3+SXJZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 6.0-STABLE: PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 13 root 1 171 52 0K 8K CPU1 0 0:00 100.00% idle: cp= u1 =20 Note: the cpu1 idle task is running on CPU 0. Actually it is not running, since it's not accumulating any CPU time, and in fact nothing at all is being scheduled on CPU 1. Kris --lrZ03NoBR/3+SXJZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhDBlWry0BWjoQKURAgBAAJ9DIHYJ3tyzTQe6AXMwQ3F2ptvOGwCg3WOC cGFmhGufK/2OYLgO2szvYh0= =mJxE -----END PGP SIGNATURE----- --lrZ03NoBR/3+SXJZ-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 09:07:10 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1547316A41F; Wed, 23 Nov 2005 09:07:10 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4FD043D5C; Wed, 23 Nov 2005 09:07:09 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id A24871A3C2A; Wed, 23 Nov 2005 01:07:09 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 89981528C8; Wed, 23 Nov 2005 04:07:07 -0500 (EST) Date: Wed, 23 Nov 2005 04:07:07 -0500 From: Kris Kennaway To: Kris Kennaway Message-ID: <20051123090706.GA91223@xor.obsecurity.org> References: <20051123090334.GA90972@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline In-Reply-To: <20051123090334.GA90972@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i Cc: cperciva@FreeBSD.org, current@FreeBSD.org, jhb@FreeBSD.org Subject: Re: idle task running on the wrong CPU X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 09:07:10 -0000 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 23, 2005 at 04:03:34AM -0500, Kris Kennaway wrote: > On 6.0-STABLE: >=20 > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 13 root 1 171 52 0K 8K CPU1 0 0:00 100.00% idle: = cpu1 > =20 > Note: the cpu1 idle task is running on CPU 0. Actually it is not > running, since it's not accumulating any CPU time, and in fact nothing > at all is being scheduled on CPU 1. >=20 > Kris It was pointed out that machdep.hyperthreading_allowed=3D1 fixes this bug (it was set to 0). However, hyperthreading was already in use (partly), because this machine has 2 physical CPUs with HTT, and CPUs 0, 2 and 3 were running jobs. Looks like machdep.hyperthreading_allowed=3D0 does not work as intended. Kris --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhDE6Wry0BWjoQKURAonNAJ9QsfYWiBrZlX0TPcvKV1bujvQDpwCeNJOJ 50ujf6MlrbgBncmN5CBcm08= =//dH -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 10:01:52 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FF9B16A41F; Wed, 23 Nov 2005 10:01:52 +0000 (GMT) (envelope-from cperciva@freebsd.org) Received: from pd2mo3so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15C7443D4C; Wed, 23 Nov 2005 10:01:52 +0000 (GMT) (envelope-from cperciva@freebsd.org) Received: from pd5mr8so.prod.shaw.ca (pd5mr8so-qfe3.prod.shaw.ca [10.0.141.184]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IQE00788JV30K00@l-daemon>; Wed, 23 Nov 2005 03:01:51 -0700 (MST) Received: from pn2ml7so.prod.shaw.ca ([10.0.121.151]) by pd5mr8so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IQE006FFJV3KQ70@pd5mr8so.prod.shaw.ca>; Wed, 23 Nov 2005 03:01:51 -0700 (MST) Received: from [192.168.0.60] (S0106006067227a4a.vc.shawcable.net [24.87.209.6]) by l-daemon (iPlanet Messaging Server 5.2 HotFix 1.18 (built Jul 28 2003)) with ESMTP id <0IQE007IKJV2QJ@l-daemon>; Wed, 23 Nov 2005 03:01:51 -0700 (MST) Date: Wed, 23 Nov 2005 02:01:50 -0800 From: Colin Percival In-reply-to: <20051123090706.GA91223@xor.obsecurity.org> To: Kris Kennaway Message-id: <43843E0E.8040601@freebsd.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en X-Enigmail-Version: 0.93.0.0 References: <20051123090334.GA90972@xor.obsecurity.org> <20051123090706.GA91223@xor.obsecurity.org> User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051001) Cc: current@FreeBSD.org, jhb@FreeBSD.org Subject: Re: idle task running on the wrong CPU X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 10:01:52 -0000 Kris Kennaway wrote: > It was pointed out that machdep.hyperthreading_allowed=1 fixes this > bug (it was set to 0). However, hyperthreading was already in use > (partly), because this machine has 2 physical CPUs with HTT, and CPUs > 0, 2 and 3 were running jobs. > > Looks like machdep.hyperthreading_allowed=0 does not work as intended. That's odd. Can you tell me what values the hyperthreading_cpus_mask and hyperthreading_cpus variables in mp_machdep.c have, and what values PCPU_GET(cpumask) returns on the various (virtual) cpus? Colin Percival From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 10:54:59 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A678F16A41F for ; Wed, 23 Nov 2005 10:54:59 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from leguin.anholt.net (69-30-77-85.dq1sn.easystreet.com [69.30.77.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6C3243D8F for ; Wed, 23 Nov 2005 10:54:46 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from leguin.anholt.net (localhost [127.0.0.1]) by leguin.anholt.net (8.13.4/8.13.1) with ESMTP id jANAsiY0042087 for ; Wed, 23 Nov 2005 02:54:44 -0800 (PST) (envelope-from eta@lclark.edu) Received: (from anholt@localhost) by leguin.anholt.net (8.13.4/8.13.1/Submit) id jANAshqS042086 for current@FreeBSD.org; Wed, 23 Nov 2005 02:54:43 -0800 (PST) (envelope-from eta@lclark.edu) X-Authentication-Warning: leguin.anholt.net: anholt set sender to eta@lclark.edu using -f From: Eric Anholt To: current@FreeBSD.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-7Ulu3zG00ALWoXDZeHuY" Date: Wed, 23 Nov 2005 02:54:42 -0800 Message-Id: <1132743283.1197.55.camel@leguin> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Cc: Subject: DRM update for testing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 10:54:59 -0000 --=-7Ulu3zG00ALWoXDZeHuY Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I've got a patch at: http://people.freebsd.org/~anholt/dri/drm-sys-20051123.diff for testing, which merges DRM CVS into FreeBSD. I've done basic tests of a recent DRM CVS with WITNESS on AGP/PCI Matrox, AGP/PCI Rage 128, AGP Radeon r100/r200/r300, AGP Savage4 (new!), SiS, and 3dfx, and this version should be equivalent to what I tested. I'll do another pass of testing before I commit, but I'd also like to get some wider testing so more panics can show up if they exist. This particular diff has only been compile-tested with LINT on amd64 so far. Known issues: - Radeon PCIGART mode hung for me. I've heard this is caused by a change in X.Org upstream which itself worked around a different hang, so those of you not using xorg-server-snap wouldn't hit it hopefully. - Savage3d untested iirc - Savage4 PCI doesn't work (needs some love in the memory mapping department, I think). However, savage support has experimental and will only be on by default with the next release of X.Org, so I feel OK with integrating it into -current. So, for testing: If you get instant reboots while starting/using X, that almost always means a kernel panic. This is new behavior in the last year or so afaik (where a number of us have issues dumping while in X). However, I've hooked up serial consoles and got backtraces fine, which hopefully you can do if you hit issues, as well.=20 Also, note that this brings in a new enough r300 driver for running Mesa CVS's r300 driver, which hasn't been the case for a while. It doesn't bring in the via driver, which jakeb ported but which got overcome by new linux-specific code (volunteers to work on this in DRM CVS would be excellent!) in CVS. Also, the i915 (i830 through i915 integrated graphics) driver should be pretty quick for someone with a bit of newbus knowledge to finish off, or it could be a chance someone who cared to learn more about the FreeBSD kernel :) --=20 Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org --=-7Ulu3zG00ALWoXDZeHuY Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDhEpyHUdvYGzw6vcRAlgnAJwPDeUax2+FVGfZGDDnYjQLitGUSQCdGQWA SjjAbNTKdsWXseSRugeNnWc= =Zud7 -----END PGP SIGNATURE----- --=-7Ulu3zG00ALWoXDZeHuY-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 13:55:16 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C0BA16A41F for ; Wed, 23 Nov 2005 13:55:16 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0720B43D5C for ; Wed, 23 Nov 2005 13:55:14 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2475251 for multiple; Wed, 23 Nov 2005 08:55:15 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jANDtBV2090294; Wed, 23 Nov 2005 08:55:11 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 23 Nov 2005 08:48:15 -0500 User-Agent: KMail/1.8.3 References: <20051123030304.GA84202@xor.obsecurity.org> <20051123083118.GA90686@xor.obsecurity.org> <1132736116.4305.8.camel@massimo.datacode.it> In-Reply-To: <1132736116.4305.8.camel@massimo.datacode.it> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200511230848.16963.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Massimo Lusetti , Kris Kennaway Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 13:55:16 -0000 On Wednesday 23 November 2005 03:55 am, Massimo Lusetti wrote: > On Wed, 2005-11-23 at 03:31 -0500, Kris Kennaway wrote: > > Maybe it'll be OK if you disable the onboard NIC and use a different > > one. > > Sure, I'll try that, did you have any suggestion for the replacement > nic? > > And do you think something could change if the arch is 64bit? > http://www.supermicro.com/products/system/2U/6024/SYS-6024H-82R.cfm No, I've seen the same interrupt aliasing with a FreeBSD/amd64 kernel. Giv= en=20 that FreeBSD/i386 and FreeBSD/amd64 have nearly identical interrupt code th= is=20 is to be expected. =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 13:55:18 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1296916A41F for ; Wed, 23 Nov 2005 13:55:18 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id D87C343D66 for ; Wed, 23 Nov 2005 13:55:16 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2475254 for multiple; Wed, 23 Nov 2005 08:55:17 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jANDtBV3090294; Wed, 23 Nov 2005 08:55:13 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 23 Nov 2005 08:51:57 -0500 User-Agent: KMail/1.8.3 References: <20051123090334.GA90972@xor.obsecurity.org> In-Reply-To: <20051123090334.GA90972@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200511230851.58629.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Kris Kennaway Subject: Re: idle task running on the wrong CPU X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 13:55:18 -0000 On Wednesday 23 November 2005 04:03 am, Kris Kennaway wrote: > On 6.0-STABLE: > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND > 13 root 1 171 52 0K 8K CPU1 0 0:00 100.00% idle: > cpu1 > > Note: the cpu1 idle task is running on CPU 0. Actually it is not > running, since it's not accumulating any CPU time, and in fact nothing > at all is being scheduled on CPU 1. It is running, but is not accumulating time because it sits in a hlt loop. = =20 Also, the 'state =3D=3D CPU1' means it is running on CPU1. The 'C' column = is the=20 column for the CPU this process last ran on. If this is a HT CPU disabled = by=20 default during boot, then that thread has yet to perform a context switch,= =20 and all threads start off when they are created with the lastcpu being CPU = 0,=20 so it won't update the 'C' column until it actually does a context switch. = =20 I'm not sure why it is not accumulating time, however. =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 16:16:15 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C055616A41F for ; Wed, 23 Nov 2005 16:16:15 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from smtp1-g19.free.fr (smtp1-g19.free.fr [212.27.42.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07C3F43D69 for ; Wed, 23 Nov 2005 16:16:14 +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 smtp1-g19.free.fr (Postfix) with ESMTP id 37C6B5E2BB for ; Wed, 23 Nov 2005 17:16:06 +0100 (CET) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id B672E4085; Wed, 23 Nov 2005 17:15:50 +0100 (CET) Date: Wed, 23 Nov 2005 17:15:50 +0100 From: Jeremie Le Hen To: freebsd-current@FreeBSD.org Message-ID: <20051123161550.GE1010@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 Cc: Subject: Lasted NDIS wrapper for D-Link DWL-520+ on RELENG_6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2005 16:16:15 -0000 Hi, I'm trying to use my PCI Wireless card with NDISulator from Bill Paul. I have tried to gather as much details as possible browsing through recent wpaul's posts, I hope this will be enough. If misfortune made me forget some details, I apologize for it and please, be indulgent and ask them. I'm running RELENG_6 from the beginning of november 7th, but I checked out src/sys/compat/ndis/ and src/sys/dev/if_ndis/ from HEAD. The system is a generic single Pentium IV (therefore, no SMP in kernel). The full non-verbose dmesg is available here : http://jeremie.le-hen.org/~tataz/dmesg.OBIWAN The card I bought is a D-Link DWL-520+, based on the T.I. chipset. Here is the output of pciconf(8) : % none0@pci0:8:0: class=0x028000 card=0x3b041186 chip=0x9066104c rev=0x00 hdr=0x00 % vendor = 'Texas Instruments (TI)' % device = 'TNETW1130(ACX111) 802.11b/g Wireless Cardbus/PCI Adapter' % class = network I'm trying to use the lastest driver for this card provided by D-Link : ftp://ftp.dlink.com/Wireless/dwl520+/Driver/dwl520+_drivers_307.zip I have to say that I'm quite puzzled by the fact that there seem to be multiple versions of the DWL-520+ card (at least two, one with an Atheros chipset and one with a T.I. chipset) but strangely there is only one driver. Even stranger, the Drivers/WinXP/ directory contains only one .SYS file. I guess there must be some magic in it. I've generated the driver using ndisgen(8) : % cd drivers/dwl520+_drivers_307/Drivers/WinXP/ % ndisgen AIRPLUS.INF AIRPLUS.SYS At this stage, I gave all .BIN files in turn as firmware files as I don't know which one are useful. % cp AIRPLUS_SYS.ko WLANGEN.bin.ko RADIO0d.BIN.ko RADIO11.BIN.ko RADIO15.BIN.ko /boot/kernel/ % cd /sys/modules/ndis/ % make && make install Then, I tried to load AIRPLUS_SYS.ko in conjunction with WLANGEN.bin.ko alone first, and then I loaded RADIO*.bin.ko, but the dmesg didn't showed any additional device probe but : % warning: KLD '/boot/kernel/AIRPLUS_SYS.ko' is newer than the linker.hints file And ndis0 didn't appear obviously. Note that I didn't tried to load those modules from loader since I read it is generally a bad idea because NDIS drivers assume the OS is fully initialized, which is obviously not the case when loading modules from the loader. As a side note, the acx(4) driver from Darron Broad doesn't handle ACX111 chips, unfortunately, therefore this is not an option for me (anyway ISTR that it doesn't compile on RELENG_6 due to kernel internal networking interface change). Thank you. Best regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 16:19:50 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6111916A41F; Wed, 23 Nov 2005 16:19:50 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10B9B43D5F; Wed, 23 Nov 2005 16:19:47 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.4/8.13.4) with ESMTP id jANGJknq022680; Wed, 23 Nov 2005 11:19:46 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.3/8.13.3) with ESMTP id jANGJkKc014294; Wed, 23 Nov 2005 11:19:46 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 76D537302F; Wed, 23 Nov 2005 11:19:46 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051123161946.76D537302F@freebsd-current.sentex.ca> Date: Wed, 23 Nov 2005 11:19:46 -0500 (EST) X-Virus-Scanned: ClamAV version 0.86, clamav-milter version 0.86 on clamscanner1 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on i386/pc98 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2005 16:19:50 -0000 TB --- 2005-11-23 15:07:06 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-11-23 15:07:06 - starting HEAD tinderbox run for i386/pc98 TB --- 2005-11-23 15:07:06 - cleaning the object tree TB --- 2005-11-23 15:07:39 - checking out the source tree TB --- 2005-11-23 15:07:39 - cd /tinderbox/HEAD/i386/pc98 TB --- 2005-11-23 15:07:39 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-11-23 15:13:40 - building world (CFLAGS=-O2 -pipe) TB --- 2005-11-23 15:13:40 - cd /src TB --- 2005-11-23 15:13:40 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-11-23 16:18:06 - generating LINT kernel config TB --- 2005-11-23 16:18:06 - cd /src/sys/pc98/conf TB --- 2005-11-23 16:18:06 - /usr/bin/make -B LINT TB --- 2005-11-23 16:18:06 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-11-23 16:18:06 - cd /src TB --- 2005-11-23 16:18:06 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Nov 23 16:18:06 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 [...] awk -f /src/sys/tools/makeobjops.awk /src/sys/kern/linker_if.m -h awk -f /src/sys/tools/makeobjops.awk /src/sys/libkern/iconv_converter_if.m -h awk -f /src/sys/tools/makeobjops.awk /src/sys/pci/agp_if.m -h awk -f /src/sys/tools/makeobjops.awk /src/sys/pc98/pc98/canbus_if.m -h rm -f .newdep /usr/bin/make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES | MKDEP_CPP="cc -E" CC="cc" xargs mkdep -a -f .newdep -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/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/contrib/dev/ath/freebsd -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding /src/sys/i386/i386/mp_machdep.c:34:21: opt_smp.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-23 16:19:46 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-23 16:19:46 - ERROR: failed to build lint kernel TB --- 2005-11-23 16:19:46 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 15:58:28 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E0CC16A41F for ; Wed, 23 Nov 2005 15:58:28 +0000 (GMT) (envelope-from kbuild@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E79C43D95 for ; Wed, 23 Nov 2005 15:57:58 +0000 (GMT) (envelope-from kbuild@gmail.com) Received: by xproxy.gmail.com with SMTP id t14so170187wxc for ; Wed, 23 Nov 2005 07:57:54 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:mime-version:content-type; b=aMs1+ue1BTINKBFvpVaXQnKh8+tqbhHZaCjFZ60wXdo7DktMp3py/Bdo3wg6m5gGErR5sQeqjz/4buLrhn0mceLK1+ZaxDvwbw3QSyH9ePqVYYAfWClJlzO78uZRlAh1CcG8e+P8FXKAjkq7Df1rj07gNx02YyHyuxyNvfareeM= Received: by 10.65.237.13 with SMTP id o13mr2547866qbr; Wed, 23 Nov 2005 06:05:16 -0800 (PST) Received: by 10.65.228.3 with HTTP; Wed, 23 Nov 2005 06:05:16 -0800 (PST) Message-ID: Date: Wed, 23 Nov 2005 22:05:16 +0800 From: Sun Le To: freebsd-current@FreeBSD.org MIME-Version: 1.0 X-Mailman-Approved-At: Wed, 23 Nov 2005 16:20:39 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: delphij@freebsd.org Subject: meet up with a problem when doing the installation X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 15:58:28 -0000 Hi folks, I encountered a problem that need your help. The matter goes as follow: My box is Dell DIMENSION 1100 using Dell USB keyboard and mouse.When I installed the 6.0 release,I selected `boot with usb keyboard' option.Withthat,my usb keyboard worked well.Then I noticed that the usbd was been launched when the prompt appeared,and after that,When I set up my mouse,there is no option or protocols about the usb which can be selected.Moreover,of course,the mouse did not work.I hang on there. So,who can offer my some information that help me solve it? Many thanks in advance. Sandy -- Sun Le (Sandy) - Keep it simple,stupid and low-key From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 17:16:35 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E556C16A41F for ; Wed, 23 Nov 2005 17:16:35 +0000 (GMT) (envelope-from eculp@bafirst.com) Received: from bafirst.com (72-12-2-214.wan.networktel.net [72.12.2.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BDCE43D5D for ; Wed, 23 Nov 2005 17:16:27 +0000 (GMT) (envelope-from eculp@bafirst.com) Received: from localhost (localhost [127.0.0.1]) (uid 80) by bafirst.com with local; Wed, 23 Nov 2005 11:16:26 -0600 id 00095804.4384A3EA.000120DC Received: from local4.local.net (local4.local.net [192.168.1.4]) by mail.bafirst.com (Horde MIME library) with HTTP; Wed, 23 Nov 2005 11:16:26 -0600 Message-ID: <20051123111626.ix99g4tm4okg88w4@mail.bafirst.com> Date: Wed, 23 Nov 2005 11:16:26 -0600 From: eculp@bafirst.com To: freebsd-current@freebsd.org References: <20051120183309.ysgk624asksckwow@mail.bafirst.com> <20051121004749.GA39061@xor.obsecurity.org> <43812AC7.3020506@rogers.com> <20051121020816.GA19252@xor.obsecurity.org> <438136B5.9030506@freebsd.org> <20051121131713.bakf4048too0osk0@mail.bafirst.com> In-Reply-To: <20051121131713.bakf4048too0osk0@mail.bafirst.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.1-cvs Subject: Re: avail memory is short by 1G on my FreeBSD 6.0-STABLE MP Dell X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 17:16:36 -0000 Quoting eculp@bafirst.com: > Quoting Paul Saab : > >> Chad Leigh -- Shire.Net LLC wrote: >>> I assume you are talking about the "phenomenon" of RAM "missing" >>> due to PCI and other I/O mapping into the 4GB address space? What >>> struck me about the OP is that the amount of RAM "missing" is more >>> than I have ever seen due to this. My systems are usually >>> 3.4-3.6GB of RAM with 4GB installed, not 2.86GB (3005MB)... So are >>> we sure that the PCI space mapping is the problem? >>> >> Enable PAE and you'll get all your ram. > > Done that but I am going to wait until early tomorrow morning to > reboot because I want to get a verbose boot with this kernel and then > try the PAE kernel, for whatever. For Closure, enable PAE seems to get all ram as Chad said. I found the amounts a bit strange but a heck of a lot better. Boot with PAE now shows: real memory = 5368709120 (5120 MB) avail memory = 4185292800 (3991 MB) Boot withoug PAE shows: real memory = 3220963328 (3071 MB) avail memory = 3151077376 (3005 MB) Of course now I will need to recompile the kernel with the modules that we now load, some of which I forgot but probably a small price for almost a GB more memory and if I'm lucky the kernel might even be a bit faster ;) Thanks again for all your suggestions and comments, it was definitly a learning experience. ed P.S. No problem at all with the kernel booting or anything, just be sure to compile in all the modules that you are now using. From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 19:07:08 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05A0416A452 for ; Wed, 23 Nov 2005 19:07:08 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 653EC43D62 for ; Wed, 23 Nov 2005 19:07:06 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2489445 for ; Wed, 23 Nov 2005 14:07:06 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jANJ6xDQ092202 for ; Wed, 23 Nov 2005 14:07:02 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: current@freebsd.org Date: Wed, 23 Nov 2005 14:06:05 -0500 User-Agent: KMail/1.8.2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511231406.06282.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Subject: nve locking fixes round 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 19:07:08 -0000 Ok, now that the first set of locking overhaul is in the tree, can folks with working nve(4) adapters test the patch referenced below and make sure there are no regressions. Having the IFF_UP fiddling turned off may or may not help folks getting the TX timeouts as well, btw, so if people are feeling brave they can try this patch as well. Note it is only applicable to recent current. http://www.FreeBSD.org/~jhb/patches/nve_locking.patch -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 20:18:39 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F010D16A41F for ; Wed, 23 Nov 2005 20:18:39 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id EEBFE43D55 for ; Wed, 23 Nov 2005 20:18:38 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 5954F1A3C1C for ; Wed, 23 Nov 2005 12:18:38 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C7BB051592; Wed, 23 Nov 2005 15:18:37 -0500 (EST) Date: Wed, 23 Nov 2005 15:18:37 -0500 From: Kris Kennaway To: current@FreeBSD.org Message-ID: <20051123201837.GA4822@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IJpNTDwzlM2Ie8A6" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: 4BSD process starvation during I/O X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 20:18:40 -0000 --IJpNTDwzlM2Ie8A6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I have noticed that when multiple identical processes (e.g. gtar, or dd) are run on 4BSD, when there are N CPUs on a machine there will be N processes that run with a higher CPU share than all the others. As a result, these N processes finish first, then another N, and so on. This is true under both 4.11 and 6.0 (so in that sense it's not so surprising), but the effect is much more pronounced on 6.0 (which may be possible to fix). Here are the exit times for 6 identical gtar processes (and same 4.11 gtar binary) started together on a 2-CPU machine: 6.0: 1132776233 1132776235 1132776264 1132776265 1132776279 1132776279 238.86 real 10.87 user 166.00 sys You can see they finish in pairs, and there's a spread of 46 seconds from first to last. On 4.11: 1132775426 1132775429 1132775431 1132775432 1132775448 1132775449 275.56 real 0.43 user 336.26 sys They also finish in pairs, but the spread is half, at 23 seconds. This seems to be correlated to the rate at which the processes perform I/O. On a quad amd64 machine running 6.0 when I run multiple dd processes at different offsets in a md device: 268435456 bytes transferred in 1.734285 secs (154781618 bytes/sec) 268435456 bytes transferred in 1.737857 secs (154463501 bytes/sec) 268435456 bytes transferred in 1.751760 secs (153237575 bytes/sec) 268435456 bytes transferred in 3.263460 secs (82254865 bytes/sec) 268435456 bytes transferred in 3.295294 secs (81460244 bytes/sec) 268435456 bytes transferred in 3.349770 secs (80135487 bytes/sec) 268435456 bytes transferred in 4.716637 secs (56912467 bytes/sec) 268435456 bytes transferred in 4.850927 secs (55336941 bytes/sec) 268435456 bytes transferred in 4.953528 secs (54190760 bytes/sec) They finish in groups of 3 here since the 4th CPU is being used to drive the md worker thread (which takes up most of the CPU). In this case the first 3 dd processes get essentially 100% of the CPU, and the rest get close to 0% until those 3 processes finish. Perhaps this can be tweaked. Kris P.S. Please, no responses about how maybe someone could write a new scheduler that doesn't have this property. --IJpNTDwzlM2Ie8A6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhM6dWry0BWjoQKURAhHYAJsGeMDK0VC4L1SjiwVNqBXZlXhvsACdEu8Q i/aW/zCh2xRnTkRffNlS3SQ= =5sR6 -----END PGP SIGNATURE----- --IJpNTDwzlM2Ie8A6-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 21:02:22 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5690116A420 for ; Wed, 23 Nov 2005 21:02:22 +0000 (GMT) (envelope-from chris@haakonia.hitnet.rwth-aachen.de) Received: from ms-dienst.rz.rwth-aachen.de (ms-1.rz.RWTH-Aachen.DE [134.130.3.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id F36A143D75 for ; Wed, 23 Nov 2005 21:02:05 +0000 (GMT) (envelope-from chris@haakonia.hitnet.rwth-aachen.de) Received: from r220-1 (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by ms-dienst.rz.rwth-aachen.de (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0IQF007R3EFF3A@ms-dienst.rz.rwth-aachen.de> for freebsd-current@freebsd.org; Wed, 23 Nov 2005 22:02:04 +0100 (MET) Received: from relay.rwth-aachen.de ([134.130.3.1]) by r220-1 (MailMonitor for SMTP v1.2.2 ) ; Wed, 23 Nov 2005 22:02:02 +0100 (MET) Received: from bigboss.hitnet.rwth-aachen.de (bigspace.hitnet.RWTH-Aachen.DE [137.226.181.2]) by relay.rwth-aachen.de (8.13.3/8.13.3/1) with ESMTP id jANL21jH016382; Wed, 23 Nov 2005 22:02:01 +0100 (MET) Received: from lorien.hitnet.rwth-aachen.de ([137.226.181.92] helo=haakonia.hitnet.rwth-aachen.de) by bigboss.hitnet.rwth-aachen.de with esmtp (Exim 3.35 #1 (Debian)) id 1Ef1kc-0005GT-00; Wed, 23 Nov 2005 22:01:58 +0100 Received: by haakonia.hitnet.rwth-aachen.de (Postfix, from userid 1001) id 2D0363F40B; Wed, 23 Nov 2005 22:01:57 +0100 (CET) Date: Wed, 23 Nov 2005 22:01:56 +0100 From: Christian Brueffer In-reply-to: <20051122141101.G24336@carver.gumbysoft.com> To: Doug White Message-id: <20051123210156.GC1856@unixpages.org> MIME-version: 1.0 Content-type: multipart/signed; boundary=L6iaP+gRLNZHKoI4; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-disposition: inline User-Agent: Mutt/1.5.11 X-Operating-System: FreeBSD 6.0-STABLE X-PGP-Key: http://people.FreeBSD.org/~brueffer/brueffer.key.asc X-PGP-Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D References: <200511150403.jAF43B6f001417@jerry.xoo.net> <20051119162011.I88861@carver.gumbysoft.com> <20051120011438.GA4194@unixpages.org> <20051122141101.G24336@carver.gumbysoft.com> Cc: Ulf Kieber , freebsd-current@freebsd.org Subject: Re: GEOM error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 21:02:22 -0000 --L6iaP+gRLNZHKoI4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 22, 2005 at 02:11:23PM -0800, Doug White wrote: > On Sun, 20 Nov 2005, Christian Brueffer wrote: >=20 > > On Sat, Nov 19, 2005 at 04:22:11PM -0800, Doug White wrote: > > > On Tue, 15 Nov 2005, Ulf Kieber wrote: > > > > > > > Re, > > > > > > > > on a 6.0-RELEASE I receive the following error since I tried restor= ing > > > > a large dump > > > > > > > > Nov 14 12:30:11 nexus kernel: g_vfs_done():da1s1d.bde[WRITE(offset= =3D72350695424, length=3D131072)]error =3D 1 > > > > > > > > Besides that, no other errors are logged, especially no SCSI errors. > > > > The problem persists even after the restore has completed. > > > > > > errno 1 is EPERM ("Operation not permitted") and is generally returne= d if > > > you attempt to write somewhere you're not allowed to. Considering the > > > offset is near the end of the disk, GBDE may be trying to prevent you= from > > > overwriting metadata blocks at the end of the partition. How or why > > > restore(8) would be writing there I'm not sure. > > > > > > A SCSI error would return as errno 5 (EIO, "Input/output error"). > > > > > > > I get the same messages with my external USB drive from time to time > > (interestingly also GBDE encrypted). > > > > Nov 20 02:03:30 haakonia kernel: g_vfs_done():da3s2c.bde[WRITE(offset= =3D383341297664, length=3D65536)]error =3D 1 > > > > The message repeats every 30 seconds and trying to unmount the file > > system fails. When I try to shut the system down, the message appears > > n > 50 times followed by a panic. > > > > Is it possible that the system tries to write on a bad sector and > > consequently fails (provided that the on-disk sector remapping also > > fails)? >=20 > You would get a SCSI error in that case since usb storage is attached > through CAM. >=20 Ok. Any suggestion on where to go from here? I can trigger this pretty reliably on the drive. Just have to copy enough data around. - Christian --=20 Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D --L6iaP+gRLNZHKoI4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhNjEbHYXjKDtmC0RAkWLAJ0YdRNa8PMuwdPTb/IaD5WTKExv/wCgkH3e WGszBBShJGaKfAQh8JpMrPc= =QVgL -----END PGP SIGNATURE----- --L6iaP+gRLNZHKoI4-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 21:08:32 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9B2E16A41F for ; Wed, 23 Nov 2005 21:08:32 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from leguin.anholt.net (69-30-77-85.dq1sn.easystreet.com [69.30.77.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DCD043D78 for ; Wed, 23 Nov 2005 21:08:16 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from leguin.anholt.net (localhost [127.0.0.1]) by leguin.anholt.net (8.13.4/8.13.1) with ESMTP id jANL8Eqj049290 for ; Wed, 23 Nov 2005 13:08:14 -0800 (PST) (envelope-from eta@lclark.edu) Received: (from anholt@localhost) by leguin.anholt.net (8.13.4/8.13.1/Submit) id jANL8EeK049289 for current@freebsd.org; Wed, 23 Nov 2005 13:08:14 -0800 (PST) (envelope-from eta@lclark.edu) X-Authentication-Warning: leguin.anholt.net: anholt set sender to eta@lclark.edu using -f From: Eric Anholt To: current@freebsd.org In-Reply-To: <1132743283.1197.55.camel@leguin> References: <1132743283.1197.55.camel@leguin> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-xUKrEWBlhES+6UWEue1c" Date: Wed, 23 Nov 2005 13:08:13 -0800 Message-Id: <1132780093.1197.60.camel@leguin> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Cc: Subject: Re: DRM update for testing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 21:08:33 -0000 --=-xUKrEWBlhES+6UWEue1c Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2005-11-23 at 02:54 -0800, Eric Anholt wrote: > I've got a patch at: > http://people.freebsd.org/~anholt/dri/drm-sys-20051123.diff > for testing, which merges DRM CVS into FreeBSD. I've done basic tests > of a recent DRM CVS with WITNESS on AGP/PCI Matrox, AGP/PCI Rage 128, > AGP Radeon r100/r200/r300, AGP Savage4 (new!), SiS, and 3dfx, and this > version should be equivalent to what I tested. I'll do another pass of > testing before I commit, but I'd also like to get some wider testing so > more panics can show up if they exist. This particular diff has only > been compile-tested with LINT on amd64 so far. I've fixed the lack of savage module Makefile in the diff and updated the diff in-place. --=20 Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org --=-xUKrEWBlhES+6UWEue1c Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDhNo9HUdvYGzw6vcRAh1WAJ9mp6BNumPftp9EulHlLCXZna2yTgCeNf5c CcKvNgraWZLGgnH3f47VXg8= =uuv2 -----END PGP SIGNATURE----- --=-xUKrEWBlhES+6UWEue1c-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 21:26:29 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AEBC16A41F for ; Wed, 23 Nov 2005 21:26:29 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from ant.bwct.de (ant.bwct.de [85.159.14.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DE8C43D72 for ; Wed, 23 Nov 2005 21:26:24 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by ant.bwct.de (8.12.11/8.12.11) with ESMTP id jANLQG27007109; Wed, 23 Nov 2005 22:26:17 +0100 (CET) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id jANLQ5uO024681 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Nov 2005 22:26:06 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id jANLQ5WB012627; Wed, 23 Nov 2005 22:26:05 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id jANLQ1gr012626; Wed, 23 Nov 2005 22:26:01 +0100 (CET) (envelope-from ticso) Date: Wed, 23 Nov 2005 22:26:01 +0100 From: Bernd Walter To: Christian Brueffer Message-ID: <20051123212600.GQ8256@cicely12.cicely.de> References: <200511150403.jAF43B6f001417@jerry.xoo.net> <20051119162011.I88861@carver.gumbysoft.com> <20051120011438.GA4194@unixpages.org> <20051122141101.G24336@carver.gumbysoft.com> <20051123210156.GC1856@unixpages.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051123210156.GC1856@unixpages.org> X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 X-Spam-Report: * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on cicely12.cicely.de Cc: Ulf Kieber , freebsd-current@freebsd.org Subject: Re: GEOM error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2005 21:26:29 -0000 On Wed, Nov 23, 2005 at 10:01:56PM +0100, Christian Brueffer wrote: > On Tue, Nov 22, 2005 at 02:11:23PM -0800, Doug White wrote: > > On Sun, 20 Nov 2005, Christian Brueffer wrote: > > > > > On Sat, Nov 19, 2005 at 04:22:11PM -0800, Doug White wrote: > > > > On Tue, 15 Nov 2005, Ulf Kieber wrote: > > > > > > > > > Re, > > > > > > > > > > on a 6.0-RELEASE I receive the following error since I tried restoring > > > > > a large dump > > > > > > > > > > Nov 14 12:30:11 nexus kernel: g_vfs_done():da1s1d.bde[WRITE(offset=72350695424, length=131072)]error = 1 > > > > > > > > > > Besides that, no other errors are logged, especially no SCSI errors. > > > > > The problem persists even after the restore has completed. > > > > > > > > errno 1 is EPERM ("Operation not permitted") and is generally returned if > > > > you attempt to write somewhere you're not allowed to. Considering the > > > > offset is near the end of the disk, GBDE may be trying to prevent you from > > > > overwriting metadata blocks at the end of the partition. How or why > > > > restore(8) would be writing there I'm not sure. > > > > > > > > A SCSI error would return as errno 5 (EIO, "Input/output error"). > > > > > > > > > > I get the same messages with my external USB drive from time to time > > > (interestingly also GBDE encrypted). > > > > > > Nov 20 02:03:30 haakonia kernel: g_vfs_done():da3s2c.bde[WRITE(offset=383341297664, length=65536)]error = 1 > > > > > > The message repeats every 30 seconds and trying to unmount the file > > > system fails. When I try to shut the system down, the message appears > > > n > 50 times followed by a panic. > > > > > > Is it possible that the system tries to write on a bad sector and > > > consequently fails (provided that the on-disk sector remapping also > > > fails)? > > > > You would get a SCSI error in that case since usb storage is attached > > through CAM. > > > > Ok. Any suggestion on where to go from here? I can trigger this pretty > reliably on the drive. Just have to copy enough data around. I don't know if the offset is in Bytes or sector, but even in case of Bytes the second example is at 714G, which is obviously out of disk size unless you are using multiple drives, which is not likely for an USB drive. The first one is at 134G, which is also very high, the owner should compare it with the physical disk size. So Doug is absolutely correct, the access isn't allowed, because out of range. I would say a corrupted FS, partition table or something like that. Don't know why - maybe GBDE's fault, but could very well any other reason for data corruption, faulty RAM, etc... -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 20:59:08 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1BF2D16A41F for ; Wed, 23 Nov 2005 20:59:08 +0000 (GMT) (envelope-from misho@interbgc.com) Received: from mail.interbgc.com (mx03.interbgc.com [217.9.224.229]) by mx1.FreeBSD.org (Postfix) with SMTP id 6A20C43D46 for ; Wed, 23 Nov 2005 20:59:05 +0000 (GMT) (envelope-from misho@interbgc.com) Received: (qmail 93162 invoked from network); 23 Nov 2005 20:59:04 -0000 Received: from misho@interbgc.com by keeper.interbgc.com by uid 1002 with qmail-scanner-1.14 (uvscan: v4.2.40/v4374. spamassassin: 2.63. Clear:SA:0(-2.6/8.0):. Processed in 3.054453 secs); 23 Nov 2005 20:59:04 -0000 X-Spam-Status: No, hits=-2.6 required=8.0 Received: from topilapi-wlan.ddns.cablebg.net (HELO misho) (213.240.221.12) by mx03.interbgc.com with SMTP; 23 Nov 2005 20:59:01 -0000 Message-ID: <006701c5f070$bab75e70$0cddf0d5@misho> From: "Mihail Balikov" To: "Kris Kennaway" References: <20051123030304.GA84202@xor.obsecurity.org> <20051123084653.GA90927@xor.obsecurity.org> Date: Wed, 23 Nov 2005 22:59:00 +0200 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.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 X-Mailman-Approved-At: Wed, 23 Nov 2005 21:49:28 +0000 Cc: current@freebsd.org, net@freebsd.org Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mihail Balikov List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2005 20:59:08 -0000 try to enable kern.polling sysctl -w kern.polling.enable=1 ----- Original Message ----- From: "Kris Kennaway" To: "John Polstra" Cc: ; ; "Kris Kennaway" Sent: Wednesday, November 23, 2005 10:46 AM Subject: Re: em interrupt storm From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 22:17:51 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E2D216A422 for ; Wed, 23 Nov 2005 22:17:51 +0000 (GMT) (envelope-from chris@haakonia.hitnet.rwth-aachen.de) Received: from ms-dienst.rz.rwth-aachen.de (ms-1.rz.RWTH-Aachen.DE [134.130.3.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B17743D62 for ; Wed, 23 Nov 2005 22:17:38 +0000 (GMT) (envelope-from chris@haakonia.hitnet.rwth-aachen.de) Received: from r220-1 (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by ms-dienst.rz.rwth-aachen.de (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0IQF00BMEHXCEC@ms-dienst.rz.rwth-aachen.de> for freebsd-current@freebsd.org; Wed, 23 Nov 2005 23:17:37 +0100 (MET) Received: from relay.rwth-aachen.de ([134.130.3.1]) by r220-1 (MailMonitor for SMTP v1.2.2 ) ; Wed, 23 Nov 2005 23:17:35 +0100 (MET) Received: from bigboss.hitnet.rwth-aachen.de (bigspace.hitnet.RWTH-Aachen.DE [137.226.181.2]) by relay.rwth-aachen.de (8.13.3/8.13.3/1) with ESMTP id jANMHZDl026228; Wed, 23 Nov 2005 23:17:35 +0100 (MET) Received: from lorien.hitnet.rwth-aachen.de ([137.226.181.92] helo=haakonia.hitnet.rwth-aachen.de) by bigboss.hitnet.rwth-aachen.de with esmtp (Exim 3.35 #1 (Debian)) id 1Ef2vn-0008JK-00; Wed, 23 Nov 2005 23:17:35 +0100 Received: by haakonia.hitnet.rwth-aachen.de (Postfix, from userid 1001) id 2CEDF3F40B; Wed, 23 Nov 2005 23:17:34 +0100 (CET) Date: Wed, 23 Nov 2005 23:17:34 +0100 From: Christian Brueffer In-reply-to: <20051123212600.GQ8256@cicely12.cicely.de> To: ticso@cicely.de Message-id: <20051123221734.GD1856@unixpages.org> MIME-version: 1.0 Content-type: multipart/signed; boundary=KdquIMZPjGJQvRdI; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-disposition: inline User-Agent: Mutt/1.5.11 X-Operating-System: FreeBSD 6.0-STABLE X-PGP-Key: http://people.FreeBSD.org/~brueffer/brueffer.key.asc X-PGP-Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D References: <200511150403.jAF43B6f001417@jerry.xoo.net> <20051119162011.I88861@carver.gumbysoft.com> <20051120011438.GA4194@unixpages.org> <20051122141101.G24336@carver.gumbysoft.com> <20051123210156.GC1856@unixpages.org> <20051123212600.GQ8256@cicely12.cicely.de> Cc: Ulf Kieber , freebsd-current@freebsd.org Subject: Re: GEOM error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 22:17:51 -0000 --KdquIMZPjGJQvRdI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 23, 2005 at 10:26:01PM +0100, Bernd Walter wrote: > On Wed, Nov 23, 2005 at 10:01:56PM +0100, Christian Brueffer wrote: > > On Tue, Nov 22, 2005 at 02:11:23PM -0800, Doug White wrote: > > > On Sun, 20 Nov 2005, Christian Brueffer wrote: > > >=20 > > > > On Sat, Nov 19, 2005 at 04:22:11PM -0800, Doug White wrote: > > > > > On Tue, 15 Nov 2005, Ulf Kieber wrote: > > > > > > > > > > > Re, > > > > > > > > > > > > on a 6.0-RELEASE I receive the following error since I tried re= storing > > > > > > a large dump > > > > > > > > > > > > Nov 14 12:30:11 nexus kernel: g_vfs_done():da1s1d.bde[WRITE(off= set=3D72350695424, length=3D131072)]error =3D 1 > > > > > > > > > > > > Besides that, no other errors are logged, especially no SCSI er= rors. > > > > > > The problem persists even after the restore has completed. > > > > > > > > > > errno 1 is EPERM ("Operation not permitted") and is generally ret= urned if > > > > > you attempt to write somewhere you're not allowed to. Considering= the > > > > > offset is near the end of the disk, GBDE may be trying to prevent= you from > > > > > overwriting metadata blocks at the end of the partition. How or w= hy > > > > > restore(8) would be writing there I'm not sure. > > > > > > > > > > A SCSI error would return as errno 5 (EIO, "Input/output error"). > > > > > > > > > > > > > I get the same messages with my external USB drive from time to time > > > > (interestingly also GBDE encrypted). > > > > > > > > Nov 20 02:03:30 haakonia kernel: g_vfs_done():da3s2c.bde[WRITE(offs= et=3D383341297664, length=3D65536)]error =3D 1 > > > > > > > > The message repeats every 30 seconds and trying to unmount the file > > > > system fails. When I try to shut the system down, the message appe= ars > > > > n > 50 times followed by a panic. > > > > > > > > Is it possible that the system tries to write on a bad sector and > > > > consequently fails (provided that the on-disk sector remapping also > > > > fails)? > > >=20 > > > You would get a SCSI error in that case since usb storage is attached > > > through CAM. > > >=20 > >=20 > > Ok. Any suggestion on where to go from here? I can trigger this pretty > > reliably on the drive. Just have to copy enough data around. >=20 > I don't know if the offset is in Bytes or sector, but even in case of > Bytes the second example is at 714G, which is obviously out of disk > size unless you are using multiple drives, which is not likely for an > USB drive. > The first one is at 134G, which is also very high, the owner should > compare it with the physical disk size. > So Doug is absolutely correct, the access isn't allowed, because out > of range. > I would say a corrupted FS, partition table or something like that. > Don't know why - maybe GBDE's fault, but could very well any other > reason for data corruption, faulty RAM, etc... >=20 In my case it is a 400GB PATA drive in an external enclosure. It only happens with this drive, tried it on two boxes (connection via USB or FireWire doesn't make a difference either). - Christian --=20 Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D --KdquIMZPjGJQvRdI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhOp+bHYXjKDtmC0RAppnAKC3uLS7xhmEnENeGTrWSMYa3+Vc5ACgsJHM 74eADkX+llS2iUq7CV2RKxk= =s5/L -----END PGP SIGNATURE----- --KdquIMZPjGJQvRdI-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 22:53:38 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 148CA16A41F for ; Wed, 23 Nov 2005 22:53:38 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C9D043D60 for ; Wed, 23 Nov 2005 22:53:35 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper [212.12.50.230]) by schlepper.zs64.net (8.13.3/8.12.9) with ESMTP id jANMrY1Z048163; Wed, 23 Nov 2005 23:53:34 +0100 (CET) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.3/8.12.9/Submit) id jANMrYoW048161; Wed, 23 Nov 2005 17:53:34 -0500 (EST) (envelope-from cracauer) Date: Wed, 23 Nov 2005 17:53:33 -0500 From: Martin Cracauer To: Nils Berzins Message-ID: <20051123175333.A48096@cons.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from nils.berzins@gmail.com on Wed, Nov 23, 2005 at 05:38:40AM +0200 Cc: current@freebsd.org Subject: Re: Trouble with amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2005 22:53:38 -0000 Nils Berzins wrote on Wed, Nov 23, 2005 at 05:38:40AM +0200: > Hi ! > > Few days ago I downloaded release 6.0 ISOs, in hope that I will finally be > able to run FreeBSD on my home computer. Unfortunately, booting from CD dies > with: > > > panic: sym: VTOBUS FAILED ! > > Is there something I can do to get around this error, or do I just wait for > more less stable 7.0 :-( > > Best Regards > Nils Berzins > > P.S. I have ASUS A8V-E Deluxe with Athlon 64D. More context please. I have an A8V-E SE which works fine with 6.0/i386 and 7-current/amd64. What's an Athlon 64D? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 23:02:40 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4CD016A41F for ; Wed, 23 Nov 2005 23:02:40 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73AE643D8E for ; Wed, 23 Nov 2005 23:02:21 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from smiley (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 2153F19F2D; Wed, 23 Nov 2005 15:08:59 -0800 (PST) From: "Darren Pilgrim" To: "'Scott Long'" , "'Kris Kennaway'" Date: Wed, 23 Nov 2005 15:02:05 -0800 Message-ID: <002801c5f081$f01ff200$642a15ac@smiley> 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.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <43842D41.1050401@samsco.org> Importance: Normal Cc: freebsd-current@freebsd.org Subject: RE: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 23:02:40 -0000 From: Scott Long > >>On Tue, 2005-11-22 at 22:03 -0500, Kris Kennaway wrote: > >> > >>>I am seeing the em driver undergoing an interrupt storm whenever the > >>>amr driver receives interrupts. In this case I was running newfs on > >>>the amr array and em0 was not in use: <...> > >>>This is on both 6.0-RELEASE and 6.0-STABLE. > > This is apparently a side effect of how we process interupts, which is > different from Windows and Linux. Since we mask the interrupt in the > APIC while the ithread runs, the Intel hardware tries to outsmart us > and continue delivering the interrupt via irq16. There are been > rumors on ways to turn off this 'feature', but none of them seem to > work. Since ithreads are integral to SMPng, and masking the APIC pins > in integral to making ithreads work, the solution will probably be to > be more aggressive in adopting MSI, and in doing filtered interrupt > handlers that don't require the APIC to be masked. Note that Solaris > and Darwin would likely exhibit the same problem since they handle > interrupts similar to us. Scott, from your message the problem is going to on any E7520 chipset, regardless of the NICs, disk controllers, etc. used in the system. Does this problem also exist for the E7525 chipset? I know the two are almost identical, but I figured it would be good to make sure. I ask because I have a machine with a Supermicro X6DAL-G (which uses the E7525) on which I got messages about interrupt storms during builds. This was back before if_em was fixed, so they were shelved along with use of the em interface until if_em was fixed. My apologies for not having the exact messages. I don't having access to the logs. Until this gets "fixed" in FreeBSD, what should those of us who are effectively stuck with this hardware do to avoid the problem? Does the problem exist in RELENG_4? From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 23:04:07 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE83416A429 for ; Wed, 23 Nov 2005 23:04:07 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from ant.bwct.de (ant.bwct.de [85.159.14.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44DF043D72 for ; Wed, 23 Nov 2005 23:03:33 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by ant.bwct.de (8.12.11/8.12.11) with ESMTP id jANN3EgE012287; Thu, 24 Nov 2005 00:03:27 +0100 (CET) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id jANN2xEo025527 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Nov 2005 00:02:59 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id jANN2wMC012929; Thu, 24 Nov 2005 00:02:58 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id jANN2t8N012928; Thu, 24 Nov 2005 00:02:55 +0100 (CET) (envelope-from ticso) Date: Thu, 24 Nov 2005 00:02:55 +0100 From: Bernd Walter To: Christian Brueffer Message-ID: <20051123230254.GA12630@cicely12.cicely.de> References: <200511150403.jAF43B6f001417@jerry.xoo.net> <20051119162011.I88861@carver.gumbysoft.com> <20051120011438.GA4194@unixpages.org> <20051122141101.G24336@carver.gumbysoft.com> <20051123210156.GC1856@unixpages.org> <20051123212600.GQ8256@cicely12.cicely.de> <20051123221734.GD1856@unixpages.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051123221734.GD1856@unixpages.org> X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 X-Spam-Report: * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on cicely12.cicely.de Cc: Ulf Kieber , ticso@cicely.de, freebsd-current@freebsd.org Subject: Re: GEOM error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Nov 2005 23:04:08 -0000 On Wed, Nov 23, 2005 at 11:17:34PM +0100, Christian Brueffer wrote: > On Wed, Nov 23, 2005 at 10:26:01PM +0100, Bernd Walter wrote: > > On Wed, Nov 23, 2005 at 10:01:56PM +0100, Christian Brueffer wrote: > > > On Tue, Nov 22, 2005 at 02:11:23PM -0800, Doug White wrote: > > > > On Sun, 20 Nov 2005, Christian Brueffer wrote: > > > > > Nov 20 02:03:30 haakonia kernel: g_vfs_done():da3s2c.bde[WRITE(offset=383341297664, length=65536)]error = 1 > > I don't know if the offset is in Bytes or sector, but even in case of > > Bytes the second example is at 714G, which is obviously out of disk > > size unless you are using multiple drives, which is not likely for an > > USB drive. > > In my case it is a 400GB PATA drive in an external enclosure. It only > happens with this drive, tried it on two boxes (connection via USB or > FireWire doesn't make a difference either). Damn - I managed to misscalculate the offsets (did /512 once itstead of 1024), but nevertheless it may fit here. The given write is near the end of your 400G drive. You should carefully check your partition sizes - not that your FS is just a few sectors longer than the partition. Don't forget to check the offset + 64k, which marks the end of the data range that the transfer wants to access and check all partition layers (slice, disklabel, etc) about correctness. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 23:16:37 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 908C216A420 for ; Wed, 23 Nov 2005 23:16:37 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D25143D55 for ; Wed, 23 Nov 2005 23:15:22 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jANNFIoG039411; Wed, 23 Nov 2005 16:15:18 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4384F807.6050105@samsco.org> Date: Wed, 23 Nov 2005 16:15:19 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Darren Pilgrim References: <002801c5f081$f01ff200$642a15ac@smiley> In-Reply-To: <002801c5f081$f01ff200$642a15ac@smiley> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-current@freebsd.org, 'Kris Kennaway' Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 23:16:37 -0000 Darren Pilgrim wrote: > From: Scott Long > >>>>On Tue, 2005-11-22 at 22:03 -0500, Kris Kennaway wrote: >>>> >>>> >>>>>I am seeing the em driver undergoing an interrupt storm whenever the >>>>>amr driver receives interrupts. In this case I was running newfs on >>>>>the amr array and em0 was not in use: > > <...> > >>>>>This is on both 6.0-RELEASE and 6.0-STABLE. >> >>This is apparently a side effect of how we process interupts, which is >>different from Windows and Linux. Since we mask the interrupt in the >>APIC while the ithread runs, the Intel hardware tries to outsmart us >>and continue delivering the interrupt via irq16. There are been >>rumors on ways to turn off this 'feature', but none of them seem to >>work. Since ithreads are integral to SMPng, and masking the APIC pins >>in integral to making ithreads work, the solution will probably be to >>be more aggressive in adopting MSI, and in doing filtered interrupt >>handlers that don't require the APIC to be masked. Note that Solaris >>and Darwin would likely exhibit the same problem since they handle >>interrupts similar to us. > > > Scott, from your message the problem is going to on any E7520 chipset, > regardless of the NICs, disk controllers, etc. used in the system. Does > this problem also exist for the E7525 chipset? I know the two are almost > identical, but I figured it would be good to make sure. I've directly observed it on 7501WV2 and 7520BD2 boards. I don't know if it's a problem that will affect other board configurations or cousin chipsets like the 7505 and 7525. > > I ask because I have a machine with a Supermicro X6DAL-G (which uses the > E7525) on which I got messages about interrupt storms during builds. This > was back before if_em was fixed, so they were shelved along with use of the > em interface until if_em was fixed. My apologies for not having the exact > messages. I don't having access to the logs. This could be the same problem, yes. > > Until this gets "fixed" in FreeBSD, what should those of us who are > effectively stuck with this hardware do to avoid the problem? Does the > problem exist in RELENG_4? > > What I've done is vacated the use of irq16 on my machines by disabling things like usb and if_em. This isn't ideal, of course. The storming doesn't usually cause a problem, but it can affect performance, especially if USB is involved. I only do this when I'm testing performance, otherwise I leave everything enabled and don't worry about it. 4.x won't see this problem since it handles interrupts in the more traditional way, but using 4.x also has many other tradeoffs that may or may not be worthwhile. Scott From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 23:52:13 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id ECBAF16A41F; Wed, 23 Nov 2005 23:52:12 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <438500BE.3020507@freebsd.org> Date: Thu, 24 Nov 2005 07:52:30 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.10) Gecko/20050806 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <20051123201837.GA4822@xor.obsecurity.org> In-Reply-To: <20051123201837.GA4822@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: current@FreeBSD.org Subject: Re: 4BSD process starvation during I/O X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 23:52:13 -0000 Kris Kennaway wrote: >Perhaps this can be tweaked. > >Kris > >P.S. Please, no responses about how maybe someone could write a new >scheduler that doesn't have this property. > > > > Can you try it again with FULL_PREEMPTION is turned on ? David Xu From owner-freebsd-current@FreeBSD.ORG Wed Nov 23 23:57:44 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03FDF16A41F; Wed, 23 Nov 2005 23:57:44 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7172743D4C; Wed, 23 Nov 2005 23:57:43 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 4B66F1A3C29; Wed, 23 Nov 2005 15:57:43 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5073F5158D; Wed, 23 Nov 2005 18:57:42 -0500 (EST) Date: Wed, 23 Nov 2005 18:57:42 -0500 From: Kris Kennaway To: David Xu Message-ID: <20051123235741.GA10825@xor.obsecurity.org> References: <20051123201837.GA4822@xor.obsecurity.org> <438500BE.3020507@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IJpNTDwzlM2Ie8A6" Content-Disposition: inline In-Reply-To: <438500BE.3020507@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: current@FreeBSD.org, Kris Kennaway Subject: Re: 4BSD process starvation during I/O X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 23 Nov 2005 23:57:44 -0000 --IJpNTDwzlM2Ie8A6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 24, 2005 at 07:52:30AM +0800, David Xu wrote: > Kris Kennaway wrote: >=20 > >Perhaps this can be tweaked. > > > >Kris > > > >P.S. Please, no responses about how maybe someone could write a new > >scheduler that doesn't have this property. > > > > > >=20 > > > Can you try it again with FULL_PREEMPTION is turned on ? OK. Is this option believed to be "safe" (i.e. largely free from bugs), and would it be useful to test more widely? Kris --IJpNTDwzlM2Ie8A6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhQH1Wry0BWjoQKURAkVNAJ4hOLWU2ec6WHjqo3vk/lx20M2W1QCfXtAr 2MO/9w0N9LXIMqECD3hdLJU= =d6/3 -----END PGP SIGNATURE----- --IJpNTDwzlM2Ie8A6-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 00:08:26 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5324E16A41F; Thu, 24 Nov 2005 00:08:26 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 625B843D5E; Thu, 24 Nov 2005 00:08:25 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 191A31A3C1A; Wed, 23 Nov 2005 16:08:25 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 67D6051592; Wed, 23 Nov 2005 19:08:24 -0500 (EST) Date: Wed, 23 Nov 2005 19:08:24 -0500 From: Kris Kennaway To: David Xu Message-ID: <20051124000824.GA11032@xor.obsecurity.org> References: <20051123201837.GA4822@xor.obsecurity.org> <438500BE.3020507@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OXfL5xGRrasGEqWY" Content-Disposition: inline In-Reply-To: <438500BE.3020507@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: current@FreeBSD.org, Kris Kennaway Subject: Re: 4BSD process starvation during I/O X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 00:08:26 -0000 --OXfL5xGRrasGEqWY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 24, 2005 at 07:52:30AM +0800, David Xu wrote: > Kris Kennaway wrote: >=20 > >Perhaps this can be tweaked. > > > >Kris > > > >P.S. Please, no responses about how maybe someone could write a new > >scheduler that doesn't have this property. > > > > > >=20 > > > Can you try it again with FULL_PREEMPTION is turned on ? Didn't really make a difference: # sh dd.sh 1 mdconfig: ioctl(/dev/mdctl): No such file or directory md0 16384+0 records in 16384+0 records out 268435456 bytes transferred in 1.325922 secs (202451919 bytes/sec) # sh dd.sh 2 md0 16384+0 records in 16384+0 records out 268435456 bytes transferred in 1.828649 secs (146794428 bytes/sec) 16384+0 records in 16384+0 records out 268435456 bytes transferred in 1.828715 secs (146789108 bytes/sec) # sh dd.sh 3 md0 16384+0 records in 16384+0 records out 268435456 bytes transferred in 1.875729 secs (143109929 bytes/sec) 16384+0 records in 16384+0 records out 268435456 bytes transferred in 1.879152 secs (142849247 bytes/sec) 16384+0 records in 16384+0 records out 268435456 bytes transferred in 1.883898 secs (142489377 bytes/sec) # sh dd.sh 4 md0 16384+0 records in 16384+0 records out 268435456 bytes transferred in 1.834240 secs (146346968 bytes/sec) 16384+0 records in 16384+0 records out 268435456 bytes transferred in 1.858093 secs (144468255 bytes/sec) 16384+0 records in 16384+0 records out 268435456 bytes transferred in 1.894780 secs (141671047 bytes/sec) 16384+0 records in 16384+0 records out 268435456 bytes transferred in 3.108751 secs (86348335 bytes/sec) # sh dd.sh 12 md0 16384+0 records in 16384+0 records out 268435456 bytes transferred in 1.860367 secs (144291681 bytes/sec) 16384+0 records in 16384+0 records out 268435456 bytes transferred in 1.885677 secs (142354961 bytes/sec) 16384+0 records in 16384+0 records out 268435456 bytes transferred in 1.983243 secs (135351757 bytes/sec) 16384+0 records in 16384+0 records out 268435456 bytes transferred in 3.409261 secs (78737139 bytes/sec) 16384+0 records in 16384+0 records out 268435456 bytes transferred in 3.762066 secs (71353204 bytes/sec) 16384+0 records in 16384+0 records out 268435456 bytes transferred in 3.910402 secs (68646510 bytes/sec) 16384+0 records in 16384+0 records out 268435456 bytes transferred in 5.086984 secs (52769079 bytes/sec) 16384+0 records in 16384+0 records out 268435456 bytes transferred in 5.566311 secs (48225018 bytes/sec) 16384+0 records in 16384+0 records out 268435456 bytes transferred in 5.816347 secs (46151897 bytes/sec) 16384+0 records in 16384+0 records out 268435456 bytes transferred in 6.818567 secs (39368309 bytes/sec) 16384+0 records in 16384+0 records out 268435456 bytes transferred in 7.375191 secs (36397085 bytes/sec) 16384+0 records in 16384+0 records out 268435456 bytes transferred in 7.568077 secs (35469440 bytes/sec) # --OXfL5xGRrasGEqWY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhQR3Wry0BWjoQKURAigDAJ951FvCLW4lhhL5laz//H5GaIkf6QCg0Daf 7rtmBRUfV9A8EIIAJrm4GsQ= =0Wlz -----END PGP SIGNATURE----- --OXfL5xGRrasGEqWY-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 00:10:23 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5540816A41F; Thu, 24 Nov 2005 00:10:23 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <43850500.5090908@freebsd.org> Date: Thu, 24 Nov 2005 08:10:40 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.10) Gecko/20050806 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <20051123201837.GA4822@xor.obsecurity.org> <438500BE.3020507@freebsd.org> <20051123235741.GA10825@xor.obsecurity.org> In-Reply-To: <20051123235741.GA10825@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: current@FreeBSD.org Subject: Re: 4BSD process starvation during I/O X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 00:10:24 -0000 Kris Kennaway wrote: >On Thu, Nov 24, 2005 at 07:52:30AM +0800, David Xu wrote: > > >>Kris Kennaway wrote: >> >> >> >>>Perhaps this can be tweaked. >>> >>>Kris >>> >>>P.S. Please, no responses about how maybe someone could write a new >>>scheduler that doesn't have this property. >>> >>> >>> >>> >>> >>> >>Can you try it again with FULL_PREEMPTION is turned on ? >> >> > >OK. Is this option believed to be "safe" (i.e. largely free from >bugs), and would it be useful to test more widely? > >Kris > > > I didn't test it on big machine. if I remembered it correctly, we only do preemption at user boundary if the FULL_PREEMPTION is turned off, you know system thread won't go to user boundary. :-) David Xu From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 00:34:46 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5811216A41F; Thu, 24 Nov 2005 00:34:46 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <43850AB7.4000109@freebsd.org> Date: Thu, 24 Nov 2005 08:35:03 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.10) Gecko/20050806 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <20051123201837.GA4822@xor.obsecurity.org> <438500BE.3020507@freebsd.org> <20051124000824.GA11032@xor.obsecurity.org> In-Reply-To: <20051124000824.GA11032@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: current@FreeBSD.org Subject: Re: 4BSD process starvation during I/O X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 00:34:47 -0000 Kris Kennaway wrote: >On Thu, Nov 24, 2005 at 07:52:30AM +0800, David Xu wrote: > > >>Kris Kennaway wrote: >> >> >> >>>Perhaps this can be tweaked. >>> >>>Kris >>> >>>P.S. Please, no responses about how maybe someone could write a new >>>scheduler that doesn't have this property. >>> >>> >>> >>> >>> >>> >>Can you try it again with FULL_PREEMPTION is turned on ? >> >> > >Didn't really make a difference: > > > This might only can be fixed when msleep no longer explicitly fiddles thread priority, let scheduler fully control it. From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 00:37:17 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 149F916A420; Thu, 24 Nov 2005 00:37:16 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <43850B4E.6050301@freebsd.org> Date: Thu, 24 Nov 2005 08:37:34 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.10) Gecko/20050806 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <200511231406.06282.jhb@freebsd.org> In-Reply-To: <200511231406.06282.jhb@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: nve locking fixes round 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 00:37:17 -0000 John Baldwin wrote: >Ok, now that the first set of locking overhaul is in the tree, can folks with >working nve(4) adapters test the patch referenced below and make sure there >are no regressions. Having the IFF_UP fiddling turned off may or may not >help folks getting the TX timeouts as well, btw, so if people are feeling >brave they can try this patch as well. Note it is only applicable to recent >current. > >http://www.FreeBSD.org/~jhb/patches/nve_locking.patch > > > Make no difference on my AMD64 machine,dmesg: http://people.freebsd.org/~davidxu/epox9nda3j.txt From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 00:40:51 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A53B116A41F; Thu, 24 Nov 2005 00:40:51 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38D3243D53; Thu, 24 Nov 2005 00:40:51 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 2179C1A3C2C; Wed, 23 Nov 2005 16:40:51 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7ECAC51593; Wed, 23 Nov 2005 19:40:50 -0500 (EST) Date: Wed, 23 Nov 2005 19:40:50 -0500 From: Kris Kennaway To: David Xu Message-ID: <20051124004050.GA11567@xor.obsecurity.org> References: <20051123201837.GA4822@xor.obsecurity.org> <438500BE.3020507@freebsd.org> <20051124000824.GA11032@xor.obsecurity.org> <43850AB7.4000109@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="G4iJoqBmSsgzjUCe" Content-Disposition: inline In-Reply-To: <43850AB7.4000109@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: current@FreeBSD.org, Kris Kennaway Subject: Re: 4BSD process starvation during I/O X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 00:40:51 -0000 --G4iJoqBmSsgzjUCe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 24, 2005 at 08:35:03AM +0800, David Xu wrote: > Kris Kennaway wrote: >=20 > >On Thu, Nov 24, 2005 at 07:52:30AM +0800, David Xu wrote: > >=20 > > > >>Kris Kennaway wrote: > >> > >> =20 > >> > >>>Perhaps this can be tweaked. > >>> > >>>Kris > >>> > >>>P.S. Please, no responses about how maybe someone could write a new > >>>scheduler that doesn't have this property. > >>> > >>> > >>> > >>> > >>> =20 > >>> > >>Can you try it again with FULL_PREEMPTION is turned on ? > >> =20 > >> > > > >Didn't really make a difference: > > > >=20 > > > This might only can be fixed when msleep no longer explicitly fiddles > thread priority, let scheduler fully control it. OK, thanks for looking at it. Kris --G4iJoqBmSsgzjUCe Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhQwSWry0BWjoQKURAnn6AKDzMMQodfA9r7duwyhm2wHFGbwVMwCgg7CQ h5octLmYlI2LIauhApQxbDg= =F5a+ -----END PGP SIGNATURE----- --G4iJoqBmSsgzjUCe-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 00:41:23 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0CD116A41F; Thu, 24 Nov 2005 00:41:23 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id F405A43D55; Thu, 24 Nov 2005 00:41:20 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jAO0fJQf039908; Wed, 23 Nov 2005 17:41:19 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43850C30.4060801@samsco.org> Date: Wed, 23 Nov 2005 17:41:20 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Xu References: <20051123201837.GA4822@xor.obsecurity.org> <438500BE.3020507@freebsd.org> <20051124000824.GA11032@xor.obsecurity.org> <43850AB7.4000109@freebsd.org> In-Reply-To: <43850AB7.4000109@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: current@freebsd.org, Kris Kennaway Subject: Re: 4BSD process starvation during I/O X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 00:41:23 -0000 David Xu wrote: > Kris Kennaway wrote: > >> On Thu, Nov 24, 2005 at 07:52:30AM +0800, David Xu wrote: >> >> >>> Kris Kennaway wrote: >>> >>> >>> >>>> Perhaps this can be tweaked. >>>> >>>> Kris >>>> >>>> P.S. Please, no responses about how maybe someone could write a new >>>> scheduler that doesn't have this property. >>>> >>>> >>>> >>>> >>>> >>> >>> Can you try it again with FULL_PREEMPTION is turned on ? >>> >> >> >> Didn't really make a difference: >> >> >> > This might only can be fixed when msleep no longer explicitly fiddles > thread priority, let scheduler fully control it. > I don't agree. The more likely problem according Stephan is that threads returning from userland get their priority elevated so they have a better chance of running right away. If you have plans to change how tsleep and msleep manage priorities, please discuss it on arch@ before you start making changes. Scott From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 00:54:16 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4409916A41F for ; Thu, 24 Nov 2005 00:54:16 +0000 (GMT) (envelope-from boris@brooknet.com.au) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 742C243D6B for ; Thu, 24 Nov 2005 00:54:12 +0000 (GMT) (envelope-from boris@brooknet.com.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87]) by mailout1.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id jAO0s9JO009183; Thu, 24 Nov 2005 11:54:09 +1100 Received: from [192.168.0.7] (ppp28C3.dyn.pacific.net.au [61.8.40.195]) by mailproxy2.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id jAO0s6GQ001949; Thu, 24 Nov 2005 11:54:07 +1100 In-Reply-To: <20051123201837.GA4822@xor.obsecurity.org> References: <20051123201837.GA4822@xor.obsecurity.org> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1686B643-388A-4848-9683-AEDF3B7F60FF@brooknet.com.au> Content-Transfer-Encoding: 7bit From: Sam Lawrance Date: Thu, 24 Nov 2005 11:54:05 +1100 To: Kris Kennaway X-Mailer: Apple Mail (2.746.2) Cc: current@freebsd.org Subject: Re: 4BSD process starvation during I/O X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 00:54:16 -0000 On 24/11/2005, at 7:18 AM, Kris Kennaway wrote: > I have noticed that when multiple identical processes (e.g. gtar, or > dd) are run on 4BSD, when there are N CPUs on a machine there will be > N processes that run with a higher CPU share than all the others. As > a result, these N processes finish first, then another N, and so on. > > This is true under both 4.11 and 6.0 (so in that sense it's not so > surprising), but the effect is much more pronounced on 6.0 (which may > be possible to fix). > > Here are the exit times for 6 identical gtar processes (and same 4.11 > gtar binary) started together on a 2-CPU machine: > > 6.0: > > 1132776233 > 1132776235 > 1132776264 > 1132776265 > 1132776279 > 1132776279 > 238.86 real 10.87 user 166.00 sys > > You can see they finish in pairs, and there's a spread of 46 seconds > from first to last. > > On 4.11: > > 1132775426 > 1132775429 > 1132775431 > 1132775432 > 1132775448 > 1132775449 > 275.56 real 0.43 user 336.26 sys > > They also finish in pairs, but the spread is half, at 23 seconds. > > This seems to be correlated to the rate at which the processes perform > I/O. On a quad amd64 machine running 6.0 when I run multiple dd > processes at different offsets in a md device: > > 268435456 bytes transferred in 1.734285 secs (154781618 bytes/sec) > 268435456 bytes transferred in 1.737857 secs (154463501 bytes/sec) > 268435456 bytes transferred in 1.751760 secs (153237575 bytes/sec) > 268435456 bytes transferred in 3.263460 secs (82254865 bytes/sec) > 268435456 bytes transferred in 3.295294 secs (81460244 bytes/sec) > 268435456 bytes transferred in 3.349770 secs (80135487 bytes/sec) > 268435456 bytes transferred in 4.716637 secs (56912467 bytes/sec) > 268435456 bytes transferred in 4.850927 secs (55336941 bytes/sec) > 268435456 bytes transferred in 4.953528 secs (54190760 bytes/sec) > > They finish in groups of 3 here since the 4th CPU is being used to > drive the md worker thread (which takes up most of the CPU). In this > case the first 3 dd processes get essentially 100% of the CPU, and the > rest get close to 0% until those 3 processes finish. > > Perhaps this can be tweaked. > I tried this on a dual Xeon, with 12 processes like mdconfig -a -t swap -s 320m dd if=/dev/md0 of=1 bs=1m skip=0 count=40 & dd if=/dev/md0 of=2 bs=1m skip=40 count=40 & ... and all processes finished within a frame of about 1 second. No interesting difference with HTT on or off. Generic SMP RELENG_6 from 8 November. Is your dd test different somehow? From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 01:02:50 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2B7616A41F for ; Thu, 24 Nov 2005 01:02:49 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id A049343D45 for ; Thu, 24 Nov 2005 01:02:32 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id BC1101A3C1A; Wed, 23 Nov 2005 17:02:31 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A0EDD51588; Wed, 23 Nov 2005 20:02:30 -0500 (EST) Date: Wed, 23 Nov 2005 20:02:29 -0500 From: Kris Kennaway To: Sam Lawrance Message-ID: <20051124010229.GA11953@xor.obsecurity.org> References: <20051123201837.GA4822@xor.obsecurity.org> <1686B643-388A-4848-9683-AEDF3B7F60FF@brooknet.com.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SLDf9lqlvOQaIe6s" Content-Disposition: inline In-Reply-To: <1686B643-388A-4848-9683-AEDF3B7F60FF@brooknet.com.au> User-Agent: Mutt/1.4.2.1i Cc: current@freebsd.org, Kris Kennaway Subject: Re: 4BSD process starvation during I/O X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 01:02:50 -0000 --SLDf9lqlvOQaIe6s Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 24, 2005 at 11:54:05AM +1100, Sam Lawrance wrote: >=20 > On 24/11/2005, at 7:18 AM, Kris Kennaway wrote: >=20 > >I have noticed that when multiple identical processes (e.g. gtar, or > >dd) are run on 4BSD, when there are N CPUs on a machine there will be > >N processes that run with a higher CPU share than all the others. As > >a result, these N processes finish first, then another N, and so on. > > > >This is true under both 4.11 and 6.0 (so in that sense it's not so > >surprising), but the effect is much more pronounced on 6.0 (which may > >be possible to fix). > > > >Here are the exit times for 6 identical gtar processes (and same 4.11 > >gtar binary) started together on a 2-CPU machine: > > > >6.0: > > > >1132776233 > >1132776235 > >1132776264 > >1132776265 > >1132776279 > >1132776279 > > 238.86 real 10.87 user 166.00 sys > > > >You can see they finish in pairs, and there's a spread of 46 seconds > >from first to last. > > > >On 4.11: > > > >1132775426 > >1132775429 > >1132775431 > >1132775432 > >1132775448 > >1132775449 > > 275.56 real 0.43 user 336.26 sys > > > >They also finish in pairs, but the spread is half, at 23 seconds. > > > >This seems to be correlated to the rate at which the processes perform > >I/O. On a quad amd64 machine running 6.0 when I run multiple dd > >processes at different offsets in a md device: > > > >268435456 bytes transferred in 1.734285 secs (154781618 bytes/sec) > >268435456 bytes transferred in 1.737857 secs (154463501 bytes/sec) > >268435456 bytes transferred in 1.751760 secs (153237575 bytes/sec) > >268435456 bytes transferred in 3.263460 secs (82254865 bytes/sec) > >268435456 bytes transferred in 3.295294 secs (81460244 bytes/sec) > >268435456 bytes transferred in 3.349770 secs (80135487 bytes/sec) > >268435456 bytes transferred in 4.716637 secs (56912467 bytes/sec) > >268435456 bytes transferred in 4.850927 secs (55336941 bytes/sec) > >268435456 bytes transferred in 4.953528 secs (54190760 bytes/sec) > > > >They finish in groups of 3 here since the 4th CPU is being used to > >drive the md worker thread (which takes up most of the CPU). In this > >case the first 3 dd processes get essentially 100% of the CPU, and the > >rest get close to 0% until those 3 processes finish. > > > >Perhaps this can be tweaked. > > >=20 > I tried this on a dual Xeon, with 12 processes like >=20 > mdconfig -a -t swap -s 320m > dd if=3D/dev/md0 of=3D1 bs=3D1m skip=3D0 count=3D40 & > dd if=3D/dev/md0 of=3D2 bs=3D1m skip=3D40 count=3D40 & You're reading from the md, not writing to it. Sorry if that wasn't clear. My test is: #!/bin/sh mdconfig -d -u 0 mdconfig -a -t swap -s 16g for i in `jot $1 1`; do dd if=3D/dev/zero of=3D/dev/md0 seek=3D$(($i*16384)) count=3D16384 = bs=3D16k > /dev/null & done wait Kris --SLDf9lqlvOQaIe6s Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhRElWry0BWjoQKURAvZTAJ4ujEdmqrD+cBVhAJfFlfb+zurHTQCgjkMF I0nwZfPgQGR9zs1vbGip7jQ= =mcvC -----END PGP SIGNATURE----- --SLDf9lqlvOQaIe6s-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 01:08:43 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B72C16A420 for ; Thu, 24 Nov 2005 01:08:43 +0000 (GMT) (envelope-from boris@brooknet.com.au) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E1A243D5A for ; Thu, 24 Nov 2005 01:08:21 +0000 (GMT) (envelope-from boris@brooknet.com.au) Received: from mailproxy2.pacific.net.au (mailproxy2.pacific.net.au [61.8.0.87]) by mailout1.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id jAO188Qc019899; Thu, 24 Nov 2005 12:08:08 +1100 Received: from [192.168.0.7] (ppp28C3.dyn.pacific.net.au [61.8.40.195]) by mailproxy2.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id jAO1853I012861; Thu, 24 Nov 2005 12:08:07 +1100 In-Reply-To: <20051124010229.GA11953@xor.obsecurity.org> References: <20051123201837.GA4822@xor.obsecurity.org> <1686B643-388A-4848-9683-AEDF3B7F60FF@brooknet.com.au> <20051124010229.GA11953@xor.obsecurity.org> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <07FB05F8-2AA8-485E-A61B-E6360882CE46@brooknet.com.au> Content-Transfer-Encoding: 7bit From: Sam Lawrance Date: Thu, 24 Nov 2005 12:08:05 +1100 To: Kris Kennaway X-Mailer: Apple Mail (2.746.2) Cc: current@freebsd.org Subject: Re: 4BSD process starvation during I/O X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 01:08:43 -0000 On 24/11/2005, at 12:02 PM, Kris Kennaway wrote: > On Thu, Nov 24, 2005 at 11:54:05AM +1100, Sam Lawrance wrote: >> >> On 24/11/2005, at 7:18 AM, Kris Kennaway wrote: >> >>> I have noticed that when multiple identical processes (e.g. gtar, or >>> dd) are run on 4BSD, when there are N CPUs on a machine there >>> will be >>> N processes that run with a higher CPU share than all the >>> others. As >>> a result, these N processes finish first, then another N, and so on. >>> >>> This is true under both 4.11 and 6.0 (so in that sense it's not so >>> surprising), but the effect is much more pronounced on 6.0 (which >>> may >>> be possible to fix). >>> >>> Here are the exit times for 6 identical gtar processes (and same >>> 4.11 >>> gtar binary) started together on a 2-CPU machine: >>> >>> 6.0: >>> >>> 1132776233 >>> 1132776235 >>> 1132776264 >>> 1132776265 >>> 1132776279 >>> 1132776279 >>> 238.86 real 10.87 user 166.00 sys >>> >>> You can see they finish in pairs, and there's a spread of 46 seconds >>> from first to last. >>> >>> On 4.11: >>> >>> 1132775426 >>> 1132775429 >>> 1132775431 >>> 1132775432 >>> 1132775448 >>> 1132775449 >>> 275.56 real 0.43 user 336.26 sys >>> >>> They also finish in pairs, but the spread is half, at 23 seconds. >>> >>> This seems to be correlated to the rate at which the processes >>> perform >>> I/O. On a quad amd64 machine running 6.0 when I run multiple dd >>> processes at different offsets in a md device: >>> >>> 268435456 bytes transferred in 1.734285 secs (154781618 bytes/sec) >>> 268435456 bytes transferred in 1.737857 secs (154463501 bytes/sec) >>> 268435456 bytes transferred in 1.751760 secs (153237575 bytes/sec) >>> 268435456 bytes transferred in 3.263460 secs (82254865 bytes/sec) >>> 268435456 bytes transferred in 3.295294 secs (81460244 bytes/sec) >>> 268435456 bytes transferred in 3.349770 secs (80135487 bytes/sec) >>> 268435456 bytes transferred in 4.716637 secs (56912467 bytes/sec) >>> 268435456 bytes transferred in 4.850927 secs (55336941 bytes/sec) >>> 268435456 bytes transferred in 4.953528 secs (54190760 bytes/sec) >>> >>> They finish in groups of 3 here since the 4th CPU is being used to >>> drive the md worker thread (which takes up most of the CPU). In >>> this >>> case the first 3 dd processes get essentially 100% of the CPU, >>> and the >>> rest get close to 0% until those 3 processes finish. >>> >>> Perhaps this can be tweaked. >>> >> >> I tried this on a dual Xeon, with 12 processes like >> >> mdconfig -a -t swap -s 320m >> dd if=/dev/md0 of=1 bs=1m skip=0 count=40 & >> dd if=/dev/md0 of=2 bs=1m skip=40 count=40 & > > You're reading from the md, not writing to it. Sorry if that wasn't > clear. > > My test is: > > #!/bin/sh > > mdconfig -d -u 0 > mdconfig -a -t swap -s 16g > for i in `jot $1 1`; do > dd if=/dev/zero of=/dev/md0 seek=$(($i*16384)) count=16384 > bs=16k > /dev/null & > done > wait Ah :-) Now I see it, very pronounced. From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 01:40:27 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41C1016A41F; Thu, 24 Nov 2005 01:40:27 +0000 (GMT) (envelope-from mv@roq.com) Received: from vault.mel.jumbuck.com (ppp166-27.static.internode.on.net [150.101.166.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28BEB43D5E; Thu, 24 Nov 2005 01:40:25 +0000 (GMT) (envelope-from mv@roq.com) Received: from vault.mel.jumbuck.com (localhost [127.0.0.1]) by vault.mel.jumbuck.com (Postfix) with ESMTP id 796F98A065; Thu, 24 Nov 2005 12:40:17 +1100 (EST) Received: from [192.168.46.52] (unknown [192.168.46.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by vault.mel.jumbuck.com (Postfix) with ESMTP id 470878A023; Thu, 24 Nov 2005 12:40:17 +1100 (EST) Message-ID: <43851A08.5080802@roq.com> Date: Thu, 24 Nov 2005 12:40:24 +1100 From: Michael Vince User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.12) Gecko/20051110 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <20051123030304.GA84202@xor.obsecurity.org> <20051123084653.GA90927@xor.obsecurity.org> In-Reply-To: <20051123084653.GA90927@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: net@freebsd.org, current@freebsd.org, John Polstra Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 01:40:27 -0000 Kris Kennaway wrote: >On Tue, Nov 22, 2005 at 08:54:49PM -0800, John Polstra wrote: > > >>On 23-Nov-2005 Kris Kennaway wrote: >> >> >>>I am seeing the em driver undergoing an interrupt storm whenever the >>>amr driver receives interrupts. In this case I was running newfs on >>>the amr array and em0 was not in use: >>> >>> 28 root 1 -68 -187 0K 8K CPU1 1 0:32 53.98% irq16: em0 >>> 36 root 1 -64 -183 0K 8K RUN 1 0:37 27.75% irq24: amr0 >>> >>># vmstat -i >>>interrupt total rate >>>irq1: atkbd0 2 0 >>>irq4: sio0 199 1 >>>irq6: fdc0 32 0 >>>irq13: npx0 1 0 >>>irq14: ata0 47 0 >>>irq15: ata1 931 5 >>>irq16: em0 6321801 37187 >>>irq24: amr0 28023 164 >>>cpu0: timer 337533 1985 >>>cpu1: timer 337285 1984 >>>Total 7025854 41328 >>> >>>When newfs finished (i.e. amr was idle), em0 stopped storming. >>> >>>MPTable: >>> >>> >>This is the dreaded interrupt aliasing problem that several of us have >>experienced with this chipset. High-numbered interrupts alias down to >>interrupts in the range 16..19 (or maybe 16..23), a multiple of 8 less >>than the original interupt. >> >>Nobody knows what causes it, and nobody knows how to fix it. >> >> > >This would be good to document somewhere so that people don't either >accidentally buy this hardware, or know what to expect when they run >it. > >Kris > > This is Intels latest server chipset designs and Dell are putting that chipset in all their servers. Luckily I haven't not seen the problem on any of my Dell servers (as long as I am looking at this right). This server has been running for a long time. vmstat -i interrupt total rate irq1: atkbd0 6 0 irq4: sio0 23433 0 irq6: fdc0 10 0 irq8: rtc 2631238611 128 irq13: npx0 1 0 irq14: ata0 99 0 irq16: uhci0 1507608958 73 irq18: uhci2 42005524 2 irq19: uhci1 3 0 irq23: atapci0 151 0 irq46: amr0 41344088 2 irq64: em0 1513106157 73 irq0: clk 2055605782 99 Total 7790932823 379 This one just transfered over 8gigs of data in 77seconds with around 1000 simultaneous tcp connections under a load of 35. Both seem OK. vmstat -i interrupt total rate irq4: sio0 315 0 irq13: npx0 1 0 irq14: ata0 47 0 irq16: uhci0 2894669 2 irq18: uhci2 977413 0 irq23: ehci0 3 0 irq46: amr0 883138 0 irq64: em0 2890414 2 cpu0: timer 2763566717 1999 cpu3: timer 2763797300 1999 cpu1: timer 2763551479 1999 cpu2: timer 2763797870 1999 Total 11062359366 8004 Mike From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 01:46:54 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74E6F16A41F; Thu, 24 Nov 2005 01:46:54 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74C4A43D83; Thu, 24 Nov 2005 01:46:23 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jAO1kFMa040293; Wed, 23 Nov 2005 18:46:15 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43851B69.5090701@samsco.org> Date: Wed, 23 Nov 2005 18:46:17 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Vince References: <20051123030304.GA84202@xor.obsecurity.org> <20051123084653.GA90927@xor.obsecurity.org> <43851A08.5080802@roq.com> In-Reply-To: <43851A08.5080802@roq.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: John Polstra , net@freebsd.org, current@freebsd.org, Kris Kennaway Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 01:46:54 -0000 Michael Vince wrote: > Kris Kennaway wrote: > >> On Tue, Nov 22, 2005 at 08:54:49PM -0800, John Polstra wrote: >> >> >>> On 23-Nov-2005 Kris Kennaway wrote: >>> >>> >>>> I am seeing the em driver undergoing an interrupt storm whenever the >>>> amr driver receives interrupts. In this case I was running newfs on >>>> the amr array and em0 was not in use: >>>> >>>> 28 root 1 -68 -187 0K 8K CPU1 1 0:32 53.98% >>>> irq16: em0 >>>> 36 root 1 -64 -183 0K 8K RUN 1 0:37 27.75% >>>> irq24: amr0 >>>> >>>> # vmstat -i >>>> interrupt total rate >>>> irq1: atkbd0 2 0 >>>> irq4: sio0 199 1 >>>> irq6: fdc0 32 0 >>>> irq13: npx0 1 0 >>>> irq14: ata0 47 0 >>>> irq15: ata1 931 5 >>>> irq16: em0 6321801 37187 >>>> irq24: amr0 28023 164 >>>> cpu0: timer 337533 1985 >>>> cpu1: timer 337285 1984 >>>> Total 7025854 41328 >>>> >>>> When newfs finished (i.e. amr was idle), em0 stopped storming. >>>> >>>> MPTable: >>>> >>> >>> This is the dreaded interrupt aliasing problem that several of us have >>> experienced with this chipset. High-numbered interrupts alias down to >>> interrupts in the range 16..19 (or maybe 16..23), a multiple of 8 less >>> than the original interupt. >>> >>> Nobody knows what causes it, and nobody knows how to fix it. >>> >> >> >> This would be good to document somewhere so that people don't either >> accidentally buy this hardware, or know what to expect when they run >> it. >> >> Kris >> >> > This is Intels latest server chipset designs and Dell are putting that > chipset in all their servers. > Luckily I haven't not seen the problem on any of my Dell servers (as > long as I am looking at this right). > > This server has been running for a long time. > vmstat -i > interrupt total rate > irq1: atkbd0 6 0 > irq4: sio0 23433 0 > irq6: fdc0 10 0 > irq8: rtc 2631238611 128 > irq13: npx0 1 0 > irq14: ata0 99 0 > irq16: uhci0 1507608958 73 > irq18: uhci2 42005524 2 > irq19: uhci1 3 0 > irq23: atapci0 151 0 > irq46: amr0 41344088 2 > irq64: em0 1513106157 73 > irq0: clk 2055605782 99 > Total 7790932823 379 > > This one just transfered over 8gigs of data in 77seconds with around > 1000 simultaneous tcp connections under a load of 35. Both seem OK. > vmstat -i > interrupt total rate > irq4: sio0 315 0 > irq13: npx0 1 0 > irq14: ata0 47 0 > irq16: uhci0 2894669 2 > irq18: uhci2 977413 0 > irq23: ehci0 3 0 > irq46: amr0 883138 0 > irq64: em0 2890414 2 > cpu0: timer 2763566717 1999 > cpu3: timer 2763797300 1999 > cpu1: timer 2763551479 1999 > cpu2: timer 2763797870 1999 > Total 11062359366 8004 > > Mike > > Looks like at least some of your interrupts are being aliased to irq16, which just happens to be USB(uhci) in this case. Note that the rate is the same between irq64 and irq16, and the totals are pretty close. If you don't need USB, I'd suggest turning it off. Scott From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 01:54:18 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3FFE16A41F for ; Thu, 24 Nov 2005 01:54:18 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 840B643D8E for ; Thu, 24 Nov 2005 01:54:07 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from smiley (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id F219C19F2D; Wed, 23 Nov 2005 18:00:47 -0800 (PST) From: "Darren Pilgrim" To: "'Scott Long'" Date: Wed, 23 Nov 2005 17:53:56 -0800 Message-ID: <000401c5f099$f1ae1f30$642a15ac@smiley> 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.6626 In-Reply-To: <4384F807.6050105@samsco.org> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Cc: freebsd-current@freebsd.org Subject: RE: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 01:54:19 -0000 From: Scott Long [mailto:scottl@samsco.org] > Darren Pilgrim wrote: > > > > Until this gets "fixed" in FreeBSD, what should those of us who are > > effectively stuck with this hardware do to avoid the problem? > > What I've done is vacated the use of irq16 on my machines by disabling > things like usb and if_em. Do the devices have to be really turned off (meaning disabled in the BIOS) or do I just not load the corresponding driver? If nothing is using irq16, does the aliasing not occur or does it just become transparent to FreeBSD? From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 01:57:11 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C96B16A422 for ; Thu, 24 Nov 2005 01:57:11 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE00443D95 for ; Thu, 24 Nov 2005 01:56:16 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jAO1uEfl040352; Wed, 23 Nov 2005 18:56:14 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43851DBF.9060702@samsco.org> Date: Wed, 23 Nov 2005 18:56:15 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Darren Pilgrim References: <000401c5f099$f1ae1f30$642a15ac@smiley> In-Reply-To: <000401c5f099$f1ae1f30$642a15ac@smiley> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-current@freebsd.org Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 01:57:11 -0000 Darren Pilgrim wrote: > From: Scott Long [mailto:scottl@samsco.org] > >>Darren Pilgrim wrote: >> >>>Until this gets "fixed" in FreeBSD, what should those of us who are >>>effectively stuck with this hardware do to avoid the problem? >> >>What I've done is vacated the use of irq16 on my machines by disabling >>things like usb and if_em. > > > Do the devices have to be really turned off (meaning disabled in the BIOS) > or do I just not load the corresponding driver? I think that either works. > > If nothing is using irq16, does the aliasing not occur or does it just > become transparent to FreeBSD? > > If no drivers request a particular interrupt vector, then it gets masked. The chipset probably still tries to deliver the interrupt, but it never makes it to the CPU and thus is transparent. Scott From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 03:27:43 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C736C16A420; Thu, 24 Nov 2005 03:27:43 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52F2543D55; Thu, 24 Nov 2005 03:27:42 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 3D3521A3C28; Wed, 23 Nov 2005 19:27:42 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 46AC451592; Wed, 23 Nov 2005 22:27:41 -0500 (EST) Date: Wed, 23 Nov 2005 22:27:41 -0500 From: Kris Kennaway To: Michael Vince Message-ID: <20051124032740.GA13569@xor.obsecurity.org> References: <20051123030304.GA84202@xor.obsecurity.org> <20051123084653.GA90927@xor.obsecurity.org> <43851A08.5080802@roq.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="oyUTqETQ0mS9luUI" Content-Disposition: inline In-Reply-To: <43851A08.5080802@roq.com> User-Agent: Mutt/1.4.2.1i Cc: John Polstra , net@freebsd.org, current@freebsd.org, Kris Kennaway Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 03:27:43 -0000 --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 24, 2005 at 12:40:24PM +1100, Michael Vince wrote: > chipset in all their servers. > Luckily I haven't not seen the problem on any of my Dell servers (as=20 > long as I am looking at this right). >=20 > This server has been running for a long time. > vmstat -i > interrupt total rate > irq1: atkbd0 6 0 > irq4: sio0 23433 0 > irq6: fdc0 10 0 > irq8: rtc 2631238611 128 > irq13: npx0 1 0 > irq14: ata0 99 0 The interrupt storm only happens when other interrupts are delivered to other devices, e.g. when you're doing a lot of filesystem I/O. =20 > irq16: uhci0 1507608958 73 > irq64: em0 1513106157 73 Both of these look like they might be experiencing it, since they have extremely high counts. Your USB controller shouldn't have that many interrupts, for example. > 1000 simultaneous tcp connections under a load of 35. Both seem OK. > vmstat -i > interrupt total rate > irq4: sio0 315 0 > irq13: npx0 1 0 > irq14: ata0 47 0 > irq16: uhci0 2894669 2 > irq64: em0 2890414 2 Again uhci seems to have a lot of interrupts. Kris --oyUTqETQ0mS9luUI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhTMsWry0BWjoQKURApuSAKDAJN9PEgWc4aGVvTxp8JIsluAk3QCffNrr 5TEzezZZCjVRkd4tMYZV1CY= =AYDB -----END PGP SIGNATURE----- --oyUTqETQ0mS9luUI-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 03:35:11 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFD8E16A41F; Thu, 24 Nov 2005 03:35:11 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id A90DB43D5C; Thu, 24 Nov 2005 03:35:00 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jAO3YwhK040830; Wed, 23 Nov 2005 20:34:59 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <438534E2.1000004@samsco.org> Date: Wed, 23 Nov 2005 20:34:58 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mihail Balikov References: <20051123030304.GA84202@xor.obsecurity.org> <20051123084653.GA90927@xor.obsecurity.org> <006701c5f070$bab75e70$0cddf0d5@misho> In-Reply-To: <006701c5f070$bab75e70$0cddf0d5@misho> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: net@freebsd.org, current@freebsd.org, Kris Kennaway Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 03:35:12 -0000 Mihail Balikov wrote: > try to enable kern.polling > > sysctl -w kern.polling.enable=1 > > Polling solves specific problems, but isn't a good choice for every situation. Scott From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 04:22:14 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 801F816A41F; Thu, 24 Nov 2005 04:22:14 +0000 (GMT) (envelope-from mv@roq.com) Received: from vault.mel.jumbuck.com (ppp166-27.static.internode.on.net [150.101.166.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE17943D66; Thu, 24 Nov 2005 04:22:12 +0000 (GMT) (envelope-from mv@roq.com) Received: from vault.mel.jumbuck.com (localhost [127.0.0.1]) by vault.mel.jumbuck.com (Postfix) with ESMTP id 5C4698A023; Thu, 24 Nov 2005 15:22:04 +1100 (EST) Received: from [192.168.46.52] (unknown [192.168.46.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by vault.mel.jumbuck.com (Postfix) with ESMTP id 38DE68A01F; Thu, 24 Nov 2005 15:22:04 +1100 (EST) Message-ID: <43853FF3.2050103@roq.com> Date: Thu, 24 Nov 2005 15:22:11 +1100 From: Michael Vince User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.12) Gecko/20051110 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <20051123030304.GA84202@xor.obsecurity.org> <20051123084653.GA90927@xor.obsecurity.org> <43851A08.5080802@roq.com> <43851B69.5090701@samsco.org> In-Reply-To: <43851B69.5090701@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: Kris Kennaway , current@freebsd.org, net@freebsd.org Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 04:22:14 -0000 Scott Long wrote: > Michael Vince wrote: > >> Kris Kennaway wrote: >> >>> On Tue, Nov 22, 2005 at 08:54:49PM -0800, John Polstra wrote: >>> >>> >>>> On 23-Nov-2005 Kris Kennaway wrote: >>>> >>>> >>>>> I am seeing the em driver undergoing an interrupt storm whenever the >>>>> amr driver receives interrupts. In this case I was running newfs on >>>>> the amr array and em0 was not in use: >>>>> >>>>> 28 root 1 -68 -187 0K 8K CPU1 1 0:32 53.98% >>>>> irq16: em0 >>>>> 36 root 1 -64 -183 0K 8K RUN 1 0:37 27.75% >>>>> irq24: amr0 >>>>> >>>>> # vmstat -i >>>>> interrupt total rate >>>>> irq1: atkbd0 2 0 >>>>> irq4: sio0 199 1 >>>>> irq6: fdc0 32 0 >>>>> irq13: npx0 1 0 >>>>> irq14: ata0 47 0 >>>>> irq15: ata1 931 5 >>>>> irq16: em0 6321801 37187 >>>>> irq24: amr0 28023 164 >>>>> cpu0: timer 337533 1985 >>>>> cpu1: timer 337285 1984 >>>>> Total 7025854 41328 >>>>> >>>>> When newfs finished (i.e. amr was idle), em0 stopped storming. >>>>> >>>>> MPTable: >>>>> >>>> >>>> >>>> This is the dreaded interrupt aliasing problem that several of us have >>>> experienced with this chipset. High-numbered interrupts alias down to >>>> interrupts in the range 16..19 (or maybe 16..23), a multiple of 8 less >>>> than the original interupt. >>>> >>>> Nobody knows what causes it, and nobody knows how to fix it. >>>> >>> >>> >>> >>> This would be good to document somewhere so that people don't either >>> accidentally buy this hardware, or know what to expect when they run >>> it. >>> >>> Kris >>> >>> >> This is Intels latest server chipset designs and Dell are putting >> that chipset in all their servers. >> Luckily I haven't not seen the problem on any of my Dell servers (as >> long as I am looking at this right). >> >> This server has been running for a long time. >> vmstat -i >> interrupt total rate >> irq1: atkbd0 6 0 >> irq4: sio0 23433 0 >> irq6: fdc0 10 0 >> irq8: rtc 2631238611 128 >> irq13: npx0 1 0 >> irq14: ata0 99 0 >> irq16: uhci0 1507608958 73 >> irq18: uhci2 42005524 2 >> irq19: uhci1 3 0 >> irq23: atapci0 151 0 >> irq46: amr0 41344088 2 >> irq64: em0 1513106157 73 >> irq0: clk 2055605782 99 >> Total 7790932823 379 >> >> This one just transfered over 8gigs of data in 77seconds with around >> 1000 simultaneous tcp connections under a load of 35. Both seem OK. >> vmstat -i >> interrupt total rate >> irq4: sio0 315 0 >> irq13: npx0 1 0 >> irq14: ata0 47 0 >> irq16: uhci0 2894669 2 >> irq18: uhci2 977413 0 >> irq23: ehci0 3 0 >> irq46: amr0 883138 0 >> irq64: em0 2890414 2 >> cpu0: timer 2763566717 1999 >> cpu3: timer 2763797300 1999 >> cpu1: timer 2763551479 1999 >> cpu2: timer 2763797870 1999 >> Total 11062359366 8004 >> >> Mike >> >> > > Looks like at least some of your interrupts are being aliased to > irq16, which just happens to be USB(uhci) in this case. Note that the > rate is > the same between irq64 and irq16, and the totals are pretty close. If > you don't need USB, I'd suggest turning it off. > > Scott Most of my Dell servers occasionally use the USB ports to serial out via tip using a usb2serial cable with the uplcom driver and then into another servers real serial port (sio) so its not really an option to disable USB. How much do you think it affects performance if the USB device is actually rarely used. I also have a 6-stable machine and noticed that the vmstat -i output lists the em and usb together, but em0 isn't used at all, em2 and em3 are the active ones, it doesn't seem reasonable that my usb serial usage would be that high for irq16 or could it be that em2 and em3 and also going through irq16 vmstat -i interrupt total rate irq4: sio0 228 0 irq14: ata0 47 0 irq16: em0 uhci0 917039 11 irq18: uhci2 54823 0 irq23: ehci0 3 0 irq46: amr0 45998 0 irq64: em2 898628 11 lapic0: timer 159140889 1999 Total 161057655 2024 Mike From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 04:52:16 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68BEA16A41F; Thu, 24 Nov 2005 04:52:16 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id C32E243D64; Thu, 24 Nov 2005 04:52:10 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jAO4q841041176; Wed, 23 Nov 2005 21:52:08 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <438546F8.5010601@samsco.org> Date: Wed, 23 Nov 2005 21:52:08 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Vince References: <20051123030304.GA84202@xor.obsecurity.org> <20051123084653.GA90927@xor.obsecurity.org> <43851A08.5080802@roq.com> <43851B69.5090701@samsco.org> <43853FF3.2050103@roq.com> In-Reply-To: <43853FF3.2050103@roq.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: Kris Kennaway , current@freebsd.org, net@freebsd.org Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 04:52:16 -0000 Michael Vince wrote: > Scott Long wrote: > >> Michael Vince wrote: >> >>> Kris Kennaway wrote: >>> >>>> On Tue, Nov 22, 2005 at 08:54:49PM -0800, John Polstra wrote: >>>> >>>> >>>>> On 23-Nov-2005 Kris Kennaway wrote: >>>>> >>>>> >>>>>> I am seeing the em driver undergoing an interrupt storm whenever the >>>>>> amr driver receives interrupts. In this case I was running newfs on >>>>>> the amr array and em0 was not in use: >>>>>> >>>>>> 28 root 1 -68 -187 0K 8K CPU1 1 0:32 53.98% >>>>>> irq16: em0 >>>>>> 36 root 1 -64 -183 0K 8K RUN 1 0:37 27.75% >>>>>> irq24: amr0 >>>>>> >>>>>> # vmstat -i >>>>>> interrupt total rate >>>>>> irq1: atkbd0 2 0 >>>>>> irq4: sio0 199 1 >>>>>> irq6: fdc0 32 0 >>>>>> irq13: npx0 1 0 >>>>>> irq14: ata0 47 0 >>>>>> irq15: ata1 931 5 >>>>>> irq16: em0 6321801 37187 >>>>>> irq24: amr0 28023 164 >>>>>> cpu0: timer 337533 1985 >>>>>> cpu1: timer 337285 1984 >>>>>> Total 7025854 41328 >>>>>> >>>>>> When newfs finished (i.e. amr was idle), em0 stopped storming. >>>>>> >>>>>> MPTable: >>>>>> >>>>> >>>>> >>>>> >>>>> This is the dreaded interrupt aliasing problem that several of us have >>>>> experienced with this chipset. High-numbered interrupts alias down to >>>>> interrupts in the range 16..19 (or maybe 16..23), a multiple of 8 less >>>>> than the original interupt. >>>>> >>>>> Nobody knows what causes it, and nobody knows how to fix it. >>>>> >>>> >>>> >>>> >>>> >>>> This would be good to document somewhere so that people don't either >>>> accidentally buy this hardware, or know what to expect when they run >>>> it. >>>> >>>> Kris >>>> >>>> >>> This is Intels latest server chipset designs and Dell are putting >>> that chipset in all their servers. >>> Luckily I haven't not seen the problem on any of my Dell servers (as >>> long as I am looking at this right). >>> >>> This server has been running for a long time. >>> vmstat -i >>> interrupt total rate >>> irq1: atkbd0 6 0 >>> irq4: sio0 23433 0 >>> irq6: fdc0 10 0 >>> irq8: rtc 2631238611 128 >>> irq13: npx0 1 0 >>> irq14: ata0 99 0 >>> irq16: uhci0 1507608958 73 >>> irq18: uhci2 42005524 2 >>> irq19: uhci1 3 0 >>> irq23: atapci0 151 0 >>> irq46: amr0 41344088 2 >>> irq64: em0 1513106157 73 >>> irq0: clk 2055605782 99 >>> Total 7790932823 379 >>> >>> This one just transfered over 8gigs of data in 77seconds with around >>> 1000 simultaneous tcp connections under a load of 35. Both seem OK. >>> vmstat -i >>> interrupt total rate >>> irq4: sio0 315 0 >>> irq13: npx0 1 0 >>> irq14: ata0 47 0 >>> irq16: uhci0 2894669 2 >>> irq18: uhci2 977413 0 >>> irq23: ehci0 3 0 >>> irq46: amr0 883138 0 >>> irq64: em0 2890414 2 >>> cpu0: timer 2763566717 1999 >>> cpu3: timer 2763797300 1999 >>> cpu1: timer 2763551479 1999 >>> cpu2: timer 2763797870 1999 >>> Total 11062359366 8004 >>> >>> Mike >>> >>> >> >> Looks like at least some of your interrupts are being aliased to >> irq16, which just happens to be USB(uhci) in this case. Note that the >> rate is >> the same between irq64 and irq16, and the totals are pretty close. If >> you don't need USB, I'd suggest turning it off. >> >> Scott > > > Most of my Dell servers occasionally use the USB ports to serial out via > tip using a usb2serial cable with the uplcom driver and then into > another servers real serial port (sio) so its not really an option to > disable USB. > > How much do you think it affects performance if the USB device is > actually rarely used. > > I also have a 6-stable machine and noticed that the vmstat -i output > lists the em and usb together, but em0 isn't used at all, em2 and em3 > are the active ones, it doesn't seem reasonable that my usb serial usage > would be that high for irq16 or could it be that em2 and em3 and also > going through irq16 > > vmstat -i > interrupt total rate > irq4: sio0 228 0 > irq14: ata0 47 0 > irq16: em0 uhci0 917039 11 > irq18: uhci2 54823 0 > irq23: ehci0 3 0 > irq46: amr0 45998 0 > irq64: em2 898628 11 > lapic0: timer 159140889 1999 > Total 161057655 2024 > > Mike > You're seeing the same aliasing. Here's exactly what happens: irq64 generates an interrupt and the APIC routes it to the CPU. FreeBSD services the interrupt, masks irq64 in the APIC, and schedules the interrupt thread for em2. When that ithread runs, the driver will take action to turn off the interrupt at the card, and then irq64 will be unmasked when the ithread completes. PCI interrupts are level driven, so they stay active until the driver tells the hardware to turn them off. However, as soon as the interrupt get masked, the APIC re-routes the signal to irq16. Since irq16 is an interrupt that freebsd cares about, it's enabled, so FreeBSD gets interrupted again. It then masks irq16 and schedules the em0/uhci0 ithread. Servicing irq16 doesn't take a whole lot of time, but running the ithread for it does. The uhci driver has to grab the Giant lock, so things like the bufdaemon get locked out while it runs. The em0 driver also has to grab a lock, but according to you that interface isnt' doing any work so it's likely to not be a big deal. But even so, these lock operations consume thousands of CPU cycles, plus the drivers have to read status either on the card or in memory, and that will also take thousands of cycles, maybe more (especially for UHCI). Add that up, and the CPU is spending a lot of time doing useless work. On a lightly loaded system you won't notice a difference, but if you're trying to do something like push lots of packets through, it quickly becomes noticable. Masking the interrupt in the APIC is vital so that the PCI interrupt can be silenced while the ithread gets scheduled to run. We can't EOI the APIC until it's silenced or else we'll get immediately re-interrupted, and if we don't EOI then we can't get any other interrupts. This scheme works fairly well for typical PC hardware, and these Intel chipsets seem to be the exception, albeit a popular one. One solution that is being worked on is to allow drivers to test and clear the hardware interrupt registers directly in the low-level interrupt handler, before their ithread runs. That'll eliminate the need to mask the APIC. This probably won't work for all drivers, but it should work for drivers like if_em. I've tried doing tricks like deferring the EOI and the masking, but the OS quickly looses its mind because it startsmissing clock interrupts. Scott From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 05:17:29 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE50B16A41F; Thu, 24 Nov 2005 05:17:29 +0000 (GMT) (envelope-from julian@elischer.org) Received: from delight.idiom.com (outbound.idiom.com [216.240.47.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BDBE43D55; Thu, 24 Nov 2005 05:17:29 +0000 (GMT) (envelope-from julian@elischer.org) Received: from idiom.com (idiom.com [216.240.32.1]) by delight.idiom.com (Postfix) with ESMTP id 25D05226FD4; Wed, 23 Nov 2005 21:17:29 -0800 (PST) Received: from [192.168.2.5] (home.elischer.org [216.240.48.38]) by idiom.com (8.12.11/8.12.11) with ESMTP id jAO5HR66038288; Wed, 23 Nov 2005 21:17:27 -0800 (PST) (envelope-from julian@elischer.org) Message-ID: <43854CE6.6030200@elischer.org> Date: Wed, 23 Nov 2005 21:17:26 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Vince References: <20051123030304.GA84202@xor.obsecurity.org> <20051123084653.GA90927@xor.obsecurity.org> <43851A08.5080802@roq.com> In-Reply-To: <43851A08.5080802@roq.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: John Polstra , net@freebsd.org, current@freebsd.org, Kris Kennaway Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 05:17:30 -0000 Michael Vince wrote: > Kris Kennaway wrote: > >> >> > This is Intels latest server chipset designs and Dell are putting that > chipset in all their servers. > Luckily I haven't not seen the problem on any of my Dell servers (as > long as I am looking at this right). > I just tried intel's latest em driver (3.2.18) with 6 interfaces on a 4.10 system on a dell 2850 server. (E7525 chipset I think) The result was the system hanging (couldn't do anything other than enter the debugger). backtraces showed tight loops in the em interrupt routines. Not sure if it's related yet. From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 05:24:35 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AAA1816A42B for ; Thu, 24 Nov 2005 05:24:35 +0000 (GMT) (envelope-from stb@lassitu.de) Received: from schlepper.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FA2C43D62 for ; Thu, 24 Nov 2005 05:24:31 +0000 (GMT) (envelope-from stb@lassitu.de) Received: from [127.0.0.1] (schlepper [212.12.50.230]) by schlepper.zs64.net (8.13.3/8.12.9) with ESMTP id jAO5OTGZ062815; Thu, 24 Nov 2005 06:24:29 +0100 (CET) (envelope-from stb@lassitu.de) In-Reply-To: <4384F807.6050105@samsco.org> References: <002801c5f081$f01ff200$642a15ac@smiley> <4384F807.6050105@samsco.org> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <14BE0E5B-F596-4CB2-8048-07FC275C089F@lassitu.de> Content-Transfer-Encoding: 7bit From: Stefan Bethke Date: Thu, 24 Nov 2005 06:24:17 +0100 To: Scott Long X-Mailer: Apple Mail (2.746.2) Cc: freebsd-current@freebsd.org Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 05:24:35 -0000 Am 24.11.2005 um 00:15 schrieb Scott Long: > I've directly observed it on 7501WV2 and 7520BD2 boards. I don't > know if it's a problem that will affect other board configurations > or cousin chipsets like the 7505 and 7525. We've got a Tyan i7501 Pro that we have had stability issues with since the beginning. Is it thinkable that the interrupt masking could lead to a hard lock (no break to debugger possible)? I can trigger the issue by copying about 10 GB from one disk to another. Either to a disk connected through a Promise TX4 150 or a 3ware 8004 (twe). I see this with 5-stable as well as 6-stable, with GENERIC or custom kernels. Thanks, Stefan Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-STABLE #5: Thu Nov 10 23:36:19 CET 2005 root@majestix.tallence.de:/data/00/build/obj/data/00/build/src/ sys/MAJESTIX Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2799.21-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf25 Stepping = 5 Features=0xbfebfbff real memory = 2147483648 (2048 MB) avail memory = 2095292416 (1998 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard ioapic3 irqs 72-95 on motherboard ioapic4 irqs 96-119 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 2.0 on pci0 pci5: on pcib1 pci5: at device 28.0 (no driver attached) pcib2: at device 29.0 on pci5 pci7: on pcib2 em0: port 0xe880-0xe8bf mem 0xfe9c0000-0xfe9dffff irq 48 at device 1.0 on pci7 em0: Ethernet address: 00:e0:81:28:97:ea em0: Speed:N/A Duplex:N/A em1: port 0xec00-0xec3f mem 0xfe9e0000-0xfe9fffff irq 49 at device 1.1 on pci7 em1: Ethernet address: 00:e0:81:28:97:eb em1: Speed:N/A Duplex:N/A pci5: at device 30.0 (no driver attached) pcib3: at device 31.0 on pci5 pci6: on pcib3 pcib4: at device 3.0 on pci0 pci2: on pcib4 pci2: at device 28.0 (no driver attached) pcib5: at device 29.0 on pci2 pci4: on pcib5 twe0: <3ware Storage Controller. Driver version 1.50.01.002> port 0xdc00-0xdc0f mem 0xfd800000-0xfdffffff irq 96 at device 3.0 on pci4 twe0: 8 ports, Firmware FE8S 1.05.00.068, BIOS BE7X 1.08.00.048 pci2: at device 30.0 (no driver attached) pcib6: at device 31.0 on pci2 pci3: on pcib6 pcib7: at device 30.0 on pci0 pci1: on pcib7 fxp0: port 0xb080-0xb0bf mem 0xfd380000-0xfd39ffff,0xfd3fd000-0xfd3fdfff irq 19 at device 1.0 on pci1 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:e0:81:28:97:d8 pci1: at device 2.0 (no driver attached) atapci0: port 0xb400-0xb47f, 0xb480-0xb48f,0xbc00-0xbc3f mem 0xfd3a0000-0xfd3bffff, 0xfd3fe000-0xfd3fefff irq 18 at device 3.0 on pci1 atapci0: failed: rid 0x20 is memory, requested 4 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 ata4: channel #2 on atapci0 ata5: channel #3 on atapci0 isab0: at device 31.0 on pci0 isa0: on isab0 atapci1: port 0xffa0-0xffaf, 0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci1 ata1: channel #1 on atapci1 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console npx0: on motherboard npx0: INT 16 interface orm0: at iomem 0xd0000-0xd17ff,0xce800-0xcffff, 0xcd000-0xcdfff,0xcb800-0xccfff,0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 10.000 msec acd0: DVDROM at ata0-master PIO4 ad8: 239372MB [486344/16/63] at ata4-master SATA150 ad10: 239372MB [486344/16/63] at ata5- master SATA150 twed0: on twe0 twed0: 718114MB (1470698112 sectors) GEOM_LABEL: Label for provider twed0s3a is ufs/tallence. GEOM_LABEL: Label for provider twed0s3d is ufs/install. GEOM_LABEL: Label for provider twed0s3e is ufs/home. GEOM_LABEL: Label for provider twed0s3f is ufs/devhome. GEOM_LABEL: Label for provider twed0s3g is ufs/scratch. SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/twed0s1a WARNING: / was not properly dismounted GEOM_LABEL: Label for provider twed0s3a is ufs/tallence. GEOM_LABEL: Label for provider twed0s3d is ufs/install. GEOM_LABEL: Label for provider twed0s3e is ufs/home. GEOM_LABEL: Label for provider twed0s3f is ufs/devhome. GEOM_LABEL: Label for provider twed0s3g is ufs/scratch. -- Stefan Bethke Fon +49 170 346 0140 From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 05:32:00 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AEDA16A41F; Thu, 24 Nov 2005 05:32:00 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83C7543D4C; Thu, 24 Nov 2005 05:31:58 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.13.4/8.13.4) with ESMTP id jAO5VOr7051047; Wed, 23 Nov 2005 21:31:24 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.13.4/8.13.4/Submit) id jAO5VOEm051046; Wed, 23 Nov 2005 21:31:24 -0800 (PST) Date: Wed, 23 Nov 2005 21:31:24 -0800 (PST) From: Matthew Dillon Message-Id: <200511240531.jAO5VOEm051046@apollo.backplane.com> To: Scott Long References: <20051123030304.GA84202@xor.obsecurity.org> <20051123084653.GA90927@xor.obsecurity.org> <43851A08.5080802@roq.com> <43851B69.5090701@samsco.org> <43853FF3.2050103@roq.com> <438546F8.5010601@samsco.org> Cc: Michael Vince , net@freebsd.org, current@freebsd.org, Kris Kennaway Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 05:32:00 -0000 :You're seeing the same aliasing. Here's exactly what happens: :irq64 generates an interrupt and the APIC routes it to the CPU. :FreeBSD services the interrupt, masks irq64 in the APIC, and schedules :the interrupt thread for em2. When that ithread runs, the driver :will take action to turn off the interrupt at the card, and then :irq64 will be unmasked when the ithread completes. PCI interrupts are :level driven, so they stay active until the driver tells the hardware to :turn them off. However, as soon as the interrupt get masked, the APIC :re-routes the signal to irq16. Since irq16 is an interrupt that freebsd :cares about, it's enabled, so FreeBSD gets interrupted again. It then :masks irq16 and schedules the em0/uhci0 ithread. I'm a little confused as to what 'irq16' really means in this context. Are we talking about pin 16 on the IOAPIC (i.e. the 'irq16' cannot be distinguished from an interrupt on pin 16), or is it generating an actual BASE+16 vector to the LAPIC whenever some other pin is masked, or is it generating a fixed vector? It should be possible to work around the problem by using the trick that Linux uses, which is to 'mask' the IOAPIC interrupt by programming the pin from level to edge triggered (and then back to level triggered when the interrupt thread is finished with it), instead of masking the pin. This trick can result in a double interrupt, but it will stop the continuous interrupts. -Matt Matthew Dillon From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 06:01:59 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AECF616A41F; Thu, 24 Nov 2005 06:01:59 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01A9743D5D; Thu, 24 Nov 2005 06:01:46 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 54C6C1A3C2C; Wed, 23 Nov 2005 22:01:45 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 401E7515B2; Thu, 24 Nov 2005 01:01:44 -0500 (EST) Date: Thu, 24 Nov 2005 01:01:44 -0500 From: Kris Kennaway To: David Xu Message-ID: <20051124060143.GA15395@xor.obsecurity.org> References: <20051123201837.GA4822@xor.obsecurity.org> <438500BE.3020507@freebsd.org> <20051124000824.GA11032@xor.obsecurity.org> <43850AB7.4000109@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9jxsPFA5p3P2qPhR" Content-Disposition: inline In-Reply-To: <43850AB7.4000109@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: current@FreeBSD.org, Kris Kennaway Subject: Re: 4BSD process starvation during I/O X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 06:01:59 -0000 --9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 24, 2005 at 08:35:03AM +0800, David Xu wrote: > Kris Kennaway wrote: >=20 > >On Thu, Nov 24, 2005 at 07:52:30AM +0800, David Xu wrote: > >=20 > > > >>Kris Kennaway wrote: > >> > >> =20 > >> > >>>Perhaps this can be tweaked. > >>> > >>>Kris > >>> > >>>P.S. Please, no responses about how maybe someone could write a new > >>>scheduler that doesn't have this property. > >>> > >>> > >>> > >>> > >>> =20 > >>> > >>Can you try it again with FULL_PREEMPTION is turned on ? > >> =20 > >> > > > >Didn't really make a difference: > > > >=20 > > > This might only can be fixed when msleep no longer explicitly fiddles > thread priority, let scheduler fully control it. ULE doesn't seem to suffer from the "variance" problem nearly as badly on the simultaneous dd writing test I detailed earlier: ULE 268435456 bytes transferred in 6.738002 secs (39839028 bytes/sec) 268435456 bytes transferred in 6.755917 secs (39733385 bytes/sec) 268435456 bytes transferred in 6.828591 secs (39310518 bytes/sec) 268435456 bytes transferred in 7.173220 secs (37421891 bytes/sec) 268435456 bytes transferred in 7.359424 secs (36475064 bytes/sec) 268435456 bytes transferred in 7.452125 secs (36021330 bytes/sec) 268435456 bytes transferred in 7.657969 secs (35053087 bytes/sec) 268435456 bytes transferred in 7.848142 secs (34203695 bytes/sec) 268435456 bytes transferred in 8.061658 secs (33297798 bytes/sec) 268435456 bytes transferred in 8.159963 secs (32896652 bytes/sec) 268435456 bytes transferred in 8.176940 secs (32828351 bytes/sec) 268435456 bytes transferred in 8.184902 secs (32796416 bytes/sec) 4BSD 268435456 bytes transferred in 1.860367 secs (144291681 bytes/sec) 268435456 bytes transferred in 1.885677 secs (142354961 bytes/sec) 268435456 bytes transferred in 1.983243 secs (135351757 bytes/sec) 268435456 bytes transferred in 3.409261 secs (78737139 bytes/sec) 268435456 bytes transferred in 3.762066 secs (71353204 bytes/sec) 268435456 bytes transferred in 3.910402 secs (68646510 bytes/sec) 268435456 bytes transferred in 5.086984 secs (52769079 bytes/sec) 268435456 bytes transferred in 5.566311 secs (48225018 bytes/sec) 268435456 bytes transferred in 5.816347 secs (46151897 bytes/sec) 268435456 bytes transferred in 6.818567 secs (39368309 bytes/sec) 268435456 bytes transferred in 7.375191 secs (36397085 bytes/sec) 268435456 bytes transferred in 7.568077 secs (35469440 bytes/sec) Performance is lower on ULE though. Kris --9jxsPFA5p3P2qPhR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhVdHWry0BWjoQKURAm96AJ9J2uJCgnven7nCUyCWYVQIq7HljQCg2BVf GAVQcLK0aZvgD0185AiN5G8= =sYqT -----END PGP SIGNATURE----- --9jxsPFA5p3P2qPhR-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 06:26:26 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D11116A41F for ; Thu, 24 Nov 2005 06:26:26 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8AAC43D53 for ; Thu, 24 Nov 2005 06:26:25 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id C39A91A3C1A; Wed, 23 Nov 2005 22:26:25 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 2D1B3515B2; Thu, 24 Nov 2005 01:26:25 -0500 (EST) Date: Thu, 24 Nov 2005 01:26:25 -0500 From: Kris Kennaway To: Stefan Bethke Message-ID: <20051124062624.GA15944@xor.obsecurity.org> References: <002801c5f081$f01ff200$642a15ac@smiley> <4384F807.6050105@samsco.org> <14BE0E5B-F596-4CB2-8048-07FC275C089F@lassitu.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Nq2Wo0NMKNjxTN9z" Content-Disposition: inline In-Reply-To: <14BE0E5B-F596-4CB2-8048-07FC275C089F@lassitu.de> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 06:26:26 -0000 --Nq2Wo0NMKNjxTN9z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 24, 2005 at 06:24:17AM +0100, Stefan Bethke wrote: > Am 24.11.2005 um 00:15 schrieb Scott Long: >=20 > >I've directly observed it on 7501WV2 and 7520BD2 boards. I don't =20 > >know if it's a problem that will affect other board configurations =20 > >or cousin chipsets like the 7505 and 7525. >=20 > We've got a Tyan i7501 Pro that we have had stability issues with =20 > since the beginning. Is it thinkable that the interrupt masking =20 > could lead to a hard lock (no break to debugger possible)? Sounds like a different problem. Enable KDB_STOP_NMI in your kernel, which should let you break to DDB. Kris --Nq2Wo0NMKNjxTN9z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhV0QWry0BWjoQKURApE3AKCyHGk5MoV0PsDCdoYVQq5uLOlsnACfaTCz oXaEtrAYyOw0kDXXGCQ2EN8= =SQyC -----END PGP SIGNATURE----- --Nq2Wo0NMKNjxTN9z-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 06:27:12 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D794D16A41F for ; Thu, 24 Nov 2005 06:27:12 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 214B143D46 for ; Thu, 24 Nov 2005 06:27:12 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 0BD691A3C1A; Wed, 23 Nov 2005 22:27:12 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 75158519E7; Thu, 24 Nov 2005 01:27:11 -0500 (EST) Date: Thu, 24 Nov 2005 01:27:11 -0500 From: Kris Kennaway To: Darren Pilgrim Message-ID: <20051124062711.GA15961@xor.obsecurity.org> References: <43842D41.1050401@samsco.org> <002801c5f081$f01ff200$642a15ac@smiley> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mP3DRpeJDSE+ciuQ" Content-Disposition: inline In-Reply-To: <002801c5f081$f01ff200$642a15ac@smiley> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org, 'Kris Kennaway' Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 06:27:13 -0000 --mP3DRpeJDSE+ciuQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Nov 23, 2005 at 03:02:05PM -0800, Darren Pilgrim wrote: > Until this gets "fixed" in FreeBSD, what should those of us who are > effectively stuck with this hardware do to avoid the problem? Does the > problem exist in RELENG_4? Yes, on the same machine I first mentioned. Kris --mP3DRpeJDSE+ciuQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhV0/Wry0BWjoQKURAt4KAJ4zpYsWNW72WMIzjYOwu60RoKJyfACgsuWS ERRlxQOPs2iwLE4xFNwXvu8= =FSlf -----END PGP SIGNATURE----- --mP3DRpeJDSE+ciuQ-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 06:28:36 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 1558016A421; Thu, 24 Nov 2005 06:28:36 +0000 (GMT) In-Reply-To: <20051123161550.GE1010@obiwan.tataz.chchile.org> from Jeremie Le Hen at "Nov 23, 2005 05:15:50 pm" To: jeremie@le-hen.org (Jeremie Le Hen) Date: Thu, 24 Nov 2005 06:28:36 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20051124062836.1558016A421@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Cc: freebsd-current@freebsd.org Subject: Re: Lasted NDIS wrapper for D-Link DWL-520+ on RELENG_6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2005 06:28:36 -0000 Ok, there's something I just have to know: what the hell did you mean in the Subject: line when you said "Lasted?" > Hi, > > I'm trying to use my PCI Wireless card with NDISulator from Bill Paul. > I have tried to gather as much details as possible browsing through > recent wpaul's posts, I hope this will be enough. If misfortune made me > forget some details, I apologize for it and please, be indulgent and ask > them. Fortune has nothing to do with it. I think you picked the wrong driver. Your device's PCI vendor/device/subsystem ID says: > % none0@pci0:8:0: class=0x028000 card=0x3b041186 chip=0x9066104c rev=0x00 hdr=0x00 > % vendor = 'Texas Instruments (TI)' > % device = 'TNETW1130(ACX111) 802.11b/g Wireless Cardbus/PCI Adapter' > % class = network And you said you used the driver from: > I'm trying to use the lastest driver for this card provided by D-Link : > ftp://ftp.dlink.com/Wireless/dwl520+/Driver/dwl520+_drivers_307.zip Now, The first thing you should have done is to actually inspect the .INF file. Like the self-documenting ndisgen(8) script tells you, this is the file that actually contains the device ID information that the Windows Plug & Play Mangler will use when trying to match a device to a driver. The AIRPLUS.INF file says: [D-Link] %AIRPLUS.DeviceDesc1% = AIRPLUS.8400, PCI\VEN_104C&DEV_8400&SUBSYS_3B001186 %AIRPLUS.DeviceDesc2% = AIRPLUS.8400, PCI\VEN_104C&DEV_8400&SUBSYS_3B011186 Note that the PCI vendor ID (0x104c) matches your device, but the device ID (0x8400) does not (yours is 0x9066). In this case, the .INF file tells Windows to look for two possible devices. In reality, both devices use the same chip (vendor 0x104c, device 0x8400), but there are two board variants (one with 0x3b001186, the other 0x3b011186). The subsystem ID is really another vendor/device ID combination (0x1186 is D-Link's vendor ID, 0x3b00 and 0x3b01 are the device codes D-Link has assigned to their boards). Exactly what the differences are between the board revs is anyone's guess. Maybe they use the same Texas Instruments chip, but with slightly different RF circuitry. Maybe they're really the same electronically, but D-Link decided to give each production run their own ID code because they're funny that way. In any case, not only do the vendor ID and device ID not match your board, the subsystem IDs don't match yours either (0x3b041186). So this driver is not the one that goes with your card. > I have to say that I'm quite puzzled by the fact that there seem to be > multiple versions of the DWL-520+ card (at least two, one with an Atheros > chipset and one with a T.I. chipset) but strangely there is only one driver. > Even stranger, the Drivers/WinXP/ directory contains only one .SYS file. > I guess there must be some magic in it. Oh, _you're_ puzzled that there's multiple versions of the same card. Welcome to _my_ world, buster. I want you to explain, in precise detail, why you're trying to download a driver instead of using the one on the CD that came with the card. If the reason is that you lost the CD, then you're being appropriately punished for your carelessness. It's entirely possible that D-Link hasn't put the driver for your card on their FTP server yet. "So what do I do now?" I hear you ask. You look on other vendors' sites for other cards based on the on the Texas Instruments chipset and check their .INF files until you find one where the vendor and device ID matches yours. And you remind yourself to keep better track of your driver CDs in the future. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 07:14:08 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36F6316A41F for ; Thu, 24 Nov 2005 07:14:08 +0000 (GMT) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (p72-0-224-2.acedsl.com [72.0.224.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6662D43D58 for ; Thu, 24 Nov 2005 07:14:07 +0000 (GMT) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.13.4/8.13.4) with ESMTP id jAO7E6Bg022454; Thu, 24 Nov 2005 02:14:06 -0500 (EST) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.13.4/8.13.3/Submit) id jAO7E6A3022453; Thu, 24 Nov 2005 02:14:06 -0500 (EST) (envelope-from barney) Date: Thu, 24 Nov 2005 02:14:06 -0500 From: Barney Wolff Message-ID: <20051124071405.GA15743@pit.databus.com> References: <002801c5f081$f01ff200$642a15ac@smiley> <4384F807.6050105@samsco.org> <14BE0E5B-F596-4CB2-8048-07FC275C089F@lassitu.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <14BE0E5B-F596-4CB2-8048-07FC275C089F@lassitu.de> User-Agent: Mutt/1.5.11 Cc: freebsd-current@freebsd.org Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 07:14:08 -0000 I've observed the interrupt aliasing problem on an Asus A7M266-D with 2 Athlon 2200-MPs, so it's not confined to the Intel chipset. Here's the evidence (there is nothing connected to ehci0): lab:/home/barney $ vmstat -i interrupt total rate irq6: fdc0 10 0 irq13: npx0 1 0 irq14: ata0 12380884 6 irq15: ata1 58 0 irq16: ehci0 212494994 109 irq17: pcm0 4551325 2 irq18: ohci1 4275754 2 irq19: fxp0 ohci0+ 124765 0 irq20: em0 210064498 108 irq21: ahc0 4245565 2 irq22: ahc1 4261858 2 cpu0: timer 3877840775 1999 cpu1: timer 3877813525 1999 Total 8208054012 4233 lab:/home/barney $ uname -a FreeBSD lab.databus.com 7.0-CURRENT FreeBSD 7.0-CURRENT #1: Thu Oct 20 16:16:12 EDT 2005 toor@lab.databus.com:/usr/obj/usr/src/sys/LAB i386 It's been there for a long time - I just assumed it was a hw issue. -- Barney Wolff http://www.databus.com/bwresume.pdf I never met a computer I didn't like. From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 07:16:41 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D06A816A41F for ; Thu, 24 Nov 2005 07:16:41 +0000 (GMT) (envelope-from kbuild@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDAC543D46 for ; Thu, 24 Nov 2005 07:16:40 +0000 (GMT) (envelope-from kbuild@gmail.com) Received: by zproxy.gmail.com with SMTP id 16so374084nzp for ; Wed, 23 Nov 2005 23:16:40 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=dTZJgjzgXViXiPNGHkopxll46qBO/Z1BVQXawQqxJXEI4yF2HWfgDaMvETgfggI5OQinpMt6LlEzU9dtX937SjFUijcYyBb7HN1Mv6e9wH+qBsQX96tu7WAD0PWpaAFiiiLg+KR5BOXggywr5A8hg9n9scqlcsId8ayP455dJYk= Received: by 10.65.148.6 with SMTP id a6mr7009808qbo; Wed, 23 Nov 2005 23:16:40 -0800 (PST) Received: by 10.65.228.3 with HTTP; Wed, 23 Nov 2005 23:16:40 -0800 (PST) Message-ID: Date: Thu, 24 Nov 2005 15:16:40 +0800 From: Sun Le To: freebsd-current@freebsd.org In-Reply-To: MIME-Version: 1.0 References: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: meet up with a problem when doing the installation X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 07:16:41 -0000 Hi folks, I encountered a problem that need your help. The matter goes as follow: My box is Dell DIMENSION 1100 using Dell USB keyboard and mouse.When I installed the 6.0 release,I selected `boot with usb keyboard' option.Withthat,my usb keyboard worked well.Then I noticed that the usbd was been launched when the prompt appeared,and after that,When I set up my mouse,there is no option or protocols about the usb which can be selected.Moreover,of course,the mouse did not work.I hang on there. So,who can offer my some information that help me solve it? Many thanks in advance. Sandy -- Sun Le (Sandy) - Keep it simple,stupid and low-key From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 07:42:59 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A907C16A41F for ; Thu, 24 Nov 2005 07:42:59 +0000 (GMT) (envelope-from frank@exit.com) Received: from tinker.exit.com (tinker.exit.com [206.223.0.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1AB643D81 for ; Thu, 24 Nov 2005 07:42:45 +0000 (GMT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime [206.223.0.5]) by tinker.exit.com (8.13.4/8.13.4) with ESMTP id jAO7gX9F031757; Wed, 23 Nov 2005 23:42:33 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (localhost [127.0.0.1]) by realtime.exit.com (8.13.4/8.13.4) with ESMTP id jAO7gXn9045491; Wed, 23 Nov 2005 23:42:33 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.13.4/8.13.4/Submit) id jAO7gWM4045490; Wed, 23 Nov 2005 23:42:32 -0800 (PST) (envelope-from frank@exit.com) X-Authentication-Warning: realtime.exit.com: frank set sender to frank@exit.com using -f From: Frank Mayhar To: Barney Wolff In-Reply-To: <20051124071405.GA15743@pit.databus.com> References: <002801c5f081$f01ff200$642a15ac@smiley> <4384F807.6050105@samsco.org> <14BE0E5B-F596-4CB2-8048-07FC275C089F@lassitu.de> <20051124071405.GA15743@pit.databus.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Exit Consulting Date: Wed, 23 Nov 2005 23:42:32 -0800 Message-Id: <1132818152.54736.7.camel@realtime.exit.com> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port X-Virus-Scanned: ClamAV 0.87.1/1191/Wed Nov 23 15:50:25 2005 on tinker.exit.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: frank@exit.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2005 07:42:59 -0000 On Thu, 2005-11-24 at 02:14 -0500, Barney Wolff wrote: > I've observed the interrupt aliasing problem on an Asus A7M266-D > with 2 Athlon 2200-MPs, so it's not confined to the Intel chipset. > Here's the evidence (there is nothing connected to ehci0): This prompted me to take a look at my setup. Sure enough, same thing: realtime ~>vmstat -i interrupt total rate irq1: atkbd0 6218 0 irq3: sio1 2 0 irq4: sio0 245363 1 irq6: fdc0 3 0 irq12: psm0 379932 2 irq13: npx0 1 0 irq16: ohci2 1651974 9 irq17: pcm0 ehci0 35766600 198 irq18: nvidia0++ 15223737 84 irq19: xl0 ohci0+ 2407671 13 irq20: ahc0 1610309 8 irq21: em0 35275352 196 cpu0: timer 359360608 1998 cpu1: timer 359337445 1998 Total 811265215 4512 I haven't been using pcm0 and there's nothing on ohci2. This is a dual Athlon MP 1900+, AMD chipset (Tyan Tiger MPX board)... realtime ~>uname -a FreeBSD realtime.exit.com 6.0-STABLE FreeBSD 6.0-STABLE #0: Wed Nov 16 19:57:03 PST 2005 frank@jill.exit.com:/usr/obj/usr/src/sys/REALTIME i386 -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 08:02:39 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C27A116A41F for ; Thu, 24 Nov 2005 08:02:39 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from insomma.datacode.it (ip-152-166.sn2.eutelia.it [83.211.152.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0796243D45 for ; Thu, 24 Nov 2005 08:02:38 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from localhost (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with SMTP id 5F7282C90D for ; Thu, 24 Nov 2005 09:02:37 +0100 (CET) Received: from insomma.datacode.it (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with ESMTP id F09EF2C90A; Thu, 24 Nov 2005 09:02:35 +0100 (CET) Received: from massimo.datacode.it (massimo.datacode.it [192.168.1.13]) by insomma.datacode.it (Postfix) with ESMTP id ABB682C906; Thu, 24 Nov 2005 09:02:35 +0100 (CET) From: Massimo Lusetti To: Scott Long In-Reply-To: <4384F807.6050105@samsco.org> References: <002801c5f081$f01ff200$642a15ac@smiley> <4384F807.6050105@samsco.org> Content-Type: text/plain Organization: CEDOC - Modena Date: Thu, 24 Nov 2005 09:02:35 +0100 Message-Id: <1132819355.4307.1.camel@massimo.datacode.it> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: 'Kris Kennaway' , Darren Pilgrim , freebsd-current@freebsd.org Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 08:02:39 -0000 On Wed, 2005-11-23 at 16:15 -0700, Scott Long wrote: > What I've done is vacated the use of irq16 on my machines by disabling > things like usb and if_em. This isn't ideal, of course. The storming > doesn't usually cause a problem, but it can affect performance, > especially if USB is involved. I only do this when I'm testing > performance, otherwise I leave everything enabled and don't worry about > it. 4.x won't see this problem since it handles interrupts in the > more traditional way, but using 4.x also has many other tradeoffs that > may or may not be worthwhile. That's good to hear. Thanks for pointing it out Scott. -- Massimo.run(); From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 08:13:04 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0D3816A41F for ; Thu, 24 Nov 2005 08:13:04 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id D081343DA6 for ; Thu, 24 Nov 2005 08:11:42 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 071B01A3C1A; Thu, 24 Nov 2005 00:11:41 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id DCBEE515B3; Thu, 24 Nov 2005 03:11:39 -0500 (EST) Date: Thu, 24 Nov 2005 03:11:39 -0500 From: Kris Kennaway To: Massimo Lusetti Message-ID: <20051124081139.GA17568@xor.obsecurity.org> References: <002801c5f081$f01ff200$642a15ac@smiley> <4384F807.6050105@samsco.org> <1132819355.4307.1.camel@massimo.datacode.it> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FCuugMFkClbJLl1L" Content-Disposition: inline In-Reply-To: <1132819355.4307.1.camel@massimo.datacode.it> User-Agent: Mutt/1.4.2.1i Cc: 'Kris Kennaway' , Darren Pilgrim , freebsd-current@freebsd.org Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 08:13:05 -0000 --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 24, 2005 at 09:02:35AM +0100, Massimo Lusetti wrote: > On Wed, 2005-11-23 at 16:15 -0700, Scott Long wrote: >=20 > > What I've done is vacated the use of irq16 on my machines by disabling > > things like usb and if_em. This isn't ideal, of course. The storming > > doesn't usually cause a problem, but it can affect performance, > > especially if USB is involved. I only do this when I'm testing > > performance, otherwise I leave everything enabled and don't worry about > > it. 4.x won't see this problem since it handles interrupts in the > > more traditional way, but using 4.x also has many other tradeoffs that > > may or may not be worthwhile. >=20 > That's good to hear. Thanks for pointing it out Scott. As I mentioned in another reply, I do see a similar interrupt storm on the same hardware running 4.11. Kris --FCuugMFkClbJLl1L Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhXW7Wry0BWjoQKURAmo8AKDBo8tlxnDNAy8IO6dKWhzmyDmSggCfZJKe zLUVh2lhNE8mTJILt2trpJA= =xNBq -----END PGP SIGNATURE----- --FCuugMFkClbJLl1L-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 08:39:00 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DA4A16A41F for ; Thu, 24 Nov 2005 08:39:00 +0000 (GMT) (envelope-from akbeech@gmail.com) Received: from vfemail.net (miwi2dsl-a234.wi.tds.net [216.170.248.235]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01FCF43D55 for ; Thu, 24 Nov 2005 08:38:58 +0000 (GMT) (envelope-from akbeech@gmail.com) Received: (qmail 22630 invoked by uid 85); 24 Nov 2005 08:38:58 -0000 Received: from akbeech@gmail.com by mail.vfemail.net by uid 0 with qmail-scanner-1.16 (clamscan: 0.75.1. spamassassin: 2.63. Clear:. Processed in 2.019082 secs); 24 Nov 2005 08:38:58 -0000 Received: from unknown (HELO ?192.168.241.120?) (alaska@vfemail.net@24.237.206.237) by miwi2dsl-a234.wi.tds.net with RC4-MD5 encrypted SMTP; 24 Nov 2005 08:38:55 -0000 From: Beecher Rintoul Organization: NorthWind Communications To: freebsd-current@freebsd.org Date: Wed, 23 Nov 2005 23:38:28 -0900 User-Agent: KMail/1.8.3 References: <20051124062836.1558016A421@hub.freebsd.org> In-Reply-To: <20051124062836.1558016A421@hub.freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1138347.1Nv7pN153P"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200511232338.43455.akbeech@gmail.com> Cc: Bill Paul , Jeremie Le Hen Subject: Re: Lasted NDIS wrapper for D-Link DWL-520+ on RELENG_6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2005 08:39:00 -0000 --nextPart1138347.1Nv7pN153P Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 23 November 2005 09:28 pm, Bill Paul wrote: > Ok, there's something I just have to know: what the hell did you mean > in the Subject: line when you said "Lasted?" > > > Hi, > > > > I'm trying to use my PCI Wireless card with NDISulator from Bill Paul. > > I have tried to gather as much details as possible browsing through > > recent wpaul's posts, I hope this will be enough. If misfortune made me > > forget some details, I apologize for it and please, be indulgent and ask > > them. > > Fortune has nothing to do with it. > > I think you picked the wrong driver. > > Your device's PCI vendor/device/subsystem ID says: > > % none0@pci0:8:0: class=3D0x028000 card=3D0x3b041186 chip=3D0x9066104c = rev=3D0x00 > > hdr=3D0x00 % vendor =3D 'Texas Instruments (TI)' > > % device =3D 'TNETW1130(ACX111) 802.11b/g Wireless Cardbus/PCI > > Adapter' % class =3D network > > And you said you used the driver from: > > I'm trying to use the lastest driver for this card provided by D-Link : > > ftp://ftp.dlink.com/Wireless/dwl520+/Driver/dwl520+_drivers_307.zip > > Now, The first thing you should have done is to actually inspect the > .INF file. Like the self-documenting ndisgen(8) script tells you, this > is the file that actually contains the device ID information that the > Windows Plug & Play Mangler will use when trying to match a device > to a driver. The AIRPLUS.INF file says: > > [D-Link] > %AIRPLUS.DeviceDesc1% =3D AIRPLUS.8400, PCI\VEN_104C&DEV_8400&SUBSYS_3B00= 1186 > %AIRPLUS.DeviceDesc2% =3D AIRPLUS.8400, PCI\VEN_104C&DEV_8400&SUBSYS_3B01= 1186 > > Note that the PCI vendor ID (0x104c) matches your device, but the > device ID (0x8400) does not (yours is 0x9066). > > In this case, the .INF file tells Windows to look for two possible > devices. In reality, both devices use the same chip (vendor 0x104c, > device 0x8400), but there are two board variants (one with 0x3b001186, > the other 0x3b011186). The subsystem ID is really another vendor/device > ID combination (0x1186 is D-Link's vendor ID, 0x3b00 and 0x3b01 are > the device codes D-Link has assigned to their boards). Exactly what > the differences are between the board revs is anyone's guess. Maybe > they use the same Texas Instruments chip, but with slightly different > RF circuitry. Maybe they're really the same electronically, but D-Link > decided to give each production run their own ID code because they're > funny that way. > > In any case, not only do the vendor ID and device ID not match your board, > the subsystem IDs don't match yours either (0x3b041186). So this driver > is not the one that goes with your card. > > > I have to say that I'm quite puzzled by the fact that there seem to be > > multiple versions of the DWL-520+ card (at least two, one with an Ather= os > > chipset and one with a T.I. chipset) but strangely there is only one > > driver. Even stranger, the Drivers/WinXP/ directory contains only one > > .SYS file. I guess there must be some magic in it. > > Oh, _you're_ puzzled that there's multiple versions of the same card. > Welcome to _my_ world, buster. > > I want you to explain, in precise detail, why you're trying to download > a driver instead of using the one on the CD that came with the card. If > the reason is that you lost the CD, then you're being appropriately > punished for your carelessness. > > It's entirely possible that D-Link hasn't put the driver for your card > on their FTP server yet. > > "So what do I do now?" I hear you ask. > > You look on other vendors' sites for other cards based on the on > the Texas Instruments chipset and check their .INF files until you > find one where the vendor and device ID matches yours. And you remind > yourself to keep better track of your driver CDs in the future. > > -Bill I'm using the AG-530 with ndis and everything works correctly. I'll be happ= y=20 to send you the .inf and .sys files that I use if you want them. Beech =2D------------------------------------------------------------------------= =2D------------- Beech Rintoul - System Administrator - akbeech@gmail.com /"\ ASCII Ribbon Campaign | NorthWind Communications \ / - NO HTML/RTF in e-mail | 201 East 9th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \=20 =2D------------------------------------------------------------------------= =2D------------- --nextPart1138347.1Nv7pN153P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDhXwTVq19LUoGB+MRAu9mAJ9jCERvfhmQ0sMHWgw8MN0PJFWwygCgm9He 71eBdlBUFRxjD/CzL0YnE5c= =CdR4 -----END PGP SIGNATURE----- --nextPart1138347.1Nv7pN153P-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 09:33:05 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B86CF16A41F for ; Thu, 24 Nov 2005 09:33:05 +0000 (GMT) (envelope-from stb@lassitu.de) Received: from schlepper.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EE2543D46 for ; Thu, 24 Nov 2005 09:33:03 +0000 (GMT) (envelope-from stb@lassitu.de) Received: from [127.0.0.1] (schlepper [212.12.50.230]) by schlepper.zs64.net (8.13.3/8.12.9) with ESMTP id jAO9X2j8071997; Thu, 24 Nov 2005 10:33:02 +0100 (CET) (envelope-from stb@lassitu.de) In-Reply-To: <20051124062624.GA15944@xor.obsecurity.org> References: <002801c5f081$f01ff200$642a15ac@smiley> <4384F807.6050105@samsco.org> <14BE0E5B-F596-4CB2-8048-07FC275C089F@lassitu.de> <20051124062624.GA15944@xor.obsecurity.org> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <858BF11C-E2B4-404B-B502-26AD49F5C962@lassitu.de> Content-Transfer-Encoding: 7bit From: Stefan Bethke Date: Thu, 24 Nov 2005 10:28:59 +0100 To: Kris Kennaway X-Mailer: Apple Mail (2.746.2) Cc: freebsd-current@freebsd.org Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 09:33:05 -0000 Am 24.11.2005 um 07:26 schrieb Kris Kennaway: > On Thu, Nov 24, 2005 at 06:24:17AM +0100, Stefan Bethke wrote: >> Am 24.11.2005 um 00:15 schrieb Scott Long: >> >>> I've directly observed it on 7501WV2 and 7520BD2 boards. I don't >>> know if it's a problem that will affect other board configurations >>> or cousin chipsets like the 7505 and 7525. >> >> We've got a Tyan i7501 Pro that we have had stability issues with >> since the beginning. Is it thinkable that the interrupt masking >> could lead to a hard lock (no break to debugger possible)? > > Sounds like a different problem. Enable KDB_STOP_NMI in your kernel, > which should let you break to DDB. Unfortunatly, no luck: can't break into the debugger with the option compiled into the kernel and debug.kdb.stop_cpus_with_nmi=1 set in loader.conf either. Stefan -- Stefan Bethke Fon +49 170 346 0140 From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 09:36:18 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4774716A41F for ; Thu, 24 Nov 2005 09:36:18 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBD8843D4C for ; Thu, 24 Nov 2005 09:36:17 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id CDEBE1A3C1A; Thu, 24 Nov 2005 01:36:17 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id CAB1851593; Thu, 24 Nov 2005 04:36:16 -0500 (EST) Date: Thu, 24 Nov 2005 04:36:16 -0500 From: Kris Kennaway To: Stefan Bethke Message-ID: <20051124093616.GA18522@xor.obsecurity.org> References: <002801c5f081$f01ff200$642a15ac@smiley> <4384F807.6050105@samsco.org> <14BE0E5B-F596-4CB2-8048-07FC275C089F@lassitu.de> <20051124062624.GA15944@xor.obsecurity.org> <858BF11C-E2B4-404B-B502-26AD49F5C962@lassitu.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/04w6evG8XlLl3ft" Content-Disposition: inline In-Reply-To: <858BF11C-E2B4-404B-B502-26AD49F5C962@lassitu.de> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org, Kris Kennaway Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 09:36:18 -0000 --/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 24, 2005 at 10:28:59AM +0100, Stefan Bethke wrote: >=20 > Am 24.11.2005 um 07:26 schrieb Kris Kennaway: >=20 > >On Thu, Nov 24, 2005 at 06:24:17AM +0100, Stefan Bethke wrote: > >>Am 24.11.2005 um 00:15 schrieb Scott Long: > >> > >>>I've directly observed it on 7501WV2 and 7520BD2 boards. I don't > >>>know if it's a problem that will affect other board configurations > >>>or cousin chipsets like the 7505 and 7525. > >> > >>We've got a Tyan i7501 Pro that we have had stability issues with > >>since the beginning. Is it thinkable that the interrupt masking > >>could lead to a hard lock (no break to debugger possible)? > > > >Sounds like a different problem. Enable KDB_STOP_NMI in your kernel, > >which should let you break to DDB. >=20 > Unfortunatly, no luck: can't break into the debugger with the option =20 > compiled into the kernel and debug.kdb.stop_cpus_with_nmi=3D1 set in =20 > loader.conf either. I've never encountered this..is it possible this hardware is faulty? Kris --/04w6evG8XlLl3ft Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDhYmQWry0BWjoQKURAlt4AJ9YZ9tYhYfuIZ5yEdXlFk8TEltkoACcCR8h SCBNpQShcgyWS1U5D99WPUw= =kWWF -----END PGP SIGNATURE----- --/04w6evG8XlLl3ft-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 09:48:49 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8B1016A41F for ; Thu, 24 Nov 2005 09:48:49 +0000 (GMT) (envelope-from stb@lassitu.de) Received: from schlepper.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 852A543D66 for ; Thu, 24 Nov 2005 09:48:48 +0000 (GMT) (envelope-from stb@lassitu.de) Received: from [127.0.0.1] (schlepper [212.12.50.230]) by schlepper.zs64.net (8.13.3/8.12.9) with ESMTP id jAO9mlqS072511; Thu, 24 Nov 2005 10:48:47 +0100 (CET) (envelope-from stb@lassitu.de) In-Reply-To: <20051124093616.GA18522@xor.obsecurity.org> References: <002801c5f081$f01ff200$642a15ac@smiley> <4384F807.6050105@samsco.org> <14BE0E5B-F596-4CB2-8048-07FC275C089F@lassitu.de> <20051124062624.GA15944@xor.obsecurity.org> <858BF11C-E2B4-404B-B502-26AD49F5C962@lassitu.de> <20051124093616.GA18522@xor.obsecurity.org> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <0E77DBEA-B698-47D4-AEFC-AB78DB5EC255@lassitu.de> Content-Transfer-Encoding: 7bit From: Stefan Bethke Date: Thu, 24 Nov 2005 10:48:50 +0100 To: Kris Kennaway X-Mailer: Apple Mail (2.746.2) Cc: freebsd-current@freebsd.org Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 09:48:49 -0000 Am 24.11.2005 um 10:36 schrieb Kris Kennaway: > On Thu, Nov 24, 2005 at 10:28:59AM +0100, Stefan Bethke wrote: >> >> Am 24.11.2005 um 07:26 schrieb Kris Kennaway: >> >>> On Thu, Nov 24, 2005 at 06:24:17AM +0100, Stefan Bethke wrote: >>>> Am 24.11.2005 um 00:15 schrieb Scott Long: >>>> >>>>> I've directly observed it on 7501WV2 and 7520BD2 boards. I don't >>>>> know if it's a problem that will affect other board configurations >>>>> or cousin chipsets like the 7505 and 7525. >>>> >>>> We've got a Tyan i7501 Pro that we have had stability issues with >>>> since the beginning. Is it thinkable that the interrupt masking >>>> could lead to a hard lock (no break to debugger possible)? >>> >>> Sounds like a different problem. Enable KDB_STOP_NMI in your >>> kernel, >>> which should let you break to DDB. >> >> Unfortunatly, no luck: can't break into the debugger with the option >> compiled into the kernel and debug.kdb.stop_cpus_with_nmi=1 set in >> loader.conf either. > > I've never encountered this..is it possible this hardware is faulty? Quite possible, although we've swapped everything except for the CPUs. We've got a replacement mainboard we'll try next. Stefan -- Stefan Bethke Fon +49 170 346 0140 From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 10:50:12 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D010016A421 for ; Thu, 24 Nov 2005 10:50:12 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from insomma.datacode.it (ip-152-166.sn2.eutelia.it [83.211.152.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEB3943D53 for ; Thu, 24 Nov 2005 10:50:08 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from localhost (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with SMTP id 8006A2C90C for ; Thu, 24 Nov 2005 11:50:06 +0100 (CET) Received: from insomma.datacode.it (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with ESMTP id B69C82C90A; Thu, 24 Nov 2005 11:50:05 +0100 (CET) Received: from massimo.datacode.it (massimo.datacode.it [192.168.1.13]) by insomma.datacode.it (Postfix) with ESMTP id 6AB7B2C906; Thu, 24 Nov 2005 11:50:05 +0100 (CET) From: Massimo Lusetti To: Scott Long In-Reply-To: <438546F8.5010601@samsco.org> References: <20051123030304.GA84202@xor.obsecurity.org> <20051123084653.GA90927@xor.obsecurity.org> <43851A08.5080802@roq.com> <43851B69.5090701@samsco.org> <43853FF3.2050103@roq.com> <438546F8.5010601@samsco.org> Content-Type: text/plain Organization: CEDOC - Modena Date: Thu, 24 Nov 2005 11:50:05 +0100 Message-Id: <1132829405.4307.5.camel@massimo.datacode.it> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: Michael Vince , net@freebsd.org, current@freebsd.org, Kris Kennaway Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 10:50:12 -0000 On Wed, 2005-11-23 at 21:52 -0700, Scott Long wrote: [..] > and if we don't EOI then we can't get any other interrupts. This scheme > works fairly well for typical PC hardware, and these Intel chipsets seem > to be the exception, albeit a popular one. One solution that is being [..] Yep, the wide spread of this kind of hardware makes this a big issue, isn't it? Regards -- Massimo.run(); From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 11:24:29 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDA4B16A41F; Thu, 24 Nov 2005 11:24:29 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18B8743D49; Thu, 24 Nov 2005 11:24:28 +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 smtp5-g19.free.fr (Postfix) with ESMTP id 2ED2296AC; Thu, 24 Nov 2005 12:24:28 +0100 (CET) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 081F8405A; Thu, 24 Nov 2005 12:24:13 +0100 (CET) Date: Thu, 24 Nov 2005 12:24:13 +0100 From: Jeremie Le Hen To: Bill Paul Message-ID: <20051124112413.GA1006@obiwan.tataz.chchile.org> References: <20051123161550.GE1010@obiwan.tataz.chchile.org> <20051124062836.1558016A421@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051124062836.1558016A421@hub.freebsd.org> User-Agent: Mutt/1.5.11 Cc: freebsd-current@freebsd.org Subject: Re: Lasted NDIS wrapper for D-Link DWL-520+ on RELENG_6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2005 11:24:30 -0000 Hi Bill, Thank you for your cynical reply, my face is always showing a smile whenever I can read your words :-). > Ok, there's something I just have to know: what the hell did you mean > in the Subject: line when you said "Lasted?" Hmm well, as you have surely already understood, English is not my native tongue. My mind wished to write "Lastest" but my fingers typed "Lasted" and my eyes didn't notice it. > I think you picked the wrong driver. > > Your device's PCI vendor/device/subsystem ID says: > > > % none0@pci0:8:0: class=0x028000 card=0x3b041186 chip=0x9066104c rev=0x00 hdr=0x00 > > % vendor = 'Texas Instruments (TI)' > > % device = 'TNETW1130(ACX111) 802.11b/g Wireless Cardbus/PCI Adapter' > > % class = network > > And you said you used the driver from: > > > I'm trying to use the lastest driver for this card provided by D-Link : > > ftp://ftp.dlink.com/Wireless/dwl520+/Driver/dwl520+_drivers_307.zip > > Now, The first thing you should have done is to actually inspect the > .INF file. Like the self-documenting ndisgen(8) script tells you, this > is the file that actually contains the device ID information that the > Windows Plug & Play Mangler will use when trying to match a device > to a driver. The AIRPLUS.INF file says: > > [D-Link] > %AIRPLUS.DeviceDesc1% = AIRPLUS.8400, PCI\VEN_104C&DEV_8400&SUBSYS_3B001186 > %AIRPLUS.DeviceDesc2% = AIRPLUS.8400, PCI\VEN_104C&DEV_8400&SUBSYS_3B011186 > > Note that the PCI vendor ID (0x104c) matches your device, but the > device ID (0x8400) does not (yours is 0x9066). > > In this case, the .INF file tells Windows to look for two possible > devices. In reality, both devices use the same chip (vendor 0x104c, > device 0x8400), but there are two board variants (one with 0x3b001186, > the other 0x3b011186). The subsystem ID is really another vendor/device > ID combination (0x1186 is D-Link's vendor ID, 0x3b00 and 0x3b01 are > the device codes D-Link has assigned to their boards). Exactly what > the differences are between the board revs is anyone's guess. Maybe > they use the same Texas Instruments chip, but with slightly different > RF circuitry. Maybe they're really the same electronically, but D-Link > decided to give each production run their own ID code because they're > funny that way. > > In any case, not only do the vendor ID and device ID not match your board, > the subsystem IDs don't match yours either (0x3b041186). So this driver > is not the one that goes with your card. Ok thank you very much for this explanation, this is now very clear. I'm going to try other drivers, I think looking on Google for these vendor and device IDs will point out a relevant driver. At first glance it seems that NetGear WG-311 uses the same chip, I'm going to have a try to their driver. > > I have to say that I'm quite puzzled by the fact that there seem to be > > multiple versions of the DWL-520+ card (at least two, one with an Atheros > > chipset and one with a T.I. chipset) but strangely there is only one driver. > > Even stranger, the Drivers/WinXP/ directory contains only one .SYS file. > > I guess there must be some magic in it. > > Oh, _you're_ puzzled that there's multiple versions of the same card. > Welcome to _my_ world, buster. > > I want you to explain, in precise detail, why you're trying to download > a driver instead of using the one on the CD that came with the card. If > the reason is that you lost the CD, then you're being appropriately > punished for your carelessness. You read my mind. I hope God will forgive me before I have to leave the purgatory :). > It's entirely possible that D-Link hasn't put the driver for your card > on their FTP server yet. > > "So what do I do now?" I hear you ask. > > You look on other vendors' sites for other cards based on the on > the Texas Instruments chipset and check their .INF files until you > find one where the vendor and device ID matches yours. And you remind > yourself to keep better track of your driver CDs in the future. Noted. Excuse me for wasting your time because I lost the CD. I will follow up this thread when I will have got my card running with NDIS, for the records. Best regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 11:26:02 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85E3716A41F for ; Thu, 24 Nov 2005 11:26:02 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from smtp2-g19.free.fr (smtp2-g19.free.fr [212.27.42.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1ACF43D90 for ; Thu, 24 Nov 2005 11:25:52 +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 smtp2-g19.free.fr (Postfix) with ESMTP id 3641D522E8; Thu, 24 Nov 2005 12:25:51 +0100 (CET) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 2BAFE405A; Thu, 24 Nov 2005 12:25:37 +0100 (CET) Date: Thu, 24 Nov 2005 12:25:37 +0100 From: Jeremie Le Hen To: Beecher Rintoul Message-ID: <20051124112537.GB1006@obiwan.tataz.chchile.org> References: <20051124062836.1558016A421@hub.freebsd.org> <200511232338.43455.akbeech@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200511232338.43455.akbeech@gmail.com> User-Agent: Mutt/1.5.11 Cc: freebsd-current@freebsd.org Subject: Re: Lasted NDIS wrapper for D-Link DWL-520+ on RELENG_6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2005 11:26:02 -0000 Hi Beecher, On Wed, Nov 23, 2005 at 11:38:28PM -0900, Beecher Rintoul wrote: > I'm using the AG-530 with ndis and everything works correctly. I'll be happy > to send you the .inf and .sys files that I use if you want them. Yes please, I would like to give a try to these drivers as well, please send them in private E-mail, or give me an URL when I can get them. Thank you. Best regards; -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 14:49:48 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4969716A41F for ; Thu, 24 Nov 2005 14:49:48 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90CDF43D66 for ; Thu, 24 Nov 2005 14:49:46 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so1395688wxc for ; Thu, 24 Nov 2005 06:49:45 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=KiEVs9GF/JviUKfBBcCPyWLouDMMWVYDD7K8+bf7XStOO1DHA4X/7bH5OoFi1lgUjdR+cDlTg1YpFVj0ykZdvIK+oUEPnKZZMIP65P1eXx3cS3pqUPP0IenuJOmmZGu+KGteLnvCxRYV1ZmydJ/iXWnSm6xcNmqKFAxBjTRcAgE= Received: by 10.70.108.5 with SMTP id g5mr6482435wxc; Thu, 24 Nov 2005 06:49:45 -0800 (PST) Received: by 10.70.105.13 with HTTP; Thu, 24 Nov 2005 06:49:45 -0800 (PST) Message-ID: <84dead720511240649n3d3fc9c6y9010e69e937e1dfe@mail.gmail.com> Date: Thu, 24 Nov 2005 20:19:45 +0530 From: Joseph Koshy To: "Wojciech A. Koszek" In-Reply-To: <20051121135401.GA94609@freebsd.czest.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051120172755.GA85641@freebsd.czest.pl> <84dead720511200943ua2cf8b8y49bff0dcf3e2fa63@mail.gmail.com> <20051120183037.GA85917@freebsd.czest.pl> <200511211011.29745.doconnor@gsoft.com.au> <20051121135401.GA94609@freebsd.czest.pl> Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Specifying alternative file for devd(8) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 14:49:48 -0000 wk> Sorry and thanks for the explanation. Updated patch: wk> http://freebsd.czest.pl/dunstan/FreeBSD/diff.2.devd I've committed this patch with a few changes: - getopt's args and the cases in the switch statement were ordered alphabetically. - the manual page was tweaked (since I was there) - the following change is unnecessary. "${name}_flags" is automatically used by rcNG. --- /usr/src/etc/rc.d/devd=09Fri Oct 28 18:55:38 2005 +++ src/etc/rc.d/devd=09Sun Nov 20 18:15:07 2005 @@ -13,6 +13,7 @@ name=3D"devd" rcvar=3D`set_rcvar` command=3D"/sbin/${name}" +command_args=3D"${devd_flags}" Also, 'devd_flags' is set by the invocation of load_rc_config further down, so this change is actually a no-op. Thank you for sending in the patch. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 16:51:28 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D800316A41F for ; Thu, 24 Nov 2005 16:51:28 +0000 (GMT) (envelope-from mayank@microsoft.com) Received: from mail-sin2.microsoft.com (mail-sin2.microsoft.com [207.46.50.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C50343D6E for ; Thu, 24 Nov 2005 16:51:27 +0000 (GMT) (envelope-from mayank@microsoft.com) Received: from APS-MSG-01.southpacific.corp.microsoft.com ([157.60.218.52]) by mail-sin2.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 25 Nov 2005 00:51:26 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 25 Nov 2005 00:51:26 +0800 Message-ID: <3A5384BC2FBA4C488865F2275A036BFF040B269C@APS-MSG-01.southpacific.corp.microsoft.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: What is the correct behaviour for local socket(AF_UNIX) in the following scenario? thread-index: AcXxFp58uFz/JQ5cRk61nDgcDjPArQAAKXyA From: "Mayank Kumar" To: X-OriginalArrivalTime: 24 Nov 2005 16:51:26.0938 (UTC) FILETIME=[4F729BA0:01C5F117] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: What is the correct behaviour for local socket(AF_UNIX) in the following scenario? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 16:51:29 -0000 =20 Hi All I am trying to understand the behavior of localsockets in the following scenario. =20 A process p1 writes a huge amoount of data to a AF_UNIX,DGRAM socket and exits. Now if there is no process p2 to read the data written by process p1 from the same localsocket, then this has resulted in a huge memory leak on a FreeBSD system. =20 I want to understand, if there is a mechanism in FreeBsd to take care of this leak or this is the expected behaviour and application writers should take care of this situation. Also what should be the behaviour on such a socket if shutdown or close is issued on such a socket. Any help on the behaviour on other unixes in the same scenario would also help a lot. =20 Thanks & Regards Mayank =20 From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 18:07:59 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F8D216A420 for ; Thu, 24 Nov 2005 18:07:59 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB98A43D68 for ; Thu, 24 Nov 2005 18:07:58 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so1437781wxc for ; Thu, 24 Nov 2005 10:07:56 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=MaFTZRqEoeH+5pFuWp3yFMpZTCYwEzP+E+B5lMDsexn/HkJ2ahKVVBT200b22n81CYeCgHNOxAare2SXjL6cILnXb1LQIVvD5uOfFHWJW6VhzbXPwYAOoz6tacm1sYp8CElCntKJ1p5XtuOyjjhhMVGVdVE2ogASdNc63kj+XWg= Received: by 10.70.108.5 with SMTP id g5mr6690763wxc; Thu, 24 Nov 2005 10:07:55 -0800 (PST) Received: by 10.70.105.13 with HTTP; Thu, 24 Nov 2005 10:07:55 -0800 (PST) Message-ID: <84dead720511241007g44770cabufbb1f51bd9927572@mail.gmail.com> Date: Thu, 24 Nov 2005 23:37:55 +0530 From: Joseph Koshy To: Mayank Kumar In-Reply-To: <3A5384BC2FBA4C488865F2275A036BFF040B269C@APS-MSG-01.southpacific.corp.microsoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <3A5384BC2FBA4C488865F2275A036BFF040B269C@APS-MSG-01.southpacific.corp.microsoft.com> Cc: freebsd-current@freebsd.org Subject: Re: What is the correct behaviour for local socket(AF_UNIX) in the following scenario? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 18:07:59 -0000 > Now if there is no process p2 to read the data written by > process p1 from the same localsocket, then this has resulted > in a huge memory leak on a FreeBSD system. How are you measuring the 'leak', and which version of FreeBSD are you using? -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 16:46:59 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1181216A41F for ; Thu, 24 Nov 2005 16:46:59 +0000 (GMT) (envelope-from mayank@microsoft.com) Received: from mail-sin2.microsoft.com (mail-sin2.microsoft.com [207.46.50.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CFBF43D98 for ; Thu, 24 Nov 2005 16:46:34 +0000 (GMT) (envelope-from mayank@microsoft.com) Received: from APS-MSG-01.southpacific.corp.microsoft.com ([157.60.218.52]) by mail-sin2.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 25 Nov 2005 00:46:30 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Fri, 25 Nov 2005 00:46:30 +0800 Message-ID: <3A5384BC2FBA4C488865F2275A036BFF040B269B@APS-MSG-01.southpacific.corp.microsoft.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: What is the correct behaviour for local socket(AF_UNIX) in the following scenario? thread-index: AcXxFp58uFz/JQ5cRk61nDgcDjPArQ== From: "Mayank Kumar" To: X-OriginalArrivalTime: 24 Nov 2005 16:46:30.0756 (UTC) FILETIME=[9EE8D240:01C5F116] X-Mailman-Approved-At: Thu, 24 Nov 2005 18:20:03 +0000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: What is the correct behaviour for local socket(AF_UNIX) in the following scenario? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 16:46:59 -0000 Hi All I am trying to understand the behavior of localsockets in the following scenario. =20 A process p1 writes a huge amoount of data to a AF_UNIX,DGRAM socket and exits. Now if there is no process p2 to read the data written by process p1 from the same localsocket, then this has resulted in a huge memory leak on a FreeBSD system. =20 I want to understand, if there is a mechanism in FreeBsd to take care of this leak or this is the expected behaviour and application writers should take care of this situation. Also what should be the behaviour on such a socket if shutdown or close is issued on such a socket. Any help on the behaviour on other unixes in the same scenario would also help a lot. =20 Thanks & Regards Mayank =20 From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 18:47:58 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDEFE16A41F; Thu, 24 Nov 2005 18:47:58 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB83643D53; Thu, 24 Nov 2005 18:47:57 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (ppp-71-139-30-140.dsl.snfc21.pacbell.net [71.139.30.140]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id jAOIlwZM032076 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 24 Nov 2005 10:48:00 -0800 Message-ID: <43860AD3.7090608@root.org> Date: Thu, 24 Nov 2005 10:47:47 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mathieu Prevot References: <4383C083.6010300@root.org> <4383D58C.5040004@samsco.org> <20051123024911.GA99513@polands.org> <20051123144850.GA1613@polands.org> <74C4FED8-AFD1-4375-A875-438827BECC57@club-internet.fr> In-Reply-To: <74C4FED8-AFD1-4375-A875-438827BECC57@club-internet.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: Doug Poland , acpi@freebsd.org, FreeBSD Current Subject: Re: Build just one module (was Re: [Fwd: cvs commit: src/sys/dev/acpica acpi_cmbat.c]) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2005 18:47:58 -0000 Mathieu Prevot wrote: > > Le 23 nov. 05 à 15:48, Doug Poland a écrit : > >> On Wed, Nov 23, 2005 at 11:49:20AM +0100, Mathieu Prevot wrote: >> >>> >>> Le 23 nov. 05 ? 03:49, Doug Poland a ?crit : >>> >>>>> Nate Lawson wrote: >>>>> >>>>>> Here is a patch that should fix the battery hangs on RELENG_6. It >>>>>> was tested to work fine, although I need testing from an affected >>>>>> user to verify it fixes the problem. It was committed to HEAD and >>>>>> will be MFCed if it fixes the problem. >>>>>> >>>> My Dell C600 is affected by this problem. I'm running 6.0-STABLE and >>>> would be glad to test the patch. Since I don't run patches often, if >>>> someone could point me to a doc on how to apply the patch, I'd >>>> appreciate it. >>> >>> You should think man 'subject', Unix for the impatient or google and >>> find things like: >>> >>> patch -i patchfile filetopatch >>> patch>> >> Thank you, that part is fairly obvious. What I'm unsure of is where in >> the source tree do I apply that patch from, and, must I to rebuild >> world, or just the affected part of sys/dev. > > > Try and see for the patch. 'patch -i patchfile filetopatch' works from > anywhere. > I don't think you need to rebuild world. I think you can just build > acpi module but I don't know how. > You may glance at /usr/src/Makefile* ... Look at the path in the patch start. If it's "sys/dev", then patch from your src dir. If it's "src/sys/dev", patch from above the src dir. If it's just "file.c", then you have to find file.c and patch from there (but few people generate diffs this way, it's bad form). For acpi, then just: cd /sys/modules/acpi/acpi && make && cp acpi.ko / Then at the loader prompt: load /acpi.ko You don't want to use "make install", otherwise you overwrite your known good acpi.ko -- Nate From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 19:20:11 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2977516A41F for ; Thu, 24 Nov 2005 19:20:11 +0000 (GMT) (envelope-from Danovitsch@vitsch.net) Received: from amsfep12-int.chello.nl (amsfep12-int.chello.nl [213.46.243.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id F12CD43D46 for ; Thu, 24 Nov 2005 19:20:07 +0000 (GMT) (envelope-from Danovitsch@vitsch.net) Received: from Vitsch.net ([80.56.187.161]) by amsfep12-int.chello.nl (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20051124192005.DPLN17934.amsfep12-int.chello.nl@Vitsch.net> for ; Thu, 24 Nov 2005 20:20:05 +0100 Received: from [192.168.87.6] (j56043.upc-j.chello.nl [24.132.56.43]) by Vitsch.net (8.12.3p2/8.11.3) with ESMTP id jAOJIMT8098368 for ; Thu, 24 Nov 2005 20:18:23 +0100 (CET) (envelope-from Danovitsch@vitsch.net) From: "Daan Vreeken [PA4DAN]" Organization: Vitsch Electronics To: freebsd-current@freebsd.org Date: Thu, 24 Nov 2005 20:19:58 +0100 User-Agent: KMail/1.8.2 References: <20051124062836.1558016A421@hub.freebsd.org> <200511232338.43455.akbeech@gmail.com> <20051124112537.GB1006@obiwan.tataz.chchile.org> In-Reply-To: <20051124112537.GB1006@obiwan.tataz.chchile.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511242019.58323.Danovitsch@vitsch.net> Subject: Re: Lasted NDIS wrapper for D-Link DWL-520+ on RELENG_6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2005 19:20:11 -0000 Hi Jeremie, On Thursday 24 November 2005 12:25, you wrote: > Hi Beecher, > > On Wed, Nov 23, 2005 at 11:38:28PM -0900, Beecher Rintoul wrote: > > I'm using the AG-530 with ndis and everything works correctly. I'll be > > happy to send you the .inf and .sys files that I use if you want them. > > Yes please, I would like to give a try to these drivers as well, please > send them in private E-mail, or give me an URL when I can get them. > > Thank you. > Best regards; A couple of weeks ago I helped a friend of mine to get her DWL-520+ to work with the ndis driver. If Beecher's driver don't work for you, feel free to email me and I will send you the files. grtz, Daan From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 19:42:35 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id E8CDB16A420; Thu, 24 Nov 2005 19:42:35 +0000 (GMT) In-Reply-To: <20051124112413.GA1006@obiwan.tataz.chchile.org> from Jeremie Le Hen at "Nov 24, 2005 12:24:13 pm" To: jeremie@le-hen.org (Jeremie Le Hen) Date: Thu, 24 Nov 2005 19:42:35 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20051124194235.E8CDB16A420@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Cc: freebsd-current@freebsd.org Subject: Re: Lasted NDIS wrapper for D-Link DWL-520+ on RELENG_6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2005 19:42:36 -0000 > > Now, The first thing you should have done is to actually inspect the > > .INF file. Like the self-documenting ndisgen(8) script tells you, this > > is the file that actually contains the device ID information that the > > Windows Plug & Play Mangler will use when trying to match a device > > to a driver. The AIRPLUS.INF file says: > > > > [D-Link] > > %AIRPLUS.DeviceDesc1% = AIRPLUS.8400, PCI\VEN_104C&DEV_8400&SUBSYS_3B001186 > > %AIRPLUS.DeviceDesc2% = AIRPLUS.8400, PCI\VEN_104C&DEV_8400&SUBSYS_3B011186 > > > > Note that the PCI vendor ID (0x104c) matches your device, but the > > device ID (0x8400) does not (yours is 0x9066). > > > > In this case, the .INF file tells Windows to look for two possible > > devices. In reality, both devices use the same chip (vendor 0x104c, > > device 0x8400), but there are two board variants (one with 0x3b001186, > > the other 0x3b011186). The subsystem ID is really another vendor/device > > ID combination (0x1186 is D-Link's vendor ID, 0x3b00 and 0x3b01 are > > the device codes D-Link has assigned to their boards). Exactly what > > the differences are between the board revs is anyone's guess. Maybe > > they use the same Texas Instruments chip, but with slightly different > > RF circuitry. Maybe they're really the same electronically, but D-Link > > decided to give each production run their own ID code because they're > > funny that way. > > > > In any case, not only do the vendor ID and device ID not match your board, > > the subsystem IDs don't match yours either (0x3b041186). So this driver > > is not the one that goes with your card. > > Ok thank you very much for this explanation, this is now very clear. > I'm going to try other drivers, I think looking on Google for these > vendor and device IDs will point out a relevant driver. At first > glance it seems that NetGear WG-311 uses the same chip, I'm going to > have a try to their driver. One more thing. Different board distributors will often use the same chips, but sometimes they assign their cards different subsystem IDs, just to fool people into thinking the cards are really different. For example, the Netgear WG311 driver's .INF file might have entries that specify the same VEN/DEV values, but with a different subsystem ID. This would prevent Windows from recognizing that Netgear's driver will work with D-Link's card, and vice-versa. To defeat this, you need to edit the .INF a little. You can remove the &SUBSYS portion of the device description. In other words, if the .INF says this: [D-Link] %AIRPLUS.DeviceDesc1% = AIRPLUS.8400, PCI\VEN_104C&DEV_8400&SUBSYS_3B001186 %AIRPLUS.DeviceDesc2% = AIRPLUS.8400, PCI\VEN_104C&DEV_8400&SUBSYS_3B011186 Then make it say this: [D-Link] %AIRPLUS.DeviceDesc1% = AIRPLUS.8400, PCI\VEN_104C&DEV_8400 %AIRPLUS.DeviceDesc2% = AIRPLUS.8400, PCI\VEN_104C&DEV_8400&SUBSYS_3B011186 Note that you don't have to remove the &SUBSYS specification from both lines: one is enough. This will allow Windows (and, coincidentally, the NDISulator), to match the driver to any card with the correct PCI vendor/device ID, regardless of its subsystem ID. A couple of points: - Some .INF files don't have the &SUBSYS specifications to begin with. Usually these are driver kits supplied by the chip manufacturer directly, which are meant to work with any board that uses their chipset. - Do _NOT_ add or remove lines to the device specification section of the .INF file. The .INF file syntax is very tricky: you can sometimes edit existing entries, but you can't add or remove lines without making additional changes. Just putting in a new line will make the .INF file invalid and ndiscvt(8) won't be able to parse it correctly anymore. (Always keep a copy of the original file handy.) - In rare cases, someone will go the extra step and modify the driver source code itself so that it will only work with specific boards, so even changing the .INF file won't work. I've only seen this once though. Alteon Networks had code in their drivers to check for a special byte in the EEPROMs of all the gigabit ethernet cards with their chips (the Tigon I and II). This byte contained the OEM vendor code. There were a lot of Alteon OEM cards: IBM, SGI, 3Com, Netgear, etc. Some of them were very expensive (the IBM card sold specifically for AIX RS/6000 systems cost over $1000) and some were very cheap (the Netgear one was $200, which at the time was amazing). But they were all really the same hardware. In theory, if you had an RS/6000 machine, you could save $800 by buying a Netgear card instead of the IBM one. Alteon had to stop people doing that though, since it would piss off some of their OEMs, so each OEM's driver would specifically check to make sure you were using it with the right card. This would stop the AIX driver from working with a Netgear card. If you were really clever, I suppose you could patch the AIX driver binary to recognize a different OEM ID code (it was just one byte) but as far as I know I don't think anyone did this. - When a driver is 'digitally signed' by Microsoft, the signature is calculated using both the .SYS file and the .INF file, so if you edit the .INF file for a signed driver, you'll invalidate the digital signature, and Windows will whine that you're trying to load an unsigned driver. Just tell it to load the driver anyway. (The NDISulator obviously doesn't care.) -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 22:00:49 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8FF1516A42C; Thu, 24 Nov 2005 22:00:49 +0000 (GMT) (envelope-from oberman@es.net) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1063D43FAE; Thu, 24 Nov 2005 20:37:35 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id IBA74465; Thu, 24 Nov 2005 12:37:31 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id C9F235D09; Thu, 24 Nov 2005 12:37:31 -0800 (PST) To: Mathieu Prevot In-reply-to: Your message of "Thu, 24 Nov 2005 13:05:47 +0100." <74C4FED8-AFD1-4375-A875-438827BECC57@club-internet.fr> Date: Thu, 24 Nov 2005 12:37:31 -0800 From: "Kevin Oberman" Message-Id: <20051124203731.C9F235D09@ptavv.es.net> Cc: Doug Poland , acpi@freebsd.org, FreeBSD Current Subject: Re: Build just one module (was Re: [Fwd: cvs commit: src/sys/dev/acpica acpi_cmbat.c]) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2005 22:00:49 -0000 > From: Mathieu Prevot > Date: Thu, 24 Nov 2005 13:05:47 +0100 > Sender: owner-freebsd-acpi@freebsd.org > > > Le 23 nov. 05 à 15:48, Doug Poland a écrit : > > > On Wed, Nov 23, 2005 at 11:49:20AM +0100, Mathieu Prevot wrote: > >> > >> Le 23 nov. 05 ? 03:49, Doug Poland a ?crit : > >> > >>>> Nate Lawson wrote: > >>>>> Here is a patch that should fix the battery hangs on RELENG_6. It > >>>>> was tested to work fine, although I need testing from an affected > >>>>> user to verify it fixes the problem. It was committed to HEAD and > >>>>> will be MFCed if it fixes the problem. > >>>>> > >>> My Dell C600 is affected by this problem. I'm running 6.0-STABLE > > >>> and > >>> would be glad to test the patch. Since I don't run patches > >>> often, if > >>> someone could point me to a doc on how to apply the patch, I'd > >>> appreciate it. > >> You should think man 'subject', Unix for the impatient or google and > >> find things like: > >> > >> patch -i patchfile filetopatch > >> patch >> > > Thank you, that part is fairly obvious. What I'm unsure of is > > where in > > the source tree do I apply that patch from, and, must I to rebuild > > world, or just the affected part of sys/dev. > > Try and see for the patch. 'patch -i patchfile filetopatch' works > from anywhere. > I don't think you need to rebuild world. I think you can just build > acpi module but I don't know how. > You may glance at /usr/src/Makefile* ... While reading /usr/src/Makefile* should get you there, those with limited make-foo should go to /sys/modules/acpi and: make obj make clean make depend make make install This will only take a couple of minutes, then reboot your system. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 23:14:23 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D0EE16A700 for ; Thu, 24 Nov 2005 23:14:22 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C94C44187 for ; Thu, 24 Nov 2005 19:31:09 +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 smtp4-g19.free.fr (Postfix) with ESMTP id BE29C401A5; Thu, 24 Nov 2005 20:31:06 +0100 (CET) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 47018405A; Thu, 24 Nov 2005 20:30:52 +0100 (CET) Date: Thu, 24 Nov 2005 20:30:52 +0100 From: Jeremie Le Hen To: "Wojciech A. Koszek" Message-ID: <20051124193052.GU1006@obiwan.tataz.chchile.org> References: <20051121162544.GB94958@freebsd.czest.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051121162544.GB94958@freebsd.czest.pl> User-Agent: Mutt/1.5.11 Cc: freebsd-current@freebsd.org Subject: Re: Linking basesystem with additional libraries. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 23:14:23 -0000 Hi Wojciech, > Is there any reason why we couldn't have LDADD honored in "buildworld" > process? If there are no negative implications, I volunteer to do the > work. I'd find it really useful. Yes, I'm curious, but could you explain in what way it would be useful ? Thank you, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 23:17:18 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 993EF16A5FA for ; Thu, 24 Nov 2005 23:17:07 +0000 (GMT) (envelope-from caiquanqing@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E31A4558C for ; Thu, 24 Nov 2005 21:06:01 +0000 (GMT) (envelope-from caiquanqing@gmail.com) Received: by xproxy.gmail.com with SMTP id t12so271376wxc for ; Thu, 24 Nov 2005 13:05:59 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ZMIU6/H7uhnJNgRxnGrXz7kGgBehGD2q7K9khDjKySukisblqf8i9mba/E7ZpobAk1lGE8gKDJCoXMFL0caeNCqkdAqO607ufOcv5h/Sz1DEwHZV6BCE5l2aZOfCTO1hjnGlTR3F67wsDhxwV2kCqvsGwX9rYJpTSPYpD6etmds= Received: by 10.70.88.3 with SMTP id l3mr5539734wxb; Thu, 24 Nov 2005 12:59:53 -0800 (PST) Received: by 10.70.12.18 with HTTP; Thu, 24 Nov 2005 12:59:52 -0800 (PST) Message-ID: <2b22951e0511241259y513b74c3x9a81ad2ff7e47c36@mail.gmail.com> Date: Thu, 24 Nov 2005 12:59:53 -0800 From: "Cai, Quanqing" To: Eric Anholt In-Reply-To: <1132780093.1197.60.camel@leguin> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1132743283.1197.55.camel@leguin> <1132780093.1197.60.camel@leguin> Cc: current@freebsd.org Subject: Re: DRM update for testing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 23:17:20 -0000 I have an on-board video chip: pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x5333 device 0x8d04 S3 Inc. VT8375 [ProSavage8 KM266/KL266] The kernel driver is OK, and I can kldload it or compile it into kernel. dmesg shows: drm0: mem 0xed000000-0xed07ffff,0xe0000000-0xe7ffffff at device 0.0 on pci1 info: [drm] AGP at 0xe8000000 64MB info: [drm] Initialized savage 2.4.1 20050313 But there is no DRI in Xorg, here is glxinfo: name of display: :0.0 display: :0 screen: 0 direct rendering: No Thanks On 11/23/05, Eric Anholt wrote: > On Wed, 2005-11-23 at 02:54 -0800, Eric Anholt wrote: > > I've got a patch at: > > http://people.freebsd.org/~anholt/dri/drm-sys-20051123.diff > > for testing, which merges DRM CVS into FreeBSD. I've done basic tests > > of a recent DRM CVS with WITNESS on AGP/PCI Matrox, AGP/PCI Rage 128, > > AGP Radeon r100/r200/r300, AGP Savage4 (new!), SiS, and 3dfx, and this > > version should be equivalent to what I tested. I'll do another pass of > > testing before I commit, but I'd also like to get some wider testing so > > more panics can show up if they exist. This particular diff has only > > been compile-tested with LINT on amd64 so far. > > I've fixed the lack of savage module Makefile in the diff and updated > the diff in-place. > > -- > Eric Anholt eta@lclark.edu > http://people.freebsd.org/~anholt/ anholt@FreeBSD.org > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2 (FreeBSD) > > iD8DBQBDhNo9HUdvYGzw6vcRAh1WAJ9mp6BNumPftp9EulHlLCXZna2yTgCeNf5c > CcKvNgraWZLGgnH3f47VXg8=3D > =3Duuv2 > -----END PGP SIGNATURE----- > > > From owner-freebsd-current@FreeBSD.ORG Thu Nov 24 23:29:41 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D05316A41F; Thu, 24 Nov 2005 23:29:41 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id A99B443D55; Thu, 24 Nov 2005 23:29:40 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.13.4/8.13.4) with ESMTP id jAONTEEe055791; Thu, 24 Nov 2005 15:29:14 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.13.4/8.13.4/Submit) id jAONTEkr055790; Thu, 24 Nov 2005 15:29:14 -0800 (PST) Date: Thu, 24 Nov 2005 15:29:14 -0800 (PST) From: Matthew Dillon Message-Id: <200511242329.jAONTEkr055790@apollo.backplane.com> To: John Baldwin References: <200511231406.06282.jhb@freebsd.org> Cc: current@freebsd.org Subject: Re: nve locking fixes round 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 24 Nov 2005 23:29:41 -0000 :Ok, now that the first set of locking overhaul is in the tree, can folks with :working nve(4) adapters test the patch referenced below and make sure there :are no regressions. Having the IFF_UP fiddling turned off may or may not :help folks getting the TX timeouts as well, btw, so if people are feeling :brave they can try this patch as well. Note it is only applicable to recent :current. : :http://www.FreeBSD.org/~jhb/patches/nve_locking.patch : :-- :John Baldwin <>< http://www.FreeBSD.org/~jhb/ :"Power Users Use the Power to Serve" = http://www.FreeBSD.org The reason I set sc->pending_txs to 0 in DFly after the reinit is because when a watchdog timeout occurs and you reset the device, *ALL* mbufs still sitting in the transmit ring are lost. They will never be acknowledged, ever. So pending_txs will never drop back to 0 on its own. This is what led to continuous watchdog timeout reports when, in fact, only one timeout actually occured. The FreeBSD code does set pending_txs to 0 in nve_stop(). I'm not sure this is correct, however, unless the pfnStop() ABI call cleans out pending mbufs in the transmit ring (which seems unlikely). The count would wind up going negative. Another problem that neither of us has dealt with yet is recovery of dead transmit mbufs. Right now that only occurs in nve_ospackettx(), but nve_ospackettx() is only called by the Nvidia code during normal operation. ABI calls to e.g. reset the Nvidia device will *NOT* clean out the transmit ring and call nve_ospackettx(), so we lose track of all the mbufs that were sitting in there at the time of a reinit. But, of course, the biggest problem is simply the fact that the NVidia ABI library seems to be rather broken. On my nForce4-based boxes the DFly driver can recover from numerous watchdog timeouts (and they occur quite often, even when the network load is virtually nil), but after an hour or two of testing at GiGE speeds the hardware itself stops working entirely, to the point where I have to physically unplug and replug the power cord for the machine for the hardware to start working again. -Matt Matthew Dillon From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 00:23:46 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AF9E16A42A for ; Fri, 25 Nov 2005 00:23:46 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8729143D45 for ; Fri, 25 Nov 2005 00:23:35 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 78BA446B7F; Thu, 24 Nov 2005 19:23:32 -0500 (EST) Date: Fri, 25 Nov 2005 00:23:32 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Mayank Kumar In-Reply-To: <3A5384BC2FBA4C488865F2275A036BFF040B269C@APS-MSG-01.southpacific.corp.microsoft.com> Message-ID: <20051125001652.N81764@fledge.watson.org> References: <3A5384BC2FBA4C488865F2275A036BFF040B269C@APS-MSG-01.southpacific.corp.microsoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: What is the correct behaviour for local socket(AF_UNIX) in the following scenario? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Nov 2005 00:23:46 -0000 On Fri, 25 Nov 2005, Mayank Kumar wrote: > I am trying to understand the behavior of localsockets in the following > scenario. > > A process p1 writes a huge amoount of data to a AF_UNIX,DGRAM socket and > exits. Now if there is no process p2 to read the data written by process > p1 from the same localsocket, then this has resulted in a huge memory > leak on a FreeBSD system. > > I want to understand, if there is a mechanism in FreeBsd to take care of > this leak or this is the expected behaviour and application writers > should take care of this situation. Also what should be the behaviour on > such a socket if shutdown or close is issued on such a socket. Any help > on the behaviour on other unixes in the same scenario would also help a > lot. Mayank, The key to understanding how this is handled is to understand that UNIX domain sockets aren't file system objects -- the file system simply provides a name space by which to reach the socket. The buffers associated with UNIX domain sockets belong to the sockets, not to the name. You can think of this in the same way as you might think of port numbers and IP addresses, although there are some subtle differences. There are two common operational modes for UNIX domain sockets: stream mode, and datagram mode. In stream mode, a listen socket is bound to the name, and then new socket pairs are generated when that name is connected. In datagram mode, a single socket exists on the "server" end, and then a series of other sockets may send to it using sendto and send. The buffers are associated with the active communication sockets in both case, so if all endpoints are closed, the name persists, but has no persisting buffers. So a name can be leaked (i.e., not be unlinked when a process is done with it), which is similar to leaking a temporary file that isn't unlinked. Hope this helps, Robert N M Watson From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 00:54:22 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56AA416A41F; Fri, 25 Nov 2005 00:54:22 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id B177243D6E; Fri, 25 Nov 2005 00:54:18 +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 smtp4-g19.free.fr (Postfix) with ESMTP id EB6B93FEE2; Fri, 25 Nov 2005 01:54:12 +0100 (CET) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id D98D9405A; Fri, 25 Nov 2005 01:53:57 +0100 (CET) Date: Fri, 25 Nov 2005 01:53:57 +0100 From: Jeremie Le Hen To: Bill Paul Message-ID: <20051125005357.GX1006@obiwan.tataz.chchile.org> References: <20051124112413.GA1006@obiwan.tataz.chchile.org> <20051124194235.E8CDB16A420@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051124194235.E8CDB16A420@hub.freebsd.org> User-Agent: Mutt/1.5.11 Cc: freebsd-current@freebsd.org Subject: Re: Lasted NDIS wrapper for D-Link DWL-520+ on RELENG_6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2005 00:54:22 -0000 Hi Bill, > > > Now, The first thing you should have done is to actually inspect the > > > .INF file. Like the self-documenting ndisgen(8) script tells you, this > > > is the file that actually contains the device ID information that the > > > Windows Plug & Play Mangler will use when trying to match a device > > > to a driver. The AIRPLUS.INF file says: > > > > > > [D-Link] > > > %AIRPLUS.DeviceDesc1% = AIRPLUS.8400, PCI\VEN_104C&DEV_8400&SUBSYS_3B001186 > > > %AIRPLUS.DeviceDesc2% = AIRPLUS.8400, PCI\VEN_104C&DEV_8400&SUBSYS_3B011186 > > > > > > Note that the PCI vendor ID (0x104c) matches your device, but the > > > device ID (0x8400) does not (yours is 0x9066). > > > > > > In this case, the .INF file tells Windows to look for two possible > > > devices. In reality, both devices use the same chip (vendor 0x104c, > > > device 0x8400), but there are two board variants (one with 0x3b001186, > > > the other 0x3b011186). The subsystem ID is really another vendor/device > > > ID combination (0x1186 is D-Link's vendor ID, 0x3b00 and 0x3b01 are > > > the device codes D-Link has assigned to their boards). Exactly what > > > the differences are between the board revs is anyone's guess. Maybe > > > they use the same Texas Instruments chip, but with slightly different > > > RF circuitry. Maybe they're really the same electronically, but D-Link > > > decided to give each production run their own ID code because they're > > > funny that way. > > > > > > In any case, not only do the vendor ID and device ID not match your board, > > > the subsystem IDs don't match yours either (0x3b041186). So this driver > > > is not the one that goes with your card. > > > > Ok thank you very much for this explanation, this is now very clear. > > I'm going to try other drivers, I think looking on Google for these > > vendor and device IDs will point out a relevant driver. At first > > glance it seems that NetGear WG-311 uses the same chip, I'm going to > > have a try to their driver. > > One more thing. Different board distributors will often use the same > chips, but sometimes they assign their cards different subsystem IDs, > just to fool people into thinking the cards are really different. For > example, the Netgear WG311 driver's .INF file might have entries that > specify the same VEN/DEV values, but with a different subsystem ID. > This would prevent Windows from recognizing that Netgear's driver > will work with D-Link's card, and vice-versa. > > To defeat this, you need to edit the .INF a little. You can remove > the &SUBSYS portion of the device description. In other words, if > the .INF says this: > > [D-Link] > %AIRPLUS.DeviceDesc1% = AIRPLUS.8400, PCI\VEN_104C&DEV_8400&SUBSYS_3B001186 > %AIRPLUS.DeviceDesc2% = AIRPLUS.8400, PCI\VEN_104C&DEV_8400&SUBSYS_3B011186 > > Then make it say this: > > [D-Link] > %AIRPLUS.DeviceDesc1% = AIRPLUS.8400, PCI\VEN_104C&DEV_8400 > %AIRPLUS.DeviceDesc2% = AIRPLUS.8400, PCI\VEN_104C&DEV_8400&SUBSYS_3B011186 > > Note that you don't have to remove the &SUBSYS specification from both > lines: one is enough. This will allow Windows (and, coincidentally, > the NDISulator), to match the driver to any card with the correct > PCI vendor/device ID, regardless of its subsystem ID. Ok, these precisions have been indeed *very* precious, is it the first time you post them ? I have had this card for two years and I have tried to make it work many times in the past, so I now have a great collection of DWL-520+'s driver versions from D-Link. I check for my own card ID (9066) among them, none of the provided .INF handles it. That's a pity. I checked NetGear WG311's drivers and it appears that the WG311v2 family does use the same chip as my D-Link DWL-520+ based on a Texas Instrument chip. I downloaded this driver : ftp://downloads.netgear.com/files/wg311v2_v2_0_0_7.zip I wanted to use the Windows XP driver, but the SUBSYS value didn't match, as you described it. Therefore I suppressed it and got the ndis0 interface for the first time since I own this card ! % ndis0: mem 0xc9a00000-0xc9a01fff,0xc99e0000-0xc99fffff irq 19 at device 8.0 on pci0 % ndis0: NDIS API version: 5.1 % ndis0: Ethernet address: 00:80:c8:2c:58:db For the sake of completeness, I loaded firmware related KLD before loading the real driver itself. Thank you very much for you help P^HBill ;-). Best regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 01:08:19 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7246F16A41F for ; Fri, 25 Nov 2005 01:08:19 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from smtp2-g19.free.fr (smtp2-g19.free.fr [212.27.42.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83D4243D7D for ; Fri, 25 Nov 2005 01:08:11 +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 smtp2-g19.free.fr (Postfix) with ESMTP id E51F0521E2 for ; Fri, 25 Nov 2005 02:08:10 +0100 (CET) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 6B6C2405B; Fri, 25 Nov 2005 02:07:56 +0100 (CET) Date: Fri, 25 Nov 2005 02:07:56 +0100 From: Jeremie Le Hen To: freebsd-current@freebsd.org Message-ID: <20051125010756.GZ1006@obiwan.tataz.chchile.org> References: <20051124112413.GA1006@obiwan.tataz.chchile.org> <20051124194235.E8CDB16A420@hub.freebsd.org> <20051125005357.GX1006@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051125005357.GX1006@obiwan.tataz.chchile.org> User-Agent: Mutt/1.5.11 Subject: Re: Lasted NDIS wrapper for D-Link DWL-520+ on RELENG_6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2005 01:08:19 -0000 For the sake of accuracy : > I checked NetGear WG311's drivers and it appears that the WG311v2 > family does use the same chip as my D-Link DWL-520+ based on a Texas > Instrument chip. ... based on a Texas Instrument ACX111 chip. -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 02:21:04 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73D4F16A41F for ; Fri, 25 Nov 2005 02:21:04 +0000 (GMT) (envelope-from emil@cs.rmit.edu.au) Received: from its-mu-mail2.its.rmit.edu.au (its-mu-mail2.its.rmit.edu.au [131.170.2.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FD0D43D5F for ; Fri, 25 Nov 2005 02:20:50 +0000 (GMT) (envelope-from emil@cs.rmit.edu.au) Received: from wombat.cs.rmit.edu.au (wombat.cs.rmit.edu.au [131.170.24.41]) by its-mu-mail2.its.rmit.edu.au (8.13.1/8.12.11/mail2) with ESMTP id jAP2Kf57008513 for ; Fri, 25 Nov 2005 13:20:41 +1100 (EST) Received: from goanna.cs.rmit.edu.au (goanna.cs.rmit.edu.au [131.170.24.40]) by wombat.cs.rmit.edu.au (8.12.10/8.12.10/cshub) with ESMTP id jAP2Kffj021838 for ; Fri, 25 Nov 2005 13:20:41 +1100 (EST) Received: (from emil@localhost) by goanna.cs.rmit.edu.au (8.11.3/8.9.3/csnode) id jAP2Kfb18348 for freebsd-current@freebsd.org; Fri, 25 Nov 2005 13:20:41 +1100 (EST) Date: Fri, 25 Nov 2005 13:20:41 +1100 From: Emil Mikulic To: freebsd-current@freebsd.org Message-ID: <20051125022040.GA9150@cs.rmit.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: SunOS 5.9 X-PGP-Fingerprint: D2B4 7C14 0C41 9AE5 8D2B 16B0 D3D6 F910 8E4C 5D35 X-Authentication-Warning: localhost: emil pwned teh intarweb User-Agent: Mutt/1.5.9i X-Scanned-By: MIMEDefang 2.44 Subject: bge driver autoneg failure and system-wide stalls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Nov 2005 02:21:04 -0000 I have a network port with bad wiring in the walls - a cable tester shows only wires 1,2,3 and 6 are actually connected. My solution is to patch directly into the switch, in which case the bge driver works just fine. However, the bad wiring exposes two problems with the bge driver in 7-CURRENT. From memory, I think these turned up in the 5.x line because I wasn't seeing either issue in 4.x The first problem is that, once ifconfig'd to an IP address, there will be periodic system-wide stalls. They generally last a little under a second and are incredibly annoying and can cause keypresses to be lost at the console. I instrumented the kernel and, as far as I can tell, once ifconfig'd, the following will happen in brgphy (mii module): Every second there is a call to brgphy_service() with cmd=MII_TICK. Every five seconds, this function will call brgphy_mii_phy_auto(). This function calls brgphy_loop(). In brgphy_loop(), there is a #if 0'd bit of code that device_printf()'s how many times it looped. I enabled it. Sometimes it reports zero loops - when this happens there is no stall. On a very pronounced stall, there will be between 3000-7000 loops. (i.e. the stalls appear a bit random because they only get a chance to happen once every five seconds, and sometimes brgphy_loop() doesn't result in a noticeable stall) The other problem is that bge will never negotiate a working link speed. ifconfig will always return "status: no carrier" If I force the media to 10baseT/UTP or 100baseTX (either mediaopt full-duplex or not), it will issue a couple more MII_TICKs then stop, ifconfig will return "status: active", there will be no more stalls, and, most importantly, the network connection will actually work. Is this fixable and actually worth fixing? --Emil From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 02:41:52 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1679B16A420 for ; Fri, 25 Nov 2005 02:41:52 +0000 (GMT) (envelope-from emil@cs.rmit.edu.au) Received: from its-mu-mail1.its.rmit.edu.au (its-mu-mail1.its.rmit.edu.au [131.170.1.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id D426643D62 for ; Fri, 25 Nov 2005 02:41:49 +0000 (GMT) (envelope-from emil@cs.rmit.edu.au) Received: from wombat.cs.rmit.edu.au (wombat.cs.rmit.edu.au [131.170.24.41]) by its-mu-mail1.its.rmit.edu.au (8.13.1/8.13.1/mail1) with ESMTP id jAP2fat4026009 for ; Fri, 25 Nov 2005 13:41:47 +1100 (EST) Received: from goanna.cs.rmit.edu.au (goanna.cs.rmit.edu.au [131.170.24.40]) by wombat.cs.rmit.edu.au (8.12.10/8.12.10/cshub) with ESMTP id jAP2e5fj023989 for ; Fri, 25 Nov 2005 13:40:05 +1100 (EST) Received: (from emil@localhost) by goanna.cs.rmit.edu.au (8.11.3/8.9.3/csnode) id jAP2e4d22187 for freebsd-current@freebsd.org; Fri, 25 Nov 2005 13:40:04 +1100 (EST) Date: Fri, 25 Nov 2005 13:40:04 +1100 From: Emil Mikulic To: freebsd-current@freebsd.org Message-ID: <20051125024004.GA21161@cs.rmit.edu.au> References: <20051125022040.GA9150@cs.rmit.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <20051125022040.GA9150@cs.rmit.edu.au> X-Operating-System: SunOS 5.9 X-PGP-Fingerprint: D2B4 7C14 0C41 9AE5 8D2B 16B0 D3D6 F910 8E4C 5D35 X-Authentication-Warning: localhost: emil pwned teh intarweb User-Agent: Mutt/1.5.9i X-Scanned-By: MIMEDefang 2.44 Subject: Re: bge driver autoneg failure and system-wide stalls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Nov 2005 02:41:52 -0000 I don't know how I forgot to mention what kind of card it is. =46rom pciconf -lv: card=3D0x3008103c chip=3D0x167714e4 rev=3D0x01 hdr=3D0x00 device=3D'BCM5750A1 NetXtreme Gigabit Ethernet PCI Express' =46rom dmesg: bge0: It's the onboard network interface on an HP xw4200 workstation. ( http://www.hp.com/workstations/pws/xw4200/ ) --Emil From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 03:23:58 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A57A016A41F for ; Fri, 25 Nov 2005 03:23:58 +0000 (GMT) (envelope-from caiquanqing@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BE2843D64 for ; Fri, 25 Nov 2005 03:23:57 +0000 (GMT) (envelope-from caiquanqing@gmail.com) Received: by xproxy.gmail.com with SMTP id t12so325820wxc for ; Thu, 24 Nov 2005 19:23:56 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Fw//zB4mncAQwHZMUkMVmsG5XRmN9Z33ht+jn9y5BaUOXtXhNLsllOnLCl7aiF9540z2gO6QS8vkZmy0/jpA7Zbx2l3+aKP08dCbEgZlzFlnkaVFJz8cVlcOfcGxHJtnrX0TfDmDi0zp8W2gMRk6yNdFmTo3KfSFDdEnBCtAG1U= Received: by 10.70.52.18 with SMTP id z18mr5934980wxz; Thu, 24 Nov 2005 19:23:56 -0800 (PST) Received: by 10.70.12.18 with HTTP; Thu, 24 Nov 2005 19:23:56 -0800 (PST) Message-ID: <2b22951e0511241923u5e6e00b2q148fd03aa11c42ca@mail.gmail.com> Date: Thu, 24 Nov 2005 19:23:56 -0800 From: "Cai, Quanqing" To: simokawa@freebsd.org, bug-followup@FreeBSD.org, fbsd-lists@dudes.ch, freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: Re: kern/83999 : [firewire] [patch] panic in fw_bus_explore due to NULL reference X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Nov 2005 03:23:58 -0000 Can somebody please have a look at this and apply the patch? However, I can't re-produce this bug, but the fix does not hurt anything. I made the changement on my two machines according the patch, and everything looks and works good. One of machine is 7.0-CURRENT, another one is 6-STABLE. BR Cai, Quanqing From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 03:49:52 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8ED816A420 for ; Fri, 25 Nov 2005 03:49:52 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from nic.ach.sch.gr (nic.sch.gr [194.63.238.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8BEB43D67 for ; Fri, 25 Nov 2005 03:49:43 +0000 (GMT) (envelope-from keramida@linux.gr) Received: (qmail 24812 invoked by uid 207); 25 Nov 2005 03:49:38 -0000 Received: from keramida@linux.gr by nic by uid 201 with qmail-scanner-1.21 (sophie: 3.04/2.30/3.97. Clear:RC:1(81.186.70.191):. Processed in 0.40811 secs); 25 Nov 2005 03:49:38 -0000 Received: from dialup191.ach.sch.gr (HELO flame.pc) ([81.186.70.191]) (envelope-sender ) by nic.sch.gr (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 25 Nov 2005 03:49:37 -0000 Received: from flame.pc (flame [127.0.0.1]) by flame.pc (8.13.4/8.13.4) with ESMTP id jAP3n6IX016868; Fri, 25 Nov 2005 05:49:06 +0200 (EET) (envelope-from keramida@linux.gr) Received: (from keramida@localhost) by flame.pc (8.13.4/8.13.4/Submit) id jAP3n34c016867; Fri, 25 Nov 2005 05:49:03 +0200 (EET) (envelope-from keramida@linux.gr) Date: Fri, 25 Nov 2005 05:49:02 +0200 From: Giorgos Keramidas To: Jeremie Le Hen Message-ID: <20051125034902.GA16834@flame.pc> References: <20051121162544.GB94958@freebsd.czest.pl> <20051124193052.GU1006@obiwan.tataz.chchile.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051124193052.GU1006@obiwan.tataz.chchile.org> Cc: "Wojciech A. Koszek" , freebsd-current@freebsd.org Subject: Re: Linking basesystem with additional libraries. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Nov 2005 03:49:52 -0000 On 2005-11-24 20:30, Jeremie Le Hen wrote: > > Is there any reason why we couldn't have LDADD honored in "buildworld" > > process? If there are no negative implications, I volunteer to do the > > work. I'd find it really useful. > > Yes, I'm curious, but could you explain in what way it would be useful ? I'd be interested too. I think the main reason why this would NOT be a good idea is that changing an external library to a newer version can break the buildworld/installworld process in unexpected ways From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 05:34:59 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BAFE716A41F for ; Fri, 25 Nov 2005 05:34:59 +0000 (GMT) (envelope-from mayank@microsoft.com) Received: from mail-sin1.microsoft.com (mail-sin1.microsoft.com [207.46.50.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id 140FA43D4C for ; Fri, 25 Nov 2005 05:34:58 +0000 (GMT) (envelope-from mayank@microsoft.com) Received: from APS-MSG-01.southpacific.corp.microsoft.com ([157.60.218.52]) by mail-sin1.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 25 Nov 2005 14:34:57 +0900 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 25 Nov 2005 13:34:56 +0800 Message-ID: <3A5384BC2FBA4C488865F2275A036BFF040B284E@APS-MSG-01.southpacific.corp.microsoft.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: What is the correct behaviour for local socket(AF_UNIX) in the following scenario? thread-index: AcXxIgHQPkjcHToxTGCqbr9PZGeVDAAX63Bg From: "Mayank Kumar" To: "Joseph Koshy" X-OriginalArrivalTime: 25 Nov 2005 05:34:57.0603 (UTC) FILETIME=[F8BB5930:01C5F181] Cc: freebsd-current@freebsd.org Subject: RE: What is the correct behaviour for local socket(AF_UNIX) in the following scenario? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Nov 2005 05:34:59 -0000 I have not measured this leak. This is just my feeling that the behaviour would be like this. If the behavior is not this way, then how do we take account of this in FREEBSD is what I want to know.=20 I mean, if p1 has written data and exits and there is no p1 to read it, then what happens to the data written by p1. Regards Mayank -----Original Message----- From: Joseph Koshy [mailto:joseph.koshy@gmail.com]=20 Sent: Thursday, November 24, 2005 11:38 PM To: Mayank Kumar Cc: freebsd-current@freebsd.org Subject: Re: What is the correct behaviour for local socket(AF_UNIX) in the following scenario? > Now if there is no process p2 to read the data written by process p1=20 > from the same localsocket, then this has resulted in a huge memory=20 > leak on a FreeBSD system. How are you measuring the 'leak', and which version of FreeBSD are you using? -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 05:44:16 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FFE716A41F; Fri, 25 Nov 2005 05:44:16 +0000 (GMT) (envelope-from mayank@microsoft.com) Received: from mail-sin2.microsoft.com (mail-sin2.microsoft.com [207.46.50.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 214D743D5C; Fri, 25 Nov 2005 05:44:14 +0000 (GMT) (envelope-from mayank@microsoft.com) Received: from APS-MSG-01.southpacific.corp.microsoft.com ([157.60.218.52]) by mail-sin2.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 25 Nov 2005 13:44:14 +0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 25 Nov 2005 13:44:13 +0800 Message-ID: <3A5384BC2FBA4C488865F2275A036BFF040B285D@APS-MSG-01.southpacific.corp.microsoft.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: What is the correct behaviour for local socket(AF_UNIX) in the following scenario? thread-index: AcXxVno/bOuphiUIQ4S9gX6juQAODQAK+1FQ From: "Mayank Kumar" To: "Robert Watson" X-OriginalArrivalTime: 25 Nov 2005 05:44:14.0195 (UTC) FILETIME=[447C8C30:01C5F183] Cc: freebsd-current@freebsd.org Subject: RE: What is the correct behaviour for local socket(AF_UNIX) in the following scenario? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Nov 2005 05:44:16 -0000 Hi Robert >From this I understand that if p1 closes the socket, then all the data written by it is discarded since the buffers associated with this socket no longer exists. If that is the case, then this is not at all true that p1 can write data on a socket and close it and exit=20 and p2 will still be able to retrieve the data written by p1. Does FreeBSD differ with solaris or other unixes in this implementation. I believe that Solaris does support the above scenario although I am not sure. Do you know How other unixes behave here. Because it makes a lot=20 of sense for localsockets to facilitate IPC on a system by supporting the above scenario between two processes. Regards Mayank -----Original Message----- From: Robert Watson [mailto:rwatson@FreeBSD.org]=20 Sent: Friday, November 25, 2005 5:54 AM To: Mayank Kumar Cc: freebsd-current@freebsd.org Subject: Re: What is the correct behaviour for local socket(AF_UNIX) in the following scenario? On Fri, 25 Nov 2005, Mayank Kumar wrote: > I am trying to understand the behavior of localsockets in the=20 > following scenario. > > A process p1 writes a huge amoount of data to a AF_UNIX,DGRAM socket=20 > and exits. Now if there is no process p2 to read the data written by=20 > process > p1 from the same localsocket, then this has resulted in a huge memory=20 > leak on a FreeBSD system. > > I want to understand, if there is a mechanism in FreeBsd to take care=20 > of this leak or this is the expected behaviour and application writers > should take care of this situation. Also what should be the behaviour=20 > on such a socket if shutdown or close is issued on such a socket. Any=20 > help on the behaviour on other unixes in the same scenario would also=20 > help a lot. Mayank, The key to understanding how this is handled is to understand that UNIX domain sockets aren't file system objects -- the file system simply provides a name space by which to reach the socket. The buffers associated with UNIX domain sockets belong to the sockets, not to the name. You can think of this in the same way as you might think of port numbers and IP addresses, although there are some subtle differences. There are two common operational modes for UNIX domain sockets: stream mode, and datagram mode. In stream mode, a listen socket is bound to the name, and then new socket pairs are generated when that name is connected.=20 In datagram mode, a single socket exists on the "server" end, and then a series of other sockets may send to it using sendto and send. The buffers are associated with the active communication sockets in both case, so if all endpoints are closed, the name persists, but has no persisting buffers. So a name can be leaked (i.e., not be unlinked when a process is done with it), which is similar to leaking a temporary file that isn't unlinked. Hope this helps, Robert N M Watson From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 07:29:22 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D57616A41F for ; Fri, 25 Nov 2005 07:29:22 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from leguin.anholt.net (69-30-77-85.dq1sn.easystreet.com [69.30.77.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32C4843D5E for ; Fri, 25 Nov 2005 07:29:14 +0000 (GMT) (envelope-from eta@lclark.edu) Received: from leguin.anholt.net (localhost [127.0.0.1]) by leguin.anholt.net (8.13.4/8.13.1) with ESMTP id jAP7TDMS045130; Thu, 24 Nov 2005 23:29:14 -0800 (PST) (envelope-from eta@lclark.edu) Received: (from anholt@localhost) by leguin.anholt.net (8.13.4/8.13.1/Submit) id jAP7TDIo045129; Thu, 24 Nov 2005 23:29:13 -0800 (PST) (envelope-from eta@lclark.edu) X-Authentication-Warning: leguin.anholt.net: anholt set sender to eta@lclark.edu using -f From: Eric Anholt To: "Cai, Quanqing" In-Reply-To: <2b22951e0511241259y513b74c3x9a81ad2ff7e47c36@mail.gmail.com> References: <1132743283.1197.55.camel@leguin> <1132780093.1197.60.camel@leguin> <2b22951e0511241259y513b74c3x9a81ad2ff7e47c36@mail.gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-mhx1qsKdoV5tTNFmyKSn" Date: Thu, 24 Nov 2005 23:29:12 -0800 Message-Id: <1132903752.1197.95.camel@leguin> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Cc: current@freebsd.org Subject: Re: DRM update for testing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Nov 2005 07:29:22 -0000 --=-mhx1qsKdoV5tTNFmyKSn Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2005-11-24 at 12:59 -0800, Cai, Quanqing wrote: > I have an on-board video chip: > pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x5333 device 0x8d04 > S3 Inc. VT8375 [ProSavage8 KM266/KL266] >=20 > The kernel driver is OK, and I can kldload it or compile it into > kernel. dmesg shows: > drm0: mem > 0xed000000-0xed07ffff,0xe0000000-0xe7ffffff at device 0.0 on pci1 > info: [drm] AGP at 0xe8000000 64MB > info: [drm] Initialized savage 2.4.1 20050313 >=20 > But there is no DRI in Xorg, here is glxinfo: > name of display: :0.0 > display: :0 screen: 0 > direct rendering: No New DRM drivers aren't enough -- you need new userland. That means xorg-server-snap and dri-devel. If that's not enough, http://dri.freedesktop.org/wiki/DriTroubleshooting --=20 Eric Anholt eta@lclark.edu http://people.freebsd.org/~anholt/ anholt@FreeBSD.org --=-mhx1qsKdoV5tTNFmyKSn Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDhr1IHUdvYGzw6vcRAkcqAKCNhRg2Nv0CXz8d4opk46+O4VwZLwCfZ9bA tXKGQyXksyJaNUbHYb8SPQM= =71Oi -----END PGP SIGNATURE----- --=-mhx1qsKdoV5tTNFmyKSn-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 08:24:02 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 0AEF216A420; Fri, 25 Nov 2005 08:24:02 +0000 (GMT) In-Reply-To: <20051125005357.GX1006@obiwan.tataz.chchile.org> from Jeremie Le Hen at "Nov 25, 2005 01:53:57 am" To: jeremie@le-hen.org (Jeremie Le Hen) Date: Fri, 25 Nov 2005 08:24:02 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20051125082402.0AEF216A420@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Cc: freebsd-current@freebsd.org Subject: Re: Lasted NDIS wrapper for D-Link DWL-520+ on RELENG_6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2005 08:24:02 -0000 > Ok, these precisions have been indeed *very* precious, is it the > first time you post them ? I didn't think I needed to, since the only skill one really needs to figure this stuff out on their own is the ability to read. But I guess it's too much to expect that people be able do that. > Thank you very much for you help P^HBill ;-). Now look, dumbass. I thought I made it very clear that getting my name wrong was not funny. As in not a laughing matter. As in not something to be joked about. It seems in addition to being prone to losing things and not being able to read, you're unable to grasp this concept either. So let me make it clear to you: IT IS NOT A FUCKING JOKE, YOU RAT BASTARD. And _NO_, a smiley face does not make it ok! If you really want to thank me for my help, then do me the fucking courtesy of not insulting me in the same breath. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 09:33:29 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32DAA16A41F for ; Fri, 25 Nov 2005 09:33:29 +0000 (GMT) (envelope-from sico@loquefaltaba.com) Received: from mail.loquefaltaba.com (78.Red-213-96-97.staticIP.rima-tde.net [213.96.97.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78A3A43D58 for ; Fri, 25 Nov 2005 09:33:27 +0000 (GMT) (envelope-from sico@loquefaltaba.com) Received: from localhost (localhost.loquefaltaba.com [127.0.0.1]) by mail.loquefaltaba.com (Postfix) with ESMTP id 23409C32C; Fri, 25 Nov 2005 10:33:26 +0100 (CET) Received: from mail.loquefaltaba.com ([127.0.0.1]) by localhost (sico.loquefaltaba.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 68628-02; Fri, 25 Nov 2005 10:33:18 +0100 (CET) Received: from webmail.loquefaltaba.com (localhost.loquefaltaba.com [127.0.0.1]) by mail.loquefaltaba.com (Postfix) with ESMTP id BA2D5C326; Fri, 25 Nov 2005 10:33:18 +0100 (CET) Received: from 187.red-80-38-105.staticip.rima-tde.net ([80.38.105.187]) (SquirrelMail authenticated user sico) by webmail.loquefaltaba.com with HTTP; Fri, 25 Nov 2005 10:33:18 +0100 (CET) Message-ID: <64084.80.38.105.187.1132911198.squirrel@webmail.loquefaltaba.com> In-Reply-To: <20051125010756.GZ1006@obiwan.tataz.chchile.org> References: <20051124112413.GA1006@obiwan.tataz.chchile.org> <20051124194235.E8CDB16A420@hub.freebsd.org> <20051125005357.GX1006@obiwan.tataz.chchile.org> <20051125010756.GZ1006@obiwan.tataz.chchile.org> Date: Fri, 25 Nov 2005 10:33:18 +0100 (CET) From: "David Barbero" To: "Jeremie Le Hen" User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: amavisd-new at loquefaltaba.com Cc: current@freebsd.org Subject: Re: Lasted NDIS wrapper for D-Link DWL-520+ on RELENG_6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2005 09:33:29 -0000 Hi all. This chipset is suported by acx100 driver, you can install and probe this from ports net/acx100 o in URL: http://dev.kewl.org/acx100/ . Regards -- "Linux is for people who hate Windows, BSD is for people who love UNIX" "Social Engineer -> Because there is no patch for human stupidity" Jeremie Le Hen wrote: > For the sake of accuracy : > >> I checked NetGear WG311's drivers and it appears that the WG311v2 >> family does use the same chip as my D-Link DWL-520+ based on a Texas >> Instrument chip. > > ... based on a Texas Instrument ACX111 chip. > > -- > Jeremie Le Hen > < jeremie at le-hen dot org >< ttz at chchile dot 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 Nov 25 09:49:07 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEBDF16A41F; Fri, 25 Nov 2005 09:49:07 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9575943D66; Fri, 25 Nov 2005 09:49:06 +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 smtp3-g19.free.fr (Postfix) with ESMTP id F17DB37392; Fri, 25 Nov 2005 10:49:04 +0100 (CET) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id B7C42405A; Fri, 25 Nov 2005 10:48:49 +0100 (CET) Date: Fri, 25 Nov 2005 10:48:49 +0100 From: Jeremie Le Hen To: Bill Paul Message-ID: <20051125094849.GA1006@obiwan.tataz.chchile.org> References: <20051125005357.GX1006@obiwan.tataz.chchile.org> <20051125082402.0AEF216A420@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051125082402.0AEF216A420@hub.freebsd.org> User-Agent: Mutt/1.5.11 Cc: freebsd-current@freebsd.org Subject: Re: Lasted NDIS wrapper for D-Link DWL-520+ on RELENG_6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2005 09:49:08 -0000 Hi Bill, > > Ok, these precisions have been indeed *very* precious, is it the > > first time you post them ? > > I didn't think I needed to, since the only skill one really needs > to figure this stuff out on their own is the ability to read. But I > guess it's too much to expect that people be able do that. It seems to be indeed, at least concerning myself. I'm volonteering to document this following your advices, do you know where it can be documented ? I would say this should live in the handbook, but there is no NDISulator article currently unfortunately. Does anyone know about an article being written ? > > Thank you very much for you help P^HBill ;-). > > Now look, dumbass. I thought I made it very clear that getting my > name wrong was not funny. As in not a laughing matter. As in not > something to be joked about. It seems in addition to being prone to > losing things and not being able to read, you're unable to grasp > this concept either. So let me make it clear to you: IT IS NOT A > FUCKING JOKE, YOU RAT BASTARD. And _NO_, a smiley face does not > make it ok! > > If you really want to thank me for my help, then do me the fucking > courtesy of not insulting me in the same breath. I am sorry for this, I would certainly not have made this joke if I have known you were so sensitive to it. I should have simply thank you for the work you have done so far, especially on the Project Evil. Best regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 09:53:09 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4CAF16A41F for ; Fri, 25 Nov 2005 09:53:09 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 71AFD43D73 for ; Fri, 25 Nov 2005 09:52:53 +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 smtp3-g19.free.fr (Postfix) with ESMTP id 917C337191; Fri, 25 Nov 2005 10:52:46 +0100 (CET) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 10B23405B; Fri, 25 Nov 2005 10:52:32 +0100 (CET) Date: Fri, 25 Nov 2005 10:52:32 +0100 From: Jeremie Le Hen To: David Barbero Message-ID: <20051125095231.GB1006@obiwan.tataz.chchile.org> References: <20051124112413.GA1006@obiwan.tataz.chchile.org> <20051124194235.E8CDB16A420@hub.freebsd.org> <20051125005357.GX1006@obiwan.tataz.chchile.org> <20051125010756.GZ1006@obiwan.tataz.chchile.org> <64084.80.38.105.187.1132911198.squirrel@webmail.loquefaltaba.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <64084.80.38.105.187.1132911198.squirrel@webmail.loquefaltaba.com> User-Agent: Mutt/1.5.11 Cc: current@freebsd.org Subject: Re: Lasted NDIS wrapper for D-Link DWL-520+ on RELENG_6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2005 09:53:10 -0000 Hi David, > This chipset is suported by acx100 driver, you can install and probe this > from ports net/acx100 o in URL: http://dev.kewl.org/acx100/ . Last time I checked it (there was not yet a port for it), it did support most of the ACX chip family, but ACX111 wasn't supported. After that, I checked Darron Broad's webcvs and I saw no new commit claiming this revision was indeed support. Furthermore, ISTR that I read this port does not compile on RELENG_6 due to changes on the ifnet structure and is only working on RELENG_5. Is it not true any longer ? I have no time in the next couple of hours, but I will give it a try ASAP. Thank you. Best regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org > From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 10:14:57 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F7E716A420 for ; Fri, 25 Nov 2005 10:14:57 +0000 (GMT) (envelope-from sico@loquefaltaba.com) Received: from mail.loquefaltaba.com (78.Red-213-96-97.staticIP.rima-tde.net [213.96.97.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id D43F043D5D for ; Fri, 25 Nov 2005 10:14:55 +0000 (GMT) (envelope-from sico@loquefaltaba.com) Received: from localhost (localhost.loquefaltaba.com [127.0.0.1]) by mail.loquefaltaba.com (Postfix) with ESMTP id 3D9F7C111; Fri, 25 Nov 2005 11:14:54 +0100 (CET) Received: from mail.loquefaltaba.com ([127.0.0.1]) by localhost (sico.loquefaltaba.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 68628-06; Fri, 25 Nov 2005 11:14:46 +0100 (CET) Received: from webmail.loquefaltaba.com (localhost.loquefaltaba.com [127.0.0.1]) by mail.loquefaltaba.com (Postfix) with ESMTP id 7AD49C0E0; Fri, 25 Nov 2005 11:14:46 +0100 (CET) Received: from 187.red-80-38-105.staticip.rima-tde.net ([80.38.105.187]) (SquirrelMail authenticated user sico) by webmail.loquefaltaba.com with HTTP; Fri, 25 Nov 2005 11:14:46 +0100 (CET) Message-ID: <62024.80.38.105.187.1132913686.squirrel@webmail.loquefaltaba.com> In-Reply-To: <20051125095231.GB1006@obiwan.tataz.chchile.org> References: <20051124112413.GA1006@obiwan.tataz.chchile.org> <20051124194235.E8CDB16A420@hub.freebsd.org> <20051125005357.GX1006@obiwan.tataz.chchile.org> <20051125010756.GZ1006@obiwan.tataz.chchile.org> <64084.80.38.105.187.1132911198.squirrel@webmail.loquefaltaba.com> <20051125095231.GB1006@obiwan.tataz.chchile.org> Date: Fri, 25 Nov 2005 11:14:46 +0100 (CET) From: "David Barbero" To: "Jeremie Le Hen" User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: amavisd-new at loquefaltaba.com Cc: current@freebsd.org Subject: Re: Lasted NDIS wrapper for D-Link DWL-520+ on RELENG_6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Nov 2005 10:14:57 -0000 Jeremie Le Hen wrote: > Last time I checked it (there was not yet a port for it), it did > support most of the ACX chip family, but ACX111 wasn't supported. > After that, I checked Darron Broad's webcvs and I saw no new > commit claiming this revision was indeed support. I see the problem now, this driver wasn't updated... In the original port of the driver for Linux this chipset are supported, but the work of Darron it's out of date, i don't see this when i send the last post... > Furthermore, ISTR that I read this port does not compile on RELENG_6 > due to changes on the ifnet structure and is only working on RELENG_5. > Is it not true any longer ? The last commit of Darron compile in the 6-current before the re@ announcement the 6.0-Release and the code don't updated for compile in 6-stable :( > I have no time in the next couple of hours, but I will give it a try > ASAP. Thank you. > > Best regards, PS: The original port of acx100 for Linux is http://acx100.sf.net Regards. -- "Linux is for people who hate Windows, BSD is for people who love UNIX" "Social Engineer -> Because there is no patch for human stupidity" From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 11:22:08 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A3C416A41F for ; Fri, 25 Nov 2005 11:22:08 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1429F43D45 for ; Fri, 25 Nov 2005 11:22:07 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id EE00146B90; Fri, 25 Nov 2005 06:22:06 -0500 (EST) Date: Fri, 25 Nov 2005 11:22:06 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Mayank Kumar In-Reply-To: <3A5384BC2FBA4C488865F2275A036BFF040B285D@APS-MSG-01.southpacific.corp.microsoft.com> Message-ID: <20051125111526.H81764@fledge.watson.org> References: <3A5384BC2FBA4C488865F2275A036BFF040B285D@APS-MSG-01.southpacific.corp.microsoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: RE: What is the correct behaviour for local socket(AF_UNIX) in the following scenario? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Nov 2005 11:22:08 -0000 On Fri, 25 Nov 2005, Mayank Kumar wrote: > From this I understand that if p1 closes the socket, then all the data > written by it is discarded since the buffers associated with this socket > no longer exists. > If that is the case, then this is not at all true that p1 can > write data on a socket and close it and exit and p2 will still be able > to retrieve the data written by p1. Does FreeBSD differ with solaris or > other unixes in this implementation. I believe that Solaris does support > the above scenario although I am not sure. Do you know How other unixes > behave here. Because it makes a lot of sense for localsockets to > facilitate IPC on a system by supporting the above scenario between two > processes. I imagine most UNIXes take a similar approach to UNIX domain sockets, at least for stream sockets, as the file system reference socket is a rendezvous point to create new socket pairs that have the same properties as sockets created using socketpair(). It's possible to imagine alternative behavior in the datagram case, but I don't know of any such implementations. There are several other message queue related facilities you may want to look at, which might provide more of the semantics you're looking for: - POSIX "named pipes", or fifos. Unlike with UNIX domain sockets, the file system name isn't simply a rendezvous using which communication instances can be created. However, I think they may get flushed on last close. - System V IPC message queues, which don't use the file system name space, but do have a notion of persisting beyond application reference. - David Xu is working to create a POSIX message queue implementation currently, so it will likely be available in the near future. Robert N M Watson > > Regards > Mayank > > -----Original Message----- > From: Robert Watson [mailto:rwatson@FreeBSD.org] > Sent: Friday, November 25, 2005 5:54 AM > To: Mayank Kumar > Cc: freebsd-current@freebsd.org > Subject: Re: What is the correct behaviour for local socket(AF_UNIX) in > the following scenario? > > > On Fri, 25 Nov 2005, Mayank Kumar wrote: > >> I am trying to understand the behavior of localsockets in the >> following scenario. >> >> A process p1 writes a huge amoount of data to a AF_UNIX,DGRAM socket >> and exits. Now if there is no process p2 to read the data written by >> process >> p1 from the same localsocket, then this has resulted in a huge memory >> leak on a FreeBSD system. >> >> I want to understand, if there is a mechanism in FreeBsd to take care >> of this leak or this is the expected behaviour and application writers > >> should take care of this situation. Also what should be the behaviour >> on such a socket if shutdown or close is issued on such a socket. Any >> help on the behaviour on other unixes in the same scenario would also >> help a lot. > > Mayank, > > The key to understanding how this is handled is to understand that UNIX > domain sockets aren't file system objects -- the file system simply > provides a name space by which to reach the socket. The buffers > associated with UNIX domain sockets belong to the sockets, not to the > name. You can think of this in the same way as you might think of port > numbers and IP addresses, although there are some subtle differences. > > There are two common operational modes for UNIX domain sockets: stream > mode, and datagram mode. In stream mode, a listen socket is bound to > the name, and then new socket pairs are generated when that name is > connected. > In datagram mode, a single socket exists on the "server" end, and then a > series of other sockets may send to it using sendto and send. The > buffers are associated with the active communication sockets in both > case, so if all endpoints are closed, the name persists, but has no > persisting buffers. So a name can be leaked (i.e., not be unlinked when > a process is done with it), which is similar to leaking a temporary file > that isn't unlinked. > > Hope this helps, > > Robert N M Watson > From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 12:02:37 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5822F16A41F for ; Fri, 25 Nov 2005 12:02:37 +0000 (GMT) (envelope-from jsmith@drexel.edu) Received: from smtp.mail.drexel.edu (pm1.irt.drexel.edu [144.118.29.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id E907243D60 for ; Fri, 25 Nov 2005 12:02:35 +0000 (GMT) (envelope-from jsmith@drexel.edu) Received: from smtp.mail.drexel.edu (localhost.localdomain [127.0.0.1]) by smtp.mail.drexel.edu (Postfix) with SMTP id 23B41225EA7 for ; Fri, 25 Nov 2005 07:02:33 -0500 (EST) Received: from vorpal.math.drexel.edu (vorpal.math.drexel.edu [129.25.6.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mail.drexel.edu (Postfix) with ESMTP id 13E01225EA1 for ; Fri, 25 Nov 2005 07:02:33 -0500 (EST) Received: from [IPv6:::1] (vorpal.math.drexel.edu [127.0.0.1]) by vorpal.math.drexel.edu (8.13.4/8.13.4) with ESMTP id jAPC2O2O014689 for ; Fri, 25 Nov 2005 07:02:24 -0500 Message-ID: <4386FD58.3080308@drexel.edu> Date: Fri, 25 Nov 2005 07:02:32 -0500 From: "Justin R. Smith" Organization: Drexel University User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051122) 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 Subject: A4Tech Wireless mouse wheel not detected X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Nov 2005 12:02:37 -0000 FreeBSD jsmith.org 6.0-STABLE FreeBSD 6.0-STABLE #0: Sun Nov 20 15:06:19 EST 2005 root@jsmith.org:/usr/obj/usr/src/sys/MYKERNEL i386 I have an A4 Tech wireless keyboard and mouse. Linux and windows both find it to be indistinguishable from a PS/2 and use the mouse wheel. The Stable FreeBSD doesn't respond to wheel events. sysmouse identifies it as a microsoft mouse (with no mouse wheel) but depressing the wheel generated middle-button event. Killing sysmoused and configuring the X server to access /dev/psm0 (with the Zaxismapping, etc) doesn't change anything. I think the problem lied in psm0 itself. Running xev show that no X events are generated when turning the mouse wheel. Any suggestions? From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 13:23:06 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04E4916A41F for ; Fri, 25 Nov 2005 13:23:06 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0BC543D6B for ; Fri, 25 Nov 2005 13:22:48 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id jAPDMS3v062244 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Nov 2005 16:22:29 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id jAPDMSRF062243; Fri, 25 Nov 2005 16:22:28 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Fri, 25 Nov 2005 16:22:28 +0300 From: Gleb Smirnoff To: Emil Mikulic Message-ID: <20051125132228.GN25711@cell.sick.ru> References: <20051125022040.GA9150@cs.rmit.edu.au> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="MAH+hnPXVZWQ5cD/" Content-Disposition: inline In-Reply-To: <20051125022040.GA9150@cs.rmit.edu.au> User-Agent: Mutt/1.5.6i Cc: freebsd-current@FreeBSD.org Subject: Re: bge driver autoneg failure and system-wide stalls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Nov 2005 13:23:06 -0000 --MAH+hnPXVZWQ5cD/ Content-Type: text/plain; charset=koi8-r Content-Disposition: inline On Fri, Nov 25, 2005 at 01:20:41PM +1100, Emil Mikulic wrote: E> I have a network port with bad wiring in the walls - a cable tester E> shows only wires 1,2,3 and 6 are actually connected. E> E> My solution is to patch directly into the switch, in which case the bge E> driver works just fine. However, the bad wiring exposes two problems E> with the bge driver in 7-CURRENT. From memory, I think these turned up E> in the 5.x line because I wasn't seeing either issue in 4.x E> E> The first problem is that, once ifconfig'd to an IP address, there will E> be periodic system-wide stalls. They generally last a little under a E> second and are incredibly annoying and can cause keypresses to be lost E> at the console. E> E> I instrumented the kernel and, as far as I can tell, once ifconfig'd, E> the following will happen in brgphy (mii module): E> E> Every second there is a call to brgphy_service() with cmd=MII_TICK. E> Every five seconds, this function will call brgphy_mii_phy_auto(). E> This function calls brgphy_loop(). E> E> In brgphy_loop(), there is a #if 0'd bit of code that device_printf()'s E> how many times it looped. I enabled it. E> E> Sometimes it reports zero loops - when this happens there is no stall. E> On a very pronounced stall, there will be between 3000-7000 loops. E> E> (i.e. the stalls appear a bit random because they only get a chance to E> happen once every five seconds, and sometimes brgphy_loop() doesn't E> result in a noticeable stall) E> E> The other problem is that bge will never negotiate a working link speed. E> ifconfig will always return "status: no carrier" E> E> If I force the media to 10baseT/UTP or 100baseTX (either mediaopt E> full-duplex or not), it will issue a couple more MII_TICKs then stop, E> ifconfig will return "status: active", there will be no more stalls, E> and, most importantly, the network connection will actually work. E> E> Is this fixable and actually worth fixing? Please try out the attached patch. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE --MAH+hnPXVZWQ5cD/ Content-Type: text/plain; charset=koi8-r Content-Disposition: attachment; filename="bge_link.patch" Index: sys/dev/bge/if_bge.c =================================================================== RCS file: /home/ncvs/src/sys/dev/bge/if_bge.c,v retrieving revision 1.91.2.4 diff -u -r1.91.2.4 if_bge.c --- sys/dev/bge/if_bge.c 9 Oct 2005 04:15:11 -0000 1.91.2.4 +++ sys/dev/bge/if_bge.c 22 Oct 2005 08:36:05 -0000 @@ -3026,24 +3094,20 @@ struct bge_softc *sc; { struct mii_data *mii = NULL; - struct ifmedia *ifm = NULL; struct ifnet *ifp; - ifp = sc->bge_ifp; - BGE_LOCK_ASSERT(sc); + ifp = sc->bge_ifp; + if (sc->bge_asicrev == BGE_ASICREV_BCM5705 || sc->bge_asicrev == BGE_ASICREV_BCM5750) bge_stats_update_regs(sc); else bge_stats_update(sc); callout_reset(&sc->bge_stat_ch, hz, bge_tick, sc); - if (sc->bge_link) - return; if (sc->bge_tbi) { - ifm = &sc->bge_ifmedia; if (CSR_READ_4(sc, BGE_MAC_STS) & BGE_MACSTAT_TBI_PCS_SYNCHED) { sc->bge_link++; @@ -3073,8 +3137,6 @@ if (!IFQ_DRV_IS_EMPTY(&ifp->if_snd)) bge_start_locked(ifp); } - - return; } static void --MAH+hnPXVZWQ5cD/-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 14:01:30 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A425D16A41F for ; Fri, 25 Nov 2005 14:01:30 +0000 (GMT) (envelope-from kbuild@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA76D43D5F for ; Fri, 25 Nov 2005 14:01:26 +0000 (GMT) (envelope-from kbuild@gmail.com) Received: by zproxy.gmail.com with SMTP id z31so487618nzd for ; Fri, 25 Nov 2005 06:01:26 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=SLAPu1idbDpC9EsBnRCJ9c4oCQjBrzPJozYO47SdV6Uv52rGBc+/hBOXwl59ifoC8HAlEx7gOauVFZ+MLokoQ/Y4Oz9vDwIKzr3WLUOwtm874Rn3o6haPWCo/6q4ez1ZGVocyj/Ckl0APutWREQNALUM1koB9c2c9wm2bckOTTA= Received: by 10.65.237.13 with SMTP id o13mr4614661qbr; Fri, 25 Nov 2005 06:01:25 -0800 (PST) Received: by 10.65.228.3 with HTTP; Fri, 25 Nov 2005 06:01:25 -0800 (PST) Message-ID: Date: Fri, 25 Nov 2005 22:01:25 +0800 From: Sun Le To: freebsd-current@freebsd.org In-Reply-To: MIME-Version: 1.0 References: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: meet up with a problem when doing the installation X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Nov 2005 14:01:30 -0000 Hi folks, Have you installed the 6.0 successfully with an usb mouse on the box? If you did,please tell me how to make it worked. -Sandy On 11/24/05, Sun Le wrote: > > Hi folks, > > I encountered a problem that need your help. > > The matter goes as follow: > My box is Dell DIMENSION 1100 using Dell USB keyboard and mouse.When I > installed the 6.0 release,I selected `boot with usb keyboard' option.With= that,my usb keyboard worked > well.Then I noticed that the usbd was been launched when the prompt > appeared,and after that,When I set up my mouse,there is no option or > protocols about the usb which can be selected.Moreover,of course,the mous= e > did not work.I hang on there. > > So,who can offer my some information that help me solve it? > > Many thanks in advance. > > Sandy > > > -- Sun Le (Sandy) - Keep it simple,stupid and low-key From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 14:33:07 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A4D9B16A41F; Fri, 25 Nov 2005 14:33:07 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id F377743D64; Fri, 25 Nov 2005 14:33:06 +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 1A2001FFAD1; Fri, 25 Nov 2005 15:33:06 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 6AC621FF931; Fri, 25 Nov 2005 15:33:03 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 0044B444F50; Fri, 25 Nov 2005 14:29:15 +0000 (UTC) Date: Fri, 25 Nov 2005 14:29:15 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Matthew Dillon In-Reply-To: <200511242329.jAONTEkr055790@apollo.backplane.com> Message-ID: <20051125142713.M23990@maildrop.int.zabbadoz.net> References: <200511231406.06282.jhb@freebsd.org> <200511242329.jAONTEkr055790@apollo.backplane.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: FreeBSD current mailing list Subject: Re: nve locking fixes round 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Nov 2005 14:33:07 -0000 On Thu, 24 Nov 2005, Matthew Dillon wrote: Hi, > :Ok, now that the first set of locking overhaul is in the tree, can folks with > :working nve(4) adapters test the patch referenced below and make sure there > :are no regressions. Having the IFF_UP fiddling turned off may or may not > :help folks getting the TX timeouts as well, btw, so if people are feeling > :brave they can try this patch as well. Note it is only applicable to recent > :current. > : > :http://www.FreeBSD.org/~jhb/patches/nve_locking.patch > : > :-- > :John Baldwin <>< http://www.FreeBSD.org/~jhb/ > :"Power Users Use the Power to Serve" = http://www.FreeBSD.org > > The reason I set sc->pending_txs to 0 in DFly after the reinit is > because when a watchdog timeout occurs and you reset the device, > *ALL* mbufs still sitting in the transmit ring are lost. They will > never be acknowledged, ever. So pending_txs will never drop back to 0 on > its own. This is what led to continuous watchdog timeout reports > when, in fact, only one timeout actually occured. the problem is that with some versions of the hardware you are not even able to get the first packet out. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 14:48:03 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F18C16A41F; Fri, 25 Nov 2005 14:48:03 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn.pobox.com (thorn.pobox.com [208.210.124.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F4D143D98; Fri, 25 Nov 2005 14:47:45 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn (localhost [127.0.0.1]) by thorn.pobox.com (Postfix) with ESMTP id 6240612C; Fri, 25 Nov 2005 09:48:06 -0500 (EST) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thorn.sasl.smtp.pobox.com (Postfix) with ESMTP id 1AF8458B; Fri, 25 Nov 2005 09:48:04 -0500 (EST) Received: from lists by mappit.local.linnet.org with local (Exim 4.54 (FreeBSD)) id 1EferU-000Pkh-NG; Fri, 25 Nov 2005 14:47:40 +0000 Date: Fri, 25 Nov 2005 14:47:40 +0000 From: Brian Candler To: Robert Watson Message-ID: <20051125144740.GB98953@uk.tiscali.com> References: <3A5384BC2FBA4C488865F2275A036BFF040B285D@APS-MSG-01.southpacific.corp.microsoft.com> <20051125111526.H81764@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051125111526.H81764@fledge.watson.org> User-Agent: Mutt/1.4.2.1i Cc: Mayank Kumar , freebsd-current@freebsd.org Subject: Re: What is the correct behaviour for local socket(AF_UNIX) in the following scenario? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Nov 2005 14:48:03 -0000 On Fri, Nov 25, 2005 at 11:22:06AM +0000, Robert Watson wrote: > There are several other message queue related facilities you may want to > look at, which might provide more of the semantics you're looking for: And an excellent source of information is the series of reference books by the late Richard Stevens and published by Addison Wesley, especially "Advanced Programming in the UNIX Environment" "Unix Network Programming (vol 1): The Sockets Networking API" "Unix Network Programming (vol 2): Interprocess Communications" They're not cheap, but they're a really good investment. Regards, Brian. From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 16:09:56 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E3BD16A423; Fri, 25 Nov 2005 16:09:56 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 043A543D5F; Fri, 25 Nov 2005 16:09:55 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.13.4/8.13.4) with ESMTP id jAPG9TKB059537; Fri, 25 Nov 2005 08:09:29 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.13.4/8.13.4/Submit) id jAPG9TRQ059536; Fri, 25 Nov 2005 08:09:29 -0800 (PST) Date: Fri, 25 Nov 2005 08:09:29 -0800 (PST) From: Matthew Dillon Message-Id: <200511251609.jAPG9TRQ059536@apollo.backplane.com> To: "Bjoern A. Zeeb" References: <200511231406.06282.jhb@freebsd.org> <200511242329.jAONTEkr055790@apollo.backplane.com> <20051125142713.M23990@maildrop.int.zabbadoz.net> Cc: FreeBSD current mailing list Subject: Re: nve locking fixes round 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Nov 2005 16:09:56 -0000 :... :> :> The reason I set sc->pending_txs to 0 in DFly after the reinit is :> because when a watchdog timeout occurs and you reset the device, :> *ALL* mbufs still sitting in the transmit ring are lost. They will :> never be acknowledged, ever. So pending_txs will never drop back to 0 on :> its own. This is what led to continuous watchdog timeout reports :> when, in fact, only one timeout actually occured. : :the problem is that with some versions of the hardware you are not :even able to get the first packet out. : :-- :Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT I'm not sure if its the same as what happened to me, but I believe I have observed this as well. But at least in my case it turned out to be a bug in (if_nv.c for DFly) that issued ABI calls before resetting the hardware. I think it had something to do with nv_stop() being called before the initial hardware reset and nv_stop() then making an ABI call or two that expected the hardware to already be in a sane state (when it wasn't). You'd have to look at the DFly commit to see for sure. -Matt Matthew Dillon From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 17:10:10 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9116C16A41F for ; Fri, 25 Nov 2005 17:10:10 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id C1F1F43D55 for ; Fri, 25 Nov 2005 17:10:09 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so1647437wxc for ; Fri, 25 Nov 2005 09:10:09 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=h0PVbg8d1sXQv+ZoR26pTRcqDY0YWpIZ1Op9UXmgsO8N49UIOkFSYnedRT/64UKTbSoLcUJt2LXdE3A5uWOVP9+fO0cDi8fJk5PkCCFxQeb6tijTWZ/sKAseme5Cca92/AocziPHQSz2B5E4CF8YVB7roSuJbHSFYY85PmKvOIo= Received: by 10.70.54.9 with SMTP id c9mr7755534wxa; Fri, 25 Nov 2005 09:03:43 -0800 (PST) Received: by 10.70.31.5 with HTTP; Fri, 25 Nov 2005 09:03:42 -0800 (PST) Message-ID: <790a9fff0511250903q931b66cte7a3e6555dc38f83@mail.gmail.com> Date: Fri, 25 Nov 2005 11:03:42 -0600 From: Scot Hetzel To: "Wojciech A. Koszek" In-Reply-To: <20051121162544.GB94958@freebsd.czest.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051121162544.GB94958@freebsd.czest.pl> Cc: freebsd-current@freebsd.org Subject: Re: Linking basesystem with additional libraries. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Nov 2005 17:10:10 -0000 On 11/21/05, Wojciech A. Koszek wrote: > Hello, > > Is there any reason why we couldn't have LDADD honored in "buildworld" > process? If there are no negative implications, I volunteer to do the > work. I'd find it really useful. > What do you want to link the base system with? Currently, the base sendmail can be linked with the security/cyrus-sasl* ports by setting: #=09SENDMAIL_CFLAGS=3D-I/usr/local/include -DSASL2 #=09SENDMAIL_LDFLAGS=3D-L/usr/local/lib #=09SENDMAIL_LDADD=3D-lsasl2 in /etc/make.conf. You could possibly link sendmail with one of the openldap ports also. Haven't tried it myself yet. Note: This may cause a busted sendmail, especially during a major version upgrade. A rebuild of the security/cyrus-sasl* port, and sendmail will fix it. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 20:04:04 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 188BE16A41F for ; Fri, 25 Nov 2005 20:04:04 +0000 (GMT) (envelope-from lofi@freebsd.org) Received: from mail-in-01.arcor-online.net (mail-in-01.arcor-online.net [151.189.21.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1392A43D58 for ; Fri, 25 Nov 2005 20:04:02 +0000 (GMT) (envelope-from lofi@freebsd.org) Received: from mail-in-01-z2.arcor-online.net (mail-in-01-z2.arcor-online.net [151.189.8.13]) by mail-in-01.arcor-online.net (Postfix) with ESMTP id CFF855E419; Fri, 25 Nov 2005 21:04:00 +0100 (CET) Received: from mail-in-02.arcor-online.net (mail-in-02.arcor-online.net [151.189.21.42]) by mail-in-01-z2.arcor-online.net (Postfix) with ESMTP id C5019AB4CC; Fri, 25 Nov 2005 21:04:00 +0100 (CET) Received: from lofi.dyndns.org (dslb-084-061-144-232.pools.arcor-ip.net [84.61.144.232]) by mail-in-02.arcor-online.net (Postfix) with ESMTP id 7E73982CA4; Fri, 25 Nov 2005 21:04:00 +0100 (CET) Received: from kiste.my.domain (root@kiste.my.domain [192.168.8.4]) by lofi.dyndns.org (8.13.4/8.13.3) with ESMTP id jAPK3wSI066420 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Nov 2005 21:03:58 +0100 (CET) (envelope-from lofi@freebsd.org) Received: from kiste.my.domain (lofi@localhost [127.0.0.1]) by kiste.my.domain (8.13.4/8.13.1) with ESMTP id jAPK3wd1047146; Fri, 25 Nov 2005 21:03:58 +0100 (CET) (envelope-from lofi@freebsd.org) Received: from localhost (localhost [[UNIX: localhost]]) by kiste.my.domain (8.13.4/8.13.1/Submit) id jAPK3vQO047145; Fri, 25 Nov 2005 21:03:57 +0100 (CET) (envelope-from lofi@freebsd.org) X-Authentication-Warning: kiste.my.domain: lofi set sender to lofi@freebsd.org using -f From: Michael Nottebrock To: freebsd-current@freebsd.org Date: Fri, 25 Nov 2005 21:03:49 +0100 User-Agent: KMail/1.8.3 References: <4386FD58.3080308@drexel.edu> In-Reply-To: <4386FD58.3080308@drexel.edu> X-Face: =Ym$`&q\+S2X$4`X%x%6"L4>Y,$]<":'L%c9"#7#`2tb&E&wsN31on!N\)3BD[g<=?utf-8?q?=2EjnfV=5B=0A=093=23?=>XchLK,o; >bD>c:]^; :>0>vyZ.X[,63GW`&M>}nYnr]-Fp``,[[@lJ!QL|sfW!s)=?utf-8?q?A2!*=0A=09vNkB/=7CL-?=>&QdSbQg X-Virus-Scanned: by amavisd-new Cc: "Justin R. Smith" Subject: Re: A4Tech Wireless mouse wheel not detected X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Nov 2005 20:04:04 -0000 --nextPart1797754.mDlrvCIWnC Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday, 25. November 2005 13:02, Justin R. Smith wrote: > I have an A4 Tech wireless keyboard and mouse. Linux and windows both > find it to be indistinguishable from a PS/2 and use the mouse wheel. The > Stable FreeBSD doesn't respond to wheel events. > > [...] > > Any suggestions? You need to run moused with the -z4 argument to activate axis mapping (put= =20 moused_flags=3D-z4 into /etc/rc.conf), but since you already tried in X and= =20 said it didn't work ... might be worth a try though, less opportunities for= =20 typos with moused compared to xorg.conf I myself use an A4 Tech Office 8K wireless mouse with moused, connected to = a=20 USB port however, and had to change the default usbd.conf line that runs=20 moused to include the axis mapping switch. =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart1797754.mDlrvCIWnC Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDh24tXhc68WspdLARAm8qAJsG48mxEiT7O1vS6MNtBeTEMrMiogCdFnjw KC8VH1+Z3hCklxk0ZrtlUNk= =FIOw -----END PGP SIGNATURE----- --nextPart1797754.mDlrvCIWnC-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 21:49:53 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C18616A41F for ; Fri, 25 Nov 2005 21:49:53 +0000 (GMT) (envelope-from csaba@beastie.creo.hu) Received: from beastie.creo.hu (www.creo.hu [217.113.62.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4315D43D58 for ; Fri, 25 Nov 2005 21:49:50 +0000 (GMT) (envelope-from csaba@beastie.creo.hu) Received: from beastie.creo.hu (localhost [127.0.0.1]) by beastie.creo.hu (8.13.3/8.13.3) with ESMTP id jAPLlc10027144 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 25 Nov 2005 22:47:38 +0100 (CET) (envelope-from csaba@beastie.creo.hu) Received: (from csaba@localhost) by beastie.creo.hu (8.13.3/8.13.3/Submit) id jAPLlcDF027143 for freebsd-current@freebsd.org; Fri, 25 Nov 2005 22:47:38 +0100 (CET) (envelope-from csaba) Date: Fri, 25 Nov 2005 22:47:38 +0100 From: Csaba Henk To: freebsd-current@freebsd.org Message-ID: <20051125214738.GL2911@beastie.creo.hu> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="sm4nu43k4a2Rpi4c" Content-Disposition: inline User-Agent: Mutt/1.5.9i Subject: double close strikes panic if md attaching a corrupt file X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Nov 2005 21:49:53 -0000 --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi! Imagine the following: You have a corrupt file (so that you can open it, but when you try reading from it, it returns EIO). Pretty common with crappy optical media. You try "mdconfig -a -t vnode" on it. This will lead to a call to xmdioctl() such that mdio->md_type is MD_VNODE. So you get the following call chain: xmdioctl -> mdcreate_vnode -> mdsetcred -> VOP_READ VOP_READ returns EIO. This error value will be propagated to mdcreate_vnode, who will then feel like vn_close-ing the vnode, and propagate the error further. Now we got back to xmdioctl, who will call for mddestroy because of the error. mddestroy still sees the vnode, and will vn_close it again. This will yield a "negative refcount" panic. Two different ideas for fixing this: 1. Don't vn_close in mdcreate_vnode when there is an error. 2. Not just vn_close in mdcreate_vnode upon error but also nullify the sc->vnode field. I attach two patches, they realize the above ideas, respectively. Note that I didn't test either. Regards, Csaba --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="md-doubleclose-1.diff" --- /sys/dev/md/md.c Sun Nov 13 10:43:06 2005 +++ - Fri Nov 25 22:42:29 2005 @@ -889,11 +889,7 @@ mdcreate_vnode(struct md_s *sc, struct m sc->vnode = nd.ni_vp; error = mdsetcred(sc, td->td_ucred); - if (error != 0) { - (void)vn_close(nd.ni_vp, flags, td->td_ucred, td); - return (error); - } - return (0); + return (error); } static int --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="md-doubleclose-2.diff" --- /sys/dev/md/md.c Sun Nov 13 10:43:06 2005 +++ - Fri Nov 25 22:41:40 2005 @@ -891,6 +891,7 @@ mdcreate_vnode(struct md_s *sc, struct m error = mdsetcred(sc, td->td_ucred); if (error != 0) { (void)vn_close(nd.ni_vp, flags, td->td_ucred, td); + sc->vnode = NULL; return (error); } return (0); --sm4nu43k4a2Rpi4c-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 25 23:00:03 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B30616A41F for ; Fri, 25 Nov 2005 23:00:03 +0000 (GMT) (envelope-from pckizer@nostrum.com) Received: from nostrum.com (magus.nostrum.com [69.5.195.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A8C443D53 for ; Fri, 25 Nov 2005 23:00:02 +0000 (GMT) (envelope-from pckizer@nostrum.com) Received: from [10.0.1.4] (dsl081-116-173.dfw1.dsl.speakeasy.net [64.81.116.173]) (authenticated bits=0) by nostrum.com (8.12.11/8.12.11) with ESMTP id jAPMxxGD050223 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Fri, 25 Nov 2005 17:00:00 -0600 (CST) (envelope-from pckizer@nostrum.com) Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <790a9fff0511250903q931b66cte7a3e6555dc38f83@mail.gmail.com> References: <20051121162544.GB94958@freebsd.czest.pl> <790a9fff0511250903q931b66cte7a3e6555dc38f83@mail.gmail.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <96C3189B-8FA3-4EA9-9BFC-C5800FF7766F@nostrum.com> Content-Transfer-Encoding: 7bit From: Philip Kizer Date: Fri, 25 Nov 2005 16:59:59 -0600 To: freebsd-current@freebsd.org X-Mailer: Apple Mail (2.746.2) Received-SPF: pass (nostrum.com: 64.81.116.173 is authenticated by a trusted mechanism) Subject: Re: Linking basesystem with additional libraries. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 25 Nov 2005 23:00:03 -0000 On Nov 25, 2005, at 11:03, Scot Hetzel wrote: > What do you want to link the base system with? > Currently, the base sendmail can be linked with the > security/cyrus-sasl* ports by setting: > [...elided...] > in /etc/make.conf. You could possibly link sendmail with one of the > openldap ports also. Haven't tried it myself yet. Just to confirm, I've been using these options in make.conf for a while: > SENDMAIL_CFLAGS=-I/usr/local/include/sasl -I/usr/local/include - > DSASL=2 -DLDAPMAP > SENDMAIL_LDFLAGS=-L/usr/local/lib > SENDMAIL_LDADD=-lsasl2 -lldap -llber -lcom_err > Note: This may cause a busted sendmail, especially during a major > version upgrade. A rebuild of the security/cyrus-sasl* port, and > sendmail will fix it. I can confirm it breaks the buildworld across a major update. I just did the obvious: . comment them out of make.conf . finish the make+install+reboot . reinstall the problem libraries (sasl2/ldap/etc) . uncomment them in make.conf . re-do just the sendmail pieces > cd /usr/src/lib/libsm ; make cleandir && make obj && make && make > install > cd /usr/src/usr.sbin/sendmail ; make cleandir && make obj && make > && make install -philip From owner-freebsd-current@FreeBSD.ORG Sat Nov 26 02:56:22 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BF2B16A41F for ; Sat, 26 Nov 2005 02:56:22 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00DCF43D5D for ; Sat, 26 Nov 2005 02:56:22 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id D67CB1A3C27; Fri, 25 Nov 2005 18:56:21 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id AA9525158D; Fri, 25 Nov 2005 21:56:20 -0500 (EST) Date: Fri, 25 Nov 2005 21:56:20 -0500 From: Kris Kennaway To: Csaba Henk Message-ID: <20051126025620.GA62284@xor.obsecurity.org> References: <20051125214738.GL2911@beastie.creo.hu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GvXjxJ+pjyke8COw" Content-Disposition: inline In-Reply-To: <20051125214738.GL2911@beastie.creo.hu> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: double close strikes panic if md attaching a corrupt file X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Nov 2005 02:56:22 -0000 --GvXjxJ+pjyke8COw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 25, 2005 at 10:47:38PM +0100, Csaba Henk wrote: > Hi! >=20 > Imagine the following: >=20 > You have a corrupt file (so that you can open it, but when you try reading > from it, it returns EIO). Pretty common with crappy optical media. >=20 > You try "mdconfig -a -t vnode" on it. >=20 > This will lead to a call to xmdioctl() such that mdio->md_type is=20 > MD_VNODE. So you get the following call chain: >=20 > xmdioctl -> mdcreate_vnode -> mdsetcred -> VOP_READ >=20 > VOP_READ returns EIO. This error value will be propagated to mdcreate_vno= de, > who will then feel like vn_close-ing the vnode, and propagate the error > further. >=20 > Now we got back to xmdioctl, who will call for mddestroy because of the e= rror. > mddestroy still sees the vnode, and will vn_close it again. >=20 > This will yield a "negative refcount" panic. >=20 > Two different ideas for fixing this: >=20 > 1. Don't vn_close in mdcreate_vnode when there is an error. > 2. Not just vn_close in mdcreate_vnode upon error but also > nullify the sc->vnode field. >=20 > I attach two patches, they realize the above ideas, respectively. > Note that I didn't test either. You probably should do so ;-) This isn't the easiest thing for someone to test without such corrupted media. Kris --GvXjxJ+pjyke8COw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDh87UWry0BWjoQKURAkLaAKD+8ZxrnxY45FFi3euFE5SMcNYy1QCeOoex txVeD1J4RBeKR7xW7Sh5+DM= =PrDQ -----END PGP SIGNATURE----- --GvXjxJ+pjyke8COw-- From owner-freebsd-current@FreeBSD.ORG Sat Nov 26 05:03:28 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B62516A41F for ; Sat, 26 Nov 2005 05:03:28 +0000 (GMT) (envelope-from julian@elischer.org) Received: from delight.idiom.com (outbound.idiom.com [216.240.47.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07DD143D5A for ; Sat, 26 Nov 2005 05:03:26 +0000 (GMT) (envelope-from julian@elischer.org) Received: from idiom.com (idiom.com [216.240.32.1]) by delight.idiom.com (Postfix) with ESMTP id C0C682253F2 for ; Fri, 25 Nov 2005 21:03:26 -0800 (PST) Received: from [192.168.2.5] (home.elischer.org [216.240.48.38]) by idiom.com (8.12.11/8.12.11) with ESMTP id jAQ53QZp038899 for ; Fri, 25 Nov 2005 21:03:26 -0800 (PST) (envelope-from julian@elischer.org) Message-ID: <4387EC9E.5040709@elischer.org> Date: Fri, 25 Nov 2005 21:03:26 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <002801c5f081$f01ff200$642a15ac@smiley> <4384F807.6050105@samsco.org> <14BE0E5B-F596-4CB2-8048-07FC275C089F@lassitu.de> <20051124071405.GA15743@pit.databus.com> In-Reply-To: <20051124071405.GA15743@pit.databus.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Nov 2005 05:03:28 -0000 So I haven't been paying too much attention to this thread and now suddenly I find that I may have a variant of this problem. I have been tasked with adding a 4 port intel (em) based card into a Dell 2850 based system. It is based on the intel E7525 chipset and running 4.11. I have noticed that this system has irq's in use from 16 down (Maybe in -current it may use higher) but that some interrupt counts seem to move together, as if they are wired to gether. I also have the problem that the system seems to get completely wedged sometimes as it seems to get into the em driver interupt routine and never get out again, or if it does get out it gets called right back in again. Can someone who was following this tell me if this is the same problem? I can get into the kernel debugger and it usually shows the amr interrupt handler, having been interrupted by the em driver, (and that interrupted by the keyboard interrupt handler for the KDB entry.) It seems that no matter how hard it tries or how often it is called the em driver is unable to clear this interrupt. Am I reading this correctly in that it seems to be the same problem as was being discussed here? From owner-freebsd-current@FreeBSD.ORG Sat Nov 26 05:50:02 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E631016A41F for ; Sat, 26 Nov 2005 05:50:02 +0000 (GMT) (envelope-from csaba@beastie.creo.hu) Received: from beastie.creo.hu (www.creo.hu [217.113.62.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4298443D58 for ; Sat, 26 Nov 2005 05:50:01 +0000 (GMT) (envelope-from csaba@beastie.creo.hu) Received: from beastie.creo.hu (localhost [127.0.0.1]) by beastie.creo.hu (8.13.3/8.13.3) with ESMTP id jAQ5lnYh035512 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Nov 2005 06:47:49 +0100 (CET) (envelope-from csaba@beastie.creo.hu) Received: (from csaba@localhost) by beastie.creo.hu (8.13.3/8.13.3/Submit) id jAQ5lmeC035511; Sat, 26 Nov 2005 06:47:48 +0100 (CET) (envelope-from csaba) Date: Sat, 26 Nov 2005 06:47:48 +0100 From: Csaba Henk To: Kris Kennaway Message-ID: <20051126054748.GM2911@beastie.creo.hu> References: <20051125214738.GL2911@beastie.creo.hu> <20051126025620.GA62284@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051126025620.GA62284@xor.obsecurity.org> User-Agent: Mutt/1.5.9i Cc: freebsd-current@freebsd.org Subject: Re: double close strikes panic if md attaching a corrupt file X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Nov 2005 05:50:03 -0000 On Fri, Nov 25, 2005 at 09:56:20PM -0500, Kris Kennaway wrote: > > I attach two patches, they realize the above ideas, respectively. > > Note that I didn't test either. > > You probably should do so ;-) This isn't the easiest thing for someone > to test without such corrupted media. Umm... I was hoping that someone in the list will suggest a way for easily creating corrupt files. As I don't have a corrupt media, either :) I picked this when Fuse was panicking upon md attaching from a Fuse based filesystem, cf. http://lists.freebsd.org/pipermail/freebsd-ports/2005-November/027724.html The fuse module didn't implement VOP_READ (it rather used a file level "fo_read" method), hence from the point of the md code all files under a Fuse filesystem seem corrupt. So this was triggered. (Since then I added the VOP_READ, btw.) If I test the proposed fixes with a VOP_READ-less fuse module and they will save me from the panic (and work well on traditional fs-es), will you say it's OK? The fuse module lacks a proper audit from "serious" people, so you could dismiss it as well, saying you can't be sure that the problem is not with Fuse... Btw, if you said yes, that means you can as well easily get at a fine "corrupt media" :) Csaba From owner-freebsd-current@FreeBSD.ORG Sat Nov 26 10:31:06 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0735216A420 for ; Sat, 26 Nov 2005 10:31:06 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from geri.cc.fer.hr (geri.cc.fer.hr [161.53.72.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F9BB43D53 for ; Sat, 26 Nov 2005 10:31:03 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from geri.cc.fer.hr (localhost.cc.fer.hr [127.0.0.1]) by geri.cc.fer.hr (8.13.4/8.13.1) with ESMTP id jAQAUo9e024862 for ; Sat, 26 Nov 2005 11:30:50 +0100 (CET) (envelope-from ivoras@fer.hr) Received: from localhost (ivoras@localhost) by geri.cc.fer.hr (8.13.4/8.13.1/Submit) with ESMTP id jAQAUnmg024859 for ; Sat, 26 Nov 2005 11:30:50 +0100 (CET) (envelope-from ivoras@fer.hr) X-Authentication-Warning: geri.cc.fer.hr: ivoras owned process doing -bs Date: Sat, 26 Nov 2005 11:30:49 +0100 (CET) From: Ivan Voras Sender: ivoras@geri.cc.fer.hr To: current@freebsd.org Message-ID: <20051126112818.E24836@geri.cc.fer.hr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: Re: double close strikes panic if md attaching a corrupt file X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Nov 2005 10:31:06 -0000 Kris Kennaway wrote: > You probably should do so ;-) This isn't the easiest thing for someone > to test without such corrupted media. Maybe gnop GEOM class would help here? (the "-f" option) From owner-freebsd-current@FreeBSD.ORG Sat Nov 26 12:43:37 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9674316A41F for ; Sat, 26 Nov 2005 12:43:37 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6C4043D60 for ; Sat, 26 Nov 2005 12:43:36 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 3A72E46B91; Sat, 26 Nov 2005 07:43:36 -0500 (EST) Date: Sat, 26 Nov 2005 12:43:36 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Csaba Henk In-Reply-To: <20051126054748.GM2911@beastie.creo.hu> Message-ID: <20051126124248.L81764@fledge.watson.org> References: <20051125214738.GL2911@beastie.creo.hu> <20051126025620.GA62284@xor.obsecurity.org> <20051126054748.GM2911@beastie.creo.hu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org, Kris Kennaway Subject: Re: double close strikes panic if md attaching a corrupt file X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Nov 2005 12:43:37 -0000 On Sat, 26 Nov 2005, Csaba Henk wrote: > On Fri, Nov 25, 2005 at 09:56:20PM -0500, Kris Kennaway wrote: >>> I attach two patches, they realize the above ideas, respectively. >>> Note that I didn't test either. >> >> You probably should do so ;-) This isn't the easiest thing for someone >> to test without such corrupted media. > > Umm... I was hoping that someone in the list will suggest a way for > easily creating corrupt files. As I don't have a corrupt media, either > :) > > I picked this when Fuse was panicking upon md attaching from a Fuse > based filesystem, cf. > > http://lists.freebsd.org/pipermail/freebsd-ports/2005-November/027724.html Well, a very easy way to test would be to add a local modification to UFS to create a file flag that causes VOP_READ to return EIO :-). That way you can easily mark files to return EIO. Robert N M Watson From owner-freebsd-current@FreeBSD.ORG Sat Nov 26 13:30:11 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17D7716A41F; Sat, 26 Nov 2005 13:30:11 +0000 (GMT) (envelope-from jsmith@drexel.edu) Received: from smtp.mail.drexel.edu (pm1.irt.drexel.edu [144.118.29.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C9E343D62; Sat, 26 Nov 2005 13:30:06 +0000 (GMT) (envelope-from jsmith@drexel.edu) Received: from smtp.mail.drexel.edu (localhost.localdomain [127.0.0.1]) by smtp.mail.drexel.edu (Postfix) with SMTP id 3851D225E08; Sat, 26 Nov 2005 08:30:03 -0500 (EST) Received: from vorpal.math.drexel.edu (vorpal.math.drexel.edu [129.25.6.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mail.drexel.edu (Postfix) with ESMTP id 22A6A225DF4; Sat, 26 Nov 2005 08:30:03 -0500 (EST) Received: from [IPv6:::1] (vorpal.math.drexel.edu [127.0.0.1]) by vorpal.math.drexel.edu (8.13.4/8.13.4) with ESMTP id jAQ5240I015175; Sat, 26 Nov 2005 00:02:03 -0500 Message-ID: <43885AC1.2060908@drexel.edu> Date: Sat, 26 Nov 2005 07:53:21 -0500 From: "Justin R. Smith" Organization: Drexel University User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051122) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Nottebrock References: <4386FD58.3080308@drexel.edu> <200511252103.57059.lofi@freebsd.org> In-Reply-To: <200511252103.57059.lofi@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: A4Tech Wireless mouse wheel not detected X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Nov 2005 13:30:11 -0000 Michael Nottebrock wrote: > >You need to run moused with the -z4 argument to activate axis mapping (put >moused_flags=-z4 into /etc/rc.conf), but since you already tried in X and >said it didn't work ... might be worth a try though, less opportunities for >typos with moused compared to xorg.conf > >I myself use an A4 Tech Office 8K wireless mouse with moused, connected to a >USB port however, and had to change the default usbd.conf line that runs >moused to include the axis mapping switch. > > > Thank you1 I've tried this and nothing changes. I get the impression that the events are not being picked up at the /dev/psm0 level. After trying this, I changed my xorg.conf file and replaced /dev/sysmouse by /dev/psm0 (bypassing moused completely). X worked but the wheel didn't. If I find the time, I'll look at the psm driver myself. It looks as though it takes some special actions with A4Tech mice and the solution might be to force it to regard them as generic PS/2 mice... From owner-freebsd-current@FreeBSD.ORG Sat Nov 26 13:35:27 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0465316A420; Sat, 26 Nov 2005 13:35:27 +0000 (GMT) (envelope-from jsmith@drexel.edu) Received: from smtp.mail.drexel.edu (pm2.irt.drexel.edu [144.118.29.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id D485643D64; Sat, 26 Nov 2005 13:35:16 +0000 (GMT) (envelope-from jsmith@drexel.edu) Received: from smtp.mail.drexel.edu (localhost.localdomain [127.0.0.1]) by smtp.mail.drexel.edu (Postfix) with SMTP id 6AB561165E4; Sat, 26 Nov 2005 08:35:15 -0500 (EST) Received: from vorpal.math.drexel.edu (vorpal.math.drexel.edu [129.25.6.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mail.drexel.edu (Postfix) with ESMTP id 4B7B6116669; Sat, 26 Nov 2005 08:35:15 -0500 (EST) Received: from [IPv6:::1] (vorpal.math.drexel.edu [127.0.0.1]) by vorpal.math.drexel.edu (8.13.4/8.13.4) with ESMTP id jAQDZE1g008676; Sat, 26 Nov 2005 08:35:14 -0500 Message-ID: <43886492.20702@drexel.edu> Date: Sat, 26 Nov 2005 08:35:14 -0500 From: "Justin R. Smith" Organization: Drexel University User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051122) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Nottebrock References: <4386FD58.3080308@drexel.edu> <200511252103.57059.lofi@freebsd.org> In-Reply-To: <200511252103.57059.lofi@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: A4Tech Wireless mouse wheel not detected X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Nov 2005 13:35:27 -0000 Michael Nottebrock wrote: > >You need to run moused with the -z4 argument to activate axis mapping (put >moused_flags=-z4 into /etc/rc.conf), but since you already tried in X and >said it didn't work ... might be worth a try though, less opportunities for >typos with moused compared to xorg.conf > >I myself use an A4 Tech Office 8K wireless mouse with moused, connected to a >USB port however, and had to change the default usbd.conf line that runs >moused to include the axis mapping switch. > > > Thank you1 I've tried this and nothing changes. I get the impression that the events are not being picked up at the /dev/psm0 level. After trying this, I changed my xorg.conf file and replaced /dev/sysmouse by /dev/psm0 (bypassing moused completely). X worked but the wheel didn't. If I find the time, I'll look at the psm driver myself. It looks as though it takes some special actions with A4Tech mice and the solution might be to force it to regard them as generic PS/2 mice... From owner-freebsd-current@FreeBSD.ORG Sat Nov 26 22:37:00 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AA9216A420 for ; Sat, 26 Nov 2005 22:37:00 +0000 (GMT) (envelope-from jsmith@drexel.edu) Received: from smtp.mail.drexel.edu (pm2.irt.drexel.edu [144.118.29.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F56343D5F for ; Sat, 26 Nov 2005 22:36:50 +0000 (GMT) (envelope-from jsmith@drexel.edu) Received: from smtp.mail.drexel.edu (localhost.localdomain [127.0.0.1]) by smtp.mail.drexel.edu (Postfix) with SMTP id 099C211666A for ; Sat, 26 Nov 2005 17:36:39 -0500 (EST) Received: from vorpal.math.drexel.edu (vorpal.math.drexel.edu [129.25.6.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mail.drexel.edu (Postfix) with ESMTP id E490F11664D for ; Sat, 26 Nov 2005 17:36:38 -0500 (EST) Received: from [IPv6:::1] (vorpal.math.drexel.edu [127.0.0.1]) by vorpal.math.drexel.edu (8.13.4/8.13.4) with ESMTP id jAQMabkI008788 for ; Sat, 26 Nov 2005 17:36:37 -0500 Message-ID: <4388E376.5010605@drexel.edu> Date: Sat, 26 Nov 2005 17:36:38 -0500 From: "Justin R. Smith" Organization: Drexel University User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051122) 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 Subject: A4Tech mouse problem solved (but strangely!) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 26 Nov 2005 22:37:00 -0000 I had a problem with the mouse wheel being detected on my wireless A4Tech mouse. It is supposed to emulate a generic Intellimouse. The solution is to run moused with NO type parameter. A parameter of "auto" or "ps/2" or "microsoft" won't work. You must have a command line of: /usr/sbin/moused -p /dev/psm0 (with NO -t parameter) Unfortunately, one cannot use the automatic scripts in rc.conf to do this because they always use a parameter and fill in "microsoft" if one leaves the mouse type blank. Therefore, one must 1. disable moused in rc.conf 2. Set up a local script in /usr/local/etc/rc.d to run moused with the proper command-line.