From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 05:13:32 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B26716A4CE for ; Sun, 5 Dec 2004 05:13:32 +0000 (GMT) Received: from smtp3.server.rpi.edu (smtp3.server.rpi.edu [128.113.2.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id A51CD43D49 for ; Sun, 5 Dec 2004 05:13:31 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp3.server.rpi.edu (8.13.0/8.13.0) with ESMTP id iB55DS61010446; Sun, 5 Dec 2004 00:13:30 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: <37474.1102154897@critter.freebsd.dk> References: <37474.1102154897@critter.freebsd.dk> Date: Sun, 5 Dec 2004 00:13:27 -0500 To: Poul-Henning Kamp , current@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) Subject: Re: [TEST/REVIEW]: rootfs mounting code rework X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 05:13:32 -0000 At 11:08 AM +0100 12/4/04, Poul-Henning Kamp wrote: >http://phk.freebsd.dk/patch/rootfs.patch > >Please test and review. Hmm. Does this mean that we'll always get the correct partition for '/', even if /etc/fstab is wrong for '/'? By "correct", I mean "the partition that the kernel was loaded from". -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 08:44:04 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91FA716A4CE for ; Sun, 5 Dec 2004 08:44:04 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF5FC43D4C for ; Sun, 5 Dec 2004 08:44:03 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB58i1Vq056326; Sun, 5 Dec 2004 09:44:01 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Garance A Drosihn From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sun, 05 Dec 2004 00:13:27 EST." Date: Sun, 05 Dec 2004 09:44:01 +0100 Message-ID: <56325.1102236241@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@freebsd.org Subject: Re: [TEST/REVIEW]: rootfs mounting code rework X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 08:44:04 -0000 In message , Garance A Drosihn writes: >At 11:08 AM +0100 12/4/04, Poul-Henning Kamp wrote: >>http://phk.freebsd.dk/patch/rootfs.patch >> >>Please test and review. > >Hmm. Does this mean that we'll always get the correct partition >for '/', even if /etc/fstab is wrong for '/'? By "correct", I >mean "the partition that the kernel was loaded from". The loader reads /etc/fstab and picks the entry for '/' out of it so I can only pressume that whoever did that disagree with your notion of "correct". -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 09:42:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FC7B16A4CE for ; Sun, 5 Dec 2004 09:42:23 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3044E43D48 for ; Sun, 5 Dec 2004 09:42:23 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id iB59gL0N003946; Sun, 5 Dec 2004 04:42:21 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)iB59gLQf003943; Sun, 5 Dec 2004 04:42:21 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Sun, 5 Dec 2004 04:42:21 -0500 (EST) From: Jeff Roberson To: Poul-Henning Kamp In-Reply-To: <56325.1102236241@critter.freebsd.dk> Message-ID: <20041205044145.A18185@mail.chesapeake.net> References: <56325.1102236241@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Garance A Drosihn cc: current@freebsd.org Subject: Re: [TEST/REVIEW]: rootfs mounting code rework X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 09:42:23 -0000 On Sun, 5 Dec 2004, Poul-Henning Kamp wrote: > In message , Garance A Drosihn writes: > >At 11:08 AM +0100 12/4/04, Poul-Henning Kamp wrote: > >>http://phk.freebsd.dk/patch/rootfs.patch > >> > >>Please test and review. > > > >Hmm. Does this mean that we'll always get the correct partition > >for '/', even if /etc/fstab is wrong for '/'? By "correct", I > >mean "the partition that the kernel was loaded from". > > The loader reads /etc/fstab and picks the entry for '/' out of it > so I can only pressume that whoever did that disagree with your > notion of "correct". I believe he's referring to the case where you load a kernel from somewhere other than the default '/'. > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 10:02:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B48116A4CE for ; Sun, 5 Dec 2004 10:02:16 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9823443D66 for ; Sun, 5 Dec 2004 10:02:15 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB5A29j3057431; Sun, 5 Dec 2004 11:02:09 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Jeff Roberson From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sun, 05 Dec 2004 04:42:21 EST." <20041205044145.A18185@mail.chesapeake.net> Date: Sun, 05 Dec 2004 11:02:09 +0100 Message-ID: <57430.1102240929@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: Garance A Drosihn cc: current@freebsd.org Subject: Re: [TEST/REVIEW]: rootfs mounting code rework X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 10:02:16 -0000 In message <20041205044145.A18185@mail.chesapeake.net>, Jeff Roberson writes: >On Sun, 5 Dec 2004, Poul-Henning Kamp wrote: > >> In message , Garance A Drosihn writes: >> >At 11:08 AM +0100 12/4/04, Poul-Henning Kamp wrote: >> >>http://phk.freebsd.dk/patch/rootfs.patch >> >> >> >>Please test and review. >> > >> >Hmm. Does this mean that we'll always get the correct partition >> >for '/', even if /etc/fstab is wrong for '/'? By "correct", I >> >mean "the partition that the kernel was loaded from". >> >> The loader reads /etc/fstab and picks the entry for '/' out of it >> so I can only pressume that whoever did that disagree with your >> notion of "correct". > >I believe he's referring to the case where you load a kernel from >somewhere other than the default '/'. I'm not sure, and I don't really care much. The order in which the kernel tries various root filesystems is not affected apart from me removing the "ask" mode which is badly implemented, prone to problems and unecessary now that we can set it in the loader. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 10:19:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B6AB916A4CF for ; Sun, 5 Dec 2004 10:19:47 +0000 (GMT) Received: from ares.strahov.cz (wireless.blueboard.cz [82.208.31.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6730D43D62 for ; Sun, 5 Dec 2004 10:19:42 +0000 (GMT) (envelope-from lists@hosting50.cz) Received: (qmail 45444 invoked by uid 1002); 5 Dec 2004 10:17:29 -0000 Received: from lists@hosting50.cz by wireless.blueboard.cz by uid 89 with qmail-scanner-1.22 (clamscan: 0.75.1. spamassassin: 2.64. Clear:RC:1(10.15.141.3):. Processed in 1.231674 secs); 05 Dec 2004 10:17:29 -0000 Received: from unknown (HELO ?10.15.141.3?) (ares@hosting50.cz@10.15.141.3) by 10.15.0.77 with (DHE-RSA-AES256-SHA encrypted) SMTP; 5 Dec 2004 10:17:27 -0000 Message-ID: <41B2E0B7.1020001@hosting50.cz> Date: Sun, 05 Dec 2004 11:19:35 +0100 From: Tomas Randa User-Agent: Mozilla Thunderbird 0.9 (X11/20041205) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org, mobile@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: estctrl & ACPI question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 10:19:47 -0000 Hi, I have Acer TravelMate 3200 and have following problems with estctrl: estctrl: Error reading AC line status: No such file or directory It is because sysctl hw.acpi.acline not exists. Is anybody here with this problems? Thanks for help. Tomas Randa From owner-freebsd-current@FreeBSD.ORG Sat Dec 4 17:40:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9973B16A4CE for ; Sat, 4 Dec 2004 17:40:06 +0000 (GMT) Received: from mail.squidge.com (mail0.squidge.com [195.10.252.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF63743D39 for ; Sat, 4 Dec 2004 17:40:05 +0000 (GMT) (envelope-from henry@jot.to) Received: from lightbox (82-70-14-145.dsl.in-addr.zen.co.uk [82.70.14.145]) (authenticated bits=0) by mail.squidge.com (8.12.11/8.12.9) with ESMTP id iB4HdwZB046807 for ; Sat, 4 Dec 2004 17:39:59 GMT Message-ID: <006501c4da28$5692e130$0a64a8c0@techiebod.com> From: "Henry Whincup" To: Date: Sat, 4 Dec 2004 17:40:24 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Scanned: by AMaViS at mail.squidge.com X-Spam-Level: 0.0 X-Mailman-Approved-At: Sun, 05 Dec 2004 12:47:39 +0000 Subject: ffs_clusteralloc: allocated out of group on 5TB fs (5.3-Stable) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 17:40:06 -0000 On a machine with a 5TB array I created a single partition via gpt and a filesystem using the defaults from newfs. All seemed well until I tried to fill the partition with data. With "only" 870GB or so used utilities started reporting the disk as full. Shortly (a few hours) after the machine panic'd. During this time I had been trying to copy file via nfs and rsync onto the array. After several crashes I tried a simple "dd if=/dev/zero of=./file" and after writing ~33GB the machine rebooted (the panic details below are from this reboot) Details follow: # ls -l /fs/file -rw-r--r-- 1 root wheel 35446063104 Nov 29 15:00 /fs/file # gpt -r -v show /dev/da0 gpt show: /dev/da0: mediasize=5597405642752; sectorsize=512; blocks=10932432896 start size index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 34 10932432829 1 GPT part - FreeBSD UFS/UFS2 10932432863 32 Sec GPT table 10932432895 1 Sec GPT header # df -h /fs Filesystem Size Used Avail Capacity Mounted on /dev/da0p1 4.9T 897G 3.7T 19% /fs # df -ki /fs Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/da0p1 5294245800 940234932 3930471204 19% 2190679 681971367 0% /fs Error messages before panic: Nov 29 12:29:46 mach kernel: pid 6749 (bsdtar), uid 0 inumber 234766339 on /fs: filesystem full Nov 29 14:19:00 mach kernel: pid 34204 (pax), uid 0 inumber 505543685 on /fs: filesystem full Dumpfs header: magic 19540119 (UFS2) time Mon Nov 29 15:23:41 2004 superblock location 65536 id [ 419208fe aae47fbc ] ncg 29049 size 2733108207 blocks 2647122900 bsize 16384 shift 14 mask 0xffffc000 fsize 2048 shift 11 mask 0xfffff800 frag 8 shift 3 fsbtodb 2 minfree 8% optim time symlinklen 120 maxbsize 16384 maxbpg 2048 maxcontig 8 contigsumsize 8 nbfree 272113785 ndir 267986 nifree 681971367 nffree 95154 bpg 11761 fpg 94088 ipg 23552 nindir 2048 inopb 64 maxfilesize 140806241583103 sbsize 2048 cgsize 16384 csaddr 3000 cssize 464896 sblkno 40 cblkno 48 iblkno 56 dblkno 3000 cgrotor 22824 fmod 0 ronly 0 clean 0 avgfpdir 64 avgfilesize 16384 flags none fsmnt /fs volname swuid 0 info file contents: Good dump found on device /dev/da1s1e Architecture: i386 Architecture version: 1 Dump length: 2147483648B (2048 MB) Blocksize: 512 Dumptime: Mon Nov 29 15:01:10 2004 Hostname: mach.example.com Versionstring: FreeBSD 5.3-STABLE #0: Fri Nov 12 13:05:18 UTC 2004 root@mach.example.com:/usr/obj/usr/src/sys/SMP Panicstring: ffs_clusteralloc: allocated out of group Bounds: 0 Backtrace: #0 0xc060ce82 in doadump () #1 0xc060d47b in boot () #2 0xc060d7a1 in panic () #3 0xc073445e in ffs_clusteralloc () #4 0xc0733680 in ffs_hashalloc () #5 0xc07329ea in ffs_reallocblks_ufs2 () #6 0xc073205a in ffs_reallocblks () #7 0xc0657e7c in cluster_write () #8 0xc074c350 in ffs_write () #9 0xc066bf10 in vn_write () #10 0xc062d624 in dofilewrite () #11 0xc062d4d1 in write () #12 0xc07bb07f in syscall () #13 0xc07a8a0f in Xint0x80_syscall () Kernel is the default SMP kernel and sources are from 28th Nov 2004. I assume a proper debug kernel with symbols would be more helpful, but I just wanted to know if this was a known bug - or something I have done wrong, first. Other than that is there anything else I can provide to help find this bug? Thanks Henry From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 10:43:55 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 034FF16A4CE for ; Sun, 5 Dec 2004 10:43:55 +0000 (GMT) Received: from united.networks.org (united.networks.org [209.209.49.209]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8C1143D53 for ; Sun, 5 Dec 2004 10:43:54 +0000 (GMT) (envelope-from hogan@ninthgate.net) Received: by united.networks.org (Postfix, from userid 101) id 751ABB744; Sun, 5 Dec 2004 02:43:23 -0800 (PST) Date: Sun, 5 Dec 2004 10:43:23 +0000 From: Hogan Whittall To: Doug White Message-ID: <20041205104323.GA21375@ninthgate.net> References: <20041123182254.GB10721@ninthgate.net> <20041124231627.I2006@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041124231627.I2006@carver.gumbysoft.com> User-Agent: Mutt/1.4.2.1i X-Header: It's a Jeep thing, you wouldn't understand... X-Mailman-Approved-At: Sun, 05 Dec 2004 12:47:39 +0000 cc: freebsd-current@freebsd.org Subject: Re: Random panics with 5.3-REL, SMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: hogan@ninthgate.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 10:43:55 -0000 Here's the output of the panic. It hung again while dumping core... Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 02 fault virtual address = 0xa748d260 fault code = supervisor write, page not present instruction pointer = 0x8:0xc060b611 stack pointer = 0x10:0xe971bc20 frame pointer = 0x10:0xe971bc20 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 = 52 (swi6: task queue) trap number = 12 panic: page fault cpuid = 3 boot() called on cpu#3 Uptime: 5d6h6m34s Dumping 3967 MB 16 32 48 64 80 96 112 128 144 160 Whenever it panics it will hang at a random point during the dump, this last time was the farthest it got... Someone seems to suspect bad ram as the culprit. I can always swap it out and see what happens. -Hogan On Wed, Nov 24, 2004 at 11:24:43PM -0800, Doug White wrote: > On Tue, 23 Nov 2004, Hogan Whittall wrote: > > > Dell PE6450 server, 4xP3-700 Xeon, 4gb ram, system disks reside on > > a 2 disk RAID1 attached to a MegaRAID controller. Wireless is a > > D-Link DWL-G520-B, also has Intel Pro/100 ethernet. > > For the record, I have a PE6300 (4x500MHz) I'm testing a fix for panics of > the form > > panic: Previous IPI is stuck > > if thats one of the "random panics" you're seeing. The thread "number of > CPUs and IPI panic" in -current has details, and a temporary patch is > available from > > http://people.freebsd.org/~ups/ipi4_patch > > I believe this patch will apply to both RELENG_5 and -CURRENT, for now. > > I was having a problem with random resets (no panic, just reset) and > traced it to a broken cpu0. Replacing it made the resets go away. > > If you have room you may want to install RedHat or Windows on another > partition, load up the OpenManage tools, and inspect the system event log > for anything peculiar. If you've never run this before then you may need > to clear the event log for it to log any new events. If you have a DRAC > card in the machine you can use that too. > > -- > Doug White | FreeBSD: The Power to Serve > dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 14:31:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08EF116A4CE for ; Sun, 5 Dec 2004 14:31:40 +0000 (GMT) Received: from ms-smtp-02-eri0.ohiordc.rr.com (ms-smtp-02-smtplb.ohiordc.rr.com [65.24.5.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E72643D48 for ; Sun, 5 Dec 2004 14:31:39 +0000 (GMT) (envelope-from dzerkel@columbus.rr.com) Received: from [192.168.2.29] (dhcp065-024-056-219.columbus.rr.com [65.24.56.219])iB5EVbJl026156 for ; Sun, 5 Dec 2004 09:31:37 -0500 (EST) Message-ID: <41B31BF1.50909@columbus.rr.com> Date: Sun, 05 Dec 2004 09:32:17 -0500 From: "Danny J. Zerkel" User-Agent: Mozilla Thunderbird 0.9 (X11/20041123) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Observations about geom mirror and slices X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 14:31:40 -0000 Just a note about geom mirror and slices. I don't know how many people have run into this yet, but a warning may be in order in the man pages. When I first started experimenting with mirroring on my system, I naively thought I could just mirror any disk partition. Turns out this can be very bad. The problem is that if you mirror a partition that extends all the way to the end of the slice, then geom mirror will think that the mirror part is the entire slice. This is because geom mirror uses the last block for status information. When geom starts tasting the disks, geom mirror sees the last block of the whole slice before it sees the individual partitions. To avoid this, none of the partitions, except c, should include the last block of the slice. Danny J. Zerkel dzerkel@columbus.rr.com From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 15:09:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D4AD816A4CE; Sun, 5 Dec 2004 15:09:27 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 278F643D5C; Sun, 5 Dec 2004 15:09:27 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB5F9PKT061739; Sun, 5 Dec 2004 16:09:25 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: arch@freebsd.org, current@freebsd.org From: Poul-Henning Kamp Date: Sun, 05 Dec 2004 16:09:25 +0100 Message-ID: <61738.1102259365@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Subject: [HEADSUP/TEST]: mount(2)/nmount(2) & rootfs mounting X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 15:09:28 -0000 Please help test this megapatch: http://phk.freebsd.dk/patch/nmount.patch Any observations of filesystems behaving differently etc are most welcome. I intend to commit this before X-mas if at all possible. The problem, briefly stated: ---------------------------- The old mount(2) interface, ("omount") does not help filesystems much with argument passing. A single pointer is passed in along with a set of flags of which some are magic to varying degrees. The single pointer is usually used for a struct MYFS_args, which contains what the filesystem needs. Since these structs differ from filesystem to filesystem, we can not reuse the userland mount code, but need a mount_msdos(8), mount_nwfs(8) etc etc. We ran out of flags, and rather than just postpone the trouble by making the flags field wider, we (mux@ & I) created a new mount system call ("nmount") which can pass lists of options and help filesystems manage them. How nmount(2) works ------------------- In userland, a list of options are collected, they have names which are ascii-strings and values which can be anything: build_iovec(&iov, &iovlen, "fstype", "ufs", -1); build_iovec(&iov, &iovlen, "fspath", mntpath, -1); build_iovec(&iov, &iovlen, "from", dev, -1); build_iovec(&iov, &iovlen, "flags", &ufs_flags, sizeof ufs_flags); build_iovec(&iov, &iovlen, "export", &export, sizeof export); if (nmount(iov, iovlen, mntflags) < 0) err(1, "%s", dev); On the kernel side, the options are copyin(9)'ed and arranged into a list. A number of functions allows a filesystem to access elements in the list. Compatibility ------------- If an old style mount call comes in, the filesystem offers a "vfs_cmount" function which converts old-style arguments into an kernel call to nmount: error = copyin(data, &args, sizeof args); if (error) return (error); ma = mount_arg(ma, "from", args.fspec, -1); ma = mount_arg(ma, "export", &args.export, sizeof args.export); ma = mount_argf(ma, "uid", "%d", args.uid); ma = mount_argf(ma, "gid", "%d", args.gid); [...] error = kernel_mount(ma, flags); Root mounting ------------- When we mount the root filesystem, we do with an ascii string of the form "$filesystem:$something", if the filesystem is able to parse $something (passed in mount argument "from", the filesystem can be used as root filesystem (NB: there must be a /dev directory or things go downhill really fast). There are no other requirements or special code needed in the filesystem. In theory, we should be able to use a msdosfs as rootfilesystem now. (see other email about how root mounting works) The Short Future Pespective --------------------------- After some more testing I will commit my current megapatch and deal with breakage we find it. The Long Future Perspective --------------------------- A few filesystems need magic userland support, nfs, nwfs and similar where userland does some of the network setup. For these we will still need a mount_blafs(8) program which knows about these things. For all other filesystems my hope is that we can keep all mount options as ascii strings so that a single mount(8) tool can work for all of these filesystems. Currently I have made the omount->nmount conversion as best I could, (refinements are more than welcome) and the kernel will now respond to both nmount and omount systemcalls. Before 6.0 freeze I want to convert userland to use nmount exclusively, this hopefully will amount to getting rid of a number of mount_foofs(8) programs. After 6.0 branch I want to remove the omount compatibility in the kernel so that 7.x is nmount exclusively. So, the problem here is that I can not even test all these various filesystems and I would be surprised if I can find the time to polish each and every one of them, so I hope the various filesystem owners and other interested hackers will step in and help me with the last bit of this. What needs to be done --------------------- UFS/FFS: release global mount flags which are areally UFS/FFS private flags (MNT_SOFTDEP etc). NFS/NFSv4: More sharing is possible here I think. Root mount code is too magic, we don't really interpret the "from" string as far as I can tell, rather we rely on various magic stuff dropped by bootloader. Would be nice if we DTRT so that one could point a kernel at any NFS server without bootloader support. All filesystems: Verify that things work. Tune the option names and error checking. Get rid of mount_foofs(8) if possible. Documentation. All "single user" filesystems There may be a "market" for some library routines to handle filesystems which are designed for single-user (msdosfs etc) rather than have the uid/gid/filemode/dirmode in three or four separate filesystems. Documentation Please help! *END* -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 17:08:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53A5516A4CE for ; Sun, 5 Dec 2004 17:08:10 +0000 (GMT) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3ED943D53 for ; Sun, 5 Dec 2004 17:08:09 +0000 (GMT) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.13.1/8.13.1) with ESMTP id iB5H888G096859 for ; Sun, 5 Dec 2004 12:08:08 -0500 (EST) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.13.1/8.13.1/Submit) id iB5H881t096858 for current@freebsd.org; Sun, 5 Dec 2004 12:08:08 -0500 (EST) (envelope-from barney) Date: Sun, 5 Dec 2004 12:08:08 -0500 From: Barney Wolff To: current@freebsd.org Message-ID: <20041205170808.GA96727@pit.databus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i X-Scanned-By: MIMEDefang 2.48 on 127.0.0.1 Subject: mbuf count negative X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 17:08:10 -0000 Is anybody else seeing this? lab:/root # netstat -m 4294959731 mbufs in use 1170/25600 mbuf clusters in use (current/max) 0/3/6656 sfbufs in use (current/peak/max) 448 KBytes allocated to network 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 650 calls to protocol drain routines lab:/root # uname -a FreeBSD lab.databus.com 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Fri Dec 3 21:44:57 EST 2004 toor@lab.databus.com:/usr/obj/usr/src/sys/LAB i386 It happens almost instantly during periodic when the system is used to receive a backup via nfs. Normal operation, including a dozen hours of port building, does not cause it. It is consistent, 3 times now. H/W is Asus A7M266-D with 2xAthlon 2200MP, 1GB, 39160, gvinum, em. Problem did not occur with prior -current from 11/19/04. Other than cvsup, I changed make.conf to say CPUTYPE=athlon-mp (was i686 or nothing). What can I do to help debug this? -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net. From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 17:29:32 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B77816A4CE; Sun, 5 Dec 2004 17:29:32 +0000 (GMT) Received: from ss.eunet.cz (ss.eunet.cz [193.85.228.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4030043D2F; Sun, 5 Dec 2004 17:29:31 +0000 (GMT) (envelope-from mime@traveller.cz) Received: from [127.0.0.1] (ss.eunet.cz. [193.85.228.13]) by ss.eunet.cz (8.13.1/8.13.1) with ESMTP id iB5HTXdT083133; Sun, 5 Dec 2004 18:29:33 +0100 (CET) (envelope-from mime@traveller.cz) Message-ID: <41B34579.5060703@traveller.cz> Date: Sun, 05 Dec 2004 18:29:29 +0100 From: Michal Mertl User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; cs-CZ; rv:1.7.3) Gecko/20041117 X-Accept-Language: cs, en-us, en MIME-Version: 1.0 To: Tomas Randa References: <41B2E0B7.1020001@hosting50.cz> In-Reply-To: <41B2E0B7.1020001@hosting50.cz> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: mobile@freebsd.org Subject: Re: estctrl & ACPI question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 17:29:32 -0000 Tomas Randa napsal(a): > Hi, I have Acer TravelMate 3200 and have following problems with estctrl: > > estctrl: Error reading AC line status: No such file or directory > > It is because sysctl hw.acpi.acline not exists. This may be stupid question but do you have acpi loaded? -- Michal Mertl From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 18:12:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0186F16A4CE for ; Sun, 5 Dec 2004 18:12:33 +0000 (GMT) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E31D43D62 for ; Sun, 5 Dec 2004 18:12:32 +0000 (GMT) (envelope-from kientzle@freebsd.org) Received: from freebsd.org (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id iB5ICU90025235; Sun, 5 Dec 2004 10:12:31 -0800 (PST) (envelope-from kientzle@freebsd.org) Message-ID: <41B34F8D.5030401@freebsd.org> Date: Sun, 05 Dec 2004 10:12:29 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <56325.1102236241@critter.freebsd.dk> In-Reply-To: <56325.1102236241@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: Garance A Drosihn cc: current@freebsd.org Subject: Re: [TEST/REVIEW]: rootfs mounting code rework X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 18:12:33 -0000 Poul-Henning Kamp wrote: > In message , Garance A Drosihn writes: > >>At 11:08 AM +0100 12/4/04, Poul-Henning Kamp wrote: >> >>>http://phk.freebsd.dk/patch/rootfs.patch >>> >>>Please test and review. >> >>Hmm. Does this mean that we'll always get the correct partition >>for '/', even if /etc/fstab is wrong for '/'? By "correct", I >>mean "the partition that the kernel was loaded from". > > The loader reads /etc/fstab and picks the entry for '/' out of it > so I can only pressume that whoever did that disagree with your > notion of "correct". Here's a situation that may be worth thinking about: * Working FreeBSD system that uses a separate controller. / is /dev/da4. * Controller blows up. * Connect hard disk to the on-board controller. Note: kernel is now being loaded from /dev/da0, but /etc/fstab still says / is /dev/da4. With the old rootfs code, this system is unbootable. I hope you've considered situations like this. Tim Kientzle From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 18:23:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0A5A16A4CE; Sun, 5 Dec 2004 18:23:51 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A1BE43D54; Sun, 5 Dec 2004 18:23:50 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB5INlrI064532; Sun, 5 Dec 2004 19:23:48 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Tim Kientzle From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sun, 05 Dec 2004 10:12:29 PST." <41B34F8D.5030401@freebsd.org> Date: Sun, 05 Dec 2004 19:23:47 +0100 Message-ID: <64531.1102271027@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: Garance A Drosihn cc: current@freebsd.org Subject: Re: [TEST/REVIEW]: rootfs mounting code rework X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 18:23:51 -0000 In message <41B34F8D.5030401@freebsd.org>, Tim Kientzle writes: >> The loader reads /etc/fstab and picks the entry for '/' out of it >> so I can only pressume that whoever did that disagree with your >> notion of "correct". > >Here's a situation that may be worth thinking >about: > > * Working FreeBSD system that uses > a separate controller. / is /dev/da4. > > * Controller blows up. > > * Connect hard disk to the on-board controller. > >Note: kernel is now being loaded from /dev/da0, >but /etc/fstab still says / is /dev/da4. >With the old rootfs code, this system is >unbootable. > >I hope you've considered situations like this. First: I have _not_ changed the logic that decides _which_ rootfs to mount, only the mechanics of how it is mounted. Second: I belive you could simply type something like: set vfs.root.mountfrom="ufs:/dev/da0" in the loader and your system would do what you expect it to. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 18:53:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74F4616A4CE for ; Sun, 5 Dec 2004 18:53:39 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCE2C43D2D for ; Sun, 5 Dec 2004 18:53:38 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iB5IpFN5045995; Sun, 5 Dec 2004 13:51:15 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iB5IpFnB045991; Sun, 5 Dec 2004 18:51:15 GMT (envelope-from robert@fledge.watson.org) Date: Sun, 5 Dec 2004 18:51:15 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Barney Wolff In-Reply-To: <20041205170808.GA96727@pit.databus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: mbuf count negative X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 18:53:39 -0000 On Sun, 5 Dec 2004, Barney Wolff wrote: > Is anybody else seeing this? Currently, the mbuf counters in the mbuf allocator are subject to races. I have a somewhat dated patch at: http://www.watson.org/~robert/freebsd/netperf/20040910-atomic-mballoc.diff It replaces non-atomic maintenance of the counters with atomic maintenance. However, this adds measurably to the cost of allocation, so I've been reluctant to commit it. The counters maintained by UMA are likely sufficient to generate the desired mbuf output now that we have mbuma, but I haven't had an opportunity to walk through the details of it. I hope to do so once I get closer to merging patches to use critical sections to protect UMA per-cpu caches, since I need to redo parts of the sysctl code then anyway. You might want to give this patch, or one much like it, a spin to confirm that the race is the one I think it is. The race in updating mbuf allocator statistics is one I hope to get fixed prior to 5.4. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research > > lab:/root # netstat -m > 4294959731 mbufs in use > 1170/25600 mbuf clusters in use (current/max) > 0/3/6656 sfbufs in use (current/peak/max) > 448 KBytes allocated to network > 0 requests for sfbufs denied > 0 requests for sfbufs delayed > 0 requests for I/O initiated by sendfile > 650 calls to protocol drain routines > lab:/root # uname -a > FreeBSD lab.databus.com 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Fri Dec 3 21:44:57 EST 2004 toor@lab.databus.com:/usr/obj/usr/src/sys/LAB i386 > > It happens almost instantly during periodic when the system is used to > receive a backup via nfs. Normal operation, including a dozen hours of > port building, does not cause it. It is consistent, 3 times now. > > H/W is Asus A7M266-D with 2xAthlon 2200MP, 1GB, 39160, gvinum, em. > > Problem did not occur with prior -current from 11/19/04. Other than cvsup, > I changed make.conf to say CPUTYPE=athlon-mp (was i686 or nothing). > > What can I do to help debug this? > > -- > Barney Wolff http://www.databus.com/bwresume.pdf > I'm available by contract or FT, in the NYC metro area or via the 'Net. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 19:01:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D8AB16A4CE; Sun, 5 Dec 2004 19:01:39 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB82943D55; Sun, 5 Dec 2004 19:01:38 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 79670F216C; Sun, 5 Dec 2004 11:01:38 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 71742-10; Sun, 5 Dec 2004 11:01:30 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 6976DF2148; Sun, 5 Dec 2004 11:01:30 -0800 (PST) From: Sean McNeil To: Robert Watson In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-TiWKaKKSWh+L5RXbSe+H" Date: Sun, 05 Dec 2004 11:01:29 -0800 Message-Id: <1102273289.81612.1.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com cc: Barney Wolff cc: current@freebsd.org Subject: Re: mbuf count negative X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 19:01:39 -0000 --=-TiWKaKKSWh+L5RXbSe+H Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2004-12-05 at 18:51 +0000, Robert Watson wrote: > On Sun, 5 Dec 2004, Barney Wolff wrote: >=20 > > Is anybody else seeing this? >=20 > Currently, the mbuf counters in the mbuf allocator are subject to races. > I have a somewhat dated patch at: >=20 > http://www.watson.org/~robert/freebsd/netperf/20040910-atomic-mballoc= .diff >=20 > It replaces non-atomic maintenance of the counters with atomic > maintenance. However, this adds measurably to the cost of allocation, so > I've been reluctant to commit it. The counters maintained by UMA are > likely sufficient to generate the desired mbuf output now that we have > mbuma, but I haven't had an opportunity to walk through the details of it= .=20 > I hope to do so once I get closer to merging patches to use critical > sections to protect UMA per-cpu caches, since I need to redo parts of the > sysctl code then anyway. You might want to give this patch, or one much > like it, a spin to confirm that the race is the one I think it is. The > race in updating mbuf allocator statistics is one I hope to get fixed > prior to 5.4. Since they appear to not be required for actual system use (by the fact that it being negative doesn't cause problems), could the counts be computed for display instead? --=-TiWKaKKSWh+L5RXbSe+H Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBs1sJyQsGN30uGE4RAqFsAJ9GhLFbygSb4DlwyZkiQbkcLX8nNwCglNM4 6wozPnmIZQ1QMnrlgOVQXr8= =F6eC -----END PGP SIGNATURE----- --=-TiWKaKKSWh+L5RXbSe+H-- From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 19:05:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 056B816A4CF for ; Sun, 5 Dec 2004 19:05:20 +0000 (GMT) Received: from mail.ciam.ru (mail.ciam.ru [213.147.57.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 89C2943D5A for ; Sun, 5 Dec 2004 19:05:19 +0000 (GMT) (envelope-from sem@FreeBSD.org) Received: from ppp83-237-103-117.pppoe.mtu-net.ru ([83.237.103.117]) by mail.ciam.ru with esmtpa (Exim 4.x) id 1Cb1h7-000CEI-Hb for current@freebsd.org; Sun, 05 Dec 2004 22:05:17 +0300 Message-ID: <41B35BFB.2060100@FreeBSD.org> Date: Sun, 05 Dec 2004 22:05:31 +0300 From: Sergey Matveychuk User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040815 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: nVidia nForce2 sound X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 19:05:20 -0000 Hello! My sound has dissapeared after pcm was removed. I've change pcm with 'sound', but it does not help. Today I decide to spend my time and to get back my sound. But I have no success. pciconf -l -v: ... pcm0@pci0:6:0: class=0x040100 card=0x10011695 chip=0x006a10de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce MCP-T Audio Codec Interface' class = multimedia subclass = audio ... 'kldload snd_driver' loads all drivers with the same error: pcm0: port 0xb800-0xb87f,0xb400-0xb4ff mem 0xeb001000-0xeb001fff irq 11 at device 6.0 on pci0 pcm0: [GIANT-LOCKED] pcm0: cannot reset channel 0 pcm0: unable to initialize the card device_attach: pcm0 attach returned 6 What's up? --- Sem. From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 19:10:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F0D816A4CE for ; Sun, 5 Dec 2004 19:10:56 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB63343D5C for ; Sun, 5 Dec 2004 19:10:55 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iB5J8agQ046276; Sun, 5 Dec 2004 14:08:36 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iB5J8acn046273; Sun, 5 Dec 2004 19:08:36 GMT (envelope-from robert@fledge.watson.org) Date: Sun, 5 Dec 2004 19:08:35 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Sean McNeil In-Reply-To: <1102273289.81612.1.camel@server.mcneil.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Barney Wolff cc: current@freebsd.org Subject: Re: mbuf count negative X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 19:10:56 -0000 On Sun, 5 Dec 2004, Sean McNeil wrote: > > It replaces non-atomic maintenance of the counters with atomic > > maintenance. However, this adds measurably to the cost of allocation, so > > I've been reluctant to commit it. The counters maintained by UMA are > > likely sufficient to generate the desired mbuf output now that we have > > mbuma, but I haven't had an opportunity to walk through the details of it. > > I hope to do so once I get closer to merging patches to use critical > > sections to protect UMA per-cpu caches, since I need to redo parts of the > > sysctl code then anyway. You might want to give this patch, or one much > > like it, a spin to confirm that the race is the one I think it is. The > > race in updating mbuf allocator statistics is one I hope to get fixed > > prior to 5.4. > > Since they appear to not be required for actual system use (by the fact > that it being negative doesn't cause problems), could the counts be > computed for display instead? This is pretty much what UMA does with its per-CPU caches. It pulls and pushes statistics from the caches in a couple of situations: - When pulling a new bucket into or out of the cache, it has to acquire the zone mutex, so also pushes statistics. - When a timer fires every few seconds, all the caches are checked to update the global zone statistics. - When the sysctl runs, it replicates the logic in the timer code to also update the zone statistics for display. And you can already extract pretty much all of the interesting allocation information for mbufs from vmstat -z as the mbufs are now stored using UMA. In the critical section protected version of the code, I haven't yet decided if the timers should run per-cpu, and/or how the sysctl should coalesce the information for display. I hope to have much of this resolved shortly. My current leaning is that a small amount of localized and temporary inconsistency in the stats isn't a problem, so simply doing a set of lockless reads across the per-cpu caches to update stats for presentation should be fine, and that we can probably drop the timer updates of statistics since the cache bucket balancing keeps things pretty in sync. I haven't committed the move to critical sections yet as it's currently a performance pessimization for the UP case, as entering a critical section on UP is more expensive than acquiring a mutex. John Baldwin has patches that remedy this, but hasn't yet merged them (there's also an instability with them I've seen). I know that Stephen Uphoff has also been investigating this issue. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 19:16:11 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CB8316A52A; Sun, 5 Dec 2004 19:16:11 +0000 (GMT) Received: from lakermmtao07.cox.net (lakermmtao07.cox.net [68.230.240.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69B7B43D68; Sun, 5 Dec 2004 19:16:10 +0000 (GMT) (envelope-from mezz7@cox.net) Received: from mezz.mezzweb.com ([68.103.32.140]) by lakermmtao07.cox.net (InterMail vM.6.01.03.04 201-2131-111-106-20040729) with ESMTP id <20041205191609.CMYB20686.lakermmtao07.cox.net@mezz.mezzweb.com>; Sun, 5 Dec 2004 14:16:09 -0500 Date: Sun, 05 Dec 2004 13:17:06 -0600 To: "Sergey Matveychuk" References: <41B35BFB.2060100@FreeBSD.org> From: "Jeremy Messenger" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <41B35BFB.2060100@FreeBSD.org> User-Agent: Opera M2/7.54 (Linux, build 751) cc: current@freebsd.org Subject: Re: nVidia nForce2 sound X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 19:16:11 -0000 On Sun, 05 Dec 2004 22:05:31 +0300, Sergey Matveychuk wrote: > Hello! > > My sound has dissapeared after pcm was removed. I've change pcm with > 'sound', but it does not help. Try to add snd_ich too. Cheers, Mezz > Today I decide to spend my time and to get back my sound. > But I have no success. > > pciconf -l -v: > ... > pcm0@pci0:6:0: class=0x040100 card=0x10011695 chip=0x006a10de rev=0xa1 > hdr=0x00 > vendor = 'NVIDIA Corporation' > device = 'nForce MCP-T Audio Codec Interface' > class = multimedia > subclass = audio > ... > > 'kldload snd_driver' loads all drivers with the same error: > pcm0: port 0xb800-0xb87f,0xb400-0xb4ff mem > 0xeb001000-0xeb001fff irq 11 at device 6.0 on pci0 > pcm0: [GIANT-LOCKED] > pcm0: cannot reset channel 0 > pcm0: unable to initialize the card > device_attach: pcm0 attach returned 6 > > What's up? -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 20:02:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 014EB16A4CE; Sun, 5 Dec 2004 20:02:16 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04E0943D3F; Sun, 5 Dec 2004 20:02:15 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB5K2DLX019728; Sun, 5 Dec 2004 22:02:13 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 94910-16; Sun, 5 Dec 2004 22:02:12 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB5K2Cxa019725 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 5 Dec 2004 22:02:12 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iB5K2EmZ065293; Sun, 5 Dec 2004 22:02:14 +0200 (EET) (envelope-from ru) Date: Sun, 5 Dec 2004 22:02:14 +0200 From: Ruslan Ermilov To: Sergey Matveychuk Message-ID: <20041205200214.GA65263@ip.net.ua> References: <41B35BFB.2060100@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZGiS0Q5IWpPtfppv" Content-Disposition: inline In-Reply-To: <41B35BFB.2060100@FreeBSD.org> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: current@freebsd.org Subject: Re: nVidia nForce2 sound X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 20:02:16 -0000 --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 05, 2004 at 10:05:31PM +0300, Sergey Matveychuk wrote: > Hello! >=20 > My sound has dissapeared after pcm was removed. I've change pcm with=20 > 'sound', but it does not help. > Today I decide to spend my time and to get back my sound. > But I have no success. >=20 > pciconf -l -v: > ... > pcm0@pci0:6:0: class=3D0x040100 card=3D0x10011695 chip=3D0x006a10de rev= =3D0xa1=20 > hdr=3D0x00 > vendor =3D 'NVIDIA Corporation' > device =3D 'nForce MCP-T Audio Codec Interface' > class =3D multimedia > subclass =3D audio > ... >=20 > 'kldload snd_driver' loads all drivers with the same error: > pcm0: port 0xb800-0xb87f,0xb400-0xb4ff mem=20 > 0xeb001000-0xeb001fff irq 11 at device 6.0 on pci0 > pcm0: [GIANT-LOCKED] > pcm0: cannot reset channel 0 > pcm0: unable to initialize the card > device_attach: pcm0 attach returned 6 >=20 > What's up? >=20 I've the same problem on my AMD64 box. kldload'ing snd_ich and some other modules from user mode does not work. Pre-loading modules from loader(8) works. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --ZGiS0Q5IWpPtfppv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBs2lGqRfpzJluFF4RAtKCAJ9CRKZjCLt5w1MzoxgvmjBdUPul5wCaArHT RPuOAoXIuk3SNkQfrRCv3F4= =DYZv -----END PGP SIGNATURE----- --ZGiS0Q5IWpPtfppv-- From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 20:09:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEB2916A4CE; Sun, 5 Dec 2004 20:09:49 +0000 (GMT) Received: from ss.eunet.cz (ss.eunet.cz [193.85.228.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10A1843D55; Sun, 5 Dec 2004 20:09:49 +0000 (GMT) (envelope-from mime@traveller.cz) Received: from [127.0.0.1] (ss.eunet.cz. [193.85.228.13]) by ss.eunet.cz (8.13.1/8.13.1) with ESMTP id iB5K9pxK006938; Sun, 5 Dec 2004 21:09:51 +0100 (CET) (envelope-from mime@traveller.cz) Message-ID: <41B36AF6.8010906@traveller.cz> Date: Sun, 05 Dec 2004 21:09:26 +0100 From: Michal Mertl User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; cs-CZ; rv:1.7.3) Gecko/20041117 X-Accept-Language: cs, en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Increase of WITNESS_COUNT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 20:09:49 -0000 Hello, for some time I'm seeing "witness exhausted" message in my logs when I run with WITNESS enabled. I know it's nothing new but it's either the bug which is causing it is surviving for long time or there's something special in my setups or that it's just normal (as more code get fine grained locking more witnesses are used). What are the consequences of increasing WITNESS_COUNT in src/sys/kern/subr_witness.c? I don't see any ill effects and I don't get the dreaded "witness exhausted" message. Can it be increased by default? Thanks. -- Michal Mertl From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 21:13:11 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9DD716A4E2; Sun, 5 Dec 2004 21:13:11 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4880943D2F; Sun, 5 Dec 2004 21:13:11 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from h00609772adf0.ne.client2.attbi.com ([66.30.114.143]) by comcast.net (sccrmhc12) with ESMTP id <2004120521131001200ankghe>; Sun, 5 Dec 2004 21:13:10 +0000 Received: from h00609772adf0.ne.client2.attbi.com (localhost [127.0.0.1]) iB5LD9VM005330; Sun, 5 Dec 2004 16:13:09 -0500 (EST) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: (from rodrigc@localhost)iB5LD8oj005329; Sun, 5 Dec 2004 16:13:08 -0500 (EST) (envelope-from rodrigc) Date: Sun, 5 Dec 2004 16:13:08 -0500 From: Craig Rodrigues To: Poul-Henning Kamp Message-ID: <20041205211308.GA5174@crodrigues.org> References: <61738.1102259365@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <61738.1102259365@critter.freebsd.dk> User-Agent: Mutt/1.4.1i cc: arch@freebsd.org cc: current@freebsd.org Subject: Re: [HEADSUP/TEST]: mount(2)/nmount(2) & rootfs mounting X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 21:13:11 -0000 On Sun, Dec 05, 2004 at 04:09:25PM +0100, Poul-Henning Kamp wrote: > > Please help test this megapatch: > > http://phk.freebsd.dk/patch/nmount.patch I mounted an ISO file: mdconfig -a -t vnode -f ./freesbie.iso -u 4 mount -t cd9660 /dev/md4 /tmp/mnt1 The output of 'mount' showed: on /tmp/mnt1 (cd9660, local, read-only) i.e. it did not show "/dev/md4 on" I mounted an NFS filesystem via the automounter: cd /net/rincewind-2/opt/home/ACE_wrappers The output of 'mount' showed: rincewind-2:/opt/home/ACE_wrappers on XXX: foo (nfs, nosuid) i.e it did not show 'on /net/rincewind-2'. I tried to mount the same NFS file system via nfs4: mount_nfs4 rincewind-2:/opt/home/ACE_wrappers /tmp/mnt1 mount_nfs4: /tmp/mnt1: Operation not supported -- Craig Rodrigues rodrigc@crodrigues.org From owner-freebsd-current@FreeBSD.ORG Sun Dec 5 23:56:09 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 774ED16A4EA; Sun, 5 Dec 2004 23:56:09 +0000 (GMT) Received: from smtp3.server.rpi.edu (smtp3.server.rpi.edu [128.113.2.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DA2843D1D; Sun, 5 Dec 2004 23:56:09 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp3.server.rpi.edu (8.13.0/8.13.0) with ESMTP id iB5Nu7Wt018060; Sun, 5 Dec 2004 18:56:08 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: <41B34F8D.5030401@freebsd.org> References: <56325.1102236241@critter.freebsd.dk> <41B34F8D.5030401@freebsd.org> Date: Sun, 5 Dec 2004 18:56:07 -0500 To: Tim Kientzle , Poul-Henning Kamp From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) cc: current@freebsd.org Subject: Re: [TEST/REVIEW]: rootfs mounting code rework X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2004 23:56:09 -0000 At 10:12 AM -0800 12/5/04, Tim Kientzle wrote: > >Here's a situation that may be worth thinking about: > > * Working FreeBSD system that uses a > separate controller. / is /dev/da4. > > * Controller blows up. > > * Connect hard disk to the on-board controller. > >Note: kernel is now being loaded from /dev/da0, but /etc/fstab >still says / is /dev/da4. With the old rootfs code, this system >is unbootable. This is the kind of situation I was thinking of, where you get into a mess due to some hardware shuffling. It does not come up often, but it can be frustrating when you do run into it. I was just wondering if Poul's work might help in that situation. In a later message, Poul-Henning Kamp wrote: >First: I have _not_ changed the logic that decides _which_ rootfs >to mount, only the mechanics of how it is mounted. > >Second: I belive you could simply type something like: > > set vfs.root.mountfrom="ufs:/dev/da0" > >in the loader and your system would do what you expect it to. Ah, very good. I'll save that away for future reference. So with your changes, should we just check to see that it works the same as it used to work? Or is there any kind of new behavior that we should try to exercise? -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 00:44:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9AB716A4FE for ; Mon, 6 Dec 2004 00:44:30 +0000 (GMT) Received: from sb.santaba.com (sb.santaba.com [207.154.84.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8888543D48 for ; Mon, 6 Dec 2004 00:44:30 +0000 (GMT) (envelope-from jbehl@fastclick.com) Received: from [192.168.1.100] (ip68-6-38-163.sb.sd.cox.net [68.6.38.163]) by sb.santaba.com (Postfix) with ESMTP id 25B9128433; Sun, 5 Dec 2004 16:44:30 -0800 (PST) Message-ID: <41B3AB74.6050801@fastclick.com> Date: Sun, 05 Dec 2004 16:44:36 -0800 From: Jeff Behl User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Barney Wolff References: <20041205170808.GA96727@pit.databus.com> In-Reply-To: <20041205170808.GA96727@pit.databus.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: mbuf count negative X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 00:44:30 -0000 even better: 442444 mbufs in use 18446744073709494664/25600 mbuf clusters in use (current/max) 0/0/0 sfbufs in use (current/peak/max) 18014398509478691 KBytes allocated to network 0 requests for sfbufs denied 0 requests for sfbufs delayed 0 requests for I/O initiated by sendfile 8 calls to protocol drain routines uname -a: FreeBSD www1.cdn.wdc 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Wed Nov 17 16:54:49 PST 2004 root@www1.cdn.wdc:/usr/obj/usr/src/sys/SMP amd64 i've seen this on all iterations of 5.3 (betas/current). this is also a dual proc amd system (opteron)... Barney Wolff wrote: >Is anybody else seeing this? > >lab:/root # netstat -m >4294959731 mbufs in use >1170/25600 mbuf clusters in use (current/max) >0/3/6656 sfbufs in use (current/peak/max) >448 KBytes allocated to network >0 requests for sfbufs denied >0 requests for sfbufs delayed >0 requests for I/O initiated by sendfile >650 calls to protocol drain routines >lab:/root # uname -a >FreeBSD lab.databus.com 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Fri Dec 3 21:44:57 EST 2004 toor@lab.databus.com:/usr/obj/usr/src/sys/LAB i386 > >It happens almost instantly during periodic when the system is used to >receive a backup via nfs. Normal operation, including a dozen hours of >port building, does not cause it. It is consistent, 3 times now. > >H/W is Asus A7M266-D with 2xAthlon 2200MP, 1GB, 39160, gvinum, em. > >Problem did not occur with prior -current from 11/19/04. Other than cvsup, >I changed make.conf to say CPUTYPE=athlon-mp (was i686 or nothing). > >What can I do to help debug this? > > > From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 02:40:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E35216A4CE for ; Mon, 6 Dec 2004 02:40:33 +0000 (GMT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1048643D60 for ; Mon, 6 Dec 2004 02:40:33 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 21629 invoked from network); 6 Dec 2004 02:40:32 -0000 Received: from gate.funkthat.com (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 6 Dec 2004 02:40:32 -0000 Received: from hydrogen.funkthat.com (nkdqte@localhost.funkthat.com [127.0.0.1])iB62eVGH096012; Sun, 5 Dec 2004 18:40:31 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id iB62eUdQ096011; Sun, 5 Dec 2004 18:40:30 -0800 (PST) Date: Sun, 5 Dec 2004 18:40:30 -0800 From: John-Mark Gurney To: Tim Kientzle Message-ID: <20041206024030.GM19624@funkthat.com> Mail-Followup-To: Tim Kientzle , Poul-Henning Kamp , Garance A Drosihn , current@freebsd.org References: <56325.1102236241@critter.freebsd.dk> <41B34F8D.5030401@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41B34F8D.5030401@freebsd.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE 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: Poul-Henning Kamp cc: Garance A Drosihn cc: current@freebsd.org Subject: Re: [TEST/REVIEW]: rootfs mounting code rework X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 02:40:33 -0000 Tim Kientzle wrote this message on Sun, Dec 05, 2004 at 10:12 -0800: > Here's a situation that may be worth thinking > about: > > * Working FreeBSD system that uses > a separate controller. / is /dev/da4. > > * Controller blows up. > > * Connect hard disk to the on-board controller. > > Note: kernel is now being loaded from /dev/da0, > but /etc/fstab still says / is /dev/da4. > With the old rootfs code, this system is > unbootable. > > I hope you've considered situations like this. Simply boot single user mode, update /etc/fstab and reboot.. if you really care, then you should be using labeled providers, and then it'll just magicly work... assuming you use the label provider in your /etc/fstab.. I don't think we should EVER magicly mount root if /etc/fstab disagrees.. Unix is suppose to do what you tell it to... If /dev/ad4 doesn't exist anymore, then it shouldn't boot until you fix it.. -- 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-current@FreeBSD.ORG Mon Dec 6 03:45:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9921C16A4CE for ; Mon, 6 Dec 2004 03:45:31 +0000 (GMT) Received: from duchess.speedfactory.net (duchess.speedfactory.net [66.23.201.84]) by mx1.FreeBSD.org (Postfix) with SMTP id F2A8543D48 for ; Mon, 6 Dec 2004 03:45:30 +0000 (GMT) (envelope-from ups@tree.com) Received: (qmail 31303 invoked by uid 89); 6 Dec 2004 03:45:28 -0000 Received: from duchess.speedfactory.net (66.23.201.84) by duchess.speedfactory.net with SMTP; 6 Dec 2004 03:45:28 -0000 Received: (qmail 31283 invoked by uid 89); 6 Dec 2004 03:45:28 -0000 Received: from unknown (HELO palm.tree.com) (66.23.216.49) by duchess.speedfactory.net with SMTP; 6 Dec 2004 03:45:28 -0000 Received: from [127.0.0.1] (localhost.tree.com [127.0.0.1]) by palm.tree.com (8.12.10/8.12.10) with ESMTP id iB63jN9k059246; Sun, 5 Dec 2004 22:45:23 -0500 (EST) (envelope-from ups@tree.com) From: Stephan Uphoff To: Robert Watson In-Reply-To: References: Content-Type: text/plain Message-Id: <1102304723.56978.113.camel@palm.tree.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 05 Dec 2004 22:45:23 -0500 Content-Transfer-Encoding: 7bit cc: Barney Wolff cc: "current@freebsd.org" Subject: Re: mbuf count negative X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 03:45:31 -0000 On Sun, 2004-12-05 at 14:08, Robert Watson wrote: > On Sun, 5 Dec 2004, Sean McNeil wrote: > > > > It replaces non-atomic maintenance of the counters with atomic > > > maintenance. However, this adds measurably to the cost of allocation, so > > > I've been reluctant to commit it. The counters maintained by UMA are > > > likely sufficient to generate the desired mbuf output now that we have > > > mbuma, but I haven't had an opportunity to walk through the details of it. > > > I hope to do so once I get closer to merging patches to use critical > > > sections to protect UMA per-cpu caches, since I need to redo parts of the > > > sysctl code then anyway. You might want to give this patch, or one much > > > like it, a spin to confirm that the race is the one I think it is. The > > > race in updating mbuf allocator statistics is one I hope to get fixed > > > prior to 5.4. > > > > Since they appear to not be required for actual system use (by the fact > > that it being negative doesn't cause problems), could the counts be > > computed for display instead? > > This is pretty much what UMA does with its per-CPU caches. It pulls and > pushes statistics from the caches in a couple of situations: > > - When pulling a new bucket into or out of the cache, it has to acquire > the zone mutex, so also pushes statistics. > - When a timer fires every few seconds, all the caches are checked to > update the global zone statistics. > - When the sysctl runs, it replicates the logic in the timer code to also > update the zone statistics for display. > > And you can already extract pretty much all of the interesting allocation > information for mbufs from vmstat -z as the mbufs are now stored using > UMA. In the critical section protected version of the code, I haven't yet > decided if the timers should run per-cpu, and/or how the sysctl should > coalesce the information for display. I hope to have much of this > resolved shortly. My current leaning is that a small amount of localized > and temporary inconsistency in the stats isn't a problem, so simply doing > a set of lockless reads across the per-cpu caches to update stats for > presentation should be fine, and that we can probably drop the timer > updates of statistics since the cache bucket balancing keeps things pretty > in sync. > > I haven't committed the move to critical sections yet as it's currently a > performance pessimization for the UP case, as entering a critical section > on UP is more expensive than acquiring a mutex. John Baldwin has patches > that remedy this, but hasn't yet merged them (there's also an instability > with them I've seen). I know that Stephen Uphoff has also been > investigating this issue. I am wondering if critical sections are overkill for this application since the interrupt blocking capability is not needed. Perhaps a mutex_lock_local, mutex_unlock_local that work on per CPU mutexes and require the current thread to be pinned to a CPU would be more appropriate. The functions would have the same functionality as mutex_lock/mutex_unlock but without using atomic operations. The "local" mutex would be a clone of the UP sleep mutex and the SMP sleep mutex and the local mutex could even be used together in any order. (With working priority inheritance) I think I will try this in my p4 mutex branch in the next days. A "do not preempt" section (Interrupt enabled) would be another possibility. Stephan From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 06:04:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D353816A4CE for ; Mon, 6 Dec 2004 06:04:31 +0000 (GMT) Received: from www.mmlab.cse.yzu.edu.tw (www.mmlab.cse.yzu.edu.tw [140.138.150.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5434543D5D for ; Mon, 6 Dec 2004 06:04:29 +0000 (GMT) (envelope-from avatar@mmlab.cse.yzu.edu.tw) Received: by www.mmlab.cse.yzu.edu.tw (qmail, from userid 1000) id E9F904EFCD3; Mon, 6 Dec 2004 14:04:26 +0800 (CST) Received: from localhost (localhost [127.0.0.1]) by www.mmlab.cse.yzu.edu.tw (qmail) with ESMTP id E02894EFCD0; Mon, 6 Dec 2004 14:04:26 +0800 (CST) Date: Mon, 6 Dec 2004 14:04:26 +0800 (CST) From: Tai-hwa Liang To: Josh Tolbert In-Reply-To: <20041202211601.GA12673@just.puresimplicity.net> Message-ID: <04120613590712.22997@www.mmlab.cse.yzu.edu.tw> References: <20041202002939.GA2834@ns1.xcllnt.net> <16815.31852.46550.983276@jerusalem.litteratus.org> <20041202211601.GA12673@just.puresimplicity.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: Robert Huff cc: current@freebsd.org Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 06:04:31 -0000 On Thu, 2 Dec 2004, Josh Tolbert wrote: > On Thu, Dec 02, 2004 at 03:34:52PM -0500, Robert Huff wrote: >> Marcel Moolenaar writes: >> >>> > 1. Keyboard multiplexer. >>> >>> I actually fail to stop thinking about a complete syscons and >>> pcvt replacement. You know, the one and only console >>> implementation that makes all others obsolete. Big plans, little >>> time, yada yada yada... >> >> As long as we're talking about keyboards ... may I add "Get the >> boot code to recognize USB keyboards." >> (Unless this has already happened and I missed the meno. >> Again.) >> >> >> Robert Huff > > As long as we're talking about keyboards, re-vamping the console driver, etc., > can something be done with psm? FreeBSD is the only OS that requires me to > pass flags to psm to get my mouse to behave properly on my KVM switch, and the > flag I use (0x200) forces "true" PS/2 mode, disabling the wheel and such. > > Granted, the only other OSes I've had on KVM switches with FreeBSD machines > are Windows, Linux and OS/X, but it still seems like something's amiss with > psm. > > Thanks, > Josh Agreed. That's exactly the same workaround I have to apply on my device.hints. Without 0x200, my PS/2 mouse doesn't work with the Lextek ConsoleManager Smart KVM Switch. kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 And yes, Linux/Windoze doesn't need any tweaking to get such combination work.... From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 06:28:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E7AC16A4CE for ; Mon, 6 Dec 2004 06:28:45 +0000 (GMT) Received: from smtp1.server.rpi.edu (smtp1.server.rpi.edu [128.113.2.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id B85EA43D60 for ; Mon, 6 Dec 2004 06:28:44 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp1.server.rpi.edu (8.13.0/8.13.0) with ESMTP id iB66SaN3026126; Mon, 6 Dec 2004 01:28:38 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Mon, 6 Dec 2004 01:28:35 -0500 To: freebsd-current@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) cc: =?iso-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: Another twist on WRITE_DMA issues <- ProblemFound X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 06:28:45 -0000 At 9:31 PM -0500 12/2/04, Garance A Drosihn wrote: > >I have now switched from that Western Digital drive to a Seagate >Barracuda 7200.7 120-gig (ST3120026AS). The drive seems to be >working fairly well, but now I sometimes see some combination >like the following three lines: > >Dec 2 20:29:50 kernel: Interrupt storm detected on > "irq20: atapci0"; throttling interrupt source >Dec 2 20:29:54 kernel: ad4: TIMEOUT - WRITE_DMA retrying > (2 retries left) LBA=20627679 >Dec 2 20:29:54 kernel: ad4: FAILURE - WRITE_DMA timed out > >Where atapci0: >And >ad4: 114473MB [232581/16/63] at ata2-master SATA150 > >This does not come up often, and it usually doesn't cause any >noticeable problem. As it luck would have it, the one time it has >caused problems is during installworlds. ... It has caused problems on many other occasions, too. But in any case, it looks like this set of problems are my own fault. Earlier, I spent about two months trying to solve problems on this PC which (it turned out) were due to the SiL SATA controller combined with the western-digital drive. Just before I realized that SATA controller was the problem, I had added: hw.ata.ata_dma=0 to /boot/loader.conf.local, because someone else had suggested that it *might* help with my earlier WRITE_DMA problems. At that time, the setting seemed to make no difference. But now that I am using a good SATA controller *and* I have switched to the "real-SATA" hard drive from Seagate, the above setting seems to *cause* problems. I removed that setting, rebooted, and I have now done a complete buildworld/installworld cycle without seeing a single "interrupt storm" or a single WRITE_DMA error. While the setting was still there, I would always see at least a few of those warning messages (and sometimes end up with a system panic). So, my hope is that this has finally solved the last of my problems with this machine. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 06:30:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85EE016A4D7; Mon, 6 Dec 2004 06:30:57 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5BB043D3F; Mon, 6 Dec 2004 06:30:56 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB66Utst075756; Mon, 6 Dec 2004 07:30:55 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Garance A Drosihn From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sun, 05 Dec 2004 18:56:07 EST." Date: Mon, 06 Dec 2004 07:30:55 +0100 Message-ID: <75755.1102314655@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: Tim Kientzle cc: current@freebsd.org Subject: Re: [TEST/REVIEW]: rootfs mounting code rework X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 06:30:57 -0000 In message , Garance A Drosihn writes: >So with your changes, should we just check to see that it works >the same as it used to work? Or is there any kind of new >behavior that we should try to exercise? It should be all the same as usual. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 06:38:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB8D916A4D0 for ; Mon, 6 Dec 2004 06:38:00 +0000 (GMT) Received: from pimout1-ext.prodigy.net (pimout1-ext.prodigy.net [207.115.63.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F46143D49 for ; Mon, 6 Dec 2004 06:37:58 +0000 (GMT) (envelope-from julian@elischer.org) Received: from [192.168.1.102] (adsl-68-123-122-146.dsl.snfc21.pacbell.net [68.123.122.146])iB66bp6M253484; Mon, 6 Dec 2004 01:37:52 -0500 Message-ID: <41B3FE3E.3070407@elischer.org> Date: Sun, 05 Dec 2004 22:37:50 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8a3) Gecko/20041017 X-Accept-Language: en, hu MIME-Version: 1.0 To: Poul-Henning Kamp References: <57430.1102240929@critter.freebsd.dk> In-Reply-To: <57430.1102240929@critter.freebsd.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Jeff Roberson cc: Garance A Drosihn cc: current@freebsd.org Subject: Re: [TEST/REVIEW]: rootfs mounting code rework X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 06:38:00 -0000 Poul-Henning Kamp wrote: > In message <20041205044145.A18185@mail.chesapeake.net>, Jeff Roberson writes: > >>On Sun, 5 Dec 2004, Poul-Henning Kamp wrote: >> >> >>>In message , Garance A Drosihn writes: >>> >>>>At 11:08 AM +0100 12/4/04, Poul-Henning Kamp wrote: >>>> >>>>>http://phk.freebsd.dk/patch/rootfs.patch >>>>> >>>>>Please test and review. >>>> >>>>Hmm. Does this mean that we'll always get the correct partition >>>>for '/', even if /etc/fstab is wrong for '/'? By "correct", I >>>>mean "the partition that the kernel was loaded from". >>> >>>The loader reads /etc/fstab and picks the entry for '/' out of it >>>so I can only pressume that whoever did that disagree with your >>>notion of "correct". >> >>I believe he's referring to the case where you load a kernel from >>somewhere other than the default '/'. > > > I'm not sure, and I don't really care much. The order in which the > kernel tries various root filesystems is not affected apart from me > removing the "ask" mode which is badly implemented, prone to problems > and unecessary now that we can set it in the loader. Where it's not documented well enough to use in an emergency, while the "ask" mode had a good example right there in front of you.. saved my bacon several times. > From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 06:46:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B485216A4CE for ; Mon, 6 Dec 2004 06:46:20 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49CE843D48 for ; Mon, 6 Dec 2004 06:46:20 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: by rproxy.gmail.com with SMTP id 40so20954rnz for ; Sun, 05 Dec 2004 22:46:19 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=ZmtnvzF09Scu3MEv3cRkNNwwaCexfend/sij4aYVXcCxqK6KRdC9cTnUeqG9V2LVlInRQJVoA75Fgx3pktvtsMrZzYWIThbuDe5AJWH2eNH9r1e9F4uLhPyeCTLci62auC5Zm0VLbZr+k53uztlTUsS1pUTjh0PkZmdUqpMRTHE= Received: by 10.38.8.40 with SMTP id 40mr1262313rnh; Sun, 05 Dec 2004 22:46:19 -0800 (PST) Received: by 10.38.8.31 with HTTP; Sun, 5 Dec 2004 22:46:19 -0800 (PST) Message-ID: Date: Mon, 6 Dec 2004 14:46:19 +0800 From: Jiawei Ye To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: sockstat weirdness X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jiawei Ye List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 06:46:20 -0000 With the latest -current (3 hrs old), my box says: leafy@chihiro:~$ sockstat sockstat: sysctlbyname(): No such file or directory What have I missed here? Jiawei -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 07:15:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C410716A4CE; Mon, 6 Dec 2004 07:15:47 +0000 (GMT) Received: from pd3mo3so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA94543D5C; Mon, 6 Dec 2004 07:15:44 +0000 (GMT) (envelope-from colin.percival@wadham.ox.ac.uk) Received: from pd5mr7so.prod.shaw.ca (pd5mr7so-qfe3.prod.shaw.ca [10.0.141.183]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0I8A00E2FHH5O2F0@l-daemon>; Mon, 06 Dec 2004 00:15:05 -0700 (MST) Received: from pn2ml10so.prod.shaw.ca ([10.0.121.80]) by pd5mr7so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0I8A003E5HH57540@pd5mr7so.prod.shaw.ca>; Mon, 06 Dec 2004 00:15:05 -0700 (MST) Received: from [192.168.0.60] (S0106006067227a4a.vc.shawcable.net [24.87.233.42])2003)) with ESMTP id <0I8A00G6PHH4Q2@l-daemon>; Mon, 06 Dec 2004 00:15:04 -0700 (MST) Date: Sun, 05 Dec 2004 23:15:04 -0800 From: Colin Percival In-reply-to: To: Jiawei Ye Message-id: <41B406F8.1000409@wadham.ox.ac.uk> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime References: User-Agent: Mozilla Thunderbird 0.9 (X11/20041107) cc: freebsd-current@freebsd.org Subject: Re: sockstat weirdness X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 07:15:47 -0000 Jiawei Ye wrote: > leafy@chihiro:~$ sockstat > sockstat: sysctlbyname(): No such file or directory > > What have I missed here? You haven't missed anything, it's broken. In revision 1.11 of src/usr.bin/sockstat/sockstat.c code was added which uses the net.inet.divert.pcblist sysctl. Unfortunately, this might not exist, so sockstat(8) gets legitimately unhappy. I'd guess that the right solution would be to replace line 226 err(1, "sysctlbyname()"); with goto out; but I'm not sure; ru, could you tell me if this is correct and/or fix it yourself? Colin Percival From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 07:39:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BF8316A4CE; Mon, 6 Dec 2004 07:39:10 +0000 (GMT) Received: from lp1001.snu.ac.kr (lp1001.snu.ac.kr [147.46.70.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id A87F543D80; Mon, 6 Dec 2004 07:39:09 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: from [147.46.44.181] (cisr.snu.ac.kr [147.46.44.181]) (authenticated (0 bits)) by lp1001.snu.ac.kr (8.13.1/8.11.6) with ESMTP id iB67awdv015570; Mon, 6 Dec 2004 16:36:58 +0900 Message-ID: <41B40C97.7000102@yahoo.com> Date: Mon, 06 Dec 2004 16:39:03 +0900 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org, freebsd-current Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: names of supfiles in /usr/share/examples/cvsup X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 07:39:10 -0000 Hi, For 5.3 in /usr/share/examples/cvsup, there's: stable-supfile : for FreeBSD-stable standard-supfile : for FreeBSD-current I find this naming rather confusing. Why "stable" refers to STABLE, but "standard" refers to CURRENT ? This causes unnecessary confusion. Why not the following name convention: release-supfile : for FreeBSD-RELEASE stable-supfile : for FreeBSD-STABLE current-supfile : for FreeBSD-CURRENT as default supplied files in /usr/share/examples/cvsup ? At least the naming of files is then very obvious for people who start learning about the cvsup stuff. ------------- Another point, which I miss in the guidelines for using these files: I would advice people to do one of following (whatever appropriate) cvsup -h your.nearest.server.org /usr/share/examples/cvsup/release-supfile cvsup -h your.nearest.server.org /usr/share/examples/cvsup/stable-supfile cvsup -h your.nearest.server.org /usr/share/examples/cvsup/current-supfile instead of copying the files and edit them. Usually one only needs to modify the server's hostname; the -h option can do that in an easier way. Regards, Rob. From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 08:58:12 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B5EC16A4CE; Mon, 6 Dec 2004 08:58:12 +0000 (GMT) Received: from mail.ciam.ru (mail.ciam.ru [213.147.57.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3C6D43D5E; Mon, 6 Dec 2004 08:58:11 +0000 (GMT) (envelope-from sem@FreeBSD.org) Received: from ppp83-237-98-132.pppoe.mtu-net.ru ([83.237.98.132]) by mail.ciam.ru with esmtpa (Exim 4.x) id 1CbEh8-000P7E-9w; Mon, 06 Dec 2004 11:58:10 +0300 Message-ID: <41B41F32.4030205@FreeBSD.org> Date: Mon, 06 Dec 2004 11:58:26 +0300 From: Sergey Matveychuk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ruslan Ermilov References: <41B35BFB.2060100@FreeBSD.org> <20041205200214.GA65263@ip.net.ua> In-Reply-To: <20041205200214.GA65263@ip.net.ua> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: nVidia nForce2 sound X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 08:58:12 -0000 Ruslan Ermilov wrote: > I've the same problem on my AMD64 box. kldload'ing > snd_ich and some other modules from user mode does > not work. Pre-loading modules from loader(8) works. That's it! Thank you, Ruslan. -- Sem. From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 09:18:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2118516A4CE for ; Mon, 6 Dec 2004 09:18:52 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B34FE43D45 for ; Mon, 6 Dec 2004 09:18:51 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iB69GUft059079; Mon, 6 Dec 2004 04:16:30 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iB69GUSM059076; Mon, 6 Dec 2004 09:16:30 GMT (envelope-from robert@fledge.watson.org) Date: Mon, 6 Dec 2004 09:16:30 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Stephan Uphoff In-Reply-To: <1102304723.56978.113.camel@palm.tree.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Barney Wolff cc: "current@freebsd.org" Subject: Re: mbuf count negative X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 09:18:52 -0000 On Sun, 5 Dec 2004, Stephan Uphoff wrote: > I am wondering if critical sections are overkill for this application > since the interrupt blocking capability is not needed. > > Perhaps a mutex_lock_local, mutex_unlock_local that work on per CPU > mutexes and require the current thread to be pinned to a CPU would be > more appropriate. The functions would have the same functionality as > mutex_lock/mutex_unlock but without using atomic operations. The > "local" mutex would be a clone of the UP sleep mutex and the SMP sleep > mutex and the local mutex could even be used together in any order. > (With working priority inheritance) I think I will try this in my p4 > mutex branch in the next days. > > A "do not preempt" section (Interrupt enabled) would be another > possibility. Silby suggested a UP mutex implementation on SMP to use with pinned threads a month or two ago, and that would work just fine here; I was having similar thoughts also -- while the critical sections are brief, there's really no reason not to allow preemption there. However, the critical section optimizations that I was referring to from John basically do what you suggest second: they implement critical sections via a software "Don't preempt". I don't really mind what the mechanism is, as long as they neither invoke cli/sti or use atomic operations, and it should be possible to easily substitute in the UMA code once my patch is in place. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 09:19:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71D5916A4CE for ; Mon, 6 Dec 2004 09:19:49 +0000 (GMT) Received: from smtp-vbr4.xs4all.nl (smtp-vbr4.xs4all.nl [194.109.24.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 517E443D31 for ; Mon, 6 Dec 2004 09:19:48 +0000 (GMT) (envelope-from michiel@boland.org) Received: from xs6.xs4all.nl (xs6.xs4all.nl [194.109.21.6]) by smtp-vbr4.xs4all.nl (8.12.11/8.12.11) with ESMTP id iB69JkZG091775 for ; Mon, 6 Dec 2004 10:19:47 +0100 (CET) (envelope-from michiel@boland.org) Received: from xs6.xs4all.nl (boland37@localhost.xs4all.nl [127.0.0.1]) by xs6.xs4all.nl (8.12.10/8.12.10) with ESMTP id iB69Jkjl034255 for ; Mon, 6 Dec 2004 10:19:46 +0100 (CET) (envelope-from michiel@boland.org) Received: (from boland37@localhost) by xs6.xs4all.nl (8.12.10/8.12.9/Submit) id iB69Jfk8034254 for current@freebsd.org; Mon, 6 Dec 2004 10:19:41 +0100 (CET) (envelope-from michiel@boland.org) X-Authentication-Warning: xs6.xs4all.nl: boland37 set sender to michiel@boland.org using -f Date: Mon, 6 Dec 2004 10:19:41 +0100 From: Michiel Boland To: current@freebsd.org Message-ID: <20041206091941.GA23932@xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Virus-Scanned: by XS4ALL Virus Scanner Subject: mkdir in /dev causes crash X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 09:19:49 -0000 Hi. If I create a directory in /dev, the kernel crashes at kern_mkdir+0x293: movl 0x60,%ecx (Sorry, I forgot to take the console output to work, so I don't have much more info.) I guess this is related to changes made to /sys/fs/devfs/devfs_vnops.c et al? I'll try to put this into a PR, unless someone can spot immediately where the problem lies. Cheers Michiel From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 09:29:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2BD8516A4CE for ; Mon, 6 Dec 2004 09:29:02 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6000D43D2D for ; Mon, 6 Dec 2004 09:29:01 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB69T0tM065740; Mon, 6 Dec 2004 11:29:00 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 35822-02; Mon, 6 Dec 2004 11:28:59 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB69Sx8p065737 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 6 Dec 2004 11:28:59 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iB69T2G0008195; Mon, 6 Dec 2004 11:29:02 +0200 (EET) (envelope-from ru) Date: Mon, 6 Dec 2004 11:29:01 +0200 From: Ruslan Ermilov To: Colin Percival Message-ID: <20041206092901.GB7976@ip.net.ua> References: <41B406F8.1000409@wadham.ox.ac.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LwW0XdcUbUexiWVK" Content-Disposition: inline In-Reply-To: <41B406F8.1000409@wadham.ox.ac.uk> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: freebsd-current@FreeBSD.org cc: Jiawei Ye Subject: Re: sockstat weirdness X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 09:29:02 -0000 --LwW0XdcUbUexiWVK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 05, 2004 at 11:15:04PM -0800, Colin Percival wrote: > Jiawei Ye wrote: > >leafy@chihiro:~$ sockstat > >sockstat: sysctlbyname(): No such file or directory > > > >What have I missed here? >=20 > You haven't missed anything, it's broken. In revision 1.11 of > src/usr.bin/sockstat/sockstat.c code was added which uses the > net.inet.divert.pcblist sysctl. Unfortunately, this might not > exist, so sockstat(8) gets legitimately unhappy. >=20 > I'd guess that the right solution would be to replace line 226 > err(1, "sysctlbyname()"); > with > goto out; > but I'm not sure; ru, could you tell me if this is correct and/or > fix it yourself? >=20 I've committed a better fix in revision 1.12. Thanks! Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --LwW0XdcUbUexiWVK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBtCZdqRfpzJluFF4RAg9BAJ9nJwgwAagIuK0X80+LXiw6psiLYgCfXmSj hPU71pZHe6/3u3urxgB8aIA= =v2Jk -----END PGP SIGNATURE----- --LwW0XdcUbUexiWVK-- From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 09:29:19 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9AC5616A4D0 for ; Mon, 6 Dec 2004 09:29:19 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D13C43D73 for ; Mon, 6 Dec 2004 09:29:18 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB69T6K3078804; Mon, 6 Dec 2004 10:29:06 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Michiel Boland From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 06 Dec 2004 10:19:41 +0100." <20041206091941.GA23932@xs4all.nl> Date: Mon, 06 Dec 2004 10:29:06 +0100 Message-ID: <78803.1102325346@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@freebsd.org Subject: Re: mkdir in /dev causes crash X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 09:29:19 -0000 In message <20041206091941.GA23932@xs4all.nl>, Michiel Boland writes: >Hi. If I create a directory in /dev, the kernel crashes at > > kern_mkdir+0x293: movl 0x60,%ecx > >(Sorry, I forgot to take the console output to work, so I don't have >much more info.) > >I guess this is related to changes made to /sys/fs/devfs/devfs_vnops.c >et al? Right off the top of my head I can't reproduce it: syv# mkdir /dev/foo mkdir: /dev/foo: Operation not supported syv# mkdir /dev/tty mkdir: /dev/tty: File exists -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 09:53:09 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C89F16A4CE for ; Mon, 6 Dec 2004 09:53:09 +0000 (GMT) Received: from smtp-vbr8.xs4all.nl (smtp-vbr8.xs4all.nl [194.109.24.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id E229A43D45 for ; Mon, 6 Dec 2004 09:53:08 +0000 (GMT) (envelope-from michiel@boland.org) Received: from xs6.xs4all.nl (xs6.xs4all.nl [194.109.21.6]) by smtp-vbr8.xs4all.nl (8.12.11/8.12.11) with ESMTP id iB69r7T3016525; Mon, 6 Dec 2004 10:53:07 +0100 (CET) (envelope-from michiel@boland.org) Received: from xs6.xs4all.nl (boland37@localhost.xs4all.nl [127.0.0.1]) by xs6.xs4all.nl (8.12.10/8.12.10) with ESMTP id iB69r7jl068296; Mon, 6 Dec 2004 10:53:07 +0100 (CET) (envelope-from michiel@boland.org) Received: (from boland37@localhost) by xs6.xs4all.nl (8.12.10/8.12.9/Submit) id iB69r70K068277; Mon, 6 Dec 2004 10:53:07 +0100 (CET) (envelope-from michiel@boland.org) X-Authentication-Warning: xs6.xs4all.nl: boland37 set sender to michiel@boland.org using -f Date: Mon, 6 Dec 2004 10:53:07 +0100 From: Michiel Boland To: Poul-Henning Kamp Message-ID: <20041206095306.GA60091@xs4all.nl> References: <20041206091941.GA23932@xs4all.nl> <78803.1102325346@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <78803.1102325346@critter.freebsd.dk> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by XS4ALL Virus Scanner cc: current@freebsd.org Subject: Re: mkdir in /dev causes crash X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 09:53:09 -0000 The problem is gone. CVSuped at a bad time. Sorry about noise. From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 13:59:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C19D16A4CE for ; Mon, 6 Dec 2004 13:59:39 +0000 (GMT) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.FreeBSD.org (Postfix) with SMTP id 8E20743D6D for ; Mon, 6 Dec 2004 13:59:38 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 28110 invoked from network); 6 Dec 2004 13:59:36 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 6 Dec 2004 13:59:36 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iB6DxYAN024289; Mon, 6 Dec 2004 14:59:34 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iB6DxYEM024288; Mon, 6 Dec 2004 14:59:34 +0100 (CET) (envelope-from pho) Date: Mon, 6 Dec 2004 14:59:34 +0100 From: Peter Holm To: John Baldwin Message-ID: <20041206135934.GA24238@peter.osted.lan> References: <20041112123343.GA12048@peter.osted.lan> <200411151546.15533.jhb@FreeBSD.org> <20041119075924.GA22320@peter.osted.lan> <200411191710.19215.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200411191710.19215.jhb@FreeBSD.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@FreeBSD.org cc: bmilekic@FreeBSD.org cc: jeffr@FreeBSD.org cc: jroberson@chesapeake.net Subject: Re: Freeze X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 13:59:39 -0000 On Fri, Nov 19, 2004 at 05:10:19PM -0500, John Baldwin wrote: > On Friday 19 November 2004 02:59 am, Peter Holm wrote: > > On Mon, Nov 15, 2004 at 03:46:15PM -0500, John Baldwin wrote: > > > On Friday 12 November 2004 07:33 am, Peter Holm wrote: > > > > GENERIC HEAD from Nov 11 08:05 UTC > > > > > > > > The following stack traces etc. was done before my first > > > > cup of coffee, so it's not so informative as it could have been :-( > > > > > > > > The test box appeared to have been frozen for more than 6 hours, > > > > but was pingable. > > > > > > > > http://www.holm.cc/stress/log/cons86.html > > > > > > A weak guess is that you have the system in some sort of livelock due to > > > fork()? Have you tried running with 'debug.mpsafevm=1' set from the > > > loader? > > > > > > -- > > > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > > > "Power Users Use the Power to Serve" = http://www.FreeBSD.org > > > > OK, I've got some more info: > > > > http://www.holm.cc/stress/log/cons88.html > > > > Looks like a spin in uma_zone_slab() when slab_zalloc() fails? > > Yes, I think if you specify M_WAITOK, then that might happen. slab_zalloc() > can fail if any of the init functions fail for example, in which case it > would loop forever. You can try this hack (though it may very well be wrong) > to return failure if that is what is triggering: > > Index: uma_core.c > =================================================================== > RCS file: /usr/cvs/src/sys/vm/uma_core.c,v > retrieving revision 1.110 > diff -u -r1.110 uma_core.c > --- uma_core.c 6 Nov 2004 11:43:30 -0000 1.110 > +++ uma_core.c 19 Nov 2004 22:08:26 -0000 > @@ -1998,6 +1998,10 @@ > */ > if (flags & M_NOWAIT) > flags |= M_NOVM; > + > + /* XXXHACK */ > + if (flags & M_WAITOK) > + break; > } > return (slab); > } > > -- > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve" = http://www.FreeBSD.org I instrumented the code with this: $ cvs diff -u cvs diff: Diffing . Index: uma_core.c =================================================================== RCS file: /home/ncvs/src/sys/vm/uma_core.c,v retrieving revision 1.110 diff -u -r1.110 uma_core.c --- uma_core.c 6 Nov 2004 11:43:30 -0000 1.110 +++ uma_core.c 6 Dec 2004 13:49:36 -0000 @@ -1926,6 +1926,7 @@ { uma_slab_t slab; uma_keg_t keg; + int i; keg = zone->uz_keg; @@ -1943,7 +1944,8 @@ slab = NULL; - for (;;) { + for (i = 0;;i++) { + KASSERT(i < 10000, ("uma_zone_slab is looping")); /* * Find a slab with some space. Prefer slabs that are partially * used over those that are totally full. This helps to reduce and now during test of Jeff Roberson's "SMP FFS" patch the assert triggered: http://www.holm.cc/stress/log/cons92.html -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 16:01:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC42E16A4CE for ; Mon, 6 Dec 2004 16:01:03 +0000 (GMT) Received: from pozo.com (pozo.com [216.101.162.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E24443D1F for ; Mon, 6 Dec 2004 16:01:03 +0000 (GMT) (envelope-from null@pozo.com) Received: from sunpci.pozo.com (sunpci.pozo.com [192.168.0.29]) (authenticated bits=0) by pozo.com (8.13.1/8.13.1) with ESMTP id iB6G10dB000694 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 6 Dec 2004 08:01:01 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <6.2.0.14.2.20041206075313.03e74db8@pozo.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Mon, 06 Dec 2004 08:01:01 -0800 To: current@freebsd.org From: Manfred Antar Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: dump broken with new kernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 16:01:03 -0000 When I try to do a dump of the root filesystem I get : mksnap_ffs: Cannot create //.snap/dump_snapshot: Invalid argument dump: Cannot create //.snap/dump_snapshot: No such file or directory A kernel from a week ago works fine. The command I'm using is: dump 0Lfua /dev/nsa0 /dev/ad0s1a The .snap directory does exist and it is: drwxrwx--- 2 root operator 512 Dec 6 07:52 .snap ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 16:04:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 57D3116A4CE; Mon, 6 Dec 2004 16:04:23 +0000 (GMT) Received: from smtp.cegetel.net (mf01.sitadelle.com [212.94.174.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5F8F43D41; Mon, 6 Dec 2004 16:04:22 +0000 (GMT) (envelope-from jspedron@club-internet.fr) Received: from [172.16.142.1] (213-223-184-193.dti.cegetel.net [213.223.184.193]) by smtp.cegetel.net (Postfix) with ESMTP id C8FFA37B6B; Mon, 6 Dec 2004 17:04:21 +0100 (CET) Message-ID: <41B48316.90004@club-internet.fr> Date: Mon, 06 Dec 2004 17:04:38 +0100 From: =?ISO-8859-1?Q?Jean-S=E9bastien_P=E9dron?= User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20041006 X-Accept-Language: fr, en-us, en MIME-Version: 1.0 To: Doug Barton References: <20041204163103.M787@cp254-91.vpnaapncrgbja.pb.mn> In-Reply-To: <20041204163103.M787@cp254-91.vpnaapncrgbja.pb.mn> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig3A01D74E1A78B7D4415D521F" cc: Poul-Henning Kamp cc: freebsd-current@freebsd.org Subject: Re: panic: Inconsistent vnode bufstrategy X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 16:04:23 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig3A01D74E1A78B7D4415D521F Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Doug Barton wrote: > I'm using mount_ntfs to read data off my winxp partition on a dual boot > system. For a week or so I've been getting a panic, which I've finally > been able to get a dump for: > > [stack trace] I get exactly the same panic() with NTFS and ReiserFS. I think it's related with phk's commit about: "Make VOP_BMAP return a struct bufobj for the underlying storage device instead of a vnode for it." (dated Mon Nov 15 09:18:26 2004 UTC) The panic() occurs with mmap(2), for example while cp(1)'ing files smaller than 8 MB. In file systems like ufs, msdosfs or ext2fs, VOP_BMAP will do: *ap->a_bop = &VTOI(ap->a_vp)->i_devvp->v_bufobj; So the vm will call the device bo_strategy callback, and everything works. In NTFS, VOP_BMAP is different: *ap->a_bop = &ap->a_vp->v_bufobj; The goal is that the vm should call the file system's VOP_STRATEGY, not the device directly (that's what I guess, I'm not familiar with this fs :-). Here is what I understand in the code, when the vm read a page: 1) vnode_pager_generic_getpages prepare a new struct buf *bp (sys/vm/vnode_pager.c:817) and, twice, will KASSERT() that bp->b_vp is NULL (in initpbuf, called by getpbuf, and in pbgetbo). 2) in pbgetbo, bp->b_bufobj = bo (bo is "returned" by file system's VOP_BMAP; see the "*ap->a_bop = ..." lines above) 2) vnode_pager_generic_getpages call bstrategy, which in turn call bp->b_bufobj->bo_ops->bop_strategy(). For NTFS, the callback is bufstrategy (sys/kern/vfs_bio.c:3826) 3) in bufstrategy, KASSERT(bp->b_vp == bo->bo_private, ("Inconsistent vnode bufstrategy")); but bp->b_vp is NULL. In ReiserFS, because small files are not 512b-aligned on the device and the vm must call the fs' VOP_STRATEGY, I did the same thing in VOP_BMAP, which triggered this panic(). Cc'd to phk, he surely know the internals better than me :-) Jean-Seb --------------enig3A01D74E1A78B7D4415D521F Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBtIMea+xGJsFYOlMRAmPkAJ9pTEslqM83G0D/W0avM8OzfKlAawCfelA2 jHLFfpaiW5h2CfadoYhuG1g= =h6t5 -----END PGP SIGNATURE----- --------------enig3A01D74E1A78B7D4415D521F-- From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 17:17:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 342A916A4CE for ; Mon, 6 Dec 2004 17:17:06 +0000 (GMT) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9CC043D45 for ; Mon, 6 Dec 2004 17:17:05 +0000 (GMT) (envelope-from kirk@strauser.com) Received: from localhost (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id 773F921D667 for ; Mon, 6 Dec 2004 11:17:05 -0600 (CST) Received: from kanga.honeypot.net ([127.0.0.1]) by localhost (kanga.honeypot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 99340-10 for ; Mon, 6 Dec 2004 11:17:04 -0600 (CST) Received: from janus.daycos.com (janus.daycos.com [204.26.70.77]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTP id B0BFE21D3B1 for ; Mon, 6 Dec 2004 11:17:04 -0600 (CST) From: Kirk Strauser To: freebsd-current@freebsd.org User-Agent: KMail/1.7.1 References: <20041206153223.GD4427@pleiades.aeternal.net> In-Reply-To: <20041206153223.GD4427@pleiades.aeternal.net> MIME-Version: 1.0 X-UID: 22 X-Length: 2632 Date: Mon, 6 Dec 2004 11:17:03 -0600 Content-Type: multipart/signed; boundary="nextPart1878733.tYijkakFvV"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412061117.03901.kirk@strauser.com> X-Virus-Scanned: by amavisd-new at honeypot.net Subject: Fixed my WRITE_DMA problems by removing vinum X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 17:17:06 -0000 --nextPart1878733.tYijkakFvV Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I recently became one of the growing number of users seeing WRITE_DMA-related panics on a regular basis any time I loaded down my system. I'd tried the workaround of running my main 120GB drive in PIO4 mode, but it was unbearably slow and the system crawled during large transfers. I'd been installing FreeBSD on vinum concat volumes for several years for the flexibility in allocating storage (want to grow /usr? Just tack another plex to the end and growfs it). However, I'd noticed that my storage requirements had pretty well stabilized over the last couple of years, and I decided to remove my vinum setup in favor of traditional partitions. When I did that, my WRITE_DMA problems disappeared completely under all circumstances that I've been able to test. I have been totally unable to panic my system (or get any kind of DMA warnings) since the migration. I'm not ready to completely blame vinum for destabilizing my ATA system - I wouldn't testify in court that I didn't inadvertently change any seemingly minor but actually important setting - but the circumstantial evidence seems pretty strong for me. =2D-=20 Kirk Strauser --nextPart1878733.tYijkakFvV Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iD8DBQBBtJQP5sRg+Y0CpvERAg9XAJ0Q6I24YVPWzKXFasjD9VNDwQhBYwCffx5q TCSU+pXo28jYyDXihtIPBVg= =ETY2 -----END PGP SIGNATURE----- --nextPart1878733.tYijkakFvV-- From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 17:17:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D424316A4CE for ; Mon, 6 Dec 2004 17:17:49 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40DE043D5C for ; Mon, 6 Dec 2004 17:17:49 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iB6HHmR0032983; Mon, 6 Dec 2004 09:17:48 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iB6HHmN4032982; Mon, 6 Dec 2004 09:17:48 -0800 (PST) (envelope-from obrien) Date: Mon, 6 Dec 2004 09:17:48 -0800 From: "David O'Brien" To: Manfred Antar Message-ID: <20041206171748.GB32801@dragon.nuxi.com> References: <6.2.0.14.2.20041206075313.03e74db8@pozo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.2.0.14.2.20041206075313.03e74db8@pozo.com> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-current@freebsd.org Subject: Re: dump broken with new kernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 17:17:49 -0000 On Mon, Dec 06, 2004 at 08:01:01AM -0800, Manfred Antar wrote: > When I try to do a dump of the root filesystem I get : > > mksnap_ffs: Cannot create //.snap/dump_snapshot: Invalid argument > dump: Cannot create //.snap/dump_snapshot: No such file or directory > > A kernel from a week ago works fine. > The command I'm using is: > dump 0Lfua /dev/nsa0 /dev/ad0s1a > > The .snap directory does exist and it is: > drwxrwx--- 2 root operator 512 Dec 6 07:52 .snap I got this over the week end as I was trying to move some file systems to a new disk. By chance can you use a binary search and track it down to a particular day or maybe even the exact commit? -- -- David (obrien@FreeBSD.org) From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 17:23:42 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1783116A4CE for ; Mon, 6 Dec 2004 17:23:42 +0000 (GMT) Received: from pozo.com (pozo.com [216.101.162.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id D08E743D67 for ; Mon, 6 Dec 2004 17:23:41 +0000 (GMT) (envelope-from null@pozo.com) Received: from sunpci.pozo.com (sunpci.pozo.com [192.168.0.29]) (authenticated bits=0) by pozo.com (8.13.1/8.13.1) with ESMTP id iB6HNewV001721 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 6 Dec 2004 09:23:40 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <6.2.0.14.2.20041206092120.084fd908@pozo.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Mon, 06 Dec 2004 09:23:41 -0800 To: freebsd-current@freebsd.org From: Manfred Antar Cc: freebsd-current@freebsd.org In-Reply-To: <20041206171748.GB32801@dragon.nuxi.com> References: <6.2.0.14.2.20041206075313.03e74db8@pozo.com> <20041206171748.GB32801@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: Re: dump broken with new kernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 17:23:42 -0000 At 09:17 AM 12/6/2004, David O'Brien wrote: >On Mon, Dec 06, 2004 at 08:01:01AM -0800, Manfred Antar wrote: >> When I try to do a dump of the root filesystem I get : >> >> mksnap_ffs: Cannot create //.snap/dump_snapshot: Invalid argument >> dump: Cannot create //.snap/dump_snapshot: No such file or directory >> >> A kernel from a week ago works fine. >> The command I'm using is: >> dump 0Lfua /dev/nsa0 /dev/ad0s1a >> >> The .snap directory does exist and it is: >> drwxrwx--- 2 root operator 512 Dec 6 07:52 .snap > >I got this over the week end as I was trying to move some file systems to >a new disk. By chance can you use a binary search and track it down to a >particular day or maybe even the exact commit? > >-- >-- David (obrien@FreeBSD.org) The kernel that works for me is : 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Fri Nov 26 13:32:50 PST 2004 I don't have any in between. I could check out from cvs from then till now and try narrow it down a bit. I'll let you know. ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 17:42:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2CAF16A4CE for ; Mon, 6 Dec 2004 17:42:07 +0000 (GMT) Received: from portpc-design.spb.ru (ns2.portpc-design.spb.ru [195.161.118.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DC7243D5F for ; Mon, 6 Dec 2004 17:42:06 +0000 (GMT) (envelope-from mcsi@mcsi.pp.ru) Received: from [83.237.208.244] (ppp83-237-208-244.pppoe.mtu-net.ru [83.237.208.244]) (authenticated bits=0) by portpc-design.spb.ru (8.13.1/8.13.1) with ESMTP id iB6Hg3CN002487 for ; Mon, 6 Dec 2004 20:42:04 +0300 (MSK) (envelope-from mcsi@mcsi.pp.ru) Message-ID: <41B499E6.5020309@mcsi.pp.ru> Date: Mon, 06 Dec 2004 20:41:58 +0300 From: Maxim Maximov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041112 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: two kernel warnings X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 17:42:07 -0000 Hello. With today's current I've got two kernel warnings: Starting ppp as "root" WARNING: attempt to net_add_domain(netgraph) after domainfinalize() Additional routing options:. Starting devd. Starting ums0 moused: mousechar_start. hw.acpi.cpu.cx_lowest: C1 -> C1 hw.acpi.cpu.throttle_state: 8 -> 8 Starting ums0 moused:moused: unable to open /dev/ums0: Device busy mousechar_start. Mounting NFS file systems:. ndis0: link up Starting syslogd. witness_get: witness exhausted I'm running pppoe:ndis0. Everything works ok. Is this normal, should I just ignore it? -- Maxim Maximov From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 18:24:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81A4116A4CE; Mon, 6 Dec 2004 18:24:24 +0000 (GMT) Received: from CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com (CPE000103d44c07-CM000f9f7ae88c.cpe.net.cable.rogers.com [69.193.222.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EE0643D46; Mon, 6 Dec 2004 18:24:24 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from cpe000103d44c07-cm000f9f7ae88c.cpe.net.cable.rogers.com (localhost [127.0.0.1])with ESMTP id C64E0295437; Mon, 6 Dec 2004 13:24:16 -0500 (EST) Received: from 207.219.213.163 (proxying for unknown) (SquirrelMail authenticated user mikej); by cpe000103d44c07-cm000f9f7ae88c.cpe.net.cable.rogers.com with HTTP; Mon, 6 Dec 2004 13:24:16 -0500 (EST) Message-ID: <65174.207.219.213.163.1102357456.squirrel@207.219.213.163> In-Reply-To: <41B40C97.7000102@yahoo.com> References: <41B40C97.7000102@yahoo.com> Date: Mon, 6 Dec 2004 13:24:16 -0500 (EST) From: "Mike Jakubik" To: "Rob" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-wettoast-MailScanner-Information: Please contact the ISP for more information X-wettoast-MailScanner: Found to be clean X-MailScanner-From: mikej@rogers.com cc: freebsd-current cc: freebsd-stable@freebsd.org Subject: Re: names of supfiles in /usr/share/examples/cvsup X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 18:24:24 -0000 Rob said: > > Hi, > > For 5.3 in /usr/share/examples/cvsup, there's: > > stable-supfile : for FreeBSD-stable > standard-supfile : for FreeBSD-current > > I find this naming rather confusing. Why "stable" refers to STABLE, but > "standard" refers to CURRENT ? > > This causes unnecessary confusion. Why not the following name convention: > > release-supfile : for FreeBSD-RELEASE > stable-supfile : for FreeBSD-STABLE > current-supfile : for FreeBSD-CURRENT > > as default supplied files in /usr/share/examples/cvsup ? I agree with you. It has been weird like this ever since 5.x. In the 4.x days they were named with some common sense. From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 18:33:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10B0C16A4CE for ; Mon, 6 Dec 2004 18:33:49 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id E195343D39 for ; Mon, 6 Dec 2004 18:33:48 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id BAE7C72DD4; Mon, 6 Dec 2004 10:33:48 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id B5E1072DCB; Mon, 6 Dec 2004 10:33:48 -0800 (PST) Date: Mon, 6 Dec 2004 10:33:48 -0800 (PST) From: Doug White To: Hogan Whittall In-Reply-To: <20041205104323.GA21375@ninthgate.net> Message-ID: <20041206102915.U19661@carver.gumbysoft.com> References: <20041123182254.GB10721@ninthgate.net> <20041124231627.I2006@carver.gumbysoft.com> <20041205104323.GA21375@ninthgate.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: Random panics with 5.3-REL, SMP X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 18:33:49 -0000 On Sun, 5 Dec 2004, Hogan Whittall wrote: > Here's the output of the panic. It hung again while dumping core... > > Fatal trap 12: page fault while in kernel mode > > cpuid = 3; apic id = 02 > fault virtual address = 0xa748d260 Hm, that is sure out in space. Its certainly a bit-flip away from legitimate regions, so I think the bad RAM theory is the more likely one at this point. The 6450 should be using ECC memory though so you might make sure its enabled and figure out a way of interrogating the ESM bits for any messages (It'll log ECC correction events). Could also be a bad processor. > fault code = supervisor write, page not present > instruction pointer = 0x8:0xc060b611 > stack pointer = 0x10:0xe971bc20 > frame pointer = 0x10:0xe971bc20 > 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 = 52 (swi6: task queue) > trap number = 12 > panic: page fault > cpuid = 3 > boot() called on cpu#3 > Uptime: 5d6h6m34s > Dumping 3967 MB > 16 32 48 64 80 96 112 128 144 160 > > Whenever it panics it will hang at a random point during the dump, this > last time was the farthest it got... > > Someone seems to suspect bad ram as the culprit. I can always swap > it out and see what happens. > > -Hogan > > On Wed, Nov 24, 2004 at 11:24:43PM -0800, Doug White wrote: > > On Tue, 23 Nov 2004, Hogan Whittall wrote: > > > > > Dell PE6450 server, 4xP3-700 Xeon, 4gb ram, system disks reside on > > > a 2 disk RAID1 attached to a MegaRAID controller. Wireless is a > > > D-Link DWL-G520-B, also has Intel Pro/100 ethernet. > > > > For the record, I have a PE6300 (4x500MHz) I'm testing a fix for panics of > > the form > > > > panic: Previous IPI is stuck > > > > if thats one of the "random panics" you're seeing. The thread "number of > > CPUs and IPI panic" in -current has details, and a temporary patch is > > available from > > > > http://people.freebsd.org/~ups/ipi4_patch > > > > I believe this patch will apply to both RELENG_5 and -CURRENT, for now. > > > > I was having a problem with random resets (no panic, just reset) and > > traced it to a broken cpu0. Replacing it made the resets go away. > > > > If you have room you may want to install RedHat or Windows on another > > partition, load up the OpenManage tools, and inspect the system event log > > for anything peculiar. If you've never run this before then you may need > > to clear the event log for it to log any new events. If you have a DRAC > > card in the machine you can use that too. > > > > -- > > Doug White | FreeBSD: The Power to Serve > > dwhite@gumbysoft.com | www.FreeBSD.org > -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 18:36:34 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 568BA16A4CE; Mon, 6 Dec 2004 18:36:34 +0000 (GMT) Received: from smtp2.jazztel.es (smtp2.jazztel.es [62.14.3.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 761B943D4C; Mon, 6 Dec 2004 18:36:33 +0000 (GMT) (envelope-from josemi@freebsd.jazztel.es) Received: from antivirus by smtp2.jazztel.es with antivirus id 1CbNio-0007oY-00 Mon, 06 Dec 2004 19:36:30 +0100 Received: from [212.106.236.196] (helo=rguez.homeunix.net) by smtp2.jazztel.es with esmtp id 1CbNio-0007oL-00 Mon, 06 Dec 2004 19:36:30 +0100 Received: from redesjm.local (orion.redesjm.local [192.168.254.16]) by rguez.homeunix.net (8.13.1/8.13.1) with ESMTP id iB6IaUkf002520; Mon, 6 Dec 2004 19:36:30 +0100 (CET) (envelope-from freebsd@redesjm.local) Received: by redesjm.local (8.13.1/8.13.1/Submit) id iB6IabV4001471; Mon, 6 Dec 2004 19:36:37 +0100 (CET) (envelope-from freebsd@redesjm.local) From: Jose M Rodriguez To: freebsd-stable@freebsd.org Date: Mon, 6 Dec 2004 19:36:34 +0100 User-Agent: KMail/1.7.1 References: <41B40C97.7000102@yahoo.com> In-Reply-To: <41B40C97.7000102@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200412061936.35851.freebsd@redesjm.local> X-AntiVirus: checked by AntiVir Milter (version: 1.1; AVE: 6.28.0.19; VDF: 6.28.0.106; host: antares.redesjm.local) X-Virus-Scanned: by antivirus cc: Rob cc: freebsd-current Subject: Re: names of supfiles in /usr/share/examples/cvsup X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 18:36:34 -0000 El Lunes, 6 de Diciembre de 2004 08:39, Rob escribi=F3: > Hi, > > For 5.3 in /usr/share/examples/cvsup, there's: > > stable-supfile : for FreeBSD-stable > standard-supfile : for FreeBSD-current > > I find this naming rather confusing. Why "stable" refers to STABLE, > but "standard" refers to CURRENT ? > > This causes unnecessary confusion. Why not the following name > convention: > > release-supfile : for FreeBSD-RELEASE Better security-supfile. There is just one release, things like=20 RELENG_5_3 are security branchs, not release branchs. > stable-supfile : for FreeBSD-STABLE > current-supfile : for FreeBSD-CURRENT > =2D- josemi From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 18:56:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3843016A4CE for ; Mon, 6 Dec 2004 18:56:35 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED59D43D6B for ; Mon, 6 Dec 2004 18:56:34 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id D89E772DD4; Mon, 6 Dec 2004 10:56:34 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id D6E2F72DCB; Mon, 6 Dec 2004 10:56:34 -0800 (PST) Date: Mon, 6 Dec 2004 10:56:34 -0800 (PST) From: Doug White To: Henry Whincup In-Reply-To: <006501c4da28$5692e130$0a64a8c0@techiebod.com> Message-ID: <20041206105139.E19661@carver.gumbysoft.com> References: <006501c4da28$5692e130$0a64a8c0@techiebod.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: ffs_clusteralloc: allocated out of group on 5TB fs (5.3-Stable) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 18:56:35 -0000 On Sat, 4 Dec 2004, Henry Whincup wrote: > On a machine with a 5TB array I created a single partition via gpt and a > filesystem using the defaults from newfs. > > All seemed well until I tried to fill the partition with data. With "only" > 870GB or so used utilities started reporting the disk as full. Shortly (a > few hours) after the machine panic'd. Ooh, fun. I wish I had a 5TB array to play with :) > During this time I had been trying to copy file via nfs and rsync onto the > array. After several crashes I tried a simple "dd if=/dev/zero of=./file" > and after writing ~33GB the machine rebooted (the panic details below are > from this reboot) > > Details follow: [..] > Backtrace: > #0 0xc060ce82 in doadump () > #1 0xc060d47b in boot () > #2 0xc060d7a1 in panic () > #3 0xc073445e in ffs_clusteralloc () > #4 0xc0733680 in ffs_hashalloc () > #5 0xc07329ea in ffs_reallocblks_ufs2 () > #6 0xc073205a in ffs_reallocblks () > #7 0xc0657e7c in cluster_write () > #8 0xc074c350 in ffs_write () > #9 0xc066bf10 in vn_write () > #10 0xc062d624 in dofilewrite () > #11 0xc062d4d1 in write () > #12 0xc07bb07f in syscall () > #13 0xc07a8a0f in Xint0x80_syscall () > > Kernel is the default SMP kernel and sources are from 28th Nov 2004. > > I assume a proper debug kernel with symbols would be more helpful, but I > just wanted to know if this was a known bug - or something I have done > wrong, first. > Other than that is there anything else I can provide to help find this bug? Very large FFS filesystems have not been extensively tested. Maybe you can help :) You should be able to compile GENERIC with makeoptions "DEBUG=-g" in the config file and that will leave a kernel.debug in the compile directory that you can use. Once you get that loaded up the output of 'bt full' would be nice to have. I suspect an integer overflow in dtog(), which is a macro. 1545 if (dtog(fs, bno) != cg) 1546 panic("ffs_clusteralloc: allocated out of group"); -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 18:59:59 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D46616A4CF for ; Mon, 6 Dec 2004 18:59:59 +0000 (GMT) Received: from smtp001.bizmail.yahoo.com (smtp001.bizmail.yahoo.com [216.136.172.125]) by mx1.FreeBSD.org (Postfix) with SMTP id 9D31E43D53 for ; Mon, 6 Dec 2004 18:59:58 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: from unknown (HELO optimator.noacks.org) (noackjr@supercrime.org@70.240.198.174 with login) by smtp001.bizmail.yahoo.com with SMTP; 6 Dec 2004 18:59:57 -0000 Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 0D6CC614D; Mon, 6 Dec 2004 12:59:56 -0600 (CST) Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 69136-11; Mon, 6 Dec 2004 12:59:44 -0600 (CST) Received: from www.noacks.org (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 9FA1560F0; Mon, 6 Dec 2004 12:59:44 -0600 (CST) Received: from 69.53.57.66 (SquirrelMail authenticated user noackjr); by www.noacks.org with HTTP; Mon, 6 Dec 2004 12:59:44 -0600 (CST) Message-ID: <8783.69.53.57.66.1102359584.squirrel@69.53.57.66> In-Reply-To: <41B40C97.7000102@yahoo.com> References: <41B40C97.7000102@yahoo.com> Date: Mon, 6 Dec 2004 12:59:44 -0600 (CST) From: "Jon Noack" To: "Rob" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: amavisd-new at noacks.org cc: freebsd-current cc: freebsd-stable@freebsd.org Subject: Re: names of supfiles in /usr/share/examples/cvsup X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 18:59:59 -0000 Rob wrote: > For 5.3 in /usr/share/examples/cvsup, there's: > > stable-supfile : for FreeBSD-stable > standard-supfile : for FreeBSD-current > > I find this naming rather confusing. Why "stable" refers to STABLE, but > "standard" refers to CURRENT ? Actually, this is not correct. For 5.3-RELEASE and RELENG_5_3, standard-supfile points to RELENG_5_3. For RELENG_5, standard-supfile points to RELENG_5 (despite the incorrect comment at the top saying it gets you -CURRENT -- look at the actual CVS tag used). For -CURRENT, standard-supfile points to "." (HEAD). Thus, standard-supfile keeps you on the branch you are using. I like that the "standard" is to keep you on the branch you are using. This makes sense to me. I think adding a current-supfile would reduce confusion (seems like it's the time of year to discuss this: http://lists.freebsd.org/pipermail/freebsd-current/2003-December/016071.html). However, the biggest problem is definitely the incorrect comment in standard-supfile... Jon From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 19:44:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D73616A4CE for ; Mon, 6 Dec 2004 19:44:45 +0000 (GMT) Received: from pozo.com (pozo.com [216.101.162.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1A0F43D55 for ; Mon, 6 Dec 2004 19:44:44 +0000 (GMT) (envelope-from null@pozo.com) Received: from sunpci.pozo.com (sunpci.pozo.com [192.168.0.29]) (authenticated bits=0) by pozo.com (8.13.1/8.13.1) with ESMTP id iB6Jii88000667 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 6 Dec 2004 11:44:44 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <6.2.0.14.2.20041206114020.08851e60@pozo.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Mon, 06 Dec 2004 11:44:44 -0800 To: freebsd-current@freebsd.org From: Manfred Antar In-Reply-To: <20041206171748.GB32801@dragon.nuxi.com> References: <6.2.0.14.2.20041206075313.03e74db8@pozo.com> <20041206171748.GB32801@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: Re: dump broken with new kernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 19:44:45 -0000 At 09:17 AM 12/6/2004, you wrote: >On Mon, Dec 06, 2004 at 08:01:01AM -0800, Manfred Antar wrote: >> When I try to do a dump of the root filesystem I get : >> >> mksnap_ffs: Cannot create //.snap/dump_snapshot: Invalid argument >> dump: Cannot create //.snap/dump_snapshot: No such file or directory >> >> A kernel from a week ago works fine. >> The command I'm using is: >> dump 0Lfua /dev/nsa0 /dev/ad0s1a >> >> The .snap directory does exist and it is: >> drwxrwx--- 2 root operator 512 Dec 6 07:52 .snap > >I got this over the week end as I was trying to move some file systems to >a new disk. By chance can you use a binary search and track it down to a >particular day or maybe even the exact commit? > >-- >-- David (obrien@FreeBSD.org) It happened sometime between the 3rd and 4th. cvs co -D3-dec sys Works cvs co -D4-dec sys Is broken I'm also seeing alot of : Dec 6 10:06:53 pozo kernel: Accounting resumed Dec 6 10:07:23 pozo kernel: Accounting suspended Dec 6 10:07:38 pozo kernel: Accounting resumed Dec 6 10:12:23 pozo kernel: Accounting suspended Dec 6 10:12:38 pozo kernel: Accounting resumed Dec 6 10:12:53 pozo kernel: Accounting suspended This is with a new kernel and I don't think it is same as the dump problem as the kernel from the 4th doesn't do that. I'll try and narrow down the time a bit closer ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 21:10:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAD8F16A4E5; Mon, 6 Dec 2004 21:10:16 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4152243D68; Mon, 6 Dec 2004 21:10:15 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB6LAD48090141; Mon, 6 Dec 2004 22:10:14 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: arch@freebsd.org, current@freebsd.org From: Poul-Henning Kamp Date: Mon, 06 Dec 2004 22:10:13 +0100 Message-ID: <90140.1102367413@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Subject: NMOUNT/OMOUNT midway status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 21:10:17 -0000 I have now converted all of the filesystems which are not rootfs candidates under the old world order[1] (nfs, cd9660 and ufs). There shouldn't be any visible effects of this work seen from userland: the old mount_*(8) binaries and mount(2) system calls should all just work like they used to. If they don't, try to take a peek yourself, it's pretty simple after all. If you can't spot the mistake I've made, send me email. The next step involved converting the three 'big' filesystems and the root filesystem mount code, and I have not quite found out how to partition that into a sequence of sensible commits. If you want to help me test I keep a patch relative to -current up to date: http://phk.freebsd.dk/patch/nmount.patch Poul-Henning [1] In the new worldorder all filesystems which understand a "from" argument is a root filesystem candidate, that means that msdosfs, ntfs, hpfs and ext2fs with no or only minor tweaking can be used for root filesystem. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 21:53:59 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECC2016A4CE for ; Mon, 6 Dec 2004 21:53:59 +0000 (GMT) Received: from pozo.com (pozo.com [216.101.162.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6423F43D4C for ; Mon, 6 Dec 2004 21:53:59 +0000 (GMT) (envelope-from null@pozo.com) Received: from sunpci.pozo.com (sunpci.pozo.com [192.168.0.29]) (authenticated bits=0) by pozo.com (8.13.1/8.13.1) with ESMTP id iB6LrsDm000702 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 6 Dec 2004 13:53:56 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <6.2.0.14.2.20041206134829.08ad2d00@pozo.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Mon, 06 Dec 2004 13:53:39 -0800 To: freebsd-current@freebsd.org From: Manfred Antar Cc: freebsd-current@freebsd.org In-Reply-To: <20041206171748.GB32801@dragon.nuxi.com> References: <6.2.0.14.2.20041206075313.03e74db8@pozo.com> <20041206171748.GB32801@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: Re: dump broken with new kernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 21:54:00 -0000 At 09:17 AM 12/6/2004, David O'Brien wrote: >On Mon, Dec 06, 2004 at 08:01:01AM -0800, Manfred Antar wrote: >> When I try to do a dump of the root filesystem I get : >> >> mksnap_ffs: Cannot create //.snap/dump_snapshot: Invalid argument >> dump: Cannot create //.snap/dump_snapshot: No such file or directory >> >> A kernel from a week ago works fine. >> The command I'm using is: >> dump 0Lfua /dev/nsa0 /dev/ad0s1a >> >> The .snap directory does exist and it is: >> drwxrwx--- 2 root operator 512 Dec 6 07:52 .snap > >I got this over the week end as I was trying to move some file systems to >a new disk. By chance can you use a binary search and track it down to a >particular day or maybe even the exact commit? > >-- >-- David (obrien@FreeBSD.org) This seems to be when the change was made: cvs co -D"December 3, 2004 20:00 UTC" sys -- dump broken cvs co -D"December 3, 2004 18:00 UTC" sys -- dump works The suspect files seem to be: sys/kern/vfs_mount.c $FreeBSD: src/sys/kern/vfs_mount.c,v 1.156 2004/12/03 19:25:44 phk Exp sys/sys/mount.h $FreeBSD: src/sys/sys/mount.h,v 1.180 2004/12/03 19:33:19 phk Exp $ I know phk has been working on the mount stuff. ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 22:23:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F88716A4CE for ; Mon, 6 Dec 2004 22:23:57 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id B36EF43D1F for ; Mon, 6 Dec 2004 22:23:56 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB6MNstt091248; Mon, 6 Dec 2004 23:23:54 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Manfred Antar From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 06 Dec 2004 13:53:39 PST." <6.2.0.14.2.20041206134829.08ad2d00@pozo.com> Date: Mon, 06 Dec 2004 23:23:54 +0100 Message-ID: <91247.1102371834@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-current@freebsd.org Subject: Re: dump broken with new kernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 22:23:57 -0000 In message <6.2.0.14.2.20041206134829.08ad2d00@pozo.com>, Manfred Antar writes: >This seems to be when the change was made: >cvs co -D"December 3, 2004 20:00 UTC" sys -- dump broken > >cvs co -D"December 3, 2004 18:00 UTC" sys -- dump works > >The suspect files seem to be: >sys/kern/vfs_mount.c >$FreeBSD: src/sys/kern/vfs_mount.c,v 1.156 2004/12/03 19:25:44 phk Exp > >sys/sys/mount.h >$FreeBSD: src/sys/sys/mount.h,v 1.180 2004/12/03 19:33:19 phk Exp $ > >I know phk has been working on the mount stuff. It seems I've broken snapshots and I think I've found out how/why. sbin/mount_ufs.c mounts using the filesystem "ufs". mksnap_ffs uses filesystem name "ffs". I think the problem is that previously a MNT_UPDATE would not actually check the filesystem name provided once it got hold of the mountpoint[1] and I start out looking for the filesystem type first. The problem is compounded by the fact that "ufs" is the wrong name, the correct name is "ffs"[2]. I tried to make the name "ffs" and make "ufs" an alias for it, but it blows up all over the place. So against my better judgement I have just committed code to the kernel to accept "ffs" as an alias for "ufs" when it comes to filesystems. I'm far from sure that is all there is to it, but it seems to let dumps work for me again. Poul-Henning [1] If anybody have a kernel a couple of weeks old, try this: mount -o ro /dev/mumble /mnt # mount ufs/ffs filesytem mount_msdos -u -o rw /mnt # upgrade it... and lets us know if it works. There may be other checks which stop it from working. [2] "ufs" is a more or less generic layer which could be used by another storage manager. It does the search directory and name management. "ffs" is the storage management which cares about putting files on disk. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 22:49:34 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B86BF16A4CF for ; Mon, 6 Dec 2004 22:49:34 +0000 (GMT) Received: from smtp2.arin.net (smtp2.arin.net [192.149.252.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CD1F43D5F for ; Mon, 6 Dec 2004 22:49:34 +0000 (GMT) (envelope-from matt@arin.net) Received: by smtp2.arin.net (Postfix, from userid 5003) id 70241144AB2; Mon, 6 Dec 2004 17:49:33 -0500 (EST) Received: from mercury.arin.net (mercury.arin.net [192.149.252.131]) by smtp2.arin.net (Postfix) with ESMTP id E574A144A86 for ; Mon, 6 Dec 2004 17:49:31 -0500 (EST) Received: from elric.arin.net (elric.arin.net [192.136.136.23]) by mercury.arin.net (Postfix) with ESMTP id 7465A1FE89 for ; Mon, 6 Dec 2004 17:45:53 -0500 (EST) Date: Mon, 06 Dec 2004 17:49:19 -0500 From: Matt Rowley To: freebsd-current@freebsd.org Message-ID: X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Checker-Version: SpamAssassin 2.63-arin1 (2004-01-11) on smtp2.arin.net X-Spam-Level: X-Spam-Status: No, hits=-5.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=2.63-arin1 Subject: FreeBSD 5.3 and Adaptec raidutils (again) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 22:49:34 -0000 Sorry, I don't have a copy of the original message that went to current@... On 11/04/04, Scott Long wrote: > Ah, it is a BSD-style license. However, someone will have to take a > careful look through each file to check for consistency here. Any > volunteers? I pulled down I20-on-linux's raidutils tarball and went through their license headers. Just about all of the files begin with Adaptec's BSD-ish license: 1) Source distributions must retain copyright notice and disclaimer, 2) Binary distributions must reproduce the notice and disclaimer, 3) Neither the name of the Adaptec Corporation nor the names of its contributors may be used to endorse or promote products derived from this software A few other files have different license headers, copyrighted by Adaptec, Distributed Processing Technology Corporation, and I2O Special Interest Group. The files are: raidutils-0.0.4/raideng/i2oadptr.h ...i2obscsi.h ...i2odpt.h ...i2oexec.h ...i2omsg.h ...i2omstor.h ...i2otypes.h ...i2outil.h But these licenses look identical to those in /usr/src/sys/dev/asr/i2o* in FreeBSD's tree. These two files: i2omodul.h i2odep.h, in raidutils-0.0.4/raideng/ have a different I20 license that says "These header files are provided, pursuant to your I2O SIG membership agreement"... it basically sounds like a no-warranty disclaimer, but I don't know what the I20 SIG agreement is to which they referring. Hopefully this helps in determining whether this code is useful. I'd love to see the asr_utils working in FreeBSD5. But I also really appreciate the large amounts of fixing-up that's gone into the asr driver over the past few years. many thanks, Matt From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 22:54:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4F3C16A4CE for ; Mon, 6 Dec 2004 22:54:36 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDA8C43D58 for ; Mon, 6 Dec 2004 22:54:35 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB6MsY9N028516; Tue, 7 Dec 2004 00:54:34 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 25856-13; Tue, 7 Dec 2004 00:54:33 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB6MsXXd028513 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Dec 2004 00:54:33 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iB6MsXui091219; Tue, 7 Dec 2004 00:54:33 +0200 (EET) (envelope-from ru) Date: Tue, 7 Dec 2004 00:54:33 +0200 From: Ruslan Ermilov To: Poul-Henning Kamp Message-ID: <20041206225432.GA87510@ip.net.ua> References: <90140.1102367413@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: <90140.1102367413@critter.freebsd.dk> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: current@freebsd.org Subject: Re: NMOUNT/OMOUNT midway status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 22:54:36 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Mon, Dec 06, 2004 at 10:10:13PM +0100, Poul-Henning Kamp wrote: >=20 > I have now converted all of the filesystems which are not rootfs > candidates under the old world order[1] (nfs, cd9660 and ufs). >=20 > There shouldn't be any visible effects of this work seen from > userland: the old mount_*(8) binaries and mount(2) system calls > should all just work like they used to. >=20 > If they don't, try to take a peek yourself, it's pretty simple > after all. If you can't spot the mistake I've made, send me > email. >=20 > The next step involved converting the three 'big' filesystems and > the root filesystem mount code, and I have not quite found out > how to partition that into a sequence of sensible commits. >=20 > If you want to help me test I keep a patch relative to -current > up to date: >=20 > http://phk.freebsd.dk/patch/nmount.patch >=20 > Poul-Henning >=20 >=20 > [1] In the new worldorder all filesystems which understand a "from" > argument is a root filesystem candidate, that means that msdosfs, > ntfs, hpfs and ext2fs with no or only minor tweaking can be used > for root filesystem. >=20 Are you aware of the following problem? On a recent -CURRENT system, remounting / by fsck(8) is not possible: mount reload of '/' failed: Invalid argument This has been triggered by an unclean shutdown due to a panic, but can also be reproduced easily by booting or shutting down into single-user mode, having / mounted read-only, and typing "fsck /". Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --17pEHd4RhPHOinZp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBtOMoqRfpzJluFF4RAg39AJ49xTcXBRnfurwpfmqzvf1Z0p+mhgCePdJ9 hp655+nkyyLrYoq/79z6w34= =ksOp -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp-- From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 23:05:05 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C1BD16A4CE; Mon, 6 Dec 2004 23:05:05 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 14D1C43D49; Mon, 6 Dec 2004 23:05:05 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iB6N53C4011033 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 6 Dec 2004 15:05:04 -0800 Message-ID: <41B4E577.9060502@root.org> Date: Mon, 06 Dec 2004 15:04:23 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: acpi@freebsd.org Subject: suspend/resume improved? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 23:05:05 -0000 I made a commit over the weekend to -current that may fix some suspend/resume driver issues for people. Please test and let me know if it helps. -- Nate From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 23:15:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 337E016A4CE for ; Mon, 6 Dec 2004 23:15:28 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 301A443D5D for ; Mon, 6 Dec 2004 23:15:18 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44])iB6NEj53017943 for ; Mon, 6 Dec 2004 17:14:45 -0600 Received: from s228130hz1ew17.apptix-01.savvis.net ([10.146.4.29]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 6 Dec 2004 17:14:41 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew17.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 6 Dec 2004 17:14:33 -0600 Message-ID: <41B4E7D3.5040108@savvis.net> Date: Mon, 06 Dec 2004 15:14:27 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: multipart/mixed; boundary="------------020106050205040500050409" X-OriginalArrivalTime: 06 Dec 2004 23:14:33.0168 (UTC) FILETIME=[587D3500:01C4DBE9] X-ECS-MailScanner: No virus is found X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: help! acpi kills my laptop X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 23:15:28 -0000 This is a multi-part message in MIME format. --------------020106050205040500050409 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Dear Hackers, after recent upgrade i no longer can boot my laptop (toshiba tecra 8100) with acpi enabled. all i get is a bunch of ACPI-025: *** Error: No object was returned from [\_SB_.LNKB._STA] Node (0xc118f080), AE_NOT_EXIST and the everyting hangs. i've attached dsdt. beetle% uname -a FreeBSD beetle.digisle.com 6.0-CURRENT FreeBSD 6.0-CURRENT #1: Fri Dec 3 15:18:39 PST 2004 max@beetle.digisle.com:/usr/obj/usr/src/sys/BEETLE i386 beetle% anyone sees this? or its just me. max --------------020106050205040500050409-- From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 23:21:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0620C16A4CF for ; Mon, 6 Dec 2004 23:21:45 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id A772543D39 for ; Mon, 6 Dec 2004 23:21:44 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45])iB6NLQ53018462 for ; Mon, 6 Dec 2004 17:21:26 -0600 Received: from s228130hz1ew17.apptix-01.savvis.net ([10.146.4.29]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 6 Dec 2004 17:21:24 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew17.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 6 Dec 2004 17:21:14 -0600 Message-ID: <41B4E968.9080502@savvis.net> Date: Mon, 06 Dec 2004 15:21:12 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <41B4E7D3.5040108@savvis.net> In-Reply-To: <41B4E7D3.5040108@savvis.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 06 Dec 2004 23:21:15.0091 (UTC) FILETIME=[480DCA30:01C4DBEA] X-ECS-MailScanner: No virus is found Subject: Re: help! acpi kills my laptop X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 23:21:45 -0000 > Dear Hackers, > > after recent upgrade i no longer can boot my laptop (toshiba tecra 8100) > with acpi enabled. all i get is a bunch of > > ACPI-025: *** Error: No object was returned from [\_SB_.LNKB._STA] Node > (0xc118f080), AE_NOT_EXIST > > and the everyting hangs. i've attached dsdt. or you can download it here http://www.geocities.com/m_evmenkin/toshiba.dsdt.gz attachment did not make it to the list :( > > beetle% uname -a > FreeBSD beetle.digisle.com 6.0-CURRENT FreeBSD 6.0-CURRENT #1: Fri Dec 3 > 15:18:39 PST 2004 max@beetle.digisle.com:/usr/obj/usr/src/sys/BEETLE i386 > beetle% > > anyone sees this? or its just me. > > max > > > ------------------------------------------------------------------------ > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 23:46:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B190A16A4CE for ; Mon, 6 Dec 2004 23:46:06 +0000 (GMT) Received: from error404.nls.net (error404.nls.net [216.144.36.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C0B343D54 for ; Mon, 6 Dec 2004 23:46:06 +0000 (GMT) (envelope-from ketrien@error404.nls.net) Received: from error404.nls.net (ketrien@error404.nls.net [216.144.36.24]) by error404.nls.net (8.13.1/8.13.1) with ESMTP id iB6NkrKE070460; Mon, 6 Dec 2004 18:46:53 -0500 (EST) (envelope-from ketrien@error404.nls.net) Date: Mon, 6 Dec 2004 18:46:53 -0500 (EST) From: "Ketrien I. Saihr-Kenchedra" X-X-Sender: ketrien@bahre.achedra.org To: Matt Rowley In-Reply-To: Message-ID: <20041206183904.S88450@bahre.achedra.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: ClamAV 0.80/609/Fri Nov 26 15:20:39 2004 clamav-milter version 0.80j on bahre.achedra.org X-Virus-Status: Clean cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 5.3 and Adaptec raidutils (again) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 23:46:06 -0000 On Mon, 6 Dec 2004, Matt Rowley wrote: > Sorry, I don't have a copy of the original message that went to current@... > A few other files have different license headers, copyrighted by Adaptec, > Distributed Processing Technology Corporation, and I2O Special Interest > Group. The files are: > But these licenses look identical to those in /usr/src/sys/dev/asr/i2o* in > FreeBSD's tree. > These two files: i2omodul.h i2odep.h, in raidutils-0.0.4/raideng/ have a > different I20 license that says "These header files are provided, pursuant to > your I2O SIG membership agreement"... it basically sounds like a no-warranty > disclaimer, but I don't know what the I20 SIG agreement is to which they > referring. I have to wonder at the validity of those licenses, actually. I was looking at them with relation to some i960 work I've been doing, and try as I might, the I2O SIG seems to no longer exist in any form. I'd love to find out otherwise, if only so the license can be clarified. -Ketrien I. Saihr-Kenchedra From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 00:52:05 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D561F16A4CE for ; Tue, 7 Dec 2004 00:52:05 +0000 (GMT) Received: from smtp3.server.rpi.edu (smtp3.server.rpi.edu [128.113.2.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41CD243D5D for ; Tue, 7 Dec 2004 00:52:05 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp3.server.rpi.edu (8.13.0/8.13.0) with ESMTP id iB70pveq002532; Mon, 6 Dec 2004 19:51:57 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Mon, 6 Dec 2004 19:51:56 -0500 To: freebsd-current@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) cc: =?iso-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: Another twist on WRITE_DMA issues <- ProblemFound X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 00:52:05 -0000 At 1:28 AM -0500 12/6/04, Garance A Drosihn wrote: >At 9:31 PM -0500 12/2/04, Garance A Drosihn wrote: >> >>I have now switched from that Western Digital drive to a Seagate >>Barracuda 7200.7 120-gig (ST3120026AS). The drive seems to be >>working fairly well, but now I sometimes see some combination >>like the following three lines: >> >>Dec 2 20:29:50 kernel: Interrupt storm detected on >> "irq20: atapci0"; throttling interrupt source >>Dec 2 20:29:54 kernel: ad4: TIMEOUT - WRITE_DMA retrying >> (2 retries left) LBA=20627679 >>Dec 2 20:29:54 kernel: ad4: FAILURE - WRITE_DMA timed out [skipping] >Just before I realized that SATA controller was the problem, I had >added: > hw.ata.ata_dma=0 >to /boot/loader.conf.local, ... >I removed that setting, rebooted, and I have now done a complete >buildworld/installworld cycle without seeing a single "interrupt >storm" or a single WRITE_DMA error. While the setting was still >there, I would always see at least a few of those warning messages >(and sometimes end up with a system panic). So, my hope is that >this has finally solved the last of my problems with this machine. That isn't it either. I think the hardware is just mocking me. I had zero problems for more than 24 hours. I then copied one set of partitions to another, booted up to that second set, and immediately I was back to having the above warnings/errors, and before long I had a system panic. And when I try to 'call doadump()', that fails with an error writing to the disk, so I can't get a core dump of it either. Maybe it's an overheating issue, or maybe it's something else. But whatever it is, I am going to assume it's the fault of something in my PC. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 01:04:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C01416A4CE for ; Tue, 7 Dec 2004 01:04:37 +0000 (GMT) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 535F843D41 for ; Tue, 7 Dec 2004 01:04:37 +0000 (GMT) (envelope-from kirk@strauser.com) Received: from localhost (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id AECD121CB5F for ; Mon, 6 Dec 2004 19:04:36 -0600 (CST) Received: from kanga.honeypot.net ([127.0.0.1]) by localhost (kanga.honeypot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11567-08 for ; Mon, 6 Dec 2004 19:04:28 -0600 (CST) Received: from pooh.honeypot.net (unknown [IPv6:2001:470:1f01:224:1::2]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTP id 8704B21C99E for ; Mon, 6 Dec 2004 19:04:28 -0600 (CST) From: Kirk Strauser To: current@freebsd.org Date: Mon, 6 Dec 2004 19:04:27 -0600 User-Agent: KMail/1.7.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3310053.72AlOi05KY"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412061904.27758.kirk@strauser.com> X-Virus-Scanned: by amavisd-new at honeypot.net Subject: Re: Another twist on WRITE_DMA issues... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 01:04:37 -0000 --nextPart3310053.72AlOi05KY Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 02 December 2004 08:31 pm, Garance A Drosihn wrote: > I have now switched from that Western Digital drive to a Seagate > Barracuda 7200.7 120-gig (ST3120026AS). The drive seems to be > working fairly well, but now I sometimes see some combination > like the following three lines: Out of curiosity, are you using (g)vinum or accessing the drive directly? = I=20 migrated my partitions from the former to the latter and all of my DMA=20 problems disappeared. =2D-=20 Kirk Strauser --nextPart3310053.72AlOi05KY Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBtQGb5sRg+Y0CpvERAoRBAJ0a2cTgxp6rBlBbNcXc2y322VJ0HACfdu1e NGHQkYs496NhbnURngXym78= =/FfX -----END PGP SIGNATURE----- --nextPart3310053.72AlOi05KY-- From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 01:24:11 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1691616A4CE; Tue, 7 Dec 2004 01:24:11 +0000 (GMT) Received: from pd3mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7230D43D5D; Tue, 7 Dec 2004 01:24:10 +0000 (GMT) (envelope-from colin.percival@wadham.ox.ac.uk) Received: from pd3mr5so.prod.shaw.ca (pd3mr5so-qfe3.prod.shaw.ca [10.0.141.12])2004)) with ESMTP id <0I8B0039CVWAOP20@l-daemon>; Mon, 06 Dec 2004 18:24:10 -0700 (MST) Received: from pn2ml6so.prod.shaw.ca ([10.0.121.150]) by pd3mr5so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0I8B00GHHVW9W3A0@pd3mr5so.prod.shaw.ca>; Mon, 06 Dec 2004 18:24:10 -0700 (MST) Received: from [192.168.0.60] (S0106006067227a4a.vc.shawcable.net [24.87.233.42])2003)) with ESMTP id <0I8B00E2VVW9ZX@l-daemon>; Mon, 06 Dec 2004 18:24:09 -0700 (MST) Date: Mon, 06 Dec 2004 17:24:09 -0800 From: Colin Percival In-reply-to: <41B2E0B7.1020001@hosting50.cz> To: Tomas Randa Message-id: <41B50639.6070307@wadham.ox.ac.uk> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-2 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime References: <41B2E0B7.1020001@hosting50.cz> User-Agent: Mozilla Thunderbird 0.9 (X11/20041107) cc: freebsd-current@freebsd.org cc: mobile@freebsd.org Subject: Re: estctrl & ACPI question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 01:24:11 -0000 Tomas Randa wrote: > Hi, I have Acer TravelMate 3200 and have following problems with estctrl: > > estctrl: Error reading AC line status: No such file or directory > > It is because sysctl hw.acpi.acline not exists. > > Is anybody here with this problems? Once the latest version of estctrl has been committed (ports/74795) this should be fixed. Colin Percival From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 01:27:09 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CC1E16A4CE for ; Tue, 7 Dec 2004 01:27:09 +0000 (GMT) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1054143D55 for ; Tue, 7 Dec 2004 01:27:09 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.13.0/8.13.0) with ESMTP id iB71R7Lf010228; Mon, 6 Dec 2004 20:27:08 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: <200412061904.27758.kirk@strauser.com> References: <200412061904.27758.kirk@strauser.com> Date: Mon, 6 Dec 2004 20:27:06 -0500 To: Kirk Strauser , current@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) Subject: Re: Another twist on WRITE_DMA issues... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 01:27:09 -0000 At 7:04 PM -0600 12/6/04, Kirk Strauser wrote: >On Thursday 02 December 2004 08:31 pm, Garance A Drosihn wrote: > >> I have now switched from that Western Digital drive to a Seagate >> Barracuda 7200.7 120-gig (ST3120026AS). The drive seems to be >> working fairly well, but now I sometimes see some combination >> like the following three lines: > >Out of curiosity, are you using (g)vinum or accessing the drive >directly? I migrated my partitions from the former to the latter >and all of my DMA problems disappeared. I noticed your message go by. No, I do not use either vinum or gvinum. Just plain BSD partitions inside of DOS-style slices. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 02:42:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58A0716A4CE for ; Tue, 7 Dec 2004 02:42:58 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2471543D66 for ; Tue, 7 Dec 2004 02:42:58 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 0BEDD72DD4; Mon, 6 Dec 2004 18:42:58 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 0690D72DCB; Mon, 6 Dec 2004 18:42:58 -0800 (PST) Date: Mon, 6 Dec 2004 18:42:57 -0800 (PST) From: Doug White To: Erik Greenwald In-Reply-To: <20041206193921.GA31784@phoenix.smluc.org> Message-ID: <20041206183531.T23442@carver.gumbysoft.com> References: <006501c4da28$5692e130$0a64a8c0@techiebod.com> <20041206193921.GA31784@phoenix.smluc.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Henry Whincup cc: freebsd-current@freebsd.org cc: erikg@arl.army.mil Subject: Re: ffs_clusteralloc: allocated out of group on 5TB fs (5.3-Stable) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 02:42:58 -0000 On Mon, 6 Dec 2004, Erik Greenwald wrote: > > 1545 if (dtog(fs, bno) != cg) > > 1546 panic("ffs_clusteralloc: allocated out of group"); > > a couple weeks ago, when I found the issue, I tried dumping that line > using a printf and got > > dtog(0xc4896800, -1894026712) != 25518 > > (I think I used %x, %d, %d) Unfortunately bno is a int64_t (via ufs2_daddr_t) so that value is incorrect. > I've no idea what those #'s mean, and couldn't find any documentation on > 'dtog' (something to group?) dtog translates a filesystem block to a cylinder group: #define dtog(fs, d) ((d) / (fs)->fs_fpg) (fpg is frags per group) bno comes from: bno = cg * fs->fs_fpg + blkstofrags(fs, got - run + 1); That seems more likely to overflow or be the victim of a bad cast since everything on the rhs are ints. blkstofrags is a bit-shift. a 'bt full' would print all this, but if you have to instrument then this should be a good start. > I have a kernel with the DEBUG=-g option, (and config -g), can't get the > dang thing to dump, though It might help if you put the dump volume on something other than the gigantic array, in case stuff is getting tied up there because of the ffs problem. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 02:55:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89C1316A4CE; Tue, 7 Dec 2004 02:55:38 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5004743D58; Tue, 7 Dec 2004 02:55:38 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 4089C72DD4; Mon, 6 Dec 2004 18:55:38 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 3E0E272DCB; Mon, 6 Dec 2004 18:55:38 -0800 (PST) Date: Mon, 6 Dec 2004 18:55:38 -0800 (PST) From: Doug White To: Ruslan Ermilov In-Reply-To: <20041206225432.GA87510@ip.net.ua> Message-ID: <20041206185349.G23442@carver.gumbysoft.com> References: <90140.1102367413@critter.freebsd.dk> <20041206225432.GA87510@ip.net.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Poul-Henning Kamp cc: current@freebsd.org Subject: Re: NMOUNT/OMOUNT midway status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 02:55:38 -0000 On Tue, 7 Dec 2004, Ruslan Ermilov wrote: > Are you aware of the following problem? On a recent > -CURRENT system, remounting / by fsck(8) is not possible: > > mount reload of '/' failed: Invalid argument > > This has been triggered by an unclean shutdown due to a > panic, but can also be reproduced easily by booting or > shutting down into single-user mode, having / mounted > read-only, and typing "fsck /". I got this today on one of my machines. It would seem that whatever in the kernel checks the clean bit isn't picking it up after fsck finishes. I wonder if this may be related to the ufs/ffs aliasing problem fixed earlier. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 03:11:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52D6D16A4CE for ; Tue, 7 Dec 2004 03:11:47 +0000 (GMT) Received: from imf22aec.mail.bellsouth.net (imf22aec.mail.bellsouth.net [205.152.59.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id B28C843D75 for ; Tue, 7 Dec 2004 03:11:46 +0000 (GMT) (envelope-from chaosasj@bellsouth.net) Received: from [216.76.216.79] by imf22aec.mail.bellsouth.netESMTP <20041207031145.EARO2051.imf22aec.mail.bellsouth.net@[216.76.216.79]> for ; Mon, 6 Dec 2004 22:11:45 -0500 Message-ID: <41B51FF3.60403@bellsouth.net> Date: Mon, 06 Dec 2004 22:13:55 -0500 From: Andrew Jones Organization: Webcoven.org User-Agent: Mozilla Thunderbird 0.9 (X11/20041204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: 6.0-current and USB modem problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 03:11:47 -0000 After cvsuping to current and then building the world with a new kernel and everything, I found that no matter what I did, the usb modem using ucom0 didn't work; it would hang with trying to dial out (it would say 'working in whatever mode' then hang). After reading commit logs and the updating file, I changed the device name in /etc/ppp/ppp.conf to the new one (cuau0) with no avail. Anybody know why this is happening and/or how to fix it? From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 04:47:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9782A16A4CE for ; Tue, 7 Dec 2004 04:47:39 +0000 (GMT) Received: from frodo.anembo.nu.org (dsl-202-173-130-73.nsw.westnet.com.au [202.173.130.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B2AD43D62 for ; Tue, 7 Dec 2004 04:47:38 +0000 (GMT) (envelope-from christopher@nu.org) Received: from elrond.anembo.nu.org (elrond.anembo.nu.org [10.5.1.3]) by frodo.anembo.nu.org (8.13.1/8.13.1) with SMTP id iB74lZoe007111 for ; Tue, 7 Dec 2004 15:47:36 +1100 (EST) Received: by elrond.anembo.nu.org (sSMTP sendmail emulation); Tue, 7 Dec 2004 15:47:34 +1100 Date: Tue, 7 Dec 2004 15:47:34 +1100 From: Christopher Vance To: current@freebsd.org Message-ID: <20041207044734.GA7994@nu.org> References: <200410081937.15068.miha@ghuug.org> <200410291044.34973.soralx@cydem.org> <200410291657.33606.miha@ghuug.org> <20041030004556.B13046@unix.local> <4182BD51.6070800@freebsdbrasil.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <4182BD51.6070800@freebsdbrasil.com.br> Subject: Re: ad0: FAILURE - WRITE_DMA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 04:47:39 -0000 On Fri, Oct 29, 2004 at 06:59:45PM -0300, Patrick Tracanelli wrote: >>In FreeBSD 5.3b7 I have the same problem with the Maxtor 120GB IDE >>ad2: 117246MB [238216/16/63] at ata1-master >>UDMA66 >> >>ad2: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=14301663 >>ad2: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=14301663 >>ad2: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=14301663 >>ad2: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=14301663 >>ad2: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=14301663 >>ad2: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=14301663 >>ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=160532482 >>ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=209834594 >>ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=218490706 >>ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=211340046 >>ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=209834594 >>ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=163587418 >>ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=209834786 >>ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=17312287 I gave up with 5.3 on my SiI3512A with Seagate SATA disks because of this (mine was not only TIMEOUT, but also FAILURE) and related panics. OpenBSD current seems more stable on this hardware. Pity really, as I've been using FreeBSD for years, and they're not quite so friendly over on the other side. My VIA SATA stuff still seems fine with 5.3, so I have to pick between a friendly OS (5.3), and one which can run VMware 4 (L*x). -- Christopher Vance From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 04:58:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7006416A4CE for ; Tue, 7 Dec 2004 04:58:38 +0000 (GMT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B95C43D55 for ; Tue, 7 Dec 2004 04:58:38 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from h00609772adf0.ne.client2.attbi.com ([66.30.114.143]) by comcast.net (rwcrmhc11) with ESMTP id <2004120704583701300shco7e>; Tue, 7 Dec 2004 04:58:37 +0000 Received: from h00609772adf0.ne.client2.attbi.com (localhost [127.0.0.1]) iB74wZ5p000920; Mon, 6 Dec 2004 23:58:35 -0500 (EST) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: (from rodrigc@localhost)iB74wVqH000919; Mon, 6 Dec 2004 23:58:31 -0500 (EST) (envelope-from rodrigc) Date: Mon, 6 Dec 2004 23:58:31 -0500 From: Craig Rodrigues To: Poul-Henning Kamp Message-ID: <20041207045831.GA886@crodrigues.org> References: <90140.1102367413@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <90140.1102367413@critter.freebsd.dk> User-Agent: Mutt/1.4.1i cc: current@freebsd.org Subject: Re: NMOUNT/OMOUNT midway status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 04:58:38 -0000 On Mon, Dec 06, 2004 at 10:10:13PM +0100, Poul-Henning Kamp wrote: > If you want to help me test I keep a patch relative to -current > up to date: > > http://phk.freebsd.dk/patch/nmount.patch I cvsup'd to -current and applied this patch. When I mounted an iso9660 file system, mount showed: on /mnt (cd9660, local, read-only) I applied this patch (based on what I saw in the UDF fs code): --- sys/isofs/cd9660/cd9660_vfsops.c.org Mon Dec 6 23:34:15 2004 +++ sys/isofs/cd9660/cd9660_vfsops.c Mon Dec 6 23:48:38 2004 @@ -203,6 +203,8 @@ return error; } imp = VFSTOISOFS(mp); + + vfs_mountedfrom(mp, fspec); return 0; } And now mount shows: /dev/acd0 on /mnt (cd9660, local, read-only) -- Craig Rodrigues rodrigc@crodrigues.org From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 06:20:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D41F16A4CE for ; Tue, 7 Dec 2004 06:20:23 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 30D9543D49 for ; Tue, 7 Dec 2004 06:20:13 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 26742 invoked by uid 65534); 7 Dec 2004 06:20:11 -0000 Received: from p5087DF53.dip.t-dialin.net (EHLO lofi.dyndns.org) (80.135.223.83) by mail.gmx.net (mp014) with SMTP; 07 Dec 2004 07:20:11 +0100 X-Authenticated: #443188 Received: from kiste.my.domain (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iB76K4d1089300 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Tue, 7 Dec 2004 07:20:07 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: freebsd-current@freebsd.org Date: Tue, 7 Dec 2004 07:18:28 +0100 User-Agent: KMail/1.7.1 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart8106911.aYQrEq6lGm"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412070718.36750.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new Subject: Watchdog questions X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 06:20:23 -0000 --nextPart8106911.aYQrEq6lGm Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I recently configured SW_WATCHDOG in my kernel and put watchdogd_enable=3D"= YES"=20 in my rc.conf, hoping it would reboot the machine automatically if it hangs= =2E=20 However, it seems that the watchdog just triggers a panic without resetting= =20 the machine - how can I configure things to reboot? Also I noticed that the default timeout (what is the default timeout anyway= -=20 the watchdogd manpage doesn't tell) is a little short: I got a watchdogd=20 triggered panic once during a normal shutdown, after "rebooting" was printe= d=20 but before the reboot could happen. =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart8106911.aYQrEq6lGm Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBtUs8Xhc68WspdLARAhouAJwIWIS2QC8W1+gVFliVGdGvrozQKQCbB+GY WE0rNufRt+pUgrKKB8vWqv4= =TXFw -----END PGP SIGNATURE----- --nextPart8106911.aYQrEq6lGm-- From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 06:38:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1539816A4CE for ; Tue, 7 Dec 2004 06:38:35 +0000 (GMT) Received: from smtp1.server.rpi.edu (smtp1.server.rpi.edu [128.113.2.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id A11EC43D2F for ; Tue, 7 Dec 2004 06:38:34 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp1.server.rpi.edu (8.13.0/8.13.0) with ESMTP id iB76cX5E014178; Tue, 7 Dec 2004 01:38:33 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: <20041207044734.GA7994@nu.org> References: <200410081937.15068.miha@ghuug.org> <200410291044.34973.soralx@cydem.org> <200410291657.33606.miha@ghuug.org> <20041030004556.B13046@unix.local> <4182BD51.6070800@freebsdbrasil.com.br> <20041207044734.GA7994@nu.org> Date: Tue, 7 Dec 2004 01:38:32 -0500 To: Christopher Vance , freebsd-current@FreeBSD.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) Subject: Re: ad0: FAILURE - WRITE_DMA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 06:38:35 -0000 At 3:47 PM +1100 12/7/04, Christopher Vance wrote: >I gave up with 5.3 on my SiI3512A with Seagate SATA disks because of >this (mine was not only TIMEOUT, but also FAILURE) and related panics. > >OpenBSD current seems more stable on this hardware. Pity really, as >I've been using FreeBSD for years, and they're not quite so friendly >over on the other side. > >My VIA SATA stuff still seems fine with 5.3, so I have to pick between >a friendly OS (5.3), and one which can run VMware 4 (L*x). I can sympathize. I've been having WRITE_DMA problems, apparently from a variety of causes. At the moment my disk seems to be working fine, but every time I think I can *trust* the disk, I start getting another round of headaches. About all I can do is guess at some possible problems. What is the capacity of the Seagate drive that you're having trouble with? Are you using vinum or gvinum on it? Is your machine set up with a serial console? If the machine panics, can you get a core-dump of it, or do you just get a disk error when it tries to write the dump to disk? [disclaimer: I do not work at this level, so I wouldn't know what to do to fix this. I'm just saying that I know how frustrating these WRITE_DMA errors can be...] -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 07:02:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD92E16A4CE for ; Tue, 7 Dec 2004 07:02:26 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEBFF43D39 for ; Tue, 7 Dec 2004 07:02:25 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB772AE9099058; Tue, 7 Dec 2004 08:02:10 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Craig Rodrigues From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 06 Dec 2004 23:58:31 EST." <20041207045831.GA886@crodrigues.org> Date: Tue, 07 Dec 2004 08:02:10 +0100 Message-ID: <99057.1102402930@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@freebsd.org Subject: Re: NMOUNT/OMOUNT midway status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 07:02:26 -0000 thanks ! In message <20041207045831.GA886@crodrigues.org>, Craig Rodrigues writes: >On Mon, Dec 06, 2004 at 10:10:13PM +0100, Poul-Henning Kamp wrote: >> If you want to help me test I keep a patch relative to -current >> up to date: >> >> http://phk.freebsd.dk/patch/nmount.patch > >I cvsup'd to -current and applied this patch. >When I mounted an iso9660 file system, mount showed: > > on /mnt (cd9660, local, read-only) > > >I applied this patch (based on what I saw in the UDF fs code): > >--- sys/isofs/cd9660/cd9660_vfsops.c.org Mon Dec 6 23:34:15 2004 >+++ sys/isofs/cd9660/cd9660_vfsops.c Mon Dec 6 23:48:38 2004 >@@ -203,6 +203,8 @@ > return error; > } > imp = VFSTOISOFS(mp); >+ >+ vfs_mountedfrom(mp, fspec); > return 0; > } > > >And now mount shows: > >/dev/acd0 on /mnt (cd9660, local, read-only) > > >-- >Craig Rodrigues >rodrigc@crodrigues.org > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 07:02:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1479516A4CF; Tue, 7 Dec 2004 07:02:31 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CBA143D5E; Tue, 7 Dec 2004 07:02:30 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB772T1F099074; Tue, 7 Dec 2004 08:02:29 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Doug White From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 06 Dec 2004 18:55:38 PST." <20041206185349.G23442@carver.gumbysoft.com> Date: Tue, 07 Dec 2004 08:02:29 +0100 Message-ID: <99073.1102402949@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@freebsd.org Subject: Re: NMOUNT/OMOUNT midway status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 07:02:31 -0000 In message <20041206185349.G23442@carver.gumbysoft.com>, Doug White writes: >On Tue, 7 Dec 2004, Ruslan Ermilov wrote: > >> Are you aware of the following problem? On a recent >> -CURRENT system, remounting / by fsck(8) is not possible: >> >> mount reload of '/' failed: Invalid argument >> >> This has been triggered by an unclean shutdown due to a >> panic, but can also be reproduced easily by booting or >> shutting down into single-user mode, having / mounted >> read-only, and typing "fsck /". > >I got this today on one of my machines. It would seem that whatever in the >kernel checks the clean bit isn't picking it up after fsck finishes. > >I wonder if this may be related to the ufs/ffs aliasing problem fixed >earlier. Fixed. No it was slightly different. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 07:02:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1781B16A4CE; Tue, 7 Dec 2004 07:02:49 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E49243D55; Tue, 7 Dec 2004 07:02:48 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB772lGq099085; Tue, 7 Dec 2004 08:02:47 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Ruslan Ermilov From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 07 Dec 2004 00:54:33 +0200." <20041206225432.GA87510@ip.net.ua> Date: Tue, 07 Dec 2004 08:02:47 +0100 Message-ID: <99084.1102402967@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@freebsd.org Subject: Re: NMOUNT/OMOUNT midway status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 07:02:49 -0000 In message <20041206225432.GA87510@ip.net.ua>, Ruslan Ermilov writes: >Are you aware of the following problem? On a recent >-CURRENT system, remounting / by fsck(8) is not possible: > > mount reload of '/' failed: Invalid argument > >This has been triggered by an unclean shutdown due to a >panic, but can also be reproduced easily by booting or >shutting down into single-user mode, having / mounted >read-only, and typing "fsck /". Fixed. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 07:09:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FBAE16A4CE; Tue, 7 Dec 2004 07:09:24 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA82D43D68; Tue, 7 Dec 2004 07:09:23 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB779Msw099249; Tue, 7 Dec 2004 08:09:22 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: =?ISO-8859-1?Q?Jean-S=E9bastien_P=E9dron?= From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 06 Dec 2004 17:04:38 +0100." <41B48316.90004@club-internet.fr> Date: Tue, 07 Dec 2004 08:09:22 +0100 Message-ID: <99248.1102403362@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-current@freebsd.org Subject: Re: panic: Inconsistent vnode bufstrategy X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 07:09:24 -0000 In message <41B48316.90004@club-internet.fr>, =?ISO-8859-1?Q?Jean-S=E9bastien_P =E9dron?= writes: >In file systems like ufs, msdosfs or ext2fs, VOP_BMAP will do: > *ap->a_bop = &VTOI(ap->a_vp)->i_devvp->v_bufobj; >So the vm will call the device bo_strategy callback, and everything works. > >In NTFS, VOP_BMAP is different: > *ap->a_bop = &ap->a_vp->v_bufobj; >The goal is that the vm should call the file system's VOP_STRATEGY, not >the device directly (that's what I guess, I'm not familiar with this fs :-). Spot on, now for an encore, can you also create a patch to fix this ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 08:17:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5B17016A4CE for ; Tue, 7 Dec 2004 08:17:31 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id B62B643D1F for ; Tue, 7 Dec 2004 08:17:30 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB78HRYC000431 for ; Tue, 7 Dec 2004 09:17:27 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 07 Dec 2004 08:15:41 GMT." <200412070815.iB78Ff97049336@repoman.freebsd.org> Date: Tue, 07 Dec 2004 09:17:27 +0100 Message-ID: <430.1102407447@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Subject: Mount megapatch committed: PLEASE TEST!! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 08:17:31 -0000 Please test and report all problems you find! In message <200412070815.iB78Ff97049336@repoman.freebsd.org>, Poul-Henning Kamp writes: >phk 2004-12-07 08:15:41 UTC > > FreeBSD src repository > > Modified files: > sys/fs/devfs devfs_vnops.c > sys/isofs/cd9660 cd9660_vfsops.c > sys/kern init_main.c vfs_init.c vfs_mount.c > vfs_subr.c > sys/nfsclient nfs_vfsops.c > sys/sys mount.h systm.h vnode.h > sys/ufs/ffs ffs_vfsops.c > Log: > The remaining part of nmount/omount/rootfs mount changes. I cannot sensibly > split the conversion of the remaining three filesystems out from the root > mounting changes, so in one go: > [...] -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 08:56:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 816F516A4CE for ; Tue, 7 Dec 2004 08:56:52 +0000 (GMT) Received: from chantry.devlix.dk (chantry.devlix.dk [195.41.43.228]) by mx1.FreeBSD.org (Postfix) with ESMTP id E829B43D53 for ; Tue, 7 Dec 2004 08:56:51 +0000 (GMT) (envelope-from spamtrap1@devlix.dk) Received: by chantry.devlix.dk (Postfix, from userid 1002) id 54CC164A3; Tue, 7 Dec 2004 09:56:50 +0100 (CET) Received: from localhost (localhost.devlix.dk [127.0.0.1]) by chantry.devlix.dk (Postfix) with ESMTP id E226F64A1; Tue, 7 Dec 2004 09:56:44 +0100 (CET) Received: from chantry.devlix.dk ([127.0.0.1]) by localhost (chantry.devlix.dk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 54899-10; Tue, 7 Dec 2004 09:56:42 +0100 (CET) Received: from 192.168.1.175 (unknown [192.168.1.175]) by chantry.devlix.dk (Postfix) with ESMTP id 468B764A0; Tue, 7 Dec 2004 09:56:42 +0100 (CET) From: Jimmy Selgen To: Garance A Drosihn In-Reply-To: References: <200410081937.15068.miha@ghuug.org> <200410291657.33606.miha@ghuug.org> <4182BD51.6070800@freebsdbrasil.com.br> Content-Type: text/plain Date: Tue, 07 Dec 2004 09:56:38 +0100 Message-Id: <1102409798.5240.6.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at devlix.dk X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on chantry.devlix.dk X-Spam-Level: X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=ham version=3.0.1 cc: freebsd-current@FreeBSD.org cc: Christopher Vance Subject: Re: ad0: FAILURE - WRITE_DMA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 08:56:52 -0000 On Tue, 2004-12-07 at 01:38 -0500, Garance A Drosihn wrote: > At 3:47 PM +1100 12/7/04, Christopher Vance wrote: > >I gave up with 5.3 on my SiI3512A with Seagate SATA disks because of > >this (mine was not only TIMEOUT, but also FAILURE) and related panics. I too have been getting TIMEOUT and FAILURE messages with 5.3. Hardware works perfect with 5.2.1, but somewhere around 5.3-BETA7 i started getting FAILURE messages on one of my disks when it returns from powersave/spin down. When trying to access the mounted device after a TIMEOUT i get "Bad file descriptor", and then on a following reboot i get a panic after i finishes syncing disks, like "vlere, negative ref count" or something. setting hw.ata.ata_dma = 0 didn't help. i just got READ_MUL TIMEOUT instead. I tried reinstalling 5.2.1 and it works like a dream there. I already sent my info to sos@, so i'm just sounding off to let you know you're not alone :) /Jimmy From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 10:32:34 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 329AA16A4CE for ; Tue, 7 Dec 2004 10:32:34 +0000 (GMT) Received: from mailout03.sul.t-online.com (mailout03.sul.t-online.com [194.25.134.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4C7E43D5C for ; Tue, 7 Dec 2004 10:32:33 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from fwd02.aul.t-online.de by mailout03.sul.t-online.com with smtp id 1Cbcdx-0004lZ-00; Tue, 07 Dec 2004 11:32:29 +0100 Received: from Andro-Beta.Leidinger.net (VT0AyZZLoeseHEASWsqEzIzDeTxtIlpM3OHpcV4Zumct+jSAVFzAZY@[217.83.18.101]) by fmrl02.sul.t-online.com with esmtp id 1Cbcdj-0m8Nn60; Tue, 7 Dec 2004 11:32:15 +0100 Received: from Andro-Beta.Leidinger.net (localhost [127.0.0.1]) iB7AW0D7045876; Tue, 7 Dec 2004 11:32:00 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: (from www@localhost)iB7AW0wM045875; Tue, 7 Dec 2004 11:32:00 +0100 (CET) (envelope-from Alexander@Leidinger.net) X-Authentication-Warning: Andro-Beta.Leidinger.net: www set sender to Alexander@Leidinger.net using -f Received: from 141.113.101.32 ([141.113.101.32]) by netchild.homeip.net (IMP) with HTTP for ; Tue, 7 Dec 2004 11:32:00 +0100 Message-ID: <1102415520.41b586a04aac0@netchild.homeip.net> Date: Tue, 7 Dec 2004 11:32:00 +0100 From: Alexander Leidinger To: Garance A Drosihn References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.6 / FreeBSD-4.10 X-Originating-IP: 141.113.101.32 X-ID: VT0AyZZLoeseHEASWsqEzIzDeTxtIlpM3OHpcV4Zumct+jSAVFzAZY@t-dialin.net X-TOI-MSGID: ab2a11b1-9158-4f4d-a391-ac498829c693 cc: freebsd-current@freebsd.org cc: =?iso-8859-1?b?U/hyZW4=?= Schmidt Subject: Re: Another twist on WRITE_DMA issues <- ProblemFound X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 10:32:34 -0000 Zitat von Garance A Drosihn : > Maybe it's an overheating issue, or maybe it's something else. But > whatever it is, I am going to assume it's the fault of something in > my PC. I had a similar problem... try to monitor the temperature of the disks with smartmontools. If they are below 50 degree celcius you may be on the safe side, but if the temperature grows over 55 degrees I suggest to install some additional fans to cool the drives. Bye, Alexander. -- http://www.Leidinger.net/ Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org/ netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 11:47:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 417D716A4CE for ; Tue, 7 Dec 2004 11:47:38 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9197443D5A for ; Tue, 7 Dec 2004 11:47:37 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB7BlZ1Z001078 for ; Tue, 7 Dec 2004 12:47:35 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org From: Poul-Henning Kamp Date: Tue, 07 Dec 2004 12:47:35 +0100 Message-ID: <1077.1102420055@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Subject: current panic igmp related ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 11:47:38 -0000 Timecounters tick every 1.000 msec panic: mtx_lock() of spin mutex (null) @ ../../../netinet/igmp.c:431 cpuid = 0 KDB: enter: panic [thread pid 37 tid 100013 ] Stopped at kdb_enter+0x2c: leave db> trace Tracing pid 37 tid 100013 td 0xc3485480 kdb_enter(c06d85e0,100,c3485480,1af,c06e0fec) at kdb_enter+0x2c panic(c06d7ac5,0,c06e0fec,1af,c0713fc4) at panic+0x17f _mtx_lock_flags(c0738740,0,c06e0fec,1af,e4c97cc8) at _mtx_lock_flags+0x82 igmp_slowtimo(e,0,e4c97cf4,c050683a,0) at igmp_slowtimo+0x19 pfslowtimo(0,27,0,2,2) at pfslowtimo+0x66 softclock(0,0,0,c34d07e0,0) at softclock+0x10a ithread_loop(c34cf100,e4c97d48,c34cf100,c04e9200,0) at ithread_loop+0x18e fork_exit(c04e9200,c34cf100,e4c97d48) at fork_exit+0x7e fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe4c97d7c, ebp = 0 --- db> -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 12:42:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F5A716A4CE; Tue, 7 Dec 2004 12:42:01 +0000 (GMT) Received: from relay.bestcom.ru (relay.bestcom.ru [217.72.144.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 707A743D5A; Tue, 7 Dec 2004 12:42:00 +0000 (GMT) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (root@cell.sick.ru [217.72.144.68]) by relay.bestcom.ru (8.13.1/8.12.9) with ESMTP id iB7CfuSr084370 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 7 Dec 2004 15:41:56 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.11/8.12.8) with ESMTP id iB7CftEc077531 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Dec 2004 15:41:55 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id iB7CftNj077530; Tue, 7 Dec 2004 15:41:55 +0300 (MSK) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@freebsd.org using -f Date: Tue, 7 Dec 2004 15:41:54 +0300 From: Gleb Smirnoff To: current@freebsd.org, stable@freebsd.org Message-ID: <20041207124154.GA76825@cell.sick.ru> References: <20041202151048.GA33485@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20041202151048.GA33485@cell.sick.ru> User-Agent: Mutt/1.5.6i X-Virus-Scanned: clamd / ClamAV version devel-20041013, clamav-milter version 0.75l on 127.0.0.1 X-Virus-Status: Clean Subject: Re: [TEST] netgraph callout interface X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 12:42:01 -0000 The patch at http://people.freebsd.org/~glebius/totest/netgraph_callout has been updated. Now it covers the following nodes: ng_bridge.c ng_l2tp.c ng_lmi.c ng_pppoe.c ng_pptpgre.c One more time I ask for testing. The patch can be applied both to HEAD and RELENG_5. On Thu, Dec 02, 2004 at 06:10:48PM +0300, Gleb Smirnoff wrote: T> Dear collegues, T> T> we are working on making netgraph ISR mpsafe. To do it we need to T> fix all (ab)users of bare timeout(9) in src/sys/netgraph. These T> timeout calls are running in synch with netgraph now because timeout(9) T> is Giant-locked. As soon as we mark ISR mpsafe, they are going to break. T> T> This patch semi-mechanically changes all timeout(9) calls to ng_callout(9), T> which runs scheduled callouts in netgraph context: T> T> http://people.freebsd.org/~glebius/totest/netgraph_callout T> T> It can be applied to HEAD or RELENG_5 (not 5.3-RELEASE). It patches T> the following nodes: T> T> ng_bridge.c T> ng_l2tp.c T> ng_lmi.c T> ng_ppp.c T> ng_pppoe.c T> ng_tty.c T> T> If you are using at least one of them, then I'm asking you to test the T> patch and respond. Thanks in advance! T> T> P.S. Sorry for crossposting. The target users are both RELENG_5 and CURRENT. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 12:53:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D29916A4CE; Tue, 7 Dec 2004 12:53:10 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C75743D1F; Tue, 7 Dec 2004 12:53:10 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iB7CokkD088766; Tue, 7 Dec 2004 07:50:46 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iB7Coj7f088763; Tue, 7 Dec 2004 12:50:46 GMT (envelope-from robert@fledge.watson.org) Date: Tue, 7 Dec 2004 12:50:45 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Poul-Henning Kamp In-Reply-To: <1077.1102420055@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: mlaier@freebsd.org cc: current@freebsd.org Subject: Protocol timer running before protocol init (Re: current panic igmp related ?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 12:53:10 -0000 On Tue, 7 Dec 2004, Poul-Henning Kamp wrote: > Timecounters tick every 1.000 msec > panic: mtx_lock() of spin mutex (null) @ ../../../netinet/igmp.c:431 > cpuid = 0 > KDB: enter: panic > [thread pid 37 tid 100013 ] > Stopped at kdb_enter+0x2c: leave > db> trace > Tracing pid 37 tid 100013 td 0xc3485480 > kdb_enter(c06d85e0,100,c3485480,1af,c06e0fec) at kdb_enter+0x2c > panic(c06d7ac5,0,c06e0fec,1af,c0713fc4) at panic+0x17f > _mtx_lock_flags(c0738740,0,c06e0fec,1af,e4c97cc8) at _mtx_lock_flags+0x82 > igmp_slowtimo(e,0,e4c97cf4,c050683a,0) at igmp_slowtimo+0x19 > pfslowtimo(0,27,0,2,2) at pfslowtimo+0x66 > softclock(0,0,0,c34d07e0,0) at softclock+0x10a > ithread_loop(c34cf100,e4c97d48,c34cf100,c04e9200,0) at ithread_loop+0x18e > fork_exit(c04e9200,c34cf100,e4c97d48) at fork_exit+0x7e > fork_trampoline() at fork_trampoline+0x8 > --- trap 0x1, eip = 0, esp = 0xe4c97d7c, ebp = 0 --- igmp_mtx looks to be uninitialized here (BSS memory). This suggests that igmp_slowtimo is being called before igmp_init(), which strikes me as somewhat odd. There's recently been some rerrangement of the domain initialization code to correct potentially related problems, but perhaps things aren't quite there yet. CC'ing Max on general principle. :-) Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 18:50:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F9EB16A4CE for ; Mon, 6 Dec 2004 18:50:53 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id C593C43D46 for ; Mon, 6 Dec 2004 18:50:52 +0000 (GMT) (envelope-from imp@harmony.village.org) Received: from localhost (localhost [IPv6:::1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iB6Il1xr054824; Mon, 6 Dec 2004 11:47:01 -0700 (MST) (envelope-from imp@harmony.village.org) Date: Mon, 06 Dec 2004 11:47:01 -0700 (MST) Message-Id: <20041206.114701.104086228.imp@harmony.village.org> To: jroberson@chesapeake.net From: Warner Losh In-Reply-To: <20041205044145.A18185@mail.chesapeake.net> References: <56325.1102236241@critter.freebsd.dk> <20041205044145.A18185@mail.chesapeake.net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 07 Dec 2004 13:01:54 +0000 cc: phk@phk.freebsd.dk cc: drosih@rpi.edu cc: current@freebsd.org Subject: Re: [TEST/REVIEW]: rootfs mounting code rework X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 18:50:53 -0000 > On Sun, 5 Dec 2004, Poul-Henning Kamp wrote: > > > In message , Garance A Drosihn writes: > > >At 11:08 AM +0100 12/4/04, Poul-Henning Kamp wrote: > > >>http://phk.freebsd.dk/patch/rootfs.patch > > >> > > >>Please test and review. > > > > > >Hmm. Does this mean that we'll always get the correct partition > > >for '/', even if /etc/fstab is wrong for '/'? By "correct", I > > >mean "the partition that the kernel was loaded from". > > > > The loader reads /etc/fstab and picks the entry for '/' out of it > > so I can only pressume that whoever did that disagree with your > > notion of "correct". > > I believe he's referring to the case where you load a kernel from > somewhere other than the default '/'. The only way I've made this work is to put a /etc/fstab on the default / which points to the real one I want to use... Warner From owner-freebsd-current@FreeBSD.ORG Mon Dec 6 19:36:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B48A316A4CE for ; Mon, 6 Dec 2004 19:36:52 +0000 (GMT) Received: from phoenix.smluc.org (phoenix.smluc.org [12.28.48.23]) by mx1.FreeBSD.org (Postfix) with SMTP id 0CAA643D31 for ; Mon, 6 Dec 2004 19:36:50 +0000 (GMT) (envelope-from erik@phoenix.smluc.org) Received: (qmail 415 invoked by uid 1000); 6 Dec 2004 19:39:21 -0000 Date: Mon, 6 Dec 2004 13:39:21 -0600 From: Erik Greenwald To: Doug White Message-ID: <20041206193921.GA31784@phoenix.smluc.org> References: <006501c4da28$5692e130$0a64a8c0@techiebod.com> <20041206105139.E19661@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041206105139.E19661@carver.gumbysoft.com> User-Agent: Mutt/1.5.6+20040722i X-Mailman-Approved-At: Tue, 07 Dec 2004 13:01:54 +0000 cc: Henry Whincup cc: freebsd-current@freebsd.org cc: erikg@arl.army.mil Subject: Re: ffs_clusteralloc: allocated out of group on 5TB fs (5.3-Stable) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2004 19:36:52 -0000 On Mon, Dec 06, 2004 at 10:56:34AM -0800, Doug White wrote: > On Sat, 4 Dec 2004, Henry Whincup wrote: > > > On a machine with a 5TB array I created a single partition via gpt and a > > filesystem using the defaults from newfs. > > > > All seemed well until I tried to fill the partition with data. With "only" > > 870GB or so used utilities started reporting the disk as full. Shortly (a > > few hours) after the machine panic'd. I, too, have a 5tb box (two 2.5tb 3ware 9xxx raid5's and gstripe), and see the issue fairly quickly. One of my users has a 50gb tarball of his homedir, and about 20g into untarring, it panics with the message. 5.3p1 > > Ooh, fun. I wish I had a 5TB array to play with :) > > > During this time I had been trying to copy file via nfs and rsync onto the > > array. After several crashes I tried a simple "dd if=/dev/zero of=./file" > > and after writing ~33GB the machine rebooted (the panic details below are > > from this reboot) I wasn't able to get dd to crash it, even with 100g out file. > > > > Details follow: > > [..] > > Backtrace: > > #0 0xc060ce82 in doadump () > > #1 0xc060d47b in boot () > > #2 0xc060d7a1 in panic () > > #3 0xc073445e in ffs_clusteralloc () > > #4 0xc0733680 in ffs_hashalloc () > > #5 0xc07329ea in ffs_reallocblks_ufs2 () > > #6 0xc073205a in ffs_reallocblks () > > #7 0xc0657e7c in cluster_write () > > #8 0xc074c350 in ffs_write () > > #9 0xc066bf10 in vn_write () > > #10 0xc062d624 in dofilewrite () > > #11 0xc062d4d1 in write () > > #12 0xc07bb07f in syscall () > > #13 0xc07a8a0f in Xint0x80_syscall () > > > > Kernel is the default SMP kernel and sources are from 28th Nov 2004. > > > > I assume a proper debug kernel with symbols would be more helpful, but I > > just wanted to know if this was a known bug - or something I have done > > wrong, first. > > Other than that is there anything else I can provide to help find this bug? > > Very large FFS filesystems have not been extensively tested. Maybe you can > help :) dang > > You should be able to compile GENERIC with > > makeoptions "DEBUG=-g" > > in the config file and that will leave a kernel.debug in the compile > directory that you can use. > > Once you get that loaded up the output of 'bt full' would be nice to have. > I suspect an integer overflow in dtog(), which is a macro. > > 1545 if (dtog(fs, bno) != cg) > 1546 panic("ffs_clusteralloc: allocated out of group"); a couple weeks ago, when I found the issue, I tried dumping that line using a printf and got dtog(0xc4896800, -1894026712) != 25518 (I think I used %x, %d, %d) I've no idea what those #'s mean, and couldn't find any documentation on 'dtog' (something to group?) I have a kernel with the DEBUG=-g option, (and config -g), can't get the dang thing to dump, though > > -- > Doug White | FreeBSD: The Power to Serve > dwhite@gumbysoft.com | www.FreeBSD.org > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- -Erik [http://math.smsu.edu/~erik] The opinions expressed by me are not necessarily opinions. In all probability, they are random rambling, and to be ignored. Failure to ignore may result in severe boredom or confusion. Shake well before opening. Keep Refrigerated. From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 13:25:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9754916A4CE; Tue, 7 Dec 2004 13:25:16 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB2BC43D45; Tue, 7 Dec 2004 13:25:15 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.208] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1CbfL8-00032Z-00; Tue, 07 Dec 2004 14:25:14 +0100 Received: from [217.227.158.40] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1CbfL8-0001E9-00; Tue, 07 Dec 2004 14:25:14 +0100 From: Max Laier To: Robert Watson Date: Tue, 7 Dec 2004 14:25:39 +0100 User-Agent: KMail/1.7.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5864589.AEktvzQOIo"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412071425.47840.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 cc: Poul-Henning Kamp cc: current@freebsd.org Subject: Re: Protocol timer running before protocol init (Re: current panic igmp related ?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 13:25:17 -0000 --nextPart5864589.AEktvzQOIo Content-Type: multipart/mixed; boundary="Boundary-01=_V9atBeVGf/h7x4/" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-01=_V9atBeVGf/h7x4/ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 07 December 2004 13:50, Robert Watson wrote: > On Tue, 7 Dec 2004, Poul-Henning Kamp wrote: > > Timecounters tick every 1.000 msec > > panic: mtx_lock() of spin mutex (null) @ ../../../netinet/igmp.c:431 > > cpuid =3D 0 > > KDB: enter: panic > > [thread pid 37 tid 100013 ] > > Stopped at kdb_enter+0x2c: leave > > db> trace > > Tracing pid 37 tid 100013 td 0xc3485480 > > kdb_enter(c06d85e0,100,c3485480,1af,c06e0fec) at kdb_enter+0x2c > > panic(c06d7ac5,0,c06e0fec,1af,c0713fc4) at panic+0x17f > > _mtx_lock_flags(c0738740,0,c06e0fec,1af,e4c97cc8) at _mtx_lock_flags+0x= 82 > > igmp_slowtimo(e,0,e4c97cf4,c050683a,0) at igmp_slowtimo+0x19 > > pfslowtimo(0,27,0,2,2) at pfslowtimo+0x66 > > softclock(0,0,0,c34d07e0,0) at softclock+0x10a > > ithread_loop(c34cf100,e4c97d48,c34cf100,c04e9200,0) at ithread_loop+0x1= 8e > > fork_exit(c04e9200,c34cf100,e4c97d48) at fork_exit+0x7e > > fork_trampoline() at fork_trampoline+0x8 > > --- trap 0x1, eip =3D 0, esp =3D 0xe4c97d7c, ebp =3D 0 --- > > igmp_mtx looks to be uninitialized here (BSS memory). This suggests that > igmp_slowtimo is being called before igmp_init(), which strikes me as > somewhat odd. There's recently been some rerrangement of the domain > initialization code to correct potentially related problems, but perhaps > things aren't quite there yet. CC'ing Max on general principle. :-) That's not mine. Didn't touch the protosw parts ;)=20 Still, the attached diff might help. It looks like we try to use Giant to=20 protect the pfslowtimo() array walking, thus we must make sure that we hold= =20 Giant long enough while we set things up. I hope protosw_init() and therein= =20 called pr_init()s are fine with Giant hold. It'd surprise me, if not. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --Boundary-01=_V9atBeVGf/h7x4/ Content-Type: text/x-diff; charset="iso-8859-1"; name="GIANTprotosw_init.diff" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="GIANTprotosw_init.diff" Index: uipc_domain.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /usr/store/mlaier/fcvs/src/sys/kern/uipc_domain.c,v retrieving revision 1.42 diff -u -r1.42 uipc_domain.c =2D-- uipc_domain.c 2 Dec 2004 15:47:15 -0000 1.42 +++ uipc_domain.c 7 Dec 2004 13:19:59 -0000 @@ -337,12 +337,12 @@ /* Copy the new struct protosw over the spacer. */ bcopy(npr, fpr, sizeof(*fpr)); =20 =2D /* Job is done, no more protection required. */ =2D mtx_unlock(&Giant); =2D /* Initialize and activate the protocol. */ protosw_init(fpr); =20 + /* Job is done, no more protection required. */ + mtx_unlock(&Giant); + return (0); } =20 --Boundary-01=_V9atBeVGf/h7x4/-- --nextPart5864589.AEktvzQOIo Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBta9bXyyEoT62BG0RAhYfAJ4zMrV97Fosq4R0hSCX5AQAHYg+RACePkK1 oloCFM4hGQ54hgVpsg7C8qk= =pHRu -----END PGP SIGNATURE----- --nextPart5864589.AEktvzQOIo-- From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 14:34:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0745516A4CE for ; Tue, 7 Dec 2004 14:34:02 +0000 (GMT) Received: from peedub.jennejohn.org (Jb2f0.j.pppool.de [85.74.178.240]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3784A43D6A for ; Tue, 7 Dec 2004 14:34:01 +0000 (GMT) (envelope-from garyj@jennejohn.org) Received: from jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.13.1/8.11.6) with ESMTP id iB7EXxXQ000829 for ; Tue, 7 Dec 2004 15:33:59 +0100 (CET) (envelope-from garyj@jennejohn.org) Message-Id: <200412071433.iB7EXxXQ000829@peedub.jennejohn.org> X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: freebsd-current@freebsd.org From: Gary Jennejohn Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_-12333322120" Date: Tue, 07 Dec 2004 15:33:59 +0100 Sender: garyj@jennejohn.org Subject: NTFS after phk's changes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 14:34:02 -0000 This is a multipart MIME message. --==_Exmh_-12333322120 Content-Type: text/plain; charset=us-ascii NTFS is unusable after phk's changes. Mounting an NTFS file system results in a panic. Line 336 in /sys/fs/ntfs/ntfs_vfsops.c is the culprit: ntfs_u28_init(ntmp, NULL, cs_local, cs_ntfs); Passing NULL causes the panic because ntfs_u28_init() dereferences the pointer without checking whether it's NULL. With the (hopefully) attached patch I can at least mount and ls a NTFS file system, which is about all that could be done prior to phk's modifications. The handling of (p == NULL) in ntfs_u28() is questionable, but it works for my test case. -------- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org garyj[at]denx.de --==_Exmh_-12333322120 Content-Type: text/plain ; name="ntfs_subr.diff"; charset=us-ascii Content-Description: ntfs_subr.diff --- /sys/fs/ntfs/ntfs_subr.c.orig Tue Dec 7 13:17:33 2004 +++ /sys/fs/ntfs/ntfs_subr.c Tue Dec 7 13:17:10 2004 @@ -2049,6 +2049,10 @@ return (0); } + /* prevent a panic */ + if (u2w == NULL) + return (0); + MALLOC(u28, char **, 256 * sizeof(char*), M_TEMP, M_WAITOK | M_ZERO); for (i=0; i<256; i++) { --- /sys/fs/ntfs/ntfs_subr.c.orig Tue Dec 7 13:46:54 2004 +++ /sys/fs/ntfs/ntfs_subr.c Tue Dec 7 14:59:06 2004 @@ -2168,9 +2168,10 @@ return ('?'); } - p = ntmp->ntm_u28[(wc>>8)&0xFF]; + /* prevent a panic */ + p = ntmp->ntm_u28?ntmp->ntm_u28[(wc>>8)&0xFF]:NULL; if (p == NULL) - return ('_'); + return (wc); return (p[wc&0xFF]&0xFF); } --==_Exmh_-12333322120-- From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 14:39:05 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8EBC416A4CE; Tue, 7 Dec 2004 14:39:05 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1279743D5C; Tue, 7 Dec 2004 14:39:05 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.161] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1CbgUZ-0002yV-00; Tue, 07 Dec 2004 15:39:03 +0100 Received: from [217.227.158.40] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1CbgUY-0000u9-00; Tue, 07 Dec 2004 15:39:03 +0100 From: Max Laier To: freebsd-current@freebsd.org Date: Tue, 7 Dec 2004 15:39:40 +0100 User-Agent: KMail/1.7.1 References: <200412071425.47840.max@love2party.net> In-Reply-To: <200412071425.47840.max@love2party.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1123259.71DLjs6cSq"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412071539.50647.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 cc: Poul-Henning Kamp cc: Robert Watson Subject: Re: Protocol timer running before protocol init (Re: current panic igmp related ?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 14:39:05 -0000 --nextPart1123259.71DLjs6cSq Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 07 December 2004 14:25, Max Laier wrote: > On Tuesday 07 December 2004 13:50, Robert Watson wrote: > > On Tue, 7 Dec 2004, Poul-Henning Kamp wrote: > > > Timecounters tick every 1.000 msec > > > panic: mtx_lock() of spin mutex (null) @ ../../../netinet/igmp.c:431 > > > cpuid =3D 0 > > > KDB: enter: panic > > > [thread pid 37 tid 100013 ] > > > Stopped at kdb_enter+0x2c: leave > > > db> trace > > > Tracing pid 37 tid 100013 td 0xc3485480 > > > kdb_enter(c06d85e0,100,c3485480,1af,c06e0fec) at kdb_enter+0x2c > > > panic(c06d7ac5,0,c06e0fec,1af,c0713fc4) at panic+0x17f > > > _mtx_lock_flags(c0738740,0,c06e0fec,1af,e4c97cc8) at > > > _mtx_lock_flags+0x82 igmp_slowtimo(e,0,e4c97cf4,c050683a,0) at > > > igmp_slowtimo+0x19 > > > pfslowtimo(0,27,0,2,2) at pfslowtimo+0x66 > > > softclock(0,0,0,c34d07e0,0) at softclock+0x10a > > > ithread_loop(c34cf100,e4c97d48,c34cf100,c04e9200,0) at > > > ithread_loop+0x18e fork_exit(c04e9200,c34cf100,e4c97d48) at > > > fork_exit+0x7e > > > fork_trampoline() at fork_trampoline+0x8 > > > --- trap 0x1, eip =3D 0, esp =3D 0xe4c97d7c, ebp =3D 0 --- > > > > igmp_mtx looks to be uninitialized here (BSS memory). This suggests th= at > > igmp_slowtimo is being called before igmp_init(), which strikes me as > > somewhat odd. There's recently been some rerrangement of the domain > > initialization code to correct potentially related problems, but perhaps > > things aren't quite there yet. CC'ing Max on general principle. :-) > > That's not mine. Didn't touch the protosw parts ;) > > Still, the attached diff might help. It looks like we try to use Giant to > protect the pfslowtimo() array walking, thus we must make sure that we ho= ld > Giant long enough while we set things up. I hope protosw_init() and there= in > called pr_init()s are fine with Giant hold. It'd surprise me, if not. Actually, that will only help in the debug.mpsafenet=3D0 case. A better fix= is=20 to initialize first and hook into the array afterwards - not sure if that i= s=20 a safe thing to do for all protocols. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1123259.71DLjs6cSq Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBtcC2XyyEoT62BG0RAhOxAJ44hE17qIurLkl723YITFGgQWtc4ACeJ5XM yEwDoXDh3tB3mIrmIpCg67Y= =bejD -----END PGP SIGNATURE----- --nextPart1123259.71DLjs6cSq-- From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 15:33:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7386B16A4CE; Tue, 7 Dec 2004 15:33:01 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8815C43D70; Tue, 7 Dec 2004 15:33:00 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB7FWxHp090419; Tue, 7 Dec 2004 17:32:59 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 99552-13; Tue, 7 Dec 2004 17:32:58 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB7FWwWk090416 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Dec 2004 17:32:58 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iB7FWw9R002028; Tue, 7 Dec 2004 17:32:58 +0200 (EET) (envelope-from ru) Date: Tue, 7 Dec 2004 17:32:57 +0200 From: Ruslan Ermilov To: current@FreeBSD.org, stable@FreeBSD.org Message-ID: <20041207153257.GE1336@ip.net.ua> Mail-Followup-To: Ruslan Ermilov , current@FreeBSD.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3oCie2+XPXTnK5a5" Content-Disposition: inline User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: amd64@FreeBSD.org Subject: [TEST] Updated port net/nvnet X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 15:33:01 -0000 --3oCie2+XPXTnK5a5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I'm the lucky owner of the ASUS SK8N (amd64) motherboard with the onboard NVIDIA MCP Ethernet. With this patch, http://people.freebsd.org/~ru/patches/port_net_nvnet.patch I'm happily running it for three days without any glitches noticed so far: : nv0: port 0xec00-0xec07 mem 0xfeb= fc000-0xfebfcfff irq 5 at device 5.0 on pci0 : nv0: Ethernet address 00:0e:a6:54:dc:67 : miibus0: on nv0 : rlphy0: on miibus0 : rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto : nv0: Ethernet address: 00:0e:a6:54:dc:67 : nv0: [GIANT-LOCKED] I'd be grateful if someone could test this update on i386. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --3oCie2+XPXTnK5a5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBtc0pqRfpzJluFF4RAkxCAJ91k1u3NhuMZOMIAhcRZhPlS6UTbgCeKIPq 1kwZrEJ4W8Jj3lk8ZLlkYpM= =p0Ey -----END PGP SIGNATURE----- --3oCie2+XPXTnK5a5-- From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 18:02:05 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14BA616A4CE for ; Tue, 7 Dec 2004 18:02:05 +0000 (GMT) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED0C543D5D for ; Tue, 7 Dec 2004 18:02:04 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) iB7I1jwR022028; Tue, 7 Dec 2004 10:02:03 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (h229.neville-neil.com [209.157.133.229] (may be forged)) by mail.meer.net (8.12.10/8.12.10/meer) with ESMTP id iB7I1X7j027574; Tue, 7 Dec 2004 10:01:34 -0800 (PST) (envelope-from gnn@neville-neil.com) Date: Tue, 07 Dec 2004 10:01:30 -0800 Message-ID: From: gnn@FreeBSD.org To: Max Laier Sent-via: Max Laier Sent-via: freebsd-current@freebsd.org In-Reply-To: <200412071539.50647.max@love2party.net> References: <200412071425.47840.max@love2party.net> <200412071539.50647.max@love2party.net> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.5 Emacs/21.2 (powerpc-apple-darwin) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: freebsd-current@FreeBSD.org Subject: Re: Protocol timer running before protocol init (Re: current panic igmp related ?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 18:02:05 -0000 At Tue, 7 Dec 2004 15:39:40 +0100, Max Laier wrote: > Actually, that will only help in the debug.mpsafenet=0 case. A better fix is > to initialize first and hook into the array afterwards - not sure if that is > a safe thing to do for all protocols. I'm not sure how safe it is for IPv6, I just went and glanced at the code, but perhaps we should just force this anyways, as it's the "right thing to do." Later, George From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 18:10:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFC5F16A4CE for ; Tue, 7 Dec 2004 18:10:57 +0000 (GMT) Received: from lakermmtao08.cox.net (lakermmtao08.cox.net [68.230.240.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E58043D60 for ; Tue, 7 Dec 2004 18:10:57 +0000 (GMT) (envelope-from mkucenski@cox.net) Received: from smtp.east.cox.net ([172.18.52.53]) by lakermmtao08.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with SMTP id <20041207181056.OJMF28664.lakermmtao08.cox.net@smtp.east.cox.net> for ; Tue, 7 Dec 2004 13:10:56 -0500 X-Mailer: Openwave WebEngine, version 2.8.15 (webedge20-101-1103-20040528) From: Matt Kucenski To: Date: Tue, 7 Dec 2004 13:10:56 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20041207181056.OJMF28664.lakermmtao08.cox.net@smtp.east.cox.net> Subject: ATAPI Problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: m.kucenski@computer.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 18:10:57 -0000 I have had this problem with my DVD drive since 5.3RC1. I just installed 6-LATEST hoping that the problem may have been corrected, but no such luck. A normal boot of the GENERIC kernel gives these messages: acd0: FAILURE - MODE_SENSE_BIG timed out acd0: FAILURE - MODE_SENSE_BIG timed out acd0: FAILURE - MODE_SENSE_BIG timed out acd0: FAILURE - MODE_SENSE_BIG timed out acd0: FAILURE - MODE_SENSE_BIG timed out acd0: CDROM at ata1-master UDMA33 acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - PREVENT_ALLOW timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - PREVENT_ALLOW timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - PREVENT_ALLOW timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - PREVENT_ALLOW timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - PREVENT_ALLOW timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - TEST_UNIT_READY timed out acd0: FAILURE - PREVENT_ALLOW timed out Afterwards, I am unable to mount a CD. I receive several more of the same "timed out" messages, followed by "Input/output error" message when running 'mount /cdrom'. If I run 'atacontrol mode 1 BIOSPIO BIOSPIO' (DVD drive is only drive on second ata channel), I receive one acd0: FAILURE - TEST_UNIT_READY timed out message and then the drive will mount normally. Also, if I boot verbosely, my dmesg shows this: acd0: CDRW drive at ata1 as master acd0: read 6890KB/s (6890KB/s) write 2755KB/s (2755KB/s), 2048KB buffer, PIO4 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, packet acd0: Writes: CDR, CDRW, test write, burnproof acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: CD-R 120mm data disc No errors and the drive will mount normally. I have tried several combinations of slave/master on different ATA channels with the same results. I have also tried booting with/without ACPI and with/without DMA (hw.ata.atapi_dma="0/1" in loader.conf) and combinations of the two. Any ideas where else I can look to find the source of this problem? Thanks, -Matt From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 18:30:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83F7716A4CE for ; Tue, 7 Dec 2004 18:30:39 +0000 (GMT) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC45B43D54 for ; Tue, 7 Dec 2004 18:30:38 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.13.0/8.13.0) with ESMTP id iB7IUUQn018984; Tue, 7 Dec 2004 13:30:32 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: <1102415520.41b586a04aac0@netchild.homeip.net> References: <1102415520.41b586a04aac0@netchild.homeip.net> Date: Tue, 7 Dec 2004 13:30:30 -0500 To: Alexander Leidinger From: Garance A Drosihn Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) cc: freebsd-current@freebsd.org cc: =?iso-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: Another twist on WRITE_DMA issues <- ProblemFound X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 18:30:39 -0000 At 11:32 AM +0100 12/7/04, Alexander Leidinger wrote: >Zitat von Garance A Drosihn : > > > Maybe it's an overheating issue, or maybe it's something else. > > But whatever it is, I am going to assume it's the fault of > > something in my PC. > >I had a similar problem... try to monitor the temperature of the >disks with smartmontools. If they are below 50 degree celcius you >may be on the safe side, but if the temperature grows over 55 >degrees I suggest to install some additional fans to cool the >drives. Well, I have a dual-boot system. One system is a very recent snapshot of -stable, and it is getting no errors. The second system was a copy of a snapshot I had built in late October. It was the one getting lots of WRITE_DMA errors. After my previous message in this thread, I copied the kernel from the first system to the second, and was able to do an up-to-the-minute build of 6.x-current on it. I installed that. I then started up a sequence of five consecutive buildworlds, closed up my office and went home for the night. My office always warms up a few degrees when the door is closed for a few hours. The PC finished all five of those buildworlds without a single warning or error. So, now I'm thinking (hoping?) that at least some of my problems have been fixed by system changes between late October and now. Of course, now that I've said that, it will probably start giving errors again... One other long-shot guess on my problems. After thinking about it awhile, it seemed that I was much much more likely to have problems when I was working on the serial console. Also, this PC is the first time that I have set up a serial console on FreeBSD. So, the other thing I did last night (before I did the first build of 6.x) was to get rid of the serial-console setup. This is one step short of using tea-leaves to guess at my problem, but it seemed worth a try. If the stupid PC remains reliable under load for a few weeks, then I will switch the serial console back on and see if my problems return. I realize my reports so far have been pretty useless to S=F8ren, but they are all I have been able come up with... Sorry about that. -- Garance Alistair Drosehn =3D gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 18:36:53 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5AAD16A4CE; Tue, 7 Dec 2004 18:36:53 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 933D143D6D; Tue, 7 Dec 2004 18:36:53 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 83E4172DD4; Tue, 7 Dec 2004 10:36:53 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 7C81F72DCB; Tue, 7 Dec 2004 10:36:53 -0800 (PST) Date: Tue, 7 Dec 2004 10:36:53 -0800 (PST) From: Doug White To: Poul-Henning Kamp In-Reply-To: <99073.1102402949@critter.freebsd.dk> Message-ID: <20041207103619.B30209@carver.gumbysoft.com> References: <99073.1102402949@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: NMOUNT/OMOUNT midway status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 18:36:53 -0000 On Tue, 7 Dec 2004, Poul-Henning Kamp wrote: > >I got this today on one of my machines. It would seem that whatever in the > >kernel checks the clean bit isn't picking it up after fsck finishes. > > > >I wonder if this may be related to the ufs/ffs aliasing problem fixed > >earlier. > > Fixed. No it was slightly different. Cool, thanks -- I'll try panicking that test box again and see if it works :) -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 23:06:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC70216A4CE; Tue, 7 Dec 2004 23:06:35 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00D9D43D31; Tue, 7 Dec 2004 23:06:35 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id A7F637A403; Tue, 7 Dec 2004 15:06:34 -0800 (PST) Message-ID: <41B6377A.2070003@elischer.org> Date: Tue, 07 Dec 2004 15:06:34 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Gleb Smirnoff References: <20041202151048.GA33485@cell.sick.ru> <20041207124154.GA76825@cell.sick.ru> In-Reply-To: <20041207124154.GA76825@cell.sick.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: stable@freebsd.org cc: current@freebsd.org Subject: Re: [TEST] netgraph callout interface X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 23:06:36 -0000 Gleb Smirnoff wrote: > The patch at > > http://people.freebsd.org/~glebius/totest/netgraph_callout > >has been updated. Now it covers the following nodes: > > ng_bridge.c > ng_l2tp.c > ng_lmi.c > ng_pppoe.c > ng_pptpgre.c > >One more time I ask for testing. The patch can be applied both to HEAD >and RELENG_5. > the bits I am familiar with look reasonable. > >On Thu, Dec 02, 2004 at 06:10:48PM +0300, Gleb Smirnoff wrote: >T> Dear collegues, >T> >T> we are working on making netgraph ISR mpsafe. To do it we need to >T> fix all (ab)users of bare timeout(9) in src/sys/netgraph. These >T> timeout calls are running in synch with netgraph now because timeout(9) >T> is Giant-locked. As soon as we mark ISR mpsafe, they are going to break. >T> >T> This patch semi-mechanically changes all timeout(9) calls to ng_callout(9), >T> which runs scheduled callouts in netgraph context: >T> >T> http://people.freebsd.org/~glebius/totest/netgraph_callout >T> >T> It can be applied to HEAD or RELENG_5 (not 5.3-RELEASE). It patches >T> the following nodes: >T> >T> ng_bridge.c >T> ng_l2tp.c >T> ng_lmi.c >T> ng_ppp.c >T> ng_pppoe.c >T> ng_tty.c >T> >T> If you are using at least one of them, then I'm asking you to test the >T> patch and respond. Thanks in advance! >T> >T> P.S. Sorry for crossposting. The target users are both RELENG_5 and CURRENT. > > > From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 23:26:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B725C16A4CE for ; Tue, 7 Dec 2004 23:26:35 +0000 (GMT) Received: from hq.sectorb.msk.ru (petaflop.b.gz.ru [217.67.124.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4ED3943D67 for ; Tue, 7 Dec 2004 23:26:31 +0000 (GMT) (envelope-from chinhngt@sectorb.msk.ru) Received: from unix.local (unix.local [172.16.12.120]) by hq.sectorb.msk.ru (Postfix) with ESMTP id 09A444106 for ; Wed, 8 Dec 2004 02:26:29 +0300 (MSK) Date: Wed, 8 Dec 2004 02:26:30 +0300 (MSK) From: Nguyen Tam Chinh X-X-Sender: chinhngt@unix.local To: current@freebsd.org Message-ID: <20041208020510.W39053@unix.local> Keywords: 216091683 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: [READ_DMA again] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 23:26:35 -0000 Hi all, I know that there're many discussions about this, but I still want to take a note more here. I've just cvsup and update world and kernel this afternoon. ---------------- %uname -a FreeBSD unix.hackers 6.0-CURRENT FreeBSD 6.0-CURRENT #8: Tue Dec 7 22:07:14 MSK 2004 ---------------- On the FreeBSD beta-6 and 5.3-REL the problems of READ_DMA, WRITE_DMA very often occured and many times they made the system hang! The 5.2.1 also met the "*_DMA" problem, but I'm sure all is okay, my computer still worked. Then I decided to go on to 6.0-CURRENT, with the hope that someone will fix this problem. And as you see, it is not better. After producing some messages like: ------------ Dec 8 00:29:39 unix kernel: ad2: TIMEOUT - READ_DMA retrying (2 retries left) LBA=163544546 Dec 8 00:29:39 unix kernel: ad2: FAILURE - READ_DMA timed out Dec 8 00:29:39 unix kernel: g_vfs_done():ad2s3[READ(offset=20811415552, length=16384)]error = 5 ------------ the computer hanged immediately. Just that. Using atacontrol to turn the chanel to PIO4, for example, didn't help, errors like "READ_???" or "WRITE_???" still there, and the system will hang again. What can be the problem here? May be it is because i put an ATA-133 HDD in an old ATA66 only computer? dmesg here: ----------------------------------------------------------------------- %dmesg Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-CURRENT #8: Tue Dec 7 22:07:14 MSK 2004 root@unix.hackers:/mnt/unix/Temp/obj/usr/src/sys/kernel Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Celeron (730.97-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383fbff real memory = 267386880 (255 MB) avail memory = 256503808 (244 MB) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: pcibus 0 on motherboard pir0: on motherboard pci0: on pcib0 agp0: mem 0x40300000-0x4037ffff,0x44000000-0x47ffffff irq 9 at device 2.0 on pci0 pcib1: at device 30.0 on pci0 pci2: on pcib1 rl0: port 0x1000-0x10ff mem 0x40000000-0x400000ff irq 5 at device 9.0 on pci2 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:10:b5:eb:df:f7 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x2460-0x246f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 31.2 (no driver attached) pci0: at device 31.5 (no driver attached) cpu0 on motherboard orm0: at iomem 0xe0000-0xeffff,0xc0000-0xc7fff on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (port) unknown: can't assign resources (port) Timecounter "TSC" frequency 730967047 Hz quality 800 Timecounters tick every 1.000 msec ipfw2 initialized, divert loadable, rule-based forwarding disabled, default to accept, logging disabled ad0: 9541MB [19386/16/63] at ata0-master UDMA66 ad2: 117246MB [238216/16/63] at ata1-master UDMA66 kern_symlink = 0 Trying to mount root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted ----- With best regards, | The Power to Serve Nguyen Tam Chinh | http://www.FreeBSD.org Loc: sp.cs.msu.ru | http://chinhngt.svmgu.com | http://www.gnu.org/copyleft/copyleft.html From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 01:47:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 50F4916A4CE for ; Wed, 8 Dec 2004 01:47:56 +0000 (GMT) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 5278343D60 for ; Wed, 8 Dec 2004 01:47:55 +0000 (GMT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 8 Dec 2004 01:47:54 +0000 (GMT) To: Garance A Drosihn In-Reply-To: Your message of "Mon, 06 Dec 2004 19:51:56 EST." Date: Wed, 08 Dec 2004 01:47:53 +0000 From: Ian Dowse Message-ID: <200412080147.aa24331@salmon.maths.tcd.ie> cc: freebsd-current@freebsd.org cc: =?iso-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: Another twist on WRITE_DMA issues <- ProblemFound X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 01:47:56 -0000 In message , Garance A Drosihn writes: >That isn't it either. I think the hardware is just mocking me. I >had zero problems for more than 24 hours. I then copied one set of >partitions to another, booted up to that second set, and immediately >I was back to having the above warnings/errors, and before long I >had a system panic. And when I try to 'call doadump()', that fails >with an error writing to the disk, so I can't get a core dump of it >either. If you don't mind the risk of triggering some asserts, you could try the patches in http://people.freebsd.org/~iedowse/callout/ to see if they make any difference. The aim of callout.diff is to provide callouts with race-free semantics, and then callout_ata.diff is an attempt to fix some timeout race conditions in the ATA driver using the new API. The patches seem to have fixed the ATA timeout messages I was getting after suspend/resume events, but it's a bit early to tell for sure as I've only been using them on my laptop now for a few days. Depending on what drivers you use (especially ethernet), you may get panics with those patches. This is because the patched callout code requires that Giant is held while stopping and starting non-mpsafe timers. It is safe to #if 0 out the new mtx_assert conditions in kern_timeout.c for now as a workaround. Ian From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 02:23:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E24416A4CE for ; Wed, 8 Dec 2004 02:23:46 +0000 (GMT) Received: from onix.netpar.com.br (onix.netpar.com.br [200.103.225.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93F7343D75 for ; Wed, 8 Dec 2004 02:23:45 +0000 (GMT) (envelope-from cbraga@smsweb.com.br) Received: from [200.103.254.184] (unverified [200.103.254.184]) by onix.netpar.com.br for ; Wed, 8 Dec 2004 00:29:17 -0200 Message-ID: <41B665AF.7060509@smsweb.com.br> Date: Wed, 08 Dec 2004 00:23:43 -0200 From: =?ISO-8859-1?Q?Crist=F3v=E3o_Dalla_Costa?= User-Agent: Mozilla Thunderbird 1.0RC1 (Windows/20041201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: installing 5.3 on Promise FastTrack 378 and Intel raid controllers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 02:23:46 -0000 Hello We got a new P4 server today with an Asus PC-DL deluxe motherboard w/ Intel 875P chipset which we were disappointed to find sucks with respect to the RAID controllers. We managed to boot the FreeBSD installation using floppies, and when we get to the partitioning screen we are shown 5 disks, while we actually only have four (4 serial ata 120 GB drives). We configured two in raid-1 and two in raid-0 in each of the raid controllers, and all disks that appear in the setup are 120 GB while we were expecting to find a 240 GB one corresponding to the raid-0 setup. We already found out the so-called raid controllers are fakes which require the operating system to do the work, what I'd like to know is if there's a way to install and boot FreeBSD in raid mode or if I'll have to just install it normally and use vinum, or even throw this junk MB out the window and get a new one, or a separate raid controller. I've found a couple other messages on the list archive mentioning this controller so I thought someone mught have a few pointers. Thanks in advance, Cristóvão Dalla Costa From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 03:53:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58AF216A4CE for ; Wed, 8 Dec 2004 03:53:36 +0000 (GMT) Received: from omoikane.mb.skyweb.ca (omoikane.mb.skyweb.ca [64.42.246.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA8BA43D41 for ; Wed, 8 Dec 2004 03:53:35 +0000 (GMT) (envelope-from mark@skyweb.ca) Received: by omoikane.mb.skyweb.ca (Postfix, from userid 1001) id 35F6161D75; Tue, 7 Dec 2004 21:53:33 -0600 (CST) From: Mark Johnston To: current@freebsd.org, freebsd-cvs-summary@lists.enderunix.org Date: Tue, 7 Dec 2004 21:53:33 -0600 User-Agent: KMail/1.6.1 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200412072153.33561.mjohnston@skyweb.ca> Subject: cvs-src summary for November 29 - December 6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 03:53:36 -0000 Sorry for the lateness of this summary; my spare time has been occupied dealing with an insidious trojan distributed by www.nisamerica.com. :) FreeBSD cvs-src summary for 29/11/04 to 06/12/04 ++++++++++++++++++++++++++++++++++++++++++++++++ This is a regular weekly summary of FreeBSD's cutting-edge development. It is intended to help the FreeBSD community keep up with the fast-paced work going on in FreeBSD-CURRENT by distilling the deluge of data from the CVS mailing list into a (hopefully) easy-to-read newsletter. This newsletter is marked up in reStructuredText_, so any odd punctuation that you see is likely intended for the reST parser. .. _reStructuredText: http://docutils.sourceforge.net/rst.html You can get old summaries, and an HTML version of this one, at http://www.xl0.org/FreeBSD/. Please send any comments to Mark Johnston (mark at xl0.org). For Lukasz Dudek and Szymon Roczniak's Polish translations of these summaries, which may lag the English ones slightly, please see http://mocart.pinco.pl/FreeBSD/. .. contents:: ============ New features ============ ACPI-CA 20041119 imported ------------------------- Mark Santcroos (marks) imported release 20041119 of Intel ACPI-CA, the Advanced Configuration and Power Interface support code. ACPI supports power management and PCI configuration features, and is especially important on laptops. This new version should help general stability and compatibility. http://www.freebsd.org/cgi/mid.cgi?200412012314.iB1NECQl023863 PCI Express configuration mechanism supported --------------------------------------------- Scott Long (scottl) added support for the PCI Express configuration mechanism, allowing the system to configure and better support PCIe cards. Currently, the driver supports only Intel's Grantsdale and Lindenhurst (925 and 752x) chipsets. http://www.freebsd.org/cgi/mid.cgi?200412060827.iB68RAmE058040 =================== Important bug fixes =================== Security fix in procfs ---------------------- Colin Percival (cperciva) fixed a bug in the procfs code that allowed local users to cause system panics or read arbitrary parts of kernel memory. FreeBSD 4.x is vulnerable if procfs is mounted, and 5.x is vulnerable if either procfs or linprocfs (the Linux-emulation procfs) is mounted. 4.x mounts procfs by default, but 5.x does not mount either procfs or linprocfs. Colin also committed the fix to 5-STABLE, 4-STABLE, 5.3, 5.2, 4.10, and 4.8. Note that 4.8 was patched, but not 4.9; this is because 4.8 is in an extended support phase. The security advisory `FreeBSD-SA-04:17.procfs`_ deals with this vulnerability. The bug was reported by Bryan Fulton and Ted Unangst, with help from Coverity, Inc.'s SWAT analysis tool. .. _`FreeBSD-SA-04:17.procfs`: ftp://ftp.freebsd.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-04:17.procfs.asc http://www.freebsd.org/cgi/mid.cgi?200412012133.iB1LX2JC019417 Several NFS fixes ----------------- Paul Saab (ps) committed a number of bug fixes to the NFS (Network Filesystem) code. The bugs included negative values being returned by df, a deadlock when exclusive locks were enabled, and a consistency problem in applications using mmap. All three bug fixes were submitted by Mohan Srinivasan of Yahoo. http://www.freebsd.org/cgi/mid.cgi?200412010642.iB16gLHF059505 http://www.freebsd.org/cgi/mid.cgi?200412010648.iB16msH9059728 http://www.freebsd.org/cgi/mid.cgi?200412010651.iB16p79s059890 =============== Other bug fixes =============== Maxim Konovalov (maxim) committed a fix to a bug in sh that could cause an infinite loop. The bug was analyzed by demon, and the fix was submitted by tegge. This closes `PR 66242`_. .. _`PR 66242`: http://www.freebsd.org/cgi/query-pr.cgi?pr=66242 http://www.freebsd.org/cgi/mid.cgi?200412021312.iB2DChsd078387 Scott Long (scottl) made major changes to the amr driver for Adaptec MegaRAID cards (also found as HP and Dell-branded adapters) to allow it to work properly with more than 4 GB of memory. http://www.freebsd.org/cgi/mid.cgi?200412052348.iB5NmILF025647 Xin LI (delphij) committed a fix to the PPP support code that caused problems when using CBCP, a callback negotiation protocol. http://www.freebsd.org/cgi/mid.cgi?200412061549.iB6FnqhN086863 From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 04:21:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 175D216A4CE for ; Wed, 8 Dec 2004 04:21:27 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1460643D67 for ; Wed, 8 Dec 2004 04:21:26 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from [192.168.4.250] (dhcp50.pn.xcllnt.net [192.168.4.250]) by ns1.xcllnt.net (8.13.1/8.13.1) with ESMTP id iB84LOZq002689 for ; Tue, 7 Dec 2004 20:21:25 -0800 (PST) (envelope-from marcel@xcllnt.net) Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: <9EF07AD4-48D0-11D9-BD23-000D93C47836@xcllnt.net> Content-Type: text/plain; charset=US-ASCII; format=flowed To: current@freebsd.org From: Marcel Moolenaar Date: Tue, 7 Dec 2004 20:21:24 -0800 X-Mailer: Apple Mail (2.619) Subject: msdosfs borked X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 04:21:27 -0000 Permissions seems to have gone out to lunch... pluto2# mount | grep efi /dev/da0p1 on /efi (msdosfs, local) pluto2# ls -alR /efi total 22 d--------- 1 root wheel 16384 Jan 1 1980 . drwxr-xr-x 21 root wheel 512 Dec 8 04:06 .. d--------- 1 root wheel 4096 Jan 30 2003 boot /efi/boot: total 1668 d--------- 1 root wheel 4096 Jan 30 2003 . d--------- 1 root wheel 16384 Jan 1 1980 .. d--------- 1 root wheel 4096 Jul 18 22:14 backup d--------- 1 root wheel 4096 Jan 30 2003 defaults ---------- 1 root wheel 110 Nov 20 20:29 device.hints d--------- 1 root wheel 4096 Dec 8 04:05 kernel d--------- 1 root wheel 4096 Dec 6 05:23 kernel.old ---------- 1 root wheel 7772 Dec 6 05:27 loader.4th ---------- 1 root wheel 96 Jan 31 2004 loader.conf ---------- 1 root wheel 542608 Dec 6 05:27 loader.efi ---------- 1 root wheel 12465 Dec 6 05:27 loader.help ---------- 1 root wheel 365 Jul 25 2002 loader.rc d--------- 1 root wheel 4096 Jan 30 2003 modules ---------- 1 root wheel 1031168 Dec 6 05:27 skiload ---------- 1 root wheel 12465 Dec 6 05:27 skiload.help ---------- 1 root wheel 36440 Dec 6 05:27 support.4th ...and so on... This is with an up-to-date kernel: FreeBSD 6.0-CURRENT #1: Wed Dec 8 04:05:20 UTC 2004 marcel@pluto2.freebsd.org:/q/obj/q/6.x/src/sys/PLUTO2 A kernel dated december 6th, doesn't have this problem. -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 04:51:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69EE416A4CE for ; Wed, 8 Dec 2004 04:51:01 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id E272643D55 for ; Wed, 8 Dec 2004 04:51:00 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) iB84owf1002270; Tue, 7 Dec 2004 23:50:58 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)iB84owCc002267; Tue, 7 Dec 2004 23:50:58 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Tue, 7 Dec 2004 23:50:58 -0500 (EST) From: Andre Guibert de Bruet To: Poul-Henning Kamp In-Reply-To: <91247.1102371834@critter.freebsd.dk> Message-ID: <20041207234332.Q637@alpha.siliconlandmark.com> References: <91247.1102371834@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: freebsd-current@freebsd.org Subject: Re: dump broken with new kernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 04:51:01 -0000 On Mon, 6 Dec 2004, Poul-Henning Kamp wrote: > In message <6.2.0.14.2.20041206134829.08ad2d00@pozo.com>, Manfred Antar writes: > >> This seems to be when the change was made: >> cvs co -D"December 3, 2004 20:00 UTC" sys -- dump broken >> >> cvs co -D"December 3, 2004 18:00 UTC" sys -- dump works >> >> The suspect files seem to be: >> sys/kern/vfs_mount.c >> $FreeBSD: src/sys/kern/vfs_mount.c,v 1.156 2004/12/03 19:25:44 phk Exp >> >> sys/sys/mount.h >> $FreeBSD: src/sys/sys/mount.h,v 1.180 2004/12/03 19:33:19 phk Exp $ >> >> I know phk has been working on the mount stuff. > > It seems I've broken snapshots and I think I've found out how/why. > > sbin/mount_ufs.c mounts using the filesystem "ufs". > > mksnap_ffs uses filesystem name "ffs". > > I think the problem is that previously a MNT_UPDATE would not > actually check the filesystem name provided once it got hold > of the mountpoint[1] and I start out looking for the filesystem > type first. > > The problem is compounded by the fact that "ufs" is the wrong name, > the correct name is "ffs"[2]. > > I tried to make the name "ffs" and make "ufs" an alias for it, but > it blows up all over the place. > > So against my better judgement I have just committed code to the > kernel to accept "ffs" as an alias for "ufs" when it comes to > filesystems. I'm far from sure that is all there is to it, but > it seems to let dumps work for me again. I am still running into dump problems on my system. I'm using: $FreeBSD: src/sys/kern/vfs_mount.c,v 1.168 2004/12/07 08:15:40 phk Exp $ $FreeBSD: src/sys/sys/mount.h,v 1.187 2004/12/07 08:15:40 phk Exp $ FreeBSD bling.home 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Tue Dec 7 23:02:43 EST 2004 root@bling.home:/usr/CURRENT/sys/i386/compile/BLING i386 # /sbin/dump -0uaLf "/mnt/backups/`hostname -s`-`utime`-amrd0a.dump" /mnt/amrd0a mksnap_ffs: Cannot create /mnt/amrd0a/.snap/dump_snapshot: Bad address dump: Cannot create /mnt/amrd0a/.snap/dump_snapshot: No such file or directory Thanks, Andy | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ > From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 04:54:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D86F16A4CE for ; Wed, 8 Dec 2004 04:54:21 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA1D943D55 for ; Wed, 8 Dec 2004 04:54:20 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) iB84sH3L002292; Tue, 7 Dec 2004 23:54:17 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)iB84sCxY002289; Tue, 7 Dec 2004 23:54:17 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Tue, 7 Dec 2004 23:54:12 -0500 (EST) From: Andre Guibert de Bruet To: Manfred Antar In-Reply-To: <6.2.0.14.2.20041206114020.08851e60@pozo.com> Message-ID: <20041207235104.K637@alpha.siliconlandmark.com> References: <6.2.0.14.2.20041206075313.03e74db8@pozo.com> <6.2.0.14.2.20041206114020.08851e60@pozo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: freebsd-current@freebsd.org Subject: Accounting resumed, Accounting suspended repeatedly (Was: Re: dump broken with new kernel) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 04:54:21 -0000 On Mon, 6 Dec 2004, Manfred Antar wrote: > I'm also seeing alot of : > Dec 6 10:06:53 pozo kernel: Accounting resumed > Dec 6 10:07:23 pozo kernel: Accounting suspended > Dec 6 10:07:38 pozo kernel: Accounting resumed > Dec 6 10:12:23 pozo kernel: Accounting suspended > Dec 6 10:12:38 pozo kernel: Accounting resumed > Dec 6 10:12:53 pozo kernel: Accounting suspended Ditto. Running accton all by itself to turn off accounting stops these cycles from occuring (Hardly a fix as you end up without logs to run reports from). Andy | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ > From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 05:06:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1174916A4CE for ; Wed, 8 Dec 2004 05:06:22 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEC7843D1D for ; Wed, 8 Dec 2004 05:06:21 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iB856LRo007589; Tue, 7 Dec 2004 23:06:21 -0600 (CST) (envelope-from dan) Date: Tue, 7 Dec 2004 23:06:20 -0600 From: Dan Nelson To: Andre Guibert de Bruet Message-ID: <20041208050620.GG2629@dan.emsphone.com> References: <6.2.0.14.2.20041206075313.03e74db8@pozo.com> <6.2.0.14.2.20041206114020.08851e60@pozo.com> <20041207235104.K637@alpha.siliconlandmark.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041207235104.K637@alpha.siliconlandmark.com> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: Accounting resumed, Accounting suspended repeatedly (Was: Re: dump broken with new kernel) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 05:06:22 -0000 In the last episode (Dec 07), Andre Guibert de Bruet said: > On Mon, 6 Dec 2004, Manfred Antar wrote: > > >I'm also seeing alot of : > >Dec 6 10:06:53 pozo kernel: Accounting resumed > >Dec 6 10:07:23 pozo kernel: Accounting suspended > >Dec 6 10:07:38 pozo kernel: Accounting resumed > >Dec 6 10:12:23 pozo kernel: Accounting suspended > >Dec 6 10:12:38 pozo kernel: Accounting resumed > >Dec 6 10:12:53 pozo kernel: Accounting suspended > > Ditto. Running accton all by itself to turn off accounting stops > these cycles from occuring (Hardly a fix as you end up without logs > to run reports from). It's a safety device that prevents accounting records from filling up your hard drive in the event of forkbombs, configure scripts or other things that cause high process turnover. It's controlled by the following sysctls: kern.acct_chkfreq: frequency for checking the free space (seconds) kern.acct_resume: percentage of free disk space above which accounting resumes kern.acct_suspend: percentage of free disk space below which accounting stops -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 05:15:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDC8916A4CE for ; Wed, 8 Dec 2004 05:15:10 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72D0743D39 for ; Wed, 8 Dec 2004 05:15:10 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) iB85F5mL002416; Wed, 8 Dec 2004 00:15:05 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)iB85F52h002413; Wed, 8 Dec 2004 00:15:05 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Wed, 8 Dec 2004 00:15:05 -0500 (EST) From: Andre Guibert de Bruet To: Dan Nelson In-Reply-To: <20041208050620.GG2629@dan.emsphone.com> Message-ID: <20041208000849.D637@alpha.siliconlandmark.com> References: <6.2.0.14.2.20041206075313.03e74db8@pozo.com> <20041207235104.K637@alpha.siliconlandmark.com> <20041208050620.GG2629@dan.emsphone.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: freebsd-current@freebsd.org Subject: Re: Accounting resumed, Accounting suspended repeatedly (Was: Re: dump broken with new kernel) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 05:15:11 -0000 On Tue, 7 Dec 2004, Dan Nelson wrote: > In the last episode (Dec 07), Andre Guibert de Bruet said: >> On Mon, 6 Dec 2004, Manfred Antar wrote: >> >>> I'm also seeing alot of : >>> Dec 6 10:06:53 pozo kernel: Accounting resumed >>> Dec 6 10:07:23 pozo kernel: Accounting suspended >>> Dec 6 10:07:38 pozo kernel: Accounting resumed >>> Dec 6 10:12:23 pozo kernel: Accounting suspended >>> Dec 6 10:12:38 pozo kernel: Accounting resumed >>> Dec 6 10:12:53 pozo kernel: Accounting suspended >> >> Ditto. Running accton all by itself to turn off accounting stops >> these cycles from occuring (Hardly a fix as you end up without logs >> to run reports from). > > It's a safety device that prevents accounting records from filling up > your hard drive in the event of forkbombs, configure scripts or other > things that cause high process turnover. It's controlled by the > following sysctls: > > kern.acct_chkfreq: frequency for checking the free space (seconds) > kern.acct_resume: percentage of free disk space above which accounting resumes > kern.acct_suspend: percentage of free disk space below which accounting stops Noted. I am at a loss to see which of my filesystem it believes is running out of space. /var, the logical choice is not even at 10%: bling# df -h Filesystem Size Used Avail Capacity Mounted on /dev/ad4s1a 248M 125M 103M 55% / devfs 1.0K 1.0K 0B 100% /dev procfs 4.0K 4.0K 0B 100% /proc /dev/ad4s1d 248M 14K 228M 0% /tmp /dev/ad4s1e 3.9G 307M 3.3G 8% /var /dev/ad4s1f 180G 6.1G 159G 4% /usr /dev/ad6s1d 180G 20G 145G 12% /mnt/misc /dev/amrd0a 265G 42G 202G 17% /mnt/amrd0a /dev/ad0 226G 111G 97G 53% /mnt/backups devfs 1.0K 1.0K 0B 100% /var/named/dev Thanks! Andy | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ > From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 05:20:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECBC516A4CE for ; Wed, 8 Dec 2004 05:20:54 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id A63FB43D5F for ; Wed, 8 Dec 2004 05:20:54 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) iB85KpkN002462; Wed, 8 Dec 2004 00:20:51 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)iB85KhZj002459; Wed, 8 Dec 2004 00:20:51 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Wed, 8 Dec 2004 00:20:43 -0500 (EST) From: Andre Guibert de Bruet To: Mark Johnston In-Reply-To: <200412072153.33561.mjohnston@skyweb.ca> Message-ID: <20041208001739.M637@alpha.siliconlandmark.com> References: <200412072153.33561.mjohnston@skyweb.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: current@freebsd.org Subject: Re: cvs-src summary for November 29 - December 6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 05:20:55 -0000 On Tue, 7 Dec 2004, Mark Johnston wrote: > Scott Long (scottl) made major changes to the amr driver for Adaptec > MegaRAID cards (also found as HP and Dell-branded adapters) to allow it to > work properly with more than 4 GB of memory. > > http://www.freebsd.org/cgi/mid.cgi?200412052348.iB5NmILF025647 Sorry for being pedantic, but amr(4) supports the LSI Logic MegaRAID line of cards (Not Adaptec). I never miss your summaries, they're awesome! Keep up the good work! Regards, Andy | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ > From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 05:36:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F163816A4CE for ; Wed, 8 Dec 2004 05:36:23 +0000 (GMT) Received: from pozo.com (pozo.com [216.101.162.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A89143D62 for ; Wed, 8 Dec 2004 05:36:22 +0000 (GMT) (envelope-from null@pozo.com) Received: from sunpci.pozo.com (sunpci.pozo.com [192.168.0.29]) (authenticated bits=0) by pozo.com (8.13.1/8.13.1) with ESMTP id iB85a76V092829 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 7 Dec 2004 21:36:07 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <6.2.0.14.2.20041207213333.03eb7298@pozo.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Tue, 07 Dec 2004 21:36:07 -0800 To: Andre Guibert de Bruet , Dan Nelson From: Manfred Antar In-Reply-To: <20041208000849.D637@alpha.siliconlandmark.com> References: <6.2.0.14.2.20041206075313.03e74db8@pozo.com> <20041207235104.K637@alpha.siliconlandmark.com> <20041208050620.GG2629@dan.emsphone.com> <20041208000849.D637@alpha.siliconlandmark.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" cc: freebsd-current@freebsd.org Subject: Re: Accounting resumed, Accounting suspended repeatedly (Was: Re: dump broken with new kernel) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 05:36:24 -0000 At 09:15 PM 12/7/2004, Andre Guibert de Bruet wrote: >On Tue, 7 Dec 2004, Dan Nelson wrote: > >>In the last episode (Dec 07), Andre Guibert de Bruet said: >>>On Mon, 6 Dec 2004, Manfred Antar wrote: >>> >>>>I'm also seeing alot of : >>>>Dec 6 10:06:53 pozo kernel: Accounting resumed >>>>Dec 6 10:07:23 pozo kernel: Accounting suspended >>>>Dec 6 10:07:38 pozo kernel: Accounting resumed >>>>Dec 6 10:12:23 pozo kernel: Accounting suspended >>>>Dec 6 10:12:38 pozo kernel: Accounting resumed >>>>Dec 6 10:12:53 pozo kernel: Accounting suspended >>> >>>Ditto. Running accton all by itself to turn off accounting stops >>>these cycles from occuring (Hardly a fix as you end up without logs >>>to run reports from). >> >>It's a safety device that prevents accounting records from filling up >>your hard drive in the event of forkbombs, configure scripts or other >>things that cause high process turnover. It's controlled by the >>following sysctls: >> >>kern.acct_chkfreq: frequency for checking the free space (seconds) >>kern.acct_resume: percentage of free disk space above which accounting resumes >>kern.acct_suspend: percentage of free disk space below which accounting stops > >Noted. I am at a loss to see which of my filesystem it believes is running out of space. /var, the logical choice is not even at 10%: > >bling# df -h >Filesystem Size Used Avail Capacity Mounted on >/dev/ad4s1a 248M 125M 103M 55% / >devfs 1.0K 1.0K 0B 100% /dev >procfs 4.0K 4.0K 0B 100% /proc >/dev/ad4s1d 248M 14K 228M 0% /tmp >/dev/ad4s1e 3.9G 307M 3.3G 8% /var >/dev/ad4s1f 180G 6.1G 159G 4% /usr >/dev/ad6s1d 180G 20G 145G 12% /mnt/misc >/dev/amrd0a 265G 42G 202G 17% /mnt/amrd0a >/dev/ad0 226G 111G 97G 53% /mnt/backups >devfs 1.0K 1.0K 0B 100% /var/named/dev > >Thanks! >Andy Same here I have over 19Gigs of free space. It's something else a kernel from last Friday does not do this. ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 06:48:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0253716A4CE for ; Wed, 8 Dec 2004 06:48:43 +0000 (GMT) Received: from smtpauth.kewlio.net (smtpauth.kewlio.net [195.22.134.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FFD643D1D for ; Wed, 8 Dec 2004 06:48:42 +0000 (GMT) (envelope-from tlp@LiquidX.org) Received: from maya.liquidx.org (70-56-157-27.bois.qwest.net [70.56.157.27]) (authenticated bits=0) by smtpauth.kewlio.net (8.12.10/8.12.10) with ESMTP id iB86mc90037137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 8 Dec 2004 06:48:40 GMT Date: Tue, 7 Dec 2004 23:48:40 -0700 From: Travis Poppe To: freebsd-current@freebsd.org Message-ID: <20041207234840.7287cdf4@maya.liquidx.org> X-Mailer: Sylpheed-Claws 0.9.12b (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: FreeBSD sound distortion problems with SB Live! fixed with PREEMPTION X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 06:48:43 -0000 Hello all, Back in October, I contacted the list and described a problem I was having with FreeBSD 5.X (now 5.3-RELEASE) and sound. I will reiterate the problem one more time for those of you who did not follow the posts. I was using FreeBSD 5.3-BETA7 at the time (as far as I know, all of 5.x has this problem) and have an SB Live! 5.1 which uses the emu10k1 driver. I've been told that this problem may be specific to my driver (and possibly others). The problem: When playing music with XMMS after my box had been up for at least a day or two, I'd hear these "random" skips and sound distortions that can be described as the sound being slowed down for 1/4th of a second and then back to normal again (a "lagged sound" skip). A much more severe version of this can easily be reproduced by extracting the firefox source code from bz2 while playing music and can be witnessed for as long as it takes to extract the archive. Note that these are not just "skips" but complete sound distortion as well. If you hear very minor brief skips when running this test but no distortion, you are not witnessing the same problem. In the previous posts to -CURRENT, I was advised to increase the sound buffer which did HELP, but the problem was still there. Increasing the buffer also caused de-synced sound in games. This was not a good workaround. Anyway, today I was playing around with a few patches derived from DragonFly that make it possible to use high resolution VESA modes with syscons. I was using a 1024x768 VESA text console when I noticed that if a lot of text were to be scrolled on the screen at once, I'd hear the same sound problem described above. Frustrated, I began conversation on IRC and described my problem. A friend of mine suggested something no one else had before, and that suggestion was to enable PREEMPTION in the kernel. A GNU/Linux user in another channel also said this to me: "Sounds like FreeBSD needs a preemptable kernel." So, I decided to give it a try. To my amazement, it worked completely. Enabling PREEMPTION in the kernel completely "fixes" this problem to the fullest extent. I have not been able to reproduce the problem since using any of the methods described above. I'm hoping that with this new information someone might be able to figure out what is truly causing this problem and can come up with a solution (or is PREEMPTION a good solution?). It seems that only a handful of drivers (emu10k1 is the one I'm having problems with) have this problem. For the record, I am not the only one who has reported this problem to the lists. Thanks all, -Travis Poppe P.S. I was unsure whether or not this was best suited for freebsd-current or freebsd-stable. My apologized if I posted to the wrong list. From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 07:10:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C2AA516A4CE for ; Wed, 8 Dec 2004 07:10:49 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id E967743D49 for ; Wed, 8 Dec 2004 07:10:47 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iB879hZg009224 for ; Wed, 8 Dec 2004 17:39:43 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Wed, 8 Dec 2004 17:40:38 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iB874kQ12762 for ; Wed, 8 Dec 2004 17:34:46 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id YK36JP2C; Wed, 8 Dec 2004 17:34:33 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iB874sDF011271 ; Wed, 8 Dec 2004 17:34:54 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iB874s47011270; Wed, 8 Dec 2004 17:34:54 +1030 (CST) (envelope-from wilkinsa) Date: Wed, 8 Dec 2004 17:34:54 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20041208070454.GA11139@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org, matthew.thyer@dsto.defence.gov.au Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline User-Agent: Mutt/1.5.6i cc: matthew.thyer@dsto.defence.gov.au Subject: panic: process 839(xmms):1 holds process lock but isn't blocked ona lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 07:10:50 -0000 Hi all, I got this panic today on a: FreeBSD 5.3-STABLE #13: Mon Nov 29 09:49:10 CST 2004 This panic is reproduceable via two methods: 1. # kldload snd_ich 2. add snd_ich_load="YES" to /boot/loader.conf; reboot; # kldunload snd_ich I have a kernel with debugging symbols and a vmcore if anyone is interested. db> trace kdb_enter(c068735f,c06df360,c068a355,e3744c64,c266c320) at kdb_enter+0x32 panic(c068a355,347,c3020698,1,c0686981) at panic+0x14b turnstile_wait(c2ef6600,c06ddec0,c3021e10,220,c06ddec0) at turnstile_wait+0x5ec _mtx_lock_sleep(c06ddec0,c266c320,0,c0684ceb,222) at _mtx_lock_sleep+0xb0 _mtx_lock_flags(c06ddec0,0,c0684ceb,222,0) at _mtx_lock_flags+0xaf ithread_loop(c2661480,e3744d48,c0684acc,323,c2661480) at ithread_loop+0x1ea fork_exit(c04de759,c2661480,e3744d48) at fork_exit+0xa6 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe3744d7c, ebp = 0 --- db> show pcpu cpuid = 0 curthread = 0xc266c320: pid 28 "irq18: uhci2 bt0++" curpcb = 0xe3744da0 fpcurthread = none idlethread = 0xc26644b0: pid 11 "idle" APIC ID = 0 currentldt = 0x28 spin locks held: db> show lockedvnods Locked vnodes db> (850)-08.12.2004 hostname-{17:26}-[/var/crash]->sudo kldunload snd_ich Password: lock order reversal 1st 0xc2781a40 pcm0 (sound cdev) @ /usr/src/sys/modules/sound/sound/../../../dev/sound/pcm/sound.c:706 2nd 0xc07c6a20 sndstat (sndstat) @ /usr/src/sys/modules/sound/sound/../../../dev/sound/pcm/sndstat.c:257 KDB: stack backtrace: witness_checkorder(c07c6a20,9,c07c1a3d,101,0) at witness_checkorder+0x5fa _sx_xlock(c07c6a20,c07c1a3d,101,0,c2738e00) at _sx_xlock+0x5c sndstat_unregister(c2753800,8,c07c1b35,2c2,c2753800) at sndstat_unregister+0x27 pcm_unregister(c2753800,c06a5f7c,c2753800,e75e2bfc,c2753800) at pcm_unregister+0x1f5 ich_pci_detach(c2753800,c26fd850,c06a5f7c,c07a88f1,3) at ich_pci_detach+0x13 device_detach(c2753800,c07a8909,c26e2000,1,c26aed80) at device_detach+0x6b From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 08:36:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEF1D16A4CE for ; Wed, 8 Dec 2004 08:36:48 +0000 (GMT) Received: from frodo.anembo.nu.org (dsl-202-173-130-73.nsw.westnet.com.au [202.173.130.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5ED4343D41 for ; Wed, 8 Dec 2004 08:36:47 +0000 (GMT) (envelope-from christopher@nu.org) Received: from elrond.anembo.nu.org (elrond.anembo.nu.org [10.5.1.3]) by frodo.anembo.nu.org (8.13.1/8.13.1) with SMTP id iB88ai2T028139; Wed, 8 Dec 2004 19:36:45 +1100 (EST) Received: by elrond.anembo.nu.org (sSMTP sendmail emulation); Wed, 8 Dec 2004 19:36:44 +1100 Date: Wed, 8 Dec 2004 19:36:44 +1100 From: Christopher Vance To: Garance A Drosihn Message-ID: <20041208083644.GA12015@nu.org> References: <200410081937.15068.miha@ghuug.org> <200410291044.34973.soralx@cydem.org> <200410291657.33606.miha@ghuug.org> <20041030004556.B13046@unix.local> <4182BD51.6070800@freebsdbrasil.com.br> <20041207044734.GA7994@nu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: cc: freebsd-current@freebsd.org Subject: Re: ad0: FAILURE - WRITE_DMA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 08:36:48 -0000 On Tue, Dec 07, 2004 at 01:38:32AM -0500, Garance A Drosihn wrote: >About all I can do is guess at some possible problems. What is the >capacity of the Seagate drive that you're having trouble with? Are >you using vinum or gvinum on it? Is your machine set up with a serial >console? If the machine panics, can you get a core-dump of it, or do >you just get a disk error when it tries to write the dump to disk? My disks are 200MB, but I am/was only booting with one at a time. No *vinum or anything fancy. FreeBSD with UFS2 is on one disk, OpenBSD on the other. Both occupy their whole disk. At least one incident was a freeze, where it might have been trying to panic, but didn't shutdown. With the real panics, there were several kinds, with different messages which I can no longer remember. Gigabyte 7N400Pro2 AMD Barton 2600+ 0.5GB memory SiI 3512A disk controlled 2 x 200MB Seagate 7200.7 SATA disks (1 in use) re0 GigE onboard onboard AC97 Audio not used Radeon 9200SE currently in text mode no floppy - I forgot to order one I'm not running FreeBSD on this machine any more, so there won't be anything to make a FreeBSD coredump from. I'm not even going to try again unless someone convinces me that it's fixed and available on installation media. Maybe 5.4 if I still care enough to keep my CD subscription alive. I'll keep 5.3 on the disk it's on until I need the space, though, so it could be updated if there's reason later. I only got it to 5.3 by installing 5.2 from CD onto a different machine, cvsup'ing to 5.3-R and compiling that before moving the disk to this machine. The OpenBSD message I get occasionally (less frequently than the FreeBSD WRITE_DMA failure) is "aborted command, interface CRC error writing fsbn [...]". My understanding is that the SiI 3*1* stuff just sux, but it's a new motherboard, and I did get what I ordered, so I'd feel funny trying to replace it just now. -- Christopher Vance From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 08:48:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C07D16A4CE for ; Wed, 8 Dec 2004 08:48:13 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id E74C143D60 for ; Wed, 8 Dec 2004 08:48:12 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB88mBkP020122; Wed, 8 Dec 2004 09:48:11 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Marcel Moolenaar From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 07 Dec 2004 20:21:24 PST." <9EF07AD4-48D0-11D9-BD23-000D93C47836@xcllnt.net> Date: Wed, 08 Dec 2004 09:48:11 +0100 Message-ID: <20121.1102495691@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@freebsd.org Subject: Re: msdosfs borked X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 08:48:13 -0000 In message <9EF07AD4-48D0-11D9-BD23-000D93C47836@xcllnt.net>, Marcel Moolenaar writes: >Permissions seems to have gone out to lunch... Hmm, do you know what kind of filesystem it is ? FAT12/FAT16/FAT32 ? I think it says in a string if you hexdump the first sector. Poul-Henning >pluto2# mount | grep efi >/dev/da0p1 on /efi (msdosfs, local) > >pluto2# ls -alR /efi >total 22 >d--------- 1 root wheel 16384 Jan 1 1980 . >drwxr-xr-x 21 root wheel 512 Dec 8 04:06 .. >d--------- 1 root wheel 4096 Jan 30 2003 boot > >/efi/boot: >total 1668 >d--------- 1 root wheel 4096 Jan 30 2003 . >d--------- 1 root wheel 16384 Jan 1 1980 .. >d--------- 1 root wheel 4096 Jul 18 22:14 backup >d--------- 1 root wheel 4096 Jan 30 2003 defaults >---------- 1 root wheel 110 Nov 20 20:29 device.hints >d--------- 1 root wheel 4096 Dec 8 04:05 kernel >d--------- 1 root wheel 4096 Dec 6 05:23 kernel.old >---------- 1 root wheel 7772 Dec 6 05:27 loader.4th >---------- 1 root wheel 96 Jan 31 2004 loader.conf >---------- 1 root wheel 542608 Dec 6 05:27 loader.efi >---------- 1 root wheel 12465 Dec 6 05:27 loader.help >---------- 1 root wheel 365 Jul 25 2002 loader.rc >d--------- 1 root wheel 4096 Jan 30 2003 modules >---------- 1 root wheel 1031168 Dec 6 05:27 skiload >---------- 1 root wheel 12465 Dec 6 05:27 skiload.help >---------- 1 root wheel 36440 Dec 6 05:27 support.4th > >...and so on... > >This is with an up-to-date kernel: > >FreeBSD 6.0-CURRENT #1: Wed Dec 8 04:05:20 UTC 2004 > marcel@pluto2.freebsd.org:/q/obj/q/6.x/src/sys/PLUTO2 > >A kernel dated december 6th, doesn't have this problem. > >-- > Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net > >_______________________________________________ >freebsd-current@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-current >To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 08:49:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C77E16A4CE for ; Wed, 8 Dec 2004 08:49:02 +0000 (GMT) Received: from natnoddy.rzone.de (natnoddy.rzone.de [81.169.145.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id D01A143D46 for ; Wed, 8 Dec 2004 08:49:01 +0000 (GMT) (envelope-from uwe@laverenz.de) Received: from athena.laverenz.de (pD9550B48.dip.t-dialin.net [217.85.11.72]) by post.webmailer.de (8.13.1/8.13.1) with ESMTP id iB88mxeG015672 for ; Wed, 8 Dec 2004 09:48:59 +0100 (MET) Received: from localhost (localhost.localdomain [127.0.0.1]) by athena.laverenz.de (Postfix) with ESMTP id 8E2CBE023F2D for ; Wed, 8 Dec 2004 09:48:58 +0100 (CET) Received: from athena.laverenz.de ([127.0.0.1]) by localhost (athena [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 27371-02-2 for ; Wed, 8 Dec 2004 09:48:58 +0100 (CET) Received: from jungle.laverenz.de (jungle.laverenz.de [192.168.100.8]) by athena.laverenz.de (Postfix) with ESMTP id 1F9E3E023F29 for ; Wed, 8 Dec 2004 09:48:58 +0100 (CET) Received: by jungle.laverenz.de (Postfix, from userid 2000) id C4AC3800B3D1; Wed, 8 Dec 2004 09:48:57 +0100 (CET) Date: Wed, 8 Dec 2004 09:48:57 +0100 From: Uwe Laverenz To: freebsd-current@freebsd.org Message-ID: <20041208084857.GC5317@laverenz.de> Mail-Followup-To: freebsd-current@freebsd.org References: <20041207234840.7287cdf4@maya.liquidx.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041207234840.7287cdf4@maya.liquidx.org> Organization: private site Sender: uwe@laverenz.de User-Agent: Mutt/1.5.6+20040722i X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at laverenz.de Subject: Re: FreeBSD sound distortion problems with SB Live! fixed with PREEMPTION X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 08:49:02 -0000 Hi Travis, > handful of drivers (emu10k1 is the one I'm having problems with) have I have the same problem with emu10k1 on RELENG_5, and I know of others, who have the same with emu10k1 and es137x. > this problem. For the record, I am not the only one who has reported > this problem to the lists. Yes, there are many users with this annoying problem and although sound is not the most important thing for FreeBSD, it has the potential to make people lose confidence in FreeBSD 5.x. However, I can can confirm that PREEMPTION solves the problem on my machine also and I thank you very much for finding this solution. :-) cu, Uwe From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 08:57:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C475716A4CE; Wed, 8 Dec 2004 08:57:35 +0000 (GMT) Received: from postfix4-1.free.fr (postfix4-1.free.fr [213.228.0.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 513ED43D53; Wed, 8 Dec 2004 08:57:35 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (unknown [82.233.239.98]) by postfix4-1.free.fr (Postfix) with ESMTP id 4F10021850A; Wed, 8 Dec 2004 09:57:34 +0100 (CET) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 6D4CE412C; Wed, 8 Dec 2004 09:56:01 +0100 (CET) Date: Wed, 8 Dec 2004 09:56:00 +0100 From: Jeremie Le Hen To: Travis Poppe Message-ID: <20041208085600.GR79919@obiwan.tataz.chchile.org> References: <20041207234840.7287cdf4@maya.liquidx.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041207234840.7287cdf4@maya.liquidx.org> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD sound distortion problems with SB Live! fixed with PREEMPTION X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 08:57:36 -0000 [ freebsd-stabl@ is now the right place for RELENG_5 ]. On Tue, Dec 07, 2004 at 11:48:40PM -0700, Travis Poppe wrote: > Hello all, > > Back in October, I contacted the list and described a problem I was > having with FreeBSD 5.X (now 5.3-RELEASE) and sound. I will reiterate > the problem one more time for those of you who did not follow the posts. > > I was using FreeBSD 5.3-BETA7 at the time (as far as I know, all of 5.x > has this problem) and have an SB Live! 5.1 which uses the emu10k1 > driver. I've been told that this problem may be specific to my driver > (and possibly others). > > The problem: > > When playing music with XMMS after my box had been up for at least a day > or two, I'd hear these "random" skips and sound distortions that can be > described as the sound being slowed down for 1/4th of a second and then > back to normal again (a "lagged sound" skip). I have *exactly* the same problem on a 5.3 box (branch RELENG_5 after RELENG_5_3_BP). FreeBSD obiwan 5.3-STABLE FreeBSD 5.3-STABLE #3: Sun Nov 21 17:22:54 CET 2004 root@obiwan:/usr/src/sys/i386/compile/OBIWAN i386 > A much more severe version of this can easily be reproduced by > extracting the firefox source code from bz2 while playing music and can > be witnessed for as long as it takes to extract the archive. Note that > these are not just "skips" but complete sound distortion as well. If you > hear very minor brief skips when running this test but no distortion, > you are not witnessing the same problem. > > In the previous posts to -CURRENT, I was advised to increase the sound > buffer which did HELP, but the problem was still there. Increasing the > buffer also caused de-synced sound in games. This was not a good > workaround. > > Anyway, today I was playing around with a few patches derived from > DragonFly that make it possible to use high resolution VESA modes with > syscons. I was using a 1024x768 VESA text console when I noticed that if > a lot of text were to be scrolled on the screen at once, I'd hear the > same sound problem described above. > > Frustrated, I began conversation on IRC and described my problem. A > friend of mine suggested something no one else had before, and that > suggestion was to enable PREEMPTION in the kernel. A GNU/Linux user in > another channel also said this to me: "Sounds like FreeBSD needs a > preemptable kernel." So, I decided to give it a try. > > To my amazement, it worked completely. Enabling PREEMPTION in the kernel > completely "fixes" this problem to the fullest extent. I have not been > able to reproduce the problem since using any of the methods described > above. > > I'm hoping that with this new information someone might be able to > figure out what is truly causing this problem and can come up with a > solution (or is PREEMPTION a good solution?). It seems that only a > handful of drivers (emu10k1 is the one I'm having problems with) have > this problem. For the record, I am not the only one who has reported > this problem to the lists. You make me happy ! I noticed this problem yesterday evening, and I did'nt have time to investigate yet. It definitely seems that PREEMPTION is the good solution since these small "breaks" in sounds indicates that, coarsely, the kernel does not "have enough time" to do what it wants between two sound frames. Basically, PREEMPTION allows to interrupt the kernel in its current task if there is something more important to do, like pushing a new sound frame. (If someone wants to make a more precise description -- or even correct me if I'm wrong --, I would be graceful.) FIY, Linux folks have a dedicated preemption patch which was initially started to make things such as Jack Audio Connection Kit [1] and related softwares work fine. Regards, [1] http://jackit.sf.net/ -- Jeremie Le Hen jeremie@le-hen.org From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 10:08:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16F4B16A4CE for ; Wed, 8 Dec 2004 10:08:54 +0000 (GMT) Received: from smtp02.syd.iprimus.net.au (smtp02.syd.iprimus.net.au [210.50.76.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1A2443D49 for ; Wed, 8 Dec 2004 10:08:53 +0000 (GMT) (envelope-from tim@robbins.dropbear.id.au) Received: from robbins.dropbear.id.au (210.50.220.100) by smtp02.syd.iprimus.net.au (7.0.036) id 41A76DCB004ECCE7; Wed, 8 Dec 2004 21:08:52 +1100 Received: by robbins.dropbear.id.au (Postfix, from userid 1000) id BBB6E4264; Wed, 8 Dec 2004 21:09:19 +1100 (EST) Date: Wed, 8 Dec 2004 21:09:19 +1100 From: Tim Robbins To: Poul-Henning Kamp Message-ID: <20041208100919.GA18279@cat.robbins.dropbear.id.au> References: <9EF07AD4-48D0-11D9-BD23-000D93C47836@xcllnt.net> <20121.1102495691@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20121.1102495691@critter.freebsd.dk> User-Agent: Mutt/1.4.1i cc: current@freebsd.org cc: Marcel Moolenaar Subject: Re: msdosfs borked X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 10:08:54 -0000 On Wed, Dec 08, 2004 at 09:48:11AM +0100, Poul-Henning Kamp wrote: > In message <9EF07AD4-48D0-11D9-BD23-000D93C47836@xcllnt.net>, Marcel Moolenaar > writes: > >Permissions seems to have gone out to lunch... > > Hmm, do you know what kind of filesystem it is ? FAT12/FAT16/FAT32 ? This kind of thing is symptomatic of mount arguments not being passed correctly and ending up as zero. I've seen it happen in the past when the layout of struct msdosfs_args changed. Tim From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 10:29:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DD60F16A4CE; Wed, 8 Dec 2004 10:29:52 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3939A43D58; Wed, 8 Dec 2004 10:29:52 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB8ATnt7021758; Wed, 8 Dec 2004 11:29:50 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Tim Robbins From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 08 Dec 2004 21:09:19 +1100." <20041208100919.GA18279@cat.robbins.dropbear.id.au> Date: Wed, 08 Dec 2004 11:29:49 +0100 Message-ID: <21757.1102501789@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@freebsd.org cc: Marcel Moolenaar Subject: Re: msdosfs borked X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 10:29:53 -0000 In message <20041208100919.GA18279@cat.robbins.dropbear.id.au>, Tim Robbins wri tes: >On Wed, Dec 08, 2004 at 09:48:11AM +0100, Poul-Henning Kamp wrote: >> In message <9EF07AD4-48D0-11D9-BD23-000D93C47836@xcllnt.net>, Marcel Moolenaar >> writes: >> >Permissions seems to have gone out to lunch... >> >> Hmm, do you know what kind of filesystem it is ? FAT12/FAT16/FAT32 ? > >This kind of thing is symptomatic of mount arguments not being passed >correctly and ending up as zero. I've seen it happen in the past when the >layout of struct msdosfs_args changed. yes indeed, (this is, btw, one of the things nmount hopefully will improve once we use it all the way from userland) Only trouble is I don't see the zero perms here... + ls -l /mnt + head -4 total 1347 -rwxr-xr-x 1 root wheel 6260 Sep 30 1993 ansi.sy_ -rwxr-xr-x 1 root wheel 7467 Sep 30 1993 append.ex_ -rwxr-xr-x 1 root wheel 11208 Sep 30 1993 attrib.exe -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 11:47:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8B6216A4CE for ; Wed, 8 Dec 2004 11:47:15 +0000 (GMT) Received: from email11.aon.at (warsl404pip7.highway.telekom.at [195.3.96.91]) by mx1.FreeBSD.org (Postfix) with SMTP id C1A4E43D58 for ; Wed, 8 Dec 2004 11:47:14 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: (qmail 237166 invoked from network); 8 Dec 2004 11:47:13 -0000 Received: from m096p026.dipool.highway.telekom.at (HELO localhost.localdomain) ([62.46.1.250]) (envelope-sender ) by email11.aon.at (qmail-ldap-1.03) with SMTP for ; 8 Dec 2004 11:47:13 -0000 From: Stefan Ehmann To: Travis Poppe In-Reply-To: <20041207234840.7287cdf4@maya.liquidx.org> References: <20041207234840.7287cdf4@maya.liquidx.org> Content-Type: text/plain Date: Wed, 08 Dec 2004 12:47:11 +0100 Message-Id: <1102506431.1090.8.camel@taxman> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: FreeBSD sound distortion problems with SB Live! fixed with PREEMPTION X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 11:47:15 -0000 On Tue, 2004-12-07 at 23:48 -0700, Travis Poppe wrote: ... > To my amazement, it worked completely. Enabling PREEMPTION in the kernel > completely "fixes" this problem to the fullest extent. I have not been > able to reproduce the problem since using any of the methods described > above. > > I'm hoping that with this new information someone might be able to > figure out what is truly causing this problem and can come up with a > solution (or is PREEMPTION a good solution?). It seems that only a > handful of drivers (emu10k1 is the one I'm having problems with) have > this problem. For the record, I am not the only one who has reported > this problem to the lists. I also experience the same problems with sound you've described. As PREEMPTION seems to stable for you, I tried to turn it on again. Unfortunately PREEMPTION remains to be completely unusable for me. The system freezes within 5 minutes. The problem is described here: http://lists.freebsd.org/pipermail/freebsd-current/2004-September/037949.html I wonder if no one else gets this kind of problem. From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 11:53:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6033E16A4CE for ; Wed, 8 Dec 2004 11:53:37 +0000 (GMT) Received: from email08.aon.at (warsl404pip7.highway.telekom.at [195.3.96.91]) by mx1.FreeBSD.org (Postfix) with SMTP id 5DC5F43D58 for ; Wed, 8 Dec 2004 11:53:36 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: (qmail 317778 invoked from network); 8 Dec 2004 11:53:35 -0000 Received: from m096p026.dipool.highway.telekom.at (HELO localhost.localdomain) ([62.46.1.250]) (envelope-sender ) by email08.aon.at (qmail-ldap-1.03) with SMTP for ; 8 Dec 2004 11:53:35 -0000 From: Stefan Ehmann To: Poul-Henning Kamp Content-Type: text/plain Date: Wed, 08 Dec 2004 12:53:33 +0100 Message-Id: <1102506813.1090.14.camel@taxman> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: ext2fs oddness X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 11:53:37 -0000 Today, after recovering from a crash, I noticed some strangeness. I got this line in my /etc/fstab: /dev/ad1s1 /mnt/stuff ext2fs ro,noauto After the crash, I got this when I tried to mount the filesystem: WARNING: R/W mount denied. Filesystem is not clean - run fsck So the filesystem was modified although it was mounted read-only. And it also complained that it couldn't be mounted rw although I only wanted it mounted ro. So this looks like it was mounted rw instead of ro. df though says: /dev/ad1s1 on /mnt/stuff (ext2fs, local, read-only) Also this doesn't work: touch /mnt/stuff/foo touch: /mnt/stuff/foo: Read-only file system I suspect your mount patch since I haven't seen this before. From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 11:55:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D328F16A4CF for ; Wed, 8 Dec 2004 11:55:26 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 181F043D58 for ; Wed, 8 Dec 2004 11:55:26 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB8BtNqv023034; Wed, 8 Dec 2004 12:55:24 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Andre Guibert de Bruet From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 07 Dec 2004 23:50:58 EST." <20041207234332.Q637@alpha.siliconlandmark.com> Date: Wed, 08 Dec 2004 12:55:23 +0100 Message-ID: <23033.1102506923@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-current@freebsd.org Subject: Re: dump broken with new kernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 11:55:27 -0000 In message <20041207234332.Q637@alpha.siliconlandmark.com>, Andre Guibert de Br uet writes: >I am still running into dump problems on my system. I'm using: >$FreeBSD: src/sys/kern/vfs_mount.c,v 1.168 2004/12/07 08:15:40 phk Exp $ >$FreeBSD: src/sys/sys/mount.h,v 1.187 2004/12/07 08:15:40 phk Exp $ > >FreeBSD bling.home 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Tue Dec 7 23:02:43 >EST 2004 root@bling.home:/usr/CURRENT/sys/i386/compile/BLING i386 > ># /sbin/dump -0uaLf "/mnt/backups/`hostname -s`-`utime`-amrd0a.dump" /mnt/amrd0a >mksnap_ffs: Cannot create /mnt/amrd0a/.snap/dump_snapshot: Bad address >dump: Cannot create /mnt/amrd0a/.snap/dump_snapshot: No such file or directory Ok, should work now. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 12:02:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5806C16A4CE for ; Wed, 8 Dec 2004 12:02:35 +0000 (GMT) Received: from lara.cc.fer.hr (lara.cc.fer.hr [161.53.72.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 777F743D39 for ; Wed, 8 Dec 2004 12:02:34 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [127.0.0.1] (localhost.cc.fer.hr [127.0.0.1]) by lara.cc.fer.hr (8.13.1/8.13.1) with ESMTP id iB8C2Mrf005035 for ; Wed, 8 Dec 2004 13:02:22 +0100 (CET) (envelope-from ivoras@fer.hr) Message-ID: <41B6ED4E.6030301@fer.hr> Date: Wed, 08 Dec 2004 13:02:22 +0100 From: Ivan Voras User-Agent: Mozilla Thunderbird 0.9 (X11/20041111) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org References: <20041207234840.7287cdf4@maya.liquidx.org> <1102506431.1090.8.camel@taxman> In-Reply-To: <1102506431.1090.8.camel@taxman> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD sound distortion problems with SB Live! fixed with PREEMPTION X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 12:02:35 -0000 Stefan Ehmann wrote: > On Tue, 2004-12-07 at 23:48 -0700, Travis Poppe wrote: > ... > >>To my amazement, it worked completely. Enabling PREEMPTION in the kernel >>completely "fixes" this problem to the fullest extent. I have not been >>able to reproduce the problem since using any of the methods described >>above. > Unfortunately PREEMPTION remains to be completely unusable for me. The > system freezes within 5 minutes. > I wonder if no one else gets this kind of problem. Not exactly a freeze, but PREEMPTION doesn't help me at all with SB Live (slowdowns, stuttering sound, etc.), especially with large amounts of filesystem operations (this is 5-stable). From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 19:46:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5569C16A4CE for ; Tue, 7 Dec 2004 19:46:43 +0000 (GMT) Received: from mail.squidge.com (mail0.squidge.com [195.10.252.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5028B43D5C for ; Tue, 7 Dec 2004 19:46:42 +0000 (GMT) (envelope-from henry@jot.to) Received: from lightbox (82-70-14-145.dsl.in-addr.zen.co.uk [82.70.14.145]) (authenticated bits=0) by mail.squidge.com (8.13.1/8.12.9) with ESMTP id iB7JkbwC036838; Tue, 7 Dec 2004 19:46:37 GMT Message-ID: <00a601c4dc95$7ae36fe0$0a64a8c0@techiebod.com> From: "Henry Whincup" To: "Doug White" References: <006501c4da28$5692e130$0a64a8c0@techiebod.com> <20041206105139.E19661@carver.gumbysoft.com> Date: Tue, 7 Dec 2004 19:46:43 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 8bit 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: by AMaViS at mail.squidge.com X-Spam-Level: -1.0 X-Mailman-Approved-At: Wed, 08 Dec 2004 12:53:08 +0000 cc: freebsd-current@freebsd.org Subject: Re: ffs_clusteralloc: allocated out of group on 5TB fs (5.3-Stable) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 19:46:43 -0000 > Very large FFS filesystems have not been extensively tested. Maybe you can > help :) > > You should be able to compile GENERIC with > > makeoptions "DEBUG=-g" > > in the config file and that will leave a kernel.debug in the compile > directory that you can use. > > Once you get that loaded up the output of 'bt full' would be nice to have. Let me know if you want anything else... (kgdb) bt full #0 doadump () at pcpu.h:159 No locals. #1 0xc060d47b in boot (howto=0x104) at /usr/src/sys/kern/kern_shutdown.c:397 first_buf_printf = 0x1 #2 0xc060d7a1 in panic (fmt=0xc082c448 "ffs_clusteralloc: allocated out of group") at /usr/src/sys/kern/kern_shutdown.c:553 td = (struct thread *) 0xc39b7320 bootopt = 0x104 newpanic = 0x0 ap = 0xc39b7320 "Ôh\233ÃÀ\201\233Ã" buf = "ffs_clusteralloc: allocated out of group", '\0' #3 0xc0734456 in ffs_clusteralloc (ip=0xc3b5808c, cg=0x5928, bpref=0x1, len=0x5) at /usr/src/sys/ufs/ffs/ffs_alloc.c:1526 fs = (struct fs *) 0xc372f000 cgp = (struct cg *) 0xdae55000 bp = (struct buf *) 0xd76807c8 i = 0x0 run = 0x5 bit = 0x0 map = 0x0 got = 0xc372f000 bno = 0xffffffff80000020 mapp = (u_char *) 0xffffffff "" lp = (int32_t *) 0x0 blksfree = (u_int8_t *) 0xdae55c28 "ÿ" #4 0xc0733678 in ffs_hashalloc (ip=0xc3b5808c, cg=0x5928, pref=0x7fffb548, size=0x5, allocator=0xc07340f0 ) at /usr/src/sys/ufs/ffs/ffs_alloc.c:1159 fs = (struct fs *) 0xc372f000 result = Unhandled dwarf expression opcode 0x93 (kgdb) print *cgp $4 = { cg_firstfield = 0x0, cg_magic = 0x90255, cg_old_time = 0x41b59fe4, cg_cgx = 0x5928, cg_old_ncyl = 0x0, cg_old_niblk = 0x0, cg_ndblk = 0x16f88, cg_cs = { cs_ndir = 0x0, cs_nbfree = 0x2496, cs_nifree = 0x5c00, cs_nffree = 0x0 }, cg_rotor = 0x4ad8, cg_frotor = 0x4ad8, cg_irotor = 0x0, cg_frsum = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, cg_old_btotoff = 0x0, cg_old_boff = 0x0, cg_iusedoff = 0xa8, cg_freeoff = 0xc28, cg_nextfreeoff = 0x3ffb, cg_clustersumoff = 0x3a18, cg_clusteroff = 0x3a3c, cg_nclusterblks = 0x2df1, cg_niblk = 0x5c00, cg_initediblk = 0x80, cg_sparecon32 = {0x0, 0x0, 0x0}, cg_time = 0x41b59fe4, cg_sparecon64 = {0x0, 0x0, 0x0}, cg_space = "" } (kgdb) print *bp $5 = { b_io = { bio_cmd = 0x1, bio_flags = 0x2, bio_cflags = 0x0, bio_pflags = 0x0, bio_dev = 0xc3977900, bio_disk = 0x0, bio_offset = 0x3fffdab8000, bio_bcount = 0x4000, bio_data = 0xdae55000 "", bio_error = 0x0, bio_resid = 0x0, bio_done = 0xc0653cdc , bio_driver1 = 0x0, bio_driver2 = 0x0, bio_caller1 = 0x0, bio_caller2 = 0xd76807c8, bio_queue = { tqe_next = 0x0, tqe_prev = 0x0 }, bio_attribute = 0x0, bio_from = 0x0, bio_to = 0x0, bio_length = 0x0, bio_completed = 0x0, bio_children = 0x7d, bio_inbed = 0x0, bio_parent = 0x0, bio_t0 = { sec = 0x0, frac = 0x0 }, bio_task = 0, bio_task_arg = 0x0, bio_pblkno = 0x0 }, b_op = 0xc0878bc8, b_magic = 0x10b10b10, b_iodone = 0, b_blkno = 0x1fffed5c0, b_offset = 0x3fffdab8000, b_vnbufs = { tqe_next = 0x0, tqe_prev = 0xd752f4e8 }, b_left = 0xd752f448, b_right = 0x0, b_vflags = 0x0, b_freelist = { tqe_next = 0xd768097c, tqe_prev = 0xc08dd048 }, b_qindex = 0x0, b_flags = 0x20000220, b_xflags = 0x12, b_lock = { lk_interlock = 0xc08d5bf8, lk_flags = 0x400, lk_sharecount = 0x0, lk_waitcount = 0x0, lk_exclusivecount = 0x1, lk_prio = 0x50, lk_wmesg = 0xc0820fb6 "bufwait", lk_timo = 0x0, lk_lockholder = 0xc39b7320, lk_newlock = 0x0 }, b_bufsize = 0x4000, b_runningbufspace = 0x0, b_kvabase = 0xdae55000 "", b_kvasize = 0x4000, b_lblkno = 0x1fffed5c0, b_vp = 0xc39e5738, b_object = 0xc39eb948, b_dirtyoff = 0x0, b_dirtyend = 0x0, b_rcred = 0x0, b_wcred = 0x0, b_saveaddr = 0xdae55000, b_pager = { pg_reqpage = 0x0 }, b_cluster = { cluster_head = { tqh_first = 0x0, tqh_last = 0x0 }, cluster_entry = { tqe_next = 0x0, tqe_prev = 0x0 } }, b_pages = {0xc2f21a90, 0xc2f0fad8, 0xc2f7a020, 0xc2f62668, 0x0 }, b_npages = 0x4, b_dep = { lh_first = 0x0 } } (kgdb) From owner-freebsd-current@FreeBSD.ORG Tue Dec 7 21:01:14 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A21E716A4CE for ; Tue, 7 Dec 2004 21:01:14 +0000 (GMT) Received: from mailbox.rainbownet.com (mailbox.rainbownet.com [213.174.191.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4344743D64 for ; Tue, 7 Dec 2004 21:01:13 +0000 (GMT) (envelope-from aturetta@commit.it) Received: from 192.168.42.122 ([81.174.12.226]) (authenticated user aturetta@rainbownet.com) by rainbownet.com (mailbox.rainbownet.com [127.0.0.1]) (MDaemon.PRO.v6.8.5.R) with ESMTP id 44-md50000000567.tmp for ; Tue, 07 Dec 2004 22:00:28 +0100 Message-ID: <41B619ED.5090909@commit.it> Date: Tue, 07 Dec 2004 22:00:29 +0100 From: Angelo Turetta User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20041207181056.OJMF28664.lakermmtao08.cox.net@smtp.east.cox.net> In-Reply-To: <20041207181056.OJMF28664.lakermmtao08.cox.net@smtp.east.cox.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-Sender: aturetta@rainbownet.com X-Spam-Processed: mailbox.rainbownet.com, Tue, 07 Dec 2004 22:00:28 +0100 (not processed: message from valid local sender) X-MDRemoteIP: 81.174.12.226 X-Return-Path: aturetta@commit.it X-MDaemon-Deliver-To: freebsd-current@freebsd.org X-Mailman-Approved-At: Wed, 08 Dec 2004 12:53:08 +0000 cc: m.kucenski@computer.org Subject: Re: ATAPI Problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Dec 2004 21:01:14 -0000 Matt Kucenski wrote: > I have had this problem with my DVD drive since 5.3RC1. I > just installed 6-LATEST hoping that the problem may have > been corrected, but no such luck. > > A normal boot of the GENERIC kernel gives these messages: > > acd0: FAILURE - MODE_SENSE_BIG timed out > acd0: CDROM at ata1-master UDMA33 > > Afterwards, I am unable to mount a CD. I receive several > more of the same "timed out" messages, followed > by "Input/output error" message when running 'mount /cdrom'. Same here, BETA7 did not exhibit this behaviour: ad0: 78167MB [158816/16/63] at ata0-master UDMA133 acd0: FAILURE - MODE_SENSE_BIG timed out acd0: CDRW at ata1-slave UDMA33 > If I run 'atacontrol mode 1 BIOSPIO BIOSPIO' (DVD drive is > only drive on second ata channel), I receive one > > acd0: FAILURE - TEST_UNIT_READY timed out > > message and then the drive will mount normally. Not tried, I'll do.. > Also, if I boot verbosely, my dmesg shows this: > (...) > No errors and the drive will mount normally. So you say that booting -v you don't see the error? I'll try this too! > I have tried several combinations of slave/master on > different ATA channels with the same results. I have also > tried booting with/without ACPI and with/without DMA > (hw.ata.atapi_dma="0/1" in loader.conf) and combinations of > the two. Yes, that's the first thing I thought of, but it did no difference for me too. A bug with the same simptoms has existed ever since in 4-STABLE: the ATA/ATAPI code is compeletely new in 5.x so I think it's not related, but I quote the PRs for reference, who knows: http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/66368 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/36610 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/56889 (the latter has been closed, but without being fixed on 4-STABLE, and the same thing happened to 36610. I hope this one is not beeing 'forgot' for some months and the closed because 'This bug is old, I think it's been fixed') I've already declared in the past my availability to help in debugging, but nobody cared (and the bug was never fixed): nevertheless, here I am again. Angelo Turetta. From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 04:42:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BFF616A4CE for ; Wed, 8 Dec 2004 04:42:33 +0000 (GMT) Received: from draft.nq.nu (203-173-42-29.perm.iinet.net.au [203.173.42.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67E3743D1D for ; Wed, 8 Dec 2004 04:42:31 +0000 (GMT) (envelope-from warren@draft.nq.nu) Received: from www.slingo.nq.nu (localhost [127.0.0.1]) by draft.nq.nu (8.12.10/8.12.8) with ESMTP id iB84gAF6091375 for ; Wed, 8 Dec 2004 14:42:10 +1000 (EST) (envelope-from warren@draft.nq.nu) From: "Warren Liddell" To: freebsd-current@freebsd.org Date: Wed, 8 Dec 2004 14:42:10 +1000 Message-Id: <20041208043614.M16581@slingo.nq.nu> X-Mailer: Open WebMail 2.32 20040525 X-OriginatingIP: 10.100.2.10 (warren) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Virus-Scanned: by amavisd-new X-Mailman-Approved-At: Wed, 08 Dec 2004 12:53:08 +0000 Subject: Complete build failure of package py24-qt-3.13 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 04:42:33 -0000 py24-qt-3.13 refuses to build coming out qwith multiple errors from the moment it starts to install .. is this port being worked on ? Below is a snippet of the errors i get. ============================================================ sipqtQString.cpp:2882: error: variable or field `dealloc_QString' declared void sipqtQString.cpp:2882: error: `sipWrapper' was not declared in this scope sipqtQString.cpp:2882: error: `sipSelf' was not declared in this scope sipqtQString.cpp:2883: error: expected `,' or `;' before '{' token sipqtQString.cpp:2891: error: `sipWrapper' was not declared in this scope sipqtQString.cpp:2891: error: expected primary-expression before ',' token sipqtQString.cpp:2891: error: `PyObject' was not declared in this scope sipqtQString.cpp:2891: error: `sipArgs' was not declared in this scope sipqtQString.cpp:2891: error: expected primary-expression before "int" sipqtQString.cpp:2892: error: initializer expression list treated as compound expression sipqtQString.cpp:2892: error: expected `,' or `;' before '{' token sipqtQString.cpp:2997: error: `PyObject' was not declared in this scope sipqtQString.cpp:2997: error: `sipPy' was not declared in this scope sipqtQString.cpp:2997: error: expected primary-expression before "void" sipqtQString.cpp:2997: error: expected primary-expression before "int" sipqtQString.cpp:2998: error: initializer expression list treated as compound expression sipqtQString.cpp:2998: error: expected `,' or `;' before '{' token sipqtQString.cpp:3054: error: `PyObject' was not declared in this scope sipqtQString.cpp:3054: error: `valobj' was not declared in this scope sipqtQString.cpp:3054: error: expected primary-expression before "int" sipqtQString.cpp:3055: error: initializer expression list treated as compound expression sipqtQString.cpp:3055: error: expected `,' or `;' before '{' token sipqtQString.cpp:3077: error: `sipPySlotDef' does not name a type sipqtQString.cpp:3093: error: `PyMethodDef' does not name a type sipqtQString.cpp:3156: error: `sipEnumValueInstanceDef' does not name a type sipqtQString.cpp:3166: error: `sipTypeDef' does not name a type sipqtQString.cpp:2482: warning: 'slot_QString___contains__' defined but not used sipqtQString.cpp:2517: warning: 'slot_QString___len__' defined but not used sipqtQString.cpp:2874: warning: 'void* cast_QString(void*, int*)' defined but not used sipqtQString.cpp:2882: warning: 'dealloc_QString' defined but not used sipqtQString.cpp:2891: warning: 'init_QString' defined but not used sipqtQString.cpp:2997: warning: 'convertTo_QString' defined but not used sipqtQString.cpp:3054: warning: 'forceConvertTo_QString' defined but not used *** Error code 1 Stop in /usr/ports/x11-toolkits/py-qt/work/PyQt-x11-gpl-3.13/qt. *** Error code 1 Stop in /usr/ports/x11-toolkits/py-qt/work/PyQt-x11-gpl-3.13. *** Error code 1 Stop in /usr/ports/x11-toolkits/py-qt. *** Error code 1 Stop in /usr/ports/net/qtorrent. -- Yours Sincerely Shinjii. From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 07:52:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03BE716A4CE for ; Wed, 8 Dec 2004 07:52:58 +0000 (GMT) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5028043D4C for ; Wed, 8 Dec 2004 07:52:57 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86])iB87qtKP008863; Wed, 8 Dec 2004 18:52:55 +1100 Received: from epsplex.bde.org (katana.zip.com.au [61.8.7.246]) iB87qrcH022387; Wed, 8 Dec 2004 18:52:54 +1100 Date: Wed, 8 Dec 2004 18:52:53 +1100 (EST) From: Bruce Evans X-X-Sender: bde@epsplex.bde.org To: Mike Tancsa In-Reply-To: <6.0.3.0.0.20040603220621.045655e0@64.7.153.2> Message-ID: <20041208184326.W1740@epsplex.bde.org> References: <6.0.3.0.0.20040517154946.06d23d60@64.7.153.2> <6.0.3.0.0.20040603220621.045655e0@64.7.153.2> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Wed, 08 Dec 2004 12:53:08 +0000 cc: freebsd-current@freebsd.org Subject: Re: sio / puc wedging on both -current and -stable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 07:52:58 -0000 Long ago, On Thu, 3 Jun 2004, Mike Tancsa wrote: > Just a quick recap. I can fairly easily trigger an interrupt storm on > these machines with USB enabled in the BIOS. If I disable it, I dont have > a problem and all works well.... However, what I accidently came across > today, was that if I load the USB drivers as a kld, I can *not* wedge the > machine. Note the bottom of the following diff I can now explain this. When usb is in the kernel proper, it normally gets the interrupt first and exposes bugs in sio (see other mail -- there is a conflict but sio ignores the error). When usb is in a module, sio normally gets the interrupt first. There is again a conflict but usb doesn't ignore the error. > diff dmesg.kld dmesg.static > > < uhci2: port 0xb400-0xb41f irq > 12 at device 29.2 on pci0 > < uhci2: Could not allocate irq > < device_probe_and_attach: uhci2 attach returned 6 > < uhci2: port 0xb400-0xb41f irq > 12 at device 29.2 on pci0 > < uhci2: Could not allocate irq > < device_probe_and_attach: uhci2 attach returned 6 This shows uhci2 not ignoring the error. Bruce From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 12:58:19 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C1A116A4CF for ; Wed, 8 Dec 2004 12:58:19 +0000 (GMT) Received: from avscan2.sentex.ca (avscan2.sentex.ca [199.212.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 959CD43D72 for ; Wed, 8 Dec 2004 12:58:18 +0000 (GMT) (envelope-from mike@sentex.net) Received: from localhost (localhost.sentex.ca [127.0.0.1]) by avscan2.sentex.ca (8.12.11/8.12.11) with ESMTP id iB8CwLoo021614 for ; Wed, 8 Dec 2004 07:58:21 -0500 (EST) (envelope-from mike@sentex.net) Received: from avscan2.sentex.ca ([127.0.0.1]) by localhost (avscan2.sentex.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 20840-08 for ; Wed, 8 Dec 2004 07:58:20 -0500 (EST) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by avscan2.sentex.ca (8.12.11/8.12.11) with ESMTP id iB8CwKqr021591 for ; Wed, 8 Dec 2004 07:58:20 -0500 (EST) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.11/8.12.11) with ESMTP id iB8CwA2J034008 for ; Wed, 8 Dec 2004 07:58:10 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <6.2.0.14.0.20041208075458.09709888@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Wed, 08 Dec 2004 07:58:53 -0500 To: freebsd-current@freebsd.org From: Mike Tancsa Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Virus-Scanned: by amavisd-new at avscan2b Subject: possible PPP bugfix / enhancement ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 12:58:19 -0000 Can someone take a look at http://www.freebsd.org/cgi/query-pr.cgi?pr=74821 This has been an outstanding bug / issue for some time in FreeBSD's PPPoE for a lot of DSL users. The patches in the PR add a new config var that allows the user to work around a bug either in FreeBSD's LQR or a bug in Juniper's LQR implementation. Its not clear who is at fault. Without this fix, PPPoE users in Canada and parts of Europe cannot use LCP ECHOs to monitor link status. ---Mike -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 13:51:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F9EF16A4CF for ; Wed, 8 Dec 2004 13:51:48 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72EDB43D5C for ; Wed, 8 Dec 2004 13:51:47 +0000 (GMT) (envelope-from arr@watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iB8DnG3w001158; Wed, 8 Dec 2004 08:49:16 -0500 (EST) (envelope-from arr@watson.org) Received: from localhost (arr@localhost)iB8DnFXw001155; Wed, 8 Dec 2004 08:49:16 -0500 (EST) (envelope-from arr@watson.org) X-Authentication-Warning: fledge.watson.org: arr owned process doing -bs Date: Wed, 8 Dec 2004 08:49:14 -0500 (EST) From: "Andrew R. Reiter" To: "Wilkinson, Alex" In-Reply-To: <20041208070454.GA11139@squash.dsto.defence.gov.au> Message-ID: <20041208084757.T1146@fledge.watson.org> References: <20041208070454.GA11139@squash.dsto.defence.gov.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: matthew.thyer@dsto.defence.gov.au cc: freebsd-current@freebsd.org Subject: Re: panic: process 839(xmms):1 holds process lock but isn't blocked ona lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 13:51:48 -0000 On Wed, 8 Dec 2004, Wilkinson, Alex wrote: :Hi all, : :I got this panic today on a: :FreeBSD 5.3-STABLE #13: Mon Nov 29 09:49:10 CST 2004 : :This panic is reproduceable via two methods: : :1. # kldload snd_ich : :2. add snd_ich_load="YES" to /boot/loader.conf; reboot; : # kldunload snd_ich : For what it's worth, on recent -CURRENt, I've had 'kdload snd_ich' hang my machine... as in full lock up. kldload snd_driver I've had varied success... I booted yesterday AM's -CURRENT and after boot kldload'd snd_Driver and had a hang... but after reb ooting, starting X, su'ing to root, and loading.. it worked. Random :-) :I have a kernel with debugging symbols and a vmcore if anyone is :interested. : :db> trace :kdb_enter(c068735f,c06df360,c068a355,e3744c64,c266c320) at :kdb_enter+0x32 :panic(c068a355,347,c3020698,1,c0686981) at panic+0x14b :turnstile_wait(c2ef6600,c06ddec0,c3021e10,220,c06ddec0) at :turnstile_wait+0x5ec :_mtx_lock_sleep(c06ddec0,c266c320,0,c0684ceb,222) at :_mtx_lock_sleep+0xb0 :_mtx_lock_flags(c06ddec0,0,c0684ceb,222,0) at _mtx_lock_flags+0xaf :ithread_loop(c2661480,e3744d48,c0684acc,323,c2661480) at :ithread_loop+0x1ea :fork_exit(c04de759,c2661480,e3744d48) at fork_exit+0xa6 :fork_trampoline() at fork_trampoline+0x8 :--- trap 0x1, eip = 0, esp = 0xe3744d7c, ebp = 0 --- :db> show pcpu :cpuid = 0 :curthread = 0xc266c320: pid 28 "irq18: uhci2 bt0++" :curpcb = 0xe3744da0 :fpcurthread = none :idlethread = 0xc26644b0: pid 11 "idle" :APIC ID = 0 :currentldt = 0x28 :spin locks held: :db> show lockedvnods :Locked vnodes :db> : : (850)-08.12.2004 hostname-{17:26}-[/var/crash]->sudo kldunload snd_ich :Password: :lock order reversal : 1st 0xc2781a40 pcm0 (sound cdev) @ :/usr/src/sys/modules/sound/sound/../../../dev/sound/pcm/sound.c:706 : 2nd 0xc07c6a20 sndstat (sndstat) @ :/usr/src/sys/modules/sound/sound/../../../dev/sound/pcm/sndstat.c:257 :KDB: stack backtrace: :witness_checkorder(c07c6a20,9,c07c1a3d,101,0) at :witness_checkorder+0x5fa :_sx_xlock(c07c6a20,c07c1a3d,101,0,c2738e00) at _sx_xlock+0x5c :sndstat_unregister(c2753800,8,c07c1b35,2c2,c2753800) at :sndstat_unregister+0x27 :pcm_unregister(c2753800,c06a5f7c,c2753800,e75e2bfc,c2753800) at :pcm_unregister+0x1f5 :ich_pci_detach(c2753800,c26fd850,c06a5f7c,c07a88f1,3) at :ich_pci_detach+0x13 :device_detach(c2753800,c07a8909,c26e2000,1,c26aed80) at :device_detach+0x6b : :_______________________________________________ :freebsd-current@freebsd.org mailing list :http://lists.freebsd.org/mailman/listinfo/freebsd-current :To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" : : -- Andrew R. Reiter arr@watson.org arr@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 15:02:19 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DDB316A4CE for ; Wed, 8 Dec 2004 15:02:19 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 419DA43D54 for ; Wed, 8 Dec 2004 15:02:18 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 5921 invoked by uid 65534); 8 Dec 2004 15:02:16 -0000 Received: from p3EE2699E.dip.t-dialin.net (EHLO lofi.dyndns.org) (62.226.105.158) by mail.gmx.net (mp008) with SMTP; 08 Dec 2004 16:02:15 +0100 X-Authenticated: #443188 Received: from kiste.my.domain (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iB8F26Lw015173 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 8 Dec 2004 16:02:07 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: freebsd-current@freebsd.org Date: Wed, 8 Dec 2004 16:02:00 +0100 User-Agent: KMail/1.7.1 References: <20041208043614.M16581@slingo.nq.nu> In-Reply-To: <20041208043614.M16581@slingo.nq.nu> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2590273.icSjtpLPXs"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412081602.05053.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new cc: Warren Liddell Subject: Re: Complete build failure of package py24-qt-3.13 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 15:02:19 -0000 --nextPart2590273.icSjtpLPXs Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday, 8. December 2004 05:42, Warren Liddell wrote: > py24-qt-3.13 refuses to build coming out qwith multiple errors from the > moment it starts to install .. is this port being worked on ? No. PyQt only supports Python up to version 2.3.3. and there hasn't been a = new=20 upstream release yet, so you'll have to stick with older python for pyqt (a= nd=20 any applications using pyqt) for now. =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart2590273.icSjtpLPXs Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBtxdsXhc68WspdLARAp1WAKCLyCbkctV0C0ZRrZ/tLgLCcndJrwCfd59c wI0PeRktQyQlgSjyjTFw6J0= =m0FB -----END PGP SIGNATURE----- --nextPart2590273.icSjtpLPXs-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 15:14:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9846516A4CE for ; Wed, 8 Dec 2004 15:14:13 +0000 (GMT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 8314643D69 for ; Wed, 8 Dec 2004 15:14:12 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 27278 invoked by uid 65534); 8 Dec 2004 15:14:11 -0000 Received: from p3EE2699E.dip.t-dialin.net (EHLO lofi.dyndns.org) (62.226.105.158) by mail.gmx.net (mp004) with SMTP; 08 Dec 2004 16:14:10 +0100 X-Authenticated: #443188 Received: from kiste.my.domain (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iB8FE4Lw015269 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 8 Dec 2004 16:14:06 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: freebsd-current@freebsd.org Date: Wed, 8 Dec 2004 16:14:01 +0100 User-Agent: KMail/1.7.1 References: <20041208043614.M16581@slingo.nq.nu> <200412081602.05053.michaelnottebrock@gmx.net> In-Reply-To: <200412081602.05053.michaelnottebrock@gmx.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1183895.nCbyGI8di7"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412081614.02332.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new cc: Warren Liddell Subject: Re: Complete build failure of package py24-qt-3.13 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 15:14:13 -0000 --nextPart1183895.nCbyGI8di7 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday, 8. December 2004 16:02, Michael Nottebrock wrote: > On Wednesday, 8. December 2004 05:42, Warren Liddell wrote: > > py24-qt-3.13 refuses to build coming out qwith multiple errors from the > > moment it starts to install .. is this port being worked on ? > > No. PyQt only supports Python up to version 2.3.3. and there hasn't been a > new upstream release yet, so you'll have to stick with older python for > pyqt (and any applications using pyqt) for now. I'll define USE_PYTHON accordingly for all consumers of PyQt so that at lea= st=20 portupgrade will stop to bail as soon as I get a minute to do it. =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart1183895.nCbyGI8di7 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBtxo6Xhc68WspdLARAmjRAJ9kd0r5R2GAwgYKtNpqmVRdehOcAwCdGDjY iU1cNFO8VFACtYaY7GhCHnM= =1FBw -----END PGP SIGNATURE----- --nextPart1183895.nCbyGI8di7-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 15:37:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C46F116A4CE for ; Wed, 8 Dec 2004 15:37:16 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id D5A8D43D62 for ; Wed, 8 Dec 2004 15:37:15 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 27688 invoked by uid 65534); 8 Dec 2004 15:37:12 -0000 Received: from p3EE2699E.dip.t-dialin.net (EHLO lofi.dyndns.org) (62.226.105.158) by mail.gmx.net (mp005) with SMTP; 08 Dec 2004 16:37:12 +0100 X-Authenticated: #443188 Received: from kiste.my.domain (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iB8Fb0Lw015579 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 8 Dec 2004 16:37:04 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: freebsd-current@freebsd.org Date: Wed, 8 Dec 2004 16:36:56 +0100 User-Agent: KMail/1.7.1 References: <20041208043614.M16581@slingo.nq.nu> <200412081602.05053.michaelnottebrock@gmx.net> <200412081614.02332.michaelnottebrock@gmx.net> In-Reply-To: <200412081614.02332.michaelnottebrock@gmx.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1313166.ITftAJhKnV"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412081636.57802.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new cc: Warren Liddell Subject: Re: Complete build failure of package py24-qt-3.13 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 15:37:16 -0000 --nextPart1313166.ITftAJhKnV Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday, 8. December 2004 16:14, Michael Nottebrock wrote: > On Wednesday, 8. December 2004 16:02, Michael Nottebrock wrote: > > On Wednesday, 8. December 2004 05:42, Warren Liddell wrote: > > > py24-qt-3.13 refuses to build coming out qwith multiple errors from t= he > > > moment it starts to install .. is this port being worked on ? > > > > No. PyQt only supports Python up to version 2.3.3. and there hasn't been > > a new upstream release yet, so you'll have to stick with older python f= or > > pyqt (and any applications using pyqt) for now. > > I'll define USE_PYTHON accordingly for all consumers of PyQt so that at > least portupgrade will stop to bail as soon as I get a minute to do it. And finally, this is kind of offtopic on freebsd-current@, freebsd-ports@=20 would be a more appropriate place. =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart1313166.ITftAJhKnV Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBtx+ZXhc68WspdLARAn7uAJ4poGBqG+juqT/abgX3iEdngL8BcwCdGXTv KUkDPcri8cuow1uEe+tY7S4= =6BIY -----END PGP SIGNATURE----- --nextPart1313166.ITftAJhKnV-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 16:43:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01C5816A4CE for ; Wed, 8 Dec 2004 16:43:40 +0000 (GMT) Received: from avscan2.sentex.ca (avscan2.sentex.ca [199.212.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98D8643D2F for ; Wed, 8 Dec 2004 16:43:39 +0000 (GMT) (envelope-from mike@sentex.net) Received: from localhost (localhost.sentex.ca [127.0.0.1]) by avscan2.sentex.ca (8.12.11/8.12.11) with ESMTP id iB8Ghcsk093084 for ; Wed, 8 Dec 2004 11:43:38 -0500 (EST) (envelope-from mike@sentex.net) Received: from avscan2.sentex.ca ([127.0.0.1]) by localhost (avscan2.sentex.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 92485-06 for ; Wed, 8 Dec 2004 11:43:37 -0500 (EST) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by avscan2.sentex.ca (8.12.11/8.12.11) with ESMTP id iB8GhbtP093043 for ; Wed, 8 Dec 2004 11:43:37 -0500 (EST) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.11/8.12.11) with ESMTP id iB8GhVoV034748 for ; Wed, 8 Dec 2004 11:43:31 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <6.2.0.14.0.20041208114117.03027f20@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14 Date: Wed, 08 Dec 2004 11:43:56 -0500 To: freebsd-current@freebsd.org From: Mike Tancsa In-Reply-To: <20041208184326.W1740@epsplex.bde.org> References: <6.0.3.0.0.20040517154946.06d23d60@64.7.153.2> <6.0.3.0.0.20040603220621.045655e0@64.7.153.2> <20041208184326.W1740@epsplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Virus-Scanned: by amavisd-new at avscan2b Subject: Re: sio / puc wedging on both -current and -stable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 16:43:40 -0000 At 02:52 AM 08/12/2004, Bruce Evans wrote: >Long ago, On Thu, 3 Jun 2004, Mike Tancsa wrote: > > >I can now explain this. When usb is in the kernel proper, it normally >gets the interrupt first and exposes bugs in sio (see other mail -- >there is a conflict but sio ignores the error). When usb is in a >module, sio normally gets the interrupt first. There is again a >conflict but usb doesn't ignore the error. For the archives and those interested in this issue, more information along with a number of patches can be found here http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/74786 ---Mike From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 17:13:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA75E16A4E9; Wed, 8 Dec 2004 17:13:22 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAD0443D60; Wed, 8 Dec 2004 17:13:22 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 52F455141A; Wed, 8 Dec 2004 09:19:47 -0800 (PST) Date: Wed, 8 Dec 2004 09:19:47 -0800 From: Kris Kennaway To: Mikhail Teterin Message-ID: <20041208171947.GA46271@xor.obsecurity.org> References: <200412081205.39354.mi+mx@aldan.algebra.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BOKacYhQ+x31HxR3" Content-Disposition: inline In-Reply-To: <200412081205.39354.mi+mx@aldan.algebra.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@FreeBSD.org cc: ade@FreeBSD.org cc: freebsd-amd64@FreeBSD.org cc: Kris Kennaway Subject: Re: new TCL vs. current-6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 17:13:23 -0000 --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 08, 2004 at 12:05:38PM -0500, Mikhail Teterin wrote: > Three of my TCL-based ports fail now on amd64 running current-6. All fail= ures=20 > occur, when an attempt is made to use the TCL-interpreter -- either to ru= n=20 > the port's self-tests, or to generate the manual pages. The failures are= =20 > either "Floating point exceptions" or "Segmentation faults" and appear to= =20 > only happen on amd64 (may be, on ia64 as well): >=20 > http://people.freebsd.org/~fenner/errorlogs/mi%40aldan.algebra.com.html >=20 > Can anyone confirm being able to use freshly built TCL on amd64 _at all_? >=20 > My ports did not change in months -- what could be wrong with TCL and/or= =20 > amd64? Peter speculated a problem when the world is built with -O2 (with or without -fno-strict-aliasing). I haven't been able to confirm this by testing with a world built with -O, because I only have one working amd64 package builder. Kris --BOKacYhQ+x31HxR3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBtzezWry0BWjoQKURAgNWAKDkKLJ2A8O/20nlScYHDdvpqvMr1gCdH0fe Mg8vbrXTRD0BWCrspYw/6cY= =uNBu -----END PGP SIGNATURE----- --BOKacYhQ+x31HxR3-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 17:29:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31E9216A4CE; Wed, 8 Dec 2004 17:29:07 +0000 (GMT) Received: from mail.lovett.com (core.lovett.com [216.168.8.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2225443D55; Wed, 8 Dec 2004 17:29:07 +0000 (GMT) (envelope-from ade@FreeBSD.org) Received: from 66-169-240-6.or.charter.com ([66.169.240.6] helo=[10.21.91.101]) by mail.lovett.com with esmtpa (Exim 4.43 (FreeBSD)) id 1Cc5cg-0008y9-Vm; Wed, 08 Dec 2004 17:29:07 +0000 Message-ID: <41B739E1.8080304@FreeBSD.org> Date: Wed, 08 Dec 2004 09:29:05 -0800 From: Ade Lovett User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mikhail Teterin References: <200412081205.39354.mi+mx@aldan.algebra.com> In-Reply-To: <200412081205.39354.mi+mx@aldan.algebra.com> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@FreeBSD.org cc: freebsd-amd64@FreeBSD.org cc: Kris Kennaway Subject: Re: new TCL vs. current-6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 17:29:07 -0000 Mikhail Teterin wrote: > Can anyone confirm being able to use freshly built TCL on amd64 _at all_? > > My ports did not change in months -- what could be wrong with TCL and/or > amd64? No idea. My one and only working amd64 box (the other is a presario r3000z laptop, don't laugh :P) is running 5.3-STABLE and attempting to do GNOME package building. Sorry. -aDe From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 17:54:44 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3423416A4CE for ; Wed, 8 Dec 2004 17:54:44 +0000 (GMT) Received: from dd1318.kasserver.com (dd1318.kasserver.com [81.209.148.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F39D43D4C for ; Wed, 8 Dec 2004 17:54:43 +0000 (GMT) (envelope-from gbergling@0xfce3.net) Received: from spot.0xfce3.net (port-ip-213-211-224-147.reverse.mdcc-fun.de [213.211.224.147]) by dd1318.kasserver.com (Postfix) with ESMTP id 787D7B05EC for ; Wed, 8 Dec 2004 18:54:41 +0100 (CET) Received: from spot.0xfce3.net (localhost [127.0.0.1]) by spot.0xfce3.net (8.13.1/8.13.1) with ESMTP id iB8HseLK000877 for ; Wed, 8 Dec 2004 18:54:40 +0100 (CET) (envelope-from gbergling@0xfce3.net) Received: (from gordon@localhost) by spot.0xfce3.net (8.13.1/8.13.1/Submit) id iB8HsejP000876 for freebsd-current@freebsd.org; Wed, 8 Dec 2004 18:54:40 +0100 (CET) (envelope-from gbergling@0xfce3.net) X-Authentication-Warning: spot.0xfce3.net: gordon set sender to gbergling@0xfce3.net using -f Date: Wed, 8 Dec 2004 18:54:40 +0100 From: Gordon Bergling To: freebsd-current@freebsd.org Message-ID: <20041208175439.GA829@spot.0xfce3.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Mutt/1.4.2.1i X-Url: X-Operating-System: FreeBSD 5.3-STABLE i386 X-Host-Uptime: 6:47PM up 11 mins, 3 users, load averages: 0.19, 0.23, 0.14 Subject: recent 5-STABLE crash (usb and acpi related) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Gordon Bergling List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 17:54:44 -0000 Hi folks, I bought an optical usb mouse. If I boot with acpi enabled and I plug the usb-mouse in the system hangs immediately. (No kernel output.) If I boot with acpi disabled I had no problems to get the mouse working. System is a 5-STABLE from a few hours ago. dmesg from the mouse: | ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/20.00, addr 2, iclass | 3/1 | ums0: 3 buttons and Z dir. | ums0: at uhub1 port 1 (addr 2) disconnected | ums0: detached | ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/20.00, addr 2, iclass | 3/1 | ums0: 3 buttons and Z dir. dmesg of usb stuff (without acpi): |< ohci0: mem 0xdfffd000-0xdfffdfff irq 20 at | device 3.0 on pci0 | ohci0: [GIANT-LOCKED] | usb0: OHCI version 1.0, legacy support | usb0: SMM does not respond, resetting | usb0: on ohci0 | usb0: USB revision 1.0 | uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 | uhub0: 3 ports with 3 removable, self powered | ohci1: mem 0xdfffe000-0xdfffefff irq 21 at | device 3.1 on pci0 | ohci1: [GIANT-LOCKED] | usb1: OHCI version 1.0, legacy support | usb1: SMM does not respond, resetting | usb1: on ohci1 | usb1: USB revision 1.0 | uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 | uhub1: 3 ports with 3 removable, self powered any hints on how I could solve this problem? best regards, Gordon --=20 Gordon Bergling http://www.0xFCE3.net/ PGP Fingerprint: 7732 9BB1 5013 AE8B E42C 28E0 93B9 D32B C76F 02A0 RIPE-HDL: MDTP-RIPE "There is no place like 127.0.0.0/8" From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 18:35:12 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D0DB16A4CE for ; Wed, 8 Dec 2004 18:35:12 +0000 (GMT) Received: from mailhost.tao.org.uk (transwarp.tao.org.uk [212.135.162.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 183D143D4C for ; Wed, 8 Dec 2004 18:35:12 +0000 (GMT) (envelope-from joe@tao.org.uk) Received: from genius.tao.org.uk (genius.pact.cpes.susx.ac.uk [139.184.130.240]) by mailhost.tao.org.uk (Postfix) with ESMTP id 642447523 for ; Wed, 8 Dec 2004 18:35:11 +0000 (GMT) Received: by genius.tao.org.uk (Postfix, from userid 100) id 49626406F; Wed, 8 Dec 2004 18:35:10 +0000 (GMT) Date: Wed, 8 Dec 2004 18:35:10 +0000 From: Josef Karthauser To: current@freebsd.org Message-ID: <20041208183510.GM1291@genius.pact.cpes.susx.ac.uk> Mail-Followup-To: Josef Karthauser , current@freebsd.org References: <20040927193236.GA39950@laptoxa.toxa.lan> <20041001105544.GG840@genius.tao.org.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3xQkynibq3FKlJyM" Content-Disposition: inline In-Reply-To: <20041001105544.GG840@genius.tao.org.uk> User-Agent: Mutt/1.5.6i Subject: Re: Sony VGN-A 197XP? (Re: Laptop recommendations?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 18:35:12 -0000 --3xQkynibq3FKlJyM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 01, 2004 at 11:55:44AM +0100, Josef Karthauser wrote: > Because I'm a mug, and that they look nice, I'm considering a new Vaio. > The model that has me wetting myself in anticipation is that VGN-A > 197XP, which has a 1.8GHz centrino with a 2mb cache, a 17" 1920x1200 > screen and an 80gb harddrive. It's lovely. >=20 > The big question is how well does FreeBSD run on it? I absolutely need > to have suspend/resume support as it only has a single battery with a > life of around 2.5 hours (no second battery slot :(). >=20 > Has anyone tried FreeBSD on anything like this? What's the chances that > the wireless 802.11g and bluetooth will work? A followup. My girlfriend went to the US recently and brought me back the american version of this one the VGN-A290. It's lovely and under 5.3 the power management works wonderfully :) Thanks ACPI guys. Joe. ps. it's not quite the same spec as the VGN-A 297, missing the blue tooth basically :(. Still it's pretty nice though :). --=20 Josef Karthauser (joe@tao.org.uk) http://www.josef-k.net/ FreeBSD (cvs meister, admin and hacker) http://www.uk.FreeBSD.org/ Physics Particle Theory (student) http://www.pact.cpes.sussex.ac.uk/ =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D An eclectic mix of fact an= d theory. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --3xQkynibq3FKlJyM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iEYEARECAAYFAkG3SV0ACgkQXVIcjOaxUBa+DQCggDuJJbLAGHs8x3Va8KByCv7x ANIAoJD8zcRQtmHmhkV9cp/vHlE/ByXm =Ph4r -----END PGP SIGNATURE----- --3xQkynibq3FKlJyM-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 18:46:50 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6716316A4CE for ; Wed, 8 Dec 2004 18:46:50 +0000 (GMT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DBA543D77 for ; Wed, 8 Dec 2004 18:46:50 +0000 (GMT) (envelope-from bkelly@vadev.org) Received: (qmail 10879 invoked from network); 8 Dec 2004 18:46:49 -0000 Received: from nat.argoneng.com (HELO [192.168.33.71]) (Desdicardo@[208.247.255.11]) (envelope-sender )encrypted SMTP for ; 8 Dec 2004 18:46:46 -0000 Message-ID: <41B74C02.9010002@vadev.org> Date: Wed, 08 Dec 2004 13:46:26 -0500 From: Ben Kelly User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ruslan Ermilov References: <20041207153257.GE1336@ip.net.ua> In-Reply-To: <20041207153257.GE1336@ip.net.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: [TEST] Updated port net/nvnet X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 18:46:50 -0000 Ruslan Ermilov wrote: > Hi, > > I'm the lucky owner of the ASUS SK8N (amd64) motherboard with > the onboard NVIDIA MCP Ethernet. > > With this patch, > > http://people.freebsd.org/~ru/patches/port_net_nvnet.patch > > I'm happily running it for three days without any glitches > noticed so far: > > : nv0: port 0xec00-0xec07 mem 0xfebfc000-0xfebfcfff irq 5 at device 5.0 on pci0 > : nv0: Ethernet address 00:0e:a6:54:dc:67 > : miibus0: on nv0 > : rlphy0: on miibus0 > : rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > : nv0: Ethernet address: 00:0e:a6:54:dc:67 > : nv0: [GIANT-LOCKED] > > I'd be grateful if someone could test this update on i386. I tried this on a CURRENT box last cvsup'ed about a week ago running GENERIC. The hardware is a Shuttle SN45G: http://us.shuttle.com/specs_access.asp?pro_id=279 Unfortunately the patch did not seem to work for me. It looks like nv0 is not detected correctly. All network access results in a nv0 timeout errors. I saw a panic during the boot scroll, but I could not scroll back or investigate as my USB keyboard stopped operating at this point. Its not clear if the panic was related to the nvnet port. I'm sorry this isn't a very helpful report. I am going to work on getting serial access running so I can get more information off the box. I will also try upgrading/reverting my src tree in case I am just stuck on a particularly unstable cvs point; any suggestions for a stable date are welcome. Thanks. - Ben From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 18:52:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0AD616A4CE for ; Wed, 8 Dec 2004 18:52:06 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7D7143D69 for ; Wed, 8 Dec 2004 18:52:06 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.91] ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id iB8IpAWi026244 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Wed, 8 Dec 2004 10:52:06 -0800 (PST) (envelope-from sam@errno.com) From: Sam Leffler Organization: Errno Consulting To: freebsd-current@freebsd.org Date: Wed, 8 Dec 2004 10:59:19 -0800 User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412081059.22949.sam@errno.com> Subject: HEADSUP: updated net80211 layer committed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 18:52:07 -0000 I just committed a major update to the 802.11 support. I did my best to verify all existing users compile and work (where I have cards) but there's sure to be some fallout. In particular I expect that wi cards operating in hostap with wep will need some fixup. If you encounter problems please post here as I've been promised other folks will assist in handling issues. There are many new features added. The most important probably is that there is now full support for WPA, 802.11i, and 802.1x though the wpa_supplicant and hostap programs. I've got simple ports for these packages http://people.freebsd.org/~sam/security-wpa_supplicant.tgz http://people.freebsd.org/~sam/security-hostapd.tgz If someone wants to step up and see them committed it would be appreciated. More work will be filtering in to the tree. I've got a revised ifconfig that hooks up to all the new 802.11 functionality and a dhclient that understands events generated by the 802.11 layer so, for example, roaming between AP's results in fast IP address changes. Sam From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 19:01:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E7D216A4CE for ; Wed, 8 Dec 2004 19:01:13 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id D653343D70 for ; Wed, 8 Dec 2004 19:01:12 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.91] ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id iB8J1BWi026318 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Wed, 8 Dec 2004 11:01:12 -0800 (PST) (envelope-from sam@errno.com) From: Sam Leffler Organization: Errno Consulting To: freebsd-current@freebsd.org Date: Wed, 8 Dec 2004 11:09:43 -0800 User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412081109.43840.sam@errno.com> Subject: HEADSUP: ath updates X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 19:01:13 -0000 I just committed updates for the ath driver and the ath hal. There are many changes to this code including a split of the tx rate control algorithm into a separate module. This means that when statically configuring the driver you now need to specify: device ath device ath_hal device ath_rate_onoe to get the previous functionality (i.e. the previous rate control algorithm). There is a second rate control algorithm that is slightly different from the onoe algorithm; you can try that with device ath_rate_amrr However both of these algorithms are still rather lame and a good algorithm is needed. I encourage folks to step up and work on this as a good tx rate control algorithm makes all the difference. The new hal should support all shipping Atheros parts. Operation should be noticeably better and the driver supports all the functionality of the revised net80211 layer. This includes the security protocols (WPA, 802.11i, 802.1x), the QoS/Multi-media protocols (WME/WMM), and more. One problem to beware of is that WME and WPA currently do not work together (for AP operation at least). If you want to test out WPA be sure to disable wme--this will require the new ifconfig that I'll be committing shortly. There's still a bunch of work to do on the driver. I'll be working fulltime on this stuff for the next few months; mainly on AP support. Sam From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 19:34:18 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 37C0916A4CE for ; Wed, 8 Dec 2004 19:34:18 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8ECE543D3F for ; Wed, 8 Dec 2004 19:34:17 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.91] ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id iB8JYGWi026450 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Wed, 8 Dec 2004 11:34:17 -0800 (PST) (envelope-from sam@errno.com) From: Sam Leffler Organization: Errno Consulting To: freebsd-current@freebsd.org Date: Wed, 8 Dec 2004 11:42:48 -0800 User-Agent: KMail/1.7 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412081142.48494.sam@errno.com> Subject: HEADSUP: ifconfig updated X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 19:34:18 -0000 I just committed a major overhaul of ifconfig. If you see any regression in backwards compatiblity please let me know. I've been running it for a while w/o issues but the command line parsing was completely redone and I didn't test all the possible operations (e.g. ipv6 tunnel stuff). The main visible change is in the handling of 802.11 interface.s You may see many new parameters and there are many new controls for use with the revised net80211 layer and the update ath driver. There are also some experimental commands for listing status for a device that might move to a different program (based on feedback). For example when operating as a station you can list the set of access points found in the last scan with minky# ifconfig ath0 list scan SSID BSSID CHAN RATE S:N INT CAPS TestAP 00:02:6f:01:86:2a 3 11M 24:0 100 E CurryNet1 00:09:5b:9f:0c:52 7 11M 1:0 100 Ec samb 00:03:7f:00:c8:32 11 54M 57:0 100 ES sama 00:03:7f:00:c8:31 60 54M 57:0 100 E When operating as an access point or in adhoc mode you can get a similar listing of the stations/neighbors using "list sta". The default status for an 802.11 device is now a bit more minimal. To get complete status there is a new -v option; for example: minky# ifconfig ath0 ath0: flags=8843 mtu 1500 inet 10.0.0.142 netmask 0xffffff00 broadcast 10.0.0.255 ether 00:03:7f:04:a0:a4 media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/54Mbps) status: associated ssid samb channel 11 bssid 00:03:7f:00:c8:32 authmode OPEN privacy OFF txpowmax 48 protmode CTS wme bintval 100 minky# ifconfig -v ath0 ath0: flags=8843 mtu 1500 inet 10.0.0.142 netmask 0xffffff00 broadcast 10.0.0.255 ether 00:03:7f:04:a0:a4 media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/54Mbps) status: associated ssid samb channel 11 (2462) bssid 00:03:7f:00:c8:32 authmode OPEN privacy OFF deftxkey UNDEF powersavemode OFF powersavesleep 100 txpowmax 48 txpower 60 rtsthreshold 2312 protmode CTS wme roaming AUTO bintval 100 AC_BE cwmin 4 cwmax 10 aifs 3 txopLimit 0 -acm ack cwmin 4 cwmax 10 aifs 3 txopLimit 0 -acm AC_BK cwmin 4 cwmax 10 aifs 7 txopLimit 0 -acm ack cwmin 4 cwmax 10 aifs 7 txopLimit 0 -acm AC_VI cwmin 3 cwmax 4 aifs 2 txopLimit 94 -acm ack cwmin 3 cwmax 4 aifs 2 txopLimit 94 -acm AC_VO cwmin 2 cwmax 3 aifs 2 txopLimit 47 -acm ack cwmin 2 cwmax 3 aifs 2 txopLimit 47 -acm Finally, you can get some device capability-style information. To see the set of available channels a device is capable of using, use "list chan": minky# ifconfig ath0 list chan Channel 1 : 2412 Mhz 11g Channel 48 : 5240 Mhz 11a Channel 2 : 2417 Mhz 11g Channel 50 : 5250 Mhz 11a Turbo Channel 3 : 2422 Mhz 11g Channel 52 : 5260 Mhz 11a Channel 4 : 2427 Mhz 11g Channel 56 : 5280 Mhz 11a Channel 5 : 2432 Mhz 11g Channel 58 : 5290 Mhz 11a Turbo Channel 6 : 2437 Mhz 11g Channel 60 : 5300 Mhz 11a Channel 7 : 2442 Mhz 11g Channel 64 : 5320 Mhz 11a Channel 8 : 2447 Mhz 11g Channel 149 : 5745 Mhz 11a Channel 9 : 2452 Mhz 11g Channel 152 : 5760 Mhz 11a Turbo Channel 10 : 2457 Mhz 11g Channel 153 : 5765 Mhz 11a Channel 11 : 2462 Mhz 11g Channel 157 : 5785 Mhz 11a Channel 36 : 5180 Mhz 11a Channel 160 : 5800 Mhz 11a Turbo Channel 40 : 5200 Mhz 11a Channel 161 : 5805 Mhz 11a Channel 42 : 5210 Mhz 11a Turbo Channel 165 : 5825 Mhz 11a Channel 44 : 5220 Mhz 11a (when a channel is marked with a "*" that means you can only do a passive scan--i.e. you can only listen for an ap and not actively send a probe request frame). Similarly, "list active" will show the set of channels currently enabled for use, taking into account restrictions due to locking the band (e.g with "mode 11a") or through the channel list mechanism. Finally, you can see the set of capabilites an 802.11 driver has specified using "list caps": minky# ifconfig ath0 list caps ath0=783e50f You can also change these so, for example, you can disable hardware crypto support in a driver to test a software implementation. The ifconfig manual page is currently lagging behind the code. I'll be updating it as soon as I have time (volunteers welcome). Sam From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 19:47:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36EC916A4CE for ; Wed, 8 Dec 2004 19:47:03 +0000 (GMT) Received: from alternator.sgh.waw.pl (alternator.sgh.waw.pl [194.145.96.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1D6343D4C for ; Wed, 8 Dec 2004 19:47:02 +0000 (GMT) (envelope-from dry@dry.pl) Received: from localhost (localhost [127.0.0.1]) by alternator.sgh.waw.pl (Postfix) with SMTP id 0DE152AA953 for ; Wed, 8 Dec 2004 20:47:02 +0100 (CET) Received: from prolongator.sgh.waw.pl (prolongator.sgh.waw.pl [194.145.96.30]) by alternator.sgh.waw.pl (Postfix) with ESMTP id 02DD12AA94A for ; Wed, 8 Dec 2004 20:47:02 +0100 (CET) Received: by prolongator.sgh.waw.pl (Postfix, from userid 5250) id B02B440AF; Wed, 8 Dec 2004 20:47:21 +0100 (CET) Date: Wed, 8 Dec 2004 20:47:21 +0100 From: Michal Suszko To: current@freebsd.org Message-ID: <20041208194721.GB1571@dry.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: deadlocks in recent 6-CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 19:47:03 -0000 Since switching to PF (few weeks ago) I'm frequently experiencing deadlocks. breaking to DDB works, and ps shows lock in PF, like here: 43273 c1ee57e0 1001 42753 43273 0004002 [LOCK pf task mtx c1c45040] dia Setting debug.mpsafenet to 0 helps a little (system runs without deadlock for few days) but doesn't eliminate it. PREEMPTION is on WITNESS show two kinds of LOR's: 1st 0xc1888414 inp (tcpinp) @ /usr/src/sys/netinet/tcp_syncache.c:1086 2nd 0xc06b9400 pf task mtx (pf task mtx) @ /usr/src/sys/contrib/pf/net/pf.c:5891 KDB: stack backtrace: witness_checkorder(c06b9400,9,c0668a25,1703,7) at witness_checkorder+0x388 _mtx_lock_flags(c06b9400,0,c0668a25,1703,cbc9c8f8) at _mtx_lock_flags+0x37 pf_test(2,c15ce000,cbc9ca08,c1888384,c163cba0) at pf_test+0x72 pf_check_out(0,cbc9ca08,c15ce000,2,c1888384) at pf_check_out+0x4e pfil_run_hooks(c06eafe0,cbc9ca94,c15ce000,2,c1888384) at pfil_run_hooks+0x145 ip_output(c16bad00,0,cbc9ca60,0,0) at ip_output+0x299 syncache_respond(cbc9cb20,c06eba40,1c,8,78) at syncache_respond+0x26a syncache_add(cbc9cbac,cbc9cbfc,c17a8034,cbc9cba8,c1773b00) at syncache_add+0x428 tcp_input(c1773b00,14,c15ce000,1,0) at tcp_input+0x1a87 ip_input(c1773b00,0,c06797c5,e8,18) at ip_input+0xd5 netisr_processqueue(cbc9ccdc,80246,c06bf1a0,8,c14f3c40) at netisr_processqueue+0x15 swi_net(0,0,c0670763,257,0) at swi_net+0x9f ithread_loop(c14fa500,cbc9cd48,c06705b6,318,c14fa500) at ithread_loop+0x1d2 fork_exit(c04d53e0,c14fa500,cbc9cd48) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xcbc9cd7c, ebp = 0 --- 1st 0xc06eb44c tcp (tcp) @ /usr/src/sys/netinet/tcp_input.c:615 2nd 0xc06b9400 pf task mtx (pf task mtx) @ /usr/src/sys/contrib/pf/net/pf.c:5891 KDB: stack backtrace: witness_checkorder(c06b9400,9,c0668a25,1703,0) at witness_checkorder+0x388 _mtx_lock_flags(c06b9400,0,c0668a25,1703,c04e1dc9) at _mtx_lock_flags+0x37 pf_test(2,c16cf014,cbc9ca7c,0,c163cba0) at pf_test+0x72 pf_check_out(0,cbc9ca7c,c16cf014,2,0) at pf_check_out+0x4e pfil_run_hooks(c06eafe0,cbc9cb08,c16cf014,2,0) at pfil_run_hooks+0x145 ip_output(c16b6a00,0,cbc9cad4,0,0,0,0,0,c06a495c,c8) at ip_output+0x299 tcp_respond(0,c16b6a34,c16b6a48,c16b6a00,e5623f88) at tcp_respond+0x16e tcp_input(c16b6a00,14,c16cf014,1,0) at tcp_input+0x91e ip_input(c16b6a00,0,c06797c5,e8,18) at ip_input+0xd5 netisr_processqueue(cbc9ccdc,80246,c06bf1a0,8,c14f3c40) at netisr_processqueue+0x15 swi_net(0,0,c0670763,257,0) at swi_net+0x9f ithread_loop(c14fa500,cbc9cd48,c06705b6,318,c14fa500) at ithread_loop+0x1d2 fork_exit(c04d53e0,c14fa500,cbc9cd48) at fork_exit+0x70 fork_trampoline() at fork_trampoline+0x8 I can provide core dump along with kernel.debug and configuration files. Michal From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 19:48:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C88FD16A4CE; Wed, 8 Dec 2004 19:48:28 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D64243D31; Wed, 8 Dec 2004 19:48:28 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id iB8JmQRn013233; Wed, 8 Dec 2004 14:48:26 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.1/8.13.1) with ESMTP id iB8JmPHJ015569; Wed, 8 Dec 2004 14:48:25 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 47C5D7306E; Wed, 8 Dec 2004 14:48:26 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041208194826.47C5D7306E@freebsd-current.sentex.ca> Date: Wed, 8 Dec 2004 14:48:26 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/621/Tue Dec 7 07:55:16 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Status: Clean Subject: [current tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 19:48:29 -0000 TB --- 2004-12-08 18:16:37 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-12-08 18:16:37 - starting CURRENT tinderbox run for sparc64/sparc64 TB --- 2004-12-08 18:16:37 - checking out the source tree TB --- 2004-12-08 18:16:37 - cd /home/tinderbox/CURRENT/sparc64/sparc64 TB --- 2004-12-08 18:16:37 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-12-08 18:23:05 - building world (CFLAGS=-O2 -pipe) TB --- 2004-12-08 18:23:05 - cd /home/tinderbox/CURRENT/sparc64/sparc64/src TB --- 2004-12-08 18:23:05 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-12-08 19:28:52 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-12-08 19:28:52 - cd /home/tinderbox/CURRENT/sparc64/sparc64/src TB --- 2004-12-08 19:28:52 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Wed Dec 8 19:28:52 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Wed Dec 8 19:40:31 UTC 2004 TB --- 2004-12-08 19:40:31 - generating LINT kernel config TB --- 2004-12-08 19:40:31 - cd /home/tinderbox/CURRENT/sparc64/sparc64/src/sys/sparc64/conf TB --- 2004-12-08 19:40:31 - /usr/bin/make -B LINT TB --- 2004-12-08 19:40:31 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-12-08 19:40:31 - cd /home/tinderbox/CURRENT/sparc64/sparc64/src TB --- 2004-12-08 19:40:31 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Wed Dec 8 19:40:31 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/altq -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/pf -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /tinderbox/CURRENT/sparc64/sparc64/src/sys/net/zlib.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/altq -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/pf -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /tinderbox/CURRENT/sparc64/sparc64/src/sys/net80211/ieee80211.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/altq -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/pf -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /tinderbox/CURRENT/sparc64/sparc64/src/sys/net80211/ieee80211_crypto.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/altq -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/pf -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /tinderbox/CURRENT/sparc64/sparc64/src/sys/net80211/ieee80211_crypto_none.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/tinderbox/CURRENT/sparc64/sparc64/src/sys -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/acpica -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/altq -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ipfilter -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/pf -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/dev/ath/freebsd -I/tinderbox/CURRENT/sparc64/sparc64/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /tinderbox/CURRENT/sparc64/sparc64/src/sys/net80211/ieee80211_freebsd.c /tinderbox/CURRENT/sparc64/sparc64/src/sys/net80211/ieee80211_freebsd.c: In function `ieee80211_notify_replay_failure': /tinderbox/CURRENT/sparc64/sparc64/src/sys/net80211/ieee80211_freebsd.c:260: warning: long long unsigned int format, u_int64_t arg (arg 4) /tinderbox/CURRENT/sparc64/sparc64/src/sys/net80211/ieee80211_freebsd.c:260: warning: long long unsigned int format, u_int64_t arg (arg 5) *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/obj/sparc64/tinderbox/CURRENT/sparc64/sparc64/src/sys/LINT. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src. *** Error code 1 Stop in /tinderbox/CURRENT/sparc64/sparc64/src. TB --- 2004-12-08 19:48:26 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-12-08 19:48:26 - ERROR: failed to build lint kernel TB --- 2004-12-08 19:48:26 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 19:53:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD4F216A4CE for ; Wed, 8 Dec 2004 19:53:36 +0000 (GMT) Received: from smtpauth.kewlio.net (smtpauth.kewlio.net [195.22.134.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3551943D5C for ; Wed, 8 Dec 2004 19:53:36 +0000 (GMT) (envelope-from tlp@LiquidX.org) Received: from maya.liquidx.org (70-56-157-27.bois.qwest.net [70.56.157.27]) (authenticated bits=0) by smtpauth.kewlio.net (8.12.10/8.12.10) with ESMTP id iB8JrW90005940 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Dec 2004 19:53:34 GMT Date: Wed, 8 Dec 2004 12:53:37 -0700 From: Travis Poppe To: Stefan Ehmann Message-ID: <20041208125337.3882898a@maya.liquidx.org> In-Reply-To: <1102506431.1090.8.camel@taxman> References: <20041207234840.7287cdf4@maya.liquidx.org> <1102506431.1090.8.camel@taxman> X-Mailer: Sylpheed-Claws 0.9.12b (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: FreeBSD sound distortion problems with SB Live! fixed with PREEMPTION X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 19:53:36 -0000 On Wed, 08 Dec 2004 12:47:11 +0100 Stefan Ehmann wrote: > On Tue, 2004-12-07 at 23:48 -0700, Travis Poppe wrote: > ... > > To my amazement, it worked completely. Enabling PREEMPTION in the > > kernel completely "fixes" this problem to the fullest extent. I have > > not been able to reproduce the problem since using any of the > > methods described above. > > > > I'm hoping that with this new information someone might be able to > > figure out what is truly causing this problem and can come up with a > > solution (or is PREEMPTION a good solution?). It seems that only a > > handful of drivers (emu10k1 is the one I'm having problems with) > > have this problem. For the record, I am not the only one who has > > reported this problem to the lists. > > I also experience the same problems with sound you've described. > > As PREEMPTION seems to stable for you, I tried to turn it on again. > > Unfortunately PREEMPTION remains to be completely unusable for me. The > system freezes within 5 minutes. > > The problem is described here: > http://lists.freebsd.org/pipermail/freebsd-current/2004-September/037949.html This is the first time I've ever used PREEMPTION and have so far experienced zero problems with it. However, I've been using it for less than 24 hours. -Travis Poppe From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 20:05:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8DE9216A4CE; Wed, 8 Dec 2004 20:05:57 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0E2943D53; Wed, 8 Dec 2004 20:05:56 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB8K5sDh093683; Wed, 8 Dec 2004 22:05:54 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 51291-07; Wed, 8 Dec 2004 22:05:53 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB8K5rkm093680 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 8 Dec 2004 22:05:53 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iB8K5rNl001489; Wed, 8 Dec 2004 22:05:53 +0200 (EET) (envelope-from ru) Date: Wed, 8 Dec 2004 22:05:53 +0200 From: Ruslan Ermilov To: Poul-Henning Kamp Message-ID: <20041208200553.GB1340@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ftEhullJWpWg/VHq" Content-Disposition: inline User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: current@FreeBSD.org Subject: mount oddities X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 20:05:57 -0000 --ftEhullJWpWg/VHq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Poul-Henning, I first noticed this oddity with MS-DOS formatted floppies, when no matter what floppy I insert into the drive later, it's still treated as MS-DOS. I believe the testcase below is related to the problem I'm seeing. dd if=3D/dev/zero of=3Dimage bs=3D1k count=3D1440 mdconfig -a -t vnode -f image -u 0 mount /dev/md0 /mnt newfs /dev/md0 mount /dev/md0 /mnt && umount /mnt mdconfig -du0 mdconfig -a -t vnode -f image -u 0 mount /dev/md0 /mnt umount /mnt mdconfig -du0 The second "mount" command should succeed but it doesn't. Note that if you remove the first "mount" command, the second one succeeds. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --ftEhullJWpWg/VHq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBt16gqRfpzJluFF4RAh8bAJ0cSjubWcK9lTAkCo03ZG4s/4LJ6gCgmXwA aagYDX4qi4RAGiI2i21YCAQ= =MzUk -----END PGP SIGNATURE----- --ftEhullJWpWg/VHq-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 20:33:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1615E16A4CE for ; Wed, 8 Dec 2004 20:33:43 +0000 (GMT) Received: from blank.neverwhere.org (blank.neverwhere.org [66.135.33.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDC6943D2D for ; Wed, 8 Dec 2004 20:33:42 +0000 (GMT) (envelope-from jolly@blank.neverwhere.org) Received: from blank.neverwhere.org (localhost.localdomain [127.0.0.1]) by blank.neverwhere.org (8.12.10/8.12.10) with ESMTP id iB8KbSVD020902 for ; Wed, 8 Dec 2004 15:37:28 -0500 Received: (from jolly@localhost) by blank.neverwhere.org (8.12.10/8.12.10/Submit) id iB8KbS27020900 for current@freebsd.org; Wed, 8 Dec 2004 15:37:28 -0500 Date: Wed, 8 Dec 2004 15:37:28 -0500 From: Jacob Frelinger To: current@freebsd.org Message-ID: <20041208203728.GB17576@thecoffinclub.com> Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4SFOXa2GPu3tIq4H" Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: writing usb quirk entries and determining revision numbers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 20:33:43 -0000 --4SFOXa2GPu3tIq4H Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I've managed to get the data cable for my samsung n400 cell phone working with the umodem driver, but it requires a quirk entry in usb_quirks.c (setting UQ_ASSUME_CM_OVER_DATA). I'm planning on submiting a PR for this, but I don't know how to determine the version number for the quirk entry (currently I have it set to ANY like most the other acm modems in usb_quirks.c). How do I determine what the version number is? --=20 Jacob "I'm Brainy For Zombie Pops" Frelinger=20 Jolly at TheCoffinClub dot Com=20 http://www.thecoffinclub.com=20 --4SFOXa2GPu3tIq4H Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFBt2YIO887GYmMIQIRAltMAKDk0fUEPHhc8xzJgcOf8JrUMclACACfeqaE Nt6jv25zEmp3q6fseHNrjQ0= =Um4n -----END PGP SIGNATURE----- --4SFOXa2GPu3tIq4H-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 20:36:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1ACF716A4CE for ; Wed, 8 Dec 2004 20:36:00 +0000 (GMT) Received: from cicero0.cybercity.dk (cicero0.cybercity.dk [212.242.40.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3752D43D5C for ; Wed, 8 Dec 2004 20:35:59 +0000 (GMT) (envelope-from tom@motd.dk) Received: from bart.motd.dk (port95.ds1-ro.adsl.cybercity.dk [212.242.60.98]) by cicero0.cybercity.dk (Postfix) with ESMTP id B30772B33D; Wed, 8 Dec 2004 21:35:55 +0100 (CET) Received: from localhost (localhost.motd.dk [127.0.0.1]) by bart.motd.dk (Postfix) with ESMTP id DF3DF630D; Wed, 8 Dec 2004 21:34:14 +0100 (CET) Received: from bart.motd.dk ([127.0.0.1]) by localhost (bart.motd.dk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 56658-02; Wed, 8 Dec 2004 21:34:13 +0100 (CET) Received: from home03 (unknown [192.168.10.3]) by bart.motd.dk (Postfix) with ESMTP id 5FB1A62DF; Wed, 8 Dec 2004 21:34:13 +0100 (CET) From: "Tom Jensen" To: "'Sam Leffler'" Date: Wed, 8 Dec 2004 21:36:16 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <200412081142.48494.sam@errno.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Thread-Index: AcTdXL9VNw4vt1aPQJSoYnAEn401FQAB3aqg Message-Id: <20041208203413.5FB1A62DF@bart.motd.dk> X-Virus-Scanned: by amavisd-new at motd.dk cc: freebsd-current@freebsd.org Subject: RE: HEADSUP: ifconfig updated X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 20:36:00 -0000 Any chances that these updates (ifconfig, ath, net80211) could be applied/working with the 5.3 sources? - T -----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Sam Leffler Sent: 8. december 2004 20:43 To: freebsd-current@freebsd.org Subject: HEADSUP: ifconfig updated I just committed a major overhaul of ifconfig. If you see any regression in backwards compatiblity please let me know. I've been running it for a while w/o issues but the command line parsing was completely redone and I didn't test all the possible operations (e.g. ipv6 tunnel stuff). The main visible change is in the handling of 802.11 interface.s You may see many new parameters and there are many new controls for use with the revised net80211 layer and the update ath driver. There are also some experimental commands for listing status for a device that might move to a different program (based on feedback). For example when operating as a station you can list the set of access points found in the last scan with minky# ifconfig ath0 list scan SSID BSSID CHAN RATE S:N INT CAPS TestAP 00:02:6f:01:86:2a 3 11M 24:0 100 E CurryNet1 00:09:5b:9f:0c:52 7 11M 1:0 100 Ec samb 00:03:7f:00:c8:32 11 54M 57:0 100 ES sama 00:03:7f:00:c8:31 60 54M 57:0 100 E When operating as an access point or in adhoc mode you can get a similar listing of the stations/neighbors using "list sta". The default status for an 802.11 device is now a bit more minimal. To get complete status there is a new -v option; for example: minky# ifconfig ath0 ath0: flags=8843 mtu 1500 inet 10.0.0.142 netmask 0xffffff00 broadcast 10.0.0.255 ether 00:03:7f:04:a0:a4 media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/54Mbps) status: associated ssid samb channel 11 bssid 00:03:7f:00:c8:32 authmode OPEN privacy OFF txpowmax 48 protmode CTS wme bintval 100 minky# ifconfig -v ath0 ath0: flags=8843 mtu 1500 inet 10.0.0.142 netmask 0xffffff00 broadcast 10.0.0.255 ether 00:03:7f:04:a0:a4 media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/54Mbps) status: associated ssid samb channel 11 (2462) bssid 00:03:7f:00:c8:32 authmode OPEN privacy OFF deftxkey UNDEF powersavemode OFF powersavesleep 100 txpowmax 48 txpower 60 rtsthreshold 2312 protmode CTS wme roaming AUTO bintval 100 AC_BE cwmin 4 cwmax 10 aifs 3 txopLimit 0 -acm ack cwmin 4 cwmax 10 aifs 3 txopLimit 0 -acm AC_BK cwmin 4 cwmax 10 aifs 7 txopLimit 0 -acm ack cwmin 4 cwmax 10 aifs 7 txopLimit 0 -acm AC_VI cwmin 3 cwmax 4 aifs 2 txopLimit 94 -acm ack cwmin 3 cwmax 4 aifs 2 txopLimit 94 -acm AC_VO cwmin 2 cwmax 3 aifs 2 txopLimit 47 -acm ack cwmin 2 cwmax 3 aifs 2 txopLimit 47 -acm Finally, you can get some device capability-style information. To see the set of available channels a device is capable of using, use "list chan": minky# ifconfig ath0 list chan Channel 1 : 2412 Mhz 11g Channel 48 : 5240 Mhz 11a Channel 2 : 2417 Mhz 11g Channel 50 : 5250 Mhz 11a Turbo Channel 3 : 2422 Mhz 11g Channel 52 : 5260 Mhz 11a Channel 4 : 2427 Mhz 11g Channel 56 : 5280 Mhz 11a Channel 5 : 2432 Mhz 11g Channel 58 : 5290 Mhz 11a Turbo Channel 6 : 2437 Mhz 11g Channel 60 : 5300 Mhz 11a Channel 7 : 2442 Mhz 11g Channel 64 : 5320 Mhz 11a Channel 8 : 2447 Mhz 11g Channel 149 : 5745 Mhz 11a Channel 9 : 2452 Mhz 11g Channel 152 : 5760 Mhz 11a Turbo Channel 10 : 2457 Mhz 11g Channel 153 : 5765 Mhz 11a Channel 11 : 2462 Mhz 11g Channel 157 : 5785 Mhz 11a Channel 36 : 5180 Mhz 11a Channel 160 : 5800 Mhz 11a Turbo Channel 40 : 5200 Mhz 11a Channel 161 : 5805 Mhz 11a Channel 42 : 5210 Mhz 11a Turbo Channel 165 : 5825 Mhz 11a Channel 44 : 5220 Mhz 11a (when a channel is marked with a "*" that means you can only do a passive scan--i.e. you can only listen for an ap and not actively send a probe request frame). Similarly, "list active" will show the set of channels currently enabled for use, taking into account restrictions due to locking the band (e.g with "mode 11a") or through the channel list mechanism. Finally, you can see the set of capabilites an 802.11 driver has specified using "list caps": minky# ifconfig ath0 list caps ath0=783e50f You can also change these so, for example, you can disable hardware crypto support in a driver to test a software implementation. The ifconfig manual page is currently lagging behind the code. I'll be updating it as soon as I have time (volunteers welcome). Sam _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 20:39:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D13C16A4CE for ; Wed, 8 Dec 2004 20:39:07 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id E399A43D1D for ; Wed, 8 Dec 2004 20:39:06 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.91] ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id iB8Kd4Wi026867 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 8 Dec 2004 12:39:06 -0800 (PST) (envelope-from sam@errno.com) From: Sam Leffler Organization: Errno Consulting To: freebsd-current@freebsd.org Date: Wed, 8 Dec 2004 12:47:35 -0800 User-Agent: KMail/1.7 References: <20041208203413.5FB1A62DF@bart.motd.dk> In-Reply-To: <20041208203413.5FB1A62DF@bart.motd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412081247.36272.sam@errno.com> cc: Tom Jensen Subject: Re: HEADSUP: ifconfig updated X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 20:39:07 -0000 On Wednesday 08 December 2004 12:36 pm, Tom Jensen wrote: > Any chances that these updates (ifconfig, ath, net80211) could be > applied/working with the 5.3 sources? There's no reason someone couldn't create a patch set for 5.3, but it would take a lot of work (and it ain't going to be me). As to committing the changes to 5-stable that will not happen as they break driver API's. Sam From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 22:53:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02DB616A4CF for ; Wed, 8 Dec 2004 22:53:22 +0000 (GMT) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A83143D53 for ; Wed, 8 Dec 2004 22:53:21 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) iB8MrJwN071552; Wed, 8 Dec 2004 14:53:19 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (fa0-1-wlan-rtr.corp.yahoo.com [216.145.49.5]) by mail.meer.net (8.12.10/8.12.10/meer) with ESMTP id iB8Mr52X020677; Wed, 8 Dec 2004 14:53:05 -0800 (PST) (envelope-from gnn@neville-neil.com) Date: Wed, 08 Dec 2004 14:53:00 -0800 Message-ID: From: gnn@freebsd.org To: Sam Leffler In-Reply-To: <200412081142.48494.sam@errno.com> References: <200412081142.48494.sam@errno.com> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.5 Emacs/21.2 (powerpc-apple-darwin) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: HEADSUP: ifconfig updated X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 22:53:22 -0000 At Wed, 8 Dec 2004 11:42:48 -0800, sam wrote: > > I just committed a major overhaul of ifconfig. Cool! Thanks. Later, George From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 23:28:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00CC516A4CE for ; Wed, 8 Dec 2004 23:28:45 +0000 (GMT) Received: from hq.sectorb.msk.ru (petaflop.b.gz.ru [217.67.124.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC59143D68 for ; Wed, 8 Dec 2004 23:28:43 +0000 (GMT) (envelope-from chinhngt@sectorb.msk.ru) Received: from unix.local (unix.local [172.16.12.120]) by hq.sectorb.msk.ru (Postfix) with ESMTP id CDC5F2DBB for ; Thu, 9 Dec 2004 02:28:40 +0300 (MSK) Date: Thu, 9 Dec 2004 02:28:41 +0300 (MSK) From: Nguyen Tam Chinh X-X-Sender: chinhngt@unix.local To: current@freebsd.org Message-ID: <20041209022545.G96955@unix.local> Keywords: 216091683 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: [fsck -B problem] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 23:28:45 -0000 Hi all, The system is 6.0-CURRENT (cvsup 09/12), ------------- unix# fsck -B Can't stat /home/.snap/fsck_snapshot: No such file or directory Can't stat /root/.snap/fsck_snapshot: No such file or directory Can't stat /tmp/.snap/fsck_snapshot: No such file or directory Can't stat /usr/.snap/fsck_snapshot: No such file or directory Can't stat /var/.snap/fsck_snapshot: No such file or directory ------------ What could be the problem here? what is fsck_snapshot using for? ----- With best regards, | The Power to Serve Nguyen Tam Chinh | http://www.FreeBSD.org Loc: sp.cs.msu.ru | http://chinhngt.svmgu.com | http://www.gnu.org/copyleft/copyleft.html From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 23:32:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B5DC16A4CE for ; Wed, 8 Dec 2004 23:32:48 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79D1D43D55 for ; Wed, 8 Dec 2004 23:32:47 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iB8NWh22028336; Thu, 9 Dec 2004 00:32:43 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Nguyen Tam Chinh From: "Poul-Henning Kamp" In-Reply-To: Your message of "Thu, 09 Dec 2004 02:28:41 +0300." <20041209022545.G96955@unix.local> Date: Thu, 09 Dec 2004 00:32:43 +0100 Message-ID: <28335.1102548763@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@freebsd.org Subject: Re: [fsck -B problem] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 23:32:48 -0000 In message <20041209022545.G96955@unix.local>, Nguyen Tam Chinh writes: >Hi all, >The system is 6.0-CURRENT (cvsup 09/12), >------------- >unix# fsck -B >Can't stat /home/.snap/fsck_snapshot: No such file or directory >Can't stat /root/.snap/fsck_snapshot: No such file or directory >Can't stat /tmp/.snap/fsck_snapshot: No such file or directory >Can't stat /usr/.snap/fsck_snapshot: No such file or directory >Can't stat /var/.snap/fsck_snapshot: No such file or directory >------------ >What could be the problem here? >what is fsck_snapshot using for? I belive I fixed this earlier today. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 23:50:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 57FB516A550 for ; Wed, 8 Dec 2004 23:50:27 +0000 (GMT) Received: from hq.sectorb.msk.ru (petaflop.b.gz.ru [217.67.124.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4080A43D31 for ; Wed, 8 Dec 2004 23:50:21 +0000 (GMT) (envelope-from chinhngt@sectorb.msk.ru) Received: from unix.local (unix.local [172.16.12.120]) by hq.sectorb.msk.ru (Postfix) with ESMTP id F39021F74; Thu, 9 Dec 2004 02:50:18 +0300 (MSK) Date: Thu, 9 Dec 2004 02:50:19 +0300 (MSK) From: Nguyen Tam Chinh X-X-Sender: chinhngt@unix.local To: Poul-Henning Kamp In-Reply-To: <28335.1102548763@critter.freebsd.dk> Message-ID: <20041209024624.E95734@unix.local> References: <28335.1102548763@critter.freebsd.dk> Keywords: 216091683 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: current@freebsd.org Subject: Re: [fsck -B problem] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 23:50:29 -0000 On Thu, 9 Dec 2004, Poul-Henning Kamp wrote: > In message <20041209022545.G96955@unix.local>, Nguyen Tam Chinh writes: >> Hi all, >> The system is 6.0-CURRENT (cvsup 09/12), >> ------------- >> unix# fsck -B >> Can't stat /home/.snap/fsck_snapshot: No such file or directory >> Can't stat /root/.snap/fsck_snapshot: No such file or directory >> Can't stat /tmp/.snap/fsck_snapshot: No such file or directory >> Can't stat /usr/.snap/fsck_snapshot: No such file or directory >> Can't stat /var/.snap/fsck_snapshot: No such file or directory >> ------------ >> What could be the problem here? >> what is fsck_snapshot using for? > > I belive I fixed this earlier today. > OK. I'm cvsuping again (already get your commit). The build process will take some hours. ----- With best regards, | The Power to Serve Nguyen Tam Chinh | http://www.FreeBSD.org Loc: sp.cs.msu.ru | http://chinhngt.svmgu.com | http://www.gnu.org/copyleft/copyleft.html From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 00:01:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 731C716A4CE for ; Thu, 9 Dec 2004 00:01:49 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FBE543D66 for ; Thu, 9 Dec 2004 00:01:49 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iB901mbZ005693 for ; Wed, 8 Dec 2004 16:01:48 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iB901mik005692 for freebsd-current@freebsd.org; Wed, 8 Dec 2004 16:01:48 -0800 (PST) (envelope-from sgk) Date: Wed, 8 Dec 2004 16:01:48 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Message-ID: <20041209000148.GA4674@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 Subject: make(1) is broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 00:01:49 -0000 Well, it appears that -current is highly unstable at the moment. In particularly, INET6 is causing a panic, so I went to build a new kernel without it. I'm now stuck with a broken make(1). make buildkernel yields make -V SFILES | MKDEP_CPP="cc -E" xargs mkdep -a -f .newdep -x assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding rm -f .depend mv .newdep .depend *** Signal 11 Stop in /data/obj/usr/src/sys/SPEW. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. troutmask:root[203] tail -1 /var/log/messages Dec 8 15:58:39 troutmask kernel: pid 4794 (make), uid 0: exited on signal 11 troutmask:root[204] uname -a FreeBSD troutmask.apl.washington.edu 6.0-CURRENT FreeBSD 6.0-CURRENT #1: Mon Dec 6 15:56:39 PST 2004 kargl@dhcp-78-96.apl.washington.edu:/data/obj/usr/src/sys/SPEW amd64 -- Steve From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 00:07:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CABED16A4CE for ; Thu, 9 Dec 2004 00:07:10 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94AF043D5D for ; Thu, 9 Dec 2004 00:07:10 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iB907Aku006936 for ; Wed, 8 Dec 2004 16:07:10 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iB907Agw006935 for freebsd-current@freebsd.org; Wed, 8 Dec 2004 16:07:10 -0800 (PST) (envelope-from sgk) Date: Wed, 8 Dec 2004 16:07:10 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Message-ID: <20041209000710.GB4674@troutmask.apl.washington.edu> References: <20041209000148.GA4674@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041209000148.GA4674@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.2.1i Subject: Re: make(1) is broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 00:07:10 -0000 On Wed, Dec 08, 2004 at 04:01:48PM -0800, Steve Kargl wrote: > Well, it appears that -current is highly unstable at > the moment. In particularly, INET6 is causing a > panic, so I went to build a new kernel without it. I'm > now stuck with a broken make(1). > > make buildkernel yields > > make -V SFILES | MKDEP_CPP="cc -E" xargs mkdep -a -f .newdep -x assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding > rm -f .depend > mv .newdep .depend > *** Signal 11 > > Stop in /data/obj/usr/src/sys/SPEW. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > troutmask:root[203] tail -1 /var/log/messages > Dec 8 15:58:39 troutmask kernel: pid 4794 (make), uid 0: exited on signal 11 > > > troutmask:root[204] uname -a > FreeBSD troutmask.apl.washington.edu 6.0-CURRENT FreeBSD 6.0-CURRENT #1: > Mon Dec 6 15:56:39 PST 2004 > kargl@dhcp-78-96.apl.washington.edu:/data/obj/usr/src/sys/SPEW amd64 > troutmask:root[225] find /usr/obj/ -name make.core /usr/obj/usr/src/sys/SPEW/make.core troutmask:root[226] gdb /usr/bin/make /usr/obj/usr/src/sys/SPEW/make.core #0 Lst_Remove (list=0x5580a0, ln=0x0) at /usr/src/usr.bin/make/lst.lib/lstRemove.c:74 74 if (ln->nextPtr != NULL) (gdb) bt #0 Lst_Remove (list=0x5580a0, ln=0x0) at /usr/src/usr.bin/make/lst.lib/lstRemove.c:74 #1 0x00000000004052bb in Dir_Destroy (pp=0x81e780) at /usr/src/usr.bin/make/dir.c:1143 #2 0x0000000000405300 in Dir_ClearPath (path=0x5580a0) at /usr/src/usr.bin/make/dir.c:1172 #3 0x0000000000404283 in Dir_End () at /usr/src/usr.bin/make/dir.c:265 #4 0x000000000040a8da in main (argc=2, argv=0x7fffffffe3e0) at /usr/src/usr.bin/make/main.c:888 -- Steve From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 00:17:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2FE7216A4CE for ; Thu, 9 Dec 2004 00:17:38 +0000 (GMT) Received: from ns1.xcllnt.net (209-128-86-226.BAYAREA.NET [209.128.86.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB38E43D39 for ; Thu, 9 Dec 2004 00:17:37 +0000 (GMT) (envelope-from marcel@xcllnt.net) Received: from ns1.xcllnt.net (localhost [127.0.0.1]) by ns1.xcllnt.net (8.13.1/8.13.1) with ESMTP id iB90HaRG008896; Wed, 8 Dec 2004 16:17:37 -0800 (PST) (envelope-from marcel@ns1.xcllnt.net) Received: (from marcel@localhost) by ns1.xcllnt.net (8.13.1/8.13.1/Submit) id iB90HamM008895; Wed, 8 Dec 2004 16:17:36 -0800 (PST) (envelope-from marcel) Date: Wed, 8 Dec 2004 16:17:35 -0800 From: Marcel Moolenaar To: Poul-Henning Kamp Message-ID: <20041209001735.GA8756@ns1.xcllnt.net> References: <9EF07AD4-48D0-11D9-BD23-000D93C47836@xcllnt.net> <20121.1102495691@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20121.1102495691@critter.freebsd.dk> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: msdosfs borked X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 00:17:38 -0000 On Wed, Dec 08, 2004 at 09:48:11AM +0100, Poul-Henning Kamp wrote: > In message <9EF07AD4-48D0-11D9-BD23-000D93C47836@xcllnt.net>, Marcel Moolenaar > writes: > >Permissions seems to have gone out to lunch... > > Hmm, do you know what kind of filesystem it is ? FAT12/FAT16/FAT32 ? FAT16: pluto2# hexdump -C sec0 00000000 eb 3c 90 42 53 44 20 20 34 2e 34 00 02 08 01 00 |.<.BSD 4.4.....| 00000010 02 00 02 00 00 f0 c4 00 3f 00 ff 00 00 00 00 00 |........?.......| 00000020 9a 20 06 00 00 00 29 fe 19 4d 48 4e 4f 20 4e 41 |. ....)..MHNO NA| 00000030 4d 45 20 20 20 20 46 41 54 31 36 20 20 20 fa 31 |ME FAT16 .1| 00000040 c0 8e d0 bc 00 7c fb 8e d8 e8 00 00 5e 83 c6 19 |.....|......^...| 00000050 bb 07 00 fc ac 84 c0 74 06 b4 0e cd 10 eb f5 30 |.......t.......0| 00000060 e4 cd 16 cd 19 0d 0a 4e 6f 6e 2d 73 79 73 74 65 |.......Non-syste| 00000070 6d 20 64 69 73 6b 0d 0a 50 72 65 73 73 20 61 6e |m disk..Press an| 00000080 79 20 6b 65 79 20 74 6f 20 72 65 62 6f 6f 74 0d |y key to reboot.| 00000090 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 000000a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.| This may or may not be related, but I get a bunch of weird output when booting: : Waiting 2 seconds for SCSI devices to settle da0 at mpt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 34732MB (71132960 512 byte sectors: 255H 63S/T 4427C) kern_symlink = 0 Trying to mount root from ufs:/dev/da0p2 kernel_vmount = 0 WARNING: preposterous time in filesystem -- CHECK AND RESET THE DATE! Pre-seeding PRNG: kickstart. Loading configuration files. Entropy harvesting: interrupts ethernet point_to_point kickstart. swapon: adding /dev/da0p3 as swap device Starting file system checks: /dev/da0p2: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0p2: clean, 102747 free (587 frags, 12770 blocks, 0.5% fragmentation) /dev/da0p4: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0p4: clean, 322464 free (8664 frags, 39225 blocks, 0.9% fragmentation) /dev/da0p5: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0p5: clean, 114386 free (1186 frags, 14150 blocks, 0.9% fragmentation) /dev/da0p6: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0p6: clean, 126835 free (19 frags, 15852 blocks, 0.0% fragmentation) /dev/da0p7: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/da0p7: clean, 8100895 free (166671 frags, 991778 blocks, 1.2% fragmentation) /dev/da0p1: FILESYSTEM CLEAN; SKIPPING CHECKS Setting hostname: pluto2.freebsd.org. : Dec 9 00:08:17 pluto2 syslogd: kernel boot file is /boot/kernel/kernel Setting date via ntp. 9 Dec 00:08:23 ntpdate[278]: step time server 216.136.204.18 offset 0.578687 sec Starting rpcbind. : Starting mountd. Dec 9 00:08:23 pluto2 mountd[365]: can't delete exports for /efi: Bad address Starting nfsd. : The weird messages being: o kern_symlink = 0 o kernel_vmount = 0 o WARNING: preposterous time in filesystem -- CHECK AND RESET THE DATE! o ... mountd[365]: can't delete exports for /efi: Bad address I don't know what to think of the first two, but the last two shouldn't be there. And even after a reboot the /efi mount point is without permissions. I'll sync and rebuild. Maybe I just got a bad mix (kernel & mount)... -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 00:23:04 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 683C216A4CE for ; Thu, 9 Dec 2004 00:23:04 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F04943D3F for ; Thu, 9 Dec 2004 00:23:04 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iB90N3mR007265 for ; Wed, 8 Dec 2004 16:23:03 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iB90N3C2007264 for freebsd-current@freebsd.org; Wed, 8 Dec 2004 16:23:03 -0800 (PST) (envelope-from sgk) Date: Wed, 8 Dec 2004 16:23:03 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Message-ID: <20041209002303.GC4674@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 Subject: panic: mtx_lock() of spin mutex ... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 00:23:04 -0000 panic: mtx_lock() of spin mutex (null) @ sys/netinet/frag6.c:682 cpuid = 0 kdb_backtrace+0x37 panic+0x1d1 _mtx_lock_flags+0x72 frag6_slowtimo+0x26 pfslowtimo+0x5a softclock+0x1c0 ithread_loop+0x179 fork_exit+0xe9 fork_trampoline+0xe This is FreeBSD/amd64 from today's sources of about 30 minutes ago. -- Steve From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 00:24:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BF9316A4CE for ; Thu, 9 Dec 2004 00:24:31 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20E5843D3F for ; Thu, 9 Dec 2004 00:24:31 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id iB90OUa18988 for freebsd-current@freebsd.org; Wed, 8 Dec 2004 16:24:30 -0800 (PST) Date: Wed, 8 Dec 2004 16:24:30 -0800 From: Mike Hunter To: freebsd-current@freebsd.org Message-ID: <20041209002430.GA18622@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: coredump while trying to build world (2004.12.08.1600-0800 src) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 00:24:31 -0000 Hi, I'm trying to go from RELENG_5 to HEAD on my new amd64, but I'm bombing out here: cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe -DMAGIC='"/usr/share/misc/magic"' -DBUILTIN_ELF -DELFCORE -DHAVE_CONFIG_H -I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file -c /usr/src/lib/libmagic/../../contrib/file/softmagic.c -o softmagic.So building shared library libmagic.so.1 Segmentation fault (core dumped) *** Error code 139 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. It died twice in that same spot. I cvsup'd at about 1600 PST on December 8, 2004. I can issue the above `cc` by hand and it works fine...but it doesn't seem like a memory/cpu/hdd problem because it died in that same spot both times I tried it (cvsupping again in between.) Or is it failing on a ranlib that I don't see? This system has 8G of ram; I'm trying to jump to current because of rumored mmap fixes...the machine built 5.3 from 5.2.1 just fine, but now it can't build perl from 5.3; it runs out of memory.... Any help would be appreciated, Mike From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 00:26:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8732316A4CE for ; Thu, 9 Dec 2004 00:26:46 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 551BE43D58 for ; Thu, 9 Dec 2004 00:26:46 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iB90QkO3011151 for ; Wed, 8 Dec 2004 16:26:46 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iB90QkMF011150 for freebsd-current@freebsd.org; Wed, 8 Dec 2004 16:26:46 -0800 (PST) (envelope-from sgk) Date: Wed, 8 Dec 2004 16:26:46 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Message-ID: <20041209002645.GA7272@troutmask.apl.washington.edu> References: <20041209000148.GA4674@troutmask.apl.washington.edu> <20041209000710.GB4674@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041209000710.GB4674@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.2.1i Subject: Re: make(1) is broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 00:26:46 -0000 On Wed, Dec 08, 2004 at 04:07:10PM -0800, Steve Kargl wrote: > On Wed, Dec 08, 2004 at 04:01:48PM -0800, Steve Kargl wrote: > > Well, it appears that -current is highly unstable at > > the moment. In particularly, INET6 is causing a > > panic, so I went to build a new kernel without it. I'm > > now stuck with a broken make(1). (snip) > > Stop in /usr/src. > > troutmask:root[203] tail -1 /var/log/messages > > Dec 8 15:58:39 troutmask kernel: pid 4794 (make), uid 0: exited on signal 11 > > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Backing out the recent changes to the make sources via cvsup (*default date=2004.11.08.00.00.00) allows one to build a function make. -- Steve From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 00:29:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB46216A4CE for ; Thu, 9 Dec 2004 00:29:45 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86D1943D1D for ; Thu, 9 Dec 2004 00:29:45 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iB90TdTq011420; Wed, 8 Dec 2004 16:29:39 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iB90TdwP011419; Wed, 8 Dec 2004 16:29:39 -0800 (PST) (envelope-from sgk) Date: Wed, 8 Dec 2004 16:29:39 -0800 From: Steve Kargl To: Mike Hunter Message-ID: <20041209002939.GB7272@troutmask.apl.washington.edu> References: <20041209002430.GA18622@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041209002430.GA18622@ack.Berkeley.EDU> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: coredump while trying to build world (2004.12.08.1600-0800 src) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 00:29:45 -0000 On Wed, Dec 08, 2004 at 04:24:30PM -0800, Mike Hunter wrote: > Hi, > > I'm trying to go from RELENG_5 to HEAD on my new amd64, but I'm bombing > out here: > > cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe -DMAGIC='"/usr/share/misc/magic"' -DBUILTIN_ELF -DELFCORE -DHAVE_CONFIG_H -I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file -c /usr/src/lib/libmagic/../../contrib/file/softmagic.c -o softmagic.So > building shared library libmagic.so.1 > Segmentation fault (core dumped) > *** Error code 139 > You need to back out the recent changes to make(1). In your supfile file that you use with cvsup, set *default date=2004.11.08.00.00.00 src-usrbin cd /usr/src/usr.bin/make make make install PS: surprising the broken make(1) actually works for building a new make(1). -- Steve From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 00:30:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FFD116A4CE for ; Thu, 9 Dec 2004 00:30:39 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id D82D243D31 for ; Thu, 9 Dec 2004 00:30:38 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8554151385; Wed, 8 Dec 2004 16:37:06 -0800 (PST) Date: Wed, 8 Dec 2004 16:37:06 -0800 From: Kris Kennaway To: Mike Hunter Message-ID: <20041209003706.GA58263@xor.obsecurity.org> References: <20041209002430.GA18622@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WIyZ46R2i8wDzkSu" Content-Disposition: inline In-Reply-To: <20041209002430.GA18622@ack.Berkeley.EDU> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: coredump while trying to build world (2004.12.08.1600-0800 src) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 00:30:39 -0000 --WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Dec 08, 2004 at 04:24:30PM -0800, Mike Hunter wrote: > Hi, >=20 > I'm trying to go from RELENG_5 to HEAD on my new amd64, but I'm bombing > out here: >=20 > cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe -DMAGIC=3D'"/usr/share/mis= c/magic"' -DBUILTIN_ELF -DELFCORE -DHAVE_CONFIG_H -I/usr/src/lib/libmagic -= I/usr/src/lib/libmagic/../../contrib/file -c /usr/src/lib/libmagic/../../c= ontrib/file/softmagic.c -o softmagic.So > building shared library libmagic.so.1 > Segmentation fault (core dumped) > *** Error code 139 Looks like make might be broken, see Steve's post. Kris --WIyZ46R2i8wDzkSu Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBt54yWry0BWjoQKURAg4SAKC83AXr+86PrJq60ZPev14Xb96z4wCfZvp0 O7Ko99cdhbDlL6DDllYHWZQ= =VrMP -----END PGP SIGNATURE----- --WIyZ46R2i8wDzkSu-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 00:36:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B82E816A4D0 for ; Thu, 9 Dec 2004 00:36:28 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EAF043D5F for ; Thu, 9 Dec 2004 00:36:28 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id iB90Yh819452; Wed, 8 Dec 2004 16:34:43 -0800 (PST) Date: Wed, 8 Dec 2004 16:34:43 -0800 From: Mike Hunter To: Steve Kargl Message-ID: <20041209003443.GA19328@ack.Berkeley.EDU> References: <20041209002430.GA18622@ack.Berkeley.EDU> <20041209002939.GB7272@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041209002939.GB7272@troutmask.apl.washington.edu> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: coredump while trying to build world (2004.12.08.1600-0800 src) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 00:36:28 -0000 On Dec 08, "Steve Kargl" wrote: > On Wed, Dec 08, 2004 at 04:24:30PM -0800, Mike Hunter wrote: > > Hi, > > > > I'm trying to go from RELENG_5 to HEAD on my new amd64, but I'm bombing > > out here: > > > > cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe -DMAGIC='"/usr/share/misc/magic"' -DBUILTIN_ELF -DELFCORE -DHAVE_CONFIG_H -I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file -c /usr/src/lib/libmagic/../../contrib/file/softmagic.c -o softmagic.So > > building shared library libmagic.so.1 > > Segmentation fault (core dumped) > > *** Error code 139 > > > > You need to back out the recent changes to make(1). > In your supfile file that you use with cvsup, set > > *default date=2004.11.08.00.00.00 > src-usrbin > > cd /usr/src/usr.bin/make > make > make install Thank you for the detailed help! I'll let you know if it doesn't work (currently up against the cvs access limit :| ). > PS: surprising the broken make(1) actually works for building > a new make(1). :) Mike From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 00:43:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D55D16A4CE for ; Thu, 9 Dec 2004 00:43:36 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 44B1B43D67 for ; Thu, 9 Dec 2004 00:43:36 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iB90hZrY000649 for ; Wed, 8 Dec 2004 16:43:35 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iB90hZ1P000648 for freebsd-current@freebsd.org; Wed, 8 Dec 2004 16:43:35 -0800 (PST) (envelope-from sgk) Date: Wed, 8 Dec 2004 16:43:35 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Message-ID: <20041209004335.GA624@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 Subject: nfs appears broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 00:43:36 -0000 troutmask:root[201] mount /jumbo [udp] jumbo:/data: RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed out [udp] jumbo:/data: RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed out troutmask:root[203] grep jumbo /etc/fstab jumbo:/data /jumbo nfs rw,noauto 0 0 This is with world+kernel from about 30 minutes on amd64. I was able to mount /jumbo with a kernel from monday. -- Steve From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 01:01:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16C7616A4CE for ; Thu, 9 Dec 2004 01:01:06 +0000 (GMT) Received: from wasley.bl.mmtr.or.jp (wasley.bl.mmtr.or.jp [210.228.173.142]) by mx1.FreeBSD.org (Postfix) with SMTP id 7B15443D41 for ; Thu, 9 Dec 2004 01:01:02 +0000 (GMT) (envelope-from rushani@bl.mmtr.or.jp) Received: (qmail 15077 invoked from network); 9 Dec 2004 10:01:00 +0900 Received: from unknown (HELO localhost) (210.165.212.57) by wasley.bl.mmtr.or.jp with SMTP; 9 Dec 2004 10:01:00 +0900 Date: Thu, 09 Dec 2004 10:00:08 +0900 (JST) Message-Id: <20041209.100008.21874313.rushani@bl.mmtr.or.jp> To: sam@errno.com From: Hideyuki KURASHINA In-Reply-To: <200412081109.43840.sam@errno.com> References: <200412081109.43840.sam@errno.com> X-URL: http://www.rushani.jp/ X-PGP-Public-Key: http://www.rushani.jp/rushani.asc X-PGP-Fingerprint: A052 6F98 6146 6FE3 91E2 DA6B F2FA 2088 439A DC57 X-RC5-72-Stats: http://stats.distributed.net/participant/psummary.php?project_id=8&id=432320 X-Mailer: Mew version 4.1.52 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: WEP does not work? (was Re: HEADSUP: ath updates) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 01:01:06 -0000 Hi, First of all, I would like to thank your hard work. That's great! I decided to track HEAD rather than RELENG_5 with my new laptop. Here is my environment: Access Point: PRISM3 on NetBSD 2.0 box Client: Atheros 5212 on FreeBSD 6.0 laptop >>> On Wed, 8 Dec 2004 11:09:43 -0800, Sam Leffler said: > I just committed updates for the ath driver and the ath hal. There are many > changes to this code including a split of the tx rate control algorithm into > a separate module. This means that when statically configuring the driver > you now need to specify: > > device ath > device ath_hal > device ath_rate_onoe I compiled kernel including above devices and with device wlan device wlan_wep then installed new kernel and ifconfig (dmesg from boot -v is attached). After rebooting, I set IPv4 and IPv6 addresses and those routes. Because access point supports only 802.11b, I configured my wireless network by 128bit WEP as follows /sbin/ifconfig ath0 nwid MY-SSID nwkey 0x01234567890123456789012345 media autoselect mode 11b then I got following error: ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) ath0: ath_chan_set: unable to reset channel 12 (2467 Mhz) It seems that ath0 failed to reset channel. I manually specified channel, then ifconfig shows: # ifconfig -v ath0 ath0: flags=8843 mtu 1500 inet 192.168.1.11 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::20e:XXXX:XXXX:XXXX%ath0 prefixlen 64 scopeid 0x2 inet6 2001:3e0:XX:X::XX prefixlen 64 ether 00:0e:9b:XX:XX:XX media: IEEE 802.11 Wireless Ethernet autoselect mode 11b (DS/11Mbps) status: associated ssid MY-SSID channel 3 (2422) bssid 00:90:cc:XX:XX:XX authmode OPEN privacy ON deftxkey 1 powersavemode OFF powersavesleep 100 txpowmax 14 txpower 60 rtsthreshold 2312 protmode CTS wme roaming AUTO bintval 100 AC_BE cwmin 5 cwmax 10 aifs 3 txopLimit 0 -acm ack cwmin 5 cwmax 10 aifs 3 txopLimit 0 -acm AC_BK cwmin 5 cwmax 10 aifs 7 txopLimit 0 -acm ack cwmin 5 cwmax 10 aifs 7 txopLimit 0 -acm AC_VI cwmin 4 cwmax 5 aifs 2 txopLimit 188 -acm ack cwmin 4 cwmax 5 aifs 2 txopLimit 188 -acm AC_VO cwmin 3 cwmax 4 aifs 2 txopLimit 102 -acm ack cwmin 3 cwmax 4 aifs 2 txopLimit 102 -acm # ifconfig ath0 list chan Channel 1 : 2412* Mhz 11g Channel 11 : 2462* Mhz 11g Channel 2 : 2417* Mhz 11g Channel 12 : 2467* Mhz 11a 11g Channel 3 : 2422* Mhz 11g Channel 13 : 2472* Mhz 11g Channel 4 : 2427* Mhz 11g Channel 14 : 2484* Mhz 11b Channel 5 : 2432* Mhz 11g Channel 16 : 5080* Mhz 11a Channel 6 : 2437* Mhz 11g Channel 34 : 5170* Mhz 11a Channel 7 : 2442* Mhz 11g Channel 38 : 5190* Mhz 11a Channel 8 : 2447* Mhz 11a 11g Channel 42 : 5210* Mhz 11a Channel 9 : 2452* Mhz 11g Channel 46 : 5230* Mhz 11a Channel 10 : 2457* Mhz 11g # ifconfig ath0 list scan SSID BSSID CHAN RATE S:N INT CAPS MY-SSID 00:90:cc:XX:XX:XX 3 11M 43:0 100 EP Unfortunately, this does not work (default router is not reachable). # ping -n 192.168.1.254 PING 192.168.1.254 (192.168.1.254): 56 data bytes ping: sendto: Host is down ping: sendto: Host is down ping: sendto: Host is down ping: sendto: Host is down ping: sendto: Host is down ping: sendto: Host is down ping: sendto: Host is down ping: sendto: Host is down ^C --- 192.168.1.254 ping statistics --- 14 packets transmitted, 0 packets received, 100% packet loss Disabling WEP on both access point and client is OK: # ping -n 192.168.1.254 PING 192.168.1.254 (192.168.1.254): 56 data bytes 64 bytes from 192.168.1.254: icmp_seq=0 ttl=255 time=3.773 ms 64 bytes from 192.168.1.254: icmp_seq=1 ttl=255 time=1.513 ms 64 bytes from 192.168.1.254: icmp_seq=2 ttl=255 time=1.362 ms 64 bytes from 192.168.1.254: icmp_seq=3 ttl=255 time=1.774 ms ^C --- 192.168.1.254 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max/stddev = 1.362/2.106/3.773/0.974 ms Am I missing something? Same configuration worked file with FreeBSD 5.3-RELEASE on this laptop. -- rushani Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.0-CURRENT #1: Thu Dec 9 08:19:03 JST 2004 hideyuki@*****.*******.jp:/usr/obj/usr/src/sys/***** Preloaded elf kernel "/boot/kernel/kernel" at 0xc085d000. Preloaded elf module "/boot/kernel/cd9660.ko" at 0xc085d1c4. Preloaded elf module "/boot/kernel/ntfs.ko" at 0xc085d270. Preloaded elf module "/boot/kernel/nullfs.ko" at 0xc085d31c. Preloaded elf module "/boot/kernel/linux.ko" at 0xc085d3c8. Preloaded elf module "/boot/kernel/sysvshm.ko" at 0xc085d474. Preloaded elf module "/boot/kernel/sysvsem.ko" at 0xc085d520. Preloaded elf module "/boot/kernel/sysvmsg.ko" at 0xc085d5cc. Preloaded elf module "/boot/kernel/ipfw.ko" at 0xc085d678. Preloaded elf module "/boot/kernel/if_em.ko" at 0xc085d724. Preloaded elf module "/boot/kernel/snd_ich.ko" at 0xc085d7d0. Preloaded elf module "/boot/kernel/sound.ko" at 0xc085d87c. Preloaded elf module "/boot/kernel/usb.ko" at 0xc085d928. Preloaded elf module "/boot/kernel/ugen.ko" at 0xc085d9d0. Preloaded elf module "/boot/kernel/umass.ko" at 0xc085da7c. Preloaded elf module "/boot/kernel/agp.ko" at 0xc085db28. Preloaded elf module "/boot/kernel/random.ko" at 0xc085dbd0. Preloaded elf module "/boot/kernel/speaker.ko" at 0xc085dc7c. Preloaded elf module "/boot/modules/est.ko" at 0xc085dd28. Preloaded elf module "/boot/kernel/io.ko" at 0xc085ddd4. Preloaded elf module "/boot/kernel/joy.ko" at 0xc085de7c. Preloaded elf module "/boot/kernel/mem.ko" at 0xc085df24. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc085dfcc. Enhanced Speedstep running at 1400 MHz Calibrating clock(s) ... i8254 clock: 1193174 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 1395477560 Hz CPU: Intel(R) Pentium(R) M processor 1.40GHz (1395.48-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6d6 Stepping = 6 Features=0xafe9fbbf real memory = 527302656 (502 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000000c25000 - 0x000000001edd8fff, 505102336 bytes (123316 pages) avail memory = 506773504 (483 MB) bios32: Found BIOS32 Service Directory header at 0xc00f6fd0 bios32: Entry = 0xfd740 (c00fd740) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xfd6d0+0x1f8 pnpbios: Found PnP BIOS data at 0xc00f7050 pnpbios: Entry = f0000:b6c4 Rev = 1.0 pnpbios: Event flag at 4b4 Other BIOS signatures found: ath_rate: wlan: <802.11 Link Layer> random: io: mem: Pentium Pro MTRR support enabled null: ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: [MPSAFE] acpi_ec0: port 0x66,0x62 on acpi0 pci_open(1): mode 1 addr port (0x0cf8) is 0x8000f904 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=35808086) pcibios: BIOS version 2.10 Found $PIR table, 14 entries at 0xc00fdeb0 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded 0 0 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 0 0 B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 0 0 C 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 0 0 D 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded 0 2 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 0 2 B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 0 1 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 0 1 B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 1 0 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 1 0 B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 0 30 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 0 30 B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 0 30 C 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 0 30 D 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded 2 0 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 2 0 B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 2 0 C 0x62 3 4 5 6 7 9 10 11 12 14 15 slot 1 2 2 A 0x69 3 4 5 6 7 9 10 11 12 14 15 slot 1 2 2 B 0x6a 3 4 5 6 7 9 10 11 12 14 15 embedded 2 3 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 2 3 B 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 2 3 C 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 2 3 D 0x63 3 4 5 6 7 9 10 11 12 14 15 slot 2 9 0 A 0x60 3 4 5 6 7 9 10 11 12 14 15 slot 2 9 0 B 0x61 3 4 5 6 7 9 10 11 12 14 15 slot 2 9 0 C 0x62 3 4 5 6 7 9 10 11 12 14 15 slot 2 9 0 D 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded 9 1 A 0x61 3 4 5 6 7 9 10 11 12 14 15 embedded 9 2 A 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 9 2 B 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 2 1 A 0x68 3 4 5 6 7 9 10 11 12 14 15 embedded 0 29 A 0x60 3 4 5 6 7 9 10 11 12 14 15 embedded 0 29 B 0x63 3 4 5 6 7 9 10 11 12 14 15 embedded 0 29 C 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 0 29 D 0x6b 3 4 5 6 7 9 10 11 12 14 15 embedded 0 31 A 0x62 3 4 5 6 7 9 10 11 12 14 15 embedded 0 31 B 0x61 3 4 5 6 7 9 10 11 12 14 15 AcpiOsDerivePciId: bus 0 dev 31 func 0 AcpiOsDerivePciId: bus 2 dev 0 func 0 AcpiOsDerivePciId: bus 0 dev 29 func 7 acpi0: Power Button (fixed) atpic: Programming IRQ9 as level/low AcpiOsDerivePciId: bus 0 dev 0 func 0 AcpiOsDerivePciId: bus 0 dev 0 func 1 ACPI timer: 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_tz0: on acpi0 pci_link0: irq 11 on acpi0 pci_link0: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 6 7 9 10 11 pci_link0: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 6 7 9 10 11 pci_link0: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 pci_link1: irq 11 on acpi0 pci_link1: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 6 7 9 10 11 pci_link1: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 6 7 9 10 11 pci_link1: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 pci_link2: irq 11 on acpi0 pci_link2: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 6 7 9 10 11 pci_link2: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 6 7 9 10 11 pci_link2: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 pci_link3: irq 11 on acpi0 pci_link3: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 6 7 9 10 11 pci_link3: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 6 7 9 10 11 pci_link3: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 pci_link4: irq 11 on acpi0 pci_link4: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 6 7 9 10 11 pci_link4: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 6 7 9 10 11 pci_link4: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 pci_link5: irq 11 on acpi0 pci_link5: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 6 7 9 10 11 pci_link5: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 6 7 9 10 11 pci_link5: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 pci_link6: on acpi0 pci_link6: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 pci_link6: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 pci_link6: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 pci_link7: irq 11 on acpi0 pci_link7: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 6 7 9 10 11 pci_link7: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 6 7 9 10 11 pci_link7: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 acpi_lid0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 ACPI: Found matching pin for 0.2.INTA at func 0: 11 ACPI: Found matching pin for 0.29.INTA at func 0: 11 ACPI: Found matching pin for 0.29.INTB at func 1: 11 ACPI: Found matching pin for 0.29.INTC at func 2: 11 ACPI: Found matching pin for 0.29.INTD at func 7: 11 ACPI: Found matching pin for 0.31.INTA at func 1: 255 ACPI: Found matching pin for 0.31.INTB at func 3: 11 pci0: on pcib0 pci0: physical bus=0 found-> vendor=0x8086, dev=0x3580, revid=0x02 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0106, statreg=0x2090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x3584, revid=0x02 bus=0, slot=0, func=1 class=08-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0080, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x3585, revid=0x02 bus=0, slot=0, func=3 class=08-80-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x0080, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 3, range 32, base e0000000, size 27, enabled map[14]: type 1, range 32, base d0000000, size 19, enabled map[18]: type 4, range 32, base 00001800, size 3, enabled pcib0: matched entry for 0.2.INTA (src \\_SB_.LNKA:0) pcib0: slot 2 INTA routed to irq 11 via \\_SB_.LNKA found-> vendor=0x8086, dev=0x3582, revid=0x02 bus=0, slot=2, func=0 class=03-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0003, statreg=0x0090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 1 supports D0 D1 D3 current D0 map[10]: type 3, range 32, base e8000000, size 27, enabled map[14]: type 1, range 32, base d0080000, size 19, enabled found-> vendor=0x8086, dev=0x3582, revid=0x02 bus=0, slot=2, func=1 class=03-80-00, hdrtype=0x00, mfdev=1 cmdreg=0x0003, statreg=0x0090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 1 supports D0 D1 D3 current D0 map[20]: type 4, range 32, base 00001820, size 5, enabled pcib0: matched entry for 0.29.INTA (src \\_SB_.LNKA:0) pcib0: slot 29 INTA routed to irq 11 via \\_SB_.LNKA found-> vendor=0x8086, dev=0x24c2, revid=0x01 bus=0, slot=29, func=0 class=0c-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 map[20]: type 4, range 32, base 00001840, size 5, enabled pcib0: matched entry for 0.29.INTB (src \\_SB_.LNKD:0) pcib0: slot 29 INTB routed to irq 11 via \\_SB_.LNKD found-> vendor=0x8086, dev=0x24c4, revid=0x01 bus=0, slot=29, func=1 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 map[20]: type 4, range 32, base 00001860, size 5, enabled pcib0: matched entry for 0.29.INTC (src \\_SB_.LNKC:0) pcib0: slot 29 INTC routed to irq 11 via \\_SB_.LNKC found-> vendor=0x8086, dev=0x24c7, revid=0x01 bus=0, slot=29, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0001, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=11 map[10]: type 1, range 32, base d0100000, size 10, enabled pcib0: matched entry for 0.29.INTD (src \\_SB_.LNKH:0) pcib0: slot 29 INTD routed to irq 11 via \\_SB_.LNKH found-> vendor=0x8086, dev=0x24cd, revid=0x01 bus=0, slot=29, func=7 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=11 powerspec 2 supports D0 D3 current D0 found-> vendor=0x8086, dev=0x2448, revid=0x81 bus=0, slot=30, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x8080, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x24cc, revid=0x01 bus=0, slot=31, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x000f, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base 00001810, size 4, enabled found-> vendor=0x8086, dev=0x24ca, revid=0x01 bus=0, slot=31, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 map[20]: type 4, range 32, base 00001880, size 5, enabled pcib0: matched entry for 0.31.INTB (src \\_SB_.LNKB:0) pcib0: slot 31 INTB routed to irq 11 via \\_SB_.LNKB found-> vendor=0x8086, dev=0x24c3, revid=0x01 bus=0, slot=31, func=3 class=0c-05-00, hdrtype=0x00, mfdev=0 cmdreg=0x0001, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 map[10]: type 4, range 32, base 00001c00, size 8, enabled map[14]: type 4, range 32, base 000018c0, size 6, enabled map[18]: type 1, range 32, base d0100c00, size 9, enabled map[1c]: type 1, range 32, base d0100800, size 8, enabled pcib0: matched entry for 0.31.INTB (src \\_SB_.LNKB:0) pcib0: slot 31 INTB routed to irq 11 via \\_SB_.LNKB found-> vendor=0x8086, dev=0x24c5, revid=0x01 bus=0, slot=31, func=5 class=04-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type 4, range 32, base 00002400, size 8, enabled map[14]: type 4, range 32, base 00002000, size 7, enabled pcib0: matched entry for 0.31.INTB (src \\_SB_.LNKB:0) pcib0: slot 31 INTB routed to irq 11 via \\_SB_.LNKB found-> vendor=0x8086, dev=0x24c6, revid=0x01 bus=0, slot=31, func=6 class=07-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 powerspec 2 supports D0 D3 current D0 pci0: at device 0.1 (no driver attached) pci0: at device 0.3 (no driver attached) agp0: port 0x1800-0x1807 mem 0xd0000000-0xd007ffff,0xe0000000-0xe7ffffff irq 11 at device 2.0 on pci0 agp0: Reserved 0x8000000 bytes for rid 0x10 type 3 at 0xe0000000 agp0: Reserved 0x80000 bytes for rid 0x14 type 3 at 0xd0000000 agp0: detected 8060k stolen memory agp0: aperture size is 128M pci0: at device 2.1 (no driver attached) uhci0: port 0x1820-0x183f irq 11 at device 29.0 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1820 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x1840-0x185f irq 11 at device 29.1 on pci0 uhci1: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1840 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x1860-0x187f irq 11 at device 29.2 on pci0 uhci2: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1860 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xd0100000-0xd01003ff irq 11 at device 29.7 on pci0 ehci0: Reserved 0x400 bytes for rid 0x10 type 3 at 0xd0100000 ehci0: [GIANT-LOCKED] ehci_pci_attach: companion usb0 ehci_pci_attach: companion usb1 ehci_pci_attach: companion usb2 usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: single transaction translator uhub3: 6 ports with 6 removable, self powered pcib1: at device 30.0 on pci0 pcib1: secondary bus 2 pcib1: subordinate bus 5 pcib1: I/O decode 0x3000-0x7fff pcib1: memory decode 0xd0200000-0xdfffffff pcib1: prefetched decode 0xf0000000-0xf7ffffff pcib1: Subtractively decoded bridge. ACPI: Found matching pin for 0.2.INTA at func 0: 11 pci2: on pcib1 pci2: physical bus=2 map[10]: type 1, range 32, base b0000000, size 12, enabled pcib1: device (null) requested decoded memory range 0xb0000000-0xb0000fff pcib1: matched entry for 2.0.INTA (src \\_SB_.LNKA:0) pcib1: slot 0 INTA routed to irq 11 via \\_SB_.LNKA found-> vendor=0x1180, dev=0x0476, revid=0x8d bus=2, slot=0, func=0 class=06-07-00, hdrtype=0x02, mfdev=1 cmdreg=0x0107, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x80 (32000 ns), maxlat=0x07 (1750 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base d0210000, size 8, enabled pcib1: device (null) requested decoded memory range 0xd0210000-0xd02100ff pcib1: matched entry for 2.0.INTB (src \\_SB_.LNKB:0) pcib1: slot 0 INTB routed to irq 11 via \\_SB_.LNKB found-> vendor=0x1180, dev=0x0822, revid=0x13 bus=2, slot=0, func=1 class=08-05-00, hdrtype=0x00, mfdev=1 cmdreg=0x0106, statreg=0x0210, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base d0220000, size 17, enabled pcib1: device (null) requested decoded memory range 0xd0220000-0xd023ffff map[18]: type 4, range 32, base 00007000, size 6, enabled pcib1: device (null) requested decoded I/O range 0x7000-0x703f pcib1: matched entry for 2.1.INTA (src \\_SB_.LNKE:0) pcib1: slot 1 INTA routed to irq 11 via \\_SB_.LNKE found-> vendor=0x8086, dev=0x1077, revid=0x00 bus=2, slot=1, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0230, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0xff (63750 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type 1, range 32, base d0200000, size 16, enabled pcib1: device (null) requested decoded memory range 0xd0200000-0xd020ffff pcib1: matched entry for 2.2.INTA (src \\_SB_.LNKF:0) pcib1: slot 2 INTA routed to irq 11 via \\_SB_.LNKF found-> vendor=0x168c, dev=0x1014, revid=0x01 bus=2, slot=2, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0116, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x50 (2400 ns), mingnt=0x0a (2500 ns), maxlat=0x1c (7000 ns) intpin=a, irq=11 powerspec 2 supports D0 D3 current D0 cbb0: mem 0xb0000000-0xb0000fff irq 11 at device 0.0 on pci2 cbb0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xb0000000 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb0: [MPSAFE] cbb0: PCI Configuration space: 0x00: 0x04761180 0x02100107 0x0607008d 0x00824000 0x10: 0xb0000000 0x020000dc 0xb0050302 0xfffff000 0x20: 0x00000000 0xfffff000 0x00000000 0xfffffffc 0x30: 0x00000000 0xfffffffc 0x00000000 0x0700010b 0x40: 0x05551014 0x00000001 0x00000000 0x00000000 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 0x80: 0x04800001 0x00000000 0x04630464 0x00000001 0x90: 0x00000000 0x00000000 0x00000000 0x00000000 0xa0: 0x008a0000 0x00000000 0x00f00000 0x00000000 0xb0: 0x00000000 0x36000000 0x00003800 0x00000000 0xc0: 0x05551014 0x00000000 0x00000000 0x00000000 0xd0: 0x00000000 0x00000000 0x00000000 0xfe0a0001 0xe0: 0x24c04000 0x00000000 0x00000000 0x00000000 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 pci2: at device 0.1 (no driver attached) em0: port 0x7000-0x703f mem 0xd0220000-0xd023ffff irq 11 at device 1.0 on pci2 em0: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xd0220000 em0: Reserved 0x40 bytes for rid 0x18 type 4 at 0x7000 em0: [MPSAFE] em0: bpf attached em0: Ethernet address: 00:0a:e4:XX:XX:XX em0: Speed:N/A Duplex:N/A ath0: mem 0xd0200000-0xd020ffff irq 11 at device 2.0 on pci2 ath0: Reserved 0x10000 bytes for rid 0x10 type 3 at 0xd0200000 ath0: [MPSAFE] ath0: bad hal channel 858993443 (4920/340) ignored ath0: bad hal channel 858993447 (4940/340) ignored ath0: bad hal channel 858993451 (4960/340) ignored ath0: bad hal channel 858993455 (4980/340) ignored ath0: bpf attached ath0: Ethernet address: 00:0e:9b:XX:XX:XX ath0: bpf attached ath0: bpf attached ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: mac 5.9 phy 4.3 radio 3.6 ath0: Use hw queue 1 for WME_AC_BE traffic ath0: Use hw queue 0 for WME_AC_BK traffic ath0: Use hw queue 2 for WME_AC_VI traffic ath0: Use hw queue 3 for WME_AC_VO traffic ath0: Use hw queue 8 for CAB traffic ath0: Use hw queue 9 for beacons isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1810-0x181f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x1810 ata0: channel #0 on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0-master: stat=0x50 err=0x01 lsb=0x00 msb=0x00 ata0-slave: stat=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ata0: [MPSAFE] ata1: channel #1 on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=00 ostat0=ff ostat1=ff ata1: [MPSAFE] ichsmb0: port 0x1880-0x189f irq 11 at device 31.3 on pci0 ichsmb0: Reserved 0x20 bytes for rid 0x20 type 4 at 0x1880 ichsmb0: [GIANT-LOCKED] smbus0: on ichsmb0 smb0: on smbus0 pcm0: port 0x18c0-0x18ff,0x1c00-0x1cff mem 0xd0100800-0xd01008ff,0xd0100c00-0xd0100dff irq 11 at device 31.5 on pci0 pcm0: Reserved 0x100 bytes for rid 0x10 type 4 at 0x1c00 pcm0: Reserved 0x40 bytes for rid 0x14 type 4 at 0x18c0 pcm0: [GIANT-LOCKED] pcm0: pcm0: Codec features headphone, 20 bit DAC, 5 bit master volume, no 3D Stereo Enhancement pcm0: Primary codec extended features variable rate PCM, AMAP, reserved 4 pcm0: sndbuf_setmap 1eb85000, 4000; 0xdcfcc000 -> 1eb85000 pcm0: sndbuf_setmap 1eb7c000, 4000; 0xdcfd0000 -> 1eb7c000 pci0: at device 31.6 (no driver attached) pci0:31:6: Transition from D0 to D3 speaker0: port 0x61 on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x54ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 atkbd0: [GIANT-LOCKED] psm0: unable to allocate IRQ psmcpnp0: irq 12 on acpi0 psm0: current command byte:0047 psm0: flags 0x2000 irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:00002000, flags:00000008, packet size:3 psm0: syncmask:c0, syncbits:00 acpi_cmbat0: on acpi0 acpi_acad0: on acpi0 ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it atkbdc: atkbdc0 already exists; skipping it sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices pmtimer0 on isa0 orm0: at iomem 0xdc000-0xdffff,0xcd800-0xce7ff,0xcc800-0xcd7ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 adv0: not probed (disabled) aha0: not probed (disabled) aic0: not probed (disabled) bt0: not probed (disabled) cs0: not probed (disabled) ed0: not probed (disabled) fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 fe0: not probed (disabled) ie0: not probed (disabled) lnc0: not probed (disabled) pcic0 failed to probe at port 0x3e0 iomem 0xd0000 on isa0 pcic1: not probed (disabled) ppc0 failed to probe at irq 7 on isa0 sio0 failed to probe at port 0x3f8 irq 4 on isa0 sio1 failed to probe at port 0x2f8 irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) sn0: not probed (disabled) vt0: not probed (disabled) isa_probe_children: probing PnP devices Device configuration finished. Timecounter "TSC" frequency 1395477560 Hz quality 800 Timecounters tick every 1.000 msec Linux ELF exec handler installed lo0: bpf attached ipfw2 initialized, divert loadable, rule-based forwarding disabled, default to deny, logging unlimited cpu0: set speed to 100.0% acpi_cpu: throttling enabled, 8 steps (100% to 12.5%), currently 100.0% acpi_cmbat0: battery initialization start acpi_acad0: acline initialization start acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times ata0-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin ata0-master: setting PIO4 on Intel ICH4 chip ata0-master: setting UDMA100 on Intel ICH4 chip ad0: ATA-5 disk at ata0-master ad0: 38154MB (78140160 sectors), 77520 C, 16 H, 63 S, 512 B ad0: 16 secs/int, 1 depth queue, UDMA100 pcm0: measured ac97 link rate at 47997 Hz, will use 48000 Hz GEOM: new disk ad0 kern_symlink = 0 Trying to mount root from ufs:/dev/ad0s2a kernel_vmount = 0 start_init: trying /sbin/init procfs registered linprocfs registered splash: image decoder found: daemon_saver ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) ath0: ath_chan_set: unable to reset channel 12 (2467 Mhz) acpi_cmbat0: battery initialization failed, giving up em0: Link is up 100 Mbps Full Duplex em0: Link is Down From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 01:06:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9F0916A4CE for ; Thu, 9 Dec 2004 01:06:58 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4A9E43D31 for ; Thu, 9 Dec 2004 01:06:58 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iB916w0r016221 for ; Wed, 8 Dec 2004 17:06:58 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iB916wRp016220 for freebsd-current@freebsd.org; Wed, 8 Dec 2004 17:06:58 -0800 (PST) (envelope-from sgk) Date: Wed, 8 Dec 2004 17:06:58 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Message-ID: <20041209010658.GA14890@troutmask.apl.washington.edu> References: <20041209000148.GA4674@troutmask.apl.washington.edu> <20041209000710.GB4674@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041209000710.GB4674@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.2.1i Subject: Re: make(1) is broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 01:06:58 -0000 On Wed, Dec 08, 2004 at 04:07:10PM -0800, Steve Kargl wrote: > > troutmask:root[225] find /usr/obj/ -name make.core > /usr/obj/usr/src/sys/SPEW/make.core > troutmask:root[226] gdb /usr/bin/make /usr/obj/usr/src/sys/SPEW/make.core > > #0 Lst_Remove (list=0x5580a0, ln=0x0) > at /usr/src/usr.bin/make/lst.lib/lstRemove.c:74 > 74 if (ln->nextPtr != NULL) > (gdb) bt > #0 Lst_Remove (list=0x5580a0, ln=0x0) > at /usr/src/usr.bin/make/lst.lib/lstRemove.c:74 > #1 0x00000000004052bb in Dir_Destroy (pp=0x81e780) > at /usr/src/usr.bin/make/dir.c:1143 > #2 0x0000000000405300 in Dir_ClearPath (path=0x5580a0) > at /usr/src/usr.bin/make/dir.c:1172 > #3 0x0000000000404283 in Dir_End () at /usr/src/usr.bin/make/dir.c:265 > #4 0x000000000040a8da in main (argc=2, argv=0x7fffffffe3e0) > at /usr/src/usr.bin/make/main.c:888 > Looking at the diff between the 1.17 and 1.16, I suspect this chunk of code in Lst_Remove: - if (!Lst_Valid(list) || !Lst_NodeValid(ln, list)) { - return (FAILURE); - } should have been replaced by if (list == NULL || ln == NULL) return; -- Steve From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 01:16:50 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6E2F16A4CE for ; Thu, 9 Dec 2004 01:16:50 +0000 (GMT) Received: from freebsd3.cimlogic.com.au (adsl-20-121.swiftdsl.com.au [218.214.20.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 189C643D5C for ; Thu, 9 Dec 2004 01:16:46 +0000 (GMT) (envelope-from jb@cimlogic.com.au) Received: by freebsd3.cimlogic.com.au (Postfix, from userid 102) id 95FC46ACE0; Thu, 9 Dec 2004 12:16:43 +1100 (EST) Date: Thu, 9 Dec 2004 12:16:43 +1100 From: John Birrell To: Steve Kargl Message-ID: <20041209011643.GB95055@freebsd3.cimlogic.com.au> References: <20041209004335.GA624@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041209004335.GA624@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: nfs appears broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 01:16:51 -0000 On Wed, Dec 08, 2004 at 04:43:35PM -0800, Steve Kargl wrote: > troutmask:root[201] mount /jumbo > [udp] jumbo:/data: RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed out > [udp] jumbo:/data: RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed out > > troutmask:root[203] grep jumbo /etc/fstab > jumbo:/data /jumbo nfs rw,noauto 0 0 > > > This is with world+kernel from about 30 minutes on amd64. I was > able to mount /jumbo with a kernel from monday. I updated a current machine yesterday and mountd complains about in invalid line in /etc/exports, saying that / isn't a mount point. The client reports "permission denied". I cvsup'd again today and the kernel panics before I can even get to try NFS. -- John Birrell From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 01:30:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F48916A4D0 for ; Thu, 9 Dec 2004 01:30:30 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DBB843D54 for ; Thu, 9 Dec 2004 01:30:30 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iB91TFwu031465; Wed, 8 Dec 2004 17:29:15 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iB91TFlo031464; Wed, 8 Dec 2004 17:29:15 -0800 (PST) (envelope-from sgk) Date: Wed, 8 Dec 2004 17:29:15 -0800 From: Steve Kargl To: John Birrell Message-ID: <20041209012915.GA16228@troutmask.apl.washington.edu> References: <20041209004335.GA624@troutmask.apl.washington.edu> <20041209011643.GB95055@freebsd3.cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041209011643.GB95055@freebsd3.cimlogic.com.au> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: nfs appears broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 01:30:30 -0000 On Thu, Dec 09, 2004 at 12:16:43PM +1100, John Birrell wrote: > On Wed, Dec 08, 2004 at 04:43:35PM -0800, Steve Kargl wrote: > > troutmask:root[201] mount /jumbo > > [udp] jumbo:/data: RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed out > > [udp] jumbo:/data: RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed out > > > > troutmask:root[203] grep jumbo /etc/fstab > > jumbo:/data /jumbo nfs rw,noauto 0 0 > > > > > > This is with world+kernel from about 30 minutes on amd64. I was > > able to mount /jumbo with a kernel from monday. > > I updated a current machine yesterday and mountd complains about in invalid > line in /etc/exports, saying that / isn't a mount point. The client reports > "permission denied". > > I cvsup'd again today and the kernel panics before I can even get to try NFS. > Do you have INET6 in your kernel? I had to remove it or the kernel would panic. Fortunately, I don't need INET6. -- Steve From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 01:31:19 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6CFDB16A4CE for ; Thu, 9 Dec 2004 01:31:19 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 244C443D54 for ; Thu, 9 Dec 2004 01:31:17 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iB91UDpg014363 for ; Thu, 9 Dec 2004 12:00:13 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Thu, 9 Dec 2004 12:00:59 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iB91LIQ16370 for ; Thu, 9 Dec 2004 11:51:18 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id YK36KZ3P; Thu, 9 Dec 2004 11:51:03 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iB91LSxM014573 ; Thu, 9 Dec 2004 11:51:28 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iB91LSCM014572; Thu, 9 Dec 2004 11:51:28 +1030 (CST) (envelope-from wilkinsa) Date: Thu, 9 Dec 2004 11:51:28 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20041209012125.GA14557@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org, matthew.thyer@dsto.defence.gov.au References: <20041208070454.GA11139@squash.dsto.defence.gov.au> <20041208084757.T1146@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20041208084757.T1146@fledge.watson.org> User-Agent: Mutt/1.5.6i cc: matthew.thyer@dsto.defence.gov.au Subject: Re: panic: process 839(xmms):1 holds process lock but isn't blocked ona lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 01:31:19 -0000 Another panic whilst mp3s were playing on xmms: db> tr kdb_enter(c068735f,c06df360,c068a355,e87308e4,c30adc80) at kdb_enter+0x32 panic(c068a355,e4e,c2e18be4,1,c0686981) at panic+0x14b turnstile_wait(c2b37200,c2e18b04,c30ade10,220,c2e18b04) at turnstile_wait+0x5ec _mtx_lock_sleep(c2e18b04,c30adc80,0,c0684acc,170) at _mtx_lock_sleep+0xb0 _mtx_lock_flags(c2e18b04,0,c0684acc,170,c0518b28) at _mtx_lock_flags+0xaf fork1(c06da1e0,60034,0,e87309bc,8) at fork1+0x3f5 kthread_create(c0594878,c0709834,0,40000,0) at kthread_create+0x40 nfs_nfsiodnew(d69e16bc,200000a4,e8730a20,c04e7eca,c06dedf4) at nfs_nfsiodnew+0x8d nfs_asyncio(d69e15f4,0,0,0,0) at nfs_asyncio+0x69 nfs_strategy(e8730a64,1,c068e01e,36a,d69e16bc) at nfs_strategy+0x72 ibwrite(d69e15f4,0,c0693489,b1b,c0518b55) at ibwrite+0x2dc nfs_flush(1,c30adc80,0,2,31d) at nfs_flush+0x3ed nfs_close(e8730ba4,1,c068ff9d,140,c06d3360) at nfs_close+0x7d vn_close(c3598738,3,c6d53700,c30adc80,c06b5e64) at vn_close+0x68 vn_closefile(c31453b8,c30adc80,c0684320,82a,0) at vn_closefile+0x5d fdrop_locked(c31453b8,c30adc80,c06e2f20,c30adc80,0) at fdrop_locked+0xab closef(c31453b8,c30adc80,c0684320,3e3,0) at closef+0x32 close(c30adc80,e8730d14,4,431,1) at close+0xef syscall(bfbf002f,8d4002f,bfbf002f,8062200,1) at syscall+0x13b Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (6, FreeBSD ELF32, close), eip = 0x28216b0f, esp = 0xbfbfe7bc, ebp = 0xbfbfe7e8 --- db> 0n Wed, Dec 08, 2004 at 08:49:14AM -0500, Andrew R. Reiter wrote: > On Wed, 8 Dec 2004, Wilkinson, Alex wrote: > > :Hi all, > : > :I got this panic today on a: > :FreeBSD 5.3-STABLE #13: Mon Nov 29 09:49:10 CST 2004 > : > :This panic is reproduceable via two methods: > : > :1. # kldload snd_ich > : > :2. add snd_ich_load="YES" to /boot/loader.conf; reboot; > : # kldunload snd_ich > : > > For what it's worth, on recent -CURRENt, I've had 'kdload snd_ich' hang my > machine... as in full lock up. kldload snd_driver I've had varied > success... I booted yesterday AM's -CURRENT and after boot kldload'd > snd_Driver and had a hang... but after reb ooting, starting X, su'ing to > root, and loading.. it worked. Random :-) > > :I have a kernel with debugging symbols and a vmcore if anyone is > :interested. > : > :db> trace > :kdb_enter(c068735f,c06df360,c068a355,e3744c64,c266c320) at > :kdb_enter+0x32 > :panic(c068a355,347,c3020698,1,c0686981) at panic+0x14b > :turnstile_wait(c2ef6600,c06ddec0,c3021e10,220,c06ddec0) at > :turnstile_wait+0x5ec > :_mtx_lock_sleep(c06ddec0,c266c320,0,c0684ceb,222) at > :_mtx_lock_sleep+0xb0 > :_mtx_lock_flags(c06ddec0,0,c0684ceb,222,0) at _mtx_lock_flags+0xaf > :ithread_loop(c2661480,e3744d48,c0684acc,323,c2661480) at > :ithread_loop+0x1ea > :fork_exit(c04de759,c2661480,e3744d48) at fork_exit+0xa6 > :fork_trampoline() at fork_trampoline+0x8 > :--- trap 0x1, eip = 0, esp = 0xe3744d7c, ebp = 0 --- > :db> show pcpu > :cpuid = 0 > :curthread = 0xc266c320: pid 28 "irq18: uhci2 bt0++" > :curpcb = 0xe3744da0 > :fpcurthread = none > :idlethread = 0xc26644b0: pid 11 "idle" > :APIC ID = 0 > :currentldt = 0x28 > :spin locks held: > :db> show lockedvnods > :Locked vnodes > :db> > : > : (850)-08.12.2004 hostname-{17:26}-[/var/crash]->sudo kldunload snd_ich > :Password: > :lock order reversal > : 1st 0xc2781a40 pcm0 (sound cdev) @ > :/usr/src/sys/modules/sound/sound/../../../dev/sound/pcm/sound.c:706 > : 2nd 0xc07c6a20 sndstat (sndstat) @ > :/usr/src/sys/modules/sound/sound/../../../dev/sound/pcm/sndstat.c:257 > :KDB: stack backtrace: > :witness_checkorder(c07c6a20,9,c07c1a3d,101,0) at > :witness_checkorder+0x5fa > :_sx_xlock(c07c6a20,c07c1a3d,101,0,c2738e00) at _sx_xlock+0x5c > :sndstat_unregister(c2753800,8,c07c1b35,2c2,c2753800) at > :sndstat_unregister+0x27 > :pcm_unregister(c2753800,c06a5f7c,c2753800,e75e2bfc,c2753800) at > :pcm_unregister+0x1f5 > :ich_pci_detach(c2753800,c26fd850,c06a5f7c,c07a88f1,3) at > :ich_pci_detach+0x13 > :device_detach(c2753800,c07a8909,c26e2000,1,c26aed80) at > :device_detach+0x6b > : > :_______________________________________________ > :freebsd-current@freebsd.org mailing list > :http://lists.freebsd.org/mailman/listinfo/freebsd-current > :To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > : > : > > -- > Andrew R. Reiter > arr@watson.org > arr@FreeBSD.org > From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 01:35:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B20A816A4CE for ; Thu, 9 Dec 2004 01:35:57 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5922543D60 for ; Thu, 9 Dec 2004 01:35:57 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.91] ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id iB91ZsWi028079 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 8 Dec 2004 17:35:54 -0800 (PST) (envelope-from sam@errno.com) From: Sam Leffler Organization: Errno Consulting To: freebsd-current@freebsd.org Date: Wed, 8 Dec 2004 17:44:27 -0800 User-Agent: KMail/1.7 References: <200412081109.43840.sam@errno.com> <20041209.100008.21874313.rushani@bl.mmtr.or.jp> In-Reply-To: <20041209.100008.21874313.rushani@bl.mmtr.or.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412081744.27539.sam@errno.com> Subject: Re: WEP does not work? (was Re: HEADSUP: ath updates) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 01:35:57 -0000 On Wednesday 08 December 2004 05:00 pm, Hideyuki KURASHINA wrote: > Hi, > > First of all, I would like to thank your hard work. That's great! > I decided to track HEAD rather than RELENG_5 with my new laptop. > Here is my environment: > > Access Point: PRISM3 on NetBSD 2.0 box > Client: Atheros 5212 on FreeBSD 6.0 laptop > > >>> On Wed, 8 Dec 2004 11:09:43 -0800, Sam Leffler said: > > > > I just committed updates for the ath driver and the ath hal. There are > > many changes to this code including a split of the tx rate control > > algorithm into a separate module. This means that when statically > > configuring the driver you now need to specify: > > > > device ath > > device ath_hal > > device ath_rate_onoe > > I compiled kernel including above devices and with > > device wlan > device wlan_wep > > then installed new kernel and ifconfig (dmesg from boot -v is attached). > > After rebooting, I set IPv4 and IPv6 addresses and those routes. Because > access point supports only 802.11b, I configured my wireless network > by 128bit WEP as follows > > /sbin/ifconfig ath0 nwid MY-SSID nwkey 0x01234567890123456789012345 media > autoselect mode 11b > > then I got following error: > > ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) > ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) > ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) > ath0: ath_chan_set: unable to reset channel 12 (2467 Mhz) Weird, can you send me the regdomain and country code: e.g. the output of sysctl dev.ath.0. > > It seems that ath0 failed to reset channel. I manually specified channel, > then ifconfig shows: > > # ifconfig -v ath0 > ath0: flags=8843 mtu 1500 > inet 192.168.1.11 netmask 0xffffff00 broadcast 192.168.1.255 > inet6 fe80::20e:XXXX:XXXX:XXXX%ath0 prefixlen 64 scopeid 0x2 > inet6 2001:3e0:XX:X::XX prefixlen 64 > ether 00:0e:9b:XX:XX:XX > media: IEEE 802.11 Wireless Ethernet autoselect mode 11b (DS/11Mbps) > status: associated > ssid MY-SSID channel 3 (2422) bssid 00:90:cc:XX:XX:XX > authmode OPEN privacy ON deftxkey 1 powersavemode OFF > powersavesleep 100 txpowmax 14 txpower 60 rtsthreshold 2312 protmode CTS > wme roaming AUTO bintval 100 > AC_BE cwmin 5 cwmax 10 aifs 3 txopLimit 0 -acm ack > cwmin 5 cwmax 10 aifs 3 txopLimit 0 -acm > AC_BK cwmin 5 cwmax 10 aifs 7 txopLimit 0 -acm ack > cwmin 5 cwmax 10 aifs 7 txopLimit 0 -acm > AC_VI cwmin 4 cwmax 5 aifs 2 txopLimit 188 -acm ack > cwmin 4 cwmax 5 aifs 2 txopLimit 188 -acm > AC_VO cwmin 3 cwmax 4 aifs 2 txopLimit 102 -acm ack > cwmin 3 cwmax 4 aifs 2 txopLimit 102 -acm This doesn't show a key installed. I don't typically use nwkey; I'll have to check it. > > # ifconfig ath0 list chan > Channel 1 : 2412* Mhz 11g Channel 11 : 2462* Mhz 11g > Channel 2 : 2417* Mhz 11g Channel 12 : 2467* Mhz 11a 11g > Channel 3 : 2422* Mhz 11g Channel 13 : 2472* Mhz 11g > Channel 4 : 2427* Mhz 11g Channel 14 : 2484* Mhz 11b > Channel 5 : 2432* Mhz 11g Channel 16 : 5080* Mhz 11a > Channel 6 : 2437* Mhz 11g Channel 34 : 5170* Mhz 11a > Channel 7 : 2442* Mhz 11g Channel 38 : 5190* Mhz 11a > Channel 8 : 2447* Mhz 11a 11g Channel 42 : 5210* Mhz 11a > Channel 9 : 2452* Mhz 11g Channel 46 : 5230* Mhz 11a > Channel 10 : 2457* Mhz 11g > So it seems channels 8 and 12 are supposedly available. > # ifconfig ath0 list scan > SSID BSSID CHAN RATE S:N INT CAPS > MY-SSID 00:90:cc:XX:XX:XX 3 11M 43:0 100 EP > > Unfortunately, this does not work (default router is not reachable). > > # ping -n 192.168.1.254 > PING 192.168.1.254 (192.168.1.254): 56 data bytes > ping: sendto: Host is down > ping: sendto: Host is down > ping: sendto: Host is down > ping: sendto: Host is down > ping: sendto: Host is down > ping: sendto: Host is down > ping: sendto: Host is down > ping: sendto: Host is down > ^C > --- 192.168.1.254 ping statistics --- > 14 packets transmitted, 0 packets received, 100% packet loss > > Disabling WEP on both access point and client is OK: > > # ping -n 192.168.1.254 > PING 192.168.1.254 (192.168.1.254): 56 data bytes > 64 bytes from 192.168.1.254: icmp_seq=0 ttl=255 time=3.773 ms > 64 bytes from 192.168.1.254: icmp_seq=1 ttl=255 time=1.513 ms > 64 bytes from 192.168.1.254: icmp_seq=2 ttl=255 time=1.362 ms > 64 bytes from 192.168.1.254: icmp_seq=3 ttl=255 time=1.774 ms > ^C > --- 192.168.1.254 ping statistics --- > 4 packets transmitted, 4 packets received, 0% packet loss > round-trip min/avg/max/stddev = 1.362/2.106/3.773/0.974 ms > > Am I missing something? Same configuration worked file with FreeBSD > 5.3-RELEASE on this laptop. <...stuff deleted...> Try using wepkey instead of nwkey. Sam From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 01:44:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1794316A4CE for ; Thu, 9 Dec 2004 01:44:27 +0000 (GMT) Received: from freebsd3.cimlogic.com.au (adsl-20-121.swiftdsl.com.au [218.214.20.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9986C43D4C for ; Thu, 9 Dec 2004 01:44:26 +0000 (GMT) (envelope-from jb@cimlogic.com.au) Received: by freebsd3.cimlogic.com.au (Postfix, from userid 102) id B1F3A6AA04; Thu, 9 Dec 2004 12:44:25 +1100 (EST) Date: Thu, 9 Dec 2004 12:44:25 +1100 From: John Birrell To: Steve Kargl Message-ID: <20041209014425.GC95055@freebsd3.cimlogic.com.au> References: <20041209004335.GA624@troutmask.apl.washington.edu> <20041209011643.GB95055@freebsd3.cimlogic.com.au> <20041209012915.GA16228@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041209012915.GA16228@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: nfs appears broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 01:44:27 -0000 On Wed, Dec 08, 2004 at 05:29:15PM -0800, Steve Kargl wrote: > On Thu, Dec 09, 2004 at 12:16:43PM +1100, John Birrell wrote: > > On Wed, Dec 08, 2004 at 04:43:35PM -0800, Steve Kargl wrote: > > > troutmask:root[201] mount /jumbo > > > [udp] jumbo:/data: RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed out > > > [udp] jumbo:/data: RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed out > > > > > > troutmask:root[203] grep jumbo /etc/fstab > > > jumbo:/data /jumbo nfs rw,noauto 0 0 > > > > > > > > > This is with world+kernel from about 30 minutes on amd64. I was > > > able to mount /jumbo with a kernel from monday. > > > > I updated a current machine yesterday and mountd complains about in invalid > > line in /etc/exports, saying that / isn't a mount point. The client reports > > "permission denied". > > > > I cvsup'd again today and the kernel panics before I can even get to try NFS. > > > > Do you have INET6 in your kernel? I had to remove it > or the kernel would panic. Fortunately, I don't need > INET6. No INET6. My kernel is pretty basic. The kernel has witness and invariants. The DDB trace shows: Tracing pid 159 tid 100047 td 0xc1592340 kdb_enter(c066578d,100,0,0,0) at kdb_enter+0x2c panic(c0680600,c068096e,d4047010,0,0) at panic+0x10s syscall(c1564cc00,c15c3680,c1564d00,c0709c40,c06c18c4) at syscall Process 159 is ifconfig. I have GDB in the kernel, but haven't connected a serial console to this machine before, so I'll need to hunt around for a cable and finish the upgrade of my desktop machine which I decided to clean and re-install all ports on yesterday. Bugger. -- John Birrell From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 02:25:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBCB316A4CE for ; Thu, 9 Dec 2004 02:25:26 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4CD643D55 for ; Thu, 9 Dec 2004 02:25:26 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 1EFB6512D0; Wed, 8 Dec 2004 18:31:55 -0800 (PST) Date: Wed, 8 Dec 2004 18:31:55 -0800 From: Kris Kennaway To: freebsd-current@freebsd.org, matthew.thyer@dsto.defence.gov.au Message-ID: <20041209023154.GA90315@xor.obsecurity.org> References: <20041208070454.GA11139@squash.dsto.defence.gov.au> <20041208084757.T1146@fledge.watson.org> <20041209012125.GA14557@squash.dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="azLHFNyN32YCQGCU" Content-Disposition: inline In-Reply-To: <20041209012125.GA14557@squash.dsto.defence.gov.au> User-Agent: Mutt/1.4.2.1i Subject: Re: panic: process 839(xmms):1 holds process lock but isn't blocked ona lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 02:25:27 -0000 --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Dec 09, 2004 at 11:51:28AM +1030, Wilkinson, Alex wrote: > Another panic whilst mp3s were playing on xmms: What scheduler? Kris --azLHFNyN32YCQGCU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBt7kZWry0BWjoQKURAimFAJ43P+fiMDQM8caYGmqyBpsE8O7OzQCgxhfc UY1X+v+yh2FRu37nkJ+YU4s= =1tZU -----END PGP SIGNATURE----- --azLHFNyN32YCQGCU-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 02:33:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB3F116A4CE; Thu, 9 Dec 2004 02:33:48 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 770CD43D54; Thu, 9 Dec 2004 02:33:48 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iB92VKPJ046478; Wed, 8 Dec 2004 21:31:20 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iB92VJKh046475; Thu, 9 Dec 2004 02:31:19 GMT (envelope-from robert@fledge.watson.org) Date: Thu, 9 Dec 2004 02:31:19 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Steve Kargl In-Reply-To: <20041209002303.GC4674@troutmask.apl.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: mlaier@freebsd.org Subject: protocol timer running before protocol is fully initialized (again) (was re: panic: mtx_lock() of spin mutex ...) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 02:33:48 -0000 On Wed, 8 Dec 2004, Steve Kargl wrote: > panic: mtx_lock() of spin mutex (null) @ sys/netinet/frag6.c:682 > cpuid = 0 > kdb_backtrace+0x37 > panic+0x1d1 > _mtx_lock_flags+0x72 > frag6_slowtimo+0x26 > pfslowtimo+0x5a > softclock+0x1c0 > ithread_loop+0x179 > fork_exit+0xe9 > fork_trampoline+0xe > > This is FreeBSD/amd64 from today's sources of about 30 minutes ago. >From the instant interpretation unit: it looks like this is another example of a protocl's timeout firing before the protocol is properly initialized, as the mutex appears to be zero'd due to being in BSS. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 03:10:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 69FC016A4CE; Thu, 9 Dec 2004 03:10:58 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED6B843D4C; Thu, 9 Dec 2004 03:10:57 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.207] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1CcEhk-0003AQ-00; Thu, 09 Dec 2004 04:10:56 +0100 Received: from [84.128.137.142] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1CcEhk-0002hQ-00; Thu, 09 Dec 2004 04:10:56 +0100 From: Max Laier To: freebsd-current@freebsd.org Date: Thu, 9 Dec 2004 04:11:26 +0100 User-Agent: KMail/1.7.1 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1551341.iXytlVmc3k"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412090411.42258.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 cc: gnn@freebsd.org cc: Robert Watson cc: Steve Kargl Subject: Re: protocol timer running before protocol is fully initialized (again) (was re: panic: mtx_lock() of spin mutex ...) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 03:10:58 -0000 --nextPart1551341.iXytlVmc3k Content-Type: multipart/mixed; boundary="Boundary-01=_jJ8tBMMl+ZnYkYB" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-01=_jJ8tBMMl+ZnYkYB Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 09 December 2004 03:31, Robert Watson wrote: > On Wed, 8 Dec 2004, Steve Kargl wrote: > > panic: mtx_lock() of spin mutex (null) @ sys/netinet/frag6.c:682 > > cpuid =3D 0 > > kdb_backtrace+0x37 > > panic+0x1d1 > > _mtx_lock_flags+0x72 > > frag6_slowtimo+0x26 > > pfslowtimo+0x5a > > softclock+0x1c0 > > ithread_loop+0x179 > > fork_exit+0xe9 > > fork_trampoline+0xe > > > > This is FreeBSD/amd64 from today's sources of about 30 minutes ago. > > > >From the instant interpretation unit: it looks like this is another > > example of a protocl's timeout firing before the protocol is properly > initialized, as the mutex appears to be zero'd due to being in BSS. Here is a lazy fix: http://people.freebsd.org/~mlaier/uipc_domain.c.lazy.diff Should help for (almost) sure. This fixes all domains that are initialized = in=20 SI_SUB_PROTO_DOMAIN, those that are initialized later on (netgraph e.g.) ca= n=20 still trigger this prime example why it's bad to hook something in before=20 initializing it properly. Unfortunately our code and API force us to do so = at=20 the moment :-\ Please tell me if the patch (apply to src/sys/kern/uipc_domain.c) helps. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --Boundary-01=_jJ8tBMMl+ZnYkYB Content-Type: text/x-diff; charset="iso-8859-1"; name="uipc_domain.c.lazy.diff" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="uipc_domain.c.lazy.diff" =3D=3D=3D=3D //depot/user/mlaier/carp2/sys/kern/uipc_domain.c#3 - /usr/stor= e/mlaier/p4/carp2/sys/kern/uipc_domain.c =3D=3D=3D=3D =2D-- /tmp/tmp.40917.0 Thu Dec 9 04:02:36 2004 +++ /usr/store/mlaier/p4/carp2/sys/kern/uipc_domain.c Thu Dec 9 03:43:12 2= 004 @@ -215,9 +215,6 @@ KASSERT(domain_init_status =3D=3D 0, ("domaininit called too late!")); domain_init_status =3D 1; mtx_unlock(&dom_mtx); =2D =2D callout_reset(&pffast_callout, 1, pffasttimo, NULL); =2D callout_reset(&pfslow_callout, 1, pfslowtimo, NULL); } =20 /* ARGSUSED*/ @@ -228,6 +225,9 @@ KASSERT(domain_init_status =3D=3D 1, ("domainfinalize called too late!")); domain_init_status =3D 2; mtx_unlock(&dom_mtx);=09 + + callout_reset(&pffast_callout, 1, pffasttimo, NULL); + callout_reset(&pfslow_callout, 1, pfslowtimo, NULL); } =20 struct protosw * --Boundary-01=_jJ8tBMMl+ZnYkYB-- --nextPart1551341.iXytlVmc3k Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBt8JuXyyEoT62BG0RAmfoAJ9wdQ8vP1vXWl8xUxMI2xTLvMM9RgCdEsAp 4ZHbOKicXf9vrfQcsXAI1Lg= =ydzf -----END PGP SIGNATURE----- --nextPart1551341.iXytlVmc3k-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 04:20:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 955DA16A4CE for ; Thu, 9 Dec 2004 04:20:41 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18B0343D39 for ; Thu, 9 Dec 2004 04:20:41 +0000 (GMT) (envelope-from Chrisst141@comcast.net) Received: from [172.16.2.9] (c-24-11-36-120.client.comcast.net[24.11.36.120]) by comcast.net (sccrmhc12) with ESMTP id <2004120904204001200c1uqae>; Thu, 9 Dec 2004 04:20:40 +0000 Message-ID: <41B7D294.7020801@Comcast.net> Date: Wed, 08 Dec 2004 23:20:36 -0500 From: Chris Stone User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20041209000200.BD1F616A4F2@hub.freebsd.org> In-Reply-To: <20041209000200.BD1F616A4F2@hub.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: HP D325 Panic Fault Trap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 04:20:41 -0000 I have a new HP D325 minitower with an Athlon XP 3000+ processor, 512 RAM, 40GB 7200 HD, CD-RW/DVD-Rom. If I try to boot a 5.2.1 based CD (Official Install or FreeSBIE) I get this message: FreeBSD/i386 Bootstrap loader, Revision 1.1 (root@nathan, Mon Feb 23 15:05:46 CET 2004) | int=0000000d err=00000000 efl=00030246 eip=0000249a eax=00002025 ebx=00000004 ecx=00002000 edx=0000a654 esi=000008d5 edi=0006290c ebp=00001516 esp=000014e0 cs=f000 ds=ede1 es=ede1 fs=0000 gs=0000 ss=ede1 cs:eip=0f 20 dd 81 e5 00 f0 0f-20 c2 0f 01 e0 a8 01 75 08 80 c2 fe e8 53 ff eb-21 0f 20 e0 a9 30 00 75 ss:esp=0c 29 06 00 d5 08 c0 00-16 15 00 00 00 15 00 00 04 00 00 00 54 a6 00 00-04 00 00 00 25 a6 00 00 BTX Halted If I use the 5.3 floppy I get get into the sysinstall by disabling ACPI. Once I have it installed and it tries to boot off the HD I get the same as above. If I do not disable ACPI when booting from the floppies the kernel starts and I get this: CPU: AMD Athlon XP 3000+ (remaining spec omitted) real memory = 469762048 (448 MB) avail memory = 445825024 (425 MB) Kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode Fault virtual address = 0x1c Fault code = Supervisor write, page not present Instruction pointer = 0x8:0xc075a5b0 Stack pointer = 0x10:0xc1021be0 Frame pointer = 0x10:0xc1021cac Code segment = base 0x0, Limit 0xfffff, Type 0x1b DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 Current process = 0 () Trap number = 12 Panic: page fault Uptime: 1s At that point it is totally frozen, no Ctrl+Alt+Del, no scrolling up or down, no nothing. Any ideas, hints, patches, bios settings; anything?? ~Chris From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 05:44:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A309D16A4CE for ; Thu, 9 Dec 2004 05:44:31 +0000 (GMT) Received: from mail.zrz.tu-berlin.de (mail.zrz.TU-Berlin.DE [130.149.4.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FDCB43D1F for ; Thu, 9 Dec 2004 05:44:31 +0000 (GMT) (envelope-from Peter.Ross@alumni.tu-berlin.de) Received: from localhost ([127.0.0.1] helo=mail.zrz.TU-Berlin.DE) by mail.zrz.tu-berlin.de with esmtp (exim-4.43) for id 1CcH6M-0006AS-KE; Thu, 09 Dec 2004 06:44:30 +0100 Received: from mail.zrz.TU-Berlin.DE ([130.149.4.15]) by mail.zrz.TU-Berlin.DE (MailMonitor for SMTP v1.2.2 ) ; Thu, 9 Dec 2004 06:44:30 +0100 (CET) Received: from mailbox.tu-berlin.de ([130.149.4.18]) by mail.zrz.tu-berlin.de with esmtp (exim-4.43) for id 1CcH6L-0006AE-MN; Thu, 09 Dec 2004 06:44:29 +0100 Received: from apache by mailbox.tu-berlin.de with local (exim-4.43) for id 1CcH6L-0007qz-Rq; Thu, 09 Dec 2004 06:44:29 +0100 Received: from 211.26.240.17 (SquirrelMail authenticated user rossicbb) by mailbox.TU-Berlin.DE with HTTP; Thu, 9 Dec 2004 16:44:29 +1100 (EST) Message-ID: <54038.211.26.240.17.1102571069.squirrel@mailbox.TU-Berlin.DE> Date: Thu, 9 Dec 2004 16:44:29 +1100 (EST) From: "Peter Ross" To: X-Priority: 3 Importance: Normal X-Mailer: SquirrelMail (version 1.2.8) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Sophos MailMonitor on mail.zrz.tu-berlin.de; Thu, 09 Dec 2004 06:44:30 +0100 Subject: Re: My project wish-list for the next 12 months X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 05:44:31 -0000 Scott Long, Wed Dec 1 14:02:28 PST 2004 > 5. Clustered FS support. SANs are all the rage these days, and > clustered filesystems that allow data to be distributed across many > storage enpoints and accessed concurrently through the SAN are very > powerful. RedHat recently bought Sistina and re-opened the GFS source > code, so exploring this would be very interesting. As we see there are some unfinished pieces (BTW: The freebsd-cluster list is very quiet). I browsed through some of them. It is difficult to judge how far they away from beeing mature. There is: 1) 2x AFS (BSD project, OpenAFS) 2) iSCSI The Lucent code Peter Blok seems to have some ideas comparable to mine when I started to play with iSCSI@FreeBSD when I was unemployed last year. (Unfortunatelly not long enough;-) My naive idea for network mirroring to get basic SAN multipath functionality is to combine vinum + iSCSI. Is it achievable? 3) NFSv4 NFS Version 4 is part of FreeBSD now. There is an idea to implement replication but AFAIK it is not implemented yet (I have to check). At least there is a whitepaper: http://www.citi.umich.edu/projects/nfsv4/reports/replication.pdf It could be used as a frontend for concurrent access (NFSv4 provides _real_ locking including byterange locking etc.) There are some ideas to implement concurrent access in UFS.. Is it the right place? (Hint: There are many Linux filesystems with beautiful features but it is hard to find a reliable one - possibly because the featuritis makes them too complex?) Maybe it is better to have one specialised filesystem (see Veritas as already mentioned). Or a layer above the "real" FS. BTW: AFAIK ReiserFS (suggested as a FreeBSD port) does not support ACLs.. Regards Peter From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 08:50:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8043A16A4CE for ; Thu, 9 Dec 2004 08:50:46 +0000 (GMT) Received: from smtp-1.dlr.de (smtp-1.dlr.de [129.247.247.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 61ABC43D46 for ; Thu, 9 Dec 2004 08:50:45 +0000 (GMT) (envelope-from Hartmut.Brandt@dlr.de) Received: from beagle.kn.op.dlr.de ([129.247.173.178]) by smtp-1.dlr.de over TLS secured channel with Microsoft SMTPSVC(5.0.2195.6713); Thu, 9 Dec 2004 09:50:43 +0100 Date: Thu, 9 Dec 2004 09:51:53 +0100 (CET) From: Harti Brandt X-X-Sender: brandt@beagle.kn.op.dlr.de To: Steve Kargl In-Reply-To: <20041209010658.GA14890@troutmask.apl.washington.edu> Message-ID: <20041209094923.B85802@beagle.kn.op.dlr.de> References: <20041209000148.GA4674@troutmask.apl.washington.edu> <20041209000710.GB4674@troutmask.apl.washington.edu> <20041209010658.GA14890@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 09 Dec 2004 08:50:43.0121 (UTC) FILETIME=[2A9CEA10:01C4DDCC] cc: freebsd-current@freebsd.org Subject: Re: make(1) is broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Harti Brandt List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 08:50:46 -0000 On Wed, 8 Dec 2004, Steve Kargl wrote: SK>On Wed, Dec 08, 2004 at 04:07:10PM -0800, Steve Kargl wrote: SK>> SK>> troutmask:root[225] find /usr/obj/ -name make.core SK>> /usr/obj/usr/src/sys/SPEW/make.core SK>> troutmask:root[226] gdb /usr/bin/make /usr/obj/usr/src/sys/SPEW/make.core SK>> SK>> #0 Lst_Remove (list=0x5580a0, ln=0x0) SK>> at /usr/src/usr.bin/make/lst.lib/lstRemove.c:74 SK>> 74 if (ln->nextPtr != NULL) SK>> (gdb) bt SK>> #0 Lst_Remove (list=0x5580a0, ln=0x0) SK>> at /usr/src/usr.bin/make/lst.lib/lstRemove.c:74 SK>> #1 0x00000000004052bb in Dir_Destroy (pp=0x81e780) SK>> at /usr/src/usr.bin/make/dir.c:1143 SK>> #2 0x0000000000405300 in Dir_ClearPath (path=0x5580a0) SK>> at /usr/src/usr.bin/make/dir.c:1172 SK>> #3 0x0000000000404283 in Dir_End () at /usr/src/usr.bin/make/dir.c:265 SK>> #4 0x000000000040a8da in main (argc=2, argv=0x7fffffffe3e0) SK>> at /usr/src/usr.bin/make/main.c:888 SK>> SK> SK>Looking at the diff between the 1.17 and 1.16, I suspect this chunk SK>of code in Lst_Remove: SK> SK>- if (!Lst_Valid(list) || !Lst_NodeValid(ln, list)) { SK>- return (FAILURE); SK>- } SK> SK>should have been replaced by SK> SK> if (list == NULL || ln == NULL) SK> return; I see no sense in those runtime checks because they just hide the real problems (as are uninitialized lists or removing items not on the list). Nobody actually checked the return codes so that was just 'close your eyes and continue'. I'd rather have the root problem fixed. I have a look into this. harti From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 10:09:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CEDA16A4CE for ; Thu, 9 Dec 2004 10:09:35 +0000 (GMT) Received: from smtp-1.dlr.de (smtp-1.dlr.de [129.247.247.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD56F43D46 for ; Thu, 9 Dec 2004 10:09:33 +0000 (GMT) (envelope-from Hartmut.Brandt@dlr.de) Received: from beagle.kn.op.dlr.de ([129.247.173.178]) by smtp-1.dlr.de over TLS secured channel with Microsoft SMTPSVC(5.0.2195.6713); Thu, 9 Dec 2004 11:09:32 +0100 Date: Thu, 9 Dec 2004 11:10:59 +0100 (CET) From: Harti Brandt X-X-Sender: brandt@beagle.kn.op.dlr.de To: Steve Kargl In-Reply-To: <20041209000148.GA4674@troutmask.apl.washington.edu> Message-ID: <20041209110942.F86222@beagle.kn.op.dlr.de> References: <20041209000148.GA4674@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 09 Dec 2004 10:09:32.0696 (UTC) FILETIME=[2DA8C980:01C4DDD7] cc: freebsd-current@freebsd.org Subject: Re: make(1) is broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Harti Brandt List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 10:09:35 -0000 On Wed, 8 Dec 2004, Steve Kargl wrote: SK>Well, it appears that -current is highly unstable at SK>the moment. In particularly, INET6 is causing a SK>panic, so I went to build a new kernel without it. I'm SK>now stuck with a broken make(1). SK> SK>make buildkernel yields SK> SK>make -V SFILES | MKDEP_CPP="cc -E" xargs mkdep -a -f .newdep -x assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding SK>rm -f .depend SK>mv .newdep .depend SK>*** Signal 11 SK> SK>Stop in /data/obj/usr/src/sys/SPEW. SK>*** Error code 1 SK> SK>Stop in /usr/src. SK>*** Error code 1 SK> SK>Stop in /usr/src. SK>troutmask:root[203] tail -1 /var/log/messages SK>Dec 8 15:58:39 troutmask kernel: pid 4794 (make), uid 0: exited on signal 11 SK> SK> SK>troutmask:root[204] uname -a SK>FreeBSD troutmask.apl.washington.edu 6.0-CURRENT FreeBSD 6.0-CURRENT #1: SK>Mon Dec 6 15:56:39 PST 2004 SK>kargl@dhcp-78-96.apl.washington.edu:/data/obj/usr/src/sys/SPEW amd64 Thanks for the report. This has been caused by make during clean-up to remove a path element that was never opened as a directory from the list of open directories. Fixed in rev. 1.43 of dir.c. harti From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 10:10:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE99116A4CE for ; Thu, 9 Dec 2004 10:10:43 +0000 (GMT) Received: from smtp-1.dlr.de (smtp-1.dlr.de [129.247.247.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B3F443D2D for ; Thu, 9 Dec 2004 10:10:43 +0000 (GMT) (envelope-from Hartmut.Brandt@dlr.de) Received: from beagle.kn.op.dlr.de ([129.247.173.178]) by smtp-1.dlr.de over TLS secured channel with Microsoft SMTPSVC(5.0.2195.6713); Thu, 9 Dec 2004 11:10:42 +0100 Date: Thu, 9 Dec 2004 11:12:11 +0100 (CET) From: Harti Brandt X-X-Sender: brandt@beagle.kn.op.dlr.de To: Mike Hunter In-Reply-To: <20041209003443.GA19328@ack.Berkeley.EDU> Message-ID: <20041209111146.N86222@beagle.kn.op.dlr.de> References: <20041209002430.GA18622@ack.Berkeley.EDU> <20041209003443.GA19328@ack.Berkeley.EDU> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 09 Dec 2004 10:10:42.0291 (UTC) FILETIME=[57242430:01C4DDD7] cc: freebsd-current@freebsd.org cc: Steve Kargl Subject: Re: coredump while trying to build world (2004.12.08.1600-0800 src) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Harti Brandt List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 10:10:43 -0000 On Wed, 8 Dec 2004, Mike Hunter wrote: MH>On Dec 08, "Steve Kargl" wrote: MH> MH>> On Wed, Dec 08, 2004 at 04:24:30PM -0800, Mike Hunter wrote: MH>> > Hi, MH>> > MH>> > I'm trying to go from RELENG_5 to HEAD on my new amd64, but I'm bombing MH>> > out here: MH>> > MH>> > cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe -DMAGIC='"/usr/share/misc/magic"' -DBUILTIN_ELF -DELFCORE -DHAVE_CONFIG_H -I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file -c /usr/src/lib/libmagic/../../contrib/file/softmagic.c -o softmagic.So MH>> > building shared library libmagic.so.1 MH>> > Segmentation fault (core dumped) MH>> > *** Error code 139 MH>> > MH>> MH>> You need to back out the recent changes to make(1). MH>> In your supfile file that you use with cvsup, set MH>> MH>> *default date=2004.11.08.00.00.00 MH>> src-usrbin MH>> MH>> cd /usr/src/usr.bin/make MH>> make MH>> make install MH> MH>Thank you for the detailed help! I'll let you know if it doesn't work MH>(currently up against the cvs access limit :| ). Fixed in rev. 1.43 of dir.c harti From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 10:15:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3EB616A4CE; Thu, 9 Dec 2004 10:15:27 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id A725643D46; Thu, 9 Dec 2004 10:15:26 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB9AFPFD042498; Thu, 9 Dec 2004 12:15:25 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 05238-10; Thu, 9 Dec 2004 12:15:24 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB9AFORQ042494 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Dec 2004 12:15:24 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iB9AFO7N062709; Thu, 9 Dec 2004 12:15:24 +0200 (EET) (envelope-from ru) Date: Thu, 9 Dec 2004 12:15:24 +0200 From: Ruslan Ermilov To: Max Laier Message-ID: <20041209101524.GC62331@ip.net.ua> References: <200412090411.42258.max@love2party.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0eh6TmSyL6TZE2Uz" Content-Disposition: inline In-Reply-To: <200412090411.42258.max@love2party.net> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: gnn@freebsd.org cc: freebsd-current@freebsd.org cc: Robert Watson cc: Steve Kargl Subject: Re: protocol timer running before protocol is fully initialized (again) (was re: panic: mtx_lock() of spin mutex ...) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 10:15:27 -0000 --0eh6TmSyL6TZE2Uz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Max, On Thu, Dec 09, 2004 at 04:11:26AM +0100, Max Laier wrote: > On Thursday 09 December 2004 03:31, Robert Watson wrote: > > On Wed, 8 Dec 2004, Steve Kargl wrote: > > > panic: mtx_lock() of spin mutex (null) @ sys/netinet/frag6.c:682 > > > cpuid =3D 0 > > > kdb_backtrace+0x37 > > > panic+0x1d1 > > > _mtx_lock_flags+0x72 > > > frag6_slowtimo+0x26 > > > pfslowtimo+0x5a > > > softclock+0x1c0 > > > ithread_loop+0x179 > > > fork_exit+0xe9 > > > fork_trampoline+0xe > > > > > > This is FreeBSD/amd64 from today's sources of about 30 minutes ago. > > > > > >From the instant interpretation unit: it looks like this is another > > > > example of a protocl's timeout firing before the protocol is properly > > initialized, as the mutex appears to be zero'd due to being in BSS. >=20 > Here is a lazy fix: > http://people.freebsd.org/~mlaier/uipc_domain.c.lazy.diff >=20 > Should help for (almost) sure. This fixes all domains that are initialize= d in=20 > SI_SUB_PROTO_DOMAIN, those that are initialized later on (netgraph e.g.) = can=20 > still trigger this prime example why it's bad to hook something in before= =20 > initializing it properly. Unfortunately our code and API force us to do s= o at=20 > the moment :-\ >=20 > Please tell me if the patch (apply to src/sys/kern/uipc_domain.c) helps. >=20 I've got the same panic early on boot, but in ip_input(), on i386. Your patch helps. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --0eh6TmSyL6TZE2Uz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBuCW8qRfpzJluFF4RAhgFAJ96SsxXyyuSwLbnvfPPp2Z8JYOdKwCgjI+S +DCfDmYsUbxqYl6SjtgF3Qg= =Gda9 -----END PGP SIGNATURE----- --0eh6TmSyL6TZE2Uz-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 11:33:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5B6D16A4CE; Thu, 9 Dec 2004 11:33:35 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1801A43D49; Thu, 9 Dec 2004 11:33:35 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.162] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1CcMY9-0004Cl-00; Thu, 09 Dec 2004 12:33:33 +0100 Received: from [84.128.137.142] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1CcMY9-0006mc-00; Thu, 09 Dec 2004 12:33:34 +0100 From: Max Laier To: Ruslan Ermilov Date: Thu, 9 Dec 2004 12:34:08 +0100 User-Agent: KMail/1.7.1 References: <200412090411.42258.max@love2party.net> <20041209101524.GC62331@ip.net.ua> In-Reply-To: <20041209101524.GC62331@ip.net.ua> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1178026.9nY22vnAXz"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412091234.19912.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 cc: gnn@freebsd.org cc: freebsd-current@freebsd.org cc: Robert Watson cc: Steve Kargl Subject: Re: protocol timer running before protocol is fully initialized (again) (was re: panic: mtx_lock() of spin mutex ...) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 11:33:35 -0000 --nextPart1178026.9nY22vnAXz Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Ruslan, On Thursday 09 December 2004 11:15, Ruslan Ermilov wrote: > Hi Max, > > On Thu, Dec 09, 2004 at 04:11:26AM +0100, Max Laier wrote: > > On Thursday 09 December 2004 03:31, Robert Watson wrote: > > > On Wed, 8 Dec 2004, Steve Kargl wrote: > > > > panic: mtx_lock() of spin mutex (null) @ sys/netinet/frag6.c:682 > > > > cpuid =3D 0 > > > > kdb_backtrace+0x37 > > > > panic+0x1d1 > > > > _mtx_lock_flags+0x72 > > > > frag6_slowtimo+0x26 > > > > pfslowtimo+0x5a > > > > softclock+0x1c0 > > > > ithread_loop+0x179 > > > > fork_exit+0xe9 > > > > fork_trampoline+0xe > > > > > > > > This is FreeBSD/amd64 from today's sources of about 30 minutes ago. > > > > > > > >From the instant interpretation unit: it looks like this is another > > > > > > example of a protocl's timeout firing before the protocol is properly > > > initialized, as the mutex appears to be zero'd due to being in BSS. > > > > Here is a lazy fix: > > http://people.freebsd.org/~mlaier/uipc_domain.c.lazy.diff > > > > Should help for (almost) sure. This fixes all domains that are > > initialized in SI_SUB_PROTO_DOMAIN, those that are initialized later on > > (netgraph e.g.) can still trigger this prime example why it's bad to ho= ok > > something in before initializing it properly. Unfortunately our code and > > API force us to do so at the moment :-\ > > > > Please tell me if the patch (apply to src/sys/kern/uipc_domain.c) helps. > > I've got the same panic early on boot, but in ip_input(), on i386. > Your patch helps. in ip_input() - that's not good! Can you send me the trace? I was under the= =20 impression that net send and esp. reveice is off during this part of the=20 initialization. Crashing ip_input() would question that assumption. Thanks. Anyway, have enough "working for me" by now. Will commit the temporary fix. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1178026.9nY22vnAXz Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBuDg7XyyEoT62BG0RAn/IAJ9EEGZeSi07aLkreBF4wrQ73figXgCfdwYq XXVqE+BSznlgx3+OZVTgnKw= =zr7M -----END PGP SIGNATURE----- --nextPart1178026.9nY22vnAXz-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 11:39:39 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12F2516A4CE; Thu, 9 Dec 2004 11:39:39 +0000 (GMT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id C57EA43D45; Thu, 9 Dec 2004 11:39:38 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from h00609772adf0.ne.client2.attbi.com ([66.30.114.143]) by comcast.net (rwcrmhc13) with ESMTP id <2004120911393701500e5jjae>; Thu, 9 Dec 2004 11:39:37 +0000 Received: from h00609772adf0.ne.client2.attbi.com (localhost [127.0.0.1]) iB9BdZIg001098; Thu, 9 Dec 2004 06:39:36 -0500 (EST) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: (from rodrigc@localhost)iB9BdZoo001097; Thu, 9 Dec 2004 06:39:35 -0500 (EST) (envelope-from rodrigc) Date: Thu, 9 Dec 2004 06:39:34 -0500 From: Craig Rodrigues To: Pav Lucistnik Message-ID: <20041209113934.GA1022@crodrigues.org> References: <20040923032045.GA52428@crodrigues.org> <20041201.143909.971160851.chat95@mac.com> <20041201063204.GA6754@crodrigues.org> <1101892801.51033.6.camel@pav.hide.vol.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1101892801.51033.6.camel@pav.hide.vol.cz> User-Agent: Mutt/1.4.1i cc: NAKATA Maho cc: freebsd-current@FreeBSD.org Subject: Re: REPORT_KEY ILLEGAL REQUEST: encrypted DVD's under FreeBSD? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 11:39:39 -0000 On Wed, Dec 01, 2004 at 10:20:01AM +0100, Pav Lucistnik wrote: > > > > acd0: FAILURE - REPORT_KEY ILLEGAL REQUEST asc=0x6f ascq=0x04 error=4 > > > > > > > > This is my brand of DVD player: > > > > acd0: CDRW drive at ata0 as slave > > > > > > I also encountered the exact problem. > > > acd0: DVDR at ata1-master UDMA33 > > > > Hi, > > > > Garrett Wollman explained this quite nicely to me. > > In the MMC-3 standard (SCSI) at T10.org, there is a > > standard section on sense codes: > > > > 6F/04 R MEDIA REGION CODE IS MISMATCHED TO LOGICAL UNIT REGION > > I had good results with FreeDOS bootup from CD-ROM, then swapping CDs > for a second one with DOS based Mediatek flashing utility and firmware > image. I could whip up a page with downloads and instructions, but it's > all easily googlabe. Look for bootdisk.iso, MTKFLASH.EXE and BIN > firmwares (unofficial). Thanks for the tip. I actually did two things. I got a Windows-based firmware updating utility my Lite-ON LDW-811S from Lite-ON: http://www.liteonit.com/ODD/English/e_downloads/e_firmware_dvd%20rw.asp That worked, but it did not seem to help. The next thing I did was I obtained a DOS based utility called LtnRPCDOS to examine the region code of the drive: http://dhc014.rpc1.org/LtnRPC/ According to that utility, my drive is Region 1 (North America), so since I live in the U.S., that should work. The utility also reported that I could change the region code 5 more times, so it had not been previously reset. The next thing I did was to put the following line in /boot/loader.conf: hw.ata.atapi_dma="0" That seemed to make things better. I still seem to get the 6F/04 (REPORT_KEY ILLEGAL REQUEST) errors, but I now seem to be able to play DVD's which I could not play before. I will try to test this out with some more DVD's. -- Craig Rodrigues rodrigc@crodrigues.org From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 11:41:14 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3DCF216A4CE for ; Thu, 9 Dec 2004 11:41:14 +0000 (GMT) Received: from amsfep17-int.chello.nl (amsfep17-int.chello.nl [213.46.243.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0512543D41 for ; Thu, 9 Dec 2004 11:41:13 +0000 (GMT) (envelope-from Danovitsch@vitsch.net) Received: from Vitsch.net ([212.187.83.215]) by amsfep17-int.chello.nl (InterMail vM.6.01.03.04 201-2131-111-106-20040729) with ESMTP id <20041209114110.SWLP84.amsfep17-int.chello.nl@Vitsch.net>; Thu, 9 Dec 2004 12:41:10 +0100 Received: from localhost.Danovitsch.LAN (b83007.upc-b.chello.nl [212.83.83.7]) by Vitsch.net (8.12.3p2/8.11.3) with ESMTP id iB9BeLeD076207; Thu, 9 Dec 2004 12:40:23 +0100 (CET) (envelope-from Danovitsch@vitsch.net) From: "Daan Vreeken [PA4DAN]" To: Hideyuki KURASHINA Date: Thu, 9 Dec 2004 12:41:02 +0100 User-Agent: KMail/1.7 References: <200412081109.43840.sam@errno.com> <20041209.100008.21874313.rushani@bl.mmtr.or.jp> In-Reply-To: <20041209.100008.21874313.rushani@bl.mmtr.or.jp> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412091241.02372.Danovitsch@vitsch.net> cc: FreeBSD-current@FreeBSD.org Subject: Re: WEP does not work? (was Re: HEADSUP: ath updates) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 11:41:14 -0000 On Thursday 09 December 2004 02:00, Hideyuki KURASHINA wrote: > Hi, > > First of all, I would like to thank your hard work. That's great! > I decided to track HEAD rather than RELENG_5 with my new laptop. > Here is my environment: > > Access Point: PRISM3 on NetBSD 2.0 box > Client: Atheros 5212 on FreeBSD 6.0 laptop > > >>> On Wed, 8 Dec 2004 11:09:43 -0800, Sam Leffler said: > > > > I just committed updates for the ath driver and the ath hal. There are > > many changes to this code including a split of the tx rate control > > algorithm into a separate module. This means that when statically > > configuring the driver you now need to specify: > > > > device ath > > device ath_hal > > device ath_rate_onoe > > I compiled kernel including above devices and with > > device wlan > device wlan_wep > > then installed new kernel and ifconfig (dmesg from boot -v is attached). > > After rebooting, I set IPv4 and IPv6 addresses and those routes. Because > access point supports only 802.11b, I configured my wireless network > by 128bit WEP as follows > > /sbin/ifconfig ath0 nwid MY-SSID nwkey 0x01234567890123456789012345 media > autoselect mode 11b > > then I got following error: > > ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) > ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) > ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) > ath0: ath_chan_set: unable to reset channel 12 (2467 Mhz) > > It seems that ath0 failed to reset channel. I manually specified channel, > then ifconfig shows: > > # ifconfig -v ath0 > ath0: flags=8843 mtu 1500 > inet 192.168.1.11 netmask 0xffffff00 broadcast 192.168.1.255 > inet6 fe80::20e:XXXX:XXXX:XXXX%ath0 prefixlen 64 scopeid 0x2 > inet6 2001:3e0:XX:X::XX prefixlen 64 > ether 00:0e:9b:XX:XX:XX > media: IEEE 802.11 Wireless Ethernet autoselect mode 11b (DS/11Mbps) > status: associated > ssid MY-SSID channel 3 (2422) bssid 00:90:cc:XX:XX:XX > authmode OPEN privacy ON deftxkey 1 powersavemode OFF > powersavesleep 100 txpowmax 14 txpower 60 rtsthreshold 2312 protmode CTS > wme roaming AUTO bintval 100 > AC_BE cwmin 5 cwmax 10 aifs 3 txopLimit 0 -acm ack > cwmin 5 cwmax 10 aifs 3 txopLimit 0 -acm > AC_BK cwmin 5 cwmax 10 aifs 7 txopLimit 0 -acm ack > cwmin 5 cwmax 10 aifs 7 txopLimit 0 -acm > AC_VI cwmin 4 cwmax 5 aifs 2 txopLimit 188 -acm ack > cwmin 4 cwmax 5 aifs 2 txopLimit 188 -acm > AC_VO cwmin 3 cwmax 4 aifs 2 txopLimit 102 -acm ack > cwmin 3 cwmax 4 aifs 2 txopLimit 102 -acm > > # ifconfig ath0 list chan > Channel 1 : 2412* Mhz 11g Channel 11 : 2462* Mhz 11g > Channel 2 : 2417* Mhz 11g Channel 12 : 2467* Mhz 11a 11g > Channel 3 : 2422* Mhz 11g Channel 13 : 2472* Mhz 11g > Channel 4 : 2427* Mhz 11g Channel 14 : 2484* Mhz 11b > Channel 5 : 2432* Mhz 11g Channel 16 : 5080* Mhz 11a > Channel 6 : 2437* Mhz 11g Channel 34 : 5170* Mhz 11a > Channel 7 : 2442* Mhz 11g Channel 38 : 5190* Mhz 11a > Channel 8 : 2447* Mhz 11a 11g Channel 42 : 5210* Mhz 11a > Channel 9 : 2452* Mhz 11g Channel 46 : 5230* Mhz 11a > Channel 10 : 2457* Mhz 11g > > # ifconfig ath0 list scan > SSID BSSID CHAN RATE S:N INT CAPS > MY-SSID 00:90:cc:XX:XX:XX 3 11M 43:0 100 EP > > Unfortunately, this does not work (default router is not reachable). Have you tried : ifconfig ath0 wepmode on after setting the wep key? > > # ping -n 192.168.1.254 > PING 192.168.1.254 (192.168.1.254): 56 data bytes > ping: sendto: Host is down > ping: sendto: Host is down > ping: sendto: Host is down > ping: sendto: Host is down > ping: sendto: Host is down > ping: sendto: Host is down > ping: sendto: Host is down > ping: sendto: Host is down > ^C > --- 192.168.1.254 ping statistics --- > 14 packets transmitted, 0 packets received, 100% packet loss > > Disabling WEP on both access point and client is OK: > > # ping -n 192.168.1.254 > PING 192.168.1.254 (192.168.1.254): 56 data bytes > 64 bytes from 192.168.1.254: icmp_seq=0 ttl=255 time=3.773 ms > 64 bytes from 192.168.1.254: icmp_seq=1 ttl=255 time=1.513 ms > 64 bytes from 192.168.1.254: icmp_seq=2 ttl=255 time=1.362 ms > 64 bytes from 192.168.1.254: icmp_seq=3 ttl=255 time=1.774 ms > ^C > --- 192.168.1.254 ping statistics --- > 4 packets transmitted, 4 packets received, 0% packet loss > round-trip min/avg/max/stddev = 1.362/2.106/3.773/0.974 ms > > Am I missing something? Same configuration worked file with FreeBSD > 5.3-RELEASE on this laptop. > > -- rushani grtz, Daan From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 12:17:17 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2156016A4CE for ; Thu, 9 Dec 2004 12:17:17 +0000 (GMT) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.FreeBSD.org (Postfix) with SMTP id 9331543D39 for ; Thu, 9 Dec 2004 12:17:16 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 79786 invoked from network); 9 Dec 2004 08:27:22 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 9 Dec 2004 08:27:22 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iB98RL1a044593 for ; Thu, 9 Dec 2004 09:27:21 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iB98RLJ5044592 for current@freebsd.org; Thu, 9 Dec 2004 09:27:21 +0100 (CET) (envelope-from pho) Date: Thu, 9 Dec 2004 09:27:21 +0100 From: Peter Holm To: current@freebsd.org Message-ID: <20041209082721.GA44545@peter.osted.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: panic: sleeping thread (pid 13224) owns a non-sleepable lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 12:17:17 -0000 I can't seem to remember status of this problem? I get a lot of these lately during stress test: http://www.holm.cc/stress/log/cons93.html -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 12:36:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C1B716A4CE; Thu, 9 Dec 2004 12:36:43 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCE9F43D4C; Thu, 9 Dec 2004 12:36:39 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iB9CaXLO010201; Thu, 9 Dec 2004 23:06:33 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Thu, 9 Dec 2004 23:06:24 +1030 User-Agent: KMail/1.7.1 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1205150.sf6evmOIZK"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412092306.31353.doconnor@gsoft.com.au> X-Spam-Score: -3 () MIME_LONG_LINE_QP,PGP_SIGNATURE_2,SPAM_PHRASE_00_01,SUPERLONG_LINE,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: sam@freebsd.org Subject: if_ndis is broken with recent 802.11 changes X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 12:36:43 -0000 --nextPart1205150.sf6evmOIZK Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, The recent mega commit to the 802.11 stuff has broken if_ndis.. [inchoate 23:02] /usr/src/sys/modules/if_ndis >make Warning: Object directory not changed from original /usr/src/sys/modules/if= _ndis cc -O2 -fno-strict-aliasing -pipe -D_KERNEL -DKLD_MODULE -nostdinc -I- -= I. -I@ -I@/contrib/altq -I@/../include -finline-limit=3D8000 -fno-common -= mno-align-long-strings -mpreferred-stack-boundary=3D2 -ffreestanding -Wall = =2DWredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototy= pes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=3Dc99 -c= /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c: In function `ndis= _setstate_80211': /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c:1541: error: struc= ture has no member named `ic_wep_mode' /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c:1541: error: `IEEE= 80211_WEP_8021X' undeclared (first use in this function) /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c:1541: error: (Each= undeclared identifier is reported only once /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c:1541: error: for e= ach function it appears in.) /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c:1542: error: struc= ture has no member named `ic_wep_mode' /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c: In function `ndis= _media_status': /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c:1708: error: `IEEE= 80211_MODE_TURBO' undeclared (first use in this function) *** Error code 1 Stop in /usr/src/sys/modules/if_ndis. If it matters I am using the following driver=20 http://ftp.us.dell.com/network/R73206.EXE (w70n51.*) I have rev 1.72 of if_ndis.c. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1205150.sf6evmOIZK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBuEbP5ZPcIHs/zowRApbaAJ9PyG5OQ75FZNfXbLoXRtdW50TPbQCfUfb8 Ly8+eRWoKCC1eY5c2ldHclw= =P1XC -----END PGP SIGNATURE----- --nextPart1205150.sf6evmOIZK-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 12:40:19 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDE0A16A4CE; Thu, 9 Dec 2004 12:40:19 +0000 (GMT) Received: from relay.bestcom.ru (relay.bestcom.ru [217.72.144.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C61643D5C; Thu, 9 Dec 2004 12:40:18 +0000 (GMT) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (root@cell.sick.ru [217.72.144.68]) by relay.bestcom.ru (8.13.1/8.12.9) with ESMTP id iB9CeGdG031345 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 9 Dec 2004 15:40:17 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.11/8.12.8) with ESMTP id iB9CeF97097114 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Dec 2004 15:40:16 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id iB9CeFKQ097113; Thu, 9 Dec 2004 15:40:15 +0300 (MSK) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@freebsd.org using -f Date: Thu, 9 Dec 2004 15:40:15 +0300 From: Gleb Smirnoff To: current@freebsd.org, stable@freebsd.org Message-ID: <20041209124015.GA97077@cell.sick.ru> References: <20041202151048.GA33485@cell.sick.ru> <20041207124154.GA76825@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20041207124154.GA76825@cell.sick.ru> User-Agent: Mutt/1.5.6i X-Virus-Scanned: clamd / ClamAV version devel-20041013, clamav-milter version 0.75l on 127.0.0.1 X-Virus-Status: Clean Subject: Re: [TEST] ng_bridge ng_l2tp ng_lmi X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 12:40:20 -0000 The list of untested nodes has been narrowed down to the following three: ng_bridge, ng_l2tp, ng_lmi Please, if you use one of these three test this patch: http://people.freebsd.org/~glebius/totest/netgraph_callout T> On Thu, Dec 02, 2004 at 06:10:48PM +0300, Gleb Smirnoff wrote: T> T> Dear collegues, T> T> T> T> we are working on making netgraph ISR mpsafe. To do it we need to T> T> fix all (ab)users of bare timeout(9) in src/sys/netgraph. These T> T> timeout calls are running in synch with netgraph now because timeout(9) T> T> is Giant-locked. As soon as we mark ISR mpsafe, they are going to break. T> T> T> T> This patch semi-mechanically changes all timeout(9) calls to ng_callout(9), T> T> which runs scheduled callouts in netgraph context: T> T> T> T> http://people.freebsd.org/~glebius/totest/netgraph_callout T> T> T> T> It can be applied to HEAD or RELENG_5 (not 5.3-RELEASE). It patches T> T> the following nodes: T> T> T> T> ng_bridge.c T> T> ng_l2tp.c T> T> ng_lmi.c T> T> ng_ppp.c T> T> ng_pppoe.c T> T> ng_tty.c T> T> T> T> If you are using at least one of them, then I'm asking you to test the T> T> patch and respond. Thanks in advance! T> T> T> T> P.S. Sorry for crossposting. The target users are both RELENG_5 and CURRENT. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 17:05:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 33E5E16A4CE; Wed, 8 Dec 2004 17:05:58 +0000 (GMT) Received: from harik.murex.com (mail.murex.com [194.98.239.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id A19F843D46; Wed, 8 Dec 2004 17:05:57 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from interscan.fr.murex.com (iscan.murex.fr [172.21.17.207] (may be forged)) by harik.murex.com with ESMTP id iB8Gw7ka006209; Wed, 8 Dec 2004 17:58:07 +0100 (CET) Received: from mxmail.murex.com (interscan.murex.fr [127.0.0.1]) by interscan.fr.murex.com (8.11.6/8.11.6) with ESMTP id iB8HTTs28276; Wed, 8 Dec 2004 18:29:29 +0100 Received: from mteterin.us.murex.com ([172.21.130.86]) by mxmail.murex.com with Microsoft SMTPSVC(6.0.3790.0); Wed, 8 Dec 2004 18:05:30 +0100 From: Mikhail Teterin Organization: Virtual Estates, Inc. Date: Wed, 8 Dec 2004 12:05:38 -0500 User-Agent: KMail/1.7.1 To: freebsd-current@FreeBSD.org, freebsd-amd64@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-u" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412081205.39354.mi+mx@aldan.algebra.com> X-OriginalArrivalTime: 08 Dec 2004 17:05:31.0028 (UTC) FILETIME=[1F924540:01C4DD48] X-Mailman-Approved-At: Thu, 09 Dec 2004 12:58:04 +0000 cc: ade@FreeBSD.org cc: Kris Kennaway Subject: new TCL vs. current-6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 17:05:58 -0000 Three of my TCL-based ports fail now on amd64 running current-6. All failures occur, when an attempt is made to use the TCL-interpreter -- either to run the port's self-tests, or to generate the manual pages. The failures are either "Floating point exceptions" or "Segmentation faults" and appear to only happen on amd64 (may be, on ia64 as well): http://people.freebsd.org/~fenner/errorlogs/mi%40aldan.algebra.com.html Can anyone confirm being able to use freshly built TCL on amd64 _at all_? My ports did not change in months -- what could be wrong with TCL and/or amd64? Thanks! -mi From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 17:40:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84A4916A4CE for ; Wed, 8 Dec 2004 17:40:52 +0000 (GMT) Received: from gw02.mail.saunalahti.fi (gw02.mail.saunalahti.fi [195.197.172.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4328743D58 for ; Wed, 8 Dec 2004 17:40:52 +0000 (GMT) (envelope-from koston@iki.fi) Received: from norsu.kameli.org (YZCXLIII.dsl.saunalahti.fi [85.76.34.44]) by gw02.mail.saunalahti.fi (Postfix) with SMTP id 4EAC887A58 for ; Wed, 8 Dec 2004 19:40:51 +0200 (EET) Received: by norsu.kameli.org (sSMTP sendmail emulation); Wed, 8 Dec 2004 18:20:22 +0200 From: "Atte Peltomaki" Date: Wed, 8 Dec 2004 18:20:22 +0200 To: current@freebsd.org Message-ID: <20041208162022.GA2968@norsu.kameli.org> References: <20041207234840.7287cdf4@maya.liquidx.org> <1102506431.1090.8.camel@taxman> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1102506431.1090.8.camel@taxman> User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Thu, 09 Dec 2004 12:58:04 +0000 Subject: Re: FreeBSD sound distortion problems with SB Live! fixed with PREEMPTION X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 17:40:52 -0000 > > To my amazement, it worked completely. Enabling PREEMPTION in the kernel > > completely "fixes" this problem to the fullest extent. I have not been > > able to reproduce the problem since using any of the methods described > > above. > > > > I'm hoping that with this new information someone might be able to > > figure out what is truly causing this problem and can come up with a > > solution (or is PREEMPTION a good solution?). It seems that only a > > handful of drivers (emu10k1 is the one I'm having problems with) have > > this problem. For the record, I am not the only one who has reported > > this problem to the lists. > > I also experience the same problems with sound you've described. > > As PREEMPTION seems to stable for you, I tried to turn it on again. > > Unfortunately PREEMPTION remains to be completely unusable for me. The > system freezes within 5 minutes. > > The problem is described here: > http://lists.freebsd.org/pipermail/freebsd-current/2004-September/037949.html > > I wonder if no one else gets this kind of problem. Last I was running -current, PREEMPTION was just brought back, but it remained completely unusable for me too. Complete system freeze with no panic, in matter of minutes. -Atte From owner-freebsd-current@FreeBSD.ORG Wed Dec 8 16:24:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7CD7F16A4CE for ; Wed, 8 Dec 2004 16:24:46 +0000 (GMT) Received: from sloth.wcug.wwu.edu (sloth.wcug.wwu.edu [140.160.139.223]) by mx1.FreeBSD.org (Postfix) with SMTP id 36A7943D31 for ; Wed, 8 Dec 2004 16:24:46 +0000 (GMT) (envelope-from cjohnson@wcug.wwu.edu) Received: (qmail 7740 invoked by uid 1089); 8 Dec 2004 17:38:29 -0000 From: cjohnson@wcug.wwu.edu Date: Wed, 8 Dec 2004 09:38:29 -0800 To: freebsd-current@freebsd.org Message-ID: <20041208173829.GA7645@wcug.wwu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i X-Mailman-Approved-At: Thu, 09 Dec 2004 12:58:22 +0000 Subject: Microsoft Wireless Intellimouse Explorer X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Dec 2004 16:24:46 -0000 I'd like to help get my Microsoft Wireless Intellimouse Explorer working under 5.3-RELEASE. I've installed 5.3-RELEASE (x86) and updated to about 3 AM PST with the GENERIC kernel, and the mouse is recognized as ums0: ums0: Microsoft Microsoft Wireless Intellimouse Explorer\M-. 1.0A, rev 1.10/0.0e, addr 2, iclass 3/1 ums0: 5 buttons and Z dir. So the driver sees it, but I can't get much output from the mouse. moused starts and sees the device, but I'm unable to move the cursor in X or on the console. If I kill off moused and point X at /dev/ums0, X can't open the device and I get the message: usbd_setup_pipe: failed to start endpoint, TIMEOUT I've also tried ' moused -p /dev/ums0 -i all ' after killing off moused and I get: moused: unable to open /dev/ums0: Input/output error I've got about two weeks to poke and prod and I'd like to work with someone to get this mouse working. I'd rather not have to have a separate mouse for FreeBSD than for Windows XP. (And as an odd side note: it works in Solaris 10 (x86), though Solaris won't install properly on this machine.) Any help would be appreciated. I can provide remote access if needed. -- Chris Johnson cjohnson@wcug.wwu.edu Tua toga suspina est. From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 00:11:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 201E716A4CE; Thu, 9 Dec 2004 00:11:13 +0000 (GMT) Received: from area51.capnet.state.tx.us (area51.capnet.state.tx.us [141.198.193.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id D084D43D1D; Thu, 9 Dec 2004 00:11:12 +0000 (GMT) (envelope-from trorki@area51.capnet.state.tx.us) Received: from area51.capnet.state.tx.us (localhost.capnet.state.tx.us [127.0.0.1])iB909JHY029515; Wed, 8 Dec 2004 18:09:19 -0600 (CST) (envelope-from trorki@area51.capnet.state.tx.us) Received: from localhost (stu@localhost)iB909Gu6029512; Wed, 8 Dec 2004 18:09:18 -0600 (CST) X-Authentication-Warning: area51.capnet.state.tx.us: stu owned process doing -bs Date: Wed, 8 Dec 2004 18:09:16 -0600 (CST) From: trorki@area51.capnet.state.tx.us X-X-Sender: stu@area51.capnet.state.tx.us To: Mikhail Teterin In-Reply-To: <200412081205.39354.mi+mx@aldan.algebra.com> Message-ID: <20041208180601.T29045@area51.capnet.state.tx.us> References: <200412081205.39354.mi+mx@aldan.algebra.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Thu, 09 Dec 2004 13:00:56 +0000 cc: freebsd-current@freebsd.org cc: ade@freebsd.org cc: freebsd-amd64@freebsd.org cc: Kris Kennaway Subject: Re: new TCL vs. current-6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: trorki@area51.capnet.state.tx.us List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 00:11:13 -0000 On Wed, 8 Dec 2004, Mikhail Teterin wrote: > Three of my TCL-based ports fail now on amd64 running current-6. All failures > occur, when an attempt is made to use the TCL-interpreter -- either to run > the port's self-tests, or to generate the manual pages. The failures are > either "Floating point exceptions" or "Segmentation faults" and appear to > only happen on amd64 (may be, on ia64 as well): > http://people.freebsd.org/~fenner/errorlogs/mi%40aldan.algebra.com.html > Can anyone confirm being able to use freshly built TCL on amd64 _at all_? > My ports did not change in months -- what could be wrong with TCL and/or > amd64? I just build expect a few minutes ago on: FreeBSD rc.capnet.state.tx.us 5.3-RELEASE FreeBSD 5.3-RELEASE #1: Wed Dec 8 11:39:15 CST 2004 stu@rc.capnet.state.tx.us:/usr/obj/usr/src/sys/SMP amd64 and it seems to work fine, though I haven't pushed it. Let me know if you need specific tests. I can do a -current tomorrow, possibly. stu From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 13:51:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 359AB16A4CE for ; Thu, 9 Dec 2004 13:51:28 +0000 (GMT) Received: from wasley.bl.mmtr.or.jp (wasley.bl.mmtr.or.jp [210.228.173.142]) by mx1.FreeBSD.org (Postfix) with SMTP id AC77B43D39 for ; Thu, 9 Dec 2004 13:51:25 +0000 (GMT) (envelope-from rushani@bl.mmtr.or.jp) Received: (qmail 9890 invoked from network); 9 Dec 2004 22:51:19 +0900 Received: from unknown (HELO localhost) (210.165.212.57) by wasley.bl.mmtr.or.jp with SMTP; 9 Dec 2004 22:51:19 +0900 Date: Thu, 09 Dec 2004 22:50:41 +0900 (JST) Message-Id: <20041209.225041.63112571.rushani@bl.mmtr.or.jp> To: sam@errno.com From: Hideyuki KURASHINA In-Reply-To: <200412081744.27539.sam@errno.com> References: <200412081109.43840.sam@errno.com> <20041209.100008.21874313.rushani@bl.mmtr.or.jp> <200412081744.27539.sam@errno.com> X-URL: http://www.rushani.jp/ X-PGP-Public-Key: http://www.rushani.jp/rushani.asc X-PGP-Fingerprint: A052 6F98 6146 6FE3 91E2 DA6B F2FA 2088 439A DC57 X-RC5-72-Stats: http://stats.distributed.net/participant/psummary.php?project_id=8&id=432320 X-Mailer: Mew version 4.1.52 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: WEP does not work? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 13:51:28 -0000 Hi, >>> On Wed, 8 Dec 2004 17:44:27 -0800, Sam Leffler said: > On Wednesday 08 December 2004 05:00 pm, Hideyuki KURASHINA wrote: > > After rebooting, I set IPv4 and IPv6 addresses and those routes. Because > > access point supports only 802.11b, I configured my wireless network > > by 128bit WEP as follows > > > > /sbin/ifconfig ath0 nwid MY-SSID nwkey 0x01234567890123456789012345 media > > autoselect mode 11b > > > > then I got following error: > > > > ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) > > ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) > > ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) > > ath0: ath_chan_set: unable to reset channel 12 (2467 Mhz) > > Weird, can you send me the regdomain and country code: e.g. the output of > sysctl dev.ath.0. Sure. # sysctl dev.ath.0 dev.ath.0.%desc: Atheros 5212 dev.ath.0.%driver: ath dev.ath.0.%location: slot=2 function=0 dev.ath.0.%pnpinfo: vendor=0x168c device=0x1014 subvendor=0x1014 subdevice=0x057e class=0x020000 dev.ath.0.%parent: pci2 dev.ath.0.countrycode: 395 dev.ath.0.regdomain: 67 dev.ath.0.debug: 0 dev.ath.0.slottime: 20 dev.ath.0.acktimeout: 48 dev.ath.0.ctstimeout: 48 dev.ath.0.softled: 1 dev.ath.0.ledpin: 0 dev.ath.0.txantenna: 0 dev.ath.0.rxantenna: 1 dev.ath.0.txintrperiod: 5 dev.ath.0.diag: 0 dev.ath.0.tpscale: 0 dev.ath.0.rate_interval: 1000 dev.ath.0.rate_raise: 10 dev.ath.0.rate_raise_threshold: 10 Just curiosity, `hw' MIBs print both regdomain and countrycode are 0. # sysctl hw.ath hw.ath.hal.swba_backoff: 0 hw.ath.hal.sw_brt: 10 hw.ath.hal.dma_brt: 2 hw.ath.hal.version: 0.9.14.9 hw.ath.debug: 0 hw.ath.regdomain: 0 hw.ath.countrycode: 0 hw.ath.xchanmode: 1 hw.ath.outdoor: 1 hw.ath.calibrate: 30 hw.ath.dwell: 200 > > # ifconfig ath0 list chan > > Channel 1 : 2412* Mhz 11g Channel 11 : 2462* Mhz 11g > > Channel 2 : 2417* Mhz 11g Channel 12 : 2467* Mhz 11a 11g > > Channel 3 : 2422* Mhz 11g Channel 13 : 2472* Mhz 11g > > Channel 4 : 2427* Mhz 11g Channel 14 : 2484* Mhz 11b > > Channel 5 : 2432* Mhz 11g Channel 16 : 5080* Mhz 11a > > Channel 6 : 2437* Mhz 11g Channel 34 : 5170* Mhz 11a > > Channel 7 : 2442* Mhz 11g Channel 38 : 5190* Mhz 11a > > Channel 8 : 2447* Mhz 11a 11g Channel 42 : 5210* Mhz 11a > > Channel 9 : 2452* Mhz 11g Channel 46 : 5230* Mhz 11a > > Channel 10 : 2457* Mhz 11g > > > > So it seems channels 8 and 12 are supposedly available. Actually, no. I'll show you my AP side wireless network setting. % dmesg | grep wi0 wi0 at pcmcia0 function 0: PLANEX, GW-NS11H Wireless LAN PC Card, wi0: 802.11 address 00:90:cc:XX:XX:XX wi0: using RF:PRISM3 MAC:ISL3871(PCMCIA) wi0: Intersil Firmware: Primary (1.0.7), Station (1.3.5) wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps % ifconfig wi0 wi0: flags=8863 mtu 1500 ssid MY-SSID nwkey ***** powersave off bssid 00:90:cc:XX:XX:XX chan 3 address: 00:90:cc:XX:XX:XX media: IEEE802.11 autoselect mode 11b hostap (DS2 hostap) status: active inet 192.168.1.7 netmask 0xffffff00 broadcast 192.168.1.255 inet alias 192.168.1.254 netmask 0xffffffff broadcast 192.168.1.254 inet6 fe80::290:XXXX:XXXX:XXXX%wi0 prefixlen 64 scopeid 0x4 inet6 2001:3e0:XXX:X::X prefixlen 64 % sudo wiconfig wi0 NIC serial number: [ 99SA01XXXXXX ] Station name: [ ] SSID for IBSS creation: [ MY-SSID ] Current netname (SSID): [ MY-SSID ] Desired netname (SSID): [ MY-SSID ] Current BSSID: [ 00:90:cc:XX:XX:XX ] Channel list: [ 1 2 3 4 5 6 7 8 9 10 11 12 13 14 ] IBSS channel: [ 3 ] Current channel: [ 3 ] Comms quality/signal/noise: [ 0 81 27 ] Promiscuous mode: [ Off ] Port type: [ 6 ] MAC address: [ 00:90:cc:XX:XX:XX ] TX rate (selection): [ 0 ] TX rate (actual speed): [ 2 ] Beacon Interval (current) [msec]: [ 100 ] Maximum data length: [ 2304 ] RTS/CTS handshake threshold: [ 2347 ] fragmentation threshold: [ 2346 ] RSSI -> dBm adjustment: [ 100 ] Create IBSS: [ Off ] Microwave oven robustness: [ 0 ] Roaming mode(1:firm,3:disable): [ 1 ] Access point density: [ 1 ] Power Mgmt (1=on, 0=off): [ 0 ] Max sleep time (msec): [ 100 ] Vendor info: [ Unknown ID: 31 version: 1.3 ] WEP encryption: [ On ] Authentication type (1=OpenSys, 2=Shared Key): [ 1 ] TX encryption key: [ 1 ] Encryption keys: [ 0x01234567890123456789012345 ][ ][ ][ ] > > It seems that ath0 failed to reset channel. I manually specified channel, > > then ifconfig shows: > > > > # ifconfig -v ath0 > > ath0: flags=8843 mtu 1500 > > inet 192.168.1.11 netmask 0xffffff00 broadcast 192.168.1.255 > > inet6 fe80::20e:XXXX:XXXX:XXXX%ath0 prefixlen 64 scopeid 0x2 > > inet6 2001:3e0:XX:X::XX prefixlen 64 > > ether 00:0e:9b:XX:XX:XX > > media: IEEE 802.11 Wireless Ethernet autoselect mode 11b (DS/11Mbps) > > status: associated > > ssid MY-SSID channel 3 (2422) bssid 00:90:cc:XX:XX:XX > > authmode OPEN privacy ON deftxkey 1 powersavemode OFF > > powersavesleep 100 txpowmax 14 txpower 60 rtsthreshold 2312 protmode CTS > > wme roaming AUTO bintval 100 > > AC_BE cwmin 5 cwmax 10 aifs 3 txopLimit 0 -acm ack > > cwmin 5 cwmax 10 aifs 3 txopLimit 0 -acm > > AC_BK cwmin 5 cwmax 10 aifs 7 txopLimit 0 -acm ack > > cwmin 5 cwmax 10 aifs 7 txopLimit 0 -acm > > AC_VI cwmin 4 cwmax 5 aifs 2 txopLimit 188 -acm ack > > cwmin 4 cwmax 5 aifs 2 txopLimit 188 -acm > > AC_VO cwmin 3 cwmax 4 aifs 2 txopLimit 102 -acm ack > > cwmin 3 cwmax 4 aifs 2 txopLimit 102 -acm > > This doesn't show a key installed. I don't typically use nwkey; I'll have to > check it. I tried # /sbin/ifconfig ath0 ssid MY-SSID wepmode on weptxkey 1 wepkey 1:0x01234567890123456789012345 wepkey 2:- wepkey 3:- wepkey 4:- media autoselect mode 11b but nothing changed (default router is still not reachable). The card in question is labeled ``Atheros AR5BMB-44''. http://www.rushani.jp/photo/20041209/12090019.jpg -- rushani From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 14:00:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70A5116A4CE for ; Thu, 9 Dec 2004 14:00:03 +0000 (GMT) Received: from wasley.bl.mmtr.or.jp (wasley.bl.mmtr.or.jp [210.228.173.142]) by mx1.FreeBSD.org (Postfix) with SMTP id 4595643D31 for ; Thu, 9 Dec 2004 14:00:02 +0000 (GMT) (envelope-from rushani@bl.mmtr.or.jp) Received: (qmail 12044 invoked from network); 9 Dec 2004 23:00:01 +0900 Received: from unknown (HELO localhost) (210.165.212.57) by wasley.bl.mmtr.or.jp with SMTP; 9 Dec 2004 23:00:01 +0900 Date: Thu, 09 Dec 2004 22:59:25 +0900 (JST) Message-Id: <20041209.225925.30166884.rushani@bl.mmtr.or.jp> To: Danovitsch@vitsch.net From: Hideyuki KURASHINA In-Reply-To: <200412091241.02372.Danovitsch@vitsch.net> References: <200412081109.43840.sam@errno.com> <20041209.100008.21874313.rushani@bl.mmtr.or.jp> <200412091241.02372.Danovitsch@vitsch.net> X-URL: http://www.rushani.jp/ X-PGP-Public-Key: http://www.rushani.jp/rushani.asc X-PGP-Fingerprint: A052 6F98 6146 6FE3 91E2 DA6B F2FA 2088 439A DC57 X-RC5-72-Stats: http://stats.distributed.net/participant/psummary.php?project_id=8&id=432320 X-Mailer: Mew version 4.1.52 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: FreeBSD-current@FreeBSD.org Subject: Re: WEP does not work? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 14:00:03 -0000 Hi, >>> On Thu, 9 Dec 2004 12:41:02 +0100, "Daan Vreeken [PA4DAN]" said: > Have you tried : > ifconfig ath0 wepmode on > after setting the wep key? I challenged following command lines, # /sbin/ifconfig ath0 ssid MY-SSID weptxkey 1 wepkey 1:0x01234567890123456789012345 wepkey 2:- wepkey 3:- wepkey 4:- media autoselect mode 11b # /sbin/ifconfig ath0 wepmode on However, the behavior was not changed. -- rushani From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 14:23:12 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 205E016A4D1 for ; Thu, 9 Dec 2004 14:23:12 +0000 (GMT) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B37D43D53 for ; Thu, 9 Dec 2004 14:23:11 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from ury.york.ac.uk (ury.york.ac.uk [144.32.108.81]) by mail-gw0.york.ac.uk (8.12.10/8.12.10) with ESMTP id iB9EN8uZ025733; Thu, 9 Dec 2004 14:23:08 GMT Received: from ury.york.ac.uk (localhost.york.ac.uk [127.0.0.1]) by ury.york.ac.uk (8.12.9p2/8.12.9) with ESMTP id iB9EN7Cu026573; Thu, 9 Dec 2004 14:23:07 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from localhost (gavin@localhost)iB9EN7h2026570; Thu, 9 Dec 2004 14:23:07 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: ury.york.ac.uk: gavin owned process doing -bs Date: Thu, 9 Dec 2004 14:23:07 +0000 (GMT) From: Gavin Atkinson X-X-Sender: gavin@ury.york.ac.uk To: cjohnson@wcug.wwu.edu In-Reply-To: <20041208173829.GA7645@wcug.wwu.edu> Message-ID: <20041209141745.H26445@ury.york.ac.uk> References: <20041208173829.GA7645@wcug.wwu.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk cc: freebsd-current@freebsd.org Subject: Re: Microsoft Wireless Intellimouse Explorer X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 14:23:12 -0000 On Wed, 8 Dec 2004 cjohnson@wcug.wwu.edu wrote: > I'd like to help get my Microsoft Wireless Intellimouse Explorer > working under 5.3-RELEASE. I've installed 5.3-RELEASE (x86) and > updated to about 3 AM PST with the GENERIC kernel, and the mouse > is recognized as ums0: > > ums0: Microsoft Microsoft Wireless Intellimouse Explorer\M-. 1.0A, rev 1.10/0.0e, addr 2, iclass 3/1 > ums0: 5 buttons and Z dir. > > So the driver sees it, but I can't get much output from the mouse. > moused starts and sees the device, but I'm unable to move the cursor > in X or on the console. If I kill off moused and point X at > /dev/ums0, X can't open the device and I get the message: > > usbd_setup_pipe: failed to start endpoint, TIMEOUT > > I've also tried ' moused -p /dev/ums0 -i all ' after killing off > moused and I get: > > moused: unable to open /dev/ums0: Input/output error Try the patch at http://www.devrandom.co.uk/freebsd/intellimouse.diff - and let me know if it works for you. However, from your description, I suspect it's a different problem so you may not have any success. > Any help would be appreciated. I can provide remote access if needed If that patch doesn't work, I may take you up on this offer. It would be nice to get them working. Gavin From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 14:41:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B337716A4CE; Thu, 9 Dec 2004 14:41:06 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B47743D5D; Thu, 9 Dec 2004 14:41:06 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.1.102] (CPE000625f86c85-CM000e5c22aba0.cpe.net.cable.rogers.com [69.193.110.163] (may be forged)) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iB9EhDPx021106; Thu, 9 Dec 2004 07:43:14 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41B863FD.7000007@freebsd.org> Date: Thu, 09 Dec 2004 07:41:01 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org Subject: Wanted: lots of 6-CURRENT testing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 14:41:06 -0000 All, There has been an incredible amount of work going into 6-CURRENT in the last 5 weeks. With the holidays quickly approaching, now seems like a good time to step back and start really testing the system to shake out the bugs and catch the developers before they disappear for the holidays. In particular, the recent massive changes to the vnode layer and the upgrade of the net80211 layer and wireless lan drivers needs a lot of review and testing. Now is also a good time to review the recent additions to the PR database and start seeing if there are trends developing and/or areas that need immediate attention. While 6-CURRENT remains in a high state of flux I'll also ask that people carefully consider what to merge into 5-STABLE and when to merge it. Don't let important bugfixes that would benefit 5-STABLE and 4-STABLE drop on the floor, but also make sure that they recieve thorough testing before being merged back. Thanks, Scott From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 14:42:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FB6716A4CE for ; Thu, 9 Dec 2004 14:42:36 +0000 (GMT) Received: from relay.pair.com (relay00.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id A0C3543D5A for ; Thu, 9 Dec 2004 14:42:35 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 46249 invoked from network); 9 Dec 2004 14:42:34 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 9 Dec 2004 14:42:34 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iB9EgXUM046944 for ; Thu, 9 Dec 2004 15:42:33 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iB9EgX8S046943 for current@freebsd.org; Thu, 9 Dec 2004 15:42:33 +0100 (CET) (envelope-from pho) Date: Thu, 9 Dec 2004 15:42:33 +0100 From: Peter Holm To: current@freebsd.org Message-ID: <20041209144233.GA46928@peter.osted.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: panic: uma_zone_slab is looping X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 14:42:36 -0000 I modified: $ cvs diff -u uma_core.c Index: uma_core.c =================================================================== RCS file: /home/ncvs/src/sys/vm/uma_core.c,v retrieving revision 1.110 diff -u -r1.110 uma_core.c --- uma_core.c 6 Nov 2004 11:43:30 -0000 1.110 +++ uma_core.c 9 Dec 2004 14:38:32 -0000 @@ -1926,6 +1926,7 @@ { uma_slab_t slab; uma_keg_t keg; + int i; keg = zone->uz_keg; @@ -1943,7 +1944,8 @@ slab = NULL; - for (;;) { + for (i = 0;;i++) { + KASSERT(i < 10000, ("uma_zone_slab is looping")); /* * Find a slab with some space. Prefer slabs that are partially * used over those that are totally full. This helps to reduce and caught this one: http://www.holm.cc/stress/log/cons94.html -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 16:23:05 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9AD0A16A4CE; Thu, 9 Dec 2004 16:23:05 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F56643D5A; Thu, 9 Dec 2004 16:23:05 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iB9GN5gr053714; Thu, 9 Dec 2004 08:23:05 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iB9GN55s053713; Thu, 9 Dec 2004 08:23:05 -0800 (PST) (envelope-from sgk) Date: Thu, 9 Dec 2004 08:23:05 -0800 From: Steve Kargl To: Harti Brandt Message-ID: <20041209162305.GB53640@troutmask.apl.washington.edu> References: <20041209000148.GA4674@troutmask.apl.washington.edu> <20041209110942.F86222@beagle.kn.op.dlr.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041209110942.F86222@beagle.kn.op.dlr.de> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: make(1) is broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 16:23:05 -0000 On Thu, Dec 09, 2004 at 11:10:59AM +0100, Harti Brandt wrote: > On Wed, 8 Dec 2004, Steve Kargl wrote: > > SK> > SK>Stop in /usr/src. > SK>troutmask:root[203] tail -1 /var/log/messages > SK>Dec 8 15:58:39 troutmask kernel: pid 4794 (make), uid 0: exited on signal 11 > SK> > > Thanks for the report. This has been caused by make during clean-up to > remove a path element that was never opened as a directory from the list > of open directories. Fixed in rev. 1.43 of dir.c. Thanks for the fix. -- Steve From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 16:48:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BB4516A4CF for ; Thu, 9 Dec 2004 16:48:43 +0000 (GMT) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 902D843D62 for ; Thu, 9 Dec 2004 16:48:42 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy.york.ac.uk [144.32.226.160]) by mail-gw0.york.ac.uk (8.12.10/8.12.10) with ESMTP id iB9GmduZ019656; Thu, 9 Dec 2004 16:48:39 GMT Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.1/8.13.1) with ESMTP id iB9Gmc7X005145; Thu, 9 Dec 2004 16:48:38 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.1/8.13.1/Submit) id iB9GmbWg005144; Thu, 9 Dec 2004 16:48:37 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: cjohnson@wcug.wwu.edu In-Reply-To: <20041209141745.H26445@ury.york.ac.uk> References: <20041208173829.GA7645@wcug.wwu.edu> <20041209141745.H26445@ury.york.ac.uk> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 09 Dec 2004 16:48:36 +0000 Message-Id: <1102610916.4474.5.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk cc: freebsd-current@freebsd.org Subject: Re: Microsoft Wireless Intellimouse Explorer X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 16:48:43 -0000 On Thu, 2004-12-09 at 14:23 +0000, Gavin Atkinson wrote: > On Wed, 8 Dec 2004 cjohnson@wcug.wwu.edu wrote: > > > I'd like to help get my Microsoft Wireless Intellimouse Explorer > > working under 5.3-RELEASE. I've installed 5.3-RELEASE (x86) and > > updated to about 3 AM PST with the GENERIC kernel, and the mouse > > is recognized as ums0: > > > > ums0: Microsoft Microsoft Wireless Intellimouse Explorer\M-. 1.0A, rev 1.10/0.0e, addr 2, iclass 3/1 > > ums0: 5 buttons and Z dir. > > > > So the driver sees it, but I can't get much output from the mouse. > > moused starts and sees the device, but I'm unable to move the cursor > > in X or on the console. > > Try the patch at http://www.devrandom.co.uk/freebsd/intellimouse.diff - > and let me know if it works for you. However, from your description, I > suspect it's a different problem so you may not have any success. Sorry, I should probably just say that it is an updated version of the patch in PR 70607 and is not all my own work :) Gavin From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 17:13:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7C9E16A4D5 for ; Thu, 9 Dec 2004 17:13:58 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 873EB43D55 for ; Thu, 9 Dec 2004 17:13:57 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id iB9HDuc0010595 for ; Thu, 9 Dec 2004 20:13:56 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id iB9HDurA010594 for current@freebsd.org; Thu, 9 Dec 2004 20:13:56 +0300 (MSK) (envelope-from ache) Date: Thu, 9 Dec 2004 20:13:55 +0300 From: Andrey Chernov To: current@freebsd.org Message-ID: <20041209171355.GA7967@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1; AVE: 6.29.0.4; VDF: 6.29.0.6; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [127.0.0.1]); Thu, 09 Dec 2004 20:13:56 +0300 (MSK) Subject: Lots of ACPI warnings with recent -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 17:13:58 -0000 acpi0: on motherboard ACPI-0252: *** Error: No object was returned from [\\_SB_.PCI0.PX40.UAR2._STA] (Node 0xc1186240), AE_NOT_EXIST It is repeated later about 40 times. -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 17:29:44 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0E9F916A4CE for ; Thu, 9 Dec 2004 17:29:44 +0000 (GMT) Received: from galaxy.uci.agh.edu.pl (galaxy.uci.agh.edu.pl [149.156.96.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 255D243D55 for ; Thu, 9 Dec 2004 17:29:43 +0000 (GMT) (envelope-from kkowalik@uci.agh.edu.pl) Received: by galaxy.uci.agh.edu.pl (Postfix, from userid 1001) id 927BDAF40D; Thu, 9 Dec 2004 18:29:41 +0100 (CET) Date: Thu, 9 Dec 2004 18:29:41 +0100 From: Krzysztof Kowalik To: current@freebsd.org Message-ID: <20041209172941.GA29369@uci.agh.edu.pl> References: <20041207234840.7287cdf4@maya.liquidx.org> <1102506431.1090.8.camel@taxman> <41B6ED4E.6030301@fer.hr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41B6ED4E.6030301@fer.hr> Subject: Re: FreeBSD sound distortion problems with SB Live! fixed with PREEMPTION X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 17:29:44 -0000 Ivan Voras [ivoras@fer.hr] wrote: > [...] > Not exactly a freeze, but PREEMPTION doesn't help me at all with SB Live > (slowdowns, stuttering sound, etc.), especially with large amounts of > filesystem operations (this is 5-stable). Exactly. I tried to use both emu10k1 and emu10kx drivers, with kernel with and without PREEMPTION, and both 5.x and 6.0 serie did behave same. Intensive I/O made the system quite unusable, and it was not only a sound-related issue, but a general one -- slow, lagging mouse in X, etc. I asked about it on stable@ and somehow got no answers but "me too". Finally, I decided to restore my 4.9 system from the backups, where the problem does not exist. Regards, -- Krzysztof Kowalik | () ASCII Ribbon Campaign Computer Center, AGH UST | /\ Support plain text e-mail From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 17:47:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9362916A4CE for ; Thu, 9 Dec 2004 17:47:58 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D18343D53 for ; Thu, 9 Dec 2004 17:47:58 +0000 (GMT) (envelope-from arr@watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iB9HjSjj058033 for ; Thu, 9 Dec 2004 12:45:28 -0500 (EST) (envelope-from arr@watson.org) Received: from localhost (arr@localhost)iB9HjSpb058030 for ; Thu, 9 Dec 2004 12:45:28 -0500 (EST) (envelope-from arr@watson.org) X-Authentication-Warning: fledge.watson.org: arr owned process doing -bs Date: Thu, 9 Dec 2004 12:45:28 -0500 (EST) From: "Andrew R. Reiter" To: current@Freebsd.org Message-ID: <20041209124257.X57958@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: panic not going to debugger? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 17:47:58 -0000 Anyone else experiencing issues when a panic, something simple like a recursion on a non-recursable lock, occurs, it won't break to DDB? I've got all the right bits for it (KERNCONF options etc) but seems to have stopped working since I updated to CURRENT yesterday... after battling through trying to figure out the do_powerstate=0 issue I was having. I have a easily reproducible panic but can't dump or anything b/c of this problem. So, instead, I'll have to send an email with old information (line #'s etc)... Did I miss something? :-) Cheers, Andrew -- Andrew R. Reiter arr@watson.org arr@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 17:56:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CD8C16A4CF for ; Thu, 9 Dec 2004 17:56:02 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72B6143D39 for ; Thu, 9 Dec 2004 17:56:01 +0000 (GMT) (envelope-from arr@watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iB9HrVNs058181 for ; Thu, 9 Dec 2004 12:53:31 -0500 (EST) (envelope-from arr@watson.org) Received: from localhost (arr@localhost)iB9HrVGZ058178 for ; Thu, 9 Dec 2004 12:53:31 -0500 (EST) (envelope-from arr@watson.org) X-Authentication-Warning: fledge.watson.org: arr owned process doing -bs Date: Thu, 9 Dec 2004 12:53:31 -0500 (EST) From: "Andrew R. Reiter" To: current@freebsd.org Message-ID: <20041209124839.V57958@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: rtentry recursion panic (fwd) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 17:56:02 -0000 Sending since I know Sam and Bruce are busy; I am busy.. not as busy.. but busy enough to not have time to track code paths down further than I did in the below email. NOTE: The line # in the panicstr is WRONG! this message was after me doing some minor printf() additions to see what was going on a bit further after I was unable to get a good vmcore. NOTE: The way I explained the way to reproduce it is a bit more difficult than it can be done. Ie.. just do: ifconfig 10.9.9.100 netmask 255.255.0.0 up route add default 10.9.0.1 route delete default route delete 10.9/16 route add default 10.9.0.1 traceroute 10.9.0.1 panic... I explain a bit further in the below email where the actual problem is.. I just am not sure the exact means it got to that point. I've verified this exists on CURRENT of yesterday. So it's still lingering.. ---------- Forwarded message ---------- Date: Wed, 1 Dec 2004 03:24:36 -0500 (EST) From: Andrew R. Reiter To: sam@freebsd.org, bms@freebsd.org Subject: rtentry recursion panic Sam & Bruce, I am admittedly running a slightly out of date CURRENT, but am hoping to see whether or not you all have seen this (or related) panic. The panic string is [ignore line #, added debug goo for own use]: _mtx_lock_sleep: recursed on non-recursive mutex rtentry @ /usr/au_src/sys/net/route.c:1311 And the [long] backtrace is: #0 doadump () at pcpu.h:159 #1 0xc0466dee in db_fncall (dummy1=-1065588687, dummy2=0, dummy3=-563291948, dummy4=0xde6cd86c "l") at /usr/au_src/sys/ddb/db_command.c:531 #2 0xc0467184 in db_command_loop () at /usr/au_src/sys/ddb/db_command.c:349 #3 0xc0468b8c in db_trap (type=3, code=0) at /usr/au_src/sys/ddb/db_main.c:221 #4 0xc064e32e in kdb_trap (type=3, code=0, tf=0xde6cd994) at /usr/au_src/sys/kern/subr_kdb.c:421 #5 0xc07d977c in trap (frame= {tf_fs = -563347432, tf_es = -1067122672, tf_ds = -1065091056, tf_edi = 0, tf_esi = 1, tf_ebp = -563291692, tf_isp = -563291712, tf_ebx = -563291648, tf_edx = -1065058018, tf_ecx = -1064210208, tf_eax = -1065049367, tf_trapno = 3, tf_err = 0, tf_eip = -1067131032, tf_cs = 8, tf_eflags = 642, tf_esp = -563291660, tf_ss = -1067222809}) at /usr/au_src/sys/i386/i386/trap.c:577 #6 0xc07c82aa in calltrap () at /usr/au_src/sys/i386/i386/exception.s:140 #7 0xde6c0018 in ?? () #8 0xc0650010 in kvprintf (fmt=0x1
, func=0x100, arg=0xc1f1aaf0, radix=-1042196716, ap=0xc1e15714 "D+\213\v\204\v\204") at /usr/au_src/sys/kern/subr_prf.c:543 #9 0xc06378e7 in panic (fmt=0x282
) at /usr/au_src/sys/kern/kern_shutdown.c:525 #10 0xc06301b1 in _mtx_lock_sleep (m=0xc1e15714, td=0xc1f1aaf0, opts=0, file=0xc0852322 "/usr/au_src/sys/net/route.c", line=1311) at /usr/au_src/sys/kern/kern_mutex.c:492 #11 0xc063023c in _mtx_lock_flags (m=0xc1e15714, opts=0, file=0xc0852322 "/usr/au_src/sys/net/route.c", line=1311) at /usr/au_src/sys/kern/kern_mutex.c:273 #12 0xc06a87ed in rt_check (lrt=0x0, lrt0=0xde6cdab4, dst=0xc1fa7a10) at /usr/au_src/sys/net/route.c:1311 #13 0xc06b3481 in arpresolve (ifp=0xc1cea000, rt0=0xc1e156b4, m=0xc1e0f300, dst=0xc1fa7a10, desten=0xde6cdad0 "") at /usr/au_src/sys/netinet/if_ether.c:351 #14 0xc069c392 in ether_output (ifp=0xc1cea000, m=0xc1e0f300, dst=0xc1fa7a10, rt0=0x0) at /usr/au_src/sys/net/if_ethersubr.c:160 #15 0xc06bd94f in ip_output (m=0xc1e0f300, opt=0xc1cea000, ro=0xde6cdb40, flags=34, imo=0x0, inp=0xc1faeec4) at /usr/au_src/sys/netinet/ip_output.c:771 #16 0xc06bdf81 in rip_output (m=0xc1e0f300, so=0x0, dst=0) at /usr/au_src/sys/netinet/raw_ip.c:320 #17 0xc06bea8f in rip_send (so=0xc1d78798, flags=0, m=0xc1e0f300, nam=0xc1ba51a0, control=0x0, td=0xc1f1aaf0) at /usr/au_src/sys/netinet/raw_ip.c:784 #18 0xc066db10 in sosend (so=0xc1d78798, addr=0xc1ba51a0, uio=0xde6cdc54, top=0xc1e0f300, control=0x0, flags=0, td=0xc1f1aaf0) at /usr/au_src/sys/kern/uipc_socket.c:816 #19 0xc06739ea in kern_sendit (td=0xc1f1aaf0, s=7, mp=0xde6cdccc, flags=0, control=0x0) at /usr/au_src/sys/kern/uipc_syscalls.c:784 #20 0xc067488c in sendit (td=0xc1f1aaf0, s=7, mp=0xde6cdccc, flags=0) at /usr/au_src/sys/kern/uipc_syscalls.c:725 #21 0xc0674b7d in sendto (td=0x0, uap=0x0) at /usr/au_src/sys/kern/uipc_syscalls.c:841 #22 0xc07d9bc9 in syscall (frame= {tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 0, tf_esi = 0, tf_ebp = -1077941288, tf_isp = -563290764, tf_ebx = 672388112, tf_edx = 134553600, tf_ecx = 1, tf_eax = 133, tf_trapno = 12, tf_err = 2, tf_eip = 671908087, tf_cs = 31, tf_eflags = 662, tf_esp = -1077941348, tf_ss = 47}) at /usr/au_src/sys/i386/i386/trap.c:1003 #23 0xc07c82ff in Xint0x80_syscall () at /usr/au_src/sys/i386/i386/exception.s:201 #24 0x0000002f in ?? () #25 0x0000002f in ?? () #26 0x0000002f in ?? () #27 0x00000000 in ?? () #28 0x00000000 in ?? () #29 0xbfbfebd8 in ?? () #30 0xde6cdd74 in ?? () #31 0x2813d410 in ?? () #32 0x08052000 in ?? () #33 0x00000001 in ?? () #34 0x00000085 in ?? () #35 0x0000000c in ?? () #36 0x00000002 in ?? () #37 0x280c80f7 in ?? () #38 0x0000001f in ?? () #39 0x00000296 in ?? () #40 0xbfbfeb9c in ?? () #41 0x0000002f in ?? () #42 0x00000000 in ?? () #43 0x00000000 in ?? () #44 0x00000000 in ?? () #45 0x00000000 in ?? () #46 0x1f343000 in ?? () #47 0x00000000 in ?? () #48 0xc1f1aaf0 in ?? () #49 0xde6cda28 in ?? () #50 0xde6cda10 in ?? () #51 0xc19da640 in ?? () #52 0xc0647643 in sched_switch (td=0x0, newtd=0x2813d410, flags=Cannot access memory at address 0xbfbfebe8 ) at /usr/au_src/sys/kern/sched_4bsd.c:865 (kgdb) The recursion takes place in rt_check() after rtalloc1()'ing for a rt_gwroute since rt0's (*lrt0) rt_gwroute is NULL. The value rtentry object allocated is pointing at the same address as rt0... and when we return from rtalloc1() the rtentry object is locked.... so the following occurs in rt_check() (indent python-esque format): rt_check(..., struct rtentry **lrt0, ...) rt = rt0 = *lrt0 if (rt) RT_LOCK(rt) ...checks to see if RTF_GATEWAY; jumps down since rt_gwroute==0 RT_UNLOCK(rt0) // remember, rt == rt0, even now due to beginning code // alloc new gateway rtentry rt = rtalloc1(rt->rt_gateway, 1, 0); // is rt_gateway safe?? RT_LOCK(rt0); // BAM! panic.. rt (after rtalloc1()) points to same addr as rt0... hows that happening?) The locked is grabbed in rtalloc1() as well as a refcnt is added (not marked RTF_CLONING at alloc time). I've narrowed down how to reproduce in a reasonable fashion... perhaps could be narrowed down further, but am starting to get sleepy tonight.. can help tomorrow. This UP laptop has a bge ethernet nic and a wi wireless nic. Upon boot, my startup scripts are configured to ifconfig bge to a 10.x.x.x ipaddress and set the default route (nothing exciting). The wi device is left untouched. So, to cause the panic... # ifconfig wi0 192.168.0.3 netmask 255.255.255.0 ssid BLAH stationname j # route delete default // Whacks 10.x.x.x default route # route delete 10.5/16 # route delete 192.168.0.1 // Shouldnt be there unless pingd or other # route delete -net 192.168.0 # route add default 192.168.0.1 # traceroute 192.168.0.1 The traceroute command calls sendto().... and so on (as seen above). As you can tell, I've not gone through the code paths in the above steps to try and determine the root of the problem; my apologies. I plan on picking this up tomorrow when I have time at work and going from there. Please let me know if you have any thoughts or can help and would like more information. Cheers, Andrew -- Andrew R. Reiter arr@watson.org arr@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 18:10:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 812F816A4CE for ; Thu, 9 Dec 2004 18:10:35 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4792143D39 for ; Thu, 9 Dec 2004 18:10:35 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id iB9IAYc18796; Thu, 9 Dec 2004 10:10:34 -0800 (PST) Date: Thu, 9 Dec 2004 10:10:34 -0800 From: Mike Hunter To: Steve Kargl Message-ID: <20041209181034.GA16160@ack.Berkeley.EDU> References: <20041209002430.GA18622@ack.Berkeley.EDU> <20041209002939.GB7272@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041209002939.GB7272@troutmask.apl.washington.edu> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: coredump while trying to build world (2004.12.08.1600-0800 src) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 18:10:35 -0000 On Dec 08, "Steve Kargl" wrote: > On Wed, Dec 08, 2004 at 04:24:30PM -0800, Mike Hunter wrote: > > Hi, > > > > I'm trying to go from RELENG_5 to HEAD on my new amd64, but I'm bombing > > out here: > > > > cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe -DMAGIC='"/usr/share/misc/magic"' -DBUILTIN_ELF -DELFCORE -DHAVE_CONFIG_H -I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file -c /usr/src/lib/libmagic/../../contrib/file/softmagic.c -o softmagic.So > > building shared library libmagic.so.1 > > Segmentation fault (core dumped) > > *** Error code 139 > > > > You need to back out the recent changes to make(1). > In your supfile file that you use with cvsup, set > > *default date=2004.11.08.00.00.00 > src-usrbin > > cd /usr/src/usr.bin/make > make > make install > > PS: surprising the broken make(1) actually works for building > a new make(1). Ugh. I tried cvsupping as you suggested, but it gave the same error. This morning I cvsup'd again after make was fixed (thanks!), and it *still* gives the same error. I don't think my installed /usr/bin/make is being updated. I forgot to md5 the original make, but this is from this morning's fixed-make sources: bash-2.05b# cd /usr/src/usr.sbin/make bash-2.05b# make ... job.o(.text+0x2973): In function `Job_Init': : warning: warning: mktemp() possibly used unsafely; consider using mkstemp() gzip -cn /usr/src/usr.bin/make/make.1 > make.1.gz bash-2.05b# md5 `which make` MD5 (/usr/bin/make) = fbb5679f9fde6036770a13ea5d6f9373 bash-2.05b# find /usr/obj -type f -name make | xargs -L 1 md5 MD5 (/usr/obj/usr/src/make.amd64/usr/src/usr.bin/make/make) = 5d3d91bf4ca06d1dae5a5d0874589b2c MD5 (/usr/obj/usr/src/make.amd64/make) = 5d3d91bf4ca06d1dae5a5d0874589b2c MD5 (/usr/obj/usr/src/usr.bin/make/make) = 0e719846f3f245fa7aa7d3aa2dca0bfd bash-2.05b# make install install -s -o root -g wheel -m 555 make /usr/bin install -o root -g wheel -m 444 make.1.gz /usr/share/man/man1 bash-2.05b# md5 `which make` MD5 (/usr/bin/make) = fbb5679f9fde6036770a13ea5d6f9373 Why doesn't /usr/bin/make change? Let me guess, there's a bug in make? :| I am trying again after copying /usr/obj/usr/src/usr.bin/make/make over /usr/bin/make by hand. Am I missing something here? Also, what's the make.amd64 directory about, and why are those make binaries also different? Befuddled in Berkeley From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 18:26:32 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02D3B16A4CE for ; Thu, 9 Dec 2004 18:26:32 +0000 (GMT) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id C51C843D2D for ; Thu, 9 Dec 2004 18:26:31 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) iB9IQUwN000192; Thu, 9 Dec 2004 10:26:30 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (h229.neville-neil.com [209.157.133.229] (may be forged)) by mail.meer.net (8.12.10/8.12.10/meer) with ESMTP id iB9IPr8r094407; Thu, 9 Dec 2004 10:25:53 -0800 (PST) (envelope-from gnn@neville-neil.com) Date: Thu, 09 Dec 2004 10:25:49 -0800 Message-ID: From: gnn@freebsd.org To: "Andrew R. Reiter" In-Reply-To: <20041209124839.V57958@fledge.watson.org> References: <20041209124839.V57958@fledge.watson.org> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.5 Emacs/21.2 (powerpc-apple-darwin) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: current@freebsd.org Subject: Re: rtentry recursion panic (fwd) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 18:26:32 -0000 At Thu, 9 Dec 2004 12:53:31 -0500 (EST), Andrew R. Reiter wrote: > > Sending since I know Sam and Bruce are busy; I am busy.. not as busy.. but > busy enough to not have time to track code paths down further than I did > in the below email. I'll take a quick look and see if I see anything obvious. Later, George From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 18:28:17 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 709F916A4CE for ; Thu, 9 Dec 2004 18:28:17 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45F9643D46 for ; Thu, 9 Dec 2004 18:28:17 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iB9ISG8r069565; Thu, 9 Dec 2004 10:28:16 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iB9ISGc5069564; Thu, 9 Dec 2004 10:28:16 -0800 (PST) (envelope-from sgk) Date: Thu, 9 Dec 2004 10:28:16 -0800 From: Steve Kargl To: Mike Hunter Message-ID: <20041209182816.GA27303@troutmask.apl.washington.edu> References: <20041209002430.GA18622@ack.Berkeley.EDU> <20041209002939.GB7272@troutmask.apl.washington.edu> <20041209181034.GA16160@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041209181034.GA16160@ack.Berkeley.EDU> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: coredump while trying to build world (2004.12.08.1600-0800 src) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 18:28:17 -0000 On Thu, Dec 09, 2004 at 10:10:34AM -0800, Mike Hunter wrote: (snip) > > Ugh. I tried cvsupping as you suggested, but it gave the same error. This > morning I cvsup'd again after make was fixed (thanks!), and it *still* gives > the same error. I don't think my installed /usr/bin/make is being updated. > > I forgot to md5 the original make, but this is from this morning's fixed-make > sources: > > bash-2.05b# cd /usr/src/usr.sbin/make > bash-2.05b# make > ... > job.o(.text+0x2973): In function `Job_Init': > : warning: warning: mktemp() possibly used unsafely; consider using mkstemp() > gzip -cn /usr/src/usr.bin/make/make.1 > make.1.gz > bash-2.05b# md5 `which make` > MD5 (/usr/bin/make) = fbb5679f9fde6036770a13ea5d6f9373 > bash-2.05b# find /usr/obj -type f -name make | xargs -L 1 md5 > MD5 (/usr/obj/usr/src/make.amd64/usr/src/usr.bin/make/make) = 5d3d91bf4ca06d1dae5a5d0874589b2c > MD5 (/usr/obj/usr/src/make.amd64/make) = 5d3d91bf4ca06d1dae5a5d0874589b2c > MD5 (/usr/obj/usr/src/usr.bin/make/make) = 0e719846f3f245fa7aa7d3aa2dca0bfd > bash-2.05b# make install > install -s -o root -g wheel -m 555 make /usr/bin > install -o root -g wheel -m 444 make.1.gz /usr/share/man/man1 > bash-2.05b# md5 `which make` > MD5 (/usr/bin/make) = fbb5679f9fde6036770a13ea5d6f9373 > > Why doesn't /usr/bin/make change? Let me guess, there's a bug in make? :| > > I am trying again after copying /usr/obj/usr/src/usr.bin/make/make over > /usr/bin/make by hand. Am I missing something here? Also, what's the > make.amd64 directory about, and why are those make binaries also different? > I'm not sure what is causing your problem, I will note that I do not have a make.amd64 directory. This suggests to me that your src tree may be messed up. I'm running -current while you appear to be using RELENG_5 perhaps you need to install from make.amd64 instead of from make. One other thing to do. Clean out your trees. rm -rf /usr/obj cd /usr/src make cleandir && make cleandir (the 2nd cleandir my be unnecessary) make buildworld yada yada -- Steve From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 20:04:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 020CC16A4CE for ; Thu, 9 Dec 2004 20:04:36 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id D50E543D3F for ; Thu, 9 Dec 2004 20:04:35 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iB9K4Z60000991 for ; Thu, 9 Dec 2004 12:04:35 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iB9K4ZXH000990 for freebsd-current@freebsd.org; Thu, 9 Dec 2004 12:04:35 -0800 (PST) (envelope-from sgk) Date: Thu, 9 Dec 2004 12:04:35 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Message-ID: <20041209200435.GA697@troutmask.apl.washington.edu> References: <20041209004335.GA624@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041209004335.GA624@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.2.1i Subject: Re: nfs appears broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 20:04:36 -0000 On Wed, Dec 08, 2004 at 04:43:35PM -0800, Steve Kargl wrote: > troutmask:root[201] mount /jumbo > [udp] jumbo:/data: RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed out > [udp] jumbo:/data: RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed out > > troutmask:root[203] grep jumbo /etc/fstab > jumbo:/data /jumbo nfs rw,noauto 0 0 > > > This is with world+kernel from about 30 minutes on amd64. I was > able to mount /jumbo with a kernel from monday. > Argh. I thought this may be related to phk's recent vfs work. It appears the admin of the NFS server tighten his firewall rules and locked me out. -- Steve From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 20:09:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86A1716A4CE for ; Thu, 9 Dec 2004 20:09:02 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68EA743D5C for ; Thu, 9 Dec 2004 20:09:02 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id iB9K91i25421; Thu, 9 Dec 2004 12:09:01 -0800 (PST) Date: Thu, 9 Dec 2004 12:09:01 -0800 From: Mike Hunter To: Steve Kargl Message-ID: <20041209200901.GA25184@ack.Berkeley.EDU> References: <20041209002430.GA18622@ack.Berkeley.EDU> <20041209002939.GB7272@troutmask.apl.washington.edu> <20041209181034.GA16160@ack.Berkeley.EDU> <20041209182816.GA27303@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041209182816.GA27303@troutmask.apl.washington.edu> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: coredump while trying to build world (2004.12.08.1600-0800 src) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 20:09:02 -0000 On Dec 09, "Steve Kargl" wrote: > I'm not sure what is causing your problem, I will note that I do not > have a make.amd64 directory. This suggests to me that your src tree > may be messed up. I'm running -current while you appear to be using > RELENG_5 perhaps you need to install from make.amd64 instead of from > make. > > One other thing to do. Clean out your trees. > rm -rf /usr/obj > cd /usr/src > make cleandir && make cleandir (the 2nd cleandir my be unnecessary) > make buildworld > yada yada It looks like rm -rf /usr/obj and make cleandir have gotten me past buildworld. Thanks Steve. Have no fear that I will pipe up again if there's more trouble :) Mike From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 20:33:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9EFF816A4CE; Thu, 9 Dec 2004 20:33:38 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id A99E643D49; Thu, 9 Dec 2004 20:33:36 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB9KXZbj099596; Thu, 9 Dec 2004 22:33:35 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 79527-18; Thu, 9 Dec 2004 22:33:34 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id iB9KXYYT099593 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Dec 2004 22:33:34 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iB9KXYCP091602; Thu, 9 Dec 2004 22:33:35 +0200 (EET) (envelope-from ru) Date: Thu, 9 Dec 2004 22:33:34 +0200 From: Ruslan Ermilov To: Max Laier Message-ID: <20041209203334.GB74745@ip.net.ua> References: <200412090411.42258.max@love2party.net> <20041209101524.GC62331@ip.net.ua> <200412091234.19912.max@love2party.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3lcZGd9BuhuYXNfi" Content-Disposition: inline In-Reply-To: <200412091234.19912.max@love2party.net> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: gnn@FreeBSD.org cc: Robert Watson cc: current@FreeBSD.org Subject: Re: protocol timer running before protocol is fully initialized (again) (was re: panic: mtx_lock() of spin mutex ...) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 20:33:38 -0000 --3lcZGd9BuhuYXNfi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Max, On Thu, Dec 09, 2004 at 12:34:08PM +0100, Max Laier wrote: [...] > in ip_input() - that's not good! Can you send me the trace? I was under t= he=20 > impression that net send and esp. reveice is off during this part of the= =20 > initialization. Crashing ip_input() would question that assumption. >=20 I don't have a serial attached to this notebook (all my serial cables are at work), so this is hand-copied from the screen: Timecounters tick every 1.000 msec panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/netinet/ip_input.c:10= 96 KDB: enter: panic [thread pid 27 tid 100001 ] Stopped at kdb_enter+0x32: leal 0(%esi),%esi db> where Tracing pid 27 tid 100001 td 0xc1219180 kdb_enter(...) at kdb_enter+0x32 panic(...) at panic+0x14d _mtx_lock_flags(...) at _mtx_lock_flags+0x114 ip_slowtimo(...) at ip_slowtimo+0x2f pfslowtimo(...) at pfslowtimo+0x82 softclock(...) at softclock+0x12f ithread_loop(...) at ithread_loop+0x210 fork_exit(...) at fork_exit+0xa9 fork_trampoline(...) at fork_trampoline+0x8 --- trap 0x1, eip =3D 0, esp =3D 0xcdbbbd7c, ebp =3D 0 --- PID 27 is "[CPU 0] swi4: clock sio Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --3lcZGd9BuhuYXNfi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBuLaeqRfpzJluFF4RAgwRAJ4/AB/AYOGWn3ERa/0y4qOxD/3rDgCcCsjT yMO/Qyg3itWP5wCKKSlA1lY= =QHAG -----END PGP SIGNATURE----- --3lcZGd9BuhuYXNfi-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 21:14:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0202116A4CE for ; Thu, 9 Dec 2004 21:14:00 +0000 (GMT) Received: from pne-smtpout2-sn2.hy.skanova.net (pne-smtpout2-sn2.hy.skanova.net [81.228.8.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FF1843D2D for ; Thu, 9 Dec 2004 21:13:59 +0000 (GMT) (envelope-from pawel.worach@telia.com) Received: from pne-ps4-sn1 (81.228.11.133) by pne-smtpout2-sn2.hy.skanova.net (7.1.026.6) id 41A335AA000091FF for freebsd-current@freebsd.org; Thu, 9 Dec 2004 22:13:58 +0100 Message-ID: <20587818.1102626838092.JavaMail.tomcat@pne-ps4-sn1> Date: Thu, 9 Dec 2004 22:13:58 +0100 (MET) From: Pawel Worach To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain;charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: CP Presentation Server X-clientstamp: [217.208.189.47] Subject: Re: page fault panic in device_get_softc/acpi_pcib_route_interrupt X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: pawel.worach@telia.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 21:14:00 -0000 Finally got around to fetch some more info about this. boot output and kgdb symbol decodes. FreeBSD 6.0-CURRENT #0: Wed Dec 8 17:58:20 CET 2004 root@zero:/usr/obj/usr/src/sys/ZERO Preloaded elf kernel "/boot/kernel/kernel" at 0xc07ee000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc07ee16c. Calibrating clock(s) ... i8254 clock: 1193157 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2793900608 Hz CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.90-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff real memory = 1073590272 (1023 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009cfff, 638976 bytes (156 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000000828000 - 0x000000003edaafff, 1045966848 bytes (255363 pages) avail memory = 1046142976 (997 MB) MP Configuration Table version 1.4 found at 0xc009e2a0 Table 'FACP' at 0x3ffdff00 Table 'APIC' at 0x3ffdfe80 MADT: Found table at 0x3ffdfe80 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 0: enabled SMP: Added CPU 0 (AP) MADT: Found CPU APIC ID 6 ACPI ID 1: enabled SMP: Added CPU 6 (AP) ACPI APIC Table: APIC ID: physical 0, logical 0:0 APIC ID: physical 6, logical 0:1 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 bios32: Found BIOS32 Service Directory header at 0xc00fd790 bios32: Entry = 0xfd7a1 (c00fd7a1) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0xd7dc pnpbios: Found PnP BIOS data at 0xc00fdf90 pnpbios: Entry = f0000:444c Rev = 1.0 Other BIOS signatures found: APIC: CPU 0 has ACPI ID 0 APIC: CPU 1 has ACPI ID 1 MADT: Found IO APIC ID 14, Interrupt 0 at 0xfec00000 ioapic0: Routing external 8259A's -> intpin 0 ioapic0: intpin 0 -> ExtINT (edge, high) ioapic0: intpin 1 -> ISA IRQ 1 (edge, high) ioapic0: intpin 2 -> ISA IRQ 2 (edge, high) ioapic0: intpin 3 -> ISA IRQ 3 (edge, high) ioapic0: intpin 4 -> ISA IRQ 4 (edge, high) ioapic0: intpin 5 -> ISA IRQ 5 (edge, high) ioapic0: intpin 6 -> ISA IRQ 6 (edge, high) ioapic0: intpin 7 -> ISA IRQ 7 (edge, high) ioapic0: intpin 8 -> ISA IRQ 8 (edge, high) ioapic0: intpin 9 -> ISA IRQ 9 (edge, high) ioapic0: intpin 10 -> ISA IRQ 10 (edge, high) ioapic0: intpin 11 -> ISA IRQ 11 (edge, high) ioapic0: intpin 12 -> ISA IRQ 12 (edge, high) ioapic0: intpin 13 -> ISA IRQ 13 (edge, high) ioapic0: intpin 14 -> ISA IRQ 14 (edge, high) ioapic0: intpin 15 -> ISA IRQ 15 (edge, high) MADT: Found IO APIC ID 13, Interrupt 16 at 0xfec01000 ioapic1: intpin 0 -> PCI IRQ 16 (level, low) ioapic1: intpin 1 -> PCI IRQ 17 (level, low) ioapic1: intpin 2 -> PCI IRQ 18 (level, low) ioapic1: intpin 3 -> PCI IRQ 19 (level, low) ioapic1: intpin 4 -> PCI IRQ 20 (level, low) ioapic1: intpin 5 -> PCI IRQ 21 (level, low) ioapic1: intpin 6 -> PCI IRQ 22 (level, low) ioapic1: intpin 7 -> PCI IRQ 23 (level, low) ioapic1: intpin 8 -> PCI IRQ 24 (level, low) ioapic1: intpin 9 -> PCI IRQ 25 (level, low) ioapic1: intpin 10 -> PCI IRQ 26 (level, low) ioapic1: intpin 11 -> PCI IRQ 27 (level, low) ioapic1: intpin 12 -> PCI IRQ 28 (level, low) ioapic1: intpin 13 -> PCI IRQ 29 (level, low) ioapic1: intpin 14 -> PCI IRQ 30 (level, low) ioapic1: intpin 15 -> PCI IRQ 31 (level, low) MADT: Found IO APIC ID 12, Interrupt 32 at 0xfec02000 ioapic2: intpin 0 -> PCI IRQ 32 (level, low) ioapic2: intpin 1 -> PCI IRQ 33 (level, low) ioapic2: intpin 2 -> PCI IRQ 34 (level, low) ioapic2: intpin 3 -> PCI IRQ 35 (level, low) ioapic2: intpin 4 -> PCI IRQ 36 (level, low) ioapic2: intpin 5 -> PCI IRQ 37 (level, low) ioapic2: intpin 6 -> PCI IRQ 38 (level, low) ioapic2: intpin 7 -> PCI IRQ 39 (level, low) ioapic2: intpin 8 -> PCI IRQ 40 (level, low) ioapic2: intpin 9 -> PCI IRQ 41 (level, low) ioapic2: intpin 10 -> PCI IRQ 42 (level, low) ioapic2: intpin 11 -> PCI IRQ 43 (level, low) ioapic2: intpin 12 -> PCI IRQ 44 (level, low) ioapic2: intpin 13 -> PCI IRQ 45 (level, low) ioapic2: intpin 14 -> PCI IRQ 46 (level, low) ioapic2: intpin 15 -> PCI IRQ 47 (level, low) MADT: intr override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 ioapic0: intpin 2 trigger: edge ioapic0: intpin 2 polarity: high lapic0: Routing NMI -> LINT1 MADT: Ignoring local NMI routed to ACPI CPU 6 MADT: Forcing active-low polarity and level trigger for SCI ioapic0: intpin 3 polarity: low ioapic0: intpin 3 trigger: level ioapic2 irqs 32-47 on motherboard ioapic1 irqs 16-31 on motherboard ioapic0 irqs 0-15 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00050014 LDR: 0x01000000 DFR: 0x0fffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff random: io:
mem: Pentium Pro MTRR support enabled null: npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: [MPSAFE] pci_open(1): mode 1 addr port (0x0cf8) is 0x80002800 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00141166) pcibios: BIOS version 2.10 AcpiOsDerivePciId: bus 0 dev 15 func 2 acpi0: Power Button (fixed) AcpiOsDerivePciId: bus 0 dev 0 func 0 AcpiOsDerivePciId: bus 0 dev 16 func 0 AcpiOsDerivePciId: bus 0 dev 16 func 2 AcpiOsDerivePciId: bus 0 dev 17 func 0 AcpiOsDerivePciId: bus 0 dev 17 func 2 acpi0: reservation of 460, 2 (4) failed ACPI timer: 0/3 0/3 0/3 0/3 0/3 0/3 0/3 0/3 0/3 0/3 -> 0 Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x488-0x48b on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: on acpi0 pci0: on pcib0 pci0: physical bus=0 found-> vendor=0x1166, dev=0x0014, revid=0x33 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1166, dev=0x0014, revid=0x00 bus=0, slot=0, func=1 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x1166, dev=0x0014, revid=0x00 bus=0, slot=0, func=2 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0000, statreg=0x0000, cachelnsz=16 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 1, range 32, base fd000000, size 24, enabled map[14]: type 4, range 32, base 00002400, size 8, enabled map[18]: type 1, range 32, base febff000, size 12, enabled pcib0: matched entry for 0.6.INTA pcib0: slot 6 INTA hardwired to IRQ 26 found-> vendor=0x1002, dev=0x4752, revid=0x27 bus=0, slot=6, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0087, statreg=0x0290, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 ns) intpin=a, irq=26 powerspec 2 supports D0 D1 D2 D3 current D0 found-> vendor=0x1166, dev=0x0201, revid=0x93 bus=0, slot=15, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0147, statreg=0x2200, cachelnsz=0 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[20]: type 4, range 32, base 00000700, size 4, enabled found-> vendor=0x1166, dev=0x0212, revid=0x93 bus=0, slot=15, func=1 class=01-01-82, hdrtype=0x00, mfdev=1 cmdreg=0x0155, statreg=0x0200, cachelnsz=8 (dwords) lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 1, range 32, base febfe000, size 12, enabled pcib0: matched entry for 0.15.INTA (src \LPUS:0) Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x48 fault code = supervisor read, page not present instruction pointer = 0x8:0xc051d7a7 stack pointer = 0x10:0xc08208d8 frame pointer = 0x10:0xc08208ec code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) [thread pid 0 tid 0 ] Stopped at device_get_softc+0x7: movl 0x48(%eax),%eax db> tr Tracing pid 0 tid 0 td 0xc06eda40 device_get_softc(c07db4a0,c07d690d,35a,c0820928,c07b0e59) at device_get_softc+0x7 acpi_pci_link_route_interrupt(0,0,c0820a28,f,41) at acpi_pci_link_route_interrupt+0x37 acpi_pcib_route_interrupt(c1f16d00,c1f8b780,1,c1f7e214,1) at acpi_pcib_route_interrupt+0x33c acpi_pcib_acpi_route_interrupt(c1f16d00,c1f8b780,1,c06c60d0,c1f8b808) at acpi_pcib_acpi_route_interrupt+0x2f pci_assign_interrupt_method(c1f16a00,c1f8b780,f,2,24) at pci_assign_interrupt_method+0x71 pci_add_child(c1f16a00,c1f8b800,f,2,80) at pci_add_child+0x207 pci_add_children(c1f16a00,0,80,c0820b54,c051fbaf) at pci_add_children+0x123 acpi_pci_attach(c1f16a00,c1f5684c,c06bf6bc,c06a8919,0) at acpi_pci_attach+0x86 device_attach(c1f16a00,c1ed5d80,c0820bdc,c07c234c,c1f16d00) at device_attach+0x2c9 bus_generic_attach(c1f16d00,c07d61e7,0,c0820bcc,0) at bus_generic_attach+0x18 acpi_pcib_attach(c1f16d00,c1f7e214,0,c0820c04,c07bcf57) at acpi_pcib_attach+0xec acpi_pcib_acpi_attach(c1f16d00,c1f5584c,c06bf6bc,c06a8919,0) at acpi_pcib_acpi_attach+0xf9 device_attach(c1f16d00,2f,c0820cbc,c07bf784,c1ed5d80) at device_attach+0x2c9 bus_generic_attach(c1ed5d80,2e,2f,c1f7dc48,2e) at bus_generic_attach+0x18 acpi_attach(c1ed5d80,c1f5804c,c06bf6bc,c06a8919,0) at acpi_attach+0x7b4 device_attach(c1ed5d80,c1f15000,c0820d18,c067852a,c1f15000) at device_attach+0x2c9 bus_generic_attach(c1f15000,c1f1504c,c0820d54,c051eb59,c1f15000) at bus_generic_attach+0x18 nexus_attach(c1f15000,c1f4684c,c06bf6bc,c06a8919,0) at nexus_attach+0x1a device_attach(c1f15000,c06dbb50,c0820d78,c0665758,c1f15680) at device_attach+0x2c9 root_bus_configure(c1f15680,c06b95b7,0,c0820d98,c04d06a6) at root_bus_configure+0x19 configure(0,0,c1e6f774,81ec00,81e000) at configure+0x28 mi_startup() at mi_startup+0xd6 begin() at begin+0x2c db> (kgdb) l *device_get_softc+0x7 0xc051d7a7 is in device_get_softc (/usr/src/sys/kern/subr_bus.c:1937). 1932 * on the size field of the driver. 1933 */ 1934 void * 1935 device_get_softc(device_t dev) 1936 { 1937 return (dev->softc); 1938 } 1939 1940 /** 1941 * @brief Set the device's softc field (kgdb) l *acpi_pci_link_route_interrupt+0x37 0x35ba7 is in acpi_pci_link_route_interrupt (/usr/src/sys/modules/acpi/acpi/.. /../../dev/acpica/acpi_pci_link.c:860). 855 { 856 struct link *link; 857 858 ACPI_SERIAL_BEGIN(pci_link); 859 link = acpi_pci_link_lookup(dev, index); 860 if (link == NULL) 861 panic("%s: apparently invalid index %d", __func__, index); 862 863 /* 864 * If this link device is already routed to an interrupt, just return (kgdb) l *acpi_pcib_route_interrupt+0x33c 0x327dc is in acpi_pcib_route_interrupt (acpivar.h:208). 203 acpivar.h: No such file or directory. in acpivar.h (kgdb) l *acpi_pcib_acpi_route_interrupt+0x2f 0x32d9f is in acpi_pcib_acpi_route_interrupt (/usr/src/sys/modules/acpi/acpi/.. /../../dev/acpica/acpi_pcib_acpi.c:303). 298 acpi_pcib_acpi_route_interrupt(device_t pcib, device_t dev, int pin) 299 { 300 struct acpi_hpcib_softc *sc = device_get_softc(pcib); 301 302 return (acpi_pcib_route_interrupt(pcib, dev, pin, &sc->ap_prt)); 303 } 304 305 static u_long acpi_host_mem_start = 0x80000000; 306 TUNABLE_ULONG("hw.acpi.host_mem_start", &acpi_host_mem_start); 307 (kgdb) l *pci_assign_interrupt_method+0x71 0xc04b24b1 is in pci_assign_interrupt_method (/usr/src/sys/dev/pci/pci.c: 1814). 1809 struct pci_devinfo *dinfo = device_get_ivars(child); 1810 pcicfgregs *cfg = &dinfo->cfg; 1811 1812 return (PCIB_ROUTE_INTERRUPT(device_get_parent(dev), child, 1813 cfg->intpin)); 1814 } 1815 1816 static int 1817 pci_modevent(module_t mod, int what, void *arg) 1818 { (kgdb) l *pci_add_child+0x207 0xc04b0187 is in pci_add_child (/usr/src/sys/dev/pci/pci.c:940). 935 * firmware may leave bogus values in these registers. 936 * If the re-route fails, then just stick with what we 937 * have. 938 */ 939 irq = PCI_ASSIGN_INTERRUPT(bus, dev); 940 if (PCI_INTERRUPT_VALID(irq)) { 941 pci_write_config(dev, PCIR_INTLINE, irq, 1); 942 cfg->intline = irq; 943 } else 944 #endif (kgdb) ps. sorry for the top-post, lost the original mail. -- Pawel -- Pawel From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 21:18:12 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44EF916A4CE for ; Thu, 9 Dec 2004 21:18:12 +0000 (GMT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73F5843D2D for ; Thu, 9 Dec 2004 21:18:11 +0000 (GMT) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.13.1/8.13.1) with ESMTP id iB9LI9h3002500 for ; Fri, 10 Dec 2004 00:18:10 +0300 (MSK) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.13.1/8.13.1/Submit) id iB9LI9RE002499 for current@freebsd.org; Fri, 10 Dec 2004 00:18:09 +0300 (MSK) (envelope-from ache) Date: Fri, 10 Dec 2004 00:18:08 +0300 From: Andrey Chernov To: current@freebsd.org Message-ID: <20041209211808.GA2477@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i X-AntiVirus: checked by AntiVir Milter (version: 1.1; AVE: 6.29.0.4; VDF: 6.29.0.6; host: nagual.pp.ru) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (nagual.pp.ru [127.0.0.1]); Fri, 10 Dec 2004 00:18:10 +0300 (MSK) Subject: New kernel netgraph warning with recent -current: PPPoE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 21:18:12 -0000 Just start ppp as usual, with set device PPPoE:fxp0 in /etc/ppp/ppp.conf and got kernel warning now: WARNING: attempt to net_add_domain(netgraph) after domainfinalize() Month old -current don't say this. -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 21:26:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C2EE16A4CE for ; Thu, 9 Dec 2004 21:26:25 +0000 (GMT) Received: from pne-smtpout1-sn2.hy.skanova.net (pne-smtpout1-sn2.hy.skanova.net [81.228.8.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F37243D39 for ; Thu, 9 Dec 2004 21:26:24 +0000 (GMT) (envelope-from pawel.worach@telia.com) Received: from pne-ps4-sn1 (81.228.11.133) by pne-smtpout1-sn2.hy.skanova.net (7.1.026.6) id 4199C6960000A5C2 for freebsd-current@freebsd.org; Thu, 9 Dec 2004 22:26:23 +0100 Message-ID: <15219186.1102627583229.JavaMail.tomcat@pne-ps4-sn1> Date: Thu, 9 Dec 2004 22:26:23 +0100 (MET) From: Pawel Worach To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain;charset="ISO-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: CP Presentation Server X-clientstamp: [217.208.189.47] Subject: panic: pmap_mapdev: Couldn't alloc kernel virtual memory on mpt_attach X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: pawel.worach@telia.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 21:26:25 -0000 Booting an IBM x345 box without ACPI (see other problem) generates this panic during the scsi controller probe. It sits on the line before the panic message for about 1-2 minutes. I got a similar/the same panic with ACPI before the other ACPI problem showed up. FreeBSD 6.0-CURRENT #0: Wed Dec 8 17:58:20 CET 2004 root@zero:/usr/obj/usr/src/sys/ZERO MPTable: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.90-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff real memory = 1073590272 (1023 MB) avail memory = 1046147072 (997 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 ioapic0: Assuming intbase of 0 ioapic1: Assuming intbase of 16 ioapic2: Assuming intbase of 32 ioapic2 irqs 32-47 on motherboard ioapic1 irqs 16-31 on motherboard ioapic0 irqs 0-15 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: pcibus 0 on motherboard pci0: on pcib0 pci0: at device 6.0 (no driver attached) atapci0: port 0x700-0x70f,0x376,0x170- 0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 15.2 (no driver attached) isab0: at device 15.3 on pci0 isa0: on isab0 pcib1: pcibus 1 on motherboard pci1: on pcib1 pcib2: pcibus 2 on motherboard pci2: on pcib2 fxp0: port 0x2500-0x253f mem 0xfbfc0000- 0xfbfdffff,0xfbfff000-0xfbffffff irq 20 at device 3.0 on pci2 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:0e:0c:2e:98:88 pcib4: pcibus 4 on motherboard pci4: on pcib4 pcib6: pcibus 6 on motherboard pci6: on pcib6 em0: port 0x2540- 0x257f mem 0xf9fe0000-0xf9ffffff irq 29 at device 8.0 on pci6 em0: Ethernet address: 00:0d:60:1a:4f:c6 em0: Speed:N/A Duplex:N/A em1: port 0x2580- 0x25bf mem 0xf9fc0000-0xf9fdffff irq 30 at device 8.1 on pci6 em1: Ethernet address: 00:0d:60:1a:4f:c7 em1: Speed:N/A Duplex:N/A pcib8: pcibus 8 on motherboard pci8: on pcib8 mpt0: port 0x2600-0x26ff mem 0xf7fe0000- 0xf7feffff,0xf7ff0000-0xf7ffffff irq 27 at device 7.0 on pci8 mpt0: [GIANT-LOCKED] mpt1: port 0x2700-0x27ff mem 0xf7fc0000- 0xf7fcffff,0xf7fd0000-0xf7fdffff irq 28 at device 7.1 on pci8 panic: pmap_mapdev: Couldn't alloc kernel virtual memory cpuid = 0 KDB: enter: panic [thread pid 0 tid 0 ] Stopped at kdb_enter+0x32: leal 0(%esi),%esi db> tr Tracing pid 0 tid 0 td 0xc06eda40 kdb_enter(c06a75b3,0,c06b9a7d,c0820a20,0) at kdb_enter+0x32 panic(c06b9a7d,10000,c1f5eb00,0,0) at panic+0x1f3 pmap_mapdev(f7fd0000,10000,c1f5eb88,c1fcea80,c1f5eb84) at pmap_mapdev+0xd2 nexus_activate_resource(c1ee6e00,c1f5eb00,3,14,c1f79980) at nexus_activate_resource+0xa4 pci_alloc_resource(c1f5ed00,c1f5eb00,3,c1fdee90,0,ffffffff,0,2) at pci_alloc_resource+0x597 bus_alloc_resource(c1f5eb00,3,c1fdee90,0,ffffffff) at bus_alloc_resource+0x7d mpt_attach(c1f5eb00,c1f5eb00,ffffffff,c06a8919,0) at mpt_attach+0x453 device_attach(c1f5eb00,8,c0820bdc,c04b088a,c1f5ed00) at device_attach+0x2c9 bus_generic_attach(c1f5ed00,8,78,c0820bd0,8) at bus_generic_attach+0x18 pci_attach(c1f5ed00,c1f5ed00,ffffffff,c06a8919,0) at pci_attach+0x8a device_attach(c1f5ed00,c1ee6d80,c0820c4c,c0678171,c1ee6a00) at device_attach+0x2c9 bus_generic_attach(c1ee6a00,c06b6d31,8,c0820c40,8) at bus_generic_attach+0x18 mptable_hostb_attach(c1ee6a00,c1ee6a00,ffffffff,c06a8919,0) at mptable_hostb_attach+0x81 device_attach(c1ee6a00,c1ee6dcc,c0820cbc,c0670bff,c1ee6d80) at device_attach+0x2c9 bus_generic_attach(c1ee6d80,c1f373c0,c06bf6bc,c1ee6d80,c1ee6dcc) at bus_generic_attach+0x18 legacy_attach(c1ee6d80,c1f3904c,c06bf6bc,c06a8919,0) at legacy_attach+0x1f device_attach(c1ee6d80,c1ee6e00,c0820d18,c067852a,c1ee6e00) at device_attach+0x2c9 bus_generic_attach(c1ee6e00,c1ee6e4c,c0820d54,c051eb59,c1ee6e00) at bus_generic_attach+0x18 nexus_attach(c1ee6e00,c1f3f04c,c06bf6bc,c06a8919,0) at nexus_attach+0x1a device_attach(c1ee6e00,c06dbb50,c0820d78,c0665758,c1e7f500) at device_attach+0x2c9 root_bus_configure(c1e7f500,c06b95b7,0,c0820d98,c04d06a6) at root_bus_configure+0x19 configure(0,0,c06bc314,81ec00,81e000) at configure+0x28 mi_startup() at mi_startup+0xd6 begin() at begin+0x2c db> (kgdb) l *pmap_mapdev+0xd2 0xc067d342 is at /usr/src/sys/i386/i386/pmap.c:2877. 2872 if (pa < KERNLOAD && pa + size <= KERNLOAD) 2873 va = KERNBASE + pa; 2874 else 2875 va = kmem_alloc_nofault(kernel_map, size); 2876 if (!va) 2877 panic("pmap_mapdev: Couldn't alloc kernel virtual memory"); 2878 2879 for (tmpva = va; size > 0; ) { 2880 pmap_kenter(tmpva, pa); 2881 size -= PAGE_SIZE; (kgdb) l *nexus_activate_resource+0xa4 0xc06788f4 is in nexus_activate_resource (/usr/src/sys/i386/i386/nexus. c:419). 414 415 paddr = rman_get_start(r); 416 psize = rman_get_size(r); 417 418 poffs = paddr - trunc_page(paddr); 419 vaddr = (caddr_t) pmap_mapdev(paddr-poffs, psize+poffs) + poffs; 420 } 421 rman_set_virtual(r, vaddr); 422 #ifdef PC98 423 /* PC-98: the type of bus_space_handle_t is the structure. */ (kgdb) l *pci_alloc_resource+0x597 0xc04b1e87 is in pci_alloc_resource (/usr/src/sys/dev/pci/pci.c:1705). 1700 rman_get_size(rle->res), *rid, type, 1701 rman_get_start(rle->res)); 1702 if ((flags & RF_ACTIVE) && 1703 bus_generic_activate_resource(dev, child, type, 1704 *rid, rle->res) != 0) 1705 return NULL; 1706 return (rle->res); 1707 } 1708 } 1709 return (resource_list_alloc(rl, dev, child, type, rid, (kgdb) l *bus_alloc_resource+0x7d 0xc051c7ed is in bus_alloc_resource (/usr/src/sys/kern/subr_bus.c:3179). 3174 { 3175 if (dev->parent == 0) 3176 return (0); 3177 return (BUS_ALLOC_RESOURCE(dev->parent, dev, type, rid, start, end, 3178 count, flags)); 3179 } 3180 3181 /** 3182 * @brief Wrapper function for BUS_ACTIVATE_RESOURCE(). 3183 * (kgdb) l *mpt_attach+0x453 0xc04aaf93 is in mpt_attach (/usr/src/sys/dev/mpt/mpt_pci.c:309). 304 } 305 306 /* Set up the memory regions */ 307 /* Allocate kernel virtual memory for the 9x9's Mem0 region */ 308 mpt->pci_reg_id = MEM_MAP_REG; 309 mpt->pci_reg = bus_alloc_resource(dev, SYS_RES_MEMORY, 310 &mpt->pci_reg_id, 0, ~0, 0, RF_ACTIVE); 311 if (mpt->pci_reg == NULL) { 312 device_printf(dev, "unable to map any ports\n"); 313 goto bad; (kgdb) -- Pawel From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 22:30:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB9A516A4CE for ; Thu, 9 Dec 2004 22:30:48 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B12243D3F for ; Thu, 9 Dec 2004 22:30:47 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iB9MTiFb009016 for ; Fri, 10 Dec 2004 08:59:45 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Fri, 10 Dec 2004 09:00:36 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iB9MSOQ30480 for ; Fri, 10 Dec 2004 08:58:25 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id YK36MMC4; Fri, 10 Dec 2004 08:58:24 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iB9MSddU018129 for ; Fri, 10 Dec 2004 08:58:39 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iB9MSdTS018128 for freebsd-current@freebsd.org; Fri, 10 Dec 2004 08:58:39 +1030 (CST) (envelope-from wilkinsa) Date: Fri, 10 Dec 2004 08:58:39 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20041209222835.GA18003@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org References: <20041209023154.GA90315@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20041209023154.GA90315@xor.obsecurity.org> User-Agent: Mutt/1.5.6i Subject: Re: panic: process 839(xmms):1 holds process lock but isn't blocked ona lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 22:30:49 -0000 0n Thu, Dec 09, 2004 at 01:01:55PM +1030, Kris Kennaway wrote: > On Thu, Dec 09, 2004 at 11:51:28AM +1030, Wilkinson, Alex wrote: > > Another panic whilst mp3s were playing on xmms: > > What scheduler? SCHED_4BSD - aW From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 23:20:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF66516A4CE for ; Thu, 9 Dec 2004 23:20:58 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E3BF43D49 for ; Thu, 9 Dec 2004 23:20:58 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iB9NJuQn015548 for ; Fri, 10 Dec 2004 09:49:56 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Fri, 10 Dec 2004 09:50:51 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iB9NCEQ01460 for ; Fri, 10 Dec 2004 09:42:14 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id YK36M3WW; Fri, 10 Dec 2004 09:42:14 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iB9NCSQs018319 for ; Fri, 10 Dec 2004 09:42:28 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iB9NCSbX018318 for freebsd-current@freebsd.org; Fri, 10 Dec 2004 09:42:28 +1030 (CST) (envelope-from wilkinsa) Date: Fri, 10 Dec 2004 09:42:28 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20041209231228.GD18003@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: does this mean my kernel is trashed ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 23:20:59 -0000 # sudo indent /boot/kernel/kernel .... Warning@1751: Extra ) Warning@1751: Extra ] Error@1753: Unbalanced parens Error@1753: Statement nesting error Error@1770: Statement nesting error Error@1772: Statement nesting error Error@1774: Statement nesting error Error@1776: Statement nesting error Error@1776: Unbalanced parens Warning@1785: Extra ) Warning@1787: Extra ) Warning@1788: Extra ) 1788: Unterminated literal Warning@1790: Extra ] Warning@1792: Extra ] Error@1793: Statement nesting error Warning@1793: Extra ] Error@1796: Unbalanced parens Error@1796: Statement nesting error Error@1799: Statement nesting error Warning@1799: Extra ] Error@1800: Statement nesting error Error@1801: Statement nesting error Error@1802: Statement nesting error Warning@1802: Extra ] Error@1803: Statement nesting error Warning@1803: Extra ] Warning@1803: Extra ] Error@1804: Statement nesting error Warning@1804: Extra ] Warning@1804: Extra ) Warning@1804: Extra ] Warning@1805: Extra ] Warning@1805: Extra ] Error@1806: Statement nesting error Warning@1807: Extra ] Warning@1807: Extra ] Error@1808: Statement nesting error Warning@1810: Extra ] .... - aW From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 23:26:42 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0710916A4CE for ; Thu, 9 Dec 2004 23:26:42 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF6E843D1F for ; Thu, 9 Dec 2004 23:26:41 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 74CE9512D1; Thu, 9 Dec 2004 15:33:18 -0800 (PST) Date: Thu, 9 Dec 2004 15:33:18 -0800 From: Kris Kennaway To: freebsd-current@freebsd.org Message-ID: <20041209233318.GA21779@xor.obsecurity.org> References: <20041209231228.GD18003@squash.dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="azLHFNyN32YCQGCU" Content-Disposition: inline In-Reply-To: <20041209231228.GD18003@squash.dsto.defence.gov.au> User-Agent: Mutt/1.4.2.1i Subject: Re: does this mean my kernel is trashed ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 23:26:42 -0000 --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Dec 10, 2004 at 09:42:28AM +1030, Wilkinson, Alex wrote: > # sudo indent /boot/kernel/kernel ^ Um, no. Kris --azLHFNyN32YCQGCU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBuOC+Wry0BWjoQKURAoZOAJ0abl/2fkVwPZnBdl5YXRJpQHQ4SQCbB+pe 2MLtiuJInr/X4xL/K4EA6pE= =kKw1 -----END PGP SIGNATURE----- --azLHFNyN32YCQGCU-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 23:31:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D643016A4CE for ; Thu, 9 Dec 2004 23:31:13 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id F402443D5D for ; Thu, 9 Dec 2004 23:31:12 +0000 (GMT) (envelope-from hoang.trung.hai@gmail.com) Received: by rproxy.gmail.com with SMTP id z35so371793rne for ; Thu, 09 Dec 2004 15:31:11 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=Xpoz7EzVK2g8mVsV/9MttUFyaXVdRLvFuWwAqyGzECYc/ZHzFep4+ADr3K1X8YRSIoT+NHNnqECurIx72Rtp6Z3FVIGjK/cojgU2zyEQv5eyfU7DBVwW7Xs9i/stb2B/Bvzbb7BbyQ3pUb0F9hEvlw8sL/517Us+u9b29BSS6L8= Received: by 10.39.3.78 with SMTP id f78mr136768rni; Thu, 09 Dec 2004 15:31:11 -0800 (PST) Received: by 10.38.208.44 with HTTP; Thu, 9 Dec 2004 15:31:11 -0800 (PST) Message-ID: <6f57d9c8041209153125c6a6cc@mail.gmail.com> Date: Fri, 10 Dec 2004 00:31:11 +0100 From: Hoang Trung Hai To: freebsd-current@freebsd.org In-Reply-To: <20041209232109.38C0E16A50E@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041209232109.38C0E16A50E@hub.freebsd.org> Subject: Re: freebsd-current Digest, Vol 82, Issue 9 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Hoang Trung Hai List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 23:31:14 -0000 On Thu, 9 Dec 2004 23:21:09 +0000 (GMT), freebsd-current-request@freebsd.org wrote: > Send freebsd-current mailing list submissions to > freebsd-current@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.freebsd.org/mailman/listinfo/freebsd-current > or, via email, send a message with subject or body 'help' to > freebsd-current-request@freebsd.org > > You can reach the person managing the list at > freebsd-current-owner@freebsd.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of freebsd-current digest..." > > Today's Topics: > > 1. panic: sleeping thread (pid 13224) owns a non-sleepable lock > (Peter Holm) > 2. if_ndis is broken with recent 802.11 changes (Daniel O'Connor) > 3. Re: [TEST] ng_bridge ng_l2tp ng_lmi (Gleb Smirnoff) > 4. new TCL vs. current-6 (Mikhail Teterin) > 5. Re: FreeBSD sound distortion problems with SB Live! fixed > with PREEMPTION (Atte Peltomaki) > 6. Microsoft Wireless Intellimouse Explorer (cjohnson@wcug.wwu.edu) > 7. Re: new TCL vs. current-6 (trorki@area51.capnet.state.tx.us) > 8. Re: WEP does not work? (Hideyuki KURASHINA) > 9. Re: WEP does not work? (Hideyuki KURASHINA) > 10. Re: Microsoft Wireless Intellimouse Explorer (Gavin Atkinson) > 11. Wanted: lots of 6-CURRENT testing (Scott Long) > 12. panic: uma_zone_slab is looping (Peter Holm) > 13. Re: make(1) is broken (Steve Kargl) > 14. Re: Microsoft Wireless Intellimouse Explorer (Gavin Atkinson) > 15. Lots of ACPI warnings with recent -current (Andrey Chernov) > 16. Re: FreeBSD sound distortion problems with SB Live! fixed > with PREEMPTION (Krzysztof Kowalik) > 17. panic not going to debugger? (Andrew R. Reiter) > 18. rtentry recursion panic (fwd) (Andrew R. Reiter) > 19. Re: coredump while trying to build world > (2004.12.08.1600-0800 src) (Mike Hunter) > 20. Re: rtentry recursion panic (fwd) (gnn@freebsd.org) > 21. Re: coredump while trying to build world > (2004.12.08.1600-0800 src) (Steve Kargl) > 22. Re: nfs appears broken (Steve Kargl) > 23. Re: coredump while trying to build world > (2004.12.08.1600-0800 src) (Mike Hunter) > 24. Re: protocol timer running before protocol is fully > initialized (again) (was re: panic: mtx_lock() of spin mutex > ...) (Ruslan Ermilov) > 25. Re: page fault panic in > device_get_softc/acpi_pcib_route_interrupt (Pawel Worach) > 26. New kernel netgraph warning with recent -current: PPPoE > (Andrey Chernov) > 27. panic: pmap_mapdev: Couldn't alloc kernel virtual memory on > mpt_attach (Pawel Worach) > 28. Re: panic: process 839(xmms):1 holds process lock but isn't > blocked ona lock (Wilkinson, Alex) > 29. does this mean my kernel is trashed ? (Wilkinson, Alex) > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 9 Dec 2004 09:27:21 +0100 > From: Peter Holm > Subject: panic: sleeping thread (pid 13224) owns a non-sleepable lock > To: current@freebsd.org > Message-ID: <20041209082721.GA44545@peter.osted.lan> > Content-Type: text/plain; charset=us-ascii > > I can't seem to remember status of this problem? I get a > lot of these lately during stress test: > http://www.holm.cc/stress/log/cons93.html > -- > Peter Holm > > ------------------------------ > > Message: 2 > Date: Thu, 9 Dec 2004 23:06:24 +1030 > From: "Daniel O'Connor" > Subject: if_ndis is broken with recent 802.11 changes > To: freebsd-current@freebsd.org > Cc: sam@freebsd.org > Message-ID: <200412092306.31353.doconnor@gsoft.com.au> > Content-Type: text/plain; charset="us-ascii" > > Hi, > The recent mega commit to the 802.11 stuff has broken if_ndis.. > > [inchoate 23:02] /usr/src/sys/modules/if_ndis >make > Warning: Object directory not changed from original /usr/src/sys/modules/if_ndis > cc -O2 -fno-strict-aliasing -pipe -D_KERNEL -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c > /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c: In function `ndis_setstate_80211': > /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c:1541: error: structure has no member named `ic_wep_mode' > /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c:1541: error: `IEEE80211_WEP_8021X' undeclared (first use in this function) > /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c:1541: error: (Each undeclared identifier is reported only once > /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c:1541: error: for each function it appears in.) > /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c:1542: error: structure has no member named `ic_wep_mode' > /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c: In function `ndis_media_status': > /usr/src/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c:1708: error: `IEEE80211_MODE_TURBO' undeclared (first use in this function) > *** Error code 1 > > Stop in /usr/src/sys/modules/if_ndis. > > If it matters I am using the following driver > http://ftp.us.dell.com/network/R73206.EXE (w70n51.*) > > I have rev 1.72 of if_ndis.c. > > -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 187 bytes > Desc: not available > Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20041209/b805604b/attachment-0001.bin > > ------------------------------ > > Message: 3 > Date: Thu, 9 Dec 2004 15:40:15 +0300 > From: Gleb Smirnoff > Subject: Re: [TEST] ng_bridge ng_l2tp ng_lmi > To: current@freebsd.org, stable@freebsd.org > Message-ID: <20041209124015.GA97077@cell.sick.ru> > Content-Type: text/plain; charset=koi8-r > > The list of untested nodes has been narrowed down > to the following three: > > ng_bridge, ng_l2tp, ng_lmi > > Please, if you use one of these three test this patch: > > http://people.freebsd.org/~glebius/totest/netgraph_callout > > T> On Thu, Dec 02, 2004 at 06:10:48PM +0300, Gleb Smirnoff wrote: > T> T> Dear collegues, > T> T> > T> T> we are working on making netgraph ISR mpsafe. To do it we need to > T> T> fix all (ab)users of bare timeout(9) in src/sys/netgraph. These > T> T> timeout calls are running in synch with netgraph now because timeout(9) > T> T> is Giant-locked. As soon as we mark ISR mpsafe, they are going to break. > T> T> > T> T> This patch semi-mechanically changes all timeout(9) calls to ng_callout(9), > T> T> which runs scheduled callouts in netgraph context: > T> T> > T> T> http://people.freebsd.org/~glebius/totest/netgraph_callout > T> T> > T> T> It can be applied to HEAD or RELENG_5 (not 5.3-RELEASE). It patches > T> T> the following nodes: > T> T> > T> T> ng_bridge.c > T> T> ng_l2tp.c > T> T> ng_lmi.c > T> T> ng_ppp.c > T> T> ng_pppoe.c > T> T> ng_tty.c > T> T> > T> T> If you are using at least one of them, then I'm asking you to test the > T> T> patch and respond. Thanks in advance! > T> T> > T> T> P.S. Sorry for crossposting. The target users are both RELENG_5 and CURRENT. > > -- > Totus tuus, Glebius. > GLEBIUS-RIPN GLEB-RIPE > > ------------------------------ > > Message: 4 > Date: Wed, 8 Dec 2004 12:05:38 -0500 > From: Mikhail Teterin > Subject: new TCL vs. current-6 > To: freebsd-current@FreeBSD.org, freebsd-amd64@FreeBSD.org > Cc: ade@FreeBSD.org > Message-ID: <200412081205.39354.mi+mx@aldan.algebra.com> > Content-Type: text/plain; charset="koi8-u" > > Three of my TCL-based ports fail now on amd64 running current-6. All failures > occur, when an attempt is made to use the TCL-interpreter -- either to run > the port's self-tests, or to generate the manual pages. The failures are > either "Floating point exceptions" or "Segmentation faults" and appear to > only happen on amd64 (may be, on ia64 as well): > > http://people.freebsd.org/~fenner/errorlogs/mi%40aldan.algebra.com.html > > Can anyone confirm being able to use freshly built TCL on amd64 _at all_? > > My ports did not change in months -- what could be wrong with TCL and/or > amd64? > > Thanks! > > -mi > > ------------------------------ > > Message: 5 > Date: Wed, 8 Dec 2004 18:20:22 +0200 > From: "Atte Peltomaki" > Subject: Re: FreeBSD sound distortion problems with SB Live! fixed > with PREEMPTION > To: current@freebsd.org > Message-ID: <20041208162022.GA2968@norsu.kameli.org> > Content-Type: text/plain; charset=us-ascii > > > > To my amazement, it worked completely. Enabling PREEMPTION in the kernel > > > completely "fixes" this problem to the fullest extent. I have not been > > > able to reproduce the problem since using any of the methods described > > > above. > > > > > > I'm hoping that with this new information someone might be able to > > > figure out what is truly causing this problem and can come up with a > > > solution (or is PREEMPTION a good solution?). It seems that only a > > > handful of drivers (emu10k1 is the one I'm having problems with) have > > > this problem. For the record, I am not the only one who has reported > > > this problem to the lists. > > > > I also experience the same problems with sound you've described. > > > > As PREEMPTION seems to stable for you, I tried to turn it on again. > > > > Unfortunately PREEMPTION remains to be completely unusable for me. The > > system freezes within 5 minutes. > > > > The problem is described here: > > http://lists.freebsd.org/pipermail/freebsd-current/2004-September/037949.html > > > > I wonder if no one else gets this kind of problem. > > Last I was running -current, PREEMPTION was just brought back, but it > remained completely unusable for me too. Complete system freeze with no > panic, in matter of minutes. > > -Atte > > ------------------------------ > > Message: 6 > Date: Wed, 8 Dec 2004 09:38:29 -0800 > From: cjohnson@wcug.wwu.edu > Subject: Microsoft Wireless Intellimouse Explorer > To: freebsd-current@freebsd.org > Message-ID: <20041208173829.GA7645@wcug.wwu.edu> > Content-Type: text/plain; charset=us-ascii > > I'd like to help get my Microsoft Wireless Intellimouse Explorer > working under 5.3-RELEASE. I've installed 5.3-RELEASE (x86) and > updated to about 3 AM PST with the GENERIC kernel, and the mouse > is recognized as ums0: > > ums0: Microsoft Microsoft Wireless Intellimouse Explorer\M-. 1.0A, rev 1.10/0.0e, addr 2, iclass 3/1 > ums0: 5 buttons and Z dir. > > So the driver sees it, but I can't get much output from the mouse. > moused starts and sees the device, but I'm unable to move the cursor > in X or on the console. If I kill off moused and point X at > /dev/ums0, X can't open the device and I get the message: > > usbd_setup_pipe: failed to start endpoint, TIMEOUT > > I've also tried ' moused -p /dev/ums0 -i all ' after killing off > moused and I get: > > moused: unable to open /dev/ums0: Input/output error > > I've got about two weeks to poke and prod and I'd like to work > with someone to get this mouse working. I'd rather not have to have a > separate mouse for FreeBSD than for Windows XP. (And as an odd side > note: it works in Solaris 10 (x86), though Solaris won't install > properly on this machine.) > > Any help would be appreciated. I can provide remote access if needed. > > -- > Chris Johnson > cjohnson@wcug.wwu.edu > Tua toga suspina est. > > ------------------------------ > > Message: 7 > Date: Wed, 8 Dec 2004 18:09:16 -0600 (CST) > From: trorki@area51.capnet.state.tx.us > Subject: Re: new TCL vs. current-6 > To: Mikhail Teterin > Cc: freebsd-current@freebsd.org > Message-ID: <20041208180601.T29045@area51.capnet.state.tx.us> > Content-Type: TEXT/PLAIN; charset=US-ASCII > > On Wed, 8 Dec 2004, Mikhail Teterin wrote: > > > Three of my TCL-based ports fail now on amd64 running current-6. All failures > > occur, when an attempt is made to use the TCL-interpreter -- either to run > > the port's self-tests, or to generate the manual pages. The failures are > > either "Floating point exceptions" or "Segmentation faults" and appear to > > only happen on amd64 (may be, on ia64 as well): > > > http://people.freebsd.org/~fenner/errorlogs/mi%40aldan.algebra.com.html > > > Can anyone confirm being able to use freshly built TCL on amd64 _at all_? > > > My ports did not change in months -- what could be wrong with TCL and/or > > amd64? > > I just build expect a few minutes ago on: > > FreeBSD rc.capnet.state.tx.us 5.3-RELEASE FreeBSD 5.3-RELEASE #1: Wed > Dec 8 11:39:15 CST 2004 stu@rc.capnet.state.tx.us:/usr/obj/usr/src/sys/SMP amd64 > > and it seems to work fine, though I haven't pushed it. > > Let me know if you need specific tests. I can do a -current tomorrow, > possibly. > > stu > > ------------------------------ > > Message: 8 > Date: Thu, 09 Dec 2004 22:50:41 +0900 (JST) > From: Hideyuki KURASHINA > Subject: Re: WEP does not work? > To: sam@errno.com > Cc: freebsd-current@freebsd.org > Message-ID: <20041209.225041.63112571.rushani@bl.mmtr.or.jp> > Content-Type: Text/Plain; charset=us-ascii > > Hi, > > >>> On Wed, 8 Dec 2004 17:44:27 -0800, Sam Leffler said: > > > On Wednesday 08 December 2004 05:00 pm, Hideyuki KURASHINA wrote: > > > After rebooting, I set IPv4 and IPv6 addresses and those routes. Because > > > access point supports only 802.11b, I configured my wireless network > > > by 128bit WEP as follows > > > > > > /sbin/ifconfig ath0 nwid MY-SSID nwkey 0x01234567890123456789012345 media > > > autoselect mode 11b > > > > > > then I got following error: > > > > > > ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) > > > ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) > > > ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) > > > ath0: ath_chan_set: unable to reset channel 12 (2467 Mhz) > > > > Weird, can you send me the regdomain and country code: e.g. the output of > > sysctl dev.ath.0. > > Sure. > > # sysctl dev.ath.0 > dev.ath.0.%desc: Atheros 5212 > dev.ath.0.%driver: ath > dev.ath.0.%location: slot=2 function=0 > dev.ath.0.%pnpinfo: vendor=0x168c device=0x1014 subvendor=0x1014 subdevice=0x057e class=0x020000 > dev.ath.0.%parent: pci2 > dev.ath.0.countrycode: 395 > dev.ath.0.regdomain: 67 > dev.ath.0.debug: 0 > dev.ath.0.slottime: 20 > dev.ath.0.acktimeout: 48 > dev.ath.0.ctstimeout: 48 > dev.ath.0.softled: 1 > dev.ath.0.ledpin: 0 > dev.ath.0.txantenna: 0 > dev.ath.0.rxantenna: 1 > dev.ath.0.txintrperiod: 5 > dev.ath.0.diag: 0 > dev.ath.0.tpscale: 0 > dev.ath.0.rate_interval: 1000 > dev.ath.0.rate_raise: 10 > dev.ath.0.rate_raise_threshold: 10 > > Just curiosity, `hw' MIBs print both regdomain and countrycode are 0. > > # sysctl hw.ath > hw.ath.hal.swba_backoff: 0 > hw.ath.hal.sw_brt: 10 > hw.ath.hal.dma_brt: 2 > hw.ath.hal.version: 0.9.14.9 > hw.ath.debug: 0 > hw.ath.regdomain: 0 > hw.ath.countrycode: 0 > hw.ath.xchanmode: 1 > hw.ath.outdoor: 1 > hw.ath.calibrate: 30 > hw.ath.dwell: 200 > > > > # ifconfig ath0 list chan > > > Channel 1 : 2412* Mhz 11g Channel 11 : 2462* Mhz 11g > > > Channel 2 : 2417* Mhz 11g Channel 12 : 2467* Mhz 11a 11g > > > Channel 3 : 2422* Mhz 11g Channel 13 : 2472* Mhz 11g > > > Channel 4 : 2427* Mhz 11g Channel 14 : 2484* Mhz 11b > > > Channel 5 : 2432* Mhz 11g Channel 16 : 5080* Mhz 11a > > > Channel 6 : 2437* Mhz 11g Channel 34 : 5170* Mhz 11a > > > Channel 7 : 2442* Mhz 11g Channel 38 : 5190* Mhz 11a > > > Channel 8 : 2447* Mhz 11a 11g Channel 42 : 5210* Mhz 11a > > > Channel 9 : 2452* Mhz 11g Channel 46 : 5230* Mhz 11a > > > Channel 10 : 2457* Mhz 11g > > > > > > > So it seems channels 8 and 12 are supposedly available. > > Actually, no. I'll show you my AP side wireless network setting. > > % dmesg | grep wi0 > wi0 at pcmcia0 function 0: PLANEX, GW-NS11H Wireless LAN PC Card, > wi0: 802.11 address 00:90:cc:XX:XX:XX > wi0: using RF:PRISM3 MAC:ISL3871(PCMCIA) > wi0: Intersil Firmware: Primary (1.0.7), Station (1.3.5) > wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > > % ifconfig wi0 > wi0: flags=8863 mtu 1500 > ssid MY-SSID nwkey ***** > powersave off > bssid 00:90:cc:XX:XX:XX chan 3 > address: 00:90:cc:XX:XX:XX > media: IEEE802.11 autoselect mode 11b hostap (DS2 hostap) > status: active > inet 192.168.1.7 netmask 0xffffff00 broadcast 192.168.1.255 > inet alias 192.168.1.254 netmask 0xffffffff broadcast 192.168.1.254 > inet6 fe80::290:XXXX:XXXX:XXXX%wi0 prefixlen 64 scopeid 0x4 > inet6 2001:3e0:XXX:X::X prefixlen 64 > > % sudo wiconfig wi0 > NIC serial number: [ 99SA01XXXXXX ] > Station name: [ ] > SSID for IBSS creation: [ MY-SSID ] > Current netname (SSID): [ MY-SSID ] > Desired netname (SSID): [ MY-SSID ] > Current BSSID: [ 00:90:cc:XX:XX:XX ] > Channel list: [ 1 2 3 4 5 6 7 8 9 10 11 12 13 14 ] > IBSS channel: [ 3 ] > Current channel: [ 3 ] > Comms quality/signal/noise: [ 0 81 27 ] > Promiscuous mode: [ Off ] > Port type: [ 6 ] > MAC address: [ 00:90:cc:XX:XX:XX ] > TX rate (selection): [ 0 ] > TX rate (actual speed): [ 2 ] > Beacon Interval (current) [msec]: [ 100 ] > Maximum data length: [ 2304 ] > RTS/CTS handshake threshold: [ 2347 ] > fragmentation threshold: [ 2346 ] > RSSI -> dBm adjustment: [ 100 ] > Create IBSS: [ Off ] > Microwave oven robustness: [ 0 ] > Roaming mode(1:firm,3:disable): [ 1 ] > Access point density: [ 1 ] > Power Mgmt (1=on, 0=off): [ 0 ] > Max sleep time (msec): [ 100 ] > Vendor info: [ Unknown ID: 31 version: 1.3 ] > WEP encryption: [ On ] > Authentication type > (1=OpenSys, 2=Shared Key): [ 1 ] > TX encryption key: [ 1 ] > Encryption keys: [ 0x01234567890123456789012345 ][ ][ ][ ] > > > > It seems that ath0 failed to reset channel. I manually specified channel, > > > then ifconfig shows: > > > > > > # ifconfig -v ath0 > > > ath0: flags=8843 mtu 1500 > > > inet 192.168.1.11 netmask 0xffffff00 broadcast 192.168.1.255 > > > inet6 fe80::20e:XXXX:XXXX:XXXX%ath0 prefixlen 64 scopeid 0x2 > > > inet6 2001:3e0:XX:X::XX prefixlen 64 > > > ether 00:0e:9b:XX:XX:XX > > > media: IEEE 802.11 Wireless Ethernet autoselect mode 11b (DS/11Mbps) > > > status: associated > > > ssid MY-SSID channel 3 (2422) bssid 00:90:cc:XX:XX:XX > > > authmode OPEN privacy ON deftxkey 1 powersavemode OFF > > > powersavesleep 100 txpowmax 14 txpower 60 rtsthreshold 2312 protmode CTS > > > wme roaming AUTO bintval 100 > > > AC_BE cwmin 5 cwmax 10 aifs 3 txopLimit 0 -acm ack > > > cwmin 5 cwmax 10 aifs 3 txopLimit 0 -acm > > > AC_BK cwmin 5 cwmax 10 aifs 7 txopLimit 0 -acm ack > > > cwmin 5 cwmax 10 aifs 7 txopLimit 0 -acm > > > AC_VI cwmin 4 cwmax 5 aifs 2 txopLimit 188 -acm ack > > > cwmin 4 cwmax 5 aifs 2 txopLimit 188 -acm > > > AC_VO cwmin 3 cwmax 4 aifs 2 txopLimit 102 -acm ack > > > cwmin 3 cwmax 4 aifs 2 txopLimit 102 -acm > > > > This doesn't show a key installed. I don't typically use nwkey; I'll have to > > check it. > > I tried > > # /sbin/ifconfig ath0 ssid MY-SSID wepmode on weptxkey 1 wepkey 1:0x01234567890123456789012345 wepkey 2:- wepkey 3:- wepkey 4:- media autoselect mode 11b > > but nothing changed (default router is still not reachable). > > The card in question is labeled ``Atheros AR5BMB-44''. > > http://www.rushani.jp/photo/20041209/12090019.jpg > > -- rushani > > ------------------------------ > > Message: 9 > Date: Thu, 09 Dec 2004 22:59:25 +0900 (JST) > From: Hideyuki KURASHINA > Subject: Re: WEP does not work? > To: Danovitsch@vitsch.net > Cc: FreeBSD-current@FreeBSD.org > Message-ID: <20041209.225925.30166884.rushani@bl.mmtr.or.jp> > Content-Type: Text/Plain; charset=us-ascii > > Hi, > > >>> On Thu, 9 Dec 2004 12:41:02 +0100, "Daan Vreeken [PA4DAN]" said: > > > Have you tried : > > ifconfig ath0 wepmode on > > after setting the wep key? > > I challenged following command lines, > > # /sbin/ifconfig ath0 ssid MY-SSID weptxkey 1 wepkey 1:0x01234567890123456789012345 wepkey 2:- wepkey 3:- wepkey 4:- media autoselect mode 11b > # /sbin/ifconfig ath0 wepmode on > > However, the behavior was not changed. > > -- rushani > > ------------------------------ > > Message: 10 > Date: Thu, 9 Dec 2004 14:23:07 +0000 (GMT) > From: Gavin Atkinson > Subject: Re: Microsoft Wireless Intellimouse Explorer > To: cjohnson@wcug.wwu.edu > Cc: freebsd-current@freebsd.org > Message-ID: <20041209141745.H26445@ury.york.ac.uk> > Content-Type: TEXT/PLAIN; charset=US-ASCII > > On Wed, 8 Dec 2004 cjohnson@wcug.wwu.edu wrote: > > > I'd like to help get my Microsoft Wireless Intellimouse Explorer > > working under 5.3-RELEASE. I've installed 5.3-RELEASE (x86) and > > updated to about 3 AM PST with the GENERIC kernel, and the mouse > > is recognized as ums0: > > > > ums0: Microsoft Microsoft Wireless Intellimouse Explorer\M-. 1.0A, rev 1.10/0.0e, addr 2, iclass 3/1 > > ums0: 5 buttons and Z dir. > > > > So the driver sees it, but I can't get much output from the mouse. > > moused starts and sees the device, but I'm unable to move the cursor > > in X or on the console. If I kill off moused and point X at > > /dev/ums0, X can't open the device and I get the message: > > > > usbd_setup_pipe: failed to start endpoint, TIMEOUT > > > > I've also tried ' moused -p /dev/ums0 -i all ' after killing off > > moused and I get: > > > > moused: unable to open /dev/ums0: Input/output error > > Try the patch at http://www.devrandom.co.uk/freebsd/intellimouse.diff - > and let me know if it works for you. However, from your description, I > suspect it's a different problem so you may not have any success. > > > Any help would be appreciated. I can provide remote access if needed > > If that patch doesn't work, I may take you up on this offer. It would be > nice to get them working. > > Gavin > > ------------------------------ > > Message: 11 > Date: Thu, 09 Dec 2004 07:41:01 -0700 > From: Scott Long > Subject: Wanted: lots of 6-CURRENT testing > To: current@freebsd.org > Message-ID: <41B863FD.7000007@freebsd.org> > Content-Type: text/plain; charset=us-ascii; format=flowed > > All, > > There has been an incredible amount of work going into 6-CURRENT in the > last 5 weeks. With the holidays quickly approaching, now seems like a > good time to step back and start really testing the system to shake out > the bugs and catch the developers before they disappear for the > holidays. In particular, the recent massive changes to the vnode layer > and the upgrade of the net80211 layer and wireless lan drivers needs a > lot of review and testing. Now is also a good time to review the recent > additions to the PR database and start seeing if there are trends > developing and/or areas that need immediate attention. > > While 6-CURRENT remains in a high state of flux I'll also ask that > people carefully consider what to merge into 5-STABLE and when to merge > it. Don't let important bugfixes that would benefit 5-STABLE and > 4-STABLE drop on the floor, but also make sure that they recieve > thorough testing before being merged back. > > Thanks, > > Scott > > ------------------------------ > > Message: 12 > Date: Thu, 9 Dec 2004 15:42:33 +0100 > From: Peter Holm > Subject: panic: uma_zone_slab is looping > To: current@freebsd.org > Message-ID: <20041209144233.GA46928@peter.osted.lan> > Content-Type: text/plain; charset=us-ascii > > I modified: > > $ cvs diff -u uma_core.c > Index: uma_core.c > =================================================================== > RCS file: /home/ncvs/src/sys/vm/uma_core.c,v > retrieving revision 1.110 > diff -u -r1.110 uma_core.c > --- uma_core.c 6 Nov 2004 11:43:30 -0000 1.110 > +++ uma_core.c 9 Dec 2004 14:38:32 -0000 > @@ -1926,6 +1926,7 @@ > { > uma_slab_t slab; > uma_keg_t keg; > + int i; > > keg = zone->uz_keg; > > @@ -1943,7 +1944,8 @@ > > slab = NULL; > > - for (;;) { > + for (i = 0;;i++) { > + KASSERT(i < 10000, ("uma_zone_slab is looping")); > /* > * Find a slab with some space. Prefer slabs that are partially > * used over those that are totally full. This helps to reduce > > and caught this one: > http://www.holm.cc/stress/log/cons94.html > -- > Peter Holm > > ------------------------------ > > Message: 13 > Date: Thu, 9 Dec 2004 08:23:05 -0800 > From: Steve Kargl > Subject: Re: make(1) is broken > To: Harti Brandt > Cc: freebsd-current@freebsd.org > Message-ID: <20041209162305.GB53640@troutmask.apl.washington.edu> > Content-Type: text/plain; charset=us-ascii > > On Thu, Dec 09, 2004 at 11:10:59AM +0100, Harti Brandt wrote: > > On Wed, 8 Dec 2004, Steve Kargl wrote: > > > > SK> > > SK>Stop in /usr/src. > > SK>troutmask:root[203] tail -1 /var/log/messages > > SK>Dec 8 15:58:39 troutmask kernel: pid 4794 (make), uid 0: exited on signal 11 > > SK> > > > > Thanks for the report. This has been caused by make during clean-up to > > remove a path element that was never opened as a directory from the list > > of open directories. Fixed in rev. 1.43 of dir.c. > > Thanks for the fix. > > -- > Steve > > ------------------------------ > > Message: 14 > Date: Thu, 09 Dec 2004 16:48:36 +0000 > From: Gavin Atkinson > Subject: Re: Microsoft Wireless Intellimouse Explorer > To: cjohnson@wcug.wwu.edu > Cc: freebsd-current@freebsd.org > Message-ID: <1102610916.4474.5.camel@buffy.york.ac.uk> > Content-Type: text/plain > > On Thu, 2004-12-09 at 14:23 +0000, Gavin Atkinson wrote: > > On Wed, 8 Dec 2004 cjohnson@wcug.wwu.edu wrote: > > > > > I'd like to help get my Microsoft Wireless Intellimouse Explorer > > > working under 5.3-RELEASE. I've installed 5.3-RELEASE (x86) and > > > updated to about 3 AM PST with the GENERIC kernel, and the mouse > > > is recognized as ums0: > > > > > > ums0: Microsoft Microsoft Wireless Intellimouse Explorer\M-. 1.0A, rev 1.10/0.0e, addr 2, iclass 3/1 > > > ums0: 5 buttons and Z dir. > > > > > > So the driver sees it, but I can't get much output from the mouse. > > > moused starts and sees the device, but I'm unable to move the cursor > > > in X or on the console. > > > > Try the patch at http://www.devrandom.co.uk/freebsd/intellimouse.diff - > > and let me know if it works for you. However, from your description, I > > suspect it's a different problem so you may not have any success. > > Sorry, I should probably just say that it is an updated version of the > patch in PR 70607 and is not all my own work :) > > Gavin > > ------------------------------ > > Message: 15 > Date: Thu, 9 Dec 2004 20:13:55 +0300 > From: Andrey Chernov > Subject: Lots of ACPI warnings with recent -current > To: current@freebsd.org > Message-ID: <20041209171355.GA7967@nagual.pp.ru> > Content-Type: text/plain; charset=us-ascii > > acpi0: on motherboard > ACPI-0252: *** Error: No object was returned from > [\\_SB_.PCI0.PX40.UAR2._STA] (Node 0xc1186240), AE_NOT_EXIST > > It is repeated later about 40 times. > > -- > http://ache.pp.ru/ > > ------------------------------ > > Message: 16 > Date: Thu, 9 Dec 2004 18:29:41 +0100 > From: Krzysztof Kowalik > Subject: Re: FreeBSD sound distortion problems with SB Live! fixed > with PREEMPTION > To: current@freebsd.org > Message-ID: <20041209172941.GA29369@uci.agh.edu.pl> > Content-Type: text/plain; charset=us-ascii > > Ivan Voras [ivoras@fer.hr] wrote: > > [...] > > Not exactly a freeze, but PREEMPTION doesn't help me at all with SB Live > > (slowdowns, stuttering sound, etc.), especially with large amounts of > > filesystem operations (this is 5-stable). > > Exactly. I tried to use both emu10k1 and emu10kx drivers, with kernel > with and without PREEMPTION, and both 5.x and 6.0 serie did behave same. > Intensive I/O made the system quite unusable, and it was not only a > sound-related issue, but a general one -- slow, lagging mouse in X, etc. > > I asked about it on stable@ and somehow got no answers but "me too". > > Finally, I decided to restore my 4.9 system from the backups, where the > problem does not exist. > > Regards, > -- > Krzysztof Kowalik | () ASCII Ribbon Campaign > Computer Center, AGH UST | /\ Support plain text e-mail > > ------------------------------ > > Message: 17 > Date: Thu, 9 Dec 2004 12:45:28 -0500 (EST) > From: "Andrew R. Reiter" > Subject: panic not going to debugger? > To: current@Freebsd.org > Message-ID: <20041209124257.X57958@fledge.watson.org> > Content-Type: TEXT/PLAIN; charset=US-ASCII > > Anyone else experiencing issues when a panic, something simple like a > recursion on a non-recursable lock, occurs, it won't break to DDB? I've > got all the right bits for it (KERNCONF options etc) but seems to have > stopped working since I updated to CURRENT yesterday... after battling > through trying to figure out the do_powerstate=0 issue I was having. > > I have a easily reproducible panic but can't dump or anything b/c of this > problem. So, instead, I'll have to send an email with old information > (line #'s etc)... > > Did I miss something? :-) > > Cheers, > Andrew > > -- > Andrew R. Reiter > arr@watson.org > arr@FreeBSD.org > > ------------------------------ > > Message: 18 > Date: Thu, 9 Dec 2004 12:53:31 -0500 (EST) > From: "Andrew R. Reiter" > Subject: rtentry recursion panic (fwd) > To: current@freebsd.org > Message-ID: <20041209124839.V57958@fledge.watson.org> > Content-Type: TEXT/PLAIN; charset=US-ASCII > > Sending since I know Sam and Bruce are busy; I am busy.. not as busy.. but > busy enough to not have time to track code paths down further than I did > in the below email. > > NOTE: The line # in the panicstr is WRONG! this message was after me > doing some minor printf() additions to see what was going on a bit further > after I was unable to get a good vmcore. > > NOTE: The way I explained the way to reproduce it is a bit more difficult > than it can be done. Ie.. just do: > > ifconfig 10.9.9.100 netmask 255.255.0.0 up > route add default 10.9.0.1 > route delete default > route delete 10.9/16 > route add default 10.9.0.1 > traceroute 10.9.0.1 > panic... > > I explain a bit further in the below email where the actual problem is.. I > just am not sure the exact means it got to that point. I've verified this > exists on CURRENT of yesterday. So it's still lingering.. > > ---------- Forwarded message ---------- > Date: Wed, 1 Dec 2004 03:24:36 -0500 (EST) > From: Andrew R. Reiter > To: sam@freebsd.org, bms@freebsd.org > Subject: rtentry recursion panic > > Sam & Bruce, > > I am admittedly running a slightly out of date CURRENT, but am hoping to > see whether or not you all have seen this (or related) panic. > > The panic string is [ignore line #, added debug goo for own use]: > > _mtx_lock_sleep: recursed on non-recursive mutex rtentry @ > /usr/au_src/sys/net/route.c:1311 > > And the [long] backtrace is: > > #0 doadump () at pcpu.h:159 > #1 0xc0466dee in db_fncall (dummy1=-1065588687, dummy2=0, > dummy3=-563291948, > dummy4=0xde6cd86c "l") at /usr/au_src/sys/ddb/db_command.c:531 > #2 0xc0467184 in db_command_loop () at > /usr/au_src/sys/ddb/db_command.c:349 > #3 0xc0468b8c in db_trap (type=3, code=0) at > /usr/au_src/sys/ddb/db_main.c:221 > #4 0xc064e32e in kdb_trap (type=3, code=0, tf=0xde6cd994) > at /usr/au_src/sys/kern/subr_kdb.c:421 > #5 0xc07d977c in trap (frame= > {tf_fs = -563347432, tf_es = -1067122672, tf_ds = -1065091056, > tf_edi = 0, tf_esi = 1, tf_ebp = -563291692, tf_isp = -563291712, tf_ebx = > -563291648, tf_edx = -1065058018, tf_ecx = -1064210208, tf_eax = > -1065049367, tf_trapno = 3, tf_err = 0, tf_eip = -1067131032, tf_cs = 8, > tf_eflags = 642, tf_esp = -563291660, tf_ss = -1067222809}) at > /usr/au_src/sys/i386/i386/trap.c:577 > #6 0xc07c82aa in calltrap () at /usr/au_src/sys/i386/i386/exception.s:140 > #7 0xde6c0018 in ?? () > #8 0xc0650010 in kvprintf (fmt=0x1
, > func=0x100, > arg=0xc1f1aaf0, radix=-1042196716, ap=0xc1e15714 "D+\213\v\204\v\204") > at /usr/au_src/sys/kern/subr_prf.c:543 > #9 0xc06378e7 in panic (fmt=0x282
) > at /usr/au_src/sys/kern/kern_shutdown.c:525 > #10 0xc06301b1 in _mtx_lock_sleep (m=0xc1e15714, td=0xc1f1aaf0, opts=0, > file=0xc0852322 "/usr/au_src/sys/net/route.c", line=1311) > at /usr/au_src/sys/kern/kern_mutex.c:492 > #11 0xc063023c in _mtx_lock_flags (m=0xc1e15714, opts=0, > file=0xc0852322 "/usr/au_src/sys/net/route.c", line=1311) > at /usr/au_src/sys/kern/kern_mutex.c:273 > #12 0xc06a87ed in rt_check (lrt=0x0, lrt0=0xde6cdab4, dst=0xc1fa7a10) > at /usr/au_src/sys/net/route.c:1311 > #13 0xc06b3481 in arpresolve (ifp=0xc1cea000, rt0=0xc1e156b4, > m=0xc1e0f300, > dst=0xc1fa7a10, desten=0xde6cdad0 "") > at /usr/au_src/sys/netinet/if_ether.c:351 > #14 0xc069c392 in ether_output (ifp=0xc1cea000, m=0xc1e0f300, > dst=0xc1fa7a10, > rt0=0x0) at /usr/au_src/sys/net/if_ethersubr.c:160 > #15 0xc06bd94f in ip_output (m=0xc1e0f300, opt=0xc1cea000, ro=0xde6cdb40, > flags=34, imo=0x0, inp=0xc1faeec4) > at /usr/au_src/sys/netinet/ip_output.c:771 > #16 0xc06bdf81 in rip_output (m=0xc1e0f300, so=0x0, dst=0) > at /usr/au_src/sys/netinet/raw_ip.c:320 > #17 0xc06bea8f in rip_send (so=0xc1d78798, flags=0, m=0xc1e0f300, > nam=0xc1ba51a0, control=0x0, td=0xc1f1aaf0) > at /usr/au_src/sys/netinet/raw_ip.c:784 > #18 0xc066db10 in sosend (so=0xc1d78798, addr=0xc1ba51a0, uio=0xde6cdc54, > top=0xc1e0f300, control=0x0, flags=0, td=0xc1f1aaf0) > at /usr/au_src/sys/kern/uipc_socket.c:816 > #19 0xc06739ea in kern_sendit (td=0xc1f1aaf0, s=7, mp=0xde6cdccc, flags=0, > control=0x0) at /usr/au_src/sys/kern/uipc_syscalls.c:784 > #20 0xc067488c in sendit (td=0xc1f1aaf0, s=7, mp=0xde6cdccc, flags=0) > at /usr/au_src/sys/kern/uipc_syscalls.c:725 > #21 0xc0674b7d in sendto (td=0x0, uap=0x0) > at /usr/au_src/sys/kern/uipc_syscalls.c:841 > #22 0xc07d9bc9 in syscall (frame= > {tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 0, tf_esi = 0, tf_ebp > = -1077941288, tf_isp = -563290764, tf_ebx = 672388112, tf_edx = > 134553600, tf_ecx = 1, tf_eax = 133, tf_trapno = 12, tf_err = 2, tf_eip = > 671908087, tf_cs = 31, tf_eflags = 662, tf_esp = -1077941348, tf_ss = 47}) > at /usr/au_src/sys/i386/i386/trap.c:1003 > #23 0xc07c82ff in Xint0x80_syscall () > at /usr/au_src/sys/i386/i386/exception.s:201 > #24 0x0000002f in ?? () > #25 0x0000002f in ?? () > #26 0x0000002f in ?? () > #27 0x00000000 in ?? () > #28 0x00000000 in ?? () > #29 0xbfbfebd8 in ?? () > #30 0xde6cdd74 in ?? () > #31 0x2813d410 in ?? () > #32 0x08052000 in ?? () > #33 0x00000001 in ?? () > #34 0x00000085 in ?? () > #35 0x0000000c in ?? () > #36 0x00000002 in ?? () > #37 0x280c80f7 in ?? () > #38 0x0000001f in ?? () > #39 0x00000296 in ?? () > #40 0xbfbfeb9c in ?? () > #41 0x0000002f in ?? () > #42 0x00000000 in ?? () > #43 0x00000000 in ?? () > #44 0x00000000 in ?? () > #45 0x00000000 in ?? () > #46 0x1f343000 in ?? () > #47 0x00000000 in ?? () > #48 0xc1f1aaf0 in ?? () > #49 0xde6cda28 in ?? () > #50 0xde6cda10 in ?? () > #51 0xc19da640 in ?? () > #52 0xc0647643 in sched_switch (td=0x0, newtd=0x2813d410, flags=Cannot > access memory at address 0xbfbfebe8 > ) > at /usr/au_src/sys/kern/sched_4bsd.c:865 > (kgdb) > > The recursion takes place in rt_check() after rtalloc1()'ing for a > rt_gwroute since rt0's (*lrt0) rt_gwroute is NULL. The value rtentry > object allocated is pointing at the same address as rt0... and when we > return from rtalloc1() the rtentry object is locked.... so the following > occurs in rt_check() (indent python-esque format): > > rt_check(..., struct rtentry **lrt0, ...) > rt = rt0 = *lrt0 > if (rt) > RT_LOCK(rt) > ...checks to see if RTF_GATEWAY; jumps down since rt_gwroute==0 > RT_UNLOCK(rt0) // remember, rt == rt0, even now due to beginning code > // alloc new gateway rtentry > rt = rtalloc1(rt->rt_gateway, 1, 0); // is rt_gateway safe?? > RT_LOCK(rt0); // BAM! panic.. rt (after rtalloc1()) points to > same addr as rt0... hows that happening?) > > The locked is grabbed in rtalloc1() as well as a refcnt is added (not > marked RTF_CLONING at alloc time). > > I've narrowed down how to reproduce in a reasonable fashion... perhaps > could be narrowed down further, but am starting to get sleepy tonight.. > can help tomorrow. This UP laptop has a bge ethernet nic and a wi > wireless nic. Upon boot, my startup scripts are configured to ifconfig > bge to a 10.x.x.x ipaddress and set the default route (nothing exciting). > The wi device is left untouched. So, to cause the panic... > > # ifconfig wi0 192.168.0.3 netmask 255.255.255.0 ssid BLAH stationname j > # route delete default // Whacks 10.x.x.x default route > # route delete 10.5/16 > # route delete 192.168.0.1 // Shouldnt be there unless pingd or other > # route delete -net 192.168.0 > # route add default 192.168.0.1 > # traceroute 192.168.0.1 > > The traceroute command calls sendto().... and so on (as seen above). > > As you can tell, I've not gone through the code paths in the above steps > to try and determine the root of the problem; my apologies. I plan on > picking this up tomorrow when I have time at work and going from there. > Please let me know if you have any thoughts or can help and would like > more information. > > Cheers, > Andrew > > -- > Andrew R. Reiter > arr@watson.org > arr@FreeBSD.org > > ------------------------------ > > Message: 19 > Date: Thu, 9 Dec 2004 10:10:34 -0800 > From: Mike Hunter > Subject: Re: coredump while trying to build world > (2004.12.08.1600-0800 src) > To: Steve Kargl > Cc: freebsd-current@freebsd.org > Message-ID: <20041209181034.GA16160@ack.Berkeley.EDU> > Content-Type: text/plain; charset=us-ascii > > On Dec 08, "Steve Kargl" wrote: > > > On Wed, Dec 08, 2004 at 04:24:30PM -0800, Mike Hunter wrote: > > > Hi, > > > > > > I'm trying to go from RELENG_5 to HEAD on my new amd64, but I'm bombing > > > out here: > > > > > > cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe -DMAGIC='"/usr/share/misc/magic"' -DBUILTIN_ELF -DELFCORE -DHAVE_CONFIG_H -I/usr/src/lib/libmagic -I/usr/src/lib/libmagic/../../contrib/file -c /usr/src/lib/libmagic/../../contrib/file/softmagic.c -o softmagic.So > > > building shared library libmagic.so.1 > > > Segmentation fault (core dumped) > > > *** Error code 139 > > > > > > > You need to back out the recent changes to make(1). > > In your supfile file that you use with cvsup, set > > > > *default date=2004.11.08.00.00.00 > > src-usrbin > > > > cd /usr/src/usr.bin/make > > make > > make install > > > > PS: surprising the broken make(1) actually works for building > > a new make(1). > > Ugh. I tried cvsupping as you suggested, but it gave the same error. This > morning I cvsup'd again after make was fixed (thanks!), and it *still* gives > the same error. I don't think my installed /usr/bin/make is being updated. > > I forgot to md5 the original make, but this is from this morning's fixed-make > sources: > > bash-2.05b# cd /usr/src/usr.sbin/make > bash-2.05b# make > ... > job.o(.text+0x2973): In function `Job_Init': > : warning: warning: mktemp() possibly used unsafely; consider using mkstemp() > gzip -cn /usr/src/usr.bin/make/make.1 > make.1.gz > bash-2.05b# md5 `which make` > MD5 (/usr/bin/make) = fbb5679f9fde6036770a13ea5d6f9373 > bash-2.05b# find /usr/obj -type f -name make | xargs -L 1 md5 > MD5 (/usr/obj/usr/src/make.amd64/usr/src/usr.bin/make/make) = 5d3d91bf4ca06d1dae5a5d0874589b2c > MD5 (/usr/obj/usr/src/make.amd64/make) = 5d3d91bf4ca06d1dae5a5d0874589b2c > MD5 (/usr/obj/usr/src/usr.bin/make/make) = 0e719846f3f245fa7aa7d3aa2dca0bfd > bash-2.05b# make install > install -s -o root -g wheel -m 555 make /usr/bin > install -o root -g wheel -m 444 make.1.gz /usr/share/man/man1 > bash-2.05b# md5 `which make` > MD5 (/usr/bin/make) = fbb5679f9fde6036770a13ea5d6f9373 > > Why doesn't /usr/bin/make change? Let me guess, there's a bug in make? :| > > I am trying again after copying /usr/obj/usr/src/usr.bin/make/make over > /usr/bin/make by hand. Am I missing something here? Also, what's the > make.amd64 directory about, and why are those make binaries also different? > > Befuddled in Berkeley > > ------------------------------ > > Message: 20 > Date: Thu, 09 Dec 2004 10:25:49 -0800 > From: gnn@freebsd.org > Subject: Re: rtentry recursion panic (fwd) > To: "Andrew R. Reiter" > Cc: current@freebsd.org > Message-ID: > Content-Type: text/plain; charset=US-ASCII > > At Thu, 9 Dec 2004 12:53:31 -0500 (EST), > Andrew R. Reiter wrote: > > > > Sending since I know Sam and Bruce are busy; I am busy.. not as busy.. but > > busy enough to not have time to track code paths down further than I did > > in the below email. > > I'll take a quick look and see if I see anything obvious. > > Later, > George > > ------------------------------ > > Message: 21 > Date: Thu, 9 Dec 2004 10:28:16 -0800 > From: Steve Kargl > Subject: Re: coredump while trying to build world > (2004.12.08.1600-0800 src) > To: Mike Hunter > Cc: freebsd-current@freebsd.org > Message-ID: <20041209182816.GA27303@troutmask.apl.washington.edu> > Content-Type: text/plain; charset=us-ascii > > On Thu, Dec 09, 2004 at 10:10:34AM -0800, Mike Hunter wrote: > > (snip) > > > > > Ugh. I tried cvsupping as you suggested, but it gave the same error. This > > morning I cvsup'd again after make was fixed (thanks!), and it *still* gives > > the same error. I don't think my installed /usr/bin/make is being updated. > > > > I forgot to md5 the original make, but this is from this morning's fixed-make > > sources: > > > > bash-2.05b# cd /usr/src/usr.sbin/make > > bash-2.05b# make > > ... > > job.o(.text+0x2973): In function `Job_Init': > > : warning: warning: mktemp() possibly used unsafely; consider using mkstemp() > > gzip -cn /usr/src/usr.bin/make/make.1 > make.1.gz > > bash-2.05b# md5 `which make` > > MD5 (/usr/bin/make) = fbb5679f9fde6036770a13ea5d6f9373 > > bash-2.05b# find /usr/obj -type f -name make | xargs -L 1 md5 > > MD5 (/usr/obj/usr/src/make.amd64/usr/src/usr.bin/make/make) = 5d3d91bf4ca06d1dae5a5d0874589b2c > > MD5 (/usr/obj/usr/src/make.amd64/make) = 5d3d91bf4ca06d1dae5a5d0874589b2c > > MD5 (/usr/obj/usr/src/usr.bin/make/make) = 0e719846f3f245fa7aa7d3aa2dca0bfd > > bash-2.05b# make install > > install -s -o root -g wheel -m 555 make /usr/bin > > install -o root -g wheel -m 444 make.1.gz /usr/share/man/man1 > > bash-2.05b# md5 `which make` > > MD5 (/usr/bin/make) = fbb5679f9fde6036770a13ea5d6f9373 > > > > Why doesn't /usr/bin/make change? Let me guess, there's a bug in make? :| > > > > I am trying again after copying /usr/obj/usr/src/usr.bin/make/make over > > /usr/bin/make by hand. Am I missing something here? Also, what's the > > make.amd64 directory about, and why are those make binaries also different? > > > > I'm not sure what is causing your problem, I will note that I do not > have a make.amd64 directory. This suggests to me that your src tree > may be messed up. I'm running -current while you appear to be using > RELENG_5 perhaps you need to install from make.amd64 instead of from > make. > > One other thing to do. Clean out your trees. > rm -rf /usr/obj > cd /usr/src > make cleandir && make cleandir (the 2nd cleandir my be unnecessary) > make buildworld > yada yada > > -- > Steve > > ------------------------------ > > Message: 22 > Date: Thu, 9 Dec 2004 12:04:35 -0800 > From: Steve Kargl > Subject: Re: nfs appears broken > To: freebsd-current@freebsd.org > Message-ID: <20041209200435.GA697@troutmask.apl.washington.edu> > Content-Type: text/plain; charset=us-ascii > > On Wed, Dec 08, 2004 at 04:43:35PM -0800, Steve Kargl wrote: > > troutmask:root[201] mount /jumbo > > [udp] jumbo:/data: RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed out > > [udp] jumbo:/data: RPCPROG_NFS: RPC: Port mapper failure - RPC: Timed out > > > > troutmask:root[203] grep jumbo /etc/fstab > > jumbo:/data /jumbo nfs rw,noauto 0 0 > > > > > > This is with world+kernel from about 30 minutes on amd64. I was > > able to mount /jumbo with a kernel from monday. > > > > Argh. I thought this may be related to phk's recent vfs work. > It appears the admin of the NFS server tighten his firewall > rules and locked me out. > > -- > Steve > > ------------------------------ > > Message: 23 > Date: Thu, 9 Dec 2004 12:09:01 -0800 > From: Mike Hunter > Subject: Re: coredump while trying to build world > (2004.12.08.1600-0800 src) > To: Steve Kargl > Cc: freebsd-current@freebsd.org > Message-ID: <20041209200901.GA25184@ack.Berkeley.EDU> > Content-Type: text/plain; charset=us-ascii > > On Dec 09, "Steve Kargl" wrote: > > > I'm not sure what is causing your problem, I will note that I do not > > have a make.amd64 directory. This suggests to me that your src tree > > may be messed up. I'm running -current while you appear to be using > > RELENG_5 perhaps you need to install from make.amd64 instead of from > > make. > > > > One other thing to do. Clean out your trees. > > rm -rf /usr/obj > > cd /usr/src > > make cleandir && make cleandir (the 2nd cleandir my be unnecessary) > > make buildworld > > yada yada > > It looks like rm -rf /usr/obj and make cleandir have gotten me past > buildworld. Thanks Steve. Have no fear that I will pipe up again if there's > more trouble :) > > Mike > > ------------------------------ > > Message: 24 > Date: Thu, 9 Dec 2004 22:33:34 +0200 > From: Ruslan Ermilov > Subject: Re: protocol timer running before protocol is fully > initialized (again) (was re: panic: mtx_lock() of spin mutex ...) > To: Max Laier > Cc: gnn@FreeBSD.org > Message-ID: <20041209203334.GB74745@ip.net.ua> > Content-Type: text/plain; charset="us-ascii" > > Hi Max, > > On Thu, Dec 09, 2004 at 12:34:08PM +0100, Max Laier wrote: > [...] > > in ip_input() - that's not good! Can you send me the trace? I was under the > > impression that net send and esp. reveice is off during this part of the > > initialization. Crashing ip_input() would question that assumption. > > > I don't have a serial attached to this notebook (all my > serial cables are at work), so this is hand-copied from > the screen: > > Timecounters tick every 1.000 msec > panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/netinet/ip_input.c:1096 > KDB: enter: panic > [thread pid 27 tid 100001 ] > Stopped at kdb_enter+0x32: leal 0(%esi),%esi > db> where > Tracing pid 27 tid 100001 td 0xc1219180 > kdb_enter(...) at kdb_enter+0x32 > panic(...) at panic+0x14d > _mtx_lock_flags(...) at _mtx_lock_flags+0x114 > ip_slowtimo(...) at ip_slowtimo+0x2f > pfslowtimo(...) at pfslowtimo+0x82 > softclock(...) at softclock+0x12f > ithread_loop(...) at ithread_loop+0x210 > fork_exit(...) at fork_exit+0xa9 > fork_trampoline(...) at fork_trampoline+0x8 > --- trap 0x1, eip = 0, esp = 0xcdbbbd7c, ebp = 0 --- > > PID 27 is "[CPU 0] swi4: clock sio > > Cheers, > -- > Ruslan Ermilov > ru@FreeBSD.org > FreeBSD committer > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 187 bytes > Desc: not available > Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20041209/47050619/attachment-0001.bin > > ------------------------------ > > Message: 25 > Date: Thu, 9 Dec 2004 22:13:58 +0100 (MET) > From: Pawel Worach > Subject: Re: page fault panic in > device_get_softc/acpi_pcib_route_interrupt > To: freebsd-current@freebsd.org > Message-ID: <20587818.1102626838092.JavaMail.tomcat@pne-ps4-sn1> > Content-Type: text/plain;charset="ISO-8859-1" > > Finally got around to fetch some more info about this. > > boot output and kgdb symbol decodes. > > FreeBSD 6.0-CURRENT #0: Wed Dec 8 17:58:20 CET 2004 > root@zero:/usr/obj/usr/src/sys/ZERO > Preloaded elf kernel "/boot/kernel/kernel" at 0xc07ee000. > Preloaded elf module "/boot/kernel/acpi.ko" at 0xc07ee16c. > Calibrating clock(s) ... i8254 clock: 1193157 Hz > CLK_USE_I8254_CALIBRATION not specified - using default frequency > Timecounter "i8254" frequency 1193182 Hz quality 0 > Calibrating TSC clock ... TSC clock: 2793900608 Hz > CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.90-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > Features=0xbfebfbff PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HT > T,TM,PBE> > real memory = 1073590272 (1023 MB) > Physical memory chunk(s): > 0x0000000000001000 - 0x000000000009cfff, 638976 bytes (156 pages) > 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) > 0x0000000000828000 - 0x000000003edaafff, 1045966848 bytes (255363 pages) > avail memory = 1046142976 (997 MB) > MP Configuration Table version 1.4 found at 0xc009e2a0 > Table 'FACP' at 0x3ffdff00 > Table 'APIC' at 0x3ffdfe80 > MADT: Found table at 0x3ffdfe80 > APIC: Using the MADT enumerator. > MADT: Found CPU APIC ID 0 ACPI ID 0: enabled > SMP: Added CPU 0 (AP) > MADT: Found CPU APIC ID 6 ACPI ID 1: enabled > SMP: Added CPU 6 (AP) > ACPI APIC Table: > APIC ID: physical 0, logical 0:0 > APIC ID: physical 6, logical 0:1 > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 6 > bios32: Found BIOS32 Service Directory header at 0xc00fd790 > bios32: Entry = 0xfd7a1 (c00fd7a1) Rev = 0 Len = 1 > pcibios: PCI BIOS entry at 0xf0000+0xd7dc > pnpbios: Found PnP BIOS data at 0xc00fdf90 > pnpbios: Entry = f0000:444c Rev = 1.0 > Other BIOS signatures found: > APIC: CPU 0 has ACPI ID 0 > APIC: CPU 1 has ACPI ID 1 > MADT: Found IO APIC ID 14, Interrupt 0 at 0xfec00000 > ioapic0: Routing external 8259A's -> intpin 0 > ioapic0: intpin 0 -> ExtINT (edge, high) > ioapic0: intpin 1 -> ISA IRQ 1 (edge, high) > ioapic0: intpin 2 -> ISA IRQ 2 (edge, high) > ioapic0: intpin 3 -> ISA IRQ 3 (edge, high) > ioapic0: intpin 4 -> ISA IRQ 4 (edge, high) > ioapic0: intpin 5 -> ISA IRQ 5 (edge, high) > ioapic0: intpin 6 -> ISA IRQ 6 (edge, high) > ioapic0: intpin 7 -> ISA IRQ 7 (edge, high) > ioapic0: intpin 8 -> ISA IRQ 8 (edge, high) > ioapic0: intpin 9 -> ISA IRQ 9 (edge, high) > ioapic0: intpin 10 -> ISA IRQ 10 (edge, high) > ioapic0: intpin 11 -> ISA IRQ 11 (edge, high) > ioapic0: intpin 12 -> ISA IRQ 12 (edge, high) > ioapic0: intpin 13 -> ISA IRQ 13 (edge, high) > ioapic0: intpin 14 -> ISA IRQ 14 (edge, high) > ioapic0: intpin 15 -> ISA IRQ 15 (edge, high) > MADT: Found IO APIC ID 13, Interrupt 16 at 0xfec01000 > ioapic1: intpin 0 -> PCI IRQ 16 (level, low) > ioapic1: intpin 1 -> PCI IRQ 17 (level, low) > ioapic1: intpin 2 -> PCI IRQ 18 (level, low) > ioapic1: intpin 3 -> PCI IRQ 19 (level, low) > ioapic1: intpin 4 -> PCI IRQ 20 (level, low) > ioapic1: intpin 5 -> PCI IRQ 21 (level, low) > ioapic1: intpin 6 -> PCI IRQ 22 (level, low) > ioapic1: intpin 7 -> PCI IRQ 23 (level, low) > ioapic1: intpin 8 -> PCI IRQ 24 (level, low) > ioapic1: intpin 9 -> PCI IRQ 25 (level, low) > ioapic1: intpin 10 -> PCI IRQ 26 (level, low) > ioapic1: intpin 11 -> PCI IRQ 27 (level, low) > ioapic1: intpin 12 -> PCI IRQ 28 (level, low) > ioapic1: intpin 13 -> PCI IRQ 29 (level, low) > ioapic1: intpin 14 -> PCI IRQ 30 (level, low) > ioapic1: intpin 15 -> PCI IRQ 31 (level, low) > MADT: Found IO APIC ID 12, Interrupt 32 at 0xfec02000 > ioapic2: intpin 0 -> PCI IRQ 32 (level, low) > ioapic2: intpin 1 -> PCI IRQ 33 (level, low) > ioapic2: intpin 2 -> PCI IRQ 34 (level, low) > ioapic2: intpin 3 -> PCI IRQ 35 (level, low) > ioapic2: intpin 4 -> PCI IRQ 36 (level, low) > ioapic2: intpin 5 -> PCI IRQ 37 (level, low) > ioapic2: intpin 6 -> PCI IRQ 38 (level, low) > ioapic2: intpin 7 -> PCI IRQ 39 (level, low) > ioapic2: intpin 8 -> PCI IRQ 40 (level, low) > ioapic2: intpin 9 -> PCI IRQ 41 (level, low) > ioapic2: intpin 10 -> PCI IRQ 42 (level, low) > ioapic2: intpin 11 -> PCI IRQ 43 (level, low) > ioapic2: intpin 12 -> PCI IRQ 44 (level, low) > ioapic2: intpin 13 -> PCI IRQ 45 (level, low) > ioapic2: intpin 14 -> PCI IRQ 46 (level, low) > ioapic2: intpin 15 -> PCI IRQ 47 (level, low) > MADT: intr override: source 0, irq 2 > ioapic0: Routing IRQ 0 -> intpin 2 > ioapic0: intpin 2 trigger: edge > ioapic0: intpin 2 polarity: high > lapic0: Routing NMI -> LINT1 > MADT: Ignoring local NMI routed to ACPI CPU 6 > MADT: Forcing active-low polarity and level trigger for SCI > ioapic0: intpin 3 polarity: low > ioapic0: intpin 3 trigger: level > ioapic2 irqs 32-47 on motherboard > ioapic1 irqs 16-31 on motherboard > ioapic0 irqs 0-15 on motherboard > cpu0 BSP: > ID: 0x00000000 VER: 0x00050014 LDR: 0x01000000 DFR: 0x0fffffff > lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff > random: > io:
> mem: > Pentium Pro MTRR support enabled > null: > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > acpi0: [MPSAFE] > pci_open(1): mode 1 addr port (0x0cf8) is 0x80002800 > pci_open(1a): mode1res=0x80000000 (0x80000000) > pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00141166) > pcibios: BIOS version 2.10 > AcpiOsDerivePciId: bus 0 dev 15 func 2 > acpi0: Power Button (fixed) > AcpiOsDerivePciId: bus 0 dev 0 func 0 > AcpiOsDerivePciId: bus 0 dev 16 func 0 > AcpiOsDerivePciId: bus 0 dev 16 func 2 > AcpiOsDerivePciId: bus 0 dev 17 func 0 > AcpiOsDerivePciId: bus 0 dev 17 func 2 > acpi0: reservation of 460, 2 (4) failed > ACPI timer: 0/3 0/3 0/3 0/3 0/3 0/3 0/3 0/3 0/3 0/3 -> 0 > Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x488-0x48b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > pcib0: on acpi0 > pci0: on pcib0 > pci0: physical bus=0 > found-> vendor=0x1166, dev=0x0014, revid=0x33 > bus=0, slot=0, func=0 > class=06-00-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0000, statreg=0x0000, cachelnsz=16 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > found-> vendor=0x1166, dev=0x0014, revid=0x00 > bus=0, slot=0, func=1 > class=06-00-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0000, statreg=0x0000, cachelnsz=16 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > found-> vendor=0x1166, dev=0x0014, revid=0x00 > bus=0, slot=0, func=2 > class=06-00-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0000, statreg=0x0000, cachelnsz=16 (dwords) > lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > map[10]: type 1, range 32, base fd000000, size 24, enabled > map[14]: type 4, range 32, base 00002400, size 8, enabled > map[18]: type 1, range 32, base febff000, size 12, enabled > pcib0: matched entry for 0.6.INTA > pcib0: slot 6 INTA hardwired to IRQ 26 > found-> vendor=0x1002, dev=0x4752, revid=0x27 > bus=0, slot=6, func=0 > class=03-00-00, hdrtype=0x00, mfdev=0 > cmdreg=0x0087, statreg=0x0290, cachelnsz=8 (dwords) > lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x00 (0 > ns) > intpin=a, irq=26 > powerspec 2 supports D0 D1 D2 D3 current D0 > found-> vendor=0x1166, dev=0x0201, revid=0x93 > bus=0, slot=15, func=0 > class=06-00-00, hdrtype=0x00, mfdev=1 > cmdreg=0x0147, statreg=0x2200, cachelnsz=0 (dwords) > lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > map[20]: type 4, range 32, base 00000700, size 4, enabled > found-> vendor=0x1166, dev=0x0212, revid=0x93 > bus=0, slot=15, func=1 > class=01-01-82, hdrtype=0x00, mfdev=1 > cmdreg=0x0155, statreg=0x0200, cachelnsz=8 (dwords) > lattimer=0x40 (1920 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) > map[10]: type 1, range 32, base febfe000, size 12, enabled > pcib0: matched entry for 0.15.INTA (src \LPUS:0) > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x48 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc051d7a7 > stack pointer = 0x10:0xc08208d8 > frame pointer = 0x10:0xc08208ec > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 0 (swapper) > [thread pid 0 tid 0 ] > Stopped at device_get_softc+0x7: movl 0x48(%eax),%eax > db> tr > Tracing pid 0 tid 0 td 0xc06eda40 > device_get_softc(c07db4a0,c07d690d,35a,c0820928,c07b0e59) at device_get_softc+0x7 > acpi_pci_link_route_interrupt(0,0,c0820a28,f,41) at acpi_pci_link_route_interrupt+0x37 > acpi_pcib_route_interrupt(c1f16d00,c1f8b780,1,c1f7e214,1) at acpi_pcib_route_interrupt+0x33c > acpi_pcib_acpi_route_interrupt(c1f16d00,c1f8b780,1,c06c60d0,c1f8b808) at > acpi_pcib_acpi_route_interrupt+0x2f > pci_assign_interrupt_method(c1f16a00,c1f8b780,f,2,24) at pci_assign_interrupt_method+0x71 > pci_add_child(c1f16a00,c1f8b800,f,2,80) at pci_add_child+0x207 > pci_add_children(c1f16a00,0,80,c0820b54,c051fbaf) at pci_add_children+0x123 > acpi_pci_attach(c1f16a00,c1f5684c,c06bf6bc,c06a8919,0) at acpi_pci_attach+0x86 > device_attach(c1f16a00,c1ed5d80,c0820bdc,c07c234c,c1f16d00) at device_attach+0x2c9 > bus_generic_attach(c1f16d00,c07d61e7,0,c0820bcc,0) at bus_generic_attach+0x18 > acpi_pcib_attach(c1f16d00,c1f7e214,0,c0820c04,c07bcf57) at acpi_pcib_attach+0xec > acpi_pcib_acpi_attach(c1f16d00,c1f5584c,c06bf6bc,c06a8919,0) at acpi_pcib_acpi_attach+0xf9 > device_attach(c1f16d00,2f,c0820cbc,c07bf784,c1ed5d80) at device_attach+0x2c9 > bus_generic_attach(c1ed5d80,2e,2f,c1f7dc48,2e) at bus_generic_attach+0x18 > acpi_attach(c1ed5d80,c1f5804c,c06bf6bc,c06a8919,0) at acpi_attach+0x7b4 > device_attach(c1ed5d80,c1f15000,c0820d18,c067852a,c1f15000) at device_attach+0x2c9 > bus_generic_attach(c1f15000,c1f1504c,c0820d54,c051eb59,c1f15000) at bus_generic_attach+0x18 > nexus_attach(c1f15000,c1f4684c,c06bf6bc,c06a8919,0) at nexus_attach+0x1a > device_attach(c1f15000,c06dbb50,c0820d78,c0665758,c1f15680) at device_attach+0x2c9 > root_bus_configure(c1f15680,c06b95b7,0,c0820d98,c04d06a6) at root_bus_configure+0x19 > configure(0,0,c1e6f774,81ec00,81e000) at configure+0x28 > mi_startup() at mi_startup+0xd6 > begin() at begin+0x2c > db> > > (kgdb) l *device_get_softc+0x7 > 0xc051d7a7 is in device_get_softc (/usr/src/sys/kern/subr_bus.c:1937). > 1932 * on the size field of the driver. > 1933 */ > 1934 void * > 1935 device_get_softc(device_t dev) > 1936 { > 1937 return (dev->softc); > 1938 } > 1939 > 1940 /** > 1941 * @brief Set the device's softc field > (kgdb) l *acpi_pci_link_route_interrupt+0x37 > 0x35ba7 is in acpi_pci_link_route_interrupt (/usr/src/sys/modules/acpi/acpi/.. > /../../dev/acpica/acpi_pci_link.c:860). > 855 { > 856 struct link *link; > 857 > 858 ACPI_SERIAL_BEGIN(pci_link); > 859 link = acpi_pci_link_lookup(dev, index); > 860 if (link == NULL) > 861 panic("%s: apparently invalid index %d", __func__, > index); > 862 > 863 /* > 864 * If this link device is already routed to an interrupt, > just return > (kgdb) l *acpi_pcib_route_interrupt+0x33c > 0x327dc is in acpi_pcib_route_interrupt (acpivar.h:208). > 203 acpivar.h: No such file or directory. > in acpivar.h > (kgdb) l *acpi_pcib_acpi_route_interrupt+0x2f > 0x32d9f is in acpi_pcib_acpi_route_interrupt (/usr/src/sys/modules/acpi/acpi/.. > /../../dev/acpica/acpi_pcib_acpi.c:303). > 298 acpi_pcib_acpi_route_interrupt(device_t pcib, device_t dev, int > pin) > 299 { > 300 struct acpi_hpcib_softc *sc = device_get_softc(pcib); > 301 > 302 return (acpi_pcib_route_interrupt(pcib, dev, pin, &sc->ap_prt)); > 303 } > 304 > 305 static u_long acpi_host_mem_start = 0x80000000; > 306 TUNABLE_ULONG("hw.acpi.host_mem_start", &acpi_host_mem_start); > 307 > (kgdb) l *pci_assign_interrupt_method+0x71 > 0xc04b24b1 is in pci_assign_interrupt_method (/usr/src/sys/dev/pci/pci.c: > 1814). > 1809 struct pci_devinfo *dinfo = device_get_ivars(child); > 1810 pcicfgregs *cfg = &dinfo->cfg; > 1811 > 1812 return (PCIB_ROUTE_INTERRUPT(device_get_parent(dev), child, > 1813 cfg->intpin)); > 1814 } > 1815 > 1816 static int > 1817 pci_modevent(module_t mod, int what, void *arg) > 1818 { > (kgdb) l *pci_add_child+0x207 > 0xc04b0187 is in pci_add_child (/usr/src/sys/dev/pci/pci.c:940). > 935 * firmware may leave bogus values in these registers. > 936 * If the re-route fails, then just stick with > what we > 937 * have. > 938 */ > 939 irq = PCI_ASSIGN_INTERRUPT(bus, dev); > 940 if (PCI_INTERRUPT_VALID(irq)) { > 941 pci_write_config(dev, PCIR_INTLINE, irq, > 1); > 942 cfg->intline = irq; > 943 } else > 944 #endif > (kgdb) > > ps. sorry for the top-post, lost the original mail. > > -- > Pawel > > -- > Pawel > > ------------------------------ > > Message: 26 > Date: Fri, 10 Dec 2004 00:18:08 +0300 > From: Andrey Chernov > Subject: New kernel netgraph warning with recent -current: PPPoE > To: current@freebsd.org > Message-ID: <20041209211808.GA2477@nagual.pp.ru> > Content-Type: text/plain; charset=us-ascii > > Just start ppp as usual, with > set device PPPoE:fxp0 > in /etc/ppp/ppp.conf and got kernel warning now: > WARNING: attempt to net_add_domain(netgraph) after domainfinalize() > > Month old -current don't say this. > > -- > http://ache.pp.ru/ > > ------------------------------ > > Message: 27 > Date: Thu, 9 Dec 2004 22:26:23 +0100 (MET) > From: Pawel Worach > Subject: panic: pmap_mapdev: Couldn't alloc kernel virtual memory on > mpt_attach > To: freebsd-current@freebsd.org > Message-ID: <15219186.1102627583229.JavaMail.tomcat@pne-ps4-sn1> > Content-Type: text/plain;charset="ISO-8859-1" > > Booting an IBM x345 box without ACPI (see other problem) generates this > panic during > the scsi controller probe. It sits on the line before the panic message > for about 1-2 minutes. > I got a similar/the same panic with ACPI before the other ACPI problem > showed up. > > FreeBSD 6.0-CURRENT #0: Wed Dec 8 17:58:20 CET 2004 > root@zero:/usr/obj/usr/src/sys/ZERO > MPTable: > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.90-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > Features=0xbfebfbff PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PB > E> > real memory = 1073590272 (1023 MB) > avail memory = 1046147072 (997 MB) > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 6 > ioapic0: Assuming intbase of 0 > ioapic1: Assuming intbase of 16 > ioapic2: Assuming intbase of 32 > ioapic2 irqs 32-47 on motherboard > ioapic1 irqs 16-31 on motherboard > ioapic0 irqs 0-15 on motherboard > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > pcib0: pcibus 0 on motherboard > pci0: on pcib0 > pci0: at device 6.0 (no driver attached) > atapci0: port 0x700-0x70f,0x376,0x170- > 0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 > ata0: channel #0 on atapci0 > ata1: channel #1 on atapci0 > pci0: at device 15.2 (no driver attached) > isab0: at device 15.3 on pci0 > isa0: on isab0 > pcib1: pcibus 1 on motherboard > pci1: on pcib1 > pcib2: pcibus 2 on motherboard > pci2: on pcib2 > fxp0: port 0x2500-0x253f mem 0xfbfc0000- > 0xfbfdffff,0xfbfff000-0xfbffffff irq 20 at device 3.0 on pci2 > miibus0: on fxp0 > inphy0: on miibus0 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > fxp0: Ethernet address: 00:0e:0c:2e:98:88 > pcib4: pcibus 4 on motherboard > pci4: on pcib4 > pcib6: pcibus 6 on motherboard > pci6: on pcib6 > em0: port 0x2540- > 0x257f mem 0xf9fe0000-0xf9ffffff irq 29 at device 8.0 on pci6 > em0: Ethernet address: 00:0d:60:1a:4f:c6 > em0: Speed:N/A Duplex:N/A > em1: port 0x2580- > 0x25bf mem 0xf9fc0000-0xf9fdffff irq 30 at device 8.1 on pci6 > em1: Ethernet address: 00:0d:60:1a:4f:c7 > em1: Speed:N/A Duplex:N/A > pcib8: pcibus 8 on motherboard > pci8: on pcib8 > mpt0: port 0x2600-0x26ff mem 0xf7fe0000- > 0xf7feffff,0xf7ff0000-0xf7ffffff irq 27 at device 7.0 on pci8 > mpt0: [GIANT-LOCKED] > mpt1: port 0x2700-0x27ff mem 0xf7fc0000- > 0xf7fcffff,0xf7fd0000-0xf7fdffff irq 28 at device 7.1 on pci8 > panic: pmap_mapdev: Couldn't alloc kernel virtual memory > cpuid = 0 > KDB: enter: panic > [thread pid 0 tid 0 ] > Stopped at kdb_enter+0x32: leal 0(%esi),%esi > db> tr > Tracing pid 0 tid 0 td 0xc06eda40 > kdb_enter(c06a75b3,0,c06b9a7d,c0820a20,0) at kdb_enter+0x32 > panic(c06b9a7d,10000,c1f5eb00,0,0) at panic+0x1f3 > pmap_mapdev(f7fd0000,10000,c1f5eb88,c1fcea80,c1f5eb84) at pmap_mapdev+0xd2 > nexus_activate_resource(c1ee6e00,c1f5eb00,3,14,c1f79980) at nexus_activate_resource+0xa4 > pci_alloc_resource(c1f5ed00,c1f5eb00,3,c1fdee90,0,ffffffff,0,2) at pci_alloc_resource+0x597 > bus_alloc_resource(c1f5eb00,3,c1fdee90,0,ffffffff) at bus_alloc_resource+0x7d > mpt_attach(c1f5eb00,c1f5eb00,ffffffff,c06a8919,0) at mpt_attach+0x453 > device_attach(c1f5eb00,8,c0820bdc,c04b088a,c1f5ed00) at device_attach+0x2c9 > bus_generic_attach(c1f5ed00,8,78,c0820bd0,8) at bus_generic_attach+0x18 > pci_attach(c1f5ed00,c1f5ed00,ffffffff,c06a8919,0) at pci_attach+0x8a > device_attach(c1f5ed00,c1ee6d80,c0820c4c,c0678171,c1ee6a00) at device_attach+0x2c9 > bus_generic_attach(c1ee6a00,c06b6d31,8,c0820c40,8) at bus_generic_attach+0x18 > mptable_hostb_attach(c1ee6a00,c1ee6a00,ffffffff,c06a8919,0) at mptable_hostb_attach+0x81 > device_attach(c1ee6a00,c1ee6dcc,c0820cbc,c0670bff,c1ee6d80) at device_attach+0x2c9 > bus_generic_attach(c1ee6d80,c1f373c0,c06bf6bc,c1ee6d80,c1ee6dcc) at bus_generic_attach+0x18 > legacy_attach(c1ee6d80,c1f3904c,c06bf6bc,c06a8919,0) at legacy_attach+0x1f > device_attach(c1ee6d80,c1ee6e00,c0820d18,c067852a,c1ee6e00) at device_attach+0x2c9 > bus_generic_attach(c1ee6e00,c1ee6e4c,c0820d54,c051eb59,c1ee6e00) at bus_generic_attach+0x18 > nexus_attach(c1ee6e00,c1f3f04c,c06bf6bc,c06a8919,0) at nexus_attach+0x1a > device_attach(c1ee6e00,c06dbb50,c0820d78,c0665758,c1e7f500) at device_attach+0x2c9 > root_bus_configure(c1e7f500,c06b95b7,0,c0820d98,c04d06a6) at root_bus_configure+0x19 > configure(0,0,c06bc314,81ec00,81e000) at configure+0x28 > mi_startup() at mi_startup+0xd6 > begin() at begin+0x2c > db> > > (kgdb) l *pmap_mapdev+0xd2 > 0xc067d342 is at /usr/src/sys/i386/i386/pmap.c:2877. > 2872 if (pa < KERNLOAD && pa + size <= KERNLOAD) > 2873 va = KERNBASE + pa; > 2874 else > 2875 va = kmem_alloc_nofault(kernel_map, size); > 2876 if (!va) > 2877 panic("pmap_mapdev: Couldn't alloc kernel virtual > memory"); > 2878 > 2879 for (tmpva = va; size > 0; ) { > 2880 pmap_kenter(tmpva, pa); > 2881 size -= PAGE_SIZE; > (kgdb) l *nexus_activate_resource+0xa4 > 0xc06788f4 is in nexus_activate_resource (/usr/src/sys/i386/i386/nexus. > c:419). > 414 > 415 paddr = rman_get_start(r); > 416 psize = rman_get_size(r); > 417 > 418 poffs = paddr - trunc_page(paddr); > 419 vaddr = (caddr_t) pmap_mapdev(paddr-poffs, > psize+poffs) + poffs; > 420 } > 421 rman_set_virtual(r, vaddr); > 422 #ifdef PC98 > 423 /* PC-98: the type of bus_space_handle_t is the > structure. */ > (kgdb) l *pci_alloc_resource+0x597 > 0xc04b1e87 is in pci_alloc_resource (/usr/src/sys/dev/pci/pci.c:1705). > 1700 rman_get_size(rle->res), *rid, > type, > 1701 rman_get_start(rle->res)); > 1702 if ((flags & RF_ACTIVE) && > 1703 bus_generic_activate_resource(dev, > child, type, > 1704 *rid, rle->res) != 0) > 1705 return NULL; > 1706 return (rle->res); > 1707 } > 1708 } > 1709 return (resource_list_alloc(rl, dev, child, type, rid, > (kgdb) l *bus_alloc_resource+0x7d > 0xc051c7ed is in bus_alloc_resource (/usr/src/sys/kern/subr_bus.c:3179). > 3174 { > 3175 if (dev->parent == 0) > 3176 return (0); > 3177 return (BUS_ALLOC_RESOURCE(dev->parent, dev, type, rid, > start, end, > 3178 count, flags)); > 3179 } > 3180 > 3181 /** > 3182 * @brief Wrapper function for BUS_ACTIVATE_RESOURCE(). > 3183 * > (kgdb) l *mpt_attach+0x453 > 0xc04aaf93 is in mpt_attach (/usr/src/sys/dev/mpt/mpt_pci.c:309). > 304 } > 305 > 306 /* Set up the memory regions */ > 307 /* Allocate kernel virtual memory for the 9x9's Mem0 region > */ > 308 mpt->pci_reg_id = MEM_MAP_REG; > 309 mpt->pci_reg = bus_alloc_resource(dev, SYS_RES_MEMORY, > 310 &mpt->pci_reg_id, 0, ~0, 0, RF_ACTIVE); > 311 if (mpt->pci_reg == NULL) { > 312 device_printf(dev, "unable to map any ports\n"); > 313 goto bad; > (kgdb) > > -- > Pawel > > ------------------------------ > > Message: 28 > Date: Fri, 10 Dec 2004 08:58:39 +1030 > From: "Wilkinson, Alex" > Subject: Re: panic: process 839(xmms):1 holds process lock but isn't > blocked ona lock > To: freebsd-current@freebsd.org > Message-ID: <20041209222835.GA18003@squash.dsto.defence.gov.au> > Content-Type: text/plain; charset="us-ascii" > > 0n Thu, Dec 09, 2004 at 01:01:55PM +1030, Kris Kennaway wrote: > > > On Thu, Dec 09, 2004 at 11:51:28AM +1030, Wilkinson, Alex wrote: > > > Another panic whilst mp3s were playing on xmms: > > > > What scheduler? > > SCHED_4BSD > > - aW > > ------------------------------ > > Message: 29 > Date: Fri, 10 Dec 2004 09:42:28 +1030 > From: "Wilkinson, Alex" > Subject: does this mean my kernel is trashed ? > To: freebsd-current@freebsd.org > Message-ID: <20041209231228.GD18003@squash.dsto.defence.gov.au> > Content-Type: text/plain; charset="us-ascii" > > # sudo indent /boot/kernel/kernel > > .... > > Warning@1751: Extra ) > Warning@1751: Extra ] > Error@1753: Unbalanced parens > Error@1753: Statement nesting error > Error@1770: Statement nesting error > Error@1772: Statement nesting error > Error@1774: Statement nesting error > Error@1776: Statement nesting error > Error@1776: Unbalanced parens > Warning@1785: Extra ) > Warning@1787: Extra ) > Warning@1788: Extra ) > 1788: Unterminated literal > Warning@1790: Extra ] > Warning@1792: Extra ] > Error@1793: Statement nesting error > Warning@1793: Extra ] > Error@1796: Unbalanced parens > Error@1796: Statement nesting error > Error@1799: Statement nesting error > Warning@1799: Extra ] > Error@1800: Statement nesting error > Error@1801: Statement nesting error > Error@1802: Statement nesting error > Warning@1802: Extra ] > Error@1803: Statement nesting error > Warning@1803: Extra ] > Warning@1803: Extra ] > Error@1804: Statement nesting error > Warning@1804: Extra ] > Warning@1804: Extra ) > Warning@1804: Extra ] > Warning@1805: Extra ] > Warning@1805: Extra ] > Error@1806: Statement nesting error > Warning@1807: Extra ] > Warning@1807: Extra ] > Error@1808: Statement nesting error > Warning@1810: Extra ] > > .... > > - aW > > ------------------------------ > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > End of freebsd-current Digest, Vol 82, Issue 9 > ********************************************** > From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 23:33:09 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05A3416A4CE for ; Thu, 9 Dec 2004 23:33:09 +0000 (GMT) Received: from smtpx.spintech.ro (smtpx.spintech.ro [81.181.24.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF40143D1D for ; Thu, 9 Dec 2004 23:33:08 +0000 (GMT) (envelope-from aanton@spintech.ro) Received: from smtpx.spintech.ro (jail-clamsmtp [15.0.0.1]) by smtpx.spintech.ro (Postfix) with ESMTP id 714C23A4F2; Thu, 9 Dec 2004 22:18:37 +0000 (UTC) Received: from [81.181.24.230] (beastie.spintech.ro [81.181.24.230]) by smtpx.spintech.ro (Postfix) with ESMTP id 2CF483A4DF; Thu, 9 Dec 2004 22:18:37 +0000 (UTC) Message-ID: <41B8E0B9.9030602@spintech.ro> Date: Fri, 10 Dec 2004 01:33:13 +0200 From: Alin-Adrian Anton User-Agent: Mozilla Thunderbird 0.8 (X11/20041016) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Wilkinson, Alex" References: <20041209231228.GD18003@squash.dsto.defence.gov.au> In-Reply-To: <20041209231228.GD18003@squash.dsto.defence.gov.au> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AV-Checked: ClamAV using ClamSMTP cc: freebsd-current@freebsd.org Subject: Re: does this mean my kernel is trashed ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 23:33:09 -0000 Wilkinson, Alex wrote: > # sudo indent /boot/kernel/kernel > No. According to the man pages, indent is a tool used to "indent and format C program source". On the other hand, /boot/kernel/kernel is already compiled code, it's not a .c source file. You can check that with the "file" utility: %file /boot/kernel/kernel /boot/kernel/kernel: ELF 32-bit LSB executable, Intel 80386, version 1 (FreeBSD), dynamically linked (uses shared libs), not stripped % (that corresponds to my system) Regards, -- Alin-Adrian Anton Spintech Systems GPG keyID 0x1E2FFF2E (2963 0C11 1AF1 96F6 0030 6EE9 D323 639D 1E2F FF2E) gpg --keyserver pgp.mit.edu --recv-keys 1E2FFF2E From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 00:09:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D68EC16A4CE; Fri, 10 Dec 2004 00:09:40 +0000 (GMT) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D9E043D68; Fri, 10 Dec 2004 00:09:40 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from h00609772adf0.ne.client2.attbi.com ([66.30.114.143]) by comcast.net (sccrmhc11) with ESMTP id <2004121000093501100es9f1e>; Fri, 10 Dec 2004 00:09:35 +0000 Received: from h00609772adf0.ne.client2.attbi.com (localhost [127.0.0.1]) iBA09YuZ005390; Thu, 9 Dec 2004 19:09:34 -0500 (EST) (envelope-from rodrigc@h00609772adf0.ne.client2.attbi.com) Received: (from rodrigc@localhost)iBA09YFq005389; Thu, 9 Dec 2004 19:09:34 -0500 (EST) (envelope-from rodrigc) Date: Thu, 9 Dec 2004 19:09:33 -0500 From: Craig Rodrigues To: freebsd-current@freebsd.org Message-ID: <20041210000933.GA5325@crodrigues.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i cc: freebsd-docs@freebsd.org Subject: hw.ata.atapi_dma patch for ata(4) man page? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 00:09:41 -0000 Hi, In ata(4), it states: hw.ata.atapi_dma set to 1 for DMA access, 0 for PIO (default is PIO). In src/sys/dev/ata/ata-all.c, this sysctl is by default set to 1 (on -CURRENT, and also on 5.3-RELEASE). Perhaps this patch is in order? --- share/man/man4/ata.4.orig Thu Dec 9 19:07:53 2004 +++ share/man/man4/ata.4 Thu Dec 9 19:08:08 2004 @@ -86,7 +86,7 @@ .It Va hw.ata.ata_dma set to 1 for DMA access, 0 for PIO (default is DMA). .It Va hw.ata.atapi_dma -set to 1 for DMA access, 0 for PIO (default is PIO). +set to 1 for DMA access, 0 for PIO (default is DMA). .It Va hw.ata.wc set to 1 to enable Write Caching, 0 to disable (default is enabled). .Em WARNING : -- Craig Rodrigues rodrigc@crodrigues.org From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 00:54:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1BEC816A4CE for ; Fri, 10 Dec 2004 00:54:37 +0000 (GMT) Received: from hq.sectorb.msk.ru (petaflop.b.gz.ru [217.67.124.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5EE2643D31 for ; Fri, 10 Dec 2004 00:54:35 +0000 (GMT) (envelope-from chinhngt@sectorb.msk.ru) Received: from unix.local (unix.local [172.16.12.120]) by hq.sectorb.msk.ru (Postfix) with ESMTP id 101F0408A; Fri, 10 Dec 2004 03:54:33 +0300 (MSK) Date: Fri, 10 Dec 2004 03:54:32 +0300 (MSK) From: Nguyen Tam Chinh X-X-Sender: chinhngt@unix.local To: Poul-Henning Kamp In-Reply-To: <20041209024624.E95734@unix.local> Message-ID: <20041210034850.C2440@unix.local> References: <28335.1102548763@critter.freebsd.dk> <20041209024624.E95734@unix.local> Keywords: 216091683 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: current@freebsd.org Subject: Re: [fsck -B problem] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 00:54:37 -0000 On Thu, 9 Dec 2004, Nguyen Tam Chinh wrote: > On Thu, 9 Dec 2004, Poul-Henning Kamp wrote: > >> In message <20041209022545.G96955@unix.local>, Nguyen Tam Chinh writes: >>> Hi all, >>> The system is 6.0-CURRENT (cvsup 09/12), >>> ------------- >>> unix# fsck -B >>> Can't stat /home/.snap/fsck_snapshot: No such file or directory >>> Can't stat /root/.snap/fsck_snapshot: No such file or directory >>> Can't stat /tmp/.snap/fsck_snapshot: No such file or directory >>> Can't stat /usr/.snap/fsck_snapshot: No such file or directory >>> Can't stat /var/.snap/fsck_snapshot: No such file or directory >>> ------------ >>> What could be the problem here? >>> what is fsck_snapshot using for? >> >> I belive I fixed this earlier today. >> > > OK. I'm cvsuping again (already get your commit). The build process will take > some hours. Hmm, I think the problem is still there, or maybe I misunderstanding something ... See the result: ------------------------------------------- unix# dmesg | grep WARN WARNING: /root was not properly dismounted WARNING: attempt to net_add_domain(netgraph) after domainfinalize() unix# fsck -B ad0s1h Can't stat /root/.snap/fsck_snapshot: No such file or directory unix# uname -a FreeBSD unix.hackers 6.0-CURRENT FreeBSD 6.0-CURRENT #10: Fri Dec 10 02:42:45 MSK 2004 root@unix.hackers:/mnt/unix/Temp/obj/usr/src/sys/kernel i386 unix# ------------------------------------------- I must reboot in single user mode to manually run fsck other slides, but I left /root to verify the background fsck. ----- With best regards, | The Power to Serve Nguyen Tam Chinh | http://www.FreeBSD.org Loc: sp.cs.msu.ru | http://chinhngt.svmgu.com | http://www.gnu.org/copyleft/copyleft.html From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 00:54:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B021216A518 for ; Fri, 10 Dec 2004 00:54:46 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 9BFAF43D4C for ; Fri, 10 Dec 2004 00:54:45 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 7288 invoked by uid 65534); 10 Dec 2004 00:54:44 -0000 Received: from p3EE262B8.dip.t-dialin.net (EHLO lofi.dyndns.org) (62.226.98.184) by mail.gmx.net (mp027) with SMTP; 10 Dec 2004 01:54:44 +0100 X-Authenticated: #443188 Received: from kiste.my.domain (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iBA0sfgj042413 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 10 Dec 2004 01:54:42 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: freebsd-current@freebsd.org Date: Fri, 10 Dec 2004 01:54:38 +0100 User-Agent: KMail/1.7.1 References: <20041209231228.GD18003@squash.dsto.defence.gov.au> <20041209233318.GA21779@xor.obsecurity.org> In-Reply-To: <20041209233318.GA21779@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart7184508.Ag4G0aYZHN"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412100154.39722.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new cc: Kris Kennaway Subject: Re: does this mean my kernel is trashed ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 00:54:46 -0000 --nextPart7184508.Ag4G0aYZHN Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday, 10. December 2004 00:33, Kris Kennaway wrote: > On Fri, Dec 10, 2004 at 09:42:28AM +1030, Wilkinson, Alex wrote: > > # sudo indent /boot/kernel/kernel > > ^ > Um, no. Well, _now_ it probably is. =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart7184508.Ag4G0aYZHN Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBuPPPXhc68WspdLARAoO7AJ4zIa80sdf/raJ5LUMmIRIH0pI95QCff5V6 zitcc5KhRdBvx0J+UKhFBGc= =ULI+ -----END PGP SIGNATURE----- --nextPart7184508.Ag4G0aYZHN-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 01:17:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 071AB16A4CE for ; Fri, 10 Dec 2004 01:17:20 +0000 (GMT) Received: from avout1.midco.net (avout1.midco.net [24.220.0.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CE4C43D48 for ; Fri, 10 Dec 2004 01:17:19 +0000 (GMT) (envelope-from pmes@bis.midco.net) Received: (qmail 6789 invoked by uid 1009); 10 Dec 2004 01:17:18 -0000 Received: from pmes@bis.midco.net by avout1 by uid 1002 with qmail-scanner-1.22 (f-prot: 4.4.2/3.14.11. Clear:RC:1(24.220.217.4):. Processed in 0.012379 secs); 10 Dec 2004 01:17:18 -0000 X-Qmail-Scanner-Mail-From: pmes@bis.midco.net via avout1 X-Qmail-Scanner: 1.22 (Clear:RC:1(24.220.217.4):. Processed in 0.012379 secs) Received: from host-4-217-220-24.midco.net (HELO [10.0.0.3]) ([24.220.217.4]) (envelope-sender ) by avout1.midco.net (qmail-ldap-1.03) with SMTP for ; 10 Dec 2004 01:17:18 -0000 Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: <3B4A0670-4A49-11D9-AEA4-000D936BE398@bis.midco.net> Content-Type: text/plain; charset=US-ASCII; format=flowed To: current@freebsd.org From: Peter Schultz Date: Thu, 9 Dec 2004 19:17:17 -0600 X-Mailer: Apple Mail (2.619) Subject: LOR setting up wireless bridge X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 01:17:20 -0000 1st 0xc06a5aa0 ifnet (ifnet) @ /home/admin/files/code/src/sys/modules/bridge/.. /../net/bridge.c:423 2nd 0xc10a5c7c radix node head (radix node head) @ /home/admin/files/code/src/s ys/net/route.c:148 KDB: stack backtrace: http://bis.midco.net/pmes/bridge_lor.txt This occurs after setting: sysctl net.link.ether.bridge.config="wi0,fxp1" Please let me know if you need more info. Pete... P.S. Does ethercons work with 6-CURRENT? From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 02:31:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E9DE116A4CE for ; Fri, 10 Dec 2004 02:31:25 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C49CA43D46 for ; Fri, 10 Dec 2004 02:31:22 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iBA2V76X030182; Fri, 10 Dec 2004 13:01:08 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Fri, 10 Dec 2004 13:00:51 +1030 User-Agent: KMail/1.7.1 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1147218.RbaanzER34"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412101301.06484.doconnor@gsoft.com.au> X-Spam-Score: -3 () MIME_LONG_LINE_QP,PGP_SIGNATURE_2,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: sam@errno.com Subject: Recent ifconfig changes choke on fwip X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 02:31:26 -0000 --nextPart1147218.RbaanzER34 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline [inchoate 12:55] /usr/src/sbin/ifconfig >gdb /usr/obj/usr/src/sbin/ifconfig= /ifconfig 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"... (gdb) run Starting program: /usr/obj/usr/src/sbin/ifconfig/ifconfig bfe0: flags=3D8843 mtu 1500 options=3D8 inet 203.31.81.38 netmask 0xffffffc0 broadcast 203.31.81.63 ether 00:0d:56:b3:99:6e media: Ethernet autoselect (100baseTX ) status: active fwip0: flags=3D108802 mtu 1500 lladdr 43.4f.c0.0.8.17.a4.38.a.2.ff.fe.0.0.0.0 Program received signal SIGSEGV, Segmentation fault. 0x0804b2f9 in in_status (s=3D7, info=3D0x8058134) at /usr/src/sbin/ifconfig= /af_inet.c:69 69 printf("\tinet %s ", inet_ntoa(sin->sin_addr)); (gdb) print sin->sin_addr Error accessing memory address 0x102: Bad address. (gdb) bt #0 0x0804b2f9 in in_status (s=3D7, info=3D0x8058134) at /usr/src/sbin/ifco= nfig/af_inet.c:69 fwip is the IP over Firewire interface. I tried to do some tracing in GDB the line numbers don't seem to match up=20 properly :-/ =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1147218.RbaanzER34 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBuQpq5ZPcIHs/zowRAj0MAJ94zZn269sukPITQrCZkln87MTP2wCfTRx5 JXto9uAtw2QhYz2Ep+1lQNI= =LyKn -----END PGP SIGNATURE----- --nextPart1147218.RbaanzER34-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 02:48:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8AA6B16A4CE for ; Fri, 10 Dec 2004 02:48:30 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B11A43D46 for ; Fri, 10 Dec 2004 02:48:29 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iBA2mGdv030339; Fri, 10 Dec 2004 13:18:16 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Fri, 10 Dec 2004 13:18:14 +1030 User-Agent: KMail/1.7.1 References: <200412101301.06484.doconnor@gsoft.com.au> In-Reply-To: <200412101301.06484.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2456800.3VtqN1daq8"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412101318.15278.doconnor@gsoft.com.au> X-Spam-Score: -4.3 () IN_REP_TO,MIME_LONG_LINE_QP,PGP_SIGNATURE_2,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: sam@errno.com Subject: Re: Recent ifconfig changes choke on fwip X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 02:48:30 -0000 --nextPart2456800.3VtqN1daq8 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Fri, 10 Dec 2004 13:00, Daniel O'Connor wrote: > I tried to do some tracing in GDB the line numbers don't seem to match up > properly :-/ Ahh, building without -O2 helps.. (gdb) bt #0 0x0804b57a in in_status (s=3D7, info=3D0x805a134) at /usr/src/sbin/ifco= nfig/af_inet.c:69 #1 0x0804a046 in af_all_status (s=3D7, sdl=3D0x805a134) at /usr/src/sbin/i= fconfig/ifconfig.c:405 #2 0x0804af39 in status (afp=3D0x80563c0, addrcount=3D0, sdl=3D0x805a134, = ifm=3D0x805a0d4, ifam=3D0x0) at /usr/src/sbin/ifconfig/ifconfig.c:850 #3 0x08049e05 in main (argc=3D0, argv=3D0xbfbfe914) at /usr/src/sbin/ifcon= fig/ifconfig.c:349 (gdb) list af_inet.c:69 64 65 sin =3D (struct sockaddr_in *)info->rti_info[RTAX_IFA]; 66 if (sin =3D=3D NULL) 67 return; 68 69 printf("\tinet %s ", inet_ntoa(sin->sin_addr)); 70 71 if (flags & IFF_POINTOPOINT) { 72 /* note RTAX_BRD overlap with IFF_BROADCAST */ 73 sin =3D (struct sockaddr_in *)info->rti_info[RTAX_B= RD]; (gdb) print sin $3 =3D (struct sockaddr_in *) 0xfe (gdb) print info->rti_info $4 =3D {0x100590, 0x70697766, 0xc04f4330, 0xa4170800, 0xff020a38, 0xfe, 0x0= , 0x0} =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart2456800.3VtqN1daq8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBuQ5v5ZPcIHs/zowRAl+HAJ42NKKNytc7EmZIyp37HH2Y2QbIRACgjmOh a2ejnGwt1VrEs2xfJR8ThGw= =dd5c -----END PGP SIGNATURE----- --nextPart2456800.3VtqN1daq8-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 03:00:23 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4464316A4CF; Fri, 10 Dec 2004 03:00:23 +0000 (GMT) Received: from juniper.fornext.org (53.35.138.210.xn.2iij.net [210.138.35.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5033443D41; Fri, 10 Dec 2004 03:00:22 +0000 (GMT) (envelope-from shino@fornext.org) Received: from [127.0.0.1] (ariel.net.ss.titech.ac.jp [131.112.21.25]) by juniper.fornext.org (Postfix) with ESMTP id E99A42A; Fri, 10 Dec 2004 12:00:20 +0900 (JST) Date: Fri, 10 Dec 2004 12:00:21 +0900 From: Shunsuke SHINOMIYA To: Jeremie Le Hen Message-Id: <20041210113318.BBF3.SHINO@fornext.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------_41B90AE6BC9B03DC2588_MULTIPART_MIXED_" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.12.01 [ja] cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: if_em int_throttle_ceil patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 03:00:23 -0000 --------_41B90AE6BC9B03DC2588_MULTIPART_MIXED_ Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Hi, Jeremie and Lists. The previous patch to change if_em's int_throttle_ceil into sysctl-able cause a kernel panic. If you set em's int_throttle_ceil=0 and then reconfigure the em, it cause a diveded by zero panic. This patch for original if_em.[ch] which is attached to this mail is corrected this problem. -- Shunsuke SHINOMIYA --------_41B90AE6BC9B03DC2588_MULTIPART_MIXED_ Content-Type: application/octet-stream; name="if_em.diff" Content-Disposition: attachment; filename="if_em.diff" Content-Transfer-Encoding: base64 LS0tIGlmX2VtLmMtMS40NC4yLjMub3JpZwlUdWUgTm92ICA5IDA1OjA2OjE0IDIwMDQKKysrIGlm X2VtLmMJRnJpIERlYyAxMCAxMToyMjowNSAyMDA0CkBAIC0zMiw2ICszMiw3IEBACiAqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKiovCiAKIC8qJEZyZWVCU0Q6IHNyYy9zeXMvZGV2L2VtL2lmX2VtLmMsdiAxLjQ0 LjIuMyAyMDA0LzExLzA4IDIwOjA2OjE0IHNjb3R0bCBFeHAgJCovCiAKICNpbmNsdWRlIDxkZXYv ZW0vaWZfZW0uaD4KIApAQCAtMTgyLDYgKzE4Myw5IEBACiBzdGF0aWMgdm9pZCBlbV9hZGRfaW50 X2RlbGF5X3N5c2N0bChzdHJ1Y3QgYWRhcHRlciAqLCBjb25zdCBjaGFyICosCiAJCQkJICAgIGNv bnN0IGNoYXIgKiwgc3RydWN0IGVtX2ludF9kZWxheV9pbmZvICosCiAJCQkJICAgIGludCwgaW50 KTsKKyNpZmRlZiAxCitzdGF0aWMgaW50IGVtX3N5c2N0bF90aHJvdHRsZV9jZWlsKFNZU0NUTF9I QU5ETEVSX0FSR1MpOworI2VuZGlmCiAKIC8qKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioKICAqICBGcmVlQlNEIERldmlj ZSBJbnRlcmZhY2UgRW50cnkgUG9pbnRzICAgICAgICAgICAgICAgICAgICAKQEAgLTIwNSw2ICsy MDksMTMgQEAKIE1PRFVMRV9ERVBFTkQoZW0sIHBjaSwgMSwgMSwgMSk7CiBNT0RVTEVfREVQRU5E KGVtLCBldGhlciwgMSwgMSwgMSk7CiAKKyNpZmRlZiAxCisvKiBTZXQgdGhlIGludGVycnVwdCB0 aHJvdHRsaW5nIHJhdGUuICBWYWx1ZSBpcyBjYWxjdWxhdGVkCisgKiBhcyBJVFIgPSAxLyhJTlRT X1BFUl9TRUMgKiAyNTZucykgKi8KKyNkZWZpbmUgSVRSX1ZBTFVFKGlwcykJCSgoaXBzKSA+IDAg PyAxMDAwMDAwMDAwIC8gKChpcHMpICogMjU2KSA6IDApCisjZGVmaW5lIE1BWF9JTlRTX1BFUl9T RUMgICAgICAgIDgwMDAKKyNlbmRpZgorCiAvKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqCiAgKiAgVHVuYWJsZSBkZWZh dWx0IHZhbHVlcy4KICAqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKiovCkBAIC0zNTgsNiArMzY5LDEzIEBACiAJCSAgICAm YWRhcHRlci0+dHhfYWJzX2ludF9kZWxheSwKIAkJICAgIEUxMDAwX1JFR19PRkZTRVQoJmFkYXB0 ZXItPmh3LCBUQURWKSwKIAkJICAgIGVtX3R4X2Fic19pbnRfZGVsYXlfZGZsdCk7CisjaWZkZWYg MQorCQlTWVNDVExfQUREX1BST0MoJmFkYXB0ZXItPnN5c2N0bF9jdHgsCisJCSAgICBTWVNDVExf Q0hJTERSRU4oYWRhcHRlci0+c3lzY3RsX3RyZWUpLCBPSURfQVVUTywKKwkJICAgICJpbnRfdGhy b3R0bGVfY2VpbCIsIENUTFRZUEVfSU5UfENUTEZMQUdfUlcsCisJCSAgICBhZGFwdGVyLCAwLCBl bV9zeXNjdGxfdGhyb3R0bGVfY2VpbCwgIklVIiwKKwkJICAgICJpbnRlcnJ1cHQgdGhyb3R0bGlu ZyByYXRlIik7CisjZW5kaWYKIAl9CiAgICAgICAKIAkvKiBQYXJhbWV0ZXJzICh0byBiZSByZWFk IGZyb20gdXNlcikgKi8gICAKQEAgLTQwMyw2ICs0MjEsOSBAQAogCSAqLwogCWFkYXB0ZXItPmh3 LnJlcG9ydF90eF9lYXJseSA9IDE7CiAKKyNpZmRlZiAxCisJYWRhcHRlci0+dGhyb3R0bGVfY2Vp bCA9IE1BWF9JTlRTX1BFUl9TRUM7CisjZW5kaWYKIAogCWlmIChlbV9hbGxvY2F0ZV9wY2lfcmVz b3VyY2VzKGFkYXB0ZXIpKSB7CiAJCXByaW50ZigiZW0lZDogQWxsb2NhdGlvbiBvZiBQQ0kgcmVz b3VyY2VzIGZhaWxlZFxuIiwgCkBAIC0yNjA5LDExICsyNjMwLDE2IEBACiAJCUUxMDAwX1dSSVRF X1JFRygmYWRhcHRlci0+aHcsIFJBRFYsCiAJCSAgICBhZGFwdGVyLT5yeF9hYnNfaW50X2RlbGF5 LnZhbHVlKTsKIAorI2lmZGVmIDEKKyAgICAgICAgICAgICAgICBFMTAwMF9XUklURV9SRUcoJmFk YXB0ZXItPmh3LCBJVFIsCisJCSAgICBJVFJfVkFMVUUoYWRhcHRlci0+dGhyb3R0bGVfY2VpbCkp OworI2Vsc2UKICAgICAgICAgICAgICAgICAvKiBTZXQgdGhlIGludGVycnVwdCB0aHJvdHRsaW5n IHJhdGUuICBWYWx1ZSBpcyBjYWxjdWxhdGVkCiAgICAgICAgICAgICAgICAgICogYXMgREVGQVVM VF9JVFIgPSAxLyhNQVhfSU5UU19QRVJfU0VDICogMjU2bnMpICovCiAjZGVmaW5lIE1BWF9JTlRT X1BFUl9TRUMgICAgICAgIDgwMDAKICNkZWZpbmUgREVGQVVMVF9JVFIgICAgICAgICAgICAgMTAw MDAwMDAwMC8oTUFYX0lOVFNfUEVSX1NFQyAqIDI1NikKICAgICAgICAgICAgICAgICBFMTAwMF9X UklURV9SRUcoJmFkYXB0ZXItPmh3LCBJVFIsIERFRkFVTFRfSVRSKTsKKyNlbmRpZgogICAgICAg ICB9ICAgICAgIAogCiAJLyogU2V0dXAgdGhlIEJhc2UgYW5kIExlbmd0aCBvZiB0aGUgUnggRGVz Y3JpcHRvciBSaW5nICovCkBAIC0zMzgzLDQgKzM0MDksMjggQEAKIAkgICAgU1lTQ1RMX0NISUxE UkVOKGFkYXB0ZXItPnN5c2N0bF90cmVlKSwKIAkgICAgT0lEX0FVVE8sIG5hbWUsIENUTFRZUEVf SU5UfENUTEZMQUdfUlcsCiAJICAgIGluZm8sIDAsIGVtX3N5c2N0bF9pbnRfZGVsYXksICJJIiwg ZGVzY3JpcHRpb24pOworfQorCitzdGF0aWMgaW50CitlbV9zeXNjdGxfdGhyb3R0bGVfY2VpbChT WVNDVExfSEFORExFUl9BUkdTKQoreworCXN0cnVjdCBhZGFwdGVyICphZGFwdGVyOworCWludCBl cnJvcjsKKwl1X2ludDMyX3QgY2VpbDsKKwlpbnQgczsKKworCWFkYXB0ZXIgPSAoc3RydWN0IGFk YXB0ZXIgKilhcmcxOworCWNlaWwgPSAgYWRhcHRlci0+dGhyb3R0bGVfY2VpbDsKKwllcnJvciA9 IHN5c2N0bF9oYW5kbGVfaW50KG9pZHAsICZjZWlsLCAwLCByZXEpOworCWlmIChlcnJvciAhPSAw IHx8IHJlcS0+bmV3cHRyID09IE5VTEwpCisJCXJldHVybiBlcnJvcjsKKwlhZGFwdGVyLT50aHJv dHRsZV9jZWlsID0gY2VpbDsKKwkKKwlzID0gc3BsaW1wKCk7CisKKwlFMTAwMF9XUklURV9SRUco JmFkYXB0ZXItPmh3LCBJVFIsIElUUl9WQUxVRShjZWlsKSk7CisKKwlzcGx4KHMpOworCisJcmV0 dXJuIDA7CiB9Ci0tLSBpZl9lbS5oLTEuMjUuMi4xLm9yaWcJRnJpIE5vdiAxOSAxOTowMDowMyAy MDA0CisrKyBpZl9lbS5oCU1vbiBOb3YgMjIgMTM6Mjk6NTggMjAwNApAQCAtMzUzLDYgKzM1Myw5 IEBACiAJdV9pbnQxNl90ICAgICAgIGxpbmtfc3BlZWQ7CiAJdV9pbnQxNl90ICAgICAgIGxpbmtf ZHVwbGV4OwogCXVfaW50MzJfdCAgICAgICBzbWFydHNwZWVkOworI2lmZGVmIDEKKwl1X2ludDMy X3QJdGhyb3R0bGVfY2VpbDsKKyNlbmRpZgogCXN0cnVjdCBlbV9pbnRfZGVsYXlfaW5mbyB0eF9p bnRfZGVsYXk7CiAJc3RydWN0IGVtX2ludF9kZWxheV9pbmZvIHR4X2Fic19pbnRfZGVsYXk7CiAJ c3RydWN0IGVtX2ludF9kZWxheV9pbmZvIHJ4X2ludF9kZWxheTsK --------_41B90AE6BC9B03DC2588_MULTIPART_MIXED_-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 04:41:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1748B16A50F for ; Fri, 10 Dec 2004 04:41:38 +0000 (GMT) Received: from mailserv1.neuroflux.com (mailserv1.neuroflux.com [204.228.228.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id A957E43D5A for ; Fri, 10 Dec 2004 04:41:37 +0000 (GMT) (envelope-from ryans@gamersimpact.com) Received: (qmail 85027 invoked by uid 89); 10 Dec 2004 04:40:43 -0000 Received: from unknown (HELO www2.neuroflux.com) (127.0.0.1) by localhost with SMTP; 10 Dec 2004 04:40:43 -0000 Received: from 63.231.165.87 (SquirrelMail authenticated user ryans@gamersimpact.com); by www2.neuroflux.com with HTTP; Thu, 9 Dec 2004 21:40:43 -0700 (MST) Message-ID: <54799.63.231.165.87.1102653643.squirrel@63.231.165.87> Date: Thu, 9 Dec 2004 21:40:43 -0700 (MST) From: "Ryan Sommers" To: current@freebsd.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: dc(4) oddity X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 04:41:38 -0000 Since about two days ago a box had been spewing: dc0: watchdog timeout every 10-15 seconds. Network connectivity was nonexistant. I tried down/uping the device, reboots, network plug, anything I could think of. Nothing helped. And this box has been running since FreeBSD 6.0-CURRENT #6: Tue Sep 28 16:48:13 CDT 2004 without problems. Not constantly, it goes up in the morning and down at night. Switch lights were active the during the whole 'scrolling timeout' period. I was about ready to call it a bad network card when all of a sudden I switched the KVM back over to it and I see dc0: failed to force tx and rx to idle state as the last message on the console. No scrolling watchdog timeouts. Interesting I thought. I down'ed the interface and brought it back up and tried pinging the router. Success. So, after about 36 hours of watchdog timeouts it came back to life. Any idea what this might be? -- Ryan Sommers ryans@gamersimpact.com From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 05:23:45 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47D5F16A4CE for ; Fri, 10 Dec 2004 05:23:45 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1543343D58 for ; Fri, 10 Dec 2004 05:23:44 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iBA5NVrQ032770; Fri, 10 Dec 2004 15:53:31 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Fri, 10 Dec 2004 15:53:21 +1030 User-Agent: KMail/1.7.1 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart11031657.SRQEMWpjGH"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412101553.29518.doconnor@gsoft.com.au> X-Spam-Score: -3.3 () PGP_SIGNATURE_2,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: sam@errno.com Subject: Can't see BSS ID on if_ndis X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 05:23:45 -0000 --nextPart11031657.SRQEMWpjGH Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, 1.73 of if_ndis.c works which is the good news :) However I don't see which BSSID I'm associated with using wicontrol -L.. [inchoate 15:50] ~ >sudo wicontrol -i ndis0 -L =2E.. TX encryption key: [ 0 ] Encryption keys: [ ][ ][ ][ ] Available APs: 1 station: SSID BSSID Chan SN S N Intrvl Capinfo citilan [ 00:00:00:00:00:00 ] [ 4 ] [ 0 0 0 ] 0 [ 11b 5b 2b 1b 5.5b ] Neither does ifconfig.. [inchoate 15:51] ~ >ifconfig -v ndis0 list scan SSID BSSID CHAN RATE S:N INT CAPS citilan 00:00:00:00:00:00 4 11M 0:0 0 Howver, using wicontrol -l shows it.. [inchoate 15:50] ~ >sudo wicontrol -i ndis0 -l 1 station: ap[0]: netname (SSID): [ citilan ] BSSID: [ 00:40:96:40:47:80 ] Channel: [ 4 ] Quality/Signal/Noise [signal]: [ 72 / 72 / 0 ] [dBm]: [ 72 / -77 / -149 ] BSS Beacon Interval [msec]: [ 0 ] Capinfo: [ ] DataRate [Mbps]: [ 11 ] Also, when you run ifconfig after setting an SSID it doesn't actually displ= ay=20 it unless you're associated (not sure if that's a bug). =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart11031657.SRQEMWpjGH Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBuTLR5ZPcIHs/zowRAmBeAKCfWiufFz74IBN9W2XVJknafo8ZiACcD0E8 mrzUSdb3loHtBIByeNCAaEY= =4efU -----END PGP SIGNATURE----- --nextPart11031657.SRQEMWpjGH-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 05:45:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 608AC16A4CE for ; Fri, 10 Dec 2004 05:45:20 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA36C43D48 for ; Fri, 10 Dec 2004 05:45:19 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) iBA5jGQ5019803; Fri, 10 Dec 2004 00:45:16 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)iBA5jDdP019800; Fri, 10 Dec 2004 00:45:16 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Fri, 10 Dec 2004 00:45:13 -0500 (EST) From: Andre Guibert de Bruet To: Poul-Henning Kamp In-Reply-To: <23033.1102506923@critter.freebsd.dk> Message-ID: <20041210004250.I637@alpha.siliconlandmark.com> References: <23033.1102506923@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: freebsd-current@freebsd.org Subject: Re: dump broken with new kernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 05:45:20 -0000 On Wed, 8 Dec 2004, Poul-Henning Kamp wrote: > In message <20041207234332.Q637@alpha.siliconlandmark.com>, Andre Guibert de Br > uet writes: > >> I am still running into dump problems on my system. I'm using: >> $FreeBSD: src/sys/kern/vfs_mount.c,v 1.168 2004/12/07 08:15:40 phk Exp $ >> $FreeBSD: src/sys/sys/mount.h,v 1.187 2004/12/07 08:15:40 phk Exp $ >> >> FreeBSD bling.home 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Tue Dec 7 23:02:43 >> EST 2004 root@bling.home:/usr/CURRENT/sys/i386/compile/BLING i386 >> >> # /sbin/dump -0uaLf "/mnt/backups/`hostname -s`-`utime`-amrd0a.dump" /mnt/amrd0a >> mksnap_ffs: Cannot create /mnt/amrd0a/.snap/dump_snapshot: Bad address >> dump: Cannot create /mnt/amrd0a/.snap/dump_snapshot: No such file or directory > > Ok, should work now. It appears to have fixed it. I'm now debugging the amr(4) driver as it hangs with a "bad slot 0 completed" message. From the source, that number could be any positive integer, but i've never seen it hang with anything other than 0 (I've reproduced the problem about 10 times already). It's fun stuff... :-) Thanks, Andy | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ > From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 05:56:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA35C16A4CE for ; Fri, 10 Dec 2004 05:56:36 +0000 (GMT) Received: from alpha.siliconlandmark.com (alpha.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 685AF43D31 for ; Fri, 10 Dec 2004 05:56:36 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from alpha.siliconlandmark.com (andy@localhost [127.0.0.1]) iBA5uYMZ019908; Fri, 10 Dec 2004 00:56:34 -0500 (EST) (envelope-from andy@siliconlandmark.com) Received: from localhost (andy@localhost)iBA5uXJN019905; Fri, 10 Dec 2004 00:56:34 -0500 (EST) (envelope-from andy@siliconlandmark.com) X-Authentication-Warning: alpha.siliconlandmark.com: andy owned process doing -bs Date: Fri, 10 Dec 2004 00:56:33 -0500 (EST) From: Andre Guibert de Bruet To: Michael Nottebrock In-Reply-To: <200412100154.39722.michaelnottebrock@gmx.net> Message-ID: <20041210005538.O637@alpha.siliconlandmark.com> References: <20041209231228.GD18003@squash.dsto.defence.gov.au> <200412100154.39722.michaelnottebrock@gmx.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean cc: freebsd-current@freebsd.org Subject: Re: does this mean my kernel is trashed ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 05:56:36 -0000 On Fri, 10 Dec 2004, Michael Nottebrock wrote: > On Friday, 10. December 2004 00:33, Kris Kennaway wrote: >> On Fri, Dec 10, 2004 at 09:42:28AM +1030, Wilkinson, Alex wrote: >>> # sudo indent /boot/kernel/kernel >> ^ >> Um, no. > > Well, _now_ it probably is. FYI, from the manpage: NOTE: If you only specify an input-file, the formatting is done `in- place', that is, the formatted file is written back into input-file and a backup copy of input-file is written in the current directory. If input-file is named `/blah/blah/file', the backup file is named file.BAK. Regards, Andy | Andre Guibert de Bruet | Enterprise Software Consultant > | Silicon Landmark, LLC. | http://siliconlandmark.com/ > From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 06:42:29 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 46A3116A4CE for ; Fri, 10 Dec 2004 06:42:29 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAA4043D5C for ; Fri, 10 Dec 2004 06:42:28 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.90] ([66.127.85.90]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id iBA6gMWi034408 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Dec 2004 22:42:23 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <41B9454F.9080903@errno.com> Date: Thu, 09 Dec 2004 22:42:23 -0800 From: Sam Leffler Organization: Errno Consulting User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Hideyuki KURASHINA References: <200412081109.43840.sam@errno.com> <20041209.100008.21874313.rushani@bl.mmtr.or.jp> <200412081744.27539.sam@errno.com> <20041209.225041.63112571.rushani@bl.mmtr.or.jp> In-Reply-To: <20041209.225041.63112571.rushani@bl.mmtr.or.jp> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: WEP does not work? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 06:42:29 -0000 Hideyuki KURASHINA wrote: > Hi, > > >>>>On Wed, 8 Dec 2004 17:44:27 -0800, Sam Leffler said: > > >>On Wednesday 08 December 2004 05:00 pm, Hideyuki KURASHINA wrote: >> >>>After rebooting, I set IPv4 and IPv6 addresses and those routes. Because >>>access point supports only 802.11b, I configured my wireless network >>>by 128bit WEP as follows >>> >>> /sbin/ifconfig ath0 nwid MY-SSID nwkey 0x01234567890123456789012345 media >>>autoselect mode 11b >>> >>>then I got following error: >>> >>> ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) >>> ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) >>> ath0: ath_chan_set: unable to reset channel 8 (2447 Mhz) >>> ath0: ath_chan_set: unable to reset channel 12 (2467 Mhz) >> >>Weird, can you send me the regdomain and country code: e.g. the output of >>sysctl dev.ath.0. > > > Sure. > > # sysctl dev.ath.0 > dev.ath.0.%desc: Atheros 5212 > dev.ath.0.%driver: ath > dev.ath.0.%location: slot=2 function=0 > dev.ath.0.%pnpinfo: vendor=0x168c device=0x1014 subvendor=0x1014 subdevice=0x057e class=0x020000 > dev.ath.0.%parent: pci2 > dev.ath.0.countrycode: 395 > dev.ath.0.regdomain: 67 > dev.ath.0.debug: 0 > dev.ath.0.slottime: 20 > dev.ath.0.acktimeout: 48 > dev.ath.0.ctstimeout: 48 > dev.ath.0.softled: 1 > dev.ath.0.ledpin: 0 > dev.ath.0.txantenna: 0 > dev.ath.0.rxantenna: 1 > dev.ath.0.txintrperiod: 5 > dev.ath.0.diag: 0 > dev.ath.0.tpscale: 0 > dev.ath.0.rate_interval: 1000 > dev.ath.0.rate_raise: 10 > dev.ath.0.rate_raise_threshold: 10 > > Just curiosity, `hw' MIBs print both regdomain and countrycode are 0. hw.ath mib entries define values used to initialize each new ath device. You cannot set regdomain (yet) but countrycode can be overridden by setting hw.ath.countrycode before loading a device. > > # sysctl hw.ath > hw.ath.hal.swba_backoff: 0 > hw.ath.hal.sw_brt: 10 > hw.ath.hal.dma_brt: 2 > hw.ath.hal.version: 0.9.14.9 > hw.ath.debug: 0 > hw.ath.regdomain: 0 > hw.ath.countrycode: 0 > hw.ath.xchanmode: 1 > hw.ath.outdoor: 1 > hw.ath.calibrate: 30 > hw.ath.dwell: 200 > > >>> # ifconfig ath0 list chan >>> Channel 1 : 2412* Mhz 11g Channel 11 : 2462* Mhz 11g >>> Channel 2 : 2417* Mhz 11g Channel 12 : 2467* Mhz 11a 11g >>> Channel 3 : 2422* Mhz 11g Channel 13 : 2472* Mhz 11g >>> Channel 4 : 2427* Mhz 11g Channel 14 : 2484* Mhz 11b >>> Channel 5 : 2432* Mhz 11g Channel 16 : 5080* Mhz 11a >>> Channel 6 : 2437* Mhz 11g Channel 34 : 5170* Mhz 11a >>> Channel 7 : 2442* Mhz 11g Channel 38 : 5190* Mhz 11a >>> Channel 8 : 2447* Mhz 11a 11g Channel 42 : 5210* Mhz 11a >>> Channel 9 : 2452* Mhz 11g Channel 46 : 5230* Mhz 11a >>> Channel 10 : 2457* Mhz 11g >>> Note this says channels 8 and 12 are capable of 11a which is nonsense. Looks like a hal regdomain problem, probably related to the addition of turboG (turbo+11g). For now you'll need to lock the channel to your ap or filter out 8+12 using something like ifconfig ath0 chanlist 1-7,9,10,13-46 (13-46 is ok as unavailable channels should be silently ignored). >> >>So it seems channels 8 and 12 are supposedly available. > > > Actually, no. I'll show you my AP side wireless network setting. > > % dmesg | grep wi0 > wi0 at pcmcia0 function 0: PLANEX, GW-NS11H Wireless LAN PC Card, > wi0: 802.11 address 00:90:cc:XX:XX:XX > wi0: using RF:PRISM3 MAC:ISL3871(PCMCIA) > wi0: Intersil Firmware: Primary (1.0.7), Station (1.3.5) > wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > > % ifconfig wi0 > wi0: flags=8863 mtu 1500 > ssid MY-SSID nwkey ***** > powersave off > bssid 00:90:cc:XX:XX:XX chan 3 > address: 00:90:cc:XX:XX:XX > media: IEEE802.11 autoselect mode 11b hostap (DS2 hostap) > status: active > inet 192.168.1.7 netmask 0xffffff00 broadcast 192.168.1.255 > inet alias 192.168.1.254 netmask 0xffffffff broadcast 192.168.1.254 > inet6 fe80::290:XXXX:XXXX:XXXX%wi0 prefixlen 64 scopeid 0x4 > inet6 2001:3e0:XXX:X::X prefixlen 64 > > % sudo wiconfig wi0 > NIC serial number: [ 99SA01XXXXXX ] > Station name: [ ] > SSID for IBSS creation: [ MY-SSID ] > Current netname (SSID): [ MY-SSID ] > Desired netname (SSID): [ MY-SSID ] > Current BSSID: [ 00:90:cc:XX:XX:XX ] > Channel list: [ 1 2 3 4 5 6 7 8 9 10 11 12 13 14 ] > IBSS channel: [ 3 ] > Current channel: [ 3 ] > Comms quality/signal/noise: [ 0 81 27 ] > Promiscuous mode: [ Off ] > Port type: [ 6 ] > MAC address: [ 00:90:cc:XX:XX:XX ] > TX rate (selection): [ 0 ] > TX rate (actual speed): [ 2 ] > Beacon Interval (current) [msec]: [ 100 ] > Maximum data length: [ 2304 ] > RTS/CTS handshake threshold: [ 2347 ] > fragmentation threshold: [ 2346 ] > RSSI -> dBm adjustment: [ 100 ] > Create IBSS: [ Off ] > Microwave oven robustness: [ 0 ] > Roaming mode(1:firm,3:disable): [ 1 ] > Access point density: [ 1 ] > Power Mgmt (1=on, 0=off): [ 0 ] > Max sleep time (msec): [ 100 ] > Vendor info: [ Unknown ID: 31 version: 1.3 ] > WEP encryption: [ On ] > Authentication type > (1=OpenSys, 2=Shared Key): [ 1 ] > TX encryption key: [ 1 ] > Encryption keys: [ 0x01234567890123456789012345 ][ ][ ][ ] > > >>>It seems that ath0 failed to reset channel. I manually specified channel, >>>then ifconfig shows: >>> >>> # ifconfig -v ath0 >>> ath0: flags=8843 mtu 1500 >>> inet 192.168.1.11 netmask 0xffffff00 broadcast 192.168.1.255 >>> inet6 fe80::20e:XXXX:XXXX:XXXX%ath0 prefixlen 64 scopeid 0x2 >>> inet6 2001:3e0:XX:X::XX prefixlen 64 >>> ether 00:0e:9b:XX:XX:XX >>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11b (DS/11Mbps) >>> status: associated >>> ssid MY-SSID channel 3 (2422) bssid 00:90:cc:XX:XX:XX >>> authmode OPEN privacy ON deftxkey 1 powersavemode OFF >>> powersavesleep 100 txpowmax 14 txpower 60 rtsthreshold 2312 protmode CTS >>> wme roaming AUTO bintval 100 >>> AC_BE cwmin 5 cwmax 10 aifs 3 txopLimit 0 -acm ack >>> cwmin 5 cwmax 10 aifs 3 txopLimit 0 -acm >>> AC_BK cwmin 5 cwmax 10 aifs 7 txopLimit 0 -acm ack >>> cwmin 5 cwmax 10 aifs 7 txopLimit 0 -acm >>> AC_VI cwmin 4 cwmax 5 aifs 2 txopLimit 188 -acm ack >>> cwmin 4 cwmax 5 aifs 2 txopLimit 188 -acm >>> AC_VO cwmin 3 cwmax 4 aifs 2 txopLimit 102 -acm ack >>> cwmin 3 cwmax 4 aifs 2 txopLimit 102 -acm >> >>This doesn't show a key installed. I don't typically use nwkey; I'll have to >>check it. > > > I tried > > # /sbin/ifconfig ath0 ssid MY-SSID wepmode on weptxkey 1 wepkey 1:0x01234567890123456789012345 wepkey 2:- wepkey 3:- wepkey 4:- media autoselect mode 11b > > but nothing changed (default router is still not reachable). > I'll try to look tomorrow. I have a patch for fixing wep with ndis that I need to review and this is probably the same thing. Sam From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 07:05:17 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6893416A4CE; Fri, 10 Dec 2004 07:05:17 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0511E43D1D; Fri, 10 Dec 2004 07:05:17 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id iBA75GhE049564; Fri, 10 Dec 2004 02:05:16 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.1/8.13.1) with ESMTP id iBA75GqM090080; Fri, 10 Dec 2004 02:05:16 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id CB7897306E; Fri, 10 Dec 2004 02:05:15 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041210070515.CB7897306E@freebsd-current.sentex.ca> Date: Fri, 10 Dec 2004 02:05:15 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/624/Thu Dec 9 14:01:06 2004 clamav-milter version 0.80j on clamscanner2 X-Virus-Status: Clean Subject: [current tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 07:05:17 -0000 TB --- 2004-12-10 04:47:03 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-12-10 04:47:03 - starting CURRENT tinderbox run for i386/i386 TB --- 2004-12-10 04:47:03 - checking out the source tree TB --- 2004-12-10 04:47:03 - cd /home/tinderbox/CURRENT/i386/i386 TB --- 2004-12-10 04:47:03 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-12-10 04:53:25 - building world (CFLAGS=-O2 -pipe) TB --- 2004-12-10 04:53:25 - cd /home/tinderbox/CURRENT/i386/i386/src TB --- 2004-12-10 04:53:25 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-12-10 06:20:26 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-12-10 06:20:26 - cd /home/tinderbox/CURRENT/i386/i386/src TB --- 2004-12-10 06:20:26 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Dec 10 06:20:27 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Fri Dec 10 06:47:13 UTC 2004 TB --- 2004-12-10 06:47:13 - generating LINT kernel config TB --- 2004-12-10 06:47:13 - cd /home/tinderbox/CURRENT/i386/i386/src/sys/i386/conf TB --- 2004-12-10 06:47:13 - /usr/bin/make -B LINT TB --- 2004-12-10 06:47:14 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-12-10 06:47:14 - cd /home/tinderbox/CURRENT/i386/i386/src TB --- 2004-12-10 06:47:14 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Dec 10 06:47:16 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -O2 -pipe -I/sys/contrib/dev/acpica -D_KERNEL -DKLD_MODULE -nostdinc -I- -I/sys/contrib/dev/acpica -include /tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -I/tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/LINT -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c: In function `acpi_ibm_attach': /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c:155: error: `_COMPONENT' undeclared (first use in this function) /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c:155: error: (Each undeclared identifier is reported only once /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c:155: error: for each function it appears in.) /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c:155: error: `_THIS_MODULE' undeclared (first use in this function) /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c: In function `acpi_ibm_detach': /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c:260: error: `_Dbg' undeclared (first use in this function) *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src/sys/modules. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/LINT. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. TB --- 2004-12-10 07:05:15 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-12-10 07:05:15 - ERROR: failed to build lint kernel TB --- 2004-12-10 07:05:15 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 07:21:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D776B16A4CE for ; Fri, 10 Dec 2004 07:21:37 +0000 (GMT) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAA4543D41 for ; Fri, 10 Dec 2004 07:21:37 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) iBA7LZwN021620; Thu, 9 Dec 2004 23:21:36 -0800 (PST) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (h229.neville-neil.com [209.157.133.229] (may be forged)) by mail.meer.net (8.12.10/8.12.10/meer) with ESMTP id iBA7LY8r026773; Thu, 9 Dec 2004 23:21:34 -0800 (PST) (envelope-from gnn@neville-neil.com) Date: Thu, 09 Dec 2004 23:21:32 -0800 Message-ID: From: gnn@freebsd.org To: "Andrew R. Reiter" In-Reply-To: <20041209124839.V57958@fledge.watson.org> References: <20041209124839.V57958@fledge.watson.org> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.5 Emacs/21.2 (powerpc-apple-darwin) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: current@freebsd.org Subject: Re: rtentry recursion panic (fwd) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 07:21:37 -0000 At Thu, 9 Dec 2004 12:53:31 -0500 (EST), Andrew R. Reiter wrote: > > Sending since I know Sam and Bruce are busy; I am busy.. not as busy.. but > busy enough to not have time to track code paths down further than I did > in the below email. OK, I can repro this in a Virtual PC simulation as well. I'll look into it more tomorrow. Later, George From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 09:36:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E981016A4CE for ; Fri, 10 Dec 2004 09:36:26 +0000 (GMT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id DAC0243D31 for ; Fri, 10 Dec 2004 09:36:25 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 15224 invoked by uid 65534); 10 Dec 2004 09:36:24 -0000 Received: from pD955F9FD.dip.t-dialin.net (EHLO lofi.dyndns.org) (217.85.249.253) by mail.gmx.net (mp026) with SMTP; 10 Dec 2004 10:36:24 +0100 X-Authenticated: #443188 Received: from kiste.my.domain (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iBA9a9hS050789 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 10 Dec 2004 10:36:11 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: freebsd-current@freebsd.org Date: Fri, 10 Dec 2004 10:36:06 +0100 User-Agent: KMail/1.7.1 References: <200412081109.43840.sam@errno.com> <20041209.225041.63112571.rushani@bl.mmtr.or.jp> <41B9454F.9080903@errno.com> In-Reply-To: <41B9454F.9080903@errno.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart9673824.8mTDrTBG3F"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412101036.07460.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new cc: Sam Leffler Subject: Re: WEP does not work? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 09:36:27 -0000 --nextPart9673824.8mTDrTBG3F Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday, 10. December 2004 07:42, Sam Leffler wrote: > > Just curiosity, `hw' MIBs print both regdomain and countrycode are 0. > > hw.ath mib entries define values used to initialize each new ath device. > You cannot set regdomain (yet) but countrycode can be overridden by > setting hw.ath.countrycode before loading a device. This I've been wondering for a long time now - what countrycode represents= =20 what country? =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart9673824.8mTDrTBG3F Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBuW4HXhc68WspdLARAr4MAKCbK9V7LOJqSO/0PigVBGG+VhV+sQCfdDlL KGlTIX9MNVnKOuSbIwBLy8I= =7sa2 -----END PGP SIGNATURE----- --nextPart9673824.8mTDrTBG3F-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 09:50:34 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD8EF16A4CE for ; Fri, 10 Dec 2004 09:50:34 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0299643D58 for ; Fri, 10 Dec 2004 09:50:34 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by rproxy.gmail.com with SMTP id z35so407743rne for ; Fri, 10 Dec 2004 01:50:33 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=sqUrpEaYGwX0zRtlMXEAG/sBDb/VqKiT3+4wqkORNYWrMXKO/dRp/mRMaXSXmgHCAZgkkkGmg21p5ubmIMWcRZExCd3odfhEhz6S6+cZ9ogZYYDmMAuNZyA3I8Ki6Z3ydQS7SFXrr7ZsBPjJQNB2qOOhE1x8G5HA1GKdNMWklDU= Received: by 10.38.83.22 with SMTP id g22mr228618rnb; Fri, 10 Dec 2004 01:50:33 -0800 (PST) Received: by 10.38.209.11 with HTTP; Fri, 10 Dec 2004 01:50:33 -0800 (PST) Message-ID: <84dead7204121001507bb07f4f@mail.gmail.com> Date: Fri, 10 Dec 2004 15:20:33 +0530 From: Joseph Koshy To: alex.wilkinson@dsto.defence.gov.au In-Reply-To: <20041210005538.O637@alpha.siliconlandmark.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041209231228.GD18003@squash.dsto.defence.gov.au> <200412100154.39722.michaelnottebrock@gmx.net> <20041210005538.O637@alpha.siliconlandmark.com> cc: freebsd-current@freebsd.org Subject: Re: does this mean my kernel is trashed ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joseph Koshy List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 09:50:34 -0000 mn> Well, _now_ it probably is. Depending on whether you've done a "build/install kernel" step earlier, you might find a usable backup kernel in /boot/kernel.old/kernel. Good luck. From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 09:56:57 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A88416A4CE for ; Fri, 10 Dec 2004 09:56:57 +0000 (GMT) Received: from www.mmlab.cse.yzu.edu.tw (www.mmlab.cse.yzu.edu.tw [140.138.150.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id A2E1D43D54 for ; Fri, 10 Dec 2004 09:56:56 +0000 (GMT) (envelope-from avatar@mmlab.cse.yzu.edu.tw) Received: by www.mmlab.cse.yzu.edu.tw (qmail, from userid 1000) id F0F424EFD55; Fri, 10 Dec 2004 17:56:52 +0800 (CST) Received: from localhost (localhost [127.0.0.1]) by www.mmlab.cse.yzu.edu.tw (qmail) with ESMTP id ED9664EFD54; Fri, 10 Dec 2004 17:56:52 +0800 (CST) Date: Fri, 10 Dec 2004 17:56:52 +0800 (CST) From: Tai-hwa Liang To: Joseph Koshy In-Reply-To: <84dead7204121001507bb07f4f@mail.gmail.com> Message-ID: <0412101755508.81515@www.mmlab.cse.yzu.edu.tw> References: <20041209231228.GD18003@squash.dsto.defence.gov.au> <20041210005538.O637@alpha.siliconlandmark.com> <84dead7204121001507bb07f4f@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: freebsd-current@freebsd.org cc: alex.wilkinson@dsto.defence.gov.au Subject: Re: does this mean my kernel is trashed ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 09:56:57 -0000 I believe indent will leave a backup in the same directory. With .BAK extension or just a ~ appended to the original filename. On Fri, 10 Dec 2004, Joseph Koshy wrote: > mn> Well, _now_ it probably is. > > Depending on whether you've done a "build/install kernel" step > earlier, you might > find a usable backup kernel in /boot/kernel.old/kernel. > > Good luck. From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 10:14:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3C22216A4CE for ; Fri, 10 Dec 2004 10:14:07 +0000 (GMT) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id C724143D55 for ; Fri, 10 Dec 2004 10:14:06 +0000 (GMT) (envelope-from kstewart@owt.com) Received: from [207.41.94.233] (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id iBAACXdP015530; Fri, 10 Dec 2004 02:12:34 -0800 From: Kent Stewart To: freebsd-current@freebsd.org Date: Fri, 10 Dec 2004 02:13:40 -0800 User-Agent: KMail/1.7.1 References: <200412081109.43840.sam@errno.com> <41B9454F.9080903@errno.com> <200412101036.07460.michaelnottebrock@gmx.net> In-Reply-To: <200412101036.07460.michaelnottebrock@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412100213.40286.kstewart@owt.com> cc: Sam Leffler Subject: Re: WEP does not work? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 10:14:07 -0000 On Friday 10 December 2004 01:36 am, Michael Nottebrock wrote: > On Friday, 10. December 2004 07:42, Sam Leffler wrote: > > > Just curiosity, `hw' MIBs print both regdomain and countrycode > > > are 0. > > > > hw.ath mib entries define values used to initialize each new ath > > device. You cannot set regdomain (yet) but countrycode can be > > overridden by setting hw.ath.countrycode before loading a device. > > This I've been wondering for a long time now - what countrycode > represents what country? Are the following the ones you mean. See http://www.ics.uci.edu/WebSoft/wwwstat/country-codes.txt Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 10:20:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C0C216A4CE for ; Fri, 10 Dec 2004 10:20:47 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 9682643D48 for ; Fri, 10 Dec 2004 10:20:46 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 23563 invoked by uid 65534); 10 Dec 2004 10:20:45 -0000 Received: from pD955F9FD.dip.t-dialin.net (EHLO lofi.dyndns.org) (217.85.249.253) by mail.gmx.net (mp020) with SMTP; 10 Dec 2004 11:20:45 +0100 X-Authenticated: #443188 Received: from kiste.my.domain (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iBAAKehS051257 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 10 Dec 2004 11:20:42 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: Kent Stewart Date: Fri, 10 Dec 2004 11:20:37 +0100 User-Agent: KMail/1.7.1 References: <200412081109.43840.sam@errno.com> <200412101036.07460.michaelnottebrock@gmx.net> <200412100213.40286.kstewart@owt.com> In-Reply-To: <200412100213.40286.kstewart@owt.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart11140297.9AWg76zxlh"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412101120.38869.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new cc: Sam Leffler cc: freebsd-current@freebsd.org Subject: Re: WEP does not work? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 10:20:47 -0000 --nextPart11140297.9AWg76zxlh Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday, 10. December 2004 11:13, Kent Stewart wrote: > On Friday 10 December 2004 01:36 am, Michael Nottebrock wrote: > > On Friday, 10. December 2004 07:42, Sam Leffler wrote: > > > > Just curiosity, `hw' MIBs print both regdomain and countrycode > > > > are 0. > > > > > > hw.ath mib entries define values used to initialize each new ath > > > device. You cannot set regdomain (yet) but countrycode can be > > > overridden by setting hw.ath.countrycode before loading a device. > > > > This I've been wondering for a long time now - what countrycode > > represents what country? > > Are the following the ones you mean. See > http://www.ics.uci.edu/WebSoft/wwwstat/country-codes.txt No, I mean what values are valid for hw.ath.countrycode? =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart11140297.9AWg76zxlh Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBuXh2Xhc68WspdLARAk3xAKClpJBf5zQwmlkGI72Rq1EicNZEYgCgg4QQ FD5hd02NRX1sNljweSz49jg= =TpqH -----END PGP SIGNATURE----- --nextPart11140297.9AWg76zxlh-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 10:52:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E2AE16A4CE for ; Fri, 10 Dec 2004 10:52:49 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6221743D4C for ; Fri, 10 Dec 2004 10:52:46 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iBAAqWuj035375; Fri, 10 Dec 2004 21:22:32 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Fri, 10 Dec 2004 21:22:10 +1030 User-Agent: KMail/1.7.1 References: <200412081109.43840.sam@errno.com> <200412100213.40286.kstewart@owt.com> <200412101120.38869.michaelnottebrock@gmx.net> In-Reply-To: <200412101120.38869.michaelnottebrock@gmx.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1214133.RUsMVXFYZo"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412102122.30538.doconnor@gsoft.com.au> X-Spam-Score: -4.6 () IN_REP_TO,PGP_SIGNATURE_2,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: Sam Leffler cc: Kent Stewart Subject: Re: WEP does not work? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 10:52:49 -0000 --nextPart1214133.RUsMVXFYZo Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Fri, 10 Dec 2004 20:50, Michael Nottebrock wrote: > > Are the following the ones you mean. See > > http://www.ics.uci.edu/WebSoft/wwwstat/country-codes.txt > > No, I mean what values are valid for hw.ath.countrycode? I'd guess phone codes (ISO?) but it wouldn't suprise me if they invented=20 something new :) http://unstats.un.org/unsd/methods/m49/m49alpha.htm =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1214133.RUsMVXFYZo Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBuX/u5ZPcIHs/zowRAlyRAJ9imDufgyu/MT6noljwGJUl9dihVwCgqAPh HmWaQS4en7Nc1iJSLQUJn18= =vuH/ -----END PGP SIGNATURE----- --nextPart1214133.RUsMVXFYZo-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 11:11:36 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D00416A4CE for ; Fri, 10 Dec 2004 11:11:36 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 3E26843D1D for ; Fri, 10 Dec 2004 11:11:35 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 20260 invoked by uid 65534); 10 Dec 2004 11:11:33 -0000 Received: from pD955F9FD.dip.t-dialin.net (EHLO lofi.dyndns.org) (217.85.249.253) by mail.gmx.net (mp004) with SMTP; 10 Dec 2004 12:11:33 +0100 X-Authenticated: #443188 Received: from kiste.my.domain (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iBABBNhS051831 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 10 Dec 2004 12:11:27 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: "Daniel O'Connor" Date: Fri, 10 Dec 2004 12:11:18 +0100 User-Agent: KMail/1.7.1 References: <200412081109.43840.sam@errno.com> <200412101120.38869.michaelnottebrock@gmx.net> <200412102122.30538.doconnor@gsoft.com.au> In-Reply-To: <200412102122.30538.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1184401.jzl95Se8Iu"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412101211.22451.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new cc: Sam Leffler cc: freebsd-current@freebsd.org cc: Kent Stewart Subject: Re: WEP does not work? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 11:11:36 -0000 --nextPart1184401.jzl95Se8Iu Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday, 10. December 2004 11:52, Daniel O'Connor wrote: > On Fri, 10 Dec 2004 20:50, Michael Nottebrock wrote: > > > Are the following the ones you mean. See > > > http://www.ics.uci.edu/WebSoft/wwwstat/country-codes.txt > > > > No, I mean what values are valid for hw.ath.countrycode? > > I'd guess phone codes (ISO?) but it wouldn't suprise me if they invented > something new :) > > http://unstats.un.org/unsd/methods/m49/m49alpha.htm Nonono, no guessing this time, I want a definitive answer. :-) I tried about every countrycode-scheme I could find on hw.ath.countrycode o= n=20 my 5.2.1-R box yet, and some of them would be accepted, some not, but none = of=20 them would allow me to use the channels allowed by german regulations - I'm= =20 stuck with US defaults.=20 =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart1184401.jzl95Se8Iu Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBuYRaXhc68WspdLARAt0wAKCIJSo/YJ1PTZQryJ18cgbzX3xYfgCgnAz4 lBBlhMGBJdL2RAOMpl7p27s= =JUhQ -----END PGP SIGNATURE----- --nextPart1184401.jzl95Se8Iu-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 12:16:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F36316A4CE for ; Fri, 10 Dec 2004 12:16:33 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C63E43D5A for ; Fri, 10 Dec 2004 12:16:32 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iBACGMoP036061; Fri, 10 Dec 2004 22:46:22 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Fri, 10 Dec 2004 22:46:12 +1030 User-Agent: KMail/1.7.1 References: <200412081109.43840.sam@errno.com> <200412101120.38869.michaelnottebrock@gmx.net> <200412102122.30538.doconnor@gsoft.com.au> In-Reply-To: <200412102122.30538.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1140202.8BaqZDymvK"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412102246.20522.doconnor@gsoft.com.au> X-Spam-Score: -3.8 () IN_REP_TO,MIME_LONG_LINE_QP,NORMAL_HTTP_TO_IP,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: Sam Leffler cc: Kent Stewart Subject: Re: WEP does not work? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 12:16:33 -0000 --nextPart1140202.8BaqZDymvK Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Fri, 10 Dec 2004 21:22, Daniel O'Connor wrote: > On Fri, 10 Dec 2004 20:50, Michael Nottebrock wrote: > > > Are the following the ones you mean. See > > > http://www.ics.uci.edu/WebSoft/wwwstat/country-codes.txt > > > > No, I mean what values are valid for hw.ath.countrycode? > > I'd guess phone codes (ISO?) but it wouldn't suprise me if they invented > something new :) > > http://unstats.un.org/unsd/methods/m49/m49alpha.htm Ahah, I have strong evidence it's the OID number.. =46rom this patch.. http://216.239.63.104/search?q=3Dcache:o18wSW0lNSIJ:hanzubon.jp/tmp/madwifi= =2DIBM-combo.diff+atheros+%22country+code%22&hl=3Den&ie=3DUTF-8 0x188 =3D 392, 392 + Japan in Google gets you to=20 http://www.alvestrand.no/objectid/1.2.html So Germany would be 276. It's another guess, but more informed 8-) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1140202.8BaqZDymvK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBuZOU5ZPcIHs/zowRAlnAAJ0QILwJX3wCs21Zz6ycEePHctg7FwCgqNDH pIP7Ru7Sq7mpV968W2M0Z1A= =kXoQ -----END PGP SIGNATURE----- --nextPart1140202.8BaqZDymvK-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 9 17:39:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71AEF16A4CE for ; Thu, 9 Dec 2004 17:39:51 +0000 (GMT) Received: from damo.axelero.hu (fe01.axelero.hu [195.228.240.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 952EF43D58 for ; Thu, 9 Dec 2004 17:39:50 +0000 (GMT) (envelope-from kutizs@axelero.hu) Received: from damo (localhost-02 [127.0.2.1]) by damo.axelero.hu (8.12.11/8.12.11) with SMTP id iB9Hdnvi049162 for ; Thu, 9 Dec 2004 18:39:49 +0100 (CET) Received: from fe01.axelero.hu [127.0.2.1] via SMTP gateway by damo [195.228.240.89]; id A0C004F1FF8 at Thu, 09 Dec 2004 18:39:48 +0100 Received: from tinca.kuti.hu (ktv32-239-75.catv-pool.axelero.hu [62.201.75.239]) by fe01.axelero.hu (8.12.11/8.12.11) with SMTP id iB9HdkJj049119 for ; Thu, 9 Dec 2004 18:39:47 +0100 (CET) Date: Thu, 9 Dec 2004 18:39:11 +0100 From: Zsolt =?ISO-8859-2?Q?K=FAti?= To: freebsd-current@freebsd.org Message-Id: <20041209183911.068c9a84.kutizs@axelero.hu> X-Mailer: Sylpheed version 1.0.0beta3 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new X-Mailman-Approved-At: Fri, 10 Dec 2004 12:42:52 +0000 Subject: TIMEOUT - WRITE_DMA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Dec 2004 17:39:51 -0000 Hello, My system produces these messages that I already know well from this list (as well ;): ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=213249674 I would like to report my experiences with 5.3 RELEASE/STABLE/B7 After these messages the two former cases result in FAILURE and finally in panic. Even background fsck cannot run without another panic, only single user mode can help. All these prevent using them on my HW. However B7, although displays the messages as well, works seemingly fine. For the time being this version is sufficent, but I'd like to know - if possible at all - what the difference could be between the versions and if one can expect to bring the actual 5.3 version's state to B7's in this respect? Further to this, the different versions display the behavior of relatively frequently (many time in an hour?) stalling their responsivity for some seconds. Most of the times no message can be seen on the consol after this. It is also more rare on B7. I also found that pendrive's sensing by 5.3 RELEASE/STABLE more frequently results in panic than B7's. (As a matter of fact I have not seen it with B7 for weeks since I installed it.) I use the following either with GENERIC or custom kernel: Abit NF7-S (nVidia chipsets, SiI3112 on board), Athlon 2600+, Samsung 120G SATA, LEXAR MEDIA JUMPDRIVE, rev 1.10/0.01 Please cc it to me as well, since I'am not on the list for the time being. Many thanks! Zsolt -------------------- Zsolt Kuti From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 12:21:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 179A116A4CE for ; Fri, 10 Dec 2004 12:21:41 +0000 (GMT) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 545A343D45 for ; Fri, 10 Dec 2004 12:21:38 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from orion.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226])iBACLaBB024771 for ; Fri, 10 Dec 2004 14:21:36 +0200 Received: from orion.daedalusnetworks.priv (orion [127.0.0.1]) iBACLZjb083713 for ; Fri, 10 Dec 2004 14:21:35 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost)iBACLZaR083708 for freebsd-current@freebsd.org; Fri, 10 Dec 2004 14:21:35 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Date: Fri, 10 Dec 2004 14:21:35 +0200 From: Giorgos Keramidas To: freebsd-current@freebsd.org Message-ID: <20041210122135.GA55683@orion.daedalusnetworks.priv> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Mailman-Approved-At: Fri, 10 Dec 2004 12:42:52 +0000 Subject: PicoBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 12:21:41 -0000 Has anyone successfully built a PicoBSD floppy in CURRENT? I hacked at the picobsd shell script last night, and actually made it the part that the kernel is copied into the md filesystem. There seems to be no way to fit PICOBSD kernels in a single 1.44MB floppy though. From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 14:51:14 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 324ED16A4CE for ; Fri, 10 Dec 2004 14:51:14 +0000 (GMT) Received: from mailgate3.roche.com (mailgate3.roche.com [196.3.50.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 498BA43D4C for ; Fri, 10 Dec 2004 14:51:13 +0000 (GMT) (envelope-from andre.van_schalkwyk@roche.com) Received: from rkamsemcn1.emea.roche.com ([145.245.214.243]) by mailgate3.roche.com (MOS 3.5.5-GR) with ESMTP id APG30771; Fri, 10 Dec 2004 15:51:10 +0100 (CET) Received: from rkamsem1.emea.roche.com ([145.245.142.209]) by rkamsemcn1.emea.roche.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 10 Dec 2004 15:51:10 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 10 Dec 2004 15:51:10 +0100 Message-ID: <47318C4EB396E34F85DEEBB86C3718F801D3D52B@rkamsem1.emea.roche.com> Thread-Topic: HEADSUP: ath updates Thread-Index: AcTdWGQK1oza1RpiTieJod5Ll/tQjQBbutwA From: "van Schalkwyk, Andre {PGIN~Kaiseraugst}" To: "Sam Leffler" , X-OriginalArrivalTime: 10 Dec 2004 14:51:10.0677 (UTC) FILETIME=[B00DD050:01C4DEC7] Subject: RE: HEADSUP: ath updates X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 14:51:14 -0000 Any idea when the ath_hal will support atheros 5213 chips?=20 -andre -----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Sam Leffler Sent: Wednesday, December 08, 2004 8:10 PM To: freebsd-current@freebsd.org Subject: HEADSUP: ath updates I just committed updates for the ath driver and the ath hal. There are many=20 changes to this code including a split of the tx rate control algorithm into=20 a separate module. This means that when statically configuring the driver=20 you now need to specify: device ath device ath_hal device ath_rate_onoe to get the previous functionality (i.e. the previous rate control algorithm). =20 There is a second rate control algorithm that is slightly different from the=20 onoe algorithm; you can try that with device ath_rate_amrr However both of these algorithms are still rather lame and a good algorithm is=20 needed. I encourage folks to step up and work on this as a good tx rate control algorithm makes all the difference. The new hal should support all shipping Atheros parts. Operation should be=20 noticeably better and the driver supports all the functionality of the=20 revised net80211 layer. This includes the security protocols (WPA, 802.11i,=20 802.1x), the QoS/Multi-media protocols (WME/WMM), and more. One problem to beware of is that WME and WPA currently do not work together=20 (for AP operation at least). If you want to test out WPA be sure to disable=20 wme--this will require the new ifconfig that I'll be committing shortly. There's still a bunch of work to do on the driver. I'll be working fulltime=20 on this stuff for the next few months; mainly on AP support. Sam _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 15:57:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 23D4B16A4CE for ; Fri, 10 Dec 2004 15:57:43 +0000 (GMT) Received: from ns1.u-strasbg.fr (ns1.u-strasbg.fr [130.79.200.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F20D43D66 for ; Fri, 10 Dec 2004 15:57:42 +0000 (GMT) (envelope-from pda@crc.u-strasbg.fr) Received: from vagabond.ma.maison (vagabond.u-strasbg.fr [130.79.201.140]) iBAFvPUQ017541 ; Fri, 10 Dec 2004 16:57:25 +0100 (CET) Received: from vagabond.ma.maison (localhost [127.0.0.1]) iBAFvPaT000275 ; Fri, 10 Dec 2004 16:57:25 +0100 (CET) Received: (from pda@localhost) by vagabond.ma.maison (8.13.1/8.13.1/Submit) id iBAFL74r033770; Fri, 10 Dec 2004 16:21:07 +0100 (CET) (envelope-from pda) Date: Fri, 10 Dec 2004 16:16:28 +0100 From: Pierre DAVID To: Sam Leffler Message-ID: <20041210151628.GA33593@vagabond.ma.maison> References: <200412081059.22949.sam@errno.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200412081059.22949.sam@errno.com> User-Agent: Mutt/1.5.6i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.3 (ns1.u-strasbg.fr [130.79.200.1]); Fri, 10 Dec 2004 16:57:25 +0100 (CET) X-Antivirus: scanned by sophos at u-strasbg.fr cc: freebsd-current@freebsd.org Subject: Re: HEADSUP: updated net80211 layer committed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 15:57:43 -0000 On Wed, Dec 08, 2004 at 10:59:19AM -0800, Sam Leffler wrote: > > I just committed a major update to the 802.11 support. I did my best to > verify all existing users compile and work (where I have cards) but there's > sure to be some fallout. In particular I expect that wi cards operating in > hostap with wep will need some fixup. If you encounter problems please post > here as I've been promised other folks will assist in handling issues. > This is really a major update! I'm now able to use our 802.11 network, with an EAP/TTLS based 802.1X authentication. Nearly everything went smoothly, except two nits: - as EAP/TTLS support was apparently not enabled in the wpa_supplicant port, I had to force its configuration. - I had to manually set: ifconfig ath0 authmode 8021x (ifconfig was incorrectly using WPA1+WPA2) Thanks for this great and long awaited work! Pierre From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 16:04:32 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C245D16A4CE for ; Fri, 10 Dec 2004 16:04:32 +0000 (GMT) Received: from kweetal.tue.nl (kweetal.tue.nl [131.155.3.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57D0943D1F for ; Fri, 10 Dec 2004 16:04:32 +0000 (GMT) (envelope-from stijn@pcwin002.win.tue.nl) Received: by kweetal.tue.nl (Postfix, from userid 40) id 6D8E413B8EB; Fri, 10 Dec 2004 17:04:31 +0100 (CET) Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by kweetal.tue.nl (Postfix) with ESMTP id 707EC13B804; Fri, 10 Dec 2004 17:04:30 +0100 (CET) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.13.1/8.13.1/Submit) id iBAG4U6l002431; Fri, 10 Dec 2004 17:04:30 +0100 (CET) (envelope-from stijn) Date: Fri, 10 Dec 2004 17:04:30 +0100 From: Stijn Hoop To: Pierre DAVID Message-ID: <20041210160430.GY69536@pcwin002.win.tue.nl> References: <200412081059.22949.sam@errno.com> <20041210151628.GA33593@vagabond.ma.maison> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="W/D3X8sky0X3AmG5" Content-Disposition: inline In-Reply-To: <20041210151628.GA33593@vagabond.ma.maison> User-Agent: Mutt/1.4.2.1i X-Bright-Idea: Let's abolish HTML mail! X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on kweetal.tue.nl X-Spam-DCC: : X-Spam-Status: No, hits=-4.9 required=6.3 tests=BAYES_00 autolearn=ham version=2.64 X-Spam-Level: cc: Sam Leffler cc: freebsd-current@freebsd.org Subject: Re: HEADSUP: updated net80211 layer committed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 16:04:32 -0000 --W/D3X8sky0X3AmG5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 10, 2004 at 04:16:28PM +0100, Pierre DAVID wrote: > This is really a major update! I'm now able to use our 802.11 > network, with an EAP/TTLS based 802.1X authentication. I guess it doesn't yet work with the 'unofficial' ipi/ipw driver? I haven't tried it yet but I recently acquired an Intel 2200BG to replace my Dell Broadcom proprietary card. So I guess I'll wait for the iwi/ipw maintainer = to catch up. No hurry, Damien! I'm just anxious! Great work by Sam though -- this is indeed what I need to get wireless to work at our university. --Stijn --=20 If today is the first day of the rest of your life, what the hell was yesterday? --W/D3X8sky0X3AmG5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBuckOY3r/tLQmfWcRAuPrAKCQv3sFX2Oec3nAnZkYKohWjoYDVACdEnDi e76V8gIiSAQHYqBn1LI1zEU= =Fmfx -----END PGP SIGNATURE----- --W/D3X8sky0X3AmG5-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 16:46:01 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9C34216A4CE for ; Fri, 10 Dec 2004 16:46:01 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D9E643D48 for ; Fri, 10 Dec 2004 16:46:01 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.91] ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id iBAGjuWi036591 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Dec 2004 08:45:56 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <41B9D4C6.5010307@errno.com> Date: Fri, 10 Dec 2004 08:54:30 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pierre DAVID References: <200412081059.22949.sam@errno.com> <20041210151628.GA33593@vagabond.ma.maison> In-Reply-To: <20041210151628.GA33593@vagabond.ma.maison> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: HEADSUP: updated net80211 layer committed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 16:46:01 -0000 Pierre DAVID wrote: > On Wed, Dec 08, 2004 at 10:59:19AM -0800, Sam Leffler wrote: > >>I just committed a major update to the 802.11 support. I did my best to >>verify all existing users compile and work (where I have cards) but there's >>sure to be some fallout. In particular I expect that wi cards operating in >>hostap with wep will need some fixup. If you encounter problems please post >>here as I've been promised other folks will assist in handling issues. >> > > > This is really a major update! I'm now able to use our 802.11 > network, with an EAP/TTLS based 802.1X authentication. > > Nearly everything went smoothly, except two nits: > > - as EAP/TTLS support was apparently not enabled in the > wpa_supplicant port, I had to force its configuration. Hmm, yes forgot about that. We have openssl already in the base system so we can automatically include support (though not sure if the current version has everything). As I said before it'd be good if someone were to pick up the port and fix it up and commit it. > > - I had to manually set: > ifconfig ath0 authmode 8021x > (ifconfig was incorrectly using WPA1+WPA2) This is a bug in driver_bsd.c. It should check if no WPA is request and set the authentication mode appropriately. If you have a fix please send it to Jouni; otherwise I'll add it to my TODO list. Sam From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 16:52:08 2004 Return-Path: Delivered-To: freebsd-current@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2432C16A4CE for ; Fri, 10 Dec 2004 16:52:08 +0000 (GMT) Received: from area51.capnet.state.tx.us (area51.capnet.state.tx.us [141.198.193.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9F0943D2F for ; Fri, 10 Dec 2004 16:52:07 +0000 (GMT) (envelope-from trorki@area51.capnet.state.tx.us) Received: from area51.capnet.state.tx.us (localhost.capnet.state.tx.us [127.0.0.1])iBAGoBHY035673 for ; Fri, 10 Dec 2004 10:50:11 -0600 (CST) (envelope-from trorki@area51.capnet.state.tx.us) Received: from localhost (stu@localhost)iBAGoBaG035670 for ; Fri, 10 Dec 2004 10:50:11 -0600 (CST) X-Authentication-Warning: area51.capnet.state.tx.us: stu owned process doing -bs Date: Fri, 10 Dec 2004 10:50:11 -0600 (CST) From: trorki@area51.capnet.state.tx.us X-X-Sender: stu@area51.capnet.state.tx.us To: freebsd-current@www.freebsd.org In-Reply-To: <20041208180601.T29045@area51.capnet.state.tx.us> Message-ID: <20041210104635.J35181@area51.capnet.state.tx.us> References: <200412081205.39354.mi+mx@aldan.algebra.com> <20041208180601.T29045@area51.capnet.state.tx.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: -current ISOs and update cvsup sites for AMD64? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: trorki@area51.capnet.state.tx.us List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 16:52:08 -0000 I've looked at snapshots.jp.freebsd.org and snapshots.se.freebsd.org and can't find a recent snapshot ISO to get -current for AMD64. Am I missing the directory, or what? Someone please let me know where to get a recent ISO, and where I should point cvsup for the updates. Please be specific. stu From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 17:01:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F31216A4CE for ; Fri, 10 Dec 2004 17:01:33 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E43743D1F for ; Fri, 10 Dec 2004 17:01:33 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.91] ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id iBAH1PWi036642 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Dec 2004 09:01:30 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <41B9D868.20900@errno.com> Date: Fri, 10 Dec 2004 09:10:00 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Daniel O'Connor" References: <200412101301.06484.doconnor@gsoft.com.au> <200412101318.15278.doconnor@gsoft.com.au> In-Reply-To: <200412101318.15278.doconnor@gsoft.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Recent ifconfig changes choke on fwip X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 17:01:33 -0000 Daniel O'Connor wrote: >On Fri, 10 Dec 2004 13:00, Daniel O'Connor wrote: > > >>I tried to do some tracing in GDB the line numbers don't seem to match up >>properly :-/ >> >> > >Ahh, building without -O2 helps.. >(gdb) bt >#0 0x0804b57a in in_status (s=7, info=0x805a134) at /usr/src/sbin/ifconfig/af_inet.c:69 >#1 0x0804a046 in af_all_status (s=7, sdl=0x805a134) at /usr/src/sbin/ifconfig/ifconfig.c:405 >#2 0x0804af39 in status (afp=0x80563c0, addrcount=0, sdl=0x805a134, ifm=0x805a0d4, ifam=0x0) > at /usr/src/sbin/ifconfig/ifconfig.c:850 >#3 0x08049e05 in main (argc=0, argv=0xbfbfe914) at /usr/src/sbin/ifconfig/ifconfig.c:349 > >(gdb) list af_inet.c:69 >64 >65 sin = (struct sockaddr_in *)info->rti_info[RTAX_IFA]; >66 if (sin == NULL) >67 return; >68 >69 printf("\tinet %s ", inet_ntoa(sin->sin_addr)); >70 >71 if (flags & IFF_POINTOPOINT) { >72 /* note RTAX_BRD overlap with IFF_BROADCAST */ >73 sin = (struct sockaddr_in *)info->rti_info[RTAX_BRD]; >(gdb) print sin >$3 = (struct sockaddr_in *) 0xfe >(gdb) print info->rti_info >$4 = {0x100590, 0x70697766, 0xc04f4330, 0xa4170800, 0xff020a38, 0xfe, 0x0, 0x0 > > I don't have any firewire devicesto test with. Someone else will need to pickup this one. Sam From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 17:08:44 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6B0B16A4CE for ; Fri, 10 Dec 2004 17:08:44 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B55743D48 for ; Fri, 10 Dec 2004 17:08:44 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.91] ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id iBAH8hWi036681 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Dec 2004 09:08:44 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <41B9DA1E.4060504@errno.com> Date: Fri, 10 Dec 2004 09:17:18 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Daniel O'Connor" References: <200412101553.29518.doconnor@gsoft.com.au> In-Reply-To: <200412101553.29518.doconnor@gsoft.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Can't see BSS ID on if_ndis X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 17:08:44 -0000 Daniel O'Connor wrote: >Hi, >1.73 of if_ndis.c works which is the good news :) > >However I don't see which BSSID I'm associated with using wicontrol -L.. >[inchoate 15:50] ~ >sudo wicontrol -i ndis0 -L > > wicontrol is now completely deprecated unless you want to look at something like the nic serial number. Every other function is available in ifconfig. At some point I want to remove wicontrol (and other tools) and place the device-specific functionality in ifconfig extensions/plugins (e.g. for loading firmware). This would permit us to nuke all the ioctl compatibility code unless it's needed/fdesired for 3rd party apps like dstumbler. Ideally these apps will move to the new ioctls because they are better (simpler to use, return more information, and provide more direct control over the device). >... >TX encryption key: [ 0 ] >Encryption keys: [ ][ ][ ][ ] >Available APs: >1 station: >SSID BSSID Chan SN S N Intrvl Capinfo >citilan [ 00:00:00:00:00:00 ] [ 4 ] [ 0 0 0 ] 0 > [ 11b 5b 2b 1b 5.5b ] > >Neither does ifconfig.. >[inchoate 15:51] ~ >ifconfig -v ndis0 list scan >SSID BSSID CHAN RATE S:N INT CAPS >citilan 00:00:00:00:00:00 4 11M 0:0 0 > >Howver, using wicontrol -l shows it.. >[inchoate 15:50] ~ >sudo wicontrol -i ndis0 -l >1 station: >ap[0]: > netname (SSID): [ citilan ] > BSSID: [ 00:40:96:40:47:80 ] > Channel: [ 4 ] > Quality/Signal/Noise [signal]: [ 72 / 72 / 0 ] > [dBm]: [ 72 / -77 / -149 ] > BSS Beacon Interval [msec]: [ 0 ] > Capinfo: [ ] > DataRate [Mbps]: [ 11 ] > > wicontrol uses compatibility ioctls and direct RID requests to fetch data. ifconfig uses ioctls that are intended to be common across all devices. Drivers will need some updates to insure all the common ioctls are supported. I don't use the ndis driver so someone else will need to help out on this. Folks have promised to help with issues like this. The good news is that the new ioctls provide significantly more information than the older ones so it's like that data that was being discarded because it was not available will finally be accessible. >Also, when you run ifconfig after setting an SSID it doesn't actually display >it unless you're associated (not sure if that's a bug). > > I'll check; there are two ssids maintained: a desired ssid which is the one you want to match when associating, and the ssid actually returned by the ap. One or the other is returned depending the state of the interface. Sam From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 17:10:14 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A64E116A4CE for ; Fri, 10 Dec 2004 17:10:14 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E58843D2F for ; Fri, 10 Dec 2004 17:10:14 +0000 (GMT) (envelope-from arr@watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iBAH7cVT079490; Fri, 10 Dec 2004 12:07:38 -0500 (EST) (envelope-from arr@watson.org) Received: from localhost (arr@localhost)iBAH7caN079487; Fri, 10 Dec 2004 12:07:38 -0500 (EST) (envelope-from arr@watson.org) X-Authentication-Warning: fledge.watson.org: arr owned process doing -bs Date: Fri, 10 Dec 2004 12:07:38 -0500 (EST) From: "Andrew R. Reiter" To: Sam Leffler In-Reply-To: <41B9D868.20900@errno.com> Message-ID: <20041210120617.S79401@fledge.watson.org> References: <200412101301.06484.doconnor@gsoft.com.au> <200412101318.15278.doconnor@gsoft.com.au> <41B9D868.20900@errno.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: Recent ifconfig changes choke on fwip X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 17:10:14 -0000 On Fri, 10 Dec 2004, Sam Leffler wrote: :Daniel O'Connor wrote: : :>On Fri, 10 Dec 2004 13:00, Daniel O'Connor wrote: :> :> :>>I tried to do some tracing in GDB the line numbers don't seem to match up :>>properly :-/ :>> :>> :> :>Ahh, building without -O2 helps.. :>(gdb) bt :>#0 0x0804b57a in in_status (s=7, info=0x805a134) at /usr/src/sbin/ifconfig/af_inet.c:69 :>#1 0x0804a046 in af_all_status (s=7, sdl=0x805a134) at /usr/src/sbin/ifconfig/ifconfig.c:405 :>#2 0x0804af39 in status (afp=0x80563c0, addrcount=0, sdl=0x805a134, ifm=0x805a0d4, ifam=0x0) :> at /usr/src/sbin/ifconfig/ifconfig.c:850 :>#3 0x08049e05 in main (argc=0, argv=0xbfbfe914) at /usr/src/sbin/ifconfig/ifconfig.c:349 :> :>(gdb) list af_inet.c:69 :>64 :>65 sin = (struct sockaddr_in *)info->rti_info[RTAX_IFA]; :>66 if (sin == NULL) :>67 return; :>68 :>69 printf("\tinet %s ", inet_ntoa(sin->sin_addr)); :>70 :>71 if (flags & IFF_POINTOPOINT) { :>72 /* note RTAX_BRD overlap with IFF_BROADCAST */ :>73 sin = (struct sockaddr_in *)info->rti_info[RTAX_BRD]; :>(gdb) print sin :>$3 = (struct sockaddr_in *) 0xfe :>(gdb) print info->rti_info :>$4 = {0x100590, 0x70697766, 0xc04f4330, 0xa4170800, 0xff020a38, 0xfe, 0x0, 0x0 :> I missed the earlier post, how to reproduce this? I am building world right now (update from a couple days ago to pickup net80211, some phk changes, and urmm uhh, oh imp@ changes) so I can test... pending my TI ieee1394 cbb card works. Cheers, Andrew :> : :I don't have any firewire devicesto test with. Someone else will need :to pickup this one. : : Sam : :_______________________________________________ :freebsd-current@freebsd.org mailing list :http://lists.freebsd.org/mailman/listinfo/freebsd-current :To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" : : -- Andrew R. Reiter arr@watson.org arr@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 17:14:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E191A16A4CE for ; Fri, 10 Dec 2004 17:14:15 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id B589443D2F for ; Fri, 10 Dec 2004 17:14:15 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.91] ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id iBAHEEWi036725 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Dec 2004 09:14:15 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <41B9DB69.1050708@errno.com> Date: Fri, 10 Dec 2004 09:22:49 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Nottebrock References: <200412081109.43840.sam@errno.com> <20041209.225041.63112571.rushani@bl.mmtr.or.jp> <41B9454F.9080903@errno.com> <200412101036.07460.michaelnottebrock@gmx.net> In-Reply-To: <200412101036.07460.michaelnottebrock@gmx.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: WEP does not work? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 17:14:16 -0000 Michael Nottebrock wrote: >On Friday, 10. December 2004 07:42, Sam Leffler wrote: > > > >>>Just curiosity, `hw' MIBs print both regdomain and countrycode are 0. >>> >>> >>hw.ath mib entries define values used to initialize each new ath device. >> You cannot set regdomain (yet) but countrycode can be overridden by >>setting hw.ath.countrycode before loading a device. >> >> > >This I've been wondering for a long time now - what countrycode represents >what country? > > These are iso country codes. The regulatory domain codes are iso also but include non-iso ones defined for groups of locales with common operating characteristics. Then there are ones that have been added because countries/regdomain's change their operating requirements and it's necessary to recognize both old and new requirements. Sam From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 17:22:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5774316A4CE for ; Fri, 10 Dec 2004 17:22:27 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AB5F43D39 for ; Fri, 10 Dec 2004 17:22:27 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.91] ([66.127.85.91]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id iBAHMOWi036756 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Dec 2004 09:22:25 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <41B9DD52.4030603@errno.com> Date: Fri, 10 Dec 2004 09:30:58 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0RC1 (X11/20041208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Stijn Hoop References: <200412081059.22949.sam@errno.com> <20041210151628.GA33593@vagabond.ma.maison> <20041210160430.GY69536@pcwin002.win.tue.nl> In-Reply-To: <20041210160430.GY69536@pcwin002.win.tue.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: HEADSUP: updated net80211 layer committed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 17:22:27 -0000 Stijn Hoop wrote: >On Fri, Dec 10, 2004 at 04:16:28PM +0100, Pierre DAVID wrote: > > >>This is really a major update! I'm now able to use our 802.11 >>network, with an EAP/TTLS based 802.1X authentication. >> >> > >I guess it doesn't yet work with the 'unofficial' ipi/ipw driver? I haven't >tried it yet but I recently acquired an Intel 2200BG to replace my Dell >Broadcom proprietary card. So I guess I'll wait for the iwi/ipw maintainer to >catch up. No hurry, Damien! I'm just anxious! > >Great work by Sam though -- this is indeed what I need to get wireless >to work at our university. > > I would like to see all the drivers in the tree updated to use the new functionality. Most drivers should be capable of doing WPA, albeit with some work. If wpa_supplicant and hostapd work out well (and I believe they will) I'd like to see them brought into the base system and properly integrated. There's really no reason to use static key'd WEP any more now that we can build WPA authenticators and commercial AP's are supporting WPA-PSK. Sam From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 17:32:32 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5097E16A4CE for ; Fri, 10 Dec 2004 17:32:32 +0000 (GMT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 553B043D4C for ; Fri, 10 Dec 2004 17:32:31 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 24714 invoked by uid 65534); 10 Dec 2004 17:32:30 -0000 Received: from pD955F9FD.dip.t-dialin.net (EHLO lofi.dyndns.org) (217.85.249.253) by mail.gmx.net (mp004) with SMTP; 10 Dec 2004 18:32:30 +0100 X-Authenticated: #443188 Received: from kiste.my.domain (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iBAHWQhS056216 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 10 Dec 2004 18:32:27 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: Sam Leffler Date: Fri, 10 Dec 2004 18:32:23 +0100 User-Agent: KMail/1.7.1 References: <200412081109.43840.sam@errno.com> <200412101036.07460.michaelnottebrock@gmx.net> <41B9DB69.1050708@errno.com> In-Reply-To: <41B9DB69.1050708@errno.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3188266.zPYpLrZaCd"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412101832.24112.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new cc: freebsd-current@freebsd.org Subject: Re: WEP does not work? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 17:32:32 -0000 --nextPart3188266.zPYpLrZaCd Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday, 10. December 2004 18:22, Sam Leffler wrote: > Michael Nottebrock wrote: > >On Friday, 10. December 2004 07:42, Sam Leffler wrote: > >>>Just curiosity, `hw' MIBs print both regdomain and countrycode are 0. > >> > >>hw.ath mib entries define values used to initialize each new ath device. > >> You cannot set regdomain (yet) but countrycode can be overridden by > >>setting hw.ath.countrycode before loading a device. > > > >This I've been wondering for a long time now - what countrycode represen= ts > >what country? > > These are iso country codes. The regulatory domain codes are iso also > but include non-iso ones defined for groups of locales with common > operating characteristics. Then there are ones that have been added > because countries/regdomain's change their operating requirements and > it's necessary to recognize both old and new requirements. Does somebody (perhaps Atheros Comms. themselves) maintain a publicly=20 available list somewhere? =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart3188266.zPYpLrZaCd Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBud2oXhc68WspdLARAnv3AJ41feDqeVeFhxFa8b+8907ffU2FQQCff8W+ J0Ga8MbtoZC8Yjdt2kN/ePE= =e+6J -----END PGP SIGNATURE----- --nextPart3188266.zPYpLrZaCd-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 20:01:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9271E16A4CF for ; Fri, 10 Dec 2004 20:01:21 +0000 (GMT) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E7D643D68 for ; Fri, 10 Dec 2004 20:01:20 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 96897 invoked from network); 10 Dec 2004 19:50:52 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 10 Dec 2004 19:50:52 -0000 Message-ID: <41BA0088.9000107@freebsd.org> Date: Fri, 10 Dec 2004 21:01:12 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a5) Gecko/20041122 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-net@freebsd.org cc: gallatin@cs.duke.edu Subject: Rewritten TCP reassembly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 20:01:21 -0000 I've totally rewritten the TCP reassembly function to be a lot more efficient. In tests with normal bw*delay products and packet loss plus severe reordering I've measured an improvment of at least 30% in performance. For high and very high bw*delay product links the performance improvement is most likely much higher. The main property of the new code is O(1) insert for 95% of all normal reassembly cases. If there is more than one hole the insert time is O(holes). If a packet arrives that closes a hole the chains to the left and right are merged. Artificially constructed worst case is O(n). No malloc's are done for new segments. The old code was O(n) in all cases plus n*malloc for a describing structure. There are some problems with the new code I will fix before committing it to the tree. One is it can't handle non-writeable mbuf's and the other is too little leading space in the mbuf (found only on loopback interface, but there we don't have packet loss). Once these two are dealed with it is ready to go in. Nothing is perfect and this code is only a first significant step over what we have currently in the tree, especially for transfers over lossy (wireless) and high speed links with and without packet reordering. I have the next steps already in the works which will further optimize (worst case O(windowsize/mclusters) instead of O(n)) and simplify a bit more again. The patch can be found here: http://www.nrg4u.com/freebsd/tcp_reass-20041210.patch Please test and report good and bad news back. -- Andre From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 20:52:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F4CE16A4CE for ; Fri, 10 Dec 2004 20:52:28 +0000 (GMT) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C4E543D49 for ; Fri, 10 Dec 2004 20:52:28 +0000 (GMT) (envelope-from sepotvin@videotron.ca) Received: from [10.0.0.210] ([67.70.237.74]) by VL-MO-MR011.ip.videotron.ca (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTPA id <0I8I00DFSXZDZ3@VL-MO-MR011.ip.videotron.ca> for freebsd-current@FreeBSD.org; Fri, 10 Dec 2004 15:52:27 -0500 (EST) Date: Fri, 10 Dec 2004 15:52:23 -0500 From: "Stephane E. Potvin" To: freebsd-current@FreeBSD.org Message-id: <41BA0C87.8080008@videotron.ca> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en User-Agent: Mozilla Thunderbird 1.0 (X11/20041208) X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Subject: Latest 802.11 changes and ndis X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 20:52:28 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Since the recent changes to the 802.11 infrastructure, I've not been unable to use the wireless card in my laptop using the ndis interface. Using tcpdump on the interface, I noticed that no packets are making their way out (no packets whatsoever in the dump). The association with the AP is making place though. The interface is configured to use WEP. The wireless router is a Linksys WRT54G. here's the relevent output of dmesg before and after the changes: before: ndis0: mem 0xfafec000-0xfafedfff irq 17 at device 3.0 on pci2 ndis0: NDIS API version: 5.0 ndis0: Ethernet address: 00:90:4b:78:cb:fc ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 36Mbps 48Mbps 54Mbps ndis0: link up after (with verbose on): ndis0: mem 0xfafec000-0xfafedfff irq 17 at device 3.0 on pci2 ndis0: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfafec000 ndis0: [MPSAFE] ndis0: NDIS API version: 5.0 ndis0: bpf attached ndis0: Ethernet address: 00:90:4b:78:cb:fc ndis0: bpf attached ndis0: link up The ndis driver data was generated from the driver that came with the laptop: DriverVer=06/13/2003, 3.20.32.0 files: bcmwl5.inf, bcmwl5.sys I'll be happy to provide any other information needed in case what is here is not complete. Thanks in advance, Steph -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBugyGmdOXtTCX/nsRAvaZAKCgDMPSBB41Eok99erUxaKiXPlh3wCffH3G LWjNXnv0++FKaPtl7jrfUYk= =KrRl -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 20:53:07 2004 Return-Path: Delivered-To: freebsd-current@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C74C16A4CE for ; Fri, 10 Dec 2004 20:53:07 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CDA143D46 for ; Fri, 10 Dec 2004 20:53:07 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A8016540F7; Fri, 10 Dec 2004 12:59:51 -0800 (PST) Date: Fri, 10 Dec 2004 12:59:51 -0800 From: Kris Kennaway To: trorki@area51.capnet.state.tx.us Message-ID: <20041210205951.GA54091@xor.obsecurity.org> References: <200412081205.39354.mi+mx@aldan.algebra.com> <20041208180601.T29045@area51.capnet.state.tx.us> <20041210104635.J35181@area51.capnet.state.tx.us> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="82I3+IH0IqGh5yIs" Content-Disposition: inline In-Reply-To: <20041210104635.J35181@area51.capnet.state.tx.us> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@www.freebsd.org Subject: Re: -current ISOs and update cvsup sites for AMD64? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 20:53:07 -0000 --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 10, 2004 at 10:50:11AM -0600, trorki@area51.capnet.state.tx.us = wrote: >=20 > I've looked at snapshots.jp.freebsd.org and snapshots.se.freebsd.org > and can't find a recent snapshot ISO to get -current for AMD64. > Am I missing the directory, or what? Someone please let me know where > to get a recent ISO The above site; talk to the admins about why they're not being produced (probably it's just an oversight). >, and where I should point cvsup for the updates. Updates to what? amd64 isn't different from the other architectures; you can read the documentation on using and configuring cvsup in the handbook, and if you have further specific questions then ask them then. Kris --82I3+IH0IqGh5yIs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBug5HWry0BWjoQKURAqpCAKCljr7ublpz6QhSVAsrTJ5mahbYcwCfWoEN GWqUUH73N19u0RxYTIUY8BM= =e6vz -----END PGP SIGNATURE----- --82I3+IH0IqGh5yIs-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 21:37:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19D4E16A4CE for ; Fri, 10 Dec 2004 21:37:51 +0000 (GMT) Received: from vsmtp2.tin.it (vsmtp2alice.tin.it [212.216.176.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8411A43D58 for ; Fri, 10 Dec 2004 21:37:50 +0000 (GMT) (envelope-from rionda@gufi.org) Received: from kaiser.sig11.org (82.52.116.120) by vsmtp2.tin.it (7.0.027) id 41B458B9001D76E1 for freebsd-current@freebsd.org; Fri, 10 Dec 2004 22:37:50 +0100 Received: from localhost.localdomain (localhost [127.0.0.1]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by kaiser.sig11.org (Postfix) with ESMTP id 0194C620D for ; Fri, 10 Dec 2004 22:37:47 +0100 (CET) From: Matteo Riondato To: freebsd-current@freebsd.org In-Reply-To: <6.2.0.14.2.20041207213333.03eb7298@pozo.com> References: <6.2.0.14.2.20041206075313.03e74db8@pozo.com> <20041207235104.K637@alpha.siliconlandmark.com> <20041208050620.GG2629@dan.emsphone.com> <20041208000849.D637@alpha.siliconlandmark.com> <6.2.0.14.2.20041207213333.03eb7298@pozo.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-cwEIIK2HmDT//hYD5lj1" Date: Fri, 10 Dec 2004 22:37:44 +0100 Message-Id: <1102714664.773.0.camel@kaiser.sig11.org> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Subject: Re: Accounting resumed, Accounting suspended repeatedly (Was: Re: dump broken with new kernel) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 21:37:51 -0000 --=-cwEIIK2HmDT//hYD5lj1 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Il giorno Mar, 07-12-2004 alle 21:36 -0800, Manfred Antar ha scritto: > At 09:15 PM 12/7/2004, Andre Guibert de Bruet wrote: >=20 > >On Tue, 7 Dec 2004, Dan Nelson wrote: > > > >>In the last episode (Dec 07), Andre Guibert de Bruet said: > >>>On Mon, 6 Dec 2004, Manfred Antar wrote: > >>> > >>>>I'm also seeing alot of : > >>>>Dec 6 10:06:53 pozo kernel: Accounting resumed > >>>>Dec 6 10:07:23 pozo kernel: Accounting suspended > >>>>Dec 6 10:07:38 pozo kernel: Accounting resumed > >>>>Dec 6 10:12:23 pozo kernel: Accounting suspended > >>>>Dec 6 10:12:38 pozo kernel: Accounting resumed > >>>>Dec 6 10:12:53 pozo kernel: Accounting suspended > >>> > >>>Ditto. Running accton all by itself to turn off accounting stops > >>>these cycles from occuring (Hardly a fix as you end up without logs > >>>to run reports from). > >> > >>It's a safety device that prevents accounting records from filling up > >>your hard drive in the event of forkbombs, configure scripts or other > >>things that cause high process turnover. It's controlled by the > >>following sysctls: > >> > >>kern.acct_chkfreq: frequency for checking the free space (seconds) > >>kern.acct_resume: percentage of free disk space above which accounting = resumes > >>kern.acct_suspend: percentage of free disk space below which accounting= stops > > > >Noted. I am at a loss to see which of my filesystem it believes is runni= ng out of space. /var, the logical choice is not even at 10%: > > > >bling# df -h > >Filesystem Size Used Avail Capacity Mounted on > >/dev/ad4s1a 248M 125M 103M 55% / > >devfs 1.0K 1.0K 0B 100% /dev > >procfs 4.0K 4.0K 0B 100% /proc > >/dev/ad4s1d 248M 14K 228M 0% /tmp > >/dev/ad4s1e 3.9G 307M 3.3G 8% /var > >/dev/ad4s1f 180G 6.1G 159G 4% /usr > >/dev/ad6s1d 180G 20G 145G 12% /mnt/misc > >/dev/amrd0a 265G 42G 202G 17% /mnt/amrd0a > >/dev/ad0 226G 111G 97G 53% /mnt/backups > >devfs 1.0K 1.0K 0B 100% /var/named/dev > > > >Thanks! > >Andy >=20 > Same here I have over 19Gigs of free space. > It's something else a kernel from last Friday does not do this. Same problem here. --=20 Rionda aka Matteo Riondato GUFI Staff Member (http://www.gufi.org) FreeSBIE Developer (http://www.freesbie.org) BSD-FAQ-it Main Developer (http://utenti.gufi.org/~rionda) Sent from: kaiser.sig11.org running FreeBSD-6.0-CURRENT --=-cwEIIK2HmDT//hYD5lj1 Content-Type: application/pgp-signature; name=signature.asc Content-Description: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBuhco2Mp4pR7Fa+wRApNZAKDAabbnYJH4ZVU3TIEiBIYJKxGjzwCgjeNF s2vyKYPXoeL4Yb/AypNvr58= =m20M -----END PGP SIGNATURE----- --=-cwEIIK2HmDT//hYD5lj1-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 21:42:42 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6CC216A4CE for ; Fri, 10 Dec 2004 21:42:42 +0000 (GMT) Received: from vsmtp3.tin.it (vsmtp3alice.tin.it [212.216.176.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F49943D48 for ; Fri, 10 Dec 2004 21:42:42 +0000 (GMT) (envelope-from rionda@gufi.org) Received: from kaiser.sig11.org (82.52.116.120) by vsmtp3.tin.it (7.0.027) id 41B2BD6A00239F03 for freebsd-current@freebsd.org; Fri, 10 Dec 2004 22:42:42 +0100 Received: from localhost.localdomain (localhost [127.0.0.1]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by kaiser.sig11.org (Postfix) with ESMTP id A7FA3620D for ; Fri, 10 Dec 2004 22:42:40 +0100 (CET) From: Matteo Riondato To: freebsd-current@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-sWboaQ3qe/HB/HpuNAJK" Date: Fri, 10 Dec 2004 22:42:40 +0100 Message-Id: <1102714960.773.5.camel@kaiser.sig11.org> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port Subject: make fetchindex broken in -CURRENT? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 21:42:42 -0000 --=-sWboaQ3qe/HB/HpuNAJK Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi folks,=20 from today Icannot get ports INDEX anymore: kaiser#pwd /usr/ports kaiser#make fetchindex fetch: http://www.FreeBSD.org/ports/INDEX-6.bz2: Not Found *** Error code 1 Stop in /usr/ports. kaiser#=20 Perhaps it should fetch INDEX-5.bz2 or a INDEX-6.bz2 should be created. Best Regards --=20 Rionda aka Matteo Riondato GUFI Staff Member (http://www.gufi.org) FreeSBIE Developer (http://www.freesbie.org) BSD-FAQ-it Main Developer (http://utenti.gufi.org/~rionda) Sent from: kaiser.sig11.org running FreeBSD-6.0-CURRENT --=-sWboaQ3qe/HB/HpuNAJK Content-Type: application/pgp-signature; name=signature.asc Content-Description: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBuhhQ2Mp4pR7Fa+wRAv6yAJ9j+dZQ4acj9FBEeJBppVapW27VXACfe4W4 7aA40tPqgFxr3BdOOf8cz2g= =UQx4 -----END PGP SIGNATURE----- --=-sWboaQ3qe/HB/HpuNAJK-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 21:45:24 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A8B616A4CE for ; Fri, 10 Dec 2004 21:45:24 +0000 (GMT) Received: from vsmtp3.tin.it (vsmtp3alice.tin.it [212.216.176.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F13B43D4C for ; Fri, 10 Dec 2004 21:45:24 +0000 (GMT) (envelope-from rionda@gufi.org) Received: from kaiser.sig11.org (82.52.116.120) by vsmtp3.tin.it (7.0.027) id 41B2BD6A0023A1F9 for freebsd-current@freebsd.org; Fri, 10 Dec 2004 22:45:24 +0100 Received: from localhost.localdomain (localhost [127.0.0.1]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by kaiser.sig11.org (Postfix) with ESMTP id ED533620D; Fri, 10 Dec 2004 22:45:22 +0100 (CET) From: Matteo Riondato To: Andrey Chernov In-Reply-To: <20041209211808.GA2477@nagual.pp.ru> References: <20041209211808.GA2477@nagual.pp.ru> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-TQzpyQoMxJZil3YfAL36" Date: Fri, 10 Dec 2004 22:45:22 +0100 Message-Id: <1102715122.773.9.camel@kaiser.sig11.org> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port cc: freebsd-current@freebsd.org Subject: Re: New kernel netgraph warning with recent -current: PPPoE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 21:45:24 -0000 --=-TQzpyQoMxJZil3YfAL36 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Andrey Chernov wrote: > Just start ppp as usual, with =20 > set device PPPoE:fxp0 > in /etc/ppp/ppp.conf and got kernel warning now: > WARNING: attempt to net_add_domain(netgraph) after domainfinalize() >=20 > Month old -current don't say this. Same problem here with a world+kernel from today. I think it's related to this commit: glebius 2004-12-08 13:27:55 UTC FreeBSD src repository Modified files: sys/netgraph ng_pppoe.c=20 Log: - Use ng_callout() instead of timeout() - remove spl(9) calls Tested by: Ilya Pizik Approved by: julian (mentor) =20 Revision Changes Path 1.70 +23 -30 src/sys/netgraph/ng_pppoe.c Best Regards --=20 Rionda aka Matteo Riondato GUFI Staff Member (http://www.gufi.org) FreeSBIE Developer (http://www.freesbie.org) BSD-FAQ-it Main Developer (http://utenti.gufi.org/~rionda) Sent from: kaiser.sig11.org running FreeBSD-6.0-CURRENT --=-TQzpyQoMxJZil3YfAL36 Content-Type: application/pgp-signature; name=signature.asc Content-Description: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBuhjy2Mp4pR7Fa+wRAkZqAJwP4DlzTO6wx8jBEZ+jS/nPC7pD0ACdFVcz b6abFFTNly1E1KexNY1gIfk= =4XWj -----END PGP SIGNATURE----- --=-TQzpyQoMxJZil3YfAL36-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 21:56:15 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 675A916A4CE for ; Fri, 10 Dec 2004 21:56:15 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BF2443D53 for ; Fri, 10 Dec 2004 21:56:15 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 3DAB1512C8; Fri, 10 Dec 2004 14:03:00 -0800 (PST) Date: Fri, 10 Dec 2004 14:03:00 -0800 From: Kris Kennaway To: Matteo Riondato Message-ID: <20041210220259.GA23586@xor.obsecurity.org> References: <1102714960.773.5.camel@kaiser.sig11.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZPt4rx8FFjLCG7dd" Content-Disposition: inline In-Reply-To: <1102714960.773.5.camel@kaiser.sig11.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org Subject: Re: make fetchindex broken in -CURRENT? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 21:56:15 -0000 --ZPt4rx8FFjLCG7dd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 10, 2004 at 10:42:40PM +0100, Matteo Riondato wrote: > Hi folks,=20 > from today Icannot get ports INDEX anymore: >=20 > kaiser#pwd > /usr/ports > kaiser#make fetchindex > fetch: http://www.FreeBSD.org/ports/INDEX-6.bz2: Not Found > *** Error code 1 >=20 > Stop in /usr/ports. > kaiser#=20 >=20 > Perhaps it should fetch INDEX-5.bz2 or a INDEX-6.bz2 should be created. Already asked and answered; waiting for webmaster@ Kris --ZPt4rx8FFjLCG7dd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBuh0TWry0BWjoQKURAqgTAJ98+V7b8VFtegsL5ymcPcFxPV1nNQCgk0kI VY0C3+xDAS88TA+gg9a7pFU= =zdRx -----END PGP SIGNATURE----- --ZPt4rx8FFjLCG7dd-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 21:59:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9387216A4CE for ; Fri, 10 Dec 2004 21:59:56 +0000 (GMT) Received: from smtp104.rog.mail.re2.yahoo.com (smtp104.rog.mail.re2.yahoo.com [206.190.36.82]) by mx1.FreeBSD.org (Postfix) with SMTP id 0A38143D2D for ; Fri, 10 Dec 2004 21:59:56 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from unknown (HELO cpe000103d44c07-cm000f9f7ae88c.cpe.net.cable.rogers.com) (mikej@69.193.222.195 with login) by smtp104.rog.mail.re2.yahoo.com with SMTP; 10 Dec 2004 21:52:53 -0000 Received: from 207.219.213.163 (proxying for unknown) (SquirrelMail authenticated user mikej); by cpe000103d44c07-cm000f9f7ae88c.cpe.net.cable.rogers.com with HTTP; Fri, 10 Dec 2004 16:52:43 -0500 (EST) Message-ID: <47703.207.219.213.163.1102715563.squirrel@207.219.213.163> In-Reply-To: <1102714960.773.5.camel@kaiser.sig11.org> References: <1102714960.773.5.camel@kaiser.sig11.org> Date: Fri, 10 Dec 2004 16:52:43 -0500 (EST) From: "Mike Jakubik" To: "Matteo Riondato" User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal cc: freebsd-current@freebsd.org Subject: Re: make fetchindex broken in -CURRENT? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 21:59:56 -0000 Matteo Riondato said: > Hi folks, > from today Icannot get ports INDEX anymore: > > kaiser#pwd > /usr/ports > kaiser#make fetchindex > fetch: http://www.FreeBSD.org/ports/INDEX-6.bz2: Not Found > *** Error code 1 > > Stop in /usr/ports. "me too". I noticed this problem yesterday, it was late so i just left it hoping it would get resolved by morning. This used to work on current just fine. From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 22:16:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3CF216A4CE for ; Fri, 10 Dec 2004 22:16:47 +0000 (GMT) Received: from wasley.bl.mmtr.or.jp (wasley.bl.mmtr.or.jp [210.228.173.142]) by mx1.FreeBSD.org (Postfix) with SMTP id 9A3A943D69 for ; Fri, 10 Dec 2004 22:16:44 +0000 (GMT) (envelope-from rushani@bl.mmtr.or.jp) Received: (qmail 23981 invoked from network); 11 Dec 2004 07:16:43 +0900 Received: from unknown (HELO localhost) (210.165.212.57) by wasley.bl.mmtr.or.jp with SMTP; 11 Dec 2004 07:16:43 +0900 Date: Sat, 11 Dec 2004 07:15:58 +0900 (JST) Message-Id: <20041211.071558.112592739.rushani@bl.mmtr.or.jp> To: sam@errno.com From: Hideyuki KURASHINA In-Reply-To: <41B9454F.9080903@errno.com> References: <200412081744.27539.sam@errno.com> <20041209.225041.63112571.rushani@bl.mmtr.or.jp> <41B9454F.9080903@errno.com> X-URL: http://www.rushani.jp/ X-PGP-Public-Key: http://www.rushani.jp/rushani.asc X-PGP-Fingerprint: A052 6F98 6146 6FE3 91E2 DA6B F2FA 2088 439A DC57 X-RC5-72-Stats: http://stats.distributed.net/participant/psummary.php?project_id=8&id=432320 X-Mailer: Mew version 4.1.52 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: WEP does not work? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 22:16:47 -0000 Hi, >>> On Thu, 09 Dec 2004 22:42:23 -0800, Sam Leffler said: > Hideyuki KURASHINA wrote: > >>>>On Wed, 8 Dec 2004 17:44:27 -0800, Sam Leffler said: > >>On Wednesday 08 December 2004 05:00 pm, Hideyuki KURASHINA wrote: > > Just curiosity, `hw' MIBs print both regdomain and countrycode are 0. > > hw.ath mib entries define values used to initialize each new ath device. > You cannot set regdomain (yet) but countrycode can be overridden by > setting hw.ath.countrycode before loading a device. Thanks for clarification. I'm in Japan, so put following line hw.ath.countrycode=392 into /boot/loader.conf. However, after reboot sysctl says % sysctl hw.ath.countrycode dev.ath.0.countrycode hw.ath.countrycode: 392 dev.ath.0.countrycode: 395 I think dev.ath.0.countrycode will be same value as hw.ath.countrycode, but it won't. > > I tried > > > > # /sbin/ifconfig ath0 ssid MY-SSID wepmode on weptxkey 1 wepkey 1:0x01234567890123456789012345 wepkey 2:- wepkey 3:- wepkey 4:- media autoselect mode 11b > > > > but nothing changed (default router is still not reachable). > > > > I'll try to look tomorrow. I have a patch for fixing wep with ndis that > I need to review and this is probably the same thing. Is this patch included src/sys/net80211/ieee80211_ioctl.c in its rev. 1.15? I also tried this one, but no luck here. -- rushani From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 23:13:43 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF49316A4CE for ; Fri, 10 Dec 2004 23:13:43 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C5FE43D5F for ; Fri, 10 Dec 2004 23:13:43 +0000 (GMT) (envelope-from clint@0lsen.net) Received: from 0lsen.net ([24.20.127.157]) by comcast.net (sccrmhc12) with ESMTP id <2004121023134201200ioerfe>; Fri, 10 Dec 2004 23:13:42 +0000 Received: by 0lsen.net (Postfix, from userid 1001) id BB6A2178FC; Fri, 10 Dec 2004 15:13:41 -0800 (PST) Date: Fri, 10 Dec 2004 15:13:41 -0800 From: Clint Olsen To: current@freebsd.org Message-ID: <20041210231341.GA14072@0lsen.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Organization: NULlsen Network X-Disclaimer: Mutt Bites! Subject: Truss issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 23:13:44 -0000 So, I used to be able to run truss. Now I get: truss: cannot open /proc/14071/mem: No such file or directory belle# truss: cannot open /proc/curproc/mem: No such file or directory FreeBSD belle.0lsen.net 5.3-STABLE FreeBSD 5.3-STABLE #8: Wed Nov 3 18:46:55 PST 2004 root@belle.0lsen.net:/usr/obj/usr/src/sys/GENERIC i386 -Clint From owner-freebsd-current@FreeBSD.ORG Fri Dec 10 23:52:27 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3EB8116A4CE for ; Fri, 10 Dec 2004 23:52:27 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B4D043D60 for ; Fri, 10 Dec 2004 23:52:27 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 0E4AE72DF4; Fri, 10 Dec 2004 15:52:27 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 0BBD872DD4; Fri, 10 Dec 2004 15:52:27 -0800 (PST) Date: Fri, 10 Dec 2004 15:52:27 -0800 (PST) From: Doug White To: =?ISO-8859-1?Q?Crist=F3v=E3o_Dalla_Costa?= In-Reply-To: <41B665AF.7060509@smsweb.com.br> Message-ID: <20041210154536.T63382@carver.gumbysoft.com> References: <41B665AF.7060509@smsweb.com.br> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE cc: freebsd-current@freebsd.org Subject: Re: installing 5.3 on Promise FastTrack 378 and Intel raid controllers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Dec 2004 23:52:27 -0000 On Wed, 8 Dec 2004, [ISO-8859-1] Crist=F3v=E3o Dalla Costa wrote: > We got a new P4 server today with an Asus PC-DL deluxe motherboard w/ > Intel 875P chipset which we were disappointed to find sucks with > respect to the RAID controllers. > > We managed to boot the FreeBSD installation using floppies, and when we > get to the partitioning screen we are shown 5 disks, while we actually > only have four (4 serial ata 120 GB drives). We configured two in raid-1 > and two in raid-0 in each of the raid controllers, and all disks that > appear in the setup are 120 GB while we were expecting to find a 240 GB > one corresponding to the raid-0 setup. You set up the arrays in the BIOS prior to booting FreeBSD? If they were detected you should have a number of ar# devices to choose from. The Promise controllers tend to be better supported than other ATA RAID variants, but FreeBSD has to rely on the RAID metadata stored on the disk. BIOS vendors are free to change the metadata format, and obviously FreeBSD has no way of knowing whether a given system is using one of these custom formats. I would suggest trying to boot in verbose mode (boot -v) and look for the metadata probes and see if it is complaining about a specific one. You might also check that FreeBSD is actually detecting your Promise controller as RAID capable or if its just showing up as a generic ATA controller. If you are just doing simple mirroring you can use atacontrol to set up FreeBSD-style ATA RAID partitions. The RAID controller BIOS won't know whats going on but it will otherwise work. Boot the install CD then go into the fixit menu and mount CD #2. You will then have access to the atacontrol program to set up the volumes. Once done there, boot off the install CD again and the ar devices should appear. Once you get installed post the output of 'dmesg' and 'pciconf -lv'; these may help in debugging the issue. --=20 Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 00:01:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA48516A4CE for ; Sat, 11 Dec 2004 00:01:31 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7961C43D31 for ; Sat, 11 Dec 2004 00:01:31 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 710EC72DD4; Fri, 10 Dec 2004 16:01:31 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 6EE8972DCB; Fri, 10 Dec 2004 16:01:31 -0800 (PST) Date: Fri, 10 Dec 2004 16:01:31 -0800 (PST) From: Doug White To: Krzysztof Kowalik In-Reply-To: <20041209172941.GA29369@uci.agh.edu.pl> Message-ID: <20041210155518.O63382@carver.gumbysoft.com> References: <20041207234840.7287cdf4@maya.liquidx.org> <1102506431.1090.8.camel@taxman> <41B6ED4E.6030301@fer.hr> <20041209172941.GA29369@uci.agh.edu.pl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: FreeBSD sound distortion problems with SB Live! fixed with PREEMPTION X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 00:01:31 -0000 On Thu, 9 Dec 2004, Krzysztof Kowalik wrote: > Ivan Voras [ivoras@fer.hr] wrote: > > [...] > > Not exactly a freeze, but PREEMPTION doesn't help me at all with SB Live > > (slowdowns, stuttering sound, etc.), especially with large amounts of > > filesystem operations (this is 5-stable). > > Exactly. I tried to use both emu10k1 and emu10kx drivers, with kernel > with and without PREEMPTION, and both 5.x and 6.0 serie did behave same. > Intensive I/O made the system quite unusable, and it was not only a > sound-related issue, but a general one -- slow, lagging mouse in X, etc. I purchased a SBLive 5.1 and ran tests with it in a Dell PowerEdge 1750 (2x2.4GHz Xeon) the last time we had complaints about sound jitteryness and I wasn't able to reproduce it, even with heavy buildworld load. Guess its time to pull the card out and give it another try (after I just pulled it out of the machine yesterday...) -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 00:03:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A4B716A4CE for ; Sat, 11 Dec 2004 00:03:22 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6092443D5E for ; Sat, 11 Dec 2004 00:03:22 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 825CF512C8; Fri, 10 Dec 2004 16:10:08 -0800 (PST) Date: Fri, 10 Dec 2004 16:10:08 -0800 From: Kris Kennaway To: Clint Olsen Message-ID: <20041211001008.GA96467@xor.obsecurity.org> References: <20041210231341.GA14072@0lsen.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qDbXVdCdHGoSgWSk" Content-Disposition: inline In-Reply-To: <20041210231341.GA14072@0lsen.net> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: Truss issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 00:03:22 -0000 --qDbXVdCdHGoSgWSk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 10, 2004 at 03:13:41PM -0800, Clint Olsen wrote: > So, I used to be able to run truss. Now I get: >=20 > truss: cannot open /proc/14071/mem: No such file or directory > belle# truss: cannot open /proc/curproc/mem: No such file or directory Because you don't have procfs mounted? Kris --qDbXVdCdHGoSgWSk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBujrgWry0BWjoQKURArqrAKC46VRtIampyXt9L+QUgTZic3YxiwCfdgJO a/9fonkXyjjXeUtfzvlYGvA= =lqNM -----END PGP SIGNATURE----- --qDbXVdCdHGoSgWSk-- From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 00:05:34 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 923CE16A4CE for ; Sat, 11 Dec 2004 00:05:34 +0000 (GMT) Received: from galaxy.uci.agh.edu.pl (galaxy.uci.agh.edu.pl [149.156.96.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id A79AC43D39 for ; Sat, 11 Dec 2004 00:05:33 +0000 (GMT) (envelope-from kkowalik@uci.agh.edu.pl) Received: by galaxy.uci.agh.edu.pl (Postfix, from userid 1001) id 54977AF45E; Sat, 11 Dec 2004 01:05:32 +0100 (CET) Date: Sat, 11 Dec 2004 01:05:32 +0100 From: Krzysztof Kowalik To: Doug White Message-ID: <20041211000532.GA23501@uci.agh.edu.pl> References: <20041207234840.7287cdf4@maya.liquidx.org> <1102506431.1090.8.camel@taxman> <41B6ED4E.6030301@fer.hr> <20041209172941.GA29369@uci.agh.edu.pl> <20041210155518.O63382@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041210155518.O63382@carver.gumbysoft.com> cc: current@freebsd.org Subject: Re: FreeBSD sound distortion problems with SB Live! fixed with PREEMPTION X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 00:05:34 -0000 Doug White [dwhite@gumbysoft.com] wrote: > I purchased a SBLive 5.1 and ran tests with it in a Dell PowerEdge 1750 > (2x2.4GHz Xeon) the last time we had complaints about sound jitteryness > and I wasn't able to reproduce it, even with heavy buildworld load. > [...] For me, untaring firefox's source did the trick. -- Krzysztof Kowalik | () ASCII Ribbon Campaign Computer Center, AGH UST | /\ Support plain text e-mail From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 00:23:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2248716A4CE; Sat, 11 Dec 2004 00:23:58 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A8F143D46; Sat, 11 Dec 2004 00:23:58 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id EB17372DD4; Fri, 10 Dec 2004 16:23:57 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id E6B1C72DCB; Fri, 10 Dec 2004 16:23:57 -0800 (PST) Date: Fri, 10 Dec 2004 16:23:57 -0800 (PST) From: Doug White To: Kris Kennaway In-Reply-To: <20041208171947.GA46271@xor.obsecurity.org> Message-ID: <20041210161650.I63382@carver.gumbysoft.com> References: <200412081205.39354.mi+mx@aldan.algebra.com> <20041208171947.GA46271@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Mikhail Teterin cc: freebsd-current@FreeBSD.org cc: freebsd-amd64@FreeBSD.org cc: ade@FreeBSD.org Subject: Re: new TCL vs. current-6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 00:23:58 -0000 On Wed, 8 Dec 2004, Kris Kennaway wrote: > On Wed, Dec 08, 2004 at 12:05:38PM -0500, Mikhail Teterin wrote: > > Three of my TCL-based ports fail now on amd64 running current-6. All failures > > occur, when an attempt is made to use the TCL-interpreter -- either to run > > the port's self-tests, or to generate the manual pages. The failures are > > either "Floating point exceptions" or "Segmentation faults" and appear to > > only happen on amd64 (may be, on ia64 as well): > > > > http://people.freebsd.org/~fenner/errorlogs/mi%40aldan.algebra.com.html > > > > Can anyone confirm being able to use freshly built TCL on amd64 _at all_? > > > > My ports did not change in months -- what could be wrong with TCL and/or > > amd64? > > Peter speculated a problem when the world is built with -O2 (with or > without -fno-strict-aliasing). I haven't been able to confirm this by > testing with a world built with -O, because I only have one working > amd64 package builder. A quick Makefile look and gdb run finds it taking SIGFPE in strtod(). The tcl build is also very odd since it seems to apply CFLAGS twice like: cc $CFLAGS -O $CFLAGS ... I haven't gone looking for why, just noticed it during the build. This is on a machine built with -O2. I'll kick off an -O build now and see what happens. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 00:40:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBBBE16A4CF for ; Sat, 11 Dec 2004 00:40:41 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E93B43D48 for ; Sat, 11 Dec 2004 00:40:41 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iBB0edst051504; Fri, 10 Dec 2004 16:40:39 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iBB0ecB0051503; Fri, 10 Dec 2004 16:40:38 -0800 (PST) (envelope-from obrien) Date: Fri, 10 Dec 2004 16:40:38 -0800 From: "David O'Brien" To: Matt Rowley Message-ID: <20041211004038.GC50516@dragon.nuxi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 5.3 and Adaptec raidutils (again) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 00:40:41 -0000 On Mon, Dec 06, 2004 at 05:49:19PM -0500, Matt Rowley wrote: > On 11/04/04, Scott Long wrote: > >Ah, it is a BSD-style license. However, someone will have to take a > >careful look through each file to check for consistency here. Any > >volunteers? > > I pulled down I20-on-linux's raidutils tarball and went through their > license headers. I don't follow the license concerns since this is a port... Someone please educated me. In order for the asr(4) utilities to work under FreeBSD 5.x someone just needs to convert the ports/sysutils/asr-utils port I made to build from sources as a first step -- patch submission welcomed. And then to patch the sources to catch up with the changes in asr(4) that happened from RELENG_4 to RELENG_5. Simple huh? -- -- David (obrien@FreeBSD.org) From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 00:45:11 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEE2516A4CE for ; Sat, 11 Dec 2004 00:45:11 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75A8F43D46 for ; Sat, 11 Dec 2004 00:45:11 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 67D6372DF8; Fri, 10 Dec 2004 16:45:11 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 61B8672DCB; Fri, 10 Dec 2004 16:45:11 -0800 (PST) Date: Fri, 10 Dec 2004 16:45:11 -0800 (PST) From: Doug White To: Michal Suszko In-Reply-To: <20041208194721.GB1571@dry.pl> Message-ID: <20041210164407.E63382@carver.gumbysoft.com> References: <20041208194721.GB1571@dry.pl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: deadlocks in recent 6-CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 00:45:11 -0000 On Wed, 8 Dec 2004, Michal Suszko wrote: > > Since switching to PF (few weeks ago) I'm frequently experiencing deadlocks. > breaking to DDB works, and ps shows lock in PF, like here: Is it deadlocks or just going really slowly? You have witness enabled which will exact a high penalty on system performance. Does the problem clear up if you do 'sysctl debug.witness.watch=0"? > 43273 c1ee57e0 1001 42753 43273 0004002 [LOCK pf task mtx c1c45040] dia > > Setting debug.mpsafenet to 0 helps a little (system runs without > deadlock for few days) but doesn't eliminate it. > > PREEMPTION is on > > WITNESS show two kinds of LOR's: > > 1st 0xc1888414 inp (tcpinp) @ /usr/src/sys/netinet/tcp_syncache.c:1086 > 2nd 0xc06b9400 pf task mtx (pf task mtx) @ /usr/src/sys/contrib/pf/net/pf.c:5891 > KDB: stack backtrace: > witness_checkorder(c06b9400,9,c0668a25,1703,7) at witness_checkorder+0x388 > _mtx_lock_flags(c06b9400,0,c0668a25,1703,cbc9c8f8) at _mtx_lock_flags+0x37 > pf_test(2,c15ce000,cbc9ca08,c1888384,c163cba0) at pf_test+0x72 > pf_check_out(0,cbc9ca08,c15ce000,2,c1888384) at pf_check_out+0x4e > pfil_run_hooks(c06eafe0,cbc9ca94,c15ce000,2,c1888384) at pfil_run_hooks+0x145 > ip_output(c16bad00,0,cbc9ca60,0,0) at ip_output+0x299 > syncache_respond(cbc9cb20,c06eba40,1c,8,78) at syncache_respond+0x26a > syncache_add(cbc9cbac,cbc9cbfc,c17a8034,cbc9cba8,c1773b00) at syncache_add+0x428 > tcp_input(c1773b00,14,c15ce000,1,0) at tcp_input+0x1a87 > ip_input(c1773b00,0,c06797c5,e8,18) at ip_input+0xd5 > netisr_processqueue(cbc9ccdc,80246,c06bf1a0,8,c14f3c40) at netisr_processqueue+0x15 > swi_net(0,0,c0670763,257,0) at swi_net+0x9f > ithread_loop(c14fa500,cbc9cd48,c06705b6,318,c14fa500) at ithread_loop+0x1d2 > fork_exit(c04d53e0,c14fa500,cbc9cd48) at fork_exit+0x70 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0x1, eip = 0, esp = 0xcbc9cd7c, ebp = 0 --- > > 1st 0xc06eb44c tcp (tcp) @ /usr/src/sys/netinet/tcp_input.c:615 > 2nd 0xc06b9400 pf task mtx (pf task mtx) @ /usr/src/sys/contrib/pf/net/pf.c:5891 > KDB: stack backtrace: > witness_checkorder(c06b9400,9,c0668a25,1703,0) at witness_checkorder+0x388 > _mtx_lock_flags(c06b9400,0,c0668a25,1703,c04e1dc9) at _mtx_lock_flags+0x37 > pf_test(2,c16cf014,cbc9ca7c,0,c163cba0) at pf_test+0x72 > pf_check_out(0,cbc9ca7c,c16cf014,2,0) at pf_check_out+0x4e > pfil_run_hooks(c06eafe0,cbc9cb08,c16cf014,2,0) at pfil_run_hooks+0x145 > ip_output(c16b6a00,0,cbc9cad4,0,0,0,0,0,c06a495c,c8) at ip_output+0x299 > tcp_respond(0,c16b6a34,c16b6a48,c16b6a00,e5623f88) at tcp_respond+0x16e > tcp_input(c16b6a00,14,c16cf014,1,0) at tcp_input+0x91e > ip_input(c16b6a00,0,c06797c5,e8,18) at ip_input+0xd5 > netisr_processqueue(cbc9ccdc,80246,c06bf1a0,8,c14f3c40) at netisr_processqueue+0x15 > swi_net(0,0,c0670763,257,0) at swi_net+0x9f > ithread_loop(c14fa500,cbc9cd48,c06705b6,318,c14fa500) at ithread_loop+0x1d2 > fork_exit(c04d53e0,c14fa500,cbc9cd48) at fork_exit+0x70 > fork_trampoline() at fork_trampoline+0x8 > > I can provide core dump along with kernel.debug and configuration files. > > > > Michal > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 00:46:09 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BA7516A4CE for ; Sat, 11 Dec 2004 00:46:09 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E3D143D5A for ; Sat, 11 Dec 2004 00:46:09 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 665F172DF8; Fri, 10 Dec 2004 16:46:09 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 6493A72DCB; Fri, 10 Dec 2004 16:46:09 -0800 (PST) Date: Fri, 10 Dec 2004 16:46:09 -0800 (PST) From: Doug White To: Michal Suszko In-Reply-To: <20041210164407.E63382@carver.gumbysoft.com> Message-ID: <20041210164540.H63382@carver.gumbysoft.com> References: <20041208194721.GB1571@dry.pl> <20041210164407.E63382@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: deadlocks in recent 6-CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 00:46:09 -0000 Oops, ignore me. Didn't see that witness was enabled afterwards. > > PREEMPTION is on This is known to cause problems. You enable it at your own risk. > > WITNESS show two kinds of LOR's: > > > > 1st 0xc1888414 inp (tcpinp) @ /usr/src/sys/netinet/tcp_syncache.c:1086 > > 2nd 0xc06b9400 pf task mtx (pf task mtx) @ /usr/src/sys/contrib/pf/net/pf.c:5891 > > KDB: stack backtrace: > > witness_checkorder(c06b9400,9,c0668a25,1703,7) at witness_checkorder+0x388 > > _mtx_lock_flags(c06b9400,0,c0668a25,1703,cbc9c8f8) at _mtx_lock_flags+0x37 > > pf_test(2,c15ce000,cbc9ca08,c1888384,c163cba0) at pf_test+0x72 > > pf_check_out(0,cbc9ca08,c15ce000,2,c1888384) at pf_check_out+0x4e > > pfil_run_hooks(c06eafe0,cbc9ca94,c15ce000,2,c1888384) at pfil_run_hooks+0x145 > > ip_output(c16bad00,0,cbc9ca60,0,0) at ip_output+0x299 > > syncache_respond(cbc9cb20,c06eba40,1c,8,78) at syncache_respond+0x26a > > syncache_add(cbc9cbac,cbc9cbfc,c17a8034,cbc9cba8,c1773b00) at syncache_add+0x428 > > tcp_input(c1773b00,14,c15ce000,1,0) at tcp_input+0x1a87 > > ip_input(c1773b00,0,c06797c5,e8,18) at ip_input+0xd5 > > netisr_processqueue(cbc9ccdc,80246,c06bf1a0,8,c14f3c40) at netisr_processqueue+0x15 > > swi_net(0,0,c0670763,257,0) at swi_net+0x9f > > ithread_loop(c14fa500,cbc9cd48,c06705b6,318,c14fa500) at ithread_loop+0x1d2 > > fork_exit(c04d53e0,c14fa500,cbc9cd48) at fork_exit+0x70 > > fork_trampoline() at fork_trampoline+0x8 > > --- trap 0x1, eip = 0, esp = 0xcbc9cd7c, ebp = 0 --- > > > > 1st 0xc06eb44c tcp (tcp) @ /usr/src/sys/netinet/tcp_input.c:615 > > 2nd 0xc06b9400 pf task mtx (pf task mtx) @ /usr/src/sys/contrib/pf/net/pf.c:5891 > > KDB: stack backtrace: > > witness_checkorder(c06b9400,9,c0668a25,1703,0) at witness_checkorder+0x388 > > _mtx_lock_flags(c06b9400,0,c0668a25,1703,c04e1dc9) at _mtx_lock_flags+0x37 > > pf_test(2,c16cf014,cbc9ca7c,0,c163cba0) at pf_test+0x72 > > pf_check_out(0,cbc9ca7c,c16cf014,2,0) at pf_check_out+0x4e > > pfil_run_hooks(c06eafe0,cbc9cb08,c16cf014,2,0) at pfil_run_hooks+0x145 > > ip_output(c16b6a00,0,cbc9cad4,0,0,0,0,0,c06a495c,c8) at ip_output+0x299 > > tcp_respond(0,c16b6a34,c16b6a48,c16b6a00,e5623f88) at tcp_respond+0x16e > > tcp_input(c16b6a00,14,c16cf014,1,0) at tcp_input+0x91e > > ip_input(c16b6a00,0,c06797c5,e8,18) at ip_input+0xd5 > > netisr_processqueue(cbc9ccdc,80246,c06bf1a0,8,c14f3c40) at netisr_processqueue+0x15 > > swi_net(0,0,c0670763,257,0) at swi_net+0x9f > > ithread_loop(c14fa500,cbc9cd48,c06705b6,318,c14fa500) at ithread_loop+0x1d2 > > fork_exit(c04d53e0,c14fa500,cbc9cd48) at fork_exit+0x70 > > fork_trampoline() at fork_trampoline+0x8 > > > > I can provide core dump along with kernel.debug and configuration files. > > > > > > > > Michal > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > > -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 01:03:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 461D216A4CE for ; Sat, 11 Dec 2004 01:03:46 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1987243D1D for ; Sat, 11 Dec 2004 01:03:46 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id AE69A513A0; Fri, 10 Dec 2004 17:10:32 -0800 (PST) Date: Fri, 10 Dec 2004 17:10:32 -0800 From: Kris Kennaway To: Doug White Message-ID: <20041211011032.GA10749@xor.obsecurity.org> References: <20041208194721.GB1571@dry.pl> <20041210164407.E63382@carver.gumbysoft.com> <20041210164540.H63382@carver.gumbysoft.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl" Content-Disposition: inline In-Reply-To: <20041210164540.H63382@carver.gumbysoft.com> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org cc: Michal Suszko Subject: Re: deadlocks in recent 6-CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 01:03:46 -0000 --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 10, 2004 at 04:46:09PM -0800, Doug White wrote: > Oops, ignore me. Didn't see that witness was enabled afterwards. >=20 > > > PREEMPTION is on >=20 > This is known to cause problems. You enable it at your own risk. Only on ULE, I thought. > > > WITNESS show two kinds of LOR's: If you're getting LORs, chances are good you'll also get deadlocks (that's why lock order reversals are bad). Kris --BXVAT5kNtrzKuDFl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBukkIWry0BWjoQKURArVfAJ9ModcUQDLkXCGXmiYvEJ+7kpYxXACfWYKu PTPA8jYEuexpwurpQ68sNA4= =lwXs -----END PGP SIGNATURE----- --BXVAT5kNtrzKuDFl-- From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 01:19:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DDBF16A4CE for ; Sat, 11 Dec 2004 01:19:56 +0000 (GMT) Received: from pne-smtpout1-sn2.hy.skanova.net (pne-smtpout1-sn2.hy.skanova.net [81.228.8.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A59643D58 for ; Sat, 11 Dec 2004 01:19:55 +0000 (GMT) (envelope-from pawel.worach@telia.com) Received: from [127.0.0.1] (81.225.14.129) by pne-smtpout1-sn2.hy.skanova.net (7.1.026.6) (authenticated as u86211448) id 4199C6960000B697; Sat, 11 Dec 2004 02:19:44 +0100 Message-ID: <41BA4B22.5070403@telia.com> Date: Sat, 11 Dec 2004 02:19:30 +0100 From: Pawel Worach User-Agent: Mozilla Thunderbird 1.0 (X11/20041210) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sam Leffler References: <200412081109.43840.sam@errno.com> <20041209.100008.21874313.rushani@bl.mmtr.or.jp> <200412081744.27539.sam@errno.com> <20041209.225041.63112571.rushani@bl.mmtr.or.jp> <41B9454F.9080903@errno.com> In-Reply-To: <41B9454F.9080903@errno.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: WEP does not work? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 01:19:56 -0000 Sam Leffler wrote: > I'll try to look tomorrow. I have a patch for fixing wep with ndis that > I need to review and this is probably the same thing. I have the same problem on a ThinkPad T41. Device is: ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413) ath0: mem 0xc0210000-0xc021ffff irq 11 at device 2.0 on pci2 ath0: Ethernet address: 00:05:4e:4b:76:13 ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3 Sysctls: dev.ath.0.countrycode: 0 dev.ath.0.regdomain: 97 I tried setting hw.ath.countrycode to 752 (sweden) but the driver complained on boot that it was invalid. It was zero with the old kernel too. The card works fine in ad-hoc mode without wep, if I enable wep it breaks. The funny thing is that on the other end I can see ARP requests but no replies are sent when wep is on (other end is a ~3 weeks old current with a cisco aironet 350 card). "status" claims "associated", everything looks the way it should be. # ifconfig ath0 list chan Channel 1 : 2412 Mhz 11g Channel 48 : 5240* Mhz 11a Channel 2 : 2417 Mhz 11g Channel 52 : 5260* Mhz 11a Channel 3 : 2422 Mhz 11g Channel 56 : 5280* Mhz 11a Channel 4 : 2427 Mhz 11g Channel 60 : 5300* Mhz 11a Channel 5 : 2432 Mhz 11g Channel 64 : 5320* Mhz 11a Channel 6 : 2437 Mhz 11g Channel 100 : 5500* Mhz 11a Channel 7 : 2442 Mhz 11g Channel 104 : 5520* Mhz 11a Channel 8 : 2447 Mhz 11g Channel 108 : 5540* Mhz 11a Channel 9 : 2452 Mhz 11g Channel 112 : 5560* Mhz 11a Channel 10 : 2457 Mhz 11g Channel 116 : 5580* Mhz 11a Channel 11 : 2462 Mhz 11g Channel 120 : 5600* Mhz 11a Channel 12 : 2467* Mhz 11g Channel 124 : 5620* Mhz 11a Channel 13 : 2472* Mhz 11g Channel 128 : 5640* Mhz 11a Channel 14 : 2484* Mhz 11b Channel 132 : 5660* Mhz 11a Channel 34 : 5170* Mhz 11a Channel 136 : 5680* Mhz 11a Channel 36 : 5180* Mhz 11a Channel 140 : 5700* Mhz 11a Channel 38 : 5190* Mhz 11a Channel 149 : 5745* Mhz 11a Channel 40 : 5200* Mhz 11a Channel 153 : 5765* Mhz 11a Channel 42 : 5210* Mhz 11a Channel 157 : 5785* Mhz 11a Channel 44 : 5220* Mhz 11a Channel 161 : 5805* Mhz 11a Channel 46 : 5230* Mhz 11a Channel 165 : 5825* Mhz 11a Ad-Hoc mode without wep: # ifconfig -v ath0 ath0: flags=8843 mtu 1500 inet 192.168.1.200 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::205:4eff:fe4b:7613%ath0 prefixlen 64 scopeid 0x2 ether 00:05:4e:4b:76:13 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect ) status: associated ssid cookie channel 7 (2442) bssid da:00:a4:01:3b:02 authmode OPEN privacy OFF deftxkey UNDEF powersavemode OFF powersavesleep 100 txpowmax 34 txpower 60 rtsthreshold 2312 protmode CTS wme roaming AUTO bintval 100 AC_BE cwmin 4 cwmax 10 aifs 3 txopLimit 0 -acm ack cwmin 4 cwmax 10 aifs 3 txopLimit 0 -acm AC_BK cwmin 4 cwmax 10 aifs 7 txopLimit 0 -acm ack cwmin 4 cwmax 10 aifs 7 txopLimit 0 -acm AC_VI cwmin 3 cwmax 4 aifs 2 txopLimit 94 -acm ack cwmin 3 cwmax 4 aifs 2 txopLimit 94 -acm AC_VO cwmin 2 cwmax 3 aifs 2 txopLimit 47 -acm ack cwmin 2 cwmax 3 aifs 2 txopLimit 47 -acm I also get a couple of these from time to time, could be related to reconfiguration. ath0: device timeout ath0: device timeout ath0: device timeout Another minor thing I noted, when you play around with 'ifconfig ath0 wepmode' it looks like the wepkeys are displayed sometimes and sometimes not afterwards, it seems very random. It it required to set wepkey and wepmode in the same command? -- Pawel From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 01:41:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB9B016A4CE for ; Sat, 11 Dec 2004 01:41:02 +0000 (GMT) Received: from itesec.hsc.fr (itesec.hsc.fr [192.70.106.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31FE243D1D for ; Sat, 11 Dec 2004 01:41:02 +0000 (GMT) (envelope-from yb@sainte-barbe.org) Received: from taz.hsc.fr (taz.hsc.fr [192.70.106.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "taz.hsc.fr", Issuer "HSC CA" (verified OK)) by itesec.hsc.fr (Postfix) with ESMTP id EAF202119D; Sat, 11 Dec 2004 02:41:00 +0100 (CET) Received: by taz.hsc.fr (Postfix, from userid 1001) id 53CEB3FE0; Sat, 11 Dec 2004 02:41:01 +0100 (CET) Date: Sat, 11 Dec 2004 02:41:01 +0100 From: Yann Berthier To: freebsd-current@freebsd.org Message-ID: <20041211014101.GA714@hsc.fr> Mail-Followup-To: freebsd-current@freebsd.org, damien.bergamini@free.fr References: <200412081059.22949.sam@errno.com> <20041210151628.GA33593@vagabond.ma.maison> <20041210160430.GY69536@pcwin002.win.tue.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041210160430.GY69536@pcwin002.win.tue.nl> X-Organization: Herve Schauer Consultants X-Web: http://www.hsc.fr/ X-Operating-System: FreeBSD 6.0-CURRENT User-Agent: Mutt/1.5.6i cc: damien.bergamini@free.fr Subject: Re: HEADSUP: updated net80211 layer committed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 01:41:03 -0000 [cc:ing the main responsible] On Fri, 10 Dec 2004, Stijn Hoop wrote: > On Fri, Dec 10, 2004 at 04:16:28PM +0100, Pierre DAVID wrote: > > This is really a major update! I'm now able to use our 802.11 > > network, with an EAP/TTLS based 802.1X authentication. > > I guess it doesn't yet work with the 'unofficial' ipi/ipw driver? I haven't > tried it yet but I recently acquired an Intel 2200BG to replace my Dell > Broadcom proprietary card. So I guess I'll wait for the iwi/ipw maintainer to > catch up. No hurry, Damien! I'm just anxious! Satisfied users of ipw/iwi seem to pop up every day or so I'm sure that it would be easier for Damien if his drivers were in the tree (more incentives to keep up, at least). Now, that reminds me a recent thread ;) > Great work by Sam though -- this is indeed what I need to get wireless > to work at our university. Indeed ! :) Regards, - yann From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 02:10:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C0AF616A4D3 for ; Sat, 11 Dec 2004 02:10:29 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CE9143D5C for ; Sat, 11 Dec 2004 02:10:28 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iBB2A8xq059474; Sat, 11 Dec 2004 12:40:09 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: "Andrew R. Reiter" Date: Sat, 11 Dec 2004 12:39:57 +1030 User-Agent: KMail/1.7.1 References: <200412101301.06484.doconnor@gsoft.com.au> <41B9D868.20900@errno.com> <20041210120617.S79401@fledge.watson.org> In-Reply-To: <20041210120617.S79401@fledge.watson.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1318519.PnfaltHDn4"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412111240.05112.doconnor@gsoft.com.au> X-Spam-Score: -5.4 () IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: Sam Leffler cc: freebsd-current@freebsd.org Subject: Re: Recent ifconfig changes choke on fwip X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 02:10:30 -0000 --nextPart1318519.PnfaltHDn4 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sat, 11 Dec 2004 03:37, Andrew R. Reiter wrote: > I missed the earlier post, how to reproduce this? I am building world > right now (update from a couple days ago to pickup net80211, some phk > changes, and urmm uhh, oh imp@ changes) so I can test... pending my TI > ieee1394 cbb card works. Pretty easy.. kldload if_fwip ifconfig fwip0 :) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1318519.PnfaltHDn4 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBulb95ZPcIHs/zowRAlsIAJwNlOtYPUa0UVC+s7EVachHq9SHQACfUlsG CUSARKjGPUGbVv2of2rqt6U= =c3Am -----END PGP SIGNATURE----- --nextPart1318519.PnfaltHDn4-- From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 02:34:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9AF6216A4CE for ; Sat, 11 Dec 2004 02:34:54 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56AE943D45 for ; Sat, 11 Dec 2004 02:34:54 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iBB2Yq6Z091607; Fri, 10 Dec 2004 18:34:52 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iBB2Yq27091606; Fri, 10 Dec 2004 18:34:52 -0800 (PST) (envelope-from obrien) Date: Fri, 10 Dec 2004 18:34:52 -0800 From: "David O'Brien" To: Chris Stone Message-ID: <20041211023452.GC74718@dragon.nuxi.com> References: <20041209000200.BD1F616A4F2@hub.freebsd.org> <41B7D294.7020801@Comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41B7D294.7020801@Comcast.net> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-current@freebsd.org Subject: Re: HP D325 Panic Fault Trap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 02:34:54 -0000 On Wed, Dec 08, 2004 at 11:20:36PM -0500, Chris Stone wrote: > I have a new HP D325 minitower with an Athlon XP 3000+ processor, 512 > RAM, 40GB 7200 HD, CD-RW/DVD-Rom. .. > Any ideas, hints, patches, bios settings; anything?? This is an nVidia nForce2 based system. So the ACPI BIOS is FUBARed. With linux you have to use "acpi=oldboot". AFAIK, FreeBSD has no simular handling. -- -- David (obrien@FreeBSD.org) From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 03:00:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB11516A4CE; Sat, 11 Dec 2004 03:00:06 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BF7443D31; Sat, 11 Dec 2004 03:00:06 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id iBB306vb035566; Fri, 10 Dec 2004 22:00:06 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.1/8.13.1) with ESMTP id iBB305tP074529; Fri, 10 Dec 2004 22:00:05 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 989EE7306E; Fri, 10 Dec 2004 22:00:05 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041211030005.989EE7306E@freebsd-current.sentex.ca> Date: Fri, 10 Dec 2004 22:00:05 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/625/Fri Dec 10 12:41:57 2004 clamav-milter version 0.80j on clamscanner2 X-Virus-Status: Clean Subject: [current tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 03:00:07 -0000 TB --- 2004-12-11 01:15:52 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-12-11 01:15:52 - starting CURRENT tinderbox run for i386/i386 TB --- 2004-12-11 01:15:52 - checking out the source tree TB --- 2004-12-11 01:15:52 - cd /home/tinderbox/CURRENT/i386/i386 TB --- 2004-12-11 01:15:52 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-12-11 01:22:20 - building world (CFLAGS=-O2 -pipe) TB --- 2004-12-11 01:22:20 - cd /home/tinderbox/CURRENT/i386/i386/src TB --- 2004-12-11 01:22:20 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-12-11 02:28:42 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-12-11 02:28:42 - cd /home/tinderbox/CURRENT/i386/i386/src TB --- 2004-12-11 02:28:42 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sat Dec 11 02:28:42 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Sat Dec 11 02:45:49 UTC 2004 TB --- 2004-12-11 02:45:49 - generating LINT kernel config TB --- 2004-12-11 02:45:49 - cd /home/tinderbox/CURRENT/i386/i386/src/sys/i386/conf TB --- 2004-12-11 02:45:49 - /usr/bin/make -B LINT TB --- 2004-12-11 02:45:49 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-12-11 02:45:49 - cd /home/tinderbox/CURRENT/i386/i386/src TB --- 2004-12-11 02:45:49 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Dec 11 02:45:49 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -O2 -pipe -I/sys/contrib/dev/acpica -D_KERNEL -DKLD_MODULE -nostdinc -I- -I/sys/contrib/dev/acpica -include /tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -I/tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/LINT -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c: In function `acpi_ibm_attach': /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c:155: error: `_COMPONENT' undeclared (first use in this function) /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c:155: error: (Each undeclared identifier is reported only once /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c:155: error: for each function it appears in.) /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c:155: error: `_THIS_MODULE' undeclared (first use in this function) /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c: In function `acpi_ibm_detach': /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c:260: error: `_Dbg' undeclared (first use in this function) *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src/sys/modules. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/LINT. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. TB --- 2004-12-11 03:00:05 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-12-11 03:00:05 - ERROR: failed to build lint kernel TB --- 2004-12-11 03:00:05 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 03:48:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A9CE16A4CE for ; Sat, 11 Dec 2004 03:48:22 +0000 (GMT) Received: from lakermmtao01.cox.net (lakermmtao01.cox.net [68.230.240.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEFF443D2F for ; Sat, 11 Dec 2004 03:48:21 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.70.32]) by lakermmtao01.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20041211034821.PGW27357.lakermmtao01.cox.net@dolphin.local.net> for ; Fri, 10 Dec 2004 22:48:21 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with SMTP id iBB3mKqq000827 for ; Fri, 10 Dec 2004 21:48:20 -0600 (CST) (envelope-from conrads@cox.net) Date: Fri, 10 Dec 2004 21:48:15 -0600 From: "Conrad J. Sabatier" To: freebsd-current@freebsd.org Message-ID: <20041210214815.12ebd529@dolphin.local.net> X-Mailer: Sylpheed-Claws 0.9.12b (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: df showing weird stats for nfs mounts X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 03:48:22 -0000 [ irrelevant lines snipped ] dolphin:conrads:/usr/home/conrads$ df -H Filesystem Size Used Avail Capacity Mounted on gateway:/mm 83906 30871 0B 100% /mm gateway:/usr/home/ncvs 83906 -456 0B 100% /usr/home/ncvs gateway:/usr/ports/distfiles 83906 -456 0B 100% /usr/ports/distfiles dolphin:conrads:/usr/home/conrads$ ssh gateway df -H Filesystem Size Used Avail Capacity Mounted on /dev/ad0s1f 34G 11G 21G 35% /usr /dev/ad1s1e 79G 71G 3.6G 95% /mm dolphin:conrads:/usr/home/conrads$ uname -a FreeBSD dolphin.local.net 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Fri Dec 10 21:22:39 CST 2004 conrads@dolphin.local.net:/usr/obj/usr/src/sys/CUSTOM amd64 -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 06:30:34 2004 Return-Path: Delivered-To: freebsd-current@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75F4716A4CE for ; Sat, 11 Dec 2004 06:30:34 +0000 (GMT) Received: from area51.capnet.state.tx.us (area51.capnet.state.tx.us [141.198.193.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2909C43D1F for ; Sat, 11 Dec 2004 06:30:34 +0000 (GMT) (envelope-from trorki@area51.capnet.state.tx.us) Received: from area51.capnet.state.tx.us (localhost.capnet.state.tx.us [127.0.0.1])iBB6SEHY037606; Sat, 11 Dec 2004 00:28:14 -0600 (CST) (envelope-from trorki@area51.capnet.state.tx.us) Received: from localhost (stu@localhost)iBB6SEeA037603; Sat, 11 Dec 2004 00:28:14 -0600 (CST) X-Authentication-Warning: area51.capnet.state.tx.us: stu owned process doing -bs Date: Sat, 11 Dec 2004 00:28:14 -0600 (CST) From: trorki@area51.capnet.state.tx.us X-X-Sender: stu@area51.capnet.state.tx.us To: Kris Kennaway In-Reply-To: <20041210205951.GA54091@xor.obsecurity.org> Message-ID: <20041210235009.O37514@area51.capnet.state.tx.us> References: <200412081205.39354.mi+mx@aldan.algebra.com> <20041208180601.T29045@area51.capnet.state.tx.us> <20041210205951.GA54091@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@www.freebsd.org cc: trorki@area51.capnet.state.tx.us Subject: AMD64 -current ISOs and cvsup repository: Was: Re: -current ISOs and update cvsup sites for AMD64? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: trorki@area51.capnet.state.tx.us List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 06:30:34 -0000 On Fri, 10 Dec 2004, Kris Kennaway wrote: > On Fri, Dec 10, 2004 at 10:50:11AM -0600, trorki@area51.capnet.state.tx.us > > I've looked at snapshots.jp.freebsd.org and snapshots.se.freebsd.org > > and can't find a recent snapshot ISO to get -current for AMD64. > > Am I missing the directory, or what? Someone please let me know where > > to get a recent ISO > The above site; talk to the admins about why they're not being > produced (probably it's just an oversight). The last AMD64 -current ISO on snapshots.se and snapshots.jp was in October, if I'm looking at the right directories. A month and a half is hardly an "oversight", since October isn't even in the 6.0 timeframe. Maybe terminology has changed since summer, but all the -current sources peter out at the end of October, and no 6.0 build seems to have ever worked on snapshots.se, to judge from the log files. I'd like some help with AMD64 -current, yes AMD64 6.0-current. Am I making this clear??? I haven't played with -current since before the switch to 6.0 as -current, so the last ISO I used (and still have) is a 5.x-current from July. I want a clean AMD64 6.0-current ISO to start with, and that would presumedly be AFTER November 05, preferably very recent... > >, and where I should point cvsup for the updates. > Updates to what? amd64 isn't different from the other architectures; > you can read the documentation on using and configuring cvsup in the > handbook, and if you have further specific questions then ask them > then. The information isn't IN the handbook, or is obscure. If it was there to read, I wouldn't have asked the list. Duh. Since I mentioned cvsup you might/maybe get the idea that I know how to use it. Duh. Since I can't find the snapshots where they are expected, they might be somewhere else, and I'd probably need to cvsup from somewhere else, too, which is why I asked. Duh. Would somebody that actually uses -current on AMD64 tell me how to get a recent ISO, and which servers are carrying the AMD 6.0-current branch so I can cvsup updates? Please don't reply to the list if you don't know what the hell I'm asking about. stu From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 07:01:35 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 047CA16A4CE for ; Sat, 11 Dec 2004 07:01:35 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id C346A43D6B for ; Sat, 11 Dec 2004 07:01:31 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iBB71HKM063767; Sat, 11 Dec 2004 17:31:17 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org, trorki@area51.capnet.state.tx.us Date: Sat, 11 Dec 2004 17:31:04 +1030 User-Agent: KMail/1.7.1 References: <200412081205.39354.mi+mx@aldan.algebra.com> <20041210205951.GA54091@xor.obsecurity.org> <20041210235009.O37514@area51.capnet.state.tx.us> In-Reply-To: <20041210235009.O37514@area51.capnet.state.tx.us> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart110275828.UIyKImhdzB"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412111731.15897.doconnor@gsoft.com.au> X-Spam-Score: -5.4 () IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: freebsd-current@freebsd.org cc: Kris Kennaway Subject: Re: AMD64 -current ISOs and cvsup repository: Was: Re: -current ISOs and update cvsup sites for AMD64? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 07:01:35 -0000 --nextPart110275828.UIyKImhdzB Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sat, 11 Dec 2004 16:58, trorki@area51.capnet.state.tx.us wrote: > The last AMD64 -current ISO on snapshots.se and snapshots.jp was in > October, if I'm looking at the right directories. A month and a half is > hardly an "oversight", since October isn't even in the 6.0 timeframe. Why not? I don't recall you paying for them to make the snapshot ISOs, so they get m= ade=20 when they can. Maybe if you provided some constructive support about it (eg= =20 hardware, money, bandwidth) they'd be able to produce them more consistentl= y. > Would somebody that actually uses -current on AMD64 tell me > how to get a recent ISO, and which servers are carrying the > AMD 6.0-current branch so I can cvsup updates? > > Please don't reply to the list if you don't know what the hell > I'm asking about. I think your attitude stinks, however you should try a 5.3 release and then= =20 upgrade to -current. Also, chewing out the main ports manager is really demonstrative of your la= ck=20 of clue. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart110275828.UIyKImhdzB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBups75ZPcIHs/zowRAiB2AJ4nUgcCmaA6bl3QxqKESXJU0+vnnQCfbhcW 0lZJfI3TuG1uMytootfYKng= =vioM -----END PGP SIGNATURE----- --nextPart110275828.UIyKImhdzB-- From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 07:44:26 2004 Return-Path: Delivered-To: freebsd-current@www.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D202C16A4CE for ; Sat, 11 Dec 2004 07:44:26 +0000 (GMT) Received: from bsd.ultra-secure.de (bsd.ultra-secure.de [62.146.20.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF84C43D31 for ; Sat, 11 Dec 2004 07:44:25 +0000 (GMT) (envelope-from rainer@ultra-secure.de) Received: (qmail 29666 invoked by uid 1005); 11 Dec 2004 07:44:24 -0000 Received: from rainer@ultra-secure.de by bsd.ultra-secure.de by uid 89 with qmail-scanner-1.22 (clamdscan: 0.75.1. spamassassin: 2.64. Clear:RC:1(217.232.238.2):. Processed in 0.329393 secs); 11 Dec 2004 07:44:24 -0000 Received: from unknown (HELO ?192.168.1.224?) (rainer@ultra-secure.de@217.232.238.2) by bsd.ultra-secure.de with (DHE-RSA-AES256-SHA encrypted) SMTP; 11 Dec 2004 07:44:24 -0000 Message-ID: <41BAA556.5080705@ultra-secure.de> Date: Sat, 11 Dec 2004 08:44:22 +0100 From: Rainer Duffner User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: trorki@area51.capnet.state.tx.us References: <200412081205.39354.mi+mx@aldan.algebra.com> <20041208180601.T29045@area51.capnet.state.tx.us> <20041210205951.GA54091@xor.obsecurity.org> <20041210235009.O37514@area51.capnet.state.tx.us> In-Reply-To: <20041210235009.O37514@area51.capnet.state.tx.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@www.freebsd.org Subject: Re: AMD64 -current ISOs and cvsup repository: Was: Re: -currentISOs and update cvsup sites for AMD64? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 07:44:27 -0000 trorki@area51.capnet.state.tx.us wrote: >On Fri, 10 Dec 2004, Kris Kennaway wrote: > > > >>On Fri, Dec 10, 2004 at 10:50:11AM -0600, trorki@area51.capnet.state.tx.us >> >> > > > >>>I've looked at snapshots.jp.freebsd.org and snapshots.se.freebsd.org >>>and can't find a recent snapshot ISO to get -current for AMD64. >>>Am I missing the directory, or what? Someone please let me know where >>>to get a recent ISO >>> >>> > > > >>The above site; talk to the admins about why they're not being >>produced (probably it's just an oversight). >> >> > >The last AMD64 -current ISO on snapshots.se and snapshots.jp was in >October, if I'm looking at the right directories. A month and a half is >hardly an "oversight", since October isn't even in the 6.0 timeframe. >Maybe terminology has changed since summer, but all the -current >sources peter out at the end of October, and no 6.0 build seems to >have ever worked on snapshots.se, to judge from the log files. >I'd like some help with AMD64 -current, yes AMD64 6.0-current. >Am I making this clear??? > >I haven't played with -current since before the switch to 6.0 >as -current, so the last ISO I used (and still have) is a 5.x-current >from July. > Then I'd update to RELENG_5_3 first, and then cvsup to HEAD. > I want a clean AMD64 6.0-current ISO to start with, and that >would presumedly be AFTER November 05, preferably very recent... > > > >>>, and where I should point cvsup for the updates. >>> >>> > > > >>Updates to what? amd64 isn't different from the other architectures; >>you can read the documentation on using and configuring cvsup in the >>handbook, and if you have further specific questions then ask them >>then. >> >> > >The information isn't IN the handbook, or is obscure. If it was >there to read, I wouldn't have asked the list. Duh. >Since I mentioned cvsup you might/maybe get the idea that I know >how to use it. Duh. > > > You like that word, eh ? ;-) The snapshot-servers have, TTBOMK, nothing to do with the cvsup-servers. >Since I can't find the snapshots where they are expected, >they might be somewhere else, and I'd probably need to cvsup from >somewhere else, too, which is why I asked. Duh. > > That's why Kris talked about the handbook. To an outsider, it is not clear if you are making a fool of yourself or just want to fool around and insult people. Or if you are really a fool ;-) >Would somebody that actually uses -current on AMD64 tell me >how to get a recent ISO, and which servers are carrying the >AMD 6.0-current branch so I can cvsup updates? > >Please don't reply to the list if you don't know what the hell >I'm asking about. > > I'm not using AMD64 (If I had the hardware, I'd use it though) and I'm not using current either (used to, but now it's called 5_3-stable), but it is my understanding that you can just - cvsup to RELENG_5_3 - perhaps cvsup to RELENG_5 - then cvsup to current - with make buildworld etc-cycle between the cvsups. At least, at this point in time, where RELENG_5 and HEAD are not very much different like with RELENG_4 and RELENG_5. You can then make your own snapshot - with an AMD64 it should only take an hour or so ;-) Correct me if my assumptions are wrong. Rainer From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 08:39:09 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7205D16A4CE for ; Sat, 11 Dec 2004 08:39:09 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39D8A43D39 for ; Sat, 11 Dec 2004 08:39:09 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1Cd2mS-000MnM-Gs for freebsd-current@freebsd.org; Sat, 11 Dec 2004 00:39:08 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16826.45612.44509.939434@ran.psg.com> Date: Sat, 11 Dec 2004 00:39:08 -0800 To: FreeBSD Current Subject: dump time message X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 08:39:09 -0000 DUMP: 11.73% done, finished in 0:37 at Sat Dec 11 08:39:42 2004 DUMP: 22.67% done, finished in 0:34 at Sat Dec 11 08:41:12 2004 DUMP: 32.96% done, finished in 0:30 at Sat Dec 11 08:42:36 2004 DUMP: 43.35% done, finished in 0:26 at Sat Dec 11 08:43:14 2004 DUMP: 54.40% done, finished in 0:20 at Sat Dec 11 08:43:03 2004 DUMP: 65.30% done, finished in 0:15 at Sat Dec 11 08:43:02 2004 DUMP: 76.38% done, finished in 0:10 at Sat Dec 11 08:42:55 2004 DUMP: 88.74% done, finished in 0:05 at Sat Dec 11 08:42:10 2004 notice that the time of day is descending! # date Sat Dec 11 08:38:42 UTC 2004 which is correct have i found i time machine? i would desperately love to rewind a few decades. randy From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 08:45:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2285016A4CE for ; Sat, 11 Dec 2004 08:45:22 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7615643D1F for ; Sat, 11 Dec 2004 08:45:21 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iBB8jGaI088158; Sat, 11 Dec 2004 09:45:17 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Randy Bush From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 11 Dec 2004 00:39:08 PST." <16826.45612.44509.939434@ran.psg.com> Date: Sat, 11 Dec 2004 09:45:16 +0100 Message-ID: <88157.1102754716@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: FreeBSD Current Subject: Re: dump time message X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 08:45:22 -0000 In message <16826.45612.44509.939434@ran.psg.com>, Randy Bush writes: > DUMP: 11.73% done, finished in 0:37 at Sat Dec 11 08:39:42 2004 > DUMP: 22.67% done, finished in 0:34 at Sat Dec 11 08:41:12 2004 > DUMP: 32.96% done, finished in 0:30 at Sat Dec 11 08:42:36 2004 > DUMP: 43.35% done, finished in 0:26 at Sat Dec 11 08:43:14 2004 > DUMP: 54.40% done, finished in 0:20 at Sat Dec 11 08:43:03 2004 > DUMP: 65.30% done, finished in 0:15 at Sat Dec 11 08:43:02 2004 > DUMP: 76.38% done, finished in 0:10 at Sat Dec 11 08:42:55 2004 > DUMP: 88.74% done, finished in 0:05 at Sat Dec 11 08:42:10 2004 > >notice that the time of day is descending! That's not the time of day, that's the estimated completion time. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 08:47:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F8BC16A4CE for ; Sat, 11 Dec 2004 08:47:49 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0077B43D5D for ; Sat, 11 Dec 2004 08:47:49 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1Cd2uq-000N1U-9l; Sat, 11 Dec 2004 00:47:48 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16826.46131.792273.632711@ran.psg.com> Date: Sat, 11 Dec 2004 00:47:47 -0800 To: "Poul-Henning Kamp" References: <16826.45612.44509.939434@ran.psg.com> <88157.1102754716@critter.freebsd.dk> cc: FreeBSD Current Subject: Re: dump time message X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 08:47:49 -0000 >> DUMP: 11.73% done, finished in 0:37 at Sat Dec 11 08:39:42 2004 >> DUMP: 22.67% done, finished in 0:34 at Sat Dec 11 08:41:12 2004 >> DUMP: 32.96% done, finished in 0:30 at Sat Dec 11 08:42:36 2004 >> DUMP: 43.35% done, finished in 0:26 at Sat Dec 11 08:43:14 2004 >> DUMP: 54.40% done, finished in 0:20 at Sat Dec 11 08:43:03 2004 >> DUMP: 65.30% done, finished in 0:15 at Sat Dec 11 08:43:02 2004 >> DUMP: 76.38% done, finished in 0:10 at Sat Dec 11 08:42:55 2004 >> DUMP: 88.74% done, finished in 0:05 at Sat Dec 11 08:42:10 2004 >> >> notice that the time of day is descending! > > That's not the time of day, that's the estimated completion time. ! time to get some sleep. sorreeeee. randy From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 09:17:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E44816A4CE; Sat, 11 Dec 2004 09:17:21 +0000 (GMT) Received: from smtp4.wanadoo.fr (smtp4.wanadoo.fr [193.252.22.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1651143D64; Sat, 11 Dec 2004 09:17:21 +0000 (GMT) (envelope-from aurelien.nephtali@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0401.wanadoo.fr (SMTP Server) with SMTP id B34041C002FB; Sat, 11 Dec 2004 10:17:19 +0100 (CET) Received: from [192.168.2.30] (ca-sqy-12-203.w80-8.abo.wanadoo.fr [80.8.65.203]) by mwinf0401.wanadoo.fr (SMTP Server) with ESMTP id 890421C002E8; Sat, 11 Dec 2004 10:17:19 +0100 (CET) Message-ID: <41BABB1E.5000200@wanadoo.fr> Date: Sat, 11 Dec 2004 10:17:18 +0100 From: Aurelien Nephtali User-Agent: Mozilla Thunderbird 0.9 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: curent@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Setting up a "Parallel Console" ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 09:17:21 -0000 Hi, I would like to debug my ACPI resume/suspend but I'm limitated since I've no serial port on my laptop, just a parallel port... Is there a way to go through the parallel port instead of the serial port ? Thanks. -- NEPHTALI 'dak' Aurelien From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 10:13:56 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C21516A4CE; Sat, 11 Dec 2004 10:13:56 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id A35AE43D39; Sat, 11 Dec 2004 10:13:55 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iBBADrVM089334; Sat, 11 Dec 2004 11:13:53 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Aurelien Nephtali From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 11 Dec 2004 10:17:18 +0100." <41BABB1E.5000200@wanadoo.fr> Date: Sat, 11 Dec 2004 11:13:53 +0100 Message-ID: <89333.1102760033@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-current@freebsd.org cc: curent@freebsd.org Subject: Re: Setting up a "Parallel Console" ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 10:13:56 -0000 In message <41BABB1E.5000200@wanadoo.fr>, Aurelien Nephtali writes: >Hi, > > I would like to debug my ACPI resume/suspend but I'm limitated since >I've no serial port on my laptop, just a parallel port... >Is there a way to go through the parallel port instead of the serial port ? I've thought about it but never gotten around to it. If you have a printer it's not very hard though... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 10:17:46 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3D7616A4CE for ; Sat, 11 Dec 2004 10:17:46 +0000 (GMT) Received: from smtp10.wanadoo.fr (smtp10.wanadoo.fr [193.252.22.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5776C43D49 for ; Sat, 11 Dec 2004 10:17:46 +0000 (GMT) (envelope-from aurelien.nephtali@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf1002.wanadoo.fr (SMTP Server) with SMTP id 14C9924000A1; Sat, 11 Dec 2004 11:17:45 +0100 (CET) Received: from [192.168.2.30] (ca-sqy-11-176.w80-8.abo.wanadoo.fr [80.8.64.176]) by mwinf1002.wanadoo.fr (SMTP Server) with ESMTP id 9309D2400095; Sat, 11 Dec 2004 11:17:44 +0100 (CET) Message-ID: <41BAC947.6010905@wanadoo.fr> Date: Sat, 11 Dec 2004 11:17:43 +0100 From: Aurelien Nephtali User-Agent: Mozilla Thunderbird 0.9 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <89333.1102760033@critter.freebsd.dk> In-Reply-To: <89333.1102760033@critter.freebsd.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Setting up a "Parallel Console" ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 10:17:46 -0000 Poul-Henning Kamp wrote: > In message <41BABB1E.5000200@wanadoo.fr>, Aurelien Nephtali writes: > >>Hi, >> >> I would like to debug my ACPI resume/suspend but I'm limitated since >>I've no serial port on my laptop, just a parallel port... >>Is there a way to go through the parallel port instead of the serial port ? > > > I've thought about it but never gotten around to it. > > If you have a printer it's not very hard though... > I have a printer but I don't see what you mean by "it's not very hard though". Could you be clearer ? Thanks. -- NEPHTALI 'dak' Aurelien From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 10:24:50 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DF5B916A4CE for ; Sat, 11 Dec 2004 10:24:50 +0000 (GMT) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.FreeBSD.org (Postfix) with SMTP id 82E2243D68 for ; Sat, 11 Dec 2004 10:24:50 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 86514 invoked from network); 11 Dec 2004 10:24:49 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 11 Dec 2004 10:24:49 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iBBAOm7S068927 for ; Sat, 11 Dec 2004 11:24:48 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iBBAOmqB068926 for current@freebsd.org; Sat, 11 Dec 2004 11:24:48 +0100 (CET) (envelope-from pho) Date: Sat, 11 Dec 2004 11:24:48 +0100 From: Peter Holm To: current@freebsd.org Message-ID: <20041211102448.GA68917@peter.osted.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Fatal trap 12 in kern/kern_event.c:1451 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 10:24:51 -0000 http://www.holm.cc/stress/log/cons95.html -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 10:30:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A570D16A4CE for ; Sat, 11 Dec 2004 10:30:49 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B7CF43D39 for ; Sat, 11 Dec 2004 10:30:49 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iBBAUl1Y089656; Sat, 11 Dec 2004 11:30:47 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Aurelien Nephtali From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 11 Dec 2004 11:17:43 +0100." <41BAC947.6010905@wanadoo.fr> Date: Sat, 11 Dec 2004 11:30:47 +0100 Message-ID: <89655.1102761047@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-current@freebsd.org Subject: Re: Setting up a "Parallel Console" ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 10:30:49 -0000 In message <41BAC947.6010905@wanadoo.fr>, Aurelien Nephtali writes: >Poul-Henning Kamp wrote: >> In message <41BABB1E.5000200@wanadoo.fr>, Aurelien Nephtali writes: >> >>>Hi, >>> >>> I would like to debug my ACPI resume/suspend but I'm limitated since >>>I've no serial port on my laptop, just a parallel port... >>>Is there a way to go through the parallel port instead of the serial port ? >> >> >> I've thought about it but never gotten around to it. >> >> If you have a printer it's not very hard though... >> > >I have a printer but I don't see what you mean by "it's not very hard >though". Could you be clearer ? "... to write everything that goes to the console to the printer also" -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 10:45:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1991816A4CE for ; Sat, 11 Dec 2004 10:45:47 +0000 (GMT) Received: from smtp6.wanadoo.fr (smtp6.wanadoo.fr [193.252.22.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2E3D43D39 for ; Sat, 11 Dec 2004 10:45:46 +0000 (GMT) (envelope-from aurelien.nephtali@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0606.wanadoo.fr (SMTP Server) with SMTP id 964701C002BA; Sat, 11 Dec 2004 11:45:45 +0100 (CET) Received: from [192.168.2.30] (ca-sqy-11-176.w80-8.abo.wanadoo.fr [80.8.64.176]) by mwinf0606.wanadoo.fr (SMTP Server) with ESMTP id 6F1901C002B0; Sat, 11 Dec 2004 11:45:45 +0100 (CET) Message-ID: <41BACFD8.8040909@wanadoo.fr> Date: Sat, 11 Dec 2004 11:45:44 +0100 From: Aurelien Nephtali User-Agent: Mozilla Thunderbird 0.9 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <89655.1102761047@critter.freebsd.dk> In-Reply-To: <89655.1102761047@critter.freebsd.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Setting up a "Parallel Console" ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 10:45:47 -0000 Poul-Henning Kamp wrote: > > "... to write everything that goes to the console to the printer also" > OK :) So if it's possible, how can I do ? Is there a way or the way needs to be coded first ? Thanks. -- NEPHTALI 'dak' Aurelien From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 11:45:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C14E016A4CE for ; Sat, 11 Dec 2004 11:45:10 +0000 (GMT) Received: from smtp2.wanadoo.fr (smtp2.wanadoo.fr [193.252.22.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0309C43D31 for ; Sat, 11 Dec 2004 11:45:10 +0000 (GMT) (envelope-from cbaud@laposte.net) Received: from me-wanadoo.net (unknown [127.0.0.1]) by mwinf0206.wanadoo.fr (SMTP Server) with SMTP id B6E691C001B2 for ; Sat, 11 Dec 2004 12:45:08 +0100 (CET) Received: from libra.baudcl-liber.fr (AAmiens-151-1-34-133.w83-192.abo.wanadoo.fr [83.192.180.133]) by mwinf0206.wanadoo.fr (SMTP Server) with ESMTP id 4A86D1C001AB for ; Sat, 11 Dec 2004 12:45:08 +0100 (CET) From: "Claude B." To: freebsd-current@freebsd.org Content-Type: text/plain; charset=iso-8859-15 Message-Id: <1102769123.2856.11.camel@libra.baudcl-liber.fr> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4-8mdk Date: Sat, 11 Dec 2004 12:45:23 +0000 Content-Transfer-Encoding: 8bit Subject: Promise PDC20319 4 ports SATA and the RAID1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 11:45:10 -0000 Hello, I just install FreeBSD5.3 on Asus "PSCH-L" motherboard. There is a onboard ship Promise PDC20319 4 ports SATA and the RAID1 is setup in the BIOS "FastBuild(tm) Utility2.01(c) 2002-2005 Promise". The kernel messages and the next commands:"atacontrol list" and "atacontrol status ar0" point out all things are fine, except this line in the file /var/log/messages : "kernel: atapci0: failed: rid 0x20 is memory, requested 4". FreeBSD5.3 seems normally to work although I don't know how to make sure the RAID1 works fine. Here are commands issues and some lines of /var/log/messages: login# atacontrol list ATA channel 0: Master: acd0 ATA/ATAPI revision 4 Slave: no device present ATA channel 1: Master: no device present Slave: no device present ATA channel 2: Master: no device present Slave: no device present ATA channel 3: Master: ad6 Slave: no device present ATA channel 4: Master: no device present Slave: no device present ATA channel 5: Master: ad10 Slave: no device present login# atacontrol status ar0 ar0: ATA RAID1 subdisks: ad6 ad10 status: READY login# /var/log/messages: kernel: atapci0: port 0xb400-0xb47f,0xb800-0xb80f,0xbc00-0xbc3f mem 0xfc960000-0xfc97ffff,0xfc99f000-0xfc99ffff irq 27 at device 5.0 on pci2 kernel: atapci0: failed: rid 0x20 is memory, requested 4 kernel: ata2: channel #0 on atapci0 kernel: ata3: channel #1 on atapci0 kernel: ata4: channel #2 on atapci0 kernel: ata5: channel #3 on atapci0 What means this kernel message :"atapci0: failed: rid 0x20 is memory, requested 4" and how to make sure the RAID1 works fine? Thank in anticipation, claude -- Clé publique: http://pgp.mit.edu From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 12:19:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14C1916A4CE for ; Sat, 11 Dec 2004 12:19:41 +0000 (GMT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60C2D43D3F for ; Sat, 11 Dec 2004 12:19:40 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id iBBCJZwq091068; Sat, 11 Dec 2004 13:19:37 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <41BAE5C3.60609@DeepCore.dk> Date: Sat, 11 Dec 2004 13:19:15 +0100 From: =?ISO-8859-15?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Claude B." References: <1102769123.2856.11.camel@libra.baudcl-liber.fr> In-Reply-To: <1102769123.2856.11.camel@libra.baudcl-liber.fr> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: freebsd-current@freebsd.org Subject: Re: Promise PDC20319 4 ports SATA and the RAID1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 12:19:41 -0000 Claude B. wrote: > kernel: atapci0: port > 0xb400-0xb47f,0xb800-0xb80f,0xbc00-0xbc3f mem > 0xfc960000-0xfc97ffff,0xfc99f000-0xfc99ffff irq 27 at device 5.0 on pci= 2 > kernel: atapci0: failed: rid 0x20 is memory, requested 4 > kernel: ata2: channel #0 on atapci0 > kernel: ata3: channel #1 on atapci0 > kernel: ata4: channel #2 on atapci0 > kernel: ata5: channel #3 on atapci0 >=20 > What means this kernel message :"atapci0: failed: rid 0x20 is memory, > requested 4" and how to make sure the RAID1 works fine? Its just a warning from the kernel (which IMHO shouldn't be there). The reason is that "normal" ATA controllers has port space there and the = generic part of ATA probes it as part of the generic probe code. Later=20 in the probe where ATA knows it deals with a Promise chip it also knows=20 how to use that resource as memory space. --=20 -S=F8ren From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 12:44:14 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D848A16A4CE for ; Sat, 11 Dec 2004 12:44:14 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2008F43D5A for ; Sat, 11 Dec 2004 12:44:14 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iBBCiAJD091435; Sat, 11 Dec 2004 13:44:10 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Aurelien Nephtali From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 11 Dec 2004 11:45:44 +0100." <41BACFD8.8040909@wanadoo.fr> Date: Sat, 11 Dec 2004 13:44:09 +0100 Message-ID: <91434.1102769049@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-current@freebsd.org Subject: Re: Setting up a "Parallel Console" ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 12:44:15 -0000 In message <41BACFD8.8040909@wanadoo.fr>, Aurelien Nephtali writes: >Poul-Henning Kamp wrote: >> >> "... to write everything that goes to the console to the printer also" >> >OK :) >So if it's possible, how can I do ? >Is there a way or the way needs to be coded first ? You need to code it yourself. there are many faq's on the net about parallel ports etc. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 12:50:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A864116A4CE; Sat, 11 Dec 2004 12:50:10 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8572843D48; Sat, 11 Dec 2004 12:50:09 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iBBCo5an066431; Sat, 11 Dec 2004 23:20:05 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Sat, 11 Dec 2004 23:19:44 +1030 User-Agent: KMail/1.7.1 References: <41BABB1E.5000200@wanadoo.fr> In-Reply-To: <41BABB1E.5000200@wanadoo.fr> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3676883.eQkbMRFOpv"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412112320.04019.doconnor@gsoft.com.au> X-Spam-Score: -5.4 () IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: Aurelien Nephtali cc: curent@freebsd.org Subject: Re: Setting up a "Parallel Console" ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 12:50:10 -0000 --nextPart3676883.eQkbMRFOpv Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sat, 11 Dec 2004 19:47, Aurelien Nephtali wrote: > I would like to debug my ACPI resume/suspend but I'm limitated since > I've no serial port on my laptop, just a parallel port... > Is there a way to go through the parallel port instead of the serial port= ? If you have firewire you can use that. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart3676883.eQkbMRFOpv Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBuuz75ZPcIHs/zowRAirOAJ96W5znyQmwXCX4kjgBEYTaIuJECQCfUGoI v0l5gJa7/zWcTtEjhFG3iZk= =S6P8 -----END PGP SIGNATURE----- --nextPart3676883.eQkbMRFOpv-- From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 13:13:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC5A016A4CE for ; Sat, 11 Dec 2004 13:13:40 +0000 (GMT) Received: from smtp8.wanadoo.fr (smtp8.wanadoo.fr [193.252.22.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C66F43D60 for ; Sat, 11 Dec 2004 13:13:40 +0000 (GMT) (envelope-from aurelien.nephtali@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0801.wanadoo.fr (SMTP Server) with SMTP id 2ADC118000B3; Sat, 11 Dec 2004 14:13:39 +0100 (CET) Received: from [192.168.2.30] (ca-sqy-11-176.w80-8.abo.wanadoo.fr [80.8.64.176]) by mwinf0801.wanadoo.fr (SMTP Server) with ESMTP id DD497180008C; Sat, 11 Dec 2004 14:13:38 +0100 (CET) Message-ID: <41BAF281.5000009@wanadoo.fr> Date: Sat, 11 Dec 2004 14:13:37 +0100 From: Aurelien Nephtali User-Agent: Mozilla Thunderbird 0.9 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel O'Connor References: <41BABB1E.5000200@wanadoo.fr> <200412112320.04019.doconnor@gsoft.com.au> In-Reply-To: <200412112320.04019.doconnor@gsoft.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Setting up a "Parallel Console" ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 13:13:40 -0000 Daniel O'Connor wrote: > On Sat, 11 Dec 2004 19:47, Aurelien Nephtali wrote: > >> I would like to debug my ACPI resume/suspend but I'm limitated since >>I've no serial port on my laptop, just a parallel port... >>Is there a way to go through the parallel port instead of the serial port ? > > > If you have firewire you can use that. > Yes, but I do not have a firewire port. I just have a Parallel port! -- NEPHTALI 'dak' Aurelien From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 13:35:21 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DBC316A4CE for ; Sat, 11 Dec 2004 13:35:21 +0000 (GMT) Received: from smtp9.wanadoo.fr (smtp9.wanadoo.fr [193.252.22.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 933C943D58 for ; Sat, 11 Dec 2004 13:35:20 +0000 (GMT) (envelope-from cbaud@laposte.net) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0909.wanadoo.fr (SMTP Server) with SMTP id 39BF5240012C; Sat, 11 Dec 2004 14:35:19 +0100 (CET) Received: from libra.baudcl-liber.fr (AAmiens-151-1-34-133.w83-192.abo.wanadoo.fr [83.192.180.133]) by mwinf0909.wanadoo.fr (SMTP Server) with ESMTP id BB919240012B; Sat, 11 Dec 2004 14:35:18 +0100 (CET) From: "Claude B." To: =?ISO-8859-1?Q?S=F8ren?= Schmidt In-Reply-To: <41BAE5C3.60609@DeepCore.dk> References: <1102769123.2856.11.camel@libra.baudcl-liber.fr> <41BAE5C3.60609@DeepCore.dk> Content-Type: text/plain; charset=ISO-8859-15 Message-Id: <1102775734.3061.30.camel@libra.baudcl-liber.fr> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4-8mdk Date: Sat, 11 Dec 2004 14:35:34 +0000 Content-Transfer-Encoding: 8bit cc: freebsd-current@freebsd.org Subject: Re: Promise PDC20319 4 ports SATA and the RAID1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 13:35:21 -0000 Thank you Søren, I was a little worry about this message. What is means to make sure the RAID1 works fine? I have 2 X SATA Maxtor 6Y160M0 disks and RAID1 on. claude Le sam 11/12/2004 à 12:19, Søren Schmidt a écrit : > Claude B. wrote: > > > kernel: atapci0: port > > 0xb400-0xb47f,0xb800-0xb80f,0xbc00-0xbc3f mem > > 0xfc960000-0xfc97ffff,0xfc99f000-0xfc99ffff irq 27 at device 5.0 on pci2 > > kernel: atapci0: failed: rid 0x20 is memory, requested 4 > > kernel: ata2: channel #0 on atapci0 > > kernel: ata3: channel #1 on atapci0 > > kernel: ata4: channel #2 on atapci0 > > kernel: ata5: channel #3 on atapci0 > > > > What means this kernel message :"atapci0: failed: rid 0x20 is memory, > > requested 4" and how to make sure the RAID1 works fine? > > Its just a warning from the kernel (which IMHO shouldn't be there). > The reason is that "normal" ATA controllers has port space there and the > generic part of ATA probes it as part of the generic probe code. Later > in the probe where ATA knows it deals with a Promise chip it also knows > how to use that resource as memory space. -- Clé publique: http://pgp.mit.edu From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 13:48:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DF7516A4CE for ; Sat, 11 Dec 2004 13:48:40 +0000 (GMT) Received: from shrike.submonkey.net (cpc2-cdif3-6-0-cust204.cdif.cable.ntl.com [81.103.67.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 053E143D48 for ; Sat, 11 Dec 2004 13:48:40 +0000 (GMT) (envelope-from setantae@submonkey.net) Received: from setantae by shrike.submonkey.net with local (Exim 4.43 (FreeBSD)) id 1Cd7bx-000IGa-FX; Sat, 11 Dec 2004 13:48:37 +0000 Date: Sat, 11 Dec 2004 13:48:37 +0000 From: Ceri Davies To: trorki@area51.capnet.state.tx.us Message-ID: <20041211134837.GB70052@submonkey.net> Mail-Followup-To: Ceri Davies , trorki@area51.capnet.state.tx.us, Kris Kennaway , freebsd-current@freebsd.org References: <200412081205.39354.mi+mx@aldan.algebra.com> <20041208180601.T29045@area51.capnet.state.tx.us> <20041210205951.GA54091@xor.obsecurity.org> <20041210235009.O37514@area51.capnet.state.tx.us> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BI5RvnYi6R4T2M87" Content-Disposition: inline In-Reply-To: <20041210235009.O37514@area51.capnet.state.tx.us> X-PGP: finger ceri@FreeBSD.org User-Agent: Mutt/1.5.6i Sender: Ceri Davies cc: freebsd-current@freebsd.org cc: Kris Kennaway Subject: Re: AMD64 -current ISOs and cvsup repository: Was: Re: -current ISOs and update cvsup sites for AMD64? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 13:48:40 -0000 --BI5RvnYi6R4T2M87 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 11, 2004 at 12:28:14AM -0600, trorki@area51.capnet.state.tx.us = wrote: > On Fri, 10 Dec 2004, Kris Kennaway wrote: > > On Fri, Dec 10, 2004 at 10:50:11AM -0600, trorki@area51.capnet.state.tx= =2Eus >=20 > > > I've looked at snapshots.jp.freebsd.org and snapshots.se.freebsd.org > > > and can't find a recent snapshot ISO to get -current for AMD64. > > > Am I missing the directory, or what? Someone please let me know where > > > to get a recent ISO >=20 > > The above site; talk to the admins about why they're not being > > produced (probably it's just an oversight). >=20 > The last AMD64 -current ISO on snapshots.se and snapshots.jp was in > October, if I'm looking at the right directories. A month and a half is > hardly an "oversight", since October isn't even in the 6.0 timeframe. > Maybe terminology has changed since summer, but all the -current > sources peter out at the end of October, and no 6.0 build seems to > have ever worked on snapshots.se, to judge from the log files. > I'd like some help with AMD64 -current, yes AMD64 6.0-current. > Am I making this clear??? You're making something clear. Asshole. > I haven't played with -current since before the switch to 6.0 > as -current, so the last ISO I used (and still have) is a 5.x-current > from July. I want a clean AMD64 6.0-current ISO to start with, and that > would presumedly be AFTER November 05, preferably very recent... >=20 > > >, and where I should point cvsup for the updates. >=20 > > Updates to what? amd64 isn't different from the other architectures; > > you can read the documentation on using and configuring cvsup in the > > handbook, and if you have further specific questions then ask them > > then. >=20 > The information isn't IN the handbook, or is obscure. If it was > there to read, I wouldn't have asked the list. Duh. > Since I mentioned cvsup you might/maybe get the idea that I know > how to use it. Duh. >=20 > Since I can't find the snapshots where they are expected, > they might be somewhere else, and I'd probably need to cvsup from > somewhere else, too, which is why I asked. Duh. >=20 > Would somebody that actually uses -current on AMD64 tell me > how to get a recent ISO, Speak to the admins of the servers above and remind them that they have forgotten to update the scripts since 6 was branched. > and which servers are carrying the > AMD 6.0-current branch so I can cvsup updates? Any of them, like you were told. There is no separate CVS branch for amd64, like you were told. Duh. > Please don't reply to the list if you don't know what the hell > I'm asking about. I think Kris has a better idea of what you're talking about than you do. Ceri --=20 Only two things are infinite, the universe and human stupidity, and I'm not sure about the former. -- Einstein (attrib.) --BI5RvnYi6R4T2M87 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBuvq1ocfcwTS3JF8RArbFAKCY4PeCkGO+GVKQRBW3uQGFYP+lmwCeJ1RM MsNoXeWZ8tWGHTRoGydAT7Q= =jvc9 -----END PGP SIGNATURE----- --BI5RvnYi6R4T2M87-- From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 14:10:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F01C16A4CE for ; Sat, 11 Dec 2004 14:10:40 +0000 (GMT) Received: from av3-1-sn3.vrr.skanova.net (av3-1-sn3.vrr.skanova.net [81.228.9.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8AA1543D31 for ; Sat, 11 Dec 2004 14:10:39 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av3-1-sn3.vrr.skanova.net (Postfix, from userid 502) id BC1D137E51; Sat, 11 Dec 2004 15:10:38 +0100 (CET) Received: from smtp1-2-sn3.vrr.skanova.net (smtp1-2-sn3.vrr.skanova.net [81.228.9.178]) by av3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id AB0EF37E45; Sat, 11 Dec 2004 15:10:38 +0100 (CET) Received: from sentinel (h211n1fls11o822.telia.com [213.64.66.211]) by smtp1-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 7EDF33801A; Sat, 11 Dec 2004 15:10:38 +0100 (CET) From: "Daniel Eriksson" To: "'Conrad J. Sabatier'" , Date: Sat, 11 Dec 2004 15:10:32 +0100 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <20041210214815.12ebd529@dolphin.local.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcTfNNIiQdbX0PmLTweQGtdb/2boFQAVa67Q cc: 'Poul-Henning Kamp' Subject: RE: df showing weird stats for nfs mounts X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 14:10:40 -0000 Conrad J. Sabatier wrote: > dolphin:conrads:/usr/home/conrads$ df -H > Filesystem Size Used Avail Capacity > Mounted on > gateway:/mm 83906 30871 0B 100% /mm > gateway:/usr/home/ncvs 83906 -456 0B 100% > /usr/home/ncvs > gateway:/usr/ports/distfiles 83906 -456 0B 100% > /usr/ports/distfiles This problem started after the recent changes by phk to the mount code, and it also affects mount_nullfs. 2004.12.03.09.00.00 = OK 2004.12.08.12.00.00 = not OK Sorry, but that is all the info I have at the moment. /Daniel Eriksson From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 14:24:17 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2DABC16A4CE; Sat, 11 Dec 2004 14:24:17 +0000 (GMT) Received: from web.portaone.com (web.portaone.com [195.70.151.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6677643D5A; Sat, 11 Dec 2004 14:24:16 +0000 (GMT) (envelope-from sobomax@portaone.com) Received: from [192.168.1.26] ([192.168.1.26]) (authenticated bits=0) by web.portaone.com (8.12.11/8.12.11) with ESMTP id iBBEOD0a093231 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 11 Dec 2004 15:24:14 +0100 (CET) (envelope-from sobomax@portaone.com) Message-ID: <41BB0305.7000206@portaone.com> Date: Sat, 11 Dec 2004 16:24:05 +0200 From: Maxim Sobolev Organization: Porta Software Ltd User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: phk@freebsd.org Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.80/589/Wed Nov 17 13:38:41 2004 clamav-milter version 0.80j on www.portaone.com X-Virus-Status: Clean cc: "current@freebsd.org" Subject: GBDE write performance really sucks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 14:24:17 -0000 Hi Poul, I have noticed that GBDE write performance is very low, even on modest hardware (3.2 P4 with 1MB cache and 7200 IDE HDD): $ sudo dd if=/dev/zero of=/dev/ad0e.bde bs=128k 29491200 bytes transferred in 31.959903 secs (922756 bytes/sec) load: 0.00 cmd: dd 3289 [physwr] 0.00u 0.02s 0% 832k 229+0 records in 228+0 records out 29884416 bytes transferred in 32.376493 secs (923028 bytes/sec) load: 0.00 cmd: dd 3289 [physwr] 0.00u 0.02s 0% 832k 232+0 records in 231+0 records out 30277632 bytes transferred in 32.800038 secs (923097 bytes/sec) load: 0.00 cmd: dd 3289 [physwr] 0.00u 0.02s 0% 832k 238+0 records in 237+0 records out 31064064 bytes transferred in 33.637685 secs (923490 bytes/sec) load: 0.00 cmd: dd 3289 [physwr] 0.00u 0.02s 0% 832k 242+0 records in 241+0 records out 31588352 bytes transferred in 34.204824 secs (923506 bytes/sec) load: 0.00 cmd: dd 3289 [physwr] 0.00u 0.02s 0% 832k 247+0 records in 246+0 records out 32243712 bytes transferred in 34.898871 secs (923918 bytes/sec) load: 0.00 cmd: dd 3289 [physwr] 0.00u 0.02s 0% 832k 258+0 records in 257+0 records out 33685504 bytes transferred in 36.440052 secs (924409 bytes/sec) load: 0.00 cmd: dd 3289 [physwr] 0.00u 0.02s 0% 832k 262+0 records in 261+0 records out 34209792 bytes transferred in 36.990503 secs (924826 bytes/sec) gstat(8) shows that ad0e.bde is nearly 100% busy. I guess that exsessive seeks back and forth are knocking performance down, but are there any plans to address this issue? Since practical usefullness of the file system that can't even sustain 1MB/s on modest hardware is quiestionable. Regards, Maxim From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 14:30:28 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C75DD16A4CE; Sat, 11 Dec 2004 14:30:28 +0000 (GMT) Received: from postfix4-2.free.fr (postfix4-2.free.fr [213.228.0.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id 644C543D48; Sat, 11 Dec 2004 14:30:28 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (unknown [82.233.239.98]) by postfix4-2.free.fr (Postfix) with ESMTP id 3B13125593B; Sat, 11 Dec 2004 15:30:26 +0100 (CET) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 5FCF9412C; Sat, 11 Dec 2004 15:28:26 +0100 (CET) Date: Sat, 11 Dec 2004 15:28:25 +0100 From: Jeremie Le Hen To: Shunsuke SHINOMIYA Message-ID: <20041211142825.GB65171@obiwan.tataz.chchile.org> References: <20041210113318.BBF3.SHINO@fornext.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041210113318.BBF3.SHINO@fornext.org> User-Agent: Mutt/1.5.6i cc: freebsd-stable@freebsd.org cc: freebsd-current@freebsd.org cc: Jeremie Le Hen Subject: Re: if_em int_throttle_ceil patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 14:30:28 -0000 On Fri, Dec 10, 2004 at 12:00:21PM +0900, Shunsuke SHINOMIYA wrote: > The previous patch to change if_em's int_throttle_ceil into > sysctl-able cause a kernel panic. If you set em's int_throttle_ceil=0 > and then reconfigure the em, it cause a diveded by zero panic. > > This patch for original if_em.[ch] which is attached to this mail is > corrected this problem. Great work Shunsuke, thank you ! Any chance to get this patch reviewed and commited ? Although Bjoern Zeeb proposed to use a global way to control interrupt moderation among network drivers, there was no proposition to unify it. It would be a pity if this patch gets lost in the archives without being either commited or submited as a PR. Regards, -- Jeremie Le Hen jeremie@le-hen.org From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 14:54:26 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E759B16A4CE; Sat, 11 Dec 2004 14:54:26 +0000 (GMT) Received: from av9-2-sn1.fre.skanova.net (av9-2-sn1.fre.skanova.net [81.228.11.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68A8743D5E; Sat, 11 Dec 2004 14:54:26 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av9-2-sn1.fre.skanova.net (Postfix, from userid 502) id 96BC337EBA; Sat, 11 Dec 2004 15:54:25 +0100 (CET) Received: from smtp3-1-sn1.fre.skanova.net (smtp3-1-sn1.fre.skanova.net [81.228.11.163]) by av9-2-sn1.fre.skanova.net (Postfix) with ESMTP id 86D5937E4B; Sat, 11 Dec 2004 15:54:25 +0100 (CET) Received: from sentinel (h211n1fls11o822.telia.com [213.64.66.211]) by smtp3-1-sn1.fre.skanova.net (Postfix) with ESMTP id 2293D37E6F; Sat, 11 Dec 2004 15:54:25 +0100 (CET) From: "Daniel Eriksson" To: "'Maxim Sobolev'" , Date: Sat, 11 Dec 2004 15:54:19 +0100 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <41BB0305.7000206@portaone.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcTfjax1i96an0iPRb27iUEEYL/yiAAAoJ/A cc: current@freebsd.org Subject: RE: GBDE write performance really sucks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 14:54:27 -0000 Maxim Sobolev wrote: > I have noticed that GBDE write performance is very low, even > on modest > hardware (3.2 P4 with 1MB cache and 7200 IDE HDD): If you look through the freebsd-current archive you'll find a mail from me called "Simple BDE disc encryption benchmark" (2004-08-06). In that very simple benchmark I got quite different results on much slower hardware. I'll paste the entire mail below. As you can see from the benchmark, on old and slow hardware I managed to get ~4.5MB/s write performance (1.7GB written in 379 seconds). Could there be a problem with your test setup? ---[snip]--- Hi! I just ran a very simple benchmark on the GBDE disc encryption in CURRENT. The benchmark setup looked like this: * Slow machine (Celeron 366, 128MB mem) * 5-CURRENT from yesterday, running off of some old ATA disc * 2 x 9GB 10k rpm SCSI discs hooked up to an Adaptec 2940 The benchmark was to copy the /usr directory (copied from the ATA disc, 1.7GB) or a directory containing big files (/bigfiles, 1.7GB in 16 files created by 'dd if=/dev/random ...') from scsi disc 1 to scsi disc 2. I ran each benchmark twice and took a simple average of the results. unencrypted to unencrypted: /usr : 697 real 10.6 user 235 sys (~50% idle) /bigfiles: 123 real 0.4 user 84 sys (~25% idle) unencrypted to encrypted: /usr : 1778 real 10.7 user 236 sys (~35% idle) /bigfiles: 379 real 0.4 user 82 sys (~10% idle) encrypted to encrypted: /usr : 1978 real 11.6 user 242 sys (~25% idle) /bigfiles: 615 real 0.4 user 80 sys (0% idle) The only time the CPU was completely busy was when copying /bigfiles from encrypted to encrypted. ---[snip]--- /Daniel Eriksson From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 14:57:40 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BC42016A4CF for ; Sat, 11 Dec 2004 14:57:40 +0000 (GMT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 9F7A243D5D for ; Sat, 11 Dec 2004 14:57:39 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 13864 invoked by uid 65534); 11 Dec 2004 14:57:38 -0000 Received: from pD9E24334.dip.t-dialin.net (EHLO lofi.dyndns.org) (217.226.67.52) by mail.gmx.net (mp020) with SMTP; 11 Dec 2004 15:57:38 +0100 X-Authenticated: #443188 Received: from [192.168.8.4] (lofi@kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iBBEvW6B072913 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sat, 11 Dec 2004 15:57:33 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: freebsd-current@freebsd.org Date: Sat, 11 Dec 2004 15:57:29 +0100 User-Agent: KMail/1.7.1 References: <200412081205.39354.mi+mx@aldan.algebra.com> <20041210235009.O37514@area51.capnet.state.tx.us> <20041211134837.GB70052@submonkey.net> In-Reply-To: <20041211134837.GB70052@submonkey.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart14510773.SzMuOarRRh"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412111557.31017.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new cc: Ceri Davies cc: trorki@area51.capnet.state.tx.us cc: Kris Kennaway Subject: Re: AMD64 -current ISOs and cvsup repository: Was: Re: -current ISOs and update cvsup sites for AMD64? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 14:57:40 -0000 --nextPart14510773.SzMuOarRRh Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday, 11. December 2004 14:48, Ceri Davies wrote: > Speak to the admins of the servers above and remind them that they have > forgotten to update the scripts since 6 was branched. Incidentally, I noticed the breakage a few days ago as well and already tol= d=20 Will, who is however very short on time since he's about to graduate. =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart14510773.SzMuOarRRh Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBuwraXhc68WspdLARAgXuAJ9K4P5OUviDY/shBnX8fjDcRLSKDgCfYMHu TvIyMrS0560bmuKrEvuJbRs= =1S5p -----END PGP SIGNATURE----- --nextPart14510773.SzMuOarRRh-- From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 15:34:48 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E52616A4CE for ; Sat, 11 Dec 2004 15:34:48 +0000 (GMT) Received: from alternator.sgh.waw.pl (alternator.sgh.waw.pl [194.145.96.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5761443D39 for ; Sat, 11 Dec 2004 15:34:47 +0000 (GMT) (envelope-from dry@dry.pl) Received: from localhost (localhost [127.0.0.1]) by alternator.sgh.waw.pl (Postfix) with SMTP id 1E1002AA5D4 for ; Sat, 11 Dec 2004 16:34:45 +0100 (CET) Received: from prolongator.sgh.waw.pl (prolongator.sgh.waw.pl [194.145.96.30]) by alternator.sgh.waw.pl (Postfix) with ESMTP id 132502AA5C4 for ; Sat, 11 Dec 2004 16:34:45 +0100 (CET) Received: by prolongator.sgh.waw.pl (Postfix, from userid 5250) id 4FD0540EF; Sat, 11 Dec 2004 16:35:09 +0100 (CET) Date: Sat, 11 Dec 2004 16:35:09 +0100 From: Michal Suszko To: current@freebsd.org Message-ID: <20041211153509.GI1571@dry.pl> References: <20041208194721.GB1571@dry.pl> <20041210164407.E63382@carver.gumbysoft.com> <20041210164540.H63382@carver.gumbysoft.com> <20041211011032.GA10749@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041211011032.GA10749@xor.obsecurity.org> X-Organization: Dry User-Agent: Mutt/1.5.6i Subject: Re: deadlocks in recent 6-CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 15:34:48 -0000 On Fri, 10 December 2004 at 17:10:32 -0800, Kris Kennaway wrote: > On Fri, Dec 10, 2004 at 04:46:09PM -0800, Doug White wrote: > > Oops, ignore me. Didn't see that witness was enabled afterwards. > > > > > > PREEMPTION is on > > > > This is known to cause problems. You enable it at your own risk. > > Only on ULE, I thought. It's 4BSD in my case. > > > > WITNESS show two kinds of LOR's: > > If you're getting LORs, chances are good you'll also get deadlocks > (that's why lock order reversals are bad). Thanks to suggestions received off the list I removed 'user' rules from pf.conf and box runs fine for over 3 days. Michal From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 15:58:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41AB016A4CE for ; Sat, 11 Dec 2004 15:58:06 +0000 (GMT) Received: from smtp2.netcologne.de (smtp2.netcologne.de [194.8.194.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1E1943D39 for ; Sat, 11 Dec 2004 15:58:05 +0000 (GMT) (envelope-from thomas@laurel.tmseck.homedns.org) Received: from laurel.tmseck.homedns.org (xdsl-213-196-254-95.netcologne.de [213.196.254.95]) by smtp2.netcologne.de (Postfix) with SMTP id 9BD88432F for ; Sat, 11 Dec 2004 16:58:03 +0100 (MET) Received: (qmail 16410 invoked by uid 1001); 11 Dec 2004 15:58:25 -0000 Date: 11 Dec 2004 15:58:25 -0000 Message-ID: <20041211155825.16409.qmail@laurel.tmseck.homedns.org> From: tmseck-lists@netcologne.de (Thomas-Martin Seck) To: freebsd-current@freebsd.org Organization: a private site in Germany In-Reply-To: <20041210155518.O63382@carver.gumbysoft.com> X-Newsgroups: gmane.os.freebsd.current X-Attribution: tms Subject: Re: FreeBSD sound distortion problems with SB Live! fixed with PREEMPTION X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 15:58:06 -0000 * Doug White : > I purchased a SBLive 5.1 and ran tests with it in a Dell PowerEdge 1750 > (2x2.4GHz Xeon) the last time we had complaints about sound jitteryness > and I wasn't able to reproduce it, even with heavy buildworld load. > Guess its time to pull the card out and give it another try (after I just > pulled it out of the machine yesterday...) Do add another datapoint here: Playing an mp3 with mpg321 from the console while doing a 'make extract' or even 'make clean' in www/firefox is sufficient for reproducing the sound related issues here. (This is pIII-550 with a Soundblaster card (ES137x driver), 4BSD scheduler and an IDE disk on a Promise PDC20268 UDMA100 controller). With PREEMPTION enabled, the playback is slowed down noticeably, pops and clicks are rare, though. Without PREEMPTION enabled, mp3 output was severely distorted even when not much system activity happened beyond running mpg321. From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 16:50:16 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E73D416A4CE for ; Sat, 11 Dec 2004 16:50:16 +0000 (GMT) Received: from hex.databits.net (hex.databits.net [216.118.117.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5F9E43D31 for ; Sat, 11 Dec 2004 16:50:16 +0000 (GMT) (envelope-from will@csociety.org) Received: by hex.databits.net (Postfix, from userid 1001) id 2AD3C57ACB; Sat, 11 Dec 2004 10:50:16 -0600 (CST) Date: Sat, 11 Dec 2004 10:50:16 -0600 From: Will Andrews To: trorki@area51.capnet.state.tx.us Message-ID: <20041211165016.GI62516@hex.databits.net> Mail-Followup-To: trorki@area51.capnet.state.tx.us, freebsd-current@freebsd.org References: <200412081205.39354.mi+mx@aldan.algebra.com> <20041208180601.T29045@area51.capnet.state.tx.us> <20041210205951.GA54091@xor.obsecurity.org> <20041210235009.O37514@area51.capnet.state.tx.us> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3607uds81ZQvwCD0" Content-Disposition: inline In-Reply-To: <20041210235009.O37514@area51.capnet.state.tx.us> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: snapshots.se [was Re: AMD64 -current ISOs and cvsup repository: Was: Re: -current ISOs and update cvsup sites for AMD64?] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 16:50:17 -0000 --3607uds81ZQvwCD0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 11, 2004 at 12:28:14AM -0600, trorki@area51.capnet.state.tx.us = wrote: > The last AMD64 -current ISO on snapshots.se and snapshots.jp was in > October, if I'm looking at the right directories. A month and a half is > hardly an "oversight", since October isn't even in the 6.0 timeframe. Sure it is. 6.0 started in August. However, I haven't had time to even notice that snapshots.se is broken until recently. I usually rely on users such as yourself to notify me via the email address posted on the front page. As of today, I received one such email since most of the builds broke in late October. (For some reason, the site isn't popular among developers but rather only a few users. I don't know why.) At any rate, as Michael points out, I am much too busy dealing with my own problems to look at the ones on snapshots.se. I will be able to look at them in about 7 days. It will probably take me a few days from that point to get them all working again, since builds take quite a bit of time to run. While the scripts are in hiatus, please install 5.3 and upgrade to 6.0 from there. Or you can install one of the older 6.0 ISOs and upgrade from there. Sorry for any inconvenience this may cause. In the future, please notify the email address mentioned on the snapshots.se.freebsd.org site that something is wrong, before complaining on the mailing lists. Thank you. Regards, --=20 wca - snapshots.se.freebsd.org maintainer --3607uds81ZQvwCD0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBuyVHF47idPgWcsURAsNSAJsHTvvbwGc1IpvMf8bz8ocIw4tQtwCdFJnW /6ewm7sqY1+JeQKtPZyMr18= =Xhjs -----END PGP SIGNATURE----- --3607uds81ZQvwCD0-- From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 20:35:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99E2616A4CE for ; Sat, 11 Dec 2004 20:35:22 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCA4543D31 for ; Sat, 11 Dec 2004 20:35:21 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iBBKZHJR097665; Sat, 11 Dec 2004 21:35:18 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Maxim Sobolev From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 11 Dec 2004 16:24:05 +0200." <41BB0305.7000206@portaone.com> Date: Sat, 11 Dec 2004 21:35:17 +0100 Message-ID: <97664.1102797317@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: "current@freebsd.org" Subject: Re: GBDE write performance really sucks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 20:35:22 -0000 In message <41BB0305.7000206@portaone.com>, Maxim Sobolev writes: >Hi Poul, > >I have noticed that GBDE write performance is very low, even on modest >hardware (3.2 P4 with 1MB cache and 7200 IDE HDD): Which logical sectorsize did you use ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 21:00:55 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99B9D16A4D2 for ; Sat, 11 Dec 2004 21:00:55 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4288F43D31 for ; Sat, 11 Dec 2004 21:00:55 +0000 (GMT) (envelope-from gert.cuykens@gmail.com) Received: by rproxy.gmail.com with SMTP id z35so531558rne for ; Sat, 11 Dec 2004 13:00:54 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=BxfmcrQG5vHaFuDctbUmEmHdzxVnp0InOjTZhBohzJ7PbrvaCYRoMk4tKwzL7xhI0bIwOqmsaAgSqfeAtLdfO+GNY77JrPOx5+UJVdLD//riZyxDxvXD1Nm8BHCoMNi2OlLyCgxrsVmW4y7m2NYFBbP0QzhxWQRAn3zkr6dWdUQ= Received: by 10.38.163.80 with SMTP id l80mr655008rne; Sat, 11 Dec 2004 13:00:54 -0800 (PST) Received: by 10.38.104.71 with HTTP; Sat, 11 Dec 2004 13:00:54 -0800 (PST) Message-ID: Date: Sat, 11 Dec 2004 22:00:54 +0100 From: Gert Cuykens To: Thomas-Martin Seck In-Reply-To: <20041211155825.16409.qmail@laurel.tmseck.homedns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041210155518.O63382@carver.gumbysoft.com> <20041211155825.16409.qmail@laurel.tmseck.homedns.org> cc: freebsd-current@freebsd.org Subject: Re: FreeBSD sound distortion problems with SB Live! fixed with PREEMPTION X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Gert Cuykens List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 21:00:55 -0000 On 11 Dec 2004 15:58:25 -0000, Thomas-Martin Seck wrote: > * Doug White : > > > I purchased a SBLive 5.1 and ran tests with it in a Dell PowerEdge 1750 > > (2x2.4GHz Xeon) the last time we had complaints about sound jitteryness > > and I wasn't able to reproduce it, even with heavy buildworld load. > > Guess its time to pull the card out and give it another try (after I just > > pulled it out of the machine yesterday...) > > Do add another datapoint here: > > Playing an mp3 with mpg321 from the console while doing a 'make extract' > or even 'make clean' in www/firefox is sufficient for reproducing the > sound related issues here. (This is pIII-550 with a Soundblaster card > (ES137x driver), 4BSD scheduler and an IDE disk on a Promise PDC20268 > UDMA100 controller). With PREEMPTION enabled, the playback is slowed > down noticeably, pops and clicks are rare, though. Without PREEMPTION > enabled, mp3 output was severely distorted even when not much system > activity happened beyond running mpg321. > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > i think i have the same problem expect on my sk8n onboard sound (ich driver) i have total distortion all the time. help please, me would like sound very much :) From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 21:33:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F07416A4D1 for ; Sat, 11 Dec 2004 21:33:25 +0000 (GMT) Received: from smtp.dkm.cz (smtp.dkm.cz [62.24.64.34]) by mx1.FreeBSD.org (Postfix) with SMTP id 7F55B43D45 for ; Sat, 11 Dec 2004 21:33:24 +0000 (GMT) (envelope-from varga@stonehenge.sk) Received: (qmail 68642 invoked by uid 0); 11 Dec 2004 21:33:22 -0000 Received: from r4i114.chello.upc.cz (84.42.136.114) by smtp.dkm.cz with SMTP; 11 Dec 2004 21:33:22 -0000 From: Michal Varga To: freebsd-current@freebsd.org In-Reply-To: References: <20041210155518.O63382@carver.gumbysoft.com> <20041211155825.16409.qmail@laurel.tmseck.homedns.org> Content-Type: text/plain Organization: Stonehenge Date: Sat, 11 Dec 2004 22:31:59 +0100 Message-Id: <1102800719.52376.33.camel@andrasta.4net.local> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Re: FreeBSD sound distortion problems with SB Live! fixed with PREEMPTION X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 21:33:25 -0000 On Sat, 2004-12-11 at 22:00 +0100, Gert Cuykens wrote: > i think i have the same problem expect on my sk8n onboard sound (ich > driver) i have total distortion all the time. > > help please, me would like sound very much :) > Same problem here for about one year on two Athlon configurations, one with SB Live!, one with VT823x onboard, always running latest -CURRENT. (usually updated 4 times a month). The distortion is not really that bad, but it's always present, under any load. Even with 98% CPU idle, at least a second or two every other minute the sound is not "real time" (but not choppy, just "slow"). One can live with that, but it would be great to get rid of it, after all that time without any change.. By the way, Intel configuration with onboard audio (though, don't know right now what it was), which is mostly a clone of the OS used on two Athlons mentioned above doesn't show these symptoms. They were present for some time near the end of 2003, but after then the sound is fine there (at least until about half of 2004, didn't check after that, but no one mentioned any sound problems with this one). And maybe one more thing - with one of the Athlons (the SB Live! one), the distortions were present during earlier 2003 with FreeBSD 4.x too. The symptoms were not the same and not that much visible, but still present from time to time. Without any load, of course. m. -- Michal Varga Stonehenge From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 22:14:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 465EA16A4CE for ; Sat, 11 Dec 2004 22:14:03 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D09943D31 for ; Sat, 11 Dec 2004 22:14:02 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iBBMDqac099250; Sat, 11 Dec 2004 23:13:53 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Daniel Eriksson" From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 11 Dec 2004 15:10:32 +0100." Date: Sat, 11 Dec 2004 23:13:52 +0100 Message-ID: <99249.1102803232@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: "'Conrad J. Sabatier'" cc: freebsd-current@freebsd.org Subject: Re: df showing weird stats for nfs mounts X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 22:14:03 -0000 In message , "Daniel Eriksson" writes: >Conrad J. Sabatier wrote: > >> dolphin:conrads:/usr/home/conrads$ df -H >> Filesystem Size Used Avail Capacity >> Mounted on >> gateway:/mm 83906 30871 0B 100% /mm >> gateway:/usr/home/ncvs 83906 -456 0B 100% >> /usr/home/ncvs >> gateway:/usr/ports/distfiles 83906 -456 0B 100% >> /usr/ports/distfiles > >This problem started after the recent changes by phk to the mount code, and >it also affects mount_nullfs. > >2004.12.03.09.00.00 = OK >2004.12.08.12.00.00 = not OK > >Sorry, but that is all the info I have at the moment. Hi, I found one bug which I just fixed, it doesn't solve it for my NFS which makes me suspect ps/mohan may be involved. Is it possible that you can use the fix from rev. 1.171 in kern/vfs_mount.c and then try to nail down exactly which version of nfs_vfsops.c that breaks it ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 22:39:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 46E9316A4CF for ; Sat, 11 Dec 2004 22:39:52 +0000 (GMT) Received: from web80601.mail.yahoo.com (web80601.mail.yahoo.com [66.218.79.90]) by mx1.FreeBSD.org (Postfix) with SMTP id 3272243D5D for ; Sat, 11 Dec 2004 22:39:52 +0000 (GMT) (envelope-from mohan_srinivasan@yahoo.com) Message-ID: <20041211223952.67613.qmail@web80601.mail.yahoo.com> Received: from [64.168.23.67] by web80601.mail.yahoo.com via HTTP; Sat, 11 Dec 2004 14:39:52 PST Date: Sat, 11 Dec 2004 14:39:52 -0800 (PST) From: Mohan Srinivasan To: freebsd-current@freebsd.org, phk@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: NFS df bug... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 22:39:52 -0000 Among the changes that we committed, only nfs_vfsops.c:1.162 seems like a likely suspect. Can someone who can readily reproduce this back out that change and test ? mohan From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 22:48:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E602716A4CE for ; Sat, 11 Dec 2004 22:48:51 +0000 (GMT) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9C5943D5A for ; Sat, 11 Dec 2004 22:48:51 +0000 (GMT) (envelope-from alc@cs.rice.edu) Received: from localhost (calypso.cs.rice.edu [128.42.1.127]) by cs.rice.edu (Postfix) with ESMTP id 4AD474A9B3 for ; Sat, 11 Dec 2004 16:48:51 -0600 (CST) Received: from cs.rice.edu ([128.42.1.30]) by localhost (calypso.cs.rice.edu [128.42.1.127]) (amavisd-new, port 10024) with LMTP id 17511-01-4; Sat, 11 Dec 2004 16:48:50 -0600 (CST) Received: by cs.rice.edu (Postfix, from userid 19572) id E1B784A9AD; Sat, 11 Dec 2004 16:48:50 -0600 (CST) Date: Sat, 11 Dec 2004 16:48:50 -0600 From: Alan Cox To: current@freebsd.org Message-ID: <20041211224850.GV17820@cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2i X-Virus-Scanned: by amavis-20030616-p7 at cs.rice.edu cc: Alan Cox Subject: panic: sbflush_locked X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 22:48:52 -0000 I just got the following panic for a second time in the last three days doing a "make -jN buildworld". This is a with a recent copy of HEAD. If anyone wants more detail, let me know. panic: sbflush_locked: cc 4 || mb 0xffffff0052afa400 || mbcnt 0 cpuid = 1 KDB: enter: panic [thread pid 12163 tid 100188 ] Stopped at kdb_enter+0x2f: nop db> trace Tracing pid 12163 tid 100188 td 0xffffff008d169500 kdb_enter() at kdb_enter+0x2f panic() at panic+0x291 sbflush_locked() at sbflush_locked+0x64 sbrelease_locked() at sbrelease_locked+0x1c sbrelease() at sbrelease+0x48 sorflush() at sorflush+0x15c sofree() at sofree+0x204 soclose() at soclose+0x3af fifo_cleanup() at fifo_cleanup+0x38 fifo_close() at fifo_close+0x79 ufsfifo_close() at ufsfifo_close+0x7d vn_close() at vn_close+0x8e vn_closefile() at vn_closefile+0x65 fdrop_locked() at fdrop_locked+0xc0 closef() at closef+0x39 close() at close+0x1a5 syscall() at syscall+0x51e Xfast_syscall() at Xfast_syscall+0xa8 --- syscall (6, FreeBSD ELF64, close), rip = 0x41e2c0, rsp = 0x7fffffffded8, rbp = 0x57a540 --- From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 22:50:12 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B3C716A4CE for ; Sat, 11 Dec 2004 22:50:12 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 493C443D66 for ; Sat, 11 Dec 2004 22:50:11 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iBBMo7DP099911; Sat, 11 Dec 2004 23:50:08 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Mohan Srinivasan From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sat, 11 Dec 2004 14:39:52 PST." <20041211223952.67613.qmail@web80601.mail.yahoo.com> Date: Sat, 11 Dec 2004 23:50:07 +0100 Message-ID: <99910.1102805407@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-current@freebsd.org Subject: Re: NFS df bug... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 22:50:12 -0000 In message <20041211223952.67613.qmail@web80601.mail.yahoo.com>, Mohan Srinivas an writes: >Among the changes that we committed, only nfs_vfsops.c:1.162 seems >like a likely suspect. > >Can someone who can readily reproduce this back out that change and >test ? I tried that already but it didn't solve it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 22:58:22 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E43616A50B for ; Sat, 11 Dec 2004 22:58:22 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4921043D5F for ; Sat, 11 Dec 2004 22:58:22 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CdGBx-000LSb-Fa for freebsd-current@freebsd.org; Sat, 11 Dec 2004 14:58:21 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16827.31629.73080.383613@ran.psg.com> Date: Sat, 11 Dec 2004 14:58:21 -0800 To: FreeBSD Current Subject: buildkernel ath breakage X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 22:58:22 -0000 cvsup of 2004.12.11 08:54 gmt MAKE=/usr/obj/usr/src/make.i386/make sh /usr/src/sys/conf/newvers.sh ROAM cc -c -O -pipe -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror vers.c linking kernel.debug if_ath.o(.text+0x6fd): In function `ath_attach': /usr/src/sys/dev/ath/if_ath.c:436: undefined reference to `ath_rate_attach' if_ath.o(.text+0xc98): In function `ath_detach': /usr/src/sys/dev/ath/if_ath.c:607: undefined reference to `ath_rate_detach' if_ath.o(.text+0x3fd2): In function `ath_node_alloc': /usr/src/sys/dev/ath/if_ath.c:2300: undefined reference to `ath_rate_node_init' if_ath.o(.text+0x416e): In function `ath_node_free': /usr/src/sys/dev/ath/if_ath.c:2343: undefined reference to `ath_rate_node_cleanup' if_ath.o(.text+0x53e4): In function `ath_tx_start': /usr/src/sys/dev/ath/if_ath.c:3099: undefined reference to `ath_rate_findrate' if_ath.o(.text+0x581a):/usr/src/sys/dev/ath/if_ath.c:3287: undefined reference to `ath_rate_setupxtxdesc' if_ath.o(.text+0x5df9): In function `ath_tx_processq': /usr/src/sys/dev/ath/if_ath.c:3440: undefined reference to `ath_rate_tx_complete' if_ath.o(.text+0x6a63): In function `ath_newstate': /usr/src/sys/dev/ath/if_ath.c:3846: undefined reference to `ath_rate_newstate' if_ath.o(.text+0x6bb1):/usr/src/sys/dev/ath/if_ath.c:3876: undefined reference to `ath_rate_newstate' if_ath.o(.text+0x6d90): In function `ath_newassoc': /usr/src/sys/dev/ath/if_ath.c:3941: undefined reference to `ath_rate_newassoc' *** Error code 1 i will cvsup again on the presumption i caught sam mid-hacque. randy From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 23:03:05 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D46516A4CE; Sat, 11 Dec 2004 23:03:05 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0021B43D5D; Sat, 11 Dec 2004 23:03:04 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iBBN316t000214; Sun, 12 Dec 2004 00:03:01 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Ruslan Ermilov From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 08 Dec 2004 22:05:53 +0200." <20041208200553.GB1340@ip.net.ua> Date: Sun, 12 Dec 2004 00:03:01 +0100 Message-ID: <213.1102806181@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@FreeBSD.org Subject: Re: mount oddities X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 23:03:05 -0000 That's actually interesting... This patch fixes it. For all I can see, the responsibility for purging the buffer cache rests with the filesystem implementation, and therefore I would expect the problem to have existed ever since UFS2 was introduced. Anyone with a 5.3 box who can check if this is also a problem there ? Poul-Henning Index: ufs/ffs/ffs_vfsops.c =================================================================== RCS file: /home/ncvs/src/sys/ufs/ffs/ffs_vfsops.c,v retrieving revision 1.262 diff -u -r1.262 ffs_vfsops.c --- ufs/ffs/ffs_vfsops.c 7 Dec 2004 15:09:30 -0000 1.262 +++ ufs/ffs/ffs_vfsops.c 11 Dec 2004 22:56:42 -0000 @@ -778,6 +778,7 @@ out: if (bp) brelse(bp); + vinvalbuf(devvp, V_SAVE, NOCRED, td, 0, 0); if (cp != NULL) { DROP_GIANT(); g_topology_lock(); In message <20041208200553.GB1340@ip.net.ua>, Ruslan Ermilov writes: > >--ftEhullJWpWg/VHq >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline >Content-Transfer-Encoding: quoted-printable > >Hi Poul-Henning, > >I first noticed this oddity with MS-DOS formatted floppies, >when no matter what floppy I insert into the drive later, >it's still treated as MS-DOS. > >I believe the testcase below is related to the problem I'm >seeing. > >dd if=3D/dev/zero of=3Dimage bs=3D1k count=3D1440 >mdconfig -a -t vnode -f image -u 0 >mount /dev/md0 /mnt >newfs /dev/md0 >mount /dev/md0 /mnt && umount /mnt >mdconfig -du0 >mdconfig -a -t vnode -f image -u 0 >mount /dev/md0 /mnt >umount /mnt >mdconfig -du0 > >The second "mount" command should succeed but it doesn't. >Note that if you remove the first "mount" command, the >second one succeeds. > > >Cheers, >--=20 >Ruslan Ermilov >ru@FreeBSD.org >FreeBSD committer > >--ftEhullJWpWg/VHq >Content-Type: application/pgp-signature >Content-Disposition: inline > >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.2.6 (FreeBSD) > >iD8DBQFBt16gqRfpzJluFF4RAh8bAJ0cSjubWcK9lTAkCo03ZG4s/4LJ6gCgmXwA >aagYDX4qi4RAGiI2i21YCAQ= >=MzUk >-----END PGP SIGNATURE----- > >--ftEhullJWpWg/VHq-- > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 23:04:31 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A80316A4CE for ; Sat, 11 Dec 2004 23:04:31 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F57843D2F for ; Sat, 11 Dec 2004 23:04:31 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.90] ([66.127.85.90]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id iBBN4UWi044993 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 11 Dec 2004 15:04:30 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <41BB7D00.6050402@errno.com> Date: Sat, 11 Dec 2004 15:04:32 -0800 From: Sam Leffler Organization: Errno Consulting User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Randy Bush References: <16827.31629.73080.383613@ran.psg.com> In-Reply-To: <16827.31629.73080.383613@ran.psg.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD Current Subject: Re: buildkernel ath breakage X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 23:04:31 -0000 You're missing device ath_rate_onoe this was mentioned in the HEADSUP. Likewise people experiencing WEP problems should make sure they have device wlan_wep in their kernel or built as a module and available for loading. Sam From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 23:07:03 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEF5516A4CE for ; Sat, 11 Dec 2004 23:07:03 +0000 (GMT) Received: from ran.psg.com (ip192.186.dsl-acs2.seawa0.iinet.com [209.20.186.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D92343D54 for ; Sat, 11 Dec 2004 23:07:03 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.43 (FreeBSD)) id 1CdGKM-000Lgz-Lu; Sat, 11 Dec 2004 15:07:02 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16827.32150.170345.893195@ran.psg.com> Date: Sat, 11 Dec 2004 15:07:02 -0800 To: Sam Leffler References: <16827.31629.73080.383613@ran.psg.com> <41BB7D00.6050402@errno.com> cc: FreeBSD Current Subject: Re: buildkernel ath breakage X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 23:07:03 -0000 > You're missing > device ath_rate_onoe whoops! sorreee! perhaps a not should also go in UPDATING? randy From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 23:10:33 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA41416A4CE for ; Sat, 11 Dec 2004 23:10:33 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7225043D5A for ; Sat, 11 Dec 2004 23:10:33 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 68B8272DD4; Sat, 11 Dec 2004 15:10:33 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 6420372DCB; Sat, 11 Dec 2004 15:10:33 -0800 (PST) Date: Sat, 11 Dec 2004 15:10:33 -0800 (PST) From: Doug White To: Krzysztof Kowalik In-Reply-To: <20041209172941.GA29369@uci.agh.edu.pl> Message-ID: <20041211141852.M72997@carver.gumbysoft.com> References: <20041207234840.7287cdf4@maya.liquidx.org> <1102506431.1090.8.camel@taxman> <41B6ED4E.6030301@fer.hr> <20041209172941.GA29369@uci.agh.edu.pl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: FreeBSD sound distortion problems with SB Live! fixed with PREEMPTION X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 23:10:33 -0000 Okay, I'm testing this now ... so far no issues, unless I force things. The system is currently running 5.3-STABLE built Dec 5. The machine is an Althon 3000+ (Barton) on a KT400-based Soyo using either the built-in CMI audio or a PCI SBLive 5.1 Digital card. SCHED_4BSD, no PREEMPTION, no apic, no WITNESS/INVARIANTS. I played a 160kb VBR MP3 with mpg321 (mpg123 was compiled to use esound on this system so I decided to try something not so polluted) direct to each card in turn with a -j3 buildworld running in the background, using the same disk as the MP3s were located on. I ran the buildworld in a Konsole window on KDE 3.2.3 and played the mp3's in another. I start getting wierdness when the load average hits 5+ with 0% idle. Otherwise things hold up. Interrupt layout: zao,ttyp3,~,11>vmstat -i interrupt total rate irq0: clk 115654 99 irq1: atkbd0 3131 2 irq5: fwohci0 uhci2 2 0 irq6: fdc0 9 0 irq8: rtc 148030 127 irq10: pcm0 ehci0 23453 20 irq11: vr0 uhci0 23291 20 irq12: pcm1 uhci1 20841 17 irq13: npx0 1 0 irq14: ata0 64869 56 irq15: ata1 46 0 Total 399327 344 During the test pcm0 is running at 600 interrupts/s and pcm1 is at a measely 85 interrupts/s. If you are getting distortion on an otherwise idle system I'll be more interested, although that doesn't appear to be the case... I'll repeat the runs after world finishes building & installing and see if its something that changed in the last week. I'd suggest that people verify that their sound card isn't stuck on the same interrupt as a really busy device or they aren't having a quiet interrupt storm going off somewhere else or otherwise running things that chew CPU. Of course, make sure WITNESS & INVARIANTS are removed from the running kernel. WITNESS is guaranteed to cause problems with sound; setting 'sysctl debug.witness.watch=0' should clear up problems immediately if you have WITNESS compiled in. phk's suggested that usb is a huge hog and sharing interrupts with a USB controller could cause latency problems. I'll investigate this after the buildworld finishes and I check if things are different than with last week's build. On Thu, 9 Dec 2004, Krzysztof Kowalik wrote: > Ivan Voras [ivoras@fer.hr] wrote: > > [...] > > Not exactly a freeze, but PREEMPTION doesn't help me at all with SB Live > > (slowdowns, stuttering sound, etc.), especially with large amounts of > > filesystem operations (this is 5-stable). > > Exactly. I tried to use both emu10k1 and emu10kx drivers, with kernel > with and without PREEMPTION, and both 5.x and 6.0 serie did behave same. > Intensive I/O made the system quite unusable, and it was not only a > sound-related issue, but a general one -- slow, lagging mouse in X, etc. > > I asked about it on stable@ and somehow got no answers but "me too". > > Finally, I decided to restore my 4.9 system from the backups, where the > problem does not exist. > > Regards, > -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 23:36:50 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E4B4816A4CE for ; Sat, 11 Dec 2004 23:36:50 +0000 (GMT) Received: from ns1.kolbu.ws (ns1.kolbu.ws [81.0.164.100]) by mx1.FreeBSD.org (Postfix) with SMTP id 0CBC643D39 for ; Sat, 11 Dec 2004 23:36:50 +0000 (GMT) (envelope-from oyvind@ns1.kolbu.ws) Received: (qmail 69493 invoked by uid 1000); 11 Dec 2004 23:36:49 -0000 Date: Sun, 12 Dec 2004 00:36:49 +0100 From: =?iso-8859-1?Q?=D8yvind?= Kolbu To: current@freebsd.org Message-ID: <20041211233649.GA69017@ns1.kolbu.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.6i Subject: Panic when mounting ntfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 23:36:51 -0000 Tried to mount my ntfs drive after an upgrade to todays current, running a GENERIC kernel. Kernel and userland in sync, this happens every time I try to mount the drive. Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x0 fault code = supervisor read instruction pointer = 0x8:0xc205596c stack pointer = 0x10:0xe6655830 frame pointer = 0x10:0xe665584c 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 = 507 (mount_ntfs) [thread pid 507 100077 ] Stopped at ntfs_u28_init+0x7c: movzwl 0(%edx,%edi,2),%eax db> trace Tracing pid 507 tid 100077 td 0xc1d56a80 ntfs_u28_init(c1fe7e00,0,0,0,0) at ntfs_u28_init+0x7c ntfs_mount(c1c18400,c1d56a80,e6655abc,2c3,0) at ntfs_mount+0x65c vfs_donmount(e6655be4,c0944360,c1fe7d00,18,e6655d14) at vfs_donmount+0x9ba kernel_mount(c1c0f320,0,c2056271,1ed,bfdfee07) at kernel_mount+0x5c ntfs_cmount(c1c0f320,bfdfec50,0,c1d56a80,0) at ntfs_cmount+0x13d mount(c1d56a80,e6655d14,10,377,4) at mount+0x175 syscall(2f,2f,2f,0,bfbfe7f0) at syscall+0x137 Xint0x80_syscall() at Xint0x80_syscall+0x17 --- syscall (21, FreeBSD ELF32, mount), eip = 0x280ca41f, esp=0xbfbfe7ac, ebp = 0xbfbfecf8 --- db> -- Øyvind Kolbu From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 23:40:02 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B46316A4CE for ; Sat, 11 Dec 2004 23:40:02 +0000 (GMT) Received: from ebb.errno.com (ebb.errno.com [66.127.85.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 337E243D45 for ; Sat, 11 Dec 2004 23:40:01 +0000 (GMT) (envelope-from sam@errno.com) Received: from [66.127.85.90] ([66.127.85.90]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id iBBNdwWi045166 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 11 Dec 2004 15:39:59 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <41BB8550.30208@errno.com> Date: Sat, 11 Dec 2004 15:40:00 -0800 From: Sam Leffler Organization: Errno Consulting User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pawel Worach References: <200412081109.43840.sam@errno.com> <20041209.100008.21874313.rushani@bl.mmtr.or.jp> <200412081744.27539.sam@errno.com> <20041209.225041.63112571.rushani@bl.mmtr.or.jp> <41B9454F.9080903@errno.com> <41BA4B22.5070403@telia.com> In-Reply-To: <41BA4B22.5070403@telia.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: WEP does not work? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 23:40:02 -0000 Pawel Worach wrote: > Sam Leffler wrote: > >> I'll try to look tomorrow. I have a patch for fixing wep with ndis >> that I need to review and this is probably the same thing. > > > I have the same problem on a ThinkPad T41. What problem? Are you saying that wep does not work with the ath driver? I communicated with a couple of people that have setup static key'd wep fine so I'm not sure what to think. I've still had no time to try it myself (it was tested a while back but not immediatel before the commit). One thing I found from talking to folks is I did not make it clear you must have the wlan_wep module configured in the kernel or available for loading by the wlan layer when you configure a wep key. But if that happens then ifconfig will complain; things won't silently fail. > > Device is: > ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413) > ath0: mem 0xc0210000-0xc021ffff irq 11 at device 2.0 on pci2 > ath0: Ethernet address: 00:05:4e:4b:76:13 > ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3 > > Sysctls: > dev.ath.0.countrycode: 0 > dev.ath.0.regdomain: 97 > > I tried setting hw.ath.countrycode to 752 (sweden) but the driver > complained on boot that it was invalid. It was zero with the old > kernel too. Regdomain 97 is incompatible with the country code you requested. What were you trying to accomplish by setting the country code? > > The card works fine in ad-hoc mode without wep, if I enable wep it breaks. "breaks" how? Please provide the exact steps you take to demonstrate the problem. > The funny thing is that on the other end I can see ARP requests but no > replies are sent when wep is on (other end is a ~3 weeks old current with > a cisco aironet 350 card). "status" claims "associated", everything looks > the way it should be. > > # ifconfig ath0 list chan > Channel 1 : 2412 Mhz 11g Channel 48 : 5240* Mhz 11a > Channel 2 : 2417 Mhz 11g Channel 52 : 5260* Mhz 11a > Channel 3 : 2422 Mhz 11g Channel 56 : 5280* Mhz 11a > Channel 4 : 2427 Mhz 11g Channel 60 : 5300* Mhz 11a > Channel 5 : 2432 Mhz 11g Channel 64 : 5320* Mhz 11a > Channel 6 : 2437 Mhz 11g Channel 100 : 5500* Mhz 11a > Channel 7 : 2442 Mhz 11g Channel 104 : 5520* Mhz 11a > Channel 8 : 2447 Mhz 11g Channel 108 : 5540* Mhz 11a > Channel 9 : 2452 Mhz 11g Channel 112 : 5560* Mhz 11a > Channel 10 : 2457 Mhz 11g Channel 116 : 5580* Mhz 11a > Channel 11 : 2462 Mhz 11g Channel 120 : 5600* Mhz 11a > Channel 12 : 2467* Mhz 11g Channel 124 : 5620* Mhz 11a > Channel 13 : 2472* Mhz 11g Channel 128 : 5640* Mhz 11a > Channel 14 : 2484* Mhz 11b Channel 132 : 5660* Mhz 11a > Channel 34 : 5170* Mhz 11a Channel 136 : 5680* Mhz 11a > Channel 36 : 5180* Mhz 11a Channel 140 : 5700* Mhz 11a > Channel 38 : 5190* Mhz 11a Channel 149 : 5745* Mhz 11a > Channel 40 : 5200* Mhz 11a Channel 153 : 5765* Mhz 11a > Channel 42 : 5210* Mhz 11a Channel 157 : 5785* Mhz 11a > Channel 44 : 5220* Mhz 11a Channel 161 : 5805* Mhz 11a > Channel 46 : 5230* Mhz 11a Channel 165 : 5825* Mhz 11a > > Ad-Hoc mode without wep: > # ifconfig -v ath0 > ath0: flags=8843 mtu 1500 > inet 192.168.1.200 netmask 0xffffff00 broadcast 192.168.1.255 > inet6 fe80::205:4eff:fe4b:7613%ath0 prefixlen 64 scopeid 0x2 > ether 00:05:4e:4b:76:13 > media: IEEE 802.11 Wireless Ethernet autoselect > (autoselect ) > status: associated > ssid cookie channel 7 (2442) bssid da:00:a4:01:3b:02 > authmode OPEN privacy OFF deftxkey UNDEF powersavemode OFF > powersavesleep 100 txpowmax 34 txpower 60 rtsthreshold 2312 > protmode CTS > wme roaming AUTO bintval 100 > AC_BE cwmin 4 cwmax 10 aifs 3 txopLimit 0 -acm ack > cwmin 4 cwmax 10 aifs 3 txopLimit 0 -acm > AC_BK cwmin 4 cwmax 10 aifs 7 txopLimit 0 -acm ack > cwmin 4 cwmax 10 aifs 7 txopLimit 0 -acm > AC_VI cwmin 3 cwmax 4 aifs 2 txopLimit 94 -acm ack > cwmin 3 cwmax 4 aifs 2 txopLimit 94 -acm > AC_VO cwmin 2 cwmax 3 aifs 2 txopLimit 47 -acm ack > cwmin 2 cwmax 3 aifs 2 txopLimit 47 -acm How about showing ifconfig when wep is configured? And btw, the -v option is NOT needed; ifconfig should show all useful info w/o -v. > > I also get a couple of these from time to time, could be related to > reconfiguration. > ath0: device timeout > ath0: device timeout > ath0: device timeout > You should not get these. Please go to /usr/src/tools/tools/ath and build athstats. Run it w/o arguments and provide the output. Please identify what your configuration was when these occurred (e.g. adhoc mode w/ wep?). > Another minor thing I noted, when you play around with 'ifconfig ath0 > wepmode' > it looks like the wepkeys are displayed sometimes and sometimes not > afterwards, it seems very random. It it required to set wepkey and > wepmode in the same > command? > Never seen it. You can enable debugging in the 802.11 layer and/or ath driver to observe crypto operations. In the tools/ath directory you'll find athdebug and 80211debug apps; use them to enable debugging with something like 80211debug +crypto to see 802.11 layer operations and/or athdebug +crypto to see stuff happen in the driver. Sam From owner-freebsd-current@FreeBSD.ORG Sat Dec 11 23:55:07 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5621716A4CE for ; Sat, 11 Dec 2004 23:55:07 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 100CC43D64 for ; Sat, 11 Dec 2004 23:55:03 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iBBNsxdI082247; Sun, 12 Dec 2004 10:24:59 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Aurelien Nephtali Date: Sun, 12 Dec 2004 10:24:48 +1030 User-Agent: KMail/1.7.1 References: <41BABB1E.5000200@wanadoo.fr> <200412112320.04019.doconnor@gsoft.com.au> <41BAF281.5000009@wanadoo.fr> In-Reply-To: <41BAF281.5000009@wanadoo.fr> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1483255.bUJiLiWEbs"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412121024.57858.doconnor@gsoft.com.au> X-Spam-Score: -5.4 () IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: freebsd-current@freebsd.org Subject: Re: Setting up a "Parallel Console" ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Dec 2004 23:55:07 -0000 --nextPart1483255.bUJiLiWEbs Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sat, 11 Dec 2004 23:43, Aurelien Nephtali wrote: > > If you have firewire you can use that. > > Yes, but I do not have a firewire port. I just have a Parallel port! Ahh, pitty :( I don't think there's any built-in way of grabbing a dump in that case.. As PHK said though, it's probably not too hard to add :) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1483255.bUJiLiWEbs Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBu4jR5ZPcIHs/zowRAhf9AKCYa7wQgChW4/IB6izE7DK2vxbomACfde6F B/CQFZViKYwU5U8EgyZSRw4= =teQ9 -----END PGP SIGNATURE----- --nextPart1483255.bUJiLiWEbs-- From owner-freebsd-current@FreeBSD.ORG Sun Dec 12 00:00:30 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91E0016A4CF; Sun, 12 Dec 2004 00:00:30 +0000 (GMT) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1996F43D5E; Sun, 12 Dec 2004 00:00:30 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.1/8.13.1) with ESMTP id iBC00TTs061448; Sat, 11 Dec 2004 19:00:29 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.1/8.13.1) with ESMTP id iBC00SjA099535; Sat, 11 Dec 2004 19:00:28 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id B5A357306E; Sat, 11 Dec 2004 19:00:28 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041212000028.B5A357306E@freebsd-current.sentex.ca> Date: Sat, 11 Dec 2004 19:00:28 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/625/Fri Dec 10 12:41:57 2004 clamav-milter version 0.80j on clamscanner3 X-Virus-Scanned: ClamAV 0.80/625/Fri Dec 10 12:41:57 2004 clamav-milter version 0.80j on clamscanner1 X-Virus-Status: Clean X-Virus-Status: Clean Subject: [current tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Dec 2004 00:00:30 -0000 TB --- 2004-12-11 22:16:07 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-12-11 22:16:07 - starting CURRENT tinderbox run for i386/i386 TB --- 2004-12-11 22:16:07 - checking out the source tree TB --- 2004-12-11 22:16:07 - cd /home/tinderbox/CURRENT/i386/i386 TB --- 2004-12-11 22:16:07 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-12-11 22:22:36 - building world (CFLAGS=-O2 -pipe) TB --- 2004-12-11 22:22:36 - cd /home/tinderbox/CURRENT/i386/i386/src TB --- 2004-12-11 22:22:36 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-12-11 23:29:08 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-12-11 23:29:08 - cd /home/tinderbox/CURRENT/i386/i386/src TB --- 2004-12-11 23:29:08 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sat Dec 11 23:29:08 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for GENERIC completed on Sat Dec 11 23:46:28 UTC 2004 TB --- 2004-12-11 23:46:28 - generating LINT kernel config TB --- 2004-12-11 23:46:28 - cd /home/tinderbox/CURRENT/i386/i386/src/sys/i386/conf TB --- 2004-12-11 23:46:28 - /usr/bin/make -B LINT TB --- 2004-12-11 23:46:28 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-12-11 23:46:28 - cd /home/tinderbox/CURRENT/i386/i386/src TB --- 2004-12-11 23:46:28 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Dec 11 23:46:28 UTC 2004 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -O2 -pipe -I/sys/contrib/dev/acpica -D_KERNEL -DKLD_MODULE -nostdinc -I- -I/sys/contrib/dev/acpica -include /tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -I/tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/LINT -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c: In function `acpi_ibm_attach': /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c:155: error: `_COMPONENT' undeclared (first use in this function) /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c:155: error: (Each undeclared identifier is reported only once /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c:155: error: for each function it appears in.) /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c:155: error: `_THIS_MODULE' undeclared (first use in this function) /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c: In function `acpi_ibm_detach': /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm/../../../dev/acpi_support/acpi_ibm.c:260: error: `_Dbg' undeclared (first use in this function) *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_ibm. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src/sys/modules. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/LINT. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. TB --- 2004-12-12 00:00:28 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-12-12 00:00:28 - ERROR: failed to build lint kernel TB --- 2004-12-12 00:00:28 - tinderbox aborted