From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 4 00:41:32 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCA3716A41F; Sun, 4 Dec 2005 00:41:32 +0000 (GMT) (envelope-from craig@tobuj.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A60843D5F; Sun, 4 Dec 2005 00:41:32 +0000 (GMT) (envelope-from craig@tobuj.gank.org) Received: by ion.gank.org (mail, from userid 1001) id 008EC2BBBE; Sat, 3 Dec 2005 18:41:31 -0600 (CST) Date: Sat, 3 Dec 2005 18:41:31 -0600 From: Craig Boston To: John Baldwin Message-ID: <20051204004131.GA7596@nowhere> References: <20051130020734.GA6577@nowhere> <200512020817.55769.jhb@freebsd.org> <20051203005104.GA22567@nowhere> <200512031630.59476.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200512031630.59476.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org, imp@freebsd.org Subject: Re: Weird PCI interrupt delivery problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 00:41:33 -0000 On Sat, Dec 03, 2005 at 04:30:58PM -0500, John Baldwin wrote: > That's becuase the dmesg prints out what their current setting was before the > pci_link driver attached to them. It's basically what the BIOS set them up > as. Ah, makes sense. > Grrr. I'm pretty much out of ideas at this point. Yeah, it's pretty frustrating... Then again I knew when I got this machine what I might be getting myself into. Thanks for taking the time to help work on this and provide some ideas. I'll keep hacking on it and follow up here if I figure anything out. > At least you have it working in -ACPI -APIC mode. :-/ Unfortunately it seems that it's actually still broken in this case. I just discovered that even with the hint, the cardbus controller / devices don't generate any interrupts at all. The only reason it seemed to be working is that when I have the radio enabled, ath0 generates about 1000 interrupts/second (which seems high, but that's another discussion). So effectively is was just running in polling mode. I didn't notice that until this morning when I booted into single user mode and was trying to use some cardbus cards before ath0 was configured. Random tangent, it's kind of sad that one of the co-authors of the ACPI spec (Toshiba) would sell a machine that has so many problems with it. Though I think ATI deserves at least part of the blame as this appears to use one of their "system-on-a-chip" designs. Craig From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 4 01:40:28 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F7BA16A41F for ; Sun, 4 Dec 2005 01:40:28 +0000 (GMT) (envelope-from craig@tobuj.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5695443D55 for ; Sun, 4 Dec 2005 01:40:28 +0000 (GMT) (envelope-from craig@tobuj.gank.org) Received: by ion.gank.org (mail, from userid 1001) id 290CB2BBBE; Sat, 3 Dec 2005 19:40:28 -0600 (CST) Date: Sat, 3 Dec 2005 19:40:28 -0600 From: Craig Boston To: freebsd-hackers@freebsd.org Message-ID: <20051204014028.GB92337@nowhere> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Re: Weird PCI interrupt delivery problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 01:40:28 -0000 Sam, I hope you're reading -hackers, it seems errno.com is rejecting my mail again... Forward and reverse DNS looks OK, and I always send from the address published in my SPF records; not sure why it doesn't like me. Final-Recipient: rfc822; sam@errno.com Action: failed Status: 5.0.0 Diagnostic-Code: X-mail; host mail.dcc-servers.net[204.152.184.184] said: 550 5.7.1 mail jB41YEJt015277 from 69.55.238.164 rejected by DCC (in reply to end of DATA command) Date: Sat, 3 Dec 2005 19:34:12 -0600 From: Craig Boston To: Sam Leffler Subject: Re: Weird PCI interrupt delivery problem On Sat, Dec 03, 2005 at 04:48:20PM -0800, Sam Leffler wrote: > Yes that is too high. Run athstats 1 to see what the interrupts are > for. dmesg|grep ath to identify the part might also help explain things. Haven't been too worried about it yet, just counting my blessings that the "Built-in 802.11g" turned out to be a working Atheros card. Here's the info: ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413) ath0: mem 0xd0200000-0xd020ffff irq 11 at device 4.0 on pci9 ath0: Ethernet address: 00:11:f5:89:75:d4 ath0: mac 7.8 phy 4.5 radio 5.6 # ./athstats 1 input output altrate short long xretry crcerr crypt phyerr rssi rate 5 7 1 0 140 11 32394 0 91648 31 54M 0 0 0 0 0 0 207 0 969 31 54M 0 0 0 0 0 0 684 0 523 31 54M 0 0 0 0 0 0 401 0 859 31 54M 0 0 0 0 0 0 476 0 708 31 54M 0 0 0 0 0 0 389 0 841 30 54M 0 0 0 0 0 0 312 0 890 31 54M 0 0 0 0 0 0 751 0 525 31 54M 0 0 0 0 0 0 497 0 757 31 54M 0 0 0 0 0 0 248 0 946 31 54M 0 0 0 0 0 0 864 0 482 31 54M 0 0 0 0 0 0 714 0 579 31 54M 0 0 0 0 0 0 391 0 861 31 54M 0 0 0 0 0 0 373 0 886 31 54M 0 0 0 0 0 0 221 0 1077 31 54M 0 0 0 0 0 0 736 0 530 31 54M 0 0 0 0 0 0 554 0 666 31 54M 0 0 0 0 0 0 432 0 879 31 54M 0 0 0 0 0 0 220 0 1070 28 54M ----- End forwarded message ----- From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 4 10:23:26 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9E55916A41F for ; Sun, 4 Dec 2005 10:23:26 +0000 (GMT) (envelope-from itzike@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3170C43D4C for ; Sun, 4 Dec 2005 10:23:26 +0000 (GMT) (envelope-from itzike@gmail.com) Received: by wproxy.gmail.com with SMTP id i12so965464wra for ; Sun, 04 Dec 2005 02:23:25 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=iGmz79j/d9CHSpHYgwrJCTPXa5TS1LdNyXkrGShx/3B+x2poJrZsgMG61UTO+F2lA+YTzSbAzcV4wWGBClGBwJe9Gl3DTIbE7jPARAkll+pgSmzjVabAhdw4q5xz2EX9cqPWk6ElwialRIljOzC3YeDKh2G7sFTrKQxIYBLdDVg= Received: by 10.65.126.16 with SMTP id d16mr1658156qbn; Sun, 04 Dec 2005 02:23:25 -0800 (PST) Received: by 10.65.244.3 with HTTP; Sun, 4 Dec 2005 02:23:25 -0800 (PST) Message-ID: <626139650512040223h5b84072k174c7488667fc833@mail.gmail.com> Date: Sun, 4 Dec 2005 12:23:25 +0200 From: Izik Eidus To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: (no subject) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 10:23:26 -0000 itzike@gmail.com From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 4 14:27:49 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0D1016A41F for ; Sun, 4 Dec 2005 14:27:49 +0000 (GMT) (envelope-from gizmen@blurp.t2.ds.pwr.wroc.pl) Received: from blurp.t2.ds.pwr.wroc.pl (blurp.t2.ds.pwr.wroc.pl [156.17.224.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27C6843D49 for ; Sun, 4 Dec 2005 14:27:48 +0000 (GMT) (envelope-from gizmen@blurp.t2.ds.pwr.wroc.pl) Received: by blurp.t2.ds.pwr.wroc.pl (Postfix, from userid 1001) id E59A6723; Sun, 4 Dec 2005 15:27:44 +0100 (CET) Date: Sun, 4 Dec 2005 15:27:44 +0100 From: GiZmen To: hackers@freebsd.org Message-ID: <20051204142744.GA53154@blurp.pl> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="d6Gm4EdcadzBjdND" Content-Disposition: inline User-Agent: Mutt/1.5.11 Cc: Subject: clock interrupts eating whole cpu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 14:27:49 -0000 --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, yesterday i have noticed that my cpu is runnig on 100%. And almost 100% is used on interrupts CPU states: 0.0% user, 0.0% nice, 1.4% system, 98.6% interrupt, 0.0% idle i tried to check what is going on. I ran top and pressed S so i could see all processes: PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND 27 root 1 -32 -151 0K 8K RUN 62:48 67.72% swi4: clock 29 root 1 -44 -163 0K 8K RUN 28:30 28.17% swi1: net 11 root 1 171 52 0K 8K RUN 1:03 1.12% idle I have noticed that clock is eating most free cpu time. Net load is in normal because this is router for about 150 hosts. Could any one tell me what is going on? I am running FreeBSD 6.0-STABLE. i didnt have any problems like that before with FreeBSD 6.0-BETA ,RC,RELEASE and even STABLE. This happend yesterday or dwo days ago. I have downloaded newest src from cvsup and recompiled kernel which took quite long time due cpu usage. System is runnig postfix,mysql,apache2,dhcpd. I have attached my kernel config. I dont know where to look for problem. Please help me with this. -- Best Regards: GiZmen UNIX is user-friendly; it's just picky about its friends UNIX is simple; it just takes a genius to understand its simplicity --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=BLURP machine i386 cpu I686_CPU ident BLURP makeoptions COPTFLAGS="-O2 -pipe -funroll-loops -ffast-math -fno-builtin" makeoptions CONF_CFLAGS="-O2 -pipe -funroll-loops -ffast-math -fno-builtin" #makeoptions DEBUG=-g options SCHED_4BSD #options SCHED_ULE # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories #options MD_ROOT # MD is a potential root device #options NFSCLIENT # Network Filesystem Client #options NFSSERVER # Network Filesystem Server #options NFS_ROOT # NFS usable as /, requires NFSCLIENT #options MSDOSFS # MSDOS Filesystem #options CD9660 # ISO 9660 Filesystem #options PROCFS # Process filesystem (requires PSEUDOFS) #options PSEUDOFS # Pseudo-filesystem framework options NULLFS options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 #options SCSI_DELAY=15000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores #options SHMMAXPGS=4096 #options SHMSEG=256 #options SEMMNI=256 #options SEMMNS=512 #options SEMMNU=256 #options SEMMAP=256 options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev #options AHC_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~128k to driver. #options AHD_REG_PRETTY_PRINT # Print register bitfields in debug # output. Adds ~215k to driver. options ADAPTIVE_GIANT # Giant mutex is adaptive. #device apic # I/O APIC # Bus support. Do not remove isa, even if you have no isa slots device isa device pci # Floppy drives #device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives #device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID # Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device sc #device agp # support several AGP chipsets device npx # Add suspend/resume support for the i8254. device pmtimer #options CPU_ENABLE_TCC #options VESA options GEOM_BDE # Disk encryption. options ALTQ #options ALTQ_CBQ # Class Bases Queueing options ALTQ_RED # Random Early Drop #options ALTQ_RIO # RED In/Out options ALTQ_HFSC # Hierarchical Packet Scheduler #options ALTQ_CDNR # Traffic conditioner #options ALTQ_PRIQ # Priority Queueing device pf #PF OpenBSD packet-filter firewall device pflog #logging support interface for PF device pfsync #synchronization interface for PF options IPSTEALTH #support for stealth forwarding options ACCEPT_FILTER_DATA options ACCEPT_FILTER_HTTP options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN options BRIDGE options ZERO_COPY_SOCKETS options QUOTA #enable disk quotas options MAXCONS=5 options MAC options SC_HISTORY_SIZE=5000 #options SC_DISABLE_DDBKEY #options SC_DISABLE_REBOOT #options SC_TWOBUTTON_MOUSE #options CPU_SUSP_HLT #options MAC_BIBA #options MAC_BSDEXTENDED options HZ=1000 #device sound #options INCLUDE_CONFIG_FILE # Include this file in kernel #options HW_WDOG #options SW_WATCHDOG options DEVICE_POLLING options CPU_ATHLON_SSE_HACK #options NETGRAPH #options KDB #options KDB_TRACE #options KDB_UNATTENDED #options DDB #options INVARIANTS #options INVARIANT_SUPPORT #options DIAGNOSTIC #options WITNESS #options CD9660_ICONV #options MSDOSFS_ICONV #options NTFS_ICONV #options UDF_ICONV device miibus # MII bus support #device re # RealTek 8139C+/8169/8169S/8110S device rl # RealTek 8129/8139 #device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards device fxp device xl # Pseudo devices. device loop # Network loopback device mem # Memory and kernel memory devices device io # I/O device device random # Entropy device device ether # Ethernet support #device sl # Kernel SLIP #device ppp # Kernel PPP #device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) device snp #Snoop device - to look at pty/vty/etc.. device bpf # Berkeley packet filter --d6Gm4EdcadzBjdND-- From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 4 16:59:44 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 38D6816A41F for ; Sun, 4 Dec 2005 16:59:44 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from pinus.cc.fer.hr (pinus.cc.fer.hr [161.53.73.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FC8143D5C for ; Sun, 4 Dec 2005 16:59:43 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [161.53.72.113] (lara.cc.fer.hr [161.53.72.113]) by pinus.cc.fer.hr (8.12.2/8.12.2) with ESMTP id jB4GxMFx004890; Sun, 4 Dec 2005 17:59:30 +0100 (MET) Message-ID: <43932040.8040207@fer.hr> Date: Sun, 04 Dec 2005 17:58:40 +0100 From: Ivan Voras User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050921) X-Accept-Language: en-us, en MIME-Version: 1.0 To: GiZmen References: <20051204142744.GA53154@blurp.pl> In-Reply-To: <20051204142744.GA53154@blurp.pl> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: clock interrupts eating whole cpu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 16:59:44 -0000 GiZmen wrote: > Hi, > > yesterday i have noticed that my cpu is runnig on 100%. > And almost 100% is used on interrupts > > PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND > 27 root 1 -32 -151 0K 8K RUN 62:48 67.72% swi4: clock Verify you don't have a console screen-saver configured, especially a graphical one - it happened to me several times. From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 4 17:50:33 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BC0A16A422 for ; Sun, 4 Dec 2005 17:50:33 +0000 (GMT) (envelope-from gizmen@blurp.t2.ds.pwr.wroc.pl) Received: from blurp.t2.ds.pwr.wroc.pl (blurp.t2.ds.pwr.wroc.pl [156.17.224.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA58643D91 for ; Sun, 4 Dec 2005 17:50:19 +0000 (GMT) (envelope-from gizmen@blurp.t2.ds.pwr.wroc.pl) Received: by blurp.t2.ds.pwr.wroc.pl (Postfix, from userid 1001) id 4D4BB723; Sun, 4 Dec 2005 18:50:13 +0100 (CET) Date: Sun, 4 Dec 2005 18:50:13 +0100 From: GiZmen To: hackers@freebsd.org Message-ID: <20051204175013.GA53785@blurp.pl> References: <20051204142744.GA53154@blurp.pl> <43932040.8040207@fer.hr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43932040.8040207@fer.hr> User-Agent: Mutt/1.5.11 Cc: Subject: Re: clock interrupts eating whole cpu X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 17:50:33 -0000 > >yesterday i have noticed that my cpu is runnig on 100%. > >And almost 100% is used on interrupts > > > > > PID USERNAME THR PRI NICE SIZE RES STATE TIME WCPU COMMAND > > 27 root 1 -32 -151 0K 8K RUN 62:48 67.72% swi4: clock > > Verify you don't have a console screen-saver configured, especially a > graphical one - it happened to me several times. No i don't have screen saver on my box. From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 4 22:34:31 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71B7116A41F for ; Sun, 4 Dec 2005 22:34:31 +0000 (GMT) (envelope-from aanton@spintech.ro) Received: from smtpx.spintech.ro (smtpx.spintech.ro [81.180.92.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D2BC43D66 for ; Sun, 4 Dec 2005 22:34:28 +0000 (GMT) (envelope-from aanton@spintech.ro) Received: from laura-axiomeda (unknown [11.0.0.25]) by smtpx.spintech.ro (Postfix) with ESMTP id 199E83A4B8 for ; Sun, 4 Dec 2005 22:42:15 +0000 (UTC) X-Laura: version 0.0.1b10-frustratus proxied X-Laura-Remote-IP: 10.0.0.2 Received: from [10.0.0.2] (beastie [10.0.0.2]) by smtpx.spintech.ro (Postfix) with ESMTP id 819E53A4AC for ; Sun, 4 Dec 2005 22:42:14 +0000 (UTC) Message-ID: <43936EEE.80309@spintech.ro> Date: Mon, 05 Dec 2005 00:34:22 +0200 From: Alin-Adrian Anton Organization: Spintech Security Systems User-Agent: Mozilla Thunderbird 1.0 (X11/20041229) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <438F00D8.4040302@spintech.ro> <79722fad0512010559n29e957f5j47c99586ebbd3a0f@mail.gmail.com> <20051201150949.W56270@fledge.watson.org> <4390F425.5060600@spintech.ro> In-Reply-To: <4390F425.5060600@spintech.ro> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: cwnd and sstresh monitor X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: aanton@spintech.ro List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 22:34:31 -0000 Alin-Adrian Anton wrote: > > I used it now, and with a small patch it shows exactly what I need (seq, > ack, timestamp, cwnd and ssthresh). I just added my knob to trpt.c . > > I also modified the iptime() function to provide microsecond resolution > instead of miliseconds, because most of the packets have the same > timestamp attached. Still, a decent number of packets have the same > timestamp. I'm looking at them only on one side of the connection (the > transmitter), I wonder if there is any better solution then timestamping > them on both sides - and mixing the values. > > Thanks guys for the precious information, it helped a lot! > Actually the method above had issues, packets not being logged in the debug buffer (which is limited and gets discarded quickly). Using trpt -f did solve this problem, at the cost of duplicate entries. So what finally did the job was a small "patch" of tcp_debug.c to print on console and print only what is needed (FreeBSD 6.0 won't allow "options TCPCONSDEBUG"), and /var/log/messages was parsed to extract the values. Cheers, -- Alin-Adrian Anton GPG keyID 0x183087BA (B129 E8F4 7B34 15A9 0785 2F7C 5823 ABA0 1830 87BA) gpg --keyserver pgp.mit.edu --recv-keys 0x183087BA "It is dangerous to be right when the government is wrong." - Voltaire From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 4 23:42:24 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BDC7116A41F for ; Sun, 4 Dec 2005 23:42:24 +0000 (GMT) (envelope-from gizmen@blurp.t2.ds.pwr.wroc.pl) Received: from blurp.t2.ds.pwr.wroc.pl (blurp.t2.ds.pwr.wroc.pl [156.17.224.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 662B743D45 for ; Sun, 4 Dec 2005 23:42:24 +0000 (GMT) (envelope-from gizmen@blurp.t2.ds.pwr.wroc.pl) Received: by blurp.t2.ds.pwr.wroc.pl (Postfix, from userid 1001) id B6D2C706; Mon, 5 Dec 2005 00:42:19 +0100 (CET) Date: Mon, 5 Dec 2005 00:42:19 +0100 From: GiZmen To: hackers@freebsd.org Message-ID: <20051204234219.GA55059@blurp.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.11 Cc: Subject: clock interrupts eating whole cpu [solved] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 23:42:24 -0000 Hi, I have spent whole day to track what is wrong with this interrupts. I found that altq is the problem. When i turn on pf only with rules my box behaves normally. When i turned on altq rules in one second my whole cpu was used. what was strange that i didn't change rules in some significant way. I checked them and i found that i left one rule like this pass all on pfsync0 i have added this rule when i was messing with pfsync iface. I forgot to remove it. When i removed this rule everything come back to normal state. This quite strange that this rule can cause such big mess on system. Is it some kind of bug ?? -- Best Regards: GiZmen UNIX is user-friendly; it's just picky about its friends UNIX is simple; it just takes a genius to understand its simplicity From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 5 04:24:22 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2E6616A41F for ; Mon, 5 Dec 2005 04:24:22 +0000 (GMT) (envelope-from saggarwa@cs.utah.edu) Received: from mail-svr1.cs.utah.edu (mail-svr1.cs.utah.edu [155.98.64.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5559143D5A for ; Mon, 5 Dec 2005 04:24:22 +0000 (GMT) (envelope-from saggarwa@cs.utah.edu) Received: from localhost (localhost [127.0.0.1]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id C526E346ED for ; Sun, 4 Dec 2005 21:24:20 -0700 (MST) Received: from mail-svr1.cs.utah.edu ([127.0.0.1]) by localhost (mail-svr1.cs.utah.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20256-04 for ; Sun, 4 Dec 2005 21:24:20 -0700 (MST) Received: from antitrust.cs.utah.edu (antitrust.cs.utah.edu [155.98.65.29]) by mail-svr1.cs.utah.edu (Postfix) with ESMTP id 64C69346DE for ; Sun, 4 Dec 2005 21:24:20 -0700 (MST) Received: by antitrust.cs.utah.edu (Postfix, from userid 4973) id 426F1108E41; Sun, 4 Dec 2005 21:24:20 -0700 (MST) Received: from localhost (localhost [127.0.0.1]) by antitrust.cs.utah.edu (Postfix) with ESMTP id 34468108E40 for ; Sun, 4 Dec 2005 21:24:20 -0700 (MST) Date: Sun, 4 Dec 2005 21:24:20 -0700 (MST) From: Siddharth Aggarwal To: freebsd-hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: amavisd-new at cs.utah.edu Subject: freeing disk block in 4.x kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 04:24:22 -0000 Hi, I am trying to find out where in the kernel code blocks on disk are freed. I want to track all the blocks freed on the disk as a result of file deletes etc., in my pseudo disk driver. Is there an equivalent of a blockfree() or something in the 4.x kernel code, where I can put a hook into my driver? Thanks, Sid. From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 4 23:00:07 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AAD9C16A41F for ; Sun, 4 Dec 2005 23:00:07 +0000 (GMT) (envelope-from tlang@csu.edu.au) Received: from csunb.mit.csu.edu.au (csunb.csu.edu.au [137.166.4.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68FFF43D62 for ; Sun, 4 Dec 2005 23:00:04 +0000 (GMT) (envelope-from tlang@csu.edu.au) Received: from ESBA01.CSUMain.csu.edu.au (ESBA01.CSUMain.csu.edu.au [137.166.5.27]) by csunb.mit.csu.edu.au (8.12.11/8.12.11) with ESMTP id jB4MxkJA017866 for ; Mon, 5 Dec 2005 10:00:00 +1100 (EST) Received: from ESWW02.CSUMain.csu.edu.au ([137.166.69.126]) by ESBA01.CSUMain.csu.edu.au with Microsoft SMTPSVC(6.0.3790.1830); Mon, 5 Dec 2005 09:59:59 +1100 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Mon, 5 Dec 2005 09:59:58 +1100 Message-ID: <0C7AF4692D7A6143A72AD00E5681D7E5ADA454@ESWW02.CSUMain.csu.edu.au> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: noise level measurement with Atheros driver Thread-Index: AcX5JnNIeB89wNbYSbGC8f/sfW468Q== From: "Lang, Tanja" To: X-OriginalArrivalTime: 04 Dec 2005 22:59:59.0159 (UTC) FILETIME=[737D4470:01C5F926] X-Mailman-Approved-At: Mon, 05 Dec 2005 05:35:25 +0000 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: noise level measurement with Atheros driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 23:00:07 -0000 Hi, =20 I would like to record signal strength and noise level for each client packet received on a wireless access point. I found the fields IEEE80211_RADIOTAP_DBM_ANTSIGNAL and IEEE80211_RADIOTAP_DBM_ANTNOISE in the radiotap header which should give me this information.=20 =20 The 'wi' interface sets both of these values in if_wi.c=20 if_wi.c: sc->sc_rx_th.wr_antnoise =3D = frmhdr.wi_rx_silence; if_wi.c: sc->sc_rx_th.wr_antsignal =3D = frmhdr.wi_rx_signal; =20 While the 'ath' interface only provides signal strength information. if_ath.c sc->sc_rx_th.wr_antsignal =3D = ds->ds_rxstat.rs_rssi; =20 Is the Atheros driver (which my current wireless card in the AP uses) capable of providing noise information? If yes, which line needs to be added in if_ath.c? =20 Thanks, Tanja =20 From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 5 05:50:10 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7AB4016A41F for ; Mon, 5 Dec 2005 05:50:10 +0000 (GMT) (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 B3E5D43D6A for ; Mon, 5 Dec 2005 05:50:09 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.192] ([10.0.0.192]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id jB55nsXq005078 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 4 Dec 2005 21:49:54 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <4393D4C0.7090500@errno.com> Date: Sun, 04 Dec 2005 21:48:48 -0800 From: Sam Leffler Organization: Errno Consulting User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Lang, Tanja" References: <0C7AF4692D7A6143A72AD00E5681D7E5ADA454@ESWW02.CSUMain.csu.edu.au> In-Reply-To: <0C7AF4692D7A6143A72AD00E5681D7E5ADA454@ESWW02.CSUMain.csu.edu.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: noise level measurement with Atheros driver X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 05:50:10 -0000 Lang, Tanja wrote: > Hi, > > > > I would like to record signal strength and noise level for each client > packet received on a wireless access point. I found the fields > IEEE80211_RADIOTAP_DBM_ANTSIGNAL and IEEE80211_RADIOTAP_DBM_ANTNOISE > in the radiotap header which should give me this information. > > > > The 'wi' interface sets both of these values in if_wi.c > > if_wi.c: sc->sc_rx_th.wr_antnoise = frmhdr.wi_rx_silence; > > if_wi.c: sc->sc_rx_th.wr_antsignal = frmhdr.wi_rx_signal; > > > > While the 'ath' interface only provides signal strength information. > > if_ath.c sc->sc_rx_th.wr_antsignal = ds->ds_rxstat.rs_rssi; > > > > Is the Atheros driver (which my current wireless card in the AP uses) > capable of providing noise information? If yes, which line needs to be > added in if_ath.c? Can't get calibrated noise floor info with the current hal. I've done the work and it will be available in the next hal I release. Sam From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 5 07:26:43 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D183C16A41F for ; Mon, 5 Dec 2005 07:26:43 +0000 (GMT) (envelope-from rzhe@agava.com) Received: from agava.mipt.ru (ofc2.agava.net [81.5.88.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5476343D5F for ; Mon, 5 Dec 2005 07:26:42 +0000 (GMT) (envelope-from rzhe@agava.com) Received: by agava.mipt.ru (Postfix, from userid 426) id 976B3721F68; Mon, 5 Dec 2005 10:07:11 +0300 (MSK) Received: from mailhub (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 4DF609D9AE0; Mon, 5 Dec 2005 09:42:04 +0300 (MSK) Received: from rzhe.agava-dubna.local (unknown [213.33.195.194]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by agava.mipt.ru (Postfix) with ESMTP id 8FFC2720B0F; Mon, 5 Dec 2005 09:21:36 +0300 (MSK) Date: Mon, 5 Dec 2005 09:27:50 +0300 From: Dmitry Agaphonov To: John-Mark Gurney Message-ID: <20051205092750.1c6d4f5d@rzhe.agava-dubna.local> In-Reply-To: <20051201185514.GP885@funkthat.com> References: <20051201150608.5e8d49f1@rzhe.agava-dubna.local> <20051201185514.GP885@funkthat.com> Organization: AGAVA Software X-Mailer: Sylpheed-Claws 1.0.1 (GTK+ 1.2.10; i386-portbld-freebsd4.11) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Kevent(2) doesn't notify about EVFILT_WRITE filter event X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 07:26:43 -0000 John-Mark Gurney wrote on 01.12.2005 10:55 MSK: JMG> Dmitry Agaphonov wrote this message on Thu, Dec 01, 2005 at 15:06 +0300: JMG> > I have two applications (server A and server B, A asks B for data to JMG> > serve clients) communicating via UNIX-domain socket. Testing local JMG> > clients interact to server A via UNIX-domain sockets too. Server A JMG> > uses kqueue(2) to handle clients and server B. JMG> > JMG> > When about 20 clients start requesting server A without delay, kevent(2) JMG> > doesn't notify about requested EVFILT_WRITE after only few small JMG> > requests. JMG> > JMG> > JMG> > Dumping kevent(2) changelist and eventlist gives the following: JMG> > JMG> > Server A asks for write event (with EV_ONESHOT flag set) to server B: JMG> > [13:45:36][DBG] Changing SysEvent: ident: 8, filter: -2, flags: 0x11, fflags: 0, data: 0, udata: 0x0 JMG> > [13:45:36][DBG] Received SysEvent: ident: 8, filter: -2, flags: 0x11, fflags: 0, data: 8192, udata: 0x0 JMG> > JMG> > So, the socket send buffer has 8192 bytes free. Then A sends 426 JMG> > bytes to B. JMG> > JMG> > Then server A asks for write event again: JMG> > [13:45:36][DBG] Changing SysEvent: ident: 8, filter: -2, flags: 0x11, fflags: 0, data: 0, udata: 0x0 JMG> > JMG> > After this, EVFILT_WRITE event is not returned. Noone else writes to JMG> > this socket. How it is possible? JMG> JMG> are you checking the output from the kevent that sets the sysevent? JMG> kevent if you do something "stupid" like set a _ONESHOT in kevent, and JMG> provide space for events to be returned to userland, the _ONESHOT will JMG> be immediately returned and cleared... JMG> JMG> It could also be an error is trying to be set, but can't be if you JMG> don't provide return space... so w/o seeing your code, I'd make sure JMG> when setting you are able to receive some events, and check what events JMG> you get back... Not in this, but that was my fault. Thank you for answer. From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 5 16:29:07 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66DA716A41F for ; Mon, 5 Dec 2005 16:29:07 +0000 (GMT) (envelope-from jacques.fourie@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7935E43D69 for ; Mon, 5 Dec 2005 16:29:03 +0000 (GMT) (envelope-from jacques.fourie@gmail.com) Received: by zproxy.gmail.com with SMTP id 12so806253nzp for ; Mon, 05 Dec 2005 08:29:03 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=O9zaylx9OE8nDlsyJtBShJD3PV5Q97XJjZo3WqQgEhGgRXr8YoE8IXF3MLlmEam2k6a6tNq0RtK/5fWoVe5DWR4fmCjrMCh/+R8HGPwMs9KcN2kMN4xDzvju0vp7iIaOowDJivXqq+jpmrLe2feSGonof4irsg/E8QZAqTqv5fI= Received: by 10.65.137.17 with SMTP id p17mr2895877qbn; Mon, 05 Dec 2005 08:29:02 -0800 (PST) Received: by 10.65.158.14 with HTTP; Mon, 5 Dec 2005 08:29:02 -0800 (PST) Message-ID: Date: Mon, 5 Dec 2005 18:29:02 +0200 From: Jacques Fourie To: John Baldwin In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200512011133.10441.jhb@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: 4.11 SMP issues on Intel SE7501CW2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 16:29:07 -0000 On 12/1/05, Jacques Fourie wrote: > Hi John, > > I booted a 6.0-RELEASE CD and the same thing (panic that freezes the > machine) happens. Can you think of any way in which to reliably reboot > the machine if this situation occurs? > > regards, > jacques > > On 12/1/05, John Baldwin wrote: > > On Thursday 01 December 2005 08:20 am, Jacques Fourie wrote: > > > Hi, > > > > > > With reference to the following thread : > > > http://groups.google.com/group/mailing.freebsd.smp/browse_thread/thre= ad/bd4 > > >5afab721e1a85/f66c8476272952af?lnk=3Dst&q=3D%2Bfreebsd+%2B%22failed!%2= 2+%2Bpanic > > >&rnum=3D80#f66c8476272952af > > > > > > I am seeing the same issue on an Intel SE7501CW2 dual Xeon machine. 6= .0 as > > > well as -current exhibits the same behaviour. Various postings to the > > > above thread suggests that this may be due to the APIC ID that the BI= OS > > > claims is assigned to the CPU not being the actual APIC ID assigned t= o the > > > CPU. Does anyone have any new information on this issue? If the subse= quent > > > panic succeeded in rebooting the machine this would not be a big issu= e for > > > me but unfortunately the machine hangs after pressing 'y' to the "pan= ic > > > [y/n]" prompt. Is there a way in which to initiate a hard reset in > > > software? > > > > No, there hasn't been any recent info on this and I haven't had any rec= ent > > reports of these problems, at least not on 5.x or 6.x. Can you try boo= ting > > up a 5.4 or 6.0 CD to see if they boot up ok? > > > > -- > > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > > "Power Users Use the Power to Serve" =3D http://www.FreeBSD.org > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.o= rg" > > > Hi John, In the end a workaround that "solved" the issue for me (on 4.11) was to call cpu_reset() instead of panic() when failing to start an AP. This causes the box to reboot reliably instead of freezing and after the reboot all AP's also start without any issues. On FreeBSD 6.0 (and -current) the panic() call successfully reboots the box so although the original problem of failing to start the AP is present on these platforms the problem is not that severe. In case anyone is interested in how to reproduce the problem (on 4.11, 6.0 or -current) - just cycle through a few soft reboot cycles (I placed a /sbin/reboot line in /etc/rc.local). regards, jacques From owner-freebsd-hackers@FreeBSD.ORG Mon Dec 5 18:54:49 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9237916A420 for ; Mon, 5 Dec 2005 18:54:49 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0811343D5E for ; Mon, 5 Dec 2005 18:54:46 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3200096 for multiple; Mon, 05 Dec 2005 13:52:18 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB5Is6L2040561; Mon, 5 Dec 2005 13:54:06 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Jacques Fourie Date: Mon, 5 Dec 2005 13:22:32 -0500 User-Agent: KMail/1.8.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512051322.32993.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-hackers@freebsd.org Subject: Re: 4.11 SMP issues on Intel SE7501CW2 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 18:54:49 -0000 On Monday 05 December 2005 11:29 am, Jacques Fourie wrote: > On 12/1/05, Jacques Fourie wrote: > > Hi John, > > > > I booted a 6.0-RELEASE CD and the same thing (panic that freezes the > > machine) happens. Can you think of any way in which to reliably reboot > > the machine if this situation occurs? > > > > regards, > > jacques > > > > On 12/1/05, John Baldwin wrote: > > > On Thursday 01 December 2005 08:20 am, Jacques Fourie wrote: > > > > Hi, > > > > > > > > With reference to the following thread : > > > > http://groups.google.com/group/mailing.freebsd.smp/browse_thread/thre > > > >ad/bd4 > > > > 5afab721e1a85/f66c8476272952af?lnk=st&q=%2Bfreebsd+%2B%22failed!%22+% > > > >2Bpanic &rnum=80#f66c8476272952af > > > > > > > > I am seeing the same issue on an Intel SE7501CW2 dual Xeon machine. > > > > 6.0 as well as -current exhibits the same behaviour. Various postings > > > > to the above thread suggests that this may be due to the APIC ID that > > > > the BIOS claims is assigned to the CPU not being the actual APIC ID > > > > assigned to the CPU. Does anyone have any new information on this > > > > issue? If the subsequent panic succeeded in rebooting the machine > > > > this would not be a big issue for me but unfortunately the machine > > > > hangs after pressing 'y' to the "panic [y/n]" prompt. Is there a way > > > > in which to initiate a hard reset in software? > > > > > > No, there hasn't been any recent info on this and I haven't had any > > > recent reports of these problems, at least not on 5.x or 6.x. Can you > > > try booting up a 5.4 or 6.0 CD to see if they boot up ok? > > > > > > -- > > > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > > > "Power Users Use the Power to Serve" = http://www.FreeBSD.org > > > _______________________________________________ > > > freebsd-hackers@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > > To unsubscribe, send any mail to > > > "freebsd-hackers-unsubscribe@freebsd.org" > > Hi John, > > In the end a workaround that "solved" the issue for me (on 4.11) was > to call cpu_reset() instead of panic() when failing to start an AP. > This causes the box to reboot reliably instead of freezing and after > the reboot all AP's also start without any issues. On FreeBSD 6.0 > (and -current) the panic() call successfully reboots the box so > although the original problem of failing to start the AP is present on > these platforms the problem is not that severe. > > In case anyone is interested in how to reproduce the problem (on 4.11, > 6.0 or -current) - just cycle through a few soft reboot cycles (I > placed a /sbin/reboot line in /etc/rc.local). Hmm, weird. I have no idea why the CPU is failing to startup the first time. Maybe it needs a longer timeout. You can try increasing the last DELAY() in start_ap() in sys/i386/i386/mp_machdep.c. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 6 01:51:33 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D76E16A41F; Tue, 6 Dec 2005 01:51:33 +0000 (GMT) (envelope-from craig@tobuj.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id A31F943D46; Tue, 6 Dec 2005 01:51:32 +0000 (GMT) (envelope-from craig@tobuj.gank.org) Received: by ion.gank.org (mail, from userid 1001) id 185E12D405; Mon, 5 Dec 2005 19:51:32 -0600 (CST) Date: Mon, 5 Dec 2005 19:51:29 -0600 From: Craig Boston To: freebsd-hackers@freebsd.org Message-ID: <20051206015129.GA34415@nowhere> Mail-Followup-To: Craig Boston , freebsd-hackers@freebsd.org, John Baldwin References: <20051130020734.GA6577@nowhere> <200512020817.55769.jhb@freebsd.org> <20051203005104.GA22567@nowhere> <200512031630.59476.jhb@freebsd.org> <20051204004131.GA7596@nowhere> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051204004131.GA7596@nowhere> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: Weird PCI interrupt delivery problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 01:51:33 -0000 On Sat, Dec 03, 2005 at 06:41:31PM -0600, Craig Boston wrote: > I'll keep hacking on it and follow up here if I figure anything out. Following up, I have made some interesting progress. With the ACPI timer disabled (debug.acpi.disabled=timer), the ACPI+APIC case now behaves the same as the plain APIC case. Each IRQ gets anywhere from 10,000-500,000 interrupts before it simply stops working. Switching the timecounter from ACPI-fast to something else after boot also improves the situation, but not as much as disabling the timer entirely. Up to about 50,000 but better than the <50 it would get otherwise. Switching the timecounter does not bring back any IRQs that have already "died". Disabling the timer does not change the +ACPI -APIC case, but I've been experimenting with that mode of operation and discovered it's not quite as it fist appeared. It's difficult to tell which device is producing interrupts since they all go to IRQ 11. I didn't notice before, but with +ACPI -APIC, the USB controller works fine (indefinitely). Also, I'm not 100% sure, but I don't think the devices on pci9 are producing _ANY_ interrupts at all. With the APIC enabled, rl0 sometimes lasts long enough to get a lease, but with it disabled it has yet to manage that. Also, the irq 11 count looks too low for multiple devices. I compared the entire PCI configuration space for the bridge with ACPI enabled and disabled and they were identical. The only thing that struck me as suspect is that the secondary status register for the bridge has the received master abort bit set, however that happens even when things are working so I'm not sure it's relevant. I get the same results after "fixing" the _PRT for bus 9. I tried both hardcoding the interrupts to 0xb and routing them via various link devices -- no luck. That's all really academic; I suspect ACPI+APIC is the only configuration that has a chance of actually working, and I'm halfway there... Craig From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 6 03:52:32 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9992D16A41F; Tue, 6 Dec 2005 03:52:32 +0000 (GMT) (envelope-from craig@tobuj.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5781043D55; Tue, 6 Dec 2005 03:52:32 +0000 (GMT) (envelope-from craig@tobuj.gank.org) Received: by ion.gank.org (mail, from userid 1001) id E2F7F2D405; Mon, 5 Dec 2005 21:52:31 -0600 (CST) Date: Mon, 5 Dec 2005 21:52:28 -0600 From: Craig Boston To: freebsd-hackers@freebsd.org Message-ID: <20051206035228.GA34979@nowhere> Mail-Followup-To: Craig Boston , freebsd-hackers@freebsd.org, John Baldwin References: <20051130020734.GA6577@nowhere> <200512020817.55769.jhb@freebsd.org> <20051203005104.GA22567@nowhere> <200512031630.59476.jhb@freebsd.org> <20051204004131.GA7596@nowhere> <20051206015129.GA34415@nowhere> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051206015129.GA34415@nowhere> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: Weird PCI interrupt delivery problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 03:52:32 -0000 On Mon, Dec 05, 2005 at 07:51:29PM -0600, Craig Boston wrote: > With the ACPI timer disabled (debug.acpi.disabled=timer), the ACPI+APIC > case now behaves the same as the plain APIC case. Each IRQ gets > anywhere from 10,000-500,000 interrupts before it simply stops working. And to follow up to myself yet again, the i8254 timecounter is also bad news for APIC. Switching to it, with or without ACPI, causes things to stop working really fast. Just a stab in the dark, but it sounds like there may be something screwy going on in the interconnect between the I/O APIC and the 8259s. I'm pretty familiar with old-style (ISA) design, but somewhat fuzzy on exactly how those two normally coexist, especially when everything is integrated together on a bridge chip somewhere. IIRC there used to be some mixed-mode hacks that have been cleaned up in 6.0. Might Windows still be doing something similar and that's why it works? Craig From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 6 06:57:27 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B91316A41F for ; Tue, 6 Dec 2005 06:57:27 +0000 (GMT) (envelope-from bsdforfree@rambler.ru) Received: from sotelrostov.ru (sotelrostov.ru [213.27.18.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1186543D4C for ; Tue, 6 Dec 2005 06:57:25 +0000 (GMT) (envelope-from bsdforfree@rambler.ru) Received: (qmail 92611 invoked by uid 98); 6 Dec 2005 10:02:23 +0300 Received: from 192.168.0.4 by mail.sotelrostov.ru (envelope-from , uid 82) with qmail-scanner-1.25 (clamdscan: 0.87.1/1204. spamassassin: 3.1.0. Clear:RC:1(192.168.0.4):. Processed in 0.121929 secs); 06 Dec 2005 07:02:23 -0000 X-Qmail-Scanner-Mail-From: bsdforfree@rambler.ru via mail.sotelrostov.ru X-Qmail-Scanner: 1.25 (Clear:RC:1(192.168.0.4):. Processed in 0.121929 secs) Received: from unknown (HELO ?192.168.0.4?) (192.168.0.4) by sotelrostov.ru with AES256-SHA encrypted SMTP; 6 Dec 2005 10:02:23 +0300 Message-ID: <439560E6.7080203@rambler.ru> Date: Tue, 06 Dec 2005 09:59:02 +0000 From: Vyacheslav Sotnikov User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Subject: SB Live 7.1 soundcard trouble X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 06:57:27 -0000 Hi list. I've got trouble with drivers for my soundcard - they dont detect it. pciconf brings that: none0@pci0:9:0: class=0x040100 card=0x10061102 chip=0x00071102 rev=0x00 hdr=0x00 vendor = 'Creative Labs' device = 'CA0106-DAT Audigy LS' class = multimedia subclass = audio I has tried standard snd_emu10k1, that shipped with FreeBSD and that is in ports - /usr/ports/audio/emu10kx/ - they both failed. I also try to install OSS from opensound.com and it failed with "kernel trap 18" while installation. What i can to do to get my card working? Thank you in advance. PS. I'm using FreeBSD 6.0-RELEASE. PPS. sorry my English. From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 6 08:58:38 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75AE716A41F for ; Tue, 6 Dec 2005 08:58:38 +0000 (GMT) (envelope-from igor@doom.homeunix.org) Received: from mail.ecolines.ru (ns.ecolines.ru [81.3.181.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5959843D5D for ; Tue, 6 Dec 2005 08:58:37 +0000 (GMT) (envelope-from igor@doom.homeunix.org) Received: (qmail 11162 invoked from network); 6 Dec 2005 09:02:06 -0000 Received: from unknown (HELO doom.homeunix.org) (ip@212.113.114.39) by mail.ecolines.ru with ESMTPA; 6 Dec 2005 09:02:06 -0000 Received: from doom.homeunix.org (localhost [127.0.0.1]) by doom.homeunix.org (8.13.4/8.13.4) with ESMTP id jB68vl9T000807; Tue, 6 Dec 2005 11:57:50 +0300 (MSK) (envelope-from igor@doom.homeunix.org) Received: (from igor@localhost) by doom.homeunix.org (8.13.4/8.13.4/Submit) id jB68kS2e000725; Tue, 6 Dec 2005 11:46:28 +0300 (MSK) (envelope-from igor) Date: Tue, 6 Dec 2005 11:46:28 +0300 From: Igor Pokrovsky To: Vyacheslav Sotnikov Message-ID: <20051206084628.GA645@doom.homeunix.org> Mail-Followup-To: Vyacheslav Sotnikov , freebsd-hackers@freebsd.org References: <439560E6.7080203@rambler.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <439560E6.7080203@rambler.ru> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org Subject: Re: SB Live 7.1 soundcard trouble X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 08:58:38 -0000 On Tue, Dec 06, 2005 at 09:59:02AM +0000, Vyacheslav Sotnikov wrote: > Hi list. > I've got trouble with drivers for my soundcard - they dont detect it. > pciconf brings that: > > none0@pci0:9:0: class=0x040100 card=0x10061102 chip=0x00071102 rev=0x00 > hdr=0x00 > vendor = 'Creative Labs' > device = 'CA0106-DAT Audigy LS' > class = multimedia > subclass = audio > > I has tried standard snd_emu10k1, that shipped with FreeBSD and that is > in ports - /usr/ports/audio/emu10kx/ - they both failed. > > I also try to install OSS from opensound.com and it failed with "kernel > trap 18" while installation. Before trying to install OSS drivers you should first uninstall FreeBSD ones. And make also sure you downloaded drivers for your version of FreeBSD. If nothing helps you can bug OSS people, they are very responsible. -ip -- Self starters --- won't. From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 6 09:07:59 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3DCB16A41F for ; Tue, 6 Dec 2005 09:07:59 +0000 (GMT) (envelope-from bsdforfree@rambler.ru) Received: from sotelrostov.ru (sotelrostov.ru [213.27.18.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C35143D7E for ; Tue, 6 Dec 2005 09:07:51 +0000 (GMT) (envelope-from bsdforfree@rambler.ru) Received: (qmail 1170 invoked by uid 98); 6 Dec 2005 12:12:48 +0300 Received: from 192.168.0.4 by mail.sotelrostov.ru (envelope-from , uid 82) with qmail-scanner-1.25 (clamdscan: 0.87.1/1204. spamassassin: 3.1.0. Clear:RC:1(192.168.0.4):. Processed in 0.133421 secs); 06 Dec 2005 09:12:48 -0000 X-Qmail-Scanner-Mail-From: bsdforfree@rambler.ru via mail.sotelrostov.ru X-Qmail-Scanner: 1.25 (Clear:RC:1(192.168.0.4):. Processed in 0.133421 secs) Received: from unknown (HELO ?192.168.0.4?) (192.168.0.4) by sotelrostov.ru with AES256-SHA encrypted SMTP; 6 Dec 2005 12:12:48 +0300 Message-ID: <43957F84.1070909@rambler.ru> Date: Tue, 06 Dec 2005 12:09:40 +0000 From: Vyacheslav Sotnikov User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Igor Pokrovsky References: <439560E6.7080203@rambler.ru> <20051206084628.GA645@doom.homeunix.org> In-Reply-To: <20051206084628.GA645@doom.homeunix.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: SB Live 7.1 soundcard trouble X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 09:07:59 -0000 Igor Pokrovsky wrote: >>I also try to install OSS from opensound.com and it failed with "kernel >>trap 18" while installation. > > > Before trying to install OSS drivers you should first uninstall FreeBSD ones. If by uninstalling you mean to kldunload current drivers, that i had do it already, and version of drivers is correct - oss3993c-freebsd-x86-v6.0-RELEASE.tar.gz > And make also sure you downloaded drivers for your version of FreeBSD. > If nothing helps you can bug OSS people, they are very responsible. thank you. i'll try. > > -ip From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 6 11:55:36 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FF1916A41F; Tue, 6 Dec 2005 11:55:36 +0000 (GMT) (envelope-from bushman@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1897043D68; Tue, 6 Dec 2005 11:55:30 +0000 (GMT) (envelope-from bushman@rsu.ru) Received: from [195.208.252.201] (celsius.cc.rsu.ru [195.208.252.201]) by mail.r61.net (8.13.4/8.13.4) with ESMTP id jB6BtRJx088166; Tue, 6 Dec 2005 14:55:27 +0300 (MSK) (envelope-from bushman@rsu.ru) Message-ID: <43957D3F.4070109@rsu.ru> Date: Tue, 06 Dec 2005 14:59:59 +0300 From: Michael Bushkov User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051018) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on asterix.r61.net X-Virus-Status: Clean Cc: Subject: [PATCH] nsswitch extensions + caching X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 11:55:36 -0000 Hello! I've made the "nsswitch + caching daemon" project during the Google's Summer of Code. I'm still working on it - there is always a room for improvements :) Since previous release, I've made a lot of changes to the initial version, fixed some bugs, and this version seems to be worth using it :) Here is the the new release of the patch: http://www.rsu.ru/~bushman/nsswitch_cached/nss_cached_rev2.patch The description of the project itself and of its several new features can be found here: http://rsu.ru/~bushman/nsswitch_cached/ Your feedback would be great! Michael Bushkov Rostov State University From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 6 12:27:15 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0822716A41F for ; Tue, 6 Dec 2005 12:27:15 +0000 (GMT) (envelope-from tkarpiniec@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22E8643D5E for ; Tue, 6 Dec 2005 12:27:14 +0000 (GMT) (envelope-from tkarpiniec@gmail.com) Received: by wproxy.gmail.com with SMTP id 36so334869wra for ; Tue, 06 Dec 2005 04:27:13 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=PqhcdvXh73spqH1FQEK6Cx5WYxZD/2/+LQSd3JBoCFjXkvqFX50wmd1YNn8rBpIV/kalB/bJq9lX8js9mgCGdtLb6+U2PnbBhzbjaqFWiSqT97/XnaBaFymRFmiaq32Y0UeUBUIOP8wnO3Ae4DHY/F2jcVd7iRtGSdebMBnRj7Y= Received: by 10.65.250.3 with SMTP id c3mr368247qbs; Tue, 06 Dec 2005 04:27:13 -0800 (PST) Received: by 10.65.123.7 with HTTP; Tue, 6 Dec 2005 04:27:13 -0800 (PST) Message-ID: <150f896b0512060427m4c253a65j6b2da78afd1c5490@mail.gmail.com> Date: Tue, 6 Dec 2005 23:27:13 +1100 From: Thomas Karpiniec To: Vyacheslav Sotnikov In-Reply-To: <43957F84.1070909@rambler.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <439560E6.7080203@rambler.ru> <20051206084628.GA645@doom.homeunix.org> <43957F84.1070909@rambler.ru> Cc: freebsd-hackers@freebsd.org Subject: Re: SB Live 7.1 soundcard trouble X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 12:27:15 -0000 Hi, First of all, I'm actually a Linux/Ubuntu user *avoids thrown squidgy fruit* but I have a CA0106 SB Audigy LS and have had no end of trouble with it - working presently, though. I could not get it to work with standard emu10k1 drivers, but to some extent using ALSA. It tended to have buffer issues - to get smooth sound out of xmms I had to use the custom options within xmms to set very high buffers on the output. I invite you to look at http://ubuntuforums.org/showthread.php?t=3D19307 I'm aware that the L in ALSA stands for linux, and that this method uses apt-get then dpkg to compile then install as a .deb package, but I can testify that this is the only way I have ever seen that has given me seamless sound (currently using eSound daemon) completely OS-wide. Good luck & regards, Thomas K From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 6 11:14:41 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 641F016A41F for ; Tue, 6 Dec 2005 11:14:41 +0000 (GMT) (envelope-from panda@mlc.edu.tw) Received: from mail.mlc.edu.tw (mail.mlc.edu.tw [163.19.163.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBFB743D58 for ; Tue, 6 Dec 2005 11:14:40 +0000 (GMT) (envelope-from panda@mlc.edu.tw) Received: from jhlh (jhlh.mlc.edu.tw [163.19.163.97]) (authenticated bits=0) by mail.mlc.edu.tw (8.12.11/8.12.11) with ESMTP id jB6B7378023122 for ; Tue, 6 Dec 2005 19:07:04 +0800 (CST) (envelope-from panda@mlc.edu.tw) Message-ID: <000601c5fa56$3bcd2a00$61a313a3@jhlh> From: "K.C.Huang-MLC" To: Date: Tue, 6 Dec 2005 19:14:26 +0800 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-MLC-MailScanner-Information: Please contact the ISP for more information X-MLC-MailScanner: Found to be clean X-MailScanner-From: panda@mlc.edu.tw X-Mailman-Approved-At: Tue, 06 Dec 2005 12:51:26 +0000 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: rm: Directory not empty ..(had tried chflag ...) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 11:14:41 -0000 Dear All: I running fsck -y to a device, and I delete some files in the same = time . I found there were some files could'nt be delete.. message: rm: old_files: Directory not empty I had tried=20 chflags -R noschg old_files rm -rf old_files thanks in advance ..^^ From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 6 16:39:54 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B1B8816A41F for ; Tue, 6 Dec 2005 16:39:54 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id E9F6743D5E for ; Tue, 6 Dec 2005 16:39:53 +0000 (GMT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id ; 6 Dec 2005 16:39:49 +0000 (GMT) Date: Tue, 6 Dec 2005 16:39:48 +0000 From: David Malone To: "K.C.Huang-MLC" Message-ID: <20051206163948.GA83751@walton.maths.tcd.ie> References: <000601c5fa56$3bcd2a00$61a313a3@jhlh> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000601c5fa56$3bcd2a00$61a313a3@jhlh> User-Agent: Mutt/1.5.6i Sender: dwmalone@maths.tcd.ie Cc: freebsd-hackers@freebsd.org Subject: Re: rm: Directory not empty ..(had tried chflag ...) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 16:39:54 -0000 On Tue, Dec 06, 2005 at 07:14:26PM +0800, K.C.Huang-MLC wrote: > Dear All: > I running fsck -y to a device, and I delete some files in the same time . > I found there were some files could'nt be delete.. > > message: > rm: old_files: Directory not empty > > I had tried > chflags -R noschg old_files > rm -rf old_files Did you run fsck until the filesystem is clean? If not try running fsck from single user mode a few more times. Another possibility is that this can sometimes happen with softupdates with fsck running in the background. If you wait for fsck to finish running in the background, then the problem should go away (this has been fixed in more recent FreeBSD releases). David. From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 6 16:41:41 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB06916A41F for ; Tue, 6 Dec 2005 16:41:41 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 822BA43D9E for ; Tue, 6 Dec 2005 16:41:26 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id jB6Gf4QA076781; Tue, 6 Dec 2005 10:41:04 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <4395BF04.50101@centtech.com> Date: Tue, 06 Dec 2005 10:40:36 -0600 From: Eric Anderson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1204/Mon Dec 5 04:09:54 2005 on mh1.centtech.com X-Virus-Status: Clean Cc: Nate Lawson Subject: scsi-target and the buffer cache X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 16:41:41 -0000 I'm curious about whether a target mode device would use the buffer cache or not. Here's a scenario: Host A: has fibre channel host adapter, in target mode, large memory pool, and another fiber channel host adapter connecting to fibre channel block device. Host B: Fibre channel host adapter, connecting to Host A. 'sees' the target mode block device created by Host A. Will Host A use the buffer cache to cache blocks between the real block device, and the shared target mode device? What about if Host A put a filesystem on the block device, created a single file the size of the filesystem, and shared that filesystem via a target mode device to Host B? What I'm wanting is a box (FreeBSD?) that can be placed between a fibre channel block device (like a RAID array), and a fibre channel host using that block device, and act as a block cache for that device, using the FreeBSD's memory. If it had a significant amount of memory, this could be very useful. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 6 18:46:32 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2199C16A41F; Tue, 6 Dec 2005 18:46:32 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE8B743D4C; Tue, 6 Dec 2005 18:46:31 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.17.229]) ([10.251.17.229]) by a50.ironport.com with ESMTP; 06 Dec 2005 10:46:27 -0800 X-IronPort-Anti-Spam-Filtered: true Message-ID: <4395DC82.1080103@elischer.org> Date: Tue, 06 Dec 2005 10:46:26 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Bushkov References: <43957D3F.4070109@rsu.ru> In-Reply-To: <43957D3F.4070109@rsu.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: [PATCH] nsswitch extensions + caching X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 18:46:32 -0000 Michael Bushkov wrote: [...] so, I've been wonderring.. what's all the fuss about nsswitch? what does it get us? (Not saying it doesn't, just hoping someone will explain) From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 6 19:33:19 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E256916A41F; Tue, 6 Dec 2005 19:33:19 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5523843D5A; Tue, 6 Dec 2005 19:33:19 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id jB6JXHuq004166; Tue, 6 Dec 2005 11:33:17 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jB6JXHSD004164; Tue, 6 Dec 2005 11:33:17 -0800 Date: Tue, 6 Dec 2005 11:33:17 -0800 From: Brooks Davis To: Julian Elischer Message-ID: <20051206193317.GB31292@odin.ac.hmc.edu> References: <43957D3F.4070109@rsu.ru> <4395DC82.1080103@elischer.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CUfgB8w4ZwR/yMy5" Content-Disposition: inline In-Reply-To: <4395DC82.1080103@elischer.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, Michael Bushkov Subject: Re: [PATCH] nsswitch extensions + caching X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 19:33:20 -0000 --CUfgB8w4ZwR/yMy5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 06, 2005 at 10:46:26AM -0800, Julian Elischer wrote: > Michael Bushkov wrote: > [...] >=20 > so, I've been wonderring.. what's all the fuss about nsswitch? > what does it get us? It gives us the ability use modules to provide arbitrary backends for a variety of interfaces to system databases. For instance getpw*(), gethost*(), etc. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --CUfgB8w4ZwR/yMy5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDled7XY6L6fI4GtQRAvfpAJ9YhDgT4KsY19do3iArGig+LixbawCgyPj+ KJgNXqw1x4JvAwghd/2bCtg= =lsxm -----END PGP SIGNATURE----- --CUfgB8w4ZwR/yMy5-- From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 6 19:39:12 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B574216A41F; Tue, 6 Dec 2005 19:39:12 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id E366843D82; Tue, 6 Dec 2005 19:38:42 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id jB6JcVbs019222; Tue, 6 Dec 2005 13:38:31 -0600 (CST) (envelope-from dan) Date: Tue, 6 Dec 2005 13:38:31 -0600 From: Dan Nelson To: Brooks Davis Message-ID: <20051206193830.GA33064@dan.emsphone.com> References: <43957D3F.4070109@rsu.ru> <4395DC82.1080103@elischer.org> <20051206193317.GB31292@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051206193317.GB31292@odin.ac.hmc.edu> X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, Julian Elischer , Michael Bushkov Subject: Re: [PATCH] nsswitch extensions + caching X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 19:39:12 -0000 In the last episode (Dec 06), Brooks Davis said: > On Tue, Dec 06, 2005 at 10:46:26AM -0800, Julian Elischer wrote: > > Michael Bushkov wrote: > > [...] > > > > so, I've been wonderring.. what's all the fuss about nsswitch? > > what does it get us? > > It gives us the ability use modules to provide arbitrary backends for a > variety of interfaces to system databases. For instance getpw*(), > gethost*(), etc. Michael's patch itself adds caching to our nsswitch implementation, which dramatically improves performance on slow sources (ldaps, for example). -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 6 19:45:09 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE9B916A422; Tue, 6 Dec 2005 19:45:08 +0000 (GMT) (envelope-from bushman@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE88D43D69; Tue, 6 Dec 2005 19:44:57 +0000 (GMT) (envelope-from bushman@rsu.ru) Received: from jersey (p49.mp96.aaanet.ru [80.80.96.49]) (authenticated bits=0) by mail.r61.net (8.13.4/8.13.4) with ESMTP id jB6Ji2wo078126 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 6 Dec 2005 22:44:11 +0300 (MSK) (envelope-from bushman@rsu.ru) Message-ID: <000c01c5fa9d$7d219710$0100a8c0@jersey> From: "Michael Bushkov" To: "Julian Elischer" References: <43957D3F.4070109@rsu.ru> <4395DC82.1080103@elischer.org> Date: Tue, 6 Dec 2005 22:44:02 +0300 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.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on asterix.r61.net X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: [PATCH] nsswitch extensions + caching X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 19:45:09 -0000 I haven't seen much fuss, actually :) Here are some points: 1. Nsswitch makes caching easy. As nsswitch-related calls are done quite often, caching can be very useful. With nsswitch we can organize caching of different types of data (passwd, groups, services, etc) in the quite simple uniform manner. In other OSes caching is usually organized via nscd. The caching daemon (it's implementation is in the patch) is the analogue of the nscd in some way. It has different approach for caching, but can work in the way, the nscd usually works. 2. Nsswitch implementation is not yet completed. There's a number of databases, which can be supported, but their support is not yet implemented. Their support in nsswitch will give us: a) uniform way to configure the data sources to use (via nsswitch.conf) 2) the ability to cache their data 3. More concrete example is /etc/services file. The services database didn't utilize nsswitch/nsdispatch. If it uses nsdispatch, it will be able to cache data from the file - and we'll be able to make it as big as we want. Of course, first "uncached" requests will take some time, but all subsequent requests for the information, that is already in the cache will be extremely fast - they won't event open the /etc/services file. 4. Another concrete example is OpenSSH authroization keys. If we use nsswitch to retrieve them, we can easily use NIS or LDAP as their storage, which is a good thing. I hope, this will satisfy you :) With best regards, Michael ----- Original Message ----- From: "Julian Elischer" To: "Michael Bushkov" Cc: ; Sent: Tuesday, December 06, 2005 9:46 PM Subject: Re: [PATCH] nsswitch extensions + caching > Michael Bushkov wrote: > [...] > > so, I've been wonderring.. what's all the fuss about nsswitch? > what does it get us? > (Not saying it doesn't, just hoping someone will explain) > From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 6 20:47:45 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB0A916A41F for ; Tue, 6 Dec 2005 20:47:45 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F72D43D5A for ; Tue, 6 Dec 2005 20:47:45 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id jB6KlhFQ095675; Tue, 6 Dec 2005 12:47:43 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id jB6KlfaA095674; Tue, 6 Dec 2005 12:47:41 -0800 (PST) (envelope-from jmg) Date: Tue, 6 Dec 2005 12:47:41 -0800 From: John-Mark Gurney To: "K.C.Huang-MLC" Message-ID: <20051206204741.GJ55657@funkthat.com> Mail-Followup-To: "K.C.Huang-MLC" , freebsd-hackers@freebsd.org References: <000601c5fa56$3bcd2a00$61a313a3@jhlh> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000601c5fa56$3bcd2a00$61a313a3@jhlh> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-hackers@freebsd.org Subject: Re: rm: Directory not empty ..(had tried chflag ...) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 20:47:46 -0000 K.C.Huang-MLC wrote this message on Tue, Dec 06, 2005 at 19:14 +0800: > I running fsck -y to a device, and I delete some files in the same time . > I found there were some files could'nt be delete.. Don't run fsck -y while you have the file system mounted.. if you do, you will end up with troubles like you have... you should make sure to pass -B to fsck if you want to run fsck while the file system is mounted... Though I've never done that manually (I let the rc scripts handle that for me)... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 6 21:49:23 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8BC616A420 for ; Tue, 6 Dec 2005 21:49:23 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 287B143D79 for ; Tue, 6 Dec 2005 21:49:09 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3275227 for multiple; Tue, 06 Dec 2005 16:49:18 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB6Ln0Uu051148; Tue, 6 Dec 2005 16:49:03 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Craig Boston Date: Tue, 6 Dec 2005 15:20:30 -0500 User-Agent: KMail/1.8.2 References: <20051130020734.GA6577@nowhere> <20051206015129.GA34415@nowhere> <20051206035228.GA34979@nowhere> In-Reply-To: <20051206035228.GA34979@nowhere> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512061520.31168.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-hackers@freebsd.org Subject: Re: Weird PCI interrupt delivery problem X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 21:49:24 -0000 On Monday 05 December 2005 10:52 pm, Craig Boston wrote: > On Mon, Dec 05, 2005 at 07:51:29PM -0600, Craig Boston wrote: > > With the ACPI timer disabled (debug.acpi.disabled=timer), the ACPI+APIC > > case now behaves the same as the plain APIC case. Each IRQ gets > > anywhere from 10,000-500,000 interrupts before it simply stops working. > > And to follow up to myself yet again, the i8254 timecounter is also bad > news for APIC. Switching to it, with or without ACPI, causes things to > stop working really fast. > > Just a stab in the dark, but it sounds like there may be something > screwy going on in the interconnect between the I/O APIC and the 8259s. > I'm pretty familiar with old-style (ISA) design, but somewhat fuzzy on > exactly how those two normally coexist, especially when everything is > integrated together on a bridge chip somewhere. > > IIRC there used to be some mixed-mode hacks that have been cleaned up in > 6.0. Might Windows still be doing something similar and that's why it > works? No, Windows doesn't use mixed mode. That stuff only had to do with routing IRQ0 anyways. We use the lapic timer instead of IRQ0 now (as does Windows). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 6 22:23:28 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1336116A41F for ; Tue, 6 Dec 2005 22:23:28 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 856AC43D5F for ; Tue, 6 Dec 2005 22:23:27 +0000 (GMT) (envelope-from nate@root.org) Received: from [172.16.0.224] (fi01-84CBdd.tokyo.flets.isao.net [211.132.203.221]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id jB6MNSdu003007 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 6 Dec 2005 14:23:29 -0800 Message-ID: <43960F55.3010508@root.org> Date: Wed, 07 Dec 2005 07:23:17 +0900 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <4395BF04.50101@centtech.com> In-Reply-To: <4395BF04.50101@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 06 Dec 2005 22:25:51 +0000 Cc: hackers@freebsd.org Subject: Re: scsi-target and the buffer cache X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 22:23:28 -0000 Eric Anderson wrote: > I'm curious about whether a target mode device would use the buffer > cache or not. Here's a scenario: > > Host A: has fibre channel host adapter, in target mode, large memory > pool, and another fiber channel host adapter connecting to fibre channel > block device. > Host B: Fibre channel host adapter, connecting to Host A. 'sees' the > target mode block device created by Host A. > > Will Host A use the buffer cache to cache blocks between the real block > device, and the shared target mode device? > What about if Host A put a filesystem on the block device, created a > single file the size of the filesystem, and shared that filesystem via a > target mode device to Host B? > What I'm wanting is a box (FreeBSD?) that can be placed between a fibre > channel block device (like a RAID array), and a fibre channel host using > that block device, and act as a block cache for that device, using the > FreeBSD's memory. If it had a significant amount of memory, this could > be very useful. If you use the example scsi_target usermode (usr/share/examples/scsi_target), then the buffer cache will be used since its reads/writes are from usermode like normal. If you don't want that behavior, you can set O_DIRECT in the open() call of the backing store file. If you chose to modify the kernel side, you'd have to make sure your accesses were through the VOP layer and then it would be cached. You should check to be sure the target mode performance meets your expectations also. -- Nate From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 7 07:11:01 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8942816A41F for ; Wed, 7 Dec 2005 07:11:01 +0000 (GMT) (envelope-from ilovefd@topaz.plala.or.jp) Received: from mvs5.plala.or.jp (c158133.vh.plala.or.jp [210.150.158.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADF5943D46 for ; Wed, 7 Dec 2005 07:10:59 +0000 (GMT) (envelope-from ilovefd@topaz.plala.or.jp) Received: from ilovefd533 ([150.29.122.91]) by mvs5.plala.or.jp with SMTP id <20051207071058.DGLG5652.mvs5.plala.or.jp@ilovefd533> for ; Wed, 7 Dec 2005 16:10:58 +0900 Message-ID: <017b01c5fafd$a5f9d250$1400a8c0@ilovefd533> From: "gama" To: References: <20051130020734.GA6577@nowhere> <20051206015129.GA34415@nowhere><20051206035228.GA34979@nowhere> <200512061520.31168.jhb@freebsd.org> Date: Wed, 7 Dec 2005 16:12:56 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Subject: twm doesn"t start with vnc server on FreeBSD l5.4/amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 07:11:01 -0000 I am using FreeBSD5.4/amd5.4 but any windows manager doesn"t start with vnc server. FreeBSD5.4/amd64 has any troubles with X windows? FreeBSD5.4/i386 workede well with vnc and twm. ----- Original Message ----- From: "John Baldwin" To: "Craig Boston" Cc: Sent: Wednesday, December 07, 2005 5:20 AM Subject: Re: Weird PCI interrupt delivery problem > On Monday 05 December 2005 10:52 pm, Craig Boston wrote: > > On Mon, Dec 05, 2005 at 07:51:29PM -0600, Craig Boston wrote: > > > With the ACPI timer disabled (debug.acpi.disabled=timer), the ACPI+APIC > > > case now behaves the same as the plain APIC case. Each IRQ gets > > > anywhere from 10,000-500,000 interrupts before it simply stops working. > > > > And to follow up to myself yet again, the i8254 timecounter is also bad > > news for APIC. Switching to it, with or without ACPI, causes things to > > stop working really fast. > > > > Just a stab in the dark, but it sounds like there may be something > > screwy going on in the interconnect between the I/O APIC and the 8259s. > > I'm pretty familiar with old-style (ISA) design, but somewhat fuzzy on > > exactly how those two normally coexist, especially when everything is > > integrated together on a bridge chip somewhere. > > > > IIRC there used to be some mixed-mode hacks that have been cleaned up in > > 6.0. Might Windows still be doing something similar and that's why it > > works? > > No, Windows doesn't use mixed mode. That stuff only had to do with routing > IRQ0 anyways. We use the lapic timer instead of IRQ0 now (as does Windows). > > -- > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve" = http://www.FreeBSD.org > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 7 07:23:56 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1452C16A420 for ; Wed, 7 Dec 2005 07:23:56 +0000 (GMT) (envelope-from ilovefd@topaz.plala.or.jp) Received: from mvs2.plala.or.jp (c158130.vh.plala.or.jp [210.150.158.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5617F43D53 for ; Wed, 7 Dec 2005 07:23:54 +0000 (GMT) (envelope-from ilovefd@topaz.plala.or.jp) Received: from ilovefd533 ([150.29.122.91]) by mvs2.plala.or.jp with SMTP id <20051207072353.QCAM18439.mvs2.plala.or.jp@ilovefd533> for ; Wed, 7 Dec 2005 16:23:53 +0900 Message-ID: <01a001c5faff$74c26ab0$1400a8c0@ilovefd533> From: "gama" To: References: <4395BF04.50101@centtech.com> <43960F55.3010508@root.org> Date: Wed, 7 Dec 2005 16:25:45 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Subject: /usr/ports/sysutils/sge is broken ? for amd 64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 07:23:56 -0000 I am trying to install Sun Grid Engine with FreeBSD5.4/amd64. It needs glibc-common-2.3.2-4.80.8.amd64.rpm glibc-common-2.3.2-4.80.8.i386.rpm can be found in ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/rpm/i386/8.0/ but amd64. Where can I get glibc-common-2.3.2-4.80.8.amd64.rpm. From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 7 07:47:21 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC45C16A41F; Wed, 7 Dec 2005 07:47:20 +0000 (GMT) (envelope-from yuri@irfu.se) Received: from colibri.its.uu.se (colibri.its.uu.se [130.238.4.154]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5193B43D5E; Wed, 7 Dec 2005 07:47:16 +0000 (GMT) (envelope-from yuri@irfu.se) Received: by colibri.its.uu.se (Postfix, from userid 211) id F1028F76; Wed, 7 Dec 2005 08:47:14 +0100 (NFT) Received: from colibri.its.uu.se(127.0.0.1) by colibri.its.uu.se via virus-scan id s14345; Wed, 7 Dec 05 08:47:07 +0100 Received: from hq.irfu.se (hq.irfu.se [130.238.30.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by colibri.its.uu.se (Postfix) with ESMTP id BF8DBF73; Wed, 7 Dec 2005 08:47:06 +0100 (NFT) Received: from ice.irfu.se (ice.irfu.se [130.238.30.157]) (authenticated bits=0) by hq.irfu.se (8.13.4/8.13.4) with ESMTP id jB77l56H018503 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 7 Dec 2005 08:47:06 +0100 (CET) (envelope-from yuri@irfu.se) From: Yuri Khotyaintsev Organization: Swedish Institute of Space Physics To: John Baldwin Date: Wed, 7 Dec 2005 08:47:04 +0100 User-Agent: KMail/1.8.3 References: <200512021100.03167.yuri@irfu.se> <200512020854.20959.jhb@freebsd.org> In-Reply-To: <200512020854.20959.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512070847.04980.yuri@irfu.se> X-Spam-Status: No, score=-1.4 required=7.0 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on hq.irfu.se X-Mailman-Approved-At: Wed, 07 Dec 2005 12:35:54 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Fatal trap 12: page fault while in kernel mode X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 07:47:21 -0000 On Friday 02 December 2005 14.54, John Baldwin wrote: > On Friday 02 December 2005 05:00 am, Yuri Khotyaintsev wrote: > > I have the following panic occurring several times a week. The machine = is > > an NFS server, and it usually panics early in the morning, when first > > people try to access it. After reboot it may work OK for 1-2 days, and > > then panics again. I have tried changing memory and replacing disk which > > was exported via NFS, but nothing helped :( > > > > Any suggestion on how to fix this panic will be very much appreciated ! > > This panic (in propagate_priority) is usually caused when a thread goes to > sleep while holding a mutex (which is forbidden). If you enable INVARIAN= TS > and/or WITNESS you should get a better panic, and with WITNESS you will > even be warned when a thread goes to sleep while holding a mutex. Howeve= r, > these options do introduce considerable execution overhead, and sometimes > that overhead changes the timing enough to hide the race. :( Here are the two panics which I got with INVARIANTS and WITNESS enabled. # kgdb /usr/obj/usr/src/sys/HEM.DEBUG/kernel.debug vmcore.8=20 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:= =20 Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain condition= s. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: Memory modified after free 0xc4759e00(508) val=3D0 @ 0xc4759e00 panic: Most recently used by UFS dirhash Uptime: 11h8m36s Dumping 511 MB (2 chunks) chunk 0: 1MB (160 pages) ... ok chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367 351 335= =20 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:165 165 pcpu.h: No such file or directory. in pcpu.h (kgdb) where #0 doadump () at pcpu.h:165 #1 0xc050fd4f in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:3= 99 #2 0xc0510043 in panic (fmt=3D0xc06dccbb "Most recently used by %s\n") at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xc0648ccf in mtrash_ctor (mem=3D0xc4759e00, size=3D0, arg=3D0x0, flags= =3D2) at /usr/src/sys/vm/uma_dbg.c:137 #4 0xc06469c1 in uma_zalloc_arg (zone=3D0xc104d980, udata=3D0x0, flags=3D2) at /usr/src/sys/vm/uma_core.c:1850 #5 0xc05043cd in malloc (size=3D400, mtp=3D0xc06fb700, flags=3D2) at uma.h= :275 #6 0xc063fba9 in ufs_readdir (ap=3D0xd56eaaec) at /usr/src/sys/ufs/ufs/ufs_vnops.c:1846 #7 0xc06a61cc in VOP_READDIR_APV (vop=3D0x0, a=3D0xd56eaaec) at vnode_if.c= :1427 #8 0xc0607716 in nfsrv_readdir (nfsd=3D0xc4368c00, slp=3D0x0, td=3D0xc3326= 780,=20 mrq=3D0xd56eac80) at vnode_if.h:746 #9 0xc060fa5b in nfssvc_nfsd (td=3D0x0) at /usr/src/sys/nfsserver/nfs_syscalls.c:472 #10 0xc060f280 in nfssvc (td=3D0xc3326780, uap=3D0xd56ead04) at /usr/src/sys/nfsserver/nfs_syscalls.c:181 #11 0xc069b6b0 in syscall (frame=3D =2D--Type to continue, or q to quit--- {tf_fs =3D 59, tf_es =3D 59, tf_ds =3D 59, tf_edi =3D 0, tf_esi =3D 0= , tf_ebp =3D=20 =2D1077941464, tf_isp =3D -714166940, tf_ebx =3D 0, tf_edx =3D -1077936144,= tf_ecx =3D=20 1, tf_eax =3D 155, tf_trapno =3D 12, tf_err =3D 2, tf_eip =3D 671852067, tf= _cs =3D 51,=20 tf_eflags =3D 582, tf_esp =3D -1077941492, tf_ss =3D 59})=20 at /usr/src/sys/i386/i386/trap.c:981 #12 0xc068947f in Xint0x80_syscall ()=20 at /usr/src/sys/i386/i386/exception.s:200 #13 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) quit # kgdb /usr/obj/usr/src/sys/HEM.DEBUG/kernel.debug vmcore.9 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so:= =20 Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain condition= s. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: Memory modified after free 0xc5172800(508) val=3D0 @ 0xc5172800 panic: Most recently used by UFS dirhash Uptime: 1d1h7m17s Dumping 511 MB (2 chunks) chunk 0: 1MB (160 pages) ... ok chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367 351 335= =20 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:165 165 pcpu.h: No such file or directory. in pcpu.h (kgdb) where #0 doadump () at pcpu.h:165 #1 0xc050fd4f in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:3= 99 #2 0xc0510043 in panic (fmt=3D0xc06dccbb "Most recently used by %s\n") at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xc0648ccf in mtrash_ctor (mem=3D0xc5172800, size=3D0, arg=3D0x0, flags= =3D257) at /usr/src/sys/vm/uma_dbg.c:137 #4 0xc06469c1 in uma_zalloc_arg (zone=3D0xc104d980, udata=3D0x0, flags=3D2= 57) at /usr/src/sys/vm/uma_core.c:1850 #5 0xc05043cd in malloc (size=3D368, mtp=3D0xc070eb60, flags=3D257) at uma= =2Eh:275 #6 0xc063729b in ufsdirhash_build (ip=3D0xc55664a4) at /usr/src/sys/ufs/ufs/ufs_dirhash.c:184 #7 0xc0639441 in ufs_lookup (ap=3D0xd57c283c) at /usr/src/sys/ufs/ufs/ufs_lookup.c:192 #8 0xc06a4e0a in VOP_CACHEDLOOKUP_APV (vop=3D0x0, a=3D0xd57c283c) at vnode_if.c:150 #9 0xc0565e3b in vfs_cache_lookup (ap=3D0x0) at vnode_if.h:82 #10 0xc06a4d2f in VOP_LOOKUP_APV (vop=3D0xc070eee0, a=3D0xd57c28e4) at vnode_if.c:99 #11 0xc056a8d0 in lookup (ndp=3D0xd57c2bec) at vnode_if.h:56 =2D--Type to continue, or q to quit--- #12 0xc060df58 in nfs_namei (ndp=3D0xd57c2bec, fhp=3D0x0, len=3D0, slp=3D0x= 0, nam=3D0x0,=20 mdp=3D0xd57c2a04, dposp=3D0xd57c2a08, retdirp=3D0xd57c29f0, v3=3D8,=20 retdirattrp=3D0x0, retdirattr_retp=3D0x0, td=3D0xc350a780, pubflag=3D0) at /usr/src/sys/nfsserver/nfs_srvsubs.c:780 #13 0xc05fd284 in nfsrv_lookup (nfsd=3D0xc5764100, slp=3D0x0, td=3D0xc350a7= 80,=20 mrq=3D0xd57c2c80) at /usr/src/sys/nfsserver/nfs_serv.c:517 #14 0xc060fa5b in nfssvc_nfsd (td=3D0x0) at /usr/src/sys/nfsserver/nfs_syscalls.c:472 #15 0xc060f280 in nfssvc (td=3D0xc350a780, uap=3D0xd57c2d04) at /usr/src/sys/nfsserver/nfs_syscalls.c:181 #16 0xc069b6b0 in syscall (frame=3D {tf_fs =3D 59, tf_es =3D 59, tf_ds =3D 59, tf_edi =3D 0, tf_esi =3D 0= , tf_ebp =3D=20 =2D1077941464, tf_isp =3D -713282204, tf_ebx =3D 0, tf_edx =3D -1077936144,= tf_ecx =3D=20 1, tf_eax =3D 155, tf_trapno =3D 12, tf_err =3D 2, tf_eip =3D 671852067, tf= _cs =3D 51,=20 tf_eflags =3D 582, tf_esp =3D -1077941492, tf_ss =3D 59})=20 at /usr/src/sys/i386/i386/trap.c:981 #17 0xc068947f in Xint0x80_syscall ()=20 at /usr/src/sys/i386/i386/exception.s:200 #18 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) exit Undefined command: "exit". Try "help". (kgdb) quit =2D-=20 Dr. Yuri Khotyaintsev Institutet f=F6r rymdfysik (IRF), Uppsala From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 7 08:39:49 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6553716A41F; Wed, 7 Dec 2005 08:39:49 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn.pobox.com (thorn.pobox.com [208.210.124.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9939E43D55; Wed, 7 Dec 2005 08:39:48 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn (localhost [127.0.0.1]) by thorn.pobox.com (Postfix) with ESMTP id A4E49B8; Wed, 7 Dec 2005 03:40:09 -0500 (EST) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thorn.sasl.smtp.pobox.com (Postfix) with ESMTP id 3B9EE10BF; Wed, 7 Dec 2005 03:40:04 -0500 (EST) Received: from lists by mappit.local.linnet.org with local (Exim 4.60 (FreeBSD)) (envelope-from ) id 1Ejupv-0003Om-P3; Wed, 07 Dec 2005 08:39:40 +0000 Date: Wed, 7 Dec 2005 08:39:39 +0000 From: Brian Candler To: Brooks Davis Message-ID: <20051207083939.GA13055@uk.tiscali.com> References: <43957D3F.4070109@rsu.ru> <4395DC82.1080103@elischer.org> <20051206193317.GB31292@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051206193317.GB31292@odin.ac.hmc.edu> User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Wed, 07 Dec 2005 12:37:58 +0000 Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, Julian Elischer , Michael Bushkov Subject: Re: [PATCH] nsswitch extensions + caching X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 08:39:49 -0000 On Tue, Dec 06, 2005 at 11:33:17AM -0800, Brooks Davis wrote: > On Tue, Dec 06, 2005 at 10:46:26AM -0800, Julian Elischer wrote: > > Michael Bushkov wrote: > > [...] > > > > so, I've been wonderring.. what's all the fuss about nsswitch? > > what does it get us? > > It gives us the ability use modules to provide arbitrary backends for a > variety of interfaces to system databases. For instance getpw*(), > gethost*(), etc. Or put it another way - it supplies the missing half to PAM. Whilst PAM can check your password using arbitary backend modules, it can't return your $HOME directory or the uid/gid to use. Regards, Brian. From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 7 12:41:06 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B9B316A41F for ; Wed, 7 Dec 2005 12:41:05 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from mail08a.verio.de (mail08a.verio.de [213.198.55.73]) by mx1.FreeBSD.org (Postfix) with SMTP id DD46743D5A for ; Wed, 7 Dec 2005 12:41:04 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from mx33.stngva01.us.mxservers.net (204.202.242.74) by mail08a.verio.de (RS ver 1.0.95vs) with SMTP id 0-0203609260; Wed, 7 Dec 2005 13:41:02 +0100 (CET) Received: from www.jennejohn.org [213.198.5.174] (EHLO peedub.jennejohn.org) by mx33.stngva01.us.mxservers.net (mxl_mta-1.3.8-10p4) with ESMTP id d58d6934.13438.174.mx33.stngva01.us.mxservers.net; Wed, 07 Dec 2005 07:41:01 -0500 (EST) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.4/8.11.6) with ESMTP id jB7CexvJ025961; Wed, 7 Dec 2005 13:40:59 +0100 (CET) (envelope-from garyj@jennejohn.org) Message-Id: <200512071240.jB7CexvJ025961@peedub.jennejohn.org> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 To: "gama" In-Reply-To: Message from "gama" of "Wed, 07 Dec 2005 16:25:45 +0900." <01a001c5faff$74c26ab0$1400a8c0@ilovefd533> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 07 Dec 2005 13:40:59 +0100 From: Gary Jennejohn X-Spam: [F=0.0100000000; heur=0.500(-19800); stat=0.010; spamtraq-heur=0.500(2005120618)] X-MAIL-FROM: X-SOURCE-IP: [213.198.5.174] X-Loop-Detect: 1 X-DistLoop-Detect: 1 Cc: freebsd-hackers@freebsd.org Subject: Re: /usr/ports/sysutils/sge is broken ? for amd 64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 12:41:06 -0000 "gama" writes: > I am trying to install Sun Grid Engine with FreeBSD5.4/amd64. > It needs glibc-common-2.3.2-4.80.8.amd64.rpm > > glibc-common-2.3.2-4.80.8.i386.rpm can be found in > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/rpm/i386/8.0/ but amd64. > > Where can I get glibc-common-2.3.2-4.80.8.amd64.rpm. > See this URL: http://lists.freebsd.org/pipermail/freebsd-ports/2005-November/027550.html You could have this out for yourself by doing a simple search using e.g. google. --- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 7 14:28:48 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C73F16A449; Wed, 7 Dec 2005 14:28:48 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 505B043D62; Wed, 7 Dec 2005 14:28:39 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3319101 for multiple; Wed, 07 Dec 2005 09:29:49 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB7ERYo5056800; Wed, 7 Dec 2005 09:27:42 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Yuri Khotyaintsev Date: Wed, 7 Dec 2005 09:27:12 -0500 User-Agent: KMail/1.8.3 References: <200512021100.03167.yuri@irfu.se> <200512020854.20959.jhb@freebsd.org> <200512070847.04980.yuri@irfu.se> In-Reply-To: <200512070847.04980.yuri@irfu.se> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512070927.14391.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Fatal trap 12: page fault while in kernel mode X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 14:28:49 -0000 On Wednesday 07 December 2005 02:47 am, Yuri Khotyaintsev wrote: > On Friday 02 December 2005 14.54, John Baldwin wrote: > > On Friday 02 December 2005 05:00 am, Yuri Khotyaintsev wrote: > > > I have the following panic occurring several times a week. The machine > > > is an NFS server, and it usually panics early in the morning, when > > > first people try to access it. After reboot it may work OK for 1-2 > > > days, and then panics again. I have tried changing memory and replaci= ng > > > disk which was exported via NFS, but nothing helped :( > > > > > > Any suggestion on how to fix this panic will be very much appreciated= ! > > > > This panic (in propagate_priority) is usually caused when a thread goes > > to sleep while holding a mutex (which is forbidden). If you enable > > INVARIANTS and/or WITNESS you should get a better panic, and with WITNE= SS > > you will even be warned when a thread goes to sleep while holding a > > mutex. However, these options do introduce considerable execution > > overhead, and sometimes that overhead changes the timing enough to hide > > the race. :( > > Here are the two panics which I got with INVARIANTS and WITNESS enabled. > > Unread portion of the kernel message buffer: > Memory modified after free 0xc4759e00(508) val=3D0 @ 0xc4759e00 > panic: Most recently used by UFS dirhash Well, this isn't the panic I was expecting, but it points to something=20 trashing free'd memory via a stale pointer or some such. You might be able= =20 to use MEMGUARD to track this down. =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 7 19:38:38 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 549F116A41F for ; Wed, 7 Dec 2005 19:38:38 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B96443D49 for ; Wed, 7 Dec 2005 19:38:29 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id jB7JcPtR032092; Wed, 7 Dec 2005 11:38:25 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jB7JcOA0032091; Wed, 7 Dec 2005 11:38:24 -0800 Date: Wed, 7 Dec 2005 11:38:24 -0800 From: Brooks Davis To: Gary Jennejohn Message-ID: <20051207193824.GA22992@odin.ac.hmc.edu> References: <01a001c5faff$74c26ab0$1400a8c0@ilovefd533> <200512071240.jB7CexvJ025961@peedub.jennejohn.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EeQfGwPcQSOJBaQU" Content-Disposition: inline In-Reply-To: <200512071240.jB7CexvJ025961@peedub.jennejohn.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-hackers@freebsd.org Subject: Re: /usr/ports/sysutils/sge is broken ? for amd 64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 19:38:38 -0000 --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 07, 2005 at 01:40:59PM +0100, Gary Jennejohn wrote: >=20 > "gama" writes: > > I am trying to install Sun Grid Engine with FreeBSD5.4/amd64. > > It needs glibc-common-2.3.2-4.80.8.amd64.rpm > >=20 > > glibc-common-2.3.2-4.80.8.i386.rpm can be found in > > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/rpm/i386/8.0/ but amd= 64. > >=20 > > Where can I get glibc-common-2.3.2-4.80.8.amd64.rpm. > >=20 >=20 > See this URL: > http://lists.freebsd.org/pipermail/freebsd-ports/2005-November/027550.html >=20 > You could have this out for yourself by doing a simple search using e.g. > google. Additionaly, this has nothing to do with SGE except that SGE defaults to including Java API support (just disable DRMAA support if you don't need it) which in turn requires Linux support to bootstrap. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --EeQfGwPcQSOJBaQU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDlzorXY6L6fI4GtQRAp9HAKCloQA/BfgYrhVQBcmrfg6rj3ntIwCfSTJw 2qkO73hrsXZm/AOokQaQT5Y= =3N/d -----END PGP SIGNATURE----- --EeQfGwPcQSOJBaQU-- From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 7 21:51:04 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 444A816A42B for ; Wed, 7 Dec 2005 21:51:04 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66ADA43D73 for ; Wed, 7 Dec 2005 21:51:02 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id jB7Lox0J001845; Wed, 7 Dec 2005 15:51:00 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <43975926.1010302@centtech.com> Date: Wed, 07 Dec 2005 15:50:30 -0600 From: Eric Anderson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nate Lawson References: <4395BF04.50101@centtech.com> <43960F55.3010508@root.org> In-Reply-To: <43960F55.3010508@root.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1205/Wed Dec 7 08:00:48 2005 on mh1.centtech.com X-Virus-Status: Clean Cc: hackers@freebsd.org Subject: Re: scsi-target and the buffer cache X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 21:51:04 -0000 Nate Lawson wrote: > Eric Anderson wrote: > >> I'm curious about whether a target mode device would use the buffer >> cache or not. Here's a scenario: >> >> Host A: has fibre channel host adapter, in target mode, large memory >> pool, and another fiber channel host adapter connecting to fibre >> channel block device. >> Host B: Fibre channel host adapter, connecting to Host A. 'sees' the >> target mode block device created by Host A. >> >> Will Host A use the buffer cache to cache blocks between the real >> block device, and the shared target mode device? >> What about if Host A put a filesystem on the block device, created a >> single file the size of the filesystem, and shared that filesystem >> via a target mode device to Host B? >> What I'm wanting is a box (FreeBSD?) that can be placed between a >> fibre channel block device (like a RAID array), and a fibre channel >> host using that block device, and act as a block cache for that >> device, using the FreeBSD's memory. If it had a significant amount >> of memory, this could be very useful. > > > If you use the example scsi_target usermode > (usr/share/examples/scsi_target), then the buffer cache will be used > since its reads/writes are from usermode like normal. If you don't > want that behavior, you can set O_DIRECT in the open() call of the > backing store file. > > If you chose to modify the kernel side, you'd have to make sure your > accesses were through the VOP layer and then it would be cached. > > You should check to be sure the target mode performance meets your > expectations also. > I guess I would be using the user mode tool, unless there's another way? Your comment on performance also makes me a little worried about that now - do you think I would see a large performance hit? Thanks! Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 7 22:10:07 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E58416A424 for ; Wed, 7 Dec 2005 22:10:07 +0000 (GMT) (envelope-from danilo.asara@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF37943D55 for ; Wed, 7 Dec 2005 22:10:06 +0000 (GMT) (envelope-from danilo.asara@gmail.com) Received: by wproxy.gmail.com with SMTP id i23so445230wra for ; Wed, 07 Dec 2005 14:10:06 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:to:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=e0kG8t9GRQT4b/NIobEUkjtNCDWZHpqBJ7CSzcKTAiZep/Jibb1Kvh/nWUsER6FIiYUb7PwZCHnDB7DqW+IZ3LqU1gNhrEdQAcQhQcbxSU+Om/1ikKx/CME5DioR2snu9lR45pL46ECJLT23FzKkmUJYar1QOvQeLZl/DeHRKRQ= Received: by 10.65.145.9 with SMTP id x9mr2310839qbn; Wed, 07 Dec 2005 14:10:04 -0800 (PST) Received: from ?192.168.0.2? ( [62.101.126.222]) by mx.gmail.com with ESMTP id f18sm1068957qba.2005.12.07.14.10.04; Wed, 07 Dec 2005 14:10:04 -0800 (PST) From: Danilo Asara To: hackers@FreeBSD.org Content-Type: text/plain Date: Wed, 07 Dec 2005 23:09:54 +0100 Message-Id: <1133993394.1426.2.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 07 Dec 2005 22:13:03 +0000 Cc: Subject: Fatal trap 12: page fault while in kernel mode X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 22:10:07 -0000 danilo@resolza [~]$ uname -a FreeBSD resolza.fastwebnet.it 6.0-STABLE FreeBSD 6.0-STABLE #0: Fri Nov18 11:19:38 CET root@resolza.fastwebnet.it:/usr/obj/usr/src/sys/RESOLZA i386 danilo@resolza [~]$ root@resolza [/usr/crash]# kgdb kernel.debug.0 vmcore.0 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0500411 stack pointer = 0x28:0xef58fcac frame pointer = 0x28:0xef58fcdc 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 = 722 (artsd) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: kdb_backtrace(100,c2a83a80,28,ef58fc6c,c) at kdb_backtrace+0x29 panic(c06b2fec,c06d9f5b,0,fffff,c09b) at panic+0x114 trap_fatal(ef58fc6c,0,c2a83a80,c2890bb8,c) at trap_fatal+0x2ca trap_pfault(ef58fc6c,0,0) at trap_pfault+0x1d7 trap(8,28,28,c2ea9e70,c2a83a80) at trap+0x2fd calltrap() at calltrap+0x5 --- trap 0xc, eip = 0xc0500411, esp = 0xef58fcac, ebp = 0xef58fcdc --- kse_release(c2a83a80,ef58fd04,1,0,200292) at kse_release+0x165 syscall(3b,3b,3b,80f2100,81) at syscall+0x2bf Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (383, FreeBSD ELF32, kse_release), eip = 0x287d81af, esp = 0xbf9fef30, ebp = 0xbf9fef8c --- Uptime: 12h9m20s Dumping 1023 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 1023MB (261872 pages) 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:165 165 pcpu.h: No such file or directory. in pcpu.h (kgdb) where #0 doadump () at pcpu.h:165 #1 0xc05132bf in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399 #2 0xc0513615 in panic (fmt=0xc06b2fec "%s") at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xc068d8ca in trap_fatal (frame=0xef58fc6c, eva=0) at /usr/src/sys/i386/i386/trap.c:831 #4 0xc068d5d7 in trap_pfault (frame=0xef58fc6c, usermode=0, eva=0) at /usr/src/sys/i386/i386/trap.c:742 #5 0xc068d1ed in trap (frame= {tf_fs = 8, tf_es = 40, tf_ds = 40, tf_edi = -1024811408, tf_esi = -1029162368, tf_ebp = -279380772, tf_isp = -279380840, tf_ebx = -1026066384, tf_edx = -1029162368, tf_ecx = -1026066303, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1068497903, tf_cs = 32, tf_eflags = 2687622, tf_esp = -1036728832, tf_ss = 30}) at /usr/src/sys/i386/i386/trap.c:432 #6 0xc067aaca in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc0500411 in kse_release (td=0xc2a83a80, uap=0xef58fd04) at /usr/src/sys/kern/kern_kse.c:428 #8 0xc068dc0f in syscall (frame= {tf_fs = 59, tf_es = 59, tf_ds = 59, tf_edi = 135209216, tf_esi = 129, tf_ebp = -1080037492, tf_isp = -279380636, tf_ebx = 679326900, tf_edx = 3, tf_ecx = 31, tf_eax = 383, tf_trapno = 32, tf_err = 2, tf_eip = 679313839, tf_cs = 51, tf_eflags = 2097810, tf_esp = -1080037584, tf_ss = 59}) at /usr/src/sys/i386/i386/trap.c:976 #9 0xc067ab1f in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:200 #10 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 7 22:17:13 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D06E16A41F for ; Wed, 7 Dec 2005 22:17:13 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC9BC43D8C for ; Wed, 7 Dec 2005 22:17:00 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jB7MGpme060864; Wed, 7 Dec 2005 15:16:52 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43975F5F.5080901@samsco.org> Date: Wed, 07 Dec 2005 15:17:03 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <4395BF04.50101@centtech.com> <43960F55.3010508@root.org> <43975926.1010302@centtech.com> In-Reply-To: <43975926.1010302@centtech.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: hackers@freebsd.org, Nate Lawson Subject: Re: scsi-target and the buffer cache X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 22:17:13 -0000 Eric Anderson wrote: > Nate Lawson wrote: > >> Eric Anderson wrote: >> >>> I'm curious about whether a target mode device would use the buffer >>> cache or not. Here's a scenario: >>> >>> Host A: has fibre channel host adapter, in target mode, large memory >>> pool, and another fiber channel host adapter connecting to fibre >>> channel block device. >>> Host B: Fibre channel host adapter, connecting to Host A. 'sees' the >>> target mode block device created by Host A. >>> >>> Will Host A use the buffer cache to cache blocks between the real >>> block device, and the shared target mode device? >>> What about if Host A put a filesystem on the block device, created a >>> single file the size of the filesystem, and shared that filesystem >>> via a target mode device to Host B? >>> What I'm wanting is a box (FreeBSD?) that can be placed between a >>> fibre channel block device (like a RAID array), and a fibre channel >>> host using that block device, and act as a block cache for that >>> device, using the FreeBSD's memory. If it had a significant amount >>> of memory, this could be very useful. >> >> >> >> If you use the example scsi_target usermode >> (usr/share/examples/scsi_target), then the buffer cache will be used >> since its reads/writes are from usermode like normal. If you don't >> want that behavior, you can set O_DIRECT in the open() call of the >> backing store file. >> >> If you chose to modify the kernel side, you'd have to make sure your >> accesses were through the VOP layer and then it would be cached. >> >> You should check to be sure the target mode performance meets your >> expectations also. >> > > I guess I would be using the user mode tool, unless there's another > way? Your comment on performance also makes me a little worried about > that now - do you think I would see a large performance hit? > Thanks! > Eric > > The way the target mode stack works in FreeBSD is that the kernel provides some of the basic services, but the actual target emulator is meant to live in userland. The userland program responds to events from the kernel via the select interface. This generally works pretty well. However, it does mean that control has to cross the kernel-userland boundary at least once for every event. What I'd suggest doing is prototyping your target emulator in userland and evaluating the performance there, and then moving it to the kernel if you _really_ need more performance. Scott From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 8 00:48:06 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1BF5D16A41F for ; Thu, 8 Dec 2005 00:48:06 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73E6243D69 for ; Thu, 8 Dec 2005 00:48:05 +0000 (GMT) (envelope-from nate@root.org) Received: from [172.16.0.224] (fi01-84CBdd.tokyo.flets.isao.net [211.132.203.221]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id jB80lodu021436 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 7 Dec 2005 16:47:58 -0800 Message-ID: <439782AA.6000408@root.org> Date: Thu, 08 Dec 2005 09:47:38 +0900 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <4395BF04.50101@centtech.com> <43960F55.3010508@root.org> <43975926.1010302@centtech.com> <43975F5F.5080901@samsco.org> In-Reply-To: <43975F5F.5080901@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 08 Dec 2005 00:58:25 +0000 Cc: hackers@freebsd.org, Eric Anderson Subject: Re: scsi-target and the buffer cache X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 00:48:06 -0000 Scott Long wrote: > Eric Anderson wrote: > >> Nate Lawson wrote: >> >>> Eric Anderson wrote: >>> >>>> I'm curious about whether a target mode device would use the buffer >>>> cache or not. Here's a scenario: >>>> >>>> Host A: has fibre channel host adapter, in target mode, large memory >>>> pool, and another fiber channel host adapter connecting to fibre >>>> channel block device. >>>> Host B: Fibre channel host adapter, connecting to Host A. 'sees' >>>> the target mode block device created by Host A. >>>> >>>> Will Host A use the buffer cache to cache blocks between the real >>>> block device, and the shared target mode device? >>>> What about if Host A put a filesystem on the block device, created a >>>> single file the size of the filesystem, and shared that filesystem >>>> via a target mode device to Host B? >>>> What I'm wanting is a box (FreeBSD?) that can be placed between a >>>> fibre channel block device (like a RAID array), and a fibre channel >>>> host using that block device, and act as a block cache for that >>>> device, using the FreeBSD's memory. If it had a significant amount >>>> of memory, this could be very useful. >>> >>> >>> >>> >>> If you use the example scsi_target usermode >>> (usr/share/examples/scsi_target), then the buffer cache will be used >>> since its reads/writes are from usermode like normal. If you don't >>> want that behavior, you can set O_DIRECT in the open() call of the >>> backing store file. >>> >>> If you chose to modify the kernel side, you'd have to make sure your >>> accesses were through the VOP layer and then it would be cached. >>> >>> You should check to be sure the target mode performance meets your >>> expectations also. >>> >> >> I guess I would be using the user mode tool, unless there's another >> way? Your comment on performance also makes me a little worried about >> that now - do you think I would see a large performance hit? >> Thanks! >> Eric >> >> > > The way the target mode stack works in FreeBSD is that the kernel > provides some of the basic services, but the actual target emulator > is meant to live in userland. The userland program responds to > events from the kernel via the select interface. This generally > works pretty well. However, it does mean that control has to > cross the kernel-userland boundary at least once for every event. > > What I'd suggest doing is prototyping your target emulator in userland > and evaluating the performance there, and then moving it to the kernel > if you _really_ need more performance. Agree 100%. While having it in usermode means there are boundary crossings that increase per-transaction latency, the actual bulk data transfer is via zero-copy IO and you should be able to exceed the data transfer rates of several 10K RPM drives on decent hardware. -- Nate From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 8 04:32:34 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DEFC516A41F for ; Thu, 8 Dec 2005 04:32:33 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85F3743D5C for ; Thu, 8 Dec 2005 04:32:33 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.22] (andersonbox2.centtech.com [192.168.42.22]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id jB84WFZa007079; Wed, 7 Dec 2005 22:32:15 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <4397B731.6010308@centtech.com> Date: Wed, 07 Dec 2005 22:31:45 -0600 From: Eric Anderson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nate Lawson References: <4395BF04.50101@centtech.com> <43960F55.3010508@root.org> <43975926.1010302@centtech.com> <43975F5F.5080901@samsco.org> <439782AA.6000408@root.org> In-Reply-To: <439782AA.6000408@root.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1205/Wed Dec 7 08:00:48 2005 on mh2.centtech.com X-Virus-Status: Clean Cc: Scott Long , hackers@freebsd.org Subject: Re: scsi-target and the buffer cache X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 04:32:34 -0000 Nate Lawson wrote: > Scott Long wrote: > >> Eric Anderson wrote: >> >>> Nate Lawson wrote: >>> >>>> Eric Anderson wrote: >>>> >>>>> I'm curious about whether a target mode device would use the >>>>> buffer cache or not. Here's a scenario: >>>>> >>>>> Host A: has fibre channel host adapter, in target mode, large >>>>> memory pool, and another fiber channel host adapter connecting to >>>>> fibre channel block device. >>>>> Host B: Fibre channel host adapter, connecting to Host A. 'sees' >>>>> the target mode block device created by Host A. >>>>> >>>>> Will Host A use the buffer cache to cache blocks between the real >>>>> block device, and the shared target mode device? >>>>> What about if Host A put a filesystem on the block device, created >>>>> a single file the size of the filesystem, and shared that >>>>> filesystem via a target mode device to Host B? >>>>> What I'm wanting is a box (FreeBSD?) that can be placed between a >>>>> fibre channel block device (like a RAID array), and a fibre >>>>> channel host using that block device, and act as a block cache for >>>>> that device, using the FreeBSD's memory. If it had a significant >>>>> amount of memory, this could be very useful. >>>> >>>> >>>> >>>> >>>> >>>> If you use the example scsi_target usermode >>>> (usr/share/examples/scsi_target), then the buffer cache will be >>>> used since its reads/writes are from usermode like normal. If you >>>> don't want that behavior, you can set O_DIRECT in the open() call >>>> of the backing store file. >>>> >>>> If you chose to modify the kernel side, you'd have to make sure >>>> your accesses were through the VOP layer and then it would be cached. >>>> >>>> You should check to be sure the target mode performance meets your >>>> expectations also. >>>> >>> >>> I guess I would be using the user mode tool, unless there's another >>> way? Your comment on performance also makes me a little worried >>> about that now - do you think I would see a large performance hit? >>> Thanks! >>> Eric >>> >>> >> >> The way the target mode stack works in FreeBSD is that the kernel >> provides some of the basic services, but the actual target emulator >> is meant to live in userland. The userland program responds to >> events from the kernel via the select interface. This generally >> works pretty well. However, it does mean that control has to >> cross the kernel-userland boundary at least once for every event. >> >> What I'd suggest doing is prototyping your target emulator in userland >> and evaluating the performance there, and then moving it to the kernel >> if you _really_ need more performance. > > > Agree 100%. While having it in usermode means there are boundary > crossings that increase per-transaction latency, the actual bulk data > transfer is via zero-copy IO and you should be able to exceed the data > transfer rates of several 10K RPM drives on decent hardware. > Ok, great.. Now, will scsi_target work ok with raw devices, or only files? (although I'm not sure theres all that much difference really). Thanks!! Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 8 04:36:10 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1622E16A41F for ; Thu, 8 Dec 2005 04:36:10 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id D216F43D90 for ; Thu, 8 Dec 2005 04:35:57 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jB84ZjKU062536; Wed, 7 Dec 2005 21:35:45 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4397B82C.5020004@samsco.org> Date: Wed, 07 Dec 2005 21:35:56 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <4395BF04.50101@centtech.com> <43960F55.3010508@root.org> <43975926.1010302@centtech.com> <43975F5F.5080901@samsco.org> <439782AA.6000408@root.org> <4397B731.6010308@centtech.com> In-Reply-To: <4397B731.6010308@centtech.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: hackers@freebsd.org, Nate Lawson Subject: Re: scsi-target and the buffer cache X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 04:36:10 -0000 Eric Anderson wrote: > Nate Lawson wrote: > >> Scott Long wrote: >> >>> Eric Anderson wrote: >>> >>>> Nate Lawson wrote: >>>> >>>>> Eric Anderson wrote: >>>>> >>>>>> I'm curious about whether a target mode device would use the >>>>>> buffer cache or not. Here's a scenario: >>>>>> >>>>>> Host A: has fibre channel host adapter, in target mode, large >>>>>> memory pool, and another fiber channel host adapter connecting to >>>>>> fibre channel block device. >>>>>> Host B: Fibre channel host adapter, connecting to Host A. 'sees' >>>>>> the target mode block device created by Host A. >>>>>> >>>>>> Will Host A use the buffer cache to cache blocks between the real >>>>>> block device, and the shared target mode device? >>>>>> What about if Host A put a filesystem on the block device, created >>>>>> a single file the size of the filesystem, and shared that >>>>>> filesystem via a target mode device to Host B? >>>>>> What I'm wanting is a box (FreeBSD?) that can be placed between a >>>>>> fibre channel block device (like a RAID array), and a fibre >>>>>> channel host using that block device, and act as a block cache for >>>>>> that device, using the FreeBSD's memory. If it had a significant >>>>>> amount of memory, this could be very useful. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> If you use the example scsi_target usermode >>>>> (usr/share/examples/scsi_target), then the buffer cache will be >>>>> used since its reads/writes are from usermode like normal. If you >>>>> don't want that behavior, you can set O_DIRECT in the open() call >>>>> of the backing store file. >>>>> >>>>> If you chose to modify the kernel side, you'd have to make sure >>>>> your accesses were through the VOP layer and then it would be cached. >>>>> >>>>> You should check to be sure the target mode performance meets your >>>>> expectations also. >>>>> >>>> >>>> I guess I would be using the user mode tool, unless there's another >>>> way? Your comment on performance also makes me a little worried >>>> about that now - do you think I would see a large performance hit? >>>> Thanks! >>>> Eric >>>> >>>> >>> >>> The way the target mode stack works in FreeBSD is that the kernel >>> provides some of the basic services, but the actual target emulator >>> is meant to live in userland. The userland program responds to >>> events from the kernel via the select interface. This generally >>> works pretty well. However, it does mean that control has to >>> cross the kernel-userland boundary at least once for every event. >>> >>> What I'd suggest doing is prototyping your target emulator in userland >>> and evaluating the performance there, and then moving it to the kernel >>> if you _really_ need more performance. >> >> >> >> Agree 100%. While having it in usermode means there are boundary >> crossings that increase per-transaction latency, the actual bulk data >> transfer is via zero-copy IO and you should be able to exceed the data >> transfer rates of several 10K RPM drives on decent hardware. >> > > > Ok, great.. Now, will scsi_target work ok with raw devices, or only > files? (although I'm not sure theres all that much difference really). > > Thanks!! > Eric > > You can write your userland code to use whatever files or devices you want. Are you talking about the scs_target.c code in /usr/share/examples? That's just a skeletal example that you can use as a starting point for your own work. Scott Scott From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 8 04:45:34 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7C2216A41F for ; Thu, 8 Dec 2005 04:45:34 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BF4143D6D for ; Thu, 8 Dec 2005 04:45:34 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.22] (andersonbox2.centtech.com [192.168.42.22]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id jB84jXe5007221; Wed, 7 Dec 2005 22:45:33 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <4397BA4F.8060708@centtech.com> Date: Wed, 07 Dec 2005 22:45:03 -0600 From: Eric Anderson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <4395BF04.50101@centtech.com> <43960F55.3010508@root.org> <43975926.1010302@centtech.com> <43975F5F.5080901@samsco.org> <439782AA.6000408@root.org> <4397B731.6010308@centtech.com> <4397B82C.5020004@samsco.org> In-Reply-To: <4397B82C.5020004@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1205/Wed Dec 7 08:00:48 2005 on mh2.centtech.com X-Virus-Status: Clean Cc: hackers@freebsd.org, Nate Lawson Subject: Re: scsi-target and the buffer cache X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 04:45:35 -0000 Scott Long wrote: > Eric Anderson wrote: > >> Nate Lawson wrote: >> >>> Scott Long wrote: >>> >>>> Eric Anderson wrote: >>>> >>>>> Nate Lawson wrote: >>>>> >>>>>> Eric Anderson wrote: >>>>>> >>>>>>> I'm curious about whether a target mode device would use the >>>>>>> buffer cache or not. Here's a scenario: >>>>>>> >>>>>>> Host A: has fibre channel host adapter, in target mode, large >>>>>>> memory pool, and another fiber channel host adapter connecting >>>>>>> to fibre channel block device. >>>>>>> Host B: Fibre channel host adapter, connecting to Host A. >>>>>>> 'sees' the target mode block device created by Host A. >>>>>>> >>>>>>> Will Host A use the buffer cache to cache blocks between the >>>>>>> real block device, and the shared target mode device? >>>>>>> What about if Host A put a filesystem on the block device, >>>>>>> created a single file the size of the filesystem, and shared >>>>>>> that filesystem via a target mode device to Host B? >>>>>>> What I'm wanting is a box (FreeBSD?) that can be placed between >>>>>>> a fibre channel block device (like a RAID array), and a fibre >>>>>>> channel host using that block device, and act as a block cache >>>>>>> for that device, using the FreeBSD's memory. If it had a >>>>>>> significant amount of memory, this could be very useful. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> If you use the example scsi_target usermode >>>>>> (usr/share/examples/scsi_target), then the buffer cache will be >>>>>> used since its reads/writes are from usermode like normal. If >>>>>> you don't want that behavior, you can set O_DIRECT in the open() >>>>>> call of the backing store file. >>>>>> >>>>>> If you chose to modify the kernel side, you'd have to make sure >>>>>> your accesses were through the VOP layer and then it would be >>>>>> cached. >>>>>> >>>>>> You should check to be sure the target mode performance meets >>>>>> your expectations also. >>>>>> >>>>> >>>>> I guess I would be using the user mode tool, unless there's >>>>> another way? Your comment on performance also makes me a little >>>>> worried about that now - do you think I would see a large >>>>> performance hit? >>>>> Thanks! >>>>> Eric >>>>> >>>>> >>>> >>>> The way the target mode stack works in FreeBSD is that the kernel >>>> provides some of the basic services, but the actual target emulator >>>> is meant to live in userland. The userland program responds to >>>> events from the kernel via the select interface. This generally >>>> works pretty well. However, it does mean that control has to >>>> cross the kernel-userland boundary at least once for every event. >>>> >>>> What I'd suggest doing is prototyping your target emulator in userland >>>> and evaluating the performance there, and then moving it to the kernel >>>> if you _really_ need more performance. >>> >>> >>> >>> >>> Agree 100%. While having it in usermode means there are boundary >>> crossings that increase per-transaction latency, the actual bulk >>> data transfer is via zero-copy IO and you should be able to exceed >>> the data transfer rates of several 10K RPM drives on decent hardware. >>> >> >> >> Ok, great.. Now, will scsi_target work ok with raw devices, or only >> files? (although I'm not sure theres all that much difference really). >> >> Thanks!! >> Eric >> >> > > You can write your userland code to use whatever files or devices you > want. Are you talking about the scs_target.c code in > /usr/share/examples? That's just a skeletal example that you can use > as a starting point for your own work. Alright.. I was indeed talking about the example code, but I suppose it wouldn't be too hard to make it work with raw devices. Thanks for the help! Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 8 07:29:15 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC79C16A41F for ; Thu, 8 Dec 2005 07:29:15 +0000 (GMT) (envelope-from zhou.bowen@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7740D43D6E for ; Thu, 8 Dec 2005 07:29:08 +0000 (GMT) (envelope-from zhou.bowen@gmail.com) Received: by zproxy.gmail.com with SMTP id z31so538886nzd for ; Wed, 07 Dec 2005 23:29:07 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=uVKt9ssbVEzbGjFkj/YK3rPiwPdNYV2VCuUZ7Kxjvyfom0bf7X1IzrVyIhem/BAZloWEfFSWLt1ogyI85/tcOWc4E2ZBLSX+Y0xHw499LmKq685dK7dh5ojFOx6pTs8J8IhB+d+CrGSoBF+e+2FIcEPk+X42b6woLvbxVneVqCw= Received: by 10.65.216.1 with SMTP id t1mr2611750qbq; Wed, 07 Dec 2005 23:29:07 -0800 (PST) Received: by 10.65.43.18 with HTTP; Wed, 7 Dec 2005 23:29:07 -0800 (PST) Message-ID: <821419ca0512072329q4ad120c5g367dd2192b91eccd@mail.gmail.com> Date: Thu, 8 Dec 2005 15:29:07 +0800 From: Bowen Zhou To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Object reusement implementation in 6.0release: HELP Wanted!!! X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 07:29:16 -0000 hello, everyone. I need solutions to implement object reusement in FreeBSD6.0. What I want to do is to clean the content of data blocks before the re-allocation of them. Then where (in which function ) should I insert my cleaning code in order t= o fulfill the reusement of data blocks? thanks. From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 8 08:57:40 2005 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9535F16A420 for ; Thu, 8 Dec 2005 08:57:40 +0000 (GMT) (envelope-from joel@FreeBSD.org) Received: from av10-1-sn2.hy.skanova.net (av10-1-sn2.hy.skanova.net [81.228.8.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7DF9B43D8F for ; Thu, 8 Dec 2005 08:57:31 +0000 (GMT) (envelope-from joel@FreeBSD.org) Received: by av10-1-sn2.hy.skanova.net (Postfix, from userid 502) id 117F137F7A; Thu, 8 Dec 2005 09:57:29 +0100 (CET) Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net [81.228.8.92]) by av10-1-sn2.hy.skanova.net (Postfix) with ESMTP id DD544381EC; Thu, 8 Dec 2005 09:57:29 +0100 (CET) Received: from t3o955p111.telia.com (t3o955p111.telia.com [195.252.53.111]) by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id 1361237E4B; Thu, 8 Dec 2005 09:57:28 +0100 (CET) From: Joel Dahl To: current@FreeBSD.org Content-Type: text/plain Date: Thu, 08 Dec 2005 09:55:01 +0100 Message-Id: <1134032101.664.22.camel@dude.automatvapen.se> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: hackers@FreeBSD.org Subject: FreeBSD list of projects for volunteers X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 08:57:40 -0000 Hi all, As some of you may have noticed, we've added a new section to the website, which contains a lot of interesting projects and ideas that volunteers and developers are encouraged to evaluate and work on. Some of these projects are simple, and someone just needs to spend some time on them and do the work, some are harder, intended for junior kernel hackers. This should also serve as a good starting point for people that would like to contribute to FreeBSD and perhaps become committers in the future. You can find the list here: http://www.freebsd.org/projects/ideas/ -- Joel - joel at FreeBSD dot org From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 8 08:16:29 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F61516A41F for ; Thu, 8 Dec 2005 08:16:29 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id C710A43D79 for ; Thu, 8 Dec 2005 08:16:19 +0000 (GMT) (envelope-from nate@root.org) Received: from [172.16.0.224] (fi01-84CBdd.tokyo.flets.isao.net [211.132.203.221]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id jB88GKdu025083 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 8 Dec 2005 00:16:23 -0800 Message-ID: <4397EBC7.9030105@root.org> Date: Thu, 08 Dec 2005 17:16:07 +0900 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <4395BF04.50101@centtech.com> <43960F55.3010508@root.org> <43975926.1010302@centtech.com> <43975F5F.5080901@samsco.org> <439782AA.6000408@root.org> <4397B731.6010308@centtech.com> <4397B82C.5020004@samsco.org> In-Reply-To: <4397B82C.5020004@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 08 Dec 2005 12:27:28 +0000 Cc: hackers@freebsd.org, Eric Anderson Subject: Re: scsi-target and the buffer cache X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 08:16:29 -0000 Scott Long wrote: > Eric Anderson wrote: > >> Nate Lawson wrote: >>> Agree 100%. While having it in usermode means there are boundary >>> crossings that increase per-transaction latency, the actual bulk data >>> transfer is via zero-copy IO and you should be able to exceed the >>> data transfer rates of several 10K RPM drives on decent hardware. >> >> Ok, great.. Now, will scsi_target work ok with raw devices, or only >> files? (although I'm not sure theres all that much difference really). >> > > You can write your userland code to use whatever files or devices you > want. Are you talking about the scs_target.c code in > /usr/share/examples? That's just a skeletal example that you can use > as a starting point for your own work. No, it's not just a skeletal example. You can point it at a raw device as the backing store file and it will work as a block device (i.e. RBC command set). It has been tested as working at least moderately fast over SCSI, FC, and firewire. -- Nate From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 8 17:12:51 2005 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C615B16A41F for ; Thu, 8 Dec 2005 17:12:51 +0000 (GMT) (envelope-from pfgshield-freebsd@yahoo.com) Received: from web32915.mail.mud.yahoo.com (web32915.mail.mud.yahoo.com [68.142.206.62]) by mx1.FreeBSD.org (Postfix) with SMTP id 1D10F43D4C for ; Thu, 8 Dec 2005 17:12:43 +0000 (GMT) (envelope-from pfgshield-freebsd@yahoo.com) Received: (qmail 78442 invoked by uid 60001); 8 Dec 2005 17:12:42 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type; b=XZIvUiDMSMrfitYHsap7aOfZ57xlE+KWNE4rfYkl/8xjmi0e+H/fJKTJudDa+zstfd+7vM6wDFNTANdmLpty7Pbehvegj5m5ts1gj7nf8eWb3HFIDv2Br+uP0eJdWnNG2VD+l4F0fMzmC53eUjmHTPNZUUC8wXIFUnfbS3OllH0= ; Message-ID: <20051208171242.78440.qmail@web32915.mail.mud.yahoo.com> Received: from [69.79.60.158] by web32915.mail.mud.yahoo.com via HTTP; Thu, 08 Dec 2005 18:12:42 CET Date: Thu, 8 Dec 2005 18:12:42 +0100 (CET) From: To: freebsd-emulation@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailman-Approved-At: Thu, 08 Dec 2005 17:28:25 +0000 Cc: freebsd-hackers@FreeBSD.org Subject: OpenSolaris emulation? (was Re: FreeBSD list of projects for volunteers) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pfgshield-freebsd@yahoo.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 17:12:51 -0000 (sorry for cross-posting, in the future this seems better suited for emulation@ ) Hi; I didn't see any interest for this on the website but perhaps we should be working on improving our SVR4 emulation now that OpenSolaris is available. Possible tasks include: - Updating the emulator wrt NetBSD. - Packaging OpenSolaris binary libraries: it seems like the license might require us setting some of it as RESTRICTED though. - General testing on sparc64, i386 or amd64 platforms. - Porting ZFS would be great ;-). Pedro ___________________________________ Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB http://mail.yahoo.it From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 8 19:23:57 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2919816A41F for ; Thu, 8 Dec 2005 19:23:57 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3198643D7E for ; Thu, 8 Dec 2005 19:23:47 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id jB8JNi8P062642; Thu, 8 Dec 2005 11:23:44 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id jB8JNhOF062641; Thu, 8 Dec 2005 11:23:43 -0800 (PST) (envelope-from jmg) Date: Thu, 8 Dec 2005 11:23:43 -0800 From: John-Mark Gurney To: Bowen Zhou Message-ID: <20051208192343.GT55657@funkthat.com> Mail-Followup-To: Bowen Zhou , freebsd-hackers@freebsd.org References: <821419ca0512072329q4ad120c5g367dd2192b91eccd@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <821419ca0512072329q4ad120c5g367dd2192b91eccd@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-hackers@freebsd.org Subject: Re: Object reusement implementation in 6.0release: HELP Wanted!!! X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 19:23:57 -0000 Bowen Zhou wrote this message on Thu, Dec 08, 2005 at 15:29 +0800: > I need solutions to implement object reusement in FreeBSD6.0. > > What I want to do is to clean the content of data blocks before the > re-allocation of them. > > Then where (in which function ) should I insert my cleaning code in order to > fulfill the reusement of data blocks? If you are talking about in kernel land, take a look at zone(9).. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 8 22:56:48 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C89116A41F for ; Thu, 8 Dec 2005 22:56:48 +0000 (GMT) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [83.98.131.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 215BA43D7E for ; Thu, 8 Dec 2005 22:56:45 +0000 (GMT) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 67A621702B; Thu, 8 Dec 2005 23:56:44 +0100 (CET) Date: Thu, 8 Dec 2005 23:56:44 +0100 From: Ed Schouten To: FreeBSD Hackers Message-ID: <20051208225644.GJ15719@hoeg.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6lCXDTVICvIQMz0h" Content-Disposition: inline User-Agent: Mutt/1.5.11 X-Mailman-Approved-At: Thu, 08 Dec 2005 23:01:05 +0000 Cc: Subject: [WIP] uhid(4): Support for the Microsoft Xbox360 gamepad X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 22:56:48 -0000 --6lCXDTVICvIQMz0h Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, Last week I heard that Microsoft's new Xbox360 uses regular USB connectors for their gamepads. Because the guys at Xbox-Linux.org already wrote a driver for Linux, I decided to buy one and write a FreeBSD driver for it. The Xbox360 gamepad is like any normal HID gamepad, except that it has been slightly crippled by Microsoft: - They don't use the regular HID interface class, but the vendor specific class in combination with an interface subclass. - Their device does not contain a HID report descriptor. The first problem was easy to solve; I just changed the USB_MATCH code to accept the UICLASS_VENDOR in combination with the interface subclass and interface protocol. Limiting vendor and product ID's should be avoided because that would block third party gamepads. The second problem was a little trickier because I had no experience with writing report descriptors. After taking a look at examples and reading documents at usb.org, I hacked one together. It's quite nice the FreeBSD driver was somewhat prepared for custom report descriptors (the Wacom Graphire gets a custom report descriptor for example). The result can be found here: http://g-rave.nl/files/xbox/freebsd-xbox360-gamepad.diff There are only some small unfinished parts though: - I don't know the output format state; I cannot control the rumbles or the LEDs on the gamepad (I constantly see green leds flashing) - For some reason, I can only read data when polling the gamepad. `usbhidctl -f -al` does not return any output. Useful hints would really be appreciated; I'm not a real wizard when it comes to USB ;-) Yours, --=20 Ed Schouten WWW: http://g-rave.nl/ --6lCXDTVICvIQMz0h Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDmLosmVI4SHXwmhERAiUTAKDSWkd/VvXandrMDUo3T3Ih+iM8ewCgwQTs fSC4YHRh9SQjFBeXtAHwOJw= =lNtj -----END PGP SIGNATURE----- --6lCXDTVICvIQMz0h-- From owner-freebsd-hackers@FreeBSD.ORG Thu Dec 8 23:28:26 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DAEE16A438 for ; Thu, 8 Dec 2005 23:28:26 +0000 (GMT) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [83.98.131.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EAB643D60 for ; Thu, 8 Dec 2005 23:28:21 +0000 (GMT) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id B154717035; Fri, 9 Dec 2005 00:28:08 +0100 (CET) Date: Fri, 9 Dec 2005 00:28:08 +0100 From: Ed Schouten To: FreeBSD Hackers Message-ID: <20051208232808.GK15719@hoeg.nl> References: <20051208225644.GJ15719@hoeg.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Ublo+h3cBgJ33ahC" Content-Disposition: inline In-Reply-To: <20051208225644.GJ15719@hoeg.nl> User-Agent: Mutt/1.5.11 X-Mailman-Approved-At: Thu, 08 Dec 2005 23:40:51 +0000 Cc: Subject: Re: [WIP] uhid(4): Support for the Microsoft Xbox360 gamepad X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 23:28:26 -0000 --Ublo+h3cBgJ33ahC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Sorry for replying to myself, but... * Ed Schouten wrote: > - For some reason, I can only read data when polling the gamepad. > `usbhidctl -f -al` does not return any output. I've just fixed this. It seems that there were some trailing unused bytes in the device input report which caused usbhidctl to block. I just played a game of Neverball with the gamepad and it works like a charm.=20 Yours, --=20 Ed Schouten WWW: http://g-rave.nl/ --Ublo+h3cBgJ33ahC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDmMGImVI4SHXwmhERAhi6AJ9pK3nsBzWmjUwOJaoPPJrY+VYorwCfegjV YiVvKARoxKKdWDrShIvYmFE= =AFU6 -----END PGP SIGNATURE----- --Ublo+h3cBgJ33ahC-- From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 9 01:06:21 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E004E16A420 for ; Fri, 9 Dec 2005 01:06:21 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6FB243D4C for ; Fri, 9 Dec 2005 01:06:16 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id jB916G3n059766 for ; Thu, 8 Dec 2005 17:06:16 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id jB916GBT059765 for freebsd-hackers@freebsd.org; Thu, 8 Dec 2005 17:06:16 -0800 (PST) (envelope-from sgk) Date: Thu, 8 Dec 2005 17:06:16 -0800 From: Steve Kargl To: freebsd-hackers@freebsd.org Message-ID: <20051209010616.GA59667@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Fri, 09 Dec 2005 01:25:11 +0000 Subject: sysctl, HW_PHYSMEM, and crippled gcc X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 01:06:22 -0000 Anyone have any insight into fixing gcc to make better use of system memory on systems with more than 4 GB. It appears that libiberty/physmem.c tries to use sysctl() to determine the amount of physical memory in a system. { /* This works on *bsd and darwin. */ unsigned int physmem; size_t len = sizeof physmem; static int mib[2] = { CTL_HW, HW_PHYSMEM }; if (sysctl (mib, ARRAY_SIZE (mib), &physmem, &len, NULL, 0) == 0 && len == sizeof (physmem)) return (double) physmem; } This works if you have less than 4GB because of the unsigned int physmem. I have 12 GB, which of course, when expanded to the number of bytes doesn't fit into a unsigned int physmem. What is the ramification? Well, gcc uses this estimate of memory to size internal parameters. troutmask:sgk[259] gcc -v h.c Using built-in specs. Configured with: FreeBSD/amd64 system compiler Thread model: posix gcc version 3.4.4 [FreeBSD] 20050518 GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096 In particular, ggc-min-heapsize=4096 is ridiculously small for a system with 12 GB of memory. -- Steve From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 9 01:37:47 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D44B016A41F for ; Fri, 9 Dec 2005 01:37:47 +0000 (GMT) (envelope-from zhou.bowen@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F7A543D49 for ; Fri, 9 Dec 2005 01:37:44 +0000 (GMT) (envelope-from zhou.bowen@gmail.com) Received: by wproxy.gmail.com with SMTP id i23so736308wra for ; Thu, 08 Dec 2005 17:37:44 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Z5Lhb6HTcyKlSj0y1d58gCXAOGc+9+JQombbw17RWW1aH9DOpgg4Wyu3g8vH3Gr2aY7q6UNT2mmb0ZkYesRCszYA8bONZTHEjT8kT5AXeGoP/qRD2NfP7R0zapAC5pr/VNJMwRO8OtID6QpI5qps2q85V9hDNljncBr7wthRmIA= Received: by 10.64.253.8 with SMTP id a8mr3399299qbi; Thu, 08 Dec 2005 17:37:43 -0800 (PST) Received: by 10.65.43.18 with HTTP; Thu, 8 Dec 2005 17:37:43 -0800 (PST) Message-ID: <821419ca0512081737j1e2f1186r9931b747f1dc0691@mail.gmail.com> Date: Fri, 9 Dec 2005 09:37:43 +0800 From: Bowen Zhou To: Andrey Simonenko In-Reply-To: <20051208120001.GA921@pm513-1.comsys.ntu-kpi.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline References: <821419ca0512072329q4ad120c5g367dd2192b91eccd@mail.gmail.com> <20051208120001.GA921@pm513-1.comsys.ntu-kpi.kiev.ua> Cc: freebsd-hackers@freebsd.org Subject: Re: Object reusement implementation in 6.0release: HELP Wanted!!! X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 01:37:48 -0000 VGhhbmtzIGZvciBjb25jZXJuaW5nIG15IHF1ZXN0aW9uLgoKSSBuZWVkIHRvIGNsZWFuIGFsbCB0 aGUgZGF0YSBibG9ja3Mgb2YgYSBpbm9kZSwgaW5jbHVkaW5nIGRpcmVjdCBkaXNrCmJsb2Nrcywg aW5kaXJlY3QgZGlzayBibG9ja3MgYW5kIGV4dGVybmFsIGF0dHJpYnV0ZXMgYmxvY2tzLgoKSSBo YXZlIHRyaWVkIHRvIGluc2VydCBjbGVhbmluZyBjb2RlIGludG8KZmZzX2Jsa2ZyZWUoL3Vmcy9m ZnMvZmZzX2FsbG9jLmMpLCBidXQgdGhlIHJlc3VsdCB3YXMgbm90IGdvb2QgZW5vdWdoLgpBZnRl ciBjb21waWxlZCB0aGUga2VybmVsKEdFTkVSSUMpIHdpdGggbXkgY2xlYW5pbmcgY29kZSBhbmQg cmVzdGFydGVkCnRoZSBjb21wdXRlciwgSSBmb3VuZCB0aGF0IHNvbWUgZGF0YSBibG9ja3Mgb2Yg bm9ybWFsIGZpbGVzIHdoaWNoIGhhdmUKbm90IGJlZW4gZGVsZXRlZCB5ZXQgZGlzYXBwZWFyZWQg cmFuZG9tbHkuCgpUaGUgZm9sbG93aW5nIGlzIHRoZSBjb2RlIEkgaGF2ZSBpbnNlcnRlZCBpbnRv IGZmc19ibGtmcmVlKGluY2x1ZGluZwp0aGUgYmVnaW5uaW5nIHBhcnQgb2YgdGhlIG9yaWdpbmFs IGZ1bmN0aW9uKToKCnZvaWQKZmZzX2Jsa2ZyZWUodW1wLCBmcywgZGV2dnAsIGJubywgc2l6ZSwg aW51bSkKCXN0cnVjdCB1ZnNtb3VudCAqdW1wOwoJc3RydWN0IGZzICpmczsKCXN0cnVjdCB2bm9k ZSAqZGV2dnA7Cgl1ZnMyX2RhZGRyX3QgYm5vOwoJbG9uZyBzaXplOwoJaW5vX3QgaW51bTsKewoJ c3RydWN0IGNnICpjZ3A7CglzdHJ1Y3QgYnVmICpicDsKCXN0cnVjdCBidWYgKmJwMTsKCXVmczFf ZGFkZHJfdCBmcmFnbm8sIGNnYm5vOwoJdWZzMl9kYWRkcl90IGNnYmxrbm87CglpbnQgaSwgY2cs IGJsaywgZnJhZ3MsIGJiYXNlOwoJdV9pbnQ4X3QgKmJsa3NmcmVlOwoJc3RydWN0IGNkZXYgKmRl djsKCgkvKm9iamVjdCByZXVzZSBzdGFydHMgaGVyZS4qLwoJaWYoYnJlYWQoZGV2dnAsIGZzYnRv ZGIoZnMsIGJubyksIHNpemUsIE5PQ1JFRCwgJmJwMSkpewoJCWJyZWxzZShicDEpOwoJCXJldHVy bjsKCQl9CgliemVybyhicDEtPmJfZGF0YSwgc2l6ZSk7CgliZHdyaXRlKGJwMSk7CgkvKm9iamVj dCByZXVzZSBlbmRzIGhlcmUuKi8KLi4uLgoKSSBndWVzcyB0aGVyZSBhcmUgZXJyb3JzIGluIGVp dGhlciBteSBjbGVhbmluZyBjb2RlIG9yIHRoZSBwbGFjZSBJCmluc2VydGVkIHRoZXNlIGNvZGUu CgpBbnkgc3VnZ2VzdGlvbiBpcyB3ZWxjb21lLgoKT24gMTIvOC8wNSwgQW5kcmV5IFNpbW9uZW5r byA8c2ltb25AY29tc3lzLm50dS1rcGkua2lldi51YT4gd3JvdGU6Cj4gT24gVGh1LCBEZWMgMDgs IDIwMDUgYXQgMDM6Mjk6MDdQTSArMDgwMCwgQm93ZW4gWmhvdSB3cm90ZToKPiA+IGhlbGxvLCBl dmVyeW9uZS4KPiA+Cj4gPiBJIG5lZWQgc29sdXRpb25zIHRvIGltcGxlbWVudCBvYmplY3QgcmV1 c2VtZW50IGluIEZyZWVCU0Q2LjAuCj4gPgo+ID4gV2hhdCBJIHdhbnQgdG8gZG8gaXMgdG8gY2xl YW4gdGhlIGNvbnRlbnQgb2YgZGF0YSBibG9ja3MgYmVmb3JlIHRoZQo+ID4gcmUtYWxsb2NhdGlv biBvZiB0aGVtLgo+ID4KPiA+IFRoZW4gd2hlcmUgKGluIHdoaWNoIGZ1bmN0aW9uICkgc2hvdWxk IEkgaW5zZXJ0IG15IGNsZWFuaW5nIGNvZGUgaW4gb3JkZXIgdG8KPiA+IGZ1bGZpbGwgdGhlIHJl dXNlbWVudCBvZiBkYXRhIGJsb2Nrcz8KPgo+IEFib3V0IHdoaWNoIGRhdGFibG9jayBhcmUgeW91 IGFza2luZz8KPgo= From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 9 02:12:33 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C5F216A431; Fri, 9 Dec 2005 02:12:33 +0000 (GMT) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.swip.net [212.247.154.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id F399643D5C; Fri, 9 Dec 2005 02:12:14 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: Y1QAsIk9O44SO+J/q9KNyQ== X-Cloudmark-Score: 0.000000 [] Received: from mp-216-88-125.daxnet.no ([193.216.88.125] verified) by mailfe07.swip.net (CommuniGate Pro SMTP 5.0.2) with ESMTP id 41217186; Fri, 09 Dec 2005 03:12:07 +0100 From: Hans Petter Selasky To: freebsd-hackers@freebsd.org, freebsd-usb@freebsd.org, Ed Schouten Date: Fri, 9 Dec 2005 03:13:26 +0100 User-Agent: KMail/1.7 References: <20051208225644.GJ15719@hoeg.nl> In-Reply-To: <20051208225644.GJ15719@hoeg.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512090313.27392.hselasky@c2i.net> Cc: Subject: Re: [WIP] uhid(4): Support for the Microsoft Xbox360 gamepad X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hselasky@c2i.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 02:12:33 -0000 On Thursday 08 December 2005 23:56, Ed Schouten wrote: > Hello, > > Last week I heard that Microsoft's new Xbox360 uses regular USB > connectors for their gamepads. Because the guys at Xbox-Linux.org > already wrote a driver for Linux, I decided to buy one and write a > FreeBSD driver for it. > > The Xbox360 gamepad is like any normal HID gamepad, except that it has > been slightly crippled by Microsoft: > > - They don't use the regular HID interface class, but the vendor > specific class in combination with an interface subclass. > - Their device does not contain a HID report descriptor. > > The first problem was easy to solve; I just changed the USB_MATCH code > to accept the UICLASS_VENDOR in combination with the interface subclass > and interface protocol. Limiting vendor and product ID's should be > avoided because that would block third party gamepads. > > The second problem was a little trickier because I had no experience > with writing report descriptors. After taking a look at examples and > reading documents at usb.org, I hacked one together. It's quite nice the > FreeBSD driver was somewhat prepared for custom report descriptors (the > Wacom Graphire gets a custom report descriptor for example). > > The result can be found here: > > http://g-rave.nl/files/xbox/freebsd-xbox360-gamepad.diff > > There are only some small unfinished parts though: > > - I don't know the output format state; I cannot control the rumbles or > the LEDs on the gamepad (I constantly see green leds flashing) > - For some reason, I can only read data when polling the gamepad. > `usbhidctl -f -al` does not return any output. > > Useful hints would really be appreciated; I'm not a real wizard when it > comes to USB ;-) > > Yours, Hi, Maybe when you have tested this patch more, then make a PR, see "man send-pr", using "Category: usb", so that it does not get lost. --HPS From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 9 04:05:55 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69E5816A41F for ; Fri, 9 Dec 2005 04:05:55 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8721543D53 for ; Fri, 9 Dec 2005 04:05:54 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id jB945moE082586; Thu, 8 Dec 2005 22:05:48 -0600 (CST) (envelope-from dan) Date: Thu, 8 Dec 2005 22:05:48 -0600 From: Dan Nelson To: Steve Kargl Message-ID: <20051209040548.GD95420@dan.emsphone.com> References: <20051209010616.GA59667@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051209010616.GA59667@troutmask.apl.washington.edu> X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org Subject: Re: sysctl, HW_PHYSMEM, and crippled gcc X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 04:05:55 -0000 In the last episode (Dec 08), Steve Kargl said: > Anyone have any insight into fixing gcc to make better use of system > memory on systems with more than 4 GB. It appears that > libiberty/physmem.c tries to use sysctl() to determine the amount of > physical memory in a system. > > { /* This works on *bsd and darwin. */ > unsigned int physmem; > size_t len = sizeof physmem; > static int mib[2] = { CTL_HW, HW_PHYSMEM }; > > if (sysctl (mib, ARRAY_SIZE (mib), &physmem, &len, NULL, 0) == 0 > && len == sizeof (physmem)) > return (double) physmem; > } > > This works if you have less than 4GB because of the unsigned int > physmem. I have 12 GB, which of course, when expanded to the number > of bytes doesn't fit into a unsigned int physmem. physmem is actually an unsigned long, not an unsigned int, so on amd64 that sysctl call should fail anyway (amd64 is LP64, so a long won't fit into an int). > What is the ramification? Well, gcc uses this estimate of > memory to size internal parameters. > > troutmask:sgk[259] gcc -v h.c > Using built-in specs. > Configured with: FreeBSD/amd64 system compiler > Thread model: posix > gcc version 3.4.4 [FreeBSD] 20050518 > GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096 > > In particular, ggc-min-heapsize=4096 is ridiculously small for a > system with 12 GB of memory. On all my FreeBSD boxes from 128MB to 1GB of RAM, I get the exact same heuristic values as you, so I'm not sure whether the code works at all. I seem to remember having the opposite problem on a memory-limited machine which insisted in allocating a relatively huge percentage of RAM for a sort, and gnu sort uses the same physmem() call for its dynamic sizing. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 9 15:33:31 2005 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9540016A420; Fri, 9 Dec 2005 15:33:31 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EB4243DBB; Fri, 9 Dec 2005 15:32:24 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id DB6EC1A3C25; Fri, 9 Dec 2005 07:32:18 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 06F8251593; Fri, 9 Dec 2005 10:32:17 -0500 (EST) Date: Fri, 9 Dec 2005 10:32:17 -0500 From: Kris Kennaway To: pfgshield-freebsd@yahoo.com Message-ID: <20051209153217.GA53316@xor.obsecurity.org> References: <20051208171242.78440.qmail@web32915.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0OAP2g/MAC+5xKAE" Content-Disposition: inline In-Reply-To: <20051208171242.78440.qmail@web32915.mail.mud.yahoo.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@FreeBSD.org, freebsd-emulation@FreeBSD.org Subject: Re: OpenSolaris emulation? (was Re: FreeBSD list of projects for volunteers) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 15:33:31 -0000 --0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 08, 2005 at 06:12:42PM +0100, pfgshield-freebsd@yahoo.com wrote: > (sorry for cross-posting, in the future this seems better suited for emul= ation@ > ) >=20 > Hi; >=20 > I didn't see any interest for this on the website but perhaps we should be > working on improving our SVR4 emulation now that OpenSolaris is available. > Possible tasks include: >=20 > - Updating the emulator wrt NetBSD. > - Packaging OpenSolaris binary libraries: it seems like the license might > require us setting some of it as RESTRICTED though. > - General testing on sparc64, i386 or amd64 platforms. > - Porting ZFS would be great ;-). Sounds great, keep us informed! Kris --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDmaOBWry0BWjoQKURAimlAJ0R3TsjQ3SiSBgsjMRgLR2K6h83MACg2qjo mocQe/g8l4cEzY90/g4/lj8= =fN+o -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE-- From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 9 19:25:34 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EAC0F16A41F for ; Fri, 9 Dec 2005 19:25:34 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0826343D5A for ; Fri, 9 Dec 2005 19:25:33 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (envelope-from xdivac02@eva.fit.vutbr.cz) (8.13.4/8.13.3) with ESMTP id jB9JPTbt042911 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Fri, 9 Dec 2005 20:25:29 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.4/8.13.3/Submit) id jB9JPTr9042910 for freebsd-hackers@freebsd.org; Fri, 9 Dec 2005 20:25:29 +0100 (CET) Date: Fri, 9 Dec 2005 20:25:29 +0100 From: Divacky Roman To: freebsd-hackers@freebsd.org Message-ID: <20051209192529.GA40894@stud.fit.vutbr.cz> References: <20051209010616.GA59667@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051209010616.GA59667@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.49 on 147.229.10.14 Subject: Re: sysctl, HW_PHYSMEM, and crippled gcc X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 19:25:35 -0000 On Thu, Dec 08, 2005 at 05:06:16PM -0800, Steve Kargl wrote: > Anyone have any insight into fixing gcc to make better > use of system memory on systems with more than 4 GB. > It appears that libiberty/physmem.c tries to use sysctl() > to determine the amount of physical memory in a system. > > { /* This works on *bsd and darwin. */ > unsigned int physmem; > size_t len = sizeof physmem; > static int mib[2] = { CTL_HW, HW_PHYSMEM }; > > if (sysctl (mib, ARRAY_SIZE (mib), &physmem, &len, NULL, 0) == 0 > && len == sizeof (physmem)) > return (double) physmem; > } > > This works if you have less than 4GB because of the unsigned > int physmem. I have 12 GB, which of course, when expanded > to the number of bytes doesn't fit into a unsigned int physmem. > > What is the ramification? Well, gcc uses this estimate of > memory to size internal parameters. > > troutmask:sgk[259] gcc -v h.c > Using built-in specs. > Configured with: FreeBSD/amd64 system compiler > Thread model: posix > gcc version 3.4.4 [FreeBSD] 20050518 > GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096 > > In particular, ggc-min-heapsize=4096 is ridiculously small for a > system with 12 GB of memory. the code works here (512M of memory)... dont know about the ifdefs its surrounded by.. if you manually rewrite the physmem to some bigger value - does it have any effect on performance of gcc? roman From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 9 20:04:48 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 705A216A41F for ; Fri, 9 Dec 2005 20:04:48 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from vms048pub.verizon.net (vms048pub.verizon.net [206.46.252.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03AA243D5D for ; Fri, 9 Dec 2005 20:04:48 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from vms070.mailsrvcs.net ([192.168.1.3]) by vms048.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IR800LZUYC1EXF1@vms048.mailsrvcs.net> for freebsd-hackers@freebsd.org; Fri, 09 Dec 2005 14:02:25 -0600 (CST) Date: Fri, 09 Dec 2005 14:02:25 -0600 (CST) From: Sergey Babkin To: Divacky Roman , freebsd-hackers@freebsd.org Message-id: <10939303.1134158545675.JavaMail.root@vms070.mailsrvcs.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Mailman-Approved-At: Fri, 09 Dec 2005 20:39:13 +0000 Cc: Subject: Re: Re: sysctl, HW_PHYSMEM, and crippled gcc X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: babkin@users.sf.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 20:04:48 -0000 >From: Divacky Roman >On Thu, Dec 08, 2005 at 05:06:16PM -0800, Steve Kargl wrote: >> Anyone have any insight into fixing gcc to make better >> use of system memory on systems with more than 4 GB. >> It appears that libiberty/physmem.c tries to use sysctl() >> to determine the amount of physical memory in a system. >> >> { /* This works on *bsd and darwin. */ >> unsigned int physmem; >> size_t len = sizeof physmem; >> static int mib[2] = { CTL_HW, HW_PHYSMEM }; >> >> if (sysctl (mib, ARRAY_SIZE (mib), &physmem, &len, NULL, 0) == 0 >> && len == sizeof (physmem)) >> return (double) physmem; >> } >> >> This works if you have less than 4GB because of the unsigned >> int physmem. I have 12 GB, which of course, when expanded >> to the number of bytes doesn't fit into a unsigned int physmem. >> In particular, ggc-min-heapsize=4096 is ridiculously small for a >> system with 12 GB of memory. > >the code works here (512M of memory)... dont know about the ifdefs its >surrounded by.. I guess you've confused M and G :-) The point is that it breaks with over 4G of memory. -SB From owner-freebsd-hackers@FreeBSD.ORG Fri Dec 9 20:09:22 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3567616A41F for ; Fri, 9 Dec 2005 20:09:22 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id B486443D4C for ; Fri, 9 Dec 2005 20:09:21 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id jB9K9IX9030296; Fri, 9 Dec 2005 12:09:18 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id jB9K9EcI030295; Fri, 9 Dec 2005 12:09:14 -0800 (PST) (envelope-from sgk) Date: Fri, 9 Dec 2005 12:09:14 -0800 From: Steve Kargl To: Dan Nelson Message-ID: <20051209200914.GA30276@troutmask.apl.washington.edu> References: <20051209010616.GA59667@troutmask.apl.washington.edu> <20051209040548.GD95420@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051209040548.GD95420@dan.emsphone.com> User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Fri, 09 Dec 2005 20:39:27 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: sysctl, HW_PHYSMEM, and crippled gcc X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 20:09:22 -0000 On Thu, Dec 08, 2005 at 10:05:48PM -0600, Dan Nelson wrote: > In the last episode (Dec 08), Steve Kargl said: > > Anyone have any insight into fixing gcc to make better use of system > > memory on systems with more than 4 GB. It appears that > > libiberty/physmem.c tries to use sysctl() to determine the amount of > > physical memory in a system. > > > > { /* This works on *bsd and darwin. */ > > unsigned int physmem; > > size_t len = sizeof physmem; > > static int mib[2] = { CTL_HW, HW_PHYSMEM }; > > > > if (sysctl (mib, ARRAY_SIZE (mib), &physmem, &len, NULL, 0) == 0 > > && len == sizeof (physmem)) > > return (double) physmem; > > } > > > > This works if you have less than 4GB because of the unsigned int > > physmem. I have 12 GB, which of course, when expanded to the number > > of bytes doesn't fit into a unsigned int physmem. > > physmem is actually an unsigned long, not an unsigned int, so on amd64 > that sysctl call should fail anyway (amd64 is LP64, so a long won't fit > into an int). I changed "unsigned int physmem;" to "size_t physmem;". Now, the 12 GB are recognized. > > gcc version 3.4.4 [FreeBSD] 20050518 > > GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096 > > > > In particular, ggc-min-heapsize=4096 is ridiculously small for a > > system with 12 GB of memory. > > On all my FreeBSD boxes from 128MB to 1GB of RAM, I get the exact same > heuristic values as you, so I'm not sure whether the code works at all. I forced physmem to be 8196 and recompiled gcc. For whatever reason, ggc-min-heapsize=4096 was still reported, but my compiling problems disappeared. I think you may be right about the code not doing working as the programmer may have thought. -- Steve From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 10 02:07:38 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6435216A422 for ; Sat, 10 Dec 2005 02:07:38 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33C1643D4C for ; Sat, 10 Dec 2005 02:07:36 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from flame.pc (patr530-a085.otenet.gr [212.205.215.85]) by kane.otenet.gr (8.13.4/8.13.4/Debian-8) with ESMTP id jBA27XML004622; Sat, 10 Dec 2005 04:07:33 +0200 Received: by flame.pc (Postfix, from userid 1001) id 8487F11551; Sat, 10 Dec 2005 04:06:43 +0200 (EET) Date: Sat, 10 Dec 2005 04:06:43 +0200 From: Giorgos Keramidas To: babkin@users.sourceforge.net Message-ID: <20051210020643.GA6206@flame.pc> References: <10939303.1134158545675.JavaMail.root@vms070.mailsrvcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <10939303.1134158545675.JavaMail.root@vms070.mailsrvcs.net> Cc: freebsd-hackers@freebsd.org, Divacky Roman Subject: Re: Re: sysctl, HW_PHYSMEM, and crippled gcc X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 02:07:38 -0000 On 2005-12-09 14:02, Sergey Babkin wrote: >Divacky Roman wrote: >>On Thu, Dec 08, 2005 at 05:06:16PM -0800, Steve Kargl wrote: >>> Anyone have any insight into fixing gcc to make better >>> use of system memory on systems with more than 4 GB. >>> It appears that libiberty/physmem.c tries to use sysctl() >>> to determine the amount of physical memory in a system. >>> >>> { /* This works on *bsd and darwin. */ >>> unsigned int physmem; >>> size_t len = sizeof physmem; >>> static int mib[2] = { CTL_HW, HW_PHYSMEM }; >>> >>> if (sysctl (mib, ARRAY_SIZE (mib), &physmem, &len, NULL, 0) == 0 >>> && len == sizeof (physmem)) >>> return (double) physmem; >>> } >>> >>> This works if you have less than 4GB because of the unsigned >>> int physmem. I have 12 GB, which of course, when expanded >>> to the number of bytes doesn't fit into a unsigned int physmem. > >>> In particular, ggc-min-heapsize=4096 is ridiculously small for a >>> system with 12 GB of memory. >> >> the code works here (512M of memory)... dont know about the ifdefs its >> surrounded by.. > > I guess you've confused M and G :-) The point is that > it breaks with over 4G of memory. Can someone with access to a system with more than 4 GB verify that the following works correctly? % flame:/home/keramida/tmp/physmem$ cat -n physmem.c % 1 #include % 2 #include % 3 % 4 #include % 5 #include % 6 #include % 7 #include % 8 % 9 int % 10 main(void) % 11 { % 12 uint64_t physmem; % 13 size_t len = sizeof physmem; % 14 static int mib[] = { CTL_HW, HW_PHYSMEM }; % 15 static size_t miblen = sizeof(mib) / sizeof(mib[0]); % 16 % 17 if (sysctl(mib, miblen, &physmem, &len, NULL, 0) != 0) % 18 err(1, "sysctl hw.physmem"); % 19 printf("Physical memory = %ju bytes\n", (intmax_t)physmem); % 20 return EXIT_SUCCESS; % 21 } % flame:/home/keramida/tmp/physmem$ ./physmem % Physical memory = 526151680 bytes % flame:/home/keramida/tmp/physmem$ Then we can probably try to push a similar change towards the libiberty developers too, unless there are serious problems with supporting uint64_t on some of the platforms that libiberty needs to run on. From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 10 03:46:31 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2DE5C16A4F2 for ; Sat, 10 Dec 2005 03:46:31 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id A184C43D62 for ; Sat, 10 Dec 2005 03:46:30 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id jBA3kTcc025106; Fri, 9 Dec 2005 21:46:29 -0600 (CST) (envelope-from dan) Date: Fri, 9 Dec 2005 21:46:29 -0600 From: Dan Nelson To: Giorgos Keramidas Message-ID: <20051210034629.GI95420@dan.emsphone.com> References: <10939303.1134158545675.JavaMail.root@vms070.mailsrvcs.net> <20051210020643.GA6206@flame.pc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051210020643.GA6206@flame.pc> X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org, babkin@users.sourceforge.net, Divacky Roman Subject: Re: sysctl, HW_PHYSMEM, and crippled gcc X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 03:46:31 -0000 In the last episode (Dec 10), Giorgos Keramidas said: > >>On Thu, Dec 08, 2005 at 05:06:16PM -0800, Steve Kargl wrote: > >>> Anyone have any insight into fixing gcc to make better > >>> use of system memory on systems with more than 4 GB. > >>> It appears that libiberty/physmem.c tries to use sysctl() > >>> to determine the amount of physical memory in a system. > >>> > >>> { /* This works on *bsd and darwin. */ > >>> unsigned int physmem; > >>> size_t len = sizeof physmem; > >>> static int mib[2] = { CTL_HW, HW_PHYSMEM }; > >>> > >>> if (sysctl (mib, ARRAY_SIZE (mib), &physmem, &len, NULL, 0) == 0 > >>> && len == sizeof (physmem)) > >>> return (double) physmem; > >>> } > >>> > >>> This works if you have less than 4GB because of the unsigned > >>> int physmem. I have 12 GB, which of course, when expanded > >>> to the number of bytes doesn't fit into a unsigned int physmem. > > Can someone with access to a system with more than 4 GB verify that the > following works correctly? > > % flame:/home/keramida/tmp/physmem$ cat -n physmem.c > % 9 int > % 10 main(void) > % 11 { > % 12 uint64_t physmem; > % 13 size_t len = sizeof physmem; > % 14 static int mib[] = { CTL_HW, HW_PHYSMEM }; > % 15 static size_t miblen = sizeof(mib) / sizeof(mib[0]); > % 16 > % 17 if (sysctl(mib, miblen, &physmem, &len, NULL, 0) != 0) > % 18 err(1, "sysctl hw.physmem"); > % 19 printf("Physical memory = %ju bytes\n", (intmax_t)physmem); > % 20 return EXIT_SUCCESS; > % 21 } Won't this break on x86, where physmem is 32 bits? Just use "unsigned long", which is what the sysctl type is according to kern_mib.c . -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 10 11:17:26 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5123216A41F for ; Sat, 10 Dec 2005 11:17:26 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99CDB43D64 for ; Sat, 10 Dec 2005 11:17:24 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (envelope-from xdivac02@eva.fit.vutbr.cz) (8.13.4/8.13.3) with ESMTP id jBABHL4b096600 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 10 Dec 2005 12:17:21 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.4/8.13.3/Submit) id jBABHKFj096598; Sat, 10 Dec 2005 12:17:20 +0100 (CET) Date: Sat, 10 Dec 2005 12:17:20 +0100 From: Divacky Roman To: Sergey Babkin Message-ID: <20051210111720.GA96448@stud.fit.vutbr.cz> References: <10939303.1134158545675.JavaMail.root@vms070.mailsrvcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <10939303.1134158545675.JavaMail.root@vms070.mailsrvcs.net> User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.49 on 147.229.10.14 Cc: freebsd-hackers@freebsd.org Subject: Re: Re: sysctl, HW_PHYSMEM, and crippled gcc X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 11:17:26 -0000 On Fri, Dec 09, 2005 at 02:02:25PM -0600, Sergey Babkin wrote: > >From: Divacky Roman > > >On Thu, Dec 08, 2005 at 05:06:16PM -0800, Steve Kargl wrote: > >> Anyone have any insight into fixing gcc to make better > >> use of system memory on systems with more than 4 GB. > >> It appears that libiberty/physmem.c tries to use sysctl() > >> to determine the amount of physical memory in a system. > >> > >> { /* This works on *bsd and darwin. */ > >> unsigned int physmem; > >> size_t len = sizeof physmem; > >> static int mib[2] = { CTL_HW, HW_PHYSMEM }; > >> > >> if (sysctl (mib, ARRAY_SIZE (mib), &physmem, &len, NULL, 0) == 0 > >> && len == sizeof (physmem)) > >> return (double) physmem; > >> } > >> > >> This works if you have less than 4GB because of the unsigned > >> int physmem. I have 12 GB, which of course, when expanded > >> to the number of bytes doesn't fit into a unsigned int physmem. > > >> In particular, ggc-min-heapsize=4096 is ridiculously small for a > >> system with 12 GB of memory. > > > >the code works here (512M of memory)... dont know about the ifdefs its > >surrounded by.. > > I guess you've confused M and G :-) The point is that > it breaks with over 4G of memory. dan nelson reported he has the same value with all machine with various ram sizes. so he presumed the code doesnt work at all... and it did for me From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 10 15:01:41 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA43816A41F for ; Sat, 10 Dec 2005 15:01:41 +0000 (GMT) (envelope-from zhou.bowen@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id CFA3143D60 for ; Sat, 10 Dec 2005 15:01:40 +0000 (GMT) (envelope-from zhou.bowen@gmail.com) Received: by wproxy.gmail.com with SMTP id i22so1113435wra for ; Sat, 10 Dec 2005 07:01:40 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Kl0ItyLB3MKDl+asbasd65FhI/GOzxluHO2dKzzwedDXp1sIcLTx7ZgWPESXv3pKwUf5SJ1pTlLoFXTqApYktCK4XdMEeMt/I+zqtGsfkHrs9XFRfGuqBrvDjyiJ6SC97m7cYCJu/o1NmNjt8q+Fi5xxcc0Im5lfykYq6SvtBys= Received: by 10.64.251.2 with SMTP id y2mr1455939qbh; Sat, 10 Dec 2005 07:01:39 -0800 (PST) Received: by 10.65.43.18 with HTTP; Sat, 10 Dec 2005 07:01:39 -0800 (PST) Message-ID: <821419ca0512100701oa12651ao34f40c14cae37175@mail.gmail.com> Date: Sat, 10 Dec 2005 23:01:39 +0800 From: Bowen Zhou To: freebsd-hackers@freebsd.org In-Reply-To: <821419ca0512100657u363cdfc6wbae45b207cbd71f2@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 Content-Disposition: inline References: <821419ca0512072329q4ad120c5g367dd2192b91eccd@mail.gmail.com> <20051208120001.GA921@pm513-1.comsys.ntu-kpi.kiev.ua> <821419ca0512081737j1e2f1186r9931b747f1dc0691@mail.gmail.com> <821419ca0512100657u363cdfc6wbae45b207cbd71f2@mail.gmail.com> Subject: Fwd: Object reusement implementation in 6.0release: HELP Wanted!!! X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 15:01:41 -0000 U29ycnkgZm9yIHJlcGx5IG15c2VsZi4KCkkgcmVhbGx5IGNvbmZ1c2VkIGJ5IHRoaXMgcHJvYmxl bS4KCk5lZWQgeW91ciBoZWxwISEhCgpPbiAxMi85LzA1LCBCb3dlbiBaaG91IDx6aG91LmJvd2Vu QGdtYWlsLmNvbT4gd3JvdGU6Cj4gVGhhbmtzIGZvciBjb25jZXJuaW5nIG15IHF1ZXN0aW9uLgo+ Cj4gSSBuZWVkIHRvIGNsZWFuIGFsbCB0aGUgZGF0YSBibG9ja3Mgb2YgYSBpbm9kZSwgaW5jbHVk aW5nIGRpcmVjdCBkaXNrCj4gYmxvY2tzLCBpbmRpcmVjdCBkaXNrIGJsb2NrcyBhbmQgZXh0ZXJu YWwgYXR0cmlidXRlcyBibG9ja3MuCj4KPiBJIGhhdmUgdHJpZWQgdG8gaW5zZXJ0IGNsZWFuaW5n IGNvZGUgaW50bwo+IGZmc19ibGtmcmVlKC91ZnMvZmZzL2Zmc19hbGxvYy5jKSwgYnV0IHRoZSBy ZXN1bHQgd2FzIG5vdCBnb29kIGVub3VnaC4KPiBBZnRlciBjb21waWxlZCB0aGUga2VybmVsKEdF TkVSSUMpIHdpdGggbXkgY2xlYW5pbmcgY29kZSBhbmQgcmVzdGFydGVkCj4gdGhlIGNvbXB1dGVy LCBJIGZvdW5kIHRoYXQgc29tZSBkYXRhIGJsb2NrcyBvZiBub3JtYWwgZmlsZXMgd2hpY2ggaGF2 ZQo+IG5vdCBiZWVuIGRlbGV0ZWQgeWV0IGRpc2FwcGVhcmVkIHJhbmRvbWx5Lgo+Cj4gVGhlIGZv bGxvd2luZyBpcyB0aGUgY29kZSBJIGhhdmUgaW5zZXJ0ZWQgaW50byBmZnNfYmxrZnJlZShpbmNs dWRpbmcKPiB0aGUgYmVnaW5uaW5nIHBhcnQgb2YgdGhlIG9yaWdpbmFsIGZ1bmN0aW9uKToKPgo+ IHZvaWQKPiBmZnNfYmxrZnJlZSh1bXAsIGZzLCBkZXZ2cCwgYm5vLCBzaXplLCBpbnVtKQo+ICAg ICAgICBzdHJ1Y3QgdWZzbW91bnQgKnVtcDsKPiAgICAgICAgc3RydWN0IGZzICpmczsKPiAgICAg ICAgc3RydWN0IHZub2RlICpkZXZ2cDsKPiAgICAgICAgdWZzMl9kYWRkcl90IGJubzsKPiAgICAg ICAgbG9uZyBzaXplOwo+ICAgICAgICBpbm9fdCBpbnVtOwo+IHsKPiAgICAgICAgc3RydWN0IGNn ICpjZ3A7Cj4gICAgICAgIHN0cnVjdCBidWYgKmJwOwo+ICAgICAgICBzdHJ1Y3QgYnVmICpicDE7 Cj4gICAgICAgIHVmczFfZGFkZHJfdCBmcmFnbm8sIGNnYm5vOwo+ICAgICAgICB1ZnMyX2RhZGRy X3QgY2dibGtubzsKPiAgICAgICAgaW50IGksIGNnLCBibGssIGZyYWdzLCBiYmFzZTsKPiAgICAg ICAgdV9pbnQ4X3QgKmJsa3NmcmVlOwo+ICAgICAgICBzdHJ1Y3QgY2RldiAqZGV2Owo+Cj4gICAg ICAgIC8qb2JqZWN0IHJldXNlIHN0YXJ0cyBoZXJlLiovCj4gICAgICAgIGlmKGJyZWFkKGRldnZw LCBmc2J0b2RiKGZzLCBibm8pLCBzaXplLCBOT0NSRUQsICZicDEpKXsKPiAgICAgICAgICAgICAg ICBicmVsc2UoYnAxKTsKPiAgICAgICAgICAgICAgICByZXR1cm47Cj4gICAgICAgICAgICAgICAg fQo+ICAgICAgICBiemVybyhicDEtPmJfZGF0YSwgc2l6ZSk7Cj4gICAgICAgIGJkd3JpdGUoYnAx KTsKPiAgICAgICAgLypvYmplY3QgcmV1c2UgZW5kcyBoZXJlLiovCj4gLi4uLgo+Cj4gSSBndWVz cyB0aGVyZSBhcmUgZXJyb3JzIGluIGVpdGhlciBteSBjbGVhbmluZyBjb2RlIG9yIHRoZSBwbGFj ZSBJCj4gaW5zZXJ0ZWQgdGhlc2UgY29kZS4KPgo+IEFueSBzdWdnZXN0aW9uIGlzIHdlbGNvbWUu Cj4KPiBPbiAxMi84LzA1LCBBbmRyZXkgU2ltb25lbmtvIDxzaW1vbkBjb21zeXMubnR1LWtwaS5r aWV2LnVhPiB3cm90ZToKPiA+IE9uIFRodSwgRGVjIDA4LCAyMDA1IGF0IDAzOjI5OjA3UE0gKzA4 MDAsIEJvd2VuIFpob3Ugd3JvdGU6Cj4gPiA+IGhlbGxvLCBldmVyeW9uZS4KPiA+ID4KPiA+ID4g SSBuZWVkIHNvbHV0aW9ucyB0byBpbXBsZW1lbnQgb2JqZWN0IHJldXNlbWVudCBpbiBGcmVlQlNE Ni4wLgo+ID4gPgo+ID4gPiBXaGF0IEkgd2FudCB0byBkbyBpcyB0byBjbGVhbiB0aGUgY29udGVu dCBvZiBkYXRhIGJsb2NrcyBiZWZvcmUgdGhlCj4gPiA+IHJlLWFsbG9jYXRpb24gb2YgdGhlbS4K PiA+ID4KPiA+ID4gVGhlbiB3aGVyZSAoaW4gd2hpY2ggZnVuY3Rpb24gKSBzaG91bGQgSSBpbnNl cnQgbXkgY2xlYW5pbmcgY29kZSBpbiBvcmRlciB0bwo+ID4gPiBmdWxmaWxsIHRoZSByZXVzZW1l bnQgb2YgZGF0YSBibG9ja3M/Cj4gPgo+ID4gQWJvdXQgd2hpY2ggZGF0YWJsb2NrIGFyZSB5b3Ug YXNraW5nPwo+ID4KPgo= From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 10 17:36:11 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AE2016A41F for ; Sat, 10 Dec 2005 17:36:11 +0000 (GMT) (envelope-from flag@longino.wired.org) Received: from mail.oltrelinux.com (krisma.oltrelinux.com [194.242.226.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8077343D80 for ; Sat, 10 Dec 2005 17:36:01 +0000 (GMT) (envelope-from flag@longino.wired.org) Received: from longino.wired.org (ip-79-218.sn1.eutelia.it [62.94.79.218]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.oltrelinux.com (Postfix) with ESMTP id 0BD8C11AE58 for ; Sat, 10 Dec 2005 18:36:00 +0100 (CET) Received: from longino.wired.org (localhost.wired.org [127.0.0.1]) by longino.wired.org (8.13.4/8.13.4) with ESMTP id jBAHZuer000870 for ; Sat, 10 Dec 2005 18:35:56 +0100 (CET) (envelope-from flag@longino.wired.org) Received: (from flag@localhost) by longino.wired.org (8.13.4/8.13.4/Submit) id jBAHZuAh000869 for freebsd-hackers@freebsd.org; Sat, 10 Dec 2005 18:35:56 +0100 (CET) (envelope-from flag) Date: Sat, 10 Dec 2005 18:35:56 +0100 From: Paolo Pisati To: FreeBSD_Hackers Message-ID: <20051210173556.GA820@tin.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at krisma.oltrelinux.com Subject: EVENTHANDLER and ifaddr_event X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 17:36:11 -0000 Hi hackers, i'm using EVENTHANDLER(ifaddr_event, ...) to monitor nic address change on FreeBSD 6.x. It's working fine but my callback function is called 2 times per address change, and i don't understand why. Is it the supposed behavior? Thanks -- Paolo From owner-freebsd-hackers@FreeBSD.ORG Sat Dec 10 22:46:16 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 729B816A420 for ; Sat, 10 Dec 2005 22:46:16 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5A2143D64 for ; Sat, 10 Dec 2005 22:46:15 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.13.4/8.13.4) with ESMTP id jBAMjiMa087759 for ; Sat, 10 Dec 2005 14:45:44 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.13.4/8.13.4/Submit) id jBAMjiu0087758; Sat, 10 Dec 2005 14:45:44 -0800 (PST) Date: Sat, 10 Dec 2005 14:45:44 -0800 (PST) From: Matthew Dillon Message-Id: <200512102245.jBAMjiu0087758@apollo.backplane.com> To: FreeBSD_Hackers References: <20051210150612.648aef0e.eric@theeric.com> Subject: DragonFly talk at the upcoming BAYLISA (15 December 2005) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 22:46:16 -0000 Hello everyone! I will be giving a DragonFly talk at the next Bay Lisa. The primary focus of my talk will be a physical characterization (latencies, overheads, etc) of MP mechanisms and algorithms implemented by DragonFly. I'll be explaining how the algorithms work and providing hard (TSC-derived) numbers from a dual-core Athlon 64 X2 based system. The Bay Lisa in question will be held on December 15's 2005 7:30 p.m. to 9:30 p.m. on Apple Campus in Cupertino (California, USA). Site information and directions below: http://www.baylisa.org/ http://www.baylisa.org/location.shtml It is open to the public. Since the algorithms are fairly low level, the discussion and hard numbers I present really applies to anyone doing MP work on any operating system. -Matt