From owner-freebsd-current@FreeBSD.ORG Sun Jan 20 03:13:55 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0BF7216A469; Sun, 20 Jan 2008 03:13:55 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from frontmail.ipactive.de (frontmail.maindns.de [85.214.95.103]) by mx1.freebsd.org (Postfix) with ESMTP id 765D413C478; Sun, 20 Jan 2008 03:13:53 +0000 (UTC) (envelope-from volker@vwsoft.com) Received: from mail.vtec.ipme.de (Q7cf2.q.ppp-pool.de [89.53.124.242]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by frontmail.ipactive.de (Postfix) with ESMTP id 6C40112883F; Sun, 20 Jan 2008 04:13:45 +0100 (CET) Received: from cesar.sz.vwsoft.com (unknown [192.168.18.33]) by mail.vtec.ipme.de (Postfix) with ESMTP id B19183F43B; Sun, 20 Jan 2008 04:12:27 +0100 (CET) Message-ID: <4792BC5E.4030703@vwsoft.com> Date: Sun, 20 Jan 2008 04:13:34 +0100 From: Volker User-Agent: Thunderbird 2.0.0.9 (X11/20080113) MIME-Version: 1.0 To: FreeBSD Stable X-Enigmail-Version: 0.95.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit MailScanner-NULL-Check: 1201403551.55055@iX4yPSzDpUr6NHYVDXgR8A X-VWSoft-MailScanner: Found to be clean X-MailScanner-From: volker@vwsoft.com X-ipactive-MailScanner-Information: Please contact the ISP for more information X-ipactive-MailScanner: Found to be clean X-ipactive-MailScanner-From: volker@vwsoft.com Cc: FreeBSD current , cokane@freebsd.org Subject: patch for review: ATI SB600 SATA AHCI X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 03:13:55 -0000 Hi! I've done the following local changes to get the ATA controller being correctly detected and initialized as an AHCI controller on an HP 6715b notebook using ATI SB-600 chipset. With stock kernel, the ATA controller is being recognized as a generic ATA controller and devices being driven in UDMA-33 mode. With the following patch, the controller is being initialized in AHCI mode and devices being set to SATA-150/300 mode. atapci0: port 0x9000-0x9007,0x9008-0x900b,0x9010-0x9017,0x5018-0x501b,0x5020-0x502f mem 0xd0609000-0xd06093ff irq 16 at device 18.0 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x5020 atapci0: Reserved 0x400 bytes for rid 0x24 type 3 at 0xd0609000 atapci0: [MPSAFE] atapci0: [ITHREAD] atapci0: AHCI Version 01.10 controller with 4 ports detected %atacontrol mode ad4 current mode = SATA150 My patch has been tested on RELENG_7 as of 2008-01-19. Please review, check and test if possible. Should work on 8-CURRENT, too. If nobody complains until tuesday (2008-01-22), I'll file a PR for that patch. Volker --- sys/dev/ata/ata-chipset.c.orig 2008-01-20 03:22:37.000000000 +0100 +++ sys/dev/ata/ata-chipset.c 2008-01-20 03:30:03.000000000 +0100 @@ -1348,6 +1348,7 @@ { ATA_ATI_IXP400_S1, 0x00, SIIMEMIO, 0, ATA_SA150, "IXP400" }, { ATA_ATI_IXP400_S2, 0x00, SIIMEMIO, 0, ATA_SA150, "IXP400" }, { ATA_ATI_IXP600, 0x00, 0, 0, ATA_UDMA6, "IXP600" }, + { ATA_ATI_IXP600_S1, 0x00, 0, AHCI, ATA_SA300, "IXP600" }, { ATA_ATI_IXP700, 0x00, 0, 0, ATA_UDMA6, "IXP700" }, { 0, 0, 0, 0, 0, 0}}; @@ -1360,7 +1361,10 @@ if (ctlr->chip->cfg1 & SIIMEMIO) ctlr->chipinit = ata_sii_chipinit; else - ctlr->chipinit = ata_ati_chipinit; + if (ctlr->chip->cfg2 & AHCI) + ctlr->chipinit = ata_ahci_chipinit; + else + ctlr->chipinit = ata_ati_chipinit; return 0; } --- sys/dev/ata/ata-pci.h.orig 2008-01-20 03:22:28.000000000 +0100 +++ sys/dev/ata/ata-pci.h 2008-01-20 03:23:56.000000000 +0100 @@ -104,6 +104,7 @@ #define ATA_ATI_IXP400_S1 0x43791002 #define ATA_ATI_IXP400_S2 0x437a1002 #define ATA_ATI_IXP600 0x438c1002 +#define ATA_ATI_IXP600_S1 0x43801002 #define ATA_ATI_IXP700 0x439c1002 #define ATA_CENATEK_ID 0x16ca From owner-freebsd-current@FreeBSD.ORG Sun Jan 20 03:42:45 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BEB8316A41A for ; Sun, 20 Jan 2008 03:42:45 +0000 (UTC) (envelope-from pawel.worach@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170]) by mx1.freebsd.org (Postfix) with ESMTP id 1AE8213C459 for ; Sun, 20 Jan 2008 03:42:44 +0000 (UTC) (envelope-from pawel.worach@gmail.com) Received: by ug-out-1314.google.com with SMTP id y2so903469uge.37 for ; Sat, 19 Jan 2008 19:42:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; bh=cUbKGfHLi4WNeilUetMWcxexV02n3wJw7AKXQqfWXrc=; b=sSv9vt9/Lq96WaUghftqd3pVxFzNVY68ULIlx6zMq60V+9/Q9LfPqVgqdIAD5xj9AVwFRMuH+7qcX5dZz9K41DFEpntNJv+1lyTqELLNeJVmnoeTB59SwA1y0Waa2k9Ix7cjTkxEi/ajGV71gInBlIzIewvvnaXJ+VaGP/WiXBs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=TL26YSE7ItokQ0PVzfT1ZAmULWTTyqfycakgXX+omXANwsp4csreOvZXKEvaU1TMqRv5dPLs1KOPBuY8I22vIxmlAUvBMCJOxgjt2sX68379XYAxVgloChIt32DUW0/agBRURnSQw6s3PxnIzxfcX/xJbvmYG2mIOiytjZ1Hz2s= Received: by 10.67.115.17 with SMTP id s17mr2716322ugm.56.1200800563828; Sat, 19 Jan 2008 19:42:43 -0800 (PST) Received: from ?192.168.10.200? ( [80.216.221.6]) by mx.google.com with ESMTPS id d24sm2147422nfh.19.2008.01.19.19.42.42 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 19 Jan 2008 19:42:42 -0800 (PST) Message-ID: <4792C32C.5010205@gmail.com> Date: Sun, 20 Jan 2008 04:42:36 +0100 From: Pawel Worach User-Agent: Thunderbird 2.0.0.9 (X11/20080119) MIME-Version: 1.0 To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: page fault panic in scioctl and console-kit-daemon X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 03:42:45 -0000 Hi, While starting console-kit-daemon (sysutils/consolekit 0.2.3) during boot or in single-user mode the system panics. If I start it post-boot it runs fine. This is on 8.0-CURRENT from about 12 hours ago, another user also reported the same on RELENG_7. Any other information I can provide ? Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x20:0xc04d2ab4 stack pointer = 0x28:0xe6499b18 frame pointer = 0x28:0xe6499b80 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 = 134 (console-kit-daemon) Physical memory: 1014 MB Dumping 43 MB: 28 12 #0 doadump () at pcpu.h:195 195 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:195 #1 0xc0461c69 in db_fncall (dummy1=1, dummy2=0, dummy3=-1064824544, dummy4=0xe64998b0 "\200�\233�") at /usr/src/sys/ddb/db_command.c:514 #2 0xc046221a in db_command (last_cmdp=0xc084eaf4, cmd_table=0x0, dopager=1) at /usr/src/sys/ddb/db_command.c:411 #3 0xc0462335 in db_command_loop () at /usr/src/sys/ddb/db_command.c:464 #4 0xc0463e1c in db_trap (type=12, code=0) at /usr/src/sys/ddb/db_main.c:228 #5 0xc0577aa3 in kdb_trap (type=12, code=0, tf=0xe6499ad8) at /usr/src/sys/kern/subr_kdb.c:510 #6 0xc07a280f in trap_fatal (frame=0xe6499ad8, eva=4) at /usr/src/sys/i386/i386/trap.c:889 #7 0xc07a2abb in trap_pfault (frame=0xe6499ad8, usermode=0, eva=4) at /usr/src/sys/i386/i386/trap.c:811 #8 0xc07a34a2 in trap (frame=0xe6499ad8) at /usr/src/sys/i386/i386/trap.c:489 #9 0xc079183b in calltrap () at /usr/src/sys/i386/i386/exception.s:146 #10 0xc04d2ab4 in scioctl (dev=0xc3b20d00, cmd=537163270, data=0xe6499c70 "\002", flag=1, td=0xc3d3c880) at /usr/src/sys/dev/syscons/syscons.c:1073 #11 0xc051ed1a in giant_ioctl (dev=0xc3b20d00, cmd=537163270, data=0xe6499c70 "\002", fflag=1, td=0xc3d3c880) at /usr/src/sys/kern/kern_conf.c:349 #12 0xc0598194 in cnioctl (dev=0xc3b20d00, cmd=537163270, data=0xe6499c70 "\002", flag=1, td=0xc3d3c880) ---Type to continue, or q to quit--- at /usr/src/sys/kern/tty_cons.c:521 #13 0xc051ed1a in giant_ioctl (dev=0xc39bf900, cmd=537163270, data=0xe6499c70 "\002", fflag=1, td=0xc3d3c880) at /usr/src/sys/kern/kern_conf.c:349 #14 0xc04f1127 in devfs_ioctl_f (fp=0xc3ce0dd0, com=537163270, data=0xe6499c70, cred=0xc39a0900, td=0xc3d3c880) at /usr/src/sys/fs/devfs/devfs_vnops.c:494 #15 0xc05845f8 in kern_ioctl (td=0xc3d3c880, fd=9, com=537163270, data=0xe6499c70 "\002") at file.h:254 #16 0xc058476f in ioctl (td=0xc3d3c880, uap=0xe6499cfc) at /usr/src/sys/kern/sys_generic.c:677 #17 0xc07a2e25 in syscall (frame=0xe6499d38) at /usr/src/sys/i386/i386/trap.c:1034 #18 0xc07918a0 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:203 #19 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) f 10 #10 0xc04d2ab4 in scioctl (dev=0xc3b20d00, cmd=537163270, data=0xe6499c70 "\002", flag=1, td=0xc3d3c880) at /usr/src/sys/dev/syscons/syscons.c:1073 1073 scp = sc_get_stat(SC_DEV(sc, i)); (kgdb) p sc $1 = (sc_softc_t *) 0xc0881120 (kgdb) p *sc $2 = {unit = 0, config = 768, flags = 65536, keyboard = 1, kbd = 0xc39fd800, adapter = 0, adp = 0xc087c3e0, initial_mode = 24, first_vty = 0, vtys = 16, dev = 0xc0862320, cur_scp = 0xc08621e0, new_scp = 0x0, old_scp = 0x0, delayed_next_scr = 0, font_loading_in_progress = 0 '\0', switch_in_progress = 0 '\0', write_in_progress = 0 '\0', blink_in_progress = 0 '\0', video_mtx = {lock_object = { lo_name = 0xc07dc198 "syscons video lock", lo_type = 0xc07dc198 "syscons video lock", lo_flags = 196608, lo_witness_data = {lod_list = {stqe_next = 0x0}, lod_witness = 0x0}}, mtx_lock = 4, mtx_recurse = 0}, scrn_time_stamp = 459, dflt_curs_attr = { flags = 0, base = 3, height = 2}, curs_attr = {flags = 0, base = 3, height = 2}, scr_map = "\000\001\002\003\004\005\006\a\b\t\n\v\f\r\016\017\020\021\022\023\024\025\026\027\030\031\032\033\034\035\036\037 !\"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`abcdefghijklmnopqrstuvwxyz{|}~\177\200\201\202\203\204\205\206\207\210\211\212\213\214\215\216\217\220\221\222\223\224\225\226\227\230\231\232\233\234\235\236\237����������������������������������������"..., scr_rmap = "\000\001\002\003\004\005\006\a\b\t\n\v\f\r\016\017\020\021\022\023\024\025\026\027\030\031\032\033\034\035\036\037 !\"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`abcdefghijklmnopqrstuvwxyz{|}~\177\200\201\202\203\204\205\206\207\210\211\212\213\214\215\216\217\220\221\222\223\224\225\226\227\230\231\232\233\234\235\236\237����������������������������������������"...---Type to continue, or q to quit--- , palette = "\000\000\000\000\000�\000�\000\000���\000\000�\000���\000���\000\000T\000\000�\000�T\000���\000T�\000���T���\000T\000\000T�\000�\000\000���T\000�T���\000���\000TT\000T�\000�T\000���TT�T���T���T\000\000T\000�T�\000T���\000\000�\000���\000���T\000TT\000�T�TT���\000T�\000���T���TT\000TT�T�\000T���T\000�T���\000���TTTTT�T�TT���TT�T���Tʏ 33;��", '\0' ..., fonts_loaded = 8, font_8 = 0xc0852f60 "", font_14 = 0xc0852160 "", font_16 = 0xc0851160 "", font_22 = 0x0, cursor_char = 7 '\a', mouse_char = 208 '�'} (kgdb) list 1068 s = spltty(); 1069 error = sc_clean_up(sc->cur_scp); 1070 splx(s); 1071 if (error) 1072 return error; 1073 scp = sc_get_stat(SC_DEV(sc, i)); 1074 if (scp == scp->sc->cur_scp) 1075 return 0; 1076 error = tsleep(&scp->smode, PZERO | PCATCH, "waitvt", 0); 1077 return error; (kgdb) p i $3 = 1 (kgdb) p sc->dev $4 = (struct cdev **) 0xc0862320 (kgdb) p *sc->dev $5 = (struct cdev *) 0xc3b20700 (kgdb) p **sc->dev $6 = {si_priv = 0xc3b20700, si_flags = 4, si_atime = {tv_sec = 0, tv_nsec = 0}, si_ctime = {tv_sec = 0, tv_nsec = 0}, si_mtime = { tv_sec = 0, tv_nsec = 0}, si_uid = 0, si_gid = 0, si_mode = 384, si_cred = 0x0, si_drv0 = 0, si_refcount = 1, si_list = {le_next = 0x0, le_prev = 0xc3b20638}, si_clone = {le_next = 0x0, le_prev = 0x0}, si_children = {lh_first = 0x0}, si_siblings = {le_next = 0x0, le_prev = 0x0}, si_parent = 0x0, si_name = 0xc3b20778 "ttyv0", si_drv1 = 0xc08621e0, si_drv2 = 0x0, si_devsw = 0xc0815320, si_iosize_max = 0, si_usecount = 0, si_threadcount = 0, __si_u = { __sit_tty = 0xc3b2a400, __sid_snapdata = 0xc3b2a400}, __si_namebuf = "ttyv0", '\0' } (kgdb) p sc->first_vty $7 = 0 -- Pawel From owner-freebsd-current@FreeBSD.ORG Sun Jan 20 14:15:40 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3F6816A41B for ; Sun, 20 Jan 2008 14:15:40 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: from mail.0x20.net (mail.ipv6.0x20.net [IPv6:2001:aa8:fffb::3]) by mx1.freebsd.org (Postfix) with ESMTP id 67EE013C45D for ; Sun, 20 Jan 2008 14:15:40 +0000 (UTC) (envelope-from lars@e.0x20.net) Received: by mail.0x20.net (Postfix, from userid 1002) id EBEC13A5CD; Sun, 20 Jan 2008 15:15:38 +0100 (CET) Date: Sun, 20 Jan 2008 15:15:38 +0100 From: Lars Engels To: current@freebsd.org Message-ID: <20080120141538.GH47164@e.0x20.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fU0UwhtRbpo05rnG" Content-Disposition: inline X-Editor: VIM - Vi IMproved 7.1 X-Operation-System: FreeBSD 5.5-RELEASE User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: Subject: sysutils/hal causes ath device timeout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Lars Engels 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 Jan 2008 14:15:40 -0000 --fU0UwhtRbpo05rnG Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Hi all, I don't know if mobile@, ports@ or current@ is the right list to report this so I will give it a try here. The hal daemon causes a timeout of my ath-driven Netgear WAG511 PC-Card. As soon as hald is started, the wireless connection is lost and I get this kernel message: ath0: device timeout ath0: ath_reset: unable to reset hardware; hal status 3230239248 When I eject the card then, the machine reboots. Environment: FreeBSD 8.0-CURRENT #0: Mon Jan 14 22:37:27 CET 2008 lars@maggie.bsd-geek.de:/usr/obj/usr/src/sys/MAGGIE i386 dmesg: ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) ath0: mem 0x88000000-0x8800ffff irq 20 at device 0.0 on cardbus0 ath0: [ITHREAD] ath0: using obsoleted if_watchdog interface ath0: Ethernet address: 00:0f:b5:9a:47:47 ath0: mac 5.9 phy 4.3 radio 3.6 lars@ttyp3 > pkginfo hal hal-0.5.8.20071224 sysctl: hw.ath.hal.swba_backoff: 0 hw.ath.hal.sw_brt: 10 hw.ath.hal.dma_brt: 2 hw.ath.hal.version: 0.9.20.3 hw.ath.txbuf: 200 hw.ath.rxbuf: 40 hw.ath.regdomain: 0 hw.ath.countrycode: 0 hw.ath.xchanmode: 1 hw.ath.outdoor: 1 hw.ath.calibrate: 30 dev.ath.0.%desc: Atheros 5212 dev.ath.0.%driver: ath dev.ath.0.%location: slot=0 function=0 dev.ath.0.%pnpinfo: vendor=0x168c device=0x0013 subvendor=0x1385 subdevice=0x4610 class=0x020000 dev.ath.0.%parent: cardbus0 dev.ath.0.smoothing_rate: 95 dev.ath.0.sample_rate: 10 dev.ath.0.countrycode: 0 dev.ath.0.regdomain: 0 dev.ath.0.slottime: 9 dev.ath.0.acktimeout: 48 dev.ath.0.ctstimeout: 48 dev.ath.0.softled: 0 dev.ath.0.ledpin: 0 dev.ath.0.ledon: 0 dev.ath.0.ledidle: 2700 dev.ath.0.txantenna: 0 dev.ath.0.rxantenna: 2 dev.ath.0.diversity: 1 dev.ath.0.txintrperiod: 5 dev.ath.0.diag: 0 dev.ath.0.tpscale: 0 dev.ath.0.tpc: 0 dev.ath.0.tpack: 63 dev.ath.0.tpcts: 63 dev.ath.0.fftxqmin: 2 dev.ath.0.fftxqmax: 50 dev.ath.0.monpass: 24 Perhaps somebody knows an answer to this? Thanks Lars --fU0UwhtRbpo05rnG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFHk1eKKc512sD3afgRAkPrAJ9GtlSv2AmcygPERHOGX1OZyCE/nACgp8We WN5WjmZRW6/j2dOs+A264Vk= =lZB6 -----END PGP SIGNATURE----- --fU0UwhtRbpo05rnG-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 20 15:30:19 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4FEC016A41B for ; Sun, 20 Jan 2008 15:30:19 +0000 (UTC) (envelope-from mail@maxlor.com) Received: from popeye1.ggamaur.net (popeye1.ggamaur.net [213.160.40.50]) by mx1.freebsd.org (Postfix) with ESMTP id EF68013C500 for ; Sun, 20 Jan 2008 15:30:17 +0000 (UTC) (envelope-from mail@maxlor.com) Received: from maxlor.mine.nu (c-82-192-240-247.customer.ggaweb.ch [82.192.240.247]) by popeye1.ggamaur.net (8.13.7/8.13.7/Submit) with ESMTP id m0KEwqki095801; Sun, 20 Jan 2008 15:58:55 +0100 (CET) (envelope-from mail@maxlor.com) Received: from localhost (unknown [127.0.0.1]) by maxlor.mine.nu (Postfix) with ESMTP id 813652E2CE; Sun, 20 Jan 2008 14:59:52 +0100 (CET) X-Virus-Scanned: amavisd-new at atlantis.intranet Received: from maxlor.mine.nu ([127.0.0.1]) by localhost (atlantis.intranet [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S9HP7mvpGtel; Sun, 20 Jan 2008 14:59:43 +0100 (CET) Received: from mini.intranet (mini.intranet [10.0.0.17]) by maxlor.mine.nu (Postfix) with ESMTP id 463212E2CD; Sun, 20 Jan 2008 14:59:43 +0100 (CET) From: Benjamin Lutz To: "Andrew Atrens" Date: Sun, 20 Jan 2008 14:59:39 +0100 User-Agent: KMail/1.9.7 References: <472E9D0B.5080409@csub.edu> <47821585.10804@moneybookers.com> <47824627.40701@nortel.com> In-Reply-To: <47824627.40701@nortel.com> X-Face: $Ov27?7*N,h60fIEfNJdb!m,@#4T/d; 1hw|W0zvsHM(a$Yn6BYQ0^SEEXvi8>D`|V*F"=?utf-8?q?=5F+=0A=09R2?=@Aq>+mNb4`,'[[%z9v0Fa~]AD1}xQO3|>b.z&}l#R-_(P`?@Mz"kS; XC>Eti,i3>%@=?utf-8?q?g=3F=0A=094f?=,\c7|Ghwb&ky$b2PJ^\0b83NkLsFKv|smL/cI4UD%Tu8alAD MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart9315603.0L7vy2ccm4"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200801201459.43152.mail@maxlor.com> X-Scanned-By: MIMEDefang 2.62 on 213.160.40.60 Cc: freebsd-current@freebsd.org Subject: Re: powerd adaptive mode latching X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 15:30:19 -0000 --nextPart9315603.0L7vy2ccm4 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello Andrew, On Monday 07 January 2008 16:32:55 Andrew Atrens wrote: > As far as I know a fix has not been submitted. My brain is still a > bit foggy from being off on holiday, but it seems to me that Benjamin > still had a problem with his AMD dual core system. I updated the machine in question to FreeBSD 6.3-RELEASE now. I was=20 happy to notice that the problem is fixed for me now: dev.cpu.0.freq_levels: 2100/15000 2000/13720 1800/11360 1000/5531 I still don't know exactly what the cause for the previous misbehaviour=20 was; my investigations quickly led me to code that was too complex to=20 understand in the time I was willing to invest in this; I guess this is=20 moot now. Thanks for your help! Cheers Benjamin --nextPart9315603.0L7vy2ccm4 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) iD8DBQBHk1PPzZEjpyKHuQwRAsaEAJ4+I6h6+nrrjJMVY6lS5wSjvsO9BgCfdsmF 8UA31JmxMljXOu3RbA6tyk0= =d9GF -----END PGP SIGNATURE----- --nextPart9315603.0L7vy2ccm4-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 20 15:39:12 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3BC7016A469 for ; Sun, 20 Jan 2008 15:39:12 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id F19C213C4D1 for ; Sun, 20 Jan 2008 15:39:11 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: by blah.sun-fish.com (Postfix, from userid 1002) id 7FDF31B10EFA; Sun, 20 Jan 2008 16:39:10 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on blah.cmotd.com X-Spam-Level: X-Spam-Status: No, score=-10.6 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.3 Received: from [10.1.1.2] (unknown [192.168.25.10]) by blah.sun-fish.com (Postfix) with ESMTP id C30821B10EBB for ; Sun, 20 Jan 2008 16:39:07 +0100 (CET) Message-ID: <47936B15.5050909@moneybookers.com> Date: Sun, 20 Jan 2008 17:39:01 +0200 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <472E9D0B.5080409@csub.edu> <47821585.10804@moneybookers.com> <47824627.40701@nortel.com> <200801201459.43152.mail@maxlor.com> In-Reply-To: <200801201459.43152.mail@maxlor.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.91.2/5499/Sun Jan 20 02:31:52 2008 on blah.cmotd.com X-Virus-Status: Clean Subject: Re: powerd adaptive mode latching X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 15:39:12 -0000 Greetings, Well this means that once we have the fix from Nate MFCed both reported issues will be fixed in 7.0-Release :) Benjamin Lutz wrote: > Hello Andrew, > > On Monday 07 January 2008 16:32:55 Andrew Atrens wrote: > >> As far as I know a fix has not been submitted. My brain is still a >> bit foggy from being off on holiday, but it seems to me that Benjamin >> still had a problem with his AMD dual core system. >> > > I updated the machine in question to FreeBSD 6.3-RELEASE now. I was > happy to notice that the problem is fixed for me now: > > dev.cpu.0.freq_levels: 2100/15000 2000/13720 1800/11360 1000/5531 > > I still don't know exactly what the cause for the previous misbehaviour > was; my investigations quickly led me to code that was too complex to > understand in the time I was willing to invest in this; I guess this is > moot now. > > Thanks for your help! > > Cheers > Benjamin > From owner-freebsd-current@FreeBSD.ORG Sun Jan 20 16:05:07 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1AEC16A421 for ; Sun, 20 Jan 2008 16:05:07 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.freebsd.org (Postfix) with ESMTP id 89BAF13C469 for ; Sun, 20 Jan 2008 16:05:07 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so175428nfb.33 for ; Sun, 20 Jan 2008 08:05:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer:sender; bh=yDFlQWKbhJJQpG/fxVu0MXTJLXbGHh+zV2bfTmI9qKo=; b=PL9kPHrl7ObfsJFeRSMt3F89D5oDPN1SCIejp+Tu7qHaD1ctFdyE4PTDT3Fx9gObtaW3H569W/4jpXyG9fqjBBJOK7FHmagpJX3Fk+B6qOq+bcXHffe/dOk4sEXImUOUfVLAelal+fssc84GNqm94s7JIgu6/3ZfRkaO1XyTmgY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer:sender; b=qN0F49QKB4/Yh3g0te+sKPSFSe3yRbDvK6lJYVAkW3ItbchK/wqpyfbwXEza6U+YNucp7hCIx7GpGxqNj+SL9+kxaHEXvuuC1LGtSLmKG7mIbj/OZYfOhrGounWd1/3JDJUWhMPNnUtvocFP/3XEVpQdjyDTRWpnw0TRSzaZ+7M= Received: by 10.78.132.2 with SMTP id f2mr7871326hud.19.1200845106027; Sun, 20 Jan 2008 08:05:06 -0800 (PST) Received: from epsilon.mshome.net ( [88.210.115.142]) by mx.google.com with ESMTPS id h6sm3820616nfh.30.2008.01.20.08.04.56 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 20 Jan 2008 08:05:01 -0800 (PST) Message-Id: <40174685-22BE-4D70-A18C-EAA578DD6227@FreeBSD.org> From: Rui Paulo To: Ian FREISLICH In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Date: Sun, 20 Jan 2008 16:04:53 +0000 References: X-Mailer: Apple Mail (2.915) Sender: Rui Paulo Cc: Eric Anholt , freebsd-current@FreeBSD.org Subject: Re: FreeBSD on macbook & backlight module X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 16:05:08 -0000 On Jan 19, 2008, at 5:08 PM, Ian FREISLICH wrote: > Rui Paulo wrote: >> On Jan 15, 2008, at 8:34 PM, Eric Anholt wrote: >> >>> I use xbacklight -set to control backlight. Your issue >>> with it flipping to only a high/low value may have been the one >>> jbarnes >>> fixed in git recently (apparently a low bit got redefined on us). >> >> That's great news. This way we can rely on Xorg to set the backlight >> instead of adding one more kernel module. > > Neither work for me - my MacBook 17" uses the Radeon Mobility X1600 > (M56P) chip. Yes, this is only specific to MacBooks with Intel graphic cards. -- Rui Paulo From owner-freebsd-current@FreeBSD.ORG Sun Jan 20 18:15:36 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E275916A41B for ; Sun, 20 Jan 2008 18:15:36 +0000 (UTC) (envelope-from mailinglist@nesluop.dk) Received: from unixdunk.nesluop.dk (cpe.atm4-0-51450.0x535f05ca.hrnxx12.customer.tele.dk [83.95.5.202]) by mx1.freebsd.org (Postfix) with SMTP id 3CA1813C448 for ; Sun, 20 Jan 2008 18:15:35 +0000 (UTC) (envelope-from mailinglist@nesluop.dk) Received: (qmail 79512 invoked by uid 89); 20 Jan 2008 18:08:50 -0000 Received: from unknown (HELO ?192.168.1.100?) (192.168.1.100) by unixdunk.nesluop.dk with SMTP; 20 Jan 2008 18:08:50 -0000 Message-ID: <47938E33.6000601@nesluop.dk> Date: Sun, 20 Jan 2008 19:08:51 +0100 From: Chris Poulsen User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: pyunyh@gmail.com References: <20071225234723.GA1018@cdnetworks.co.kr> <4772D649.3010001@nesluop.dk> <20071227002252.GE1018@cdnetworks.co.kr> <20080116012154.GB84758@cdnetworks.co.kr> <478E7DF3.4080908@nesluop.dk> <20080117014013.GA89210@cdnetworks.co.kr> <478F98D7.5040007@nesluop.dk> <20080118010100.GC92718@cdnetworks.co.kr> <20080118082609.GA93423@cdnetworks.co.kr> <4790EBA8.9090500@nesluop.dk> <20080119060354.GA98043@cdnetworks.co.kr> In-Reply-To: <20080119060354.GA98043@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kevlo@freebsd.org, FreeBSD Current Subject: Re: Problem with nfe stability and throughput X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 18:15:37 -0000 Hi, Pyun YongHyeon wrote: > Did you have to bring nfe(4) down and up manually due to network lockups? > Yes, I did it manually. > Maybe this would come from atphy(4) bug. atphy(4) does not seem to > reliabily detect an established link. > I saw several nfe0 down/up messages in my log after i did the manual down/up, but they stopped appearing as I stopped stressing the link. > > ifconfig nfe0 yields: > > > > nfe0: flags=8843 metric 0 mtu 1500 > > options=48 > > ether 00:1d:60:6d:73:ec > > inet 192.168.1.11 netmask 0xffffff00 broadcast 192.168.1.255 > > media: Ethernet autoselect (100baseTX ) > > status: active > > > > How about the following change? > From /usr/src/sys/dev/mii/athpy.c: > 288 ssr = PHY_READ(sc, ATPHY_SSR); > 289 if ((((bmcr & BMCR_AUTOEN) != 0) && ((bmsr & BMSR_ACOMP) == 0)) || > 290 (ssr & ATPHY_SSR_SPD_DPLX_RESOLVED) == 0) { > 291 /* Erg, still trying, I guess... */ > 292 mii->mii_media_active |= IFM_NONE; > 293 return; > 294 } > > To: > 288 ssr = PHY_READ(sc, ATPHY_SSR); > 289 if ((ssr & ATPHY_SSR_SPD_DPLX_RESOLVED) == 0) { > 290 /* Erg, still trying, I guess... */ > 291 mii->mii_media_active |= IFM_NONE; > 292 return; > 293 } > I applied the patch and rebooted the server remotely earlier this day (was feeling a little adventurous). The driver seems to run somewhat stable (not fast and not 100% reliable, but good enough for my current usage). When I get home, I'll try stressing the network some, to see how badly it misbehaves. I tried pinging the machine and the result of that is that 10-20 pings are OK and then usually a single timeout follows and then another 10-20 OK pings etc. SSH transfer from the machine does not look to be especially fast, it seemed to settle around 150 Kilo byte / sec (I'm able to pull around 1,3-2,0 MB/sec off this one using rl0 (there is some wlan involved so transfer speeds are not as reliable as the ftp uploads from my other bsd machine. > Thanks for your patience and testing. > I'd like to get my HW up and running :) - and I don't mind going through a little trouble, if it can help fbsd get even better. So I also appreciate you taking your time to give this a shot. I'll drop a mail when I get home tomorrow and have had a chance to beat up the network a little ;) -- Regards Chris From owner-freebsd-current@FreeBSD.ORG Sun Jan 20 21:02:25 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F53316A419 for ; Sun, 20 Jan 2008 21:02:25 +0000 (UTC) (envelope-from kirk@strauser.com) Received: from kanga.honeypot.net (kanga.honeypot.net [IPv6:2001:470:1f01:383:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5EBC713C459 for ; Sun, 20 Jan 2008 21:02:25 +0000 (UTC) (envelope-from kirk@strauser.com) Received: from localhost (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id 8BCB15F0C79 for ; Sun, 20 Jan 2008 15:02:24 -0600 (CST) X-Virus-Scanned: amavisd-new at honeypot.net Received: from kanga.honeypot.net ([127.0.0.1]) by localhost (kanga.honeypot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CBb-belJFN+L for ; Sun, 20 Jan 2008 15:02:21 -0600 (CST) Received: from janus.daycos.com (janus.daycos.com [10.45.12.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTP id D366F5F0B7B for ; Sun, 20 Jan 2008 15:02:20 -0600 (CST) From: Kirk Strauser To: freebsd-current@freebsd.org Date: Sun, 20 Jan 2008 15:02:14 -0600 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) X-Face: T+/_{qmjgbosI0J/e83I~w[&VF'w)!((xEpj///^bA/6?jHHS?nq+T8_+`nh"WnEWCWG, \}]Y2$)) =?utf-8?q?vLVz4ACChrEcb=7DCO=5EtYmMG=5C=0A=09ts=2Em=3F=5B7=5B6OwE*dAJ*9f+m?= =?utf-8?q?X=2E7R32qeN=5EDJ=5C?=(k@evW?IRQCy.^ MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4931621.QSvs1YG4Xp"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200801201502.18814.kirk@strauser.com> Subject: "Bad address" with smbfs inside a jail X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 21:02:25 -0000 --nextPart4931621.QSvs1YG4Xp Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I have a very new FreeBSD 7 build on a server: =2D------------------------ $ uname -a =46reeBSD jail1.daycos.com 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #0: Sat Ja= n 19 11:16:27 CST 2008 root@jail1.daycos.com:/usr/obj/usr/src/sys/JAIL1= i386 =2D------------------------ Its kernel is very close to GENERIC (and I've tried GENERIC with /etc/make.conf:CPUTYPE unset just to rule it out): =2D------------------------ $ cat /usr/src/sys/i386/conf/JAIL1 include GENERIC ident JAIL1 options PMAP_SHPGPERPROC=3D301 nooption SCHED_4BSD option SCHED_ULE # Don't let Mike accidentally reboot the server option SC_DISABLE_REBOOT # disable reboot key sequen= ce =2D------------------------ I have the same smbfs share mounted in two different places on the system: once inside the "main" system and once inside a jail. I'm having a problem with the jailed version when copying new files: =2D------------------------ $ cp /mnt/tiffsrv/vdrive/Scanned/2008/01/20/2008012014450000.tif /tmp/foo cp: /tmp/foo: Bad address =2D------------------------ This only affects new files; that is, ones that have been created since the filesystem was mounted. If I unmount/remount the filesystem, that copy succeeds: =2D------------------------ $ cp /mnt/tiffsrv/vdrive/Scanned/2008/01/20/2008012014450000.tif /tmp/foo $ =2D------------------------ The fstab entries for those mounts are identical: =2D------------------------ $ grep tiffsrv /etc/fstab //web2@tiffsrv/vdrive /mnt/tiffsrv/vdrive smbfs rw,noexec 0 0 $ grep tiffsrv /etc/fstab.web2 //web2@tiffsrv/vdrive /var/jail/web2/mnt/tiffsrv/vdrive smbfs rw,noexec 0 0 =2D------------------------ Again, those errors *never* happen inside the host OS - just inside that jail. Any suggestions? =2D-=20 Kirk Strauser --nextPart4931621.QSvs1YG4Xp Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- iD8DBQBHk7ba5sRg+Y0CpvERAgE6AKCAV+WezCm34oCPjahRjSXxn3SaVQCcDM+U lELdFN3bEnZpE9qgjwAwlGQ= =15W1 -----END PGP SIGNATURE----- --nextPart4931621.QSvs1YG4Xp-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 20 23:18:51 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C687F16A46B for ; Sun, 20 Jan 2008 23:18:51 +0000 (UTC) (envelope-from cptsalek@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.190]) by mx1.freebsd.org (Postfix) with ESMTP id 6189513C468 for ; Sun, 20 Jan 2008 23:18:51 +0000 (UTC) (envelope-from cptsalek@gmail.com) Received: by mu-out-0910.google.com with SMTP id w9so1137804mue.6 for ; Sun, 20 Jan 2008 15:18:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=6bqLk4+RApChwvkb4SoxgBvhxrTge28nmdy/hMdPXjM=; b=lF+EayU9pP8hEEkffCnztxIKj8H7+FSxiFWHnFCKUQJjkY04IhnWzyONY73CsnMqcfgh6p676zopKOa7wTVtFinMoih5PCIM4PYK3Yh1I4+6jGK4WTG2JkI18XD2/zpbzi1MXfcYNpMy5/+3TdO3QSNkdGjXNWCs7iWSLZ5lTBs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=NB8381MERp9V08qcJczA4yiTxZyFL0gYV/mXuWlA1mJyRRuqFJKBgm74KmUToyYAn5g9aiYDWSLDzeDRm+9rM7f/kkpOpKTRqLLi0A6WbbcEb0zw0bKO86erzFvObCZI6WWy8xLi7Oipy8ZbZaPURV+zW/6yObrA3QhYQuBd2sI= Received: by 10.82.134.12 with SMTP id h12mr11042450bud.29.1200869604946; Sun, 20 Jan 2008 14:53:24 -0800 (PST) Received: by 10.82.159.19 with HTTP; Sun, 20 Jan 2008 14:53:24 -0800 (PST) Message-ID: <14989d6e0801201453y405bdd09lc35fb55234dff6ae@mail.gmail.com> Date: Sun, 20 Jan 2008 22:53:24 +0000 From: "Christian Walther" To: "Lars Engels" In-Reply-To: <20080120141538.GH47164@e.0x20.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080120141538.GH47164@e.0x20.net> Cc: current@freebsd.org Subject: Re: sysutils/hal causes ath device timeout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 23:18:51 -0000 Hi Lars, Hi List, On 20/01/2008, Lars Engels wrote: > Hi all, > [...] > The hal daemon causes a timeout of my ath-driven Netgear WAG511 PC-Card. > As soon as hald is started, the wireless connection is lost and I get > this kernel message: > ath0: device timeout > ath0: ath_reset: unable to reset hardware; hal status 3230239248 > Same here: Card is an D-Link DWl-G650 Jan 19 22:24:28 fairy kernel: ath0: mem 0x88000000-0x8800ffff irq 16 at device 0.0 on cardbus0 Jan 19 22:24:28 fairy kernel: ath0: Ethernet address: 00:19:5b:3a:82:be Jan 19 22:24:28 fairy kernel: ath0: mac 7.9 phy 4.5 radio 5.6 dhclient is able to receive and set the IP address, but that's all. The message appear to be the same, too: Jan 20 23:26:26 fairy kernel: ath0: device timeout Jan 20 23:26:26 fairy kernel: ath0: ath_reset: unable to reset hardware; hal status 3232504036 > When I eject the card then, the machine reboots. The reason for the panic seems to be: Jan 20 23:27:59 fairy savecore: reboot after panic: resource_list_release: resource entry is not busy > > Environment: > > FreeBSD 8.0-CURRENT #0: Mon Jan 14 22:37:27 CET 2008 > lars@maggie.bsd-geek.de:/usr/obj/usr/src/sys/MAGGIE i386 > For me this is: FreeBSD fairy.alashan.de 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #0: Sun Jan 20 18:41:12 UTC 2008 zoot@fairy:/usr/obj/usr/src/sys/GENERIC i386 I guess I'll rebuilt all ports now, just to make sure that everything is fine. Maybe the problem goes away with a newly built hal. Christian From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 00:50:12 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7B1E416A418 for ; Mon, 21 Jan 2008 00:50:12 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id E9F7D13C4F2 for ; Mon, 21 Jan 2008 00:50:11 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JGkrY-0006o1-Qn for freebsd-current@freebsd.org; Mon, 21 Jan 2008 00:50:08 +0000 Received: from 89-172-56-197.adsl.net.t-com.hr ([89.172.56.197]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 21 Jan 2008 00:50:08 +0000 Received: from ivoras by 89-172-56-197.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 21 Jan 2008 00:50:08 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Mon, 21 Jan 2008 01:50:00 +0100 Lines: 198 Message-ID: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig0B4F2D47CCEEE59E86C1ABD2" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 89-172-56-197.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) X-Enigmail-Version: 0.95.6 Sender: news Subject: Only 64 MB memory recognized - HP xw4550 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 00:50:12 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0B4F2D47CCEEE59E86C1ABD2 Content-Type: multipart/mixed; boundary="------------010906020902040906030204" This is a multi-part message in MIME format. --------------010906020902040906030204 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Hi, I'm attaching a dmesg from 7.0-BETA4, i386, on a HP workstation with an=20 Opteron CPU and 2 GB memory. The main problem is that only 64 MB memory=20 is recognized by FreeBSD (the BIOS and the FreeBSD loader account all of = 2 GB). This is a "FYI-only" post as I don't have the hardware any more.=20 Maybe someone gets an idea about the problem. --------------010906020902040906030204 Content-Type: text/plain; name="dmesg.txt" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="dmesg.txt" Q29weXJpZ2h0IChjKSAxOTkyLTIwMDcgVGhlIEZyZWVCU0QgUHJvamVjdC4KQ29weXJpZ2h0 IChjKSAxOTc5LCAxOTgwLCAxOTgzLCAxOTg2LCAxOTg4LCAxOTg5LCAxOTkxLCAxOTkyLCAx OTkzLCAxOTk0CglUaGUgUmVnZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlh LiBBbGwgcmlnaHRzIHJlc2VydmVkLgpGcmVlQlNEIGlzIGEgcmVnaXN0ZXJlZCB0cmFkZW1h cmsgb2YgVGhlIEZyZWVCU0QgRm91bmRhdGlvbi4KRnJlZUJTRCA3LjAtQkVUQTQgIzE6IEZy aSBEZWMgIDcgMDE6Mzc6NTUgQ0VUIDIwMDcKICAgIHJvb3RAZmluc3RhbGwuY29zbW9zOi91 c3Ivb2JqL3Vzci9zcmMvc3lzL0dFTkVSSUMKVGltZWNvdW50ZXIgImk4MjU0IiBmcmVxdWVu Y3kgMTE5MzE4MiBIeiBxdWFsaXR5IDAKQ1BVOiBEdWFsLUNvcmUgQU1EIE9wdGVyb24odG0p IFByb2Nlc3NvciAxMjIyICgyOTkyLjUyLU1IeiA2ODYtY2xhc3MgQ1BVKQogIE9yaWdpbiA9 ICJBdXRoZW50aWNBTUQiICBJZCA9IDB4NDBmMzMgIFN0ZXBwaW5nID0gMwogIEZlYXR1cmVz PTB4MTc4YmZiZmY8RlBVLFZNRSxERSxQU0UsVFNDLE1TUixQQUUsTUNFLENYOCxBUElDLFNF UCxNVFJSLFBHRSxNQ0EsQ01PVixQQVQsUFNFMzYsQ0xGTFVTSCxNTVgsRlhTUixTU0UsU1NF MixIVFQ+CiAgRmVhdHVyZXMyPTB4MjAwMTxTU0UzLENYMTY+CiAgQU1EIEZlYXR1cmVzPTB4 ZWE1MDA4MDA8U1lTQ0FMTCxOWCxNTVgrLEZGWFNSLFJEVFNDUCxMTSwzRE5vdyErLDNETm93 IT4KICBBTUQgRmVhdHVyZXMyPTB4MWY8TEFIRixDTVAsU1ZNLEV4dEFQSUMsQ1I4PgogIENv cmVzIHBlciBwYWNrYWdlOiAyCnJlYWwgbWVtb3J5ICA9IDY3MTA4ODY0ICg2NCBNQikKYXZh aWwgbWVtb3J5ID0gNTE2NTg3NTIgKDQ5IE1CKQpBQ1BJIEFQSUMgVGFibGU6IDxIUFFPRU0g ICB4dzQ1NTA+CkZyZWVCU0QvU01QOiBNdWx0aXByb2Nlc3NvciBTeXN0ZW0gRGV0ZWN0ZWQ6 IDIgQ1BVcwogY3B1MCAoQlNQKTogQVBJQyBJRDogIDAKIGNwdTEgKEFQKTogQVBJQyBJRDog IDEKQUNQSSBXYXJuaW5nICh0YmZhZHQtMDMyNCk6IEZBRFQgKHJldmlzaW9uIDMpIGlzIGxv bmdlciB0aGFuIEFDUEkgMi4wIHZlcnNpb24sIHRydW5jYXRpbmcgbGVuZ3RoIDB4MTBDIHRv IDB4RjQgWzIwMDcwMzIwXQppb2FwaWMwIDxWZXJzaW9uIDIuMT4gaXJxcyAwLTIzIG9uIG1v dGhlcmJvYXJkCmtiZDEgYXQga2JkbXV4MAphdGhfaGFsOiAwLjkuMjAuMyAoQVI1MjEwLCBB UjUyMTEsIEFSNTIxMiwgUkY1MTExLCBSRjUxMTIsIFJGMjQxMywgUkY1NDEzKQphY3BpMDog PEhQUU9FTSBTTElDLVdLUz4gb24gbW90aGVyYm9hcmQKYWNwaTA6IFtJVEhSRUFEXQphY3Bp MDogUG93ZXIgQnV0dG9uIChmaXhlZCkKYWNwaTA6IHJlc2VydmF0aW9uIG9mIDAsIGEwMDAw ICgzKSBmYWlsZWQKYWNwaTA6IHJlc2VydmF0aW9uIG9mIDEwMDAwMCwgN2ZmMDAwMDAgKDMp IGZhaWxlZApUaW1lY291bnRlciAiQUNQSS1mYXN0IiBmcmVxdWVuY3kgMzU3OTU0NSBIeiBx dWFsaXR5IDEwMDAKYWNwaV90aW1lcjA6IDwyNC1iaXQgdGltZXIgYXQgMy41Nzk1NDVNSHo+ IHBvcnQgMHhmODA4LTB4ZjgwYiBvbiBhY3BpMAphY3BpX2hwZXQwOiA8SGlnaCBQcmVjaXNp b24gRXZlbnQgVGltZXI+IGlvbWVtIDB4ZmVkMDAwMDAtMHhmZWQwMDNmZiBvbiBhY3BpMApU aW1lY291bnRlciAiSFBFVCIgZnJlcXVlbmN5IDE0MzE4MTgwIEh6IHF1YWxpdHkgOTAwCmNw dTA6IDxBQ1BJIENQVT4gb24gYWNwaTAKcG93ZXJub3cwOiA8UG93ZXJOb3chIEs4PiBvbiBj cHUwCmFjcGlfdGhyb3R0bGUwOiA8QUNQSSBDUFUgVGhyb3R0bGluZz4gb24gY3B1MApjcHUx OiA8QUNQSSBDUFU+IG9uIGFjcGkwCnBvd2Vybm93MTogPFBvd2VyTm93ISBLOD4gb24gY3B1 MQphY3BpX3Rocm90dGxlMTogPEFDUEkgQ1BVIFRocm90dGxpbmc+IG9uIGNwdTEKYWNwaV90 aHJvdHRsZTE6IGZhaWxlZCB0byBhdHRhY2ggUF9DTlQKZGV2aWNlX2F0dGFjaDogYWNwaV90 aHJvdHRsZTEgYXR0YWNoIHJldHVybmVkIDYKcGNpYjA6IDxBQ1BJIEhvc3QtUENJIGJyaWRn ZT4gcG9ydCAweGNmOC0weGNmZiBvbiBhY3BpMApwY2kwOiA8QUNQSSBQQ0kgYnVzPiBvbiBw Y2liMApwY2liMTogPEFDUEkgUENJLVBDSSBicmlkZ2U+IGF0IGRldmljZSAyLjAgb24gcGNp MApwY2kyOiA8QUNQSSBQQ0kgYnVzPiBvbiBwY2liMQp2Z2FwY2kwOiA8VkdBLWNvbXBhdGli bGUgZGlzcGxheT4gcG9ydCAweDExMDAtMHgxMTdmIG1lbSAweGM0MDAwMDAwLTB4YzRmZmZm ZmYsMHhhMDAwMDAwMC0weGJmZmZmZmZmLDB4YzIwMDAwMDAtMHhjM2ZmZmZmZiBpcnEgMTgg YXQgZGV2aWNlIDAuMCBvbiBwY2kyCnBjaWIyOiA8QUNQSSBQQ0ktUENJIGJyaWRnZT4gYXQg ZGV2aWNlIDcuMCBvbiBwY2kwCnBjaTYzOiA8QUNQSSBQQ0kgYnVzPiBvbiBwY2liMgpiZ2Uw OiA8QnJvYWRjb20gTmV0WHRyZW1lIEdpZ2FiaXQgRXRoZXJuZXQgQ29udHJvbGxlciwgQVNJ QyByZXYuIDB4YTAwMj4gbWVtIDB4YzA0MDAwMDAtMHhjMDQwZmZmZiBpcnEgMTkgYXQgZGV2 aWNlIDAuMCBvbiBwY2k2MwptaWlidXMwOiA8TUlJIGJ1cz4gb24gYmdlMApicmdwaHkwOiA8 QkNNNTc1NSAxMC8xMDAvMTAwMGJhc2VUWCBQSFk+IFBIWSAxIG9uIG1paWJ1czAKYnJncGh5 MDogIDEwYmFzZVQsIDEwYmFzZVQtRkRYLCAxMDBiYXNlVFgsIDEwMGJhc2VUWC1GRFgsIDEw MDBiYXNlVCwgMTAwMGJhc2VULUZEWCwgYXV0bwpiZ2UwOiBFdGhlcm5ldCBhZGRyZXNzOiAw MDoxYzpjNDo5ODo2ODphZQpiZ2UwOiBbSVRIUkVBRF0KYXRhcGNpMDogPFxNLUAJXF5CXE0t QSkld1xNLUBcTS1oPiBwb3J0IDB4MWYwLTB4MWY3LDB4M2Y2LDB4MTcwLTB4MTc3LDB4Mzc2 LDB4MjEwMC0weDIxMGYgbWVtIDB4YzA1MDkwMDAtMHhjMDUwOTNmZiBpcnEgMjIgYXQgZGV2 aWNlIDE4LjAgb24gcGNpMAphdGEwOiA8QVRBIGNoYW5uZWwgMD4gb24gYXRhcGNpMAphdGEw OiBbSVRIUkVBRF0KYXRhMTogPEFUQSBjaGFubmVsIDE+IG9uIGF0YXBjaTAKYXRhMTogW0lU SFJFQURdCm9oY2kwOiA8T0hDSSAoZ2VuZXJpYykgVVNCIGNvbnRyb2xsZXI+IG1lbSAweGMw NTA0MDAwLTB4YzA1MDRmZmYgaXJxIDE2IGF0IGRldmljZSAxOS4wIG9uIHBjaTAKb2hjaTA6 IFtHSUFOVC1MT0NLRURdCm9oY2kwOiBbSVRIUkVBRF0KdXNiMDogT0hDSSB2ZXJzaW9uIDEu MCwgbGVnYWN5IHN1cHBvcnQKdXNiMDogPE9IQ0kgKGdlbmVyaWMpIFVTQiBjb250cm9sbGVy PiBvbiBvaGNpMAp1c2IwOiBVU0IgcmV2aXNpb24gMS4wCnVodWIwOiA8QVRJIE9IQ0kgcm9v dCBodWIsIGNsYXNzIDkvMCwgcmV2IDEuMDAvMS4wMCwgYWRkciAxPiBvbiB1c2IwCnVodWIw OiAyIHBvcnRzIHdpdGggMiByZW1vdmFibGUsIHNlbGYgcG93ZXJlZApvaGNpMTogPE9IQ0kg KGdlbmVyaWMpIFVTQiBjb250cm9sbGVyPiBtZW0gMHhjMDUwNTAwMC0weGMwNTA1ZmZmIGly cSAxNyBhdCBkZXZpY2UgMTkuMSBvbiBwY2kwCm9oY2kxOiBbR0lBTlQtTE9DS0VEXQpvaGNp MTogW0lUSFJFQURdCnVzYjE6IE9IQ0kgdmVyc2lvbiAxLjAsIGxlZ2FjeSBzdXBwb3J0CnVz YjE6IDxPSENJIChnZW5lcmljKSBVU0IgY29udHJvbGxlcj4gb24gb2hjaTEKdXNiMTogVVNC IHJldmlzaW9uIDEuMAp1aHViMTogPEFUSSBPSENJIHJvb3QgaHViLCBjbGFzcyA5LzAsIHJl diAxLjAwLzEuMDAsIGFkZHIgMT4gb24gdXNiMQp1aHViMTogMiBwb3J0cyB3aXRoIDIgcmVt b3ZhYmxlLCBzZWxmIHBvd2VyZWQKb2hjaTI6IDxPSENJIChnZW5lcmljKSBVU0IgY29udHJv bGxlcj4gbWVtIDB4YzA1MDYwMDAtMHhjMDUwNmZmZiBpcnEgMTggYXQgZGV2aWNlIDE5LjIg b24gcGNpMApvaGNpMjogW0dJQU5ULUxPQ0tFRF0Kb2hjaTI6IFtJVEhSRUFEXQp1c2IyOiBP SENJIHZlcnNpb24gMS4wLCBsZWdhY3kgc3VwcG9ydAp1c2IyOiA8T0hDSSAoZ2VuZXJpYykg VVNCIGNvbnRyb2xsZXI+IG9uIG9oY2kyCnVzYjI6IFVTQiByZXZpc2lvbiAxLjAKdWh1YjI6 IDxBVEkgT0hDSSByb290IGh1YiwgY2xhc3MgOS8wLCByZXYgMS4wMC8xLjAwLCBhZGRyIDE+ IG9uIHVzYjIKdWh1YjI6IDIgcG9ydHMgd2l0aCAyIHJlbW92YWJsZSwgc2VsZiBwb3dlcmVk Cm9oY2kzOiA8T0hDSSAoZ2VuZXJpYykgVVNCIGNvbnRyb2xsZXI+IG1lbSAweGMwNTA3MDAw LTB4YzA1MDdmZmYgaXJxIDE3IGF0IGRldmljZSAxOS4zIG9uIHBjaTAKb2hjaTM6IFtHSUFO VC1MT0NLRURdCm9oY2kzOiBbSVRIUkVBRF0KdXNiMzogT0hDSSB2ZXJzaW9uIDEuMCwgbGVn YWN5IHN1cHBvcnQKdXNiMzogPE9IQ0kgKGdlbmVyaWMpIFVTQiBjb250cm9sbGVyPiBvbiBv aGNpMwp1c2IzOiBVU0IgcmV2aXNpb24gMS4wCnVodWIzOiA8QVRJIE9IQ0kgcm9vdCBodWIs IGNsYXNzIDkvMCwgcmV2IDEuMDAvMS4wMCwgYWRkciAxPiBvbiB1c2IzCnVodWIzOiAyIHBv cnRzIHdpdGggMiByZW1vdmFibGUsIHNlbGYgcG93ZXJlZApvaGNpNDogPE9IQ0kgKGdlbmVy aWMpIFVTQiBjb250cm9sbGVyPiBtZW0gMHhjMDUwODAwMC0weGMwNTA4ZmZmIGlycSAxOCBh dCBkZXZpY2UgMTkuNCBvbiBwY2kwCm9oY2k0OiBbR0lBTlQtTE9DS0VEXQpvaGNpNDogW0lU SFJFQURdCnVzYjQ6IE9IQ0kgdmVyc2lvbiAxLjAsIGxlZ2FjeSBzdXBwb3J0CnVzYjQ6IDxP SENJIChnZW5lcmljKSBVU0IgY29udHJvbGxlcj4gb24gb2hjaTQKdXNiNDogVVNCIHJldmlz aW9uIDEuMAp1aHViNDogPEFUSSBPSENJIHJvb3QgaHViLCBjbGFzcyA5LzAsIHJldiAxLjAw LzEuMDAsIGFkZHIgMT4gb24gdXNiNAp1aHViNDogMiBwb3J0cyB3aXRoIDIgcmVtb3ZhYmxl LCBzZWxmIHBvd2VyZWQKZWhjaTA6IDxFSENJIChnZW5lcmljKSBVU0IgMi4wIGNvbnRyb2xs ZXI+IG1lbSAweGMwNTA5NDAwLTB4YzA1MDk0ZmYgaXJxIDE5IGF0IGRldmljZSAxOS41IG9u IHBjaTAKZWhjaTA6IFtHSUFOVC1MT0NLRURdCmVoY2kwOiBbSVRIUkVBRF0KdXNiNTogRUhD SSB2ZXJzaW9uIDEuMAp1c2I1OiBjb21wYW5pb24gY29udHJvbGxlcnMsIDIgcG9ydHMgZWFj aDogdXNiMCB1c2IxIHVzYjIgdXNiMyB1c2I0CnVzYjU6IDxFSENJIChnZW5lcmljKSBVU0Ig Mi4wIGNvbnRyb2xsZXI+IG9uIGVoY2kwCnVzYjU6IFVTQiByZXZpc2lvbiAyLjAKdWh1YjU6 IDxBVEkgRUhDSSByb290IGh1YiwgY2xhc3MgOS8wLCByZXYgMi4wMC8xLjAwLCBhZGRyIDE+ IG9uIHVzYjUKdWh1YjU6IDEwIHBvcnRzIHdpdGggMTAgcmVtb3ZhYmxlLCBzZWxmIHBvd2Vy ZWQKdWh1YjY6IDxBcHBsZSwgSW5jLiBLZXlib2FyZCBIdWIsIGNsYXNzIDkvMCwgcmV2IDIu MDAvOTQuMTUsIGFkZHIgMj4gb24gdWh1YjUKdWh1YjY6IHNpbmdsZSB0cmFuc2FjdGlvbiB0 cmFuc2xhdG9yCnVodWI2OiAzIHBvcnRzIHdpdGggMiByZW1vdmFibGUsIGJ1cyBwb3dlcmVk CnVrYmQwOiA8QXBwbGUsIEluYyBBcHBsZSBLZXlib2FyZCwgY2xhc3MgMC8wLCByZXYgMi4w MC8wLjY3LCBhZGRyIDM+IG9uIHVodWI2CmtiZDIgYXQgdWtiZDAKdWhpZDA6IDxBcHBsZSwg SW5jIEFwcGxlIEtleWJvYXJkLCBjbGFzcyAwLzAsIHJldiAyLjAwLzAuNjcsIGFkZHIgMz4g b24gdWh1YjYKdW1hc3MwOiA8R2VuZXJpYyBVU0IyLjAtQ1JXLCBjbGFzcyAwLzAsIHJldiAy LjAwLzExLjIyLCBhZGRyIDQ+IG9uIHVodWI1CnBjaTA6IDxzZXJpYWwgYnVzLCBTTUJ1cz4g YXQgZGV2aWNlIDIwLjAgKG5vIGRyaXZlciBhdHRhY2hlZCkKYXRhcGNpMTogPEFUSSBJWFA2 MDAgVURNQTEzMyBjb250cm9sbGVyPiBwb3J0IDB4MjE0MC0weDIxNDcsMHgyMTU4LTB4MjE1 YiwweDIxNDgtMHgyMTRmLDB4MjE1Yy0weDIxNWYsMHgyMTIwLTB4MjEyZiBpcnEgMTYgYXQg ZGV2aWNlIDIwLjEgb24gcGNpMAphdGFwY2kxOiBbSVRIUkVBRF0KYXRhMjogPEFUQSBjaGFu bmVsIDA+IG9uIGF0YXBjaTEKYXRhMjogW0lUSFJFQURdCnBjaTA6IDxtdWx0aW1lZGlhPiBh dCBkZXZpY2UgMjAuMiAobm8gZHJpdmVyIGF0dGFjaGVkKQppc2FiMDogPFBDSS1JU0EgYnJp ZGdlPiBhdCBkZXZpY2UgMjAuMyBvbiBwY2kwCmlzYTA6IDxJU0EgYnVzPiBvbiBpc2FiMApw Y2liMzogPEFDUEkgUENJLVBDSSBicmlkZ2U+IGF0IGRldmljZSAyMC40IG9uIHBjaTAKcGNp NzogPEFDUEkgUENJIGJ1cz4gb24gcGNpYjMKYWNwaV9idXR0b24wOiA8UG93ZXIgQnV0dG9u PiBvbiBhY3BpMApzaW8wOiA8U3RhbmRhcmQgUEMgQ09NIHBvcnQ+IHBvcnQgMHgzZjgtMHgz ZmYgaXJxIDQgZmxhZ3MgMHgxMCBvbiBhY3BpMApzaW8wOiB0eXBlIDE2NTUwQQpzaW8wOiBb RklMVEVSXQpmZGMwOiA8ZmxvcHB5IGRyaXZlIGNvbnRyb2xsZXIgKEZERSk+IHBvcnQgMHgz ZjAtMHgzZjUsMHgzZjcgaXJxIDYgZHJxIDIgb24gYWNwaTAKZmRjMDogW0ZJTFRFUl0KcG10 aW1lcjAgb24gaXNhMAphdGtiZGMwOiA8S2V5Ym9hcmQgY29udHJvbGxlciAoaTgwNDIpPiBh dCBwb3J0IDB4NjAsMHg2NCBvbiBpc2EwCmF0a2JkMDogPEFUIEtleWJvYXJkPiBpcnEgMSBv biBhdGtiZGMwCmtiZDAgYXQgYXRrYmQwCmF0a2JkMDogW0dJQU5ULUxPQ0tFRF0KYXRrYmQw OiBbSVRIUkVBRF0KcHBjMDogcGFyYWxsZWwgcG9ydCBub3QgZm91bmQuCnNjMDogPFN5c3Rl bSBjb25zb2xlPiBhdCBmbGFncyAweDEwMCBvbiBpc2EwCnNjMDogVkdBIDwxNiB2aXJ0dWFs IGNvbnNvbGVzLCBmbGFncz0weDMwMD4Kc2lvMTogY29uZmlndXJlZCBpcnEgMyBub3QgaW4g Yml0bWFwIG9mIHByb2JlZCBpcnFzIDAKc2lvMTogcG9ydCBtYXkgbm90IGJlIGVuYWJsZWQK dmdhMDogPEdlbmVyaWMgSVNBIFZHQT4gYXQgcG9ydCAweDNjMC0weDNkZiBpb21lbSAweGEw MDAwLTB4YmZmZmYgb24gaXNhMAp1bXMwOiA8TG9naXRlY2ggVVNCLVBTLzIgT3B0aWNhbCBN b3VzZSwgY2xhc3MgMC8wLCByZXYgMi4wMC8yNS4wMCwgYWRkciAyPiBvbiB1aHViMAp1bXMw OiA0IGJ1dHRvbnMgYW5kIFogZGlyLgpUaW1lY291bnRlcnMgdGljayBldmVyeSAxLjAwMCBt c2VjCmFkMDogMjM4NDc1TUIgPFNlYWdhdGUgU1QzMjUwNjIwQVMgMy5DSEw+IGF0IGF0YTAt bWFzdGVyIFVETUEzMwphY2QwOiBEVkRSIDxBVEFQSSBEVkQgQSBESDE2QTFML0tIMzc+IGF0 IGF0YTEtbWFzdGVyIFVETUEzMwpHRU9NX0xBQkVMOiBMYWJlbCBmb3IgcHJvdmlkZXIgYWQw czIgaXMgbnRmcy9IUF9SRUNPVkVSWS4KR0VPTV9MQUJFTDogTGFiZWwgZm9yIHByb3ZpZGVy IGFjZDAgaXMgaXNvOTY2MC9GcmVlQlNENy4KU01QOiBBUCBDUFUgIzEgTGF1bmNoZWQhCmRh MCBhdCB1bWFzcy1zaW0wIGJ1cyAwIHRhcmdldCAwIGx1biAwCmRhMDogPEdlbmVyaWMtIENv bXBhY3QgRmxhc2ggMS4wMD4gUmVtb3ZhYmxlIERpcmVjdCBBY2Nlc3MgU0NTSS0wIGRldmlj ZSAKZGEwOiA0MC4wMDBNQi9zIHRyYW5zZmVycwpkYTA6IEF0dGVtcHQgdG8gcXVlcnkgZGV2 aWNlIHNpemUgZmFpbGVkOiBOT1QgUkVBRFksIE1lZGl1bSBub3QgcHJlc2VudApkYTEgYXQg dW1hc3Mtc2ltMCBidXMgMCB0YXJnZXQgMCBsdW4gMQpkYTE6IDxHZW5lcmljLSBTTS94RC1Q aWN0dXJlIDEuMDA+IFJlbW92YWJsZSBEaXJlY3QgQWNjZXNzIFNDU0ktMCBkZXZpY2UgCmRh MTogNDAuMDAwTUIvcyB0cmFuc2ZlcnMKZGExOiBBdHRlbXB0IHRvIHF1ZXJ5IGRldmljZSBz aXplIGZhaWxlZDogTk9UIFJFQURZLCBNZWRpdW0gbm90IHByZXNlbnQKZGEyIGF0IHVtYXNz LXNpbTAgYnVzIDAgdGFyZ2V0IDAgbHVuIDIKZGEyOiA8R2VuZXJpYy0gU0QvTU1DIDEuMDA+ IFJlbW92YWJsZSBEaXJlY3QgQWNjZXNzIFNDU0ktMCBkZXZpY2UgCmRhMjogNDAuMDAwTUIv cyB0cmFuc2ZlcnMKZGEyOiBBdHRlbXB0IHRvIHF1ZXJ5IGRldmljZSBzaXplIGZhaWxlZDog Tk9UIFJFQURZLCBNZWRpdW0gbm90IHByZXNlbnQKZGEzIGF0IHVtYXNzLXNpbTAgYnVzIDAg dGFyZ2V0IDAgbHVuIDMKZGEzOiA8R2VuZXJpYy0gTVMvTVMtUHJvIDEuMDA+IFJlbW92YWJs ZSBEaXJlY3QgQWNjZXNzIFNDU0ktMCBkZXZpY2UgCmRhMzogNDAuMDAwTUIvcyB0cmFuc2Zl cnMKZGEzOiBBdHRlbXB0IHRvIHF1ZXJ5IGRldmljZSBzaXplIGZhaWxlZDogTk9UIFJFQURZ LCBNZWRpdW0gbm90IHByZXNlbnQKVHJ5aW5nIHRvIG1vdW50IHJvb3QgZnJvbSBjZDk2NjA6 L2Rldi9pc285NjYwL0ZyZWVCU0Q3Cm1kNjAudXppcDogNDQ4MDAgeCAxNjM4NCBibG9ja3MK aXBmdzIgKCtpcHY2KSBpbml0aWFsaXplZCwgZGl2ZXJ0IGxvYWRhYmxlLCBydWxlLWJhc2Vk IGZvcndhcmRpbmcgZGlzYWJsZWQsIGRlZmF1bHQgdG8gZGVueSwgbG9nZ2luZyBkaXNhYmxl ZAo= --------------010906020902040906030204-- --------------enig0B4F2D47CCEEE59E86C1ABD2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHk+w4ldnAQVacBcgRAlQFAKCcOLr4pDN7eXOo9z3ZApM4rnKC2ACgmtQk txdaL0yOtfFIF9OWcexn9nc= =7dac -----END PGP SIGNATURE----- --------------enig0B4F2D47CCEEE59E86C1ABD2-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 05:22:55 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B67F416A41A for ; Mon, 21 Jan 2008 05:22:55 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.freebsd.org (Postfix) with ESMTP id 456F013C442 for ; Mon, 21 Jan 2008 05:22:55 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so248855nfb.33 for ; Sun, 20 Jan 2008 21:22:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=ngbpiP9nfro4nJyCNZbhbNezEohiEe9AawQa+UEyOBQ=; b=PgLRjQWcA/eSpnm/PwTeyZ1DUOUoRwWRhbZiHnq8Wj/qAZRVXHd5x2hCuAh2OWJof1IX8nY3gUh5N1PmnpdzYR1OpFz9eCFsZ1DikGkvU0J+X9h30b09W8LNcesRyiCLO/OFdaMsQadsZZGxQEti4VMqMzKKBz1an9b1uqCGSIA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ImUJepOQ9ZoyE3jgPFnIOIKogSoaDKBmRMIgcLKIJzHz8xikai0Vn2PuDWNPrImHnjBGAOhs40AlSBzoJIyR0Y49OHjwIsJTQFxIipGTH8v1XnoSVoWVPobbKI4v4vlMamTcMZr5X7zumdnycFilkOXt5/aGN64yIcsxShF4LdM= Received: by 10.78.149.15 with SMTP id w15mr8344685hud.72.1200892973052; Sun, 20 Jan 2008 21:22:53 -0800 (PST) Received: by 10.78.16.10 with HTTP; Sun, 20 Jan 2008 21:22:53 -0800 (PST) Message-ID: Date: Mon, 21 Jan 2008 08:22:53 +0300 From: pluknet To: "Bruce M Simpson" In-Reply-To: <479012F5.9050408@incunabulum.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <478B89F6.1010703@incunabulum.net> <479012F5.9050408@incunabulum.net> Cc: FreeBSD Current Subject: Re: exmap port - shared memory profiler X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 05:22:55 -0000 On 18/01/2008, Bruce M Simpson wrote: > pluknet wrote: > > As I can see this port depends on sysutil/pmap which is broken on 7.0. > > I just submitted PR with patch in it. Look at ports/119704, please. > > btw, procstat provides similar functionality when specified with -v flag. > > > Actually, procstat doesn't provide the functionality which > pmap_helper.ko or exmap does, although it is still a useful tool to have. > > I unfortunately don't have time to look at sysutils/pmap or do further > work on exmap at this moment, which is why I'm asking people for help as > they may also benefit from the tool. > > Thanks for the feedback! > BMS > I've slightly cleared exmap port to more working state. Now it compiles (with also patched sysutils/pmap) and all binaries from this port works (including gtk tool) on 7.0 (still not tested on 6.x and HEAD). It is accessible from http://pluknet.nm.ru/dev/exmap.tar.gz wbr, pluknet From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 05:34:50 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E73C16A417; Mon, 21 Jan 2008 05:34:50 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp2.yandex.ru (smtp2.yandex.ru [213.180.200.18]) by mx1.freebsd.org (Postfix) with ESMTP id 7B95A13C468; Mon, 21 Jan 2008 05:34:49 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mail.kirov.so-cdu.ru ([77.72.136.145]:14024 "EHLO [127.0.0.1]" smtp-auth: "bu7cher" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S4395421AbYAUFVy (ORCPT + 2 others); Mon, 21 Jan 2008 08:21:54 +0300 X-Yandex-Spam: 1 X-Yandex-Front: smtp2 X-Yandex-TimeMark: 1200892914 X-MsgDayCount: 5 X-Comment: RFC 2476 MSA function at smtp2.yandex.ru logged sender identity as: bu7cher Message-ID: <47942BEF.8030103@yandex.ru> Date: Mon, 21 Jan 2008 08:21:51 +0300 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: Volker References: <4792BC5E.4030703@vwsoft.com> In-Reply-To: <4792BC5E.4030703@vwsoft.com> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable , FreeBSD current , cokane@freebsd.org Subject: Re: patch for review: ATI SB600 SATA AHCI X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 05:34:50 -0000 Volker wrote: > If nobody complains until tuesday (2008-01-22), I'll file a PR for > that patch. Hi, there was several PR's and patches for ATI. http://lists.freebsd.org/pipermail/freebsd-current/2008-January/081982.html http://lists.freebsd.org/pipermail/freebsd-current/2007-November/079466.html http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/113195 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/118193 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/116125 I think Soren and Xin are busy and don't have time for do it. -- WBR, Andrey V. Elsukov From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 07:02:59 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9865616A41B for ; Mon, 21 Jan 2008 07:02:59 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.180]) by mx1.freebsd.org (Postfix) with ESMTP id 57A5B13C467 for ; Mon, 21 Jan 2008 07:02:59 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so3563858waf.3 for ; Sun, 20 Jan 2008 23:02:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:subject:message-id:reply-to:mime-version:content-type:content-disposition:user-agent; bh=tNJw9P+p3TEvPPcir8H3nMoeFPe23dQhkEPmi8RMrko=; b=djsVmlcVnVocJJHiyCj2yUp+NlvbCEmyzOcwNH4c4Dh1hoSD3sa1NaYaCZI/dZ1dpVGxLFlYfPmka9Lrqr07l0vw3x7bL+3mGZvs1Ak0e1xhQklIfL07WSOjkOTJqoZetpEcLKLQ3GB0M3THJB3MnU/aiQjUmjbhFNFnsqZ/Bt8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:reply-to:mime-version:content-type:content-disposition:user-agent; b=k2s9wJFP4mipvK9u7EsMuxNUfAoIduJWqZpydlsOi6kEfZXzQsj3OXS+yqLIyXGnXZvqxS8BrfqxAzGlaik7tSyhulDTn/+YMhjSY0lTqFEHLFcnqcMWXiJ+H7cmfS/plIiU6EVdjzJTAGvs4A0ZDSewyayIQRvuxxlJg0Dcahc= Received: by 10.114.184.7 with SMTP id h7mr3588184waf.28.1200898978331; Sun, 20 Jan 2008 23:02:58 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id m6sm10501041wag.11.2008.01.20.23.02.55 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 20 Jan 2008 23:02:57 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m0L72qiL006804 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 21 Jan 2008 16:02:52 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m0L72q7a006803 for freebsd-current@FreeBSD.org; Mon, 21 Jan 2008 16:02:52 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 21 Jan 2008 16:02:52 +0900 From: Pyun YongHyeon To: freebsd-current@FreeBSD.org Message-ID: <20080121070252.GC5499@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: HEADS UP! : sf(4) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jan 2008 07:02:59 -0000 Dear all, I've committed overhauled sf(4) to HEAD. Overhauled sf(4) has many performance improvements over previous version and supports Rx/Tx checksum offload with the help of firmware. Since I've changed very fundamental things such as descriptor formats in driver there could be unnoticed bugs in it. If you happen to encounter any issues related with sf(4) please let me know. I've included the commit message below. Overhaul sf(4) to make it run on all architectures and implement checksum offoload by downloading AIC-6915 firmware. Changes are o Header file cleanup. o Simplified probe logic. o s/u_int{8,16,32}_t/uint{8,16,32}_t/g o K&R -> ANSI C. o In register access function, added support both memory mapped and IO space register acccess. The function will dynamically detect which method would be choosed. o sf_setperf() was modified to support strict-alignment architectures. o Use SF_MII_DATAPORT instead of hardcoded value 0xffff. o Added link state/speed, duplex changes handling task q. The task q is also responsible for flow control settings. o Always hornor link up/down state reported by mii layers. The link state information is used in sf_start() to determine whether we got a valid link. o Added experimental flow-control setup. It was commented out but will be activated once we have flow-cotrol infrastructure in mii layer. o Simplify IFF_UP/IFCAP_POLLING and IFF_PROMISC handling logic. Rx filter always honors promiscuous mode. o Implemented suspend/resume methods. o Reorganized Rx filter routine so promiscuous mode changes doesn't require interface re-initialization. o Reimplemnted driver probe routine such that it looks for matching device from supported hardware list table. This change will help to add newer hardware revision to the driver. o Use ETHER_ADDR_LEN instead of hardcoded value. o Prefer memory space register mapping over I/O space as the hardware requires lots of register access to get various consumer/producer index. Failing to get memory space mapping, sf(4) falls back to I/O space mapping. Use of memory space register mapping requires somewhat large memory space(512K), though. o Switch to simpler bus_{read,write}_{1,2,4}. o Use PCIR_BAR macro to get BARs. o Program PCI cache line size if the cache line size was set to 0 and enable PCI MWI. o Add a new sysctl node 'dev.sf.N.stats' that shows various MAC counters for Rx/Tx statistics. o Add a sysctl node to configure interrupt moderation timer. The timer defers interrupts generation until time specified in timer control register is expired. The value in the timer register is in units of 102.4us. The allowable range for the timer is 0 - 31 (0 ~ 3.276ms). The default value is 1(102.4us). Users can change the timer value with dev.sf.N.int_mod sysctl(8) variable/loader(8) tunable. o bus_dma(9) conversion - Enable 64bit DMA addressing. - Enable 64bit descriptor format support. - Apply descriptor ring alignment requirements(256 bytes alignment). - Apply Rx buffer address alignment requirements(4 bytes alignment). - Apply 4GB boundary restrictions(Tx/Rx ring and its completion ring should live in the same 4GB address space.) - Set number of allowable number of DMA segments to 16. In fact, AIC-6915 doesn't have a limit for number of DMA segments but it would be waste of Tx descriptor resource if we allow more than 16. - Rx/Tx side bus_dmamap_load_mbuf_sg(9) support. - Added alignment fixup code for strict-alignment architectures. - Added endianness support code in Tx/Rx descriptor access. With these changes sf(4) should work on all platforms. o Don't set if_mtu in device attach, it's handled in ether_ifattach. o Use our own callout to drive watchdog timer. o Enable VLAN oversized frames and announce sf(4)'s VLAN capability to upper layer. o In sf_detach(), remove mtx_initialized KASSERT as it's not possible to get there without initialzing the mutex. Also mark that we're about to detaching so active bpf listeners do not panic the system. o To reduce PCI register access cycles, Rx completion ring is directly scanned instead of reading consumer/producer index registers. In theory, Tx completion ring also can be directly scanned. However the completion ring is composed of two types completion(1 for Tx done and 1 and DMA done). So reading producer index via register access would be more safer way to detect the ring wrap-around. o In sf_rxeof(), don't use m_devget(9) to align recevied frames. The alignment is required only for strict-alignment architectures and now the alignment is handled by sf_fixup_rx() if required. The removal of the copy operation in fast path should increase Rx performance a lot on non-strict-alignemnt architectures such as i386 and amd64. o In sf_newbuf(), don't set descriptor valid bit as sf(4) is programmed to run with normal mode. In normal mode, the valid bit have no meaning. The valid bit should be used only when the hardware uses polling(prefetch) mode. The end of descriptor queue bit could be used if needed, but sf(4) relys on auto-wrapping of hardware on 256 descriptor queue entries so both valid and descriptor end bit are not used anymore. o Don't disable generation of Tx DMA completion as said in datasheet and use the Tx DMA completion entry instead of relying on Tx done completion entry. Also added additional Tx completion entry type check in Tx completion handler. o Don't blindly reset watchdog timer in sf_txeof(). sf(4) now unarm the the watchdog only if there are no active Tx descriptors in Tx queue. o Don't manually update various counters in driver, instead, use built-in MAC statistic registers to update them. The statistic registers are updated in every second. o Modified Tx underrun handlers to increase the threshold value in units of 256 bytes. Previously it used to increase 16 bytes at a time which seems to take too long to stabalize whenever Tx underrun occurrs. o In interrupt handler, additional check for the interrupt is performed such that interrupts only for this device is allowed to process descriptor rings. Because reading SF_ISR register clears all interrtups, nuke writing to a SF_ISR register. o Tx underrun is abonormal condition and SF_ISR_ABNORMALINTR includes the interrupt. So there is no need to inspect the Tx underrun again in main interrupt loop. o Don't blindly reinitialize hardware for abnormal interrupt condition. sf(4) reintializes the hardware only when it encounters DMA error which requires an explicit hardware reinitialization. o Fix a long standing bug that incorrectly clears MAC statistic registers in sf_init_locked. o Added strict-alignment safe way of ethernet address reprogramming as IF_LLADDR may return unaligned address. o Move sf_reset() to sf_init_locked in order to always reset the hardware to a known state prior to configuring hardware. o Set default Rx DMA, Tx DMA paramters as shown in datasheet. o Enable PCI busmaster logic and autopadding for VLAN frames. o Rework sf_encap. - Previously sf(4) used to type 0 of Tx descriptor with padding enabled to store driver private data. Emebedding private data structures into descriptors is bad idea as the structure size would be different between 64bit and 32bit architectures. The type 0 descriptor allows fixed number of DMA segments in a descriptor format and provides relatively simple interface to manage multi-fragmented frames. However, it wastes lots of Tx descriptors as not all frames are fragmented as the number of allowable segments in a descriptor. - To overcome the limitation of type 0 descriptor, switch to type 2 descriptor which allows 64bit DMA addressing and can handle unliumited number of fragmented DMA segments. The drawback of type 2 descriptor is in its complexity in managing descriptors as driver should handle the end of Tx ring manually. - Manually set Tx desciptor queue end mark and record number of used descriptors to reclaim used descriptors in sf_txeof(). o Rework sf_start. - Honor link up/down state before attempting transmission. - Because sf(4) uses only one of two Tx queues, use low priority queue instead of high one. This will remove one shift operation in each Tx kick command. - Cache last produder index into softc such that subsequenet Tx operation doesn't need to access producer index register. o Rewrote sf_stats_update to include all available MAC statistic counters. o Employ AIC-6915 firmware from Adaptec and implement firmware download routine and TCP/UDP checksum offload. Partial checksum offload support was commented out due to the possibility of firmware bug in RxGFP. The firmware can strip VLAN tag in Rx path but the lack of firmware assistance of VLAN tag insertion in transmit side made it useless on FreeBSD. Unlike checksum offload, FreeBSD requires both Tx/Rx hardware VLAN assistance capability. The firmware may also detect wakeup frame and can wake system up from states other than D0. However, the lack of wakeup support form D3cold state keep me from adding WOL capability. Also detecting WOL frame requires firmware support but it's not yet known to me whether the firmware can process the WOL frame. o Changed *_ADDR_HIADDR to *_ADDR_HI to match other definitions of registers. o Added definitioan to interrupt moderation related constants. o Redefined SF_INTRS to include Tx DMA done and DMA errors. Removed Tx done as it's not needed anymore. o Added definition for Rx/Tx DMA high priority threshold. o Nuked unused marco SF_IDX_LO, SF_IDX_HI. o Added complete MAC statistic register definition. o Modified sf_stats structure to hold all MAC statistic regiters. o Nuke various driver private padding data in Tx/Rx descriptor definition. sf(4) no longer requires private padding. Also remove unused padding related definitions. This greatly simplifies descriptor manipulation on 64bit architectures. o Becase we no longer pad driver private data into descriptor, remove deprecated/not-applicable comments for padding. o Redefine Rx/Tx desciptor status. sf(4) doesn't use bit fileds anymore to support endianness. Tested by: bruffer (initial version) Thanks. -- Regards, Pyun YongHyeon From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 08:09:52 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EEE2A16A420; Mon, 21 Jan 2008 08:09:52 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id A3DD413C455; Mon, 21 Jan 2008 08:09:52 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from homeKamikaze.norad (nat-wh-1.rz.uni-karlsruhe.de [129.13.72.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 52396405CA3; Mon, 21 Jan 2008 09:09:50 +0100 (CET) Message-ID: <4794534C.1040306@bsdforen.de> Date: Mon, 21 Jan 2008 09:09:48 +0100 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.9 (X11/20071203) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <478556AD.6090400@bsdforen.de> In-Reply-To: <478556AD.6090400@bsdforen.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD's problems as seen by the BSDForen.de community X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 08:09:53 -0000 Herewith I apologize for starting this thread. It caused a lot of useless noise on your lists and while our members have spent months intensively discussing the topic, they are now very reluctant about acquiring the information necessary to find the source of their problems. I regret the work reading through a whole (large) forum thread and coming up with a summary and I am sorry for wasting so much of all your time. Regards Dominic Fandrey From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 09:25:14 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF86C16A417; Mon, 21 Jan 2008 09:25:13 +0000 (UTC) (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 B827C13C45A; Mon, 21 Jan 2008 09:25:13 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.14.2/8.14.2) with ESMTP id m0L9PCbD052412; Mon, 21 Jan 2008 04:25:12 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.14.2/8.14.1) with ESMTP id m0L9PCXC067609; Mon, 21 Jan 2008 04:25:12 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 651F173039; Mon, 21 Jan 2008 04:25:12 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080121092512.651F173039@freebsd-current.sentex.ca> Date: Mon, 21 Jan 2008 04:25:12 -0500 (EST) X-Virus-Scanned: ClamAV 0.92/5493/Thu Jan 17 13:09:26 2008 clamav-milter version 0.91.2 on clamscanner2 X-Virus-Status: Clean 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: Mon, 21 Jan 2008 09:25:14 -0000 TB --- 2008-01-21 07:45:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-01-21 07:45:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-01-21 07:45:00 - cleaning the object tree TB --- 2008-01-21 07:45:51 - cvsupping the source tree TB --- 2008-01-21 07:45:51 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-01-21 07:45:57 - building world (CFLAGS=-O -pipe) TB --- 2008-01-21 07:45:57 - cd /src TB --- 2008-01-21 07:45:57 - /usr/bin/make -B buildworld >>> World build started on Mon Jan 21 07:46:00 UTC 2008 >>> 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 >>> World build completed on Mon Jan 21 09:19:39 UTC 2008 TB --- 2008-01-21 09:19:39 - generating LINT kernel config TB --- 2008-01-21 09:19:39 - cd /src/sys/amd64/conf TB --- 2008-01-21 09:19:39 - /usr/bin/make -B LINT TB --- 2008-01-21 09:19:39 - building LINT kernel (COPTFLAGS=) TB --- 2008-01-21 09:19:39 - cd /src TB --- 2008-01-21 09:19:39 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Jan 21 09:19:39 UTC 2008 >>> 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 -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -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 -pg -mprofiler-epilogue /src/sys/dev/scc/scc_dev_sab82532.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -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 -pg -mprofiler-epilogue /src/sys/dev/scc/scc_dev_z8530.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -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 -pg -mprofiler-epilogue /src/sys/dev/scd/scd.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -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 -pg -mprofiler-epilogue /src/sys/dev/scd/scd_isa.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -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 -pg -mprofiler-epilogue /src/sys/dev/sf/if_sf.c /src/sys/dev/sf/if_sf.c: In function 'sf_poll': /src/sys/dev/sf/if_sf.c:1826: error: 'struct sf_stats' has no member named 'tx_gfp_stall' /src/sys/dev/sf/if_sf.c:1832: error: 'struct sf_stats' has no member named 'rx_gfp_stall' *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-01-21 09:25:12 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-01-21 09:25:12 - ERROR: failed to build lint kernel TB --- 2008-01-21 09:25:12 - tinderbox aborted TB --- 4184.54 user 533.93 system 6011.74 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 09:52:41 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2091F16A417 for ; Mon, 21 Jan 2008 09:52:41 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by mx1.freebsd.org (Postfix) with ESMTP id D322313C448 for ; Mon, 21 Jan 2008 09:52:40 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so3645490waf.3 for ; Mon, 21 Jan 2008 01:52:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=hS7uc4iumL0nxYuj9RCB5nsrqwfQC5c2L2/aJVpkQXA=; b=YV3Cxqq/JUFUJvz6Fn+B0ZSXwUX6kHO8j92F0kkjaNnW23KcPXotBs+2uJzUpqb7EXwbrbTQMQeCMaZmjOzJI/TTCbQqVSd14SqquneP7tkUQu0icHv+NsU7jKt2m1TZ9XHV/e1YLwhdwV+YfsQVdP9N0poOisveGZLuwltyx5o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=WvSLhOsJRFJPPN8Wzjht+OHSGdsgpCG327bkWUhlTsIK8oqAWZDZwLawSN5FkT7PQ2ZAamQlYzjNy5m03eg6REH8C7zBhDyjB+Zp5Z7SwV0CIMAOt3pfAPL8GTbXuNyiRLDDQO3njg9LqV/RxgGqZ6csffDHhA4XzcsewLEt1GY= Received: by 10.114.110.12 with SMTP id i12mr7783069wac.73.1200909160446; Mon, 21 Jan 2008 01:52:40 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id v37sm14745852wah.12.2008.01.21.01.52.37 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Jan 2008 01:52:39 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m0L9qXP2007310 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 Jan 2008 18:52:33 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m0L9qWEt007309; Mon, 21 Jan 2008 18:52:32 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 21 Jan 2008 18:52:32 +0900 From: Pyun YongHyeon To: FreeBSD Tinderbox Message-ID: <20080121095232.GE5499@cdnetworks.co.kr> References: <20080121092512.651F173039@freebsd-current.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080121092512.651F173039@freebsd-current.sentex.ca> User-Agent: Mutt/1.4.2.1i Cc: amd64@freebsd.org, current@freebsd.org Subject: Re: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jan 2008 09:52:41 -0000 On Mon, Jan 21, 2008 at 04:25:12AM -0500, FreeBSD Tinderbox wrote: > TB --- 2008-01-21 07:45:00 - tinderbox 2.3 running on freebsd-current.sentex.ca > TB --- 2008-01-21 07:45:00 - starting HEAD tinderbox run for amd64/amd64 > TB --- 2008-01-21 07:45:00 - cleaning the object tree > TB --- 2008-01-21 07:45:51 - cvsupping the source tree > TB --- 2008-01-21 07:45:51 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile > TB --- 2008-01-21 07:45:57 - building world (CFLAGS=-O -pipe) > TB --- 2008-01-21 07:45:57 - cd /src > TB --- 2008-01-21 07:45:57 - /usr/bin/make -B buildworld > >>> World build started on Mon Jan 21 07:46:00 UTC 2008 > >>> 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 > >>> World build completed on Mon Jan 21 09:19:39 UTC 2008 > TB --- 2008-01-21 09:19:39 - generating LINT kernel config > TB --- 2008-01-21 09:19:39 - cd /src/sys/amd64/conf > TB --- 2008-01-21 09:19:39 - /usr/bin/make -B LINT > TB --- 2008-01-21 09:19:39 - building LINT kernel (COPTFLAGS=) > TB --- 2008-01-21 09:19:39 - cd /src > TB --- 2008-01-21 09:19:39 - /usr/bin/make -B buildkernel KERNCONF=LINT > >>> Kernel build for LINT started on Mon Jan 21 09:19:39 UTC 2008 > >>> 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 -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -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 -pg -mprofiler-epilogue /src/sys/dev/scc/scc_dev_sab82532.c > cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -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 -pg -mprofiler-epilogue /src/sys/dev/scc/scc_dev_z8530.c > cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -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 -pg -mprofiler-epilogue /src/sys/dev/scd/scd.c > cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -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 -pg -mprofiler-epilogue /src/sys/dev/scd/scd_isa.c > cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -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 -pg -mprofiler-epilogue /src/sys/dev/sf/if_sf.c > /src/sys/dev/sf/if_sf.c: In function 'sf_poll': > /src/sys/dev/sf/if_sf.c:1826: error: 'struct sf_stats' has no member named 'tx_gfp_stall' > /src/sys/dev/sf/if_sf.c:1832: error: 'struct sf_stats' has no member named 'rx_gfp_stall' > *** Error code 1 > > Stop in /obj/amd64/src/sys/LINT. > *** Error code 1 > > Stop in /src. > *** Error code 1 > > Stop in /src. > TB --- 2008-01-21 09:25:12 - WARNING: /usr/bin/make returned exit code 1 > TB --- 2008-01-21 09:25:12 - ERROR: failed to build lint kernel > TB --- 2008-01-21 09:25:12 - tinderbox aborted > TB --- 4184.54 user 533.93 system 6011.74 real > Should be fixed now. I should have rechecked polling case again after chainging variable name. Sorry. -- Regards, Pyun YongHyeon From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 09:59:32 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5B2B16A473; Mon, 21 Jan 2008 09:59:32 +0000 (UTC) (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 6523C13C4E3; Mon, 21 Jan 2008 09:59:32 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m0L9xVZt047685; Mon, 21 Jan 2008 04:59:31 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.14.2/8.14.1) with ESMTP id m0L9xVLA078024; Mon, 21 Jan 2008 04:59:31 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 5A60F73039; Mon, 21 Jan 2008 04:59:31 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080121095931.5A60F73039@freebsd-current.sentex.ca> Date: Mon, 21 Jan 2008 04:59:31 -0500 (EST) X-Virus-Scanned: ClamAV 0.92/5493/Thu Jan 17 13:09:26 2008 clamav-milter version 0.91.1 on clamscanner3 X-Virus-Status: Clean 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: Mon, 21 Jan 2008 09:59:32 -0000 TB --- 2008-01-21 08:51:18 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-01-21 08:51:18 - starting HEAD tinderbox run for i386/i386 TB --- 2008-01-21 08:51:18 - cleaning the object tree TB --- 2008-01-21 08:51:46 - cvsupping the source tree TB --- 2008-01-21 08:51:46 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/i386/i386/supfile TB --- 2008-01-21 08:51:52 - building world (CFLAGS=-O -pipe) TB --- 2008-01-21 08:51:52 - cd /src TB --- 2008-01-21 08:51:52 - /usr/bin/make -B buildworld >>> World build started on Mon Jan 21 08:51:54 UTC 2008 >>> 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 >>> World build completed on Mon Jan 21 09:53:31 UTC 2008 TB --- 2008-01-21 09:53:31 - generating LINT kernel config TB --- 2008-01-21 09:53:31 - cd /src/sys/i386/conf TB --- 2008-01-21 09:53:31 - /usr/bin/make -B LINT TB --- 2008-01-21 09:53:31 - building LINT kernel (COPTFLAGS=) TB --- 2008-01-21 09:53:31 - cd /src TB --- 2008-01-21 09:53:31 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Jan 21 09:53:31 UTC 2008 >>> 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 -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -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 -pg -mprofiler-epilogue /src/sys/dev/scc/scc_dev_sab82532.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -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 -pg -mprofiler-epilogue /src/sys/dev/scc/scc_dev_z8530.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -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 -pg -mprofiler-epilogue /src/sys/dev/scd/scd.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -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 -pg -mprofiler-epilogue /src/sys/dev/scd/scd_isa.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -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 -pg -mprofiler-epilogue /src/sys/dev/sf/if_sf.c /src/sys/dev/sf/if_sf.c: In function 'sf_poll': /src/sys/dev/sf/if_sf.c:1826: error: 'struct sf_stats' has no member named 'tx_gfp_stall' /src/sys/dev/sf/if_sf.c:1832: error: 'struct sf_stats' has no member named 'rx_gfp_stall' *** Error code 1 Stop in /obj/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-01-21 09:59:31 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-01-21 09:59:31 - ERROR: failed to build lint kernel TB --- 2008-01-21 09:59:31 - tinderbox aborted TB --- 3047.23 user 376.62 system 4093.32 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 10:32:41 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC6B316A418; Mon, 21 Jan 2008 10:32:41 +0000 (UTC) (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 8147C13C468; Mon, 21 Jan 2008 10:32:41 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m0LAWfZh049206; Mon, 21 Jan 2008 05:32:41 -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.14.2/8.14.1) with ESMTP id m0LAWeIo018065; Mon, 21 Jan 2008 05:32:40 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id C8F4073039; Mon, 21 Jan 2008 05:32:40 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080121103240.C8F4073039@freebsd-current.sentex.ca> Date: Mon, 21 Jan 2008 05:32:40 -0500 (EST) X-Virus-Scanned: ClamAV 0.92/5493/Thu Jan 17 13:09:26 2008 clamav-milter version 0.91.2 on clamscanner1 X-Virus-Status: Clean 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: Mon, 21 Jan 2008 10:32:42 -0000 TB --- 2008-01-21 09:25:12 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-01-21 09:25:12 - starting HEAD tinderbox run for i386/pc98 TB --- 2008-01-21 09:25:12 - cleaning the object tree TB --- 2008-01-21 09:25:38 - cvsupping the source tree TB --- 2008-01-21 09:25:38 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/i386/pc98/supfile TB --- 2008-01-21 09:25:45 - building world (CFLAGS=-O -pipe) TB --- 2008-01-21 09:25:45 - cd /src TB --- 2008-01-21 09:25:45 - /usr/bin/make -B buildworld >>> World build started on Mon Jan 21 09:25:46 UTC 2008 >>> 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 >>> World build completed on Mon Jan 21 10:27:26 UTC 2008 TB --- 2008-01-21 10:27:26 - generating LINT kernel config TB --- 2008-01-21 10:27:26 - cd /src/sys/pc98/conf TB --- 2008-01-21 10:27:26 - /usr/bin/make -B LINT TB --- 2008-01-21 10:27:26 - building LINT kernel (COPTFLAGS=) TB --- 2008-01-21 10:27:26 - cd /src TB --- 2008-01-21 10:27:26 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Jan 21 10:27:26 UTC 2008 >>> 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 -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -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 -pg -mprofiler-epilogue /src/sys/dev/scc/scc_dev_sab82532.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -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 -pg -mprofiler-epilogue /src/sys/dev/scc/scc_dev_z8530.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -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 -pg -mprofiler-epilogue /src/sys/dev/scd/scd.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -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 -pg -mprofiler-epilogue /src/sys/dev/scd/scd_isa.c cc -c -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -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 -pg -mprofiler-epilogue /src/sys/dev/sf/if_sf.c /src/sys/dev/sf/if_sf.c: In function 'sf_poll': /src/sys/dev/sf/if_sf.c:1826: error: 'struct sf_stats' has no member named 'tx_gfp_stall' /src/sys/dev/sf/if_sf.c:1832: error: 'struct sf_stats' has no member named 'rx_gfp_stall' *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-01-21 10:32:40 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-01-21 10:32:40 - ERROR: failed to build lint kernel TB --- 2008-01-21 10:32:40 - tinderbox aborted TB --- 2978.24 user 378.34 system 4048.28 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-pc98.full From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 11:52:28 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DCC5E16A418 for ; Mon, 21 Jan 2008 11:52:28 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:610:652::211]) by mx1.freebsd.org (Postfix) with ESMTP id A6B3613C478 for ; Mon, 21 Jan 2008 11:52:28 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id F02491CD79; Mon, 21 Jan 2008 12:52:27 +0100 (CET) Date: Mon, 21 Jan 2008 12:52:27 +0100 From: Ed Schouten To: FreeBSD Current Message-ID: <20080121115227.GR67081@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="v4cNTr+tRGSs1txX" Content-Disposition: inline User-Agent: Mutt/1.5.17 (2007-11-01) Subject: cnclose() doesn't actually call TTY's close routines X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 11:52:28 -0000 --v4cNTr+tRGSs1txX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello everyone, This morning I discovered a very strange bug this morning on my FreeBSD box and I think even RELENG_6 has this issue. Here's what you do: - Make sure you've got a kernel with all the debugging options enabled, so free() writes all 0xdeadc0de's in memory. - Boot your box and make sure it has been running for a couple of minutes (fsck is already finished, etc). - Now run `pstat -t'. If you look at consolectl's entry (the boot console device of syscons), you'll (hopefully) see that its session ID is -559038242, which is 0xdeadc0de. I already tried to track it down and I think I understand where things go wrong. In /sys/kern/tty_cons.c there are wrappers around individual cdevsw's to multiplex console output to multiple terminal devices. In the cnclose() routines, it calls vn_close() on all the terminal devices in the list, which makes sense. But for some reason, vn_close() eventually doesn't call scclose(). It isn't a real problem, because nobody runs TIOCSCTTY on /dev/console and pstat(8) only displays some info in that structure, but it should be fixed I guess. I'll take a look at this one of these days, but it will probably be quite hard for me, because I'm not really familiar with the VFS's design. --=20 Ed Schouten WWW: http://g-rave.nl/ --v4cNTr+tRGSs1txX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEARECAAYFAkeUh3sACgkQ52SDGA2eCwVJ0gCeJBE0qgO7LiLsbR6Cg2TJeAMu dncAnjagb+dtp11Ur7DPoSuUxfhVtrfq =vH3r -----END PGP SIGNATURE----- --v4cNTr+tRGSs1txX-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 12:49:23 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9ED2C16A419 for ; Mon, 21 Jan 2008 12:49:23 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:610:652::211]) by mx1.freebsd.org (Postfix) with ESMTP id 6715C13C455 for ; Mon, 21 Jan 2008 12:49:23 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id B721E1CD79; Mon, 21 Jan 2008 13:49:22 +0100 (CET) Date: Mon, 21 Jan 2008 13:49:22 +0100 From: Ed Schouten To: FreeBSD Current Message-ID: <20080121124922.GS67081@hoeg.nl> References: <20080121115227.GR67081@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XMM+kVNHGkMezEqK" Content-Disposition: inline In-Reply-To: <20080121115227.GR67081@hoeg.nl> User-Agent: Mutt/1.5.17 (2007-11-01) Subject: Re: cnclose() doesn't actually call TTY's close routines X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 12:49:23 -0000 --XMM+kVNHGkMezEqK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Ed Schouten wrote: > It isn't a real problem, because nobody runs TIOCSCTTY on /dev/console > and pstat(8) only displays some info in that structure, but it should be > fixed I guess. I'll take a look at this one of these days, but it will > probably be quite hard for me, because I'm not really familiar with the > VFS's design. Ah, I guess I figured it out. It doesn't happen on systems where moused isn't running. moused opens /dev/consolectl on startup and leaves it open during its lifetime. When cnclose() calls vn_close(), it won't run the TTY's close routine because /dev/consolectl is used multiple times. This means that when a TTY is opened by multiple processes (quite common), the session will be unset when all users are gone, not when session itself is being released. This could cause scary things, for example in ttymodem() when a SIGHUP is sent to the session leader. This could be fixed by adding a ttysessrel(), which basically performs a ttyrel(), but also unsets the t_session. I'll take a look at this next month, when I'll be working on FreeBSD full-time. :-) Yours, --=20 Ed Schouten WWW: http://g-rave.nl/ --XMM+kVNHGkMezEqK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEARECAAYFAkeUlNIACgkQ52SDGA2eCwU2PwCeKutXGJowVOoybSWl9VzoFpwm WKIAn1g9ifk8pfyy4CFjpqlLbDs4f58i =YVHG -----END PGP SIGNATURE----- --XMM+kVNHGkMezEqK-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 12:55:19 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3AD0616A468 for ; Mon, 21 Jan 2008 12:55:19 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.freebsd.org (Postfix) with ESMTP id 1540113C474 for ; Mon, 21 Jan 2008 12:55:16 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.4) with ESMTP id m0LCO3hR063987; Mon, 21 Jan 2008 15:24:03 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.4/Submit) id m0LCO2Vj063982; Mon, 21 Jan 2008 15:24:02 +0300 (MSK) (envelope-from yar) Date: Mon, 21 Jan 2008 15:24:02 +0300 From: Yar Tikhiy To: Jeff Roberson Message-ID: <20080121122402.GA63088@comp.chem.msu.su> References: <20071120141403.GE81260@comp.chem.msu.su> <4743342A.10507@FreeBSD.org> <20080101185451.S957@desktop> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080101185451.S957@desktop> User-Agent: Mutt/1.5.9i Cc: Kris Kennaway , freebsd-current@FreeBSD.org Subject: Re: SCHED_ULE & niceness / rtprio X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 12:55:19 -0000 On Tue, Jan 01, 2008 at 06:56:59PM -1000, Jeff Roberson wrote: > On Tue, 20 Nov 2007, Kris Kennaway wrote: > > >Yar Tikhiy wrote: > >>Hi all, > >> > >>SCHED_ULE seems to do an unfair job to processes with low niceness > >>or with real-time priority. Here are my observations: > >> > >>A few days ago I noticed that music (played by Totem, Gnome's default > >>player) would pause for a fraction of second each time I did something > >>in X/Gnome, such as switched between windows, clicked on a link in > >>the web browser, etc. Then I found that music was jerky only if > >>the player ran with a negative niceness or a real-time priority: > >>As soon as I returned it to niceness 0 and normal priority, sound > >>became totally seamless notwithstanding my activity in X. > >> > >>The approximate value required for the effect to appear was niceness > >>as low as -5 or RT priority as high as 10; niceness -1 or rtprio 1 > >>wasn't enough. > >> > >>Curious, I substituted SCHED_4BSD for SCHED_ULE in my otherwise > >>GENERIC kernel, and the jerkiness of sound was gone irrespective > >>of the niceness or RT priority of the player. > >> > >>To rule out other possible causes, I also tried kernels with SCHED_ULE > >>but without SMP or without debug stuff (INVARIANTS+WITNESS), but > >>the issue was there in both cases, unlike in the case of SCHED_4BSD. > >> > >>Of course, X+Gnome+stuff isn't the clearest environment for debugging > >>schedulers, but multimedia apps are rather sensitive to scheduling > >>quality. This case should be rather obvious: When I click in an > >>inactive window, some processes are woken that have been idle. > >>After that the high-priority player isn't scheduled long enough for > >>the hardware audo buffer to drain, although it would be scheduled > >>soon if it had normal priority. > >> > >>Did I hit a known issue? > > > >Others have reported it, but I don't know if Jeff has had time to > >investigate yet. > > > > I tried to reproduce this recently by running mplayer with various nice > values while scrolling around a lot in firefox. This is on a 1.4ghz > machine. I didn't encounter any problems. Well, scrolling around might not trigger the problem. The issue might be seen, or heard, better when different processes are being woken up. > If anyone is having nice related problems with ULE I'd love a simple test > case that shows it. I tried installing boinc which was mentioned in other > threads but had trouble contacting the servers and getting it setup. > Something simpler would be very beneficial. Today I've finally got a chance to update my workstation to the latest HEAD and try again in order to see if your last patch has any effect for my issue. Alas, it doesn't, sorry. My environment: GNOME 2 out of the box, namely as installed from the gnome2-lite port. That includes Firefox and Totem player. What I did: was switching between windows of different apps (Firefox, Terminal) via Alt+Tab, or between virtual desktops with some windows on them using mouse, while playing an mp3 tune in the Totem player. What I also noticed was that assigning an idle priority to the player makes the sound falter as well. I.e., the sound is smooth only when the player runs at normal priority and zero, or numerically greater, niceness. Lastly, I think I've found a simpler test case. Attached is a proglet that essentially simulates the load pattern by waking up periodically and doing dummy things. In my case (1GHz CPU,) 4-6 instances of it running in the background are enough to make the issue manifest itself: When I assign an RT/idle priority or negative niceness to the player process, it starts to stutter, but as soon as I return the player process to normal priority & niceness, it plays fluently again. I haven't found a suitable detector other than a media player yet. However, in my case, madplay is as good as Totem in detecting the presumable scheduling problem, from which I infer that any audio player will do, including command-line ones. Sorry, I can't test this against mplayer now as my ADSL line is temporarily down and I have to resort to dial-up, so downloading mplayer isn't an option for me now. :-) -- Yar #include #include #include #include #include const int n = 10 * 1024 * 1024; /* how many bytes of RAM to burn */ const int v = 0; /* verbose flag */ int main() { struct timespec ts0, ts; char *p; long dn, ds; int i; for (;;) { if (v) clock_gettime(CLOCK_MONOTONIC, &ts0); if ((p = malloc(n)) != NULL) { for (i = 0; i < n; i++) p[i] = (char)(i % 53); /* just a prime number */ free(p); } if (v) { clock_gettime(CLOCK_MONOTONIC, &ts); ds = ts.tv_sec - ts0.tv_sec; dn = ts.tv_nsec - ts0.tv_nsec; if (dn < 0) { ds--; dn += 1000 * 1000 * 1000L; } if (dn < 0 || ds < 0) abort(); printf("last run took %ld.%09ld sec\n", ds, dn); } /* sleep 1-2 sec */ usleep(1000 * 1000L + random() % (1000 * 1000L)); } } From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 15:39:38 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7235116A418 for ; Mon, 21 Jan 2008 15:39:38 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.239]) by mx1.freebsd.org (Postfix) with ESMTP id 3357913C46A for ; Mon, 21 Jan 2008 15:39:38 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by wx-out-0506.google.com with SMTP id i29so1051345wxd.7 for ; Mon, 21 Jan 2008 07:39:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=ToXneElEqSri1Iu9n+geCGOdYJHKWHzg3VjhqJfYpZY=; b=pD+mvgzE9MEDSFNv071D9moBZ7idSrIV6bs1h7dqWabkDZ9FTJTmSzWLgVcYlYGy0QKDy7J1oplNs7kI4KiiJBgGypl7FST/N/YXYAJcqarUhSOV4ifUOF8S5pGwXWjhJsaixZeavWGaoO/AipHnx3T5P6xN51A/KmDCojvDJVY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=Olx19rR42HG1mYvH8QKs9/mRnvZaH2wk6rs3Da6jBDVPbVXQ/uo1zwudbjq2iWw0xAN8k1VdHq7DVdoRQSgpWNTSn7pMi/qBh1Lr53T0pd3OcPmaPRgsgX4fVq47wk5WGUArXvvjyw46/i2dbakx5Uvcb9g5nnUTC1chfo8k63U= Received: by 10.142.50.15 with SMTP id x15mr3234324wfx.169.1200929976788; Mon, 21 Jan 2008 07:39:36 -0800 (PST) Received: by 10.142.178.11 with HTTP; Mon, 21 Jan 2008 07:39:36 -0800 (PST) Message-ID: <3a142e750801210739v7db696e4hde8ec4fce717d628@mail.gmail.com> Date: Mon, 21 Jan 2008 15:39:36 +0000 From: "Paul B. Mahol" To: freebsd-current MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: bsdlabel 26 partitions X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 15:39:38 -0000 As I read from here: http://lists.freebsd.org/pipermail/cvs-src/2007-December/084949.html This change actually does not do anything, because kernel still operate with 8 partitions. ==> sys/sys/disklabel.h MAXPARTITIONS 8 I have some trivial patches, but there appears to be problem with compatibility with old partitions table. (new kernel will not boot root partition with old world, but inside qemu, with installation of new world and new kernel at once, booting works fine - except that there are to many /dev/ads1* entries - false positives) But on newly created partitions with bsdlabel inside qemu there is of course no false positives (there are correct numbers of partitions). From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 15:53:50 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCF3716A468 for ; Mon, 21 Jan 2008 15:53:50 +0000 (UTC) (envelope-from astrodog@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.235]) by mx1.freebsd.org (Postfix) with ESMTP id 76AA213C457 for ; Mon, 21 Jan 2008 15:53:50 +0000 (UTC) (envelope-from astrodog@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so1046246nzf.13 for ; Mon, 21 Jan 2008 07:53:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=FYj1ro54ubV7UYOxycHFwXO9YVR/YgG1Y7FaO9TGEEA=; b=OjCAz0EYpU+lgmtK7q42N6PMdtOE3Z1HX+GlV+6RawUc1wgi1z1kqzpdRIxcOQ6xPU7LyucGavywcmCTwSKy30RF6OSD13CfYZfbN/epilMajy/ljBQpATQA2z+f3PT0CFrVpPKXN5rGs+l3l08rTkhO5Tu0hBoF6mjcph3xZW8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Ws/UKxdAizbT/dn1Pt4YL1ZbuqCsaDxn6nNeLW9PYpSvL70arj/YpJV62Onx2lf/TP0OJ/aoUniV58DmvIy2zxnmzTpkaVfk9BZycCOmE/ujvUso2fhj1oExJOURph+hF2b+a8sk0fo3+/hl8kALyp7KaQPgRHCSf+mvOAiUfP8= Received: by 10.141.15.19 with SMTP id s19mr4537237rvi.205.1200930829165; Mon, 21 Jan 2008 07:53:49 -0800 (PST) Received: by 10.141.68.21 with HTTP; Mon, 21 Jan 2008 07:53:49 -0800 (PST) Message-ID: <2fd864e0801210753y3fc49cd5v67ca75e0376bdb21@mail.gmail.com> Date: Mon, 21 Jan 2008 23:53:49 +0800 From: Astrodog To: "Yar Tikhiy" In-Reply-To: <20080121122402.GA63088@comp.chem.msu.su> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071120141403.GE81260@comp.chem.msu.su> <4743342A.10507@FreeBSD.org> <20080101185451.S957@desktop> <20080121122402.GA63088@comp.chem.msu.su> Cc: Jeff Roberson , freebsd-current@freebsd.org Subject: Re: SCHED_ULE & niceness / rtprio X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 15:53:50 -0000 On Jan 21, 2008 8:24 PM, Yar Tikhiy wrote: > > On Tue, Jan 01, 2008 at 06:56:59PM -1000, Jeff Roberson wrote: > > On Tue, 20 Nov 2007, Kris Kennaway wrote: > > > > >Yar Tikhiy wrote: > > >>Hi all, > > >> > > >>SCHED_ULE seems to do an unfair job to processes with low niceness > > >>or with real-time priority. Here are my observations: > > >> > > >>A few days ago I noticed that music (played by Totem, Gnome's default > > >>player) would pause for a fraction of second each time I did something > > >>in X/Gnome, such as switched between windows, clicked on a link in > > >>the web browser, etc. Then I found that music was jerky only if > > >>the player ran with a negative niceness or a real-time priority: > > >>As soon as I returned it to niceness 0 and normal priority, sound > > >>became totally seamless notwithstanding my activity in X. > > >> > > >>The approximate value required for the effect to appear was niceness > > >>as low as -5 or RT priority as high as 10; niceness -1 or rtprio 1 > > >>wasn't enough. > > >> > > >>Curious, I substituted SCHED_4BSD for SCHED_ULE in my otherwise > > >>GENERIC kernel, and the jerkiness of sound was gone irrespective > > >>of the niceness or RT priority of the player. > > >> > > >>To rule out other possible causes, I also tried kernels with SCHED_ULE > > >>but without SMP or without debug stuff (INVARIANTS+WITNESS), but > > >>the issue was there in both cases, unlike in the case of SCHED_4BSD. > > >> > > >>Of course, X+Gnome+stuff isn't the clearest environment for debugging > > >>schedulers, but multimedia apps are rather sensitive to scheduling > > >>quality. This case should be rather obvious: When I click in an > > >>inactive window, some processes are woken that have been idle. > > >>After that the high-priority player isn't scheduled long enough for > > >>the hardware audo buffer to drain, although it would be scheduled > > >>soon if it had normal priority. > > >> > > >>Did I hit a known issue? > > > > > >Others have reported it, but I don't know if Jeff has had time to > > >investigate yet. > > > > > > > I tried to reproduce this recently by running mplayer with various nice > > values while scrolling around a lot in firefox. This is on a 1.4ghz > > machine. I didn't encounter any problems. > > Well, scrolling around might not trigger the problem. The issue might > be seen, or heard, better when different processes are being woken up. > > > If anyone is having nice related problems with ULE I'd love a simple test > > case that shows it. I tried installing boinc which was mentioned in other > > threads but had trouble contacting the servers and getting it setup. > > Something simpler would be very beneficial. > > Today I've finally got a chance to update my workstation to the > latest HEAD and try again in order to see if your last patch has > any effect for my issue. Alas, it doesn't, sorry. > > My environment: GNOME 2 out of the box, namely as installed from > the gnome2-lite port. That includes Firefox and Totem player. > > What I did: was switching between windows of different apps (Firefox, > Terminal) via Alt+Tab, or between virtual desktops with some windows > on them using mouse, while playing an mp3 tune in the Totem player. > > What I also noticed was that assigning an idle priority to the > player makes the sound falter as well. I.e., the sound is smooth > only when the player runs at normal priority and zero, or numerically > greater, niceness. > > Lastly, I think I've found a simpler test case. Attached is a > proglet that essentially simulates the load pattern by waking up > periodically and doing dummy things. In my case (1GHz CPU,) 4-6 > instances of it running in the background are enough to make the > issue manifest itself: When I assign an RT/idle priority or negative > niceness to the player process, it starts to stutter, but as soon > as I return the player process to normal priority & niceness, it > plays fluently again. > > I haven't found a suitable detector other than a media player yet. > However, in my case, madplay is as good as Totem in detecting the > presumable scheduling problem, from which I infer that any audio > player will do, including command-line ones. Sorry, I can't test > this against mplayer now as my ADSL line is temporarily down and I > have to resort to dial-up, so downloading mplayer isn't an option > for me now. :-) > > -- > Yar > > #include > #include > #include > #include > #include > > const int n = 10 * 1024 * 1024; /* how many bytes of RAM to burn */ > const int v = 0; /* verbose flag */ > > int > main() > { > struct timespec ts0, ts; > char *p; > long dn, ds; > int i; > > for (;;) { > if (v) > clock_gettime(CLOCK_MONOTONIC, &ts0); > if ((p = malloc(n)) != NULL) { > for (i = 0; i < n; i++) > p[i] = (char)(i % 53); /* just a prime number */ > free(p); > } > if (v) { > clock_gettime(CLOCK_MONOTONIC, &ts); > ds = ts.tv_sec - ts0.tv_sec; > dn = ts.tv_nsec - ts0.tv_nsec; > if (dn < 0) { > ds--; > dn += 1000 * 1000 * 1000L; > } > if (dn < 0 || ds < 0) > abort(); > printf("last run took %ld.%09ld sec\n", ds, dn); > } > /* sleep 1-2 sec */ > usleep(1000 * 1000L + random() % (1000 * 1000L)); > > } > } > _______________________________________________ > 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" > Just to be sure I understand this correctly... the player stutters when you *decrease* its priority (Or increase its niceness) only? From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 16:52:18 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 20C0016A473; Mon, 21 Jan 2008 16:52:18 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.freebsd.org (Postfix) with ESMTP id D967413C447; Mon, 21 Jan 2008 16:52:16 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.6/8.13.6) with ESMTP id m0LGqFkq003969; Mon, 21 Jan 2008 11:52:15 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: David Schultz Date: Mon, 21 Jan 2008 11:52:00 -0500 User-Agent: KMail/1.6.2 References: <200801181217.52788.jkim@FreeBSD.org> <20080119121316.GA21917@VARK.MIT.EDU> In-Reply-To: <20080119121316.GA21917@VARK.MIT.EDU> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200801211152.07680.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.92/5507/Mon Jan 21 09:34:07 2008 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-current@FreeBSD.org, freebsd-arch@FreeBSD.org Subject: Re: [RFC] SysV SHM on 64-bit platforms X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 16:52:18 -0000 On Saturday 19 January 2008 07:13 am, David Schultz wrote: > On Fri, Jan 18, 2008, Jung-uk Kim wrote: > > Because fixing this PR breaks ABI, I had to make compat shims. > > But the question is which branch to break? Since we are very > > close to 7.0-RELEASE, the question became more complicated. A > > lot of people are asking me to fix this PR because it is much > > needed fix for large database installations, so I have to make a > > quick decision. :-( > > It's far too late to fix it for 7.0. RC1 is out, the packages have > already been built, and this could potentially break things. In > particular, you have no way of guaranteeing that an "old" shared > library that uses semctl(2) linked with a "new" binary will work > properly, or vise versa. I know the compat shim is not bullet-proof and I perfectly understand your concerns. That's why I had to give four options and three sets of patches. :-( > For 8-CURRENT, I'd say go ahead and fix it and add the syscall > compat goop. Then I guess backport it to 7-STABLE after a while if > nothing important breaks and nobody has any objections to that > plan. Well, since the policy is 'no seat belt for -CURRENT', I think that is aceptable, too. > It would also be cool if struct ipcperm got fixed at the same time > so we only have to do this once. I think that only entails adding > compat crud to semctl and maybe one or two other syscalls. Those > changes aren't urgent enough to make it worthwhile to backport to > 7.X IMO, though. So, you are in between option 1 and 4, i.e., bigger fix goes to HEAD and partial MFC to RELENG_7, right? > Two questions/comments about the patches: > - Why the #if !defined(__i386__)? There are better ways to test > whether you're compiling for a 32-bit architecture, if that's > what you meant. I reused oshmid_ds, which was only for __i386__ && (COMPAT_FREEBSD4 || COMPAT_43). Basically I didn't want to add struct oh_my_god_we_did_it_again_shmid_ds. ;-) Actually, the arch check is done like this: if (sizeof(size_t) != sizeof(int) && td->td_proc->p_osrel <= WHATEVER) I am hoping the compiler is smart enough to optimize away 'sizeof(size_t) != sizeof(int)'. > - The 8.X version needs to take the p_osrel for the equivalent > change in 7.X into account. I thought it did, didn't it? Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 17:31:13 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2535B16A468 for ; Mon, 21 Jan 2008 17:31:13 +0000 (UTC) (envelope-from wearabnet@yahoo.ca) Received: from web33710.mail.mud.yahoo.com (web33710.mail.mud.yahoo.com [68.142.201.207]) by mx1.freebsd.org (Postfix) with SMTP id C1CF013C4F3 for ; Mon, 21 Jan 2008 17:31:12 +0000 (UTC) (envelope-from wearabnet@yahoo.ca) Received: (qmail 96055 invoked by uid 60001); 21 Jan 2008 17:04:30 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.ca; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=OBlcTb0a1Vpb2eCiT4iR1P4zP53ZJjUCJwZvJFWJIKZVJ6sSZ0LZq42A9bqPQqGudd7PMtTKQntKPzNUmF6lIwLF2xnBYGugGBsz3RYXr40K7GP+gDGDcDMQf3Ax8lofv4Pld1rgvZmpq6RkB3t9Ql1raJqhJ67nruF0Hqb1aYM=; X-YMail-OSG: iVSuL9IVM1mjFihVVYz_wrUF6u2Stn1ItWWfOVvaR4LznvNvcP44lTm9kp2QfC.JeHu4GaoHIYt1XBtQdFpgJeLpjwPW84c37FPod8mKv1h3twhrpvs- Received: from [89.211.7.3] by web33710.mail.mud.yahoo.com via HTTP; Mon, 21 Jan 2008 09:04:29 PST X-Mailer: YahooMailRC/818.31 YahooMailWebService/0.7.160 Date: Mon, 21 Jan 2008 09:04:29 -0800 (PST) From: Abdullah Ibn Hamad Al-Marri To: FreeBSD CURRENT MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <933741.93778.qm@web33710.mail.mud.yahoo.com> Subject: LatencyTOP and FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 17:31:13 -0000 Heya, Is there any plan to use LatencyTOP with the FreeBSD for making our performance better? Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 17:41:08 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95BC616A418 for ; Mon, 21 Jan 2008 17:41:08 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from hs-out-2122.google.com (hs-out-0708.google.com [64.233.178.247]) by mx1.freebsd.org (Postfix) with ESMTP id 3E3F513C474 for ; Mon, 21 Jan 2008 17:41:08 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: by hs-out-2122.google.com with SMTP id h53so2096355hsh.11 for ; Mon, 21 Jan 2008 09:41:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type; bh=n1tt3VBWhwwFM9atk0pejFz1iQFU+GY/RSrI4mq073Q=; b=BqjZ89BI1BFQD3MxrETLmFoFVmgpD7Wg9V2WYKLqqsPUhWGxLnNh9fpDmyGRFZ9jnHUD1BGFyCrZiJSAQI86xidJa7gYtrQUmBy/v1xkUC7wC/SEqccpHtsN5VlRg+oAfZGasioMz2jjZOpl8u59HROWHR4nD3UEPiDWME5+pvM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type; b=XqaKNcSA90hVi1ldEENDjflFInVRKi8AbOeSWT1mpgW0rW9IsSGPYtyKEwM3Mppben7yQeSLkEPKh26a/16h0rUwT/2OcTwCR45kUq+AbkF4/J+Vvd78X6rza13CKgue7spJhMs9gtKUfajg05C3qmTEgLWPj//R5sFSLUrMtok= Received: by 10.100.255.10 with SMTP id c10mr15250727ani.54.1200937266990; Mon, 21 Jan 2008 09:41:06 -0800 (PST) Received: from kan.dnsalias.net ( [24.218.183.247]) by mx.google.com with ESMTPS id d36sm10787097and.37.2008.01.21.09.41.05 (version=SSLv3 cipher=OTHER); Mon, 21 Jan 2008 09:41:06 -0800 (PST) Date: Mon, 21 Jan 2008 12:40:59 -0500 From: Alexander Kabaev To: Abdullah Ibn Hamad Al-Marri Message-ID: <20080121124100.06f2ea93@kan.dnsalias.net> In-Reply-To: <933741.93778.qm@web33710.mail.mud.yahoo.com> References: <933741.93778.qm@web33710.mail.mud.yahoo.com> X-Mailer: Claws Mail 3.0.2 (GTK+ 2.12.5; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/65doaCvjEZdbPQRU+=DJsDD"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: FreeBSD CURRENT Subject: Re: LatencyTOP and FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 17:41:08 -0000 --Sig_/65doaCvjEZdbPQRU+=DJsDD Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 21 Jan 2008 09:04:29 -0800 (PST) Abdullah Ibn Hamad Al-Marri wrote: > Heya, >=20 >=20 >=20 > Is there any plan to use=20 > LatencyTOP with the FreeBSD for making our performance better? >=20 > =20 >=20 > Regards,=20 >=20 > -Abdullah Ibn Hamad Al-Marri >=20 > Arab Portal Hope not. This kind of statistics should easily be done with DTrace. --=20 Alexander Kabaev --Sig_/65doaCvjEZdbPQRU+=DJsDD Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iD8DBQFHlNksQ6z1jMm+XZYRAix0AJ4+GYNB/rg9aiyhPfUIqumFpnk1RACg18f4 L1q/CQvUSK1t/ghtvyjKMjY= =oX2X -----END PGP SIGNATURE----- --Sig_/65doaCvjEZdbPQRU+=DJsDD-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 18:22:19 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92C2016A41B; Mon, 21 Jan 2008 18:22:19 +0000 (UTC) (envelope-from peter.schuller@infidyne.com) Received: from smtp.infidyne.com (ds9.infidyne.com [88.80.6.206]) by mx1.freebsd.org (Postfix) with ESMTP id 1EFF113C468; Mon, 21 Jan 2008 18:22:19 +0000 (UTC) (envelope-from peter.schuller@infidyne.com) Received: from c-8216e555.03-51-73746f3.cust.bredbandsbolaget.se (c-8216e555.03-51-73746f3.cust.bredbandsbolaget.se [85.229.22.130]) by smtp.infidyne.com (Postfix) with ESMTP id DFA1F880E; Mon, 21 Jan 2008 19:22:14 +0100 (CET) From: Peter Schuller To: freebsd-current@freebsd.org Date: Mon, 21 Jan 2008 19:22:20 +0100 User-Agent: KMail/1.9.7 References: <200707282028.37102.peter.schuller@infidyne.com> <200707310126.06923.peter.schuller@infidyne.com> <200801011857.57757.peter.schuller@infidyne.com> In-Reply-To: <200801011857.57757.peter.schuller@infidyne.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart11573178.0QpTdHsbOW"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200801211922.29463.peter.schuller@infidyne.com> Cc: Pawel Jakub Dawidek , current@freebsd.org Subject: Re: (ZFS?): panic: lockmgr: locking against myself X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 18:22:19 -0000 --nextPart11573178.0QpTdHsbOW Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline > I *think* I just experienced the same problem on 7.0-BETA3, except the > kernel does not have WITNESS/INVARIANTS so I just get a hack instead of a > panic. I wanted to post with the information I have for completeness; I > realize what follows is a bunch of anecdotal mumbo-jumbo. So I can now confirm this problem on 7.0-RC1 on the machine where I origina= lly=20 saw this happen. If I could trigger this in a debuggable environment I would try to get some= =20 much more interesting information, but as this was during time-limited acce= ss=20 to the machine in a noisy colocation facility, with people waiting on the=20 machine to come back up, I was not in a position to do very much. Instead I= =20 will again, as an added data point, provide an approximate timeline below. = As=20 previously observed, it seems to be triggered by changes in the availabilit= y=20 of disks and/or zpool configuration, with cold reboots somehow mitigating t= he=20 problem. Note that the drives are likely to have been moved around a bit logically (= but=20 not physically), due to the level of indirection and drive number allocatio= n=20 resulting from the single-disk raid0 virtual hardware raid device. Timeline: * Machine running 7-CURRENT from the october/september era. * One disk in a three-way zfs mirror (tank, on which root fs is) gets kicke= d=20 out. * For probably unrelated reasons, the machine crashes with a kmem_alloc err= or=20 (this was the first time ever on this machine). Don't have details; this wa= s=20 observed by colocation personel. * Machine rebooted and panic:s as described in this thread. * I arrive on-site and reboot again just for kicks. Same problem. * I physically remove the broken disk and replace it with the new one, and = add=20 the virtual disk in the RAID controller bios (recap: this is a Dell 2950). * Now it boots again. * I zpool replace tank label/tank3 label/tank3r1 (after various=20 disklabel/glabel action). * make installkernell (7.0-RC1) * Reboot with resilvering/replacement still in progress. * Panic on boot. * Tried cold reboot (turn off,turn on) -> it now boots again without a pani= c. * Make installworld. * At this point I no longer remember whether it booted again or whether I h= ad=20 to do another cold reboot. * Machine has not been rebooted again since resilvering completed. =2D-=20 / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org --nextPart11573178.0QpTdHsbOW Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHlOLlDNor2+l1i30RAsFRAKCgj/XuvtqTc+WXzjOtWy/cxgkncACff+vg 3H9oCfMme4pUkUyIhkT9aXI= =/YjJ -----END PGP SIGNATURE----- --nextPart11573178.0QpTdHsbOW-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 18:22:19 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92C2016A41B; Mon, 21 Jan 2008 18:22:19 +0000 (UTC) (envelope-from peter.schuller@infidyne.com) Received: from smtp.infidyne.com (ds9.infidyne.com [88.80.6.206]) by mx1.freebsd.org (Postfix) with ESMTP id 1EFF113C468; Mon, 21 Jan 2008 18:22:19 +0000 (UTC) (envelope-from peter.schuller@infidyne.com) Received: from c-8216e555.03-51-73746f3.cust.bredbandsbolaget.se (c-8216e555.03-51-73746f3.cust.bredbandsbolaget.se [85.229.22.130]) by smtp.infidyne.com (Postfix) with ESMTP id DFA1F880E; Mon, 21 Jan 2008 19:22:14 +0100 (CET) From: Peter Schuller To: freebsd-current@freebsd.org Date: Mon, 21 Jan 2008 19:22:20 +0100 User-Agent: KMail/1.9.7 References: <200707282028.37102.peter.schuller@infidyne.com> <200707310126.06923.peter.schuller@infidyne.com> <200801011857.57757.peter.schuller@infidyne.com> In-Reply-To: <200801011857.57757.peter.schuller@infidyne.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart11573178.0QpTdHsbOW"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200801211922.29463.peter.schuller@infidyne.com> Cc: Pawel Jakub Dawidek , current@freebsd.org Subject: Re: (ZFS?): panic: lockmgr: locking against myself X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 18:22:19 -0000 --nextPart11573178.0QpTdHsbOW Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline > I *think* I just experienced the same problem on 7.0-BETA3, except the > kernel does not have WITNESS/INVARIANTS so I just get a hack instead of a > panic. I wanted to post with the information I have for completeness; I > realize what follows is a bunch of anecdotal mumbo-jumbo. So I can now confirm this problem on 7.0-RC1 on the machine where I origina= lly=20 saw this happen. If I could trigger this in a debuggable environment I would try to get some= =20 much more interesting information, but as this was during time-limited acce= ss=20 to the machine in a noisy colocation facility, with people waiting on the=20 machine to come back up, I was not in a position to do very much. Instead I= =20 will again, as an added data point, provide an approximate timeline below. = As=20 previously observed, it seems to be triggered by changes in the availabilit= y=20 of disks and/or zpool configuration, with cold reboots somehow mitigating t= he=20 problem. Note that the drives are likely to have been moved around a bit logically (= but=20 not physically), due to the level of indirection and drive number allocatio= n=20 resulting from the single-disk raid0 virtual hardware raid device. Timeline: * Machine running 7-CURRENT from the october/september era. * One disk in a three-way zfs mirror (tank, on which root fs is) gets kicke= d=20 out. * For probably unrelated reasons, the machine crashes with a kmem_alloc err= or=20 (this was the first time ever on this machine). Don't have details; this wa= s=20 observed by colocation personel. * Machine rebooted and panic:s as described in this thread. * I arrive on-site and reboot again just for kicks. Same problem. * I physically remove the broken disk and replace it with the new one, and = add=20 the virtual disk in the RAID controller bios (recap: this is a Dell 2950). * Now it boots again. * I zpool replace tank label/tank3 label/tank3r1 (after various=20 disklabel/glabel action). * make installkernell (7.0-RC1) * Reboot with resilvering/replacement still in progress. * Panic on boot. * Tried cold reboot (turn off,turn on) -> it now boots again without a pani= c. * Make installworld. * At this point I no longer remember whether it booted again or whether I h= ad=20 to do another cold reboot. * Machine has not been rebooted again since resilvering completed. =2D-=20 / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org --nextPart11573178.0QpTdHsbOW Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHlOLlDNor2+l1i30RAsFRAKCgj/XuvtqTc+WXzjOtWy/cxgkncACff+vg 3H9oCfMme4pUkUyIhkT9aXI= =/YjJ -----END PGP SIGNATURE----- --nextPart11573178.0QpTdHsbOW-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 19:44:43 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC49E16A421; Mon, 21 Jan 2008 19:44:43 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.bsdforen.de (bsdforen.de [212.204.60.79]) by mx1.freebsd.org (Postfix) with ESMTP id EE8A513C44B; Mon, 21 Jan 2008 19:44:42 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from homeKamikaze.norad (nat-wh-1.rz.uni-karlsruhe.de [129.13.72.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.bsdforen.de (Postfix) with ESMTP id 5B1D3405CA3; Mon, 21 Jan 2008 20:44:41 +0100 (CET) Message-ID: <4794F627.8070209@bsdforen.de> Date: Mon, 21 Jan 2008 20:44:39 +0100 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.9 (X11/20071203) MIME-Version: 1.0 To: Kris Kennaway References: <478556AD.6090400@bsdforen.de> <478560AE.2000102@FreeBSD.org> <47875131.4040802@FreeBSD.org> In-Reply-To: <47875131.4040802@FreeBSD.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD's problems as seen by the BSDForen.de community X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 19:44:43 -0000 Kris Kennaway wrote: > FYI this was not a dismissal, it was an invitation for you to follow up > with the specific problems your members have seen so we can try to > evaluate them. > > Kris We finally have some data. This is from end-2005 running 6.0-release. The output was generated, while the system was very unresponsive, the user has since stopped using FreeBSD and is thus not able to provide us with newer data: [stell @ nexxus:~]% vmstat -i interrupt total rate irq1: atkbd0 27306 1 irq6: fdc0 10 0 irq14: ata0 47 0 irq16: fwohci0+ 239567 11 irq17: skc0 486496 22 irq20: atapci1 549162 25 irq21: uhci0 uhci1+ 35743 1 irq22: pcm0 231032 10 lapic0: timer 42834660 1999 Total 44404023 2073 The following output was generated by a single user running a 7.0-prerelease. Running dd causes the system to be unresponsive even though the CPU load is not very high: top -S without load: last pid: 1072; load averages: 0.18, 0.21, 0.24 up 0+00:26:29 16:29:23 117 processes: 2 running, 97 sleeping, 18 waiting CPU states: 0.7% user, 0.0% nice, 0.7% system, 0.0% interrupt, 98.5% idle Mem: 206M Active, 175M Inact, 177M Wired, 26M Cache, 112M Buf, 1411M Free Swap: 4096M Total, 16K Used, 4096M Free PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 11 root 1 171 ki31 0K 8K RUN 21:32 92.58% idle: cpu0 917 tuck 2 -8 0 26944K 16932K piperd 0:03 0.78% gnome-termina 835 tuck 1 44 0 77760K 66200K select 1:39 0.00% Xorg 904 tuck 8 44 0 97660K 74248K ucond 0:37 0.00% firefox-bin 964 tuck 9 44 0 65412K 31244K pcmwr 0:14 0.00% vlc 3 root 1 -8 - 0K 8K - 0:08 0.00% g_up 30 root 1 -80 - 0K 8K WAIT 0:08 0.00% irq18: nvidia 862 tuck 1 44 0 16204K 10056K select 0:05 0.00% metacity 877 tuck 3 44 19 11760K 7440K ucond 0:05 0.00% trackerd 4 root 1 -8 - 0K 8K - 0:03 0.00% g_down 883 tuck 1 44 0 29064K 13168K select 0:03 0.00% wnck-applet 13 root 1 -32 - 0K 8K WAIT 0:03 0.00% swi4: clock s 28 root 1 -64 - 0K 8K WAIT 0:02 0.00% irq14: ata0 870 tuck 1 44 0 38804K 17432K select 0:02 0.00% nautilus 853 tuck 1 44 0 6008K 2892K select 0:02 0.00% gam_server 496 root 1 44 0 3240K 836K select 0:02 0.00% moused 46 root 1 -16 - 0K 8K sdflus 0:02 0.00% softdepflush 865 tuck 1 44 0 30836K 15008K select 0:01 0.00% gnome-panel 40 root 1 -16 - 0K 8K psleep 0:01 0.00% pagedaemon 893 tuck 1 44 0 29940K 13544K select 0:01 0.00% mixer_applet2 958 tuck 1 44 0 31636K 16032K select 0:01 0.00% gedit 15 root 1 -16 - 0K 8K - 0:01 0.00% yarrow 849 tuck 2 -8 0 22312K 12156K piperd 0:00 0.00% gnome-setting 31 root 1 -80 - 0K 8K WAIT 0:00 0.00% irq19: pcm0 840 tuck 2 -8 0 29516K 13080K piperd 0:00 0.00% gnome-session 44 root 1 20 - 0K 8K syncer 0:00 0.00% syncer 22 root 1 -64 - 0K 8K WAIT 0:00 0.00% irq21: ohci0+ 842 tuck 1 44 0 6888K 3756K select 0:00 0.00% gconfd-2 920 tuck 1 5 0 4244K 2836K ttyin 0:00 0.00% zsh 32 root 1 -68 - 0K 8K - 0:00 0.00% nfe0 taskq 892 tuck 1 44 0 19588K 10436K select 0:00 0.00% drivemount_ap 891 tuck 1 44 0 21384K 11780K select 0:00 0.00% clock-applet 869 tuck 2 44 0 9308K 3852K select 0:00 0.00% bonobo-activa 928 tuck 1 20 0 4100K 2544K pause 0:00 0.00% zsh 887 tuck 1 44 0 19828K 10376K select 0:00 0.00% notification- 813 tuck 1 20 0 4100K 2460K pause 0:00 0.00% zsh 879 tuck 1 44 0 9792K 4380K select 0:00 0.00% gnome-vfs-dae 2 root 1 -8 - 0K 8K - 0:00 0.00% g_event 37 root 1 -60 - 0K 8K WAIT 0:00 0.00% irq1: atkbd0 750 root 1 44 0 5840K 2132K select 0:00 0.00% sendmail 20 root 1 -24 - 0K 8K WAIT 0:00 0.00% swi6: Giant t 847 tuck 1 44 0 3232K 1428K select 0:00 0.00% dbus-daemon 918 tuck 1 4 0 5072K 1344K sbwait 0:00 0.00% gnome-pty-hel 33 root 1 0 - 0K 8K tzpoll 0:00 0.00% acpi_thermal 885 tuck 1 44 0 4980K 1472K select 0:00 0.00% mapping-daemo 805 root 1 8 0 3596K 1244K wait 0:00 0.00% login 620 root 1 44 0 3156K 1016K select 0:00 0.00% syslogd 1072 tuck 1 44 0 3524K 1428K RUN 0:00 0.00% top 895 tuck 1 8 0 3456K 1124K wait 0:00 0.00% sh 35 root 1 -8 - 0K 8K - 0:00 0.00% fdc0 760 root 1 8 0 3184K 1008K nanslp 0:00 0.00% cron 1 root 1 8 0 1888K 296K wait 0:00 0.00% init 43 root 1 -16 - 0K 8K psleep 0:00 0.00% bufdaemon 45 root 1 -4 - 0K 8K vlruwt 0:00 0.00% vnlru 816 tuck 1 8 0 3456K 1120K wait 0:00 0.00% sh 900 tuck 1 8 0 3456K 1156K wait 0:00 0.00% sh 834 tuck 1 8 0 4116K 1308K wait 0:00 0.00% xinit 806 root 1 5 0 3156K 872K ttyin 0:00 0.00% getty 810 root 1 5 0 3156K 872K ttyin 0:00 0.00% getty 812 root 1 5 0 3156K 872K ttyin 0:00 0.00% getty 807 root 1 5 0 3156K 872K ttyin 0:00 0.00% getty under load for 30 seconds: last pid: 1076; load averages: 0.33, 0.24, 0.25 up 0+00:27:23 16:30:17 117 processes: 2 running, 97 sleeping, 18 waiting CPU states: 2.3% user, 0.0% nice, 18.8% system, 1.1% interrupt, 77.8% idle Mem: 209M Active, 1522M Inact, 181M Wired, 68M Cache, 112M Buf, 15M Free Swap: 4096M Total, 16K Used, 4096M Free PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 11 root 1 171 ki31 0K 8K RUN 22:17 79.59% idle: cpu0 1073 tuck 1 -16 0 5188K 1652K wdrain 0:05 12.16% dd 496 root 1 44 0 3240K 836K select 0:02 0.59% moused 3 root 1 -8 - 0K 8K - 0:09 0.20% g_up 835 tuck 1 44 0 79696K 66236K select 1:40 0.00% Xorg 904 tuck 7 44 0 97660K 74236K ucond 0:37 0.00% firefox-bin 964 tuck 9 -8 0 65412K 32252K pcmwr 0:14 0.00% vlc 30 root 1 -80 - 0K 8K WAIT 0:08 0.00% irq18: nvidia 862 tuck 1 44 0 16204K 10056K select 0:05 0.00% metacity 877 tuck 3 8 19 11760K 7440K nanslp 0:05 0.00% trackerd 4 root 1 -8 - 0K 8K - 0:04 0.00% g_down 917 tuck 2 -8 0 26944K 16996K piperd 0:04 0.00% gnome-termina 13 root 1 -32 - 0K 8K WAIT 0:03 0.00% swi4: clock s 883 tuck 1 44 0 29064K 13168K select 0:03 0.00% wnck-applet 28 root 1 -64 - 0K 8K WAIT 0:02 0.00% irq14: ata0 870 tuck 1 44 0 38804K 17432K select 0:02 0.00% nautilus 853 tuck 1 44 0 6008K 2892K select 0:02 0.00% gam_server 46 root 1 -16 - 0K 8K sdflus 0:02 0.00% softdepflush 40 root 1 -16 - 0K 8K psleep 0:01 0.00% pagedaemon 865 tuck 1 44 0 30836K 15008K select 0:01 0.00% gnome-panel 958 tuck 1 44 0 31636K 15988K select 0:01 0.00% gedit 893 tuck 1 44 0 29940K 13544K select 0:01 0.00% mixer_applet2 15 root 1 -16 - 0K 8K - 0:01 0.00% yarrow 31 root 1 -80 - 0K 8K WAIT 0:00 0.00% irq19: pcm0 849 tuck 2 -8 0 22312K 12156K piperd 0:00 0.00% gnome-setting 840 tuck 2 -8 0 29516K 13080K piperd 0:00 0.00% gnome-session 44 root 1 20 - 0K 8K syncer 0:00 0.00% syncer 22 root 1 -64 - 0K 8K WAIT 0:00 0.00% irq21: ohci0+ 842 tuck 1 44 0 6888K 3756K select 0:00 0.00% gconfd-2 920 tuck 1 20 0 4244K 2836K pause 0:00 0.00% zsh 32 root 1 -68 - 0K 8K - 0:00 0.00% nfe0 taskq 892 tuck 1 44 0 19588K 10436K select 0:00 0.00% drivemount_ap 891 tuck 1 44 0 21384K 11780K select 0:00 0.00% clock-applet 869 tuck 2 44 0 9308K 3852K select 0:00 0.00% bonobo-activa 928 tuck 1 20 0 4100K 2544K pause 0:00 0.00% zsh 887 tuck 1 44 0 19828K 10376K select 0:00 0.00% notification- 813 tuck 1 20 0 4100K 2460K pause 0:00 0.00% zsh 879 tuck 1 44 0 9792K 4380K select 0:00 0.00% gnome-vfs-dae 2 root 1 -8 - 0K 8K - 0:00 0.00% g_event 37 root 1 -60 - 0K 8K WAIT 0:00 0.00% irq1: atkbd0 1072 tuck 1 44 0 3524K 1428K RUN 0:00 0.00% top 750 root 1 44 0 5840K 2132K select 0:00 0.00% sendmail 20 root 1 -24 - 0K 8K WAIT 0:00 0.00% swi6: Giant t 847 tuck 1 44 0 3232K 1428K select 0:00 0.00% dbus-daemon 918 tuck 1 4 0 5072K 1344K sbwait 0:00 0.00% gnome-pty-hel 33 root 1 0 - 0K 8K tzpoll 0:00 0.00% acpi_thermal 885 tuck 1 44 0 4980K 1472K select 0:00 0.00% mapping-daemo 805 root 1 8 0 3596K 1244K wait 0:00 0.00% login 620 root 1 44 0 3156K 1016K select 0:00 0.00% syslogd 895 tuck 1 8 0 3456K 1124K wait 0:00 0.00% sh 35 root 1 -8 - 0K 8K - 0:00 0.00% fdc0 760 root 1 8 0 3184K 1008K nanslp 0:00 0.00% cron 43 root 1 -16 - 0K 8K psleep 0:00 0.00% bufdaemon 1 root 1 8 0 1888K 296K wait 0:00 0.00% init 45 root 1 -4 - 0K 8K vlruwt 0:00 0.00% vnlru 816 tuck 1 8 0 3456K 1120K wait 0:00 0.00% sh 900 tuck 1 8 0 3456K 1156K wait 0:00 0.00% sh 834 tuck 1 8 0 4116K 1308K wait 0:00 0.00% xinit 806 root 1 5 0 3156K 872K ttyin 0:00 0.00% getty 810 root 1 5 0 3156K 872K ttyin 0:00 0.00% getty 812 root 1 5 0 3156K 872K ttyin 0:00 0.00% getty #################### *** vmstat *** without load: knirsch% vmstat procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad0 ad14 in sy cs us sy id 4 4 0 399928 59896 942 3 1 0 3194 1943 0 0 430 5638 2397 9 7 84 knirsch% vmstat procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad0 ad14 in sy cs us sy id 2 4 0 396216 61908 941 3 1 0 3191 1941 0 0 430 5633 2395 9 7 84 under load: knirsch% vmstat procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad0 ad14 in sy cs us sy id 2 6 0 400844 1492488 932 3 1 0 3411 1917 0 0 430 5606 2393 9 7 84 knirsch% vmstat procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad0 ad14 in sy cs us sy id 4 4 0 400844 1271572 931 3 1 0 3403 1913 0 0 431 5600 2397 9 7 84 #################### *** vmstat -i *** without load: knirsch% vmstat -i interrupt total rate irq1: atkbd0 2875 1 irq6: fdc0 10 0 irq14: ata0 504046 300 irq18: nvidia0+ 102591 61 irq19: pcm0 52611 31 irq21: ohci0+ 50774 30 irq22: ehci0+ 1 0 irq23: nfe0 15532 9 cpu0: timer 3347777 1998 Total 4076217 2433 knirsch% vmstat -i interrupt total rate irq1: atkbd0 2885 1 irq6: fdc0 10 0 irq14: ata0 504099 300 irq18: nvidia0+ 102794 61 irq19: pcm0 52921 31 irq21: ohci0+ 50774 30 irq22: ehci0+ 1 0 irq23: nfe0 15532 9 cpu0: timer 3354434 1999 Total 4083450 2433 under load: knirsch% vmstat -i interrupt total rate irq1: atkbd0 2925 1 irq6: fdc0 10 0 irq14: ata0 512437 301 irq18: nvidia0+ 104169 61 irq19: pcm0 54977 32 irq21: ohci0+ 51364 30 irq22: ehci0+ 1 0 irq23: nfe0 15532 9 cpu0: timer 3398629 1999 Total 4140044 2435 knirsch% vmstat -i interrupt total rate irq1: atkbd0 2935 1 irq6: fdc0 10 0 irq14: ata0 515080 302 irq18: nvidia0+ 104368 61 irq19: pcm0 55282 32 irq21: ohci0+ 51364 30 irq22: ehci0+ 1 0 irq23: nfe0 15532 9 cpu0: timer 3405190 1999 Total 4149762 2436 #################### knirsch% uname -a FreeBSD knirsch.sandbox.net 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #1: Wed Jan 16 15:39:55 CET 2008 root@knirsch.sandbox.net:/usr/obj/usr/src/sys/KNIRSCH i386 knirsch% dmesg Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-PRERELEASE #1: Wed Jan 16 15:39:55 CET 2008 root@knirsch.sandbox.net:/usr/obj/usr/src/sys/KNIRSCH Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 4000+ (2412.38-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x20f71 Stepping = 1 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800 AMD Features2=0x1 real memory = 2147418112 (2047 MB) avail memory = 2087649280 (1990 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, 7fef0000 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 powernow0: on cpu0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: at device 0.0 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xfe02f000-0xfe02ffff irq 21 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] ohci0: [ITHREAD] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 10 ports with 10 removable, self powered ehci0: mem 0xfeb00000-0xfeb000ff irq 22 at device 2.1 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb1: EHCI version 1.0 usb1: companion controller, 4 ports each: usb0 usb1: on ehci0 usb1: USB revision 2.0 uhub1: on usb1 uhub1: 10 ports with 10 removable, self powered pci0: at device 4.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xe000-0xe00f at device 6.0 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xcc00-0xcc0f mem 0xfe02b000-0xfe02bfff irq 21 at device 7.0 on pci0 atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] atapci2: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xb800-0xb80f mem 0xfe02a000-0xfe02afff irq 22 at device 8.0 on pci0 atapci2: [ITHREAD] ata4: on atapci2 ata4: [ITHREAD] ata5: on atapci2 ata5: [ITHREAD] pcib1: at device 9.0 on pci0 pci1: on pcib1 atapci3: port 0xac00-0xac7f,0xa800-0xa8ff mem 0xfdeff000-0xfdefffff,0xfdec0000-0xfdedffff irq 18 at device 8.0 on pci1 atapci3: [ITHREAD] atapci3: [ITHREAD] ata6: on atapci3 ata6: [ITHREAD] ata7: on atapci3 ata7: [ITHREAD] ata8: on atapci3 ata8: [ITHREAD] ata9: on atapci3 ata9: [ITHREAD] pcm0: port 0xa400-0xa41f irq 19 at device 9.0 on pci1 pcm0: pcm0: [ITHREAD] nfe0: port 0xb400-0xb407 mem 0xfe029000-0xfe029fff irq 23 at device 10.0 on pci0 miibus0: on nfe0 e1000phy0: PHY 1 on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto nfe0: Ethernet address: 00:16:17:ba:9d:bd nfe0: [FILTER] pcib2: at device 11.0 on pci0 pci2: on pcib2 pcib3: at device 12.0 on pci0 pci3: on pcib3 pcib4: at device 13.0 on pci0 pci4: on pcib4 pcib5: at device 14.0 on pci0 pci5: on pcib5 nvidia0: mem 0xfa000000-0xfaffffff,0xd0000000-0xdfffffff,0xfb000000-0xfbffffff irq 18 at device 0.0 on pci5 nvidia0: [GIANT-LOCKED] nvidia0: [ITHREAD] acpi_tz0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FILTER] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio0: [FILTER] atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] pmtimer0 on isa0 orm0: at iomem 0xd0000-0xd3fff,0xd4000-0xd8fff pnpid ORM0000 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 ppbus0: [ITHREAD] plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ppc0: [GIANT-LOCKED] ppc0: [ITHREAD] sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled ums0: on uhub0 ums0: 5 buttons and Z dir. Timecounter "TSC" frequency 2412376512 Hz quality 800 Timecounters tick every 1.000 msec ad0: 286168MB at ata0-master UDMA100 acd0: DVDR at ata0-slave UDMA33 ad14: 239372MB at ata7-master SATA300 ad18: 239372MB at ata9-master SATA300 GEOM_LABEL: Label for provider ad14s1 is ext2fs/ext_1. GEOM_LABEL: Label for provider ad18s1 is ext2fs/ext_2. GEOM_LABEL: Label for provider ad0s5 is msdosfs/1_1. GEOM_LABEL: Label for provider ad0s6 is ext2fs/1_2. Trying to mount root from ufs:/dev/ad0s2a pid 856 (gnome-screensaver), uid 1001: exited on signal 6 (core dumped) GEOM_LABEL: Label ext2fs/1_2 removed. GEOM_LABEL: Label msdosfs/1_1 removed. GEOM_LABEL: Label ext2fs/ext_2 removed. GEOM_LABEL: Label ext2fs/ext_1 removed. From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 21:01:49 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32B2A16A419; Mon, 21 Jan 2008 21:01:49 +0000 (UTC) (envelope-from das@FreeBSD.ORG) Received: from VARK.MIT.EDU (VARK.MIT.EDU [18.95.3.179]) by mx1.freebsd.org (Postfix) with ESMTP id DF6F013C457; Mon, 21 Jan 2008 21:01:48 +0000 (UTC) (envelope-from das@FreeBSD.ORG) Received: from VARK.MIT.EDU (localhost [127.0.0.1]) by VARK.MIT.EDU (8.14.2/8.14.1) with ESMTP id m0LL1jQd009419; Mon, 21 Jan 2008 16:01:45 -0500 (EST) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by VARK.MIT.EDU (8.14.2/8.14.1/Submit) id m0LL1jBP009418; Mon, 21 Jan 2008 16:01:45 -0500 (EST) (envelope-from das@FreeBSD.ORG) Date: Mon, 21 Jan 2008 16:01:45 -0500 From: David Schultz To: Jung-uk Kim Message-ID: <20080121210145.GA9107@VARK.MIT.EDU> Mail-Followup-To: Jung-uk Kim , freebsd-current@FreeBSD.ORG, freebsd-arch@FreeBSD.ORG References: <200801181217.52788.jkim@FreeBSD.org> <20080119121316.GA21917@VARK.MIT.EDU> <200801211152.07680.jkim@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200801211152.07680.jkim@FreeBSD.org> Cc: freebsd-current@FreeBSD.ORG, freebsd-arch@FreeBSD.ORG Subject: Re: [RFC] SysV SHM on 64-bit platforms X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 21:01:49 -0000 On Mon, Jan 21, 2008, Jung-uk Kim wrote: > On Saturday 19 January 2008 07:13 am, David Schultz wrote: > > For 8-CURRENT, I'd say go ahead and fix it and add the syscall > > compat goop. Then I guess backport it to 7-STABLE after a while if > > nothing important breaks and nobody has any objections to that > > plan. > > Well, since the policy is 'no seat belt for -CURRENT', I think that is > aceptable, too. Right, but you need the compat shims to avoid breaking the ABI when 8.0 is released anyway. > > It would also be cool if struct ipcperm got fixed at the same time > > so we only have to do this once. I think that only entails adding > > compat crud to semctl and maybe one or two other syscalls. Those > > changes aren't urgent enough to make it worthwhile to backport to > > 7.X IMO, though. > > So, you are in between option 1 and 4, i.e., bigger fix goes to HEAD > and partial MFC to RELENG_7, right? I'd say try to fix everything once and for all in HEAD, including struct ipcperm, but only MFC the shmid_ds changes to minimize the chance that anything breaks between 7.X releases. Others may have different opinions... > Actually, the arch check is > done like this: > > if (sizeof(size_t) != sizeof(int) && td->td_proc->p_osrel <= WHATEVER) > > I am hoping the compiler is smart enough to optimize away > 'sizeof(size_t) != sizeof(int)'. Yes, gcc does basic dead code elimination like this at all optimization levels, including -O0. Of course the code within the if block still has to be syntactically valid on all architectures; if it isn't, then you need ifdefs. > > - The 8.X version needs to take the p_osrel for the equivalent > > change in 7.X into account. > > I thought it did, didn't it? Oops, maybe you did and I was looking at one of the other versions of the patch. From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 21:10:09 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4AE7016A469; Mon, 21 Jan 2008 21:10:09 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 122B413C468; Mon, 21 Jan 2008 21:10:08 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.2/8.14.2/NETPLEX) with ESMTP id m0LLA2Mm022834; Mon, 21 Jan 2008 16:10:02 -0500 (EST) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Mon, 21 Jan 2008 16:10:02 -0500 (EST) Date: Mon, 21 Jan 2008 16:10:02 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: David Schultz In-Reply-To: <20080121210145.GA9107@VARK.MIT.EDU> Message-ID: References: <200801181217.52788.jkim@FreeBSD.org> <20080119121316.GA21917@VARK.MIT.EDU> <200801211152.07680.jkim@FreeBSD.org> <20080121210145.GA9107@VARK.MIT.EDU> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org, Jung-uk Kim , freebsd-arch@freebsd.org Subject: Re: [RFC] SysV SHM on 64-bit platforms X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jan 2008 21:10:09 -0000 On Mon, 21 Jan 2008, David Schultz wrote: > On Mon, Jan 21, 2008, Jung-uk Kim wrote: >> On Saturday 19 January 2008 07:13 am, David Schultz wrote: >>> For 8-CURRENT, I'd say go ahead and fix it and add the syscall >>> compat goop. Then I guess backport it to 7-STABLE after a while if >>> nothing important breaks and nobody has any objections to that >>> plan. >> >> Well, since the policy is 'no seat belt for -CURRENT', I think that is >> aceptable, too. > > Right, but you need the compat shims to avoid breaking the ABI > when 8.0 is released anyway. The compat shims should be committed at the same time as the actual change so that applications built on [4-7].x will continue to work. -- DE From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 21:27:42 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A373C16A419 for ; Mon, 21 Jan 2008 21:27:42 +0000 (UTC) (envelope-from andrew-freebsd@areilly.bpc-users.org) Received: from omta03ps.mx.bigpond.com (omta03ps.mx.bigpond.com [144.140.82.155]) by mx1.freebsd.org (Postfix) with ESMTP id 2575613C458 for ; Mon, 21 Jan 2008 21:27:41 +0000 (UTC) (envelope-from andrew-freebsd@areilly.bpc-users.org) Received: from oaamta03ps.mx.bigpond.com ([124.188.162.219]) by omta03ps.mx.bigpond.com with ESMTP id <20080121212740.MRXD2997.omta03ps.mx.bigpond.com@oaamta03ps.mx.bigpond.com> for ; Mon, 21 Jan 2008 21:27:40 +0000 Received: from areilly.bpa.nu ([124.188.162.219]) by oaamta03ps.mx.bigpond.com with ESMTP id <20080121212739.TDNS20831.oaamta03ps.mx.bigpond.com@areilly.bpa.nu> for ; Mon, 21 Jan 2008 21:27:39 +0000 Received: (qmail 1860 invoked from network); 21 Jan 2008 21:27:14 -0000 Received: from localhost (HELO duncan.reilly.home) (127.0.0.1) by localhost with SMTP; 21 Jan 2008 21:27:14 -0000 Date: Tue, 22 Jan 2008 08:27:14 +1100 From: Andrew Reilly To: Yar Tikhiy Message-ID: <20080122082714.760f966c@duncan.reilly.home> In-Reply-To: <20080121122402.GA63088@comp.chem.msu.su> References: <20071120141403.GE81260@comp.chem.msu.su> <4743342A.10507@FreeBSD.org> <20080101185451.S957@desktop> <20080121122402.GA63088@comp.chem.msu.su> X-Mailer: Claws Mail 3.0.2 (GTK+ 2.12.5; amd64-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A090206.47950E4B.0019,ss=1,fgs=0 Cc: Jeff Roberson , Kris Kennaway , freebsd-current@FreeBSD.org Subject: Re: SCHED_ULE & niceness / rtprio X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 21:27:42 -0000 On Mon, 21 Jan 2008 15:24:02 +0300 Yar Tikhiy wrote: > What I did: was switching between windows of different apps (Firefox, > Terminal) via Alt+Tab, or between virtual desktops with some windows > on them using mouse, while playing an mp3 tune in the Totem player. Firefox isn't necessarily an adequate specification, if the problem involves paging at all: it's VM footprint can change dramatically depending on the page view history and how long it's been running. Cheers, -- Andrew From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 21:32:18 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FB3F16A420; Mon, 21 Jan 2008 21:32:18 +0000 (UTC) (envelope-from so14k@valentine.liquidneon.com) Received: from valentine.liquidneon.com (valentine.liquidneon.com [216.87.78.132]) by mx1.freebsd.org (Postfix) with ESMTP id 7B7E113C45B; Mon, 21 Jan 2008 21:32:18 +0000 (UTC) (envelope-from so14k@valentine.liquidneon.com) Received: by valentine.liquidneon.com (Postfix, from userid 1018) id A7B668FD71; Mon, 21 Jan 2008 14:00:10 -0700 (MST) Date: Mon, 21 Jan 2008 14:00:10 -0700 From: Brad Davis To: freebsd-hackers@FreeBSD.org Message-ID: <20080121210010.GC15409@valentine.liquidneon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@FreeBSD.org Subject: FreeBSD Status Reports due: January 28th, 2008 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 21:32:18 -0000 Hi Everyone, It is that time again. We would like to remind everybody who has exciting news to share to write a report about their project. This is a good way to improve exposure of your work, receive feedback and help. As we are closing in on 7.0 everybody is interested to know what's new - so please, do tell! Looking forward to your reports. As always you can either use the template or the CGI generator and mail the output to monthly@ by Monday January 28th, 2008. http://www.freebsd.org/news/status/ http://www.freebsd.org/cgi/monthly.cgi http://www.freebsd.org/news/status/report-sample.xml Regards, Brad Davis From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 22:00:35 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E63CC16A418 for ; Mon, 21 Jan 2008 22:00:35 +0000 (UTC) (envelope-from freebsdlists@bsdunix.ch) Received: from conversation.bsdunix.ch (ns1.bsdunix.ch [82.220.1.90]) by mx1.freebsd.org (Postfix) with ESMTP id AB27813C458 for ; Mon, 21 Jan 2008 22:00:34 +0000 (UTC) (envelope-from freebsdlists@bsdunix.ch) Received: from localhost (localhost.bsdunix.ch [127.0.0.1]) by conversation.bsdunix.ch (Postfix) with ESMTP id 2B9F05EC1 for ; Mon, 21 Jan 2008 23:00:33 +0100 (CET) X-Virus-Scanned: by amavisd-new at mail.bsdunix.ch Received: from conversation.bsdunix.ch ([127.0.0.1]) by localhost (conversation.bsdunix.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id IE+wLz2UWvMD for ; Mon, 21 Jan 2008 23:00:32 +0100 (CET) Received: from Tom.local (home.bsdunix.ch [82.220.17.23]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by conversation.bsdunix.ch (Postfix) with ESMTP id 521E15E51 for ; Mon, 21 Jan 2008 23:00:32 +0100 (CET) Message-ID: <479515FF.1010709@bsdunix.ch> Date: Mon, 21 Jan 2008 23:00:31 +0100 From: Thomas Vogt User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070807) 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: Can't delete any files on my filled up ZFS pool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 22:00:36 -0000 Hello I need help. My ZFS sytem is filled up. I can't delete any files. root@bert:/tank# rm input.wav rm: input.wav: No space left on device ZFS: root@bert:/tank# zfs list tank NAME USED AVAIL REFER MOUNTPOINT tank 109G 0 4.11G /tank mount: tank 4.1G 4.1G 0B 100% /tank FreeBSD 7.0-RC1 #11: Wed Jan 16 04:23:37 CET 2008 root@bert.mlan.solnet.ch:/usr/obj/usr/src/sys/BERT i386 Any idea? Best Regards, Thomas From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 22:22:51 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CFD5216A421 for ; Mon, 21 Jan 2008 22:22:51 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 59C8713C474 for ; Mon, 21 Jan 2008 22:22:50 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from js.berklix.net (p549A4A80.dip.t-dialin.net [84.154.74.128]) (authenticated bits=0) by tower.berklix.org (8.13.6/8.13.6) with ESMTP id m0LMMgBP054836; Mon, 21 Jan 2008 22:22:47 GMT (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by js.berklix.net (8.13.8/8.13.8) with ESMTP id m0LMP1H6060213; Mon, 21 Jan 2008 23:25:02 +0100 (CET) (envelope-from jhs@berklix.org) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.13.8/8.13.8) with ESMTP id m0LMOoP7072911; Mon, 21 Jan 2008 23:24:55 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <200801212224.m0LMOoP7072911@fire.js.berklix.net> To: Thomas Vogt In-reply-to: <479515FF.1010709@bsdunix.ch> References: <479515FF.1010709@bsdunix.ch> Comments: In-reply-to Thomas Vogt message dated "Mon, 21 Jan 2008 23:00:31 +0100." Date: Mon, 21 Jan 2008 23:24:50 +0100 From: "Julian H. Stacey" Cc: freebsd-current@freebsd.org Subject: Re: Can't delete any files on my filled up ZFS pool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 22:22:51 -0000 Thomas Vogt wrote: > Hello > > I need help. My ZFS sytem is filled up. I can't delete any files. > > root@bert:/tank# rm input.wav > rm: input.wav: No space left on device I know nothing about ZFS :-) (Well nearly, just reading the ZFS pain on @freebsd lists is enough to scare me off for now ;-) ) But if I was stuck on this, with no ZFS experts to quickly ask, I'd guess & try: It needs more space for another Inode, or extended directory entry, cos its maybe going to create another inode in a backup/ deleted entity first, so either: A) Maybe su ; rm input.wav # if the concept of extra space still exists # per "tunefs -m" for root as per UFS etc. Or B) Perhaps more likely: truncate existing inode to create some space before deleting it: cat /dev/null > input.wav ; rm input.wav Presumably if you filled it as root, B might still empty it. There will doubtless be better ZFS answers, but could be interesting to hear if either of above could work. -- Julian Stacey. Munich Computer Consultant, BSD Unix C Linux. http://berklix.com From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 22:43:41 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C88716A420 for ; Mon, 21 Jan 2008 22:43:41 +0000 (UTC) (envelope-from freebsdlists@bsdunix.ch) Received: from conversation.bsdunix.ch (ns1.bsdunix.ch [82.220.1.90]) by mx1.freebsd.org (Postfix) with ESMTP id 4B03A13C45A for ; Mon, 21 Jan 2008 22:43:41 +0000 (UTC) (envelope-from freebsdlists@bsdunix.ch) Received: from localhost (localhost.bsdunix.ch [127.0.0.1]) by conversation.bsdunix.ch (Postfix) with ESMTP id 96E3D5F5C; Mon, 21 Jan 2008 23:43:40 +0100 (CET) X-Virus-Scanned: by amavisd-new at mail.bsdunix.ch Received: from conversation.bsdunix.ch ([127.0.0.1]) by localhost (conversation.bsdunix.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id I0yPvTlDckjU; Mon, 21 Jan 2008 23:43:37 +0100 (CET) Received: from Tom.local (home.bsdunix.ch [82.220.17.23]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by conversation.bsdunix.ch (Postfix) with ESMTP id C71155F4F; Mon, 21 Jan 2008 23:43:37 +0100 (CET) Message-ID: <47952019.3010309@bsdunix.ch> Date: Mon, 21 Jan 2008 23:43:37 +0100 From: Thomas Vogt User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070807) MIME-Version: 1.0 To: "Julian H. Stacey" References: <479515FF.1010709@bsdunix.ch> <200801212224.m0LMOoP7072911@fire.js.berklix.net> In-Reply-To: <200801212224.m0LMOoP7072911@fire.js.berklix.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Can't delete any files on my filled up ZFS pool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 22:43:41 -0000 Hello Julian Julian H. Stacey wrote: > Thomas Vogt wrote: >> Hello >> >> I need help. My ZFS sytem is filled up. I can't delete any files. >> >> root@bert:/tank# rm input.wav >> rm: input.wav: No space left on device > > I know nothing about ZFS :-) (Well nearly, just reading the ZFS pain > on @freebsd lists is enough to scare me off for now ;-) ) But if I > was stuck on this, with no ZFS experts to quickly ask, I'd guess & try: > > It needs more space for another Inode, or extended directory > entry, cos its maybe going to create another inode in a > backup/ deleted entity first, so either: > > A) > Maybe su ; rm input.wav # if the concept of extra space still exists > # per "tunefs -m" for root as per UFS etc. I filled it as root. So it does not work > Or B) > Perhaps more likely: > truncate existing inode to create some space > before deleting it: > cat /dev/null > input.wav ; rm input.wav Nice. B) works fine. Thank you. > Presumably if you filled it as root, B might still empty it. > > There will doubtless be better ZFS answers, but could be interesting > to hear if either of above could work. I hope there will be a "ZFS" answer :) Regards, Thomas From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 23:20:40 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A272A16A419 for ; Mon, 21 Jan 2008 23:20:40 +0000 (UTC) (envelope-from lists+freebsd-current@xinu.tv) Received: from fugu.xinu.tv (fugu.slackasses.com [204.11.33.69]) by mx1.freebsd.org (Postfix) with ESMTP id 7BF8813C4D3 for ; Mon, 21 Jan 2008 23:20:40 +0000 (UTC) (envelope-from lists+freebsd-current@xinu.tv) Received: from [192.168.3.3] (c-68-40-200-8.hsd1.mi.comcast.net [68.40.200.8]) by fugu.xinu.tv (Postfix) with ESMTP id 288A04A42FF; Mon, 21 Jan 2008 17:57:57 -0500 (EST) Message-ID: <479523CF.7020804@xinu.tv> Date: Mon, 21 Jan 2008 17:59:27 -0500 From: Bill User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: Thomas Vogt References: <479515FF.1010709@bsdunix.ch> <200801212224.m0LMOoP7072911@fire.js.berklix.net> <47952019.3010309@bsdunix.ch> In-Reply-To: <47952019.3010309@bsdunix.ch> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Julian H. Stacey" , freebsd-current@freebsd.org Subject: Re: Can't delete any files on my filled up ZFS pool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 23:20:40 -0000 Do you have snapshots on the pool? What is the output from 'zfs list'? It's possible when you have a snapshot on tank that the delete causes a copy-on-write for the snapshot that then doesn't have enough space. Bill Thomas Vogt wrote: > Hello Julian > > Julian H. Stacey wrote: >> Thomas Vogt wrote: >>> Hello >>> >>> I need help. My ZFS sytem is filled up. I can't delete any files. >>> >>> root@bert:/tank# rm input.wav >>> rm: input.wav: No space left on device >> >> I know nothing about ZFS :-) (Well nearly, just reading the ZFS pain >> on @freebsd lists is enough to scare me off for now ;-) ) But if I >> was stuck on this, with no ZFS experts to quickly ask, I'd guess & try: >> >> It needs more space for another Inode, or extended directory >> entry, cos its maybe going to create another inode in a >> backup/ deleted entity first, so either: >> >> A) >> Maybe su ; rm input.wav # if the concept of extra space still >> exists >> # per "tunefs -m" for root as per UFS etc. > > I filled it as root. So it does not work > >> Or B) >> Perhaps more likely: >> truncate existing inode to create some space >> before deleting it: >> cat /dev/null > input.wav ; rm input.wav > > Nice. B) works fine. Thank you. > > >> Presumably if you filled it as root, B might still empty it. >> >> There will doubtless be better ZFS answers, but could be interesting >> to hear if either of above could work. > > I hope there will be a "ZFS" answer :) > > Regards, > Thomas > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 23:29:34 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E82D516A41B for ; Mon, 21 Jan 2008 23:29:34 +0000 (UTC) (envelope-from freebsdlists@bsdunix.ch) Received: from conversation.bsdunix.ch (ns1.bsdunix.ch [82.220.1.90]) by mx1.freebsd.org (Postfix) with ESMTP id A363513C459 for ; Mon, 21 Jan 2008 23:29:34 +0000 (UTC) (envelope-from freebsdlists@bsdunix.ch) Received: from localhost (localhost.bsdunix.ch [127.0.0.1]) by conversation.bsdunix.ch (Postfix) with ESMTP id CAD4E5E6B; Tue, 22 Jan 2008 00:29:33 +0100 (CET) X-Virus-Scanned: by amavisd-new at mail.bsdunix.ch Received: from conversation.bsdunix.ch ([127.0.0.1]) by localhost (conversation.bsdunix.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id uzpF0+g2B2jM; Tue, 22 Jan 2008 00:29:31 +0100 (CET) Received: from Tom.local (home.bsdunix.ch [82.220.17.23]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by conversation.bsdunix.ch (Postfix) with ESMTP id 8C3095E3C; Tue, 22 Jan 2008 00:29:31 +0100 (CET) Message-ID: <47952ADB.4060306@bsdunix.ch> Date: Tue, 22 Jan 2008 00:29:31 +0100 From: Thomas Vogt User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070807) MIME-Version: 1.0 To: Bill References: <479515FF.1010709@bsdunix.ch> <200801212224.m0LMOoP7072911@fire.js.berklix.net> <47952019.3010309@bsdunix.ch> <479523CF.7020804@xinu.tv> In-Reply-To: <479523CF.7020804@xinu.tv> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Julian H. Stacey" , freebsd-current@freebsd.org Subject: Re: Can't delete any files on my filled up ZFS pool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 23:29:35 -0000 Hello Bill wrote: > Do you have snapshots on the pool? What is the output from 'zfs list'? > It's possible when you have a snapshot on tank that the delete causes a > copy-on-write for the snapshot that then doesn't have enough space. I don't use snapshots. zfs list NAME USED AVAIL REFER MOUNTPOINT tank 104G 5.70G 4.11G /tank tank/wav 99.5G 5.70G 99.5G /wav Cheers, Thomas > Thomas Vogt wrote: >> Hello Julian >> >> Julian H. Stacey wrote: >>> Thomas Vogt wrote: >>>> Hello >>>> >>>> I need help. My ZFS sytem is filled up. I can't delete any files. >>>> >>>> root@bert:/tank# rm input.wav >>>> rm: input.wav: No space left on device >>> >>> I know nothing about ZFS :-) (Well nearly, just reading the ZFS pain >>> on @freebsd lists is enough to scare me off for now ;-) ) But if I >>> was stuck on this, with no ZFS experts to quickly ask, I'd guess & try: >>> >>> It needs more space for another Inode, or extended directory >>> entry, cos its maybe going to create another inode in a >>> backup/ deleted entity first, so either: >>> >>> A) >>> Maybe su ; rm input.wav # if the concept of extra space still >>> exists >>> # per "tunefs -m" for root as per UFS etc. >> >> I filled it as root. So it does not work >> >>> Or B) >>> Perhaps more likely: >>> truncate existing inode to create some space >>> before deleting it: >>> cat /dev/null > input.wav ; rm input.wav >> >> Nice. B) works fine. Thank you. >> >> >>> Presumably if you filled it as root, B might still empty it. >>> >>> There will doubtless be better ZFS answers, but could be interesting >>> to hear if either of above could work. >> >> I hope there will be a "ZFS" answer :) >> >> Regards, >> Thomas >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe@freebsd.org" >> > From owner-freebsd-current@FreeBSD.ORG Mon Jan 21 23:49:21 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B39816A418 for ; Mon, 21 Jan 2008 23:49:21 +0000 (UTC) (envelope-from lists+freebsd-current@xinu.tv) Received: from fugu.xinu.tv (fugu.slackasses.com [204.11.33.69]) by mx1.freebsd.org (Postfix) with ESMTP id 5B4FB13C455 for ; Mon, 21 Jan 2008 23:49:21 +0000 (UTC) (envelope-from lists+freebsd-current@xinu.tv) Received: from [192.168.3.3] (c-68-40-200-8.hsd1.mi.comcast.net [68.40.200.8]) by fugu.xinu.tv (Postfix) with ESMTP id 8577B4A42FF; Mon, 21 Jan 2008 18:49:15 -0500 (EST) Message-ID: <47952FD6.8030207@xinu.tv> Date: Mon, 21 Jan 2008 18:50:46 -0500 From: Bill User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: Thomas Vogt References: <479515FF.1010709@bsdunix.ch> <200801212224.m0LMOoP7072911@fire.js.berklix.net> <47952019.3010309@bsdunix.ch> <479523CF.7020804@xinu.tv> <47952ADB.4060306@bsdunix.ch> In-Reply-To: <47952ADB.4060306@bsdunix.ch> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Julian H. Stacey" , freebsd-current@freebsd.org Subject: Re: Can't delete any files on my filled up ZFS pool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 23:49:21 -0000 Does the delete work now? In your original post, tank was: NAME USED AVAIL REFER MOUNTPOINT tank 109G 0 4.11G /tank and now: NAME USED AVAIL REFER MOUNTPOINT tank 104G 5.70G 4.11G /tank Is it possible a process was writing to /wav, filled the disk, you tried your 'rm /tank/input.wav' and then the original process writing to /wav unlinked the file that didn't fit, thus freeing 5.7G? /tank and /wav share the available free space on tank. If that ends up being the problem, you can set the reservation option on tank to prevent it from happening again. If it's not that I'm not sure what it could be, I'm just trying to point out 'quirky' behavior from ZFS that's different from UFS and the like, do to its pooling nature. Bill Thomas Vogt wrote: > Hello > > Bill wrote: >> Do you have snapshots on the pool? What is the output from 'zfs list'? >> It's possible when you have a snapshot on tank that the delete causes >> a copy-on-write for the snapshot that then doesn't have enough space. > > I don't use snapshots. > > zfs list > NAME USED AVAIL REFER MOUNTPOINT > tank 104G 5.70G 4.11G /tank > tank/wav 99.5G 5.70G 99.5G /wav > > Cheers, > Thomas > > >> Thomas Vogt wrote: >>> Hello Julian >>> >>> Julian H. Stacey wrote: >>>> Thomas Vogt wrote: >>>>> Hello >>>>> >>>>> I need help. My ZFS sytem is filled up. I can't delete any files. >>>>> >>>>> root@bert:/tank# rm input.wav >>>>> rm: input.wav: No space left on device >>>> >>>> I know nothing about ZFS :-) (Well nearly, just reading the ZFS pain >>>> on @freebsd lists is enough to scare me off for now ;-) ) But if I >>>> was stuck on this, with no ZFS experts to quickly ask, I'd guess & >>>> try: >>>> >>>> It needs more space for another Inode, or extended directory >>>> entry, cos its maybe going to create another inode in a >>>> backup/ deleted entity first, so either: >>>> >>>> A) >>>> Maybe su ; rm input.wav # if the concept of extra space >>>> still exists >>>> # per "tunefs -m" for root as per UFS etc. >>> >>> I filled it as root. So it does not work >>> >>>> Or B) >>>> Perhaps more likely: >>>> truncate existing inode to create some space >>>> before deleting it: >>>> cat /dev/null > input.wav ; rm input.wav >>> >>> Nice. B) works fine. Thank you. >>> >>> >>>> Presumably if you filled it as root, B might still empty it. >>>> >>>> There will doubtless be better ZFS answers, but could be interesting >>>> to hear if either of above could work. >>> >>> I hope there will be a "ZFS" answer :) >>> >>> Regards, >>> Thomas >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to >>> "freebsd-current-unsubscribe@freebsd.org" >>> >> > From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 00:10:31 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34C5D16A46C for ; Tue, 22 Jan 2008 00:10:31 +0000 (UTC) (envelope-from freebsdlists@bsdunix.ch) Received: from conversation.bsdunix.ch (ns1.bsdunix.ch [82.220.1.90]) by mx1.freebsd.org (Postfix) with ESMTP id B0AB213C4E1 for ; Tue, 22 Jan 2008 00:10:30 +0000 (UTC) (envelope-from freebsdlists@bsdunix.ch) Received: from localhost (localhost.bsdunix.ch [127.0.0.1]) by conversation.bsdunix.ch (Postfix) with ESMTP id CF9145F89; Tue, 22 Jan 2008 01:10:29 +0100 (CET) X-Virus-Scanned: by amavisd-new at mail.bsdunix.ch Received: from conversation.bsdunix.ch ([127.0.0.1]) by localhost (conversation.bsdunix.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id fq40XHOOZYUK; Tue, 22 Jan 2008 01:10:28 +0100 (CET) Received: from Tom.local (home.bsdunix.ch [82.220.17.23]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by conversation.bsdunix.ch (Postfix) with ESMTP id 207815F85; Tue, 22 Jan 2008 01:10:28 +0100 (CET) Message-ID: <47953473.9030405@bsdunix.ch> Date: Tue, 22 Jan 2008 01:10:27 +0100 From: Thomas Vogt User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070807) MIME-Version: 1.0 To: Bill References: <479515FF.1010709@bsdunix.ch> <200801212224.m0LMOoP7072911@fire.js.berklix.net> <47952019.3010309@bsdunix.ch> <479523CF.7020804@xinu.tv> <47952ADB.4060306@bsdunix.ch> <47952FD6.8030207@xinu.tv> In-Reply-To: <47952FD6.8030207@xinu.tv> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Julian H. Stacey" , freebsd-current@freebsd.org Subject: Re: Can't delete any files on my filled up ZFS pool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 00:10:31 -0000 Hello Bill Bill wrote: > Does the delete work now? Sorry for not mentioning. Yes delete work with 'cat /dev/null > input.wav ; rm input.wav'. Simple use of rm didn't work > > In your original post, tank was: > > NAME USED AVAIL REFER MOUNTPOINT > tank 109G 0 4.11G /tank Before Julians hint with cat /dev/null > > and now: > > NAME USED AVAIL REFER MOUNTPOINT > tank 104G 5.70G 4.11G /tank After Julians hint. > Is it possible a process was writing to /wav, filled the disk, you tried > your 'rm /tank/input.wav' and then the original process writing to /wav > unlinked the file that didn't fit, thus freeing 5.7G? Unlikely. This pool is only used for storing data. No writing from any the system. > > /tank and /wav share the available free space on tank. If that ends up > being the problem, you can set the reservation option on tank to prevent > it from happening again. If it's not that I'm not sure what it could > be, I'm just trying to point out 'quirky' behavior from ZFS that's > different from UFS and the like, do to its pooling nature. You're right. Maybe it's better to set reservation for zfs too. Cheers, Thomas > Thomas Vogt wrote: >> Hello >> >> Bill wrote: >>> Do you have snapshots on the pool? What is the output from 'zfs list'? >>> It's possible when you have a snapshot on tank that the delete causes >>> a copy-on-write for the snapshot that then doesn't have enough space. >> >> I don't use snapshots. >> >> zfs list >> NAME USED AVAIL REFER MOUNTPOINT >> tank 104G 5.70G 4.11G /tank >> tank/wav 99.5G 5.70G 99.5G /wav >> >> Cheers, >> Thomas >> >> >>> Thomas Vogt wrote: >>>> Hello Julian >>>> >>>> Julian H. Stacey wrote: >>>>> Thomas Vogt wrote: >>>>>> Hello >>>>>> >>>>>> I need help. My ZFS sytem is filled up. I can't delete any files. >>>>>> >>>>>> root@bert:/tank# rm input.wav >>>>>> rm: input.wav: No space left on device >>>>> >>>>> I know nothing about ZFS :-) (Well nearly, just reading the ZFS pain >>>>> on @freebsd lists is enough to scare me off for now ;-) ) But if I >>>>> was stuck on this, with no ZFS experts to quickly ask, I'd guess & >>>>> try: >>>>> >>>>> It needs more space for another Inode, or extended directory >>>>> entry, cos its maybe going to create another inode in a >>>>> backup/ deleted entity first, so either: >>>>> >>>>> A) >>>>> Maybe su ; rm input.wav # if the concept of extra space >>>>> still exists >>>>> # per "tunefs -m" for root as per UFS etc. >>>> >>>> I filled it as root. So it does not work >>>> >>>>> Or B) >>>>> Perhaps more likely: >>>>> truncate existing inode to create some space >>>>> before deleting it: >>>>> cat /dev/null > input.wav ; rm input.wav >>>> >>>> Nice. B) works fine. Thank you. >>>> >>>> >>>>> Presumably if you filled it as root, B might still empty it. >>>>> >>>>> There will doubtless be better ZFS answers, but could be interesting >>>>> to hear if either of above could work. >>>> >>>> I hope there will be a "ZFS" answer :) >>>> >>>> Regards, >>>> Thomas >>>> _______________________________________________ >>>> freebsd-current@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>>> To unsubscribe, send any mail to >>>> "freebsd-current-unsubscribe@freebsd.org" >>>> >>> >> > From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 04:50:01 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CF60116A417 for ; Tue, 22 Jan 2008 04:50:01 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.freebsd.org (Postfix) with ESMTP id 8EC1813C455 for ; Tue, 22 Jan 2008 04:50:01 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 36DC18CDE0; Mon, 21 Jan 2008 23:50:01 -0500 (EST) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 21 Jan 2008 23:50:01 -0500 X-Sasl-enc: fvaAqb7siYzK6edq9aLOlglrUiUc/qhHBAnmBgDPfqeb 1200977400 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id C47F5209D7; Mon, 21 Jan 2008 23:50:00 -0500 (EST) Message-ID: <479575F7.80605@incunabulum.net> Date: Tue, 22 Jan 2008 04:49:59 +0000 From: Bruce M Simpson User-Agent: Thunderbird 2.0.0.6 (X11/20070928) MIME-Version: 1.0 To: pluknet References: <478B89F6.1010703@incunabulum.net> <479012F5.9050408@incunabulum.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: exmap port - shared memory profiler X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 04:50:01 -0000 pluknet wrote: > I've slightly cleared exmap port to more working state. Now it > compiles (with also patched sysutils/pmap) and all binaries from this > port works (including gtk tool) on 7.0 (still not tested on 6.x and > HEAD). > Thanks for the help! I almost have it running on 6.3-RELEASE with these changes. I haven't tested with -CURRENT. Now it crashes due to finding some kind of inconsistency in the page map it has learned. Compiling with -O0 and then examining the core file suggests it's creating the FbsdSysInfo instance again. Exmap is still tied to being able to reach into Linux and grab physical page maps. I think the best way forward may be to adapt the pmap_helper.ko module and extend it to return the result of its call to pmap_extract(), rather than faking 'page cookies' as I have currently patched Exmap to do. There's no way for it to learn precisely which pages are mapped and resident for the same reason, and it really should. I have to crack on with other work, I may get around to this later on. thanks again BMS From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 05:16:12 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CFE516A419 for ; Tue, 22 Jan 2008 05:16:12 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by mx1.freebsd.org (Postfix) with ESMTP id CB97613C447 for ; Tue, 22 Jan 2008 05:16:11 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so4176870waf.3 for ; Mon, 21 Jan 2008 21:16:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:subject:message-id:reply-to:mime-version:content-type:content-disposition:user-agent; bh=Irla5+PBglLS8PrysAlM7JVLL3Rv3s4Z1LaZ/w3SlCU=; b=jmyaKW2csbKBIUvAvSSrVEdWdOoX6zpbV3LX3b76l7LpTpVQCqkBByXO/t7On6uvqM5HFHkMkV+6DtalOOf67hKFGysamadcRrNSEWVdlSyEPnGAGu5mtuSyvXUlb+7yuU1DcGrQ5xr30Fetko/fhjkqqilKpzC75VXWnRM1u3U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:reply-to:mime-version:content-type:content-disposition:user-agent; b=qVnD4FlMpddMAtkq05m8gWYtGALVw6WrwPuQlEDqvyFMUZmN1PtgWCHj92RVrvx4aCGiSmB43WYcB7K9cl03AHIPi9GC8IiwM7cRi/3SehB+delY1iUyzhuHNZgbsXkUPRdudBCCalKn5X4PTs8XXVTnr+lOn+HS9r9i7NEokd4= Received: by 10.114.75.1 with SMTP id x1mr6493549waa.137.1200978971573; Mon, 21 Jan 2008 21:16:11 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id j29sm16983435waf.18.2008.01.21.21.16.08 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Jan 2008 21:16:10 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m0M5G5QP010903 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 22 Jan 2008 14:16:05 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m0M5G4TC010902 for freebsd-current@FreeBSD.org; Tue, 22 Jan 2008 14:16:04 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 22 Jan 2008 14:16:04 +0900 From: Pyun YongHyeon To: freebsd-current@FreeBSD.org Message-ID: <20080122051604.GC10560@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="cmJC7u66zC7hs+87" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: CFT: re(4) WOL support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2008 05:16:12 -0000 --cmJC7u66zC7hs+87 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Dear all, Attached patch enables WOL capability on re(4). Since there are too many variants of hardwares that uses re(4), I'd like to hear success/failure report of the patch prior to commit. You can wake the system in suspend state as well as power down state. Because suspend/resume does not work on my box I don't know whether waking up from suspend work. WOL packets can be greated with tools like ports/net/wol. Patch was generated against HEAD and you should have latest CURRENT to get WOL infrasture before running the patch. -- Regards, Pyun YongHyeon --cmJC7u66zC7hs+87 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="re.WOL.diff" --- sys/dev/re/if_re.c.orig 2008-01-18 10:50:49.000000000 +0900 +++ sys/dev/re/if_re.c 2008-01-22 13:49:26.000000000 +0900 @@ -280,6 +280,8 @@ static void re_setmulti (struct rl_softc *); static void re_reset (struct rl_softc *); +static void re_setwol (struct rl_softc *); +static void re_clrwol (struct rl_softc *); #ifdef RE_DIAG static int re_diag (struct rl_softc *); @@ -1334,6 +1336,9 @@ ifp->if_capabilities |= IFCAP_VLAN_MTU | IFCAP_VLAN_HWTAGGING; if (ifp->if_capabilities & IFCAP_HWCSUM) ifp->if_capabilities |= IFCAP_VLAN_HWCSUM; + /* Enable WOL if PM is supported. */ + if (pci_find_extcap(sc->rl_dev, PCIY_PMG, ®) == 0) + ifp->if_capabilities |= IFCAP_WOL; ifp->if_capenable = ifp->if_capabilities; #ifdef DEVICE_POLLING ifp->if_capabilities |= IFCAP_POLLING; @@ -2715,6 +2720,15 @@ else ifp->if_hwassist &= ~CSUM_TSO; } + if ((mask & IFCAP_WOL) != 0 && + (ifp->if_capabilities & IFCAP_WOL) != 0) { + if ((mask & IFCAP_WOL_UCAST) != 0) + ifp->if_capenable ^= IFCAP_WOL_UCAST; + if ((mask & IFCAP_WOL_MCAST) != 0) + ifp->if_capenable ^= IFCAP_WOL_MCAST; + if ((mask & IFCAP_WOL_MAGIC) != 0) + ifp->if_capenable ^= IFCAP_WOL_MAGIC; + } if (reinit && ifp->if_drv_flags & IFF_DRV_RUNNING) re_init(sc); VLAN_CAPABILITIES(ifp); @@ -2820,6 +2834,7 @@ RL_LOCK(sc); re_stop(sc); + re_setwol(sc); sc->suspended = 1; RL_UNLOCK(sc); @@ -2848,6 +2863,11 @@ if (ifp->if_flags & IFF_UP) re_init_locked(sc); + /* + * Clear WOL matching such that normal Rx filtering + * wouldn't interfere with WOL patterns. + */ + re_clrwol(sc); sc->suspended = 0; RL_UNLOCK(sc); @@ -2874,7 +2894,95 @@ * cases. */ sc->rl_ifp->if_flags &= ~IFF_UP; + re_setwol(sc); RL_UNLOCK(sc); return (0); } + +static void +re_setwol(sc) + struct rl_softc *sc; +{ + struct ifnet *ifp; + int pmc; + uint16_t pmstat; + uint8_t v; + + RL_LOCK_ASSERT(sc); + + if (pci_find_extcap(sc->rl_dev, PCIY_PMG, &pmc) != 0) + return; + + ifp = sc->rl_ifp; + /* Enable config register write. */ + CSR_WRITE_1(sc, RL_EECMD, RL_EE_MODE); + + /* Enable PME. */ + v = CSR_READ_1(sc, RL_CFG1); + v &= ~RL_CFG1_PME; + if ((ifp->if_capenable & IFCAP_WOL) != 0) + v |= RL_CFG1_PME; + CSR_WRITE_1(sc, RL_CFG1, v); + + v = CSR_READ_1(sc, RL_CFG3); + v &= ~(RL_CFG3_WOL_LINK | RL_CFG3_WOL_MAGIC); + if ((ifp->if_capenable & IFCAP_WOL_MAGIC) != 0) + v |= RL_CFG3_WOL_MAGIC; + CSR_WRITE_1(sc, RL_CFG3, v); + + /* Config register write done. */ + CSR_WRITE_1(sc, RL_EECMD, 0); + + v = CSR_READ_1(sc, RL_CFG5); + v &= ~(RL_CFG5_WOL_BCAST | RL_CFG5_WOL_MCAST | RL_CFG5_WOL_UCAST); + v &= ~RL_CFG5_WOL_LANWAKE; + if ((ifp->if_capenable & IFCAP_WOL_UCAST) != 0) + v |= RL_CFG5_WOL_UCAST; + if ((ifp->if_capenable & IFCAP_WOL_MCAST) != 0) + v |= RL_CFG5_WOL_MCAST | RL_CFG5_WOL_BCAST; + if ((ifp->if_capenable & IFCAP_WOL) != 0) + v |= RL_CFG5_WOL_LANWAKE; + CSR_WRITE_1(sc, RL_CFG5, v); + + /* + * It seems that hardware resets its link speed to 100Mbps in + * power down mode so switching to 100Mbps in driver is not + * needed. + */ + + /* Request PME if WOL is requested. */ + pmstat = pci_read_config(sc->rl_dev, pmc + PCIR_POWER_STATUS, 2); + pmstat &= ~(PCIM_PSTAT_PME | PCIM_PSTAT_PMEENABLE); + if ((ifp->if_capenable & IFCAP_WOL) != 0) + pmstat |= PCIM_PSTAT_PME | PCIM_PSTAT_PMEENABLE; + pci_write_config(sc->rl_dev, pmc + PCIR_POWER_STATUS, pmstat, 2); +} + +static void +re_clrwol(sc) + struct rl_softc *sc; +{ + int pmc; + uint8_t v; + + RL_LOCK_ASSERT(sc); + + if (pci_find_extcap(sc->rl_dev, PCIY_PMG, &pmc) != 0) + return; + + /* Enable config register write. */ + CSR_WRITE_1(sc, RL_EECMD, RL_EE_MODE); + + v = CSR_READ_1(sc, RL_CFG3); + v &= ~(RL_CFG3_WOL_LINK | RL_CFG3_WOL_MAGIC); + CSR_WRITE_1(sc, RL_CFG3, v); + + /* Config register write done. */ + CSR_WRITE_1(sc, RL_EECMD, 0); + + v = CSR_READ_1(sc, RL_CFG5); + v &= ~(RL_CFG5_WOL_BCAST | RL_CFG5_WOL_MCAST | RL_CFG5_WOL_UCAST); + v &= ~RL_CFG5_WOL_LANWAKE; + CSR_WRITE_1(sc, RL_CFG5, v); +} --- sys/pci/if_rlreg.h.orig 2008-01-15 10:10:31.000000000 +0900 +++ sys/pci/if_rlreg.h 2008-01-22 13:42:39.000000000 +0900 @@ -76,7 +76,11 @@ #define RL_EECMD 0x0050 /* EEPROM command register */ #define RL_CFG0 0x0051 /* config register #0 */ #define RL_CFG1 0x0052 /* config register #1 */ - /* 0053-0057 reserved */ +#define RL_CFG2 0x0053 /* config register #2 */ +#define RL_CFG3 0x0054 /* config register #3 */ +#define RL_CFG4 0x0055 /* config register #4 */ +#define RL_CFG5 0x0056 /* config register #5 */ + /* 0057 reserved */ #define RL_MEDIASTAT 0x0058 /* media status register (8139) */ /* 0059-005A reserved */ #define RL_MII 0x005A /* 8129 chip only */ @@ -359,16 +363,50 @@ * Config 1 register */ #define RL_CFG1_PWRDWN 0x01 +#define RL_CFG1_PME 0x01 #define RL_CFG1_SLEEP 0x02 +#define RL_CFG1_VPDEN 0x02 #define RL_CFG1_IOMAP 0x04 #define RL_CFG1_MEMMAP 0x08 #define RL_CFG1_RSVD 0x10 +#define RL_CFG1_LWACT 0x10 #define RL_CFG1_DRVLOAD 0x20 #define RL_CFG1_LED0 0x40 #define RL_CFG1_FULLDUPLEX 0x40 /* 8129 only */ #define RL_CFG1_LED1 0x80 /* + * Config 2 register + */ +#define RL_CFG2_PCI33MHZ 0x00 +#define RL_CFG2_PCI66MHZ 0x01 +#define RL_CFG2_PCI64BIT 0x08 +#define RL_CFG2_AUXPWR 0x10 + +/* + * Config 3 register + */ +#define RL_CFG3_GRANTSEL 0x80 +#define RL_CFG3_WOL_MAGIC 0x20 +#define RL_CFG3_WOL_LINK 0x10 +#define RL_CFG3_FAST_B2B 0x01 + +/* + * Config 4 register + */ +#define RL_CFG4_LWPTN 0x04 +#define RL_CFG4_LWPME 0x10 + +/* + * Config 5 register + */ +#define RL_CFG5_WOL_BCAST 0x40 +#define RL_CFG5_WOL_MCAST 0x20 +#define RL_CFG5_WOL_UCAST 0x10 +#define RL_CFG5_WOL_LANWAKE 0x02 +#define RL_CFG5_PME_STS 0x01 + +/* * 8139C+ register definitions */ --cmJC7u66zC7hs+87-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 05:38:11 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 923D116A41A for ; Tue, 22 Jan 2008 05:38:11 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by mx1.freebsd.org (Postfix) with ESMTP id 408DC13C45A for ; Tue, 22 Jan 2008 05:38:11 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so4186609waf.3 for ; Mon, 21 Jan 2008 21:38:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:subject:message-id:reply-to:mime-version:content-type:content-disposition:user-agent; bh=mEgPUl8UFDKC3yrnW4Hv6oS1CrBG/jr0b1UxjQaquas=; b=IRdxzGxOXmhfmWCzkhV9I7ksv6BpkfnLyxLiz74FodLDQgxKBFY8ZbWbKDIhqCgAR5XiRzQPSsc2LUcy1DiynX4piBWvceWVHrLuO768HgpAobITZQCrq4q8SDKX77sjwyWw1Z7euxG/dJaWRDumOjkaTj6QC0I9um0ewRGl5SU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:reply-to:mime-version:content-type:content-disposition:user-agent; b=J+/2tet8nBPqKlEQSZO0haz3y60rvw5IgZ3oyc0BTviXWOvNCG6g2f/pEvwjPPwAH07McPvPqFBfalGvj1MXDcJ72yXGp0YXvoesu+A1bbPz9RXWms7+ZzauWvi1aVN9hrgv8ZpkFbewLIHucQrCHPeSgFzfsP4H7Pp5TWmRh6c= Received: by 10.114.169.2 with SMTP id r2mr1661339wae.76.1200980290870; Mon, 21 Jan 2008 21:38:10 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id k26sm17021333waf.58.2008.01.21.21.38.08 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 21 Jan 2008 21:38:09 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m0M5c49R010983 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 22 Jan 2008 14:38:04 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m0M5c4av010982 for freebsd-current@FreeBSD.org; Tue, 22 Jan 2008 14:38:04 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 22 Jan 2008 14:38:04 +0900 From: Pyun YongHyeon To: freebsd-current@FreeBSD.org Message-ID: <20080122053804.GA10963@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: cvs in CURRENT broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2008 05:38:11 -0000 When I try to update sources with cvs on latest CURRENT, I always get the following. 504 [monster: ~/NetBSD]export CVSROOT=:pserver:anoncvs@anoncvs.NetBSD.org:/cvsroot 505 [monster: ~/NetBSD]cvs login Logging in to :pserver:anoncvs@anoncvs.netbsd.org:2401/cvsroot CVS password: Assertion failed: ((run->regs_mask[elm] & (1U << bit)) == 0), function arena_run_reg_dalloc, file /usr/src/lib/libc/stdlib/malloc.c, line 2197. cvs [login aborted]: received abort signal Is it known issue of cvs-1.11.22? -- Regards, Pyun YongHyeon From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 06:37:00 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A6F0416A41A for ; Tue, 22 Jan 2008 06:37:00 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from mp2.macomnet.net (mp2.macomnet.net [195.128.64.6]) by mx1.freebsd.org (Postfix) with ESMTP id E578813C442 for ; Tue, 22 Jan 2008 06:36:59 +0000 (UTC) (envelope-from maxim@macomnet.ru) Received: from localhost (localhost.int.ru [127.0.0.1] (may be forged)) by mp2.macomnet.net (8.13.7/8.13.8) with ESMTP id m0M6DheZ054072; Tue, 22 Jan 2008 09:13:43 +0300 (MSK) (envelope-from maxim@macomnet.ru) Date: Tue, 22 Jan 2008 09:13:42 +0300 (MSK) From: Maxim Konovalov To: Pyun YongHyeon In-Reply-To: <20080122053804.GA10963@cdnetworks.co.kr> Message-ID: <20080122091333.K9942@mp2.macomnet.net> References: <20080122053804.GA10963@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-current@freebsd.org Subject: Re: cvs in CURRENT broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 06:37:00 -0000 On Tue, 22 Jan 2008, 14:38+0900, Pyun YongHyeon wrote: > When I try to update sources with cvs on latest CURRENT, I always get the > following. > > 504 [monster: ~/NetBSD]export CVSROOT=:pserver:anoncvs@anoncvs.NetBSD.org:/cvsroot > 505 [monster: ~/NetBSD]cvs login > Logging in to :pserver:anoncvs@anoncvs.netbsd.org:2401/cvsroot > CVS password: > Assertion failed: ((run->regs_mask[elm] & (1U << bit)) == 0), function arena_run_reg_dalloc, file /usr/src/lib/libc/stdlib/malloc.c, line 2197. > cvs [login aborted]: received abort signal > > Is it known issue of cvs-1.11.22? > Sort of. http://lists.freebsd.org/pipermail/freebsd-current/2008-January/082546.html -- Maxim Konovalov From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 06:44:30 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5918F16A41A for ; Tue, 22 Jan 2008 06:44:30 +0000 (UTC) (envelope-from AFriedman@drsns.com) Received: from bigmama.drsns.com (rrcs-71-41-74-142.se.biz.rr.com [71.41.74.142]) by mx1.freebsd.org (Postfix) with ESMTP id D5CE513C4DB for ; Tue, 22 Jan 2008 06:44:29 +0000 (UTC) (envelope-from AFriedman@drsns.com) Received: from aharonlap (rrcs-71-41-74-141.se.biz.rr.com [71.41.74.141]) by bigmama.drsns.com (8.14.2/8.13.8) with ESMTP id m0M6GJhc008304 for ; Tue, 22 Jan 2008 01:16:19 -0500 (EST) (envelope-from AFriedman@drsns.com) From: "Dr. Aharon Friedman" To: Date: Tue, 22 Jan 2008 01:15:52 -0500 Message-ID: <012101c85cbe$3d93fef0$292d280a@friedman.net> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Thread-Index: Achcvj0TyiPoMfk2RnivEDO9TNsNPQ== X-Mailman-Approved-At: Tue, 22 Jan 2008 06:57:23 +0000 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: IPSEC on 7.0-PRERELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 06:44:30 -0000 I am trying to compile a 7.0 kernel with IPSEC and I keep getting a compilation error. Did the IPSEC options change? Aharon Friedman No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.19.8/1235 - Release Date: 1/21/2008 9:39 AM From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 07:05:05 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E7E716A419 for ; Tue, 22 Jan 2008 07:05:05 +0000 (UTC) (envelope-from astrodog@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.186]) by mx1.freebsd.org (Postfix) with ESMTP id 1C6AE13C461 for ; Tue, 22 Jan 2008 07:05:04 +0000 (UTC) (envelope-from astrodog@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so2253813rvb.43 for ; Mon, 21 Jan 2008 23:05:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=ovD0oordyy2ej+p9pMEJcoVk84gzC3mui2U30vTuXZg=; b=UNBY0qu0GrSE+nTsSolj8Eg6j7RRBHq2W1vKmPyFzzzx0vjCkBV7vw150Depc3TkcZ9ru8hP3DKfPCNREmyWWCV1Jju27f85KIieZBLQ6ieYsNAZEVy7YEKA6eh1exQZh10AnFzP9foWCpCe7/gnRky5sxpVOxfF9OLdrj0VPgQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=eB5N2Sy3xi2AA9lkOhmQh58ijdGjZz/GhVa4Ain1QbHaIPlRSt+XgrCtX/BC4/rGycsQJS2k9BDVxvuSNzOxf3S252QUhGT0bn+z3LrMrcAJmEvGnaor6YfCGEAzbhX5qEo5Pxac2iVuhWneqmTKHoIPSW+4BNP5gyLHC/zxad8= Received: by 10.141.185.3 with SMTP id m3mr5118162rvp.236.1200985504462; Mon, 21 Jan 2008 23:05:04 -0800 (PST) Received: by 10.141.68.21 with HTTP; Mon, 21 Jan 2008 23:05:04 -0800 (PST) Message-ID: <2fd864e0801212305n5da155fejd4f8f27c23b7b3f@mail.gmail.com> Date: Tue, 22 Jan 2008 15:05:04 +0800 From: Astrodog To: "Dr. Aharon Friedman" In-Reply-To: <012101c85cbe$3d93fef0$292d280a@friedman.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <012101c85cbe$3d93fef0$292d280a@friedman.net> Cc: freebsd-current@freebsd.org Subject: Re: IPSEC on 7.0-PRERELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 07:05:05 -0000 On Jan 22, 2008 2:15 PM, Dr. Aharon Friedman wrote: > I am trying to compile a 7.0 kernel with IPSEC and I keep getting a > compilation error. Did the IPSEC options change? > > > > Aharon Friedman > Yes. You must have IPv6 to use SCTP. --- Harrison From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 08:34:04 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA81E16A46D for ; Tue, 22 Jan 2008 08:34:04 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp7.yandex.ru (smtp7.yandex.ru [213.180.200.45]) by mx1.freebsd.org (Postfix) with ESMTP id D0F3F13C46A for ; Tue, 22 Jan 2008 08:34:03 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mail.kirov.so-cdu.ru ([77.72.136.145]:27364 "EHLO [127.0.0.1]" smtp-auth: "bu7cher" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S738624AbYAVId7 (ORCPT ); Tue, 22 Jan 2008 11:33:59 +0300 X-Yandex-Spam: 1 X-Yandex-Front: smtp7 X-Yandex-TimeMark: 1200990839 X-MsgDayCount: 9 X-Comment: RFC 2476 MSA function at smtp7.yandex.ru logged sender identity as: bu7cher Message-ID: <4795AA75.5060000@yandex.ru> Date: Tue, 22 Jan 2008 11:33:57 +0300 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: "Dr. Aharon Friedman" References: <012101c85cbe$3d93fef0$292d280a@friedman.net> In-Reply-To: <012101c85cbe$3d93fef0$292d280a@friedman.net> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: IPSEC on 7.0-PRERELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 08:34:04 -0000 Dr. Aharon Friedman wrote: > I am trying to compile a 7.0 kernel with IPSEC and I keep getting a > compilation error. Did the IPSEC options change? Which error do you get? -- WBR, Andrey V. Elsukov From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 09:22:01 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32DCB16A417 for ; Tue, 22 Jan 2008 09:22:01 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id AAC4413C47E for ; Tue, 22 Jan 2008 09:21:59 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id E3E7B45E97; Tue, 22 Jan 2008 10:21:57 +0100 (CET) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 38E7345E8F; Tue, 22 Jan 2008 10:21:53 +0100 (CET) Date: Tue, 22 Jan 2008 10:21:41 +0100 From: Pawel Jakub Dawidek To: Ollivier Robert Message-ID: <20080122092141.GA56119@garage.freebsd.pl> References: <20071216205518.0A5665B2E@mail.bitblocks.com> <20071219080908.GA1335@garage.freebsd.pl> <20071219090715.GA2305@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o" Content-Disposition: inline In-Reply-To: <20071219090715.GA2305@keltia.freenix.fr> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-current@freebsd.org Subject: Re: ZFS melting under postgres... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 09:22:01 -0000 --IS0zKkzwUGydFO0o Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 19, 2007 at 10:07:15AM +0100, Ollivier Robert wrote: > According to Pawel Jakub Dawidek: > > It is ported to FreeBSD, but will be imported to the HEAD branch after > > 7.0-RELEASE. >=20 > Will it be in 7.1? [...] Yes, I'd like to have it in 7.1. > [...] Are there any bugs fixed that we'd like to have in 7.0 > anyway? Probably, but it's a bit hard to track small bug fixes in OpenSolaris as they do commits of many large changes at once as opposed to one-change-per-commit rule that we have in FreeBSD. I had a situation already where I was tracking a bug in FreeBSD/ZFS and when I found the bug, I went to compare with OpenSolaris version and found that it is already fixed, but the fix wasn't mentioned in the commit log... All in all, it is sometimes hard to tell which bugs are FreeBSD-specific and which are bugs in ZFS itself. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --IS0zKkzwUGydFO0o Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHlbWlForvXbEpPzQRAhkGAJ9xFpWRNEThaIvoZXyc0Jver5wL5QCg03zt mTX4wjpDh53mFsEKfUzL9Do= =wiLG -----END PGP SIGNATURE----- --IS0zKkzwUGydFO0o-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 09:29:28 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6146D16A41B for ; Tue, 22 Jan 2008 09:29:28 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from s200aog14.obsmtp.com (s200aog14.obsmtp.com [207.126.144.128]) by mx1.freebsd.org (Postfix) with SMTP id 88B9713C47E for ; Tue, 22 Jan 2008 09:29:26 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from source ([217.206.187.80]) by eu1sys200aob014.postini.com ([207.126.147.11]) with SMTP; Tue, 22 Jan 2008 09:29:22 UTC Received: from bill.mintel.co.uk (bill.mintel.co.uk [10.0.0.89]) by rodney.mintel.co.uk (Postfix) with ESMTP id 0F62D18141B; Tue, 22 Jan 2008 09:29:22 +0000 (GMT) Message-ID: <4795B771.7020607@tomjudge.com> Date: Tue, 22 Jan 2008 09:29:21 +0000 From: Tom Judge User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: Astrodog References: <012101c85cbe$3d93fef0$292d280a@friedman.net> <2fd864e0801212305n5da155fejd4f8f27c23b7b3f@mail.gmail.com> In-Reply-To: <2fd864e0801212305n5da155fejd4f8f27c23b7b3f@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Dr. Aharon Friedman" , freebsd-current@freebsd.org Subject: Re: IPSEC on 7.0-PRERELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 09:29:28 -0000 Astrodog wrote: > On Jan 22, 2008 2:15 PM, Dr. Aharon Friedman wrote: >> I am trying to compile a 7.0 kernel with IPSEC and I keep getting a >> compilation error. Did the IPSEC options change? >> >> >> >> Aharon Friedman >> > > Yes. You must have IPv6 to use SCTP. I'm not sure how you can come to this conclusion as the OP talks neither about IPv6 or SCTP only IPSEC. Also neither IPv6 or SCTP are pre requisites for IPSEC..... It would be helpful if the OP could post the error messages that he got during the compilation process. Tom From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 09:46:07 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC5B816A418 for ; Tue, 22 Jan 2008 09:46:07 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id 5E4DC13C44B for ; Tue, 22 Jan 2008 09:46:07 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 0B3EB45E8F; Tue, 22 Jan 2008 10:46:06 +0100 (CET) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 383A345683; Tue, 22 Jan 2008 10:45:58 +0100 (CET) Date: Tue, 22 Jan 2008 10:45:47 +0100 From: Pawel Jakub Dawidek To: Peter Losher Message-ID: <20080122094546.GB56119@garage.freebsd.pl> References: <47606C09.2070209@isc.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dTy3Mrz/UPE2dbVg" Content-Disposition: inline In-Reply-To: <47606C09.2070209@isc.org> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: FreeBSD Current Subject: Re: ZFS melting under postgres... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 09:46:07 -0000 --dTy3Mrz/UPE2dbVg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 12, 2007 at 03:17:29PM -0800, Peter Losher wrote: > Hi, >=20 > As part of our testing 7.0/ZFS we tried putting it thru it's paces > having ZFS act as our storage medium for some test pgsql db's (like for > sqlgrey, etc) and in both BETA2 and BETA4 (amd64) we get the same > results with a RAIDZ2 container: >=20 > -=3D- > Dec 12 14:24:12 nsa sqlgrey: fatal: setconfig error at > /usr/local/sbin/sqlgrey line 186. > Dec 12 16:49:53 nsa root: ZFS: checksum mismatch, zpool=3Dvault > path=3D/dev/ad4 offset=3D3665128448 size=3D22016 [...] > It basically corrupts the container from the inside until it fails > completely (usually withing 24-48 hours depending on how busy the db is) >=20 > I had thought it was a bad SATA replicator/controller, but we had that > replaced w/ one from Supermicro. So it's either the disks, or something > in ZFS. Anyone used ZFS to backend any db's (mysql or pgsql?) >=20 > If you need more info, let me know... It is hard for me to believe that this is FreeBSD-specific bug, because checksumming is below FreeBSD-specific code. Of course everything is possible, but I just think it's just unlikely. I'd start from configuring UFS on top of GELI with authentication. GELI will also detect silent data corruptions: # geli init -a hmac/md5 -e null -s 4096 -P -K /dev/null /dev/ad4 # geli attach -p -k /dev/null /dev/ad4 # dd if=3D/dev/zero of=3D/dev/ad4.eli bs=3D1m (this will take a while) # newfs -U /dev/ad4.eli # mount -o noatime /dev/ad4.eli /mnt/tmp Try your DB test on this file system. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --dTy3Mrz/UPE2dbVg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHlbtKForvXbEpPzQRApvOAJ9c9UGv8gWbubyuYk2GGthRsDERfQCgpslk MU38yYY2u6y00k9a/+yF210= =MnIM -----END PGP SIGNATURE----- --dTy3Mrz/UPE2dbVg-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 10:07:09 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1FBB16A417 for ; Tue, 22 Jan 2008 10:07:09 +0000 (UTC) (envelope-from bazerka@beardz.net) Received: from svr03-temp.btshosting.co.uk (svr03-temp.btshosting.co.uk [87.117.208.48]) by mx1.freebsd.org (Postfix) with ESMTP id EB7EB13C468 for ; Tue, 22 Jan 2008 10:07:08 +0000 (UTC) (envelope-from bazerka@beardz.net) Received: from [192.168.1.65] (host217-42-180-139.range217-42.btcentralplus.com [217.42.180.139]) (authenticated bits=0) by svr03-temp.btshosting.co.uk (8.14.1/8.14.1) with ESMTP id m0M9R4vF004632; Tue, 22 Jan 2008 09:27:04 GMT (envelope-from bazerka@beardz.net) Message-ID: <4795B6ED.8020902@beardz.net> Date: Tue, 22 Jan 2008 09:27:09 +0000 From: Jase Thew User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: "Dr. Aharon Friedman" References: <012101c85cbe$3d93fef0$292d280a@friedman.net> In-Reply-To: <012101c85cbe$3d93fef0$292d280a@friedman.net> Content-Type: text/plain; charset=windows-1250; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.92, clamav-milter version 0.92 on 87.117.208.49 X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: IPSEC on 7.0-PRERELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bazerka@beardz.net 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 Jan 2008 10:07:09 -0000 Dr. Aharon Friedman wrote: > I am trying to compile a 7.0 kernel with IPSEC and I keep getting a > compilation error. Did the IPSEC options change? > > > > Aharon Friedman > Did you specify "device crypto" in your kernel config too? This is now a requirement for IPSEC ( as noted in src/sys/conf/NOTES ). Regards, Jase. From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 11:41:17 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63F9316A418 for ; Tue, 22 Jan 2008 11:41:17 +0000 (UTC) (envelope-from iwasaki@jp.FreeBSD.org) Received: from locore.org (ns01.locore.org [218.45.21.227]) by mx1.freebsd.org (Postfix) with ESMTP id DC5EA13C455 for ; Tue, 22 Jan 2008 11:41:16 +0000 (UTC) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (celeron.v4.locore.org [192.168.0.10]) by locore.org (8.13.8/8.13.8/iwasaki) with ESMTP/inet id m0MBTF8Y068562; Tue, 22 Jan 2008 20:29:15 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Date: Tue, 22 Jan 2008 20:29:15 +0900 (JST) Message-Id: <20080122.202915.97273397.iwasaki@jp.FreeBSD.org> To: atkin901@yahoo.com From: Mitsuru IWASAKI In-Reply-To: References: X-Mailer: Mew version 3.3 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: strange message from ciss: ciss0: SENDING NOP MESSAGE FAILED X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 11:41:17 -0000 Hi, > I get the following on the console every few seconds after upgrading a hp > dl380g3 today to -current. My old kernel was from Aug 9th where I didn't > see this behavior. I'm not sure if that kernel contained 1.16 of > cissreg.h. > > ciss0: command status 0x2 (data underrun) scsi status 0x0 > ciss0: SENDING NOP MESSAGE FAILED Could you try the following patches? http://people.freebsd.org/~iwasaki/ciss/ciss-fix-20080122.patch Thanks From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 07:11:19 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8775916A417 for ; Tue, 22 Jan 2008 07:11:19 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46]) by mx1.freebsd.org (Postfix) with ESMTP id 516FE13C455 for ; Tue, 22 Jan 2008 07:11:19 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 2872C8C09A; Tue, 22 Jan 2008 01:11:19 -0600 (CST) Date: Tue, 22 Jan 2008 01:11:19 -0600 To: Dominic Fandrey Message-ID: <20080122071119.GA25774@soaustin.net> References: <478556AD.6090400@bsdforen.de> <4794534C.1040306@bsdforen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4794534C.1040306@bsdforen.de> User-Agent: Mutt/1.5.13 (2006-08-11) From: linimon@lonesome.com (Mark Linimon) X-Mailman-Approved-At: Tue, 22 Jan 2008 12:26:02 +0000 Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD's problems as seen by the BSDForen.de community X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 07:11:19 -0000 On Mon, Jan 21, 2008 at 09:09:48AM +0100, Dominic Fandrey wrote: > Herewith I apologize for starting this thread. It caused a lot of useless > noise on your lists and while our members have spent months intensively > discussing the topic, they are now very reluctant about acquiring the > information necessary to find the source of their problems. Unfortunately this doesn't solve anyone's problems :-( If we haven't opened up the lines of communication about how to get the specific information that is needed to debug complex problems, then the complex problems will remain unsolved. One of the subthreads that was spawned was actually quite productive, and has led to some ideas about how some of more expert users can help to work with less expert users on issues like this. (We can conclude that submitting them to the PR database is only effective if it happens to catch the attention of a committer on the way in). IMHO that subthread alone made the whole thread worthwhile -- despite the rest of the noise. I hope we can build on the postive momentum and interest from several new contributors. mcl From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 15:10:16 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 712C616A46C; Tue, 22 Jan 2008 15:10:16 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx1.freebsd.org (Postfix) with ESMTP id 3C6D613C4D5; Tue, 22 Jan 2008 15:10:16 +0000 (UTC) (envelope-from darrenr@freebsd.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 79BDE8D414; Tue, 22 Jan 2008 10:10:15 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 22 Jan 2008 10:10:15 -0500 X-Sasl-enc: FERHP24Mga6n5IPP2k3BwPfjuzTUW9RJ+uOmpavV8Czi 1201014614 Received: from [192.168.1.100] (dsl-202-45-110-141-static.VIC.netspace.net.au [202.45.110.141]) by mail.messagingengine.com (Postfix) with ESMTP id E12417C7B; Tue, 22 Jan 2008 10:10:13 -0500 (EST) Message-ID: <47960745.3050409@freebsd.org> Date: Wed, 23 Jan 2008 02:09:57 +1100 From: Darren Reed Organization: FreeBSD User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Robert Watson References: <20080106141157.I105@fledge.watson.org> <20080106170452.L105@fledge.watson.org> In-Reply-To: <20080106170452.L105@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Ivan Voras Subject: Re: When will ZFS become stable? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: darrenr@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2008 15:10:16 -0000 Robert Watson wrote: >... One advantage > Solaris has is that it runs primarily on expensive 64-bit servers with > lots of memory. Part of the problem on FreeBSD is that people run ZFS > on sytems with 32-bit CPUs and a lot less memory. It could be that ZFS > should be enforcing higher minimum hardware requirements to mount (i.e., > refusing to run on systems with 32-bit address spaces or <4gb of memory > and inadequate tuning). Before ZFS was released, I was using it internally on a 32bit desktop. It never panic'd although it did get very slow after a while because of the way it managed memory (and probably some bugs :) while in early alpha/beta. At work I run it on my Ultra20 desktop with Solaris 10. It has an AMD64 CPU and I'm pretty only 2GB of RAM, but I'll have to check on the RAM. Darren From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 15:49:40 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC7CC16A41A for ; Tue, 22 Jan 2008 15:49:40 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id D403713C442 for ; Tue, 22 Jan 2008 15:49:40 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.1/8.14.1) with ESMTP id m0MFner0003398; Tue, 22 Jan 2008 07:49:40 -0800 (PST) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.1/8.14.1/Submit) id m0MFndrh003396; Tue, 22 Jan 2008 07:49:39 -0800 (PST) (envelope-from obrien) Date: Tue, 22 Jan 2008 07:49:39 -0800 From: "David O'Brien" To: Maxim Konovalov Message-ID: <20080122154939.GA86052@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, Maxim Konovalov , Pyun YongHyeon , freebsd-current@freebsd.org References: <20080122053804.GA10963@cdnetworks.co.kr> <20080122091333.K9942@mp2.macomnet.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080122091333.K9942@mp2.macomnet.net> X-Operating-System: FreeBSD 8.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: Pyun YongHyeon , freebsd-current@freebsd.org Subject: Re: cvs in CURRENT broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2008 15:49:41 -0000 On Tue, Jan 22, 2008 at 09:13:42AM +0300, Maxim Konovalov wrote: > On Tue, 22 Jan 2008, 14:38+0900, Pyun YongHyeon wrote: > > > When I try to update sources with cvs on latest CURRENT, I always get the > > following. > > > > 504 [monster: ~/NetBSD]export CVSROOT=:pserver:anoncvs@anoncvs.NetBSD.org:/cvsroot > > 505 [monster: ~/NetBSD]cvs login > > Logging in to :pserver:anoncvs@anoncvs.netbsd.org:2401/cvsroot > > CVS password: > > Assertion failed: ((run->regs_mask[elm] & (1U << bit)) == 0), function arena_run_reg_dalloc, file /usr/src/lib/libc/stdlib/malloc.c, line 2197. > > cvs [login aborted]: received abort signal > > > > Is it known issue of cvs-1.11.22? > > Sort of. > > http://lists.freebsd.org/pipermail/freebsd-current/2008-January/082546.html First I've seen of this. I'll look into it. -- -- David (obrien@FreeBSD.org) From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 15:58:18 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9434416A419 for ; Tue, 22 Jan 2008 15:58:18 +0000 (UTC) (envelope-from scode@hyperion.scode.org) Received: from hyperion.scode.org (hyperion.scode.org [85.17.42.115]) by mx1.freebsd.org (Postfix) with ESMTP id 702C013C469 for ; Tue, 22 Jan 2008 15:58:18 +0000 (UTC) (envelope-from scode@hyperion.scode.org) Received: by hyperion.scode.org (Postfix, from userid 1001) id 99ABE23C431; Tue, 22 Jan 2008 16:42:54 +0100 (CET) Date: Tue, 22 Jan 2008 16:42:54 +0100 From: Peter Schuller To: Thomas Vogt Message-ID: <20080122154254.GA28963@hyperion.scode.org> References: <479515FF.1010709@bsdunix.ch> <200801212224.m0LMOoP7072911@fire.js.berklix.net> <47952019.3010309@bsdunix.ch> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V" Content-Disposition: inline In-Reply-To: <47952019.3010309@bsdunix.ch> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: "Julian H. Stacey" , freebsd-current@freebsd.org Subject: Re: Can't delete any files on my filled up ZFS pool X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 15:58:18 -0000 --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable >> There will doubtless be better ZFS answers, but could be interesting >> to hear if either of above could work. >=20 > I hope there will be a "ZFS" answer :) It used to be that this situation could arise even without snapshots or such "mitigating" circumstances. I'm pretty sure this was fixed, such that you would not get into a catch-22 under such circumstances. However I don't have the ML post I read this in, and I do not know whether the fix has been integrated into FreeBSD (though this was a while ago, so I would have guess it had). -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org --xHFwDpU9dbj6ez1V Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHlg7+DNor2+l1i30RAuK3AKCMyZqJWRMA/REig5GDeMH17ngoWQCghmh6 DiPo65pBVrvctQlLRgXD5kU= =NLfh -----END PGP SIGNATURE----- --xHFwDpU9dbj6ez1V-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 13:54:15 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01D4616A41B for ; Tue, 22 Jan 2008 13:54:15 +0000 (UTC) (envelope-from gizmen@blurp.pl) Received: from albion.azs.pwr.wroc.pl (albion.azs.pwr.wroc.pl [156.17.17.145]) by mx1.freebsd.org (Postfix) with ESMTP id B0FE313C447 for ; Tue, 22 Jan 2008 13:54:14 +0000 (UTC) (envelope-from gizmen@blurp.pl) Received: from [10.8.1.58] (unknown [213.172.177.22]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by albion.azs.pwr.wroc.pl (Postfix) with ESMTP id 656661152C for ; Tue, 22 Jan 2008 14:38:55 +0100 (CET) From: Bartosz Giza Organization: BLURP.pl To: freebsd-current@freebsd.org Date: Tue, 22 Jan 2008 14:38:53 +0100 User-Agent: KMail/1.9.7 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801221438.53254.gizmen@blurp.pl> X-Mailman-Approved-At: Tue, 22 Jan 2008 16:08:18 +0000 Subject: bsnmpd daemon eating all 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: Tue, 22 Jan 2008 13:54:15 -0000 Hi, I am using dell poweredge sc440 router with one xeon dual core cpu. This is basicly only router for dummynet firewall dhcpd and named. I want to run bsnmpd daemon but when i start it it starts eating all cpu from one core. I have run truss to check what it is doing and i have got huge amount of such syscalls gettimeofday({1201008182.366354},0x0) = 0 (0x0) I want to use this daemon because it is in base system but if i could not run this daemon in normal way i will be forced to use net-snmpd port. I have basic config with hotres module added. I am running freebsd 7.0-prerelease. Alsa what is strange i have exactly the same machine with freebsd 7.0-prerelase but with only one network card for testing and bsnmpd behaves normal. Could some one help me with this. I can send dump from truss or even do some more testing. Second strange thing is when i have compiled kernel with ULE scheduler bsnmpd shoed me 100% cpu utilization on both cores for all time. And after recompiling kernel with 4BSD it shows good numbers for cpu utilization. PS. Please cc me i am subscribed to the list. From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 16:25:15 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D80E16A417 for ; Tue, 22 Jan 2008 16:25:15 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from smtp-1.dlr.de (smtp-1.dlr.de [195.37.61.185]) by mx1.freebsd.org (Postfix) with ESMTP id D568613C46B for ; Tue, 22 Jan 2008 16:25:14 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from knop-beagle.kn.op.dlr.de ([129.247.173.6]) by smtp-1.dlr.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Tue, 22 Jan 2008 17:25:12 +0100 Date: Tue, 22 Jan 2008 17:25:15 +0100 (CET) From: Harti Brandt X-X-Sender: brandt_h@knop-beagle.kn.op.dlr.de To: Bartosz Giza In-Reply-To: <200801221438.53254.gizmen@blurp.pl> Message-ID: <20080122172058.Y94121@knop-beagle.kn.op.dlr.de> References: <200801221438.53254.gizmen@blurp.pl> X-OpenPGP-Key: harti@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 22 Jan 2008 16:25:12.0423 (UTC) FILETIME=[5CE36F70:01C85D13] Cc: freebsd-current@freebsd.org Subject: Re: bsnmpd daemon eating all cpu X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Harti Brandt List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2008 16:25:15 -0000 Hi, On Tue, 22 Jan 2008, Bartosz Giza wrote: BG>I am using dell poweredge sc440 router with one xeon dual core cpu. BG>This is basicly only router for dummynet firewall dhcpd and named. BG>I want to run bsnmpd daemon but when i start it it starts eating all cpu from BG>one core. BG>I have run truss to check what it is doing and i have got huge amount of such BG>syscalls BG>gettimeofday({1201008182.366354},0x0) = 0 (0x0) BG> BG>I want to use this daemon because it is in base system but if i could not run BG>this daemon in normal way i will be forced to use net-snmpd port. BG>I have basic config with hotres module added. BG>I am running freebsd 7.0-prerelease. BG>Alsa what is strange i have exactly the same machine with freebsd BG>7.0-prerelase but with only one network card for testing and bsnmpd behaves BG>normal. BG>Could some one help me with this. I can send dump from truss or even do some BG>more testing. Could you please disable all modules? Just comment out all lines starting from the Load MIB-2 module line. What does it do then? BG>Second strange thing is when i have compiled kernel with ULE scheduler bsnmpd BG>shoed me 100% cpu utilization on both cores for all time. And after BG>recompiling kernel with 4BSD it shows good numbers for cpu utilization. I have a report about this and there it says that the reason is the kern.ccpu variable beeing 0 for ULE. Unfortunately I was not able to work on this because of RealJob. I should probably look into this. harti From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 17:27:36 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D0DCD16A417 for ; Tue, 22 Jan 2008 17:27:36 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.230]) by mx1.freebsd.org (Postfix) with ESMTP id 935C413C45D for ; Tue, 22 Jan 2008 17:27:36 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by wr-out-0506.google.com with SMTP id 68so921940wra.13 for ; Tue, 22 Jan 2008 09:27:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=YDMecOYvBI+tFY3sxM/4sIK4UgEqd8KZQmtj+Dn5egI=; b=dlQrsX9shnPHpZHmNL5/9kB0JoLerb4ImxHX7fb5n9tQRDyIVk/qZky6IZ3QKK19PehJOmp2+lr8zPzQ2vCyqtaU6nxWKjT5GvpfFQBt3wtfFcSjIdhrCfQXSr1hZhpRKWyWfnuVy1R6frnzaLpSsWdRN+ZkNrcdB+Gl9HJGGSw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=VX9PGsH/GdDj/cMue5QfIrKMJSabp7FNSy3xbEqsfUlFhAfpX1hpD+iQFyNe6nInP8IwPLo4vjgSgOy17yM7IICtgYD8dCP1MPlxsZnZT0f1qtjkefdMbZbPZKPK8HA54plYlaT+jJU7lx+TSlyaxoRRHGBfbR53hbNDs3jebVU= Received: by 10.142.52.9 with SMTP id z9mr4227048wfz.134.1201022854249; Tue, 22 Jan 2008 09:27:34 -0800 (PST) Received: by 10.142.178.11 with HTTP; Tue, 22 Jan 2008 09:27:34 -0800 (PST) Message-ID: <3a142e750801220927q3b818ecg464c6319b5be30ca@mail.gmail.com> Date: Tue, 22 Jan 2008 18:27:34 +0100 From: "Paul B. Mahol" To: freebsd-current MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: tcsh coredumps X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 17:27:36 -0000 % set autologout = (15 1) When entering password, or just pressing enter, tcsh will dump core. This bug is a bit old, I think. From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 17:47:05 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D517816A418; Tue, 22 Jan 2008 17:47:05 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.freebsd.org (Postfix) with ESMTP id 88F0113C4DD; Tue, 22 Jan 2008 17:47:05 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.6/8.13.6) with ESMTP id m0MHl4WK090477; Tue, 22 Jan 2008 12:47:04 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-current@FreeBSD.org Date: Tue, 22 Jan 2008 12:46:45 -0500 User-Agent: KMail/1.6.2 References: <200801181217.52788.jkim@FreeBSD.org> In-Reply-To: <200801181217.52788.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200801221247.02342.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.92/5521/Tue Jan 22 09:55:56 2008 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: freebsd-arch@FreeBSD.org Subject: Re: [RFC] SysV SHM on 64-bit platforms X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 17:47:06 -0000 On Friday 18 January 2008 12:17 pm, Jung-uk Kim wrote: > While I was working on kern/113218, I realized it is a bigger > problem than I originally thought: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=113218 > > Because fixing this PR breaks ABI, I had to make compat shims. But > the question is which branch to break? Since we are very close to > 7.0-RELEASE, the question became more complicated. A lot of people > are asking me to fix this PR because it is much needed fix for > large database installations, so I have to make a quick decision. > :-( FYI, re@ said "it's simply too late" for RELENG_7_0. Let's just shut up and fix ipc_perm and friends once and for all. ;-) Thank you all! Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 18:16:21 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 90CEC16A41B for ; Tue, 22 Jan 2008 18:16:21 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 4A4C013C469 for ; Tue, 22 Jan 2008 18:16:21 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JHNfR-00067N-8E for freebsd-current@freebsd.org; Tue, 22 Jan 2008 18:16:13 +0000 Received: from 78-0-80-205.adsl.net.t-com.hr ([78.0.80.205]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 22 Jan 2008 18:16:13 +0000 Received: from ivoras by 78-0-80-205.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 22 Jan 2008 18:16:13 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Tue, 22 Jan 2008 19:16:02 +0100 Lines: 38 Message-ID: References: <200801221438.53254.gizmen@blurp.pl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigB77DB852CFEC8ABC30260323" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 78-0-80-205.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) In-Reply-To: <200801221438.53254.gizmen@blurp.pl> X-Enigmail-Version: 0.95.6 Sender: news Subject: Re: bsnmpd daemon eating all 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: Tue, 22 Jan 2008 18:16:21 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB77DB852CFEC8ABC30260323 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Bartosz Giza wrote: > Hi, >=20 > I am using dell poweredge sc440 router with one xeon dual core cpu. > This is basicly only router for dummynet firewall dhcpd and named. > I want to run bsnmpd daemon but when i start it it starts eating all cp= u from=20 > one core. I can sort-of confirm this, but on 6-STABLE, 4BSD scheduler, and not=20 "all CPU" but just an unreasonable chunk. The usage seems to increase=20 with load (this is a PHP+pgsql web server): as the load increases,=20 bsnmpd uses more and more CPU. Don't know exactly what causes it - could = be network or disk IO (does it somehow "listen" for IO events??). As=20 this is silly and I need the CPU for Real Work, I've disabled it. --------------enigB77DB852CFEC8ABC30260323 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHljLildnAQVacBcgRAlkBAKCPGWmp7zNlK8Xbg7prlCs1CnsAkACgnCOp gnmep+zlzWskwPFUqVM+cUM= =auMu -----END PGP SIGNATURE----- --------------enigB77DB852CFEC8ABC30260323-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 18:27:07 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5D0B16A419 for ; Tue, 22 Jan 2008 18:27:07 +0000 (UTC) (envelope-from pawel.worach@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.freebsd.org (Postfix) with ESMTP id 53A1E13C448 for ; Tue, 22 Jan 2008 18:27:07 +0000 (UTC) (envelope-from pawel.worach@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so528157nfb.33 for ; Tue, 22 Jan 2008 10:27:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=Rdg7fVbBIrtZmALKM4U7LaYVT9JLil360KrSrZI7MoU=; b=bVUbo6sMVk8619yt9S+mmx9EgtSei+59+DqcJh8+7ioJbVL+nCZabdko4vc1t0uzTPUZpVsz1h7rUouMlTzQkA6hkKzfE4UxuDUkLO9bjAVcVxnW+nZ6sPsOlzgRygUlQJNdz9U6nxmq0dwMH17WKfd/YoXDAZrLi/FsAP6AkeY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=kACI79pWBJlr3Ry8Xc7nYJ0b1JTRtW37gZ2qjMWg1lili+4evjL6MEIkgNb0g9GFjtsbbOH7CGGkswIExts3Z6JGrVHMmRYdJeWQ5JjbG0x1DanidPMHwNpekqyo28XDm9OUDXUfCsQxUzmG3b5gA1I3+XaZt65Ln2smogBxG94= Received: by 10.78.201.10 with SMTP id y10mr11780941huf.11.1201026425333; Tue, 22 Jan 2008 10:27:05 -0800 (PST) Received: from ?192.168.10.200? ( [90.227.56.82]) by mx.google.com with ESMTPS id 7sm95083nfv.35.2008.01.22.10.27.03 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 22 Jan 2008 10:27:04 -0800 (PST) Message-ID: <4796356D.9080809@gmail.com> Date: Tue, 22 Jan 2008 19:26:53 +0100 From: Pawel Worach User-Agent: Thunderbird 2.0.0.9 (X11/20080119) MIME-Version: 1.0 To: Kostik Belousov References: <4792C32C.5010205@gmail.com> <20080122133835.GT57756@deviant.kiev.zoral.com.ua> In-Reply-To: <20080122133835.GT57756@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: page fault panic in scioctl and console-kit-daemon X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 18:27:08 -0000 Kostik Belousov wrote: > On Sun, Jan 20, 2008 at 04:42:36AM +0100, Pawel Worach wrote: >> Hi, >> >> While starting console-kit-daemon (sysutils/consolekit 0.2.3) during >> boot or in single-user mode the system panics. If I start it post-boot >> it runs fine. This is on 8.0-CURRENT from about 12 hours ago, another >> user also reported the same on RELENG_7. Any other information I can >> provide ? >> >> Fatal trap 12: page fault while in kernel mode >> fault virtual address = 0x4 >> fault code = supervisor read, page not present >> instruction pointer = 0x20:0xc04d2ab4 >> stack pointer = 0x28:0xe6499b18 >> frame pointer = 0x28:0xe6499b80 >> 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 = 134 (console-kit-daemon) >> Physical memory: 1014 MB >> Dumping 43 MB: 28 12 >> >> #8 0xc07a34a2 in trap (frame=0xe6499ad8) at >> /usr/src/sys/i386/i386/trap.c:489 >> #9 0xc079183b in calltrap () at /usr/src/sys/i386/i386/exception.s:146 >> #10 0xc04d2ab4 in scioctl (dev=0xc3b20d00, cmd=537163270, >> data=0xe6499c70 "\002", flag=1, td=0xc3d3c880) >> at /usr/src/sys/dev/syscons/syscons.c:1073 >> #11 0xc051ed1a in giant_ioctl (dev=0xc3b20d00, cmd=537163270, >> data=0xe6499c70 "\002", fflag=1, td=0xc3d3c880) >> at /usr/src/sys/kern/kern_conf.c:349 >> #12 0xc0598194 in cnioctl (dev=0xc3b20d00, cmd=537163270, >> data=0xe6499c70 "\002", flag=1, td=0xc3d3c880) >> ---Type to continue, or q to quit--- >> at /usr/src/sys/kern/tty_cons.c:521 > > Unless the virtual screen is opened, the screen state scr_stat structure > is not allocated. The following patch would fix the panic, but I do not > know how the console-kit would react to the ENXIO from the > VT_WAITACTIVE ioctl. Please, test it. Thanks! The patch works. -- Pawel From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 14:25:14 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB89916A46B for ; Tue, 22 Jan 2008 14:25:14 +0000 (UTC) (envelope-from AFriedman@drsns.com) Received: from bigmama.drsns.com (rrcs-71-41-74-142.se.biz.rr.com [71.41.74.142]) by mx1.freebsd.org (Postfix) with ESMTP id 9DD3513C478 for ; Tue, 22 Jan 2008 14:25:14 +0000 (UTC) (envelope-from AFriedman@drsns.com) Received: from aharonlap (rrcs-71-41-74-141.se.biz.rr.com [71.41.74.141]) by bigmama.drsns.com (8.14.2/8.13.8) with ESMTP id m0MEP8xr011606; Tue, 22 Jan 2008 09:25:09 -0500 (EST) (envelope-from AFriedman@drsns.com) From: "Dr. Aharon Friedman" To: References: <012101c85cbe$3d93fef0$292d280a@friedman.net> <4795B6ED.8020902@beardz.net> Date: Tue, 22 Jan 2008 09:25:07 -0500 Message-ID: <003901c85d02$96a78d60$292d280a@friedman.net> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 Thread-Index: Achc2PTP5+R19EyJRkmLaunCpzjugAAKUj6g In-Reply-To: <4795B6ED.8020902@beardz.net> X-Mailman-Approved-At: Tue, 22 Jan 2008 18:42:59 +0000 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: RE: IPSEC on 7.0-PRERELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 14:25:15 -0000 This looks like the solution. It did pass compile. I have not run it yet, but I am sure it will work. Here is the configuration part for IPSEC: options IPSEC #IP security (requires device crypto) options IPSEC_FILTERTUNNEL #filter ipsec packets from a tunnel device enc #IPsec interface device crypto # core crypto support device cryptodev # /dev/crypto for access to h/w Aharon -----Original Message----- From: Jase Thew [mailto:bazerka@beardz.net] Sent: Tuesday, January 22, 2008 4:27 AM To: Dr. Aharon Friedman Cc: freebsd-current@freebsd.org Subject: Re: IPSEC on 7.0-PRERELEASE Dr. Aharon Friedman wrote: > I am trying to compile a 7.0 kernel with IPSEC and I keep getting a > compilation error. Did the IPSEC options change? > > > > Aharon Friedman > Did you specify "device crypto" in your kernel config too? This is now a requirement for IPSEC ( as noted in src/sys/conf/NOTES ). Regards, Jase. No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.19.9/1237 - Release Date: 1/22/2008 11:04 AM No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.19.9/1237 - Release Date: 1/22/2008 11:04 AM From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 18:34:23 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D059C16A417 for ; Tue, 22 Jan 2008 18:34:23 +0000 (UTC) (envelope-from gizmen@blurp.pl) Received: from albion.azs.pwr.wroc.pl (albion.azs.pwr.wroc.pl [156.17.17.145]) by mx1.freebsd.org (Postfix) with ESMTP id 901A413C44B for ; Tue, 22 Jan 2008 18:34:23 +0000 (UTC) (envelope-from gizmen@blurp.pl) Received: from gizmen (blurp.t2.ds.pwr.wroc.pl [156.17.224.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by albion.azs.pwr.wroc.pl (Postfix) with ESMTP id 38D6711522; Tue, 22 Jan 2008 19:34:22 +0100 (CET) From: Bartosz Giza To: Harti Brandt , freebsd-current@freebsd.org Date: Tue, 22 Jan 2008 19:34:20 +0100 User-Agent: KMail/1.9.7 References: <200801221438.53254.gizmen@blurp.pl> <20080122172058.Y94121@knop-beagle.kn.op.dlr.de> In-Reply-To: <20080122172058.Y94121@knop-beagle.kn.op.dlr.de> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200801221934.20774.gizmen@blurp.pl> X-Mailman-Approved-At: Tue, 22 Jan 2008 18:57:31 +0000 Cc: Subject: Re: bsnmpd daemon eating all 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: Tue, 22 Jan 2008 18:34:23 -0000 Tuesday 22 of January 2008 17:25:15 Harti Brandt napisa=C5=82(a): > Hi, > > On Tue, 22 Jan 2008, Bartosz Giza wrote: > > BG>I am using dell poweredge sc440 router with one xeon dual core cpu. > BG>This is basicly only router for dummynet firewall dhcpd and named. > BG>I want to run bsnmpd daemon but when i start it it starts eating all c= pu > from BG>one core. > BG>I have run truss to check what it is doing and i have got huge amount = of > such BG>syscalls > BG>gettimeofday({1201008182.366354},0x0) =3D 0 (0x0) > BG> > BG>I want to use this daemon because it is in base system but if i could > not run BG>this daemon in normal way i will be forced to use net-snmpd > port. BG>I have basic config with hotres module added. > BG>I am running freebsd 7.0-prerelease. > BG>Alsa what is strange i have exactly the same machine with freebsd > BG>7.0-prerelase but with only one network card for testing and bsnmpd > behaves BG>normal. > BG>Could some one help me with this. I can send dump from truss or even do > some BG>more testing. > > Could you please disable all modules? Just comment out all lines starting > from the Load MIB-2 module line. What does it do then? When i turn off all modules bsnmpd uses 0% of cpu. When i have added this=20 snmp_mibII.so module it started again to use 100% of one core. On other UP kernels with 7-PRE bsnmpd behaves good. And also when i was try= ing=20 to find what is going on i found that it happens when there is quite bit of= =20 traffic on interfaces. =46or test purposes i have downed lan interface and bsnmpd stopped to use 1= 00%=20 of cpu. And when i have brought up lan interface bsnmpd started again to us= e=20 100% od cpu. So it is related to IP traffic. Right now i am using net-snmpd daemon and it uses almoust nothing of cpu. =2D-=20 Pozdrawiam Bartosz Giza From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 19:35:30 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BE8B16A421 for ; Tue, 22 Jan 2008 19:35:30 +0000 (UTC) (envelope-from mailinglist@nesluop.dk) Received: from unixdunk.nesluop.dk (cpe.atm4-0-51450.0x535f05ca.hrnxx12.customer.tele.dk [83.95.5.202]) by mx1.freebsd.org (Postfix) with SMTP id 66BE913C478 for ; Tue, 22 Jan 2008 19:35:29 +0000 (UTC) (envelope-from mailinglist@nesluop.dk) Received: (qmail 91300 invoked by uid 89); 22 Jan 2008 19:28:45 -0000 Received: from unknown (HELO ?192.168.1.100?) (192.168.1.100) by unixdunk.nesluop.dk with SMTP; 22 Jan 2008 19:28:45 -0000 Message-ID: <479643EC.4000908@nesluop.dk> Date: Tue, 22 Jan 2008 20:28:44 +0100 From: Chris Poulsen User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: pyunyh@gmail.com References: <20071225234723.GA1018@cdnetworks.co.kr> <4772D649.3010001@nesluop.dk> <20071227002252.GE1018@cdnetworks.co.kr> <20080116012154.GB84758@cdnetworks.co.kr> <478E7DF3.4080908@nesluop.dk> <20080117014013.GA89210@cdnetworks.co.kr> <478F98D7.5040007@nesluop.dk> <20080118010100.GC92718@cdnetworks.co.kr> <20080118082609.GA93423@cdnetworks.co.kr> <4790EBA8.9090500@nesluop.dk> <20080119060354.GA98043@cdnetworks.co.kr> In-Reply-To: <20080119060354.GA98043@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kevlo@freebsd.org, FreeBSD Current Subject: Re: Problem with nfe stability and throughput X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 19:35:30 -0000 Hi, I've had the chance to punish the atphy you suggested below (diff2 + suggested change). The driver seems slow (but "stable") when it is not being pushed (my ssh shell is lagging ;) and it seems to lock up within 10 secs (tried 3 times) when I try to perform a ftp transfer to the machine. By "lock-up" I see the network stops working. The ftp transfer stops, I'm unable to ping from the server and browsing the web from the machine also does not work. Manually doing ifconfig down/up brings the network back into a working state, I tried waiting a little to see if it recovered itself, but it didn't seem like it. So is there anything else I can do to help nailing this one? -- Regards Chris Pyun YongHyeon wrote: > On Fri, Jan 18, 2008 at 07:10:48PM +0100, Chris Poulsen wrote: > > Hi, > > > > Pyun YongHyeon wrote: > > >On Fri, Jan 18, 2008 at 10:01:00AM +0900, To Chris Poulsen wrote: > > > > On Thu, Jan 17, 2008 at 07:05:11PM +0100, Chris Poulsen wrote: > > > > > Hi, > > > > > > > > > > Pyun YongHyeon wrote: > > > > > >Would you show me the output of "ifconfig nfe0"? > > > > > > > > > > > nfe0: flags=8843 metric 0 > > > mtu 1500 > > > > > options=48 > > > > > ether 00:1d:60:6d:73:ec > > > > > inet 192.168.1.11 netmask 0xffffff00 broadcast 192.168.1.255 > > > > > media: Ethernet 100baseTX > > > > > status: active > > > > > > > > Hmmm, it seems that you've set media type manually without relying > > > > on automatic media detection. Is there any reason not using auto > > > > media type? How about using media type 'auto'? > > > > #ifconfig nfe0 media auto > > > > > > > > > >I've updated the experimental driver. Please revert previous patch and > > >apply the following one. > > > > > >http://people.freebsd.org/~yongari/atphy.diff2 > > > > > >And show me the 'ifconfig nfe0' output again. > > > > > > > I tried specifying the media type manually, when I was trying to get nfe > > up and running earlier, I've reverted to auto now. > > > > The box in question is currently running with your latest patch, I did > > manage to stress it (with a couple of concurrent ftp uploads+some web > > browing) into a state where it once again gave me a bunch of the following: > > > > kernel: nfe0: discard frame w/o leading ethernet header (len 4 pkt len 4) > > kernel: nfe0: discard frame w/o leading ethernet header (len 0 pkt len 0) > > last message repeated 12 times > > kernel: nfe0: discard frame w/o leading ethernet header (len 3 pkt len 3) > > kernel: nfe0: discard frame w/o leading ethernet header (len 11 pkt len 11) > > kernel: nfe0: discard frame w/o leading ethernet header (len 5 pkt len 5) > > kernel: nfe0: discard frame w/o leading ethernet header (len 5 pkt len 5) > > kernel: nfe0: link state changed to DOWN > > kernel: nfe0: link state changed to UP > > > > However bringing the interface down and up seemed to put it back into a > > normal state. (I just noticed that nfe0 went down/up again, without my > > Did you have to bring nfe(4) down and up manually due to network lockups? > > > interaction, if that matters). > > > > Maybe this would come from atphy(4) bug. atphy(4) does not seem to > reliabily detect an established link. > > > ifconfig nfe0 yields: > > > > nfe0: flags=8843 metric 0 mtu 1500 > > options=48 > > ether 00:1d:60:6d:73:ec > > inet 192.168.1.11 netmask 0xffffff00 broadcast 192.168.1.255 > > media: Ethernet autoselect (100baseTX ) > > status: active > > > > How about the following change? > From /usr/src/sys/dev/mii/athpy.c: > 288 ssr = PHY_READ(sc, ATPHY_SSR); > 289 if ((((bmcr & BMCR_AUTOEN) != 0) && ((bmsr & BMSR_ACOMP) == 0)) || > 290 (ssr & ATPHY_SSR_SPD_DPLX_RESOLVED) == 0) { > 291 /* Erg, still trying, I guess... */ > 292 mii->mii_media_active |= IFM_NONE; > 293 return; > 294 } > > To: > 288 ssr = PHY_READ(sc, ATPHY_SSR); > 289 if ((ssr & ATPHY_SSR_SPD_DPLX_RESOLVED) == 0) { > 290 /* Erg, still trying, I guess... */ > 291 mii->mii_media_active |= IFM_NONE; > 292 return; > 293 } > > Thanks for your patience and testing. > From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 20:01:53 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 071AB16A41B for ; Tue, 22 Jan 2008 20:01:53 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from smtp-1.dlr.de (smtp-1.dlr.de [195.37.61.185]) by mx1.freebsd.org (Postfix) with ESMTP id 99BCE13C46A for ; Tue, 22 Jan 2008 20:01:52 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from [192.168.2.100] ([172.21.151.1]) by smtp-1.dlr.de with Microsoft SMTPSVC(6.0.3790.1830); Tue, 22 Jan 2008 21:01:50 +0100 Message-ID: <47964BB9.8030602@dlr.de> Date: Tue, 22 Jan 2008 21:02:01 +0100 From: Hartmut Brandt Organization: German Aerospace Center User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Bartosz Giza References: <200801221438.53254.gizmen@blurp.pl> <20080122172058.Y94121@knop-beagle.kn.op.dlr.de> <200801221934.20774.gizmen@blurp.pl> In-Reply-To: <200801221934.20774.gizmen@blurp.pl> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-OriginalArrivalTime: 22 Jan 2008 20:01:50.0704 (UTC) FILETIME=[A077B700:01C85D31] Cc: freebsd-current@freebsd.org Subject: Re: bsnmpd daemon eating all 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: Tue, 22 Jan 2008 20:01:53 -0000 Bartosz Giza wrote: > Tuesday 22 of January 2008 17:25:15 Harti Brandt napisaÅ‚(a): >> Hi, >> >> On Tue, 22 Jan 2008, Bartosz Giza wrote: >> >> BG>I am using dell poweredge sc440 router with one xeon dual core cpu. >> BG>This is basicly only router for dummynet firewall dhcpd and named. >> BG>I want to run bsnmpd daemon but when i start it it starts eating all cpu >> from BG>one core. >> BG>I have run truss to check what it is doing and i have got huge amount of >> such BG>syscalls >> BG>gettimeofday({1201008182.366354},0x0) = 0 (0x0) >> BG> >> BG>I want to use this daemon because it is in base system but if i could >> not run BG>this daemon in normal way i will be forced to use net-snmpd >> port. BG>I have basic config with hotres module added. >> BG>I am running freebsd 7.0-prerelease. >> BG>Alsa what is strange i have exactly the same machine with freebsd >> BG>7.0-prerelase but with only one network card for testing and bsnmpd >> behaves BG>normal. >> BG>Could some one help me with this. I can send dump from truss or even do >> some BG>more testing. >> >> Could you please disable all modules? Just comment out all lines starting >> from the Load MIB-2 module line. What does it do then? > > When i turn off all modules bsnmpd uses 0% of cpu. When i have added this > snmp_mibII.so module it started again to use 100% of one core. > On other UP kernels with 7-PRE bsnmpd behaves good. And also when i was trying > to find what is going on i found that it happens when there is quite bit of > traffic on interfaces. > For test purposes i have downed lan interface and bsnmpd stopped to use 100% > of cpu. And when i have brought up lan interface bsnmpd started again to use > 100% od cpu. So it is related to IP traffic. I have a feeling that this is related to the 64-bit counter emulation. Could you please tell me what interfaces you have in that machine and on what speed they are running? Have you set any of the begemot* variables for MIB-2 in snmpd.conf (especially the polling related ones)? Maybe just send me the snmpd.conf? harti From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 20:06:08 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBC6D16A420 for ; Tue, 22 Jan 2008 20:06:08 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: from smtp803.mail.ird.yahoo.com (smtp803.mail.ird.yahoo.com [217.146.188.63]) by mx1.freebsd.org (Postfix) with SMTP id 26CC913C458 for ; Tue, 22 Jan 2008 20:06:07 +0000 (UTC) (envelope-from tom@tomjudge.com) Received: (qmail 52699 invoked from network); 22 Jan 2008 20:06:06 -0000 Received: from unknown (HELO ?192.168.1.2?) (thomasjudge@btinternet.com@86.140.145.126 with plain) by smtp803.mail.ird.yahoo.com with SMTP; 22 Jan 2008 20:06:06 -0000 X-YMail-OSG: Hl5lk.cVM1mhDD4o8HbrMTr6IZGMzqZZseTuyid6CH2tc6ONCIxl3NKKmD_33XsenC5byq7clQ-- X-Yahoo-Newman-Property: ymail-3 Message-ID: <47964CBA.6020603@tomjudge.com> Date: Tue, 22 Jan 2008 20:06:18 +0000 From: Tom Judge User-Agent: Thunderbird 1.5.0.13 (X11/20070824) MIME-Version: 1.0 To: Bartosz Giza References: <200801221438.53254.gizmen@blurp.pl> <20080122172058.Y94121@knop-beagle.kn.op.dlr.de> <200801221934.20774.gizmen@blurp.pl> In-Reply-To: <200801221934.20774.gizmen@blurp.pl> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org, Harti Brandt Subject: Re: bsnmpd daemon eating all 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: Tue, 22 Jan 2008 20:06:08 -0000 Bartosz Giza wrote: > Tuesday 22 of January 2008 17:25:15 Harti Brandt napisaÅ‚(a): >> Hi, >> >> On Tue, 22 Jan 2008, Bartosz Giza wrote: >> >> BG>I am using dell poweredge sc440 router with one xeon dual core cpu. >> BG>This is basicly only router for dummynet firewall dhcpd and named. >> BG>I want to run bsnmpd daemon but when i start it it starts eating all cpu >> from BG>one core. >> BG>I have run truss to check what it is doing and i have got huge amount of >> such BG>syscalls >> BG>gettimeofday({1201008182.366354},0x0) = 0 (0x0) >> BG> >> BG>I want to use this daemon because it is in base system but if i could >> not run BG>this daemon in normal way i will be forced to use net-snmpd >> port. BG>I have basic config with hotres module added. >> BG>I am running freebsd 7.0-prerelease. >> BG>Alsa what is strange i have exactly the same machine with freebsd >> BG>7.0-prerelase but with only one network card for testing and bsnmpd >> behaves BG>normal. >> BG>Could some one help me with this. I can send dump from truss or even do >> some BG>more testing. >> >> Could you please disable all modules? Just comment out all lines starting >> from the Load MIB-2 module line. What does it do then? > > When i turn off all modules bsnmpd uses 0% of cpu. When i have added this > snmp_mibII.so module it started again to use 100% of one core. > On other UP kernels with 7-PRE bsnmpd behaves good. And also when i was trying > to find what is going on i found that it happens when there is quite bit of > traffic on interfaces. > For test purposes i have downed lan interface and bsnmpd stopped to use 100% > of cpu. And when i have brought up lan interface bsnmpd started again to use > 100% od cpu. So it is related to IP traffic. > Right now i am using net-snmpd daemon and it uses almoust nothing of cpu. > > There is a problem with net-snmp in that it does not support the ifXTable mib on FreeBSD so you are stuck with 32bit counters on the network interfaces, which can easily overflow on GBit nics between polls. We where about to deploy bsnmpd behind net-snmpd and proxy the ifXTable mib to bsnmpd to try to avoid overflows, but if there is a problem with bsnmpd this may not be a good idea. Has anyone come across this problem on RELENG_6_2 ? Tom From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 20:10:31 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2629C16A420 for ; Tue, 22 Jan 2008 20:10:31 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (trang.nuxi.org [74.95.12.85]) by mx1.freebsd.org (Postfix) with ESMTP id 1115313C46E for ; Tue, 22 Jan 2008 20:10:31 +0000 (UTC) (envelope-from obrien@NUXI.org) Received: from dragon.nuxi.org (obrien@localhost [127.0.0.1]) by dragon.nuxi.org (8.14.1/8.14.1) with ESMTP id m0MKAUc5010597; Tue, 22 Jan 2008 12:10:30 -0800 (PST) (envelope-from obrien@dragon.nuxi.org) Received: (from obrien@localhost) by dragon.nuxi.org (8.14.1/8.14.1/Submit) id m0MKAUMU010596; Tue, 22 Jan 2008 12:10:30 -0800 (PST) (envelope-from obrien) Date: Tue, 22 Jan 2008 12:10:30 -0800 From: "David O'Brien" To: Pyun YongHyeon Message-ID: <20080122201030.GA10526@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, Pyun YongHyeon , freebsd-current@FreeBSD.org References: <20080122053804.GA10963@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080122053804.GA10963@cdnetworks.co.kr> X-Operating-System: FreeBSD 8.0-CURRENT User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-current@FreeBSD.org Subject: Re: cvs in CURRENT broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2008 20:10:31 -0000 On Tue, Jan 22, 2008 at 02:38:04PM +0900, Pyun YongHyeon wrote: > When I try to update sources with cvs on latest CURRENT, I always get the > following. > > 504 [monster: ~/NetBSD]export CVSROOT=:pserver:anoncvs@anoncvs.NetBSD.org:/cvsroot > 505 [monster: ~/NetBSD]cvs login > Logging in to :pserver:anoncvs@anoncvs.netbsd.org:2401/cvsroot > CVS password: > Assertion failed: ((run->regs_mask[elm] & (1U << bit)) == 0), function arena_run_reg_dalloc, file /usr/src/lib/libc/stdlib/malloc.c, line 2197. > cvs [login aborted]: received abort signal > > Is it known issue of cvs-1.11.22? This is fixed in this cvs-1.11 branch commit: 2006-07-25 Mark D. Baushke * login.c (free_cvs_password): New function to control freeing of the static get_cvs_passwd() returned storage. (login): Call it. * cvs.h (free_cvs_password): Add prototype for it. * client.c (auth_server): Call it. [Alter the previous NetBSD coverity cid-3404 patch.] I'll look into when 1.11.23 will come out, or if I should import a snapshot of the 1.11 branch. From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 20:17:59 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9629C16A41A for ; Tue, 22 Jan 2008 20:17:59 +0000 (UTC) (envelope-from gizmen@blurp.pl) Received: from albion.azs.pwr.wroc.pl (albion.azs.pwr.wroc.pl [156.17.17.145]) by mx1.freebsd.org (Postfix) with ESMTP id 23E0213C45B for ; Tue, 22 Jan 2008 20:17:59 +0000 (UTC) (envelope-from gizmen@blurp.pl) Received: from gizmen (blurp.t2.ds.pwr.wroc.pl [156.17.224.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by albion.azs.pwr.wroc.pl (Postfix) with ESMTP id D426511522; Tue, 22 Jan 2008 21:17:57 +0100 (CET) From: Bartosz Giza To: Hartmut Brandt , freebsd-current@freebsd.org Date: Tue, 22 Jan 2008 21:17:56 +0100 User-Agent: KMail/1.9.7 References: <200801221438.53254.gizmen@blurp.pl> <200801221934.20774.gizmen@blurp.pl> <47964BB9.8030602@dlr.de> In-Reply-To: <47964BB9.8030602@dlr.de> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200801222117.56737.gizmen@blurp.pl> X-Mailman-Approved-At: Tue, 22 Jan 2008 20:29:29 +0000 Cc: Subject: Re: bsnmpd daemon eating all 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: Tue, 22 Jan 2008 20:17:59 -0000 Tuesday 22 of January 2008 21:02:01 napisa=C5=82e=C5=9B(-=C5=82a=C5=9B): > Bartosz Giza wrote: > > Tuesday 22 of January 2008 17:25:15 Harti Brandt napisa=C5=82(a): > >> Hi, > >> > >> On Tue, 22 Jan 2008, Bartosz Giza wrote: > >> > >> BG>I am using dell poweredge sc440 router with one xeon dual core cpu. > >> BG>This is basicly only router for dummynet firewall dhcpd and named. > >> BG>I want to run bsnmpd daemon but when i start it it starts eating all > >> cpu from BG>one core. > >> BG>I have run truss to check what it is doing and i have got huge amou= nt > >> of such BG>syscalls > >> BG>gettimeofday({1201008182.366354},0x0) =3D 0 (0x0) > >> BG> > >> BG>I want to use this daemon because it is in base system but if i cou= ld > >> not run BG>this daemon in normal way i will be forced to use net-snmpd > >> port. BG>I have basic config with hotres module added. > >> BG>I am running freebsd 7.0-prerelease. > >> BG>Alsa what is strange i have exactly the same machine with freebsd > >> BG>7.0-prerelase but with only one network card for testing and bsnmpd > >> behaves BG>normal. > >> BG>Could some one help me with this. I can send dump from truss or even > >> do some BG>more testing. > >> > >> Could you please disable all modules? Just comment out all lines > >> starting from the Load MIB-2 module line. What does it do then? > > > > When i turn off all modules bsnmpd uses 0% of cpu. When i have added th= is > > snmp_mibII.so module it started again to use 100% of one core. > > On other UP kernels with 7-PRE bsnmpd behaves good. And also when i was > > trying to find what is going on i found that it happens when there is > > quite bit of traffic on interfaces. > > For test purposes i have downed lan interface and bsnmpd stopped to use > > 100% of cpu. And when i have brought up lan interface bsnmpd started > > again to use 100% od cpu. So it is related to IP traffic. > > I have a feeling that this is related to the 64-bit counter emulation. > Could you please tell me what interfaces you have in that machine and on > what speed they are running? Have you set any of the begemot* variables > for MIB-2 in snmpd.conf (especially the polling related ones)? Maybe > just send me the snmpd.conf? > > harti Ok, i have one bge and two fxp interfaces. bge0: media: Ethernet autoselect (1000baseTX ) fxp0: media: Ethernet autoselect (100baseTX ) fxp1: media: Ethernet autoselect (100baseTX ) Below is my config, and i hardly changed anything exept of comunity and=20 listening ip. Thanks =2D-------------------- location :=3D "" contact :=3D "" system :=3D 1 # FreeBSD traphost :=3D localhost trapport :=3D 162 # Change this! read :=3D "" # Uncomment begemotSnmpdCommunityString.0.2 below that sets the community # string to enable write access. write :=3D "geheim" trap :=3D "mytrap" # # Configuration # %snmpd begemotSnmpdDebugDumpPdus =3D 2 begemotSnmpdDebugSyslogPri =3D 7 # # Set the read and write communities. # # The default value of the community strings is NULL (note, that this is # different from the empty string). This disables both read and write acces= s. # To enable read access only the read community string must be set. Setting # the write community string enables both read and write access with that # string. # # Be sure to understand the security implications of SNMPv2 - the community # strings are readable on the wire! # begemotSnmpdCommunityString.0.1 =3D $(read) # begemotSnmpdCommunityString.0.2 =3D $(write) begemotSnmpdCommunityDisable =3D 1 # open standard SNMP ports begemotSnmpdPortStatus..161 =3D 1 # open a unix domain socket begemotSnmpdLocalPortStatus."/var/run/snmpd.sock" =3D 1 begemotSnmpdLocalPortType."/var/run/snmpd.sock" =3D 4 # send traps to the traphost begemotTrapSinkStatus.[$(traphost)].$(trapport) =3D 4 begemotTrapSinkVersion.[$(traphost)].$(trapport) =3D 2 begemotTrapSinkComm.[$(traphost)].$(trapport) =3D $(trap) sysContact =3D $(contact) sysLocation =3D $(location) sysObjectId =3D 1.3.6.1.4.1.12325.1.1.2.1.$(system) #snmpEnableAuthenTraps =3D 2 # # Load MIB-2 module # begemotSnmpdModulePath."mibII" =3D "/usr/lib/snmp_mibII.so" # Force a polling rate for the 64-bit interface counters in case # the automatic computation is wrong (which may be the case if an interface # announces the wrong bit rate via its MIB). #%mibII #begemotIfForcePoll =3D 2000 # # Netgraph module # #begemotSnmpdModulePath."netgraph" =3D "/usr/lib/snmp_netgraph.so" # #%netgraph #begemotNgControlNodeName =3D "snmpd" # # pf(4) module # #begemotSnmpdModulePath."pf" =3D "/usr/lib/snmp_pf.so" # # Host resources module # This requires the mibII module. # begemotSnmpdModulePath."hostres" =3D "/usr/lib/snmp_hostres.so" # # Bridge module # This requires the mibII module. # #begemotSnmpdModulePath."bridge" =3D "/usr/lib/snmp_bridge.so" =2D-=20 Pozdrawiam Bartosz Giza From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 23:13:11 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 568E916A418 for ; Tue, 22 Jan 2008 23:13:11 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from mx-out.forthnet.gr (mx-out.forthnet.gr [193.92.150.104]) by mx1.freebsd.org (Postfix) with ESMTP id B517D13C455 for ; Tue, 22 Jan 2008 23:13:10 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from mx-av-03.forthnet.gr (mx-av.forthnet.gr [193.92.150.27]) by mx-out-02.forthnet.gr (8.14.0/8.14.0) with ESMTP id m0MND84V028686; Wed, 23 Jan 2008 01:13:08 +0200 Received: from MX-IN-03.forthnet.gr (mx-in-05.forthnet.gr [193.92.150.32]) by mx-av-03.forthnet.gr (8.14.1/8.14.1) with ESMTP id m0MND8fH013508; Wed, 23 Jan 2008 01:13:08 +0200 Received: from kobe.laptop (ppp133-151.adsl.forthnet.gr [62.1.124.151]) by MX-IN-03.forthnet.gr (8.14.2/8.14.2) with ESMTP id m0MND5rF010052; Wed, 23 Jan 2008 01:13:06 +0200 Authentication-Results: MX-IN-03.forthnet.gr smtp.mail=keramida@ceid.upatras.gr; spf=neutral Authentication-Results: MX-IN-03.forthnet.gr header.from=keramida@ceid.upatras.gr; sender-id=neutral Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.2/8.14.2) with ESMTP id m0MND3Yb001547; Wed, 23 Jan 2008 01:13:03 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by kobe.laptop (8.14.2/8.14.2/Submit) id m0MKAfqe001838; Tue, 22 Jan 2008 22:10:41 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Tue, 22 Jan 2008 22:10:41 +0200 From: Giorgos Keramidas To: "Paul B. Mahol" Message-ID: <20080122201040.GA1554@kobe.laptop> References: <3a142e750801220927q3b818ecg464c6319b5be30ca@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3a142e750801220927q3b818ecg464c6319b5be30ca@mail.gmail.com> X-Mailman-Approved-At: Tue, 22 Jan 2008 23:23:44 +0000 Cc: freebsd-current Subject: Re: tcsh coredumps X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 23:13:11 -0000 On 2008-01-22 18:27, "Paul B. Mahol" wrote: > % set autologout = (15 1) > > When entering password, or just pressing enter, tcsh will dump core. > > This bug is a bit old, I think. I can't reproduce this here. Which version of FreeBSD are you running? $ tcsh -l % % % % % set autologout = (15 1) % % passwd Changing local password for keramida Old Password: New Password: Retype New Password: % % From owner-freebsd-current@FreeBSD.ORG Tue Jan 22 23:45:41 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE4E116A419 for ; Tue, 22 Jan 2008 23:45:41 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6CE4813C467 for ; Tue, 22 Jan 2008 23:45:41 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (unknown [202.108.54.204]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTP id 0650828448 for ; Wed, 23 Jan 2008 07:45:40 +0800 (CST) Received: from localhost (unknown [202.108.54.204]) by tarsier.geekcn.org (Postfix) with ESMTP id AB297EB9403; Wed, 23 Jan 2008 07:45:39 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([202.108.54.204]) by localhost (mail.geekcn.org [202.108.54.204]) (amavisd-new, port 10024) with ESMTP id JYTgOLRk1eja; Wed, 23 Jan 2008 07:45:34 +0800 (CST) Received: from charlie.delphij.net (71.5.7.139.ptr.us.xo.net [71.5.7.139]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id 598B4EB8DCC; Wed, 23 Jan 2008 07:45:34 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:subject:x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=s/pjMZ8OtxznlhVtLinwyKMoXRItfBJHn2XuEtM2ZVhktv1dz5JsF8kHdGZGt7qe7 qdtmkn6YFwRwq6LmAIt3Q== Message-ID: <4796801C.7010601@delphij.net> Date: Tue, 22 Jan 2008 15:45:32 -0800 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20080122) MIME-Version: 1.0 To: FreeBSD Current X-Enigmail-Version: 0.95.5 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: RELENG_7_0: vm_thread_new: kstack allocation failed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2008 23:45:41 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have got a lot of this in dmesg output for RELENG_7_0 as of today: vm_thread_new: kstack allocation failed vm_thread_new: kstack allocation failed vm_thread_new: kstack allocation failed vm_thread_new: kstack allocation failed vm_thread_new: kstack allocation failed vm_thread_new: kstack allocation failed Any idea? Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHloAci+vbBBjt66ARAl+8AJ9MR39A2x4ynKQ06BOKAWEaoJfBVQCgkwDg jTeZCc0rALWjABp2wOBK2u0= =YRAd -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 02:19:46 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85B2E16A41A for ; Wed, 23 Jan 2008 02:19:46 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.235]) by mx1.freebsd.org (Postfix) with ESMTP id 2E68B13C457 for ; Wed, 23 Jan 2008 02:19:46 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so1546574nzf.13 for ; Tue, 22 Jan 2008 18:19:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=y5r1/ouK/AI+DcWErBY8wRIxo/wN5Y4WDBP5QYkQLGM=; b=bLKwOiswhLHSyZOOl+UZdpcGmclWAbmyNxWLposaox2+p6Lgf3z7IY+DpEpzQncFwGP9h44sDuThkPaZzE9Gv4AVF/fiI4ezJYZPQZ6RjkZ/6t6g/5SQxOx2ydb4Tma94AzHF30zwyXaHUJ7MUvcLVsh9fvupU6BiNOMNRvMkUE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=erxi1n2G7wafZAAfXUkoIgS8hnizrxiEzLwSeAyLnOnLWv0txNinlwHwEH+bxOciY2TZ31s5dxgfXKeFCZGZQW6TfbAiZwCazjqfITLXSDvHOxoRdmFnoENbaFWod4HEfG04Eqd0LRMwDHOpGxa7S6228BLKWq7Myb6/OmhTipg= Received: by 10.114.144.1 with SMTP id r1mr6734107wad.53.1201054785138; Tue, 22 Jan 2008 18:19:45 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id v35sm19355571wah.19.2008.01.22.18.19.42 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 22 Jan 2008 18:19:44 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m0N2JcRw014541 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Jan 2008 11:19:38 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m0N2JbBp014540; Wed, 23 Jan 2008 11:19:37 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 23 Jan 2008 11:19:37 +0900 From: Pyun YongHyeon To: Chris Poulsen Message-ID: <20080123021937.GA14495@cdnetworks.co.kr> References: <20071227002252.GE1018@cdnetworks.co.kr> <20080116012154.GB84758@cdnetworks.co.kr> <478E7DF3.4080908@nesluop.dk> <20080117014013.GA89210@cdnetworks.co.kr> <478F98D7.5040007@nesluop.dk> <20080118010100.GC92718@cdnetworks.co.kr> <20080118082609.GA93423@cdnetworks.co.kr> <4790EBA8.9090500@nesluop.dk> <20080119060354.GA98043@cdnetworks.co.kr> <479643EC.4000908@nesluop.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <479643EC.4000908@nesluop.dk> User-Agent: Mutt/1.4.2.1i Cc: kevlo@freebsd.org, FreeBSD Current Subject: Re: Problem with nfe stability and throughput X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com 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 Jan 2008 02:19:46 -0000 On Tue, Jan 22, 2008 at 08:28:44PM +0100, Chris Poulsen wrote: > Hi, > > I've had the chance to punish the atphy you suggested below (diff2 + > suggested change). The driver seems slow (but "stable") when it is not > being pushed (my ssh shell is lagging ;) and it seems to lock up within > 10 secs (tried 3 times) when I try to perform a ftp transfer to the > machine. By "lock-up" I see the network stops working. The ftp transfer > stops, I'm unable to ping from the server and browsing the web from the > machine also does not work. > > Manually doing ifconfig down/up brings the network back into a working > state, I tried waiting a little to see if it recovered itself, but it > didn't seem like it. > Hmm, this seems to be backward... Please revert previous patch and apply the following one. http://people.freebsd.org/~yongari/atphy.diff3 > So is there anything else I can do to help nailing this one? > What we need here is documentation for the PHY hardware. I have no idea why hardware vendors don't like to release their datasheet for their PHY. Most vendors provides datasheet for their PHY even though they don't want to reveal their ethernet controller datasheet. -- Regards, Pyun YongHyeon From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 03:01:24 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3169E16A417 for ; Wed, 23 Jan 2008 03:01:24 +0000 (UTC) (envelope-from jrh29@alumni.cwru.edu) Received: from QMTA08.emeryville.ca.mail.comcast.net (qmta08.emeryville.ca.mail.comcast.net [76.96.30.80]) by mx1.freebsd.org (Postfix) with ESMTP id 1222C13C43E for ; Wed, 23 Jan 2008 03:01:24 +0000 (UTC) (envelope-from jrh29@alumni.cwru.edu) Received: from OMTA14.emeryville.ca.mail.comcast.net ([76.96.30.60]) by QMTA08.emeryville.ca.mail.comcast.net with comcast id gQvY1Y0071HpZEs0A03g00; Wed, 23 Jan 2008 02:50:24 +0000 Received: from earth.knownspace ([69.255.34.108]) by OMTA14.emeryville.ca.mail.comcast.net with comcast id gSpU1Y00S2KzDb18a00000; Wed, 23 Jan 2008 02:49:30 +0000 X-Authority-Analysis: v=1.0 c=1 a=6I5d2MoRAAAA:8 a=yxaTE_L9TyYTWgdkrIgA:9 a=vFzc0qrUVJ4uC0Bj2ooA:7 a=Qh5saE2PBx_aqSXNHh3nQ0F7hHkA:4 a=SV7veod9ZcQA:10 a=LY0hPdMaydYA:10 a=mvjz27HkuDG8Dnm0gs8A:9 a=_p2FXCRIv7PyA5N189kj5vC7xaoA:4 a=rPt6xJ-oxjAA:10 From: Justin Hibbits To: freebsd-current@freebsd.org Date: Tue, 22 Jan 2008 21:49:47 -0500 User-Agent: KMail/1.9.7 References: <3a142e750801220927q3b818ecg464c6319b5be30ca@mail.gmail.com> In-Reply-To: <3a142e750801220927q3b818ecg464c6319b5be30ca@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1864803.u7OViWUlzg"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200801222150.00296.jrh29@alumni.cwru.edu> Subject: Re: tcsh coredumps X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 03:01:24 -0000 --nextPart1864803.u7OViWUlzg Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Tuesday 22 January 2008 12:27:34 Paul B. Mahol wrote: > % set autologout = (15 1) > > When entering password, or just pressing enter, tcsh will dump core. > > This bug is a bit old, I think. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" I can confirm this, 8-CURRENT from 2007-12-24. Exits with SIGABRT. - Justin --nextPart1864803.u7OViWUlzg Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHlqtYqt29EJDZlM4RAjQpAJ9/XvfqZDiZ26LwwufpcqzFKQ3XCQCglQQ6 dt1BhOxK++2eZdhotSrAspc= =oV4o -----END PGP SIGNATURE----- --nextPart1864803.u7OViWUlzg-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 03:47:42 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F5B116A469 for ; Wed, 23 Jan 2008 03:47:42 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.180]) by mx1.freebsd.org (Postfix) with ESMTP id CD88313C45A for ; Wed, 23 Jan 2008 03:47:41 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so4785546waf.3 for ; Tue, 22 Jan 2008 19:47:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from:to:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=8C+fvZDcwfRLlFHplYLtWcDXbyPCs/k/qziJ23vVs/s=; b=wWukNsj9LhaICGGenPRhRZ7X4wi4I/5rjLwPQRk/mu/Cla+44iWxndOeouLSaMO5jqF3H0T59YOOQeMOEkkhUn+KIuhdH1qP7+WKvmF5QZgVrMPeJZ0lGK289DDnzvA751mDFwmSQER6acgJl6tb+BWM7gI7hWJQBvW9L08JWBI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=dyCOdXRrWfsYuhbit2MkdWovelT3FT+Orfs2vihU09BX29q0btpNX1pjAikIGZ9yqMZ0VlAvIYAr4pgeCvJdhbmQQGS7fTNoHlemZLnhzyeC1OtYEQrhodIKR1HSqK9McS1e8upCW69d2vjn30HQD65kUAoYjbMiV25rmjsYtmw= Received: by 10.114.168.1 with SMTP id q1mr7509173wae.96.1201060061254; Tue, 22 Jan 2008 19:47:41 -0800 (PST) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id n30sm14187942wag.43.2008.01.22.19.47.38 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 22 Jan 2008 19:47:40 -0800 (PST) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m0N3lZqE014781 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Jan 2008 12:47:35 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m0N3lYaA014780; Wed, 23 Jan 2008 12:47:34 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 23 Jan 2008 12:47:34 +0900 From: Pyun YongHyeon To: obrien@freebsd.org, freebsd-current@freebsd.org Message-ID: <20080123034734.GC14495@cdnetworks.co.kr> References: <20080122053804.GA10963@cdnetworks.co.kr> <20080122201030.GA10526@dragon.NUXI.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080122201030.GA10526@dragon.NUXI.org> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: cvs in CURRENT broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com 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 Jan 2008 03:47:42 -0000 On Tue, Jan 22, 2008 at 12:10:30PM -0800, David O'Brien wrote: > On Tue, Jan 22, 2008 at 02:38:04PM +0900, Pyun YongHyeon wrote: > > When I try to update sources with cvs on latest CURRENT, I always get the > > following. > > > > 504 [monster: ~/NetBSD]export CVSROOT=:pserver:anoncvs@anoncvs.NetBSD.org:/cvsroot > > 505 [monster: ~/NetBSD]cvs login > > Logging in to :pserver:anoncvs@anoncvs.netbsd.org:2401/cvsroot > > CVS password: > > Assertion failed: ((run->regs_mask[elm] & (1U << bit)) == 0), function arena_run_reg_dalloc, file /usr/src/lib/libc/stdlib/malloc.c, line 2197. > > cvs [login aborted]: received abort signal > > > > Is it known issue of cvs-1.11.22? > > This is fixed in this cvs-1.11 branch commit: > > 2006-07-25 Mark D. Baushke > * login.c (free_cvs_password): New function to control freeing of > the static get_cvs_passwd() returned storage. > (login): Call it. > * cvs.h (free_cvs_password): Add prototype for it. > * client.c (auth_server): Call it. > [Alter the previous NetBSD coverity cid-3404 patch.] > > I'll look into when 1.11.23 will come out, or if I should import a > snapshot of the 1.11 branch. Thanks for clarifying it. -- Regards, Pyun YongHyeon From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 04:47:40 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9044216A46B for ; Wed, 23 Jan 2008 04:47:40 +0000 (UTC) (envelope-from erik@cederstrand.dk) Received: from mx2.itu.dk (unknown [130.226.142.29]) by mx1.freebsd.org (Postfix) with ESMTP id 5523613C457 for ; Wed, 23 Jan 2008 04:47:40 +0000 (UTC) (envelope-from erik@cederstrand.dk) Received: from [192.168.1.148] (stud1-15.itu.dk [130.226.140.15]) by mx2.itu.dk (Postfix) with ESMTP id 420C9F48077 for ; Wed, 23 Jan 2008 05:47:39 +0100 (CET) Message-ID: <4796C717.9000507@cederstrand.dk> Date: Wed, 23 Jan 2008 05:48:23 +0100 From: Erik Cederstrand User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Performance Tracker project update X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2008 04:47:40 -0000 Hi I'd like to send a small update on my progress on the Performance Tracker project. I now have a small setup of a server and a slave chugging along, currently collecting data. I'm following CURRENT and collecting results from super-smack and unixbench. The project still needs some work, but there's a temporary web interface to the data here: http://littlebit.dk:5000/plot/. Apart from the plotting it's possible to compare two dates and see the files that have changed. Error bars are 3*standard deviation, for the points with multiple measurements. Of interest is e.g. super-smack (select-key, 1 client) right when the GENERIC kernel was moved from the 4BSD to ULE scheduler on Oct. 19. Unixbench (arithmetic test, float) also has a significant jump on Oct. 3. There setup of the slave is documented roughly on the page but I'll be writing a full report and documentation over the next month. Comments are very welcome but please followup on performance@. Thanks, Erik From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 05:12:40 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2F7C16A419 for ; Wed, 23 Jan 2008 05:12:40 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from relay02.kiev.sovam.com (relay02.kiev.sovam.com [62.64.120.197]) by mx1.freebsd.org (Postfix) with ESMTP id 6867913C47E for ; Wed, 23 Jan 2008 05:12:40 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from [212.82.216.226] (helo=skuns.kiev.zoral.com.ua) by relay02.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1JHXue-000EhH-Bf for freebsd-current@freebsd.org; Wed, 23 Jan 2008 07:12:38 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by skuns.kiev.zoral.com.ua (8.14.1/8.14.1) with ESMTP id m0N5BwaM046352 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Jan 2008 07:11:58 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m0N5CFWN069148; Wed, 23 Jan 2008 07:12:15 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2/Submit) id m0N5CFiI069147; Wed, 23 Jan 2008 07:12:15 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 23 Jan 2008 07:12:15 +0200 From: Kostik Belousov To: d@delphij.net Message-ID: <20080123051215.GU57756@deviant.kiev.zoral.com.ua> References: <4796801C.7010601@delphij.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="DpucUjQmhxB+SJDU" Content-Disposition: inline In-Reply-To: <4796801C.7010601@delphij.net> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Scanner-Signature: 7155bbd8d023de41950ebecbe4708355 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 2032 [Jan 22 2008] X-SpamTest-Info: helo_type=3 X-SpamTest-Info: {received from trusted relay: not dialup} X-SpamTest-Method: none X-SpamTest-Method: Local Lists X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0255], KAS30/Release Cc: FreeBSD Current Subject: Re: RELENG_7_0: vm_thread_new: kstack allocation failed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 05:12:40 -0000 --DpucUjQmhxB+SJDU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 22, 2008 at 03:45:32PM -0800, Xin LI wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > Hi, >=20 > I have got a lot of this in dmesg output for RELENG_7_0 as of today: >=20 > vm_thread_new: kstack allocation failed > vm_thread_new: kstack allocation failed > vm_thread_new: kstack allocation failed > vm_thread_new: kstack allocation failed > vm_thread_new: kstack allocation failed > vm_thread_new: kstack allocation failed >=20 > Any idea? Does it cause any problems aside from printing these messages ? What workload do you put on the machine ? The messages came from the failure of the kernel to allocate address space for the kernel stack for a thread being created. Previously, the system would panic encountering this situation. This may happen due to kernel_map address space depletion, for instance, by having a lot (on i386 machines with > 1Gb memory, ~40000) threads. --DpucUjQmhxB+SJDU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEARECAAYFAkeWzK4ACgkQC3+MBN1Mb4g2JwCeLauj/eM4Puvet6eJpw+VkNfH DyEAoMzuW0LM2hklvW69Y9xCKQzVxxIU =EirA -----END PGP SIGNATURE----- --DpucUjQmhxB+SJDU-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 05:16:59 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 644D416A419 for ; Wed, 23 Jan 2008 05:16:59 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from relay02.kiev.sovam.com (relay02.kiev.sovam.com [62.64.120.197]) by mx1.freebsd.org (Postfix) with ESMTP id EF4DC13C4E7 for ; Wed, 23 Jan 2008 05:16:58 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from [212.82.216.226] (helo=skuns.kiev.zoral.com.ua) by relay02.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1JHXyn-000G4J-Hl for freebsd-current@freebsd.org; Wed, 23 Jan 2008 07:16:58 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by skuns.kiev.zoral.com.ua (8.14.1/8.14.1) with ESMTP id m0N5GVms046700 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Jan 2008 07:16:32 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m0N5Gmwg069332; Wed, 23 Jan 2008 07:16:48 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2/Submit) id m0N5GmcF069331; Wed, 23 Jan 2008 07:16:48 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 23 Jan 2008 07:16:48 +0200 From: Kostik Belousov To: Pawel Worach Message-ID: <20080123051648.GV57756@deviant.kiev.zoral.com.ua> References: <4792C32C.5010205@gmail.com> <20080122133835.GT57756@deviant.kiev.zoral.com.ua> <4796356D.9080809@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5HT6cwC5gT1+UL1y" Content-Disposition: inline In-Reply-To: <4796356D.9080809@gmail.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Scanner-Signature: 9f090f397804869cf00fade203417d62 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 2032 [Jan 22 2008] X-SpamTest-Info: helo_type=3 X-SpamTest-Info: {received from trusted relay: not dialup} X-SpamTest-Method: none X-SpamTest-Method: Local Lists X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0255], KAS30/Release Cc: FreeBSD Current Subject: Re: page fault panic in scioctl and console-kit-daemon X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 05:16:59 -0000 --5HT6cwC5gT1+UL1y Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 22, 2008 at 07:26:53PM +0100, Pawel Worach wrote: > Kostik Belousov wrote: > >On Sun, Jan 20, 2008 at 04:42:36AM +0100, Pawel Worach wrote: > >>Hi, > >> > >>While starting console-kit-daemon (sysutils/consolekit 0.2.3) during=20 > >>boot or in single-user mode the system panics. If I start it post-boot= =20 > >>it runs fine. This is on 8.0-CURRENT from about 12 hours ago, another= =20 > >>user also reported the same on RELENG_7. Any other information I can=20 > >>provide ? > >> > >>Fatal trap 12: page fault while in kernel mode > >>fault virtual address =3D 0x4 > >>fault code =3D supervisor read, page not present > >>instruction pointer =3D 0x20:0xc04d2ab4 > >>stack pointer =3D 0x28:0xe6499b18 > >>frame pointer =3D 0x28:0xe6499b80 > >>code segment =3D base 0x0, limit 0xfffff, type 0x1b > >> =3D DPL 0, pres 1, def32 1, gran 1 > >>processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > >>current process =3D 134 (console-kit-daemon) > >>Physical memory: 1014 MB > >>Dumping 43 MB: 28 12 > >> > >>#8 0xc07a34a2 in trap (frame=3D0xe6499ad8) at=20 > >>/usr/src/sys/i386/i386/trap.c:489 > >>#9 0xc079183b in calltrap () at /usr/src/sys/i386/i386/exception.s:146 > >>#10 0xc04d2ab4 in scioctl (dev=3D0xc3b20d00, cmd=3D537163270, > >> data=3D0xe6499c70 "\002", flag=3D1, td=3D0xc3d3c880) > >> at /usr/src/sys/dev/syscons/syscons.c:1073 > >>#11 0xc051ed1a in giant_ioctl (dev=3D0xc3b20d00, cmd=3D537163270, > >> data=3D0xe6499c70 "\002", fflag=3D1, td=3D0xc3d3c880) > >> at /usr/src/sys/kern/kern_conf.c:349 > >>#12 0xc0598194 in cnioctl (dev=3D0xc3b20d00, cmd=3D537163270, > >> data=3D0xe6499c70 "\002", flag=3D1, td=3D0xc3d3c880) > >>---Type to continue, or q to quit--- > >> at /usr/src/sys/kern/tty_cons.c:521 > > > >Unless the virtual screen is opened, the screen state scr_stat structure > >is not allocated. The following patch would fix the panic, but I do not > >know how the console-kit would react to the ENXIO from the > >VT_WAITACTIVE ioctl. Please, test it. >=20 > Thanks! The patch works. To clarify: do you see any problems with the console-kit after the patch ? In particular, can you verify that the program functions correctly, esp. on the virtual terminals 1, 2 ... , whatever this means ? --5HT6cwC5gT1+UL1y Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEARECAAYFAkeWzb8ACgkQC3+MBN1Mb4gERQCgxzckcYwfHQ4+BX6ioF8tD1qA kU4AoIcc468dCUN4lfhyBat8Fd7E58NG =VQR0 -----END PGP SIGNATURE----- --5HT6cwC5gT1+UL1y-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 05:59:46 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF9FB16A418 for ; Wed, 23 Jan 2008 05:59:46 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id EF5AB13C4D3 for ; Wed, 23 Jan 2008 05:59:44 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (unknown [202.108.54.204]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTP id A7D3928448 for ; Wed, 23 Jan 2008 13:59:43 +0800 (CST) Received: from localhost (unknown [202.108.54.204]) by tarsier.geekcn.org (Postfix) with ESMTP id 337F6EB9513; Wed, 23 Jan 2008 13:59:43 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([202.108.54.204]) by localhost (mail.geekcn.org [202.108.54.204]) (amavisd-new, port 10024) with ESMTP id s8SxrTXiPQgw; Wed, 23 Jan 2008 13:59:37 +0800 (CST) Received: from charlie.delphij.net (c-67-161-39-180.hsd1.ca.comcast.net [67.161.39.180]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTP id 3E987EB9510; Wed, 23 Jan 2008 13:59:36 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=f55O7Bj80UawyzRIkIpvTt04JS8P3fFUkuHioBCJB7t2uWjI2QLzP886Y7bT08tdz 421AU5S3zUmWWezSwjvGw== Message-ID: <4796D7C5.3020307@delphij.net> Date: Tue, 22 Jan 2008 21:59:33 -0800 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.9 (X11/20080122) MIME-Version: 1.0 To: Kostik Belousov References: <4796801C.7010601@delphij.net> <20080123051215.GU57756@deviant.kiev.zoral.com.ua> In-Reply-To: <20080123051215.GU57756@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 0.95.5 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , d@delphij.net Subject: Re: RELENG_7_0: vm_thread_new: kstack allocation failed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2008 05:59:46 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kostik Belousov wrote: > On Tue, Jan 22, 2008 at 03:45:32PM -0800, Xin LI wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi, >> >> I have got a lot of this in dmesg output for RELENG_7_0 as of today: >> >> vm_thread_new: kstack allocation failed >> vm_thread_new: kstack allocation failed >> vm_thread_new: kstack allocation failed >> vm_thread_new: kstack allocation failed >> vm_thread_new: kstack allocation failed >> vm_thread_new: kstack allocation failed >> >> Any idea? > > Does it cause any problems aside from printing these messages ? It causes some fork() to fail. > What workload do you put on the machine ? It was an rsync from NFS to ZFS with ~15M of files, and rsync will consume basically all physical memory. I end up with some 2GB active, 4GB wired thing. (The system has 8GB of RAM), and I added a "make -j9 buildworld" into the chaos to see if things get worse, and it did :-) > The messages came from the failure of the kernel to allocate address > space for the kernel stack for a thread being created. Previously, the > system would panic encountering this situation. Yes, I knew, previously it just panic and hangs there, and thanks a lot for fixing it =-) > This may happen due to kernel_map address space depletion, for instance, > by having a lot (on i386 machines with > 1Gb memory, ~40000) threads. It seems that I have hit some sort of "leak" or some exhaustion issue. Say, when the workload is gone, the system did not recover from the situation, and reboot worked fine. The system is sort of in production and it is about 20 miles away from my office. Do you want me to do some experiments for this? Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHltfEi+vbBBjt66ARAi+yAKC3HKy9YaOHNZK3l45NUVYDxc5EZQCfWOlN rTaCDmEc9ZZoizRRdcBOFF4= =/tP1 -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 07:03:48 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD92716A41B for ; Wed, 23 Jan 2008 07:03:48 +0000 (UTC) (envelope-from gahr@gahr.ch) Received: from cpanel03.rubas-s03.net (cpanel03.rubas-s03.net [195.182.222.73]) by mx1.freebsd.org (Postfix) with ESMTP id 4BD8113C43E for ; Wed, 23 Jan 2008 07:03:48 +0000 (UTC) (envelope-from gahr@gahr.ch) Received: from 80-218-191-236.dclient.hispeed.ch ([80.218.191.236] helo=gahrtop.localhost) by cpanel03.rubas-s03.net with esmtpsa (SSLv3:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1JHTN3-0007IU-Kr; Wed, 23 Jan 2008 01:21:37 +0100 Message-ID: <4796888A.2090108@gahr.ch> Date: Wed, 23 Jan 2008 01:21:30 +0100 From: Pietro Cerutti User-Agent: Thunderbird 2.0.0.9 (X11/20071121) MIME-Version: 1.0 To: Giorgos Keramidas References: <3a142e750801220927q3b818ecg464c6319b5be30ca@mail.gmail.com> <20080122201040.GA1554@kobe.laptop> In-Reply-To: <20080122201040.GA1554@kobe.laptop> X-Enigmail-Version: 0.95.5 OpenPGP: id=9571F78E; url=http://www.gahr.ch/pgp Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enigFEE638EA5598469850377D5D" X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cpanel03.rubas-s03.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - gahr.ch X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-current Subject: Re: tcsh coredumps X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 07:03:48 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFEE638EA5598469850377D5D Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Giorgos Keramidas wrote: > On 2008-01-22 18:27, "Paul B. Mahol" wrote: >> % set autologout =3D (15 1) >> >> When entering password, or just pressing enter, tcsh will dump core. >> >> This bug is a bit old, I think. >=20 > I can't reproduce this here. Which version of FreeBSD are you running?= >=20 > $ tcsh -l > % > % > % > % > % set autologout =3D (15 1) > % > % passwd > Changing local password for keramida > Old Password: > New Password: > Retype New Password: > % > % Nope. What paul is saying is the following: % tcsh % set autologout =3D (15 1) =2E.. now wait for a minute until the shell asks you for your password: Password: =2E.. now try to type your password and press enter.. tcsh will seg-fault= =2E tcsh 6.14.00 (Astron) 2005-03-25 on Linux doesn't suffer from this problem, though... --=20 Pietro Cerutti PGP Public Key: http://gahr.ch/pgp --------------enigFEE638EA5598469850377D5D Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHloiPwMJqmJVx944RCvKHAKCvcZIMDPUpT1X6FPUNJ9Mc7Es1EQCgneID +d5cr4ycWCK1c/QGjRylgUY= =Zb07 -----END PGP SIGNATURE----- --------------enigFEE638EA5598469850377D5D-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 07:35:02 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9ADF516A41B for ; Wed, 23 Jan 2008 07:35:02 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from cdptpa-omtalb.mail.rr.com (cdptpa-omtalb.mail.rr.com [75.180.132.120]) by mx1.freebsd.org (Postfix) with ESMTP id 5404F13C45D for ; Wed, 23 Jan 2008 07:35:02 +0000 (UTC) (envelope-from morganw@chemikals.org) Received: from shop.chemikals.org ([75.182.2.94]) by cdptpa-omta01.mail.rr.com with ESMTP id <20080123071410.RCQN16228.cdptpa-omta01.mail.rr.com@shop.chemikals.org>; Wed, 23 Jan 2008 07:14:10 +0000 Received: from volatile.chemikals.org (root@r74-193-170-223.bssrcmta01.bscyla.by.dh.suddenlink.net [74.193.170.223] (may be forged)) by shop.chemikals.org (8.14.1/8.14.1) with ESMTP id m0N7E58B033994; Wed, 23 Jan 2008 02:14:10 -0500 (EST) (envelope-from morganw@chemikals.org) Received: from localhost (morganw@localhost [127.0.0.1]) by volatile.chemikals.org (8.14.2/8.14.2) with ESMTP id m0MNVV8s002538; Tue, 22 Jan 2008 17:31:32 -0600 (CST) (envelope-from morganw@chemikals.org) Date: Tue, 22 Jan 2008 17:31:31 -0600 (CST) From: Wes Morgan To: Christian Walther In-Reply-To: <14989d6e0801201453y405bdd09lc35fb55234dff6ae@mail.gmail.com> Message-ID: References: <20080120141538.GH47164@e.0x20.net> <14989d6e0801201453y405bdd09lc35fb55234dff6ae@mail.gmail.com> User-Agent: Alpine 1.00 (BSF 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: Lars Engels , current@freebsd.org Subject: Re: sysutils/hal causes ath device timeout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 07:35:02 -0000 On Sun, 20 Jan 2008, Christian Walther wrote: > Hi Lars, > Hi List, > > > On 20/01/2008, Lars Engels wrote: >> Hi all, >> > [...] >> The hal daemon causes a timeout of my ath-driven Netgear WAG511 PC-Card. >> As soon as hald is started, the wireless connection is lost and I get >> this kernel message: >> ath0: device timeout >> ath0: ath_reset: unable to reset hardware; hal status 3230239248 >> > Same here: Card is an D-Link DWl-G650 > Jan 19 22:24:28 fairy kernel: ath0: mem > 0x88000000-0x8800ffff irq 16 at device 0.0 on cardbus0 > Jan 19 22:24:28 fairy kernel: ath0: Ethernet address: 00:19:5b:3a:82:be > Jan 19 22:24:28 fairy kernel: ath0: mac 7.9 phy 4.5 radio 5.6 > > dhclient is able to receive and set the IP address, but that's all. > > The message appear to be the same, too: > > Jan 20 23:26:26 fairy kernel: ath0: device timeout > Jan 20 23:26:26 fairy kernel: ath0: ath_reset: unable to reset > hardware; hal status 3232504036 > > >> When I eject the card then, the machine reboots. > > The reason for the panic seems to be: > > Jan 20 23:27:59 fairy savecore: reboot after panic: > resource_list_release: resource entry is not busy > >> >> Environment: >> >> FreeBSD 8.0-CURRENT #0: Mon Jan 14 22:37:27 CET 2008 >> lars@maggie.bsd-geek.de:/usr/obj/usr/src/sys/MAGGIE i386 >> > For me this is: > FreeBSD fairy.alashan.de 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #0: Sun > Jan 20 18:41:12 UTC 2008 zoot@fairy:/usr/obj/usr/src/sys/GENERIC > i386 > > I guess I'll rebuilt all ports now, just to make sure that everything > is fine. Maybe the problem goes away with a newly built hal. I can say ditto. I ran across this when playing with KDE4, and I am pretty sure that rebuilding hal won't fix it. I rebuilt *everything* from the ground up, multiple times, still had it. From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 08:36:06 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6707416A468 for ; Wed, 23 Jan 2008 08:36:06 +0000 (UTC) (envelope-from yuri.pankov@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.188]) by mx1.freebsd.org (Postfix) with ESMTP id 9F7C513C458 for ; Wed, 23 Jan 2008 08:36:05 +0000 (UTC) (envelope-from yuri.pankov@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so2644376rvb.43 for ; Wed, 23 Jan 2008 00:36:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=xjv1GcMmRB0yiE4uWfYLbH+bgr6lDvuZElTEXA88yzU=; b=oaRUYlR8EZnf9TEBPgfHsFUxmS1LZlMraNPV37aXNZTTJamarfyLcgjKMglH/iAnbMXaIUIYAt27dJ28kAiRbn4itnXytWAXJDLvTpfHZNJN8ImbE7r6gKN3zFaAzGNkbeCmxOor1Xpstx7XpVqBnEEPCFwSHtB+whob8RkzBQ0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=UsbXQKZtwDI+y4gD+rzzAvCWThnOob5argg6M4peP4FHkpq99ylrFcpZzilUKY+CtrIyWHqlwBBvD+XHDDiqa9v68Pe6CI9W4fs+f34F5Y5be02N/62RVYUmsQp9iHNNVfcaDMPzYX5RFVxv3I2/L40dAOqcdxxUCJ4WvmQxdDw= Received: by 10.140.132.8 with SMTP id f8mr6130241rvd.122.1201075736446; Wed, 23 Jan 2008 00:08:56 -0800 (PST) Received: by 10.141.115.8 with HTTP; Wed, 23 Jan 2008 00:08:56 -0800 (PST) Message-ID: Date: Wed, 23 Jan 2008 11:08:56 +0300 From: "Yuri Pankov" To: freebsd-current@freebsd.org In-Reply-To: <20080118112931.GB24750@darklight.org.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080118061338.GA24750@darklight.org.ru> <20080118112931.GB24750@darklight.org.ru> Subject: Re: SIGABRT on `cvs login` X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 08:36:06 -0000 And yet another reply to myself :-) It was fixed in 1.2.23, please see following bug report for details: https://savannah.nongnu.org/bugs/?22045 Yuri From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 08:40:53 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71D4116A418 for ; Wed, 23 Jan 2008 08:40:53 +0000 (UTC) (envelope-from gahr@gahr.ch) Received: from cpanel03.rubas-s03.net (cpanel03.rubas-s03.net [195.182.222.73]) by mx1.freebsd.org (Postfix) with ESMTP id 254E713C467 for ; Wed, 23 Jan 2008 08:40:53 +0000 (UTC) (envelope-from gahr@gahr.ch) Received: from town.bfh.ch ([147.87.98.171]) by cpanel03.rubas-s03.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1JHbAB-0001AV-MV; Wed, 23 Jan 2008 09:40:51 +0100 Message-ID: <4796FD91.2000602@gahr.ch> Date: Wed, 23 Jan 2008 09:40:49 +0100 From: Pietro Cerutti User-Agent: Thunderbird 1.5.0.9 (X11/20070104) MIME-Version: 1.0 To: "Paul B. Mahol" References: <3a142e750801220927q3b818ecg464c6319b5be30ca@mail.gmail.com> In-Reply-To: <3a142e750801220927q3b818ecg464c6319b5be30ca@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cpanel03.rubas-s03.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - gahr.ch X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-current Subject: Re: tcsh coredumps X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 08:40:53 -0000 Paul B. Mahol wrote: > % set autologout = (15 1) > > When entering password, or just pressing enter, tcsh will dump core. > > This bug is a bit old, I think. I've tried the 6.14 version. It doesn't seg-fault, but it doesn't accept the password, neither. It says "Invalid password" 3 times and then it automatically logs out anyway.. -- Pietro Cerutti PGP Public Key: http://gahr.ch/pgp From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 10:52:44 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42C3B16A417 for ; Wed, 23 Jan 2008 10:52:44 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from relay02.kiev.sovam.com (relay02.kiev.sovam.com [62.64.120.197]) by mx1.freebsd.org (Postfix) with ESMTP id CA94E13C468 for ; Wed, 23 Jan 2008 10:52:43 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from [212.82.216.226] (helo=skuns.kiev.zoral.com.ua) by relay02.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1JHdDl-000LYb-Ju for freebsd-current@freebsd.org; Wed, 23 Jan 2008 12:52:42 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by skuns.kiev.zoral.com.ua (8.14.1/8.14.1) with ESMTP id m0NAq8BG054728 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Jan 2008 12:52:08 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m0NAqPEU069628; Wed, 23 Jan 2008 12:52:25 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2/Submit) id m0NAqOf7069627; Wed, 23 Jan 2008 12:52:24 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 23 Jan 2008 12:52:24 +0200 From: Kostik Belousov To: d@delphij.net Message-ID: <20080123105224.GY57756@deviant.kiev.zoral.com.ua> References: <4796801C.7010601@delphij.net> <20080123051215.GU57756@deviant.kiev.zoral.com.ua> <4796D7C5.3020307@delphij.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="QD2trd1dTxsoIJGg" Content-Disposition: inline In-Reply-To: <4796D7C5.3020307@delphij.net> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Scanner-Signature: eacc24c597fa83a26e5f02f00d1ff66c X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 2033 [Jan 23 2008] X-SpamTest-Info: helo_type=3 X-SpamTest-Info: {received from trusted relay: not dialup} X-SpamTest-Method: none X-SpamTest-Method: Local Lists X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0255], KAS30/Release Cc: FreeBSD Current Subject: Re: RELENG_7_0: vm_thread_new: kstack allocation failed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 10:52:44 -0000 --QD2trd1dTxsoIJGg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 22, 2008 at 09:59:33PM -0800, Xin LI wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > Kostik Belousov wrote: > > On Tue, Jan 22, 2008 at 03:45:32PM -0800, Xin LI wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA1 > >> > >> Hi, > >> > >> I have got a lot of this in dmesg output for RELENG_7_0 as of today: > >> > >> vm_thread_new: kstack allocation failed > >> vm_thread_new: kstack allocation failed > >> vm_thread_new: kstack allocation failed > >> vm_thread_new: kstack allocation failed > >> vm_thread_new: kstack allocation failed > >> vm_thread_new: kstack allocation failed > >> > >> Any idea? > >=20 > > Does it cause any problems aside from printing these messages ? >=20 > It causes some fork() to fail. >=20 > > What workload do you put on the machine ? >=20 > It was an rsync from NFS to ZFS with ~15M of files, and rsync will > consume basically all physical memory. I end up with some 2GB active, > 4GB wired thing. (The system has 8GB of RAM), and I added a "make -j9 > buildworld" into the chaos to see if things get worse, and it did :-) >=20 > > The messages came from the failure of the kernel to allocate address > > space for the kernel stack for a thread being created. Previously, the > > system would panic encountering this situation. >=20 > Yes, I knew, previously it just panic and hangs there, and thanks a lot > for fixing it =3D-) >=20 > > This may happen due to kernel_map address space depletion, for instance, > > by having a lot (on i386 machines with > 1Gb memory, ~40000) threads. >=20 > It seems that I have hit some sort of "leak" or some exhaustion issue. > Say, when the workload is gone, the system did not recover from the > situation, and reboot worked fine. >=20 > The system is sort of in production and it is about 20 miles away from > my office. Do you want me to do some experiments for this? Yes, I want to know what exactly leaked. Ideally, I would like to see the series of the output of the vmstat -z and vmstat -m for some time before the system is bogged down. But, even the one snapshot of the vmstat -z/-m output immediately before things stop working would be good to look at. Output of the ps auxwwH is helpful too. --QD2trd1dTxsoIJGg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEARECAAYFAkeXHGgACgkQC3+MBN1Mb4iQbwCg79R8T9RFPR5tXS4ZjoaVVKUz 4PUAn2YsAkbFnh1WnFwv7+zo7SdfeJhs =lY8d -----END PGP SIGNATURE----- --QD2trd1dTxsoIJGg-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 12:40:27 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 001E016A418 for ; Wed, 23 Jan 2008 12:40:26 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from hs-out-2122.google.com (hs-out-0708.google.com [64.233.178.246]) by mx1.freebsd.org (Postfix) with ESMTP id 97E7C13C474 for ; Wed, 23 Jan 2008 12:40:26 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by hs-out-2122.google.com with SMTP id h53so2851296hsh.11 for ; Wed, 23 Jan 2008 04:40:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=TKpwc0X5rSJaKMWotg5G1rDOA4kiP4wPAFelhAv33iU=; b=R4sddi5+0YVL/0XCOTspYHO+GxtATNmP+z748KM31i22gdZrM4v38KJwfv3m55cWnVCtubNUa0oC9YnwAIc9DtvamsWKapUJnS2iVP3RSbINamc7arImj7PRJ2xIZCHtHkq5WPpLQQsnp/4aJMP2IDzviBfTiG8QAQU15oKpRUE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=fwwo1xQ1Xe97HEJBG/rIT+7m1BaVOGENwHIyrrkh0WEOvhX9zoQgqZPP8Ez/k3Rs77S2uXa9owwIKzpyYi/v8FfBmBuFNLethpNa2PK6hv3FebI+PNdXahcrR5HaCSK7M/PWtyHh0qKC+F0in1ZbfHEOuyncof1viVk5dqd4He8= Received: by 10.142.191.2 with SMTP id o2mr4813741wff.132.1201092025036; Wed, 23 Jan 2008 04:40:25 -0800 (PST) Received: by 10.142.178.11 with HTTP; Wed, 23 Jan 2008 04:40:24 -0800 (PST) Message-ID: <3a142e750801230440t15b93afbhb1e68c5f4f665294@mail.gmail.com> Date: Wed, 23 Jan 2008 13:40:24 +0100 From: "Paul B. Mahol" To: "Pietro Cerutti" In-Reply-To: <4796FD91.2000602@gahr.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3a142e750801220927q3b818ecg464c6319b5be30ca@mail.gmail.com> <4796FD91.2000602@gahr.ch> Cc: freebsd-current Subject: Re: tcsh coredumps X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 12:40:27 -0000 8.0 CURRENT here. I think I read somewhere in source (when just looking how locking stuff is implemented in tchs) that thing only works for root, but anyway it segfault in root login shell always, but for locking stuff it could just fork "lock -p" On Jan 23, 2008 9:40 AM, Pietro Cerutti wrote: > > Paul B. Mahol wrote: > > % set autologout = (15 1) > > > > When entering password, or just pressing enter, tcsh will dump core. > > > > This bug is a bit old, I think. > > I've tried the 6.14 version. > > It doesn't seg-fault, but it doesn't accept the password, neither. It > says "Invalid password" 3 times and then it automatically logs out anyway.. > > > -- > Pietro Cerutti > > PGP Public Key: > http://gahr.ch/pgp > From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 18:32:31 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 382A616A418; Wed, 23 Jan 2008 18:32:31 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.freebsd.org (Postfix) with ESMTP id 9F33613C442; Wed, 23 Jan 2008 18:32:30 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.4) with ESMTP id m0NIWIaL056657; Wed, 23 Jan 2008 21:32:18 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.4/Submit) id m0NIWHwg056656; Wed, 23 Jan 2008 21:32:17 +0300 (MSK) (envelope-from yar) Date: Wed, 23 Jan 2008 21:32:17 +0300 From: Yar Tikhiy To: Astrodog Message-ID: <20080123183217.GK30249@comp.chem.msu.su> References: <20071120141403.GE81260@comp.chem.msu.su> <4743342A.10507@FreeBSD.org> <20080101185451.S957@desktop> <20080121122402.GA63088@comp.chem.msu.su> <2fd864e0801210753y3fc49cd5v67ca75e0376bdb21@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2fd864e0801210753y3fc49cd5v67ca75e0376bdb21@mail.gmail.com> User-Agent: Mutt/1.5.9i Cc: Jeff Roberson , freebsd-current@freebsd.org Subject: Re: SCHED_ULE & niceness / rtprio X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 18:32:31 -0000 On Mon, Jan 21, 2008 at 11:53:49PM +0800, Astrodog wrote: > > Just to be sure I understand this correctly... the player stutters > when you *decrease* its priority (Or increase its niceness) only? The player stutters when I assign a realtime or idle priority to it, or when I decrease its niceness, e.g., to -10 or less. As for the priority question: AFAIK, there are 3 run queue groups in the kernel, for realtime, normal, and idle priority processes willing to run. Normal priority processes can run only if the real time queue group is empty, and idle priority processes run only if both the real time and normal queue groups are empty. My problem manifests itself if the process is not on the normal queue group. At the same time, the numeric value of its idle or realtime priority doesn't seem to matter. (Note that realtime priority of 16 and idle priority of 16 are totally different.) Therefore I cannot tell whether I increase or decrease its priority. I just move it to a different queue group. Of course, it can be said roughly that idprio(1) decreases process' priority and rtprio(1) increases it, but it isn't technically correct because the term `priority' already refers to the preference of a process within its current queue group. -- Yar From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 18:35:09 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91B4016A419; Wed, 23 Jan 2008 18:35:09 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.freebsd.org (Postfix) with ESMTP id EE67913C447; Wed, 23 Jan 2008 18:35:08 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.4) with ESMTP id m0NIYmFZ056742; Wed, 23 Jan 2008 21:34:48 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.4/Submit) id m0NIYgkS056735; Wed, 23 Jan 2008 21:34:42 +0300 (MSK) (envelope-from yar) Date: Wed, 23 Jan 2008 21:34:42 +0300 From: Yar Tikhiy To: Andrew Reilly Message-ID: <20080123183442.GL30249@comp.chem.msu.su> References: <20071120141403.GE81260@comp.chem.msu.su> <4743342A.10507@FreeBSD.org> <20080101185451.S957@desktop> <20080121122402.GA63088@comp.chem.msu.su> <20080122082714.760f966c@duncan.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080122082714.760f966c@duncan.reilly.home> User-Agent: Mutt/1.5.9i Cc: Jeff Roberson , Kris Kennaway , freebsd-current@FreeBSD.org Subject: Re: SCHED_ULE & niceness / rtprio X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 18:35:09 -0000 On Tue, Jan 22, 2008 at 08:27:14AM +1100, Andrew Reilly wrote: > On Mon, 21 Jan 2008 15:24:02 +0300 > Yar Tikhiy wrote: > > > What I did: was switching between windows of different apps (Firefox, > > Terminal) via Alt+Tab, or between virtual desktops with some windows > > on them using mouse, while playing an mp3 tune in the Totem player. > > Firefox isn't necessarily an adequate specification, if the > problem involves paging at all: it's VM footprint can change > dramatically depending on the page view history and how long > it's been running. If using Firefox to trigger the problem, it's enough to just start it with about:blank opened in its window. I think almost any X app can substitute for Firefox there. -- Yar From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 19:06:49 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 868E216A41B for ; Wed, 23 Jan 2008 19:06:49 +0000 (UTC) (envelope-from nikclayton@gmail.com) Received: from jc.ngo.org.uk (jc.ngo.org.uk [69.55.225.33]) by mx1.freebsd.org (Postfix) with ESMTP id 71D6A13C458 for ; Wed, 23 Jan 2008 19:06:49 +0000 (UTC) (envelope-from nikclayton@gmail.com) Received: from [192.168.3.3] (50-141.1-85.cust.bluewin.ch [85.1.141.50]) by jc.ngo.org.uk (8.13.8/8.13.8) with ESMTP id m0NIsB7W045204; Wed, 23 Jan 2008 10:54:42 -0800 (PST) (envelope-from nikclayton@gmail.com) Message-ID: <47978D60.4020805@gmail.com> Date: Wed, 23 Jan 2008 19:54:24 +0100 From: Nik Clayton User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: "Michael W. Lucas" References: <20080119214128.GA57253@bewilderbeast.blackhelicopters.org> In-Reply-To: <20080119214128.GA57253@bewilderbeast.blackhelicopters.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: * (1.988) RCVD_IN_SORBS_DUL X-Scanned-By: MIMEDefang 2.57 on 69.55.225.33 X-Mailman-Approved-At: Wed, 23 Jan 2008 19:11:12 +0000 Cc: i b , freebsd-current@freebsd.org Subject: Re: Taking screenshots during install X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 19:06:49 -0000 Michael W. Lucas wrote: > Install without taking screenshots. > > Then run in console-only mode. On the main console, run > sysinstall(8). On the second virtual console, use "vidcontrol -p" to > capture the contents of the first screen to a screenshot file. Then > use scr2png to transform that screen shot into a .png. +1 -- that's the specific use case that the '-p' option to vidcontrol, and the scr2* utilities were intended to support (it's how the installation screenshots in the Handbook were/are generated). N From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 19:20:54 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E474716A47A for ; Wed, 23 Jan 2008 19:20:54 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.178]) by mx1.freebsd.org (Postfix) with ESMTP id 2E55313C447 for ; Wed, 23 Jan 2008 19:20:53 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by py-out-1112.google.com with SMTP id u52so4338458pyb.10 for ; Wed, 23 Jan 2008 11:20:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:x-enigmail-version:content-type:content-transfer-encoding; bh=r5/cCfeJTltefYQB+EljJdBVN8sHeK9/lO4zTSxVJEI=; b=m16MyqD3mk4g/FaknAK8l9qFbGg13yFbnxaZqkJSqvGGKusyYNLcN2OcxJSYoQtbkLUUlhFzMhRoGhNGmV/Wqdk6EbxwkxC9Xr346ufCYVpTL6YwcjCxG+UUkMc5ZkyDypwFomekE4B+HdvuKsggUTuvmvwXTwkYimuF7jMJbhw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:x-enigmail-version:content-type:content-transfer-encoding; b=u1B5+6cx8r/nt3NqFjyzgghuJhxoJNOk34sijXx8GA6Bcvp7gqoyNfWSrbLjbTYslHchEpzTL2UGOTR+4OoQZNdz7CuI/fD7nXP8VIoyZTlB5jAWcMfDcpHz/O+D2qQGre2DyJNJF0sZ4IDy1ri3dvhVQycc8kr5/iT65Bl0iRY= Received: by 10.65.241.20 with SMTP id t20mr21353659qbr.88.1201116052994; Wed, 23 Jan 2008 11:20:52 -0800 (PST) Received: from flosoft.no-ip.biz ( [67.85.89.184]) by mx.google.com with ESMTPS id e16sm8190543qbe.10.2008.01.23.11.20.51 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 23 Jan 2008 11:20:52 -0800 (PST) Message-ID: <47979391.50006@gmail.com> Date: Wed, 23 Jan 2008 14:20:49 -0500 From: "Aryeh M. Friedman" User-Agent: Thunderbird 2.0.0.9 (X11/20080121) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: fetch fails on 8-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2008 19:20:55 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 flosoft# /usr/bin/fetch -s ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ports/ports.tar.gz > ports.size Segmentation fault (core dumped) (this can be found during a make install in /www {from local cvs repo}) According to a gdb backtrace it looks like a infinite recurse. #0 0x0000000800bd2457 in fclose () from /lib/libc.so.7 #1 0x000000080063bb88 in fetchStatFTP () from /usr/lib/libfetch.so.5 #2 0x00000000004021de in ?? () #3 0x0000000000403a40 in ?? () #4 0x0000000000401b65 in ?? () #5 0x000000080052a000 in ?? () #6 0x0000000000000000 in ?? () #7 0x0000000000000003 in ?? () #8 0x00007fffffffed80 in ?? () #9 0x00007fffffffed8f in ?? () #10 0x00007fffffffed92 in ?? () #11 0x0000000000000000 in ?? () #12 0x00007fffffffedcd in ?? () #13 0x00007fffffffedd9 in ?? () #14 0x00007fffffffede2 in ?? () #15 0x00007fffffffedf0 in ?? () #16 0x00007fffffffee05 in ?? () #17 0x00007fffffffee10 in ?? () #18 0x00007fffffffee1b in ?? () #19 0x00007fffffffee30 in ?? () #20 0x00007fffffffee3d in ?? () #21 0x00007fffffffee4f in ?? () #22 0x00007fffffffee8a in ?? () #23 0x00007fffffffee99 in ?? () #24 0x00007fffffffeea6 in ?? () #25 0x00007fffffffeeb1 in ?? () #26 0x00007fffffffeebe in ?? () #27 0x00007fffffffef15 in ?? () #28 0x00007fffffffef28 in ?? () #29 0x00007fffffffef34 in ?? () #30 0x00007fffffffef45 in ?? () #31 0x00007fffffffef54 in ?? () #32 0x00007fffffffef63 in ?? () #33 0x00007fffffffef74 in ?? () #34 0x00007fffffffef7c in ?? () #35 0x00007fffffffef88 in ?? () #36 0x00007fffffffef9f in ?? () #37 0x00007fffffffefab in ?? () #38 0x00007fffffffefb5 in ?? () #39 0x0000000000000000 in ?? () #40 0x0000000000000003 in ?? () #41 0x0000000000400040 in ?? () #42 0x0000000000000004 in ?? () #43 0x0000000000000038 in ?? () #44 0x0000000000000005 in ?? () #45 0x0000000000000007 in ?? () #46 0x0000000000000006 in ?? () #47 0x0000000000001000 in ?? () #48 0x0000000000000008 in ?? () #49 0x0000000000000000 in ?? () #50 0x0000000000000009 in ?? () #51 0x0000000000401ae0 in ?? () #52 0x0000000000000007 in ?? () #53 0x0000000800504000 in ?? () #54 0x0000000000000000 in ?? () ... #653 0x0000000000000000 in ?? () #654 0x247c8d48002454ff in ?? () #655 0x01a1c0c748006a10 in ?? () #656 0x66fdebf4050f0000 in ?? () #657 0x9066669066669066 in ?? () #658 0x00007fffffffeb90 in ?? () #659 0x0000000000000003 in ?? () #660 0x00007fffffffebb0 in ?? () #661 0x000000000000001b in ?? () Error accessing memory address 0x800000000000: Bad address. - -- Aryeh M. Friedman FloSoft Systems, Java Tool Developers Developer, not business, friendly http://www.flosoft-systems.com "Free software != Free beer" Blog: http://www.flosoft-systems.com/flosoft_systems_community/blogs/aryeh/index.php -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHl5ORQi2hk2LEXBARAptXAJwNVEjUNvjFmco7YEK95Ka1fH7k2QCfTNoP +sr9pZV6mCSwnB9KhHZYGW4= =Fvo5 -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 19:30:55 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0ECC816A468 for ; Wed, 23 Jan 2008 19:30:55 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: from syn.atarininja.org (syn.csh.rit.edu [129.21.60.158]) by mx1.freebsd.org (Postfix) with ESMTP id E9F3513C467 for ; Wed, 23 Jan 2008 19:30:54 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: by syn.atarininja.org (Postfix, from userid 1001) id 4AF065C5A; Wed, 23 Jan 2008 14:32:11 -0500 (EST) Date: Wed, 23 Jan 2008 14:32:11 -0500 From: Wesley Shields To: "Aryeh M. Friedman" Message-ID: <20080123193211.GG60410@atarininja.org> References: <47979391.50006@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47979391.50006@gmail.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-current@freebsd.org Subject: Re: fetch fails on 8-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2008 19:30:55 -0000 On Wed, Jan 23, 2008 at 02:20:49PM -0500, Aryeh M. Friedman wrote: > > flosoft# /usr/bin/fetch -s > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ports/ports.tar.gz > ports.size > Segmentation fault (core dumped) I can't reproduce this... wxs@rst ~ % fetch -s ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ports/ports.tar.gz > ports.size wxs@rst ~ % cat ports.size 39987735 wxs@rst ~ % uname -a FreeBSD rst.atarininja.org 8.0-CURRENT FreeBSD 8.0-CURRENT #3: Tue Dec 4 12:39:11 EST 2007 root@rst.atarininja.org:/usr/obj/usr/src/sys/GENERIC amd64 wxs@rst ~ % -- WXS From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 19:34:29 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45A0516A419 for ; Wed, 23 Jan 2008 19:34:29 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177]) by mx1.freebsd.org (Postfix) with ESMTP id 088FD13C4F7 for ; Wed, 23 Jan 2008 19:34:28 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by py-out-1112.google.com with SMTP id u52so4343761pyb.10 for ; Wed, 23 Jan 2008 11:34:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; bh=395zpTT0UZ3Yo/kyL7sDmzRdYH4pEJGVOWbBhTcZPqw=; b=C6bz6sIGwq+uYlLV83El5lct9FX4gK5G24EFZVBRbQBL3rMnECNkqVIXRcOMYOUDeaY7d3NvS237hteTgcBSIxsYaViyH4X6sn03wkcBMkExUpe0lLdGJUTGxXCNhxzqugwRCknYqt/Oi5rI9174XY/Z77p8/3gQbeyayJTh/70= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=IUOHEyEZKX6viI6p6IaPdzg5JFN2sfjfwBHnyODHKj9vT1eSqQ3Uu681SF4k7xy+LTU9CzmOohaITzya/H6vFvGxM7dYPvodynmecNP75UBVRp0CyY6AOJcpVs9UXU2rLgdbwECAa/LPPz0Bzr2YjMwmYviuKR/S2/0EkquqWas= Received: by 10.65.241.20 with SMTP id t20mr21381711qbr.88.1201116867870; Wed, 23 Jan 2008 11:34:27 -0800 (PST) Received: from flosoft.no-ip.biz ( [67.85.89.184]) by mx.google.com with ESMTPS id q16sm6142925qbq.0.2008.01.23.11.34.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 23 Jan 2008 11:34:27 -0800 (PST) Message-ID: <479796C2.30106@gmail.com> Date: Wed, 23 Jan 2008 14:34:26 -0500 From: "Aryeh M. Friedman" User-Agent: Thunderbird 2.0.0.9 (X11/20080121) MIME-Version: 1.0 To: Wesley Shields References: <47979391.50006@gmail.com> <20080123193211.GG60410@atarininja.org> In-Reply-To: <20080123193211.GG60410@atarininja.org> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: fetch fails on 8-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2008 19:34:29 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Wesley Shields wrote: > On Wed, Jan 23, 2008 at 02:20:49PM -0500, Aryeh M. Friedman wrote: >> flosoft# /usr/bin/fetch -s >> ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ports/ports.tar.gz > >> ports.size Segmentation fault (core dumped) > > I can't reproduce this... > > wxs@rst ~ % fetch -s > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ports/ports.tar.gz > > ports.size wxs@rst ~ % cat ports.size 39987735 wxs@rst ~ % uname -a > FreeBSD rst.atarininja.org 8.0-CURRENT FreeBSD 8.0-CURRENT #3: Tue > Dec 4 12:39:11 EST 2007 > root@rst.atarininja.org:/usr/obj/usr/src/sys/GENERIC amd64 wxs@rst > ~ % > That is weird because: flosoft# fetch -s ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ports/ports.tar.gz > ports.size Segmentation fault (core dumped) flosoft# cat ports.size flosoft# uname -a FreeBSD flosoft.no-ip.biz 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Tue Jan 22 23:37:49 EST 2008 aryeh@flosoft.no-ip.biz:/usr/obj/usr/src/sys/MONSTER amd64 The only difference in MONSTER vs. GENERIC is I added IPI_PREEMPTION and removed the debugging options. - -- Aryeh M. Friedman FloSoft Systems, Java Tool Developers Developer, not business, friendly http://www.flosoft-systems.com "Free software != Free beer" Blog: http://www.flosoft-systems.com/flosoft_systems_community/blogs/aryeh/index.php -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHl5bCQi2hk2LEXBARAjq9AJ9zcbBW68c00sqKTaeQYbf5MVaw+ACg7lVb e5tkxvCUFZBoezkiTAJTIbo= =AI+f -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 19:35:05 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F9F516A417 for ; Wed, 23 Jan 2008 19:35:05 +0000 (UTC) (envelope-from pawel.worach@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.freebsd.org (Postfix) with ESMTP id 0F10713C4D5 for ; Wed, 23 Jan 2008 19:35:01 +0000 (UTC) (envelope-from pawel.worach@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so667789nfb.33 for ; Wed, 23 Jan 2008 11:35:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=N02I746i7e9Y9C1LZTjX2xBBabVCjhz0UgqhYf849LE=; b=KGPhMao6KGen9q9B+8Gn1LUrc1JYyDoxzd4ITdcnp/3QVPtR8xWTCX7YVdYDlz/RDHQpfmtddZ9CqzjIE3oGerfGyCp1zwbjplS9fiu6pkI7B7uKSq5X+cX8ec3ZygdujwBCRfLEdsqGV63OqKqAWfs3zbgkiTSuEFqU0awun10= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=Sn+OFIgNYRvMXp9LkQI01ZOefnNUpRjeWZOeYFI6cgaM7zp8YzppqBYrc6sYw4R77LDwkbHS6gg1VfZruNqbtASJcTQ7nX73UGULzlrpJwasQ61c507EB6W6ZkwoZEm6WHTeD+iB690hYSEwODC7YKXDH/mVN3yNoPxw8jyLMCQ= Received: by 10.78.171.20 with SMTP id t20mr13954052hue.41.1201116899865; Wed, 23 Jan 2008 11:34:59 -0800 (PST) Received: from ?192.168.10.200? ( [90.227.56.82]) by mx.google.com with ESMTPS id c9sm18545875nfi.16.2008.01.23.11.34.58 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 23 Jan 2008 11:34:58 -0800 (PST) Message-ID: <479796E1.4000500@gmail.com> Date: Wed, 23 Jan 2008 20:34:57 +0100 From: Pawel Worach User-Agent: Thunderbird 2.0.0.9 (X11/20080119) MIME-Version: 1.0 To: Kostik Belousov References: <4792C32C.5010205@gmail.com> <20080122133835.GT57756@deviant.kiev.zoral.com.ua> <4796356D.9080809@gmail.com> <20080123051648.GV57756@deviant.kiev.zoral.com.ua> In-Reply-To: <20080123051648.GV57756@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , Joe Marcus Clarke Subject: Re: page fault panic in scioctl and console-kit-daemon X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 19:35:05 -0000 Kostik Belousov wrote: > On Tue, Jan 22, 2008 at 07:26:53PM +0100, Pawel Worach wrote: >> Kostik Belousov wrote: >>> On Sun, Jan 20, 2008 at 04:42:36AM +0100, Pawel Worach wrote: >>>> Hi, >>>> >>>> While starting console-kit-daemon (sysutils/consolekit 0.2.3) during >>>> boot or in single-user mode the system panics. If I start it post-boot >>>> it runs fine. This is on 8.0-CURRENT from about 12 hours ago, another >>>> user also reported the same on RELENG_7. Any other information I can >>>> provide ? >>>> >>>> Fatal trap 12: page fault while in kernel mode >>>> fault virtual address = 0x4 >>>> fault code = supervisor read, page not present >>>> instruction pointer = 0x20:0xc04d2ab4 >>>> stack pointer = 0x28:0xe6499b18 >>>> frame pointer = 0x28:0xe6499b80 >>>> 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 = 134 (console-kit-daemon) >>>> Physical memory: 1014 MB >>>> Dumping 43 MB: 28 12 >>>> >>>> #8 0xc07a34a2 in trap (frame=0xe6499ad8) at >>>> /usr/src/sys/i386/i386/trap.c:489 >>>> #9 0xc079183b in calltrap () at /usr/src/sys/i386/i386/exception.s:146 >>>> #10 0xc04d2ab4 in scioctl (dev=0xc3b20d00, cmd=537163270, >>>> data=0xe6499c70 "\002", flag=1, td=0xc3d3c880) >>>> at /usr/src/sys/dev/syscons/syscons.c:1073 >>>> #11 0xc051ed1a in giant_ioctl (dev=0xc3b20d00, cmd=537163270, >>>> data=0xe6499c70 "\002", fflag=1, td=0xc3d3c880) >>>> at /usr/src/sys/kern/kern_conf.c:349 >>>> #12 0xc0598194 in cnioctl (dev=0xc3b20d00, cmd=537163270, >>>> data=0xe6499c70 "\002", flag=1, td=0xc3d3c880) >>>> ---Type to continue, or q to quit--- >>>> at /usr/src/sys/kern/tty_cons.c:521 >>> Unless the virtual screen is opened, the screen state scr_stat structure >>> is not allocated. The following patch would fix the panic, but I do not >>> know how the console-kit would react to the ENXIO from the >>> VT_WAITACTIVE ioctl. Please, test it. >> Thanks! The patch works. > > To clarify: do you see any problems with the console-kit after the patch ? > In particular, can you verify that the program functions correctly, esp. > on the virtual terminals 1, 2 ... , whatever this means ? The panic is of course gone, while chatting a bit with Marcus (CCd) it looks like console-kit does not do any error handling at all. I've not looked at what c-k does so maybe Marcus can answer the question better. Regards -- Pawel From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 19:39:26 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5ECBF16A418 for ; Wed, 23 Jan 2008 19:39:26 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: from syn.atarininja.org (syn.csh.rit.edu [129.21.60.158]) by mx1.freebsd.org (Postfix) with ESMTP id 4583613C457 for ; Wed, 23 Jan 2008 19:39:26 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: by syn.atarininja.org (Postfix, from userid 1001) id DD8335C5A; Wed, 23 Jan 2008 14:40:46 -0500 (EST) Date: Wed, 23 Jan 2008 14:40:46 -0500 From: Wesley Shields To: "Aryeh M. Friedman" Message-ID: <20080123194046.GH60410@atarininja.org> References: <47979391.50006@gmail.com> <20080123193211.GG60410@atarininja.org> <479796C2.30106@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <479796C2.30106@gmail.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-current@freebsd.org Subject: Re: fetch fails on 8-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2008 19:39:26 -0000 On Wed, Jan 23, 2008 at 02:34:26PM -0500, Aryeh M. Friedman wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Wesley Shields wrote: > > On Wed, Jan 23, 2008 at 02:20:49PM -0500, Aryeh M. Friedman wrote: > >> flosoft# /usr/bin/fetch -s > >> ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ports/ports.tar.gz > > >> ports.size Segmentation fault (core dumped) > > > > I can't reproduce this... > > > > wxs@rst ~ % fetch -s > > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ports/ports.tar.gz > > > ports.size wxs@rst ~ % cat ports.size 39987735 wxs@rst ~ % uname -a > > FreeBSD rst.atarininja.org 8.0-CURRENT FreeBSD 8.0-CURRENT #3: Tue > > Dec 4 12:39:11 EST 2007 > > root@rst.atarininja.org:/usr/obj/usr/src/sys/GENERIC amd64 wxs@rst > > ~ % > > > > That is weird because: > > flosoft# fetch -s > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ports/ports.tar.gz > ports.size > Segmentation fault (core dumped) > flosoft# cat ports.size > flosoft# uname -a > FreeBSD flosoft.no-ip.biz 8.0-CURRENT FreeBSD 8.0-CURRENT #1: Tue Jan > 22 23:37:49 EST 2008 > aryeh@flosoft.no-ip.biz:/usr/obj/usr/src/sys/MONSTER amd64 > > The only difference in MONSTER vs. GENERIC is I added IPI_PREEMPTION > and removed the debugging options. I will go ahead and update to a more recent build and get back to you. -- WXS From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 19:56:00 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 11BE716A418 for ; Wed, 23 Jan 2008 19:56:00 +0000 (UTC) (envelope-from marcus@FreeBSD.org) Received: from creme-brulee.marcuscom.com (penna-pt.tunnel.tserv1.fmt.ipv6.he.net [IPv6:2001:470:1f00:ffff::1279]) by mx1.freebsd.org (Postfix) with ESMTP id C326413C448 for ; Wed, 23 Jan 2008 19:55:59 +0000 (UTC) (envelope-from marcus@FreeBSD.org) Received: from [IPv6:2001:470:1f00:2464::4] (shumai.marcuscom.com [IPv6:2001:470:1f00:2464::4]) by creme-brulee.marcuscom.com (8.14.2/8.14.2) with ESMTP id m0NJvtq3031485; Wed, 23 Jan 2008 14:57:55 -0500 (EST) (envelope-from marcus@FreeBSD.org) From: Joe Marcus Clarke To: Pawel Worach In-Reply-To: <479796E1.4000500@gmail.com> References: <4792C32C.5010205@gmail.com> <20080122133835.GT57756@deviant.kiev.zoral.com.ua> <4796356D.9080809@gmail.com> <20080123051648.GV57756@deviant.kiev.zoral.com.ua> <479796E1.4000500@gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-4WW6dkmWsaMshlBMmLkO" Organization: FreeBSD, Inc. Date: Wed, 23 Jan 2008 14:55:59 -0500 Message-Id: <1201118159.38742.17.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 FreeBSD GNOME Team Port X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on creme-brulee.marcuscom.com Cc: Kostik Belousov , FreeBSD Current Subject: Re: page fault panic in scioctl and console-kit-daemon X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 19:56:00 -0000 --=-4WW6dkmWsaMshlBMmLkO Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2008-01-23 at 20:34 +0100, Pawel Worach wrote: > Kostik Belousov wrote: > > On Tue, Jan 22, 2008 at 07:26:53PM +0100, Pawel Worach wrote: > >> Kostik Belousov wrote: > >>> On Sun, Jan 20, 2008 at 04:42:36AM +0100, Pawel Worach wrote: > >>>> Hi, > >>>> > >>>> While starting console-kit-daemon (sysutils/consolekit 0.2.3) during= =20 > >>>> boot or in single-user mode the system panics. If I start it post-bo= ot=20 > >>>> it runs fine. This is on 8.0-CURRENT from about 12 hours ago, anothe= r=20 > >>>> user also reported the same on RELENG_7. Any other information I can= =20 > >>>> provide ? > >>>> > >>>> Fatal trap 12: page fault while in kernel mode > >>>> fault virtual address =3D 0x4 > >>>> fault code =3D supervisor read, page not present > >>>> instruction pointer =3D 0x20:0xc04d2ab4 > >>>> stack pointer =3D 0x28:0xe6499b18 > >>>> frame pointer =3D 0x28:0xe6499b80 > >>>> code segment =3D base 0x0, limit 0xfffff, type 0x1b > >>>> =3D DPL 0, pres 1, def32 1, gran 1 > >>>> processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > >>>> current process =3D 134 (console-kit-daemon) > >>>> Physical memory: 1014 MB > >>>> Dumping 43 MB: 28 12 > >>>> > >>>> #8 0xc07a34a2 in trap (frame=3D0xe6499ad8) at=20 > >>>> /usr/src/sys/i386/i386/trap.c:489 > >>>> #9 0xc079183b in calltrap () at /usr/src/sys/i386/i386/exception.s:= 146 > >>>> #10 0xc04d2ab4 in scioctl (dev=3D0xc3b20d00, cmd=3D537163270, > >>>> data=3D0xe6499c70 "\002", flag=3D1, td=3D0xc3d3c880) > >>>> at /usr/src/sys/dev/syscons/syscons.c:1073 > >>>> #11 0xc051ed1a in giant_ioctl (dev=3D0xc3b20d00, cmd=3D537163270, > >>>> data=3D0xe6499c70 "\002", fflag=3D1, td=3D0xc3d3c880) > >>>> at /usr/src/sys/kern/kern_conf.c:349 > >>>> #12 0xc0598194 in cnioctl (dev=3D0xc3b20d00, cmd=3D537163270, > >>>> data=3D0xe6499c70 "\002", flag=3D1, td=3D0xc3d3c880) > >>>> ---Type to continue, or q to quit--- > >>>> at /usr/src/sys/kern/tty_cons.c:521 > >>> Unless the virtual screen is opened, the screen state scr_stat struct= ure > >>> is not allocated. The following patch would fix the panic, but I do n= ot > >>> know how the console-kit would react to the ENXIO from the > >>> VT_WAITACTIVE ioctl. Please, test it. > >> Thanks! The patch works. > >=20 > > To clarify: do you see any problems with the console-kit after the patc= h ? > > In particular, can you verify that the program functions correctly, esp= . > > on the virtual terminals 1, 2 ... , whatever this means ? >=20 > The panic is of course gone, while chatting a bit with Marcus (CCd) it=20 > looks like console-kit does not do any error handling at all. I've not=20 > looked at what c-k does so maybe Marcus can answer the question better. It tries to install a wait thread on each available VT. That thread sets the WAITACTIVE ioctl, and waits for its VT to become active. When it does, it sets the CK active VT accordingly, and reattaches the wait. When an error occurs in the ioctl, no wait is attached, and CK will not know when a particular VT becomes active. This will essentially cripple CK (assuming the VT really does become available at a later point). =20 Now, admittedly, there is no error correction in CK for this situation. It would be trivial to add something that periodically attempts to reestablish a failed wait. However, I am very curious why only a few users are seeing this panic (me excluded on two different machines). It seems to me that the scp should be initialized when sc_attach_unit() is called during device probing. I don't see anything special in init(8)'s code that would cause these VT devices to become initialized. I would assume that if one can open(2) them, then they should be available for ioctls? Joe --=20 Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome --=-4WW6dkmWsaMshlBMmLkO Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEABECAAYFAkeXm8sACgkQb2iPiv4Uz4dJjgCfUYrKyh3f0Z85HayeCIVqH+hU v9YAnjeb9cgDW7GR/4fS07tJ2Lm+0cKw =mD9u -----END PGP SIGNATURE----- --=-4WW6dkmWsaMshlBMmLkO-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 20:05:52 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85C9D16A474 for ; Wed, 23 Jan 2008 20:05:52 +0000 (UTC) (envelope-from gallatin@cs.duke.edu) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.freebsd.org (Postfix) with ESMTP id 3903413C4F7 for ; Wed, 23 Jan 2008 20:05:52 +0000 (UTC) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.14.0/8.14.0) with ESMTP id m0NK5pbr027335 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Jan 2008 15:05:51 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id m0NK5Nnq004553; Wed, 23 Jan 2008 15:05:23 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18327.40474.360956.331813@grasshopper.cs.duke.edu> Date: Wed, 23 Jan 2008 15:05:23 -0500 (EST) To: Alexander Kabaev In-Reply-To: <20080121124100.06f2ea93@kan.dnsalias.net> References: <933741.93778.qm@web33710.mail.mud.yahoo.com> <20080121124100.06f2ea93@kan.dnsalias.net> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Cc: FreeBSD CURRENT Subject: Re: LatencyTOP and FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 20:05:52 -0000 Alexander Kabaev writes: > Hope not. This kind of statistics should easily be done with DTrace. Indeed, see the thread at http://mail.opensolaris.org/pipermail/dtrace-discuss/2008-January/005439.html What is the status of Dtrace in FreeBSD? I thought the original port was permantly stalled due to licensing conflicts over CDDL, and that John was starting from scratch. Drew From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 20:48:45 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A529A16A419 for ; Wed, 23 Jan 2008 20:48:45 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 70BCD13C4D5 for ; Wed, 23 Jan 2008 20:48:45 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id A99C0208C; Wed, 23 Jan 2008 21:48:37 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 970F6208A; Wed, 23 Jan 2008 21:48:37 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id 89D08844B6; Wed, 23 Jan 2008 21:48:37 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "Aryeh M. Friedman" References: <47979391.50006@gmail.com> Date: Wed, 23 Jan 2008 21:48:37 +0100 In-Reply-To: <47979391.50006@gmail.com> (Aryeh M. Friedman's message of "Wed\, 23 Jan 2008 14\:20\:49 -0500") Message-ID: <86bq7cp8t6.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: fetch fails on 8-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2008 20:48:45 -0000 "Aryeh M. Friedman" writes: > flosoft# /usr/bin/fetch -s > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/ports/ports.tar.gz > ports.size > Segmentation fault (core dumped) bug in src/lib/libfetch/ftp.c rev 1.99, will fix DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 20:57:20 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2E6016A417 for ; Wed, 23 Jan 2008 20:57:20 +0000 (UTC) (envelope-from mezz7@cox.net) Received: from eastrmpop111.cox.net (eastrmpop111.cox.net [68.230.240.53]) by mx1.freebsd.org (Postfix) with ESMTP id 8C73113C45A for ; Wed, 23 Jan 2008 20:57:20 +0000 (UTC) (envelope-from mezz7@cox.net) Received: from eastrmimpo03.cox.net ([68.1.16.126]) by eastrmmtao105.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20080123202815.FJDD4251.eastrmmtao105.cox.net@eastrmimpo03.cox.net>; Wed, 23 Jan 2008 15:28:15 -0500 Received: from mezz.mezzweb.com ([24.255.149.218]) by eastrmimpo03.cox.net with bizsmtp id gkBv1Y0044iy4EG0000000; Wed, 23 Jan 2008 15:11:55 -0500 Date: Wed, 23 Jan 2008 14:29:02 -0600 To: "Andrew Gallatin" From: "Jeremy Messenger" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 References: <933741.93778.qm@web33710.mail.mud.yahoo.com> <20080121124100.06f2ea93@kan.dnsalias.net> <18327.40474.360956.331813@grasshopper.cs.duke.edu> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <18327.40474.360956.331813@grasshopper.cs.duke.edu> User-Agent: Opera Mail/9.25 (Linux) Cc: FreeBSD CURRENT Subject: Re: LatencyTOP and FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 20:57:21 -0000 On Wed, 23 Jan 2008 14:05:23 -0600, Andrew Gallatin wrote: > > Alexander Kabaev writes: > > Hope not. This kind of statistics should easily be done with DTrace. > > Indeed, see the thread at > http://mail.opensolaris.org/pipermail/dtrace-discuss/2008-January/005439.html > > What is the status of Dtrace in FreeBSD? I thought the original port > was permantly stalled due to licensing conflicts over CDDL, and > that John was starting from scratch. http://dtrace.what-creek.com/ (hasn't been update since Nov 2007) Honestly, I don't understand how CDDL can be conflict with BSD license since it's file based license rather than whole like GPL. Also, it doesn't force BSD license to be change to CDDL. Sun doesn't see any problem for FreeBSD to ship with it either. Feel free to explain more to me in private to avoid license war in this list. Cheers, Mezz > Drew -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src) http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org http://wiki.freebsd.org/multimedia - multimedia@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 21:06:12 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3433816A418 for ; Wed, 23 Jan 2008 21:06:12 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.152]) by mx1.freebsd.org (Postfix) with ESMTP id C241013C4E8 for ; Wed, 23 Jan 2008 21:06:11 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so2847419fgg.35 for ; Wed, 23 Jan 2008 13:06:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer:sender; bh=5AfCEvIr50Q0J9k3lRT+KAbBg6HawjXBSjwgzWbSeE8=; b=AGxFylw7M02OU8Of6qtfJGjQA2NUgEU5Hem22B5ZHChzyu4m+vc2P9Uvz8wxTQ/M2F4sBo5LauYws3sPwwqmy2rywJSM+unWCSWQuNkn5wu/k/tE3zNTZgXhFqd1XcXeifroVKMWKbPgXcv4sg9fXs89J03iv68SPCAWIg7TMaw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type:content-transfer-encoding:mime-version:subject:date:references:x-mailer:sender; b=EM79baoy1RizL2XxqtIkdMAyikNV/nRgi3LZPogfWbORiA8DXIpGRrtft7+GUdE2rFYqqSJKgi8wM+ry42kaOpsVtPzrrIw3DNjvdUvGTN56qyVRsxkSyQepcljUy/1efkhKh/UpqvkwJDFSvULTD8gaRExWjqgC8ONwoM74Z3I= Received: by 10.82.121.15 with SMTP id t15mr18027119buc.1.1201122369975; Wed, 23 Jan 2008 13:06:09 -0800 (PST) Received: from ?10.0.0.15? ( [83.144.140.64]) by mx.google.com with ESMTPS id f13sm9353682gvd.9.2008.01.23.13.06.05 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 23 Jan 2008 13:06:06 -0800 (PST) Message-Id: From: Rui Paulo To: pyunyh@gmail.com In-Reply-To: <20080122051604.GC10560@cdnetworks.co.kr> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Date: Wed, 23 Jan 2008 21:06:02 +0000 References: <20080122051604.GC10560@cdnetworks.co.kr> X-Mailer: Apple Mail (2.915) Sender: Rui Paulo Cc: freebsd-current@FreeBSD.org Subject: Re: CFT: re(4) WOL 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: Wed, 23 Jan 2008 21:06:12 -0000 On Jan 22, 2008, at 5:16 AM, Pyun YongHyeon wrote: > > Dear all, > > Attached patch enables WOL capability on re(4). Since there are too > many variants of hardwares that uses re(4), I'd like to hear > success/failure report of the patch prior to commit. You can wake > the system in suspend state as well as power down state. Because > suspend/resume does not work on my box I don't know whether waking > up from suspend work. WOL packets can be greated with tools like > ports/net/wol. > Patch was generated against HEAD and you should have latest CURRENT > to get WOL infrasture before running the patch. I have a re(4) and I'll try your patch in the next weekend/week. Regards. -- Rui Paulo From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 21:12:32 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 958CE16A41B; Wed, 23 Jan 2008 21:12:32 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from relay02.kiev.sovam.com (relay02.kiev.sovam.com [62.64.120.197]) by mx1.freebsd.org (Postfix) with ESMTP id 39FC513C46E; Wed, 23 Jan 2008 21:12:32 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from [212.82.216.226] (helo=skuns.kiev.zoral.com.ua) by relay02.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1JHmtN-000AnO-3D; Wed, 23 Jan 2008 23:12:30 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by skuns.kiev.zoral.com.ua (8.14.1/8.14.1) with ESMTP id m0NLBXqX079960 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Jan 2008 23:11:33 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m0NLBoWe025201; Wed, 23 Jan 2008 23:11:50 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2/Submit) id m0NLBnSQ025200; Wed, 23 Jan 2008 23:11:49 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 23 Jan 2008 23:11:49 +0200 From: Kostik Belousov To: Joe Marcus Clarke Message-ID: <20080123211149.GA57756@deviant.kiev.zoral.com.ua> References: <4792C32C.5010205@gmail.com> <20080122133835.GT57756@deviant.kiev.zoral.com.ua> <4796356D.9080809@gmail.com> <20080123051648.GV57756@deviant.kiev.zoral.com.ua> <479796E1.4000500@gmail.com> <1201118159.38742.17.camel@shumai.marcuscom.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gwHyQuq5wHWsurqv" Content-Disposition: inline In-Reply-To: <1201118159.38742.17.camel@shumai.marcuscom.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Scanner-Signature: 5705bde2e570895834f5a69800e19fe2 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 2039 [Jan 23 2008] X-SpamTest-Info: helo_type=3 X-SpamTest-Info: {received from trusted relay: not dialup} X-SpamTest-Method: none X-SpamTest-Method: Local Lists X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0255], KAS30/Release Cc: FreeBSD Current Subject: Re: page fault panic in scioctl and console-kit-daemon X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 21:12:32 -0000 --gwHyQuq5wHWsurqv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 23, 2008 at 02:55:59PM -0500, Joe Marcus Clarke wrote: >=20 > On Wed, 2008-01-23 at 20:34 +0100, Pawel Worach wrote: > > Kostik Belousov wrote: > > > On Tue, Jan 22, 2008 at 07:26:53PM +0100, Pawel Worach wrote: > > >> Kostik Belousov wrote: > > >>> On Sun, Jan 20, 2008 at 04:42:36AM +0100, Pawel Worach wrote: > > >>>> Hi, > > >>>> > > >>>> While starting console-kit-daemon (sysutils/consolekit 0.2.3) duri= ng=20 > > >>>> boot or in single-user mode the system panics. If I start it post-= boot=20 > > >>>> it runs fine. This is on 8.0-CURRENT from about 12 hours ago, anot= her=20 > > >>>> user also reported the same on RELENG_7. Any other information I c= an=20 > > >>>> provide ? > > >>>> > > >>>> Fatal trap 12: page fault while in kernel mode > > >>>> fault virtual address =3D 0x4 > > >>>> fault code =3D supervisor read, page not present > > >>>> instruction pointer =3D 0x20:0xc04d2ab4 > > >>>> stack pointer =3D 0x28:0xe6499b18 > > >>>> frame pointer =3D 0x28:0xe6499b80 > > >>>> code segment =3D base 0x0, limit 0xfffff, type 0x1b > > >>>> =3D DPL 0, pres 1, def32 1, gran 1 > > >>>> processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > > >>>> current process =3D 134 (console-kit-daemon) > > >>>> Physical memory: 1014 MB > > >>>> Dumping 43 MB: 28 12 > > >>>> > > >>>> #8 0xc07a34a2 in trap (frame=3D0xe6499ad8) at=20 > > >>>> /usr/src/sys/i386/i386/trap.c:489 > > >>>> #9 0xc079183b in calltrap () at /usr/src/sys/i386/i386/exception.= s:146 > > >>>> #10 0xc04d2ab4 in scioctl (dev=3D0xc3b20d00, cmd=3D537163270, > > >>>> data=3D0xe6499c70 "\002", flag=3D1, td=3D0xc3d3c880) > > >>>> at /usr/src/sys/dev/syscons/syscons.c:1073 > > >>>> #11 0xc051ed1a in giant_ioctl (dev=3D0xc3b20d00, cmd=3D537163270, > > >>>> data=3D0xe6499c70 "\002", fflag=3D1, td=3D0xc3d3c880) > > >>>> at /usr/src/sys/kern/kern_conf.c:349 > > >>>> #12 0xc0598194 in cnioctl (dev=3D0xc3b20d00, cmd=3D537163270, > > >>>> data=3D0xe6499c70 "\002", flag=3D1, td=3D0xc3d3c880) > > >>>> ---Type to continue, or q to quit--- > > >>>> at /usr/src/sys/kern/tty_cons.c:521 > > >>> Unless the virtual screen is opened, the screen state scr_stat stru= cture > > >>> is not allocated. The following patch would fix the panic, but I do= not > > >>> know how the console-kit would react to the ENXIO from the > > >>> VT_WAITACTIVE ioctl. Please, test it. > > >> Thanks! The patch works. > > >=20 > > > To clarify: do you see any problems with the console-kit after the pa= tch ? > > > In particular, can you verify that the program functions correctly, e= sp. > > > on the virtual terminals 1, 2 ... , whatever this means ? > >=20 > > The panic is of course gone, while chatting a bit with Marcus (CCd) it= =20 > > looks like console-kit does not do any error handling at all. I've not= =20 > > looked at what c-k does so maybe Marcus can answer the question better. >=20 > It tries to install a wait thread on each available VT. That thread > sets the WAITACTIVE ioctl, and waits for its VT to become active. When > it does, it sets the CK active VT accordingly, and reattaches the wait. >=20 > When an error occurs in the ioctl, no wait is attached, and CK will not > know when a particular VT becomes active. This will essentially cripple > CK (assuming the VT really does become available at a later point). =20 >=20 > Now, admittedly, there is no error correction in CK for this situation. > It would be trivial to add something that periodically attempts to > reestablish a failed wait. However, I am very curious why only a few > users are seeing this panic (me excluded on two different machines). It > seems to me that the scp should be initialized when sc_attach_unit() is > called during device probing. I don't see anything special in init(8)'s > code that would cause these VT devices to become initialized. I would > assume that if one can open(2) them, then they should be available for > ioctls? =46rom my reading of the code, scp would be non-NULL after the first open of the corresponding /dev/ttyvX. sc_attach_unit() creates the scp for the console and the consolectl devices. VT_WAITACTIVE ioctl is performed on arbitrary syscons /dev node, and can wait for any other screens, in particular, the screens that are not opened at the moment (the reason for the reported panic). The patch I posted may be improved by making the VT_WAITACTIVE ioctl to wait for the scp being allocated, and only then for the screen to be switched too. Please, test. diff --git a/sys/dev/syscons/syscons.c b/sys/dev/syscons/syscons.c index e0c9725..3127ae6 100644 --- a/sys/dev/syscons/syscons.c +++ b/sys/dev/syscons/syscons.c @@ -178,6 +178,7 @@ static int scparam(struct tty *tp, struct termios *t); static void scstart(struct tty *tp); static void scinit(int unit, int flags); static scr_stat *sc_get_stat(struct cdev *devptr); +static void sc_set_stat(struct cdev *devptr, scr_stat *st); static void scterm(int unit, int flags); static void scshutdown(void *arg, int howto); static u_int scgetc(sc_softc_t *sc, u_int flags); @@ -421,7 +422,7 @@ sc_attach_unit(int unit, int flags) UID_ROOT, GID_WHEEL, 0600, "ttyv%r", vc + unit * MAXCONS); sc_alloc_tty(sc->dev[vc]); if (vc =3D=3D 0 && sc->dev =3D=3D main_devs) - SC_STAT(sc->dev[0]) =3D &main_console; + sc_set_stat(sc->dev[0], &main_console); } /* * The first vty already has struct tty and scr_stat initialized @@ -434,7 +435,7 @@ sc_attach_unit(int unit, int flags) UID_ROOT, GID_WHEEL, 0600, "consolectl"); sc_console_tty =3D sc_alloc_tty(dev); ttyconsolemode(sc_console_tty, 0); - SC_STAT(dev) =3D sc_console; + sc_set_stat(dev, sc_console); =20 return 0; } @@ -525,7 +526,8 @@ scopen(struct cdev *dev, int flag, int mode, struct thr= ead *td) =20 scp =3D sc_get_stat(dev); if (scp =3D=3D NULL) { - scp =3D SC_STAT(dev) =3D alloc_scp(sc, SC_VTY(dev)); + scp =3D alloc_scp(sc, SC_VTY(dev)); + sc_set_stat(dev, scp); if (ISGRAPHSC(scp)) sc_set_pixel_mode(scp, NULL, COL, ROW, 16, 8); } @@ -1063,6 +1065,7 @@ scioctl(struct cdev *dev, u_long cmd, caddr_t data, i= nt flag, struct thread *td) #endif case VT_WAITACTIVE: /* wait for switch to occur */ i =3D (*(int *)data =3D=3D 0) ? scp->index : (*(int *)data - 1); + wait_active: if ((i < sc->first_vty) || (i >=3D sc->first_vty + sc->vtys)) return EINVAL; s =3D spltty(); @@ -1071,6 +1074,12 @@ scioctl(struct cdev *dev, u_long cmd, caddr_t data, = int flag, struct thread *td) if (error) return error; scp =3D sc_get_stat(SC_DEV(sc, i)); + if (scp =3D=3D NULL) { + error =3D tsleep(&(dev)->si_drv1, PZERO | PCATCH, "waitvt0", 0); + if (error) + return (error); + goto wait_active; + } if (scp =3D=3D scp->sc->cur_scp) return 0; error =3D tsleep(&scp->smode, PZERO | PCATCH, "waitvt", 0); @@ -2769,7 +2778,7 @@ scinit(int unit, int flags) UID_ROOT, GID_WHEEL, 0600, "ttyv%r", unit * MAXCONS); sc_alloc_tty(sc->dev[0]); scp =3D alloc_scp(sc, sc->first_vty); - SC_STAT(sc->dev[0]) =3D scp; + sc_set_stat(sc->dev[0], scp); } sc->cur_scp =3D scp; =20 @@ -3662,6 +3671,14 @@ sc_get_stat(struct cdev *devptr) return (SC_STAT(devptr)); } =20 +static void +sc_set_stat(struct cdev *devptr, scr_stat *st) +{ + + SC_STAT(devptr) =3D st; + wakeup(&devptr->si_drv1); +} + /* * Allocate active keyboard. Try to allocate "kbdmux" keyboard first, and, * if found, add all non-busy keyboards to "kbdmux". Otherwise look for --gwHyQuq5wHWsurqv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEARECAAYFAkeXrZMACgkQC3+MBN1Mb4gkGgCdEr2DgrZH8fYECBw74bj+G968 QQUAoMQ0rxMBzMIFndRzY/k0HV8RndD6 =8n5X -----END PGP SIGNATURE----- --gwHyQuq5wHWsurqv-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 21:32:14 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04E3716A420 for ; Wed, 23 Jan 2008 21:32:14 +0000 (UTC) (envelope-from marcus@FreeBSD.org) Received: from creme-brulee.marcuscom.com (marcuscom-pt.tunnel.tserv1.fmt.ipv6.he.net [IPv6:2001:470:1f00:ffff::1279]) by mx1.freebsd.org (Postfix) with ESMTP id A679213C44B for ; Wed, 23 Jan 2008 21:32:13 +0000 (UTC) (envelope-from marcus@FreeBSD.org) Received: from [IPv6:2001:470:1f00:2464::4] (shumai.marcuscom.com [IPv6:2001:470:1f00:2464::4]) by creme-brulee.marcuscom.com (8.14.2/8.14.2) with ESMTP id m0NLY9d1033110; Wed, 23 Jan 2008 16:34:09 -0500 (EST) (envelope-from marcus@FreeBSD.org) From: Joe Marcus Clarke To: Kostik Belousov In-Reply-To: <20080123211149.GA57756@deviant.kiev.zoral.com.ua> References: <4792C32C.5010205@gmail.com> <20080122133835.GT57756@deviant.kiev.zoral.com.ua> <4796356D.9080809@gmail.com> <20080123051648.GV57756@deviant.kiev.zoral.com.ua> <479796E1.4000500@gmail.com> <1201118159.38742.17.camel@shumai.marcuscom.com> <20080123211149.GA57756@deviant.kiev.zoral.com.ua> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Z1ETJrIctgY+OPXYJmYw" Organization: FreeBSD, Inc. Date: Wed, 23 Jan 2008 16:32:13 -0500 Message-Id: <1201123933.62127.9.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 FreeBSD GNOME Team Port X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on creme-brulee.marcuscom.com Cc: FreeBSD Current Subject: Re: page fault panic in scioctl and console-kit-daemon X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 21:32:14 -0000 --=-Z1ETJrIctgY+OPXYJmYw Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2008-01-23 at 23:11 +0200, Kostik Belousov wrote: > On Wed, Jan 23, 2008 at 02:55:59PM -0500, Joe Marcus Clarke wrote: > >=20 > > On Wed, 2008-01-23 at 20:34 +0100, Pawel Worach wrote: > > > Kostik Belousov wrote: > > > > On Tue, Jan 22, 2008 at 07:26:53PM +0100, Pawel Worach wrote: > > > >> Kostik Belousov wrote: > > > >>> On Sun, Jan 20, 2008 at 04:42:36AM +0100, Pawel Worach wrote: > > > >>>> Hi, > > > >>>> > > > >>>> While starting console-kit-daemon (sysutils/consolekit 0.2.3) du= ring=20 > > > >>>> boot or in single-user mode the system panics. If I start it pos= t-boot=20 > > > >>>> it runs fine. This is on 8.0-CURRENT from about 12 hours ago, an= other=20 > > > >>>> user also reported the same on RELENG_7. Any other information I= can=20 > > > >>>> provide ? > > > >>>> > > > >>>> Fatal trap 12: page fault while in kernel mode > > > >>>> fault virtual address =3D 0x4 > > > >>>> fault code =3D supervisor read, page not present > > > >>>> instruction pointer =3D 0x20:0xc04d2ab4 > > > >>>> stack pointer =3D 0x28:0xe6499b18 > > > >>>> frame pointer =3D 0x28:0xe6499b80 > > > >>>> code segment =3D base 0x0, limit 0xfffff, type 0x1b > > > >>>> =3D DPL 0, pres 1, def32 1, gran 1 > > > >>>> processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > > > >>>> current process =3D 134 (console-kit-daemon) > > > >>>> Physical memory: 1014 MB > > > >>>> Dumping 43 MB: 28 12 > > > >>>> > > > >>>> #8 0xc07a34a2 in trap (frame=3D0xe6499ad8) at=20 > > > >>>> /usr/src/sys/i386/i386/trap.c:489 > > > >>>> #9 0xc079183b in calltrap () at /usr/src/sys/i386/i386/exceptio= n.s:146 > > > >>>> #10 0xc04d2ab4 in scioctl (dev=3D0xc3b20d00, cmd=3D537163270, > > > >>>> data=3D0xe6499c70 "\002", flag=3D1, td=3D0xc3d3c880) > > > >>>> at /usr/src/sys/dev/syscons/syscons.c:1073 > > > >>>> #11 0xc051ed1a in giant_ioctl (dev=3D0xc3b20d00, cmd=3D537163270= , > > > >>>> data=3D0xe6499c70 "\002", fflag=3D1, td=3D0xc3d3c880) > > > >>>> at /usr/src/sys/kern/kern_conf.c:349 > > > >>>> #12 0xc0598194 in cnioctl (dev=3D0xc3b20d00, cmd=3D537163270, > > > >>>> data=3D0xe6499c70 "\002", flag=3D1, td=3D0xc3d3c880) > > > >>>> ---Type to continue, or q to quit--- > > > >>>> at /usr/src/sys/kern/tty_cons.c:521 > > > >>> Unless the virtual screen is opened, the screen state scr_stat st= ructure > > > >>> is not allocated. The following patch would fix the panic, but I = do not > > > >>> know how the console-kit would react to the ENXIO from the > > > >>> VT_WAITACTIVE ioctl. Please, test it. > > > >> Thanks! The patch works. > > > >=20 > > > > To clarify: do you see any problems with the console-kit after the = patch ? > > > > In particular, can you verify that the program functions correctly,= esp. > > > > on the virtual terminals 1, 2 ... , whatever this means ? > > >=20 > > > The panic is of course gone, while chatting a bit with Marcus (CCd) i= t=20 > > > looks like console-kit does not do any error handling at all. I've no= t=20 > > > looked at what c-k does so maybe Marcus can answer the question bette= r. > >=20 > > It tries to install a wait thread on each available VT. That thread > > sets the WAITACTIVE ioctl, and waits for its VT to become active. When > > it does, it sets the CK active VT accordingly, and reattaches the wait. > >=20 > > When an error occurs in the ioctl, no wait is attached, and CK will not > > know when a particular VT becomes active. This will essentially crippl= e > > CK (assuming the VT really does become available at a later point). =20 > >=20 > > Now, admittedly, there is no error correction in CK for this situation. > > It would be trivial to add something that periodically attempts to > > reestablish a failed wait. However, I am very curious why only a few > > users are seeing this panic (me excluded on two different machines). I= t > > seems to me that the scp should be initialized when sc_attach_unit() is > > called during device probing. I don't see anything special in init(8)'= s > > code that would cause these VT devices to become initialized. I would > > assume that if one can open(2) them, then they should be available for > > ioctls? >=20 > From my reading of the code, scp would be non-NULL after the first open > of the corresponding /dev/ttyvX. sc_attach_unit() creates the scp for > the console and the consolectl devices. >=20 > VT_WAITACTIVE ioctl is performed on arbitrary syscons /dev node, and > can wait for any other screens, in particular, the screens that are > not opened at the moment (the reason for the reported panic). Right, and this is where I was confused. I had thought from an old reading of the CK code that CK opened each ttyvX device to perform the ioctl. It does not. Instead, it opens /dev/console, and performs the ioctl for each ttyvX on that fd. That does explain the panic, but not exactly why I did not see it. I'm guessing a race condition, but I can't be sure. >=20 > The patch I posted may be improved by making the VT_WAITACTIVE ioctl > to wait for the scp being allocated, and only then for the screen to be > switched too. Please, test. I really appreciate your attention to this. Funny thing is, CK 0.2.4 was just released, and it is no longer started out of rc.d. I've also added error correcting in the CK code path. The problem may disappear depending on when CK is executed out of D-BUS. However, it would be good to prevent this in the kernel. Pawel said he would try and test this patch. Joe >=20 >=20 > diff --git a/sys/dev/syscons/syscons.c b/sys/dev/syscons/syscons.c > index e0c9725..3127ae6 100644 > --- a/sys/dev/syscons/syscons.c > +++ b/sys/dev/syscons/syscons.c > @@ -178,6 +178,7 @@ static int scparam(struct tty *tp, struct termios *t)= ; > static void scstart(struct tty *tp); > static void scinit(int unit, int flags); > static scr_stat *sc_get_stat(struct cdev *devptr); > +static void sc_set_stat(struct cdev *devptr, scr_stat *st); > static void scterm(int unit, int flags); > static void scshutdown(void *arg, int howto); > static u_int scgetc(sc_softc_t *sc, u_int flags); > @@ -421,7 +422,7 @@ sc_attach_unit(int unit, int flags) > UID_ROOT, GID_WHEEL, 0600, "ttyv%r", vc + unit * MAXCONS); > sc_alloc_tty(sc->dev[vc]); > if (vc =3D=3D 0 && sc->dev =3D=3D main_devs) > - SC_STAT(sc->dev[0]) =3D &main_console; > + sc_set_stat(sc->dev[0], &main_console); > } > /* > * The first vty already has struct tty and scr_stat initialized > @@ -434,7 +435,7 @@ sc_attach_unit(int unit, int flags) > UID_ROOT, GID_WHEEL, 0600, "consolectl"); > sc_console_tty =3D sc_alloc_tty(dev); > ttyconsolemode(sc_console_tty, 0); > - SC_STAT(dev) =3D sc_console; > + sc_set_stat(dev, sc_console); > =20 > return 0; > } > @@ -525,7 +526,8 @@ scopen(struct cdev *dev, int flag, int mode, struct t= hread *td) > =20 > scp =3D sc_get_stat(dev); > if (scp =3D=3D NULL) { > - scp =3D SC_STAT(dev) =3D alloc_scp(sc, SC_VTY(dev)); > + scp =3D alloc_scp(sc, SC_VTY(dev)); > + sc_set_stat(dev, scp); > if (ISGRAPHSC(scp)) > sc_set_pixel_mode(scp, NULL, COL, ROW, 16, 8); > } > @@ -1063,6 +1065,7 @@ scioctl(struct cdev *dev, u_long cmd, caddr_t data,= int flag, struct thread *td) > #endif > case VT_WAITACTIVE: /* wait for switch to occur */ > i =3D (*(int *)data =3D=3D 0) ? scp->index : (*(int *)data - 1); > + wait_active: > if ((i < sc->first_vty) || (i >=3D sc->first_vty + sc->vtys)) > return EINVAL; > s =3D spltty(); > @@ -1071,6 +1074,12 @@ scioctl(struct cdev *dev, u_long cmd, caddr_t data= , int flag, struct thread *td) > if (error) > return error; > scp =3D sc_get_stat(SC_DEV(sc, i)); > + if (scp =3D=3D NULL) { > + error =3D tsleep(&(dev)->si_drv1, PZERO | PCATCH, "waitvt0", 0); > + if (error) > + return (error); > + goto wait_active; > + } > if (scp =3D=3D scp->sc->cur_scp) > return 0; > error =3D tsleep(&scp->smode, PZERO | PCATCH, "waitvt", 0); > @@ -2769,7 +2778,7 @@ scinit(int unit, int flags) > UID_ROOT, GID_WHEEL, 0600, "ttyv%r", unit * MAXCONS); > sc_alloc_tty(sc->dev[0]); > scp =3D alloc_scp(sc, sc->first_vty); > - SC_STAT(sc->dev[0]) =3D scp; > + sc_set_stat(sc->dev[0], scp); > } > sc->cur_scp =3D scp; > =20 > @@ -3662,6 +3671,14 @@ sc_get_stat(struct cdev *devptr) > return (SC_STAT(devptr)); > } > =20 > +static void > +sc_set_stat(struct cdev *devptr, scr_stat *st) > +{ > + > + SC_STAT(devptr) =3D st; > + wakeup(&devptr->si_drv1); > +} > + > /* > * Allocate active keyboard. Try to allocate "kbdmux" keyboard first, an= d, > * if found, add all non-busy keyboards to "kbdmux". Otherwise look for --=20 Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome --=-Z1ETJrIctgY+OPXYJmYw Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEABECAAYFAkeXslwACgkQb2iPiv4Uz4ffdACggJYhSUh9iqbji3xQQKIdeEbn vP8An2UaxZ8hcv/T+LEyRJEwHNvQchtR =bnFd -----END PGP SIGNATURE----- --=-Z1ETJrIctgY+OPXYJmYw-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 21:35:15 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7200716A46D for ; Wed, 23 Jan 2008 21:35:15 +0000 (UTC) (envelope-from pawel.worach@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.189]) by mx1.freebsd.org (Postfix) with ESMTP id DAA8113C4D1 for ; Wed, 23 Jan 2008 21:35:14 +0000 (UTC) (envelope-from pawel.worach@gmail.com) Received: by mu-out-0910.google.com with SMTP id w9so2364420mue.6 for ; Wed, 23 Jan 2008 13:35:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=N2wsKKaY5p3OooUs7N1VkCAIYQbh1RArcM7zwqk8Qjc=; b=gOahn3DfDYDqYF9UtINqSIY5pDUrKVGQ2HnO/2p8IK1/8wlaf5/23Rf8u1ZgC23QUSlGYrkEJxLMdnURltXysznA3x/3m+IUTSwUtalmVmncRxVdlbCCpV26QhCXYu0bqdDZm0WXOPL9X4YJO62HBkMAmAaW5jkCjyoi+hFZTos= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=NHCMtG25JIAAI7KRH9yDNjUV9WLUiNIOhHfPLADC5ULJmciyBY8XDnSEF2WZtawGkAp/NmywRdzPTwZITNNwEvHwkDnewgTeK16Gw1y65KTXuzeBDRVZ8c+dDai5789TZoXMNAcbriukizx1zCx2yjqe1EXWj7vLN7NuFK1eW5g= Received: by 10.78.81.20 with SMTP id e20mr14171144hub.60.1201124111421; Wed, 23 Jan 2008 13:35:11 -0800 (PST) Received: from ?192.168.10.200? ( [90.227.56.82]) by mx.google.com with ESMTPS id 33sm18733959nfu.9.2008.01.23.13.35.10 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 23 Jan 2008 13:35:10 -0800 (PST) Message-ID: <4797B307.8010701@gmail.com> Date: Wed, 23 Jan 2008 22:35:03 +0100 From: Pawel Worach User-Agent: Thunderbird 2.0.0.9 (X11/20080119) MIME-Version: 1.0 To: Kostik Belousov References: <4792C32C.5010205@gmail.com> <20080122133835.GT57756@deviant.kiev.zoral.com.ua> <4796356D.9080809@gmail.com> <20080123051648.GV57756@deviant.kiev.zoral.com.ua> <479796E1.4000500@gmail.com> <1201118159.38742.17.camel@shumai.marcuscom.com> <20080123211149.GA57756@deviant.kiev.zoral.com.ua> In-Reply-To: <20080123211149.GA57756@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , Joe Marcus Clarke Subject: Re: page fault panic in scioctl and console-kit-daemon X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 21:35:15 -0000 Kostik Belousov wrote: > On Wed, Jan 23, 2008 at 02:55:59PM -0500, Joe Marcus Clarke wrote: >> On Wed, 2008-01-23 at 20:34 +0100, Pawel Worach wrote: >>> Kostik Belousov wrote: >>>> On Tue, Jan 22, 2008 at 07:26:53PM +0100, Pawel Worach wrote: >>>>> Kostik Belousov wrote: >>>>>> On Sun, Jan 20, 2008 at 04:42:36AM +0100, Pawel Worach wrote: >>>>>>> Hi, >>>>>>> >>>>>>> While starting console-kit-daemon (sysutils/consolekit 0.2.3) during >>>>>>> boot or in single-user mode the system panics. If I start it post-boot >>>>>>> it runs fine. This is on 8.0-CURRENT from about 12 hours ago, another >>>>>>> user also reported the same on RELENG_7. Any other information I can >>>>>>> provide ? >>>>>>> >>>>>>> Fatal trap 12: page fault while in kernel mode >>>>>>> fault virtual address = 0x4 >>>>>>> fault code = supervisor read, page not present >>>>>>> instruction pointer = 0x20:0xc04d2ab4 >>>>>>> stack pointer = 0x28:0xe6499b18 >>>>>>> frame pointer = 0x28:0xe6499b80 >>>>>>> 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 = 134 (console-kit-daemon) >>>>>>> Physical memory: 1014 MB >>>>>>> Dumping 43 MB: 28 12 >>>>>>> >>>>>>> #8 0xc07a34a2 in trap (frame=0xe6499ad8) at >>>>>>> /usr/src/sys/i386/i386/trap.c:489 >>>>>>> #9 0xc079183b in calltrap () at /usr/src/sys/i386/i386/exception.s:146 >>>>>>> #10 0xc04d2ab4 in scioctl (dev=0xc3b20d00, cmd=537163270, >>>>>>> data=0xe6499c70 "\002", flag=1, td=0xc3d3c880) >>>>>>> at /usr/src/sys/dev/syscons/syscons.c:1073 >>>>>>> #11 0xc051ed1a in giant_ioctl (dev=0xc3b20d00, cmd=537163270, >>>>>>> data=0xe6499c70 "\002", fflag=1, td=0xc3d3c880) >>>>>>> at /usr/src/sys/kern/kern_conf.c:349 >>>>>>> #12 0xc0598194 in cnioctl (dev=0xc3b20d00, cmd=537163270, >>>>>>> data=0xe6499c70 "\002", flag=1, td=0xc3d3c880) >>>>>>> ---Type to continue, or q to quit--- >>>>>>> at /usr/src/sys/kern/tty_cons.c:521 >>>>>> Unless the virtual screen is opened, the screen state scr_stat structure >>>>>> is not allocated. The following patch would fix the panic, but I do not >>>>>> know how the console-kit would react to the ENXIO from the >>>>>> VT_WAITACTIVE ioctl. Please, test it. >>>>> Thanks! The patch works. >>>> To clarify: do you see any problems with the console-kit after the patch ? >>>> In particular, can you verify that the program functions correctly, esp. >>>> on the virtual terminals 1, 2 ... , whatever this means ? >>> The panic is of course gone, while chatting a bit with Marcus (CCd) it >>> looks like console-kit does not do any error handling at all. I've not >>> looked at what c-k does so maybe Marcus can answer the question better. >> It tries to install a wait thread on each available VT. That thread >> sets the WAITACTIVE ioctl, and waits for its VT to become active. When >> it does, it sets the CK active VT accordingly, and reattaches the wait. >> >> When an error occurs in the ioctl, no wait is attached, and CK will not >> know when a particular VT becomes active. This will essentially cripple >> CK (assuming the VT really does become available at a later point). >> >> Now, admittedly, there is no error correction in CK for this situation. >> It would be trivial to add something that periodically attempts to >> reestablish a failed wait. However, I am very curious why only a few >> users are seeing this panic (me excluded on two different machines). It >> seems to me that the scp should be initialized when sc_attach_unit() is >> called during device probing. I don't see anything special in init(8)'s >> code that would cause these VT devices to become initialized. I would >> assume that if one can open(2) them, then they should be available for >> ioctls? > > From my reading of the code, scp would be non-NULL after the first open > of the corresponding /dev/ttyvX. sc_attach_unit() creates the scp for > the console and the consolectl devices. > > VT_WAITACTIVE ioctl is performed on arbitrary syscons /dev node, and > can wait for any other screens, in particular, the screens that are > not opened at the moment (the reason for the reported panic). > > The patch I posted may be improved by making the VT_WAITACTIVE ioctl > to wait for the scp being allocated, and only then for the screen to be > switched too. Please, test. > > This patch also seems to work from the no-panic point of view. -- Pawel From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 22:27:11 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 232DD16A421 for ; Wed, 23 Jan 2008 22:27:11 +0000 (UTC) (envelope-from echobinary@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.237]) by mx1.freebsd.org (Postfix) with ESMTP id E2F7613C442 for ; Wed, 23 Jan 2008 22:27:10 +0000 (UTC) (envelope-from echobinary@gmail.com) Received: by nz-out-0506.google.com with SMTP id l8so1818018nzf.13 for ; Wed, 23 Jan 2008 14:27:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; bh=K6CY/N9KB60Mq01OuJnR5vX4gyDL8Oa8tcUKGbIh++U=; b=M+8JDEOKf2rl7nqNxqYGvgJ3Lc/SQN1yKS5yzXEEkbJH+Ft9rZ2NTgZNLCW3zo5tpAM7e4WA9Rl3SIUburZSMyfWLdwu6fFxxDhvy6cWsA6YnW1TZXD2wA6tDac5s8b5QVfbQWIzU1KHv0JP4WwZLrBYm5+ZUazyVnexAyqOhtQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=A8nN6KdoCMAt8+yyhSR5Wg7BurBLyKDDk7IUsaIE9IDWgIIVZRry2OwFalFRkXlvYxg5yH5QzB9bftJmW9Sesg530BFbfe0cyzPABf9md/PN8jsycuUepLoDBR4QtUg5pBhKDDmEKz9+APmZDH5Oh2bdhlUUeD8rOAKP/nOlsVg= Received: by 10.142.239.11 with SMTP id m11mr5352087wfh.76.1201125664922; Wed, 23 Jan 2008 14:01:04 -0800 (PST) Received: from ?192.168.1.108? ( [67.100.158.34]) by mx.google.com with ESMTPS id o34sm6139995rog.19.2008.01.23.14.01.03 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 23 Jan 2008 14:01:04 -0800 (PST) Message-ID: <4797B923.6030400@gmail.com> Date: Wed, 23 Jan 2008 17:01:07 -0500 From: EchoB User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: XEN and ZFS Status? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 22:27:11 -0000 Hi all :) Can anyone point me in the direction of any detailed docs or perhaps just an answer on here re: production status of Xen and ZFS when 7.0 is released? I have read somewhere that ZFS is experimental at best, and wanted to confirm that. Also, using Xen would be a great plus in a production environment. Also - read somewhere about 8.0-Current - whats that all about? what are the differences between 7.0 and 8.0? Ciao! From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 22:30:23 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDF2116A49E for ; Wed, 23 Jan 2008 22:30:23 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.178]) by mx1.freebsd.org (Postfix) with ESMTP id C15B913C46A for ; Wed, 23 Jan 2008 22:30:23 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so5291870waf.3 for ; Wed, 23 Jan 2008 14:30:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=5z5wSSHwwqWwDxCJuFpDBF5itEB2uBazvsEsjCtx0WU=; b=LDlGOyatBpVFC8dYzLI76bBsooRRtLomChY/gSeEyHIgmy4NAPDWCn8BbVVfSyRUnaHxY6fmspO8rxi6DrhVhcKDYut0xdpVbNnPWigtv1VzhRTzRfSDExnSundUW6G2FQmBiAlEctY2cAMaQbQsFOmvHibd9XVNAHHi2KbtRFk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=cSuKQJrk5TFBw+puRPUgHunO5sVwU0G3jPBMTi7jHMLmH6UZZE3Pr+GPMDRUpL2gT45bXgLpzZcGfw3p5Yy3x6JikycBp34ieNTwLGOeYOIBk8KHOdmv+ZY6FMZ06s9wVvbH+PCDyIkUf8xhpE2zZ5lPTmiEzQBZNfcfCPoTH8Y= Received: by 10.114.167.2 with SMTP id p2mr8585717wae.78.1201127423202; Wed, 23 Jan 2008 14:30:23 -0800 (PST) Received: by 10.114.255.16 with HTTP; Wed, 23 Jan 2008 14:30:23 -0800 (PST) Message-ID: Date: Wed, 23 Jan 2008 14:30:23 -0800 From: "Kip Macy" To: EchoB In-Reply-To: <4797B923.6030400@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4797B923.6030400@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: XEN and ZFS Status? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 22:30:24 -0000 WRT Xen: http://wiki.freebsd.org/FreeBSD/Xen Check there for other topics as well. On Jan 23, 2008 2:01 PM, EchoB wrote: > Hi all :) Can anyone point me in the direction of any detailed docs or > perhaps just an answer on here re: production status of Xen and ZFS when > 7.0 is released? I have read somewhere that ZFS is experimental at best, > and wanted to confirm that. Also, using Xen would be a great plus in a > production environment. > > Also - read somewhere about 8.0-Current - whats that all about? what > are the differences between 7.0 and 8.0? > Ciao! > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 22:31:04 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9CE3E16A418 for ; Wed, 23 Jan 2008 22:31:03 +0000 (UTC) (envelope-from dds@FreeBSD.org) Received: from mx-out-05.forthnet.gr (mx-out.forthnet.gr [193.92.150.104]) by mx1.freebsd.org (Postfix) with ESMTP id 2323B13C4D9 for ; Wed, 23 Jan 2008 22:31:02 +0000 (UTC) (envelope-from dds@FreeBSD.org) Received: from mx-av-04.forthnet.gr (mx-av.forthnet.gr [193.92.150.27]) by mx-out-05.forthnet.gr (8.13.8/8.13.8) with ESMTP id m0NMV1h2018102 for ; Thu, 24 Jan 2008 00:31:01 +0200 Received: from MX-IN-03.forthnet.gr (mx-in-05.forthnet.gr [193.92.150.32]) by mx-av-04.forthnet.gr (8.14.1/8.14.1) with ESMTP id m0NMV165008044 for ; Thu, 24 Jan 2008 00:31:01 +0200 Received: from [192.168.136.22] (ppp144-181.adsl.forthnet.gr [62.1.135.181]) by MX-IN-03.forthnet.gr (8.14.2/8.14.2) with ESMTP id m0NMUv55000616 for ; Thu, 24 Jan 2008 00:30:58 +0200 Authentication-Results: MX-IN-03.forthnet.gr smtp.mail=dds@FreeBSD.org; spf=permerror Authentication-Results: MX-IN-03.forthnet.gr header.from=dds@FreeBSD.org; sender-id=permerror Message-ID: <4797C01E.1010807@FreeBSD.org> Date: Thu, 24 Jan 2008 00:30:54 +0200 From: Diomidis Spinellis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 MIME-Version: 1.0 To: freebsd-current@FreeBSD.org References: <4797BADB.7000802@FreeBSD.org> In-Reply-To: <4797BADB.7000802@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-7; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Low NTFS read performance X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 22:31:04 -0000 Diomidis Spinellis wrote: > Diomidis Spinellis wrote in freebsd-stable@: >> I can't get an Ultrium-2 LTO drive to stream, and (I think) I've >> traced the problem to the read performance of the USB2-attached NTFS [...] >> I'd appreciate any suggestions you may have. > > Today I upgraded the machine to 8.0-CURRENT, and obtained similar results: > - 5372041 bytes/sec reading an NTFS file > - 15369758 bytes/sec reading from the raw device > > The raw/FS read performance difference with UFS is a lot lower: > - 33162654 bytes/sec reading a UFS file > - 47221133 bytes/sec reading from the raw device > > I'd welcome any ideas on why the NTFS layer makes reading three time > slower than reading from the raw device and suggestions for improving > the performance. I'd also be happy to work on improving the situation, > if I get any pointers on where to start. [Apologies for talking to myself.] It looks like the problem is the small (4K) block size NTFS uses for its requests. iostat -t da -zx -w 1 NTFS file: device r/s w/s kr/s kw/s wait svc_t %b da0 1329.6 0.0 5318.5 0.0 1 0.7 95 Raw device: device r/s w/s kr/s kw/s wait svc_t %b da0 234.8 0.0 15024.4 0.0 1 6.3 100 iostat -z -w1 NTFS file: tty ad0 da0 cpu tin tout KB/t tps MB/s KB/t tps MB/s us ni sy in id 0 77 0.00 0 0.00 4.00 1324 5.17 0 0 1 0 99 0 78 0.00 0 0.00 4.00 1331 5.20 0 0 1 0 99 0 78 0.00 0 0.00 4.00 1322 5.16 0 0 0 0 100 0 79 0.00 0 0.00 4.00 1331 5.20 0 0 0 0 100 Raw device: tty ad0 da0 cpu tin tout KB/t tps MB/s KB/t tps MB/s us ni sy in id 0 228 8.00 1 0.01 64.00 236 14.73 0 0 0 0 100 0 78 0.00 0 0.00 64.00 235 14.67 0 0 0 0 100 0 78 0.00 0 0.00 64.00 235 14.67 0 0 0 0 100 0 78 0.00 0 0.00 64.00 235 14.67 0 0 0 0 100 Diomidis Spinellis - http://www.spinellis.gr From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 22:34:58 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F8C616A419 for ; Wed, 23 Jan 2008 22:34:56 +0000 (UTC) (envelope-from dds@FreeBSD.org) Received: from mx-out.forthnet.gr (mx-out.forthnet.gr [193.92.150.104]) by mx1.freebsd.org (Postfix) with ESMTP id 306CF13C447 for ; Wed, 23 Jan 2008 22:34:55 +0000 (UTC) (envelope-from dds@FreeBSD.org) Received: from mx-av-02.forthnet.gr (mx-av.forthnet.gr [193.92.150.27]) by mx-out-02.forthnet.gr (8.14.0/8.14.0) with ESMTP id m0NM8WvK000725 for ; Thu, 24 Jan 2008 00:08:32 +0200 Received: from MX-IN-03.forthnet.gr (mx-in-05.forthnet.gr [193.92.150.32]) by mx-av-02.forthnet.gr (8.14.1/8.14.1) with ESMTP id m0NM8W6j017259 for ; Thu, 24 Jan 2008 00:08:32 +0200 Received: from [192.168.136.22] (ppp144-181.adsl.forthnet.gr [62.1.135.181]) by MX-IN-03.forthnet.gr (8.14.2/8.14.2) with ESMTP id m0NM8UsA011227 for ; Thu, 24 Jan 2008 00:08:31 +0200 Authentication-Results: MX-IN-03.forthnet.gr smtp.mail=dds@FreeBSD.org; spf=permerror Authentication-Results: MX-IN-03.forthnet.gr header.from=dds@FreeBSD.org; sender-id=permerror Message-ID: <4797BADB.7000802@FreeBSD.org> Date: Thu, 24 Jan 2008 00:08:27 +0200 From: Diomidis Spinellis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-7; format=flowed Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: Low NTFS read performance X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 22:34:58 -0000 Diomidis Spinellis wrote in freebsd-stable@: > I can't get an Ultrium-2 LTO drive to stream, and (I think) I've traced= =20 > the problem to the read performance of the USB2-attached NTFS disk, and= =20 > specifically the NTFS filesystem. I'm reading a single 190GB file, and= =20 > the throughput I'm getting is 5.4MB/s: >=20 > $ dd if=3Dad2c.dump of=3D/dev/null bs=3D1M > ^=D4 > load: 0.04 cmd: dd 1434 [biord] 0.00u 4.78s 2% 1672k > 610+0 records in > 610+0 records out > 639631360 bytes transferred in 117.937613 secs (5423472 bytes/sec) >=20 > The is an old but relatively fast machine >=20 > CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2407.18-MHz 686-class CPU) >=20 > running 7.0-RC1: >=20 > $ uname -a > FreeBSD icarian.dmst.aueb.gr 7.0-RC1 FreeBSD 7.0-RC1 #0: Mon Dec 24=20 > 12:18:24 UTC 2007=20 > root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 >=20 > and the load during the read remains comfortably low: >=20 > $ uptime > 6:34PM up 3:50, 3 users, load averages: 0.09, 0.04, 0.04 >=20 > Reading from the raw device tripples the performance: >=20 > # dd if=3D/dev/da0s1 bs=3D1m of=3D/dev/null > 533725184 bytes transferred in 34.777460 secs (15346871 bytes/sec) >=20 > bringing it on par with what I get from Windows (on a different machine= ): >=20 > F:\>dd if=3Dother.20051007.tgz of=3D/dev/null bs=3D1M > 1231030919 bytes (1.2 GB) copied, 82.845 s, 14.9 MB/s >=20 > [...] >=20 > I'd appreciate any suggestions you may have. Today I upgraded the machine to 8.0-CURRENT, and obtained similar result= s: - 5372041 bytes/sec reading an NTFS file - 15369758 bytes/sec reading from the raw device The raw/FS read performance difference with UFS is a lot lower: - 33162654 bytes/sec reading a UFS file - 47221133 bytes/sec reading from the raw device I'd welcome any ideas on why the NTFS layer makes reading three time=20 slower than reading from the raw device and suggestions for improving=20 the performance. I'd also be happy to work on improving the situation,=20 if I get any pointers on where to start. Diomidis Spinellis - http://www.spinellis.gr From owner-freebsd-current@FreeBSD.ORG Wed Jan 23 23:50:17 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5C40816A417 for ; Wed, 23 Jan 2008 23:50:17 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 24DC813C458 for ; Wed, 23 Jan 2008 23:50:17 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JHpMA-0001pO-TN for freebsd-current@freebsd.org; Wed, 23 Jan 2008 23:50:11 +0000 Received: from 78-1-98-105.adsl.net.t-com.hr ([78.1.98.105]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Jan 2008 23:50:10 +0000 Received: from ivoras by 78-1-98-105.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 23 Jan 2008 23:50:10 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Thu, 24 Jan 2008 00:49:59 +0100 Lines: 42 Message-ID: References: <4797B923.6030400@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigB2ADAB5030150AACF1977ABF" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 78-1-98-105.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) In-Reply-To: <4797B923.6030400@gmail.com> X-Enigmail-Version: 0.95.6 Sender: news Subject: Re: XEN and ZFS Status? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 23:50:17 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB2ADAB5030150AACF1977ABF Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable EchoB wrote: > I have read somewhere that ZFS is experimental at best,=20 Correct. > and wanted to confirm that. Also, using Xen would be a great plus in a = > production environment. Xen doesn't exist in 7.0, it may or may not be exist in 8.0. > Also - read somewhere about 8.0-Current - whats that all about? what=20 > are the differences between 7.0 and 8.0? Read=20 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.= html (8 is "current", 7 will be named "stable" when 7.0 gets released;=20 currently the latest official stable release is 6.3). --------------enigB2ADAB5030150AACF1977ABF Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHl9KnldnAQVacBcgRAtCMAJ4/vdD5Ht6Y4dKppdyyeYELPJCAaQCgru5H iOnNJve/qM7eMmOSsVoQwVI= =YLol -----END PGP SIGNATURE----- --------------enigB2ADAB5030150AACF1977ABF-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 00:07:50 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8530116A41B for ; Thu, 24 Jan 2008 00:07:50 +0000 (UTC) (envelope-from jb@what-creek.com) Received: from what-creek.com (what-creek.com [66.111.37.70]) by mx1.freebsd.org (Postfix) with ESMTP id 7643913C44B for ; Thu, 24 Jan 2008 00:07:50 +0000 (UTC) (envelope-from jb@what-creek.com) Received: by what-creek.com (Postfix, from userid 102) id D7EBC732FF; Wed, 23 Jan 2008 23:50:33 +0000 (GMT) Date: Wed, 23 Jan 2008 23:50:33 +0000 From: John Birrell To: gallatin@cs.duke.edu Message-ID: <20080123235033.GA3126@what-creek.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org Subject: DTrace for FreeBSD - status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 00:07:50 -0000 On Wed, 23 Jan 2008 14:05:23 -0600, Andrew Gallatin wrote: > What is the status of Dtrace in FreeBSD? I thought the original port > was permantly stalled due to licensing conflicts over CDDL, and > that John was starting from scratch. Cisco is currently funding the port of DTrace to FreeBSD part of their move to FreeBSD. I am probably a week away from putting up a set of diffs for the initial integration into CURRENT. See: for the list of changes/reasons. That page is still a work in progress. As of today, the port passes 752 of Sun's DTrace tests. FreeBSD developers with p4 access can build //depot/projects/dtrace/src and get an up-to-date CURRENT with DTrace built in. "make universe" works for all arches. The kernel modules are limited to amd64 and i386 at the moment. -- John Birrell From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 01:28:46 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1B7E16A417 for ; Thu, 24 Jan 2008 01:28:46 +0000 (UTC) (envelope-from gallatin@cs.duke.edu) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.freebsd.org (Postfix) with ESMTP id 7885213C45B for ; Thu, 24 Jan 2008 01:28:46 +0000 (UTC) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.14.0/8.14.0) with ESMTP id m0O1Sjrk012282 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Jan 2008 20:28:45 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id m0O1Rn4U005277; Wed, 23 Jan 2008 20:27:49 -0500 (EST) (envelope-from gallatin) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18327.59820.220839.701472@grasshopper.cs.duke.edu> Date: Wed, 23 Jan 2008 20:27:49 -0500 (EST) To: John Birrell In-Reply-To: <20080123235033.GA3126@what-creek.com> References: <20080123235033.GA3126@what-creek.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Cc: current@freebsd.org Subject: Re: DTrace for FreeBSD - status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 01:28:46 -0000 John Birrell writes: > On Wed, 23 Jan 2008 14:05:23 -0600, Andrew Gallatin > wrote: > > What is the status of Dtrace in FreeBSD? I thought the original port > > was permantly stalled due to licensing conflicts over CDDL, and > > that John was starting from scratch. > > Cisco is currently funding the port of DTrace to FreeBSD part of their > move to FreeBSD. > > I am probably a week away from putting up a set of diffs for the > initial integration into CURRENT. See: > for the list > of changes/reasons. That page is still a work in progress. That's the best news I've heard all month! Hurray! Drew From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 01:52:23 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F5B516A421 for ; Thu, 24 Jan 2008 01:52:23 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by mx1.freebsd.org (Postfix) with ESMTP id 0D62F13C47E for ; Thu, 24 Jan 2008 01:52:22 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay11.apple.com (relay11.apple.com [17.128.113.48]) by mail-out4.apple.com (Postfix) with ESMTP id 226551FE06A5 for ; Wed, 23 Jan 2008 17:37:16 -0800 (PST) Received: from relay11.apple.com (unknown [127.0.0.1]) by relay11.apple.com (Symantec Mail Security) with ESMTP id 0C8F7280D8 for ; Wed, 23 Jan 2008 17:37:16 -0800 (PST) X-AuditID: 11807130-a6c3fbb0000028a7-d7-4797ebcba6d1 Received: from cswiger1.apple.com (cswiger1.apple.com [17.214.13.96]) by relay11.apple.com (Apple SCV relay) with ESMTP id E92F4280C6 for ; Wed, 23 Jan 2008 17:37:15 -0800 (PST) Message-Id: <27DE3CFE-5B11-4544-8364-A3804AE8E252@mac.com> From: Chuck Swiger To: current@freebsd.org In-Reply-To: <18327.59820.220839.701472@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Date: Wed, 23 Jan 2008 17:37:15 -0800 References: <20080123235033.GA3126@what-creek.com> <18327.59820.220839.701472@grasshopper.cs.duke.edu> X-Mailer: Apple Mail (2.915) X-Brightmail-Tracker: AAAAAA== Cc: Subject: Re: DTrace for FreeBSD - status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 01:52:23 -0000 On Jan 23, 2008, at 5:27 PM, Andrew Gallatin wrote: > John Birrell writes: >> [ ... ] >> Cisco is currently funding the port of DTrace to FreeBSD part of >> their >> move to FreeBSD. >> >> I am probably a week away from putting up a set of diffs for the >> initial integration into CURRENT. See: >> for the list >> of changes/reasons. That page is still a work in progress. > > That's the best news I've heard all month! Hurray! Seconded. Thanks, John; and thanks, Cisco, for sponsoring this effort... -- -Chuck From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 02:04:53 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED2D716A419 for ; Thu, 24 Jan 2008 02:04:53 +0000 (UTC) (envelope-from SRS0=3a518e69b77a8b5a6b18de542effc7a2432d9fed=589=es.net=oberman@es.net) Received: from postal1.es.net (postal1.es.net [IPv6:2001:400:14:3::6]) by mx1.freebsd.org (Postfix) with ESMTP id 8733F13C44B for ; Thu, 24 Jan 2008 02:04:53 +0000 (UTC) (envelope-from SRS0=3a518e69b77a8b5a6b18de542effc7a2432d9fed=589=es.net=oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id EDC08352; Wed, 23 Jan 2008 18:04:52 -0800 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id C7D924500F; Wed, 23 Jan 2008 18:04:51 -0800 (PST) To: John Birrell In-Reply-To: Your message of "Wed, 23 Jan 2008 23:50:33 GMT." <20080123235033.GA3126@what-creek.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1201140291_84737P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Wed, 23 Jan 2008 18:04:51 -0800 From: "Kevin Oberman" Message-Id: <20080124020451.C7D924500F@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ;;; X-Sender: X-To_Name: John Birrell X-To_Domain: what-creek.com X-To: John Birrell X-To_Email: jb@what-creek.com X-To_Alias: jb Cc: gallatin@cs.duke.edu, current@freebsd.org Subject: Re: DTrace for FreeBSD - status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 02:04:54 -0000 --==_Exmh_1201140291_84737P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Wed, 23 Jan 2008 23:50:33 +0000 > From: John Birrell > Sender: owner-freebsd-current@freebsd.org > > On Wed, 23 Jan 2008 14:05:23 -0600, Andrew Gallatin > wrote: > > What is the status of Dtrace in FreeBSD? I thought the original port > > was permantly stalled due to licensing conflicts over CDDL, and > > that John was starting from scratch. > > Cisco is currently funding the port of DTrace to FreeBSD part of their > move to FreeBSD. > > I am probably a week away from putting up a set of diffs for the > initial integration into CURRENT. See: > for the list > of changes/reasons. That page is still a work in progress. > > As of today, the port passes 752 of Sun's DTrace tests. > > FreeBSD developers with p4 access can build //depot/projects/dtrace/src > and get an up-to-date CURRENT with DTrace built in. "make universe" > works for all arches. The kernel modules are limited to amd64 and i386 > at the moment. John, Thanks you and Cisco very much for this work. It should be incredibly valuable to a large number of FreeBSD users as well as the FreeBSD development community. -- 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 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1201140291_84737P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFHl/JDkn3rs5h7N1ERApZOAKC0BZ8EceNl6VQSaaMw3L/GNLoD6QCeK7Ab nI9x1ON03Z/5bGrn/vMU65c= =3D9T -----END PGP SIGNATURE----- --==_Exmh_1201140291_84737P-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 03:23:53 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8524C16A419; Thu, 24 Jan 2008 03:23:53 +0000 (UTC) (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 5323713C46A; Thu, 24 Jan 2008 03:23:53 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m0O3NoGK070716; Wed, 23 Jan 2008 20:23:50 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <479804C6.4060001@samsco.org> Date: Wed, 23 Jan 2008 20:23:50 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.11) Gecko/20071128 SeaMonkey/1.1.7 MIME-Version: 1.0 To: Ivan Voras References: <4797B923.6030400@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Wed, 23 Jan 2008 20:23:50 -0700 (MST) X-Spam-Status: No, score=-1.4 required=5.4 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: freebsd-current@freebsd.org Subject: Re: XEN and ZFS Status? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 03:23:53 -0000 Ivan Voras wrote: > EchoB wrote: >> I have read somewhere that ZFS is experimental at best, > > Correct. > >> and wanted to confirm that. Also, using Xen would be a great plus in a >> production environment. > > Xen doesn't exist in 7.0, it may or may not be exist in 8.0. > Despite Ivan's brief and pessimistic assessment of Xen in FreeBSD, progress is quickly being made, and there's a pretty good chance that code will be made available soon for public testing. See Kip Macy's posting on this thread for more information. Scott From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 08:02:06 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 487E616A469 for ; Thu, 24 Jan 2008 08:02:06 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155]) by mx1.freebsd.org (Postfix) with ESMTP id C27F313C44B for ; Thu, 24 Jan 2008 08:02:05 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so146419fgg.35 for ; Thu, 24 Jan 2008 00:02:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=omlC2+n3Jx5W0KIph2yH2MN/4e3rvwGG3BVn199NJ0s=; b=pUVMrrqeY2DBap+Zt9MaxOayrSqcIUOwQRvsb9y/xWkFYV5Aa11rjEIXUHIEYCmzJfILHKNecBgqlgWSP9uLayel1OP1hXQjdoTctS68DiijlopL8L3o61Qapj+EUg/bcyKkrHc4oTUjnWL3imT2DdFidaYcoYNvhzbIGs2Hx/8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ebuLiKl9ZlL3vjF7OU3lFgNybmXV9eo68hj8b9k05f12q9wMsxZTui3XF7w/XFrwEk+PEb+ammCOhO4+IZNXFGZo40hhMzZz1wRH0u11svichwbMs7CIY9Cin+uNquMophrotWKYl5iM8DeXUc0IRgIqIJBqdxy/NxQ1ucoxI40= Received: by 10.86.26.11 with SMTP id 11mr352193fgz.37.1201161724311; Thu, 24 Jan 2008 00:02:04 -0800 (PST) Received: by 10.86.52.6 with HTTP; Thu, 24 Jan 2008 00:02:04 -0800 (PST) Message-ID: <11167f520801240002q178c8545qf5b2ce83c4627761@mail.gmail.com> Date: Thu, 24 Jan 2008 02:02:04 -0600 From: "Sam Fourman Jr." To: "Scott Long" In-Reply-To: <479804C6.4060001@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4797B923.6030400@gmail.com> <479804C6.4060001@samsco.org> Cc: freebsd-current@freebsd.org, Ivan Voras Subject: Re: XEN and ZFS Status? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 08:02:06 -0000 On Jan 23, 2008 9:23 PM, Scott Long wrote: > Ivan Voras wrote: > > EchoB wrote: > >> I have read somewhere that ZFS is experimental at best, > > > > Correct. > > > >> and wanted to confirm that. Also, using Xen would be a great plus in a > >> production environment. > > > > Xen doesn't exist in 7.0, it may or may not be exist in 8.0. > > > > Despite Ivan's brief and pessimistic assessment of Xen in FreeBSD, > progress is quickly being made, and there's a pretty good chance that > code will be made available soon for public testing. See Kip Macy's > posting on this thread for more information. > > Scott dom0 on amd64? Sam Fourman Jr. From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 08:04:53 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4C0D16A421 for ; Thu, 24 Jan 2008 08:04:53 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by mx1.freebsd.org (Postfix) with ESMTP id AA13313C447 for ; Thu, 24 Jan 2008 08:04:53 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so243529waf.3 for ; Thu, 24 Jan 2008 00:04:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=j8ZDJcqDMLIZKJlDOxccb1Bp+VSfr/eUY9//pP34cPM=; b=NJLFIprznR5IR7kx0FkaglV1XJgz8IByofP5BJ7+qgT3tmTESDtcTlOjOUxGhQMUlTcjCauTWEl8sXQTan5e/jUhJjyBVTzGBeKkGcvKgyJmbSzBFV0+X8duqRLvHE6yJKXbes1+fh5i1uZfTcGxxdhVN/HKoWYEDfno1rcgYkU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RBM2imCkxkvwqQV4MviVfwI/XjIwwsM/kLmHjWe7EKSdR3RDYdYrGvtBGTEo3vKJh2KAgBbnCc3lwpSSsyynTqUHsPkifXyeNJHrG8mHdAXtGbRef5WYZmfeFOa6eb6qVDZbAgMHhgnFlAdqCZi41B24B1CYa9lHb+1QfBGmJ00= Received: by 10.114.179.1 with SMTP id b1mr417223waf.143.1201161892881; Thu, 24 Jan 2008 00:04:52 -0800 (PST) Received: by 10.114.255.16 with HTTP; Thu, 24 Jan 2008 00:04:52 -0800 (PST) Message-ID: Date: Thu, 24 Jan 2008 00:04:52 -0800 From: "Kip Macy" To: "Sam Fourman Jr." In-Reply-To: <11167f520801240002q178c8545qf5b2ce83c4627761@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4797B923.6030400@gmail.com> <479804C6.4060001@samsco.org> <11167f520801240002q178c8545qf5b2ce83c4627761@mail.gmail.com> Cc: freebsd-current@freebsd.org, Ivan Voras Subject: Re: XEN and ZFS Status? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 08:04:53 -0000 On Jan 24, 2008 12:02 AM, Sam Fourman Jr. wrote: > On Jan 23, 2008 9:23 PM, Scott Long wrote: > > Ivan Voras wrote: > > > EchoB wrote: > > >> I have read somewhere that ZFS is experimental at best, > > > > > > Correct. > > > > > >> and wanted to confirm that. Also, using Xen would be a great plus in a > > >> production environment. > > > > > > Xen doesn't exist in 7.0, it may or may not be exist in 8.0. > > > > > > > Despite Ivan's brief and pessimistic assessment of Xen in FreeBSD, > > progress is quickly being made, and there's a pretty good chance that > > code will be made available soon for public testing. See Kip Macy's > > posting on this thread for more information. > > > > Scott > > dom0 on amd64? amd64 soonish, dom0 only if sponsored to do so or if a substantial amount of free time opens up. -Kip From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 09:45:26 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B55A216A417 for ; Thu, 24 Jan 2008 09:45:26 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 12F7913C448 for ; Thu, 24 Jan 2008 09:45:25 +0000 (UTC) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 24 Jan 2008 09:45:23 -0000 Received: from unknown (EHLO [192.168.0.10]) [85.127.93.157] by mail.gmx.net (mp011) with SMTP; 24 Jan 2008 10:45:23 +0100 X-Authenticated: #16703784 X-Provags-ID: V01U2FsdGVkX1/TLVFw7jXTqSfv4fZGAFCR9mFuj0NVRt93A1yUf9 LkpVFNGXTLbjpd From: Stefan Ehmann To: freebsd-current@freebsd.org Date: Thu, 24 Jan 2008 10:45:22 +0100 User-Agent: KMail/1.9.7 References: <4797BADB.7000802@FreeBSD.org> In-Reply-To: <4797BADB.7000802@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-7" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801241045.23164.shoesoft@gmx.net> X-Y-GMX-Trusted: 0 Cc: Diomidis Spinellis Subject: Re: Low NTFS read performance X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 09:45:26 -0000 On Wednesday 23 January 2008 23:08:27 Diomidis Spinellis wrote: > Diomidis Spinellis wrote in freebsd-stable@: > > I can't get an Ultrium-2 LTO drive to stream, and (I think) I've traced > > the problem to the read performance of the USB2-attached NTFS disk, and > > specifically the NTFS filesystem. I'm reading a single 190GB file, and > > the throughput I'm getting is 5.4MB/s: Are you using the NTFS kernel option or the sysutils/fusefs-ntfs Port? In my experience the latter is much faster and probably superior in most other aspects. From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 09:48:27 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F122016A41A for ; Thu, 24 Jan 2008 09:48:27 +0000 (UTC) (envelope-from oskar-FreeBSD@eyb.de) Received: from beastie.eyb.de (beastie.eyb.de [85.214.103.56]) by mx1.freebsd.org (Postfix) with ESMTP id E9C4113C4F2 for ; Thu, 24 Jan 2008 09:48:26 +0000 (UTC) (envelope-from oskar-FreeBSD@eyb.de) Received: from chuck.ath.cx (dslb-088-066-233-083.pools.arcor-ip.net [88.66.233.83]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by beastie.eyb.de (Postfix) with ESMTP id 35F3F8B799C for ; Thu, 24 Jan 2008 10:32:07 +0100 (CET) Received: from [10.0.0.3] (saturn.intra.eyb.de [10.0.0.3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by chuck.ath.cx (Postfix) with ESMTP id 528AF11850D5 for ; Thu, 24 Jan 2008 10:32:36 +0100 (CET) Message-ID: <47985B01.6000003@eyb.de> Date: Thu, 24 Jan 2008 10:31:45 +0100 From: Oskar Eyb User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: syncache_timer: Response timeout and other msgs, whats up? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 09:48:28 -0000 Hello! I#m not sure if this is a issue belonging to -current, but maybe.. A remote MTA cannot deliver me any email. the admin gets the following errors: "retry time not reached for any host after a long failure period" and "retry timeout exceeded". After I cant find anything related to this server in my postfix log, I grep'ed for in /var/log/* and got the following hits: [...] dmesg.yesterday:TCP: [85.214.42.62]:43127 to [172.16.0.2]:25 tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK dmesg.yesterday:TCP: [85.214.42.62]:43127 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (1) SYN|ACK dmesg.yesterday:TCP: [85.214.42.62]:43127 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (2) SYN|ACK dmesg.yesterday:TCP: [85.214.42.62]:43127 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (3) SYN|ACK dmesg.yesterday:TCP: [85.214.42.62]:43127 to [172.16.0.2]:25; syncache_timer: Retransmits exhausted, giving up and removing syncache entry 85.214.42.62 is the other MTA, 172.16.0.2 is my jail. I use PF with rdr/nat on FreeBSD 7 RC4. in the daily security email I get dozens of messages like this, also to other tcp ports. default-values for: net.inet.tcp.syncache.rst_on_sock_fail: 1 net.inet.tcp.syncache.rexmtlimit: 3 net.inet.tcp.syncache.hashsize: 512 net.inet.tcp.syncache.count: 0 net.inet.tcp.syncache.cachelimit: 15360 net.inet.tcp.syncache.bucketlimit: 30 Can anybody help me out of this? Greets, Oskar +TCP: [58.182.131.11]:4216 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_1: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4216 to [172.16.0.2]:25 tcpflags 0x10; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4216 to [172.16.0.2]:25 tcpflags 0x11; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4217 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_1: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4217 to [172.16.0.2]:25 tcpflags 0x10; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4217 to [172.16.0.2]:25 tcpflags 0x11; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4218 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_2: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4218 to [172.16.0.2]:25 tcpflags 0x11; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4219 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_2: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4219 to [172.16.0.2]:25 tcpflags 0x11; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4220 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_1: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4220 to [172.16.0.2]:25 tcpflags 0x10; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4220 to [172.16.0.2]:25 tcpflags 0x11; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4221 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_2: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4221 to [172.16.0.2]:25 tcpflags 0x11; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4222 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_1: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4222 to [172.16.0.2]:25 tcpflags 0x10; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4222 to [172.16.0.2]:25 tcpflags 0x11; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4223 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_2: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4223 to [172.16.0.2]:25 tcpflags 0x11; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4224 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_1: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4224 to [172.16.0.2]:25 tcpflags 0x10; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4224 to [172.16.0.2]:25 tcpflags 0x11; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4225 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_2: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4225 to [172.16.0.2]:25 tcpflags 0x11; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4226 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_1: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4226 to [172.16.0.2]:25 tcpflags 0x10; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4226 to [172.16.0.2]:25 tcpflags 0x11; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4227 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_1: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4227 to [172.16.0.2]:25 tcpflags 0x10; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4227 to [172.16.0.2]:25 tcpflags 0x11; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4228 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_2: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4228 to [172.16.0.2]:25 tcpflags 0x11; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4229 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_1: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4230 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_2: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4231 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_2: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4232 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_2: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4230 to [172.16.0.2]:25 tcpflags 0x18; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4231 to [172.16.0.2]:25 tcpflags 0x18; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4234 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_1: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4234 to [172.16.0.2]:25 tcpflags 0x10; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4234 to [172.16.0.2]:25 tcpflags 0x11; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4235 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_1: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4235 to [172.16.0.2]:25 tcpflags 0x10; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4235 to [172.16.0.2]:25 tcpflags 0x11; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4236 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_2: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4236 to [172.16.0.2]:25 tcpflags 0x11; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [58.182.131.11]:4233 to [172.16.0.2]:25 tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK +TCP: [58.182.131.11]:4233 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_2: Received 6 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [58.182.131.11]:4233 to [172.16.0.2]:25 tcpflags 0x18; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +Connection attempt to UDP 172.16.0.2:57897 from 85.214.103.56:53 +Connection attempt to UDP 172.16.0.2:60521 from 85.214.103.56:53 +TCP: [59.189.18.5]:1332 to [172.16.0.2]:25 tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK +TCP: [59.189.18.5]:1332 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (1) SYN|ACK +TCP: [59.189.18.5]:1332 to [172.16.0.2]:25 tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK +TCP: [59.189.18.5]:1332 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (1) SYN|ACK +TCP: [59.189.18.5]:1332 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (2) SYN|ACK +TCP: [59.189.18.5]:1332 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (3) SYN|ACK +TCP: [59.189.18.5]:1700 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (1) SYN|ACK +TCP: [59.189.18.5]:1700 to [172.16.0.2]:25 tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK +TCP: [59.189.18.5]:1700 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (1) SYN|ACK +TCP: [59.189.18.5]:1700 to [172.16.0.2]:25 tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK +TCP: [59.189.18.5]:1332 to [172.16.0.2]:25; syncache_timer: Retransmits exhausted, giving up and removing syncache entry +TCP: [59.189.18.5]:1700 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (1) SYN|ACK +TCP: [59.189.18.5]:1700 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (2) SYN|ACK +TCP: [59.189.18.5]:1700 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (3) SYN|ACK +Connection attempt to UDP 85.214.103.56:57111 from 88.191.254.7:53 +TCP: [59.189.18.5]:2189 to [172.16.0.2]:25 tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK +TCP: [83.40.210.36]:27836 to [172.16.0.2]:25 tcpflags 0x4; syncache_chkrst: Spurious RST without matching syncache entry (possibly syncookie only), segment ignored +TCP: [59.189.18.5]:2189 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (1) SYN|ACK +TCP: [59.189.18.5]:1700 to [172.16.0.2]:25; syncache_timer: Retransmits exhausted, giving up and removing syncache entry +TCP: [59.189.18.5]:2189 to [172.16.0.2]:25 tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK +TCP: [59.189.18.5]:2189 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (1) SYN|ACK +TCP: [59.189.18.5]:2189 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (2) SYN|ACK +TCP: [59.189.18.5]:2189 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (3) SYN|ACK +TCP: [213.5.169.184]:62636 to [172.16.0.2]:25 tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK +TCP: [213.5.169.184]:62636 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (1) SYN|ACK +TCP: [213.5.169.184]:62636 to [172.16.0.2]:25 tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK +TCP: [213.5.169.184]:62636 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (1) SYN|ACK +TCP: [59.189.18.5]:2189 to [172.16.0.2]:25; syncache_timer: Retransmits exhausted, giving up and removing syncache entry +TCP: [213.5.169.184]:62636 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (2) SYN|ACK +TCP: [213.5.169.184]:62636 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (3) SYN|ACK +TCP: [193.43.150.242]:60772 to [85.214.103.56]:22 tcpflags 0x2; tcp_input: Connection attempt to closed port +Connection attempt to UDP 172.16.0.2:59259 from 85.214.103.56:53 +Connection attempt to UDP 172.16.0.2:52025 from 85.214.103.56:53 +TCP: [213.5.169.184]:62636 to [172.16.0.2]:25; syncache_timer: Retransmits exhausted, giving up and removing syncache entry +TCP: [64.237.204.59]:64347 to [172.16.0.2]:25 tcpflags 0x4; syncache_chkrst: Spurious RST without matching syncache entry (possibly syncookie only), segment ignored +Connection attempt to UDP 172.16.0.2:49575 from 85.214.103.56:53 +Connection attempt to UDP 172.16.0.2:49201 from 85.214.103.56:53 +Connection attempt to UDP 172.16.0.2:53140 from 85.214.103.56:53 +Connection attempt to UDP 172.16.0.2:60597 from 85.214.103.56:53 +TCP: [209.223.48.146]:36342 to [172.16.0.2]:25 tcpflags 0x4; syncache_chkrst: Spurious RST without matching syncache entry (possibly syncookie only), segment ignored +TCP: [189.132.247.46]:3006 to [172.16.0.2]:25 tcpflags 0x14; syncache_chkrst: Spurious RST with ACK, SYN or FIN flag set, segment ignored +TCP: [190.142.56.104]:1990 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (1) SYN|ACK +TCP: [190.142.56.104]:1990 to [172.16.0.2]:25 tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK +TCP: [190.142.56.104]:2350 to [172.16.0.2]:25 tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK +TCP: [72.52.143.18]:38333 to [172.16.0.2]:25 tcpflags 0x4; syncache_chkrst: Spurious RST without matching syncache entry (possibly syncookie only), segment ignored +TCP: [65.19.179.9]:1973 to [172.16.0.2]:25 tcpflags 0x4; syncache_chkrst: Spurious RST without matching syncache entry (possibly syncookie only), segment ignored +TCP: [88.67.29.27]:62531 to [172.16.0.2]:25 tcpflags 0x18; tcp_do_segment: FIN_WAIT_2: Received 37 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [88.67.29.27]:62531 to [172.16.0.2]:25 tcpflags 0x11; syncache_expand: Segment failed SYNCOOKIE authentication, segment rejected (probably spoofed) +TCP: [195.4.92.9]:25 to [172.16.0.2]:57654 tcpflags 0x18; tcp_do_segment: FIN_WAIT_1: Received 69 bytes of data after socket was closed, sending RST and removing tcpcb +TCP: [213.133.109.71]:47054 to [172.16.0.2]:25 tcpflags 0x4; syncache_chkrst: Spurious RST without matching syncache entry (possibly syncookie only), segment ignored +TCP: [202.164.234.72]:3775 to [172.16.0.2]:25 tcpflags 0x4; syncache_chkrst: Spurious RST without matching syncache entry (possibly syncookie only), segment ignored +TCP: [207.217.120.84]:54387 to [172.16.0.2]:25 tcpflags 0x4; syncache_chkrst: Spurious RST without matching syncache entry (possibly syncookie only), segment ignored +TCP: [207.217.120.84]:54387 to [172.16.0.2]:25 tcpflags 0x4; syncache_chkrst: Spurious RST without matching syncache entry (possibly syncookie only), segment ignored +TCP: [220.226.52.141]:3655 to [172.16.0.2]:25 tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK +TCP: [220.226.52.141]:3655 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (1) SYN|ACK +TCP: [220.226.52.141]:3655 to [172.16.0.2]:25 tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK +TCP: [220.226.52.141]:3655 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (1) SYN|ACK +TCP: [217.255.195.182]:61347 to [172.16.0.2]:25 tcpflags 0x4; syncache_chkrst: Spurious RST without matching syncache entry (possibly syncookie only), segment ignored +TCP: [220.226.52.141]:4446 to [172.16.0.2]:25; syncache_timer: Response timeout, retransmitting (1) SYN|ACK +TCP: [220.226.52.141]:4446 to [172.16.0.2]:25 tcpflags 0x2; syncache_add: Received duplicate SYN, resetting timer and retransmitting SYN|ACK From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 09:51:03 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E42016A469 for ; Thu, 24 Jan 2008 09:51:03 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 53BE013C442 for ; Thu, 24 Jan 2008 09:51:02 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id D010D2083; Thu, 24 Jan 2008 10:50:53 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id C2F5B2082; Thu, 24 Jan 2008 10:50:53 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id B5367844AF; Thu, 24 Jan 2008 10:50:53 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: EchoB References: <4797B923.6030400@gmail.com> Date: Thu, 24 Jan 2008 10:50:53 +0100 In-Reply-To: <4797B923.6030400@gmail.com> (EchoB's message of "Wed\, 23 Jan 2008 17\:01\:07 -0500") Message-ID: <86odbbwo02.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: XEN and ZFS Status? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 09:51:03 -0000 EchoB writes: > Hi all :) Can anyone point me in the direction of any detailed docs or > perhaps just an answer on here re: production status of Xen and ZFS > when 7.0 is released? I have read somewhere that ZFS is experimental > at best, and wanted to confirm that. Also, using Xen would be a great > plus in a production environment. I use ZFS in production. Xen is currently not supported at all, AFAIK. > Also - read somewhere about 8.0-Current - whats that all about? what > are the differences between 7.0 and 8.0? Read the fine handbook and / or the fine FAQ: http://www.freebsd.org/doc/en/books/handbook/ http://www.freebsd.org/doc/en/books/faq/ DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 09:55:57 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3178916A469 for ; Thu, 24 Jan 2008 09:55:57 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id E868513C465 for ; Thu, 24 Jan 2008 09:55:56 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id BD1422093; Thu, 24 Jan 2008 10:55:49 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id AF2522092; Thu, 24 Jan 2008 10:55:49 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id A1EA3844C3; Thu, 24 Jan 2008 10:55:49 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: John Birrell References: <20080123235033.GA3126@what-creek.com> Date: Thu, 24 Jan 2008 10:55:49 +0100 In-Reply-To: <20080123235033.GA3126@what-creek.com> (John Birrell's message of "Wed\, 23 Jan 2008 23\:50\:33 +0000") Message-ID: <86k5lzwnru.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: gallatin@cs.duke.edu, current@freebsd.org Subject: Re: DTrace for FreeBSD - status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 09:55:57 -0000 John Birrell writes: > I am probably a week away from putting up a set of diffs for the > initial integration into CURRENT. See: > for the list > of changes/reasons. That page is still a work in progress. http://wiki.freebsd.org/DTrace would be nice :) If you want, I can bootstrap it from reasons.html for you. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 11:01:30 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14F8916A419 for ; Thu, 24 Jan 2008 11:01:30 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 9442713C4F4 for ; Thu, 24 Jan 2008 11:01:28 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JHzpn-0005CQ-16 for freebsd-current@freebsd.org; Thu, 24 Jan 2008 11:01:27 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 24 Jan 2008 11:01:27 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 24 Jan 2008 11:01:27 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Thu, 24 Jan 2008 12:01:25 +0100 Lines: 41 Message-ID: References: <4797B923.6030400@gmail.com> <479804C6.4060001@samsco.org> <11167f520801240002q178c8545qf5b2ce83c4627761@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig0AB94F49C5FC52B0BEBBCE8B" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.6 (X11/20071022) In-Reply-To: X-Enigmail-Version: 0.95.0 Sender: news Subject: Re: XEN and ZFS Status? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 11:01:30 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0AB94F49C5FC52B0BEBBCE8B Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Kip Macy wrote: > amd64 soonish, dom0 only if sponsored to do so or if a substantial > amount of free time opens up. Then my pessimism is not ungrounded :) Seriously, the only way I would use Xen (meaning me, for my projects - other people are sure to have different priorities) is as dom0 for hosting other OS-es (mainly Linux). In the other direction (FreeBSD as guest of other systems) there are other free and good solutions like VMWa= re. I'm all for sponsoring you or anyone else to develop the functionality, but I probably can't even approach the amount such serious work would require. I know FreeBSD Foundation has barred targeted donations so would you (and the community of potential donators) be interested in doing something like phk did a few years back, personally ask and set up the infrastructure (paypal?) to receive a mass of small donations to fund this work? --------------enig0AB94F49C5FC52B0BEBBCE8B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHmHAFldnAQVacBcgRAmuqAKCM0e2UJIx/KDdoUG09pnfzFSaNvQCgumNR pNuaLg7uLTTkEsAqEdzW6yM= =7dv5 -----END PGP SIGNATURE----- --------------enig0AB94F49C5FC52B0BEBBCE8B-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 10:02:18 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE26016A469 for ; Thu, 24 Jan 2008 10:02:18 +0000 (UTC) (envelope-from dds@aueb.gr) Received: from mx-out.forthnet.gr (mx-out.forthnet.gr [193.92.150.104]) by mx1.freebsd.org (Postfix) with ESMTP id 4A7AF13C455 for ; Thu, 24 Jan 2008 10:02:18 +0000 (UTC) (envelope-from dds@aueb.gr) Received: from mx-av-01.forthnet.gr (mx-av.forthnet.gr [193.92.150.27]) by mx-out-02.forthnet.gr (8.14.0/8.14.0) with ESMTP id m0O9psaP018177; Thu, 24 Jan 2008 11:51:54 +0200 Received: from MX-IN-01.forthnet.gr (mx-in-01.forthnet.gr [193.92.150.23]) by mx-av-01.forthnet.gr (8.14.1/8.14.1) with ESMTP id m0O9pskA022995; Thu, 24 Jan 2008 11:51:54 +0200 Received: from [192.168.136.22] (ppp144-181.adsl.forthnet.gr [62.1.135.181]) by MX-IN-01.forthnet.gr (8.14.2/8.14.2) with ESMTP id m0O9pqRa019413; Thu, 24 Jan 2008 11:51:53 +0200 Authentication-Results: MX-IN-01.forthnet.gr smtp.mail=dds@aueb.gr; spf=neutral Authentication-Results: MX-IN-01.forthnet.gr header.from=dds@aueb.gr; sender-id=neutral Message-ID: <47985FB3.2070500@aueb.gr> Date: Thu, 24 Jan 2008 11:51:47 +0200 From: Diomidis Spinellis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 MIME-Version: 1.0 To: Stefan Ehmann References: <4797BADB.7000802@FreeBSD.org> <200801241045.23164.shoesoft@gmx.net> In-Reply-To: <200801241045.23164.shoesoft@gmx.net> Content-Type: text/plain; charset=ISO-8859-7; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 24 Jan 2008 12:24:19 +0000 Cc: freebsd-current@FreeBSD.ORG Subject: Re: Low NTFS read performance X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 10:02:19 -0000 Stefan Ehmann wrote: > On Wednesday 23 January 2008 23:08:27 Diomidis Spinellis wrote: >> Diomidis Spinellis wrote in freebsd-stable@: >>> I can't get an Ultrium-2 LTO drive to stream, and (I think) I've traced >>> the problem to the read performance of the USB2-attached NTFS disk, and >>> specifically the NTFS filesystem. I'm reading a single 190GB file, and >>> the throughput I'm getting is 5.4MB/s: > > Are you using the NTFS kernel option or the sysutils/fusefs-ntfs Port? > > In my experience the latter is much faster and probably superior in most other > aspects. I'm using the NTFS kernel option. I think the problem lies in the line bread(vp, cn, ntfs_cntob(1), NOCRED, &bp); of ntfs_vnops.c. We should be reading bigger blocks. Thanks for the suggestion, I'll try the port. From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 12:28:08 2008 Return-Path: Delivered-To: freebsd-current@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56AB116A41A; Thu, 24 Jan 2008 12:28:08 +0000 (UTC) (envelope-from yar@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 45C8C13C46B; Thu, 24 Jan 2008 12:28:08 +0000 (UTC) (envelope-from yar@FreeBSD.org) Received: from freefall.freebsd.org (yar@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m0OCS8Eh038947; Thu, 24 Jan 2008 12:28:08 GMT (envelope-from yar@freefall.freebsd.org) Received: (from yar@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m0OCS8fN038946; Thu, 24 Jan 2008 12:28:08 GMT (envelope-from yar) Date: Thu, 24 Jan 2008 12:28:08 +0000 From: Yar Tikhiy To: Kostik Belousov Message-ID: <20080124122808.GA15600@freefall.freebsd.org> References: <790a9fff0801150552l542a4238ofc12efe5fdb45fc2@mail.gmail.com> <20080115143924.GB57756@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080115143924.GB57756@deviant.kiev.zoral.com.ua> User-Agent: Mutt/1.4.2.3i Cc: Attilio Rao , freebsd-current@FreeBSD.org Subject: Re: panic: System call lstat returning with 1 locks held X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 12:28:08 -0000 On Tue, Jan 15, 2008 at 04:39:24PM +0200, Kostik Belousov wrote: > > I think this could be related to the recent vn_lock()/VOP_LOCK() KPI changes. > Please, add DEBUG_VFS_LOCKS to the kernel config, and do the > show lockedvnods > from the ddb prompt when the panic occurs. The witness does not track > the lockmgr locks. I think I'm seeing the same panic on UFS. It's rather nasty: I cannot rebuild CURRENT natively due to it so I have to build it under 6-STABLE. My favourite way to trigger the panic reliably is running `make install' in a simple port directory, e.g., portmaster, but my system also panics during daily scripts run and, as already said, if trying to build world. Now my kernel config is: include GENERIC ident "_LOCKTEST" options DEBUG_VFS_LOCKS Attached is the debug output after the panic. Alas, no locked vnodes are shown. How can I help to investigate this issue further? Yar panic: System call lstat returning with 1 locks held cpuid = 0 KDB: enter: panic [thread pid 2024 tid 100102 ] Stopped at kdb_enter+0x3a: movl $0,kdb_why db> show lockedvnods Locked vnodes db> where Tracing pid 2024 tid 100102 td 0xc3720000 kdb_enter(c0b0bdc0,c0b0bdc0,c0b3c319,d6218c8c,0,...) at kdb_enter+0x3a panic(c0b3c319,c0b11902,1,c0b11902,c0bbf390,...) at panic+0x12c syscall(d6218d38) at syscall+0x46e Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (0, FreeBSD ELF32, nosys), eip = 0x2815da8b, esp = 0xbfbfe86c, ebp = 0xbfbfe8f8 --- From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 12:42:27 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2333916A417; Thu, 24 Jan 2008 12:42:27 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from relay02.kiev.sovam.com (relay02.kiev.sovam.com [62.64.120.197]) by mx1.freebsd.org (Postfix) with ESMTP id 9A8A413C4E9; Thu, 24 Jan 2008 12:42:26 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from [212.82.216.226] (helo=skuns.kiev.zoral.com.ua) by relay02.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1JI1PS-000Gj5-H1; Thu, 24 Jan 2008 14:42:25 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by skuns.kiev.zoral.com.ua (8.14.1/8.14.1) with ESMTP id m0OCfvhQ004134 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Jan 2008 14:41:57 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m0OCgET1049518; Thu, 24 Jan 2008 14:42:14 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2/Submit) id m0OCgDqs049517; Thu, 24 Jan 2008 14:42:13 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 24 Jan 2008 14:42:13 +0200 From: Kostik Belousov To: Joe Marcus Clarke Message-ID: <20080124124213.GD57756@deviant.kiev.zoral.com.ua> References: <4792C32C.5010205@gmail.com> <20080122133835.GT57756@deviant.kiev.zoral.com.ua> <4796356D.9080809@gmail.com> <20080123051648.GV57756@deviant.kiev.zoral.com.ua> <479796E1.4000500@gmail.com> <1201118159.38742.17.camel@shumai.marcuscom.com> <20080123211149.GA57756@deviant.kiev.zoral.com.ua> <1201123933.62127.9.camel@shumai.marcuscom.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4Vp5PwKxXEv3SO34" Content-Disposition: inline In-Reply-To: <1201123933.62127.9.camel@shumai.marcuscom.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Scanner-Signature: 0938e96f3945d0d200dbca064d41c639 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 2045 [Jan 24 2008] X-SpamTest-Info: helo_type=3 X-SpamTest-Info: {received from trusted relay: not dialup} X-SpamTest-Method: none X-SpamTest-Method: Local Lists X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0255], KAS30/Release Cc: FreeBSD Current Subject: Re: page fault panic in scioctl and console-kit-daemon X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 12:42:27 -0000 --4Vp5PwKxXEv3SO34 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 23, 2008 at 04:32:13PM -0500, Joe Marcus Clarke wrote: >=20 > On Wed, 2008-01-23 at 23:11 +0200, Kostik Belousov wrote: > > On Wed, Jan 23, 2008 at 02:55:59PM -0500, Joe Marcus Clarke wrote: > > >=20 > > > On Wed, 2008-01-23 at 20:34 +0100, Pawel Worach wrote: > > > > Kostik Belousov wrote: > > > > > On Tue, Jan 22, 2008 at 07:26:53PM +0100, Pawel Worach wrote: > > > > >> Kostik Belousov wrote: > > > > >>> On Sun, Jan 20, 2008 at 04:42:36AM +0100, Pawel Worach wrote: > > > > >>>> Hi, > > > > >>>> > > > > >>>> While starting console-kit-daemon (sysutils/consolekit 0.2.3) = during=20 > > > > >>>> boot or in single-user mode the system panics. If I start it p= ost-boot=20 > > > > >>>> it runs fine. This is on 8.0-CURRENT from about 12 hours ago, = another=20 > > > > >>>> user also reported the same on RELENG_7. Any other information= I can=20 > > > > >>>> provide ? > > > > >>>> > > > > >>>> Fatal trap 12: page fault while in kernel mode > > > > >>>> fault virtual address =3D 0x4 > > > > >>>> fault code =3D supervisor read, page not present > > > > >>>> instruction pointer =3D 0x20:0xc04d2ab4 > > > > >>>> stack pointer =3D 0x28:0xe6499b18 > > > > >>>> frame pointer =3D 0x28:0xe6499b80 > > > > >>>> code segment =3D base 0x0, limit 0xfffff, type 0x1b > > > > >>>> =3D DPL 0, pres 1, def32 1, gran 1 > > > > >>>> processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > > > > >>>> current process =3D 134 (console-kit-daemon) > > > > >>>> Physical memory: 1014 MB > > > > >>>> Dumping 43 MB: 28 12 > > > > >>>> > > > > >>>> #8 0xc07a34a2 in trap (frame=3D0xe6499ad8) at=20 > > > > >>>> /usr/src/sys/i386/i386/trap.c:489 > > > > >>>> #9 0xc079183b in calltrap () at /usr/src/sys/i386/i386/except= ion.s:146 > > > > >>>> #10 0xc04d2ab4 in scioctl (dev=3D0xc3b20d00, cmd=3D537163270, > > > > >>>> data=3D0xe6499c70 "\002", flag=3D1, td=3D0xc3d3c880) > > > > >>>> at /usr/src/sys/dev/syscons/syscons.c:1073 > > > > >>>> #11 0xc051ed1a in giant_ioctl (dev=3D0xc3b20d00, cmd=3D5371632= 70, > > > > >>>> data=3D0xe6499c70 "\002", fflag=3D1, td=3D0xc3d3c880) > > > > >>>> at /usr/src/sys/kern/kern_conf.c:349 > > > > >>>> #12 0xc0598194 in cnioctl (dev=3D0xc3b20d00, cmd=3D537163270, > > > > >>>> data=3D0xe6499c70 "\002", flag=3D1, td=3D0xc3d3c880) > > > > >>>> ---Type to continue, or q to quit--- > > > > >>>> at /usr/src/sys/kern/tty_cons.c:521 > > > > >>> Unless the virtual screen is opened, the screen state scr_stat = structure > > > > >>> is not allocated. The following patch would fix the panic, but = I do not > > > > >>> know how the console-kit would react to the ENXIO from the > > > > >>> VT_WAITACTIVE ioctl. Please, test it. > > > > >> Thanks! The patch works. > > > > >=20 > > > > > To clarify: do you see any problems with the console-kit after th= e patch ? > > > > > In particular, can you verify that the program functions correctl= y, esp. > > > > > on the virtual terminals 1, 2 ... , whatever this means ? > > > >=20 > > > > The panic is of course gone, while chatting a bit with Marcus (CCd)= it=20 > > > > looks like console-kit does not do any error handling at all. I've = not=20 > > > > looked at what c-k does so maybe Marcus can answer the question bet= ter. > > >=20 > > > It tries to install a wait thread on each available VT. That thread > > > sets the WAITACTIVE ioctl, and waits for its VT to become active. Wh= en > > > it does, it sets the CK active VT accordingly, and reattaches the wai= t. > > >=20 > > > When an error occurs in the ioctl, no wait is attached, and CK will n= ot > > > know when a particular VT becomes active. This will essentially crip= ple > > > CK (assuming the VT really does become available at a later point). = =20 > > >=20 > > > Now, admittedly, there is no error correction in CK for this situatio= n. > > > It would be trivial to add something that periodically attempts to > > > reestablish a failed wait. However, I am very curious why only a few > > > users are seeing this panic (me excluded on two different machines). = It > > > seems to me that the scp should be initialized when sc_attach_unit() = is > > > called during device probing. I don't see anything special in init(8= )'s > > > code that would cause these VT devices to become initialized. I would > > > assume that if one can open(2) them, then they should be available for > > > ioctls? > >=20 > > From my reading of the code, scp would be non-NULL after the first open > > of the corresponding /dev/ttyvX. sc_attach_unit() creates the scp for > > the console and the consolectl devices. > >=20 > > VT_WAITACTIVE ioctl is performed on arbitrary syscons /dev node, and > > can wait for any other screens, in particular, the screens that are > > not opened at the moment (the reason for the reported panic). >=20 > Right, and this is where I was confused. I had thought from an old > reading of the CK code that CK opened each ttyvX device to perform the > ioctl. It does not. Instead, it opens /dev/console, and performs the > ioctl for each ttyvX on that fd. That does explain the panic, but not > exactly why I did not see it. I'm guessing a race condition, but I > can't be sure. >=20 > >=20 > > The patch I posted may be improved by making the VT_WAITACTIVE ioctl > > to wait for the scp being allocated, and only then for the screen to be > > switched too. Please, test. >=20 > I really appreciate your attention to this. Funny thing is, CK 0.2.4 > was just released, and it is no longer started out of rc.d. I've also > added error correcting in the CK code path. The problem may disappear > depending on when CK is executed out of D-BUS. However, it would be > good to prevent this in the kernel. Pawel said he would try and test > this patch. This must be fixed in the kernel, at least because it allows any console user to panic the system. The question I have to you is what approach shall we use: - return the ENXIO (1) - do the wait for the open, then wait for the switch (2) I would prefer (1), both due to putting the decision to the userspace, and to not have the algorithm that could be implemented in userspace, in the kernel. On the other hand, as the maintainer of the one of the major API consumer there, you may have the different opinion, that is crusial. --4Vp5PwKxXEv3SO34 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEARECAAYFAkeYh6UACgkQC3+MBN1Mb4hRAgCgrVAlGCQhAYBf+4pXXnIJz7jo NDgAoJ3szwFlF6L5FJGmwB4j6NaZ/2uQ =CCls -----END PGP SIGNATURE----- --4Vp5PwKxXEv3SO34-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 13:12:24 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D310E16A418 for ; Thu, 24 Jan 2008 13:12:24 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by mx1.freebsd.org (Postfix) with ESMTP id 5FB4813C45D for ; Thu, 24 Jan 2008 13:12:23 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so249495fgg.35 for ; Thu, 24 Jan 2008 05:12:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=pqpGIfJ97k76+dCvY4TTEAadw8k8fziuBiAGUboKPx8=; b=qSVKW+SVvyca4jUSfTTjgXl3gY7r3yhP22RPMOAT1VpOunQ1rg4PPEFTAkR9MNEKIQEwTHCt3nBbbXt4yLNLY6D0Uke4sPjDV9zorhuU1+t1ivo2TBXA+qWGpPEuqlGkyoFUy9hRGk1XjN8omr5OnKy0YGuNi7TwRwmGp68iaZE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=HqEFz1BDtyFzgu4WKqRUtymeYoo5eJEw2VJH497w4hITQp8Ds8KlFDLYgCuRMpCdWHqkA/5YCpkAf7napLFfBoE49Kylga4HjUBn7JFRMJnA5m7326lDv95ZOJ3JA+A31V7dT5/IllmhJJcezOIVz39+ZZScMFbPEviXTiBED9M= Received: by 10.86.51.2 with SMTP id y2mr580405fgy.56.1201180342812; Thu, 24 Jan 2008 05:12:22 -0800 (PST) Received: by 10.86.99.17 with HTTP; Thu, 24 Jan 2008 05:12:22 -0800 (PST) Message-ID: <790a9fff0801240512m1a43fee6s12fcb164f4be1f7c@mail.gmail.com> Date: Thu, 24 Jan 2008 07:12:22 -0600 From: "Scot Hetzel" To: "Yar Tikhiy" In-Reply-To: <20080124122808.GA15600@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <790a9fff0801150552l542a4238ofc12efe5fdb45fc2@mail.gmail.com> <20080115143924.GB57756@deviant.kiev.zoral.com.ua> <20080124122808.GA15600@freefall.freebsd.org> Cc: Kostik Belousov , Attilio Rao , freebsd-current@freebsd.org Subject: Re: panic: System call lstat returning with 1 locks held X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 13:12:24 -0000 On Jan 24, 2008 6:28 AM, Yar Tikhiy wrote: > On Tue, Jan 15, 2008 at 04:39:24PM +0200, Kostik Belousov wrote: > > > > I think this could be related to the recent vn_lock()/VOP_LOCK() KPI changes. > > Please, add DEBUG_VFS_LOCKS to the kernel config, and do the > > show lockedvnods > > from the ddb prompt when the panic occurs. The witness does not track > > the lockmgr locks. > > I think I'm seeing the same panic on UFS. It's rather nasty: I > cannot rebuild CURRENT natively due to it so I have to build it > under 6-STABLE. My favourite way to trigger the panic reliably is > running `make install' in a simple port directory, e.g., portmaster, > but my system also panics during daily scripts run and, as already > said, if trying to build world. > Try backing the -CURRENT sources to "Jan 08 23:45 UTC 2008", and then rebuild/install the kernel. This is the point before the vn_lock/VOP_LOCK changes. Reboot your system and perform your steps that caused the lstat panic (this kernel shouldn't give the lstat panic). Create a backup of this kernel: cd /boot cp -rp kernel kernel_good Then try building/installing a kernel from the -CURRENT sources that have been updated to "Jan 08 23:49 UTC 2008". Reboot and try the same steps again, this kernel should give the lstat panic. After it panics, just reboot, break into the boot loader, then do: unload boot kernel_good Then either copy kernel_good to kernel or add the following to /boot/loader.conf: kernel="kernel_good" Scot From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 13:18:58 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 848B816A417 for ; Thu, 24 Jan 2008 13:18:58 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mx1.freebsd.org (Postfix) with ESMTP id 11B6213C46B for ; Thu, 24 Jan 2008 13:18:57 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so251591fgg.35 for ; Thu, 24 Jan 2008 05:18:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=h/aU4/fxnfTmVAORFA+9rxzgsJ+NO7NvuIrH0dkHgLE=; b=ERHQocDTHTCcaFnIefR9Aws+zjUYdUMxU/HAqrmVF/P4VXp21D1XbILsNdPHN0VbNo9GjpO3/2KkmwefcmC3h8rSjQKRJNhxS5AKuWBm/htrioxCjic2SvqHF7yM48owXwVrDuP3d5sWr51i5Tqhb84G2/CKMoNbvyV9UQPvdJ4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=E+3jAcWdoa8JxyVf0AGUx6ijq8AFjA42Jv1nVLglheortvX65UE4Z0fO2RRFdaB1y+KEnAocS4vdr38FsnIpp9aY/lPjcque7iHW+HiwQPxtKqjuPTZOXcCs8nZem6MiacJCaFKCP1FZUqV8X4Y7DTvGXZwcy1DTuKbs498d62k= Received: by 10.86.99.9 with SMTP id w9mr610390fgb.22.1201180736963; Thu, 24 Jan 2008 05:18:56 -0800 (PST) Received: by 10.86.53.7 with HTTP; Thu, 24 Jan 2008 05:18:56 -0800 (PST) Message-ID: <3bbf2fe10801240518i6e18b2f5w84de652d4170c95b@mail.gmail.com> Date: Thu, 24 Jan 2008 14:18:56 +0100 From: "Attilio Rao" Sender: asmrookie@gmail.com To: "Yar Tikhiy" In-Reply-To: <20080124122808.GA15600@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <790a9fff0801150552l542a4238ofc12efe5fdb45fc2@mail.gmail.com> <20080115143924.GB57756@deviant.kiev.zoral.com.ua> <20080124122808.GA15600@freefall.freebsd.org> X-Google-Sender-Auth: 95af06cbb3fa0c88 Cc: Kostik Belousov , freebsd-current@freebsd.org Subject: Re: panic: System call lstat returning with 1 locks held X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 13:18:58 -0000 2008/1/24, Yar Tikhiy : > On Tue, Jan 15, 2008 at 04:39:24PM +0200, Kostik Belousov wrote: > > > > I think this could be related to the recent vn_lock()/VOP_LOCK() KPI changes. > > Please, add DEBUG_VFS_LOCKS to the kernel config, and do the > > show lockedvnods > > from the ddb prompt when the panic occurs. The witness does not track > > the lockmgr locks. > > I think I'm seeing the same panic on UFS. It's rather nasty: I > cannot rebuild CURRENT natively due to it so I have to build it > under 6-STABLE. My favourite way to trigger the panic reliably is > running `make install' in a simple port directory, e.g., portmaster, > but my system also panics during daily scripts run and, as already > said, if trying to build world. Yar, as it seems reproducible for you, can you please add this patch to the tree: http://www.freebsd.org/~attilio/debug_tdlocks.diff compile your kernel with: options KTR options KTR_COMPILE=(KTR_SPARE2) options KTR_MASK=(KTR_SPARE2) options KTR_ENTRIES=32768 and once kernel panics, at ddb prompts do: > show ktr Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 13:28:36 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C62A916A417 for ; Thu, 24 Jan 2008 13:28:36 +0000 (UTC) (envelope-from gahr@gahr.ch) Received: from cpanel03.rubas-s03.net (cpanel03.rubas-s03.net [195.182.222.73]) by mx1.freebsd.org (Postfix) with ESMTP id 5AA9113C4FA for ; Thu, 24 Jan 2008 13:28:36 +0000 (UTC) (envelope-from gahr@gahr.ch) Received: from 80-218-191-236.dclient.hispeed.ch ([80.218.191.236] helo=gahrtop.localhost) by cpanel03.rubas-s03.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1JI28B-00031T-IC for freebsd-current@freebsd.org; Thu, 24 Jan 2008 14:28:35 +0100 Message-ID: <47989278.6050802@gahr.ch> Date: Thu, 24 Jan 2008 14:28:24 +0100 From: Pietro Cerutti User-Agent: Thunderbird 2.0.0.9 (X11/20071121) MIME-Version: 1.0 To: freebsd-current X-Enigmail-Version: 0.95.5 OpenPGP: id=9571F78E; url=http://www.gahr.ch/pgp Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enigBE811D1FE021F15724DDD0ED" X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cpanel03.rubas-s03.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - gahr.ch X-Source: X-Source-Args: X-Source-Dir: Subject: [Fwd: SMP in machine/params.h] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 13:28:36 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigBE811D1FE021F15724DDD0ED Content-Type: multipart/mixed; boundary="------------010909030109070303020500" This is a multi-part message in MIME format. --------------010909030109070303020500 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable -------- Original Message -------- Subject: SMP in machine/params.h Date: Thu, 24 Jan 2008 13:38:39 +0100 From: Pietro Cerutti To: freebsd-hackers@freebsd.org Hello, I'm running a Core2Duo on CURRENT, SMP kernel, but somehow the macro SMP in machine/param.h 1.81 2006/01/09 line 68 is not defined, thus MAXCPU is defined to 1. Any idea why? > uname -a FreeBSD gahrtop.localhost 8.0-CURRENT FreeBSD 8.0-CURRENT #23: Tue Jan 22 00:15:05 CET 2008 root@gahrtop.localhost:/usr/obj/usr/src/sys/MSI1034 i386 > sysctl kern.smp.active kern.smp.maxcpus kern.smp.active: 1 kern.smp.maxcpus: 16 > cat smp.c #include #ifndef SMP # error SMP not defined #endif > make smp cc -O2 -pipe -march=3Dpentiumpro smp.c -o smp smp.c:5:3: error: #error SMP not defined *** Error code 1 > cat maxcpu.c #include #include int main(void) { return (MAXCPU); } > ./maxcpu; echo $? 1 Any idea? --=20 Pietro Cerutti PGP Public Key: http://gahr.ch/pgp --=20 Pietro Cerutti PGP Public Key: http://gahr.ch/pgp --------------010909030109070303020500 Content-Type: application/pgp-signature; name="signature.asc" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="signature.asc" LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KVmVyc2lvbjogR251UEcgdjEuNC43IChG cmVlQlNEKQoKaUQ4REJRRkhtSWJYd01KcW1KVng5NDRSQ29FZkFKOTNPUU90V3dqM3NOQlNC N2E0NTdmaWlBZ0o5QUNncDhzQwpsL3VJNnlORUduaURTVWVlV0lWdnZzUT0KPU1SSHcKLS0t LS1FTkQgUEdQIFNJR05BVFVSRS0tLS0tCgo= --------------010909030109070303020500-- --------------enigBE811D1FE021F15724DDD0ED Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHmJJ8wMJqmJVx944RCk2EAJ44N0J7GLkAHkU/ECbsPs/MHUAPeACfR1C4 p9SlaCKD4E5cI6WKgkv5+cc= =AaOJ -----END PGP SIGNATURE----- --------------enigBE811D1FE021F15724DDD0ED-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 13:38:15 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 036B116A417; Thu, 24 Jan 2008 13:38:15 +0000 (UTC) (envelope-from gahr@gahr.ch) Received: from cpanel03.rubas-s03.net (cpanel03.rubas-s03.net [195.182.222.73]) by mx1.freebsd.org (Postfix) with ESMTP id 8B6CA13C455; Thu, 24 Jan 2008 13:38:14 +0000 (UTC) (envelope-from gahr@gahr.ch) Received: from 80-218-191-236.dclient.hispeed.ch ([80.218.191.236] helo=gahrtop.localhost) by cpanel03.rubas-s03.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1JI2HV-0004v3-JH; Thu, 24 Jan 2008 14:38:13 +0100 Message-ID: <479894BA.2010403@gahr.ch> Date: Thu, 24 Jan 2008 14:38:02 +0100 From: Pietro Cerutti User-Agent: Thunderbird 2.0.0.9 (X11/20071121) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-current References: <479886CF.7040506@gahr.ch> In-Reply-To: <479886CF.7040506@gahr.ch> X-Enigmail-Version: 0.95.5 OpenPGP: id=9571F78E; url=http://www.gahr.ch/pgp Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enig95A38527E4CA9E8B469F7535" X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cpanel03.rubas-s03.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - gahr.ch X-Source: X-Source-Args: X-Source-Dir: Cc: Subject: Re: SMP in machine/params.h X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 13:38:15 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig95A38527E4CA9E8B469F7535 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Some more interesting findings in this field lead me to another related question: what is the relation between kern.smp.cpus, kern.smp.active and kern.smp.maxcpus? To my understanding, it should be: If the machine has more than one CPU, and SMP and apic are enabled in the config file, then kern.smp.cpus =3D nof cpus in the system kern.smp.active =3D 1 kern.smp.maxcpus =3D 16 else kern.smp.cpus =3D 1 kern.smp.active =3D 0 kern.smp.maxcpus =3D 1 This is the expected result, and also the result I get from my single CPU Pentium 3, running 6.3-RELEASE: kern.smp.cpus: 1 kern.smp.active: 0 kern.smp.maxcpus: 1 =46rom my single CPU sparc64, running 7.0-PRERELEASE, I get: kern.smp.cpus: 1 kern.smp.active: 0 kern.smp.maxcpus: 16 <-- why not 1?? =46rom my Core2Due, running 8.0-CURRENT, I get: kern.smp.cpus: 2 kern.smp.active: 1 kern.smp.maxcpus: 16 which is OK, but nevertheless SMP is not defined in sys/param.h (see previous posts). Thanks for any insight, --=20 Pietro Cerutti PGP Public Key: http://gahr.ch/pgp --------------enig95A38527E4CA9E8B469F7535 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHmJS+wMJqmJVx944RCjAZAJ9QE5o4sP8ZwwoIthm4HGYyC7iBnQCgj/uv wVIiPcIXFv2u2f43VagTuE8= =lvQt -----END PGP SIGNATURE----- --------------enig95A38527E4CA9E8B469F7535-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 13:45:36 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 654DD16A474 for ; Thu, 24 Jan 2008 13:45:36 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 2974313C474 for ; Thu, 24 Jan 2008 13:45:35 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id BCA5E2084; Thu, 24 Jan 2008 14:45:26 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id AF7EA2082; Thu, 24 Jan 2008 14:45:26 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id 91C56844AF; Thu, 24 Jan 2008 14:45:26 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Pietro Cerutti References: <47989278.6050802@gahr.ch> Date: Thu, 24 Jan 2008 14:45:26 +0100 In-Reply-To: <47989278.6050802@gahr.ch> (Pietro Cerutti's message of "Thu\, 24 Jan 2008 14\:28\:24 +0100") Message-ID: <86hch3uykp.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current Subject: Re: SMP in machine/params.h X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 13:45:36 -0000 Pietro Cerutti writes: > I'm running a Core2Duo on CURRENT, SMP kernel, but somehow the macro SMP > in machine/param.h 1.81 2006/01/09 line 68 is not defined, thus MAXCPU > is defined to 1. Any idea why? You didn't specify it in your kernel config. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 13:45:50 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0439C16A494 for ; Thu, 24 Jan 2008 13:45:50 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id B308913C46A for ; Thu, 24 Jan 2008 13:45:49 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JI2Ol-0005FN-4E for freebsd-current@freebsd.org; Thu, 24 Jan 2008 13:45:43 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 24 Jan 2008 13:45:43 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 24 Jan 2008 13:45:43 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Thu, 24 Jan 2008 14:45:36 +0100 Lines: 40 Message-ID: References: <479886CF.7040506@gahr.ch> <479894BA.2010403@gahr.ch> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigC8D75864FCF47486FD70E502" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.6 (X11/20071022) In-Reply-To: <479894BA.2010403@gahr.ch> X-Enigmail-Version: 0.95.0 Sender: news Cc: freebsd-hackers@freebsd.org Subject: Re: SMP in machine/params.h X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 13:45:50 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC8D75864FCF47486FD70E502 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Pietro Cerutti wrote: > This is the expected result, and also the result I get from my single > CPU Pentium 3, running 6.3-RELEASE: >=20 > kern.smp.cpus: 1 > kern.smp.active: 0 > kern.smp.maxcpus: 1 >=20 > From my single CPU sparc64, running 7.0-PRERELEASE, I get: >=20 > kern.smp.cpus: 1 > kern.smp.active: 0 > kern.smp.maxcpus: 16 <-- why not 1?? maxcpus is the maximum number of CPUs supported by the kernel. I.e. if the kernel is UP, maxcpus is 1, if the kernel is SMP, maxcpus is 16. This means (though you probably won't care) that if you have a 32-CPU machine, ony 16 of them will be used by the SMP kernel. --------------enigC8D75864FCF47486FD70E502 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHmJaAldnAQVacBcgRAlBkAKCXEg8EbCCtyFUCfkNyNZak7mxPEACg6rzf u6+OMQJ5AWqXQT5KrLXDRac= =L4JJ -----END PGP SIGNATURE----- --------------enigC8D75864FCF47486FD70E502-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 13:51:56 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AFA0E16A41A; Thu, 24 Jan 2008 13:51:56 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from mx-out-05.forthnet.gr (mx-out.forthnet.gr [193.92.150.104]) by mx1.freebsd.org (Postfix) with ESMTP id 2B29413C442; Thu, 24 Jan 2008 13:51:55 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from mx-av-03.forthnet.gr (mx-av.forthnet.gr [193.92.150.27]) by mx-out-05.forthnet.gr (8.13.8/8.13.8) with ESMTP id m0ODbGT2013245; Thu, 24 Jan 2008 15:37:16 +0200 Received: from MX-IN-04.forthnet.gr (mx-in-04.forthnet.gr [193.92.150.163]) by mx-av-03.forthnet.gr (8.14.1/8.14.1) with ESMTP id m0ODbGId025893; Thu, 24 Jan 2008 15:37:16 +0200 Received: from kobe.laptop (ppp133-151.adsl.forthnet.gr [62.1.124.151]) by MX-IN-04.forthnet.gr (8.14.2/8.14.2) with ESMTP id m0ODbAGd030953; Thu, 24 Jan 2008 15:37:12 +0200 Authentication-Results: MX-IN-04.forthnet.gr smtp.mail=keramida@freebsd.org; spf=permerror Authentication-Results: MX-IN-04.forthnet.gr header.from=keramida@freebsd.org; sender-id=permerror Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.2/8.14.2) with ESMTP id m0ODbA4g002266; Thu, 24 Jan 2008 15:37:10 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by kobe.laptop (8.14.2/8.14.2/Submit) id m0ODb98P002265; Thu, 24 Jan 2008 15:37:09 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Thu, 24 Jan 2008 15:37:09 +0200 From: Giorgos Keramidas To: Christos Zoulas , Mark Peek , tcsh-bugs@mx.gw.com, current@freebsd.org Message-ID: <20080124133708.GA2220@kobe.laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Cc: Subject: `set autologout = (15 1)' aborts X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 13:51:56 -0000 Hi Christos, Mark and everyone, The following is a patch which fixes an abort() in tcsh 6.15.00 on FreeBSD. The proposed commit log explains why the change is needed, so if we can get this committed upstream to the tcsh sources, then it will find its way back to FreeBSD's src/contrib :) %%% tcsh: fix abort in cleanup_until(), caused by internal xgetpass() The xgetpass() function pushes a cleanup entry for &osa, but then attempts to flush the stack until an entry matching &sa. The two object pointers do not match, so the stack is popped too much, and then cleanup_until calls abort() when it unexpectedly hits the bottom of the cleanup stack. Reported by: Paul B. Mahol, onemda at gmail.com, Pietro Cerutti, gahr at gahr.ch diff -r 2cc0e20ca15b -r ea3fdd703cbf contrib/tcsh/tc.func.c --- a/contrib/tcsh/tc.func.c Wed Jan 23 11:47:09 2008 +0000 +++ b/contrib/tcsh/tc.func.c Thu Jan 24 15:33:31 2008 +0200 @@ -632,7 +632,7 @@ } strbuf_terminate(&pass); - cleanup_until(&sa); + cleanup_until(&osa); return pass.s; } %%% From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 14:58:15 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A733C16A41B for ; Thu, 24 Jan 2008 14:58:15 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.freebsd.org (Postfix) with ESMTP id EFC9F13C4D1 for ; Thu, 24 Jan 2008 14:58:14 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.4) with ESMTP id m0OEwCcp090735; Thu, 24 Jan 2008 17:58:12 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.4/Submit) id m0OEwBe6090732; Thu, 24 Jan 2008 17:58:12 +0300 (MSK) (envelope-from yar) Date: Thu, 24 Jan 2008 17:58:11 +0300 From: Yar Tikhiy To: Attilio Rao Message-ID: <20080124145811.GB78114@comp.chem.msu.su> References: <790a9fff0801150552l542a4238ofc12efe5fdb45fc2@mail.gmail.com> <20080115143924.GB57756@deviant.kiev.zoral.com.ua> <20080124122808.GA15600@freefall.freebsd.org> <3bbf2fe10801240518i6e18b2f5w84de652d4170c95b@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3bbf2fe10801240518i6e18b2f5w84de652d4170c95b@mail.gmail.com> User-Agent: Mutt/1.5.9i Cc: Kostik Belousov , freebsd-current@freebsd.org Subject: Re: panic: System call lstat returning with 1 locks held X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 14:58:15 -0000 On Thu, Jan 24, 2008 at 02:18:56PM +0100, Attilio Rao wrote: > 2008/1/24, Yar Tikhiy : > > On Tue, Jan 15, 2008 at 04:39:24PM +0200, Kostik Belousov wrote: > > > > > > I think this could be related to the recent vn_lock()/VOP_LOCK() KPI changes. > > > Please, add DEBUG_VFS_LOCKS to the kernel config, and do the > > > show lockedvnods > > > from the ddb prompt when the panic occurs. The witness does not track > > > the lockmgr locks. > > > > I think I'm seeing the same panic on UFS. It's rather nasty: I > > cannot rebuild CURRENT natively due to it so I have to build it > > under 6-STABLE. My favourite way to trigger the panic reliably is > > running `make install' in a simple port directory, e.g., portmaster, > > but my system also panics during daily scripts run and, as already > > said, if trying to build world. > > Yar, > as it seems reproducible for you, can you please add this patch to the tree: > http://www.freebsd.org/~attilio/debug_tdlocks.diff > > compile your kernel with: > options KTR > options KTR_COMPILE=(KTR_SPARE2) > options KTR_MASK=(KTR_SPARE2) > options KTR_ENTRIES=32768 > > and once kernel panics, at ddb prompts do: > > show ktr Thank you for your instant response! The patched kernel is already being built, but I've got the following question in the meanwhile: Should I have updated my kernel to get your latest changes to kern_lock.c? Now my local copy of kern_lock.c is at rev. 1.119, i.e., 1 revision behind today's change. -- Yar From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 15:07:45 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE77D16A41A for ; Thu, 24 Jan 2008 15:07:44 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.152]) by mx1.freebsd.org (Postfix) with ESMTP id 7D32B13C459 for ; Thu, 24 Jan 2008 15:07:44 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so284280fgg.35 for ; Thu, 24 Jan 2008 07:07:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=aAAO5OVVSD7Ytul9GAfwvmQfNIwmWsqj4XU4uLjfqIU=; b=hRJ+G15ayHhA/UJ3qYxG4mOi7whXJgLl3nBhtPGKRBKc8gTVBIE44bkDdNGD3oxRiKfSqF0HoUzLYgF6TwHR37bgXBoq5UAXJx+f5tQVgUXgh2Qzl3ua/CloDzuCdHUsdmbDte3tPQ0AQrRGJRJGRG2dHloHwXscmMbdIcZ7cHo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=ZZqpJoXrGm+u7xhqKLK1FDXB9Zf8EOWWQnv2t7FwdTAAt5Z2lk9fZZJLMqdR8HAInzk42szdBpvxg9ms+imt3T+aqFanTQBP8KVSGHoZ4r65EGkEGFoqe1nhgB7YMp2kd99xCwzStJ6xyKHEpt1cEQE61P5g9Ibl0oUkuzmnWO0= Received: by 10.86.58.3 with SMTP id g3mr719374fga.1.1201187263337; Thu, 24 Jan 2008 07:07:43 -0800 (PST) Received: by 10.86.53.7 with HTTP; Thu, 24 Jan 2008 07:07:43 -0800 (PST) Message-ID: <3bbf2fe10801240707o72b927cg74dbf9b7bbcd88fc@mail.gmail.com> Date: Thu, 24 Jan 2008 16:07:43 +0100 From: "Attilio Rao" Sender: asmrookie@gmail.com To: "Yar Tikhiy" In-Reply-To: <20080124145811.GB78114@comp.chem.msu.su> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <790a9fff0801150552l542a4238ofc12efe5fdb45fc2@mail.gmail.com> <20080115143924.GB57756@deviant.kiev.zoral.com.ua> <20080124122808.GA15600@freefall.freebsd.org> <3bbf2fe10801240518i6e18b2f5w84de652d4170c95b@mail.gmail.com> <20080124145811.GB78114@comp.chem.msu.su> X-Google-Sender-Auth: b78dd12f67775387 Cc: Kostik Belousov , freebsd-current@freebsd.org Subject: Re: panic: System call lstat returning with 1 locks held X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 15:07:45 -0000 2008/1/24, Yar Tikhiy : > On Thu, Jan 24, 2008 at 02:18:56PM +0100, Attilio Rao wrote: > > 2008/1/24, Yar Tikhiy : > > > On Tue, Jan 15, 2008 at 04:39:24PM +0200, Kostik Belousov wrote: > > > > > > > > I think this could be related to the recent vn_lock()/VOP_LOCK() KPI changes. > > > > Please, add DEBUG_VFS_LOCKS to the kernel config, and do the > > > > show lockedvnods > > > > from the ddb prompt when the panic occurs. The witness does not track > > > > the lockmgr locks. > > > > > > I think I'm seeing the same panic on UFS. It's rather nasty: I > > > cannot rebuild CURRENT natively due to it so I have to build it > > > under 6-STABLE. My favourite way to trigger the panic reliably is > > > running `make install' in a simple port directory, e.g., portmaster, > > > but my system also panics during daily scripts run and, as already > > > said, if trying to build world. > > > > Yar, > > as it seems reproducible for you, can you please add this patch to the tree: > > http://www.freebsd.org/~attilio/debug_tdlocks.diff > > > > compile your kernel with: > > options KTR > > options KTR_COMPILE=(KTR_SPARE2) > > options KTR_MASK=(KTR_SPARE2) > > options KTR_ENTRIES=32768 > > > > and once kernel panics, at ddb prompts do: > > > show ktr > > Thank you for your instant response! > > The patched kernel is already being built, but I've got the following > question in the meanwhile: Should I have updated my kernel to get your > latest changes to kern_lock.c? Now my local copy of kern_lock.c is at > rev. 1.119, i.e., 1 revision behind today's change. As long as this patch still applies, it should not any meaningful difference. Thanks a lot for your effort of testing and reporting bugs! Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 15:21:03 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8668116A417 for ; Thu, 24 Jan 2008 15:21:03 +0000 (UTC) (envelope-from marcus@FreeBSD.org) Received: from creme-brulee.marcuscom.com (marcuscom-pt.tunnel.tserv1.fmt.ipv6.he.net [IPv6:2001:470:1f00:ffff::1279]) by mx1.freebsd.org (Postfix) with ESMTP id 28FB713C459 for ; Thu, 24 Jan 2008 15:21:03 +0000 (UTC) (envelope-from marcus@FreeBSD.org) Received: from [IPv6:2001:470:1f00:2464::4] (shumai.marcuscom.com [IPv6:2001:470:1f00:2464::4]) by creme-brulee.marcuscom.com (8.14.2/8.14.2) with ESMTP id m0OFMxnb042070; Thu, 24 Jan 2008 10:22:59 -0500 (EST) (envelope-from marcus@FreeBSD.org) From: Joe Marcus Clarke To: Kostik Belousov In-Reply-To: <20080124124213.GD57756@deviant.kiev.zoral.com.ua> References: <4792C32C.5010205@gmail.com> <20080122133835.GT57756@deviant.kiev.zoral.com.ua> <4796356D.9080809@gmail.com> <20080123051648.GV57756@deviant.kiev.zoral.com.ua> <479796E1.4000500@gmail.com> <1201118159.38742.17.camel@shumai.marcuscom.com> <20080123211149.GA57756@deviant.kiev.zoral.com.ua> <1201123933.62127.9.camel@shumai.marcuscom.com> <20080124124213.GD57756@deviant.kiev.zoral.com.ua> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-MG3FTPiDJWmrIKzquvlA" Organization: FreeBSD, Inc. Date: Thu, 24 Jan 2008 10:21:02 -0500 Message-Id: <1201188062.24613.1.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 FreeBSD GNOME Team Port X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on creme-brulee.marcuscom.com Cc: FreeBSD Current Subject: Re: page fault panic in scioctl and console-kit-daemon X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 15:21:03 -0000 --=-MG3FTPiDJWmrIKzquvlA Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2008-01-24 at 14:42 +0200, Kostik Belousov wrote: > On Wed, Jan 23, 2008 at 04:32:13PM -0500, Joe Marcus Clarke wrote: > >=20 > > On Wed, 2008-01-23 at 23:11 +0200, Kostik Belousov wrote: > > > On Wed, Jan 23, 2008 at 02:55:59PM -0500, Joe Marcus Clarke wrote: > > > >=20 > > > > On Wed, 2008-01-23 at 20:34 +0100, Pawel Worach wrote: > > > > > Kostik Belousov wrote: > > > > > > On Tue, Jan 22, 2008 at 07:26:53PM +0100, Pawel Worach wrote: > > > > > >> Kostik Belousov wrote: > > > > > >>> On Sun, Jan 20, 2008 at 04:42:36AM +0100, Pawel Worach wrote: > > > > > >>>> Hi, > > > > > >>>> > > > > > >>>> While starting console-kit-daemon (sysutils/consolekit 0.2.3= ) during=20 > > > > > >>>> boot or in single-user mode the system panics. If I start it= post-boot=20 > > > > > >>>> it runs fine. This is on 8.0-CURRENT from about 12 hours ago= , another=20 > > > > > >>>> user also reported the same on RELENG_7. Any other informati= on I can=20 > > > > > >>>> provide ? > > > > > >>>> > > > > > >>>> Fatal trap 12: page fault while in kernel mode > > > > > >>>> fault virtual address =3D 0x4 > > > > > >>>> fault code =3D supervisor read, page not present > > > > > >>>> instruction pointer =3D 0x20:0xc04d2ab4 > > > > > >>>> stack pointer =3D 0x28:0xe6499b18 > > > > > >>>> frame pointer =3D 0x28:0xe6499b80 > > > > > >>>> code segment =3D base 0x0, limit 0xfffff, type 0x1b > > > > > >>>> =3D DPL 0, pres 1, def32 1, gran 1 > > > > > >>>> processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > > > > > >>>> current process =3D 134 (console-kit-daemon) > > > > > >>>> Physical memory: 1014 MB > > > > > >>>> Dumping 43 MB: 28 12 > > > > > >>>> > > > > > >>>> #8 0xc07a34a2 in trap (frame=3D0xe6499ad8) at=20 > > > > > >>>> /usr/src/sys/i386/i386/trap.c:489 > > > > > >>>> #9 0xc079183b in calltrap () at /usr/src/sys/i386/i386/exce= ption.s:146 > > > > > >>>> #10 0xc04d2ab4 in scioctl (dev=3D0xc3b20d00, cmd=3D537163270= , > > > > > >>>> data=3D0xe6499c70 "\002", flag=3D1, td=3D0xc3d3c880) > > > > > >>>> at /usr/src/sys/dev/syscons/syscons.c:1073 > > > > > >>>> #11 0xc051ed1a in giant_ioctl (dev=3D0xc3b20d00, cmd=3D53716= 3270, > > > > > >>>> data=3D0xe6499c70 "\002", fflag=3D1, td=3D0xc3d3c880) > > > > > >>>> at /usr/src/sys/kern/kern_conf.c:349 > > > > > >>>> #12 0xc0598194 in cnioctl (dev=3D0xc3b20d00, cmd=3D537163270= , > > > > > >>>> data=3D0xe6499c70 "\002", flag=3D1, td=3D0xc3d3c880) > > > > > >>>> ---Type to continue, or q to quit--- > > > > > >>>> at /usr/src/sys/kern/tty_cons.c:521 > > > > > >>> Unless the virtual screen is opened, the screen state scr_sta= t structure > > > > > >>> is not allocated. The following patch would fix the panic, bu= t I do not > > > > > >>> know how the console-kit would react to the ENXIO from the > > > > > >>> VT_WAITACTIVE ioctl. Please, test it. > > > > > >> Thanks! The patch works. > > > > > >=20 > > > > > > To clarify: do you see any problems with the console-kit after = the patch ? > > > > > > In particular, can you verify that the program functions correc= tly, esp. > > > > > > on the virtual terminals 1, 2 ... , whatever this means ? > > > > >=20 > > > > > The panic is of course gone, while chatting a bit with Marcus (CC= d) it=20 > > > > > looks like console-kit does not do any error handling at all. I'v= e not=20 > > > > > looked at what c-k does so maybe Marcus can answer the question b= etter. > > > >=20 > > > > It tries to install a wait thread on each available VT. That threa= d > > > > sets the WAITACTIVE ioctl, and waits for its VT to become active. = When > > > > it does, it sets the CK active VT accordingly, and reattaches the w= ait. > > > >=20 > > > > When an error occurs in the ioctl, no wait is attached, and CK will= not > > > > know when a particular VT becomes active. This will essentially cr= ipple > > > > CK (assuming the VT really does become available at a later point).= =20 > > > >=20 > > > > Now, admittedly, there is no error correction in CK for this situat= ion. > > > > It would be trivial to add something that periodically attempts to > > > > reestablish a failed wait. However, I am very curious why only a f= ew > > > > users are seeing this panic (me excluded on two different machines)= . It > > > > seems to me that the scp should be initialized when sc_attach_unit(= ) is > > > > called during device probing. I don't see anything special in init= (8)'s > > > > code that would cause these VT devices to become initialized. I wo= uld > > > > assume that if one can open(2) them, then they should be available = for > > > > ioctls? > > >=20 > > > From my reading of the code, scp would be non-NULL after the first op= en > > > of the corresponding /dev/ttyvX. sc_attach_unit() creates the scp for > > > the console and the consolectl devices. > > >=20 > > > VT_WAITACTIVE ioctl is performed on arbitrary syscons /dev node, and > > > can wait for any other screens, in particular, the screens that are > > > not opened at the moment (the reason for the reported panic). > >=20 > > Right, and this is where I was confused. I had thought from an old > > reading of the CK code that CK opened each ttyvX device to perform the > > ioctl. It does not. Instead, it opens /dev/console, and performs the > > ioctl for each ttyvX on that fd. That does explain the panic, but not > > exactly why I did not see it. I'm guessing a race condition, but I > > can't be sure. > >=20 > > >=20 > > > The patch I posted may be improved by making the VT_WAITACTIVE ioctl > > > to wait for the scp being allocated, and only then for the screen to = be > > > switched too. Please, test. > >=20 > > I really appreciate your attention to this. Funny thing is, CK 0.2.4 > > was just released, and it is no longer started out of rc.d. I've also > > added error correcting in the CK code path. The problem may disappear > > depending on when CK is executed out of D-BUS. However, it would be > > good to prevent this in the kernel. Pawel said he would try and test > > this patch. >=20 > This must be fixed in the kernel, at least because it allows any console > user to panic the system. The question I have to you is what approach sha= ll > we use: Fully agree. > - return the ENXIO (1) > - do the wait for the open, then wait for the switch (2) >=20 > I would prefer (1), both due to putting the decision to the userspace, an= d > to not have the algorithm that could be implemented in userspace, in the > kernel. On the other hand, as the maintainer of the one of the major API > consumer there, you may have the different opinion, that is crusial. I've already added code to CK to handle ENXIO (or any error) in userspace, so I'm okay with option 1. Joe --=20 Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome --=-MG3FTPiDJWmrIKzquvlA Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEABECAAYFAkeYrN0ACgkQb2iPiv4Uz4cGnwCcDhSsKg2TdNDO4MabQMPTbW4G 09YAni7ZkbDxKPmik9Vju7X7FrTviOR2 =wXHU -----END PGP SIGNATURE----- --=-MG3FTPiDJWmrIKzquvlA-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 16:01:29 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 245D716A418 for ; Thu, 24 Jan 2008 16:01:29 +0000 (UTC) (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 D26C413C4E7 for ; Thu, 24 Jan 2008 16:01:28 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m0OG1LP7074698; Thu, 24 Jan 2008 09:01:22 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4798B651.7000108@samsco.org> Date: Thu, 24 Jan 2008 09:01:21 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.11) Gecko/20071128 SeaMonkey/1.1.7 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <4797B923.6030400@gmail.com> <86odbbwo02.fsf@ds4.des.no> In-Reply-To: <86odbbwo02.fsf@ds4.des.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Thu, 24 Jan 2008 09:01:22 -0700 (MST) X-Spam-Status: No, score=-1.4 required=5.4 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: EchoB , freebsd-current@freebsd.org Subject: Re: XEN and ZFS Status? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 16:01:29 -0000 Dag-Erling Smørgrav wrote: > EchoB writes: >> Hi all :) Can anyone point me in the direction of any detailed docs or >> perhaps just an answer on here re: production status of Xen and ZFS >> when 7.0 is released? I have read somewhere that ZFS is experimental >> at best, and wanted to confirm that. Also, using Xen would be a great >> plus in a production environment. > > I use ZFS in production. > > Xen is currently not supported at all, AFAIK. > Would it be possible to have any more completely uninformed opinions on Xen by people completely out of the loop on its development? Scott From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 15:50:01 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5359616A41A for ; Thu, 24 Jan 2008 15:50:01 +0000 (UTC) (envelope-from bruce@zuhause.org) Received: from mail.zuhause.org (216.243.156.193.real-time.com [216.243.156.193]) by mx1.freebsd.org (Postfix) with ESMTP id 2ADAD13C455 for ; Thu, 24 Jan 2008 15:50:01 +0000 (UTC) (envelope-from bruce@zuhause.org) Received: by mail.zuhause.org (Postfix, from userid 1001) id D65BD7C04; Thu, 24 Jan 2008 09:38:10 -0600 (CST) From: Bruce Albrecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18328.45282.562906.708945@celery.zuhause.org> Date: Thu, 24 Jan 2008 09:38:10 -0600 To: freebsd-current@freebsd.org X-Mailer: VM 7.15 under 21.4 (patch 12) "Portable Code" XEmacs Lucid X-Mailman-Approved-At: Thu, 24 Jan 2008 17:08:42 +0000 Subject: Weird performance behaviour in 7.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: Thu, 24 Jan 2008 15:50:01 -0000 This is my first Q6600 based system, and my first 7.0 system, and my first AMD-64 system and my first ZFS base system, and I'm seeing something really strange. Every now and then, processes run really slowly, like at 1/600th (or worse) than it ought to, but it racks up the CPU time as though it's running full tilt. For example, I have this little test program that just does a tight loop, and most times, it takes about 3 seconds to complete, but right now, it's taking about 2000 seconds to complete. Right now, it's consistently running slow, but sometimes it will run slow, but I can terminate it and start another one which will run at normal speed. Currently sysctl reports: dev.cpu.0.freq: 2400 dev.cpu.0.temperature: 55 dev.cpu.1.temperature: 57 dev.cpu.2.temperature: 51 dev.cpu.3.temperature: 54 What might be causing this? What information is pertinent for inclusion in a problem report? From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 17:38:20 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C22816A419 for ; Thu, 24 Jan 2008 17:38:20 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id D1F7913C46B for ; Thu, 24 Jan 2008 17:38:19 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id B326E2083; Thu, 24 Jan 2008 18:38:11 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 3A36C2049; Thu, 24 Jan 2008 18:38:11 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id 0E5F6844AF; Thu, 24 Jan 2008 18:38:11 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Scott Long References: <4797B923.6030400@gmail.com> <86odbbwo02.fsf@ds4.des.no> <4798B651.7000108@samsco.org> Date: Thu, 24 Jan 2008 18:38:10 +0100 In-Reply-To: <4798B651.7000108@samsco.org> (Scott Long's message of "Thu\, 24 Jan 2008 09\:01\:21 -0700") Message-ID: <868x2f86pp.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: EchoB , freebsd-current@freebsd.org Subject: Re: XEN and ZFS Status? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 17:38:20 -0000 Scott Long writes: > Dag-Erling Sm=C3=B8rgrav writes: > > Xen is currently not supported at all, AFAIK. > Would it be possible to have any more completely uninformed opinions on > Xen by people completely out of the loop on its development? Scott, wtf is wrong with you? You've been acting like an ass both on and off the lists lately. In any case, I stand by what I wrote - Xen is not supported at all in FreeBSD 7, nor in 8 for that matter. What is or isn't available in Perforce is completely irrelevant to the OP. You (assuming you are involved in Xen development) really don't make it easy, BTW - the wiki page contains epsilon information, and the status reports none at all. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 17:39:03 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59E4F16A41A for ; Thu, 24 Jan 2008 17:39:03 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.freebsd.org (Postfix) with ESMTP id DBC2813C458 for ; Thu, 24 Jan 2008 17:39:02 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so48271nfb.33 for ; Thu, 24 Jan 2008 09:39:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:reply-to:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; bh=m+4dFdEbCHPYe134AXv5Sj3fRjuI9i2kLGMLDQRt8oQ=; b=tfL/xfgqBRrg+H1VRjH0BWA0PNxcUHqpBdeR97/03NP109dRlormnU+naoaHO2fH54TJMkh9PfMlcnJeFLA8Fm6UyDuthc/MIg7Lt7RgkSD5BOk4aB7DOSVGOD2LhLTqP/sgGfaCsDDRhUjTv99yt59lj7eRXhREJMB6qQkOZ+8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=iwPJjDZ6eLuOtBQlOJSpGF9tvobO7+whlRu8mWZAPPVtZqE2sQ1aIWUC/Fk2hB7AEf1JkmO5qP4nhCTyc2CHacdNlEozzD6QU4i1pl+m3jQ/mk367kHRrhl33MB4GjGxeNK61SMYUNRAqvq52NHk2c7+QDrTy4hveb4n050T+bM= Received: by 10.78.134.2 with SMTP id h2mr1298858hud.77.1201196341277; Thu, 24 Jan 2008 09:39:01 -0800 (PST) Received: from ?192.168.1.11? ( [89.162.141.1]) by mx.google.com with ESMTPS id h1sm1927191nfh.20.2008.01.24.09.38.58 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 24 Jan 2008 09:39:00 -0800 (PST) From: Nikolay Pavlov To: freebsd-current@freebsd.org Date: Thu, 24 Jan 2008 19:39:00 +0200 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) References: <20080123235033.GA3126@what-creek.com> In-Reply-To: <20080123235033.GA3126@what-creek.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801241939.01169.qpadla@gmail.com> Subject: Re: DTrace for FreeBSD - status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: qpadla@gmail.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 Jan 2008 17:39:03 -0000 On Thursday 24 January 2008 01:50:33 John Birrell wrote: > On Wed, 23 Jan 2008 14:05:23 -0600, Andrew Gallatin > > > wrote: > > What is the status of Dtrace in FreeBSD? I thought the original port > > was permantly stalled due to licensing conflicts over CDDL, and > > that John was starting from scratch. > > Cisco is currently funding the port of DTrace to FreeBSD part of their > move to FreeBSD. > > I am probably a week away from putting up a set of diffs for the > initial integration into CURRENT. See: > for the list > of changes/reasons. That page is still a work in progress. > > As of today, the port passes 752 of Sun's DTrace tests. > > FreeBSD developers with p4 access can build //depot/projects/dtrace/src > and get an up-to-date CURRENT with DTrace built in. "make universe" > works for all arches. The kernel modules are limited to amd64 and i386 > at the moment. > > -- > John Birrell You are the MAN. Thanks John for your work and Cisco for sponsoring it. -- ====================================================================== - Best regards, Nikolay Pavlov. <<<----------------------------------- ====================================================================== From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 17:48:03 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF2C416A41A; Thu, 24 Jan 2008 17:48:03 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.freebsd.org (Postfix) with ESMTP id 0029C13C45B; Thu, 24 Jan 2008 17:48:02 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.4) with ESMTP id m0OHm0xx097967; Thu, 24 Jan 2008 20:48:00 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.4/Submit) id m0OHm0dQ097961; Thu, 24 Jan 2008 20:48:00 +0300 (MSK) (envelope-from yar) Date: Thu, 24 Jan 2008 20:47:59 +0300 From: Yar Tikhiy To: Attilio Rao Message-ID: <20080124174759.GC78114@comp.chem.msu.su> References: <790a9fff0801150552l542a4238ofc12efe5fdb45fc2@mail.gmail.com> <20080115143924.GB57756@deviant.kiev.zoral.com.ua> <20080124122808.GA15600@freefall.freebsd.org> <3bbf2fe10801240518i6e18b2f5w84de652d4170c95b@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3bbf2fe10801240518i6e18b2f5w84de652d4170c95b@mail.gmail.com> User-Agent: Mutt/1.5.9i Cc: Kostik Belousov , freebsd-current@freebsd.org Subject: Re: panic: System call lstat returning with 1 locks held X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 17:48:03 -0000 On Thu, Jan 24, 2008 at 02:18:56PM +0100, Attilio Rao wrote: > 2008/1/24, Yar Tikhiy : > > On Tue, Jan 15, 2008 at 04:39:24PM +0200, Kostik Belousov wrote: > > > > > > I think this could be related to the recent vn_lock()/VOP_LOCK() KPI changes. > > > Please, add DEBUG_VFS_LOCKS to the kernel config, and do the > > > show lockedvnods > > > from the ddb prompt when the panic occurs. The witness does not track > > > the lockmgr locks. > > > > I think I'm seeing the same panic on UFS. It's rather nasty: I > > cannot rebuild CURRENT natively due to it so I have to build it > > under 6-STABLE. My favourite way to trigger the panic reliably is > > running `make install' in a simple port directory, e.g., portmaster, > > but my system also panics during daily scripts run and, as already > > said, if trying to build world. > > Yar, > as it seems reproducible for you, can you please add this patch to the tree: > http://www.freebsd.org/~attilio/debug_tdlocks.diff > > compile your kernel with: > options KTR > options KTR_COMPILE=(KTR_SPARE2) > options KTR_MASK=(KTR_SPARE2) > options KTR_ENTRIES=32768 > > and once kernel panics, at ddb prompts do: > > show ktr The first lines of the ktr output are attached. I can try to extract all 32768 lines if needed, but they all look almost the same. I.e., the function name and the td pointer are the same while td_locks bump is 1 or -1. -- Yar db> show ktr 430 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 429 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 428 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 427 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 426 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 425 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 424 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 423 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 422 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 421 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 420 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 419 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 418 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 417 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 416 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 415 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 414 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 413 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 412 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 411 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 410 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 409 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 408 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 407 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 406 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 405 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 404 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 403 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 402 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 401 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 400 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 399 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 398 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 397 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 396 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 395 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 394 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 393 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 392 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 391 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 390 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 389 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 388 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 387 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 386 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 385 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 384 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of 1 td_locks 383 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 382 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks 381 (0xc37e1220:cpu0): _lockmgr: 0xc37e1220 bumping of -1 td_locks ... From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 17:54:48 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EAEDE16A419 for ; Thu, 24 Jan 2008 17:54:47 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mx1.freebsd.org (Postfix) with ESMTP id 785AC13C459 for ; Thu, 24 Jan 2008 17:54:47 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so338465fgg.35 for ; Thu, 24 Jan 2008 09:54:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=MepzIdhbEiseX8v1OK5vgUySFZRC7pPPb5wIIwlXTgk=; b=A1u9eupJ+VjnQiPaQlHNwGbxsKwgzsbusYgAMxDFrYMx6rFLPShmyoUDqHF4H2hE4am/MZ+2JAnlMBnIYym72tQ9bX1PRh1RGtwlPerdhj6SXHu82ghuo6W5m7YYoLaQvaIbJ4ZK6ywjqaMGF3SEDBJoRnKtquUR9nLzT32iP6w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=Xqx3DYB0tAdjst5bGisvKiQSP3dm8IFBV9sahN/mF/tOEmg9whPJg9WhtU4ejh16K92w/uWcGJP6RATShUEET6e8S5X5Z5TthYCx9jjeD6IcPumGFq8eifLyD7J3qHVAXtavFWFbNi2keKxxeUbTP1naCCBtzAg/ltqZd6n7pzE= Received: by 10.86.99.9 with SMTP id w9mr863138fgb.44.1201197286132; Thu, 24 Jan 2008 09:54:46 -0800 (PST) Received: by 10.86.53.7 with HTTP; Thu, 24 Jan 2008 09:54:46 -0800 (PST) Message-ID: <3bbf2fe10801240954r1aa5ae1g3ce347cf4dbbbba@mail.gmail.com> Date: Thu, 24 Jan 2008 18:54:46 +0100 From: "Attilio Rao" Sender: asmrookie@gmail.com To: "Yar Tikhiy" In-Reply-To: <20080124174759.GC78114@comp.chem.msu.su> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <790a9fff0801150552l542a4238ofc12efe5fdb45fc2@mail.gmail.com> <20080115143924.GB57756@deviant.kiev.zoral.com.ua> <20080124122808.GA15600@freefall.freebsd.org> <3bbf2fe10801240518i6e18b2f5w84de652d4170c95b@mail.gmail.com> <20080124174759.GC78114@comp.chem.msu.su> X-Google-Sender-Auth: 3d730bb7106d8c93 Cc: Kostik Belousov , freebsd-current@freebsd.org Subject: Re: panic: System call lstat returning with 1 locks held X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 17:54:48 -0000 2008/1/24, Yar Tikhiy : > On Thu, Jan 24, 2008 at 02:18:56PM +0100, Attilio Rao wrote: > > 2008/1/24, Yar Tikhiy : > > > On Tue, Jan 15, 2008 at 04:39:24PM +0200, Kostik Belousov wrote: > > > > > > > > I think this could be related to the recent vn_lock()/VOP_LOCK() KPI changes. > > > > Please, add DEBUG_VFS_LOCKS to the kernel config, and do the > > > > show lockedvnods > > > > from the ddb prompt when the panic occurs. The witness does not track > > > > the lockmgr locks. > > > > > > I think I'm seeing the same panic on UFS. It's rather nasty: I > > > cannot rebuild CURRENT natively due to it so I have to build it > > > under 6-STABLE. My favourite way to trigger the panic reliably is > > > running `make install' in a simple port directory, e.g., portmaster, > > > but my system also panics during daily scripts run and, as already > > > said, if trying to build world. > > > > Yar, > > as it seems reproducible for you, can you please add this patch to the tree: > > http://www.freebsd.org/~attilio/debug_tdlocks.diff > > > > compile your kernel with: > > options KTR > > options KTR_COMPILE=(KTR_SPARE2) > > options KTR_MASK=(KTR_SPARE2) > > options KTR_ENTRIES=32768 > > > > and once kernel panics, at ddb prompts do: > > > show ktr > > The first lines of the ktr output are attached. I can try to extract > all 32768 lines if needed, but they all look almost the same. I.e., > the function name and the td pointer are the same while td_locks > bump is 1 or -1. You mean the traced owner is always the same? Do you see any call to lockmgr_disown() in the code? Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 17:59:05 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6ED0A16A419 for ; Thu, 24 Jan 2008 17:59:05 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 27D7E13C4EC for ; Thu, 24 Jan 2008 17:59:04 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JI6Lt-0002Ih-Ho for freebsd-current@freebsd.org; Thu, 24 Jan 2008 17:59:01 +0000 Received: from 78-0-88-44.adsl.net.t-com.hr ([78.0.88.44]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 24 Jan 2008 17:59:01 +0000 Received: from ivoras by 78-0-88-44.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 24 Jan 2008 17:59:01 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Thu, 24 Jan 2008 18:58:52 +0100 Lines: 37 Message-ID: References: <18328.45282.562906.708945@celery.zuhause.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig6524D27A1A652E455CF1D99C" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 78-0-88-44.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) In-Reply-To: <18328.45282.562906.708945@celery.zuhause.org> X-Enigmail-Version: 0.95.6 Sender: news Subject: Re: Weird performance behaviour in 7.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: Thu, 24 Jan 2008 17:59:05 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig6524D27A1A652E455CF1D99C Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Bruce Albrecht wrote: > This is my first Q6600 based system, and my first 7.0 system, and my > first AMD-64 system and my first ZFS base system, and I'm seeing > something really strange. Every now and then, processes run really > slowly, like at 1/600th (or worse) than it ought to, but it racks up > the CPU time as though it's running full tilt. Are you running powerd? Also, cpufreq driver was included in the GENERIC kernel in 7.0 (it was=20 optional in 6.x), so it might also cause problems somehow. To verify=20 this, try building a kernel without cpufreq. Also, does your BIOS do any power-saving gimmicks? --------------enig6524D27A1A652E455CF1D99C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHmNHdldnAQVacBcgRAs3fAJ0aEtZ7aG2myiufvLVPRclgqnOlywCg+YlI 6ySN3zwxOT90Plf7TkHdGP4= =p1rA -----END PGP SIGNATURE----- --------------enig6524D27A1A652E455CF1D99C-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 18:44:54 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C5E916A418 for ; Thu, 24 Jan 2008 18:44:54 +0000 (UTC) (envelope-from baldur@foo.is) Received: from gremlin.foo.is (gremlin.foo.is [194.105.250.10]) by mx1.freebsd.org (Postfix) with ESMTP id E587913C44B for ; Thu, 24 Jan 2008 18:44:53 +0000 (UTC) (envelope-from baldur@foo.is) Received: from 127.0.0.1 (localhost.foo.is [127.0.0.1]) by injector.foo.is (Postfix) with SMTP id D3FFFDA8C3 for ; Thu, 24 Jan 2008 18:27:13 +0000 (GMT) X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on gremlin.foo.is X-Spam-Level: X-Spam-Status: No, score=-2.6 required=6.0 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.1.7 Received: by gremlin.foo.is (Postfix, from userid 1000) id B9D33DA8B9; Thu, 24 Jan 2008 18:27:10 +0000 (GMT) Date: Thu, 24 Jan 2008 18:27:10 +0000 From: Baldur Gislason To: freebsd-current@freebsd.org Message-ID: <20080124182710.GC14026@gremlin.foo.is> User-Agent: Mutt/1.4.2.2i X-Sanitizer: Foo MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline Subject: 4GB RAM with an intel core 2 processor X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 18:44:54 -0000 I recently tried to upgrade my Dell workstation from 2GB to 4GB RAM. It's an Optiplex 755 with an Intel Core 2 Quad Q6600 processor. I'm running 7.0-RC1 When I install the 2 extra memory modules, the kernel tells me on startup that it's ignoring 640MB memory above 4GB, leaving me with a total of 3.375GB of accessible memory. However when X starts (using a PCI-e Geforce with nvidia driver) the system reboots. Now, I took a quick look at PAE and discovered that the PAE kernel is not meant for anything but headless systems, most of the drivers (including USB!) are out and no module support either. Do I have any options for using my 4GB of RAM and still retain USB and the nvidia driver? Baldur From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 18:59:42 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B324B16A419 for ; Thu, 24 Jan 2008 18:59:42 +0000 (UTC) (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 85B3813C45B for ; Thu, 24 Jan 2008 18:59:41 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m0OIxXeg075490; Thu, 24 Jan 2008 11:59:33 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4798E015.3050105@samsco.org> Date: Thu, 24 Jan 2008 11:59:33 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.11) Gecko/20071128 SeaMonkey/1.1.7 MIME-Version: 1.0 To: Baldur Gislason References: <20080124182710.GC14026@gremlin.foo.is> In-Reply-To: <20080124182710.GC14026@gremlin.foo.is> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Thu, 24 Jan 2008 11:59:34 -0700 (MST) X-Spam-Status: No, score=-1.4 required=5.4 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: freebsd-current@freebsd.org Subject: Re: 4GB RAM with an intel core 2 processor X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 18:59:42 -0000 Baldur Gislason wrote: > I recently tried to upgrade my Dell workstation from 2GB to 4GB RAM. > It's an Optiplex 755 with an Intel Core 2 Quad Q6600 processor. I'm running 7.0-RC1 > When I install the 2 extra memory modules, the kernel tells me on startup > that it's ignoring 640MB memory above 4GB, leaving me with a total of 3.375GB > of accessible memory. However when X starts (using a PCI-e Geforce with nvidia driver) > the system reboots. > Now, I took a quick look at PAE and discovered that the PAE kernel is > not meant for anything but headless systems, most of the drivers (including USB!) are out and no > module support either. > > Do I have any options for using my 4GB of RAM and still retain USB and the nvidia driver? > At the top of the 32 bit address space is a large region that is reserved for addressing system and peripheral devices. It's typically the top 256-768MB of the address space. Any RAM that is mapped into this space is not available, so what system designers typically do these days is exclude this region from RAM, and map the RAM that would be otherwise lost into the address space to be above the 32-bit limit. That's why it says that it's "ignoring" 640MB of RAM; it knows that it's there, but since the OS is confined to a 32-bit address space, it knows it can't get to it. I would guess that the reason you're getting panic/reboot in X is because you're using a graphics card with a lot of on-board RAM. The video driver is trying to map this RAM into the CPU's address space, and there simply isn't enough room for it because you have the space full of RAM (and the above mentioned reserved space for other devices). With the PAE kernel, modules aren't allowed because PAE caused system data structures to change in a way that module builds couldn't cope with at the time the PAE was written. I believe that that might not be the case any longer, so long as you use the "buildkernel" method and don't try to individually compile modules. It's worth testing. Also, USB was very unreliable in 64-bit environments at the time that PAE was written, so it was also excluded. So what's really happened here is that the PAE kernel config file has probably just gotten stale and in need of a review. I don't know if PAE will fix your X video problems, though. Probably the better bet all around is to run amd64. Scott From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 19:06:25 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6BFFD16A41A; Thu, 24 Jan 2008 19:06:25 +0000 (UTC) (envelope-from peter.schuller@infidyne.com) Received: from smtp.infidyne.com (ds9.infidyne.com [88.80.6.206]) by mx1.freebsd.org (Postfix) with ESMTP id 29B0813C458; Thu, 24 Jan 2008 19:06:24 +0000 (UTC) (envelope-from peter.schuller@infidyne.com) Received: from c-8216e555.03-51-73746f3.cust.bredbandsbolaget.se (c-8216e555.03-51-73746f3.cust.bredbandsbolaget.se [85.229.22.130]) by smtp.infidyne.com (Postfix) with ESMTP id 10DA5127D3; Thu, 24 Jan 2008 20:06:23 +0100 (CET) From: Peter Schuller To: freebsd-current@freebsd.org Date: Thu, 24 Jan 2008 20:06:35 +0100 User-Agent: KMail/1.9.7 References: <20080123235033.GA3126@what-creek.com> In-Reply-To: <20080123235033.GA3126@what-creek.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart12941827.vfj8ktTnq9"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200801242006.43922.peter.schuller@infidyne.com> Cc: current@freebsd.org, John Birrell , gallatin@cs.duke.edu Subject: Re: DTrace for FreeBSD - status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 19:06:25 -0000 --nextPart12941827.vfj8ktTnq9 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline > Cisco is currently funding the port of DTrace to FreeBSD part of their > move to FreeBSD. There is a "move to FreeBSD" on their part? That sounds interesting. Google= =20 did not turn up much for me. =2D-=20 / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org --nextPart12941827.vfj8ktTnq9 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHmOHDDNor2+l1i30RAgvYAKCXooOAyBpntlbkFeHHi2vxeVFAmQCfZzw7 GH+zoJmn2/e4NZ+FP2lj7v0= =J+4T -----END PGP SIGNATURE----- --nextPart12941827.vfj8ktTnq9-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 19:06:25 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6BFFD16A41A; Thu, 24 Jan 2008 19:06:25 +0000 (UTC) (envelope-from peter.schuller@infidyne.com) Received: from smtp.infidyne.com (ds9.infidyne.com [88.80.6.206]) by mx1.freebsd.org (Postfix) with ESMTP id 29B0813C458; Thu, 24 Jan 2008 19:06:24 +0000 (UTC) (envelope-from peter.schuller@infidyne.com) Received: from c-8216e555.03-51-73746f3.cust.bredbandsbolaget.se (c-8216e555.03-51-73746f3.cust.bredbandsbolaget.se [85.229.22.130]) by smtp.infidyne.com (Postfix) with ESMTP id 10DA5127D3; Thu, 24 Jan 2008 20:06:23 +0100 (CET) From: Peter Schuller To: freebsd-current@freebsd.org Date: Thu, 24 Jan 2008 20:06:35 +0100 User-Agent: KMail/1.9.7 References: <20080123235033.GA3126@what-creek.com> In-Reply-To: <20080123235033.GA3126@what-creek.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart12941827.vfj8ktTnq9"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200801242006.43922.peter.schuller@infidyne.com> Cc: current@freebsd.org, John Birrell , gallatin@cs.duke.edu Subject: Re: DTrace for FreeBSD - status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 19:06:25 -0000 --nextPart12941827.vfj8ktTnq9 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline > Cisco is currently funding the port of DTrace to FreeBSD part of their > move to FreeBSD. There is a "move to FreeBSD" on their part? That sounds interesting. Google= =20 did not turn up much for me. =2D-=20 / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org --nextPart12941827.vfj8ktTnq9 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHmOHDDNor2+l1i30RAgvYAKCXooOAyBpntlbkFeHHi2vxeVFAmQCfZzw7 GH+zoJmn2/e4NZ+FP2lj7v0= =J+4T -----END PGP SIGNATURE----- --nextPart12941827.vfj8ktTnq9-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 19:15:49 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 76B1216A417 for ; Thu, 24 Jan 2008 19:15:49 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from hs-out-2122.google.com (hs-out-0708.google.com [64.233.178.244]) by mx1.freebsd.org (Postfix) with ESMTP id 1D23D13C43E for ; Thu, 24 Jan 2008 19:15:48 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by hs-out-2122.google.com with SMTP id h53so358561hsh.11 for ; Thu, 24 Jan 2008 11:15:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=q9tSiG8hpIysiHnJ4yRuBx5vLuc6BMTp8cMoq2nS8To=; b=aImp7cl8WWhQzRM2dCeT6GccEejZfHZyXf+lllHYlu1wE1piMl18o4wLNFXkWQVoHRMZ2LWz+Txdnhi+GUAU60LlcQPuNrTjXX4iMI18xD1fBWVB8DbyOoQn7jVgxKvDLq03k9eqZKML9DWAHgxy7iSWqn/k9hLOgEtI1yfspEw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=GU8o46JcA+IrUE8t6iX+7UcY8ZIZJrXzHBLqpCCS4DwROI6jIZlXzYiVyZ6zKfBB+dLwPU0HMB51OqZfGhMLi9tdq3+r8KXYRoCUKCwNlYU1aBsaDFk8Bc8vzIChupj4vlt9D0CIfJcoNdIsdDTbEkzPrPbJ2vniqKWu6LyzX64= Received: by 10.114.89.1 with SMTP id m1mr1193478wab.77.1201202147334; Thu, 24 Jan 2008 11:15:47 -0800 (PST) Received: by 10.114.255.16 with HTTP; Thu, 24 Jan 2008 11:15:47 -0800 (PST) Message-ID: Date: Thu, 24 Jan 2008 11:15:47 -0800 From: "Kip Macy" To: "=?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?=" In-Reply-To: <868x2f86pp.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4797B923.6030400@gmail.com> <86odbbwo02.fsf@ds4.des.no> <4798B651.7000108@samsco.org> <868x2f86pp.fsf@ds4.des.no> Cc: EchoB , freebsd-current@freebsd.org Subject: Re: XEN and ZFS Status? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 19:15:49 -0000 It says: - it is basically stable on 8 - where to get an md root and configuration files - where to get it via cvsup This has been sufficient for quite a few people to get up and running. I think Scott's irritation may stem from the fact that reality contradicts your statements. -Kip On 1/24/08, Dag-Erling Sm=F8rgrav wrote: > Scott Long writes: > > Dag-Erling Sm=F8rgrav writes: > > > Xen is currently not supported at all, AFAIK. > > Would it be possible to have any more completely uninformed opinions on > > Xen by people completely out of the loop on its development? > > Scott, wtf is wrong with you? You've been acting like an ass both on > and off the lists lately. > > In any case, I stand by what I wrote - Xen is not supported at all in > FreeBSD 7, nor in 8 for that matter. What is or isn't available in > Perforce is completely irrelevant to the OP. > > You (assuming you are involved in Xen development) really don't make it > easy, BTW - the wiki page contains epsilon information, and the status > reports none at all. > > DES > -- > Dag-Erling Sm=F8rgrav - des@des.no > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 19:38:36 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE31816A418 for ; Thu, 24 Jan 2008 19:38:36 +0000 (UTC) (envelope-from rmtodd@ichotolot.servalan.com) Received: from mx2.synetsystems.com (mx2.synetsystems.com [76.10.206.15]) by mx1.freebsd.org (Postfix) with ESMTP id B961413C45A for ; Thu, 24 Jan 2008 19:38:36 +0000 (UTC) (envelope-from rmtodd@ichotolot.servalan.com) Received: by mx2.synetsystems.com (Postfix, from userid 66) id A09C1660; Thu, 24 Jan 2008 14:15:27 -0500 (EST) Received: from rmtodd by servalan.servalan.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1JI7N1-0008mW-85; Thu, 24 Jan 2008 13:04:15 -0600 To: freebsd-current@freebsd.org References: <18328.45282.562906.708945@celery.zuhause.org> From: Richard Todd Date: Thu, 24 Jan 2008 13:04:15 -0600 In-Reply-To: (Bruce Albrecht's message of "Thu, 24 Jan 2008 09:38:10 -0600") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.21 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Weird performance behaviour in 7.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: Thu, 24 Jan 2008 19:38:36 -0000 Bruce Albrecht writes: > This is my first Q6600 based system, and my first 7.0 system, and my > first AMD-64 system and my first ZFS base system, and I'm seeing > something really strange. Every now and then, processes run really > slowly, like at 1/600th (or worse) than it ought to, but it racks up > the CPU time as though it's running full tilt. > > For example, I have this little test program that just does a tight > loop, and most times, it takes about 3 seconds to complete, but right > now, it's taking about 2000 seconds to complete. Right now, it's > consistently running slow, but sometimes it will run slow, but I can > terminate it and start another one which will run at normal speed. This wouldn't by any chance be an Intel 965-chipset-based motherboard with 4G or more of memory, would it? Because there's an interesting little bug in the BIOS on some of those boards which causes the cache-control registers to incorrectly declare a chunk of main memory as uncacheable. This results in random slowdowns depending on whether your process lands in the "bad" zone of memory or not. See http://article.gmane.org/gmane.os.freebsd.stable/50135/ for more details. From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 20:27:24 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC9CD16A469 for ; Thu, 24 Jan 2008 20:27:24 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 98B9E13C457 for ; Thu, 24 Jan 2008 20:27:24 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id B9E002085; Thu, 24 Jan 2008 21:27:15 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 23D64207F; Thu, 24 Jan 2008 21:27:15 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id 0338F844AF; Thu, 24 Jan 2008 21:27:15 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "Kip Macy" References: <4797B923.6030400@gmail.com> <86odbbwo02.fsf@ds4.des.no> <4798B651.7000108@samsco.org> <868x2f86pp.fsf@ds4.des.no> Date: Thu, 24 Jan 2008 21:27:14 +0100 In-Reply-To: (Kip Macy's message of "Thu\, 24 Jan 2008 11\:15\:47 -0800") Message-ID: <86ir1j6kbh.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: EchoB , freebsd-current@freebsd.org Subject: Re: XEN and ZFS Status? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 20:27:25 -0000 "Kip Macy" writes: > I think Scott's irritation may stem from the fact that reality > contradicts your statements. The reality is that there is *zero* support for Xen in CVS. What is or is not in Perforce is completely irrelevant when what the OP asked about was, and I quote, "the production status of Xen and ZFS when 7.0 is released". You and Scott and many others may wish it were otherwise, but it isn't. Yelling at me and blacklisting me on your mail server won't change it. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 20:35:40 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2AAA416A417; Thu, 24 Jan 2008 20:35:40 +0000 (UTC) (envelope-from christos@zoulas.com) Received: from rebar.astron.com (rebar.astron.com [38.117.134.202]) by mx1.freebsd.org (Postfix) with ESMTP id 0623113C465; Thu, 24 Jan 2008 20:35:39 +0000 (UTC) (envelope-from christos@zoulas.com) Received: by rebar.astron.com (Postfix, from userid 10080) id 2611E56544; Thu, 24 Jan 2008 15:17:31 -0500 (EST) From: christos@zoulas.com (Christos Zoulas) Date: Thu, 24 Jan 2008 15:17:31 -0500 In-Reply-To: <20080124133708.GA2220@kobe.laptop> from Giorgos Keramidas (Jan 24, 3:37pm) Organization: Astron Software X-Mailer: Mail User's Shell (7.2.6 beta(4.pl1)+dynamic 20000103) To: Giorgos Keramidas , Mark Peek , tcsh-bugs@mx.gw.com, current@freebsd.org Message-Id: <20080124201731.2611E56544@rebar.astron.com> X-Mailman-Approved-At: Thu, 24 Jan 2008 20:43:02 +0000 Cc: Subject: Re: `set autologout = (15 1)' aborts X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 20:35:40 -0000 On Jan 24, 3:37pm, keramida@freebsd.org (Giorgos Keramidas) wrote: -- Subject: `set autologout = (15 1)' aborts | Hi Christos, Mark and everyone, | | The following is a patch which fixes an abort() in tcsh 6.15.00 on | FreeBSD. The proposed commit log explains why the change is needed, | so if we can get this committed upstream to the tcsh sources, then it | will find its way back to FreeBSD's src/contrib :) | | %%% | tcsh: fix abort in cleanup_until(), caused by internal xgetpass() | | The xgetpass() function pushes a cleanup entry for &osa, but then | attempts to flush the stack until an entry matching &sa. The two | object pointers do not match, so the stack is popped too much, | and then cleanup_until calls abort() when it unexpectedly hits | the bottom of the cleanup stack. | | Reported by: Paul B. Mahol, onemda at gmail.com, | Pietro Cerutti, gahr at gahr.ch thanks! christos | | diff -r 2cc0e20ca15b -r ea3fdd703cbf contrib/tcsh/tc.func.c | --- a/contrib/tcsh/tc.func.c Wed Jan 23 11:47:09 2008 +0000 | +++ b/contrib/tcsh/tc.func.c Thu Jan 24 15:33:31 2008 +0200 | @@ -632,7 +632,7 @@ | } | strbuf_terminate(&pass); | | - cleanup_until(&sa); | + cleanup_until(&osa); | | return pass.s; | } | %%% -- End of excerpt from Giorgos Keramidas From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 20:53:58 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CBE8316A417 for ; Thu, 24 Jan 2008 20:53:58 +0000 (UTC) (envelope-from jb@what-creek.com) Received: from what-creek.com (what-creek.com [66.111.37.70]) by mx1.freebsd.org (Postfix) with ESMTP id A9AD713C45A for ; Thu, 24 Jan 2008 20:53:58 +0000 (UTC) (envelope-from jb@what-creek.com) Received: by what-creek.com (Postfix, from userid 102) id 42BE57330B; Thu, 24 Jan 2008 20:53:58 +0000 (GMT) Date: Thu, 24 Jan 2008 20:53:58 +0000 From: John Birrell To: Dag-Erling Sm??rgrav Message-ID: <20080124205358.GC11488@what-creek.com> References: <20080123235033.GA3126@what-creek.com> <86k5lzwnru.fsf@ds4.des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86k5lzwnru.fsf@ds4.des.no> User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org Subject: Re: DTrace for FreeBSD - status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 20:53:58 -0000 On Thu, Jan 24, 2008 at 10:55:49AM +0100, Dag-Erling Sm??rgrav wrote: > John Birrell writes: > > I am probably a week away from putting up a set of diffs for the > > initial integration into CURRENT. See: > > for the list > > of changes/reasons. That page is still a work in progress. > > http://wiki.freebsd.org/DTrace would be nice :) > > If you want, I can bootstrap it from reasons.html for you. The "reasons" page is automatically generated and is only intended as a way of presenting the diffs for review. Once the code is integrated, that page will die. Sun would like FreeBSD references to go in their wiki. -- John Birrell From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 20:55:32 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D058416A417 for ; Thu, 24 Jan 2008 20:55:32 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by mx1.freebsd.org (Postfix) with ESMTP id 33EDA13C448 for ; Thu, 24 Jan 2008 20:55:32 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so605518waf.3 for ; Thu, 24 Jan 2008 12:55:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=/BSclsbZKU0RHl3/EEn16UA5N8xA6pdxotfLVq8FE7Q=; b=LkZ+/SvltWK00d8ZWi0kEGftzIDdDEoJ7IVT+v4iTvKK4LV7JjaB/iCOcuQc4CuBPgowl7tLrwkPsPi/z8pS/o8lzRvlkN0Qbp/u/sdC7f+h6e17jXXYkdHA6QXQcpZbBXWbkVqV4FFpCN0uQCW4DEWu0usGmODH7ijplMJ2WT4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gnSaG5/mnuBiG0nJWW3jJZer9lkgeY03m73sGWJZK8M+9WOnDyGeKVd9scdEYu7SVO4bjr1UZ84q0qsaAMvdj+hewKrqMxatv7v3St8hWU7uRbuUJ9+osRg57CgNj8vo1eJDEyn/TuNmDs7BOqyubm0R6RJ4vyIiSZvHFZjsgCA= Received: by 10.115.46.9 with SMTP id y9mr1289770waj.129.1201208131845; Thu, 24 Jan 2008 12:55:31 -0800 (PST) Received: by 10.114.255.16 with HTTP; Thu, 24 Jan 2008 12:55:31 -0800 (PST) Message-ID: Date: Thu, 24 Jan 2008 12:55:31 -0800 From: "Kip Macy" To: "=?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?=" In-Reply-To: <86ir1j6kbh.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4797B923.6030400@gmail.com> <86odbbwo02.fsf@ds4.des.no> <4798B651.7000108@samsco.org> <868x2f86pp.fsf@ds4.des.no> <86ir1j6kbh.fsf@ds4.des.no> Cc: EchoB , freebsd-current@freebsd.org Subject: Re: XEN and ZFS Status? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 20:55:32 -0000 LOL. On Jan 24, 2008 12:27 PM, Dag-Erling Sm=F8rgrav wrote: > "Kip Macy" writes: > > I think Scott's irritation may stem from the fact that reality > > contradicts your statements. > > The reality is that there is *zero* support for Xen in CVS. > > What is or is not in Perforce is completely irrelevant when what the OP > asked about was, and I quote, "the production status of Xen and ZFS when > 7.0 is released". > > You and Scott and many others may wish it were otherwise, but it isn't. > Yelling at me and blacklisting me on your mail server won't change it. > > > DES > -- > Dag-Erling Sm=F8rgrav - des@des.no > From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 21:25:51 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C309D16A41B for ; Thu, 24 Jan 2008 21:25:51 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by mx1.freebsd.org (Postfix) with ESMTP id 86E9D13C4EB for ; Thu, 24 Jan 2008 21:25:51 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so619602waf.3 for ; Thu, 24 Jan 2008 13:25:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=NlMBgb9946HZpb2OkWKZQmMVW5ZspJfVDgtglxIT/J8=; b=YZSkXu8+RCKV/zhJhnyzVik0eZUgywrD+x6YS36Teg+uwF/zT4DO+kelmPDRoA/PB7qR+jeHlEIdIUWxi+8qStPRWP3dbeI3lsWVnnOvInWQeko+53EMp9ioc7B1jTOYzKFObF/1FIMOWpL8NvWRFX/9AiOQpnMI4TOGt8g/G84= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=E2TowmQYYKN5KIKb3N8m70DYiaCTQcnwPDNoMV1HKLoT+gQ5aczsuOw3WbLcWCeeDTjssm/wFlX0EH4Soyba7EDZB6ErPqsNM6NOX5e4KlbbrMJnawcRUZBAdiEa1C7kW2ER+fFQHPv93F0Bhyd5BuG45ZBvdVxZSOAbJSBIaUg= Received: by 10.114.197.1 with SMTP id u1mr1352070waf.61.1201209951067; Thu, 24 Jan 2008 13:25:51 -0800 (PST) Received: by 10.114.255.16 with HTTP; Thu, 24 Jan 2008 13:25:51 -0800 (PST) Message-ID: Date: Thu, 24 Jan 2008 13:25:51 -0800 From: "Kip Macy" To: EchoB In-Reply-To: <4797B923.6030400@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4797B923.6030400@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: XEN and ZFS Status? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 21:25:51 -0000 > and wanted to confirm that. Also, using Xen would be a great plus in a > production environment. Unfortunately, DES and Ivan felt the need to derail the thread to get their 2 cents in. In short, yes you can use xen, a patch for 7.0 is available. It is not yet ready for production. -Kip From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 22:10:19 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B17B16A4A6 for ; Thu, 24 Jan 2008 22:10:19 +0000 (UTC) (envelope-from bazzoola@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.243]) by mx1.freebsd.org (Postfix) with ESMTP id B50CB13C4D3 for ; Thu, 24 Jan 2008 22:10:18 +0000 (UTC) (envelope-from bazzoola@gmail.com) Received: by an-out-0708.google.com with SMTP id c14so110832anc.13 for ; Thu, 24 Jan 2008 14:10:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to:content-type:content-transfer-encoding:mime-version:subject:date:x-mailer; bh=/8wIZW1nst3INWkXUnXCyzzGzARwaO6c4XpO0FbgrkQ=; b=UoZ6eTY97IfzDnCcPM9IH9isudynmre7w7ThSnm+Ejecc6sXlXhjD6gKTQSNnN6l0Ury/lhlZ0lzP9BXH2ET/AZjgcm9S0KtZUgVyAhccgMX5nhhAb0bECzuxEhbzQ+7WF9wElvUybgJ7HH2yPTB3vXqdedq2eoRZP3+eYHk/sY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:content-type:content-transfer-encoding:mime-version:subject:date:x-mailer; b=gzA4knAr6cIRgg9sidHBjhTMciVCT+9DwORq1kIBcP6tSExkyFwVZKfCoHuRKWKi9oumZHrwz1Z6cIrEerFODyCVnjiHJyPGLDHGWJQ0ZsR63UWYvgfBa5OY73qDcLt7yMgqAQOLor4IrGTw6ExTWNvAZKQAvekouIW3COS0UBs= Received: by 10.100.206.11 with SMTP id d11mr2448192ang.88.1201211062914; Thu, 24 Jan 2008 13:44:22 -0800 (PST) Received: from macwire.local ( [76.247.130.45]) by mx.google.com with ESMTPS id m33sm2091740ele.18.2008.01.24.13.44.21 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 24 Jan 2008 13:44:21 -0800 (PST) Message-Id: <2C14CF79-F269-4622-9E99-89BC20D73F59@gmail.com> From: bazzoola To: freebsd-current@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Date: Thu, 24 Jan 2008 16:44:19 -0500 X-Mailer: Apple Mail (2.915) Subject: Noise ratio on -CURRENT has increased recently X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 22:10:19 -0000 Greetings, I come from an academic background and I have been reading and enjoying -CURRENT for years I use it to learn and adapt new ideas in my research. I just wanted to say that recently, I noticed that the noise ratio here has increased more than 'the usual' and it really saddens me to see intelligent and very active developers throwing bricks at each other on this public list. I have always liked this educated and kind community of FreeBSD and I hope it remains like that. Thanks for all your efforts! -b From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 22:16:57 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9088B16A418 for ; Thu, 24 Jan 2008 22:16:57 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.freebsd.org (Postfix) with ESMTP id F3A6613C459 for ; Thu, 24 Jan 2008 22:16:56 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from [200.152.88.34] (n80.matik.com.br [200.152.88.34] (may be forged)) by msrv.matik.com.br (8.14.1/8.13.1) with ESMTP id m0OL4CHG057223 for ; Thu, 24 Jan 2008 19:04:12 -0200 (BRT) (envelope-from joao@matik.com.br) Message-ID: <4798FD35.5080007@matik.com.br> Date: Thu, 24 Jan 2008 19:03:49 -0200 From: joao_br User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV version 0.91.2, clamav-milter version 0.91.2 on msrv.matik.com.br X-Virus-Status: Clean Subject: panic on recent source X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 22:16:57 -0000 unfortunatly I got no trace only this from the panic output ffffffff80361740 t lock_profile_obtain_lock_success ffffffff80361760 t __curthread ffffffff80361780 t atomic_cmpset_long ffffffff803617d0 T eventhandler_deregister it is 7-prerelease with sources from jan 19th on amd64 SMP any hint or is this already a known problem? thank´s João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 22:28:32 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFB8916A469; Thu, 24 Jan 2008 22:28:32 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 7AFE413C469; Thu, 24 Jan 2008 22:28:32 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id E9787207F; Thu, 24 Jan 2008 23:28:23 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id D66982049; Thu, 24 Jan 2008 23:28:23 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id C24FD844AF; Thu, 24 Jan 2008 23:28:23 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Peter Schuller References: <20080123235033.GA3126@what-creek.com> <200801242006.43922.peter.schuller@infidyne.com> Date: Thu, 24 Jan 2008 23:28:23 +0100 In-Reply-To: <200801242006.43922.peter.schuller@infidyne.com> (Peter Schuller's message of "Thu\, 24 Jan 2008 20\:06\:35 +0100") Message-ID: <868x2e7ta0.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, current@freebsd.org, gallatin@cs.duke.edu, John Birrell Subject: Re: DTrace for FreeBSD - status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 22:28:32 -0000 Peter Schuller writes: > John Birrell writes: > > Cisco is currently funding the port of DTrace to FreeBSD part of > > their move to FreeBSD. > There is a "move to FreeBSD" on their part? Yes, and they've been hiring FreeBSD devs left and right... DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 22:28:32 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFB8916A469; Thu, 24 Jan 2008 22:28:32 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 7AFE413C469; Thu, 24 Jan 2008 22:28:32 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id E9787207F; Thu, 24 Jan 2008 23:28:23 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id D66982049; Thu, 24 Jan 2008 23:28:23 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id C24FD844AF; Thu, 24 Jan 2008 23:28:23 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Peter Schuller References: <20080123235033.GA3126@what-creek.com> <200801242006.43922.peter.schuller@infidyne.com> Date: Thu, 24 Jan 2008 23:28:23 +0100 In-Reply-To: <200801242006.43922.peter.schuller@infidyne.com> (Peter Schuller's message of "Thu\, 24 Jan 2008 20\:06\:35 +0100") Message-ID: <868x2e7ta0.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, current@freebsd.org, gallatin@cs.duke.edu, John Birrell Subject: Re: DTrace for FreeBSD - status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 22:28:32 -0000 Peter Schuller writes: > John Birrell writes: > > Cisco is currently funding the port of DTrace to FreeBSD part of > > their move to FreeBSD. > There is a "move to FreeBSD" on their part? Yes, and they've been hiring FreeBSD devs left and right... DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 22:57:48 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EBE6A16A417 for ; Thu, 24 Jan 2008 22:57:48 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 9F09713C45A for ; Thu, 24 Jan 2008 22:57:48 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JIB0v-0000z3-Vw for freebsd-current@freebsd.org; Thu, 24 Jan 2008 22:57:42 +0000 Received: from 78-0-88-44.adsl.net.t-com.hr ([78.0.88.44]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 24 Jan 2008 22:57:41 +0000 Received: from ivoras by 78-0-88-44.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 24 Jan 2008 22:57:41 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Thu, 24 Jan 2008 23:57:31 +0100 Lines: 34 Message-ID: References: <4797B923.6030400@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig827381E67F0763A1645AAD46" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 78-0-88-44.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) In-Reply-To: X-Enigmail-Version: 0.95.6 Sender: news Subject: Re: XEN and ZFS Status? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 22:57:49 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig827381E67F0763A1645AAD46 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Kip Macy wrote: >> and wanted to confirm that. Also, using Xen would be a great plus in a= >> production environment. >=20 > Unfortunately, DES and Ivan felt the need to derail the thread to get > their 2 cents in. In short, yes you can use xen, a patch for 7.0 is > available. It is not yet ready for production. Hey, I *want* Xen to work. How do you feel about the idea of "community" = funding? --------------enig827381E67F0763A1645AAD46 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHmRfbldnAQVacBcgRArWFAKD4TZWyaYHatQnXVA/Cig/V1ne8IQCeIu5l PyZHV6ouO/rIgkYvE6t8khU= =e7Yi -----END PGP SIGNATURE----- --------------enig827381E67F0763A1645AAD46-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 23:05:08 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8DB0A16A539 for ; Thu, 24 Jan 2008 23:05:08 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.freebsd.org (Postfix) with ESMTP id 52A1913C467 for ; Thu, 24 Jan 2008 23:05:08 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from thor.farley.org (thor.farley.org [192.168.1.5]) by mail.farley.org (8.14.1/8.14.1) with ESMTP id m0ON502v005773; Thu, 24 Jan 2008 17:05:00 -0600 (CST) (envelope-from scf@FreeBSD.org) Date: Thu, 24 Jan 2008 17:05:00 -0600 (CST) From: "Sean C. Farley" To: Baldur Gislason In-Reply-To: <20080124182710.GC14026@gremlin.foo.is> Message-ID: References: <20080124182710.GC14026@gremlin.foo.is> User-Agent: Alpine 1.00 (BSF 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on mail.farley.org Cc: freebsd-current@FreeBSD.org Subject: Re: 4GB RAM with an intel core 2 processor X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 23:05:08 -0000 On Thu, 24 Jan 2008, Baldur Gislason wrote: > I recently tried to upgrade my Dell workstation from 2GB to 4GB RAM. > It's an Optiplex 755 with an Intel Core 2 Quad Q6600 processor. I'm > running 7.0-RC1 When I install the 2 extra memory modules, the kernel > tells me on startup that it's ignoring 640MB memory above 4GB, leaving > me with a total of 3.375GB of accessible memory. However when X starts > (using a PCI-e Geforce with nvidia driver) the system reboots. > Now, I took a quick look at PAE and discovered that the PAE kernel is > not meant for anything but headless systems, most of the drivers > (including USB!) are out and no module support either. > > Do I have any options for using my 4GB of RAM and still retain USB and > the nvidia driver? The nvidia driver supposedly does not support PAE, and I know it does not support memory remapping (at least with FreeBSD). If you disable memory remapping in the BIOS, then the reboots should stop. I do not know if the Optiplex 755 has that option or not. Sean -- scf@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 23:26:20 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D3E516A46C for ; Thu, 24 Jan 2008 23:26:20 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 6E2B013C45A for ; Thu, 24 Jan 2008 23:26:20 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1JIBAy-0005OY-6z for freebsd-current@freebsd.org; Thu, 24 Jan 2008 15:08:04 -0800 Message-ID: <15077333.post@talk.nabble.com> Date: Thu, 24 Jan 2008 15:08:04 -0800 (PST) From: sleep`walker To: freebsd-current@freebsd.org In-Reply-To: <868x2e7ta0.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Nabble-From: sleep.walk@yahoo.com References: <20080123235033.GA3126@what-creek.com> <200801242006.43922.peter.schuller@infidyne.com> <868x2e7ta0.fsf@ds4.des.no> X-Mailman-Approved-At: Thu, 24 Jan 2008 23:36:45 +0000 Subject: Re: DTrace for FreeBSD - status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 23:26:20 -0000 Dag-Erling Sm=C3=B8rgrav wrote: >=20 > Yes, and they've been hiring FreeBSD devs left and right... >=20 Wow! Great news! Can you tell me, please, will Cisco replace IOS's kernel with FreeBSD's and port their configuration tools to FreeBSD, or it will be regular FreeBSD with it's tools and applications? I would like to see pf and csh on Ciscro router out of box ;) --=20 View this message in context: http://www.nabble.com/DTrace-for-FreeBSD---st= atus-tp15055963p15077333.html Sent from the freebsd-current mailing list archive at Nabble.com. From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 23:37:25 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C734216A418; Thu, 24 Jan 2008 23:37:25 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.freebsd.org (Postfix) with ESMTP id 9F44613C43E; Thu, 24 Jan 2008 23:37:25 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.141] (may be forged)) by mxout4.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.09) with ESMTP id m0ONbOA7019051 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 24 Jan 2008 15:37:24 -0800 X-Auth-Received: from [128.208.7.236] (shiina.dyn.cs.washington.edu [128.208.7.236]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW07.09) with ESMTP id m0ONbOgp019983 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 24 Jan 2008 15:37:24 -0800 In-Reply-To: <200801242006.43922.peter.schuller@infidyne.com> References: <20080123235033.GA3126@what-creek.com> <200801242006.43922.peter.schuller@infidyne.com> Mime-Version: 1.0 (Apple Message framework v753) X-Gpgmail-State: !signed Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <2C5C9108-085E-4006-841C-CBFBF841F6ED@u.washington.edu> Content-Transfer-Encoding: 7bit From: Garrett Cooper Date: Thu, 24 Jan 2008 15:37:25 -0800 To: Peter Schuller X-Mailer: Apple Mail (2.753) X-PMX-Version: 5.4.1.325704, Antispam-Engine: 2.6.0.325393, Antispam-Data: 2008.1.24.152433 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='BODY_SIZE_900_999 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: freebsd-current@freebsd.org, current@freebsd.org, gallatin@cs.duke.edu, John Birrell Subject: Re: DTrace for FreeBSD - status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 23:37:25 -0000 On Jan 24, 2008, at 11:06 AM, Peter Schuller wrote: >> Cisco is currently funding the port of DTrace to FreeBSD part of >> their >> move to FreeBSD. > > There is a "move to FreeBSD" on their part? That sounds > interesting. Google > did not turn up much for me. > > -- > / Peter Schuller > > PGP userID: 0xE9758B7D or 'Peter Schuller > ' > Key retrieval: Send an E-Mail to getpgpkey@scode.org > E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org It might not have been made public insomuch, but I know some of the folks who are spearheading that effort. It's to help reduce development efforts in some respects by using a stable foundation, while contributing back to the [Free]BSD community through volunteering, as part of patch submissions, commits, etc. I know [a little] because I was interviewing with one group involved with the effort :). Cheers, -Garrett From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 23:37:25 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C734216A418; Thu, 24 Jan 2008 23:37:25 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout4.cac.washington.edu (mxout4.cac.washington.edu [140.142.33.19]) by mx1.freebsd.org (Postfix) with ESMTP id 9F44613C43E; Thu, 24 Jan 2008 23:37:25 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.141] (may be forged)) by mxout4.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.09) with ESMTP id m0ONbOA7019051 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 24 Jan 2008 15:37:24 -0800 X-Auth-Received: from [128.208.7.236] (shiina.dyn.cs.washington.edu [128.208.7.236]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW07.09) with ESMTP id m0ONbOgp019983 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 24 Jan 2008 15:37:24 -0800 In-Reply-To: <200801242006.43922.peter.schuller@infidyne.com> References: <20080123235033.GA3126@what-creek.com> <200801242006.43922.peter.schuller@infidyne.com> Mime-Version: 1.0 (Apple Message framework v753) X-Gpgmail-State: !signed Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <2C5C9108-085E-4006-841C-CBFBF841F6ED@u.washington.edu> Content-Transfer-Encoding: 7bit From: Garrett Cooper Date: Thu, 24 Jan 2008 15:37:25 -0800 To: Peter Schuller X-Mailer: Apple Mail (2.753) X-PMX-Version: 5.4.1.325704, Antispam-Engine: 2.6.0.325393, Antispam-Data: 2008.1.24.152433 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='BODY_SIZE_900_999 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: freebsd-current@freebsd.org, current@freebsd.org, gallatin@cs.duke.edu, John Birrell Subject: Re: DTrace for FreeBSD - status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 23:37:25 -0000 On Jan 24, 2008, at 11:06 AM, Peter Schuller wrote: >> Cisco is currently funding the port of DTrace to FreeBSD part of >> their >> move to FreeBSD. > > There is a "move to FreeBSD" on their part? That sounds > interesting. Google > did not turn up much for me. > > -- > / Peter Schuller > > PGP userID: 0xE9758B7D or 'Peter Schuller > ' > Key retrieval: Send an E-Mail to getpgpkey@scode.org > E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org It might not have been made public insomuch, but I know some of the folks who are spearheading that effort. It's to help reduce development efforts in some respects by using a stable foundation, while contributing back to the [Free]BSD community through volunteering, as part of patch submissions, commits, etc. I know [a little] because I was interviewing with one group involved with the effort :). Cheers, -Garrett From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 23:50:01 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA60416A420 for ; Thu, 24 Jan 2008 23:50:01 +0000 (UTC) (envelope-from ari@ish.com.au) Received: from fish.ish.com.au (eth5921.nsw.adsl.internode.on.net [59.167.240.32]) by mx1.freebsd.org (Postfix) with ESMTP id 76F2213C442 for ; Thu, 24 Jan 2008 23:50:01 +0000 (UTC) (envelope-from ari@ish.com.au) Received: from ip-182.ish.com.au ([203.29.62.182]) by fish.ish.com.au with esmtpa (Exim 4.43) id 1JIBr4-0007cX-Aw for freebsd-current@freebsd.org; Fri, 25 Jan 2008 10:51:34 +1100 Message-Id: From: Aristedes Maniatis To: freebsd-current@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v915) Date: Fri, 25 Jan 2008 10:49:59 +1100 X-Mailer: Apple Mail (2.915) Subject: freebsd 7 release process X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 23:50:01 -0000 How can non-committers like myself keep up to date with the progress of freebsd releases? I read stable, current and cvs mailing lists. I've even looked at the qa mailing list but it looks completely abandoned (perhaps the links to it should be removed from the web site). I see this page: http://www.freebsd.org/releases/7.0R/todo.html but it tells me that we are just waiting for Robert Watson to complete testing of the MAC framework changes. Nothing in commit logs or mailing lists correlates to that so I assume it is incorrect. Really, all I want to do is to get a handle on the known outstanding bugs, but the FreeBSD bug tracking system is very crappy (compared to almost all other open source projects I use or am involved in) and has no way to look at bugs by reported-in version or target release. So my question is: how do other people know what is happening? Does re have a mailing list somewhere I can read? I know many people are putting in vast amount of effort here, so this is not a criticism of the delays. Just without any regular bulletins, emails to the mailing lists, bug tracker or web site updates I can't tell what bugs are left, what are fixed and what I need to be aware of. Thanks Ari Maniatis --------------------------> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A From owner-freebsd-current@FreeBSD.ORG Thu Jan 24 23:59:01 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 902F516A419 for ; Thu, 24 Jan 2008 23:59:01 +0000 (UTC) (envelope-from baldur@foo.is) Received: from gremlin.foo.is (gremlin.foo.is [194.105.250.10]) by mx1.freebsd.org (Postfix) with ESMTP id 5128F13C448 for ; Thu, 24 Jan 2008 23:59:01 +0000 (UTC) (envelope-from baldur@foo.is) Received: from 127.0.0.1 (localhost.foo.is [127.0.0.1]) by injector.foo.is (Postfix) with SMTP id 9904CDA8C1; Thu, 24 Jan 2008 23:59:00 +0000 (GMT) X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on gremlin.foo.is X-Spam-Level: X-Spam-Status: No, score=-2.6 required=6.0 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.1.7 Received: by gremlin.foo.is (Postfix, from userid 1000) id A2A6ADA8BB; Thu, 24 Jan 2008 23:58:57 +0000 (GMT) Date: Thu, 24 Jan 2008 23:58:57 +0000 From: Baldur Gislason To: Scott Long Message-ID: <20080124235857.GD14026@gremlin.foo.is> References: <20080124182710.GC14026@gremlin.foo.is> <4798E015.3050105@samsco.org> In-Reply-To: <4798E015.3050105@samsco.org> User-Agent: Mutt/1.4.2.2i X-Sanitizer: Foo MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline Cc: freebsd-current@freebsd.org Subject: Re: 4GB RAM with an intel core 2 processor X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 23:59:01 -0000 On Thu, Jan 24, 2008 at 11:59:33AM -0700, Scott Long wrote: > I don't know if PAE will fix your X video problems, though. Probably > the better bet all around is to run amd64. > > Scott > Even if PAE would fix the X problem I can't live without USB. This system has no PS/2 keyboard controller. I wasn't aware that amd64 was the same 64 bit architecture as used by Intel. Are there any known backwards compatibility issues with running i386 linux binaries for example if I switch over to amd64? Also, could I switch to amd64 by just changing make.conf and doing a buildworld and buildkernel or would I have to do a binary upgrade or maybe even a clean install? Baldur From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 00:04:25 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2506816A419 for ; Fri, 25 Jan 2008 00:04:25 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outO.internet-mail-service.net (outO.internet-mail-service.net [216.240.47.238]) by mx1.freebsd.org (Postfix) with ESMTP id E704313C45A for ; Fri, 25 Jan 2008 00:04:24 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Thu, 24 Jan 2008 16:04:24 -0800 Received: from julian-mac.elischer.org (localhost [127.0.0.1]) by idiom.com (Postfix) with ESMTP id D65D5126FE9; Thu, 24 Jan 2008 16:04:23 -0800 (PST) Message-ID: <47992787.9030406@elischer.org> Date: Thu, 24 Jan 2008 16:04:23 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: sleep`walker References: <20080123235033.GA3126@what-creek.com> <200801242006.43922.peter.schuller@infidyne.com> <868x2e7ta0.fsf@ds4.des.no> <15077333.post@talk.nabble.com> In-Reply-To: <15077333.post@talk.nabble.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org Subject: Re: DTrace for FreeBSD - status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 00:04:25 -0000 sleep`walker wrote: > > > Dag-Erling Smørgrav wrote: >> Yes, and they've been hiring FreeBSD devs left and right... >> > > Wow! Great news! > Can you tell me, please, will Cisco replace IOS's kernel with FreeBSD's and > port their configuration tools to FreeBSD, or it will be regular FreeBSD > with it's tools and applications? > I would like to see pf and csh on Ciscro router out of box ;) Firstly, cisco makes a lot more than just routers. Secondly, when it's embedded you will probably not know it's freebsd or Linux or whatever. Cisco has a lot of Linux out there that you don't know about. Some might become BSD based but you wouldn't see a difference since you didn't know it was linux in the first place :-) There is not any ONE os for cisco. There are many and freeBSD will in all probability not take over from them all. It's just another arrow in the quiver. From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 03:26:23 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B7E1716A417 for ; Fri, 25 Jan 2008 03:26:23 +0000 (UTC) (envelope-from bruce@zuhause.org) Received: from mail.zuhause.org (216.243.156.193.real-time.com [216.243.156.193]) by mx1.freebsd.org (Postfix) with ESMTP id 1FA0E13C43E for ; Fri, 25 Jan 2008 03:26:23 +0000 (UTC) (envelope-from bruce@zuhause.org) Received: from bhfs.zuhause.org (bhfs.zuhause.org [10.0.2.10]) by mail.zuhause.org (Postfix) with ESMTP id 3DA567C04 for ; Thu, 24 Jan 2008 21:26:22 -0600 (CST) Received: by bhfs.zuhause.org (Postfix, from userid 1001) id 45A4B5C023; Thu, 24 Jan 2008 21:26:54 -0600 (CST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18329.22270.123314.900543@bhfs.zuhause.org> Date: Thu, 24 Jan 2008 21:26:54 -0600 To: freebsd-current@freebsd.org From: bruce@zuhause.mn.org In-Reply-To: References: <18328.45282.562906.708945@celery.zuhause.org> X-Mailer: VM 7.17 under 21.4 (patch 20) "Double Solitaire" XEmacs Lucid Subject: Re: Weird performance behaviour in 7.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: Fri, 25 Jan 2008 03:26:23 -0000 Richard Todd writes: > Bruce Albrecht writes: > > > This is my first Q6600 based system, and my first 7.0 system, and my > > first AMD-64 system and my first ZFS base system, and I'm seeing > > something really strange. Every now and then, processes run really > > slowly, like at 1/600th (or worse) than it ought to, but it racks up > > the CPU time as though it's running full tilt. > > > > For example, I have this little test program that just does a tight > > loop, and most times, it takes about 3 seconds to complete, but right > > now, it's taking about 2000 seconds to complete. Right now, it's > > consistently running slow, but sometimes it will run slow, but I can > > terminate it and start another one which will run at normal speed. > > This wouldn't by any chance be an Intel 965-chipset-based motherboard > with 4G or more of memory, would it? Because there's an interesting > little bug in the BIOS on some of those boards which causes the > cache-control registers to incorrectly declare a chunk of main memory > as uncacheable. This results in random slowdowns depending on whether > your process lands in the "bad" zone of memory or not. See > http://article.gmane.org/gmane.os.freebsd.stable/50135/ for more details. Bingo! This is a Intel DG965WH with 4 GB of memory. I don't think I can downgrade to the 1669 firmware because of the processor I'm using. The Fedora thread says that there's a hack to do the following in linux to fix the "bad" zone echo "base=0x1a8000000 size=0x4000000 type=write-back" >| /proc/mtrr What would be the FreeBSD equivalent? The output of memcontrol list is 0x0/0x10000 BIOS write-back fixed-base fixed-length set-by-firmware active 0x10000/0x10000 BIOS write-back fixed-base fixed-length set-by-firmware active 0x20000/0x10000 BIOS write-back fixed-base fixed-length set-by-firmware active 0x30000/0x10000 BIOS write-back fixed-base fixed-length set-by-firmware active 0x40000/0x10000 BIOS write-back fixed-base fixed-length set-by-firmware active 0x50000/0x10000 BIOS write-back fixed-base fixed-length set-by-firmware active 0x60000/0x10000 BIOS write-back fixed-base fixed-length set-by-firmware active 0x70000/0x10000 BIOS write-back fixed-base fixed-length set-by-firmware active 0x80000/0x4000 BIOS write-back fixed-base fixed-length set-by-firmware active 0x84000/0x4000 BIOS write-back fixed-base fixed-length set-by-firmware active 0x88000/0x4000 BIOS write-back fixed-base fixed-length set-by-firmware active 0x8c000/0x4000 BIOS write-back fixed-base fixed-length set-by-firmware active 0x90000/0x4000 BIOS write-back fixed-base fixed-length set-by-firmware active 0x94000/0x4000 BIOS write-back fixed-base fixed-length set-by-firmware active 0x98000/0x4000 BIOS write-back fixed-base fixed-length set-by-firmware active 0x9c000/0x4000 BIOS write-back fixed-base fixed-length set-by-firmware active 0xa0000/0x4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xa4000/0x4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xa8000/0x4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xac000/0x4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xb0000/0x4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xb4000/0x4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xb8000/0x4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xbc000/0x4000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xc0000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xc1000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xc2000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xc3000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xc4000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xc5000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xc6000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xc7000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xc8000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xc9000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xca000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xcb000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xcc000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xcd000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xce000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xcf000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xd0000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xd1000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xd2000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xd3000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xd4000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xd5000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xd6000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xd7000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xd8000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xd9000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xda000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xdb000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xdc000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xdd000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xde000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xdf000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xe0000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xe1000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xe2000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xe3000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xe4000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xe5000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xe6000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xe7000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xe8000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xe9000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xea000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xeb000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xec000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xed000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xee000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xef000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xf0000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xf1000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xf2000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xf3000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xf4000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xf5000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xf6000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xf7000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xf8000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xf9000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xfa000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xfb000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xfc000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xfd000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xfe000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0xff000/0x1000 BIOS uncacheable fixed-base fixed-length set-by-firmware active 0x0/0xf080000000 BIOS write-back set-by-firmware active bogus 0x80000000/0xf040000000 BIOS write-back set-by-firmware active bogus 0xc0000000/0xf010000000 BIOS write-back set-by-firmware active bogus 0xcf800000/0xf000800000 BIOS uncacheable set-by-firmware active bogus 0xcf700000/0xf000100000 BIOS uncacheable set-by-firmware active bogus From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 04:37:51 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DEE1A16A41B for ; Fri, 25 Jan 2008 04:37:51 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 8852E13C457 for ; Fri, 25 Jan 2008 04:37:51 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.1/8.14.1) with ESMTP id m0P4XhQA022822; Thu, 24 Jan 2008 21:33:43 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 24 Jan 2008 21:37:41 -0700 (MST) Message-Id: <20080124.213741.1628329459.imp@bsdimp.com> To: gahr@gahr.ch From: "M. Warner Losh" In-Reply-To: <47989278.6050802@gahr.ch> References: <47989278.6050802@gahr.ch> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: [Fwd: SMP in machine/params.h] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 04:37:52 -0000 Why do you think that the SMP macro should be defined in machine/param.h? Warner From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 06:09:49 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE30A16A421 for ; Fri, 25 Jan 2008 06:09:49 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.185]) by mx1.freebsd.org (Postfix) with ESMTP id 462F013C43E for ; Fri, 25 Jan 2008 06:09:49 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so498037rvb.43 for ; Thu, 24 Jan 2008 22:09:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=4ZTtL0Icq+O4VdgrxAb2O7ANxZn7DSs/L0qg3RNUSZg=; b=JEtN1sh81l+sjT+bHsW+q/TIkVzH7/3l/OAFEIsfm59R2HCGRCxNRG/XZrL/Bd5e0Y58McBXAbWtJ+l1clOxtdralwS6CoTCVT4bkXtXu60AznU4E2vRDR1O0xKMsiBJMGO5kXMOXKS1xlglc/qNyhZKrmRj0LiXIwrwi3tK98g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=azdaKZAk6AZxw7YHw0j7jc2yfOVyO/IC/ZKvFd3O1u8Pr/x4+ajV6HZK6Joekfscn8WSYpAYp9WfwD7NQscf/TKsW+ne6NykX3vbFNq1jad2k7PJVuk+4gt+bFOSs21Rp3DNOtEcOoqMyX7rtT6/RMEoavweNuugcocDkH6x6Us= Received: by 10.114.179.1 with SMTP id b1mr1831120waf.143.1201241388463; Thu, 24 Jan 2008 22:09:48 -0800 (PST) Received: by 10.114.255.16 with HTTP; Thu, 24 Jan 2008 22:09:48 -0800 (PST) Message-ID: Date: Thu, 24 Jan 2008 22:09:48 -0800 From: "Kip Macy" To: "Ivan Voras" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4797B923.6030400@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: XEN and ZFS Status? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 06:09:49 -0000 > Hey, I *want* Xen to work. How do you feel about the idea of "community" > funding? It is a possible approach. I'll see if I can't get any corporate sponsors for it first. From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 07:55:57 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 120D316A421; Fri, 25 Jan 2008 07:55:57 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.freebsd.org (Postfix) with ESMTP id C16DC13C465; Fri, 25 Jan 2008 07:55:55 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.4) with ESMTP id m0P7tq6V022587; Fri, 25 Jan 2008 10:55:52 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.4/Submit) id m0P7tpXO022584; Fri, 25 Jan 2008 10:55:51 +0300 (MSK) (envelope-from yar) Date: Fri, 25 Jan 2008 10:55:51 +0300 From: Yar Tikhiy To: Attilio Rao Message-ID: <20080125075551.GB21633@comp.chem.msu.su> References: <790a9fff0801150552l542a4238ofc12efe5fdb45fc2@mail.gmail.com> <20080115143924.GB57756@deviant.kiev.zoral.com.ua> <20080124122808.GA15600@freefall.freebsd.org> <3bbf2fe10801240518i6e18b2f5w84de652d4170c95b@mail.gmail.com> <20080124145811.GB78114@comp.chem.msu.su> <3bbf2fe10801240707o72b927cg74dbf9b7bbcd88fc@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3bbf2fe10801240707o72b927cg74dbf9b7bbcd88fc@mail.gmail.com> User-Agent: Mutt/1.5.9i Cc: Kostik Belousov , freebsd-current@freebsd.org Subject: Re: panic: System call lstat returning with 1 locks held X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 07:55:57 -0000 On Thu, Jan 24, 2008 at 04:07:43PM +0100, Attilio Rao wrote: > 2008/1/24, Yar Tikhiy : > > On Thu, Jan 24, 2008 at 02:18:56PM +0100, Attilio Rao wrote: > > > 2008/1/24, Yar Tikhiy : > > > > On Tue, Jan 15, 2008 at 04:39:24PM +0200, Kostik Belousov wrote: > > > > > > > > > > I think this could be related to the recent vn_lock()/VOP_LOCK() KPI changes. > > > > > Please, add DEBUG_VFS_LOCKS to the kernel config, and do the > > > > > show lockedvnods > > > > > from the ddb prompt when the panic occurs. The witness does not track > > > > > the lockmgr locks. > > > > > > > > I think I'm seeing the same panic on UFS. It's rather nasty: I > > > > cannot rebuild CURRENT natively due to it so I have to build it > > > > under 6-STABLE. My favourite way to trigger the panic reliably is > > > > running `make install' in a simple port directory, e.g., portmaster, > > > > but my system also panics during daily scripts run and, as already > > > > said, if trying to build world. > > > > > > Yar, > > > as it seems reproducible for you, can you please add this patch to the tree: > > > http://www.freebsd.org/~attilio/debug_tdlocks.diff > > > > > > compile your kernel with: > > > options KTR > > > options KTR_COMPILE=(KTR_SPARE2) > > > options KTR_MASK=(KTR_SPARE2) > > > options KTR_ENTRIES=32768 > > > > > > and once kernel panics, at ddb prompts do: > > > > show ktr > > > > Thank you for your instant response! > > > > The patched kernel is already being built, but I've got the following > > question in the meanwhile: Should I have updated my kernel to get your > > latest changes to kern_lock.c? Now my local copy of kern_lock.c is at > > rev. 1.119, i.e., 1 revision behind today's change. > > As long as this patch still applies, it should not any meaningful difference. > > Thanks a lot for your effort of testing and reporting bugs! I don't deserve these kind words because I disinformed you seriously. My panic appears to be related not to UFS, but to NTFS. Namely I have an NTFS volume mounted read-only at /ntfs. I have no idea why the ports framework touches the /ntfs sub-tree, but not mounting it in the first place makes the panic go away. (I still wonder why my system would also panic during buildworld, which should not touch my /ntfs at all... Now I'll try to do a buildworld w/o /ntfs mounted.) At the same time, dismounting the NTFS volume leads to an instant panic of a similar kind: panic: System call unmount returning with 5 locks held More debug output is attached. So at least UFS doesn't seem affected by the panic. Excuse me for my having provided wrong info. -- Yar panic: System call unmount returning with 5 locks held cpuid = 0 KDB: enter: panic [thread pid 985 tid 100085 ] Stopped at kdb_enter+0x3a: movl $0,kdb_why db> show lockedvn Locked vnodes db> sh ktr 678 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks 677 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks 676 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks 675 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of 1 td_locks 674 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks 673 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of 1 td_locks 672 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks 671 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of 1 td_locks 670 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks 669 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of 1 td_locks 668 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks 667 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of 1 td_locks 666 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks 665 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of 1 td_locks 664 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks 663 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of 1 td_locks 662 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks 661 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of 1 td_locks 660 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks 659 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of 1 td_locks db> where Tracing pid 985 tid 100085 td 0xc37dd000 kdb_enter(c0b0c893,c0b0c893,c0b3ce37,d639cc8c,0,...) at kdb_enter+0x3a panic(c0b3ce37,c0b2b59e,5,c0b2b59e,c0bbef10,...) at panic+0x12c syscall(d639cd38) at syscall+0x46e Xint0x80_syscall() at Xint0x80_syscall+0x20 --- syscall (0, FreeBSD ELF32, nosys), eip = 0x280c4bbb, esp = 0xbfbfe59c, ebp = 0xbfbfe658 --- From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 08:00:14 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3F3616A418 for ; Fri, 25 Jan 2008 08:00:14 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by mx1.freebsd.org (Postfix) with ESMTP id 2877B13C47E for ; Fri, 25 Jan 2008 08:00:08 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so599606fgg.35 for ; Fri, 25 Jan 2008 00:00:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=wewvjPSO0aGtD4AABhCDerb+qm+l0BxWea3+jJCkeBk=; b=heZMwst3j4JTMrn2dFkm/V/eoTeBcX/4vyEFBbBHZSHdn0KNQBbTRDWb2MnMwV4iSPRJChyARz//efGqx/8vfvjXA1pzQsMGZ9VFuwsl8nIZgQ2jMjjgBFtqI0iYe53bA6Q9Xcm2OH+vSquV6XCAPU3gKU2uSYgp9nrXiHz81aQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=R24hL/qWNZwjgVuWXzVEpsqPQsrxxJxU9zXc27Qi0aANqCbPFQALb1TVNhbeHrf7ptnQPy6l2b+0kKaMUAzjO2NcWl/GDEN8iHZ3WYrl5HJQ3zaLCPv6tEILIBxBZ4055QC8WhIM+voG+/E7n4Eu6HBGtKydEry1V0huCzb0ZVw= Received: by 10.86.74.15 with SMTP id w15mr1551118fga.46.1201248007843; Fri, 25 Jan 2008 00:00:07 -0800 (PST) Received: by 10.86.53.7 with HTTP; Fri, 25 Jan 2008 00:00:07 -0800 (PST) Message-ID: <3bbf2fe10801250000k5852c2f2j5d1897c900096818@mail.gmail.com> Date: Fri, 25 Jan 2008 09:00:07 +0100 From: "Attilio Rao" Sender: asmrookie@gmail.com To: "Yar Tikhiy" In-Reply-To: <20080125075551.GB21633@comp.chem.msu.su> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <790a9fff0801150552l542a4238ofc12efe5fdb45fc2@mail.gmail.com> <20080115143924.GB57756@deviant.kiev.zoral.com.ua> <20080124122808.GA15600@freefall.freebsd.org> <3bbf2fe10801240518i6e18b2f5w84de652d4170c95b@mail.gmail.com> <20080124145811.GB78114@comp.chem.msu.su> <3bbf2fe10801240707o72b927cg74dbf9b7bbcd88fc@mail.gmail.com> <20080125075551.GB21633@comp.chem.msu.su> X-Google-Sender-Auth: 5d22ed6d6bbc235e Cc: Kostik Belousov , freebsd-current@freebsd.org Subject: Re: panic: System call lstat returning with 1 locks held X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 08:00:14 -0000 2008/1/25, Yar Tikhiy : > On Thu, Jan 24, 2008 at 04:07:43PM +0100, Attilio Rao wrote: > > 2008/1/24, Yar Tikhiy : > > > On Thu, Jan 24, 2008 at 02:18:56PM +0100, Attilio Rao wrote: > > > > 2008/1/24, Yar Tikhiy : > > > > > On Tue, Jan 15, 2008 at 04:39:24PM +0200, Kostik Belousov wrote: > > > > > > > > > > > > I think this could be related to the recent vn_lock()/VOP_LOCK() KPI changes. > > > > > > Please, add DEBUG_VFS_LOCKS to the kernel config, and do the > > > > > > show lockedvnods > > > > > > from the ddb prompt when the panic occurs. The witness does not track > > > > > > the lockmgr locks. > > > > > > > > > > I think I'm seeing the same panic on UFS. It's rather nasty: I > > > > > cannot rebuild CURRENT natively due to it so I have to build it > > > > > under 6-STABLE. My favourite way to trigger the panic reliably is > > > > > running `make install' in a simple port directory, e.g., portmaster, > > > > > but my system also panics during daily scripts run and, as already > > > > > said, if trying to build world. > > > > > > > > Yar, > > > > as it seems reproducible for you, can you please add this patch to the tree: > > > > http://www.freebsd.org/~attilio/debug_tdlocks.diff > > > > > > > > compile your kernel with: > > > > options KTR > > > > options KTR_COMPILE=(KTR_SPARE2) > > > > options KTR_MASK=(KTR_SPARE2) > > > > options KTR_ENTRIES=32768 > > > > > > > > and once kernel panics, at ddb prompts do: > > > > > show ktr > > > > > > Thank you for your instant response! > > > > > > The patched kernel is already being built, but I've got the following > > > question in the meanwhile: Should I have updated my kernel to get your > > > latest changes to kern_lock.c? Now my local copy of kern_lock.c is at > > > rev. 1.119, i.e., 1 revision behind today's change. > > > > As long as this patch still applies, it should not any meaningful difference. > > > > Thanks a lot for your effort of testing and reporting bugs! > > I don't deserve these kind words because I disinformed you seriously. > > My panic appears to be related not to UFS, but to NTFS. Namely I > have an NTFS volume mounted read-only at /ntfs. I have no idea why > the ports framework touches the /ntfs sub-tree, but not mounting > it in the first place makes the panic go away. (I still wonder why > my system would also panic during buildworld, which should not touch > my /ntfs at all... Now I'll try to do a buildworld w/o /ntfs mounted.) Well, this is still to be fixed :) > At the same time, dismounting the NTFS volume leads to an instant > panic of a similar kind: > > panic: System call unmount returning with 5 locks held > > More debug output is attached. > > So at least UFS doesn't seem affected by the panic. Excuse me for > my having provided wrong info. > > -- > Yar > > panic: System call unmount returning with 5 locks held > cpuid = 0 > KDB: enter: panic > [thread pid 985 tid 100085 ] > Stopped at kdb_enter+0x3a: movl $0,kdb_why > db> show lockedvn > Locked vnodes > db> sh ktr > 678 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks > 677 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks > 676 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks > 675 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of 1 td_locks > 674 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks > 673 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of 1 td_locks > 672 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks > 671 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of 1 td_locks > 670 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks > 669 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of 1 td_locks > 668 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks > 667 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of 1 td_locks > 666 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks > 665 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of 1 td_locks > 664 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks > 663 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of 1 td_locks > 662 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks > 661 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of 1 td_locks > 660 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of -1 td_locks > 659 (0xc37dd000:cpu0): _lockmgr: 0xc37dd000 bumping of 1 td_locks > db> where > Tracing pid 985 tid 100085 td 0xc37dd000 > kdb_enter(c0b0c893,c0b0c893,c0b3ce37,d639cc8c,0,...) at kdb_enter+0x3a > panic(c0b3ce37,c0b2b59e,5,c0b2b59e,c0bbef10,...) at panic+0x12c > syscall(d639cd38) at syscall+0x46e > Xint0x80_syscall() at Xint0x80_syscall+0x20 > --- syscall (0, FreeBSD ELF32, nosys), eip = 0x280c4bbb, esp = 0xbfbfe59c, ebp = 0xbfbfe658 --- Do you see any call to lockmgr_disown() in this ktr trace? Can you past relevant lines of it, otherwise? Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 09:15:43 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A72016A41A for ; Fri, 25 Jan 2008 09:15:43 +0000 (UTC) (envelope-from gahr@gahr.ch) Received: from cpanel03.rubas-s03.net (cpanel03.rubas-s03.net [195.182.222.73]) by mx1.freebsd.org (Postfix) with ESMTP id 4C5DC13C45A for ; Fri, 25 Jan 2008 09:15:43 +0000 (UTC) (envelope-from gahr@gahr.ch) Received: from 80-218-191-236.dclient.hispeed.ch ([80.218.191.236] helo=gahrtop.localhost) by cpanel03.rubas-s03.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1JIKf0-0002bU-3K; Fri, 25 Jan 2008 10:15:42 +0100 Message-ID: <4799A8AD.1000905@gahr.ch> Date: Fri, 25 Jan 2008 10:15:25 +0100 From: Pietro Cerutti User-Agent: Thunderbird 2.0.0.9 (X11/20071121) MIME-Version: 1.0 To: "M. Warner Losh" References: <47989278.6050802@gahr.ch> <20080124.213741.1628329459.imp@bsdimp.com> In-Reply-To: <20080124.213741.1628329459.imp@bsdimp.com> X-Enigmail-Version: 0.95.5 OpenPGP: id=9571F78E; url=http://www.gahr.ch/pgp Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enigAB1DC61B9B338309741A8B0B" X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cpanel03.rubas-s03.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - gahr.ch X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-current@freebsd.org Subject: Re: [Fwd: SMP in machine/params.h] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 09:15:43 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigAB1DC61B9B338309741A8B0B Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable M. Warner Losh wrote: > Why do you think that the SMP macro should be defined in > machine/param.h? I meant "set". I was having a problem understanding with the following (from machine/param.h): #ifdef SMP #define MAXCPU 16 #else #define MAXCPU 1 #endif /* SMP */ but as jhb@ said (see hackers@), they're not supposed to be exported to userland anyway. Maybe some #ifdef _KERNEL ..... #endif could help... >=20 > Warner --=20 Pietro Cerutti PGP Public Key: http://gahr.ch/pgp --------------enigAB1DC61B9B338309741A8B0B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHmaiywMJqmJVx944RCoEAAKCfzfgD71eCc0hrhHmn9S3EG9RKlwCgwNIP ZEKTFEFT7IkdTxTCaCnlDRA= =o4o+ -----END PGP SIGNATURE----- --------------enigAB1DC61B9B338309741A8B0B-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 04:47:34 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 773A316A418 for ; Fri, 25 Jan 2008 04:47:34 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.178]) by mx1.freebsd.org (Postfix) with ESMTP id 47E6F13C4DB for ; Fri, 25 Jan 2008 04:47:34 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so827734waf.3 for ; Thu, 24 Jan 2008 20:47:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=LyTu5SvtkwD7FjeZIQPQom4xUyIVj0+OTm5OvJOtraM=; b=juwKFIQwVyqZaTQt1FH7K02LwNL2yQm2BCetZXSp25HHaP4dzNQg42+8/dCzm6QBhEBwn2z5pEcRHlnDGSy2fC5G+6ZS1FwTkjU0FqqYxwMDlzhiJUG8IZEUZFS0ZAXQXsRWP8V6rH64tQ8vlXMvwUMc+7hPgiGU4Hv/gGwLr2Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=cdiuXQZ9/BFq8kxvyp7RdeZkEx+VjmhF0W9yZNBkQS0fqylC1/NOesVpmPbFQJrrpVXZZT1PmQ2RBasBEVlJuM2Us5N/EkUG3yCy2yZe5n8/oplgpzN6RrcQUeumzPnma6AZkAO5tV1EGYKFVUUJgEGopRLd03Oa9JMyy+UohDo= Received: by 10.114.178.1 with SMTP id a1mr1727204waf.135.1201234809013; Thu, 24 Jan 2008 20:20:09 -0800 (PST) Received: by 10.115.16.7 with HTTP; Thu, 24 Jan 2008 20:20:08 -0800 (PST) Message-ID: <4956a5e50801242020j41fea759v84720c62a246db63@mail.gmail.com> Date: Fri, 25 Jan 2008 01:20:08 -0300 From: Nenhum_de_Nos To: freebsd-current@freebsd.org In-Reply-To: <4956a5e50801242019m37675b90t7fbbb72d4d917960@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <012101c85cbe$3d93fef0$292d280a@friedman.net> <4795B6ED.8020902@beardz.net> <003901c85d02$96a78d60$292d280a@friedman.net> <4956a5e50801242019m37675b90t7fbbb72d4d917960@mail.gmail.com> X-Mailman-Approved-At: Fri, 25 Jan 2008 12:15:48 +0000 Subject: IPSEC on 7.0-PRERELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 04:47:34 -0000 ---------- Forwarded message ---------- From: Nenhum_de_Nos Date: Jan 25, 2008 1:19 AM Subject: Re: IPSEC on 7.0-PRERELEASE To: "Dr. Aharon Friedman" On Jan 22, 2008 11:25 AM, Dr. Aharon Friedman wrote: > This looks like the solution. It did pass compile. I have not run it yet, > but I am sure it will work. Here is the configuration part for IPSEC: > > > > options IPSEC #IP security (requires device crypto) > > options IPSEC_FILTERTUNNEL #filter ipsec packets from a > tunnel > > device enc #IPsec interface > > device crypto # core crypto support > > device cryptodev # /dev/crypto for access to h/w > > > > Aharon I have a IPSec tunnel over gif ifaces and all ok. was I supposed to change anything ? thanks, matheus -- We will call you cygnus, The God of balance you shall be -- We will call you cygnus, The God of balance you shall be From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 14:00:06 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9168A16A480 for ; Fri, 25 Jan 2008 14:00:06 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 77B6A13C468 for ; Fri, 25 Jan 2008 14:00:06 +0000 (UTC) (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 EAC0746B0F; Fri, 25 Jan 2008 09:00:05 -0500 (EST) Date: Fri, 25 Jan 2008 14:00:05 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: bazzoola In-Reply-To: <2C14CF79-F269-4622-9E99-89BC20D73F59@gmail.com> Message-ID: <20080125135906.W15118@fledge.watson.org> References: <2C14CF79-F269-4622-9E99-89BC20D73F59@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: Noise ratio on -CURRENT has increased recently X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 14:00:06 -0000 On Thu, 24 Jan 2008, bazzoola wrote: > I come from an academic background and I have been reading and enjoying > -CURRENT for years I use it to learn and adapt new ideas in my research. I > just wanted to say that recently, I noticed that the noise ratio here has > increased more than 'the usual' and it really saddens me to see intelligent > and very active developers throwing bricks at each other on this public > list. > > I have always liked this educated and kind community of FreeBSD and I hope > it remains like that. I agree, and have had similar worries. I expect a moderate amount of it is because a lot of people are sitting around twiddling their thumbs waiting for 7.0 to ship so they can get "back to business" with the pent-up works in progress. Hopefully that will be remedied shortly. :-) Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 14:27:49 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF19416A41A for ; Fri, 25 Jan 2008 14:27:49 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 6834213C458 for ; Fri, 25 Jan 2008 14:27:48 +0000 (UTC) (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 8430847490; Fri, 25 Jan 2008 09:27:48 -0500 (EST) Date: Fri, 25 Jan 2008 14:27:48 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Aristedes Maniatis In-Reply-To: Message-ID: <20080125142322.E15118@fledge.watson.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: freebsd 7 release process X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 14:27:49 -0000 On Fri, 25 Jan 2008, Aristedes Maniatis wrote: > How can non-committers like myself keep up to date with the progress of > freebsd releases? I read stable, current and cvs mailing lists. I've even > looked at the qa mailing list but it looks completely abandoned (perhaps the > links to it should be removed from the web site). > > I see this page: > > http://www.freebsd.org/releases/7.0R/todo.html > > but it tells me that we are just waiting for Robert Watson to complete > testing of the MAC framework changes. Nothing in commit logs or mailing > lists correlates to that so I assume it is incorrect. > > Really, all I want to do is to get a handle on the known outstanding bugs, > but the FreeBSD bug tracking system is very crappy (compared to almost all > other open source projects I use or am involved in) and has no way to look > at bugs by reported-in version or target release. So my question is: how do > other people know what is happening? Does re have a mailing list somewhere I > can read? > > I know many people are putting in vast amount of effort here, so this is not > a criticism of the delays. Just without any regular bulletins, emails to the > mailing lists, bug tracker or web site updates I can't tell what bugs are > left, what are fixed and what I need to be aware of. Thanks for the prod -- I've update the todo list to reflect the 7.0RC2 issues I'm aware of (that is, the things currently blocking building and shipping RC2). If I bump into any others, I'll add them. It takes a bit for the web site to rebuild, so I've attached the current pending TODO items for 7.0RC2 here: A race in TCP will lead to very occasional returning of 0.0.0.0:0 rather than the TCP accept Gleb Smirnoff, correct IP address via the race condition In progress Robert Watson socket address returned by accept(). A patch is in HEAD and RELENG_7, and will shortly be merged to RELENG_7_0 for inclusion in 7.0RC2. Races in the sleepq implementation will occasionally result in sleeps with timeouts failing to wake up. A patch is sleepq race in HEAD and will shortly be condition In progress John Baldwin merged to RELENG_7 and RELENG_7_0 for inclusion in 7.0RC2. The sleepq code is being reviewed for other possibly related bugs and further fixes may be forthcoming. Multiple race conditions in the tty/pty code have lead to occasional panics. One set of pty race In progress Konstantin problems has been fixed, but condition Belousov others are still being explored It is aniticipated that the remaining problems will be fixed for 7.0RC2. There have been status e-mails from Ken ... but only to the private developers mailing list. I've asked him if he could start also sending them to current@/stable@, it was just an oversight that they weren't being sent there. We're extremely close to a 7.0RC2, which with any luck will be the last RC, btw. 7.0 is looking like one of the most stable ".0" releases we've ever done, and has some very nice features... Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 14:29:15 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4450716A418 for ; Fri, 25 Jan 2008 14:29:15 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from phoebe.cse.buffalo.edu (phoebe.cse.buffalo.edu [128.205.32.89]) by mx1.freebsd.org (Postfix) with ESMTP id 1C62913C457 for ; Fri, 25 Jan 2008 14:29:14 +0000 (UTC) (envelope-from kensmith@cse.Buffalo.EDU) Received: from [128.205.32.76] (bauer.cse.buffalo.edu [128.205.32.76]) (authenticated bits=0) by phoebe.cse.buffalo.edu (8.14.1/8.13.7) with ESMTP id m0PET6jb076233 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Jan 2008 09:29:07 -0500 (EST) (envelope-from kensmith@cse.buffalo.edu) From: Ken Smith To: Aristedes Maniatis In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-1QzS9USnDmntAQVIU4tc" Organization: U. Buffalo CSE Department Date: Fri, 25 Jan 2008 09:29:06 -0500 Message-Id: <1201271346.36488.23.camel@bauer.cse.buffalo.edu> Mime-Version: 1.0 X-Mailer: Evolution 2.12.1 FreeBSD GNOME Team Port X-DCC-Buffalo.EDU-Metrics: phoebe.cse.buffalo.edu 1336; Body=0 Fuz1=0 Fuz2=0 X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on phoebe.cse.buffalo.edu Cc: freebsd-current@freebsd.org Subject: Re: freebsd 7 release process X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 14:29:15 -0000 --=-1QzS9USnDmntAQVIU4tc Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2008-01-25 at 10:49 +1100, Aristedes Maniatis wrote: > How can non-committers like myself keep up to date with the progress =20 > of freebsd releases? I read stable, current and cvs mailing lists. =20 > I've even looked at the qa mailing list but it looks completely =20 > abandoned (perhaps the links to it should be removed from the web site). >=20 > I see this page: >=20 > http://www.freebsd.org/releases/7.0R/todo.html >=20 > but it tells me that we are just waiting for Robert Watson to complete =20 > testing of the MAC framework changes. Nothing in commit logs or =20 > mailing lists correlates to that so I assume it is incorrect. >=20 > Really, all I want to do is to get a handle on the known outstanding =20 > bugs, but the FreeBSD bug tracking system is very crappy (compared to =20 > almost all other open source projects I use or am involved in) and has =20 > no way to look at bugs by reported-in version or target release. So my =20 > question is: how do other people know what is happening? Does re have =20 > a mailing list somewhere I can read? >=20 > I know many people are putting in vast amount of effort here, so this =20 > is not a criticism of the delays. Just without any regular bulletins, =20 > emails to the mailing lists, bug tracker or web site updates I can't =20 > tell what bugs are left, what are fixed and what I need to be aware of. >=20 Yeah, sorry. I've got communication issues that run so deep at this point I've basically given up on "fixing it" for this release and will try again from scratch next release. [ Anybody wanna be a secretary? No pay, no benefits, and likely no praise/recognition other than me saying "Thanks" periodically but you'll make lots of people happy. Applications welcome. :-] I'll see if I can do a sweep through mailing lists with a quick note and fix up some of the Web stuff this weekend, I actually have a bit of a breather because 6.3-REL is done and I'll need to wait for Monday to do the 7.0-RC2 builds. Quick summary we're shooting for getting 7.0-RC2 done Real Soon Now (originally targetted this weekend but three things came up through the past day or two that will delay it to Monday-ish) and we hope that's the last of the RCs. Release about two weeks after RC2. Status updates in general should have been more regular (sorry!) but in-depth ones are actually harder and less "useful" than it seems. We've *thought* we were ready to proceed with -RELEASE for a while now. To me that's what Release Candidate *means*. But what's been happening lately has been a relatively critical bug pops up on a mailing list, a developer immediately notices and starts working it through, and a day or two or three later it's patched and a day or two or three after that it's MFCed. It's not like we need to "advertise" for someone to fix the thing, and it progresses as fast as can be expected given "develop fix, test, get a reviewer or two to look at it, commit to head, wait a bit, then MFC it". But it adds days... We wouldn't have entered the RC phase if we knew there were as yet unresolved bugs so big we wouldn't release until they're fixed (you can't set timetables of peoples' work in an all-volunteer project) so at this point we're just reacting to new ones that are deemed so critical they need to be fixed before release. Hence lack of an "items list" in the form you're asking about. If one existed we wouldn't be in this phase of the release. That said we do know there are still bugs. But we are an all volunteer project. If I waited for all the bugs to be fixed we'd never do a release. Except for the small handful of bugs that have cropped up and are "in progress" 7.0 is actually in pretty good shape, especially for a ".0 release". --=20 Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel | --=-1QzS9USnDmntAQVIU4tc Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBHmfIo/G14VSmup/YRAlcEAKCPb7PiLQ6ROSpMLp3kXnNaQIKlZACggAeb XitAbse7HyjqfLGOhC4Lo0I= =NoIY -----END PGP SIGNATURE----- --=-1QzS9USnDmntAQVIU4tc-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 17:24:38 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBBE816A420 for ; Fri, 25 Jan 2008 17:24:38 +0000 (UTC) (envelope-from freebsd@stigascorp.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7FB8513C461 for ; Fri, 25 Jan 2008 17:24:38 +0000 (UTC) (envelope-from freebsd@stigascorp.com) Received: by py-out-1112.google.com with SMTP id u52so1173086pyb.10 for ; Fri, 25 Jan 2008 09:24:37 -0800 (PST) Received: by 10.65.44.5 with SMTP id w5mr4769139qbj.45.1201280144341; Fri, 25 Jan 2008 08:55:44 -0800 (PST) Received: by 10.64.150.17 with HTTP; Fri, 25 Jan 2008 08:55:44 -0800 (PST) Message-ID: <75988d070801250855h352c1d9chc7f54ebcd63a5bef@mail.gmail.com> Date: Fri, 25 Jan 2008 11:55:44 -0500 From: "FreeBSD User" To: freebsd-current@freebsd.org MIME-Version: 1.0 X-Mailman-Approved-At: Fri, 25 Jan 2008 17:46:17 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: installation problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2008 17:24:38 -0000 Hello, I'm not sure if this is the correct mailing list. I have tried installing FreeBSD 7.0-Current for amd64, and I am having problems with my mouse and video card. Firstly my hardware is as follows: Gigabyte p35-ds3r motherboard Intel Core 2 Quad 2.4GHz (Q6600) NVidia 8400GS Microsoft Comfort Optical 3000 mouse Microsoft Natural Ergonomic Keyboard 4000 Problem 1: The mouse is not working at all. When I look at the output of "dmesg", I see the mouse (ums0), however no movement. Problem 2: I cannot get X started. I get the following errors: Failed to load module "nv" (module does not exist, 0) Failed to load module "mouse" (module does not exist, 0) Failed to load module "kbd" (module does not exist, 0) No drivers available Help! Chris From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 17:59:43 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C4D616A419 for ; Fri, 25 Jan 2008 17:59:43 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id 9CFE613C447 for ; Fri, 25 Jan 2008 17:59:42 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: by blah.sun-fish.com (Postfix, from userid 1002) id 3F8D71B10EBB; Fri, 25 Jan 2008 18:59:41 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on blah.cmotd.com X-Spam-Level: X-Spam-Status: No, score=-10.6 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.3 Received: from hater.haters.org (unknown [192.168.25.10]) by blah.sun-fish.com (Postfix) with ESMTP id 205CA1B10C26 for ; Fri, 25 Jan 2008 18:59:38 +0100 (CET) Message-ID: <479A2389.2000802@moneybookers.com> Date: Fri, 25 Jan 2008 19:59:37 +0200 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.9 (X11/20071120) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.91.2/5550/Fri Jan 25 08:02:45 2008 on blah.cmotd.com X-Virus-Status: Clean Subject: FreeBSD 7, bridge, PF and syn flood = very bad performance X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 17:59:43 -0000 Greetings, Does anyone try to see PF with "keep state" in action when under syn flood attack? I tried to get some help in freebsd-pf@, because the test firewall, that I build hardly can handle 2-5MB/s syn flood. Unfortunately I do not saw useful advice. The problem is that a quad core bridge firewall running freebsd 7 amd64 with PF is near useless and can't handle "small" SYN ddos. Here is the schema that I'm testing: web server (freebsd) - freebsd (bridged interfaces) - gigabit switch - clients + flooders In this configuration ~25MB/s syn flood (and I think this limit is because of my switch) is not a problem and the web server responds without a problem. With this configuration netperf -l 610 -p 10303 -H 10.3.3.1 shows 116MB/s stable speed , so I guess there are no problems with cables, hardware and etc :) But when I start pf (see below the config file) the traffic drops to 2-3MB/s and the web server is hardly accessible. It seems that device polling helps a lot in this situation, and at least the bridge firewall is accessible. Without "polling" the firewall is so heavily loaded that even commands like "date" take few seconds to finish, with 2 cores at ~100% idle at same time. I have "flat profiles" from hwpmc, and I think it indicates a problem: (bridge, pf enabled, polling enabled, sched_ule - I have profiles and for other combinations too if needed) % cumulative self self total time seconds seconds calls ms/call ms/call name 24.0 268416.00 268416.00 0 100.00% _mtx_lock_sleep [1] 6.7 343572.50 75156.50 0 100.00% pf_state_compare_ext_gwy [2] 6.7 418405.50 74833.00 0 100.00% pf_src_compare [3] 3.9 462298.50 43893.00 0 100.00% pf_state_compare_lan_ext [4] 3.6 503019.50 40721.00 0 100.00% pf_test [5] 3.2 538671.50 35652.00 0 100.00% pf_test_tcp [6] 3.1 573743.50 35072.00 0 100.00% bcopy [7] 2.3 599406.50 25663.00 0 100.00% bridge_pfil [8] 2.0 622096.50 22690.00 0 100.00% pf_state_compare_id [9] 2.0 644331.50 22235.00 0 100.00% pfsync_pack_state [10] 1.5 661563.50 17232.00 0 100.00% uma_zalloc_arg [11] 1.3 676296.50 14733.00 0 100.00% bzero [12] 1.3 690842.00 14545.50 0 100.00% bus_dmamap_load_mbuf_sg [13] 1.2 704521.50 13679.50 0 100.00% uma_zfree_arg [14] 1.2 717554.50 13033.00 0 100.00% bridge_rtnode_lookup [15] 1.2 730575.50 13021.00 0 100.00% _rw_rlock [16] 1.1 743076.50 12501.00 0 100.00% rn_match [17] 1.0 754016.50 10940.00 0 100.00% bridge_forward [18] 1.0 764766.00 10749.50 0 100.00% em_encap [19] 0.9 775400.00 10634.00 0 100.00% _rw_runlock [20] ........ Also when running without polling top -S shows that external em0 interface's taskq takes 100% CPU The situation is even worse when running with SCHED_BSD. Here is my test pf.conf quick #macros ext_if="em0" int_if="em1" br_if="bridge0" www="10.3.3.1" #sets set skip on lo0 set skip on $int_if set skip on $br_if set limit states 20000000 set limit src-nodes 19000000 set optimization aggressive table persist file "/etc/abusive_hosts" block log quick from to any block log quick from any to pass in on $ext_if proto tcp from any to $www port { 80, 443 } flags S/SA keep state \ (source-track rule, max-src-conn-rate 150/10, max-src-states 500, max-src-nodes 4000000, overload flush global) -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 18:29:40 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E374116A41A for ; Fri, 25 Jan 2008 18:29:39 +0000 (UTC) (envelope-from rermilov@team.vega.ru) Received: from mail.vega.ru (infra.dev.vega.ru [90.156.167.14]) by mx1.freebsd.org (Postfix) with ESMTP id 9F2C413C4EA for ; Fri, 25 Jan 2008 18:29:39 +0000 (UTC) (envelope-from rermilov@team.vega.ru) Received: from [87.242.97.68] (port=57757 helo=edoofus.dev.vega.ru) by mail.vega.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1JISxt-0006ri-QU for current@FreeBSD.org; Fri, 25 Jan 2008 18:07:45 +0000 Received: from edoofus.dev.vega.ru (localhost [127.0.0.1]) by edoofus.dev.vega.ru (8.14.2/8.14.2) with ESMTP id m0PI7esR080205 for ; Fri, 25 Jan 2008 21:07:40 +0300 (MSK) (envelope-from rermilov@team.vega.ru) Received: (from ru@localhost) by edoofus.dev.vega.ru (8.14.2/8.14.2/Submit) id m0PI7eM9080204 for current@FreeBSD.org; Fri, 25 Jan 2008 21:07:40 +0300 (MSK) (envelope-from rermilov@team.vega.ru) X-Authentication-Warning: edoofus.dev.vega.ru: ru set sender to rermilov@team.vega.ru using -f Date: Fri, 25 Jan 2008 21:07:40 +0300 From: Ruslan Ermilov To: current@FreeBSD.org Message-ID: <20080125180740.GA1646@team.vega.ru> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="/9DWx/yDrRhgMJTb" Content-Disposition: inline User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Subject: minidumps are unsafe on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2008 18:29:40 -0000 --/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, Kernel minidumps on amd64 SMP can write beyond the bounds of the configured dump device causing (as in our case) the file system data following swap partition to be overwritten with the dump contents. The problem is that while we're in the process of dumping mapped physical pages via a bitmap (in minidump_machdep.c), other CPUs continue to work and may modify page mappings of processes. This in turn causes the modifications to pv_entries, which in turn modifies the bitmap of pages to dump. As the result, we can dump more pages than we've calculated, and since dumps are written to the end of the dump device, we may end up overwriting it. The attached patch mitigates the problem, but the real solution seems to be to disable interrupts (there's an XXX about this in kern_shutdown.c before calling doadump()), and stopping other CPUs, so we don't modify page tables while we're dumping. This only affects 7.x/8.x amd64 SMP systems configured with minidump. i386 systems aren't affected. Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=p Index: minidump_machdep.c =================================================================== RCS file: /home/ncvs/src/sys/amd64/amd64/minidump_machdep.c,v retrieving revision 1.2 diff -u -p -r1.2 minidump_machdep.c --- minidump_machdep.c 5 Dec 2006 11:31:33 -0000 1.2 +++ minidump_machdep.c 25 Jan 2008 17:47:49 -0000 @@ -60,6 +60,7 @@ int vm_page_dump_size; static struct kerneldumpheader kdh; static off_t dumplo; +static int zz = 0; /* Handle chunked writes. */ static size_t fragsz; @@ -68,6 +69,9 @@ static size_t counter, progress; CTASSERT(sizeof(*vm_page_dump) == 8); +static void _dump_add_page(vm_paddr_t pa); +static void _dump_drop_page(vm_paddr_t pa); + static int is_dumpable(vm_paddr_t pa) { @@ -239,6 +243,7 @@ minidumpsys(struct dumperinfo *di) } /* Calculate dump size. */ + zz = 1; dumpsize = ptesize; dumpsize += round_page(msgbufp->msg_size); dumpsize += round_page(vm_page_dump_size); @@ -251,7 +256,7 @@ minidumpsys(struct dumperinfo *di) if (is_dumpable(pa)) { dumpsize += PAGE_SIZE; } else { - dump_drop_page(pa); + _dump_drop_page(pa); } bits &= ~(1ul << bit); } @@ -383,9 +388,11 @@ minidumpsys(struct dumperinfo *di) /* Signal completion, signoff and exit stage left. */ di->dumper(di->priv, NULL, 0, 0, 0); printf("\nDump complete\n"); + zz = 0; return; fail: + zz = 0; if (error < 0) error = -error; @@ -397,8 +404,8 @@ minidumpsys(struct dumperinfo *di) printf("\n** DUMP FAILED (ERROR %d) **\n", error); } -void -dump_add_page(vm_paddr_t pa) +static void +_dump_add_page(vm_paddr_t pa) { int idx, bit; @@ -409,7 +416,20 @@ dump_add_page(vm_paddr_t pa) } void -dump_drop_page(vm_paddr_t pa) +dump_add_page(vm_paddr_t pa) +{ + + if (zz) { + printf("delaying %s\n", __func__); + while (zz) + DELAY(1000000); + printf("resuming %s\n", __func__); + } + _dump_add_page(pa); +} + +static void +_dump_drop_page(vm_paddr_t pa) { int idx, bit; @@ -418,3 +438,16 @@ dump_drop_page(vm_paddr_t pa) bit = pa & 63; atomic_clear_long(&vm_page_dump[idx], 1ul << bit); } + +void +dump_drop_page(vm_paddr_t pa) +{ + + if (zz) { + printf("delaying %s\n", __func__); + while (zz) + DELAY(1000000); + printf("resuming %s\n", __func__); + } + _dump_drop_page(pa); +} --/9DWx/yDrRhgMJTb-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 18:38:27 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91E3216A421; Fri, 25 Jan 2008 18:38:27 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46]) by mx1.freebsd.org (Postfix) with ESMTP id 7E9E913C468; Fri, 25 Jan 2008 18:38:27 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 37D7E8C098; Fri, 25 Jan 2008 12:38:27 -0600 (CST) Date: Fri, 25 Jan 2008 12:38:27 -0600 To: freebsd-current@FreeBSD.org Message-ID: <20080125183827.GB21911@soaustin.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.13 (2006-08-11) From: linimon@lonesome.com (Mark Linimon) X-Mailman-Approved-At: Fri, 25 Jan 2008 18:58:45 +0000 Cc: linimon@FreeBSD.org Subject: upcoming bugathon this weekend X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-bugbusters@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2008 18:38:27 -0000 If you're interested in helping out on our PR database problems, please see my posting on freebsd-bugbusters@: We're having a bugathon this weekend, with the agenda being mostly to figure out where we are, who would like to help, and coming up with ways that they can do so. Followups to freebsd-bugbusters@, please. mcl From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 19:23:19 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 226AD16A473 for ; Fri, 25 Jan 2008 19:23:19 +0000 (UTC) (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 C363E13C4CC for ; Fri, 25 Jan 2008 19:23:18 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id m0PIsM8F082488; Fri, 25 Jan 2008 11:54:22 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <479A305E.3020801@samsco.org> Date: Fri, 25 Jan 2008 11:54:22 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.11) Gecko/20071128 SeaMonkey/1.1.7 MIME-Version: 1.0 To: Ruslan Ermilov References: <20080125180740.GA1646@team.vega.ru> In-Reply-To: <20080125180740.GA1646@team.vega.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Fri, 25 Jan 2008 11:54:22 -0700 (MST) X-Spam-Status: No, score=-1.4 required=5.4 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: current@freebsd.org Subject: Re: minidumps are unsafe on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2008 19:23:19 -0000 Ruslan Ermilov wrote: > Hi, > > Kernel minidumps on amd64 SMP can write beyond the bounds > of the configured dump device causing (as in our case) the > file system data following swap partition to be overwritten > with the dump contents. > > The problem is that while we're in the process of dumping > mapped physical pages via a bitmap (in minidump_machdep.c), > other CPUs continue to work and may modify page mappings of > processes. This in turn causes the modifications to > pv_entries, which in turn modifies the bitmap of pages to > dump. As the result, we can dump more pages than we've > calculated, and since dumps are written to the end of the > dump device, we may end up overwriting it. > > The attached patch mitigates the problem, but the real solution > seems to be to disable interrupts (there's an XXX about this > in kern_shutdown.c before calling doadump()), and stopping > other CPUs, so we don't modify page tables while we're dumping. > > This only affects 7.x/8.x amd64 SMP systems configured with > minidump. i386 systems aren't affected. > Is this a case where you are manually triggering a dump on a system that is otherwise running fine? I thought that crashes already disabled interrupts and made an attempt to stop other CPUs. That's why there is dump-specific code in every storage driver in the first place; it implements polled i/o so that crashdump i/o can take place with interrupts disabled. If it's a case where interrupts aren't actually getting disabled, then that's one thing. If it's a case where you're trying to fix something that isn't broken, then I'm very cautious about the added complexity that you're proposing. Scott From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 20:10:48 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42A7F16A418; Fri, 25 Jan 2008 20:10:48 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0F53613C457; Fri, 25 Jan 2008 20:10:47 +0000 (UTC) (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 A66594821B; Fri, 25 Jan 2008 15:10:47 -0500 (EST) Date: Fri, 25 Jan 2008 20:10:47 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Scott Long In-Reply-To: <479A305E.3020801@samsco.org> Message-ID: <20080125195603.I37258@fledge.watson.org> References: <20080125180740.GA1646@team.vega.ru> <479A305E.3020801@samsco.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@freebsd.org Subject: Re: minidumps are unsafe on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2008 20:10:48 -0000 On Fri, 25 Jan 2008, Scott Long wrote: > Is this a case where you are manually triggering a dump on a system that is > otherwise running fine? I thought that crashes already disabled interrupts > and made an attempt to stop other CPUs. That's why there is dump-specific > code in every storage driver in the first place; it implements polled i/o so > that crashdump i/o can take place with interrupts disabled. If it's a case > where interrupts aren't actually getting disabled, then that's one thing. > If it's a case where you're trying to fix something that isn't broken, then > I'm very cautious about the added complexity that you're proposing. Unfortunately, we don't really do this today -- we do stop the other CPUs when we enter the debugger, but we restart them when we leave, and the dump code runs outside of the debugger context. I ran into this problem when working on textdumps, as common storage drivers attempt to acquire locks in their dump path. Instead of writing out DDB output incrementally block-at-a-time, I have to buffer it all and then generate it at the normal dump point after leaving the debugger. In terms of generally improving robustness of the debugging environment, I've been pondering the following: - Dump routines run from the KDB context, so that they get the protections associated with running in the debugger. In particular, they need a more reliable assumption that the rest of the kernel is halted. I'm a bit surprised we haven't been bitten by this more in the past... - A more SMP-safe passage into the debugger, especially from panic(). We should disable interrupts immediately on panic() to prevent preemption on the panicking CPU by an interrupt. We should write any state to pass into the debugger into a per-CPU buffer to be picked up after kdb_trap() has popped us into the debugger. The panic message should be printed by KDB, and not using printf(), which is prone to preemption especially on serial consoles. - Dump routines pass through a bounds checking block write call. Right now they directly invoke di->dumper(), and the caller is responsible for not asking for blocks outside the swap partition. A wrapper on the order of dump_blockwrite() should do the bounds checking to add robustness (obviously, callers should also place their blocks correctly). I'm almost certainly not the right person to look at making dumper routines work in KDB, but I can look at improving the reliability of getting into KDB, as well as passing data into it more reliably. I'm happy to let someone else pick this up and run with it, though, as it will be a ways down on my TODO list for a bit. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 20:47:41 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14C4916A468 for ; Fri, 25 Jan 2008 20:47:41 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail10.syd.optusnet.com.au (mail10.syd.optusnet.com.au [211.29.132.191]) by mx1.freebsd.org (Postfix) with ESMTP id 9E99A13C447 for ; Fri, 25 Jan 2008 20:47:40 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c220-239-20-82.belrs4.nsw.optusnet.com.au [220.239.20.82]) by mail10.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m0PKlaEi016717 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Jan 2008 07:47:38 +1100 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.1) with ESMTP id m0PKlaGp053338; Sat, 26 Jan 2008 07:47:36 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m0PKla56053337; Sat, 26 Jan 2008 07:47:36 +1100 (EST) (envelope-from peter) Date: Sat, 26 Jan 2008 07:47:35 +1100 From: Peter Jeremy To: Scott Long Message-ID: <20080125204735.GQ53741@server.vk2pj.dyndns.org> References: <20080125180740.GA1646@team.vega.ru> <479A305E.3020801@samsco.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nVMJ2NtxeReIH9PS" Content-Disposition: inline In-Reply-To: <479A305E.3020801@samsco.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.17 (2007-11-01) Cc: current@freebsd.org Subject: Re: minidumps are unsafe on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2008 20:47:41 -0000 --nVMJ2NtxeReIH9PS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 25, 2008 at 11:54:22AM -0700, Scott Long wrote: >Ruslan Ermilov wrote: >> Kernel minidumps on amd64 SMP can write beyond the bounds >> of the configured dump device causing (as in our case) the >> file system data following swap partition to be overwritten >> with the dump contents. =2E.. >> This only affects 7.x/8.x amd64 SMP systems configured with >> minidump. i386 systems aren't affected. >>=20 > >Is this a case where you are manually triggering a dump on a >system that is otherwise running fine? IMO, this is irrelevant. Over-writing data outside the defined partition boundaries is unacceptable on a production system. It would be nice if there were some sanity checks to pick this up. Somewhere down the chain, one of the lower-level write functions should verify that each write is contained within [dumperinfo.mediaoffset .. dumperinfo.mediaoffset+dumperinfo.mediasize) Ideally this would be inside dumperinfo.dumper() but that function doesn't currently get passed dumperinfo so this change is too intrusive for 7.0. Likewise dumperinfo.dumper() is called in too many places to reasonably add the code to the callers. Maybe a MI wrapper function replacing each of the existing dumperinfo.dumper() calls would be the least intrusive fix: Replace each existing di->dumper(di->priv, va, pa, offset, len); with dumper_write(di, va, pa, offset, len); and add the following in (probably) kern/kern_shutdown: void dumper_write(struct dumperinfo *di, void *va, vm_offset_t *pa, off_t offset= , size_t length) { if (offset >=3D di->mediaoffset && offset + size <=3D di->mediaoffset + di->mediasize) di->dumper(di->priv, va, pa, offset, len); else printf("Attempt to write outside dumpdev boundaries ignored\n"); } >that's one thing. If it's a case where you're trying to fix >something that isn't broken, then I'm very cautious about the >added complexity that you're proposing. I'd suggest that, for 7.0-RELEASE, either amd64 minidumps, or manually triggered amd64 minidumps, needs to be disabled (or hidden behind a "do you really want to shoot yourself in the foot" check). This can be noted in ERRATA and fixed in 7.1. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --nVMJ2NtxeReIH9PS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFHmkrn/opHv/APuIcRAo0eAJ967HBcIXrv2bm1scPpmqGb84c2ngCeJy7n WyKR1G+l6fDcDYXbdryelpw= =qkIM -----END PGP SIGNATURE----- --nVMJ2NtxeReIH9PS-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 21:04:01 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA10A16A421; Fri, 25 Jan 2008 21:04:01 +0000 (UTC) (envelope-from rermilov@team.vega.ru) Received: from mail.vega.ru (infra.dev.vega.ru [90.156.167.14]) by mx1.freebsd.org (Postfix) with ESMTP id 7B5EE13C455; Fri, 25 Jan 2008 21:04:00 +0000 (UTC) (envelope-from rermilov@team.vega.ru) Received: from [87.242.97.68] (port=1155 helo=edoofus.dev.vega.ru) by mail.vega.ru with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from ) id 1JIViQ-000EfV-Dl; Fri, 25 Jan 2008 21:03:58 +0000 Received: from edoofus.dev.vega.ru (localhost [127.0.0.1]) by edoofus.dev.vega.ru (8.14.2/8.14.2) with ESMTP id m0PL3q3i082664; Sat, 26 Jan 2008 00:03:52 +0300 (MSK) (envelope-from rermilov@team.vega.ru) Received: (from ru@localhost) by edoofus.dev.vega.ru (8.14.2/8.14.2/Submit) id m0PL3q0I082663; Sat, 26 Jan 2008 00:03:52 +0300 (MSK) (envelope-from rermilov@team.vega.ru) X-Authentication-Warning: edoofus.dev.vega.ru: ru set sender to rermilov@team.vega.ru using -f Date: Sat, 26 Jan 2008 00:03:52 +0300 From: Ruslan Ermilov To: Robert Watson Message-ID: <20080125210352.GA82354@team.vega.ru> References: <20080125180740.GA1646@team.vega.ru> <479A305E.3020801@samsco.org> <20080125195603.I37258@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080125195603.I37258@fledge.watson.org> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: current@FreeBSD.org Subject: Re: minidumps are unsafe on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2008 21:04:02 -0000 On Fri, Jan 25, 2008 at 08:10:47PM +0000, Robert Watson wrote: > > On Fri, 25 Jan 2008, Scott Long wrote: > Hmm. Somehow I didn't get your email, only this one. >> Is this a case where you are manually triggering a dump on a system that >> is otherwise running fine? Not quite. We were testing how dumps work on GEOM mirror, to set it up on production boxes, when we found that dumping destroys the mirror itself. Our testing includes setting debug.kdb.panic=1 to trigger a panic and a dump. Our test system has four dual-core CPUs. >> I thought that crashes already disabled >> interrupts and made an attempt to stop other CPUs. That's why there is >> dump-specific code in every storage driver in the first place; it >> implements polled i/o so that crashdump i/o can take place with interrupts >> disabled. If it's a case where interrupts aren't actually getting >> disabled, then that's one thing. If it's a case where you're trying to fix >> something that isn't broken, then I'm very cautious about the added >> complexity that you're proposing. > > Unfortunately, we don't really do this today -- we do stop the other CPUs > when we enter the debugger, but we restart them when we leave, and the dump > code runs outside of the debugger context. I ran into this problem when > working on textdumps, as common storage drivers attempt to acquire locks in > their dump path. Instead of writing out DDB output incrementally > block-at-a-time, I have to buffer it all and then generate it at the normal > dump point after leaving the debugger. > Yes, and about interrupts, we don't really disable them now: : static void : boot(int howto) : { : [...] : /* XXX This doesn't disable interrupts any more. Reconsider? */ : splhigh(); : : if ((howto & (RB_HALT|RB_DUMP)) == RB_DUMP && !cold && !dumping) : doadump(); > In terms of generally improving robustness of the debugging environment, > I've been pondering the following: > > - Dump routines run from the KDB context, so that they get the protections > associated with running in the debugger. In particular, they need a more > reliable assumption that the rest of the kernel is halted. I'm a bit > surprised we haven't been bitten by this more in the past... > > - A more SMP-safe passage into the debugger, especially from panic(). We > should disable interrupts immediately on panic() to prevent preemption on > the panicking CPU by an interrupt. We should write any state to pass into > the debugger into a per-CPU buffer to be picked up after kdb_trap() has > popped us into the debugger. The panic message should be printed by KDB, > and not using printf(), which is prone to preemption especially on serial > consoles. > > - Dump routines pass through a bounds checking block write call. Right now > they directly invoke di->dumper(), and the caller is responsible for not > asking for blocks outside the swap partition. A wrapper on the order of > dump_blockwrite() should do the bounds checking to add robustness > (obviously, callers should also place their blocks correctly). > > I'm almost certainly not the right person to look at making dumper routines > work in KDB, but I can look at improving the reliability of getting into > KDB, as well as passing data into it more reliably. I'm happy to let > someone else pick this up and run with it, though, as it will be a ways > down on my TODO list for a bit. > While experimenting, I also found that to safely "call doadump" from the debugger, and then be able to "continue", one needs this: %%% Index: kern_shutdown.c =================================================================== RCS file: /home/ncvs/src/sys/kern/kern_shutdown.c,v retrieving revision 1.188 diff -u -p -r1.188 kern_shutdown.c --- kern_shutdown.c 19 Jan 2008 17:36:22 -0000 1.188 +++ kern_shutdown.c 25 Jan 2008 20:54:34 -0000 @@ -249,6 +249,7 @@ doadump(void) else #endif dumpsys(&dumper); + dumping--; } static int %%% Some code (ata(4) in my case) behaves slightly differently when "dumping", such as NOT acquiring locks, etc. Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 21:26:21 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 991FC16A41B for ; Fri, 25 Jan 2008 21:26:21 +0000 (UTC) (envelope-from tim1timau@yahoo.com) Received: from web50303.mail.re2.yahoo.com (web50303.mail.re2.yahoo.com [206.190.38.57]) by mx1.freebsd.org (Postfix) with SMTP id 4FC8613C4CC for ; Fri, 25 Jan 2008 21:26:21 +0000 (UTC) (envelope-from tim1timau@yahoo.com) Received: (qmail 61541 invoked by uid 60001); 25 Jan 2008 21:26:20 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=guvyOPeBe2d1z0BwF6C+YYw1RsSvZZdT/GGPPGgHzyJo/22D7253KqVSwObE5lQIBZ+AHpdhgerr8BKfyjglINxg0yMWA/zJRAydTDxlgcNb1G7lLsrlQaiHfcbJQaC8CdHouidEyXxEgFxB60pHEDAG4MtRXr0YZp5EMhVjGBI=; X-YMail-OSG: wBHOBm0VM1n0hTccJiG9PQfUvmbgoyv72MA304RvhwvJsqBaOjg4.OY.ps8x4Yl3fiJ3920i2OSJEFlTv3CUtnywP.yoiSbNNbs9Bgt_Y8BRF.d5KIIFyG3v_e70K97YJcHk7dqiozi7CvY- Received: from [210.215.149.194] by web50303.mail.re2.yahoo.com via HTTP; Fri, 25 Jan 2008 13:26:20 PST Date: Fri, 25 Jan 2008 13:26:20 -0800 (PST) From: Tim Clewlow To: FreeBSD User , freebsd-current@freebsd.org In-Reply-To: <75988d070801250855h352c1d9chc7f54ebcd63a5bef@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <352187.61016.qm@web50303.mail.re2.yahoo.com> Cc: Subject: Re: installation problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2008 21:26:21 -0000 --- FreeBSD User wrote: > Hello, > > I'm not sure if this is the correct mailing list. > > I have tried installing FreeBSD 7.0-Current for amd64, and I am having > problems with my mouse and video card. > > Firstly my hardware is as follows: > > Gigabyte p35-ds3r motherboard > Intel Core 2 Quad 2.4GHz (Q6600) > NVidia 8400GS > Microsoft Comfort Optical 3000 mouse > Microsoft Natural Ergonomic Keyboard 4000 > > Problem 1: > The mouse is not working at all. When I look at the output of "dmesg", > I see the mouse (ums0), however no movement. > > Problem 2: > I cannot get X started. I get the following errors: > > Failed to load module "nv" (module does not exist, 0) > Failed to load module "mouse" (module does not exist, 0) > Failed to load module "kbd" (module does not exist, 0) > No drivers available > Hello, First you need to get the mouse working, I would go in to sysinstall, select Configure, then select Mouse. Now select "3 Type" and then try the first one. Then select "2 Enable" and see if it works. Keep doing that until you find one that works - I dont know what exactly a "Microsoft Comfort Optical 3000 mouse" will need. Trial and error will hopefully solve that. Next to the missing modules. Well, they mean pretty much what they say, bits of X are missing. Did you install the x11/xorg meta port, or did you install bits and pieces one by one? I would go and install the x11/xorg meta port to make sure everything is there. Next start X to make sure it doesnt give those errors (the nv one might still appear - will look at that next). Ok, I have never attempted to install/use the nvidia drivers, but I am guessing they are in x11-drivers/xf86-video-nv in the ports tree. You might want to google around a bit to confirm that, or find more information. I dont have any experience installing or using nv drivers. Lastly, this is all in 7.0 which I believe is technically still a testing version. There may be issues I dont know about with ums or usb in general or X or X/nv in 7.0 - hopefully someone else can confirm if there are. PS - this should probably be in freebsd-questions@ as it is not really a current specific problem. :-) Cheers, Tim. We are BSD ... resistance is futile. http://www.freebsd.org/ - http://www.openbsd.org/ - http://www.netbsd.org/ ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 21:59:34 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71D0216A41A for ; Fri, 25 Jan 2008 21:59:34 +0000 (UTC) (envelope-from chargen@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mx1.freebsd.org (Postfix) with ESMTP id E223513C465 for ; Fri, 25 Jan 2008 21:59:33 +0000 (UTC) (envelope-from chargen@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so863339fgg.35 for ; Fri, 25 Jan 2008 13:59:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=CcHxQq1v7dXwEysT1H9x2yF00IfBlQBHNxhK13s2nLo=; b=RqF2CUvLLVROfvvfV0MQHgH7wkM/6LMqUYCXMc53UyXJaY42hjvywsfO2DuoAnovGDXcS+iqw0XFSVnJpDIYMQ+dpRlPa+XDZTMWscX6PKDoc0L2kSzEajehJRx5Gc9sDCCOGa+wvfspt6xr2BlmPh8fwWSRyh5YDL3V/CESjj0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=GWG91lvIXLcXybTcVvI8i9kOOe+Ue3hM0ldbC7Bsex4+kVUmXHU0wqW20d6odEDa7j6c6Ps4sl9Ox+Q5E9kqG7yb3mIshkEUPvne5cOH3gScttipkqiVMGTLjMm8mJ8yzGkhoLPv9F1xcAaZ8t+AioiA09JV1nNAFliKAnoL0bI= Received: by 10.86.50.8 with SMTP id x8mr2272287fgx.30.1201296834976; Fri, 25 Jan 2008 13:33:54 -0800 (PST) Received: by 10.86.49.12 with HTTP; Fri, 25 Jan 2008 13:33:54 -0800 (PST) Message-ID: <292361ab0801251333v43896313qd6f8c9103870eda@mail.gmail.com> Date: Fri, 25 Jan 2008 22:33:54 +0100 From: Chargen To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: CUR: /usr/sbin/config and hardcoding eng_cryptodev.c to work with HIFN 795X and only aes-128-cbc supported X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 21:59:34 -0000 Dear all, I don't know which branch or maillist to subscribe to discuss these issues I found a some things, 1. concerning /usr/sbin/config {kernelname} packetstorm# pwd /usr/src/sys/i386/conf packetstorm# config santaclaus config: santaclaus: No such file or directory packetstorm# ls -alrt ../compile/ total 32 -rw-r--r-- 1 root wheel 13 Jul 2 2001 .cvsignore drwxr-xr-x 15 root wheel 512 Jan 21 23:33 .. drwxr-xr-x 2 root wheel 512 Jan 23 20:51 santaclaus I don't think the creation of this dir inode is intentional after config fails to find a kernelconfiguration :-) packetstorm# uname -a FreeBSD packetstorm 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #0: Thu Jan 24 03:37:11 CET 2008 root@packetstorm:/usr/src/sys/i386/compile/PACKETSTORM i386 2. Hardware support for cryptodev -> wired to HIFN - crypto/OPENSSL/ eng_cryptodev.c these are know issues , apparently the correct freebsd version isn't properly checked or recognised, some fixes have spreading been around but none are taken into 7) ( options crypto, options cryptodev, device hifn are included in my kernelconfig) I still have to hardcode eng_cryptodev.c in order to make openssl work with my device hifn (7955 - soekris VPN140x) packetstorm# diff /usr/src/crypto/openssl/crypto/engine/eng_cryptodev.c /root/eng_cryptodev.c 44a45,47 > #include > # define HAVE_CRYPTODEV > 1128a1132 > ENGINE_set_default_ciphers(engine); yes, dirty :-) (dmesg : hifn0 mem 0xfe12c000-0xfe12cfff,0xfe12a000-0xfe12bfff,0xfe120000-0xfe127fff irq 25 at device 4.0 on pci0 hifn0: [ITHREAD] hifn0: Hifn 7955, rev 0, 32KB dram, pll=0x801 ) the following concerns the lack of AES-192/256-CBC support over HIFN795X cryptocards A) AES-256-CBC fails to pass over HIFN packetstorm# time dd if=/dev/zero bs=1m count=2 | openssl aes-256-cbc -pass pass:test -out /dev/null 2+0 records in 2+0 records out 2097152 bytes transferred in 0.081557 secs (25713931 bytes/sec) packetstorm# hifnstats input 0 bytes 0 packets output 0 bytes 0 packets invalid 0 nomem 0 abort 0 noirq 0 unaligned 0 totbatch 0 maxbatch 0 nomem: map 0 load 0 mbuf 0 mcl 0 cr 0 sd 0 B) AES-128-CBC works (eng_cryptodev.c hardcoded to work ) packetstorm# time dd if=/dev/zero bs=1m count=2 | openssl aes-128-cbc -pass pass:test -out /dev/null 2+0 records in 2+0 records out 2097152 bytes transferred in 0.124829 secs (16800191 bytes/sec) packetstorm# hifnstats input 2097168 bytes 513 packets output 2097168 bytes 513 packets invalid 0 nomem 0 abort 0 noirq 0 unaligned 0 totbatch 0 maxbatch 0 nomem: map 0 load 0 mbuf 0 mcl 0 cr 0 sd 0 systat -vmstat really shows HIFN takes ints when processing aes-128-cbc packetstorm# sysctl -a | grep "cryp" kern.cryptodevallowsoft: 0 kern.userasymcrypto: 0 net.inet.ipsec.crypto_support: 50331648 debug.crypto_timing: 0 hw.via_feature_xcrypt: 0 dev.cryptosoft.0.%desc: software crypto dev.cryptosoft.0.%driver: cryptosoft dev.cryptosoft.0.%parent: nexus0 packetstorm# dmesg | grep "cryp" cryptosoft0: on motherboard Kind regards, and have a nice weekend all Chargen From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 22:03:11 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5962816A419 for ; Fri, 25 Jan 2008 22:03:11 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.176]) by mx1.freebsd.org (Postfix) with ESMTP id 2A41813C478 for ; Fri, 25 Jan 2008 22:03:10 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so1314559waf.3 for ; Fri, 25 Jan 2008 14:03:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=OJtdjVI0uObM0V1ETtg0xhjRx4qluS3ijwDuphbqvQk=; b=JlnS6fI16+BQgbYInK5rbkFo2NzGm4XnZ+3YaXYETYP/AASnNjkB46bVZXMsaYu62soIc2Jv2hYLspDJ4od8em7Yl/vJVUo/8ceFCEWU+ITdk6MndV2R9sijPi2exTDSR6zRFiwpsr/1S5V/SSB75VbdvkYYs1Y1ivOARZeoinA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=itvzTWRTO03sXbEF7z/ajCiPiIhxh6absJmY3tQae0KDddKYl6uG78TLsWoOAUUCxgksOjD0tf1e1qiX1WRGUYjGj1qKh3rfOZzPhX19BhWO3m5g7AR5qoIwYlp+NNf0bDwmVFH+BG+C1U/aosVqp/lI2N8WjzkES1Ge/3X7svg= Received: by 10.115.95.1 with SMTP id x1mr2856942wal.94.1201297045921; Fri, 25 Jan 2008 13:37:25 -0800 (PST) Received: by 10.114.255.16 with HTTP; Fri, 25 Jan 2008 13:37:25 -0800 (PST) Message-ID: Date: Fri, 25 Jan 2008 13:37:25 -0800 From: "Kip Macy" To: "Peter Jeremy" In-Reply-To: <20080125204735.GQ53741@server.vk2pj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080125180740.GA1646@team.vega.ru> <479A305E.3020801@samsco.org> <20080125204735.GQ53741@server.vk2pj.dyndns.org> Cc: current@freebsd.org Subject: Re: minidumps are unsafe on amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2008 22:03:11 -0000 On Jan 25, 2008 12:47 PM, Peter Jeremy wrote: > On Fri, Jan 25, 2008 at 11:54:22AM -0700, Scott Long wrote: > >Ruslan Ermilov wrote: > >> Kernel minidumps on amd64 SMP can write beyond the bounds > >> of the configured dump device causing (as in our case) the > >> file system data following swap partition to be overwritten > >> with the dump contents. > ... > >> This only affects 7.x/8.x amd64 SMP systems configured with > >> minidump. i386 systems aren't affected. > >> > > > >Is this a case where you are manually triggering a dump on a > >system that is otherwise running fine? > > IMO, this is irrelevant. Over-writing data outside the defined > partition boundaries is unacceptable on a production system. Uhm, not really. If the caller is violating the conditions expected / required by the dump routines then it is the caller (i.e. the code path for creating dumps artificially) that needs to be fixed. > > It would be nice if there were some sanity checks to pick this up. > Somewhere down the chain, one of the lower-level write functions > should verify that each write is contained within > [dumperinfo.mediaoffset .. dumperinfo.mediaoffset+dumperinfo.mediasize) > Ideally this would be inside dumperinfo.dumper() but that function > doesn't currently get passed dumperinfo so this change is too > intrusive for 7.0. Likewise dumperinfo.dumper() is called in too > many places to reasonably add the code to the callers. Maybe a > MI wrapper function replacing each of the existing dumperinfo.dumper() > calls would be the least intrusive fix: Replace each existing > di->dumper(di->priv, va, pa, offset, len); > with > dumper_write(di, va, pa, offset, len); > and add the following in (probably) kern/kern_shutdown: > void > dumper_write(struct dumperinfo *di, void *va, vm_offset_t *pa, off_t offset, size_t length) > { > if (offset >= di->mediaoffset && > offset + size <= di->mediaoffset + di->mediasize) > di->dumper(di->priv, va, pa, offset, len); > else > printf("Attempt to write outside dumpdev boundaries ignored\n"); > } > > >that's one thing. If it's a case where you're trying to fix > >something that isn't broken, then I'm very cautious about the > >added complexity that you're proposing. > > I'd suggest that, for 7.0-RELEASE, either amd64 minidumps, or manually > triggered amd64 minidumps, needs to be disabled (or hidden behind a > "do you really want to shoot yourself in the foot" check). This can > be noted in ERRATA and fixed in 7.1. > > -- > Peter Jeremy > Please excuse any delays as the result of my ISP's inability to implement > an MTA that is either RFC2821-compliant or matches their claimed behaviour. > From owner-freebsd-current@FreeBSD.ORG Fri Jan 25 22:14:15 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3971D16A418 for ; Fri, 25 Jan 2008 22:14:15 +0000 (UTC) (envelope-from w0lfie@clear.net.nz) Received: from smtp5.clear.net.nz (smtp5.clear.net.nz [203.97.33.68]) by mx1.freebsd.org (Postfix) with ESMTP id 0492D13C43E for ; Fri, 25 Jan 2008 22:14:14 +0000 (UTC) (envelope-from w0lfie@clear.net.nz) Received: from clear.net.nz (lb2-srcnat.clear.net.nz [203.97.32.237]) by smtp5.clear.net.nz (CLEAR Net Mail) with SMTP id <0JV700F0LZQND710@smtp5.clear.net.nz> for freebsd-current@freebsd.org; Sat, 26 Jan 2008 10:59:12 +1300 (NZDT) Date: Sat, 26 Jan 2008 10:59:11 +1300 From: Sam Banks Sender: w0lfie@clear.net.nz To: freebsd-current@freebsd.org Message-id: <479a5baf.c8.565e.23810@clear.net.nz> MIME-version: 1.0 X-Mailer: CLEAR Net WebMail; webmail.clear.net.nz; user: w0lfie; ip: 121.73.22.121 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable Priority: normal Cc: Benjamin.Close@clearchain.com Subject: if_wpi panic in 7.0-PRERELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: w0lfie@clear.net.nz 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 Jan 2008 22:14:15 -0000 Hey all, I have just got myself a new laptop (Dell Vostro 1500) which has an Intel 3945ABG wifi card in it. I am getting frequent kernel panics with the if_wpi driver. >From the attached kgdb output, it appears that a valid mbuf struct is being passed into tkip_demic but once m_copydata is called (within tkip_demic), it's being passed a null pointer. At least, this is what I can see is going on :) Does anyone have any ideas why this would be happening or any further insight? I've attached what info I think will be helpful but if there's anything else needed, just yell out. Cheers, Sam. FreeBSD wolfie.evil 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE #3: Fri Jan 25 17:35:41 NZDT 2008 root@wolfie.evil:/usr/src/sys/i386/compile/WOLFIE i386 wpi0@pci0:12:0:0: class=3d0x028000 card=3d0x10208086 chip=3d0x42228086 rev=3d0x02 hdr=3d0x00 vendor =3d 'Intel Corporation' device =3d '10418086 Intel 3945ABG Wireless LAN controller' class =3d network Fatal trap 12: page fault while in kernel mode cpuid =3d 0; apic id =3d 00 fault virtual address =3d 0xc fault code =3d supervisor read, page not present instruction pointer =3d 0x20:0xc0597e0f stack pointer =3d 0x28:0xe59c0b00 frame pointer =3d 0x28:0xe59c0b18 code segment =3d base 0x0, limit 0xfffff, type 0x1b =3d DPL 0, pres 1, def32 1, gran 1 processor eflags =3d interrupt enabled, resume, IOPL =3d 0 current process =3d 34 (irq17: wpi0 bfe0+) panic: from debugger cpuid =3d 0 Uptime: 16s Physical memory: 2034 MB Dumping 72 MB: 57 41 25 9 #0 doadump () at pcpu.h:195 195 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:195 #1 0xc054d14a in boot (howto=3d260) at ./../../kern/kern_shutdown.c:409 #2 0xc054d44f in panic (fmt=3dVariable "fmt" is not available. ) at ../../../kern/kern_shutdown.c:563 #3 0xc044ad49 in db_panic (addr=3dCould not find the frame base for "db_panic". ) at ../../../ddb/db_command.c:433 #4 0xc044b44c in db_command_loop () at ./../../ddb/db_command.c:401 #5 0xc044cd28 in db_trap (type=3d12, code=3d0) at ./../../ddb/db_main.c:222 #6 0xc0573c18 in kdb_trap (type=3d12, code=3d0, tf=3ddwarf2_read_address: Corrupted DWARF expression. ) at ../../../kern/subr_kdb.c:502 #7 0xc06cd159 in trap_fatal (frame=3d0xe59c0ac0, eva=3d12) at ../../../i386/i386/trap.c:890 #8 0xc06cd40e in trap_pfault (frame=3d0xe59c0ac0, usermode=3d0, eva=3d12) at ../../../i386/i386/trap.c:812 #9 0xc06cdddb in trap (frame=3d0xe59c0ac0) at ./../../i386/i386/trap.c:490 #10 0xc06b502b in calltrap () at ./../../i386/i386/exception.s:139 #11 0xc0597e0f in m_copydata (m=3d0x0, off=3d4, len=3d8, cp=3d0xe59c0b38 "=a4=f0i=c5") at ./../../kern/uipc_mbuf.c:808 #12 0xc05ee9d2 in tkip_demic (k=3d0xc569f0a4, m=3d0xc5293000, force=3d0) at ../../../net80211/ieee80211_crypto_tkip.c:338 #13 0xc05f7a7e in ieee80211_input (ic=3d0xc527c008, m=3d0xc5293000, ni=3d0xc569f000, rssi=3d54, noise=3d0, rstamp=3d0) at ieee80211_crypto.h:186 #14 0xc06a9687 in wpi_intr (arg=3d0xc527c000) at ./../../dev/wpi/if_wpi.c:1699 #15 0xc0530e6c in ithread_loop (arg=3d0xc525ab90) at ./../../kern/kern_intr.c:1036 #16 0xc052d931 in fork_exit (callout=3d0xc0530cd0 , arg=3d0xc525ab90, frame=3d0xe59c0d38) at ../../../kern/kern_fork.c:781 #17 0xc06b50a0 in fork_trampoline () at ./../../i386/i386/exception.s:205 Contents of mbuf struct being passed into tkip_demic: $1 =3d {m_hdr =3d {mh_next =3d 0x0, mh_nextpkt =3d 0x0, mh_data =3d 0xe5753820 "\b\002~", mh_len =3d 68, mh_flags =3d 1, mh_type =3d 1, pad =3d "\000"}, M_dat =3d {MH =3d {MH_pkthdr =3d {rcvif =3d 0xc527a000, header =3d 0x0, len =3d 80, csum_flags =3d 0, csum_data =3d 0, tso_segsz =3d 0, ether_vtag =3d 0, tags =3d {slh_first =3d 0x0}}, MH_dat =3d { MH_ext =3d {ext_buf =3d 0xe5753800 "t", ext_free =3d 0xc06a5c7d , ext_args =3d 0xc527d990, ext_size =3d 3072, ref_cnt =3d 0xc52965a0, ext_type =3d 100}, MH_databuf =3d "\0008u=e5}\\j=c0\220=d9'=c5\000\f\000\000 e)=c5d", '\0' }}, M_databuf =3d "\000 '=c5\000\000\000\000P", '\0' , "8u=e5}\\j=c0\220=d9'=c5\000\f\000\000 e)=c5d", '\0' }} From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 00:06:23 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9788D16A419 for ; Sat, 26 Jan 2008 00:06:23 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 192C613C447 for ; Sat, 26 Jan 2008 00:06:22 +0000 (UTC) (envelope-from sam@errno.com) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id m0PNkPRd039346 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Jan 2008 15:46:25 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <479A74D1.6060907@errno.com> Date: Fri, 25 Jan 2008 15:46:25 -0800 From: Sam Leffler User-Agent: Thunderbird 2.0.0.9 (X11/20071125) MIME-Version: 1.0 To: w0lfie@clear.net.nz References: <479a5baf.c8.565e.23810@clear.net.nz> In-Reply-To: <479a5baf.c8.565e.23810@clear.net.nz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: freebsd-current@freebsd.org, Benjamin.Close@clearchain.com Subject: Re: if_wpi panic in 7.0-PRERELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 00:06:23 -0000 Sam Banks wrote: > Hey all, > > I have just got myself a new laptop (Dell Vostro 1500) which > has an Intel 3945ABG wifi card in it. I am getting frequent > kernel panics with the if_wpi driver. > > >From the attached kgdb output, it appears that a valid mbuf > struct is being passed into tkip_demic but once m_copydata > is called (within tkip_demic), it's being passed a null > pointer. At least, this is what I can see is going on :) > > Does anyone have any ideas why this would be happening or > any further insight? > > I've attached what info I think will be helpful but if > there's anything else needed, just yell out. > > Cheers, > > Sam. > > > FreeBSD wolfie.evil 7.0-PRERELEASE FreeBSD 7.0-PRERELEASE > #3: Fri Jan 25 17:35:41 NZDT 2008 > root@wolfie.evil:/usr/src/sys/i386/compile/WOLFIE i386 > > > wpi0@pci0:12:0:0: class=0x028000 card=0x10208086 > chip=0x42228086 rev=0x02 hdr=0x00 > vendor = 'Intel Corporation' > device = '10418086 Intel 3945ABG Wireless LAN > controller' > class = network > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0xc > fault code = supervisor read, page not > present > instruction pointer = 0x20:0xc0597e0f > stack pointer = 0x28:0xe59c0b00 > frame pointer = 0x28:0xe59c0b18 > 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 = 34 (irq17: wpi0 bfe0+) > panic: from debugger > cpuid = 0 > Uptime: 16s > Physical memory: 2034 MB > Dumping 72 MB: 57 41 25 9 > > #0 doadump () at pcpu.h:195 > 195 pcpu.h: No such file or directory. > in pcpu.h > (kgdb) bt > #0 doadump () at pcpu.h:195 > #1 0xc054d14a in boot (howto=260) at > ./../../kern/kern_shutdown.c:409 > #2 0xc054d44f in panic (fmt=Variable "fmt" is not > available. > ) at ../../../kern/kern_shutdown.c:563 > #3 0xc044ad49 in db_panic (addr=Could not find the frame > base for "db_panic". > ) at ../../../ddb/db_command.c:433 > #4 0xc044b44c in db_command_loop () at > ./../../ddb/db_command.c:401 > #5 0xc044cd28 in db_trap (type=12, code=0) at > ./../../ddb/db_main.c:222 > #6 0xc0573c18 in kdb_trap (type=12, code=0, > tf=dwarf2_read_address: Corrupted DWARF expression. > ) at ../../../kern/subr_kdb.c:502 > #7 0xc06cd159 in trap_fatal (frame=0xe59c0ac0, eva=12) > at ../../../i386/i386/trap.c:890 > #8 0xc06cd40e in trap_pfault (frame=0xe59c0ac0, > usermode=0, eva=12) at ../../../i386/i386/trap.c:812 > #9 0xc06cdddb in trap (frame=0xe59c0ac0) at > ./../../i386/i386/trap.c:490 > #10 0xc06b502b in calltrap () at > ./../../i386/i386/exception.s:139 > #11 0xc0597e0f in m_copydata (m=0x0, off=4, len=8, > cp=0xe59c0b38 "¤ðiÅ") at > ./../../kern/uipc_mbuf.c:808 > #12 0xc05ee9d2 in tkip_demic (k=0xc569f0a4, > m=0xc5293000, force=0) > at ../../../net80211/ieee80211_crypto_tkip.c:338 > #13 0xc05f7a7e in ieee80211_input (ic=0xc527c008, > m=0xc5293000, ni=0xc569f000, rssi=54, noise=0, > rstamp=0) > at ieee80211_crypto.h:186 > #14 0xc06a9687 in wpi_intr (arg=0xc527c000) at > ./../../dev/wpi/if_wpi.c:1699 > #15 0xc0530e6c in ithread_loop (arg=0xc525ab90) at > ./../../kern/kern_intr.c:1036 > #16 0xc052d931 in fork_exit (callout=0xc0530cd0 > , arg=0xc525ab90, frame=0xe59c0d38) > at ../../../kern/kern_fork.c:781 > #17 0xc06b50a0 in fork_trampoline () at > ./../../i386/i386/exception.s:205 > > > Contents of mbuf struct being passed into tkip_demic: > > $1 = {m_hdr = {mh_next = 0x0, mh_nextpkt = 0x0, > mh_data = 0xe5753820 "\b\002~", mh_len = 68, mh_flags > = 1, > mh_type = 1, pad = "\000"}, M_dat = {MH = > {MH_pkthdr = {rcvif = 0xc527a000, header = 0x0, len > = 80, > csum_flags = 0, csum_data = 0, tso_segsz = 0, > ether_vtag = 0, tags = {slh_first = 0x0}}, MH_dat = > { > MH_ext = {ext_buf = 0xe5753800 "t", ext_free = > 0xc06a5c7d , ext_args = 0xc527d990, > ext_size = 3072, ref_cnt = 0xc52965a0, > ext_type = 100}, > MH_databuf = > "\0008uå}\\jÀ\220Ù'Å\000\f\000\000 e)Åd", '\0' > }}, > M_databuf = "\000 'Å\000\000\000\000P", '\0' > , "8uå}\\jÀ\220Ù'Å\000\f\000\000 > e)Åd", '\0' }} > I think there is some confusion in the setup of mbufs for the rx ring. Frames passed up the stack must have a pkthdr on the first mbuf but it looks like wpi_alloc_rx_ring allocates regular mbufs w/ m_get and not m_gethdr. This would explain why mh_flags above is 1 (M_EXT) and not 3 (M_EXT+M_PKTHDR). Sam From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 00:40:26 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 82D2716A469 for ; Sat, 26 Jan 2008 00:40:26 +0000 (UTC) (envelope-from w0lfie@clear.net.nz) Received: from smtp4.clear.net.nz (smtp4.clear.net.nz [203.97.37.64]) by mx1.freebsd.org (Postfix) with ESMTP id 473F513C4D3 for ; Sat, 26 Jan 2008 00:40:26 +0000 (UTC) (envelope-from w0lfie@clear.net.nz) Received: from clear.net.nz (lb2-srcnat.clear.net.nz [203.97.32.237]) by smtp4.clear.net.nz (CLEAR Net Mail) with SMTP id <0JV80063R77B4G30@smtp4.clear.net.nz> for freebsd-current@freebsd.org; Sat, 26 Jan 2008 13:40:25 +1300 (NZDT) Date: Sat, 26 Jan 2008 13:40:23 +1300 From: Sam Banks Sender: w0lfie@clear.net.nz To: Sam Leffler Message-id: <479a8177.32d.4948.26949@clear.net.nz> MIME-version: 1.0 X-Mailer: CLEAR Net WebMail; webmail.clear.net.nz; user: w0lfie; ip: 121.73.22.121 Content-type: multipart/mixed; boundary="-=_fep17479a8177" Priority: normal Cc: freebsd-current@freebsd.org, Benjamin.Close@clearchain.com Subject: Re: if_wpi panic in 7.0-PRERELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: w0lfie@clear.net.nz 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 Jan 2008 00:40:26 -0000 This is a multi-part message in MIME format. ---=_fep17479a8177 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thanks for that Sam :) The attached patch (against 1.5.2.1) seems to have fixed my problems. Does it look ok to everyone? If so, I would like, if possible, to get it included so other people hopefully don't run into the same problem. Cheers, Sam. ----- Original Message Follows ----- > Sam Banks wrote: > > Hey all, > > > > I have just got myself a new laptop (Dell Vostro 1500) > > which has an Intel 3945ABG wifi card in it. I am getting > > frequent kernel panics with the if_wpi driver. > > > > >From the attached kgdb output, it appears that a valid > > mbuf struct is being passed into tkip_demic but once > > m_copydata is called (within tkip_demic), it's being > > passed a null pointer. At least, this is what I can see > is going on :) > > > Does anyone have any ideas why this would be happening > > or any further insight? > > > > I've attached what info I think will be helpful but if > > there's anything else needed, just yell out. > > > > Cheers, > > > > Sam. > > > > > > FreeBSD wolfie.evil 7.0-PRERELEASE FreeBSD > > 7.0-PRERELEASE #3: Fri Jan 25 17:35:41 NZDT 2008 > > root@wolfie.evil:/usr/src/sys/i386/compile/WOLFIE i386 > > > > > > wpi0@pci0:12:0:0: class=3d0x028000 card=3d0x10208086 > > chip=3d0x42228086 rev=3d0x02 hdr=3d0x00 > > vendor =3d 'Intel Corporation' > > device =3d '10418086 Intel 3945ABG Wireless LAN > > controller' > > class =3d network > > > > > > Fatal trap 12: page fault while in kernel mode > > cpuid =3d 0; apic id =3d 00 > > fault virtual address =3d 0xc > > fault code =3d supervisor read, page not > > present > > instruction pointer =3d 0x20:0xc0597e0f > > stack pointer =3d 0x28:0xe59c0b00 > > frame pointer =3d 0x28:0xe59c0b18 > > code segment =3d base 0x0, limit 0xfffff, type > > 0x1b > > =3d DPL 0, pres 1, def32 1, gran 1 > > processor eflags =3d interrupt enabled, resume, > > IOPL =3d 0 > > current process =3d 34 (irq17: wpi0 bfe0+) > > panic: from debugger > > cpuid =3d 0 > > Uptime: 16s > > Physical memory: 2034 MB > > Dumping 72 MB: 57 41 25 9 > > > > #0 doadump () at pcpu.h:195 > > 195 pcpu.h: No such file or directory. > > in pcpu.h > > (kgdb) bt > > #0 doadump () at pcpu.h:195 > > #1 0xc054d14a in boot (howto=3d260) at > > ./../../kern/kern_shutdown.c:409 > > #2 0xc054d44f in panic (fmt=3dVariable "fmt" is not > > available. > > ) at ../../../kern/kern_shutdown.c:563 > > #3 0xc044ad49 in db_panic (addr=3dCould not find the > > frame base for "db_panic". > > ) at ../../../ddb/db_command.c:433 > > #4 0xc044b44c in db_command_loop () at > > ./../../ddb/db_command.c:401 > > #5 0xc044cd28 in db_trap (type=3d12, code=3d0) at > > ./../../ddb/db_main.c:222 > > #6 0xc0573c18 in kdb_trap (type=3d12, code=3d0, > > tf=3ddwarf2_read_address: Corrupted DWARF expression. > > ) at ../../../kern/subr_kdb.c:502 > > #7 0xc06cd159 in trap_fatal (frame=3d0xe59c0ac0, eva=3d12) > > at ../../../i386/i386/trap.c:890 > > #8 0xc06cd40e in trap_pfault (frame=3d0xe59c0ac0, > > usermode=3d0, eva=3d12) at ../../../i386/i386/trap.c:812 > > #9 0xc06cdddb in trap (frame=3d0xe59c0ac0) at > > ./../../i386/i386/trap.c:490 > > #10 0xc06b502b in calltrap () at > > ./../../i386/i386/exception.s:139 > > #11 0xc0597e0f in m_copydata (m=3d0x0, off=3d4, len=3d8, > > cp=3d0xe59c0b38 "=a4=f0i=c5 ---=_fep17479a8177 Content-Type: application/octet-stream; name="if_wpi.c.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="if_wpi.c.patch" LS0tIGlmX3dwaS5jLm9yaWcJMjAwOC0wMS0yNiAxMzozMTo1MS4wMDAwMDAw MDAgKzEzMDAKKysrIGlmX3dwaS5jCTIwMDgtMDEtMjYgMTM6MzI6MDQuMDAw MDAwMDAwICsxMzAwCkBAIC0xMDQxLDcgKzEwNDEsNyBAQAogCWZvciAoaSA9 IDA7IGkgPCBXUElfUlhfUklOR19DT1VOVDsgaSsrKSB7CiAJCWRhdGEgPSAm cmluZy0+ZGF0YVtpXTsKIAotCQlkYXRhLT5tID0gbV9nZXQoTV9ET05UV0FJ VCwgTVRfSEVBREVSKTsKKwkJZGF0YS0+bSA9IG1fZ2V0aGRyKE1fRE9OVFdB SVQsIE1UX0hFQURFUik7CiAJCWlmIChkYXRhLT5tID09IE5VTEwpIHsKIAkJ CWRldmljZV9wcmludGYoc2MtPnNjX2RldiwKIAkJCSAgICAiY291bGQgbm90 IGFsbG9jYXRlIHJ4IG1idWZcbiIpOwo= ---=_fep17479a8177-- From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 04:15:26 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9290E16A419 for ; Sat, 26 Jan 2008 04:15:26 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by mx1.freebsd.org (Postfix) with ESMTP id 0B5B713C4D5 for ; Sat, 26 Jan 2008 04:15:25 +0000 (UTC) (envelope-from swhetzel@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so969117fgg.35 for ; Fri, 25 Jan 2008 20:15:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=MtwPRj6zdaI3VNoQcd20/zLhwz4mP7VWTlxRy90a9jo=; b=mftqgJMJgbE7GXlQiCkAhLtLsYhkcberbG4GBKhmVQV+DJ+F9j+bdns4/WzWV6Bi3KGdc3eg4nV7FYoJaAaeUBqfiPYz8SSORZ7NZIpXNOQ5C1XrxOvmkOWhsQM9cMzcTw1CBvKcDhe131At+nTtJCcFn9bJjtuW3BPWRkSfj7U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=xCz9jQ/TO2kceIqmghDaRJLHvgoE9GPTY/gjU4nmZVxTxeWJQvymPTSR95yeCYVAqBKFPj7/0iWyb0aLpNyAZ8AHfT4xzo3P5AaOyiGC8gJwYh8nJCEUY6CzUOPQEF3jsdF7NlwSsBH2nNLDlpyPSX/dLftszdxw5mOulhPK7qI= Received: by 10.86.100.7 with SMTP id x7mr2590070fgb.10.1201320924773; Fri, 25 Jan 2008 20:15:24 -0800 (PST) Received: by 10.86.99.17 with HTTP; Fri, 25 Jan 2008 20:15:24 -0800 (PST) Message-ID: <790a9fff0801252015l34f524d1k704fa0accffe2545@mail.gmail.com> Date: Fri, 25 Jan 2008 22:15:24 -0600 From: "Scot Hetzel" To: "Attilio Rao" In-Reply-To: <3bbf2fe10801240518i6e18b2f5w84de652d4170c95b@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <790a9fff0801150552l542a4238ofc12efe5fdb45fc2@mail.gmail.com> <20080115143924.GB57756@deviant.kiev.zoral.com.ua> <20080124122808.GA15600@freefall.freebsd.org> <3bbf2fe10801240518i6e18b2f5w84de652d4170c95b@mail.gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: panic: System call lstat returning with 1 locks held X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 04:15:26 -0000 On 1/24/08, Attilio Rao wrote: > 2008/1/24, Yar Tikhiy : > > On Tue, Jan 15, 2008 at 04:39:24PM +0200, Kostik Belousov wrote: > > > > > > I think this could be related to the recent vn_lock()/VOP_LOCK() KPI changes. > > > Please, add DEBUG_VFS_LOCKS to the kernel config, and do the > > > show lockedvnods > > > from the ddb prompt when the panic occurs. The witness does not track > > > the lockmgr locks. > > > > I think I'm seeing the same panic on UFS. It's rather nasty: I > > cannot rebuild CURRENT natively due to it so I have to build it > > under 6-STABLE. My favourite way to trigger the panic reliably is > > running `make install' in a simple port directory, e.g., portmaster, > > but my system also panics during daily scripts run and, as already > > said, if trying to build world. > > Yar, > as it seems reproducible for you, can you please add this patch to the tree: > http://www.freebsd.org/~attilio/debug_tdlocks.diff > > compile your kernel with: > options KTR > options KTR_COMPILE=(KTR_SPARE2) > options KTR_MASK=(KTR_SPARE2) > options KTR_ENTRIES=32768 > > and once kernel panics, at ddb prompts do: > > show ktr > I added the above options to my kernel, and performed a scripted textdump. /sbin/ddb script lockinfo="show locks; show alllocks; show lockedvnods" /sbin/ddb script kdb.enter.panic="textdump set; capture on; show ktr ; run lockinfo ; show pcpu; bt; ps; alltrace; capture off; call doadump; reset" After the kernel paniced, the kdb.enter.panic script ran and created a textdump. When I extracted the 2.7M ddb.txt file, it didn't show any calls to lockmgr_disown in the ktr trace. Let me know if there is anything else that I can do. To get this dump, DB_CAPTURE_MAXBUFSIZE (sys/ddb/db_capture.c) needed to be increased from its default of 512K to 5M, and then setting the debug.ddb.capure.bufsize to 5M after rebooting with the new kernel. See PR 119993 (http://www.freebsd.org/cgi/query-pr.cgi?pr=119993) which adds two new kernel options to allow the capture buffer size to be changed at compile time. Scot From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 04:36:43 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89E4F16A419 for ; Sat, 26 Jan 2008 04:36:43 +0000 (UTC) (envelope-from chargen@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by mx1.freebsd.org (Postfix) with ESMTP id 17A1F13C448 for ; Sat, 26 Jan 2008 04:36:42 +0000 (UTC) (envelope-from chargen@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so974678fgg.35 for ; Fri, 25 Jan 2008 20:36:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; bh=tE+SZ3ZtfXEME8jacvaj/gtVDJ3hIa3orL7P6OzyHf4=; b=LijfDT4jkn4ArSN6rAYeStYDEsPiMxx2E2fwy8Joy/WH9FEi0CkUksdy9WvuZ+7Id1gBdAsuLUI7mOKhDJsbIKqqz4nJeCsLUVhsPoAnHkzsCpxBjxyTAuCmgHbm+lVDLtNnKjitVrV95/Pffm/ntFHmbpExblpiJ2PNQ2br1mY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=VPkkcJpwBsdJIJ5+o5VwVvmR4evalKaCp3iW8e03nClqBWaZFU1XDl8/EQeuHlnZ1OliyzTT9UQeVoVnzp7aQthB+NNPgfawSze3y6peUZ5jk45unfNX48WRuAzWJOq7EMFuoV7IX8AMJkLKluOHPS91N4vnLeZh9kA+MSFt5uA= Received: by 10.86.100.7 with SMTP id x7mr2612475fgb.7.1201322201830; Fri, 25 Jan 2008 20:36:41 -0800 (PST) Received: by 10.86.49.12 with HTTP; Fri, 25 Jan 2008 20:36:41 -0800 (PST) Message-ID: <292361ab0801252036g75df6800x3b799aedaed02bde@mail.gmail.com> Date: Sat, 26 Jan 2008 05:36:41 +0100 From: Chargen To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: 7cur: SMP kernels /w POLLING enabled - combination garbles (syncer?) console line message(s) on 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: Sat, 26 Jan 2008 04:36:43 -0000 7cur: SMP kernels /w POLLING enabled - combination garbles (syncer?) console line message(s) on reboot SMP kernel with POLLING enabled garbles one or more of the last lines in console after issuing the {reboot} command options DEVICE_POLLING options HZ=1000 with or without sysctl -w kern.polling.enable=1 or sysctl -w kern.polling.enable=0 The garbled lines are between 'shutting down bufdaemon' and 'all buffs synced' (after 'bufdaemon', I presume these are the syncer, 'Syncing disks, vnodes synced' lines) I found it only reproducable with SMP /apic enabled kernel. Console messages after issuing reboot on UP kernels with polling_enabled are readable. Note: polling wasn't manually set on any device (tested on UP and SMP kernels) e.g.: no ifconfig em0 polling From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 05:20:04 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 791A916A419 for ; Sat, 26 Jan 2008 05:20:04 +0000 (UTC) (envelope-from prvs=1911771df7=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id BB0B013C442 for ; Sat, 26 Jan 2008 05:20:03 +0000 (UTC) (envelope-from prvs=1911771df7=killing@multiplay.co.uk) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk; s=Multiplay; t=1201323909; x=1201928709; q=dns/txt; h=Received: Message-ID:From:To:References:Subject:Date:MIME-Version: Content-Type:Content-Transfer-Encoding; bh=mIFumlgnsKzMuCKWbKQB4 A/AsT7NmYZiIxZv6/5pPvQ=; b=dq4okFmVIUVHZAWYta4VtKP9yRbsa1LT6Eja5 D50bCXm5jVYHUHYAI2qKNZl3/xav65ID7OxhuF66iMIxisADT43YVGqLETBHP0oN FMk10h5NT/xtGyzJIx6yqAyMklnRvOEecGGqJXB0jWMBl9YHUX5VqSeC9Moxq98e RYRNMU= X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-14.7 required=6.0 tests=BAYES_00, USER_IN_WHITELIST, USER_IN_WHITELIST_TO autolearn=ham version=3.1.8 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v9.6.3) with ESMTP id md50004937447.msg for ; Sat, 26 Jan 2008 05:05:08 +0000 Message-ID: <003001c85fd9$03ea2e40$b6db87d4@multiplay.co.uk> From: "Steven Hartland" To: "Chargen" , References: <292361ab0801252036g75df6800x3b799aedaed02bde@mail.gmail.com> Date: Sat, 26 Jan 2008 05:05:05 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 212.135.219.182 X-Return-Path: prvs=1911771df7=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-current@freebsd.org X-Spam-Processed: mail1.multiplay.co.uk, Sat, 26 Jan 2008 05:05:08 +0000 X-MDAV-Processed: mail1.multiplay.co.uk, Sat, 26 Jan 2008 05:05:09 +0000 Cc: Subject: Re: SMP kernels /w POLLING enabled - combination garbles(syncer?) console line message(s) on 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: Sat, 26 Jan 2008 05:20:04 -0000 ----- Original Message ----- From: "Chargen" To: Sent: Saturday, January 26, 2008 4:36 AM Subject: 7cur: SMP kernels /w POLLING enabled - combination garbles(syncer?) console line message(s) on reboot > 7cur: SMP kernels /w POLLING enabled - combination garbles (syncer?) console > line message(s) on reboot > > SMP kernel with POLLING enabled garbles one or more of the last lines in > console after issuing the {reboot} command > > options DEVICE_POLLING > options HZ=1000 > > with or without sysctl -w kern.polling.enable=1 or sysctl -w > kern.polling.enable=0 > > The garbled lines are between 'shutting down bufdaemon' and 'all buffs > synced' (after 'bufdaemon', I presume these are the syncer, 'Syncing > disks, vnodes synced' lines) > > I found it only reproducable with SMP /apic enabled kernel. Console messages > after issuing reboot on UP kernels with polling_enabled are readable. > > Note: polling wasn't manually set on any device (tested on UP and SMP > kernels) e.g.: no ifconfig em0 polling Funny you should say that. Noticed that last night when rebooting one of our new 7.0 machines but assumed it was a one off remote console corruption. Just tested this again and its not. So I can confirm the corruption here on 7.0-PRERELEASE amd64 without polling. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 05:26:14 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5694D16A41A for ; Sat, 26 Jan 2008 05:26:14 +0000 (UTC) (envelope-from astrodog@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.184]) by mx1.freebsd.org (Postfix) with ESMTP id 265DD13C44B for ; Sat, 26 Jan 2008 05:26:14 +0000 (UTC) (envelope-from astrodog@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so872505rvb.43 for ; Fri, 25 Jan 2008 21:26:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=G/mLreamQ/acAGZ63kimPgbcE0Lzd1zrsSgWF1oIQm4=; b=RLg4KlHKbwv/k3UUVyAD5yGPWfR02+lEFLe/zeDyoIKui2u9G+FY4UMgBQ0TNPrizaEjrmcQWTHDzwnkzM3ijiRbzyWTc35XC+Bbxbs91dPXNiLyFnD4Fg+BBqX9Vm1q4BiNAKAWN4LFYa4f0xxh8Y0mJxAmol04O6Ck/Otw+4A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=m5QnewgKM1MhUO+0FpA/KcxsdobtWycycW/yPnFPbjqyngONtCNmOKpY9SPLclOwLno3m6eV6QeWilzDJjp2GygJ7c5UbdaWJ2j9MBkE3/QVPpxPp5Mhjqam818dMWATUy3Qu4kiSOa8i0FtSVVn+TVyOb4WIRFj8XzHqyI7hXE= Received: by 10.141.74.17 with SMTP id b17mr1973518rvl.144.1201325173746; Fri, 25 Jan 2008 21:26:13 -0800 (PST) Received: by 10.141.68.21 with HTTP; Fri, 25 Jan 2008 21:26:13 -0800 (PST) Message-ID: <2fd864e0801252126p3476da80r966f94162c62bec0@mail.gmail.com> Date: Sat, 26 Jan 2008 13:26:13 +0800 From: Astrodog To: Chargen In-Reply-To: <292361ab0801252036g75df6800x3b799aedaed02bde@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <292361ab0801252036g75df6800x3b799aedaed02bde@mail.gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: 7cur: SMP kernels /w POLLING enabled - combination garbles (syncer?) console line message(s) on 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: Sat, 26 Jan 2008 05:26:14 -0000 On Jan 26, 2008 12:36 PM, Chargen wrote: > 7cur: SMP kernels /w POLLING enabled - combination garbles (syncer?) console > line message(s) on reboot Look for the message buffer sysctl or kernel options on the list to fix this. It might be worth submitting as a doc PR, if its not in the documentation somewhere. From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 08:54:40 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B121E16A418; Sat, 26 Jan 2008 08:54:40 +0000 (UTC) (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 6BB2913C457; Sat, 26 Jan 2008 08:54:40 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.14.2/8.14.2) with ESMTP id m0Q8sdhk051070; Sat, 26 Jan 2008 03:54:39 -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.14.2/8.14.1) with ESMTP id m0Q8sdkq094248; Sat, 26 Jan 2008 03:54:39 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 3699F73039; Sat, 26 Jan 2008 03:54:39 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080126085439.3699F73039@freebsd-current.sentex.ca> Date: Sat, 26 Jan 2008 03:54:39 -0500 (EST) X-Virus-Scanned: ClamAV 0.92/5493/Thu Jan 17 13:09:26 2008 clamav-milter version 0.91.2 on clamscanner2 X-Virus-Status: Clean 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: Sat, 26 Jan 2008 08:54:40 -0000 TB --- 2008-01-26 07:56:12 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-01-26 07:56:12 - starting HEAD tinderbox run for i386/pc98 TB --- 2008-01-26 07:56:12 - cleaning the object tree TB --- 2008-01-26 07:56:33 - cvsupping the source tree TB --- 2008-01-26 07:56:33 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/i386/pc98/supfile TB --- 2008-01-26 07:56:40 - building world (CFLAGS=-O -pipe) TB --- 2008-01-26 07:56:40 - cd /src TB --- 2008-01-26 07:56:40 - /usr/bin/make -B buildworld >>> World build started on Sat Jan 26 07:56:41 UTC 2008 >>> 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 [...] /src/usr.bin/fstat/zfs/zfs.c:111: warning: implicit declaration of function 'getvnodemount' /src/usr.bin/fstat/zfs/zfs.c:111: warning: nested extern declaration of 'getvnodemount' /src/usr.bin/fstat/zfs/zfs.c:111: warning: assignment makes pointer from integer without a cast /src/usr.bin/fstat/zfs/zfs.c:118: error: dereferencing pointer to incomplete type /src/usr.bin/fstat/zfs/zfs.c:119: error: dereferencing pointer to incomplete type /src/usr.bin/fstat/zfs/zfs.c:125: error: dereferencing pointer to incomplete type /src/usr.bin/fstat/zfs/zfs.c:126: error: dereferencing pointer to incomplete type /src/usr.bin/fstat/zfs/zfs.c:127: error: dereferencing pointer to incomplete type *** Error code 1 Stop in /src/usr.bin/fstat. *** Error code 1 Stop in /src/usr.bin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-01-26 08:54:39 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-01-26 08:54:39 - ERROR: failed to build world TB --- 2008-01-26 08:54:39 - tinderbox aborted TB --- 2492.33 user 311.62 system 3506.21 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-pc98.full From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 10:15:15 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5506916A420 for ; Sat, 26 Jan 2008 10:15:15 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 11EF713C469; Sat, 26 Jan 2008 10:15:12 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <479B082D.4020309@FreeBSD.org> Date: Sat, 26 Jan 2008 11:15:09 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Steven Hartland References: <292361ab0801252036g75df6800x3b799aedaed02bde@mail.gmail.com> <003001c85fd9$03ea2e40$b6db87d4@multiplay.co.uk> In-Reply-To: <003001c85fd9$03ea2e40$b6db87d4@multiplay.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Chargen , freebsd-current@freebsd.org Subject: Re: SMP kernels /w POLLING enabled - combination garbles(syncer?) console line message(s) on 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: Sat, 26 Jan 2008 10:15:15 -0000 Steven Hartland wrote: > ----- Original Message ----- From: "Chargen" > To: > Sent: Saturday, January 26, 2008 4:36 AM > Subject: 7cur: SMP kernels /w POLLING enabled - combination > garbles(syncer?) console line message(s) on reboot > > >> 7cur: SMP kernels /w POLLING enabled - combination garbles (syncer?) >> console >> line message(s) on reboot >> >> SMP kernel with POLLING enabled garbles one or more of the last lines in >> console after issuing the {reboot} command >> >> options DEVICE_POLLING >> options HZ=1000 >> >> with or without sysctl -w kern.polling.enable=1 or sysctl -w >> kern.polling.enable=0 >> >> The garbled lines are between 'shutting down bufdaemon' and 'all buffs >> synced' (after 'bufdaemon', I presume these are the syncer, 'Syncing >> disks, vnodes synced' lines) >> >> I found it only reproducable with SMP /apic enabled kernel. Console >> messages >> after issuing reboot on UP kernels with polling_enabled are readable. >> >> Note: polling wasn't manually set on any device (tested on UP and SMP >> kernels) e.g.: no ifconfig em0 polling > > > Funny you should say that. Noticed that last night when rebooting one of > our new 7.0 machines but assumed it was a one off remote console > corruption. > > Just tested this again and its not. So I can confirm the corruption here > on 7.0-PRERELEASE amd64 without polling. It's harmless (actually a sign of increased concurrency); two threads are running printf concurrently. Add options PRINTF_BUFR_SIZE=[...] if you don't want to see this. Kris From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 13:09:37 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C84716A418 for ; Sat, 26 Jan 2008 13:09:37 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.153]) by mx1.freebsd.org (Postfix) with ESMTP id A3E5113C448 for ; Sat, 26 Jan 2008 13:09:36 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so1108000fgg.35 for ; Sat, 26 Jan 2008 05:09:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=GQyYcX+sdAP9aHltplo+/jRb4Fgfg2CVz1r6zYhjJLQ=; b=R9ZJBLVlH/g5UQJdMM9rXL6m/6I/7rn49V5mHzxFEiMw70gZNtpYXyUsFaPDJoPFAwQfLiGWPCdVy8C0Jljnu76iQXFSJ5K23ExSrT+pvGyyDywrfd4v/W1rboMjjUUq5AU6RJL5hnwvPcTqGrIpjhEdJ+qLPtGoJDoc32FUP5s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=CtudfZkzqfdAuDkPogYXjqGBXDSW0+p6Um8pe1DrtYBZqM6aFZ7glH4GRwq4K7wpWJNCQuGA664CLh2JmaqFis3ECf6EXUdPDlloEstke07TATLFyt2Hj5lztUa/xo4XDrPtmTnFqvl7DEvtNfHwpx8xOVWx178yZHSSj5mS0/g= Received: by 10.86.72.15 with SMTP id u15mr2994375fga.21.1201352975231; Sat, 26 Jan 2008 05:09:35 -0800 (PST) Received: by 10.86.53.7 with HTTP; Sat, 26 Jan 2008 05:09:35 -0800 (PST) Message-ID: <3bbf2fe10801260509o12f7d5dof399a751ef48e5c7@mail.gmail.com> Date: Sat, 26 Jan 2008 14:09:35 +0100 From: "Attilio Rao" Sender: asmrookie@gmail.com To: "Scot Hetzel" In-Reply-To: <790a9fff0801252015l34f524d1k704fa0accffe2545@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <790a9fff0801150552l542a4238ofc12efe5fdb45fc2@mail.gmail.com> <20080115143924.GB57756@deviant.kiev.zoral.com.ua> <20080124122808.GA15600@freefall.freebsd.org> <3bbf2fe10801240518i6e18b2f5w84de652d4170c95b@mail.gmail.com> <790a9fff0801252015l34f524d1k704fa0accffe2545@mail.gmail.com> X-Google-Sender-Auth: ba6f17f5fd573026 Cc: freebsd-current@freebsd.org Subject: Re: panic: System call lstat returning with 1 locks held X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 13:09:37 -0000 2008/1/26, Scot Hetzel : > On 1/24/08, Attilio Rao wrote: > > 2008/1/24, Yar Tikhiy : > > > On Tue, Jan 15, 2008 at 04:39:24PM +0200, Kostik Belousov wrote: > > > > > > > > I think this could be related to the recent vn_lock()/VOP_LOCK() KPI changes. > > > > Please, add DEBUG_VFS_LOCKS to the kernel config, and do the > > > > show lockedvnods > > > > from the ddb prompt when the panic occurs. The witness does not track > > > > the lockmgr locks. > > > > > > I think I'm seeing the same panic on UFS. It's rather nasty: I > > > cannot rebuild CURRENT natively due to it so I have to build it > > > under 6-STABLE. My favourite way to trigger the panic reliably is > > > running `make install' in a simple port directory, e.g., portmaster, > > > but my system also panics during daily scripts run and, as already > > > said, if trying to build world. > > > > Yar, > > as it seems reproducible for you, can you please add this patch to the tree: > > http://www.freebsd.org/~attilio/debug_tdlocks.diff > > > > compile your kernel with: > > options KTR > > options KTR_COMPILE=(KTR_SPARE2) > > options KTR_MASK=(KTR_SPARE2) > > options KTR_ENTRIES=32768 > > > > and once kernel panics, at ddb prompts do: > > > show ktr > > > > I added the above options to my kernel, and performed a scripted textdump. > > /sbin/ddb script lockinfo="show locks; show alllocks; show lockedvnods" > /sbin/ddb script kdb.enter.panic="textdump set; capture on; show ktr ; > run lockinfo ; show pcpu; bt; ps; alltrace; capture off; call doadump; > reset" > > After the kernel paniced, the kdb.enter.panic script ran and created a > textdump. When I extracted the 2.7M ddb.txt file, it didn't show any > calls to lockmgr_disown in the ktr trace. > > Let me know if there is anything else that I can do. > > To get this dump, DB_CAPTURE_MAXBUFSIZE (sys/ddb/db_capture.c) needed > to be increased from its default of 512K to 5M, and then setting the > debug.ddb.capure.bufsize to 5M after rebooting with the new kernel. Scot, thanks a lot for your effort. I think I will produce more patch which can help for diagnosis very soon so that we can gather more informations and see what is the real culprit of this. > See PR 119993 (http://www.freebsd.org/cgi/query-pr.cgi?pr=119993) > which adds two new kernel options to allow the capture buffer size to > be changed at compile time. Oh, there is a PR bugathon too, this week... :) Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 14:29:05 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 10D4916A46B; Sat, 26 Jan 2008 14:29:05 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.freebsd.org (Postfix) with ESMTP id 54AE213C43E; Sat, 26 Jan 2008 14:29:04 +0000 (UTC) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.4/8.13.4) with ESMTP id m0QET1kx051254; Sat, 26 Jan 2008 17:29:02 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.4/8.13.4/Submit) id m0QET1JJ051253; Sat, 26 Jan 2008 17:29:01 +0300 (MSK) (envelope-from yar) Date: Sat, 26 Jan 2008 17:29:01 +0300 From: Yar Tikhiy To: Attilio Rao Message-ID: <20080126142901.GD49535@comp.chem.msu.su> References: <790a9fff0801150552l542a4238ofc12efe5fdb45fc2@mail.gmail.com> <20080115143924.GB57756@deviant.kiev.zoral.com.ua> <20080124122808.GA15600@freefall.freebsd.org> <3bbf2fe10801240518i6e18b2f5w84de652d4170c95b@mail.gmail.com> <20080124145811.GB78114@comp.chem.msu.su> <3bbf2fe10801240707o72b927cg74dbf9b7bbcd88fc@mail.gmail.com> <20080125075551.GB21633@comp.chem.msu.su> <3bbf2fe10801250000k5852c2f2j5d1897c900096818@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3bbf2fe10801250000k5852c2f2j5d1897c900096818@mail.gmail.com> User-Agent: Mutt/1.5.9i Cc: Kostik Belousov , freebsd-current@freebsd.org Subject: Re: panic: System call lstat returning with 1 locks held X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 14:29:05 -0000 On Fri, Jan 25, 2008 at 09:00:07AM +0100, Attilio Rao wrote: > 2008/1/25, Yar Tikhiy : > > > > I don't deserve these kind words because I disinformed you seriously. > > > > My panic appears to be related not to UFS, but to NTFS. Namely I > > have an NTFS volume mounted read-only at /ntfs. I have no idea why > > the ports framework touches the /ntfs sub-tree, but not mounting > > it in the first place makes the panic go away. (I still wonder why > > my system would also panic during buildworld, which should not touch > > my /ntfs at all... Now I'll try to do a buildworld w/o /ntfs mounted.) > > Well, this is still to be fixed :) No doubt. :-) But the urgency of this problem appears much lower than that I estimated in the first place--fortunately. Broken UFS would be a nightmare. > > At the same time, dismounting the NTFS volume leads to an instant > > panic of a similar kind: > > > > panic: System call unmount returning with 5 locks held > > > > More debug output is attached. [...] > Do you see any call to lockmgr_disown() in this ktr trace? > Can you past relevant lines of it, otherwise? I've uploaded the full "show ktr" outputs for the lstat- and umount-triggered panics there: http://people.freebsd.org/~yar/debug/ Here's their summary: $ awk '{print $3}' ktr_lstat.txt | sort | uniq -c 32752 _lockmgr: 8 sharelock: 8 shareunlock: $ awk '{print $4}' ktr_lstat.txt | sort | uniq -c 16 0xc322ccc0 32752 0xc37e1220 $ awk '{print $3}' ktr_umount.txt | sort | uniq -c 28663 _lockmgr: 1901 lockmgr_disown: 1102 sharelock: 1102 shareunlock: $ awk '{print $4}' ktr_umount.txt | sort | uniq -c 4550 0xc322ccc0 288 0xc3281220 14 0xc3282220 322 0xc3282660 104 0xc33e6220 2 0xc33e6440 4 0xc3520220 10 0xc3520440 24 0xc3772220 82 0xc3772aa0 7149 0xc3772cc0 358 0xc3774000 17766 0xc3774220 288 0xc3774440 1058 0xc3774660 719 0xc3774880 30 0xc3775000 That is, I lied again, sorry: There were calls to functions other than _lockmgr. But the ktr log for umount looks much more interesting than that for lstat. I'm ready to do more debug runs if needed--instructions are welcome. Thank you! -- Yar From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 14:38:03 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 47C1E16A418 for ; Sat, 26 Jan 2008 14:38:03 +0000 (UTC) (envelope-from prvs=1911771df7=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 8B30113C4E1 for ; Sat, 26 Jan 2008 14:38:02 +0000 (UTC) (envelope-from prvs=1911771df7=killing@multiplay.co.uk) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk; s=Multiplay; t=1201358223; x=1201963023; q=dns/txt; h=Received: Message-ID:From:To:Cc:References:Subject:Date:MIME-Version: Content-Type:Content-Transfer-Encoding; bh=SS4EfWASgbGaoOGqDgzK4 b7cop2fu0+heNHIXYLBeTo=; b=f0XiTZAlEDoj8X8d0bJ5xtRKBM7G26sygs8xn FFcayArQOq1pegWu7+Wucl+PBFCnxnpcNnTsYGHf2gTJQI8YrhcuqByld7pQox1p f+hkQ28YQEJyPJlja2yi42cGyasYTgeMXKMzrMQNIN1WhQJjSqVG99YFC9u2y8vT ikY/Ec= X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-14.7 required=6.0 tests=BAYES_00, USER_IN_WHITELIST, USER_IN_WHITELIST_TO autolearn=ham version=3.1.8 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v9.6.3) with ESMTP id md50004938786.msg; Sat, 26 Jan 2008 14:37:01 +0000 Message-ID: <003f01c86028$e7520690$b6db87d4@multiplay.co.uk> From: "Steven Hartland" To: "Kris Kennaway" References: <292361ab0801252036g75df6800x3b799aedaed02bde@mail.gmail.com><003001c85fd9$03ea2e40$b6db87d4@multiplay.co.uk> <479B082D.4020309@FreeBSD.org> Date: Sat, 26 Jan 2008 14:36:57 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 212.135.219.182 X-Return-Path: prvs=1911771df7=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-Spam-Processed: mail1.multiplay.co.uk, Sat, 26 Jan 2008 14:37:02 +0000 X-MDAV-Processed: mail1.multiplay.co.uk, Sat, 26 Jan 2008 14:37:03 +0000 Cc: Chargen , freebsd-current@freebsd.org Subject: Re: SMP kernels /w POLLING enabled - combination garbles(syncer?) console line message(s) on 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: Sat, 26 Jan 2008 14:38:03 -0000 ----- Original Message ----- From: "Kris Kennaway" > > It's harmless (actually a sign of increased concurrency); two threads > are running printf concurrently. Add options PRINTF_BUFR_SIZE=[...] if > you don't want to see this. Surely if it was just concurrency it would just be the messages jumbled and not totally corrupt as though some buffer overrun had happened? Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 14:45:20 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A35A16A46C for ; Sat, 26 Jan 2008 14:45:20 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2EF3313C4F5; Sat, 26 Jan 2008 14:45:19 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <479B477D.3050001@FreeBSD.org> Date: Sat, 26 Jan 2008 15:45:17 +0100 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.9 (Macintosh/20071031) MIME-Version: 1.0 To: Steven Hartland References: <292361ab0801252036g75df6800x3b799aedaed02bde@mail.gmail.com><003001c85fd9$03ea2e40$b6db87d4@multiplay.co.uk> <479B082D.4020309@FreeBSD.org> <003f01c86028$e7520690$b6db87d4@multiplay.co.uk> In-Reply-To: <003f01c86028$e7520690$b6db87d4@multiplay.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Chargen , freebsd-current@freebsd.org Subject: Re: SMP kernels /w POLLING enabled - combination garbles(syncer?) console line message(s) on 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: Sat, 26 Jan 2008 14:45:20 -0000 Steven Hartland wrote: > > ----- Original Message ----- From: "Kris Kennaway" >> >> It's harmless (actually a sign of increased concurrency); two threads >> are running printf concurrently. Add options PRINTF_BUFR_SIZE=[...] >> if you don't want to see this. > > Surely if it was just concurrency it would just be the messages jumbled > and not totally corrupt as though some buffer overrun had happened? Hard to say since I dont think you defined or gave an example of "garbled" :) Kris From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 14:53:08 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01B8B16A420; Sat, 26 Jan 2008 14:53:08 +0000 (UTC) (envelope-from prvs=1911771df7=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 4384813C45A; Sat, 26 Jan 2008 14:53:06 +0000 (UTC) (envelope-from prvs=1911771df7=killing@multiplay.co.uk) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk; s=Multiplay; t=1201359135; x=1201963935; q=dns/txt; h=Received: Message-ID:From:To:Cc:References:Subject:Date:MIME-Version: Content-Type:Content-Transfer-Encoding; bh=nwde6svu/Urw6dir8c3JP nwD8lgEk5ZkNwcJ8HIQYTI=; b=J7+rrbEjkCy6e9ABvlLVmI9hwOqP/zdb8smXP 3N7io18ezuGuKo487OUeJGjneRP6t8eS7uU7R2xDgDSL1olbrr1ZOg+xL8/M20GD Fk3qJGx94bQAVVabOSu/Ya3oLGEYDxChI5b4JVmlqyPJgnTLBQ/GkJkeesG6VeB4 xC9gsM= X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-14.7 required=6.0 tests=BAYES_00, USER_IN_WHITELIST, USER_IN_WHITELIST_TO autolearn=ham version=3.1.8 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v9.6.3) with ESMTP id md50004938830.msg; Sat, 26 Jan 2008 14:52:13 +0000 Message-ID: <005501c8602b$07284900$b6db87d4@multiplay.co.uk> From: "Steven Hartland" To: "Kris Kennaway" References: <292361ab0801252036g75df6800x3b799aedaed02bde@mail.gmail.com><003001c85fd9$03ea2e40$b6db87d4@multiplay.co.uk> <479B082D.4020309@FreeBSD.org> <003f01c86028$e7520690$b6db87d4@multiplay.co.uk> <479B477D.3050001@FreeBSD.org> Date: Sat, 26 Jan 2008 14:52:09 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 212.135.219.182 X-Return-Path: prvs=1911771df7=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-Spam-Processed: mail1.multiplay.co.uk, Sat, 26 Jan 2008 14:52:14 +0000 X-MDAV-Processed: mail1.multiplay.co.uk, Sat, 26 Jan 2008 14:52:15 +0000 Cc: Chargen , freebsd-current@freebsd.org Subject: Re: SMP kernels /w POLLING enabled - combination garbles(syncer?) console line message(s) on 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: Sat, 26 Jan 2008 14:53:08 -0000 ----- Original Message ----- From: "Kris Kennaway" >> ----- Original Message ----- From: "Kris Kennaway" >>> >>> It's harmless (actually a sign of increased concurrency); two threads >>> are running printf concurrently. Add options PRINTF_BUFR_SIZE=[...] >>> if you don't want to see this. >> >> Surely if it was just concurrency it would just be the messages jumbled >> and not totally corrupt as though some buffer overrun had happened? > > Hard to say since I dont think you defined or gave an example of > "garbled" :) I'm just building a kernel with PRINTF_BUFR_SIZE=128 is this the recommended value? I'll see if that fixes it but what I've seen is a mixture of what looks like jumbled chars and total Greek i.e. none a-zA-Z0-9... chars. I'll look to get a screen shot of the console if I can reproduce reliably. Thanks for the quick answers :) Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 14:58:38 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1306216A477 for ; Sat, 26 Jan 2008 14:58:38 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from outbound0.mx.meer.net (outbound0.mx.meer.net [209.157.153.23]) by mx1.freebsd.org (Postfix) with ESMTP id 0263113C45A for ; Sat, 26 Jan 2008 14:58:37 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) by outbound0.mx.meer.net (8.12.10/8.12.6) with ESMTP id m0QEY57T082747; Sat, 26 Jan 2008 06:34:05 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from mail2.meer.net (mail2.meer.net [64.13.141.16]) by mail.meer.net (8.13.3/8.13.3/meer) with ESMTP id m0QEY4Yb052665; Sat, 26 Jan 2008 06:34:04 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com ([203.118.14.76]) (authenticated bits=0) by mail2.meer.net (8.14.1/8.14.1) with ESMTP id m0QEY28G065930; Sat, 26 Jan 2008 06:34:03 -0800 (PST) (envelope-from gnn@neville-neil.com) Date: Sat, 26 Jan 2008 22:33:59 +0800 Message-ID: From: gnn@freebsd.org To: Nenhum_de_Nos In-Reply-To: <4956a5e50801242020j41fea759v84720c62a246db63@mail.gmail.com> References: <012101c85cbe$3d93fef0$292d280a@friedman.net> <4795B6ED.8020902@beardz.net> <003901c85d02$96a78d60$292d280a@friedman.net> <4956a5e50801242019m37675b90t7fbbb72d4d917960@mail.gmail.com> <4956a5e50801242020j41fea759v84720c62a246db63@mail.gmail.com> User-Agent: Wanderlust/2.15.5 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.7 Emacs/22.1.50 (i386-apple-darwin8.10.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: freebsd-current@freebsd.org Subject: Re: IPSEC on 7.0-PRERELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 14:58:38 -0000 At Fri, 25 Jan 2008 01:20:08 -0300, Nenhum_de_Nos wrote: > > ---------- Forwarded message ---------- > From: Nenhum_de_Nos > Date: Jan 25, 2008 1:19 AM > Subject: Re: IPSEC on 7.0-PRERELEASE > To: "Dr. Aharon Friedman" > > > On Jan 22, 2008 11:25 AM, Dr. Aharon Friedman wrote: > > This looks like the solution. It did pass compile. I have not run it yet, > > but I am sure it will work. Here is the configuration part for IPSEC: > > > > > > > > options IPSEC #IP security (requires device crypto) > > > > options IPSEC_FILTERTUNNEL #filter ipsec packets from a > > tunnel > > > > device enc #IPsec interface > > > > device crypto # core crypto support > > > > device cryptodev # /dev/crypto for access to h/w > > > > > > > > Aharon > > I have a IPSec tunnel over gif ifaces and all ok. was I supposed to > change anything ? > Sorry to reply so late, I'm traveling at the moment. In 7.0 we have moved to a single IPsec stack, that stack requires the "device crypto" line whether you're using software or hardware cryptography. I think it's time for a documentation update but that will have to wait until I clear away some other $dayjob related work. If someone is up for updating our IPsec docs I'd be able to help with that, just not do it completely on my own. Best, George From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 15:35:08 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E79416A477 for ; Sat, 26 Jan 2008 15:35:08 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id 3F3CD13C503 for ; Sat, 26 Jan 2008 15:35:08 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from localhost (amavis.str.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 5891F41C747; Sat, 26 Jan 2008 16:35:06 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([62.111.66.27]) by localhost (amavis.str.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id 8UYWkE2S8GS5; Sat, 26 Jan 2008 16:35:06 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id 08F3341C759; Sat, 26 Jan 2008 16:35:06 +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 C7D4C444885; Sat, 26 Jan 2008 15:33:44 +0000 (UTC) Date: Sat, 26 Jan 2008 15:33:44 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: "George V. Neville-Neil" In-Reply-To: Message-ID: <20080126153015.U36482@maildrop.int.zabbadoz.net> References: <012101c85cbe$3d93fef0$292d280a@friedman.net> <4795B6ED.8020902@beardz.net> <003901c85d02$96a78d60$292d280a@friedman.net> <4956a5e50801242019m37675b90t7fbbb72d4d917960@mail.gmail.com> <4956a5e50801242020j41fea759v84720c62a246db63@mail.gmail.com> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: IPSEC on 7.0-PRERELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 15:35:08 -0000 On Sat, 26 Jan 2008, gnn@freebsd.org wrote: [ipsec options, etc.] > Sorry to reply so late, I'm traveling at the moment. In 7.0 we have > moved to a single IPsec stack, that stack requires the "device crypto" > line whether you're using software or hardware cryptography. I think > it's time for a documentation update but that will have to wait until > I clear away some other $dayjob related work. If someone is up for > updating our IPsec docs I'd be able to help with that, just not do it > completely on my own. I think I updated all the man pages I was aware of. I am not going to comment on the handbook. I think we should rather remove that section, if noone has updated it (since FreeBSD 4;) and maybe bring it back at a later time. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT Software is harder than hardware so better get it right the first time. From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 16:42:46 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E062416A418 for ; Sat, 26 Jan 2008 16:42:46 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with SMTP id 7F9B413C469 for ; Sat, 26 Jan 2008 16:42:46 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 12209 invoked by uid 399); 26 Jan 2008 16:42:46 -0000 Received: from localhost (HELO ?192.168.0.4?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 26 Jan 2008 16:42:46 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <479B6303.6000401@FreeBSD.org> Date: Sat, 26 Jan 2008 08:42:43 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Yar Tikhiy References: <790a9fff0801150552l542a4238ofc12efe5fdb45fc2@mail.gmail.com> <20080115143924.GB57756@deviant.kiev.zoral.com.ua> <20080124122808.GA15600@freefall.freebsd.org> <3bbf2fe10801240518i6e18b2f5w84de652d4170c95b@mail.gmail.com> <20080124145811.GB78114@comp.chem.msu.su> <3bbf2fe10801240707o72b927cg74dbf9b7bbcd88fc@mail.gmail.com> <20080125075551.GB21633@comp.chem.msu.su> <3bbf2fe10801250000k5852c2f2j5d1897c900096818@mail.gmail.com> <20080126142901.GD49535@comp.chem.msu.su> In-Reply-To: <20080126142901.GD49535@comp.chem.msu.su> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Attilio Rao , Kostik Belousov , freebsd-current@freebsd.org Subject: Re: panic: System call lstat returning with 1 locks held X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 16:42:47 -0000 Yar Tikhiy wrote: > No doubt. :-) But the urgency of this problem appears much lower > than that I estimated in the first place--fortunately. Broken UFS > would be a nightmare. IMO if we're going to ship NTFS support in the base it should actually function, or at minimum not panic the box. As I reported earlier, I can panic my -current system with 100% reliability with fairly light access to an NTFS volume, which I consider to be a fairly large problem, at least for my personal usage pattern. Doug -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 17:10:40 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C78D16A474 for ; Sat, 26 Jan 2008 17:10:40 +0000 (UTC) (envelope-from w@wrzask.pl) Received: from mx.oak.pl (mx.oak.pl [217.96.108.251]) by mx1.freebsd.org (Postfix) with ESMTP id BF7F513C4F8 for ; Sat, 26 Jan 2008 17:10:39 +0000 (UTC) (envelope-from w@wrzask.pl) Received: by oak.pl (Postfix, from userid 1002) id 7BAD51CD12; Sat, 26 Jan 2008 17:54:14 +0100 (CET) Date: Sat, 26 Jan 2008 17:54:14 +0100 From: Jan Srzednicki To: John Birrell Message-ID: <20080126165414.GA53681@oak.pl> References: <20080123235033.GA3126@what-creek.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080123235033.GA3126@what-creek.com> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: gallatin@cs.duke.edu, current@freebsd.org Subject: Re: DTrace for FreeBSD - status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 17:10:40 -0000 On Wed, Jan 23, 2008 at 11:50:33PM +0000, John Birrell wrote: > On Wed, 23 Jan 2008 14:05:23 -0600, Andrew Gallatin > wrote: > > What is the status of Dtrace in FreeBSD? I thought the original port > > was permantly stalled due to licensing conflicts over CDDL, and > > that John was starting from scratch. > > Cisco is currently funding the port of DTrace to FreeBSD part of their > move to FreeBSD. > > I am probably a week away from putting up a set of diffs for the > initial integration into CURRENT. See: > for the list > of changes/reasons. That page is still a work in progress. Cool! Any plans on MFC'ing it to the 7.x line after the thing gets stable? -- Jan Srzednicki :: http://wrzask.pl/ "Remember, remember, the fifth of November" -- V for Vendetta From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 17:18:50 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6844116A417 for ; Sat, 26 Jan 2008 17:18:50 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by mx1.freebsd.org (Postfix) with ESMTP id C75C513C468 for ; Sat, 26 Jan 2008 17:18:49 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so1181203fgg.35 for ; Sat, 26 Jan 2008 09:18:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=7L1qCG6iDj9Z+T6kdx3ZeB2CRNrz0pecpyIZp6P/1vY=; b=F0vJAG9HQSjWxm5z7x/P1vLESMWfP8+ypbZkoj/faMuJFzDZeCK4QSuawyhweNjvGp8SGMaEKDsJ488locAATxgz4O/Dzorwc5QPOzgpOEBtbQIUtNspMBbAMcBPwW7xYcMB6uXsLVsPc9u/QWvzSaT6Ssa/wlbSBn1nCeWhElg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=GLgPCcEWcbNHwCmIW4RlK2HSb0VDhgixFyPYNqDxPQaKxCOVkjOkDZ15Cg9xI4JZzjtmptt+AXOYW0mH5Pb2UaUZ/x4c9YDNh1rztrg0z5hvDsd/Cj+RGrM3f07pX3Bwp4TV6WxbKN02jdDf58Lyhg76tn+rUfa5WPsVkdLg/4M= Received: by 10.86.31.18 with SMTP id e18mr3180711fge.35.1201367927148; Sat, 26 Jan 2008 09:18:47 -0800 (PST) Received: by 10.86.53.7 with HTTP; Sat, 26 Jan 2008 09:18:47 -0800 (PST) Message-ID: <3bbf2fe10801260918k56c1a73hf28ff154eca0b74c@mail.gmail.com> Date: Sat, 26 Jan 2008 18:18:47 +0100 From: "Attilio Rao" Sender: asmrookie@gmail.com To: "Doug Barton" In-Reply-To: <479B6303.6000401@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <790a9fff0801150552l542a4238ofc12efe5fdb45fc2@mail.gmail.com> <20080115143924.GB57756@deviant.kiev.zoral.com.ua> <20080124122808.GA15600@freefall.freebsd.org> <3bbf2fe10801240518i6e18b2f5w84de652d4170c95b@mail.gmail.com> <20080124145811.GB78114@comp.chem.msu.su> <3bbf2fe10801240707o72b927cg74dbf9b7bbcd88fc@mail.gmail.com> <20080125075551.GB21633@comp.chem.msu.su> <3bbf2fe10801250000k5852c2f2j5d1897c900096818@mail.gmail.com> <20080126142901.GD49535@comp.chem.msu.su> <479B6303.6000401@FreeBSD.org> X-Google-Sender-Auth: 00575f0af70a79b5 Cc: Kostik Belousov , Yar Tikhiy , freebsd-current@freebsd.org Subject: Re: panic: System call lstat returning with 1 locks held X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 17:18:50 -0000 2008/1/26, Doug Barton : > Yar Tikhiy wrote: > > > No doubt. :-) But the urgency of this problem appears much lower > > than that I estimated in the first place--fortunately. Broken UFS > > would be a nightmare. > > IMO if we're going to ship NTFS support in the base it should actually > function, or at minimum not panic the box. As I reported earlier, I can > panic my -current system with 100% reliability with fairly light access > to an NTFS volume, which I consider to be a fairly large problem, at > least for my personal usage pattern. I'm not sure now, are you referring to some problems introduced by my patches or not? Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 19:14:06 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04E5816A41A; Sat, 26 Jan 2008 19:14:06 +0000 (UTC) (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 A93CE13C447; Sat, 26 Jan 2008 19:14:05 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.14.2/8.14.2) with ESMTP id m0QJE4X5080897; Sat, 26 Jan 2008 14:14:04 -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.14.2/8.14.1) with ESMTP id m0QJE4b5069864; Sat, 26 Jan 2008 14:14:04 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 53CCF73039; Sat, 26 Jan 2008 14:14:04 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080126191404.53CCF73039@freebsd-current.sentex.ca> Date: Sat, 26 Jan 2008 14:14:04 -0500 (EST) X-Virus-Scanned: ClamAV 0.92/5493/Thu Jan 17 13:09:26 2008 clamav-milter version 0.91.2 on clamscanner1 X-Virus-Status: Clean 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: Sat, 26 Jan 2008 19:14:06 -0000 TB --- 2008-01-26 18:10:00 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-01-26 18:10:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-01-26 18:10:00 - cleaning the object tree TB --- 2008-01-26 18:10:47 - cvsupping the source tree TB --- 2008-01-26 18:10:47 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-01-26 18:10:54 - building world (CFLAGS=-O -pipe) TB --- 2008-01-26 18:10:54 - cd /src TB --- 2008-01-26 18:10:54 - /usr/bin/make -B buildworld >>> World build started on Sat Jan 26 18:10:56 UTC 2008 >>> 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 [...] /src/usr.sbin/setfmac/setfmac.c: In function 'main': /src/usr.sbin/setfmac/setfmac.c:161: warning: field precision should have type 'int', but argument 3 has type 'size_t' /src/usr.sbin/setfmac/setfmac.c:166: warning: field precision should have type 'int', but argument 2 has type 'size_t' /src/usr.sbin/setfmac/setfmac.c:174: warning: field precision should have type 'int', but argument 3 has type 'size_t' /src/usr.sbin/setfmac/setfmac.c:178: warning: field precision should have type 'int', but argument 4 has type 'size_t' /src/usr.sbin/setfmac/setfmac.c: In function 'apply_specs': /src/usr.sbin/setfmac/setfmac.c:443: warning: field precision should have type 'int', but argument 2 has type 'size_t' /src/usr.sbin/setfmac/setfmac.c:487: warning: field precision should have type 'int', but argument 3 has type 'size_t' *** Error code 1 Stop in /src/usr.sbin/setfmac. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-01-26 19:14:04 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-01-26 19:14:04 - ERROR: failed to build world TB --- 2008-01-26 19:14:04 - tinderbox aborted TB --- 2836.20 user 337.32 system 3843.45 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 19:30:33 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5C5916A41B for ; Sat, 26 Jan 2008 19:30:33 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.freebsd.org (Postfix) with ESMTP id 62CB713C4E7 for ; Sat, 26 Jan 2008 19:30:33 +0000 (UTC) (envelope-from max@love2party.net) Received: from amd64.laiers.local (dslb-088-067-244-178.pools.arcor-ip.net [88.67.244.178]) by mrelayeu.kundenserver.de (node=mrelayeu8) with ESMTP (Nemesis) id 0ML31I-1JIqXJ1yrP-0002go; Sat, 26 Jan 2008 20:17:53 +0100 From: Max Laier Organization: FreeBSD To: freebsd-current@freebsd.org Date: Sat, 26 Jan 2008 20:17:45 +0100 User-Agent: KMail/1.9.7 References: <479A2389.2000802@moneybookers.com> In-Reply-To: <479A2389.2000802@moneybookers.com> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2896453.v3WcQ0IqKx"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200801262017.52091.max@love2party.net> X-Provags-ID: V01U2FsdGVkX1/j2+fKqN1e40MJzOhKxjtgsVw+Il9Mfkvyxym SQEM7Ro3+wi8DBS1NuXmwz/KryCcILNTkb3VhFKohi4T8xCuDA v+j6i1ISEIguxE0Ocqppj9Yn/R5Hw1rLdclNy8aLWM= Cc: Stefan Lambrev Subject: Re: FreeBSD 7, bridge, PF and syn flood = very bad performance X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 19:30:33 -0000 --nextPart2896453.v3WcQ0IqKx Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 25 January 2008, Stefan Lambrev wrote: > Greetings, > > Does anyone try to see PF with "keep state" in action when under syn > flood attack? > I tried to get some help in freebsd-pf@, because the test firewall, > that I build hardly can handle 2-5MB/s syn flood. > Unfortunately I do not saw useful advice. > The problem is that a quad core bridge firewall running freebsd 7 amd64 > with PF is near useless and can't handle "small" SYN ddos. > > Here is the schema that I'm testing: > web server (freebsd) - freebsd (bridged interfaces) - gigabit switch - > clients + flooders > In this configuration ~25MB/s syn flood (and I think this limit is > because of my switch) is not a problem and the web server responds > without a problem. > With this configuration netperf -l 610 -p 10303 -H 10.3.3.1 shows > 116MB/s stable speed , so I guess there are no problems with cables, > hardware and etc :) > > But when I start pf (see below the config file) the traffic drops to > 2-3MB/s and the web server is hardly accessible. > It seems that device polling helps a lot in this situation, and at > least the bridge firewall is accessible. Without "polling" the firewall > is so heavily loaded > that even commands like "date" take few seconds to finish, with 2 cores > at ~100% idle at same time. > > I have "flat profiles" from hwpmc, and I think it indicates a problem: > > (bridge, pf enabled, polling enabled, sched_ule - I have profiles and > for other combinations too if needed) > % cumulative self self total > time seconds seconds calls ms/call ms/call name > 24.0 268416.00 268416.00 0 100.00% _mtx_lock_sleep Can you build a kernel with LOCK_PROFILING and try to figure out which=20 lock is causing this? > [1] 6.7 343572.50 75156.50 0 100.00% > pf_state_compare_ext_gwy [2] > 6.7 418405.50 74833.00 0 100.00% pf_src_compare > [3] 3.9 462298.50 43893.00 0 100.00% > pf_state_compare_lan_ext [4] > 3.6 503019.50 40721.00 0 100.00% pf_test [5] > 3.2 538671.50 35652.00 0 100.00% pf_test_tcp [6] > 3.1 573743.50 35072.00 0 100.00% bcopy [7] > 2.3 599406.50 25663.00 0 100.00% bridge_pfil [8] > 2.0 622096.50 22690.00 0 100.00% > pf_state_compare_id [9] > 2.0 644331.50 22235.00 0 100.00% pfsync_pack_state > [10] 1.5 661563.50 17232.00 0 100.00% uma_zalloc_arg > [11] 1.3 676296.50 14733.00 0 100.00% bzero [12] 1.3 > 690842.00 14545.50 0 100.00% > bus_dmamap_load_mbuf_sg [13] > 1.2 704521.50 13679.50 0 100.00% uma_zfree_arg > [14] 1.2 717554.50 13033.00 0 100.00% > bridge_rtnode_lookup [15] > 1.2 730575.50 13021.00 0 100.00% _rw_rlock [16] > 1.1 743076.50 12501.00 0 100.00% rn_match [17] > 1.0 754016.50 10940.00 0 100.00% bridge_forward > [18] 1.0 764766.00 10749.50 0 100.00% em_encap [19] > 0.9 775400.00 10634.00 0 100.00% _rw_runlock [20] > ........ > > Also when running without polling top -S shows that external em0 > interface's taskq takes 100% CPU > The situation is even worse when running with SCHED_BSD. > > Here is my test pf.conf > quick > #macros > ext_if=3D"em0" > int_if=3D"em1" > br_if=3D"bridge0" > > www=3D"10.3.3.1" > > #sets > set skip on lo0 > set skip on $int_if > set skip on $br_if > set limit states 20000000 > set limit src-nodes 19000000 > set optimization aggressive > > table persist file "/etc/abusive_hosts" > > block log quick from to any > block log quick from any to > > pass in on $ext_if proto tcp from any to $www port { 80, 443 } flags > S/SA keep state \ > (source-track rule, max-src-conn-rate 150/10, max-src-states 500, > max-src-nodes 4000000, overload flush global) =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart2896453.v3WcQ0IqKx Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHm4dgXyyEoT62BG0RAtFyAJ94+Y6hqzfnenbDZ9xzrrER9Nf8twCfVxXk VkPVOOSTLssI1OFEarjK4vg= =Lo31 -----END PGP SIGNATURE----- --nextPart2896453.v3WcQ0IqKx-- From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 20:31:59 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B212016A473 for ; Sat, 26 Jan 2008 20:31:59 +0000 (UTC) (envelope-from rmtodd@ichotolot.servalan.com) Received: from mx2.synetsystems.com (mx2.synetsystems.com [76.10.206.15]) by mx1.freebsd.org (Postfix) with ESMTP id 8D78413C455 for ; Sat, 26 Jan 2008 20:31:59 +0000 (UTC) (envelope-from rmtodd@ichotolot.servalan.com) Received: by mx2.synetsystems.com (Postfix, from userid 66) id DD4796D2; Fri, 25 Jan 2008 15:15:24 -0500 (EST) Received: from rmtodd by servalan.servalan.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1JIUO5-000J6O-WC for freebsd-current@freebsd.org; Fri, 25 Jan 2008 13:38:54 -0600 To: freebsd-current@freebsd.org References: <18328.45282.562906.708945@celery.zuhause.org> <18329.22270.123314.900543@bhfs.zuhause.org> From: Richard Todd Date: Fri, 25 Jan 2008 13:38:53 -0600 In-Reply-To: <18329.22270.123314.900543@bhfs.zuhause.org> (bruce@zuhause.mn.org's message of "Thu, 24 Jan 2008 21:26:54 -0600") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.21 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Weird performance behaviour in 7.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: Sat, 26 Jan 2008 20:31:59 -0000 bruce@zuhause.mn.org writes: > Richard Todd writes: > > This wouldn't by any chance be an Intel 965-chipset-based motherboard > > with 4G or more of memory, would it? Because there's an interesting > > little bug in the BIOS on some of those boards which causes the > > cache-control registers to incorrectly declare a chunk of main memory > > as uncacheable. This results in random slowdowns depending on whether > > your process lands in the "bad" zone of memory or not. See > > http://article.gmane.org/gmane.os.freebsd.stable/50135/ for more details. > > Bingo! This is a Intel DG965WH with 4 GB of memory. I don't think I > can downgrade to the 1669 firmware because of the processor I'm > using. The Fedora thread says that there's a hack to do the following > in linux to fix the "bad" zone > echo "base=0x1a8000000 size=0x4000000 type=write-back" >| /proc/mtrr Yeah, but the exact numbers depend on what exactly the bad zone is, and that seems to vary from system to system (depending on what memory is installed and what rev of the BIOS. Let's see if we can figure it out. It's gonna be one of the ranges in the list you posted below (the last few ones are the important ones) > 0x0/0xf080000000 BIOS write-back set-by-firmware active bogus > 0x80000000/0xf040000000 BIOS write-back set-by-firmware active bogus > 0xc0000000/0xf010000000 BIOS write-back set-by-firmware active bogus > 0xcf800000/0xf000800000 BIOS uncacheable set-by-firmware active bogus > 0xcf700000/0xf000100000 BIOS uncacheable set-by-firmware active bogus These entries each specify a start address and a length of a range of memory. Those ranges look a lot bigger than they really are thanks to that leading "f" digit on all of them, which tells me that you're running in 64-bit mode; apparently in 64-bit mode the Intel cache-control registers have fewer active bits than the AMD64 equivalent for which the existing amd64 machdep code in the kernel was written for, so we get 4 gratuitous extra high bits. So, e.g., the first range is actually of length 0x80000000 (which is 2G) starting at address zero; that one's "write-back" so cache is enabled on that range. Ditto the next one which is length 0x40000000 (1G) at address 2G. I'm guessing the bad ones are the two "uncachable" entries at the end, so try doing memcontrol clear -b 0xcf800000 -l 0xf000800000 memcontrol clear -b 0xcf700000 -l 0xf000100000 and see if that fixes things, and doesn't break anything. From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 20:32:31 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 711DD16A4DA for ; Sat, 26 Jan 2008 20:32:31 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 2E45613C4CC for ; Sat, 26 Jan 2008 20:32:31 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id E41862083; Sat, 26 Jan 2008 21:32:22 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 6DC922049; Sat, 26 Jan 2008 21:32:22 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id 5C660844AF; Sat, 26 Jan 2008 21:32:22 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Stefan Lambrev References: <479A2389.2000802@moneybookers.com> Date: Sat, 26 Jan 2008 21:32:22 +0100 In-Reply-To: <479A2389.2000802@moneybookers.com> (Stefan Lambrev's message of "Fri\, 25 Jan 2008 19\:59\:37 +0200") Message-ID: <86bq78nx9l.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 7, bridge, PF and syn flood = very bad performance X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 20:32:31 -0000 Stefan Lambrev writes: > Does anyone try to see PF with "keep state" in action when under syn > flood attack? Try "synproxy state" instead of "keep state". DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 20:36:15 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C45EC16A417 for ; Sat, 26 Jan 2008 20:36:15 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by mx1.freebsd.org (Postfix) with ESMTP id 5950F13C478 for ; Sat, 26 Jan 2008 20:36:15 +0000 (UTC) (envelope-from max@love2party.net) Received: from amd64.laiers.local (dslb-088-066-063-169.pools.arcor-ip.net [88.66.63.169]) by mrelayeu.kundenserver.de (node=mrelayeu1) with ESMTP (Nemesis) id 0MKwpI-1JIrl80FZn-0005nH; Sat, 26 Jan 2008 21:36:14 +0100 From: Max Laier Organization: FreeBSD To: freebsd-current@freebsd.org Date: Sat, 26 Jan 2008 21:36:06 +0100 User-Agent: KMail/1.9.7 References: <479A2389.2000802@moneybookers.com> <86bq78nx9l.fsf@ds4.des.no> In-Reply-To: <86bq78nx9l.fsf@ds4.des.no> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart32471297.4i0ah5vrhh"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200801262136.12975.max@love2party.net> X-Provags-ID: V01U2FsdGVkX1+LaOZHG6nsJ0GG/SxJguCwJ58ZEe99lLhhEcA IE5Epi+pdp2A0gXw++xZm7n3QxKXfboiZPJofWaXvn4zkUVcfR MTUA6umEDUpQs0NZESRK4ea3wUUIzxgZLNrF1tUiKU= Cc: Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= , Stefan Lambrev Subject: Re: FreeBSD 7, bridge, PF and syn flood = very bad performance X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 20:36:15 -0000 --nextPart32471297.4i0ah5vrhh Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 26 January 2008, Dag-Erling Sm=C3=B8rgrav wrote: > Stefan Lambrev writes: > > Does anyone try to see PF with "keep state" in action when under syn > > flood attack? > > Try "synproxy state" instead of "keep state". not on a bridge unfortunately. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart32471297.4i0ah5vrhh Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHm5m8XyyEoT62BG0RAnUDAJ9rPHCZSz+urYuCVE0dvV6Hjy6JegCdF36u DyJHttnGCsf/E9zCvtQOnXc= =dss9 -----END PGP SIGNATURE----- --nextPart32471297.4i0ah5vrhh-- From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 20:52:44 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32E5F16A41A for ; Sat, 26 Jan 2008 20:52:44 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id E577713C458 for ; Sat, 26 Jan 2008 20:52:43 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: by blah.sun-fish.com (Postfix, from userid 1002) id 4F6BF1B10EDC; Sat, 26 Jan 2008 21:52:42 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on blah.cmotd.com X-Spam-Level: X-Spam-Status: No, score=-10.3 required=5.0 tests=ALL_TRUSTED,BAYES_00, MIME_8BIT_HEADER autolearn=no version=3.2.3 Received: from [10.1.1.2] (unknown [192.168.25.10]) by blah.sun-fish.com (Postfix) with ESMTP id AEEEA1B10EEE; Sat, 26 Jan 2008 21:52:39 +0100 (CET) Message-ID: <479B9D97.9080407@moneybookers.com> Date: Sat, 26 Jan 2008 22:52:39 +0200 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= References: <479A2389.2000802@moneybookers.com> <86bq78nx9l.fsf@ds4.des.no> In-Reply-To: <86bq78nx9l.fsf@ds4.des.no> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV 0.91.2/5562/Sat Jan 26 12:34:23 2008 on blah.cmotd.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 7, bridge, PF and syn flood = very bad performance X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 20:52:44 -0000 Dag-Erling Smørgrav wrote: > Stefan Lambrev writes: > >> Does anyone try to see PF with "keep state" in action when under syn >> flood attack? >> > > Try "synproxy state" instead of "keep state". > > DES > From man pf.conf - Rules with synproxy will not work if pf(4) operates on a bridge(4). My short experience from today shows that synproxy can't handle syn flood with random source IP - 150kpps, but I'll test this after few days. From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 20:56:33 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3E6216A417 for ; Sat, 26 Jan 2008 20:56:33 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id A7E5C13C45D for ; Sat, 26 Jan 2008 20:56:33 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 7BC2B2083; Sat, 26 Jan 2008 21:56:25 +0100 (CET) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: -0.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id F0FBC207F; Sat, 26 Jan 2008 21:56:24 +0100 (CET) Received: by ds4.des.no (Postfix, from userid 1001) id DF2FC84461; Sat, 26 Jan 2008 21:56:24 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Stefan Lambrev References: <479A2389.2000802@moneybookers.com> <86bq78nx9l.fsf@ds4.des.no> <479B9D97.9080407@moneybookers.com> Date: Sat, 26 Jan 2008 21:56:24 +0100 In-Reply-To: <479B9D97.9080407@moneybookers.com> (Stefan Lambrev's message of "Sat\, 26 Jan 2008 22\:52\:39 +0200") Message-ID: <86tzl0mhl3.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 7, bridge, PF and syn flood = very bad performance X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 20:56:34 -0000 Stefan Lambrev writes: > Dag-Erling Sm=C3=B8rgrav writes: > > Try "synproxy state" instead of "keep state". > From man pf.conf - Rules with synproxy will not work if pf(4) operates > on a bridge(4). Hmm, why are you experiencing a SYN flood on a bridge? I assume the bridge is inside your network, and the attack comes from outside your network, in which case you should stop it at the entry point. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 21:00:04 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7420816A421 for ; Sat, 26 Jan 2008 21:00:04 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id 31E6A13C46E for ; Sat, 26 Jan 2008 21:00:04 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: by blah.sun-fish.com (Postfix, from userid 1002) id 376951B10EF1; Sat, 26 Jan 2008 22:00:03 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on blah.cmotd.com X-Spam-Level: X-Spam-Status: No, score=-10.6 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.3 Received: from [10.1.1.2] (unknown [192.168.25.10]) by blah.sun-fish.com (Postfix) with ESMTP id CD1AA1B10EEE; Sat, 26 Jan 2008 21:59:59 +0100 (CET) Message-ID: <479B9F4F.5010705@moneybookers.com> Date: Sat, 26 Jan 2008 22:59:59 +0200 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: Max Laier References: <479A2389.2000802@moneybookers.com> <200801262017.52091.max@love2party.net> In-Reply-To: <200801262017.52091.max@love2party.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.91.2/5562/Sat Jan 26 12:34:23 2008 on blah.cmotd.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 7, bridge, PF and syn flood = very bad performance X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 21:00:04 -0000 Max Laier wrote: > On Friday 25 January 2008, Stefan Lambrev wrote: > >> Greetings, >> >> Does anyone try to see PF with "keep state" in action when under syn >> flood attack? >> I tried to get some help in freebsd-pf@, because the test firewall, >> that I build hardly can handle 2-5MB/s syn flood. >> Unfortunately I do not saw useful advice. >> The problem is that a quad core bridge firewall running freebsd 7 amd64 >> with PF is near useless and can't handle "small" SYN ddos. >> >> Here is the schema that I'm testing: >> web server (freebsd) - freebsd (bridged interfaces) - gigabit switch - >> clients + flooders >> In this configuration ~25MB/s syn flood (and I think this limit is >> because of my switch) is not a problem and the web server responds >> without a problem. >> With this configuration netperf -l 610 -p 10303 -H 10.3.3.1 shows >> 116MB/s stable speed , so I guess there are no problems with cables, >> hardware and etc :) >> >> But when I start pf (see below the config file) the traffic drops to >> 2-3MB/s and the web server is hardly accessible. >> It seems that device polling helps a lot in this situation, and at >> least the bridge firewall is accessible. Without "polling" the firewall >> is so heavily loaded >> that even commands like "date" take few seconds to finish, with 2 cores >> at ~100% idle at same time. >> >> I have "flat profiles" from hwpmc, and I think it indicates a problem: >> >> (bridge, pf enabled, polling enabled, sched_ule - I have profiles and >> for other combinations too if needed) >> % cumulative self self total >> time seconds seconds calls ms/call ms/call name >> 24.0 268416.00 268416.00 0 100.00% _mtx_lock_sleep >> > > Can you build a kernel with LOCK_PROFILING and try to figure out which > lock is causing this? > Yes I can build kernel with LOCK_PROFILING. But I have no idea how to use it :) Can you point me to some documentation? From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 21:22:00 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE96C16A417 for ; Sat, 26 Jan 2008 21:21:59 +0000 (UTC) (envelope-from rmtodd@servalan.servalan.com) Received: from mx2.synetsystems.com (mx2.synetsystems.com [76.10.206.15]) by mx1.freebsd.org (Postfix) with ESMTP id A88A213C442 for ; Sat, 26 Jan 2008 21:21:59 +0000 (UTC) (envelope-from rmtodd@servalan.servalan.com) Received: by mx2.synetsystems.com (Postfix, from userid 66) id 9C11961B; Sat, 26 Jan 2008 15:15:18 -0500 (EST) Received: from rmtodd by servalan.servalan.com with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1JIrAE-000FyL-Q1; Sat, 26 Jan 2008 13:58:06 -0600 To: freebsd-current@freebsd.org, bruce@zuhause.mn.org References: <18328.45282.562906.708945@celery.zuhause.org> <18329.22270.123314.900543@bhfs.zuhause.org> From: Richard Todd In-Reply-To: (bruce@zuhause.mn.org's message of "Thu, 24 Jan 2008 21:26:54 -0600") Message-ID: User-Agent: Gnus/5.1008 (Gnus v5.10.8) XEmacs/21.4.21 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Lines: 59 Date: Sat, 26 Jan 2008 13:58:06 -0600 Cc: Subject: Re: Weird performance behaviour in 7.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: Sat, 26 Jan 2008 21:22:00 -0000 bruce@zuhause.mn.org writes: > Richard Todd writes: > > This wouldn't by any chance be an Intel 965-chipset-based motherboard > > with 4G or more of memory, would it? Because there's an interesting > > little bug in the BIOS on some of those boards which causes the > > cache-control registers to incorrectly declare a chunk of main memory > > as uncacheable. This results in random slowdowns depending on whether > > your process lands in the "bad" zone of memory or not. See > > http://article.gmane.org/gmane.os.freebsd.stable/50135/ for more details. > > Bingo! This is a Intel DG965WH with 4 GB of memory. I don't think I > can downgrade to the 1669 firmware because of the processor I'm > using. The Fedora thread says that there's a hack to do the following > in linux to fix the "bad" zone > echo "base=0x1a8000000 size=0x4000000 type=write-back" >| /proc/mtrr Yeah, but the exact numbers depend on what exactly the bad zone is, and that seems to vary from system to system (depending on what memory is installed and what rev of the BIOS. Let's see if we can figure it out. It's gonna be one of the ranges in the list you posted below (the last few ones are the important ones) > 0x0/0xf080000000 BIOS write-back set-by-firmware active bogus > 0x80000000/0xf040000000 BIOS write-back set-by-firmware active bogus > 0xc0000000/0xf010000000 BIOS write-back set-by-firmware active bogus > 0xcf800000/0xf000800000 BIOS uncacheable set-by-firmware active bogus > 0xcf700000/0xf000100000 BIOS uncacheable set-by-firmware active bogus These entries each specify a start address and a length of a range of memory. Those ranges look a lot bigger than they really are thanks to that leading "f" digit on all of them, which tells me that you're running in 64-bit mode; apparently in 64-bit mode the Intel cache-control registers have fewer active bits than the AMD64 equivalent for which the existing amd64 machdep code in the kernel was written for, so we get 4 gratuitous extra high bits. So, e.g., the first range is actually of length 0x80000000 (which is 2G) starting at address zero; that one's "write-back" so cache is enabled on that range. Ditto the next one which is length 0x40000000 (1G) at address 2G. I'm guessing the bad ones are the two "uncachable" entries at the end, so you might try doing memcontrol clear -b 0xcf800000 -l 0xf000800000 memcontrol clear -b 0xcf700000 -l 0xf000100000 and see if that fixes things, and doesn't break anything. I am a bit puzzled that the writeback ranges listed in the above don't seem to actually add up to enough to cover 4G of memory, though. This worries me, in that you may need to add additional cache-control entries. Before trying the memcontrol stuff above, it might help if you could boot the system in verbose mode and record the SMAP entries that get printed by getmemsize() in machdep.c as the system boots. If you have a serial console, this is easy; if you don't it gets tricky, as those SMAP lines appear before the console is fully initialized so that the SMAP lines don't show up in dmesg later, so I had to resort to booting with -d and doing cleverly-placed ddb breakpoints. From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 21:26:00 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC48116A469 for ; Sat, 26 Jan 2008 21:26:00 +0000 (UTC) (envelope-from jb@what-creek.com) Received: from what-creek.com (what-creek.com [66.111.37.70]) by mx1.freebsd.org (Postfix) with ESMTP id A04F313C47E for ; Sat, 26 Jan 2008 21:26:00 +0000 (UTC) (envelope-from jb@what-creek.com) Received: by what-creek.com (Postfix, from userid 102) id 1D9C87321F; Sat, 26 Jan 2008 21:26:00 +0000 (GMT) Date: Sat, 26 Jan 2008 21:26:00 +0000 From: John Birrell To: Jan Srzednicki Message-ID: <20080126212559.GA30553@what-creek.com> References: <20080123235033.GA3126@what-creek.com> <20080126165414.GA53681@oak.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080126165414.GA53681@oak.pl> User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org Subject: Re: DTrace for FreeBSD - status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 21:26:00 -0000 On Sat, Jan 26, 2008 at 05:54:14PM +0100, Jan Srzednicki wrote: > On Wed, Jan 23, 2008 at 11:50:33PM +0000, John Birrell wrote: > > I am probably a week away from putting up a set of diffs for the > > initial integration into CURRENT. See: > > for the list > > of changes/reasons. That page is still a work in progress. > > Cool! > > Any plans on MFC'ing it to the 7.x line after the thing gets stable? Yes. -- John Birrell From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 21:27:39 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6A5C16A41B for ; Sat, 26 Jan 2008 21:27:39 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by mx1.freebsd.org (Postfix) with ESMTP id 7BA2013C4E5 for ; Sat, 26 Jan 2008 21:27:39 +0000 (UTC) (envelope-from max@love2party.net) Received: from amd64.laiers.local (dslb-088-066-063-169.pools.arcor-ip.net [88.66.63.169]) by mrelayeu.kundenserver.de (node=mrelayeu1) with ESMTP (Nemesis) id 0MKwpI-1JIsYr3sfj-0005hn; Sat, 26 Jan 2008 22:27:38 +0100 From: Max Laier Organization: FreeBSD To: freebsd-current@freebsd.org Date: Sat, 26 Jan 2008 22:27:31 +0100 User-Agent: KMail/1.9.7 References: <479A2389.2000802@moneybookers.com> <200801262017.52091.max@love2party.net> <479B9F4F.5010705@moneybookers.com> In-Reply-To: <479B9F4F.5010705@moneybookers.com> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1320325.ad8KbAYg12"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200801262227.36970.max@love2party.net> X-Provags-ID: V01U2FsdGVkX19bYdyLt4GLN4Pi8u0Zr7M0zZMDp92Qi6IlYe2 NTxCG86bEzghjfIGo+EAxgpqu1Q+ut5wiRcgJfYZI4E1Q+uSn6 qVBmH7c4eAd3l16iJYjtLZ3CC9kf4CR3bQqH8NwC9c= Cc: Stefan Lambrev Subject: Re: FreeBSD 7, bridge, PF and syn flood = very bad performance X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 21:27:40 -0000 --nextPart1320325.ad8KbAYg12 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 26 January 2008, Stefan Lambrev wrote: > Max Laier wrote: > > On Friday 25 January 2008, Stefan Lambrev wrote: > >> Greetings, > >> > >> Does anyone try to see PF with "keep state" in action when under syn > >> flood attack? > >> I tried to get some help in freebsd-pf@, because the test firewall, > >> that I build hardly can handle 2-5MB/s syn flood. > >> Unfortunately I do not saw useful advice. > >> The problem is that a quad core bridge firewall running freebsd 7 > >> amd64 with PF is near useless and can't handle "small" SYN ddos. > >> > >> Here is the schema that I'm testing: > >> web server (freebsd) - freebsd (bridged interfaces) - gigabit switch > >> - clients + flooders > >> In this configuration ~25MB/s syn flood (and I think this limit is > >> because of my switch) is not a problem and the web server responds > >> without a problem. > >> With this configuration netperf -l 610 -p 10303 -H 10.3.3.1 shows > >> 116MB/s stable speed , so I guess there are no problems with cables, > >> hardware and etc :) > >> > >> But when I start pf (see below the config file) the traffic drops to > >> 2-3MB/s and the web server is hardly accessible. > >> It seems that device polling helps a lot in this situation, and at > >> least the bridge firewall is accessible. Without "polling" the > >> firewall is so heavily loaded > >> that even commands like "date" take few seconds to finish, with 2 > >> cores at ~100% idle at same time. > >> > >> I have "flat profiles" from hwpmc, and I think it indicates a > >> problem: > >> > >> (bridge, pf enabled, polling enabled, sched_ule - I have profiles > >> and for other combinations too if needed) > >> % cumulative self self total > >> time seconds seconds calls ms/call ms/call name > >> 24.0 268416.00 268416.00 0 100.00% =20 > >> _mtx_lock_sleep > > > > Can you build a kernel with LOCK_PROFILING and try to figure out > > which lock is causing this? > > Yes I can build kernel with LOCK_PROFILING. > But I have no idea how to use it :) > Can you point me to some documentation? man LOCK_PROFILING basically: # sysctl debug.lock.prof.enable=3D1 && sleep 60 && \ sysctl debug.lock.prof.enable=3D0 && \ sysctl debug.lock.prof.stats > log while under attack to sample one minute of lock statistics. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1320325.ad8KbAYg12 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQBHm6XIXyyEoT62BG0RAvotAJ4jJFM0qpH91Y2ByEKyKTRmObD72QCfdniT PfTCHdbKTS0Kb/Bkwd5DXlM= =X5lq -----END PGP SIGNATURE----- --nextPart1320325.ad8KbAYg12-- From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 21:51:57 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7438816A417 for ; Sat, 26 Jan 2008 21:51:57 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.freebsd.org (Postfix) with ESMTP id 1FC9213C457 for ; Sat, 26 Jan 2008 21:51:56 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from thor.farley.org (thor.farley.org [192.168.1.5]) by mail.farley.org (8.14.1/8.14.1) with ESMTP id m0QLppfB048962 for ; Sat, 26 Jan 2008 15:51:51 -0600 (CST) (envelope-from scf@FreeBSD.org) Date: Sat, 26 Jan 2008 15:51:51 -0600 (CST) From: "Sean C. Farley" To: freebsd-current@FreeBSD.org Message-ID: User-Agent: Alpine 1.00 (BSF 882 2007-12-20) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on mail.farley.org Cc: Subject: [patch] '-d' option for pw to delete list of members from a group X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 21:51:57 -0000 Currently, pw allows the deletion of members of a group by replacing the current list with a new list ('-M' option). This requires a person or program to collect the list, remove members and send the new list to pw. The patch[1] I wrote adds the '-d' option to groupmod to allow the specific deletion of members from a group. It is a bit old but applies cleanly to HEAD and RELENG_7. This was written while working on BSDUpdates[2] some time ago. It has just taken me awhile to make the patch and find time to commit it. :) I hope to commit it soon if no one has any complaints. Sean 1. http://www.farley.org/freebsd/tmp/pw.patch 2. http://bsdupdates.com/ -- scf@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 21:55:58 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D1D316A41A; Sat, 26 Jan 2008 21:55:58 +0000 (UTC) (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 E612513C4E3; Sat, 26 Jan 2008 21:55:57 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m0QLtusg077775; Sat, 26 Jan 2008 16:55:56 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.14.2/8.14.1) with ESMTP id m0QLtuK4090141; Sat, 26 Jan 2008 16:55:56 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 6FFDE73039; Sat, 26 Jan 2008 16:55:56 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080126215556.6FFDE73039@freebsd-current.sentex.ca> Date: Sat, 26 Jan 2008 16:55:56 -0500 (EST) X-Virus-Scanned: ClamAV 0.92/5493/Thu Jan 17 13:09:26 2008 clamav-milter version 0.91.1 on clamscanner2 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on ia64/ia64 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: Sat, 26 Jan 2008 21:55:58 -0000 TB --- 2008-01-26 20:46:33 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-01-26 20:46:33 - starting HEAD tinderbox run for ia64/ia64 TB --- 2008-01-26 20:46:33 - cleaning the object tree TB --- 2008-01-26 20:47:10 - cvsupping the source tree TB --- 2008-01-26 20:47:10 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/ia64/ia64/supfile TB --- 2008-01-26 20:47:17 - building world (CFLAGS=-O -pipe) TB --- 2008-01-26 20:47:17 - cd /src TB --- 2008-01-26 20:47:17 - /usr/bin/make -B buildworld >>> World build started on Sat Jan 26 20:47:19 UTC 2008 >>> 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 [...] /src/usr.sbin/setfmac/setfmac.c: In function 'main': /src/usr.sbin/setfmac/setfmac.c:161: warning: field precision should have type 'int', but argument 3 has type 'size_t' /src/usr.sbin/setfmac/setfmac.c:166: warning: field precision should have type 'int', but argument 2 has type 'size_t' /src/usr.sbin/setfmac/setfmac.c:174: warning: field precision should have type 'int', but argument 3 has type 'size_t' /src/usr.sbin/setfmac/setfmac.c:178: warning: field precision should have type 'int', but argument 4 has type 'size_t' /src/usr.sbin/setfmac/setfmac.c: In function 'apply_specs': /src/usr.sbin/setfmac/setfmac.c:443: warning: field precision should have type 'int', but argument 2 has type 'size_t' /src/usr.sbin/setfmac/setfmac.c:487: warning: field precision should have type 'int', but argument 3 has type 'size_t' *** Error code 1 Stop in /src/usr.sbin/setfmac. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-01-26 21:55:56 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-01-26 21:55:56 - ERROR: failed to build world TB --- 2008-01-26 21:55:56 - tinderbox aborted TB --- 3179.26 user 336.26 system 4162.53 real http://tinderbox.des.no/tinderbox-head-HEAD-ia64-ia64.full From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 22:32:51 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D47C716A46D for ; Sat, 26 Jan 2008 22:32:51 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.freebsd.org (Postfix) with ESMTP id 8146713C46A for ; Sat, 26 Jan 2008 22:32:51 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by py-out-1112.google.com with SMTP id u52so1726126pyb.10 for ; Sat, 26 Jan 2008 14:32:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:x-enigmail-version:content-type:content-transfer-encoding; bh=Z+rF7ah/v9o6ecefAmJD3fr3PHru5ReWko/zSc8Tcfk=; b=hZSJsKt2GB2YFJBYr4zDC8+JIYdLTksHtLpZShVMwyS/jwFVnVd9JoMQwN7rd6uVXrUjBhNEzjJYFH8xS3CcO0Ou2y34lXHHT0Qf0ehx6junKySKLhzqNkAtuBESumR/596lR61ZzvFS5b2w/PnysrFJma6oSse6IdE6QnUDY1o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:x-enigmail-version:content-type:content-transfer-encoding; b=sDutl+gpkYKbLGR5PdaTZyhNnq9oLKRpgDYGE5m9JQfrCTrl1aiuT+VFYygdexyFCE/DA82uEU9IlN/9S4Rj1N803SnJG8fUKiPRsDK4Yn5GnCKfuo4FfrbnOhq0Hi/y6mjptbrMi+qItK/SEclWIOFTfQvwnxawNfZJmq0ugtY= Received: by 10.65.95.12 with SMTP id x12mr7748571qbl.71.1201386769657; Sat, 26 Jan 2008 14:32:49 -0800 (PST) Received: from flosoft.no-ip.biz ( [67.85.89.184]) by mx.google.com with ESMTPS id d12sm3222404qbc.3.2008.01.26.14.32.48 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 26 Jan 2008 14:32:49 -0800 (PST) Message-ID: <479BB50E.2080703@gmail.com> Date: Sat, 26 Jan 2008 17:32:46 -0500 From: "Aryeh M. Friedman" User-Agent: Thunderbird 2.0.0.9 (X11/20080121) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: build/installworld break under -j n for n>1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jan 2008 22:32:51 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Installworld fails to wait for buildworld to complete under the following command line: make -j n buildworld installworld I have not tested for n!=10. - -- Aryeh M. Friedman FloSoft Systems, Java Tool Developers Developer, not business, friendly http://www.flosoft-systems.com "Free software != Free beer" Blog: http://www.flosoft-systems.com/flosoft_systems_community/blogs/aryeh/index.php -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHm7UOQi2hk2LEXBARAstMAJ4uZsNUeSUwm5Jal6POPG905PkXYwCg7uGz qOSKkk3dBDJgT+NCKsTOJEQ= =FobF -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 22:54:24 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C50C716A420; Sat, 26 Jan 2008 22:54:24 +0000 (UTC) (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 716B113C459; Sat, 26 Jan 2008 22:54:24 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m0QMsNGL084771; Sat, 26 Jan 2008 17:54:23 -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.14.2/8.14.1) with ESMTP id m0QMsN8R082575; Sat, 26 Jan 2008 17:54:23 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id A05DA73039; Sat, 26 Jan 2008 17:54:23 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080126225423.A05DA73039@freebsd-current.sentex.ca> Date: Sat, 26 Jan 2008 17:54:23 -0500 (EST) X-Virus-Scanned: ClamAV 0.92/5493/Thu Jan 17 13:09:26 2008 clamav-milter version 0.91.2 on clamscanner3 X-Virus-Status: Clean 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: Sat, 26 Jan 2008 22:54:24 -0000 TB --- 2008-01-26 21:55:56 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-01-26 21:55:56 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2008-01-26 21:55:56 - cleaning the object tree TB --- 2008-01-26 21:56:16 - cvsupping the source tree TB --- 2008-01-26 21:56:16 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2008-01-26 21:56:24 - building world (CFLAGS=-O -pipe) TB --- 2008-01-26 21:56:24 - cd /src TB --- 2008-01-26 21:56:24 - /usr/bin/make -B buildworld >>> World build started on Sat Jan 26 21:56:26 UTC 2008 >>> 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 [...] /src/usr.sbin/setfmac/setfmac.c: In function 'main': /src/usr.sbin/setfmac/setfmac.c:161: warning: field precision should have type 'int', but argument 3 has type 'size_t' /src/usr.sbin/setfmac/setfmac.c:166: warning: field precision should have type 'int', but argument 2 has type 'size_t' /src/usr.sbin/setfmac/setfmac.c:174: warning: field precision should have type 'int', but argument 3 has type 'size_t' /src/usr.sbin/setfmac/setfmac.c:178: warning: field precision should have type 'int', but argument 4 has type 'size_t' /src/usr.sbin/setfmac/setfmac.c: In function 'apply_specs': /src/usr.sbin/setfmac/setfmac.c:443: warning: field precision should have type 'int', but argument 2 has type 'size_t' /src/usr.sbin/setfmac/setfmac.c:487: warning: field precision should have type 'int', but argument 3 has type 'size_t' *** Error code 1 Stop in /src/usr.sbin/setfmac. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-01-26 22:54:23 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-01-26 22:54:23 - ERROR: failed to build world TB --- 2008-01-26 22:54:23 - tinderbox aborted TB --- 2598.09 user 315.55 system 3506.80 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sparc64.full From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 23:09:33 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6AE516A417 for ; Sat, 26 Jan 2008 23:09:33 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with SMTP id 6DD2513C455 for ; Sat, 26 Jan 2008 23:09:33 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 24769 invoked by uid 399); 26 Jan 2008 23:09:32 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTP; 26 Jan 2008 23:09:32 -0000 X-Originating-IP: 127.0.0.1 Message-ID: <479BBDAA.6000008@FreeBSD.org> Date: Sat, 26 Jan 2008 15:09:30 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.9 (X11/20071119) MIME-Version: 1.0 To: Attilio Rao References: <790a9fff0801150552l542a4238ofc12efe5fdb45fc2@mail.gmail.com> <20080115143924.GB57756@deviant.kiev.zoral.com.ua> <20080124122808.GA15600@freefall.freebsd.org> <3bbf2fe10801240518i6e18b2f5w84de652d4170c95b@mail.gmail.com> <20080124145811.GB78114@comp.chem.msu.su> <3bbf2fe10801240707o72b927cg74dbf9b7bbcd88fc@mail.gmail.com> <20080125075551.GB21633@comp.chem.msu.su> <3bbf2fe10801250000k5852c2f2j5d1897c900096818@mail.gmail.com> <20080126142901.GD49535@comp.chem.msu.su> <479B6303.6000401@FreeBSD.org> <3bbf2fe10801260918k56c1a73hf28ff154eca0b74c@mail.gmail.com> In-Reply-To: <3bbf2fe10801260918k56c1a73hf28ff154eca0b74c@mail.gmail.com> X-Enigmail-Version: 0.95.5 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Kostik Belousov , Yar Tikhiy , freebsd-current@freebsd.org Subject: Re: panic: System call lstat returning with 1 locks held X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 23:09:33 -0000 Attilio Rao wrote: > 2008/1/26, Doug Barton : >> Yar Tikhiy wrote: >> >>> No doubt. :-) But the urgency of this problem appears much lower >>> than that I estimated in the first place--fortunately. Broken UFS >>> would be a nightmare. >> IMO if we're going to ship NTFS support in the base it should actually >> function, or at minimum not panic the box. As I reported earlier, I can >> panic my -current system with 100% reliability with fairly light access >> to an NTFS volume, which I consider to be a fairly large problem, at >> least for my personal usage pattern. > > I'm not sure now, are you referring to some problems introduced by my > patches or not? Not sure of the timeline. I think this is the most relevant post on the matter, let me know if there is anything I can do to help diagnose this. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=644445+0+archive/2008/freebsd-current/20080113.freebsd-current -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 23:11:00 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 512A916A4DC; Sat, 26 Jan 2008 23:11:00 +0000 (UTC) (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 EABF813C4D1; Sat, 26 Jan 2008 23:10:59 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m0QNAxAN086566; Sat, 26 Jan 2008 18:10: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.14.2/8.14.1) with ESMTP id m0QNAxMA097679; Sat, 26 Jan 2008 18:10:59 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 04E1473039; Sat, 26 Jan 2008 18:10:59 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080126231059.04E1473039@freebsd-current.sentex.ca> Date: Sat, 26 Jan 2008 18:10:59 -0500 (EST) X-Virus-Scanned: ClamAV 0.92/5493/Thu Jan 17 13:09:26 2008 clamav-milter version 0.91.2 on clamscanner2 X-Virus-Status: Clean Cc: Subject: [head tinderbox] failure on sparc64/sun4v 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: Sat, 26 Jan 2008 23:11:00 -0000 TB --- 2008-01-26 22:15:14 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-01-26 22:15:14 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2008-01-26 22:15:14 - cleaning the object tree TB --- 2008-01-26 22:15:46 - cvsupping the source tree TB --- 2008-01-26 22:15:46 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2008-01-26 22:15:52 - building world (CFLAGS=-O -pipe) TB --- 2008-01-26 22:15:52 - cd /src TB --- 2008-01-26 22:15:52 - /usr/bin/make -B buildworld >>> World build started on Sat Jan 26 22:15:54 UTC 2008 >>> 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 [...] /src/usr.sbin/setfmac/setfmac.c: In function 'main': /src/usr.sbin/setfmac/setfmac.c:161: warning: field precision should have type 'int', but argument 3 has type 'size_t' /src/usr.sbin/setfmac/setfmac.c:166: warning: field precision should have type 'int', but argument 2 has type 'size_t' /src/usr.sbin/setfmac/setfmac.c:174: warning: field precision should have type 'int', but argument 3 has type 'size_t' /src/usr.sbin/setfmac/setfmac.c:178: warning: field precision should have type 'int', but argument 4 has type 'size_t' /src/usr.sbin/setfmac/setfmac.c: In function 'apply_specs': /src/usr.sbin/setfmac/setfmac.c:443: warning: field precision should have type 'int', but argument 2 has type 'size_t' /src/usr.sbin/setfmac/setfmac.c:487: warning: field precision should have type 'int', but argument 3 has type 'size_t' *** Error code 1 Stop in /src/usr.sbin/setfmac. *** Error code 1 Stop in /src/usr.sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-01-26 23:10:58 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-01-26 23:10:58 - ERROR: failed to build world TB --- 2008-01-26 23:10:58 - tinderbox aborted TB --- 2590.72 user 313.46 system 3344.22 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sun4v.full From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 23:02:50 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2547616A480; Sat, 26 Jan 2008 23:02:50 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46]) by mx1.freebsd.org (Postfix) with ESMTP id 0497313C45D; Sat, 26 Jan 2008 23:02:49 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 829B68C0AC; Sat, 26 Jan 2008 17:02:49 -0600 (CST) Date: Sat, 26 Jan 2008 17:02:49 -0600 To: Doug Barton Message-ID: <20080126230249.GA5183@soaustin.net> References: <790a9fff0801150552l542a4238ofc12efe5fdb45fc2@mail.gmail.com> <20080115143924.GB57756@deviant.kiev.zoral.com.ua> <20080124122808.GA15600@freefall.freebsd.org> <3bbf2fe10801240518i6e18b2f5w84de652d4170c95b@mail.gmail.com> <20080124145811.GB78114@comp.chem.msu.su> <3bbf2fe10801240707o72b927cg74dbf9b7bbcd88fc@mail.gmail.com> <20080125075551.GB21633@comp.chem.msu.su> <3bbf2fe10801250000k5852c2f2j5d1897c900096818@mail.gmail.com> <20080126142901.GD49535@comp.chem.msu.su> <479B6303.6000401@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <479B6303.6000401@FreeBSD.org> User-Agent: Mutt/1.5.13 (2006-08-11) From: linimon@lonesome.com (Mark Linimon) X-Mailman-Approved-At: Sat, 26 Jan 2008 23:44:55 +0000 Cc: Attilio Rao , Yar Tikhiy , Kostik Belousov , freebsd-current@freebsd.org Subject: Re: panic: System call lstat returning with 1 locks held X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 23:02:50 -0000 On Sat, Jan 26, 2008 at 08:42:43AM -0800, Doug Barton wrote: > IMO if we're going to ship NTFS support in the base it should actually > function, or at minimum not panic the box. This is a symptom of a general problem, "things that we doubt work very well". What's your suggestion on how we can flag these? The traditional argument is that if we don't ship code in the base, it will never get tested. IMHO it would a big change to turn off everything that isn't 100% solid. I'm open to suggestions. mcl From owner-freebsd-current@FreeBSD.ORG Sat Jan 26 23:06:04 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5897316A418 for ; Sat, 26 Jan 2008 23:06:04 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.178]) by mx1.freebsd.org (Postfix) with ESMTP id 2F33213C46A for ; Sat, 26 Jan 2008 23:06:03 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so2012587waf.3 for ; Sat, 26 Jan 2008 15:06:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=vH0bb8jGJaPnhA4pAjoTJ+VvNsYzAN+XwcQ1OjObGh0=; b=qRaYzwoHliNpogiZXcJwjkGzFrW3qom359TMHt6NNfaJu9l5YatuzYgablA/+uR2ao05gqPuL+KrPobCjkW/htkkWlLk95MBPPQSeccO/koA0m4liII3CpKaL2aEbyu3SSLzWsA/QvtH8AIi7ehiJo3qXw/TIpxVCb43o+BtbX0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Q3LzSjtosXpaRAvtQqKNgIpdiPeXeIVpQFWvBfAzP747YReR2x+F5W5VciJMqd58yeDZjf8bwpN/M65RMUCNhqWmcEIWntKPgZiB3FJnDlpfuGFdRXAGDCI1E86Wqbf2CAPCldHlc4FnePYH3MG6r4I4Q71GX8e3ZRo7CHrRk+E= Received: by 10.114.194.1 with SMTP id r1mr1377037waf.40.1201388763393; Sat, 26 Jan 2008 15:06:03 -0800 (PST) Received: by 10.115.16.7 with HTTP; Sat, 26 Jan 2008 15:06:03 -0800 (PST) Message-ID: <4956a5e50801261506x1761f175sa08e1e11b01f3fe8@mail.gmail.com> Date: Sat, 26 Jan 2008 20:06:03 -0300 From: Nenhum_de_Nos To: "Bjoern A. Zeeb" In-Reply-To: <20080126153015.U36482@maildrop.int.zabbadoz.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <012101c85cbe$3d93fef0$292d280a@friedman.net> <4795B6ED.8020902@beardz.net> <003901c85d02$96a78d60$292d280a@friedman.net> <4956a5e50801242019m37675b90t7fbbb72d4d917960@mail.gmail.com> <4956a5e50801242020j41fea759v84720c62a246db63@mail.gmail.com> <20080126153015.U36482@maildrop.int.zabbadoz.net> X-Mailman-Approved-At: Sat, 26 Jan 2008 23:45:08 +0000 Cc: "George V. Neville-Neil" , freebsd-current@freebsd.org Subject: Re: IPSEC on 7.0-PRERELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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 Jan 2008 23:06:04 -0000 On Jan 26, 2008 12:33 PM, Bjoern A. Zeeb wrote: > I think I updated all the man pages I was aware of. > > I am not going to comment on the handbook. I think we should rather > remove that section, if noone has updated it (since FreeBSD 4;) and > maybe bring it back at a later time. I do agree that it is outdated, but it helped me though. it is based on ipsec-tools, more specific the racoon package, even though racoon2 is out there. If I may say anything, keep it. is good reference. just would make the needed changes to work on ipsec-tools and racoon 1. (after reading it a couple of times I coudn't make it work as I never guessed there was a need to run /etc/rc.d/ipsec start. and the racoon examples are not on the places they say, but I do think it is all minor changes.) (I did sent a mail to doc@ for this) as I went through this guide recently, I could help to renew it. I just know nothing specific about racoon 2, but in refreshing that as it could run ok on 6.3R and 7.0R I can help :) George, to whom I should say this ? (as I read above, I think you are the guy :) just need to say what is needed :) matheus -- We will call you cygnus, The God of balance you shall be